ESLint not working on macOS due to unrs-resolver introduced in package version 4.12 when using Docker (Ubuntu 20.10)

[bpor92]

The unrs-resolver package introduced in version 4.12 causes ESLint to stop working when running the project on macOS through Docker (inside an Ubuntu 20.10 container).
This issue does not occur in version 4.6 — everything works correctly with that version.

Error: Failed to load native binding at Object.<anonymous> (/node_modules/unrs-resolver/index.js:372:11) at Module._compile (node:internal/modules/cjs/loader:1544:14) at Module._extensions..js (node:internal/modules/cjs/loader:1629:10) at Module.load (node:internal/modules/cjs/loader:1282:32) at Module._load (node:internal/modules/cjs/loader:1103:12) at c._load (node:electron/js2c/node_init:2:16955) at cjsLoader (node:internal/modules/esm/translators:302:15) at ModuleWrap.<anonymous> (node:internal/modules/esm/translators:240:7) at ModuleJob.run (node:internal/modules/esm/module_job:263:25) at async ModuleLoader.import (node:internal/modules/esm/loader:540:24)

[petercat-assistant]

It seems like you're experiencing an issue with ESLint not functioning correctly on macOS when using Docker with an Ubuntu 20.10 container. The problem arises due to the unrs-resolver package introduced in version 4.12 of un-ts/eslint-plugin-import-x. This issue does not occur with version 4.6, where everything works as expected.

To address this issue, you might consider the following steps:

1. Downgrade to Version 4.6: If version 4.6 works without issues, you can temporarily downgrade to this version until a fix is available in the newer versions.

2. Check for Updates: Keep an eye on the repository for any updates or patches that might resolve this issue in the newer versions.

3. Report the Issue: If you haven't already, reporting this issue to the maintainers of the un-ts/eslint-plugin-import-x repository can help them identify and fix the problem in future releases.

If you need further assistance or have any questions, feel free to ask!

🪧 Tips

For further assistance, please describe your question in the comments and @petercat-assistant to start a conversation with me.

[JounQin]

Reproduction please, we have https://github.com/un-ts/napi-postinstall for npm's issue FYI.

---

So, you install unrs-resolver indirectly on macOS and use docker and marknode_modules as shared volume which finally results this issue.

I'll try to add some runtime check soon later.

---

In the meantime, you can install https://npmjs.com/@unrs/resolver-binding-wasm32-wasi manually as workaround.

[bpor92]

I'm using @antfu/eslint-config, which has eslint-plugin-import-x as a dependency. In its latest version (4.12), eslint-plugin-import-x started using unrs-resolver.

As a result, a project set up in Docker (based on ubuntu:20) that uses @antfu/eslint-config and is run on macOS causes this issue.

Workaround is also install the "eslint-plugin-import-x" package: "4.6.1",

[JounQin]

I'm using @antfu/eslint-config

Then you should alreay read https://antfu.me/posts/why-reproductions-are-required, although the root cause is already posted above.

[sdavids]

Another workaround is adding all the architectures you need as optional dependencies to your package.json:

  "devDependencies": {
...
    "eslint-plugin-import-x": "4.13.0"
  },
  "optionalDependencies": {
    "@unrs/resolver-binding-darwin-arm64": "1.7.2",
    "@unrs/resolver-binding-darwin-x64": "1.7.2",
    "@unrs/resolver-binding-arm64-gnu": "1.7.2",
    "@unrs/resolver-binding-linux-x64-gnu": "1.7.2"
  },

It is just sad that npm/cli#4828 has been closed.

[bpor92]

@sdavids unfortunately, Your workaround doesn't work.

[sdavids]

It is important that you remove the node_modules folder before building inside the Dockerfile otherwise npm thinks it has nothing to do and uses the bindings from the host machine.

Add node_modules/ to .dockerignore and rm -rf node_modules before you execute npm ci in your Dockerfile.

---

You need a similar setup, if you use a Dev Container:

.devcontainer/devcontainer.json

{
...
  "postCreateCommand": "./.devcontainer/post_create.sh",
}

.devcontainer/post_create.sh

rm -rf node_modules
npm i

[JounQin]

I don't understand why you all just ignore my comment above which is the correct workaround instead:

In the meantime, you can install https://npmjs.com/@unrs/resolver-binding-wasm32-wasi manually as workaround.