From 2f73b81a132264f4c8df08d69cafc03bc292ddd1 Mon Sep 17 00:00:00 2001 From: danbulant Date: Wed, 19 Feb 2020 20:27:05 +0100 Subject: [PATCH] Add some helping notes --- README.md | 11 ++++++++++- 1 file changed, 10 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index 6148316..0e26377 100644 --- a/README.md +++ b/README.md @@ -15,6 +15,10 @@ BPM on the other hand, stores all packages in one place and also saves a file to This means, that it can save much space - some apps use same depndencies and same versions, so they will be merged. +## BPM create node_modules. Is it normal? + +Yes! Because of how node works, BPM needs to create the directory, but instead of pasting the dependencies there, it creates a symlink pointing to the actual version. + ## Commands BPM is aimed to fully **replace** NPM, *but*, as of now, it cannot. @@ -24,4 +28,9 @@ Currently supported and working commands are: * `view` (alias get, info) - Gets information about current project or given package from NPM's registry * `bin` - Shows installation path of BPM * `ping` - Does HTTP ping to NPM's registry. Note this is different from NPM ping, so it cannot be compared. -* `init` - Creates a default `package.json` in current working directory. \ No newline at end of file +* `init` - Creates a default `package.json` in current working directory. + + +## Hide package.json warnings + +Use the flag `--supressChecking` or `-sch` for short. \ No newline at end of file