forked from extern/nushell
related to - https://github.com/nushell/nushell/issues/11041 - https://github.com/nushell/nu_scripts/pull/674 cc/ @FMotalleb # Description reading the [frontpage of the standard library](https://github.com/nushell/nushell/blob/main/crates/nu-std/README.md#--welcome-to-the-standard-library-of-nushell--) and according to the last Nushell meeting, i has been agreed that `std clip` does not belong to the standard library 😮 - it is not written in pure Nushell and requires external dependencies which might not even work properly as in https://github.com/nushell/nushell/issues/11041 - it is not a building block to build more complex applications this PR deprecates the `std clip` command in favor of [`modules/system clip`](https://github.com/nushell/nu_scripts/pull/674) for now. the `std clip` command will be removed in Nushell 0.89. # User-Facing Changes the deprecation warning:  > **Note** > the link has been changed to the `nu_scripts` in fa6c17da0 according to the review comments # Tests + Formatting # After Submitting this will have to be mentionned in the next release note, namely the slight differences between the two commands.
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.