# Nx Setup

## Nx Setup with a New Project

Creating an Nx workspace is done with a single command. Run the following command to set up an Nx workspace with a React app in it.

```bash
npx create-nx-workspace --preset=react
```

## Nx Setup with an Existing Project

If you have an existing Create React App project, you can gain the benefits of Nx's computation cache without modifying the file structure by running this command:

```bash
npx cra-to-nx
```

If you have an existing Lerna or Yarn workspaces repo, you can gain the benefits of Nx's computation cache without modifying the file structure by running this command:

```bash
npx add-nx-to-monorepo
```

For more information on adding Nx to an existing repository see the [migration guides](/{{framework}}/migration/overview)

## Configuration

Nrwl maintains plugins for [Jest](/{{framework}}/jest/overview), [Cypress](/{{framework}}/cypress/overview), [ESLint](/{{framework}}/linter/eslint) and [Storybook](/{{framework}}/storybook/overview), so these tools can be easily added to your repo without the initial cost of setting up configuration files. As new versions of these tools are released, [`nx migrate latest`](/{{framework}}/core-concepts/updating-nx) automatically updates your configuration files to work with the next version. There is a growing list of [community plugins](/nx-community) that support other tools.

Need to customize your configuration somehow? Configuration files can be modified for the whole repository or at an individual project level. For instance, `libA` has a `tsconfig.json` file that extends the global `tsconfig.base.json` file:

```treeview
myorg/
├── apps/
├── libs/
│   └── libA/
│       ├── src/
│       └── tsconfig.json
├── package.json
└── tsconfig.base.json
```

## Folder Structure

Every Nx workspace has a file structure similar to this:

```treeview
myorg/
├── apps/
├── libs/
├── tools/
├── workspace.json
├── nx.json
├── package.json
└── tsconfig.base.json
```

Nx helps split up your code into separate projects. Projects come in two varieties - applications and libraries.

`/apps/` contains the application projects. This is the main entry point for a runnable application. We recommend keeping applications as light-weight as possible, with all the heavy lifting being done by libraries that are imported by each application.

`/libs/` contains the library projects. There are many different kinds of libraries, and each library defines its own external API so that boundaries between libraries remain clear.

`/tools/` contains scripts that act on your code base. This could be database scripts, [custom executors](/{{framework}}/executors/creating-custom-builders) (or builders), or [workspace generators](/{{framework}}/generators/workspace-generators).

`/workspace.json` defines each project in your workspace and the executors that can be run on those projects.

`/nx.json` adds extra information about projects, including manually defined dependencies and tags that can be used to restrict the ways projects are allowed to depend on each other.

`/tsconfig.base.json` sets up the global TypeScript settings and creates aliases for each library to aid when creating TypeScript imports.
