### Install PHP and Node Dependencies (Shell)

Source: https://github.com/opcodesio/log-viewer/blob/main/CONTRIBUTING.md

These commands install the necessary dependencies for the Log Viewer project. `composer install` handles PHP dependencies, while `npm install` manages Node.js dependencies. These are crucial for the project to function correctly during development.

```shell
composer install
npm install
```

--------------------------------

### Install Log Viewer Package (Composer)

Source: https://github.com/opcodesio/log-viewer/blob/main/README.md

This command installs the Log Viewer package for your Laravel application using Composer. Ensure you have Composer installed and configured for your project.

```bash
composer require opcodesio/log-viewer
```

--------------------------------

### Publish Log Viewer Assets (Artisan)

Source: https://github.com/opcodesio/log-viewer/blob/main/README.md

After installing the Log Viewer package, this Artisan command publishes the necessary front-end assets (like CSS and JavaScript) to your Laravel project. This makes the Log Viewer UI accessible.

```bash
php artisan log-viewer:publish
```

--------------------------------

### Clone Log Viewer Repository (Shell)

Source: https://github.com/opcodesio/log-viewer/blob/main/CONTRIBUTING.md

This command clones the Log Viewer repository to your local machine and navigates into the project directory. Replace `<YOUR-USERNAME>` with your actual GitHub username. This is the first step in setting up a local development environment.

```shell
git clone https://github.com/<YOUR-USERNAME>/log-viewer.git && cd log-viewer
```

--------------------------------

### Build Production Assets (Shell)

Source: https://github.com/opcodesio/log-viewer/blob/main/CONTRIBUTING.md

This command compiles front-end assets (CSS and JavaScript) for production deployment. It optimizes files for smaller size and faster loading, which is a necessary step before committing front-end changes.

```shell
npm run production
```

--------------------------------

### Format Code and Run Tests (Shell)

Source: https://github.com/opcodesio/log-viewer/blob/main/CONTRIBUTING.md

These commands ensure code quality and functionality. `composer format` applies code formatting using Laravel Pint. `composer test` executes the Pest PHP unit and feature tests to verify that changes have not introduced regressions.

```shell
composer format
composer test
```

--------------------------------

### Watch and Publish Front-end Assets (Shell)

Source: https://github.com/opcodesio/log-viewer/blob/main/CONTRIBUTING.md

These commands are used for front-end development. `npm run watch` recompiles CSS and JavaScript files automatically as changes are made. `php artisan log-viewer:publish` publishes these assets to the Laravel application, with an optional `--watch` flag for continuous publishing.

```shell
npm run watch
php artisan log-viewer:publish
php artisan log-viewer:publish --watch
```

--------------------------------

### Configure Local Path Repository (JSON)

Source: https://github.com/opcodesio/log-viewer/blob/main/CONTRIBUTING.md

This JSON snippet demonstrates how to configure `composer.json` to use a local path for the Log Viewer package. This is useful for testing your modified version within a Laravel application without publishing to a package repository.

```json
// File: composer.json

{
  "scripts": { ... },

  "repositories": [
    {
      "type": "path",
      "url": "/home/myuser/projects/log-viewer"

    }
  ]
}
```

--------------------------------

### Create Feature Branch (Shell)

Source: https://github.com/opcodesio/log-viewer/blob/main/CONTRIBUTING.md

This command creates and switches to a new Git branch for your code contributions. It follows a convention of prefixing branch names with `feature-`, `fix-`, or `enhancement-` followed by a descriptive name, aiding in organization and tracking.

```shell
git checkout -b feature/feature-new_about_page
```

--------------------------------

### Commit Changes (Shell)

Source: https://github.com/opcodesio/log-viewer/blob/main/CONTRIBUTING.md

This command commits your staged code changes to your local Git repository. It's important to use short, descriptive commit messages that clearly explain the nature of the changes made.

```shell
git commit -m "adds route for about page"
```

=== COMPLETE CONTENT === This response contains all available snippets from this library. No additional content exists. Do not make further requests.