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

support yarn as packageManager #540

Closed
3 tasks
GiladShoham opened this issue Jan 2, 2018 · 0 comments · Fixed by #576
Closed
3 tasks

support yarn as packageManager #540

GiladShoham opened this issue Jan 2, 2018 · 0 comments · Fixed by #576

Comments

@GiladShoham
Copy link
Member

  • add the default components folder as workspace
  • add .dependencies folder as workspace
  • add component imported with -p as workspace

If we can call yarn programmatically maybe we can pass it on runtime from the bit.map.
If not we probably need to edit the package.json of the project

another option is to tell the user to define some of the workspaces himself (maybe at least the defaults one)

@GiladShoham GiladShoham added this to the 5.1.17 milestone Jan 2, 2018
@GiladShoham GiladShoham self-assigned this Jan 2, 2018
@GiladShoham GiladShoham modified the milestones: 5.1.17, 12.1.17 Jan 4, 2018
GiladShoham added a commit that referenced this issue Jan 7, 2018
* Support yarn as package manager
Add package manager config to bit.json

* update change log
@GiladShoham GiladShoham removed the review label Jan 7, 2018
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.

1 participant