If you mean using modules from NPM in a browser add-on, the Shield client extension recently started doing this < https://github.com/mozilla/normandy/tree/master/recipe-client-addon>
We do this by using webpack to process the node modules, bundling the entire dependency tree of a library into a single file. We then add a few more bits to make the resulting file compatible with `Chrome.utils.import`. You can see the webpack config file here < https://github.com/mozilla/normandy/blob/master/recipe-client-addon/webpack.config.js> and the way we use the resulting files here < https://github.com/mozilla/normandy/blob/48a446cab33d3b261b87c3d509964987e044289d/recipe-client-addon/lib/FilterExpressions.jsm#L12 > We suspect that this approach won't be compatible with all Node libraries, because it is fairly naive. But it has worked well for the ones we've used (React, ReactDOM, ajv, and mozjexl, so far). On Fri, Jul 28, 2017 at 10:13 PM Myk Melez <m...@mykzilla.org> wrote: > > Enrico Weigelt, metux IT consult <mailto:enrico.weig...@gr13.net> > > 2017 July 28 at 21:33 > > Hi folks, > > > > > > just curious: did anyone already try nodejs modules > > for (javascript-only) extensions ? > There was some discussion of this in the dev-addons thread "Node and Web > Extensions Experiment" > <https://mail.mozilla.org/pipermail/dev-addons/2016-November/002149.html>. > We also discussed a related idea in the firefox-dev thread "SpiderNode > for Firefox chrome code" > < > https://groups.google.com/forum/#!topic/firefox-dev/MWE-_1xkokk/discussion > >. > > -myk > > _______________________________________________ > dev-platform mailing list > dev-platform@lists.mozilla.org > https://lists.mozilla.org/listinfo/dev-platform > _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
