[zanata/zanata-platform] 7c693b: chore: prevent yarn.lock getting out of sync with ...
GitHub
noreply at github.com
Thu Aug 31 05:59:43 UTC 2017
Branch: refs/heads/damason/yarn-frozen-lockfile
Home: https://github.com/zanata/zanata-platform
Commit: 7c693b9662ba0237e715f7f2c53e0b6891d0496c
https://github.com/zanata/zanata-platform/commit/7c693b9662ba0237e715f7f2c53e0b6891d0496c
Author: David Mason <drdmason at gmail.com>
Date: 2017-08-31 (Thu, 31 Aug 2017)
Changed paths:
M server/zanata-frontend/src/frontend/.yarnrc
Log Message:
-----------
chore: prevent yarn.lock getting out of sync with package.json
This just causes `yarn` or `yarn install` to fail when dependencies are
added just in package.json (manually or with `npm install --save`).
Commit: 404b078cab8e8a26f40f3eb8c3df9cad8772a743
https://github.com/zanata/zanata-platform/commit/404b078cab8e8a26f40f3eb8c3df9cad8772a743
Author: David Mason <drdmason at gmail.com>
Date: 2017-08-31 (Thu, 31 Aug 2017)
Changed paths:
M server/zanata-frontend/src/frontend/package.json
M server/zanata-frontend/src/frontend/yarn.lock
Log Message:
-----------
chore(frontend): fix broken build due to dependencies in package.json only
The build now correctly fails when dependencies in package.json are missing
from yarn.lock (meaning they were not installed with yarn - we want all
packages in frontend installed with yarn).
This also removes yarn as an explicit dependency. Yarn should be installed
globally with `npm install -g yarn` instead.
Compare: https://github.com/zanata/zanata-platform/compare/7c693b9662ba^...404b078cab8e
More information about the zanata-commits
mailing list