Huge News!Announcing our $40M Series B led by Abstract Ventures.Learn More
Socket
Sign inDemoInstall
Socket

@neosync/sdk

Package Overview
Dependencies
Maintainers
2
Versions
185
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

@neosync/sdk

Neosync SDK

  • 0.3.54
  • Source
  • npm
  • Socket score

Version published
Maintainers
2
Created
Source

Neosync TypeScript SDK

This SDK contains the generated types for Neosync API. This SDK is dogfooded by the main Neosync webapp to ensure its durability.

Installation

npm install @neosync/sdk

Usage

For a prime example of how to us this SDK, view the withNeosyncContext method in the Neosync app's BFF layer.

Note on Transports

Based on your usage, you'll have to install a different version of connect to provide the correct Transport based on your environment.

Install whichever one makes sense for you

npm install @connectrpc/connect-node
npm install @connectrpc/connect-web

Neosync API serves up Connect, which can listen using Connect, gRPC, or Web protocols. Each of the libraries above provides all three of those protocols, but it's recommended to use createConnectTransport for the most efficient setup.

import { getNeosyncClient } from '@neosync/sdk';
import { createConnectTransport } from '@connectrpc/connect-node';

const neosyncClient = getNeosyncClient({
  getTransport(interceptors) {
    return createConnectTransport({
      baseUrl: '<url>',
      httpVersion: '2',
      interceptors: interceptors,
    });
  },
});

Authenticating

To authenticate the TS Neosync Client, a function may be provided to the configuration that will be invoked prior to every request. This gives flexability in how the access token may be retrieved and supports either a Neosync API Key or a standard user JWT token.

When the getAccessToken function is provided, the Neosync Client is configured with an auth interceptor that attaches the Authorization header to every outgoingn request with the access token returned from the function. This is why the getTransport method receives a list of interceptors, and why it's important to hook them up to pass them through to the relevant transport being used.

import { getNeosyncClient } from '@neosync/sdk';
import { createConnectTransport } from '@connectrpc/connect-node';

const neosyncClient = getNeosyncClient({
  getAccessToken: () => process.env.NEOSYNC_API_KEY,
  getTransport(interceptors) {
    return createConnectTransport({
      baseUrl: process.env.NEOSYNC_API_URL,
      httpVersion: '2',
      interceptors: interceptors,
    });
  },
});

Neosync App

In the Neosync dashboard app, we pull the user access token off of the incoming request (auth is configured using next-auth.). This way we can ensure that all requests are using the user's access token and are passed through to Neosync API.

Keywords

FAQs

Package last updated on 14 Mar 2024

Did you know?

Socket

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Install

Related posts

SocketSocket SOC 2 Logo

Product

  • Package Alerts
  • Integrations
  • Docs
  • Pricing
  • FAQ
  • Roadmap
  • Changelog

Packages

npm

Stay in touch

Get open source security insights delivered straight into your inbox.


  • Terms
  • Privacy
  • Security

Made with ⚡️ by Socket Inc