Meteor on Heroku not working

Meteor on Heroku not working - meteor

I create a simple Meteor app:
meteor create test-meteor-app
cd test-meteor-app
meteor
meteor starts
Then I create a Heroku server.
git init
heroku git:remote -a remote-test-meteor-app
git add .
git commit -am "make it better"
git push heroku master
And I get:
2016-09-11T17:22:59.978392+00:00 heroku[slug-compiler]: Slug compilation started
2016-09-11T17:22:59.978397+00:00 heroku[slug-compiler]: Slug compilation finished
2016-09-11T17:23:00.336281+00:00 heroku[web.1]: State changed from crashed to starting
2016-09-11T17:23:01.911710+00:00 heroku[web.1]: Starting process with command `npm start`
2016-09-11T17:23:04.001360+00:00 heroku[web.1]: Process exited with status 1
2016-09-11T17:23:04.014649+00:00 heroku[web.1]: State changed from starting to crashed
2016-09-11T17:23:04.015767+00:00 heroku[web.1]: State changed from crashed to starting
2016-09-11T17:23:03.941425+00:00 app[web.1]:
2016-09-11T17:23:03.941445+00:00 app[web.1]: > meteor run
2016-09-11T17:23:03.941445+00:00 app[web.1]:
2016-09-11T17:23:03.946773+00:00 app[web.1]: sh: 1: meteor: not found
2016-09-11T17:23:03.957464+00:00 app[web.1]: npm ERR! Linux 3.13.0-93-generic
2016-09-11T17:23:03.957967+00:00 app[web.1]: npm ERR! node v5.11.1
2016-09-11T17:23:03.958306+00:00 app[web.1]: npm ERR! npm v3.8.6
2016-09-11T17:23:03.959375+00:00 app[web.1]: npm ERR! syscall spawn
2016-09-11T17:23:03.959909+00:00 app[web.1]: npm ERR! Failed at the test-meteor-app# start script 'meteor run'.
2016-09-11T17:23:03.960274+00:00 app[web.1]: npm ERR! not with npm itself.
2016-09-11T17:23:03.960395+00:00 app[web.1]: npm ERR! Tell the author that this fails on your system:
2016-09-11T17:23:03.960517+00:00 app[web.1]: npm ERR! meteor run
2016-09-11T17:23:03.960618+00:00 app[web.1]: npm ERR! You can get information on how to open an issue for this project with:
2016-09-11T17:23:03.960743+00:00 app[web.1]: npm ERR! npm bugs test-meteor-app
2016-09-11T17:23:03.960864+00:00 app[web.1]: npm ERR! Or if that isn't available, you can get their info via:
2016-09-11T17:23:03.961118+00:00 app[web.1]: npm ERR! npm owner ls test-meteor-app
2016-09-11T17:23:03.961242+00:00 app[web.1]: npm ERR! There is likely additional logging output above.
2016-09-11T17:23:03.964862+00:00 app[web.1]: npm ERR! Please include the following file with any support request:
2016-09-11T17:23:05.446417+00:00 heroku[web.1]: Starting process with command `npm start`
2016-09-11T17:23:07.415275+00:00 heroku[web.1]: Process exited with status 1
2016-09-11T17:23:07.447458+00:00 heroku[web.1]: State changed from starting to crashed
2016-09-11T17:23:07.323157+00:00 app[web.1]:
2016-09-11T17:23:07.323177+00:00 app[web.1]: > meteor run
2016-09-11T17:23:07.323177+00:00 app[web.1]:
2016-09-11T17:23:07.328685+00:00 app[web.1]: sh: 1: meteor: not found
2016-09-11T17:23:07.333342+00:00 app[web.1]:
2016-09-11T17:23:07.340269+00:00 app[web.1]: npm ERR! Linux 3.13.0-93-generic
2016-09-11T17:23:07.340769+00:00 app[web.1]: npm ERR! node v5.11.1
2016-09-11T17:23:07.341215+00:00 app[web.1]: npm ERR! npm v3.8.6
2016-09-11T17:23:07.341469+00:00 app[web.1]: npm ERR! file sh
2016-09-11T17:23:07.341799+00:00 app[web.1]: npm ERR! errno ENOENT
2016-09-11T17:23:07.342058+00:00 app[web.1]: npm ERR! test-meteor-app# start: `meteor run`
2016-09-11T17:23:07.342157+00:00 app[web.1]: npm ERR! spawn ENOENT
2016-09-11T17:23:07.342292+00:00 app[web.1]: npm ERR!
2016-09-11T17:23:07.342424+00:00 app[web.1]: npm ERR! Failed at the test-meteor-app# start script 'meteor run'.
2016-09-11T17:23:07.342651+00:00 app[web.1]: npm ERR! If you do, this is most likely a problem with the test-meteor-app package,
2016-09-11T17:23:07.342758+00:00 app[web.1]: npm ERR! not with npm itself.
2016-09-11T17:23:07.342853+00:00 app[web.1]: npm ERR! Tell the author that this fails on your system:
2016-09-11T17:23:07.343072+00:00 app[web.1]: npm ERR! You can get information on how to open an issue for this project with:
2016-09-11T17:23:07.343180+00:00 app[web.1]: npm ERR! npm bugs test-meteor-app
2016-09-11T17:23:07.343300+00:00 app[web.1]: npm ERR! Or if that isn't available, you can get their info via:
2016-09-11T17:23:07.343707+00:00 app[web.1]: npm ERR! There is likely additional logging output above.
2016-09-11T17:23:07.346956+00:00 app[web.1]:
2016-09-11T17:23:07.347262+00:00 app[web.1]: npm ERR! /app/npm-debug.log
Then I try access the remote app via a browser and get a 503:
remote-test-meteor-app.herokuapp.com
2016-09-11T17:26:19.347339+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=remote-test-meteor-app.herokuapp.com request_id=c3ad6369-00f9-4b16-98b8-ec5bb5a6605b fwd="105.186.215.147" dyno= connect= service= status=503 bytes=
2016-09-11T17:26:21.133873+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/favicon.ico" host=remote-test-meteor-app.herokuapp.com request_id=ec8e8ea9-af47-4cf8-9aac-1c897b4b4e70 fwd="105.186.215.147" dyno= connect= service= status=503 bytes=
2016-09-11T17:26:21.436871+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/favicon.ico" host=remote-test-meteor-app.herokuapp.com request_id=81d5cd8e-4164-4588-84fc-b0ffbcde51ad fwd="105.186.215.147" dyno= connect= service= status=503 bytes=
Any ideas appreciated please?
UPDATE
package.json
{
"name": "test-meteor-app",
"private": true,
"scripts": {
"start": "meteor run"
},
"dependencies": {
"meteor-node-stubs": "~0.2.0"
}
}

You should try using the Meteor buildpack, which includes all of the system dependencies a Meteor application needs to run (node, the meteor binary, etc.).
heroku buildpacks:set https://github.com/jordansissel/heroku-buildpack-meteor.git
See this blog post for a detailed tutorial.

The same problem. Here is the solution. You can either restart the heroku repository using heroku run meteor restart or you can reinstall the app using the steps described here : https://medium.com/#leonardykris/how-to-run-a-meteor-js-application-on-heroku-in-10-steps-7aceb12de234 .
I reinstalled the app and it works

Related

grunt dependencies "while found" & cannot resolve

