I do feel that pnpm config get and pnpm config set are still incomplete. Especially now that pnpm has expand its config structure to more nested objects.

pnpm config get can get an object, but not the property of that object. Perhaps we could make pnpm config get packageExtensions react dependencies to access config.packageExtensions.react.dependencies? Or perhaps we should make pnpm config get ignores pnpm-workspace.yaml entirely?

Yes, probably we should support that. But I think the field names should be separated by dots:

pnpm config get packageExtensions.react.dependencies

Yes, probably we should support that. But I think the field names should be separated by dots

jq does that. And looks good too. The problem is how are we suppose to escape dots in property name? Do we make another property path parser similar to jq? Is there an existing library for that?

And escaping is necessary because dependency names can contain all kinds of symbols: @, /, ., etc.

See how Yarn also supports this: https://yarnpkg.com/cli/config/set

We can check what library Yarn uses. It should be something small.

I don't see any usage of the new library in config get/set

I don't see any usage of the new library in config get/set

It's WIP. I haven't glued them together yet. But doing so should be easy.

Discovered flaws

• pnpm config get _authToken would emit an error from npm, but pnpm config list shows it regardless.
• pnpm config set <npm-setting> would write to ~/.npmrc despite local pnpm-workspace.yaml exist.