2.1.2 (2019-01-11)
- remove xtend (by jimmywarting)
2.1.1 (2018-05-15)
- Update default
ecmaVersion
to 2018 (f315b49)
2.1.0 (2017-05-21)
2.0.3 (2017-02-19)
2.0.2 (2017-01-12)
2.0.1 (2016-11-16)
2.0.0 (2016-11-11)
- Embed value capturing helper into transpiled code
- Expose visitor object for estraverse
- stop exposing Instrumentor and AssertionVisitor (afa380f9)
- Remove destructive option
- Drop support for prebuilt bundle, bower and Node v0.10
We stopped providing prebuilt bundle for browsers. Please build your own by using browserify, webpack and so on. We also dropped bower support. Please use npm instead.
- Internal classes
espower.Instrumentor
andespower.AssertionVisitor
are not exported any more.
(afa380f9)
The destructive
option has been removed.
New behavior is like destructive: true
, means that passed AST is modified directly.
If you do not want your AST to be modified directly, you should deep-clone your AST by yourself.
1.3.2 (2016-06-22)
- fix breaking changes introduced in 1.3.0 and 1.3.1
1.3.1 (2016-06-21)
- stop capturing SequenceExpression itself since SequenceExpressions are not enclosed in parentheses in some cases (e8acbc61)
1.3.0 (2016-06-21)
1.2.1 (2015-11-06)
1.2.0 (2015-11-05)
1.1.0 (2015-11-03)
1.0.7 (2015-09-21)
1.0.6 (2015-06-07)
- SourceMap's
sourceRoot
should have precedence overoptions.sourceRoot
ifsourceRoot
is URL (dcf9642d)
1.0.5 (2015-06-05)
- update escallmatch to 1.4.2 and espurify to 1.3.0 (62973ed)
- use licensify to prepend license header (d3bc5e8)
1.0.4 (2015-06-04)
- try to create relative path if sourceMap.sourceRoot is locating source files on on a server (ec0a91ba)
- never show absolute path or URL in power-assert output (252b043f)
1.0.3 (2015-05-31)
- use basename when
sourceRoot
inoptions.sourceMap
is locating source files on a server (7822df1b)
1.0.2 (2015-05-30)
- use basename when incoming
options.path
is absolute and it conflicts withoptions.sourceRoot
orsourceRoot
inoptions.sourceMap
(02f7b35a)
1.0.1 (2015-05-29)
- apply
options.sourceRoot
if and only if incomingoptions.path
is absolute (65b4012a)
1.0.0 (2015-05-25)
- transfer to power-assert-js organization (c3b79559)
- support
deepStrictEqual
andnotDeepStrictEqual
(9d98bc17) sourceRoot
option. If set, filepath in power-assert output will be relative fromsourceRoot
visitorKeys
option to customize AST traversal
0.11.0 (2015-04-18)
- throw Error if AST is already instrumented (1d47bdc3)
0.10.0 (2014-11-11)
- espower:
- espower: decide to be skipped first, then enter node (9d0a778a)
- espower:
- espower:
- built and modularized by browserify
- use escallmatch module to describe instrumentation target patterns
- support chained callee like
browser.assert.element(selector)
(ea0a3ce9)
- option
powerAssertVariableName
is now deprecated and ignored. Please usepatterns
option instead (2f023f91) - option
targetMethods
is now deprecated and ignored. Please usepatterns
option instead (e75e5d35)
If you already customize instrumentation pattern using powerAssertVariableName
and targetMethods
, you need to migarte. To migrate, change your code from the following:
var options = {
powerAssertVariableName: 'yourAssert',
targetMethods: {
oneArg: [
'okay'
],
twoArgs: [
'equal',
'customEqual'
]
}
};
var modifiedAst = espower(jsAst, options);
To:
var options = {
patterns: [
'yourAssert(value, [message])',
'yourAssert.okay(value, [message])',
'yourAssert.equal(actual, expected, [message])',
'yourAssert.customEqual(actual, expected, [message])'
]
};
var modifiedAst = espower(jsAst, options);