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.

Compatibility Issue on Nuxt 3

See original GitHub issue

Hi there, I’m having troubles using the latest version of the vueuse/motion with nuxt 3 when I follow the the Doc about Nuxt Usage. If you pass the: '@vueuse/motion/nuxt' The error returned is about: Cannot start nuxt: Package subpath ‘./nuxt’ is not defined by “exports” in…

I tried a few thing, but not solve my problem: I tried to change the version of beta.12 to beta.23 and I removed too the /nuxt on nuxt.config.ts. The error changed, but still there.

Nuxt 3.0.0-rc.13 @vueuse/motion": "^2.0.0-beta.12

Does have someone with the same problem and found a solution?

Issue Analytics

State:
Created 10 months ago
Reactions:7
Comments:8 (2 by maintainers)

Top GitHub Comments

22reactions

itzakscommented, Nov 29, 2022

Anyone have it working in nuxt3 yet?

Seems like there was an unannounced release of beta-25 that you can use now!

"@vueuse/motion": "2.0.0-beta.25",

Works fine with nuxt 3.0. 🚀✨

5reactions

grunghicommented, Nov 16, 2022

Problem might be in the deprecated addAutoImportDir function used in the nuxt module, it should be replaced with addImportsDir.

Also the publicRuntimeConfig option used in the module is no longer present in nuxt 3, as it was replaced with runtimeConfig.public.

I’ve made a patch to fix the compatibility of @vueuse/motion beta.24 with nuxt 3.0.0 stable release, you can find it here and apply it with yarn patch-package.