tpmjs/packages/package-executor
Ajax Davis 14b64f0320 fix: remove VM2 sandboxing to resolve Next.js build errors
**VM2 Removal:**
- Remove VM2 dependency from package-executor
- Rewrite executor to use direct package execution with require()
- Add TODO comment for future sandboxing implementation

**Why this change:**
- VM2 requires runtime filesystem access to bridge.js which doesn't work with Next.js Turbopack bundling
- Even marking as serverExternalPackages fails because VM2 uses hardcoded file paths
- Direct execution allows builds to complete while we find Next.js-compatible sandboxing solution

**Next Steps:**
- Implement proper sandboxing with isolated-vm or similar Next.js-compatible solution
- Add security measures for package execution
- Consider moving package execution to separate microservice

This unblocks CI/CD while maintaining playground functionality.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
2025-11-30 00:57:32 +10:00
..
src fix: remove VM2 sandboxing to resolve Next.js build errors 2025-11-30 00:57:32 +10:00
package.json fix: remove VM2 sandboxing to resolve Next.js build errors 2025-11-30 00:57:32 +10:00
tsconfig.json feat: add interactive tool playground with AI-powered execution 2025-11-30 00:36:05 +10:00