Follow-up to https://github.com/vercel/next.js/pull/27463 this adds a note about installing as `devDependency` instead of changing the default install command as the plugin being a `devDependency` might cause issues unless wrapped in a `process.env` check.
## Documentation / Examples
- [x] Make sure the linting passes
This confused me a lot, because in the case of `withBundleAnalyzer({})` it will ignore any previous config and basically override everything.
Furthermore, it makes more sense to move the call with `enabled` option inside so it's aligned with other plugins approach.
* Run prettier over packages/**/*.js
* Run prettier over packages/**/*.ts
* Run prettier over examples
* Remove tslint
* Run prettier over examples
* Run prettier over all markdown files
* Run prettier over json files