I'm a junior programmer and I got a mission to run old code on my computer.
When I try to do npm install in the project folder I get these errors:
npm WARN config global `--global`, `--local` are deprecated. Use `--location=global` instead.
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR!
npm ERR! While resolving: grunt-mocha-istanbul#3.0.1
npm ERR! Found: grunt#1.5.3
npm ERR! node_modules/grunt
npm ERR! dev grunt#"^1.0.1" from the root project
npm ERR! peer grunt#">=0.4.0" from grunt-concurrent#2.3.1
npm ERR! node_modules/grunt-concurrent
npm ERR! dev grunt-concurrent#"^2.0.0" from the root project
npm ERR! 8 more (grunt-contrib-connect, grunt-contrib-jshint, ...)
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer grunt#"0.4.x" from grunt-mocha-istanbul#3.0.1
npm ERR! node_modules/grunt-mocha-istanbul
npm ERR! dev grunt-mocha-istanbul#"^3.0.1" from the root project
npm ERR!
npm ERR! Conflicting peer dependency: grunt#0.4.5
npm ERR! node_modules/grunt
npm ERR! peer grunt#"0.4.x" from grunt-mocha-istanbul#3.0.1
npm ERR! node_modules/grunt-mocha-istanbul
npm ERR! dev grunt-mocha-istanbul#"^3.0.1" from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!
npm ERR! See C:\Users\dotan\AppData\Local\npm-cache\eresolve-report.txt for a full report.
npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\dotan\AppData\Local\npm-cache\_logs\2022-08-14T06_34_16_477Z-debug-0.log
In addition when I'm using administrator cmd and run grunt --version I get: grunt-cli v1.4.0
and when I run npm i grunt from admin cmd I get (on my windows 11):
C:\Windows\system32>npm i grunt
npm WARN config global `--global`, `--local` are deprecated. Use `--location=global` instead.
npm ERR! code EPERM
npm ERR! syscall mkdir
npm ERR! path C:\
npm ERR! errno -4048
npm ERR! Error: EPERM: operation not permitted, mkdir 'C:\'
npm ERR! [Error: EPERM: operation not permitted, mkdir 'C:\'] {
npm ERR! errno: -4048,
npm ERR! code: 'EPERM',
npm ERR! syscall: 'mkdir',
npm ERR! path: 'C:\\'
npm ERR! }
npm ERR!
npm ERR! The operation was rejected by your operating system.
npm ERR! It's possible that the file was already in use (by a text editor or antivirus),
npm ERR! or that you lack permissions to access it.
npm ERR!
npm ERR! If you believe this might be a permissions issue, please double-check the
npm ERR! permissions of the file and its containing directories, or try running
npm ERR! the command again as root/Administrator.
npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\dotan\AppData\Local\npm-cache\_logs\2022-08-14T06_57_44_173Z-debug-0.log
and when using the same command (npm i grunt) in the terminal in the project folder I get:
PS C:\Users\dotan\Desktop\ECO-OS\ecoos> npm i grunt
npm WARN config global `--global`, `--local` are deprecated. Use `--location=global` instead.
npm WARN idealTree Removing dependencies.grunt in favor of devDependencies.grunt
npm WARN ERESOLVE overriding peer dependency
npm WARN While resolving: ecoos#0.4.2
npm WARN Found: grunt#1.5.3
npm WARN node_modules/grunt
npm WARN peer grunt#">=0.4.0" from grunt-concurrent#2.3.1
npm WARN node_modules/grunt-concurrent
npm WARN dev grunt-concurrent#"^2.0.0" from the root project
npm WARN 9 more (grunt-contrib-connect, grunt-contrib-jshint, ...)
npm WARN
npm WARN Could not resolve dependency:
npm WARN peer grunt#"0.4.x" from grunt-mocha-istanbul#3.0.1
npm WARN node_modules/grunt-mocha-istanbul
npm WARN dev grunt-mocha-istanbul#"^3.0.1" from the root project
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: 'grunt-istanbul#0.6.2',
npm WARN EBADENGINE required: { node: '~0.12.0' },
npm WARN EBADENGINE current: { node: 'v16.16.0', npm: '8.11.0' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: 'karma#0.13.22',
npm WARN EBADENGINE required: { node: '0.10 || 0.12 || 4 || 5' },
npm WARN EBADENGINE current: { node: 'v16.16.0', npm: '8.11.0' }
npm WARN EBADENGINE }
npm WARN deprecated angular-aria#1.8.3: For the actively supported Angular, see https://www.npmjs.com/package/#angular/core. AngularJS support has officially ended. For extended AngularJS support options, see https://goo.gle/angularjs-path-forward.
npm WARN deprecated angular-animate#1.8.3: For the actively supported Angular, see https://www.npmjs.com/package/#angular/core. AngularJS support has officially ended. For extended AngularJS support options, see https://goo.gle/angularjs-path-forward.
npm WARN deprecated angular#1.8.3: For the actively supported Angular, see https://www.npmjs.com/package/#angular/core. AngularJS support has officially ended. For extended AngularJS support options, see https://goo.gle/angularjs-path-forward.
[##################] / reify:node-inspector: timing metavuln:calculate:security-advisory:socket
npm ERR! code 1
npm ERR! path C:\Users\dotan\Desktop\ECO-OS\ecoos\node_modules\v8-debug:security-advisory:socket
npm ERR! command failed
npm ERR! command C:\Windows\system32\cmd.exe /d /s /c node-pre-gyp install --fallback-to-build
npm ERR! Failed to execute 'C:\Program Files\nodejs\node.exe C:\Users\dotan\AppData\Roaming\nvm\v16.16.0\node_modules\npm\node_modules\node-gyp\bin\node-gyp.js configure --fallback-to-build --module=C:\Users\dotan\Desktop\ECO-OS\ecoos\node_modules\v8-debug\build\debug\v0.7.7\node-v93-win32-x64\debug.node --module_name=debug --module_path=C:\Users\dotan\Desktop\ECO-OS\ecoos\node_modules\v8-debug\build\debug\v0.7.7\node-v93-win32-x64' (1)
npm ERR! node-pre-gyp info it worked if it ends with ok
npm ERR! node-pre-gyp info using node-pre-gyp#0.6.39
npm ERR! node-pre-gyp info using node#16.16.0 | win32 | x64
npm ERR! node-pre-gyp info check checked for "C:\Users\dotan\Desktop\ECO-OS\ecoos\node_modules\v8-debug\build\debug\v0.7.7\node-v93-win32-x64\debug.node" (not found)
npm ERR! node-pre-gyp http GET https://node-inspector.s3.amazonaws.com/debug/v0.7.7/node-v93-win32-x64.tar.gz
npm ERR! node-pre-gyp http 404 https://node-inspector.s3.amazonaws.com/debug/v0.7.7/node-v93-win32-x64.tar.gz
npm ERR! node-pre-gyp ERR! Tried to download(404): https://node-inspector.s3.amazonaws.com/debug/v0.7.7/node-v93-win32-x64.tar.gz
npm ERR! node-pre-gyp ERR! Pre-built binaries not found for v8-debug#0.7.7 and node#16.16.0 (node-v93 ABI, unknown) (falling back to source compile with node-gyp)
npm ERR! node-pre-gyp http 404 status code downloading tarball https://node-inspector.s3.amazonaws.com/debug/v0.7.7/node-v93-win32-x64.tar.gz
npm ERR! node-pre-gyp ERR! Tried to download(undefined): https://node-inspector.s3.amazonaws.com/debug/v0.7.7/node-v93-win32-x64.tar.gz
npm ERR! node-pre-gyp ERR! Pre-built binaries not found for v8-debug#0.7.7 and node#16.16.0 (node-v93 ABI, unknown) (falling back to source compile with node-gyp)
npm ERR! node-pre-gyp http Connection closed while downloading tarball file
npm ERR! gyp info it worked if it ends with ok
npm ERR! gyp info using node-gyp#9.0.0
npm ERR! gyp info using node#16.16.0 | win32 | x64
npm ERR! gyp info it worked if it ends with ok
npm ERR! gyp info using node-gyp#9.0.0
npm ERR! gyp info using node#16.16.0 | win32 | x64
npm ERR! gyp info ok
npm ERR! gyp info ok
npm ERR! gyp info it worked if it ends with ok
npm ERR! gyp info using node-gyp#9.0.0
npm ERR! gyp info using node#16.16.0 | win32 | x64
npm ERR! gyp info it worked if it ends with ok
npm ERR! gyp info using node-gyp#9.0.0
npm ERR! gyp info using node#16.16.0 | win32 | x64
npm ERR! gyp info find Python using Python version 3.10.6 found at "C:\Python310\python.exe"
npm ERR! gyp info find Python using Python version 3.10.6 found at "C:\Python310\python.exe"
npm ERR! gyp info find VS using VS2022 (17.3.32804.467) found at:
npm ERR! gyp info find VS "C:\Program Files\Microsoft Visual Studio\2022\Community"
npm ERR! gyp info find VS run with --verbose for detailed information
npm ERR! gyp info find VS using VS2022 (17.3.32804.467) found at:
npm ERR! gyp info find VS "C:\Program Files\Microsoft Visual Studio\2022\Community"
npm ERR! gyp info find VS run with --verbose for detailed information
npm ERR! gyp info spawn C:\Python310\python.exe
npm ERR! gyp info spawn args [
npm ERR! gyp info spawn args 'C:\\Users\\dotan\\AppData\\Roaming\\nvm\\v16.16.0\\node_modules\\npm\\node_modules\\node-gyp\\gyp\\gyp_main.py',
npm ERR! gyp info spawn args 'binding.gyp',
npm ERR! gyp info spawn args '-f',
npm ERR! gyp info spawn args 'msvs',
npm ERR! gyp info spawn args '-I',
npm ERR! gyp info spawn args 'C:\\Users\\dotan\\Desktop\\ECO-OS\\ecoos\\node_modules\\v8-debug\\build\\config.gypi',
npm ERR! gyp info spawn args '-I',
npm ERR! gyp info spawn args 'C:\\Users\\dotan\\AppData\\Roaming\\nvm\\v16.16.0\\node_modules\\npm\\node_modules\\node-gyp\\addon.gypi',
npm ERR! gyp info spawn args '-I',
npm ERR! gyp info spawn args 'C:\\Users\\dotan\\AppData\\Local\\node-gyp\\Cache\\16.16.0\\include\\node\\common.gypi',
npm ERR! gyp info spawn args '-Dlibrary=shared_library',
npm ERR! gyp info spawn args '-Dvisibility=default',
npm ERR! gyp info spawn args '-Dnode_root_dir=C:\\Users\\dotan\\AppData\\Local\\node-gyp\\Cache\\16.16.0',
npm ERR! gyp info spawn args '-Dnode_gyp_dir=C:\\Users\\dotan\\AppData\\Roaming\\nvm\\v16.16.0\\node_modules\\npm\\node_modules\\node-gyp',
npm ERR! gyp info spawn args '-Dnode_lib_file=C:\\\\Users\\\\dotan\\\\AppData\\\\Local\\\\node-gyp\\\\Cache\\\\16.16.0\\\\<(target_arch)\\\\node.lib',
npm ERR! gyp info spawn args '-Dmodule_root_dir=C:\\Users\\dotan\\Desktop\\ECO-OS\\ecoos\\node_modules\\v8-debug',
npm ERR! gyp info spawn args '-Dnode_engine=v8',
npm ERR! gyp info spawn args '--depth=.',
npm ERR! gyp info spawn args '--no-parallel',
npm ERR! gyp info spawn args '--generator-output',
npm ERR! gyp info spawn args 'C:\\Users\\dotan\\Desktop\\ECO-OS\\ecoos\\node_modules\\v8-debug\\build',
npm ERR! gyp info spawn args '-Goutput_dir=.'
npm ERR! gyp info spawn args ]
npm ERR! gyp info spawn C:\Python310\python.exe
npm ERR! gyp info spawn args [
npm ERR! gyp info spawn args 'C:\\Users\\dotan\\AppData\\Roaming\\nvm\\v16.16.0\\node_modules\\npm\\node_modules\\node-gyp\\gyp\\gyp_main.py',
npm ERR! gyp info spawn args 'binding.gyp',
npm ERR! gyp info spawn args '-f',
npm ERR! gyp info spawn args 'msvs',
npm ERR! gyp info spawn args '-I',
npm ERR! gyp info spawn args 'C:\\Users\\dotan\\Desktop\\ECO-OS\\ecoos\\node_modules\\v8-debug\\build\\config.gypi',
npm ERR! gyp info spawn args '-I',
npm ERR! gyp info spawn args 'C:\\Users\\dotan\\AppData\\Roaming\\nvm\\v16.16.0\\node_modules\\npm\\node_modules\\node-gyp\\addon.gypi',
npm ERR! gyp info spawn args '-I',
npm ERR! gyp info spawn args 'C:\\Users\\dotan\\AppData\\Local\\node-gyp\\Cache\\16.16.0\\include\\node\\common.gypi',
npm ERR! gyp info spawn args '-Dlibrary=shared_library',
npm ERR! gyp info spawn args '-Dvisibility=default',
npm ERR! gyp info spawn args '-Dnode_root_dir=C:\\Users\\dotan\\AppData\\Local\\node-gyp\\Cache\\16.16.0',
npm ERR! gyp info spawn args '-Dnode_gyp_dir=C:\\Users\\dotan\\AppData\\Roaming\\nvm\\v16.16.0\\node_modules\\npm\\node_modules\\node-gyp',
npm ERR! gyp info spawn args '-Dnode_lib_file=C:\\\\Users\\\\dotan\\\\AppData\\\\Local\\\\node-gyp\\\\Cache\\\\16.16.0\\\\<(target_arch)\\\\node.lib',
npm ERR! gyp info spawn args '-Dmodule_root_dir=C:\\Users\\dotan\\Desktop\\ECO-OS\\ecoos\\node_modules\\v8-debug',
npm ERR! gyp info spawn args '-Dnode_engine=v8',
npm ERR! gyp info spawn args '--depth=.',
npm ERR! gyp info spawn args '--no-parallel',
npm ERR! gyp info spawn args '--generator-output',
npm ERR! gyp info spawn args 'C:\\Users\\dotan\\Desktop\\ECO-OS\\ecoos\\node_modules\\v8-debug\\build',
npm ERR! gyp info spawn args '-Goutput_dir=.'
npm ERR! gyp info spawn args ]
npm ERR! Traceback (most recent call last):
npm ERR! File "C:\Users\dotan\AppData\Roaming\nvm\v16.16.0\node_modules\npm\node_modules\node-gyp\gyp\gyp_main.py", line 45, in <module>
npm ERR! sys.exit(gyp.script_main())
npm ERR! File "C:\Users\dotan\AppData\Roaming\nvm\v16.16.0\node_modules\npm\node_modules\node-gyp\gyp\pylib\gyp\__init__.py", line 662, in script_main
npm ERR! return main(sys.argv[1:])
npm ERR! File "C:\Users\dotan\AppData\Roaming\nvm\v16.16.0\node_modules\npm\node_modules\node-gyp\gyp\pylib\gyp\__init__.py", line 654, in main
npm ERR! return gyp_main(args)
npm ERR! File "C:\Users\dotan\AppData\Roaming\nvm\v16.16.0\node_modules\npm\node_modules\node-gyp\gyp\pylib\gyp\__init__.py", line 639, in gyp_main
npm ERR! generator.GenerateOutput(flat_list, targets, data, params)
npm ERR! File "C:\Users\dotan\AppData\Roaming\nvm\v16.16.0\node_modules\npm\node_modules\node-gyp\gyp\pylib\gyp\generator\msvs.py", line 2162, in GenerateOutput
npm ERR! sln = MSVSNew.MSVSSolution(
npm ERR! File "C:\Users\dotan\AppData\Roaming\nvm\v16.16.0\node_modules\npm\node_modules\node-gyp\gyp\pylib\gyp\MSVSNew.py", line 228, in __init__
npm ERR! self.Write()
npm ERR! File "C:\Users\dotan\AppData\Roaming\nvm\v16.16.0\node_modules\npm\node_modules\node-gyp\gyp\pylib\gyp\MSVSNew.py", line 367, in Write
npm ERR! f.close()
npm ERR! File "C:\Users\dotan\AppData\Roaming\nvm\v16.16.0\node_modules\npm\node_modules\node-gyp\gyp\pylib\gyp\common.py", line 413, in close
npm ERR! os.rename(self.tmp_path, filename)
npm ERR! FileExistsError: [WinError 183] Cannot create a file when that file already exists: 'C:\\Users\\dotan\\Desktop\\ECO-OS\\ecoos\\node_modules\\v8-debug\\build\\binding.sln.gyp.4ckqfiz7.tmp' -> 'C:\\Users\\dotan\\Desktop\\ECO-OS\\ecoos\\node_modules\\v8-debug\\build\\binding.sln'
npm ERR! gyp info ok
npm ERR! gyp ERR! configure error
npm ERR! gyp ERR! stack Error: `gyp` failed with exit code: 1
npm ERR! gyp ERR! stack at ChildProcess.onCpExit (C:\Users\dotan\AppData\Roaming\nvm\v16.16.0\node_modules\npm\node_modules\node-gyp\lib\configure.js:261:16)
npm ERR! gyp ERR! stack at ChildProcess.emit (node:events:527:28)
npm ERR! gyp ERR! stack at Process.ChildProcess._handle.onexit (node:internal/child_process:291:12)
npm ERR! gyp ERR! System Windows_NT 10.0.22000
npm ERR! gyp ERR! command "C:\\Program Files\\nodejs\\node.exe" "C:\\Users\\dotan\\AppData\\Roaming\\nvm\\v16.16.0\\node_modules\\npm\\node_modules\\node-gyp\\bin\\node-gyp.js" "configure" "--fallback-to-build" "--module=C:\\Users\\dotan\\Desktop\\ECO-OS\\ecoos\\node_modules\\v8-debug\\build\\debug\\v0.7.7\\node-v93-win32-x64\\debug.node" "--module_name=debug" "--module_path=C:\\Users\\dotan\\Desktop\\ECO-OS\\ecoos\\node_modules\\v8-debug\\build\\debug\\v0.7.7\\node-v93-win32-x64"
npm ERR! gyp ERR! cwd C:\Users\dotan\Desktop\ECO-OS\ecoos\node_modules\v8-debug
npm ERR! gyp ERR! node -v v16.16.0
npm ERR! gyp ERR! node-gyp -v v9.0.0
npm ERR! gyp ERR! not ok
npm ERR! node-pre-gyp ERR! build error
npm ERR! node-pre-gyp ERR! stack Error: Failed to execute 'C:\Program Files\nodejs\node.exe C:\Users\dotan\AppData\Roaming\nvm\v16.16.0\node_modules\npm\node_modules\node-gyp\bin\node-gyp.js configure --fallback-to-build --module=C:\Users\dotan\Desktop\ECO-OS\ecoos\node_modules\v8-debug\build\debug\v0.7.7\node-v93-win32-x64\debug.node --module_name=debug --module_path=C:\Users\dotan\Desktop\ECO-OS\ecoos\node_modules\v8-debug\build\debug\v0.7.7\node-v93-win32-x64' (1)
npm ERR! node-pre-gyp ERR! stack at ChildProcess.<anonymous> (C:\Users\dotan\Desktop\ECO-OS\ecoos\node_modules\node-pre-gyp\lib\util\compile.js:83:29)
npm ERR! node-pre-gyp ERR! stack at ChildProcess.emit (node:events:527:28)
npm ERR! node-pre-gyp ERR! stack at maybeClose (node:internal/child_process:1092:16)
npm ERR! node-pre-gyp ERR! stack at Process.ChildProcess._handle.onexit (node:internal/child_process:302:5)
npm ERR! node-pre-gyp ERR! System Windows_NT 10.0.22000
npm ERR! node-pre-gyp ERR! command "C:\\Program Files\\nodejs\\node.exe" "C:\\Users\\dotan\\Desktop\\ECO-OS\\ecoos\\node_modules\\node-pre-gyp\\bin\\node-pre-gyp" "install" "--fallback-to-build"
npm ERR! node-pre-gyp ERR! cwd C:\Users\dotan\Desktop\ECO-OS\ecoos\node_modules\v8-debug
npm ERR! node-pre-gyp ERR! node -v v16.16.0
npm ERR! node-pre-gyp ERR! node-pre-gyp -v v0.6.39
npm ERR! node-pre-gyp ERR! not ok
npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\dotan\AppData\Local\npm-cache\_logs\2022-08-14T06_57_28_583Z-debug-0.log
Here are the program dependencies from the package.json file:
"dependencies": {
"acl": "~0.4.4",
"angular-material": "^1.0.1",
"angular-toastr": "^1.7.0",
"angularjs-toaster": "^1.1.0",
"async": "^2.0.0-rc.2",
"body-parser": "^1.14.2",
"bower": "^1.4.1",
"cfenv": "~1.0.0",
"chalk": "^1.1.0",
"compression": "^1.5.0",
"connect-flash": "~0.1.1",
"connect-mongo": "~1.1.0",
"consolidate": "~0.14.0",
"cookie-parser": "^1.3.2",
"crypto": "0.0.3",
"csvtojson": ">=0.5.2",
"event-stream": "^3.3.2",
"express": "^4.13.1",
"express-session": "^1.11.3",
"file-stream-rotator": "~0.0.6",
"forever": "~0.15.1",
"generate-password": "^1.1.1",
"glob": "^7.0.0",
"grunt": "^1.0.1",
"grunt-cli": "~1.4.0",
"helmet": "~1.3.0",
"jasmine-core": "^2.3.4",
"lodash": "^4.5.0",
"method-override": "^2.3.3",
"mocha": "~2.4.5",
"mongoose": "~4.4.4",
"morgan": "^1.6.1",
"multer": "~1.1.0",
"nodemailer": "^2.2.0",
"owasp-password-strength-test": "^1.3.0",
"passport": "~0.3.2",
"passport-facebook": "^2.0.0",
"passport-github": "~1.1.0",
"passport-google-oauth": "~1.0.0",
"passport-linkedin": "~1.0.0",
"passport-local": "^1.0.0",
"passport-paypal-openidconnect": "^0.1.1",
"passport-twitter": "^1.0.2",
"pdfkit": "^0.7.2",
"phantom": "^2.1.7",
"phantom-html2pdf": "^2.0.2",
"phantom-proxy": "^0.1.792",
"phantomjs-prebuilt": "^2.1.7",
"regression": "^1.2.1",
"save-svg-as-png": "^1.0.2",
"serve-favicon": "^2.3.0",
"socket.io": "^1.3.7",
"stream-to-mongo": "^0.1.5",
"swig": "^1.4.2",
"toastr": "^2.1.2",
"validator": "^5.2.0"
},
"devDependencies": {
"coveralls": "^2.11.4",
"grunt": "^1.0.1",
"grunt-concurrent": "^2.0.0",
"grunt-contrib-copy": "~1.0.0",
"grunt-contrib-csslint": "~1.0.0",
"grunt-contrib-cssmin": "~1.0.1",
"grunt-contrib-jshint": "~1.0.0",
"grunt-contrib-less": "^1.0.1",
"grunt-contrib-sass": "^1.0.0",
"grunt-contrib-uglify": "~1.0.1",
"grunt-contrib-watch": "~1.0.0",
"grunt-env": "~0.4.4",
"grunt-eslint": "~18.0.0",
"grunt-karma": "~0.12.1",
"grunt-mocha-istanbul": "~5.0.1",
"grunt-mocha-test": "~0.12.7",
"grunt-ng-annotate": "^2.0.1",
"grunt-node-inspector": "~0.4.1",
"grunt-nodemon": "~0.4.0",
"grunt-protractor-coverage": "~0.2.15",
"grunt-protractor-runner": "^3.0.0",
"gulp": "^3.9.0",
"gulp-angular-templatecache": "^1.7.0",
"gulp-autoprefixer": "^3.1.0",
"gulp-concat": "^2.6.0",
"gulp-csslint": "~0.3.0",
"gulp-cssmin": "~0.1.7",
"gulp-eslint": "~2.0.0",
"gulp-jshint": "^2.0.0",
"gulp-karma": "~0.0.4",
"gulp-less": "^3.0.3",
"gulp-livereload": "^3.8.0",
"gulp-load-plugins": "^1.0.0-rc.1",
"gulp-mocha": "^2.1.2",
"gulp-ng-annotate": "^2.0.0",
"gulp-nodemon": "^2.0.3",
"gulp-protractor": "^2.1.0",
"gulp-rename": "^1.2.2",
"gulp-sass": "^2.0.3",
"gulp-uglify": "^1.2.0",
"gulp-util": "^3.0.6",
"karma": "~0.13.21",
"karma-chrome-launcher": "~0.2.0",
"karma-coverage": "~0.5.3",
"karma-firefox-launcher": "~0.1.6",
"karma-jasmine": "~0.3.6",
"karma-ng-html2js-preprocessor": "^0.2.1",
"karma-phantomjs-launcher": "~1.0.0",
"load-grunt-tasks": "^3.2.0",
"mock-fs": "~3.8.0",
"run-sequence": "^1.1.1",
"should": "^8.2.2",
"supertest": "^1.0.1"
}
I currently using npm 8.11.0, 16.16.0.
Thanks a lot.

Firabase Functions deploy had errors

I'm trying to deploy my app to firebase but every time give me this issue but I don't know what is it need !?
this is my code in app.js
//construct
const functions = require("firebase-functions")
const express = require('express');
const app = express();
const path = require('path');
const bodyParser = require('body-parser');
const cors = require('cors');
const config = require('./config');
//const port = config.port;
//initialize
app.use(cors());
app.use(bodyParser.json());
app.use(bodyParser.urlencoded({ extended: true}));
app.use(express.static(path.join(__dirname,'../public')));
const books= require('./routes/books');
app.use('/books', books);
exports.app = functions.https.onRequest(app)
//start server code
// app.listen(port, ()=> {
// console.log('node serve has been started on port : '+port);
// })
functions: Finished running predeploy script. i functions: ensuring necessary APIs are enabled...
functions: all necessary APIs are enabled i functions: preparing functions directory for uploading... i functions: packaged functions
(57.1 KB) for uploading
functions: functions folder uploaded successfully i hosting[angular6test-1c758]: beginning deploy... i
hosting[angular6test-1c758]: found 68 files in public
hosting[angular6test-1c758]: file upload complete i functions: updating Node.js 6 function app(us-central1)... !
functions[app(us-central1)]: Deployment error. Build failed: exit
status 1
canvas#2.4.1 install /workspace/node_modules/canvas
node-pre-gyp install --fallback-to-build
node-pre-gyp WARN Using needle for node-pre-gyp https download
node-pre-gyp WARN Tried to download(404):
https://github.com/node-gfx/node-canvas-prebuilt/releases/download/v2.4.1/canvas-v2.4.1-node-v48-linux-glibc-x64.tar.gz
node-pre-gyp WARN Pre-built binaries not found for canvas#2.4.1 and
node#6.16.0 (node-v48 ABI, glibc) (falling back to source compile with
node-gyp) /bin/sh: 1: pkg-config: not found gyp: Call to 'pkg-config
pixman-1 --libs' returned exit status 127 while in binding.gyp. while
trying to load binding.gyp gyp ERR! configure error gyp ERR! stack
Error: gyp failed with exit code: 1 gyp ERR! stack at
ChildProcess.onCpExit
(/nodejs/lib/node_modules/npm/node_modules/node-gyp/lib/configure.js:305:16)
gyp ERR! stack at emitTwo (events.js:106:13) gyp ERR! stack at
ChildProcess.emit (events.js:191:7) gyp ERR! stack at
Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)
gyp ERR! System Linux 4.15.0-1028-gcp gyp ERR! command
"/nodejs/bin/node"
"/nodejs/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js"
"configure" "--fallback-to-build"
"--module=/workspace/node_modules/canvas/build/Release/canvas.node"
"--module_name=canvas"
"--module_path=/workspace/node_modules/canvas/build/Release"
"--napi_version=3" "--node_abi_napi=napi" "--napi_build_version=0"
"--node_napi_label=node-v48" gyp ERR! cwd
/workspace/node_modules/canvas gyp ERR! node -v v6.16.0 gyp ERR!
node-gyp -v v3.4.0 gyp ERR! not ok node-pre-gyp ERR! build error
node-pre-gyp ERR! stack Error: Failed to execute '/nodejs/bin/node
/nodejs/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js
configure --fallback-to-build
--module=/workspace/node_modules/canvas/build/Release/canvas.node --module_name=canvas --module_path=/workspace/node_modules/canvas/build/Release --napi_version=3 --node_abi_napi=napi --napi_build_version=0 --node_napi_label=node-v48' (1) node-pre-gyp ERR! stack at ChildProcess.
(/workspace/node_modules/canvas/node_modules/node-pre-gyp/lib/util/compile.js:83:29)
node-pre-gyp ERR! stack at emitTwo (events.js:106:13) node-pre-gyp
ERR! stack at ChildProcess.emit (events.js:191:7) node-pre-gyp
ERR! stack at maybeClose (internal/child_process.js:920:16)
node-pre-gyp ERR! stack at Process.ChildProcess._handle.onexit
(internal/child_process.js:230:5) node-pre-gyp ERR! System Linux
4.15.0-1028-gcp node-pre-gyp ERR! command "/nodejs/bin/node" "/workspace/node_modules/canvas/node_modules/.bin/node-pre-gyp"
"install" "--fallback-to-build" node-pre-gyp ERR! cwd
/workspace/node_modules/canvas node-pre-gyp ERR! node -v v6.16.0
node-pre-gyp ERR! node-pre-gyp -v v0.11.0 node-pre-gyp ERR! not ok
Failed to execute '/nodejs/bin/node
/nodejs/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js
configure --fallback-to-build
--module=/workspace/node_modules/canvas/build/Release/canvas.node --module_name=canvas --module_path=/workspace/node_modules/canvas/build/Release --napi_version=3 --node_abi_napi=napi --napi_build_version=0 --node_napi_label=node-v48' (1) aa14#0.0.1 /workspace `-- merge-images#1.1.0
npm ERR! Linux 4.15.0-1028-gcp npm ERR! argv "/nodejs/bin/node"
"/nodejs/bin/npm" "--global-style" "--production" "--fetch-retries=5"
"--fetch-retry-factor=2" "--fetch-retry-mintimeout=1000" "install"
"/workspace" npm ERR! node v6.16.0 npm ERR! npm v3.10.10 npm ERR!
code ELIFECYCLE
npm ERR! canvas#2.4.1 install: node-pre-gyp install
--fallback-to-build npm ERR! Exit status 1 npm ERR! npm ERR! Failed at the canvas#2.4.1 install script 'node-pre-gyp install
--fallback-to-build'. npm ERR! Make sure you have the latest version of node.js and npm installed. npm ERR! If you do, this is most likely
a problem with the canvas package, npm ERR! not with npm itself. npm
ERR! Tell the author that this fails on your system: npm ERR!
node-pre-gyp install --fallback-to-build npm ERR! You can get
information on how to open an issue for this project with: npm ERR!
npm bugs canvas npm ERR! Or if that isn't available, you can get their
info via: npm ERR! npm owner ls canvas npm ERR! There is likely
additional logging output above.
npm ERR! Please include the following file with any support request:
npm ERR! /workspace/npm-debug.log
Functions deploy had errors with the following functions:
app
To try redeploying those functions, run:
firebase deploy --only functions:app
To continue deploying other features (such as database), run:
firebase deploy --except functions
Error: Functions did not deploy properly.
**
I Found the answer
**
firebase deploy using node 6 as default
add "engines": { "node": "8" } to upgrade the node

