If you are working on two npm packages, on of which depends on the other (say B depends on A), what is your process for making changes to A and trying them out on B without npm publish?
So far the best I’ve found is changing the package specifier to point to the local repo + npm install but there must be something faster and less error-prone? (so many times I forgot to change it back and committed the package.json with the local specifier!)
Lea Verou /
npub1m6…pyan3
2024-03-13 13:19:09
Author Public Key
npub1m6e8q4lxpwxhjcczsjfsnf79g24pcuvppzlysycgdh40jyualamqapyan3Published at
2024-03-13 13:19:09Event JSON
{
"id": "e548cc88e9829b1d744423b926ceeddebee596b655f0f77dc4bcaea83d82990c",
"pubkey": "deb27057e60b8d796302849309a7c542aa1c718108be4813086deaf9139dff76",
"created_at": 1710335949,
"kind": 1,
"tags": [
[
"proxy",
"https://front-end.social/users/leaverou/statuses/112088576791955683",
"activitypub"
]
],
"content": "If you are working on two npm packages, on of which depends on the other (say B depends on A), what is your process for making changes to A and trying them out on B without npm publish?\n\nSo far the best I’ve found is changing the package specifier to point to the local repo + npm install but there must be something faster and less error-prone? (so many times I forgot to change it back and committed the package.json with the local specifier!)",
"sig": "da7ef7632e2a06b003c49e244b1bbe76354c1ce6aea46558117d3e704e188b7fe045f118abbcacfe7930e01167d78b41571292d8d64269c5d7a397f6fbfa95ee"
}