added es6 require support #58
Conversation
|
When I use third-party libs in my projects, first thing I do is removing AMD/CJS/Node/es6 wrappers. So I have for each lib in my custom CDN a file with .fixed.min.js ending. |
|
Why do you remove theese wrappers, for what?? |
|
@ivkodenis92 Because of babel/webpack/browserify/electron/nwjs - when you build a crossplatform app - you'd better take control of wrappers on your own. |
|
It's a simple wrap, why you can't add it? It will be feature for users. Users of any library doesn't want to write any wraps, they want to use ready lib in any comfortable way. |
|
Ok I'll provide example: When you use Masonry/Packery in your webapp it works fine unless you use the source code in Electron env. In electron env the app wont work because of the module wrappers. you have to require Masonry or to remove the wrapper or hide the module. See how much headache you get. If you intend to use require/import - it's alright. When it comes to non import/require implementation - you get more troubles with wrapped out-of-the-box libs. So yes - some want to use already wrapped, and some need clean libs. You might want to check the story with hiding modules to have a picture what I mean. |
|
Other projects generate both wrapped and unwrapped final JS files for different uses. |
Now you can import this polyfill to your project by:
let polyfill = require("./PATH_TO_LIB/classList");