All Articles

"Sorry, I Need A TypeScript Playground In Order To Help"

Matt Pocock
Matt PocockMatt is a well-regarded TypeScript expert known for his ability to demystify complex TypeScript concepts.

You have likely been sent this article because you asked someone a TypeScript question without providing a TypeScript playground.

Here's how to fix it.

  1. Go to the TypeScript Playground.

  2. Write your code in the editor. You can use libraries from npm (by simply importing them) if needed.

  3. If your code doesn't fit in the editor, make your example simpler and smaller. The less code you ask someone to read, the more likely they are to help you.

  4. Make sure you comment your code to show what you expect to happen.

// `a` should be inferred as a string, but it's a number...
const a = 1;
  1. Consider using @ts-expect-error to show where errors are expected in your code.

  2. Make sure your code has NO errors except for the ones you expect to be there.

  3. Save the playground. This will provide you with a URL that you can share with others.

  4. If you asked the question on a platform that doesn't support sharing links (like YouTube comments), head to my Discord Channel to ask it.

Why Not A Screenshot?

If you provided a screenshot to illustrate your problem, you might be over-estimating the skill of the developers you're asking for help.

Most developers can't just look at a screenshot and know exactly what the error is. They need to play with code in order to understand what it does. For this, you need an IDE.

This is why the TypeScript playground is so useful - it provides shareable playgrounds that help facilitate collaboration.

Why Not CodeSandbox/StackBlitz?

There are several tools out there that help provide a multi-file IDE with support for actually running code.

These are great for sharing code, but they're not great for asking questions.

I've had many situations where people ask me a question using a StackBlitz/CodeSandbox link, and I have to spend 10 minutes trying to figure out what the problem is, or even in which file it originates from.

So, I've learned to dread these links.

The TypeScript playground is a much better tool for asking questions, because it provides a single file with a single entry point.

Matt's signature

Share this article with your friends

`any` Considered Harmful, Except For These Cases

Discover when it's appropriate to use TypeScript's any type despite its risks. Learn about legitimate cases where any is necessary.

Matt Pocock
Matt Pocock

No, TypeScript Types Don't Exist At Runtime

Learn why TypeScript's types don't exist at runtime. Discover how TypeScript compiles down to JavaScript and how it differs from other strongly-typed languages.

Matt Pocock
Matt Pocock

Deriving vs Decoupling: When NOT To Be A TypeScript Wizard

In this book teaser, we discuss deriving vs decoupling your types: when building relationships between your types or segregating them makes sense.

Matt Pocock
Matt Pocock

NoInfer: TypeScript 5.4's New Utility Type

Learn how TypeScript's new utility type, NoInfer, can improve inference behavior by controlling where types are inferred in generic functions.

Matt Pocock
Matt Pocock