Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

npm install can sometimes fail when symlinks from a previous Stratos version exist #4513

Closed
nwmac opened this issue Aug 18, 2020 · 0 comments · Fixed by #4509
Closed

npm install can sometimes fail when symlinks from a previous Stratos version exist #4513

nwmac opened this issue Aug 18, 2020 · 0 comments · Fixed by #4509
Assignees
@nwmac
Labels
bug
Milestone
4.0.1

Comments

@nwmac
Copy link
Contributor

nwmac commented Aug 18, 2020

If you have Stratos cloned locally and update to the latest 4.X codebase, doing an npm install can fail if you have symlinks left over from the previous version.
@nwmac nwmac added the bug label Aug 18, 2020
@nwmac nwmac added this to the 4.0.1 milestone Aug 18, 2020
@nwmac nwmac self-assigned this Aug 18, 2020
@nwmac nwmac closed this as completed Aug 18, 2020
@nwmac nwmac mentioned this issue Aug 18, 2020
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@nwmac nwmac

Labels
bug
Projects
None yet
Milestone
4.0.1
Development

Successfully merging a pull request may close this issue.

Improve clean-symlinks script cloudfoundry/stratos
1 participant
@nwmac