Julien Fontanet

@furqanZafar Any news on this?

The `console.log` indeed displays the freshly set secure context, but nevertheless, the (openssl) client does receive the previous one.

The only way to talk to the plugin is to use the `plugin.configure` method. If more interactivity is needed, we can update the plugin to expose specific API methods.

`engines` is already a standard field in `package.json`, see [the documentation](https://docs.npmjs.com/files/package.json#engines). Concerning the browsers, `preset-env` uses `browserslist` which does expose a pseudo-standard `browserslist` field ([doc](https://github.com/ai/browserslist#browserslist)).

Yes, it could support browsers as well, but this probably an issue that should be created in the `browserslist` repo :)

Agreed, but this should be overridable (maybe with `node: false`).

I believe so. @existentialism do you confirm?

I agree with you, the backup should run on other non-disabled remotes. Regarding your second comment, I believe it works as expected (ie the backup run on connected pools), am...

All plugins now throw in case of errors. List of plugins used by XO: - `updater.py` - `check_update`: not impacted - `update`: no longer a JSON, returns a task ref...

It should already be using multiple connections, I'll discuss this with @fbeauchamp next week and will keep you posted.