Automagically determine rewrite paths
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 38/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- typescript
- Domain
- testing-qa, tooling
Research direction
Start by reviewing how TypeScript support currently handles rewrite paths and locates the project configuration. Check TypeScript's support for extended configurations and apply the stated nearest-configuration assumption. Done means source directories are resolved from that configuration without requiring users to provide rewrite paths.
Written by the indexing model from the issue text.
Description
It should be possible to resolve the TypeScript configuration (including extended configurations) to determine what source directories are output where. That way, users won't have to configure the rewrite paths.
I'm not sure if TypeScript supports multiple configuration files within a project. Babel does, but AVA's Babel support ignores such configuration files. It'll be simplest to do the same here.
This means we'll assume the nearest TypeScript configuration file is in the project directory itself.
- Dominant language
- JavaScript
- Stars
- 76
- Forks
- 19
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
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 avajs/typescript
-
documentation help wanted
Difficulty 1/5 Under an hour Newbie friendliness 72/100
avajs/typescript#8 ·
-
Ava watch does not work with pre-compile optionMay be free again A pull request for this issue was closed without being merged. Openbug help wanted
Difficulty 4/5 3-5 days Newbie friendliness 35/100
avajs/typescript#33 · 14 comments · 3 reactions ·
-
Difficulty 5/5 Over a week Newbie friendliness 20/100
avajs/typescript#29 · 12 comments ·
-
bug help wanted
Difficulty 3/5 1-2 days Newbie friendliness 35/100
avajs/typescript#26 · 2 comments · 1 reaction ·
-
enhancement help wanted
Difficulty 4/5 3-5 days Newbie friendliness 25/100
avajs/typescript#25 ·
All issues in avajs/typescript
Similar issues
-
change request evaluating
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
sindresorhus/eslint-plugin-unicorn#3907 ·
Maintainers usually reply within 1 day
-
Android bug feature/error-tracking react-native team/error-tracking
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
PostHog/posthog-js#5310 · 1 comment ·
Maintainers usually reply within 1 day
-
Add Prettier and a format-check CI jobPossibly taken @ezekielnathaniel070-ai claimed this today. Openbackend frontend good first issue Stellar Wave
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
OlaGreat/starbound-realms#98 · 1 comment ·
-
Add AudiobookshelfOpenapp request good first issue help wanted self-hosted app
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Secra-Solutions/Conector#15 ·
-
Complexity: See issue making label epic good first issue Issue Making: Level 1 P-Feature: Project Info and Page role: back end/devOps role: front end size: 0.25pt time sensitive
Difficulty 2/5 Under an hour Newbie friendliness 65/100
Maintainers usually reply within 1 day