# CDN for glTFFileLoader missing/changed starting in v9.5.0 **URL:** \ **Category:** Questions\ **Tags:** gltf, gltffileloader\ **Created:** [May 2, 2026, 5:40pm UTC](https://forum.babylonjs.com/t/cdn-for-gltffileloader-missing-changed-starting-in-v9-5-0/63314 "2026-05-02T17:40:16Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![regna](https://sea2.discourse-cdn.com/flex024/user_avatar/forum.babylonjs.com/regna/32/23915_2.png) [@regna](https://forum.babylonjs.com/u/regna)\ **Post date:** [May 2, 2026, 5:40pm UTC](https://forum.babylonjs.com/t/cdn-for-gltffileloader-missing-changed-starting-in-v9-5-0/63314/1 "2026-05-02T17:40:16Z")
Hi Babylon.js team! I’ve been updating local libs every update via the CDN like: ✅ [https://cdn.babylonjs.com/v9.4.1/loaders/babylon.glTFFileLoader.js](https://cdn.babylonjs.com/v9.4.1/loaders/babylon.glTFFileLoader.js) ❌ [https://cdn.babylonjs.com/v9.5.0/loaders/babylon.glTFFileLoader.js](https://cdn.babylonjs.com/v9.5.0/loaders/babylon.glTFFileLoader.js) Please notice how the link no longer works with v9.5.0. There is also a `.min.js` link: ✅ [https://cdn.babylonjs.com/v9.4.1/loaders/babylon.glTFFileLoader.min.js](https://cdn.babylonjs.com/v9.4.1/loaders/babylon.glTFFileLoader.min.js) 🔄[https://cdn.babylonjs.com/v9.5.0/loaders/babylon.glTFFileLoader.min.js](https://cdn.babylonjs.com/v9.5.0/loaders/babylon.glTFFileLoader.min.js) However, the structure of the JS file changed significantly starting in v9.5.0, and I’m having trouble loading it the way I did with v9.4.1. I was wondering if maybe there was a config issue? Thank you so much for your help! ---
**Author:** ![RaananW](https://sea2.discourse-cdn.com/flex024/user_avatar/forum.babylonjs.com/raananw/32/28955_2.png) [@RaananW](https://forum.babylonjs.com/u/RaananW)\ **Post date:** [May 4, 2026, 8:46am UTC](https://forum.babylonjs.com/t/cdn-for-gltffileloader-missing-changed-starting-in-v9-5-0/63314/2 "2026-05-04T08:46:41Z")
checking that as well, thanks for reporting ---
**Author:** ![RaananW](https://sea2.discourse-cdn.com/flex024/user_avatar/forum.babylonjs.com/raananw/32/28955_2.png) [@RaananW](https://forum.babylonjs.com/u/RaananW)\ **Post date:** [May 4, 2026, 11:18am UTC](https://forum.babylonjs.com/t/cdn-for-gltffileloader-missing-changed-starting-in-v9-5-0/63314/3 "2026-05-04T11:18:11Z")
> > > \## Summary > > Fixes UMD package compatibility regressions introduced by the webpac…k-to-Rollup migration. > > The previous webpack UMD build used \`libraryExport: "default"\`, so legacy public packages effectively exposed the legacy namespace itself. The Rollup entries were exporting namespace wrapper objects such as \`{ core, default, \_\_esModule }\` instead, which broke both browser-global and bundler/CommonJS consumption patterns. > > This PR updates the UMD entry points to: > > \`\`\`ts > import "package/legacy/legacy"; > export \* from "package/legacy/legacy"; > \`\`\` > > That preserves legacy global attachment side effects and exposes named exports directly. It also disables Rollup tree-shaking for UMD builds so legacy side-effect modules are not removed because several dev packages declare \`sideEffects: false\`. > > \## Related forum reports > > \- https://forum.babylonjs.com/t/issues-with-loading-babylonjs-packages > \- https://forum.babylonjs.com/t/cdn-for-gltffileloader-missing-changed-starting-in-v9-5-0 > \- https://forum.babylonjs.com/t/new-step-for-loading-babylon-in-webworker-starting-in-v9-5-0 > > \## Behavior restored > > \- \`import \* as BABYLON from "babylonjs"\` exposes \`BABYLON.Vector3\` at the root again. > \- Dependent UMD packages receive the expected Babylon namespace rather than a \`{ core, default }\` wrapper. > \- \`babylonjs-procedural-textures\` named imports work again, such as \`WoodProceduralTexture\`. > \- Script-tag/global usage keeps attaching symbols like \`BABYLON.GLTF2.GLTFLoader\` and \`BABYLON.WoodProceduralTexture\`. > \- Production builds continue to generate the non-min copied glTF loader artifact locally via the existing \`minToMax\` copy path. > > \## Validation > > \- Added \`packages/public/umd/test/unit/umdRollupCompatibility.test.ts\`. > \- Ran the new unit test: 2 passed. > \- Ran production UMD builds for \`babylonjs\`, \`babylonjs-loaders\`, and \`babylonjs-procedural-textures\`. > \- Smoke-tested production artifacts for browser globals and CommonJS exports. > \- Ran ES checks for the rebuilt UMD packages. > \- Ran Prettier check and \`npm run lint:changed\`. > > \## Note > > The live \`v9.5.0\` CDN 404 for \`loaders/babylon.glTFFileLoader.js\` appears to require a republish/redeploy or hotfix CDN upload. The local production build does generate the file, so this code change fixes the build output for the next publish. ---
**Author:** ![regna](https://sea2.discourse-cdn.com/flex024/user_avatar/forum.babylonjs.com/regna/32/23915_2.png) [@regna](https://forum.babylonjs.com/u/regna)\ **Post date:** [May 4, 2026, 10:23pm UTC](https://forum.babylonjs.com/t/cdn-for-gltffileloader-missing-changed-starting-in-v9-5-0/63314/4 "2026-05-04T22:23:45Z")
Thank you so much Raanan! 😄 ---
**Author:** ![regna](https://sea2.discourse-cdn.com/flex024/user_avatar/forum.babylonjs.com/regna/32/23915_2.png) [@regna](https://forum.babylonjs.com/u/regna)\ **Post date:** [May 6, 2026, 8:49pm UTC](https://forum.babylonjs.com/t/cdn-for-gltffileloader-missing-changed-starting-in-v9-5-0/63314/5 "2026-05-06T20:49:10Z")
@RaananW when you have time, could you please help look into the CDN for `glTFFileLoader` for the newly released v9.5.2? ## `.js` ✅ [https://cdn.babylonjs.com/v9.4.1/loaders/babylon.glTFFileLoader.js](https://cdn.babylonjs.com/v9.4.1/loaders/babylon.glTFFileLoader.js) ❌ [https://cdn.babylonjs.com/v9.5.2/loaders/babylon.glTFFileLoader.js](https://cdn.babylonjs.com/v9.5.2/loaders/babylon.glTFFileLoader.js) (does not exist) ## `.min.js`: ✅ [https://cdn.babylonjs.com/v9.4.1/loaders/babylon.glTFFileLoader.min.js](https://cdn.babylonjs.com/v9.4.1/loaders/babylon.glTFFileLoader.min.js) 🔄 [https://cdn.babylonjs.com/v9.5.2/loaders/babylon.glTFFileLoader.min.js](https://cdn.babylonjs.com/v9.5.2/loaders/babylon.glTFFileLoader.min.js) (exists but different structure compared to v9.4.1, and I’m having trouble loading it the same way I did with v9.4.1) Thank you so much for all of your help, Raanan! ---
**Author:** ![RaananW](https://sea2.discourse-cdn.com/flex024/user_avatar/forum.babylonjs.com/raananw/32/28955_2.png) [@RaananW](https://forum.babylonjs.com/u/RaananW)\ **Post date:** [May 11, 2026, 10:51am UTC](https://forum.babylonjs.com/t/cdn-for-gltffileloader-missing-changed-starting-in-v9-5-0/63314/6 "2026-05-11T10:51:41Z")
Can i ask what the difference is when you load it? is it still the same with 9.6.2? I am working on adding the missing file, though they are identical for quite a long time now. it can be a simple redirect, as we also provide sourcemaps. > > > \> 🤖 \*This PR was created by the create-pr skill.\* > > \## Summary > > Fixes the UMD pro…duction build helper so multi-entry packages copy the secondary filename alias for each entry after that entry's output exists. > > Previously, the \`copyMinToMaxPlugin\` was attached only to the first Rollup config for multi-entry packages, but it attempted to copy aliases for every entry. Because later entry outputs had not been written yet, only the first/main package bundle received both published names. > > \## Motivation > > A forum report noted that the versioned CDN URL for the regular glTF loader alias was missing starting in 9.5.x: > > https://forum.babylonjs.com/t/cdn-for-gltffileloader-missing-changed-starting-in-v9-5-0/63314/5?u=raananw > > For example, \`v9.5.2/loaders/babylon.glTFFileLoader.min.js\` exists, but \`v9.5.2/loaders/babylon.glTFFileLoader.js\` returns 404. > > \## What was missing > > The issue was broader than the glTF loader. In versioned CDN releases, the individual entry aliases were missing for multi-entry UMD packages while their \`.min.js\` files existed: > > \- \`loaders\`: individual loader aliases such as \`babylon.glTFFileLoader.js\` > \- \`materialsLibrary\`: individual material aliases such as \`babylon.gridMaterial.js\` > \- \`proceduralTexturesLibrary\`: individual procedural texture aliases > \- \`postProcessesLibrary\`: individual post-process aliases > \- \`serializers\`: individual serializer aliases > > The package-level bundles, such as \`babylonjs.loaders.js\` and \`babylonjs.loaders.min.js\`, were still present. > > \## Fix > > In multi-entry mode, attach \`copyMinToMaxPlugin\` to every per-entry Rollup config and scope it to the current \`chunkName\`. This ensures the secondary alias is copied after the corresponding output file exists. > > Single-entry packages, including the main \`babylonjs\` package (\`babylon.js\` / \`babylon.max.js\`), continue through the unchanged single-config path. > > \## Validation > > Ran: > > \`\`\`bash > npm run build:prod -w babylonjs-loaders > \`\`\` > > Confirmed the build now emits both names for every loader entry, including: > > \`\`\`text > babylon.glTFFileLoader.min.js > babylon.glTFFileLoader.js > babylon.objFileLoader.min.js > babylon.objFileLoader.js > babylonjs.loaders.min.js > babylonjs.loaders.js > \`\`\` ---
**Author:** ![regna](https://sea2.discourse-cdn.com/flex024/user_avatar/forum.babylonjs.com/regna/32/23915_2.png) [@regna](https://forum.babylonjs.com/u/regna)\ **Post date:** [May 20, 2026, 5:55pm UTC](https://forum.babylonjs.com/t/cdn-for-gltffileloader-missing-changed-starting-in-v9-5-0/63314/7 "2026-05-20T17:55:10Z")
Thank you so much for your help, Raanan! Although the format did change after v9.4.1, I can work with the new format moving forward, so no worries from my end. To `await import()` `glTFFileLoader` in Node.js (rather than browser), I’ve been commenting out a small part of `babylon.glTFFileLoader.min.js`: * * * `babylon.glTFFileLoader.min.js` (v9.4.1 and earlier) ```js !function(e,t){/*"object"==typeof exports&&"object"==typeof module?module.exports=t(require("babylonjs")):"function"==typeof define&&define.amd?define("babylonjs-loaders",["babylonjs"],t):"object"==typeof exports?exports["babylonjs-loaders"]=t(require("babylonjs")):*/e.LOADERS=t(e.BABYLON)} ``` `babylon.glTFFileLoader.min.js` (v9.5.0+) ```js !function(e,t){/*"object"==typeof exports&&"undefined"!=typeof module?t(exports,require("babylonjs")):"function"==typeof define&&define.amd?define(["exports","babylonjs"],t):*/t((e="undefined"!=typeof globalThis?globalThis:e||self).BABYLON=e.BABYLON||{},e.BABYLON)} ``` * * * This commenting out helps avoid the error when `await import()`ing `glTFFileLoader` in Node.js: ```js Error: Cannot find module 'babylonjs' Require stack: - /home/nonroot/app/lib/babylon/loaders/babylon.glTFFileLoader.min.js at Function._resolveFilename (node:internal/modules/cjs/loader:1383:15) at defaultResolveImpl (node:internal/modules/cjs/loader:1025:19) at resolveForCJSWithHooks (node:internal/modules/cjs/loader:1030:22) at Function._load (node:internal/modules/cjs/loader:1192:37) at TracingChannel.traceSync (node:diagnostics_channel:328:14) at wrapModuleLoad (node:internal/modules/cjs/loader:237:24) at Module.require (node:internal/modules/cjs/loader:1463:12) at require (node:internal/modules/helpers:147:16) at /home/nonroot/app/lib/babylon/loaders/babylon.glTFFileLoader.min.js:1:79 at Object. (/home/nonroot/app/lib/babylon/loaders/babylon.glTFFileLoader.min.js:1:262) { code: 'MODULE_NOT_FOUND', requireStack: [ '/home/nonroot/app/lib/babylon/loaders/babylon.glTFFileLoader.min.js' ] } ``` Because the new part to comment out for the new format has been found, I’m able to move forward with the new format.