@lform/pretty-code NPM

Pretty Code

Pretty Code is a githook-driven collection of linter & formatter configurations for PHP, CSS, HTML, and JavaScript. It is also designed for per-project customization, which is useful when dealing with older, unconventional, or problematic code bases.

When this package is updated, running composer update or npm update will pull in the latest configuration changes, minus anything you've overridden in your project. This allows for easy updates to the configuration without having to manually update files.

Requirements

Environments: OSX, Linux, WSL
PHP 7.4+
Node 20+

Installation

IMPORTANT: The NPM part of the package must be installed to use the githook-driven linters and formatters. That is the case for PHP as well, regardless of whether you are using the Composer package.

This package is designed to work in Linux and OSX environments. Windows is not supported at this time.

NPM Installation

This installs the frontend part of the package as well as the githook-driven automations.

npm install --save-dev @lform/pretty-code

Composer Installation

This installs the PHP part of the package.

composer require --dev lform/pretty-code

Laravel & PHPStan

For Laravel based projects, install Larastan, which will configure PHPStan for use in Laravel projects.

Larastan Documentation & Repo

Installing Larastan

Install Larastan (refer to documentation) via Composer
Create a phpstan.neon file in the project root or copy the one from pretty-code
Edit the .lintstagedrc.json file and remove the preset configuration path from phpstan, so it uses the project root configuration by default.
Add the larastan extension to the phpstan.neon file in the project root:
includes: - vendor/larastan/larastan/extension.neon

Initialization

Once the packages are installed, the package has to be initialized via npm to do a few things:

Copy a .lintstagedrc.json config to the project root, if it does not already exist
Copy a preconfigured .githooks directory to the project root to trigger the git automations. If the directory already exists, the initialization script will not overwrite it.
Copy a .editorconfig config to the project root, if it does not already exist
Configure the project git repo core.hooksPath to use the new .githooks directory.
Add new scripts in package.json to run the linters and formatters manually.

For Composer, initialization will just add the new scripts to composer.json to run the linters and formatters manually.

Afterward, these new files & changes should be committed to git once everything is confirmed working. Read below for how to initialize the package.

NPM Initialization

npx pretty-code init

Composer Initialization

vendor/bin/pretty-code init

Troubleshooting

PHPStan Pains

PHPStan is very helpful but can be a source of aggravation on projects that have an older code-base or used unconventional approaches. There are a few things that can be done to address these issues:

If it's a Laravel project, install Larastan (instructions are above)
Exclude files from reporting in the configuration or with inline comments. For errors that should be ignored, add them to the configuration.
Lower the reporting level in the configuration
Generate a baseline report, so you can focus on new code instead of trying to fix old code. Commit the baseline report to the project repo.

If all else fails, PHPStan can be disabled but this should be avoided except when necessary.

Disconnecting & Reconnecting the Automations

If you're having problems with the automated git hooks and need to disable or re-enable them:

# Disable automations, set the git hooks to the default:
git config core.hooksPath ".git/hooks"

# Re-enable automations, set the git hooks to our custom hooks directory:
git config core.hooksPath ".githooks"

OS Issues

NOTE: On OSX, you may also need to install coreutils since the initialization scripts use the realpath command. If you see errors related to this, run the following:

brew install coreutils

Uninstalling

To remove the package:

Delete any custom linter or formatter configs from the project root
Delete the .githooks directory
Run git config core.hooksPath .git/hooks
Run npm remove @lform/pretty-code
Run composer remove lform/pretty-code
Remove the pretty scripts from composer.json and package.json

Linters & Formatters

Linters

Formatters

PHP CS Fixer
- Configured for PHP 8.3, for 7.4 support, copy the configuration into your project and customize it.
Prettier

Supported File Types

L = Linted, F = Formatted

antlers.html (F)
antlers.php (F)
blade.php (F)
css (LF)-
html, htm (LF)
js (LF)
jsx (LF)
json (F)
pcss (LF)
php (LF)
scss (LF)
ts (LF)
tsx (LF)
twig (F)
yaml, yml (LF)

Commands

Formatters

# Runs Prettier (css, scss, pcss, js, jsx, ts, tsx, json, html, htm, twig, blade.php, yml, yaml)
npm run pretty:format <path>

# Runs PHP-CS-Fixer (php)
composer pretty:format <path>

Linters

# Runs StyleLint (css, scss, pcss)
npm run pretty:lint:css <path>

# Runs ESLint (js, jsx, ts, tsx, json)
npm run pretty:lint:js <path>

# Runs linthtml (html, htm)
npm run pretty:lint:html <path>

# Runs PHPStan (php)
composer pretty:lint <path>

Customization Per Project

To customize the linters and formatters per project:

Copy the specific configuration files that need to be modified from the Pretty Code package root to the project root. Only copy the configurations that you need, these custom configs will no longer get updated via the package management system.
Modify the copied configuration files as needed.
Open the .lintstagedrc.json file and remove the explicit config-file paths or ignore-file paths from the respective linters or formatters being adjusted.
Do the same thing for the package.json and composer.json scripts as applicable.
The linters and formatters with project-based configs will automatically use the configuration files from the project root directory.

To undo these changes, just delete the configurations and restore the original scripts by referencing the package's package.json and composer.json files.