open-index/open-npm huggingface dataset:
npm package: @fxhacker/get_date
Description: Lets you easily obtain and parse current date and time info
Latest version: 2.6.0

Get_Date is designed to make displaying the current date and time easier for your projects.

Require Package:
const now = require('/fxhacker/get_date')


If the current date and time is Thu Feb 14 2019 18:03:27 GMT-0700 you are able to output the following:

now.getTime => 06:03:27

now.getMilitaryTime => 18:03:27

now.getHours => 18

now.getMinutes => 03

now.getSeconds => 27

now.getDayOfWeek = > Thu

now.getDayOfWeekFull = > Thursday

now.getDayNumber => 14

now.getMonth => Feb

now.getMonthFull => February

now.getYear => 2019

now.getTimezone => GMT-0700
npm package: @fxhash/client
Description: Medium-level APIs to instanciate low-level @fxhash/core modules easily.
Author: fxhash
Latest version: 0.0.4

# `@fxhash/client-plugnplay`

A plug'n'play client interface to build applications with fxhash. This packages handles everything related to wallets & authentication and provides very high level functions for building applications on top of fxhash. This client is built on top of `@fxhash/client-basic`

## Usage

Installation

```sh
pnpm add @fxhash/client-plugnplay
```

```ts
// by default, nothing will be enabled
const client = clientBasic({
  metadata: {...}
})

// different wallet options are opt-in, in this case we add window &
const client = clientPlugnPlay({
  metadata: {...},
  wallets: {
    window: {...},  // must provide appropriate config
    web3auth: true, // email/oauth wallets
  },
})

const client = clientPlugnPlay() // with everything enabled

const client = clientPlugnPlay({
  wallets: {
    window: {
      evm: {
        config: wagmiConfig, // custom wagmi config
      },
      tezos: true, // default tezos config
    },
    web3auth: true, // email/oauth wallets
  },
})
```
npm package: @fxhash/client-react
Description: A react wrapper on @fxhash/client-plugnplay, implementing React providers & hooks for ease-of-use.
Author: fxhash
Latest version: 0.0.5

# `@fxhash/client-plugnplay-react`

This package wraps `@fxhash/client-plugnplay` so that it can easily be used in a React application.
npm package: @fxhash/config
Description: This contains all variables used within all modules of fx(package)
Author: fxhash
Latest version: 0.0.14

# @fxhash/config

This contains all variables used within all modules of fx(package)

## Installation

```
pnpm add @fxhash/config
```

## Usage

For you application you usually want to use the config like this:

```ts
import { config } from "@fxhash/config"
```

This singleton will expose variables for testnet/mainnet based on the `FXHASH_ENV` .env variable.

- Set `FXHASH_ENV=dev` to expose the config for testnet/dev environments
- Set `FXHASH_ENV=prd` or `FXHASH_ENV=production` to expose the config for mainnet/production environments

> Note: If the `@fxhash/config` package is used on the client side you also have to set the `NEXT_PUBLIC_FXHASH_ENV` or `REACT_APP_FXHASH_ENV` environment variable.

### Local development

Additional to the testnet and mainnet specific configuration there is the 3rd option for `local` development. This option is designed to be used within the fxhash monorepository. You can use it by setting the `FXHASH_ENV=local` environment variable. Since all services are dockerised there is an additional `localDocker` configuration. This configuration is automatically used when the `@fxhash/config` package is used inside a docker container and the `FXHASH_ENV` is set to `local`. The `localDocker` configuration basically just replaces all "localhost" urls with "host.docker.internal".

- Set `FXHASH_ENV=local` to expose the config for local development within the fxhash monorepository
npm package: @fxhash/eth
Description: 1. Clone repository
Latest version: 0.0.4

# FXHASH EVM SDK

## Setup

1. Clone repository

```
git clone git@github.com:fxhash/fxhash-evm-contracts.git
```

2. Deploy contracts from the `contracts` folder

```
npm run deploy
```

