open-index/open-npm huggingface dataset:
npm package: @gayathrisubramani/custompromise
Description: custom implementation of javascript promise
Author: Gayathri
Latest version: 1.0.0

# CustomPromise

Custom implementation of JavaScript Promise with:

- `.then()`, `.catch()`, `.finally()`  
- `MyPromise.all()`  
- `MyPromise.race()`

## Installation

```bash
npm install custompromise

## Usage
const MyPromise = require('custompromise');

// Example 1: Basic usage
const p = new MyPromise((resolve, reject) => {
  setTimeout(() => resolve(42), 1000);
});

p.then(value => console.log("Resolved:", value))
 .catch(err => console.error("Error:", err))
 .finally(() => console.log("Done!"));

// Example 2: MyPromise.all
MyPromise.all([
  new MyPromise(res => setTimeout(() => res(10), 500)),
  new MyPromise(res => setTimeout(() => res(20), 1000)),
  new MyPromise(res => setTimeout(() => res(30), 1500))
]).then(values => console.log("All resolved:", values));

// Example 3: MyPromise.race
MyPromise.race([
  new MyPromise(res => setTimeout(() => res("First!"), 500)),
  new MyPromise(res => setTimeout(() => res("Second!"), 1000))
]).then(value => console.log("Race winner:", value));
npm package: @gayatritakawale/resume
Description: Gayatri Takawale's Resume
Author: Gayatri Takawale
Latest version: 1.0.2

# 🧾 @gayatritakawale/resume

> A command-line version of my resume — just run and read in your terminal!

---

## 📦 Installation & Usage

You don’t need to install anything globally.

Just run:

```bash
npx @gayatritakawale/resume
```

That’s it! You'll see a clean, colorful version of my resume right in your terminal.

---

## 💁‍♀️ About Me

Hi, I’m **Gayatri Takawale** — a frontend-focused full-stack developer who loves clean UI, structured code, and solving real-world problems.

🔗 [LinkedIn](https://linkedin.com/in/gayatritakawale)  
🌐 [Portfolio](https://gayatri--takawale.web.app/)  
💻 [GitHub](https://github.com/Gayatri3012)

---

## ✨ Highlights

- 📄 Built with Node.js and Chalk
- 🎨 Terminal-formatted resume
- 🔧 Includes experience, projects, skills, and education
- 🧪 Lightweight and easy to use with `npx`

---

## 🔒 License

MIT © Gayatri Takawale
npm package: @gaysianbb/tsc-files
Description: A tiny tool to run tsc on specific files without ignoring tsconfig.json
Author: Gustavo P. Cardoso
Latest version: 0.0.0

# tsc-files

![GitHub Workflow Status](https://img.shields.io/github/workflow/status/gustavopch/tsc-files/Release?style=flat-square)

A tiny tool to run `tsc` on specific files without ignoring `tsconfig.json`.

## Installation

```sh
npm i -D tsc-files
```

```sh
yarn add -D tsc-files
```

## Why

I wanted to type-check **only the staged files** with [lint-staged](https://github.com/okonet/lint-staged).

Unfortunately passing specific files like `tsc --noEmit file1.ts file2.ts` will cause TypeScript to simply ignore your `tsconfig.json`.

There's already an open issue in the TypeScript repo to support this use case — you may want to give a 👍 there: https://github.com/microsoft/TypeScript/issues/27379

## Usage

With lint-staged:

```json
{
  "lint-staged": {
    "**/*.ts": "tsc-files --noEmit"
  }
}
```

## How it works

For the most part, it just forwards all arguments to `tsc` with one exception: the specified files will not be forwarded — instead, they will be put at the `files` property of a temporary config that will be generated next to your original `tsconfig.json`. Other than that, just read `tsc --help`.

## License

Released under the [MIT License](./LICENSE.md).
npm package: @gazatu/solid-select
Description: The Select component for Solid.
Author: Martin Pengelly-Phillips
Latest version: 0.13.1

<a href="https://solid-select.com">
    <img
      alt="Solid Select- The Select component for Solid."
      src="./resources/solid-select-1.png">
  </a>

- **Built for [Solid](https://solidjs.com/):** leverages fine-grained reactivity
  primitives for coordination.
- **Flexible:** built to support a wide range of cases, from single selects to
  multi-select autocomplete lists.
- **Extendable:** use the pre-fabricated components or build your own from the
  core primitives.
- **Zero dependencies:** Just pair with Solid and good to go.

![solid select preview](./resources/solid-select-preview.gif?raw=true)

## How do I get started? 🧭

Install it:

```bash
npm install @thisbeyond/solid-select
```

Use it:

```jsx
import { Select } from "@thisbeyond/solid-select";
import "@thisbeyond/solid-select/style.css";

const App = () => {
  return (
    <div>
      <Select options={["apple", "banana", "pear", "pineapple", "kiwi"]} />
    </div>
  );
};

export default App;
```

See more examples at https://solid-select.com

## What's implemented? ✔️

- [x] A high level `Select` component that can be configured with either a
  static or dynamic list of options.
- [x] Support for single value selection or multiple value selection.
- [x] `createOptions` helper for configuring filterable options based on input
  value (complete with match highlighting). Works with lists of plain strings or
  can be passed a 'key' to filter against lists of objects. Can also be used to
  configure creating new options on the fly.
- [x] Opt-in sensible default styling. Customise easily or style from scratch.
- [x] Composable building blocks to create your own control.
- [x] Lower level `createSelect` primitive if you just want the core logic.

## Who made this? ✍

[Martin Pengelly-Phillips](https://twitter.com/thesociablenet)

## Why did you make it?

I've been part of the [SolidJS community](https://discord.com/invite/solidjs)
for a while now and one of the things I really like is the emphasis on trying
things out and sharing them (https://hack.solidjs.com). The ecosystem is small
which creates a lot of opportunity and a lower barrier to entry for sharing I
find.

I published my first Solid library (https://solid-dnd.com) a short while back as
a first dabble in sharing what I had learnt on a personal project. That went
well so when I had to create a multi-select autocomplete control for another
personal project I knew I'd be sharing that too - and so `Solid Select` came to
be :)
npm package: @gazatu/solid-spectre
Description: Solid.js components styled with Spectre.css
Author: GaZaTu
Latest version: 1.6.3

<p>
  <img width="100%" src="https://assets.solidjs.com/banner?type=solid-spectre&background=tiles&project=%20" alt="solid-spectre">
</p>

# solid-spectre

Solid.js components styled with Spectre.css

## Quick start

Install it:

```bash
npm i @gazatu/solid-spectre
```

Use it:

```tsx
import {} from "solid-spectre"
```
npm package: @gazdagandras/express-sse
Description: An Express middleware for Server-Sent Events (EventSource)
Author: Dino Paskvan
Latest version: 0.5.7

express-sse
============

[![npm version](https://badge.fury.io/js/express-sse.svg)](https://badge.fury.io/js/express-sse)  [![Build Status](https://travis-ci.org/dpskvn/express-sse.svg?branch=master)](https://travis-ci.org/dpskvn/express-sse)  [![Code Climate](https://codeclimate.com/github/dpskvn/express-sse/badges/gpa.svg)](https://codeclimate.com/github/dpskvn/express-sse)  [![codecov](https://codecov.io/gh/dpskvn/express-sse/branch/master/graph/badge.svg)](https://codecov.io/gh/dpskvn/express-sse)

[![NPM](https://nodei.co/npm/express-sse.png?downloads=true)](https://nodei.co/npm/express-sse/)

An Express middleware for quick'n'easy server-sent events.

## About
`express-sse` is meant to keep things simple. You need to send server-sent events without too many complications and fallbacks? This is the library to do so.

## Installation:
`npm install --save express-sse`

or

`yarn add express-sse`

## Usage example:
### Options:
You can pass an optional options object to the constructor. Currently it only supports changing the way initial data is treated. If you set `isSerialized` to `false`, the initial data is sent as a single event. The default value is `true`.

```js
var sse = new SSE(["array", "containing", "initial", "content", "(optional)"], { isSerialized: false, initialEvent: 'optional initial event name' });
```

### Server:
```js
var SSE = require('express-sse');
var sse = new SSE(["array", "containing", "initial", "content", "(optional)"]);

...

app.get('/stream', sse.init);

...

sse.send(content);
sse.send(content, eventName);
sse.send(content, eventName, customID);
sse.updateInit(["array", "containing", "new", "content"]);
sse.serialize(["array", "to", "be", "sent", "as", "serialized", "events"]);
```

### Client:
```js
var es = new EventSource('/stream');

es.onmessage = function (event) {
  ...
};

es.addEventListener(eventName, function (event) {
  ...
});
```
npm package: @gazelleswap/sdk
Description: 🛠 An SDK for building applications on top of Pancakeswap.
Latest version: 2.4.5

# Pancakeswap SDK

Forked from the [Uniswap SDK](https://github.com/Uniswap/uniswap-v2-sdk/commit/a88048e9c4198a5bdaea00883ca00c8c8e582605).

You can refer to the Uniswap SDK documentation [uniswap.org](https://docs.uniswap.org/sdk/2.0.0/).

## Running tests

To run the tests, follow these steps. You must have at least node v10 and [yarn](https://yarnpkg.com/) installed.

First clone the repository:

```sh
git clone https://github.com/pancakeswap/pancake-swap-sdk.git
```

Move into the pancakeswap-sdk working directory

```sh
cd pancakeswap-sdk/
```

Install dependencies

```sh
yarn install
```

Run tests

```sh
yarn test
```

You should see output like the following:

```sh
yarn run v1.22.4
$ tsdx test
 PASS  test/constants.test.ts
 PASS  test/pair.test.ts
 PASS  test/fraction.test.ts
 PASS  test/miscellaneous.test.ts
 PASS  test/entities.test.ts
 PASS  test/trade.test.ts

Test Suites: 1 skipped, 6 passed, 6 of 7 total
Tests:       3 skipped, 82 passed, 85 total
Snapshots:   0 total
Time:        5.091s
Ran all test suites.
✨  Done in 6.61s.
```
npm package: @gazwai/prettier-config
Description: My Personal config.
Author: Gary
Latest version: 1.0.2

# Team Lunaris Prettier config

Basic configuration for the Prettier code formatter we use here at Team Lunaris. 🧑‍💻

## Requirements

This package is for the Prettier code formatter. It can be installed in most modern text editors such as VSCode or Atom.

More information about the project can be found [here](https://prettier.io/).

## Usage

To install the package, run the following in your command line:

```bash
# Using npm

$ npm install -D @gazwai/prettier-config
```

```bash
# Using PNPM

$ pnpm add -D @gazwai/prettier-config
```

To set Prettier to use this config, add the following to your `package.json`:

```javascript
{
  // ...
  "prettier": "@gazwai/prettier-config",
  // ...
}
```
npm package: @gazzati/eslint-config-node
Description: ESLint + Prettier config for NodeJS applications
Author: Timur Gaazev
Latest version: 1.0.15

# ESLint + Prettier config for NodeJS applications

We use both eslint and prettier to lint our code:

* eslint is for code-quality.
* prettier is for formatting.

## Installation

```sh
yarn add --dev @gazzati/eslint-config-node
```

also add `eslint` if not already added
```
yarn add --dev eslint
```

Extend the shared eslint config in `.eslintrc.js`:

```js
// .eslintrc.js

module.exports = {
  extends: ["@gazzati/eslint-config-node"],
  rules: {
    // Specific project rules
  },
};
```

Extend the shared prettier config in `.prettierrc.js`:

```js
// .prettierrc.js

module.exports = require('@gazzati/eslint-config-node/.prettierrc')
```
npm package: @gazzati/react-dictionary
Description: Dictionary library for React
Author: gazzati
Latest version: 1.0.1

# Dictionary library for React App

## Installation

```sh
yarn add @gazzati/react-dictionary
```

## Usage

1. Wrap your root component in Dictionary from lib
2. Apply useDictionary hook where you need a translate

## Docs

Dictionary props

* `locales` - Array of locales(strings)
* `localStorageKey` - Browser storage key for save locale. Optional parameter

useDictionary methods

```js
const [locale, setNextLocale] = useDictionary()
```

## Example
https://github.com/gazzati/mysite
npm package: @gb-engineering/playthreejs-engine
Description: Engine for playthreejs
Latest version: 1.0.0-gb.3

# playthreejs
engine for graphics(2D, 3D)

## npm publish setting
### Configuring your npm client with your organization settings
* https://docs.npmjs.com/configuring-your-npm-client-with-your-organization-settings

1. Setting your organization scope for a single package<br>
```
$ cd /path/to/package
$ npm config set scope <org-name>
```

2. Setting package visibility to public for a single package<br>
```
$ npm config set access public
```

### Using private packages in a CI/CD workflow
* https://docs.npmjs.com/using-private-packages-in-a-ci-cd-workflow

1. Create access-token at npm for your account/organization

2. Create and check in a project-specific .npmrc file<br>
```
//registry.npmjs.org/:_authToken=${NPM_TOKEN}
```

## publish
npm publish
npm package: @gb-maps/core
Description: core package for gb-maps
Latest version: 0.1.5

# @gb-maps/core

![npm](https://img.shields.io/npm/v/@gb-maps/core)

Parsing library for [KML](https://developers.google.com/kml/documentation/kmlreference) and [OSM](https://wiki.openstreetmap.org/wiki/OSM_XML).

## Getting Started

> npm install @gb-maps/core

```TypeScript
import { convert } from '@gb-maps/core';

// some sample keyhole markup data
const kml = `<kml xmlns="http://www.opengis.net/kml/2.2">
<Document>
  <Folder>
    <name>Folder 1</name>
    <Placemark>
      <name>Place 1</name>
      <Point>
        <coordinates>-90.86,48.25,0</coordinates>
      </Point>
    </Placemark>
    <Placemark>
      <name>Place 2</name>
      <Point>
        <coordinates>-90.96,48.15,0</coordinates>
      </Point>
    </Placemark>
  </Folder>
</Document>
</kml>`;

// some sample open street maps data
const osm = `<?xml version='1.0' encoding='UTF-8'?>
<osm version='0.6'>
  <node id='300000001' visible='true' lat='34.07222' lon='-118.73425' />
  <node id='300000002' visible='true' lat='34.07234' lon='-118.73222' />
  <node id='300000003' visible='true' lat='34.06709' lon='-118.73467' />
  <node id='300000004' visible='true' lat='34.07245' lon='-118.73425' />
  <node id='300000005' visible='true' lat='34.06711' lon='-118.73647' />
  <node id='300000006' visible='true' lat='34.07222' lon='-118.73232' />
  <way id='way1'>
    <nd ref='300000003' />
    <nd ref='300000001' />
    <nd ref='300000005' />
    <tag k='name' v='Memorial Park' />
  </way>
</osm>`;

const doc = convert(osm)[0];

for (const path of doc.paths.values()) {
  for (const point of path.points.values()) {
    console.log(point);
  }
  for (const [k, v] of path.tags) {
    console.log(k, v);
  }
}

```
npm package: @gb-maps/parsers
Description: map parsing with kml and osm
Latest version: 0.1.5

# @gb-maps/parsers

![npm](https://img.shields.io/npm/v/@gb-maps/parsers)

Parsing library for [KML](https://developers.google.com/kml/documentation/kmlreference) and [OSM](https://wiki.openstreetmap.org/wiki/OSM_XML).

## Getting Started

> npm install @gb-maps/parsers

```TypeScript
import { convertKml, convertOsm } from '@gb-maps/parsers';

// some sample keyhold markup data
const kml = `<kml xmlns="http://www.opengis.net/kml/2.2">
<Document>
  <Folder>
    <name>Folder 1</name>
    <Placemark>
      <name>Place 1</name>
      <Point>
        <coordinates>-90.86,48.25,0</coordinates>
      </Point>
    </Placemark>
    <Placemark>
      <name>Place 2</name>
      <Point>
        <coordinates>-90.96,48.15,0</coordinates>
      </Point>
    </Placemark>
  </Folder>
</Document>
</kml>`;

// some sample open street maps data
const osm = `<?xml version='1.0' encoding='UTF-8'?>
<osm version='0.6'>
  <node id='300000001' visible='true' lat='34.07222' lon='-118.73425' />
  <node id='300000002' visible='true' lat='34.07234' lon='-118.73222' />
  <node id='300000003' visible='true' lat='34.06709' lon='-118.73467' />
  <node id='300000004' visible='true' lat='34.07245' lon='-118.73425' />
  <node id='300000005' visible='true' lat='34.06711' lon='-118.73647' />
  <node id='300000006' visible='true' lat='34.07222' lon='-118.73232' />
</osm>`;
const kmlDoc = convertKml(kml);
const osmDoc = convertOsm(osm);
kmlDoc.Document.Folder.forEach((folder) => {
  console.log(folder.name);
  folder.Placemark?.forEach((place) => {
    console.log(place.name, place.Point);
  });
});

osmDoc.node.forEach((n, i) => console.log(i, n.aid));

```

You should probably be using [the core library](https://www.npmjs.com/package/@gb-maps/core).
npm package: @gb-nx/browser
Description: This library was generated with [Nx](https://nx.dev).
Latest version: 8.6.0

# @gb-nx/browser

This library was generated with [Nx](https://nx.dev).

[![CI](https://img.shields.io/github/actions/workflow/status/GaryB432/gb-nx/main.yml?branch=master)](https://github.com/GaryB432/gb-nx/actions)
[![npm version](https://img.shields.io/npm/v/@gb-nx/browser?style=flat-square)](https://www.npmjs.com/package/@gb-nx/browser)

> Nx Plugin adding first class support for [Manifest V3](https://developer.chrome.com/docs/extensions/mv3/intro/) Browser Extension applications in your Nx workspace

## Features

Here is a list of some of the coolest features of the plugin:

- ✅ Generation of browser extensions applications
- ✅ Building, testing, etc your extension projects
- ✅ Packaging your extension projects for web stores

## Prerequisite

If you have not already, [create an Nx workspace](https://github.com/nrwl/nx#creating-an-nx-workspace) with the following:

```
# npm
npx create-nx-workspace@latest

# yarn
yarn create nx-workspace@latest
```

## Getting Started

Then you need to install the plugin in order to generate browser applications later on.

### Installing Plugin

```
npx nx add @gb-nx/browser
```

### Generating Project

Simply run the `extension` generator with the following command:

```
nx generate @gb-nx/browser:extension --name=my-extension --directory=apps/my-extension --projectNameAndRootFormat=as-provided
```

### Working with your Project

> nx run my-extension:build

Load (or reload) the unpacked extension from `dist/apps/my-extension` with `Manage Extensions` in your browser.

Refresh a browser page

Observe changes

Make changes to `my-extension\src`

Repeat

### Packaging your Project for Store Distribution

Run the `zip` target to create a versioned archive of your extension.

> nx run my-extension:build:production
> nx zip my-extension --tagGit false

## Migrations

This plugin supports Nx migrations and provides necessary version and code updates. So instead of bumping plugin version manually in package.json it's recommended to run `nx migrate @gb-nx/browser` command, that includes bumping the version of the @gb-nx/browser plugin, related dependencies and running code migrations.

## @gb-nx/browser & Nx Compatibility Chart

| @gb-nx/browser version | Nx version |
| ---------------------- | ---------- |
| ^8.0.0                 | >=17.0.0   |
| ^6.0.0                 | ^17.0.0    |
| ^5.0.0                 | ^16.0.0    |
| <5.0.0                 | ^15.0.0    |

### Useful resources

- [Developer Dashboard](https://chrome.google.com/webstore/developer/dashboard)
- [Chrome Web Store - Chrome Developers](https://developer.chrome.com/docs/webstore/?hl=en)
- [Chrome Web Store - Extensions](https://chrome.google.com/webstore/category/extensions)
- [Resize a PNG - Online PNG Maker](https://onlinepngtools.com/resize-png)

## License

MIT
npm package: @gb-nx/junit
Description: [![CI](https://img.shields.io/github/actions/workflow/status/GaryB432/gb-nx/main.yml?branch=master)](https://github.com/GaryB432/gb-nx/actions) [![latest](https://img.shields.io/npm/v/@gb-nx/junit/latest.svg)](https://www.npmjs.com/package/@gb-nx/junit) [
Latest version: 4.0.1

# gb-nx/junit

[![CI](https://img.shields.io/github/actions/workflow/status/GaryB432/gb-nx/main.yml?branch=master)](https://github.com/GaryB432/gb-nx/actions)
[![latest](https://img.shields.io/npm/v/@gb-nx/junit/latest.svg)](https://www.npmjs.com/package/@gb-nx/junit)
[![No Maintenance Intended](http://unmaintained.tech/badge.svg)](http://unmaintained.tech/)

> This plugin will add [Jest Junit Reporter](https://www.npmjs.com/package/jest-junit) to your [Nx](https://nx.dev/) project.

## ⚠️This plugin is deprecated

Please use [@gb-nx/workspace:junit](https://github.com/GaryB432/gb-nx/tree/master/packages/workspace#add-junit-reporter-to-a-nxjest-project) to add junit to your project.

## Prerequisite

If you have not already, [create an Nx workspace](https://github.com/nrwl/nx#creating-an-nx-workspace) with the following:

```
npx create-nx-workspace@latest
```

## Getting Started

### Install Plugin

```
# npm
npm install @gb-nx/junit --save-dev

# yarn
yarn add @gb-nx/junit --dev
```

### Add Junit reporter to your app

You will need to have an app in your workspace. You can create one with `nx g @nx/node:app my-app`.

```
nx g @gb-nx/junit:app my-app
```

## Generators (i.e. code generation)

### Application

`nx g @gb-nx/junit:app <project> [options]`

| Arguments   | Description                  |
| ----------- | ---------------------------- |
| `<project>` | The project to add junit to. |

| Options             | Default   | Description                                |
| ------------------- | --------- | ------------------------------------------ |
| `--tags`            | -         | Tags to use for linting (comma-delimited). |
| `--reporterVersion` | `^16.0.0` | The version of `junit-reporter` to use.    |
| `--skipFormat`      | `false`   | Skip formatting files.                     |

## Migrations

This plugin supports Nx migrations and provides necessary version and code updates. So instead of bumping plugin version manually in package.json it's recommended to run `nx migrate @gb-nx/junit` command, that includes bumping the version of the @gb-nx/junit plugin, related dependencies and running code migrations.

## @gb-nx/junit & Nx Compatibility Chart

| @gb-nx/junit version | Nx version |
| -------------------- | ---------- |
| ^4.0.0               | ^17.0.0    |
| ^3.0.0               | ^16.0.0    |
| <3.0.0               | ^15.0.0    |

## License

MIT