open-index/open-npm huggingface dataset:
npm package: @0xshady/solarbeamsdk
Description: 🛠 An SDK for building applications via 0x Shady.
Latest version: 2.4.0

# 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://uniswap.org/docs/v2/SDK/getting-started/).

## 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: @0xshady/solarflaresdk
Description: 🛠 A multichain Decentralized Exchange SDK for building applications via 0x Shady.
Latest version: 2.6.0

# 0xShady MoonBeam SolarFlare 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://uniswap.org/docs/v2/SDK/getting-started/).

## Running tests

To run the tests, follow these steps. You must have at least node v10 and [yarn](https://yarnpkg.com/) installed.

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: @0xshariq/voxa-types
Description: Shared TypeScript type definitions for Voxa HTTP Client ecosystem (CLI, API, SDKs)
Author: Sharique Chaudhary
Latest version: 1.0.0

# @0xshariq/voxa-types

Shared TypeScript type definitions for the Voxa HTTP Client ecosystem.

## Installation

```bash
npm install @0xshariq/voxa-types
# or
pnpm add @0xshariq/voxa-types
# or
yarn add @0xshariq/voxa-types
```

## Usage

### Import All Types

```typescript
import type { VoxaConfig, HttpMethod, CacheConfig } from '@0xshariq/voxa-types';
```

### Import Specific Modules

```typescript
// Client types
import type { VoxaConfig, VoxaResponse } from '@0xshariq/voxa-types/client';

// Cache types
import type { CacheConfig, CacheAdapter } from '@0xshariq/voxa-types/cache';

// Streaming types
import type { StreamingImageOptions, ImagePayload } from '@0xshariq/voxa-types/streaming';

// GraphQL types
import type { GraphQLConfig, GraphQLRequest } from '@0xshariq/voxa-types/graphql';
```

## Type Categories

### Client Types
- `VoxaConfig` - Main client configuration
- `VoxaResponse` - Response wrapper with metadata
- `HttpMethod` - Supported HTTP methods
- `RequestPriority` - Request priority levels

### Cache Types
- `CacheConfig` - Cache configuration
- `CacheAdapter` - Custom cache adapter interface
- `CacheEntry` - Cache entry structure

### Streaming Types
- `StreamingImageOptions` - Image streaming configuration
- `StreamingVideoOptions` - Video streaming configuration
- `ImagePayload` - Supported image types
- `VideoPayload` - Supported video types

### GraphQL Types
- `GraphQLConfig` - GraphQL configuration
- `GraphQLRequest` - GraphQL query request
- `GraphQLResponse` - GraphQL response structure
- `GraphQLError` - GraphQL error format

### HTTP/2 Types
- `Http2PushConfig` - HTTP/2 push configuration
- `PushedResource` - Pushed resource metadata

### Common Types
- `RequestMetadata` - Request tracking metadata
- `RetryConfig` - Retry configuration
- `QueueConfig` - Queue configuration
- `CircuitBreakerConfig` - Circuit breaker configuration
- And more...

## Usage in Projects

### In CLI
```typescript
import type { VoxaConfig } from '@0xshariq/voxa-types';

function createClient(config: VoxaConfig) {
  // CLI implementation
}
```

### In API
```typescript
import type { VoxaResponse, HttpMethod } from '@0xshariq/voxa-types';

async function handleRequest(method: HttpMethod): Promise<VoxaResponse> {
  // API implementation
}
```

### In SDKs
```typescript
import type { CacheConfig, StreamingImageOptions } from '@0xshariq/voxa-types';

class VoxaSDK {
  constructor(
    cache: CacheConfig,
    streaming: StreamingImageOptions
  ) {
    // SDK implementation
  }
}
```

## License

MIT © [Sharique Chaudhary](https://github.com/0xshariq)
npm package: @0xsodium/sdk4337
Description: This package provides 2 APIs for using UserOperations:
Latest version: 1.17.0

# SDK to create and send UserOperation 

This package provides 2 APIs for using UserOperations:

- Low-level "walletAPI"
- High-level Provider


## LowLevel API:

### BaseWalletAPI

An abstract base-class to create UserOperation for a contract wallet.

### SimpleWalletAPI

An implementation of the BaseWalletAPi, for the SimpleWallet sample of account-abstraction.

```typescript
owner = provider.getSigner()
const walletAPI = new SimpleWalletAPI({
    provider, 
    entryPointAddress,
    owner,
    factoryAddress
})
const op = await walletAPi.createSignedUserOp({
  target: recipient.address,
  data: recipient.interface.encodeFunctionData('something', ['hello'])
})
```

## High-Level Provider API

A simplified mode that doesn't require a different wallet extension. 
Instead, the current provider's account is used as wallet owner by calling its "Sign Message" operation.

This can only work for wallets that use an EIP-191 ("Ethereum Signed Message") signatures (like our sample SimpleWallet)
Also, the UX is not great (the user is asked to sign a hash, and even the wallet address is not mentioned, only the signer)

```typescript
import { wrapProvider } from '@account-abstraction/sdk'

//use this account as wallet-owner (which will be used to sign the requests)
const signer = provider.getSigner()
const config = {
  chainId: await provider.getNetwork().then(net => net.chainId),
  entryPointAddress,
  bundlerUrl: 'http://localhost:3000/rpc'
} 
const aaProvider = await wrapProvider(provider, config, aasigner)
const walletAddress = await aaProvider.getSigner().getAddress()

// send some eth to the wallet Address: wallet should have some balance to pay for its own creation, and for calling methods.

const myContract = new Contract(abi, aaProvider)

// this method will get called from the wallet address, through account-abstraction EntryPoint
await myContract.someMethod()
```
npm package: @0xsplits/splits-sdk
Description: SDK for the 0xSplits protocol
Author: 0xSplits
Latest version: 6.5.0

# Splits Core SDK

## Install

### Install the package with yarn or npm:

```bash
yarn add @0xsplits/splits-sdk

npm install @0xsplits/splits-sdk
```

## Documentation

Detailed documentation for the SDK can be found [here](https://docs.splits.org/sdk)

### Viem vs Ethers

The Splits SDK uses Viem under the hood. There is an older version of the SDK that uses ethers-v5.
If you would like to use that instead, you can install it with:

```bash
yarn add @0xsplits/splits-sdk@2

npm install @0xsplits/splits-sdk@2
```

Documentation for the old Ethers version can be found [here](https://docs.splits.org/sdk-ethers)
npm package: @0xsplits/splits-sdk-react
Description: React wrapper for the 0xSplits SDK
Author: 0xSplits
Latest version: 4.4.0

# Splits React SDK

This is the react wrapper for the core splits sdk. It provides convenient hooks for easily 
displaying 0xSplits data in a React app. The core sdk client is also available for performing 
all contract transactions.

## Install

### Install the package with yarn or npm:

```bash
yarn add @0xsplits/splits-sdk-react

npm install @0xsplits/splits-sdk-react

```

## Documentation

Detailed documentation for the SDK can be found [here](https://docs.splits.org/react)


### Viem vs Ethers

The Splits SDK uses Viem under the hood. There is an older version of the SDK that uses ethers-v5.
If you would like to use that instead, you can install it with:

```bash
yarn add @0xsplits/splits-sdk-react@0

npm install @0xsplits/splits-sdk-react@0
```

Documentation for the old Ethers version can be found [here](https://docs.splits.org/react-ethers)
npm package: @0xsuk/path-browserify
Description: the path module from node core for browsers that does not use process
Author: 0xsuk
Latest version: 1.0.1

# path-browserify [![Build Status](https://travis-ci.org/browserify/path-browserify.png?branch=master)](https://travis-ci.org/browserify/path-browserify)

> The `path` module from Node.js for browsers

This implements the Node.js [`path`][path] module for environments that do not have it, like browsers.

> `path-browserify` currently matches the **Node.js 10.3** API.

## Install

You usually do not have to install `path-browserify` yourself! If your code runs in Node.js, `path` is built in. If your code runs in the browser, bundlers like [browserify](https://github.com/browserify/browserify) or [webpack](https://github.com/webpack/webpack) include the `path-browserify` module by default.

But if none of those apply, with npm do:

```
npm install path-browserify
```

## Usage

```javascript
var path = require('path')

var filename = 'logo.png';
var logo = path.join('./assets/img', filename);
document.querySelector('#logo').src = logo;
```

## API

See the [Node.js path docs][path]. `path-browserify` currently matches the Node.js 10.3 API.
`path-browserify` only implements the POSIX functions, not the win32 ones.

## Contributing

PRs are very welcome! The main way to contribute to `path-browserify` is by porting features, bugfixes and tests from Node.js. Ideally, code contributions to this module are copy-pasted from Node.js and transpiled to ES5, rather than reimplemented from scratch. Matching the Node.js code as closely as possible makes maintenance simpler when new changes land in Node.js.
This module intends to provide exactly the same API as Node.js, so features that are not available in the core `path` module will not be accepted. Feature requests should instead be directed at [nodejs/node](https://github.com/nodejs/node) and will be added to this module once they are implemented in Node.js.

If there is a difference in behaviour between Node.js's `path` module and this module, please open an issue!

## License

[MIT](./LICENSE)

[path]: https://nodejs.org/docs/v10.3.0/api/path.html