251 comments found.
Please give me gitlab access @otakujonn – I am receiving errors when running npm run dev, build and generate on NODE_VER v14.16.0
Error: Callback was already called.
at throwError (C:\...\node_modules\neo-async\async.js:16:11)
at C:\...\node_modules\neo-async\async.js:2818:7
at processTicksAndRejections (internal/process/task_queues.js:75:11)
Hi,
Access granted.
Not sure whats causing the error. I’ve got node v14.15.1 and works just fine.
To try and resolve the issue, please do:
1. remove node_modules folder 2. remove package-lock.json 3. remove npm cache (npm cache clear --force) 4. reinstall packages (npm install)
Please let me know if that solved the issue.
Thanks!
i am getting below error when npm run dev NODE VER = v14.6.0 NPM VER = 6.14.11
/eac-lms/components/Page.vue 1:1 error Parsing error: Unexpected token <
✖ 1 problem (1 error, 0 warnings)
friendly-errors 15:55:57
@ ./node_modules/babel-loader/lib??ref--2-0
./pages/_layout/ui-drawer-layout.vue?vue&type=script&lang=js& 9:0-36 9:163-167
@ ./pages/_layout/ui-drawer-layout.vue?vue&type=script&lang=js&
@ ./pages/_layout/ui-drawer-layout.vue
@ ./.nuxt/router.js
@ ./.nuxt/index.js
@ ./.nuxt/client.js
@ multi ./node_modules/eventsource-polyfill/dist/browserify-eventsource.js (webpack)-hot-middleware/client.js?reload=true&timeout=30000&ansiColors=&overlayStyles=&path=%2F__webpack_hmr%2Fclient&name=client ./.nuxt/client.js
friendly-errors 15:55:57ERROR in ./components/Settings.vue friendly-errors 15:55:57Module Error (from ./node_modules/eslint-loader/dist/cjs.js):
Hi,
Have you changed anything after downloading the code?
Could you please make sure the download wasn’t affected and re-download then try again?
Thanks!
Also, it’s worth trying the following:
1. remove node_modules folder 2. remove package-lock.json 3. remove npm cache (npm cache clear --force) 4. reinstall packages (npm install)
It may fix the issue.
Please give me gitlab access @sk8027
Access granted!
I am planning to get the vue/nuxt version and can I configure it with Firebase backend just as the rest of other templates? Are there any challenges doing so? Thanks
Hi,
That’s a great question. It Should be possible just fine, vue components don’t care about where the data is coming from. Please let me know if you struggle with anything and I’ll try to help. Thank you!
Does this template allow me to create a fresh project repo and copy over only the components and things I need or am I required to build my project in the original template repo?
can you grant me access to gitlab repo: @ikmalsuzali. Also when I run npm run dev, no changes are made?
Hi, access granted.
Which files are you changing exactly?
Hello Guys Which version of Vue js is used.
Hi,
It’s Vue 2.6.
Can you add me on gitlab: @enorenio
Done
Hi please add me for latest gitlab update. My instance is not running locally has issues.
Lucas Allen GITLAB: @ln2x Member since May 23, 2019 lallen@ln2x.comAccess granted. What error are you getting?
Hey guys. Any fix for this issue? In https://luma-nuxt.demo.frontendmatter.com/fixed/student-course/ Scroll down to “Top Development Courses” Click on the button of the carousel and it takes you to index :/ Basically the carousel is not working when clicking on the next button
I have used version 1.1 before and it was working when i made ADMIN group to sidebar like this :
components/App/Sidebar.vue:
<div class="sidebar-heading">Admin</div>
<fmv-sidebar-menu
:menu="i18nMenu.admin"
class="mb-24pt" />
sidebarMenuConfigs.js :
export const admin = [{......}]
....
export const state = () => ({
student,
instructor,
admin,
....
And today we tried to use latest version of template and it is not working on latest version. We could not add Group to sidebar.
How to solve this problem ?
Hi,
Only the admin doesn’t show? I need to see the code for the admin variable.
Thanks!
I have copied Instructer variable from above.
export const admin = [{
{
label: 'Admin Dashboard',
route: 'instructor-dashboard',
icon: {
type: 'md-icon',
id: 'school'
}
}, {
label: 'Admin Courses',
route: 'instructor-courses',
icon: {
type: 'md-icon',
id: 'import_contacts'
}
}
Our platfrom needs 3 types of users. School admins, teachers, students
Hello, I love the nuxt template but it looks like I’m not going to use it as nuxt. any chance you can send me the HTML version, I’m using it to learn Angular and I want to start from scratch.
802ad001-659a-4a84-b3c5-c483cc668f77 – 28 Oct 2020 REGULAR LICENSE
Hi,
Thanks for not answering my last comment 24 days ago 
Now I have another question and please this time answer as this is something very annoying with the template.
There is this bluish overlay on the images of coursecard and I can’t get rid of it. I want the images in coursecard to be seen as they are.
Cheers
Hi,
Sorry about that. I’m officially starting work on Monday 11 Jan.
You can edit vue-luma/components/Course/CourseCard.vue and remove the overlay—primary class from the card.
Let me know if you need help with that.
Thanks!
It might be easier to override the css, from your main app.scss file:
.overlay--primary {
.overlay__content {
background-color: none;
}
&.overlay--show .overlay__content {
background-color: none;
}
}
Hey man, Congrats on the new job. Thanks for the tip, I used the css but put transparent instead of none and it did the trick. Cheers
Hi, I’m trying to install Luma but I’m getting this error during npm install.
Can you help me?
D:\codigos-fonte\luma-nuxt-v2.2.0\luma-nuxt-v2.2.0>npm install npm WARN deprecated eslint-loader@4.0.2: This loader has been deprecated. Please use eslint-webpack-plugin npm WARN deprecated popper.js@1.16.1: You can find the new Popper v2 at @popperjs/core, this package is dedicated to the legacy v1 npm WARN deprecated core-js@2.6.12: core-js@<3 is no longer maintained and not recommended for usage due to the number of issues. Please, upgrade your dependencies to the actual version of core-js@3. npm WARN deprecated chokidar@2.1.8: Chokidar 2 will break on node v14+. Upgrade to chokidar 3 with 15x less dependencies. npm WARN deprecated fsevents@1.2.13: fsevents 1 will break on node v14+ and could be using insecure binaries. Upgrade to fsevents 2. npm WARN deprecated urix@0.1.0: Please see https://github.com/lydell/urix#deprecated npm WARN deprecated resolve-url@0.2.1: https://github.com/lydell/resolve-url#deprecated npm ERR! code ENOENT npm ERR! syscall spawn git npm ERR! path git npm ERR! errno -4058 npm ERR! enoent Error while executing: npm ERR! enoent undefined ls-remote -h -t ssh://git@github.com/10bestdesign/jqvmap.git npm ERR! enoent npm ERR! enoent npm ERR! enoent spawn git ENOENT npm ERR! enoent This is related to npm not being able to find a file. npm ERR! enoent npm ERR! A complete log of this run can be found in: npm ERR! C:\Users\rafae\AppData\Roaming\npm-cache\_logs\2021-01-07T13_56_31_469Z-debug.log
Hi,
You can remove the faulty package from vendor/ui-huma/package.json:
"jqvmap": "github:10bestdesign/jqvmap#master",
Then delete the node_modules folder and try npm install again. Let me know if that solved the issue!
Thanks.
Hi there,
Please I’m trying to understand what makes the chat messages display left or right once I send a message https://luma-nuxt.demo.frontendmatter.com/default/messages/Hi,
I apologize for the delay!
You need to override the following from vendor/ui-huma/scss/_messages.scss:
.message {
&__aside {
margin-right: 1rem;
}
&:nth-child(even) {
.message__aside {
order: 1;
margin-right: 0;
margin-left: 1rem;
}
.message__body {
margin-left: auto;
}
}
}
Or, you could simply override from the main app.scss file:
// reset all to left
.message:nth-child(even) {
.message__aside {
order: 0;
margin-right: 1rem;
margin-left: 0;
}
.message__body {
margin-left: 0;
}
}
// add .message.message--right
.message.message--right {
.message__aside {
order: 1 !important;
margin-right: 0 !important;
margin-left: 1rem !important;
}
.message__body {
margin-left: auto !important;
}
}
Now all messages will be left aligned by default and you only need to apply .message—right class to the container with the .message class to align it to the right.
Let me know if you need further help!
Hi! When will the dark theme be available on the NuxtJS version? Thanks!
C:\Users\LN2X\Desktop\luma-nuxt-v2.2.0>npm install npm@latest -g C:\Users\LN2X\AppData\Roaming\npm\npm -> C:\Users\LN2X\AppData\Roaming\npm\node_modules\npm\bin\npm-cli.js C:\Users\LN2X\AppData\Roaming\npm\npx -> C:\Users\LN2X\AppData\Roaming\npm\node_modules\npm\bin\npx-cli.js + npm@6.14.10 updated 1 package in 7.595s
C:\Users\LN2X\Desktop\luma-nuxt-v2.2.0>npm install npm WARN saveError ENOENT: no such file or directory, open ‘C:\Users\LN2X\Desktop\luma-nuxt-v2.2.0\package.json’ npm WARN enoent ENOENT: no such file or directory, open ‘C:\Users\LN2X\Desktop\luma-nuxt-v2.2.0\package.json’ npm WARN luma-nuxt-v2.2.0 No description npm WARN luma-nuxt-v2.2.0 No repository field. npm WARN luma-nuxt-v2.2.0 No README data npm WARN luma-nuxt-v2.2.0 No license field.
up to date in 0.748s found 0 vulnerabilities
C:\Users\LN2X\Desktop\luma-nuxt-v2.2.0>
Hi,
If the package.json file is missing, you should re-download the item from your envato account. It’s possible something might have happened with the archive either when you downloaded, because of the internet connection or something might of happened when you unzipped it. Please redownload, unzip and confirm the package.json file exists, then try running npm install again.
Please let me know if that solves the issue. Thank you!
I want to ask about the design file.
Hi , please add me into gitlab repo , thanks. Here is the account username @Poxo
Hi, access granted!
✖ Client Compiled with some errors in 10.39s
● Server █████████████████████████ emitting (95%) vue-server-plugin
ERROR Failed to compile with 2 errors friendly-errors 03:07:46- vue-luma in ./node_modules/babel-loader/lib??ref—2-0
./node_modules/vue-loader/lib??vue-loader-options!./pages/_layout/billing.vue?vue&type=script&lang=js&
- ~/components/Page in ./node_modules/babel-loader/lib??ref—2-0
Hi,
That is so strange! No one had this error before. Can you please redownload the package again? Maybe something was wrong when downloading or when unzipping the archive and then try again.
Please let me know if you still get the same error once you do that. Also if you’re still getting the same error let me know what’s your environment, operating system, node version and npm version.
Also, have you modified anything?
