-
Notifications
You must be signed in to change notification settings - Fork 0
/
webpack.karma.js
44 lines (41 loc) · 1.66 KB
/
webpack.karma.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
// FIM - Fast Image Manipulation Library for Javascript
// Copyright (c) Leo C. Singleton IV <leo@leosingleton.com>
// See LICENSE in the project root for license information.
const path = require('path');
const glob = require('glob');
module.exports = {
mode: 'development',
entry: glob.sync('./**/__tests__/**/*.@(browser|test).ts', { ignore: './**/node_modules/**' }),
devtool: 'inline-source-map',
module: {
rules: [
{
test: /\.tsx?$/,
loader: 'ts-loader',
exclude: /node_modules/,
options: {
// ts-loader has an issue where it reads the tsconfig.json file for the first .ts file it encounters and
// doesn't look for different tsconfig.json files for other files. This causes an issue for FIM as each NPM
// package has a different rootDir, so unit tests from more than one package will fail to compile. To work
// around this, we force ts-loader to use the shared configuration file at the root of the repo.
// See https://github.com/TypeStrong/ts-loader/issues/647
configFile: path.resolve(__dirname, 'tsconfig.karma.json'),
// Do not output .d.ts files. I'm not sure why, but ts-loader was always emitting them next to the source
// files, not in the build output directory. They don't serve any purpose for the karma unit tests, so turning
// them off completely here...
compilerOptions: {
declaration: false
}
}
}
]
},
resolve: {
extensions: [ '.js', '.ts' ]
},
output: {
path: path.resolve(__dirname, 'build'),
filename: 'browser-tests.js',
libraryTarget: 'umd'
}
};