serverless-webpack can't resolve module

Question

Getting this error from serverless-webpack:

ERROR in ../db/actions/index.js
Module not found: Error: Can't resolve 'amazon-dax-client' in '/var/task/db/actions'
 @ ../db/actions/index.js 2:24-52
 @ ../db/db.js
 @ ./crop.js

My webpack.config.js file contains:

const slsw = require('serverless-webpack')

module.exports = {
    entry: slsw.lib.entries,
    target: 'node',
    externals: {
        sharp: 'commonjs sharp',
    },
    // Run babel on all .js files and skip those in node_modules
    module: {
        rules: [{
            test: /\.js$/,
            loader: 'babel-loader',
            include: __dirname,
            exclude: /node_modules/,
        }]
    }
}

The amazon-dax-client module is present in node_modules.

I've rolled back to the last versions of webpack and serverless-webpack that worked for me:

"serverless-webpack": "4.3.0",
"webpack": "3.11.0"

Any ideas on how to resolve or to get additional logging output to track down the issue?

sarp · Accepted Answer · 2018-10-13 00:55:27Z

1

Alternatively, you may consider using node-prune to remove unnecessary files from node_modules (.md, .ts, ...) It would not be as effective as webpack but it's way less complicated and definitely not error-prone. It can be good enough for certain projects.

answered Oct 13, 2018 at 0:55

sarp

3,7507 gold badges41 silver badges60 bronze badges

Sign up to request clarification or add additional context in comments.

Comments

Aaron · Accepted Answer · 2018-09-28 01:44:56Z

0

Can you try removing the /node_modules/ exclusion? If that's removed, I'd imagine it'd be able to get into that folder and do what you need. Since amazon-dax-client is in that folder, and you're telling webpack to ignore the node_modules folder, it won't be able to reach it. Let me know if that helps.

answered Sep 28, 2018 at 1:44

Aaron

1,3069 silver badges10 bronze badges

2 Comments

genestd Over a year ago

I commented out that line, and got the same result.

Aaron Over a year ago

Can you share your file structure with me and point out your entry point? I have an idea as to what might be going on.

genestd · Accepted Answer · 2018-09-28 16:27:01Z

0

I'm no longer getting the error, although I can't say specifically what fixed it. Deleting package-lock.json and node_modules seemed to be the catalyst.

answered Sep 28, 2018 at 16:27

genestd

4044 silver badges16 bronze badges

Collectives™ on Stack Overflow

serverless-webpack can't resolve module

3 Answers 3

Comments

2 Comments

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

3 Answers 3

Comments

2 Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Related