gulpfile relative paths about gulp-util

[yocontra]

The cwd will always be the gulpfile directory when using the CLI https://github.com/wearefractal/gulp/blob/master/bin/gulp.js#L93

It's semi-reliable to just use process.cwd() assuming they didn't run it with node.

[sindresorhus]

Doesn't that defeats its purpose if it can't be run with node?

[yocontra]

@sindresorhus If you are relying on cwd (using relative paths) you have a few options

• Use the gulp CLI
• Use node from the same dir as your gulpfile
• Add process.chdir(__dirname) to the top of your gulpfile

[sindresorhus]

k, but should at least be documented as it can cause obscure errors if you're not aware.

[sindresorhus]

the behaviour of process.cwd() should also be documented as a way to get gulpfile relative paths.

[yocontra]

@sindresorhus Your plugin shouldnt need to get the gulpfile path - you can just require() whatever path they pass in since they are ultimately in charge of relativity (using one of the 3 methods above). If they don't use any of the 3 methods above then they need to pass in the full path to their config file themselves since they aren't using relativity anyways

[sindresorhus]

@contra hm, you might be right. the thing is that the file should be somewhere relative to the gulpfile so thought it would make sense to make it relative by default for ease of use.

[yocontra]

@sindresorhus For gulp-jshint I support them passing in an object for settings, them require()ing their conf file and passing it in (handled same as the first way), or them passing a full path string and the plugin requires it in

[sindresorhus]

@contra good point: jscs-dev/gulp-jscs@9bd1fc5

[yocontra]

@sindresorhus Do you think this needs further discussion/consideration or does letting the user handle relativity sound good to you?

[sindresorhus]

Works for me, but needs docs as mentioned.