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
{{ message }}
This repository has been archived by the owner on Mar 30, 2023. It is now read-only.
ZCPKG_PATH_LENGTH_BUDGET is currently dead, mainly because I wasn't sure how to use it.
I think it makes sense for use in a report where you:
Assume a given workspace directory
Find the longest path in the workspace
Subtract the length of the longest path from the path budget.
So if you say a workspace sits in a Windows C:\Users\John\Code directory, you can estimate if a workspace will create a path that exceeds Windows' default max path length (which is pretty short, and causes issues like microsoft/nodejstools#69).
I hesitate to implement this because it could just as easily be a package written for zcpkg. I'm partial to keeping it lean, but the only defense for putting in this feature is that zcpkg does make this problem possible.
The text was updated successfully, but these errors were encountered:
ZCPKG_PATH_LENGTH_BUDGET
is currently dead, mainly because I wasn't sure how to use it.I think it makes sense for use in a report where you:
So if you say a workspace sits in a Windows
C:\Users\John\Code
directory, you can estimate if a workspace will create a path that exceeds Windows' default max path length (which is pretty short, and causes issues like microsoft/nodejstools#69).I hesitate to implement this because it could just as easily be a package written for
zcpkg
. I'm partial to keeping it lean, but the only defense for putting in this feature is thatzcpkg
does make this problem possible.The text was updated successfully, but these errors were encountered: