Skip to content
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

CallStackSizeExceeded when accessing $i18n.localeProperties.value within a component with a local scope applied #2338

Closed
FreekVR opened this issue Aug 22, 2023 · 1 comment · Fixed by #2340
Labels
API ❗ p4-important Priority 4: bugs that violate documented behavior, or significantly impact perf regression v8

Comments

@FreekVR
Copy link

FreekVR commented Aug 22, 2023

Environment


  • Operating System: Linux
  • Node Version: v16.17.0
  • Nuxt Version: 3.6.5
  • Nitro Version: 2.5.2
  • Package Manager: yarn@1.22.19
  • Builder: vite
  • User Config: telemetry, modules, i18n
  • Runtime Modules: @nuxtjs/i18n@8.0.0-rc.3
  • Build Modules: -

Reproduction

https://codesandbox.io/p/github/nuxt/starter/csb-ctzmpk/draft/cranky-brown?file=/pages/index.vue:12,1

Describe the bug

This combination in a page component results in a "Maximum call stack size exceeded"

<script setup>
import { useI18n } from "#i18n";

// Remove this block to remove the error...
const { t } = useI18n({
  useScope: "local",
});

// Or don't do this...
console.log(useI18n().localeProperties.value);
</script>

Additional context

No response

Logs

No response

Copy link
Collaborator

kazupon commented Aug 24, 2023

Thank you for you reporting!

The root cause of this issue is the same as #2335

@kazupon kazupon added the ❗ p4-important Priority 4: bugs that violate documented behavior, or significantly impact perf label Aug 24, 2023 — with Volta.net
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
API ❗ p4-important Priority 4: bugs that violate documented behavior, or significantly impact perf regression v8
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants