Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/jeffreyguenther/vue-turbolinks
A Vue mixin to fix Turbolinks caching
https://github.com/jeffreyguenther/vue-turbolinks
cache mixins rails turbolinks vue vue-components webpacker
Last synced: about 3 hours ago
JSON representation
A Vue mixin to fix Turbolinks caching
- Host: GitHub
- URL: https://github.com/jeffreyguenther/vue-turbolinks
- Owner: jeffreyguenther
- License: mit
- Created: 2017-04-04T19:02:50.000Z (almost 8 years ago)
- Default Branch: master
- Last Pushed: 2021-04-12T13:00:54.000Z (almost 4 years ago)
- Last Synced: 2025-01-15T05:24:29.764Z (7 days ago)
- Topics: cache, mixins, rails, turbolinks, vue, vue-components, webpacker
- Language: JavaScript
- Homepage:
- Size: 34.2 KB
- Stars: 285
- Watchers: 10
- Forks: 20
- Open Issues: 1
-
Metadata Files:
- Readme: README.md
- Changelog: CHANGELOG.md
- License: LICENSE.md
Awesome Lists containing this project
README
# A Turbolinks & Hotwire Adapter for Vue components
vue-turbolinks is a package to allow you to easily add Vue.js components
to your Turbolinks & Hotwire powered apps. We handle the events to
properly setup and teardown your Vue components on the page.
#### Supported Libraries
* [Hotwire's Turbo.js](https://turbo.hotwire.dev/)
* [Turbolinks](https://github.com/turbolinks/turbolinks)
>:warning: If you're using [vue-router](https://github.com/vuejs/vue-router) or another
Javascript routing library, you don't need to use Turbolinks or this adapter.
Turbolinks is meant to level up the traditional request-render cycle
by loading the new page in the background and this adapter makes it possible
to use Vue components on pages rendered in this manner. If you've decided to
use a single-page app, you already have everything you need. :metal:
To use this in a Rails project with [webpacker](https://github.com/rails/webpacker) support:
``` bash
$ ./bin/yarn add vue-turbolinks
```
To use the mixin, include it where you setup your component.
For example, if you used `rails new myapp --webpack=vue` to create your project using
webpacker, you'll include it in your `hello_vue.js` file:
### Mixin Option 1: Global
``` javascript
import TurbolinksAdapter from 'vue-turbolinks';
Vue.use(TurbolinksAdapter);
document.addEventListener('turbo:load', () => {
const vueapp = new Vue({
el: "#hello",
template: '',
components: { App }
});
});
```
### Mixin Option 2: Single Component
``` javascript
import { turbolinksAdapterMixin } from 'vue-turbolinks';
document.addEventListener('turbo:load', () => {
const vueapp = new Vue({
el: "#hello",
template: '',
mixins: [turbolinksAdapterMixin],
components: { App }
});
});
```
### Running Vue only on specific pages
If you want your Vue component to run only on certain pages, you can
conditionally initialize it:
``` javascript
import TurbolinksAdapter from 'vue-turbolinks';
Vue.use(TurbolinksAdapter);
document.addEventListener('turbo:load', () => {
const element = document.getElementById("hello");
if (element != null) {
const vueapp = new Vue({
el: element,
template: '',
components: { App }
});
}
});
```
Or you can use a library like [Punchbox](https://github.com/kieraneglin/punchbox) whose JS is available for the asset pipeline or on [NPM](https://www.npmjs.com/package/punchbox-js).
### Options
You can pass in `destroyEvent` if you would like to customize which event Vue is torn down on. By default, this uses `turbo:before-cache` or `turbolinks:before-cache`.
`Vue.use(TurbolinksAdapter, { destroyEvent: 'turbo:before-cache' });`
### A note on transitions
If a `$root` component's **root node** is a Vue `` then calling the `$destroy` method may fail, throwing `NoModificationAllowedError: Failed to set the 'outerHTML' property on 'Element'` errors on the next `turbo:visit` event. To prevent this, wrap the `transition` in a DOM element:
Instead of:
```html
...
```
do:
```html
...
```