Let's create a standard Angular CLI application with a few libraries.

ng new application-name
cd application-name/
yarn install
ng g lib libraryA
ng g lib libraryB
ng g lib libraryC

This set of commands should create a simple Angular CLI application with three libraries.
If you list files, you should get something similar to the structure below.

README.md
angular.json
node_modules/
package.json
projects/
src/
tsconfig.app.json
tsconfig.json
tsconfig.spec.json
yarn.lock

If, at this point, you still need to install NX, let's do it.
You may need to use 

 in front of the command. It depends on your 

 command that will interactively navigate you through the migration process.

You'll be asked which targets are cacheable.
It's recommended not to cache the 

 target, which is used during development.
When you write the code, you don't want to manually clear your browser cache, etc.

The next question, similar to creating a new empty NX mono repository, is about the distributed caching feature.
Please remember that this option strictly depends on your organization's privacy policy, so ensure you can use it.

After migration, your file structure should appear in the text snipped below.

README.md
node_modules/
nx.json
package.json
project.json
projects/
src/
tsconfig.app.json
tsconfig.json
tsconfig.spec.json
yarn.lock

---
title: Automatic migration of existing applications
description: How to automatically migrate simple applications to the NX mono repository
code: https://gitlab.com/fullstackio/books/newline-course-apps/building-angular-applications-with-nx-app/-/tree/main/manuscript/code/06.02-automatic-migration?ref_type=heads
privateVideoUrl: https://stream.mux.com/DwfU1GEmPehpE6ZAR2LCg00bNEypvYGIpFtKVlChze8E.m3u8
---

## How to perform automatic migration

Let's create a standard Angular CLI application with a few libraries.

```bash
ng new application-name
cd application-name/
yarn install
ng g lib libraryA
ng g lib libraryB
ng g lib libraryC
```

This set of commands should create a simple Angular CLI application with three libraries.
If you list files, you should get something similar to the structure below.

```text
README.md
angular.json
node_modules/
package.json
projects/
src/
tsconfig.app.json
tsconfig.json
tsconfig.spec.json
yarn.lock
```

If, at this point, you still need to install NX, let's do it.
You may need to use `sudo` in front of the command. It depends on your `npm` and `node` installation.

```bash
npm install --global nx@latest
```

Now, you're ready to execute the `init` command that will interactively navigate you through the migration process.

![nx init](https://d2uusema5elisf.cloudfront.net/courses/building-angular-applications-with-nx/module_07/lesson_07.02/public/images/06-02-01.png)

You'll be asked which targets are cacheable.
It's recommended not to cache the `serve` target, which is used during development.
When you write the code, you don't want to manually clear your browser cache, etc.

The next question, similar to creating a new empty NX mono repository, is about the distributed caching feature.
Please remember that this option strictly depends on your organization's privacy policy, so ensure you can use it.

After migration, your file structure should appear in the text snipped below.

```text
README.md
node_modules/
nx.json
package.json
project.json
projects/
src/
tsconfig.app.json
tsconfig.json
tsconfig.spec.json
yarn.lock
```

The biggest changes are:

-   `angular.json` changed into `project.json`
-   `nx.json` was created

Even when you check `git status`, it won't show you many changes.

```text
Changes not staged for commit:
  (use "git add/rm <file>..." to update what will be committed)
  (use "git restore <file>..." to discard changes in working directory)
	deleted:	angular.json
	modified:   package.json
	modified:   yarn.lock

galczo5

How to automatically migrate simple applications to the NX mono repository

Automatic migration of existing applications

In this lesson, you will learn how automatic migration to NX-Monorepo works for

So let's start by creating a brand new Angular application. I will use Angular

a new app, I will install all the dependencies, and then I will add three

and C. All the comments that I'm going to execute, you can see on the screen at

Options that I choose here are not that important because automatic migration

options. So let's select CSS and now we don't want SSR. All right, so app has

I entered application name of my application directory, I've run yarn install

the dependencies. Now let's add three libraries. So first one is library A, it

to install it. The second is library B and library C is the last one. So at the

standard Angular CLI application generated with ng comment. So if we try to

directories here, you will find that we have read me and denote modules, and

have as our C and projects. And all libraries live in projects. So if we go to

list it, as you can see, we have our free libraries. So let's run git in here

GitHub repository. And let's execute git status to list all untracked files.

everything to my git repository as a starting point that we always can revert

So git add everything git comment, minutes message, empty, angular app. All

angular application generated with standard ng comment. So now let's use

to migrate it to nx monorepo. To do this, you need to install nx globally. And

it installed at the moment. If you don't have it, you have to run npm install -

at latest, if you want to have the latest version. In some configurations of

you will need to add sudo in front of the command. So we have empty Angular

our nx installed globally. Let's run automatic regression. To do this, you need

command nx in it. And nx will ask you which targets should be cached at all. In

it's built in tests. I don't want to cache for serve and the second one. So let

the selected build and test. The second question, as always, is about nx cloud.

it? Let's say yes. And that's all. So if you want to use automatic migration in

all you need to do is to have a standard ngcli application and run nx in it. It

for small and medium applications. So let's check what has changed in my

status. And we have lists of all the files that has changed. The most important

Angular JSON. It was replaced by project JSON. Every library has its own

have in nx model repo. And xdjson file has been added. So you know that you

model repo. Let's list all the files and let's check how it looks like after

So you may wonder why we don't have that apps, leaps and tools, their stories.

automatic migration doesn't change your folder structure. It will try to keep

for the structure that you had before migration. And that's nice because you

new stuff. So it has some pros and cons, right? And the second difference is

end to end project for your application. One of the most important features of

with all tools preconfigured. And in this case, you have only things that you

before migration. Now we are going to reset changes in our Git repository. And

comment with additional comments. So git reset minus minus heart. And if we run

see that we have only additional files. We don't have any changes. So let's

running these two comments, we have everything as we had before migration. So

with two additional flags. First one is called add e to e. And the second one

integrated. So with these comments, with these two additional flags, add e to e

we should get our application migrated with end to end tests and unit tests

So let's run git status to check what has changed. All right. So as you can see

deleted files. We have our, of course, we have our angular JSON 5 deleted, we

deleted, and then added as leaps and apps. So it's closer to menorepos that we

lessons. To sum up, as you can see, automatic migration is a useful tool that

game changer for small or medium applications. You can migrate it up to nx mon

Learn

The newline Guide to Building Your First GraphQL Server with Node and TypeScript

Teach

Amelia Wattenberger

Author of Fullstack D3

Community

Masterclasses

Tutorials

Fullstack React with TypeScript