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.3.1
->6.0.4
13.3.0
->15.3.0
v3
->v4
v3
->v4
v3
->v4
2.8.8
->3.3.3
3.1.4
->4.0.13
2.79.2
->4.24.0
4.9.5
->5.6.2
Release Notes
rollup/plugins (@rollup/plugin-babel)
v6.0.4
Compare Source
2023-10-05
Bugfixes
v6.0.3
Compare Source
2022-11-25
Updates
v6.0.2
Compare Source
2022-10-21
Updates
v6.0.1
Compare Source
Skipped for repo rebase
v6.0.0
2022-10-08
Breaking Changes
rollup/plugins (@rollup/plugin-node-resolve)
v15.3.0
2024-09-23
Features
v15.2.4
2024-09-22
Updates
v15.2.3
Compare Source
2023-10-08
Bugfixes
v15.2.2
Compare Source
2023-10-05
Bugfixes
v15.2.1
Compare Source
2023-08-22
Bugfixes
v15.2.0
Compare Source
2023-08-17
Features
v15.1.0
Compare Source
2023-05-30
Features
v15.0.2
Compare Source
2023-04-04
Bugfixes
v15.0.1
Compare Source
2022-10-21
Updates
v15.0.0
Compare Source
2022-10-10
Breaking Changes
v14.1.0
Compare Source
2022-09-12
Features
v14.0.1
Compare Source
2022-09-08
Bugfixes
v14.0.0
2022-09-06
Breaking Changes
actions/checkout (actions/checkout)
v4
Compare Source
actions/setup-node (actions/setup-node)
v4
Compare Source
codecov/codecov-action (codecov/codecov-action)
v4
Compare Source
prettier/prettier (prettier)
v3.3.3
Compare Source
diff
Add parentheses for nullish coalescing in ternary (#16391 by @cdignam-segment)
This change adds clarity to operator precedence.
Add parentheses for decorator expressions (#16458 by @y-schneider)
Prevent parentheses around member expressions or tagged template literals from being removed to follow the stricter parsing rules of TypeScript 5.5.
Support
@let
declaration syntax (#16474 by @sosukesuzuki)Adds support for Angular v18
@let
declaration syntax.Please see the following code example. The
@let
declaration allows you to define local variables within the template:For more details, please refer to the excellent blog post by the Angular Team: Introducing @let in Angular.
We also appreciate the Angular Team for kindly answering our questions to implement this feature.
v3.3.2
Compare Source
diff
Fix handlebars path expressions starts with
@
(#16358 by @Princeyadav05)v3.3.1
Compare Source
diff
Preserve empty lines in front matter (#16347 by @fisker)
Preserve explicit language in front matter (#16348 by @fisker)
Avoid line breaks in import attributes (#16349 by @fisker)
v3.3.0
Compare Source
diff
🔗 Release Notes
v3.2.5
Compare Source
diff
Support Angular inline styles as single template literal (#15968 by @sosukesuzuki)
Angular v17 supports single string inline styles.
Unexpected embedded formatting for Angular template (#15969 by @JounQin)
Computed template should not be considered as Angular component template
Use
"json"
parser fortsconfig.json
by default (#16012 by @sosukesuzuki)In v2.3.0, we introduced
"jsonc"
parser which adds trialing comma by default.When adding a new parser we also define how it will be used based on the
linguist-languages
data.tsconfig.json
is a special file used by TypeScript, it uses.json
file extension, but it actually uses the JSON with Comments syntax. However, we found that there are many third-party tools not recognize it correctly because of the confusing.json
file extension.We decide to treat it as a JSON file for now to avoid the extra configuration step.
To keep using the
"jsonc"
parser for yourtsconfig.json
files, add the following to your.pretterrc
filev3.2.4
Compare Source
diff
Fix incorrect parser inference (#15947 by @fisker)
Files like
.eslintrc.json
were incorrectly formatted as JSONC files.v3.2.3
Compare Source
diff
Throw errors for invalid code (#15881 by @fisker, @Josh-Cena, @auvred)
Fix parser inference (#15927 by @fisker)
v3.2.2
Compare Source
diff
Fix crash when parsing template literal CSS in a JSX style tag using a spread attribute (#15896 by @eelco)
For example this code would crash before:
Fix formatting error on optional call expression and member chain (#15920 by @sosukesuzuki)
v3.2.1
Compare Source
diff
Fix formatting error on member chain (#15915 by @sosukesuzuki)
v3.2.0
Compare Source
diff
🔗 Release Notes
v3.1.1
Compare Source
diff
Fix config file search (#15363 by @fisker)
Previously, we start search for config files from the filePath as a directory, if it happened to be a directory and contains config file, it will be used by mistake.
Skip explicitly passed symbolic links with
--no-error-on-unmatched-pattern
(#15533 by @sanmai-NL)Since Prettier v3, we stopped following symbolic links, however in some use cases, the symbolic link patterns can't be filtered out, and there is no way to prevent Prettier from throwing errors.
In Prettier 3.1.1, you can use
--no-error-on-unmatched-pattern
to simply skip symbolic links.Consistently use tabs in ternaries when
useTabs
istrue
(#15662 by @auvred)Improve config file search (#15663 by @fisker)
The Prettier config file search performance has been improved by more effective cache strategy.
Fix unstable and ugly formatting for comments in destructuring patterns (#15708 by @sosukesuzuki)
Support "Import Attributes" (#15718 by @fisker)
TypeScript 5.3 supports the latest updates to the import attributes proposal.
Fix false claim in docs that cursorOffset is incompatible with rangeStart/rangeEnd (#15750 by @ExplodingCabbage)
The cursorOffset option has in fact been compatible with rangeStart/rangeEnd for over 5 years, thanks to work by @ds300. However, Prettier's documentation (including the CLI
--help
text) continued to claim otherwise, falsely. The documentation is now fixed.Keep curly braces and
from
keyword in emptyimport
statements (#15756 by @fisker)Keep empty import attributes and assertions (#15757 by @fisker)
v3.1.0
Compare Source
diff
🔗 Release Notes
v3.0.3
Compare Source
diff
Add
preferUnplugged: true
topackage.json
(#15169 by @fisker and @so1ve)Prettier v3 uses dynamic imports, user will need to unplug Prettier when Yarn's PnP mode is enabled, add
preferUnplugged: true
topackage.json
, so Yarn will install Prettier as unplug by default.Support shared config that forbids
require()
(#15233 by @fisker)If an external shared config package is used, and the package
exports
don't haverequire
ordefault
export.In Prettier 3.0.2 Prettier fails when attempt to
require()
the package, and throws an error.Allow argument of
require()
to break (#15256 by @fisker)Do not print trailing commas in arrow function type parameter lists in
ts
code blocks (#15286 by @sosukesuzuki)Support TypeScript 5.2
using
/await using
declaration (#15321 by @sosukesuzuki)Support for the upcoming Explicit Resource Management feature in ECMAScript.
using
/await using
declarationv3.0.2
Compare Source
diff
Break after
=
of assignment if RHS is poorly breakable AwaitExpression or YieldExpression (#15204 by @seiyab)Do not add trailing comma for grouped scss comments (#15217 by @auvred)
Print
declare
andexport
keywords for nested namespace (#15249 by @sosukesuzuki)v3.0.1
Compare Source
diff
Fix cursor positioning for a special case (#14812 by @fisker)
Fix plugins/estree.d.ts to make it a module (#15018 by @kingyue737)
Add
export {}
inplugins/estree.d.ts
to fix the "File is not a module" errorAdd parenthesis around leading multiline comment in return statement (#15037 by @auvred)
Add support for Vue "Generic Components" (#15066 by @auvred)
https://blog.vuejs.org/posts/vue-3-3#generic-components
Fix comments print in
IfStatement
(#15076 by @fisker)Add missing type definition for
printer.preprocess
(#15123 by @so1ve)Add missing
getVisitorKeys
method type definition forPrinter
(#15125 by @auvred)Add typing to support
readonly
array properties of AST Node (#15127 by @auvred)Add space before unary minus followed by a function call (#15129 by @pamelalozano)
v3.0.0
Compare Source
diff
🔗 Release Notes
bvaughn/react-error-boundary (react-error-boundary)
v4.0.13
Compare Source
Removed references to ESLint config
kcd-scripts
frompackage.json
v4.0.12
Compare Source
v4.0.11
Compare Source
9b7b15b
)v4.0.10
Compare Source
v4.0.9
Compare Source
v4.0.8
Compare Source
v4.0.7
Compare Source
*Replaced post-processing
"use client"
insertion step with a custom Parcel plug-in. This should hopefully produce better source maps.v4.0.6
Compare Source
v4.0.5
Compare Source
Move
"use client"
directive to top of the bundled file.v4.0.4
Compare Source
README changes only
v4.0.3
Compare Source
withErrorBoundary
forwards refs"use client"
directivev4.0.2
Compare Source
Fix broken TypeScript definitions file (#133, https://github.com/parcel-bundler/parcel/issues/8908)
v4.0.1
Compare Source
ErrorBoundaryContext
around fallback UI as well, so theuseErrorBoundary
hook could be used within the fallback component to reset the boundary.For example:
See this demo: https://codesandbox.io/s/nostalgic-browser-e9lpmf
v4.0.0
Compare Source
useErrorHandler
hook withuseErrorBoundary
; can be used to trigger an error boundary or dismiss oneonReset
andonResetKeys
props; pass "details" object explaining the cause of the resetWhy did the
useErrorHandler
hook change?The old hook had two design flaws, both related to the
givenError
parameter:throw
this value. This seemed unnecessary, because if a component already has a reference to an error during render, it can justthrow
the value itself.null
orundefined
values. (Although an edge case, JavaScript enables throwing any values/types.)If you were using the
givenError
functionality– you can now just throw the value directly instead.How can I use the new
useErrorHandler
hook?Show the nearest error boundary from an event handler
React only handles errors thrown during render or during component lifecycle methods (e.g. effects and did-mount/did-update). Errors thrown in event handlers, or after async code has run, will not be caught.
This hook can be used to pass those errors to the nearest error boundary:
Dismiss the nearest error boundary
A fallback component can use this hook to request the nearest error boundary retry the render that original failed.
rollup/rollup (rollup)
v4.24.0
Compare Source
2024-10-02
Features
Pull Requests
v4.23.0
Compare Source
2024-10-01
Features
Pull Requests
v4.22.5
Compare Source
2024-09-27
Bug Fixes
Pull Requests
v4.22.4
Compare Source
2024-09-21
Bug Fixes
Pull Requests
v4.22.3
Compare Source
2024-09-21
Bug Fixes
Pull Requests
v4.22.2
Compare Source
2024-09-20
Bug Fixes
Pull Requests
v4.22.1
Compare Source
2024-09-20
Bug Fixes
Pull Requests
v4.22.0
Compare Source
2024-09-19
Features
Bug Fixes
Pull Requests
AggregateError
,FinalizationRegistry
,WeakRef
to knownGlobals (@re-taro)Configuration
📅 Schedule: Branch creation - "before 4am on Monday" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, 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.