-
Notifications
You must be signed in to change notification settings - Fork 7
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
Do not name modules "module" #178
Comments
I'm doing an update of our packages and for the |
@ronaldruzicka nice! |
@ronaldruzicka there also is a cookie law module as an example so I think we may delete the suffix.js (previously module.js) altogether… Regarding @kettanaito’s concern – I find it difficult to address it. The same may happen with the bootstrap.less – you can include half of the bootstrap modules while using only a handful of them. So it’s more about the developer’s care I think. But in general I agree that it’s better to avoid having lots of examples in the devstack (if any) and try to create more complex boilerplates/examples separately maybe (?) |
There is another discussion about JS examples: #82 The |
What
We should not have a module/component named "module".
Why
module
is a global variable inserted into code during the compilation. For instance, module is also responsible for HMR in webpack builds. We have just experienced this issue with @ronaldruzicka today morning:There are no hot updates accepted, since
module
is being overwritten with our custom component with the same name.How
I would recommend to remove "module" example completely, since it doesn't add any value to the devstack (neither it shows some good practices, nor has an objective value, like being a useful snippet or reusable component).
The text was updated successfully, but these errors were encountered: