[wp-trac] [WordPress Trac] #43055: Reorganize Core JS / introduce build step
WordPress Trac
noreply at wordpress.org
Tue Jan 9 15:15:42 UTC 2018
#43055: Reorganize Core JS / introduce build step
--------------------------+------------------------------
Reporter: omarreiss | Owner:
Type: enhancement | Status: new
Priority: normal | Milestone: Awaiting Review
Component: General | Version: trunk
Severity: normal | Resolution:
Keywords: dev-feedback | Focuses: javascript
--------------------------+------------------------------
Comment (by omarreiss):
This ticket was discussed today in #core-js on WordPress Slack, see
https://wordpress.slack.com/archives/C5UNMSU4R/p1515505132000043
The main concern that was raised was the transition problems that might
occur in not being able to run WordPress from the src directory anymore. I
took 3 options from the :
1) Stop allowing running from src and only build to `/build`.
2) Allow running from src after a build step but .gitignore the built
files.
3) Allow running from src and commit the latest stable version of JS in
src.
The general consensus seems to be that we need to have a transition period
in which we start out with option 3 and after some time transition to
option 2 and/or option 1. I will do another iteration to make this
possible.
I would personally be in favor of `gitignoring` the built files from the
start, because of the confusion that comes with having a set version of
build files in the source. This can lead to a myriad of issues that I'd
like to avoid. If we choose option 2 as the initial approach, the
configuration / dev workflow impact would be minimal, while the gain would
still be complete.
--
Ticket URL: <https://core.trac.wordpress.org/ticket/43055#comment:3>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list