push docson to npm

[yanick]

@rom1504 The master branch is now in a npmsable state. Would you be willing to give back the npm docson namespace to this version of the project?

[rom1504]

Sure no problem, just please publish a new major version compared to what is already published (1.0.2 is published so just publish a 2.0.0), so that dependents on the current lib don't break. What is your nickname on npm so I can add you as maintainer there ?

…

On Thu, Jul 19, 2018, 02:57 Yanick Champoux ***@***.***> wrote: @rom1504 <https://github.com/rom1504> The master branch is now in a npmsable state. Would you be willing to give back the npm docson namespace to this version of the project? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#70>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ACPN_udUNx61TO-XhWmfgRVGc_7jJZ39ks5uH9l9gaJpZM4VVlmk> .

[rom1504]

Well except if you didn't change the API at all compared to what is currently published and it won't be breaking ?

[yanick]

Yeah, I already tagged the latest milestones in master as v2.0.0 in preparation for that. :-)

And I'm yanick on npm. I'm anything if not consistent. ^.^

[rom1504]

Ok I've added you as maintainer on npm, you can publish.

…

On Thu, Jul 19, 2018, 16:26 Yanick Champoux ***@***.***> wrote: Yeah, I already tagged the latest milestones in master as v2.0.0 in preparation for that. :-) And I'm yanick on npm. I'm anything if not consistent. ^.^ — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#70 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ACPN_heGO4ZqCPOqAu4lF11ZMYVsj3nxks5uIJclgaJpZM4VVlmk> .

[yanick]

Awesome. Thanks!

[yanick]

It is done. Woot!