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

WordPress Trac noreply at wordpress.org
Wed Jan 10 07:10:48 UTC 2018


#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 jorbin):

 Thanks for working on this @omarreiss! I fully support us doing this, but
 have a handful of thoughts and questions before I think it should be
 committed to core.  I still need to review the actual code, but here are
 some thoughts on the idea and process for proceeding.

 1) We should add file mapping to `grunt-patch-wordpress` so that we don't
 invalidate every single patch on trac that has JS in it.

 2) Should we also modify the organization of qunit tests? The standard
 that we have used there is for test file names to match the path and name
 of files being tested.

 3) We should come up with a communication plan for this.  I think
 something along the lines of:
 - announcing it in dev chat the week this will land
 - Have a make/core post ready to go live within a few minutes of this
 landing in core

 4) We should have some documentation about how to patch libraries that we
 load and also how to test those patches. `npm link` can be a new barrier
 to testing changes for many developers.

 5) If we start relying on more and more external JS, I would love to come
 up with some philosophy points around it. In general, we should be relying
 on projects that have a strong commitment to backward compatibility.

 6) as far as transitioning, I lean towards going all in and communicating
 it loud. This may also require working with maintainers of things such as
 VVV and other common dev platforms so that they are ready for the change.

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


More information about the wp-trac mailing list