README.md
Changed around line 90: As a result, both `n` itself and all Node.js versions it manages are hosted insi
- Changing from a previous Node.js installed to a different location may involve a few extra steps. See docs for [changing node location]((./docs/changing-node-location.md)) for a walk-through example of switching from using Homebrew to using `n` to manage Node.js.
+ Changing from a previous Node.js installed to a different location may involve a few extra steps. See docs for [changing node location](./docs/changing-node-location.md) for a walk-through example of switching from using Homebrew to using `n` to manage Node.js.
README.md
Changed around line 13: Node.js version management: no subshells, no profile setup, no convoluted API, j
- [Supported Platforms](#supported-platforms)
- [Installation](#installation)
- [Third Party Installers](#third-party-installers)
+ - [Replacing a previous node install](#replacing-a-previous-node-install)
- [Installing Node.js Versions](#installing-nodejs-versions)
- [Specifying Node.js Versions](#specifying-nodejs-versions)
- [Removing Versions](#removing-versions)
Changed around line 88: n-install sets both `PREFIX` and `N_PREFIX` to `$HOME/n`, installs `n` to `$HOME
+ ### Replacing a previous node install
+
+ Changing from a previous Node.js installed to a different location may involve a few extra steps. See docs for [changing node location]((./docs/changing-node-location.md)) for a walk-through example of switching from using Homebrew to using `n` to manage Node.js.
+
+ You have a problem with multiple versions if after installing node you see the "installed" and "active" locations are different:
+ ```console
+ % n lts
+ copying : node/20.12.2
+ installed : v20.12.2 to /usr/local/bin/node
+ active : v21.7.3 at /opt/homebrew/bin/node
+ ```
+
docs/changing-node-location.md
Changed around line 1
+ # Switching To `n` Managed Node.js
+
+ If you already have Node.js installed to a different root than `n` uses, you can easily end up with multiple copies of node (and npm, and npx, and globally installed packages!). Some common situations are you already had Node.js installed using your Linux package manager, or using another node version manager, or using say Homebrew. The two main ways you might resolve this are:
+
+ - uninstall from the old directory and reinstall to the new directory
+ - put the `bin` directory that `n` uses early in the `PATH` environment variable, so the `n` installed node is found first
+
+ The simplest setup to understand is the first one. Just have one version of `node` installed.
+
+ Let's walk-through the process of switching over from using Homebrew as an example. Let's start off with Node.js installed, `npm` updated, and an example global npm package. The key point is there are two install prefixes involved:
+
+ - old: `/opt/homebrew`
+ - new: `/usr/local`
+
+ ```console
+ % brew install node
+ % npm install --global npm@latest
+ % npm install --global @shadowspawn/forest-arborist
+ % brew list node
+ /opt/homebrew/Cellar/node/21.7.3/bin/node
+ /opt/homebrew/Cellar/node/21.7.3/bin/npm
+ /opt/homebrew/Cellar/node/21.7.3/bin/npx
+ /opt/homebrew/Cellar/node/21.7.3/etc/bash_completion.d/npm
+ /opt/homebrew/Cellar/node/21.7.3/include/node/ (107 files)
+ /opt/homebrew/Cellar/node/21.7.3/libexec/bin/ (2 files)
+ /opt/homebrew/Cellar/node/21.7.3/libexec/lib/ (2012 files)
+ /opt/homebrew/Cellar/node/21.7.3/share/doc/ (2 files)
+ /opt/homebrew/Cellar/node/21.7.3/share/man/man1/node.1
+ % command -v node
+ /opt/homebrew/bin/node
+ % command -v npm
+ /opt/homebrew/bin/npm
+ % npm prefix --global
+ /opt/homebrew
+ ```
+
+ Before we start transferring, list the global npm packages in the "old" location. We will refer back to this list.
+
+ ```console
+ % npm list --global
+ /opt/homebrew/lib
+ ├── @shadowspawn/forest-arborist@12.0.0
+ └── npm@10.5.0
+ ```
+
+ We could clean out the old location first, but let's install `n` and another copy of node and see what that looks like. We end up with two versions of node, and the active one is still the Homebrew managed version.
+
+ ```console
+ % brew install n
+ % n lts
+ installing : node-v20.12.2
+ mkdir : /usr/local/n/versions/node/20.12.2
+ fetch : https://nodejs.org/dist/v20.12.2/node-v20.12.2-darwin-arm64.tar.xz
+ copying : node/20.12.2
+ installed : v20.12.2 to /usr/local/bin/node
+ active : v21.7.3 at /opt/homebrew/bin/node
+ % command -v node
+ /opt/homebrew/bin/node
+ % which -a node
+ /opt/homebrew/bin/node
+ /usr/local/bin/node
+ % command -v npm
+ /opt/homebrew/bin/npm
+ % command -v npx
+ /opt/homebrew/bin/npx
+ % n doctor
+ <...>
+
+ CHECKS
+
+ Checking n install destination is in PATH...
+ good
+
+ Checking n install destination priority in PATH...
+ ⚠️ There is a version of node installed which will be found in PATH before the n installed version.
+
+ Checking npm install destination...
+ ⚠️ There is an active version of npm shadowing the version installed by n. Check order of entries in PATH.
+ installed : /usr/local/bin/npm
+ active : /opt/homebrew/bin/npm
+
+ <...>
+ ```
+
+ Now let's switch over. Delete everything from the old location. Delete all the global npm packages _except_ npm itself, then delete npm, then delete node.
+
+ ```console
+ npm uninstall --global @shadowspawn/forest-arborist
+
+ npm uninstall --global npm
+
+ brew uninstall node
+ ```
+
+ Check the active binaries are now the ones installed by `n`:
+ ```console
+ % command -v node
+ /usr/local/bin/node
+ % command -v npm
+ /usr/local/bin/npm
+ % command -v npx
+ /usr/local/bin/npx
+ ```
+
+ And lastly, reinstall the global npm packages you started with:
+ ```
+ % npm prefix --global
+ /usr/local
+ % npm install --global npm@latest
+ % npm install --global @shadowspawn/forest-arborist
+ % npm list -g
+ /usr/local/lib
+ ├── @shadowspawn/forest-arborist@12.0.0
+ └── npm@10.5.0
+ ```
package-lock.json
Changed around line 1
- "version": "9.2.3-0",
+ "version": "9.2.3",
package.json
Changed around line 1
- "version": "9.2.3-0",
+ "version": "9.2.3",
CHANGELOG.md
Changed around line 7: and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
- ## [9.2.2] (2024-04-21)
+ ## [9.2.3] (2024-04-21)
- avoid problems with `curl` 8.7.1 and `--compressed` by removing option until fixed
+ ## [9.2.2] (2024-04-21)
+
+ (No changes.)
+
Changed around line 508: Only minor functional changes, but technically could break scripts relying on sp
+ [9.2.3]: https://github.com/tj/n/compare/v9.2.2...v9.2.3
bin/n
Changed around line 61: function n_grep() {
- VERSION="v9.2.3-0"
+ VERSION="v9.2.3"
CHANGELOG.md
Changed around line 7: and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
- ## [Unreleased] (date goes here)
+ ## [9.2.2] (2024-04-21)
+
+ ### Fixed
+
+ - avoid problems with `curl` 8.7.1 and `--compressed` by removing option until fixed
Changed around line 504: Only minor functional changes, but technically could break scripts relying on sp
+ [9.2.2]: https://github.com/tj/n/compare/v9.2.1...v9.2.2
bin/n
Changed around line 61: function n_grep() {
- VERSION="v9.2.2-0"
+ VERSION="v9.2.2"
Changed around line 853: function do_get() {
- curl --silent --compressed "${CURL_OPTIONS[@]}" "$@"
+ curl --silent "${CURL_OPTIONS[@]}" "$@"
bin/n
Changed around line 61: function n_grep() {
- VERSION="v9.2.2-0"
+ VERSION="v9.2.3-0"
package-lock.json
Changed around line 1
- "version": "9.2.2",
+ "version": "9.2.3-0",
package.json
Changed around line 1
- "version": "9.2.2",
+ "version": "9.2.3-0",
package-lock.json
Changed around line 1
- "version": "9.2.2-0",
+ "version": "9.2.2",
package.json
Changed around line 1
- "version": "9.2.2-0",
+ "version": "9.2.2",
CHANGELOG.md
Changed around line 7: and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
+ ## [Unreleased] (date goes here)
+
bin/n
Changed around line 61: function n_grep() {
- VERSION="v9.2.1"
+ VERSION="v9.2.2-0"
package-lock.json
Changed around line 1
- "version": "9.2.1",
+ "version": "9.2.2-0",
package.json
Changed around line 1
- "version": "9.2.1",
+ "version": "9.2.2-0",
package-lock.json
Changed around line 1
- "version": "9.2.0",
+ "version": "9.2.1",
package.json
Changed around line 1
- "version": "9.2.0",
+ "version": "9.2.1",
CHANGELOG.md
Changed around line 7: and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
- ## [Unreleased] (date goes here)
+ ## [9.2.1] (2024-02-25)
+
+ ### Fixed
+
+ - `n doctor` works with custom `N_CACHE_PREFIX`
+
+ ### Added
+
+ - expand tests in `n doctor` for folder existence and permissions
Changed around line 31: and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
- ### Fixes
+ ### Fixed
- `Makefile` compatible with more flavours of `make` ([#745])
- quote paths in `Makefile` in case `PREFIX` contains spaces ([#746])
Changed around line 498: Only minor functional changes, but technically could break scripts relying on sp
+ [9.2.1]: https://github.com/tj/n/compare/v9.2.0...v9.2.1
bin/dev/release
Changed around line 18: function confirm {
- readonly N_VERSION="$(n --version)"
+ readonly N_VERSION="$(./bin/n --version)"
bin/n
Changed around line 61: function n_grep() {
- VERSION="v9.2.0"
+ VERSION="v9.2.1"
bin/n
Changed around line 1425: uninstall_installed() {
- echo "- define N_PREFIX to a writeable location, or"
+ if [[ "${N_CACHE_PREFIX}" == "${N_PREFIX}" ]]; then
+ echo "- define N_PREFIX to a writeable location, or"
+ else
+ echo "- define N_PREFIX and N_CACHE_PREFIX to writeable locations, or"
+ fi
Changed around line 1560: function show_diagnostics() {
- printf "\nChecking permissions for cache folder...\n"
- # Most likely problem is ownership rather than than permissions as such.
- local cache_root="${N_PREFIX}/n"
- if [[ -e "${N_PREFIX}" && ! -w "${N_PREFIX}" && ! -e "${cache_root}" ]]; then
- echo_red "You do not have write permission to create: ${cache_root}"
- show_permission_suggestions
- echo "- make a folder you own:"
- echo " sudo mkdir -p \"${cache_root}\""
- echo " sudo chown $(whoami) \"${cache_root}\""
- elif [[ -e "${cache_root}" && ! -w "${cache_root}" ]]; then
- echo_red "You do not have write permission to: ${cache_root}"
- show_permission_suggestions
- echo "- change folder ownership to yourself:"
- echo " sudo chown -R $(whoami) \"${cache_root}\""
- elif [[ ! -e "${cache_root}" ]]; then
- echo "Cache folder does not exist: ${cache_root}"
- echo "This is normal if you have not done an install yet, as cache is only created when needed."
- elif [[ -e "${CACHE_DIR}" && ! -w "${CACHE_DIR}" ]]; then
- echo_red "You do not have write permission to: ${CACHE_DIR}"
- show_permission_suggestions
- echo "- change folder ownership to yourself:"
- echo " sudo chown -R $(whoami) \"${CACHE_DIR}\""
- else
+ printf "\nChecking prefix folders...\n"
+ if [[ ! -e "${N_PREFIX}" ]]; then
+ echo "Folder does not exist: ${N_PREFIX}"
+ echo "- This folder will be created when you do an install."
+ fi
+ if [[ "${N_PREFIX}" != "${N_CACHE_PREFIX}" && ! -e "${N_CACHE_PREFIX}" ]]; then
+ echo "Folder does not exist: ${N_CACHE_PREFIX}"
+ echo "- This folder will be created when you do an install."
+ fi
+ if [[ -e "${N_PREFIX}" && -e "${N_CACHE_PREFIX}" ]]; then
+ if [[ -e "${N_CACHE_PREFIX}" ]]; then
+ printf "\nChecking permissions for cache folder...\n"
+ # Using knowledge cache path ends in /n/versions in following check.
+ if [[ ! -e "${CACHE_DIR}" && (( -e "${N_CACHE_PREFIX}/n" && ! -w "${N_CACHE_PREFIX}/n" ) || ( ! -e "${N_CACHE_PREFIX}/n" && ! -w "${N_CACHE_PREFIX}" )) ]]; then
+ echo_red "You do not have write permission to create: ${CACHE_DIR}"
+ show_permission_suggestions
+ echo "- make a folder you own:"
+ echo " sudo mkdir -p \"${CACHE_DIR}\""
+ echo " sudo chown $(whoami) \"${CACHE_DIR}\""
+ elif [[ ! -e "${CACHE_DIR}" ]]; then
+ echo "Cache folder does not exist: ${CACHE_DIR}"
+ echo "- This is normal if you have not done an install yet, as cache is only created when needed."
+ elif [[ ! -w "${CACHE_DIR}" ]]; then
+ echo_red "You do not have write permission to: ${CACHE_DIR}"
+ show_permission_suggestions
+ echo "- change folder ownership to yourself:"
+ echo " sudo chown -R $(whoami) \"${CACHE_DIR}\""
+ else
+ echo "good"
+ fi
+ fi
+
- # Most likely problem is ownership rather than than permissions as such.
Changed around line 1604: function show_diagnostics() {
+ if [[ ! -e "${N_PREFIX}/${subdir}" && ! -w "${N_PREFIX}" ]]; then
+ install_writeable="false"
+ echo_red "You do not have write permission to create: ${N_PREFIX}/${subdir}"
+ break
+ fi
- echo " (cd \"${N_PREFIX}\" && sudo chown -R $(whoami) bin lib include share)"
+ echo " cd \"${N_PREFIX}\""
+ echo " sudo mkdir -p bin lib include share"
+ echo " sudo chown -R $(whoami) bin lib include share"
FUNDING.yml
Changed around line 1
+ github: [tj, shadowspawn]
+ tidelift: npm/n
SECURITY.md
Changed around line 1
+ # Security Policy
+
+ ## Supported Versions
+
+ The latest two major versions get security updates.
+
+ Pull Requests for security issues will be considered for older versions.
+
+ ## Reporting a Vulnerability
+
+ To report a security vulnerability, please use the
+ [Tidelift security contact](https://tidelift.com/security).
+ Tidelift will coordinate the fix and disclosure.
docs/proxy-server.md
Changed around line 14: If your proxy requires authentication you can add the [url-encoded](https://urle
+ If you use `sudo` to run `n`, you need to do something extra to make the environment variables available. A simple way is to use `-E` (`--preserve-env`):
+
+ sudo -E n lts
+
bin/n
Changed around line 61: function n_grep() {
- VERSION="v9.2.1"
+ VERSION="v9.2.0"
package-lock.json
Changed around line 1
- "version": "9.2.1",
+ "version": "9.2.0",
package.json
Changed around line 1
- "version": "9.2.1",
+ "version": "9.2.0",
bin/n
Changed around line 61: function n_grep() {
- VERSION="v9.2.1-0"
+ VERSION="v9.2.1"
package-lock.json
Changed around line 1
- "version": "9.2.1-0",
+ "version": "9.2.1",
package.json
Changed around line 1
- "version": "9.2.1-0",
+ "version": "9.2.1",
README.md
Changed around line 67: Alternatively, you can clone this repo and
- to install `n` to `bin/n` of the directory specified in the environment variable `$PREFIX`, which defaults to `/usr/local` (note that you will likely need to use `sudo`). To install `n` in a custom location (such as `$CUSTOM_LOCATION/bin/n`), run `PREFIX=$CUSTOM_LOCATION make install`.
+ which defaults to `/usr/local/bin/n`. To install `n` in a custom location such as `$CUSTOM_LOCATION/bin/n`, run `PREFIX=$CUSTOM_LOCATION make install`.
README.md
Changed around line 37: If you already have Node.js installed, an easy way to install `n` is using `npm`
- The `n` command downloads and installs to `/usr/local` by default, but you may override this location by defining `N_PREFIX`.
+ The default root location used when running `n` is `/usr/local` where a normal user does not have write permission. You may strike the same sort of permission error when using npm to install global modules, like the above command. You have three main options:
+
+ 1) change the ownership of the relevant directories to yourself (see below)
+ 2) tell `n` to use a custom location where you do have write permissions (see `N_PREFIX`)
+ 3) put `sudo` in front of the command to run it as super user
+
- To avoid requiring `sudo` for `n` and `npm` global installs, it is suggested you either install to your home directory using `N_PREFIX`, or take ownership of the system directories:
+ To take ownership of the system directories (option 1):
README.md
Changed around line 215: List downloaded versions in cache:
+ Use `n` to access cached versions (already downloaded) without internet available.
+
+ n --offline 12
+
bin/n
Changed around line 61: function n_grep() {
- VERSION="v9.2.0"
+ VERSION="v9.2.1-0"
package-lock.json
Changed around line 1
- "version": "9.2.0",
+ "version": "9.2.1-0",
package.json
Changed around line 1
- "version": "9.2.0",
+ "version": "9.2.1-0",
package-lock.json
Changed around line 1
- "version": "9.1.1-0",
+ "version": "9.2.0",
package.json
Changed around line 1
- "version": "9.1.1-0",
+ "version": "9.2.0",
CHANGELOG.md
Changed around line 9: and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
+ ## [9.2.0] (2023-10-15)
+
+ ### Added
+
+ - `--offline` for resolving target version against cached downloads instead of internet lookup ([#785])
+
Changed around line 485: Only minor functional changes, but technically could break scripts relying on sp
+ [#785]: https://github.com/tj/n/pull/785
+ [9.2.0]: https://github.com/tj/n/compare/v9.1.0...v9.2.0
bin/n
Changed around line 61: function n_grep() {
- VERSION="v9.1.1-0"
+ VERSION="v9.2.0"
bin/n
Changed around line 135: g_target_node=
+ OFFLINE=false
Changed around line 394: Options:
- q, --quiet Disable curl output. Disable log messages processing "auto" and "engine" labels.
- d, --download Download if necessary, and don't make active
- a, --arch Override system architecture
+ --offline Resolve target version against cached downloads instead of internet lookup
- -all ls-remote displays all matches instead of last 20
- -insecure Turn off certificate checking for https requests (may be needed from behind a proxy server)
- -use-xz/--no-use-xz Override automatic detection of xz support and enable/disable use of xz compressed node downloads.
Changed around line 786: install() {
+ if [[ "$OFFLINE" == "true" ]]; then
+ abort "version unavailable offline"
+ fi
Changed around line 1108: function get_package_engine_version() {
+ [[ "$OFFLINE" != "true" ]] || abort "offline: an internet connection is required for looking up complex 'engine' ranges from package.json"
Changed around line 1205: function get_latest_resolved_version() {
+ elif [[ "$OFFLINE" == "true" ]]; then
+ g_target_node=$(display_local_versions "${version}")
Changed around line 1240: function display_match_limit(){
+ #
+ # Synopsis: display_local_versions version
+ #
+
+ function display_local_versions() {
+ local version="$1"
+ local match='.'
+ verbose_log "offline" "matching cached versions"
+
+ # Transform some labels before processing further.
+ if is_node_support_version "${version}"; then
+ version="$(display_latest_node_support_alias "${version}")"
+ match_count=1
+ elif [[ "${version}" = "auto" ]]; then
+ # suppress stdout logging so lsr layout same as usual for scripting
+ get_auto_version || return 2
+ version="${g_target_node}"
+ elif [[ "${version}" = "engine" ]]; then
+ # suppress stdout logging so lsr layout same as usual for scripting
+ get_engine_version || return 2
+ version="${g_target_node}"
+ fi
+
+ if [[ "${version}" = "latest" || "${version}" = "current" ]]; then
+ match='^node/.'
+ elif is_exact_numeric_version "${version}"; then
+ # Quote any dots in version so they are literal for expression
+ match="^node/${version//\./\.}"
+ elif is_numeric_version "${version}"; then
+ version="${version#v}"
+ # Quote any dots in version so they are literal for expression
+ match="${version//\./\.}"
+ # Avoid 1.2 matching 1.23
+ match="^node/${match}[^0-9]"
+ # elif is_lts_codename "${version}"; then
+ # see if demand
+ elif is_download_folder "${version}"; then
+ match="^${version}/"
+ # elif is_download_version "${version}"; then
+ # see if demand
+ else
+ abort "invalid version '$1' for offline matching"
+ fi
+
+ display_versions_paths \
+ | n_grep -E "${match}" \
+ | tail -n 1 \
+ | sed 's|node/||'
+ }
+
Changed around line 1635: while [[ $# -ne 0 ]]; do
- h|--help|help) display_help; exit ;;
- q|--quiet) set_quiet ;;
- d|--download) DOWNLOAD="true" ;;
+ --offline) OFFLINE="true" ;;
- -insecure) set_insecure ;;
- p|--preserve) N_PRESERVE_NPM="true" N_PRESERVE_COREPACK="true" ;;
- -no-preserve) N_PRESERVE_NPM="" N_PRESERVE_COREPACK="" ;;
test/tests/offline.bats
Changed around line 1
+ #!/usr/bin/env bats
+
+ load shared-functions
+ load '../../node_modules/bats-support/load'
+ load '../../node_modules/bats-assert/load'
+
+ function setup_file() {
+ unset_n_env
+ setup_tmp_prefix
+ # Note, NOT latest version of 16.
+ n --download 16.19.0
+ export N_NODE_MIRROR="https://no.internet.available"
+ }
+
+ function teardown_file() {
+ rm -rf "${TMP_PREFIX_DIR}"
+ }
+
+ function setup() {
+ hash -r
+ }
+
+ @test "n --offline 16" {
+ n --offline 16
+ hash -r
+ output="$(node --version)"
+ assert_equal "${output}" "v16.19.0"
+ rm "${TMP_PREFIX_DIR}/bin/node"
+ }
+
+ @test "n --offline latest" {
+ n --offline latest
+ hash -r
+ output="$(node --version)"
+ assert_equal "${output}" "v16.19.0"
+ rm "${TMP_PREFIX_DIR}/bin/node"
+ }
+
+ @test "n --offline run 16..." {
+ output="$(n --offline run 16 --version)"
+ assert_equal "${output}" "v16.19.0"
+ }
+
+ @test "n --offline exec 16..." {
+ output="$(n --offline exec 16 node --version)"
+ assert_equal "${output}" "v16.19.0"
+ }
+
+ @test "n --offline which 16..." {
+ output="$(n --offline which 16)"
+ assert_equal "${output}" "${TMP_PREFIX_DIR}/n/versions/node/16.19.0/bin/node"
+ }
README.md
Changed around line 66: to install `n` to `bin/n` of the directory specified in the environment variable
- On macOS with [Homebrew](https://brew.sh/) you can install the [n formula](https://github.com/Homebrew/homebrew-core/blob/master/Formula/n.rb).
+ On macOS with [Homebrew](https://brew.sh/) you can install the [n formula](https://github.com/Homebrew/homebrew-core/blob/master/Formula/n/n.rb).
bin/n
Changed around line 61: function n_grep() {
- VERSION="v9.1.0"
+ VERSION="v9.1.1-0"
package-lock.json
Changed around line 1
- "version": "9.1.0",
+ "version": "9.1.1-0",
package.json
Changed around line 1
- "version": "9.1.0",
+ "version": "9.1.1-0",
package-lock.json
Changed around line 1
- "version": "9.0.2-0",
+ "version": "9.1.0",
package.json
Changed around line 1
- "version": "9.0.2-0",
+ "version": "9.1.0",
CHANGELOG.md
Changed around line 9: and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
+ ## [9.1.0] (2023-04-15)
+
+ ### Added
+
+ - check for possible problem with multiple `npm` locations when running `n doctor` ([#764])
+
Changed around line 478: Only minor functional changes, but technically could break scripts relying on sp
+ [#764]: https://github.com/tj/n/pull/764
+ [9.1.0]: https://github.com/tj/n/compare/v9.0.1...v9.1.0
bin/n
Changed around line 61: function n_grep() {
- VERSION="v9.0.2-0"
+ VERSION="v9.1.0"
bin/n
Changed around line 1484: function show_diagnostics() {
+ # Check npm too. Simpler check than for PATH and node, more like the runtime logging for active/installed node.
+ if [[ -z "${N_PRESERVE_NPM}" ]]; then
+ printf "\nChecking npm install destination...\n"
+ local installed_npm="${N_PREFIX}/bin/npm"
+ local active_npm="$(command -v npm)"
+ if [[ -e "${active_npm}" && -e "${installed_npm}" && "${active_npm}" != "${installed_npm}" ]]; then
+ echo_red "There is an active version of npm shadowing the version installed by n. Check order of entries in PATH."
+ log "installed" "${installed_npm}"
+ log "active" "${active_npm}"
+ else
+ printf "good\n"
+ fi
+ fi
+
test/bin/run-all-tests
Changed around line 2
- services=( ubuntu-curl ubuntu-wget )
+ services=( fedora-curl ubuntu-wget )
test/docker-compose.yml
Changed around line 14: services:
+ fedora-curl:
+ extends:
+ file: ./docker-base.yml
+ service: testbed
+ build:
+ context: dockerfiles
+ dockerfile: Dockerfile-fedora-curl
test/dockerfiles/Dockerfile-fedora-curl
Changed around line 1
+ FROM fedora:latest
+
+ CMD ["/bin/bash"]