FATAL ERROR: Reached heap limit Allocation failed - JavaScript heap out of memory

nuxt-modules / i18n

I18n module for Nuxt

MIT License

1.66k stars 467 forks source link

Environment

Operating System: Darwin
Node Version: v20.9.0
Nuxt Version: 3.12.2
CLI Version: 3.12.0
Nitro Version: 2.9.7
Package Manager: npm@10.2.5
Builder: -
User Config: app, devtools, imports, components, vite, modules, css, i18n, build, top_menu, serverOptions, runtimeConfig, license, style, form, security, routeRules
Runtime Modules: @vueuse/nuxt@10.10.0, nuxt-security@1.4.3, nuxt3-leaflet@1.0.13, nuxt-scheduler@0.1.9, @pinia/nuxt@0.5.1, nuxt-lodash@2.5.3, @vee-validate/nuxt@4.12.6, @nuxtjs/i18n@8.3.1, (), @sidebase/nuxt-pdf@0.1.2
Build Modules: -

Reproduction

cannot reproduction on stackblitz

Describe the bug

use last version v8.3.1, not work. I get this error after "npm run build":

<--- Last few GCs --->

[21894:0x7fc7c1700000]   176963 ms: Scavenge 2023.9 (2075.8) -> 2017.4 (2077.1) MB, 4.16 / 0.00 ms  (average mu = 0.539, current mu = 0.465) allocation failure; 
[21894:0x7fc7c1700000]   177023 ms: Scavenge 2025.2 (2077.6) -> 2022.4 (2077.6) MB, 4.09 / 0.00 ms  (average mu = 0.539, current mu = 0.465) allocation failure; 
[21894:0x7fc7c1700000]   177044 ms: Scavenge 2025.6 (2077.6) -> 2022.1 (2097.4) MB, 11.38 / 0.00 ms  (average mu = 0.539, current mu = 0.465) allocation failure; 

<--- JS stacktrace --->

FATAL ERROR: Reached heap limit Allocation failed - JavaScript heap out of memory
[....]
zsh: abort      npm run build

Additional context

No response

Logs

No response

Would you be able to provide a reproduction? 🙏

More info

### Why do I need to provide a reproduction? Reproductions make it possible for us to triage and fix issues quickly with a relatively small team. It helps us discover the source of the problem, and also can reveal assumptions you or we might be making. ### What will happen? If you've provided a reproduction, we'll remove the label and try to reproduce the issue. If we can, we'll mark it as a bug and prioritise it based on its severity and how many people we think it might affect. If `needs reproduction` labeled issues don't receive any substantial activity (e.g., new comments featuring a reproduction link), we'll close them. That's not because we don't care! At any point, feel free to comment with a reproduction and we'll reopen it. ### How can I create a reproduction? We have a couple of templates for starting with a minimal reproduction: 👉 [Reproduction starter (v8 and higher)](https://stackblitz.com/fork/github/BobbieGoede/nuxt-i18n-starter/tree/v8) 👉 [Reproduction starter (edge)](https://stackblitz.com/fork/github/BobbieGoede/nuxt-i18n-starter/tree/edge) A public GitHub repository is also perfect. 👌 Please ensure that the reproduction is as **minimal** as possible. See more details [in our guide](https://nuxt.com/docs/community/reporting-bugs/#create-a-minimal-reproduction). You might also find these other articles interesting and/or helpful: - [The Importance of Reproductions](https://antfu.me/posts/why-reproductions-are-required) - [How to Generate a Minimal, Complete, and Verifiable Example](https://stackoverflow.com/help/mcve)

nuxt-modules / i18n