Skip to content

Correct checkNonRootProjectManifest: Remove pnpm, check for its sub fields other than pnpm.executionEnv #8413

@KSXGitHub

Description

@KSXGitHub

Verify latest release

  • I verified that the issue exists in the latest pnpm release

pnpm version

No response

Which area(s) of pnpm are affected? (leave empty if unsure)

No response

Link to the code that reproduces this issue or a replay of the bug

No response

Reproduction steps

Set pnpm.executionEnv in a member of a pnpm monorepo then run pnpm run.

Describe the Bug

It wrongly warns that the field "pnpm" will not take effect even though it does.

Expected Behavior

Doesn't warn for "pnpm" itself, only its global sub fields that aren't "executionEnv"

Which Node.js version are you using?

irrelevant

Which operating systems have you used?

  • macOS
  • Windows
  • Linux

If your OS is a Linux based, which one it is? (Include the version if relevant)

irrelevant

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions