-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Transpile source files in the main process #577
Comments
Am I confused or we already do this via #390? |
#390 transpiles tests files. This is suggesting infrastructure to transpile source files in the main process as well. |
Yeah, but we don't transpile source files at all now. So we may start with that. |
Yes, that's the point of this issue. We'd have to use the approach from |
Or use Either way this won't do much good for dynamic I think a first step should be supporting transpilation of helper files (files in the test directory prefixed with |
For "non-Babel" transpilers (typescript, etc), we would have to create a plugin ecosystem. We would still need to finish up with Babel for powerAssert support. Conceivably, users may want to chain custom transforms. See |
This will be tackled through RFC 001. See the project here: https://github.com/avajs/ava/projects/1. |
@novemberborn link is dead so I'm not sure where to look |
Yea, I pulled the RFC recently. #1908 is probably the best issue to track for now. |
To improve startup time (#78) we could provide a framework where source files are optimistically transpiled and cached in the main process. No require hooks would be required in the test files avoiding the Babel startup penalty. Thanks @tomazzaman for the suggestion.
--require
hooks won't do, we should support plugins and wrap them like howcaching-precompiler
wraps Babel--source
patterns so would require useful error messaging somehowThe text was updated successfully, but these errors were encountered: