Registry / communication / prismarine-web-client

prismarine-web-client

library1.6.0jsnpmunverified

Prismarine Web Client is a browser-based Minecraft client that allows users to connect to and interact with Minecraft servers directly from a web page. It leverages the `mineflayer` library for high-level bot API interactions and `prismarine-viewer` for 3D world rendering within the browser. The current stable version is 1.6.0, with releases appearing somewhat frequently, indicating active development. A key differentiator is its ability to run entirely client-side in a web browser, connecting to standard Minecraft TCP servers via an intermediary WebSocket-to-TCP proxy that is bundled and managed by the CLI tool. This package is primarily distributed as a globally installable command-line tool that serves the client application, rather than a library intended for direct `import` into other JavaScript projects for code-level integration. Developers can interact with the running client's core functionalities, such as the `bot` instance and `viewer` for debugging and custom extensions, through global `window` objects.

communication http-networking web-framework

npm install prismarine-web-client

github ↗package ↗

INSTALL

IMPORT

SIG · PRISMARINE-WEB-CLI

prismarine-web-client

communicationjavascriptv1.6.0

Install

—

Import

—

Disk

—

Pass rate

0/ 6

Env Coverage0 / 6

glibc

18–22

musl

18–22

Install & Compatibility

Where this runs

tested against v? · npm install

Install × environment matrix

Each cell = how many times install + import succeeded across repeated harness runs. Partial = flaky.
glibc = Debian/Ubuntu slim · musl = Alpine Linux

musl

node 18–226 runs

build_error

glibc

node 18–226 runs

build_error

Code

Verified usage

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

bot

✓ window.bot

✗ import { bot } from 'prismarine-web-client'

The `bot` instance is exposed globally in the browser environment served by the client, not typically imported as a module from the package itself.

viewer

✓ window.viewer

✗ import { viewer } from 'prismarine-web-client'

The 3D viewer instance is exposed globally in the browser environment for debugging and interaction.

debugMenu

✓ window.debugMenu

✗ import { debugMenu } from 'prismarine-web-client'

The `debugMenu` object is exposed globally for extending and customizing the client's debug capabilities.

Demonstrates how to globally install, run, and then interact with the served Minecraft web client via browser console commands.

npm install -g prismarine-web-client # Run the client, which starts a web server and proxy prismarine-web-client # Open your browser and navigate to the client. Typically: # http://localhost:8080 // --- Interact with the client in your browser's developer console --- // Example: Send a chat message // window.bot.chat('Hello from prismarine-web-client!'); // Example: Make the bot jump // window.bot.entity.position.y += 5; // Example: Find a diamond ore block within 256 blocks // const diamondOrePos = window.bot.findBlock({ // matching: (block) => block.name === 'diamond_ore', // maxDistance: 256 // }); // if (diamondOrePos) { // console.log('Diamond ore found at:', diamondOrePos.position); // } else { // console.log('No diamond ore found nearby.'); // }

prismarine-web-client --version

Debug

Known issues

gotchaThe `prismarine-web-client` requires an intermediary WebSocket proxy (automatically handled by the CLI tool) to translate browser WebSocket connections to standard Minecraft TCP server connections. Direct connection to TCP servers from the browser is not possible due to browser security restrictions.

fix

Ensure the `prismarine-web-client` CLI is running correctly, as it provides the necessary proxy and web server for the client.

affects: >=1.0.0

gotchaCore API objects like `bot`, `viewer`, `mcData`, `worldView`, `Vec3`, and `debugMenu` are exposed as global variables on the `window` object within the served browser application (e.g., `window.bot`) for debugging and direct interaction. Attempting to `import` these directly as modules from the `prismarine-web-client` npm package will not work as expected.

fix

Access these objects directly via the `window` global in the browser's developer console or in custom scripts injected into the web page after the client has loaded.

affects: >=1.0.0

gotchaWhen developing locally using `npm start`, the Webpack build process will recompile the client application on every file save, which the README notes can take up to 5 seconds per change. This can significantly slow down the development feedback loop.

fix

Consider disabling auto-saving features in your Integrated Development Environment (IDE) or exploring Webpack configuration options for more granular control over rebuild triggers to optimize the development experience.

affects: >=1.0.0

Errors

Common errors & fixes

ReferenceError: bot is not defined

The `bot` object (or `viewer`, `mcData`, etc.) is accessed in the browser console before the client application has fully initialized or before the `window` global has been populated with these objects.

fix

Ensure the web client is fully loaded in your browser and that you are interacting with the correct browser window's developer console. Verify access via `window.bot`.

WebSocket connection to 'ws://localhost:XXXX/' failed: WebSocket is closed before the connection is established.

The `prismarine-web-client` CLI tool, which acts as both the web server and the WebSocket-to-TCP proxy, is not running, or a network configuration (e.g., firewall) is blocking the connection to `localhost`.

fix

Verify that `prismarine-web-client` is running in your terminal and listening on the expected port (default `8080`). Check for any local firewall rules or network issues preventing connection to `localhost`.

Cannot find module 'prismarine-web-client' (e.g., in a Node.js project or another browser bundle)

The `prismarine-web-client` npm package is primarily designed as a standalone application that serves a web client. It is not typically intended for programmatic `import` into other Node.js or browser projects in the usual module fashion. Its core functionalities are exposed as globals within its *own* served browser environment.

fix

To run the client, use the global installation and execution commands: `npm install -g prismarine-web-client` followed by `prismarine-web-client`. If you intend to use underlying functionalities like the Minecraft client API or 3D viewer programmatically in a separate project, install and import `mineflayer` or `prismarine-viewer` directly.

Upgrade

Version history

1.6.0latest on npm

Audit

Dependencies

mineflayerrequiredProvides the high-level Minecraft client API for bot interactions.

prismarine-viewerrequiredHandles 3D world rendering within the browser environment.

Agent activity

16 hits · last 30 days

node

OpenAI (training)

Resources

githubhttps://github.com/PrismarineJS/prismarine-web-client ↗

packagehttps://www.npmjs.com/package/prismarine-web-client ↗