PHPackages                             nrel/eom-project - 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. [Framework](/categories/framework)
4. /
5. nrel/eom-project

ActiveProject[Framework](/categories/framework)

nrel/eom-project
================

Project template for Drupal 8 sites built with the Eom Lightning sub-profile distribution.

1.0.4(8y ago)045GPL-2.0+PHP

Since Sep 8Pushed 8y ago2 watchersCompare

[ Source](https://github.com/NREL/eom-project)[ Packagist](https://packagist.org/packages/nrel/eom-project)[ Docs](https://github.com/NREL/eom-project)[ RSS](/packages/nrel-eom-project/feed)WikiDiscussions master Synced 3d ago

READMEChangelogDependencies (19)Versions (5)Used By (0)

This is a Composer-based installer for the [Eom](https://github.com/NREL/profile-eom) sub-profile based on the [Lightning](https://www.drupal.org/project/lightning) Drupal distribution. Welcome to the future!

Get Started
-----------

[](#get-started)

```
$ composer create-project NREL/eom-project MY_PROJECT

```

Composer will create a new directory called MY\_PROJECT containing a `docroot` directory with a full Lightning code base therein. You can then install it like you would any other Drupal site.

Maintenance
-----------

[](#maintenance)

`drush make`, `drush pm-download`, `drush pm-update` and their ilk are the old-school way of maintaining your code base. Forget them. You're in Composer land now!

Let this handy table be your guide:

TaskDrushComposerInstalling a contrib project (latest version)`drush pm-download PROJECT``composer require drupal/PROJECT`Installing a contrib project (specific version)`drush pm-download PROJECT-8.x-1.0-beta3``composer require drupal/PROJECT:1.0.0-beta3`Updating all contrib projects and Drupal core`drush pm-update``composer update`Updating a single contrib project`drush pm-update PROJECT``composer update drupal/PROJECT`Updating Drupal core`drush pm-update drupal``composer update drupal/core`The magic is that Composer, unlike Drush, is a *dependency manager*. If module `foo version: 1.0.0` depends on `baz version: 3.2.0`, Composer will not let you update baz to `3.3.0` (or downgrade it to `3.1.0`, for that matter). Drush has no concept of dependency management. If you've ever accidentally hosed a site because of dependency issues like this, you've probably already realized how valuable Composer can be.

But to be clear: it is still very helpful to use a site management tool like Drush or Drupal Console. Tasks such as database updates (`drush updatedb`) are still firmly in the province of such utilities. This installer will install a copy of Drush (local to the project) in the `bin` directory.

### Specifying a version

[](#specifying-a-version)

you can specify a version from the command line with:

```
$ composer require drupal/:

```

For example:

```
$ composer require drupal/ctools:3.0.0-alpha26
$ composer require drupal/token:1.x-dev

```

In these examples, the composer version 3.0.0-alpha26 maps to the drupal.org version 8.x-3.0-alpha26 and 1.x-dev maps to 8.x-1.x branch on drupal.org.

If you specify a branch, such as 1.x you must add -dev to the end of the version.

**Composer is only responsible for maintaining the code base**.

Source Control
--------------

[](#source-control)

If you peek at the `.gitignore` we provide, you'll see that certain directories, including all directories containing contributed projects, are excluded from source control. This might be a bit disconcerting if you're newly arrived from Planet Drush, but in a Composer-based project like this one, **you SHOULD NOT commit your installed dependencies to source control**.

When you set up the project, Composer will create a file called `composer.lock`, which is a list of which dependencies were installed, and in which versions. **Commit `composer.lock` to source control!** Then, when your colleagues want to spin up their own copies of the project, all they'll have to do is run `composer install`, which will install the correct versions of everything in `composer.lock`.

###  Health Score

28

—

LowBetter than 54% of packages

Maintenance20

Infrequent updates — may be unmaintained

Popularity6

Limited adoption so far

Community7

Small or concentrated contributor base

Maturity66

Established project with proven stability

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 ~3 days

Total

5

Last Release

3158d ago

### Community

Maintainers

![](https://www.gravatar.com/avatar/399d67b5f044fadc29d052caa6cf1e0d43250dac95c1d0167dcecadb90698ba7?d=identicon)[nomad](/maintainers/nomad)

###  Code Quality

TestsPHPUnit

### Embed Badge

![Health badge](/badges/nrel-eom-project/health.svg)

```
[![Health](https://phpackages.com/badges/nrel-eom-project/health.svg)](https://phpackages.com/packages/nrel-eom-project)
```

###  Alternatives

[drupalwxt/wxt

Project template for Drupal 10 sites built with the WxT distribution.

29159.8k8](/packages/drupalwxt-wxt)

PHPackages © 2026

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