-
-
Notifications
You must be signed in to change notification settings - Fork 4.7k
resolveConfig(cwd) fails to find config file #15879
Copy link
Copy link
Closed
Labels
help wantedWe're a small group who can't get to every issue promptly. We’d appreciate help fixing this issue!We're a small group who can't get to every issue promptly. We’d appreciate help fixing this issue!locked-due-to-inactivityPlease open a new issue and fill out the template instead of commenting.Please open a new issue and fill out the template instead of commenting.type:docsIssues about adding or improving documentationIssues about adding or improving documentation
Metadata
Metadata
Assignees
Labels
help wantedWe're a small group who can't get to every issue promptly. We’d appreciate help fixing this issue!We're a small group who can't get to every issue promptly. We’d appreciate help fixing this issue!locked-due-to-inactivityPlease open a new issue and fill out the template instead of commenting.Please open a new issue and fill out the template instead of commenting.type:docsIssues about adding or improving documentationIssues about adding or improving documentation
Environments:
Steps to reproduce:
node ./test.jsExpected behavior:
The script prints the parsed contents of the
.prettierrcinside that directory, sincecwdis an explicitly supported input parameter (see https://prettier.io/docs/en/api.html#prettierresolveconfigfileurlorpath--options)Actual behavior:
The script prints
null.Notes:
package.jsonfollowed by runningnpm install.node ./test.jswill print the expected outputdirname(cwd)instead ofcwd, thus never testing for the existence of.prettierrcin the project directory.