No longer works with uglify-js

[ibc]

I think that, due this commit debug no longer works with browserify + gulp-uglify (which uses uglify-js internally):

 GulpUglifyError: unable to minify JavaScript
Caused by: SyntaxError: Unexpected token: keyword (const)
File: /Users/ibc/xxxx/src/myApp/myApp.js
Line: 24207
Col: 1

If I use browserify without uglify and check the generated bundled JS file, it contains:

const c = 'color: ' + this.color;

// and many other ES6 stuff

I don't think this is intentional, am I right?

[Qix-]

It is intentional. Uglify is outdated doesn't work on ES6 code. Use gulp-uglify-es instead.

[ibc]

gulp-uglify-es uses uglify-es which is buggy and unmaintained. You may mean gulp-terser and terser.

Anyway, are you aware that webpack requires that NPM dependencies are ES5? I mean: expect lot of complains due to this change in debug.

[Qix-]

Check the package readme for gulp-uglify-es:

gulp stream to uglify with 'terser' (es6 supported).

terser is the new 'uglify-es'. uglify-es is no longer maintained.

It uses terser, pretty plainly indicated at the top of their readme.

[ibc]

Thanks, didn't check that.

Anyway, as said above, expect lot of complains from webpack users.

[Qix-]

Also,

Anyway, are you aware that webpack requires that NPM dependencies are ES5?

Are you aware that babel exists and is a standard tool to compile ES6+ code to ES5 and pretty seamlessly interops with weboack, rollup, parcel and a slew of other bundlers that could have been easily researched with a Google search instead of yelling at a package maintainer? 😉

[ibc]

Sure, I know babel. I also know that default webpack configuration (that which is widely used) does not convert node_modules/* to ES5:

Just a reference: vercel/next.js#3564

[Qix-]

@ibc I used to work at ZEIT. We used Babel very effectively where needed. You don't want your entire node_modules compiled because that would be silly.

Further, modules providing a transpiled version is unsustainable. Please read vercel/next.js#3564 (comment) as he is pretty objectively correct.

I won't discuss this issue any more as the decision has been made to follow current best practices. I suggest researching further as there are leagues of prose on this matter available to you through various searches. This is where the JavaScript ecosystem is headed and has already been adopted pretty much everywhere else.

Debug will not be transpiling code any longer except for browser versions, which I'm looking into deprecating as well.