Skip to content

DEV.md

Latest commit

 

History

History
138 lines (108 loc) · 7.08 KB

DEV.md

File metadata and controls

138 lines (108 loc) · 7.08 KB
Raw

Build Tools Development Guide

Dependencies

This document tracks dependencies that are specially managed for technical reasons.

Dependencies Blocked from Major Version Upgrades

The following dependencies are pinned to older major versions because newer versions may be incompatible with the current CommonJS-based codebase. Most of these packages have migrated to ESM-only in their latest versions and compatibility with "module-sync" has not been investigated. Migrating to ESM is recommended resolution.

ESM-Only Dependencies (Cannot upgrade until build-tools migrates to ESM)

  1. execa - Pinned to ^5.x

    • Latest: ^9.x
    • Highest compatible: ^5.x (v6+ is ESM-only)
    • Issue: Version 6+ is ESM-only and removed default export
    • Error: Module has no default export and Module has no exported member 'command'
    • Used in: build-cli, build-infrastructure

  2. globby - Pinned to ^11.x

    • Latest: ^16.x
    • Highest compatible: ^11.x (v12+ is ESM-only)
    • Issue: Version 12+ is ESM-only and removed default export
    • Error: Module has no default export
    • Used in: build-cli, build-tools

  3. glob - Pinned to ^7.x

    • Latest: ^11.x
    • Issue: Version 8+ rewrote the API and is ESM-only
    • Error: Cannot find name 'IOptions' and Property 'default' does not exist
    • Used in: build-tools

  4. multimatch - Pinned to ^5.x

    • Latest: ^7.x
    • Issue: Version 6+ is ESM-only
    • Error: The current file is a CommonJS module... however, the referenced file is an ECMAScript module
    • Used in: build-tools

  5. picospinner - Pinned to ^2.x

    • Latest: ^3.x
    • Issue: Version 3 is ESM-only
    • Error: however, the referenced file is an ECMAScript module and cannot be imported with 'require'
    • Used in: build-tools

  6. read-pkg-up - Pinned to ^7.x

    • Latest: ^11.x
    • Highest compatible: ^7.x (v8+ has transitive dependency issues with type-fest)
    • Issue: Version 8+ is ESM-only, also pulls in incompatible type-fest versions
    • Error: The requested module 'read-pkg-up' does not provide an export named 'default'
    • Used in: build-cli

  7. replace-in-file - Pinned to ^7.x

    • Latest: ^8.x
    • Issue: Version 8 is ESM-only
    • Error: The requested module 'replace-in-file' does not provide an export named 'default'
    • Used in: build-cli

  8. date-fns - Upgraded to ^3.x ✅

    • Latest: ^4.x
    • Highest compatible: ^3.x (v4+ is ESM-only)
    • Issue: Version 4+ is ESM-only
    • Used in: build-cli, build-tools
    • Note: Successfully upgraded to v3 for newer features while maintaining CommonJS compatibility

  9. @manypkg/get-packages - Pinned to ^2.x

    • Latest: ^3.x
    • Issue: Version 3 is ESM-only
    • Error: however, the referenced file is an ECMAScript module and cannot be imported with 'require'
    • Used in: build-infrastructure, build-tools

  10. detect-indent - Pinned to ^6.x

    • Latest: ^7.x
    • Issue: Version 7 is ESM-only
    • Error: however, the referenced file is an ECMAScript module and cannot be imported with 'require'
    • Used in: build-infrastructure, build-tools

  11. type-fest - Pinned to ^2.x

    • Latest: ^4.x
    • Highest compatible: ^2.x (v3+ is ESM-only)
    • Issue: Version 3+ is ESM-only
    • Error: The current file is a CommonJS module... however, the referenced file is an ECMAScript module and cannot be imported with 'require'
    • Used in: build-cli, build-infrastructure, build-tools
    • Note: v5+ also deprecated the Opaque type in favor of Tagged

Type Compatibility Issues

  1. @types/minimatch - Pinned to ~5.1.2 for @types/glob dependency (via pnpm override)

    • Latest: ^6.x
    • Issue: @types/glob@7.x uses minimatch.IOptions and minimatch.IMinimatch interfaces that were removed in @types/minimatch@6.x
    • Dependency chain: sort-package-json@1.57.0 → globby@10.0.0 → @types/glob@7.2.0 → @types/minimatch@6.0.0
    • Error: Namespace has no exported member 'IOptions' and has no exported member named 'IMinimatch'
    • Solution: pnpm override @types/glob>@types/minimatch@~5.1.2 only affects the @types/glob dependency chain
    • Note: Targeted override allows rest of codebase to use modern minimatch/types while maintaining compatibility for glob types

  2. azure-devops-node-api - Pinned to ^11.x

    • Latest: ^15.x
    • Issue: Version 15 has incompatible type definitions and breaks bundle size analysis tools
    • Error: Types have separate declarations of a private property and Type is missing properties
    • Used in: build-cli
    • Note: Pinned at ^11.2.0 to maintain compatibility; upgrade blocked until type issues resolved

API/Structure Breaking Changes

  1. eslint - Upgraded to ^9.x ✅

    • Latest: ^9.x
    • Previously pinned to ~8.57.0 due to flat config migration required
    • Note: Successfully migrated to ESLint 9 flat config system

  2. eslint-config-oclif - Removed ✅

    • Previously used eslint-config-oclif@^5.x and eslint-config-oclif-typescript@^3.x
    • Note: Permanently removed. The oclif ESLint configs don't provide oclif-specific rules—they're general Node.js/TypeScript style configs (XO-based) that conflict with @fluidframework/eslint-config-fluid. The v6 config redefines the @typescript-eslint plugin causing ESLint errors.
    • Oclif-specific overrides (default exports, etc.) are handled in per-package eslint.config.mts files.

  3. npm-check-updates - Pinned to ^16.x

    • Latest: ^19.x
    • Highest compatible: ^16.x (v17+ changed internal module structure)
    • Issue: Version 17+ changed internal module structure and removed exported types
    • Error: Cannot find module 'npm-check-updates/build/src/types/IndexType.js' and type errors
    • Used in: build-cli

build-cli sets skipLibCheck for vscode-jsonrpc

vscode-jsonrpc (transitive dep via @github/copilot-sdk) uses IterableIterator in its LinkedMap types, which is incompatible with TS 5.6+'s MapIterator. See microsoft/vscode-languageserver-node#1590 tracking the issue. Fix will be in vscode-jsonrpc 9.0.0 which has not been released as of 2026-05-10.

Linked Dependency: ESLint Config

The @fluidframework/eslint-config-fluid package is referenced using link:../common/build/eslint-config-fluid because the package exists in the root FluidFramework workspace but build-tools is a separate pnpm workspace. When using link: protocol, transitive dependencies are not automatically installed.

To work around this limitation, the root package.json includes a postinstall script that runs pnpm install inside the linked eslint-config-fluid directory, ensuring its dependencies are available:

"postinstall": "pnpm install --dir ../common/build/eslint-config-fluid"

This approach keeps the dependency list clean while ensuring all ESLint plugins and parsers required by the shared config are installed. Once eslint-config-fluid is published to npm and consumed via a normal version specifier instead of link:, this postinstall hook can be removed.