Overview - @builder.io/sdks

@builder.io/sdks

7 days30 days

Latest CI Pipeline Executions

Fuzzy

Succeeded
ENG-11229-fix-context-prop-vue
714c49dc Update title in CUSTOM_COMPONENTS_MODELS_RESTRICTION from 'Hello World' to 'World' for consistency in component data.
17 days ago by floating-d...
Succeeded
ENG-11229-fix-context-prop-vue
714c49dc Update title in CUSTOM_COMPONENTS_MODELS_RESTRICTION from 'Hello World' to 'World' for consistency in component data.
20 days ago by floating-d...
Succeeded
ENG-11229-fix-context-prop-vue
714c49dc Update title in CUSTOM_COMPONENTS_MODELS_RESTRICTION from 'Hello World' to 'World' for consistency in component data.
23 days ago by floating-d...
Succeeded
ENG-11229-fix-context-prop-vue
58e8be6c Update Hello component template to use <h1> tag and include ng-content for better structure across multiple frameworks
23 days ago by floating-d...
Succeeded
ENG-11229-fix-context-prop-vue
3dc03194 Update Hello component across multiple frameworks to utilize context
23 days ago by floating-d...
Succeeded
ENG-11229-fix-context-prop-vue
9a41729a fix[gen2][vue]: correct comment capitalization in InteractiveElement for consistency in Builder context explanation
23 days ago by floating-d...
Succeeded
ENG-11229-fix-context-prop-vue
9a41729a fix[gen2][vue]: correct comment capitalization in InteractiveElement for consistency in Builder context explanation
23 days ago by floating-d...
Succeeded
ENG-11229-fix-context-prop-vue
52ee69a7 fix[gen2][vue]: update InteractiveElement to use state.targetWrapperProps for improved context handling
23 days ago by floating-d...
Failed
ENG-11229-fix-context-prop-vue
89245fca refactor[gen2][vue]: streamline comments in InteractiveElement for clarity on Builder context usage
24 days ago by floating-d...
Succeeded
ENG-11229-fix-context-prop-vue
21dcbebf fix[gen2][vue]: enhance InteractiveElement to pass Builder context to custom components
24 days ago by floating-d...
Failed
ENG-11229-fix-context-prop-vue
151b959b fix[gen2][vue]: pass Builder context to custom components in InteractiveElement
24 days ago by floating-d...
Failed
main
659cc99c fix[gen2]: try to not use a global isolate instance and create fresh instance for each request (#4210) ## Description - Current Architecture: It seems the SDK creates ONE Global Isolate (a single Virtual Machine) when the server starts, and reuses it for every single request (2000+ requests). - The Leak: The V8 engine inside that single Isolate is accumulating "Script Compilation" data, fragmentation, or hidden caches from running 2000 different closures. Eventually, the Isolate's heap limit (usually 128MB) explodes, or it leaks into the main process. **The Strategy:** 1. **Create** a fresh Isolate for *every single request*. 2. **Run** the code. 3. **Dispose** (Destroy) the Isolate immediately. This guarantees memory cleanup because the entire memory block is freed by C++. _Testing_ Notion doc for dev testing - https://www.notion.so/builderio/ENG-10865-testing-memory-leak-fix-2cb3d7274be5804988edd838631a6b62 _Screenshot_ - https://www.loom.com/share/e00e30234bf44a0bb08cabdea0b81b2e - Another Loom where I have showcased the chrome dev tools for the memory profiles in case of our fix - https://www.loom.com/share/bbf7aa018f6e47a6854620b0b11df6d7  --- > [!NOTE] > Switches Node runtime to create a fresh isolated-vm per request and dispose it after execution, addressing memory leaks; updates changeset to bump minor versions across SDKs. > > - **Node runtime (`packages/sdks/.../node-runtime.ts`)**: > - Create a new `ivm.Isolate` per request using stored `IsolateOptions` and dispose it in `finally`. > - Remove global `Context`/shared isolate; eliminate `setIsolateContext`/`getIsolateContext`. > - Update `setIvm` to accept optional options and store them for per-request use. > - **Release**: > - Changeset adds minor version bumps for multiple `@builder.io/*` SDKs and notes memory leak elimination. > > <sup>Written by [Cursor Bugbot](https://cursor.com/dashboard?tab=bugbot) for commit e3272211dd2d2f42213031c2122991b24aef48b5. This will update automatically on new commits. Configure [here](https://cursor.com/dashboard?tab=bugbot).</sup> 
2 months ago by floating-d...
Succeeded
vue-sdk-issue-fix-2
a2450cda update changesets for minor version releases and memory leak fixes and remove previous changeset
2 months ago by floating-d...
Failed
vue-sdk-issue-fix-2
a2450cda update changesets for minor version releases and memory leak fixes and remove previous changeset
2 months ago by floating-d...
Succeeded
vue-sdk-issue-fix-2
4cc701b3 Update the console logs
2 months ago by floating-d...
Failed
vue-sdk-issue-fix-2
4cc701b3 Update the console logs
2 months ago by floating-d...
Succeeded
vue-sdk-issue-fix-2
c5eebf80 add changeset for major version updates and memory leak fixes
2 months ago by floating-d...
Succeeded
vue-sdk-issue-fix-2
409a8be5 refactor(node-runtime): remove unused Context import for cleaner code - Eliminated the unused `Context` import from `isolated-vm` in the node-runtime file. - This change simplifies the code and improves readability by removing unnecessary dependencies. This refactor contributes to maintaining a clean and efficient codebase.
2 months ago by floating-d...
Failed
vue-sdk-issue-fix-2
409a8be5 refactor(node-runtime): remove unused Context import for cleaner code - Eliminated the unused `Context` import from `isolated-vm` in the node-runtime file. - This change simplifies the code and improves readability by removing unnecessary dependencies. This refactor contributes to maintaining a clean and efficient codebase.
2 months ago by floating-d...
Succeeded
vue-sdk-issue-fix-2
48fcf90a refactor(node-runtime): introduce per-request isolate options for improved memory management - Added `IVM_OPTIONS` to store isolate options, defaulting to a memory limit of 128. - Updated `setIvm` to accept and store options for each request, enhancing flexibility. - Modified `runInNode` to utilize stored options when creating isolates, ensuring consistent memory management. - Improved comments for clarity on the new approach and its benefits. This refactor aims to further optimize memory usage and isolate management in the node runtime.
2 months ago by floating-d...