robbyuitbeijerse

mc-account-api-react

You need to provide a JWT token to consume the API. You will be able to obtain this user-specific JWT token after your user has logged in on your application.

@onbeam/automation-api-client

The Beam Automation API request client is meant to be implemented in **server side environments**. It allows you to create (managed) account abstractions and manage assets for said accounts accordingly, all authorized through an API key.

@onbeam/biome-config

The default biome config used throughout all Beam packages and apps. Used to extend upon in your local biome configuration file.

@onbeam/cli

A tool to update your @onbeam/* packages with the detected package manager.

@onbeam/errors

@onbeam/features

A collection of features built by combining components from `@onbeam/ui` and utils/hooks from `@onbeam/utils`, forming fully functioning ready to go features (for example handling cookie consent and wallet connections). It is necessary to setup `@onbeam/s

@onbeam/icons

A collection of icons (as React components) from the Beam design system, which can also be used standalone. [Click here](https://beam-packages.vercel.app/?path=/docs/theme-icons--docs) for an overview of all icons.

@onbeam/node

The Beam client for the node.js ecosystem provides a type-safe interface for consuming the Beam API. Please note that this client is not meant to be used in client side javascript, as following these instructions in a client-side environment would expose

@onbeam/player-api-client

The Beam Player API request client is meant to be implemented in **server side environments**. It allows you to read data through our service, and generate Operations for your users.

@onbeam/react

You need to provide a JWT token to consume the API. You will be able to obtain this user-specific JWT token after your user has logged in on your application.