Sukka

[appDir] Next.js can't pickup css imports from client components

14

### Verify canary release - [X] I verified that the issue exists in the latest Next.js canary release ### Provide environment information Operating System: Platform: linux Arch: x64 Version: Ubuntu...

types(#42003): better typing for `next/link`

10

The PR closes #42003. Replace `(e: any) => void` with `React.MouseEventHandler` and `React.TouchEventHandler`. The original typing overlap issue has also been fixed. ## Bug - [x] Related issues linked using...

[Bug report] Remove useLatest

3

https://github.com/streamich/react-use/blob/3685b7502a4d1980953deed11c3dee31b220c89d/src/useLatest.ts#L3-L7 Although the current React documentation doesn't mention it, according to [the React beta documentation](https://beta.reactjs.org/apis/useref): > Do not write or read `ref.current` during rendering. > React expects that the body...

parentNode returns null

4

```javascript const domParser = require("dom-parser"); const parser = new domParser(); const html = ` Example Domain This domain is established to be used for illustrative examples in documents. You may...

types: better type definition for internal utils

2

The PR removes some `as unknown as` assertions by improving type definitions.

https://react.dev/blog/2018/06/07/you-probably-dont-need-derived-state The page is not redirected to `legacy.reactjs.org`. And https://legacy.reactjs.org/blog/2018/06/07/you-probably-dont-need-derived-state is also 404 (missing `.html`). https://legacy.reactjs.org/blog/2018/06/07/you-probably-dont-need-derived-state.html is fine.

[Beta] Migrating Error Decoder

3

`beta.reactjs.org` currently missing `/error-decoder` (E.g. https://reactjs.org/docs/error-decoder.html/?invariant=421). https://beta.reactjs.org/docs/error-decoder.html/?invariant=421 will be redirected to ~~https://legacy.reactjs.org/error-decoder.html?invariant=421 which becomes 404.~~ https://legacy.reactjs.org/docs/error-decoder.html?invariant=421

[HTTP/2] Aborted requests for same domain might fail unexpectedly

3

## Bug Description As the title, pipelined requests might fail unexpectedly if another request toward the same domain has been aborted: ``` node:assert:399 throw err; ^ AssertionError [ERR_ASSERTION]: The expression...

Fail to bundle `npm/lib/cli-entry.js` and `@npmcli/arborist`

6

https://bundlejs.com/?q=npm%2Flib%2Fcli-entry.js The error during the bundling: ``` http-url:https://unpkg.com/[email protected]/lib/:1:1 ``` Where `https://unpkg.com/[email protected]/lib/` returns HTML (404) while `https://unpkg.com/[email protected]/lib/index.js` does return JS. Is there any option that enables node-like resolving?