访问 Sencha 的 npm 仓库

如果您是试用客户

Ext JS 30 天试用包可从公共 npm 安装。使用以下命令安装最新的 Ext JS 版本，然后跳到步骤 2。

$ npm install -g @sencha/ext-gen

如果您是活跃客户

Ext JS 和所有相关的商业软件包都托管在 Sencha 的私有 npm 注册表中。使用以下命令登录到注册表，该命令配置 npm 以从 Sencha 的注册表下载 @sencha 范围内的软件包。

用户名注意

支持门户激活期间使用的电子邮件和密码（购买许可证后）将用于登录 Sencha 的 NPM 仓库。用户名与使用的电子邮件相同，但是，@ 字符替换为 '..' 两个句点。例如 [email protected] 转换为用户名：name..gmail.com

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

CI/构建服务器登录和访问

当您需要在服务器环境登录时，请使用此步骤。

1. 在本地登录，以便您可以从您的 ~/.npmrc 文件中获取访问令牌。
2. 在 CI 构建步骤中，您可以通过两种方式之一登录。

使用 NPM 命令

使用 npm 命令。将 $SENCHA_NPM_TOKEN_VERDACCIO 替换为您 ~/.npmrc 文件中的令牌。

npm config set @sencha:registry https://npm.sencha.com/
npm config set //npm.sencha.com/:_authToken=$SENCHA_NPM_TOKEN_VERDACCIO

编写授权文件

创建并编写一个 ~/.npmrc 文件。将 %npm.sencha.com-authtoken% 替换为您 ~/.npmrc 文件中的令牌。

# Remove previous file
rm -f ~/.npmrc

# Write new ~/.npmrc
echo "Writing auth tokens to ~/.npmrc"
echo "@sencha:registry=http://npm.sencha.com" >> ~/.npmrc
echo "//npm.sencha.com/:_authToken=%npm.sencha.com-authtoken%" >> ~/.npmrc

# Debug
echo "Debug contents of ~/.npmrc:"
echo "~~~~~~~~~~~~~~~~~~~~~~"
cat ~/.npmrc
echo "~~~~~~~~~~~~~~~~~~~~~~"

# Check login with whoami
echo "Invoking NPM whoami"
echo "~~~~~~~~~~~~~~~~~~~~~~"
npm --registry http://npm.sencha.com/ whoami
echo "~~~~~~~~~~~~~~~~~~~~~~"

Travis CI 配置

这是一个 Travis CI 示例配置。

env:
  # npm.sencha.com
  # gem install travis
  # travis login --pro --github-token replace_with_github_personal_token
  # cd to/repo
  # travis encrypt SENCHA_NPM_TOKEN_VERDACCIO="replace_with_apikey"
  # SENCHA_NPM_TOKEN_VERDACCIO - secure: "XXXX... generation removed"
  # early-adopter
  # travis encrypt SENCHA_NPM_TOKEN_EARLYADOPTER="replace_with_apikey"
  - secure: "XXXX... generation removed"

os: osx
language: node_js
node_js:
 - "lts/*"

cache:
  npm: false

before_install:
  # NPM Login - commercial
  # - npm config set @sencha:registry https://npm.sencha.com/
  # - npm config set //npm.sencha.com/:_authToken=$SENCHA_NPM_TOKEN_VERDACCIO
  # NPM Login - early-adopter
  - npm config set @sencha:registry https://sencha.myget.org/F/early-adopter/npm/
  - npm config set //sencha.myget.org/F/early-adopter/npm/:_authToken=$SENCHA_NPM_TOKEN_EARLYADOPTER

install: 
  - cd internal-components
  - npm install

script:
  - npm run build

deploy:
  skip_cleanup: true
  provider: script
  script: bash deploy.sh
  on:
    branch: master 

# Run CLI in this repo
# Delete Cache
# travis cache
# travis cache --delete

注意：现有客户使用您的支持门户凭据。但将用户名中的 @ 字符替换为 '..' 两个句点，因此转换后的用户名将如下所示：name..gmail.com。

创建您自己的 Sencha 仓库副本

有时，特别是对于持续集成，您可能希望有一种场景，您不必担心访问凭据或身份验证来从我们的 NPM 仓库获取内容。

本节概述了您可以从我们的仓库下载所有 Sencha 节点软件包，并将它们本地保存，而无需持续身份验证的方法。

在本指南中，我们将使用目标本地目录“./vendor”来包含所有 Sencha 节点软件包。这可以命名为您认为有意义的任何名称。以下步骤假设您在应用程序的根目录中。

    1. Login to Sencha’s NPM repository to authenticate yourself so you may access all Sencha packages.

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

    2. While authenticated, install all Sencha packages required by your application except @sencha/ext-webpack-plugin.

    3. After all packages are installed, copy the contents of ./node_modules/@sencha to ./vendor/@sencha. Ensure that any source control application you use has the ‘./vendor’ directory added to it so that these packages are available in any target system that will checkout your application.

    4. Update your package.json to link all required packages to their new location in the ./vendor folder. For example:

      “dependencies”: {
        “@sencha/ext”: “file:vendor/@sencha/ext”
      }

    5. Next, update the package.json file for each individual Sencha package found in the ‘vendor’ directory (e.g. vendor/@sencha/ext/package.json). You will want to

      a. Remove any/all “scripts” definitions in the file. For example:

        “scripts”: {
          “install”: “node authorize.js”
        }

      b. Update dependency references to reflect that other packages are now locally found in the vendor folder. For example:

        “@dependencies”: {
          “@sencha/ext-core”: “file:../ext-core”
        }

      c. Finally, remove any “_activatedby” property which may exist in the package.json (it should be located at the bottom). These properties are part of npm authentication and may cause issues if retained.

    6. As you will no longer be using Sencha NPM server, unregister the packages locally from the server by editing your .npmrc file and commenting out the following line (if present) by placing a hash symbol at the start:

      # @sencha:registry = “https://npm.sencha.com”

    7. Delete your ./node modules directory along with the package-lock.json file.

    8. Edit package.json and remove ‘@sencha/ext-webpack-plugin’ from the “devDependencies” block (if one exists).

    9. Run npm install to re-populate the node_modules required for your application. This will also populate the ‘node_modules/@sencha’ directory with links to your vendor directory locations, rather than downloading the source from our repository.

    10. Run npm install @sencha/ext-webpack-plugin --save-dev. NPM will install this package and its @sencha/cmd dependency from the public npm registry.

    11. If you previously have a build server configured with any Sencha authentication, you may remove this authentication from any buildspec files. As you will be using your own local copy of our packages, Sencha npm repo authentication is no longer necessary.

    12. Finally, commit these changes to any CVS and review CI/CD pipelines as necessary to ensure builds run correctly and without incident.

请参考以下 GIF 以查看该过程。

演示 1

演示 2

故障排除

有关对 Sencha 仓库进行身份验证的故障排除，请参阅 Npm 故障排除