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
I'm running injectManifest in development mode, but it's erroring out:
The swSrc file refers to a sourcemap that can't be opened: ENOENT: no such file or directory, open 'D:\a_work\1\s\CacheStatus.js.map'
I checked the swSrc file and the first sourcemap is indeed //# sourceMappingURL=CacheStatus.js.map . However the file being injected is output to a folder without the sourcemaps beside them. This was working fine in v4, but is broken in v6. Can we update the behavior to ignore the invalid sourcemap and continue with the manifest injection? Or add an option to do so?
I'm not entirely sure why that logic would have changed between v4 and v6, but if you have a development set up that's broken by this exception, I think we can "demote" it to be a warning instead.
Library Affected:
workbox-build
Browser & Platform:
all browsers
Issue or Feature Request Description:
I'm running injectManifest in development mode, but it's erroring out:
I checked the swSrc file and the first sourcemap is indeed
//# sourceMappingURL=CacheStatus.js.map
. However the file being injected is output to a folder without the sourcemaps beside them. This was working fine in v4, but is broken in v6. Can we update the behavior to ignore the invalid sourcemap and continue with the manifest injection? Or add an option to do so?workbox/packages/workbox-build/src/inject-manifest.ts
Line 185 in 8afb372
The text was updated successfully, but these errors were encountered: