No description
Find a file
2020-02-19 18:11:20 +01:00
modules export console width & height 2020-02-19 18:11:13 +01:00
test Sample package.json to test on 2020-02-19 17:10:57 +01:00
.gitattributes Initial commit 2020-02-19 16:33:30 +01:00
.gitignore Initial commit 2020-02-19 16:33:30 +01:00
bpm.bat Fix to work everywhere 2020-02-19 17:45:29 +01:00
index.js Add view alias 2020-02-19 18:11:20 +01:00
LICENSE Initial commit 2020-02-19 16:33:30 +01:00
README.md Sample readme 2020-02-19 16:56:32 +01:00

bpm

Better package manager.

BPM is NOT ready to use, please wait until using it in production until stable version is released

Manages your packages more easily, is way faster than any other available package manager and most importanly, saves space for your projects.

Why?

NPM (node package manager) and others always use folder node_modules in the projects directory. This is to always use the version the package specifies, but it also means that it uses much more space than it needs - even same versions are installed duplicately.

BPM on the other hand, stores all packages in one place and also saves a file to mention which projects are actively using the package. If all projects remove the dependency, then it's simply removed from the disk to save space.

This means, that it can save much space - some apps use same depndencies and same versions, so they will be merged.