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
How to use path aliases #334
Comments
using "paths" in |
@egoist I get {
"compilerOptions": {
"paths": {
"@app/*": ["./src/*"]
}
}
} |
@hampuskraft maybe you forgot |
That gives the same result, since |
@hampuskraft yeah, a repro would be nice then, since I can't reproduce it locally |
@egoist Here's a repro, thanks! https://github.com/hampuskraft/tsup-paths |
@hampuskraft I tried |
I guess this is a runtime error? seems to be related to #409 |
I'll close this and further updates will be added to #409. |
Hi, it seems that path alias is not working for |
@bhvngt does |
I have been using some of node's built-in packages and my project is following
|
@bhvngt a repo would be helpful |
@egoist I have created a repo tsup-node-esm which replicates my issue. I have realised that if I move I do see that the code gets inlined during transpilation. Is there anyway to avoid that? |
I would like to use absolute path aliases but couldn't figure out how to set it up with this project
I would like a path like this:
import { formatNumber } from "../../../utils"
be like this:
import { formatNumber } from "@utils"
The text was updated successfully, but these errors were encountered: