polyfill.js | js application that serves the polyfill.js client | Runtime Evironment library

Thanks to user14649759's tip, I was able to solve the problem! :)

Webpack 5 must be used. To achieve this, I have made the following changes:

(I think you have a larger question as to whether the approach you describe is actually going to give a good, predictable, offline-capable experience for your users, but I'm just going to focus on the actual technical question you asked.)

First off, you should keep in mind that it's possible to have multiple tabs open for the same URL, and if you, you're going to end up with your update code potentially running multiple times. The code in this answer handles the "reload" step for you from inside of the service worker, after the asynchronous cache update has completed, by getting a list of all the active clients of the service worker and telling each to navigate to the current URL (which is effectively a reload).

I highly recommend you to use Workbox for ServiceWorker code. In your case revision would help. More info here: https://developers.google.com/web/tools/workbox/modules/workbox-precaching

Well i solved this by adding data to localStorage:

as @Kaiido point out, the polyfill only patched new URL() and new URLSearchParams() usage, but not URL.createObjectURL, so this won't solve the problem.

URL.createObjectURL polyfill seems hard to patch in Node.js, as the output url is supposed to be consumed by other Web APIs. There is not much related npm packages.

A way to use full Web API in Node.js may be just use puppeteer or similar headless Browser, and run your Web part of code inside. Or try Electron which allow some context mix between Node.js and Web.

From the code: https://github.com/lifaon74/url-polyfill/blob/34122120/url-polyfill.js#L464

Seems like this is a webpacked polyfill for Node.js, and you should just do:

You are getting: You are passing empty value to the q param, the exception happens because it is like calling: $query = $builder->like('titulo', null), this cannot happen, only strings are accepted as the second parameter for the like method.

To solve this, validate your parameter before using it:

Angular always includes the polyfills-es5.js file if your build target is ES5, which makes your Angular app compatible with browsers as old as IE11 (at least an empty app).

If your own code makes uses of ES6+ features that are not included in Angular's polyfills, you have to add them in the dedicated polyfills.ts file of your project which will output the polyfill.js file

The issue turned out to be related to the css styling that was being applied to the canvas portion of my site that was loading the labeling tools.

The reason why the error was so nebulous was because I was loading one entire page via AJAX, scripts included (I initially did this years ago before I knew better). I changed this and after a few days, I got a different error but with some of the same offending lines numbers.