Closed MaximBalaganskiy closed 4 years ago
@EisenbergEffect at the moment, dependencies are specified as peer deps. This is to combat an issue where users would have duplicated version of a modules. Though this makes lerna skip updating dependencies of packages, as it ignore peers section.
Do you see any issues with hooking into prepublishOnly
? Description:
prepublishOnly: Run BEFORE the package is prepared and packed, ONLY on npm publish. (See below.)
No objections from me.
@MaximBalaganskiy is there any other hook that let us have "what you see in git is what you get in npm"? As I understand that this will modify package.json, but won't create a commit for git.
version
hook suits better - it's run right before the commit
The description of version
commands from https://docs.npmjs.com/misc/scripts. If we want t enhance this more, maybe use some more from lerna and https://docs.npmjs.com/cli/version.html
preversion: Run BEFORE bumping the package version.
version: Run AFTER bumping the package version, but BEFORE commit.
postversion: Run AFTER bumping the package version, and AFTER commit.
Looks suitable for this to me. Thanks @MaximBalaganskiy
Lerna ignores
peerDependencies
completely whilst they need to be in line withdevDependencies
.Also, add missing modules to
components