Crème — Elegant Vanilla JS Toast & Notification Widget
Description
Overview
Crème is a refined, self-contained notification and toast widget crafted in pure vanilla JavaScript with zero dependencies. Wrapped in a warm crème-and-cocoa visual language — soft ivory backgrounds, warm sepia accents, gentle caramel highlights — it brings a taste of bespoke boutique design to any web project. Forget the cold blue system alerts or aggressively purple popups: Crème is built for websites and apps that value warmth, readability and quiet sophistication.
Drop in one <script> tag and one <link> tag. That's it. No build step, no npm, no bundler required. Crème works in any static site, CMS theme, landing page or admin panel.
Who It's For
- Frontend developers tired of restyling noisy third-party toast libraries.
- Designers who want notification UI that matches a warm, editorial or boutique aesthetic.
- Landing page & marketing site builders wanting polished success/error feedback without heavy dependencies.
- Theme and template authors looking for a lightweight, plug-and-play notification component to bundle.
Key Features in Depth
Crème ships four notification types — success, error, warning, and info — each with its own warm icon, colour tint and tone. Toasts stack vertically with smooth CSS slide-in and fade-out transitions. A configurable auto-dismiss timer with a live progress bar gives the user a clear visual cue before the notification disappears. Toasts can also be dismissed manually via a close button with a hover state that feels intentional, not tacked-on.
Position is fully configurable: top-right, top-left, bottom-right or bottom-left, set globally or per-call. A maximum stack limit prevents the screen from flooding. All API options are set through a clean JavaScript object, making integration with any codebase trivial.
What's Included
index.html— fully styled interactive demo showcasing all toast types, positions and options.creme-toast.js— the standalone widget script (~120 lines, heavily commented).README.md— usage guide, API reference and customisation notes.
How to Customise / Get Started
1. Add <script src="creme-toast.js"></script> to your page. The widget injects its own CSS automatically — no separate stylesheet needed.
2. Call CremeToast.show({ message: "Saved!", type: "success" }) from any event handler.
3. Tweak the CSS custom properties at the top of creme-toast.js (colour tokens, font, border-radius, shadow) to match your brand palette in seconds.
4. Set global defaults once with CremeToast.configure({ position: "bottom-right", duration: 4000 }).
Features
Requirements
- Any modern browser (Chrome 80+, Firefox 75+, Safari 13+, Edge 80+)
- No build step or bundler required
- No npm or Node.js required
- No external libraries or frameworks required
Changelog
Frequently Asked Questions
Do I need npm, Node.js or a build tool to use Crème?
No. Crème is a single vanilla JS file that injects its own CSS. Just add one script tag to your HTML and call the API. No build step, bundler or package manager needed.
Can I change the colours to match my brand?
Yes. All colour, typography, border-radius and shadow values are stored as CSS custom properties injected by the script. Edit the token block at the top of creme-toast.js to match any palette in under a minute.
How do I set a different position for individual toasts vs a global default?
Call CremeToast.configure({ position: 'bottom-right' }) once to set the global default, then pass position as an option to any individual CremeToast.show() call to override it for just that notification.
What frameworks does it work with?
Crème is framework-agnostic vanilla JS and works with any HTML page, CMS theme, static site generator, React app, Vue app or admin template — anywhere you can add a script tag.
Is there a limit to how many toasts can appear at once?
Yes. The default maximum stack is 5 simultaneous toasts. Older toasts are removed from the bottom of the stack when the limit is exceeded, keeping the UI clean. You can adjust this limit via the configure() API.
Can I use Crème in a commercial project or client site?
The Regular License covers use in one end product, including client projects, free or paid. For SaaS products or tools where the widget is part of a product sold to multiple end users, an Extended License applies.
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
- 12 listed features
- Changelog included on the product page
Who is this product for
- Teams shopping within TypeScript
- Use cases aligned with toast notification, vanilla javascript, widget, ui component
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
Tags
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 →