[Bug]: Legacy decorator not parsed anymore on class (regression from 7.14)

💻

• Would you like to work on a fix?

How are you using Babel?

babel-loader (webpack)

Input code

Similar code & conf than this REPL

except you have to set decorator to legacy (REPL does not save this parameter)

Configuration file name

none, babel-loader options

Configuration

See REPL above

Current and expected behavior

Current behavior

SyntaxError: /Foo.jsx: Unexpected token, expected "{" (43:7)

  41 | }) => isButton ? <button {...restProps} /> : <a {...restProps} />;
  42 |
> 43 | export @withRoute
     |        ^
  44 | class Foo extends React.Component {
  45 |   static propTypes = {

notice the export being before the decorator (in real code it is after)

Expected behavior

no error

Environment

• Babel v7.15.3
• Node v14
• Webpack 5
• babel-loader 8

Possible solution

No response

Additional context

I really do not understand why it fails with my base code and not in REPL, it is very disturbing 😦

[JSteunou]

Ok so pure linaria issue, can I close this issue and share your analyse?

[JSteunou]

@nicolo-ribaudo I made a repo with minimal code so you can help analyze this issue https://github.com/JSteunou/babel-linaria-decorator-issue

Our babel configuration might seems over-engineered but that is because we have a really large code base and I based this repo on it, keeping the same structure to be sure to keep everything that could help.

You can play with it and see that rolling back linaria to 1.4 solve it but not rolling back babel, so the issue is really on linaria side.