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.91.1"

[dependencies]
nu-parser = { version = "0.91.1", path = "../nu-parser" }
nu-protocol = { version = "0.91.1", path = "../nu-protocol" }
nu-engine = { version = "0.91.1", path = "../nu-engine" }
miette = { workspace = true, features = ["fancy-no-backtrace"] }
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 version to `0.91.1` (#12085) 2024-03-06 23:08:14 +01:00			`version = "0.91.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]`
Bump version to `0.91.1` (#12085) 2024-03-06 23:08:14 +01:00			`nu-parser = { version = "0.91.1", path = "../nu-parser" }`
			`nu-protocol = { version = "0.91.1", path = "../nu-protocol" }`
			`nu-engine = { version = "0.91.1", path = "../nu-engine" }`
Introduce workspace dependencies (#12043) # Description This PR introduces [workspaces dependencies](https://doc.rust-lang.org/cargo/reference/workspaces.html#the-dependencies-table). The advantages are: - a single place where dependency versions are declared - reduces the number of files to change when upgrading a dependency - reduces the risk of accidentally depending on 2 different versions of the same dependency I've only done a few so far. If this PR is accepted, I might continue and progressively do the rest. # User-Facing Changes N/A # Tests + Formatting - :green_circle: `toolkit fmt` - :green_circle: `toolkit clippy` - :green_circle: `toolkit test` - :green_circle: `toolkit test stdlib` # After Submitting N/A 2024-03-07 23:40:31 +01:00			`miette = { workspace = true, features = ["fancy-no-backtrace"] }`
Bump miette from 5.10.0 to 7.0.0 (#11788) <!-- if this PR closes one or more issues, you can automatically link the PR with them by using one of the [linking keywords](https://docs.github.com/en/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword), e.g. - this PR should close #xxxx - fixes #xxxx you can also mention related issues, PRs or discussions! --> # Description Bump miette from 5.10.0 to 7.0.0 # 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` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass (on Windows make sure to [enable developer mode](https://learn.microsoft.com/en-us/windows/apps/get-started/developer-mode-features-and-debugging)) - `cargo run -- -c "use std testing; testing run-tests --path crates/nu-std"` 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. --> --------- Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com> 2024-02-08 02:26:18 +01:00