There should be an updater running fixing those imports but maybe it doesnt catch all cases ?
The error thrown from my scripts are basically Behaviour scripts not starting and other TS scripts that depend on them fail. But besides that no other errors.
by user 615280976855171083
Could you send me the errors?
Sounds like some other issue.
The errors are the comments, and they happen after page load of course where the game should already be running.
by user 615280976855171083
do you think you could send me a bug report zip?
Yes, let’s do that. 
Thanks for the help.
by user 615280976855171083
Thank you!
Got a fix - it was caused by the codegen change where it tries to assign the exported files array to the <needle-engine> src attribute when the component is not yet in the dom. Working on a fix
When manually changing that and assigning the file as src it seems to load and work fine again
A hotfix is out, could you try that?
Oops I didn’t see you sent me a message ! I’ll try that on Monday. 
Thanks for the investigation !
by user 615280976855171083
@marwie1 
Sorry I haven’t been able to get back to the project. But I’ve just updated to 2.65.2 and it’s fixed ! 
Everything’s back to normal.
by user 615280976855171083
As trying to pack to production (using needle-tools 2.65.2-pre), our Gitlab server thrown this error:
> tsc && vite build && npm run copy-files
node_modules/@needle-tools/engine/src/engine/engine_loaders.ts:6:32 - error TS2307: Cannot find module 'three/examples/jsm/libs/meshopt_decoder.module.js' or its corresponding type declarations.
6 import { MeshoptDecoder } from 'three/examples/jsm/libs/meshopt_decoder.module.js';
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Found 1 error in node_modules/@needle-tools/engine/src/engine/engine_loaders.ts:6
Does it mean we should stuck with your version of Three ?
by user 615280976855171083
Which version is your gitlab server using? Do you have a specific reason for another three version? We regularly rebase to the latest three version and made a bunch of changes and fixes in our fork (if possible we make PRs to the main repo)
Oops I misread, we do use your version of Three, this is what we’ve installed : “@needle-tools/engine”: “2.65.2-pre”, “@needle-tools/three”: “0.146.5”
Is that correct ?
by user 615280976855171083
Yes that’s correct
Then we do have this issue (above) with these versions.
by user 615280976855171083