14 breaking releases

0.40.0 Nov 16, 2021
0.38.0 Oct 5, 2021
0.34.0 Jul 13, 2021
0.29.0 Mar 30, 2021
Download history 304/week @ 2021-08-11 340/week @ 2021-08-18 574/week @ 2021-08-25 289/week @ 2021-09-01 434/week @ 2021-09-08 740/week @ 2021-09-15 388/week @ 2021-09-22 388/week @ 2021-09-29 576/week @ 2021-10-06 374/week @ 2021-10-13 313/week @ 2021-10-20 537/week @ 2021-10-27 317/week @ 2021-11-03 351/week @ 2021-11-10 622/week @ 2021-11-17 374/week @ 2021-11-24

1,733 downloads per month
Used in 4 crates

MIT license

7.5K SLoC


Nu-engine handles most of the core logic of nushell. For example, engine handles: - Passing of data between commands - Evaluating a commands return values - Loading of user configurations

Top level introduction

The following topics shall give the reader a top level understanding how various topics are handled in nushell.

How are environment variables handled?

Environment variables (or short envs) are stored in the Scope of the EvaluationContext. That means that environment variables are scoped by default and we don't use std::env to store envs (but make exceptions where convenient).

Nushell handles environment variables and their lifetime the following:

  • At startup all existing environment variables are read and put into Scope. (Nushell reads existing environment variables platform independent by asking the Host. They will most likely come from std::env::*)
  • Envs can also be loaded from config files. Each loaded config produces a new ScopeFrame with the envs of the loaded config.
  • Nu-Script files and internal commands read and write env variables from / to the Scope. External scripts and binaries can't interact with the Scope. Therefore all env variables are read from the Scope and put into the external binaries environment-variables-memory area.


~404K SLoC