Summary

Hello, trying to move from webpack to turbopack for a documentation website running Next.js.

We are using raw-loading a lot to embbed generated css files to our documentation but also to add them to the context of our sandbox components based on sandpack.

We used to set the !!raw-loading! prefix to any file import where we would need to get the raw content rather than the file itself, which also allowed us to import the file as is in other scenarios :

import rawStyle from "!!raw-loader!./style.css" // can be used to embed the css file in documentation
import style from "./style.css" // can be used as css to apply styling to some web content

Following the documentation, all I could find is setting additional rules in the next configuration so that files matching a certain pattern can be handled by a given loader :

experimental: {
    turbo: {
      rules: {
        "**/styles/*.css": {
          loaders: ["raw-loader"],
        },
      },
    },

While this is working fine, this prevents to ever use two different kind of loaders for a given file : either we are raw-loading it or not, which is unfortunately an issue for us.

I am looking for any kind of suggestion, or advise from people who went through a similar scenario during a migration.

Many thanks !

Additional information

No response

Example

No response