A bug by using ismobilejs because of the wrong api uesed

[HypnosNova]

Expected Behavior

no mistakes when compiling

Current Behavior

Possible Solution

Steps to Reproduce

STEP 1: npm i pixi.js and then using
import * as PIXI from './pixi.js';
And just write a hello world demo.
STEP 2: compiler the project and failed

Environment

• pixi.js version: _e.g. newest
• Browser & Version: _e.g. any bloswers
• OS & Version: _e.g. any os
• Running Example:

[bigtimebuddy]

Please provide a repo the reproduces the issue. Your step are insufficient and the tools you’re using to compile probably matter.

[HypnosNova]

Using PIXI with react.
When compiling the whole project and run it on browser, we could see following error:

I add a console to see what ismobilecall is.
And in browser console, we could see ismobilecall is an object that contains several APIs,

That means after the project compiled, ismobilejs export default an Object instead of a function.

But strangely, I create a new project and use rollup to compile, nothing went wrong, only in react project it went wrong.
So is it a bug in react tools? Or do you know any solutions to solve it

[notorigine]

I believe it is an issue with v1 of ismobilejs - see issue #115.

Using a complete different stack than React (Gulp, ES6), it is also causing an error when running my build process, because ismobilejs isn't transpiled when imported as a dependancy by @pixi/settings (see screenshots).

Any thoughts on how to solve this?

[bigtimebuddy]

Fixed, will try to get out a release ASAP.