---
title: 🟢 Module to Standalone
description: Challenge 31 is about migrating a module based application to a standalone application.
sidebar:
  order: 31
---

:::note
WIP: The following documentation will be reviewed and improved. However, you can still take on the challenge. If you don't understand a certain part, please feel free to reach out or create an issue.
:::

<div class="chip">Challenge #31</div>

## Information

In v14, standalone components were released and made stable in v15. If you haven't played with them, it's never too late. You can try them out in this challenge.

Moreover, the goal is to see how Nx and standalone components work together, and experience the process of decoupling your app with Nx lib and standalone components.

Finally, standalone components are very simple to understand, but routing/lazy-loaded components can be a bit harder to grasp. This challenge will allow you to manipulate components at different levels of nesting and work with lazy loaded routes.

After completing this challenge, standalone components will no longer hold any secrets for you.

## Statement

The goal of this challenge is to migrate your application from module based components to standalone components.

---

:::note
Start the project by running: `npx nx serve module-to-standalone`.
:::

:::tip[Reminder]
Your PR title must start with <b>Answer:31</b>.
:::

<div class="article-footer">
  <a
    href="https://github.com/tomalaforge/angular-challenges/pulls?q=label%3A31+label%3Aanswer"
    alt="Module to Standalone community solutions">
    ❖ Community Answers
  </a>
  <a
    href='https://github.com/tomalaforge/angular-challenges/pulls?q=label%3A31+label%3A'
    alt="Module to Standalone solution author">
    ▶︎ Author Answer
  </a>
  </div>
