How about that guys?
It could also detect the presence of a .yarnrc file.
Or, as an alternative, support adding a way to add project-local configuration that vsce could pick up and would allow you to specify defaults for --yarn (as well as --baseContentUrl, --baseImagesUrl, and a few others). Something like one of the following:
package.json (since that's used for other settings related to the extension).vscerc or other configuration file.It could also detect the presence of a .yarnrc file.
Nice catch, you're right.
Yes, that would be very useful, but I believe it deserves its own Issue. To do that, I strongly recommend cosmiconfig. :-)
I created a PR for this since I'd also find it useful.
Another detection method might be the presence of a "workspaces" key in package.json, since that is generally indicative of a project using yarn workspaces.
Another detection method might be the presence of a
"workspaces"key inpackage.json, since that is generally indicative of a project using yarn workspaces.
It seems that npm v7+ is going to support Yarn workspaces, so I think it's not a good idea to use as detection criteria.
@joaomoreno are you planning to release this anytime soon?