test(linter/plugins): conformance tester set default export on parser modules#18553
Conversation
How to use the Graphite Merge QueueAdd either label to this PR to merge it via the merge queue:
You must have a Graphite account in order to use the merge queue. Sign up using this link. An organization admin has enabled the Graphite Merge Queue in this repository. Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue. This stack of pull requests is managed by Graphite. Learn more about stacking. |
There was a problem hiding this comment.
Pull request overview
This PR adds a workaround for a bug in tsx where ESM code importing CommonJS modules (specifically parser modules like @typescript-eslint/parser) can malfunction. The fix adds a default property to parser modules to work around this issue.
Changes:
- Added a default export property to parser modules loaded by the conformance tester
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
ca2d841 to
e07c667
Compare
94e1803 to
da1199c
Compare
Merge activity
|
… modules (#18553) Conformance tester is run with `tsx` to support test files written in TS. `tsx` seems to sometimes malfunction where ESM code `import`s CommonJS modules (like parsers e.g. `@typescript-eslint/parser`. Add a `default` property to parser modules, to solve this problem.
da1199c to
886ac2f
Compare
e07c667 to
da76bc5
Compare

Conformance tester is run with
tsxto support test files written in TS.tsxseems to sometimes malfunction where ESM codeimports CommonJS modules (like parsers e.g.@typescript-eslint/parser. Add adefaultproperty to parser modules, to solve this problem.