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
{{ message }}
Repository navigation
@sei-js/precompiles: sei and seiTestnet chain exports missing from source, will be dropped on next release #314
The published v2.1.2 dist exports sei, seiTestnet, and seiDevnet chain definitions from @sei-js/precompiles, but these are not present in the current source. The dist is a stale artifact inherited from the @sei-js/evm rename and was never rebuilt from the new source. When the package is next built and published, these exports will silently disappear.
Details
packages/precompiles/src/viem/chain.ts currently only exports seiLocal:
But the published v2.1.2 dist (dist/types/viem/chain.d.ts) declares:
exportdeclareconstsei: { ... };// mainnet, chain ID 1329exportdeclareconstseiTestnet: { ... };// testnet, chain ID 1328exportdeclareconstseiDevnet: { ... };// devnet, chain ID 713715exportdeclareconstseiLocal: { ... };// local, chain ID 713714
The rename commit (b888b94e) carried over a stale dist from @sei-js/evm which had these definitions. The source for @sei-js/evm also only had seiLocal — so these were already stale before the rename.
Impact
Any project importing chain config from @sei-js/precompiles:
import{sei,seiTestnet}from'@sei-js/precompiles';
works today against the published package but will break silently on the next release when the package is rebuilt from source.
Suggested fix
Add sei, seiTestnet, and seiDevnet back to packages/precompiles/src/viem/chain.ts explicitly, so the exports are intentional and version-controlled:
Thank you for opening this issue and taking the time to share your thoughts.
We’d love to keep moving this forward, but we need a bit more information from you.
Please add any additional details within the next 2 day(s) so we can continue collaborating on a solution together.
If we don’t hear back, the issue will close automatically — but you’re always welcome to reopen it when you’re ready.
Closing because the regression premise is incorrect. I verified npm releases 2.1.0–2.1.2 export only seiLocal; sei, seiTestnet, and seiDevnet were never published. Commit 441daea9 was on closed, unmerged #300. The valid API gap is being handled as a new feature with current Seiscan URLs and export tests.
Activity
github-actions commentedon Aug 6, 2026
Thank you for opening this issue and taking the time to share your thoughts.
We’d love to keep moving this forward, but we need a bit more information from you.
Please add any additional details within the next 2 day(s) so we can continue collaborating on a solution together.
If we don’t hear back, the issue will close automatically — but you’re always welcome to reopen it when you’re ready.
alexander-sei commentedon Aug 15, 2026
Closing because the regression premise is incorrect. I verified npm releases 2.1.0–2.1.2 export only
seiLocal;sei,seiTestnet, andseiDevnetwere never published. Commit441daea9was on closed, unmerged #300. The valid API gap is being handled as a new feature with current Seiscan URLs and export tests.