Update Dojo url in package.json

[dylans]

Once dojo.io is live, update url in various package.json repos to dojo.io so that it links to that on npm for future releases.

[rishson]

Update repo url and package.json url to https://dojo.io in:

• dojo-app
• dojo-actions
• dojo-cli
• dojo-cli-build
• dojo-cli-create-app
• dojo-cli-test-intern
• dojo-compose
• dojo-core
• dojo-crypto
• dojo-dataviz
• dojo-dgrid
• dojo-dom
• dojo-examples
• dojo-has
• dojo-i18n
• dojo-interfaces
• dojo-loader
• dojo-routing
• dojo-shim
• dojo-stores
• dojo-streams
• dojo-test-extras
• dojo-widgets
• dojo-widget-core

In addition:

• update dojo-package-template package.json

[rishson]

@agubler if we wanted to make this less painful, then would we alter grunt-dojo2 's package to check the package.json 's homepage and autocorrect to dojo.io or would it be better to do this, or some other solution?

[agubler]

@rishson It certainly is possible to enhance the release task to correct package.json meta data on release.

We could also potentially create a task that can auto update package.json meta independently of the release.

[rishson]

@agubler yup and I have a PR ready to go for enhancing the release task. Would you prefer a generic 'alter metadata' task, e.g. here, or a hardcoded update url check to the release task?

[rishson]

Most repos will now be updated by #183

[kitsonk]

Let's try to action this and close it out. @eheasley if Dylan doesn't have the time, we should assign it to others.

[kitsonk]

Again, please action this.

[edhager]

Skipping dojo/examples because it does not have a package.json file.

[edhager]

PRs have been created for the unchecked (for now) repos above.

[edhager]

All PRs have been landed.