open-index/open-npm huggingface dataset:
npm package: @jafri/ecurve
Description: Elliptic curve cryptography
Latest version: 1.0.6

ecurve
=======

[![build status](https://secure.travis-ci.org/cryptocoinjs/ecurve.svg)](http://travis-ci.org/cryptocoinjs/ecurve)


JavaScript component for [Elliptic Curve Cryptography](http://en.wikipedia.org/wiki/Elliptic_curve_cryptography). Works in both Node.js and the browser.

Official documentation:

http://cryptocoinjs.com/modules/crypto/ecurve/


### LICENSE [MIT](LICENSE)
Parts of this software are derivative works of [`ec.js`](http://www-cs-students.stanford.edu/~tjw/jsbn/ec.js) by Tom Wu,  please see the MIT-like in [LICENSE](https://github.com/cryptocoinjs/ecurve/blob/ecd0f386024dba37bba40850b4ea6d1607f10e26/lib/point.js)
npm package: @jafri/eosio-asc
Description: Build tool for building AssemblyScript projects
Author: yjhmelody
Latest version: 0.1.117

# Transform

Compiling the `eosio-asc` smart contract code to generate as normal `as` code that can be directly compiled into wasm.

## Build

```sh
yarn build
```

<!-- TODO: we need to use pure ts code and remove the dist dir -->

## Example

```sh
npx asc path/to/examples/solar/solar.ts --transform ./index.ts  --noEmit
```

Note: You need to use the `asc` under transform module for `transform`, that is `./transform/node_modules/assemblyscript/bin/asc`

It generated a normal `as` file. And then you could compile it by `asc`.

You need set `--runtime stub` for compiling `as` code to smart contract environment.

Recommanded args are:

```sh
--importMemory --initialMemory 2 --maximumMemory 16 --noExportMemory --runtime stub --use abort= -O2
```
npm package: @jafri/eosio-transform
Description: Build tool for building AssemblyScript projects
Author: yjhmelody
Latest version: 0.0.21

# Transform

Compiling the `eosio-asc` smart contract code to generate as normal `as` code that can be directly compiled into wasm.

## Build

```sh
yarn build
```

<!-- TODO: we need to use pure ts code and remove the dist dir -->

## Example

```sh
npx asc path/to/examples/solar/solar.ts --transform ./index.ts  --noEmit
```

Note: You need to use the `asc` under transform module for `transform`, that is `./transform/node_modules/assemblyscript/bin/asc`

It generated a normal `as` file. And then you could compile it by `asc`.

You need set `--runtime stub` for compiling `as` code to smart contract environment.

Recommanded args are:

```sh
--importMemory --initialMemory 2 --maximumMemory 16 --noExportMemory --runtime stub --use abort= -O2
```
npm package: @jafri/named
Description: DNS server library for node.js
Author: trevoro
Latest version: 0.0.1

# node-named - DNS Server in Node.js

Node-named is a lightweight DNS server written in pure javascript. It has
limited support for the DNS spec, but aims to implement all of the *common*
functionality that is in use today. 



## Creating a DNS Server
```javascript
    var named = require('./lib/index');
    var server = named.createServer();
    var ttl = 300;

    server.listen(9999, '127.0.0.1', function() {
      console.log('DNS server started on port 9999');
    });

    server.on('query', function(query) {
      var domain = query.name();
      console.log('DNS Query: %s', domain)
      var target = new named.SOARecord(domain, {serial: 12345});
      query.addAnswer(domain, target, ttl);
      server.send(query);
    });
```
## Creating DNS Records

node-named provides helper functions for creating DNS records. 
The records are available under 'named.record.NAME' where NAME is one
of ['A', 'AAAA', 'CNAME', 'SOA', 'MX', 'TXT, 'SRV']. It is important to 
remember that these DNS records are not permanently added to the server. 
They only exist fo the length of the particular request. After that, they are
destroyed. This means you have to create your own lookup mechanism.
```javascript
    var named = require('node-named');
    
    var soaRecord = named.SOARecord('example.com', {serial: 201205150000});
    console.log(soaRecord);
```
### Supported Record Types

The following record types are supported

 * A (ipv4)
 * AAAA (ipv6)
 * CNAME (aliases)
 * SOA (start of authority)
 * MX (mail server records)
 * TXT (arbitrary text entries)
 * SRV (service discovery)

## Logging

node-named uses [http://github.com/trentm/node-bunyan](bunyan) for logging.
It's a lot nicer to use if you npm install bunyan and put the bunyan tool in
your path. Otherwise, you will end up with JSON formatted log output by default.

### Replacing the default logger

You can pass in an alternate logger if you wish. If you do not, then it will use
bunyan by default. Your logger must expose the functions 'info', 'debug',
'warn', 'trace', 'error', and 'notice'.

### TODO

 * Better record validation
 * Create DNS client for query recursor
 * Add support for PTR records
 * Add support for TCP AXFR requests

## Tell me even more...

When DNS was designed it was designed prior
to the web existing, so many of the features in the RFC are either never used,
or were never implemented. This server aims to be RFC compliant, but does not
implement any other protocol other than INET (the one we're all used to), and
only supports a handful of record types (the ones that are in use on a regular
basis).
npm package: @jafri/react-native-tcp
Description: node's net API for react-native
Author: Andy Prock
Latest version: 3.3.0

# TCP in React Native

node's [net](https://nodejs.org/api/net.html) API in React Native

This module is used by [Peel](http://www.peel.com/)

## Install

* Create a new react-native project. [Check react-native getting started](http://facebook.github.io/react-native/docs/getting-started.html#content)

* In your project dir:

```
npm install react-native-tcp --save
```

__Note for iOS:__ If your react-native version < 0.40 install with this tag instead:
```
npm install react-native-tcp@3.1.0 --save
```
## if using Cocoapods

Update the following line with your path to `node_modules/` and add it to your
podfile:

```ruby
pod 'TcpSockets', :path => '../node_modules/react-native-tcp'
```

## Link in the native dependency

```
react-native link react-native-tcp
```

## Additional dependencies

### Due to limitations in the react-native packager, streams need to be hacked in with [rn-nodeify](https://www.npmjs.com/package/rn-nodeify)

1. install rn-nodeify as a dev-dependency
``` npm install --save-dev rn-nodeify ```
2. run rn-nodeify manually
``` rn-nodeify --install stream,process,util --hack ```
3. optionally you can add this as a postinstall script
``` "postinstall": "rn-nodeify --install stream,process,util --hack" ```

## Usage

### package.json

_only if you want to write require('net') in your javascript_

```json
{
  "browser": {
    "net": "react-native-tcp"
  }
}
```

### JS

_see/run [index.ios.js/index.android.js](examples/rctsockets) for a complete example, but basically it's just like net_

```js
var net = require('net');
// OR, if not shimming via package.json "browser" field:
// var net = require('react-native-tcp')

var server = net.createServer(function(socket) {
  socket.write('excellent!');
}).listen(12345);

var client = net.createConnection(12345);

client.on('error', function(error) {
  console.log(error)
});

client.on('data', function(data) {
  console.log('message was received', data)
});
```

### TODO

add select tests from node's tests for net

PR's welcome!



_originally forked from [react-native-udp](https://github.com/tradle/react-native-udp)_
npm package: @jafri/vert
Description: VM emulation RunTime for WASM-based blockchain contracts
Author: Jeeyong Um
Latest version: 0.1.46

# VeRT

**VM emulation RunTime for WASM-based blockchain contracts**

VeRT is a blockchain virtual machine emulator for WASM-based contracts like EOSIO. (CosmWasm and Substrate will be supported.)
It uses the built-in WebAssembly object in JavaScript, so can be executed on any modern browsers or runtime environments without additional dependencies.
It doesn't support the full specification of each blockchain state-machine, but can be used to run and test smart contracts before deployment.
The focus of VeRT is on the better compatibility than the performance, so it can be integrated with development pipelines.

- Run and test smart contracts
- Minimum dependencies (No native wrapper, docker or remote connection)
- Volatile key-value store with state rollback 

## Requirement

- WebAssembly binary with the exported memory ([blanc](https://github.com/haderech/blanc) v0.9.2 or higher)
- JavaScript runtime with WebAssembly BigInt support (nodejs v16 or higher)

## Installation

```shell
npm install vert
```

## Test

- nodejs v16 or higher

```shell
npm run test
```

- nodejs v14

```shell
node --experimental-wasm-bigint node_modules/mocha/bin/_mocha src/**/*.spec.ts -r ts-node/register
```

## License

[MIT](./LICENSE)

[@greymass-eosio](./src/eos/@greymass-eosio/LICENSE)
npm package: @jafri/vue-diff-view
Description: > a git diff component for Vue.js
Author: liuye
Latest version: 0.7.0

# vue-diff-view
> a git diff component for Vue.js

## Usage
```vue
<template>
    <div id="app">
        <code-diff-viewer :new-content="newStr" :old-content="oldStr" title="测试修改"/>
    </div>
</template>

<script>
import CodeDiffViewer from 'VueDiffView';

export default {
    name: 'app',
    components: {
        CodeDiffViewer
    },
    data() {
        return {
            oldStr: '[\n    {\n        name: title\n        displayName: "标题"\n        datatype: "OBJECT"\n    }\n]',
            newStr: '[\n    {\n        name: title\n        displayName: "TAB"\n        datatype: "ARRAY"\n    }\n    {\n        name: title\n        displayName: "TAB"\n        datatype: "ARRAY"\n    }\n]'
        };
    }
};
</script>
```

## Overview

### diff result
![add delete file](https://github.com/codeDebugTest/vue-diff-view/raw/master/screenshots/add_delete.png)

![modify file](https://github.com/codeDebugTest/vue-diff-view/raw/master/screenshots/modify.png)

### todo
when select code, not trigger line number.
npm package: @jafri/vue-select
Description: Everything you wish the HTML <select> element could do, wrapped up into a lightweight, extensible Vue component.
Author: Jeff Sagal
Latest version: 3.11.3

# vue-select ![Current Release](https://img.shields.io/github/release/sagalbot/vue-select.svg?style=flat-square) ![Release Date](https://img.shields.io/github/release-date/sagalbot/vue-select?style=flat-square) ![Bundle Size](https://flat.badgen.net/bundlephobia/min/vue-select) ![Monthly Downloads](https://img.shields.io/npm/dm/vue-select.svg?style=flat-square) [![Coverage Status](https://coveralls.io/repos/github/sagalbot/vue-select/badge.svg?branch=master)](https://coveralls.io/github/sagalbot/vue-select?branch=master) ![MIT License](https://img.shields.io/github/license/sagalbot/vue-select.svg?style=flat-square)

> **Everything you wish the HTML `<select>` element could do, wrapped up into a lightweight, zero
> dependency, extensible Vue component.**

Vue Select is a feature rich select/dropdown/typeahead component. It provides a default
template that fits most use cases for a filterable select dropdown. The component is designed to be as
lightweight as possible, while maintaining high standards for accessibility,
developer experience, and customization.

- Tagging
- Filtering / Searching
- Vuex Support
- AJAX Support
- SSR Support
- Accessible
- ~20kb Total / ~5kb CSS / ~15kb JS
- Select Single/Multiple Options
- Customizable with slots and SCSS variables
- Zero dependencies

## Documentation

Complete documentation and examples available at https://vue-select.org.

- **[API Documentation](https://vue-select.org)**
- **[CodePen Template](http://codepen.io/sagalbot/pen/NpwrQO)**

## Sponsors :tada:

It takes a lot of effort to maintain this project. If it has saved you development time, please consider [sponsoring the project](https://github.com/sponsors/sagalbot)
with GitHub sponsors!

Huge thanks to the [sponsors](https://github.com/sponsors/sagalbot) and [contributors](https://github.com/sagalbot/vue-select/graphs/contributors) that make Vue Select possible!

## Install

```bash
yarn add vue-select

# or use npm

npm install vue-select
```

Then, import and register the component:

```js
import Vue from "vue";
import vSelect from "vue-select";

Vue.component("v-select", vSelect);
```

The component itself does not include any CSS. You'll need to include it separately:

```js
import "vue-select/dist/vue-select.css";
```

Alternatively, you can import the scss for complete control of the component styles:

```scss
@import "vue-select/src/scss/vue-select.scss";
```

You can also include vue-select directly in the browser. Check out the
[documentation for loading from CDN.](https://vue-select.org/guide/install.html#in-the-browser).

## License

[MIT](https://github.com/sagalbot/vue-select/blob/master/LICENSE.md)
npm package: @jagaad/strapi-utils-v4
Description: A collection of JavaScript/TypeScript utility functions and helpers for Jagaad projects
Author: Jagaad
Latest version: 0.1.0

# @jagaad/strapi-utils-v4

A collection of JavaScript/TypeScript utility functions and helpers for Strapi v4 in Jagaad projects.

## Description

This package provides a set of utilities to simplify working with Strapi v4 API. It includes helper functions and TypeScript type definitions that make it easier to work with Strapi's core functionalities like routers, services, and lifecycle events.

## Requirements

- Node.js >=20
- npm >=10
- Strapi v4

## Installation

```bash
# npm
npm install @jagaad/strapi-utils-v4
```

## Usage

### Importing

```typescript
// ESM
import { extendRouter } from '@jagaad/strapi-utils-v4';
```

## API Documentation

Please check [src/](./src/) folder for more information

## Contributing

Contributions are welcome! Please feel free to submit a Pull Request.

1. Fork the repository
2. Create your feature branch (`git checkout -b feature/amazing-feature`)
3. Commit your changes (`git commit -m 'Add some amazing feature'`)
4. Push to the branch (`git push origin feature/amazing-feature`)
5. Open a Pull Request

Please make sure to update tests as appropriate and follow the existing coding style.

## License

This project is licensed under the MIT License - see the [LICENSE](./LICENSE) file for details.
npm package: @jagaad/tsconfig
Description: Hosts TSConfigs for Jagaad organisation to extend in your apps.   Basically Definitely Typed for TSConfigs.
Latest version: 0.4.0

# @jagaad/tsconfig

Hosts TSConfigs for Jagaad organisation to extend in your apps.  
Basically Definitely Typed for TSConfigs.

Install:

```bash
npm install --save-dev @jagaad/tsconfig
```

Add to your `tsconfig.json`:

```jsonc
"extends": "@jagaad/tsconfig/strict.json"
```

Inspired by https://github.com/tsconfig/bases
npm package: @jagaad/tsconfig-bases
Description: Hosts TSConfigs for Jagaad organisation to extend in your apps.   Basically Definitely Typed for TSConfigs.
Latest version: 0.2.0
Deprecated: Use @jagaad/tsconfig package instead

# @jagaad/tsconfig-bases

Hosts TSConfigs for Jagaad organisation to extend in your apps.  
Basically Definitely Typed for TSConfigs.

Install:

```bash
npm install --save-dev @jagaad/tsconfig-bases
```

Add to your `tsconfig.json`:

```jsonc
"extends": "@jagaad/tsconfig-bases/tsconfig.json"
```

Inspired by https://github.com/tsconfig/bases
npm package: @jagaad/utils
Description: A collection of JavaScript/TypeScript utility functions and helpers for Jagaad projects
Author: Jagaad
Latest version: 0.29.0

# @jagaad/utils

A comprehensive JavaScript/TypeScript utility library that provides a collection of helper functions for Jagaad projects.

[![npm version](https://img.shields.io/npm/v/@jagaad/utils.svg)](https://www.npmjs.com/package/@jagaad/utils)
[![TypeScript](https://img.shields.io/badge/%3C%2F%3E-TypeScript-%230074c1.svg)](https://www.typescriptlang.org/)
[![MIT License](https://img.shields.io/badge/license-MIT-blue.svg)](LICENSE)

## Description

`@jagaad/utils` is a collection of utility functions designed to simplify common programming tasks in JavaScript/TypeScript projects. The library provides a wide range of functions categorized by type (array, string, date, etc.) with proper TypeScript typing to enhance developer experience.

## Installation

You can install the package using npm:

```bash
npm install @jagaad/utils
```

## Usage

Import the entire library:

```typescript
import { clamp } from '@jagaad/utils';

// Use any utility
const clampedValue = clamp(10, 20, 30);
```

## Contributing

Contributions are welcome! Please feel free to submit a Pull Request.

> [!NOTE]
> Please make sure that you add only generic types and utilities.  
> Anything that is more specific, should live in the project repository itself.

1. Fork the repository
2. Create your feature branch (`git checkout -b feature/amazing-feature`)
3. Commit your changes (`git commit -m 'Add some amazing feature'`)
4. Push to the branch (`git push origin feature/amazing-feature`)
5. Open a Pull Request

Please ensure your code follows the existing style and includes appropriate tests.

## Building from Source

```bash
# Clone the repository
git clone https://github.com/jagaad/utils.js.git
cd utils.js

# Install dependencies
npm install

# Build the library
npm run build
```

## License

This project is licensed under the MIT License - see the [LICENSE](./LICENSE) file for details.

## Acknowledgments

- Developed and maintained by the Jagaad Team
- Inspired by utility libraries like lodash, ramda, type-fest and others.
npm package: @jagadhis/fullstack-monorepo-template
Description: A full-stack monorepo template with Next.js, Node.js, Supabase, and Prisma
Author: jagadhis
Latest version: 1.30.3

# Full-stack Monorepo Template
![Socket Badge](https://socket.dev/api/badge/npm/package/@jagadhis/fullstack-monorepo-template/1.30.0)

A modern, production-ready monorepo template featuring Next.js, Node.js, Supabase, and Prisma.

## Features

- 🏗️ **Monorepo Structure** using Turborepo
- 🎯 **Type Safety** with TypeScript
- 🚀 **Frontend** with Next.js
- 🛠️ **Backend** with Node.js & Express
- 📦 **Database** with Prisma & Supabase
- 🔄 **Version Control** with semantic-release
- 📋 **Code Quality** with ESLint & Prettier
- 🪝 **Git Hooks** with lefthook
- 🏃‍♂️ **Fast Builds** with Turborepo's caching

## Quick Start

```bash
npx @jagadhis/fullstack-monorepo-template my-app
cd my-app
npm run dev
```

## Project Structure

```
.
├── apps/
│   ├── frontend/          # Next.js frontend
│   └── backend/          # Node.js & Express backend
├── packages/
│   └── types/           # Shared TypeScript types
├── package.json
└── turbo.json
```

## Available Scripts

- `npm run dev` - Start development servers
- `npm run build` - Build all packages
- `npm run lint` - Lint all packages
- `npm run test` - Run tests across packages

## Environment Setup

1. Frontend (.env.local):
```env
NEXT_PUBLIC_SUPABASE_URL=your_supabase_url
NEXT_PUBLIC_SUPABASE_ANON_KEY=your_supabase_key
```

2. Backend (.env):
```env
DATABASE_URL=your_database_url
```

## Contributing

1. Fork the repository
2. Create your feature branch (`git checkout -b feature/amazing-feature`)
3. Commit your changes (`git commit -m 'feat: add amazing feature'`)
4. Push to the branch (`git push origin feature/amazing-feature`)
5. Open a Pull Request

## Commit Convention

This project follows [Conventional Commits](https://www.conventionalcommits.org/):

- `feat:` New features
- `fix:` Bug fixes
- `docs:` Documentation changes
- `style:` Code style changes
- `refactor:` Code refactoring
- `test:` Adding or modifying tests
- `chore:` Maintenance tasks

## License

MIT © [jagadhis]

## Support

If you find this template helpful, please consider giving it a ⭐️ on GitHub!

For issues and feature requests, please use the [GitHub issues page](https://github.com/jagadhis/fullstack-monorepo-template/issues).