Skip to content

feat: pinned nodejs requirements with npm ci#666

Merged
regisb merged 1 commit intomasterfrom
regisb/npm-ci
May 24, 2022
Merged

feat: pinned nodejs requirements with npm ci#666
regisb merged 1 commit intomasterfrom
regisb/npm-ci

Conversation

@regisb
Copy link
Contributor

@regisb regisb commented May 16, 2022

Contrary to what we might expect, npm install does not install pinned
requirements from a project's package-lock.json. That's the responsibility of
npm ci: https://docs.npmjs.com/cli/v8/commands/npm-ci

Running npm ci is also much faster than npm install, so that's a huge win.

See this issue for reference: openedx/wg-frontend#100

@regisb
Copy link
Contributor Author

regisb commented May 16, 2022

This is ready for review @overhangio/tutor-developers. Cc @ghassanmas.

Copy link
Member

@ghassanmas ghassanmas left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This will be applied for building the image in production and development right? if yes
I think for development using npm install would be a batter option (unless developer in development mode is not concnered about node_modules)

Contrary to what we might expect, `npm install` does not install pinned
requirements from a project's package-lock.json. That's the responsibility of
`npm ci`: https://docs.npmjs.com/cli/v8/commands/npm-ci

Running `npm ci` is also *much* faster than `npm install`, so that's a huge win.

See this issue for reference: openedx/wg-frontend#100
@regisb regisb merged commit 4bbeb4b into master May 24, 2022
@regisb regisb deleted the regisb/npm-ci branch May 24, 2022 09:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants