| Age | Commit message (Collapse) | Author | |
|---|---|---|---|
| 2017-09-10 | Testing all leading comments against being PURE comments (#2305) | Mateusz Burzyński | |
| 2017-03-31 | combine rules for binary boolean operations (#1744) | Alex Lam S.L | |
| 2017-02-28 | warn & drop `#__PURE__` iff IIFE is dropped (#1511) | Alex Lam S.L | |
| - consolidate `side-effects` optimisations - improve string `+` optimisation - enhance literal & `conditionals` optimisations | |||
| 2017-02-21 | Support marking a call as pure | kzc | |
| A function call or IIFE with an immediately preceding comment containing `@__PURE__` or `#__PURE__` is deemed to be a side-effect-free pure function call and can potentially be dropped. Depends on `side_effects` option. `[#@]__PURE__` hint will be removed from comment when pure call is dropped. fixes #1261 closes #1448 | |||
 |
index : tracifyjs | |
| Reverse engineer's tool for tracing the flow of data in JS program, based on UglifyJS |
| aboutsummaryrefslogtreecommitdiff |