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

Move from yarn to npm #2008

Closed
KonstantinEpam23 opened this issue Dec 27, 2022 · 1 comment · Fixed by #2126
Closed

Move from yarn to npm #2008

KonstantinEpam23 opened this issue Dec 27, 2022 · 1 comment · Fixed by #2126

Comments

@KonstantinEpam23
Copy link
Collaborator

KonstantinEpam23 commented Dec 27, 2022

Is your feature request related to a problem? Please describe.
At the moment the project uses yarn, which seems to be problematic sometimes , for example we had problems with compiling different versions: #1970 Yarn seems to be too aggressive with its caching and .lock file handling when working with the workspaces feature.
npm is the standard tool for node, has larger userbase and more stable releases. Many developers are more familiar with it. It also supports some features out of the box that yarn requires plugins for.

We would like to switch to using npm as it an official tool for node and JS and .

Describe the solution you'd like
Replace yarn with npm

Steps that need to be taken:

  • completely replacing yarn with npm commands throughout the project (this includes package.json scripts, husky integrations, etc)
  • update documentation: update all documentation throughout the project, including readme files
  • announce changes to repo
  • update ci/cd and other infrastructure-related scripts that may contain yarn-specific commans
  • update node to at least verion 14 to be able to use npm version 6 workspace features
  • updateupdate github ci

Additional context
It is also important to note that such changes will need to be announced to the community, since many peoples workflows may depend on yarn. Probably this should be done within a major version release.

Related issues
#2031 #2030 #2029

@KonstantinEpam23
Copy link
Collaborator Author

Related ticket: #1740
It needs to be re-evaluated after this task is complete

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

Successfully merging a pull request may close this issue.

3 participants