search

nickdodd79 / vscode-gulptasks

A gulp task visualization and execution extension for Visual Studio Code
MIT License
8 stars 6 forks source link

Skip when node_modules not found #29

Open garrettw opened 5 years ago

garrettw commented 5 years ago

It seems that finding all tasks in a project fails when the extension finds a gulpfile without a corresponding set of installed node_modules. Instead of failing out completely, could that particular gulpfile just be skipped, perhaps with a notice in the extension's output pane?

nickdodd79 commented 5 years ago

Hi @garrettw

Are you using workspaces in vscode?

If so, there is a known issue with the extension resolving gulp multiple times (per workspace project). I started a solution, but haven't got around to completing it. I am hoping to shortly so will let you when it is done.

If not, can you provide some more info around your project structure.

Thanks, Nick.

garrettw commented 5 years ago

I am using workspaces. When I submitted this issue, I was working on a Drupal 7 project where I have a custom module and a custom theme, both of which have their own gulpfiles (rather than one at the root). I was making changes to the theme, and I had already run yarn install in that directory, but I hadn't in the module's directory -- and according to the output pane, the module was where this extension was getting hung up. So I went and ran yarn install in that directory and refreshed the Gulp Tasks pane, and it worked just fine.