jsx

The JSX specification is a XML-like syntax extension to ECMAScript. (by facebook)

Jsx Alternatives

Similar projects and alternatives to jsx

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a better jsx alternative or higher similarity.

jsx reviews and mentions

Posts with mentions or reviews of jsx. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2023-05-12.
  • I am having to pass down 8+ props even for simple components. What are some common ways to mitigate this? (Typescript)
    2 projects | /r/reactjs | 12 May 2023
    Svelte syntax? Yes, there is upcoming initiative JSX 2.0 which includes shorthands like that. However, have no idea whether it will be released any time soon. So let's say "this is part of React/JSX 1.0" (shrugging)
  • Why TypeScript is the better JavaScript
    2 projects | dev.to | 7 May 2023
    Inherent support for JSX in the language itself
  • Node.js やReact、ESM、Viteの説明
    7 projects | dev.to | 21 Jan 2023
    JavaScript + HTML(DOM)= JSX
  • Alpine.js
    17 projects | news.ycombinator.com | 13 Jan 2023
    FWIW, the className prop is a React thing not a JSX thing. Other libraries which use JSX will happily accept a plain class prop. The React limitation is abstraction leakage: props are not attributes, they map to DOM properties.

    But to the point that JSX is a DSL, that limitation is specifically because React itself is very tightly coupled to DOM semantics… but JSX explicitly has no built in semantics[1].

    1: First sentence of https://facebook.github.io/jsx/ - “JSX is an XML-like syntax extension to ECMAScript without any defined semantics.”

  • React - Introducing JSX
    2 projects | dev.to | 6 Sep 2022
    JSX stands for 'JavaScript XML' and is a syntax extension for JavaScript. It is used to create DOM elements that are then rendered in the React DOM. Although it looks like HTML, it is actually an XML-like syntax specifically written for use in React. Interestingly, JSX is not valid JavaScript either. JSX needs to be compiled by a tool like Babel to be translated into regular JavaScript that a browser can understand. Put simply, JSX describes what the UI should look like, and React takes care of properly rendering it.
  • Web lagnunages to learn
    3 projects | /r/learnprogramming | 29 Jul 2022
  • My thoughts on Mithril.js
    7 projects | dev.to | 3 May 2022
    Alternatively, you can use JSX syntax (like with React), but then you need build-tools.
  • Incrementally adopting TypeScript in a create-react-app project
    6 projects | dev.to | 11 Jan 2022
    Note: For React component files (JSX) we'll use .tsx to maintain JSX support and for non React files we'll use the .ts file extension. However, if you want you could still use .ts file extension for React components without any problem.
  • Sciter, the 5 MB Electron alternative, has switched to JavaScript
    16 projects | news.ycombinator.com | 30 Dec 2021
    I’m concerned that you’re falling into the same trap here with integrating your own variant of JSX, and mulling over adding more things like hyphens in unquoted object literal keys.

    JSX is popular enough that it’s safe, ECMAScript isn’t going to break it, but your alterations to JSX are already significantly incompatible: you have being equivalent to JSX("input", {"class": "search"}, null), but the JSX everyone else is using has that equivalent to JSX(input.search, {}, null). I’m not certain if your JSX syntax is supposed to be able to be used with React code or anything else that uses JSX syntax, but if yes then it’ll be broken in a significant number of cases so that it’s worse than useless, and if no, well, it’s going to be misleading, and what if JSX did get merged into ECMAScript in some form? Then you’d be incompatible with ECMAScript again.

    Same deal with hyphens in unquoted object literal keys: it’s not part of ECMAScript now, but just because it’d be a syntax error now doesn’t mean it always will be. Decorators in TypeScript are a good example of things going badly wrong even when an extremely popular project is involved.

    I say: if you want to go JavaScript, go JavaScript, maaaaaybe plus standard JSX conforming with <https://facebook.github.io/jsx/>, and no further. Even if what you do is obviously superior, &c. &c. I’d apply the same reasoning on your fork of CSS: you introduced it for a good reason back then, but now it’s just friction, even if it’s a little better in a vacuum (and maybe it is in parts, maybe it isn’t in other parts).

  • Do you think HTML is a programming language
    3 projects | /r/ProgrammerHumor | 24 Dec 2021
    Then it might be time for a pull request which identifies these parts as JSX.
  • A note from our sponsor - SaaSHub
    www.saashub.com | 25 Apr 2024
    SaaSHub helps you find the best software and product alternatives Learn more →

Stats

Basic jsx repo stats
14
1,944
0.0
5 months ago

Sponsored
SaaSHub - Software Alternatives and Reviews
SaaSHub helps you find the best software and product alternatives
www.saashub.com