Skip to content

Releases: tclindner/npm-package-json-lint

v2.11.0

02 Sep 19:01
Compare
Choose a tag to compare

Added

v2.10.0

02 Sep 16:55
Compare
Choose a tag to compare

Changed

  • Addressed issues, from @moshest, #57 and #58. This change gives better recommendations for what change is required by the user to resolve the lint issue. It also no longer throws an error when a property exists in the package.json file that doesn't exist in the preferred property order array. Thanks @moshest.

v2.9.0

30 Aug 03:24
Compare
Choose a tag to compare

Changed

  • Updated all rules to export a ruleType. Current valid values are "standard" and "array". The rules loader has been updated to references the ruleType export rather than trying to maintain a separate list of array style rules. This change closes issue #56 and should prevent the issue discussed in issue #53 from occurring again.

v2.8.2

24 Aug 02:16
Compare
Choose a tag to compare

Fixed

v2.8.1

22 Aug 02:43
Compare
Choose a tag to compare

Changed/Fixed

v2.8.0

17 Aug 02:12
Compare
Choose a tag to compare

Added

v2.7.1

16 Aug 02:01
Compare
Choose a tag to compare

Fixed

v2.7.0

09 Aug 03:28
Compare
Choose a tag to compare

Added

  • The ability to pass config using:
    1. a npmPackageJsonLintConfig property in package.json
    2. a .npmpackagejsonlintrc file in the current working directory
    3. a npmpackagejsonlint.config.js file that exports a config object in the current working directory.
    4. a global .npmpackagejsonlintrc file in the root of your user directory
    5. a global npmpackagejsonlint.config.js file that exports a config object in the root of your user directory

Please see configuration object wiki page.

v2.6.0

31 Jul 03:20
Compare
Choose a tag to compare

Changed

  • Bumped dependencies
  • Converted grunt tasks to npm scripts
  • Update cli output format for cleaner output

v2.5.0

11 Jun 18:23
Compare
Choose a tag to compare

@chr1shaefn3r enhanced the following rules so they no longer require a leading equals sign