hash.js import issue with ESM: “does not provide an export named 'sha256'”

[bilou42]

Currently WharfKit packages (for example @wharfkit/session) assume a Node or bundler environment such as Vite or Webpack. When attempting to load them directly in the browser as ESM modules via a CDN like jsDelivr, the imports fail due to internal CommonJS dependencies such as hash.js.

Example:
import SessionKit from 'https://cdn.jsdelivr.net/npm/@wharfkit/session@1.6.1/+esm'

Error shown in console:
Uncaught SyntaxError: The requested module '/npm/hash.js@1.1.7/+esm' does not provide an export named 'sha256'

This happens because hash.js is CommonJS-only, but WharfKit’s generated ESM build expects named exports from it.

For lightweight dApps or static sites, it would be very useful to load WharfKit modules directly from a CDN without needing a bundler or build step — similar to how Anchor-Link supported pure browser ESM usage.

I understand WharfKit is designed for modern JS app environments, but adding browser-compatible builds would make it much easier to integrate with small web projects or simple dApp frontends that don’t use build tooling.

[aaroncox]

Ideally, we'd go through and update the 30-40 repositories and modernize their build processes so each could be imported individually (maybe even move to a monorepo). We can't justify spending that amount of time on something I don't think will get used that regularly, so below is sort of a stop-gap solution for now.

https://github.com/wharfkit/bundle

It's a library published as @wharfkit/bundle that includes the majority of commonly used packages. There's examples for both an iife import and an esm import in the ./public folder of the bundle. This bundle (esm) allows code like:

import {
  Chains,
  SessionKit,
  WalletPluginAnchor, 
  WalletPluginCloudWallet, 
  WalletPluginMetaMask, 
  WalletPluginTokenPocket, 
  WalletPluginWebAuthenticator, 
  WalletPluginWombat,
  WebRenderer
} from 'https://cdn.jsdelivr.net/npm/@wharfkit/bundle@0.1.1/+esm'

Let me know if that works for you.

In the future, time permitting, it'd be nice to properly distribute them as individual packages.