Skip to content

Please output more debugging information for "CSS module does not exist" #171

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

Closed
jjinux opened this issue Mar 28, 2018 · 3 comments
Closed

Comments

@jjinux
Copy link
Contributor

jjinux commented Mar 28, 2018

In getClassName.js, there are exceptions such as console.warn('CSS module does not exist.');. That error is really hard to debug because it doesn't give much context. If you included importName and moduleName in the exception, it'd be a lot easier to debug. I've resorted to adding console.log statements in order to workaround this in the meantime.

Here's a sample error message I get via Karma:

Chrome 63.0.3239 (Mac OS X 10.13.3) ERROR
  Uncaught Error: Module build failed: Error: /Users/jjbehrens/Code/udemy-django/static/src/udemy/js/organization-common/expired-modal/expired-modal-content/expired-trial.react-component.js: CSS module does not exist.
    at getClassNameForNamespacedStyleName (/Users/jjbehrens/Code/udemy-django/static/node_modules/babel-plugin-react-css-modules/dist/getClassName.js:47:13)
    at styleNameValue.split.filter.map.styleName (/Users/jjbehrens/Code/udemy-django/static/node_modules/babel-plugin-react-css-modules/dist/getClassName.js:68:14)
...
@gajus
Copy link
Owner

gajus commented Apr 7, 2018

PR welcome.

@jjinux
Copy link
Contributor Author

jjinux commented Apr 19, 2018

@jjinux jjinux closed this as completed Apr 20, 2018
@jjinux
Copy link
Contributor Author

jjinux commented Apr 20, 2018

This has been resolved.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants