NPM build has a broken componentType switch, or outdated code? about gltf-js-utils HOT 5 CLOSED

Hm... I tried re-publishing the module myself from the master branch, compiling that with bundle.run, and the result is still broken. Maybe this is a bug in bundle.run...

from gltf-js-utils.

Ok, it's something about the TS->JS transpilation?

• https://github.com/wnayes/glTF-js-utils/blob/master/src/buffer.ts#L178-L183
• https://github.com/wnayes/glTF-js-utils/blob/master/dist/buffer.js#L142-L147

The JS version is not equivalent to the TS. :/

from gltf-js-utils.

It looks to me like I must have compiled the individual .ts files at an earlier state of development, and then eventually changed how the module build was done. They no longer change when I run npm run build, the only maintained output is the /dist/gltfutils.js UMD module.

I could delete the individual compiled files, or would it be useful to maintain those?

from gltf-js-utils.

Thanks! I’m not typically used to seeing individual files in a dist/ folder, so just having the one file would be fine from my perspective. Sounds like a fix for #1 would solve this as well — I only tried to use index.js because the default entry point didn’t work for me.

from gltf-js-utils.

Installing the latest version from NPM, I no longer have this issue. 🎉

from gltf-js-utils.