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.

Module nuxt-icons is disabled due to incompatibility issues

See original GitHub issue

Environment

Operating System: Windows_NT
Node Version: v16.17.0
Nuxt Version: 3.0.0-rc.9
Nitro Version: 0.5.0
Package Manager: npm@8.15.0
Builder: vite
User Config: modules, runtimeConfig
Runtime Modules: @nuxtjs/tailwindcss@5.3.2, @vueuse/nuxt@9.1.1, nuxt-icons@2.0.1, @pinia/nuxt@0.4.1
Build Modules: -

Reproduction

use npx nuxi update to upgrade from RC8 to RC9

Reproduction link: https://stackblitz.com/edit/github-wdogcw

Describe the bug

After Upgrading from RC8 Nuxt Icon Module are not working anymore.

Additional context

In Node Console

In Browser Console

Logs

No response

Issue Analytics

State:
Created a year ago
Comments:5 (3 by maintainers)

Top GitHub Comments

1reaction

danielroecommented, Sep 5, 2022

@daver987 And which modules are those?

0reactions

danielroecommented, Sep 12, 2022

This is now resolved in v2.0.2 of nuxt-icons. Please raise an issue on any other modules this affects, and feel free to tag me; I’ll happily help resolve.

Top Results From Across the Web

Recently Active 'nuxtjs3' Questions - Stack Overflow

Hello I'm currently having issues with the integration of pinia in Nuxt3 ... WARN Module pinia is disabled due to incompatibility issues: -...

Release Notes - Nuxt

Discover all the release notes for the Nuxt framework.

nuxt-purgecss - npm

Start using nuxt-purgecss in your project by running `npm i ... TypeScript icon, indicating that this package has built-in type declarations.

Nuxt.js - Pinia

We supply a module to handle everything for you, you only need to add it to modules in your nuxt.config.js file: // nuxt.config.js...

To v5 from v4 - webpack

Test webpack 5 compatibility. Try to set the following options in your webpack 4 configuration and check if build still works correctly. module.exports ......