chore(deps-dev): bump publint from 0.1.16 to 0.3.17 in /packages/svelte

[dependabot]

Bumps publint from 0.1.16 to 0.3.17.

Release notes

Sourced from publint's releases.

publint@0.3.17

Patch Changes

• Fix packing packages with pnpm when publishConfig.directory is set (#216)

• Updated dependencies [2dcb107]:

  • @​publint/pack@​0.1.3

publint@0.3.16

Patch Changes

• Re-enable file existence checks for TS and TSX files if they do not use custom conditions. In v0.3.10, this was done unconditionally instead which missed catching possible file typos if only common conditions are used. (7b1408e)

publint@0.3.15

Patch Changes

• Skip file existence checks when crawling subpath imports as they may be dev-only and not used after bundling or publish. This check may be improved in the future when publint can scan for files to see if the subpath imports are used. (0d72997)

• Handle exports["default"] and exports['default'] for CJS_WITH_ESMODULE_DEFAULT_EXPORT rule (8285f77)

publint@0.3.14

Patch Changes

• Add a new warning when an entrypoint is exported as CJS-only, has a default export, and has the __esModule marker. This setup has different interpretations by bundlers and runtimes, and implicit handling detection that may not be obvious for both package authors and users, hence it is discouraged. (#201)

publint@0.3.13

Patch Changes

• Improve message for "main" field with empty value and has missing files (0499518)

• Update fallback arrays message for CLI output (37b9dd5)

publint@0.3.12

Patch Changes

• Fix shebang check to allow spaces after the #! (#183)

publint@0.3.11

Patch Changes

• Update EXPORTS_GLOB_NO_DEPRECATED_SUBPATH_MAPPING message and severity to error (#179)

• Add a new warning when the "exports" or "imports" field contain a fallback array as most tooling will only the pick the first value that can be parsed, and other tooling may work differently leading to inconsistent behaviors (#180)

publint@0.3.10

Patch Changes

• Support custom conditions in "exports" that points to raw TS or TSX files. This configuration is common in monorepo setups where packages refer to the raw files among themselves using a custom condition so custom aliasing isn't needed. (b34ea94)

  With this support, the "types" condition is allowed to come after any exports of the raw TS or TSX files. File existence checks are also disabled for raw TS and TSX files reference as after publish these files may intentionally be not published.

... (truncated)

Changelog

Sourced from publint's changelog.

0.3.17

Patch Changes

• Fix packing packages with pnpm when publishConfig.directory is set (#216)

• Updated dependencies [2dcb107]:

  • @​publint/pack@​0.1.3

0.3.16

Patch Changes

• Re-enable file existence checks for TS and TSX files if they do not use custom conditions. In v0.3.10, this was done unconditionally instead which missed catching possible file typos if only common conditions are used. (7b1408e)

0.3.15

Patch Changes

• Skip file existence checks when crawling subpath imports as they may be dev-only and not used after bundling or publish. This check may be improved in the future when publint can scan for files to see if the subpath imports are used. (0d72997)

• Handle exports["default"] and exports['default'] for CJS_WITH_ESMODULE_DEFAULT_EXPORT rule (8285f77)

0.3.14

Patch Changes

• Add a new warning when an entrypoint is exported as CJS-only, has a default export, and has the __esModule marker. This setup has different interpretations by bundlers and runtimes, and implicit handling detection that may not be obvious for both package authors and users, hence it is discouraged. (#201)

0.3.13

Patch Changes

• Improve message for "main" field with empty value and has missing files (0499518)

• Update fallback arrays message for CLI output (37b9dd5)

0.3.12

Patch Changes

• Fix shebang check to allow spaces after the #! (#183)

0.3.11

Patch Changes

• Update EXPORTS_GLOB_NO_DEPRECATED_SUBPATH_MAPPING message and severity to error (#179)

• Add a new warning when the "exports" or "imports" field contain a fallback array as most tooling will only the pick the first value that can be parsed, and other tooling may work differently leading to inconsistent behaviors (#180)

... (truncated)

Commits

• 0b5c272 Release packages (#217)
• 2dcb107 Support pnpm publishConfig.directory config (#216)
• 9927d7e Update dependencies
• 9ef31c5 Release packages (#210)
• 7fb8483 Set prettier printWidth to 100
• 6e45f1e Update dependencies
• 7b1408e Re-enable TS file existence check for common conditions
• d02eb46 Improve repo parse
• 849f435 Update dependencies
• fa7e5a5 Release packages (#206)
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by [GitHub Actions](https://www.npmjs.com/~GitHub Actions), a new releaser for publint since your current version.

You can trigger a rebase of this PR 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 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)

Note
Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 401a6a0

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