Ah, I see!<p>So neon-bridge is a utility npm package I published that automates loading your Neon project (so it&#x27;s not the name of an example module). And the expectation is that you only have one Rust package (&quot;crate&quot; in Rust parlance) per Node package, which is why you don&#x27;t need to pass it the name of anything -- it&#x27;s looking for _the_ native module in the package, as opposed to _a_ native module.<p>However, that single Rust crate may have multiple modules in its implementation. They live in the src&#x2F; directory of your Neon project and are picked up by the Rust compiler and build tool.<p>And yes, deeeeefinitely need to get some docs going... :P