{"componentChunkName":"component---src-templates-docs-js","path":"/docs/introducing-jsx.html","result":{"data":{"markdownRemark":{"html":"

Consider this variable declaration:

\n
const element = <h1>Hello, world!</h1>;
\n

This funny tag syntax is neither a string nor HTML.

\n

It is called JSX, and it is a syntax extension to JavaScript. We recommend using it with React to describe what the UI should look like. JSX may remind you of a template language, but it comes with the full power of JavaScript.

\n

JSX produces React “elements”. We will explore rendering them to the DOM in the next section. Below, you can find the basics of JSX necessary to get you started.

\n

Why JSX?

\n

React embraces the fact that rendering logic is inherently coupled with other UI logic: how events are handled, how the state changes over time, and how the data is prepared for display.

\n

Instead of artificially separating technologies by putting markup and logic in separate files, React separates concerns with loosely coupled units called “components” that contain both. We will come back to components in a further section, but if you’re not yet comfortable putting markup in JS, this talk might convince you otherwise.

\n

React doesn’t require using JSX, but most people find it helpful as a visual aid when working with UI inside the JavaScript code. It also allows React to show more useful error and warning messages.

\n

With that out of the way, let’s get started!

\n

Embedding Expressions in JSX

\n

In the example below, we declare a variable called name and then use it inside JSX by wrapping it in curly braces:

\n
const name = 'Josh Perez';const element = <h1>Hello, {name}</h1>;\nReactDOM.render(\n  element,\n  document.getElementById('root')\n);
\n

You can put any valid JavaScript expression inside the curly braces in JSX. For example, 2 + 2, user.firstName, or formatName(user) are all valid JavaScript expressions.

\n

In the example below, we embed the result of calling a JavaScript function, formatName(user), into an <h1> element.

\n
function formatName(user) {\n  return user.firstName + ' ' + user.lastName;\n}\n\nconst user = {\n  firstName: 'Harper',\n  lastName: 'Perez'\n};\n\nconst element = (\n  <h1>\n    Hello, {formatName(user)}!  </h1>\n);\n\nReactDOM.render(\n  element,\n  document.getElementById('root')\n);
\n

Try it on CodePen

\n

We split JSX over multiple lines for readability. While it isn’t required, when doing this, we also recommend wrapping it in parentheses to avoid the pitfalls of automatic semicolon insertion.

\n

JSX is an Expression Too

\n

After compilation, JSX expressions become regular JavaScript function calls and evaluate to JavaScript objects.

\n

This means that you can use JSX inside of if statements and for loops, assign it to variables, accept it as arguments, and return it from functions:

\n
function getGreeting(user) {\n  if (user) {\n    return <h1>Hello, {formatName(user)}!</h1>;  }\n  return <h1>Hello, Stranger.</h1>;}
\n

Specifying Attributes with JSX

\n

You may use quotes to specify string literals as attributes:

\n
const element = <div tabIndex=\"0\"></div>;
\n

You may also use curly braces to embed a JavaScript expression in an attribute:

\n
const element = <img src={user.avatarUrl}></img>;
\n

Don’t put quotes around curly braces when embedding a JavaScript expression in an attribute. You should either use quotes (for string values) or curly braces (for expressions), but not both in the same attribute.

\n
\n

Warning:

\n

Since JSX is closer to JavaScript than to HTML, React DOM uses camelCase property naming convention instead of HTML attribute names.

\n

For example, class becomes className in JSX, and tabindex becomes tabIndex.

\n
\n

Specifying Children with JSX

\n

If a tag is empty, you may close it immediately with />, like XML:

\n
const element = <img src={user.avatarUrl} />;
\n

JSX tags may contain children:

\n
const element = (\n  <div>\n    <h1>Hello!</h1>\n    <h2>Good to see you here.</h2>\n  </div>\n);
\n

JSX Prevents Injection Attacks

\n

It is safe to embed user input in JSX:

\n
const title = response.potentiallyMaliciousInput;\n// This is safe:\nconst element = <h1>{title}</h1>;
\n

By default, React DOM escapes any values embedded in JSX before rendering them. Thus it ensures that you can never inject anything that’s not explicitly written in your application. Everything is converted to a string before being rendered. This helps prevent XSS (cross-site-scripting) attacks.

\n

JSX Represents Objects

\n

Babel compiles JSX down to React.createElement() calls.

\n

These two examples are identical:

\n
const element = (\n  <h1 className=\"greeting\">\n    Hello, world!\n  </h1>\n);
\n
const element = React.createElement(\n  'h1',\n  {className: 'greeting'},\n  'Hello, world!'\n);
\n

React.createElement() performs a few checks to help you write bug-free code but essentially it creates an object like this:

\n
// Note: this structure is simplified\nconst element = {\n  type: 'h1',\n  props: {\n    className: 'greeting',\n    children: 'Hello, world!'\n  }\n};
\n

These objects are called “React elements”. You can think of them as descriptions of what you want to see on the screen. React reads these objects and uses them to construct the DOM and keep it up to date.

\n

We will explore rendering React elements to the DOM in the next section.

\n
\n

Tip:

\n

We recommend using the “Babel” language definition for your editor of choice so that both ES6 and JSX code is properly highlighted.

\n
","frontmatter":{"title":"Introducing JSX","next":"rendering-elements.html","prev":"hello-world.html"},"fields":{"path":"content/docs/introducing-jsx.md","slug":"docs/introducing-jsx.html"}}},"pageContext":{"slug":"docs/introducing-jsx.html"}},"staticQueryHashes":[]}