Dan Ristea
Dan Ristea
Yes, I'd like to know if it was blocked by an ad blocker. Particularly, if a script was added to pathsNotFound by the logic here https://github.com/muicss/loadjs/blob/master/src/loadjs.js#L166.
OK, I see. I did look at that issue before posting but didn't know you were looking to remove the detection. Has there been any additional testing to verify that...
Sorry, I don't know of any off the top of my head.
I might have a play with different adblockers and browsers when I get some time, and report back with any findings.
I tested uBlock, Adblock, Adblock Plus, and Ghostery on Chrome, Firefox, and Safari (all on Mac). Only Safari triggered the `beforeload` event with `defaultPrevented` and it did it for all...
I've not seen the issue described in #47. Loadjs always fired the correct success/error callback in my tests.
OK, I understand, so it's the correct exception, hence the `{ diagnosticCodes: [ 2345 ] }` output but the `diagnosticText` is being lost in the serialisation of the exception. I...
@cspotcode serialisation has been fixed in the nightly version of Node. The problem is that `internalBinding('errors').triggerUncaughtException(` ignores `Symbol(nodejs.util.inspect.custom)` but with `process.setUncaughtExceptionCaptureCallback(console.error)` the type error info is shown again in the...
@cspotcode Node 20.4 is out now with the serialisation fix in place. Could you please release a new version of `ts-node` so it can be used like this? ```js //logError.js...