Closed yelworc closed 1 year ago
Thanks for reporting this, @yelworc. We'll look into this, but you also seem to know your way around Node.js, so if you are able to provide a PR, that will speed things up. We can then easily and quickly provide (you with) a new release. Is this something you could do?
Thanks for the quick response @otisg!
After opening the issue, I realized that this only applies when updating the package in a project where it's already installed; otherwise, ip
is installed in its latest version due to the ^
in package.json. I simply removed and re-added logsene-js
in my project, and it seems to be working just fine with Node 18.
Feel free to close the issue, or leave it open for the two unit tests that are failing on Node 18 (I briefly looked into that, but I'm not sure what the right approach would be there. Maybe it's just something in my environment that breaks them).
Tested in Node 18 and it works fine.
The lib does not declare compatibility with particular Node.js versions (e.g. via
engines
in package.json – maybe it should?), but it doesn't seem to work with Node 18:Updating the
ip
dependency (to v1.1.8) fixes the module loading issue, but there are still test failures (that don't occur with Node 16 on the same system):