Comments (2)
Just looked into microsoft/TypeScript#58042 a bit. It looks like as far as esbuild is concerned, this only affects baseUrl
and paths
. If the string starts with "${configDir}"
(only at the start, not anywhere else), I need to replace that prefix with "./"
and then resolve that into an absolute path relative to the directory containing the root-level tsconfig.json
file. In particular, it looks like you don't need to use a slash after ${configDir}
since "${configDir}/lib"
becomes ".//lib"
after this substitution. Hopefully I'm understanding everything correctly.
from esbuild.
Yeah if there's something that should be done differently in your implementation I don't know what it is. Thanks 👍
from esbuild.
Related Issues (20)
- DirectAdmin cannot backup application due to hardlink in esbuild HOT 2
- Import attributes should be enabled for `node18` and >= `node20` targets HOT 2
- Code splitting is creating many small unnecessary chunks HOT 1
- Class missing metadata field in certain cases
- esbuild tried to read "../../.." , in vite , using npm run dev HOT 1
- Destructuring bug in Safari when renamed parameter property is identical to the function name
- Class binding references in static field initializers should be resolved to the decorated class HOT 3
- `browsers` field not taken into account when using `exports`. HOT 1
- esbuild doesn't respect noImplicitUseStrict option in tsconfig.json HOT 1
- On-resolve result suffix property also requires path property?
- Substituting multi-use constants results in a larger bundle HOT 5
- Importing with a type attribute of "css" is not supported HOT 7
- Feature Request: Add polyfill for CSS `light-dark()`
- panic: Internal error: failed to parse runtime with `--supported:object-accessors=false` HOT 1
- [Bug?] Esbuild slow performance due to discarding dir cache when the plugin calls the built-in resolver
- Getting weird esbuild version when using 0.20.2 HOT 3
- ESbuild loader Plugin: Dynamic Imports do not contain "with" information HOT 3
- Dynamic imports with string literal templates are not resolved when using tsconfig paths
- Could not resolve "path", could not resolve "os" HOT 3
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from esbuild.