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, this is probably a bug somewhere in workbox or VitePWA, would you mind opening an issue in their respective repositories?
You can point them to this comment. My suspicion here is that they are trying to resolve or rewrite the virtual module which they should generally not do since it starts with a null bye \0. This is a convention in rollup/vite that everybody building plugins should adhere to.
Ideally you also share your build logs in case there are any warnings or similar!
Here's what my generated service worker looks like:
/**
* Copyright 2018 Google Inc. All Rights Reserved.
* Licensed under the Apache License, Version 2.0 (the "License");
* you may not use this file except in compliance with the License.
* You may obtain a copy of the License at
* http://www.apache.org/licenses/LICENSE-2.0
* Unless required by applicable law or agreed to in writing, software
* distributed under the License is distributed on an "AS IS" BASIS,
* WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
* See the License for the specific language governing permissions and
* limitations under the License.
*/
// If the loader is already loaded, just stop.
if (!self.define) {
let registry = {};
// Used for `eval` and `importScripts` where we can't get script URL by other means.
// In both cases, it's safe to use a global var because those functions are synchronous.
let nextDefineUri;
const singleRequire = (uri,parentUri)=>{
uri = new URL(uri + ".js",parentUri).href;
return registry[uri] || (
new Promise(resolve=>{
if ("document"in self) {
const script = document.createElement("script");
script.src = uri;
script.onload = resolve;
document.head.appendChild(script);
} else {
nextDefineUri = uri;
importScripts(uri);
resolve();
}
}
)
.then(()=>{
let promise = registry[uri];
if (!promise) {
throw new Error(`Module ${uri} didn’t register its module`);
}
return promise;
}
));
}
;
self.define = (depsNames,factory)=>{
const uri = nextDefineUri || ("document"in self ? document.currentScript.src : "") || location.href;
if (registry[uri]) {
// Module is already loading or loaded.
return;
}
let exports = {};
const require = depUri=>singleRequire(depUri, uri);
const specialDeps = {
module: {
uri
},
exports,
require
};
registry[uri] = Promise.all(depsNames.map(depName=>specialDeps[depName] || require(depName))).then(deps=>{
factory(...deps);
return exports;
}
);
}
;
}
define(['./workbox-ffaa3760'], (function(workbox) {
'use strict';
self.addEventListener('message', event=>{
if (event.data && event.data.type === 'SKIP_WAITING') {
self.skipWaiting();
}
}
);
/**
* The precacheAndRoute() method efficiently caches and responds to
* requests for URLs in the manifest.
* See https://goo.gl/S9QRab
*/
workbox.precacheAndRoute([{
"url": "/",
"revision": "0.ia2na8sk9i"
}], {});
workbox.cleanupOutdatedCaches();
workbox.registerRoute(new workbox.NavigationRoute(workbox.createHandlerBoundToURL("/"),{
allowlist: [/^\/$/]
}));
}
));
//# sourceMappingURL=sw.js.map
;import "/_nuxt/@id/__x00__sentry-release-injection-file";
The last line ;import "/_nuxt/@id/__x00__sentry-release-injection-file"; is causing the error:
And idea on how we can get vite-pwa to work with Sentry Vite plugin?
The text was updated successfully, but these errors were encountered:
getsentry/sentry-javascript-bundler-plugins#460
@ArnauKokoro posted this issue in the getsentry/sentry-javascript-bundler-plugins repo.
Within this issue @iforst writes the following:
getsentry/sentry-javascript-bundler-plugins#460 (comment)
Here's what my generated service worker looks like:
The last line
;import "/_nuxt/@id/__x00__sentry-release-injection-file";
is causing the error:And idea on how we can get vite-pwa to work with Sentry Vite plugin?
The text was updated successfully, but these errors were encountered: