-
Notifications
You must be signed in to change notification settings - Fork 5.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature request: deno tsc #3281
Comments
How would this be effectively different from |
Really just being able to compile browser code without necessitating two TypeScript compilers and npm. It's more of a "why not" to me I guess... this kind of thing would help justify the executable size on the surface. |
#2927 Would seem more useful and less redundant in my opinion. Trying to replicate |
This isn't supposed to replace #2927 to be clear, but I get what you're saying. This would be redundant alongside good programmatic access. I guess all I want is some way on the CLI of using deno's compiler on browser code. If #2927 was used to implement a stripped down |
That doesn't make sense, because generally the Deno compiler doesn't produce code that is usable in the browser, it doesn't do any real magic, it is the stuff it doesn't do that is really different from |
Okay, I think I'd overestimated the amount of |
Expose the TypeScript compiler for CLI usage as a subcommand:
deno tsc
. I think this has a clearer story than the runtime APIs which have been suggested before.@kitsonk I've assumed this is easier than #2927. Or is it dependent on the same issues?
The text was updated successfully, but these errors were encountered: