react/scripts/flow
Sebastian Markbåge ce09ace9a2
Improve Error Messages when Access Client References (#26059)
This renames Module References to Client References, since they are in
the server->client direction.

I also changed the Proxies exposed from the `node-register` loader to
provide better error messages. Ideally, some of this should be
replicated in the ESM loader too but neither are the source of truth.
We'll replicate this in the static form in the Next.js loaders. cc
@huozhi @shuding

- All references are now functions so that when you call them on the
server, we can yield a better error message.
- References that are themselves already referring to an export name are
now proxies that error when you dot into them.
- `use(...)` can now be used on a client reference to unwrap it server
side and then pass a reference to the awaited value.
2023-01-27 20:08:26 -05:00
..
config Upgrade to Flow 0.196.3 (#25974) 2023-01-09 17:52:42 -05:00
createFlowConfigs.js [flow] enable enforce_local_inference_annotations (#25921) 2023-01-09 15:46:48 -05:00
environment.js Try assigning fetch to globalThis if global assignment fails (#25571) 2022-10-27 02:43:17 -04:00
react-devtools.js ESLint upgrade to use hermes-eslint (#25915) 2022-12-20 14:27:01 -05:00
react-native-host-hooks.js Add support for setNativeProps to Fabric (#25737) 2022-12-09 14:43:52 +00:00
react-relay-hooks.js Improve Error Messages when Access Client References (#26059) 2023-01-27 20:08:26 -05:00
runFlow.js [Codemod] Update copyright header to Meta (#25315) 2022-10-18 11:19:24 -04:00
xplat.js [Codemod] Update copyright header to Meta (#25315) 2022-10-18 11:19:24 -04:00