jadjoubran / laravel5-angular-material-starter

Get started with Laravel 5.3 and AngularJS (material)
https://laravel-angular.readme.io/
MIT License
1.66k stars 400 forks source link

gulp && gulp watch gives Elixer version error on final.js #430

Closed kumarravisingh closed 7 years ago

kumarravisingh commented 7 years ago

On my browser console i get

GET http://localhost:8000/build/js/final-7939682aa0.js fail to load response data And GET http://localhost:8000/build/js/final-7939682aa0.js 500 internal server error

kumarravisingh commented 7 years ago

By searching I found out that it is .copy() function issue in gulpfile.js and I need to move them to storage/app/public but here I don't think that will be an option.

Stackoverflow answer Stackoverflow solution Something like this : removing these lines from gulpfile.js:

.copy('resources/assets/fonts', 'public/build/fonts') .copy('resources/assets/images', 'public/build/images')

placing the fonts and images folders into the storage/app/public running PHP artisan storage:link

changing the paths in the assets files to the new directory

running gulp

jadjoubran commented 7 years ago

Thanks @kumarravisingh for this To make sure I got what you mean: the problem only happens with any file type that isn't a JS, HTML or CSS right? So that's why the problem is for fonts and images And the reason why they must be in build is to maintain the same paths? or can't they be fixed by just using absolute paths /images/.. and /fonts/..?

kumarravisingh commented 7 years ago

Oh. .sry for bad explanation :( All I know is there is an error whenever I run gulp && gulp watch which seems like a versioning issue.

stream.js:74 throw er; // Unhandled stream error in pipe. ^ Error: ENOENT: no such file or directory, stat 'C:\laragon\www\cms\public\build\js\final-393dd5527e.js' at Error (native)

and I can't solve it.

kumarravisingh commented 7 years ago

Also, there is no issue with version : 3.2, it is occurring in version 3.4 only.

gultomic commented 7 years ago

laravel/elixir#626

gultomic commented 7 years ago

I'm facing the same issue on windows, seems it because versioning in my case have manually running gulp till the versioning filename get change then running gulp watch

hope this will help you too

jadjoubran commented 7 years ago

Thanks @albertgultom for the temporary fix Let's keep it open and hope for a fix in upstream

craigjmidwinter commented 6 years ago

Sorry to bump an old issue, but the link to the fix for this is gone. Any idea what it was? Seeing the same versioning issue

jadjoubran commented 6 years ago

Hi @wardcraigj so this fix did not work for you?

mtx-z commented 6 years ago

It didn't for me...

jadjoubran commented 6 years ago

@mtx-z please open a new issue with the error message Thanks!