History

Stefan Holderbach d7ebe5fdc3 Update `nu-ansi-term`, `lscolors`, and `reedline` (#9787 ) # Description Now use `nu-ansi-term` 0.49 Small adjustments to accommodate breaking changes. # User-Facing Changes None		2023-07-24 13:16:18 +02:00
..
assets	REFACTOR: move the 0% commands to `nu-cmd-extra` (#9404 )	2023-07-06 08:31:31 -07:00
src	Use explicit in/out list types for vectorized commands (#9742 )	2023-07-23 20:46:53 +02:00
tests	Clean up tests containing unnecessary `cwd:` tokens (#9692 )	2023-07-17 18:43:51 +02:00
Cargo.toml	Update `nu-ansi-term`, `lscolors`, and `reedline` (#9787 )	2023-07-24 13:16:18 +02:00
LICENSE	nu-cmd-extra crate infrastructure in place with the Bits command as the model for adding other commands (#9327 )	2023-06-01 10:46:16 -07:00
README.md	add in a Readme for the crate nu-cmd-extra (#9745 )	2023-07-19 21:35:58 -07:00

README.md

nu-cmd-extra

the extra commands are not part of the Nushell binary

The commands in this crate are the extra commands of Nushell. They do not get built for the release and it is the responsibility of the developer to build these commands if they want to use them.

These commands are not going to part of the 1.0 Api; meaning that there is no guarantee longer term that these commands will be around into the future. Of course since they are part of the source tree one could always incorporate them into their own custom release.

How to build the commands in this crate

Step 1 is to read the installation notes for Nushell which is located in our Nushell book.

Once Rust is installed you can then build Nushell with the following command.

cargo build --features=extra

Your Nushell binary which just got built is called nu and will be located here.

nushell/target/debug/nu