2.3.0 (2018-06-12)
2.2.0 (2017-05-05)
2.1.0 (2017-04-09)
2.0.1 (2017-02-13)
2.0.0 (2016-11-12)
- Integrate
empower-assertto enable transparent assertion enhancement - Embed value capturing helper into transpiled code (by upgrading espower to 2.0.0) (78a57687)
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.
1.2.0 (2016-10-25)
1.1.0 (2016-01-22)
- relax too strict originalCode checking (458ef9f1)
1.0.0 (2015-08-08)
- properties of outgoing SourceMap is broken when
typeof options.sourceMapis string (af6ba419) - preserve sourceRoot if incoming sourceMap contains sourceRoot (c95e3252)
- transfer to power-assert-js organization (ff22316e)
- ship bundle for browsers with npm module (36b4ed84)
- sourceRoot option
- throw EspowerError when
originalCodeis not specified (04d86abb) - clarify parameter prerequisite and its outcome (95ed841b)
0.10.0 (2014-11-11)
- espower-source:
- update espower to 0.10.0 (cd05911e)
- espower-source: update espower to 0.9.1 (8acad23d)
- espower-source: backport espowerify to support multi-stage sourcemaps (71de737c)
- espower-source:
- update espower to 0.8.0 (ae15a229)
If you already customize instrumentation pattern using powerAssertVariableName and targetMethods, you need to migarte. To migrate, change your code from the following:
var espowerSource = require('espower-source');
var options = {
powerAssertVariableName: 'yourAssert',
targetMethods: {
oneArg: [
'okay'
],
twoArgs: [
'equal',
'customEqual'
]
}
};
var modifiedCode = espowerSource(originalCode, filepath, options);To:
var espowerSource = require('espower-source');
var options = {
patterns: [
'yourAssert(value, [message])',
'yourAssert.okay(value, [message])',
'yourAssert.equal(actual, expected, [message])',
'yourAssert.customEqual(actual, expected, [message])'
]
};
var modifiedCode = espowerSource(originalCode, filepath, options);