mercredi 14 octobre 2015

Laravel Gulp not creating js folder

I am currently trying to get gulp to run on my Laravel project.

I can successfully run gulp on my app.scss

I am trying to run gulp on a test coffee script, the coffee script is found in resources > assets > coffee > test.coffee

here is my gulpfile.js

var elixir = require('laravel-elixir');

/*
 |--------------------------------------------------------------------------
 | Elixir Asset Management
 |--------------------------------------------------------------------------
 |
 | Elixir provides a clean, fluent API for defining some basic Gulp tasks
 | for your Laravel application. By default, we are compiling the Sass
 | file for our application, as well as publishing vendor resources.
 |
 */

elixir(function(mix) {
    mix.sass('app.scss');
    mix.coffee();
});

When I run gulp I get this error.

fetching Sass Source Files...
   - resources/assets/sass/app.scss


Saving To...
   - public/css/app.css

[23:08:58] Finished 'default' after 313 ms
[23:08:58] gulp-notify: [Laravel Elixir] Sass Compiled!
[23:08:58] Finished 'sass' after 403 ms
[23:08:58] Starting 'coffee'...
[23:08:58] 'coffee' errored after 311 μs
[23:08:58] TypeError: Cannot call method 'indexOf' of undefined
    at prefixOne (/home/pocockn/projects/http://ift.tt/1jAI39a)
    at GulpPaths.prefix (/home/pocockn/projects/http://ift.tt/1G6qcBt)
    at GulpPaths.src (/home/pocockn/projects/http://ift.tt/1jAI3pq)
    at prepGulpPaths (/home/pocockn/projects/http://ift.tt/1G6qcBv)
    at null.definition (/home/pocockn/projects/http://ift.tt/1jAI3pu)
    at Task.run (/home/pocockn/projects/http://ift.tt/1jAI5xJ)
    at Gulp.<anonymous> (/home/pocockn/projects/http://ift.tt/1G6qcBx)
    at module.exports (/home/pocockn/projects/http://ift.tt/1jAI3pw)
    at Gulp.Orchestrator._runTask (/home/pocockn/projects/http://ift.tt/1G6qdFB)
    at Gulp.Orchestrator._runStep (/home/pocockn/projects/http://ift.tt/1jAI5xN)
[23:08:58] Error in plugin 'run-sequence'
Message:
    An error occured in task 'coffee'.

Has anyone else experienced this error?



via Chebli Mohamed

Aucun commentaire:

Enregistrer un commentaire