Alexey Sholohov

This solved the problem for me. ```js const glob = require('glob') const fs = require('fs') const replace = (path) => { try { const str = fs.readFileSync(path, 'utf-8') const regex...

I solved the problem for myself like this ```ts // plugins.d.ts import type { Device } from "@nuxtjs/device/runtime/types"; declare module '@vue/runtime-core' { interface ComponentCustomProperties { $device: Device; } } ```

Tried to downgrade Nitro to 2.9.7 in Nuxt 3.14 and the error stack appeared. UPD: Override dependency in `package.json` for `yarn` is worked for me. ``` "resolutions": { "nuxt/nitropack": "2.9.7"...

@danielroe Tell me, where is the problem, on the Nuxt or Nitropack side? Is this issue enough or do I need to create another one in the Nitro repository to...

Everything seems to be ok in Nitro... Reproduced - https://stackblitz.com/edit/github-8lb6ue6d?file=server%2Froutes%2Findex.ts,server%2Ftest.ts 

Now it's a dilemma, had to update to the latest version of nitropack due to the websockets update and now the stacktrace issue has come up again. Any news on...

> fyi, i ran into this problem on Nuxt 3.15.1 while debugging [vuejs/pinia#2872](https://github.com/vuejs/pinia/issues/2872) > > no trace was present, until I did: > > ``` > "resolutions": { > "nitropack":...

@danielroe I couldn't reproduce this bug in the `nitorpack`. Could there be a problem in some layer between `nuxt` and `ntropack`?

> It might be caused by the fact that `nuxi` forks the dev server process - you can try with `nuxi dev --no-fork` to see if that makes a difference....

@Vincentdevreede Thanks for the answer. We also came to this method and are trying to use it. But we have already encountered the fact that you need to manually register...