Is there an option to exclude a package?

[chmac]

In an old nodejs project, I automatically get +yarnpkg.com added, but I manually added +classic.yarnpkg.com. However, I end up with a conflict. I have both versions of yarn installed, and the latest is the one that gets run from yarn. Can I somehow exclude that package from being picked up by pkgx?

[jhheider]

You can do env -yarnpkg.com to remove it. As currently constituted:

https://github.com/pkgxdev/pkgx/blob/f28d9311eac07c0dd0b4c3900eab2420199b6604/src/utils/devenv.ts#L76-L86

.yarnrc brings in v1, and yarn.lock and .yarnrc.yml bring in berry.

[chmac]

The - trick is neat, I didn't know about it, thanks a lot.

In this old project I have a yarn.lock, so I'm getting yarnpkg.com. When I try adding "pkgx": "-yarnpkg.com" to my package.json then I get the following error:

dev
× nothing provides: -yarnpkg.com
│ we haven’t pkgd this yet. can you?
╰─➤ https://docs.pkgx.sh/pantry

But without it, I get the yarnpkg.com package loaded. Is there a way round this, or am I making another mistake here somewhere?

[jhheider]

I don't believe you can do it in a spec file. Only manually, using the env shell function created by the dev instance.

I believe ordering should be maintained, so if you put both in you spec file with classic first, that should get you what you want.

[chmac]

@jhheider That's awesome, thanks a lot. You're absolutely right, ordering does fix the issue I'm facing. 🥳 Would be awesome if -foo worked in spec files also, but I'm totally satisfied with the workaround.

Thanks again for working on pkgx and for all the help you've given me, I really appreciate it. 🧡