Broken @needle-tools/gltf-build-pipeline

I was trying to build my project but sadly in the build pipeline when running:

npx --yes @needle-tools/gltf-build-pipeline@latest
‘needle-gltf’ is not recognized as an internal or external command,
operable program or batch file.

I would suggest instead of “latest” use “stable” in build-pipeline.js as it is quite dangerous to default to the latest version since it could be experimental.

Hi Martin, thanks for sharing your feedback on this issue. It looks like the current use of the “latest” tag in the build pipeline may be causing the experimental changes to surface, which in your case leads to the “needle-gltf is not recognized” error. Your suggestion to default to the stable version makes sense—it can avoid unexpected issues that might arise from experimental updates.

In the meantime, try running the build pipeline using the stable version explicitly by executing:

npx --yes @needle-tools/gltf-build-pipeline@stable

If doing so resolves the issue, it would confirm that the latest version is indeed introducing conflicts with the expected command-line setup. Additionally, please ensure that your Node.js environment (including PATH settings) is configured properly, as sometimes CLI tools might require that.

If you continue to experience any issues even after switching to stable, consider sharing more details (such as your Node.js version or any additional logs), so that the Needle team can take a closer look.

Happy developing with Needle Engine, and thanks again for your constructive suggestion!

1 replies left - Become PRO for more replies.
thread_EwivBGOiNvCMXwWV3McDEI8v
Reply to this post directly if you need further help (bottom right button)

Hi, this has been fixed in the latest engine versions, the use of latest here was a oversight from older versions when stable was not yet available - could you upgrade to 4.5.x ?

That being said: Indeed it seems like a broken package has been released yesterday and tagged with latest. Will fix this right now so your current version should work as expected again too

1 Like

This topic was automatically closed 13 days after the last reply. New replies are no longer allowed.