[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 jeremyfelt):

 This is great work so far @omarreiss, thank you.

 > 2) Allow running from /src after a build step but .gitignore the built
 files.

 This seems like the option least likely to impact existing workflows. If
 you work on JS, you'll already be used to the existing process and have
 likely used `grunt watch` as part of your workflow. If you work on PHP,
 then nothing really changes.

 > 1) Stop allowing running from /src and only build to /build

 That said, option 1 is much cleaner and I don't think it will be too
 impactful to users of VVV if we switch to a "must build" workflow. We
 already have a `build.wordpress-develop.test` that's intended to use with
 the `build/` directory and that is built with `grunt` by default during
 provisioning. We'll probably need to dust that off and make sure the docs
 are good.

 Personally - as long as the builds triggered by `grunt watch` (or whatever
 is doing the instant builds) are quick, especially when working on files
 that don't require a build, then +1.

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