You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
diff --git a/node_modules/@pota/cli/lib/loadCommands.js b/node_modules/@pota/cli/lib/loadCommands.js
index 15fe75a..d6beee2 100644
--- a/node_modules/@pota/cli/lib/loadCommands.js+++ b/node_modules/@pota/cli/lib/loadCommands.js@@ -2,7 +2,7 @@ import { pathToFileURL } from 'url';
import { resolve, isAbsolute, extname } from 'path';
export function resolveModulePath(path, root) {
if (extname(path))
- return isAbsolute(path) ? pathToFileURL(path).toString() : resolve(root, path);+ return pathToFileURL(isAbsolute(path) ? path : resolve(root, path)).toString();
// if the path does not have an extension, then assume its a npm package
return path;
}
Today I used patch-package to patch
@pota/[email protected]
for the project I'm working on.Relative paths to pota commands were not properly resolved on windows starting with
c:
instead offile://c/
Here is the diff that solved my problem:
This issue body was partially generated by patch-package.
The text was updated successfully, but these errors were encountered: