Pooya Parsa
Pooya Parsa
Thanks for helping and upstream issue report dear @max06 I have pushed a `.devcontainer` setup to this repository. (https://github.com/nuxt/cli/commit/b8f9fd3a0c1ace6c3f548cc8a92d76f4be0eb43d). After cloning repo, you can reopen it in dev container and...
> I reported the https://github.com/microsoft/vscode/issues/191945 a while ago and it was already fixed. This shouldn't matter anymore at least for vscode features. Thanks for the previous reports and references it...
Thanks. Have to locally doublecheck but this seems a nice fix. (for context, addition was from https://github.com/nuxt/nuxt/pull/18882)
Thanks for the issue. I will be working on a quick solution to make it working again on nuxi 3.7 👍🏼
host issue is fixed already in latest 3.7.2 cli release. Can you please confirm that? 🙏
@jktantan I meant the host. WebSocket issue is not resolved yet.
With #127 ([v3.7.3](https://github.com/nuxt/cli/releases/tag/v3.7.3)), you can hook into the `listen` event to register a custom ws handler. Check out [this example](https://github.com/nuxt/cli/blob/main/playground/modules/ws.ts) for usage. Will be working on some upstream (nitro) fixes...
If modules expect them as peer, maybe we can ensure via an nypm to install peer deps? (npm does but it is implicit behavior)
Can you share more context in what common usecases this might be useful to use something different from `NODE_ENV`?
> In addition to @fmoessle's comment, build sets the NODE_ENV always to production, leaving no room for further options. This is a bug we might try to fix first.