nushell/Cargo.toml

230 lines
6.7 KiB
TOML
Raw Normal View History

2019-05-10 18:59:12 +02:00
[package]
2019-05-17 01:39:58 +02:00
name = "nu"
2020-01-29 03:17:02 +01:00
version = "0.9.0"
2019-08-23 07:36:52 +02:00
authors = ["Yehuda Katz <wycats@gmail.com>", "Jonathan Turner <jonathan.d.turner@gmail.com>", "Andrés N. Robalino <andres@androbtech.com>"]
2019-05-16 23:46:24 +02:00
description = "A shell for the GitHub era"
2019-06-02 18:50:41 +02:00
license = "MIT"
2019-05-10 18:59:12 +02:00
edition = "2018"
2019-07-16 21:17:46 +02:00
readme = "README.md"
2019-06-27 06:56:48 +02:00
default-run = "nu"
2019-07-16 21:17:46 +02:00
repository = "https://github.com/nushell/nushell"
homepage = "https://www.nushell.sh"
2019-12-15 13:56:26 +01:00
documentation = "https://www.nushell.sh/book/"
exclude = ["images"]
2019-05-10 18:59:12 +02:00
2019-12-18 18:58:23 +01:00
[workspace]
members = [
"crates/nu-macros",
"crates/nu-errors",
"crates/nu-source",
"crates/nu_plugin_average",
"crates/nu_plugin_binaryview",
"crates/nu_plugin_fetch",
"crates/nu_plugin_inc",
"crates/nu_plugin_match",
"crates/nu_plugin_post",
"crates/nu_plugin_ps",
"crates/nu_plugin_str",
"crates/nu_plugin_sum",
"crates/nu_plugin_sys",
"crates/nu_plugin_textview",
"crates/nu_plugin_tree",
"crates/nu-protocol",
"crates/nu-plugin",
2019-12-18 18:58:23 +01:00
"crates/nu-parser",
"crates/nu-value-ext",
"crates/nu-build"
]
2019-05-10 18:59:12 +02:00
# See more keys and their definitions at https://doc.rust-lang.org/cargo/reference/manifest.html
[dependencies]
nu-source = { version = "0.9.0", path = "./crates/nu-source" }
nu-plugin = { version = "0.9.0", path = "./crates/nu-plugin" }
nu-protocol = { version = "0.9.0", path = "./crates/nu-protocol" }
nu-errors = { version = "0.9.0", path = "./crates/nu-errors" }
nu-parser = { version = "0.9.0", path = "./crates/nu-parser" }
nu-value-ext = { version = "0.9.0", path = "./crates/nu-value-ext" }
nu_plugin_average = { version = "0.9.0", path = "./crates/nu_plugin_average", optional=true }
nu_plugin_binaryview = { version = "0.9.0", path = "./crates/nu_plugin_binaryview", optional=true }
nu_plugin_fetch = { version = "0.9.0", path = "./crates/nu_plugin_fetch", optional=true }
nu_plugin_inc = { version = "0.9.0", path = "./crates/nu_plugin_inc", optional=true }
nu_plugin_match = { version = "0.9.0", path = "./crates/nu_plugin_match", optional=true }
nu_plugin_post = { version = "0.9.0", path = "./crates/nu_plugin_post", optional=true }
nu_plugin_ps = { version = "0.9.0", path = "./crates/nu_plugin_ps", optional=true }
nu_plugin_str = { version = "0.9.0", path = "./crates/nu_plugin_str", optional=true }
nu_plugin_sum = { version = "0.9.0", path = "./crates/nu_plugin_sum", optional=true }
nu_plugin_sys = { version = "0.9.0", path = "./crates/nu_plugin_sys", optional=true }
nu_plugin_textview = { version = "0.9.0", path = "./crates/nu_plugin_textview", optional=true }
nu_plugin_tree = { version = "0.9.0", path = "./crates/nu_plugin_tree", optional=true }
2020-01-29 03:17:02 +01:00
nu-macros = { version = "0.9.0", path = "./crates/nu-macros" }
Add Range and start Signature support This commit contains two improvements: - Support for a Range syntax (and a corresponding Range value) - Work towards a signature syntax Implementing the Range syntax resulted in cleaning up how operators in the core syntax works. There are now two kinds of infix operators - tight operators (`.` and `..`) - loose operators Tight operators may not be interspersed (`$it.left..$it.right` is a syntax error). Loose operators require whitespace on both sides of the operator, and can be arbitrarily interspersed. Precedence is left to right in the core syntax. Note that delimited syntax (like `( ... )` or `[ ... ]`) is a single token node in the core syntax. A single token node can be parsed from beginning to end in a context-free manner. The rule for `.` is `<token node>.<member>`. The rule for `..` is `<token node>..<token node>`. Loose operators all have the same syntactic rule: `<token node><space><loose op><space><token node>`. The second aspect of this pull request is the beginning of support for a signature syntax. Before implementing signatures, a necessary prerequisite is for the core syntax to support multi-line programs. That work establishes a few things: - `;` and newlines are handled in the core grammar, and both count as "separators" - line comments begin with `#` and continue until the end of the line In this commit, multi-token productions in the core grammar can use separators interchangably with spaces. However, I think we will ultimately want a different rule preventing separators from occurring before an infix operator, so that the end of a line is always unambiguous. This would avoid gratuitous differences between modules and repl usage. We already effectively have this rule, because otherwise `x<newline> | y` would be a single pipeline, but of course that wouldn't work.
2019-12-04 22:14:52 +01:00
query_interface = "0.3.5"
typetag = "0.1.4"
rustyline = "6.0.0"
2019-12-08 18:56:21 +01:00
chrono = { version = "0.4.10", features = ["serde"] }
2019-08-31 23:19:59 +02:00
derive-new = "0.5.8"
2019-05-10 18:59:12 +02:00
prettytable-rs = "0.8.0"
2019-12-08 18:56:21 +01:00
itertools = "0.8.2"
2019-09-13 05:44:21 +02:00
ansi_term = "0.12.1"
2019-11-10 18:48:49 +01:00
nom = "5.0.1"
2019-05-11 09:00:33 +02:00
dunce = "1.0.0"
2020-01-17 21:35:48 +01:00
indexmap = { version = "1.3.1", features = ["serde-1"] }
2019-11-10 18:48:49 +01:00
byte-unit = "3.0.3"
base64 = "0.11"
Futures v0.3 upgrade (#1344) * Upgrade futures, async-stream, and futures_codec These were the last three dependencies on futures-preview. `nu` itself is now fully dependent on `futures@0.3`, as opposed to `futures-preview` alpha. Because the update to `futures` from `0.3.0-alpha.19` to `0.3.0` removed the `Stream` implementation of `VecDeque` ([changelog][changelog]), most commands that convert a `VecDeque` to an `OutputStream` broke and had to be fixed. The current solution is to now convert `VecDeque`s to a `Stream` via `futures::stream::iter`. However, it may be useful for `futures` to create an `IntoStream` trait, implemented on the `std::collections` (or really any `IntoIterator`). If something like this happends, it may be worthwhile to update the trait implementations on `OutputStream` and refactor these commands again. While upgrading `futures_codec`, we remove a custom implementation of `LinesCodec`, as one has been added to the library. There's also a small refactor to make the stream output more idiomatic. [changelog]: https://github.com/rust-lang/futures-rs/blob/master/CHANGELOG.md#030---2019-11-5 * Upgrade sys & ps plugin dependencies They were previously dependent on `futures-preview`, and `nu_plugin_ps` was dependent on an old version of `futures-timer`. * Remove dependency on futures-timer from nu * Update Cargo.lock * Fix formatting * Revert fmt regressions CI is still on 1.40.0, but the latest rustfmt v1.41.0 has changes to the `val @ pattern` syntax, causing the linting job to fail. * Fix clippy warnings
2020-02-06 04:46:48 +01:00
futures = { version = "0.3", features = ["compat", "io-compat"] }
async-stream = "0.2"
futures_codec = "0.4"
2020-01-17 21:35:48 +01:00
num-traits = "0.2.11"
term = "0.5.2"
2019-05-25 21:07:52 +02:00
bytes = "0.4.12"
2019-08-07 19:49:11 +02:00
log = "0.4.8"
2019-08-23 05:29:08 +02:00
pretty_env_logger = "0.3.1"
2020-01-17 21:35:48 +01:00
serde = { version = "1.0.104", features = ["derive"] }
2019-08-31 16:22:45 +02:00
bson = { version = "0.14.0", features = ["decimal128"] }
2019-12-08 18:56:21 +01:00
serde_json = "1.0.44"
2019-08-23 05:29:08 +02:00
serde-hjson = "0.9.1"
2019-06-03 09:41:28 +02:00
serde_yaml = "0.8"
2019-12-08 18:56:21 +01:00
serde_bytes = "0.11.3"
2019-11-10 18:48:49 +01:00
getset = "0.0.9"
2019-10-15 21:54:46 +02:00
language-reporting = "0.4.0"
app_dirs = "1.2.1"
csv = "1.1"
2020-01-17 21:35:48 +01:00
toml = "0.5.6"
clap = "2.33.0"
2020-01-17 21:35:48 +01:00
git2 = { version = "0.11.0", default_features = false }
2019-07-29 09:46:24 +02:00
dirs = "2.0.2"
glob = "0.3.0"
2019-06-07 02:31:22 +02:00
ctrlc = "3.1.3"
2020-01-17 21:35:48 +01:00
roxmltree = "0.9.0"
nom_locate = "1.0.0"
2019-11-10 18:48:49 +01:00
nom-tracable = "0.4.1"
2019-07-29 09:46:24 +02:00
unicode-xid = "0.2.0"
2019-06-16 08:43:40 +02:00
serde_ini = "0.2.0"
2019-11-10 18:48:49 +01:00
pretty-hex = "0.1.1"
hex = "0.4"
tempfile = "3.1.0"
which = "3.1.0"
ichwh = "0.3"
2019-08-16 07:47:47 +02:00
textwrap = {version = "0.11.0", features = ["term_size"]}
2020-01-17 21:35:48 +01:00
shellexpand = "1.1.1"
2019-08-30 21:07:07 +02:00
pin-utils = "0.1.0-alpha.4"
2020-01-17 21:35:48 +01:00
num-bigint = { version = "0.2.5", features = ["serde"] }
bigdecimal = { version = "0.1.0", features = ["serde"] }
2019-09-19 06:25:29 +02:00
serde_urlencoded = "0.6.1"
trash = "1.0.0"
2019-10-02 20:56:28 +02:00
regex = "1"
cfg-if = "0.1"
strip-ansi-escapes = "0.1.0"
calamine = "0.16"
2019-11-19 06:46:47 +01:00
umask = "0.1"
2019-12-08 18:56:21 +01:00
futures-util = "0.3.1"
2020-01-17 21:35:48 +01:00
termcolor = "1.1.0"
natural = "0.3.0"
parking_lot = "0.10.0"
2020-01-29 14:34:36 +01:00
meval = "0.2"
2019-05-23 06:30:43 +02:00
clipboard = {version = "0.5", optional = true }
ptree = {version = "0.2" }
2020-01-17 21:35:48 +01:00
starship = { version = "0.33.1", optional = true}
syntect = {version = "3.2.0", optional = true }
onig_sys = {version = "=69.1.0", optional = true }
crossterm = {version = "0.14.2", optional = true}
2020-01-17 21:35:48 +01:00
url = {version = "2.1.1", optional = true}
Restructure and streamline token expansion (#1123) Restructure and streamline token expansion The purpose of this commit is to streamline the token expansion code, by removing aspects of the code that are no longer relevant, removing pointless duplication, and eliminating the need to pass the same arguments to `expand_syntax`. The first big-picture change in this commit is that instead of a handful of `expand_` functions, which take a TokensIterator and ExpandContext, a smaller number of methods on the `TokensIterator` do the same job. The second big-picture change in this commit is fully eliminating the coloring traits, making coloring a responsibility of the base expansion implementations. This also means that the coloring tracer is merged into the expansion tracer, so you can follow a single expansion and see how the expansion process produced colored tokens. One side effect of this change is that the expander itself is marginally more error-correcting. The error correction works by switching from structured expansion to `BackoffColoringMode` when an unexpected token is found, which guarantees that all spans of the source are colored, but may not be the most optimal error recovery strategy. That said, because `BackoffColoringMode` only extends as far as a closing delimiter (`)`, `]`, `}`) or pipe (`|`), it does result in fairly granular correction strategy. The current code still produces an `Err` (plus a complete list of colored shapes) from the parsing process if any errors are encountered, but this could easily be addressed now that the underlying expansion is error-correcting. This commit also colors any spans that are syntax errors in red, and causes the parser to include some additional information about what tokens were expected at any given point where an error was encountered, so that completions and hinting could be more robust in the future. Co-authored-by: Jonathan Turner <jonathandturner@users.noreply.github.com> Co-authored-by: Andrés N. Robalino <andres@androbtech.com>
2020-01-21 23:45:03 +01:00
semver = {version = "0.9.0", optional = true}
[target.'cfg(unix)'.dependencies]
users = "0.9"
2019-08-29 01:32:58 +02:00
[features]
# Test executables
test-bins = []
default = ["sys", "ps", "textview", "inc", "str"]
stable = ["default", "starship-prompt", "binaryview", "match", "tree", "average", "sum", "post", "fetch", "clipboard"]
2019-12-19 18:18:06 +01:00
# Default
textview = ["crossterm", "syntect", "onig_sys", "url", "nu_plugin_textview"]
sys = ["nu_plugin_sys"]
ps = ["nu_plugin_ps"]
inc = ["semver", "nu_plugin_inc"]
str = ["nu_plugin_str"]
2019-12-19 18:18:06 +01:00
# Stable
average = ["nu_plugin_average"]
2019-12-04 18:51:20 +01:00
binaryview = ["nu_plugin_binaryview"]
2019-12-19 18:18:06 +01:00
fetch = ["nu_plugin_fetch"]
match = ["nu_plugin_match"]
2019-12-19 18:18:06 +01:00
post = ["nu_plugin_post"]
starship-prompt = ["starship"]
sum = ["nu_plugin_sum"]
Add Range and start Signature support This commit contains two improvements: - Support for a Range syntax (and a corresponding Range value) - Work towards a signature syntax Implementing the Range syntax resulted in cleaning up how operators in the core syntax works. There are now two kinds of infix operators - tight operators (`.` and `..`) - loose operators Tight operators may not be interspersed (`$it.left..$it.right` is a syntax error). Loose operators require whitespace on both sides of the operator, and can be arbitrarily interspersed. Precedence is left to right in the core syntax. Note that delimited syntax (like `( ... )` or `[ ... ]`) is a single token node in the core syntax. A single token node can be parsed from beginning to end in a context-free manner. The rule for `.` is `<token node>.<member>`. The rule for `..` is `<token node>..<token node>`. Loose operators all have the same syntactic rule: `<token node><space><loose op><space><token node>`. The second aspect of this pull request is the beginning of support for a signature syntax. Before implementing signatures, a necessary prerequisite is for the core syntax to support multi-line programs. That work establishes a few things: - `;` and newlines are handled in the core grammar, and both count as "separators" - line comments begin with `#` and continue until the end of the line In this commit, multi-token productions in the core grammar can use separators interchangably with spaces. However, I think we will ultimately want a different rule preventing separators from occurring before an infix operator, so that the end of a line is always unambiguous. This would avoid gratuitous differences between modules and repl usage. We already effectively have this rule, because otherwise `x<newline> | y` would be a single pipeline, but of course that wouldn't work.
2019-12-04 22:14:52 +01:00
trace = ["nu-parser/trace"]
2019-12-19 18:18:06 +01:00
tree = ["nu_plugin_tree"]
2019-08-29 01:32:58 +02:00
2019-08-27 23:45:18 +02:00
[dependencies.rusqlite]
Restructure and streamline token expansion (#1123) Restructure and streamline token expansion The purpose of this commit is to streamline the token expansion code, by removing aspects of the code that are no longer relevant, removing pointless duplication, and eliminating the need to pass the same arguments to `expand_syntax`. The first big-picture change in this commit is that instead of a handful of `expand_` functions, which take a TokensIterator and ExpandContext, a smaller number of methods on the `TokensIterator` do the same job. The second big-picture change in this commit is fully eliminating the coloring traits, making coloring a responsibility of the base expansion implementations. This also means that the coloring tracer is merged into the expansion tracer, so you can follow a single expansion and see how the expansion process produced colored tokens. One side effect of this change is that the expander itself is marginally more error-correcting. The error correction works by switching from structured expansion to `BackoffColoringMode` when an unexpected token is found, which guarantees that all spans of the source are colored, but may not be the most optimal error recovery strategy. That said, because `BackoffColoringMode` only extends as far as a closing delimiter (`)`, `]`, `}`) or pipe (`|`), it does result in fairly granular correction strategy. The current code still produces an `Err` (plus a complete list of colored shapes) from the parsing process if any errors are encountered, but this could easily be addressed now that the underlying expansion is error-correcting. This commit also colors any spans that are syntax errors in red, and causes the parser to include some additional information about what tokens were expected at any given point where an error was encountered, so that completions and hinting could be more robust in the future. Co-authored-by: Jonathan Turner <jonathandturner@users.noreply.github.com> Co-authored-by: Andrés N. Robalino <andres@androbtech.com>
2020-01-21 23:45:03 +01:00
version = "0.20.0"
2019-08-27 23:45:18 +02:00
features = ["bundled", "blob"]
2019-05-29 17:26:45 +02:00
[dev-dependencies]
pretty_assertions = "0.6.1"
2020-01-29 03:17:02 +01:00
nu-test-support = { version = "0.9.0", path = "./crates/nu-test-support" }
2019-06-27 06:56:48 +02:00
[build-dependencies]
2020-01-17 21:35:48 +01:00
toml = "0.5.6"
serde = { version = "1.0.104", features = ["derive"] }
2020-01-29 03:17:02 +01:00
nu-build = { version = "0.9.0", path = "./crates/nu-build" }
2019-06-27 06:56:48 +02:00
[lib]
name = "nu"
doctest = false
2019-06-27 06:56:48 +02:00
path = "src/lib.rs"
[[bin]]
name = "fail"
path = "crates/nu-test-support/src/bins/fail.rs"
required-features = ["test-bins"]
[[bin]]
name = "chop"
path = "crates/nu-test-support/src/bins/chop.rs"
required-features = ["test-bins"]
[[bin]]
name = "cococo"
path = "crates/nu-test-support/src/bins/cococo.rs"
required-features = ["test-bins"]
# Core plugins that ship with `cargo install nu` by default
# Currently, Cargo limits us to installing only one binary
# unless we use [[bin]], so we use this as a workaround
[[bin]]
name = "nu_plugin_core_textview"
path = "src/plugins/nu_plugin_core_textview.rs"
required-features = ["textview"]
2019-12-10 01:59:13 +01:00
[[bin]]
name = "nu_plugin_core_inc"
path = "src/plugins/nu_plugin_core_inc.rs"
2019-12-10 01:59:13 +01:00
required-features = ["inc"]
[[bin]]
name = "nu_plugin_core_ps"
path = "src/plugins/nu_plugin_core_ps.rs"
required-features = ["ps"]
2019-12-10 01:59:13 +01:00
[[bin]]
name = "nu_plugin_core_str"
path = "src/plugins/nu_plugin_core_str.rs"
2019-12-10 01:59:13 +01:00
required-features = ["str"]
[[bin]]
name = "nu_plugin_core_sys"
path = "src/plugins/nu_plugin_core_sys.rs"
required-features = ["sys"]
# Main nu binary
2019-06-27 06:56:48 +02:00
[[bin]]
name = "nu"
path = "src/main.rs"