[英]Webpack/Karma/awesome-typescript-loader Won't Ignore Files
我使用Webpack 2.x編譯Angular 2 App。 對於生產代碼,我結合使用ngc
和@ngtools/webpack
的AotPlugin進行編譯。 為了測試,我使用awesome-typescript-loader
。 我的代碼的生產版本工作正常。 但是,當我執行npm test
時,發生了非常奇怪的事情…… awesome-typescript-loader
抱怨它未能編譯代碼,但是Karma仍然通過了測試,並且都通過了測試。
bash-3.2$ npm test
> btc2017@1.0.0 test /Users/tomb/Projects/brandontom.com/wp-content/themes/btc2017
> NODE_ENV=test node ./node_modules/.bin/karma start --single-run=true
webpack: wait until bundle finished:
[at-loader] Using typescript@2.2.1 from typescript and "tsconfig.json" from /Users/tomb/Projects/brandontom.com/wp-content/themes/b
tc2017/tsconfig.json.
[at-loader] Checking started in a separate process...
[at-loader] Ok, 1.054 sec.
ERROR in ./ngfactory/src/app/app.module.ngfactory.ts
Module parse failed: /Users/tomb/Projects/brandontom.com/wp-content/themes/btc2017/ngfactory/src/app/app.module.ngfactory.ts Unexpe
cted token (65:56)
You may need an appropriate loader to handle this file type.
| import * as import55 from '@angular/router/src/router_config_loader';
| import * as import56 from '@angular/router/src/router_state';
| class AppModuleInjector extends import0.NgModuleInjector<import1.AppModule> {
| _CommonModule_0:import2.CommonModule;
| _ApplicationModule_1:import3.ApplicationModule;
@ ./bootstrap/main.aot.ts 1:0-78
webpack: Failed to compile.
Chrome 56.0.2924 (Mac OS X 10.12.3): Executed 4 of 4 SUCCESS (1.41 secs / 0.758 secs)
這是一個巧妙的技巧,但是我寧願跳過嘗試首先解析該文件的過程,特別是因為該文件已生成。
我的第一個想法是忽略生成文件的目錄。它被構建在名為ngfactory
的文件夾中。 這是我將以下規則添加到webpack.config.js
規則:
{
test: /\.ts$/,
loaders: ['awesome-typescript-loader', 'angular2-template-loader'],
exclude: [/(node_modules|bootstrap|prebuild|ngfactory)/]
}
但是,盡管exclude
但是awesome-typescript-loader
仍然嘗試解析此文件。 接下來,我認為可能是Karma導致了此問題,因此我在我的karma.conf.js
添加了排除規則。
module.exports = function (config) {
var _config = {
basePath: '',
frameworks: ['jasmine'],
files: [
{ pattern: './karma-shim.js', watched: false }
],
exclude: [
'bootstrap',
'dist',
'ngfactory', // <--- here's where that file lives
'node_modules',
'prebuild'
],
...
...
當我刪除工件文件夾( prebuild
和ngfactory
)時,我意識到引導文件(位於名為bootstrap
的目錄中)正在解析,並且該文件正嘗試導入app.module.ngfactory.ts
我將bootstrap
添加到了各種exclude
屬性(包括我的tsconfig.json
)。 但是,沒有任何事情可以阻止該問題的產生。 如果有人看到過這樣的內容,我很想知道您是如何做到的。
這是我完整的webpack.config.js
:
var neat = require('node-neat')
var path = require('path')
var webpack = require('webpack')
var AotPlugin = require('@ngtools/webpack').AotPlugin
var sassPaths = neat.includePaths.map(function (path) {
return 'includePaths[]=' + path
}).join('&')
module.exports = (function (nodeEnv) {
var config = {
entry: {
globals: [ 'core-js/client/shim.min', 'reflect-metadata', 'zone.js' ],
main: path.resolve(__dirname, 'bootstrap') + '/main.aot.ts'
},
devServer: {
inline: true
},
module: {
rules: [
{ test: /\.html$/, loader: 'raw-loader' },
{ test: /\.scss$/, loader: 'raw-loader!css-loader!sass-loader?' + sassPaths, exclude: /node_modules/ }
]
},
output: {
filename: '[name].js',
path: path.resolve(__dirname, 'dist')
},
resolve: {
extensions: ['.js', '.ts']
},
plugins: [
new webpack.ContextReplacementPlugin(
/angular(\\|\/)core(\\|\/)(esm(\\|\/)src|src)(\\|\/)linker/,
__dirname
),
new webpack.DefinePlugin({
process: { env: { NODE_ENV: JSON.stringify(nodeEnv) } }
})
]
}
if (nodeEnv !== 'test') {
config.module.rules.push({
test: /\.ts$/,
loader: '@ngtools/webpack'
})
config.plugins.push(new AotPlugin({
tsConfigPath: './tsconfig.json'
}))
config.plugins.push(new webpack.optimize.UglifyJsPlugin({
mangle: { screw_ie8: true, keep_fnames: true },
compress: { screw_ie8: true, warnings: false },
comments: false
}))
} else {
config.module.rules.push({
test: /\.ts$/,
loaders: ['awesome-typescript-loader', 'angular2-template-loader'],
exclude: [/(node_modules|bootstrap|prebuild|ngfactory)/]
})
}
return config
})(process.env.NODE_ENV)
這是我的tsconfig.json
:
{
"compilerOptions": {
"target": "es5",
"module": "es2015",
"moduleResolution": "node",
"emitDecoratorMetadata": true,
"experimentalDecorators": true,
"sourceMap": true,
"noEmitHelpers": false,
"noUnusedLocals": false,
"noUnusedParameters": false,
"outDir": "./prebuild",
"lib": [
"es2015",
"dom"
],
"types": [
"jasmine",
"node"
]
},
"compileOnSave": false,
"buildOnSave": false,
"awesomeTypescriptLoaderOptions": {
"forkChecker": true,
"useWebpackText": true
},
"angularCompilerOptions": {
"genDir": "./ngfactory",
"entryModule": "src/app/app.module#AppModule"
}
}
從好的方面來說,這也是我的karma.conf.js
:
var webpackConfig = require('./webpack.config')
module.exports = function (config) {
var _config = {
basePath: '',
frameworks: ['jasmine'],
files: [
{ pattern: './karma-shim.js', watched: false }
],
exclude: [
'bootstrap',
'dist',
'ngfactory',
'node_modules',
'prebuild'
],
preprocessors: {
'./karma-shim.js': ['webpack']
},
webpack: webpackConfig,
webpackMiddleware: {
stats: 'errors-only'
},
webpackServer: {
noInfo: true
},
progress: ['progress'],
port: 9876,
color: true,
logLevel: config.LOG_ERROR,
browsers: ['Chrome']
}
config.set(_config)
}
盡管我無法阻止awesome-typescript-loader
編譯工件,但awesome-typescript-loader
,我都能使它停止失敗。 加載程序具有一個稱為transpileOnly
的布爾設置。 將其設置為true
可以防止加載程序進行類型檢查。 我在awesomeTypescriptLoaderOptions
部分tsconfig.json
其添加到了tsconfig.json
中。
這不是理想的選擇,但是我現在還可以使用awesome-typescript-loader
而不在測試端強制執行類型檢查...我想...只要ngc
確實在生產代碼上強制執行它。
這是我的tsconfig.json
{
"compilerOptions": {
"target": "es5",
"module": "es2015",
"moduleResolution": "node",
"emitDecoratorMetadata": true,
"experimentalDecorators": true,
"sourceMap": true,
"noEmitHelpers": false,
"noUnusedLocals": false,
"noUnusedParameters": false,
"outDir": "./prebuild",
"lib": [
"es2015",
"dom"
],
"types": [
"jasmine",
"node"
]
},
"compileOnSave": false,
"buildOnSave": false,
"awesomeTypescriptLoaderOptions": {
"forkChecker": true,
"useWebpackText": true,
"transpileOnly": true
},
"angularCompilerOptions": {
"genDir": "./ngfactory",
"entryModule": "src/app/app.module#AppModule"
}
}
聲明:本站的技術帖子網頁,遵循CC BY-SA 4.0協議,如果您需要轉載,請注明本站網址或者原文地址。任何問題請咨詢:yoyou2525@163.com.