Upgrade to Node.js v25.8.1 compatibility

[badlee]

Summary

• Replace deprecated os.getNetworkInterfaces() with os.networkInterfaces()
• Replace all new Buffer() with Buffer.from() for Node.js 12+ compatibility
• Update package.json engines field to require Node.js >= 18.0.0
• Modernize variable declarations from var to const where appropriate
• Fix loose equality (==) to strict equality (===) in interface filtering
• Update major dependencies to latest compatible versions
• Add .npmignore file for proper package publishing

Verification

• Tested os.networkInterfaces() API
• Tested Buffer.from() API
• All deprecated APIs have been replaced

Notes

Some dependencies (modem, kannel, shorty) are custom packages from GitHub repositories and may need separate compatibility updates for Node.js 25.

Closes Node.js compatibility issues

[gemini-code-assist]

Code Review

This pull request updates the codebase to support Node.js >=18.0.0 by updating the engines field in package.json, replacing deprecated new Buffer() calls with Buffer.from(), and switching to the modern os.networkInterfaces() API. The review feedback highlights a compatibility issue in bin/cli.js where strict string comparison for IP families will fail on Node.js versions 18.0.0 to 18.3.0. Additionally, multiple potential runtime crashes were identified across several files due to unsafe calls to Buffer.from() and .toString() on potentially null or undefined values, with suggestions to add defensive fallback guards.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.

[gemini-code-assist]

In Node.js versions 18.0.0 through 18.3.0, the family property returned by os.networkInterfaces() is a number (4 or 6) rather than a string ('IPv4' or 'IPv6'). Since the project's engines field in package.json now specifies node: ">=18.0.0", using strict equality x.family === 'IPv4' will fail to match any IPv4 interfaces on those Node.js versions. To ensure compatibility across all Node.js 18+ versions, check for both 'IPv4' and 4.

Suggested change

	const interfacesList = Object.keys(interfaces).map(x=>interfaces[x].filter(x=>x.family === 'IPv4').map(x=>x.address).join(":"+settings.httpPort+", http://")).filter(x=>x).join(":"+settings.httpPort+", http://");
	const interfacesList = Object.keys(interfaces).map(x=>interfaces[x].filter(x=>x.family === 'IPv4' || x.family === 4).map(x=>x.address).join(":"+settings.httpPort+", http://")).filter(x=>x).join(":"+settings.httpPort+", http://");

[gemini-code-assist]

If data is null/undefined, or if data.receiver or data.sender is null/undefined, calling Buffer.from() or .toString() will throw a TypeError and crash the application. Since line 199 explicitly guards against data and data.receiver being undefined, line 200 must also be made safe to prevent runtime crashes.

Suggested change

	console.log("receive SMS",Buffer.from(data.receiver).toString(),Buffer.from(data.sender).toString(),data.msgdata.toString());
	console.log("receive SMS",Buffer.from(data && data.receiver || "").toString(),Buffer.from(data && data.sender || "").toString(),(data && data.msgdata || "").toString());

[gemini-code-assist]

If m.receiver is undefined or null, calling Buffer.from(m.receiver) will throw a TypeError and crash the process. Provide a fallback value (such as an empty string) to prevent runtime exceptions.

Suggested change

	this.sendSMS(m,Buffer.from(m.receiver).toString());
	this.sendSMS(m,Buffer.from(m.receiver || "").toString());

[gemini-code-assist]

If data.receiver or data.sender is undefined or null, Buffer.from() will throw a TypeError. Additionally, if data.msgdata is undefined or null, calling .toString() on it will throw a TypeError. Use defensive guards or fallback values to prevent potential runtime crashes.

Suggested change

	console.log("send SMS",Buffer.from(data.receiver).toString(),Buffer.from(data.sender).toString(),data.msgdata.toString());
	console.log("send SMS",Buffer.from(data && data.receiver || "").toString(),Buffer.from(data && data.sender || "").toString(),(data && data.msgdata || "").toString());

[gemini-code-assist]

If m.msgdata, m.receiver, or m.sender is undefined or null, Buffer.from() will throw a TypeError and crash the VM process. Use fallback values to ensure robustness.

Suggested change

	m.msgdata = Buffer.from(m.msgdata).toString().trim();
	m.receiver = Buffer.from(m.receiver).toString().toLowerCase();
	m.sender = Buffer.from(m.sender).toString().toLowerCase();
	m.msgdata = Buffer.from(m.msgdata || "").toString().trim();
	m.receiver = Buffer.from(m.receiver || "").toString().toLowerCase();
	m.sender = Buffer.from(m.sender || "").toString().toLowerCase();

[gemini-code-assist]

If m.sender is undefined or null, Buffer.from(m.sender) will throw a TypeError. Provide a fallback value to prevent runtime crashes.

Suggested change

	var _id = Buffer.from(m.sender).toString();
	var _id = Buffer.from(m.sender || "").toString();

[gemini-code-assist]

If value is null or undefined, calling value.toString() will throw a TypeError. Guard against null or undefined values before calling toString().

Suggested change

	var tml_buf = Buffer.from(value.toString());
	var tml_buf = Buffer.from((value !== undefined && value !== null ? value : "").toString());