Clone GitLab Bundle

—

### ✅ Step 1: Find the GitLab Repo URL
Go to the GitLab project page for `myaccount-internet-overview` (the parent bundle) and copy the **repository URL**:

– For **HTTPS**:

https://gitlab.com/your-namespace/myaccount-internet-overview.git

– For **SSH** (if you use SSH keys):

git@gitlab.com:your-namespace/myaccount-internet-overview.git

> Make sure you're logged in to GitLab and have access rights to this project.

—

### ✅ Step 2: Open Terminal and Clone

Use this command in your terminal:

git clone https://gitlab.com/your-namespace/myaccount-internet-overview.git

Or with SSH:

git clone git@gitlab.com:your-namespace/myaccount-internet-overview.git

—

### ✅ Step 3: Navigate Into the Directory

After cloning:

cd myaccount-internet-overview

—

### ✅ Step 4: Check for Submodules (if it's a parent bundle)

If the bundle contains other submodules (like child modules), run:

git submodule update --init --recursive

This will pull in all submodules used by the parent bundle.

—

### ✅ Step 5: Done! You Now Have the Full Parent Bundle Locally

You can now:
– Explore the code
– Run local builds
– Create branches
– Start development

—

If you’re unsure of the GitLab URL or how to find it, paste your project link or share your GitLab structure, and I can give you the exact command.

—

### ✅ Check Node.js Version

node -v

or

node --version

📌 Example output:

v18.17.0

—

### ✅ Check npm Version

npm -v

or

npm --version

📌 Example output:

9.6.7

—

If you see an error like `command not found`, that means Node.js is not installed properly on your system.

Let me know if you're using Windows, macOS, or Linux — I can help you install or upgrade Node.js if needed.

—

### 🔍 What Are Repositories?

A **repository** (or **repo** for short) is a **storage space** for your project’s code and related files. It’s managed by a **version control system** like Git and can be **hosted online** using platforms like **GitLab**, **GitHub**, or **Bitbucket**.

—

### 🔧 Think of a Repository As:
> 🗂️ A **folder** that stores your project's files (HTML, CSS, JS, etc.)
> 🕓 + It **tracks every change** you or your team makes
> 🧑‍🤝‍🧑 + It **enables collaboration** among developers

—

### ✅ A Repository Includes:
– Source code files (e.g., `.js`, `.php`, `.py`)
– A history of commits (who changed what and when)
– Branches (parallel versions of your code)
– README file (documentation)
– Configuration files (e.g., `.gitignore`, `package.json`)
– Issues, merge requests, CI/CD pipelines (on GitLab/GitHub)

—

### 🔁 Local vs Remote Repositories
| Type | Description | Example |
|———-|——————————————–|———————————-|
| **Local** | Stored on your computer | Your project folder after `git clone` |
| **Remote** | Stored on GitLab, GitHub, etc. | `https://gitlab.com/user/project.git` |

—

### 👩‍💻 Example in Real Use:
You create a repo named `my-weather-app` → You write code → You push it to GitLab → Your teammate pulls the latest version and works on it too.

—

Let me know if you want to **create**, **clone**, or **push** a repository — I’ll guide you step-by-step!

—

### ✅ Basic NVM Commands

| Command | Description |
|——–|————-|
| `nvm –version` | Show installed version of `nvm` |
| `nvm ls` | List all Node versions installed locally |
| `nvm ls-remote` | Show all available Node.js versions from Node’s official site |
| `nvm install ` | Install a specific Node.js version (e.g., `nvm install 18`) |
| `nvm use ` | Switch to a specific version (e.g., `nvm use 18`) |
| `nvm uninstall ` | Remove an installed version |
| `nvm current` | Show the current active Node.js version |
| `nvm alias default ` | Set default Node version (used in new shells) |

—

### 🚀 Examples

nvm install 18
nvm use 18
nvm alias default 18
nvm ls

—

### 📌 Bonus

If you want to automatically use a specific Node version in a project folder:

1. Create a `.nvmrc` file in your project:

echo "18" > .nvmrc

2. Then in that folder:

nvm use

—

Let me know if `nvm` is not installed — I’ll help you install it depending on your OS (Windows/macOS/Linux).