bytefury supports this item


This author's response time can be up to 2 business days.

60 comments found.

Hello, I have some pre-sale questions:

Do you provide composer.json, package.json and all necessary files required to modify the script? Also, which version of css/js files are included in the downloaded zip file? It is compressed or non-compressed version?

Hello there,

Yes the script is 100% customizable with all the needed files and it also contains full sass files so that you can make changes to our existing code as well.



your template asset helper is not pointing to public folder like a normal laravel projects, could you please show me how to modify it ?

Hi there!

Which development server are you testing Laraspace on?

Please make sure that it meets the minimum requirements specified in documentation.

If you’re still stuck please contact me on email `` and I’ll try to resolve your issue.

Thank you

Hi, is it possible to allow push messages from Laravel to show up in Vue? Like VuePusher?

Hi there,

We don’t provide support for that feature out of the box but you can integrate that easily if you are experienced enough with VueJs and laravel.

Mayb Laravel echo would be a better choice than vuepusher for this kind of a thing considering we already use laravel in backend.



kevix Purchased

JWTAuth appears to be applied to your Vue project, but the Laravel project doesn’t. I do not know why. Also I was wondering if there are any other differences except for that. Thank you.

We’ll test on IE and get back to you.


kevix Purchased

Any news on this? is your SPA version not working on IE?

Hi there!

Sorry for the late reply but this will be fixed in the next update.

For now, You can try this workaround: Please add the below script inside `app.blade.php` above </head> tag.

<script src=""></script>

Hello, when i npm run dev I get the following error: > @ dev C:\xampp\htdocs\Laravel > cross-env NODE_ENV=development webpack --watch --progress --hide-modules fallbackLoader option has been deprecated - replace with "fallback" loader option has been deprecated - replace with "use" fallbackLoader option has been deprecated - replace with "fallback" loader option has been deprecated - replace with "use" Invalid configuration object. Webpack has been initialised using a configuration object that does not match the API schema. - configuration.output.path: The provided value "public" is not an absolute path! npm ERR! code ELIFECYCLE npm ERR! errno 1 npm ERR! @ dev: `cross-env NODE_ENV=development webpack --watch --progress --hide-modules` npm ERR! Exit status 1 npm ERR! npm ERR! Failed at the @ dev script 'cross-env NODE_ENV=development webpack --watch --progress --hide-modules'. npm ERR! Make sure you have the latest version of node.js and npm installed. npm ERR! If you do, this is most likely a problem with the package, npm ERR! not with npm itself. npm ERR! Tell the author that this fails on your system: npm ERR! cross-env NODE_ENV=development webpack --watch --progress --hide-modules npm ERR! You can get information on how to open an issue for this project with: npm ERR! npm bugs npm ERR! Or if that isn't available, you can get their info via: npm ERR! npm owner ls npm ERR! There is likely additional logging output above. npm ERR! A complete log of this run can be found in: npm ERR! C:\Users\Nicolas\AppData\Roaming\npm-cache\_logs\2017-04-01T14_31_37_627Z-debug.log please help

I tried this (locking my webpack to “webpack”: “2.2.1” in package.json) and solved my problem:

Glad you figured it out yourself nroussis84.

This problem will be solved in the next bugfix update to upgrade laravel-mix to latest version.


Hello, I try to add plugins on the installation of Laraspace, only by launching the compilation commands it does not work, I send you the logs of errors. On all my development with npm and laravel mix it works very well, but there npm run dev not at all … Thank you for your help, Raphael

LOGS—> 0 info it worked if it ends with ok 1 verbose cli [ ‘C:\\Program Files\\nodejs\\node.exe’, 1 verbose cli ‘C:\\Users\\Raphaël\\AppData\\Roaming\\npm\\node_modules\\npm\\bin\\npm-cli.js’, 1 verbose cli ‘run’, 1 verbose cli ‘dev’ ] 2 info using npm@4.2.0 3 info using node@v6.9.5 4 verbose run-script [ ‘predev’, ‘dev’, ‘postdev’ ] 5 info lifecycle ~predev: 6 silly lifecycle @predev: no script for predev, continuing 7 info lifecycle ~dev: 8 verbose lifecycle @dev: unsafe-perm in lifecycle true 9 verbose lifecycle @dev: PATH: C:\Users\Raphaël\AppData\Roaming\npm\node_modules\npm\bin\node-gyp-bin;C:\laragon\www\wently\node_modules\.bin;C:\Users\Raphaël\bin;C:\Program Files\Git\mingw64\bin;C:\Program Files\Git\usr\local\bin;C:\Program Files\Git\usr\bin;C:\Program Files\Git\usr\bin;C:\Program Files\Git\mingw64\bin;C:\Program Files\Git\usr\bin;C:\Users\Raphaël\bin;C:\Program Files (x86)\Common Files\Intel\Shared Libraries\redist\intel64\compiler;C:\Program Files (x86)\NVIDIA Corporation\PhysX\Common;C:\Program Files (x86)\Intel\iCLS Client;C:\Program Files\Intel\iCLS Client;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0;C:\Program Files\Intel\Intel® Management Engine Components\DAL;C:\Program Files\Intel\Intel® Management Engine Components\IPT;C:\Program Files (x86)\Intel\Intel® Management Engine Components\DAL;C:\Program Files (x86)\Intel\Intel® Management Engine Components\IPT;C:\Program Files\Intel\WiFi\bin;C:\Program Files\Common Files\Intel\WirelessCommon;C:\Program Files (x86)\Skype\Phone;C:\Program Files (x86)\QuickTime\QTSystem;C:\wamp64\bin\php\php7.0.0;C:\ProgramData\ComposerSetup\bin;C:\Program Files\nodejs;C:\Program Files (x86)\Brackets\command;C:\Ruby23-x64\bin;C:\Program Files\Intel\WiFi\bin;C:\Program Files\Common Files\Intel\WirelessCommon;C:\Users\Raphaël\AppData\Local\Microsoft\WindowsApps;C:\Users\Raphaël\AppData\Roaming\npm;C:\Program Files (x86)\Microsoft VS Code\bin;C:\Program Files\Git\usr\bin\vendor_perl;C:\Program Files\Git\usr\bin\core_perl 10 verbose lifecycle @dev: CWD: C:\laragon\www\wently 11 silly lifecycle @dev: Args: [ ’/d /s /c’, 11 silly lifecycle ‘cross-env NODE_ENV=development webpack—watch—progress—hide-modules’ ] 12 silly lifecycle @dev: Returned: code: 1 signal: null 13 info lifecycle @~dev: Failed to exec dev script 14 verbose stack Error: @ dev: `cross-env NODE_ENV=development webpack—watch—progress—hide-modules` 14 verbose stack Exit status 1 14 verbose stack at EventEmitter.<anonymous> (C:\Users\Raphaël\AppData\Roaming\npm\node_modules\npm\lib\utils\lifecycle.js:279:16) 14 verbose stack at emitTwo (events.js:106:13) 14 verbose stack at EventEmitter.emit (events.js:191:7) 14 verbose stack at ChildProcess.<anonymous> (C:\Users\Raphaël\AppData\Roaming\npm\node_modules\npm\lib\utils\spawn.js:40:14) 14 verbose stack at emitTwo (events.js:106:13) 14 verbose stack at ChildProcess.emit (events.js:191:7) 14 verbose stack at maybeClose (internal/child_process.js:877:16) 14 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:226:5) 15 verbose pkgid @ 16 verbose cwd C:\laragon\www\wently 17 error Windows_NT 10.0.14393 18 error argv “C:\\Program Files\\nodejs\\node.exe” “C:\\Users\\Raphaël\\AppData\\Roaming\\npm\\node_modules\\npm\\bin\\npm-cli.js” “run” “dev” 19 error node v6.9.5 20 error npm v4.2.0 21 error code ELIFECYCLE 22 error errno 1 23 error @ dev: `cross-env NODE_ENV=development webpack—watch—progress—hide-modules` 23 error Exit status 1 24 error Failed at the @ dev script ‘cross-env NODE_ENV=development webpack—watch—progress—hide-modules’. 24 error Make sure you have the latest version of node.js and npm installed. 24 error If you do, this is most likely a problem with the package, 24 error not with npm itself. 24 error Tell the author that this fails on your system: 24 error cross-env NODE_ENV=development webpack—watch—progress—hide-modules 24 error You can get information on how to open an issue for this project with: 24 error npm bugs 24 error Or if that isn’t available, you can get their info via: 24 error npm owner ls 24 error There is likely additional logging output above. 25 verbose exit [ 1, true ]

Hi there!

We’ve uploaded an update which solves all the issues related to laravel mix.

Once the update gets live (probably a day or two), you’ll get a notification from envato about it.

If the error still persists, try updating nodejs & npm to latest version and see if it fixes the problem.

Thank you for purchasing laraspace :)

Hello ! Super, it seems that everything works since the update of your package that I just installed. I’ll be able to start having fun coding! Your package looks really great! Thank you !

So glad to hear that!

Happy coding :)


kevix Purchased

Hi, I puarchased and have used your Laraspace, and there is an error – all the aria-expanded(or dropdown) areas are no expanded when clicked. There seems to be a collision between Laraspace and my codes. Which part should I look at to handle the issue? Most of the source codes are already complied into ‘plugin.js’, so it is hard for me to track every file back to a ‘dropdown’ part. Otherwise, please explain how to expand them. (I don’t know much about Bootstrap js.)

Hi there,

Please read more about Bootstrap dropdowns using the below link and see if you can find the difference between your markup and the expected markup for dropdowns to work.

Link :

If you’re still stuck, Please contact me through the form on my profile page and I’ll help you fix the problem :)

Good day.

Demo does not work. Blank page. Console:

mediasource-A249085-fc90-4e98-904f-95b25288c53b1-c-4415.min.js Failed to load resource: net::ERR_BLOCKED_BY_CLIENT 16611146:1 Refused to display ‘' in a frame because it set ‘X-Frame-Options’ to ‘sameorigin’. Failed to load resource: net::ERR_BLOCKED_BY_RESPONSE /favicon.ico Failed to load resource: the server responded with a status of 404 (Not Found)

The problem seems to occur after we installed SSL Certificate for our website.

`https` sites don’t seem to be working with Envato preview.

Thank you very much for letting us know about it.

We’ll solve the problem asap.

I purchased and am diving in now. Looks GREAT!!

So glad to hear that :)

Let me know if you need help with anything.

Have a nice day.

Hi. I have a pre-buy question that I hope you will answer. How much functionality is already made with laravel? Is the preview all of it? Im thinking login, editing user, create user and such.

Hi there!

Laraspace has admin authentication built-in.

However not every application out there requires Users CRUD, thus we haven’t included that with Laraspace. But you can easily build a user crud with very little effort , Thanks to Laravel.

Please check the docs to know about all the features in Laraspace:


Hello, i loved this template:

I’m starting with vueJs, my answer is: I have a project created with vue-cli (vue 2.1 version) with webpack default settings provided by cli.

Can i use your template in this project easily? Can you speak about installation in existent project? Thank’s, and sorry for my English.

Hey there!

Currently Laraspace is only for Laravel Applications and it would take a lot of effort to make it work inside a existing project.

However we have a simple HTML & VueJS only release planned to be released on themeforest soon which is exactly what you’re looking for.

Stay tuned!

Thanks :)

Laraspace have ACL front/backend?

It means end of june acl and will added ? ;)

Yes! It will be.

Thanks, wait for!


kevix Purchased

Hi, I am trying your Vue project, and thought a simple modal is included in this project. But no. So I would appreciate if you could let me know how to pop up a modal in your vue project ^^ (I am new to use vue.js)

Hi There,

It is a Bootstrap 4 admin template so you can easily use the default modals provided by bootstrap.

Use the markup as mentioned in bootstrap documentation and open the modals with `data-attribute` or directly through methods like below. $('#myModal').modal('show') Read more about it here :

Thank you.

Hi, i have a little problem when trying to use multiple levels of Nesting on my Vue Routes. What happens is that whenever i use multiple levels of nesting a click one of the router-links all of the sidebar UL’s open at once and i can’t close them again, so this is either related to VueRouter itself or MetisMenu.

path: "/admin/", component: MasterLayout, children: [
       { path: "reports", component: MasterLayout, children: [
         { path: "country",            component: CountryReport },
         { path: "leads",               component: LeadReport },
         { path: "financial",          component: FinancialReport },

Is this related to Vue itself or is it something with Metis that can be fixed? I ask because i wanted to use tabs on some of these pages to load some more specific views and that’s just a hassle to do if i have to add a top-level route without any nesting :(

Hi Jonny,

Have you made any changes to the default layout by any chance because that shouldn’t happen at all,

metisMenu is initialized in `layouts/partials/SiteSidebar.vue` on mounted() hook.

Can you check the console to see if there’s any error when menu stops working.

Please contact me at with more info and I’ll help you solve this issue asap.


Hi, I am interested in Laraspace and would like to try it. Do I have to purchase it to do so? And if it doesn’t fit my needs, will I then get a refund?

Thanks Gilles

I ‘ve just seen that Envato’s policy for refunds doesn’t cover evaluating the product, I understand.

I would have liked to see how Laraspace integrates into an existing Laravel app. I don’t want the admin to impose many constraints on the app files and directory structure.

More specifically, my app is served on several sub-domains (api, account) and I use related controller’s namespaces to isolate the logic for each sub-domain (namespace app\Http\Controllers\Api…). I would like to keep it that way for the admin: serve it on an admin subdomain and have the controllers in an app\Http\Controllers\Admin namespace.

Is this possible with Laraspace? And do you add more files or folders in the Laravel’s app folder?

Or all this part is kept in the vendor folder? If so, what if I need to override some of your controller’s logic, how can I do this?

Please take the time to answer each of my questions as I need the answers to be able to buy (which I am really willing to do!).

Hi there,

Laraspace uses laravel’s default directory structure, so it should be pretty easy to customize or make it work with an existing project.

Everything you mentioned can be easily done!

Please check for more information.

Any news for v1.4?

Hi Samuel!

We’ve added a lot of components/pages for laravel admin but we still have some small issues that need to be resolved before we release it.

We’ll be releasing the update as soon as its production ready.


I get an error when I run npm run dev :

error in ./resources/assets/admin/js/pages/todos.js Module build failed: ReferenceError: [BABEL] /home/vagrant/Code/laravel/resources/assets/admin/js/pages/todos.js: Unknown option: direct.presets at Logger.error (/home/vagrant/Code/laravel/node_modules/babel-core/lib/transformation/file/logger.js:58:11) ... error in ./resources/assets/admin/js/pages/dashboard.js Module build failed: ReferenceError: [BABEL] /home/vagrant/Code/laravel/resources/assets/admin/js/pages/dashboard.js: Unknown option: direct.presets

Glad to know that!

Have a nice day.

I must say that I am very pleased with Laraspace: it does exactly what I wanted, have a default admin project with everything in place so I can quickly start my own without needing to do a lot of setup and make a lot of library choices.

I have incorporated it inside an existing Laravel project, so it took me some time to merge the two, but that was easy since Laraspace doesn’t impose anything, you just keep what’s good for you and change or remove what is not.

Some aspects could be improved though:

- More documentation about the included javascript plugins: I don’t need all of them, so I prefer to disable them and add them back when I need them. Comments could for example be added in the webpack file.

- The Laraspace namespace is ok when starting a project from scratch but using the default “App” would make it already compatible with existing applications that kept the default (that was not very heavy to change though)

- The AuthController could benefit more from the AuthenticateUsers trait default behaviors, by just overriding the methods needed (showLoginForm, logout method to control views and redirections, $redirectTo property…).

- The rules for the default skin could be isolated inside a skin-default file, so customizing the default theme can be done without editing the others files, if one wants to start from this skin.

All these are minor improvements, Laraspace is good value for the money and it was worth paying.

Hi gilles555,

First of all thank you very much for taking the time to review Laraspace, I really appreciate it :).

We will surely look into all of the points you mentioned.

Sometimes we tend to ignore small details while working on the next big feature but a review like this helps us know about small issues that our users are facing while creating awesome web apps using Laraspace.

While working on Laraspace, if you come across any issue or if you have some more suggestions make things easier, Please don’t hesitate to post a comment here or send me an email on `

Thanks :D


Xevo Purchased

Really interested in buying this, got a couple of questions though.

It says that you have included Vue Crud, however I do not see Vuex included?

I also take it that the vue system is build as an SPA?

Hi Xevo,

We’ve included an example Vue CRUD to demonstrate how it works with Laravel.

However we haven’t included VUEX because not everyone needs it.

You can easily include vuex if your application requires it :)

And to answer your last question, Yes the vue admin is built as a SPA.

This is so well done! Lightyears beyond other similar Laravel admin templates I’ve tried from codecanyon. Thank you!

Would it be possible to integrate with Laravel Spark? I suspect it’s possible but could you help or point me in the right direction? I’m new to Vue, but excited to learn.

Hi there,

Thank you very much for the kind words!

Although We’ve never used Laravel Spark, you can easily integrate all the components of Laraspace into your spark project by pasting the contents of `resources` folder into your spark project and including all the required assets into your layout.

If you have any other suggestion or need any further help, you can contact me directly at ``.


Hello Mohit;

I need your help; do you know how to fix the following error after run "npm run production" ?
 I'm working on the latest version of Laraspace Laravel.
Image error :


This error is actually related to laravel mix.

Can you try updating your nodejs and laravel-mix to latest version?

That should fix it.


RTL version please!