npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

@tofandel/inertia-vue-modal

v0.2.26

Published

Load any inertia route into a modal

Downloads

31

Readme

Inertia Vue Modal

Limitations

This POC is a very early draft, so these limitations will probably be fixed soon.

  • No support for nested modals (modal in modal)
  • It doesn't use browser history navigation

Installation

Client-side installation

composer require tofandel/inertia-vue-modal && npm i vendor/tofandel/inertia-vue-modal

In your layout, you need to add the InertiaModal component, here is an example using the Quasar Dialog


<template>
  <div class="min-h-screen">
    <nav></nav>

    <!-- Page Content -->
    <main>
      <slot />
    </main>

    <InertiaModal>
      <template #default="{close, props}">
        <QDialog
            :model-value="true"
            v-bind="props/* props contains the modalProps option */"
            @update:model-value="close"
        >
          <ModalSlot />
        </QDialog>
      </template>
    </InertiaModal>
  </div>
</template>

<script setup>
import { InertiaModal, ModalSlot } from "@tofandel/inertia-vue-modal";
</script>
Axios dependency

It's very important that your project only uses one version of axios because of the use of interceptors, if you use webpack and your packages have conflicting versions of axios they will each be bundled separately and interceptors won't work To resolve this issue make sure that you add this to your webpack.config.js

const path = require('path');

module.exports = {
  resolve: {
    alias: {
      //...
      'axios': path.resolve('node_modules/axios/dist/axios.js'),
    },
  },
  //...
}

Server-side installation

In your Laravel application, you need to extend our HandlesInertiaModalRequest middleware

<?php

namespace App\Http\Middleware;

//...
use Tofandel\InertiaVueModal\HandlesInertiaModalRequest;

class HandleInertiaRequests extends HandlesInertiaModalRequest
{
//...
}

Usage

Since we added the InertiaModal component, the global $inertia object now has a visitInModal method. This allows you to make an Inertia visit that loads into the modal.

You can use this method, for example, in the @click handler of a button:

<button @click="$inertia.visitInModal('/user/create')">Load in modal</button>

Instead of using the method in your template, you can also use it in your script:


<script setup>
import { Inertia } from "@inertiajs/inertia";
Inertia.visitInModal('/user/create', {
  // Visit options
  
  // This is passed as additional page props to the page component of your modal
  pageProps: {
    componentProps1: 'page',
  },
  // This is passed as `props` in the InertiaModal default template
  modalProps: {
    modalProps1: 'modal',
  }
});
</script>

Update the page you want to load into a modal

In most cases, the /user/create endpoint renders a form that's wrapped into a template, maybe with other components and components to style the form. Here's a simple example of what the UserCreate.vue component might look like:

<template>
  <QLayout>
    <QPageContainer>
      <form @submit.prevent="form.post('/user/store')">
        <input type="text" v-model="form.name">
        <input type="email" v-model="form.email">

        <button type="submit">Login</button>
      </form>
    <QPageContainer>
  </QLayout>
</template>


<script setup>
import { useForm } from '@inertiajs/inertia-vue3';

const form = useForm({
  name: "",
  email: "",
});
</script>

To load this form into a modal, we don't want the sidebar, footer, and styling from the form-panel component. We want just the form itself!

To accomplish this, you need to do three things:

  1. Add the IsModalable mixin to your component.
  2. Wrap your whole component into the Modalable component.
  3. Move the form to a separate #toModal template and replace it with a ToModal component.

<template>
  <!-- the new Modalable root component -->
  <ModalableWrapper>
    <!-- the 'old' root component -->
    <!-- This will be wrapped around the #modal template but only when NOT within a modal -->
    <QLayout>
      <QPageContainer>
        <!-- the previous location of the form, replaced by the ModalSlot component, which will render the #modal template -->
        <ModalSlot />
      </QPageContainer>
    </QLayout>

    <template #modal-only>
      <!-- This will be wrapped around the #modal template but only when within a modal -->
      <QCard>
        <QCardSection>
          <!-- will render the #modal template -->
          <ModalSlot />
        </QCardSection>
      </QCard>
    </template>
    <template #modal>
      <!-- This is the content that is always shown -->
      <!-- the 'new' location of the form -->
      <form @submit.prevent="form.post('/user.store')">
        <input type="text" v-model="form.name">
        <input type="email" v-model="form.email">

        <button type="submit">Login</button>
      </form>
    </template>
  </ModalableWrapper>
</template>

<script setup>
import { ModalableWrapper, ModalSlot } from "@tofandel/inertia-vue-modal";
import { useForm } from '@inertiajs/inertia-vue3';

// This is where pageProps is received
defineProps({
  componentProps1: String,
  otherRenderProps: null,
});

const form = useForm({
  name: "",
  email: "",
});
</script>

Now when you visit /user/create, nothing has changed! You still have your layout and form-panel styling. But when you load this component into a modal, it will only render the form.

Handling redirects

By default, redirects are handled as any other Inertia request. For example you're visiting /user, you open /user/create in a modal, and after a successful submit, you redirect the user to the detail page of the newly created user:

public function store(UserStoreRequest $request)
{
    $user = User::create(...);

    return redirect()->route('user.show', $user);
}

You might not always want to route to the detail page. Luckily, you don't have to update your server-side implementation.

The visitInModal method accepts a second argument that can either a Boolean or a callback. Instead of redirecting the user, the user stays on the same page, and you can manually handle the event with the callback. This callback is executed after a successful request, for example, when the new user is stored in the database.

this.$inertia.visitInModal('/user/create', {
  redirectBack: (evt) => {
    // Do something
  },
});