Feature/plugins

[tjbenton]

Make sure that you merge the other PRs first because this PR is built off of those.

This is complete with tests nyc ava --verbose packages/fakeit-core/test and it's pretty throughly documented.

The way it will work is you import the Api into the cli package at the top then instantiate it and when you do that it will load any configs that have been set, as well as any plugins that have been installed.

Users can define options in a fakeitfile.js, package.json under the fakeit key, as well as pass in arguments to the cli. The only option that the cli will not handle is the plugins option, that's because it's not possible since we have to load the plugins before the cli is rendered so that any plugins that have a cli function are passed in and run correctly. This should not affect a single user since they have 4 other methods of including plugins.

• fakeitfile.js

  function somefunction() {}
  module.exports = {
    plugins: [ somefunction, './some-relative-file.js', 'some-installed-pacakge']
  }

• package.json fakeit key

  {
    "fakeit": {
      "plugins": [ "./some-relative-file.js", "some-installed-pacakge" ]
    }
  }

• package.json dependencies, devDependencies, and peerDependencies are filtered through to find any packages that match @fakeit/(format|plugin)-.*

  {
    "dependencies": {
      "@fakeit/format-json": "*"
    }
  }

• node_modules does a glob search on the node_modules folder for @fakeit/(format|plugin)-.*

Finally all these ways are combined and reduced to a unique array and then required(if a string) and then run them.