Module not found: Can't resolve 'dns'?

error - ./node_modules/ioredis/built/cluster/ClusterOptions.js:3:0 Module not found: Can’t resolve ‘dns’

Source:

"use strict";
Object.defineProperty(exports, "__esModule", { value: true });
const dns_1 = require("dns");

Looks the package.json does not include “dns” package.

Issue Analytics

State:
Created 3 years ago
Comments:7 (1 by maintainers)

Top GitHub Comments

9reactions

rajinwonderlandcommented, Jun 18, 2021

@baulml’s solution using webpack 5

module.exports = {
    webpack: (config, { isServer }) => {
        if (!isServer) {
             config.resolve.fallback.fs = false
             config.resolve.fallback.dns = false
             config.resolve.fallback.net = false
        }

        return config;
    }
}

7reactions

kmvancommented, May 4, 2021

Don’t run with browser. XD

Top Results From Across the Web

Error: Can't resolve 'dns' when using MongoDB - Stack Overflow

This error most likely means you are trying to do something from the client-side that needs to be done on the server-side. If...

Module not found Error: Can't resolve 'dns' · Issue #38 - GitHub

I really think there's a dependency problem, related to isemail, using dns. This error only occurs when I use ics, and ics librairy...

[Solved]-Module not found: Can't resolve 'dns' in pg/lib-Reactjs

The solution was to add the externals property to my webpack.config.js file and include all the modules that cannot be resolved by Webpack....

Getting "Module not found: Can't resolve 'dns'" error when ...

When I wrap my app in the tag I get this error and I do not understand why. Has anyone encountered this? I've...

module-not-found - Next.js

The module you're trying to import uses Node.js specific modules, for example dns , outside of getStaticProps / getStaticPaths / getServerSideProps. Possible ...