npm run deploy:frontend failing
See original GitHub issueNode version 7.2.0 NPM version 3.10.9
npm run deploy:frontend
is failing (npm run deploy:api
is working).
> NODE_ENV=production env-cmd foundation/environment/security.env.prod webpack --config foundation/webpack/webpack.prod.js -p && cp ./app/favicon.ico ./build/frontend/favicon.ico
[1] multi main 28 bytes {0} [built]
+ 1 hidden modules
npm ERR! Darwin 16.1.0
npm ERR! argv "/Users/scotttesler/.nvm/versions/node/v7.2.0/bin/node" "/Users/scotttesler/.nvm/versions/node/v7.2.0/bin/npm" "run" "build:frontend"
npm ERR! node v7.2.0
npm ERR! npm v3.10.9
npm ERR! code ELIFECYCLE
npm ERR! serverless-graphql@0.0.0 build:frontend: `NODE_ENV=production env-cmd foundation/environment/security.env.prod webpack --config foundation/webpack/webpack.prod.js -p && c
p ./app/favicon.ico ./build/frontend/favicon.ico`
npm ERR! Exit status 2
npm ERR!
npm ERR! Failed at the serverless-graphql@0.0.0 build:frontend script 'NODE_ENV=production env-cmd foundation/environment/security.env.prod webpack --config foundation/webpack/web
pack.prod.js -p && cp ./app/favicon.ico ./build/frontend/favicon.ico'.
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 serverless-graphql package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! NODE_ENV=production env-cmd foundation/environment/security.env.prod webpack --config foundation/webpack/webpack.prod.js -p && cp ./app/favicon.ico ./build/frontend/f
avicon.ico
Issue Analytics
- State:
- Created 7 years ago
- Comments:7 (3 by maintainers)
Top Results From Across the Web
npm no such file or directory when trying to run 'npm run deploy'
Failed at the frontend@1.0.0 deploy script. npm ERR! This is probably not a problem with npm. There is likely additional logging output above....
Read more >Why is the react deployment failing? Using "CI= npm run build ...
So to get the _redirects file into the client/build folder (which because it is the Publish directory is where Netlify expects it to...
Read more >Troubleshooting Node.js Deploys - Heroku Dev Center
Your Node.js deploy failed - now what? Start with these simple steps to troubleshoot a build issue. Check the buildpack.
Read more >npm-run-script
Description. This runs an arbitrary command from a package's "scripts" object. If no "command" is provided, it will list the available scripts.
Read more >Deploy Node web app Error - Render community
New > Static Site · Connect Repo · Give it a name · Build Command: npm run build (dependencies are installed automatically on...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Building/running
master
, I am now getting a new issue: https://github.com/serverless/serverless-graphql-apollo/issues/79@scotttesler Thanks for the update. I’ll comment here if I learn anything more but since it does work locally for me additional troubleshooting isn’t a priority right now.