Principal Web
Developer &


Progressive Enhancement with Petite-vue

I recently wrote about how petite-vue is a great way to sprinkle in interactivity. There’s a downside to putting all your eggs in the JavaScript basket though, especially when it involves rendering content. There’s a whole fuzzy world of, just because you can, doesn’t mean you should web dev things, and this is definitely one of them.

Similar to Single-Page Applications (SPAs), you’ll have a rougher time with SEO, because the content isn’t there when the page loads, it’s being added at runtime. Also, if JavaScript is turned off, your users will get served up a whole lot of nothin’. You can debate that we’re beyond a world that needs the web to work without JavaScript, but I like the idea of approaching JavaScript as a tool for progressive enhancement; the concept has too many benefits to out-right ignore.

The Problem

To illustrate the problem, here’s a pen showing a searchable list of grocery items being rendered to the page using petite-vue. Why not just write HTML? Because we want to enhance this list by making it searchable, and petite-vue makes that elegantly easy.

We use the v-for directive to create <li>’s from a filteredList getter that filters the original list with the <input> value. As the search term in the input updates, the filteredList getter reruns, causing the v-for to rerender the list all in real-time.

See the Pen Progressively Enhanced Petite-Vue by Andrew (@walpolea) on CodePen.

The Solution

Let’s fix the problem with a progressive enhancement pattern in petite-vue.

Effectively, we’re going to provide the list (without search functionality) as static markup, and then use petite-vue to rerender that content with its own markup. It’s essentially a bait-and-switch of static content with interactive content. As long as your markup matches, the user won’t notice any large content shifting, except for where there are added functional pieces, like the search box.

Hit Rerun down in the bottom right to see the progressive enhancement happen. For dramatic effect, there’s a 2 second setTimeout delay to give you time to see the original static content, and then watch the content become enhanced. In reality, with a quick loading site, users likely won’t even notice the transition happen.

See the Pen Progressively Enhanced Petite-Vue by Andrew (@walpolea) on CodePen.

The Progressive Enhancement Pattern

Let’s pull apart the example and break down the pattern, because that’s the bit that can be applied to a whole host of situations where you want to use petite-vue to progressively enhance your content.


First let’s get the JavaScript out of the way, because it’s important that I don’t leave you in the dark, but it really has little bearing on the pattern:

import { createApp } from '';

const searchableList = ({list}) => {
  return {
    //when the scope mounts, set initialized to true
    async mounted() {
      await new Promise(resolve => setTimeout(resolve, 2000)); //artificial delay
      this.initialized = true;
    //return a filtered version of the full list based on the search term
    get filteredList() {
      if( ) {
        return this.list.filter( g => g.toLowerCase().includes( )
      //otherwise, no search term, return the full list
      return this.list;

//this tells petite-vue to look for v-scope directives on the page,
//and we register the ability to use the searchableList scope we built


The HTML is really where we can call out the progressive enhancement pattern. We separate the block into two main parts:

<div class="container" v-scope="searchableList({list:groceries})" @vue:mounted="mounted">
  <template v-if="initialized">
    <!--   This only shows when petite-vue runs and sets initialized to true  -->
    <h1>Enhanced with Petite-vue</h1>
    <input type="text" v-model="search" placeholder="search groceries">
      <li v-for="item in filteredList">{{item}}</li>

The first block, within a <template> tag will be the petite-vue enhancement. we will add the v-if="initialized" directive so that this tag will not render unless initialize is evaluated by petite-vue as true. The beauty here is that HTML won’t render a <template> tag into the page either, so if JavaScript hasn’t run, we never see this content. Inside is all the stuff from the earlier demo, using v-for and such.

  <div v-else>
    <!--   This content would be statically or server generated and hide when petite-vue runs  -->
    <h1>Statically Rendered Content</h1>
      //this could also be server-generated, which is why I put it up here in the html block
      const groceries = ['Milk', 'Eggs', 'Bread', 'Jam', 'Cheese', 'Butter', 'Mustard'];

The second part is your statically generated content contained in <div v-else>. Once again being tricky, without JavaScript running, the v-else gets ignored and the page will render this content as normal. Here you might actually be using something like php or nunjucks or liquid to dynamically generate this markup. Whatever it is, it’s just HTML, either static or server-generated.

The last added trick is that we need to pass the list of things into petite-vue as JavaScript, so you’ll also see a <script> tag where we can generate the array petite-vue needs to recreate the list itself. Again, something that can be generated with a templating language.

That’s it! When JavaScript is disabled, the static content is displayed by default. But when petite-vue mounts, initialized becomes true and the static content hides and the enhanced petite-vue content shows.


It’s a little more work, but in a lot of production cases, I find this pattern to be very approachable as a way to provide static content that is then progressively enhanced by JavaScript. I’ve shipped this pattern on a few sites already with great success (including this blog’s tag filtering functionality). The pattern can be broken down as follows: