Skip to content

chore(deps): update dependency publint to ^0.2.0

Renovate Bot a demandé de fusionner renovate/publint-0.x vers main

This MR contains the following updates:

Package Change Age Adoption Passing Confidence
publint (source) ^0.1.9 -> ^0.2.0 age adoption passing confidence

Release Notes

bluwy/publint (publint)

v0.2.6

Compare Source

Features
Site
New Contributors

Full Changelog: https://github.com/bluwy/publint/compare/v0.2.5...v0.2.6

v0.2.5

Compare Source

Bug fixes

Full Changelog: https://github.com/bluwy/publint/compare/v0.2.4...v0.2.5

v0.2.4

Compare Source

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: https://github.com/bluwy/publint/compare/v0.2.3...v0.2.4

v0.2.3

Compare Source

Features

  • Error if package.json has fields with invalid string, boolean, object, etc type (https://github.com/bluwy/publint/issues/73)

  • Suggest using the "files" field if detected test or config files are published (https://github.com/bluwy/publint/issues/77)

  • Warn on "exports" and "browser" object conflict for browser-ish environments (https://github.com/bluwy/publint/issues/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 (https://github.com/bluwy/publint/issues/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
Site

Full Changelog: https://github.com/bluwy/publint/compare/v0.2.2...v0.2.3

v0.2.2

Compare Source

Features
Bug fixes
  • Lower deprecated trailing slash glob syntax as suggestion instead of a warning when it's used for backwards compatibility only (https://github.com/bluwy/publint/issues/62)
  • Suppress invalid globbed file format if has correct adjacent file
  • Fix extension replacement in messages
  • Improve invalid types format message and docs
Site
  • Fix invalid package name not found message
  • Highlight code blocks in rules page
New Contributors

Full Changelog: https://github.com/bluwy/publint/compare/v0.2.1...v0.2.2

v0.2.1

Compare Source

Bug fixes
  • Fix "types" condition check with "exports" array format
  • Disable packed files search when a vfs is passed
  • Fix "browser" field file existence extensions check
  • Fix file existence check with trailing slash
Site
  • Site-wide design touch-up
  • New "Popular packages" section
  • New package version select switcher (https://github.com/bluwy/publint/issues/56)
  • New navigation header design
  • Update bottom documentation for clarity
  • Improve repo URL parsing
New Contributors

Full Changelog: https://github.com/bluwy/publint/compare/v0.2.0...v0.2.1

v0.2.0

Compare Source

Breaking changes

Note: If you're using publint from the CLI, these breaking changes should not affect you.

  • publint() now returns an object with messages instead of the messages array directly. This makes way for future APIs where publint will return more information than just messages.

    - const messages = await publint()
+ const { messages } = await publint()

  • Rename printMessage API to formatMessage to better reflect it's intent. (https://github.com/bluwy/publint/issues/43)

    - import { printMessage } from "publint/utils"
+ import { formatMessage } from "publint/utils"

const { messages } = await publint()

for (const message of messages) {
- console.log(printMessage(message))
+ console.log(formatMessage(message))
}

  • Remove filePath arg for the FILE_DOES_NOT_EXIST message.

    import type { Message } from "publint"
import { getPkgPathValue } from "publint/utils"

function messageToString(message: Message, pkg: Record<string, any>) {
  switch (message.code) {
    case "FILE_DOES_NOT_EXIST":
-     return `The file "${message.args.filePath}" does not exist.`
+     return `The file "${getPkgPathValue(pkg, message.path)}" does not exist.`
  }
}

  • Remove the import condition for the publint package. This provides a better error message if you call require("publint").

Features

  • Improve warnings when the exported "types" condition has an invalid format in ESM or CJS. This ensures your library's types will work in both environments when dual publishing. (https://github.com/bluwy/publint/issues/46)

    It affects packages commonly packaged like:

    {
  "exports": {
    ".": {
      "types": "./index.d.ts", <-- only works in CJS
      "import": "./index.mjs",
      "require": "./index.js",
    }
  }
}

    For more information, visit the rules documentation. This feature is inspired by https://arethetypeswrong.github.io.

Bug fixes

Full Changelog: https://github.com/bluwy/publint/compare/v0.1.16...v0.2.0

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever MR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this MR and you won't be reminded about this update again.

  • If you want to rebase/retry this MR, check this box

This MR has been generated by Renovate Bot.

Rapports de requête de fusion