You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When requiring a module, changing the capitalization of the module can trick browserify into loading the same module twice. I'm unsure of if this is due to using a case-insensitive filesystem, or some other reason.
Are there any steps that could be taken to catch this in the future? The resulting semantics are correct in that the name is mapped to the same module, however the fact that browserify then bundles the module twice is problematic.
Here's an example of loaded files with the --list option with React. This was caused by just one file using a different casing for the React module:
When requiring a module, changing the capitalization of the module can trick browserify into loading the same module twice. I'm unsure of if this is due to using a case-insensitive filesystem, or some other reason.
Are there any steps that could be taken to catch this in the future? The resulting semantics are correct in that the name is mapped to the same module, however the fact that browserify then bundles the module twice is problematic.
Here's an example of loaded files with the
--list
option with React. This was caused by just one file using a different casing for the React module:The text was updated successfully, but these errors were encountered: