Crèmerie — Warm Cream Vanilla-JS Toast & Notification Widget
Description
Overview
Crèmerie is a delightfully warm, cream-toned toast and notification widget for modern web projects. Forget the cold blue or harsh red system alerts — Crèmerie wraps every message in a luscious palette of warm whites, soft honeys, and gentle terracotta accents that feel welcoming without sacrificing clarity. The single-file drop-in (no build step, no dependencies) slots into any plain HTML, TypeScript-built, or framework-agnostic front-end in under a minute.
The problem it solves is immediate: most open-source toast libraries are either visually generic, opinionated about your CSS framework, or require npm. Crèmerie is none of those — it is one self-contained creamerie.js script with an embedded stylesheet, plus a polished demo page that shows every state right out of the box.
Who It's For
- Indie hackers and solo developers who want beautiful, plug-and-play notifications
- TypeScript/vanilla-JS projects looking for a lightweight (~5 KB) notification solution
- Designers prototyping warm or earthy-toned UI systems
- Agency developers who need a client-safe, dependency-free component they can brand quickly
- Anyone tired of the generic grey/blue toast libraries that clash with bespoke designs
Key Features in Depth
Four semantic flavours — success (warm sage), info (honey amber), warning (soft peach), and error (dusty rose) — each carefully colour-matched to the cream base so nothing looks jarring. Every toast carries a distinctive left-accent border and a subtle cream-tinted icon drawn in pure CSS, keeping the package asset-free.
Configurable position: toasts can stack at any of the four corners of the viewport. A smooth slide-up + fade entrance and a matching fade-out exit run on CSS transitions so animation stays GPU-accelerated. Auto-dismiss timing is controllable per-call (default 4 s, 0 = persistent). A manual close button sits unobtrusively in the upper-right corner of each card.
Progress bar: a thin cream-tinted progress line drains across the bottom of each toast during its lifetime, giving users a satisfying visual cue about when the message will disappear — a small touch that makes the widget feel premium.
Pause-on-hover: the timer and progress bar freeze whenever the user's cursor enters a toast, ensuring no important message disappears before it is read.
What's Included
index.html— full interactive demo with a warm cream UI, live trigger buttons for every type and position, and configuration controlscreamerie.js— the self-contained widget (inlined CSS + vanilla JS, ES2017, no dependencies)README.md— concise usage guide, API reference, and customisation tips
How to Customise / Get Started
1. Copy creamerie.js into your project and add a single <script> tag — that is the entire installation. 2. Call Creamerie.show({ type, title, message, duration, position }) anywhere in your JS. 3. Override the handful of CSS custom properties (--cr-bg, --cr-accent, etc.) documented in the README to match your brand palette in seconds. The demo page doubles as a live sandbox to test changes before committing them.
Features
Requirements
- Any modern browser (Chrome 80+, Firefox 75+, Safari 14+, Edge 80+)
- No build step or package manager required
- Plain HTML file or any JS framework that allows injecting a script tag
- No external fonts, icons, or CDN dependencies
Changelog
Frequently Asked Questions
Do I need npm or a build tool to use Crèmerie?
No. Just copy creamerie.js into your project and add a script tag. Everything — styles and logic — is bundled inside that single file.
Can I use this in a TypeScript project?
Yes. The widget exposes a global Creamerie object and works in any TS project without type errors. You can call Creamerie.show() from TS files after the script is loaded, or wrap it in a thin TS module.
How do I change the colours to match my brand?
Override the CSS custom properties (--cr-bg, --cr-border, --cr-success, etc.) in your own stylesheet after loading creamerie.js. The README lists every available variable with default values.
Can I show a persistent toast that doesn't auto-dismiss?
Yes. Pass duration: 0 in the options object and the toast will stay visible until the user clicks the close button manually.
How many toasts can be displayed at once?
Crèmerie queues toasts in a stack; by default up to 5 are visible simultaneously. Older toasts are removed from the stack as the queue grows beyond that limit, keeping the UI clean.
Is this licensed for client projects?
A standard single-use licence covers use in one end project (your own site or a client site). For use across multiple client projects or SaaS products, please purchase the extended licence.
Technical requirements
- See the detailed requirements in the product description below.
What is included
- Downloadable product files
- Product listing and product page guidance
- Product files ready for self-hosting or integration
- 10 listed features
- Changelog included on the product page
Who is this product for
- Teams shopping within TypeScript
- Use cases aligned with toast, notification, vanilla js, widget
License and usage
- Verify the exact usage rights on the selected license before deployment or client handoff
- Keep the purchase record and license certificate for future verification
Updates and support
- 6 months of seller support included
- Review the seller support scope before purchasing.
- Recent changes are visible in the product changelog
- Use the changelog to confirm ongoing maintenance before rollout
Technical details
- Current version
- 1.0.0
- Last updated
- Jul 11, 2026
- Support period
- 6 months of seller support included
Marketplace review
Content review processNo completed marketplace review record is available for this product.
This is not a full penetration test or a guarantee that the product is vulnerability-free.
License comparison
A license is tied to one end product, not strictly to one domain. Development, staging, and the final production domain may belong to the same licensed deployment.
| Use | Regular License | Extended License |
|---|---|---|
| Source code modification | ||
| Own project use | ||
| One client project | ||
| One production deployment | ||
| Development and staging | ||
| Paid SaaS or paid user access | ||
| Multiple unrelated client projects | ||
| Redistribute source code | ||
| Resell source code |
License FAQ
Can I modify the source code?
Yes, under both licenses.
Can I use the script for a client?
Yes, for one client end product.
Can I install it on a staging domain?
Yes. Development and staging may belong to the licensed deployment.
Do I need another license for another client?
Yes, each unrelated client end product needs its own license.
Can I use it for a paid SaaS?
Yes, with an Extended License.
Can I resell the source code?
No. Standalone redistribution or resale is prohibited.
Is a license limited strictly to one domain?
No. It is tied to one end product, which may use development, staging, and production domains.
Item Details
- Last Update
- July 11, 2026
- Published
- July 10, 2026
- Version
- 1.0.0
- Category
- TypeScript
- Sales
- 0
- Reviews
- No reviews
Buying guides
Share This Item
License Info
Regular License — Use in one end product which end users are not charged for.
Extended License — Use in one end product which end users can be charged for.
Verify a license key →