---
title: "TypeScript Node"
description: "Make your complex designs easier with the help of TypeScript Node. Learn how to use Typescript Node Efficiently"
url: https://help.beegraphy.com/en/articles/101-typescript-node
collection: "Tutorial"
updated: 2026-01-29
language: en
---

# TypeScript Node

Make your complex designs easier with the help of TypeScript Node. Learn how to use Typescript Node Efficiently

The **TypeScript Node** in BeeGraphy is a scripting node that lets users write **TypeScript code directly inside the BeeGraphy editor**. It acts as a bridge between visual node-based workflows and text-based programming.

### What it is?

Normally, in BeeGraphy, you build things by **connecting nodes -** one node makes a line, another offsets it, another rotates it, and so on.  
The TypeScript Node is different: it is like a **blank workspace** where you can code instructions like:

-   _Do this step repeatedly_
    
-   _If this condition is true, do one thing; otherwise, do another_
    
-   _Create something using a formula instead of manual steps_
    

So instead of manually building long chains of nodes, you can **explain the logic once in code**, and BeeGraphy follows it. All the complex geometry gets compacted in one single programming node.

### What problem TypeScript solves?

The TypeScript Node helps when:

-   A visual node setup becomes **too crowded or confusing**
    
-   You need **repetition** (like creating many points, lines, or shapes in a pattern)
    
-   You want **precise control using math or rules**
    
-   You want BeeGraphy to **react intelligently** to inputs
    

For example:

-   Generating points in a mathematical sequence
    
-   Automatically creating geometry based on conditions
    
-   Writing your own small “tools” inside BeeGraphy
    
-   Managing complex data cleanly without dozens of nodes
    

### Why TypeScript specifically?

TypeScript is like **JavaScript with safety checks**. It helps catch mistakes early and makes scripts easier to understand, especially as they grow bigger. Even beginners benefit because it:

-   Makes inputs and outputs clearer
    
-   Reduces errors
    
-   Keeps complex logic organized
    

The TypeScript Node lets you **tell BeeGraphy** how to build **precise, programmable, and highly customizable design logic**.

![](https://staticfiles.gleap.io/gattachments/OOJyb1KmjutDcYlpRYhHD47cwTmzrwLcEE2JwymCQmDD7YbM5wYMqki9kKseqpbZnddHnxTxzZg.png)

## How to Use TypeScript Node?

_Add the TypeScript Node_

-   Open your Model in **BeeGraphy**
    
-   Search for **Scripting Node (JS/TS)** or **TypeScript Node or** Drop it onto the canvas from the Menu bar.
    
-   You’ll see an option to edit. Click Edit to open the code editor. (Default code is written, you can delete it when you start using)
    

![](https://staticfiles.gleap.io/gattachments/aImrjnXTsKrnbFLKITflC7OSfcCYi1cFbcF3WnWnww3ri48AfvISrJhvFPo9hqAUUlILmLILtoq.png)

### **Script**

The **script** is where the actual logic is written. It defines **how the input variables are processed**, combined, or transformed.

Inside the script, you can:

-   Use the input variables
    
-   Apply mathematical rules or conditions
    
-   Generate or modify geometry
    
-   Organize complex behavior in a compact form
    

The script **does not directly interact with the canvas**. It only works with the data provided through input ports and prepares the result for output.

### **Input Port**

The **input port** is basically where **all the variables or parameters that you mention in the script can be added**. Moreover, any value you want to control from outside the code (numbers, geometry, booleans, lists) must be defined as an input port. Once added, these inputs can be connected from the canvas and used directly inside the TypeScript code.

-   The **port name must exactly match** the variable name used in the script
    
-   The **label** is only the name shown on the canvas
    
-   The **type** defines what kind of data the variable accepts (number, curve, solid, etc.) By default, the type is **Any**
    

This allows the script to stay reusable while the parameters remain adjustable visually.

### **Output Port**

The **output port** defines **what the script sends back to the canvas**.

Any value, geometry, or list created in the script must be exposed through an output port to be usable by other nodes.

-   Output ports act as **return values**
    
-   Their type should match what the script produces
    
-   They allow the scripted result to connect seamlessly to other BeeGraphy nodes. By default, the type is **Any**
    

Without an output port, the script’s result **on the output window** but cannot be used further,

![](https://staticfiles.gleap.io/gattachments/iQ18ykb6CpODOdnvqMZ70Cp6Qe8jY9NmlY7SeZeHjNVnGMxp4Gpju62d2PudzPE5Sh3XpbluTNw.png)

**Input Ports** provide variables → **Script** processes them → **Output Ports** return results

This structure keeps the workflow **clean, parametric, and scalable**, allowing complex logic to live inside the script while staying fully integrated with BeeGraphy’s visual system.
