1570 comments found.
9 months from the last update, and 4 months from your last comment here, most Angular templates are now using Tailwind 4. We have made lot of efforts to understand its complexity, and heavy work that should be redone if you decide to stop supporting this template.
Es excelente el template, una consulta, también van a actualizar el diseño algo como la versión de nextjs? y también agregarle mas funcionalidades como calendario y filtros en una tabla?
I’m afraid to buy because they don’t update
I have a license for a while now, very nice template. I used to have access to the Github repo, but since a couple of weeks I am not able to clone it anymore, getting a “Repo not found” error. Is it normal?
This asset is nearing abandonment, as the author—who manages multiple accounts—seems to be prioritizing other projects. I previously purchased assets from the same author’s other accounts that have already been abandoned, making their downloads inaccessible.
looking at comments re tailwind 4 and ng20, i think it will take a HUGE effort to migrate this framework. i’ve updated angular to 20 and have used some signals and httpResource in my own code, but tailwind remains at 3.
on another note, does anyone know what a content security policy would look like that includes the fuse sources and styles? .my starter is…
<meta http-equiv=”Content-Security-Policy” content=”default-src ‘self’ fuse; style-src ‘self’ fuse ‘nonce-randomNonceGoesHere’; script-src ‘self’ fuse ‘nonce-randomNonceGoesHere’;”>
...and this breaks things…
’s ok, got it. and good luck with the updating…that’s a pile of work!
- What is angular’s current version in this projet?
- What is version from TailwindCSS in this project?
Dear author, it has been almost 5 months since the last update, and there is not even the slightest mention of when the next update will take place. TailwindCSS 4 has been out for quite some time now, and several other admin themes have already upgraded to v4. After so many years of development and excellent support for this particular theme, I believe that the buyers who are eagerly waiting for an upgrade deserve at least an estimated date for the next update. The answers given to so many people supporting your project for months now have been that there is no date to provide. At the very least, we would like to know if Fuse is still supported so we can decide whether to invest in an upgrade ourselves or whether it makes sense to wait for an official update from the author. Thank you.
When will there be an update?
Hello, is the code optimized with Signal?
Hello,
Fuse currently is not using Signals. We will start moving to them in near future.
Cheers.
Do you happen to have an estimated date?
No estimated date as of now.
Cheers
hi – is there a way to remove all the plumbing for the various layouts apart from only 1? every time i try to do this and leave, say the enterprise layout, something breaks.
Hello,
Please open a support ticket at https://support-angular.withinpixels.com/ for your support requests.
Cheers
Any update so far on TailwindCSS v4 update? Thanks.
Can I have a beta or alpha version? Thanks.
Tailwind v4 is not officially 100% supported by Angular yet, and there are relatively big issues around it (e.g., HMR and style updates not working correctly in certain cases when using a custom PostCSS config). Once all those issues are fixed and official support lands, we will start working on the update.
https://github.com/angular/angular-cli/issues/28938No worries, I am done implementing TailwindCSS v4 in my Angular 19 project. Thanks.
I will buy it once Tailwind CSS is v4
Tailwind v4 is not officially 100% supported by Angular yet, and there are relatively big issues around it (e.g., HMR and style updates not working correctly in certain cases when using a custom PostCSS config). Once all those issues are fixed and official support lands, we will start working on the update.
https://github.com/angular/angular-cli/issues/28938Still waiting for tailwind css v4 update 
Tailwind v4 is not officially 100% supported by Angular yet, and there are relatively big issues around it (e.g., HMR and style updates not working correctly in certain cases when using a custom PostCSS config). Once all those issues are fixed and official support lands, we will start working on the update.
https://github.com/angular/angular-cli/issues/28938Hello,
To speed up our decision-making, design, and development processes in our ongoing project, we need the Figma file for Fuse. We would really appreciate your support on this.
Best regards.
Hello,
We currently don’t have a Figma file, we do have plans for making one but it is not a priority at the moment.
Cheers
Fuse , was spectaculer , but now a bunch of cyclic errors , do not buy this template , the team is neglecting all now
this fuse-vertical-navigation has a bunch of cyclic reference!!!!
There are no issues with this, it’s working just fine since we use forward ref. It always has been like that, we are not neglecting anything.
Hello, the new Tailwindcss V4 for Angular 19 has been released. I noticed an upgrade for React. Will Fuse be updated in Angular too?
Yes, Fuse Angular will get an update including Tailwind v4.
Cheers
is there a way to get the angular 15 version?
TY
Hello,
You can access all previous releases via our GitHub repo.
Cheers
where can i find the repo?
You need to request an access for it:
https://support-angular.withinpixels.com/github/“This purchase code has already been used.”
Then you already have an access to it, if you forgot your details, you can open a support ticket at https://support-angular.withinpixels.com and we will check it.
Error – 400 – fast_purchase_already_exits You already have added this purchase
Hi how do i fix this bug
hook.js:608 ERROR RuntimeError: NG0100: ExpressionChangedAfterItHasBeenCheckedError: Expression has changed after it was checked. Previous value: ‘-1’. Current value: ‘0’. Expression location: _FuseLoadingBarComponent component. Find more at https://angular.dev/errors/NG0100 at throwErrorIfNoChangesMode (core.mjs:11132:9) at bindingUpdated (core.mjs:20001:9) at Module.ɵɵconditional (core.mjs:26638:7) at FuseLoadingBarComponent_Template (loading-bar.component.html:1:1)
this error keep coming up
Hello,
You can ignore it as it only happens in development due to extra change detection cycle. It won’t happen in production.
We are moving to Signals, that will solve all of these little issues.
Cheers
Ok great
Cheers!