| Age | Commit message (Expand) | Author |
|---|---|---|
| 2017-03-03 | process code with implicit return statement (#1522)...Bookmarklet for instance implicitedly assumes a "completion value" without using `return`. The `expression` option now supports such use cases. Optimisations on IIFEs also enhanced. fixes #354 fixes #543 fixes #625 fixes #628 fixes #640 closes #1293 | Alex Lam S.L |
| 2017-03-02 | trim unused invocation parameters (#1526) | Alex Lam S.L |
| 2017-03-01 | fix `evaluate` on object getter & setter (#1515) | Alex Lam S.L |
| 2017-02-28 | warn & drop `#__PURE__` iff IIFE is dropped (#1511)...- consolidate `side-effects` optimisations - improve string `+` optimisation - enhance literal & `conditionals` optimisations | Alex Lam S.L |
| 2017-02-26 | consolidate `evaluate` & `reduce_vars` (#1505)...- improve marking efficiency - apply smarter `const` replacement to `var` fixes #1501 | Alex Lam S.L |
| 2017-02-24 | enable `collapse_vars` & `reduce_vars` by default...- fix corner cases in `const` optimisation - deprecate `/*@const*/` fixes #1497 closes #1498 | alexlamsl |
| 2017-02-21 | evaluate AST_SymbolRef as parameter...fix invalid boolean conversion now exposed in `make_node_from_constant()` closes #1477 | alexlamsl |
| 2017-01-26 | optimise binary operands with evaluate() (#1427)...- remove call to evaluate() in is_constant() and let nested optimize() does its job instead - reject RegExp in is_constant() and remove special case logic under collapse_vars - operands to conditionals optimisation are now always evaluate()-ed - throw error in constant_value() instead of returning undefined to catch possible bugs, similar to make_node_from_constant() - optimise binary boolean operators under `evaluate` instead of `conditionals` | Alex Lam S.L |
| 2017-01-26 | augment evaluate to extract within objects (#1425)...- gated by `unsafe` - replaces previous optimisation specific to String.length - "123"[0] => 1 - [1, 2, 3][0] => 1 - [1, 2, 3].length => 3 - does not apply to objects with overridden prototype functions | Alex Lam S.L |
| 2016-05-24 | Completely allow evaluating -0 | Richard van Velzen |
| 2016-05-17 | Never produce -0 when evaluating expressions (like -"")...Fix for #1085. The major case was already there, but more expressions can result in -0. | Richard van Velzen |
 |
index : tracifyjs | |
| Reverse engineer's tool for tracing the flow of data in JS program, based on UglifyJS |
| aboutsummaryrefslogtreecommitdiff |