Is pixi ready to be used with the new browser modules standard?

[Gargiul0]

I have to start a project with pixi, I wondered if it already works with the newest standard for module import.

https://jakearchibald.com/2017/es-modules-in-browsers/

 

I guess not because I don't see the built pixi.js export structured like in the article.

 

[ivan.popelyshev]

PIXI is written with ES6 but built into ES5. You can clone it (https://github.com/pixijs/pixi.js/tree/) and add your build system or reconfigure existing to get a module that satisfies you. As far as i know, there's no pure ES6 build.

[ivan.popelyshev]

Personally, I think those standarts are uncomplete and uncomfortable. For example, they really should use different extension, not "js" for those kind of files. Java has ".class" and ".jar", why not just copy that system? A directory of js files is built into a module, I would love that

[xerver]

12 hours ago, ivan.popelyshev said:

Personally, I think those standarts are uncomplete and uncomfortable. For example, they really should use different extension, not "js" for those kind of files. Java has ".class" and ".jar", why not just copy that system? A directory of js files is built into a module, I would love that

Electron uses something similar called asar that works pretty well. I think it would be cool to see something like that in browserland (but optimized for network). https://github.com/electron/asar