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
For `@nodewell/path to be more usable, multiple config file name and extensions should be added.
Add support for the following:
.pathrc.json
.pathsrc.json
.pathrc.json5
.pathsrc.json5
Also these files can contain JavaScript, JSON, and JSON5 (the content will be automatically detected):
.pathrc
.pathsrc
Also add a CLI option for custom config files, e.g.: npx @nodewell/path -- --config=paths.js
npx @nodewell/path -- --config=paths.js
The text was updated successfully, but these errors were encountered:
richrdkng
No branches or pull requests
🚀 Description
For `@nodewell/path to be more usable, multiple config file name and extensions should be added.
💡 Solution
Add support for the following:
.pathrc.json
.pathsrc.json
.pathrc.json5
.pathsrc.json5
Also these files can contain JavaScript, JSON, and JSON5 (the content will be automatically detected):
.pathrc
.pathsrc
Also add a CLI option for custom config files, e.g.:
npx @nodewell/path -- --config=paths.js
The text was updated successfully, but these errors were encountered: