New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Babel "loose" mode option #268
Comments
I have the same problem in Nuxt storybook, manually adding to nuxt.config.js {
build: {
babel: {
plugins: [
// https://github.com/nuxt/nuxt.js/issues/9224#issuecomment-830577523
['@babel/plugin-proposal-private-property-in-object', { loose: true }],
],
},
},
} didn't silence the warning. |
@pi0 some problem, 2.15.6 |
Then we may have same issue in storybook generated webpack/babel config. /cc @farnabaz |
Any way to fix this yet? |
This works for me, I also have a babel.config.json file with this config.
|
not for me :( |
Didn't work for me either. This other one did though: nuxt/nuxt#9224 (comment) |
Pinning the versions via. yarn resolutions also worked for me -- nuxt/nuxt#9224 (comment) |
Yeah, I've disabled loose mode as well.
and it works fine now
…On Fri, May 28, 2021, 5:23 PM Nigel Ellis ***@***.***> wrote:
Pinning the versions via. yarn resolutions also worked for me -- nuxt/nuxt#9224
(comment)
<nuxt/nuxt#9224 (comment)>
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#268 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAKHIXGGTWGM6LXP7END3BLTP73VJANCNFSM44GVQ33Q>
.
|
This will fix in the next release #277 |
dont fixed @farnabaz .nuxt, .nuxt-storybook, node_modules delete and yarn and repeat dev some problem |
I also still have the same message, adding plugins: [
// https://github.com/nuxt/nuxt.js/issues/9224#issuecomment-830577523
["@babel/plugin-proposal-private-property-in-object", { loose: true }],
], to nuxt.config.js also didn't change it. Using |
The issue exists in Storybook core and seems that they plan to release fix with v6.3. Do you guys can confirm that this fixes using |
Hi @farnabaz , it is working now for me using |
v4.0.4 seems to have fixed the issue for me. Thanks for all the work done! 👍 |
Same here, keep up the good work 👌 |
Version
nuxt-edge@2.16.0-27004333.1676b861
@nuxtjs/storybook@4.0.2
Steps to reproduce
Newest nuxt-edge version fixes the below console error for nuxt, but still shows up for nuxt-storybook...
See original issue at nuxt/nuxt#9224 and fix at nuxt/nuxt#9232
The text was updated successfully, but these errors were encountered: