StackShareStackShare
Follow on
StackShare

Discover and share technology stacks from companies around the world.

Product

  • Stacks
  • Tools
  • Companies
  • Feed

Company

  • About
  • Blog
  • Contact

Legal

  • Privacy Policy
  • Terms of Service

© 2025 StackShare. All rights reserved.

API StatusChangelog
TypeScript
ByTypeScriptTypeScript

TypeScript

#6in Languages
Discussions218
Followers74.1k
OverviewDiscussions218

What is TypeScript?

TypeScript is a language for application-scale JavaScript development. It's a typed superset of JavaScript that compiles to plain JavaScript.

TypeScript is a tool in the Languages category of a tech stack.

TypeScript Pros & Cons

Pros of TypeScript

  • ✓More intuitive and type safe javascript
  • ✓Type safe
  • ✓JavaScript superset
  • ✓The best AltJS ever
  • ✓Best AltJS for BackEnd
  • ✓Powerful type system, including generics & JS features
  • ✓Compile time errors
  • ✓Nice and seamless hybrid of static and dynamic typing
  • ✓Aligned with ES development for compatibility
  • ✓Angular

Cons of TypeScript

  • ✗Code may look heavy and confusing
  • ✗Hype

TypeScript Alternatives & Comparisons

What are some alternatives to TypeScript?

JavaScript

JavaScript

JavaScript is most known as the scripting language for Web pages, but used in many non-browser environments as well such as node.js or Apache CouchDB. It is a prototype-based, multi-paradigm scripting language that is dynamic,and supports object-oriented, imperative, and functional programming styles.

Python

Python

Python is a general purpose programming language created by Guido Van Rossum. Python is most praised for its elegant syntax and readable code, if you are just beginning your programming career python suits you best.

HTML5

HTML5

HTML5 is a core technology markup language of the Internet used for structuring and presenting content for the World Wide Web. As of October 2014 this is the final and complete fifth revision of the HTML standard of the World Wide Web Consortium (W3C). The previous version, HTML 4, was standardised in 1997.

PHP

PHP

Fast, flexible and pragmatic, PHP powers everything from your blog to the most popular websites in the world.

Java

Java

Java is a programming language and computing platform first released by Sun Microsystems in 1995. There are lots of applications and websites that will not work unless you have Java installed, and more are created every day. Java is fast, secure, and reliable. From laptops to datacenters, game consoles to scientific supercomputers, cell phones to the Internet, Java is everywhere!

CSS 3

CSS 3

CSS3 is the latest evolution of the Cascading Style Sheets language and aims at extending CSS2.1. It brings a lot of long-awaited novelties, like rounded corners, shadows, gradients, transitions or animations, as well as new layouts like multi-columns, flexible box or grid layouts. Experimental parts are vendor-prefixed and should either be avoided in production environments, or used with extreme caution as both their syntax and semantics can change in the future.

TypeScript Integrations

TaskBotJS, Saleor, Majestic GUI, Pyright, TSLint and 7 more are some of the popular tools that integrate with TypeScript. Here's a list of all 12 tools that integrate with TypeScript.

TaskBotJS
TaskBotJS
Saleor
Saleor
Majestic GUI
Majestic GUI
Pyright
Pyright
TSLint
TSLint
SinonJS
SinonJS
FullStack Boilerplate
FullStack Boilerplate
Lightweight Charts
Lightweight Charts
Just
Just
Mithril
Mithril
nodemon
nodemon
GraphQL Zeus
GraphQL Zeus

TypeScript Discussions

Discover why developers choose TypeScript. Read real-world technical decisions and stack choices from the StackShare community.

Lee Benson
Lee Benson

Nov 30, 2018

Needs adviceonReactReactGraphQLGraphQLApolloApollo

ReactQL is a React + GraphQL front-end starter kit. #JSX is a natural way to think about building UI, and it renders to pure #HTML in the browser and on the server, making it trivial to build server-rendered Single Page Apps. GraphQL via Apollo was chosen for the data layer; #GraphQL makes it simple to request just the data your app needs, and #Apollo takes care of communicating with your API (written in any language; doesn't have to be JavaScript!), caching, and rendering to #React.

ReactQL is written in TypeScript to provide full types/Intellisense, and pick up hard-to-diagnose goofs that might later show up at runtime. React makes heavy use of Webpack 4 to handle transforming your code to an optimised client-side bundle, and in throws back just enough code needed for the initial render, while seamlessly handling import statements asynchronously as needed, making the payload your user downloads ultimately much smaller than trying to do it by hand.

React Helmet was chosen to handle <head> content, because it works universally, making it easy to throw back the correct <title> and other tags on the initial render, as well as inject new tags for subsequent client-side views.

