open-index/open-npm huggingface dataset:
npm package: @proxymanllc/better-curl-to-json
Description: Convert curl format to json
Author: rony
Latest version: 0.2.0

# curl-to-json

https://www.npmjs.com/package/@proxymanllc/better-curl-to-json

## Install

```
npm i @proxymanllc/better-curl-to-json
```

## Usage

```ts
const parse = require("@proxymanllc/better-curl-to-json");

var out = parse(`your_curl`);
```

## How to publish new version

- Go to package.json and change the version
- Run `npm login` then `npm publish --access public`
npm package: @proxymanllc/better-node-fetch
Description: Better light-weight module that brings window.fetch to node.js. Support GET request with body
Author: Proxyman LLC
Latest version: 0.4.0

### Introduction

- A better version of [node-fetch version 2.x](https://github.com/node-fetch/node-fetch/tree/2.x)
- Because node-fetch doesn't support GET request with body so I forked the library and modify the code to support it.
- This library is used in [ProxymanApp/better-node-fetch-cjs](https://github.com/ProxymanApp/better-node-fetch-cjs)
- I don't use this library directly in proxyman-electron-app because in the production mode, this library doesn't work
  so we need to install this library in [ProxymanApp/better-node-fetch-cjs](https://github.com/ProxymanApp/better-node-fetch-cjs) and use [ProxymanApp/better-node-fetch-cjs](https://github.com/ProxymanApp/better-node-fetch-cjs) instead.
- Details is in pull request https://github.com/ProxymanApp/proxyman-electron-app/pull/115

### How to publish

- Run `npm login`
- Run `npm publish --access public`
npm package: @proxymanllc/better-node-fetch-cjs
Description: Better light-weight module that brings window.fetch to node.js. Support GET request with body
Author: Proxyman LLC
Latest version: 0.4.0

### Introduction
 - A better version of [node-fetch-commonjs](https://www.npmjs.com/package/node-fetch-commonjs)
 - Since [node-fetch-commonjs](https://www.npmjs.com/package/node-fetch-commonjs) doesn't support GET request with body, so I fork the library and modify the code to support GET request with body.
 - This library use [ProxymanApp/better-node-fetch](https://github.com/ProxymanApp/better-node-fetch)

### How to build and publish
 - Run `npm i` 
 - Run `node build.js`
 - Cd to folder lib 
 - Run `npm login`
 - Run `npm publish --access public`
npm package: @proxymanllc/better-node-machine-uid
Description: Unique machine (desktop) id (no admin privileges required).doesn't use reg.exe on windows
Author: ProxymanLLC
Latest version: 0.2.0

[![CI](https://github.com/Alucard17/node-machine-uid/actions/workflows/ci.yml/badge.svg)](https://github.com/Alucard17/node-machine-uid/actions/workflows/ci.yml)

# node-machine-uid

`node-machine-uid` is a Node.js library for generating machine-unique identifiers. This library is a fork of the popular [node-machine-id](https://github.com/automation-stack/node-machine-id) library, with modifications to fix an issue on Windows where reading the registry is disabled due to access rights. `node-machine-uid` uses the [registry-js](https://github.com/desktop/registry-js) library to get the machine ID on Windows, which does not require the use of `reg.exe`.

**Cross-platform unique machine (desktop) id discovery**

## Use cases

- Software restrictions
- Installation tracking

## Features

- Hardware independent
- Unique within the OS installation
- No elevated rights required
- No external dependencies and does not require any native bindings
- Cross-platform (OSx, Win, Linux)

## Installation

To install `node-machine-uid` in your project, run:

bashCopy code

`$ npm install node-machine-uid`

## Usage

#### To use `node-machine-uid`:

```js
import machineId from "node-machine-uid"

const id = machineId()

console.log(id)
```

This will output a unique 64 character identifier in the following format:
`XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX`

On Windows, `node-machine-uid` uses `registry-js` to get the machine ID, which does not require the use of `reg.exe`. Instead, it generates a unique ID based on the computer name and the processor architecture.

## Contributing

Contributions to `node-machine-uid` are welcome! If you would like to contribute, please follow these steps:

1.  Fork the repo.
2.  Create a new branch for your feature/bugfix.
3.  Write tests for your changes.
4.  Implement your changes.
5.  Run the tests to make sure everything passes.
6.  Submit a pull request.

## License

`node-machine-uid` is licensed under the MIT License. See the [LICENSE](https://chat.openai.com/LICENSE) file for more information.

## Acknowledgments

The `node-machine-uid` library is a fork of the [node-machine-id](https://github.com/automation-stack/node-machine-id) library. Special thanks to the original authors for creating such a useful library!

`node-machine-uid` also uses the [registry-js](https://github.com/desktop/registry-js) library to get the machine ID on Windows. Thank you to the `registry
npm package: @proxyport/proxyport
Description: proxyport Node.js package provides interfaces to the Proxy Port API
Author: Proxy Port
Latest version: 1.1.1

# Proxy Port SDK
`@proxyport/proxyport` Node.js package provides interfaces to the <a href="https://proxy-port.com/en/scraping-proxy" target="_blank">Proxy Port</a> API.
## Prerequisites
To use this package you will need a free API key. Get your AIP key <a href="https://account.proxy-port.com/scraping" target="_blank">here</a>.
Detailed instructions <a href="https://proxy-port.com/en/scraping-proxy/getting-started" target="_blank">here</a>.
## Installation
Install via <a href="https://www.npmjs.com" target="_blank">npm</a>:
```shell
$ npm i @proxyport/proxyport
```
## Getting Started
Before you get your first proxy, you need to assign an <a href="https://account.proxy-port.com/scraping" target="_blank">API key</a>.
```typescript
import { ProxyPort } from '@proxyport/proxyport';

let proxyPort = new ProxyPort(<API_KEY>);

(async () => {
    let proxy = await proxyPort.getProxy();
    console.log(proxy);
})();

```