Skip to content

Conversation

@lukejans
Copy link

@lukejans lukejans commented Sep 22, 2025

  • Updated the extension to use the new download path structure which is now "{version_dir}/{binary}" instead of "{version_dir}/{asset_without_ext}/{binary}".
  • Fix the MacOS asset download by updating from a tar.gz archive to the .zip archive that is now being used by SuperHTML.

Additional Notes: All the assets that use an xz extension are not currently supported in the Zed extension API. The reason the team does not support xz downloads is because of the xz takeover that happened.

Partially addresses #4

- Update the extension to use the new download path structure which is now `"{version_dir}/{binary}"` instead of `"{version_dir}/{asset_without_ext}/{binary}"`.
- Update the MacOS asset download by updating from a `tar.gz` archive to the `.zip` archive that is now being used by SuperHTML.

All the assets that use an `xz` extension are not currently supported in the Zed extension API. The reason the team does not support xz downloads is because of the xz takeover that happened.
@WeetHet
Copy link
Collaborator

WeetHet commented Sep 22, 2025

Yeah, I know about the xz thing and I think it's just dumb tbh. Can we maybe do this by manually calling tar on Linux hoping the it's installed by default on most distros?

@lukejans
Copy link
Author

lukejans commented Sep 22, 2025

I’m sure we can find a solution similar to that, but I’m not familiar with the extent of control extension developers have. Here are some potential options to address this issue:

  • Use zed::DownloadedFileType::Uncompressed, then find a way of building it on the user’s platform.
  • Make the user install SuperHTML with their package manager (or by downloading an archive) and just make sure that superhtml is in their $PATH.

Aside from that, I’m not entirely sure what we could do. I’ll investigate other extensions to see if they use the same Uncompressed download type, as I’m quite certain the Java extension does.

It appears that the SuperHTML dev is aware of the changes breaking many tools that relied on the specific release style. Homebrew/homebrew-core#245261

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants