590 comments found.
Hi. Where can I find the product page for a single product?
Hi, when will this be migrated to tailwind 4?
I have a clean download, run npm install and def and getting error: postcss] Missing ”./dist/simplebar.css” specifier in “simplebar” package
I have just installed the deps via npm install and run dev script on vue source. Got this error:
plugin:vite:css Missing ”./dist/simplebar.css” specifier in “simplebar” package
would you migrating to tailwind v4 ?
Hi, Sorry for the late reply. Yes, the Tailwind 4 version will be released soon. Thank you for your patience!
Estou com o seguinte erro: vite:css /usr/src/app/node_modules/@left4code/tw-starter/dist/css/mixins/_media.css:3:3: ‘screens.#{$screen}’ does not exist in your theme config. ‘screens’ has the following valid keys: ‘sm’, ‘md’, ‘lg’, ‘xl’, ‘2xl’ file: /usr/src/app/resources/js/assets/css/themes/icewall/side-nav.css:3:2
ao realizar o build do meu código fonte.
Hey, Sorry for the late reply! Can you share the content of your tailwind.config.js file? That’ll help us figure out what’s causing the issue.
Looking forward to hearing from you!
Dear Midone Support Team,
I hope this message finds you well.
I recently purchased the this item and have encountered challenges integrating it with Inertia.js. Unfortunately, the compatibility does not seem to work as expected.
Dear sfwan_essam,
Thank you so much for reaching out, and I truly apologize for our very late response.
We haven’t had the chance to work with Inertia.js before, but we’d love to help you out as much as we can! Could you share a bit more about the specific issues you’re running into with the integration? We’ll do our best to guide you through it.
Looking forward to hearing from you!
Best regards
Inquiry About the Best Midone Version for Use with Laravel and Inertia.js
Dear Midone Team,
I hope this message finds you well.
I am interested in purchasing the Midone template, but I would like your guidance on which version is most suitable for my needs. I am using Laravel with Inertia.js in my project and aim to integrate the template seamlessly.
I noticed that there are multiple versions of the template available:
HTML version Vue version Vue with Laravel version Considering that I am working with Inertia.js, which version do you recommend for the best compatibility and ease of integration?
Thank you for your support. I look forward to your advice.
Best regards, Sfwan
Dear sfwan_essam,
Thank you for reaching out, and we sincerely apologize for our very delayed response.
While we haven’t had experience working with Inertia.js, we’ll do our best to assist you. Please feel free to reply to this comment with more details about your project or any specific questions, and we’ll get back to you as soon as possible to help you out.
We appreciate your patience and look forward to supporting you!
Best regards
Hi, I wanna get this template but i’m worry about vue js version, Is there any vue js version? (i saw vue typescript but i need to have js version)
Hi there,
Thank you for your interest in our template! Currently, the project is only available in Vue with TypeScript. Unfortunately, we do not offer a version using plain JavaScript at this time.
However, if you are open to working with TypeScript, it can provide additional benefits like type safety and better tooling support. If you have any questions about integrating or using TypeScript with the template, please feel free to ask – I’d be happy to assist!
Best regards
It has been long we downloaded/upgraded this. The latest version seems to be typescript. Do you have the java script version (like the older one)?
Hi,
Unfortunately, we’re now only working with the TypeScript version and no longer maintain a JavaScript version. Let us know if there’s anything else we can assist you with. Thank you!
Hi, I just purchased this template. I want to set the default theme, layout and color scheme without the themeswitcher. How can I do that?
Hi there,
Sorry for the late reply! To set the default theme, layout, and color scheme without using the theme switcher, you can follow these steps:
Open the store file located at ”/src/stores/theme.ts”. Modify the following lines to hardcode the initial theme and layout instead of retrieving them from localStorage:
state: (): ThemeState => ({
themeValue: {
// name:
// localStorage.getItem("theme") === null
// ? themes[0].name
// : getTheme().name,
name: "rubick",
// layout:
// localStorage.getItem("layout") === null
// ? themes[0].layout
// : getTheme().layout,
layout: "side-menu",
},
}),
This way, you can define the default theme and layout directly in the code.
Let me know if you need any further assistance!
Best regards
cool, how about color scheme?
Hi xhsiow,
To change the default color scheme without using the theme switcher, you can follow these steps:
Open the file located at /src/stores/color-scheme.ts and modify the following lines to hardcode the initial color scheme instead of retrieving it from localStorage:
const getColorScheme = () => {
// const colorScheme = localStorage.getItem("colorScheme");
// return colorSchemes.filter((item, key) => {
// return item === colorScheme;
// })[0];
return colorSchemes[4]; // Replace "4" with the index of your desired color scheme
};
By setting the return “colorSchemes4,” you can specify the color scheme you want to use as the default.
If you need further help, feel free to reach out!
Best regards
Hi, I’m looking for some guidance on how t fix this issue reported by my developer: resources\assets\assets\css\components\_global.css:17:13: @apply is not supported within nested at-rules like @include. You can fix this by un-nesting @include. Developer’s comments: I tried different ways to fix this issue but no use. If you could post this in template comments we can get some help from template authors.
Hi, thank you for reaching out. Could you please provide more details on how to reproduce the issue? I’ve tested the project and haven’t encountered the same error. It would be helpful to know:
The steps leading up to the error. - Any changes or customizations made to the CSS or project structure. - The versions of the tools or dependencies you are using (e.g., TailwindCSS, etc.). - Once I have more information, I’ll do my best to assist you!
Hello,
I’ve encountered an issue when running/compiling the “Midone – Tailwind CSS Vue.js 3 Admin Dashboard Template” (Rubick version). After running `npm run dev` and opening the browser, I get the following error (please see the attached image: https://postimg.cc/87Spvy1C ).
Based on my research, it seems to be related to differences between the old and new versions of the template. Could you advise on how to resolve this issue? Should I update the template version, or would some code adjustments be required? Please guide me through whichever option is necessary to fix this.
Thank you.
Hi, thank you for reaching out. Could you please provide more details on how to reproduce the issue? I’ve tested the project but haven’t encountered the same error. Additionally, I’m unable to find a supported badge on your account, so I cannot assist you further at this time.
Once the purchase is confirmed, feel free to get in touch, and I’ll be happy to help you resolve the issue!
Could you kindly help me?
I bought the template but didn’t use it once. I would like to know if these messages that appear in the console are normal when I use yarn run dev
I downloaded the template Open with vscode I’m using node v18 do yarn install then I do yarn run dev
And the following messages appear in the console:
yarn run dev yarn run v1.22.22 $ vite
VITE v5.4.7 ready in 254 ms➜ Local: http://localhost:5173/
➜ Network: use --host to expose
➜ press h + enter to show helpA PostCSS plugin did not pass the `from` option to `postcss.parse`. This may cause imported assets to be incorrectly transformed. If you’ve recently added a PostCSS plugin that raised this warning, please contact the package author to fix the issue. [@vue/compiler-sfc] withDefaults() is unnecessary when using destructure with defineProps(). Reactive destructure will be disabled when using withDefaults(). Prefer using destructure default values, e.g. const { foo = 1 } = defineProps(...).
/home/leonam/code/others/Midone Vue/Vue Version/Source/src/components/Base/Breadcrumb/Link.vue 10 | } 11 | 12 | const { to, active, index } = withDefaults(defineProps<LinkProps>(), { | ^^^^^^ 13 | to: ””, 14 | active: false,
[@vue/compiler-sfc] withDefaults() is unnecessary when using destructure with defineProps(). Reactive destructure will be disabled when using withDefaults(). Prefer using destructure default values, e.g. const { foo = 1 } = defineProps(...).
/home/leonam/code/others/Midone Vue/Vue Version/Source/src/components/Base/Headless/Popover/Popover.vue 16 | } 17 | 18 | const { as } = withDefaults(defineProps<PopoverProps>(), { | ^^^^^^ 19 | as: “div”, 20 | });
[@vue/compiler-sfc] withDefaults() is unnecessary when using destructure with defineProps(). Reactive destructure will be disabled when using withDefaults(). Prefer using destructure default values, e.g. const { foo = 1 } = defineProps(...).
/home/leonam/code/others/Midone Vue/Vue Version/Source/src/components/Base/Headless/Popover/Button.vue 16 | } 17 | 18 | const { as } = withDefaults(defineProps<ButtonProps>(), { | ^^^^^^ 19 | as: “div”, 20 | });
[@vue/compiler-sfc] withDefaults() is unnecessary when using destructure with defineProps(). Reactive destructure will be disabled when using withDefaults(). Prefer using destructure default values, e.g. const { foo = 1 } = defineProps(...).
/home/leonam/code/others/Midone Vue/Vue Version/Source/src/components/Base/Headless/Popover/Panel.vue 32 | } 33 | 34 | const { as } = withDefaults(defineProps<PanelProps>(), { | ^^^^^^ 35 | as: “div”, 36 | placement: “bottom-end”,
[@vue/compiler-sfc] withDefaults() is unnecessary when using destructure with defineProps(). Reactive destructure will be disabled when using withDefaults(). Prefer using destructure default values, e.g. const { foo = 1 } = defineProps(...).
/home/leonam/code/others/Midone Vue/Vue Version/Source/src/components/Base/Headless/Menu/Menu.vue 16 | } 17 | 18 | const { as } = withDefaults(defineProps<MenuProps>(), { | ^^^^^^ 19 | as: “div”, 20 | });
[@vue/compiler-sfc] withDefaults() is unnecessary when using destructure with defineProps(). Reactive destructure will be disabled when using withDefaults(). Prefer using destructure default values, e.g. const { foo = 1 } = defineProps(...).
/home/leonam/code/others/Midone Vue/Vue Version/Source/src/components/Base/Headless/Menu/Button.vue 16 | } 17 | 18 | const { as } = withDefaults(defineProps<ButtonProps>(), { | ^^^^^^ 19 | as: “div”, 20 | });
[@vue/compiler-sfc] withDefaults() is unnecessary when using destructure with defineProps(). Reactive destructure will be disabled when using withDefaults(). Prefer using destructure default values, e.g. const { foo = 1 } = defineProps(...).
/home/leonam/code/others/Midone Vue/Vue Version/Source/src/components/Base/Headless/Menu/Items.vue 32 | } 33 | 34 | const { as } = withDefaults(defineProps<ItemsProps>(), { | ^^^^^^ 35 | as: “div”, 36 | placement: “bottom-end”,
[@vue/compiler-sfc] withDefaults() is unnecessary when using destructure with defineProps(). Reactive destructure will be disabled when using withDefaults(). Prefer using destructure default values, e.g. const { foo = 1 } = defineProps(...).
/home/leonam/code/others/Midone Vue/Vue Version/Source/src/components/Base/Headless/Menu/Item.vue 16 | } 17 | 18 | const { as } = withDefaults(defineProps<ItemProps>(), { | ^^^^^^ 19 | as: “a”, 20 | });
[@vue/compiler-sfc] withDefaults() is unnecessary when using destructure with defineProps(). Reactive destructure will be disabled when using withDefaults(). Prefer using destructure default values, e.g. const { foo = 1 } = defineProps(...).
/home/leonam/code/others/Midone Vue/Vue Version/Source/src/components/Base/Headless/Menu/Divider.vue 14 | } 15 | 16 | const { as } = withDefaults(defineProps<DividerProps>(), { | ^^^^^^ 17 | as: “div”, 18 | });
[@vue/compiler-sfc] withDefaults() is unnecessary when using destructure with defineProps(). Reactive destructure will be disabled when using withDefaults(). Prefer using destructure default values, e.g. const { foo = 1 } = defineProps(...).
/home/leonam/code/others/Midone Vue/Vue Version/Source/src/components/Base/Headless/Menu/Header.vue 14 | } 15 | 16 | const { as } = withDefaults(defineProps<HeaderProps>(), { | ^^^^^^ 17 | as: “div”, 18 | });
[@vue/compiler-sfc] withDefaults() is unnecessary when using destructure with defineProps(). Reactive destructure will be disabled when using withDefaults(). Prefer using destructure default values, e.g. const { foo = 1 } = defineProps(...).
/home/leonam/code/others/Midone Vue/Vue Version/Source/src/components/Base/Headless/Menu/Footer.vue 14 | } 15 | 16 | const { as } = withDefaults(defineProps<FooterProps>(), { | ^^^^^^ 17 | as: “div”, 18 | });
[@vue/compiler-sfc] withDefaults() is unnecessary when using destructure with defineProps(). Reactive destructure will be disabled when using withDefaults(). Prefer using destructure default values, e.g. const { foo = 1 } = defineProps(...).
/home/leonam/code/others/Midone Vue/Vue Version/Source/src/components/Base/Headless/Tab/Button.vue 16 | } 17 | 18 | const { as } = withDefaults(defineProps<ButtonProps>(), { | ^^^^^^ 19 | as: “a”, 20 | });
[@vue/compiler-sfc] withDefaults() is unnecessary when using destructure with defineProps(). Reactive destructure will be disabled when using withDefaults(). Prefer using destructure default values, e.g. const { foo = 1 } = defineProps(...).
/home/leonam/code/others/Midone Vue/Vue Version/Source/src/components/Base/Headless/Tab/List.vue 22 | } 23 | 24 | const { variant } = withDefaults(defineProps<ListProps>(), { | ^^^^^^ 25 | variant: “tabs”, 26 | });
[@vue/compiler-sfc] withDefaults() is unnecessary when using destructure with defineProps(). Reactive destructure will be disabled when using withDefaults(). Prefer using destructure default values, e.g. const { foo = 1 } = defineProps(...).
/home/leonam/code/others/Midone Vue/Vue Version/Source/src/components/Base/Headless/Disclosure/Group.vue 20 | const slots = useSlots(); 21 | 22 | const { as, selectedIndex, variant } = withDefaults(defineProps<GroupProps>(), { | ^^^^^^ 23 | as: “div”, 24 | selectedIndex: 0,
[@vue/compiler-sfc] withDefaults() is unnecessary when using destructure with defineProps(). Reactive destructure will be disabled when using withDefaults(). Prefer using destructure default values, e.g. const { foo = 1 } = defineProps(...).
/home/leonam/code/others/Midone Vue/Vue Version/Source/src/components/Base/Headless/Disclosure/Button.vue 18 | } 19 | 20 | const { as } = withDefaults(defineProps<ButtonProps>(), { | ^^^^^^ 21 | as: “button”, 22 | });
[@vue/compiler-sfc] withDefaults() is unnecessary when using destructure with defineProps(). Reactive destructure will be disabled when using withDefaults(). Prefer using destructure default values, e.g. const { foo = 1 } = defineProps(...).
/home/leonam/code/others/Midone Vue/Vue Version/Source/src/components/Base/Headless/Disclosure/Panel.vue 19 | } 20 | 21 | const { as } = withDefaults(defineProps<PanelProps>(), { | ^^^^^^ 22 | as: “div”, 23 | });
[@vue/compiler-sfc] withDefaults() is unnecessary when using destructure with defineProps(). Reactive destructure will be disabled when using withDefaults(). Prefer using destructure default values, e.g. const { foo = 1 } = defineProps(...).
/home/leonam/code/others/Midone Vue/Vue Version/Source/src/components/Base/Headless/Dialog/Description.vue 16 | } 17 | 18 | const { as } = withDefaults(defineProps<DescriptionProps>(), { | ^^^^^^ 19 | as: “div”, 20 | });
[@vue/compiler-sfc] withDefaults() is unnecessary when using destructure with defineProps(). Reactive destructure will be disabled when using withDefaults(). Prefer using destructure default values, e.g. const { foo = 1 } = defineProps(...).
/home/leonam/code/others/Midone Vue/Vue Version/Source/src/components/Base/Headless/Dialog/Footer.vue 14 | } 15 | 16 | const { as } = withDefaults(defineProps<FooterProps>(), { | ^^^^^^ 17 | as: “div”, 18 | });
[@vue/compiler-sfc] withDefaults() is unnecessary when using destructure with defineProps(). Reactive destructure will be disabled when using withDefaults(). Prefer using destructure default values, e.g. const { foo = 1 } = defineProps(...).
/home/leonam/code/others/Midone Vue/Vue Version/Source/src/components/Base/Headless/Dialog/Panel.vue 20 | } 21 | 22 | const { as } = withDefaults(defineProps<PanelProps>(), { | ^^^^^^ 23 | as: “div”, 24 | });
[@vue/compiler-sfc] withDefaults() is unnecessary when using destructure with defineProps(). Reactive destructure will be disabled when using withDefaults(). Prefer using destructure default values, e.g. const { foo = 1 } = defineProps(...).
/home/leonam/code/others/Midone Vue/Vue Version/Source/src/components/Base/Headless/Dialog/Title.vue 16 | } 17 | 18 | const { as } = withDefaults(defineProps<TitleProps>(), { | ^^^^^^ 19 | as: “div”, 20 | });
[@vue/compiler-sfc] withDefaults() is unnecessary when using destructure with defineProps(). Reactive destructure will be disabled when using withDefaults(). Prefer using destructure default values, e.g. const { foo = 1 } = defineProps(...).
/home/leonam/code/others/Midone Vue/Vue Version/Source/src/components/Base/Headless/Slideover/Description.vue 16 | } 17 | 18 | const { as } = withDefaults(defineProps<DescriptionProps>(), { | ^^^^^^ 19 | as: “div”, 20 | });
[@vue/compiler-sfc] withDefaults() is unnecessary when using destructure with defineProps(). Reactive destructure will be disabled when using withDefaults(). Prefer using destructure default values, e.g. const { foo = 1 } = defineProps(...).
/home/leonam/code/others/Midone Vue/Vue Version/Source/src/components/Base/Headless/Slideover/Footer.vue 14 | } 15 | 16 | const { as } = withDefaults(defineProps<FooterProps>(), { | ^^^^^^ 17 | as: “div”, 18 | });
[@vue/compiler-sfc] withDefaults() is unnecessary when using destructure with defineProps(). Reactive destructure will be disabled when using withDefaults(). Prefer using destructure default values, e.g. const { foo = 1 } = defineProps(...).
/home/leonam/code/others/Midone Vue/Vue Version/Source/src/components/Base/Headless/Slideover/Panel.vue 20 | } 21 | 22 | const { as } = withDefaults(defineProps<PanelProps>(), { | ^^^^^^ 23 | as: “div”, 24 | });
[@vue/compiler-sfc] withDefaults() is unnecessary when using destructure with defineProps(). Reactive destructure will be disabled when using withDefaults(). Prefer using destructure default values, e.g. const { foo = 1 } = defineProps(...).
/home/leonam/code/others/Midone Vue/Vue Version/Source/src/components/Base/Headless/Slideover/Title.vue 16 | } 17 | 18 | const { as } = withDefaults(defineProps<TitleProps>(), { | ^^^^^^ 19 | as: “div”, 20 | });
[@vue/compiler-sfc] withDefaults() is unnecessary when using destructure with defineProps(). Reactive destructure will be disabled when using withDefaults(). Prefer using destructure default values, e.g. const { foo = 1 } = defineProps(...).
/home/leonam/code/others/Midone Vue/Vue Version/Source/src/components/Base/Headless/Tab/Tab/Tab.vue 9 | } 10 | 11 | const { fullWidth } = withDefaults(defineProps<TabProps>(), { | ^^^^^^ 12 | fullWidth: true, 13 | });
[@vue/compiler-sfc] withDefaults() is unnecessary when using destructure with defineProps(). Reactive destructure will be disabled when using withDefaults(). Prefer using destructure default values, e.g. const { foo = 1 } = defineProps(...).
/home/leonam/code/others/Midone Vue/Vue Version/Source/src/components/Base/Headless/Disclosure/Disclosure/Disclosure.vue 18 | } 19 | 20 | const { index } = withDefaults(defineProps<DisclosureProps>(), { | ^^^^^^ 21 | index: 0, 22 | });
[@vue/compiler-sfc] withDefaults() is unnecessary when using destructure with defineProps(). Reactive destructure will be disabled when using withDefaults(). Prefer using destructure default values, e.g. const { foo = 1 } = defineProps(...).
/home/leonam/code/others/Midone Vue/Vue Version/Source/src/components/Base/Button/Button.vue 49 | } 50 | 51 | const { as, size, variant, elevated, rounded } = withDefaults( | ^^^^^^ 52 | defineProps<ButtonProps>(), 53 | {
[@vue/compiler-sfc] withDefaults() is unnecessary when using destructure with defineProps(). Reactive destructure will be disabled when using withDefaults(). Prefer using destructure default values, e.g. const { foo = 1 } = defineProps(...).
/home/leonam/code/others/Midone Vue/Vue Version/Source/src/components/Base/Pagination/Link.vue 16 | } 17 | 18 | const { as, active } = withDefaults(defineProps<LinkProps>(), { | ^^^^^^ 19 | as: “a”, 20 | active: false,
[@vue/compiler-sfc] withDefaults() is unnecessary when using destructure with defineProps(). Reactive destructure will be disabled when using withDefaults(). Prefer using destructure default values, e.g. const { foo = 1 } = defineProps(...).
/home/leonam/code/others/Midone Vue/Vue Version/Source/src/components/Base/Table/Table.vue 26 | } 27 | 28 | const { dark, bordered, hover, striped, sm } = withDefaults( | ^^^^^^ 29 | defineProps<TableProps>(), 30 | {
I downloaded the template again, installed the latest Node LTS, ran yarn install, then yarn run dev,
and this shows up:
VITE v5.4.7 ready in 153 ms
➜ Local: http://localhost:5173/ ➜ Network: use—host to expose ➜ press h + enter to show help
A PostCSS plugin did not pass the `from` option to `postcss.parse`. This may cause imported assets to be incorrectly transformed. If you’ve recently added a PostCSS plugin that raised this warning, please contact the package author to fix the issue.
How can I fix this PostCSS error?
Hi there,
Thank you for reaching out. As you can see from the message, this is a warning, not an error. It won’t affect the production build, so we can safely ignore it. Let me know if you need further assistance!
Best regards
Hi, I’ve been trying to install the Vue version of your theme, but all I see when I browse to the site is the below error:
plugin:vite:vue withDefaults() is unnecessary when using destructure with defineProps(). Prefer using destructure default values, e.g. const { foo = 1 } = defineProps(...)
Could you please advise on how to handle this?
Hi there,
Thank you for reaching out! Unfortunately, we couldn’t find an active support license for this item. Please extend your support license so we can assist you further in resolving this issue.
If you need any other help, feel free to contact us.
Best regards
Hi, I’ve renewed the support license as advised.
Thank you for renewing the support license!
We’ve taken note of the issue you’re experiencing, and it seems to be related to the TypeScript compiler. To resolve this, please redownload the file and replace the base component located at the following path: ”/src/components/Base”
Feel free to let us know if the issue persists, and we’ll be happy to assist you further.
Best regards
All working now. Thanks very much for the fast response!
You’re very welcome! I’m glad everything is working now.. 
Hi, there Usining Vue 3 Enigma v1.0.8 I can’t understand, when you go to the site, it seems like all the project files are loaded at once, because of this it opens too slowly in the browser, is this how it should be?
Hi there,
Thank you for your message! Unfortunately, we couldn’t find an active license for this item. Please extend your support license so we can assist you further in resolving the issue you’re experiencing.
If you have any other questions, feel free to reach out.
Best regards
Hi my name is Iqbal, i want to use this template with Laravel11 + inertia + vue 3. Do you have documentation on how to do it ? or example boilerplate on integrated laravel 11 + inertia + vue3 and midone
Hi Iqbal,
Thank you for using our template! Unfortunately, we do not currently support Inertia at this time.
If you have any other questions or need further assistance, feel free to reach out.
Best regards
We are getting an error with Tom-Select, we needed to update vue-tsc because it wouldn’t compile
> nebulous-ui@1.0.0 build > vue-tsc && vite build
node_modules/tom-select/src/vanilla.ts:100:39 – error TS1536: Octal escape sequences and backreferences are not allowed in a character class. If this was intended as an escape sequence, use the syntax ’\x09’ instead.
100 _classes = _classes.trim().split(/[\11\12\14\15\40]/); ~~
node_modules/tom-select/src/vanilla.ts:100:42 – error TS1536: Octal escape sequences and backreferences are not allowed in a character class. If this was intended as an escape sequence, use the syntax ’\x0a’ instead.
100 _classes = _classes.trim().split(/[\11\12\14\15\40]/); ~
node_modules/tom-select/src/vanilla.ts:100:45 – error TS1536: Octal escape sequences and backreferences are not allowed in a character class. If this was intended as an escape sequence, use the syntax ’\x0c’ instead.
100 _classes = _classes.trim().split(/[\11\12\14\15\40]/); ~
node_modules/tom-select/src/vanilla.ts:100:48 – error TS1536: Octal escape sequences and backreferences are not allowed in a character class. If this was intended as an escape sequence, use the syntax ’\x0d’ instead.
100 _classes = _classes.trim().split(/[\11\12\14\15\40]/); ~~
node_modules/tom-select/src/vanilla.ts:100:51 – error TS1536: Octal escape sequences and backreferences are not allowed in a character class. If this was intended as an escape sequence, use the syntax ’\x20’ instead.
100 _classes = _classes.trim().split(/[\11\12\14\15\40]/);
Hi there,
Thank you for using our template and for bringing this issue to our attention. We are aware of the problem with the library.
For the time being, we recommend using the TypeScript version “~5.3.3” to avoid this issue while we search for an alternative plugin reference.
We appreciate your understanding and patience as we work on a solution. If you have any further questions or need assistance, feel free to reach out.
Best regards
Hi, I am using this theme from 2022. And version is 1.0.5. If i want to update theme to latest version Do we have any Upgrade guide?
Hello,
Thank you for reaching out and for being a long-time user of our theme!
We’ve made several updates since version 1.0.5, with one of the most significant changes being the consolidation of all themes into a single unified theme. Due to the extent of these updates, instead of directly upgrading the theme, we recommend starting by updating the base components and dependencies in your package.json file.
This approach will help ensure compatibility and stability as you transition to the latest version. If you need any guidance during this process, feel free to contact us.
Best regards
Who else is waiting for the Nuxt version ?
Hello,
Thank you for using our template! We appreciate your interest in a Nuxt version, and we’ll definitely consider it for the future.
Thanks for your feedback!
Best regards
