Change npmjs name from @asymmetrik to @bluehalo to avoid confusion?

[turbolego]

Related to this commit:

ec848ee

Should this package move from https://www.npmjs.com/package/@asymmetrik/ngx-leaflet to https://www.npmjs.com/package/@bluehalo/ngx-leaflet to not be confused with github.com/asymmetrik that is now hijacked?

Related posts about the hijack:
#1
#2

[reblace]

We plan to move the package name. NPM.js doesn't provide a way to rename an organization so we'll probably have to create a new organization name and then start publishing to the new namespace.

[P4]

Hi @reblace, have you considered deprecating the original package to make the notice more visible?

I've stumbled upon the README note today pretty much by accident. I check my dependencies for updates mostly using automated tools and I imagine many people do the same. When you do that it's very easy to miss the info about the name change and just assume the package simply hasn't released a new version.

Here's a random example of a deprecation notice due to renaming from a project I'm working on:
https://www.npmjs.com/package/@humanwhocodes/config-array
which then generates a warning during installation:

npm warn deprecated @humanwhocodes/[email protected]: Use @eslint/config-array instead