feat: attach .js extension to all relative/absolute file imports/exports#8034
feat: attach .js extension to all relative/absolute file imports/exports#8034
Conversation
🦋 Changeset detectedLatest commit: 8eebab3 The changes in this PR will be included in the next version bump. This PR includes changesets to release 40 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
|
The latest changes of this PR are available as alpha in npm (based on the declared |
|
@n1ru4l Is the extension needed here also? |
|
hmm I think extensions should also be added to config inputs, right? graphql-code-generator/dev-test/codegen.yml Line 215 in 9a5f31c otherwise files being generated without it |
|
this should be rethinked: extension are removed, for example graphql-code-generator/dev-test/codegen.yml Line 360 in 9a5f31c resolves into |
dotansimha
left a comment
There was a problem hiding this comment.
@n1ru4l do we have any concerns about breaking changes? older TS version or anything like that? (in the generated files, i mean)
|
default needs extension |
|
also, in this file, look for assurances of |
I think this is fine, as it is configured through a user-provided configuration. ( I added a note to the changeset for instructing people to adjust their mappers etc. |
.js worked in all previous TS version afaik |
|
Apparently, this broke Next.js... #8065 |
Closes #8022
Closes #8034