Issue: dependency could not be resolved
See original GitHub issueLibrary Affected: workbox-webpack-plugin.
Issue or Feature Request Description: In developement build, with workbox-webpack-plugin version 5.0.0 and upwards, i get the following log in the console.
'workbox-core/registerQuotaErrorCallback.js' is imported by node_modules/workbox-expiration/ExpirationPlugin.js, but could not be resolved β treating it as an external dependency
'workbox-core/_private/assert.js' is imported by node_modules/workbox-routing/NavigationRoute.js, but could not be resolved β treating it as an external dependency
'workbox-core/_private/assert.js' is imported by node_modules/workbox-expiration/ExpirationPlugin.js, but could not be resolved β treating it as an external dependency
'workbox-core/_private/assert.js' is imported by node_modules/workbox-strategies/NetworkFirst.js, but could not be resolved β treating it as an external dependency
'workbox-core/_private/assert.js' is imported by node_modules/workbox-strategies/StaleWhileRevalidate.js, but could not be resolved β treating it as an external dependency
'workbox-core/_private/logger.js' is imported by node_modules/workbox-routing/NavigationRoute.js, but could not be resolved β treating it as an external dependency
'workbox-core/_private/logger.js' is imported by node_modules/workbox-routing/registerRoute.js, but could not be resolved β treating it as an external dependency
'workbox-core/_private/logger.js' is imported by node_modules/workbox-expiration/ExpirationPlugin.js, but could not be resolved β treating it as an external dependency
'workbox-core/_private/logger.js' is imported by node_modules/workbox-strategies/NetworkFirst.js, but could not be resolved β treating it as an external dependency
'workbox-core/_private/logger.js' is imported by node_modules/workbox-strategies/StaleWhileRevalidate.js, but could not be resolved β treating it as an external dependency
'workbox-core/_private/logger.js' is imported by node_modules/workbox-navigation-preload/enable.js, but could not be resolved β treating it as an external dependency
'workbox-core/_private/logger.js' is imported by node_modules/workbox-precaching/cleanupOutdatedCaches.js, but could not be resolved β treating it as an external dependency
'workbox-core/_private/WorkboxError.js' is imported by node_modules/workbox-routing/registerRoute.js, but could not be resolved β treating it as an external dependency
'workbox-core/_private/WorkboxError.js' is imported by node_modules/workbox-expiration/ExpirationPlugin.js, but could not be resolved β treating it as an external dependency
'workbox-core/_private/WorkboxError.js' is imported by node_modules/workbox-strategies/NetworkFirst.js, but could not be resolved β treating it as an external dependency
'workbox-core/_private/WorkboxError.js' is imported by node_modules/workbox-strategies/StaleWhileRevalidate.js, but could not be resolved β treating it as an external dependency
'workbox-core/_private/cacheNames.js' is imported by node_modules/workbox-expiration/ExpirationPlugin.js, but could not be resolved β treating it as an external dependency
'workbox-core/_private/cacheNames.js' is imported by node_modules/workbox-strategies/NetworkFirst.js, but could not be resolved β treating it as an external dependency
'workbox-core/_private/cacheNames.js' is imported by node_modules/workbox-strategies/StaleWhileRevalidate.js, but could not be resolved β treating it as an external dependency
'workbox-core/_private/cacheNames.js' is imported by node_modules/workbox-precaching/cleanupOutdatedCaches.js, but could not be resolved β treating it as an external dependency
'workbox-core/_private/dontWaitFor.js' is imported by node_modules/workbox-expiration/ExpirationPlugin.js, but could not be resolved β treating it as an external dependency
'workbox-core/_private/getFriendlyURL.js' is imported by node_modules/workbox-expiration/ExpirationPlugin.js, but could not be resolved β treating it as an external dependency
'workbox-core/_private/getFriendlyURL.js' is imported by node_modules/workbox-strategies/NetworkFirst.js, but could not be resolved β treating it as an external dependency
'workbox-core/_private/getFriendlyURL.js' is imported by node_modules/workbox-strategies/StaleWhileRevalidate.js, but could not be resolved β treating it as an external dependency
'workbox-core/_private/cacheWrapper.js' is imported by node_modules/workbox-strategies/NetworkFirst.js, but could not be resolved β treating it as an external dependency
'workbox-core/_private/cacheWrapper.js' is imported by node_modules/workbox-strategies/StaleWhileRevalidate.js, but could not be resolved β treating it as an external dependency
'workbox-core/_private/fetchWrapper.js' is imported by node_modules/workbox-strategies/NetworkFirst.js, but could not be resolved β treating it as an external dependency
'workbox-core/_private/fetchWrapper.js' is imported by node_modules/workbox-strategies/StaleWhileRevalidate.js, but could not be resolved β treating it as an external dependency
'workbox-core/_private/assert.js' is imported by node_modules/workbox-routing/Route.js, but could not be resolved β treating it as an external dependency
'workbox-core/_private/assert.js' is imported by node_modules/workbox-routing/RegExpRoute.js, but could not be resolved β treating it as an external dependency
'workbox-core/_private/logger.js' is imported by node_modules/workbox-routing/RegExpRoute.js, but could not be resolved β treating it as an external dependency
'workbox-core/_private/assert.js' is imported by node_modules/workbox-expiration/CacheExpiration.js, but could not be resolved β treating it as an external dependency
'workbox-core/_private/dontWaitFor.js' is imported by node_modules/workbox-expiration/CacheExpiration.js, but could not be resolved β treating it as an external dependency
'workbox-core/_private/logger.js' is imported by node_modules/workbox-expiration/CacheExpiration.js, but could not be resolved β treating it as an external dependency
'workbox-core/_private/WorkboxError.js' is imported by node_modules/workbox-expiration/CacheExpiration.js, but could not be resolved β treating it as an external dependency
'workbox-core/_private/logger.js' is imported by node_modules/workbox-precaching/precache.js, but could not be resolved β treating it as an external dependency
'workbox-core/_private/logger.js' is imported by node_modules/workbox-strategies/utils/messages.js, but could not be resolved β treating it as an external dependency
'workbox-core/_private/getFriendlyURL.js' is imported by node_modules/workbox-strategies/utils/messages.js, but could not be resolved β treating it as an external dependency
'workbox-core/_private/assert.js' is imported by node_modules/workbox-routing/utils/normalizeHandler.js, but could not be resolved β treating it as an external dependency
'workbox-core/_private/assert.js' is imported by node_modules/workbox-routing/Router.js, but could not be resolved β treating it as an external dependency
'workbox-core/_private/logger.js' is imported by node_modules/workbox-routing/Router.js, but could not be resolved β treating it as an external dependency
'workbox-core/_private/WorkboxError.js' is imported by node_modules/workbox-routing/Router.js, but could not be resolved β treating it as an external dependency
'workbox-core/_private/getFriendlyURL.js' is imported by node_modules/workbox-routing/Router.js, but could not be resolved β treating it as an external dependency
'workbox-core/_private/cacheNames.js' is imported by node_modules/workbox-precaching/utils/addFetchListener.js, but could not be resolved β treating it as an external dependency
'workbox-core/_private/getFriendlyURL.js' is imported by node_modules/workbox-precaching/utils/addFetchListener.js, but could not be resolved β treating it as an external dependency
'workbox-core/_private/logger.js' is imported by node_modules/workbox-precaching/utils/addFetchListener.js, but could not be resolved β treating it as an external dependency
'workbox-core/_private/assert.js' is imported by node_modules/workbox-precaching/PrecacheController.js, but could not be resolved β treating it as an external dependency
'workbox-core/_private/cacheNames.js' is imported by node_modules/workbox-precaching/PrecacheController.js, but could not be resolved β treating it as an external dependency
'workbox-core/_private/cacheWrapper.js' is imported by node_modules/workbox-precaching/PrecacheController.js, but could not be resolved β treating it as an external dependency
'workbox-core/_private/fetchWrapper.js' is imported by node_modules/workbox-precaching/PrecacheController.js, but could not be resolved β treating it as an external dependency
'workbox-core/_private/logger.js' is imported by node_modules/workbox-precaching/PrecacheController.js, but could not be resolved β treating it as an external dependency
'workbox-core/_private/WorkboxError.js' is imported by node_modules/workbox-precaching/PrecacheController.js, but could not be resolved β treating it as an external dependency
'workbox-core/_private/DBWrapper.js' is imported by node_modules/workbox-expiration/models/CacheTimestampsModel.js, but could not be resolved β treating it as an external dependency
'workbox-core/_private/deleteDatabase.js' is imported by node_modules/workbox-expiration/models/CacheTimestampsModel.js, but could not be resolved β treating it as an external dependency
'workbox-core/copyResponse.js' is imported by node_modules/workbox-precaching/PrecacheController.js, but could not be resolved β treating it as an external dependency
'workbox-core/_private/WorkboxError.js' is imported by node_modules/workbox-precaching/utils/createCacheKey.js, but could not be resolved β treating it as an external dependency
'workbox-core/_private/logger.js' is imported by node_modules/workbox-precaching/utils/printCleanupDetails.js, but could not be resolved β treating it as an external dependency
'workbox-core/_private/logger.js' is imported by node_modules/workbox-precaching/utils/printInstallDetails.js, but could not be resolved β treating it as an external dependency
Issue Analytics
- State:
- Created 3 years ago
- Comments:8 (4 by maintainers)
Top Results From Across the Web
Maven Could not resolve dependencies, artifacts could not be ...
Doing mvn dependency:tree, dependency:list, or the usual build package, will result in the same error. I've tried downloading the newest version of maven,...
Read more >How to Fix Maven Artifacts Could not be Resolved Error ...
Option-1. Just upgrade log4j and zookeeper to latest version. log4j 1.2.16 and zookeeper 3.4.9 doesn't have these dependencies. Option-Β ...
Read more >Could not resolve dependencies for project #1057 - GitHub
I'll raise this issue internally; in the meantime, you can use version 1.25.1 to build the example and that should work fine. I...
Read more >Learning the Basics - Gradle User Manual
Gradle can resolve dependencies from one or many repositories based on Maven, ... The Gradle cache does not allow the local cache to...
Read more >Frequently Encountered Pipenv Problems - Read the Docs
Please take a look below and see if they resolve your problem. Note. Make sure you're running the newest Pipenv version first! β€...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Iβm sorry, but Iβm not able to reproduce and I have not heard of others running into this problem. Without steps that you can provide for a reproduction, I donβt think thereβs anything actionable at this point, so Iβm going to close this.
We can revisit if you could provide a public reproduction.
All of those failure messages are related to
webpack
not being able to resolve theworkbox-core
module, which is a failure that Iβm not able to reproduce. I am not sure what other deprecated dependencies you might be using, but I do think that this failure is related to something about yourwebpack
build environment, as if this issue were widespread, I think we would have heard from more developers at this point.Iβm happy to keep this open to see if anyone else reports a similar failure, but Iβd recommend trying to pare down your
webpack
configuration to just the basics, and then re-add additional options until you find out what might be breaking things.