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

@sackrin/react-micro-ui-express

v1.6.0

Published

This library adds the ability to quickly host a micro UI within a docker container. This library works alongside the react-micro-ui library.

Downloads

10

Readme

React Micro UI Express

This library adds the ability to quickly host a micro UI within a docker container. This library works alongside the react-micro-ui library.

Installation

npm i -s @sackrin/react-micro-ui-express

Usage

within your micro ui src/server.js

import path from "path";
import { ExampleComponent } from "./Components";
import { ExampleEndpoint } from './Endpoints';
import createExpressMicroUI from '@sackrin/react-micro-ui-express/lib/createExpressMicroUI';

// Retrieve the local config
const microUIConfig = require(path.join(process.cwd(), "microui.config.js"));
// Create the express micro UI
const { route, strap, boot } = createExpressMicroUI({
  profile: process.env.PROFILE || "local",
  config: microUIConfig,
});
// ENDPOINTS
// Add custom API endpoints
route('/ExampleEndpoint', 'get', ExampleEndpoint);
// SERVER SIDE RENDERED COMPONENTS
// Strap in the front end components
strap("ExampleComponent", ExampleComponent);
// Boot and handle the response
boot();

Create Express Micro UI

createExpressMicroUI

Use this to create your micro UI express container

  • config: the micro UI config
  • profile: the environment profile ie local, dev, stage
  • logger: your choice of logger

const { api, strap, boot, route, env, config, logger } = createExpressMicroUI({ config, profile = 'local', logger = console })

Callbacks

route(path, method, handler)

Use this to bootstrap API endpoint handlers

  • path: the api path
  • method: GET | POST | PUT | DELETE
  • handler: the handler which will be invoked

route('/example', 'GET', doExampleEndpoint)

strap(name, component)

Use this to bootstrap react components for server side rendering. Not required if you do not intend on providing server side rendered components.

  • name: the name of the component
  • component: the react component

strap('ExampleComponent', ExampleComponent)

boot()

Will start the express server

boot()

Extras

env

The current resolved environment the micro UI is using. This is calculated via the micro UI config and the supplied profile

config

The current config the micro UI is using.

logger

The current logger the micro UI is using. This will either be the logger you supplied or the default logger (console)