Hi @ianhi, thanks a lot for your review!

I solved the merge conflict. This was due to an update of the dependencies in yarn.lock. When installing the project to run it on my machine, npm found some vulnerabilties. I ran npm audit fix and npm audit fix --force, which seems to also have updated the yarn.lock file. I had to re-run the commands just now due to vulnerabilities. I do not like using --force commands ; I hope the CI will catch any potential issue.

I also had this error when running npm run dev:

⨯ ERROR: This build is using Turbopack, with a webpack config and no turbopack config.

The solution was:

Adding an empty turbopack config to silence the Next.js 16 Turbopack error. The MDX plugin likely adds a webpack config.

Regarding your comments:

It makes me wish it was available on even more platforms, including my beloved juptyerlab :)

Indeed, having such an extension for opening scientific files on Jupyterlab might be beneficial. I do not use myself this environment often, as I spend most of my time in VSCode. I wonder if some of the code of the current extension might be reusable. When I have more time I should explore this!

My answers to points 1-4:

1. Good observation. Indeed I made these screenshots a long time ago. The UI did not change a lot since then, so I did not update them. Unless there is a new breaking change, I think keeping the current ones is fine, if it's OK for you.
2. Done ✅. Updated from 2025-12-16 (initial article writing time) to 2026-02-08 (the day I write this comment)
3. I used an HTML table because the markdown one does not render, for some reason (cf screenshot below)
4. Done ✅. I used the same title as the blog post itself: Exploring Scientific Data Files in VS Code with Xarray

it might be nice to include a small picture up towards the top - it could help the tldr hit a little harder, but not neceessary. Or you can rmeove the TLDR. the problem statement is already quite compelling.

I would prefer to keep the TLDR section so that people who don't read articles in entirety but click on them to read the first lines still get some information out of it, if it's OK for you.

Regarding the picture: I added the logo of the extension (it does not take too much place, and fits on one screen with the TLDR section) as well as the download links. So the first screen of reading looks like a "home page".

This is fairly geo focused. does it work well with data from another field (e.g. an ome-zarr? https://idr.github.io/ome-ngff-samples/

When I wrote the extension, my original goal was to be able to open and have an overview of the structure of any file openable by xarray. So if ome-zarr is based on Zarr, and since the extension can open a Zarr store thanks to xarray, I would say it should work in theory. I tried to download a zarr from https://idr.github.io/ome-ngff-samples/ but did not succeed (eg when clicking on BR00109990_C2.zarr I see an error "NoSuchKey"). If you have a sample I can download, I can check (currently the extension can only open Zarr stores stored locally on the filesystem ; it is not possible to do so from remote sources)

If you have any other comment regarding the updated version please tell me!