mirror of
https://github.com/facebook/react.git
synced 2025-11-01 09:12:30 +00:00
Dan Abramov
47b003a828
* Extract base Jest config This makes it easier to change the source config without affecting the build test config. * Statically import the host config This changes react-reconciler to import HostConfig instead of getting it through a function argument. Rather than start with packages like ReactDOM that want to inline it, I started with React Noop and ensured that *custom* renderers using react-reconciler package still work. To do this, I'm making HostConfig module in the reconciler look at a global variable by default (which, in case of the react-reconciler npm package, ends up being the host config argument in the top-level scope). This is still very broken. * Add scaffolding for importing an inlined renderer * Fix the build * ES exports for renderer methods * ES modules for host configs * Remove closures from the reconciler * Check each renderer's config with Flow * Fix uncovered Flow issue We know nextHydratableInstance doesn't get mutated inside this function, but Flow doesn't so it thinks it may be null. Help Flow. * Prettier * Get rid of enable*Reconciler flags They are not as useful anymore because for almost all cases (except third party renderers) we *know* whether it supports mutation or persistence. This refactoring means react-reconciler and react-reconciler/persistent third-party packages now ship the same thing. Not ideal, but this seems worth how simpler the code becomes. We can later look into addressing it by having a single toggle instead. * Prettier again * Fix Flow config creation issue * Fix imprecise Flow typing * Revert accidental changes
29 lines
1.2 KiB
JavaScript
29 lines
1.2 KiB
JavaScript
/**
|
|
* Copyright (c) 2013-present, Facebook, Inc.
|
|
*
|
|
* This source code is licensed under the MIT license found in the
|
|
* LICENSE file in the root directory of this source tree.
|
|
*/
|
|
|
|
// This entry point is intentionally not typed. It exists only for third-party
|
|
// renderers. The renderers we ship (such as React DOM) instead import a named
|
|
// "inline" entry point (for example, `react-reconciler/inline.dom`). It uses
|
|
// the same code, but the Flow configuration redirects the host config to its
|
|
// real implementation so we can check it against exact intended host types.
|
|
//
|
|
// Only one renderer (the one you passed to `yarn flow <renderer>`) is fully
|
|
// type-checked at any given time. The Flow config maps the
|
|
// `react-reconciler/inline.<renderer>` import (which is *not* Flow typed) to
|
|
// `react-reconciler/inline-typed` (which *is*) for the current renderer.
|
|
// On CI, we run Flow checks for each renderer separately.
|
|
|
|
'use strict';
|
|
|
|
const ReactFiberReconciler = require('./src/ReactFiberReconciler');
|
|
|
|
// TODO: decide on the top-level export form.
|
|
// This is hacky but makes it work with both Rollup and Jest.
|
|
module.exports = ReactFiberReconciler.default
|
|
? ReactFiberReconciler.default
|
|
: ReactFiberReconciler;
|