Add support for sassOptions.includePaths to configure sass compiler

[oviirup]

Which project is this feature idea for?

Turbopack

Describe the feature you'd like to request

Turbo repo does not works if sassOptions.includePaths is present.

I guess this configuration is not used that often by others, but in my workflow, it is very much needed. Here is what my next.config.js looks like

// next.config.js
module.exports = nextObfuscator({
  experimental: { appDir: true },
  sassOptions: { includePaths: [path.join(__dirname, 'styles')] },
})

I use tailwind inside CSS modules, that's the main reason to use sassOptions.includePaths

Describe the solution you'd like

I know nothing about how turbopack works behind the scenes. but you can use previous sass compiler that can understand sassOptions.includePaths only if it is present

Describe alternatives you've considered

My alternative solution would be to add native support for tailwind, 😅

[GarryOne]

Meanwhile, maybe this can help:
https://nextjs.org/docs/api-reference/next.config.js/turbopack#webpack-loaders

[GarryOne]

vercel/next.js#49882

[jridgewell]

Fixed with vercel/next.js#49882

[GarryOne]

Still getting

Next v13.4.5

[GarryOne]

Still getting

Next `v13.4.5`

Fixed with:
vercel/next.js#51259

[oviirup]

The main reason I am looking for sassOptions is to use absolute paths in sass files. Something like this

@import 'styles/components.sass'
...

It seems you don't need really need to customise sassOptions if you are using postcss and tailwind. You can use absolute imports without any comfiguration.