npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

@taterer/rx-jsx

v1.0.13

Published

Reactive Extensions with JSX (UI without React)

Downloads

12

Readme

Rx-JSX

A familiar way to develop a front end using JSX, but without React. Prop drilling and lifecycle events are all replaced with simply RxJS.

Why use RxJSX?

You prefer functional (reactive) programming, you'd rather not learn more abstractions on top of html to change styles, classes, or add event listeners. Minimalist code, with no magic: it does exactly what you expect it to do.

Getting Started

Install

yarn add @taterer/rx-jsx rxjs

or

npm i --save @taterer/rx-jsx rxjs

Setup

tsconfig.json

{
  "compilerOptions": {
    "jsx": "react",
    "jsxFactory": "JSX"
  }
}

Alternative or additional to tsconfig

.babelrc

{
  "plugins": [
    ["@babel/transform-react-jsx", { "pragma": "JSX" }]
  ]
}

Import

import '@taterer/rx-jsx' // this must be imported before any JSX is rendered
import App from './App'

document.getElementById('root')?.appendChild(<App />);

Define

This is enough to render JSX at any depth. App is expected to be a function that returns JSX. EG:

const App = () => <div />

The element can be defined with styles, class, events, or with children. EG:

const App = () => <div>
  <Route />
  <div class='panel' style="width: 100%;" onclick={() => console.log('clicked')} />
</div>

How to use

A full example codebase with exercises for training can be found at: https://github.com/taterer/rx-jsx

single$

Define single$ on an html element. When the JSX element is created it will automatically subscribe to the observable passed to single$. The observable should emit HTML elements. EG:

import { css } from '@emotion/css'
import { of } from 'rxjs'

export default function App () {
  const mainElement$ = of(
    <div class={css`
      display: flex;
      height: 100%;
      width: 100%;
    `}>
      Basic
    </div>
  )
  return (
    <div single$={mainElement$} />
  )
}

Using single$ will replace the HTML element with the latest emission. When single$ or multi$ has a pipe using takeUntil, it will remove the root element upon completion.

multi$

The multi$ property does the exact same thing as single$, except that it is append only. The previous element will not be removed with a new emission of the observable.

Best practices

  • Name observables/subjects using the $ suffix.
  • Always use a destruction$ observable in a takeUntil as the last operator in pipes before passing them to single$, multi$, or creating any subscriptions.
  • If things are not rendering properly, try withAnimationFrame. import { withAnimationFrame } from @taterer/rx-jsx
  • It can be useful to throw in a share() when setting up an observable for single$/multi$ so that other subscriptions end up with the same JSX element.
  • Use RxJS Debugger for tracking emissions https://www.npmjs.com/package/@taterer/rxjs-debugger