Installing normal Aurelia plugins, what Im I doing wrong?

Is there anything special wee need to do to make normal plugins work in aurleia-cli This is what I tried`:

• 1: Forked the skeleton-plugin, incase Ive messed up what ever I have in my custom plugin.
• 2: Installed “default esnext” app with aurelia-cli
• 3: Installed plugin-skeleton : npm install git://github.com/vegarringdal/skeleton-plugin.git --save
• 4: Added to main.js this: .plugin('aurelia-skeleton-plugin') under feature(‘resources’) line
• 5: Added to aurelia.json

{
            "name": "aurelia-skeleton-plugin",
            "path": "../node_modules/aurelia-skeleton-plugin/dist/amd",
            "main": "index"
          },

But this didnt go very well, I get

Uncaught TypeError: h.load is not a function

and

Unhandled rejection Error: Load timeout for modules: template-registry-entry!aurelia-skeleton-plugin/hello-world.html_unnormalized2,template-registry-entry!aurelia-skeleton-plugin/hello-world.html,text!aurelia-skeleton-plugin/hello-world.html_unnormalized3,text!aurelia-skeleton-plugin/hello-world.html http://requirejs.org/docs/errors.html#timeout

Im sure there is a easy fix for this, so any hints would be great.

[adriatic]

I would suggest to make this restriction more pronounced - I completely missed it and we as a team spent a lot more time trying to make our bridges to work with RequireJS.

Now, speaking of RequireJS: why was that chosen as the leading actor in aurelia-cli? Other than knowing that GistRun was developed that way, there were no hints about RequireJS so far.

Why asking this? Because aurelia-cli became the greatest hit in no time, and now all our bridge users keep asking why is it that we did not deliver aurelia-cli based creation of apps that use these bridges. Pretty unenviable position, I might say with a does of humor 😃

[krig]

Just wanted to note that I’m trying to follow the Contact Manager Tutorial in the documentation, and hit this same issue. setting stub: false resolved the problem. Not sure if I missed a step somewhere, or if this is a problem that actually affects the tutorial.