Any plan on releasing to npm ? about plate-map HOT 4 CLOSED

Looking more into the project, I seem to understand that you may already be releasing it as a ruby gem, although I couldn't find anything on https://rubygems.org/

Since this project is only 1% ruby code (just for packaging IIUC), it would make much more sense to approach the dependency the other way around IMO: depend on an npm package from your ruby app.

If you / your team is indeed more familiar with Ruby, maybe this guide to creating node modules will be of interest.

(as a side note, I observed that third-party js dependencies have been committed in vendor/assets/javascripts/. this doesn't scale, and can precisely be avoided with package managers like npm)

from plate-map.

This is a good suggestion ... i'm not sure when we'll get to look at it but I agree that this is mostly js so we should release it in that environment. I'm thinking about using bower as well which might help to elminate the embedded dependencies.

from plate-map.

Glad we agree. Bower themselves recommend migrating away from them. They suggest Yarn as an alternative, but two arguments would make me lean towards npm. Disclaimer: I am partial to npm since that's what we are currently using :)

• Feedback from someone who went to yarn then back to npm
• Yarn can [...] install any package from the npm registry anyway

Moreover, I believe the choice between the two is not so definitive, by that I mean that once the lib is packaged correctly, moving from one package manager to the other shouldn't be too hard.

from plate-map.

On a more practical note. We've decided to try and integrate plate-map to our own front-end app. If that goes well and suits our needs, I'd be keen for my team to have a go at packaging it, and submit a PR if all goes well.

from plate-map.