CDN for glTFFileLoader missing/changed starting in v9.5.0

regna · May 2, 2026, 5:40pm

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.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.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!

RaananW · May 4, 2026, 8:46am

checking that as well, thanks for reporting

RaananW · May 4, 2026, 11:18am

github.com/BabylonJS/Babylon.js

Fix UMD Rollup namespace exports (#18414)

master ← RaananW:fix/umd-rollup-compat

opened 09:23AM - 04 May 26 UTC

RaananW

+203 -167

## 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.

regna · May 4, 2026, 10:23pm

Thank you so much Raanan!

regna · May 6, 2026, 8:49pm

@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.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.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!

RaananW · May 11, 2026, 10:51am

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.

github.com/BabylonJS/Babylon.js

Fix UMD secondary aliases for multi-entry builds (#18443)

master ← RaananW:fix-umd-multi-entry-aliases

opened 11:17AM - 11 May 26 UTC

RaananW

+1 -1

> 🤖 *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 ```

Topic		Replies	Views
New step for loading BABYLON in WebWorker starting in v9.5.0 Questions module	4	109	May 6, 2026
"glTFFileLoader.js" CDN makes page crash, suspecting typo in "interactivityUtils.ts" Bugs gltffileloader	4	345	January 10, 2024
Issues with loading "babylonjs-*" packages Bugs	9	122	May 15, 2026
Please help! My 3D website just stopped working, Questions	16	815	June 16, 2023
Gltf loader error when upgrading to BabylonJS 8.51.2 from 8.24.0 Bugs gltffileloader	12	261	February 19, 2026

CDN for glTFFileLoader missing/changed starting in v9.5.0

.js

.min.js:

Related topics

`.js`

`.min.js`: