How to deal with silent missing ES6 imports? And how not to import some debug imports in release stage?

Questions
1

When you use ES6 tree shaking feature some used features will warn you in a console about some missing package. But sometimes it will not.
I know about that ES6 article in BJS documentation where you can find a list of some missing packages. But let’s imagine a case where you open not yours code and you will not know about some functionality.

Let’s say outlines. Yesterday I had been finding out for 30 minutes what’s wrong with my outlines and why they not shown. No errors, no warnings in the conole but and no outline on my object :smiley:

Yeah, I got some lesson from that case. Now I import all the packages:

import ""@babylon/core";

and see if the feature now is work then I trying to find where it could be:

import "@babylonjs/core/Rendering/boundingBoxRenderer";
import "@babylonjs/core/Rendering/outlineRenderer";

but as a noob in BJS I didn’t even know that there could be some more additional imports. And yeah, that’s great thing that we can import stuff only when we need it. And yeah, that ES6-article that says about importing rendering things, but I totally forget that it’s about Rendering features :smiley: To me, all what I do in BJS is all about rendering :smiley:

By the way, the important question here is: how not to import some imports if I import it only for debug purposes? :smiley: Do you use some pre-processor techniques created by your own?

2

You can use dynamic imports:

const debug = true // false
if (debug) {
   const foo = await import("some_package");
   foo.bar();
}
2 Likes