[wp-trac] [WordPress Trac] #40894: Use Webpack instead of Browserify for build process

[WordPress Trac]

#40894: Use Webpack instead of Browserify for build process
------------------------------+------------------------------
 Reporter:  adamsilverstein   |       Owner:  adamsilverstein
     Type:  enhancement       |      Status:  assigned
 Priority:  normal            |   Milestone:  4.9
Component:  Build/Test Tools  |     Version:  3.5
 Severity:  normal            |  Resolution:
 Keywords:  has-patch commit  |     Focuses:  javascript
------------------------------+------------------------------

Comment (by adamsilverstein):

 @aduth

 Thanks for the review, feedback and questions.

 I don't think we need to add minification here, we already handle that in
 our main build process which we run to package releases. For development,
 the unminified version is preferable and this approach fits nicely with
 our existing build tool chain.

 One additional use I imagine for webpack is importing/building our
 [https://www.npmjs.com/org/wordpress npm packages] in the wp namespace for
 inclusion in core.

 Regarding splitting the configuration files, I had originally tried a
 single file and split it up based on
 [https://core.trac.wordpress.org/ticket/40894#comment:17 this comment] and
 thinking it may help optimize the production/dev builds down the road.

 I will try to clean up the configs, removing stats and maybe moving
 watch:true as well as fixing your other noted format items.

 > What does this configuration look like when it scales to accommodate
 building both media and Gutenberg?

 Thats a great question we need to figure out the answer to - hopefully we
 can port over much of what exists in the project. Having webpack in our
 core toolset will be a prerequisite.

--
Ticket URL: <https://core.trac.wordpress.org/ticket/40894#comment:25>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform