chore(deps): update dependency publint to v0.3.21#558
Open
renovate[bot] wants to merge 1 commit into
Open
Conversation
|
37fa503 to
8a2d31c
Compare
8a2d31c to
e19fad6
Compare
9aaab76 to
d8612a7
Compare
d8612a7 to
8d4fc51
Compare
8d4fc51 to
bfba529
Compare
abff6e3 to
8c1b679
Compare
8c1b679 to
43354b7
Compare
e5e95af to
a06a736
Compare
a06a736 to
f3d56aa
Compare
f3d56aa to
3525252
Compare
3525252 to
cacdab3
Compare
cacdab3 to
5a2509f
Compare
5a2509f to
174ceb2
Compare
d9bcc17 to
6803202
Compare
6803202 to
57552e4
Compare
57552e4 to
f8dcf42
Compare
f8dcf42 to
bc6e630
Compare
bc6e630 to
01cc661
Compare
01cc661 to
aa6423c
Compare
aa6423c to
1fac3ac
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
0.2.12→0.3.21Release Notes
publint/publint (publint)
v0.3.21Compare Source
Patch Changes
"sideEffects": falsewhen bundler-oriented package fields or conditions are detected and the field is missing. (#228)v0.3.20Compare Source
Patch Changes
Suggest adding
engines.nodewhen it is missing from detected Node.js packages (#226)Loosen "breaking change" wording in lint messages (
7bb3f4f)v0.3.19Compare Source
Patch Changes
Add
NESTED_PACKAGE_JSON_FIELD_IGNOREDto warn when published nestedpackage.jsonfiles define"exports"or"imports", which Node.js ignores outside the package root. (#224)Fix internal browser directory traversal logic (#224)
v0.3.18Compare Source
Patch Changes
getPkgPathValuefrompublint/utilsreturn undefined if the path is invalid (ad2aa9c)v0.3.17Compare Source
Patch Changes
Fix packing packages with pnpm when
publishConfig.directoryis set (#216)Updated dependencies [
2dcb107]:v0.3.16Compare Source
Patch Changes
7b1408e)v0.3.15Compare Source
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"]andexports['default']forCJS_WITH_ESMODULE_DEFAULT_EXPORTrule (8285f77)v0.3.14Compare Source
Patch Changes
__esModulemarker. 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)v0.3.13Compare Source
Patch Changes
Improve message for
"main"field with empty value and has missing files (0499518)Update fallback arrays message for CLI output (
37b9dd5)v0.3.12Compare Source
Patch Changes
#!(#183)v0.3.11Compare Source
Patch Changes
Update
EXPORTS_GLOB_NO_DEPRECATED_SUBPATH_MAPPINGmessage 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)v0.3.10Compare Source
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.v0.3.9Compare Source
Patch Changes
Support the
formatMessageutility in the browser. It has a newcolor: 'html'option to highlight important parts with<strong>tags instead of ANSI colors. It also has a newreference: booleanoption so the messages are worded in reference of the message location. (e1cfef0)If
formatMessageis passed apackage.jsonobject with missing keys, the message part that references the value will now fallback to"undefined"instead of completely erroring out. (45962d1)v0.3.8Compare Source
Patch Changes
Support passing a tarball path to the publint CLI. This allows to easily lint any tarball files at hand. (#166)
The
publintAPI now returns apkgobject as a convenience to pass it toformatMessage(#166)Updated dependencies [
02d169b]:v0.3.7Compare Source
Patch Changes
The
"imports"field is now linted with the following rules: (#162)IMPORTS_KEY_INVALID: Ensure the imports key starts with a#IMPORTS_VALUE_INVALID: Ensure the imports value is a valid path that starts with a./IMPORTS_GLOB_NO_MATCHED_FILES: Ensure the imports glob matches at least one fileIMPORTS_DEFAULT_SHOULD_BE_LAST: Ensure the"default"condition is last in an entrypoint's objectIMPORTS_MODULE_SHOULD_BE_ESM: Ensure the"module"condition file is ESMIMPORTS_MODULE_SHOULD_PRECEDE_REQUIRE: Ensure the"module"condition precedes the"require"condition in an entrypoint's objectImprove SSH git URL detection when checking the
"repository"field. Values like"git@github.com:user/project.git"is now detected as a valid git URL, but will be suggested to use a full git URL instead, like"git+ssh://git@github.com/user/project.git"(28da844)Fix exports types message when the
"require"or"import"condition already exists but the dts file format is still invalid (a731ec3)v0.3.6Compare Source
Patch Changes
.jsor/index.js(04f289e)v0.3.5Compare Source
Patch Changes
Check the
"bin"field if the referenced file exists, has the correct JS format, and can be executed (#150)Deprecate the
depscommand. The command has been tricky to maintain and incomplete (e.g. doesn't lint recursively). A separate tool can be used to run publint on dependencies instead, e.g.npx renoma --filter-rules "publint". (#149)v0.3.4Compare Source
Patch Changes
When globbing
"exports"values that contains*, also respect"exports"keys that mark paths as null. For example: (b9605ae){ "exports": { "./*": "./dist/*", "./browser/*": null } }The glob in
"./*": "./dist/*"will no longer match and lint files in"./browser/*"as it's marked null (internal).Update logs when running the
publintCLI: (58d96a2)publintversion is now displayed.publint depscommand no longer logs passing dependencies. Only failing dependencies are logged.Examples:
$ npx publint deps $ Running publint v0.X.X for my-library deps... $ x my-dependency $ Errors: $ 1. ...Fix detecting shorthand repository URLs with the
.character (09d8cbb)Clarify message when
"types"is not the first condition in the"exports"field (5a6ba00)Correctly detect if a
"types"value in"exports"is used for dual publishing (3f3d8b2)v0.3.3Compare Source
Patch Changes
Rename
EXPORT_TYPES_INVALID_FORMATmessage toEXPORTS_TYPES_INVALID_FORMAT(#139)Allow versioned types conditions (e.g.
"types@>=5.2") in"exports"when checking for"types"condition ordering (#138)v0.3.2Compare Source
Patch Changes
(Potentially breaking) Disable running lifecycle scripts, such as
prepare,prepack, andpostpack, when running the pack command internally. This returns to the behavior in v0.2. (Note that this change does not apply to yarn as it does not support ignoring lifecycle scripts for local projects) (#128)This change is made as running lifecycle scripts was an unintentional behavior during the v0.3 breaking change, which could cause the linting process to take longer than expected, or even cause infinite loops if
publintis used in a lifecycle script.Update repository and bugs URLs to point to the new
publintorganization (1eda033)Updated dependencies [
1eda033,10e3891]:v0.3.1Compare Source
Patch Changes
__esModulemarker. 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)v0.3.0Compare Source
Minor Changes
The
vfsoption is removed in favour of an extended support ofpack: { tarball: ArrayBuffer | ReadableStream }andpack: { files: PackFile[] }APIs. Now, it is even easier to usepublintin the browser or against a packed.tgzfile in Node.js. See the docs for more examples of how to use these new options. (#122)Bump node version support to >=18 (
cb2ed8b)publintnow runs your project's package manager'spackcommand to get the list of packed files for linting. The previousnpm-packlistdependency is now removed. (#120)A new
packoption is added to the node API to allow configuring this. It defaults to'auto'and will automatically detect your project's package manager usingpackage-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
packcommand 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:orlink:protocol is specified in thepackage.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_FORMATlinting to detect.d.mtsand.d.ctsfiles (af5e88b)Updated dependencies [
d0b406b]:Configuration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.