218 comments found.
Hey is there a private github repo that paid users can access to push PRs to for code contributions etc?
Hi can you leave your email so I can pass it to our tech lead? I’ll leave it to him to discuss that matter with you.
Something that might be of interest – I recently discovered the FeatherIcons project is no longer maintained, but a fork of it has been set up to continue the work which might be worth migrating to given they share the same base API: https://github.com/lucide-icons/lucide
Thanks for the insight. However, we already moved a while ago to the @purgeicons library which offers a huge base of icons, including feather icons. At build time, all unused icons are automatically purged. You can get a glimpse of the available icons by looking at https://icones.netlify.app/. Best.
Ah that’s great! I will log an issue on their tracker instead – thanks!
Awesome!
Nice update!
I see the dark mode of the vueform/multiselect component is fixed. 
Just a minor tweak, there’s a green box-shadow when you activate such control, in order to be consistent with the other controls you need to set it to none.
.multiselect.is-active {
box-shadow: 0 0 0 var(--ms-ring-width, 3px) var(--ms-ring-color, #10B98130);
}
Fix:
.multiselect.is-active {
box-shadow: none;
}
Other than that, it is looking great!
Hi David, I checked and you are right. They probably added this box shadow in a recent update. Will port your changes to Vuero so it is finally fixed. Thanks!
First of all, thanks for this beautiful theme. The menu system is too static. In real applications, the menus can come from the backend application according to the roles of the user. It would be better if you change the menu system to at least consist of json files.
Hi, happy you like the product. Regarding the menu, Iam not sure this is a good idea as we would have already implemented it. While we understand this would not be critical for pure admin apps, it could be bad for customer facing apps as it would negatively impact SEO. And since our pages are not rendered by a server (we’re still waiting on Nuxt 3), Iam not sure that this would benefit the project at this stage. However, if we find a way that doesn’t have a negative impact, we will think about it. Best.
Can you update the Vuero changelong in docs.cssninja.io, also the performance in linghthouse was not very good even with the quickstarter version this has been improved?
Hi, we will update the docs changelog when we have a chance. In the meantime, you can see the changelog below the item description. Regarding the lighthouse score, it was not in the scope of this technical update. Best.
I am saying this because in the website you have changelong for the version 1.3.2 (2021-09-04) and in codecanyon you dont have that!, in codecanyon you have the changelog 1.4 and the site dosen’t have.
Sure but we will update it as soon as we have a chance. So much to do currently. But yeah we will. Best.
How can I download ? (v1.3.2) Currently a download link 1.3.1
Hi, please be patient as the update will be available to download in a few hours. We’re still finishing the update process. Best.
its cool 
impatiently waiting
Awesome! Will keep you posted on when the update is available to download.
The update is live! You can download it anytime. Happy development!
Hi, could you tell me how to access userSession from router.ts So I can check if user is logged in before each page change ?
Hi, please open a ticket on https://support.cssninja.io so our support team can look at your issue. Please provide enough details and code examples so we can help you efficiently. Best.
Ticket already sent. Best
what is the problem with this deployment I have just run npm run build and publish the dist folder to the server
Hello, please open a ticket on https://support.cssninja.io , and please give us all the details so that we’re able to reproduce your issue. We will then get back to you with a solution to your problem. Best.
Do you think this would look good with the current component styles? Iam not really sure. Best.
Hi, this probably means that you forced an update on dependencies as in the initial package.json, we have “vite-plugin-components”: “0.13.2” without the ”^” symbol, preventing unwanted updates. You should probably avoid forced updates as we make sure that everything is working properly for each release. However, you still can update dependencies, but that implies that you go through each one’s release notes to avoid breaking something. Therefore, we strongly advise to work with the released version as is, in terms of dependencies. Next update will include an update for all dependencies that need to be bumped. Best.
*placement (not position)
Is the arrow remaining white whatever position you set?
All directions other than “up” (you can see in the demo site?)
Alright, thanks we’ll have those fixed and added to our issue board. Thanks for reporting this. Best.
Hi, thanks for reporting this. We are already aware about it. The plugin has been updated by it’s author and there are breaking changes. This will be fixed with the next release. Best.
Hi. I submitted a ticket almost 4 days ago and havent received a response. Please could you look into it? #152
Hi, the support is on vacation so it is a bit slower. Also, we are giving priority to tickets related to product bugs or installstion or configuration problems. Yours is about customization, meaning creating an element that doesn’t exist. Customization services are not part of support. Therefore, kindly wait until we are able to help you with this, as there are a lot of priority tickets. Best.
Hi is the figma/sketch file included? We need to make wireframes . Thanks
Hi, no figma or sketch files included. We use paper wireframes to predesign our products. The rest is made on screen. Regards.
hi, I asked few months ago if you could add a kanban with infinite horizontal scroll, I hope it’s coming soon any chance for it in the coming update ?
Hi, this is not our top priority at the moment as we have a lot of feature requests to process on our community discussions board for Vuero. This one will have to wait. Best.
Lighthouse rates you demo performance to 32 which is pretty low, and in fact, i can “feel” some low performance between routes, it takes a little more than a second to paint the content after a route change.
Any improvement that can be done?
Hi, yes we are aware about that, some of it is probably related that it is a partially implemented demo. We’ll take a look and see if there are some quick wins. The only thing about lighthouse Iam sure about is that the more you have content to load, the more your score is likely to go down. Stripping some stuff out of the demo will probably improve yhe score. Best.
I would like to know if it is okay not to use vuex, how can I share the data/state among all components?
Hi, Vuero does not use vuex, instead it uses raw composition api from vue 3, without any external dependencies !
When working with Vue2, we do not have many choices when sharing states through the entire application. Then comes the Redux pattern (https://redux.js.org/understanding/thinking-in-redux/three-principles) introduced in the React ecosystem.
The Redux pattern was implemented in Vue with the VueX package and seemed to be used anywhere by everyone, but that’s not how it should be used, here is a wonderful article that might interest you about Vuex and vue2: https://markus.oberlehner.net/blog/should-i-store-this-data-in-vuex/
The Vue 3 composition API differs a lot from these concepts, instead we are working with reactive references that can be declared outside the components. Those references can also be used outside components (we can watch them for change, alter them, etc…) This new approach is really close to managing pointers in C/C++ Take a look at the introduction part of the composition API on the vue3 documentation: https://v3.vuejs.org/guide/composition-api-introduction.html#why-composition-api
If you take a look at the wizard state management in src/state/wizardState.ts which we are using in https://vuero.cssninja.io/wizard-v1 only reactive/ref/computed vue functions are used (we will update it soon due to a new awesome feature of Vue 3.2, the effectScope API which is not yet documented but here is the related PR: https://github.com/vuejs/vue-next/pull/2195)
If you need a store, we recommend you to use pinia instead of vuex as it is developed by one of the guys from the vue core team: https://github.com/posva/pinia
Pinia will not persist any state by default (as of Vuex), instead you should do it by yourself, the question was resolved on this issue on Github: https://github.com/posva/pinia/issues/309Also, we recommend you to watch this awesome tutorial series made by Evan You itself on how the composition API and the Vue renderer is made : https://www.vuemastery.com/courses/vue3-deep-dive-with-evan-you/vue3-overview (That is a paid tutorial, but the benefits goes to the Vue core team, so it supports open-source!)
We have recently opened a public GitHub repository to gather feature requests, feel free to contribute: https://github.com/cssninjaStudio/vuero/discussions
I hope you will enjoy vue3 and the composition API as we do!
Best
Can you tell me if there is any exemple using a call with useApi.ts?
sorry forget i have solve lol
Glad to hear it!
Dont forget adding some cookies warnign on next update 
Sure!
I just noticed the new map pages, it looks awesome!
Any chance to make it more mobile friendly? On mobile the card list of places takes too much space and is not displayed properly. Would be nice to have the maps more bigger and the places list smaller or maybe in its flyout menu so you can see the whole map.
Also noticed the map markers doesn’t work with the finger taps.
Hi, thanks for the feedback we’ll think about how we can improve this component. For the touch features we’ll look at that as well. Thanks again! Best
- nodejs 14.17 - ts 4.3.5 - npm 7.15.1
Help me, Cant run dev: error when starting dev server:
npm run dev
vite.config.ts:230
if (!config?.isProduction)SyntaxError: Unexpected token ’.’
upd:
replace: vite-plugin-vuero-doc/index.ts
if (!config.?isProduction) > if (!config.isProduction)
Did you fix the issue?
This item was featured on ThemeForest
Elite Author
Contact the Envato Market Help Team
