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

@frankhe/ui-component

v1.1.1

Published

This is a [storybook](https://storybook.js.org/) project.

Downloads

13

Readme

Aisera UI Component

This is a storybook project.

Getting Started

First, run the development server:

npm run dev

Story book development

To get started with component development, run the following command:

npm run storybook

We use storybook to document our components which are based on mui and react

Build and Deploy

docker build -t uicomponent .

docker run -p 8080:80 uicomponent


## Or if you want to use latest from the ECR
docker run --rm -p 8080:80 934101271236.dkr.ecr.us-west-2.amazonaws.com/uicomponent:latest

Expose React components

Webpack

  new ModuleFederationPlugin({
      name: "uicomponent",
      shared: {
      react: {
          requiredVersion: dependencies["react-dom"],
      },
      "react-dom": {
          requiredVersion: dependencies["react-dom"],
      },
      },
      exposes: {
        "./RequestDetailsPage": "./src/pages/request-details/RequestDetailsPage"
      },
      filename: "remoteEntry.js"
  }),

Setup root font-size to 16px

If react page is rendered and visible in Admin UI, make root font size to 16px, so the react pages can manage using rem.

main.css

html:has(div.react-entity-view:not([style*="display: none"])) {
  font-size: var(--font-size-medium);
}

Rendering bridge

To render react page in Admin UI we need to write renderer function (Refer ./src/pages/request-details/RequestDetailsPage.tsx)

Http Service

Currently using HttpCommand from zplex. Passing it as props

function RequestDetailsPage(props: IRequestDetailsPageProps, container: Element) {
  const { HttpCommand, ChatSimulatorView, request } = props;
  HttpService.setHttpCommand(HttpCommand);

  ...
}

Add context for commonly used data on page to avoid prop drilling

Using request: {botId, botDomain, actions: {handler}} set value for context, so can be used anywhere in page

function RequestDetailsPage(props: IRequestDetailsPageProps, container: Element) {
  const { HttpCommand, ChatSimulatorView, request } = props;
  ...

  const root = createRoot(container);
  return root.render(
      <RequestContext.Provider value={request}>
          <RequestDetailsComponent {...{ ChatSimulatorView }} />
      </RequestContext.Provider>
  );
}

Accessed context

const RequestDetailsComponent = () => {
  const {actions} = useContext(RequestContext);
  ...

  const handleBreadCrumbClick = () => {
    ...
    actions.handler(...);
  }

For more details see src/pages/request-details/RequestDetailsComponent.tsx, src/pages/request-details/RequestDetailsPage.tsx

Add new svg icons

  1. create react component from svg code
  • Refer MSTeamsIcon component for adding new channel icon
  • Refer AnnotateIcon component for adding custom icon
  1. add icon to stories
  • render newly created component in AiseraIcons

  • npm run rollup npm login npm publish --access public npm view @frankhe/ui-component