aboutsummaryrefslogtreecommitdiff
path: root/lib/parse.js
AgeCommit message (Expand)Author
2015-11-09Prevent ReDoS by not using a regexp to verify floating point numbers...`parseFloat` will return `NaN` for invalid numbers anyway, which is the check used to throw the parse error. Fixes #857 Richard van Velzen
2015-10-07Fix handling of "use asm" when no command line flags are passed to uglifyjs. ...kzc
2015-10-07Add proper support for "use asm"; blocks. Disable -c optimization within "use...kzc
2015-10-06Implement shebang supportAnthony Van de Gejuchte
2015-08-27Fix bad parsing of `new new x()()` constructs...Fixes #739 Richard van Velzen
2015-07-29Re-use the caught exception's error message in the parse error call.Chris Cowan
2015-07-29Give a good error message if an invalid regular expression is found.Chris Cowan
2015-05-20Treat \uFEFF as whitespace....Fix #714 Mihai Bazon
2015-05-05Only drop the BOM when it's the first character....Close #704 Mihai Bazon
2015-04-23Fix parsing strings with literal DOS newlines...(should not set newline_before) Fix #693 Mihai Bazon
2015-03-18Fix parsing for U+2028 / U+2029...(they should be treated as whitespace) Mihai Bazon
2015-02-11Add filename to the JS_Parse_Error exception....It would be nice to have access to the filename of the file that includes the code that causes a JavaScript error. This is especially handy if uglifying multiple files at once. Only a small change is needed for this to happen as it's already available in the function that throws the error.Edward Casbon
2015-01-27Add 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-20Add unicode digit parsing supportAnthony Van de Gejuchte
2015-01-20Update unicode letterAnthony Van de Gejuchte
2015-01-06Track ending lines/columns; fix end locations in Mozilla AST.Ingvar Stepanyan
2015-01-05Fix handling \r\n...Close #437 Mihai Bazon
2014-10-20Add option to allow return outside of functions....Close #288 Mihai Bazon
2014-04-18Always quote property names that contain non-ASCII characters....Fix #328 Mihai Bazon
2014-01-21Fix end token for conditionals. Close #404Mihai Bazon
2013-12-22Mark `yield` as reserved word. Close #375.Mihai Bazon
2013-10-30Fix 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-30minorMihai Bazon
2013-10-03Only allow identifier start characters at the beginning of identifiers....Without this fix, the following source: x = {"\u200c": 42}; would incorrectly be converted into a quoteless key. But while \u200c is allowed to be in identifiers, it cannot be at the beginning, as per ES5. (For example, the SockJS client library doesn't work under uglify starting with d9ad3c7c.) David Glasser
2013-09-06Support 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-09-02Fix names.Mihai Bazon
2013-09-02Disallow `continue` referring to a non-IterationStatement. Fix #287...Simplifies handling of labels (their definition/references can be easily figured out at parse time, no need to do it in `figure_out_scope`). Mihai Bazon
2013-09-02Better fix for #286Mihai Bazon
2013-09-02Fix parsing `a.case /= 1`...Close #286 Mihai Bazon
2013-09-02Fix parsing regexp after unary-prefix operator...++/x/.y Fix #284 Mihai Bazon
2013-07-15Revert previous patch, it was no good.Mihai Bazon
2013-07-15Add "position" option to parser, to specify initial pos/line/col...(for parsing embedded scripts) Mihai Bazon
2013-07-12Fix typo....Close #239 Mihai Bazon
2013-05-15Add `--expr`, an option to parse a single expression (suitable for JSON)Mihai Bazon
2013-05-14Fix a["1_1"]...Close #204 Mihai Bazon
2013-05-09Fix is_assignable...(not likely to be noticed, it's only used in `strict` parse mode) Mihai Bazon
2013-05-08Fix property names...Close #199 Mihai Bazon
2013-05-07Fixed dot properties not optimizing unicode identifiers. Signed-off-by: Justi...Justin Lau
2013-03-24Don't print the warning on parse error, just throw a JS_Parse_Error....Fix #159 Mihai Bazon
2013-03-22Keep legit code working even when --screw-ie is not passed....Previously: Without `--screw-ie`, UglifyJS would always leak names of function expressions into the containing scope, as if they were function declarations. That was to emulate IE<9 behavior. Code relying on this IE bug would continue to work properly after mangling, although it would only work in IE (since other engines don't share the bug). Sometimes this broke legitimage code (see #153 and #155). With `--screw-ie` the names would not be leaked into the current scope, working properly in legit cases; but still it broke legit code when running in IE<9 (see #24). Currently: Regardless of the `--screw-ie` setting, the names will not be leaked. Code relying on the IE bug will not work properly after mangling. <evil laughter here> Without `--screw-ie`: a hack has been added to the mangler to avoid using the same name for a function expression and some other variable in the same scope. This keeps legit code working, at the (negligible, indeed) cost of one more identifier. With `--screw-ie` you allow the mangler to name function expressions with the same identifier as another variable in scope. After mangling code might break in IE<9. Oh man, the commit message is longer than the patch. Fix #153, #155 Mihai Bazon
2013-02-01Fix end token for Assign nodesMihai Bazon
2013-01-17Fix 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-22Accept string or number as name of an accessor....[not sure I'm happy about this fix] Reference mishoo/UglifyJS#478 Mihai Bazon
2012-11-07add AST_Accessor and AST_SymbolAccessor node types...AST_Accessor will represent the function for a setter or getter. Since they are not mangleable, and they should not introduce a name in scope, we have a new node for their name (AST_SymbolAccessor) which doesn't inherit from AST_SymbolDeclaration. fix #37 Mihai Bazon
2012-10-13minorMihai Bazon
2012-10-12use AST_Lambda for object setters/getters...so that the optimization that drops the name if unused doesn't apply. close #12 Mihai Bazon
2012-10-11fix pos in syntax error exceptionMihai Bazon
2012-10-11stealing more hacks from acorn in the name of speedMihai Bazon
2012-10-11using makeComparator from acorn to generate functions that tests whether a...string is keyword, reserved etc. speeds up the parser a bit, though not spectacular.. still far from acorn. Mihai Bazon
2012-10-11cleanup...- use prototype-less objects where feasible (minor speed improvement) - get rid of HOP Mihai Bazon
generated by cgit