chore: use yarn workspaces

To prepare removing lerna, keep lerna but enable workspaces. All lerna alternatives (changesets, rush) rely on workspaces. yarn hoists all dependencies to the root node_modules with a single yarn.lock. Install and testing is much faster. The issue with hoisting might cause phantom dependencies (a package is able to import packages not in their own `package.json`).
cssnano · May 25, 2021 · 70332cb · 70332cb
1 parent d593565
commit 70332cb
Show file tree

Hide file tree

Showing 41 changed files with 418 additions and 2,753 deletions.
diff --git a/lerna.json b/lerna.json
@@ -1,5 +1,6 @@
 {
   "npmClient": "yarn",
+  "useWorkspaces": true,
   "command": {
     "publish": {
       "ignoreChanges": ["yarn.lock"]

diff --git a/package.json b/package.json
@@ -17,6 +17,7 @@
     "deploy": "cd site && GIT_USER=anikethsaha yarn deploy",
     "publish": "lerna publish"
   },
+  "workspaces": ["./packages/*"],
   "engines": {
     "node": "^10 || ^12 || >=14"
   },

diff --git a/packages/css-size/yarn.lock b/packages/css-size/yarn.lock
diff --git a/packages/cssnano-preset-advanced/yarn.lock b/packages/cssnano-preset-advanced/yarn.lock
diff --git a/packages/cssnano-preset-default/yarn.lock b/packages/cssnano-preset-default/yarn.lock
diff --git a/packages/cssnano-preset-lite/yarn.lock b/packages/cssnano-preset-lite/yarn.lock
diff --git a/packages/cssnano-utils/yarn.lock b/packages/cssnano-utils/yarn.lock