-
Notifications
You must be signed in to change notification settings - Fork 97
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
Typescript metro plugin doesn't build project references #3343
Comments
Hi, this sounds like a feature request rather than something not working correctly. If you're on a recent version of Metro and you're using package exports, have you tried adding a |
@tido64 I am not sure that this issue is connected with packages export, as I understand the error is coming from typescript type checker itself. As I understand the plugin is supposed to allow you to do type checking by metro, if you have project references you have to run tsc manually what makes usages of |
It isn't. I'm saying there is a solution for your scenario with package exports that avoids building altogether. I am not opposed to adding proper support for project references, but that will be an option that we have to add. I'm not sure of the scope of this work and will have to ask someone who knows these bits better than I do. Out of curiousity, what is the error you're seeing? |
@tido64 I have this error in clean repo
When I run |
What happened?
When you use project references TypeScript force you to build your source code. When you have clean codebase there are no builded files and
@rnx-kit/metro-plugin-typescript
throws error about that.I think there should an option like in fork-ts-checker-webpack-plugin -
{ typescript: { build: true, mode: 'write-dts' } }
Ideally, just running metro should be enough, without separate running of
tsc
complilerAffected Package
@rnx-kit/metro-plugin-typescript
Version
0.4.5
Which platforms are you seeing this issue on?
System Information
Steps to Reproduce
@rnx-kit/metro-plugin-typescript
to your metro configCode of Conduct
The text was updated successfully, but these errors were encountered: