# External file https://cdn.babylonjs.com/draco\_wasm\_wrapper\_gltf.js

**URL:** <https://forum.babylonjs.com/t/external-file-https-cdn-babylonjs-com-draco-wasm-wrapper-gltf-js/53944>\
**Category:** Questions\
**Tags:** draco, cdn\
**Created:** [October 5, 2024, 11:49pm UTC](https://forum.babylonjs.com/t/external-file-https-cdn-babylonjs-com-draco-wasm-wrapper-gltf-js/53944 "2024-10-05T23:49:20Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![onekit](https://sea2.discourse-cdn.com/flex024/user_avatar/forum.babylonjs.com/onekit/32/49527_2.png) [@onekit](https://forum.babylonjs.com/u/onekit)\
**Post date:** [October 7, 2024, 11:30am UTC](https://forum.babylonjs.com/t/external-file-https-cdn-babylonjs-com-draco-wasm-wrapper-gltf-js/53944/3 "2024-10-07T11:30:15Z")

</div>

Hello Boye.

Thank you for responding to my message. Currently I use this solution:

```auto
    DracoCompression.Configuration = {
      decoder: {
        wasmUrl: "/draco/draco_wasm_wrapper_gltf.js",
        wasmBinaryUrl: "/draco/draco_decoder_gltf.wasm",
        fallbackUrl: "/draco/draco_decoder_gltf.js",
      }
    }

```

🤔 I don’t like this way of solving the problem, and it seems entirely inelegant to me.

Why do we need to add workarounds like manual configuration and manually placing files into a directory, instead of simply having these files installed via a `package.json` dependency and placed in `node_modules`, as it happens with the Havok Physics Engine?

---

_[View the full topic](https://forum.babylonjs.com/t/external-file-https-cdn-babylonjs-com-draco-wasm-wrapper-gltf-js/53944)._
