English | 中文

High-performance Node.js native addon for ip2region xdb query with IPv4/IPv6 support. Written in TypeScript with full type definitions.

Note: This project is based on the official ip2region C client with enhanced TypeScript support.

• 🚀 High Performance - Native C++ implementation with microsecond-level response
• 🌐 IPv4 & IPv6 - Full support for both IPv4 and IPv6 address queries
• 💾 Multiple Cache Strategies - file/vectorIndex/content caching options
• 🔒 Memory Safe - Automatic resource management prevents memory leaks
• 📝 TypeScript - Complete TypeScript type definitions included
• 🔧 Cross Platform - Works on Windows, Linux, and macOS
• 📦 Auto-Updated Data - Database files are automatically synced daily

npm install ts-ip2region2
# or
pnpm add ts-ip2region2
# or
yarn add ts-ip2region2

Database Included: Database files are now bundled and automatically extracted during installation.

import { Ip2Region } from 'ts-ip2region2';

// Create searcher instance (uses bundled data)
const searcher = new Ip2Region();

// Or with options
const searcher2 = new Ip2Region({ cachePolicy: 'content', ipVersion: 'v6' });

// Or specify custom database path
const searcher3 = new Ip2Region('./custom.xdb', {
  cachePolicy: 'vectorIndex',
  ipVersion: 'v4'
});

// Query IP address
const result = searcher.search('120.229.45.2');
console.log(result);
// Output: { region: '中国|广东省|深圳市|移动', ioCount: 3, took: 1000 }

// Clean up
searcher.close();

// Using default bundled data
new Ip2Region()
new Ip2Region(options: Ip2RegionOptions)

// Using custom database
new Ip2Region(dbPath: string, options?: Ip2RegionOptions)

• search(ip: string): SearchResult - Query IP address location
• close(): void - Release resources

• Ip2Region.verify(dbPath: string): boolean - Verify xdb file
• Ip2Region.verifyDetailed(dbPath: string): VerifyResult - Verify with detailed info

interface SearchResult {
  region: string; // Geographic location
  ioCount: number; // Number of IO operations
  took: number; // Query time in microseconds
}

interface Ip2RegionOptions {
  cachePolicy?: 'file' | 'vectorIndex' | 'content';
  ipVersion?: 'v4' | 'v6';
}

Benchmark results on Windows x64 with Node.js v22.14.0 (10,000 iterations):

Performance Improvements:

• vectorIndex is ~40% faster than file mode
• content is ~95% faster than vectorIndex mode
• content is ~96% faster than file mode

Comparison with Native C:

• Native C (vectorIndex): ~5 μs/op
• Node.js Addon (vectorIndex): ~22 μs/op
• Overhead: ~4.4x (mainly from N-API call overhead)

Despite the N-API overhead, the performance is still excellent for most use cases, achieving 45,000+ QPS with vectorIndex mode.

Recommendation: Use vectorIndex for most scenarios as it provides excellent performance with moderate memory usage.

Run benchmark yourself:

npm run benchmark

# Build and run example
npm run example

# Build and run tests
npm test

# Build native addon
npm run build

# Compile TypeScript
npm run compile

ts-ip2region2/
├── src/                       # TypeScript source code
│   └── index.ts              # Main TypeScript API
├── dist/                      # Compiled JavaScript output
│   ├── index.js
│   ├── index.d.ts
│   └── ...
├── data/                      # Bundled xdb database files
│   ├── checksums.json
│   └── ip2region.7z
├── extracted/                 # Extracted database files
│   ├── ip2region_v4.xdb
│   └── ip2region_v6.xdb
├── ip2region/                 # Original ip2region C source
│   ├── xdb_api.h
│   ├── xdb_util.c
│   └── xdb_searcher.c
├── scripts/                   # Build and utility scripts
├── addon.cpp                  # Node.js addon implementation
├── binding.gyp                # Build configuration
├── example.js                 # JavaScript example
├── tsconfig.json              # TypeScript configuration
├── package.json
└── README.md

Contributions are welcome! Please feel free to submit a Pull Request.

Apache-2.0