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

Migrate to yarn 2.0.0 #18

Closed
abhijithvijayan opened this issue Jan 27, 2020 · 3 comments
Closed

Migrate to yarn 2.0.0 #18

abhijithvijayan opened this issue Jan 27, 2020 · 3 comments
Labels
breaking change type: maintenance An issue or pull request describing a change that isn't a bug, feature or documentation change type: upstream Issues outside of this project's control, caused by dependencies

Comments

@abhijithvijayan
Copy link
Owner

abhijithvijayan commented Jan 27, 2020 •
edited

https://yarnpkg.com/advanced/migration
@abhijithvijayan abhijithvijayan added breaking change type: maintenance An issue or pull request describing a change that isn't a bug, feature or documentation change type: upstream Issues outside of this project's control, caused by dependencies labels Jan 27, 2020
@abhijithvijayan
Copy link
Owner Author

abhijithvijayan commented Jan 27, 2020 •
edited

Maybe use yarn 1 for now with specifying the version legacy to use instead of berry
and slowly migrate to yarn 2

@abhijithvijayan abhijithvijayan pinned this issue Jan 27, 2020
@abhijithvijayan
Copy link
Owner Author

Currently, the repo is set to use yarn v1 (with yarn 2 in local machine)
It is said that this is backward compatible.

currently, node_modules is being created when run with yarn2 as set by option

@abhijithvijayan
Copy link
Owner Author

#21 (comment)

@abhijithvijayan abhijithvijayan unpinned this issue Mar 9, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
breaking change type: maintenance An issue or pull request describing a change that isn't a bug, feature or documentation change type: upstream Issues outside of this project's control, caused by dependencies
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@abhijithvijayan