open-index/open-npm huggingface dataset:
npm package: @micahjones13/angular-lib
Description: This library was generated with [Angular CLI](https://github.com/angular/angular-cli) version 13.2.0.
Latest version: 0.0.16

# AngularLib

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

## Code scaffolding

Run `ng generate component component-name --project angular-lib` to generate a new component. You can also use `ng generate directive|pipe|service|class|guard|interface|enum|module --project angular-lib`.
> Note: Don't forget to add `--project angular-lib` or else it will be added to the default project in your `angular.json` file. 

## Build

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

## Publishing

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

## Running unit tests

Run `ng test angular-lib` 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 Overview and Command Reference](https://angular.io/cli) page.
npm package: @micahjones13/angular-workspace
Description: This project was generated with [Angular CLI](https://github.com/angular/angular-cli) version 13.2.6.
Latest version: 0.0.3

# AngularWorkspace

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

## Development server

Run `ng serve` for a dev server. Navigate to `http://localhost:4200/`. The app will automatically reload if you change any of the source files.

## Code scaffolding

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

## Build

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

## Running unit tests

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

## Running end-to-end tests

Run `ng e2e` to execute the end-to-end tests via a platform of your choice. To use this command, you need to first add a package that implements end-to-end testing capabilities.

## Further help

To get more help on the Angular CLI use `ng help` or go check out the [Angular CLI Overview and Command Reference](https://angular.io/cli) page.
npm package: @micahjones13/angular-wrapper
Description: This library was generated with [Angular CLI](https://github.com/angular/angular-cli) version 13.2.0.
Latest version: 0.0.1

# ComponentLibrary

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

## Code scaffolding

Run `ng generate component component-name --project component-library` to generate a new component. You can also use `ng generate directive|pipe|service|class|guard|interface|enum|module --project component-library`.
> Note: Don't forget to add `--project component-library` or else it will be added to the default project in your `angular.json` file. 

## Build

Run `ng build component-library` to build the project. The build artifacts will be stored in the `dist/` directory.

## Publishing

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

## Running unit tests

Run `ng test component-library` 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 Overview and Command Reference](https://angular.io/cli) page.
npm package: @micahjones13/react
Description: Astro Web Components React Wrapper
Latest version: 7.6.7

# Installation

`npm i @astrouxds/react`

## Import and Usage

First, import the css into either your index.js, app.js, or any CSS file you would like.

`import '@astrouxds/astro-web-components/dist/astro-web-components/astro-web-components.css'`

Next, Import any desired Astro components the same way you would any other React component.

`import { RuxProgress } from '@astrouxds/react`

You can now use astro-components as regular React components.

```
import React from 'react';

const MyComp = () => {
    return (
        <div>
            <RuxProgress />
        </div>
    )
}

export default MyComp;
```

## Astro Stencil Components Docs

Docs for all components can be found at our [Astro Stencil Storybook,](https://astro-stencil.netlify.app/) and in our [web-components package]('../packages/web-components/README.md)

### Known Issues

- CSS custom properties for our react-wrapped components are undefined out of the box, thus the necessity for the CSS import.
- For using checkbox, push button, or switch onRuxchange events, you need to check for the checked prop:
  ```
          <RuxSwitch
        value="switch"
        onRuxchange={(e: React.ChangeEvent<HTMLRuxSwitchElement>) =>
          setSwitchVal(e.target.checked ? e.target.value : "")
        }
      />
  ```
npm package: @micahjones13/react-starter
Description: This starter kit was intitialized with `create-react-app` and scaffolded with the dependencies needed to use Astro web components in React.
Latest version: 1.0.1

# Astro Web Components in React

This starter kit was intitialized with `create-react-app` and scaffolded with the dependencies needed to use Astro web components in React.

## Getting Started

`npm install`

Import any desired Astro components the same way you would any other React component.

`import { RuxProgress } from '@astrouxds/react`

You can now use astro-components as regular React components.

```
import React from 'react';

const MyComp = () => {
    return (
        <div>
            <RuxProgress />
        </div>
    )
}

export default MyComp;
```

### Dependencies

- [`@astrouxds/react`](https://www.npmjs.com/package/@astrouxds/react)

### Boilerplate

- Astro UXDS stylesheet import on `index.js`.
- Roboto font loading in `index.html`.

### Resources

- [@astrouxds/astro-web-components](https://www.npmjs.com/package/@astrouxds/astro-web-components)

- [Astro Components Storybook](https://astro-stencil.netlify.app/?path=/story/astro-uxds-welcome-start-here--page)

- [Astro Github](https://github.com/RocketCommunicationsInc/astro)

# Getting Started with Create React App

This project was bootstrapped with [Create React App](https://github.com/facebook/create-react-app).

## Available Scripts

In the project directory, you can run:

### `npm start`

Runs the app in the development mode.\
Open [http://localhost:3000](http://localhost:3000) to view it in the browser.

The page will reload if you make edits.\
You will also see any lint errors in the console.

### `npm test`

Launches the test runner in the interactive watch mode.\
See the section about [running tests](https://facebook.github.io/create-react-app/docs/running-tests) for more information.

### `npm run build`

Builds the app for production to the `build` folder.\
It correctly bundles React in production mode and optimizes the build for the best performance.

The build is minified and the filenames include the hashes.\
Your app is ready to be deployed!

See the section about [deployment](https://facebook.github.io/create-react-app/docs/deployment) for more information.

### `npm run eject`

**Note: this is a one-way operation. Once you `eject`, you can’t go back!**

If you aren’t satisfied with the build tool and configuration choices, you can `eject` at any time. This command will remove the single build dependency from your project.

Instead, it will copy all the configuration files and the transitive dependencies (webpack, Babel, ESLint, etc) right into your project so you have full control over them. All of the commands except `eject` will still work, but they will point to the copied scripts so you can tweak them. At this point you’re on your own.

You don’t have to ever use `eject`. The curated feature set is suitable for small and middle deployments, and you shouldn’t feel obligated to use this feature. However we understand that this tool wouldn’t be useful if you couldn’t customize it when you are ready for it.