node-containerpattern
Advanced tools
Comparing version 1.6.0 to 1.7.0
{ | ||
"name": "node-containerpattern", | ||
"version": "1.6.0", | ||
"version": "1.7.0", | ||
"description": "A 'Container pattern' object for a clean global use of data.", | ||
"main": "lib/main.js", | ||
"typings": "lib/index.d.ts", | ||
"type": "commonjs", | ||
"typings": "./lib/cjs/main.d.cts", | ||
"main": "./lib/cjs/main.cjs", | ||
"exports": { | ||
".": { | ||
"require": { | ||
"types": "./lib/cjs/main.d.cts", | ||
"default": "./lib/cjs/main.cjs" | ||
} | ||
} | ||
}, | ||
"scripts": { | ||
"lint": "npx eslint ./lib/**/*.js ./test/**/*.js", | ||
"check-updates": "npx check-version-modules", | ||
"unit-tests": "npx nyc --reporter=html --reporter=text mocha", | ||
"tests": "npm run-script lint && npm run-script check-updates && npm run-script unit-tests", | ||
"compile": "npx tsc --project \"./tsconfig-cjs.json\"", | ||
"unit-tests": "npm run compile && npx nyc --reporter=html --reporter=text mocha", | ||
"tests": "npm run-script check-updates && npm run-script unit-tests", | ||
"ci": "npm run-script tests && npx nyc report --reporter=text-lcov | coveralls" | ||
}, | ||
"files": [ | ||
"/lib" | ||
], | ||
"husky": { | ||
"hooks": { | ||
"pre-commit": "npm run-script lint", | ||
"pre-push": "npm run-script tests" | ||
@@ -47,10 +64,10 @@ } | ||
"devDependencies": { | ||
"@types/node": "17.0.35", | ||
"@types/node": "18.0.0", | ||
"check-version-modules": "1.3.5", | ||
"coveralls": "3.1.1", | ||
"eslint": "8.16.0", | ||
"fs-extra": "10.1.0", | ||
"husky": "8.0.1", | ||
"mocha": "10.0.0", | ||
"nyc": "15.1.0", | ||
"typescript": "4.6.4" | ||
"typescript": "4.7.4" | ||
}, | ||
@@ -57,0 +74,0 @@ "homepage": "https://github.com/Psychopoulet/node-containerpattern#readme", |
Major refactor
Supply chain riskPackage has recently undergone a major refactor. It may be unstable or indicate significant internal changes. Use caution when updating to versions that include significant changes.
Found 1 instance in 1 package
Dynamic require
Supply chain riskDynamic require can indicate the package is performing dangerous or unsafe dynamic code execution.
Found 1 instance in 1 package
43215
27
888
0
2