Tooling to help developers use the correct yarn version

Description

The server build uses a specific version of yarn and node. We should try to get tooling in place to help ensure developers are using the same yarn version as the build. We have nvm available for setting the node version, but nothing yet for yarn.

Activity

Show:

Sean Flanigan 4 August 2017 at 02:04

The maven-frontend-plugin does use a specific version of yarn (from the system property yarn.version). If we find a pure-JS tool for managing this, we should ensure that it and maven-frontend-plugin get the version number from the same place (eg parsing the same properties file or something).

Ready for Release

Details

Assignee

Reporter

Labels

Tested Version/s

Story Points

Components

Sprint

Fix versions

Priority

More fields

Created 3 August 2017 at 23:58
Updated 27 June 2018 at 02:15
Resolved 8 September 2017 at 02:03

Flag notifications