JSPM

@rindo/core

2.18.0
  • ESM via JSPM
  • ES Module Entrypoint
  • Export Map
  • Keywords
  • License
  • Repository URL
  • TypeScript Types
  • README
  • Created
  • Published
  • Downloads 20
  • Score
    100M100P100Q74936F
  • License MIT

A Compiler for Web Components and Progressive Web Apps

Package Exports

  • @rindo/core
  • @rindo/core/internal
  • @rindo/core/internal/app-data
  • @rindo/core/internal/client
  • @rindo/core/internal/client/index.js
  • @rindo/core/internal/index.js
  • @rindo/core/internal/rindo-core/index.cjs
  • @rindo/core/internal/rindo-core/index.js

This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (@rindo/core) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.

Readme

rindo-logo

Rindo

A compiler for generating Web Components

Rindo is a simple compiler for generating Web Components and static site generated progressive web apps (PWA). Rindo was built by the Navify team for its next generation of performant mobile and desktop Web Components.

Rindo combines the best concepts of the most popular frontend frameworks into a compile-time rather than run-time tool. It combines TypeScript, JSX, an asynchronous rendering pipeline to ensure smooth running animations and lazy-loading, to generate 100% standards-based Web Components that run on both modern browsers and legacy browsers.

Rindo components are just Web Components, so they work in any major framework or with no framework at all. In many cases, Rindo can be used as a drop in replacement for traditional frontend frameworks given the capabilities now available in the browser, though using it as such is certainly not required.

Rindo also enables a number of key capabilities on top of Web Components, in particular Server Side Rendering (SSR) without the need to run a headless browser, pre-rendering, and objects-as-properties (instead of just strings).

Getting Started

To create a new project using an interactive cli, run:

npm init rindo

To start developing your new Rindo project, run:

npm start

Creating components

Rindo components are TypeScript classes with decorator metadata. The decorators themselves are purely build-time annotations so the compiler can read metadata about each component, and removed entirely for smaller efficient components.

Create new components by creating files with a .tsx extension, such as my-component.tsx, and place them in src/components.

import { Component, Prop, h } from '@rindo/core';

@Component({
  tag: 'my-component',
  styleUrl: 'my-component.css'
})
export class MyComponent {

  @Prop() first: string;
  @Prop() last: string;

  render() {
    return (
      <div>
        Hello, my name is {this.first} {this.last}
      </div>
    );
  }
}

To use this component, just use it like any other HTML element:

<my-component first="Rindo" last="JS"></my-component>

Thanks

Rindo's internal testing suite is supported by the BrowserStack Open-Source Program