TypeScript

165 engineers on Hacker News describe using TypeScript first-hand: 60 endorse it, 13 regret it, 12 are mixed.

77%trust
165first-hand users
139in production
endorse 60mixed 12regret 13uses, no opinion

“I use TypeScript extensively (in several projects) for defining schemas types.”

endorse · production · Benjamin_Dobell · 2026-10-08 · source ↗ · wrong label?

“I would never go back to writing standard TypeScript... as TypeScript is verbose, and effect adds its own verbosity.”

mixed · production · epolanski · 2026-05-30 · source ↗ · wrong label?

“It is still JavaScript even when it is called TypeScript.”

regret · production · _the_inflator · 2026-05-12 · source ↗ · wrong label?

“This was rewrite of Node.js/Typescript computation module... Zig/DebugSafe is approximately twice faster than TypeScript/Node.js 25”

regret · production · MrResearcher · 2026-03-12 · source ↗ · wrong label?

“Should put to tsgo which has dramatically lowered our type checking latency.”

endorse · production · brynary · 2025-12-29 · source ↗ · wrong label?

“We've also switched to the new native `tsgo` [0] for type checking, saving us another minute on CI/CD”

endorse · production · sondr3 · 2025-10-26 · source ↗ · wrong label?

“Something I experience virtually never in TypeScript, the other language I've also used for a decade”

endorse · production · 10 yr · jameslk · 2025-08-27 · source ↗ · wrong label?

“We used this approach to great effect when we migrated a huge legacy project from Javascript to Typescript.”

endorse · production · Etheryte · 2025-02-28 · source ↗ · wrong label?

“It helps me ship faster when I use the same stack everywhere. I even ported my background task library to TypeScript”

endorse · personal · welder · 2024-12-19 · source ↗ · wrong label?

“TypeScript has an amazingly powerful type system which let me build the ideal abstraction I wanted”

endorse · personal · mythz · 2024-12-06 · source ↗ · wrong label?

“All newer systems are based on typescript, which is great, but not dynamic unless you do code gen.”

mixed · production · anonzzzies · 2024-11-28 · source ↗ · wrong label?

“Angular has been even more stable since the switch to TS.”

endorse · production · devjab · 2024-10-26 · source ↗ · wrong label?

“We migrated to TypeScript a little while back and the practical effect has been much more and effective type checking”

endorse · production · dwb · 2024-07-25 · source ↗ · wrong label?

“TypeScript has probably crossed that threshold maybe in the last 12 months.”

endorse · production · erikpukinskis · 2023-11-11 · source ↗ · wrong label?

“the day we switched to using Typescript all these bugs we used to have just disappeared.”

endorse · production · brigadier132 · 2023-08-08 · source ↗ · wrong label?

“The gains of async, stricter typing and being able to share api schema types with frontend were totally worth it.”

endorse · production · nojvek · 2023-07-20 · source ↗ · wrong label?

“but stick to Python/typeScript when I want to be pragmatic.”

endorse · production · eddsh1994 · 2023-03-17 · source ↗ · wrong label?

“Then I tried out TypeScript and the speed and stability were breathtaking, and we never looked back.”

endorse · production · brundolf · 2023-03-16 · source ↗ · wrong label?

“We've migrated our code to TypeScript later and it was a bit smoother sailing”

endorse · production · spoiler · 2023-03-16 · source ↗ · wrong label?

“I realized it wasn't preventing any bugs that our integration tests wouldn't catch. It was just wasting my time with verbose types”

regret · production · hot_gril · 2023-02-27 · source ↗ · wrong label?

“I previously worked with TypeScript which felt like a major productivity boost”

endorse · production · dns_snek · 2022-12-31 · source ↗ · wrong label?

“Better following of type narrowing through branches and functions... there are still times when ts can't tell that that's the case.”

mixed · production · jsf01 · 2022-12-26 · source ↗ · wrong label?

“Vue3 also has FunctionalComponent now... props work beautifully with Typescript. In contrast, I'm finding integrating Typescript with the largely-JS React codebase I work with on the day job to be a bit nightmarish”

mixed · production · evnp · 2022-12-25 · source ↗ · wrong label?

“We use TypeScript and is great, and believe it or not that is becoming the rule, not the exception.”

endorse · production · liendolucas · 2022-12-18 · source ↗ · wrong label?

“Typescript already has a better type system than a lot of languages in common usage, but it's not good enough and we run into issues all the time because it's not powerful enough.”

mixed · production · ajkjk · 2022-12-14 · source ↗ · wrong label?

“I agree that Typescript improves with each release as I and the people I work closely with use it”

mixed · production · esperent · 2022-12-14 · source ↗ · wrong label?

“we use fullstack Typescript in our dev department.”

endorse · production · devjab · 2022-12-14 · source ↗ · wrong label?

“null-safety is my #1 motivator for using TypeScript over JavaScript. In the TypeScript codebases I've worked on, ... basically zero unhandled errors in production”

endorse · production · brundolf · 2022-12-08 · source ↗ · wrong label?

“In TypeScript, I don't have the same confidence. Did they wrote the correct validator?”

regret · personal · kajaktum · 2022-11-28 · source ↗ · wrong label?

“I used to work on a project with typescript only, and it was a huge pita... Never again typescript projects for me.”

regret · production · qxxx · 2022-10-02 · source ↗ · wrong label?

“And then Microsoft released TypeScript and now we have code safety and autocompletion on everything”

endorse · production · ggregoire · 2022-09-09 · source ↗ · wrong label?

“I've always used TS for the types and nothing more, and been happy with it.”

endorse · personal · activitypea · 2022-01-20 · source ↗ · wrong label?

“I've been using TypeScript for five years professionally now and cannot understate how much easier it has made large frontend projects”

endorse · production · 5 yr · disease · 2021-12-13 · source ↗ · wrong label?

“running tsc on a project I am working on now takes dozens of seconds to complete.”

regret · production · azangru · 2021-11-03 · source ↗ · wrong label?

“it is a tool I would never again turn away from”

endorse · production · nawgz · 2021-10-19 · source ↗ · wrong label?

“The FE stack at my current co. is React, MobX and TypeScript... Agreed. Same here. It's wonderful.”

endorse · production · drewpc · 2021-09-21 · source ↗ · wrong label?

“we've run into a number of issues with TS enums, the primary one being that TS enums compile to undefined vars”

regret · production · NoahTheDuke · 2021-09-13 · source ↗ · wrong label?

“we migrated our entire frontend codebase from Flow to TypeScript and we're happier for it.”

endorse · production · Raed667 · 2021-06-18 · source ↗ · wrong label?

“One thing we liked was better TypeScript support. We're big on types and proper support”

endorse · production · steve_adams_86 · 2021-06-15 · source ↗ · wrong label?

“And with the Angular CLI and TypeScript typings and using VSCode it's an absolute joy to build sites with.”

endorse · production · ourcat · 2021-01-22 · source ↗ · wrong label?

“being able to write Typescript instead feels like moving from assembly language to C”

endorse · production · arman_ashrafian · 2020-12-31 · source ↗ · wrong label?

“Been using TS + Svelte on a side project and it has been very nice.”

endorse · personal · mattgreenrocks · 2020-12-26 · source ↗ · wrong label?

“I've taken what I learned in clojure ... and use the same approach in TypeScript. And it's a breath of fresh air.”

endorse · personal · eyelidlessness · 2020-12-22 · source ↗ · wrong label?

“I've been using a lot of typescript lately. The ide support in vscode/tsserver is very complete, but it is NOT fast.”

mixed · production · adamkf · 2020-12-12 · source ↗ · wrong label?

“My experience across ruby, python, and js codebases is that Typescript for JS is leaps and bounds above anything in the other two languages”

endorse · production · cactus2093 · 2020-12-10 · source ↗ · wrong label?

“Having spent the last several years using TS on Node in production, and the last couple months working on a web project in React”

endorse · production · eyelidlessness · 2020-12-08 · source ↗ · wrong label?

“The only language I've had a similar experience from is Typescript.”

endorse · personal · aliceryhl · 2020-11-24 · source ↗ · wrong label?

“Being able to specify interfaces is absolutely nice, but overall I'm not convinced it's worth the trouble.”

mixed · production · 1 yr · mcv · 2020-08-05 · source ↗ · wrong label?

“just raw strictly typed queries. I think in the end its a better approach for our needs.”

endorse · production · seer · 2020-07-13 · source ↗ · wrong label?

“Overall I feel that React is the best tech for building frontends that we have so far, and TypeScript makes JS quite nice.”

endorse · production · 1.5 yr · lukevp · 2020-06-18 · source ↗ · wrong label?

“Typescript doesn't really add what it's supposed to add. It adds a lot of work, without providing the security we expect from it.”

regret · production · 1 yr · mcv · 2020-02-17 · source ↗ · wrong label?

“The bigger a project gets, the more unreadably TS snippets you run into. The cost/benefit ratio is awful”

regret · production · 734129837261 · 2019-12-23 · source ↗ · wrong label?

“I personally dislike Typescript as it is most often a hindrance for me... I think it offers some benefit and irritates me more than it benefits me”

mixed · production · 1 yr · bryanrasmussen · 2019-12-19 · source ↗ · wrong label?

“I'm doing a lot of TypeScript+WebGL work right now, and though TS is fairly nice”

endorse · personal · cylon13 · 2019-12-06 · source ↗ · wrong label?

“Between TypeScript, React, and styled components, I've come to find it extremely enjoyable to build interesting and complex things for the browser.”

endorse · personal · sickcodebruh · 2019-11-29 · source ↗ · wrong label?

“You won't regret it ! It helps me every day. Just be sure to not be too strict in your tsconfig.json in the beginning.”

endorse · personal · simlevesque · 2019-11-05 · source ↗ · wrong label?

“over the last two years when we switched to use Typescript, it has gotten significantly more valuable”

endorse · production · 2 yr · sethc2 · 2019-07-02 · source ↗ · wrong label?

“We switched over all the code to TypeScript in one go, and we are gradually fixing the type errors over time.”

endorse · production · steadicat · 2019-01-25 · source ↗ · wrong label?

“I vastly prefer TypeScript to JavaScript because JS has a lot of foot-guns. ... adopting it little by little sorta gets me that balance I want.”

endorse · production · vga805 · 2019-01-15 · source ↗ · wrong label?

“We switched to Typescript mid-project and never looked back.”

endorse · production · gregopet · 2019-01-06 · source ↗ · wrong label?

“TSX is just much more intuitive to me.”

endorse · production · lowkeyokay · 2018-12-24 · source ↗ · wrong label?

“I've been using TypeScript as my main language for the last couple of years since leaving Microsoft. However, I often find myself really missing how well organized C# was.”

mixed · production · 2 yr · seanmcdirmid · 2018-12-13 · source ↗ · wrong label?

“The more recent parts of our app is written in TypeScript, and we are in the process of migrating the rest to TypeScript as well.”

endorse · production · keremkazan · 2018-12-05 · source ↗ · wrong label?

“The sheer number of bugs we have since been able to prevent by the (ever improving) strictness checks of Typescript is staggering.”

endorse · production · 2 yr · alceta · 2018-11-30 · source ↗ · wrong label?

“I would just want to use the robustness and correctness that I'm able to ensure with Haskell, compare to TypeScript”

regret · production · Tehnix · 2018-11-29 · source ↗ · wrong label?

“we migrated one of our Java backends to TypeScript/Node, and made the code 40% lighter, better typed, and much simpler”

endorse · production · jeremychone · 2018-10-02 · source ↗ · wrong label?

“we found it to be much less productive than JS exactly because stuff like prototypes becomes more complex and typesafety kind of gets in the way”

regret · production · eksemplar · 2018-10-01 · source ↗ · wrong label?

“We switched to Typescript a few years back because of the same issue and I'll never look back.”

endorse · production · thermodynthrway · 2018-07-13 · source ↗ · wrong label?

“we migrated the codebase to TypeScript, and it was a fair amount of work to migrate the existing code”

endorse · production · dgreensp · 2018-05-18 · source ↗ · wrong label?

“The concept of TypeScript code generation is very valid, saves a lot of time during rapid prototyping”

endorse · personal · buybackoff · 2017-12-12 · source ↗ · wrong label?

“I've found using TypeScript one of the better experiences I've had in the Angular ecosystem.”

endorse · personal · shusson · 2017-12-07 · source ↗ · wrong label?

“as someone using Angular in production I'd urge you to stay far away from Angular and TypeScript.”

regret · production · ChristianBundy · 2017-12-07 · source ↗ · wrong label?

“In my own experience, TypeScript is a huge advance over JavaScript without types, in both productivity... and reliability (how many bugs ever make it all the way to a customer).”

endorse · production · veidr · 2017-12-07 · source ↗ · wrong label?

“We migrated to Typescript. Error messages are more understandable... There are many gripes we've had with typescript too”

mixed · production · chmln · 2017-11-09 · source ↗ · wrong label?

“We've switched to Typescript for our React projects because we've found it's the sweet spot between developer perks”

endorse · production · dfcowell · 2017-08-09 · source ↗ · wrong label?

“I've been using Typescript for over a year, and the amount of improvement in that relatively short time span has been incredible.”

endorse · personal · 1 yr · ken47 · 2016-12-08 · source ↗ · wrong label?

“TypeScript makes you wonder how you survived with ES5”

endorse · personal · michaelbull · 2016-11-30 · source ↗ · wrong label?

“In the end we chose React due to the wonderful combination between it and TypeScript.”

endorse · production · teniutza · 2016-10-21 · source ↗ · wrong label?

“We switched to TypeScript, we cleaned up our code organization.”

endorse · production · mattetti · 2016-05-03 · source ↗ · wrong label?

“static typing for the rest of the code via TypeScript”

endorse · production · buu700 · 2016-01-23 · source ↗ · wrong label?

“So, I can't call it an unmitigated success, some of what the codebase needed was just some general structure”

mixed · production · Eridrus · 2015-07-20 · source ↗ · wrong label?

“we have a Typescript (<3) analytics payload that has to deal with lots of weird JS execution environments”

endorse · production · Eridrus · 2015-05-22 · source ↗ · wrong label?

“That's part of why we moved to TypeScript, and I'd argue that it vastly improved the quality of our codebase.”

endorse · production · tschneidereit · 2015-02-14 · source ↗ · wrong label?

“We migrated most of the ES6 codebase to Typescript, and it feels great.”

endorse · production · mushishi · 2015-01-16 · source ↗ · wrong label?

“I had been attempting to use Typescript, but after giving it a shot, ScalaJS clearly beat it in every regard”

regret · personal · benjaminjackman · 2014-11-20 · source ↗ · wrong label?

“built with Vite/TypeScript/Tailwind”

neutral · personal · vunderba · 2026-10-26 · source ↗ · wrong label?

“Stackwise we selected Three.js, typescript and bun and pushed models to test everything for webgpu, webgl and mobile simulations”

neutral · personal · Livia_Zaharia · 2026-10-05 · source ↗ · wrong label?

“Most projects my fleet works on are in other languages (TS, Go, Elixir)”

neutral · personal · s08148692 · 2026-10-01 · source ↗ · wrong label?

“It's 3x slower than TypeScript v6 compiler, but we hope to get to rough performance parity in a week or so.”

neutral · production · jeswin · 2026-08-18 · source ↗ · wrong label?

“we switched from CMake to a handrolled typescript build system and it made our builds faster and simpler.”

neutral · production · Jarred · 2026-07-27 · source ↗ · wrong label?

“the team started off composed by a bunch of TypeScript/React/Node developers”

neutral · production · dminik · 2026-07-16 · source ↗ · wrong label?

“I transpile for prod, but use --strip-types when running in dev, and all I had to do was to make a 10-line ESM register hook”

neutral · production · moogly · 2026-07-02 · source ↗ · wrong label?

“I work regularly with Go, React, TypeScript, and I don't miss VSCode.”

neutral · production · srfrog · 2025-12-16 · source ↗ · wrong label?

“Lately I've moved away from it though. Mostly to typescript, a little rust, and Gleam”

neutral · personal · dkersten · 2025-12-11 · source ↗ · wrong label?

“a somewhat smaller TypeScript codebase (~200K LOC)”

neutral · production · smithkl42 · 2025-09-17 · source ↗ · wrong label?

“recently a good amount of server-side typescript”

neutral · production · gen220 · 2025-09-02 · source ↗ · wrong label?

“We migrated Calm's large Rush.js monorepo away from tsc emit and onto Node's new type stripping feature.”

neutral · production · sdotson · 2025-08-21 · source ↗ · wrong label?

“running a server on the Rust side and calling it from a TypeScript frontend is a good approach.”

neutral · production · yujonglee · 2025-07-29 · source ↗ · wrong label?

“I spent 2 hours trying to get z3 to work with f# for an old advent of code problem before just writing it in typescript.”

neutral · personal · banashark · 2024-12-15 · source ↗ · wrong label?

“I've been using Preact on an entirely client-side SPA with a simple RPC-like backend all in typescript for 5 years or so.”

neutral · production · 5 yr · christophilus · 2024-12-03 · source ↗ · wrong label?

“every language I ever shipped software with, from ASP, PHP, and C# to Swift, TypeScript and Rust”

neutral · production · blixt · 2024-11-26 · source ↗ · wrong label?

“we completely rewrote the application in Typescript and Rust.”

neutral · production · obeavs · 2024-11-10 · source ↗ · wrong label?

“I worked with a group that basically elixir-fide typescript for the frontend and ruby for the backend.”

neutral · production · fellowniusmonk · 2024-11-08 · source ↗ · wrong label?

“had prior exp in php, python, java, Go, and Typescript, and enjoyed most of them”

neutral · production · cloverich · 2024-11-02 · source ↗ · wrong label?

“We use typescript.”

neutral · production · 015a · 2024-05-09 · source ↗ · wrong label?

“a Rails expert with Typescript experience”

neutral · production · berkes · 2024-02-20 · source ↗ · wrong label?

“Using TypeScript + Node + esbuild + my own build system”

neutral · production · DecoPerson · 2023-12-13 · source ↗ · wrong label?

“I tried it for a couple months (Typescript) in production.”

neutral · production · solardev · 2023-12-13 · source ↗ · wrong label?

“I'm a big ts and nodejs user”

neutral · production · twosdai · 2023-10-14 · source ↗ · wrong label?

“typescript is still added to the projects but only for type checking with "allowJs" and "checkJs" configured to true”

neutral · production · Zekio · 2023-09-08 · source ↗ · wrong label?

“Only in legacy code we haven’t replaced yet as we switched to TypeScript a few years ago.”

neutral · production · ickelbawd · 2023-07-18 · source ↗ · wrong label?

“We switched to c# and python and js/ts for new dev at some point”

neutral · production · monkeycantype · 2023-04-25 · source ↗ · wrong label?

“for a cross-platform typescript project”

neutral · production · matesz · 2023-02-22 · source ↗ · wrong label?

“at my previous job it was a mix of PHP / JS (Dojo), Go, Typescript”

neutral · production · Cthulhu_ · 2022-12-21 · source ↗ · wrong label?

“granted I am quite new to backend typescript.”

neutral · personal · sergiotapia · 2022-12-20 · source ↗ · wrong label?

“the irony that i work in JS/TS is not lost on me”

neutral · production · leeoniya · 2022-12-17 · source ↗ · wrong label?

“We use SPAs and a pretty strict typescript/react stack.”

neutral · production · _gabe_ · 2022-12-10 · source ↗ · wrong label?

“we use lenses in react/typescript together with jotai atoms to express data paths in complex structures.”

neutral · production · valyagolev · 2022-12-06 · source ↗ · wrong label?

“attempting to reimplement in typescript to address some of our pain was not fun”

neutral · production · for1nner · 2022-12-04 · source ↗ · wrong label?

“I’ve worked at several typescript shops and I have certainly never seen “absolutely zero runtime errors in production.””

neutral · production · mplanchard · 2022-11-28 · source ↗ · wrong label?

“after doing a lot of work in Typescript, that class Optional is a big mistake”

neutral · production · hn_throwaway_99 · 2022-11-22 · source ↗ · wrong label?

“we didn't have a fascist linter for C# the way we do with Typescript”

neutral · production · EnKopVand · 2022-07-28 · source ↗ · wrong label?

“TypeScript - for our front-end JS. This is a recent addition.”

neutral · production · haacked · 2022-07-25 · source ↗ · wrong label?

“This is the reason I don't use the typescript compiler and instead use babel to strip the types out completely”

neutral · production · bavell · 2022-06-08 · source ↗ · wrong label?

“we produce TypeScript contracts and signatures out of C# contracts and API endpoints.”

neutral · production · victorNicollet · 2022-03-15 · source ↗ · wrong label?

“At work most of the JS/TS code is namespaces and plain functions, with the occasional object when that makes sense.”

neutral · production · Zababa · 2021-12-30 · source ↗ · wrong label?

“our stack is 90% python, with TS for frontend.”

neutral · production · kortex · 2021-12-21 · source ↗ · wrong label?

“compared to any other language I've used in prod (C#, Typescript, Javascript, and PHP)”

neutral · production · aaronmu · 2021-12-20 · source ↗ · wrong label?

“it's been a nightmare dealing with package upgrades, ESM vs CJS, running tests, adding Typescript”

neutral · production · scottc · 2021-12-16 · source ↗ · wrong label?

“the largest project I'm working on is mostly in TS now”

neutral · production · forty · 2021-12-13 · source ↗ · wrong label?

“We use TypeScript not Scala”

neutral · production · derN3rd · 2021-12-10 · source ↗ · wrong label?

“For our quite big JS codebase on React + typescript, we switched from Webpack to esbuild earlier this year.”

neutral · production · Zarkaos · 2021-10-14 · source ↗ · wrong label?

“we switched from JS to TS everywhere a few years ago”

neutral · production · 015a · 2021-09-26 · source ↗ · wrong label?

“I've used all of these languages”

neutral · personal · armchairhacker · 2021-07-23 · source ↗ · wrong label?

“I prefer to NOT use If statements in typescript if it can be done in Cloudformation with conditions”

neutral · production · fimbulvetr · 2021-06-10 · source ↗ · wrong label?

“write the logic in ”something other than groovy” - typescript in our case”

neutral · production · jordanbeiber · 2021-06-03 · source ↗ · wrong label?

“Backend Node with shift to TypeScript near the end”

neutral · production · bradlys · 2021-02-13 · source ↗ · wrong label?

“We've been working with clojure/java/react/typescript.”

neutral · production · throw20210211 · 2021-02-11 · source ↗ · wrong label?

“CDK is amazing, we use it in typescript and it's just great”

neutral · production · mxz3000 · 2020-12-31 · source ↗ · wrong label?

“We use Typescript for web frontend.”

neutral · production · tinco · 2020-12-29 · source ↗ · wrong label?

