TweakCN Custom Colors Not Reflected in Laravel Projects

When customizing colors in TweakCN, the selected/customized colors are not properly reflected in the generated page when using the theme in a Laravel project.

The issue appears to occur when changing different color values in TweakCN. Although the colors can be changed in the TweakCN editor, the resulting Laravel page continues to use the default theme colors of the selected TweakCN theme instead of the customized colors.

I have tested this on both Laravel 12 and Laravel 13, and the issue occurs on both versions.

Interestingly, this is not an isolated occurrence. Five of us have encountered the same issue while creating Laravel projects, although I have not yet been able to determine the exact cause or whether it is specific to Laravel.

To Reproduce

1. Steps to reproduce the behavior:
2. Create a new Laravel 12 or Laravel 13 project.
3. Set up the project with TweakCN.
4. Open the TweakCN theme editor.
5. Select a theme.
6. Change one or more theme colors to custom colors.
7. Apply/export the customized theme to the Laravel project.
8. Run the Laravel application.
9. Observe the page/components that use the customized theme colors. The page still displays the default colors from the originally selected TweakCN theme instead of the customized colors.

Expected behavior When a color is customized in TweakCN, the customized color should be reflected in the Laravel project after the theme is applied/exported.

For example, if I change the primary color from the theme's default value to a custom color, the Laravel application should use that new custom primary color throughout the relevant components.

Desktop (please complete the following information):

• OS: WINDOWS
• Browser: BRAVE BROWSER
• Version: Brave 1.94.121

Additional context The issue has been reproduced on Laravel 12 and Laravel 13. Five different people have encountered the same behavior while working on Laravel projects. The issue seems to specifically involve customized colors not being propagated to the generated Laravel application, while the default colors of the selected TweakCN theme continue to work. I have not confirmed whether this occurs in non-Laravel projects. I also have not yet determined whether the issue is caused by TweakCN's generated CSS/theme variables, Laravel's asset/build pipeline, Tailwind configuration, or another part of the integration. It would be useful to verify whether the generated theme variables/CSS contain the customized color values and whether those values are being included correctly in the final Laravel build.