webpack: Module not found: Error: Can't resolve (with relative path)

前端 未结 10 1968
长情又很酷
长情又很酷 2021-02-05 06:34

I have this structure of an app (node_modules dir excluded from this list):

├── actions.js
├── bundle.js
├── components
│   ├── App.js
│   ├── Foote         


        
10条回答
  •  深忆病人
    2021-02-05 07:18

    Just ran into this... I have a common library shared among multiple transpiled products. I was using symlinks with brunch to handle sharing things between the projects. When moving to webpack, this stopped working.

    What did get things working was using webpack configuration to turn off symlink resolving.

    i.e. adding this in webpack.config.js:

    module.exports = {
      //...
      resolve: {
        symlinks: false
      }
    };
    

    as documented here:

    https://webpack.js.org/configuration/resolve/#resolvesymlinks

提交回复
热议问题