bytefury supports this item


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

51 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.


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.

Hey there,

Both versions are for completely different use cases thus there’s no reason for them to be the same. So JWTAuth is only applied to vue version because its a single page application.

While Laravel version does not need JWTAuth because it works on default session based authentication.

Let me know if there’s any other confusion.


Um.. then I was wondering if your SPA version works on IE properly. Now for the SPA version, Admin Dashboard button is clickable on Chrome but not on IE.

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

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 :)

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!