open-index/open-npm huggingface dataset:
npm package: @hpe.com/hew
Description: [![Netlify Status](https://api.netlify.com/api/v1/badges/2421c10f-be2e-402e-bf63-b200c1fdd750/deploy-status)](https://app.netlify.com/sites/hew-ui/deploys)
Latest version: 0.6.54

[![Netlify Status](https://api.netlify.com/api/v1/badges/2421c10f-be2e-402e-bf63-b200c1fdd750/deploy-status)](https://app.netlify.com/sites/hew-ui/deploys)

# hew

hew is a UI kit containing useful react components and common styles
for products by determined.ai.

## Live preview

[https://hew-ui.netlify.app/]

## How to use

We're currently unpublished while we set up an NPM organization, so install from
the github repo like this:

```bash
npm install @hpe.com/hew
```

Components are exported both at the top level module and as individual modules:

```tsx
import { Avatar } from '@hpe.com/hew';
import Card from '@hpe.com/hew/Card';
```

Related styling is imported alongside the module as a css file. Be sure your
build solution knows how to resolve `.css` imports.

## How to develop

Development requires Node.js version >= 18.

Bundling and the dev server is handled by vite. Run `npm start` or `npm run dev`
to start a dev server pointing to the design kit page.

When adding a new component, remember to:

- Add and document its functionality in the Design Kit (`src/DesignKit.tsx`)
- Aggregate its public facing exports in the index file (`src/index.ts`)

If the component is in a folder with an index module, remember to add the export to `package.json`

## How to release

With your changes safely in the main branch, kick off a new "publish-to-npm"
workflow in the [actions
view](https://github.com/determined-ai/hew/actions/workflows/publish-to-npm.yml):
to bump the version number of the package as well as push it as a git tag for
others. You can bump to the next major, minor, or patch version, or bump to an
arbitrary version using the npm version command line.

## Working between hew and another repo

Sometimes, you'll have to update hew as an upstream change to another repo, like determined. Here's how to handle that process:

- When you're working locally and want to check your ui kit changes in your other repo:
  - make sure you're using the same version of node between hew and your other repo
  - run `npm link` in the hew repo folder
  - run `npm link hew` in the other repo's folder
  - - remember to run `npm unlink hew` when you're done!
- When committing changes to the other repo downstream of unmerged changes in the UIKit
  - install the ui kit such that it matches the branch you're working on with `npm install https://git@github.com/determined-ai/hew.git#<BRANCH_NAME_HERE>` and commit the package.lock
  - repeat the above as new changes come from your upstream
  - - remember to switch back to a tagged version when your upstream changes are merged with `npm install https://git@github.com/determined-ai/hew.git#<VERSION_NUMBER_HERE>`
npm package: @hpe.com/vite-plugin-svg-to-jsx
Description: A vite plugin for transforming svg to jsx
Latest version: 1.0.4

# vite-plugin-svg-to-jsx
A function to transform svg to react

```tsx
const svgToReact = (config: SvgoConfig): Plugin[]
```

## How to use


```tsx
import { svgToReact } from 'vite-plugin-svg-to-jsx';
```


## How to release

With your changes safely in the main branch, run:

```sh
npm version patch # also takes minor or major
```

to bump the version number of the package as well as push it as a git tag for others.

## Working between hew and another repo

Sometimes, you'll have to update hew as an upstream change to another repo, like determined. Here's how to handle that process:

- When you're working locally and want to check your ui kit changes in your other repo:
  - make sure you're using the same version of node between this and your other repo
  - run `npm link` in this repo folder
  - run `npm link vite-plugin-svg-to-jsx --save` in the other repo's folder
  - - remember to run `npm unlink vite-plugin-svg-to-jsx` when you're done!