Linux premium71.web-hosting.com 4.18.0-513.11.1.lve.el8.x86_64 #1 SMP Thu Jan 18 16:21:02 UTC 2024 x86_64
LiteSpeed
Server IP : 198.187.29.8 & Your IP : 18.190.25.53
Domains :
Cant Read [ /etc/named.conf ]
User : cleahvkv
Terminal
Auto Root
Create File
Create Folder
Localroot Suggester
Backdoor Destroyer
Readme
/
lib /
node_modules /
npm /
node_modules /
lock-verify /
Delete
Unzip
Name
Size
Permission
Date
Action
LICENSE
752
B
-rw-r--r--
2021-03-10 14:36
README.md
703
B
-rw-r--r--
2021-03-10 14:36
index.js
2.87
KB
-rw-r--r--
2021-03-10 14:36
package.json
1.6
KB
-rw-r--r--
2021-03-10 14:36
Save
Rename
# lock-verify Report if your package.json is out of sync with your package-lock.json. ## USAGE ``` const lockVerify = require('lock-verify') lockVerify(moduleDir).then(result => { result.warnings.forEach(w => console.error('Warning:', w)) if (!result.status) { result.errors.forEach(e => console.error(e)) process.exit(1) } }) ``` As a library it's a function that takes the path to a module and returns a promise that resolves to an object with `.status`, `.warnings` and `.errors` properties. The first will be true if everything was ok (though warnings may exist). If there's no `package.json` or no lockfile in `moduleDir` or they're unreadable then the promise will be rejected.