Bug 1540655 Comment 5 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

Original comment by
on 
I don’t think `./mach vendor` supports Node.js quite yet, but my
thinking was to manage the third-party dependencies using that so
that they could live under third_party/.

As we need to lock the Puppeteer version to the remote agent and
have the ability to apply custom patches to it, I want to manually
export a git clone into remote/test/puppeteer/.  I mentioned `./mach
remote vendor-puppeteer` because those steps can be automated: not
as a replacement for `./mach vendor`.
Revision 1 by
on 
I don’t think `./mach vendor` supports Node.js quite yet, but my
thinking was to manage the third-party dependencies using that so
that they could live under third_party/.

As we need to lock the Puppeteer version to the remote agent and
have the ability to apply custom patches to it, I want to manually
export a git clone into remote/test/puppeteer/.  I mentioned
`./mach remote vendor-puppeteer` because those steps can be automated:
not as a replacement for `./mach vendor`.
Revision 2 by
on 
I don’t think `./mach vendor` supports Node.js quite yet, but my
thinking was to manage the third-party dependencies using that so
that they could live under third_party/.

As we need to lock the Puppeteer version to the remote agent and
have the ability to apply custom patches to it, I want to manually
export a git clone into remote/test/puppeteer/.  I mentioned
`./mach remote vendor-puppeteer` because those steps can
be automated: not as a replacement for `./mach vendor`.

Back to Bug 1540655 Comment 5