-
Notifications
You must be signed in to change notification settings - Fork 282
Question: Integration of Service Workers #311
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
Comments
Well I found that under assets you can actuall specify a worker, but doing that using the example I get the following:
|
Thank you for the hint. The example you are referring to is about "web workers" (i.e. a way to run code in a background thread). I was curious about "service workers" (i.e. a way to create an offline web app). |
Well once added you can register your sw either in js or your first wasm binary, linking to that second generated binary. In the second binary cast your scope and use web_sys ServiceWorkerGlobalScope to do what you need |
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days. |
This issue was closed because it has been stalled for 5 days with no activity. |
I am working on a PWA with offline capability. I have not found a description on how to create a service worker file using trunk. Hence, I assume that this in currently not possible. I found PR 187, which is adding some PWA properties. However, creating a service worker file seems out of scope of that PR.
I can see three possible routes to take with this:
Any thoughts on the topic? Are you interested in integrating this kind of functionality into trunk?
The text was updated successfully, but these errors were encountered: