Loading assets before renderer got created

[zOadT]

Hey 👋 First of: Great work on v8, looking forward to the release!

While doing some tests with v8 I noticed a new behaviour:

const asset = await PIXI.Assets.load(image); // (A)
const renderer = await PIXI.autoDetectRenderer({}); // (B)

console.log('asset', asset); // asset === null

When you put line (A) after (B) the asset will be loaded normally. I guess this is because the asset loading is dependent on which renderer gets chosen in the construction of the renderer.

In my current setup imports (like in line (A)) get generated by Webpack and run before user code that creates renderers or PIXI.Applications. I can initialise a renderer in the generated code but then either

1. The user has to import the generated renderer. Not too bad, but I would prefer if the user doesn't have to think about importing a renderer instead of creating one.
2. Let the user initialise a second renderer. I would be interested if this creates a lot of overhead or is basically negligible. It sounds unpleasant, but probably its actually not really that bad?

If the second case would resolve in some nasty behaviour, could it make sense to move the logic of importing and registering the necessary code into a separate function that gets exported by pixi?

This is not a critical issue for me though, as it just concerns my base code for game jams, so solution 2 would probably fine 😄 But wanted to share it with you anyway to hear your opinion whether other users of pixi could also be affected