-
Notifications
You must be signed in to change notification settings - Fork 11
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
Impossible to check .module.css files #182
Comments
Thank you for your suggestion! That would add extra flexibility and must be useful. I'll work on this this weekend. |
Is there any movement on this issue? |
Please add support for this! Next.js comes built in with CSS modules in files of the form |
Friendly ping @nodaguti. |
A quick an easy way to solve this would be a list of suffix that can be removed from the css filename, so that it can be compared with the js files. |
Will you make solution for *.module.css files? |
I have all css modules files names as following:
*.module.css
(i.e. Button.module.css) with correspondingtsx
file*.tsx
(i.e. Button.tsx). And using current template capabilities, I cannot match these files, becausecssName
equals toButton.module
in this case.I suggest to provide ability to specify resolver as custom function
type DocumentPathResolver = (cssFilePath: string) => string | null
, which would return path to a document.(i.e. it should be possible to provide such function via option
resolve.documents
)The text was updated successfully, but these errors were encountered: