Files
bitvid/artifacts/ONBOARDING_REPORT.md
T
google-labs-jules[bot]andPR0M3TH3AN 106f7640c4 fix(exploreData): trigger refresh immediately on visibility change
- `handleVisibility` only scheduled intervals but didn't trigger an immediate refresh when returning to the tab.
- This caused `tests/unit/services/exploreDataService.test.mjs` to fail (assertion `0 !== 1`).
- Added explicit calls to `refreshWatchHistoryTagCounts` and `refreshTagIdf` when `document.hidden` becomes false.

Co-authored-by: PR0M3TH3AN <[email protected]>
2026-02-18 15:10:29 +00:00

30 lines
1.3 KiB
Markdown

# Onboarding Audit Report
Date: 2025-02-11
## Summary
The onboarding process was audited by simulating a fresh checkout and running the documented commands. All steps passed successfully. To further improve reliability, strict Node version enforcement was added.
## Environment
- **Node Version**: v22.22.0
- **NPM Version**: 11.7.0
- **OS**: Linux (Sandbox)
## Commands Executed
1. `npm ci` - **PASS**
- Clean install of dependencies.
- Added 424 packages.
2. `npm run build:css` - **PASS**
- Built Tailwind CSS successfully.
3. `npm run format` - **PASS**
- Checked formatting for CSS, HTML, MD, Config.
- No files were modified (compliance verified).
## Configuration Checks
- **package.json**: `engines.node` is set to `>=22`.
- **.devcontainer/devcontainer.json**: Uses `mcr.microsoft.com/devcontainers/javascript-node:22`, consistent with `package.json`.
- **Dockerfile**: Uses `mcr.microsoft.com/playwright:v1.58.0-jammy`. Verified compatible with Node 22 requirement.
## Improvements Implemented
- **Enforce Node Version**: created `.npmrc` with `engine-strict=true`. This ensures developers are using the required Node version (>=22) during `npm install`/`ci`.
- **Documentation**: Updated `README.md` and `CONTRIBUTING.md` to explicitly mention the Node version requirement and its enforcement.