chore(deps-dev): Bump publint from 0.1.16 to 0.2.5

[dependabot]

Bumps publint from 0.1.16 to 0.2.5.

Release notes

Sourced from publint's releases.

v0.2.5

Bug fixes

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

Full Changelog: bluwy/publint@v0.2.4...v0.2.5

v0.2.4

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: bluwy/publint@v0.2.3...v0.2.4

v0.2.3

Features

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

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

• Warn on "exports" and "browser" object conflict for browser-ish environments (bluwy/publint#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 (bluwy/publint#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

... (truncated)

Commits

• 88ef748 Release v0.2.5
• ca0ecfe Fix missing files check for extensions
• a7e82db Release v0.2.4
• 167453a Check packed files for files suggestion
• 2f43f96 Release v0.2.3
• 3f21f86 Fix message border styles
• 9cbb9b0 Error on invalid jsx extensions
• 160318f Warn on exports browser-ish conflict
• c3fff13 Suggest files field if internal files are published
• 8c4cb79 Fix esm main suggestion detection
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)