You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A major limitations ghjk is facing right now is that hashfiles don't keep track of imports in ghjk.ts files. This means we can't invalidate the serialization cache when imported items change. This makes it difficult to iterate on local typescript files that ghjk.ts depends on.
A custom Deno runtime would allow us to hook into Deno's module resolution algorithm to get a perfect snapshot of exactly what was used. Bringing rust into the picture would ofcourse have relevance on a lot of other tickets but I recommend keeping most of the codebase in typescript similar to Metatype.
The text was updated successfully, but these errors were encountered:
A major limitations ghjk is facing right now is that hashfiles don't keep track of imports in
ghjk.ts
files. This means we can't invalidate the serialization cache when imported items change. This makes it difficult to iterate on local typescript files thatghjk.ts
depends on.A custom Deno runtime would allow us to hook into Deno's module resolution algorithm to get a perfect snapshot of exactly what was used. Bringing rust into the picture would ofcourse have relevance on a lot of other tickets but I recommend keeping most of the codebase in typescript similar to Metatype.
The text was updated successfully, but these errors were encountered: