Publish the next version of converse on npmjs

[lunika]

Is your feature request related to a problem? Please describe.

We would like to easily install the last development version of converse in a project and start theming it without waiting the release of the next version.

We are affected by the singleton bug introduced in version 8 and we have to skip this version to use the future version 9.

Publishing the next version can also ease the test of new feature and bug fix without having to modify the node_modules of a project and building converse inside it.

Describe the solution you'd like

We would like to run something yarn add converse.js@next or npm install --save converse.js@next. next is a prerelease and can not be installed by simply running yarn add converse.js.

I supposed this can be automated using your CI and on every merge on master, a build is made and pushed on npmjs with the next tag.

--- Want to back this issue? **[Post a bounty on it!](https://app.bountysource.com/issues/106357719-publish-the-next-version-of-converse-on-npmjs?utm_campaign=plugin&utm_content=tracker%2F194169&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://app.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F194169&utm_medium=issues&utm_source=github).

[roro-lv]

+1

[jcbrand]

I supposed this can be automated using your CI and on every merge on master, a build is made and pushed on npmjs with the next tag

How would this work with 2FA on npmjs.org?

[lunika]

This is explain here in the npmjs documentation: https://docs.npmjs.com/requiring-2fa-for-package-publishing-and-settings-modification

You should choose this option Require two-factor authentication or automation tokens to allow your CI to publish using an automation token.

[JatinSainiOO7]

Can I Work On This Build. Thankyou for assigning me if you can.