DocsBlog

Get Started

Components

Data Grid

Signals

Styling

Theming

↑↓Navigate
↵Select
EscClose
  • 1.8.0

  • Day

    Night

    Preview

    Switch mode
  • cerberus

    acheron

    elysium

    oceanus

Get Started
Components
Data Grid
Signals
Styling
Theming

Overview

Get StartedInstallationFAQContributing to Cerberus

AI

LLMS.txtContext-7

Presets

Theme Presets

FAQ

Frequently Asked Questions about Cerberus Design System

View as Markdown
Open this page in Markdown
Anthropic
Open in Claude
Ask questions about this page
OpenAI
Open in ChatGPT
Ask questions about this page

Why does the package path for react look weird?

The Cerberus packages are published under the @cerberus-design organization in NPM (due to the name cerberus being taken). However, in JSR, we use the @cerberus organization. We eventually plan on fully migrating to JSR when there is better support for the features we need.

The version paths are simply creating an alias to the @cerberus-design organization so that you can have consistent package naming across your project.

Everything should use the @cerberus organization in your code.

Why do I need to have a specific baseUrl in our tsconfig.json?

In order for our React components to know where to find the styled-system APIs, it needs to know where to look. By setting the baseUrl to the root of your project, we can use the styled-system import path without needing to know the exact location of the file.

On this page

  • Why does the package path for react look weird?
  • Why do I need to have a specific baseUrl in our tsconfig.json?
Edit this page on Github