Cannot use import statement outside a module when importing this package using Jest about tiny-secp256k1 HOT 10 CLOSED

Thanks for the input @junderw , I've been able to "resolve" (pun intended) this now

For anyone experiencing the same problem, here's the TLDR:

Jest currently does not support the package.json#exports field (see jestjs/jest#9771). Currently Jest plans to add support for it in v28. In case v28 has been released when you're reading this, I'd try just upgrading Jest and see if that resolves the issue.

If v28 has not been released yet or v28 also does not resolve this issue, you can use the suggestion mentioned here
I've implemented this as follows:

// jest.config.js
module.exports = {
  resolver: "<rootDir>/jest-resolver.js"
  // any other options go here
}

// ./jest-resolver.js
const enhancedResolve = require("enhanced-resolve");

const resolver = enhancedResolve.create.sync({
  conditionNames: ["require", "node", "default", "import"],
  extensions: [".js", ".json", ".node", ".ts"],
});

module.exports = (request, options) => resolver(options.basedir, request);

@junderw As I understood, adding a package.json#main field would also resolve the issue. Is there a specific reason this has not been added? If you just haven't gotten around to it, let me know and I can create a PR for it.

from tiny-secp256k1.

This is a jest configuration issue.

Both this package and uint8array-tools are set to use require for node environments and import for browser environments.

Most likely setting your jest environment to node should fix the issue.

from tiny-secp256k1.

Jest ESM support is a separate issue. Right now it's bundling the MJS code as a CJS.

from tiny-secp256k1.

Or maybe it's a babel issue. Assuming you followed that website directions exactly.

from tiny-secp256k1.

I work on a private project that uses ts-jest instead of babel and everything works fine, btw.

from tiny-secp256k1.

I've tried running files through the ts-jest transformer now, with the same result.

Let me see if I can create a repro for this

from tiny-secp256k1.

@junderw Here's a repro https://github.com/Robin-hoodie/tiny-secp256k1-repro

from tiny-secp256k1.

I am having the same issue

from tiny-secp256k1.

This issue is not with this library. We have used the official NodeJS methods for providing cjs backwards compatibility.

Please follow the issue on the jest repository.

from tiny-secp256k1.

jestjs/jest#9771 (comment)

Try using a custom resolver.

looks like babel also has the same issue.

from tiny-secp256k1.