fix(babel): loose option for babel private-property-in-object

[clarkdo]

Types of changes

• Bug fix (a non-breaking change which fixes an issue)
• New feature (a non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Description

Issue #9224 (comment)

Similar fix to #9232.

@babel/plugin-proposal-private-methods has been added to @babel/preset-env now, but the syntax is not supported by webpack 4, so this pr is excluding it from preset-env and setting loose option as a seprate plugin.

Checklist:

• My change requires a change to the documentation.
• I have updated the documentation accordingly. (PR: #)
• I have added tests to cover my changes (if not applicable, please state why)
• All new and existing tests are passing.

[henrycunh]

thanks for this!

[vinayakkulkarni]

LGTM

[yosiawan]

nice!

[frederikhors]

Please! The console gets spammed every time on npm run dev!

[atinux]

@mrleblanc101 can you try nuxt-edge?

[clarkdo]

@mrleblanc101 It is closed by issue creator, can you comment in that issue ?

[mrleblanc101]

Wait this is a merge request. I meant to comment on the issue related to that merge request, my bad.

[Intevel]

I still have the problem unfortunately, just created a new Nuxt project.

[atinux]

Can you try using nuxt-edge @Intevel ?

[monsieurnebo]

Hi @atinux ,

nuxt-edge is fixing this issue as expected.

When is the next nuxt release (including this fix) planned?

[atinux]

We are working with @pi0 to release it ASAP, some prs are pending at the moment.

[pi0]

Fix released in v2.15.8

[kingyue737]

I still meet this warning in 2.15.8

[pi0]

@kingyue737 Can you please ensure lock file is recreated and you are not using any other workaround inside nuxt.config for babel? If still have issue, a way to reproduction would be nice.

[vinayakkulkarni]

I still meet this warning in 2.15.8

add this to your sh

alias nbomb='rm -rf node_modules/ package-lock.json && npm i --no-audit'

then do nbomb in your local repo :P

voila!

[kingyue737]

I still meet this warning in 2.15.8

add this to your sh

alias nbomb='rm -rf node_modules/ package-lock.json && npm i --no-audit'

then do nbomb in your local repo :P

voila!

It works! Thank you

[mrleblanc101]

Why would you do such a thing, you just need to do npm upgrade or yarn upgrade

[kingyue737]

Why would you do such a thing, you just need to do npm upgrade or yarn upgrade

I don't know. I npm upgrade and audit fix my dependencies, but the warning still exists. After removing all the packages and reinstalling without auditing, the warning disappears.

[monsieurnebo]

Thanks for the great work @pi0 👏

[Suv4o]

Great @pi0 . Thank you for fixing it✌️

[n4an]

not work

[n4an]

Fix released in v2.15.8

is not fixed

[mrleblanc101]

@Mitch-i it is fixed, read the whole thread of how to update you peerDependancy.

[n4an]

@Mitch-i it is fixed, read the whole thread of how to update you peerDependancy.

is not fixed, it appear and the problem is not in peerDependancy. i use latest version and a fresh test project

Error: Decorating class property failed. Please ensure that proposal-class-properties is enabled and runs after the decorators transform.

[mrleblanc101]

@Mitch-i Clearly this is not the same error. You should probably open a new issue with a repro or a step by step guide on how you got this error

[IrtezaAsadRizvi]

Awesome!