-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add js extension to mdx/types import #2211
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
Codecov ReportBase: 100.00% // Head: 100.00% // No change to project coverage 👍
Additional details and impacted files@@ Coverage Diff @@
## main #2211 +/- ##
=========================================
Coverage 100.00% 100.00%
=========================================
Files 22 22
Lines 2064 2064
=========================================
Hits 2064 2064
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report at Codecov. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks! Nice catch!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, thanks!
Would it also make sense to set the module type in the root configuration, so this is tested going forward?
Lines 2 to 6 in 600b12a
"compilerOptions": { | |
"target": "ES2020", | |
"lib": ["ES2020"], | |
"module": "ES2020", | |
"moduleResolution": "node", |
Adding on @ChristianMurphy’s comment, the correct configuration would be to replace the I also wouldn’t mind removing the redundant |
I agree that Other refactoring of |
... yeah, thought that might happen. Main reason I spot fixed the one piece breaking external consumers. |
At least 15 of the errors are in the |
... okay, so that wasn't some weird local issue... thought I just didn't know how to use workspaces |
The |
I think I'll leave this here - don't have the time to spend a ton of time troubleshooting in an unfamiliar repo I don't use ;) |
The errors are coming out of That said, with |
This PR is coming out of a question on the TypeScript Discord - I don't actually use I agree - the Node16 changes would be nice, but until ESM works properly for those dependencies... |
Yes, but this shouldn’t block this PR. Even if this doesn’t test it, it does fix the issue. An alternative solution could be to add |
What is blocking? I don’t see CI breaking? |
Potentially the fact that we can't use and therefor can't test using Regardless, it's still worth considering the alternative. I currently don't have a strong opinion about it. |
Yep, exactly |
Oh wait, I missed that, I thought it was added here. |
Unfortunately doing that would result in two modules which currently have intellisense being stuck with https://github.com/mdx-js/mdx/actions/runs/3823843079/jobs/6505439634#step:5:25 |
Internal types is fine, we have tests. They don’t reach users of this project. You should be able to define
|
We could also use |
I merged Rich-Harris/estree-walker#31 and released |
Nice, I don’t think so! Thanks Rich! (while you’re here, there was another bug with export maps in periscopic/estree-walker/is-reference, it’s now fixed in Next.js/SWC, but might pop up in other compilers: #2168 (reply in thread)). TLDR: Node recommends always adding a |
Thanks @Rich-Harris! Much appreciated! Rich-Harris/is-reference#14 and one incoming for |
Done! :) |
Because
@mdx-js/mdx
's package.json includes"type": "module"
, imports within it which reference a file must include file extensions, including type only imports. This breaks downstream TypeScript users who have"module": "Node16"
in theirtsconfig.json
file.Yes, the
.js
looks odd since we're importing a declaration file from@types/mdx
here, but it is correct, since in a TS-native setup, it would be describing a.js
file alongside the declaration file.cc: @Gaurishh