Empty object being returned

[RileySpiller]

I'm getting {} returned by running...

var gulp = require('gulp');
var plugins = require('gulp-load-plugins')({lazy: false});
console.log(JSON.stringify(plugins));

I set lazy: false after reading this issue #58

And I my package.json is packed full of plugins, many with or without 'gulp-' prefix.

Any help appreciated.

[MarkAPhillips]

console.log(JSON.stringify(plugins));

I think does not return all the plugins as ran into this issue myself and only one was returned to the console and wondered why they were not all being loaded. Not sure what this should return but you would expect all plugins to be shown if lazy is false

I would suggest you run a few plugins to see if they work as expected, if you haven't already.

My config at the moment is as follows and works like a dream:

var path = require('path');
var gulpLoadPlugins = require('gulp-load-plugins');
var gulp = require('gulp');

var pluginOpts = {
        config: path.join(__dirname,'package.json'),
        replaceString: /^gulp(-|\.)/,
        scope: ['devDependencies'],
        lazy: false
};

var plugins = gulpLoadPlugins(pluginOpts);

[jackfranklin]

Not sure what this should return but you would expect all plugins to be shown if lazy is false

Yeah, I would. Not sure what's going on there.

@RileySpiller did you get to the bottom of this?

[AutoSponge]

👍 same issue

[callumacrae]

@AutoSponge Do you definitely have lazy set to false?

[AutoSponge]

Yes. I've tried multiple versions of node, throwing tasks inside nextTick, etc. Nothing seems to work yet.

package:

{
  "devDependencies": {
    "gulp": "^3.8.11",
    "gulp-load-plugins": "^0.10.0",
    "gulp-sass": "^2.0.1",
  }
}

var gulp = require('gulp);
var plugins = require('gulp-load-plugins')({
  pattern: ['gulp-*', 'gulp.*'], // the glob(s) to search for
  config: './package.json', // where to find the plugins, by default  searched up from process.cwd()
  scope: ['devDependencies'], // which keys in the config to look within
  replaceString: /^gulp(-|\.)/, // what to remove from the name of the module when adding it to the context
  camelize: true, // if true, transforms hyphenated plugins names to camel case
  lazy: false, // whether the plugins should be lazy loaded on demand
  rename: {} // a mapping of plugins to rename
});

gulp.task('sass', function () {
  gulp.src('./app/**/*.scss')
    .pipe(plugins.sass().on('error', plugins.sass.logError))
    .pipe(gulp.dest('./css'));
});

yields:

[11:47:38] Using gulpfile ~/github/.../gulpfile.js
[11:47:38] Starting 'sass'...
[11:47:38] 'sass' errored after 5.02 ms
[11:47:38] TypeError: undefined is not a function

if I add plugins.sass = require('gulp-sass'); above it, it works.

[callumacrae]

If you clone this repo locally, do the tests pass for you?

[callumacrae]

Hang on, the error indicates that plugins.sass is defined, otherwise it would say "cannot read property of undefined".

What happens if you run console.log(plugins)?

[AutoSponge]

empty object. If I do console.log(Object.keys(plugins)) empty array. It's the same issue as described above.

[jackfranklin]

What does plugins.sass.toString() log?

[AutoSponge]

TypeError: Cannot read property 'toString' of undefined

[AutoSponge]

I tried cloning master--same issue. I down-revved as far as 0.7.1 and it's still happening. I don't want to call it quits but I can probably write a utility using fs.readSync instead of banging my head against it.

BTW, thanks for being so responsive.

[AutoSponge]

Possible hint: I removed all of the config except lazy: true and that worked!

Something else in the config object I posted earlier must be messing with plugin names. So, I added a console.log:

    } else {
      console.log(requireName, name);
      object[requireName] = requireFn(name);
    }

With the original config, it never reaches this... it's not getting any plugins.

[callumacrae]

Hang on, are you using lazy: true now? Originally you were using lazy: false

[jackfranklin]

@AutoSponge are you able to recreate this issue in a repo you could push to GitHub for me to take a look at?

[AutoSponge]

@callumacrae I'm using plugins = require('gulp-load-plugins')({lazy: false}); The issue went away when I removed the other config options and just passed the lazy value. I think there's another option silently erroring out.

@jackfranklin I'll try to make a gist or something tonight.

[jackfranklin]

@AutoSponge sounds like another config is causing issues. If you could give me something that I can replicate I'll happily debug. Sorry you're having problems and thanks for being responsive!

[AutoSponge]

I think it was caused by the relative path./package.json.

Removing the ./ or using the smarter config: path.join(__dirname, 'package.json'), should fix this for others.

var gulp = require('gulp');
var path = require('path');
var plugins = require('gulp-load-plugins')({
    config: path.join(__dirname, 'package.json'),
    lazy: false
});

[jackfranklin]

@AutoSponge ahh OK. That's interesting, would be nice to show a different error rather than just silently failing weird. I'll see if I can get something going.

[jfairley]

What @AutoSponge discovered is similar to #76

[pushkin-]

I have a similar problem as above, but adding the config parameter doesn't solve it.

var gulp = require('gulp');
var path = require('path');
var plugins = require('gulp-load-plugins')({
    config: path.join(__dirname, 'package.json'),
    lazy: false
});

Printing this gives me:

{
  "util": {
      "colors": {
          "enabled": true,
          "styles": {
              "reset": {
                  "open": "\u001b[0m",
                  "close": "\u001b[0m",
                  "closeRe": {}
              },
              "bold": {
                  "open": "\u001b[1m",
                  "close": "\u001b[22m",
                  "closeRe": {}
              },
...

"util" is the only thing there. Has anyone had this issue?

util seems to refer to gulp-util. It seems to default to removing the gulp prefix even if I'm not using the parameter replaceString (is this a bug?).

[TNT-Likely]

i have a problem as same as @AutoSponge

how do you slove?

[jackfranklin]

@pushkin-

It seems to default to removing the gulp prefix even if I'm not using the parameter replaceString (is this a bug?).

Nope, the default behaviour removes gulp- and gulp. from package names.

Presumably it doesn't work if you remove the config param either?

@TNT-Likely we're not sure yet, haven't been able to lock down exactly what's going wrong.

@pushkin- @TNT-Likely if either of you can push a repo that replicates this then I'm happy to dig into it 👍

[TNT-Likely]

i reslove it ,when i use version 0.10.0,it work,it seems the lastest vesion have some problems.
@jackfranklin

[pushkin-]

@jackfranklin Correct. It doesn't work without the config parameter.

[jackfranklin]

If anyone could run this against v1.1.0 with DEBUG: true set, the output from that might shed some light?

[jackfranklin]

@RileySpiller did you get anywhere with this?

Going to close this shortly given it's not had an update really since August. If anyone is hitting this though please let me know - and a repository that replicates the issue I can clone would be awesome too. I'm happy to reopen it.

[samhh]

I gave up on the plugin upon encountering this issue months ago. I'd be happy to give it another go and pass you the repo if the issue reoccurs. Hopefully will get that to you later today.

[samhh]

Turns out that I can no longer recreate this issue. That's a good thing, I think.

[jackfranklin]

@samhh that's good news! I still don't know what caused it, which is frustrating, but perhaps it was a random edge case a recent release fixed.