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

Move from bower to yarn #29906

Closed
DeepDiver1975 opened this issue Dec 19, 2017 · 4 comments
Closed

Move from bower to yarn #29906

DeepDiver1975 opened this issue Dec 19, 2017 · 4 comments
Assignees
@PVince81
Labels
dependencies technical debt
Milestone
10.0.5

Comments

@DeepDiver1975
Copy link
Member

Bower is dead - long live yarn
@DeepDiver1975 DeepDiver1975 added this to the development milestone Dec 19, 2017
@PVince81
Copy link
Contributor

PVince81 commented Dec 19, 2017 •
edited
Loading

seems yarn also uses package.json https://bower.io/blog/2017/how-to-migrate-away-from-bower

Last line says "But initially, the only change required in code is to change any reference to bower_components with node_modules/@bower_components (though you can link it somewhere else in postinstall script)."
Our bower_components is core/vendor
If symlinking is ok we could symlink the folder to there

@PVince81
Copy link
Contributor

adding @felixheidecke for a second opinion

@PVince81 PVince81 mentioned this issue Dec 19, 2017
Merged
5 tasks
@PVince81
Copy link
Contributor

PR #29908

@ownclouders ownclouders mentioned this issue Jul 3, 2018
Closed
@PVince81 PVince81 mentioned this issue Nov 26, 2018
Closed
@PVince81
Copy link
Contributor

lets also do it for stable10: #33651

@lock lock bot locked as resolved and limited conversation to collaborators Nov 26, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@PVince81 PVince81

Labels
dependencies technical debt
Projects
None yet
Milestone
10.0.5
Development

No branches or pull requests
2 participants
@PVince81 @DeepDiver1975