@nushell/linux-arm 0.108.0 → 0.109.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +5 -5
- package/bin/nu +0 -0
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -14,17 +14,17 @@ To install `nu` by npm, simply run: `npm i -g nushell`, then you can run `nu` to
|
|
|
14
14
|
|
|
15
15
|
## FAQ
|
|
16
16
|
|
|
17
|
-
1. Why is `Nushell`
|
|
17
|
+
1. Why is `Nushell` published to `npm` even? There's nothing JavaScript about Nushell (that I know of?), Isn't npm...for js packages?
|
|
18
18
|
|
|
19
|
-
The direct cause of publishing `Nushell` to `npm` was from `Nushell`'s user feedback: "I'd like to run nu scripts in environments that only have access to npm for installing dependencies.". In fact, we have encountered many times such situation with network limitations too, and
|
|
19
|
+
The direct cause of publishing `Nushell` to `npm` was from `Nushell`'s user feedback: "I'd like to run nu scripts in environments that only have access to npm for installing dependencies.". In fact, we have encountered many times such situation with network limitations too, and publishing to `npm` is a good approach, especially for a container environment that doesn't have `winget` or `brew` installed.
|
|
20
20
|
|
|
21
|
-
`npm` may be thought as typically for js packages, however, nowadays lots of binaries written by `rust` or `go` have been published to npm, such as `git-cliff`, `lefthook`, etc. they are all dev tools, and `nushell` is an engine that could power lots of develop involved scripts, and
|
|
21
|
+
`npm` may be thought as typically for js packages, however, nowadays lots of binaries written by `rust` or `go` have been published to npm, such as `git-cliff`, `lefthook`, etc. they are all dev tools, and `nushell` is an engine that could power lots of develop involved scripts, and publishing it to `npm` will make it easier to access especially for JS related projects, as they already have `npm` been installed.
|
|
22
22
|
|
|
23
23
|
2. Will the npm version of `nu` I installed be bloated?
|
|
24
24
|
|
|
25
|
-
No. You can read that from the [base npm `package.json`](https://github.com/hustcer/nu-to-npm/blob/main/npm/app/package.json) and the [platform specific `package.json`](https://github.com/hustcer/nu-to-npm/blob/main/npm/package.json.tmpl), only the packages in `dependencies` will be installed, and the dependencies
|
|
25
|
+
No. You can read that from the [base npm `package.json`](https://github.com/hustcer/nu-to-npm/blob/main/npm/app/package.json) and the [platform specific `package.json`](https://github.com/hustcer/nu-to-npm/blob/main/npm/package.json.tmpl), only the packages in `dependencies` will be installed, and the number of dependencies to be installed is **0**, for `optionalDependencies` that means `npm` will choose the exact one package according to your `os` and `cpu` arch. For example, I'm using a mac with Intel cpu inside and `npm` will install only `@nushell/darwin-x64` for me and nothing else. See? `npm` choose the right package for me with just one command.
|
|
26
26
|
|
|
27
|
-
3.
|
|
27
|
+
3. Does the npm version of `nu` I installed have JS performance issues?
|
|
28
28
|
|
|
29
29
|
Well, you can read that from the [source here](https://github.com/hustcer/nu-to-npm/blob/main/npm/app/src/index.ts). All node does is simply call the `nu` binary itself, and nothing more.
|
|
30
30
|
|
package/bin/nu
CHANGED
|
Binary file
|