Heb

I absolutely agree it makes sense to not have to rely on these. I like `import.meta.*`, but I also worry that there's no standard and that library authors are starting...

> @daniluk4000 (or anyone else) if you are facing issues like `Cannot use import.* outside a module`, please share a reproduction. If any issues in tool chain that lack its...

> There are two parts to this: > > ## Better UI (Interactive) > An (interactive) new error page similar to youch. I prefer if we can rewrite it because...

This looks promising. Here's my personal 2 cents for "server components". _Disclaimer: I think this name in general is extremely confusing, due to the fact that it's already complicated to...

> I agree with @HendrikJan - His solution would be ideal for my use case. My main issue with `component.server.vue` is that I would still need multiple files, I would...

@tinawng @WolfVector There's a fix available [here](https://github.com/unjs/nitro/pull/1115/files), it will be applied in future versions of Nitro. In the meantime you can manually fix it by writing a pnpm patch for...

@danielroe just re-opened https://github.com/unjs/nitro/issues/1338 for upstream tracking

This is a tricky issue to fix because Nuxt relies on a flat module structure to work. Ie by installing Nuxt, you should be able to `import { ref }...

@danielroe tracked upstream there https://github.com/unjs/nitro/issues/628 documentation request with instructions upstream https://github.com/unjs/nitro/issues/1370

It would be great if we could provide code documentation for everything that ends up being auto-imported and available in userland (as well as a link towards the actual docs)....