ServerMiddleware hot reload is faulty

[AregGhazaryan]

Versions

• nuxt: 2.15.3
• node: 14.16.0

Reproduction

https://github.com/AregGhazaryan/nuxt-mongoose-server-middleware-reprod

Steps to reproduce

1. npm i
2. npm run dev
3. go to /api/index.js and hit save
4. voila error

What is Expected?

Server middleware should reload with latest changes without throwing errors.

What is actually happening?

The entire server middleware re-instantiates including, classes, functions and other resources. I can assure you that issue is not only mongoose related, because once i even had a telegram bot connected to my application which threw similar errors, like two instances are being run instead of just one.

[AregGhazaryan]

Here's also the telegram bot error when saving server middleware

[stale]

Thanks for your contribution to Nuxt!
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.
If you would like this issue to remain open:

1. Verify that you can still reproduce the issue in the latest version of nuxt-edge
2. Comment the steps to reproduce it

Issues that are labeled as pending will not be automatically marked as stale.

[AregGhazaryan]

No, bad bot

[Susccy]

I have the same problem currently and it makes developing a Mongoose backend very unpleasant. I have to manually exit and restart Nuxt everytime I make a change in any server file.
Neither the supposed fix in release v2.14.4 nor the workaround using require() suggested by @pi0 in #7917 solved it for me.

[Atinux]

We are aware of this issue and it's not that easy to fix. We have a solution coming with the Nuxt Nitro module. will keep this issue updated.

[TomBell95]

Hi, I am now experiencing the same problem as mentioned by @Susccy & @AregGhazaryan - I have tried the workaround in #7917 which has not worked as well as upgrading to Nuxt 2.15.8.

@Susccy Did you manage to fix this? I am also having to manually refresh my Mongoose backend everytime.

Is there any update on this please? Thanks.

[Susccy]

@TomBell95 The following workaround makes hot reloading possible in my current mongoose project. Keep in mind you'll have to restart the app every time you make changes to the model.

// movie.model.js

import { Schema, models, model } from "mongoose"

const movieSchema = new Schema({
  // ...
})

// Try to use the existing model if it's been created before.
// Used to suppress a mongoose error on nuxt hot reload.
export default models.Movie || model("Movie", movieSchema)

[TomBell95]

@Susccy Brilliants, thanks.

[stale]

Thanks for your contribution to Nuxt!
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.
If you would like this issue to remain open:

1. Verify that you can still reproduce the issue in the latest version of nuxt-edge
2. Comment the steps to reproduce it

Issues that are labeled as pending will not be automatically marked as stale.