Draft-js: Publish v0.10 to NPM as @next

[erykpiast]

Do you want to request a feature or report a bug? Feature

What is the current behavior? I cannot use v0.10 through NPM

What is the expected behavior? I can install draft-js v0.10 through npm i draft-js@next command

Which versions of Draft.js, and which browser / OS are affected by this issue? Did this work in previous versions of Draft.js? v0.10

I think it's common pattern to use @next or @beta to allow people to experiment with new stuff easily (see ESLint or Webpack). Or maybe there is already some way to use v0.10 through NPM which I cannot see now?

[rylev]

Version 0.10 fixes a big issue for us #667. Would be awesome to get this on NPM. Thanks so much!!

[JimLiu]

+1

[davidbyttow]

+1

[erykpiast]

@JimLiu @davidbyttow use reaction icon :) I'm happy you like my idea but "+1" comments make a mess.
https://github.com/blog/2119-add-reactions-to-pull-requests-issues-and-comments

[flarnie]

I think this is a great idea, and appreciate all the positivity on this thread. We will likely use the @next option to allow early use of 0.11.0. I'm hoping to release 0.10.0 within the next couple of days, but if any more delays occur then we will do a release under the @next tag for 0.10.0 as well. Thanks @erykpiast for this idea! I'll close this once we actually do the releases for 0.10.0 and 0.11.0@next.

[erykpiast]

I'm glad to hear that @flarnie, I'm glad :)

[adamlong5]

@flarnie Are you still planning to publish 0.11.0 under a @next tag?