Add module to npm registry

[rroblik]

Hi Jawj !

Thanks for all hard work done, and more recently with the 1.0 release.

I used a fork of your dev in a webpack project (https://www.npmjs.com/package/overlapping-marker-spiderfier) because I didn't found your on npm registry.

As now your library can be loaded asynchronously form Google Maps, do you think you can add it to npm registry ?

that can be cool to easily integrate it !

Regards

[jawj]

You’re welcome!

I’m late to the party of browser-side dependency management. To clarify, is there any value publishing an npm package if I don’t also wrap stuff up to enable browserify (for example) to do its thing?

On 4 Apr 2017, at 17:44, Rroblik [email protected] wrote:

Hi Jawj !

Thanks for all hard work done, and more recently with the 1.0 release.

I used a fork of your dev in a webpack project (https://www.npmjs.com/package/overlapping-marker-spiderfier https://www.npmjs.com/package/overlapping-marker-spiderfier) because I didn't found your on npm registry.

As now your library can be loaded asynchronously form Google Maps, do you think you can add it to npm registry ?

that can be cool to easily integrate it !

Regards

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/jawj/OverlappingMarkerSpiderfier/issues/125, or mute the thread https://github.com/notifications/unsubscribe-auth/AAIpNOX_-HuIwyx2w9t6aAHTIDyhPkYfks5rsklEgaJpZM4My4SS.

[rroblik]

I think it could be done in multiple steps :) Regards

Le 5 avr. 2017 à 14:50, George MacKerron [email protected] a écrit :

You’re welcome!

I’m late to the party of browser-side dependency management. To clarify, is there any value publishing an npm package if I don’t also wrap stuff up to enable browserify (for example) to do its thing?

On 4 Apr 2017, at 17:44, Rroblik [email protected] wrote:

Hi Jawj !

Thanks for all hard work done, and more recently with the 1.0 release.

I used a fork of your dev in a webpack project (https://www.npmjs.com/package/overlapping-marker-spiderfier https://www.npmjs.com/package/overlapping-marker-spiderfier) because I didn't found your on npm registry.

As now your library can be loaded asynchronously form Google Maps, do you think you can add it to npm registry ?

that can be cool to easily integrate it !

Regards

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/jawj/OverlappingMarkerSpiderfier/issues/125, or mute the thread https://github.com/notifications/unsubscribe-auth/AAIpNOX_-HuIwyx2w9t6aAHTIDyhPkYfks5rsklEgaJpZM4My4SS.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.

[matpb]

+1 for the recent love given to OMS, thank you Jawj!

I was recently working on an NPM module for OMS and here is what I came up with, if that can give you some ideas: https://pastebin.com/7bYgf9aa

I added an argument so that it can be loaded async and feed the window.google object to the new OMS instance.

I also played with a new function "spiderfyAll" to always spiderfy all visible markers (required for a project) but it's quite hacky...

[danielkoch]

Any updates here? I found this one: https://www.npmjs.com/package/overlapping-marker-spiderfier But I'm not quite sure if this is maintained further more.

[SerkanSipahi]

any updates for npm support?

[olibri-us]

I would love to see this happen to ! Thanks anyway for the library man !

[strarsis]

@jawj: Yes! I am not able to find a built JavaScript library from this, installing from npm would be best practice.