Skip to content

[ Question ] publishConfig package.json object support not documented #733

Closed

Description

@michaelwarren1106

I went digging for a solution to only publish a certain folder, and I found in the code that changesets supports the publishConfig package.json object that tools like lerna use/support also, but its not documented anywhere.

I'm posting this issue just for awareness, but I also may send in a docs update PR if you'd be open to it!

Activity

  1. changed the title [-][ Question ] `changeset publish` config option for folder to publish[/-] [+][ Question ] `publishConfig` package.json object support not documented[/+] on Jan 11, 2022
  2. Andarist commented on Jan 11, 2022

    @Andarist
    Member

    I'm posting this issue just for awareness, but I also may send in a docs update PR if you'd be open to it!

    Definitely, we'd appreciate such PR :)

  3. slinkardbrandon commented on Jul 6, 2022

    @slinkardbrandon

    I was just researching trying to find this exact feature, couldn't find anything until actually digging into the code. I was also really curious about what all is going on here, this would be really useful to have documented for sure.

    I can open a PR to do some basic documentation once I figure everything out here but admittedly I don't follow everything going on with the publishConfig, I'll have to do a bit more digging.

  4. beeequeue commented on Jun 8, 2026

    @beeequeue
    Member

    we delegate packing (where publishConfig overrides are applied) and publishing to package managers, so support for publishConfig overrides depends on them.

    should we add a note somewhere in the new docs about this?

    as for publishConfig.registry specifically, the new docs mention it in various places, like here or here

  5. bluwy commented on Jun 8, 2026

    @bluwy
    Member

    It looks like it's an added support in Changesets since #428. So it works in like npm even if it doesn't support publishConfig.directory.

    So I think we have to document it, but I don't really like that Changesets is adding arbitrary support like this.

  6. added a commit that references this issue on Jun 30, 2026
    fef8c9c
  7. bluwy commented on Jun 30, 2026

    @bluwy
    Member

    This is documented on the site at fef8c9c now

  8. added a commit that references this issue on Jul 29, 2026
    1b9687f
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

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