open-index/open-npm huggingface dataset:
npm package: @numpod/excel-ent
Description: The purpose of this lib is to help you export data in Excel and CSV.
Author: Leonardo R. Dias
Latest version: 2.0.5
Deprecated: WARNING: This project has been renamed to just *excel-ent*. Install using *npm install excel-ent* instead.


# Excel-ent

<p align="left">
  <a href="#" target="blank"><img src="https://i.imgur.com/vkTQF5g.jpg" width="100" alt="NUMPOD" /></a>
</p>

[![NPM](https://img.shields.io/npm/v/@numpod/excel-ent)](https://www.npmjs.com/package/@numpod/excel-ent)
[![npm](https://img.shields.io/npm/l/@numpod/excel-ent)](https://github.com/leoreisdias/excel-ent/blob/main/LICENSE)

## Description

[excel-ent](https://github.com/leoreisdias/excel-ent.git) is a helper lib to export data in XLS and CSV.

## Installation

```bash
$ yarn add @numpod/excel-ent

# or with npm

$ npm install @numpod/excel-ent --save
```

## Using excel-ent

Two main functions <b>exportmeExcel</b> & <b>exportmeToCsv</b> 

### exportmeExcel

exportmeExcel(data: any[], title: string, options?: CSS.Properties)

#### Parameters

`data`
Required, must be an array of Object

`title`
Required, name of the archive generated

`options`
Optional, receives two attributes: <i>bodyStyle</i> and <i>headerStyle</i>

- `bodyStyle` and `headerStyle`: Both receives CSS Properties in <b>camelCase</b> and provide style for the header and body in the Excel File

### Example

```js
import { exportmeExcel } from "@numpod/excel-ent";

const data = [
  {
    id: 1,
    name: 'Some Name',
    age: 21,
  },
  {
    id: 2,
    name: 'Some New Name',
    age: 23,
  },
  {
    id: 3,
    name: 'Some Name Again',
    age: 22,
  },
];

exportmeExcel(data, 'test', {
  bodyStyle: { fontSize: '20px' },
  headerStyle: { fontSize: '40px' },
});

```

### Example output
<img src="./excel-ent-example.png" alt="Example Output - Excel Screenshot" />

---

### exportmeToCsv

exportmeToCsv(data: any[], title: string)

### Parameters

`data`
Required, must be an array of Object

`title`
Required, name of the archive generated

### Example

```js
import { exportmeToCsv } from "@numpod/excel-ent";

const data = [
  {
    id: 1,
    name: "Some Name",
    age: 21,
  },
  {
    id: 2,
    name: "Some New Name",
    age: 23,
  },
  {
    id: 3,
    name: "Some Name Again",
    age: 22,
  },
];

exportmeToCSV(data, "MyReport");

```
---
```fix
Last fux
```

---

## License

@numpod/excel-ent is [MIT licensed](LICENSE).

---

## Thank you and be free to contribute.
npm package: @numpy-node/darwin-arm64
Description: numpy-node native binary for macOS ARM64 (Apple Silicon)
Latest version: 0.2.0

# @numpy-node/darwin-arm64

Native binary for numpy-node on macOS ARM64 (Apple Silicon).

This package is installed automatically by `numpy-node` - you don't need to install it directly.

## About

This package contains the pre-built native addon for macOS on Apple Silicon (M1/M2/M3).

See the main package for documentation: [numpy-node](https://www.npmjs.com/package/numpy-node)
npm package: @numpy-node/darwin-x64
Description: numpy-node native binary for macOS x64 (Intel)
Latest version: 0.1.0

# @numpy-node/darwin-arm64

Native binary for numpy-node on macOS x64 (Intel).

This package is installed automatically by `numpy-node` - you don't need to install it directly.

## About

This package contains the pre-built native addon for macOS on Intel Macs.

See the main package for documentation: [numpy-node](https://www.npmjs.com/package/numpy-node)
npm package: @numpy-node/linux-arm64
Description: numpy-node native binary for Linux ARM64
Latest version: 0.2.0

# @numpy-node/darwin-arm64

Native binary for numpy-node on Linux ARM64.

This package is installed automatically by `numpy-node` - you don't need to install it directly.

## About

This package contains the pre-built native addon for Linux on ARM64 (aarch64).

See the main package for documentation: [numpy-node](https://www.npmjs.com/package/numpy-node)
npm package: @numpy-node/linux-x64
Description: numpy-node native binary for Linux x64
Latest version: 0.2.0

# @numpy-node/darwin-arm64

Native binary for numpy-node on Linux x64.

This package is installed automatically by `numpy-node` - you don't need to install it directly.

## About

This package contains the pre-built native addon for Linux on x86_64.

See the main package for documentation: [numpy-node](https://www.npmjs.com/package/numpy-node)
npm package: @numpy-node/win32-x64
Description: numpy-node native binary for Windows x64
Latest version: 0.2.0

# @numpy-node/darwin-arm64

Native binary for numpy-node on Windows x64.

This package is installed automatically by `numpy-node` - you don't need to install it directly.

## About

This package contains the pre-built native addon for Windows on x86_64.

See the main package for documentation: [numpy-node](https://www.npmjs.com/package/numpy-node)
npm package: @numquid/route-mounter
Description: Utility that mounts routers in an Express.js app
Author: Ochuko
Latest version: 1.0.1

# route-mounter

Utility to automatically mount Express routers from a specified routes location.

## Installation

```bash
npm i @numquid/route-mounter
```

### Usage

```javascript
// main.(js|ts) or app.(js|ts)

import express from "express";
import { mountRouters } from "route-mounter";

const app = express();

const basePath = "/api";
const myRoutesLocation = path.join(__dirname, "the-folder-that-contain-my-routes")

mountRouters(app, myRoutesLocation, { basePath });


```

### Sample folder structure expected:

```javascript

src/routes/
  home/
    homeRouter.ts
  users/
    usersRouter.ts
  EveryDayIsRouter/
    EveryDayIsRouter.ts
  demoRoutes/
    routes.ts
  about-us/
    index.ts
  GloriousDay/
    ThisDayIsGlorious.ts

```
Taking the last route from the above sample; the same would be loaded as:

```javascript
http://localhost:4000/api/this-day-is-glorious
```


### ⚠️ Important Notes on Automatic Route Path Generation

The route path that each router is mounted to is automatically derived from its file or folder name.  
This helps you keep your routes organized while maintaining a predictable, human-readable structure.

#### 1. Single-file routers (PascalCase filenames)
If your router file name is written in PascalCase (e.g. `GloriousDay/ThisDayIsGlorious.ts`),  
it will be converted to a **kebab-case** route path:

```javascript
/GloriousDay/ThisDayIsGlorious.ts  →  /this-day-is-glorious
```

#### 2. Routers defined in an index.ts file
If your router file is named index.ts, the parent folder name becomes the route path:

```javascript
/about-us/index.ts  →  /about-us
```

#### 3. Routers defined in a custom file (not index.ts)
If the router is in a folder but not named index.ts, the folder name becomes the route path (converted to kebab-case):

```javascript
/demoRoutes/routes.ts  →  /demo-routes
```

#### 4. Root-level routers
f a router file is located at the root of your routes directory (e.g. home/homeRouter.ts),
it will mount to / unless a specific prefix or folder name dictates otherwise:

```javascript
/home/homeRouter.ts  →  /
```

#### 5. General behavior
- All route paths are normalized to lowercase kebab-case.
- Folder and file names determine the route path hierarchy automatically.
- No manual route prefixing is needed unless you want to override the defaults.
npm package: @numso/eslint-plugin-import
Description: A fork that adds sorting and --fix
Author: Ben Mosher
Latest version: 1.14.0

# eslint-plugin-import

This is a fork of [Ben Mosher's fantastic plugin](https://github.com/benmosher/eslint-plugin-import). You probably want to install that one instead.

I love what eslint-plugin-import gives us, but I want more granular sorting of my imports. Hopefully I'll soon have time to clean this up and do a proper PR back into the main library (if it's wanted).

### --fix

I implemented some very basic --fix functionality for the import/order rule. It's only available when you set `fixable:true`. USE AT YOUR OWN RISK:

- It hasn't been tested very thoroughly
- When fixable is true, some of the eslint flags are hard coded
- When this fix is run with other fixes (notably, object-curly), bad things can happen:

If your code snippet looks like this:

```
import foo from 'foo'
import {bar} from 'bar'
```

After fix it could end up looking like this:

```
import {bar} from 'bar'
import { bar } from 'bar'
```

In this case, the import/order fix ran first, switching foo and bar. Then the object-curly fix ran, replacing line 2 with a duplicate of what line 2 used to be, but with spaces in it.