Make internal imports more friendly for users using ES Modules

[simonmcallister0210]

Context

A user noticed an error when trying to import the package when using ES Modules:

Error [ERR_UNSUPPORTED_DIR_IMPORT]: Directory import '/project/node_modules/.pnpm/[email protected]/node_modules/buffer/' is not supported resolving ES modules imported from /project/node_modules/.pnpm/[email protected]/node_modules/cognito-srp-helper/dist/esm/index.js
Did you mean to import [email protected]/node_modules/buffer/index.js?
    at finalizeResolution (node:internal/modules/esm/resolve:249:11)
    at moduleResolve (node:internal/modules/esm/resolve:908:10)
    at defaultResolve (node:internal/modules/esm/resolve:1121:11)
    at ModuleLoader.defaultResolve (node:internal/modules/esm/loader:396:12)
    at ModuleLoader.resolve (node:internal/modules/esm/loader:365:25)
    at ModuleLoader.getModuleJob (node:internal/modules/esm/loader:240:38)
    at ModuleWrap.<anonymous> (node:internal/modules/esm/module_job:85:39)
    at link (node:internal/modules/esm/module_job:84:36) {
  code: 'ERR_UNSUPPORTED_DIR_IMPORT',
  url: 'file:///project/node_modules/.pnpm/[email protected]/node_modules/buffer/'

We're using the buffer package so that our package can work in both NodeJS and browsers. To "tell" the code to import this version of Buffer, and not the built-in version, you have to import it via a directory and not the package name. Importing from buffer/ is problematic, but buffer/index.js is fine

Whilst fixing this issue I noticed it had a problem with me import { lib, ... } from crypto-js. Using the default import fixed that

And finally I also noticed the package doesn't have a default export, so I added that too

Changes

• Make buffer imports more explicit
• Use default import for crypto-js
• Provide a default export

Testing

@wingy3181 kindly provided a repo to replicate the issue, along with some test cases. Here's the test cases succeeding with the modified version of the package: