#DocumentDB impacts payload's HMR?

4 messages · Page 1 of 1 (latest)

molten scarab
#

"payload": "^1.6.32"
"nodemon": "^2.0.22",

I use documentDB. HMR doesn't work when I make changes to a collection schema.

If I switch to a local mongoDB instance, my updates are reflected (on browser refresh). If I switch back to documentDB, they're undone.

I can assume this isn't related to a cache, or if it is, its stored in the database?

To get around the issue with documentDB, I need to run yarn build. This will reflect the most recent payload changes.

Anyone have any suggestions?

sudden mauve
#

Hey @molten scarab do you still need help here?

molten scarab
#

This is still an issue. Connecting to document db locally requires an ssh tunnel and exhibits the behaviour mentioned above

violet vortex
#

@remy Hmm, this is quite puzzling to me. There isn't anything related to HMR or webpack that would differ between two different databases. Nothing related to any of that is stored in the database as the database engine doesn't really care what the current state of the DB collections are.

I'd say please make an issue ticket detailing the above steps, so we can look into it further.