typescript
typescript copied to clipboard
avajs
Test TypeScript projects using AVA.
It'd be useful if we could use TypeScript to define our Ava configurations via an `ava.config.ts` file. Ideally, we'd be able to structure them like so: ```ts // Importable `Configuration`...
Please provide details about: * What you're trying to do Ava watch mode with this package. ```json { "ava": { "files": [ "src/**/*.test.ts" ], "typescript": { "rewritePaths": { "src/": "build/"...
I came across https://github.com/avajs/ava/issues/1109 which lists several criticisms of ts-node and predates some recent improvements. For example, ts-node has since implemented an ESM loader which I believe can handle #5....
This is more like an anti-bug than an actual bug. But it seems like this project works even when I provide a nonsensical rewritePaths entry, for example: ```json "typescript": {...
See https://github.com/avajs/ava/issues/2473 for context. We need to parse the test file, ideally using `typescript`. And then provide the call locations back to AVA. This will require some changes in AVA...
This provider doesn't translate error stack traces using source maps. We should document how you can set that up yourself, by installing `source-map-support` and adding `source-map-support/register` to AVA's `require` configuration.
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....
We should document that this also works with AVA's require option, as long as you specify the `.ts` extension.
The JSX preserve mode (https://www.typescriptlang.org/docs/handbook/jsx.html) causes compiled `.tsx` files to be written with a `.jsx` extension. This is not currently supported. We'll have to resolve the TypeScript configuration to determine...