Unexpected token { (Nuxt)

[auritylab]

Unexpected token { (Nuxt)

[WipeAir]

Hey,
I haven't tried the library with Nuxt yet. I'll try to fix it and get back to you asap!

[Ovyerus]

👍

[WipeAir]

Sorry for the delay!
I've changed the module system to commonjs in v1.3.0 (already published on npm).
Hopefully it solves your problem! If you have any further problems, don't hesitate to reply.

[Ovyerus]

Looks like it's still happening. Took a look at the file again and it looks like it still has ES6 imports. Possibly forgot to rebuild for it?

Also made a barebones Nuxt project (using create-nuxt-app) just to ensure it's the lib and not me, and it still occurs.

[WipeAir]

You may retry it now - v1.3.1

[Ovyerus]

Alright seems to be fixed in v1.3.1 now. I seem to be getting a compile error for one of my components but unsure if it's the plugin or me. Removing it works fine though.

Thanks for the help 👍

[Ovyerus]

On second look it seems to be occuring with, any input element I try to make, which is bizarre.

https://gist.github.com/Ovyerus/a89b9120b9209f6f2db89cbb70cb8f47

[WipeAir]

What do you exactly mean with input element in this case?
The plugin is not bound to any component directly...

[Ovyerus]

Any <input>. When there's none in the current view it seems to work fine, but when there's one it causes an error like shown above. Not sure why exactly. Doesn't occur when the plugin isn't loaded as well it seems.

[WipeAir]

Ok, that's crazy. Is this problem reproducible in a simple Nuxt app? If so, can you provide me an example project? Then I could look into it :)

[Ovyerus]

Alright so I go to test it in a clean one, and of course it doesn't come up, even when I try testing it again in the main project. I'll try to see if I can properly recreate it if it crops up again.

Only thing I can think that's different is that it was occuring on my laptop, but not sure why that'd change anything.

[WipeAir]

Ok, good to hear that it works.
If it occurs again just create a demo project and send it to me.