npm-package-json-lint
npm-package-json-lint copied to clipboard
tclindner
Configurable linter for package.json files
Related to #42, #93 It would be nice if we could give more granular control over what types of versions, Git URLs, tarball URLs, etc are allowed. For example, I...
Since [the `private` setting](https://docs.npmjs.com/cli/v7/configuring-npm/package-json#private) prevents `npm` from attempting to publish a package, there's no need for `publishConfig` to be configured for those packages.
Is there a possibility to make this package an ESLint plugin or rule?
Draft for preliminary review For reference: https://nodejs.org/api/esm.html#esm_main_entry_point_export **Description of change** **Checklist** - [ ] Unit tests have been added - [ ] Specific notes for documentation, if applicable
I'm running `npm-package-json-lint`, version `5.1.0` in a monorepo that has a root `package.json` and then several projects under a `packages` directory, each with their own package.json file. I added a...
When reporting a bug, please include: * A little info about your environment * npm-package-json-lint version: 5 * npm version: 6.14.5 * node version: 12.18 * The output from npm-package-json-lint...
When you add Git repo as a dependency it will grab always the latest commit upon installation, which makes it unpredictable because two developers can use different versions of the...
Hi :) Not sure if that it's a bug, but i'm pretty sure that I'm, at least, missing a point and I would need clarification about 2 rules because I...
https://github.com/tclindner/npm-package-json-lint/blob/a4d6e7cfcfd587ea0646ab01a5bde64634c138db/src/rules/valid-values-engines.js#L24-L35 `valid-engines-values` is also checking that the values are of the correct type, instead of just only cheking they are one of the specified versions. I think this type checking...
Add new rule to require name to have defined a scope. Ideally It should be a three state field (always, never or don't café).