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 🙏

© 2026 – Pkg Stats / Ryan Hefner

abw-strapi-next-starter

v1.0.14

Published

CLI to bootstrap Strapi + Next.js projects with optional Heroku pipelines and AWS S3 setup

Downloads

1,159

Readme

🚀 abw-strapi-next-starter

CLI to quickly bootstrap a fullstack project with:

  • ⚙️ Strapi (Backend)
  • Next.js (Frontend)
  • ☁️ Heroku deployment (optional)
  • 🪣 AWS S3 upload support (optional)

📦 Installation

Option 1: Use without installing (recommended)

npx abw-strapi-next-starter create my-app

Option 2: Install globally

npm install -g abw-strapi-next-starter

Then:

abw-strapi-next-starter create my-app

🚀 Usage

Create a new project

abw-strapi-next-starter create my-app

or simply:

abw-strapi-next-starter my-app

⚙️ What it does

  • Creates a full project structure:

    • /backend → Strapi (TypeScript)
    • /frontend → Next.js
  • Initializes Git repositories

  • Configures environment variables

  • Optionally sets up:

    • AWS S3 uploads
    • Heroku deployment

☁️ Deployment

During setup, you will be asked:

  • Whether to deploy to Heroku
  • Whether to use pipelines
  • App names for backend and frontend
  • Login confirmation for the Heroku account in use

Or deploy later:

abw-strapi-next-starter publish my-app

🚀 Heroku Deployment Modes

The CLI supports two Heroku deployment modes:

1. Simple deploy

Creates:

  • 1 backend app
  • 1 frontend app

Example:

my-app-api
my-app-web

Use this mode if you want a straightforward Heroku deploy without staging and production separation.


2. Pipelines deploy

Creates:

  • 2 backend apps
    • my-app-api-stage
    • my-app-api-prod
  • 2 frontend apps
    • my-app-web-stage
    • my-app-web-prod
  • 2 pipelines
    • backend pipeline
    • frontend pipeline

Use this mode if you want staging + production environments.


🔁 Environment mapping (pipelines mode)

| Environment | Backend | Frontend uses | | ----------- | -------------- | --------------- | | Staging | API Stage | API Stage | | Production | API Production | API Production |


🔄 Deploy flow

When you choose Heroku deploy, the CLI will ask:

Do you want to use pipelines (staging + production)?

If you answer No

The CLI will:

  1. Create 1 backend app
  2. Create 1 frontend app
  3. Configure environment variables
  4. Deploy both apps

If you answer Yes

The CLI will:

  1. Create 4 Heroku apps
  2. Create 2 pipelines
  3. Attach apps to staging and production
  4. Configure environment variables
  5. Deploy to both environments

📦 Naming defaults

Simple mode

my-app-api
my-app-web

Pipelines mode

my-app-api-stage
my-app-api-prod
my-app-web-stage
my-app-web-prod

🪣 AWS S3 Support

If enabled, the CLI will:

  • Install the S3 upload provider

  • Configure:

    • plugins.ts
    • middlewares.ts
    • server.ts
  • Ask for:

    • Bucket name
    • Region
    • Access key
    • Secret
  • Automatically configure Heroku environment variables


⚠️ S3 Bucket Configuration (IMPORTANT)

For image uploads to work correctly, your S3 bucket must allow public read access.


1. Block Public Access

Go to:

S3 → Your Bucket → Permissions → Block public access

Configure:

  • ❌ Do NOT block all public access
  • ✔ Allow public access (at least partially)

If everything is blocked, images will not load in the browser.


2. Object Ownership (ACLs)

Go to:

S3 → Your Bucket → Permissions → Object Ownership

Set:

  • ✔ ACLs enabled

This is required because Strapi uploads files using:

ACL: 'public-read'

🔓 What this means

  • Uploaded images will be publicly accessible via URL:
https://your-bucket.s3.region.amazonaws.com/image.jpg
  • Only your backend (using AWS credentials) can:

    • upload
    • delete
    • modify files

🔐 Is this secure?

Yes — this is standard practice for most web apps.

As long as you:

  • ❌ do NOT expose your AWS credentials
  • ✔ use restricted IAM permissions

your setup is safe.


🚀 Advanced (optional)

For more advanced setups, you can later switch to:

  • CloudFront (CDN)
  • Private buckets + signed URLs
  • Bucket policies instead of ACLs

🧠 Summary

| Feature | Supported | | ---------------------- | --------- | | Simple Heroku deploy | ✔ Yes | | Pipelines deploy | ✔ Yes | | AWS S3 uploads | ✔ Yes | | Local-only setup | ✔ Yes |


🔐 Requirements

Make sure you have installed:

  • Node.js (>= 18)
  • npm
  • Git
  • Heroku CLI

🧪 Local Development

Backend

cd backend
npm run develop

Frontend

cd frontend
npm run dev

📁 Project Structure

my-app/
├── backend/
├── frontend/
└── .abw-starter.json

🔄 Updating

If installed globally:

npm update -g abw-strapi-next-starter

🐛 Troubleshooting

Heroku app name already taken

The CLI will automatically:

  1. Try your chosen name
  2. Try a random suffix
  3. Fall back to a Heroku-generated name

Wrong Heroku account selected

Before deployment, the CLI shows the current Heroku account and asks whether you want to continue with it.


Not logged into Heroku

The CLI will prompt you to log in automatically.


Images not loading (S3)

Check:

  • Bucket is not fully blocking public access
  • ACLs are enabled
  • Correct bucket name and region

📄 License

MIT


👨‍💻 Author

Built with ❤️ by ABWorks