Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Performance for yarn watch #8

Closed
Arijus opened this issue May 30, 2024 · 3 comments
Closed

Performance for yarn watch #8

Arijus opened this issue May 30, 2024 · 3 comments
Labels

Comments

@Arijus
Copy link

Arijus commented May 30, 2024

Steps to reproduce

What is expected?

What is actually happening?

Using yarn watch for premium template after changing lets say some variable in .scss it takes to compile admin area like 3 mins.. It should be like this? I even have split admin and front compilation to work faster, but cant handle admin area..

Additional data

@Arijus Arijus added bug Something isn't working support labels May 30, 2024
@smitbhalodiya
Copy link
Member

Hi @Arijus,

Thank you for reaching out about the issue you're experiencing with SCSS compilation times.

Currently, your SCSS compilation is taking longer than expected. It seems that this issue might be related to your webpack configuration.
In our Pro version, we have switched from webpack to Vite. Vite offers faster compilation compared to webpack, which can help resolve this issue.
Additionally, our Pro version includes many applications and pages built with Vite that you can explore in our demo. https://demos.themeselection.com/sneat-bootstrap-html-laravel-admin-template/demo-1/
Upgrading to the Pro version could provide you with a better experience.

Please let us know if you need any further assistance.

Copy link

This issue has been automatically marked as stale because it has no recent activity. It will be closed if no further activity occurs. Thank you for raising the concern.

@github-actions github-actions bot added the stale label Jun 11, 2024
Copy link

This issue has been automatically marked as closed because it has no recent activity.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants