json:
  nodejs:
    versions:
      - 0.6.19
      - 0.8.4
      - 0.9.0
    aliases:
      0.6.19: 0.6
      0.8.4: 0.8
      0.9.0: 0.9
    default: 0.6.19
recipes:
  - haskell
  - java::multi
  - ant
  - maven3
  - leiningen
  - sbt
  - gradle::tarball
  - kerl
  - rebar
  # Node.js is now co-hosted, too
  - nodejs::multi
  - sweeper
json:
  nodejs:
    versions:
      - 0.4.12
      - 0.6.19
      - 0.8.4
      - 0.9.0
    aliases:
      0.4.12: 0.4
      0.6.19: 0.6
      0.8.4: 0.8
      0.9.0: 0.9
    default: 0.6.19
recipes:
  - haskell
  - java::multi
  - ant
  - maven3
  - leiningen
  - sbt
  - gradle::tarball
  - kerl
  - rebar
  # Node.js is now co-hosted, too
  - nodejs::multi
  - sweeper
Revert "With nodejs 0.9 provided, it is time for 0.4 to go"
Revert "With nodejs 0.9 provided, it is time for 0.4 to go"

This reverts commit dabf8b277f5c060140f8bd212e200713aee4587b.

We figured what caused provisioning failures: a recently introduced npmjs.org
redirects. With a small workaround in place, we can provision 0.4 again.
