aurelia / registry Goto Github PK

The registry should contain basic information about each plugin. To allow the registry to expand with additional properties, I propose we use an array of objects instead of a simple key:value pair. Example -

{
  "plugins": [
      {  
        "name": "i18next",
        "endpoint": "github",    // where to start looking?  github, npm, gist
        "location": "/zewa666/aurelia-i18next",   // where is it in the end point?
        "cli": true    // has a cli plugin to integrate?
      }
  ]
}

This will allow us to start by defining the required location information and possibly expand in the future to support other properties or special settings.

This would also allow us to start with using JSPM at the very least and potentially expand in to other package managers, since it is not tied directly.

This corresponds to the issue in the CLI.

The registry should contain basic information about each plugin that is available for the CLI. To allow the registry to expand with additional properties, I propose we use an array of objects instead of a simple key:value pair. Example -

{
  "plugins": [
    "i18next": {
      "endpoint": "github",    // where to start looking?  github, npm, gist
      "location": "/zewa666/aurelia-i18next",   // where is it in the end point?
      "libs": [
        "installer", "editor"
      ]    // what libs should be installed in the cli/lib directory?
    }
  ]
}

This will serve as the list for the docs app to pull down the official list of repositories.

This should also be updated through a gulp task.

Thinking about webpack, npm becomes relevant as well, no?