-
Notifications
You must be signed in to change notification settings - Fork 168
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
Vaadin 19: Why ts-loader is used only with useClientSideIndexFileForBootstrapping? #10414
Comments
Thank you @xdenser for the feedback, this is a bug, we will fix it.
|
As far as I remember, I had to disable it this way because |
Use |
* fix: allow TypeScript in V14 server bootstrapping mode Fixes #10414 * Fix fork-ts-checker-plugin options * fix: disable resolving TypeScript when no tsconfig.json
* fix: allow TypeScript in V14 server bootstrapping mode Fixes #10414 * Fix fork-ts-checker-plugin options * fix: disable resolving TypeScript when no tsconfig.json
* fix: allow TypeScript in V14 server bootstrapping mode Fixes #10414 * Fix fork-ts-checker-plugin options * fix: disable resolving TypeScript when no tsconfig.json
This ticket/PR has been released with platform 19.0.6. For prerelease versions, it will be included in its final version. |
I am migrating Vaadin 18.0.1 project to Vaadin 19.0.2 and and we do not use useClientSideIndexFileForBootstrapping,
Typescript compilation worked in 18.0.1 and now it stopped in 19.0.2.
OK I can add it back in my wbpack.config.js, but condition loks strange to me.
See lines 210, 241 in
https://github.com/vaadin/flow/blob/master/flow-server/src/main/resources/webpack.generated.js
61df7f7
The text was updated successfully, but these errors were encountered: