microsoft / microsoft/TypeScript-Website
Playground vNext Wishlist
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 2.6k
- Forks
- 1.5k
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 7
Description
Things we've found useful that should continue to work, very roughly in priority order:
- "Obvious" stuff: completion, quick info, error squiggles, error list
- "Share code" links should be backward compatible
- Configuration of commonly-used options, preferably via tsconfig
- Version selection
- See JS and .d.ts output
Things that would be nice, but likely below a MVP cutline if push comes to shove:
- Automatic type acquisition
- Multiple files support
Feel free to post other things you'd like to see.
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.
Research direction
The issue names no files, tests, or entry points; start by locating the Playground vNext implementation and reviewing the requested MVP capabilities. Confirm which items remain in scope and define completion criteria for the selected capability before making changes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- developer-experience, frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100