Skip to content
This repository has been archived by the owner on Jul 21, 2020. It is now read-only.

Support AVA 1.x or deprecate ava-ts #24

Open
motin opened this issue Jan 19, 2019 · 5 comments
Open

Support AVA 1.x or deprecate ava-ts #24

motin opened this issue Jan 19, 2019 · 5 comments
Labels

Comments

@motin
Copy link

motin commented Jan 19, 2019

The latest version of AVA is currently 1.1.0, and ava-ts only supports 0.* (which currently resolves to AVA 0.25.0)

@motin
Copy link
Author

motin commented Jan 19, 2019

I see that AVA 1.0 seem to have support for running ts files directly. Does this deprecate ava-ts entirely?

@motin motin changed the title Support AVA 1.x Support AVA 1.x or deprecate ava-ts Jan 19, 2019
@andywer
Copy link
Owner

andywer commented Jan 19, 2019

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 👇

@andywer
Copy link
Owner

andywer commented Feb 23, 2019

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 ts-node, *.ts extensions, disable compile enhancements) and the default file matching patterns only match *.js test files, of course.

Conclusion: There will be AVA-TS v1.0 and I basically implemented it already.
Have a look at the v1.0 branch. You can already try it by installing it as:

npm install --save-dev ava-ts@next

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! 🚀

@andywer
Copy link
Owner

andywer commented Feb 26, 2019

Memo to myself: Should support the ts-node options as CLI options.

@ckbrewer33
Copy link

Just a note if anyone else has an issue, version 1.0.0-rc fixed an issue I was having with throwsAsync not existing; since I'm guessing the version of ava in the latest official release wasn't supported yet.

commonquail added a commit to commonquail/completionist that referenced this issue Jul 17, 2019
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
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

3 participants