.npmrc
-file or with npm install
command. legacy-peer-deps
flag – this step cannot be skipped, but you should be ready to make some additional manual efforts to resolve all transitive peer dependencies. See this guide from Troubleshooting section.
This release introduces a lot of breaking changes. We put in a lot of effort to make updating easier for you. We wrote a bunch of schematics that automatically go through your entire project and fix most of the breaking changes.
// TODO: (Taiga UI migration)
). In most cases these comments contains instructions how to manually migrate some deleted entities by new alternative. @taiga-ui/legacy
. This package is a transitional state for many outdated entities before their full removal. Everything you find inside this package in the fourth major release will be removed in the fifth one. So, you can just continue to use them for a while. However, some of those components already have modern alternatives – they will be marked by comment with @deprecated
tag (most IDEs displays the such entities as stricken-through). We strongly recommend to replace them by new alternatives as soon as possible!