Laravel Toastie

Simple Toast notifications with built in default designs for ALT stack (Alpine, Laravel, Tailwind) applications with easy options to customise to your hearts content.

Install Latest Version · Report Bug · Request Feature

📔 Table of Contents

About the Project
Install
- Version Matrix
Usage
Contributing
- Project Tooling Quick Reference
Changelog
License
Acknowledgements

🌟 About the Project

All the other Laravel Toast notification libraries out there seemed to have nailed the API for creating Toasts, but the key areas they were lacking in are keeping up to date and ✨ style ✨.

This package aims to solve that by providing a default set of Toasts that look good and are easy to use, with it being very easy to change up the design if you hate the look of them and roll your own!

Toastie has support for 4 key toast types/states; Success, Info, Warning and Error.

📷 Screenshots

👾 Tech Stack

🎯 Features

Simple to use
Laravelified
Alpine & Tailwind
Expressive API
Auto hide or only on dismiss
✨ Stylish ✨ and modern default design
Highly customisable
Cheeky

💾 Install

Installation can be done via Composer:

composer require othyn/laravel-toastie

After installation you will need to do a fresh build of any assets via your frontend build tool of choice, which is probably Vite. This is so that the Tailwind bundler can pickup the new views and load in the classes the package uses (if they haven't already been bundled via usage elsewhere in your application) into your app bundles. You may also need to restart any Docker containers if you are still having issues.

Next you are going to want to head down to the configuration, so lets get started on usage! See you there.

Version Matrix

Here is the current version matrix for project supported versions of used frameworks and libraries.

Toastie Version	PHP Version	Laravel Version	Alpine Version	Tailwind Verison
`1.0.0`	`^8.1`	`^9.24`	`^3.4.2`	`^3.1.0`

If you require support for an older version of Laravel, submit an issue as we may be able to look into dropping the version requirements down, as I don't think it needs to be this new. Or, feel free to submit a PR!

🛠️ Usage

There are three key parts to Toastie;

The configuration.
- Where you can customise Toastie's behaviour.
The PHP API.
- How you can call and action Toastie.
The Blade components.
- How you can render Toastie.

Let's kick things off with the configuration, I'll meet you down there.

🔧 Configuration

Hello again! First thing we're going to need to do is publish the configuration so we can set things up how we want them.

We do this my telling Laravel to publish the config file into our working directory, instead of relying on the default one bundled with this package:

php artisan vendor:publish \
    --provider="Othyn\\Toastie\\Providers\\ToastieServiceProvider" \
    --tag="toastie-config"

You should now have an config/toastie.php file within your project that you can edit. If you go ahead and open it up, you'll see something like:

<?php

declare(strict_types=1);

return [
    'timings' => [
        /*
         * Whether the toasts should automatically close after a specified time.
         *
         * This time can be specified by setting the 'timings.dismiss_delay' value.
         */
        'auto_dismiss' => env('TOASTIE_AUTO_DISMISS', true),

        /*
         * Time, in seconds, that the toast should take to be dismissed when dismissing automatically.
         *
         * REQUIRES the 'timings.auto_dismiss' setting to be enabled.
         */
        'dismiss_delay' => env('TOASTIE_DISMISS_DELAY', 4),
    ],
];

Customise this to your hearts content, the configuration options available and a short description are provided above or in your new config/toastie.php file.

Let's move onto the PHP API.

🐘 PHP API

Calling Toastie can be achieved one of three ways;

... via the helper method.
... via the Facade.
... via a new instance of the class.

Choose whichever way you prefer to do things. I'm partial for the helper method myself, its nice and easy with good IDE type hinting.

The helper method

If you prefer taking things easy:

// An info type & style toast
toastie()->info('Remember to pick a movie to watch tonight!');

// A warning type & style toast
toastie()->warning('Its getting late, you should watch that movie...');

// An error type & style toast
toastie()->error('Ran out of popcorn.');

// A success type & style toast
toastie()->success("Watched {$favouriteMovie}.");

The Facade

If you prefer a more static way of life:

// Remember to include the class!
use Othyn\Toastie\Facades\Toastie;

// ... some ungodly code ...

// An info type & style toast
Toastie::info('Dinner\'s 5 minutes away.');

// A success type & style toast
Toastie::success('Dinner\'s ready!');

// A warning type & style toast
Toastie::warning('Dinner\'s getting cold... you should eat now.');

// An error type & style toast
Toastie::error('Dog ate it.');

You'll notice that the Facade has the concrete class as a mixin on the PHPDoc blocks, this so you're IDE will be happy. I know mine is.

The class instance

If you like things old school:

// Remember to include the class!
use Othyn\Toastie\Services\Toastie;

// ... some ungodly code ...

// Create the new toastie instance
$toastie = new Toastie();

// ... yet more ungodly code ...

// An info type & style toast
$toastie->info('Hey! How are you? Heads up, the next toast will be a warning.');

// A warning type & style toast
$toastie->warning('Uh-oh! Oh well, the next toast will be a success...');

// A success type & style toast
$toastie->success('Yes! Got the good one. Although the next one\'s going to sting...');

// An error type & style toast
$toastie->error('Ran out of bread.');

// ... when will it end?!

// Oh.

Let's move onto the Blade Components.

📄 Blade Components

By default, Toastie ships with a Toast design and paired component for all of the 4 key toast types that it supports. It also has some 'smarter' options and options that allow you to customise the appearance to your heards content whilst retaining Toastie's expressive API.

In order to have Toastie load toasts onto your page, you'll need to do one of three things;

... use the 'smart' Shared component to render only the default design but via one Component that dynamically changes; or
... add the Blade component directly for the style/type of toast you want to use (can be overridden); or
... use the 'stack' Stack component to load all toasts automatically depending on what is called (can be overridden).

By 'can be overridden', I'm refering to the fact that under those scenarios the actual underlying component file is loaded, meaning you can publish the views for the project and customise them to your hearts content, completely changing the design if you wish but retaining Toastie's expressive API. If you want to know how to do this, skip ahead to 'Customising the toast design'.

Let's kick things off with Toastie's default implementation.

Using the dynamic default design

This is the easiest way to maximise the utilisation of Toastie if you are not wanting to change up any of the designs.

<!-- my-view.blade.php -->

<!-- Will render only the required style/type of toast when called -->
<x-toastie::shared />

That's it! You're now using Toastie, just call Toastie via one of the PHP API methods described above and watch as toast goes everywhere! Enjoy!

Under the hood, this dynamically renders the default toast design, meaning this one isn't overridable - that functionality is reserved for the next two options so keep reading if that's what you want.

This should be the go to option for people just wanting Toastie to do all the work, so you can kick back and have another sip of coffee. Ahhhhhhhh.

Let's move on.

Using individual style/type components

This is the hardest, but most custom, utilisation of the Blade components:

<!-- my-view.blade.php -->

<!-- Will render a success toast when called -->
<x-toastie::success />

<!-- Will render an info toast when called -->
<x-toastie::info />

<!-- Will render a warning toast when called -->
<x-toastie::warning />

<!-- Will render an error toast when called -->
<x-toastie::error />

As you can see this is highly customisable, as you can place each toast somewhere different to render if you so wish. If you want to know how to do this, skip ahead to 'Customising the toast design'.

But having 4 lines is silly to get you access to all the components, which is where the next component comes in.

Lazy loading all components

This is the easiest way to maximise the utilisation of the Blade components whilst still retaining full control of the design:

<!-- my-view.blade.php -->

<!-- Will render only the required style/type of toast when called -->
<x-toastie::stack />

By design, this will only ever render the required component should it have been called by you calling Toastie on the last page cycle.

Under the hood, its just pulling in each component directly, meaning if you want to override the styles this will allow you to still render all of the toasts whilst using your nice new designs. If you want to know how to do this, skip ahead to 'Customising the toast design'.

Customising the toast design

So, don't like that default Toastie design eh? Well then, I suppose I better tell you how to change it. First, we need to publish Toastie's view set into your project so you can customise it:

php artisan vendor:publish \
    --provider="Othyn\\Toastie\\Providers\\ToastieServiceProvider" \
    --tag="toastie-views"

You should now have a load of view files appear in a new resources/views/vendor/toastie/components directory within your project that you can now edit to your hearts content.

To explain the files that you are seeing, in alphabetical order:

error.blade.php
- Description: The error toast component.
- Usage: Used in the x-toastie::error and x-toastie::stack components.
info.blade.php
- Description: The info toast component.
- Usage: Used in the x-toastie::info and x-toastie::stack components.
shared.blade.php
- Description: The shared toast component.
- Usage: Used in the x-toastie::shared component.
- Extra: This is the default dynamic design one, I guess you can override it if you want, its just not designed with that in mind.
stack.blade.php
- Description: The stack toast component.
- Usage: Used in the x-toastie::stack component.
- Extra: Renders the error, info, success and warning components within it depending on which one has been called, if any.
success.blade.php
- Description: The success toast component.
- Usage: Used in the x-toastie::success and x-toastie::stack components.
warning.blade.php
- Description: The warning toast component.
- Usage: Used in the x-toastie::warning and x-toastie::stack components.

Each Blade component gets access to the following variables:

$aToastieShouldBeDisplayed
- Type: Bool
- Description: Whether a toast should be displayed at all.
$shouldBeDisplayed
- Type: Bool
- Description: Whether the specific type of toast that the instance is should be displayed.
$type
- Type: Othyn\Toastie\Enums\ToastieType
- Description: The type of Toastie the instance is being called into being as.
$message
- Type: string
- Description: The message to be displayed in the toast.
$shouldAutoDismiss
- Type: Bool
- Description: Whether a toast should auto dismiss.
$autoDismissInSeconds
- Type: Integer
- Description: How long, in seconds, the toast should take to auto dismiss from when the page loads.
$autoDismissInMilliseconds
- Type: Integer
- Description: How long, in milliseconds, the toast should take to auto dismiss from when the page loads.
$colour
- Type: string
- Description: The Tailwind colour class that the component should use.
- Note: Only available on the default Shared Toastie type.
$icon
- Type: string
- Description: The SVG path string that the component should use to render the toast's icon.
- Note: Only available on the default Shared Toastie type.

🍞 Contributing

See the contribution guide on how to get started. Thank you for contributing!

Detailed within that guide are steps on how...

... issues should be used.
... to setup the project.
... branches should be used.
... commits should be formatted.
... pull requests should be submitted.
... build in project tooling; Make, Docker, testing, test coverage, static analysis and linting.
... the build process works and the automation that drives it.

🧰 Project Tooling Quick Reference

There are quite a few ease-of-use tools in place to help you manage the project, all of which are masked behind Make and Docker to make using this project as smooth as possible.

# Let's get things setup. This will run:
#  - A Docker Compose build.
#  - A Composer install via the now built project Docker container.
$ make setup

# ... happy few hours programming, adding cool new features and smashing bugs ...

# Lets make sure things are formatted correctly.
# This runs Pint (PHP-CS-Fixer) via the projects Docker container.
$ make lint

# Lets make sure things are implemented correctly.
# This runs PHPStan via the projects Docker container.
$ make stan

# Lets make sure things are still functioning as intended. This will:
#  - Run Pest (PHPUnit) and ensure all tests pass via the projects Docker container.
#  - Ensure that we are reaching the 100% code coverage target as part of that process.
$ make test

# If you want a shortcut to; lint, stan and then test all in one go via the projects Docker container
$ make all

# Finally, if you need access to the projects Docker container's shell
$ make shell

That's about it, go make something cool and submit a PR!

⚠️ License

Distributed under the MIT License. See LICENSE for more information.

💎 Acknowledgements

Useful resources and libraries that have been used in the making of this project.

Readme: Louis3797/awesome-readme-template
Readme: ikatyang/emoji-cheat-sheet
Readme: shields.io
Logo: Toast SVG Vector 63 (CC Attribution License)
Design: Tail-kit
Package: illuminate/support
Package: orchestra/testbench
Package: pestphp/pest
Package: laravel/pint
Package: phpstan/phpstan
Inspiration: (Design) Tailwind CSS Toast And Notification Example
Inspiration: (Design) Animated dynamic progress bar

Uh oh!

License

othyn/laravel-toastie

ErrorLooks like something went wrong!

About

Topics

Resources

License

Code of conduct

Security policy

Uh oh!

Stars

Watchers

Forks

Releases 1

Sponsor this project

Uh oh!

Uh oh!

Languages

Error
Looks like something went wrong!