@flybywiresim/igniter - npm Package Compare versions

Comparing version 1.0.0 to 1.1.0

package.json

 {
   "name": "@flybywiresim/igniter",
-  "version": "1.0.0",
+  "version": "1.1.0",
   "description": "An intelligent task runner written in Typescript.",
@@ -10,3 +10,3 @@ "repository": {
   "author": "Theodore Messinezis",
-  "main": "dist/library.mjs",
+  "main": "dist/index.mjs",
   "scripts": {
@@ -19,8 +19,11 @@ "build": "rollup -c",
     "@rollup/plugin-commonjs": "^17.1.0",
+    "@rollup/plugin-json": "^4.1.0",
     "@rollup/plugin-node-resolve": "^11.2.0",
     "@rollup/plugin-typescript": "^8.2.0",
     "@types/jest": "^26.0.20",
-    "@types/minimist": "^1.2.1",
     "@types/mkdirp": "^1.0.1",
     "@typescript-eslint/eslint-plugin": "^4.15.0",
+    "@wessberg/rollup-plugin-ts": "^1.3.8",
+    "chalk": "^4.1.0",
+    "commander": "^7.1.0",
     "eslint": "^7.20.0",
@@ -32,3 +35,2 @@ "eslint-config-airbnb-typescript": "^12.3.1",
     "jest": "^26.6.3",
-    "minimist": "^1.2.5",
     "mkdirp": "^1.0.4",
@@ -35,0 +37,0 @@ "reflect-metadata": "^0.1.13",

readme.md

@@ -1,34 +0,21 @@
-Run all steps with cache hash checking.
 ```
-./igniter
+npx igniter
 ```
 
-Run all steps, ignoring cache hash checking, still generate a cache.
 ```
-./igniter --force
+npx igniter --help
 ```
 
-Run all steps, ignoring cache hash checking, do not generate a cache.
 ```
-./igniter --no-cache
-```
+Usage: igniter [options]
 
-Run tasks whos names match "instruments" using regex.
+Options:
+  -V, --version            output the version number
+  -c, --config <filename>  set the configuration file name (default: "igniter.config.mjs")
+  -r, --regex <regex>      regular expression used to filter tasks
+  -i, --invert             if true, regex will be used to reject tasks
+  --no-cache               do not skip tasks, even if hash matches cache
+  -d, --dry-run            skip all tasks to show configuration
+  --debug                  stop when an exception is thrown and show trace
+  -h, --help               display help for command
 ```
-./igniter instruments
-```
-
-Run tasks whos names match "instruments" or "manifest" using regex.
-```
-./igniter "instruments|manifest"
-```
-
-Regex step matching and flags can be used together like this:
-```
-./igniter --no-cache -- "instruments|manifest"
-```
-
-or like this:
-```
-./igniter "behaviors|manifest" --force
-```

Fixed alerts

Uses eval

Supply chain risk

Package uses dynamic code execution (e.g., eval()), which is a dangerous practice. This can prevent the code from running in certain environments and increases the risk that the code may contain exploits or malicious behavior.

Found 1 instance in 1 package

Environment variable access

Supply chain risk

Package accesses environment variables, which may be a sign of credential stuffing or data theft.

Found 2 instances in 1 package

Improved metrics

Total package byte prevSize

151909

increased by37.15%

Lines of code

4712

increased by73.68%

Number of low supply chain risk alerts

4

decreased by-20%

Worsened metrics

Dev dependency count

24

increased by9.09%

Number of lines in readme file

22

decreased by-37.14%

No dependency changes