-
Notifications
You must be signed in to change notification settings - Fork 32
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: add package-lock.json and add CI check #40
Conversation
}, | ||
"devDependencies": { | ||
"npm": "10.2.3", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I install [email protected]
(which is the one we use in WebContainer) so you don't have to install that version on your machine if you want to run the package:*
scripts.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks really nice! Some questions but we probably should do as follow-ups.
new Error( | ||
`The \`package-lock.json\` is not in sync with the \`package.json\` for starter \`${name}\`.` | ||
) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice 👍
This PR adds
package-lock.json
back. This PR addresses the cons that are discussed in #14.package-lock.json
in EngineBlock projects, so we'd have to check that we don't end up adding those.package.json
but not thepackage-lock.json
, and we don't have any CI checking that.package-lock.json
, then installing dependencies becomes slower on StackBlitz that if we didn't have one (and were generating a new one on import).