Preguntas frecuentes sobre licencia e instalación
Ignite UI for Angular is offered under a dual-license model, which allows for both commercial and permissive open-source use, depending on the components, modules, directives, and services being used.
It is crucial to understand which license applies to which part of the package. The topic Open Source vs Premium contains details on what type of license is applied to each component and therefore if you need to buy a commercial license based on the components you are using in your projects.
License Agreements
For components under commercial license, it is important to know all the legal terms and conditions that apply regarding their purchase and use.
Note
We have updated our license terms and subscription model in fourth quarter of 2025.
If your trial has ended or your subscription has expired, each developer on your team using components under commercial license from 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 Angular 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 Angular.
Infragistics ofrece licencias gratuitas, no comerciales y no aptas para reventa (NFR) para lo siguiente:
- Si forma parte de un programa de desarrolladores como Microsoft MVP, Director Regional de Microsoft, Experto en Desarrolladores de Google, etc.
- Si eres estudiante de primaria, secundaria o universidad, o de una institución académica, o profesor.
Si califica para obtener una licencia NFR gratuita y no comercial o si tiene alguna pregunta sobre la licencia, comuníquese con nosotros.
Ignite UI for Angular npm packages - Using the Private npm feed
Npm es el administrador de paquetes más popular y también es el predeterminado para el entorno de ejecución Node.js. Altamente adoptada, es una de las formas más rápidas y sencillas de administrar los paquetes de los que depende en su proyecto. Para obtener más información sobre cómo funciona npm, lea la documentación oficial de npm.
Infragistics Ignite UI for Angular is available as an npm package and you can add it as a dependency to your project in a few easy steps using the Ignite UI CLI or using Ignite UI for Angular Schematics. Choosing this approach will not require configuring npm. If you plan to only use components from Ignite UI for Angular under MIT license, there is nothing else you will need to do. However, if you are using components under a commercial license, downloading the package from npm starts your trial period of the product.
Note
¿Qué significa empezar a utilizar una versión de prueba? Significa que utilizará una versión de nuestro producto con una marca de agua como parte de su vista web. Esto no significa que utilizará el paquete con licencia durante un período de tiempo determinado antes de que caduque. Por ejemplo, durante un mes.
The Infragistics Ignite UI Dock Manager Web Component is available as a separate npm package and by installing it you will start using the Ignite UI Dock Manager Web Component Trial version of the product.
More information on how to start using the Ignite UI for Angular npm package can be found in this topic. Additional information on Ignite UI Dock Manager Web Component can be found in the Dock Manager documentation.
Upgrading packages using our Angular Schematics or Ignite UI CLI
If Ignite UI for Angular has been added to the project using ng add or the project has been created through our schematics collection or Ignite UI CLI, you can use our upgrade-packages to automatically upgrade your app to using our licensed packages. Your project package dependencies will include either @igniteui/angular-schematics or igniteui-cli, with both of them supporting the upgrade command.
Note
A medida que el proceso cambia los paquetes, le recomendamos que actualice su proyecto primero antes de cambiar. De esta manera, evitará recoger una versión superior de Ignite UI Angular y perderse en posibles migraciones de actualizaciones. Siga nuestra Guía de actualización.
Dependiendo de la configuración de su proyecto, ejecute el siguiente esquema en su proyecto:
ng g @igniteui/angular-schematics:upgrade-packages
or use igniteui-cli:
ig upgrade-packages
El esquema o comando se encargará de cambiar las dependencias del paquete del proyecto y actualizar las referencias fuente. Se le pedirá que inicie sesión en nuestro registro npm si aún no está configurado.
Note
If your project is using yarn, make sure to run upgrade-packages with the --skip-install flag. Then execute yarn install after to properly update your yarn.lock as the upgrade command currently uses npm for the install.
How to setup your environment to use the private npm feed (Step by step guide)
First you need to setup the private registry and to associate this registry with the Infragistics scope
Esto le permitirá utilizar sin problemas una combinación de paquetes del registro público npm y el registro privado Infragistics.
Note
Si su cuenta no tiene licencia (todavía está usando una cuenta de prueba), no podrá acceder al feed del paquete privado, por ejemplo, devolverá un mensaje de error 404 o 403. Sólo las cuentas con licencia pueden acceder al feed privado de packages.infragistics.
Now, to log in to our private feed using npm
NPM versión 9+
Our private feed doesn't currently support login/adduser commands with npm v9, so we recommend the following steps instead to add the required auth fields to the config:
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
Puedes generar un token de acceso a través de tu perfil Infragistics.
This approach is applicable to all prior versions of npm.
versión npm hasta v8
Run the adduser command and specify a user account and password:
npm adduser --registry=https://packages.infragistics.com/npm/js-licensed/ --scope=@infragistics
Se le solicitará que proporcione el nombre de usuario y la contraseña que utiliza para iniciar sesión en su cuenta Infragistics. También debe proporcionar el correo electrónico que está registrado en su perfil Infragistics.
Note
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".
Note
macOS shell behavior: If you're using macOS and setting the :_auth token manually via npm config set, make sure to wrap the token in double quotes like this:
npm config set //packages.infragistics.com/npm/js-licensed/:_auth="YOUR_IG_AUTH_TOKEN"
Esto es necesario debido a las diferencias de análisis de shell en macOS que pueden causar problemas de autenticación si los caracteres especiales del token no se entrecomillan correctamente. Este problema no suele ocurrir en Windows.
After this is done, you will be logged in and you will be able to install the latest versions of the Ignite UI packages into your project
npm uninstall igniteui-angular
npm install @infragistics/igniteui-angular
npm uninstall igniteui-dockmanager
npm install @infragistics/igniteui-dockmanager
Keep in mind that we have set the Ignite UI for Angular package to be scoped, meaning that no registry changes are needed if you want to install packages from our private feed and from npmjs.org simultaneously.
Es posible que sea necesario realizar algunos cambios adicionales en la fuente de su proyecto.
If you are upgrading from a trial to a licensed package and you are not using the automated CLI migrations:
- Add a paths mapping in the project's tsconfig.json.
{
/* ... */
"compilerOptions": {
"baseUrl": "./",
"outDir": "./dist/out-tsc",
/* ... */
"paths": {
"igniteui-dockmanager": ["./node_modules/@infragistics/igniteui-dockmanager"],
"igniteui-dockmanager/*": ["./node_modules/@infragistics/igniteui-dockmanager/*"],
}
}
}
- Add a
stylePreprocessorOptionsmapping to your project'sangular.json
{
"projects": {
..
"prefix": "app",
"architect": {
"build": {
"builder": "@angular-devkit/build-angular:browser",
"options": {
...
"aot": true,
"stylePreprocessorOptions": {
"includePaths": [
"node_modules/@infragistics"
]
}
...
},
- Remove the
~sign from your project's Sass imports for theigniteui-angular/libsource:
@use "~igniteui-angular/lib/core/styles/themes/index" as *;
// Should be changed to
@use "igniteui-angular/lib/core/styles/themes/index" as *;
If you've already adopted npm and have an Ignite UI for Angular license, set up the Infragistics private feed to boost your productivity and use the full potential of Ignite UI for Angular.
Access Token Usage
También puede autenticarse en nuestro feed npm privado mediante un token de acceso, que puede adquirir a través de su cuenta de usuario infragistics.com. La autenticación con token de acceso es la alternativa preferida cuando se desea integrar un proceso de CI en un repositorio de acceso público que utiliza los paquetes con licencia Ignite UI for Angular.
La siguiente información trata sobre cómo configurar la autenticación en nuestro registro npm privado usando un token de acceso en la configuración local, los procedimientos de compilación de Azure Pipelines y el proceso de compilación de Travis CI:
- Genere un token desde https://account.infragistics.com/package-feeds
Note
Each token is Base64 encoded.
- Agregue lo siguiente a su archivo.npmrc
@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
Update azure-pipelines.yml with the following steps:
steps:
- script: npm config set @infragistics:registry $(npmRegistry)
displayName: 'Npm add registry'
- script: npm config set $(igScope):_auth=$(token)
displayName: 'Npm config auth'
Now, add variables for the npm registry, scope, and token. There are two ways to do so:
Define Variable Group from the Library page under Pipelines
Este artículo explica cómo utilizar un grupo de variables para almacenar valores que desea controlar y poner a disposición en múltiples canalizaciones.
Define the variables in the Pipeline Settings UI and reference them in your YAML file
En el caso más común, configura las variables y las usa dentro del archivo YAML.
Travis CI Configuration
Follow a similar approach here. The only difference is that the configuration is set in the before_install step:
before_install:
- echo "@infragistics:registry=https://packages.infragistics.com/npm/js-licensed/" >> ~/.npmrc
- echo "//packages.infragistics.com/npm/js-licensed/:_auth=$TOKEN" >> ~/.npmrc
La mejor manera de definir una variable de entorno depende del tipo de información que contendrá. Entonces tienes dos opciones:
- cifrelo y agréguelo a su .travis.yml
- agréguelo a la configuración de su repositorio
GitHub Actions Configuration
Add the following scripts before the npm install (or npm ci) step in 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 secretos (variables de entorno cifradas) y utilícelos en el flujo de trabajo de acciones de GitHub para información confidencial como el token de acceso.
GitHub