NPM Package Dependencies in Launch Scripts are Inconsistent Between Windows & Linux #15

Open
opened 2025-04-14 21:37:59 -06:00 by nicole · 2 comments
Owner

The NPM packages that are installed by the install script for each operating system are supposed to have identical NPM packages. In this instance, the Windows powershell script is more up-to-date than Linux and Linux needs to be caught up to reach parity with the Windows script.

The NPM packages that are installed by the install script for each operating system are supposed to have identical NPM packages. In this instance, the Windows powershell script is more up-to-date than Linux and Linux needs to be caught up to reach parity with the Windows script.
nicole added the
Kind/Bug
Priority
High
labels 2025-04-14 21:37:59 -06:00
nicole self-assigned this 2025-04-14 21:37:59 -06:00
Author
Owner

Proposal:

  • Take the requirements.txt approach that python uses but use it for NPM. Make it so both scripts share the same dependency list as a text file named NPM_Packages.txt
  • Reorganize the dependencies for the agent, server, and NPM into a centralized "Dependencies" folder that all of the various scripts pull from
    • Agent_Requirements.txt
    • Server_Requirements.txt
    • NPM_Packages.txt
Proposal: - Take the `requirements.txt` approach that python uses but use it for NPM. Make it so both scripts share the same dependency list as a text file named `NPM_Packages.txt` - Reorganize the dependencies for the agent, server, and NPM into a centralized "Dependencies" folder that all of the various scripts pull from - `Agent_Requirements.txt` - `Server_Requirements.txt` - `NPM_Packages.txt`
Author
Owner

Centralized package management via /Data/WebUI/package.json

This is an industry-standard way of managing packages and versions, and will eventually be cross-platform once the linux version of the launch script is re-tooled to incorporate it like the Windows launch script is now. This makes the NPM installation step nearly instant after the first launch.

Centralized package management via <ProjectRoot>/Data/WebUI/package.json This is an industry-standard way of managing packages and versions, and will eventually be cross-platform once the linux version of the launch script is re-tooled to incorporate it like the Windows launch script is now. This makes the NPM installation step nearly instant after the first launch.
Sign in to join this conversation.
No description provided.