@intrnl/bluesky-client v0.2.6

bluesky-client

Lightweight API client for Bluesky/AT Protocol.

npm install @intrnl/bluesky-client

This is an ESM-only library, if you are using TypeScript you'd need to configure your projects correctly in order to pick up the type declarations.

Why?

The official @atproto/api library is big!

• The lexicon codegen generates a ton of classes and functions due to the API being designed around RPC and namespaces. These can't be treeshaken at all if you only need access to some of the endpoints.
• The library unnecessarily bundles dependencies like graphemer and zod, which causes duplication in your app code if you also rely on said libraries.

The points above leads to @intrnl/bluesky-client, where the following tradeoffs are made instead:

• We only provide TypeScript definitions for endpoints, objects, and records, there is no runtime validation done in the library, proceed with caution.

• Queries and procedures are not accessed via property access, you're typing the nsid as a string instead.

  // ❎️
  agent.app.bsky.actor.getProfile({ actor: 'did:plc:ragtjsm2j2vknwkz3zp4oxrd' });
  
  // ✅️
  agent.rpc.get('app.bsky.actor.getProfile', {
  	params: {
  		actor: 'did:plc:ragtjsm2j2vknwkz3zp4oxrd',
  	},
  });

• No RichText class for handling texts with facets, examples as to how you can deal with RichText are available on the examples/ folder.

• No Moderation API for taking actions based on certain labels or status, this should be very trivial so long as you follow the official documentations on how it should be dealt with.

Usage

Creating an agent to make requests...

import { Agent } from '@intrnl/bluesky-client/agent';

const agent = new Agent({ serviceUri: 'https://bsky.social' });

await agent.login({
	identifier: '...',
	password: '...',
});

const profile = await agent.rpc.get('app.bsky.actor.getProfile', {
	params: {
		actor: 'did:plc:ragtjsm2j2vknwkz3zp4oxrd',
	},
});

console.log(profile);

Fiddling with AT Protocol schema...

import { type RefOf, type UnionOf } from '@intrnl/bluesky-client/atp-schema';

type Facet = RefOf<'app.bsky.richtext.facet'>;
type MentionFacet = UnionOf<'app.bsky.richtext.facet#mention'>;

const mention: MentionFacet = {
	$type: 'app.bsky.richtext.facet#mention',
	did: 'did:plc:ragtjsm2j2vknwkz3zp4oxrd',
};

const facet: Facet = {
	index: {
		byteStart: 7,
		byteEnd: 12,
	},
	features: [mention],
};

• RefOf types are used for referencing an object within another object or record.
• UnionOf types are used in places where a field can contain multiple references, requiring a $type field to differentiate the reference.
• ResponseOf can be used to retrieve the response data out of a given endpoint.
• Records interface contains the interface declarations for actual records.