fix(web-styles): publish the dist
subdirectory
#152
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes the release workflow, which currently fails for the
web-styles
package because the publish command targets thedist
folder, anddist/package.json
points to/dist/dist
, a directory that doesn't exist. Haven't looked into why looking for apackage.json
file indist/dist
doesn't produce an error, but transformingdist/package.json
should fix the issue.I have tried it out locally against
verdaccio
andchangeset publish
worked as expected. Feel free to close the PR if you have different plans for fixing the issue, I'm more interested in letting you know what went wrong.Why only
web-styles
?Not 100% sure as to why
swisspost-intranet-header
doesn't have the same issue, but my guess is:https://github.com/swisspost/common-web-frontend/blob/9203419db831f4eca3fca92b3f6b55194e0701e4/packages/angular-components/projects/swisspost-intranet-header/package.json#L9
When the
publish
command runs indist/swisspost-intranet-header
, it will end up pointing to the current directory, meaning that the relative path ends up being correct.Context
I had a similar issue as the one described in changesets/action#191 (in my case, the failure was TypeScript compilation errors).
The difference is that mine would be fixable by changesets/changesets#844, because
pnpm
does redirect compilation errors tostdout
by default (can be overridden byuse-stderr
in.npmrc
).