Description
When publishing my library, the version is set on the top-level package.json, not the project's package.json. Am I not supposed to be running this from the root of the package? The top-level package.json has "private": true on it.
Steps to reproduce
- yarn build (builds
./projects/my-moduleand writes to./distdirectory) - yarn ng publish patch
It seems to be publishing the dist folder, but the version change applies to the wrong package.json file.
It's also thus setting the new version after having built the library and writing to dist, so what gets written up into npm doesn't have the correct version.
Expected behavior
I would expect the publish command to update the version, then build, then publish.
Environment
np - 7.6.2
Node.js - 16.16.0
yarn - 1.1.25
Git - 2.37.0.windows.1
OS - Windows 10
How does funding with Polar work?
Pay now to fund the work behind this issue.
Get updates on progress being made.
Maintainer is rewarded once the issue is completed.
Backer
You're funding impactful open source efforts
Contributor
You want to contribute to this effort
Maintainer
You want to get funding like this too