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
Currently there seems to be the workaround of "dprint.path" to indicate the path inside local node_modules. But given that modern Yarn doesn't have a node_modules folder, how could one fix this?
For reference, this page mentions how the editor SDK hooks up with Prettier. It would be great to have something like this with dprint :)
The text was updated successfully, but these errors were encountered:
I wonder if the extension should check for a package.json and if there's an entry in there for dprint and no node_modules folder, then it will check yarn's cache for a dprint package that matches the version requirement.
I don't understand the documentation on that page unfortunately.
Currently there seems to be the workaround of
"dprint.path"
to indicate the path inside localnode_modules
. But given that modern Yarn doesn't have anode_modules
folder, how could one fix this?For reference, this page mentions how the editor SDK hooks up with Prettier. It would be great to have something like this with
dprint
:)The text was updated successfully, but these errors were encountered: