{"id":4252,"date":"2020-09-02T23:18:54","date_gmt":"2020-09-02T23:48:54","guid":{"rendered":"https:\/\/ultering.com\/it4us\/?p=4252"},"modified":"2020-09-12T18:04:23","modified_gmt":"2020-09-12T18:34:23","slug":"angular-creating-a-local-installation-to-preserve-current-environment","status":"publish","type":"post","link":"https:\/\/ultering.com\/it4us\/?p=4252","title":{"rendered":"ANGULAR 10: Step One B – Creating A Local Installation To Preserve Current Environment"},"content":{"rendered":"

Back to index <\/a><\/p>\n

<Previous <\/a> Next ><\/a><\/span><\/p>\n

Code download<\/a><\/p>\n

<\/h1>\n
Usually, the tutorials show how to install  angular\/cli<\/em>  globally.<\/span><\/div>\n
<\/div>\n
It happens that sometimes our environment has already a previous installation different from the new one we desire to use for a new project.
\nFor instance, suppose that you’re working using the latest versions but you need to maintain an old project that was built using Angular 7.
\n<\/span>In this case, it is required to install the Angular 7  locally, isolating it from your global environment configuration.<\/span><\/div>\n
<\/div>\n
This example uses Angular 7 plus Bootstrap.
\nTo use other versions, just switch the version in the commands used in the example.<\/div>\n

The recipe:<\/p>\n

    \n
  1. Create a new folder for the new project.
    \nmkdir it4us_v7_demo
    \n<\/em><\/em>
    \nNOTE: Be really patient, the command will take some time to finish.
    \nTake advantage to grab your coffee, or better two or three!!