ERR_PNPM_INCLUDED_DEPS_CONFLICT started occurring in 7.0.1

[BeeeQueue]

I looked into the code for this, and it doesn't seem like there have been any changes in the file that contains the code for the error, so I'm very confused why it started erroring now.

It would at least be nice with an option to disable it as many workflows are blocked by it, such as webpack applications which need webpack installed (a devDep) and then build with NODE_ENV=production pnpm webpack

pnpm version: 7.0.1

Code to reproduce the issue:

1. Create project with dev- and normal dependencies
2. Run NODE_ENV=development pnpm i
3. Run NODE_ENV=production pnpm [script]

Expected behavior:

In previous versions this worked

Actual behavior:

Errors with ERR_PNPM_INCLUDED_DEPS_CONFLICT.

Additional information:

• node -v prints: 14.19.1
• Windows, macOS, or Linux?: macOS

[BeeeQueue]

This has nothing to do with peer dependencies. It's about running scripts in a different environment than they were installed with, leading to the error:

modules directory (at "...") was installed with dependencies, devDependencies. Current install wants dependencies

[zkochan]

Sorry, I have misread that error code.

I see, this should be fixed. This error shouldn't happen when a script is executed.

[lloydjatkinson]

Happening again in latest version of pnpm

[fantun3s]

This one is happening to me as well in a pnpm monorepo:
pnpm: 7.27.0
node: 16.19.0
os: macOS Ventura 13.2.1

[BeeeQueue]

I have not encountered this since I reported it.

[sandervspl]

I have just encountered this just now in a pnpm monorepo trying to run pnpm dlx astro add tailwind using pnpm v8.9.2

ERR_PNPM_INCLUDED_DEPS_CONFLICT  modules directory (at "/Users/......") was installed with optionalDependencies, dependencies, devDependencies. Current install wants optionalDependencies, dependencies.