microsoft / microsoft/TypeScript
A flag to replace removed syntax with blank space
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 111k
- Forks
- 14.3k
- Avg merge
- 2d 4h
- Merged PRs (30d)
- 132
Description
🔍 Search Terms
Blank space
ErasableSyntax
Node.js Strip Types
Type Stripping
✅ Viability Checklist
- This wouldn't be a breaking change in existing TypeScript/JavaScript code
- This wouldn't change the runtime behavior of existing JavaScript code
- This could be implemented without emitting different JS based on the types of the expressions
- This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, new syntax sugar for JS, etc.)
- This isn't a request to add a new utility type: https://github.com/microsoft/TypeScript/wiki/No-New-Utility-Types
- This feature would agree with the rest of our Design Goals: https://github.com/Microsoft/TypeScript/wiki/TypeScript-Design-Goals
⭐ Suggestion
A new flag to replace removed syntax during transpilation with blank space. Similarly to http://github.com/bloomberg/ts-blank-space and https://swc.rs/docs/references/wasm-typescript used in Node.js. This would remove the need of sourcemaps.
It can only be used in conjuction with --erasableSyntaxOnly
📃 Motivating Example
Example:
const foo: string = "Hello World";
becomes:
const foo = "Hello World";
💻 Use Cases
- What do you want to use this for?
Remove the need of sourcemaps after transpilation. - What shortcomings exist with current approaches?
None other than only a subset of syntax defined by an existing flag can be stripped. - What workarounds are you using in the meantime?
swc and tsblankspace
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
The issue names no repository files or tests. Start by tracing the existing --erasableSyntaxOnly option through the compiler and compare the requested blank-space output with the cited swc and ts-blank-space approaches. Done means a new compatible flag replaces removed syntax with spaces and is restricted to erasable syntax.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- compilers
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 28/100