Skip to content
This repository was archived by the owner on Apr 26, 2024. It is now read-only.

feat: Replaced "yarn" with "npm run" for crosplatform reasons#553

Closed
alexandrtovmach wants to merge 1 commit into
nodejs:stagingfrom
alexandrtovmach:patch/yarn-to-npm
Closed

feat: Replaced "yarn" with "npm run" for crosplatform reasons#553
alexandrtovmach wants to merge 1 commit into
nodejs:stagingfrom
alexandrtovmach:patch/yarn-to-npm

Conversation

@alexandrtovmach

Copy link
Copy Markdown
Contributor

Description

I really like yarn and using it as default package manager, but we should be standardized and go with npm in most cases that will going to run automatically. For example, I'm temporary using a laptop without yarn, and when I tried to push stuff, I've faced with error not related to code. That's wierd and related to using yarn to initialize npm script.

Proposed changes provides similar functionality

@alexandrtovmach

Copy link
Copy Markdown
Contributor Author

@nodejs/website-redesign

@alexandrtovmach

Copy link
Copy Markdown
Contributor Author

/gcbrun

@nschonni

Copy link
Copy Markdown
Member

Ah, yarn was removed from master already, but looks like staging is behind

@alexandrtovmach

Copy link
Copy Markdown
Contributor Author

@nschonni I think staging too behind the master, I'm not sure that will be easy to merge and resolve conflicts

@alexandrtovmach alexandrtovmach added the duplicate This issue or pull request already exists label Apr 23, 2020
@alexandrtovmach

alexandrtovmach commented Apr 23, 2020

Copy link
Copy Markdown
Contributor Author

Closed in favor #554

@alexandrtovmach alexandrtovmach deleted the patch/yarn-to-npm branch April 23, 2020 16:13
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

duplicate This issue or pull request already exists

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants