open-index/open-npm huggingface dataset:
npm package: @flyke/svg-sprite-generator
Description: A SVG sprite file generator
Author: Huy Nguyen
Latest version: 0.0.7

# svg-sprite-generator

Unlike similar Gulp or Grunt tools, our SVG sprite generator is created for designers who are not fond of coding. This tool simply takes a list of SVG files and make a single sprite file using ```<symbol>``` elements. 

SVG sprite generator is a helpful for creating icon systems.

NOTICE: this is just a fork of https://github.com/frexy/svg-sprite-generator
because I needed an updated version of the required of cheerio package
to fix an npm audit issue. Whenever this issue is resolved: https://github.com/frexy/svg-sprite-generator/issues/10
you should use frexy/svg-sprite-generator instead of this one (flyke/svg-sprite-generator). 

## Installation

This program needs [Node.js](http://nodejs.org) to run. If Node already existed in your system, use ```npm``` to install the generator:

```
npm install -g svg-sprite-generator
```

## Usage

### From a directory 
Generate sprite from a directory of SVG files

```
svg-sprite-generate -d path/to/directory/of/svg/files -o path/to/sprite.svg
```

### From a list of SVG files
Or specify SVG files to generate from. File paths can be separated with a comma.

```
svg-sprite-generate -l path/to/file1.svg,path/to/file2.svg -o path/to/sprite.svg
```

### From a CSV file
Or use a CSV file. The first column contains symbol IDs, the second contains SVG file paths.

```csv
duo-alarm-clock, test/svg/duo-alarm-clock.svg
duo-bicycle, test/svg/duo-bicycle.svg
```
The command

```
svg-sprite-generate -c path/to/csv.csv -o path/to/sprite.svg
```

### From another sprite file

You can take another sprite file and generate a new one with some modification too.

```
svg-sprite-generate -s path/to/sprite.svg -l path/to/extra.svg,path/to/another-extra-one.svg -o new-sprite.svg
```
### About

SVG Sprite Generator is created by the folks at [SmartIcons](https://smarticons.co)

## License
MIT
npm package: @flykode/simplejs-format
Description: Simple JS Format Lib
Author: FlyKode
Latest version: 0.1.0

# simplejsformat
A simple JS Format Package for Study purposes


#Example

```javascript
'use strict';

const sjsformat = require('@flykode/simplejs-format');

let currency001 = new sjsformat.FkNumbers();

console.log(currency001.currencyFormat(1000));
```
npm package: @flynnodetraveler/env-config-loader
Description: A module dot-env that loads .env files and set it environment variables
Latest version: 1.0.0

# dot-env

A Node.js module that loads `.env` files and set it environment variables

## Installation

```bash
npm install dot-env
```

## Usage

### Basic Usage

```javascript
const { config } = require('dot-env');

// Load .env file and set environment variables
config();
```

### `config(options)`

Loads a `.env` file and set it environment variables

**Parameters:**

- `options` (Object): Configuration options
  - `path` (string): Path to `.env` file. Default: `'.env'`

**Returns:**

- `Promise<Object>`: Object containing:
  - `parsed`: Parsed environment variables

## Features

- ✅ Loads `.env` files and sets environment variables
- ✅ Parses environment variables from `.env` files

## Example .env File

```env
# Database configuration
DB_HOST=localhost
DB_PORT=5432
DB_NAME=myapp
DB_USER=admin
DB_PASSWORD=secret123

# API Keys
API_KEY=your-api-key-here
SECRET_KEY=your-secret-key

# Feature flags
ENABLE_FEATURE_X=true
ENABLE_FEATURE_Y=false
```

```json
{
  "parsed": {
    "DB_HOST": "localhost",
    "DB_PORT": "5432",
    ...
  }
}
```

## License


## License

[![License: MIT](https://img.shields.io/badge/License-MIT-blue.svg)](LICENSE)
npm package: @flynns-devstation/eslint-config
Description: ESlint config for flynns devstation
Author: Chris Helgert
Latest version: 1.1.0

# eslint-config

[![npm](https://img.shields.io/npm/v/@flynns-devstation/eslint-config.svg?style=for-the-badge)](https://www.npmjs.com/package/@flynns-devstation/eslint-config)
[![CircleCI](https://img.shields.io/circleci/build/github/FlynnsDevstation/eslint-config/master.svg?style=for-the-badge)](https://circleci.com/gh/FlynnsDevstation/eslint-config)

This package provides Flynns Devstation's .eslintrc as an extensible shared config.

## Features

- Supports TypeScript with `@typescript-eslint/eslint-plugin`
- Supports React and React Hooks
- Based on `eslint-config-airbnb-typescript`
- Works together with prettier

## Usage

1. Install config and peerDependencies

```bash
npm i -D @flynns-devstation/eslint-config \
  @typescript-eslint/eslint-plugin \
  eslint \
  eslint-plugin-import \
  eslint-plugin-jsx-a11y \
  eslint-plugin-react \
  eslint-plugin-react-hooks \
  typescript
```

or

```bash
yarn add -D @flynns-devstation/eslint-config \
  @typescript-eslint/eslint-plugin \
  eslint \
  eslint-plugin-import \
  eslint-plugin-jsx-a11y \
  eslint-plugin-react \
  eslint-plugin-react-hooks \
  typescript
```

2. Create eslint config

```js
// .eslintrc.js
module.exports = {
  extends: ['@flynns-devstation'],
}
```

3. Create a `lint` job in your package.json

```json
{
  "scripts": {
    "lint": "eslint --cache --ext .ts,.tsx ./src"
  }
}
```

4. Run `npm run lint` or `yarn lint` to lint all your `ts` and `tsx` files

## Contributing

1. Fork it
2. Create your feature branch
3. Commit your changes
4. Push to the branch
5. Create new Pull Request

## LICENSE

Copyright (c) 2019-present. See [License](./LICENSE) for details.
npm package: @flynns-devstation/prettier-config
Description: Shareable config for prettier
Author: Chris Helgert
Latest version: 1.0.2

# prettier-config

[![npm](https://img.shields.io/npm/v/@flynns-devstation/prettier-config.svg?style=for-the-badge)](https://www.npmjs.com/package/@flynns-devstation/prettier-config)
[![CircleCI](https://img.shields.io/circleci/build/github/FlynnsDevstation/prettier-config/master.svg?style=for-the-badge)](https://circleci.com/gh/FlynnsDevstation/prettier-config)

This package provides Flynns Devstation's .prettierrc as an extensible shared config.

## Features

- Trailing comma for `es5`
- No semicolon
- Single quotes

## Usage

### As npm script

1. Install config and peerDependencies

```bash
npm i -D @flynns-devstation/prettier-config prettier
```

or

```bash
yarn add -D @flynns-devstation/prettier-config prettier
```

2. Create prettier config

```js
// .prettierrc.js
module.exports = require('@flynns-devstation/prettier-config')
```

3. Create a `format` job in your package.json

```json
{
  "scripts": {
    "format": "prettier --write '**/*.{js,ts,md}'"
  }
}
```

4. Run `npm run format` or `yarn format` to prettier your `JavaScript`, `TypeScript` and `Markdown` files

### As commit hook

1. Install config, peerDependencies and devDependencies for commit hook

```bash
yarn add -D @flynns-devstation/prettier-config prettier husky lint-staged
```

2. Create prettier config

```js
// .prettierrc.js
module.exports = require('@flynns-devstation/prettier-config')
```

3. Create the commit hook in `package.json`

```json
{
  "husky": {
    "hooks": {
      "pre-commit": "lint-staged"
    }
  },
  "lint-staged": {
    "*{gql,js,jsx,json,md,ts,tsx,yml}": "prettier --write"
  }
}
```

4. Now on every commit the files will be automatically beatified with `prettier`

## Contributing

1. Fork it
2. Create your feature branch
3. Commit your changes
4. Push to the branch
5. Create new Pull Request

## LICENSE

Copyright (c) 2019-present. See [License](./LICENSE) for details.
npm package: @flynnt/create-odc-project
Description: A Node command line tool for scaffolding common ODC projects
Author: Ted Flynn
Latest version: 1.6.2
Deprecated: Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.

# create-odc-project
A scaffolding tool for common One Design projects. This tool does three main things:
- It copies standard starter files (templates, project config, dependency config) into a project directory.
- It can initialize a new project directory as a git repository.
- It can download node package dependencies.

The tool is meant to be extensible and can support the addition of multiple project bases. However, there is currently only one project base configured, and that is for a [Craft 4 project](#craft-cms-javascript) using Vite and Tailwind.

## Quick Start
To use the installation wizard (recommended):

`npx @flynnt/create-odc-project`

## Command Line Usage with Options
`npx create-odc-project [projectTemplate<String>] [-g|--git <Boolean>] [-i|--install <Boolean>]`

Installation with default options:

`npx create-odc-project [-y|--yes]`

### Option Reference

`[template<String>]`: The project template type. Defaults to `craftcms-js`.

`-g|--git`: Whether or not to intialize a git repository in the current working directory. Default: `true`.

`-i|--install`: Whether or not to install node package dependencies in the current working directory. Default: `true`.

`-y|--yes`: Skips prompts and accepts the default option values.

## Project Templates
### Craft CMS (JavaScript)
In the context of a Craft 4 project, the tool is meant to augment the base install from `composer create-project craftcms/craft` with our own organizational tools and preferences. This template type is meant to work in conjunction with a Craft installation and wouldn't be very useful on its own. In this context, the tool is usually called from a parent script, so you don't really have to worry about running it manually.

Nevertheless, it's certainly possible to manually install Craft 4 and then run this tool to bring that base install in line with our preferences. Note that the Craft project template presumes that the Craft application code is scoped to an `/app` directory.
npm package: @flynnt/extend-craftcms-project
Description: A Node command line tool for scaffolding common Craft CMS projects
Author: Ted Flynn
Latest version: 1.4.1

# extend-craftcms-project

A scaffolding tool for common Craft CMS projects. This tool does three main things:

- It copies standard starter files (templates, project config, dependency config) into a project directory.
- It can initialize a new project directory as a git repository.
- It can download node package dependencies.

The tool is meant to be extensible and can support the addition of multiple project bases. However, there is currently
only one project base configured, and that is for a [Craft 5 project](#craft-cms-javascript) using Vite and Tailwind.

## Quick Start

To use the installation wizard (recommended):

`npx @flynnt/extend-craftcms-project`

## Command Line Usage with Options

`npx extend-craftcms-project [projectTemplate<String>] [-g|--git <Boolean>] [-i|--install <Boolean>]`

Installation with default options:

`npx extend-craftcms-project [-y|--yes]`

### Option Reference

`[template<String>]`: The project template type. Defaults to `craftcms-js`.

`-g|--git`: Whether or not to intialize a git repository in the current working directory. Default: `true`.

`-i|--install`: Whether or not to install node package dependencies in the current working directory. Default: `true`.

`-y|--yes`: Skips prompts and accepts the default option values.

## Project Templates

### Craft CMS (JavaScript)

In the context of a Craft 5 project, the tool is meant to augment the base install from
`composer create-project craftcms/craft` with our own organizational tools and preferences. This template type is meant
to work in conjunction with a Craft installation and wouldn't be very useful on its own. In this context, the tool is
usually called from a parent script, so you don't really have to worry about running it manually.

Nevertheless, it's certainly possible to manually install Craft 5 and then run this tool to bring that base install in
line with our preferences. Note that the Craft project template presumes that the Craft application code is scoped to an
`/app` directory.