Nuxt 3 + Vite about human HOT 1 CLOSED

i've never used Nuxt 3 + Vite, but it seems its wrapping an entire instance of human into a proxy object as it can be seen even from:

Human: configuration: Proxy(Object) {backend: 'cpu', modelBasePath: '/models', cacheModels: true, validateModels: true, wasmPath: 'https://cdn.jsdelivr.net/npm/@tensorflow/[email protected]/dist/', …}

and then later it fails because some properties are private - but no framework should care about what's happening INSIDE the library.

instead of chasing down which property is private when it shouldn't be, you should configure nuxt/vite to NOT wrap libraries as such.

it could be due to you instantiating human on this object which is nuxt/vite managed:
so at least instead of

    this.human = new Human(config)
    const human = this.human

do just

   const human = new Human(config)

and more than that, there has to be a setting in nuxt/vite config to tell it not to mess with imports. for example, with standard TS, you'd set skipLibCheck in project properties. but like i said, i'm not nuxt/vite coder, you'll have to find it yourself.

i'm closing this issue as not-a-product-issue and i really cannot help much more than this.

from human.