fix: keep constant offset up to date

[mattermoran]

fixes an issue where stale analysis results would incorrectly rewrite address calculations

context: after upgrading to fastly js v4 with aot the app would fail during rendering in a preact hook. tracked it down to a bound function receiving a number instead of an object. ok that's weird so digging more led here :)

as you see here when the offset changes the work queue can miss revisiting code that's using it so later it just ends up using the old offset

the test reproduces the issue without needing to run full fastly with preact etc

let me know if you'd like to fix it in a different way but it uses the same pattern already used in eval.rs

with this patch my app happily renders :)

[cfallin]

Thanks very much for tracking this down! Yes, indeed, this was an analysis dependency-management bug and the fix looks good.

I'll cut a new release with this fix. I don't control the downstream Fastly SDK anymore so someone else will need to pick up the version bump details as needed there.

[mattermoran]

thank you! once 0.5.1 is out, I can submit a bump pr on fastly side

[cfallin]

@mattermoran weval 0.5.1 has now been published to artifacts here, to crates.io, and to NPM (local confirmation after npm publish; seems it is still processing and isn't appearing on the registry yet though).