internal: ensure the regeneration of package-lock.json does not affect future releases

Author: iOvergaard

lerna.json

@@ -3,6 +3,7 @@
   "version": "independent",
   "npmClient": "npm",
   "useWorkspaces": true,
+  "granularPathspec": false,
   "command": {
     "publish": {
       "verifyAccess": false
@@ -17,6 +18,8 @@
     ".storybook/**/*",
     "storyhelpers/**/*",
     "templates/**/*",
-    "docs/**/*"
+    "docs/**/*",
+    "package.json",
+    "package-lock.json"
   ]
 }

package.json

@@ -37,7 +37,8 @@
     "build:prod": "npm run clean && npm run build",
     "clean": "turbo run clean --parallel",
     "lerna:publish": "npm run build:prod && npm whoami && lerna publish from-package --yes",
-    "lerna:version": "lerna version --no-push --exact --conventional-commits && rimraf package-lock.json && npm i",
+    "lerna:version": "lerna version --no-push --exact --conventional-commits",
+    "postversion": "rimraf package-lock.json && npm i",
     "lerna:diff": "lerna diff",
     "lerna:fix": "lerna exec -- node ../../scripts/lerna-fix.mjs",
     "lerna:modify-package": "lerna exec -- node ../../scripts/modify-pkgjson.mjs",