Pooya Parsa

NP @jonschlinkert. Sure will update branch 😊

I would also strongly recommend depending on two `development` and `production` values for NODE_ENV. There is no standard that tells not to use other values but there were strong reasons...

Hi. I think it is a nice idea. I think we can move it forward in two directions: 1) A new `app-test` template in [nuxt/starter](https://github.com/nuxt/starter) that can initialize `/test` directory....

> I am not super familiar with the starter templates, but will this allow for a wizard-like approach like asking for a playwright, etc, or can this only create a...

By any chance are you using an endpoint with `DELETE` method? (because it is a [known issue](https://github.com/unjs/httpxy/issues/7) -- however not new one)

Yes, docker env / devcontainer is even better!

Thanks! yes I can reproduce it. Seems coming from the vite handler. ``` GET http://127.0.0.1:3000/_nuxt/node_modules/.cache/vite/client/deps/vue-router.js?v=38dcfad8 net::ERR_CONTENT_LENGTH_MISMATCH 200 (OK) ``` CLI warning might be related: ``` [Vue Router warn]: No match...

Hi again. Sorry hearing you still have issues with DevContainers. It is something we should investigate and fix for CLI proxy. In the meantime, have you tried with `nuxt dev...

@ddahan See https://github.com/nuxt/cli/issues/181#issuecomment-1719072945 -- After disabling cache issue seems to be solved.

> It just creates another error: [GET] "http://[::]:3000/__nuxt_vite_node__/manifest": fetch failed @ddahan It seems another issue with DevContainers reporting IPv6 as a listener (`{ address: '::', family: 'IPv6', port: 3000 }`)...