[heft] heft-typescript-plugin - error with an array at the extends property
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 55/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Stale
- Tech stack
- typescript
- Domain
- build-system
Research direction
Start with heft-plugins/heft-typescript-plugin/src/schemas/typescript.schema.json and compare its extends definition with the TypeScript tsconfig schema linked in the issue. Reproduce the failure using a Heft TypeScript project with an extends array, then update the schema so the documented configuration is accepted and confirm the project builds successfully.
Written by the indexing model from the issue text.
Description
Summary
I am trying to extend my tsconfig.json with a rig config and a custom config from a multi project repo. So my tsconfig.json looks something like this:
{
"extends": [
"./node_modules/@microsoft/spfx-web-build-rig/profiles/default/tsconfig-base.json",
"../../tsconfig.base.json"
]
}
When I am trying to build the project, this fails somewhere in the heft-typescript-plugin:
The schema for TypeScript allows this syntax. The schema in the heft-typescript-plugin does not.
Repro steps
I am working with a SPFx setup which is using heft since version 1.22.
So the easiest way would be to
- Create a SPFx project
- Change the tsconfig to include an array
But a simple heft typescript project should work too.
Details
What do you think is the cause of this problem? see above
How do you think we should fix this? extend the schema for allowing arrays
Standard questions
Please answer these questions to help us investigate your issue more quickly:
| Question | Answer |
|---|---|
@rushstack/heft version? |
1.1.2 |
| Operating system? | windows / linux (wsl) |
| Would you consider contributing a PR? | Maybe |
Node.js version (node -v)? |
22.17.0 |
- Dominant language
- TypeScript
- Stars
- 6.5k
- Forks
- 708
- Avg merge
- 4d 13h
- Merged PRs (30d)
- 62
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from microsoft/rushstack
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
All issues in microsoft/rushstack
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
security
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
IBM/node-sdk-core#373 ·
-
e2e-failure ready-to-code
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
chore
Difficulty 2/5 1-3 hours Newbie friendliness 88/100