PHPackages                             burdamagazinorg/thunder-dev-tools - PHPackages - PHPackages  [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register)

1. [Directory](/)
2. /
3. [Utility & Helpers](/categories/utility)
4. /
5. burdamagazinorg/thunder-dev-tools

ActiveLibrary[Utility & Helpers](/categories/utility)

burdamagazinorg/thunder-dev-tools
=================================

Developer tools for Thunder distribution

1.0.1(7y ago)535.4k—6.1%110GPL-2.0+Shell

Since Jul 17Pushed 7y ago4 watchersCompare

[ Source](https://github.com/BurdaMagazinOrg/thunder-dev-tools)[ Packagist](https://packagist.org/packages/burdamagazinorg/thunder-dev-tools)[ RSS](/packages/burdamagazinorg-thunder-dev-tools/feed)WikiDiscussions master Synced 2d ago

READMEChangelog (2)Dependencies (1)Versions (3)Used By (10)

Thunder Development Tools
=========================

[](#thunder-development-tools)

---

Code Style Guidelines
---------------------

[](#code-style-guidelines)

Thunder code style guidelines are in agreement with Drupal code styles. For general validation of files is used [Drupal Coder](https://www.drupal.org/project/coder). More detailed validation of JavaScript code is made by [ESLint](http://eslint.org/) with predefined [Drupal settings](https://www.drupal.org/node/1955232).

#### Drupal Coder

[](#drupal-coder)

In order that Drupal Coder works, following steps should be executed.

1. Install Composer (\* this step can be skipped if composer already exists on system)

- Please follow [guide](https://getcomposer.org/download/) on official page

2. Install Drupal/Coder in global Composer directory

- Please follow [installation guide](https://packagist.org/packages/drupal/coder) on Packagist

Usage from command line:

```
# check Code for Drupal coding standards
phpcs --standard=Drupal --extensions=php,module,inc,install,test,profile,theme '--ignore=*.md' -p

# autocorrect code for Drupal coding standards
phpcbf --standard=Drupal --extensions=php,module,inc,install,test,profile,theme '--ignore=*.md'
```

Additionally both commands can be used with option `--standard=DrupalPractice` for checking defined Drupal best practices.

#### ESLint

[](#eslint)

In order that ESLint works, following steps should be executed

1. Install Node.js (\* this step can be skipped if Node.js already exists on system)

- Official [guide](https://nodejs.org/en/download/package-manager/) from Node.js page should be followed

2. Install ESLint

```
npm install -g eslint
```

Usage from command line:

```
eslint
```

#### Thunder Guidelines Checker

[](#thunder-guidelines-checker)

This script is provided by Thunder Development Tools. It's wrapper for phpcs and eslint tools.

To initialize project with requirements execute:

```
vendor/bin/check-guidelines.sh --init
```

Please take in consideration that `vendor/bin` path could be customized in your root composer.json file.

Then some basic options for checking of code style guidelines can be used:

```
-cs, --phpcs            use PHP Code Sniffer with Drupal code style standard
-js, --javascript       use ESLint with usage of project defined code standard
-ac, --auto-correct     apply auto formatting with validation of code styles
```

For example to check and correct php and javascript files with auto correction:

```
vendor/bin/check-guidelines.sh --phpcs --javascript --auto-correct
```

---

Integrate Code Style checking in PHPStorm
-----------------------------------------

[](#integrate-code-style-checking-in-phpstorm)

#### Drupal Coder

[](#drupal-coder-1)

1. In PHPStorm preferences search for: `Code Sniff`
2. Select option `Languages & Frameworks | PHP | Code Sniffer`
3. Open configuration dialog by pressing edit button \[...\]
4. In Configuration dialog add new configuration or edit existing **Local**. Set correct path for **phpcs** by pressing edit button \[...\]. Path should be: `/vendor/bin/phpcs` and save that settings for Code Sniffer
5. To configure usage of PHP Code Sniffer select `Editor | Inspections`
6. Option **PHP Code Sniffer validation** should already be filtered by Search. Enable that option.
7. And for that validation procedure change **Coding standard** option to **Drupal**. (\* sometimes PHPStorm doesn't recognize that coding standard has been changed if **Drupal** is preselected. It's sufficient just to select other coding standard and then put back to **Drupal**)

After these settings are saved in PHPStorm warnings with prefix **phpcs:** will be displayed in editor.

#### ESLint

[](#eslint-1)

1. In PHPStorm preferences search for: `ESLint`
2. Select option `Languages & Frameworks | JavaScript | Code Quality Tools | ESLint`
3. Enable it

Default settings can be preserved. ESLint will automatically search for installed `eslint` command and also coding style configuration files from project will be used.

---

Git Hooks
---------

[](#git-hooks)

#### Git Pre Commit Hook

[](#git-pre-commit-hook)

To check is code valid before commit, git pre commit hook can be used with execution of thunder guideline checker script. Create script file `.git/hooks/pre-commit` in your project folder, with following content:

```
#!/bin/sh
vendor/bin/check-guidelines.sh --phpcs --javascript
```

Make sure that the file is executable. That will automatically validate files before commit and display possible problems and additionally commit will not be executed unless everything is correct and valid.

###  Health Score

37

—

LowBetter than 81% of packages

Maintenance20

Infrequent updates — may be unmaintained

Popularity32

Limited adoption so far

Community23

Small or concentrated contributor base

Maturity64

Established project with proven stability

 Bus Factor1

Top contributor holds 57.1% of commits — single point of failure

How is this calculated?**Maintenance (25%)** — Last commit recency, latest release date, and issue-to-star ratio. Uses a 2-year decay window.

**Popularity (30%)** — Total and monthly downloads, GitHub stars, and forks. Logarithmic scaling prevents top-heavy scores.

**Community (15%)** — Contributors, dependents, forks, watchers, and maintainers. Measures real ecosystem engagement.

**Maturity (30%)** — Project age, version count, PHP version support, and release stability.

###  Release Activity

Cadence

Every ~86 days

Total

2

Last Release

2823d ago

### Community

Maintainers

![](https://www.gravatar.com/avatar/dfe90fee04d5ef4d2bd1ea46dc65f6aec95b2486e2ce47f3439b3e06eb2f37dd?d=identicon)[dbosen](/maintainers/dbosen)

---

Top Contributors

[![mtodor](https://avatars.githubusercontent.com/u/3965286?v=4)](https://github.com/mtodor "mtodor (8 commits)")[![dbosen](https://avatars.githubusercontent.com/u/6398151?v=4)](https://github.com/dbosen "dbosen (3 commits)")[![chrfritsch](https://avatars.githubusercontent.com/u/731161?v=4)](https://github.com/chrfritsch "chrfritsch (2 commits)")[![alexpott](https://avatars.githubusercontent.com/u/769634?v=4)](https://github.com/alexpott "alexpott (1 commits)")

### Embed Badge

![Health badge](/badges/burdamagazinorg-thunder-dev-tools/health.svg)

```
[![Health](https://phpackages.com/badges/burdamagazinorg-thunder-dev-tools/health.svg)](https://phpackages.com/packages/burdamagazinorg-thunder-dev-tools)
```

###  Alternatives

[drupal/core-dev

require-dev dependencies from drupal/drupal; use in addition to drupal/core-recommended to run tests from drupal/core.

2022.6M344](/packages/drupal-core-dev)[ec-europa/toolkit

Toolkit packaged for Drupal projects based on Robo.

40252.8k34](/packages/ec-europa-toolkit)[drupol/drupal-conventions

Drupal conventions for coding.

2422.7k1](/packages/drupol-drupal-conventions)[wingsuit-designsystem/wingsuit-kickstarter

Starterkit for Wingsuit and Layout Builder.

131.2k](/packages/wingsuit-designsystem-wingsuit-kickstarter)

PHPackages © 2026

[Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)