nushell/crates/nu-std/Cargo.toml

[package]
authors = ["The Nushell Project Developers"]
description = "The standard library of Nushell"
repository = "https://github.com/nushell/nushell/tree/main/crates/nu-std"
edition = "2021"
license = "MIT"
name = "nu-std"
version = "0.82.1"

[dependencies]
miette = { version = "5.9", features = ["fancy-no-backtrace"] }
nu-parser = { version = "0.82.1", path = "../nu-parser" }
nu-protocol = { version = "0.82.1", path = "../nu-protocol" }
nu-engine = { version = "0.82.1", path = "../nu-engine" }
stdlib: make the library a standalone crate (#8770) # Description as we now have a prelude thanks to #8627, i'd like to work on the structure of the library :yum: and i think the first step is to make it a true standalone crate :smirk: this PR - moves all the library from `crates/nu-utils/standard_library/` to `crates/nu-std/` - moves the `rust` loading code from `src/run.rs` to `crates/nu-std/src/lib.rs` 2023-04-07 22:12:27 +02:00			`[package]`
			`authors = ["The Nushell Project Developers"]`
			`description = "The standard library of Nushell"`
			`repository = "https://github.com/nushell/nushell/tree/main/crates/nu-std"`
			`edition = "2021"`
			`license = "MIT"`
			`name = "nu-std"`
Bump to `0.82.1` dev version (#9543) # Description Marks development or hotfix 2023-06-27 21:33:53 +02:00			`version = "0.82.1"`
stdlib: make the library a standalone crate (#8770) # Description as we now have a prelude thanks to #8627, i'd like to work on the structure of the library :yum: and i think the first step is to make it a true standalone crate :smirk: this PR - moves all the library from `crates/nu-utils/standard_library/` to `crates/nu-std/` - moves the `rust` loading code from `src/run.rs` to `crates/nu-std/src/lib.rs` 2023-04-07 22:12:27 +02:00
			`[dependencies]`
update most dependencies except where deeper code changes are needed (#9296) # Description This PR updates most dependencies and tries to get in sync with reedline. # User-Facing Changes <!-- List of all changes that impact the user experience here. This helps us keep track of breaking changes. --> # Tests + Formatting <!-- Don't forget to add tests that cover your changes. Make sure you've run and fixed any issues with these commands: - `cargo fmt --all -- --check` to check standard code formatting (`cargo fmt --all` applies these changes) - `cargo clippy --workspace -- -D warnings -D clippy::unwrap_used -A clippy::needless_collect -A clippy::result_large_err` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass - `cargo run -- crates/nu-std/tests/run.nu` to run the tests for the standard library > Note > from `nushell` you can also use the `toolkit` as follows > ```bash > use toolkit.nu # or use an `env_change` hook to activate it automatically > toolkit check pr > ``` --> # After Submitting <!-- If your PR had any user-facing changes, update [the documentation](https://github.com/nushell/nushell.github.io) after the PR is merged, if necessary. This will help us keep the docs up to date. --> 2023-05-26 17:32:48 +02:00			`miette = { version = "5.9", features = ["fancy-no-backtrace"] }`
Bump to `0.82.1` dev version (#9543) # Description Marks development or hotfix 2023-06-27 21:33:53 +02:00			`nu-parser = { version = "0.82.1", path = "../nu-parser" }`
			`nu-protocol = { version = "0.82.1", path = "../nu-protocol" }`
			`nu-engine = { version = "0.82.1", path = "../nu-engine" }`