Skip to content

Advanced components

Lunchbox 2 custom components have some features built in for advanced usage.


The attach attribute works the same way in Lunchbox as it does in React, namely:

You can set attach as an attribute on a Lunchbox component and in most cases (see below for exceptions) that component's instance will be set as the parent's instance[attachValue].

For example, this:

<!-- `geometry` and `material` are attached automatically in Lunchbox. -->
<!-- This is for illustration only. -->
    <box-geometry attach="geometry"></box-geometry>
    <mesh-basic-material attach="material"></mesh-basic-material>

maps to this in ThreeJS:

import * as THREE from 'three';

const mesh = new THREE.Mesh();
const boxGeometry = new THREE.BoxGeometry();
mesh.geometry = boxGeometry; // <-- this is the `attach="geometry"` on the box-geometry component

const material = new THREE.MeshBasicMaterial();
mesh.material = material; // <-- this is the `attach="material"` on the mesh-basic-material component


attach comes in useful with loaders, which have their own special behavior in Lunchbox.

Any component ending with -loader (<texture-loader>, for example) will do the following in Lunchbox:

  1. Execute its load method, passing its src attribute as the URL
  2. Save the result of its load method to its loaded property
  3. (Optional, if attach attribute provided) Attach the loaded result to the parent

For example, this is how to load a texture in Lunchbox:

        <!-- Load the ThreeJS favicon and attach as a map -->

Special arguments

Sometimes, you need to access the scene, camera, etc in args. For example, after extending OrbitControls:

<!-- We need the camera and DOM element as args here -->
<orbit-controls args="[]"></orbit-controls>

Lunchbox has a few shortcuts built into args - you can pass any of the following strings:

$cameraThe <three-lunchbox> container's camera.
$sceneThe <three-lunchbox> container's scene.
$rendererThe <three-lunchbox> container's renderer.
$domElementThe <three-lunchbox> container's renderer's DOM element.

For example, this will start OrbitControls correctly:

<!-- We need the camera and DOM element as args here -->
<orbit-controls args="[&quot;$camera&quot;, &quot;$domElement&quot;]"></orbit-controls>

Note the &quot; characters - this is a temporary workaround while more robust parsing is being worked on.