nodulejs - npm Package Compare versions

Comparing version 1.1.17 to 1.1.21

package.json

 {
   "name": "nodulejs",
-  "version": "1.1.17",
-  "description": "Utility for discovering and initializing node/express 'nodules'",
+  "version": "1.1.21",
+  "description": "Scalable self-discovering web components",
   "main": "nodule.js",
@@ -9,2 +9,12 @@ "scripts": {
   },
+  "keywords": [
+    "nodule",
+    "yukon",
+    "express",
+    "scalable",
+    "self-discovering",
+    "framework",
+    "component-based",
+    "component-based framework"
+  ],
   "repository": {
@@ -11,0 +21,0 @@ "type": "git",

README.md

@@ -8,3 +8,3 @@ # nodulejs
 
-For a fully fleshed-out implementation of nodulejs, see the [yukon API framework](https://github.com/jackspaniel/yukon)).
+For a fully fleshed-out implementation of nodulejs, see the [yukon API framework](https://github.com/jackspaniel/yukon).
 
@@ -26,5 +26,5 @@ ## Installation
 
-1. __dirs__: <span style="color:grey">(OPTIONAL, default='/nodules')</span> *path(s) to look for your nodules, exclude property can be full or partal match* <br>__example:__ [{ path: '/app', exclude: ['demoApp.js', '.test.js', '/shared/'] }, { path: '/lib/nodules', exclude: ['.test.js'] }]
-2. __debugToConsole__: <span style="color:grey">(OPTIONAL, default=false)</span> *set to true to see nodulejs debug output in the console* 
-3. __customDebug__: <span style="color:grey">(OPTIONAL)</span> *custom debug function* <br>__example:__ function(identifier) { return function(msg){... your debug function here ...} }
+1. __dirs__: <span style="color:grey">(OPTIONAL, default='/nodules')</span> path(s) to look for your nodules, exclude property can be full or partal match <br>*__example:__ [{ path: '/app', exclude: ['demoApp.js', '.test.js', '/shared/'] }, { path: '/lib/nodules', exclude: ['.test.js'] }]*
+2. __debugToConsole__: <span style="color:grey">(OPTIONAL, default=false)</span> set to true to see nodulejs debug output in the console
+3. __customDebug__: <span style="color:grey">(OPTIONAL)</span> custom debug function <br>*__example:__ function(identifier) { return function(msg){... your debug function here ...} }*
 
@@ -39,6 +39,6 @@ ## What is a nodule?
 
-1. __route__: <span style="color:grey">(REQUIRED)</span> *one or more express routes - can be a string, RegExp, or array of either*
-2. __routeVerb__: <span style="color:grey">(OPTIONAL, default=get)</span> *get, post, put, del*
-3. __routeIndex__: <span style="color:grey">(OPTIONAL, default=0)</span> *use to load routes before or after others, can be negative, like z-index*
-4. __middlewares__:  <span style="color:grey">(OPTIONAL but your app isn't going to do much w/o them)</span> *an array of middleware functions to call for each nodule, or function(nodule) which returns said array. This array can be globally static for all modules, semi-global based on rules (by using the function option), or specified one-off within each nodule.*
+1. __route__: <span style="color:grey">(REQUIRED)</span> one or more express routes - can be a string, RegExp, or array of either
+2. __routeVerb__: <span style="color:grey">(OPTIONAL, default=get)</span> get, post, put, del
+3. __routeIndex__: <span style="color:grey">(OPTIONAL, default=0)</span> use to load routes before or after others, can be negative, like z-index
+4. __middlewares__:  <span style="color:grey">(OPTIONAL but your app isn't going to do much w/o them)</span> an array of middleware functions to call for each nodule, or function(nodule) which returns said array. This array can be globally static for all modules, semi-global based on rules (by using the function option), or specified one-off within each nodule.
 
@@ -50,3 +50,3 @@ ### Ok, what problem does this solve?
 
-From a __framework-development point of view__, we knew that as requirements evolved, we would constantly need to add default properties to each component, while hopefully causing as little disruption as possible to existing components. This is easily accomplished by adding a default property to the base config then specifying the property only in the nodules that need the new property.
+From a __framework-development point of view__, we knew that as requirements evolved, we would constantly need to add default properties to each component, while hopefully causing as little disruption as possible to existing components. This is easily accomplished by adding a default property to the base config, then specifying the property only in the nodules that need the new property.
 
@@ -53,0 +53,0 @@ We also knew we'd need to add slices of business logic globally or semi-globally at any point in the request chain. By keeping control of the middleware chain we are able to do this with ease.

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

16664

increased by0.85%

No dependency changes