open-index/open-npm huggingface dataset:
npm package: @sektek/eslint-plugin
Description: Eslint configuration for all @sektek projects
Author: Edward Kelly
Latest version: 2.0.0

# @sektek/eslint-plugin

## Installation

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

## Setup

Extend the configs you want in your `eslint.config.js` file:

```js
import { defineConfig } from 'eslint/config';
import sektek from '@sektek/eslint-plugin';

export default defineConfig([
  sektek.configs.recommended,
]);
```

## Rules

The plugin is composed of the following configurations:

- `@sektek/recommended`: recommended rules for all JavaScript projects
- `@sektek/typescript`: An extension of `@sektek/recommended` including TypeScript-specific rules
npm package: @sektek/prettier-config
Description: Prettier config used for @sektek projects
Author: Edward Kelly
Latest version: 2.0.0

# @sektek/prettier-config

Prettier config used for @sektek projects.

## Installation

```sh
npm install --save-dev prettier @sektek/prettier-config
```

## Setup

Create a `.prettierrc.js` in the root of your project with the following:

```javascript
import prettierConfig from '@sektek/prettier-config';

export default prettierConfig;
```
npm package: @sekyuriti/attest
Description: API protection middleware for Next.js - verify requests with ATTEST
Author: SEKYURITI
Latest version: 0.4.1

# @sekyuriti/attest

API protection for Next.js applications. Verify that requests come from real browsers, not bots or scripts.

## Quick Start

One command setup:

```bash
npx @sekyuriti/attest login
```

This will:
1. Open browser for authentication
2. Let you select your project
3. Auto-add environment variables to `.env.local`
4. Auto-inject the ATTEST script into `layout.tsx`

Done. Your API is protected.

## What It Does

- **Frontend script** automatically signs all `fetch()` and `XMLHttpRequest` calls
- **Backend verification** validates signatures with SEKYURITI's API
- **Bots and scripts** can't generate valid signatures without running in a real browser

## Optional: Middleware

Add server-side verification for all API routes:

```ts
// middleware.ts
import { createAttestMiddleware } from "@sekyuriti/attest/middleware";

export const middleware = createAttestMiddleware({
  projectId: process.env.NEXT_PUBLIC_ATTEST_KEY!,
  apiKey: process.env.ATTEST_SECRET_KEY!,
});

export const config = {
  matcher: "/api/:path*",
};
```

## Optional: Per-Route Verification

```ts
// app/api/protected/route.ts
import { verifyAttest } from "@sekyuriti/attest";

export async function POST(request: Request) {
  const result = await verifyAttest(request, {
    projectId: process.env.NEXT_PUBLIC_ATTEST_KEY!,
    apiKey: process.env.ATTEST_SECRET_KEY!,
  });

  if (!result.attested) {
    return Response.json({ error: "Not attested" }, { status: 403 });
  }

  // Handle request...
}
```

## CLI Commands

```bash
attest login     # Authenticate and setup project
attest logout    # Sign out
attest status    # Show account and usage info
attest init      # Re-run setup in current project
attest whoami    # Print current user email
attest help      # Show help
```

## Environment Variables

Auto-generated by `attest login`:

```env
NEXT_PUBLIC_ATTEST_KEY=your_public_key
ATTEST_SECRET_KEY=your_secret_key
```

## Protection Features

- DevTools detection
- Bot/headless browser detection
- Request signing with HMAC-SHA256
- Browser fingerprinting
- Timestamp validation

## Documentation

https://sekyuriti.build/docs/attest

## License

MIT
npm package: @sekyuriti/cloak
Description: JavaScript obfuscation CLI - code never leaves your machine
Author: SEKYURITI
Latest version: 0.1.2

# @sekyuriti/cloak

JavaScript obfuscation CLI. Your code never leaves your machine.

## Install

```bash
npm install -g @sekyuriti/cloak
```

## Quick Start

```bash
# Authenticate
cloak login

# Protect a file
cloak protect app.js

# Protect a directory
cloak protect src/ -o dist/
```

## Commands

| Command | Description |
|---------|-------------|
| `cloak login` | Authenticate with SEKYURITI |
| `cloak logout` | Sign out |
| `cloak status` | Show account info and tier |
| `cloak protect <file\|dir>` | Obfuscate JavaScript file(s) |
| `cloak help` | Show help |

## Options

| Option | Description |
|--------|-------------|
| `-o, --output <dir>` | Output directory |
| `--local` | Run locally without authentication (free features only) |
| `--domain-lock <domains>` | Lock to specific domains (PRO) |
| `--expiration <date>` | Set expiration date (PRO) |
| `--anti-debug` | Enable anti-debugging (PRO) |
| `--anti-tamper` | Enable anti-tampering (PRO) |
| `--no-control-flow` | Disable control flow flattening |
| `--no-dead-code` | Disable dead code injection |

## Tiers

### FREE

- Variable renaming
- String encryption (basic)
- Unlimited local usage

### PRO ($19/mo)

- Everything in FREE
- Control flow flattening
- Dead code injection
- Domain lock
- Anti-debugging
- Anti-tampering
- Expiration / time bomb
- Violation telemetry dashboard

## Examples

```bash
# Basic protection
cloak protect app.js

# Output to different directory
cloak protect src/ -o dist/

# Lock to specific domains (PRO)
cloak protect app.js --domain-lock example.com,www.example.com

# Set expiration date (PRO)
cloak protect app.js --expiration 2025-12-31

# Full protection (PRO)
cloak protect app.js --domain-lock example.com --anti-debug --anti-tamper
```

## Links

- Documentation: https://sekyuriti.build/docs/cloak
- Module page: https://sekyuriti.build/modules/cloak
- Dashboard: https://sekyuriti.build/dashboard/cloak

## License

MIT
npm package: @selaliadobor/next-superjson
Description: Automatically transform your Next.js Pages to use SuperJSON, without losing swc support
Author: Tommaso De Rossi, morse
Latest version: 1.0.3

## Getting started

Install the library with your package manager of choice, e.g.:

```
npm install next-superjson
```

Since this is a companion to [SuperJSON](https://github.com/blitz-js/superjson),
make sure it's also installed:

```
npm install superjson
```

Add the plugin to your `next.config.js`.
If you don't have one, create it.

```js
const { withSuperjson } = require('next-superjson')

module.exports = withSuperjson()({})
```

That's it! Now you're free to use all values and type supported by SuperJSON in your Next.js Components.

# How it works

New Nextjs 12 uses `swc` to compile user code by default, adding a custom `.babelrc` file will make Nextjs compile everything using Babel instead (much slower).

This plugin will inject the superjson babel plugin only on files under the `pages` directory so you can keep using swc for all the other files.

## Sponsors

[**Notaku**](https://notaku.website)

[![Notaku](https://preview.notaku.website/github_banner.jpg)](https://notaku.website)
npm package: @selaliadobor/next-superjson-plugin
Description: Automatically transform your Next.js Pages to use SuperJSON with SWC
Author: JH.Lee
Latest version: 0.6.5

<h1 align="middle"> Next SuperJSON Plugin</h1>
<h3 align="middle">🔌 SuperJSON Plugin for Next.js (SWC)</h3>

### /pages (Pages Directory)

```jsx
export default function Page({ date }) {
  return <div>Today is {date.toDateString()}</div>;
}

// You can also use getInitialProps, getStaticProps
export const getServerSideProps = () => {
  return {
    props: {
      date: new Date(),
    },
  };
};
```

- Allows pre-rendering functions to return props including [Non-JSON Values](https://github.com/blitz-js/superjson#parse)(Date, Map, Set..)

### /app (App Directory)

```jsx
// Use "data-superjson" attribute to pass non-serializable props to client components
// No needs to change the propsType of Client Component (It's type-safe!)

export default function ServerComponent() {
  const date = new Date();
  return <ClientComponent date={date} data-superjson />;
}
```

- Provides `data-superjson` attribute for [Server Component > Client Component Serialization](https://beta.nextjs.org/docs/rendering/server-and-client-components#passing-props-from-server-to-client-components-serialization).

## Usage

Install packages first:

```sh
npm install superjson next-superjson-plugin
# or Yarn
yarn add superjson next-superjson-plugin
```

Add the plugin into `next.config.js`

```js
// next.config.js
module.exports = {
  experimental: {
    swcPlugins: [["next-superjson-plugin", {}]],
  },
};
```

### Options

You can use the `excluded` option to exclude specific properties from serialization.

```js
['next-superjson-plugin', { excluded: ["someProp"] }],
```

#### With pages router

There is currently an issue in `Next@15`, to use this plugin with pages router add this option:
This will make the plugin only work inside the page router and is thus not compatible with projects using both routers.

```js
['next-superjson-plugin', { forcePageRouter: true }],
```

## How it works

```mermaid
sequenceDiagram
    participant Next.js
    participant SWC Plugin
    participant SuperJSON
    Next.js->>SWC Plugin: Request Transform
    SWC Plugin->>SWC Plugin: Transform Pages/Components <br> To Use SuperJSON
    SWC Plugin->>Next.js: Take Modules
    Next.js-->SuperJSON: Connected
    Next.js->>SuperJSON: Serialize Props <br> (Date, BigInt, Set, Map..)
    Note over SWC Plugin: getInitialProps <br> getServerSideProps <br> getStaticProps <br> Server Components
    SuperJSON->>Next.js: Deserialize Props
    Note over SWC Plugin: Pages <br> Client Components

```

## Bug Report

⚠️ Keep in mind: SWC Plugin is still an experimental feature for Next.js

Plugin always ensures compatibility with [Next.js Canary version](https://nextjs.org/docs/messages/opening-an-issue) only.

[Leave an Issue](https://github.com/orionmiz/next-superjson-plugin/issues)

## Special Thanks

- [kdy1](https://github.com/kdy1) (Main creator of swc project)
npm package: @selaliadobor/wawa-lipsync
Description: A simple and easy-to-use library for real-time lipsyncing with JS and web audio API.
Latest version: 0.0.1

# Wawa Lipsync

A **simple** and **easy-to-use** library built in TypeScript for **real-time lipsyncing with JS and web audio API**. Ideal for animating 2D/3D characters in web apps, chatbots, and games.

The examples shows how to use the library with a 3D model in Three.js with React Three Fiber.

[Live demo](https://wawa-lipsync.wawasensei.dev/) - [Video tutorial](https://youtu.be/GXU1amqvJF8)

## Installation

```bash
npm install wawa-lipsync
```

or

```bash
yarn add wawa-lipsync
```

## Usage

First, import the library and create a `Lipsync` instance:

```javascript
import { Lipsync } from "wawa-lipsync";

export const lipsyncManager = new Lipsync();
```

Then, you need to connect the [HTML `<audio>` element](https://www.w3schools.com/html/html5_audio.asp) to the `lipsyncManager`:

```javascript
const audioElement = new Audio("path/to/your/audio/file.mp3");

lipsyncManager.connectAudio(audioElement);
```

The [AnalyserNode](https://developer.mozilla.org/en-US/docs/Web/API/AnalyserNode) used by the library requires the audio element to have a valid source before the connection.

This will work:

```javascript
const audioElement = new Audio();
audioElement.src = "path/to/your/audio/file.mp3";
lipsyncManager.connectAudio(audioElement);
```

But this will not:

```javascript
const audioElement = new Audio();
lipsyncManager.connectAudio(audioElement);
```

After connecting the audio element, you can start the lipsyncing process by calling the `processAudio` method at the desired interval:

```javascript
const analyzeAudio = () => {
  requestAnimationFrame(analyzeAudio);
  lipsyncManager.processAudio();
  const viseme = lipsyncManager.viseme;
  // You can now use the viseme for your animation logic
  console.log(viseme);
};

analyzeAudio();
```

## Example

You can find a [complete example](https://github.com/wass08/wawa-lipsync/tree/main/examples/lipsync-demo) of how to use the library with Three.js and React Three Fiber in the `examples/lipsync-demo` directory of the repository.

> If you need help, join the [Discord server](https://wawasensei.dev/discord) or open an issue on the [GitHub repository](http://github.com/wass08/wawa-lipsync).

## Contributions

Contributions are welcome! If you have any ideas, suggestions, or improvements, feel free to open an issue or submit a pull request on the [GitHub repository](http://github.com/wass08/wawa-lipsync).

## License

This project is licensed under the MIT License. See the [LICENSE](https://github.com/wass08/wawa-lipsync/blob/main/LICENSE) for more details.
npm package: @selcip/react-scripts
Description: Custom config for Create React App.
Latest version: 1.1.4

# react-scripts

This package includes scripts and configuration used by [Create React App](https://github.com/facebookincubator/create-react-app).<br>
Please refer to its documentation:

* [Getting Started](https://github.com/facebookincubator/create-react-app/blob/master/README.md#getting-started) – How to create a new app.
* [User Guide](https://github.com/facebookincubator/create-react-app/blob/master/packages/react-scripts/template/README.md) – How to develop apps bootstrapped with Create React App.
npm package: @selco/digit-ui-module-hrms
Description: HRMS
Author: JaganKumar
Latest version: 1.0.1

<!-- TODO: update this -->

# digit-ui-module-hrms

## Install

```bash
npm install --save @selco/digit-ui-module-hrms
```

## Limitation

```bash
This Package is more specific to DIGIT-UI's can be used across mission's
```

## Usage

After adding the dependency make sure you have this dependency in

```bash
frontend/micro-ui/web/package.json
```

```json

"@selco/digit-ui-module-hrms":"^1.5.0",

```

then navigate to App.js

```bash
 frontend/micro-ui/web/src/App.js
```


```jsx
/** add this import **/

import { initHRMSComponents } from "@selco/digit-ui-module-hrms";

/** inside enabledModules add this new module key **/

const enabledModules = ["HRMS"];

/** inside init Function call this function **/

const initDigitUI = () => {
  initHRMSComponents();
};
```

### Changelog

```bash
1.8.0 workbench v1.0 release
1.8.0-beta.01 fixed compilation issue
1.8.0-beta workbench base version beta release
1.7.0 urban 2.9
1.6.0 urban 2.8
1.5.27 updated the readme content
1.5.26 some issue
1.5.25 corrected the bredcrumb issue
1.5.24 added the readme file
1.5.23 base version
```

### Contributors

[jagankumar-egov] [naveen-egov] [nipunarora-eGov] [Tulika-eGov] [Ramkrishna-egov] [vamshikrishnakole-wtt-egov] 

## Documentation

Documentation Site (https://core.digit.org/guides/developer-guide/ui-developer-guide/digit-ui)

## Maintainer

- [jagankumar-egov](https://www.github.com/jagankumar-egov)


### Published from DIGIT Frontend 
DIGIT Frontend Repo (https://github.com/egovernments/Digit-Frontend/tree/master)

![Logo](https://s3.ap-south-1.amazonaws.com/works-dev-asset/mseva-white-logo.png)
npm package: @selco/digit-ui-react-components
Description: <!-- TODO: update this -->
Author: JaganKumar
Latest version: 1.8.0



<!-- TODO: update this -->

# digit-ui-react-components

## Install

```bash
npm install --save @egovernments/digit-ui-react-components
```

## Limitation

```bash
This Package is more specific to DIGIT-UI's can be used across mission's
```

## Usage

After adding the dependency make sure you have this dependency in

```bash
frontend/micro-ui/web/package.json
```

```json
"@egovernments/digit-ui-react-components":"1.5.24",
```

then navigate to App.js

```bash
 frontend/micro-ui/web/src/App.js
```

Syntax for importing any component;

```jsx
import React, { Component } from "react";
import MyComponent from "@egovernments/digit-ui-react-components";

class Example extends Component {
  render() {
    return <MyComponent />;
  }
}
```
Syntax for the Inbox Composers

```jsx
    import { InboxSearchComposer } from "@egovernments/digit-ui-react-components";

    <React.Fragment>
      <Header className="works-header-search">{t(updatedConfig?.label)}</Header>
      <div className="inbox-search-wrapper">
        <InboxSearchComposer configs={updatedConfig}></InboxSearchComposer>
      </div>
    </React.Fragment>
```

Syntax for the FormComposersV2

```jsx
    import { FormComposerV2 as FormComposer } from "@egovernments/digit-ui-react-components";

   <React.Fragment>
      <Header >{t("CREATE_HEADER")}</Header>
      <FormComposer
        label={t("PROCEED")}
        config={configs.map((config) => {
          return {
            ...config,
            body: config.body.filter((a) => !a.hideInEmployee),
          };
        })}
        defaultValues={sessionFormData}
        onFormValueChange={onFormValueChange}
        onSubmit={onFormSubmit}
        fieldStyle={{ marginRight: 0 }}
        className="form-no-margin"
        labelBold={true}
      />
    </React.Fragment>
```
 

### Changelog

```bash
1.8.0 workbench v1.0 release
1.8.0-beta workbench base version beta release
1.7.0 urban 2.9
1.6.0 urban 2.8
1.5.36 added classname for topbar options
1.5.35 aligment issue in edit and logout
1.5.34 updated login scss and alignment issues
1.5.28 passing response data in case for custom component in inbox composer
1.5.27 integrated with the svg library
1.5.26 fixed shipping truck icon fill issue
1.5.25 added new icon and fixed other issues
1.5.24 added and updated the Readme file
1.5.23 base version
```

### Contributors

[jagankumar-egov] [nipunarora-eGov] [Tulika-eGov] [Ramkrishna-egov] [nabeelmd-eGov] [anil-egov] [vamshikrishnakole-wtt-egov] 

## Documentation

Documentation Site (https://core.digit.org/guides/developer-guide/ui-developer-guide/digit-ui)

## Maintainer

- [jagankumar-egov](https://www.github.com/jagankumar-egov)


### Published from DIGIT Frontend 
DIGIT Frontend Repo (https://github.com/egovernments/Digit-Frontend/tree/master)


![Logo](https://s3.ap-south-1.amazonaws.com/works-dev-asset/mseva-white-logo.png)
npm package: @selco/installation-ui-css
Description: ## Install
Author: Adithya Katuku
Latest version: 1.0.21



# digit-ui-css

## Install

```bash
npm install --save @egovernments/digit-ui-css
```

## Limitation

```bash
This Package is more specific to DIGIT-UI's can be used across mission's
It is the base css for all Digit UI's
```

## Usage

After adding the dependency make sure you have this dependency in

```bash
frontend/micro-ui/web/package.json
```

```json
"@egovernments/digit-ui-css":"1.8.14",
```

then navigate to App.js

```bash
frontend/micro-ui/web/public/index.html
```

```jsx
/** add this import **/

  <link rel="stylesheet" href="https://unpkg.com/@egovernments/digit-ui-css@1.5.22/dist/index.css" />

```
## Changelog

1.8.2-beta.24: added css for custom error component
1.8.2-beta.23: fixed css in pgr citizen complaint detail page
1.8.2-beta.24  added css for the side component

### Summary for Version [1.8.2-beta.1] - 2024-06-05

For a detailed changelog, see the [CHANGELOG.md](./CHANGELOG.md) file.


## Contributors

[jagankumar-egov] [nipunarora-eGov] [Tulika-eGov] [Ramkrishna-egov] [nabeelmd-eGov] [anil-egov] [vamshikrishnakole-wtt-egov] 

### Published from DIGIT Frontend 
DIGIT Frontend Repo (https://github.com/egovernments/Digit-Frontend/tree/develop)

## License

MIT © [jagankumar-egov](https://github.com/jagankumar-egov)
npm package: @selco/selco-css
Description: ## Install
Author: Jagankumar
Latest version: 1.8.28

<!-- TODO: update this -->

# digit-ui-css

## Install

```bash
npm install --save @egovernments/digit-ui-css
```

## Limitation

```bash
This Package is more specific to DIGIT-UI's can be used across mission's
It is the base css for all Digit UI's
```

## Usage

After adding the dependency make sure you have this dependency in

```bash
frontend/micro-ui/web/package.json
```

```json
"@egovernments/digit-ui-css":"^1.5.0",
```

then navigate to App.js

```bash
frontend/micro-ui/web/public/index.html
```

```jsx
/** add this import **/

  <link rel="stylesheet" href="https://unpkg.com/@egovernments/digit-ui-css@1.5.22/dist/index.css" />

```
### Changelog

```bash
1.8.0 Workbench v1.0
1.8.0-beta.13 fixed the login text styling issue
1.8.0-beta.1 styles for login dropdown and homepage dropdowns
1.8.0-beta added workbench related css and some new Digit v2 constants based on em
1.7.0 urban 2.9
1.6.0 urban 2.8
1.5.41 added styles for login dropdown and homepage dropdowns
1.5.40 aligment issue in edit and logout
1.5.39 updated login scss and alignment issues
1.5.37 updated the readme content
1.5.36 enhanced the formcomposer with header attribute
1.5.35 Fixed the card css issues
1.5.34 Fixed breadcrumb styling issue
1.5.33 fixed some card related css issues due to v2 css
1.5.32 newer css DIGITv2 added and corrected few existing issues
1.5.31 Corrected the CSS for inbox composers and default core ui
1.5.30 Updated the css for dynamic drodown filter dss
1.5.29 layout issues fixed
1.5.28 Horizontal Bar chart alignment fixes
1.5.27 DSS UI alignment fixes for Horizontal Metric and bar chart
1.5.26 added new css class for dss enhancements
1.5.25 added the css of inbox search composers
1.5.24 added the readme file
1.5.23 base version
```
## Contributors

[jagankumar-egov] [nipunarora-eGov] [Tulika-eGov] [Ramkrishna-egov] [nabeelmd-eGov] [anil-egov] [vamshikrishnakole-wtt-egov] 

### Published from DIGIT Frontend 
DIGIT Frontend Repo (https://github.com/egovernments/Digit-Frontend/tree/master)

## License

MIT © [jagankumar-egov](https://github.com/jagankumar-egov)
npm package: @selderee/plugin-htmlparser2
Description: selderee plugin - selectors decision tree builder for htmlparser2 DOM.
Author: KillyMXI
Latest version: 0.12.0

# selderee

![lint status badge](https://github.com/mxxii/selderee/workflows/lint/badge.svg)
![test status badge](https://github.com/mxxii/selderee/workflows/test/badge.svg)
[![License: MIT](https://img.shields.io/badge/license-MIT-green.svg)](https://github.com/mxxii/selderee/blob/main/LICENSE)

[selderee](https://github.com/mxxii/selderee) plugin - selectors decision tree builder for [htmlparser2](https://github.com/fb55/htmlparser2) DOM AST.

(Technically, the package depends not on `htmlparser2` but on [domhandler](https://github.com/fb55/domhandler), underlying package of `htmlparser2`.)

----

[Changelog](https://github.com/mxxii/selderee/blob/main/packages/plugin-htmlparser2/CHANGELOG.md).

See [main README file](https://github.com/mxxii/selderee/blob/main/README.md) for more info.
npm package: @seldszar/vue-entry-loader
Description: Yet another Vue entry loader for Webpack
Author: Alexandre Breteau
Latest version: 1.1.0

# @seldszar/vue-entry-loader

> Yet another Vue entry loader for Webpack

## Table of Contents

- [Install](#install)
- [Usage](#usage)
- [Author](#author)
- [License](#license)

# Install

```bash
$ npm install @seldszar/vue-entry-loader
```

# Usage

```javascript
const { VueEntryPlugin } = require('@seldszar/vue-entry-loader');

module.exports = {
	module: {
		rules: [
			{
				test: /\.vue$/,
				loader: 'vue-loader'
			}
		]
	},
	plugins: [new VueLoaderPlugin(), new VueEntryPlugin()]
};
```

## Author

Alexandre Breteau - [@0xSeldszar](https://twitter.com/0xSeldszar)

## License

MIT © [Alexandre Breteau](https://seldszar.fr)
npm package: @seldszar/yael
Description: Yet another entry loader for Webpack
Author: Alexandre Breteau
Latest version: 2.2.0

# @seldszar/yael

> Yet another entry wrapper for Webpack

## Table of Contents

- [Install](#install)
- [Usage](#usage)
- [API](#api)
- [Author](#author)
- [License](#license)

# Install

```bash
$ npm install @seldszar/yael
```

# Usage

Let's consider the following project structure using Vue.js:

```
src/
├── entry-template.js
└── app.vue
```

Here's the `webpack.config.js` configuration:

```javascript
const { VueLoaderPlugin } = require('vue-loader');

module.exports = {
	entry: './src/app.vue',
	module: {
		rules: [
			{
				test: /\.vue$/,
				loader: 'vue-loader'
			}
		]
	},
	plugins: [
		new VueLoaderPlugin()
	]
};
```

In `src/entry-template.js`, export a function taking the original entry & the context as arguments:

```javascript
import { createApp } from 'vue';

export default (App, { target }) => {
	const app = createApp(App, {
		message: 'Hello World'
	});

	if (target === 'web') {
		app.mount('#app');
	}

	return app;
};
```

## Using the wrapper

If you prefer a more granular approach, you can manually apply with `wrapEntry`:

```javascript
const { wrapEntry } = require('@seldszar/yael');

module.exports = {
	entry: wrapEntry('./src/app.vue', {
		template: './src/entry-template.js'
	}),
	// ...
};
```

## Using the plugin

Register the plugin in your Webpack configuration and set the `template` path:

```javascript
const { EntryWrapperPlugin } = require('@seldszar/yael');

module.exports = {
	// ...
	plugins: [
		// ...
		new EntryWrapperPlugin({
			template: './src/entry-template.js'
		})
	]
};
```

## API

See the [declaration file](./index.d.ts).

## Author

Alexandre Breteau - [@0xSeldszar](https://twitter.com/0xSeldszar)

## License

MIT © [Alexandre Breteau](https://seldszar.fr)