Failed at the deploy script
See original GitHub issueHello,
I’m using this command to deploy: npx -n \"-r dotenv/config\" gatsby-plugin-s3 deploy --yes
Unfortunately the deployment fails:
0 info it worked if it ends with ok
1 verbose cli [ 'C:\\Program Files (x86)\\nodejs\\node.exe',
1 verbose cli 'C:\\Users\\AppData\\Roaming\\npm\\node_modules\\npm\\bin\\npm-cli.js',
1 verbose cli 'run',
1 verbose cli 'deploy' ]
2 info using npm@6.13.1
3 info using node@v10.15.3
4 verbose run-script [ 'predeploy', 'deploy', 'postdeploy' ]
5 info lifecycle me@0.1.0~predeploy: me@0.1.0
6 info lifecycle me@0.1.0~deploy: me@0.1.0
7 verbose lifecycle me@0.1.0~deploy: unsafe-perm in lifecycle true
8 verbose lifecycle me@0.1.0~deploy: PATH:
9 verbose lifecycle me@0.1.0~deploy: CWD: C:\Projects\StaticApp\me
10 silly lifecycle me@0.1.0~deploy: Args: [ '/d /s /c',
10 silly lifecycle 'npx -n "-r dotenv/config" gatsby-plugin-s3 deploy --yes' ]
11 silly lifecycle me@0.1.0~deploy: Returned: code: 1 signal: null
12 info lifecycle me@0.1.0~deploy: Failed to exec deploy script
13 verbose stack Error: me@0.1.0 deploy: `npx -n "-r dotenv/config" gatsby-plugin-s3 deploy --yes`
13 verbose stack Exit status 1
13 verbose stack at EventEmitter.<anonymous> (C:\Users\AppData\Roaming\npm\node_modules\npm\node_modules\npm-lifecycle\index.js:332:16)
13 verbose stack at EventEmitter.emit (events.js:189:13)
13 verbose stack at ChildProcess.<anonymous> (C:\Users\AppData\Roaming\npm\node_modules\npm\node_modules\npm-lifecycle\lib\spawn.js:55:14)
13 verbose stack at ChildProcess.emit (events.js:189:13)
13 verbose stack at maybeClose (internal/child_process.js:970:16)
13 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:259:5)
14 verbose pkgid me@0.1.0
15 verbose cwd C:\Projects\StaticApp\me
16 verbose Windows_NT 10.0.17763
17 verbose argv "C:\\Program Files (x86)\\nodejs\\node.exe" "C:\\Users\\AppData\\Roaming\\npm\\node_modules\\npm\\bin\\npm-cli.js" "run" "deploy"
18 verbose node v10.15.3
19 verbose npm v6.13.1
20 error code ELIFECYCLE
21 error errno 1
22 error me@0.1.0 deploy: `npx -n "-r dotenv/config" gatsby-plugin-s3 deploy --yes`
22 error Exit status 1
23 error Failed at the me@0.1.0 deploy script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 1, true ]
Any ideas, what might be wrong?
Best regards,
MM
Issue Analytics
- State:
- Created 4 years ago
- Comments:10
Top Results From Across the Web
React app deploy failure on github - Stack Overflow
Run the command in project folder git remote add origin <url> , with the URL of your repository on GitHub. · Run the...
Read more >Failed at the course-directory@0.1.0 deploy script - Treehouse
Hi guys. After pushing my code to github and configuring the package.json, I tried the script `npm run deploy', the terminal shows the...
Read more >Build was terminated: Build script returned non-zero exit code ...
Deploying problem. Deploy failed NPM. I am facing the error on deployment. Error on deployment. Build script returned non-zero exit code: 2 -...
Read more >"Deploy script deploy-wrapper.sh failed to execute" in Tomcat ...
ERROR: "Deploy script deploy-wrapper.sh failed to execute" in Tomcat log when Secure Agent fails to start.
Read more >Deploy Failed Node.js App - Render community
The error is telling you that there is no build script. If you go to your render dashboard, find your app, select settings...
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
Since everything works as expected with the simplified command, there is no issue for me. Thanks for the support!
Hmm. I’m really not sure what’s going on. Is there any issue with leaving dotenv out of the deploy? Or is the simplified command a viable workaround for you?