greenkeeper[bot]
commented
4 years ago - The
devDependencyava was updated from2.4.0to3.1.0.
Update to this version instead 🚀
Release Notes for 3.1.0
AVA can now load pre-compiled TypeScript files!
First, install the new @ava/typescript package:
npm install --save-dev @ava/typescriptNow let's assume your TypeScript files are in a src directory, output to a build directory. Configure AVA like so:
ava.config.js file:
export default {
typescript: {
rewritePaths: {
'src/': 'build/'
}
}
}Compile your TypeScript files and run your tests! Or, to run a specific test file, run npx ava src/test.ts.
For more examples see the @ava/typescript package.
As exciting as this is, it's still early days. We need your help improving our TypeScript support. Check out the open issues.
Other changes
Thanks to @jhechtf for fixing our TypeScript recipe after the changes in AVA 3.0 91a0086
See v3.0.0...v3.1.0 for all changes.
The devDependency ava was updated from
2.4.0to3.0.0.This version is not covered by your current version range.
If you don’t accept this pull request, your project will work just like it did before. However, you might be missing out on a bunch of new features, fixes and/or performance improvements from the dependency update.
Publisher: novemberborn License: MIT
Release Notes for 3.0.0
We're proud to introduce AVA 3!🚀
When we began AVA, JavaScript was very different. Most syntax you find familiar today was not supported by Node.js. Instead we relied on Babel to support that syntax before it made its way to Node.js itself.
These days most new stage-4 syntax is adopted quickly. It's often not necessary to transpile anything. Therefore we're removing our built-in Babel support from AVA itself.
Without Babel you'll have to resort to using
require()functions in your JavaScript files. But, you say, Node.js 13 supports ECMAScript Modules!Well, we're getting there. For a start, AVA now also looks for
.cjsfiles. And.mjsfiles are recognized too, but can't be loaded just yet. This also impactsava.config.jsfiles. If you'd like to help out delivering full.mjssupport check out the issues in the ESM support project.Removing Babel allowed us to simplify how test files are selected. Likely non-test files, inside "fixture" or "helper" directories are ignored. The same for files that are inside an underscore-prefixed directory. We've made some other breaking changes in this area so please do read the full release notes.
You can again pass glob patterns on the CLI. However these now filter the test files that AVA already selected based on the configuration. In other words you can't run files that wouldn't be run by invoking
npx ava.AVA now interrupts your tests if there's no progress for 10 seconds. Use the
timeoutconfiguration or--timeoutCLI option to change this.New features
Built-in debug mode
You can now debug individual test files using the V8 Inspector:
npx ava debug test.jsConnect to the debugger with Chrome DevTools. Or set up a debugger in VSCode.
Configurable Node.js arguments
You can now configure the arguments passed to Node.js itself when AVA starts its worker processes. Use the
nodeArgumentsconfiguration or combine with the--node-argumentsCLI option.All breaking changes
Supported Node.js versions
We now support Node.js 10, 12 and 13. The minimal versions are 10.18.0, 12.14.0 and 13.5.0 respectively.
Removing Babel
Utilize Babel with AVA by installing our
@ava/babelpackage and then enabling Babel by settingbabel: truein the AVA configuration. Having this as a separate package means it can evolve independently.The
compileEnhancementssetting has been moved into thebabelconfiguration. Consequently, thet.assert()assertion will only print its detailed information when you use Babel. And we won't be able to catch typical mistakes witht.throws()as well as we could before.The
ava/stage-4preset is now available from@ava/babel/stage-4. Our old@ava/babel-preset-transform-test-filesand@ava/babel-preset-stage-4packages are no longer maintained and not installed with AVA itself.ECMAScript Module Support
AVA now also looks for
.cjsand.mjstest files. That said,.mjsfiles cannot be loaded just yet.Also, when you add
"type": "module", AVA would really like to treat.jsfiles as ECMAScript Modules, but can't just yet.Similarly,
ava.config.cjsconfiguration files are now supported.ava.config.mjsfiles not just yet.With AVA 2, we loaded
ava.config.jsfiles using theesmpackage. To avoid confusion between the different module formats we now only supportexport defaultstatements. Noimport, no__filename. Configuration files that have dependencies should be written as a.cjsfile for now.Configuration files can only have
.cjs,.jsand.mjsextensions.The remaining work is tracked in the ESM support project.
File selection
When you use the default configuration AVA will no longer select files matching the following glob patterns:
**/__tests__/**/__helper__/**/***/__tests__/**/__helpers__/**/***/__tests__/**/__fixture__/**/***/__tests__/**/__fixtures__/**/***/test/**/helper/**/***/test/**/helpers/**/***/test/**/fixture/**/***/test/**/fixtures/**/***/tests/**/helper/**/***/tests/**/helpers/**/***/tests/**/fixture/**/***/tests/**/fixtures/**/*Additionally, when a file has a parent directory that starts with a single underscore, it can never be a test file.
test.jsfiles are only selected if they're next to thepackage.jsonfile, or inside top-levelsrcandsourcedirectories.We've removed the configuration of helpers. Previously, files selected by the
helpersglob patterns were never considered test files. Now that this configuration is no longer supported you'll need to ensure thefilespatterns exclude your helper files. If you're using Babel, you can configure the compilation of additional files .The
sourcesconfiguration has also been removed. Instead, use theignoredByWatcherconfiguration. Changes to files matched by these glob patterns will not cause the watcher to rerun tests.Negated
sourcespatterns must be used without the negation inignoredByWatcher:export default { - sources: ['!examples/**/*'] + ignoredByWatcher: ['examples/**/*'] }CLI changes
Internally we've replaced
meowbyyargs. We're not expecting things to break because of this, but you never know.Resetting the cache
The
--reset-cacheargument has been replaced by a properreset-cachecommand:npx ava reset-cacheFile selection (again!)
AVA again accepts glob patterns via the CLI:
npx ava '**/api/**/*'The way this work is that AVA first finds all test files, according to the configuration, and then filters to select just the files that also match the glob patterns passed via the CLI.
You can still pass paths to specific files:
npx ava src/api/test/my-api-test.jsHowever unlike with AVA 2, you can no longer specify test files that aren't already selected by AVA's configuration.
t.throws()andt.throwsAsync()assertionsThe second argument passed to these assertions must now be an
expectationobject. You can no longer pass the expected constructor, error message or regular expression.Other breaking changes
esmversions has been removed.NODE_PATHenvironment variable is no longer rewritten to ensure values are absolute paths.Other changes
subscribefunction is assumed to be an observable. AVA's type definition has been updated accordingly.All changes
v2.4.0...v3.0.0
Thanks
Thank you @tymfear, @HeathNaylor, @grnch, @alexdrans, @MoppetX, @jimmywarting, @micaelmbagira, @aptester, @theashraf, @sramam and @maximelkin. We couldn't have done this without you!
Commits
The new version differs by 86 commits.
b4cfc8d3.0.0776788fShip v3 🎉0d11ff7More issue template tweaks9983976Update various contributing documents and GitHub configuration5a33572Fix fail-fast interrupt test61e0d05Fix VSCode debugging instructions630aac3Fix remaining AVA link5c8bcecFix AVA link in snapshot reports7b20f6cAllow Node arguments to be configuredad272463.0.0-beta.2ae948d8Lowercase CLI argument description asidesac8c852Update dependencies2bd890fDisable timeouts in debug mode15d73caMake console & process globals available to ava.config.js filesefa8635Fix patterns and unpin picomatchThere are 86 commits in total.
See the full diff
FAQ and help
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html). If those don’t help, you can always [ask the humans behind Greenkeeper](https://github.com/greenkeeperio/greenkeeper/issues/new).Your Greenkeeper bot :palm_tree: