open-index/open-npm huggingface dataset:
npm package: @microfox/zoominfo
Description: Microfox SDK for ZoomInfo.
Latest version: 1.0.2

<p align="center">
  <a href="https://microfox.so">
    <img alt="Microfox" src="https://raw.githubusercontent.com/microfox-ai/microfox/main/docs/media/microfox-header.jpg" width="308">
  </a>
</p>

<p align="center">
  <em>AI agent stdlib that works with any LLM and TypeScript AI SDK.</em>
</p>

<p align="center">
  <a href="https://github.com/microfox-ai/microfox/actions/workflows/main.yml"><img alt="Build Status" src="https://github.com/microfox-ai/microfox/actions/workflows/main.yml/badge.svg" /></a>
  <a href="https://www.npmjs.com/package/@microfox/stdlib"><img alt="NPM" src="https://img.shields.io/npm/v/@microfox/stdlib.svg" /></a>
  <a href="https://github.com/microfox-ai/microfox/blob/main/license"><img alt="MIT License" src="https://img.shields.io/badge/license-MIT-blue" /></a>
  <a href="https://prettier.io"><img alt="Prettier Code Formatting" src="https://img.shields.io/badge/code_style-prettier-brightgreen.svg" /></a>
</p>

# Microfox

**See the [github repo](https://github.com/microfox-ai/microfox) or [docs](https://microfox.so) for more info.**
npm package: @microfrontend-example/core
Description: An event-driven orchestration layer
Author: Robert H. Hameetman
Latest version: 0.2.69

# microfrontend-example

## Entities

### Registry

Manages an aggregation of `Service`s.

### Orchestrator

Determines whether or not the orchestration process should run.

### Router

Handles navigation and routing.

### Service

Represents each service in the system. Handles loading, mounting, and unmounting
of services.

## Statuses

| **Status**        |     |
| ----------------- | --: |
| `REGISTERED`      |     |
| `LOADED`          |     |
| `LOAD_ERROR`      |     |
| `BOOTSTRAPPED`    |     |
| `BOOTSTRAP_ERROR` |     |
| `MOUNTED`         |     |
| `MOUNT_ERROR`     |     |
| `RUNNING`         |     |
| `STOPPED`         |     |
| `UNMOUNTED`       |     |
| `UNMOUNT_ERROR`   |     |
| `SKIPPED`         |     |

## Events

| **Event**                 |     |
| ------------------------- | --: |
| `<service>:CHANGE_STATUS` |     |
| `<service>:REGISTER`      |     |
| `<service>:LOAD`          |     |
| `<service>:MOUNT`         |     |
| `<service>:STOP`          |     |
| `<service>:UNMOUNT`       |     |
| `<service>:UNLOAD`        |     |
| `<service>:BEFORE_CHANGE` |     |
| `<service>:NO_APP_CHANGE` |     |
| `<service>:ROUTING_EVENT` |     |

## Process

Fire Event => Update Status => Call Hooks

start() => reroute()

### Registration

The shell calls `registerApplication()` and passes in a name, a load hook, a route
activation function, and an optional set of custom props for each service.

`registerApplication()` fires an `APP_REGISTER` event. Since the s

### Orchestration

## Structure

## Apps

<!--
  Note: I could call `services` "apps" and probably would if I weren't building
  something basically like Microsoft's office.com, a distributed solution for
  enterprise-level suites of apps, so "apps" has an additional user context in
  this case.
 -->

Domain-focused solutions for performing complex integrated business logic.

- `admin`: A portal for managing users, groups, and roles
- `billing`: A portal for managing users, groups, and roles
- `portal`: The primary 'hub' for accessing apps

### Packages

Cross-domain integrations and shared functionality go here.

- `core`: An advanced event-driven orchestration layer
- `scripts`: A powerful shared build pipeline for centralized automation and other cool shib

### Services

Smaller services with more fragmented logic and little-to-no UI should go
here.

- `auth`: A portal for managing users, groups, and roles
- `data`: A GraphQL Apollo server for data aggregation logic

### Shell/Frame

The shell is the orchestration layer served as `index.html` responsible for
registering, loading, mounting, unmounting, and unloading services.
npm package: @microfrontend-example/jsx
Description: JSX rendering logic for Omniframe.
Author: Robert H. Hameetman
Latest version: 0.0.2

![Omniframe][header]

[![npm][npm-badge]][npm-badge-url]
[![Build & Test](https://github.com/omniframe/omniframe/workflows/Build%20&%20Test/badge.svg)](https://github.com/omniframe/omniframe/actions)
[![Release](https://github.com/omniframe/omniframe/workflows/Release/badge.svg)](https://github.com/omniframe/omniframe/actions)
[![license][npm-license]][npm-license-url]

# 📦 @omniframe/jsx

JSX rendering logic for Omniframe.

---

- [📦 @omniframe/jsx](#-omniframejsx)
  - [💼 [§1.0] Getting Started](#-10-getting-started)
  - [🛠 [§2.0] Building Services](#-20-building-services)
    - [[§2.1] Creating Components](#21-creating-components)
  - [📄 [§3.0] License](#-30-license)

---

```bash
npm init omniframe
```

Omniframe is a new approach to Front End microservice orchestration which
combines asynchronous rendering with organic event-driven service management.

## 💼 [§1.0] Getting Started

Create a new project using the Omniframe interactive CLI:

```bash
npm init omniframe
```

Spin up the app in `development`:

```bash
npm run dev
```

Or in `production`:

```bash
npm start
```

## 🛠 [§2.0] Building Services

To get started building services, run the following command:

```bash
npm init @omniframe/service <service>
```

### [§2.1] Creating Components

Once your new service is up and running, you may begin adding new components by
running the following command in the service's root directory:

```bash
npm run make component ./components/Example
```

## 📄 [§3.0] License

This project is licensed under the MIT License.
See the [LICENSE.md](LICENSE.md) file for details

[header]: /.github/readme.png 'Omniframe'
[npm-badge]: https://img.shields.io/npm/v/@omniframe/core.svg
[npm-badge-url]: https://www.npmjs.com/package/@omniframe/core
[npm-license]: https://img.shields.io/npm/l/@omniframe/core.svg
[npm-license-url]: https://github.com/omniframe/omniframe/blob/master/LICENSE
npm package: @microfrontend-example/scripts
Description: A powerful shared build pipeline for centralized automation and other cool shib
Author: Robert H. Hameetman
Latest version: 1.1.76

# microfrontend-example

## Entities

### Registry

Manages an aggregation of `Service`s.

### Orchestrator

Determines whether or not the orchestration process should run.

### Router

Handles navigation and routing.

### Service

Represents each service in the system. Handles loading, mounting, and unmounting
of services.

## Statuses

| **Status**        |     |
| ----------------- | --: |
| `REGISTERED`      |     |
| `LOADED`          |     |
| `LOAD_ERROR`      |     |
| `BOOTSTRAPPED`    |     |
| `BOOTSTRAP_ERROR` |     |
| `MOUNTED`         |     |
| `MOUNT_ERROR`     |     |
| `RUNNING`         |     |
| `STOPPED`         |     |
| `UNMOUNTED`       |     |
| `UNMOUNT_ERROR`   |     |
| `SKIPPED`         |     |

## Events

| **Event**                 |     |
| ------------------------- | --: |
| `<service>:CHANGE_STATUS` |     |
| `<service>:REGISTER`      |     |
| `<service>:LOAD`          |     |
| `<service>:MOUNT`         |     |
| `<service>:STOP`          |     |
| `<service>:UNMOUNT`       |     |
| `<service>:UNLOAD`        |     |
| `<service>:BEFORE_CHANGE` |     |
| `<service>:NO_APP_CHANGE` |     |
| `<service>:ROUTING_EVENT` |     |

## Process

Fire Event => Update Status => Call Hooks

start() => reroute()

### Registration

The shell calls `registerApplication()` and passes in a name, a load hook, a route
activation function, and an optional set of custom props for each service.

`registerApplication()` fires an `APP_REGISTER` event. Since the s

### Orchestration

## Structure

## Apps

<!--
  Note: I could call `services` "apps" and probably would if I weren't building
  something basically like Microsoft's office.com, a distributed solution for
  enterprise-level suites of apps, so "apps" has an additional user context in
  this case.
 -->

Domain-focused solutions for performing complex integrated business logic.

- `admin`: A portal for managing users, groups, and roles
- `billing`: A portal for managing users, groups, and roles
- `portal`: The primary 'hub' for accessing apps

### Packages

Cross-domain integrations and shared functionality go here.

- `core`: An advanced event-driven orchestration layer
- `scripts`: A powerful shared build pipeline for centralized automation and other cool shib

### Services

Smaller services with more fragmented logic and little-to-no UI should go
here.

- `auth`: A portal for managing users, groups, and roles
- `data`: A GraphQL Apollo server for data aggregation logic

### Shell/Frame

The shell is the orchestration layer served as `index.html` responsible for
registering, loading, mounting, unmounting, and unloading services.
npm package: @microfrontend-iframe-plugins/micro-app-element
Description: Custom HTML element for embedding microfrontend iframe-based plugins
Latest version: 1.0.4
Deprecated: Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.

## Getting started

### Host application

To get started with micro apps in your host application, install `@microfrontend-iframe-plugins/micro-app-element` with your package manager:

- npm: `npm install @microfrontend-iframe-plugins/micro-app-element`
- yarn: `yarn add @microfrontend-iframe-plugins/micro-app-element`

TODO: examples at microfrontend-iframe-plugins.github.io

TODO: guide on how to use 
TODO: Routing
TODO: Explain how loading of micro apps works

TODO: augmentation of `@microfrontend-iframe-plugins/types`

### Micro App

You can use any framework and any tools of your choice to create micro apps to be embedded in your host application, you simply need to make sure your micro app cooperates with the host application. 

To get started, install `@microfrontend-iframe-plugins/types` as a development dependency with your package manager:

- npm: `npm install --save-dev @microfrontend-iframe-plugins/types`
- yarn: `yarn add --dev @microfrontend-iframe-plugins/types`

In case you created a package that augments these types, you install your package instead.
npm package: @microfrontend/client
Description: Microfrontend client
Author: Taras Demyanets
Latest version: 1.6.0

# Production-quality controller for microfrontend applications

Enterprise-scale applications need a very high degree of integration and isolation between modules therefore iframes still remain the best solution to achieve it. However every browser has only one address field so you need a controller to handle many application routes simultaneously.

Microfrontend libries provide you exactly this type of functionality with a strong focus on a production quality of code.

This is the client library that shall be included into the microfrontend together with the [@microfrontend/common](https://www.npmjs.com/package/@microfrontend/common) library.

## Credits

The original idea comes from Manfred Steyer and his [meta-spa-router](https://github.com/manfredsteyer/meta-router).

Manfred has also supported this development effort at [s IT Solutions AT Spardat GmbH](https://www.s-itsolutions.at/en/home) with his valuable advice and useful hints. 

## Features

- The controller loads microfrontends (aka routed applications) in iframes
- Microfrontends are isolated and cannot influence each other in an unplanned way 
- Microfrontends may use any SPA framework
- Controller supports switching to a specific route within a child app
- Controller synchronizes microfrontend's routes with the route of the shell
- Solution supports flexible configuration of iframes
- Solution respects origins to prevent CORS issues

## Overall design

This project was generated with [Angular CLI](https://github.com/angular/angular-cli) but only its toolset was used.

Controller libraries do not have any run-time dependencies and are free from side-effects and shall be therefore compatible with any SPA framework.

Name | Description | Required in a shell | Required in a microfrontend
------------ | -------------| -------------| -------------
[@microfrontend/common](https://www.npmjs.com/package/@microfrontend/common) | Shared code | yes | yes
[@microfrontend/controller](https://www.npmjs.com/package/@microfrontend/controller) | Controller code | yes | no
[@microfrontend/client](https://www.npmjs.com/package/@microfrontend/client) | Microfrontend code | no | yes

## Install

This is a [Node.js](https://nodejs.org/en/) module available through the
[npm registry](https://www.npmjs.com/). Installation is done using the
[`npm install` command](https://docs.npmjs.com/getting-started/installing-npm-packages-locally):

```bash
$ npm install @microfrontend/common
$ npm install @microfrontend/client
```

## Documentation

Additional documentation is located in [GitHub repository](https://github.com/demyanets/microfrontend).

## License

MIT
npm package: @microfrontend/common
Description: Microfrontend shared components
Author: Taras Demyanets
Latest version: 1.6.0

# Production-quality controller for microfrontend applications

Enterprise-scale applications need a very high degree of integration and isolation between modules therefore iframes still remain the best solution to achieve it. However every browser has only one address field so you need a controller to handle many application routes simultaneously.

Microfrontend libries provide you exactly this type of functionality with a strong focus on a production quality of code.

This library contains shared code and shall be normally used together with [@microfrontend/client](https://www.npmjs.com/package/@microfrontend/common) or [@microfrontend/controller](https://www.npmjs.com/package/@microfrontend/controller) libraries.

## Credits

The original idea comes from Manfred Steyer and his [meta-spa-router](https://github.com/manfredsteyer/meta-router).

Manfred has also supported this development effort at [s IT Solutions AT Spardat GmbH](https://www.s-itsolutions.at/en/home) with his valuable advice and useful hints. 

## Features

- The controller loads microfrontends (aka routed applications) in iframes
- Microfrontends are isolated and cannot influence each other in an unplanned way 
- Microfrontends may use any SPA framework
- Controller supports switching to a specific route within a child app
- Controller synchronizes microfrontend's routes with the route of the shell
- Solution supports flexible configuration of iframes
- Solution respects origins to prevent CORS issues

## Overall design

This project was generated with [Angular CLI](https://github.com/angular/angular-cli) but only its toolset was used.

Controller libraries do not have any run-time dependencies and are free from side-effects and shall be therefore compatible with any SPA framework.

Name | Description | Required in a shell | Required in a microfrontend
------------ | -------------| -------------| -------------
[@microfrontend/common](https://www.npmjs.com/package/@microfrontend/common) | Shared code | yes | yes
[@microfrontend/controller](https://www.npmjs.com/package/@microfrontend/controller) | Controller code | yes | no
[@microfrontend/client](https://www.npmjs.com/package/@microfrontend/client) | Microfrontend code | no | yes

## Install

This is a [Node.js](https://nodejs.org/en/) module available through the
[npm registry](https://www.npmjs.com/). Installation is done using the
[`npm install` command](https://docs.npmjs.com/getting-started/installing-npm-packages-locally):

```bash
$ npm install @microfrontend/common
```

## Documentation

Additional documentation is located in [GitHub repository](https://github.com/demyanets/microfrontend).

## License

MIT
npm package: @microfrontend/controller
Description: Microfrontend controller
Author: Taras Demyanets
Latest version: 1.10.0

# Production-quality controller for microfrontend applications

Enterprise-scale applications need a very high degree of integration and isolation between modules therefore iframes still remain the best solution to achieve it. However every browser has only one address field so you need a controller to handle many application routes simultaneously.

Microfrontend libries provide you exactly this type of functionality with a strong focus on a production quality of code.

This is the application shell library that shall be included into the application controller together with the [@microfrontend/common](https://www.npmjs.com/package/@microfrontend/common) library.

## Credits

The original idea comes from Manfred Steyer and his [meta-spa-router](https://github.com/manfredsteyer/meta-router).

Manfred has also supported this development effort at [s IT Solutions AT Spardat GmbH](https://www.s-itsolutions.at/en/home) with his valuable advice and useful hints. 

## Features

- The controller loads microfrontends (aka routed applications) in iframes
- Microfrontends are isolated and cannot influence each other in an unplanned way 
- Microfrontends may use any SPA framework
- Controller supports switching to a specific route within a child app
- Controller synchronizes microfrontend's routes with the route of the shell
- Solution supports flexible configuration of iframes
- Solution respects origins to prevent CORS issues

## Overall design

This project was generated with [Angular CLI](https://github.com/angular/angular-cli) but only its toolset was used.

Controller libraries do not have any run-time dependencies and are free from side-effects and shall be therefore compatible with any SPA framework.

Name | Description | Required in a shell | Required in a microfrontend
------------ | -------------| -------------| -------------
[@microfrontend/common](https://www.npmjs.com/package/@microfrontend/common) | Shared code | yes | yes
[@microfrontend/controller](https://www.npmjs.com/package/@microfrontend/controller) | Controller code | yes | no
[@microfrontend/client](https://www.npmjs.com/package/@microfrontend/client) | Microfrontend code | no | yes

## Install

This is a [Node.js](https://nodejs.org/en/) module available through the
[npm registry](https://www.npmjs.com/). Installation is done using the
[`npm install` command](https://docs.npmjs.com/getting-started/installing-npm-packages-locally):

```bash
$ npm install @microfrontend/common
$ npm install @microfrontend/controller
```

## Documentation

Additional documentation is located in [GitHub repository](https://github.com/demyanets/microfrontend).

## License

MIT
npm package: @microfrontendly/angular-element-routing
Description: This library was generated with [Angular CLI](https://github.com/angular/angular-cli) version 10.1.4.
Author: Marcin Milewicz
Latest version: 0.0.4

# AngularRoutes

This library was generated with [Angular CLI](https://github.com/angular/angular-cli) version 10.1.4.

## Code scaffolding

Run `ng generate component component-name --project angular-element-routing` to generate a new component. You can also use `ng generate directive|pipe|service|class|guard|interface|enum|module --project angular-element-routing`.

> Note: Don't forget to add `--project angular-element-routing` or else it will be added to the default project in your `angular.json` file.

## Build

Run `ng build angular-element-routing` to build the project. The build artifacts will be stored in the `dist/` directory.

## Publishing

After building your library with `ng build angular-element-routing`, go to the dist folder `cd dist/angular-element-routing` and run `npm publish`.

## Running unit tests

Run `ng test angular-element-routing` to execute the unit tests via [Karma](https://karma-runner.github.io).

## Further help

To get more help on the Angular CLI use `ng help` or go check out the [Angular CLI README](https://github.com/angular/angular-cli/blob/master/README.md).