[feature_request] Native VS Code extension modules fail to load - missing library validation entitlement

Google Antigravity
,
1

I maintain a VS Code extension (DBCode) that ships native Node.js modules for database connectivity (better_sqlite3.node, duckdb bindings, etc). These all work fine in VS Code, Cursor, Windsurf, and other VS Code forks, but fail to load in AntiGravity on macOS.

The error:

dlopen(.../better_sqlite3.node, 0x0001): code signature in 
'...better_sqlite3.node' not valid for use in process: mapping process 
and mapped file (non-platform) have different Team IDs

This happens because macOS Library Validation blocks loading native binaries signed by a different Team ID than the host application. VS Code and other forks handle this by including the com.apple.security.cs.disable-library-validation entitlement in their app signature, which allows extensions to load third-party native modules.

Without this entitlement, any extension that bundles native Node.js addons (.node files) will be broken on macOS. This affects quite a few extensions beyond mine - anything using native node binaries.

Could this entitlement be added to AntiGravity’s code signing configuration?

1 Like