[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"project-1287":3},{"id":4,"name":5,"fullName":6,"owner":5,"repo":5,"description":7,"homepage":8,"htmlUrl":9,"language":10,"languages":9,"totalLinesOfCode":9,"stars":11,"forks":12,"watchers":13,"openIssues":14,"contributorsCount":15,"subscribersCount":15,"size":15,"stars1d":16,"stars7d":17,"stars30d":18,"stars90d":15,"forks30d":15,"starsTrendScore":19,"compositeScore":20,"rankGlobal":9,"rankLanguage":9,"license":21,"archived":22,"fork":22,"defaultBranch":23,"hasWiki":22,"hasPages":22,"topics":24,"createdAt":9,"pushedAt":9,"updatedAt":27,"readmeContent":28,"aiSummary":29,"trendingCount":15,"starSnapshotCount":15,"syncStatus":30,"lastSyncTime":31,"discoverSource":32},1287,"nushell","nushell\u002Fnushell","A new type of shell","https:\u002F\u002Fwww.nushell.sh\u002F",null,"Rust",39711,2154,203,1410,0,3,62,287,24,45,"MIT License",false,"main",[5,25,26],"rust","shell","2026-06-12 02:00:25","# Nushell \u003C!-- omit in toc -->\n[![Crates.io](https:\u002F\u002Fimg.shields.io\u002Fcrates\u002Fv\u002Fnu.svg)](https:\u002F\u002Fcrates.io\u002Fcrates\u002Fnu)\n[![Build Status](https:\u002F\u002Fimg.shields.io\u002Fgithub\u002Factions\u002Fworkflow\u002Fstatus\u002Fnushell\u002Fnushell\u002Fci.yml?branch=main)](https:\u002F\u002Fgithub.com\u002Fnushell\u002Fnushell\u002Factions)\n[![Nightly Build](https:\u002F\u002Fgithub.com\u002Fnushell\u002Fnushell\u002Factions\u002Fworkflows\u002Fnightly-build.yml\u002Fbadge.svg)](https:\u002F\u002Fgithub.com\u002Fnushell\u002Fnushell\u002Factions\u002Fworkflows\u002Fnightly-build.yml)\n[![Discord](https:\u002F\u002Fimg.shields.io\u002Fdiscord\u002F601130461678272522.svg?logo=discord)](https:\u002F\u002Fdiscord.gg\u002FNtAbbGn)\n[![The Changelog #363](https:\u002F\u002Fimg.shields.io\u002Fbadge\u002FThe%20Changelog-%23363-61c192.svg)](https:\u002F\u002Fchangelog.com\u002Fpodcast\u002F363)\n[![GitHub commit activity](https:\u002F\u002Fimg.shields.io\u002Fgithub\u002Fcommit-activity\u002Fm\u002Fnushell\u002Fnushell)](https:\u002F\u002Fgithub.com\u002Fnushell\u002Fnushell\u002Fgraphs\u002Fcommit-activity)\n[![GitHub contributors](https:\u002F\u002Fimg.shields.io\u002Fgithub\u002Fcontributors\u002Fnushell\u002Fnushell)](https:\u002F\u002Fgithub.com\u002Fnushell\u002Fnushell\u002Fgraphs\u002Fcontributors)\n\nA new type of shell.\n\n![Example of nushell](assets\u002Fnushell-autocomplete6.gif \"Example of nushell\")\n\n## Table of Contents \u003C!-- omit in toc -->\n\n- [Status](#status)\n- [Learning About Nu](#learning-about-nu)\n- [Installation](#installation)\n- [Configuration](#configuration)\n- [Philosophy](#philosophy)\n  - [Pipelines](#pipelines)\n  - [Opening files](#opening-files)\n  - [Plugins](#plugins)\n- [Goals](#goals)\n- [Officially Supported By](#officially-supported-by)\n- [Contributing](#contributing)\n- [License](#license)\n\n## Status\n\nThis project has reached a minimum-viable-product level of quality. Many people use it as their daily driver, but it may be unstable for some commands. Nu's design is subject to change as it matures.\n\n## Learning About Nu\n\nThe [Nushell book](https:\u002F\u002Fwww.nushell.sh\u002Fbook\u002F) is the primary source of Nushell documentation. You can find [a full list of Nu commands in the book](https:\u002F\u002Fwww.nushell.sh\u002Fcommands\u002F), and we have many examples of using Nu in our [cookbook](https:\u002F\u002Fwww.nushell.sh\u002Fcookbook\u002F).\n\nWe're also active on [Discord](https:\u002F\u002Fdiscord.gg\u002FNtAbbGn); come and chat with us!\n\n## Installation\n\nTo quickly install Nu:\n\n```bash\n# Linux and macOS\nbrew install nushell\n# Windows\nwinget install nushell\n```\n\nTo use `Nu` in GitHub Action, check [setup-nu](https:\u002F\u002Fgithub.com\u002Fmarketplace\u002Factions\u002Fsetup-nu) for more detail.\n\nDetailed installation instructions can be found in the [installation chapter of the book](https:\u002F\u002Fwww.nushell.sh\u002Fbook\u002Finstallation.html). Nu is available via many package managers:\n\n[![Packaging status](https:\u002F\u002Frepology.org\u002Fbadge\u002Fvertical-allrepos\u002Fnushell.svg?columns=3)](https:\u002F\u002Frepology.org\u002Fproject\u002Fnushell\u002Fversions)\n\nFor details about which platforms the Nushell team actively supports, see [our platform support policy](devdocs\u002FPLATFORM_SUPPORT.md).\n\n## Configuration\n\nThe default configurations can be found at [sample_config](crates\u002Fnu-utils\u002Fsrc\u002Fdefault_files)\nwhich are the configuration files one gets when they startup Nushell for the first time.\n\nIt sets all of the default configuration to run Nushell.  From here one can\nthen customize this file for their specific needs.\n\nTo see where *config.nu* is located on your system simply type this command.\n\n```rust\n$nu.config-path\n```\n\nPlease see our [book](https:\u002F\u002Fwww.nushell.sh) for all of the Nushell documentation.\n\n\n## Philosophy\n\nNu draws inspiration from projects like PowerShell, functional programming languages, and modern CLI tools.\nRather than thinking of files and data as raw streams of text, Nu looks at each input as something with structure.\nFor example, when you list the contents of a directory what you get back is a table of rows, where each row represents an item in that directory.\nThese values can be piped through a series of steps, in a series of commands called a 'pipeline'.\n\n### Pipelines\n\nIn Unix, it's common to pipe between commands to split up a sophisticated command over multiple steps.\nNu takes this a step further and builds heavily on the idea of _pipelines_.\nAs in the Unix philosophy, Nu allows commands to output to stdout and read from stdin.\nAdditionally, commands can output structured data (you can think of this as a third kind of stream).\nCommands that work in the pipeline fit into one of three categories:\n\n-   Commands that produce a stream (e.g., `ls`)\n-   Commands that filter a stream (e.g., `where type == \"dir\"`)\n-   Commands that consume the output of the pipeline (e.g., `table`)\n\nCommands are separated by the pipe symbol (`|`) to denote a pipeline flowing left to right.\n\n```shell\nls | where type == \"dir\" | table\n# => ╭────┬──────────┬──────┬─────────┬───────────────╮\n# => │ #  │   name   │ type │  size   │   modified    │\n# => ├────┼──────────┼──────┼─────────┼───────────────┤\n# => │  0 │ .cargo   │ dir  │     0 B │ 9 minutes ago │\n# => │  1 │ assets   │ dir  │     0 B │ 2 weeks ago   │\n# => │  2 │ crates   │ dir  │ 4.0 KiB │ 2 weeks ago   │\n# => │  3 │ docker   │ dir  │     0 B │ 2 weeks ago   │\n# => │  4 │ docs     │ dir  │     0 B │ 2 weeks ago   │\n# => │  5 │ images   │ dir  │     0 B │ 2 weeks ago   │\n# => │  6 │ pkg_mgrs │ dir  │     0 B │ 2 weeks ago   │\n# => │  7 │ samples  │ dir  │     0 B │ 2 weeks ago   │\n# => │  8 │ src      │ dir  │ 4.0 KiB │ 2 weeks ago   │\n# => │  9 │ target   │ dir  │     0 B │ a day ago     │\n# => │ 10 │ tests    │ dir  │ 4.0 KiB │ 2 weeks ago   │\n# => │ 11 │ wix      │ dir  │     0 B │ 2 weeks ago   │\n# => ╰────┴──────────┴──────┴─────────┴───────────────╯\n```\n\nBecause most of the time you'll want to see the output of a pipeline, `table` is assumed.\nWe could have also written the above:\n\n```shell\nls | where type == \"dir\"\n```\n\nBeing able to use the same commands and compose them differently is an important philosophy in Nu.\nFor example, we could use the built-in `ps` command to get a list of the running processes, using the same `where` as above.\n\n```shell\nps | where cpu > 0\n# => ╭───┬───────┬───────────┬───────┬───────────┬───────────╮\n# => │ # │  pid  │   name    │  cpu  │    mem    │  virtual  │\n# => ├───┼───────┼───────────┼───────┼───────────┼───────────┤\n# => │ 0 │  2240 │ Slack.exe │ 16.40 │ 178.3 MiB │ 232.6 MiB │\n# => │ 1 │ 16948 │ Slack.exe │ 16.32 │ 205.0 MiB │ 197.9 MiB │\n# => │ 2 │ 17700 │ nu.exe    │  3.77 │  26.1 MiB │   8.8 MiB │\n# => ╰───┴───────┴───────────┴───────┴───────────┴───────────╯\n```\n\n### Opening files\n\nNu can load file and URL contents as raw text or structured data (if it recognizes the format).\nFor example, you can load a .toml file as structured data and explore it:\n\n```shell\nopen Cargo.toml\n# => ╭──────────────────┬────────────────────╮\n# => │ bin              │ [table 1 row]      │\n# => │ dependencies     │ {record 25 fields} │\n# => │ dev-dependencies │ {record 8 fields}  │\n# => │ features         │ {record 10 fields} │\n# => │ package          │ {record 13 fields} │\n# => │ patch            │ {record 1 field}   │\n# => │ profile          │ {record 3 fields}  │\n# => │ target           │ {record 3 fields}  │\n# => │ workspace        │ {record 1 field}   │\n# => ╰──────────────────┴────────────────────╯\n```\n\nWe can pipe this into a command that gets the contents of one of the columns:\n\n```shell\nopen Cargo.toml | get package\n# => ╭───────────────┬────────────────────────────────────╮\n# => │ authors       │ [list 1 item]                      │\n# => │ default-run   │ nu                                 │\n# => │ description   │ A new type of shell                │\n# => │ documentation │ https:\u002F\u002Fwww.nushell.sh\u002Fbook\u002F       │\n# => │ edition       │ 2018                               │\n# => │ exclude       │ [list 1 item]                      │\n# => │ homepage      │ https:\u002F\u002Fwww.nushell.sh             │\n# => │ license       │ MIT                                │\n# => │ metadata      │ {record 1 field}                   │\n# => │ name          │ nu                                 │\n# => │ repository    │ https:\u002F\u002Fgithub.com\u002Fnushell\u002Fnushell │\n# => │ rust-version  │ 1.60                               │\n# => │ version       │ 0.72.0                             │\n# => ╰───────────────┴────────────────────────────────────╯\n```\n\nAnd if needed we can drill down further:\n\n```shell\nopen Cargo.toml | get package.version\n# => 0.72.0\n```\n\n### Plugins\n\nNu supports plugins that offer additional functionality to the shell and follow the same structured data model that built-in commands use. There are a few examples in the `crates\u002Fnu_plugins_*` directories.\n\nPlugins are binaries that are available in your path and follow a `nu_plugin_*` naming convention.\nThese binaries interact with nu via a simple JSON-RPC protocol where the command identifies itself and passes along its configuration, making it available for use.\nIf the plugin is a filter, data streams to it one element at a time, and it can stream data back in return via stdin\u002Fstdout.\nIf the plugin is a sink, it is given the full vector of final data and is given free reign over stdin\u002Fstdout to use as it pleases.\n\nThe [awesome-nu repo](https:\u002F\u002Fgithub.com\u002Fnushell\u002Fawesome-nu#plugins) lists a variety of nu-plugins while the [showcase repo](https:\u002F\u002Fgithub.com\u002Fnushell\u002Fshowcase) *shows* off informative blog posts that have been written about Nushell along with videos that highlight technical\ntopics that have been presented.\n\n## Goals\n\nNu adheres closely to a set of goals that make up its design philosophy. As features are added, they are checked against these goals.\n\n-   First and foremost, Nu is cross-platform. Commands and techniques should work across platforms and Nu has [first-class support for Windows, macOS, and Linux](devdocs\u002FPLATFORM_SUPPORT.md).\n\n-   Nu ensures compatibility with existing platform-specific executables.\n\n-   Nu's workflow and tools should have the usability expected of modern software in 2022 (and beyond).\n\n-   Nu views data as either structured or unstructured. It is a structured shell like PowerShell.\n\n-   Finally, Nu views data functionally. Rather than using mutation, pipelines act as a means to load, change, and save data without mutable state.\n\n## Officially Supported By\n\nPlease submit an issue or PR to be added to this list.\n\n-   [zoxide](https:\u002F\u002Fgithub.com\u002Fajeetdsouza\u002Fzoxide)\n-   [starship](https:\u002F\u002Fgithub.com\u002Fstarship\u002Fstarship)\n-   [oh-my-posh](https:\u002F\u002Fohmyposh.dev)\n-   [Couchbase Shell](https:\u002F\u002Fcouchbase.sh)\n-   [virtualenv](https:\u002F\u002Fgithub.com\u002Fpypa\u002Fvirtualenv)\n-   [atuin](https:\u002F\u002Fgithub.com\u002Fellie\u002Fatuin)\n-   [clap](https:\u002F\u002Fgithub.com\u002Fclap-rs\u002Fclap\u002Ftree\u002Fmaster\u002Fclap_complete_nushell)\n-   [Dorothy](http:\u002F\u002Fgithub.com\u002Fbevry\u002Fdorothy)\n-   [Direnv](https:\u002F\u002Fgithub.com\u002Fdirenv\u002Fdirenv\u002Fblob\u002Fmaster\u002Fdocs\u002Fhook.md#nushell)\n-   [x-cmd](https:\u002F\u002Fx-cmd.com\u002Fmod\u002Fnu)\n-   [vfox](https:\u002F\u002Fgithub.com\u002Fversion-fox\u002Fvfox)\n-   [Windmill](https:\u002F\u002Fwww.windmill.dev\u002Fdocs\u002Fgetting_started\u002Fscripts_quickstart\u002Fbash)\n\n## Contributing\n\nSee [Contributing](CONTRIBUTING.md) for details. Thanks to all the people who already contributed!\n\n\u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fnushell\u002Fnushell\u002Fgraphs\u002Fcontributors\">\n  \u003Cimg src=\"https:\u002F\u002Fcontributors-img.web.app\u002Fimage?repo=nushell\u002Fnushell&max=750&columns=20\" \u002F>\n\u003C\u002Fa>\n\n## License\n\nThe project is made available under the MIT license. See the `LICENSE` file for more information.\n","Nushell 是一种新型的命令行 shell。它使用 Rust 语言编写，具有结构化数据处理能力，支持管道操作、文件打开和插件扩展等核心功能，旨在提供更加现代化且用户友好的交互体验。Nushell 适合需要高效处理文本数据、进行系统管理和自动化脚本编写的场景，特别适用于对传统 shell 不满意并寻求更强大工具的开发者。其设计哲学强调直观性和易用性，同时保持了高度的灵活性与可配置性。",2,"2026-06-11 02:42:49","top_all"]