Khoros Global Support Home Start a conversation Sign in
Start a conversation
  1. Khoros Aurora
  2. Troubleshooting
  3. Articles

Resolve Aurora SDK npm ETARGET errors when the matching SDK version is unavailable

Table of contents

Overview

Use this article when an Aurora plugin repository cannot install or update khoros-aurora-sdk because npm reports that the requested SDK version does not exist.

The most common symptom is an npm ETARGET error like this:

npm ERR! code ETARGET
npm ERR! notarget No matching version found for khoros-aurora-sdk@~26.2.0.

This happens before the Aurora SDK can start or build your plugin. npm is only resolving package versions from the npm registry; it is not checking your community configuration yet. Clearing local files can help only after the required SDK version is actually published. If npm does not list any matching SDK version, your local repository cannot install that version until the package is available.

For the full Aurora SDK setup and Plugin Preview workflow, see Previewing local changes as different Users in staging sites. This article focuses only on the npm version-resolution failure.

Prerequisites

  • Access to the root folder of the Aurora plugin repository that contains package.json.
  • A terminal that can run npm commands from that repository root.
  • The Aurora community version you are targeting, at least the major and minor version, for example 26.2. If you do not know the community version, do not guess from the npm latest tag; ask your community administrator or contact Khoros Support before changing the SDK line.
  • Node.js installed. The Aurora SDK package declares a Node.js engine requirement of >=18.

Solution

1. Confirm that npm cannot find the requested SDK version

  1. Run the install command that is failing from the plugin repository root: 
    npm install
  2. Confirm that the error is specifically about a missing khoros-aurora-sdk version. The key lines are ETARGET, notarget, and No matching version found.
  3. Write down the exact package specifier from the error. In this example, the requested specifier is khoros-aurora-sdk@~26.2.0: 
    npm ERR! notarget No matching version found for khoros-aurora-sdk@~26.2.0.

Why this matters: An ETARGET error means npm could reach the registry but could not find a published version that satisfies the requested range. That is different from a network, proxy, or authentication problem, which usually produces different npm errors.

2. Check the SDK version range in package.json

  1. Open package.json in the plugin repository root.
  2. Find the khoros-aurora-sdk entry. It is typically in devDependencies because the SDK is used to build and preview the plugin locally: 
    {
  "devDependencies": {
    "khoros-aurora-sdk": "~26.2.0"
  }
}
  3. Compare the SDK major and minor version with the Aurora community version you are targeting. For an Aurora 26.2 community, the SDK dependency should use the 26.2.x line, such as ~26.2.0.

The tilde range keeps npm on the same minor version line. For example, ~26.2.0 can resolve to a later 26.2.x patch version, but it does not resolve to 26.3.x.

Why this matters: Aurora SDK version checks compare the SDK version installed in your repository with the SDK version reported by the community. The SDK allows compatible patch-level differences, but major and minor version mismatches can cause compatibility errors, upgrade prompts, or misleading troubleshooting. Do not switch to a different major or minor SDK line just to make npm install something.

What can go wrong if you skip this: If your community is on 26.2 and you install a newer 26.3.x SDK only because it is tagged as latest, the SDK can report that this version is not yet released for the community. If you keep an older 26.1.x SDK, the install may pass, but you have not resolved the version-alignment gap. Upgrade to the matching SDK line when it is available before investigating remaining startup or build failures.

3. Check whether the matching SDK version is published on npm

  1. Open npm in a browser, search for khoros-aurora-sdk, and open the package page.
  2. Select the Versions tab if it is not already selected.
  3. Look for a version that starts with the same major and minor version as your community. For example, for an Aurora 26.2 community, look for 26.2.0 or a later 26.2.x patch version.
  4. You can also check from the terminal: 
    npm view khoros-aurora-sdk versions --json
npm view khoros-aurora-sdk dist-tags --json

Why this matters: The latest tag tells npm what it installs when no version is specified, but it may point to a newer major or minor SDK line than the one your community is running. The important check is whether the specific major and minor line you need is published.

Note: Pre-release versions, such as versions containing -pre or -rc, are not the normal replacement for a missing stable SDK release. Use a pre-release SDK only if Khoros Support explicitly instructs you to do so.

4. If the matching version is published, refresh the dependency cleanly

If npm now lists a matching version, update the dependency and regenerate the install artifacts so your local machine and CI/CD pipeline resolve the same SDK version.

  1. Install the matching SDK version as a development dependency. Replace 26.2.0 with the matching published version for your community: 
    npm install --save-dev "khoros-aurora-sdk@~26.2.0"
  2. If the install still uses the old SDK version, remove the local install and lockfile, then reinstall.

On macOS or Linux:

rm -rf node_modules
rm -f package-lock.json
npm install

On Windows PowerShell:

Remove-Item -Recurse -Force node_modules
Remove-Item -Force package-lock.json
npm install
  1. Commit both files that control dependency resolution: 
    git add package.json package-lock.json
git commit -m "Update Aurora SDK version"

Why this matters: package.json declares the SDK version range, while package-lock.json records the exact resolved dependency tree. If you update one without the other, another developer or CI/CD job may continue using the older SDK resolution.

5. If the matching version is still missing, contact Khoros Support with the right evidence

If npm does not list any stable SDK version for the major and minor version of your Aurora community, do not keep changing your repository to unrelated SDK versions. Gather evidence and contact Khoros Support.

Include all of the following:

  • Your Aurora community URL and the community version you are targeting.
  • The khoros-aurora-sdk line from package.json.
  • The full npm error output, including the ETARGET and No matching version found lines.
  • The output of: 
    npm view khoros-aurora-sdk versions --json
npm view khoros-aurora-sdk dist-tags --json
node -v
npm -v
  • If a build pipeline is failing, the full pipeline log from the dependency-install step.

Why this matters: If the SDK package for your community version has not been published, the fix must happen at the package-availability level. Removing node_modules, deleting package-lock.json, or retrying the same install cannot make npm install a version that the registry does not have.

6. Verify that the SDK dependency and build are healthy

  1. Confirm the resolved SDK version: 
    npm ls khoros-aurora-sdk
  2. Confirm that the installed version is on the same major and minor line as your Aurora community version.
  3. Run the workflow that originally failed. For local Plugin Preview, run: 
    npm run start
  4. For a build failure, run your normal build command, for example: 
    npm run build

The npm-version issue is resolved when npm ls khoros-aurora-sdk shows the expected SDK line and the install step no longer fails with ETARGET. If npm run start or npm run build still fails after the correct SDK version installs, treat that as a separate SDK startup or build issue and provide the fresh logs to Khoros Support.

Troubleshooting reference

What you see What it means What to do next
No matching version found for khoros-aurora-sdk@~26.2.0 npm cannot find a published version that satisfies the requested 26.2.x range. Check the npm versions list. If no matching stable version exists, contact Khoros Support with the evidence listed above.
The npm page shows a matching version, but your machine still installs an older SDK. Your local install or lockfile may still be resolving the previous dependency tree. Remove node_modules, remove package-lock.json, run npm install, then commit the regenerated lockfile.
npm ls khoros-aurora-sdk shows the correct SDK version, but npm run start still fails. The package-availability problem is no longer the active blocker. Collect the complete fresh terminal output, your community URL, node -v, npm -v, and npm ls khoros-aurora-sdk, then contact Khoros Support.
The npm latest tag points to a newer SDK line than your community version. latest is not always the correct SDK line for every community. Use the SDK major and minor line that matches your community version unless Khoros Support gives different instructions.
Choose files or drag and drop files
ai_initiated
atlas_studio
kb_automation
Was this article helpful?
Yes
No

  1. Priyanka Bhotika

  2. Posted

Comments