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

laravel-template-jpz

v1.0.2

Published

Scaffold a Laravel framework template with Blade, Vite, Tailwind CSS, SQLite defaults, and a health-check API.

Readme

Laravel Framework Template CLI tool

laravel-template-jpz is a CLI tool that creates a ready-to-use Laravel framework template.

Instead of manually creating the same Laravel folders, setup files, routes, assets, migrations, and tests every time you start a new project, you can run one command and get a clean application structure.

It generates a Laravel framework application with:

  • Laravel 12
  • Blade views
  • Vite
  • Tailwind CSS
  • SQLite defaults
  • API health-check route
  • PHPUnit setup

This template is useful if you want to start a Laravel framework project quickly with a practical application skeleton already configured.

What It Creates

The CLI creates a project with the usual Laravel folders:

  • app - controllers, models, providers, and services
  • bootstrap - Laravel application bootstrap files
  • config - app, auth, cache, database, queue, mail, filesystems, logging, services, and session config
  • database - SQLite database file, migrations, factories, and seeders
  • public - front controller and public web assets
  • resources - Blade views, CSS, and JavaScript
  • routes - web, API, and console routes
  • storage - local framework and log directories
  • tests - feature and unit tests

It also includes a simple /api/health endpoint and a Blade home page so you can confirm the app is wired up.

Quick Start

Create a new project folder:

npx laravel-template-jpz my-app

my-app is the name of the folder that will be created. You can replace it with any project name you want.

You can also run the CLI without a project name:

npx laravel-template-jpz

When you do not add a project name, the template files are created in the current folder.

If you created a new project folder, open it:

cd my-app

Install PHP dependencies:

composer install

Create the app key:

php artisan key:generate

Install and build frontend assets:

npm install
npm run build

Run migrations:

php artisan migrate

Start the development server:

composer run dev

The Laravel framework app will run at:

http://localhost:8000

The health-check API route will be available at:

http://localhost:8000/api/health

Using Global Install

You can also install the CLI globally:

npm install -g laravel-template-jpz

The -g means global. This installs the CLI tool on your computer instead of inside one project folder.

After global installation, npm makes the laravel-template-jpz command available in your terminal. This means you can run the command from any folder without using npx.

Then create a project with:

laravel-template-jpz my-app

This command creates a new folder called my-app and adds the Laravel framework template files inside it.

Command Format

npx laravel-template-jpz [project-name]

Examples:

npx laravel-template-jpz my-laravel-project
npx laravel-template-jpz

If you add a project name, the CLI creates a folder with that name and puts the template files inside it.

If you do not add a project name, the CLI creates the template in the folder where you run the command.

Use npx when you only want to run the CLI once. Use global install if you want the command available on your computer all the time.

Generated Folder Structure

app/
  Http/
    Controllers/
  Models/
  Providers/
  Services/
bootstrap/
config/
database/
  factories/
  migrations/
  seeders/
public/
resources/
  css/
  js/
  views/
routes/
storage/
tests/

License

This project is licensed under the MIT License.

That means you can use, copy, modify, and share this CLI tool for personal or commercial projects.

See the full license here: LICENSE.