chore(deps): update misc npm packages#2195
Open
renovate[bot] wants to merge 1 commit into
Open
Conversation
Contributor
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
✅ Deploy Preview for cert-manager ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
renovate
Bot
force-pushed
the
renovate/misc-npm-packages
branch
from
July 6, 2026 10:48
1aa63d9 to
c84a9b4
Compare
renovate
Bot
force-pushed
the
renovate/misc-npm-packages
branch
from
July 7, 2026 01:09
c84a9b4 to
4929958
Compare
renovate
Bot
force-pushed
the
renovate/misc-npm-packages
branch
from
July 7, 2026 11:45
4929958 to
6f4ab82
Compare
renovate
Bot
force-pushed
the
renovate/misc-npm-packages
branch
from
July 8, 2026 08:30
6f4ab82 to
00cd889
Compare
renovate
Bot
force-pushed
the
renovate/misc-npm-packages
branch
from
July 8, 2026 12:29
00cd889 to
1d741fd
Compare
renovate
Bot
force-pushed
the
renovate/misc-npm-packages
branch
from
July 10, 2026 08:31
1d741fd to
f788cae
Compare
renovate
Bot
force-pushed
the
renovate/misc-npm-packages
branch
from
July 11, 2026 08:41
f788cae to
6dcd635
Compare
renovate
Bot
force-pushed
the
renovate/misc-npm-packages
branch
from
July 11, 2026 12:30
6dcd635 to
f7471f5
Compare
renovate
Bot
force-pushed
the
renovate/misc-npm-packages
branch
from
July 12, 2026 04:31
f7471f5 to
899693a
Compare
renovate
Bot
force-pushed
the
renovate/misc-npm-packages
branch
from
July 12, 2026 15:07
899693a to
e57dae0
Compare
renovate
Bot
force-pushed
the
renovate/misc-npm-packages
branch
from
July 12, 2026 19:33
e57dae0 to
88f9b46
Compare
renovate
Bot
force-pushed
the
renovate/misc-npm-packages
branch
from
July 13, 2026 20:04
88f9b46 to
771601e
Compare
renovate
Bot
force-pushed
the
renovate/misc-npm-packages
branch
14 times, most recently
from
July 19, 2026 13:02
e841de9 to
0dedb3d
Compare
Signed-off-by: Renovate Bot <renovate-bot@users.noreply.github.com>
renovate
Bot
force-pushed
the
renovate/misc-npm-packages
branch
from
July 20, 2026 02:59
0dedb3d to
7c39001
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:
5.10.0→5.17.04.3.2→4.3.310.6.0→10.7.08.5.16→8.5.193.9.4→3.9.54.3.2→4.3.3Release Notes
Rel1cx/eslint-react (@eslint-react/eslint-plugin)
v5.17.0Compare Source
🐞 Fixes
react-jsx/no-leaked-dollar: the intentional-$exemption (e.g.<div>${price}</div>) is no longer defeated by surrounding whitespace or empty siblings — a lone$before a single expression is now allowed whenever all other siblings are non-substantive. (#1911)react-jsx/no-leaked-semicolon: consecutive leaked semicolons (e.g.;;) at the start of a JSX text node are now detected. (#1911)📝 Documentation
react-x/no-unnecessary-use-prefix: reorganized the rule examples.🏗️ Internal
react-jsx: extracted the sharedfind-create-element-children-propandremove-jsx-attributerule helpers, removed deadLiteralvisitors fromno-comment-textnodesandno-leaked-semicolon, simplified theno-key-after-spreadattribute scan, and hoistedno-useless-fragmentdetection and fix helpers to module level. (#1911)@local/eff: synced theFunctionmodule with effect and added missing@categorytags.Full Changelog: Rel1cx/eslint-react@v5.16.1...v5.17.0
v5.16.1Compare Source
🐞 Fixes
react-jsx/no-children-prop:React.createElementcalls whose props argument is wrapped in a TypeScript type assertion (e.g.{ children: "x" } as Props) are now reported; computed property keys written as template literals (e.g.{ [children]: "x" }) are now recognized as thechildrenprop; fixed a false positive where a computed identifier key in acreateElementprops object (e.g.{ [propName]: "Children" }) was treated as the staticchildrenprop; the suggestion fix now escapes JSX-sensitive characters (<,>,{,},&) when moving a stringchildrenprop value into element content. (#1910)react-jsx/no-children-prop-with-children: samecreateElementedge-case fixes asno-children-prop. (#1910)react-jsx/no-useless-fragment:allowExpressions: falsenow only flags fragments with a single expression child, matching the option's documented behavior, instead of flagging any fragment inside a JSX element; fragments with spread attributes (e.g.<Fragment {...props}>) are no longer auto-fixed; the auto-fixer now removes leading indentation when collapsing whitespace-only fragments. (#1910)react-jsx/no-leaked-dollar:$character references (&#​36;,$) are no longer treated as leaked dollar signs; only a literal$in the source is reported. (#1910)react-jsx/no-leaked-semicolon: leaked semicolons followed by spaces or tabs before a newline, including CRLF line endings, are now detected. (#1910)react-x/immutability: addeduseHistoryto known navigation hooks, so navigation methods such as.push()are not treated as in-place mutations inside frozen callbacks.🏗️ Internal
@eslint-react/ast: addedExtract.getStaticPropertyNamefor resolving static property names from object properties. (#1910)Full Changelog: Rel1cx/eslint-react@v5.16.0...v5.16.1
v5.16.0Compare Source
✨ New
@eslint-react/core: added support for hook calls written as tagged template literals. (#1909)@eslint-react/jsx:findAttributenow resolves nested spread identifiers and nested object expression spreads. (#1908)🏗️ Internal
Full Changelog: Rel1cx/eslint-react@v5.15.0...v5.16.0
v5.15.0Compare Source
📝 Documentation
🏗️ Internal
typescript-eslintto8.64.0,nxto23.1.0,eslint-plugin-package-jsonto1.6.0, andpnpmto11.13.0.strictBooleanExpressionsin TSL and synchronized sample rule configurations. (#1907)pnpm/action-setupinstead of installing pnpm globally via npm.Full Changelog: Rel1cx/eslint-react@v5.14.10...v5.15.0
v5.14.10Compare Source
🐞 Fixes
@eslint-react/ast:Extract.getCalleeNamenow returnsnullfor computed member expressions (e.g.obj[foo](),obj["foo"](),obj[foo]()) instead of the property name, so callers don't treat dynamically chosen methods as static method names. (#1906)🏗️ Internal
Extract.getCalleeName.Full Changelog: Rel1cx/eslint-react@v5.14.9...v5.14.10
v5.14.9Compare Source
🐞 Fixes
@eslint-react/ast: removedExtract.getPropertyNameand addedExtract.getCalleeNamefor simpler callee name resolution. (#1905)obj["foo"]()is no longer resolved to"foo"). This avoids relying on the runtime value of computed keys and aligns callee matching across the codebase. Affected rules:react-dom/no-dangerously-set-innerhtmlreact-dom/no-find-dom-nodereact-dom/no-flush-syncreact-web-api/no-leaked-event-listenerreact-web-api/no-leaked-fetchreact-x/globalsreact-x/immutabilitycore.isJsxLike: no longer treatsReact['createElement']calls as JSX-like, since the callee is accessed through a computed member expression.🏗️ Internal
core,react-dom,react-web-api, andreact-xrules usingExtract.getCalleeName.@effect/platform,effect,fumadocs-core,fumadocs-mdx,fumadocs-ui,postcss,pnpm, andtsdown.Full Changelog: Rel1cx/eslint-react@v5.14.8...v5.14.9
v5.14.8Compare Source
📝 Documentation
react-x: refreshed the React Compiler diff reports. (#1903)🏗️ Internal
react-x: moved the purity and refs resolvers intolib.ts. (#1902)tsdown,postcss, andfumadocs.Full Changelog: Rel1cx/eslint-react@v5.14.7...v5.14.8
v5.14.7Compare Source
🐞 Fixes
react-x/immutability: ignore navigation hook methods (e.g.useNavigate,useNavigation) as mutations. (#1901)🏗️ Internal
pnpmlockfile.Full Changelog: Rel1cx/eslint-react@v5.14.6...v5.14.7
v5.14.6Compare Source
🐞 Fixes
react-x/immutability: ignoreuseRouter()navigation methods (e.g..push()) as mutations when they appear inside frozen callbacks; aliases created through variable declarators are also recognized. (#1898)🏗️ Internal
Check.isExpressionto@eslint-react/astalong with unit tests.eslint,nx,dompurify, andpnpm.react-x/immutabilityanalysis helpers by sharing initializer provenance checks foruseRef()anduseRouter()and using AST parent traversal for function-boundary detection.Full Changelog: Rel1cx/eslint-react@v5.14.5...v5.14.6
v5.14.5Compare Source
📝 Documentation
🏗️ Internal
check:configsandcheck:docsscripts into a singlecheck:rulesscript.Full Changelog: Rel1cx/eslint-react@v5.14.4...v5.14.5
v5.14.2Compare Source
🐞 Fixes
react-x/globals: added detection for global writes through destructuring assignments and property deletion withdelete. (#1896)react-x/globals: propagated render-time global mutation effects through directly called helpers and stable local aliases. (#1896)🏗️ Internal
react-debugcomponent and source detection,react-naming-conventionnaming rules, andreact-x/immutabilityReact Compiler fixtures.Full Changelog: Rel1cx/eslint-react@v5.14.1...v5.14.2
v5.14.1Compare Source
🐞 Fixes
@eslint-react/ast:Extract.getCalleeNamenow returnsnullfor computed member expressions (e.g.obj[foo](),obj["foo"](),obj[foo]()) instead of the property name, so callers don't treat dynamically chosen methods as static method names. (#1906)🏗️ Internal
Extract.getCalleeName.Full Changelog: Rel1cx/eslint-react@v5.14.9...v5.14.10
v5.14.0Compare Source
✨ New
react-x/refs: added render-reachability support for function declarations, IIFEs, synchronous array callbacks, and render-time callbacks passed touseMemoanduseReducer. (#1895)react-x/refs: added lazy-initialization support for explicitundefinedguards and for null guards enclosing additional nested conditions. (#1895)🐞 Fixes
react-x/refs: reworked render-time call analysis as an unbounded fixed-point propagation, removing the previous 50-iteration cap. (#1895)react-x/refs: tightened inverted lazy-initialization handling so the non-null branch must unconditionally return or throw. (#1895)react-x/refs: stopped treating!ref.currentas a null guard because initialized refs may contain falsy values. (#1895)🏗️ Internal
react-x/refs: refactored ref aliases, function bindings, JSX refs, and duplicate initialization tracking to use scoped ESLint variable identities and position-aware binding events instead of file-wide identifier names. (#1895)react-x/immutabilityand documented them in the spec diff report.@effect/language-serviceto^0.86.5.preactto^10.29.7.viteto^8.1.4in example apps.dprintJSON plugin to^0.23.0.Full Changelog: Rel1cx/eslint-react@v5.13.2...v5.14.0
v5.13.2Compare Source
🐞 Fixes
react-x/immutability: fixed false positive onref.currentwrite insideuseEffect. (#1894)🏗️ Internal
@types/nodeto^26.1.1.preactto^10.29.6.tsdownto^0.22.4.Full Changelog: Rel1cx/eslint-react@v5.13.1...v5.13.2
v5.13.1Compare Source
🐞 Fixes
react-x/refs: aligned error message wording forreadDuringRender,writeDuringRender, andrefPassedToFunctionwith the React Compiler specification.Full Changelog: Rel1cx/eslint-react@v5.13.0...v5.13.1
v5.13.0Compare Source
✨ New
react-x/refsnow detects nested property writes on a ref's value (e.g.ref.current.inner = value), which are now reported aswriteDuringRenderinstead of being misclassified as a read.react-x/refsnow tracks functions bound to (and called through) simple object-member-expression targets (e.g.object.foo = () => ref.current; object.foo();), closing a gap in the render-reachability analysis that previously only covered plain variable bindings.react-x/refsnow detectsref.currentaccesses inside the lazy initializer function passed directly asuseState's first argument, since it runs synchronously during the initial render unlike other hook-callback arguments.react-x/refsnow exempts calls to a function namedrender(e.g.props.render(ref), a common render-prop pattern) from therefPassedToFunctiondiagnostic, alongside the existingmergeRefs/hook exemptions.🐞 Fixes
react-x/refslazy-init guard-block detection so it is direction-aware: inside the branch of anif (ref.current == null)-style guard that is guaranteed to seeref.currentas null, only a direct write is treated as the (single) valid initialization; reads or values passed to a function there are still reported.🏗️ Internal
react-x/refsinternals, replacingisRefCurrentNullCheckwithgetRefCurrentNullCheckBranchinlib.ts.fumadocspackages andpreact.react-debug/jsxrule.Full Changelog: Rel1cx/eslint-react@v5.12.2...v5.13.0
v5.12.1Compare Source
📝 Documentation
react-x/immutabilityrule description in docs.🏗️ Internal
Full Changelog: Rel1cx/eslint-react@v5.12.0...v5.12.1
v5.12.0Compare Source
✨ New
react-x/immutabilityto align with the React Compiler'sValidateNoFreezingKnownMutableFunctionsvalidation pass: it now detects functions that (transitively) mutate a captured local variable and reports them when passed as a JSX prop, passed as a hook argument, or returned from a hook. (#1891)📝 Documentation
🏗️ Internal
typescript-eslintpackages to^8.63.0.eslint-plugin-perfectionistto^5.10.0.Full Changelog: Rel1cx/eslint-react@v5.11.3...v5.12.0
v5.11.3Compare Source
🐞 Fixes
FunctionComponentDetectionHint.DoNotIncludeFunctionDefinedAsClassPropertychecking for objectPropertynodes instead of classPropertyDefinitionnodes, so functions defined as class fields are now correctly excluded when the hint is set. (#1890)🏗️ Internal
MessageIDtypes.eslint-plugin-jsdoc,typedoc,undiciandpnpm.Full Changelog: Rel1cx/eslint-react@v5.11.2...v5.11.3
v5.11.2Compare Source
📝 Documentation
react-x/no-children-count,react-x/no-children-for-each,react-x/no-children-map,react-x/no-children-only,react-x/no-children-to-array, andreact-x/no-clone-element) with clearer guidance on why child introspection creates fragile component coupling and links to Astryx'sno-react-introspectionrule. (#1889)THIRD-PARTY-LICENSEfile.Full Changelog: Rel1cx/eslint-react@v5.11.0...v5.11.2
v5.11.0Compare Source
✨ New
react-x/refsnow detects ref mutations/reads inside helper functions that are called (directly, or through a simple variable alias) during render, closing a gap where any nested function was previously treated as a safe boundary regardless of whether it was actually invoked during render.react-x/refsnow reports a second guarded ref initialization: only a singleif (ref.current == null) { ref.current = ... }guarded initialization is allowed per ref per component/hook, and a second guarded write (in the same or a differentifblock) is reported asduplicateRefInit.react-x/refsnow supports.currentaccesses whose base is a member expression that looks like a ref (e.g.props.ref.current), not just a plain identifier.🏗️ Internal
packages/ast/src/check.ts.@effect/language-serviceto^0.86.4andpreactto^10.29.4.react-x/static-componentsinternals without changing behavior:findVariableForIdentifiernow delegates to@typescript-eslint/utils/ast-utils'sfindVariableinstead of a hand-rolled scope-chain walk,resolveDynamicValuewas split intofindDynamicCreationSiteandfindReassignmentCreationSite, and render-boundary/JSX-candidate handling was extracted into dedicated helpers.Check.isDirectiveandCheck.isIdentifierin@eslint-react/ast: both now take the node as the first argument and an optionalnameas the second, replacing the previous curried(name) => (node) => booleanshape. RemovedCheck.isStringLiteral; usets-pattern'sisMatchingor an inline type guard instead.Full Changelog: Rel1cx/eslint-react@v5.10.4...v5.11.0
v5.10.4Compare Source
🐞 Fixes
react-x/no-misused-capture-owner-stacknot recognizingprocess.env.NODE_ENVchecks wrapped in TypeScript type expressions such as(process.env as any).NODE_ENV. (#1813)Extract.getFullyQualifiedNameto unwrapTSAsExpression,TSTypeAssertion,TSNonNullExpression, andChainExpressionbefore resolving names. This improves name resolution for rules that identify React APIs or collect component/hook names through type-wrapped expressions.Full Changelog: Rel1cx/eslint-react@v5.10.3...v5.10.4
v5.10.3Compare Source
🏗️ Internal
typescript-eslintpackages to^8.62.1.@effect/language-serviceto^0.86.3.undiciandundici-typesto^8.6.0.@eslint-react/eslint-pluginpackage description.Full Changelog: Rel1cx/eslint-react@v5.10.2...v5.10.3
v5.10.2Compare Source
🐞 Fixes
<div {...{ [key]: value }} />) as static prop names. The actual property name is the runtime value of the variable; computed string literal keys are still recognized. Affected rules:react-x/no-missing-keyreact-jsx/no-children-prop-with-childrenreact-jsx/no-children-propreact-jsx/no-useless-fragmentreact-dom/no-dangerously-set-innerhtml-with-childrenreact-dom/no-dangerously-set-innerhtmlreact-dom/no-missing-button-typereact-dom/no-missing-iframe-sandboxreact-dom/no-string-style-propreact-dom/no-unsafe-iframe-sandboxreact-dom/no-unsafe-target-blankreact-dom/no-void-elements-with-childrenreact-web-api/no-leaked-event-listenerreact-web-api/no-leaked-fetchreact-x/unsupported-syntaxto no longer report IIFEs in JSX. This makes the rule consistent with the upstreamreact-hooks/unsupported-syntaxand removes theiifemessage.✨ New
react-x/unsupported-syntaxnow detectsevalcalls viaglobalThis.eval,globalThis["eval"], and type assertions like(globalThis as any).eval.🏗️ Internal
resolveparameter toExtract.getPropertyNameso callers can control how identifier and private identifier property names are resolved.Extract.getPropertyName.Full Changelog: Rel1cx/eslint-react@v5.10.1...v5.10.2
v5.10.1Compare Source
🐞 Fixes
static-componentsrule todisable-conflict-eslint-plugin-react-hooks, closes #1884.📝 Documentation
noCircularEffectrecipe sample to use@eslint-react/kitcollectors andsimpleTraverse, and updated the recipe overview accordingly.🏗️ Internal
typescript-eslint,@types/node,vite, andtailwindcss.fumadocs,lucide-react, andpostcssin the website.Full Changelog: Rel1cx/eslint-react@v5.10.0...v5.10.1
tailwindlabs/tailwindcss (@tailwindcss/postcss)
v4.3.3Compare Source
Fixed
--watch --poll[=ms]in@tailwindcss/cliwhen filesystem events are unreliable or unavailable (#20297)bg-[#fff]andbg-[#FFF]→bg-white) (#20298)iframe:focus-visibleoutline styles (#20292)theme('colors.foo')in JS plugins resolves correctly when both--color-fooand--color-foo-barexist (#20299)shadow-sm/12.5,text-shadow-sm/12.5,drop-shadow-sm/12.5, andinset-shadow-sm/12.5(#20302)[data-foo]divas two selectors instead of one (#20303)@tailwindcss/postcssrebuilds when a preprocessor like Sass changes the input CSS without changing the input file on disk (#20310)@tailwindcss/browserand Tailwind Play (#20124)oklch(#20314)--spacing(0)is optimized to0pxinstead of0so it remains a<length>when used incalc(…)(#20319)@parcel/watcheronly when needed in@tailwindcss/cli --watchmode, so one-off builds and--watch --pollwork when@parcel/watchercan't be loaded (#20325)system-uiandui-sans-serifso CJK text respects the page'slangattribute on Windows (#20318)@tailwindcss/upgradefrom rewriting ignored files when run from a subdirectory (#20329)@sourcerules pointing to nested files are scanned when later@sourcerules point to files in parent folders (#20335)@tailwindcss/vitefrom triggering full page reloads when scanned files are processed by Vite but haven't been loaded as modules yet (#20336)eslint/eslint (eslint)
v10.7.0Compare Source
Features
cf2a9bffeat: add errorClassNames option to preserve-caught-error rule (#21032) (sethamus)f8b873afeat: max-nested-callbacks option for constructor callbacks (#21063) (fnx)557fde8feat: support computedNumber.parseIntmember access inradixrule (#21041) (Pixel)0b4a73bfeat: add suggestions to no-compare-neg-zero (#21034) (den$)96cdd42feat: report invalid signed numeric radix values inradixrule (#21030) (Pixel)Bug Fixes
3e7bf15fix: applyignoreClassesWithImplementsto class expressions (#21069) (Pixel)0d7d70cfix: insert cause outside wrapping parens in preserve-caught-error (#21062) (Mahin Anowar)75ec753fix: handle static template literals ineqeqeqrule (#21058) (Pixel)b717a22fix: preventeqeqeqnull option from reporting non-equality operators (#21057) (Pixel)e35b05ffix: avoidno-invalid-regexpfalse positive for shadowed RegExp (#21051) (Pixel)a3172b6fix: avoidno-control-regexfalse positive for shadowed RegExp (#21050) (Pixel)d1f637efix: parenthesize sequence expression operands in no-implicit-coercion (#21045) (spokodev)8859baffix: avoid prefer-numeric-literals false positive for shadowed globals (#21047) (한국)a9e5961fix: use-isnan false positive on shadowed NaN/Number (#20958) (sethamus)8a240a7fix: avoid false positives inradixrule for spread arguments (#21044) (Pixel)Documentation
c30d808docs: Update README (GitHub Actions Bot)5139800docs: document ESLint migration codemods in v9 and v10 guides (#20980) (Alex Bit)04174cbdocs: Update README (GitHub Actions Bot)026e130docs: update semver policy for bug fixes (#21048) (Milos Djermanovic)9d42fefdocs: Update README (GitHub Actions Bot)b230159docs: Update README (GitHub Actions Bot)0129972docs: correct**/.jsglob to**/*.jsin config files guide (#21036) (EduardF1)Chores
9489379chore: update dependency @eslint/eslintrc to ^3.3.6 (#21076) (renovate[bot])81a4774chore: updates for v9.39.5 release (Jenkins)9835414chore: enable$ExpectTypeannotations in all TypeScript files (#21071) (Francesco Trotta)72adf6bchore: restrictmarkdownlint-cli2updates in renovate (#21067) (lumir)833ec10chore: update dependency prettier to v3.9.4 (#21061) (renovate[bot])7ea106dchore: update ecosystem plugins (#21059) (ESLint Bot)8fb550echore: add prettier update commit to.git-blame-ignore-revs(#21056) (lumir)e4e1166chore: update dependency prettier to v3.9.1 (#21055) (renovate[bot])0493f53chore: update prettier to v3.9.0 (#21054) (Pixel)1056a99chore: update dependency prettier to v3.8.5 (#21049) (renovate[bot])4d4155dci: run ecosystem tests on pull requests (#21027) (sethamus)993539fchore: update dependency @eslint/json to ^2.0.1 (#21042) (renovate[bot])53f8b69test: add error locations tono-constant-binary-expression(#21039) (lumir)5ab71d5refactor: clean up radix rule internals (#21015) (Pixel)a80a9a4chore: update ecosystem plugins (#21035) (ESLint Bot)7c9a029ci: add Node.js 26 to CI (#20847) (lumir)postcss/postcss (postcss)
v8.5.19Compare Source
beforefor new nodes inserted toRoot(by @MahinAnowar).v8.5.18Compare Source
opts.fromfolder for security reasons (useunsafeMap: trueto disable the check).v8.5.17Compare Source
Maximum call stack size exceedederror.postcss.fromJSON().Input#origin()for unmapped end position (by @chatman-media).prettier/prettier (prettier)
v3.9.5Compare Source
diff
Markdown: Cap ordered list mark at 999,999,999 (#19351 by @tats-u)
CommonMark parsers only support ordered list item numbers up to 999,999,999.
With this change, Prettier now caps the ordered list item number at 999,999,999 to ensure that the output is correctly parsed as an ordered list by CommonMark parsers. Numbers larger than 999,999,999 are not parsed as list item numbers and are left unchanged in the output:
Markdown: Avoid corrupting empty link with title (#19487 by @andersk)
Do not remove
<>from an inline link or image with an empty URL and a title, as this removal would change its interpretation.Less: Remove extra spaces after
[in map lookups (#19503 by @kovsu)CSS: Prevent addition space in
type()with+(#19516 by @bigandy)This fixes the addition space before
+in CSStype()declaration. For exampletype(<number>+)was being converted intotype(<number> +)which is invalid CSS and does not work.Less: Remove spaces between merge markers and colons (#19517 by @kovsu)
Markdown: Preserve wiki links with aliases (#19527 by @kovsu)
TypeScript: Fix comments being dropped on shorthand
typeimport/export specifiers (#19565 by @kirkwaiblinger)Miscellaneous: Preserving comments'
placementproperty (#19567 by @Janther)Prettier@3.9.0 deleted an undocumented property on comments, which was already used by plugins,
comment.placementis now available again after comment attach.Flow: Stop enforcing empty module declaration to break (#19568 by @fisker)
Angular: Support expression for exhaustive typechecking (#19571 by @fisker)
TypeScript: Ignore comments inside mapped type when checking type parameter comments (#19572 by @fisker)
Less: Fix adjacent block comments being corrupted (#19574 by @kovsu)
JavaScript: Handle dangling comments in
SwitchStatement(#19581 by @fisker)TypeScript: Remove space in comment-only object type (#19583 by @fisker)
tailwindlabs/tailwindcss (tailwindcss)
v4.3.3Compare Source
Fixed
--watch --poll[=ms]in@tailwindcss/cliwhen filesystem events are unreliable or unavailable (#20297)bg-[#fff]andbg-[#FFF]→bg-white) (#20298)iframe:focus-visibleoutline styles (#20292)theme('colors.foo')in JS plugins resolves correctly when both--color-fooand--color-foo-barexist (#20299)shadow-sm/12.5,text-shadow-sm/12.5,drop-shadow-sm/12.5, andinset-shadow-sm/12.5(#20302)[data-foo]divas two selectors instead of one (#20303)@tailwindcss/postcssrebuilds when a preprocessor like Sass changes the input CSS without changing the input file on disk (#20310)@tailwindcss/browserand Tailwind Play (#20124)oklch(#20314)--spacing(0)is optimized to0pxinstead of0so it remains a<length>when used incalc(…)(#20319)@parcel/watcheronly when needed in@tailwindcss/cli --watchmode, so one-off builds and--watch --pollwork when@parcel/watchercan't be loaded (#20325)system-uiandui-sans-serifso CJK text respects the page'slangattribute on Windows (#20318)@tailwindcss/upgradefrom rewriting ignored files when run from a subdirectory (#20329)@sourcerules pointing to nested files are scanned when later@sourcerules point to files in parent folders (#20335)@tailwindcss/vitefrom triggering full page reloads when scanned files are processed by Vite but haven't been loaded as modules yet (#20336)Configuration
📅 Schedule: (in timezone Europe/London)
🚦 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.
This PR was generated by Mend Renovate. View the repository job log.