Google and Firebase - Unexpected end of JSON input #309
Comments
|
Hi @gastonmorixe, thanks for reporting. According to the stacktrace, the plugin crashed, because it got an invalid output from the Can you try to execute it manually and post the output, so that we can check what exactly is going wrong there? |
|
@HyperBrain also |
|
@HyperBrain sorry to add more comments, it seems that with |
|
Thanks a lot. It seems that exactly the same happens during execution of the plugin (there might be a bug in the plugin that prevents noticing the npm error and so the parser fails in the end). I will try if I get some time tomorrow, so that I can prepare exactly the same package.json, so that I can try to find out why npm fails here. (currently the plugin is based entirely on npm internally). I'll let you know if I found out anything. |
|
I moved to |
|
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? Offline version package.json |
|
Looks like this is caused by using yarn. |
|
Just got caught by this while using |
|
@shwanton The section has been added just a few days ago ;-) |
|
I"m having this problem without using yarn, with identical results to @alopes |
|
@samwiseduzer Can you check your npm version and try to delete the npm cache (see |
|
Deleting and reinstalling my packages seemed to take care of this |
forabi
added a commit
to forabi/track-performance
that referenced
this issue
Feb 28, 2018
`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`](serverless-heaven/serverless-webpack#309) we have to compile it twice, which takes over 15 minutes on Travis. This PR drops `nodegit` and replaces it with a regular `git` binary [compiled specifically for AWS Lambda](https://github.com/pimterry/lambda-git). This may or may not work!
forabi
added a commit
to forabi/track-performance
that referenced
this issue
Feb 28, 2018
`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`](serverless-heaven/serverless-webpack#309) we have to compile it twice, which takes over 15 minutes on Travis. This PR drops `nodegit` and replaces it with a regular `git` binary [compiled specifically for AWS Lambda](https://github.com/pimterry/lambda-git). This may or may not work!
forabi
added a commit
to hollowverse-archive/track-performance
that referenced
this issue
Feb 28, 2018
`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`](serverless-heaven/serverless-webpack#309) we have to compile it twice, which takes over 15 minutes on Travis. This PR drops `nodegit` and replaces it with a regular `git` binary [compiled specifically for AWS Lambda](https://github.com/pimterry/lambda-git). This may or may not work!
|
I ran into this problem again because of unmet peer dependencies (which I discovered after running "npm ls -prod -json -depth=1"). Fixing the peer dependency took care of the issue for me. |
|
@alopes Yarn support is available in |
|
Update: Yarn support is just released with 5.1.0 💥 |
|
@gastonmorixe Is there any update for this issue on your side. In case you use yarn, you could try plugin version 5.1.0 and configure it to use yarn as packager (if you don't use it, you can try that too ;-) ). |
|
Sorry guys, not using it anymore. Just using firebase directly.
On Wednesday, March 14, 2018, Frank Schmid ***@***.***> wrote:
@gastonmorixe Is there any update for this issue on your side. In case
you use yarn, you could try plugin version 5.1.0 (if you don't use it, you
can try that too ;-) ).
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.<
…--
Sent from Gmail Mobile
|
|
Ok. I'm closing the issue now. Feel free to continue here if needed 😄 |
|
@gastonmorixe @alopes I finally found the root cause for the original The fix will be released soon with version 5.1.2. If you have some time, you can check out if the current master branch works for you. |
This was referenced Sep 23, 2018
1 task
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This is a (Bug Report / Feature Proposal)
Bug
Description
For bug reports:
Deployed correctly
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" } }The text was updated successfully, but these errors were encountered: