npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2025 – Pkg Stats / Ryan Hefner

eternal-core

v1.1.3

Published

<!-- Start SDK Installation [installation] --> ## SDK Installation

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Maintainers

martinmedinamartinmedina

Keywords

Readme

archivista-sdk-eternal-core

SDK Installation

NPM

npm install @archivista/eternal-core

Yarn

yarn add @archivista/eternal-core

SDK Example Usage

Example

import { EternalCoreSDK } from "@archivista/eternal-core";
import { CreateAccessRequestRole } from "@archivista/eternal-core/dist/sdk/models/shared";

async function run() {
    const sdk = new EternalCoreSDK({
        security: {
            bearer: "<YOUR_BEARER_TOKEN_HERE>",
        },
    });

    const res = await sdk.accessRequest.createAccessRequest({
        email: "",
        fullName: "",
        isEmailVerified: false,
        promoCode: "promoCode",
        role: CreateAccessRequestRole.User,
        signature: "0x0",
        wallet: "0x0",
    });

    if (res.statusCode == 200) {
        // handle response
    }
}

run();

Available Resources and Operations

accessRequest

auth

certifyRequest

cloudMedia

customApp

health

payment

recordAccess

recordDraft

recordDraftShare

recordDraftTransfer

recordGallery

admin

recordMasters

user

userRequests

userWalletRegistries

userWalletRegistriesInvitations

webhooks

Error Handling

Handling errors in this SDK should largely match your expectations. All operations return a response object or throw an error. If Error objects are specified in your OpenAPI Spec, the SDK will throw the appropriate Error type.

| Error Object | Status Code | Content Type | | ----------------------- | ----------------------- | ----------------------- | | errors.InvalidSignature | 403 | application/json | | errors.SDKError | 4xx-5xx | / |

Example

import { EternalCoreSDK } from "@archivista/eternal-core";

async function run() {
    const sdk = new EternalCoreSDK({
        security: {
            bearer: "<YOUR_BEARER_TOKEN_HERE>",
        },
    });

    let res;
    try {
        res = await sdk.auth.loginWalletAuth({
            signature: "0x0",
            wallet: "0x0",
        });
    } catch (err) {
        if (err instanceof errors.InvalidSignature) {
            console.error(err); // handle exception
            throw err;
        } else if (err instanceof errors.SDKError) {
            console.error(err); // handle exception
            throw err;
        }
    }

    if (res.statusCode == 200) {
        // handle response
    }
}

run();

Server Selection

Select Server by Index

You can override the default server globally by passing a server index to the serverIdx: number optional parameter when initializing the SDK client instance. The selected server will then be used as the default on the operations that use it. This table lists the indexes associated with the available servers:

| # | Server | Variables | | - | ------ | --------- | | 0 | https://eternal-core-{environment}.archivista.com/ | environment (default is dev) |

Example

import { EternalCoreSDK } from "@archivista/eternal-core";
import { CreateAccessRequestRole } from "@archivista/eternal-core/dist/sdk/models/shared";

async function run() {
    const sdk = new EternalCoreSDK({
        serverIdx: 0,
        security: {
            bearer: "<YOUR_BEARER_TOKEN_HERE>",
        },
    });

    const res = await sdk.accessRequest.createAccessRequest({
        email: "",
        fullName: "",
        isEmailVerified: false,
        promoCode: "promoCode",
        role: CreateAccessRequestRole.User,
        signature: "0x0",
        wallet: "0x0",
    });

    if (res.statusCode == 200) {
        // handle response
    }
}

run();

Variables

Some of the server options above contain variables. If you want to set the values of those variables, the following optional parameters are available when initializing the SDK client instance:

  • environment: models.ServerEnvironment

Override Server URL Per-Client

The default server can also be overridden globally by passing a URL to the serverURL: str optional parameter when initializing the SDK client instance. For example:

import { EternalCoreSDK } from "@archivista/eternal-core";
import { CreateAccessRequestRole } from "@archivista/eternal-core/dist/sdk/models/shared";

async function run() {
    const sdk = new EternalCoreSDK({
        serverURL: "https://eternal-core-{environment}.archivista.com/",
        security: {
            bearer: "<YOUR_BEARER_TOKEN_HERE>",
        },
    });

    const res = await sdk.accessRequest.createAccessRequest({
        email: "",
        fullName: "",
        isEmailVerified: false,
        promoCode: "promoCode",
        role: CreateAccessRequestRole.User,
        signature: "0x0",
        wallet: "0x0",
    });

    if (res.statusCode == 200) {
        // handle response
    }
}

run();

Custom HTTP Client

The Typescript SDK makes API calls using the axios HTTP library. In order to provide a convenient way to configure timeouts, cookies, proxies, custom headers, and other low-level configuration, you can initialize the SDK client with a custom AxiosInstance object.

For example, you could specify a header for every request that your sdk makes as follows:

import { @archivista/eternal-core } from "EternalCoreSDK";
import axios from "axios";

const httpClient = axios.create({
    headers: {'x-custom-header': 'someValue'}
})

const sdk = new EternalCoreSDK({defaultClient: httpClient});

Authentication

Per-Client Security Schemes

This SDK supports the following security scheme globally:

| Name | Type | Scheme | | ----------- | ----------- | ----------- | | bearer | http | HTTP Bearer |

You can set the security parameters through the security optional parameter when initializing the SDK client instance. For example:

import { EternalCoreSDK } from "@archivista/eternal-core";
import { CreateAccessRequestRole } from "@archivista/eternal-core/dist/sdk/models/shared";

async function run() {
    const sdk = new EternalCoreSDK({
        security: {
            bearer: "<YOUR_BEARER_TOKEN_HERE>",
        },
    });

    const res = await sdk.accessRequest.createAccessRequest({
        email: "",
        fullName: "",
        isEmailVerified: false,
        promoCode: "promoCode",
        role: CreateAccessRequestRole.User,
        signature: "0x0",
        wallet: "0x0",
    });

    if (res.statusCode == 200) {
        // handle response
    }
}

run();

Per-Operation Security Schemes

Some operations in this SDK require the security scheme to be specified at the request level. For example:

import { EternalCoreSDK } from "@archivista/eternal-core";
import { CreateRecordGallerySecurity } from "@archivista/eternal-core/dist/sdk/models/operations";

async function run() {
    const sdk = new EternalCoreSDK();
    const operationSecurity: CreateRecordGallerySecurity = {
        apiKey: "<YOUR_API_KEY_HERE>",
    };

    const res = await sdk.recordGallery.createRecordGallery(
        {
            address: "0x0",
            name: "My Gallery",
        },
        operationSecurity
    );

    if (res.statusCode == 200) {
        // handle response
    }
}

run();

How to use available environments

const sdk = new EternalCoreSDK({
    environment: "dev", // this could be handled dynamically to switch depending on the desired environment
});

Development

Maturity

This SDK is in beta, and there may be breaking changes between versions without a major version update. Therefore, we recommend pinning usage to a specific package version. This way, you can install the same version each time without breaking changes unless you are intentionally looking for the latest version.

Contributions

While we value open-source contributions to this SDK, this library is generated programmatically. Feel free to open a PR or a Github issue as a proof of concept and we'll do our best to include it in a future release!

Install speakeasy CLI https://www.speakeasyapi.dev/docs/speakeasy-cli/getting-started Run command to generate the sdk code based on the swagger open api specs

Ensure you have the Speakeasy CLI version 1.346.3 installed:

brew install speakeasy-api/homebrew-tap/[email protected]

Update SDK version

Before the latest version of the API is updated, run a local test to verify the SDK is generating as expected.

To do a local test, run the following command:

speakeasy generate sdk -s http://localhost:3000/api-json -o ./ -l typescript
  • If everything looks good, latest API version can be released
  • Go to gen.yaml and bump the package version up
  • Once latest API version is deployed run the following command:
speakeasy generate sdk -s https://eternal-core-dev.archivista.com/api-json -o ./ -l typescript