3. Create `.env` file in `sdk`` root directory

```
CONTRACTS_PATH=
PROVIDER_URL=
PROJECT_FACTORY_ADDRESS=
SIGNER_PK=
```

3. Install dependencies

```
npm i
```
npm package: @fxhash/gql-client
Description: The gql-client provides a simple GraphQL client which can be used with `@fxhash/gql` for running typed operations. The client works on front-ends and back-ends, although using a different package for front-end application would be best as this one doesn't
Author: fxhash
Latest version: 0.0.5

# `@fxhash/gql-client`

The gql-client provides a simple GraphQL client which can be used with `@fxhash/gql` for running typed operations. The client works on front-ends and back-ends, although using a different package for front-end application would be best as this one doesn't come with the best-in-class toolkit for front-end applications.

This package wraps [`@urql/core`](https://www.npmjs.com/package/@urql/core) by providing some default config working well with our stack.

> **Note**
>
> - The client will automatically add the `x-hasura-admin-secret` http header if the env variable `HASURA_ADMIN_SECRET` is defined.
> - The client will point to the hasura api scoped to the environment in which it's executed, based on `FXHASH_ENV` env variable (it uses the generic `@fxhash/config` package for such purpose)

## Usage

Install

```sh
pnpm add -E @fxhash/gql-client
```

Usage

```ts
import { gqlClient } from "@fxhash/gql-client"

// making a query
const { data, error } = await gqlClient.query(...)
```

## Client instanciation

If needed, instanciating a client with custom options is available. The client will not automatically add the `x-hasura-admin-secret` header, it must be passed with the `hasuraAdminSecret` option.

```ts
import { createGqlClient } from "@fxhash/gql-client"

const client = createGqlClient({
  //... custom options here
})
```
npm package: @fxhash/params
Description: `@fxhash/params` contains all code related to fx(params) feature
Author: fxhash
Latest version: 0.0.13

# fx(params)

`@fxhash/params` contains all code related to fx(params) feature

## Installation

`yarn add @fxhash/params react react-dom zod`

## Usage

```
import { BaseButton, BaseInput } from "@fxhash/params/BaseInput"
```
npm package: @fxhash/project-sdk
Description: The `@fxhash/project-sdk` is the library to create generatives artworks on fx(hash).
Author: fxhash
Latest version: 0.0.17

# @fxhash/project-sdk

The `@fxhash/project-sdk` is the library to create generatives artworks on fx(hash).

This packages is intended to be used in the browser and therefore exposes a IIFE (Immediately Invoked Function Expression) that exposes the `$fx` API on the window.

## DOCS

You can find the official documentation at [https://docs.fxhash.xyz](https://docs.fxhash.xyz).
npm package: @fxhash/sdk
Description: Bundle of all the fxhash low & medium level packages exported as one.
Author: fxhash
Latest version: 0.0.3

# `@fxhash/client-plugnplay`

A plug'n'play client interface to build applications with fxhash. This packages handles everything related to wallets & authentication and provides very high level functions for building applications on top of fxhash. This client is built on top of `@fxhash/client-basic`

## Usage

Installation

```sh
pnpm add @fxhash/client-plugnplay
```

```ts
// by default, nothing will be enabled
const client = clientBasic({
  metadata: {...}
})

// different wallet options are opt-in, in this case we add window &
const client = clientPlugnPlay({
  metadata: {...},
  wallets: {
    window: {...},  // must provide appropriate config
    web3auth: true, // email/oauth wallets
  },
})

const client = clientPlugnPlay() // with everything enabled

