Perguntas frequentes sobre licença e instalação

License Agreements in Ignite UI for Web Components

It is important to know all the legal terms and conditions regarding the Ignite UI for Web Components that you purchase and use.

Atualizamos nossos termos de licença e modelo de assinatura no segundo trimestre de 2020.

If your trial has ended or your subscription has expired, each developer on your team using Ignite UI will need to purchase a subscription. This will enable you to use our private npm feed hosted on https://packages.infragistics.com/npm/js-licensed/ for development. There you will find the latest versions of the Ignite UI for Web Components packages. If you have a current subscription, you can use this private feed and you will have access to the full version of Ignite UI for Web Components.

Para obter uma explicação detalhada do contrato de licença Ignite UI e dos termos de uso, clique aqui.

Infragistics oferece licenças gratuitas, não comerciais e não destinadas à revenda (NFR) para o seguinte:

Se você faz parte de um programa de desenvolvedor como o Microsoft MVP, o Microsoft Regional Director, o Google Developer Expert, etc.
Se você é um estudante primário, secundário ou universitário, ou uma instituição acadêmica, ou um professor.

Se você se qualificar para uma licença NFR gratuita e não comercial ou se tiver alguma dúvida sobre a licença, entre em contato conosco.

Currently only the igniteui-dockmanager package is available in our private npm feed, but in the future we will add the other Ignite UI for Web Components packages as well.

Ignite UI for Web Components npm packages - Using the Private npm feed

Npm is the most popular package manager and is also the default one for the runtime environment Node.js. It is highly adopted and is one of the fastest and easiest ways to manage the packages that you depend on in your project. For more information on how npm works, read the official npm documentation.

Infragistics Ignite UI for Web Components is available as npm packages and you can add them as dependencies to your project in a few easy steps. Choosing this approach will not require configuring npm. By installing this package you will start using the Ignite UI for Web Components Trial version of the product.

Currently only the igniteui-dockmanager npm package has a trial watermark, but in the future we will add it to the other Ignite UI for Web Components packages as well.

How to setup your environment to use the private npm feed

Primeiro, você precisa configurar o registro privado e associá-lo ao escopo Infragistics.

This will allow you to seamlessly use a mix of packages from the public npm registry and the Infragistics private registry. You will be asked to provide the username and the password that you use for logging into your Infragistics account. You should also provide the email that is registered to your Infragistics profile.

Se sua conta não estiver licenciada (você ainda estiver usando uma conta de avaliação), o feed de pacotes privado não estará acessível para você, por exemplo, ele retornará a mensagem de erro 404 ou 403. Somente contas licenciadas podem acessar o feed privado packages.infragistics.

Now, to log in to our private feed using npm

npm versão 9+

Nosso feed privado atualmente não oferece suporte a comandos login/adduser com npm v9, portanto, recomendamos as seguintes etapas para adicionar os campos de autenticação necessários à configuração:

npm config set @infragistics:registry https://packages.infragistics.com/npm/js-licensed/

npm config set //packages.infragistics.com/npm/js-licensed/:username=YOUR_USERNAME

npm config set //packages.infragistics.com/npm/js-licensed/:email=YOUR_IG_EMAIL

npm config set //packages.infragistics.com/npm/js-licensed/:_auth=YOUR_IG_AUTH_TOKEN

Você pode gerar o Access Token por meio do seu perfil Infragistics.

Essa abordagem é aplicável a todas as versões anteriores do npm.

Versão npm até v8

Execute o adduser comando e especifique uma conta de usuário e senha:

npm adduser --registry=https://packages.infragistics.com/npm/js-licensed/ --scope=@infragistics

Você será solicitado a fornecer o nome de usuário e a senha que você usa para fazer login em sua conta Infragistics. Você também deve fornecer o e-mail registrado em seu perfil Infragistics.

npm is disallowing the use of the "@" symbol inside your username as it is considered as being "not safe for the net". Because your username is actually the email that you use for your Infragistics account it always contains the symbol "@". That's why you must escape this limitation by replacing the "@" symbol with "!!" (two exclamation marks). For example, if your username is "username@example.com" when asked about your username you should provide the following input: "username!!example.com".

Depois que isso for feito, você estará logado e poderá instalar as versões mais recentes dos pacotes Ignite UI em seu projeto:

npm uninstall igniteui-dockmanager
npm install @infragistics/igniteui-dockmanager

npm uninstall igniteui-dockmanager
npm install @infragistics/igniteui-dockmanager

Have in mind that we have set the Ignite UI for Web Components package to be scoped, meaning that no changing the registries is needed if you want to install packages from our private feed and from npmjs.org simultaneously.

Changes in your project source after license package update

If you are upgrading from trial to licensed package the new packages will be scoped under @infragistics. As a result you can either:

Do a global replace for all trial packages and change then to the licensed scoped version across all files in your project. For example, replace all igniteui-dockmanager references to @infragistics/igniteui-dockmanager The change should affect all imports where such packages are used.

Or
Adicione um mapeamento de caminhos no tsconfig.json do projeto.

{
  /* ... */
  "compilerOptions": {
    "baseUrl": "./",
    "outDir": "./dist/out-tsc",
    /* ... */
    "paths": {
      "igniteui-dockmanager": ["./node_modules/@infragistics/igniteui-dockmanager"],
      "igniteui-dockmanager/*": ["./node_modules/@infragistics/igniteui-dockmanager/*"],
    }
  }
}

Change the themes imports like this:

@import '~igniteui-dockmanager/dist/collection/styles/igc.themes';

// Should be changed to

@import '~@infragistics/igniteui-dockmanager/dist/collection/styles/igc.themes';

So, if you've already adopted npm and you have an Ignite UI for Web Components license, don't hesitate setting up the Infragistics private feed and boost your productivity, using the full potential of Ignite UI for Web Components.

Access Token Usage

You can also authenticate to our private npm feed using an access token, which you can acquire through your infragistics.com user account. The access token authentication is the preferred alternative when you want to integrate a CI process in a publicly accessible repository, which uses the Ignite UI for Web Components licensed packages.

As informações a seguir são sobre como configurar a autenticação em nosso registro npm privado usando um token de acesso na configuração local, procedimentos de build do Azure Pipelines e processo de build do Travis CI:

Generate a token from https://account.infragistics.com/access-tokens

Cada token está com codificação Base64.

Adicione o seguinte ao seu.npmrc file

@infragistics:registry=https://packages.infragistics.com/npm/js-licensed/
//packages.infragistics.com/npm/js-licensed/:_auth=YOUR_ACCESS_TOKEN
//packages.infragistics.com/npm/js-licensed/:username=YOUR_USERNAME

Azure Pipelines Configuration

Atualize o azure-pipelines.yml com as seguintes etapas:

steps:

- script: npm config set @infragistics:registry $(npmRegistry)
  displayName: 'Npm add registry'
- script: npm config set $(igScope):_auth=$(token)
  displayName: 'Npm config auth'

Add npm registry and token variables.

Travis CI Configuration

Seguiremos quase a mesma abordagem aqui. A única diferença seria que a configuração será definida em before_install

before_install:
- echo "@infragistics:registry=https://packages.infragistics.com/npm/js-licensed/" >> ~/.npmrc
- echo "//packages.infragistics.com/npm/js-licensed/:_auth=$TOKEN" >> ~/.npmrc

A melhor maneira de definir uma variável de ambiente depende do tipo de informação que ela conterá. Então você tem duas opções:

criptografá-lo e adicioná-lo ao seu .travis.yml
adicione-o às configurações do repositório

GitHub Actions Configuration

Add the following scripts before the npm i(ci) step to your CI workflow configuration:

- run: echo "@infragistics:registry=https://packages.infragistics.com/npm/js-licensed/" >> ~/.npmrc
- run: echo "//packages.infragistics.com/npm/js-licensed/:_auth=${{ secrets.NPM_TOKEN }}" >> ~/.npmrc

Defina segredos (variáveis de ambiente criptografadas) e use-os no fluxo de trabalho de ações do GitHub para informações confidenciais, como o token de acesso.