chore(deps): update dependency publint to ^0.2.0 #48
Conversation
This file contains 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
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?s=60&v=4){kind=small}
|
Important Review skippedBot user detected. To trigger a single review, invoke the You can disable this status message by setting the 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #48 +/- ##
=======================================
Coverage 87.87% 87.87%
=======================================
Files 13 13
Lines 404 404
Branches 52 52
=======================================
Hits 355 355
Misses 49 49 |
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.1.9->^0.2.0Release Notes
bluwy/publint (publint)
v0.2.12Compare Source
Features
"license"field is not set inpackage.json, a suggestion will now be shown to add the field (https://github.com/bluwy/publint/issues/111)Bug fixes
"repostory"field, string shorthands with nested paths likegitlab:org/user/repois now considered valid (https://github.com/bluwy/publint/issues/113)Site
Full Changelog: bluwy/publint@v0.2.11...v0.2.12
v0.2.11Compare Source
Features
formatMessage()utility with a newcoloroption to force enable or disable returning color in string (https://github.com/bluwy/publint/pull/110)New Contributors
Full Changelog: bluwy/publint@v0.2.10...v0.2.11
v0.2.10Compare Source
Features
"repository"field (https://github.com/bluwy/publint/pull/106)"repository"is a string, it must be one of the supported shorthand strings from the docs."repository"is an object with"type": "git", the"url"must be a valid git URL and can be parsed by npm.git://protocol for GitHub repos should not be used due security concerns.git+and postfixed with.git. (This is also warned by npm when publishing a package).New Contributors
Full Changelog: bluwy/publint@v0.2.9...v0.2.10
v0.2.9Compare Source
Bug fixes
New Contributors
Full Changelog: bluwy/publint@v0.2.8...v0.2.9
v0.2.8Compare Source
Bug fixes
Full Changelog: bluwy/publint@v0.2.7...v0.2.8
v0.2.7Compare Source
Features
"main"/"module"and"exports"fields, but the"exports"field doesn't export the root entrypoint, warn about the inconsistency. When"exports"is defined, it takes the highest priority, so all the library's entrypoint (root and deep) needs to be specified here. (https://github.com/bluwy/publint/issues/88)"type"field. In Node.js v20.10.0, it introduces a new--experimental-default-typeflag to flip the default module system from "CJS-as-default" to "ESM-as-default". It's recommended for libraries to specify the"type"field explicitly to prevent CJS files from being incorrectly interpreted as ESM. This suggestion helps push towards a better ESM experience in the future. (https://github.com/bluwy/publint/issues/83)Full Changelog: bluwy/publint@v0.2.6...v0.2.7
v0.2.6Compare Source
Features
jsnext:mainorjsnextfields are used by @sapphi-red (https://github.com/bluwy/publint/pull/85)Site
New Contributors
Full Changelog: bluwy/publint@v0.2.5...v0.2.6
v0.2.5Compare Source
Bug fixes
Full Changelog: bluwy/publint@v0.2.4...v0.2.5
v0.2.4Compare Source
Bug fixes
"files"suggestion. An incorrect suggestion was given when you're using.npmignoreor.gitignoreto limit publishing certain files.Site
Full Changelog: bluwy/publint@v0.2.3...v0.2.4
v0.2.3Compare Source
Features
Error if
package.jsonhas 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
.jsxextension instead.Bug fixes
"main"field with ESM content detection (https://github.com/bluwy/publint/issues/75)Site
"types"formatFull Changelog: bluwy/publint@v0.2.2...v0.2.3
v0.2.2Compare Source
Features
"typings"field file existence (https://github.com/bluwy/publint/pull/60)"browser"field suggestion for using"imports"and"exports"fields instead (https://github.com/bluwy/publint/pull/59)Bug fixes
suggestioninstead of awarningwhen it's used for backwards compatibility only (https://github.com/bluwy/publint/issues/62)Site
New Contributors
Full Changelog: bluwy/publint@v0.2.1...v0.2.2
v0.2.1Compare Source
Bug fixes
"types"condition check with"exports"array formatvfsis passed"browser"field file existence extensions checkSite
New Contributors
Full Changelog: bluwy/publint@v0.2.0...v0.2.1
v0.2.0Compare Source
Breaking changes
Note: If you're using
publintfrom the CLI, these breaking changes should not affect you.publint()now returns an object withmessagesinstead of themessagesarray directly. This makes way for future APIs wherepublintwill return more information than justmessages.Rename
printMessageAPI toformatMessageto better reflect it's intent. (https://github.com/bluwy/publint/issues/43)Remove
filePathargfor theFILE_DOES_NOT_EXISTmessage.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
importcondition for thepublintpackage. This provides a better error message if you callrequire("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
"exports"field have adjacent.d.tsfiles and no"types"condition. This follows TypeScript's resolution algorithm. For more information, visit the rules documentation. (https://github.com/bluwy/publint/issues/46)Full Changelog: bluwy/publint@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 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.