You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When run, this command will retrieve the latest release matching the provided descriptor, assign it to the project's package.json file, and automatically perform an install.
package.json location
There is no description of how the command navigates the directory hierarchy to locate a possible existing package.json to modify.
Using the test example of @arcanis in #607 (comment) shows that it operates on the root of a hierarchy:
Issue
Under README >
corepack use
the complete description currently says:package.json
locationThere is no description of how the command navigates the directory hierarchy to locate a possible existing package.json to modify.
Using the test example of @arcanis in #607 (comment) shows that it operates on the root of a hierarchy:
In this example case, the result is that:
packages/foo/package.json
contains{}
package.json
containspackage.json
creationIf no
package.json
file is found, then one is created. This effect of the command is not described.Suggestion
For the README >
corepack use
section:package.json
file is determined.package.json
file and / or apackageManager
field is created if they don't exist.Related
corepack use
in monorepo targets root not project package.json #607The text was updated successfully, but these errors were encountered: