Support repo-root-relative import paths #319
Merged
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.
This adds
resolve.alias
to the webpack config, andcompilerOptions.baseUrl
+compilerOptions.paths
to tsconfig,allowing for JS/TS imports relative to the repository root (as long as they live under
src/
).(The second commit just updates most imports, I skipped the
./
ones and only changed the ones with../
, can be trivially regenerated.)Cc @newswangerd , @ZitaNemeckova WDYT? :)
Does it make sense to go with
src
as the alias? It fits the path so it seems like a reasonable default,except there is a
src
npm package (we don't depend on it, and it's related to redis, so, unlikely in frontend JS), so we may want to consider something a bit more exotic like^/src
or@/src
?