`npm prune --production` issue

Current Behavior

Currently the package setup is like this:

├── package-a
├── package-b
└── package-core

both package-a and package-b depends on package-core (which is also an unpublished package).

We did run npm prune --production per each package, otherwise the zip file is too big for lambda. But it ended up deleting the local dependency (package-core).

Expected Behavior

I wonder what would be the best way to use npm prune --production.

NOTE, I could not run npm install --production (as that local dependency package-core is managed thru lerna).

Possible Solution

Steps to Reproduce (for bugs)

1. lerna bootstrap
2. lerna exec – npm run build (rough command)
3. lerna exec – npm prune --production (rough command)

lerna.json

{
  "lerna": "3.16.1",
  "version": "independent",
  "packages": [
    "packages/*"
  ],
  "npmClient": "npm",
  "npmClientArgs": [
    "--no-lockfile"
  ],
  "useWorkspaces": false
}

Context

I am trying to shrink the package size with one local, unpublished, private dependency.

But when I run npm prune --production per package, the local dependency is gone.

Your Environment

Executable	Version
lerna --version	3.16.1
npm --version	6.4.1
yarn --version	VERSION
node --version	v8.16.0

OS	Version
macOS Mojave	10.14.5

[marcesengel]

When you had previously already installed your dependencies you can go for a lerna clean before doing lerna bootstrap -- --production - otherwise the extraneous dependencies will be kept.

[tristanHessell]

@chenrui333 Apologies to necropost, but in case you (or someone else) needs a potental solution.

npm prune --production --no-package-lock works to not remove packages that are not in the package-lock, which would be any hoisted or local dependencies.

However, the --no-package-lock option doesnt seem to be in the docs as a valid option for npm prune, so use it at your own risk.