Update dependency publint to v0.2.4 - autoclosed #378
Closed
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.4
Release Notes
bluwy/publint (publint)
v0.2.4
Compare Source
Bug fixes
"files"
suggestion. An incorrect suggestion was given when you're using.npmignore
or.gitignore
to limit publishing certain files.Site
Full Changelog: publint/publint@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:
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
"main"
field with ESM content detection (https://github.com/bluwy/publint/issues/75)Site
"types"
formatFull Changelog: publint/publint@v0.2.2...v0.2.3
v0.2.2
Compare 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
suggestion
instead of awarning
when it's used for backwards compatibility only (https://github.com/bluwy/publint/issues/62)Site
New Contributors
Full Changelog: publint/publint@v0.2.1...v0.2.2
v0.2.1
Compare Source
Bug fixes
"types"
condition check with"exports"
array formatvfs
is passed"browser"
field file existence extensions checkSite
New Contributors
Full Changelog: publint/publint@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 withmessages
instead of themessages
array directly. This makes way for future APIs wherepublint
will return more information than justmessages
.Rename
printMessage
API toformatMessage
to better reflect it's intent. (https://github.com/bluwy/publint/issues/43)Remove
filePath
arg
for theFILE_DOES_NOT_EXIST
message.Remove the
import
condition for thepublint
package. 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:
For more information, visit the rules documentation. This feature is inspired by https://arethetypeswrong.github.io.
Bug fixes
"exports"
field have adjacent.d.ts
files 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: publint/publint@v0.1.16...v0.2.0
v0.1.16
Compare Source
Bug fixes
module
condition to precedeimport
per se. It is now ensured to precederequire
only as otherwise the condition isn't effective (https://github.com/bluwy/publint/pull/50)Full Changelog: publint/publint@v0.1.15...v0.1.16
v0.1.15
Compare Source
Bug fixes
Full Changelog: publint/publint@v0.1.14...v0.1.15
v0.1.14
Compare Source
Features
"module"
condition precedes the"import"
and"require"
in exports conditions (https://github.com/bluwy/publint/pull/49)Bug fixes
Site
isPathDir
checkNew Contributors
Full Changelog: publint/publint@v0.1.13...v0.1.14
v0.1.13
Compare Source
Bug fixes
"types"
condition-is-first check when there's preceding conditions that has it's"types"
condition too. This is common for dual ESM-CJS packages where"types"
are located within"require"
and"import"
conditions. (https://github.com/bluwy/publint/issues/47)"types"
condition check when"typesVersions"
key exist. The"typesVersions"
key requires a complex resolution algorithm that is harder to implement, so a quick patch is applied to remove the false errors for now. (https://github.com/bluwy/publint/issues/42)Full Changelog: publint/publint@v0.1.12...v0.1.13
v0.1.12
Compare Source
Features
--strict
flag in CLI to elevate warnings as errors (https://github.com/bluwy/publint/issues/38)Bug fixes
.native.js
extensions correctly (https://github.com/bluwy/publint/issues/41)Site
Full Changelog: publint/publint@v0.1.11...v0.1.12
v0.1.11
Compare Source
Features
exports
field for"moduleResolution": "bundler"
(https://github.com/bluwy/publint/issues/34)Site
Full Changelog: publint/publint@v0.1.10...v0.1.11
v0.1.10
Compare Source
Features
browser
,node
,bundler
, etc, likely means they are meant to work in that respective environment only.Bug fixes
exports
value. (https://github.com/bluwy/publint/issues/33)publishConfig
overrides when linting locally. (https://github.com/bluwy/publint/issues/28)Site
New Contributors
Full Changelog: publint/publint@v0.1.9...v0.1.10
Configuration
📅 Schedule: Branch creation - "after 10pm,before 6:00am" in timezone Europe/Paris, 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 has been generated by Mend Renovate. View repository job log here.