-
Notifications
You must be signed in to change notification settings - Fork 331
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
How to specify 3rd party preprocessors for karma in web-module build's config? #408
Comments
In case anybody having the same issue, I ended up using the webpack html-loader plugin and import the required files as a string.
And instead of refferring the contents from
simply used
This solves the problem for the original example above. Also, it seems to be a much more elegant solution. But still, it would be great if we could add 3rd party karma preprocessors to the nwb config. |
You can use I should also add the same config function escape hatch that's available for Webpack config for Karma config, which would allow you to edit the generated config programmatically. |
Thanks. I failed to spot the |
I was trying to configure nwb with karma-html2js-preprocessor with the following configuration:
Seemingly, the both the
preprocessors
and thehtml2JsPreprocessor
are completely ignored. As I can see, thegetKarmaPluginConfig()
has only hardwired preprocessors config:I understand that nwb karma config is not the same as the raw karma config because it's being transformed. Do you guys have a workaround for this? Am I missing something? Is there any way to configure nwb karma with 3rd party pre-processors?
The text was updated successfully, but these errors were encountered: