Please release main to npm — 2.2.7 still ships the pre-refactor crash (undefined threshold / null trend)

[fakehec]

main (the TypeScript refactor) fixes a crash that the latest published version — 2.2.7 (Feb 2025) — still ships:

• In trend.js, THRESHOLDS_RATIO.sort(ascendingNumbers).find(t => Math.abs(ratio) < t.pascal) returns undefined when Math.abs(ratio) is not < any threshold (i.e. ratio is NaN/Infinity, which happens with degenerate pressure history — samples with equal/invalid timestamps making difference / from blow up). The next line reads threshold.trend.key unguarded → TypeError: Cannot read properties of undefined (reading 'trend'). (ascendingNumbers also compares the threshold objects by subtraction, so the sort is a no-op NaN comparator.)
• One level up, getPredictions() reads pressureTrend.tendency when getTrend() returned null → Cannot read properties of null (reading 'tendency').

Both are already handled on main:

• src/trend.ts — .sort((a, b) => a.pascal - b.pascal) and if (!threshold) return null;
• index.ts — if (pressureTrend === null) return null;

The problem is only that these fixes aren't released: npm latest is still 2.2.7, which predates the refactor. So a fresh npm install of signalk-barometer-trend pulls the crashing build — it throws on essentially every pressure sample and repeatedly takes the SignalK server down (reported downstream at oyve/signalk-barometer-trend#24, where the user's workaround was to disable the plugin).

Would it be possible to cut a new release from main so downstream can depend on the fixed version? Thanks for maintaining this.

[fakehec]

Extra detail that should make this easy: main's package.json is already bumped to 2.2.8 (with main: dist/index.js and the build script in place), so it looks release-ready — it just hasn't been npm published. The registry latest is still 2.2.7 (Feb 2025).

As of July 2026 that means the only version installable from npm has been the crashing one for well over a year, and anyone doing a fresh npm install signalk-barometer-trend hits it (the fix in main never reaches them). A npm publish of 2.2.8 would resolve it for all downstream users. Thanks again!