Doc load logs

[willosborne]

Description

Type of Change

• 🐛 Bug fix (non-breaking change which fixes an issue)
• ✨ New feature (non-breaking change which adds functionality)
• 💥 Breaking change (fix or feature that would cause existing functionality to not work as expected)
• 📚 Documentation update
• 🎨 Code style/formatting changes
• ♻️ Refactoring (no functional changes)
• ⚡ Performance improvements
• ✅ Test additions or updates
• 🔧 Chore (maintenance, dependencies, CI, etc.)

Affected Components

• CLI (cli/)
• Shared (shared/)
• CALM Widgets (calm-widgets/)
• CALM Hub (calm-hub/)
• CALM Hub UI (calm-hub-ui/)
• Documentation (docs/)
• VS Code Extension (calm-plugins/vscode/)
• Dependencies
• CI/CD

Commit Message Format ✅

Testing

• I have tested my changes locally
• I have added/updated unit tests
• All existing tests pass

Checklist

• My commits follow the conventional commit format
• I have updated documentation if necessary
• I have added tests for my changes (if applicable)
• My changes follow the project's coding standards

[rocketstack-matt]

Assume this is related to #1681 ?

I see we're still having the CVE scans fail 😢 will have to try some more things to see if I can get it working now it requires authentication, in the meantime I see Aidan approved but we have a conflict in the package-lock.json. Are you able to resolve that and we will merge.

[markscott-ms]

@willosborne I suspect your significant change to package-lock.json has broken the builds.

package-lock.json: 1,585 additions, 6,385 deletions

[willosborne]

@markscott-ms all i did was a fresh npm install - i havent changed the dependencies at all! i don't understand why this doesn't work. and i have to do it, because otherwise there are conflicts

[willosborne]

let me try removing node modules

[willosborne]

aha! deleting node_modules before an npm install fixed it...