Bjorn Lu

Thanks! Yeah it doesn't handle `null` well yet, so this is a bug 👍

I think it could be interesting if included in core, but perhaps at a later time once I finished building a plugin API so it can be experimented as a...

> A workaround is to update `rollupOptions.external` to include the `"events"` library (and also `"node:events"`). This isn't ideal considering there are many core Node.js modules, thus it'd be better to...

> It would make sense to determine if there are any other things that are Node-specific that Vite currently doesn't handle properly such as `process.env` to help spec out what...

Note: I found another case where `nodeXX` is used for `build.target` (https://github.com/sveltejs/kit/pull/4742). SvelteKit's using in with the `ssr` config too so it makes sense. Using `build.target: "nodeXX"` only still seems...

The gist of the discussion so far is that there's a need for: 1. An easy way to build nodejs apps 2. An easy way to build nodejs libraries no2...

Perhaps it's possible in the inspect state to mark all disabled elements with `pointer-events: none` so that the click passes through and hits the parent element?

The compiled output seems to be incorrect where the body is not rendered: ```js // ... return $$render` document ${$$renderHead($$result)} ${$$renderSlot($$result,$$slots["default"])} `; }, '', undefined); // ... ```

Can you provide a repro showing that it's not working? It seems to be working for me ([stackblitz](https://stackblitz.com/edit/github-94pv4g?file=src%2Fpages%2Findex.astro&on=stackblitz)). Maybe https://live-astro-compiler.vercel.app can help you visualize how the `await` gets evaluated.

Looks like the problem is that you can't use `set:html={await ...}` in a `Fragment` (or any component), because it generates code like: ```js `${$$renderComponent($$result,'Fragment',Fragment,{},{"default": () => $$render`${$$unescapeHTML(await value)}`,})}` ``` Maybe...