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
So, I've run into an interesting issue with a workspaces build, where when i'm running in the CI environment, I am skipping building all the modules, because we have workspaces that the CI environment isn't interested in building.
For example, one of the packages is a React Native project that we use as an example project, and in the postinstall script, as this package is never published, we run pod install to make it quick and easy for someone to jump into working.
However, in GitHub Actions, I'm running with --mode=skip-build on the initial yarn install command in the project root for the CI environment.
At this point, I've now got the problem that I want to build a few specific workspace trees, and the dev tools that they use.
I've tried yarn workspaces focus from inside the package folder.
I've tried yarn workspaces focus <package.json[name]> from the workspaces root.
I've tried yarn rebuild ...deplist but that ends up building everything because of the initial command.
I saw #3166 and was wondering if perhaps a possible solution for wanting to process the tree from a specific point would be something like..
yarn build --deps eslint which would build eslint, and all its dependencies. yarn build eslint which would only build eslint, and none of its dependencies.
I made this a discussion, because I'm not sure if I'm missing an obvious part of the workflow, or if there is some other method to achieve this already. Plus, the issue I linked already describes a workable solution for me, but I think goes against the documented behaviour of rebuild, which is to build all unbuilt dependencies.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
So, I've run into an interesting issue with a workspaces build, where when i'm running in the CI environment, I am skipping building all the modules, because we have workspaces that the CI environment isn't interested in building.
For example, one of the packages is a React Native project that we use as an example project, and in the
postinstall
script, as this package is never published, we run pod install to make it quick and easy for someone to jump into working.However, in GitHub Actions, I'm running with --mode=skip-build on the initial
yarn install
command in the project root for the CI environment.At this point, I've now got the problem that I want to build a few specific workspace trees, and the dev tools that they use.
I've tried
yarn workspaces focus
from inside the package folder.I've tried
yarn workspaces focus <package.json[name]>
from the workspaces root.I've tried
yarn rebuild ...deplist
but that ends up building everything because of the initial command.I saw #3166 and was wondering if perhaps a possible solution for wanting to process the tree from a specific point would be something like..
yarn build --deps eslint
which would build eslint, and all its dependencies.yarn build eslint
which would only build eslint, and none of its dependencies.I made this a discussion, because I'm not sure if I'm missing an obvious part of the workflow, or if there is some other method to achieve this already. Plus, the issue I linked already describes a workable solution for me, but I think goes against the documented behaviour of rebuild, which is to build all unbuilt dependencies.
Beta Was this translation helpful? Give feedback.
All reactions