default
using bracket notation by @LeshaKoss, since using dot notation to access the property default
causes an error in Internet Explorer 8.refs: Babel and CommonJS modules
power-assert:
power-assert-formatter:
espowerify:
Now power-assert 0.9.0 supports multi-stage sourcemaps.
power-assert:
empower:
power-assert-formatter:
renderers
option (265d3539)espower:
espower-source:
espower-loader:
grunt-espower:
gulp-espower:
espowerify:
espower-coffee:
No change is required if you are using default configuration.
If you are customizing renderers by options.renderers
, you may have to migrate.
To migrate, change your code from the following:
[
'file',
'assertion',
'diagram',
'binary-expression'
]
To:
[
'./built-in/file',
'./built-in/assertion',
'./built-in/diagram',
'./built-in/binary-expression'
]
power-assert:
empower:
escallmatch
module to describe target patterns (533a21a0)targetMethods
does not required any more (8ffcc49f)saveContextOnFail
option to saveContextOnRethrow
(1f6133b2)modifyMessageOnFail
option to modifyMessageOnRethrow
(0c8a88f0)power-assert-formatter:
espower:
browser.assert.element(selector)
(ea0a3ce9)espower-source:
espower-loader:
grunt-espower:
gulp-espower:
espowerify:
espower-coffee:
First of all, No change is required if you are using default configuration.
Version 0.8.0 introduces escallmatch syntax for configuration.
If you are:
* using instrumentors such as `espower-loader`, `grunt-espower`, `gulp-espower`, `espowerify` and `espower-coffee`
* or using `espower-source` or `espower` directly
And
* having custom instrumentation pattern using `powerAssertVariableName` or `targetMethods` property
Then you need to migarte. To migrate, please see CHANGELOG for the instrumentor you choose.
empower:
saveContextOnFail
option is renamed to saveContextOnRethrow
modifyMessageOnFail
option is renamed to modifyMessageOnRethrow
targetMethods
does not required any morepower-assert-formatter:
stringifyDepth
does not supported any more. use maxDepth
option instead.