New release

[nip3o]

It's been a while and a couple of bug fixes since the latest release, maybe it's time for a new one?

[bpas247]

@taion @jquense how do we feel about this? We're currently experiencing a block for react-bootstrap at this PR because we haven't published a new release yet.

Is there anything left we should do before releasing the next version?

[jquense]

we need to get #299 in

[jquense]

we could maybe release a prerelease v3 tho here

[nip3o]

@jquense the popper PR is merged now, any more stuff that we need to wait on?

[mxschmitt]

Maybe we can release our first version with semantic-release once #372 is merged. @bpas247

[boxfoot]

I also ran into this -- saw a tag v2 and tried to use the code as written here, but it kept failing and it took me a while to figure out I was still running v1.2 which is the most recent version on npm.

Since v2 has been tagged in this repo, would you be open to publishing to npm (even as pre-release) so we can have access to it?

[TrySound]

@taion @jquense @bpas247 Is there a problem with new release? Would be good to get rid from commonjs dom-helpers.

[boxfoot]

As a work-around, I forked the repo and set up a branch that includes the compiled versions of scripts so I could install the new version as a git dependency. Feel free to use it until the new version is published on npm. https://github.com/boxfoot/react-overlays/tree/include-build

npm install --save github:boxfoot/react-overlays#include-build

[bpas247]

wasn't v2.0.0-0 already released though? you could just bump your version to that.

[boxfoot]

@bpas247 it's been tagged here in the repo, but hasn't been published to npm

But ye: Given that the release has been tagged here, and the code as tagged is working for me in my fork, it seems like publishing would be pretty easy.

[TrySound]

@boxfoot It's published

[bpas247]

Closing this now as the new release was published 😃