Css order is different in turbopack and in webpack

[Shaurya-kgen]

The order in which css styles are being applied is different in turbopack and webpack. I have a dropdown component which is being imported from the mantine library and I am applying style on that using the scss module.

Code example -

import { Menu } from "@mantine/core";
import Styles from "./subComponents.module.scss";

const profileMenuStyles = {
  dropdown: Styles.profileMenuDropdown,
  item: Styles.profileMenuItem,
  divider: Styles.profileMenuDivider,
  itemLabel: Styles.profileMenuItemLabel,
  itemSection: Styles.profileMenuItemSection
};

const ProfileMenuSection = () => {
    const [isProfileClicked, setIsProfileClicked] = useState(false)
    return <Menu
        width={316}
        shadow="md"
        position="bottom-end"
        classNames={profileMenuStyles}
        onClose={() => setIsProfileClicked(false)}
        offset={menuOffset}
      >
        <Menu.Target onClick={() => setIsProfileClicked(true)}>MenuTargetIcon</Menu.Target>
        {isProfileClicked && (
          <Menu.Dropdown className={Styles.profileMenu}>
            <Menu.Item
              className={`${Styles.profileMenuItem} ${Styles.profileMenuRow}`}
              onClick={onProfileClick}
              leftSection={<UserProfileImage />}
              classNames={{ itemSection: Styles.profileMenuItemSectionImage }}
            >
              Menu Item 1
            </Menu.Item>
          </Menu.Dropdown>
        )}
      </Menu>
}

For turbopack the css being applied are

For Webpack the css being applied are

I am using scss modules to apply styles and the component is from mantine which has its style sheet imported in the layout.tsx file

Nextjs version - 15.3.4
mantine version - 7.10.2
sass version - 1.62.1

Why is there a difference between turbopack and webpack?

[elevchyt]

Can confirm that this is still happening only when using the --turbopack parameter on the dev script.

Removing it (aka running dev with webpack) fixes the issue for now, but it would be great if we could get a fix for this because .scss modules never had a problem and we'd like to keep on using turbo.