Home > database >  How can I resolve the Chrome warning: The deferred DOM Node could not be resolved to a valid node
How can I resolve the Chrome warning: The deferred DOM Node could not be resolved to a valid node

Time:06-22

I'm running a node.js project on a localhost server, and I've been doing this for months without seeing this, but recently, I've been getting this warning when I open the inspector:

The deferred DOM Node could not be resolved to a valid node.

I usually go into the inspector on an element to check out some attribute, eventListener, or other info, but this warning is popping up and it doesn't take me to the element. It's been pretty annoying, and I don't really know why it started showing up or how to get rid of it. My only clue is that I was changing some initialization settings for my express sessions around the same time this appeared, but I'm not sure that this is related.

Has anyone else run into this before? How do you get rid of the warning? Thanks!

CodePudding user response:

That might be due to a chrome extension interfering. Make sure you test in an environment with no extensions

  • Related