dynst

#1740

Yep, it got removed in #1941 in December but there hasn't been a new release cut. https://www.npmjs.com/package/@protobufjs/inquire

The integer classes recently got rewritten to use `bigint` so there are merge conflicts now.

Working ESM support is partially blocked on https://github.com/cosmos/cosmjs-types/issues/93 which might involve changes to how `cosmjs-types` exposes its API - either imports need to specify the `.js` / `.mjs` / `.cjs`...

Something more lightweight would be great. https://bundlephobia.com/package/@cosmjs/[email protected] And for the actual encryption and decryption, `@stablelib/xchacha20poly1305` is much smaller. (It used to appear unmaintained but suddenly released 2.0 with ESM support...

Great. Then for the file extension problem, can you just switch to using `tsc --noEmit` for type-checking followed by using a bundler for generating the build products instead? If it's...

Webpack is the legacy choice these days, its modern ESM support is very new, immature, and gated behind the `experiments` boolean. https://webpack.js.org/configuration/output/#type-modern-module I think Vite is the choice people gravitate...

Are these not good reasons `tsc` isn't ideal? https://github.com/microsoft/TypeScript/issues/49462 https://github.com/microsoft/TypeScript/issues/42151 Rewriting imports would be tedious, and you'd have to make sure never to add a new import that omitted the...

https://www.typescriptlang.org/docs/handbook/modules/theory.html#module-resolution-is-host-defined I can sort of respect their logic of "why TypeScript doesn’t modify import specifiers during emit," keeping `tsc` pure and magic-free in how it translates TypeScript to JS. Omitting...

Good news, `tsdown` is a transpiler with good defaults, that replaces the deprecated `tsup`, and is actually the underlying tool that Vite is planning to switch to (`rolldown`). https://voidzero.dev/posts/announcing-voidzero-inc Bad...