So it looks like you're running a github action that downloads the latest maxmind data and publishes a new npm version, weekly?
Can you provide some mechanism for how one could easily update the data in a production environment? other than running 'npm update fast-geoip' on all our servers every night?
when deploying on edge, __dirname is not defined, also it's said as a best practice to bundle all js in a single file to optimize cold start. hence, the code in here:
We were looking at replacing our version of geoip-lite with this library, but realized that the results returned from this library are incorrect; using the example IP (207.97.227.239) in the Readme results in the following:
There wasn't much increase in memory used. However, on a 1cpu 1gb memory VPS, it's consistently running at 50-80% CPU even when my express app is idle.
In comparison, without fast-geoip, my node application is running at 0.5-1% CPU.
Hello! I am using NextJS Middleware and would like to associate basic geo info with IPs and possibly bounce some IPs based on their location. It seems the NextJS Middleware API surface is limited compared to pure Node and as such neither geoip-lite nor fast-geoip work there. Would you consider adding support for Next Middleware? I am not even sure it would be technically feasible, just checking to see if you've thought about this before in case you are a Next user.