How to Submit Your Laravel Package to LaraCommunity

Tarun Korat — Sat, 06 Dec 2025 10:07:41 +0000

Built an awesome Laravel package? Let me show you how to get it in front of thousands of developers in just 5 minutes!

Why This Matters
You've spent weeks (maybe months) building a package that solves a real problem. Now it's time to share it with the world. But here's the thing—just putting it on GitHub and Packagist isn't enough. You need visibility.

That's where LaraCommunity comes in.

Quick Stats: What You Get
When you submit your package to LaraCommunity:

⚡ Auto-sync with GitHub (stars, issues, updates)
📊 Analytics on views, bookmarks, and downloads
💬 Reviews & Ratings from the community
🔍 SEO Benefits (Google indexing + search visibility)
🆓 Completely Free (no fees, no premium tiers)

Before You Submit: The Checklist

Make sure your package has:
✅ Must Have

Public GitHub repository
Valid composer.json with license
Basic README with usage examples

🎯 Should Have (Recommended)

Listed on Packagist
Automated tests
Clear documentation
Version tags

💡 Nice to Have

CI/CD (GitHub Actions)
Code coverage badge
Changelog

The 5-Step Process
Step 1: Login & Navigate
Profile dropdown → "Submit Package"

Step 2: Fill the Form (5 Minutes Max)
You only need these fields:

Composer Package Name vendor/package-name Must match your composer.json. This is what developers use to install: bashcomposer require vendor/package-name

Step 3: Auto-Sync Magic ✨
Click submit and watch the magic happen:
From GitHub:
✓ Repository description
✓ Star count
✓ Fork count
✓ Open issues
✓ Last commit date
✓ License type
✓ Topics/tags
From Packagist:
✓ Download stats
✓ Latest version
✓ PHP requirements
✓ Laravel compatibility
✓ Dependencies
All. Automatically. Updated. Daily. 🎊
No manual updates ever needed!

Step 4: Admin Review (Usually 24 Hours)
Every submission goes through a quick quality check:
What we verify:

✅ Repository is accessible
✅ Valid open-source license
✅ Clear documentation
✅ Genuinely useful for Laravel devs
✅ No security concerns

Timeline:

⏰ Typical: 24-48 hours
🚀 Established maintainers: 2-6 hours
📅 Weekend: Reviewed by Monday

You'll get an email either way!

Step 5: You're Live! 🚀
Your package now has:

Dedicated Page with all the bells and whistles
Search Visibility (findable by name, keywords, category)
Your Profile showcasing all your packages
Review System for community feedback

Introducing Laravel Asset Cleaner: Safely Remove Unused Assets from Your Laravel Projects

Tarun Korat — Wed, 12 Nov 2025 06:51:11 +0000

Introducing Laravel Asset Cleaner: Safely Remove Unused Assets from Your Laravel Projects

Have you ever inherited a Laravel project and wondered, "Are we actually using all these images?" or "Is this old JavaScript file still needed?" You're not alone.

🤔 The Problem

Over time, Laravel projects accumulate digital clutter:

Images from old designs
Unused Vue/React components
Forgotten CSS files
Legacy JavaScript libraries
Font files that nobody uses

These unused assets:

✘ Bloat your repository
✘ Slow down deployments
✘ Confuse new developers
✘ Make maintenance harder

But how do you know what's safe to delete? Manual checking is time-consuming and error-prone. Delete the wrong file, and you break production.

💡 The Solution: Laravel Asset Cleaner

I built Laravel Asset Cleaner to solve this exact problem. It's a package that:

Scans your entire Laravel project for assets
Detects which files are actually being used
Reports unused assets with details
Safely removes them with automatic backups

🚀 Quick Start

# Install
composer require tarunkorat/laravel-asset-cleaner

# Publish config
php artisan vendor:publish --tag=asset-cleaner-config

# Scan for unused assets
php artisan assets:scan

# Preview what will be deleted
php artisan assets:delete --dry-run

# Delete with automatic backup
php artisan assets:delete

✨ Key Features

1. Smart Detection

The package scans multiple locations for asset references:

Blade Templates:

<img src="{{ asset('images/logo.png') }}">
<script src="{{ mix('js/app.js') }}"></script>

JavaScript/Vue/React:

import Logo from './images/logo.png';
import Header from './components/Header.vue';

CSS/SCSS:

background-image: url('../images/banner.jpg');
@import 'components/button.css';

PHP Controllers:

$image = Image::make(public_path('images/product.jpg'));
return asset('images/logo.png');

2. Strict Matching (No False Positives!)

A common problem with asset detection is false positives. For example, a file named error.svg might match every occurrence of the word "error" in your code.

Laravel Asset Cleaner uses strict boundary checking to avoid this:

