Add .js extensions to runner imports to produce valid esm#46
Merged
andrewMacmurray merged 1 commit intomainfrom Jul 15, 2025
Merged
Add .js extensions to runner imports to produce valid esm#46andrewMacmurray merged 1 commit intomainfrom
andrewMacmurray merged 1 commit intomainfrom
Conversation
andrewMacmurray
added a commit
that referenced
this pull request
Jul 15, 2025
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
1 participant
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.
Closes #40
When using the concurrent task runner without transpiling in node, the generated esm JS was invalid, e.g.:
needs to be
This PR manually adds the
.jsextensions in, this could be done via a build tool but it feels like overkill given how stable the runner is right now.