Closed bagage closed 2 months ago
Well the version in the npm registry is ancient anyway and I assume it's only @jfirebaugh that has access to publish an update there. I certainly don't.
Some project (at least osmose) uses the master branch version directly, so it's still worth having it merged I think?
Well. Now I try to update this dependency in Osmose-QA and nowadays both yarn and npm block on this engines.node field.
I also think it could be harmless removed.
It does seem to be nonsensical in the modern age, so let's get rid of it...
This prevents using this library with
yarn
which does check that used version of node is compatible with the library.I do not think this library has any strong requirement regarding node version.