NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
npm · #4946 most downloaded on npm
Spectacular Test Runner for JavaScript.
Last release 2 years ago
no release in 18 months
Release timing varies
gaps range from 2 weeks to 10 months
No release notes found
nothing matched a version
Nothing withdrawn
no release was ever pulled
14 years old
213 releases · first in 2013
Nothing published for this version
client: Fix stringify serializing objects
socket.io: Force 0.9.16 which works with Chrome
One column per quarter.
watcher: Close file watchers on exit event
server: complete acknowledgment
Nothing published for this version
Nothing published for this version
browser: don't add already active socket again on reconnect
cli: override if an arg is defined multiple times (31eb2c2c, closes #1192)
add emscripten memory image as binary suffix
<a name="v0.12.24"></a>
Nothing published for this version
Nothing published for this version
Wrap url.parse to always return an object for query property (72452e9f, closes #1182)
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
file_list: Incorrect response after remove and add file
preprocessor: treat *.tgz, *.tbz2, *.txz & *.xz as binary
<a name="0.12.21"></a>
#### Bug Fixes * web-server: cache static files
config: #1113 Watching is not working properly on linux (c91ffbc0, closes #1113)
proxy: More useful proxyError log message
watcher: handle paths on Windows
logging: Summarize SKIPPED tests in debug.html. Before: hundreds of SKIPPING lines in con (a01100f5, closes #1111)
<a name="v0.12.16"></a>
launcher: cancel kill timeout when process exits cleanly (bd662744, closes #946)
Nothing published for this version
server: don't wait for socket.io store expiration timeout
<a name="v0.12.14"></a>
debug.html: Added whitespace after 'SKIPPED'
preprocessor: serve NaCl binaries
server: properly close flash transport
preprocessor: remove ts from binary extensions
Nothing published for this version
server: clear web server close timeout on clean close
web-server: strip scheme, host and port
web-server: inline the config, when serving debug.html
don't crash/terminate upon errors within chokidar
<a name="v0.12.5"></a>
Nothing published for this version
reporters: format fix for console log (d2d1377d, closes #934)
init: Fix type in init text (e34465b0, closes #954)
web-server: implement a timeout on webServer.close() (fe3dca78, closes #952)
<a name="v0.12.1"></a>
preprocessor: Adding the dat file extension as a recognised binary.
dat file extension as a recognised binary. (be923571)<a name="v0.12.0"></a>
<a name="v0.11.14"></a>
Nothing published for this version
preprocessor: allow preprocessor to cancel test run (4d669bf3, closes #550)
launcher: compatibility with old launchers
client: show error if an adapter is removed
Nothing published for this version
Nothing published for this version
events: resolve async events without any listener
Nothing published for this version
completion: add missin --log-level for karma init
karma init can help with this.Removed plugins that need to be installed explicitly are:
<a name="v0.11.9"></a>
browser: add browserNoActivity configuration
reporter: remove SHAs from stack traces
keep all sockets in the case an old socket will survive
<a name="v0.11.6"></a>
apply CLI logger options as soon as we can
browserDisconnectTolerance config option (19590e1f)autoWatch is true by default. If you rely on the default value being false, please set it in karma.conf.js explicitly to false.
(8454898c)<a name="v0.11.5"></a>
do not execute already executing browsers
#### Bug Fixes * browser: reply "start" event
config: not append empty module if no custom launcher/rep/prep
karma binary in favor of karma-cli (c7d46270)karma module does not export karma binary anymore. The recommended way is to have local modules (karma and all the plugins that your project needs) stored in your package.json. You can run that particular Karma by ./node_modules/karma/bin/karma. Or you can have karma-cli installed globally on your system, which enables you to use the karma command.The global karma command (installed by karma-cli) does look for local version of Karma (including parent directories) first and fall backs to a global one.
The bin/karma binary does not look for any other instances of Karma and just runs the one that it belongs to.
(c7d46270)
<a name="v0.11.2"></a>
proxy: handle proxied socket.io websocket transport upgrade
Your coding agent can read these notes before it upgrades. Set up the MCP server →