Add a registry for CLI Plugins about registry HOT 7 CLOSED

Hmm not sure if my comment here #1 might fits in better in this issue.

Could you elaborate on the libs section?

from registry.

My first thought was how do we tell the cli what should be made available namespaced under this plugin. As an example for i18next we may want some generate lang de that generates German language. The lib is named installer in this case and so the cli would know to add it to the libs folder under an i18next directory and also have a way to extend the current list of commands so a dev could aurelia i18next generate lang de or something.

from registry.

Alright for now I am going to use this method until I hear otherwise :)

from registry.

Copying over @zewa666 's comment from the other issue -

Great, installing through JSPM would also be a better alternative to the current Github download approach.

With regards to cli what would you say if we expand that to an object which might contain the commands?

Like:

{
  "plugins": [
      {  
        "name": "i18next",
        "endpoint": "github",    // where to start looking?  github, npm, gist
        "location": "/zewa666/aurelia-i18next",   // where is it in the end point?
        "cli": {
          commands: {
            parse: 'NAME_OF_EXPORTED_METHOD_FROM_INDEX',
            nextCmd: '...'
          }
        }
      }
  ]
}

EDIT:
It would be also nice to include a property like demo with the path to a working example. Might be helpful for pages listing all plugins (like the FAQ)

from registry.

@zewa666 @ahmedshuhel @EisenbergEffect What do you guys think about including the cli plugins directly in the plugin registry instead of in a separate registry

from registry.

@PWKad I think it's an excellent idea under the circumstances. All the plugins are the part of larger Aurelia ecosystem. So having a common registry totally make sense.

from registry.

This issue is closed and we will incorporate the plugins into the main registry

from registry.