in your Babel configuration. Note that legacy: true is specifically needed if you want to get the same behavior as transform-decorators-legacy because there are newer versions of the decorator specification coming out, and they do not behave the same way as this plugin does.
It's still not clear what's the difference between legacy: true mode and the normal mode exactly: which types of use cases are removed from the spec, what are the breaking changes, etc.
I have created the same issue in Babel's repo.
The docs say:
It's still not clear what's the difference between
legacy: true
mode and the normal mode exactly: which types of use cases are removed from the spec, what are the breaking changes, etc. I have created the same issue in Babel's repo.