massive update, probably broken

[dotfiles/.git] / .config / coc / extensions / node_modules / coc-json / node_modules / vscode-languageserver / lib / node / files.d.ts

diff --git a/.config/coc/extensions/node_modules/coc-json/node_modules/vscode-languageserver/lib/node/files.d.ts b/.config/coc/extensions/node_modules/coc-json/node_modules/vscode-languageserver/lib/node/files.d.ts
new file mode 100644 (file)
index 0000000..4feae3c
--- /dev/null
+++ b/.config/coc/extensions/node_modules/coc-json/node_modules/vscode-languageserver/lib/node/files.d.ts
@@ -0,0 +1,19 @@
+/**
+ * @deprecated Use the `vscode-uri` npm module which provides a more
+ * complete implementation of handling VS Code URIs.
+ */
+export declare function uriToFilePath(uri: string): string | undefined;
+export declare function resolve(moduleName: string, nodePath: string | undefined, cwd: string | undefined, tracer: (message: string, verbose?: string) => void): Promise<string>;
+/**
+ * Resolve the global npm package path.
+ * @deprecated Since this depends on the used package manager and their version the best is that servers
+ * implement this themselves since they know best what kind of package managers to support.
+ * @param tracer the tracer to use
+ */
+export declare function resolveGlobalNodePath(tracer?: (message: string) => void): string | undefined;
+export declare function resolveGlobalYarnPath(tracer?: (message: string) => void): string | undefined;
+export declare namespace FileSystem {
+    function isCaseSensitive(): boolean;
+    function isParent(parent: string, child: string): boolean;
+}
+export declare function resolveModulePath(workspaceRoot: string, moduleName: string, nodePath: string, tracer: (message: string, verbose?: string) => void): Promise<string>;