custom-require - npm Package Compare versions

Comparing version 0.0.1 to 0.0.2

package.json

@@ -13,4 +13,4 @@ {
     "module",
-	"custom",
-	"function"
+    "custom",
+    "function"
   ],
@@ -24,3 +24,3 @@ "license": "MIT",
   },
-  "version": "0.0.1"
-}
+  "version": "0.0.2"
+}

README.md

@@ -5,2 +5,6 @@ # Custom Require
 
+## Installation
+
+`npm install custom-require`
+
 ## Usage
@@ -42,3 +46,4 @@
 
-// Requiring modules already required by another instance will not be a problem. Second walker will receive all the dependencies too
+// Requiring modules already required by another instance will not be a problem
+// Second walker will receive all the dependencies too
 secondWalker.require("./test");
@@ -65,2 +70,4 @@ ```
 ```
-Custom Require will be only able to track modules loaded after it has been required for the first time, so is recommendable to require it at the top of the entry-point file. Is not needed to add it to each file. Only at the entry-point.
+Custom Require will be only able to track modules loaded after it has been required for the first time, so is recommendable to require it at the top of the entry-point file. Is not needed to add it to each file. Only at the entry-point.
+
+NOTE: Custom Require will start tracking right after requiring it. Is not necessary to immediatly create an instance.

New alerts

License Policy Violation

License

This package is not allowed per your license policy. Review the package's license to ensure compliance.

Found 1 instance in 1 package

Fixed alerts

License Policy Violation

License

This package is not allowed per your license policy. Review the package's license to ensure compliance.

Found 1 instance in 1 package

Improved metrics

Total package byte prevSize

7379

increased by2.2%

Number of lines in readme file

70

increased by11.11%

No dependency changes