chore(lapis-e2e): reenable test that broke since fetch automatically decompresses zstd now

[fengelniederhammer]

resolves #1423

PR Checklist

- [ ] All necessary documentation has been adapted.

• The implemented feature is covered by an appropriate test.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Preview	Comments	Updated (UTC)
lapis	Ready	Preview	Comment	Dec 11, 2025 10:21am

[Copilot]

Pull request overview

This PR re-enables a previously skipped end-to-end test that was failing due to Node.js's fetch automatically decompressing zstd responses as of version 24. The test now verifies the decompressed content instead of checking for zstd encoding.

• Removed the it.skip wrapper to re-enable the test
• Updated test assertions to validate decompressed content based on response type (SEQUENCES, TREE, or METADATA)
• Added a comment explaining the behavioral change in Node.js 24

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[github-actions]

There is no change in the changelog. This PR will not produce a new releasable version.

[fhennig]

Ohh, great that you found out what the issue was! But I'm not sure that the test is useful now, because how does it distinguish between

• the compression was automatically decompressed by fetch
• there was no compression in the first place
  ?

[fengelniederhammer]

Ohh, great that you found out what the issue was! But I'm not sure that the test is useful now, because how does it distinguish between

* the compression was automatically decompressed by fetch

* there was no compression in the first place
  ?

The response headers are still a good indication. And it's still better than not testing this at all.

[fhennig]

Ah I didn't realize/read well enough, that we check the headers. Ok then! LGTM