You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
es6-transpiler seems to automatically pick up linting hints like above in the code it's processing, and become all over-opinionated about it and throw errors.
I'm concatenating and transpiling a bunch of files, and some of these files aren't written by me and contain these linting hints used by their authors in their particular development/testing context.
IMO es6-transpiler should just stick to transpiling and leave it up to us users to add code-linting to our workflow.
Secondly, the transpiler also seems to want to dictate which variables I'm allowed to assign to. (This happens regardless of hinting comments.)
Message:
line 1: can't assign to const variable require
line 913: can't assign to const variable Date
This causes problems with every script emitted by browserify's b.require() method - and also with es5-shim/es5-sham
The text was updated successfully, but these errors were encountered:
/*global define, exports, module */
es6-transpiler seems to automatically pick up linting hints like above in the code it's processing, and become all over-opinionated about it and throw errors.
I'm concatenating and transpiling a bunch of files, and some of these files aren't written by me and contain these linting hints used by their authors in their particular development/testing context.
IMO es6-transpiler should just stick to transpiling and leave it up to us users to add code-linting to our workflow.
Secondly, the transpiler also seems to want to dictate which variables I'm allowed to assign to. (This happens regardless of hinting comments.)
This causes problems with every script emitted by
browserify
'sb.require()
method - and also withes5-shim
/es5-sham
The text was updated successfully, but these errors were encountered: