You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 30, 2019. It is now read-only.
With the currently used transpileOnly flag enabled for ts-loader, some issues with the generated code might occur, esp. regarding const enums, like described here:
To avoid doing duplicated work, type checking via fork-ts-checker-webpack-plugin should be disabled. However, it cannot be disabled without disabling it at all. If that is the only alternative, externalizing the linting step from the build to a separate task - executable on demand, forcefully executed on pre-commit should be useful. Already did that in some other projects with great success.
The text was updated successfully, but these errors were encountered:
With the currently used
transpileOnly
flag enabled forts-loader
, some issues with the generated code might occur, esp. regarding const enums, like described here:microsoft/TypeScript#16671
TypeStrong/ts-loader#331
To avoid doing duplicated work, type checking via
fork-ts-checker-webpack-plugin
should be disabled. However, it cannot be disabled without disabling it at all. If that is the only alternative, externalizing the linting step from the build to a separate task - executable on demand, forcefully executed onpre-commit
should be useful. Already did that in some other projects with great success.The text was updated successfully, but these errors were encountered: