npm ci fails with EBADPLATFORM when lockfile contains darwin-only
packages (fsevents), even with --omit=optional. The --force flag
bypasses this check.
Both bridge packages now have clean shrinkwraps without devDependencies,
eliminating the fsevents (darwin-only) entries that caused Heroku build failures.
Use npm ci with --omit=optional to skip optional dependencies like
fsevents (darwin-only) that were causing build failures on Linux
platforms including Heroku and local Docker builds on Mac.
- Change engines.node from '^22.x || ^20.x' to '>=16.x'
- Change engines.npm from '>=10.x' to '>=8.x'
- Update runtime checkNodeVersion to allow Node 16+
- Creates overlap with previous release (^16.x || ^14.x)
This allows users on Node 16/18 to upgrade smoothly while
recommending Node 20 or 22 LTS for best support.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
- share2nightscout-bridge: 0.2.9 → 0.2.10 (Node 22 support)
- minimed-connect-to-nightscout: 1.5.5 → 1.5.6 (Node 22 support)
Both packages now allow Node 18/20/22+ in their engines field.
This is a prerequisite for the Node 22 upgrade (PR #8357).
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
- share2nightscout-bridge: 0.2.9 → 0.2.10 (Node 22 support)
- minimed-connect-to-nightscout: 1.5.5 → 1.5.6 (Node 22 support)
Both packages now allow Node 18/20/22+ in their engines field.
This is a prerequisite for the Node 22 upgrade (PR #8357).
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Switching the way units is fetched to this way makes it similar to the other
code already in place that does something similar. This allows the tests to
pass with the existing fixtures.
Considering augmenting additional tests that explicitly tests whether the
relevant branch of code is taken.
When someone is looking at Nightscout and needs the alarm silenced, it is very
desirable to always silence the local UI. This patch documents some of the
working code around handling the alarm notification process, as well as
provides commentary on handling unauthorized scenarios. There are some open
questions such as how to update the permission set after authorization.
Create an opportunity to respond with something other than a global ack when
someone that is not authorized sends an acknolwedgement to an alarm.
Eliminate double-initializing when subscribing to alarms. The `callback`
variable is not local to the function, anyway.
This patch eliminates debugging logging in favor of commentary to capture how,
where, and why alarmSocket feature is causing different pages to demand the
authentication prompt in a variety of circumstances.
This patch is intended to allow customizing the behavior for whether or not to
prompt for authorization before subscribing or acknolweding alarms.
There was a bug in previous attempts where the profileeditor would be double
initialized, causing the profileeditor to remove some buttons from the GUI.
This patch adds checking for a permission specifically related to acknolwedging
alarms, as well as avoids double-initializing the editor, which causes the
issue with the GUI.
This patch adjusts the user feedback while the server is initializing to
communicate that Nightscout startup sequence should take closer to 15 second
than 5 seconds.
This patch allows the operator to control whether or not the API Secret
authentication dialog will display by default or not. Historically Nightscout
allows a configuration to be readable and to send alarm information to all
displays.
A change in in dev in February to support authentication and api v3 introduced
a new configuration where websocket communication is authenticated, and the API
Secret modal will display if it authenticates in error. The side-effect is
that all new instances, even readable instances with glucose data, can't be
seen or monitored without putting in the API Secreet or explicitly dismissing
it.
This patch returns to the default behavior while allowing to select the new one
using authenticationPromptOnLoad in the settings communicated from server to
client. If people strongly prefer, we can reverse to the new behavior over
time.
To select the old behavior with no API Secret needed for readabable data, do nothing.
To select the new behavior where the API Secret prompts occur on load, set
`AUTHENTICATION_PROMPT_ON_LOAD=1`.
With this patch, the new version of nightscout-connect will support
all the features of share2nightscout-bridge,
minimed-connect-to-nightscout, and more.
Ben West
