Performance issues appear when used in create-react-app

[rohan-deshpande]

Currently this is a bit of a mystery to me but when including three-nebula in a create-react-app app - performance seems to be significantly impacted. The issue can be rectified by including the lib in a script tag rather than as a dependency.

If included as a dependency via npm install three-nebula, GPU rendered systems which clock in at a rock solid 60FPS normally are maxing out at 40FPS.

If the lib is included as a script tag in public/index.html and Nebula is accessed via the window everything is fine.

Perhaps this is related to #94. You can't modify the babel config in CRA apps without ejecting so that solution is not going to work.

Ideally what would have to happen would be to investigate what function in particular was causing the issue and fix it.

@manthrax has done some investigating and noticed that the performance profiles for an identical system look totally different in the different environments.

Note that this doesn't seem to be happening in the GPURenderer example for an app built with next so it more than likely is something odd in the create-react-app config.

[rohan-deshpande]

One interesting thing re: the next app is that the library isn't pulled in via a regular import. For code splitting purposes, the following approach is used

const { default: ParticleSystem, GPURenderer } = await import(
  'three-nebula'
);

I'm unsure right now if this has any implications or not...