Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
ad7b4b0 to
2ea7804
Compare
| }, | ||
| { | ||
| name: 'function-scope-beats-module-scope', | ||
| name: 'todo-function-scope-does-not-beat-module-scope', |
There was a problem hiding this comment.
See attached snap fixture -- playground and the babel plugin diverged before this PR
Compiler playground now runs the entire program through `babel-plugin-react-compiler` instead of a custom pipeline which previously duplicated function inference logic from `Program.ts`. In addition, the playground output reflects the tranformed file (instead of a "virtual file" of manually concatenated functions). This helps with the following: - Reduce potential discrepencies between playground and babel plugin behavior. See attached fixture output for an example where we previously diverged. - Let playground users see compiler-inserted imports (e.g. `_c` or `useFire`) This also helps us repurpose playground into a more general tool for compiler-users instead of just for compiler engineers. - imports and other functions are preserved. We differentiate between imports and globals in many cases (e.g. `inferEffectDeps`), so it may be misleading to omit imports in printed output - playground now shows other program-changing behavior like position of outlined functions and hoisted declarations - emitted compiled functions do not need synthetic names
josephsavona
left a comment
There was a problem hiding this comment.
yesss this is so good! The changes to the HMR setting make sense
| @@ -1,4 +1,5 @@ | |||
| function TestComponent(t0) { | |||
| import { c as _c } from "react/compiler-runtime"; | |||
There was a problem hiding this comment.
Note that we now print inserted imports. Other program level changes (e.g. Options.gating, outlining) should work as expected without hardcoding
| import { c as _c } from "react/compiler-runtime"; | ||
| function useFoo(propVal) { | ||
| const $ = _c(2); | ||
| const t0 = (propVal.baz: number); |
There was a problem hiding this comment.
Flow now codegens and prints successfully. This means that Flow users can use playground without needing to edit / manually strip their annotations
| } else { | ||
| t0 = $[0]; | ||
| } | ||
| const x = t0 as number; |
There was a problem hiding this comment.
Typescript also codegens successfully 🎉 No type annotation changes needed
…act into issue-31578-setter-arity-gcc * 'issue-31578-setter-arity-gcc' of github.com:/davesnx/react: [flags] Clean up scheduler flags (facebook#31814) Enable debugRenderPhaseSideEffectsForStrictMode in test renderers (facebook#31761) Enable disableDefaultPropsExceptForClasses (facebook#31804) Turn on useModernStrictMode in test renderers (facebook#31769) [compiler][ez] Add shape for global Object.keys (facebook#31583) [compiler] Context variables as dependencies (facebook#31582) [compiler] Add fire to known React APIs (facebook#31795) [compiler] Add option for firing effect functions (facebook#31794) [compiler][be] Logger based debug printing in test runner (facebook#31809) [compiler][ez] Clean up duplicate code in propagateScopeDeps (facebook#31581) [compiler] Repro for aliased captures within inner function expressions (facebook#31770) [compiler][be] Playground now compiles entire program (facebook#31774) [Flight] Color and badge non-primary environments (facebook#31738) [Flight] Emit Deduped Server Components Marker (facebook#31737) [Flight] Sort Server Components Track Group ahead of Client Scheduler/Components Tracks (facebook#31736) Clean up context access profiling experiment (facebook#31806) [Flight] Stack Parallel Components in Separate Tracks (facebook#31735) Flag for requestPaint (facebook#31805)
Compiler playground now runs the entire program through
babel-plugin-react-compilerinstead of a custom pipeline which previously duplicated function inference logic fromProgram.ts. In addition, the playground output reflects the tranformed file (instead of a "virtual file" of manually concatenated functions).This helps with the following:
_coruseFire)This also helps us repurpose playground into a more general tool for compiler-users instead of just for compiler engineers.
We differentiate between imports and globals in many cases (e.g.
inferEffectDeps), so it may be misleading to omit imports in printed outputStack created with Sapling. Best reviewed with ReviewStack.