Path to appcache/sw.js

I am probably missing something but I can’t get to find how to configure the path to the appcache directory and sw.js file.

I have an express application serving assets at /assets so the current structure looks like:

/assets
  /appcache
    /manifest.appcache
    /manifest.html
  /js
    /app.js
    /sw.js

The problem is that the runtime installation tries to fetch the manifest from /appcache/manifest.html instead of /assets/appcache/manifest.html. I tried to play around with publicPath but didn’t see any effects, same for relativePaths. I tried to pass options to the runtime function but after digging the code, seems like it’s completely ignored.

Is there a way to configure the appcache and sw.js path? Must it be located at the root?

[NekR]

Oh, there seems be a lot of typos in my previous comments. Just fixed them.

Maybe relativePaths should be ignored if there’s a publicPath provided (as it can only be intentional since there’s no default value) but really, that one is on me 😃

Yeah, it was this way in v2 when publicPath was called scope (don’t ask why 😃) and I changed behavior in v3, also no idea why, it just happened.

I too think that it makes sense to revert to v2 behavior for relativePaths and publicPath, but I can do it only for v4 because I don’t want break people who uses v3. Semver, etc.

[zhouzi]

That’s totally my fault. There’s often so much warnings when building a webpack project that I’m no more reading them. I read the documentation and seen the mention of the incompatibility of publicPath/relativePaths but didn’t pay attention to the fact that relativePaths is true by default and therefore disables publicPath. Maybe relativePaths should be ignored if there’s a publicPath provided (as it can only be intentional since there’s no default value) but really, that one is on me 😃

Thanks for your kind support 👍