feat: expose tsconfigPath to AppConfig #6301
Open
+9
−1
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I can see this likely being used by others, no reason not to expose it AFAIK.
Our current use-case is that there are some properties in the
tsconfig.json
that I don't want to be available to the remix build. We have a mono-repo and we use thepaths
property intsconfig
to provide typings across all packages but at build time we expect remix to resolve the module in it's compiled form which is available through the node module resolution (symlinked inside node_modules as all other packages). This is caused by esbuild resolving paths through the tsconfig.Here's a bit of code to demonstrate why I'd like this change:
Main tsconfig is used for IDE type resolution
Whilst tsconfig.build is used strictly for building the application. This config ensures that the bundler resolves
@internal-pkg/*
fromnode_modules
or whatever the module resolution type is.