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

Switch from npm to Yarn #81

Closed
arcticicestudio opened this issue Oct 12, 2019 · 1 comment
Closed

Switch from npm to Yarn #81

arcticicestudio opened this issue Oct 12, 2019 · 1 comment
Labels
context-workflow scope-compatibility scope-stability type-task
Milestone
0.4.0

Comments

@arcticicestudio
Copy link
Owner

Since Yarn is fully compatible with npm, but provides way more useful features and uses a stable dependency solution strategy, snowsaw should use Yarn by default.
Therefore the npm specific package-lock.json file should be removed and replaced with Yarn's yarn.lock file.
@arcticicestudio arcticicestudio added this to the 0.4.0 milestone Oct 12, 2019
arcticicestudio added a commit that referenced this issue Oct 12, 2019
@arcticicestudio
Switch from npm to Yarn
b7de6db 
Since Yarn (1) is fully compatible with npm (2), but provides way more
useful features and uses a stable dependency solution strategy,
snowsaw now uses Yarn by default. Therefore the npm specific
`package-lock.json` file has been removed and replaced with Yarn's
`yarn.lock` file.

References:
  (1) https://yarnpkg.com
  (2) https://www.npmjs.com

Epic GH-33
Resolves GH-81
@arcticicestudio
Copy link
Owner Author

Resolved in b7de6db

@arcticicestudio arcticicestudio mentioned this issue Oct 12, 2019
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
context-workflow scope-compatibility scope-stability type-task
Projects
None yet
Milestone
0.4.0
Development

No branches or pull requests
2 participants
@arcticicestudio @svengreb