Absolute node_modules paths are not getting resolved during SSR

💬 Questions and Help

I am not sure if this issue is similar to #293. I am importing a component from node_modules. const ComponentName = loadable(() => import("@nodeModuleName/[path-to-component]") );

This import runs on client side. (i.e., when I run using { ssr: false }, the component gets load). But it does not load on server side. Throws error Cannot find module '/Users/[my-project]/@nodeModuleName/[path-to-component]'

the import gets resolved to

var ComponentName = (0, _component.default)({
  chunkName: function chunkName() {
    return "ComponentName";
  },
  isReady: function isReady(props) {
    if (typeof __webpack_modules__ !== 'undefined') {
      return !!__webpack_modules__[this.resolve(props)];
    }

    return false;
  },
  requireAsync: function requireAsync() {
    return import(
    "@nodeModuleName/[path-to-component]");
  },
  requireSync: function requireSync(props) {
    var id = this.resolve(props);

    if (typeof __webpack_require__ !== 'undefined') {
      return __webpack_require__(id);
    }

    return eval('module.require')(id);
  },
  resolve: function resolve() {
    if (require.resolveWeak) {
      return require.resolveWeak("@nodeModuleName/[path-to-component]");
    }

    return require('path').resolve(__dirname, "@nodeModuleName/[path-to-component]");
  }
});

Issue #293 mentioned that he is not using webpack but I do use webpack, then also getting error. Any help is appreciated

[gregberge]

I think the problem is here:

return require('path').resolve(__dirname, "@nodeModuleName/[path-to-component]");

We should replace it by:

return eval('require.resolve')("@nodeModuleName/[path-to-component]");

What do you think @theKashey?

[fatemab]

@neoziro Thank you so much for such a prompt release!