open-index/open-npm huggingface dataset:
npm package: @nomensa/nomensa-pfe-blocklist
Description: Pfe element for PatternFly Elements
Author: Kate Leigh
Latest version: 1.0.0-prerelease.14

# PatternFly Element | Pfe Element

## Dependencies

Make sure you have [Polyserve][polyserve] and [Web Component Tester][web-component-tester] installed.

    npm install -g polyserve web-component-tester

## Dev

    npm start

## Test

    npm run test

## Build

    npm run build

## Demo

Run `npm start` and Polyserve will start a server and open your default browser to the demo page of the element.

## Code style

Pfe (and all PatternFly Elements) use [Prettier][prettier] to auto-format JS and JSON.  The style rules get applied when you commit a change.  If you choose to, you can [integrate your editor][prettier-ed] with Prettier to have the style rules applied on every save.

[prettier]: https://github.com/prettier/prettier/
[prettier-ed]: https://github.com/prettier/prettier/#editor-integration
[polyserve]: https://github.com/Polymer/polyserve
[web-component-tester]: https://github.com/Polymer/web-component-tester
npm package: @nomensa/nomensa-pfe-blockquote
Description: Pfe element for PatternFly Elements
Author: Kate Leigh
Latest version: 1.0.3

# PatternFly Element | Pfe Element

## Dependencies

Make sure you have [Polyserve][polyserve] and [Web Component Tester][web-component-tester] installed.

    npm install -g polyserve web-component-tester

## Dev

    npm start

## Test

    npm run test

## Build

    npm run build

## Demo

Run `npm start` and Polyserve will start a server and open your default browser to the demo page of the element.

## Code style

Pfe (and all PatternFly Elements) use [Prettier][prettier] to auto-format JS and JSON.  The style rules get applied when you commit a change.  If you choose to, you can [integrate your editor][prettier-ed] with Prettier to have the style rules applied on every save.

[prettier]: https://github.com/prettier/prettier/
[prettier-ed]: https://github.com/prettier/prettier/#editor-integration
[polyserve]: https://github.com/Polymer/polyserve
[web-component-tester]: https://github.com/Polymer/web-component-tester
npm package: @nomensa/nomensa-pfe-card-list
Description: Pfe element for PatternFly Elements
Author: Kate Leigh
Latest version: 1.0.1

# PatternFly Element | Pfe Element

## Dependencies

Make sure you have [Polyserve][polyserve] and [Web Component Tester][web-component-tester] installed.

    npm install -g polyserve web-component-tester

## Dev

    npm start

## Test

    npm run test

## Build

    npm run build

## Demo

Run `npm start` and Polyserve will start a server and open your default browser to the demo page of the element.

## Code style

Pfe (and all PatternFly Elements) use [Prettier][prettier] to auto-format JS and JSON.  The style rules get applied when you commit a change.  If you choose to, you can [integrate your editor][prettier-ed] with Prettier to have the style rules applied on every save.

[prettier]: https://github.com/prettier/prettier/
[prettier-ed]: https://github.com/prettier/prettier/#editor-integration
[polyserve]: https://github.com/Polymer/polyserve
[web-component-tester]: https://github.com/Polymer/web-component-tester
npm package: @nomensa/nomensa-pfe-carousel
Description: Pfe element for PatternFly Elements
Author: Kate Leigh
Latest version: 1.0.12

# PatternFly Element | Pfe Element

## Dependencies

Make sure you have [Polyserve][polyserve] and [Web Component Tester][web-component-tester] installed.

    npm install -g polyserve web-component-tester

## Dev

    npm start

## Test

    npm run test

## Build

    npm run build

## Demo

Run `npm start` and Polyserve will start a server and open your default browser to the demo page of the element.

## Code style

Pfe (and all PatternFly Elements) use [Prettier][prettier] to auto-format JS and JSON.  The style rules get applied when you commit a change.  If you choose to, you can [integrate your editor][prettier-ed] with Prettier to have the style rules applied on every save.

[prettier]: https://github.com/prettier/prettier/
[prettier-ed]: https://github.com/prettier/prettier/#editor-integration
[polyserve]: https://github.com/Polymer/polyserve
[web-component-tester]: https://github.com/Polymer/web-component-tester
npm package: @nomensa/nomensa-pfe-empirix
Description: Pfe element for PatternFly Elements
Author: Kate Leigh
Latest version: 1.0.11

# PatternFly Element | Pfe Element

## Dependencies

Make sure you have [Polyserve][polyserve] and [Web Component Tester][web-component-tester] installed.

    npm install -g polyserve web-component-tester

## Dev

    npm start

## Test

    npm run test

## Build

    npm run build

## Demo

Run `npm start` and Polyserve will start a server and open your default browser to the demo page of the element.

## Code style

Pfe (and all PatternFly Elements) use [Prettier][prettier] to auto-format JS and JSON.  The style rules get applied when you commit a change.  If you choose to, you can [integrate your editor][prettier-ed] with Prettier to have the style rules applied on every save.

[prettier]: https://github.com/prettier/prettier/
[prettier-ed]: https://github.com/prettier/prettier/#editor-integration
[polyserve]: https://github.com/Polymer/polyserve
[web-component-tester]: https://github.com/Polymer/web-component-tester
npm package: @nomensa/nomensa-pfe-footer
Description: Pfe element for PatternFly Elements
Author: Kate Leigh
Latest version: 1.0.2

# PatternFly Element | Pfe Element

## Dependencies

Make sure you have [Polyserve][polyserve] and [Web Component Tester][web-component-tester] installed.

    npm install -g polyserve web-component-tester

## Dev

    npm start

## Test

    npm run test

## Build

    npm run build

## Demo

Run `npm start` and Polyserve will start a server and open your default browser to the demo page of the element.

## Code style

Pfe (and all PatternFly Elements) use [Prettier][prettier] to auto-format JS and JSON.  The style rules get applied when you commit a change.  If you choose to, you can [integrate your editor][prettier-ed] with Prettier to have the style rules applied on every save.

[prettier]: https://github.com/prettier/prettier/
[prettier-ed]: https://github.com/prettier/prettier/#editor-integration
[polyserve]: https://github.com/Polymer/polyserve
[web-component-tester]: https://github.com/Polymer/web-component-tester
npm package: @nomensa/nomensa-pfe-header
Description: Pfe element for PatternFly Elements
Author: Kate Leigh
Latest version: 1.0.4

# PatternFly Element | Pfe Element

## Dependencies

Make sure you have [Polyserve][polyserve] and [Web Component Tester][web-component-tester] installed.

    npm install -g polyserve web-component-tester

## Dev

    npm start

## Test

    npm run test

## Build

    npm run build

## Demo

Run `npm start` and Polyserve will start a server and open your default browser to the demo page of the element.

## Code style

Pfe (and all PatternFly Elements) use [Prettier][prettier] to auto-format JS and JSON.  The style rules get applied when you commit a change.  If you choose to, you can [integrate your editor][prettier-ed] with Prettier to have the style rules applied on every save.

[prettier]: https://github.com/prettier/prettier/
[prettier-ed]: https://github.com/prettier/prettier/#editor-integration
[polyserve]: https://github.com/Polymer/polyserve
[web-component-tester]: https://github.com/Polymer/web-component-tester
npm package: @nomensa/nomensa-pfe-hero
Description: Pfe element for PatternFly Elements
Author: Kate Leigh
Latest version: 1.0.4

# PatternFly Element | Pfe Element

## Dependencies

Make sure you have [Polyserve][polyserve] and [Web Component Tester][web-component-tester] installed.

    npm install -g polyserve web-component-tester

## Dev

    npm start

## Test

    npm run test

## Build

    npm run build

## Demo

Run `npm start` and Polyserve will start a server and open your default browser to the demo page of the element.

## Code style

Pfe (and all PatternFly Elements) use [Prettier][prettier] to auto-format JS and JSON.  The style rules get applied when you commit a change.  If you choose to, you can [integrate your editor][prettier-ed] with Prettier to have the style rules applied on every save.

[prettier]: https://github.com/prettier/prettier/
[prettier-ed]: https://github.com/prettier/prettier/#editor-integration
[polyserve]: https://github.com/Polymer/polyserve
[web-component-tester]: https://github.com/Polymer/web-component-tester
npm package: @nomensa/nomensa-pfe-image
Description: Responsive image component
Author: Kate Leigh
Latest version: 1.0.5

# PatternFly Element | Pfe Element

## Dependencies

Make sure you have [Polyserve][polyserve] and [Web Component Tester][web-component-tester] installed.

    npm install -g polyserve web-component-tester

## Dev

    npm start

## Test

    npm run test

## Build

    npm run build

## Demo

Run `npm start` and Polyserve will start a server and open your default browser to the demo page of the element.

## Code style

Pfe (and all PatternFly Elements) use [Prettier][prettier] to auto-format JS and JSON.  The style rules get applied when you commit a change.  If you choose to, you can [integrate your editor][prettier-ed] with Prettier to have the style rules applied on every save.

[prettier]: https://github.com/prettier/prettier/
[prettier-ed]: https://github.com/prettier/prettier/#editor-integration
[polyserve]: https://github.com/Polymer/polyserve
[web-component-tester]: https://github.com/Polymer/web-component-tester
npm package: @nomensa/nomensa-pfe-inline-links
Description: Pfe element for PatternFly Elements
Author: Kate Leigh
Latest version: 1.0.1

# PatternFly Element | Pfe Element

## Dependencies

Make sure you have [Polyserve][polyserve] and [Web Component Tester][web-component-tester] installed.

    npm install -g polyserve web-component-tester

## Dev

    npm start

## Test

    npm run test

## Build

    npm run build

## Demo

Run `npm start` and Polyserve will start a server and open your default browser to the demo page of the element.

## Code style

Pfe (and all PatternFly Elements) use [Prettier][prettier] to auto-format JS and JSON.  The style rules get applied when you commit a change.  If you choose to, you can [integrate your editor][prettier-ed] with Prettier to have the style rules applied on every save.

[prettier]: https://github.com/prettier/prettier/
[prettier-ed]: https://github.com/prettier/prettier/#editor-integration
[polyserve]: https://github.com/Polymer/polyserve
[web-component-tester]: https://github.com/Polymer/web-component-tester
npm package: @nomensa/nomensa-pfe-link
Description: Pfe element for PatternFly Elements
Author: Kate Leigh
Latest version: 1.0.6

# PatternFly Element | Pfe Element

## Dependencies

Make sure you have [Polyserve][polyserve] and [Web Component Tester][web-component-tester] installed.

    npm install -g polyserve web-component-tester

## Dev

    npm start

## Test

    npm run test

## Build

    npm run build

## Demo

Run `npm start` and Polyserve will start a server and open your default browser to the demo page of the element.

## Code style

Pfe (and all PatternFly Elements) use [Prettier][prettier] to auto-format JS and JSON.  The style rules get applied when you commit a change.  If you choose to, you can [integrate your editor][prettier-ed] with Prettier to have the style rules applied on every save.

[prettier]: https://github.com/prettier/prettier/
[prettier-ed]: https://github.com/prettier/prettier/#editor-integration
[polyserve]: https://github.com/Polymer/polyserve
[web-component-tester]: https://github.com/Polymer/web-component-tester
npm package: @nomensa/nomensa-pfe-logo
Description: Pfe element for PatternFly Elements
Author: Kate Leigh
Latest version: 1.0.1

# PatternFly Element | Pfe Element

## Dependencies

Make sure you have [Polyserve][polyserve] and [Web Component Tester][web-component-tester] installed.

    npm install -g polyserve web-component-tester

## Dev

    npm start

## Test

    npm run test

## Build

    npm run build

## Demo

Run `npm start` and Polyserve will start a server and open your default browser to the demo page of the element.

## Code style

Pfe (and all PatternFly Elements) use [Prettier][prettier] to auto-format JS and JSON.  The style rules get applied when you commit a change.  If you choose to, you can [integrate your editor][prettier-ed] with Prettier to have the style rules applied on every save.

[prettier]: https://github.com/prettier/prettier/
[prettier-ed]: https://github.com/prettier/prettier/#editor-integration
[polyserve]: https://github.com/Polymer/polyserve
[web-component-tester]: https://github.com/Polymer/web-component-tester
npm package: @nomensa/nomensa-pfe-nav
Description: Pfe element for PatternFly Elements
Author: Kate Leigh
Latest version: 1.0.5

# PatternFly Element | Pfe Element

## Dependencies

Make sure you have [Polyserve][polyserve] and [Web Component Tester][web-component-tester] installed.

    npm install -g polyserve web-component-tester

## Dev

    npm start

## Test

    npm run test

## Build

    npm run build

## Demo

Run `npm start` and Polyserve will start a server and open your default browser to the demo page of the element.

## Code style

Pfe (and all PatternFly Elements) use [Prettier][prettier] to auto-format JS and JSON.  The style rules get applied when you commit a change.  If you choose to, you can [integrate your editor][prettier-ed] with Prettier to have the style rules applied on every save.

[prettier]: https://github.com/prettier/prettier/
[prettier-ed]: https://github.com/prettier/prettier/#editor-integration
[polyserve]: https://github.com/Polymer/polyserve
[web-component-tester]: https://github.com/Polymer/web-component-tester
npm package: @nomensa/nomensa-pfe-search
Description: Pfe element for PatternFly Elements
Author: Kate Leigh
Latest version: 1.0.4

# PatternFly Element | Pfe Element

## Dependencies

Make sure you have [Polyserve][polyserve] and [Web Component Tester][web-component-tester] installed.

    npm install -g polyserve web-component-tester

## Dev

    npm start

## Test

    npm run test

## Build

    npm run build

## Demo

Run `npm start` and Polyserve will start a server and open your default browser to the demo page of the element.

## Code style

Pfe (and all PatternFly Elements) use [Prettier][prettier] to auto-format JS and JSON.  The style rules get applied when you commit a change.  If you choose to, you can [integrate your editor][prettier-ed] with Prettier to have the style rules applied on every save.

[prettier]: https://github.com/prettier/prettier/
[prettier-ed]: https://github.com/prettier/prettier/#editor-integration
[polyserve]: https://github.com/Polymer/polyserve
[web-component-tester]: https://github.com/Polymer/web-component-tester
npm package: @nomensa/nomensa-pfe-text
Description: Pfe element for PatternFly Elements
Author: Kate Leigh
Latest version: 1.0.4

# PatternFly Element | Pfe Element

## Dependencies

Make sure you have [Polyserve][polyserve] and [Web Component Tester][web-component-tester] installed.

    npm install -g polyserve web-component-tester

## Dev

    npm start

## Test

    npm run test

## Build

    npm run build

## Demo

Run `npm start` and Polyserve will start a server and open your default browser to the demo page of the element.

## Code style

Pfe (and all PatternFly Elements) use [Prettier][prettier] to auto-format JS and JSON.  The style rules get applied when you commit a change.  If you choose to, you can [integrate your editor][prettier-ed] with Prettier to have the style rules applied on every save.

[prettier]: https://github.com/prettier/prettier/
[prettier-ed]: https://github.com/prettier/prettier/#editor-integration
[polyserve]: https://github.com/Polymer/polyserve
[web-component-tester]: https://github.com/Polymer/web-component-tester
npm package: @nomensa/nomensa-pfe-video
Description: Pfe element for PatternFly Elements
Author: Kate Leigh
Latest version: 1.0.2

# PatternFly Element | Pfe Element

## Dependencies

Make sure you have [Polyserve][polyserve] and [Web Component Tester][web-component-tester] installed.

    npm install -g polyserve web-component-tester

## Dev

    npm start

## Test

    npm run test

## Build

    npm run build

## Demo

Run `npm start` and Polyserve will start a server and open your default browser to the demo page of the element.

## Code style

Pfe (and all PatternFly Elements) use [Prettier][prettier] to auto-format JS and JSON.  The style rules get applied when you commit a change.  If you choose to, you can [integrate your editor][prettier-ed] with Prettier to have the style rules applied on every save.

[prettier]: https://github.com/prettier/prettier/
[prettier-ed]: https://github.com/prettier/prettier/#editor-integration
[polyserve]: https://github.com/Polymer/polyserve
[web-component-tester]: https://github.com/Polymer/web-component-tester
npm package: @nomensa/pfe-card
Description: Cards for PatternFly Elements
Latest version: 1.0.16

PFElements Card Element

## Usage

```html
<pfe-card>
  <h2 slot="header">RH Card</h2>
  This is the pfe-card body.
  <div slot="footer">Text in footer</div>
</pfe-card>
```

## Slots

### header
If this slot is used, we expect a heading level tag (h1, h2, h3, h4, h5, h6) to
be used here.

### Default slot (body)
Any content that is not designated for the header or footer slot, will go to this slot.

### footer
Use this slot for anything that you want in the footer of the card.

## Test

    npm run test

## Build

    npm run build

## Demo

From the PFElements root directory, run:

    npm start

## Code style

Card (and all PFElements) use [Prettier][prettier] to auto-format JS and JSON. The style rules get applied when you commit a change. If you choose to, you can [integrate your editor][prettier-ed] with Prettier to have the style rules applied on every save.

[prettier]: https://github.com/prettier/prettier/
[prettier-ed]: https://prettier.io/docs/en/editors.html
[web-component-tester]: https://github.com/Polymer/web-component-tester
npm package: @nomensa/pfe-icon
Description: Icon element for PatternFly Elements
Latest version: 1.0.0-prerelease.14

# WIP 🐣: PFElements Icon Element

## Usage

```html
<pfe-icon icon="pfe-icon-server"></pfe-icon>
```

## Attributes

### icon (observed)

The name of the icon that you want to use. If the value of this attribute changes, the new icon will show up in the UI.

### data-size

Controls the size of the icon. The options for size are:
- `2x`
- `3x`
- `4x`
- `small`
- `medium`
- `large`

```html
<pfe-icon icon="pfe-icon-server" data-size="2x"></pfe-icon>
```

### data-block

By default, `pfe-icon` is set to `display: inline-block`. The `data-block` attribute sets this element to `display: block`.

```html
<pfe-icon icon="pfe-icon-server" data-block></pfe-icon>
```

### data-bg

Sets the border radius of the element to a circle (`border-radius: 50%`).

```html
<pfe-icon icon="pfe-icon-server" data-bg></pfe-icon>
```

Another option for `data-bg` is to set the attribute equal to `transparent`. This makes the background transparent.

```html
<pfe-icon icon="pfe-icon-server" data-bg="transparent"></pfe-icon>
```

## Test

    npm run test

## Build

    npm run build

## Demo

From the PFElements root directory, run:

    npm start

## Code style

Icon (and all PFElements) use [Prettier][prettier] to auto-format JS and JSON. The style rules get applied when you commit a change. If you choose to, you can [integrate your editor][prettier-ed] with Prettier to have the style rules applied on every save.

[prettier]: https://github.com/prettier/prettier/
[prettier-ed]: https://prettier.io/docs/en/editors.html
[web-component-tester]: https://github.com/Polymer/web-component-tester
npm package: @nomensa/pfe-icon-panel
Description: Icon panel for PatternFly Elements
Latest version: 1.0.1

# WIP 🐣: PFElements Icon Panel Element

## Usage

```html
<pfe-icon-panel icon="pfe-icon-server">
  <h3 slot="header">This is pfe-icon-panel</h3>
  Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.
  <pfe-cta slot="footer">
    <a href="https://pfelements.github.io">Learn more about PFElements</a>
  </pfe-cta>
</pfe-icon-panel>
```

## Slots

### header
The header of the icon panel

### Default slot (body)
Any content that is not designated for the header or footer slot, will go to this slot.

### footer
Use this slot for anything that you want in the footer of the icon panel.

## Attributes

### icon (observed)

The name of the icon that you want to use. If the value of this attribute changes, the new icon will show up in the UI.

## Test

    npm run test

## Build

    npm run build

## Demo

From the PFElements root directory, run:

    npm start

## Code style

Icon Panel (and all PFElements) use [Prettier][prettier] to auto-format JS and JSON. The style rules get applied when you commit a change. If you choose to, you can [integrate your editor][prettier-ed] with Prettier to have the style rules applied on every save.

[prettier]: https://github.com/prettier/prettier/
[prettier-ed]: https://prettier.io/docs/en/editors.html
[web-component-tester]: https://github.com/Polymer/web-component-tester
npm package: @nomensa/pfelement
Description: Base class for PatternFly Elements
Latest version: 1.0.0

# PFElement Element

This is the base element that all other PFElements should extend. It handles setting up a shadow root and applies Shady CSS if it is needed.

To create a new PFElement, use `npm run new` from the root of the PFElements repo. After answering a few questions, a new element will be generated for you by [generator-pfelement][generator].

Here is an example of a new element and how it extends the base PFElement.

```javascript
import PFElement from "../pfelement/pfelement.js";

class MyElement extends PFElement {
  // The HTML tag name for this element.  This will be passed into `customElements.define()`.
  static get tag() {
    return "my-element";
  }

  // The path to the element's SCSS file.  It is compiled to CSS at build time.
  get styleUrl() {
    return "my-element.scss";
  }

  // The path to the element's template.  This used at build time.
  get templateUrl() {
    return "my-element.html";
  }

  constructor() {
    // The call to super is first and contains a reference to the class itself.
    // This allows the base class to see any of MyElement's static properties.
    super(MyElement);

    // any other work to do during the constructor goes here
  }

  // connectedCallback runs when the element is placed into the DOM.  Note that
  // in dynamic apps, this _can_ happen more than once, for instance if an
  // element is moved from one part of the DOM tree to another.
  connectedCallback() {
    // super's connectedCallback goes first
    super.connectedCallback();

    // any other work to do during connectedCallback goes here
  }
}

PFElement.create(MyElement);
```

## Test

    npm run test

## Build

    npm run build

## Demo

From the PFElements root directory, run:

    npm start

## Code style

PFElement (and all PFElements) use [Prettier][prettier] to auto-format JS and JSON. The style rules get applied when you commit a change. If you choose to, you can [integrate your editor][prettier-ed] with Prettier to have the style rules applied on every save.

[prettier]: https://github.com/prettier/prettier/
[prettier-ed]: https://prettier.io/docs/en/editors.html
[web-component-tester]: https://github.com/Polymer/web-component-tester
[generator]: https://github.com/PFElements/generator-pfelement
npm package: @nomercy235/hsl-to-hex
Description: Convert HSL colors to RGB colors in hex format.
Author: Alexandru Florian Barascu
Latest version: 1.0.2

# hsl-to-hex
Convert HSL colors to RGB colors in hex format.
## Install
```sh
npm install --save @nomercy235/hsl-to-hex
```
## API
```
require('hsl-to-hex') => Function
hsl(hue, saturation, luminosity)` => String
```
## Example
```js
var hsl = require('hsl-to-hex')
var hue = 133
var saturation = 40
var luminosity = 60
var hex = hsl(hue, saturation, luminosity)
console.log(hex) // #70c282
```
## License
MIT
npm package: @nomercy235/weather-app
Description: A simple app which gives the weather for a location.
Author: Alexandru Florian Barascu
Latest version: 1.2.4

Weather App
=========

A simple weather app made in Node JS.

Uses the [Google geocode](https://developers.google.com/maps/documentation/geocoding/get-api-key) and [Open Weather](http://openweathermap.org/) APIs to retrive the location of an address and get the current weather for it. You will need to the keys from both of these APIs if you want to use this package.

If you want to use this as a script, create a file called `env.js` in the root directory which has the same structure as the provided example.

The same format must be provided if you use this as a package.

## Usage

    const weatherApp = require('@nomercy235/weather-app');

    // address: string
    // keys: { googleApiKey: string, forecastApiKey: string }
    // options: { type: 'weather' | 'forecast', limit: number }  
    weatherApp.getWeatherForAddress(address, keys, options)

## Tests

  TBA
  
## Contributing

In lieu of a formal style guide, take care to maintain the existing coding style. Add unit tests for any new or changed functionality (although there are none yet). Lint and test your code.

## LICENSE
MIT
npm package: @nometria-ai/claude-code
Description: Deploy any project to any cloud from Claude Code. MCP server + slash commands.
Author: Nometria
Latest version: 0.3.1

# @nometria-ai/claude-code

Deploy any project to any cloud directly from Claude Code.

## Install

### Option 1: Plugin (recommended)

```bash
# Install as a Claude Code plugin (includes MCP server + skills)
/plugin marketplace add nometria/claude-code-plugin
/plugin install nometria
```

### Option 2: MCP server

```bash
# Add MCP server to Claude Code
claude mcp add nometria -- npx -y @nometria-ai/claude-code

# If you use nvm/fnm/volta and the above fails, use:
claude mcp add nometria -- /bin/sh -c '. "${NVM_DIR:-$HOME/.nvm}/nvm.sh" 2>/dev/null; exec npx -y @nometria-ai/claude-code'
```

### Option 3: Slash commands only

```bash
# Generate slash commands + AI tool configs in your project
npx @nometria-ai/nom setup
```

## MCP Tools

| Tool | Description |
|------|-------------|
| `nometria_login` | Authenticate with your API key |
| `nometria_init` | Create nometria.json config |
| `nometria_deploy` | Deploy to production |
| `nometria_preview` | Create staging preview (free, 2hr) |
| `nometria_status` | Check deployment status |
| `nometria_logs` | View deployment logs |
| `nometria_list_apps` | List all your apps |

## Slash Commands

After running `setup`, these are available in Claude Code:

- `/deploy` — Deploy to production
- `/preview` — Create staging preview
- `/status` — Check deployment status
- `/nometria-login` — Authenticate

## Quick Start

```
> Use nometria_login with key nometria_sk_...
> Use nometria_init to set up this project
> Use nometria_deploy to ship it
```

## Authentication

Get an API key at [nometria.com/settings/api-keys](https://nometria.com/settings/api-keys).

```bash
# Option 1: Set env var
export NOMETRIA_API_KEY=nometria_sk_...

# Option 2: Use the login tool
# Claude Code will call nometria_login for you
```

## Supported Platforms

AWS, Google Cloud, Azure, DigitalOcean, Hetzner, Vercel

## Also Available

- **CLI**: `npx @nometria-ai/nom deploy` — [npm](https://npmjs.com/package/@nometria-ai/nom)
- **VS Code**: Search "Nometria" in extensions
- **Cursor**: Auto-rules via `.cursor/rules/`

## License

MIT
npm package: @nometria-ai/nom
Description: Deploy any project to any cloud from your terminal. One command, zero config.
Author: Nometria
Latest version: 0.3.1

# nom

Deploy any project to any cloud from your terminal. One command, zero config.

```bash
npx @nometria-ai/nom deploy
```

## Quick Start

```bash
# 1. Authenticate
npx @nometria-ai/nom login

# 2. Set up your project
npx @nometria-ai/nom init

# 3. Deploy
npx @nometria-ai/nom deploy
```

## Commands

| Command | Description |
|---------|-------------|
| `nom login` | Authenticate with your API key |
| `nom init` | Create a `nometria.json` config file |
| `nom deploy` | Deploy to production |
| `nom preview` | Create a staging preview |
| `nom status` | Check deployment status |
| `nom logs` | View deployment logs |
| `nom logs -f` | Stream logs in real-time |
| `nom whoami` | Show current authenticated user |

## Configuration

`nom init` creates a `nometria.json` in your project root:

```json
{
  "name": "my-app",
  "framework": "vite",
  "platform": "aws",
  "region": "us-east-1",
  "instanceType": "4gb",
  "build": {
    "command": "npm run build",
    "output": "dist"
  },
  "env": {
    "DATABASE_URL": "@env:DATABASE_URL"
  },
  "ignore": []
}
```

### Fields

| Field | Description | Default |
|-------|-------------|---------|
| `name` | Project name (becomes `{name}.nometria.com`) | from package.json |
| `framework` | `vite`, `nextjs`, `remix`, `static`, `node` | auto-detected |
| `platform` | `aws`, `gcp`, `azure`, `digitalocean`, `hetzner`, `vercel` | `aws` |
| `region` | Cloud region | `us-east-1` |
| `instanceType` | `2gb`, `4gb`, `8gb`, `16gb` | `4gb` |
| `build.command` | Build command | auto-detected |
| `build.output` | Build output directory | auto-detected |
| `env` | Environment variables. Use `@env:VAR` to read from local env | `{}` |
| `ignore` | Extra patterns to exclude from upload | `[]` |

## Authentication

Get an API key at [nometria.com/settings/api-keys](https://nometria.com/settings/api-keys).

```bash
# Option 1: Login command (stores in ~/.nometria/credentials.json)
nom login

# Option 2: Environment variable
export NOMETRIA_API_KEY=nometria_sk_...
```

## Environment Variables

Use the `@env:` prefix in `nometria.json` to reference local environment variables. These are resolved at deploy time and never stored in the config file:

```json
{
  "env": {
    "DATABASE_URL": "@env:DATABASE_URL",
    "API_SECRET": "@env:MY_API_SECRET"
  }
}
```

## Supported Platforms

- **AWS** (EC2 + Route53)
- **Google Cloud** (Compute Engine)
- **Azure** (Virtual Machines)
- **DigitalOcean** (Droplets)
- **Hetzner** (Cloud Servers)
- **Vercel** (Serverless)

## Requirements

- Node.js 18+
- `tar` command (available by default on macOS/Linux/WSL)

## License

MIT
npm package: @nomi-gee/esbuild-plugin-postcss2
Description: Use postcss with esbuild
Author: Marton Lederer
Latest version: 0.1.3
Deprecated: false

# Looking for a maintainer!

Unfortunately I don't have time for this plugin. Please contact me if you'd like to take on this project.

# esbuild-plugin-postcss2

This plugin is an optimized, type-friendly version of [esbuild-plugin-postcss](https://github.com/deanc/esbuild-plugin-postcss). It supports CSS preprocessors and CSS modules.

## Install

```sh
yarn add -D esbuild-plugin-postcss2
```

or

```sh
npm i -D esbuild-plugin-postcss2
```

## Usage

Add the plugin to your esbuild plugins:

```js
const esbuild = require("esbuild");
const postCssPlugin = require("esbuild-plugin-postcss2");

esbuild.build({
  ...
  plugins: [
    postCssPlugin.default()
  ]
  ...
});
```

### PostCSS plugins

Add your desired PostCSS plugin to the plugins array:

```js
const autoprefixer = require("autoprefixer");

esbuild.build({
  ...
  plugins: [
    postCssPlugin.default({
      plugins: [autoprefixer]
    })
  ]
  ...
});
```

### CSS modules

PostCSS modules are enabled by default. You can pass in a config or disable it with the `modules` field:

```js
postCssPlugin.default({
  // pass in `postcss-modules` custom options
  // set to false to disable
  modules: {
    getJSON(cssFileName, json, outputFileName) {
      const path = require("path");
      const cssName = path.basename(cssFileName, ".css");
      const jsonFileName = path.resolve("./build/" + cssName + ".json");

      fs.writeFileSync(jsonFileName, JSON.stringify(json));
    }
  }
});
```

As per standard any file having `module` before the extension (ie `somefile.module.css`) will be treated as a module.
The option `fileIsModule` allows to override this behavior.

```js
postCssPlugin.default({
  // pass a custom `fileIsModule` option to tell whether a file should be treated as a module
  // in this example we want everything to be a module except file finishing with `global.css`
  fileIsModule: (filepath) => !filepath.endsWith(".global.css")
});
```

### Preprocessors

To use preprocessors (`sass`, `scss`, `stylus`, `less`), just add the desired preprocessor as a `devDependency`:

```sh
yarn add -D sass
```