-
Notifications
You must be signed in to change notification settings - Fork 604
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
[api-extractor] Please support typescript 3.8 #1866
Comments
Are there any new features in 3.8 that could potentially break API Extractor? |
Yes, it seems that |
Yeah, if that gets emitted in the .d.ts file, it might be a new import pattern. API Extractor detects and walks each kind of import. Some 3.8 features that might break something:
From a quick glance at the 3.9 features, I didn't see anything that looked like it would impact API Extractor. |
We can start work on a PR to add support for these issues. None of them seems particularly difficult. But I should also point out:
|
That's where a tool like downlevel-dts can come in, to transform these new features into older syntax for older TypeScript versions. 😉 So you would first use API Extractor to create a |
TypeScript 3.9 introduces some new syntax also: #1914 |
Some progress on this:
|
With these changes, I think we can resolve this issue. There are still some remaining unsupported language features like #1914, but they have reasonable workarounds. |
This fix was released with API Extractor 7.9.0 |
Is this a feature or a bug?
Please describe the actual behavior.
What is the expected behavior?
The text was updated successfully, but these errors were encountered: