open-index/open-npm huggingface dataset:
npm package: @morr/vue-waypoint
Description: > trigger functions and events based on the element position on the screen
Latest version: 4.0.8

# VueWaypoint

> trigger functions and events based on the element position on the screen

![Latest Release](https://github.com/scaccogatto/vue-waypoint/workflows/Release/badge.svg)

## Vue2 and Nuxt version

[vue-waypoint for Vue2 repository](https://github.com/scaccogatto/vue-waypoint/tree/vue2)

## Demo

[Simple demo page](https://vue-waypoint.netlify.app/)

Open your browser console and see what's going on while scrolling up and down

## Features

- [x] Vue 3
- [x] No dependencies
- [x] Flexible
- [x] Typescript
- [x] Battle tested
- [x] Customizable
- [x] Solid project (3+ years)

## Getting started

### npm

```bash
npm i vue-waypoint
```

### Vue component

```html
<template>
  <Waypoint @change="onChange">
    slot content
  </Waypoint>
</template>
```

```html
<script lang="ts">
import { defineComponent } from "vue";
import { VueWaypoint } from 'vue-waypoint'

export default defineComponent({
  name: "SomeComponent",
  components: {
    Waypoint
  },
  setup() {
    const onChange = (waypointState) => {
      // Going can be:
      // IN
      // OUT
      console.log(waypointState.going);

      // Direction can be:
      // UP
      // DOWN
      // LEFT
      // RIGHT
      console.log(waypointState.direction);
    }

    return { onChange };
  }
});
</script>
```

## Props

### `active`

- [x] Can use a reactive variable
- [x] Can set `true`/`false` dinamically

Usage:

- Enable the waypoint: `<Waypoint :active="true" />`
- Disable the waypoint: `<Waypoint :active="false" />`

### `options`

- [x] Useful for inner div detection
- [x] Trigger `change` event a portion of the element is completely on screen
- [x] Is an [official IntersectionObserverInit implementation](https://developer.mozilla.org/en-US/docs/Web/API/IntersectionObserver/IntersectionObserver)

Usage:

- Set a custom `IntersectionObserver` options: `<Waypoint :options="options" />`
- Read what you can do with `options`: [IntersectionObserverInit docs](https://developer.mozilla.org/en-US/docs/Web/API/IntersectionObserver/IntersectionObserver)

Options example:

```js
const options: IntersectionObserverInit = {
  root: document,
  rootMargin: '0px 0px 0px 0px',
  threshold: [0.25, 0.75]
};
```

### `tag`

- [x] Set your preferred tag for the element
- [x] Defaults to `div`

- Waypoint as div: `<Waypoint :tag="'div'" /> --> renders --> <div></div>`
- Waypoint as span: `<Waypoint :tag="'span'" /> --> renders --> <span></span>`
- Waypoint as p: `<Waypoint :tag="'p'" /> --> renders --> <p></p>`

## Events

### `change`

Emitted every time the waypoint detects a change.

```html
<template>
  <Waypoint @change="onChange" />
</template>
```

```js
const changeFunction = (waypointState) => {..}
```

```js
WaypointState {
  el: Element,
  going: 'IN' | 'OUT';
  direction: 'UP' | 'DOWN' | 'LEFT' | 'RIGHT';
};
```

## Development

1. Fork the repository
2. Run the project (`npm i && npm run serve`)
3. Follow [Conventional Commits spec](https://www.conventionalcommits.org/en/v1.0.0/) for your commits
4. Open a pull request
npm package: @morr/vue3-analytics
Description: Google Analytics plugin for Vue 3
Author: Matteo Gabriele
Latest version: 1.0.0

# vue3-analytics

Vue plugin for Google Analytics

## Why should I use it?

The plugin isn't just a wrapper of the Google Analytics API, but provides a solution to issues that most of the time you don't want to deal with or you not even know you have to deal with.

For example:

* Automatic Google Analytics script loading
* Automatic page tracking
* Event batching
* Opt-out from Google Analytics with promise support
* Multiple domain ID tracking system
* Vuex support
* E-commerce API
* Vue error exception tracking system
* Debugging API

## Does this library support GA4?
Nope! GA4 is only supported by the new gtag.js library which you can find in the `vue-gtag` package. 
This package only uses analytics.js which doesn't provide that feature.

## Requirements

Vue ^3.0.0

## Articles

[Google Analytics, GDPR and Vuejs](https://medium.com/@matteo_gabriele/google-analytics-gdpr-and-vuejs-e1bd6affd2b4)

[Vuejs and Google Analytics](https://medium.com/@matteo_gabriele/vuejs-and-google-analytics-689a07e00116)

[Tips & tricks for vue-analytics](https://medium.com/@matteo_gabriele/tips-tricks-for-vue-analytics-87a9d2838915)

## Install

```bash
npm install @morr/vue3-analytics
```

## User guide

* [Get started](/docs/installation.md)
* [How to load Google Analytics](/docs/script-loader.md)
* [Page tracking](/docs/page-tracking.md)
* [Event tracking](/docs/event-tracking.md)
* [Screen tracking](/docs/screen-tracking.md)
* [Event batches](/docs/batch.md)
* [v-ga](/docs/v-ga.md)
* [Cross-domain tracking](/docs/cross-domain-tracking.md)
* [User timings](/docs/user-timings.md#user-timings)
* [Exception tracking](/docs/exception-tracking.md)
* [Require](/docs/require.md)
* [Set](/docs/set.md)
* [Social interactions](/docs/social-interactions.md)
* [Fields](/docs/fields.md)
* [On Analytics script ready](/docs/when-google-analytics-is-loaded.md)
* [Custom methods](/docs/custom-methods.md)
* [E-commerce](/docs/ecommerce.md)
* [Untracked hits](/docs/untracked-hits.md)
* [Vuex](/docs/vuex.md)
* [Turn off during development](/docs/turn-off-development.md)
* [Console logs](/docs/console-logs.md)
* [Opt-out from Google Analytics](/docs/opt-out.md)
* [Custom analytics.js URL](/docs/custom-analytics.md)
* [Debug](/docs/debug.md)
npm package: @morrigu/core
Description: This guide provides an overview of how to configure the `@morrigu/core` package for use in your React applications. `@morrigu/core` offers a suite of React hooks for interacting with the Morrigu SaaS product, including feature flagging and prompt manageme
Latest version: 1.0.4



# Configuration Guide

This guide provides an overview of how to configure the `@morrigu/core` package for use in your React applications. `@morrigu/core` offers a suite of React hooks for interacting with the Morrigu SaaS product, including feature flagging and prompt management based on environmental settings.

## Getting Started

Before you begin, ensure you have `node` and `npm`/`yarn` installed on your machine. This guide assumes you have basic knowledge of React and environment variable management in a development project.

## Installation

To use `@morrigu/core` in your project, install it via npm or yarn:

```bash
npm install @morrigu/core
```

Or, if you're using Yarn:

```bash
yarn add @morrigu/core
```

## Configuration

`@morrigu/core` requires specific environment variables to be set for authentication and API interaction:

- `MORRIGU_SECRET_KEY`: Your Morrigu application's secret key.
- `MORRIGU_CLIENT_ID`: The client ID for your Morrigu application.

### Setting Environment Variables

#### Development Environment

For local development, you can set these variables in a `.env.local` file at the root of your project:

```env
MORRIGU_SECRET_KEY=your_secret_key_here
MORRIGU_CLIENT_ID=your_client_id_here
```

Make sure to add `.env.local` to your `.gitignore` file to prevent secret leakage.

#### Production Environment

In production, set the environment variables through your hosting provider's dashboard. For example, if you're using Vercel or Netlify, you can add environment variables in the project settings.

## Using `@morrigu/core`

After configuring the environment variables, you can start using `@morrigu/core` in your React components.

```jsx
import React from 'react';
import { useFeatureFlag } from '@morrigu/core';
import { usePrompt } from '@morrigu/core';

const MyComponent = () => {
  const [prompt, {completion, reset, stream}] = usePrompt('my-prompt');

  return (

  );
};

export default MyComponent;
```

<!-- ## Support -->
<!--  -->
<!-- For support with `@morrigu/core`, please open an issue on our [GitHub repository](https://github.com/your-repo-url). -->

<!-- ## Contributing -->
<!--  -->
<!-- We welcome contributions to `@morrigu/core`! Please see our [contributing guidelines](https://github.com/your-repo-url/CONTRIBUTING.md) for more details. -->

## License

`@morrigu/core` is open-source software licensed under the MIT license.
```

This README provides a basic structure for configuring and getting started with your package. Remember to replace placeholder texts like `your_secret_key_here`, `your_client_id_here`, and repository URLs with actual information relevant to your project.
npm package: @morrisallison/tslint-config
Description: A shared TSLint configuration
Author: Morris Allison III
Latest version: 0.1.2

# tslint-config

A shared TSLint configuration.

[![npm Version][badge-npm]][npm]
[![MIT License][badge-license]][license]
[![bitHound][badge-bithound]][bithound]
[![TSLint Version][badge-tslint]][tslint]
[![TypeScript Version][badge-typescript]][typescript]

[badge-bithound]: https://img.shields.io/bithound/dependencies/github/morrisallison/tslint-config.svg?style=flat-square
[badge-license]: https://img.shields.io/badge/license-MIT-blue.svg?style=flat-square
[badge-npm]: https://img.shields.io/npm/v/@morrisallison/tslint-config.svg?style=flat-square
[badge-tslint]: https://img.shields.io/badge/TSLint-v4.2-blue.svg?style=flat-square
[badge-typescript]: https://img.shields.io/badge/TypeScript-v2.1-blue.svg?style=flat-square
[bitHound]: https://bithound.io/github/morrisallison/tslint-config
[license]: https://github.com/morrisallison/tslint-config/raw/master/LICENSE
[npm]: https://www.npmjs.com/package/@morrisallison/tslint-config
[tslint]: https://github.com/palantir/tslint
[typescript]: https://github.com/Microsoft/TypeScript

## Installation

Node.js via [Yarn][yarnpkg]

```bash
yarn add -D @morrisallison/tslint-config
```

Node.js via [npm][npmjs]

```bash
npm install @morrisallison/tslint-config --save-dev
```

[npmjs]: https://www.npmjs.com/
[yarnpkg]: https://yarnpkg.com/

## Usage

Create a file in the project root named `tslint.json` containing the following:

```json
{
    "extends": "@morrisallison/tslint-config"
}
```

## License

Copyright &copy; 2016 [Morris Allison III](http://morris.xyz).
<br>Released under the [MIT license][license].
npm package: @morrisgallego/potrans
Description: CLI tool to translate PO files easily
Author: Víctor José Gallego Fontenla
Latest version: 1.0.2

# POTrans [![npm version](https://badge.fury.io/js/%40morrisgallego%2Fpotrans.svg)](https://badge.fury.io/js/%40morrisgallego%2Fpotrans)
> Translate gettext files from console, easly

This tool helps you to translate your POT/PO files easily from the console. Also, it supports spell checking.

## Usage
### potrans install <language>
Install a dictionary for the specified language for spell checking

### potrans uninstall <language>
Uninstall an installed dictinary

### potrans list
List all installed dictinaries

### potrans translate <file> [-o output]
Translate the selected file using the tool. If output is specified the tool will save to that location. Else it will overide the source file.
npm package: @mors/eslint-config
Description: Mors Digital`s ESLint config
Author: Ilya Amursky
Latest version: 1.0.0

# `@mors/eslint-config`

## Usage

Notice: expected to be used with [@mors/prettier-config](https://www.npmjs.com/package/@mors/prettier-config).

**Install**:

```bash
$ npm i -D @mors/eslint-config
```

**Edit `package.json`**:

```jsonc
{
  // ...
  "eslintConfig": {
    "extends": "@mors/eslint-config"
  }
}
```
npm package: @mors/prettier-config
Description: Mors Digital`s Prettier config
Author: Ilya Amursky
Latest version: 1.0.0

# `@mors/prettier-config`

## Usage

**Install**:

```bash
$ npm i -D @mors/prettier-config
```

**Edit `package.json`**:

```jsonc
{
  // ...
  "prettier": "@mors/prettier-config"
}
```
npm package: @morsecodemedia/containers.css
Description: A starting point for containers and gaps when you don't want to use Bootstrap and you can't go evergreen with CSS Grid.
Author: Brandon Morse
Latest version: 1.1.8

# containers.css

> A starting point for container and gaps when you don't want to use Bootstrap and you can't go evergreen with CSS Grid.

![GitHub](https://img.shields.io/github/license/morsecodemedia/containers.css.svg?color=green&label=license)
![NPM](https://img.shields.io/npm/v/@morsecodemedia/containers.css)
![npm](https://img.shields.io/npm/dt/@morsecodemedia/containers.css)

## Installation
**YARN**
```sh
yarn add -D @morsecodemedia/containers.css
```

**NPM**
```sh
npm install -D @morsecodemedia/containers.css
```

## Adding to project
### Nuxt.js
In the `nuxt.config.js` file
```js
css: [
  '@morsecodemedia/containers.css'
]
```

## Browser support
* Chrome
* Edge
* Firefox ESR+
* Internet Explorer 10+
* Safari 8+
* Opera

## Containers
Containers are the max-width areas in which content blocks can take up. Currently there are three (1-3), 1 being the widest and 3 being the most narrow.
### A Visual Representation
https://morsecodemedia.github.io/containers.css/

### Containers Breakdown

#### 0px-767px
`.container1` 100% - 30px (15px on either side)

`.container2` 100% - 30px (15px on either side)

`.container3` 100% - 30px (15px on either side)

#### 768px-991px
`.container1` 100% - 50px (25px on either side)

`.container2` 100% - 70px (35px on either side)

`.container3` 100% - 110px (55px on either side)

#### 992px-1199px
`.container1` 100% - 70px (35px on either side)

`.container2` 100% - 200px (100px on either side)

`.container3` 100% - 400px (200px on either side)

#### 1200px-1399px
`.container1` 100% - 100px (50px on either side)

`.container2` 100% - 300px (150px on either side)

`.container3` 100% - 500px (250px on either side)

#### 1400px+
`.container1` max-width: 1300px

`.container2` max-width: 1000px

`.container3` max-width: 700px

## Gaps
Gaps are vertical spacing used between columns to keep a consistent vertical rhythm among containers. Currently there are four gaps (1-4). 1 being the smallest and 4 being the tallest.

### Gaps Breakdown

#### 0px-767px
`.gap1` 10px

`.gap2` 15px

`.gap3` 20px

`.gap4` 30px

#### 768px-1199px
`.gap1` 15px

`.gap2` 20px

`.gap3` 30px

`.gap4` 40px

#### 1200px+
`.gap1` 20px

`.gap2` 30px

`.gap3` 40px

`.gap4` 50px

## Content Blocks
`.half` `.half`

`.forty` `.sixty`

`.sixty` `.forty`

`.third` `.third` `.third`

`.quarter` `.quarter` `.quarter` `.quarter`

`.third` `.two-third`

`.two-third` `.third`

`.quarter` `.three-quarter`

`.three-quarter` `.quarter`
npm package: @morsedigital/i18n_helper
Description: Little helper for I18n-js
Author: Adrian Stainforth
Latest version: 2.0.0

# I18n_helper.js

A little helper to work with [i18n-js][0]

Set i18n-js gem in your rails app as the readme. Although maybe sure you have install i18n-js through npm/yarn.abs

By default the helper will use the lang attribute too set the language.

So:

```html
<html lang="<%= I18n.locale %>"></html>
```

Then in your JS:

```javascript
import i18nHelper from '@morsedigital/i18n_helper';

const t = i18nHelper();

// Basics
p.innerHTML = t('my.key.goes.here', { translate: true }); // looks up 'my.key.goes.here'

// split keys
p.innerHTML = t('my', 'key', 'goes.here', { translate: true }); // looks up 'my.key.goes.here'

// pass option keys
p.innerHTML = t('my', 'key', 'goes.here', { translate: true, foo: 'bar' }); // looks up 'my.key.goes.here' with options {foo: 'bar'}

// Preset part keys
const key = t('my.key');

p.innerHTML = key('goes.here', { translate: true }); // looks up 'my.key.goes.here'

p2.innerHTML = key('another.here', { translate: true }); // looks up 'my.key.another.here'

p3.innerHTML = key('another.here', { translate: true, foo: 'bar' }); // looks up 'my.key.goes.here' with options {foo: 'bar'}

// Preset part keys and options
const key = t('my.key', { foo: 'bar' });

p.innerHTML = key('goes.here', { translate: true, path: 'foo/bar' }); // looks up 'my.key.goes.here' with options {foo: 'bar', path: 'foo/bar'}

p2.innerHTML = key('another.here', { translate: true, path: 'bar/foo' }); // looks up 'my.key.another.here' with options {foo: 'bar', path: 'bar/foo'}
```

# Bug reports

If you discover any bugs, feel free to create an issue on GitHub. Please add as much information as possible to help us fixing the possible bug. We also encourage you to help even more by forking and sending us a pull request.

https://github.com/morsedigital/i18n_helper/issues

## Contribute

If you'd like to contribute, i18n_helper is written using babel and rollup in ES6.

Please make sure any additional code should be covered in tests (Jest).

If you need to run the test please use:

```bash

yarn test

```

or to rebuild the JS run:

```bash

yarn build

```

## Maintainers

Adrian Stainforth (https://github.com/djforth)

# License

i18n_helper is an open source project falling under the MIT License. By using, distributing, or contributing to this project, you accept and agree that all code within the @morsedigital/select-filter project are licensed under MIT license.

[0]: https://github.com/fnando/i18n-js
npm package: @morsedigital/morse-marker
Description: Morse Marker for JS on all projects outputs into console
Author: Adrian Stainforth
Latest version: 1.0.1

# morse-marker
Morse Marker for JS on all projects outputs into console

```bash
yarn add @morsedigital/morse-marker
```

Add into JS

```javascript
import '@morsedigital/morse-marker';
```
outputs:

```javascript
    __  ___                        ____  _       _ __        __
   /  |/  /___  _____________     / __ \(_)___ _(_) /_____ _/ /
  / /|_/ / __ \/ ___/ ___/ _ \   / / / / / __ `/ / __/  __`/ /
 / /  / / /_/ / /  (__  )  __/  / /_/ / / /_/ / / /_/ /_/ / /
/_/  /_/\____/_/  /____/\___/  /_____/_/\__, /_/\__/\__,_/_/
                                       /____/

SITE BUILT BY MORSE DIGITAL © 2017- http://morsedigital.com
```
npm package: @morsedigital/select-filter
Description: Allows a select to call api to filter results in another select.L0
Author: Adrian Stainforth
Latest version: 1.0.1

# select-filter

Allows a select to call api to filter results in another select.L0

Install into project

```
yarn add @morsedigital/select-filter
```

Set up your HTML like so:

```HTML
<select data-select-filter="second-select" data-select-filter-api="my/api/path" id="first-select">
  <option value="1">Option 1</option>
  <option value="2">Option 2</option>
</select>

<select id="second-select"> </select>
```

'data-select-filter' is id of the select you want updated

'data-select-filter-api' is the api path to where you are going to pull the data from.

In javascript add the following way:

```javascript
import SelectFilter from "@morsedigital/select-filter";

(() => {
  SelectFilter();
})();
```

Then when the select is changes it will hit the api + value. So in this example if 'Option 1' is selected the a request is sent to 'my/api/path/1'.

The response should be as json like so:

```json
[
  {
    "title": "Option",
    "value": "some value"
  },
  {
    "title": "Another Option",
    "value": "another value"
  }
]
```

and the select will be updated like so:

```HTML
<select id="second-select">
  <option value="some value">Option</option>
  <option value="another value">Another Option</option>
</select>
```

You can also change the way the api is called.

If you prefer a query string:

```javascript
import SelectFilter from "@morsedigital/select-filter";

(() => {
  SelectFilter({ query: true });
})();
```

Then when the select is changes it would call 'my/api/path?value=1'.

Or if you would prefer to POST the data for the following:

```javascript
import SelectFilter from "@morsedigital/select-filter";

(() => {
  SelectFilter(
    { query: false },
    {
      method: "POST"
      //... other fetch options
      // see https://developer.mozilla.org/en-US/docs/Web/API/Fetch_API/Using_Fetch
    }
  );
})();
```

Then when the select is changes it would call 'my/api/path' with a json body of { value: 1 }

# Bug reports

If you discover any bugs, feel free to create an issue on GitHub. Please add as much information as possible to help us fixing the possible bug. We also encourage you to help even more by forking and sending us a pull request.

https://github.com/morsedigital/select-filter/issues

## Contribute

If you'd like to contribute, @morsedigital/select-filter is written using babel and rollup in ES6.

Please make sure any additional code should be covered in tests (Jest).

If you need to run the test please use:

```bash

yarn test

```

or to rebuild the JS run:

```bash

yarn build

```

## Maintainers

Adrian Stainforth (https://github.com/djforth)

# License

@morsedigital/select-filter is an open source project falling under the MIT License. By using, distributing, or contributing to this project, you accept and agree that all code within the @morsedigital/select-filter project are licensed under MIT license.
npm package: @morsedigital/vanilla-tabbed-content
Description: Tabbed content module written in vanilla JavaScript
Author: Ian Hatton
Latest version: 2.2.2

# vanilla-tabbed-content

### Synopsis
A tabbed content module written in vanilla JavaScript.

### Installation
```
npm install @morsedigital/vanilla-tabbed-content
```

### Running tests
```
npm run test
```

### Example Instantiation
```javascript
import TabbedContentClass from '@morsedigital/vanilla-tabbed-content';

const tabbedContentElements = document.querySelectorAll('.tabbed-content');

if (tabbedContentElements.length > 0){
  Array.from(tabbedContentElements).map((element)=>{
    return new TabbedContentClass({
      element: element
    });
  });
}
```

### Configuration
A new instance of TabbedContentClass can contain the following in its configuration object:
```javascript
new TabbedContentClass({
  element: // The DOM node to be instantiated as having tabbed content
  , bodyContainerClass: // String. Class for the tabbed content's body. Default is "tabbed-content-body"
  , navContainerClass: // String. Class for the tabbed content's navigation. Default is "tabbed-content-nav"
  , tabContainerClass: // String. Class for each tab. Default is "tabbed-content-tab"
});
```

### Example HTML structure
```html
<div class="tabbed-content">
  <ul class="tabbed-content-nav" role="tablist">
    <li role="presentation">
      <a href="#" role="tab">Tab 1</a>
    </li>
    <li role="presentation">
      <a href="#" role="tab">Tab 2</a>
    </li>
  </ul>
  <div class="tabbed-content-body">
    <article class="tabbed-content-tab">
      <h1>Tab 1</h1>
      <p>Lorem ipsum dolor sit amet, consectetur adipisicing elit.</p>
    </article>
    <article class="tabbed-content-tab">
      <h1>Tab 2</h1>
      <p>Doloribus quisquam, voluptatum dolores amet incidunt dicta.</p>
    </article>
  </div>
</div>
```

All tabbed content must be wrapped in a single parent div with a class of ***tabbed-content***. The navigation is always wrapped in a div with a class of ***tabbed-content-nav***, and the body in a div with a class of ***tabbed-content-body***. The tabs themselves are individually wrapped in a div with a class of ***tabbed-content-tab***.

The relationship between navigation items and tabs is always based on their index, ie navigation item 0 will control tab 0, etc.

### CSS
As a bare minimum, you'll require the following, or similar CSS:

```scss
.tabbed-content-tab {
  display: none;

  &.active {
    display: block;
  }
}
```
npm package: @morsedigital/webpack-defaults
Description: ## Morse Webpack defaults
Author: Adrian Stainforth
Latest version: 7.3.4

# webpack-defaults

## Morse Webpack defaults

This module is for adding the Webpack defaults for Morse Projects

## What's Webpack & Webpacker?

Webpack is a Javascript bundler for front-end code and assets, built in Node.  In morse projects we use Rails default webpack gem [webpacker](https://github.com/rails/webpacker) and extends the related [webpacker module](https://www.npmjs.com/package/webpacker)

## Why webpacker?

Something that comes out often particularly from Backender is frustration at the enviroment so it worth just understanding the benefits of the approach over older techniques like adding cdn versions and sprockets.

The frontend has become increasingly complex, from the multiple devices to the requirement of clients and users for more app like interfaces. While some of these can be managed with older approaches, managing the frontend code quickly becomes unmanagable and the performance of the site also can quickly become a problem. 

Webpack allows us to add modules that helps with code management and optimising the code, which can greatly improve building frontends.  The add to this it allows to through modules like Babel for Javascript and PostCSS for CSS allows to use future syntax and normalises it for older browser like IE11. This allows to write modern focused
npm package: @morsekode/backstage-components
Description: Stencil Component Starter
Latest version: 0.0.1

# Morsekode Backstage Web Components

These components can be used in instances where Vue is either unavailable or can't be used.

## Development

This project is made with StencilJS. See their [docs](https://stenciljs.com/docs/introduction) if needed.

Run `npm start` during development for automatic recompile and browser live reload.

## Build & Publish

Run `npm run build`, increment the package.json version, and run `npm publish`.
npm package: @morshu1/uwuify
Description: Node.js wrapper to the uwuify library
Author: Morshu
Latest version: 1.0.6

# uwuify-rs
Node.js wrapper to the [uwuify](https://crates.io/crates/uwuify) library

## Requirements
An x86/x86_64 CPU that supports SSE4.1 and a copy of [Rust](https://www.rust-lang.org/tools/install) installed to compile the native module.

## Documentation
Theres only 1 function, that is `uwuify()`, which uwuifys text.
### example
```js
const {uwuify} = require('@morshu1/uwuify')
console.log(uwuify("When the imposter is sus"))
```