How to use pixi-spine and pixi v3 with require.js about spine HOT 7 CLOSED

Why are you shimming pixi? It has a UMD export so it should export fine in rjs environments. The shim could liekly be shadowing the forced global export that plugins rely on. (pixi exports as UMD and always to window.PIXI)

from spine.

Just desperate tries, since PIXI is now exposed globally, but seems that then is not needed :). Still if we remove it we get the same problem.
Minified version the exception is in this line:

e.exports = PIXI.spine = {Spine: t("./Spine"),SpineRuntime: t("./SpineRuntime"),loaders: t("./loaders")}

For some reason it tries to load browserify, as you can see in the network tab http://snag.gy/0Bez0.jpg

from spine.

Seems the examples have a similar problem which is not related to require.js http://pixijs.github.io/examples/index.html?s=spine&f=dragon.js&title=Dragon&plugins=pixi-spine

from spine.

The examples has a bad version of spine being uploaded on accident, I've fixed it.

As for your error, this happens when 1) pixi is not loaded first so the global doesn't exists, or 2) The global is shadowed by a shim or some such.

If you have a small testbed I can look at this further.

from spine.

Tried doing the testbed but couldn't. We ended up moving from requirejs to webpack and that solve the issue. Now we have another regarding spine looking for the atlas with the same the json file. This is a problem because we cache bust the files, so even if both are called dragon.png and dragon.atlas, when we build it it will have different rev.

BTW which pattern of UMD are you using https://github.com/umdjs/umd for both pixi and the pixi-spine plugin ?

from spine.

We use the browserify standalone option, so whatever they do. As for the new issue, I would open a separate ticket.

from spine.

Thanks for help :) will do

from spine.