niki4810 / gulp-devtools

Gulp task runner extension for chrome devtools

Hi there 👋

• 🔭 I’m currently working as a Principle Software Engineer at Walmart global eCommerce.
• 🌱 I’m currently learning: remix.run, react-query, graphql, K8S, TypeScript

gulp-devtools's Issues

coffeescript support

gulp introduced native gulpfile.coffee support since version >= 3.7.0; as of today there is no way to use this module withough going through a gulpfile.js

gulp-devtools throws error no matter what Gulp task I try and run

I keep getting an error when I try and run any of my Gulp tasks through gulp-devtools in Chrome (v35.0.1916.153):

C:\Program Files\WAMP Server 2\www\gulp-starter>gulp-devtools
Gulp Tasks loaded, fire up your chrome devtools
   info  - socket.io started
Running Task:stats

events.js:72
        throw er; // Unhandled 'error' event
              ^
Error: spawn ENOENT
    at errnoException (child_process.js:988:11)
    at Process.ChildProcess._handle.onexit (child_process.js:779:34)

And here is my task:

gulp.task('stats', function(){
    return gulp.src(srcJs)
        .pipe($.complexity())
    ;
});

Any ideas what I'm doing wrong?

Unable to successfully use with Chrome 35 and 36

I've been testing this project against the output of generator-gulp-webapp (a valid Gulp project) with the recommended one-line changes made to my Gulpfile.

Unfortunately, even with a fresh project following the steps in the readme I wasn't able to get Gulp DevTools successfully connecting up to my project once gulp-devtools was run. This was with Chrome Beta and Chrome Canary. Does this extension currently work in these versions of Chrome?

TypeError: Object.keys called on non-object

Hi @niki4810 !

npm installed locally with PATH enhancement. Got this:

$ gulp-devtools 
gulp.env has been deprecated. Use your own CLI parser instead. We recommend using optimist or minimist.

/Users/rroemer/scm/fmd/training/node_modules/gulp-devtools/lib/gulp-devtools.js:13
  var gulpTasks = Object.keys(gulpFile.tasks).sort();
                         ^
TypeError: Object.keys called on non-object
    at Function.keys (native)
    at Object.gulpDevTools [as init] (/Users/rroemer/scm/fmd/training/node_modules/gulp-devtools/lib/gulp-devtools.js:13:26)
    at Object.<anonymous> (/Users/rroemer/scm/fmd/training/node_modules/gulp-devtools/bin/gulp-devtools.js:3:5)
    at Module._compile (module.js:456:26)
    at Object.Module._extensions..js (module.js:474:10)
    at Module.load (module.js:356:32)
    at Function.Module._load (module.js:312:12)
    at Function.Module.runMain (module.js:497:10)
    at startup (node.js:119:16)
    at node.js:902:3

Test coverage

It seems like you have a great tool here for developers using Gulp. The only downside is that I see no tests. It shouldn't take too much as it is a fairly simple plugin.

gulp task in different file is not working

we have a modularized gulp task residing in various smaller unit of files.

Line: 13 var gulpFilePath = path.join(process.cwd(), "gulpfile"); may not have all tasks to fetch.
so gulp-devtools is failing for this instance. any thoughts on this would be help-full.

Updating Dependencies

May be good to update the dependencies, not a big issue. Just good to keep them up-to-date.

• socket.io can be updated from ~0.9.16 to ~1.0.6
• gulp can be updated from ~3.6.2 to ~3.8.6
• gulp-jshint can be updated from ~1.5.5 to ~1.8.0
• jshint-stylish can be updated from ~0.2.0 to ~0.4.0

Socket.io: Port already use

Hey there!

Awesome extension! I like how I can run tasks in the background. A question: how can you have it work for more than one project? When I type gulp-devtools for project A it works fine. When I do it in project B with A still open, I get the following:

info  - socket.io started
warn  - error raised: Error: listen EADDRINUSE

Is it because I cannot have more than 1 project running at the same time?

Cheers

Notify on errors?

It would be nice if the extension would display or atleast notify about errors specially when watching and running tasks.

Gulp 4.0 support?

We are getting very close to releasing gulp 4.0 with a new API. Are there any plans to support 4.0?

You might find the gulp.tree() API helpful for getting tasks that have been registered.

I bring this up due to an outstanding issue we have open at gulpjs/gulp#365

Cannot find gulp-devtools

❯ gulp-devtools

module.js:340
    throw err;
    ^
Error: Cannot find module 'gulp-devtools'
    at Function.Module._resolveFilename (module.js:338:15)
    at Function.Module._load (module.js:280:25)
    at Module.require (module.js:364:17)
    at require (module.js:380:17)
    at Object.<anonymous> (/Users/kevinsuttle/Code/myapp/gulpfile.js:6:16)
    at Module._compile (module.js:456:26)
    at Object.Module._extensions..js (module.js:474:10)
    at Module.load (module.js:356:32)
    at Function.Module._load (module.js:312:12)
    at Module.require (module.js:364:17)

❯ gulp -v
[gulp] CLI version 3.6.0
[gulp] Local version 3.6.2

OS X 10.9.3
npm 1.4.10
node 0.10.28

Remove node-gyp

Is there any chance this dependency could be removed? node-gyp can be a pain for Windows users. I've had it a lot in the past.

For example, the errors gotten when trying to install install project just now:

Building the projects in this solution one at a time. To enable parallel build, please add the "/m" switch.
MSBUILD : error MSB3428: Could not load the Visual C++ component "VCBuild.exe". To fix this, 1) install the .NET Framework 2.0 SDK, 2) install Microsoft Visual Studio 2005 or 3) add the location of the component to
the system path if it is installed elsewhere. [C:\Users\Adam\AppData\Roaming\npm\node_modules\gulp-devtools\node_modules\socket.io\node_modules\socket.io-client\node_modules\ws\build\binding.sln]
MSBUILD : error MSB3428: Could not load the Visual C++ component "VCBuild.exe". To fix this, 1) install the .NET Framework 2.0 SDK, 2) install Microsoft Visual Studio 2005 or 3) add the location of the component to
the system path if it is installed elsewhere. [C:\Users\Adam\AppData\Roaming\npm\node_modules\gulp-devtools\node_modules\socket.io\node_modules\socket.io-client\node_modules\ws\build\binding.sln]

Install instructions unclear.

I'm new to gulp, and I do not understand where in my gulpfile.js I'm supposed to add module.exports = gulp; Can I get a better instruction on where this should be added?

I do not have a "var modules" declaration anywhere in my gulpfile.

Would be good if UI accepts command line arguments

Our build system accepts bunch of command line arguments. would be good if UI picks these command line options so that i don;t have wrap all these in another task. just a nice to have feature.

our system is some thing gulp deploy --partner= --locale=US_en,CH_tz types.

Adding parameters to task

Just I run:

gulp connect --env mock

But, It only allows to execute task without parameters