Permalink
Commits on Dec 24, 2011
  1. v1.2.3

    committed Dec 24, 2011
  2. improved redo_if (closes #283)

    committed Dec 24, 2011
Commits on Dec 20, 2011
Commits on Dec 13, 2011
  1. v1.2.2

    committed Dec 13, 2011
  2. version 1.2.1

    committed Dec 13, 2011
Commits on Dec 9, 2011
  1. made npm happy

    committed Dec 9, 2011
  2. version 1.2

    committed Dec 9, 2011
  3. updated doc

    added --no-mangle-functions
    committed Dec 9, 2011
  4. option to prevent mangling or dropping of function names (#267)

    pass -nmf (--no-mangle-functions)
    committed Dec 9, 2011
Commits on Dec 3, 2011
Commits on Dec 2, 2011
  1. Merge pull request #248 from WolfgangKluge/endpos-in-tokens

    Keep the end position of each token
    committed Dec 2, 2011
  2. Merge pull request #258 from ikokostya/fix-error-pos

    Fixed parse error position: start line number and column number from 1.
    committed Dec 2, 2011
  3. Use a different scope for labels than for variables.

    This makes it safe to minify toplevel labels, since they can't be referenced
    from outside their immediate body.  Additionally, discard labels that aren't
    referenced.  Updated tests.
    
    (fixes #256)
    committed Dec 2, 2011
  4. Merge pull request #263 from ikokostya/object

    Unsafe Object constructor transformations:
    committed Dec 2, 2011
  5. Unsafe Object constructor transformations:

    new Object()  => {}
    new Object    => {}
    Object()      => {}
    new Object(x) => Object(x)
    ikokostya committed Dec 2, 2011
Commits on Nov 25, 2011
  1. some cleanup

    (it seems we don't need the scope in ast_squeeze; moved code that drops
    unused lambda names in ast_mangle)
    committed Nov 25, 2011
  2. at most one ';' at EOF

    committed Nov 25, 2011
Commits on Nov 23, 2011
Commits on Nov 21, 2011
  1. String(a) => a+"" (with --unsafe)

    fixes #254
    committed Nov 21, 2011
Commits on Oct 25, 2011
  1. Keep end position of each token

    The value is not sufficient to calculate the end position (e.g.
    string with escape sequences), so we need a new property.
    This modification allows e.g. color coding of the tokenized code.
    WolfgangKluge committed Oct 25, 2011
Commits on Oct 22, 2011
  1. escaped slash character in regexp

    committed Oct 22, 2011
Commits on Oct 17, 2011
Commits on Oct 11, 2011
  1. version 1.1.1

    committed Oct 11, 2011
Commits on Sep 29, 2011
  1. add final semicolon (closes #126)

    committed Sep 29, 2011
Commits on Sep 23, 2011
  1. negating >= and <= operators is back to --unsafe (closes #239)

    Rationale: when one of the operands is undefined, the result is always
    false, therefore we would have `a <= b` === `a > b` === `false`, changing
    the value of conditional expressions that rely on this horrible JS kludge.
    committed Sep 23, 2011
  2. better fix instead of f896f69

    committed Sep 23, 2011
  3. fix parenthesization of anonymous function calls

    after 1721863 expressions like this:
    
    `(function(){ ... })()`
    
    were added two pairs of parens.
    committed Sep 23, 2011
  4. reverted last patch

    (escaped literal newlines shouldn't be kept in fact.. always get tricked on
    this)
    committed Sep 23, 2011
  5. Merge pull request #238 from proxv/multiline-strings-semicolons

    Don't insert semicolons before multi-line strings.
    committed Sep 23, 2011