del is an alias for a native Windows command about del HOT 10 CLOSED

"scripts": {
    "clean": "node_modules/.bin/del dist/*"
}

from del.

@kevva That doesn't work. "node_modules/.bin/del" doesn't exist on a local del install.

from del.

On a local install it should definitely exist. On a global install it doesn't though.

nvm, this doesn't have a CLI so no wonder it doesn't work for you. Use trash if you need CLI functionality. This module only works when required as seen in the usage instructions.

from del.

@kevva I just created a new module. Ran:

npm install del

There is no node_modules/.bin/del directory! There is a node_modules\del\node_modules\.bin directory which, ironically, has rimraf in it.

from del.

As a matter of fact, it looks like even a global install of del (on Windows) doesn't attempt to alias del! Not sure why this issue was closed so quick.

_global rimraf install:_

PS C:\Users\e1031513\dev\projects\temp> npm install -g rimraf
C:\Users\e1031513\AppData\Roaming\npm\rimraf -> C:\Users\e1031513\AppData\Roaming\npm\node_modules\rimraf\bin.js
[email protected] C:\Users\e1031513\AppData\Roaming\npm\node_modules\rimraf
└── [email protected] ([email protected], [email protected], [email protected], [email protected])

_global del install:_

PS C:\Users\e1031513\dev\projects\temp> npm install -g del
[email protected] C:\Users\e1031513\AppData\Roaming\npm\node_modules\del
├── [email protected]
├── [email protected]
├── [email protected] ([email protected], [email protected])
├── [email protected] ([email protected])
├── [email protected] ([email protected])
└── [email protected] ([email protected], [email protected], [email protected])

from del.

There is no node_modules/.bin/del directory!

Because it doesn't have a CLI.

As a matter of fact, it looks like even a global install of del (on Windows) doesn't attempt to alias del!

Why would it?

from del.

I don't really care that much about the lack of a global install (although rimraf does support one and this module appears to be a superset improvement of rimraf). What I originally wanted to do was just simply use this in a simple npm "clean" script task. I was previously using rm -rf in the task, but that's doesn't have cross platform support without something like cygwin or winbash or something.

Not a huge deal, just inconvenient.

from del.

Yeah, that's what trash is for. Your code would look like this instead:

"scripts": {
    "clean": "trash dist/*"
}

from del.

trash is great, but the files I'm working with are inherently volatile (they are derived files from a build). I would never want to recover these, because they are all derived from a build; hence "putting them in the trash" is simply a waste of disk space in my scenario.

from del.

Yeah, then rimraf is the way to go.

from del.