styled-components, Sass, Less and PostCSS were added to give developers a choice of whether to build styles purely in React / JavaScript, or whether to defer to a #@{css}|topic:477| #preprocessor. This is especially useful for interop with UI frameworks like Bootstrap, Semantic UI, Foundation, etc - ReactQL lets you mix and match #css and renders to both a static .css file during bundling as well as generates per-page <style> tags when using #StyledComponents.

React Router handles routing, because it works both on the server and in the client. ReactQL customises it further by capturing non-200 responses on the server, redirecting or throwing back custom 404 pages as needed.

Koa is the web server that handles all incoming HTTP requests, because it's fast (TTFB < 5ms, even after fully rendering React), and its natively #async, making it easy to async/await inside routes and middleware.

0 views0
Comments
Eli Hooten
Eli Hooten

CTO at Codecov

Nov 30, 2018

Needs adviceonTypeScriptTypeScriptJavaScriptJavaScriptCoffeeScriptCoffeeScript

We chose TypeScript at Codecov when undergoing a recent rewrite of a legacy front end. Our previous front end was a mishmash of vanilla JavaScript and CoffeeScript , and was expanded upon haphazardly as the need arose. Without a unifying set of paradigms and patterns, the CoffeeScript and JavaScript setup was proving hard to maintain and expand upon by an engineering team. During a move to Vue.js , we decided to also make the move to TypeScript. Integrating TypeScript and Vue.js is fairly well understood at this point, so the setup wasn't all that difficult, and we felt that the benefits of incorporating TypeScript would outweigh the required time to set it up and get our engineering team up to speed.

Choosing to add TypeScript has given us one more layer to rely on to help enforce code quality, good standards, and best practices within our engineering organization. One of the biggest benefits for us as an engineering team has been how well our IDEs and editors (e.g., Visual Studio Code ) integrate with and understand TypeScript . This allows developers to catch many more errors at development time instead of relying on run time. The end result is safer (from a type perspective) code and a more efficient coding experience that helps to catch and remove errors with less developer effort.

0 views0
Comments
Cameron Sadler
Cameron Sadler

CEO at NewCraft

Sep 25, 2018

Needs adviceonTypeScriptTypeScript

TypeScript has been a win because, in general, it makes codebase maintenance less brittle. It's significantly easier to refactor in TS than JS, which encourages incremental improvements, file re-organizing, etc. Our developers are happier with the overall development experience.

The downside is that TS sometimes exacerbates problems caused by Node's fragmented ecosystem. Sometimes @types/ don't work, other times types are outdated. This can lead to problems with newly-installed libraries.

If your project is big enough, I'd say TS is nearly always worth it, but it can make selecting libraries annoying.

#typescript #NewCraft

0 views0
Comments
Dan Robinson
Dan Robinson

Sep 13, 2018

Needs adviceonjQueryjQueryBackbone.jsBackbone.jsMarionetteMarionette

The front end for Heap begun to grow unwieldy. The original jQuery pieces became difficult to maintain and scale, and a decision was made to introduce Backbone.js, Marionette, and TypeScript. Ultimately this ended up being a “detour” in the search for a scalable and maintainable front-end solution. The system did allow for developers to reuse components efficiently, but adding features was a difficult process, and it eventually became a bottleneck in advancing the product.

Today, the Heap product consists primarily of a customer-facing dashboard powered by React, MobX, and TypeScript on the front end. We wrote our migration to React and MobX in detail last year here.

#JavascriptUiLibraries #Libraries #JavascriptMvcFrameworks #TemplatingLanguagesExtensions

0 views0
Comments
Kir Shatrov
Kir Shatrov

Engineering Lead at Shopify

Sep 13, 2018

Needs adviceonjQueryjQueryJavaScriptJavaScriptReactReact

The client-side stack of Shopify Admin has been a long journey. It started with HTML templates, jQuery and Prototype. We moved to Batman.js, our in-house Single-Page-Application framework (SPA), in 2013. Then, we re-evaluated our approach and moved back to statically rendered HTML and vanilla JavaScript. As the front-end ecosystem matured, we felt that it was time to rethink our approach again. Last year, we started working on moving Shopify Admin to React and TypeScript.

Many things have changed since the days of jQuery and Batman. JavaScript execution is much faster. We can easily render our apps on the server to do less work on the client, and the resources and tooling for developers are substantially better with React than we ever had with Batman.

#FrameworksFullStack #Languages

0 views0
Comments

Try It

Visit Website

Adoption

On StackShare

Companies
6.13k
ACFFHI+6119
Developers
80.9k
YGMMBS+80876