fs methods should expose error.code

[leoortizz]

Is your feature request related to a problem? Please describe:

When writing a file to a non-existing directory, the error thrown does not expose the error code, making it hard to handle the error.

try {
  await webcontainer.fs.writeFile('non-existent-path/new-file.ts', content);
} catch (err: any) {
  console.log(error.code) // undefined
}

Describe the solution you'd like:

The error thrown should match Node.js's fs errors, at least exposing error.code to allow error handling.

try {
  await webcontainer.fs.writeFile('non-existent-path/new-file.ts', content);
} catch (err: any) {
  if (error.code === 'ENOENT') {
    await webcontainer.fs.mkdir('non-existent-path', {
      recursive: true,
    });

    await webcontainer.fs.writeFile('non-existent-path/new-file.ts', content);
  }
}

Describe alternatives you've considered:

No response

Additional context:

No response

[Nemikolh]

Hey @leoortizz ! This is a pretty nice idea, I like it a lot. I'll add this to our internal tracking system.