Launch Week Day 1: Socket for Jira Is Now Available.Learn More
Socket
Book a DemoSign in
Socket

tinylicious

Package Overview
Dependencies
Maintainers
1
Versions
81
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

tinylicious

Tiny, test implementation of the routerlicious reference service

latest
Source
npmnpm
Version
7.0.1
Version published
Weekly downloads
3K
29.76%
Maintainers
1
Weekly downloads
 
Created
Source

tinylicious

Tinylicious is a minimal, self-contained, test implementation of the Fluid Framework service that is much smaller (tinier!) than Routerlicious, our reference implementation of the service.

What is this for?

Tinylicious includes most of the basic features needed to test data stores and containers. While we use the Local Server as an in-browser service for much of our data store and container development, Tinylicious offers some advantages because it's a standalone process. For instance, testing a Fluid Container from 2+ simultaneously connected clients can be easier using Tinylicious.

If you're looking for a reference implementation of the Fluid service, don't look here! Go check out Routerlicious.

Getting Started

You can build this service by running the following in the /server/routerlicious directory (NOT in this directory):

npm i -g pnpm
pnpm i
pnpm build

Afterwards, you can start and stop this service with the following commands in this directory:

pnpm start
pnpm stop

Configuration

Port

Tinylicious uses port 7070 by default. You can change the port number by setting an environment variable named PORT to the desired number. For example:

$env:PORT=6502
pnpm start

Logging

By default, tinylicious logs all output to stdout. You can adjust the logging level using the logger__level environment variable. For example, setting logger__level=error will log only errors. Using the level crit will hide all output.

Storage

The config.json file can be used to configure the Tinylicious service.

ParameterDescriptionDefault
db.inMemoryBoolean indicating whether ops are stored in memory or to disktrue
db.pathIf db.inMemory is false the folder on disk to store the ops"/var/tmp/db"
storageStorage path for snapshots"/var/tmp/tinylicious"

See config.json for more settings and their defaults.

FAQs

Package last updated on 17 Apr 2026

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