$ npm install valid-directory
Check whether or not a directory and its descendants are valid
Validity determined via the valid-filename
package.
npm install --global valid-directory
valid-directory
npm install --save valid-directory
npx valid-directory
require('valid-directory')
This package is published with the following editions:
valid-directory
aliases valid-directory/source/index.js
valid-directory/source/index.js
is esnext source code with require for modulesEnvironments older than Node.js v8 may need Babel's Polyfill or something similar.
This project provides its type information via inline JSDoc Comments. To make use of this in TypeScript, set your maxNodeModuleJsDepth
compiler option to 5
or thereabouts. You can accomlish this via your tsconfig.json
file like so:
{
"compilerOptions": {
"maxNodeModuleJsDepth": 5
}
}
const validate = require('valid-directory')
validate(process.cwd(), function (error, valid, invalidPaths) {
if (error) throw error
else if (valid) {
console.log('ok')
}
else {
console.log('invalid due to these:', invalidPaths)
}
})
Run npm install -g valid-directory
then run against the current working directory with valid-directory
or a specified directory via valid-directory <path>
.
Exit code will be 1
if validation failed to execute, 2
if validation failed, and 0
if validation passed.
To validate your packages before you publish them, you can do the following:
npm install --save-dev valid-directory
&& npx valid-directory
to your test
script inside your package.json
fileDiscover the release history by heading on over to the HISTORY.md
file.
Discover how you can contribute by heading on over to the CONTRIBUTING.md
file.
These amazing people are maintaining this project:
No sponsors yet! Will you be the first?
These amazing people have contributed code to this project:
Discover how you can contribute by heading on over to the CONTRIBUTING.md
file.
Unless stated otherwise all works are:
and licensed under:
© 2010 - cnpmjs.org x YWFE | Home | YWFE