Update resolve-from to the latest version 🚀

[greenkeeper]

The dependency resolve-from was updated from 4.0.0 to 5.0.0.

This version is not covered by your current version range.

If you don’t accept this pull request, your project will work just like it did before. However, you might be missing out on a bunch of new features, fixes and/or performance improvements from the dependency update.

---

Release Notes for v5.0.0

Breaking:

• Require Node.js 8 (#12) 188ed7d
• Return undefined instead of null when the module cannot be found (#12) 188ed7d

Enhancements:

• Add TypeScript definition (#12) 188ed7d

v4.0.0...v5.0.0

Commits

The new version differs by 2 commits.

• 53f4a1b 5.0.0
• 188ed7d Require Node.js 8, return undefined instead of null, add TypeScript definition (#12)

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper bot 🌴

[ybiquitous]

The resolve-from module is used in stylelint here: ⬇️

stylelint/lib/utils/getModulePath.js

Lines 15 to 29 in f77b140

	let path = resolveFrom.silent(basedir, lookup);
	if (!path) {
	path = resolveFrom.silent(process.cwd(), lookup);
	}
	if (!path) {
	path = resolveFrom.silent(globalModules, lookup);
	}
	if (!path) {
	throw configurationError(
	`Could not find "${lookup}". Do you need a \`configBasedir\`?`
	);
	}

stylelint/lib/cli.js

Lines 420 to 423 in f77b140

	optionsBase.configFile =
	resolveFrom.silent(process.cwd(), cli.flags.config) ||
	path.join(process.cwd(), cli.flags.config);
	}

[ybiquitous]

The resolve-from@5.0.0 major update has a breaking change that the silent function's return type changes from null to undefined, which it doesn't seem to affect stylelint's behavior.

https://github.com/sindresorhus/resolve-from/blob/53f4a1b40f972dbfc4dda9627d24068000eae897/index.js#L35-L41

[ybiquitous]

LGTM 👍