You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi! I am running latest version (1.3.7) and I am getting this error in Sentry (242 Events and 76 Users affected). I have a SPA Vite (no SSR). Pretty simple, I have the vite-plugin-pwa using a simple sw too.
I couldn't reproduce it locally, but I think it's only on the production bundle, if it's kinda related to #44, I just post my build config from vite.config file
I've been seeing similar messages on my side as well, but have been preoccupied. I believe this has to do with the functionality of the new and more difficult-to-evade way of detecting browser engines not accounting for old versions of browsers, particularly Safari, where either the error message of Number.prototype.toFixed is different, or where Number.prototype.toFixed is not supported. I've been considering bringing back the eval.toString() method to account for instances where Number.prototype.toFixed is not supported. Again, don't have time at the moment, but if anyone wished to investigate further & submit a PR, feel free to do so!
Same issue, during the eval() under strict security context policy.
VM248:1 Uncaught EvalError: Refused to evaluate a string as JavaScript
because 'unsafe-eval' is not an allowed source of script in the following
Content Security Policy directive: "script-src 'self' _WEBSITE.COM_
https://code.jquery.com https://stackpath.bootstrapcdn.com 'unsafe-inline' _REDACTED_".
at <anonymous>:1:1
(anonymous) @ VM248:1
Hi! I am running latest version (1.3.7) and I am getting this error in Sentry (242 Events and 76 Users affected). I have a SPA Vite (no SSR). Pretty simple, I have the vite-plugin-pwa using a simple sw too.
I couldn't reproduce it locally, but I think it's only on the production bundle, if it's kinda related to #44, I just post my build config from vite.config file
Any ideas?
The text was updated successfully, but these errors were encountered: