Repository navigation
yarn.lock prevents deploying the hello-world appengine sample #308
Copy link
Copy link
Closed
Labels
🚨This issue needs some love.This issue needs some love.triage meI really want to be triaged.I really want to be triaged.
Description
Activity
I have updated the tutorial to include instructions about using Yarn, and I have I've updated the dependencies in this repo such that the
yarn check --strict-semver --integritycommand should succeed during deployment.On this tutorial - Run MongoDB on Google Cloud Platform:
https://cloud.google.com/nodejs/resources/databases/mongodbI also hit an issue when executing "gcloud app deploy", which failed in errors that are same as above.
It seems this page lacks this step!
or just remind to install yarn first, and use "yarn install", then "yarn start" :)
Good catch, I'll update this tutorial as well
- addedtriage meI really want to be triaged.I really want to be triaged.🚨This issue needs some love.This issue needs some love.
on Apr 7, 2020 - added a commit that references this issue
on Oct 26, 2022 - added 2 commits that reference this issue
on Nov 3, 2022 3 remaining items
- added 10 commits that reference this issue
on Nov 14, 2022 - added a commit that references this issue
on Nov 17, 2022 - added a commit that references this issue
on Nov 17, 2022 - added a commit that references this issue
on Nov 18, 2022 - added a commit that references this issue
on Nov 21, 2022 - added a commit that references this issue
on Nov 22, 2022
Metadata
Metadata
Assignees
Labels
🚨This issue needs some love.This issue needs some love.triage meI really want to be triaged.I really want to be triaged.
If you follow this tutorial:
https://cloud.google.com/nodejs/getting-started/hello-world
You will hit an issue when you try and
gcloud app deploywhich fails.This is because of this yarn.lock file:
https://github.com/GoogleCloudPlatform/nodejs-docs-samples/blob/master/appengine/hello-world/yarn.lock
The error you see will be:
No sure why this is checkin here as the tutorial uses npm.
Removing the file locally before deploying will fix the issue.