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
In editors like VSCode, this means that most types imported from JSR are cast to any, and do not leverage the type safety of Viem.
Expected Behavior
No response
Steps To Reproduce
No response
Link to Minimal Reproducible Example
No response
Anything else?
It is my understanding that it comes from what JSR calls "slow types", and there isn't much we can do about it for now.
Fortunately, we can still use the package published on npm. But I'm curious to know if there are any plans going forward to make viem work with JSR, or if JSR's no-slow types policy is just too much at odds with Viem's strong type guarantees.
The text was updated successfully, but these errors were encountered:
I should also add for the sake of completeness that TypeScript 5.5 has separately introduced an --isolatedDeclarations compiler option that goes in the direction of JSR's slow types policy.
Check existing issues
Viem Version
2.21.50
Current Behavior
The JSR page of
viem
does not provide types for some modules (see the documentation for themainnet
chain definition).In editors like VSCode, this means that most types imported from JSR are cast to
any
, and do not leverage the type safety of Viem.Expected Behavior
No response
Steps To Reproduce
No response
Link to Minimal Reproducible Example
No response
Anything else?
It is my understanding that it comes from what JSR calls "slow types", and there isn't much we can do about it for now.
Fortunately, we can still use the package published on
npm
. But I'm curious to know if there are any plans going forward to makeviem
work with JSR, or if JSR's no-slow types policy is just too much at odds with Viem's strong type guarantees.The text was updated successfully, but these errors were encountered: