Broken Webpack's "resolve.alias" (Next 11.1.3-canary.41)

[thecynicalpaul]

What version of Next.js are you using?

11.1.3-canary.41

What version of Node.js are you using?

14.18.0

What browser are you using?

Chrome

What operating system are you using?

Windows 10

How are you deploying your application?

next start

Describe the Bug

Hi there.

It seems like webpack's resolve.alias in webpack config is not behaving correctly in the last canary releases. When trying to create a conditional resolution, for example:

webpack: (config, {isServer}) => { 
  config.resolve = {
    ...config.resolve,
    alias: {
      ...config.resolve.alias,
      parse: isServer ? "parse/node" : "parse"
    }
  };
  return config;
};

It still keeps the "parse" imports, resulting in errors during SSR page compilation related to missing browser APIs. (localStorage in this case).

This is only the case in canary, and works fine in the lastest.

Expected Behavior

Resolve all imports during SSR stage to the specified module.

To Reproduce

1. Clone https://github.com/thecynicalpaul/broken-next-alias
2. npm i
3. npm run build

[balazsorban44]

This issue has been automatically locked due to no recent activity. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.