Kricsleo

Upstream issue: https://github.com/unjs/untyped/issues/159

Awaiting https://github.com/unjs/untyped/pull/162

Sorry, please provide a minimal reproduction so that we can debug.

> console.creatdTask does not exist in this runtime and leads to errors `hookable` inherently includes compatibility judgment, so theoretically it shouldn't be because of this. https://github.com/unjs/hookable/blob/a45a54c3ffd2dfcfa4dd053030547c78aca7460d/src/utils.ts#L64-L65

The `serialport` cannot work in worker threads, as reported here: https://github.com/serialport/node-serialport/issues/2748 > We might support alternative runner for Nitro dev server (to use full Node.js process which is slower) in...

I ran your reproduction repo, but still don't get what you mean. Could you explain the issue in more detail? 🙏

You mean this gap? I think this is the `gap-y-8`.

Now I got it. TL;DR: `` is supposed to work with ``. `` does have the same default collision padding for both [`position="popper"`](https://github.com/unovue/reka-ui/blob/v2/packages/core/src/Select/SelectPopperPosition.vue#L14) and [`position="item-aligned"`](https://github.com/unovue/reka-ui/blob/v2/packages/core/src/Select/SelectItemAlignedPosition.vue#L75), but they work differently underneath....

You should use `null` as the default state in this condition. (There's a difference between `null` and `undefined` as initial values in `reka-ui`.)

This is because `Vite` [intercepts `OPTIONS` requests by default](https://github.com/vitejs/vite/blob/bb85bd751e4568c707612b708deaba67f8af4ca3/packages/vite/src/node/server/index.ts#L1088) during `dev` (not after `build`), before `Nitro` can handle the request. If you disable `Vite`'s default behavior by setting [`server.cors: false`](https://vite.dev/config/server-options.html#server-cors),...