Fatih Aygün

Actually Rakkas needs to print errors and warnings in a lot more situations than this. It is part of the 0.6.1 journey.

Released in `0.6.1-next.0` (test with `npm i rakkasjs@next`). I'm waiting for Vite 3.1 to release `0.6.1`. Just drop a line if it doesn't solve your problem and I'll reopen the...

Next.js added [on-demand revalidation](https://nextjs.org/blog/next-12-1#on-demand-incremental-static-regeneration-beta) for incrementally rendered pages which makes this feature much more usable. Almost essential to have.

This doesn't work right now: It results in syntax errors because it leaves JSX untransformed in some cases. It seems to be because of the `restoreJsx` plugin: The Babel JSX...

Turns out it requires an uncommon combination: a React component in `node_modules`, excluded from `optimizeDeps`. I've been looking but I haven't been able to find a React component package that...

TLDR: We have two problems. 1. `restoreJsx` is not working most of the time because it can't parse optimized deps. 2. `restoreJsx` breaks this PR under rare circumstances. It would...

The problem is briefly: - The `restoreJsx` plugin compiles `React.createElement` calls back to JSX. - Without this PR, Babel compiles that JSX back to JS, so everything works. - But...

Here's a [repo that demonstrates the issue](https://github.com/cyco130/vite-esbuild-jsx-issue). I'll copy some info here for convenience. The **Before this PR** section explains why I think it's fine to remove the `restoreJsx` transform,...

> Maybe we could find a way to run `restoreJSX` before the optimizer 🤔 Isn't removing Babel one of the main goals here though?

Not yet, but I had the use case in mind, so it's not too hard. What's your use case? Caching in `localStorage` etc.? Or local cache for parts of the...