Skip to content

Releases: bluwy/publint

v0.2.12

24 Oct 08:42
Compare
Choose a tag to compare

Features

  • If the package publishes a license file, but the "license" field is not set in package.json, a suggestion will now be shown to add the field (#111)

Bug fixes

  • In the "repostory" field, string shorthands with nested paths like gitlab:org/user/repo is now considered valid (#113)

Site

  • Fixed repository url link for string shorthands (#109)

Full Changelog: v0.2.11...v0.2.12

v0.2.11

16 Sep 13:02
Compare
Choose a tag to compare

Features

  • Update formatMessage() utility with a new color option to force enable or disable returning color in string (#110)

New Contributors

Full Changelog: v0.2.10...v0.2.11

v0.2.10

15 Aug 08:12
Compare
Choose a tag to compare

Features

  • Adds a new rule that validates the "repository" field (#106)
    • If "repository" is a string, it must be one of the supported shorthand strings from the docs.
    • If "repository" is an object with "type": "git", the "url" must be a valid git URL and can be parsed by npm.
    • The git:// protocol for GitHub repos should not be used due security concerns.
    • GitHub or GitLab links should be prefixed with git+ and postfixed with .git. (This is also warned by npm when publishing a package).

New Contributors

Full Changelog: v0.2.9...v0.2.10

v0.2.9

17 Jul 06:55
Compare
Choose a tag to compare

Bug fixes

New Contributors

Full Changelog: v0.2.8...v0.2.9

v0.2.8

18 May 11:00
Compare
Choose a tag to compare

Bug fixes

  • Fix file existence check for non-js files (#96)

Full Changelog: v0.2.7...v0.2.8

v0.2.7

23 Dec 05:38
Compare
Choose a tag to compare

Features

  • If the library exports from both "main"/"module" and "exports" fields, but the "exports" field doesn't export the root entrypoint, warn about the inconsistency. When "exports" is defined, it takes the highest priority, so all the library's entrypoint (root and deep) needs to be specified here. (#88)
  • Suggest using the "type" field. In Node.js v20.10.0, it introduces a new --experimental-default-type flag to flip the default module system from "CJS-as-default" to "ESM-as-default". It's recommended for libraries to specify the "type" field explicitly to prevent CJS files from being incorrectly interpreted as ESM. This suggestion helps push towards a better ESM experience in the future. (#83)

Full Changelog: v0.2.6...v0.2.7

v0.2.6

01 Dec 16:18
Compare
Choose a tag to compare

Features

  • Warn if the deprecated jsnext:main or jsnext fields are used by @sapphi-red (#85)

Site

New Contributors

Full Changelog: v0.2.5...v0.2.6

v0.2.5

20 Oct 06:23
Compare
Choose a tag to compare

Bug fixes

  • Fix missing published files check when resolving a path with fallback extensions (#79)

Full Changelog: v0.2.4...v0.2.5

v0.2.4

09 Oct 03:57
Compare
Choose a tag to compare

Bug fixes

  • Check for packed files locally before providing the "files" suggestion. An incorrect suggestion was given when you're using .npmignore or .gitignore to limit publishing certain files.

Site

  • Fix rules page mobile responsiveness

Full Changelog: v0.2.3...v0.2.4

v0.2.3

28 Sep 14:28
Compare
Choose a tag to compare

Features

  • Error if package.json has fields with invalid string, boolean, object, etc type (#73)

  • Suggest using the "files" field if detected test or config files are published (#77)

  • Warn on "exports" and "browser" object conflict for browser-ish environments (#58)

    For example, given this setup:

    {
      "browser": {
        "./lib.server.js": "./lib.browser.js"
      },
      "exports": {
        ".": {
          "worker": "./lib.server.js",
          "browser": "./lib.browser.js",
          "default": "./lib.server.js"
        }
      }
    }

    When matching the "worker" condition, it will resolve to "./lib.server.js" which is intended to work in a worker environment. However, the "browser" field also has a matching mapping for "./lib.server.js", causing the final resolved path to be "./lib.browser.js". This is usually not intended and causes the wrong file to be loaded.

  • Error on invalid JSX extensions, such as .cjsx, .mjsx, .ctsx, and .mtsx (#76)

    These extensions are usually mistaken as ESM and CJS variants of JSX, which is not valid. Instead they should be written in ESM with the .jsx extension instead.

Bug fixes

  • Skip file format checks only for globbed files
  • Fix "main" field with ESM content detection (#75)

Site

  • Add sidebar menu to rules page by @btea (#65)
  • Quickly scroll to the prompt information location by @btea (#68)
  • Fix version switch title not updated by @btea (#72)
  • Improve documentation for "types" format
  • Fix message border styles
  • Fix docs list missing dot

Full Changelog: v0.2.2...v0.2.3