Heroku logs "meteor not found"

Hi I am trying to deploy my meteorJS app to heroku, my site is showing this, how can I fix this?:
Application error
An error occurred in the application and your page could not be served. If you are the application owner, check your logs for details.
https://mkred.herokuapp.com/
I am getting this error in my heroku logs:
2017-05-19T14:14:03.499437+00:00 heroku[web.1]: Starting process with command `npm start`
2017-05-19T14:14:06.322560+00:00 app[web.1]:
2017-05-19T14:14:06.322581+00:00 app[web.1]: > mkred# start /app
2017-05-19T14:14:06.322582+00:00 app[web.1]: > meteor run
2017-05-19T14:14:06.322582+00:00 app[web.1]:
2017-05-19T14:14:06.332513+00:00 app[web.1]: sh: 1: meteor: not found
2017-05-19T14:14:06.350330+00:00 app[web.1]: npm ERR! Linux 3.13.0-112-generic
2017-05-19T14:14:06.338381+00:00 app[web.1]:
2017-05-19T14:14:06.350859+00:00 app[web.1]: npm ERR! argv "/app/.heroku/node/bin/node" "/app/.heroku/node/bin/npm" "start"
2017-05-19T14:14:06.351084+00:00 app[web.1]: npm ERR! node v6.10.3
2017-05-19T14:14:06.351286+00:00 app[web.1]: npm ERR! npm v3.10.10
2017-05-19T14:14:06.351500+00:00 app[web.1]: npm ERR! file sh
2017-05-19T14:14:06.351682+00:00 app[web.1]: npm ERR! code ELIFECYCLE
2017-05-19T14:14:06.351907+00:00 app[web.1]: npm ERR! errno ENOENT
2017-05-19T14:14:06.352262+00:00 app[web.1]: npm ERR! syscall spawn
2017-05-19T14:14:06.352444+00:00 app[web.1]: npm ERR! mkred# start: `meteor run`
2017-05-19T14:14:06.352626+00:00 app[web.1]: npm ERR! spawn ENOENT
2017-05-19T14:14:06.352786+00:00 app[web.1]: npm ERR!
2017-05-19T14:14:06.352949+00:00 app[web.1]: npm ERR! Failed at the mkred# start script 'meteor run'.
2017-05-19T14:14:06.353081+00:00 app[web.1]: npm ERR! Make sure you have the latest version of node.js and npm installed.
2017-05-19T14:14:06.353219+00:00 app[web.1]: npm ERR! If you do, this is most likely a problem with the mkred package,
2017-05-19T14:14:06.353351+00:00 app[web.1]: npm ERR! not with npm itself.
2017-05-19T14:14:06.353481+00:00 app[web.1]: npm ERR! Tell the author that this fails on your system:
2017-05-19T14:14:06.353613+00:00 app[web.1]: npm ERR! meteor run
2017-05-19T14:14:06.353752+00:00 app[web.1]: npm ERR! You can get information on how to open an issue for this project with:
2017-05-19T14:14:06.353885+00:00 app[web.1]: npm ERR! npm bugs mkred
2017-05-19T14:14:06.354023+00:00 app[web.1]: npm ERR! Or if that isn't available, you can get their info via:
2017-05-19T14:14:06.354154+00:00 app[web.1]: npm ERR! npm owner ls mkred
2017-05-19T14:14:06.354283+00:00 app[web.1]: npm ERR! There is likely additional logging output above.
2017-05-19T14:14:06.362397+00:00 app[web.1]:
2017-05-19T14:14:06.362724+00:00 app[web.1]: npm ERR! Please include the following file with any support request:
2017-05-19T14:14:06.362875+00:00 app[web.1]: npm ERR! /app/npm-debug.log
2017-05-19T14:14:06.458295+00:00 heroku[web.1]: Process exited with status 1
2017-05-19T14:14:06.477342+00:00 heroku[web.1]: State changed from starting to crashed
2017-05-19T14:14:06.478779+00:00 heroku[web.1]: State changed from crashed to starting
2017-05-19T14:14:10.559212+00:00 heroku[web.1]: Starting process with command `npm start`
2017-05-19T14:14:16.452733+00:00 app[web.1]:
2017-05-19T14:14:16.452750+00:00 app[web.1]: > mkred# start /app
2017-05-19T14:14:16.452751+00:00 app[web.1]: > meteor run
2017-05-19T14:14:16.452751+00:00 app[web.1]:
2017-05-19T14:14:16.509230+00:00 app[web.1]: sh: 1: meteor: not found
2017-05-19T14:14:16.542185+00:00 app[web.1]:
2017-05-19T14:14:16.607377+00:00 app[web.1]: npm ERR! Linux 3.13.0-112-generic
2017-05-19T14:14:16.609274+00:00 app[web.1]: npm ERR! argv "/app/.heroku/node/bin/node" "/app/.heroku/node/bin/npm" "start"
2017-05-19T14:14:16.610648+00:00 app[web.1]: npm ERR! node v6.10.3
2017-05-19T14:14:16.611286+00:00 app[web.1]: npm ERR! npm v3.10.10
2017-05-19T14:14:16.612308+00:00 app[web.1]: npm ERR! file sh
2017-05-19T14:14:16.614062+00:00 app[web.1]: npm ERR! code ELIFECYCLE
2017-05-19T14:14:16.615617+00:00 app[web.1]: npm ERR! errno ENOENT
2017-05-19T14:14:16.620791+00:00 app[web.1]: npm ERR! syscall spawn
2017-05-19T14:14:16.621597+00:00 app[web.1]: npm ERR! mkred# start: `meteor run`
2017-05-19T14:14:16.622556+00:00 app[web.1]: npm ERR! spawn ENOENT
2017-05-19T14:14:16.623330+00:00 app[web.1]: npm ERR!
2017-05-19T14:14:16.625501+00:00 app[web.1]: npm ERR! Make sure you have the latest version of node.js and npm installed.
2017-05-19T14:14:16.625097+00:00 app[web.1]: npm ERR! Failed at the mkred# start script 'meteor run'.
2017-05-19T14:14:16.626725+00:00 app[web.1]: npm ERR! If you do, this is most likely a problem with the mkred package,
2017-05-19T14:14:16.627246+00:00 app[web.1]: npm ERR! not with npm itself.
2017-05-19T14:14:16.627589+00:00 app[web.1]: npm ERR! Tell the author that this fails on your system:
2017-05-19T14:14:16.628014+00:00 app[web.1]: npm ERR! meteor run
2017-05-19T14:14:16.628637+00:00 app[web.1]: npm ERR! You can get information on how to open an issue for this project with:
2017-05-19T14:14:16.629392+00:00 app[web.1]: npm ERR! npm bugs mkred
2017-05-19T14:14:16.629812+00:00 app[web.1]: npm ERR! Or if that isn't available, you can get their info via:
2017-05-19T14:14:16.630466+00:00 app[web.1]: npm ERR! npm owner ls mkred
2017-05-19T14:14:16.632622+00:00 app[web.1]: npm ERR! There is likely additional logging output above.
2017-05-19T14:14:16.668367+00:00 app[web.1]:
2017-05-19T14:14:16.669670+00:00 app[web.1]: npm ERR! Please include the following file with any support request:
2017-05-19T14:14:16.670806+00:00 app[web.1]: npm ERR! /app/npm-debug.log
2017-05-19T14:14:16.808709+00:00 heroku[web.1]: State changed from starting to crashed
2017-05-19T14:14:16.795557+00:00 heroku[web.1]: Process exited with status 1
2017-05-19T14:14:17.872397+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=mkred.herokuapp.com request_id=71763503-4229-4282-9056-d24e0939cd91 fwd="208.185.23.206" dyno= connect= service= status=503 bytes= protocol=https
2017-05-19T14:14:18.557778+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/favicon.ico" host=mkred.herokuapp.com request_id=e5f63fdf-4f15-4da3-896b-95196a2241bc fwd="208.185.23.206" dyno= connect= service= status=503 bytes= protocol=https
2017-05-19T14:17:14.776747+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=mkred.herokuapp.com request_id=01c50fd0-2594-4ffe-a0ea-d5764ef00b92 fwd="208.185.23.206" dyno= connect= service= status=503 bytes= protocol=https
2017-05-19T14:17:15.518706+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/favicon.ico" host=mkred.herokuapp.com request_id=fad8ff27-813f-4d20-86f4-f16d35b3a34e fwd="208.185.23.206" dyno= connect= service= status=503 bytes= protocol=https
Mohammads-MBP:mkred minimoe$

