serverless-webpack: Google and Firebase - Unexpected end of JSON input
This is a (Bug Report / Feature Proposal)
Bug
Description
For bug reports:
- What went wrong?
⟩ serverless deploy
{}
Serverless: Bundling with Webpack...
Time: 637ms
Asset Size Chunks Chunk Names
index.js 4.32 kB 0 [emitted] main
[0] ./handler.js 1.57 kB {0} [built]
[1] external "firebase-admin" 42 bytes {0} [not cacheable]
[2] external "firebase-functions" 42 bytes {0} [not cacheable]
Syntax Error -------------------------------------------
Unexpected end of JSON input
For debugging logs, run again after setting the "SLS_DEBUG=*" environment variable.
Get Support --------------------------------------------
Docs: docs.serverless.com
Bugs: github.com/serverless/serverless/issues
Forums: forum.serverless.com
Chat: gitter.im/serverless/serverless
Your Environment Information -----------------------------
OS: darwin
Node Version: 9.3.0
Serverless Version: 1.25.0
- What did you expect should have happened?
Deployed correctly
- What was the config you used?
service: wrud
provider:
name: google
runtime: nodejs
project: XXXX
credentials: ~/.gcloud/XXXX.json
plugins:
- serverless-google-cloudfunctions
- serverless-webpack
custom:
webpackIncludeModules:
packagePath: './package.json'
# needs more granular excluding in production as only the serverless provider npm
# package should be excluded (and not the whole node_modules directory)
package:
exclude:
- node_modules/**
- .gitignore
- .git/**
functions:
hello:
handler: helloWorld
events:
- http: path
- What stacktrace or error message from your provider did you see?
Stack Trace --------------------------------------------
SyntaxError: Unexpected end of JSON input
SyntaxError: Unexpected end of JSON input
at JSON.parse (<anonymous>)
at BbPromise.try (/Users/work1/Projects/wrud/wrud/node_modules/serverless-webpack/lib/packExternalModules.js:236:47)
at tryCatcher (/Users/work1/Projects/wrud/wrud/node_modules/bluebird/js/release/util.js:16:23)
at Function.Promise.attempt.Promise.try (/Users/work1/Projects/wrud/wrud/node_modules/bluebird/js/release/method.js:39:29)
at BbPromise.fromCallback.then.depJson (/Users/work1/Projects/wrud/wrud/node_modules/serverless-webpack/lib/packExternalModules.js:236:35)
at tryCatcher (/Users/work1/Projects/wrud/wrud/node_modules/bluebird/js/release/util.js:16:23)
at Promise._settlePromiseFromHandler (/Users/work1/Projects/wrud/wrud/node_modules/bluebird/js/release/promise.js:512:31)
at Promise._settlePromise (/Users/work1/Projects/wrud/wrud/node_modules/bluebird/js/release/promise.js:569:18)
at Promise._settlePromise0 (/Users/work1/Projects/wrud/wrud/node_modules/bluebird/js/release/promise.js:614:10)
at Promise._settlePromises (/Users/work1/Projects/wrud/wrud/node_modules/bluebird/js/release/promise.js:693:18)
at Promise._fulfill (/Users/work1/Projects/wrud/wrud/node_modules/bluebird/js/release/promise.js:638:18)
at /Users/work1/Projects/wrud/wrud/node_modules/bluebird/js/release/nodeback.js:42:21
at childProcess.exec (/Users/work1/Projects/wrud/wrud/node_modules/serverless-webpack/lib/packExternalModules.js:233:16)
at ChildProcess.exithandler (child_process.js:279:5)
at ChildProcess.emit (events.js:159:13)
at maybeClose (internal/child_process.js:943:16)
at Process.ChildProcess._handle.onexit (internal/child_process.js:220:5)
From previous event:
at PluginManager.invoke (/usr/local/lib/node_modules/serverless/lib/classes/PluginManager.js:368:22)
at PluginManager.spawn (/usr/local/lib/node_modules/serverless/lib/classes/PluginManager.js:386:17)
at ServerlessWebpack.BbPromise.bind.then.then.then (/Users/work1/Projects/wrud/wrud/node_modules/serverless-webpack/index.js:90:51)
at runCallback (timers.js:773:18)
at tryOnImmediate (timers.js:734:5)
at processImmediate [as _immediateCallback] (timers.js:711:5)
Additional Data
package.json
{
"name": "google-nodejs",
"version": "0.1.0",
"description": "",
"main": "index.js",
"scripts": {
"test": "echo \"Error: no test specified\" && exit 1"
},
"author": "serverless.com",
"license": "MIT",
"dependencies": {
"babel-runtime": "^6.26.0",
"firebase-admin": "^5.8.0",
"firebase-functions": "^0.8.0",
"jsonschema": "^1.2.2",
"serverless-google-cloudfunctions": "^1.1.1"
},
"devDependencies": {
"babel-core": "^6.26.0",
"babel-loader": "^7.1.2",
"babel-plugin-transform-runtime": "^6.23.0",
"babel-preset-env": "^1.6.1",
"babel-preset-stage-3": "^6.24.1",
"eslint": "^4.15.0",
"eslint-config-standard": "^11.0.0-beta.0",
"eslint-plugin-import": "^2.8.0",
"eslint-plugin-node": "^5.2.1",
"eslint-plugin-promise": "^3.6.0",
"eslint-plugin-standard": "^3.0.1",
"serverless-webpack": "^4.2.0",
"webpack": "^3.10.0",
"webpack-node-externals": "^1.6.0"
}
}
- Serverless-Webpack Version you’re using: 4.2.0
- Webpack version you’re using: 3.10.0
- Serverless Framework Version you’re using: 1.25.0
- Operating System: OSX 10.13.2 (17C88) High Sierra
- Stack Trace (if available):
About this issue
- Original URL
- State: closed
- Created 6 years ago
- Comments: 21 (10 by maintainers)
Commits related to this issue
- Drop nodegit, use lambda-git instead `nodegit` caused all sorts of issues, and it takes too long to compile whether locally or on CI. Even worse, due to [a bug in `serverless-webpack`](https://githu... — committed to forabi/track-performance by forabi 6 years ago
- Drop nodegit, use lambda-git instead `nodegit` caused all sorts of issues, and it takes too long to compile whether locally or on CI. Even worse, due to [a bug in `serverless-webpack`](https://githu... — committed to forabi/track-performance by forabi 6 years ago
- Drop nodegit, use lambda-git instead (#6) `nodegit` caused all sorts of issues, and it takes too long to compile whether locally or on CI. Even worse, due to [a bug in `serverless-webpack`](https://... — committed to hollowverse-archive/track-performance by forabi 6 years ago
Looks like this is caused by using yarn. By deleting node_modules and then using npm, it works fine.
@alopes Yarn support is available in
masternow and will be part of the next release. Please give it a try and check if it now correctly handlesyarn.lockand works with yarn as expected. The README inmastercontains the exact steps on how to configure it - and adjust the webpack plugin configuration inserverless.ymlproperly to the new format.Hi @alopes . Thanks for the information and verification.
I think, having #286 done would make these cases very rare, as the plugin can then be configured to the packager that the user normally uses in his environment.
Hey, I believe I might be having the same issue. Works fine running locally with $sls offline start but once I try to deploy it I get that same error. Any ideas on how to tackle this issue? Thanks
Offline version
package.json
Hi @gastonmorixe, thanks for reporting.
According to the stacktrace, the plugin crashed, because it got an invalid output from the
npm ls -prod -json -depth=1command execution.Can you try to execute it manually and post the output, so that we can check what exactly is going wrong there?