NAPI RS Support for serverless Edge runtimes

[aaronvg]

Some edge runtimes only have a limited number of node APIs available.

For example, vercel's runtime does not have the fs API:
https://nextjs.org/docs/app/api-reference/edge#unsupported-apis

I noticed the index.js script generated by the template napi-rs project has a require('fs') which crashes in these runtimes:

/* auto-generated by NAPI-RS */

const { existsSync, readFileSync } = require('fs')
const { join } = require('path')

const { platform, arch } = process

let nativeBinding = null
let localFileExisted = false
let loadError = null

function isMusl() {
  // For Node 10
  if (!process.report || typeof process.report.getReport !== 'function') {
    try {
      const lddPath = require('child_process').execSync('which ldd').toString().trim()
      return readFileSync(lddPath, 'utf8').includes('musl')
    } catch (e) {
      return true
    }
  } else {
    const { glibcVersionRuntime } = process.report.getReport().header
    return !glibcVersionRuntime
  }
}

switch (platform) {
  case 'android':
    switch (arch) {
      case 'arm64':
        localFileExisted = existsSync(join(__dirname, 'baml-core-napi.android-arm64.node'))
        try {
...

The script uses fs mainly to check for android-related binaries, which are not relevant in these edge function environments. Is there a way to remove that from the generated index.js? I'm trying to avoid having to edit the file.

[Brooooooklyn]

The edge runtime doesn't support the native addon, I will support it in the wasm target.

[aaronvg]

Oh interesting, is that easier than potentially creating a build that does not depend on the unsupported apis?

Also, so far we are loving this napi-rs. We were using neon and the release process left much to be desired. This just works.