Bug: [v8] Rollup export build error after upgrade to v8 - working on v7 about pixijs HOT 4 CLOSED

I would probably try to look for a Rollup plugin that could statically inline dynamic imports. We are now using dynamic imports which helps tree-shaking and up-front filesize costs for some bundlers. Since we added another big renderer in v8, it's just not practical to load everything at once.

Quick search found this issue:
rollup/rollup#3490

from pixijs.

Thanks for the issue reference @bigtimebuddy, I checked it and ESM on CanIUse:

The ESM is already supported by ~96% of browsers, and the version range is great.

Changing the build to use esm directly looks to be the right approach.

I still have other things broken after migrate to v8 that is mentioned on the following issue: #10299

So, when I run the project, on the browser I get the following error:

Uncaught TypeError: Failed to resolve module specifier "@pixi/core". Relative references must start with either "/", "./", or "../".

The browser was not able to load the Pixi core, and those are the built files:

I'll wait for the other issue and keep doing some tests to see how to fix it.

from pixijs.

hey guys, question about v8 and the ESM build, the following code is being included on the top of the build files:

import { SCALE_MODES, extensions as extensions$1, ExtensionType as ExtensionType$1, ObjectRenderer, Buffer as Buffer$1, utils, Shader, Program, Matrix as Matrix$1, Geometry as Geometry$1, Texture as Texture$1, groupD8 as groupD8$1, DRAW_MODES } from '@pixi/core';
import { Container as Container$1, Bounds as Bounds$1 } from '@pixi/display';

I don't have @pixi/display and @pixi/core as dependencies or dev dependencies on my project because I didn't need it on v7, but now it is being included on the build file and when the browser try to load it, I get the following error Uncaught TypeError: Failed to resolve module specifier "@pixi/core". Relative references must start with either "/", "./", or "../". because it is not being included on build file.

if I define it to load from CDN it works and the error goes away:

      paths: {
        '@pixi/core': 'https://cdn.skypack.dev/@pixi/core',
        '@pixi/display': 'https://cdn.skypack.dev/@pixi/display',
      },

is this an expected behavior/approach? I would like to not need this map with the CDN to fill all the needs of Pixi on my build...

can someone please give me some guidance about it? thanks!

from pixijs.

the issue is that @pixi/tilemap and other plugins are still on v7, so they need to be upgraded, after that, the build will work as expected.

Closing as there's nothing to be done here by Pixi team.

from pixijs.