Meteor Direct not support by heroku.Node.js is Directly supported. Node.js use created Meteor Build Packs . You should use meteor buildpack Meteor Buildpack . And Heroku also availble Sandbox free Database. Thank You,Happy coding.

Meteor mup deploy fibers error

i get the following error when i try to mup deploy
Building Started: /Users/../.......
Started TaskList: Deploy app 'meteor' (linux)
[195.30.108.227] - Uploading bundle
[195.30.108.227] - Uploading bundle: SUCCESS
[195.30.108.227] - Setting up Environment Variables
[195.30.108.227] - Setting up Environment Variables: SUCCESS
[195.30.108.227] - Invoking deployment process
[195.30.108.227] x Invoking deployment process: FAILED
-----------------------------------STDERR-----------------------------------
les/fibers
gyp ERR! node -v v4.4.7
gyp ERR! node-gyp -v v3.3.1
gyp ERR! not ok
Build failed
npm ERR! Linux 3.13.0-32-generic
npm ERR! argv "/opt/nodejs/bin/node" "/usr/bin/npm" "install"
npm ERR! node v4.4.7
npm ERR! npm v2.15.8
npm ERR! code ELIFECYCLE
npm ERR! fibers#1.0.5 install: `node ./build.js`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the fibers#1.0.5 install script 'node ./build.js'.
npm ERR! This is most likely a problem with the fibers package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! node ./build.js
npm ERR! You can get information on how to open an issue for this project with:
npm ERR! npm bugs fibers
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!
npm ERR! npm owner ls fibers
npm ERR! There is likely additional logging output above.
npm ERR! Please include the following file with any support request:
npm ERR! /opt/meteor/tmp/bundle/programs/server/npm-debug.log
-----------------------------------STDOUT-----------------------------------
> ./bcrypt: npm install due to binary npm modules
bindings#1.0.0 node_modules/bindings
nodeunit#0.9.1 node_modules/nodeunit
└── tap#0.7.1 (inherits#2.0.1, buffer-equal#0.0.2, slide#1.1.6, deep-equal#1.0.1, yamlish#0.0.7, nopt#3.0.6, mkdirp#0.5.1, difflet#0.2.6, glob#4.5.3, runforcover#0.0.2)
> fibers#1.0.5 install /opt/meteor/tmp/bundle/programs/server/node_modules/fibers
> node ./build.js
make: Verzeichnis »/opt/meteor/tmp/bundle/programs/server/node_modules/fibers/build« wird betreten
CXX(target) Release/obj.target/fibers/src/fibers.o
make: Verzeichnis »/opt/meteor/tmp/bundle/programs/server/node_modules/fibers/build« wird verlassen
----------------------------------------------------------------------------

You are using node version v4.4.7, but meteor build run on v0.10.40 or lower.
You can use nvm for change your node version.

Had similar problem.
The issue was related to meteor version and mup
As my meteor was 1.2.1 and my mup 1.3.1, needed to change in mup.js to use older docker "kariahq/meteord" image
docker: {
// change to 'kadirahq/meteord' if your app is not using Meteor 1.4
image: 'kadirahq/meteord'
//image: 'abernix/meteord:base'
},

meteor app deployed to heroku successfully. heroku errors when I goes to the url

These are the error logs:
Heroku local runs perfectly fine. Does anyone know what these error logs mean and what I need to do to fix it?
Thank you.
I changed the node version to 0.10.45 since I hear that's what heroku needs to run meteor apps.
Things changed but I am getting an npm error now. I believe the npm version is 2.1+.
Please note since I do not use a mongo db in the app I did NOT include a mongo:labs setting in the heroku config. Does this break things as well?
2016-06-13T03:56:13.082236+00:00 app[web.1]: npm ERR! Or if that isn't available, you can get their info via:
2016-06-13T03:56:13.082363+00:00 app[web.1]: npm ERR!
2016-06-13T03:56:13.085838+00:00 app[web.1]: npm ERR! /app/npm-debug.log
2016-06-13T03:56:13.861094+00:00 heroku[web.1]: State changed from starting to crashed
2016-06-13T03:56:15.460115+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=keela.herokuapp.com request_id=eb256901-593c-43a0-be3e-e4347daecf40 fwd="206.108.215.194" dyno= connect= service= status=503 bytes=
2016-06-13T03:56:13.082236+00:00 app[web.1]: npm ERR! Or if that isn't available, you can get their info via:
2016-06-13T03:56:13.082494+00:00 app[web.1]: npm ERR! npm owner ls keela
2016-06-13T03:56:13.085156+00:00 app[web.1]:
2016-06-13T03:56:13.085479+00:00 app[web.1]: npm ERR! Please include the following file with any support request:
2016-06-13T03:56:13.861094+00:00 heroku[web.1]: State changed from starting to crashed
2016-06-13T03:56:13.846631+00:00 heroku[web.1]: Process exited with status 1
2016-06-13T03:56:15.460115+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=keela.herokuapp.com request_id=eb256901-593c-43a0-be3e-e4347daecf40 fwd="206.108.215.194" dyno= connect= service= status=503 bytes=
2016-06-13T03:56:13.082236+00:00 app[web.1]: npm ERR! Or if that isn't available, you can get their info via:
2016-06-13T03:56:13.082363+00:00 app[web.1]: npm ERR!
2016-06-13T03:56:13.846631+00:00 heroku[web.1]: Process exited with status 1
2016-06-13T03:56:15.460115+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=keela.herokuapp.com request_id=eb256901-593c-43a0-be3e-e4347daecf40 fwd="206.108.215.194" dyno= connect= service= status=503 bytes=
2016-06-13T03:56:13.082236+00:00 app[web.1]: npm ERR! Or if that isn't available, you can get their info via:
2016-06-13T03:56:13.082363+00:00 app[web.1]: npm ERR!
2016-06-13T03:56:13.082494+00:00 app[web.1]: npm ERR! npm owner ls keela
2016-06-13T03:56:13.085156+00:00 app[web.1]:
2016-06-13T03:56:13.082702+00:00 app[web.1]: npm ERR! There is likely additional logging output above.
2016-06-13T03:56:13.085479+00:00 app[web.1]: npm ERR! Please include the following file with any support request:
2016-06-13T03:56:13.085838+00:00 app[web.1]: npm ERR! /app/npm-debug.log
2016-06-13T03:56:13.846631+00:00 heroku[web.1]: Process exited with status 1
2016-06-13T03:56:16.056881+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/favicon.ico" host=keela.herokuapp.com request_id=45e1c2db-39c7-427f-b115-5a5927267642 fwd="206.108.215.194" dyno= connect= service= status=503 bytes=
2016-06-13T03:56:13.082236+00:00 app[web.1]: npm ERR! Or if that isn't available, you can get their info via:
2016-06-13T03:56:13.082494+00:00 app[web.1]: npm ERR! npm owner ls keela
2016-06-13T03:56:13.082702+00:00 app[web.1]: npm ERR! There is likely additional logging output above.
2016-06-13T03:56:13.085838+00:00 app[web.1]: npm ERR! /app/npm-debug.log
2016-06-13T03:56:13.861094+00:00 heroku[web.1]: State changed from starting to crashed
2016-06-13T03:56:13.846631+00:00 heroku[web.1]: Process exited with status 1
2016-06-13T03:56:15.460115+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=keela.herokuapp.com request_id=eb256901-593c-43a0-be3e-e4347daecf40 fwd="206.108.215.194" dyno= connect= service= status=503 bytes=
These are the heroku logs from terminal:
2016-06-13T03:56:05.528129+00:00 heroku[web.1]: State changed from crashed to starting
2016-06-13T03:56:06.563040+00:00 heroku[web.1]: Starting process with command `npm start`
2016-06-13T03:56:08.477065+00:00 app[web.1]:
2016-06-13T03:56:08.477075+00:00 app[web.1]: > keela# start /app
2016-06-13T03:56:08.477108+00:00 app[web.1]: > meteor run
2016-06-13T03:56:08.477109+00:00 app[web.1]:
2016-06-13T03:56:08.480791+00:00 app[web.1]: sh: 1: meteor: not found
2016-06-13T03:56:08.484354+00:00 app[web.1]:
2016-06-13T03:56:08.488227+00:00 app[web.1]: npm ERR! Linux 3.13.0-85-generic
2016-06-13T03:56:08.488707+00:00 app[web.1]: npm ERR! argv "/app/.heroku/node/bin/node" "/app/.heroku/node/bin/npm" "start"
2016-06-13T03:56:08.488728+00:00 app[web.1]: npm ERR! node v0.10.45
2016-06-13T03:56:08.488892+00:00 app[web.1]: npm ERR! npm v2.15.1
2016-06-13T03:56:08.489008+00:00 app[web.1]: npm ERR! file sh
2016-06-13T03:56:08.489134+00:00 app[web.1]: npm ERR! code ELIFECYCLE
2016-06-13T03:56:08.489268+00:00 app[web.1]: npm ERR! errno ENOENT
2016-06-13T03:56:08.489383+00:00 app[web.1]: npm ERR! syscall spawn
2016-06-13T03:56:08.489490+00:00 app[web.1]: npm ERR! keela# start: `meteor run`
2016-06-13T03:56:08.489846+00:00 app[web.1]: npm ERR! spawn ENOENT
2016-06-13T03:56:08.489945+00:00 app[web.1]: npm ERR!
2016-06-13T03:56:08.490043+00:00 app[web.1]: npm ERR! Failed at the keela# start script 'meteor run'.
2016-06-13T03:56:08.490119+00:00 app[web.1]: npm ERR! This is most likely a problem with the keela package,
2016-06-13T03:56:08.490220+00:00 app[web.1]: npm ERR! not with npm itself.
2016-06-13T03:56:08.490296+00:00 app[web.1]: npm ERR! Tell the author that this fails on your system:
2016-06-13T03:56:08.490540+00:00 app[web.1]: npm ERR! meteor run
2016-06-13T03:56:08.490622+00:00 app[web.1]: npm ERR! You can get information on how to open an issue for this project with:
2016-06-13T03:56:08.490726+00:00 app[web.1]: npm ERR! npm bugs keela
2016-06-13T03:56:08.490821+00:00 app[web.1]: npm ERR! Or if that isn't available, you can get their info via:
2016-06-13T03:56:08.490919+00:00 app[web.1]: npm ERR!
2016-06-13T03:56:08.490999+00:00 app[web.1]: npm ERR! npm owner ls keela
2016-06-13T03:56:08.491174+00:00 app[web.1]: npm ERR! There is likely additional logging output above.
2016-06-13T03:56:08.493551+00:00 app[web.1]:
2016-06-13T03:56:08.493856+00:00 app[web.1]: npm ERR! Please include the following file with any support request:
2016-06-13T03:56:08.494156+00:00 app[web.1]: npm ERR! /app/npm-debug.log
2016-06-13T03:56:09.185720+00:00 heroku[web.1]: State changed from starting to crashed
2016-06-13T03:56:09.186797+00:00 heroku[web.1]: State changed from crashed to starting
2016-06-13T03:56:09.168263+00:00 heroku[web.1]: Process exited with status 1
2016-06-13T03:56:10.415088+00:00 heroku[web.1]: Starting process with command `npm start`

Buildpacks or meteor heroku are still very unstable.
I had to go through comments of a buildpack site to use a fork of a buildpack.
You are also correct that meteor still uses 0.10.41+ version of node.
I changed this by changing my version of node to 0.10.45 using nvm.
Also using a npm version of 2.1.1
Make sure to configure your package.json for these settings as well!
Heroku error logs are so vague it gives me headaches.

Develop Reference

r css asp.net wordpress firebase qt symfony nginx http apache-flex