Skip to content

Deploy September 16, 2025#5615

Merged
canova merged 26 commits intoproductionfrom
main
Sep 16, 2025
Merged

Deploy September 16, 2025#5615
canova merged 26 commits intoproductionfrom
main

Conversation

@canova
Copy link
Member

@canova canova commented Sep 16, 2025

Changes:

[Markus Stange] Switch CSS back to using relative paths inside url(...) (#5594)
[Markus Stange] Use dynamic imports for jszip (#5593)
[Florian Quèze] Allow markers to provide a marker color. (#5607)
[Ryan Hunt] Update iongraph-web to latest version (#5606)
[Florian Quèze] Fix the color contrast of hovered colored markers. (#5609)
[Florian Quèze] Scale custom marker graphs on values within the committed range. (#5587)
[Markus Stange] Fix null marker stack substitution (#5613)
[Florian Quèze] Track context menus should be accessible from anywhere in the track (#5562)
[Markus Stange] Worker + compression cleanups (#5602)

mstange and others added 26 commits September 4, 2025 10:37
esbuild doesn't respect aliases for url() references in CSS files.
We could add a plugin which implements this mapping but it seems
fine to just change this to use relative URLs.
…rker.js.

This allows us to keep the worker file located close to the file
which uses it. It also makes it easier to have equivalent handling
in esbuild.
I r+ed their removal in #5584 because node supports CompressionStream,
but I forgot to ask for the fallbacks to be put back when we switched
back to using a worker.
This is basically picking the opposite direction of #5581.

With esbuild you can configure aliases, but it only respects them for
imports into JS. It doesn't respect the aliases for url() references in
CSS files. We could add a plugin which implements this mapping but it
seems easier (and maybe more idiomatic) to just change our CSS to use
relative URLs.
Once we switch to esbuild, this will fix #817. With Webpack it doesn't
appear to quite do it, maybe because of the type imports.

Bundle chunking with esbuild after this fix:

<img width="3120" height="1600" alt="Screenshot 2025-09-04 at 10 42
21 AM"
src="https://github.com/user-attachments/assets/d1579b79-4052-408e-9adf-25def19f74e5"
/>
iongraph now supports passing in line timings, so do that.
Also use the migration API.
iongraph now supports passing in line timings, so do that. Also use the
migration API.
We want stack-less "causes" whenever we want to filter out a
stack completely, for example because it doesn't contain the
focused function when we're applying a focus function transform.

Pre-TypeScript, we were already using this field that way, even
though it wasn't typed correctly.
We need to replace cause.stack even if convertStack returned null,
otherwise we have bad stack indexes sticking around.

The incorrect `if (stack)` was added during the TypeScript migration
in commit ed02f3f.

This restores the logic as it was before the migration.
@canova canova merged commit 32a583c into production Sep 16, 2025
17 checks passed
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.

4 participants