publish new ivy-codemirror version to npm's registry

I wanted to verify #39 was fixed in our application. Our application specifies "ivy-codemirror": "2.1.0" in package.json. That resolved a 2.1.0 version of this project from 5/13/2017. The npm registry also confirms it was published 2 years ago: https://www.npmjs.com/package/ivy-codemirror

I expect to see the v2.1.0 tag in GitHub mirror what is in npm's registry.

Can you publish the versions from GitHub to npm please?

[backspace]

@omghax, you seem to be the primary maintainer here, is there something users of this addon can do to help support it? Maybe it could become an adopted addon? Or you could add maintainers/releasers? There are a few projects that rely on it at HashiCorp and we’d love to help with these things if it would be of use. Thanks for all your work on this!

/cc @omghax @nbibler @nickawalsh
Hi folks! Could one of you cut a new release / rerelease 2.1? Thanks!

[backspace]

Perhaps a rename to ember-codemirror would be appropriate so we can make it an adopted addon? I don’t see any instructions on how to proceed with a non-responsive maintainer but I think we’ll need to do something 😳

[nbibler]

You guys are certainly welcome to fork / rename / whatever.

This library has largely not been updated or supported because we haven't found a lot of regular use for it. There were updates to CodeMirror which kind of made some of this library difficult to work with in its current form.

For example, about 3 weeks ago I put CodeMirror into an Ember application by creating an element modifier and using the NPM codemirror package (and @types/codemirror package) directly. It was fairly trivial and gave direct access to all of the optional modes, add ons, hooks, and whatnot from the codemirror package.

I think our interest was kind of lost with this add on when it started to become more difficult to work with the add on than with the library directly.

[DingoEatingFuzz]

I think our interest was kind of lost with this add on when it started to become more difficult to work with the add on than with the library directly.

Neat! Also kudos to the Ember core team for delivering on their goal to work better with the larger JS ecosystem.

[nbibler]

@DingoEatingFuzz: Agreed. 👍

If it's worthwhile, i can try throwing together a gist with how I setup a modifier implementation.

[DingoEatingFuzz]

I think that'd be awesome! We already have someone at HashiCorp looking to try it out 😀 Thank you!

[nbibler]

@DingoEatingFuzz: Try https://gist.github.com/nbibler/666c06f678e64a746a4366c68e5827db and see if that helps.

[vancluever]

@nbibler thank you! Will give that a go.

[vancluever]

@nbibler happy to report that this worked! Thanks for the guidance. I'm currently working on a minimal adaptation of this as I don't think we need as much as the modifier in the gist gives, but it's great to see how other things work as we need them!

[nbibler]

@vancluever: Glad to hear it! Good luck with your project!

[knownasilya]

Maybe update the readme and pointing to that gist and mention that this addon no longer provides the value it once did. From there probably worth archiving the repo.