Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Plase add package.lock.json or yarn.lock

See original GitHub issue

Without it npm installs different versions, and the project might be broken with random error messages.

For example:

not finished load plugins - 0.671s
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! gatsby-starter-blog@0.1.0 jamstack-develop: `node createConfig.js && gatsby develop`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the gatsby-starter-blog@0.1.0 jamstack-develop script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /root/.npm/_logs/2019-11-05T12_00_51_245Z-debug.log

Caused by: https://github.com/aws-amplify/amplify-js/issues/4268

Issue Analytics

State:
Created 4 years ago
Comments:7

Top GitHub Comments

2reactions

dabit3commented, Nov 6, 2019

Hey, so tested this out some, and I have figured out that there are some issues with some npm dependencies with Amplify at the time being. For now, just use yarn and follow the new instructions, you should be good to go. Once I get the issues figured out with npm and the new release of Amplify is out, I’ll also add a package-lock.json for npm users.

1reaction

dabit3commented, Nov 5, 2019

@reece2208 have you all tried yarn?