@trueadm.dev Can Svelte ship this? Or does Svelte need this?

is it really translate's problem? won't every extension that mutates DOM cause the same issue, & this one just happens to be popular enough people notice it
feel like its not the job of every ext to account for react's design & its not react's job to account for every ext. so maybe its not fixable

Prompt Engineer

To be clear, I'm most excited for client-only apps.
- client-side form actions (svelte has nothing for client side)
- `ref` improvements (better than svelte bind:this)
- React Router v7 (miles better than +page)
- Jotai (close to Svelte $state, without compiler tricks)
- Compiler (nuf said)

Sorry, some typos. 😬
`/zh-Hans/t-b.html` -> `/zh-Hans/t-a.html`,
`/tutorial-one.html` -> `/t-a.html`

It seems that Github issues are more suitable for discussing the problem. Sorry to bother you.

Thank you very much for your reply! 🙏

If necessary, I will cancel the static export of my website and use `rewrites()` to solve this problem. I just think it would be much more convenient for many websites if this effect can also be achieved in static exports. I am also curious about the progress of the bug.

This is a popular url organization for websites that need multilingual/internationalization.

I know that this problem can be solved by using Next.js's `rewrites()` API, but these dynamic APIs are not available in static exports.