Package name

[mixn]

Hey @jeremija,

I just finished working on my own npm card (like this) and it failed when I tried publishing, this lead me to your mixn project. :)

I was wondering if you’d be willing to maybe republish the package under a different name, something like mixn-reducer, e.g. not just mixn? That’d be absolutely phenomenal and I’d appreciate it a lot. Being able to npx mixn for my card would just be awesome. :)

Thank you!

[jeremija]

Hi @mixn,

Because of the way npm works, I do not think there is a good way to handle this, unfortunately. A number of existing projects use mixn as a dependency, and removing the current functionality from the mixn could break the builds of these projects in the future. I no longer have access to most of the ones I worked at, and some of them are pre-package-lock.json.

The way I see it, there are two options:

a) Deprecate the current package to alert the current users to use a package with a different name. if I granted you rights and you then published a new major version, all users would still get the deprecation message when they try to install or run the library.

b) Since this library doesn't provide any runnable files, I could accept a pull request of with a script that prints your personal details.

I'm in the favor of option b) because this means the existing users of this library would not need to make any changes. The main and only condition would be to not introduce any dependencies because this library does not require any.

Let me know what you think.