10 comments found.
Hey, I like the template but I just want to confirm that this is indeed now built from the ground up using svelte 5? I’m a little unsure following the exchange from @william533
Hi,
For your information, we have changed all the old syntax from Svelte 4 to Svelte 5 since last few version release.
Best Regards, Sean.
I purchased this template because it was advertised as being made with Svelte 5.X. However, I found that it is not truly Svelte 5. The only reference to Svelte 5 is in the package.json file, while the code and syntax are still based on Svelte 4. It does not utilize runes or any of the updates and migrations introduced in Svelte 5.
According to the “Envato Market Refund Rules”, this situation qualifies as “Item is not as described or the item doesn’t work the way it should.” Therefore, I request that you either update the template to be fully made with Svelte 5 and it’s syntax or provide a refund. While Svelte 5 does support the legacy Svelte 4 syntax, it is not native Svelte 5. If I wanted to update and migrate to Svelte 5 syntax myself, I would not have purchased a Svelte 5 template.
Hi,
Thank you for your feedback, and I appreciate you taking the time to share your concerns.
While I understand your expectations regarding the use of Svelte 5-specific syntax, I want to clarify that Svelte 5 is fully backward-compatible with Svelte 4 syntax. The template is built to function seamlessly in a Svelte 5 environment, and all the features advertised are supported and operational.
The decision to use Svelte 4 syntax was made to maintain compatibility and accessibility for a broader range of users while still allowing the template to take advantage of Svelte 5’s runtime and features. Therefore, the template works as intended within the Svelte 5 framework, and its compatibility aligns with the description provided.
That being said, I understand that you were expecting the code to adopt Svelte 5’s newer syntax, such as runes and other updates. While these are not mandatory for the functionality of a Svelte 5-compatible template, I value your feedback and will consider updating the template in the future to incorporate the latest syntax for users who specifically prefer it.
If you have further concerns or specific requests, I’d be happy to discuss them. I appreciate your understanding and look forward to resolving this matter in a way that satisfies your expectations.
Best Regards, Sean.
Thank you for your prompt response. While I understand your perspective, initiating a new project with legacy syntax that will soon be deprecated and require updates is not ideal. When you say “updating in the future” do you have any sort of timeline of when or if this might happen?
As stated in the Svelte 5 documentation (Legacy APIs): “Svelte 5 introduced some significant changes to Svelte’s API, including runes, snippets, and event attributes. As a result, some Svelte 3/4 features are deprecated (though supported for now, unless otherwise specified) and will eventually be removed. We recommend that you incrementally migrate your existing code.”
Hi,
Thank you for your thoughtful feedback. I completely understand your concerns regarding legacy syntax and the importance of staying aligned with future updates.
No worries – we’ve updated the project to fully utilize Svelte 5 syntax to ensure long-term compatibility. You can download the latest version directly from the ThemeForest user portal at your convenience.
Best Regards, Sean.
Thank you for addressing my concerns and for updating the project to fully utilize Svelte 5 syntax so quickly. I appreciate your prompt action to ensure long-term compatibility. Excellent support
Hello,
I recently purchased your HTML theme, and I am encountering an issue with the data table included in the example. Unfortunately, it doesn’t seem to be responsive as expected. When I reduce the browser window size or view the page on smaller devices (mobile or tablet), the table does not adjust correctly.
Specifically, I noticed that the columns are not collapsing into the “+” button as they should. Instead, the table overflows off the screen, making it difficult to navigate and read.
Could you please confirm if this is a known issue or provide a solution to ensure the table behaves as intended?
Thank you in advance for your assistance and prompt response.
Best regards,
Hi,
As long as you set the table in full width with attribute width=”100%” or css class w-100, it will be able to solve the responsive issue.
Best Regards, Sean.
Hello,
I recently purchased your HTML template and I am very pleased with it. However, I would like to ask if it’s possible to add a sub-item under an existing sub-item in the horizontal menu. Could you please let me know if this functionality is supported, and if so, provide guidance on how to implement it?
Thank you in advance for your help!
Best regards,
Hi,
You may add another level of menu.children loop in /src/components/app/AppTopNav.svelte and it will be able to add another level of sub-item in horizontal menu.
Best Regards, Sean.
Hi Sean,
Thank you for your response. I followed your suggestion and added another level of menu.children loop, but the sub-item under the sub-item doesn’t seem to be working as expected. Here’s the HTML structure I implemented:
Menu 1 sub menu with items sub menu item menu item menu itemCould you please review it and let me know if I’m missing something, or if there’s an additional step needed in the CSS logic to support multiple levels of sub-items?
Best regards,
Arf sry, cant add html code, can you add an example in your demo app ? ty
Hi,
Can you share to us which version you are using right now? Svelte or HTML version?
Best Regards, Sean.
HTML, ty
Hi,
You may refer to the following example for 2 level submenu in top nav.
https://pastebin.com/zTcQ3gizBest Regards, Sean.
Thank you for providing the code. I copied and pasted it as instructed, but I encountered an error in the browser console:
Uncaught TypeError: Cannot read properties of null (reading ‘classList’)
It seems like there might be an issue with how the elements are being targeted or manipulated in the JavaScript. Could you please advise on how to resolve this error? If additional modifications to the code are needed, I’d appreciate your guidance.
Thank you again for your assistance.
For your information, my body class : app app-with-top-nav app-without-sidebar
and div id menu : app-top-nav
and error in app.js : e.classList.contains(“transitioning”) || (e.classList.add(“transitioning”),
Hi,
Can you copy and paste the html code for your top nav in pastebin?
Best Regards, Sean.
I will do
Hi,
We need to know the code from your side so that we can debug on our side. This is because the demo code that we provide just now is working fine on our side.
Best Regards, Sean.
It turns out it was my mistake! I had a second menu with an empty has-sub element, which was causing the issue. After fixing that, everything works perfectly now.
Thank you so much for your help!
Glad to hear that your issue was resolved.
Best Regards, Sean.
Good work yea! can we have it updated to svelte 5?
Hi,
Yeah. We will update to Svelte 5 once the stable version has been released.
Best Regards, Sean.
Stunning theme ! But ? What happens to the second menu in the “mixed Nav” mode ? it is nowhere to be found ?
Hi,
The top nav can be found via /src/components/app/AppTopNav.svelte.
Best Regards, Sean.
Nice Work, Congratulations GLWS 
Thank you
