We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Hi-
First of all, thanks for the fork - it is very helpful to have an active repo for this.
Question:
Am I supposed to check in the generated typings file to source control?
There is this issue in the old repo: Jimdo/typings-for-css-modules-loader#79 (comment) And without checking in the typings files, the same issue will happen.
Is there any known issues with checking in the typings file?
The text was updated successfully, but these errors were encountered:
Hi- First of all, thanks for the fork - it is very helpful to have an active repo for this. Question: Am I supposed to check in the generated typings file to source control? There is this issue in the old repo: Jimdo/typings-for-css-modules-loader#79 (comment) And without checking in the typings files, the same issue will happen. Is there any known issues with checking in the typings file?
Yep, maybe the https://github.com/TeamSupercell/typings-for-css-modules-loader#typescript-does-not-find-the-typings and you are used fork-ts-checker-webpack-plugin?
Sorry, something went wrong.
No branches or pull requests
Hi-
First of all, thanks for the fork - it is very helpful to have an active repo for this.
Question:
Am I supposed to check in the generated typings file to source control?
There is this issue in the old repo: Jimdo/typings-for-css-modules-loader#79 (comment)
And without checking in the typings files, the same issue will happen.
Is there any known issues with checking in the typings file?
The text was updated successfully, but these errors were encountered: