ESM resolution issue

[kimurayu45z]

Error [ERR_MODULE_NOT_FOUND]: Cannot find module 'xxx/node_modules/@interchainjs/types/esm/auth' imported from xxx/node_modules/@interchainjs/types/esm/index.js
    at finalizeResolution (node:internal/modules/esm/resolve:275:11)
    at moduleResolve (node:internal/modules/esm/resolve:860:10)
    at defaultResolve (node:internal/modules/esm/resolve:984:11)
    at nextResolve (node:internal/modules/esm/hooks:748:28)
    at o (file://xxx/node_modules/@tailwindcss/node/dist/esm-cache.loader.mjs:1:69)
    at nextResolve (node:internal/modules/esm/hooks:748:28)

[jaeminDelightlabs]

I'm also running into this issue with @interchainjs/cosmos@1.21.0 and related packages (@interchainjs/encoding@1.20.0, @interchainjs/utils@1.21.0, @interchainjs/auth@1.21.0, etc.).

The published ESM files use extensionless relative imports like ./types/index or ./asserts, which blow up under Node/Vitest ESM with ERR_MODULE_NOT_FOUND:

Error: Cannot find module '.../@interchainjs/cosmos/esm/types/index'
imported from '.../@interchainjs/cosmos/esm/index.js'

Error: Cannot find module '.../@interchainjs/encoding/esm/ascii'
imported from '.../@interchainjs/encoding/esm/index.js'

This looks like a build pipeline issue — Node's ESM loader requires explicit file extensions on relative imports (unlike CJS), so specifiers like ./foo need to be ./foo.js or ./foo/index.js.

I confirmed that manually adding .js extensions to the published ESM files resolves the errors.

Environment: Node.js v24.13.0, Vitest 4.0.18, pnpm 10.5.0

Seems like this was introduced around #196 (the yarn → pnpm + makage migration), likely from the new build/publish pipeline rather than anything on the consumer side.

[2wheeh]

This could be fixed by setting restoreImportExtension on telescope config after resolving hyperweb-io/telescope#839,

[2wheeh]

Apart from the auto-generated codes by telescope, interchainjs already has more codes without correct extension and tsc doesn't do anything like adding extension while transpiling. makage (depending tsc for transpiling`) is in the same situation.

I guess these are the options:

1. migrating to some other build tool, adding .js while transpiling for ESM (esbuild, tsdown, zshy, ... )
2. keeping makage, adding .js extenstions for all imports in the codebase (or updating makage to handle this)

about option 1, zshy would be the easiest choice for interchainjs due to hyperweb-io/telescope#838 - esbuild based bundler, or tsdown need explict type keyword for type-only imports/exports, which telescope doesn't support at the moment.

[2wheeh]

@pyramation Would you be open to migrate to some other build tool? Or updating makage would be better?