The Jamstack is a modern architecture for creating websites that focus on performance and developer experience. It can be used for anything from personal static blogs to large, enterprise, dynamic storefronts. The Jam in Jamstack stands for JavaScript, API’s, and markup. Worded differently, static markup is transformed by JavaScript and utilizes third-party API’s at build time and run time. A comprehensive definition and history of Jamstack can be found here.

Despite often being associated with static site generators, Jamstack sites do not need to stay static. In situations where prerendered markup alone does not suffice, dynamic content can be progressively loaded on the client side. An online storefront might statically generate listings for all the products in their catalog, and then update details like inventory or price after the page is first rendered. Web components are a great fit for this workflow, because they allow for adding zones of interactivity within otherwise static HTML.

Let’s add user-generated comments to a Jamstack site with a web component created with Stencil that utilizes Supabase to store dynamic data. Supabase is an open-source alternative to Firebase that provides an interface and API that makes database CRUD operations (creating, reading, updating and deleting) possible without writing backend code. I have been using it extensively in my personal projects, and I think combining it with Stencil’s web components is a wonderful way to create micro-frontends: dynamic, independent, contained widgets that can be dropped anywhere in a larger project (whether that is a SPA or a static HTML file).

Here is a preview of the final component we will be creating:

The full source is also available on GitHub.


When I am building a component, I like to start out with writing an example of what the end usage might look like. For our comments component, I want it to have a really low-config API: all that should be required to use the component is a unique ID, URL to our backend, and access token for Supabase.


Stencil Implementation

Let’s scaffold out a Stencil component with npm run generate my-comments in a new Stencil project. This will set us up with a boilerplate, to which we can add public properties with the @Prop decorator and internal state with the @State decorator. For a deeper introduction to props and state, check out the Stencil documentation.

  tag: 'my-comments',
  styleUrl: 'my-comments.css',
  shadow: true,
export class MyComments {
   * We don't need a Prop for `id`, since it is a global HTML attribute.
   * Instead, we can grab it from the HTML element with the @Element decorator.
  @Element() element;

   * Public URL to the Supabase backend.
  @Prop() supabaseUrl: string;

   * Public access token to the Supabase backend.
  @Prop() supabaseKey: string;

   * Comments associated with this block's `id`.
  @State() comments: MyComment[] = [];

   * Value of the new comment text input.
  @State() newCommentValue: string;

   * Supabase client to be initialized with `supabaseUrl` and `supabaseKey`.
   * We will import this type when we install Supabase.
  private supabase: SupabaseClient;

