feat: add wasm file to exports

[hadeeb]

require.resolve and bundlers like vite are unable to resolve the wasm file.

Cheers

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Updated
resvg-js	✅ Ready (Inspect)	Visit Preview	Jan 4, 2023 at 0:34AM (UTC)

[yisibl]

Thanks!

Does vite have documentation for this?

[hadeeb]

It's not specific to vite.

// if using "type":"module"
// import { createRequire } from "module";
// const require = createRequire(import.meta.url);

try {
  // This works
  const indexFile = require.resolve("@resvg/resvg-wasm");
  console.log({ indexFile });
  // This does not work
  const wasmFile = require.resolve("@resvg/resvg-wasm/index_bg.wasm");
  console.log({ wasmFile });
} catch (error) {
  console.error({ error });
}

this code works after adding the wasm file to exports.

From nodejs.org

Existing packages introducing the "exports" field will prevent consumers of the package from using any entry points that are not defined, including the package.json (e.g. require('your-package/package.json'). This will likely be a breaking change.

[yisibl]

Can you add a test case to __test__/wasm.spec.ts?

[hadeeb]

It turns out that the exports field is used only when the target file is in node_modules (I might be wrong here).
I could not replicate the same behaviour while importing from "../wasm".

From nodejs.org

The "exports" field allows defining the entry points of a package when imported by name loaded either via a node_modules lookup or a self-reference to its own name.

[yisibl]

Thank you very much, let's merge it first.

[jeetiss]

@yisibl I got the same error with webpack! Could you please release this patch?

Module not found: Package path ./index_bg.wasm is not exported from package
/playground/node_modules/@resvg/resvg-wasm (see exports field in
/playground/node_modules/@resvg/resvg-wasm/package.json)

[yisibl]

@jeetiss Done https://github.com/yisibl/resvg-js/releases/tag/v2.3.0