Skip to content
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

NPM version issue #5570

Closed
4 tasks
cnlucas opened this issue Sep 5, 2023 · 0 comments · Fixed by #5581
Closed
4 tasks

NPM version issue #5570

cnlucas opened this issue Sep 5, 2023 · 0 comments · Fixed by #5581

Comments

@cnlucas
Copy link
Member

cnlucas commented Sep 5, 2023

What we’re after

We use sudo npm install -g npm in our CMS circle config.yml file and it seems to work correctly by installing globally the NPM version that is paired by NVM with the node version we have selected. For API, we seem to be pulling in the latest NPM version. This may break our builds when they release a new NPM version and we are still on an older version. (this happened with the release of 10)

Screen Shot 2023-09-05 at 1 01 08 PM

We should figure out a way to make this consistent across repos---and pull in the paired NPM version in API instead of the most recent version.

Action item(s)

(These are the smaller tasks that should happen in order to complete this work)

  • Research how our circle NPM version is being determined
  • Confirm this issue described above
  • Implement a fix

Completion criteria

  • NPM is being pulled in correctly in circle for API

References/resources/technical considerations

(Is there sample code or a screenshot you can include to highlight a particular issue? Here is where you reinforce why this work is important)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

2 participants