The NodeVMGlobalObject was attempting to override the GlobalObjectMethodTable with function pointers that weren't properly resolved, causing a null pointer dereference when eval() was called.
The fix is to not override the method table at all and inherit the parent class's implementation. This allows eval and other code generation features to work correctly.
The test still has a remaining issue with WebAssembly code generation blocking that needs to be addressed separately.
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
2ca19d4694