Do we want serious unit tests? Should we collect (on #working-with-data) reference files that pose various problems?

Yeah, we likely want unit tests which I can add to stdlib.

it would be great if the inspector could show the sheetNames as properties that we could open instantly?

when you say open, you mean refer to to pass to .sheet()? or do you mean where everything gets parsed ahead of time and exists as an enumerable property that shows up in the inspector?

like the `everything` cell below?

Maybe more like A below? (Showing the range and headers options as interactive in the inspector is probably not possible. @tophtucker has a nice spreadsheet range selector in https://observablehq.com/d/c93b05609691d7bb that might be used to build up from what we have now.)

Can we make this match the ZipArchive interface, which exposes a fileNames enumerable property that is shown by the inspector? https://observablehq.com/@observablehq/file-attachments https://github.com/observablehq/stdlib/blob/466685ddb0eb60c2192b550b5bc57d5ed0018baa/src/fileAttachment.js#L100-L110

You should mention ( and perhaps include an example ) that you can also parse .xlsx files inside zip archives.

Thanks, Andrew; added a section (at the bottom) describing this.

Thank you!