forked from extern/nushell
6ed033737d
* Include license text in all crates Three crates already have license texts, so I'm keeping them, but symlinking the `LICENSE` from the top level to the rest of the crate directories. This works as long as `cargo publish` is done on a Unix-y system and not Windows. Also bump the copyright year to end in 2022. Signed-off-by: Michel Alexandre Salim <salimma@fedoraproject.org> * Replace symlinks Co-authored-by: sholderbach <sholderbach@users.noreply.github.com> |
||
---|---|---|
.. | ||
nu_plugin_example | ||
nu_plugin_gstat | ||
nu_plugin_inc | ||
nu_plugin_python | ||
nu_plugin_query | ||
nu-cli | ||
nu-color-config | ||
nu-command | ||
nu-engine | ||
nu-glob | ||
nu-json | ||
nu-parser | ||
nu-path | ||
nu-plugin | ||
nu-pretty-hex | ||
nu-protocol | ||
nu-system | ||
nu-table | ||
nu-term-grid | ||
nu-test-support | ||
nu-utils | ||
old | ||
README.md |
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 different capabilities like working with different file types, charting, viewing binary data, and more.