Decorators error after upgrading to 1.16.0

[markdalgleish]

Discussed in #6326

^{Originally posted by erandow May 6, 2023}
After upgrading remix to the latest version(1.16.0),
I get the following error after running project locally.]
The 'decorators' plugin requires a 'decoratorsBeforeExport' option, whose value must be a boolean. If you are migrating from Babylon/Babel 6 or want to use the old decorators proposal, you should use the 'decorators-legacy' plugin instead of 'decorators'. [plugin css-side-effects-plugin]
I also set the future.unstable_cssSideEffectImports: true but the errors still exist.

[markdalgleish]

@erandow I haven't been able to reproduce the issue. Could you please share a repro?

[markdalgleish]

@erandow It looks like the decoratorsBeforeExport option is deprecated: https://babel.dev/docs/babel-parser#plugins-options. This seems likely to do with an older version of @babel/parser. Are you able to confirm which version you're using?

[nakleiderer]

I had a similar issue when I upgraded only Remix, but it went away when I upgraded all outdated packages in my app. I imagine npm was picking up an older version of babel for one of my other dependencies.

[markdalgleish]

This shouldn't be an ongoing issue once #6390 goes out.

[github-actions]

🤖 Hello there,

We just published version v0.0.0-nightly-9de3c4b-20230515 which involves this issue. If you'd like to take it for a test run please try it out and let us know what you think!

Thanks!

[markdalgleish]

@erandow Are you able to check your issue against the night release?

[erandow]

@markdalgleish,
Thanks for creating an issue and trying to fix the issue.
Sorry, I was offline and couldn't answer your questions.

Thanks, It seems that there is no problem with the nightly release.

[github-actions]

🤖 Hello there,

We just published version 1.16.1-pre.0 which involves this issue. If you'd like to take it for a test run please try it out and let us know what you think!

Thanks!

[github-actions]

🤖 Hello there,

We just published version 1.16.1 which involves this issue. If you'd like to take it for a test run please try it out and let us know what you think!

Thanks!