# After upgrading to v5.12.1 from v5.11, webpack build breaks

**URL:** https://forum.babylonjs.com/t/after-upgrading-to-v5-12-1-from-v5-11-webpack-build-breaks/31824
**Category:** Bugs
**Created:** [June 30, 2022, 11:58pm UTC](https://forum.babylonjs.com/t/after-upgrading-to-v5-12-1-from-v5-11-webpack-build-breaks/31824 "2022-06-30T23:58:05Z")
**Posts on this page:** 1
**Showing post:** 9

<div class="post-metadata">

### Author: ![jelster](https://sea2.discourse-cdn.com/flex024/user_avatar/forum.babylonjs.com/jelster/32/25881_2.png) [@jelster](https://forum.babylonjs.com/u/jelster)
#### Post date: [July 5, 2022, 9:25pm UTC](https://forum.babylonjs.com/t/after-upgrading-to-v5-12-1-from-v5-11-webpack-build-breaks/31824/9 "2022-07-05T21:25:00Z")

</div>

Is there a message that’s telling you that or is that coming from somewhere else? I didn’t see any mention of missing that package or anything resembling that one anywhere.

I checked my package-lock.json and it appears it does appear in there although I wonder if the issue wasn’t because of this other [package versioning I read about](https://forum.babylonjs.com/t/what-is-actually-happening-when-you-import-a-npm-package/6119):

```auto
    "node_modules/babylonjs-gltf2interface": {
      "version": "5.13.2",
      "resolved": "https://registry.npmjs.org/babylonjs-gltf2interface/-/babylonjs-gltf2interface-5.13.2.tgz",
      "integrity": "sha512-BKDMo8+y6uOqJxSuBqpq6D8U/Pm6psk6EwI2O/XnSrQn0fX3ThNn3NEV2iahoYFyJEcESGf1m8v3Uds32ZvHvw==",
      "dev": true,
      "peer": true
    },

```

---

_[View the full topic](https://forum.babylonjs.com/t/after-upgrading-to-v5-12-1-from-v5-11-webpack-build-breaks/31824)._