// ❌ Won't match these:
'error' => 'Error message'
throw new Error()

// ✅ Will match these:

import icon from './error.svg'

3. Debug Mode

Not sure why a file is marked as used? Use debug mode:

php artisan assets:debug resources/images/logo.png

Output:

✓ File exists
Path: resources/images/logo.png
Size: 45 KB
🔎 Searching for references...
✓ Found 2 file(s) with references:
• resources/views/layouts/app.blade.php
Match: <img src="{{ asset('images/logo.png') }}">
• resources/js/components/Header.vue
Match: import logo from '@/images/logo.png'

4. Safety Features

💾 Automatic Backups - Creates timestamped backups before deletion
🛡️ Protected Files - Configure files that should never be deleted
👁️ Dry Run Mode - Preview changes without deleting anything
✅ Verification - Confirms files were actually deleted

📊 Real-World Results

I tested this on several production Laravel applications:

Project 1: E-commerce site (3 years old)

Found: 156 unused files
Freed: 23MB
Time saved: ~8 hours of manual checking

Project 2: SaaS application (2 years old)

Found: 89 unused files
Freed: 12MB
Cleaned up: 30 old component files

Project 3: Agency project (5 years old)

Found: 203 unused files
Freed: 31MB
Repository size reduced by 35%

🎯 Common Use Cases

After Refactoring

# Just removed old components?
php artisan assets:scan --type=js
php artisan assets:delete --type=js

Before Production Deploy

# Clean everything up
php artisan assets:scan
php artisan assets:delete --force

Optimize Images

# Find unused images
php artisan assets:scan --type=img
php artisan assets:delete --type=img

CI/CD Integration

# Generate report in CI pipeline
php artisan assets:scan --json > unused-assets.json

⚙️ Configuration

The package is highly configurable. Here's a snippet from config/asset-cleaner.php:

return [
    // Which asset types to clean
    'clean_types' => ['js', 'css', 'img'],

    // Enable strict matching
    'strict_matching' => true,

    // Define asset locations
    'asset_types' => [
        'js' => [
            'directories' => ['resources/js', 'public/js'],
            'extensions' => ['js', 'jsx', 'ts', 'tsx', 'vue'],
        ],
        'img' => [
            'directories' => ['resources/images', 'public/images'],
            'extensions' => ['jpg', 'png', 'gif', 'svg', 'webp'],
        ],
    ],

    // Files that should never be deleted
    'protected_files' => [
        'resources/js/app.js',
        'resources/css/app.css',
    ],
];

🛠️ How It Works Internally

For the curious developers, here's the high-level architecture:

AssetScanner Service
- Uses Symfony Finder to locate asset files
- Stores assets in memory with metadata (size, type, path)
Reference Extraction
- Scans all PHP, Blade, JS, CSS files
- Uses regex patterns to find asset references
- Implements strict boundary matching
Comparison Engine
- Compares found assets vs referenced assets
- Marks unused assets for deletion
- Respects protected files configuration
Safe Deletion
- Creates timestamped backup directory
- Copies files before deletion
- Verifies deletion success
- Cleans up empty directories

🤝 Contributing

This is my first Laravel package, and I'd love your feedback! The project is open source under the MIT License.

Ways to contribute:

🐛 Report bugs
💡 Suggest features
📖 Improve documentation
🔧 Submit pull requests

GitHub: https://github.com/tarunkorat/laravel-asset-cleaner

📦 Installation & Links

composer require tarunkorat/laravel-asset-cleaner

GitHub: https://github.com/tarunkorat/laravel-asset-cleaner
Packagist: https://packagist.org/packages/tarunkorat/laravel-asset-cleaner
Documentation: Full README on GitHub

🎉 Conclusion

Laravel Asset Cleaner helps you maintain cleaner, more efficient Laravel projects by safely removing unused assets. It's free, open source, and designed with safety as the top priority.

Give it a try and let me know what you think! Have questions or suggestions? Drop them in the comments below. 👇

Star the repo if you find it useful! ⭐

Happy coding! 🚀

Forem: Tarun Korat

How to Submit Your Laravel Package to LaraCommunity

Introducing Laravel Asset Cleaner: Safely Remove Unused Assets from Your Laravel Projects

🤔 The Problem

💡 The Solution: Laravel Asset Cleaner

🚀 Quick Start

✨ Key Features

1. Smart Detection

2. Strict Matching (No False Positives!)

3. Debug Mode

4. Safety Features

📊 Real-World Results

🎯 Common Use Cases

After Refactoring

Before Production Deploy

Optimize Images

CI/CD Integration

⚙️ Configuration

🛠️ How It Works Internally

🤝 Contributing

📦 Installation & Links

🎉 Conclusion