Linked Questions

Popular Questions

Error finding core node modules during webpack build in windows

Asked by At

I am trying to write modern ES code in node.js. For that I am trying to configure babel using webpack. I am not able to build my source files using webpack command. But it is unable to properly find node_modules.

My webpack.config.js looks like this

const path = require('path');

const config = {
    entry: {
        bundle: path.resolve('src/js/index.js')
    output: {
        path: path.resolve(__dirname, 'dist'),
        filename: '[name].js'
    module: {
        rules: [
                test: /\.js?$/,
                exclude: path.resolve(__dirname, 'node_modules'),
                loader: "babel-loader",
                options: {
                    presets: [
                        ["@babel/preset-env", { targets: { node: true } }]
                    plugins: [
                        ["@babel/plugin-proposal-class-properties", { 
                        "loose": false }]
module.exports = (env, args) => {

    if (args.mode === 'development') {
        config.devtool = 'source-map';

    return config;

I export the functions this way:

export default { welcome, defaultWelcomeNo };

I import the modules this way:

import welcomeHandler from './intents/welcome';
import bodyParser from 'body-parser';

I expect everything to compile properly and to get bundle.js in the end. Instead I am getting error as follows(part of a long error):

ERROR in ./node_modules/tunnel-agent/index.js
Module not found: Error: Can't resolve 'tls' in 'D:\Visual Studio 
 @ ./node_modules/tunnel-agent/index.js 4:10-24
 @ ./node_modules/request/lib/tunnel.js
 @ ./node_modules/request/request.js
 @ ./node_modules/request/index.js
 @ ./node_modules/request-promise-native/lib/rp.js
 @ ./src/js/utils/Util.js
 @ ./src/js/index.js
npm ERR! errno 2
npm ERR! [email protected] dev: `webpack --mode development`
npm ERR! Exit status 2
npm ERR!
npm ERR! Failed at the [email protected] dev script.
npm ERR! This is probably not a problem with npm. There is likely 
logging output above.

Related Questions