next-data-hooks chore(deps): update all (major)

This PR contains the following updates:

Package	Change	Type	Update
@rollup/plugin-babel (source)	`5.3.1` -> `6.0.4`	devDependencies	major
@rollup/plugin-node-resolve (source)	`13.3.0` -> `15.3.0`	devDependencies	major
actions/checkout	`v3` -> `v4`	action	major
actions/setup-node	`v3` -> `v4`	action	major
codecov/codecov-action	`v3` -> `v4`	action	major
prettier (source)	`2.8.8` -> `3.3.3`	devDependencies	major
react-error-boundary	`3.1.4` -> `4.1.2`	devDependencies	major
rollup (source)	`2.79.2` -> `4.24.0`	devDependencies	major
typescript (source)	`4.9.5` -> `5.6.3`	devDependencies	major

Release Notes

rollup/plugins (@rollup/plugin-babel)

`v6.0.4`

Compare Source

2023-10-05

Bugfixes

fix: ensure rollup 4 compatibility #1595

`v6.0.3`

Compare Source

2022-11-25

Updates

docs: small typo in babel plugin readme #1355

`v6.0.2`

Compare Source

2022-10-21

Updates

chore: update rollup dependencies (3038271)

`v6.0.0`

2022-10-08

Breaking Changes

fix: prepare for Rollup 3 #1303

rollup/plugins (@rollup/plugin-node-resolve)

`v15.3.0`

2024-09-23

Features

feat: allow preferBuiltins to be a function (#1694)

`v15.2.4`

2024-09-22

Updates

chore: remove is-builtin-module (#1735)

`v15.2.3`

Compare Source

2023-10-08

Bugfixes

fix: modulePaths default is not set #1534

`v15.2.2`

Compare Source

2023-10-05

Bugfixes

fix: ensure rollup 4 compatibility #1595

`v15.2.1`

Compare Source

2023-08-22

Bugfixes

fix: Implement package exports / imports resolution algorithm according to Node documentation #1549

`v15.2.0`

Compare Source

2023-08-17

Features

feat: pass original importee to secondary resolve #1557

`v15.1.0`

Compare Source

2023-05-30

Features

feat: Resolve js/jsx/mjs/cjs imports from TypeScript files #1498

`v15.0.2`

Compare Source

2023-04-04

Bugfixes

fix: bump is-builtin-module version, imports with a trailing slash #1424

`v15.0.1`

Compare Source

2022-10-21

Updates

chore: update rollup dependencies (3038271)

`v15.0.0`

Compare Source

2022-10-10

Breaking Changes

fix: prepare for Rollup 3 #1288

`v14.1.0`

Compare Source

2022-09-12

Features

feat: add new option, modulePaths (#1104)

`v14.0.1`

Compare Source

2022-09-08

Bugfixes

fix: handle circular commonjs (#1259)

`v14.0.0`

2022-09-06

Breaking Changes

fix: preserve moduleSideEffects when re-resolving files (#1245)

actions/checkout (actions/checkout)

`v4`

Compare Source

Check out other refs/* by commit if provided, fall back to ref by @orhantoy in https://github.com/actions/checkout/pull/1924

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.

// Input
foo ? bar ?? foo : baz;
foo ?? bar ? a : b;
a ? b : foo ?? bar;

// Prettier 3.3.2
foo ? bar ?? foo : baz;
foo ?? bar ? a : b;
a ? b : foo ?? bar;

// Prettier 3.3.3
foo ? (bar ?? foo) : baz;
(foo ?? bar) ? a : b;
a ? b : (foo ?? bar);

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.

// Input
@&#8203;(foo`tagged template`)
class X {}

// Prettier 3.3.2
@&#8203;foo`tagged template`
class X {}

// Prettier 3.3.3
@&#8203;(foo`tagged template`)
class X {}

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:

@&#8203;let name = 'Frodo';

<h1>Dashboard for {{name}}</h1>
Hello, {{name}}

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)

{{! Input }}
<div>{{@&#8203;x.y.z}}</div>

{{! Prettier 3.3.1 }}
<div>{{@&#8203;x}}</div>

{{! Prettier 3.3.2 }}
<div>{{@&#8203;x.y.z}}</div>

`v3.3.1`

Compare Source

diff

Preserve empty lines in front matter (#16347 by @fisker)

<!-- Input -->
---
foo:
  - bar1

  - bar2

  - bar3
---
Markdown

<!-- Prettier 3.3.0 -->

---
foo:
  - bar1
  - bar2
  - bar3
---

Markdown

<!-- Prettier 3.3.1 -->
---
foo:
  - bar1

  - bar2

  - bar3
---

Markdown

Preserve explicit language in front matter (#16348 by @fisker)

<!-- Input -->
---yaml
title: Hello
slug: home
---

<!-- Prettier 3.3.0 -->
---
title: Hello
slug: home
---

<!-- Prettier 3.3.1 -->
---yaml
title: Hello
slug: home
---

Avoid line breaks in import attributes (#16349 by @fisker)

// Input
import something from "./some-very-very-very-very-very-very-very-very-long-path.json" with { type: "json" };

// Prettier 3.3.0
import something from "./some-very-very-very-very-very-very-very-very-long-path.json" with { type:
  "json" };

// Prettier 3.3.1
import something from "./some-very-very-very-very-very-very-very-very-long-path.json" with { type: "json" };

`v3.2.5`

Compare Source

diff

Support Angular inline styles as single template literal (#15968 by @sosukesuzuki)

Angular v17 supports single string inline styles.

// Input
@&#8203;Component({
  template: `<div>...</div>`,
  styles: `h1 { color: blue; }`,
})
export class AppComponent {}

// Prettier 3.2.4
@&#8203;Component({
  template: `<div>...</div>`,
  styles: `h1 { color: blue; }`,
})
export class AppComponent {}

// Prettier 3.2.5
@&#8203;Component({
  template: `<div>...</div>`,
  styles: `
    h1 {
      color: blue;
    }
  `,
})
export class AppComponent {}

Unexpected embedded formatting for Angular template (#15969 by @JounQin)

Computed template should not be considered as Angular component template

// Input
const template = "foobar";

@&#8203;Component({
  [template]: `<h1>{{       hello }}</h1>`,
})
export class AppComponent {}

// Prettier 3.2.4
const template = "foobar";

@&#8203;Component({
  [template]: `<h1>{{ hello }}</h1>`,
})
export class AppComponent {}

// Prettier 3.2.5
const template = "foobar";

@&#8203;Component({
  [template]: `<h1>{{       hello }}</h1>`,
})
export class AppComponent {}

Use `"json"` parser for `tsconfig.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 your tsconfig.json files, add the following to your .pretterrc file

{
  "overrides": [
    {
      "files": ["tsconfig.json", "jsconfig.json"],
      "options": {
        "parser": "jsonc"
      }
    }
  ]
}

`v3.2.4`

Compare Source

diff

Fix incorrect parser inference (#15947 by @fisker)

Files like .eslintrc.json were incorrectly formatted as JSONC files.

// Input
prettier --file-info .eslintrc.json
{ "ignored": false, "inferredParser": "jsonc" }

// Prettier 3.2.4
prettier --file-info .eslintrc.json
{ "ignored": false, "inferredParser": "json" }

`v3.2.3`

Compare Source

diff

Throw errors for invalid code (#15881 by @fisker, @Josh-Cena, @auvred)

// Input
1++;

// Prettier 3.2.2
1++;

// Prettier 3.2.3
SyntaxError: Invalid left-hand side expression in unary operation (1:1)
> 1 | 1++;
    | ^

// Input
try {} catch (error = 1){}

// Prettier 3.2.2
try {
} catch (error) {}

// Prettier 3.2.3
SyntaxError: Catch clause variable cannot have an initializer. (1:23)
> 1 | try {} catch (error = 1){}
    |                       ^

Fix parser inference (#15927 by @fisker)

// Prettier 3.2.2
prettier --file-info tsconfig.json
{ "ignored": false, "inferredParser": "json" }

// Prettier 3.2.3
prettier --file-info tsconfig.json
{ "ignored": false, "inferredParser": "jsonc" }

`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:

<style {...spread}>{`.{}`}</style>

Fix formatting error on optional call expression and member chain (#15920 by @sosukesuzuki)

// Input
a(() => {}, c?.d());

// Prettier 3.2.1
TypeError: Cannot read properties of undefined (reading 'type')

// Prettier 3.2.2
a(() => {}, c?.d());

`v3.2.1`

Compare Source

diff

Fix formatting error on member chain (#15915 by @sosukesuzuki)

// Input
test().test2().test2(thing?.something);

// Prettier 3.2.0
TypeError: Cannot read properties of undefined (reading 'type')

// Prettier 3.2.1
test().test2().test2(thing?.something);

`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.

├─ .prettierrc
└─ test.js         (A directory)
  └─ .prettierrc

// Prettier 3.1.0
await prettier.resolveConfigFile(new URL("./test.js", import.meta.url));
// <CWD>/test.js/.prettierrc

// Prettier 3.1.1
await prettier.resolveConfigFile(new URL("./test.js", import.meta.url));
// <CWD>/.prettierrc

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` is `true` (#15662 by @auvred)

// Input
aaaaaaaaaaaaaaa
	? bbbbbbbbbbbbbbbbbb
	: ccccccccccccccc
	  ? ddddddddddddddd
	  : eeeeeeeeeeeeeee
	    ? fffffffffffffff
	    : gggggggggggggggg;

// Prettier 3.1.0
aaaaaaaaaaaaaaa
	? bbbbbbbbbbbbbbbbbb
	: ccccccccccccccc
	  ? ddddddddddddddd
	  : eeeeeeeeeeeeeee
	    ? fffffffffffffff
	    : gggggggggggggggg;

// Prettier 3.1.1
aaaaaaaaaaaaaaa
	? bbbbbbbbbbbbbbbbbb
	: ccccccccccccccc
		? ddddddddddddddd
		: eeeeeeeeeeeeeee
			? fffffffffffffff
			: gggggggggggggggg;

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)

// Input
const {
  foo,
  // bar
  // baz
}: Foo = expr;

// Prettier 3.1.0
const {
  foo1,
} // bar
// baz
: Foo = expr;

// Prettier 3.1.0 second output
const {
  foo1, // bar
} // baz
: Foo = expr;

// Prettier 3.1.1
const {
  foo1,
  // bar
  // baz
}: Foo = expr;

Support "Import Attributes" (#15718 by @fisker)

TypeScript 5.3 supports the latest updates to the import attributes proposal.

import something from "./something.json" with { type: "json" };

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 empty `import` statements (#15756 by @fisker)

// Input
import { } from 'foo';
import { /* comment */ } from 'bar';

// Prettier 3.1.0
import {} from "foo";
import /* comment */ "bar";

// Prettier 3.1.1
import {} from "foo";
import {} from /* comment */ "bar";

Keep empty import attributes and assertions (#15757 by @fisker)

// Input
import foo from "foo" with {};
import bar from "bar" assert {};

// Prettier 3.1.0
import foo from "foo";
import bar from "bar";

// Prettier 3.1.1
import foo from "foo" with {};
import bar from "bar" assert {};

`v3.1.0`

Compare Source

diff

🔗 Release Notes

`v3.0.3`

Compare Source

diff

Add `preferUnplugged: true` to `package.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 to package.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 have require or default export.

In Prettier 3.0.2 Prettier fails when attempt to require() the package, and throws an error.

Error [ERR_PACKAGE_PATH_NOT_EXPORTED]: No "exports" main defined in <packageName>/package.json

Allow argument of `require()` to break (#15256 by @fisker)

// Input
const plugin = require(
  global.STANDALONE
    ? path.join(__dirname, "../standalone.js")
    : path.join(__dirname, "..")
);

// Prettier 3.0.2
const plugin = require(global.STANDALONE
  ? path.join(__dirname, "../standalone.js")
  : path.join(__dirname, ".."));

// Prettier 3.0.3
const plugin = require(
  global.STANDALONE
    ? path.join(__dirname, "../standalone.js")
    : path.join(__dirname, "..")
);

Do not print trailing commas in arrow function type parameter lists in `ts` code blocks (#15286 by @sosukesuzuki)

<!-- Input -->
```ts
const foo = <T>() => {}
```

<!-- Prettier 3.0.2 -->
```ts
const foo = <T,>() => {}
```

<!-- Prettier 3.0.3 -->
```ts
const foo = <T>() => {}
```

Support TypeScript 5.2 `using` / `await using` declaration (#15321 by @sosukesuzuki)

Support for the upcoming Explicit Resource Management feature in ECMAScript. using / await using declaration

{
   using foo = new Foo();
   await using bar = new Bar();
}

`v3.0.2`

Compare Source

diff

Break after `=` of assignment if RHS is poorly breakable AwaitExpression or YieldExpression (#15204 by @seiyab)

// Input
const { section, rubric, authors, tags } = await utils.upsertCommonData(mainData);

// Prettier 3.0.1
const { section, rubric, authors, tags } = await utils.upsertCommonData(
  mainData,
);

// Prettier 3.0.2
const { section, rubric, authors, tags } =
  await utils.upsertCommonData(mainData);

Do not add trailing comma for grouped scss comments (#15217 by @auvred)

/* Input */
$foo: (
	'property': (),
	// comment 1
	// comment 2
)

/* Prettier 3.0.1 */
$foo: (
  "property": (),
  // comment 1
  // comment 2,
);

/* Prettier 3.0.2 */
$foo: (
  "property": (),
  // comment 1
  // comment 2
);

Print `declare` and `export` keywords for nested namespace (#15249 by @sosukesuzuki)

// Input
declare namespace abc1.def {}
export namespace abc2.def {}

// Prettier 3.0.1
namespace abc1.def {}
namespace abc2.def {}

// Prettier 3.0.2
declare namespace abc1.def {}
export namespace abc2.def {}

`v3.0.1`

Compare Source

diff

Fix cursor positioning for a special case (#14812 by @fisker)

// <|> is the cursor position

/* Input */
// All messages are represented in JSON.
// So, the prettier.py controls a subprocess which spawns "node {this_file}".
import {<|>  } from "fs"

/* Prettier 3.0.0 */
// All messages are represented in JSON.
// So, the prettier.py <|>controls a subprocess which spawns "node {this_file}".
import {} from "fs"

/* Prettier 3.0.1 */
// All messages are represented in JSON.
// So, the prettier.py controls a subprocess which spawns "node {this_file}".
import {<|>} from "fs"

Fix plugins/estree.d.ts to make it a module (#15018 by @kingyue737)

Add export {} in plugins/estree.d.ts to fix the "File is not a module" error

Add parenthesis around leading multiline comment in return statement (#15037 by @auvred)

// Input
function fn() {
  return (
    /**
     * @&#8203;type {...}
     */ expresssion
  )
}

// Prettier 3.0.0
function fn() {
  return /**
   * @&#8203;type {...}
   */ expresssion;
}

// Prettier 3.0.1
function fn() {
  return (
    /**
     * @&#8203;type {...}
     */ expresssion
  );
}

Add support for Vue "Generic Components" (#15066 by @auvred)

https://blog.vuejs.org/posts/vue-3-3#generic-components

<!-- Input -->
<script setup lang="ts" generic="T extends Type1 & Type2 & (Type3 | Type4), U extends string | number | boolean"></script>

<!-- Prettier 3.0.0 -->
<script
  setup
  lang="ts"
  generic="T extends Type1 & Type2 & (Type3 | Type4), U extends string | number | boolean"
></script>

<!-- Prettier 3.0.1 -->
<script
  setup
  lang="ts"
  generic="
    T extends Type1 & Type2 & (Type3 | Type4),
    U extends string | number | boolean
  "
></script>

Fix comments print in `IfStatement` (#15076 by @fisker)

function a(b) {
  if (b) return 1; // comment
  else return 2;
}

/* Prettier 3.0.0 */
Error: Comment "comment" was not printed. Please report this error!

/* Prettier 3.0.1 */
function a(b) {
  if (b) return 1; // comment
  else return 2;
}

Add missing type definition for `printer.preprocess` (#15123 by @so1ve)

export interface Printer<T = any> {
  // ...
+ preprocess?:
+   | ((ast: T, options: ParserOptions<T>) => T | Promise<T>)
+   | undefined;
}

Add missing `getVisitorKeys` method type definition for `Printer` (#15125 by @auvred)

const printer: Printer = {
  print: () => [],
  getVisitorKeys(node, nonTraversableKeys) {
    return ["body"];
  },
};

Add typing to support `readonly` array properties of AST Node (#15127 by @auvred)

// Input
interface TestNode {
  readonlyArray: readonly string[];
}

declare const path: AstPath<TestNode>;

path.map(() => "", "readonlyArray");

// Prettier 3.0.0
interface TestNode {
  readonlyArray: readonly string[];
}

declare const path: AstPath<TestNode>;

path.map(() => "", "readonlyArray");
//                  ^ Argument of type '"readonlyArray"' is not assignable to parameter of type '"regularArray"'. ts(2345)

// Prettier 3.0.1
interface TestNode {
  readonlyArray: readonly string[];
}

declare const path: AstPath<TestNode>;

path.map(() => "", "readonlyArray");

Add space before unary minus followed by a function call (#15129 by @pamelalozano)

// Input
div {
  margin: - func();
}

// Prettier 3.0.0
div {
  margin: -func();
}

// Prettier 3.0.1
div {
  margin: - func();
}

`v3.0.0`

Compare Source

diff

🔗 Release Notes

bvaughn/react-error-boundary (react-error-boundary)

Removed references to ESLint config kcd-scripts from package.json

`v4.0.12`

Compare Source

Support null fallback prop (#169)

`v4.0.11`

Compare Source

Re-throw original error in the event that no fallback is specified (#160)
Improved exported prop types def (#152)
Bundle built with Preconstruct (#144, #149, 9b7b15b)

`v4.0.10`

Compare Source

Target Safari 12+ compatibility (by removing optional chaining operator and default parameters)

`v4.0.9`

Compare Source

`v4.0.8`

Compare Source

144: Build release bundle with Preconstruct

`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

Removed arrow function syntax to support older versions of Safari

`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
Add "use client" directive

`v4.0.2`

Compare Source

Fix broken TypeScript definitions file (#133, https://github.com/parcel-bundler/parcel/issues/8908)

`v4.0.1`

Compare Source

Render ErrorBoundaryContext around fallback UI as well, so the useErrorBoundary hook could be used within the fallback component to reset the boundary.

For example:

import { useErrorBoundary } from "react-error-boundary";

function ErrorFallback({ error }) {
  const { resetBoundary } = useErrorBoundary();

  return (
    <div role="alert">
      <p>Something went wrong:</p>
      <pre style={{ color: "red" }}>{error.message}</pre>
      <button onClick={resetBoundary}>Try again</button>
    </div>
  );
}

See this demo: https://codesandbox.io/s/nostalgic-browser-e9lpmf

`v4.0.0`

Compare Source

Replace useErrorHandler hook with useErrorBoundary; can be used to trigger an error boundary or dismiss one
Merge onReset and onResetKeys props; pass "details" object explaining the cause of the reset

Why did the `useErrorHandler` hook change?

The old hook had two design flaws, both related to the givenError parameter:

All the hook did was throw this value. This seemed unnecessary, because if a component already has a reference to an error during render, it can just throw the value itself.

It would not properly re-throw null or undefined 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.

// Before
function Greeting() {
  const [name, setName] = React.useState('')
  const {greeting, error} = useGreeting(name)
  useErrorHandler(error)

// After
function Greeting() {
  const [name, setName] = React.useState('')
  const {greeting, error} = useGreeting(name)
  if (error) {
    throw error;
  }

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:

import { useErrorBoundary } from "react-error-boundary";

function Example() {
  const { showBoundary } = useErrorBoundary();

  useEffect(() => {
    fetchGreeting(name).then(
      response => {
        // Set data in state and re-render
      },
      error => {
        // Show error boundary
        showBoundary(error);
      }
    );
  });

  // Render ...
}

Dismiss the nearest error boundary

A fallback component can use this hook to request the nearest error boundary retry the render that original failed.

import { useErrorBoundary } from "react-error-boundary";

function ErrorFallback({ error }) {
  const { resetBoundary } = useErrorBoundary();

  return (
    <div role="alert">
      <p>Something went wrong:</p>
      <pre style={{ color: "red" }}>{error.message}</pre>
      <button onClick={resetBoundary}>Try again</button>
    </div>
  );
}

rollup/rollup (rollup)

`v4.24.0`

Compare Source

2024-10-02

Features

Support preserving and transpiling JSX syntax (#5668)

Pull Requests

#5668: Introduce JSX support (@lukastaegert, @Martin-Idel, @felixhuttmann, @AlexDroll, @tiptr)

`v4.23.0`

Compare Source

2024-10-01

Features

Collect all emitted names and originalFileNames for assets (#5686)

Pull Requests

#5686: Add names and originalFileNames to assets (@lukastaegert)

`v4.22.5`

Compare Source

2024-09-27

Bug Fixes

Allow parsing of certain unicode characters again (#5674)

Pull Requests

#5674: Fix panic with unicode characters (@sapphi-red, @lukastaegert)
#5675: chore(deps): update dependency rollup to v4.22.4 [security] (@renovate[bot])
#5680: chore(deps): update dependency @rollup/plugin-commonjs to v28 (@renovate[bot], @lukastaegert)
#5681: chore(deps): update dependency @rollup/plugin-replace to v6 (@renovate[bot])
#5682: chore(deps): update dependency @rollup/plugin-typescript to v12 (@renovate[bot])
#5684: chore(deps): lock file maintenance minor/patch updates (@renovate[bot])

`v4.22.4`

Compare Source

2024-09-21

Bug Fixes

Fix a vulnerability in generated code that affects IIFE, UMD and CJS bundles when run in a browser context (#5671)

Pull Requests

#5670: refactor: Use object.prototype to check for reserved properties (@YuHyeonWook)
#5671: Fix DOM Clobbering CVE (@lukastaegert)

`v4.22.3`

Compare Source

2024-09-21

Bug Fixes

Ensure that mutations in modules without side effects are observed while properly handling transitive dependencies (#5669)

Pull Requests

#5669: Ensure impure dependencies of pure modules are added (@lukastaegert)

`v4.22.2`

Compare Source

2024-09-20

Bug Fixes

Revert fix for side effect free modules until other issues are investigated (#5667)

Pull Requests

#5667: Partially revert #5658 and re-apply #5644 (@lukastaegert)

`v4.22.1`

Compare Source

2024-09-20

Bug Fixes

Revert #5644 "stable chunk hashes" while issues are being investigated

Pull Requests

#5663: chore(deps): update dependency inquirer to v11 (@renovate[bot], @lukastaegert)
#5664: chore(deps): lock file maintenance minor/patch updates (@renovate[bot])
#5665: fix: type in CI file (@YuHyeonWook)
#5666: chore(deps): lock file maintenance minor/patch updates (@renovate[bot])

`v4.22.0`

Compare Source

2024-09-19

Features

Add additional known global values to avoid access side effects (#5651)

Bug Fixes

Ensure deterministic chunk hash generation despite async renderChunk hook (#5644)
Improve side effect detection when using "smallest" treeshaking preset when imports are optimized away (#5658)

Pull Requests

#5644: fix: apply final hashes deterministically with stable placeholders set (@mattkubej, @lukastaegert)
#5646: chore(deps): update dependency @mermaid-js/mermaid-cli to v11 (@renovate[bot])
#5647: chore(deps): update dependency concurrently to v9 (@renovate[bot])
#5648: chore(deps): lock file maintenance minor/patch updates (@renovate[bot])
#5651: feat: add AggregateError, FinalizationRegistry, WeakRef to knownGlobals (@re-taro)
#5653: Fix example selection in REPL (@lukastaegert)
#5657: chore(deps): update depend

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.

[ ] If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

Feb 06 '23 01:02 renovate[bot]

⚠ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

any of the package files in this branch needs updating, or
the branch becomes conflicted, or
you click the rebase/retry checkbox if found above, or
you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json

npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: @typescript-eslint/[email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/eslint
npm ERR!   dev eslint@"9.2.0" from the root project
npm ERR!   peer eslint@"^7.5.0 || ^8.0.0 || ^9.0.0" from @babel/[email protected]
npm ERR!   node_modules/@babel/eslint-parser
npm ERR!     dev @babel/eslint-parser@"7.24.5" from the root project
npm ERR!     @babel/eslint-parser@"^7.16.3" from [email protected]
npm ERR!     node_modules/eslint-config-react-app
npm ERR!       dev eslint-config-react-app@"7.0.1" from the root project
npm ERR!   3 more (@eslint-community/eslint-utils, ...)
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer eslint@"^8.56.0" from @typescript-eslint/[email protected]
npm ERR! node_modules/@typescript-eslint/eslint-plugin
npm ERR!   dev @typescript-eslint/eslint-plugin@"7.8.0" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: [email protected]
npm ERR! node_modules/eslint
npm ERR!   peer eslint@"^8.56.0" from @typescript-eslint/[email protected]
npm ERR!   node_modules/@typescript-eslint/eslint-plugin
npm ERR!     dev @typescript-eslint/eslint-plugin@"7.8.0" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! See /tmp/renovate/cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /tmp/renovate/cache/others/npm/_logs/2024-05-06T08_20_00_011Z-debug-0.log

Apr 05 '24 21:04 renovate[bot]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

any of the package files in this branch needs updating, or
the branch becomes conflicted, or
you click the rebase/retry checkbox if found above, or
you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json

npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: [email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/react
npm ERR!   dev react@"19.2.0" from the root project
npm ERR!   peer react@"^19.2.0" from [email protected]
npm ERR!   node_modules/react-dom
npm ERR!     dev react-dom@"19.2.0" from the root project
npm ERR!   3 more (react-test-renderer, styled-jsx, react-error-boundary)
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer react@"^18.2.0" from [email protected]
npm ERR! node_modules/next
npm ERR!   dev next@"13.4.19" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: [email protected]
npm ERR! node_modules/react
npm ERR!   peer react@"^18.2.0" from [email protected]
npm ERR!   node_modules/next
npm ERR!     dev next@"13.4.19" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! See /runner/cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /runner/cache/others/npm/_logs/2025-11-24T10_33_03_493Z-debug-0.log

Oct 06 '25 08:10 renovate[bot]

next-data-hooks next-data-hooks copied to clipboard

chore(deps): update all (major)

Release Notes

Bugfixes

Updates

Updates

Breaking Changes

Features

Updates

Bugfixes

Bugfixes

Bugfixes

Features

Features

Bugfixes

Updates

Breaking Changes

Features

Bugfixes

Breaking Changes

Add parentheses for nullish coalescing in ternary (#​16391 by @​cdignam-segment)

Add parentheses for decorator expressions (#​16458 by @​y-schneider)

Support @let declaration syntax (#​16474 by @​sosukesuzuki)

Fix handlebars path expressions starts with @ (#​16358 by @​Princeyadav05)

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)

Support Angular inline styles as single template literal (#​15968 by @​sosukesuzuki)

Unexpected embedded formatting for Angular template (#​15969 by @​JounQin)

Use "json" parser for tsconfig.json by default (#​16012 by @​sosukesuzuki)

Fix incorrect parser inference (#​15947 by @​fisker)

Throw errors for invalid code (#​15881 by @​fisker, @​Josh-Cena, @​auvred)

Fix parser inference (#​15927 by @​fisker)

Fix crash when parsing template literal CSS in a JSX style tag using a spread attribute (#​15896 by @​eelco)

Fix formatting error on optional call expression and member chain (#​15920 by @​sosukesuzuki)

Fix formatting error on member chain (#​15915 by @​sosukesuzuki)

Fix config file search (#​15363 by @​fisker)

Skip explicitly passed symbolic links with --no-error-on-unmatched-pattern (#​15533 by @​sanmai-NL)

Consistently use tabs in ternaries when useTabs is true (#​15662 by @​auvred)

Improve config file search (#​15663 by @​fisker)

Fix unstable and ugly formatting for comments in destructuring patterns (#​15708 by @​sosukesuzuki)

Support "Import Attributes" (#​15718 by @​fisker)

Fix false claim in docs that cursorOffset is incompatible with rangeStart/rangeEnd (#​15750 by @​ExplodingCabbage)

Keep curly braces and from keyword in empty import statements (#​15756 by @​fisker)

Keep empty import attributes and assertions (#​15757 by @​fisker)

Add preferUnplugged: true to package.json (#​15169 by @​fisker and @​so1ve)

Support shared config that forbids require() (#​15233 by @​fisker)

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)

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 and export keywords for nested namespace (#​15249 by @​sosukesuzuki)

Fix cursor positioning for a special case (#​14812 by @​fisker)

Fix plugins/estree.d.ts to make it a module (#​15018 by @​kingyue737)

Add parenthesis around leading multiline comment in return statement (#​15037 by @​auvred)

Add support for Vue "Generic Components" (#​15066 by @​auvred)

Fix comments print in IfStatement (#​15076 by @​fisker)

Add missing type definition for printer.preprocess (#​15123 by @​so1ve)

Add missing getVisitorKeys method type definition for Printer (#​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)

Why did the useErrorHandler hook change?

How can I use the new useErrorHandler hook?

Show the nearest error boundary from an event handler

Dismiss the nearest error boundary

Features

Pull Requests

Features

Pull Requests

Bug Fixes

Pull Requests

Bug Fixes

Pull Requests

Bug Fixes

Pull Requests

Bug Fixes

Pull Requests

Bug Fixes

Pull Requests

next-data-hooks
next-data-hooks copied to clipboard

Add parentheses for nullish coalescing in ternary (#16391 by @cdignam-segment)

Add parentheses for decorator expressions (#16458 by @y-schneider)

Support `@let` declaration syntax (#16474 by @sosukesuzuki)

Fix handlebars path expressions starts with `@` (#16358 by @Princeyadav05)

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)

Support Angular inline styles as single template literal (#15968 by @sosukesuzuki)

Unexpected embedded formatting for Angular template (#15969 by @JounQin)

Use `"json"` parser for `tsconfig.json` by default (#16012 by @sosukesuzuki)

Fix incorrect parser inference (#15947 by @fisker)

Throw errors for invalid code (#15881 by @fisker, @Josh-Cena, @auvred)

Fix parser inference (#15927 by @fisker)

Fix crash when parsing template literal CSS in a JSX style tag using a spread attribute (#15896 by @eelco)

Fix formatting error on optional call expression and member chain (#15920 by @sosukesuzuki)

Fix formatting error on member chain (#15915 by @sosukesuzuki)

Fix config file search (#15363 by @fisker)

Skip explicitly passed symbolic links with `--no-error-on-unmatched-pattern` (#15533 by @sanmai-NL)

Consistently use tabs in ternaries when `useTabs` is `true` (#15662 by @auvred)

Improve config file search (#15663 by @fisker)

Fix unstable and ugly formatting for comments in destructuring patterns (#15708 by @sosukesuzuki)

Support "Import Attributes" (#15718 by @fisker)

Fix false claim in docs that cursorOffset is incompatible with rangeStart/rangeEnd (#15750 by @ExplodingCabbage)

Keep curly braces and `from` keyword in empty `import` statements (#15756 by @fisker)

Keep empty import attributes and assertions (#15757 by @fisker)

Add `preferUnplugged: true` to `package.json` (#15169 by @fisker and @so1ve)

Support shared config that forbids `require()` (#15233 by @fisker)

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)

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` and `export` keywords for nested namespace (#15249 by @sosukesuzuki)

Fix cursor positioning for a special case (#14812 by @fisker)

Fix plugins/estree.d.ts to make it a module (#15018 by @kingyue737)

Add parenthesis around leading multiline comment in return statement (#15037 by @auvred)

Add support for Vue "Generic Components" (#15066 by @auvred)

Fix comments print in `IfStatement` (#15076 by @fisker)

Add missing type definition for `printer.preprocess` (#15123 by @so1ve)

Add missing `getVisitorKeys` method type definition for `Printer` (#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)

Why did the `useErrorHandler` hook change?

How can I use the new `useErrorHandler` hook?