Open basslagter opened 5 years ago
Agreed, I had to roll back to 3.1.6 to get it to compile correctly
Same here
TS v3.2.2 also has an issue.
Yepp, just experienced the same
For the record, this is the error we get when building. The Final loader (...) didn't return a Buffer or String
error does not show up here as it only shows up on re-builds:
Here is the (minimal) Webpack configuration that led to this:
import webpack from 'webpack';
const config: webpack.Configuration = {
resolve: {
extensions: ['.js', '.json', '.ts', '.tsx'],
},
module: {
rules: [
{
test: /\.tsx?$/,
exclude: /node_modules/,
loader: 'awesome-typescript-loader',
},
],
},
devtool: 'source-map',
};
export default config;
What tricked us is that even though the output said ✖ 「atl」: Child process failed to process the request
, the build did not return a non-zero code, so our CI passed just fine.
It would be very useful if any failure from a child process would fail the build.
It works for me with following config (tsconfig.json):
"awesomeTypescriptLoaderOptions": {
"useTranspileModule": true
}
@bitworking what effect does this have on the output?
Also...for me it works on the first compile but fails with HMR whenever I edit a file in development.
@basslagter Yes you are right..a live reload doesn't work for me either. I didn't examine the output if there's a difference but from the docs it only uses a fast transpileModule emit mode
.
@bitworking yes, I am also thinking about switching. This package does not seem to be maintained anymore. Thanks!
That's funny but ts-loader
isn't working in my case without this package because of issue #1 in tsconfig-paths-webpack-plugin. So I switched to ts-loader
and I'm currently using a-t-l
only for proper paths handling by using TsConfigPathsPlugin
exported from it. 🤔
encounter the same problem.
maybe I should be switch ts-loader too.
When upgrading to Typescript 3.2.1 I get "Module build failed: Error: Final loader (./node_modules/awesome-typescript-loader/dist/entry.js) didn't return a Buffer or String"