Skip to content

Tags: unassert-js/unassertify

Tags

v3.0.1

Toggle v3.0.1's commit message
2022-08-07

  * [fix] put .cjs back to .js since browserify ecosystem doesn't yet understand .cjs

v3.0.0

Toggle v3.0.0's commit message
2022-08-07

  * [feat] upgrade unassert to 2.0.0
  * [chore] change `.js` to `.cjs`

This release will not affect most users. This is a major release of "just in case" for unassert-v2 which is completely rewritten.

v2.1.1

Toggle v2.1.1's commit message
2018-04-19

  * [perf] Skip parsing if file doesn't contain assertions (by @goto-bus-stop)

v2.1.0

Toggle v2.1.0's commit message
2017-10-23

  * [feat] Set `ecmaVersion: 2018` when parsing (by @goto-bus-stop)

v2.0.5

Toggle v2.0.5's commit message
hashbangs (2017-10-17)

  * [fix] fix parsing code with hashbangs (#!) (by @goto-bus-stop)

v2.0.4

Toggle v2.0.4's commit message
2016-12-28

  * [chore] transfer to unassert-js organization
  * [chore] switch to acorn

v2.0.3

Toggle v2.0.3's commit message
2015-12-16

  * [fix] copy sourceRoot even if it is an empty string

v2.0.2

Toggle v2.0.2's commit message
Ignore JSON file (2015-09-27)

  * [fix] should not transform JSON file

v2.0.1

Toggle v2.0.1's commit message
2015-09-27

  * [docs] add SUPPORTED PATTERNS section to README
  * [refactor] linting and refactoring

v2.0.0

Toggle v2.0.0's commit message
Remove assertions even if `debug` option is on (2015-09-25)

  * [feat] remove assertions even if `debug` option is on.
  * [BC] Since this release, assertions are always removed even if `debug` option is on. If you don't want to remove assertions when `debug` is on, simply do not add `unassertify` on that build configuration.