Migrate from Bower to Yarn

Description

Bower is deprecated, and they are starting to throw 410 errors to warn developers to migrate. Bower is recommending Yarn, but after consideration, it makes more sense to switch to just using NPM. We decided to go with yarn for now so that we can use our existing grunt scripts

Acceptance Criteria

  • Any current NPM dependencies need to be changed to NPM dev-dependencies

  • All bower dependencies and overwrites need to be saved as Yarn dependencies (not dev dependencies)

  • Dev-UI build tasks are updated to pull dependency list from Yarn dependencies (not dev dependencies)

Activity

Show:
Łukasz Lewczyński
November 23, 2017, 1:45 AM

What we should do if there some libraries are present in bower but not in the npm? We think we in those cases we should find alternatives and modified the code. Also we think most of libraries should be present in the npm.

cc:

Nick Reid
November 23, 2017, 9:52 AM

If a package doesn't exist in NPM but not in Bower:

  • please not the package on this ticket (and let me know

  • You can give NPM a link that it will download, so figure out where the Bower package actually lives (github probably) and pass that link to NPM

CC

Done

Assignee

Jakub Kondrat

Reporter

Nick Reid

Labels

Story Points

5

Time tracking

0m

Time remaining

1h

Components

Sprint

None

Fix versions

Priority

Major