Comparing version 1.4.1 to 1.4.2
{ | ||
"name": "nodulejs", | ||
"version": "1.4.1", | ||
"version": "1.4.2", | ||
"description": "Scalable self-discovering web components", | ||
@@ -5,0 +5,0 @@ "main": "nodule.js", |
@@ -53,3 +53,3 @@ # nodulejs | ||
Conversely a nodule's route is not tied to its filename or path. We feel this is the best of both worlds as files can be renamed and moved w/o impacting the back end or front end code. Developers are more likely to rename and reorganize files - which results in tigher, more self-explanatory code. Each nodule is roughly 1-1 with a web route (although it can serve multiple routes). Our experience is that in large distributed teams, this separation of features into bite-size files aids development considerably. | ||
Conversely a nodule's route is not tied to its filename or path. We feel this is the best of both worlds - as files can be renamed and moved w/o impacting the back end or front end code. Developers are more likely to rename and reorganize files - which results in tigher, more self-explanatory code. Each nodule is roughly 1-1 with a web route (although it can serve multiple routes). Our experience is that in large distributed teams, this separation of features into bite-sized files aids development considerably. | ||
@@ -56,0 +56,0 @@ ## Installation |
License Policy Violation
LicenseThis package is not allowed per your license policy. Review the package's license to ensure compliance.
Found 1 instance in 1 package
License Policy Violation
LicenseThis package is not allowed per your license policy. Review the package's license to ensure compliance.
Found 1 instance in 1 package
19096