nushell/scripts/install-all.ps1

33 lines
989 B
PowerShell
Raw Permalink Normal View History

# Usage: Just run `powershell install-all.ps1` in nushell root directory
Write-Output "-----------------------------------------------------------------"
Write-Output "Installing nushell (nu) and all the plugins"
Write-Output "-----------------------------------------------------------------"
Write-Output ""
Write-Output "Install nushell from local..."
Write-Output "----------------------------------------------"
cargo install --force --path . --locked
2022-08-11 16:40:35 +02:00
$NU_PLUGINS = @(
'nu_plugin_example',
'nu_plugin_gstat',
'nu_plugin_inc',
2022-08-11 16:40:35 +02:00
'nu_plugin_query',
Move some `from xxx` commands to plugin (#7942) # Description From nushell 0.8 philosophy: https://github.com/nushell/nushell.github.io/blob/main/contributor-book/philosophy_0_80.md#core-categories > The following categories should be moved to plugins: Uncommon format support So this pr is trying to move following commands to plugin: - [X] from eml - [x] from ics - [x] from ini - [x] from vcf And we can have a new plugin handles for these formatting, currently it's implemented here: https://github.com/WindSoilder/nu_plugin_format The command usage should be the same to original command. If it's ok, the plugin can support more formats like [parquet](https://github.com/fdncred/nu_plugin_from_parquet), or [EDN format](https://github.com/nushell/nushell/issues/6415), or something else. Just create a draft pr to show what's the blueprint looks like, and is it a good direction to move forward? # 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` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass # 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-02-13 13:42:08 +01:00
'nu_plugin_custom_values',
'nu_plugin_formats'
chore: Add nu_plugin_polars to build and install scripts (#13550) - Add `nu_plugin_polars` to the list of plugins in `build-all-maclin.sh`. - Add `nu_plugin_polars` to the list of plugins in `build-all.nu`. - Add `nu_plugin_polars` to the list of plugins in `install-all.ps1`. - Add `nu_plugin_polars` to the list of plugins in `install-all.sh`. - Add `nu_plugin_polars` to the list of plugins in `uninstall-all.sh`. <!-- 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 <!-- Thank you for improving Nushell. Please, check our [contributing guide](../CONTRIBUTING.md) and talk to the core team before making major changes. Description of your pull request goes here. **Provide examples and/or screenshots** if your changes affect the user experience. --> # 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 toolkit.nu; toolkit test stdlib"` 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. -->
2024-08-06 22:23:56 +02:00
'nu_plugin_polars'
)
2022-08-11 16:40:35 +02:00
foreach ( $plugin in $NU_PLUGINS) {
Write-Output ''
Write-Output "----------------------------------------------"
Write-Output "Install plugin $plugin from local..."
Write-Output "----------------------------------------------"
Set-Location crates/$plugin
cargo install --force --path .
Set-Location ../../
}