Vuejs js for multiple pages, not for a single page application

laravel vue.js laravel-5.3 vue-component vuejs2

21,362

Solution 1

Create your 'app' for every page in seperate JS files. Good practice would be using the same name as page name to get it clear where it belongs.
Name you main div the same as the file (fileName.php + assets/js/fileName.js).
Use #fileName' as yourel`
in blade use @{{ vue expressions }} to let Blade skip this and allow VueJS handle that.

Done. Good luck!

Solution 2

If you want to sprinkle a bit of vuejs within your blade files you have basically two options:

Option #1

Declare global Vue components

Example

// in laravel built in app.js file

Vue.component('foo', require('./components/Foo.vue'));
Vue.component('bar', require('./components/Bar.vue'));

const app = new Vue({
    el: '#app'
});

create a main layout file where the root div has an id of #app

// layout.blade.php

<html>
  <header></header>
  <body>
    <div id="app">
      @yield('content')
    </div>
  </body>
</html>

Finally in your views:

//some-view.blade.php

@extends('layout')

@section('content')
 <foo :prop="{{ $someVarFromController }}"></foo>
@endsection

Option #2

This is what I am currently using, and gives me more flexibility actually

// in laravel built in app.js file

const app = new Vue({
    el: '#app',
    components: {
      Foo: require('./components/Foo.vue'),
      Bar: require('./components/Bar.vue')
    }
});

In the layout file you will be using vuejs dynamic components

<html>
  <header></header>
  <body>
    <div id="app">
      @if (isset($component))
        <component :is={{ $component }} inline-template>
      @endif

         @yield('content')

     @if (isset($component))
       </component>
     @endif
    </div>
  </body>
</html>

In your views:

//some-view.blade.php

@extends('layout', ['component' => 'foo'])

@section('content')
   // all the vue stuff available in blade
   // don't forget to use the @ symbol every time you don't want blade to parse the expression.
  // Example: @{{ some.vue.propertie }}
@endsection

And finally you can create the vue components like you always would

// resources/assets/js/components/foo.vue

<script>
export default {
 // the component
}
</script>

21,362

Dinuka Thilanga

I was software engineer at eMarketingeye. Now i am Senior Software engineer at eFutures.

Updated on July 17, 2022

Comments

Dinuka Thilanga almost 2 years
I need to build an application using laravel 5.3 and vuejs 2, because I need to use two-way binding rather than use jquery.

I need to set up the views with blade templates. Then, I need to use vuejs in each page as mentioned below.

resources/asserts/js/components/List.vue
```
<script>
    const panel = new Vue({
        el: '#list-panel',
        name: 'list',
        data: {               
           message: 'Test message'
        },
        methods: {
            setMessage: function(){
                this.message = 'New message';
            }
        }
   })
</script>
```
resources/asserts/views/post/index.blade.php
```
<div id="panel" class="panel panel-default">
    <div class="panel-heading">Posts</div>

    <div class="panel-body">
       <p>{{ message }}</p>
       <button v-on:click="setMessage">SET</button>
    </div>
</div>
```
There is Add.vue to create.blade.php etc... In Add.vue el: '#add-panel'

This is my app.js. I already commented default code like follows.
```
Vue.component('list', require('./components/List.vue'));
Vue.component('add', require('./components/Add.vue'));

// const app = new Vue({
//     el: '#app'
// });
```
I hardly checked most of documentations and tutorials. But they use a single js file. They use components for small elements with template, not only js.

Is it possible to use vuejs this way? Do I need to use app.js. What is the best way to do this?
- Frnak over 7 years
  
  I'm not quite sure about your problem, however it is not meant to only create single page applications using vue. By default you do not even get the vue router. I'd suggest to simply define an inline componenet (usually a "home" component) in your blade layout file. You register your vue to an outer element (body or #app). All the other components are simply added as your already did using Vue.component. You can then define your blade templates and simply use everything of vue inside.
Prakhar almost 7 years

Option 2 seems an interesting approach.. specially for multi-page applications. However, my concern is ,if I have 50 components in my app I would end up loading all those in app.js even when i dont need them ... I was trying to find something that could be more dynamic where components could load on demand
Helder Lucas almost 7 years

To solve that you can declare your components in an async way like so: Vue.component('my-component', () => import('./my-component')). See it in more detail at: vuejs.org/v2/guide/components.html#Async-Components
Jeffrey almost 7 years

You are essentially creating a new instance of Vue for every page. right?
Mihai over 6 years

@Pyol7 Yes, that's what he's describing.
general666 over 4 years

What about SEO in this case?
Istiaque Ahmed over 4 years

So what will the app.js file contain ? Can you elaborate it with a folder structure with files ?
Istiaque Ahmed over 4 years

do we need to use the route declaration of VueJS in a file i.e. router.js and import it in app.js as we do for a SPA (Single Page application) ?
Istiaque Ahmed over 4 years

Regarding option 2: @extends('layout', ['component' => 'foo']) - how can the Laravel blade get the foo variable here ?
Istiaque Ahmed over 4 years

can you answer this question with the related topic : stackoverflow.com/questions/59289548/… ?
xslibx almost 4 years

I'm getting an error Property or method "[component name]" is not defined on the instance but referenced during render. The [component name] is what is set as the @extends('layout', ['component' => 'componentname])`. Any ideas?
Helder Lucas almost 4 years

@xslibx did you register your component? Vue.component('componentname', Component...) ?
leachim over 2 years

take care that this is not best practice and you will run into issues since this will create a new vue instance for every page. With this setup you'll not be able to use vuex store correctly, since the store cannot be shared across vue instances.