### Run TodoMVC Project Locally

Source: https://github.com/metosin/vrac/blob/main/example/todomvc/README.md

Installs project dependencies and starts the development server for the TodoMVC application using npm and Shadow-CLJS. The application will be accessible via a local link (http://localhost:3000) after compilation.

```shell
npm install
npm start
```

--------------------------------

### Run Vrac + Si-frame Development Server

Source: https://github.com/metosin/vrac/blob/main/example/si-frame-simple/README.md

Instructions to set up and run the development server for the Vrac + Si-frame project. This command installs dependencies and starts Shadow-CLJS, making the application accessible via a local URL.

```shell
npm install
npm start
```

--------------------------------

### Run Vrac Project Locally with npm

Source: https://github.com/metosin/vrac/blob/main/example/test-app/README.md

Instructions to install dependencies and start the Vrac application using npm. This command will initiate Shadow-CLJS compilation and serve the application, typically accessible via http://localhost:3000.

```shell
npm install
npm start
```

--------------------------------

### Run Vrac + React 19 Development Server

Source: https://github.com/metosin/vrac/blob/main/example/react-interop/README.md

Installs project dependencies and starts the Shadow-CLJS development server for the Vrac + React 19 application. The application will be accessible via a local URL displayed in the console after compilation.

```shell
npm install
npm start
```

--------------------------------

### Build TodoMVC Project for Production

Source: https://github.com/metosin/vrac/blob/main/example/todomvc/README.md

Compiles the TodoMVC application for production using npm, generating an optimized build. A report describing the size of different parts is available in `public/js/report.html`.

```shell
npm run release
```

--------------------------------

### Build Vrac + Si-frame for Production

Source: https://github.com/metosin/vrac/blob/main/example/si-frame-simple/README.md

Command to compile the Vrac + Si-frame project for production. After compilation, a size report is generated in `public/js/report.html`.

```shell
npm run release
```

--------------------------------

### Build Vrac Project for Production

Source: https://github.com/metosin/vrac/blob/main/example/test-app/README.md

Command to compile the Vrac application for production, generating optimized assets. A size report will be available at `public/js/report.html`.

```shell
npm run release
```

--------------------------------

### Build Vrac + React 19 for Production

Source: https://github.com/metosin/vrac/blob/main/example/react-interop/README.md

Compiles the Vrac + React 19 project for production, generating optimized assets. A detailed report on the size of different parts of the build is available in 'public/js/report.html'.

```shell
npm run release
```

--------------------------------

### Vcup Property Naming for Event Handlers

Source: https://github.com/metosin/vrac/blob/main/doc/vcup-properties.md

Vcup properties with the `on` namespace refer to events. The keyword name matches the event name, and its value is an event handler function.

```Clojure
:on/click
```

--------------------------------

### Vcup Property Naming for HTML Attributes

Source: https://github.com/metosin/vrac/blob/main/doc/vcup-properties.md

Vcup properties with the `a` namespace refer directly to HTML attributes. The keyword name matches the HTML attribute name as specified by Mozilla Developer Network.

```Clojure
:a/for
```

--------------------------------

### Vcup Property Naming for DOM Element Properties

Source: https://github.com/metosin/vrac/blob/main/doc/vcup-properties.md

Vcup properties with the `p` namespace refer to DOM element properties. The keyword name matches the DOM property name. Unnamespaced keywords can also refer to DOM properties if no other rule applies.

```Clojure
:p/htmlFor
```

--------------------------------

### Vcup Property Naming for Unnamespaced Keywords

Source: https://github.com/metosin/vrac/blob/main/doc/vcup-properties.md

Unnamespaced keywords have varying meanings: they can be Vrac-specific properties (`:style`, `:class`, `:ref`), custom data attributes (`:data-*`), SVG/MathML attributes, or DOM element properties (equivalent to `:p/*`).

```Clojure
:style
:class
:ref
:data-testid
:htmlFor
```

--------------------------------

### Vcup Property Letter Case for DOM Element Properties

Source: https://github.com/metosin/vrac/blob/main/doc/vcup-properties.md

Vrac does not modify letter case for DOM element properties. Names are used as specified in DOM API documentation, supporting both namespaced (`:p/`) and unnamespaced forms.

```Clojure
:p/readOnly
:readOnly
:p/tabIndex
:tabIndex
:p/autocorrect
:autocorrect
```

--------------------------------

### Vcup Property Letter Case for Event Names

Source: https://github.com/metosin/vrac/blob/main/doc/vcup-properties.md

Vrac does not modify letter case for event names. Event names are used exactly as specified in the Web API documentation.

```Clojure
:on/dblclick
:on/keydown
:on/fullscreenchange
```

--------------------------------

### Vcup Property Letter Case for HTML Attributes

Source: https://github.com/metosin/vrac/blob/main/doc/vcup-properties.md

Vrac does not modify letter case for HTML attributes. The attribute names are used exactly as specified in HTML standards.

```Clojure
:a/readonly
:a/tabindex
:a/accept-charset
```

=== COMPLETE CONTENT === This response contains all available snippets from this library. No additional content exists. Do not make further requests.