plugin with other plugins dependencies fails on the optimizer about r.js HOT 2 CLOSED

Right, I have hit this too, and it is a bit tricky to fix. Normally dependencies are not completely evaluated, the AST parser just pulls out the name, module dependencies and evaluates that for the module. This is important since some modules may depend on browser-specific, or env-specific variables (like window or document). However, for plugins, it does evaluate the whole file. But the system only knows it is a plugin if the name has been used as part of plugin resource.

What I need to do is allow a module definition to be "reset" if already defined when it is later seen as a plugin, or used as a plugin dependency. However, that can be tricky to know (ideally if 'text' had dependencies, those would be completely evaluated). I think it may work out given the synchronous nature of module loading in the optimizer, but it will require some fancier bookkeeping and module reset logic.

I have already hit a few cases where it would be nice to reuse the text plugin as a basis for other plugins (like the coffeescript plugin), but I ended up inlining the text plugin work in the other plugin to get around the limitation outlined in this issue. So I definitely see the usefulness of supporting it, it just make take a bit of time to sort out.

As a hack, if you specify a text resource first in the build dependencies for a layer, before the above plugin is used, then it may work out.

from r.js.

This should now be fixed in the the latest code. Try this snapshot.

from r.js.