-
-
Notifications
You must be signed in to change notification settings - Fork 510
/
metro.config.js
105 lines (89 loc) · 3.28 KB
/
metro.config.js
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
const { getDefaultConfig, mergeConfig } = require('@react-native/metro-config');
const fs = require('fs');
const path = require('path');
const exclusionList = require('metro-config/src/defaults/exclusionList');
const escape = require('escape-string-regexp');
const pack = require('../package.json');
const projectPack = require('./package.json');
// react-native-screens root directory
const rnsRoot = path.resolve(__dirname, '..');
const modules = [
'@react-navigation/native',
'@react-navigation/stack',
'react-native-reanimated',
'react-native-safe-area-context',
'react-native-gesture-handler',
...Object.keys(pack.peerDependencies),
];
const resolvedExts = ['.ts', '.tsx', '.js', '.jsx'];
const config = {
projectRoot: __dirname,
watchFolders: [rnsRoot],
// We need to make sure that only one version is loaded for peerDependencies
// So we exclude them at the root, and alias them to the versions in example's node_modules
resolver: {
blockList: exclusionList(
modules.map(
m =>
new RegExp(`^${escape(path.join(rnsRoot, 'node_modules', m))}\\/.*$`),
),
),
extraNodeModules: modules.reduce((acc, name) => {
acc[name] = path.join(__dirname, 'node_modules', name);
return acc;
}, {}),
nodeModulesPaths: [path.join(__dirname, '../../')],
// Since we use react-navigation as submodule it comes with it's own node_modules. While loading
// react-navigation code, due to how module resolution algorithms works it seems that its node_modules
// are consulted first, resulting in double-loaded packages (so doubled react, react-native and other package instances) leading
// to various errors. To mitigate this we define below custom request resolver, hijacking requests to conflicting modules and manually
// resolving appropriate files. **Most likely** this can be achieved by proper usage of blockList but I found this method working ¯\_(ツ)_/¯
resolveRequest: (context, moduleName, platform) => {
if (moduleName === 'react-native-screens') {
return {
filePath: path.join(rnsRoot, 'src', 'index.tsx'),
type: 'sourceFile',
};
}
if (moduleName in projectPack.dependencies) {
for (const ext of resolvedExts) {
const possiblePath = path.join(
__dirname,
'node_modules',
moduleName,
`index${ext}`,
);
const possibleSrcPath = path.join(
__dirname,
'node_modules',
moduleName,
'src',
`index${ext}`,
);
if (fs.existsSync(possiblePath)) {
return {
filePath: possiblePath,
type: 'sourceFile',
};
} else if (fs.existsSync(possibleSrcPath)) {
return {
filePath: possibleSrcPath,
type: 'sourceFile',
};
}
}
}
// Optionally, chain to the standard Metro resolver.
return context.resolveRequest(context, moduleName, platform);
},
},
transformer: {
getTransformOptions: async () => ({
transform: {
experimentalImportSupport: false,
inlineRequires: true,
},
}),
},
};
module.exports = mergeConfig(getDefaultConfig(__dirname), config);