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
Difference being that's a loader, and this is a plugin. Therefore, it will read the actual output and create a modernizr build from it. The reason being (unless I'm misunderstanding the correct process):
I'm effectively creating a jquery plugin as an NPM package, which needs feature detection.
I therefore add Modernizr references
Any projects depending on my NPM package will therefore require Modernizr, but in order to create a custom build, they would need to include my package in node_modules in their file search. To me, this sounds like bad practise as I would expect anyone using my package to know to do that?
If the plugin inspected the chunk output and used customizr, then I expect this would cover any situation where either the local project had used Modernizr, or a dependency had.
The text was updated successfully, but these errors were encountered:
Do you think it's worth adding customizr support, a little like:
https://github.com/andersaloof/modernizr-auto-loader
Difference being that's a loader, and this is a plugin. Therefore, it will read the actual output and create a modernizr build from it. The reason being (unless I'm misunderstanding the correct process):
If the plugin inspected the chunk output and used customizr, then I expect this would cover any situation where either the local project had used Modernizr, or a dependency had.
The text was updated successfully, but these errors were encountered: