Finally an `npm install hoodie` …

10.0.0 (2015-09-18)

… npm install --save hoodie@next to be precise.

feat

• feat(package): deduped hoodie component bundling (fd4a899)
• feat(package): updated hoodie-server to version 10.1.0 (370f319)
• feat(package): updated hoodie-server to version 10.2.0 (063c8b0)
• feat(package): updated hoodie-server to version 6.1.0 (cf2f0df)
• feat(plugins): added hoodie error test (6051c9a)
• feat: initial bunlding and testing (6fe4bb7)
• feat: pass options via CLI, .hoodierc and environment variables (c83f9bf), closes hoodiehq/hoodie-server#378 hoodiehq/hoodie-server#373 hoodiehq/hoodie-server#222

fix

• fix(package): updated hoodie-server to version 10.0.2 (15becb0)
• fix(package): updated hoodie-server to version 5.0.4 (dd41313)
• fix(package): updated hoodie-server to version 5.0.5 (0fa5b5e)
• fix(package): updated hoodie-server to version 5.0.6 (a825108)
• fix(package): updated hoodie-server to version 6.0.1 (84ce5d8)
• fix(package): updated hoodie-server to version 6.0.2 (e02dd9b)
• fix(travis): avoid bundling an invalid cache by disabling it altogether (8ece47d)

BREAKING CHANGE

• Before the config for hoodie was read from multiple places.
  Some things were read from CLI arguments and others from the environment.
  Hoodie is now using rc together with
  nopt, so one can provide any option
  via either a .hoodierc file (in json or ini format), environment variables,
  or command line arguments. For a full list of commands run
  npm start -- --help.
• If one wanted to use an external CouchDB they had to set the COUCH_URL
  environment variable. You can now set the hoodie_dbUrl environment variable,
  add an "dbUrl" field to your .hoodierc file, or pass --db-url to the CLI.
• Passing an HOODIE_ADMIN_USER and HOODIE_ADMIN_PASS via the environment does
  no longer work. Also letting Hoodie generate a password for an admin _hoodie
  user when using an external CouchDB does no longer work. Because a CouchDB is
  now only used in production scenarios Hoodie will no longer do this for you.
  You have to pass the username and password of an admin user inside of the URL
  (https://admin:password@example.com/). When letting Hoodie start a PouchDB
  Server for you it will generate an internal admin password just like before,
  but you can specify your own password using the adminPassword option.
• The --custom-ports CLI argument is gone. You can now pass each port
  individually using the port, adminPort and dbPort options.
• When starting Hoodie for the first time you will now have to pass an
  adminPassword. This could be done via the HOODIE_SETUP_PASSWORD environment
  variable, or a prompt before.