All Articles

What is JSX.IntrinsicElements?

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

JSX.IntrinsicElements is a type in TypeScript's global scope that defines which native JSX elements are in scope, and what props they require.

Usage

tsx
declare global {
namespace JSX {
interface IntrinsicElements {
"my-custom-element": {
id: string;
};
}
}
}
 
<my-custom-element />;
Property 'id' is missing in type '{}' but required in type '{ id: string; }'.2741Property 'id' is missing in type '{}' but required in type '{ id: string; }'.

In the example above, we:

  1. Declare a global type using declare global.
  2. Use the JSX namespace.
  3. Create an IntrinsicElements interface.
  4. Define a property on the interface with the name of the element we want to define.

The property that we define on the IntrinsicElements interface is the name of the element we want to define. The value of the property is the props that the element accepts.

This works because interfaces in the same scope merge their declarations. This means that the IntrinsicElements interface we define will merge with the one that TypeScript already knows about.

If you try to use an element that isn't defined on JSX.IntrinsicElements, you'll get an error:

Property 'X' does not exist on type 'JSX.IntrinsicElements'.

tsx
const Component = () => {
return <i-am-not-defined />;
Property 'i-am-not-defined' does not exist on type 'JSX.IntrinsicElements'.2339Property 'i-am-not-defined' does not exist on type 'JSX.IntrinsicElements'.
};

When will I use this?

Mostly, you won't modify JSX.InstrinsicElements yourself. Instead, the framework you're using will define the elements for you.

For instance, React uses JSX.IntrinsicElements to define the props for native HTML elements.

Pressing cmd-click on a JSX element in VSCode will take you to the definition of the element - and the definition is pretty enormous:

declare global {
  namespace JSX {
    interface IntrinsicElements {
      a: React.DetailedHTMLProps<
        React.AnchorHTMLAttributes<HTMLAnchorElement>,
        HTMLAnchorElement
      >;
      abbr: React.DetailedHTMLProps<
        React.HTMLAttributes<HTMLElement>,
        HTMLElement
      >;
      address: React.DetailedHTMLProps<
        React.HTMLAttributes<HTMLElement>,
        HTMLElement
      >;
      // ... hundreds more
    }
  }
}

Fundamentally, this is doing exactly the same thing as our code above. The name of the property is the name of the element, and the value is the props that the element accepts.

React.DetailedHTMLProps is just a utility type that creates the types that a, abbr, and address accept.

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