New-Bee ... My biggest Espruino fear is coming true!

The errors will be because the code you're minifying has some problem
which means that the minifier can't handle it. I thought it should
have told you what the errors were, but you could paste it into
closure-compiler.appspot.com/home and see what it says.

Hmmm ... The Espruino won't optimize/minimize if there is an "unknown" error/warning?
An on-line Espruino javascript closure compiler -an Espruino double check - very cool indeed.

I took the "LED test delay code snippet" out from the init() startup code.
Now I can simple optimize/whitespace (not advanced due to ?) ...

digitalWrite([LED1,LED2,LED3],0b100);
setTimeout("digitalWrite([LED1,LED2,LED3],0b010);", 1000);
setTimeout("digitalWrite([LED1,LED2,LED3],0b001);", 2000);
setTimeout("digitalWrite([LED1,LED2,LED3],0);", 3000);

From the on-line JS closure compiler warning ...
"simple"
JSC_PARSE_ERROR: Parse error. Binary integer literals are not supported in this language mode. at line 60 character 30
digitalWrite([LED1,LED2,LED3],0b100);

BTW ... going from 1800 jsvars to 3250 jsvars using DrAzzy's bigram provides a much needed breathing room for code development. Thanks DrAzzy
Update ... bigram and my application don't agree with each other?