-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
tsconfig paths not supported? #807
Comments
We don't support this yet, but is definitely aligned with one of our goals. So it'd be great to have this. We already have alias support in the sandbox compiler, so the one thing we need to do is have a way to be able to convert a path using the getAliasedPath = (path: string) => {
const { parsed } = this.configurations.tsconfig;
// Now use parsed.paths to convert path
} I expect that a similar function is already somewhere out there because it's used in the local |
I also have the same problem with custom
I hope you can fix soon! |
+1 Example project github/Angular-RU/angular-ngrx-starter |
Anything new on this? |
This issue has automatically been marked stale because there has been no activity in a while. Please leave a comment if the issue has not been resolved, or if it is not stale for any other reason. After 2 weeks, this issue will automatically be closed, unless a comment is made or the stale label is removed. |
This issue has been automatically closed because there wasn't any activity after the previous notice or the stale label wasn't removed. |
Anything new on this? ;) |
Yep I thought it did work so I asked again. Would defo love this. Otherwise all the time goes in changing the imports which is boring work 😂 |
I just had this issue myself too |
This issue has automatically been marked stale because there has been no activity in a while. Please leave a comment if the issue has not been resolved, or if it is not stale for any other reason. After 2 weeks, this issue will automatically be closed, unless a comment is made or the stale label is removed. |
This issue has been automatically closed because there wasn't any activity after the previous notice or the stale label wasn't removed. |
This is gonna be fixed once we rewrite the resolver, which is planned to happen soonish |
I am hoping to use CodeSandbox for an upcoming presentation to have an in-browser editor experience. I tried importing my (working) local TypeScript create-react-app repo: https://github.com/kamranayub/sample-react-ts-app (sandbox: https://codesandbox.io/s/n1kn3z5l9m)
When I import it into CodeSandbox, it doesn't like the tsconfig
paths
options. This is a useful feature for a lot of reasons (short imports, etc.). Any idea if that will be supported? It's supported in a vanilla CRA TS project.The text was updated successfully, but these errors were encountered: