build(server): upgrade eslint config and add compatibility workarounds #25892
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
This PR upgrades the ESLint configuration across all server/routerlicious packages and implements workarounds for compatibility issues.
ESLint Configuration Upgrade
@fluidframework/eslint-config-fluidfrom^6.1.0to^8.1.0across all packagesimport-xprefix (e.g.,import/no-nodejs-modules→import-x/no-nodejs-modules)import/namespacetoimport-x/namespacein inline eslint-disable commentsBuild Configuration Workarounds
^server/routerlicious/packages/.*/package.jsonto fluid-build for bothtsc-multiandfluid-build-tasks-tsctasksType Compatibility
@types/node@>=22override to force Node.js v20 types, working around incompatibilities with packages using different type versionsCode Quality Improvements
@typescript-eslint/return-awaitsuppression for false positive in localOrdererSetup.tsAll changes maintain backward compatibility while modernizing the linting infrastructure.