Don't use package.json to load dependencies.

Nobody has claimed this yet.

This was an early decision choice which I felt would help reduce boilerplate, and it does. On the other hand, it's magic.

EDIT: Grammar.

```js
module.exports = {
*lint(fly) {
yield fly.source(js).xo({ esnext: true })
},
*scripts(fly) {
yield fly.source(js).babel({ presets: ["es2015"] }).target(`${dist}/js`)
},
*styles(fly) {
yield fly.source(sass).sass({ outputStyle: "compressed" }).autoprefixer().target(`${dist}/css`)
},
*build(fly) {
yield fly.parallel(["lint", "scripts", "styles"])
}
}
```

If you already know the API, you'd know that `.source` and `.target` are core and that `.sass` or `.xo` must be plugins, but what about plugins like `.concat`.

Start by tracing how package.json is used to load dependencies for the JavaScript task configuration shown in the issue. Compare core methods such as .source and .target with plugins such as .sass, .xo, and .concat. The issue does not define a concrete replacement or acceptance criteria, so the desired behavior would need to be clarified before implementation.

Written by the indexing model from the issue text.