gaja-group
/
matrix-bot
2
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Merge pull request #11944 from vector-im/dbkr/fix_build_webpack 

Fix webpack to babel js-sdk & react-sdk but no other deps
This commit is contained in:
David Baker 2020-01-20 17:19:59 +00:00 committed by GitHub
parent 119802d00f 922ed597d6
commit 4c699d8001
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 17 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

18
webpack.config.js
View File

@ -109,7 +109,23 @@ module.exports = (env, argv) => {
rules: [
{
test: /\.(ts|js)x?$/,
exclude: /node_modules/,
include: (f) => {
// we use the original source files of react-sdk and js-sdk, so we need to
// run them through babel.
if (f.startsWith(path.resolve(__dirname, 'node_modules', 'matrix-js-sdk'))) return true;
if (f.startsWith(path.resolve(__dirname, 'node_modules', 'matrix-react-sdk'))) return true;
// but we can't run all of our dependencies through babel (many of them still
// use module.exports which breaks if babel injects an 'include' for its
// polyfills: probably fixable but babeling all our dependencies is probably
// not necessary anyway).
if (f.startsWith(path.resolve(__dirname, 'node_modules'))) return false;
// anything else gets babeled (our own source files, and also modules that
// are yarn linked from somewhere else because this tests the absolute,
// resolved path, so react-sdk and js-sdk fall under this case in a standard
// dev setup. This will presumably start running any other module through
// babel if yarn linked... caveat emptor.
return true;
},
loader: 'babel-loader',
options: {
cacheDirectory: true