[wp-trac] [WordPress Trac] #43055: Reorganize Core JS / introduce build step

[WordPress Trac]

#43055: Reorganize Core JS / introduce build step
------------------------------+-------------------------
 Reporter:  omarreiss         |       Owner:
     Type:  enhancement       |      Status:  new
 Priority:  normal            |   Milestone:  5.0
Component:  Build/Test Tools  |     Version:  trunk
 Severity:  normal            |  Resolution:
 Keywords:  dev-feedback      |     Focuses:  javascript
------------------------------+-------------------------

Comment (by pento):

 I commented a little on [https://github.com/Varying-Vagrant-
 Vagrants/VVV/issues/1447#issuecomment-378846868 VVV repo], but to reply to
 your comments here, too:

 Replying to [comment:56 TJNowell]:
 > Not if you run it on the host machine. Part of the opposition of VVV to
 auto running `grunt watch` is that not every user is interested in
 developing core, yet an instance is installed out of the box. Running
 grunt watch in the provisioner would add overhead to every VVV users
 installs unless they disabled the core dev sites and imo that's an
 unreasonable ask.

 VVV is a wonderful general purpose tool, if Core's development environment
 were to use something else at the base, that isn't a slight on VVV: it's
 simply a case of Core being able to create a tool that's focussed on it's
 use cases.

 With the watch command as the example, I absolutely wouldn't ask you or
 anyone on the VVV team to impose that overhead on the wider VVV user base.

 > the goal being that you could copy it off a USB drive and run it, and it
 would step through every stage of setting up an environment:
 https://github.com/tomjn/vvv-cd-installer

 That tool is pretty cool, and certainly something we'd want to make
 available to all WordPress contributors. A nice GUI to walk through the
 setup process (both offline at contributor days, as well as online) is a
 million times better than running a bunch of shell commands.

 > As an aside, if we're moving more to webpack, should we not make use of
 npm scripts so that we maintain the same commands regardless of the tools
 behind the scenes? `npm run watch` `npm run build` etc

 Yah, we'd definitely move everything to npm scripts.

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