问题
I am on a big project, first exposure to Meteor, and I am starting to get this very often. It will be hard to trace it back to a particular commit, as it seemed intermittent.
What is a fruitful way to approach finding the problem? Is there anything in the exception that helps narrow it down? How do I step through/set breakpoints in/rule out the Deps? All my deps are the auto ones from mongo operations, or one on a session var, nothing explicit.
Thank you
https://gist.github.com/jimmack1963/6254452
回答1:
In my experience, this usually means you have crashing code within a template. You're using {{#each on something that's not an array or object, or some other no-no. If you were actually using Deps.autorun somewhere, presumably you would see your function in the stack trace; but if the trace is just a list of core Meteor functions, that means the problem is likely in a template or one of its helpers.
回答2:
This was pretty helpful to anyone else getting this.
http://www.meteorpedia.com/read/TypeError_-_Cannot_read_property_nodeName_of_null
来源：https://stackoverflow.com/questions/18283607/how-to-investigate-exception-form-deps-recompute-what-are-the-clues