docs(): updating readme.md #31
Conversation
| @@ -24,12 +24,69 @@ $ npm install morose -g | |||
| morose | |||
| ``` | |||
|
|
|||
| ### Setting up npm config to use morose | |||
| ### Setting up npm config in client to use morose | |||
|
|
|||
| ```sh | |||
| npm set registry http://localhost:10000 | |||
| ``` | |||
|
|
|||
There was a problem hiding this comment.
Use cases
- Use private packages.
If you want to use all benefits of npm package system in your company without sending all code to the public, and use your private packages just as easy as public ones.
See using private packages section for details.
- Cache npmjs.org registry.
If you have more than one server you want to install packages on, you might want to use this to decrease latency (presumably "slow" npmjs.org will be connected to only once per package/version) and provide limited failover (if npmjs.org is down, we might still find something useful in the cache).
See using public packages section for details.
- Override public packages.
If you want to use a modified version of some 3rd-party package (for example, you found a bug, but maintainer didn't accept pull request yet), you can publish your version locally under the same name.
See override public packages section for details.
|
@irmana can you please check this one also when have time |
Let's discuss here about changes in our readme so it will be more attractive for visitors...