| Age | Commit message (Expand) | Author |
|---|
| 2015-07-30 | Fix semicolon printing when restricting max line length...Fixes #755
| Richard van Velzen |
| 2015-05-04 | Fix blank lines in the output....The issue was more obvious when max_line_len has a small value, rather than
the default 32K characters. A blank line showed up after most statements.
| Mihai Bazon |
| 2015-01-27 | Add option to preserve/enforce string quote style...`-q 0` (default) use single or double quotes such as to minimize the number of
bytes (prefers double quotes when both will do); this is the previous
behavior.
`-q 1` -- always use single quotes
`-q 2` -- always use double quotes
`-q 3` or just `-q` -- always use the original quotes.
Related codegen option: `quote_style`.
Close #495
Close #460
Some `yargs` guru please tell me why `uglifyjs --help` doesn't display the
help string for `-q` / `--quotes`, and why it doesn't output the expected
argument types anymore, like good old `optimist` did.
| Mihai Bazon |
| 2015-01-26 | Keep single line comments after nlb, after nlb...Fixes #583
| Anthony Van de Gejuchte |
| 2015-01-04 | Fix #556...`\uFEFF` (ZERO WIDTH NO-BREAK SPACE) is removed when parsing, but was
un-escaped for the output when `ascii_only` was false.
When using
UglifyJS multiple times (creating packages from minified sources, for
example), this would lead to problems because the byte was removed when
parsing for the second time.
| Richard van Velzen |
| 2015-01-04 | Merge pull request #592 from micschro/patch-1...Fix max_line_len not working for JSON files | Richard van Velzen |
| 2014-12-31 | Fix #597...NaN and Infinity were replaced in the output generation, instead of
during compression. This could lead to results where `1/0` was inserted
without parens leading to invalid output.
The nodes are replaced in the compression step now, and the output
generation returns their regular names. This should not be a problem,
since they're already only constructed from the original name.
| Richard van Velzen |
| 2014-12-17 | Fix max_line_len not working for JSON files...As `maybe_newline()` is only called when `might_need_semicolon` is `true`, the `max_line_len` option has no effect for files without (or with very few) semicolons (like JSON files). A simple for this problem is to use `maybe_newline()` instead of `noop` as the `newline()` function in non-beautify mode. | micschro |
| 2014-07-18 | Fix parens for AST_Undefined...Do the same as for AST_Unary, since we output undefined as `void 0`.
Reported at https://github.com/mishoo/UglifyJS2/issues/338#issuecomment-48858341
| Mihai Bazon |
| 2014-07-01 | Check for the case an AST_For's init is an EmptyStatement...(lame fix for #503)
| Mihai Bazon |
| 2014-04-27 | Actually, even better. #475...- also handle x = + ++y, x = - --y;
- don't use parens, a space suffices.
| Mihai Bazon |
| 2014-04-27 | Better fix for #475 | Mihai Bazon |
| 2014-04-27 | Fix parens in +(+x). Close #475 | Mihai Bazon |
| 2014-01-26 | Merge branch 'master' of github.com:mishoo/UglifyJS2 | Mihai Bazon |
| 2014-01-26 | Move unescaping regexps under a codegen option (`unescape_regexps`) | Mihai Bazon |
| 2014-01-25 | Don't unescape \x00 in regexes (it breaks IE8) | Daniel Stutzman |
| 2014-01-21 | More chars that cannot be unescaped in regexps. | Mihai Bazon |
| 2014-01-19 | Don't unescape byte order marks in regexps | Ville Lautanala |
| 2014-01-18 | Don't unescape \x2f (slash) in regexps. #54 | Mihai Bazon |
| 2014-01-10 | simplify | Mihai Bazon |
| 2014-01-10 | Unescape Unicode sequences in regexps when ascii_only is false. #54 | Mihai Bazon |
| 2014-01-05 | Fix parens for property access -- (foo, bar)["baz"] | Mihai Bazon |
| 2013-12-18 | Better fix for comments in AST_Exit...Close #374
| Mihai Bazon |
| 2013-12-18 | Take out all comments from an AST_Exit's value...Fix #372
| Mihai Bazon |
| 2013-10-30 | Workaround for Safari bug...Close #313
| Mihai Bazon |
| 2013-10-30 | Fix parsing setters/getters (allow keywords for name)....The "key" property was always "set" or "get", which didn't make much sense.
Now it'll be the actual name of the setter/getter (AST_Node), and the
AST_Accessor object itself, which represents the function, won't store any
name.
Close #319
| Mihai Bazon |
| 2013-10-30 | Fix output for `x = 2 * (a % b / b * c)`...(issue #337)
| Mihai Bazon |
| 2013-10-29 | Add "preamble" output option...Close #335
| Mihai Bazon |
| 2013-10-28 | Fix codegen for when comments_before is undefined....Fix #333
| Mihai Bazon |
| 2013-09-06 | Avoid printing <!-- in the output (HTML5 comment) | Mihai Bazon |
| 2013-09-06 | Support HTML5 comment syntax (enabled by default!)...See http://javascript.spec.whatwg.org/#comment-syntax
https://github.com/mishoo/UglifyJS/issues/503
https://github.com/marijnh/acorn/issues/62
| Mihai Bazon |
| 2013-08-20 | Move support for `negate_iife` in the compressor, rather than code generator...(the code generator doesn't maintain enough context to know whether
the return value is important or discarded)
Fixes #272
| Mihai Bazon |
| 2013-08-18 | fixes #259: don't unnecessarily quote object properties when --screw-ie8 | Michael Ficarra |
| 2013-07-18 | Fix output for arrays whose last element is a hole: [1,,]...1529ab96 started to do this (by considering holes to be separate from
"undefined") but it still converted
[1,,] (length 2, last element hole, trailing comma)
to
[1,] (length 1, trailing comma)
Unfortunately the test suite doesn't really make this clear: the new test here
passes with or without this patch because run-tests.js beautifys the expected
output (in "make_code"), which does the incorrect transformation! If you make
some manual change to arrays.js to make the test fail and see the INPUT and
OUTPUT, then you can see that without this fix, [1,,] -> [1,], and with this fix
it stays [1,,].
| David Glasser |
| 2013-06-03 | Escape null characters as \x00...Since \0 might be mistakenly interpreted as octal if followed by a
number and using literal null is in some cases interpreted as end of
string, escape null as \x00. | Ville Lautanala |
| 2013-05-22 | Add `negate_iife` option to the code generator....See discussion in a9511dfbe5c0d96d8cacb87582aa9a19737bbb98
| Mihai Bazon |
| 2013-05-20 | Fix output of statement: `new function(){...};`...Close #209
| Mihai Bazon |
| 2013-05-09 | Use the negation hack rather than parens for a toplevel function expression call...(only in !beautify mode)
| Mihai Bazon |
| 2013-03-31 | Quote objects with numeric keys | Vladimir Zhuravlev |
| 2013-03-31 | Don't use \xYY for identifiers...Fix #173
| Mihai Bazon |
| 2013-03-31 | Output, to_ascii: Escape non-ascii chars with \xnn instead of \unnnn whenever... | Andreas Lind Petersen |
| 2013-02-06 | Force space after literal regexp when used in "instanceof" or "in"...Close #118
| Mihai Bazon |
| 2013-02-06 | Fix parens for NaN...Close #116
| Mihai Bazon |
| 2013-02-06 | Fix parens for negative numbers...Close #115
| Mihai Bazon |
| 2013-02-06 | Fix parens for AST_New...Close #114
| Mihai Bazon |
| 2013-02-05 | Ugly hack to print comments before return/throw statements...Close #112
| Mihai Bazon |
| 2013-01-17 | [AST_Hole] the print function can be a no-op. | Mihai Bazon |
| 2013-01-17 | Fix output for arrays containing undefined values....1b6bcca7 was a first attempt at this. That commit made Uglify stop replacing
holes with undefined, but instead it started replacing undefined with
holes. This is slightly problematic, because there is a difference between a
hole and an undefined value. More problematically, it changed [1,undefined] to
[1,] which generally doesn't even parse as a hole (just as a trailing comma), so
it didn't even preserve the length of the array!
Instead, parse holes as their own special AST node which prints invisibly.
| David Glasser |
| 2012-12-21 | Fix output when semicolons is off....(need to force a semicolon for the empty body of an `if`)
Close #72
| Mihai Bazon |
| 2012-12-12 | Small cleanup | Mihai Bazon |
