published to npm as webgl-heatmap

[vicapow]

This isn't really an issue but thought it might be a good context to mention that I forked this project and converted it to ES5 and CommonJS, then published it to npm. see: https://github.com/vicapow/webgl-heatmap.

I did this mainly to require it in the heatmap-overlay I created for use with react-map-gl.

[pyalot]

That's awesome. I have a question though. How does npm resolve multiple packages resolving to webgl-heatmap?

[vicapow]

It's not possible to have multiple packages resolve to the same name.

[pyalot]

So by my counting there's 80 forks of that package, who gets to decide which of those 80 gets the name?

[vicapow]

It's first come, first serve with npm package names. Happy to give it to you, if you'd like (I think that's possible?)

[pyalot]

I see, nah I was just wondering. Seems kinda weird of npm to reserve unique names for stuff that may get forked a zillion times.

[vicapow]

I think that's why they added scoping: https://docs.npmjs.com/misc/scope

[cedricdelpoux]

@vicapow I get the error Error: Can't resolve 'fs' using [(https://github.com/vicapow/react-map-gl-heatmap-overlay) in file webgl-heatmap/heatmap-heights.js 4:9-22. It seems you did not reference any fs lib in your package.json but for now, the fs package seems do not exist anymore https://www.npmjs.com/package/fs