mirrors/element-web
1
0
Fork 0
mirror of https://github.com/element-hq/element-web synced 2024-11-25 02:35:48 +03:00
Code Issues Projects Releases Packages Wiki Activity

Fix webpack to babel js-sdk & react-sdk but no other deps

Browse source 
This was happening implicitly in our dev setups and the CI build
because of the comment on the last line.
This commit is contained in:
David Baker 2020-01-20 16:55:07 +00:00
parent 119802d00f
commit 922ed597d6
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