I usually have a "clean" script that deletes just the build artifacts. Hence the reasoning behind the name "destroy", as hopefully devs will know it applies to destroying all artifacts and dependencies.
Full stack software engineer with a flair for creating elegant solutions with the least amount of time.Exceptional problem solver with an aptitude for troubleshooting and the ability to quickly master
Instead of "destroy" you should use "clean" like in "make clean" ;) Destroy sounds too harshful imho!
I usually have a "clean" script that deletes just the build artifacts. Hence the reasoning behind the name "destroy", as hopefully devs will know it applies to destroying all artifacts and dependencies.
then go with "cleanall", as destroy implies removing something that cannot be recuperated easily. My 2 cents ;)
Nice one! I was using a bash file for it but this looks better, thanks. :)
No worries, better to have it as a script in the package.json, then it's not dependant on the OS and it's also version controlled.
Except the script doesn't work on Windows.
it does. ive tested it
Yeah that's what I meant, bash is not working with win cli. I also updated:) Cheers
I like that! π₯
Thanks for sharing! I like this idea.
No worries, glad you found it useful.
Nice one π
No worries, glad you liked it.
I thought that in package.json, you don't need to put in npx.
This would only work if you had rimraf as a dependency or rimraf was installed globally.