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 🙏

© 2026 – Pkg Stats / Ryan Hefner

@milesoft/typescript-services

v7.1.0

Published

Client-side service classes for Milesoft REST APIs, centralizing Axios configuration, authentication, and error handling.

Readme

@milesoft/typescript-services ☁️

npm version License: MIT

A collection of client-side service classes for interacting with Milesoft's standardized REST APIs. This package centralizes HTTP configuration, authentication, and error handling.

This library provides ready-to-use, initialized service objects (authService, userService, etc.) that abstract away network logic, allowing application code to focus purely on data flow.


✨ Features

The package exports singleton instances of service classes, each managing API calls for a specific domain:

| Service Export | Domain | Key Responsibilities | |:--------------------------|:---------------------------------|:----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | authService | Authentication and Authorization | Initializes and manages axios instances (including one without auth headers for login/recovery). Handles JWT storage, request cancellation, and unauthenticated response interceptors. | | accountService | Account Management and Joining | Provides logic for loading, saving, and joining accounts. Requires an external AccountUtils object for entity sanitation. | | userService | User and Profile Management | Provides CRUD operations (list, create, save, delete) for user entities, and dedicated methods for profile management. Requires an external UserUtils object for entity sanitation. | | typeService | User Typ Management | Provides standardized CRUD operations for custom user types and permissions. | | notificationService | Notifications and Preferences | Provides methods for listing, marking, and deleting user notifications. Manages user preference settings for different notification types and topics. | | nodeService | Node/Entity Management | Provides CRUD and list operations for generic graph nodes, including contact information and metadata. | | edgeService | Edge/Relationship Management | Provides CRUD and list operations for relationships (edges) between nodes. | | oauthService | OAuth integrations | Provides CRUD operations for OAuth integrations and manages tokens (load, save, delete) for connected third-party services. | | cloudinaryService | Image Uploads | Dedicated service for uploading user and account images to the configured Cloudinary instance. | | templateService | Template Management | Provides CRUD operations for managing templates. |


⚙️ Peer Dependencies

This library is designed to work within the Milesoft ecosystem and relies on the following packages (which you must install alongside this one):

| Package | Purpose | |:---------------------------------|:------------------------------------------------------------------------------| | @milesoft/typescript-constants | Provides keys for JWT and temporary password storage. | | @milesoft/typescript-utils | Provides storageUtils for browser storage and stringUtils for JWT checks. | | axios & axios-retry | The underlying HTTP client and its robust retry logic. |


🚀 Installation

Install the service package and its required peer dependencies:

# Install the core service package
npm install @milesoft/typescript-services

# Install peer dependencies
npm install @milesoft/typescript-constants @milesoft/typescript-utils axios axios-retry

💡 Usage

1. Initialization (Required)

Before making any requests, the service objects must be initialized to configure the base URL, timeouts, and error handling. It's recommended to do this once at application startup.

Note: userService and other services rely on authService for its configured axios instance.

import {authService, userService, accountService, cloudinaryService, templateService} from "@milesoft/typescript-services";

// Define unauthenticated handler
const handleUnauthenticated = () => {
    // Redirect user to login page, clear state, etc.
    authService.clearAuthToken();
    window.location.href = '/login';
};

// Required utilities for data formatting
const myAppUserUtils = {
    sanitizeUser: (user) => { /* ... */
    },
    sanitizeProfile: (profile) => { /* ... */
    },
};

const myAppAccountUtils = {
    sanitizeAccount: (account) => { /* ... */
    },
};

// 1. Initialize Auth Service (Must be first)
authService.init({
    baseUrl: 'https://api.yourdomain.com',
    timeout: 30000,
    retries: 3,
    onUnauthenticated: handleUnauthenticated,
});

// 2. Initialize other services
accountService.init({
    baseUrl: 'https://api.yourdomain.com',
    accountUtils: myAppAccountUtils,
    userUtils: myAppUserUtils,
});

userService.init({
    baseUrl: 'https://api.yourdomain.com',
    userUtils: myAppUserUtils,
});

typeService.init({
    baseUrl: 'https://api.yourdomain.com',
});

notificationService.init({
    baseUrl: 'https://api.yourdomain.com',
    notificationTypes: {
        'new_user': {role: 'ROLE_ADMIN', description: 'Someone signed up', delivery: 'App'},
        // ... other types
    },
    topicTypes: {
        'announcement': {role: 'ROLE_USER', description: 'Something interesting happened', delivery: 'App'},
        // ... other topics
    }
});

nodeService.init({
    baseUrl: 'https://api.yourdomain.com',
});

edgeService.init({
    baseUrl: 'https://api.yourdomain.com',
});

oauthService.init({
    baseUrl: 'https://api.yourdomain.com',
});

cloudinaryService.init({
    cloudinaryId: 'your-cloudinary-cloud-name', // e.g., 'milesoft'
});

templateService.init({
    baseUrl: 'https://api.yourdomain.com',
});

2. Making Requests

All service methods utilize standardized success and failure callback patterns.

// --- Example: Getting the logged-in user ---
authService.getLoggedInUser(
    (user) => {
        console.log("Logged-in user:", user.email);
    },
    (error) => {
        console.error("Failed to fetch user:", error.message);
    }
);

// --- Example: Creating a new Type Entity ---
const newTypeData: Partial<Type> = {
    title: "New Role",
    description: "A description of the role.",
    roles: ["admin", "editor"],
};

typeService.createType(
    newTypeData,
    (createdType) => {
        console.log("Type created with ID:", createdType.id);
    },
    (error) => {
        console.error("Type creation failed:", error);
    }
);

// --- Example: Marking notifications as read ---
notificationService.markAsRead(
    ["id-1", "id-2"],
    (ids) => {
        console.log(`Successfully marked ${ids.length} notifications as read.`);
    },
    (error) => {
        console.error("Failed to mark notifications as read:", error);
    }
);

// --- Example: Creating a new Node Entity ---
const newNodeData: Partial<Node> = {
    firstName: "John",
    lastName: "Doe",
    emails: [{label: "Work", value: "[email protected]"}],
};

nodeService.createNode(
    newNodeData,
    (createdNode) => {
        console.log("Node created with ID:", createdNode.id);
    },
    (error) => {
        console.error("Node creation failed:", error);
    }
);

// --- Example: Creating an Edge (relationship) between two Nodes ---
const newEdgeData: Partial<Edge> = {
    sourceNodeId: "node-123",
    targetNodeId: "node-456",
    category: "WorksWith",
    label: "Colleague",
};

edgeService.createEdge(
    newEdgeData,
    (createdEdge) => {
        console.log("Edge created from", createdEdge.sourceNodeId, "to", createdEdge.targetNodeId);
    },
    (error) => {
        console.error("Edge creation failed:", error);
    }
);

// --- Example: Listing available OAuth integrations ---
oauthService.listIntegrations(
    null, // No cursor (first page)
    10,
    (integrationList: OauthIntegrationList) => {
        console.log(`Found ${integrationList.integrations.length} integrations.`);
    },
    (error) => {
        console.error("Failed to list integrations:", error);
    }
);

// --- Example: Saving tokens after a successful OAuth flow ---
oauthService.saveTokens(
    "slack-integration-id",
    "authorization-code-from-url",
    { installationId: "i-12345" }, // Optional metadata
    () => {
        console.log("Tokens saved successfully.");
    },
    (error) => {
        console.error("Failed to save tokens:", error);
    }
);

// --- Example: Uploading an image ---
const imageFile: File = new File(["..."], "logo.png");  // Assume you have a file object
const accountId: string = "a1b2c3d4e5f6";

cloudinaryService.uploadAccountImage(
    accountId,
    imageFile,
    (secureUrl) => {
        console.log("Image uploaded to:", secureUrl);
    },
    (error) => {
        console.error("Image upload failed:", error);
    }
);

// --- Example: Creating a new Template ---
const newTemplateData: Partial<Template> = {
    title: "New Template",
    body: "The content of the template.",
};

templateService.createTemplate(
    newTemplateData,
    (createdTemplate) => {
        console.log("Template created with ID:", createdTemplate.id);
    },
    (error) => {
        console.error("Template creation failed:", error);
    }
);