3 ms·
Luckily, with native javascript modules, there is no need for any of this anymore. We switched our whole codebase to <script type=module> and it's such a joy n
by TicklishTiger 8y ago
Luckily, with native javascript modules, there is no need for any of this anymore.
We switched our whole codebase to <script type=module> and it's such a joy now.
Never going back to bundlers. Never going back to having a compilation step on the server.
- sgslo 8y agoIts a good thought, but you're excluding ~15% of all web users[0] from using your product. [0] https://caniuse.com/#feat=es6-module https://caniuse.com/#feat=es6-module
- TicklishTiger 8y agoYup. We're going where the puck is going.
- soperj 8y agoEven Microsoft is telling people not to use ie11.
- miohtama 8y agoYes and no. For many use cases, this might be justified. * You are hosting an internal enterprise application and you are forcing all of your employee desktops to use Chrome any case. * You are not serving a web site, but a business web app, which only works on a modern browser - because it is a business oriented app people are willing to switch the browser to use it. E.g. 3d modeler.
- baroffoos 8y ago15% are only still on IE because it still works. If more devs start doing this you will be excluding 0% of users.