Move path utilities to separate package #294
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
(New version of the paths part of #179)
Move the very basic path helpers to a new package
@ws-tools/paths. This helps prepare for splitting other packages, including git utilities.The main reason for splitting this package (rather than just using
exportswith various entry points) is to avoid the extra dependencies such as URL and workspace parsing where they're not actually needed.For now,
findProjectRootis staying inworkspace-toolssince it usesgetWorkspaceRoot, which then usesgetWorkspaceManagerAndRoot. The workspace manager/root logic was recently moved to separate files and could almost be pulled out, but...isCachingEnabledhelper I recently added (to support a beachball change which isn't checked in yet). This logic certainly doesn't belong in "paths" and is not clear where it should go (or if it should be replaced with an environment variable)...