lukebatchelor
lukebatchelor
It would be super hard to tell from this information alone. Are you able to push up a minimally reproducible test repo that we could look at, with instructions on...
Oh wow, that would be awesome, thank you!
Hmmm... I did notice it was moved, do you think itd be better to have the checked up location, or separated into another module?
LGTM, but the tests seem to fail in CI?
Hiya. Thanks for the contribution. None of the core maintainers do much of the way of windows development so finding and fixing these sorts of issues can be a pain...
Hiya, you don't need to run bolt init, that's just to run yarn init and probably isn't implemented. Have you added the workspaces field to your package.json?
Can you link a repo that we can test in? Fyi, you also don't need to bolt init, that's just an alias for yarn init.
@pastelsky , I don't think they're related at all but I've released that change in 0.22.6. That should fix your `bolt p` problems. This issue looks to be something wrong...
What do you mean by "before we can see them"? Also, am.i right then in assuming this would require custom logic in each tool (or config of tool) to support...