Repository navigation
[feat] ability to replace npm publish #580
Description
Affected Packages
@changesets/cli
Problem
I'm using clean-publish to publish packages, but it is not configurable in changesets, both of the two will run npm publish inside which makes them incompatible.
Proposed solution
{
"publish": "npm run clean-publish"
}Reacted by lu-zen and Taylor Buchanan
Activity
Andarist commentedon May 1, 2021
We try to balance configurability with the lean core and I think this, unfortunately, lies outside of the area of our interests at the moment.
The problem is that we still expect certain things (like a proper stdout content) from the publish script and figuring out how to get that from a configurable publish is a design challenge (not impossible, but it would take time that we don't have for this).
iamayushdas commentedon May 6, 2021
I am new here can you guide me how to do it?
bluwy commentedon Aug 26, 2026
For now I think this is out of scope for the project. You might need to workaround by building a clean output in a subdirectory and use
publishConfig.directoryto publish that instead.Andarist commentedon Aug 26, 2026
That said,
changesets/action/publishcan be configured with a customscript. But to leverage that properly, it's advised to combine it withchangeset git-tag, like hereNote that this isn't a thoroughly tested workflow so you'd have to use this at your own risk.