Support AVA 1.x or deprecate ava-ts #24
Comments
I see that AVA 1.0 seem to have support for running ts files directly. Does this deprecate ava-ts entirely? |
Very good question indeed. Not sure yet: Might be convenient to have ava-ts as just a tiny wrapper around the ava cli, setting the right settings to match the *.ts files. Or it might be too little added value and should be deprecated... Will give it some thought. Feel free to discuss here 👇 |
Ok, I finally used AVA v1.0 with TypeScript a few times and came to a conclusion: It works quite well, but some details were annoying. I had to copy and paste a few config options every time (require Conclusion: There will be AVA-TS v1.0 and I basically implemented it already.
It's not a fork of AVA anymore, but just a small, a little bit hacky wrapper around the AVA CLI. Give it a try if you have some time and please share your feedback! 🚀 |
Memo to myself: Should support the ts-node options as CLI options. |
Just a note if anyone else has an issue, version 1.0.0-rc fixed an issue I was having with |
This maintenance upgrade addresses the following security advisories: - CVE-2019-10742 - CVE-2019-10744 - CVE-2019-10744 - WS-2018-0236 Fortunately none of the necessary changes are very dramatic and none require code changes. However, the minimum NodeJS version has been raised to 8. avajs/ava@1.0.0+ ostensibly supports TypeScript natively [1], so ava-ts is potentially obsolete. ava-ts has not made a public stance yet and I did not spend time investigating migrating. - andywer/ava-ts@v0.24.2...v0.25.2 - axios/axios@v0.18.0...v0.19.0 - typicode/json-server@v0.12.1...v0.15.0 [1] andywer/ava-ts#24
The latest version of AVA is currently 1.1.0, and ava-ts only supports 0.* (which currently resolves to AVA 0.25.0)
The text was updated successfully, but these errors were encountered: