[wp-trac] [WordPress Trac] #46951: Editor: Backport packages containing bug fixes from Gutenberg 5.5
WordPress Trac
noreply at wordpress.org
Wed Apr 17 05:22:03 UTC 2019
#46951: Editor: Backport packages containing bug fixes from Gutenberg 5.5
------------------------------+------------------------------
Reporter: aduth | Owner: (none)
Type: defect (bug) | Status: new
Priority: normal | Milestone: Awaiting Review
Component: Editor | Version: trunk
Severity: normal | Resolution:
Keywords: has-patch commit | Focuses:
------------------------------+------------------------------
Comment (by netweb):
Replying to [comment:5 netweb]:
> Aside: Those `https`<>`http` changes continue to occur:
>
> {{{#!diff
> --- Version 1
> +++ Version 2
> @@ -1541,8 +1541,9 @@
> - "resolved": "https://registry.npmjs.org/util/-/util-0.10.3.tgz",
> + "resolved": "http://registry.npmjs.org/util/-/util-0.10.3.tgz",
> }}}
Actually, I went and researched this issue a little further, the main
discussion appears to be in this [https://npm.community/t/some-packages-
have-dist-tarball-as-http-and-not-https/285/55 npm community] thread, the
thread is now closed, it also appears to be closed without a resolution
either, a workaround solution though is posted [https://npm.community/t
/some-packages-have-dist-tarball-as-http-and-not-https/285/56?u=netweb
here]:
{{{#!bash
npm install --global npm at 6.9.0
rm -rf ./node_modules
npm cache clean --force
npm install --prefer-online
}}}
After performing the above using the changes in [attachment:"46951.patch"]
except for the `package-lock.json` file results in the patch
[attachment:"46951.2.patch"] which does not include the `https` to `http`
changes. I'm not sure if future `npm install`'s should include the
`--prefer-onliune` flag or not, time will tell I guess but at least there
is a sane workaround for now.
--
Ticket URL: <https://core.trac.wordpress.org/ticket/46951#comment:6>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list