Check browser JavaScript with host-only ESLint

[jatmn]

Summary

• Run ESLint in CI on the printer browser scripts (web/www/js) and the docs-site script (website/assets/js).
• Keep the checker on the build host under tools/eslint. It is not copied into printer packages.
• Leave the existing ES5 page scripts unchanged. A self-test shows the real files pass and an undefined name fails.

Test plan

• npm ci --ignore-scripts --prefix tools/eslint
• bash tools/eslint-web-selftest.sh
• bash tools/select-ci-validation-selftest.sh
• reuse lint
• Host stub builds for print service, web, UI, and Digital Factory
• GitHub policy-validation runs the new ESLint step on this pull request

Summary by Sourcery

Add host-only ESLint validation for browser JavaScript and integrate it into CI without changing the printer-delivered scripts.

New Features:

• Add host-only ESLint validation for the existing browser JavaScript in the printer web interface and documentation site.

Enhancements:

• Add a self-test that verifies the browser scripts pass linting and that undefined names are rejected.
• Keep the pinned ESLint tooling outside printer packages and document its third-party licensing and provenance.

CI:

• Run the browser JavaScript lint self-test in CI and include it in shell style checks.
• Update CI validation selection to recognize ESLint checker changes without triggering unrelated validation lanes.

Documentation:

• Document the host-only ESLint dependency and its licensing boundary.

Tests:

• Extend CI selector self-tests to cover ESLint host tooling and validation script changes.

[sourcery-ai]

Hey - I've reviewed your changes and they look great!

Sourcery assessment

Approved.

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook