React-BoilerPlate deploy to heroku successful but Application Error - heroku

i clone React-BoilerPlate and edit for test create web
and i try deploy to heroku
it's successful in log but when i open browser it show "Application Error"
(in my mac dont have problem it working)
logs in dashboard.heroku.com
-----> Node.js app detected
-----> Creating runtime environment
NPM_CONFIG_LOGLEVEL=error
NODE_VERBOSE=false
NODE_ENV=production
NODE_MODULES_CACHE=true
-----> Installing binaries
engines.node (package.json): >=5
engines.npm (package.json): >=3
Resolving node version >=5...
Downloading and installing node 10.4.1...
Bootstrapping npm >=3 (replacing 6.1.0)...
npm 6.1.0 installed
-----> Restoring cache
Loading 2 from cacheDirectories (default):
- node_modules
- bower_components (not cached - skipping)
-----> Building dependencies
Installing node modules (package.json + package-lock)
> myapp#1.0.0 preinstall /tmp/build_4cc58fca63d336e918330c92a7320a18
> npm run npmcheckversion
> myapp#1.0.0 npmcheckversion /tmp/build_4cc58fca63d336e918330c92a7320a18
> node ./internals/scripts/npmcheckversion.js
> myapp#1.0.0 postinstall /tmp/build_4cc58fca63d336e918330c92a7320a18
> npm run build:dll
> myapp#1.0.0 build:dll /tmp/build_4cc58fca63d336e918330c92a7320a18
> node ./internals/scripts/dependencies.js
audited 25883 packages in 17.902s
found 46 vulnerabilities (8 low, 38 moderate)
run `npm audit fix` to fix them, or `npm audit` for details
Running heroku-postbuild
> myapp#1.0.0 heroku-postbuild /tmp/build_4cc58fca63d336e918330c92a7320a18
> npm install && npm run build
> myapp#1.0.0 preinstall /tmp/build_4cc58fca63d336e918330c92a7320a18
> npm run npmcheckversion
> myapp#1.0.0 npmcheckversion /tmp/build_4cc58fca63d336e918330c92a7320a18
> node ./internals/scripts/npmcheckversion.js
> myapp#1.0.0 postinstall /tmp/build_4cc58fca63d336e918330c92a7320a18
> npm run build:dll
> myapp#1.0.0 build:dll /tmp/build_4cc58fca63d336e918330c92a7320a18
> node ./internals/scripts/dependencies.js
audited 25883 packages in 16.989s
found 46 vulnerabilities (8 low, 38 moderate)
run `npm audit fix` to fix them, or `npm audit` for details
> myapp#1.0.0 prebuild /tmp/build_4cc58fca63d336e918330c92a7320a18
> npm run build:clean
> myapp#1.0.0 build:clean /tmp/build_4cc58fca63d336e918330c92a7320a18
> rimraf ./build
> myapp#1.0.0 build /tmp/build_4cc58fca63d336e918330c92a7320a18
> cross-env NODE_ENV=production webpack --config internals/webpack/webpack.prod.babel.js --color -p --progress --hide-modules --display-optimization-bailout
Hash: d1b0ba3fc6910d2a897a
Version: webpack 3.5.5
Time: 45827ms
Asset Size Chunks Chunk Names
68b0c4fcb84d239f261c1a5e65818142.gif 4.13 kB [emitted]
bc47c23f4a28a80f48dbafb4ae48d853.svg 602 bytes [emitted]
b812ddd6e7e7c9bd9fc5ba89d1a87ecd.svg 693 bytes [emitted]
68d2042ac5fdae4387e8f3b98e80d755.png 19.3 kB [emitted]
0ae4b3198c60ae8e849a17c2b9e36362.png 1.99 kB [emitted]
0c41c45073224f7bf4dfdbf7b703c05c.png 2.34 kB [emitted]
ec6994795fdd10b1a14a82dd076e7c31.otf 40.1 kB [emitted]
ce0b1f00d0b40ef65010ac4ec7e4f6a3.otf 39.8 kB [emitted]
.htaccess.bin 1.79 kB [emitted]
favicon.ico 370 kB [emitted]
icon-120x120.png 11.2 kB [emitted]
icon-128x128.png 11.2 kB [emitted]
icon-144x144.png 12.7 kB [emitted]
icon-152x152.png 13.9 kB [emitted]
icon-167x167.png 16.5 kB [emitted]
icon-180x180.png 14.4 kB [emitted]
icon-192x192.png 17.9 kB [emitted]
icon-384x384.png 42 kB [emitted]
icon-512x512.png 16.7 kB [emitted]
icon-72x72.png 5.89 kB [emitted]
icon-96x96.png 8.11 kB [emitted]
manifest.json 975 bytes [emitted]
9a4cbc132ce42296701bb3cc91fc8bd3.svg 930 bytes [emitted]
ced611daf7709cc778da928fec876475.eot 2.05 kB [emitted]
f97e3bbf73254b0112091d0192f17aec.svg 2.15 kB [emitted]
d41f55a78e6f49a5512878df1737e58a.ttf 1.89 kB [emitted]
b7c9e1e479de3b53f1e4e30ebac2403a.woff 1.38 kB [emitted]
0.0f8f8d839c3c67ea9a03.chunk.js 343 kB 0 [emitted] [big]
1.d9aef47ea860a023a399.chunk.js 331 kB 1 [emitted] [big]
2.02140dd8fb729e8ec62d.chunk.js 338 kB 2 [emitted] [big]
3.59f24490e8d9db438d4a.chunk.js 162 kB 3 [emitted]
4.dedc780d9ee602a24732.chunk.js 81.5 kB 4 [emitted]
5.14ce9b3d76aef2ba3592.chunk.js 40.6 kB 5 [emitted]
6.0c6db533aceba6385e37.chunk.js 45.3 kB 6 [emitted]
7.98b59f40657a56912eaf.chunk.js 46 kB 7 [emitted]
8.3a4ea6143fc6f0ca179e.chunk.js 26.1 kB 8 [emitted]
9.13d365030651a79eb21d.chunk.js 17.5 kB 9 [emitted]
10.1e3ab2bf211e3c6c6232.chunk.js 41.1 kB 10 [emitted]
11.260090743f2cac2a0f93.chunk.js 24.1 kB 11 [emitted]
12.7bcdf07c7edc3ce0a11d.chunk.js 24.4 kB 12 [emitted]
13.c4e98897ef480410016d.chunk.js 716 bytes 13 [emitted]
main.898cbfbcec44f3cfa4c2.js 1.25 MB 14 [emitted] main
index.html 1.06 kB [emitted]
sw.js 20.6 kB [emitted]
WARNING in ./node_modules/moment/src/lib/locale/locales.js
Module not found: Error: Can't resolve './locale' in '/tmp/build_4cc58fca63d336e918330c92a7320a18/node_modules/moment/src/lib/locale'
# ./node_modules/moment/src/lib/locale/locales.js 56:12-46
# ./node_modules/moment/src/lib/locale/locale.js
# ./node_modules/moment/src/moment.js
# ./app/components/home/cover/calendar/index.js
# ./app/components/home/cover/index.js
# ./app/components/home/index.js
# ./app/containers/HomePage/index.js
# ./app/containers/HomePage/Loadable.js
# ./app/containers/App/index.js
# ./app/app.js
# multi ./app/app.js
Child html-webpack-plugin for "index.html":
1 asset
Child __offline_serviceworker:
1 asset
-----> Caching build
Clearing previous node cache
Saving 2 cacheDirectories (default):
- node_modules
- bower_components (nothing to cache)
-----> Pruning devDependencies
> pre-commit#1.2.2 uninstall node_modules/pre-commit
> node uninstall.js
removed 1620 packages and audited 1114 packages in 19.282s
found 0 vulnerabilities
-----> Build succeeded!
-----> Discovering process types
Procfile declares types -> (none)
Default types for buildpack -> web
-----> Compressing...
Done: 38.8M
-----> Launching...
Released v12
https://myapp-pr-4.herokuapp.com/ deployed to Heroku
logs by code heroku logs --tail --app myapp
2018-06-19T08:33:45.641928+00:00 heroku[web.1]: Idling
2018-06-19T08:33:45.641928+00:00 heroku[web.1]: State changed from up to down
2018-06-19T08:33:46.752542+00:00 heroku[web.1]: Stopping all processes with SIGTERM
2018-06-19T08:33:46.917240+00:00 heroku[web.1]: Process exited with status 143
(i have logs 2018-06-19T08:01:33.875099+00:00 app[web.1] but just '___' is defined but never used)
and in browser myapp show like that
(photo in link)
enter image description here
thank you for your help
if u need more detail , tell me i will show u

I had the same problem and following react-boilerplate instructions made it work for me. Here is the link: https://github.com/react-boilerplate/react-boilerplate/blob/master/docs/general/deployment.md
What it says:
Heroku
Easy 5-Step Deployment Process
Step 1: Create a Procfile with the following line: web: npm run start:prod. We do this because Heroku runs npm run start by default, so we need this setting to override the default run command.
Step 2: Install the Node.js buildpack for your Heroku app by running the following command: heroku buildpacks:set https://github.com/heroku/heroku-buildpack-nodejs#v91 -a [your app name]. Make sure to replace #v91 with whatever the latest buildpack is, which you can find here. https://github.com/heroku/heroku-buildpack-nodejs/releases.
Step 3: Add this line to your package.json file in the scripts area: "heroku-postbuild": "npm run build",. This is so Heroku can build your production assets when deploying (more of which you can read about here). Then, adjust the prebuild script in your package.json file so it looks like this: "prebuild": "npm run build:clean", to avoid having Heroku attempt to run Jest tests (which are unsupported with this buildpack).
Step 4: Run heroku config:set NPM_CONFIG_PRODUCTION=false so that Heroku can compile the NPM modules included in your devDependencies (since many of these packages are required for the build process).
Step 5: Follow the standard Heroku deploy process:
git add .
git commit -m 'Made some epic changes as per usual'
git push heroku master

Related

heroku laravel - vite not found

Any help/guidance thank you in advance.
Today I've set up a Heroku dyno, but can't get the vite command to run.
Laravel 9.29, NodeJS 8.15
Trying to run heroku run npm run dev but returns /tmp/dev-3799b748.sh: 1: vite: not found
I've set the build packs to:
heroku buildpacks
=== manage-demo Buildpack URLs
heroku/nodejs
heroku/php
Also the Config Vars NPM_CONFIG_PRODUCTION = false, YARN_PRODUCTION = false
Commands used to create the Laravel Project:
composer create-project laravel/laravel <myprojectname>
composer require laravel/breeze
php artisan breeze:install react
php artisan migrate
npm install
Deploy Branch
-----> Building on the Heroku-22 stack
-----> Using buildpacks:
1. heroku/nodejs
2. heroku/php
-----> Node.js app detected
-----> Creating runtime environment
NPM_CONFIG_PRODUCTION=false
NPM_CONFIG_LOGLEVEL=error
USE_NPM_INSTALL=true
NODE_VERBOSE=false
NODE_ENV=production
NODE_MODULES_CACHE=true
-----> Installing binaries
engines.node (package.json): unspecified
engines.npm (package.json): unspecified (use default)
Resolving node version 16.x...
Downloading and installing node 16.17.0...
Using default npm version: 8.15.0
-----> Restoring cache
- node_modules (not cached - skipping)
-----> Installing dependencies
Installing node modules (package.json + package-lock)
added 165 packages, and audited 166 packages in 3s
25 packages are looking for funding
run `npm fund` for details
found 0 vulnerabilities
-----> Build
Running build
> build
> vite build
vite v3.1.0 building for production...
transforming...
✓ 254 modules transformed.
rendering chunks...
public/build/manifest.json 3.78 KiB
public/build/assets/ConfirmPassword.6778c5aa.js 1.09 KiB / gzip: 0.61 KiB
public/build/assets/InputLabel.b7560c9a.js 0.20 KiB / gzip: 0.18 KiB
public/build/assets/TextInput.90051331.js 0.63 KiB / gzip: 0.39 KiB
public/build/assets/PrimaryButton.63fa2720.js 0.82 KiB / gzip: 0.49 KiB
public/build/assets/ApplicationLogo.4d214c56.js 3.06 KiB / gzip: 1.30 KiB
public/build/assets/ForgotPassword.863d1afc.js 1.06 KiB / gzip: 0.62 KiB
public/build/assets/Login.ffce380f.js 1.94 KiB / gzip: 0.89 KiB
public/build/assets/Register.13d4ee0d.js 1.95 KiB / gzip: 0.76 KiB
public/build/assets/ResetPassword.467e122e.js 1.57 KiB / gzip: 0.65 KiB
public/build/assets/VerifyEmail.800ac39d.js 1.07 KiB / gzip: 0.61 KiB
public/build/assets/Dashboard.c9f20060.js 17.64 KiB / gzip: 6.24 KiB
public/build/assets/Welcome.875c53e4.js 11.94 KiB / gzip: 3.72 KiB
public/build/assets/app.5c62c80a.css 22.06 KiB / gzip: 4.63 KiB
public/build/assets/app.36a55110.js 315.09 KiB / gzip: 107.01 KiB
-----> Caching build
- node_modules
-----> Pruning devDependencies
Skipping because NPM_CONFIG_PRODUCTION is 'false'
-----> Build succeeded!
-----> PHP app detected
-----> Bootstrapping...
-----> Preparing platform package installation...
-----> Installing platform packages...
- php (8.1.10)
- apache (2.4.54)
- composer (2.4.1)
- nginx (1.22.0)
NOTICE: detected userland polyfill packages for PHP extensions
NOTICE: now attempting to install native extension packages
Installing extensions provided by symfony/polyfill-mbstring:
- ext-mbstring...
Installing extensions provided by symfony/polyfill-ctype:
- ext-ctype...
-----> Installing dependencies...
Composer version 2.4.1 2022-08-20 11:44:50
Installing dependencies from lock file
Verifying lock file contents can be installed on current platform.
Package operations: 70 installs, 0 updates, 0 removals
- Installing doctrine/inflector (2.0.5): Extracting archive
- Installing doctrine/lexer (1.2.3): Extracting archive
- Installing symfony/polyfill-ctype (v1.26.0): Extracting archive
- Installing webmozart/assert (1.11.0): Extracting archive
- Installing dragonmantank/cron-expression (v3.3.2): Extracting archive
- Installing symfony/polyfill-mbstring (v1.26.0): Extracting archive
- Installing symfony/deprecation-contracts (v3.1.1): Extracting archive
- Installing symfony/http-foundation (v6.1.4): Extracting archive
- Installing fruitcake/php-cors (v1.2.0): Extracting archive
- Installing psr/http-message (1.0.1): Extracting archive
- Installing psr/http-client (1.0.1): Extracting archive
- Installing ralouphie/getallheaders (3.0.3): Extracting archive
- Installing psr/http-factory (1.0.1): Extracting archive
- Installing guzzlehttp/psr7 (2.4.1): Extracting archive
- Installing guzzlehttp/promises (1.5.2): Extracting archive
- Installing guzzlehttp/guzzle (7.5.0): Extracting archive
- Installing voku/portable-ascii (2.0.1): Extracting archive
- Installing symfony/polyfill-php80 (v1.26.0): Extracting archive
- Installing phpoption/phpoption (1.9.0): Extracting archive
- Installing graham-campbell/result-type (v1.1.0): Extracting archive
- Installing vlucas/phpdotenv (v5.4.1): Extracting archive
- Installing symfony/css-selector (v6.1.3): Extracting archive
- Installing tijsverkoyen/css-to-inline-styles (2.2.4): Extracting archive
- Installing symfony/var-dumper (v6.1.3): Extracting archive
- Installing symfony/routing (v6.1.3): Extracting archive
- Installing symfony/process (v6.1.3): Extracting archive
- Installing symfony/polyfill-php72 (v1.26.0): Extracting archive
- Installing symfony/polyfill-intl-normalizer (v1.26.0): Extracting archive
- Installing symfony/polyfill-intl-idn (v1.26.0): Extracting archive
- Installing symfony/mime (v6.1.4): Extracting archive
- Installing psr/container (2.0.2): Extracting archive
- Installing symfony/service-contracts (v3.1.1): Extracting archive
- Installing psr/event-dispatcher (1.0.0): Extracting archive
- Installing symfony/event-dispatcher-contracts (v3.1.1): Extracting archive
- Installing symfony/event-dispatcher (v6.1.0): Extracting archive
- Installing psr/log (3.0.0): Extracting archive
- Installing egulias/email-validator (3.2.1): Extracting archive
- Installing symfony/mailer (v6.1.4): Extracting archive
- Installing symfony/error-handler (v6.1.3): Extracting archive
- Installing symfony/http-kernel (v6.1.4): Extracting archive
- Installing symfony/finder (v6.1.3): Extracting archive
- Installing symfony/polyfill-intl-grapheme (v1.26.0): Extracting archive
- Installing symfony/string (v6.1.4): Extracting archive
- Installing symfony/console (v6.1.4): Extracting archive
- Installing symfony/polyfill-php81 (v1.26.0): Extracting archive
- Installing ramsey/collection (1.2.2): Extracting archive
- Installing brick/math (0.10.2): Extracting archive
- Installing ramsey/uuid (4.4.0): Extracting archive
- Installing psr/simple-cache (3.0.0): Extracting archive
- Installing nunomaduro/termwind (v1.14.0): Extracting archive
- Installing symfony/translation-contracts (v3.1.1): Extracting archive
- Installing symfony/translation (v6.1.4): Extracting archive
- Installing nesbot/carbon (2.62.1): Extracting archive
- Installing monolog/monolog (2.8.0): Extracting archive
- Installing league/mime-type-detection (1.11.0): Extracting archive
- Installing league/flysystem (3.3.0): Extracting archive
- Installing nette/utils (v3.2.7): Extracting archive
- Installing nette/schema (v1.2.2): Extracting archive
- Installing dflydev/dot-access-data (v3.0.1): Extracting archive
- Installing league/config (v1.1.1): Extracting archive
- Installing league/commonmark (2.3.5): Extracting archive
- Installing laravel/serializable-closure (v1.2.2): Extracting archive
- Installing laravel/framework (v9.29.0): Extracting archive
- Installing inertiajs/inertia-laravel (v0.6.3): Extracting archive
- Installing laravel/breeze (v1.13.0): Extracting archive
- Installing laravel/sanctum (v2.15.1): Extracting archive
- Installing nikic/php-parser (v4.15.1): Extracting archive
- Installing psy/psysh (v0.11.8): Extracting archive
- Installing laravel/tinker (v2.7.2): Extracting archive
- Installing tightenco/ziggy (v1.4.6): Extracting archive
Generating optimized autoload files
> Illuminate\Foundation\ComposerScripts::postAutoloadDump
> #php artisan package:discover --ansi
INFO Discovering packages.
inertiajs/inertia-laravel ............................................. DONE
laravel/breeze ........................................................ DONE
laravel/sanctum ....................................................... DONE
laravel/tinker ........................................................ DONE
nesbot/carbon ......................................................... DONE
nunomaduro/termwind ................................................... DONE
tightenco/ziggy ....................................................... DONE
49 packages you are using are looking for funding.
Use the `composer fund` command to find out more!
-----> Preparing runtime environment...
-----> Checking for additional extensions to install...
-----> Discovering process types
Procfile declares types -> web
-----> Compressing...
Done: 66M
-----> Launching...
Released v29
https://manage-demo.herokuapp.com/ deployed to Heroku
Starting November 28th, 2022, free Heroku Dynos, free Heroku Postgres, and free Heroku Data for Redis® will no longer be available.
If you have apps using any of these resources, you must upgrade to paid plans by this date to ensure your apps continue to run and to retain your data. For students, we will announce a new program by the end of September. Learn more at https://blog.heroku.com/next-chapter
heroku run npm run dev
npm WARN config production Use `--omit=dev` instead.
> dev
> vite
VITE v3.1.0 ready in 507 ms
➜ Local: http://localhost:5173/
➜ Network: use --host to expose
[..................] | : timing config:load:flatten Completed in 2ms
LARAVEL v9.29.0 plugin v0.6.0
➜ APP_URL: https://manage-demo.herokuapp.com/
node:internal/errors:477 timing config:load:flatten Completed in 2ms
ErrorCaptureStackTrace(err);
^
Error: ENOSPC: System limit for number of file watchers reached, watch '/app/.heroku/node/include/node/openssl/archs/linux-x86_64/asm/include/progs.h'
at FSWatcher.<computed> (node:internal/fs/watchers:244:19)
at Object.watch (node:fs:2301:34)
at createFsWatchInstance (file:///app/node_modules/vite/dist/node/chunks/dep-665b0112.js:49738:17)
at setFsWatchListener (file:///app/node_modules/vite/dist/node/chunks/dep-665b0112.js:49785:15)
at NodeFsHandler$1._watchWithNodeFs (file:///app/node_modules/vite/dist/node/chunks/dep-665b0112.js:49940:14)
at NodeFsHandler$1._handleFile (file:///app/node_modules/vite/dist/node/chunks/dep-665b0112.js:50004:23)
at NodeFsHandler$1._addToNodeFs (file:///app/node_modules/vite/dist/node/chunks/dep-665b0112.js:50246:21)
Emitted 'error' event on FSWatcher instance at:
at FSWatcher._handleError (file:///app/node_modules/vite/dist/node/chunks/dep-665b0112.js:51434:10)
at NodeFsHandler$1._addToNodeFs (file:///app/node_modules/vite/dist/node/chunks/dep-665b0112.js:50254:18) {
errno: -28,
syscall: 'watch',
code: 'ENOSPC',
path: '/app/.heroku/node/include/node/openssl/archs/linux-x86_64/asm/include/progs.h',
filename: '/app/.heroku/node/include/node/openssl/archs/linux-x86_64/asm/include/progs.h'
}

NPM RUN DEV Freezing

I am trying to install laravel and breeze. Everything goes fine up to npm install. But when I run npm dev it freezes and nothing else happens. Below is what it says when it stops:
VITE v3.0.9 ready in 1434 ms
➜ Local: http://127.0.0.1:5176/
➜ Network: use --host to expose
LARAVEL v9.25.1 plugin v0.5.4
➜ APP_URL: http://localhost
Please! How do I resolve this?
UPDATE:
After running npm build, npm run dev still freezes. Below is the code.
npm run build
> build
> vite build
vite v3.0.9 building for production...
✓ 119 modules transformed.
public/build/manifest.json 0.25 KiB
public/build/assets/app.c090eeea.css 186.93 KiB / gzip: 26.55 KiB
public/build/assets/app.aac2dc08.js 170.64 KiB / gzip: 57.15 KiB
amand#Amanda MINGW64 /c/laragon/www/patinoire
$ npm run dev
> dev
> vite
Port 5173 is in use, trying another one...
Port 5174 is in use, trying another one...
VITE v3.0.9 ready in 1043 ms
➜ Local: http://127.0.0.1:5175/
➜ Network: use --host to expose
LARAVEL v9.25.1 plugin v0.5.4
➜ APP_URL: http://localhost
try
npm run build
npm run dev
i think it will work
Follow these steps
Download Node.js installer from https://nodejs.org/en/download/
Install Node.js and NPM

Heroku APT file is not used in the Pipeline

I'm using Apt file in Heroku to have graphicmagic package available in Dyno for years.
Now I wanted to set up Heroku Pipeline tests, but the Heroku does not install apt packages in the build for tests at all. So tests using the graphicmagic are failing.
Is there any way to install the apt packages in the build for Heroku Pipeline tests?
Build logs are here:
Application build log (installing Apt packages at the end)
-----> Building on the Heroku-20 stack
-----> Using buildpacks:
1. heroku/nodejs
2. https://github.com/heroku/heroku-buildpack-apt
-----> Node.js app detected
-----> Creating runtime environment
NPM_CONFIG_LOGLEVEL=error
NODE_VERBOSE=false
NODE_ENV=test
NODE_MODULES_CACHE=true
-----> Installing binaries
engines.node (package.json): 10.23.*
engines.npm (package.json): 6.14.8
Resolving node version 10.23.*...
Downloading and installing node 10.23.3...
Bootstrapping npm 6.14.8 (replacing 6.14.11)...
npm 6.14.8 installed
-----> Restoring cache
- node_modules
-----> Installing dependencies
Installing node modules
> PayJsRouter#1.40.0 preinstall /tmp/build_6e87a3cd
> npx npm-force-resolutions
npx: installed 6 in 2.301s
> core-js#2.6.11 postinstall /tmp/build_6e87a3cd/node_modules/core-js
> node -e "try{require('./postinstall')}catch(e){}"
> protobufjs#6.10.1 postinstall /tmp/build_6e87a3cd/node_modules/protobufjs
> node scripts/postinstall
> fsevents#1.2.13 install /tmp/build_6e87a3cd/node_modules/babel/node_modules/fsevents
> node install.js
Skipping 'fsevents' build as platform linux is not supported
> fsevents#1.2.13 install /tmp/build_6e87a3cd/node_modules/steal-tools/node_modules/fsevents
> node install.js
Skipping 'fsevents' build as platform linux is not supported
> fsevents#1.2.13 install /tmp/build_6e87a3cd/node_modules/nodemon/node_modules/fsevents
> node install.js
Skipping 'fsevents' build as platform linux is not supported
> nodemon#1.19.4 postinstall /tmp/build_6e87a3cd/node_modules/nodemon
> node bin/postinstall || exit 0
Love nodemon? You can now support the project via the open collective:
> https://opencollective.com/nodemon/donate
> PayJsRouter#1.40.0 postinstall /tmp/build_6e87a3cd
> npm run build-steal && npm run build-lodash && npm run build-prepare
> PayJsRouter#1.40.0 build-steal /tmp/build_6e87a3cd
> node ./scripts/buildSteal
> PayJsRouter#1.40.0 build-lodash /tmp/build_6e87a3cd
> node ./node_modules/lodash-cli/bin/lodash compat exports=umd modularize --development --output node_modules/lodash/
Created 420 modules in 13.616 seconds.
> PayJsRouter#1.40.0 build-prepare /tmp/build_6e87a3cd
> mkdir -p ./public/dist/templates
added 1681 packages in 66.104s
-----> Build
Running build
> PayJsRouter#1.40.0 build /tmp/build_6e87a3cd
> grunt steal-build
... MANY LINES OF BUILD OUTPUT
Build was successful.
Done.
-----> Caching build
- node_modules
-----> Pruning devDependencies
Skipping because NODE_ENV is 'test'
-----> Cleanup
Running heroku-cleanup
> PayJsRouter#1.40.0 heroku-cleanup /tmp/build_6e87a3cd
> npm prune --production
added 458 packages from 863 contributors, removed 1041 packages and audited 643 packages in 28.358s
38 packages are looking for funding
run `npm fund` for details
found 44 vulnerabilities (13 low, 11 moderate, 19 high, 1 critical)
run `npm audit fix` to fix them, or `npm audit` for details
-----> Build succeeded!
-----> Apt app detected
-----> Reusing cache
-----> Updating apt caches
Get:1 http://apt.postgresql.org/pub/repos/apt focal-pgdg InRelease [81.6 kB]
Hit:2 http://archive.ubuntu.com/ubuntu focal InRelease
Get:3 http://archive.ubuntu.com/ubuntu focal-security InRelease [109 kB]
Get:4 http://apt.postgresql.org/pub/repos/apt focal-pgdg/main amd64 Packages [310 kB]
Get:5 http://archive.ubuntu.com/ubuntu focal-updates InRelease [114 kB]
Get:6 http://archive.ubuntu.com/ubuntu focal-security/main amd64 Packages [778 kB]
Get:7 http://archive.ubuntu.com/ubuntu focal-security/universe amd64 Packages [684 kB]
Get:8 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages [1,194 kB]
Get:9 http://archive.ubuntu.com/ubuntu focal-updates/universe amd64 Packages [952 kB]
Fetched 4,222 kB in 1s (3,431 kB/s)
Reading package lists...
-----> Fetching .debs for graphicsmagick
Reading package lists...
Building dependency tree...
The following additional packages will be installed:
libgraphicsmagick-q16-3
Suggested packages:
graphicsmagick-dbg
The following NEW packages will be installed:
graphicsmagick libgraphicsmagick-q16-3
0 upgraded, 2 newly installed, 0 to remove and 20 not upgraded.
Need to get 0 B/1,794 kB of archives.
After this operation, 8,566 kB of additional disk space will be used.
Download complete and in download only mode
-----> Fetching .debs for libpng-dev
Reading package lists...
Building dependency tree...
0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 20 not upgraded.
Need to get 0 B/175 kB of archives.
After this operation, 0 B of additional disk space will be used.
Download complete and in download only mode
-----> Fetching .debs for zlib1g-dev
Reading package lists...
Building dependency tree...
0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 20 not upgraded.
Need to get 0 B/155 kB of archives.
After this operation, 0 B of additional disk space will be used.
Download complete and in download only mode
-----> Installing graphicsmagick_1.4+really1.3.35-1_amd64.deb
-----> Installing libgraphicsmagick-q16-3_1.4+really1.3.35-1_amd64.deb
-----> Installing libpng-dev_1.6.37-2_amd64.deb
-----> Installing zlib1g-dev_1%3a1.2.11.dfsg-2ubuntu1.2_amd64.deb
-----> Writing profile script
-----> Rewrite package-config files
-----> Discovering process types
Procfile declares types -> web, worker
-----> Compressing...
Done: 82.1M
-----> Launching...
Released v823
https://xyz.herokuapp.com/ deployed to Heroku
Pipeline test build log (installing Apt packages is not present)
-----> Building on the Heroku-20 stack
-----> Auto detecting buildpacks...
buildpack detected
-----> Node.js app detected
-----> Creating runtime environment
NPM_CONFIG_PRODUCTION=false
NPM_CONFIG_LOGLEVEL=error
NODE_VERBOSE=false
NODE_ENV=testing
NODE_MODULES_CACHE=true
-----> Installing binaries
engines.node (package.json): 10.23.*
engines.npm (package.json): 6.14.8
Resolving node version 10.23.*...
Downloading and installing node 10.23.3...
Bootstrapping npm 6.14.8 (replacing 6.14.11)...
npm 6.14.8 installed
-----> Restoring cache
- node_modules
-----> Installing dependencies
Installing node modules
.
> PayJsRouter#1.40.0 preinstall /app
> npx npm-force-resolutions
npx: installed 6 in 2.844s
> core-js#2.6.11 postinstall /app/node_modules/core-js
> node -e "try{require('./postinstall')}catch(e){}"
> protobufjs#6.10.1 postinstall /app/node_modules/protobufjs
> node scripts/postinstall
> fsevents#1.2.13 install /app/node_modules/babel/node_modules/fsevents
> node install.js
Skipping 'fsevents' build as platform linux is not supported
> fsevents#1.2.13 install /app/node_modules/steal-tools/node_modules/fsevents
> node install.js
Skipping 'fsevents' build as platform linux is not supported
> fsevents#1.2.13 install /app/node_modules/nodemon/node_modules/fsevents
> node install.js
Skipping 'fsevents' build as platform linux is not supported
> nodemon#1.19.4 postinstall /app/node_modules/nodemon
> node bin/postinstall || exit 0
Love nodemon? You can now support the project via the open collective:
> https://opencollective.com/nodemon/donate
> PayJsRouter#1.40.0 postinstall /app
> npm run build-steal && npm run build-lodash && npm run build-prepare
> PayJsRouter#1.40.0 build-steal /app
> node ./scripts/buildSteal
> PayJsRouter#1.40.0 build-lodash /app
> node ./node_modules/lodash-cli/bin/lodash compat exports=umd modularize --development --output node_modules/lodash/
Created 420 modules in 17.29 seconds.
> PayJsRouter#1.40.0 build-prepare /app
> mkdir -p ./public/dist/templates
added 1738 packages in 85.344s
-----> Build
Running build
> PayJsRouter#1.40.0 build /app
> grunt steal-build
... MANY LINES OF BUILD OUTPUT
Build was successful.
Done.
-----> Caching build
- node_modules
-----> Pruning devDependencies
Skipping because NODE_ENV is not 'production'
-----> Build succeeded!
-----> No test-setup command provided. Skipping.
It is autodetecting. Your Apt buildpack is not recognized:
-----> Auto detecting buildpacks...
buildpack detected
-----> Node.js app detected
For your application setting the buildpack with heroku buildpacks:set is sufficient.
For the pipeline you need an app.json with your buildpacks:
{
"buildpacks": [
{
"url": "heroku/nodejs"
},
{
"url": "https://github.com/heroku/heroku-buildpack-apt"
}
]
}
Ressources to read:
https://devcenter.heroku.com/articles/heroku-ci and https://devcenter.heroku.com/articles/app-json-schema#buildpacks

After deploying getting internal server error on heroku

Build successfully but still getting internal server error.
Please help to fix this, build message is given below:-
-----> Node.js app detected
-----> Creating runtime environment
NPM_CONFIG_LOGLEVEL=error
NODE_VERBOSE=false
NODE_ENV=production
NODE_MODULES_CACHE=true
-----> Installing binaries
engines.node (package.json): 10.6.0
engines.npm (package.json): unspecified (use default)
Resolving node version 10.6.0...
Downloading and installing node 10.6.0...
Using default npm version: 6.1.0
-----> Restoring cache
Loading 2 from cacheDirectories (default):
- node_modules
- bower_components (not cached - skipping)
-----> Building dependencies
Installing node modules (package.json + package-lock)
audited 492 packages in 2.222s
found 0 vulnerabilities -----> Caching build
Clearing previous node cache
Saving 2 cacheDirectories (default):
- node_modules
- bower_components (nothing to cache)
-----> Pruning devDependencies
removed 66 packages and audited 355 packages in 2.11s
found 0 vulnerabilities
-----> Build succeeded!
-----> Discovering process types
Procfile declares types -> (none)
Default types for buildpack -> web
-----> Compressing...
Done: 22.6M
-----> Launching...
Released v14
https://young-forest-74580.herokuapp.com/ deployed to Heroku

Webpack modules building error: The process cannot access the file because it is being used by another process

I am deploying on heroku instance. One of the step uses webpack and fails during modules building. Is it possible to get more details other than next general error? Using --display-error-details doesn't help.
One or more errors occurred. (The process cannot access the file because it is being used by another process.)
remote: webpack --progress --display-error-details
remote: isDashboardMode? false
remote: isDevBuild? true
remote: Hash: da11b9b5f7b728252ffdd4bc0b7fbe62e7a1cee2
remote: Version: webpack 2.2.1
remote: Child
remote: Hash: da11b9b5f7b728252ffd
remote: Time: 29398ms
remote: Asset Size Chunks Chunk Names
remote: 0.js 7.13 kB 0 [emitted]
remote: main-client.js 1.97 MB 1 [emitted] [big] main-client
remote: 0.js.map 6.5 kB 0 [emitted]
remote: main-client.js.map 2.24 MB 1 [emitted] main-client
remote: Child
remote: Hash: d4bc0b7fbe62e7a1cee2
remote: Time: 22022ms
remote: Asset Size Chunks Chunk Names
remote: 0.js 15.9 kB 0 [emitted]
remote: main-server.js 5.13 MB 1 [emitted] [big] main-server
remote: aspnetcore-angular2-universal-starter#1.0.0-beta.6 /tmp/tmp.ypY0oo0Amq
remote: ├── UNMET PEER DEPENDENCY #angular/compiler#2.4.5
remote: ├── UNMET PEER DEPENDENCY #angular/core#2.4.5
remote: ├─┬ angular2-universal-polyfills#2.1.0-rc.1
remote: │ ├── es6-promise#3.0.2
remote: │ └── reflect-metadata#0.1.2
remote: └── UNMET PEER DEPENDENCY zone.js#0.7.2
remote: 17% [0] building modules 80/204 modules 124 active ...js/mo
One or more errors occurred.
(The process cannot access the file because it is being used by another process.)

Resources