Cannot work with nuxt 3.0.0-rc.14

[so1ve]

Describe the bug

When using unplugin-icons with nuxt 3.0.0-rc.14, this error occurs:

 ERROR  Cannot read properties of undefined (reading 'nuxt')                                                                                                                                14:12:48  

  at nuxt_default (node_modules\.pnpm\[email protected]\node_modules\unplugin-icons\dist\nuxt.js:9:24)
  at installModule (/E:/Node/dolan-client-meme/node_modules/.pnpm/@[email protected]/node_modules/@nuxt/kit/dist/index.mjs:416:9)
  at async initNuxt (/E:/Node/dolan-client-meme/node_modules/.pnpm/[email protected]_gm5c2zoibozvhuo7w6sksyhknu/node_modules/nuxt/dist/index.mjs:1827:7)
  at async loadNuxt (/E:/Node/dolan-client-meme/node_modules/.pnpm/[email protected]_gm5c2zoibozvhuo7w6sksyhknu/node_modules/nuxt/dist/index.mjs:1859:5)
  at async loadNuxt (/E:/Node/dolan-client-meme/node_modules/.pnpm/@[email protected]/node_modules/@nuxt/kit/dist/index.mjs:732:19)
  at async Object.invoke (/E:/Node/dolan-client-meme/node_modules/.pnpm/[email protected]/node_modules/nuxi/dist/chunks/prepare.mjs:30:18)
  at async _main (/E:/Node/dolan-client-meme/node_modules/.pnpm/[email protected]/node_modules/nuxi/dist/cli.mjs:50:20)

Probably caused by nuxt/framework#9010

Reproduction

https://stackblitz.com/edit/nuxt-starter-sdf5sn

System Info

System:
  OS: Windows 10 10.0.22621
  CPU: (16) x64 AMD Ryzen 9 5900HX with Radeon Graphics
  Memory: 9.22 GB / 31.42 GB
Binaries:
  Node: 16.18.1 - ~\AppData\Local\fnm_multishells\37080_1668580996883\node.EXE
  Yarn: 1.22.19 - ~\AppData\Local\fnm_multishells\37080_1668580996883\yarn.CMD
  npm: 8.19.2 - ~\AppData\Local\fnm_multishells\37080_1668580996883\npm.CMD
Browsers:
  Edge: Spartan (44.22621.819.0), Chromium (107.0.1418.42)
  Internet Explorer: 11.0.22621.1

Used Package Manager

pnpm

Validations

• Follow our Code of Conduct
• Read the Contributing Guide.
• Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
• Check that this is a concrete bug. For Q&A, please open a GitHub Discussion instead.
• The provided reproduction is a minimal reproducible of the bug.