refer to #216

In our team's workflow, prettier-eslint isn't a required dependency that we want to include in our project's package.json. While this extension has moved away from installing prettier-eslint (requiring local installation instead), this approach doesn't fully address cases where teams:

• Prefer global installations
• Use centralized style management
• Maintain custom configurations

I suggest adding a customPath configuration option that would allow users to specify an absolute path to their prettier-eslint installation.
I'd be happy to implement this feature and submit a PR.