An in-range update of ava is breaking the build π¨
greenkeeper opened this issue Β· comments
The devDependency ava was updated from 1.2.0
to 1.2.1
.
π¨ View failing branch.
This version is covered by your current version range and after updating it in your project the build failed.
ava is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.
Status Details
- β continuous-integration/travis-ci/push: The Travis CI build failed (Details).
Release Notes for 1.2.1
This is a bug fix release. In very large projects, the options send to worker processes would exceed limits on process argument size. We're now sending the options via the inter-process communication channel. 3078892
All changes π
Get involved βοΈ
We welcome new contributors. AVA is a friendly place to get started in open source. We have a great article on getting started contributing and a comprehensive contributing guide.
FAQ and help
There is a collection of frequently asked questions. If those donβt help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot π΄
After pinning to 1.2.0 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.
- The
devDependency
ava was updated from1.2.1
to1.3.0
.
Your tests are still failing with this version. Compare changes
Release Notes for 1.3.0
Bug fixes
- We've fixed a rather embarrasing bug with
t.throws()
andt.throwsAsync()
. If you'd set acode
expectation to a number we never actually checked that the thrown error had such a code! Thanks to @qlonik for both spotting and fixing this. 82daa5e - 1.2.0 contained a regression which meant that if you faked
clearTimeout()
, you'd break AVA. That's now been fixed. 40f331c - Snapshot files are now recognized as source files, so if you're using watch mode and you delete one, AVA won't rerun all your test files. d066f6f
New features
You can now use require()
in ava.config.js
files to load non-ES modules. 334e15b
All changes
Thanks
Thank you @itaisteinherz, @jdalton, @kagawagao, @KompKK, @SleeplessByte, @Chrisyee22 and @qlonik for helping us with this release. We couldn't have done this without you!
Get involved
We welcome new contributors. AVA is a friendly place to get started in open source. We have a great article on getting started contributing and a comprehensive contributing guide.
Commits
The new version differs by 12 commits.
b0fadb4
1.3.0
9600966
Bump dependencies
82daa5e
Assert on expected error code, even when a number
1e3b072
Document
timeout
configurationd97f11d
Improve pronunciation examples
40f331c
Fix unbound reference to clearTimeout
334e15b
Support require() in config files
5751226
Added few tests for lib/chalk.js
7d10446
Fix link to Babel recipe
565822e
Update esm package detection
2fce19f
Remove the
typings
field in package.jsond066f6f
Recognize snapshot files as source files
See the full diff
- The
devDependency
ava was updated from1.3.0
to1.3.1
.
Your tests are still failing with this version. Compare changes
Release Notes for 1.3.1
Bug fixes
- We've fixed a rather embarrasing bug with
t.throws()
andt.throwsAsync()
. If you'd set acode
expectation to a number we never actually checked that the thrown error had such a code! Thanks to @qlonik for both spotting and fixing this. 82daa5e - 1.2.0 contained a regression which meant that if you faked
clearTimeout()
, you'd break AVA. That's now been fixed. 40f331c - Snapshot files are now recognized as source files, so if you're using watch mode and you delete one, AVA won't rerun all your test files. d066f6f
New features
You can now use require()
in ava.config.js
files to load non-ES modules. 334e15b
All changes
Thanks
Thank you @itaisteinherz, @jdalton, @kagawagao, @KompKK, @SleeplessByte, @Chrisyee22 and @qlonik for helping us with this release. We couldn't have done this without you!
Get involved
We welcome new contributors. AVA is a friendly place to get started in open source. We have a great article on getting started contributing and a comprehensive contributing guide.
- The
devDependency
ava was updated from1.3.1
to1.4.0
.
Your tests are still failing with this version. Compare changes
Release Notes for 1.4.0
Focusing power-assert
AVA comes with power-assert
built-in, giving you more descriptive assertion messages. However it's been confusing to understand which assertions come with power-assert
. To address this we've added the new t.assert()
assertion. It's now the only assertion that is power-assert
enabled. The assertion passes if called with a truthy value. Consider this example:
test('enhanced assertions', t => { const a = /foo/; const b = 'bar'; const c = 'baz'; t.assert(a.test(b) || b === c); });
AVA will output:
6: const c = 'baz'; 7: t.assert(a.test(b) || b === c); 8: });
Value is not truthy:
false
a.test(b) || b === c
=> falseb === c
=> falsec
=> 'baz'b
=> 'bar'a.test(b)
=> falseb
=> 'bar'
a
=> /foo/
Our ESLint plugin has been updated to support this new assertion. Many thanks to @eemed for implementing this! 9406470
Watch mode
Watch mode now prints the available commands. Thanks @KompKK! cd256ac
Bug fixes
- Filtered tests (when using
--match
,.skip()
or.only()
) are no longer included in the list of pending tests when timeouts occur or when you interrupt a test run. Thanks @vancouverwill! 23e302a - We're now shimming all TTY methods in the worker processes, thanks to @okyantoro. c1f6fdf
Documentation updates
- We've added a note to say that, by default, AVA does not have a default test timeout. Thanks @amokmen! 99a10a1
All changes
Thanks
Thank you @eemed, @KompKK, @vancouverwill, @okyantoro and @amokmen. We couldn't have done this without you!
Get involved
We welcome new contributors. AVA is a friendly place to get started in open source. We have a great article on getting started contributing and a comprehensive contributing guide.
Commits
The new version differs by 7 commits.
20db474
1.4.0
0154a7f
Bump dependencies
9406470
Only apply power-assert to new t.assert() assertion
c1f6fdf
Shim all tty methods
23e302a
Don't report filtered tests as pending
99a10a1
Document that there is no default timeout
cd256ac
Print commands in watch mode
See the full diff
- The
devDependency
ava was updated from1.4.0
to1.4.1
.
Your tests are still failing with this version. Compare changes
Release Notes for 1.4.1
Focusing power-assert
AVA comes with power-assert
built-in, giving you more descriptive assertion messages. However it's been confusing to understand which assertions come with power-assert
. To address this we've added the new t.assert()
assertion. It's now the only assertion that is power-assert
enabled. The assertion passes if called with a truthy value. Consider this example:
test('enhanced assertions', t => { const a = /foo/; const b = 'bar'; const c = 'baz'; t.assert(a.test(b) || b === c); });
AVA will output:
6: const c = 'baz'; 7: t.assert(a.test(b) || b === c); 8: });
Value is not truthy:
false
a.test(b) || b === c
=> falseb === c
=> falsec
=> 'baz'b
=> 'bar'a.test(b)
=> falseb
=> 'bar'
a
=> /foo/
Our ESLint plugin has been updated to support this new assertion. Many thanks to @eemed for implementing this! 9406470
Watch mode
Watch mode now prints the available commands. Thanks @KompKK! cd256ac
Bug fixes
- Filtered tests (when using
--match
,.skip()
or.only()
) are no longer included in the list of pending tests when timeouts occur or when you interrupt a test run. Thanks @vancouverwill! 23e302a - We're now shimming all TTY methods in the worker processes, thanks to @okyantoro. c1f6fdf
Documentation updates
- We've added a note to say that, by default, AVA does not have a default test timeout. Thanks @amokmen! 99a10a1
All changes
Thanks
Thank you @eemed, @KompKK, @vancouverwill, @okyantoro and @amokmen. We couldn't have done this without you!
Get involved
We welcome new contributors. AVA is a friendly place to get started in open source. We have a great article on getting started contributing and a comprehensive contributing guide.