WordPress.org

Make WordPress Core

Changes between Initial Version and Version 1 of Ticket #40834, comment 4


Ignore:
Timestamp:
06/13/2017 08:46:51 PM (4 years ago)
Author:
jhabdas
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #40834, comment 4

    initial v1  
    1 My .02 is that WordPress already has a great module system whereby users can enqueue anything they want. I've personally worked on both enterprise React projects and have published React Native to iOS, both of which included extensive use of Webpack. My personal experience as a developer was not a happy one.
     1My .02 is that WordPress already has a great module system whereby users can enqueue anything they want and define deps. It's extremely flexible.
    22
    3 Webpack is very complex IMO, and is a slippery slope WRT the involvement of Babel and friends. If the goal is to provide more modularity in the core to start moving towards ES6 I don't see why you'd need a bundler to do that when browsers will be able to support ES6 modules natively (whereas Node will not anytime soon, and the Node EPS will show the gory tale).
     3I've personally worked on both enterprise React projects and have published React Native to iOS, both of which included extensive use of Webpack. My personal experience as a developer was not a happy one. Webpack is very complex IMO, and is a slippery slope WRT the involvement of Babel and friends. If the goal is to provide more modularity in the core to start moving towards ES6 I don't see why you'd need a bundler to do that when browsers will be able to support ES6 modules natively (whereas Node will not anytime soon, and the Node EPS will show the gory tale).
    44
    55UMD already provides quite a bit of bloat. If you skip straight to ES6 you can use the browser as your REPL and leverage advanced loading techniques coming such as WHATWG Dynamic Imports to leapfrog beyond many emerging frameworks. Building on Node is not easy. Just ask the folks from Ghost Foundation.