Description
Hello there,
There seems to be an issue in the package.json.
Currently, you have a fixed git checkout to js-function-reflector
but that requires the user to have git available.
While this is no problem for your all-day developer, this means you need git at install-time. So including z
into software that is used by the average software "user" will become difficult (of course, we can question how often the average user uses npm).
Also, this makes it hard to use z
in environments where you wish to have as few dependencies as possible, such as docker containers or strict production machines.
Another argument against having git references is that you might wish to have "the correct" version in your software. Meaning when I create a package today, I want it to behave the same tomorrow to ensure the working of my package.
I can actually not reproduce this but a colleague had this issue. I suppose you can enforce it by removing git from your system and try to install z.
What are your thoughts on this?