Skip to content

Latest version 18.1.0 overwriting pnpm-workspace.yaml #1540

@zhm

Description

@zhm

I see there was support added for pnpm workspaces, which is awesome. A couple behaviors that were unexpected for me:

  • It overwrites pnpm-workspace.yaml and I end up with a pnpm-workspace.yaml that's actually a JSON file. Is this intentional?
  • It doesn't seem to respect "named catalogs".

Example, I have this at the bottom of my pnpm-workspace.yaml for an expo/mobile project where I want these dependencies. In package.json I use catalog:mobile, and other projects like the web app I just use catalog:.

catalogs:
  mobile:
    query-string: 7.1.3
    tailwindcss: ^3.4.17

But it upgrades those dependencies anyways. (e.g. upgrades tailwind to v4)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions