2017-11-24 01:44:58 +08:00
|
|
|
'use strict';
|
|
|
|
|
|
|
|
|
|
const {readdirSync, statSync} = require('fs');
|
|
|
|
|
const {join} = require('path');
|
2018-05-19 18:29:11 +08:00
|
|
|
const baseConfig = require('./config.base');
|
2017-11-24 01:44:58 +08:00
|
|
|
|
2020-11-03 01:46:58 +08:00
|
|
|
process.env.IS_BUILD = true;
|
|
|
|
|
|
2021-01-13 01:50:38 +08:00
|
|
|
const NODE_MODULES_DIR =
|
|
|
|
|
process.env.RELEASE_CHANNEL === 'stable' ? 'oss-stable' : 'oss-experimental';
|
|
|
|
|
|
2017-11-24 01:44:58 +08:00
|
|
|
// Find all folders in packages/* with package.json
|
|
|
|
|
const packagesRoot = join(__dirname, '..', '..', 'packages');
|
|
|
|
|
const packages = readdirSync(packagesRoot).filter(dir => {
|
|
|
|
|
if (dir.charAt(0) === '.') {
|
|
|
|
|
return false;
|
|
|
|
|
}
|
|
|
|
|
const packagePath = join(packagesRoot, dir, 'package.json');
|
2019-12-17 08:03:12 +08:00
|
|
|
let stat;
|
|
|
|
|
try {
|
|
|
|
|
stat = statSync(packagePath);
|
|
|
|
|
} catch (err) {
|
|
|
|
|
return false;
|
|
|
|
|
}
|
|
|
|
|
return stat.isFile();
|
2017-11-24 01:44:58 +08:00
|
|
|
});
|
2018-09-12 23:56:04 +08:00
|
|
|
|
2017-11-24 01:44:58 +08:00
|
|
|
// Create a module map to point React packages to the build output
|
|
|
|
|
const moduleNameMapper = {};
|
2018-09-12 23:56:04 +08:00
|
|
|
|
|
|
|
|
// Allow bundle tests to read (but not write!) default feature flags.
|
2019-07-03 18:05:28 +08:00
|
|
|
// This lets us determine whether we're running in different modes
|
2018-09-12 23:56:04 +08:00
|
|
|
// without making relevant tests internal-only.
|
|
|
|
|
moduleNameMapper[
|
|
|
|
|
'^shared/ReactFeatureFlags'
|
|
|
|
|
] = `<rootDir>/packages/shared/forks/ReactFeatureFlags.readonly`;
|
|
|
|
|
|
|
|
|
|
// Map packages to bundles
|
2017-11-24 01:44:58 +08:00
|
|
|
packages.forEach(name => {
|
|
|
|
|
// Root entry point
|
2021-09-22 03:12:52 +08:00
|
|
|
moduleNameMapper[`^${name}$`] = `<rootDir>/build/${NODE_MODULES_DIR}/${name}`;
|
2017-11-24 01:44:58 +08:00
|
|
|
// Named entry points
|
2018-04-17 08:43:55 +08:00
|
|
|
moduleNameMapper[
|
Add new mock build of Scheduler with flush, yield API (#14964)
* Add new mock build of Scheduler with flush, yield API
Test environments need a way to take control of the Scheduler queue and
incrementally flush work. Our current tests accomplish this either using
dynamic injection, or by using Jest's fake timers feature. Both of these
options are fragile and rely too much on implementation details.
In this new approach, we have a separate build of Scheduler that is
specifically designed for test environments. We mock the default
implementation like we would any other module; in our case, via Jest.
This special build has methods like `flushAll` and `yieldValue` that
control when work is flushed. These methods are based on equivalent
methods we've been using to write incremental React tests. Eventually
we may want to migrate the React tests to interact with the mock
Scheduler directly, instead of going through the host config like we
currently do.
For now, I'm using our custom static injection infrastructure to create
the two builds of Scheduler — a default build for DOM (which falls back
to a naive timer based implementation), and the new mock build. I did it
this way because it allows me to share most of the implementation, which
isn't specific to a host environment — e.g. everything related to the
priority queue. It may be better to duplicate the shared code instead,
especially considering that future environments (like React Native) may
have entirely forked implementations. I'd prefer to wait until the
implementation stabilizes before worrying about that, but I'm open to
changing this now if we decide it's important enough.
* Mock Scheduler in bundle tests, too
* Remove special case by making regex more restrictive
2019-02-27 12:51:17 +08:00
|
|
|
`^${name}\/([^\/]+)$`
|
2021-09-22 03:12:52 +08:00
|
|
|
] = `<rootDir>/build/${NODE_MODULES_DIR}/${name}/$1`;
|
2017-11-24 01:44:58 +08:00
|
|
|
});
|
|
|
|
|
|
2021-11-01 06:38:03 +08:00
|
|
|
moduleNameMapper[
|
|
|
|
|
'use-sync-external-store/shim/with-selector'
|
|
|
|
|
] = `<rootDir>/build/${NODE_MODULES_DIR}/use-sync-external-store/shim/with-selector`;
|
|
|
|
|
moduleNameMapper[
|
|
|
|
|
'use-sync-external-store/shim/index.native'
|
|
|
|
|
] = `<rootDir>/build/${NODE_MODULES_DIR}/use-sync-external-store/shim/index.native`;
|
|
|
|
|
|
2018-05-19 18:29:11 +08:00
|
|
|
module.exports = Object.assign({}, baseConfig, {
|
2017-11-24 01:44:58 +08:00
|
|
|
// Redirect imports to the compiled bundles
|
|
|
|
|
moduleNameMapper,
|
2019-08-28 00:08:49 +08:00
|
|
|
modulePathIgnorePatterns: [
|
|
|
|
|
...baseConfig.modulePathIgnorePatterns,
|
2021-07-02 02:39:18 +08:00
|
|
|
'packages/react-devtools-extensions',
|
2019-08-28 00:08:49 +08:00
|
|
|
'packages/react-devtools-shared',
|
|
|
|
|
],
|
2018-09-09 23:54:28 +08:00
|
|
|
// Don't run bundle tests on -test.internal.* files
|
2017-11-24 01:44:58 +08:00
|
|
|
testPathIgnorePatterns: ['/node_modules/', '-test.internal.js$'],
|
|
|
|
|
// Exclude the build output from transforms
|
2021-09-22 03:12:52 +08:00
|
|
|
transformIgnorePatterns: ['/node_modules/', '<rootDir>/build/'],
|
Add new mock build of Scheduler with flush, yield API (#14964)
* Add new mock build of Scheduler with flush, yield API
Test environments need a way to take control of the Scheduler queue and
incrementally flush work. Our current tests accomplish this either using
dynamic injection, or by using Jest's fake timers feature. Both of these
options are fragile and rely too much on implementation details.
In this new approach, we have a separate build of Scheduler that is
specifically designed for test environments. We mock the default
implementation like we would any other module; in our case, via Jest.
This special build has methods like `flushAll` and `yieldValue` that
control when work is flushed. These methods are based on equivalent
methods we've been using to write incremental React tests. Eventually
we may want to migrate the React tests to interact with the mock
Scheduler directly, instead of going through the host config like we
currently do.
For now, I'm using our custom static injection infrastructure to create
the two builds of Scheduler — a default build for DOM (which falls back
to a naive timer based implementation), and the new mock build. I did it
this way because it allows me to share most of the implementation, which
isn't specific to a host environment — e.g. everything related to the
priority queue. It may be better to duplicate the shared code instead,
especially considering that future environments (like React Native) may
have entirely forked implementations. I'd prefer to wait until the
implementation stabilizes before worrying about that, but I'm open to
changing this now if we decide it's important enough.
* Mock Scheduler in bundle tests, too
* Remove special case by making regex more restrictive
2019-02-27 12:51:17 +08:00
|
|
|
setupFiles: [
|
|
|
|
|
...baseConfig.setupFiles,
|
|
|
|
|
require.resolve('./setupTests.build.js'),
|
|
|
|
|
],
|
2017-11-24 01:44:58 +08:00
|
|
|
});
|