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
When opening a folder like this in VS code where there are multiple projects which each has their own version of dprint installed, the extension fails to find dprint:
[ERROR] Problem launching dprint. '"dprint"' is not recognized as an internal or external command,
operable program or batch file.
[ERROR] Error initializing dprint. Ensure it is globally installed on the path (see https://dprint.dev/install) or specify a "dprint.path" setting to the executable.
[ERROR] Problem launching dprint. '"dprint"' is not recognized as an internal or external command,
operable program or batch file.
[ERROR] Error initializing dprint. Ensure it is globally installed on the path (see https://dprint.dev/install) or specify a "dprint.path" setting to the executable.
[ERROR] Problem launching dprint. '"dprint"' is not recognized as an internal or external command,
operable program or batch file.
[ERROR] Error initializing dprint. Ensure it is globally installed on the path (see https://dprint.dev/install) or specify a "dprint.path" setting to the executable.
[INFO] Configuration file not found.
[INFO] Extension active!
When opening either project-a or project-b folder in VS code, everything works as expected.
A work around is to also install dprint with npm in the root folder but this isn't optimal.
Solution:
The extension should be able to find the dprint executable closest to the file being formatted. Especially when there is a .dprint.jsonc file in the project.
I'm happy to contribute, if i'm pointed in the right direction.
Thanks!
The text was updated successfully, but these errors were encountered:
I created a git repo to better demonstrate the problem:
https://github.com/neotrow/dprint-issue
When opening a folder like this in VS code where there are multiple projects which each has their own version of dprint installed, the extension fails to find dprint:
When opening either
project-a
orproject-b
folder in VS code, everything works as expected.A work around is to also install
dprint
withnpm
in the root folder but this isn't optimal.Solution:
The extension should be able to find the
dprint
executable closest to the file being formatted. Especially when there is a .dprint.jsonc file in the project.I'm happy to contribute, if i'm pointed in the right direction.
Thanks!
The text was updated successfully, but these errors were encountered: