ESM entry points to "dist/context.esm.js" but "dist" folder only contains "dist/context.js"

[TimoGlastra]

I think updating the package.json entry should be enough? But not sure if the context.js is an ESM build?

[alexfigtree]

@dmitrizagidulin Is context.js is an ESM build?

[alexfigtree]

Dmitri says it needs to be fixed, moving this issue to our backlog.

[NaoyaMiyagawa]

Hi, just leaving a note here for those who encountered this error when building:

❯ pnpm build

> verifier-web-component@0.0.0 build /Users/xxx/...
> tsc && vite build --watch=true

vite v5.4.6 building for production...

watching for file changes...

build started...
✓ 1221 modules transformed.
[commonjs--resolver] Could not load /path/to/node_modules/@digitalcredentials/open-badges-context/dist/index.js: ENOENT: no such file or directory, open '/path/to/node_modules/@digitalcredentials/open-badges-context/dist/index.js'

This was resolved by adding alias to point the correct file path in the package.

vite.config.ts

// https://vitejs.dev/config/
export default defineConfig({
  ...
  resolve: {
    alias: {
      "@digitalcredentials/open-badges-context":
        "/node_modules/@digitalcredentials/open-badges-context/dist/context.js",
    },
  },

above pointing to context.js instead of context.esm.js defined in package.json.

[jchartrand]

The 'files' property in the package.json didn't include the esm file so it wasn't getting added to the published npm package. I've added it.