@signumjs/http

Generic HTTP client that is used as a network provider for @signumjs/core.

Installation

@signumjs/http can be used with NodeJS or Web. Two formats are available

Using with NodeJS and/or modern web frameworks

Install using npm:

npm install @signumjs/http

or using yarn:

yarn add @signumjs/http

Example

import {HttpImpl} from '@signumjs/http'

async function getTodos() {
    try{
        const client = new HttpClientFactory.createHttpClient('https://jsonplaceholder.typicode.com/');
        const result = await client.get('/todos/1')
        console.log(result)
    }
    catch(httpError){
        console.error(httpError.message)
    }
}

Using in classic <script>

Each package is available as bundled standalone library using UMD. This way signumJS can be used also within <script>-Tags. This might be useful for Wordpress and/or other PHP applications.

Just import the package using the HTML <script> tag.

<script src='https://cdn.jsdelivr.net/npm/@signumjs/http/dist/signumjs.http.min.js'></script>

Example

const {HttpClientFactory} = sig$http
const client = new HttpClientFactory.createHttpClient('https://jsonplaceholder.typicode.com/');
client.get('/todos/1').then(console.log)

See more here:

@signumjs/http Online Documentation

Change Log

2.0.7

Patch Changes

• 1a64657: improved crypto randomness for word and string generators

2.0.6

Patch Changes

• Breaking Change: renamed isAttachmentVersion to getAttachmentVersion and typed the version identifier
• Added main field in package.json to fix resolution issues

2.0.5

Patch Changes

• Uses exports in package.json and minor fixes

2.0.4

Patch Changes

• [Breaking Change] CryptoProvider renamed to CryptoAdapter

  • Crypto Adapters NodeJsCryptoAdapter and WebCryptoAdapter are dedicate path @signumjs/crypto/adapters
  • generateMnemonic has changed API to better support partial settings.

2.0.3

Patch Changes

• Decoupled Crypto Provider. Breaking Change as this requires the developer to define the platform specific crypto provider before using the sdk

  Breaking Change:

  If you see the following error:

  "No Crypto Provider provided - Use [Crypto.init()] first";

  You need to initialize the crypto module with the platform specific CryptoProvider.

  NodeJS

  import { Crypto, NodeJSCryptoProvider } from "@signumjs/crypto";
  Crypto.init(new NodeJSCryptoProvider());

  Web/Browser

  import { Crypto, WebCryptoProvider } from "@signumjs/crypto";
  Crypto.init(new WebCryptoProvider());

  Further implementations will be provided as external modules/packages, i.e. React Native Expo

2.0.2

Patch Changes

• Crypto: Custom Crypto Provider on getInstance

2.0.1

Patch Changes

• Added IIFE bundles

2.0.0

Major Changes

• 14f4944: This new version uses a completely modernized stack (turborepo, vite, vitest). Furthermore, the crypto package was rewritten to remove deprecated crypto-js library and being extensible. The standards (SRC) packages were reorganized and finally the monitor package was removed Breaking Changes:
  1. @signumjs/monitor was removed, as not really used
  2. @signumjs/crypto was completely rewritten, mainly due to the deprecation of crypto-js and certain security implications
  3. @signumjs/standards were reorganized respecting the Signum Request for Comment (SRC) numbering How to update from 1.0 to 2.0
  4. Monitor was removed Drop signumjs/monitor (no replacement here) - if you used the monitor you can copy the code from the repo and include it manually in your code base
  5. Adjust Crypto
  6. Passphrase generator was dropped, use generateMnemonic instead
  7. generateMasterKeys was renamed to generateSignKeys
  8. hashSHA256 was renamed to sha256AsHex (and more sha256 hashers are available)
  9. encryptAES and decryptAES were dropped - use native crypto methods for AES encryption. Signum uses for their P2P encryption a AES based algorithm using the shared key (encryptMessage and encryptData)

     The new crypto package offers more secure random and sha256 functions and is much more flexible. Check the docs for more info

  10. Using SRC based standards Actually, not much to do here. It's just that the internal structure is organized by the SRC numbering. All notable changes to this project will be documented in this file.

1.0.0 (TBR)

• Rebranding

Before Rebranding

0.6.0

Breaking Change

• Access to Http client through new HttpClientFactory

0.5.1

• Better message handling in case of errors

0.4.3

• Http clients with AxiosConfig

0.4.1

• Adding configuration/options for Http clients

0.4.0

• Changed License: From GPL-3.0 to Apache 2.0

0.1.3

• now available as standalone bundle (iife)