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

malley-prairie

v0.0.2

Published

made with love and:

Downloads

2

Readme

Malley prairie

made with love and:

Codeship Statuses :

Codeship Status for antistatique/malley-prairie

🔧 Prerequisites

First of all, you need to have the following tools installed globally on your environment:

  • composer

don't forget to add bins to your path such:

  • php
  • mysql

🚛 Install

Wordpress and dependencies

  1. Setup your .env file with database access and environment variables. You can find our ACF PRO key on 1Password.

  2. Setup your virtualhost (like http://website.test) to serve /web.

  3. Install Wordpress and dependencies using composer

composer install
  1. Install and configure PHPCS for coding standards, see this section.

Styleguide

  • serve your project : $ yarn start
  • build your project : $ yarn build
  • deploy your gh-pages : $ yarn deploy
  • publish your frontend build : $ sh ./publish.sh VERSION<0.0.0> ON_NPM<true>
  • publish your development frontend build : $ sh ./publish_dev.sh

🚀 Deploy

First time

# You need to have ruby & bundler installed
$ bundle install
$ npm install -g yarn

How it works

There are 4 websites (fmp, cmp, cve, cpale).

We use Capistrano to deploy:

bundle exec cap -T

Example Malleyprairie (fmp).

bundle exec cap fmp-staging deploy
bundle exec cap fmp-prodution deploy

🚔 Check Wordpress coding standards & best practices

phpcs

You need to run composer before using PHPCS. Then register the Wordpress and WordpressPractice Standard with PHPCS:

$ vendor/bin/phpcs --config-set installed_paths wpcs

Command Line Usage

Check Wordpress best practices:

$ vendor/bin/phpcs --standard=WordPress --colors --extensions=php,module,inc,install,test,profile,theme,css,info,txt,md web/app/themes/malley-prairie/resources

Automatically fix coding standards

$ vendor/bin/phpcbf --standard=Wordpress --colors --extensions=php,module,inc,install,test,profile,theme,css,info,txt,md ./web/app/themes/malley-prairie/resources --ignore=web/app/themes/malley-prairie/resources/functions.php,web/app/themes/malley-prairie/resources/index.php

Enforce code standards with git hooks

Maintaining code quality by adding the custom post-commit hook to yours.

$ cat ./scripts/hooks/post-commit >> ./.git/hooks/post-commit

🕙 Crons

Crontab

🔐 Security