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

@parameter1/base-cms-newsletter-deployment-tool

v4.74.0

Published

The deployment tool for use with @parameter1/base-cms-marko-newsletters

Downloads

101

Readme

Newsletter Deployment Tool

To use the deployment tool with your @parameter1/base-cms-marko-newsletters project, include and modify (as appropriate) the files in the templates directory at the root of your project.

Dockerfile

The Dockerfile defines the production build process for your project. No modifications to this file should be necessary.

.travis.yml

The .travis.tml defines how your project should be deployed. Copy this file to your project, and update the deployment commands to deploy each tenant. You must include both the production and staging definition for each tenant, if you would like it to deploy to both stacks.

Ensure that you replace all references to TENANT_* with the appropriate values for your tenant.