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
Automagically determine rewrite paths #2
Labels
Comments
novemberborn
added
enhancement
New feature or request
help wanted
Extra attention is needed
labels
Jan 26, 2020
Closed
While it does automatically crawl the entire tree to find a However, TypeScript configuration does support "extending" another config file. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It should be possible to resolve the TypeScript configuration (including extended configurations) to determine what source directories are output where. That way, users won't have to configure the rewrite paths.
I'm not sure if TypeScript supports multiple configuration files within a project. Babel does, but AVA's Babel support ignores such configuration files. It'll be simplest to do the same here.
This means we'll assume the nearest TypeScript configuration file is in the project directory itself.
The text was updated successfully, but these errors were encountered: