npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

drupal-composer

v1.0.1

Published

Converts a Drupal project that hasn't used composer to manage modules from the start to use the drupal-composer project's composer file

Downloads

7

Readme

Drupal 8 Composer Helper

This module's primary function will combine modules that were added to the Drupal composer file and those that were installed manually or via Drush to the modules directory. It then pulls templates from the Drupal Composer project as a base to build the new installation. Reference that project's homepage for additional information on managing your project with composer moving forward.

I originally created this because my agency used drush to install modules on a few sites only to realize afterwards that we were doing it wrong! Rather than catalog the modules individually I figured I'd write some node (my favorite DevOps tool) to solve the problem.

It assumes you have a repo structure similar to:

app
--composer.json
--modules
----contrib
----custom
...etc...

*where app contains the Drupal installation

To start install the module globally:
npm install -g drupal-composer

Enter the root of a project and run the module:
drupal-composer