2022-04-28 22:57:26 +00:00
|
|
|
on:
|
|
|
|
|
pull_request:
|
2023-07-08 10:48:01 +00:00
|
|
|
push:
|
2022-04-28 22:57:26 +00:00
|
|
|
branches:
|
|
|
|
|
- main
|
2021-09-04 07:52:28 +00:00
|
|
|
|
2022-04-24 13:03:21 +00:00
|
|
|
name: continuous-integration
|
2021-09-04 07:52:28 +00:00
|
|
|
|
2023-07-08 10:48:01 +00:00
|
|
|
env:
|
Fix unit tests on Android (#10224)
# Description
* The path to the binaries for tests is slightly incorrect. It is
missing the build target when it is set with the `CARGO_BUILD_TARGET`
environment variable. For example, when `CARGO_BUILD_TARGET` is set to
`aarch64-linux-android`, the path to the `nu` binary is:
`./target/aarch64-linux-android/debug/nu`
rather than
`./target/debug/nu`
This is common on Termux since the default target that rustc detects can
cause problems on some projects, such as [python's `cryptography`
package](https://github.com/pyca/cryptography/issues/7248).
This technically isn't a problem specific to Android, but is more likely
to happen on Android due to the latter.
* Additionally, the existing variable named `NUSHELL_CARGO_TARGET` is in
fact the profile, not the build target, so this was renamed to
`NUSHELL_CARGO_PROFILE`. This change is included because without the
rename, the build system would be using `CARGO_BUILD_TARGET` for the
build target and `NUSHELL_CARGO_TARGET` for the build profile, which is
confusing.
* `std path add` tests were missing `android` test
# User-Facing Changes
For those who would like to build nushell on Termux, the unit tests will
pass now.
2023-09-05 08:17:34 +00:00
|
|
|
NUSHELL_CARGO_PROFILE: ci
|
2023-07-08 10:48:01 +00:00
|
|
|
NU_LOG_LEVEL: DEBUG
|
2023-11-09 18:07:15 +00:00
|
|
|
# If changing these settings also change toolkit.nu
|
2024-04-17 12:25:16 +00:00
|
|
|
CLIPPY_OPTIONS: "-D warnings -D clippy::unwrap_used -D clippy::unchecked_duration_subtraction"
|
2023-07-08 10:48:01 +00:00
|
|
|
|
2024-03-26 21:16:48 +00:00
|
|
|
concurrency:
|
|
|
|
|
group: ${{ github.workflow }}-${{ github.head_ref && github.ref || github.run_id }}
|
|
|
|
|
cancel-in-progress: true
|
|
|
|
|
|
2021-09-04 07:52:28 +00:00
|
|
|
jobs:
|
2023-07-08 10:48:01 +00:00
|
|
|
fmt-clippy:
|
2021-09-04 07:52:28 +00:00
|
|
|
strategy:
|
2022-05-16 04:02:11 +00:00
|
|
|
fail-fast: true
|
2021-09-04 07:52:28 +00:00
|
|
|
matrix:
|
2022-12-05 18:12:36 +00:00
|
|
|
# Pinning to Ubuntu 20.04 because building on newer Ubuntu versions causes linux-gnu
|
|
|
|
|
# builds to link against a too-new-for-many-Linux-installs glibc version. Consider
|
|
|
|
|
# revisiting this when 20.04 is closer to EOL (April 2025)
|
2024-04-12 11:37:35 +00:00
|
|
|
#
|
|
|
|
|
# Using macOS 13 runner because 14 is based on the M1 and has half as much RAM (7 GB,
|
|
|
|
|
# instead of 14 GB) which is too little for us right now. Revisit when `dfr` commands are
|
|
|
|
|
# removed and we're only building the `polars` plugin instead
|
|
|
|
|
platform: [windows-latest, macos-13, ubuntu-20.04]
|
2021-09-04 07:52:28 +00:00
|
|
|
|
2021-10-11 19:19:43 +00:00
|
|
|
runs-on: ${{ matrix.platform }}
|
|
|
|
|
|
2021-09-04 07:52:28 +00:00
|
|
|
steps:
|
2024-06-20 08:10:39 +00:00
|
|
|
- uses: actions/checkout@v4.1.7
|
2021-09-04 07:52:28 +00:00
|
|
|
|
2022-10-30 07:24:10 +00:00
|
|
|
- name: Setup Rust toolchain and cache
|
2024-10-02 00:32:07 +00:00
|
|
|
uses: actions-rust-lang/setup-rust-toolchain@v1.10.1
|
2022-04-28 18:18:27 +00:00
|
|
|
|
2022-12-07 02:57:07 +00:00
|
|
|
- name: cargo fmt
|
|
|
|
|
run: cargo fmt --all -- --check
|
2022-02-12 20:48:17 +00:00
|
|
|
|
2023-11-09 18:07:15 +00:00
|
|
|
# If changing these settings also change toolkit.nu
|
2022-04-28 19:39:21 +00:00
|
|
|
- name: Clippy
|
2024-05-20 17:22:08 +00:00
|
|
|
run: cargo clippy --workspace --exclude nu_plugin_* -- $CLIPPY_OPTIONS
|
2023-11-09 18:07:15 +00:00
|
|
|
|
2023-09-16 19:49:10 +00:00
|
|
|
# In tests we don't have to deny unwrap
|
|
|
|
|
- name: Clippy of tests
|
2024-05-20 17:22:08 +00:00
|
|
|
run: cargo clippy --tests --workspace --exclude nu_plugin_* -- -D warnings
|
2022-05-16 04:02:11 +00:00
|
|
|
|
2024-03-11 22:20:22 +00:00
|
|
|
- name: Clippy of benchmarks
|
2024-05-20 17:22:08 +00:00
|
|
|
run: cargo clippy --benches --workspace --exclude nu_plugin_* -- -D warnings
|
2024-03-11 22:20:22 +00:00
|
|
|
|
2023-07-08 10:48:01 +00:00
|
|
|
tests:
|
2022-04-29 19:48:04 +00:00
|
|
|
strategy:
|
2022-05-16 04:02:11 +00:00
|
|
|
fail-fast: true
|
2022-04-29 19:48:04 +00:00
|
|
|
matrix:
|
2022-12-05 18:12:36 +00:00
|
|
|
platform: [windows-latest, macos-latest, ubuntu-20.04]
|
2022-04-29 19:48:04 +00:00
|
|
|
|
|
|
|
|
runs-on: ${{ matrix.platform }}
|
|
|
|
|
|
|
|
|
|
steps:
|
2024-06-20 08:10:39 +00:00
|
|
|
- uses: actions/checkout@v4.1.7
|
2022-04-29 19:48:04 +00:00
|
|
|
|
2022-10-30 07:24:10 +00:00
|
|
|
- name: Setup Rust toolchain and cache
|
2024-10-02 00:32:07 +00:00
|
|
|
uses: actions-rust-lang/setup-rust-toolchain@v1.10.1
|
2022-04-29 19:48:04 +00:00
|
|
|
|
2022-02-12 20:48:17 +00:00
|
|
|
- name: Tests
|
2024-08-28 20:19:13 +00:00
|
|
|
run: cargo test --workspace --profile ci --exclude nu_plugin_*
|
2023-12-23 19:28:07 +00:00
|
|
|
- name: Check for clean repo
|
|
|
|
|
shell: bash
|
|
|
|
|
run: |
|
|
|
|
|
if [ -n "$(git status --porcelain)" ]; then
|
|
|
|
|
echo "there are changes";
|
|
|
|
|
git status --porcelain
|
|
|
|
|
exit 1
|
|
|
|
|
else
|
|
|
|
|
echo "no changes in working directory";
|
|
|
|
|
fi
|
|
|
|
|
|
standard library: bring the tests into the main CI (#8525)
Should close one of the tasks in #8450.
# Description
> **Note**
> in order of appearance in the global diff
- 1b7497c41966306aa3103a95a9b5ef5df7111ee4 adds the `std-tests` job to
the CI which
1. installs `nushell` in the runner
2. run the `tests.nu` module
> see `open .github/workflows/ci.yml | get jobs.std-tests | to yaml`
-
[`ec85b6fd`..`9c122115`](ec85b6fd3fc004cd94e3fada5c8e5fe2714fd629..9c12211564ca8ee90ed65ae45776dccb8f8e4ef1)
is where all the magic happens => see below
- :test_tube: 799c7eb7fd5f140289b36b9dbc00329c50e2fbda introduces some
bugs and failing test to see how the CI behaves => see how the [tests
failed](https://github.com/nushell/nushell/actions/runs/4460098237/jobs/7833018256)
as expected :x:
- :test_tube: and c3de1fafb5c5313e30c08c9ca57e09df33b61b74 reverts the
failing tests, i.e. the previous commit, leaving a standard library
whose tests all pass :tada: => see the [tests
passing](https://github.com/nushell/nushell/actions/runs/4460153434/jobs/7833110719?pr=8525#step:5:1)
now :heavy_check_mark:
## the changes to the runner
> see
[`ec85b6fd`..`9c122115`](ec85b6fd3fc004cd94e3fada5c8e5fe2714fd629..9c12211564ca8ee90ed65ae45776dccb8f8e4ef1)
the issue with the previous runner was the following: the clever trick
of using `nu -c "use ...; test"` did print the errors when occuring but
they did not capture the true "failure", i.e. in all cases the
`$env.LAST_EXIT_CODE` was set to `0`, never stopping the CI when a test
failed :thinking:
i first tried to `try` / `catch` the error in
ec85b6fd3fc004cd94e3fada5c8e5fe2714fd629 which kinda worked but only
throw a single error, the first one
i thought it was not the best and started thinking about a solution to
have a complete report of all failing tests, at once, to avoid running
the CI multiple times!
the easiest solution i found was the one i implemented in
9c12211564ca8ee90ed65ae45776dccb8f8e4ef1
> **Warning**
> this changes the structure of the runner quite a bit, but the `for`
loops where annoying to manipulate structured data and allow the runner
to draw a complete report...
now the runner does the following
- compute the list of all available tests in a table with the `file`,
`module` and `name` columns (first part of the pipe until `flatten` and
`rename`)
- run the tests one by one computing the new `pass` column
- with a `log info`
- captures the failing ones => puts `true` in `pass` if the test passes,
`false` otherwise
- if at least one test has failed, throw a single error with the list of
failing tests
### hope you'll like it :relieved:
# User-Facing Changes
```
$nothing
```
# Tests + Formatting
the standard tests now return a true error that will stop the CI
# After Submitting
```
$nothing
```
2023-03-25 18:29:08 +00:00
|
|
|
std-lib-and-python-virtualenv:
|
2022-02-12 20:48:17 +00:00
|
|
|
strategy:
|
2022-05-16 04:02:11 +00:00
|
|
|
fail-fast: true
|
2022-02-12 20:48:17 +00:00
|
|
|
matrix:
|
2022-12-05 18:12:36 +00:00
|
|
|
platform: [ubuntu-20.04, macos-latest, windows-latest]
|
2022-03-18 22:36:38 +00:00
|
|
|
py:
|
|
|
|
|
- py
|
2022-02-12 20:48:17 +00:00
|
|
|
|
|
|
|
|
runs-on: ${{ matrix.platform }}
|
2021-09-04 07:52:28 +00:00
|
|
|
|
2022-02-12 20:48:17 +00:00
|
|
|
steps:
|
2024-06-20 08:10:39 +00:00
|
|
|
- uses: actions/checkout@v4.1.7
|
2022-02-12 20:48:17 +00:00
|
|
|
|
2022-10-30 07:24:10 +00:00
|
|
|
- name: Setup Rust toolchain and cache
|
2024-10-02 00:32:07 +00:00
|
|
|
uses: actions-rust-lang/setup-rust-toolchain@v1.10.1
|
2022-04-28 22:57:26 +00:00
|
|
|
|
2022-02-12 20:48:17 +00:00
|
|
|
- name: Install Nushell
|
standard library: bring the tests into the main CI (#8525)
Should close one of the tasks in #8450.
# Description
> **Note**
> in order of appearance in the global diff
- 1b7497c41966306aa3103a95a9b5ef5df7111ee4 adds the `std-tests` job to
the CI which
1. installs `nushell` in the runner
2. run the `tests.nu` module
> see `open .github/workflows/ci.yml | get jobs.std-tests | to yaml`
-
[`ec85b6fd`..`9c122115`](ec85b6fd3fc004cd94e3fada5c8e5fe2714fd629..9c12211564ca8ee90ed65ae45776dccb8f8e4ef1)
is where all the magic happens => see below
- :test_tube: 799c7eb7fd5f140289b36b9dbc00329c50e2fbda introduces some
bugs and failing test to see how the CI behaves => see how the [tests
failed](https://github.com/nushell/nushell/actions/runs/4460098237/jobs/7833018256)
as expected :x:
- :test_tube: and c3de1fafb5c5313e30c08c9ca57e09df33b61b74 reverts the
failing tests, i.e. the previous commit, leaving a standard library
whose tests all pass :tada: => see the [tests
passing](https://github.com/nushell/nushell/actions/runs/4460153434/jobs/7833110719?pr=8525#step:5:1)
now :heavy_check_mark:
## the changes to the runner
> see
[`ec85b6fd`..`9c122115`](ec85b6fd3fc004cd94e3fada5c8e5fe2714fd629..9c12211564ca8ee90ed65ae45776dccb8f8e4ef1)
the issue with the previous runner was the following: the clever trick
of using `nu -c "use ...; test"` did print the errors when occuring but
they did not capture the true "failure", i.e. in all cases the
`$env.LAST_EXIT_CODE` was set to `0`, never stopping the CI when a test
failed :thinking:
i first tried to `try` / `catch` the error in
ec85b6fd3fc004cd94e3fada5c8e5fe2714fd629 which kinda worked but only
throw a single error, the first one
i thought it was not the best and started thinking about a solution to
have a complete report of all failing tests, at once, to avoid running
the CI multiple times!
the easiest solution i found was the one i implemented in
9c12211564ca8ee90ed65ae45776dccb8f8e4ef1
> **Warning**
> this changes the structure of the runner quite a bit, but the `for`
loops where annoying to manipulate structured data and allow the runner
to draw a complete report...
now the runner does the following
- compute the list of all available tests in a table with the `file`,
`module` and `name` columns (first part of the pipe until `flatten` and
`rename`)
- run the tests one by one computing the new `pass` column
- with a `log info`
- captures the failing ones => puts `true` in `pass` if the test passes,
`false` otherwise
- if at least one test has failed, throw a single error with the list of
failing tests
### hope you'll like it :relieved:
# User-Facing Changes
```
$nothing
```
# Tests + Formatting
the standard tests now return a true error that will stop the CI
# After Submitting
```
$nothing
```
2023-03-25 18:29:08 +00:00
|
|
|
run: cargo install --path . --locked --no-default-features
|
|
|
|
|
|
|
|
|
|
- name: Standard library tests
|
2024-01-25 10:50:07 +00:00
|
|
|
run: nu -c 'use crates/nu-std/testing.nu; testing run-tests --path crates/nu-std'
|
2022-02-12 20:48:17 +00:00
|
|
|
|
2024-04-09 12:25:45 +00:00
|
|
|
- name: Ensure that Cargo.toml MSRV and rust-toolchain.toml use the same version
|
|
|
|
|
run: nu .github/workflows/check-msrv.nu
|
|
|
|
|
|
2022-03-18 22:36:38 +00:00
|
|
|
- name: Setup Python
|
2023-12-15 07:31:18 +00:00
|
|
|
uses: actions/setup-python@v5
|
2022-03-18 22:36:38 +00:00
|
|
|
with:
|
|
|
|
|
python-version: "3.10"
|
2022-02-12 20:48:17 +00:00
|
|
|
|
2022-03-18 22:36:38 +00:00
|
|
|
- name: Install virtualenv
|
2023-08-20 14:00:59 +00:00
|
|
|
run: pip install virtualenv
|
2022-03-18 22:36:38 +00:00
|
|
|
shell: bash
|
2022-02-12 20:48:17 +00:00
|
|
|
|
2022-03-18 22:36:38 +00:00
|
|
|
- name: Test Nushell in virtualenv
|
2023-08-20 14:00:59 +00:00
|
|
|
run: nu scripts/test_virtualenv.nu
|
2022-03-18 22:36:38 +00:00
|
|
|
shell: bash
|
2022-05-02 07:20:57 +00:00
|
|
|
|
2023-12-23 19:28:07 +00:00
|
|
|
- name: Check for clean repo
|
|
|
|
|
shell: bash
|
|
|
|
|
run: |
|
|
|
|
|
if [ -n "$(git status --porcelain)" ]; then
|
|
|
|
|
echo "there are changes";
|
|
|
|
|
git status --porcelain
|
|
|
|
|
exit 1
|
|
|
|
|
else
|
|
|
|
|
echo "no changes in working directory";
|
|
|
|
|
fi
|
|
|
|
|
|
2022-05-02 07:20:57 +00:00
|
|
|
plugins:
|
|
|
|
|
strategy:
|
2022-05-16 04:02:11 +00:00
|
|
|
fail-fast: true
|
2022-05-02 07:20:57 +00:00
|
|
|
matrix:
|
2024-04-12 19:43:36 +00:00
|
|
|
# Using macOS 13 runner because 14 is based on the M1 and has half as much RAM (7 GB,
|
|
|
|
|
# instead of 14 GB) which is too little for us right now.
|
|
|
|
|
#
|
2024-05-04 15:00:44 +00:00
|
|
|
# Failure occurring with clippy for rust 1.77.2
|
2024-04-12 19:43:36 +00:00
|
|
|
platform: [windows-latest, macos-13, ubuntu-20.04]
|
2022-05-02 07:20:57 +00:00
|
|
|
|
|
|
|
|
runs-on: ${{ matrix.platform }}
|
|
|
|
|
|
|
|
|
|
steps:
|
2024-06-20 08:10:39 +00:00
|
|
|
- uses: actions/checkout@v4.1.7
|
2022-05-02 07:20:57 +00:00
|
|
|
|
2022-10-30 07:24:10 +00:00
|
|
|
- name: Setup Rust toolchain and cache
|
2024-10-02 00:32:07 +00:00
|
|
|
uses: actions-rust-lang/setup-rust-toolchain@v1.10.1
|
2022-05-02 07:20:57 +00:00
|
|
|
|
2022-05-13 11:40:46 +00:00
|
|
|
- name: Clippy
|
2024-03-26 21:16:48 +00:00
|
|
|
run: cargo clippy --package nu_plugin_* -- $CLIPPY_OPTIONS
|
2022-05-02 07:20:57 +00:00
|
|
|
|
2022-05-13 11:40:46 +00:00
|
|
|
- name: Tests
|
2022-12-07 02:57:07 +00:00
|
|
|
run: cargo test --profile ci --package nu_plugin_*
|
2023-12-23 19:28:07 +00:00
|
|
|
|
|
|
|
|
- name: Check for clean repo
|
|
|
|
|
shell: bash
|
|
|
|
|
run: |
|
|
|
|
|
if [ -n "$(git status --porcelain)" ]; then
|
|
|
|
|
echo "there are changes";
|
|
|
|
|
git status --porcelain
|
|
|
|
|
exit 1
|
|
|
|
|
else
|
|
|
|
|
echo "no changes in working directory";
|
|
|
|
|
fi
|
Start to Add WASM Support Again (#14418)
<!--
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.
-->
The [nushell/demo](https://github.com/nushell/demo) project successfully
demonstrated running Nushell in the browser using WASM. However, the
current version of Nushell cannot be easily built for the
`wasm32-unknown-unknown` target, the default for `wasm-bindgen`.
This PR introduces initial support for the `wasm32-unknown-unknown`
target by disabling OS-dependent features such as filesystem access, IO,
and platform/system-specific functionality. This separation is achieved
using a new `os` feature in the following crates:
- `nu-cmd-lang`
- `nu-command`
- `nu-engine`
- `nu-protocol`
The `os` feature includes all functionality that interacts with an
operating system. It is enabled by default, but can be disabled using
`--no-default-features`. All crates that depend on these core crates now
use `--no-default-features` to allow compilation for WASM.
To demonstrate compatibility, the following script builds all crates
expected to work with WASM. Direct user interaction, running external
commands, working with plugins, and features requiring `openssl` are out
of scope for now due to their complexity or reliance on C libraries,
which are difficult to compile and link in a WASM environment.
```nushell
[ # compatible crates
"nu-cmd-base",
"nu-cmd-extra",
"nu-cmd-lang",
"nu-color-config",
"nu-command",
"nu-derive-value",
"nu-engine",
"nu-glob",
"nu-json",
"nu-parser",
"nu-path",
"nu-pretty-hex",
"nu-protocol",
"nu-std",
"nu-system",
"nu-table",
"nu-term-grid",
"nu-utils",
"nuon"
] | each {cargo build -p $in --target wasm32-unknown-unknown --no-default-features}
```
## Caveats
This PR has a few caveats:
1. **`miette` and `terminal-size` Dependency Issue**
`miette` depends on `terminal-size`, which uses `rustix` when the target
is not Windows. However, `rustix` requires `std::os::unix`, which is
unavailable in WASM. To address this, I opened a
[PR](https://github.com/eminence/terminal-size/pull/68) for
`terminal-size` to conditionally compile `rustix` only when the target
is Unix. For now, the `Cargo.toml` includes patches to:
- Use my forked version of `terminal-size`.
- ~~Use an unreleased version of `miette` that depends on
`terminal-size@0.4`.~~
These patches are temporary and can be removed once the upstream changes
are merged and released.
2. **Test Output Adjustments**
Due to the slight bump in the `miette` version, one test required
adjustments to accommodate minor formatting changes in the error output,
such as shifted newlines.
# User-Facing Changes
<!-- List of all changes that impact the user experience here. This
helps us keep track of breaking changes. -->
This shouldn't break anything but allows using some crates for targeting
`wasm32-unknown-unknown` to revive the demo page eventually.
# 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
> ```
-->
- :green_circle: `toolkit fmt`
- :green_circle: `toolkit clippy`
- :green_circle: `toolkit test`
- :green_circle: `toolkit test stdlib`
I did not add any extra tests, I just checked that compiling works, also
when using the host target but unselecting the `os` feature.
# 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.
-->
~~Breaking the wasm support can be easily done by adding some `use`s or
by adding a new dependency, we should definitely add some CI that also
at least builds against wasm to make sure that building for it keep
working.~~
I added a job to build wasm.
---------
Co-authored-by: Ian Manske <ian.manske@pm.me>
2024-11-30 13:57:11 +00:00
|
|
|
|
|
|
|
|
build-wasm:
|
|
|
|
|
runs-on: ubuntu-latest
|
|
|
|
|
steps:
|
|
|
|
|
- uses: actions/checkout@v4.1.7
|
|
|
|
|
|
|
|
|
|
- name: Setup Rust toolchain and cache
|
|
|
|
|
uses: actions-rust-lang/setup-rust-toolchain@v1.10.1
|
|
|
|
|
|
|
|
|
|
- name: Add wasm32-unknown-unknown target
|
|
|
|
|
run: rustup target add wasm32-unknown-unknown
|
|
|
|
|
|
|
|
|
|
- run: cargo build -p nu-cmd-base --no-default-features --target wasm32-unknown-unknown
|
|
|
|
|
- run: cargo build -p nu-cmd-extra --no-default-features --target wasm32-unknown-unknown
|
|
|
|
|
- run: cargo build -p nu-cmd-lang --no-default-features --target wasm32-unknown-unknown
|
|
|
|
|
- run: cargo build -p nu-color-config --no-default-features --target wasm32-unknown-unknown
|
|
|
|
|
- run: cargo build -p nu-command --no-default-features --target wasm32-unknown-unknown
|
|
|
|
|
- run: cargo build -p nu-derive-value --no-default-features --target wasm32-unknown-unknown
|
|
|
|
|
- run: cargo build -p nu-engine --no-default-features --target wasm32-unknown-unknown
|
|
|
|
|
- run: cargo build -p nu-glob --no-default-features --target wasm32-unknown-unknown
|
|
|
|
|
- run: cargo build -p nu-json --no-default-features --target wasm32-unknown-unknown
|
|
|
|
|
- run: cargo build -p nu-parser --no-default-features --target wasm32-unknown-unknown
|
|
|
|
|
- run: cargo build -p nu-path --no-default-features --target wasm32-unknown-unknown
|
|
|
|
|
- run: cargo build -p nu-pretty-hex --no-default-features --target wasm32-unknown-unknown
|
|
|
|
|
- run: cargo build -p nu-protocol --no-default-features --target wasm32-unknown-unknown
|
|
|
|
|
- run: cargo build -p nu-std --no-default-features --target wasm32-unknown-unknown
|
|
|
|
|
- run: cargo build -p nu-system --no-default-features --target wasm32-unknown-unknown
|
|
|
|
|
- run: cargo build -p nu-table --no-default-features --target wasm32-unknown-unknown
|
|
|
|
|
- run: cargo build -p nu-term-grid --no-default-features --target wasm32-unknown-unknown
|
|
|
|
|
- run: cargo build -p nu-utils --no-default-features --target wasm32-unknown-unknown
|
|
|
|
|
- run: cargo build -p nuon --no-default-features --target wasm32-unknown-unknown
|
