* Remove babel as a dependency
* Migrate from import foo from foo to const foo = require('foo')
* Update module.exports
* Update commander syntax
* Update pkg config and fix stuff
* Make XO happy
* Fix path in tests
* Fix typo
* Fix cleanup
* Debug pkg
* Fix pkg
* Fix process.argv for subcommands
* Run with --harmony-async-await when supported thx igor for help with this trick :D
* Use bash
* Set engines.node in package.json
Bail if no records are found for a domain to allow adding the records.
now alias derp domain.com -d
> [debug] Checking for updates.
> [debug] Up to date (1.0.0).
> [debug] /list: 583.880ms
> [debug] matched deployment derp by url derp.now.sh
> domain.com is a custom domain.
> Verifying the DNS settings for domain.com (see https://zeit.world for help)
> [debug] #1 GET /domains/domain.com: 271.741ms
> [debug] Found domain domain.com with verified:true
> [debug] No records found for "domain.com"
> Verification OK!
A small superficial change to bin/now-deploy.js so that we can specify one or more aliases whilst deploying.
**Examples**
```
now --alias a.com
now --alias a.com --alias b.com
```
We handle the alias assignment serially so that the CLI output makes sense.
**Some thoughts**
- I’m hoping this PR can close out #172
- Aware this PR likely affects #68
- This is a superficial change, really we should update the lib/alias.js to handle multiple domains
If syncing files fails or the user just happens to run `now ls`
before the deployment is ready `https://null` is shown as an URL
to the deployment. Instead of showing `null` we could show
something nice.