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.

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

[node-modules] Avoids recreating nm folders and only clears them #1185

Merged
merged 8 commits into from
Apr 14, 2020

Conversation

larixer
Copy link
Member

@larixer larixer commented Apr 10, 2020

What's the problem this PR addresses?

This PR solves issue: #1184

How did you fix it?

The linker does not attempt removing node_modules folders if it is going to recreate them soon.

@larixer larixer changed the title [node-modules] Avoids recreating top-level nm folders and only clears them [node-modules] Avoids recreating nm folders and only clears them Apr 10, 2020
@larixer larixer added the in progress Features claimed by a contributor label Apr 10, 2020
@larixer larixer force-pushed the top-level-nm-folders-keeping branch from 8a019ac to 8a6ed8b Compare April 11, 2020 06:39
@larixer larixer removed the in progress Features claimed by a contributor label Apr 11, 2020
@larixer larixer requested a review from arcanis April 11, 2020 07:58
@arcanis
Copy link
Member

arcanis commented Apr 14, 2020

Looks fine! Can you just add a test, to make sure there are no regressions?

@larixer
Copy link
Member Author

larixer commented Apr 14, 2020

Yes, sure, will do and let you know

@larixer larixer force-pushed the top-level-nm-folders-keeping branch from c1bd0f5 to 6f17705 Compare April 14, 2020 14:03
@larixer
Copy link
Member Author

larixer commented Apr 14, 2020

@arcanis Regression test has been added

@arcanis arcanis merged commit a6f9e6d into master Apr 14, 2020
@arcanis arcanis deleted the top-level-nm-folders-keeping branch April 14, 2020 16:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants