open-index/open-npm huggingface dataset:
npm package: @jordandavila/tailwind-fluid
Description: Figma-accurate fluid sizing utilities for Tailwind via clamp() and per-breakpoint scaling.
Author: Jordan Davila
Latest version: 0.1.1


# @jordandavila/tailwind-fluid

Figma-accurate fluid sizing utilities for Tailwind via `clamp()` and per-breakpoint scaling.
Provide a **`screens`** object and get semantic classes like `text-fluid-16`, `text-fluid-16/24`, `px-fluid-12`, `max-w-fluid-[720]`, etc.

## Install
```bash
npm i -D @jordandavila/tailwind-fluid
# or
pnpm add -D @jordandavila/tailwind-fluid
```

## Setup
```ts
// tailwind.config.ts
import { tailwindFluid } from '@jordandavila/tailwind-fluid'

export default {
  content: ['./src/**/*.{ts,tsx,js,jsx,html,njk}'],
  plugins: [
    tailwindFluid({
      screens: {
        mobile:  { figma: 375,  viewport: 375 },
        tablet:  { figma: 768,  viewport: 768 },
        desktop: { figma: 1560, viewport: 1024 },
        max:     { figma: 1560, viewport: 1560 }
      }
    })
  ]
}
```

### What the plugin does
- Injects per-breakpoint root vars (`--viewport`, `--scale`, `--min-width`, `--max-width`, `--figma-screen-width`) so **`calc(var(--scale) * px)`** equals the Figma px at that breakpoint and scales in-between.
- Extends Tailwind `theme.screens` from your `screens` so media queries and scaling use the same cutoffs.

## Class grammar
- **Typography**
  - `text-fluid-16` → `font-size: calc(var(--scale) * 16px)`
  - `text-fluid-16/24` → `font-size: clamp(1rem, …, 1.5rem)` (min/max in **px**; rem emitted)
  - `leading-fluid-18/28` → line-height clamp
- **Spacing**
  - `p-fluid-24`, `px-fluid-12`, `py-fluid-8`
  - `m-fluid-16`, `mx-fluid-12`, `my-fluid-20`
  - `gap-fluid-12`, `space-x-fluid-12`, `space-y-fluid-16`
- **Sizing**
  - `w-fluid-320`, `h-fluid-200`, `min-w-fluid-240`, `max-w-fluid-[720]`, etc.
- **Transforms**
  - `translate-x-fluid-8`, `translate-y-fluid-12`

Values are plain numbers in **px** (`8` → 8px). Use a slash for ranges `min/max` (e.g., `38/58`).

## Options
```ts
interface FluidPluginOptions {
  screens: Record<string, { figma: number; viewport: number }>
}
```

- **figma**: The design width for that breakpoint.
- **viewport**: The real viewport breakpoint (media query) boundary.

## Example
```html
<h1 class="text-fluid-38/58 leading-fluid-44/64 max-w-fluid-[720]">
  Fluid typography that matches Figma at each breakpoint
</h1>
<p class="text-fluid-16/22 mt-fluid-12 max-w-fluid-[720] opacity-80">
  Scales between your min/max screens with `clamp()`, then locks to a fixed size at max.
</p>
```

## License
MIT © 2025 Jordan Davila
npm package: @jordandelcros/stats-js
Description: This class is a rework of the original stats.js from mrdoob, it use a single canvas unlike the original that use DOM elements.
Author: Jordan Delcros
Latest version: 1.0.5

[![npm version](https://badge.fury.io/js/%40jordandelcros%2Fstats-js.svg)](https://www.npmjs.com/package/@jordandelcros/stats-js)

# stats.js #

#### JavaScript Performance Monitor ####

This class is a rework of the original `stats.js` from mrdoob.

It use a single canvas unlike the original that use DOM elements.

So, it provides a simple info box that will help you monitor your code performance.

* **FPS** Frames rendered in the last second. The higher the number the better.
* **MS** Milliseconds needed to render a frame. The lower the number the better.
* **MB** MBytes of allocated memory. (Run Chrome with `--enable-precise-memory-info`)
* **PING** Milliseconds needed to ask request something to the server. The lower the number the better.

### Screenshots ###

![fps.png](https://rawgit.com/JordanDelcros/stats-js/master/assets/screenshot-fps.png)
![ms.png](https://rawgit.com/JordanDelcros/stats-js/master/assets/screenshot-ms.png)
![mb.png](https://rawgit.com/JordanDelcros/stats-js/master/assets/screenshot-mb.png)
![ping.png](https://rawgit.com/JordanDelcros/stats-js/master/assets/screenshot-ping.png)

### NPM ###

```bash
	npm install @jordandelcros/stats-js
```

### Usage ###

`Stats([realTime]);`

```javascript
var stats = new Stats(false);

document.body.appendChild(stats.domElement););

function update() {

  window.requestAnimationFrame(update);

	stats.begin();

	// monitored code goes here

	stats.end();

};

window.requestAnimationFrame(update);
```

to get the **PING** you need to call special methods into server's requests:

```javascript
// ...

function fakeServerRequest(){

	// Call on server request send
	stats.beginPing();

	// Fake server latency
	setTimeout(function(){

		// Call on server request response
		stats.endPing();
		fakeServerRequest();

	}, 65);

};

fakeServerRequest();

// ...
```
npm package: @jordanebachelet/xml-split
Description: Split a large XML file into smaller chunks based on the given options
Author: Jordane BACHELET
Latest version: 1.1.4

# XML Split #

[![Coverage Status](https://coveralls.io/repos/bitbucket/jordanebachelet/xml-split/badge.svg?branch=master)](https://coveralls.io/bitbucket/jordanebachelet/xml-split?branch=master)
[![NPM version](https://img.shields.io/npm/v/@jordanebachelet/xml-split.svg)](https://www.npmjs.com/package/@jordanebachelet/xml-split)

## Installation

* Go to the directory where you cloned the repository.
* Run `npm install @jordanebachelet/xml-split`.

## How to use
### Through command line interface
You can run the `npm link` command before using this tool. This will allows you to directly run the `xmlsplit` command in your command line.

Then, you can run the following commands:
```bash
# without npm link
node bin/cli.js split path/to/big/xml/file.xml "child_node" -s 10 -p ".part_" -c 0

# with npm link
xmlsplit split path/to/big/xml/file.xml "child_node" -s 10 -p ".part_" -c 0
```
This command will split the given XML file into chunks of 10 Mb files, renamed as file.part_0.xml, file.part_1.xml, file.part_2.xml ...

### Through the Javascript interface
You can use this tool directly in your NodeJS scripts.

The `split` method returns a native [Promise](https://developer.mozilla.org/fr/docs/Web/JavaScript/Reference/Objets_globaux/Promise) so you can do some work after the method.

Hereafter how to integrate this tool in your scripts:
```javascript
const xmlSplit = require('xml-split');

xmlSplit.split('path/to/big/xml/file.xml', 'child_node', {
    size: 10,
    pattern: '.part_',
    counter: 0
}).then(() => {
    console.log('split complete');
});
```
## API Reference

Please check the docs folder [here](https://bitbucket.org/jordanebachelet/xml-split/src/master/docs/).