Preserve .js extension when importDocumentNodeExternallyFrom and emitLegacyCommonJSImports is false #8895
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.
🚨 IMPORTANT: Please do not create a Pull Request without creating an issue first.
Any change needs to be discussed before proceeding. Failure to do so may result in the rejection of the pull request.
Description
These changes skip removing
.js
extensions from import paths when theemitLegacyCommonJSImports
option is set tofalse
Related # (issue)
#8894
Type of change
Please delete options that are not relevant.
How Has This Been Tested?
Added unit test to simulate the input parameters and configuration options. Verify with
yarn test packages/plugins/other/visitor-plugin-common/tests/client-side-base-visitor.spec.ts
Test Environment:
OS: macOS
NodeJS: 18.13.0
graphql version: 16.6.0
@graphql-codegen/visitor-plugin-common version(s): 2.13.1
Checklist: