---
title: Nushell 0.7.0
author: Sophia Turner
author_site: https://twitter.com/sophiajturner
author_image: https://www.nushell.sh/blog/images/sophiajt.jpg
excerpt: We're happy to announce the 0.7.0 release of Nu. This release has a couple new features, bugfixes, and lots of internal improvements on the way to upcoming features.
---
# Nushell 0.7.0
Nushell, or Nu for short, is a new shell that takes a modern, structured approach to your commandline. It works seamlessly with the data from your filesystem, operating system, and a growing number of file formats to make it easy to build powerful commandline pipelines.
We're happy to announce the 0.7.0 release of Nu. This release has a couple new features, bugfixes, and lots of internal improvements on the way to upcoming features.
# Where to get it
Nu 0.7.0 is available as [pre-built binaries](https://github.com/nushell/nushell/releases/tag/0.7.0) or from [crates.io](https://crates.io/crates/nu). If you have Rust installed you can install it using `cargo install nu` (or if you want all stable features `cargo install nu --features=stable`).
# Ranges (wycats, sebastian-xyz)
We've added ranges as new fundamental type in Nu. To use it, use `<number>..<number>`. Currently, you can use it with the new `range` command, which lets you do commands like:
```
ls | range 3..5
```
And return rows 3 through 5 of the table that `ls` gives you.
# Autocomplete improvements (sophiajt)
As we improve the parser, we are getting more opportunities to do more with the results. One feature we added recently is the ability to autocomplete flags for internal commands.
For example, if you want to see what's available for the `config` command, you can now type `config --` and then immediately use the `<tab>` key to cycle through possible options.
# Nu becomes multiple crates (wycats, sophiajt)
Part of a big effort to get Nu ready for script support is to refactor the current codebase to make it cleaner and easier to work with.
For the last few weeks, a big part of this refactor involved splitting our growing monolith of a codebase into separate sub-crates that work together to give the same functionality. As we've done so, we've been able to clean up some of the interfaces between the code. The end result is something that already is easier to work with, and we're excited about what this means for future development.
One side effect of this work is that we've now separated out the plugins from the main `nu` crate. This gives you more options to configure your Nu setup how you want, as each optional crate can be separately installed.
From cargo, you can install the main crate with:
```
cargo install nu
```
Then, you can install the plugins the same way. You can find them because they have a name starting with `nu_plugin_`. For example, to install the textview plugin:
```
cargo install nu_plugin_textview
```
The current set of plugins includes:
- nu_plugin_average
- nu_plugin_binaryview
- nu_plugin_fetch
- nu_plugin_inc
- nu_plugin_match
- nu_plugin_post
- nu_plugin_ps
- nu_plugin_str
- nu_plugin_sum
- nu_plugin_sys
- nu_plugin_textview
- nu_plugin_tree
By default, Nu will install a small set of these plugins ("sys", "ps", "textview", "inc", "str"). You can optionally turn this off using: