Christopher Hiller
Christopher Hiller
See https://nodejs.org/docs/latest/api/cli.html#--frozen-intrinsics
Currently, the rule checks the package root and any directories beneath it _except_ `node_modules`. It may be useful to allow glob patterns here so the user can tag directories either...
See #403 for in-progress work. #323 will eventually be part of this.
Motivation: npm gives no warning for stuff in `files` that doesn't exist New check that should look at the `files` field and ensure that if the entry allows a file...
I want a test that checks some config files against the JSON schema directly.
Add a new option `string[]` `ignore` which can be a relative dir path or glob which will cause the rule to _not_ descend into any matching directory.
This rule would check that known values in `package.json` are of the correct format. e.g., `engines` should be a `Record`; not a `string|string[]`. I'm sure there's some tool that does...
Let's make sure we aren't publishing a bunch of temp files, cache files, etc. These aren't "sensitive", but a nuisance nonetheless.
This would check for common/useful fields that aren't in `package.json` but probably should be. The default severity here should be `warn`. - `description` - `keywords` - `author` - `repo` -...