Client Installation

Installation Paths

• Use in a browser when you want the fastest way to start writing without installing anything.
• Install as a PWA when you want an app-like shell with browser-managed updates.
• Run locally from the repo or a local build when you need a local development or self-hosted workflow.
• Use standalone modules when you only want the reusable client, editor, or renderer packages.

Quick Choice Guide

Use the browser route if you want immediate access with no setup. Use the PWA route if you want a dedicated window and installable shell. Use the local route if you need development control, local hosting, or a private self-managed deployment. Use standalone modules if you are embedding MdWrk surfaces into another product or internal tool.

Workspace Client Package

The publishable client package is:

@mdwrk/mdwrkspace

The split reusable packages start with:

@mdwrk/markdown-editor-react
@mdwrk/markdown-renderer-react
@mdwrk/markdown-renderer-core

For package discovery and published versions, use the organization page:

https://www.npmjs.com/org/mdwrk

Notes

Bundled extensions ship with the client build. External installable extensions follow the signed-manifest and trust-policy path documented in the extension docs. Published dates and statuses control whether installation docs appear on the lander at all, so draft installation notes can stay private until they are ready.