The way we're generating ESM right now transpiles src into ESM which exports the required interfaces for performing geo-ip lookups. This works well for all agents that support module types and allows import/export syntax (e.g. browsers, node, etc) (except for the dependency issues in #100).
This relates to:
98
100
The way we're generating ESM right now transpiles src into ESM which exports the required interfaces for performing geo-ip lookups. This works well for all agents that support
moduletypes and allows import/export syntax (e.g. browsers, node, etc) (except for the dependency issues in #100).However, this takes away the ability to tree-shake the module when
ipfs-geoipis included as a dependency to sayipfs-webuibecause we're unable to bundle this properly. e.g. https://github.com/ipfs-shipyard/ipfs-geoip/actions/runs/3287072521/jobs/5415859864#step:5:124AI:
Would love to hear thoughts on this @SgtPooki, @lidel