-
Notifications
You must be signed in to change notification settings - Fork 16
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
Perform compilation #3
Comments
How does this work with various For instance, I usually use two |
@szmarczak is working on an implementation in #12. Right now that assumes a single I'm inclined to ship that, and then think about supporting your use case. Though in the meanwhile ideas are most welcome. |
Come to think of it, we can just invoke |
Couldn't this be handled by |
Sure, though if I understand correctly that strips types, and there are some constructs like |
It should be possible to compile the TypeScript project before tests are run.
We should be able to control TypeScript programmatically. There is a feature to cache some of the compilation work, for faster subsequent compilation runs. We should use this.
As alluded to in #2 we should probably only support configuration files in the project directory itself (next to
package.json
files).I'm not sure where to write the output files. Perhaps just follow the TypeScript configuration. With #2 done that makes it easiest to subsequently load the test files.
I'm not sure how to handle compilation errors. We could just write the files and run the tests. We could also explore an integration with AVA to surface errors better.
This should work automatically with AVA's watch mode, since AVA invokes compilation before every test run.
The text was updated successfully, but these errors were encountered: