dprint config fails to initialize on startup

[johnnycheng0210]

Version: 0.49.0

In our (Canva's) monorepo dprint sometimes fails to initialize in VS Code/Cursor. It fails to resolve our dprint.json config file and prints the following logs to the Output panel:

[INFO] Configuration file not found.
[INFO] Extension active!

It appears to be this issue.

Looking into a bit deeper it seems that prettier doesn't suffer from this issue, it appears that prettier is doing this to resolve the configuration file.

This is affecting numerous Canva engineers and it would be great if this bug is addressed.

Thanks are all your work on dprint! (means a lot to us at Canva)

[dsherret]

I wonder if maybe there should just be a 1 second delay before searching for config files or do a retry on no files found.

[dsherret]

Can you check if the issue still persists in 0.16.5 of the vscode extension?

[johnnycheng0210]

awesome thank you for that change! the error is on/off i'll keep you updated if this has fixed it!

[johnnycheng0210]

hey @dsherret im still seeing this issue on the latest of the vscode extension. its still pretty sporadic but i don't think this has fixed the issue.

[dsherret]

Annoying, I haven’t been able to reproduce it :(

[johnnycheng0210]

would reusing the logic that prettier has be possible to implement? prettier doesn't suffer the issue that dprint does so its a reasonable guess that this would fix our issue

[todor-a]

could this be related?

the output says:

[ERROR] Problem launching dprint. /bin/sh: dprint: command not found

[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.

but it is available

[johnnycheng0210]

@dsherret I've just gotten another report from another user at Canva that they're running into this issue, could you take another look at this issue please? 🙏

Thank you!

[dsherret]

@johnnycheng0210 I published 0.16.6 that has #109

Edit: Doing a 0.16.7 release that will improve it further: #111

[dsherret]

By the way, turning on the "dprint.verbose": true setting might be useful for improving the logs.

@todor-a that sounds like dprint is available in the shell, but not however vscode is launched via the doc on mac. If you launch vscode via the shell where dprint is available via (code .) it should work. That's because the environment your shell populates on startup is different than Mac's default environment. A fix to that is to manually specify a "dprint.path" setting in your user vscode settings https://github.com/dprint/dprint-vscode?tab=readme-ov-file#extension-settings