feat: 3.0 compiler

[lxsmnsyc]

🚧 UNDER CONSTRUCTION 🚧

Goals

• [x] Add proper import identifier detection
• [x] Add proper support for client-server compilation variance
• [x] Add descriptive name generation for compiler-generated blocks
• [x] Rework compiler-generated blocks' prop generation
• [x] Add internal API for comparing block props
• [x] Rework compiler-generated code for Portals
• [ ] Rework For handling
• [x] Rework .map handling
• [x] Add internal API for managing renderPortalScope
• [x] Add support for compiling all JSX owned by the block component (unlike only return)
• [x] Rework auto mode

[CLAassistant]

All committers have signed the CLA.

[vercel[bot]]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
million-kitchen-sink	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jan 31, 2024 10:12pm
sink	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jan 31, 2024 10:12pm

[tobySolutions]

Amazing stuff!!! This is insane @lxsmnsyc!

[lxsmnsyc]

One big change is that block components no longer compile into block but into compiledBlock. compiledBlock manages both hoisted templates and portals via statically analyzing how much of the elements needs to be rendered into a portal.

Another thing that this unlocks is that you can now do branching statements inside block properly.

[tobySolutions]

One big change is that block components no longer compile into block but into compiledBlock. compiledBlock manages both hoisted templates and portals via statically analyzing how much of the elements needs to be rendered into a portal.

Another thing that this unlocks is that you can now do branching statements inside block properly.

Oh damn! That sounds awesome; and by "branching statements" you mean conditionals, yes?

[lxsmnsyc]

@tobySolutions yes. I believe the previous block compilation didn't support this, because of the compiler output for portals.

[tobySolutions]

@tobySolutions yes. I believe the previous block compilation didn't support this, because of the compiler output for portals.

Yes, you are right! Amazing work Alex, this is huge progress!

[lxsmnsyc]

Current issues (as per kitchen-sink), checked = fixed:

• [x] Guestbook (fixed by disabling queueMicrotask$)
  • State lagging (requires another re-render for the new item to render)
• [x] Markdown
  • Missing ref
• [ ] Million Quiz (crash because of fragment)
  • Cannot convert Symbol to string
• [x] QR Code
  • Missing ref
• [x] Task Tracker
  • Loses focus on state change when portal is defined as unstable
• [x] Todo List (fixed by disabling queueMicrotask$)
  • State Lagging (same with Guestbook)
• [x] Type Race
  • Flickering when portal is defined as unstable

Changes:

• JSX expressions that are defined in the children of a JSX element/fragment are automatically converted into portals.

Reworks left:

• Handle RSC
• Handle SVG

Tasks left:

• Skip expressions in JSX that are inferred as static values.
• Skip portal generation for literals.

[lxsmnsyc]

• _c has been disabled for now since there's no good metric for it to be enabled. It's tricky to know if a component is actually relying on some underlying React Fiber.
• unstable for renderReactScope is set to false for compilation since the old compilation doesn't have any scenario where it is true.
• rsc is yet to be supported.
• SSR needs to be handled. I'm lacking idea on that part but for now, compiledBlock is 1:1 code in both server and client.
• For children optimization has been skipped for now.
• Lacks warning logs for now.
• Telemetry is to be implemented.
• 62 out of 63 kitchen sink examples works properly. That one remaining is the Million Quiz example.
• auto has been disabled for now since, even though React encourages purity, they still have APIs that allow JSX mutation.

[lxsmnsyc]

@Aslemammad @aidenybai I'm closing this PR down, but not the branch, so feel free to backup things that you wanted.