-
Notifications
You must be signed in to change notification settings - Fork 222
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[5.0.0-alpha.3.0] Can't bundle Typescript #423
Comments
I made a patch for this issue. Hope this helps anyone.
|
2 tasks
To limit confusion, I am combining all threads for webpack 5 / karma6 support over here ==> #475 |
v5 is now available |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'd like to use karma-webpack to compile typescript.
Expected Behavior
Successfully complete test.
Actual Behavior
karma-webpack generates a name of bundle file from
.ts
path.https://github.com/webpack-contrib/karma-webpack/blob/eec6dfc9e80413fe957136975034757bdffe9e8e/lib/karma-webpack.js#L84-L87
However it gets a bundle content from a file path generated from
.js
path.So, second argument of
done()
is alwaysundefined
.https://github.com/webpack-contrib/karma-webpack/blob/eec6dfc9e80413fe957136975034757bdffe9e8e/lib/karma-webpack.js#L105-L120
Code
How Do We Reproduce?
See
karma.conf.js
above. You can install all dependencies bynpm i -D karma karma-chrome-launcher karma-jasmine jasmine karma-webpack@5.0.0-alpha.3.0 webpack ts-loader typescript @types/jasmine
. This bug is also reproduced if you use mocha. No problem even iftsconfig.json
is an empty file.It's not reproduced in karma-webpack@4.0.2
The text was updated successfully, but these errors were encountered: