Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/cspotcode/typescript-transpile-only
`tsc` CLI that skips typechecking.
https://github.com/cspotcode/typescript-transpile-only
compiler transpiler typescript
Last synced: 2 months ago
JSON representation
`tsc` CLI that skips typechecking.
- Host: GitHub
- URL: https://github.com/cspotcode/typescript-transpile-only
- Owner: cspotcode
- Created: 2018-09-11T16:14:15.000Z (over 6 years ago)
- Default Branch: master
- Last Pushed: 2018-09-11T16:49:47.000Z (over 6 years ago)
- Last Synced: 2024-10-23T18:40:17.405Z (3 months ago)
- Topics: compiler, transpiler, typescript
- Language: JavaScript
- Size: 7.81 KB
- Stars: 19
- Watchers: 2
- Forks: 1
- Open Issues: 2
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
`tsc` that skips typechecking but still fails on syntax errors.
Sometimes you want to use TypeScript, but you're migrating a legacy project. So you have type errors. Maybe not everyone on your team
is an expert at type annotations yet. Or maybe you renamed some old `.js` files to `.ts` so you can add annotations slowly over time, and you don't want to spam `any` all over the place.You want to `tsc` your code, and you want it to fail on syntax errors. (`const foo = = this is wrong;`)
But you *don't* want it to fail on semantic errors.This is a quick, 1 hour hack to write a `tsc` alternative that compiles your code just like `tsc` but skips typechecking.
# Usage
Install this module alongside the version of "typescript" you want to use.
```
npm install typescript-transpile-only
npm install typescript
```Run `tsc-transpile-only` instead of `tsc`. For example:
```shell
tsc-transpile-only --project .
```# Caveats
No tests; use it at your own risk. Or look at the code; it's tiny.
Does not support `--build`, `--help`, `--version`, or `--all` flags.
The only one that makes sense in this context is `--build`, but you can easily workaround this by invoking `tsc-transpile-only` multiple times.Exit codes are valid but don't exactly match `tsc`'s behavior. `tsc` uses different non-zero error codes depending on the reason for failure. We use exit code 1 for all failures; 0 for success. (no syntax errors)
# Bugs / Questions / Suggestions
Please [open an issue](https://github.com/cspotcode/typescript-transpile-only/issues) on Github.