Since Angular is based on TypeScript, it would be strange not to implement it. I think everyone who is interested in AngularJS to Angular migration has heard about this transition. If the dependency is difficult and takes up a lot of space, make it a local NPM package and append the relative URL to package.json (even without the conditions of publication in npm).
If the dependence itself is small and not very complicated, then turn it into a directive (believe me, this is a very good decision, you will not lose anything). There are also cases where dependencies can’t be replaced (usually because they are extremely outdated and widely used in the product). If certain dependencies are not readable and not suitable for NPM, I recommend conducting the research and finding a way to switch them. To do this, make a file package.json and move all dependencies in NPM. If you used to work with a bower to work with packages, it’s a perfect time for a change! I recommend you to have a Single Responsibility rule, as this will greatly simplify the AngularJS to Angular migration operation. The peculiarity of Angular is that each component of the code has its file. Since the Angular architecture is based on the use of components, this will be such a good solution for migration. Let’s start by modernization AngularJS to the newest version!
0 kommentar(er)
