-
Notifications
You must be signed in to change notification settings - Fork 653
Open
Description
Summary
When the output folder contains a symbolic link, Rush throws an error.
Details
I think this is a good default behavior in most cases, since it helps prevent people from making mistakes.
However, in some cases the symbolic link is a relative path that points to another file within the same repo. Would it make sense to make the symbolic-link check (code linked below) more precise, so that it ignores cases where the relative target resolves to a path inside the repo?
| if (child.isSymbolicLink()) { |
Standard questions
Please answer these questions to help us investigate your issue more quickly:
| Question | Answer |
|---|---|
@microsoft/rush globally installed version? |
- |
rushVersion from rush.json? |
- |
useWorkspaces from rush.json? |
No |
| Operating system? | All |
| Would you consider contributing a PR? | Yes |
Node.js version (node -v)? |
- |
Metadata
Metadata
Assignees
Labels
No labels
Type
Projects
Status
Needs triage
