Babylon.js: IE11 - multiple definitions of a property not allowed in strict mode

Created on 2 May 2018  路  12Comments  路  Source: BabylonJS/Babylon.js

Bugs

  • When compiling with babel / webpack in production mode i have this error on IE in console
    "multiple definitions of a property not allowed in strict mode"

  • this happened after upgrading from 3.2.0-alpha7 - to current verison

question

Most helpful comment

I just figured out a cause of my issue - I was accidentally specify some of my components props twice, such as

<w-button btn-style="orange" btn-style="red"/>

Once that code was converted into js object - it was causing an issue with multiple definitions

All 12 comments

Can you tell us where this error is?
We should have try catched it

Ciao @deltakosh ,
I had the problem on https://v-moda.com/pages/crossfade2-wireless_customizer - now we had to revert to alpha7 because the error was blocking all the website.
I remember that the problem was with the function MultiplyScalar ... the problem was found only in the minified version of babylon because in development mode everything was smooth.

thanks !

Francis

Woot ! I love your site. Do you want to be highlighted on babylonjs.com?
I'll have a look on MultiplyScalar to see what is wrong

@deltakosh - yes it woul be great :)
the v-moda.com runs on shopify and we have a custom platform entried made on babylon, also for
speakers https://v-moda.com/pages/remix_customizer
and in-ear https://v-moda.com/pages/forza_customizer

Do you mind giving me a title / author and a 800x500 screenshot?

Also I do not find a MultiplyScalar in Babylon.js so can you point me to where you see it in the code?

closing issue. Please reopen if required

Hi,

I had the same issue on Internet Explorer 11, it is caused by Oimo.js, more specifically this file: https://github.com/lo-th/Oimo.js/blob/gh-pages/src/math/Vec3.js where multiplyScalar is defined twice.

You can uninstall Oimo.js if you are not using it.
See http://doc.babylonjs.com/features/npm_support#using-webpack for removing warnings.

I already submitted a PR to oimo regarding this bug, but it is not yet merged - https://github.com/lo-th/Oimo.js/pull/70

I also have this issue in IE11. Using Vue + Nuxt.js

What version are you using ???

I just figured out a cause of my issue - I was accidentally specify some of my components props twice, such as

<w-button btn-style="orange" btn-style="red"/>

Once that code was converted into js object - it was causing an issue with multiple definitions

Was this page helpful?
0 / 5 - 0 ratings