Bugzilla

I need to vendor the [Puppeteer repository] along with its dependencies
in central for this bug.  My initial plan is to put the dependencies
under third_party/nodejs/ and annontate them with [moz.yaml] files,
and to put the Puppeteer repo under remote/test/puppeteer/.

I then intend to introduce a new mach command (something like `./mach
remote vendor-puppeteer`) to pull in the latest changes from GitHub.
This will allow the remote protocol to track progress towards
achieving [full Puppeteer API support].

Does that all sound reasonable to you?

[Puppeteer repository]: https://github.com/GoogleChrome/puppeteer/
[moz.yaml]: https://blog.glob.com.au/2018/06/15/moz-yaml/
[full Puppeteer API support]: https://bugzilla.mozilla.org/show_bug.cgi?id=puppeteer

I need to vendor the [Puppeteer repository] along with its dependencies
in central for this bug.  My initial plan is to put the dependencies
under third_party/nodejs/ and annontate them with [moz.yaml] files,
and to put the Puppeteer repo under remote/test/puppeteer/.

I then intend to introduce a new mach command (something like
`./mach remote vendor-puppeteer`) to pull in the latest changes from
GitHub.  This will allow the remote protocol to track progress towards
achieving [full Puppeteer API support].

Does that all sound reasonable to you?

[Puppeteer repository]: https://github.com/GoogleChrome/puppeteer/
[moz.yaml]: https://blog.glob.com.au/2018/06/15/moz-yaml/
[full Puppeteer API support]: https://bugzilla.mozilla.org/show_bug.cgi?id=puppeteer