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.

Sign up for GitHub

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

Jump to bottom

feat: use npm instead of yarn #3447

Merged
merged 6 commits into from
Nov 28, 2023
Merged

feat: use npm instead of yarn #3447

merged 6 commits into from
Nov 28, 2023

Conversation

robertsLando
Copy link
Member

No description provided.

@coveralls
Copy link

coveralls commented Nov 28, 2023 •
edited
Loading

Pull Request Test Coverage Report for Build 7019733310

  • 0 of 0 changed or added relevant lines in 0 files are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage increased (+1.1%) to 22.434%
Totals Coverage Status
Change from base Build 7007739961: 1.1%
Covered Lines: 3734
Relevant Lines: 17701
💛 - Coveralls

AlCalzone
AlCalzone previously approved these changes Nov 28, 2023
View reviewed changes
@robertsLando robertsLando changed the title chore: use npm instead of yarn feat: use npm instead of yarn Nov 28, 2023
@robertsLando robertsLando merged commit 1dc07ed into master Nov 28, 2023
8 checks passed
@robertsLando robertsLando deleted the drop-yarn branch November 28, 2023 13:53
@ahochsteger
Copy link
Collaborator

Just out of curiosity, why the switch from yarn to npm?

@robertsLando
Copy link
Member Author

See here: giaever-online-iot/zwave-js-ui#5 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@AlCalzone AlCalzone AlCalzone left review comments

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
4 participants
@robertsLando @coveralls @ahochsteger @AlCalzone