While developing a TypeScript library that is being used as a dependency by other libraries or applications, what options do I have for propagating frequent changes in the library? Is there a way to achieve it without constantly incrementing the library version, publishing it to an NPM registry, and then updating the application that depends on it?

Coming from a server-side development background, I feel like I'm repeating these 3 steps way too often...

I would expect to be able to develop a library and use it immediately as a dependency in another project without being connected to a remote registry that requires an internet connection. It can easily be done in other languages like Java, Go, and Scala, not to mention others like PHP and Python.

The example I gave here with a single library is simplified of course. This issue quickly becomes a nightmare in the real world when you have a tree consisting of many dependencies.

CodePudding user response：

You can use npm link to develop locally until you have a stable version. https://docs.npmjs.com/cli/v8/commands/npm-link