ES6 method definitions on the tag fails with babel preprocessor - SyntaxError: Unexpected token

[riot]

ES6 method definitions on the tag fails with babel preprocessor - SyntaxError: Unexpected token

[GianlucaGuarini]

@talee you can't use both the preprocessors (riot and babel) together. Your javascript gets processed only once either by babel or riot, combining both it's not possible (and it's dangerous). This does not mean that you can not build your own adding special plugin to parse that kind of expressions

[talee]

@GianlucaGuarini - Thanks for the explanation! Does the Riot preprocessor do anything else besides transpile ES6 method definitions for tag instances? It would be good to know if there any other situations where I should not use Riot specific syntax.

Running riot --type babel component.tag is not clear to the user that the Riot preprocessor is being executed. If mixing Riot and Babel preprocessors is illegal/indeterminate, we should suppress the Riot preprocessor when a --type option is passed.

A bonus would be to document this so people using ES6 and following Riot syntax for custom tags aren't confused: http://riotjs.com/guide/compiler/#pre-processors.

[aMarCruz]

@talee, the default riot parser does nothing more than remove comments and transpile ES6 method definitions.

As @GianlucaGuarini said, you can use only one JS parser, no one example shows method shortcuts of the riot parser with babel.

[aMarCruz]

Closing this issue, the answer is clear.