We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Hi,
I'm getting following error while trying to integrate swpreacache plugin.
ERROR in .//sw-precache-webpack-plugin/lib/index.js Module not found: Error: Can't resolve 'fs' in '/home/rohitn/dbs/node_modules/sw-precache-webpack-plugin/lib' @ .//sw-precache-webpack-plugin/lib/index.js 27:10-23 @ ./nuxt.config.js @ ./plugins/axios.js @ .//babel-loader/lib?{"presets":["vue-app"],"cacheDirectory":false}!.//vue-loader/lib/selector.js?type=script&index=0!./pages/index.vue @ ./pages/index.vue @ ./.nuxt/router.js @ ./.nuxt/index.js @ ./.nuxt/client.js
Any idea what such error mean?
The text was updated successfully, but these errors were encountered:
why are parts crossed out?
Looks like an issue with fs not being resolved. It's a core nodejs module so I'm not sure why it's not being resolved.
fs
Sorry, something went wrong.
If thats's the issue, it might be resolved when #63 is merged. It removes the fs dependency
try:
"browser": { "fs": false }
or see: pugjs/pug-loader#8 (comment)
No branches or pull requests
Hi,
I'm getting following error while trying to integrate swpreacache plugin.
ERROR in ./
/sw-precache-webpack-plugin/lib/index.js/sw-precache-webpack-plugin/lib/index.js 27:10-23Module not found: Error: Can't resolve 'fs' in '/home/rohitn/dbs/node_modules/sw-precache-webpack-plugin/lib'
@ ./
@ ./nuxt.config.js
@ ./plugins/axios.js
@ ./
/babel-loader/lib?{"presets":["vue-app"],"cacheDirectory":false}!.//vue-loader/lib/selector.js?type=script&index=0!./pages/index.vue@ ./pages/index.vue
@ ./.nuxt/router.js
@ ./.nuxt/index.js
@ ./.nuxt/client.js
Any idea what such error mean?
The text was updated successfully, but these errors were encountered: