Node doesn't load in latest ComfyUI frontend

[UXVirtual]

On August 15th, ComfyUI transitioned to a new frontend UI framework which has caused breaking changes to the TextureViewer node. This prevents the Three.js scene from loading correctly and it remains stuck on the "Loading scene" preloader title.

When comparing the new ComfyUI frontend UI and the legacy one we can see the following:

Legacy Frontend UI

New Frontend UI

If users have updated to the latest ComfyUI a Uncaught TypeError: Cannot read properties of undefined (reading 'api') at api.js:2:36 is thrown in the JavaScript console. Looking at this it seems to reference a shim which is no longer valid.

To workaround this issue in the meantime, starting ComfyUI with the --front-end-version Comfy-Org/ComfyUI_legacy_frontend@latest as described in this issue allows the TextureViewer node to work.

Tested this issue and the workaround using the mtb nodes workflow linked in the project README.

[huchenlei]

This is wield. The shim should access the api object bind on window.comfyAPI. Can you check if your browser console what does following code eval to?

[UXVirtual]

window.comfyAPI resolves as follows in the console:

[Mattssn]

Heya, really like the idea of this node, but still seems it doesn't work, will this be updated to work with newer versions?

[Dayuppy]

Can confirm the issue still exists.

[Sergio-Redraw]

up

[deniaud]

app.ts:1697 Error loading extension /extensions/ComfyUI-Texture-Simple/js/threeVisualizer.js TypeError: Failed to resolve module specifier "three". Relative references must start with either "/", "./", or "../".

[freeaces]

same error:

index-4Hb32CNk.js:199435 Error loading extension /extensions/ComfyUI-Texture-Simple/js/threeVisualizer.js TypeError: Failed to resolve module specifier "three". Relative references must start with either "/", "./", or "../".

[Kinglord]

It's completely broken in the new UI because of the move to Vue/Vite breaking custom nodes' ability to import libraries like this. It needs to be reworked totally and at this point probably isn't worth the effort, I spent half a day trying workarounds to use this code and they've made that neigh impossible without a complete refactor of how it imports/utilizes three.js libs