cyberia

library3.2.12jsnpmunverified

Cyberia CLI (v3.2.12) is the toolchain for the Cyberia MMO data layer, content pipeline, persistence, gRPC services, and ERC-1155 lifecycle on Hyperledger Besu. It is part of the Underpost Platform, with a sidecar-backed Node.js data engine. Released monthly, it integrates with hardhat, IPFS, and sprite-sheet generation. Unlike generic game engines, it is purpose-built for tokenized rendering layers and unified blockchain-object state.

devops

npm install cyberia

github ↗package ↗homepage ↗

INSTALL

IMPORT

SIG · CYBERIA

cyberia

devopsjavascriptv3.2.12

harness data pending

Install & Compatibility

Where this runs

No compatibility data collected yet for this library.

Code

Verified usage

Verified import paths — ran on the pinned version, not inferred.

cyberia

✓ npx cyberia <command>

✗ import cyberia from 'cyberia'

CLI tool, not a library; use npx or global install

CyberiaConfig

✓ import { CyberiaConfig } from 'cyberia/config'

✗ const CyberiaConfig = require('cyberia/config')

CommonJS via require works, but ESM is recommended for Node >=16

DataLayerClient

✓ import { DataLayerClient } from 'cyberia/data-layer'

✗ import DataLayerClient from 'cyberia'

Named export; default export is not available since v3

Initialize a new Cyberia project, set environment variables for Besu and IPFS, then build the data pipeline.

npx cyberia init my-cyberia-project cd my-cyberia-project export BESU_RPC_URL='http://localhost:8545' export IPFS_API_URL='http://localhost:5001' npx cyberia build echo 'Built content pipeline and deployed ERC-1155'

Debug

Known issues

breakingIn v3, the command 'cyberia build' replaces the previous 'cyberia compile' — 'compile' will error with 'command not found'

fix

Use 'cyberia build' instead of 'cyberia compile'.

affects: >=3.0.0 <4.0.0

deprecated'cyberia deploy' has been deprecated; use 'cyberia release' for new workflows

fix

Run 'cyberia release' instead of 'cyberia deploy'.

affects: >=3.1.0

gotchaThe package 'cyberia' is a CLI tool only; importing it as a library will yield no exports

fix

Use 'npx cyberia' or install globally. If you need programmatic access, import submodules like 'cyberia/config'.

affects: >=1.0.0

breakingWhen upgrading from v2, the configuration file format changed from JSON to YAML — existing configs will not be parsed

fix

Convert your cyberia.config.json to cyberia.config.yaml before using v3.

affects: >=3.0.0

Errors

Common errors & fixes

Error: Cannot find module 'cyberia'

Running 'require('cyberia')' or 'import' as a library import instead of using the CLI

fix

Run 'npx cyberia <command>' or install globally with 'npm install -g cyberia'.

cyberia: command not found

The CLI is not installed or not in PATH after installation

fix

Install globally: 'npm install -g cyberia'. If using npx, ensure npm >= 5.2.0.

Error: Unknown command: compile

Using the old 'compile' command that was renamed in v3

fix

Use 'cyberia build' instead.

Failed to load config: invalid yaml

Trying to use a JSON config file in v3 which requires YAML

fix

Rename cyberia.config.json to cyberia.config.yaml and convert content to YAML.

Upgrade

Version history

3.2.12latest on npm

Audit

Dependencies

hardhatrequiredERC-1155 lifecycle management and smart contract compilation

ipfs-http-clientrequiredAsset metadata and content addressed storage on IPFS

Agent activity

4 hits · last 30 days

node

Resources

githubhttps://github.com/underpostnet/engine-cyberia ↗

packagecyberia ↗

homepagehttps://github.com/underpostnet/engine-cyberia#readme ↗