Pooya Parsa

Hi @layerzzzio. The latest version of nuxthub/core should leverage nitro 2.11 hybrid polyfills. So if you are still having this issue, would you mind to open an issue in hub...

You can check [Nitro 2.11](https://github.com/nitrojs/nitro/releases/tag/v2.11.0) release notes for Enabling Node.js compatibility. ```js // Nitro export default defineNitroConfig({ compatibilityDate: "2025-03-01", cloudflare: { nodeCompat: true, deployConfig: true } }); // Nuxt export...

Thanks for preparing PR. I might need time to locally test everything before merge and release of it but current implementation looks good 👍🏼

Are you force resolving unenv to nighyly version in your Nitro project?

You have mentioned `unenv-nightly version 1.10.0-1717606461.a117952` how it is there? Can you please share `npm why unenv` / `pnpm why unenv` (depending on your package manager)

Thanks for report dear @jvbianchi As you have already figured out, adding latest (`1.9.x`) version of unenv to your main project `dependencies`, `devDependencies` (or `resolutions` if those won't work will...

The issue is resolved by #261 technically but due to hosting issues, nightly/wrong version of unenv might be picked for Nuxt/Nitro. In this case, please add `unenv@^1` dependency to your...

Thanks for reviewing! I will probably introduce change as v2 beta tag and backport later to v1 if we haven’t seen any issues in wild (however thinking more could be...

Good point for deduplicate let me see if can fit it in (it is so common and worth to test for v2, we add nested node_modules as search path, only...

Node.js ESM `resolve` requires that Windows absolute paths (same limit of `imports`) have file proto. I think for `resolvePathSync` wrapper we could identify windows absolute paths and do renormalization to...