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

Our agent couldn't find any inactive projects. #10

Open
amcc opened this issue Aug 7, 2019 · 4 comments
Open

Our agent couldn't find any inactive projects. #10

amcc opened this issue Aug 7, 2019 · 4 comments

Comments

@amcc
Copy link

amcc commented Aug 7, 2019

i'm frequently getting the message 'Our agent couldn't find any inactive projects.' on a folder containing many node projects and node_modules directories.

I'm not sure whats causing the error, however if i drill down into a specific folder containing a node_modules folder within my code directory it will find it. If I look at a folder that may contain for instance a node project folder as well as a wordpress folder and other it might come up with the above message.

I understand if the project isn't active right now, but perhaps someone has the same issue and can suggest a solution

@bntzio
Copy link
Owner

bntzio commented Aug 19, 2019

Hi @amcc, so no node_modules are getting removed?

Could you try running wipe-modules with the --dry flag to see what it finds?

wipe-modules ~/code 20 --dry

@amcc
Copy link
Author

amcc commented Aug 19, 2019

just ran this on a folder that contained 2 subfolders, one had a node module folder within it. The other had 2 more subfolders, one with 2 more folders each with a node modules folder, the other itself contained a node-modules folder.

so the structure looked like

  • parent
    • react-twitter-apps
      • funador
        • react-auth-client (containes node-modules)
        • react-auth-server (contains node-modules)
      • react-twitter (contains node-modules)
    • twitter (contains node-modules)

So thats 4 node-modules folders total.

this is the output of the command:

 Our agent is examining your files... Hold on a sec. 

 The node_modules in the following directories can be wiped out: 

 twitter 

 1 node_modules were found! 

@bntzio
Copy link
Owner

bntzio commented Aug 19, 2019

Oh yeah, right now, the agent only looks and can remove node_modules at one-level depth, so the modules inside react-twitter-apps/funador and react-twitter-apps/react-twitter won't be detected, only the twitter one.

At the moment, wipe-modules isn't very active in terms of development but I'm seriously planning to make a v2 of this with lots of features in mind, one of those features is to support nested projects as well as monorepos, among other cool stuff (rewritten in typescript or python).

What do you think?

@amcc
Copy link
Author

amcc commented Aug 20, 2019

As soon as I posted that I figured out that it was a depth thing. That list painted a picture I couldn't figure out originally!

Mining down into folders would be so handy. I put projects into folders to tidy things up.

That single feature would do it for me. It's a fantastic thing other than that. A big issue for me is time machine and Google drive (also Dropbox etc) hating those folders

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

No branches or pull requests

2 participants