Bruce Mitchener 651d425046
Remove ptree dep from nu-command, remove associated feature. (#3741)
Nothing used the `ptree` feature or optional dependency within
`nu-command` except to include it within the `version` output. This
may be related to when `nu-cli` also had a `ptree` feature, but
I'm not sure.

That leaves the code within `nu_plugin_tree` as the sole remaining
user of `ptree`, which is already covered by the feature `tree`
and included in the `version` output.
2021-07-06 10:33:24 -05:00
..
2021-06-23 19:57:41 +12:00
2021-06-23 19:57:41 +12:00
2021-06-23 19:57:41 +12:00
2021-06-23 19:57:41 +12:00
2021-06-23 19:57:41 +12:00
2021-06-23 19:57:41 +12:00
2021-06-23 19:57:41 +12:00
2021-06-23 19:57:41 +12:00
2021-06-23 19:57:41 +12:00
2021-06-23 19:57:41 +12:00
2021-06-23 19:57:41 +12:00
2021-06-23 19:57:41 +12:00
2021-06-23 19:57:41 +12:00
2021-07-05 11:46:53 +12:00
2021-06-23 19:57:41 +12:00
2021-06-23 19:57:41 +12:00
2021-06-23 19:57:41 +12:00
2021-06-23 19:57:41 +12:00
2021-07-05 11:46:53 +12:00
2021-06-23 19:57:41 +12:00
2021-06-23 19:57:41 +12:00
2021-06-23 19:57:41 +12:00

Nushell core libraries and plugins

These sub-crates form both the foundation for Nu and a set of plugins which extend Nu with additional functionality.

Foundational libraries are split into two kinds of crates:

  • Core crates - those crates that work together to build the Nushell language engine
  • Support crates - a set of crates that support the engine with additional features like JSON support, ANSI support, and more.

Plugins are likewise also split into two types:

  • Core plugins - plugins that provide part of the default experience of Nu, including access to the system properties, processes, and web-connectivity features.
  • Extra plugins - these plugins run a wide range of differnt capabilities like working with different file types, charting, viewing binary data, and more.