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:
4.0.4
->5.1.1
15.3.0
->16.0.0
2.0.4
->5.0.1
v3
->v4
v3
->v4
v3
->v5
5.1.15
->7.0.6
5.2.6
->6.5.12
2.8.8
->3.4.2
3.29.5
->4.29.1
4.9.5
->5.7.2
Release Notes
rollup/plugins (@rollup/plugin-alias)
v5.1.1
2024-09-22
Bugfixes
v5.1.0
2023-11-25
Features
v5.0.1
Compare Source
2023-10-05
Bugfixes
v5.0.0
Compare Source
2023-04-04
Breaking Changes
rollup/plugins (@rollup/plugin-node-resolve)
v16.0.0
2024-12-15
Breaking Changes
v15.3.1
2024-12-15
Updates
test
withincludes
(#1787)sanity-io/eslint-config-studio (@sanity/eslint-config-studio)
v5.0.1
Compare Source
Bug Fixes
v5.0.0
Compare Source
⚠ BREAKING CHANGES
Features
v4.0.0
Compare Source
⚠ BREAKING CHANGES
@typescript-eslint/eslint-plugin
v7.5.0Features
@typescript-eslint/eslint-plugin
v7.5.0 (4c38dba)Bug Fixes
v3.0.1
Compare Source
Bug Fixes
v3.0.0
Compare Source
⚠ BREAKING CHANGES
Bug Fixes
actions/checkout (actions/checkout)
v4
Compare Source
actions/setup-node (actions/setup-node)
v4
Compare Source
codecov/codecov-action (codecov/codecov-action)
v5
Compare Source
What's Changed
Full Changelog: https://github.com/codecov/codecov-action/compare/v5.1.0..v5.1.1
v4
Compare Source
cssnano/cssnano (cssnano)
v7.0.6
: v7.0.6Compare Source
What's Changed
0ms
to0s
by @btea in https://github.com/cssnano/cssnano/pull/1665Full Changelog: https://github.com/cssnano/cssnano/compare/cssnano@7.0.5...cssnano@7.0.6
v7.0.5
Compare Source
v7.0.4
: v7.0.4Compare Source
Bug fixes
v7.0.3
: v7.0.3Compare Source
Bug Fixes
Thanks to @ota-meshi and @seiyab for their contributions to this release.
v7.0.2
: v7.0.2Compare Source
Bug Fixes
v7.0.1
: v7.0.1Compare Source
Patch changes
Update postcss-calc dependency to latest version
v7.0.0
: v7.0.0Compare Source
Breaking changes
This release drops official support for unmaintained long term support Node.js releases 14 and 16. It also drops support for non-long term support releases 19 and 21 and add support for Node.js 22. Only the
package.json
engines
field has been updated. The code should otherwise be identical to the previous 6.1.2 release.Ensuring support for older Node.js had become difficult as the GitHub actions runners are not available for the latest MacOS and recent pnpm also could not run on CI any more.
v6.1.2
: v6.1.2Compare Source
Bug Fixes
gap
andcolumn-gap
propertiesPatch Changes
v6.1.1
Compare Source
v6.1.0
: v6.1.0Compare Source
This release contains a lot of fixes to Browserslist support thanks to @colinrotherham
Features
Additionally, this release includes improved TypeScript types.
v6.0.5
: v6.0.5Compare Source
Bug Fixes
font
declaration in edge casesinitial
property in-webkit-line-clamp
v6.0.4
: v6.0.4Compare Source
Bug Fixes
@layer
declarations@layer
without any braces afterwardsv6.0.3
: v6.0.3Compare Source
Bug fixes
Other
v6.0.2
: v6.0.2Compare Source
@Property
v6.0.1
: v6.0.1Compare Source
Bug Fixes
v6.0.0
: v6.0.0Compare Source
Major Changes
99d1e6a
: postcss-normalize-url: remove normalize-url configuration options4e272f8
: postcss-svgo: Upgrade dependency svgo to v3 and increase the minimum supported node version to v14ca9d3f5
: Switch minimum supported Node version to 14 for all packages39a2040
: feat!(cssnano): remove undocumented YAML config supportMigration instructions
preactjs/preact-render-to-string (preact-render-to-string)
v6.5.12
Compare Source
Patch Changes
ed720ef
Thanks @JoviDeCroock! - Improve performance by pre-allocating arrays6db4f95
Thanks @rschristian! - SwitchHTML_LOWER_CASE
regex to match all from line start for a marginal perf benefit.v6.5.11
Compare Source
Patch Changes
62ade27
Thanks @rschristian! - Fixspellcheck={false}
not rendering asspellcheck="false"
v6.5.10
Compare Source
Patch Changes
d80e4dc
Thanks @marvinhagemeister! - Allow any value forclass
+className
as long as it's stringified to match browser behavior.v6.5.9
Compare Source
Patch Changes
4621fa3
Thanks @marvinhagemeister! - FixspellCheck={false}
not rendering asspellcheck="false"
v6.5.8
Compare Source
Patch Changes
220ad45
Thanks @JoviDeCroock! - Add async benchmarks and iterate on perf improvements883e02b
Thanks @JoviDeCroock! - General performance optimisations45b8e8b
Thanks @JoviDeCroock! - Improve perf a bit by hoisting the typeof check to reduce calling typeofv6.5.7
Compare Source
Patch Changes
481b4f3
Thanks @rschristian! - SupportdangerouslySetInnerHTML={undefined}
withrenderToStringAsync
v6.5.6
Compare Source
Patch Changes
054dae0
Thanks @ccouzens! - Fix issue where preactRenderToString returns a promise of a promisev6.5.5
Compare Source
Patch Changes
bebe4bf
Thanks @jacob-ebey! - fix: stop client runtime from being corruptedfix: insert ooo chunks in the proper order
v6.5.4
Compare Source
Patch Changes
7871a51
Thanks @dbergey! - Fix incorrect type for renderToPipeableStreamv6.5.3
Compare Source
Patch Changes
3044ac2
Thanks @rschristian! - Correct stream exports8c7e08f
Thanks @rschristian! - Add types for/stream
and/stream-node
exportsv6.5.2
Compare Source
Patch Changes
689e88d
Thanks @JoviDeCroock! - Correctly rendernull
as an__html
value as an empty stringv6.5.1
Compare Source
Patch Changes
62ade27
Thanks @rschristian! - Fixspellcheck={false}
not rendering asspellcheck="false"
v6.5.0
Compare Source
Minor Changes
a004914
Thanks @JoviDeCroock! - Introduce a streaming renderer which can be imported frompreact-render-to-string/stream
andpreact-render-to-string/stream-node
Patch Changes
a004914
Thanks @JoviDeCroock! - EnsurepopoverTarget
andpopoverTargetAction
are serialized to lower casea004914
Thanks @JoviDeCroock! - Fix for shallow rendering incorrectly transforming Fragments into other nodesa004914
Thanks @JoviDeCroock! - EnsurecellPadding
,cellSpacing
, anduseMap
are serialized to lower casea004914
Thanks @JoviDeCroock! - streaming rendering with Suspense boundaries as flush triggerv6.4.2
Compare Source
Patch Changes
7bc77a3
Thanks @marvinhagemeister! - Fix JSX template being detected as a top level Fragment when Deno's jsxprecompile
option is used303b8c0
Thanks @marvinhagemeister! - Perf: Remove unnecessary closure when rendering child nodesv6.4.1
Compare Source
Patch Changes
27a8b0e
Thanks @JoviDeCroock! - Ensure commonjs also has the async exportc46fb59
Thanks @marvinhagemeister! - Fix error thrown after suspending not being rethrown.4462822
Thanks @marvinhagemeister! - Fix invalid parent pointer empty value when rendering a suspended vnodev6.4.0
Compare Source
Minor Changes
6acc97a
Thanks @JoviDeCroock! - Allow prepass like behavior where a Promisewill be awaited and then continued, this is done with
the new
renderToStringAsync
exportPatch Changes
87d8c21
Thanks @Geo25rey! - fix external type definitions ofrenderToString
0a0d0ce
Thanks @acelaya! - Remove incorrect second default export from jsx.d.tsv6.3.1
Compare Source
Patch Changes
6bf321d
Thanks @marvinhagemeister! - Fix mapped children not working with Deno's new precompile JSX transform.v6.3.0
Compare Source
Minor Changes
926827c
Thanks @marvinhagemeister! - Add support for precompiled JSX transform, see https://deno.com/blog/v1.38#fastest-jsx-transform. Compared to traditional JSX transforms, the precompiled JSX transform tries to pre-serialize as much of the JSX as possible. That way less objects need to be created and serialized which relieves a lot of GC pressure.v6.2.2
Compare Source
Patch Changes
f1d81be
Thanks @JoviDeCroock! - avoid adding double colon for namespaced attributesv6.2.1
Compare Source
Patch Changes
a331699
Thanks @marvinhagemeister! - Fix incorrect casing of HTML attributes and SVG attributes017a8bb
Thanks @marvinhagemeister! - Fix casing of namespaced attribute namesbccd1d6
Thanks @gpoitch! - Apply attribute name handling in pretty modev6.2.0
Compare Source
Minor Changes
#305
568f139
Thanks @marvinhagemeister! - Add support for error boundaries viacomponentDidCatch
andgetDerivedStateFromError
This feature is disabled by default and can be enabled by toggling the
errorBoundaries
option:v6.1.0
Compare Source
Minor Changes
659b456
Thanks @marvinhagemeister! - Add experimental ability to render HTML comments via<Fragment UNSTABLE_comment="my-comment" />
. When theUNSTABLE_comment
prop is present all children of thatFragment
will be ignored and a HTML comment will be rendered instead. This feature is added to allow framework authors to experiment with marking DOM for hydration in the client. Note that it's marked as unstable and might change in the future.v6.0.3
Compare Source
Patch Changes
6a4b8ed
Thanks @shinyama-k! - Fix to add type file for jsx.jsv6.0.2
Compare Source
Patch Changes
637b302
Thanks @marvinhagemeister! - Bring back exports from 5.x to make migration easierv6.0.1
Compare Source
Patch Changes
8f4692c
Thanks @marvinhagemeister! - Fix error in commonjs entry pointv6.0.0
Compare Source
Major Changes
e8cbf66
Thanks @developit! - Improve performance by another 5-10% usingswitch
and short-circuiting, and move pretty-printing from intopreact-render-to-string/jsx
.6376f62
Thanks @JoviDeCroock! - Remove trailing space for void_elements, this could fail some test_assertions as<img />
will become<img/>
, the otherVOID_ELEMENTS
this will be applied forcan be found here
7a8b590
Thanks @JoviDeCroock! - Remove the castin to VNode forpreact/debug
, this is fixed in Preact >= 10.13.0Patch Changes
7a8b590
Thanks @JoviDeCroock! - Change style calculation to use a Set rather than Regexa0546fe
Thanks @JoviDeCroock! - Fix CJS export0b04860
Thanks @glenchao! - Enumerate draggable attribute, so the output isn'tdraggable
butdraggable="true"
3defa9d
Thanks @JoviDeCroock! - Follow up fixes to #27807ebc66
Thanks @JoviDeCroock! - Supportdata
attribute5c6877d
Thanks @developit! - improve unmount option hook call performance#278
8cf7cef
Thanks @JoviDeCroock! - Improve performance byx-link
regex.toLowerCase()
insteadprettier/prettier (prettier)
v3.4.2
Compare Source
diff
Treat U+30A0 & U+30FB in Katakana Block as CJK (#16796 by @tats-u)
Prettier doesn't treat U+30A0 & U+30FB as Japanese. U+30FB is commonly used in Japanese to represent the delimitation of first and last names of non-Japanese people or “and”. The following “C言語・C++・Go・Rust” means “C language & C++ & Go & Rust” in Japanese.
U+30A0 can be used as the replacement of the
-
in non-Japanese names (e.g. “Saint-Saëns” (Charles Camille Saint-Saëns) can be represented as “サン゠サーンス” in Japanese), but substituted by ASCII hyphen (U+002D) or U+FF1D (full width hyphen) in many cases (e.g. “サン=サーンス” or “サン=サーンス”).Fix comments print on class methods with decorators (#16891 by @fisker)
Fix non-idempotent formatting (#16899 by @seiyab)
This bug fix is not language-specific. You may see similar change in any languages. This fixes regression in 3.4.0 so change caused by it should yield same formatting as 3.3.3.
v3.4.1
Compare Source
diff
Remove unnecessary parentheses around assignment in
v-on
(#16887 by @fisker)<!-- Input --> <template> <button @​click="foo += 2">Click</button> </template> <!-- Prettier 3.4.0 --> <template> <button @​click="(foo += 2)">Click</button> </template> <!-- Prettier 3.4.1 --> <template> <button @​click="foo += 2">Click</button> </template>
v3.4.0
Compare Source
diff
🔗 Release Notes
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