Replies: 5 comments
-
Can we detect that a project is using workspaces and run |
Beta Was this translation helpful? Give feedback.
-
Yes, workspaces are actually detectable from root package.json and it would solve this particular issue with yarn. Cool,
Anyway, what about the problem in general, do you not think these cases might happen with any arbitrary command that wouldn't work on user's machine for any reason - be it aliases, etc. Being able to map a task's command to a "different" one could maybe come handy. |
Beta Was this translation helpful? Give feedback.
-
Not many tasks run shell commands and I think aliasing them shouldn't be in the scope of Mrm. But supporting Yarn workspaces makes a lot of sense, since installing packages is a core feature. Mind sending a pull request with a fix? |
Beta Was this translation helpful? Give feedback.
-
Can you point me to an appropriate file? I think I will just check package.json for the |
Beta Was this translation helpful? Give feedback.
-
Sounds like a good plan! |
Beta Was this translation helpful? Give feedback.
-
So I have encountered an interesting issue while trying to run a task and I have no idea how to name it or even what to ask for. I guess I will just leave it here for your consideration.
The problem is that I am using yarn workspaces and in order to install something to root, I must explicitly call yarn with
-W
flag.Maybe perhaps if I could set an alias for
yarn
toyarn -W
temporarily..? No idea what would be the best solution, but I think cases like this may happen not only with yarn.Beta Was this translation helpful? Give feedback.
All reactions