Luca Greco

As a workaround for this issue (until we have been able to handle it with a more proper fix), `--target=chromium` can be passed as an explicit argument in an npm...

@eight04 I tried to reproduce the issue on windows 10 and I was unable, and so I'd like to ask you some additional detail to get a better picture of...

> This seems related to Firefox starting external processes, for a while I would get this only if I started a browser toolbox instance and left it open while I...

@slhck That's true, any tab which contains an extension page related to the extension being reloaded is going to be closed, but it is not `web-ext run` that is closing...

:+1: Thanks @saintsebastian

For future reference: long time ago I created a small [`create-webextension`](https://www.npmjs.com/package/create-webextension) npm package that does generate a boilerplate extension (I often use it to generate small test extensions), e.g. you...

> Going forward, Is there a plan to integrate this feature with web-ext? @ankushduacodes I'm a bit on the fence about it, but I avoided to use any big or...

> @rpl Do you think its good idea to add some documentation [here](https://github.com/mozilla/extension-workshop/blob/fb8a05c7e76760be6a86502dd27a1af368ef3ea9/src/content/documentation/develop/getting-started-with-web-ext.md#using-web-ext) in extension-workshop so that people are aware of the existence of this tool? In extension-workshop we do...

@ankushduacodes :+1: sounds a good idea (at least in my opinion)

@Fedcomp since when this issue was filed a few things are being done: - both npm and yarn introduced a command to bootstrap a package, and long time ago I...