-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot read properties of undefined (reading 'terminate') #19
Comments
What kind of bundler/build setup are you using? The stack trace implies that there may be some stuff going on that isn't coming from this lib, but probably zone.js. Sooo... Angular? What does your |
The only way that I can think of that this could happen is that if this line in index.js throws worker = new Worker(new URL('./xmllint-browser.mjs', import.meta.url), { type: 'module' }); Then Until the error handling problem is fixed, I recommend you open the index-browser.mjs file under node_modules, and try removing this line .finally(() => worker.terminate()); That won't fix the actual issue, but it will fix the poor error message and might give us better hint on why the worker can't be initialized. |
Yeah, indeed. I'm using Angular (16.2.1); |
Related to #19, this "fixes" an unactionable global uncaught error in case the xmllint worker could not be initialized for whatever reason. This patch should not cause runtime application code differences, because the error that this case created would've already been swallowed by the earlier error (as per how Promise.finally works on rejected Promise), but it did create a confusing error to logs / global error handler.
I have fixed the confusing |
Whenever I try the browser-version with a simple class:
I get the following error:
Is there something I need to do additionally?
The text was updated successfully, but these errors were encountered: