-
Notifications
You must be signed in to change notification settings - Fork 45
Watch mode #50
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
Comments
Yeah, that's true. Node.js caches all the require calls by default. I think, I can add a check for the environment variable |
Yes, it's for development workaround. env var is good idea. |
@sullenor When you can fix it? |
@markuplab I'll try tomorrow |
done, 2.1.0 |
Hey, everybody. I have some minor problem. Actually it`s not a problem at the moment, but think it could make some in future. I'm talking about this https://github.com/reactjs/express-react-views/blob/master/index.js#L59-L66 var initHooks = require('css-modules-require-hook');
initHooks({
generateScopedName: generateScopedName(config),
extensions: config.extensions.styles,
preprocessCss,
processCss,
debug: true // <------------------
}); to make cache cleaning sort of isolated. Just for that module. Without any influence to some other. Is that possible? |
#56 add pr |
Looks like you have a slightly different name of the option in the pr ( I don't mind to have a stronger option to control environment and I think its a good enhancement. Sorry for the late response, I'll make the new version soon. |
oops, my bad :)
Wait for it. Good luck! |
@yazonnile should be available for now. Check out 2.1.1 Thank you :) |
Great! Welcome)! |
CSS map changes doesn't apply, if module was changed.
It's due all modules in node js exposed as cached objects.
All reference saved in
require.cache
.This tiny helper, that we use for clear
require.cache
:The text was updated successfully, but these errors were encountered: