Skip to content
Back to skills

Stackblitz Rate Limits

ASecurity

'WebContainer resource limits: memory, CPU, file system size, process

  • 2 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added November 11, 2026
developmenttypescriptnodegitsecurity

Works with

  • claude code

Security analysis

A92/100
  • mediumInstalls packages at runtime which could introduce malicious dependencies

Pro shows the line behind each finding and how to fix it

Scanned November 11, 2026

npx -y skills add pauldx/claudifying --skill stackblitz-rate-limits --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Stackblitz Rate Limits?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Stackblitz Rate Limits
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/pauldx-stackblitz-rate-limits/badge)](https://www.skillsdirectory.com/skills/pauldx-stackblitz-rate-limits)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: stackblitz-rate-limits
description: 'WebContainer resource limits: memory, CPU, file system size, process
  count.

  Use when working with WebContainers or StackBlitz SDK.

  Trigger: "webcontainer limits".

  '
allowed-tools: Read, Write, Edit
version: 1.0.0
license: MIT
tags:
- saas
- ide
- webcontainers
- stackblitz
compatibility: Designed for Claude Code
---
# StackBlitz Rate Limits

## Overview

WebContainer resource limits: memory, CPU, file system size, process count.

## Instructions

### Step 1: WebContainer Resource Limits

| Resource | Limit | Notes |
|----------|-------|-------|
| Memory | ~2GB | Shared with browser tab |
| File system | Ephemeral, in-memory | Lost on page refresh |
| Processes | Multiple concurrent | Each consumes memory |
| Network | HTTP only | No raw TCP/UDP sockets |
| npm packages | Most work | Native addons not supported |

### Step 2: Handle Memory Pressure

```typescript
// Monitor memory usage inside WebContainer
const proc = await wc.spawn('node', ['-e', `
  setInterval(() => {
    const mem = process.memoryUsage();
    const mbUsed = Math.round(mem.heapUsed / 1024 / 1024);
    if (mbUsed > 500) console.warn('High memory: ' + mbUsed + 'MB');
  }, 5000);
`]);
```

### Step 3: Optimize File System Size

```typescript
// Mount only essential files -- skip test files, docs, etc.
const productionFiles: FileSystemTree = {
  'package.json': { file: { contents: minimalPackageJson } },
  src: { directory: { /* only source files */ } },
  // Skip: tests/, docs/, .git/, large assets
};
await wc.mount(productionFiles);
```

## Error Handling

| Issue | Cause | Solution |
|-------|-------|----------|
| Tab crashes | OOM | Reduce mounted files, fewer deps |
| Slow npm install | Large deps | Use --prefer-offline, fewer packages |
| Process killed | Memory limit | Monitor with memoryUsage() |

## Resources

- [WebContainer Guides](https://webcontainers.io/guides/introduction)

## Next Steps

For security, see `stackblitz-security-basics`.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

View all in development →

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.