prettier-webpack-plugin
prettier-webpack-plugin copied to clipboard
Process your Webpack dependencies with Prettier
Hi! Please, update peerDependencies version
## The devDependency [all-contributors-cli](https://github.com/jfmengels/all-contributors-cli) was updated from `5.4.1` to `5.5.0`. This version is **not covered** by your **current version range**. If you don’t accept this pull request, your project will...
## The devDependency [uuid](https://github.com/kelektiv/node-uuid) was updated from `3.3.2` to `3.3.3`. This version is **not covered** by your **current version range**. If you don’t accept this pull request, your project will...
## The devDependency [prettier](https://github.com/prettier/prettier) was updated from `1.14.3` to `1.15.0`. This version is **not covered** by your **current version range**. If you don’t accept this pull request, your project will...
## The devDependency [webpack](https://github.com/webpack/webpack) was updated from `4.23.0` to `4.23.1`. This version is **not covered** by your **current version range**. If you don’t accept this pull request, your project will...
Are there any options or future plans to include options to exclude files from certain directories (e.g. node_modules), or perhaps to only include files from certain directories?
Currently, the plugin rewrites files just a bit too late, so the bundler runs twice in watch mode. Once on the file changes by user, a second time when the...
I.e , which node version is required for this plugin? It would be ideal if we could match compatibility with Webpack 2.
The test `"throws on invalid prettier config options"` at [\_\_tests\_\_/index.js#L120](https://github.com/hawkins/prettier-webpack-plugin/blob/master/__tests__/index.js#L120) fails, even though it throws the exact error we expect to catch. Why aren't we catching this?