We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Due to the npm bug, wrong version of glob may be installed. For example, if add glob 7 in devDependencies, it will cause ENOTDIR invalid cwd error.
ENOTDIR invalid cwd
It's better to warn exceptions friendly in following codes. Or users will be confused for some error like TypeError: Invalid Version: undefined.
TypeError: Invalid Version: undefined
var modulePath, modulePackage; try { var delim = (process.platform === 'win32' ? ';' : ':'), paths = (process.env.NODE_PATH ? process.env.NODE_PATH.split(delim) : []); modulePath = resolve.sync(this.moduleName, {basedir: configBase || cwd, paths: paths}); modulePackage = silentRequire(fileSearch('package.json', [modulePath])); } catch (e) {}
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Due to the npm bug, wrong version of glob may be installed. For example, if add glob 7 in devDependencies, it will cause
ENOTDIR invalid cwd
error.It's better to warn exceptions friendly in following codes. Or users will be confused for some error like
TypeError: Invalid Version: undefined
.The text was updated successfully, but these errors were encountered: