590 comments found.
When on dev mode, default mode is dark mode but in production, it is non default mode. I am unable to figure out how to change it to dark mode by default
Hi,
Sorry for the late reply,
Please open this file `/src/stores/dark-mode.js` and update the following lines.https://i.imgur.com/aMB0ywM.png
Please use incognito if you are using chrome or use another browser if you can’t open the above link.
Hi, could you help me pls?, I was installing icewall starter version template, but when I run ‘npm run dev’, css styles don’t be applied to view and vite throws a warning message: ‘No utility classes were detected in your source files’, maybe I am doing something wrong
Hi there,
Thank you for reaching out to us,
Can you post step-by-step to reproduce the problem?
We just checked the Icewall starter version and there doesn’t seem to be any issue with it.
Hello, When i run npm run build, the dist folder only contains index.html, favicon.ico and assets folder. The bulk of the app is included. Could you pls guide me on how to get the dist folder populated with the entire app
Hi there,
Thank you for reaching out to us,
If you are working on production, you can apply all files in the `/dist` directory. The `/dist` directory contains all compiled and minified JS/CSS code that is ready for production.
I bought the Midone – Vuejs 3 Admin Template. It looks stunning !!
Running in dev mode works like a charm , however “building” is leading to “invalid-@nest” error.
I haven’t changed anything in the css files , do you know how to resolve this issue ? or configure the nesting rule-set ? CSS minifying seems to raise this error.
Thank you in advance !
Screenshot :
PastedGraphic-1.png
Copy (Text):
devaccount@ANiMac frontend % npm run build
> icewall-vue@0.0.0 build > vite build
vite v3.0.8 building for production… ✓ 1806 modules transformed. warnings when minifying css: ▲ [WARNING] CSS nesting syntax cannot be used outside of a style rule [invalid-@nest]
<stdin>:11581:4:
11581 │ & :root {
╵ ^
I saw SvenSt33 had the same issue reported one month ago , you replied to have it fixed with the next release.
Can you give us a fix-date ?
Hi,
Sorry for the late reply,
We have fixed this warning previously by releasing an update for our core package `@left4code/tw-starter`. However, we realized that the updates will cause other problems and there is no way to fix it without changing the template CSS code.
The warning has no effect on the template functionality and we are planning to release the patch in the next major version. But since you need it, we just released an update for this.
Please re-download the template and replace the following files.
- ”/src/assets/css/components/_breadcrumb.css”
- ”/src/assets/css/components/_chat.css”
- ”/src/assets/css/components/_content.css”
- ”/src/assets/css/components/_full-calendar.css”
- ”/src/assets/css/components/_global.css”
- ”/src/assets/css/components/_litepicker.css”
- ”/src/assets/css/components/_login.css”
- ”/src/assets/css/components/_mobile-menu.css”
- ”/src/assets/css/components/_news.css”
- ”/src/assets/css/components/_notification-content.css”
- ”/src/assets/css/components/_report-box-3.css”
- ”/src/assets/css/components/_report-box-4.css”
- ”/src/assets/css/components/_side-nav.css”
- ”/src/assets/css/components/_tabulator.css”
- ”/src/assets/css/components/_toastify.css”
- ”/src/assets/css/components/_top-nav.css”
Hope this helps.
Hi
Beautiful theme, excellent code, super easy to work with. I just have one question. How can I disable the animations entirely? Is there a plugin I can remove or a config I can adjust?
Thank you
Hi there,
Thank you for reaching out to us,
Please open this file ”/src/assets/css/app.css” and comment this line.
https://i.imgur.com/qpy6pnn.png
Next, open this file `/src/assets/css/components/_side-nav.css` and comment the following lines.
https://i.imgur.com/g2vfYt6.png
Please use incognito if you are using chrome or use another browser if you can’t open the above link.
Thank you. It works.
Glad it worked.. 
Named export ‘amberinherit’ not found. The requested module ‘tailwindcss/colors.js’ is a CommonJS module, which may not support all module.exports as named exports.
getting this error when compiling for SSR… similar multiple errors are coming.. only for SSR.. how to resolve this.
Hi there,
Sorry for the late reply,
Can you send a minimal step-by-step to reproduce the issue? So we can check it here.
Hi The theme is an outstanding work and I highly recommend for any user using vue and tailwindcss with vitejs
I have sent a detailed email to leftforcode@gmail.com. looking farward for you support…Thanks
Hi there,
Sorry for the late reply,
Just replied to your email, thanks.
Hi I bought the Midone version for Vuejs3. Do you have a guide to install it with Laravel + Vite + Vuejs 3? Or a demonstration project to pluginswelt@gmail.com?
Hi. I’m tommy. I have some questions about this template.
1. How can I get this template for Vue.js 2 ? 2. If I can get the template by email, Should I purchase template for Vue.js 3 first or purchasing the template after getting email?
Hi,
Thank you for reaching out to us,
Unfortunately, we don’t support Vue.js 2.
Hi I bought the Midone version for Vuejs3. Do you have a guide to install it with Laravel + Vite + Vuejs 3? Or a demonstration project to pluginswelt@gmail.com?
Its urgent can you please send us how to install with Laravel8 + Vite + Vuejs 3 to pluginswelt@gmail.com
Hope you are doing well. We purchased your Midone – HTML Admin Dashboard templates today to use it in our project. We are currently using Quasar framework and would like to integrate your admin template in it. We are trying to it integrate our self and we have actually solved quite a few errors in it. We were able to setup Tailwind, We added all the required package, We solved data issues, weak map key issues and many more. We also added postcss.config.js and set it up in our quasar app. And after all the error we are able to resolve all the compilation errors but now we are facing some run time issues with tippy and other packages. We would like to get some advice on how to solve it. Following is the exact error that we are facing.
Cannot read properties of undefined (reading ‘_tippy’)
The data is not coming it tippy. Also we have solved all the issues and we are not getting any error while running the project. Webpage opens up and we are able to get the data on our webpage but the css and global component is not getting loaded. And also please let us know what are the proper steps on implement it in quasar framework.
We bought the support license – can you please reply to our question
Hi there,
Thank you for reaching out to us,
To load the global components, have you imported the required css in `/src/assets/app.css`?
https://i.imgur.com/xtAb2kF.pngYou may also need to import the `base-components` in `/src/main.js`.
https://i.imgur.com/pZuwKG1.pngcan you send an example vue + laravel project?
Hi I bought the Midone version for Vuejs3. Do you have a guide to install it with Laravel 9 + Vite + Vuejs 3? Or a demonstration project?
My email is sergiocamici@gmail.fom
Hi,
Thank you for reaching out to us,
We have sent the file, thanks.
Hi, please I need to change my license for Laravel
Hello, I would like to use tom-select with pictures. So for example tom-select with usernames and their avatar. Can you help me with this?
Hi there,
Thank you for reaching out to us,
You can use `render` options to format the option and add the image, please check this link.
https://tom-select.js.org/docs/#render-templates
Hi can i get one more XD design for 1 units for Enigma please ? As my requested how long to create the XD design for Enigma ? Need your help to advise on this please.
Are there any updates in the typescript version?
Good morning, I would like to know how I can use this template in a Laravel project.
Hi,
Thank you for reaching out to us,
Yes, we can send you an example Vue + Laravel project, please leave your email, we will send it right away.
Hello,
I’m getting the following Warning when building with Laravel-Vite.
yarn run v1.22.19 $ vite build vite v3.1.3 building for production… ✓ 2614 modules transformed. rendering chunks (72)...warnings when minifying css: ▲ [WARNING] CSS nesting syntax cannot be used outside of a style rule [invalid-@nest] PS: It seems somewhere in the litepicker.css, because in the global newly generated “app.css” I found the issue which seems to be related to litepicker. And if I do not import the _litepicker.css file then the warning is no longer present
<stdin>:11232:4:
11232 │ & :root {
╵ ^
This is the section of the generated app.css file causing the warning “& :root” @media (max-width: 1023px){& :root{—litepicker-day-width: 35px}}.dark
Hi there,
Thank you for reporting this,
This seems to be due to the media query mixin we are using, we will fix it in the next release, thanks.
Hello,
I would like to have the version for VUE2 and Laravel? Could you get that to me via my email: sippe@postproval.com
Thanks in advance! regards
It’s for PhpStorm
Hi there,
Sorry for the late reply,
Unfortunately, we no longer support vue 2 version.
But do you have another Vue2 template? The version you used to send to people 4 months ago?