@islo-labs/sdk
v0.0.20
Published
Official TypeScript SDK for islo.dev
Maintainers
Readme
Islo TypeScript Library
The Islo TypeScript library provides convenient access to the Islo APIs from TypeScript.
Table of Contents
- Installation
- Quick Start
- Authentication
- Configuration
- Development
- Reference
- Usage
- Request and Response Types
- Exception Handling
- Advanced
- Contributing
Installation
npm i -s @islo-labs/sdkQuick Start
import { Islo } from "@islo-labs/sdk";
// Automatically reads ISLO_API_KEY from environment
const client = new Islo();
// Create a sandbox
const sandbox = await client.sandboxes.createSandbox({
name: "my-sandbox",
image: "ubuntu:22.04",
vcpus: 2,
memoryMb: 4096,
});
// Execute a command
const result = await client.sandboxes.execInSandbox({
sandboxName: sandbox.name,
command: ["echo", "hello world"],
});
console.log(result.exitCode);
// Clean up
await client.sandboxes.deleteSandbox({ sandboxName: sandbox.name });Authentication
Environment variable (recommended)
export ISLO_API_KEY="your-api-key"const client = new Islo(); // Picks up ISLO_API_KEY automaticallyExplicit API key
const client = new Islo({ apiKey: "your-api-key" });Custom token provider
import { IsloClient } from "@islo-labs/sdk";
const client = new IsloClient({
environment: "https://api.islo.dev",
token: async () => fetchTokenFromYourAuthService(),
});Configuration
| Environment Variable | Description | Default |
|---------------------|-------------|---------|
| ISLO_API_KEY | API key exchanged for a short-lived JWT | — |
| ISLO_BASE_URL | API base URL | https://api.islo.dev |
Development
# Install typecheck deps
npm install --no-save typescript@~5.6 @types/node@~20
# Typecheck
npx tsc --noEmitRegenerating the SDK
This SDK is generated by Fern from the OpenAPI spec maintained in islo-web-api. Fern runs from that repo and pushes the generated code here.
Custom code in Islo.ts, index.ts, tsconfig.json, and custom/ is preserved across regenerations via .fernignore.
Reference
A full reference for this library is available here.
Usage
Instantiate and use the client with the following:
import { Islo } from "@islo-labs/sdk";
const client = new Islo({ environment: "YOUR_BASE_URL", apiKey: "YOUR_API_KEY" });
await client.sandboxes.createSandbox();Request and Response Types
The SDK exports all request and response types as TypeScript interfaces. Simply import them with the following namespace:
import { IsloApi } from "@islo-labs/sdk";
const request: IsloApi.ListSandboxesRequest = {
...
};Exception Handling
When the API returns a non-success status code (4xx or 5xx response), a subclass of the following error will be thrown.
import { IsloApiError } from "@islo-labs/sdk";
try {
await client.sandboxes.createSandbox(...);
} catch (err) {
if (err instanceof IsloApiError) {
console.log(err.statusCode);
console.log(err.message);
console.log(err.body);
console.log(err.rawResponse);
}
}Advanced
Subpackage Exports
This SDK supports direct imports of subpackage clients, which allows JavaScript bundlers to tree-shake and include only the imported subpackage code. This results in much smaller bundle sizes.
import { SandboxesClient } from '@islo-labs/sdk/sandboxes';
const client = new SandboxesClient({...});Additional Headers
If you would like to send additional headers as part of the request, use the headers request option.
import { Islo } from "@islo-labs/sdk";
const client = new Islo({
...
headers: {
'X-Custom-Header': 'custom value'
}
});
const response = await client.sandboxes.createSandbox(..., {
headers: {
'X-Custom-Header': 'custom value'
}
});Additional Query String Parameters
If you would like to send additional query string parameters as part of the request, use the queryParams request option.
const response = await client.sandboxes.createSandbox(..., {
queryParams: {
'customQueryParamKey': 'custom query param value'
}
});Retries
The SDK is instrumented with automatic retries with exponential backoff. A request will be retried as long as the request is deemed retryable and the number of retry attempts has not grown larger than the configured retry limit (default: 2).
A request is deemed retryable when any of the following HTTP status codes is returned:
Use the maxRetries request option to configure this behavior.
const response = await client.sandboxes.createSandbox(..., {
maxRetries: 0 // override maxRetries at the request level
});Timeouts
The SDK defaults to a 60 second timeout. Use the timeoutInSeconds option to configure this behavior.
const response = await client.sandboxes.createSandbox(..., {
timeoutInSeconds: 30 // override timeout to 30s
});Aborting Requests
The SDK allows users to abort requests at any point by passing in an abort signal.
const controller = new AbortController();
const response = await client.sandboxes.createSandbox(..., {
abortSignal: controller.signal
});
controller.abort(); // aborts the requestAccess Raw Response Data
The SDK provides access to raw response data, including headers, through the .withRawResponse() method.
The .withRawResponse() method returns a promise that results to an object with a data and a rawResponse property.
const { data, rawResponse } = await client.sandboxes.createSandbox(...).withRawResponse();
console.log(data);
console.log(rawResponse.headers['X-My-Header']);Logging
The SDK supports logging. You can configure the logger by passing in a logging object to the client options.
import { Islo, logging } from "@islo-labs/sdk";
const client = new Islo({
...
logging: {
level: logging.LogLevel.Debug, // defaults to logging.LogLevel.Info
logger: new logging.ConsoleLogger(), // defaults to ConsoleLogger
silent: false, // defaults to true, set to false to enable logging
}
});The logging object can have the following properties:
level: The log level to use. Defaults tologging.LogLevel.Info.logger: The logger to use. Defaults to alogging.ConsoleLogger.silent: Whether to silence the logger. Defaults totrue.
The level property can be one of the following values:
logging.LogLevel.Debuglogging.LogLevel.Infologging.LogLevel.Warnlogging.LogLevel.Error
To provide a custom logger, you can pass in an object that implements the logging.ILogger interface.
Here's an example using the popular winston logging library.
import winston from 'winston';
const winstonLogger = winston.createLogger({...});
const logger: logging.ILogger = {
debug: (msg, ...args) => winstonLogger.debug(msg, ...args),
info: (msg, ...args) => winstonLogger.info(msg, ...args),
warn: (msg, ...args) => winstonLogger.warn(msg, ...args),
error: (msg, ...args) => winstonLogger.error(msg, ...args),
};Here's an example using the popular pino logging library.
import pino from 'pino';
const pinoLogger = pino({...});
const logger: logging.ILogger = {
debug: (msg, ...args) => pinoLogger.debug(args, msg),
info: (msg, ...args) => pinoLogger.info(args, msg),
warn: (msg, ...args) => pinoLogger.warn(args, msg),
error: (msg, ...args) => pinoLogger.error(args, msg),
};Custom Fetch
The SDK provides a low-level fetch method for making custom HTTP requests while still
benefiting from SDK-level configuration like authentication, retries, timeouts, and logging.
This is useful for calling API endpoints not yet supported in the SDK.
const response = await client.fetch("/v1/custom/endpoint", {
method: "GET",
}, {
timeoutInSeconds: 30,
maxRetries: 3,
headers: {
"X-Custom-Header": "custom-value",
},
});
const data = await response.json();Custom Fetcher
The SDK provides a way for you to customize the underlying HTTP client / Fetch function. If you're running in an unsupported environment, this provides a way for you to break glass and ensure the SDK works.
import { Islo } from "@islo-labs/sdk";
const client = new Islo({
...
fetcher: // provide your implementation here
});Runtime Compatibility
The SDK works in the following runtimes:
- Node.js 18+
- Vercel
- Cloudflare Workers
- Deno v1.25+
- Bun 1.0+
- React Native
Contributing
While we value open-source contributions to this SDK, this library is generated programmatically. Additions made directly to this library would have to be moved over to our generation code, otherwise they would be overwritten upon the next generated release. Feel free to open a PR as a proof of concept, but know that we will not be able to merge it as-is. We suggest opening an issue first to discuss with us!
On the other hand, contributions to the README are always very welcome!
