Release 3.6.0

website/versioned_docs/version-stable/api.md

@@ -99,7 +99,7 @@ Setting `options.ignorePath` (`string | URL | (string | URL)[]`) and `options.wi
 
 If the given `fileUrlOrPath` is ignored, the `inferredParser` is always `null`.
 
-Providing [plugin](plugins.md) paths in `options.plugins` (`string[]`) helps extract `inferredParser` for files that are not supported by Prettier core.
+Providing [plugin](plugins.md) paths in `options.plugins` (`(string | URL | Plugin)[]`) helps extract `inferredParser` for files that are not supported by Prettier core.
 
 When setting `options.resolveConfig` (`boolean`, default `true`) to `false`, Prettier will not search for configuration file. This can be useful if this function is only used to check if file is ignored.
 
@@ -124,10 +124,18 @@ The support information looks like this:
     filenames?: string[];
     linguistLanguageId?: number;
     vscodeLanguageIds?: string[];
+    isSupported?(options: { filepath: string }): boolean;
   }>;
 }
 ```
 
+:::note
+
+Prettier can not ensure that `filepath` exists on disk.\
+When using from APIs(eg: `prettier.format()`), Prettier can not ensure it's a valid path either.
+
+:::
+
 <a name="custom-parser-api"></a>
 
 ## Custom Parser API (removed)