Troubleshooting PAS Code

Accessing the PAS Code Packages Fails

You encounter problems when accessing the packages in the PAS package registry.

Possible Reason

The configuration has not been saved correctly in your .npmrc file.

Solution

To verify, if the configuration was applied, use the following command:

npm config get @pas:registry

The output should be https://npm.gitlab.scheer-group.com/.

If this is not the case, set the value to your .npmrc file using the following command:

npm config set@pas:registry=https://npm.gitlab.scheer-group.com/

Installation Fails

Although you have configured the registry correctly, there are errors during installation.

Possible Reason

You are using an incompatible Node.js version. PAS Code requires Node.js version 24.7 or later.

Solution

Check your current Node.js version with the following command:

node --version

If you version is older than 24.7, download and install the latest LTS release from the Node.js homepage.

npm on Windows: "Command Not Found"

You have installed the npm module globally but receive an error like the following

• bash: command not found

• 'command' is not recognized...

Possible Reason

These errors usually indicate, that the npm execution path is not registered in your Windows environment variables.

Why is this happening?

• Git Bash vs. CMD: Git Bash uses a Unix-style environment. If the Windows Path is updated, Git Bash usually inherits it, but sometimes requires a full restart of the application.

• NVM Users: If you use Node Version Manager (NVM), your global modules are stored inside specific version folders (e.g., ..\nvm\v20.10.0\node_modules). Switching Node versions might "hide" a module installed under a different version.

• Permissions: On some corporate machines, the installer might lack permission to automatically modify the system path.

Solution

To troubleshoot the issue, follow these steps:

Identify the location of the executables

Run the following command in your terminal to see where npm stores global executables:

Bash

npm config get prefix

Common result: C:\Users\<your user name>\AppData\Roaming\npm

Verify the executables

Navigate to that folder in your file explorer. You should see files named after your module (e.g., your-module and your-module.cmd).
If these files are missing, try reinstalling with npm install -g <your-module>.

Add to system path

If the files exist but the command fails, follow these steps to link the folder to Windows:

1. Open the editor for environment variables:

   • Press the Windows Key and type "Environment Variables"
     (German: “Umgebungsvariablen”).

   • Select Edit the system environment variables
     (German: Systemumgebungsvariablen bearbeiten).

2. Edit the path:

   • In the System Properties window, click button Environment Variables at the bottom
     (German: Systemeigenschaften, Button Umgebungsvariablen).

   • Under User variables, find the row named Path and click Edit.

3. Add a new entry:

   • Click New and paste the path you found in Step 1 (e.g., %AppData%\npm).

   • Click OK on all windows to save.

Refresh your terminal

• Close your terminal session.

• Re-open the terminal and try the command again.

Still not working?

Try running the module using npx as a fallback:

Bash

npx <your-module-name>

Related Content