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.

Next.js - You may need an additional loader

See original GitHub issue

Hi there! 👋 Thanks for the awesome work 👏

I’m trying to make it work with Next.js (Webpack) but I’ve an issue: You may need an additional loader to handle the result of these loaders. Do I need a Webpack loader to make it work?

Reproduction repo: https://github.com/FabienMotte/unplugin-icons-nextjs-issue

Thank you!

Issue Analytics

State:
Created 2 years ago
Comments:5 (2 by maintainers)

Top GitHub Comments

1reaction

antfucommented, Sep 11, 2021

With v0.8.0 now you can set the extension by:

IconResolver({
  prefix: 'Icons',
  extension: 'jsx'
})

0reactions

FabienMottecommented, Sep 11, 2021

So cool! Thanks a lot for your time @antfu 🎉 🙏

Top Results From Across the Web

You may need an appropriate loader to handle this file type ...

I solved the problem. In my next.config.js i use multiple plugins. My mistake was that I had written several module.exports statements.

You May need additional loader to handle the result of these ...

Getting same error while building my next js project and none of the solution is working for me mentioned here. https://exerror.com/failed-to- ...

Custom Webpack Config - Next.js

defaultLoaders : Object - Default loaders used internally by Next.js: babel : Object - Default babel-loader configuration. Example usage of defaultLoaders.babel ...

next.config.js: Introduction

next.config.js is a regular Node.js module, not a JSON file. It gets used by the Next.js server and build phases, ...

Migrating from Create React App - Next.js

Migrating from Create React App. This guide will help you understand how to transition from an existing non-ejected Create React App project to...