const client = clientPlugnPlay({
  wallets: {
    window: {
      evm: {
        config: wagmiConfig, // custom wagmi config
      },
      tezos: true, // default tezos config
    },
    web3auth: true, // email/oauth wallets
  },
})
```
npm package: @fxhash/shared
Description: @fxhash/shared is a TypeScript package designed to provide a flexible and reusable set of abstractions for interacting with various blockchain networks.
Author: fxhash
Latest version: 0.0.6

# @fxhash/shared

@fxhash/shared is a TypeScript package designed to provide a flexible and reusable set of abstractions for interacting with various blockchain networks.

## Installation

```
pnpm add -E @fxhash/shared
```
npm package: @fxhash/tez
Description: `@fxhash/tez` contains all code related to the Tezos blockchain.
Author: fxhash
Latest version: 0.0.3

# @fxhash/tez

`@fxhash/tez` contains all code related to the Tezos blockchain.

## Installation

```
pnpm add react react-dom onchfs @airgap/beacon-sdk @fxhash/config @fxhash/gql @taquito/beacon-wallet @taquito/taquito @taquito/signer
```
npm package: @fxhxyz/eslint-config
Description: My eslint config for web/node dev
Author: fxhxyz4
Latest version: 1.0.8

### @fxhxyz/prettier-config

#

### how to use?
+ ***npm***
```
npm install @fxhxyz/eslint-config -D
```

+ ***yarn***
```
yarn add @fxhxyz/eslint-config -D
```

+ ***pnpm***
```
pnpm add @fxhxyz/eslint-config -D
```

+ ***usage commonjs***
```js
// .eslintrc.cjs
module.exports = {
  extends: ["@fxhxyz/eslint-config/nodejs.js"]
};

// nodejs.js
// nodets.js
// webjs.js
// webts.js


// package.json
"scripts": {
    "lint": "eslint ."
}
```
npm package: @fxhxyz/prettier-config
Description: My professional prettier config
Author: fxhxyz4
Latest version: 2.0.8

### @fxhxyz/prettier-config

#

### how to use?
+ ***npm***
```
npm install @fxhxyz/prettier-config -D
```

+ ***yarn***
```
yarn add @fxhxyz/prettier-config -D
```

+ ***pnpm***
```
pnpm add @fxhxyz/prettier-config -D
```

+ ***usage commonjs***
```js
// .prettierrc.cjs
const config = require("@fxhxyz/prettier-config").default;
module.exports = config;


// package.json
"scripts": {
    "format": "prettier --write ."
}
```

+ ***usage es6***
```js
// .prettierrc.mjs/.js
import config from "@fxhxyz/prettier-config";
export { config };

// package.json
"scripts": {
    "format": "prettier --write ."
}
```


#

### copying prettierignore & editorconfig from node_modules
```
# linux/mac
cp node_modules/@fxhxyz/prettier-config/.prettierignore .prettierignore &&
cp node_modules/@fxhxyz/prettier-config/.editorconfig .editorconfig

# win
copy node_modules/@fxhxyz/prettier-config/.prettierignore .prettierignore &&
copy node_modules/@fxhxyz/prettier-config/.editorconfig .editorconfig
```
npm package: @fxi/el
Description: Quick DOM elements creation in js.
Author: unepgrid.ch
Latest version: 1.0.1


# ElementCreator

## Overview
ElementCreator is a JavaScript module designed to simplify the creation and management of DOM and SVG elements. It provides an intuitive API for creating elements, setting properties, attaching event listeners, and handling asynchronous content.

## Features
- Create HTML and SVG elements with ease.
- Manage attributes, classes, and styles.
- Attach event listeners in a structured way.
- Support for asynchronous content.
- Automatic cleanup of event listeners for removed elements.

## Usage
First, import the module:
```javascript
import { el, svg } from 'path/to/ElementCreator';
```

### Creating an HTML Element
```javascript
const div = el('div', { class: 'my-class' }, 'Hello, World!');
```

### Creating an SVG Element
```javascript
const circle = svg('circle', { cx: 20, cy: 20, r: 10 });
```

### Attaching Event Listeners
```javascript
const button = el('button', { on: ['click', () => alert('Clicked!')] });
```

### Asynchronous Content
```javascript
const asyncDiv = el('div', fetchSomeData().then(data => data.text()));
```

## License
This project is licensed under the MIT license.

## Contributions
Contributions are welcome. Please submit a pull request or open an issue for discussion.

---

ElementCreator - Simplifying DOM Manipulation
npm package: @fxi/geotickgen
Description: Lat/Long ticks on mapbox-gl / maplibre maps
Author: @fxi
Latest version: 0.0.9

# GeoTickGen

Lat/Long ticks generator for mapbox-gl / maplibre maps.

![GeoTickGen Demo Image](./img/demo.jpg) 

## Installation

There are two main methods to include `GeoTickGen` in your project:

### 1. Directly from a CDN:

```javascript
import { GeoTickGen } from "https://cdn.jsdelivr.net/npm/@fxi/geotickgen/+esm";
```

### 2. Using npm:

First, install the package:

```bash
npm install @fxi/geotickgen
```

Then, import in your project:

```javascript
import { GeoTickGen } from "@fxi/geotickgen";
```

## Usage

After importing, you can easily use `GeoTickGen` to generate Lat/Long ticks on your mapbox-gl or maplibre maps:

```javascript
const map = new mapboxgl.Map({
  // ... your map initialization here
});

const tickGen = new GeoTickGen(map, {
  // ... your optional configurations here
});
```

```css
.gtg-container {
  position: absolute;
  top: 0;
  left: 0;
  width: 100%;
  height: 100%;
  pointer-events: none;
}

.gtg-outline {
  stroke: #fff;
  fill: #000;
  font-family: monospace;
  font-size: 12px; /*should match configuration*/
  paint-order: stroke;
  stroke-width: 3px;
  stroke-linecap: round;
  stroke-linejoin: round;
}
```



## Configuration

Default options:

```javascript
{
  ticks: {
    sizeMinor: 10, // tick width
    sizeMajor: 20, // major tick width
    nStepMinor: 50, // number of step
    nStepMajor: 10, // major step each n
    enableLat: true, // show latitudes 
    enableLng: true, // show longitudes
    fontSize: 12, // for compute label position. Should match CSS
    offsetLabel: 4, // distance tick-label
    offsets: { // offsets of ticks bars
      lat: {
        top: 0,
        right: 0,
        bottom: 0,
        left: 0,
      },
      lng: {
        top: 0,
        right: 0,
        bottom: 0,
        left: 0,
      },
    },
  },
};
```

You can override these options by passing in your own configuration object when creating an instance of `GeoTickGen`.

## Issues & Contributions

If you encounter any issues or would like to contribute, please open an issue or a pull request on the [GitHub repository](https://github.com/fxi/geotickgen).

## License

MIT
npm package: @fxi/shiny-cluster
Description: Launch a Shiny app in multiple workers using node js
Author: F.Moser
Latest version: 0.0.8

# shinyCluster

`shinyCluster` is a simple Node.js module for launching a single R shiny application in a cluster of workers and keep track of sessions.

This is an experimental project. Please send me a feedback if you find this script useful.

# Other ways

* For production: use the official shiny-server or [shiny-server pro](https://www.rstudio.com/products/shiny-server-pro/).
* Load balancing: [A Shiny-app Serves as Shiny-server Load Balancer](http://withr.me/a-shiny-app-serves-as-shiny-server-load-balancer/)


# Usage 

## Prerequisite

* [nodejs + npm](https://nodejs.org/download/)
* [R](http://www.r-project.org/)
* [R package shiny](https://cran.r-project.org/web/packages/shiny/index.html)
* [shinyCluster](https://github.com/fxi/shinyCluster)


## Install

```{sh}
npm install @fxi/shiny-cluster --save
```

## Example

### Launch the default app

```{js}
var shinyCluster= require('@fxi/shiny-cluster');

/**
 * Launch a simple shiny app ( located in `./example` ),
 * using 3 workers and
 * listen on port 3456
 */
shinyCluster.run({
  path : "./example/app.R" // path to directory of shiny app or app.R file
  concurency : 3,
  port : 3456
});

```

### Launch your app

```{js}
var shinyCluster= require('@fxi/shiny-cluster');

/**
 * Launch your shiny app
 * located here `/home/john/myShinyApp/app.R`,
 * using 10 workers and
 * listen on port 3434
 */
shinyCluster.run({
  path : '/home/john/myShinyApp' ,
  concurency : 10,
  port : 3434
});

```

## Contribution

yes please !

# Change logs

0.0.6 -> 0.0.8
 - wait on shiny app to be ready using stderr output (not really clean)
 - setup config: timeoutConnect, timeoutListen, nTry
 - set option for host

0.0.5 -> 0.0.6
 
 - wait on shiny port to be available using net.connect
 - better error handling

0.0.2 -> 0.0.5

 - paths issues
 - better example

0.0.1 -> 0.0.2 

 - build a node module
 - use sticky-cluster
 - simplify everything
npm package: @fxjs-lerna/db-driver
Description: Fibjs Db Driver
Author: Richard
Latest version: 0.0.8-alpha.0

## Fibjs Orm Drivers

[![NPM version](https://img.shields.io/npm/v/@fxjs/db-driver.svg)](https://www.npmjs.org/package/@fxjs/db-driver)
[![Build Status](https://travis-ci.org/fxjs-modules/db-driver.svg)](https://travis-ci.org/fxjs-modules/db-driver)
[![Build status](https://ci.appveyor.com/api/projects/status/plarvl262d7279c3?svg=true)](https://ci.appveyor.com/project/richardo2016/db-driver)

## Install

```sh
npm install @fxjs/db-driver
```

## Built-in supported drivers

- MySQL
- SQLite
- Redis

## Support via Adapters

- @fxjs/db-driver-tdengine
- @fxjs/db-driver-elasticsearch
- @fxjs/db-driver-mongodb

## Example

```js
const DbDriver   = require("@fxjs/db-driver");

// use mysql protocol
const driver = new DbDrivers("mysql://username:password@localhost/database");
```
## Test

To test, first make sure you have development dependencies installed. Go to the root folder and do:

```sh
npm install
```

Then, just run the tests.

```sh
npm test
```

If you have a supported database server and want to test against it, first install the module:

And then run:

```sh
URI=mysql://username:password@localhost/database fibjs test/run-db
```

## Credits

This repo is checked out from [Diogo Resende]'s [node-sql-ddl-sync], which is one part of `orm`, and orm is the original source of `@fxjs/orm`. Thx a lot to him and his partner.


[Diogo Resende]:dresende@thinkdigital.pt
[node-sql-ddl-sync]:./README_orig.md
npm package: @fxjs/jws
Description: JSON Web Signatures for fibjs
Author: Liu Hu
Latest version: 0.1.1

# @fxjs/jws

**NOTE**: this is one fork version of [fib-jws], [fib-jws] cannot run on fibjs `>= 0.26.0`, but [xilion](https://github.com/xicilion) was addicted to [fibos](https://fibos.io) recently so we re-publish another package to make it available.

---

An implementation of [JSON Web Signatures](http://self-issued.info/docs/draft-ietf-jose-json-web-signature.html).

# Install

```bash
$ npm install @fxjs/jws
```

# Usage

## jws.ALGORITHMS
Array of supported algorithms. The following algorithms are currently supported.

alg Parameter Value | Digital Signature or MAC Algorithm
----------------|----------------------------
HS256 | HMAC using SHA-256 hash algorithm
HS384 | HMAC using SHA-384 hash algorithm
HS512 | HMAC using SHA-512 hash algorithm
RS256 | RSASSA using SHA-256 hash algorithm
RS384 | RSASSA using SHA-384 hash algorithm
RS512 | RSASSA using SHA-512 hash algorithm
ES256 | ECDSA using P-256 curve and SHA-256 hash algorithm
ES384 | ECDSA using P-384 curve and SHA-384 hash algorithm
ES512 | ECDSA using P-521 curve and SHA-512 hash algorithm
none | No digital signature or MAC value included


## jws.sign(header, payload, key)

Return a JSON Web Signature for a header and a payload.

Arguments:

* `header`
* `payload`
* `key`

`header` must be an object with an `alg` property. `header.alg` must be
one a value found in `jws.ALGORITHMS`. See above for a table of
supported algorithms.

If `payload` will be coerced into a string using `JSON.stringify`.

`key` is a hex encoded string or buffer containing either the secret for HMAC algorithms, or the PEM encoded public key for RSA and ECDSA.

Example

```js
const signature = jws.sign(
  // header
  { alg: 'HS256' },
  // payload
  { id: 12345, name: "Frank" },
  // secret
  '98DE76B1',
);
```

## jws.verify(signature, key, acceptAlgs)

Returns`true` or `false` for whether a signature matches a secret or key.

`signature` is a JWS Signature. `header.alg` must be a value found in `jws.ALGORITHMS`.
See above for a table of supported algorithms. `key` is a hex encoded string or
buffer containing either the secret for HMAC algorithms, or the PEM
encoded public key for RSA and ECDSA.

`acceptAlgs` is a list of what algorithms are accepted.

## jws.decode(signature)

Returns the decoded header, decoded payload, and signature parts of the JWS Signature.

Returns an object with three properties, e.g.
```js
{
  header: { alg: 'HS256' },
  payload: { id: 12345, name: "Frank" }
}
```

[fib-jws]:https://github.com/fibjs/fib-jws
npm package: @fxlint/eslint-plugin
Description: Custom rules used within People Experiences
Author: Mark Polak
Latest version: 0.5.0

# @fxlint/eslint-plugin

Some custom rules that we use internally in some of our projects that might be useful for you. You'll find more info on the project website.

## Installation

You'll first need to install [ESLint](https://eslint.org/):

```sh
npm i eslint --save-dev
```

Next, install `@fxlint/eslint-plugin`:

```sh
npm install @fxlint/eslint-plugin --save-dev
```

## Usage

Add `@fxlint` to the plugins section of your `.eslintrc` configuration file. You can omit the `eslint-plugin-` prefix:

```json
{
    "plugins": [
        "@fxlint"
    ]
}
```

Then configure the rules you want to use under the rules section.

```json
{
    "rules": {
        "@fxlint/rule-name": 2
    }
}
```

## Supported Rules

* Fill in provided rules here
npm package: @fxliperibeiro/eslint-config
Description: ESLint configuration used by @fxliperibeiro.
Latest version: 1.0.3

# @fxliperibeiro ESLint config

## Setup

1. Install the dependencies
```
npm i -D eslint @fxliperibeiro/eslint-config
```

2. Create a `.eslintrc.json` file extending the config:

### React:
```
{
  "extends": "@rocketseat/eslint-config/react"
}
```
### Node:
```
{
   "extends": "@rocketseat/eslint-config/node"
}
```

> You can also use a `.eslintrc.js` instead of JSON if you prefer.
npm package: @fxneptune/instacommandhandler
Description: Simple command handler module for insta.js
Author: Ako.
Latest version: 0.0.4

# instacommandhandler
A simple command handler for insta.js

First of all, install it with NPM

[npm i @fxneptune/instacommandhandler](https://www.npmjs.com/package/@fxneptune/instacommandhandler)

Then
Make a config.json file for clarity
```json
{
    "user": "username",
    "password": "password",
    "prefix": "../"
}
```

In your main bot class add
```javascript
const Insta = require('@androz2091/insta.js')
const client = new Insta.Client()
const config = require('./config.json');
var handler = require("@fxneptune/instacommandhandler")
var prefix = config.prefix
var cmdhandler = new handler(client, "/commands", prefix)
```

And
```javascript
client.on('messageCreate', message => {
    if(!(message.author.id == client.user.id)) {
        cmdhandler.handleCommand(message)
    }
})

client.login(config.user, config.password);
```

Now in order to have a command works you have to make a folder "commands" and in it a category like "utils"

In utils make an "help.js"

And, in help.js put
```javascript
module.exports = {
    name: "help", //main command like ../help
    aliases: [ "help", "h", "commands" ], //aliases for the command, like ../h ../help ../commands
    category: "utils", //The category where the file is, here, in "utils"
    description: "Send all commands",
    usage: "../help", //Command with the prefix
    run: async function (client, command, args, message) {

      //Here put your code as normal
        message.reply(`Help command \n * help, h, commands`);

    }
}
```

And.. That's it!

The module is in french, if a lot of eg user want's it translated I can do it
*My english is bad when I have to write a lot sorry*
_and it's 11:50 pm_
npm package: @fxnoob/translate
Description: command-line interface for initializing and synchronizing translation configurations in your project.
Author: Hitesh Saini
Latest version: 0.1.4

#  @fxnoob/translate

## Description
The Translate CLI Tool is a command-line interface for initializing and synchronizing translation configurations in your project. 

## Installation
To install the Translate CLI Tool, you need to have Node.js installed on your machine. You can install the tool globally using npm:

```bash
npm install -g @fxnoob/translate
```

## Usage

### Initialization
The `init` command initializes the translation configuration file (`translate.config.json`) in the current working directory.

```bash
translate init
```

#### Example
```bash
translate init
```

Upon running, if `translate.config.json` already exists in the directory, you will see:
```
Configuration file already exists.
```

Otherwise, it will create a new `translate.config.json` file.

### Synchronization
The `sync` command synchronizes the translation files based on the existing configuration.

```bash
translate sync
```

#### Example
```bash
translate sync
```

If `translate.config.json` does not exist, you will see:
```
Configuration file does not exist.
```

Otherwise, it will synchronize the translation files as per the configurations specified.

## Command Descriptions

- `init`: Initializes the translation configuration file.
  - **Usage**: `translate init`

- `sync`: Synchronizes the translation files based on the configuration.
  - **Usage**: `translate sync`

## Example Configuration (`translate.config.json`)
The following is an example of what the `translate.config.json` might look like:

```json
{
  "buildDir": "src",
  "defaultLocale": "en",
  "locales": ["en", "es"],
  "defaultLocaleFilePth": "en.translate.config.json"
}
```

## Internationalization (i18n)
This tool uses the `IntlUtil` class for handling internationalization. Ensure the messages and descriptions for commands are defined appropriately in your `IntlUtil` implementation.

## Development
To extend or modify the functionality, you can update the `translator.js` and `intl.js` files located in the `src` directory. These files contain the core logic for translation initialization and synchronization as well as internationalization utility functions.

## License
MIT

## Support
For any questions or issues, please open an issue on the repository or contact the maintainers.
npm package: @fxone/babel-preset
Description: babel config with typescript support
Author: fxOne
Latest version: 1.0.1

# Bebel preset

_This is a preset for babel with TypeScript support_

## Usage

Installation with yarn:

```bash
$ yarn add @fxone/babel-preset -D
```

Add some scripts to your `package.json`:

```json
{
  // ...
  "scripts": {
    "build": "babel src --extensions \".es6,.js,.es,.jsx,.mjs,.ts,.tsx\" --ignore *.spec.js --out-dir dist --copy-files --source-maps --verbose"
  }
}
```

Create a `babel.config.js` in your project directory, and set it up like so:

```js
module.exports = {
  presets: ['@fxone/babel-preset'],
};
```
npm package: @fxone/eslint-config
Description: eslint config
Author: fxOne
Latest version: 4.1.1

# eslint config

_This is a configuration for eslint_

## Installation

First, install the package:

```bash
$ npm install @fxone/eslint-config -D
# or
$ pnpm add @fxone/eslint-config -D
# or
$ yarn add @fxone/eslint-config -D
```

**Important:** You must also install ESLint as a peer dependency:

```bash
$ npm install eslint -D
# or
$ pnpm add eslint -D
# or
$ yarn add eslint -D
```

Alternatively, use `npx install-peerdeps` to automatically install peer dependencies:

```bash
$ npx install-peerdeps @fxone/eslint-config --dev
```

## Usage

Create a `eslint.config.js` file with the following content:

```js
import config from '@fxone/eslint-config';

export default [
    ...config
];
```
npm package: @fxone/prettier-config
Description: prettier config
Author: fxOne
Latest version: 2.0.0

# prettier config

_This is a configuration for prettier_

## Installation

First, install the package:

```bash
$ npm install @fxone/prettier-config -D
# or
$ pnpm add @fxone/prettier-config -D
# or
$ yarn add @fxone/prettier-config -D
```

**Important:** You must also install prettier as a peer dependency:

```bash
$ npm install prettier -D
# or
$ pnpm add prettier -D
# or
$ yarn add prettier -D
```

Alternatively, use `npx install-peerdeps` to automatically install peer dependencies:

```bash
$ npx install-peerdeps @fxone/prettier-config --dev
```

## Usage

Create a `.prettierrc.js` file with the following content:

```js
module.exports = {
  ...require('@fxone/prettier-config'),
  //add overwrites here
};
```
npm package: @fxp-co-il/fxp-web-components
Description: FXP web components library
Author: JoshK2
Latest version: 0.0.2

![Built With Stencil](https://img.shields.io/badge/-Built%20With%20Stencil-16161d.svg?logo=data%3Aimage%2Fsvg%2Bxml%3Bbase64%2CPD94bWwgdmVyc2lvbj0iMS4wIiBlbmNvZGluZz0idXRmLTgiPz4KPCEtLSBHZW5lcmF0b3I6IEFkb2JlIElsbHVzdHJhdG9yIDE5LjIuMSwgU1ZHIEV4cG9ydCBQbHVnLUluIC4gU1ZHIFZlcnNpb246IDYuMDAgQnVpbGQgMCkgIC0tPgo8c3ZnIHZlcnNpb249IjEuMSIgaWQ9IkxheWVyXzEiIHhtbG5zPSJodHRwOi8vd3d3LnczLm9yZy8yMDAwL3N2ZyIgeG1sbnM6eGxpbms9Imh0dHA6Ly93d3cudzMub3JnLzE5OTkveGxpbmsiIHg9IjBweCIgeT0iMHB4IgoJIHZpZXdCb3g9IjAgMCA1MTIgNTEyIiBzdHlsZT0iZW5hYmxlLWJhY2tncm91bmQ6bmV3IDAgMCA1MTIgNTEyOyIgeG1sOnNwYWNlPSJwcmVzZXJ2ZSI%2BCjxzdHlsZSB0eXBlPSJ0ZXh0L2NzcyI%2BCgkuc3Qwe2ZpbGw6I0ZGRkZGRjt9Cjwvc3R5bGU%2BCjxwYXRoIGNsYXNzPSJzdDAiIGQ9Ik00MjQuNywzNzMuOWMwLDM3LjYtNTUuMSw2OC42LTkyLjcsNjguNkgxODAuNGMtMzcuOSwwLTkyLjctMzAuNy05Mi43LTY4LjZ2LTMuNmgzMzYuOVYzNzMuOXoiLz4KPHBhdGggY2xhc3M9InN0MCIgZD0iTTQyNC43LDI5Mi4xSDE4MC40Yy0zNy42LDAtOTIuNy0zMS05Mi43LTY4LjZ2LTMuNkgzMzJjMzcuNiwwLDkyLjcsMzEsOTIuNyw2OC42VjI5Mi4xeiIvPgo8cGF0aCBjbGFzcz0ic3QwIiBkPSJNNDI0LjcsMTQxLjdIODcuN3YtMy42YzAtMzcuNiw1NC44LTY4LjYsOTIuNy02OC42SDMzMmMzNy45LDAsOTIuNywzMC43LDkyLjcsNjguNlYxNDEuN3oiLz4KPC9zdmc%2BCg%3D%3D&colorA=16161d&style=flat-square)

# FXP web components library

## Using this component

### Script tag

- [Publish to NPM](https://docs.npmjs.com/getting-started/publishing-npm-packages)
- Put a script tag similar to this `<script src='https://unpkg.com/my-component@0.0.1/dist/mycomponent.js'></script>` in the head of your index.html
- Then you can use the element anywhere in your template, JSX, html etc