A long time ago, I made the npm publishing of jvectormap (and the new package named jvectormap-next). I recently made a react wrapper for the map, which doesn't suffer from rerender problems (you can change props without resetting the zoom for example)
I also made a package for maps, which can be consumed by both the jquery plugin and the react wrapper.
Maybe the community could join efforts on package maintenance. My hope is to create a @jvectormap npm scope with all useful packages
@jvectormap/jquery : the jquery plugin (I failed to contact the author for permission) based on jvectormap-next
@jvectormap/react : the react wrapper. Although little used (except for private projects) my package @stadline/react-vectormap is robust. This is where your contribution is the most valuable because we share the same purpose
I already started to work on a monorepo to host the packages https://github.com/alex-pex/jvectormap but my best skill is not writting good documentation
Hey @alex-pex , sorry for the late response.
Actually my latest work introduces a similar approach. You can see it in the codebase since it's already merged to master.
I'd love to collaborate on this.
Hello,
A long time ago, I made the npm publishing of jvectormap (and the new package named jvectormap-next). I recently made a react wrapper for the map, which doesn't suffer from rerender problems (you can change props without resetting the zoom for example)
I also made a package for maps, which can be consumed by both the jquery plugin and the react wrapper.
Maybe the community could join efforts on package maintenance. My hope is to create a @jvectormap npm scope with all useful packages
I already started to work on a monorepo to host the packages https://github.com/alex-pex/jvectormap but my best skill is not writting good documentation
What do you think?