Closed DanielGarciaGuillen closed 3 years ago
Thank you for the kind words!
I believe it fails because npm ci
considers a warning as a failure. Have you tried forking this package and adding --loglevel=error
? More info here.
Otherwise, I can give a test drive during this week - I just need to find a case where I have warnings. If it solves, I'll push a fix right after. Otherwise, I'll think of something else - there's always a solution for everything.
Ok, so what I'll do is remove those messages. The "Error running" messages are more warnings than anything else. I'll bump a version this week.
I appreciate! Thanks man!
First of all, thanks for this amazing package.
The amount of hours our team is saving is incredible thanks to your work.
I am working on our pipeline (Jenkins) and I would like to use the package to do the cleanup.
My apologies if the issue is actually not related to your package, but I am not sure why this is happening.
The issue I am facing is that it seems when I do npm run clean("clean": "react-native clean-project-auto" on package.json), the step on Jenkins doesn't result in success.
Do you have any idea why? It should log it as a success and move on to the next steps, but that is not the case.
It stays there for as much time as I let it be, without returning a success.
Thanks in advance!