feat(turbo-utils): convert package to dual ESM/CommonJS build #10754
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This commit converts turbo-utils from a TypeScript-only package to a dual ESM/CommonJS package with proper build outputs, addressing compatibility requirements across different module systems. Key changes: - Package.json: Added "type": "module" and dual export configuration with separate entry points for ESM, CommonJS, and TypeScript declarations - Build system: Implemented three-stage build process (ESM, CJS, types) with corresponding TypeScript configurations - Import statements: Updated all relative imports to include .js extensions for ESM compatibility - Module handling: Fixed imports for packages like tar, fast-glob, and picocolors to work with ESM - Jest configuration: Added module name mapping to handle .js extension resolution in tests - TypeScript configs: Created separate tsconfig files for ESM (tsconfig.json), CommonJS (tsconfig.cjs.json), and type declarations (tsconfig.types.json) Build outputs: - dist/esm/: ES module build for modern environments - dist/cjs/: CommonJS build for Node.js compatibility - dist/types/: TypeScript declaration files The package now supports both import and require syntax while maintaining backward compatibility through the dual export system. update
tknickman
force-pushed
the
tomknickman/turbo-4812-convert-turboutils-to-esm
branch
from
b7de3bf to
9e5a325
Compare
turbo-orchestrator
bot
added
the
pkg: turbo-eslint
chris-olszewski
approved these changes
Aug 13, 2025
anthonyshew
added a commit
that referenced
this pull request
Aug 25, 2025
### Description Because JavaScript packaging is so finnicky, I'm thinking its a good idea to make sure our interfaces stay ecosystem compliant. PRs like #10747 and #10754 have potential to break things, so its nice to have some sanity checking. (I haven't checked yet if those PRs specifically are right, but they made me think about adding some tooling like this.) ### Testing Instructions CI
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This commit converts turbo-utils from a TypeScript-only package to a dual ESM/CommonJS package with proper build outputs, addressing compatibility requirements across different module systems.
Key changes:
Build outputs:
The package now supports both import and require syntax while maintaining backward compatibility through the dual export system.
Description
Testing Instructions