[wp-trac] [WordPress Trac] #45145: Keep `@wordpress` packages up to date
WordPress Trac
noreply at wordpress.org
Mon Oct 29 04:34:47 UTC 2018
#45145: Keep `@wordpress` packages up to date
------------------------------+-----------------------
Reporter: atimmer | Owner: (none)
Type: defect (bug) | Status: assigned
Priority: highest omg bbq | Milestone: 5.0
Component: Build/Test Tools | Version: 5.0
Severity: blocker | Resolution:
Keywords: | Focuses:
------------------------------+-----------------------
Comment (by pento):
Maybe @nacin will remember why the build server requires a special
`package-lock.json`, I don't recall off the top of my head. I suspect it's
just that it doesn't like when running `npm install` causes the `package-
lock.json` file to change (in which case, the fix is pretty easy), but I
haven't confirmed that.
The build server needs to be fixed, but there are only a handful of people
with the ability to do that, and it's a low priority for all of them.
This doesn't really raise the barrier of entry at the moment, given that
the only packages being updated are the `@wordpress/` packages, which only
a handful of people can do. It will raise the barrier if left unfixed, but
no-one is arguing in favour of doing that.
--
Ticket URL: <https://core.trac.wordpress.org/ticket/45145#comment:25>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list