You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I do import * as JZZ from 'jzz'; in my plugins/midi.client.ts file (which gets auto imported) everything is fine during $ npm run dev, but as soon as I go $ npm run generate I get this error:
Cannot call a namespace ('JZZ')
and in my Front-End
Which corresponds to this section (I guess?) in my entry.js:
I already tried importing like this: import JZZ from 'jzz'
I also read this somewhere:
import*asJZZaliasfrom'jzz'constJZZ=JZZalias
All without success :(
EDIT:
It looks like JZZ gets imported properly after all doing import JZZ from 'jzz', but the second .or() gets fired in production:
constinput=JZZ().or('somethings happening').openMidiIn().or('something else...')// I see this in production, why? :(.and(function(){console.log('Device connected:',this.name());store.midiDeviceName=this.name();});
In dev server, everything works as expected after seeing the log of Device connected: OP1 LE Bluetooth
The text was updated successfully, but these errors were encountered:
katerlouis
changed the title
Nuxt 3 (with Vite) issue on building static site
Nuxt 3 (with Vite) issue on building static site: Cannot call a namespace ('JZZ')
Feb 15, 2023
When I do
import * as JZZ from 'jzz';
in myplugins/midi.client.ts
file (which gets auto imported) everything is fine during$ npm run dev
, but as soon as I go$ npm run generate
I get this error:and in my Front-End
Which corresponds to this section (I guess?) in my entry.js:
I already tried importing like this:
import JZZ from 'jzz'
I also read this somewhere:
All without success :(
EDIT:
It looks like JZZ gets imported properly after all doing
import JZZ from 'jzz'
, but the second.or()
gets fired in production:In dev server, everything works as expected after seeing the log of
Device connected: OP1 LE Bluetooth
The text was updated successfully, but these errors were encountered: