PageSourceSearch

https://buerli.io/assets/js/0058b4c6.17759dbc.js

js buerli.io collected 2026-10-08 02:29:42 UTC 3,890 bytes, 1 lines download raw bytes

1"use strict";(globalThis.webpackChunkbuerli_io=globalThis.webpackChunkbuerli_io||[]).push([[849],{6164(e){e.exports=JSON.parse('{"version":{"pluginId":"default","version":"current","label":"Next","banner":null,"badge":false,"noIndex":false,"className":"docs-version-current","isLast":true,"docsSidebars":{"docs":[{"type":"link","href":"/docs/","label":"Introduction","docId":"intro","unlisted":false},{"type":"category","label":"Quickstart","items":[{"type":"link","href":"/docs/quickstart/wasm","label":"Getting started with WASM","docId":"quickstart/wasm","unlisted":false},{"type":"link","href":"/docs/quickstart/socketio","label":"Getting started with SocketIO","docId":"quickstart/socketio","unlisted":false}],"collapsed":true,"collapsible":true},{"type":"category","label":"API","items":[{"type":"link","href":"/docs/api/classcad","label":"@buerli.io/classcad","docId":"api/classcad","unlisted":false},{"type":"link","href":"/docs/api/react","label":"@buerli.io/react","docId":"api/react","unlisted":false}],"collapsed":true,"collapsible":true},{"type":"category","label":"Examples","items":[{"type":"link","href":"/docs/setup-backend/starters","label":"Buerli-starter","docId":"setup-backend/starters","unlisted":false},{"type":"link","href":"/docs/setup-backend/examples","label":"Buerli-examples","docId":"setup-backend/examples","unlisted":false}],"collapsed":true,"collapsible":true},{"type":"link","href":"/docs/changelogs/","label":"Changelogs","docId":"changelogs/changelogs","unlisted":false}]},"docs":{"api/classcad":{"id":"api/classcad","title":"ClassCAD","description":"This library connects Buerli with ClassCAD, the CAD engine: in the browser as WebAssembly (WASMClient), or a native engine through the ClassCAD server (SocketIOClient).","sidebar":"docs"},"api/react":{"id":"api/react","title":"React","description":"The React API provides bindings for classcad. It makes it easier to use the API in a reactive context and with components specifically. For the most part it helps you to manage and access drawing across the component tree.","sidebar":"docs"},"changelogs/changelogs":{"id":"changelogs/changelogs","title":"Changelogs","description":"","sidebar":"docs"},"intro":{"id":"intro","title":"Introduction","description":"Buerli is a powerful client-side development environment for building browser-based CAD applications. It is built on top of the ClassCAD engine and provides a set of tools and components to integrate easily with modern web environments.","sidebar":"docs"},"quickstart/socketio":{"id":"quickstart/socketio","title":"SocketIO","description":"This guide will show you how to build a simple Javascript application using the ClassCAD API with SocketIO. ClassCAD will run locally, or on a server and communicates with your application via the Socket.IO protocol. The guide assumes you have a basic understanding of the Javascript ecosystem.","sidebar":"docs"},"quickstart/wasm":{"id":"quickstart/wasm","title":"WASM","description":"This guide will show you how to build a simple Javascript application using the ClassCAD API with WASM. ClassCAD will entirely run inside the browser. With WASM ClassCAD can be hosted on a server, a CDN or bundled with your application. The guide assumes you have a basic understanding of the Javascript ecosystem.","sidebar":"docs"},"setup-backend/examples":{"id":"setup-backend/examples","title":"Examples","description":"A collection of examples showing various features and capabilities of buerli/ClassCAD. Each example focuses on a specific feature or use case. If you are searching for quick start templates you might better checkout the starters.","sidebar":"docs"},"setup-backend/starters":{"id":"setup-backend/starters","title":"Starters","description":"A collection of self-contained mini examples showing various features of Buerli, and how to employ them in a React context.","sidebar":"docs"}}}}')}}]);

Line numbers count LF bytes from the start of the resource, as the search results do. Vendor segments are library code the classifier recognised; they are stored but not indexed. Bytes are shown as Latin1 characters, one per byte.