codesandbox / codesandbox/codesandbox-client
TypeScript starter sometimes fails to find types because its tsconfig does not have `"moduleResolution": "node"`
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 13.6k
- Forks
- 2.4k
- Avg merge
- 6d 19h
- Merged PRs (30d)
- 2
Description
🐛 bug report
Preflight Checklist
- I have read the Contributing Guidelines for this project.
- I agree to follow the Code of Conduct that this project
adheres to. - I have searched the issue tracker for an issue that matches the one I want
to file, without success.
Description of the problem
Some Sandboxes cannot resolve types.
How has this issue affected you? What are you trying to accomplish?
I want to use TypeScript in my projects.
To Reproduce
I can't seem to reproduce—it sometimes works! But here's one where it doesn't:
Link to sandbox: link
If I download the first (broken) sandbox and open it in VSCode, I get this suggestion:
So I think the issue is to a missing "moduleResolution": "node" in the TSConfig.
Here's a Sandbox where I've added that line, and where types are working correctly.
Contributor 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.
Research direction
Start by inspecting the TypeScript starter configuration used by the linked broken Sandbox and compare it with the fork where types work correctly. Confirm whether the missing moduleResolution setting explains the type lookup failure, then verify the fix by opening the downloaded Sandbox in VSCode and checking that types resolve.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- developer-experience, tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100