plexiform - npm Package Compare versions

Comparing version 1.3.0 to 1.3.1

bin/plexiform.js

@@ -22,3 +22,3 @@ #!/usr/bin/env node
     name: "Plexiform",
-    version: "1.3.0",
+    version: "1.3.1",
     author: "Raith"
@@ -172,3 +172,3 @@ };
     if (!fs.existsSync(plexiformconfigname) || opt_force_overwrite) {
-        let configcontent = '{\n\t"build_name": "./path/to/build_name_without_js_extension",\n\t"config_name": "./path/to/config_name_without_json_extension)",\n\t"output_folder": "./path/to/output_folder/"\n}\n';
+        let configcontent = '{\n\t"build_name": "./path/to/build_module.js",\n\t"config_name": "./path/to/config_file.json",\n\t"output_folder": "./path/to/output_folder/"\n}\n';
         fs.outputFileSync(plexiformconfigname, configcontent);
@@ -200,3 +200,3 @@ } else {
         try {
-            build = require(`${build_name}.js`).build;
+            build = require(build_name).build;
         } catch (e) {
@@ -207,3 +207,3 @@ console.log(`ERROR! Cannot find build file "${build_name}" to require.`);
         try {
-            config = require(`${config_name}.json`);
+            config = require(config_name);
         } catch (e) {
@@ -210,0 +210,0 @@ console.log(`ERROR! Cannot find config file "${config_name}" to require.`);

package.json

 {
   "name": "plexiform",
-  "version": "1.3.0",
+  "version": "1.3.1",
   "description": "A very simple template-driven generator.",
@@ -5,0 +5,0 @@ "main": "bin/plexiform.js",

README.md

 # Plexiform
 
-> **v1.3.0**
+> **v1.3.1**
 
@@ -60,1 +60,2 @@ | In this document |
 | 2017-09-03 | v1.3.0 | Raith | Utilises process-argv and changed to explicit command line arguments rather than positional parameters |
+| 2017-09-03 | v1.3.1 | Raith | No more assumption about file extensions. Now need to specify them for build and config |

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

Dynamic require

Supply chain risk

Dynamic require can indicate the package is performing dangerous or unsafe dynamic code execution.

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

Dynamic require

Supply chain risk

Dynamic require can indicate the package is performing dangerous or unsafe dynamic code execution.

Found 1 instance in 1 package

Improved metrics

Total package byte prevSize

17771

increased by0.4%

Number of lines in readme file

61

increased by1.67%

No dependency changes