  render() {

The this.comments array we defined above will hold the comments data loaded from the Supabase backend. Let’s define a MyComment type so that we can utilize Stencil’s built in TypeScript support.

type MyComment = {
   * The id of the author who wrote the comment.
  author_id: string;
   * The body of the comment.
  content: string;
   * The datetime when the comment was first posted.
  created_at: string;
   * The `id` of the component that created this comment.
   * For example,  would create and retrieve comments with
   * a `location_id` of "blog-post-1".
  location_id: string;
   * A unique id for the comment, generated by Supabase.
  id: string;

Rendering a template

Now we are ready to think about what we need to render to the user:
– A list of current comments.
– An input field for adding a new comment.

When building Stencil components with multiple moving parts, I find it helpful to separate out semantically-different templates into multiple render functions or functional components.

The renderComment helper function will be used to render the markup for an individual comment. To make sure the comment is accessible, let’s write it as an HTML article element with the ARIA comment role.

private renderComment(comment: MyComment) {
  return (
    <article role="comment">
        <small><time dateTime={comment.created_at}>{comment.created_at}</time></small>

Now in our render function, we can call renderComment for each item in the this.comments state variable:

render() {
  return (
      { => this.renderComment(comment))}

The last thing we need to add to our template is a way for users to add new comments. Let’s add a small form with a submit button and a text input that updates the newCommentValue.

render() {
  return (
      <form onSubmit={(ev: Event) => this.handleSubmit(ev)}>
          placeholder="Add a comment..."
          onChange={(ev: Event) => this.handleChange(ev)}
        <input type="submit" value="Submit"/>
      { => renderComment(comment))}

Handling Input

In the form template above, we referenced two methods to be implemented that handle user input. In the handleChange method we want to store the current value of the input element into component state. The handleSubmit method will be implemented in the next section.

private handleChange(ev: Event) {
  const target = ev.currentTarget as HTMLInputElement;
  this.newCommentValue = target.value;
private handleSubmit(ev: Event) {
  // TODO

Setting up Supabase

Now we have a shell set up to display our comments, and props and state set up to hold our data. Let’s configure Supabase to hold our comment data and wire it up to the component’s lifecycle events.

After registering an account and creating a new project, configuring Supabase to work with our frontend only takes a couple of steps.

Creating a Table to Store Comments

In the Supabase sidebar, go to the “Tables” page in the sidebar and then select the New button. Let’s create a table with fields that match our MyComment type above. Each field will be a column in the table, and each row will represent a comment.

Get the Supabase URL and Key

In the Supabase sidebar, go to the “Settings” page in the sidebar and continue to the “API” sub-page. There, Supabase exposes two things we need:
– The “anon” key is the client side api key that allows our frontend to connect to Supabase. This key is safe to share publicly.
– The config URL is the public REST endpoint for our Supabase project.
These values correspond to the supabaseUrl and supabaseKey props that were added to the component.


This tutorial does not cover setting up authentication. Supabase has tutorials for doing so here. Setting up proper authentication is necessary to prevent unrestricted CRUD access to the database.

Connecting Supabase to Stencil

We need the component to interact with Supabase in three ways:
– Read comments from the database when first loaded
– Load new comments whenever the database is updated
– Submit a new comment when the user presses the submit button
Similar to how we added multiple render helper functions in the previous section, when I am creating a component, I like to separate logical tasks like these into their own helper functions as well.

Initialize Supabase

When our component first loads, we need to also load the Supabase client and connect to it.

Let’s add the Supabase client as a dependency to our project with npm i @supabase/supabase-js. After installing, we can get the references we need with the following import statement at the top of the component file.

import { createClient, SupabaseClient } from '@supabase/supabase-js';

Now, in the componentWillLoad lifecycle function, we can initialize Supabase with the appropriate props that were provided to the component.

 componentWillLoad() {
   this.supabase = createClient(this.supabaseUrl, this.supabaseKey);

Read comments from the database

Supabase allows for chaining function calls to grab data from a table, filter out irrelevant data, and sorting the returned entries.

private async getComments() {
  const { data } = await this.supabase
    // Grab data from the 'comments' table.
    // Only grab data that is associated with this component's `id`.
    // Order the data such that new comments are at the top of the list.
    .order('created_at', { ascending: false });
  // Store the response in the `comments` state variable.
  this.comments = data;

We want to load the state when the component is first loaded, so we can call getComments in the componentWillLoad lifecycle function.

componentWillLoad() {

Real-time updates from the database

It would be nice if new comments were automatically shown in our comment list. Supabase provides a way to do this as well.

private async watchComments() {
  await this.supabase
    // Only watch updates that match our component's id
    // When a comment is inserted into the table, update the component state.
    .on('INSERT', payload =&gt; {
    this.comments = [, ...this.comments];

This can also be added to the componentWillLoad lifecycle function.

componentWillLoad() {

Add new comment to the database

The last piece of functionality we need is the ability to add new comments.

private async addComment() {
  const { data, error } = await this.supabase
        content: this.newCommentValue,
        author: 'Author Name', // Dummy value. (To be implemented when auth is added.)
        // Supabase will automatically generate `id` and `created_at`
  return data;

Now, we need to call addComment whenever the form in our component’s template is submitted. Let’s add it to the handleSubmit function we created earlier.

private handleSubmit(ev: Event) {
  // Prevent the default event behavior to keep the page from refreshing.

Adding Styles

Lastly, let’s make the component a little nicer to look at by adding some styles. I have added the following CSS to my-comments.css, which is referenced in the @Component decorator.

:host {
  display: block;
  font-family: sans-serif;

article[role="comment"] {
  margin-top: 1rem;
  padding: 1rem;
  border: 2px solid black;
  border-radius: .5rem;
  box-shadow: black 5px 5px;

form {
  display: flex;
  flex-direction: column;

form textarea {
  width: 100%;
  border-radius: 5px;
  border: 2px solid lightgray;
  resize: vertical;
  padding: .5rem;
  box-sizing: border-box;

form input[type="submit"] {
  background-color: black;
  color: white;
  border: none;
  border-radius: 5px;
  text-align: start;
  max-width: min-content;
  margin-top: .5rem;
  padding: .5rem;

Wrapping up

There are a couple of things not covered in this tutorial that are necessary before the component is ready for public use, such as adding authentication and some content moderation capabilities. However, when we are ready and we publish the component to npm, we will have a powerful micro-frontend, wrapped in a Stencil web component, and ready to be dropped into any Jamstack website with zero additional configuration.

That is one of the natural synergies that web-standard Stencil web components have with the Jamstack. All that is required is a script tag and your components are ready to be consumed. Additionally, this component can be built to Angular, React, or Vue components using Stencil’s built in framework integrations. Personally, I can’t wait to expand this starter and add it to my Jamstack blog built with 11ty. If you enjoyed this tutorial, leave a comment below if you would like to see more!

Sign up for the Ionic Newsletter to get the latest news and updates!

Notable Replies

  1. Great article Will, this is just what I needed to get myself started on developing Stencil components.

    One question though, I keep seeing articles that say that Supabase is “an open-source alternative to Firebase”, is that something they are plugging? Firebase has NoSQL databases whereas Supabase has SQL - not really an alternative in my opinion?

    Being the developer of AceBase, which is (…wait for it…) “an open-source alternative to Firebase”, so it is fair to say I’m pretty biased, BUT AceBase truly is an alternative to Firebase because it is NoSQL and basically uses the same programming syntax - you can use your existing Firebase code and it will work with AceBase. I was hesitant to reply at first, but I would like to take this opportunity to tell you about it, you might like it! It works as a hosted db server, standalone db and even in the browser with offline support and sync functionality. All code is freely available through npm and github.

    Thanks again & have a great weekend!