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
The argument 'hints' must be an array or string of format - after upgrading to rc12 - worked on rc11 #15191
Comments
this is resolved in a newer version of h3 (or by not using node 18). probably the google fonts module is pulling in an older version. you can try refreshing your lockfile or manually installing h3 yourself. |
Hm, I used I added an output of
|
Yes, it seems the issue is content, and I'm pretty sure we'll see a new release there soon. cc: @farnabaz |
Hm, it still fails with
I updated |
I've got a similar message |
The cause is described here - and should be resolved when the version of h3 in your project is updated. You can try forcibly regenerating your lockfile or installing If that doesn't work, and you have another dependency on h3, please do let me know so we can address in the downstream module/library. |
Hi @danielroe As described, here the issue is not gone after upgrading all h3-dependencies. If I am not mistaken, I am using 0.8.4 everywhere. |
@ahoiroman Can you please confirm if disabling early hints fixes the issue with RC.12? export default defineNuxtConfig({
experimental: {
writeEarlyHints: false,
}
}) |
Hi, using
solves the issue. |
@pi0 I can confirm it works |
Ah. That's a bug in Node 18 that will be resolved when nodejs/node#44874 is released. For now you will need to use the workaround @pi0 has provided. |
@danielroe I'm using Node 19.0.0 but have exactly same issue |
Should have said Node 18+ 😆 |
@danielroe since it's not available in Node 19, do you know which release will have that fix? |
Likely the next patch release of both 18/19. |
This will be resolved with Node 19.1.0 |
This has been released. 🥳 |
Does it also mean that experimental flag was set to true by default or it will remain as false? |
No, the default value has not been changed. |
Environment
Reproduction
Upgrade to nuxt3-rc12 and start app in prod mode (
npm run build && npm run start
). Error does not appear in dev mode.Describe the bug
I am getting the following error after upgrading from rc11 to rc12:
Console shows:
Additional context
nuxt.config.js
Works fine, if I don't use the google fonts module. But well - in this case my font's are not loaded correctly ;-)
Logs
No response
The text was updated successfully, but these errors were encountered: