css-modules-typescript-loader
css-modules-typescript-loader copied to clipboard
seek-oss
Webpack loader to create TypeScript declarations for CSS Modules
I am using this library to build my webpack application and I am even using mode: verify in my CI. this is my css module written in SASS: ``` .MDButton...
I'm using Semantic UI React along with their Semantic UI CSS styles. App.tsx: ```jsx import 'semantic-ui-css/semantic.min.css'; import './App.css' import MyComponent from './components'; export const App = () => export default...
If I have a component, which is not in a resulting webpack bundle, then `css-modules-typescript-loader` does not produce corresponding `.scss.d.ts` which is correct, since the `.scss` is not running through...
As per default, npm publish is currently including everything. This includes the tests folder, the editorconfig file, etc. I believe it is safe to [add a whitelist](https://docs.npmjs.com/cli/v6/configuring-npm/package-json#files) to the package.json-...
Useful when working with tools that can differentiate between generated files and regular files.
We are using css-modules-typescript-loader to generate our types with CSS modules, css-loader and sass. I'm seeing an issue in the generated typescript files from `css-modules-typescript-loader`. When we update to `css-loader`...
Hi, I'm a Typescript newbie and I have a question not strictly related to this project: I used `css-modules-typescript-loader` to generate TypeScript declarations: I have got this structure: ``` src/Components/MyComponent...
After upgrading to `4.0.0` I have some issue with access to style object. - Previous version: 3.0.1 ```ts // This file is automatically generated. // Please do not change this...
Closes #37 It has one known limitation. Exported class names has to JS safe - eg. we can't use dash in class names.
