{"action":"opened","issue":{"url":"https://api.github.com/repos/npm/npm/issues/19925","repository_url":"https://api.github.com/repos/npm/npm","labels_url":"https://api.github.com/repos/npm/npm/issues/19925/labels{/name}","comments_url":"https://api.github.com/repos/npm/npm/issues/19925/comments","events_url":"https://api.github.com/repos/npm/npm/issues/19925/events","html_url":"https://github.com/npm/npm/issues/19925","id":300488574,"number":19925,"title":"Executing \"heroku local web\", npm install error occured","user":{"login":"knittkg","id":25094755,"avatar_url":"https://avatars1.githubusercontent.com/u/25094755?v=4","gravatar_id":"","url":"https://api.github.com/users/knittkg","html_url":"https://github.com/knittkg","followers_url":"https://api.github.com/users/knittkg/followers","following_url":"https://api.github.com/users/knittkg/following{/other_user}","gists_url":"https://api.github.com/users/knittkg/gists{/gist_id}","starred_url":"https://api.github.com/users/knittkg/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/knittkg/subscriptions","organizations_url":"https://api.github.com/users/knittkg/orgs","repos_url":"https://api.github.com/users/knittkg/repos","events_url":"https://api.github.com/users/knittkg/events{/privacy}","received_events_url":"https://api.github.com/users/knittkg/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2018-02-27T04:19:18Z","updated_at":"2018-02-27T04:19:18Z","closed_at":null,"author_association":"NONE","body":"#### I'm opening this issue because:\r\n\r\n  - [ ] npm is crashing.\r\n  - [*] npm is producing an incorrect install.\r\n  - [ ] npm is doing something I don't understand.\r\n  - [ ] Other (_see below for feature requests_):\r\n\r\n#### What's going wrong?\r\nExecuting \"heroku local web\", npm install error occured\r\n\r\n#### How can the CLI team reproduce the problem?\r\n$ heroku local web\r\n ▸    heroku-cli: update available from 6.14.39-addc925 to 6.15.26-5726b6f\r\n[OKAY] Loaded ENV .env File as KEY=VALUE Format\r\n[WARN] ENOENT: no such file or directory, open 'Procfile'\r\n[OKAY] package.json file found - trying 'npm start'\r\n03:39:19 web.1   |  npm\r\n03:39:20 web.1   |   ERR! Linux 4.9.80-c9\r\n03:39:20 web.1   |  npm ERR! argv \"/home/ubuntu/.nvm/versions/node/v6.11.2/bin/node\" \"/home/ubuntu/.nvm/versions/node/v6.11.2/bin/npm\" \"start\"\r\n03:39:20 web.1   |  npm ERR! node v6.11.2\r\n03:39:20 web.1   |  npm ERR! npm  v3.10.10\r\n03:39:20 web.1   |  npm ERR! missing script: start\r\n03:39:20 web.1   |  npm ERR! \r\n03:39:20 web.1   |  npm ERR! If you need help, you may report this error at:\r\n03:39:20 web.1   |  npm ERR!     <https://github.com/npm/npm/issues>\r\n03:39:20 web.1   |  npm ERR! Please include the following file with any support request:\r\n03:39:20 web.1   |  npm ERR!     /home/ubuntu/workspace/audio_uploader_test_app/npm-debug.log\r\n03:39:20 web.1   Exited with exit code 1\r\n$ \r\n\r\n<!--\r\n    Please a complete description of how to reproduce the problem.\r\n    Include a gist of your npm-debug.log file.\r\n    If you've never used gist.github.com, start here:\r\n      https://github.com/EmmaRamirez/how-to-submit-your-npm-debug-log\r\n-->\r\n0 info it worked if it ends with ok\r\n1 verbose cli [ '/home/ubuntu/.nvm/versions/node/v6.11.2/bin/node',\r\n1 verbose cli   '/home/ubuntu/.nvm/versions/node/v6.11.2/bin/npm',\r\n1 verbose cli   'start' ]\r\n2 info using npm@3.10.10\r\n3 info using node@v6.11.2\r\n4 verbose stack Error: missing script: start\r\n4 verbose stack     at run (/home/ubuntu/.nvm/versions/node/v6.11.2/lib/node_modules/npm/lib/run-script.js:151:19)\r\n4 verbose stack     at /home/ubuntu/.nvm/versions/node/v6.11.2/lib/node_modules/npm/lib/run-script.js:61:5\r\n4 verbose stack     at /home/ubuntu/.nvm/versions/node/v6.11.2/lib/node_modules/npm/node_modules/read-package-json/read-json.js:356:5\r\n4 verbose stack     at checkBinReferences_ (/home/ubuntu/.nvm/versions/node/v6.11.2/lib/node_modules/npm/node_modules/read-package-json/read-json.js:320:45)\r\n4 verbose stack     at final (/home/ubuntu/.nvm/versions/node/v6.11.2/lib/node_modules/npm/node_modules/read-package-json/read-json.js:354:3)\r\n4 verbose stack     at then (/home/ubuntu/.nvm/versions/node/v6.11.2/lib/node_modules/npm/node_modules/read-package-json/read-json.js:124:5)\r\n4 verbose stack     at /home/ubuntu/.nvm/versions/node/v6.11.2/lib/node_modules/npm/node_modules/read-package-json/read-json.js:243:12\r\n4 verbose stack     at /home/ubuntu/.nvm/versions/node/v6.11.2/lib/node_modules/npm/node_modules/graceful-fs/graceful-fs.js:78:16\r\n4 verbose stack     at tryToString (fs.js:456:3)\r\n4 verbose stack     at FSReqWrap.readFileAfterClose [as oncomplete] (fs.js:443:12)\r\n5 verbose cwd /home/ubuntu/workspace/audio_uploader_test_app\r\n6 error Linux 4.9.80-c9\r\n7 error argv \"/home/ubuntu/.nvm/versions/node/v6.11.2/bin/node\" \"/home/ubuntu/.nvm/versions/node/v6.11.2/bin/npm\" \"start\"\r\n8 error node v6.11.2\r\n9 error npm  v3.10.10\r\n10 error missing script: start\r\n11 error If you need help, you may report this error at:\r\n11 error     <https://github.com/npm/npm/issues>\r\n12 verbose exit [ 1, true ]\r\n\r\n\r\n### supporting information:\r\n\r\n - `npm -v` prints:\r\n3.10.10\r\n - `node -v` prints:\r\nv6.11.2\r\n - `npm config get registry` prints:\r\nhttps://registry.npmjs.org/\r\n - Windows, OS X/macOS, or Linux?:\r\nLinux\r\n - Network issues:\r\n   - Geographic location where npm was run:\r\n   - [ ] I use a proxy to connect to the npm registry.\r\n   - [ ] I use a proxy to connect to the web.\r\n   - [ ] I use a proxy when downloading Git repos.\r\n   - [ ] I access the npm registry via a VPN\r\n   - [ ] I don't use a proxy, but have limited or unreliable internet access.\r\n - Container:\r\n   - [ ] I develop using Vagrant on Windows.\r\n   - [ ] I develop using Vagrant on OS X or Linux.\r\n   - [ ] I develop / deploy using Docker.\r\n   - [*] I deploy to a PaaS (Heroku).\r\n\r\n<!--\r\n    Thank you for contributing to npm! Please review this checklist\r\n    before submitting your issue.\r\n\r\n    - Please check if there's a solution in the troubleshooting wiki:\r\n      https://github.com/npm/npm/blob/latest/TROUBLESHOOTING.md\r\n\r\n    - Also ensure that your new issue conforms to npm's contribution guidelines:\r\n      https://github.com/npm/npm/blob/latest/CONTRIBUTING.md\r\n\r\n    - Participation in this open source project is subject to the npm Code of Conduct:\r\n      https://www.npmjs.com/policies/conduct\r\n\r\n    For feature requests, delete the above and uncomment the section following this one. But first, review the existing feature requests\r\n    and make sure there isn't one that already describes the feature\r\n    you'd like to see added:\r\n      https://github.com/npm/npm/issues?q=is%3Aopen+is%3Aissue+label%3Afeature-request+label%3Aalready-looked-at\r\n-->\r\n\r\n<!--\r\n\r\n#### What's the feature?\r\n\r\n#### What problem is the feature intended to solve?\r\n\r\n#### Is the absence of this feature blocking you or your team? If so, how?\r\n\r\n#### Is this feature similar to an existing feature in another tool?\r\n\r\n#### Is this a feature you're prepared to implement, with support from the npm CLI team?\r\n\r\n-->\r\n"}}
{"actor":{"display_login":"knittkg"}}