fix: flag column and new ipfs-geoip dataset

[whizzzkid]

Blocked: ipfs-shipyard/ipfs-geoip#98

Issue: #317

In this PR:

• Corresponding PRs:
  • refactor: switch to DAG-CBOR ipfs-shipyard/ipfs-geoip#93
  • refactor: IPFS_GATEWAY ipfs-shipyard/ipfs-geoip#94
• Removed the Frontend libs loaded from the CDN.
• Replaced those with node module imports
• Now this can be built to lookup IP address.

How to test locally:

• Clone https://github.com/whizzzkid/ipfs-geoip/tree/fix/refactor/dag-cbor
• run npm i ../path-to-clone
• npm start

[whizzzkid]

explainers

[SgtPooki]

+1

[whizzzkid]

more explainers.

The weird thing I noticed while working with aegir flavoured esbuild, if I were to install a npm package locally, like:

$ npm i ../ipfs-geoip
$ npm run build
... success

The OS module get's pulled in like:

  // (disabled):os
  var require_os = __commonJS({
    "(disabled):os"() {
    }
  });

  // ../ipfs-geoip/node_modules/ip/lib/ip.js
  var require_ip = __commonJS({
    "../ipfs-geoip/node_modules/ip/lib/ip.js"(exports2) {
      var ip2 = exports2;
      var { Buffer: Buffer2 } = require_buffer();
      var os = require_os();
      ip2.toBuffer = function(ip3, buff, offset) {
        offset = ~~offset;
        let result;
        if (this.isV4Format(ip3)) {
          result = buff || Buffer2.alloc(offset + 4);

Followed here: https://github.com/indutny/node-ip/blob/main/lib/ip.js

---

However when pulled in from https://gitpkg.vercel.app/ipfs-shipyard/ipfs-geoip?refactor/dag-cbor the resolution fails with the Could not resolve "os"

The alternative was to replace the builtin import with sensible defaults e.g. os-browserify which seems to have fixed the build issues at least locally.

@lidel @SgtPooki your inputs will be valuable.

[lidel]

@whizzzkid I've released ipfs-geoip v9.0.0 with your ESM changes.

Mind refactoring this PR, so it uses Gateway instead of HTTP RPC client?

const gateway = 'https://ipfs.io'
await lookup(gateway, '66.6.44.4')

This is better because removes the need for RPC client library + Gateway responses have proper Cache-Control headers, which RPC does not have.

[lidel]

Fantastic, thanks!

ipfs-geoip is now ESM