Add ability to run the last command quickly about runrun-cli HOT 5 CLOSED

On the other hand if you want to press up to get to runrun again, it will be annoying that it's not in the user history.
So I guess implementing your own history inside runrun sounds like the best solution to me.

from runrun-cli.

Can you share a flow of events where this is useful?
As it takes time to find a command in history, perhaps it's just as easy to run runrun to execute what you want.

One thing I can think of is running an npm script with extra arguments (not yet supported).
That would be useful in command history.

@elektronik2k5 mentioned npm-quick-run, which has a way to run scripts with few characters, but the interactive mode won't add to command history either (I think).

from runrun-cli.

After using runrun for a while, I've started experiencing what you were talking about...
Running a script like lint:eslint through runrun and then wanting to run it again by pressing the Up arrow key.

So... if it's possible, should definitely push the command to the command line history.

Note to self:
ntl has some solutions without touching the history:
https://github.com/ruyadorno/ntl#arrows_counterclockwise-repeat-the-last-ran-task

from runrun-cli.

@zoharyzgiaev Let's move forward with this...

Similar to this package:
https://github.com/ruyadorno/lru-cache-fs/blob/master/index.js

We don't need lru-cache, let's just save files with latest used script name.
For each CWD we'll have a file with just a string (e.g. 'lint-eslint').

Let's add fs-extra and make sure to use env-paths.

Also we now have an rr alias for runrun so the last run should be with rrr.
This is set in package.json under bin.

from runrun-cli.

@adamkleingit Good news, it's live! 😎.
Done in #13

Read the v1.2.0 Release Notes
Would appreciate feedback.

from runrun-cli.