Fix prettier config resolution when no prettierFilePath is provided #114
  Add this suggestion to a batch that can be applied as a single commit.
  This suggestion is invalid because no changes were made to the code.
  Suggestions cannot be applied while the pull request is closed.
  Suggestions cannot be applied while viewing a subset of changes.
  Only one suggestion per line can be applied in a batch.
  Add this suggestion to a batch that can be applied as a single commit.
  Applying suggestions on deleted lines is not supported.
  You must change the existing code in this line in order to create a valid suggestion.
  Outdated suggestions cannot be applied.
  This suggestion has been applied or marked resolved.
  Suggestions cannot be applied from pending reviews.
  Suggestions cannot be applied on multi-line comments.
  Suggestions cannot be applied while the pull request is queued to merge.
  Suggestion cannot be applied right now. Please check back later.
  
    
  
    
Problem
The prettier config resolution was failing when no
prettierFilePathoption was explicitly provided in the plugin configuration. This affected users who expected the plugin to automatically discover prettier config files (.prettierrc.json,.prettierrc.yml, etc.) in their project root.Root Cause
The issue was in the fallback behavior in
src/index.ts. Whenoption.prettierFilePathwas not provided, the code fell back to usingconfig.root(a directory path):However,
prettier.resolveConfig()expects a file path to search from, not a directory path. When passed a directory directly, it returnsnull, causing prettier configuration to be ignored.Solution
Modified the fallback to provide a file path within the project root instead of the directory itself:
This allows prettier to properly search for configuration files starting from the project root when no explicit
prettierFilePathis provided.Testing
.jsonconfig files work when specified viaprettierFilePath.ymlconfig files work when specified viaprettierFilePath.cjsconfig files continue to work (no regression)Changes
joinfromnode:pathjoin(config.root, 'package.json')instead ofconfig.rootFixes #113.
Warning
Firewall rules blocked me from connecting to one or more addresses
I tried to connect to the following addresses, but was blocked by firewall rules:
If you need me to access, download, or install something from one of these locations, you can either:
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.