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

 Replying to [comment:18 jaswrks]:
 > In `package.json`, would it be a good idea to remove `^` from any of
 these and force any version bump to occur as the result of an intentional
 hard-coded change? Seems worth considering in a project like WP core.

 I've already started doing this from r42463 and all `^` and `~` are
 removed from patches yet to be committed.

 Replying to [comment:19 omarreiss]:
 > @jaswrks thanks so much for helping out with this! I can see your point
 with regard to hard versions, but it would be good to have an easy way to
 detect available updates. Something like renovate would really help, but
 then we'd need to be on Github or similar.
 https://github.com/apps/renovate. On the other hand, the package-lock.json
 already locks dependencies to a specific versions so dependency updates
 don't happen involuntarily.

 The plan is to have Greenkeeper up and running on a mirror for this

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