Skip to content

build: regenerate bbb-learning-dashboard lockfile as lockfileVersion 3 - #24

Open
antobinary wants to merge 1 commit into
v4.0.x-developfrom
lockfile-v3-learning-dashboard
Open

build: regenerate bbb-learning-dashboard lockfile as lockfileVersion 3#24
antobinary wants to merge 1 commit into
v4.0.x-developfrom
lockfile-v3-learning-dashboard

Conversation

@antobinary

Copy link
Copy Markdown
Owner

What

Regenerates bbb-learning-dashboard/package-lock.json from lockfileVersion 2 to 3 using npm 10.9.8 (npm install --package-lock-only --lockfile-version 3). npm preserves the existing lockfile format on normal installs, so this needed an explicit regeneration.

Details

Format-only change — all 1589 resolved package versions are byte-identical. The diff is one changed line ("lockfileVersion": 23) plus removal of the legacy v1-compat dependencies section (~10,650 lines), shrinking the file from 816 KB to 502 KB.

Testing

On the 4.0 dev container (node 22.23.1 / npm 10.9.8):

  • npm ci against the new lockfile succeeds
  • npm run build compiles (only the pre-existing @mui/base eslint warnings)
  • Deployed the build to /var/bigbluebutton/learning-dashboard; /learning-analytics-dashboard/ serves the new bundle over HTTPS (200 on index and main.916a0946.js)

Regenerated with npm 10.9.8 (npm install --package-lock-only --lockfile-version 3).
Format-only change: all 1589 resolved package versions are identical; the
legacy v1-compat "dependencies" section is dropped.
@antobinary
antobinary force-pushed the lockfile-v3-learning-dashboard branch from 8c4c6d8 to 9a5a94d Compare July 24, 2026 01:25
@github-actions

Copy link
Copy Markdown

🚨 Automated tests failed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant