Guide applies to: modern

Troubleshooting npm

Here are some tips and tricks for trouble shooting the node package manager.

If you are a TRIAL customer

The Ext JS 30-day trial packages are available to install from public npm. Install the latest Ext JS version using the following command and skip to Step 2.

$ npm install -g @sencha/ext-gen

If you are an ACTIVE customer

Ext JS and all related commercial packages are hosted on Sencha’s private npm registry. Login to the registry using the following command which configures npm to download packages in the @sencha scope from Sencha’s registry.

Username Note:

The email and password used during support portal activation (after license purchase) will be used to login to Sencha’s NPM repo. The username is the same as the email used, however, the @ character is replaced with ‘..’ two periods. For example [[email protected]](https://docs.sencha.com/cdn-cgi/l/email-protection) converts to username: name..gmail.com

$ npm login --registry=https://npm.sencha.com/ --scope=@sencha

$ npm install -g @sencha/ext-gen

Community Edition

https://docs.sencha.com/extjs/7.0.0-CE/index.html

npm Reset

These steps could be used to reset the npm system, should you encounter auth issues (403’s) or checksum errors.

Linux / macOS

1. Run rm ~/.npmrc - removes the stored npm repository credentials. This location may be different on your system.
2. Run npm cache clean --force or rm -rf ~/.npm - clean the npm packages cache by removing it.
3. Run npm login --registry=https://npm.sencha.com --scope=@sencha - log back into the repository.
4. Run npm install -g @sencha/ext-gen or npm install -g @sencha/ext-react-gen

Windows (Command Prompt)

1. Run del %HOMEPATH%\.npmrc - removes the stored npm repository credentials. This location may be different on your system.
2. Run npm cache clean --force or rmdir /s /q %HOMEPATH%\AppData\Roaming\npm - clean the npm packages.
3. Run rmdir /s /q %HOMEPATH%\AppData\Roaming\npm-cache - clean the npm cache by removing it.
4. Run npm login --registry=https://npm.sencha.com --scope=@sencha - log back into the repository.
5. Run npm install -g @sencha/ext-gen or npm install -g @sencha/ext-react-gen

403 Errors

When authorization errors show up on npm.sencha.com.

The first to do is verify that you are properly authenticated with our repository by verifying you have been given an access token in your .npmrc file.

Windows: Verify Authorization Token, View the Contents of .npmrc

1. Run type .npmrc from the home directory (%HOMEPATH% or wherever your installation put this file).

Linux / macOS: Verify Authorization Token, View the Contents of .npmrc

1. Run cat .npmrc from the home directory (~/ or wherever your installation put this file).

Attempt to Re-Authenticate

1. Run npm login --registry=https://npm.sencha.com --scope=@sencha and login to the npm repo again.
2. Run npm --registry https://npm.sencha.com whoami testing your athorization.
3. Run npm install -g @sencha/ext-gen or npm install -g @sencha/ext-react-gen to verify that your logged in.

403 Errors for Premium Components

Premium components require you have purchased the premium component in the product matrix in the store. If you haven’t purchased the products premium component it will throw a 403 exception when you try run npm install for the products premium component.

• Check the store to compare the product packages matrix. Check the support portal subscription information, product code, and that can be used to tell you which product package edition you have in the matrix in the store.

Project Reset

There may be times where a reset of the node packages / dependencies within a project is necessary.

Windows (Command Prompt)

1. Run rmdir /s /q node_modules removing the node_modules directory in your project.
2. Run npm install downloading the dependencies again.

Linux / macOS

1. Run rm -rf node_modules removing the node_modules directory in your project.
2. Run npm install downloading the dependencies again.

npm Run Scripts

Using Build Profiles in npm Scripts

When you generate your application with ExtGen, two npm build scripts are provided to get you started. The first script is dev. The dev script will build the development version of your application and launch it in a browser. The second script is the build script. This script is designed to created a production-ready version of your application.

As with Sencha Cmd, your app.json will contain build profiles in the builds object. By default, the desktop build profile is specified as the build profile you want used in the build script for building your production application. You can specify which build profile you want used in an npm script by setting a script argument for --env.profile like this:

"dev": "webpack-dev-server --env.profile=phone --env.browser=yes --env.verbose=no",
"build": "npm run clean && cross-env webpack --env.profile=desktop --env.environment=production --env.treeshake=yes"

I have added a build profile and now I can’t build

When adding a build profile in the app.json you have to review it and verify that all the paths exists. For example, if you generated your application with ext-gen, make sure the {build.id}/some/path exists in your project. Ensure that you go through the entire app.json and verify all the paths exist in your code.

This is an error that shows up when an app.json property path does not exist.

% sencha app build
Sencha Cmd v7.X.X.X
[INF] Processing Build Descriptor : desktop (production environment)
[INF] Loading compiler context
[INF] Loading app json manifest...
[ERR] Failed to resolve dependency MyExtGenApp.Application for file MyExtGenApp.app.$Application
[ERR] 
[ERR] BUILD FAILED
[ERR] com.sencha.exceptions.ExNotFound: Unknown definition for dependency : MyExtGenApp.Application
[ERR] 
[ERR] Total time: 3 seconds
...

Once you add the missing paths from the app.json in your project it will build.

• You can create any number of scripts to suit your needs, we simply provide an example of a development build and a production build for your convenience.