Episode 47 · 58 min

Shipping a paid Laravel package

Maya Chen · Staff Engineer, Ledgerline

▶

Now playing

Licensing, private Composer repositories, and how to keep a free package genuinely good while selling a paid one on top.

00:00 Why not just open-source everything
06:12 Picking a licensing stack
18:40 Private Composer distribution
31:05 Shipping JavaScript inside a Composer package
44:20 Support boundaries that stay kind

How this was added

app/Models/Episode.php

use Usamamuneerchaudhary\Commentify\Traits\Commentable;

class Episode extends Model
{
    use Commentable;
}

the Blade view

<livewire:comments :model="$episode" />

Pro JSON API registry

// config/commentify-pro.php
'commentables' => [
    'episodes' => \App\Models\Episode::class,
],

This surface relabels the thread via the translator. No forked views.

Listener discussion (3)

Name

Notify me of replies by email

Or Log in to comment!

Would love a follow-up episode purely on support boundaries. That was ten minutes and could easily be an hour.

The bit about no runtime license checks stood out. Is that purely a trust decision or is there a technical argument too?

The section at 31:05 on shipping JavaScript inside a Composer package is the most useful ten minutes of package advice I have heard this year. One license covering the PHP and the JS is obvious in hindsight and I had never seen anyone do it.