[Turbopack] Support Config Similar to Webpack Resolve Fallback

[CHC383]

Goals

1. Support config similar to Webpack resolve.fallback

Non-Goals

No response

Background

There are cases where server-side modules are being imported but only be used in the server-side code, currently webpack config resolve.fallback is used to resolve "module not found" errors on the client-side code. See this Stack Overflow post for the details.

Proposal

Add turbo.resolveFallback to allow modules not being imported on the client-side code.

[gobbodev]

nothing yet? ;(

[wallacerenan]

up

[timneutkens]

You can use something like the example shown here: https://nextjs.org/docs/app/api-reference/config/next-config-js/turbo#resolving-aliases but with an empty module, for example:

// empty.js
module.exports =  {}

module.exports = {
  experimental: {
    turbo: {
      resolveAlias: {
        fs: { browser: './empty.js' },
      },
    },
  },
}

Might add a specific option just for this, but that config should unblock you 🙂

[lcswillems]

Thank you! Yes, it would be great to have a config specifically for this 🙏