Fix: Add missing .js extension to builder ESM import#16
Draft
Copilot wants to merge 2 commits into
Draft
Conversation
Copilot
AI
changed the title
[WIP] Fix missing .js extension for ESM import in builder
Fix: Add missing .js extension to builder ESM import
Jun 3, 2026
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
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.
The builder module fails at runtime in native ESM environments (Node.js, Deno) due to a missing
.jsextension in a relative import. This causesError [ERR_MODULE_NOT_FOUND]when attempting to import the builder API.Changes
Builder module imports
.jsextension to the import statement insrc/builder/schema-builder.tsThe import was updated from:
To:
This aligns with ESM requirements for native module resolution and matches the pattern already used throughout the parser module.