Ivan Nikulin
Nice find, thanks!
But, I've just remembered that it's an intended behavior. If you have a callsite record for unreadable source IMHO it's an exceptional situation. Do you have any ideas how it's...
> Any node.js internal will not be able to be resolved by path. Yes and we can't do anything with it. > I think we should check if it exists,...
I believe there shouldn't be a problem in making this module work in browser. Thus, we already use [error-stack-parser](https://www.npmjs.com/package/error-stack-parser) that supports all major browsers to create callsites for errors. Unfortunately,...
@lalarsson Hi, yes due to API changes it's not compatible with gulp 4 at the moment. I don't have any plans switching to v4 for now, therefore I'm not sure...
@Boscop via `Shutdown` opcode. It seems like it's already implemented, so this issue can be closed.
@seanmonstar jfyi https://early-hints.fastlylabs.com/ Currently hyper just breaks with 103. We would like to fix that. Any pointers?
> I think this is basically whatwg/html#804 again, for which we had #159, but that didn't cover everything that was identified there. Correct. Though, at the time of testing only...
It's impossible to implement it in jsdom currently, because it requires layouting.
From the spec it's seems like we can't implement `innerText` properly without basic layout support.