[Docs] update output options in readme

[Mottie]

Fix for PR #1957

• Sorted the output options.
• Updated default options for beautify, inline_script and max_line_len.
• Added comments, ie8, preserve_line, shebang, source_map, unescape_regexps and wrap_iife.

[alexlamsl]

Please remove ie8 here as suggested in #1957 (comment)

Users should be using options.ie8 under https://github.com/mishoo/UglifyJS2#minify-options

[alexlamsl]

options.output.source_map is an internal flag used by options.sourceMap, thus no need to be documented.

[alexlamsl]

@Mottie thanks for the work 👍

Looks fine to me except for the two comments above.

[kzc]

Please don't document unescape_regexps:

$ echo 'var a = /\uABCD\uEF/;' | bin/uglifyjs -b ascii_only
var a = /\uABCD\uEF/;

$ echo 'var a = /\uABCDE\uEF/;' | bin/uglifyjs -b unescape_regexps
var a = /ꯍE\uEF/;

I think the code for it should be dropped.

[alexlamsl]

#54 is part of the reason why unescape_regexps is introduced. But as mentioned in #1929 (comment), let's stay out of that game.

I'll put together a PR to remove unescape_regexps shortly.

[Mottie]

Updated.

[alexlamsl]

@Mottie LGTM - thanks!

[kzc]

@alexlamsl Should we drop space_colon? It does not work outside of beautify=true, and even there it's of dubious value:

$ echo 'L:while(1){foo(x?y:{a:1});break L;}' | uglifyjs -b beautify=false,space_colon=false
L:while(1){foo(x?y:{a:1});break L}

$ echo 'L:while(1){foo(x?y:{a:1});break L;}' | uglifyjs -b beautify=false,space_colon=true
L:while(1){foo(x?y:{a:1});break L}

$ echo 'L:while(1){foo(x?y:{a:1});break L;}' | uglifyjs -b beautify=true,space_colon=true
L: while (1) {
    foo(x ? y : {
        a: 1
    });
    break L;
}

$ echo 'L:while(1){foo(x?y:{a:1});break L;}' | uglifyjs -b beautify=true,space_colon=false
L:while (1) {
    foo(x ? y :{
        a:1
    });
    break L;
}

Edit: in beautify=true mode, a space should always be emitted with the colon.

[alexlamsl]

@kzc I have no idea why space_colon was there, and I have explicitly set it to false myself to avoid any doubts in my use cases.

May I investigate further then put together a PR to tackle that instead of blocking this PR?

[kzc]

May I investigate further then put together a PR to tackle that instead of blocking this PR?

It's your call as the maintainer but I think this PR should remove space_colon from the documentation. We don't want to give anyone the idea that it'll be supported. :-)

[kzc]

Be aware that README commits are instantaneously shown on github and are independent of releases.

[alexlamsl]

@kzc alright, you win 🤣

@Mottie would you mind removing space_colon from this PR?

[alexlamsl]

@Mottie thanks for (literally) sorting this!