# Disable THREE.BufferGeometry warnings in my console

**URL:** <https://discourse.threejs.org/t/disable-three-buffergeometry-warnings-in-my-console/20905>\
**Category:** Questions\
**Tags:** webglrenderer\
**Created:** [November 21, 2020, 9:44am UTC](https://discourse.threejs.org/t/disable-three-buffergeometry-warnings-in-my-console/20905 "2020-11-21T09:44:08Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![AltDom](https://yyz1.discourse-cdn.com/flex035/user_avatar/discourse.threejs.org/altdom/32/14713_2.png) [@AltDom](https://discourse.threejs.org/u/AltDom)\
**Post date:** [November 21, 2020, 9:44am UTC](https://discourse.threejs.org/t/disable-three-buffergeometry-warnings-in-my-console/20905/1 "2020-11-21T09:44:08Z")

</div>

Hi!

I have a web app built in react-three-fibre and react which is in production that’s working as it should!

However… 😬 my problem is that I can’t seem to permanently disable some THREE.BufferGeometry and THREE.WebGLRenderer console warnings from the three.module.js file. I have 1000s of them and they are unfortunately affecting the performance.

I have tried deleting them from the node\_modules which does remove them when in development, however in production they are reintroduced when I build and when the node\_modules are created again. Here are some of the warnings I’m seeing:

THREE.BufferGeometry: .addAttribute() has been renamed to .setAttribute().  
THREE.BufferGeometry: .applyMatrix() has been renamed to .applyMatrix4().  
THREE.WebGLRenderer: highp not supported, using lowp instead.

Is there a way I can have these warnings removed in production as well?

Thank you in advance for any assistance that you can provide.

// Dom

---

<div class="post-metadata">

**Author:** ![Mugen87](https://yyz1.discourse-cdn.com/flex035/user_avatar/discourse.threejs.org/mugen87/32/5645_2.png) [@Mugen87](https://discourse.threejs.org/u/Mugen87)\
**Post date:** [November 21, 2020, 9:54am UTC](https://discourse.threejs.org/t/disable-three-buffergeometry-warnings-in-my-console/20905/2 "2020-11-21T09:54:42Z")

</div>

At least the first two warnings tell you that you are using outdated APIs. It’s best if you actually perform the respective migration tasks (e.g. renaming methods) if they are generated in your own code base.

If these warnings are generated in third-party libs, consider to use older versions. In this context, you should directly file issues at the respective GitHub repositories so the authors can update their code base.

In any event, it is not possible to disable three.js logs unless you overwrite `console.warn`.