Releases: fvdm/nodejs-geoip2ws
v3.0.0 - New interface, major cleanup
- Breaking: Removed legacy interface and checks
- The module now only exports the lookup function.
- Removed the IP and service name checks. The API is already doing that.
- The
ip
now defaults tome
which is your current public IP. - Updated tests, docs and example to reflect the changes.
Full Changelog: v2.1.0...v3.0.0
v2.1.0
- Changed: Replaced http dep with native code
- Changed: No more (production) dependencies
- Changed: Minimum node engine v18
- Minor edits
Note: To reduce the maintenance time for my packages I now only develop for Node releases in the Active LTS
and Current
lines. It may work on Node releases with Maintenance
and EOL
status, but no guarantees. See the release schedule for details.
Full Changelog: v2.0.5...v2.1.0
v2.0.4
- Style: Better readable whitespace
Full Changelog: v2.0.3...v2.0.5
2.0.3
- Removed adding the
confidence
property when missing. The whole accuracy reporting is changing and breaking in the API. At the momentlocation.accuracy_radius
seems to be the most reliable source. - Minor documentation edits
- Updated dependencies and tests
Full Changelog: v2.0.2...v2.0.3
v2.0.2
v2.0.1
v2.0.0
v1.10.5
v1.10.4
Maintenance release to synchronize the package with the repository and minor changes in the docs and meta info.
This is probably going to be the last release with the legacy callback interface. I'm going to drop the legacy stuff soon in v2.0. It is too annoying to maintain. So in the next major release the function arguments can only be wrapped in an object geoip2ws ({ ip: '1.2.3.4' })
. Instead of allowing a callback function it will always return a Promise.
This new interface is already supported for a while now, so you can start converting your code if you are still going the old way.
v1.9.0 - Rewrite to promises
Callback is also still supported, but not both callbacks and promises at the same time.