Build failures due to fsevents (requiring Darwin)

[psonnera]

Describe the bug
When building the app, Heroku fails due to a couple of dependencies requiring Darwin

cgm-remote-monitor/package-lock.json

Line 7346 in b03c604

"node_modules/minimed-connect-to-nightscout/node_modules/fsevents": {

cgm-remote-monitor/package-lock.json

Line 10957 in b03c604

"darwin"

To Reproduce
Deploy in Heroku

Expected behavior
fsevents should be option like here

cgm-remote-monitor/package-lock.json

Line 5220 in b03c604

"optional": true,

IMHO

[psonnera]

Installing binaries
engines.node (package.json): >=16.x
engines.npm (package.json): >=8.x
Resolving node version >=16.x...
! The requested Node.js version is using a wide range (>=16.x) that can resolve to a Node.js major version
higher than you intended. Limiting the requested range to a major LTS range like 24.x is recommended.
https://devcenter.heroku.com/articles/nodejs-support...
! The resolved Node.js version has been limited to the Active LTS (24.14.0) for the requested range of >=16.x.
To opt-out of this behavior, set the following config var: NODEJS_ALLOW_WIDE_RANGE=true
https://devcenter.heroku.com/articles/nodejs-support...
Downloading and installing node 24.14.0...
Validating checksum
Bootstrapping npm >=8.x (replacing 11.9.0)...
npm warn Unknown cli config "--unsafe-perm". This will stop working in the next major version of npm.
npm 11.11.0 installed
-----> Restoring cache
Cached directories were not restored due to a change in version of node, npm, yarn or stack
Module installation may take longer for this build
-----> Installing dependencies
Installing node modules
npm error code EBADPLATFORM
npm error notsup Unsupported platform for fsevents@2.3.3: wanted {"os":"darwin"} (current: {"os":"linux"})
npm error notsup Valid os: darwin
npm error notsup Actual os: linux
npm error A complete log of this run can be found in: /tmp/npmcache.l9B7D/_logs/2026-03-02T03_09_09_501Z-debug-0.log
-----> Build failed
We're sorry this build is failing! You can troubleshoot common issues here:
[https://devcenter.heroku.com/.../troubleshooting-node...]
Some possible problems:

• Dangerous semver range (>) in engines.node
  https://devcenter.heroku.com/articles/nodejs-support...
  Love,
  Heroku
  ! Push rejected, failed to compile Node.js app.
  ! Push failed

[psonnera]

@bewest is that supposed to compile with Node 24? Might need indeed adjusting upper range to stick to 22...

[bewest]

Thanks for the update. I think issue is with minimed connect plugin pulling it in if I recall. Can try taking that out now since it doesn't work anyway