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
-
Goals
Non-goals
No response
Background
Some task has multiple variations. e.g.:
build:cjs
/build:esm
/build:browser
/build:jsr
test:jest
/test:type
/test:react-18
/test:storybook
Currently, 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:type
against multiple versions of TypeScript:test:type:current
test:type:tsc-5.4
test:type:tsc-5.4
test:type:tsc-5.2
test:type:tsc-4.0
Proposal
it is nicer to be able to run them all by doing
turbo run test:type:*
.and define the task in
turbo.json
as"test:type:*": { ... }
related discussion but not the same: #7261
Beta Was this translation helpful? Give feedback.
All reactions