Replies: 1 comment
-
|
Currently, me workaround is using {
"scripts": {
"test:type": "run-p test:type:*",
"test:type:current": "tsc --no-emit",
"test:type:54": "buddy exec --alias=ts-54 \"tsc --no-emit\"",
"test:type:53": "buddy exec --alias=ts-53 \"tsc --no-emit\"",
"test:type:50": "buddy exec --alias=ts-50 \"tsc --no-emit\""
}
}The downside is the console log are all mingled under |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Goals
Non-goals
No response
Background
Some task has multiple variations. e.g.:
build:cjs/build:esm/build:browser/build:jsrtest:jest/test:type/test:react-18/test:storybookCurrently, we need to define them one by one in
turbo.json,and we have to specify them explicitly as
turbo run test:jest test:type test:storybook.In one specific case, I am trying to run
test:typeagainst multiple versions of TypeScript:test:type:currenttest:type:tsc-5.4test:type:tsc-5.4test:type:tsc-5.2test:type:tsc-4.0Proposal
it is nicer to be able to run them all by doing
turbo run test:type:*.and define the task in
turbo.jsonas"test:type:*": { ... }related discussion but not the same: #7261
Beta Was this translation helpful? Give feedback.
All reactions