# Quick Installation

{% hint style="info" %}
You **don’t** need to install or configure tools like WebPack or CLI.\
They are configured and hidden so that you can focus on the code.
{% endhint %}

1. First of all, it's required to install [Node](https://nodejs.org/en/) and npm.
2. Update the latest [angular-cli](https://cli.angular.io/) global package to Angular 21+ with CLI 21.x.x
3. Unzip **berry-angular-v4.x.x.zip**, and you will find the `full-version`project folder.&#x20;
4. Open the terminal and navigate to the `full-version/`folder and **install the required node packages** using the following command

   ```shell
   npm i --legacy-peer-deps
   ```
5. To run the project **locally,** the following command will run the app in development mode. Open <http://localhost:4200> to view it in the browser.

   ```shell
   npm run start
   ```
6. The page will automatically reload if you make changes to the code.
7. Now you can use this Angular project for your application development and make the necessary changes.
8. To build the app for production, the following command will create the `dist/` folder inside this project directory.

   ```
   npm run build
   ```

{% hint style="success" %}
The project was built assuming it is hosted at the server root folder of the domain/platform\
i.&#x65;**`http://example.com`**

## or

to deploy a build for a sub-folder\
i.&#x65;**`http://example.com/folder-name`**

You also need to set **\<base href="/folder-name/">**
{% endhint %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://codedthemes.gitbook.io/berry-angular/quick-installation.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
