-
Notifications
You must be signed in to change notification settings - Fork 110
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
Use workbox precache manifest output #49
Comments
Sounds good to me! |
Moreover, I'm wondering if we should really override the revision with Next's buildId. I believe the revision is the file's content hash. Thus, if the file didn't change between builds we shouldn't set another revision, as the file will already be cached. |
Good catch @joaovieira ! I can probably fix that today or this weekend unless you can beat me to it |
Nope, go ahead. I'll be on hols for the next week 😄
…On Fri, 24 Aug 2018, 17:27 Jack Hanford, ***@***.***> wrote:
Good catch! I can probably fix that today or this weekend unless you can
beat me to it
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#49 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAc96_X_KOj5uvmztf6ubh-4d29p_wG6ks5uUClmgaJpZM4WLLU5>
.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
While digging in I found out that
workbox-webpack-plugin
limits all of the "transform" options to theglobPattern
files only. I.e. don't runmodifyUrlPrefix
on webpack-generated assets, for example. See whole explanation here.I then found out this will be available in
workbox-webpack-plugin
v4: GoogleChrome/workbox#1591We can still do all of that work manually:
precache-manifest.*.js
modifyUrlPrefix
according to the existingexportPathMap
build-manifest.json
)I'd be ok to wait for v4, given the current version is working fine. Reading from the generated precache manifest is just a more accurate process.
The text was updated successfully, but these errors were encountered: