chore(deps): update all non-major dependencies

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@vercel/nft	^0.27.9 -> ^0.29.0
pnpm (source)	9.15.2 -> 9.15.3
publint (source)	^0.2.0 -> ^0.3.0

---

Release Notes

vercel/nft (@​vercel/nft)

v0.29.0

Compare Source

Features

• bump engines.node>=18 and target=es2022 (#​460) (1aec4bd)

v0.28.0

Compare Source

Features

• support module.createRequire (#​459) (fc710ff), closes #​430

v0.27.10

Compare Source

Bug Fixes

• avoid URL illegal constructor error (#​458) (5777c8b)

pnpm/pnpm (pnpm)

v9.15.3

Compare Source

bluwy/publint (publint)

v0.3.0

Compare Source

Minor Changes

• The vfs option is removed in favour of an extended support of pack: { tarball: ArrayBuffer | ReadableStream } and pack: { files: PackFile[] } APIs. Now, it is even easier to use publint in the browser or against a packed .tgz file in Node.js. See the docs for more examples of how to use these new options. (#​122)

• Bump node version support to >=18 (cb2ed8b)

• publint now runs your project's package manager's pack command to get the list of packed files for linting. The previous npm-packlist dependency is now removed. (#​120)

  A new pack option is added to the node API to allow configuring this. It defaults to 'auto' and will automatically detect your project's package manager using package-manager-detector. See its JSDoc for more information of the option.

  This change is made as package managers have different behaviors for packing files, so running their pack command directly allows for more accurate linting. However, as a result of executing these commands in a child process, it may take 200-500ms longer to lint depending on the package manager used and the project size. The new handling also does not support yarn 1. See this comment for more information.

  If you use yarn 1, you should upgrade to the latest yarn version or a different package manager. Otherwise, no other changes are required for this new behavior.

Patch Changes

• Initial setup to publish with Changesets (24a62f5)

• When a dependency with the file: or link: protocol is specified in the package.json, it will now error to prevent accidentally publishing dependencies that will likely not work when installed by end-users (6e6ab33)

• Fix EXPORT_TYPES_INVALID_FORMAT linting to detect .d.mts and .d.cts files (af5e88b)

• Updated dependencies [d0b406b]:

  • @​publint/pack@​0.1.0

v0.2.12

Compare Source

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 (https://github.com/bluwy/publint/issues/111)

Bug fixes

• In the "repostory" field, string shorthands with nested paths like gitlab:org/user/repo is now considered valid (https://github.com/bluwy/publint/issues/113)

Site

• Fixed repository url link for string shorthands (https://github.com/bluwy/publint/issues/109)

Full Changelog: publint/publint@v0.2.11...v0.2.12

v0.2.11

Compare Source

Features

• Update formatMessage() utility with a new color option to force enable or disable returning color in string (https://github.com/bluwy/publint/pull/110)

New Contributors

• @​zanminkian made their first contribution in https://github.com/bluwy/publint/pull/110

Full Changelog: publint/publint@v0.2.10...v0.2.11

v0.2.10

Compare Source

Features

• Adds a new rule that validates the "repository" field (https://github.com/bluwy/publint/pull/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

• @​Namchee made their first contribution in https://github.com/bluwy/publint/pull/106

Full Changelog: publint/publint@v0.2.9...v0.2.10

v0.2.9

Compare Source

Bug fixes

• Update message when no type field is present by @​benmccann (https://github.com/bluwy/publint/pull/104)

New Contributors

• @​benmccann made their first contribution in https://github.com/bluwy/publint/pull/104

Full Changelog: publint/publint@v0.2.8...v0.2.9

v0.2.8

Compare Source

Bug fixes

• Fix file existence check for non-js files (https://github.com/bluwy/publint/issues/96)

Full Changelog: publint/publint@v0.2.7...v0.2.8

---

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 PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

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

---

This PR was generated by Mend Renovate. View the repository job log.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 7f73daa

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[Rich-Harris]

preview: https://svelte-dev-git-preview-kit-13264-svelte.vercel.app/

this is an automated message