Using process.cwd is problematic

[segevfiner]

The cwd is something that is for the user to use and not necessarily where the app files are, the code should use __dirname instead, possibly correcting for the relative path of where pino gets bundled into the root of the out dir.

[segevfiner]

Ohhh great, and the ESM fallback is also not working and throwing: Uncaught SyntaxError: Cannot use 'import.meta' outside a module due to using import.meta inside new Function as far as I can tell...

[segevfiner]

And building pino to ESM with esbuild fails Error: Dynamic require of "os" is not supported due to evanw/esbuild#1921.

Why oh why does the JS ecosystem suck so bad...

[segevfiner]

Trying to generate different code depending on initialOptions.format seems to fail as import.meta.url causes esbuild to interpret the resulting pino.js code wrong and think it is ESM or something so it fails to find it's exports... We might need a virtual module to workaround this... Perhaps using a virtual module in the first place and requiring the user to import it is simpler anyhow, it also means you won't have to deal with sourcemaps which are currently broken for the pino.js module due to adding code to it...

Code I tried

        if (currentBuild.initialOptions.format === 'esm') {
          functionDeclaration = `
            function pinoBundlerAbsolutePath(p) {
              return new URL(p, import.meta.url).pathname;
            }
          `
        } else {
          functionDeclaration = `
            function pinoBundlerAbsolutePath(p) {
              return require('path').join(__dirname, p);
            }
          `
        }