Storybook: Babel "loose" mode option

[visini]

Version

[email protected]
@nuxtjs/[email protected]

Steps to reproduce

Newest nuxt-edge version fixes the below console error for nuxt, but still shows up for nuxt-storybook...

Though the "loose" option was set to "false" in your @babel/preset-env config, it will not be used for @babel/plugin-proposal-private-property-in-object since the "loose" mode option was set to "true" for @babel/plugin-proposal-private-methods.The "loose" option must be the same for @babel/plugin-proposal-class-properties, @babel/plugin-proposal-private-methods and @babel/plugin-proposal-private-property-in-object (when they are enabled): you can silence this warning by exp

See original issue at https://github.com/nuxt/nuxt.js/issues/9224 and fix at https://github.com/nuxt/nuxt.js/pull/9232

[pi0]

https://github.com/nuxt/nuxt.js/issues/9224#issuecomment-835742221

[rockmandash]

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.

[productfrontenddeveloper]

@pi0 some problem, 2.15.6
In case of having same issue after upgrading to 2.15.6, please remove lock file (yarn.lock or package.lock.json), node_modules/.cache and .nuxt. If still having issues, please report here.
dont fixed

[pi0]

Then we may have same issue in storybook generated webpack/babel config. /cc @farnabaz

[DominusKelvin]

Any way to fix this yet?

[irvv17]

babel

This works for me, I also have a babel.config.json file with this config.

{ "presets": [ [ "@babel/preset-env", { "targets": { "node": true } } ] ] }

[derevandal]

babel

This works for me, I also have a babel.config.json file with this config.

{ "presets": [ [ "@babel/preset-env", { "targets": { "node": true } } ] ] }

not for me :(

[hacknug]

This works for me, I also have a babel.config.json file with this config.

{ "presets": [ [ "@babel/preset-env", { "targets": { "node": true } } ] ] }

Didn't work for me either. This other one did though: https://github.com/nuxt/nuxt.js/issues/9224#issuecomment-830237126

[nigel-codaio]

Pinning the versions via. yarn resolutions also worked for me -- https://github.com/nuxt/nuxt.js/issues/9224#issuecomment-830237126

[derevandal]

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.js#9224
(comment)
https://github.com/nuxt/nuxt.js/issues/9224#issuecomment-830237126

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/nuxt-community/storybook/issues/268#issuecomment-850652293,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAKHIXGGTWGM6LXP7END3BLTP73VJANCNFSM44GVQ33Q
.

[farnabaz]

This will fix in the next release https://github.com/nuxt-community/storybook/pull/277

[productfrontenddeveloper]

dont fixed @farnabaz .nuxt, .nuxt-storybook, node_modules delete and yarn and repeat dev some problem

[krisimmig]

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 "@nuxtjs/storybook": "^4.0.3",

[farnabaz]

The issue exists in Storybook core and seems that they plan to release fix with v6.3.
I've published a patch release to fix this issue.

Do you guys can confirm that this fixes using "@nuxtjs/storybook": "^4.0.4"?

[krisimmig]

Hi @farnabaz , it is working now for me using nuxtjs/storybook 4.0.4 and not using the plugin-proposal-private-property-in-object plugin.
👍

[hacknug]

v4.0.4 seems to have fixed the issue for me. Thanks for all the work done! :+1:

[lorocher]

v4.0.4 seems to have fixed the issue for me. Thanks for all the work done! 👍

Same here, keep up the good work 👌