“Because of that we moved to Typescript.”

neutral · personal · sudosysgen · 2020-12-13 · source ↗ · wrong label?

“I worked on one huge typescript project years ago at MSFT with slow compile speeds, and was always too scared to try my hand at fixing that”

neutral · production · breck · 2020-11-25 · source ↗ · wrong label?

“That experience is similar to typescript "it's just JS"”

neutral · personal · yomly · 2020-08-11 · source ↗ · wrong label?

“We moved to Typescript two years ago, and now that I'm comfortable with that, and compiling to JS”

neutral · production · 2 yr · pedalpete · 2020-05-20 · source ↗ · wrong label?

“Combined with io-ts, it also support almost 100% TypeScript type checks both on compile-time and run-time.”

neutral · production · valand · 2020-01-01 · source ↗ · wrong label?

“after maintaining a fork for a few months we switched to TypeScript.”

neutral · production · kccqzy · 2019-12-12 · source ↗ · wrong label?

“I use "generics" in TypeScript but it's always a very small number of types: usually two, maybe up to 10...”

neutral · production · erikpukinskis · 2019-11-16 · source ↗ · wrong label?

“We use TSC for typechecking and our own typescript compiler for compiling down to ARM assembly.”

neutral · production · darzu · 2019-05-23 · source ↗ · wrong label?

“Also... there are some groups that use Javascript for this kind of work (We use Typescript for our projects)”

neutral · production · bluejay2387 · 2018-12-28 · source ↗ · wrong label?

“We use graphql-code-generator to make Typescript.”

neutral · production · ndonnellan · 2018-12-26 · source ↗ · wrong label?

“Also we use Flow / Typescript.”

neutral · production · crubier · 2018-12-26 · source ↗ · wrong label?

“you can use all of the normal tools of TypeScript for composing queries (mainly imports and template literals)”

neutral · production · mwilliamson · 2018-12-26 · source ↗ · wrong label?

“I myself and our team have clear established patterns that we use.”

neutral · production · tekkk · 2018-12-22 · source ↗ · wrong label?

“Yeah, we use tsc for node.”

neutral · production · dvlsg · 2018-12-02 · source ↗ · wrong label?

“for deployment (in our ci/cd) we run tsc to compile the typescript down to javascript”

neutral · production · itslennysfault · 2018-12-02 · source ↗ · wrong label?

“by now we've replaced Babel entirely with Typescript”

neutral · production · __s · 2018-08-27 · source ↗ · wrong label?

“A few others to typescript and we even made a few pocs with Xamarin and Wasm.”

neutral · production · eksemplar · 2018-08-21 · source ↗ · wrong label?

“K8s, Bazel, Go, Java (Android), Swift (iOS), Typescript.”

neutral · production · codesuki · 2018-05-29 · source ↗ · wrong label?

“We enforce types for communication with node, so at least you know the structure of all the json going through the network.”

neutral · production · ix-hispana · 2017-11-29 · source ↗ · wrong label?

“I've been using React with MobX and Typescript for the past year in production”

neutral · production · 1 yr · buttminer · 2017-11-16 · source ↗ · wrong label?

“I've been using preact with tsx and inline styles.”

neutral · personal · nojvek · 2016-12-20 · source ↗ · wrong label?

“I've been using VSCode for TS (nothing else though).”

neutral · personal · JohnDotAwesome · 2016-12-15 · source ↗ · wrong label?

“in the TypeScript compiler, we use very few classes at all - it's mostly written in a function-oriented style.”

neutral · production · DanRosenwasser · 2016-12-09 · source ↗ · wrong label?

“We run a good-sized app API using Typescript with Node.js.”

neutral · production · mAritz · 2015-12-16 · source ↗ · wrong label?

“I'm running through two source map steps: TypeScript to JavaScript and JavaScript to minified JavaScript.”

neutral · production · nawitus · 2014-10-03 · source ↗ · wrong label?