Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

You may need an additional loader to handle the result of these loaders.

See original GitHub issue

Module parse failed: Unexpected token (3:16)
File was processed with these loaders:
 * ./node_modules/vuetify-loader/lib/loader.js
 * ./node_modules/cache-loader/dist/cjs.js
 * ./node_modules/vue-loader/lib/index.js
You may need an additional loader to handle the result of these loaders.
| 
| {
>   "requiresAuth": true
| }

Issue Analytics

State:
Created 4 years ago
Comments:7 (4 by maintainers)

Top GitHub Comments

2reactions

ktsncommented, Jan 28, 2020

The cause of this error is because there is vuetify-loader in the chain which is noop for this custom block. Then it breaks the assumption in vue-loader which is “if no loader is assigned for the custom block, then ignore it”. I had added cache-loader in the ignore list when #4 was filed to fix this issue (cache-loader was culprit at that moment), but I don’t think we can add vuetify-loader (and every possible culprit) for this error.

I’ll end up adding dummy loader in vue-cli-plugin-auto-routing to avoid this.

0reactions

ktsncommented, Mar 4, 2020

I’m not sure if we can do this but to exclude custom blocks from matching if vuetify-loader does nothing for them?