Ask A Question

Notifications

You’re not receiving notifications from this thread.

Vue.js Components in Rails Views Discussion

Nice video. What about Vue state managment in Rails. When one Vue component mess with state of another Vue component?
Reply
Chris had done a really nice tutorials for Vue + statemanagement  tutorial series https://gorails.com/series/vuejs-trello-clone-in-rails

Reply
Hey Chris

How would you go about showing images uploaded via ActiveStorage on your vue components?
In ERB the image tag magically renders the image, but I'm not so sure how it would work on the webpacked vue files.
Reply
This approach makes for nice DRY looking code. Beware of what happens what browsers parse HTML into the DOM, though. For example, if you write 

<table>
  <row-component></row-component>
  <row-component></row-component>
</table>
the browser may say "hey, the row-component element is not valid inside a table!" during parsing and hoist them out, making it effectively
<row-component></row-component>
<row-component></row-component>
<table></table>
before Vue runs, which is not what you wanted, and there are other cases besides. Arguably it's always a concern when mounting components on an existing document, but becomes more likely when writing in this style.
Reply
Great episode Chris! Would it be possible to have something similar to stimulus [1] `definitionsFromContext` helper. A strong [naming] convention would reduce the manual import of vue components. Do you have a smart idea on this?
Reply
Reply
Second time I tried to install webpack and vue. Keep getting this error and I don't have a clue as to how to fix it. rails installed both webpacker and yarn ok, and I have node on my system. Here's the error:
Webpacker can't find application.js in /home/tom/paul/public/packs/manifest.json. Possible causes:
1. You want to set webpacker.yml value of compile to true for your environment
   unless you are using the `webpack -w` or the webpack-dev-server.
2. webpack has not yet re-run to reflect updates.
3. You have misconfigured Webpacker's config/webpacker.yml file.
4. Your webpack configuration is not creating a manifest.
Your manifest contains:
{
}
You never seem to get errors. How is that?
Reply
Hi Chris, nice work in this. I'm really excited about VueJS and the potential it has to streamline the Rails frontend dev process.

Some simple handy component examples would be very helpful ie. Form components like file_field with appropriate behaviour or table rows with CRUD actions.
Reply
Ok, after some research I found bootstrap-vue, which makes it easy to build out these components and super easy to drop them into a Rails app.
https://bootstrap-vue.js.org/docs/#individual-components-and-directives
Reply
Pure gold.
Reply
Thanks
  
By following your pattern with Turbolink/ [and data-behavior="vue »], it works perfectly on localhost, but yield not load in production (heroku) even if build success, and compiling asset «seems» good.  
  
Have you already got that type of behavior  ?

thanks
Reply
Unfortunately, this cool method is not a better way to include components to an existing layout.

First of all, VUE will parse all the page, starting from data-behaviour="vue". So it could be a really hard load.

The second, parsing the page rewrites the DOM. So all your other non VUE stuff and events won't work anymore (like jQuery or Bootstrap plugins, etc.) Or they must be initialized after VUE did its job.

So it could be a trick to make them work together.

Reply

Using this approach, how would you get rails data into a component?

Eg. In "Using VueJS for Nested Forms in Rails: Part 1" you get a reference to the form div element and then parse the element dataset. But with this approach the element could be anything and how would you get a reference to the element in a SFC?

Reply

Unfortunately, I'm seeing the same behavior as Alexandre Duval; this works great in the development environment, but silently fails in production after precompiling assets. Are there some config changes needed to get this working after precompilation?

Reply

FWIW to anyone having similar problems, I struggled with this because the webpacker docs instruct you to allow unsafe-eval in development without making the implications of this clear for production.

Reply

All work good! Thx for lesson. But i have an issue whan using ckeditor gem. Got error on pages with ckeditor :""[Vue warn]: Error compiling template:

...". Donno how to fix this collision.

Reply

This is really neat.

Reply

So, which way is best to implement Bootstrap and Vue in Rails 5.2? Keep the original Bootstrap4/jQuery sass lineup and use Vue where it is needed or a setup with Bootstrap-Vue ( https://bootstrap-vue.js.org )?

Reply

Brilliant streamlining technique by adding vue into the data-behavior! #gamechanger

Reply

Great tutorial, this was exactly what I needed to make including vue components not feel kludgy! This should be included in the vue webpacker example, seems like a very elegant solution.

Reply

Chris, thank you for amazing tutorial. I have one question, you didnt cover in this video.
How to deal with ajax loaded content?

Lets say we have remote link, wich JS response dynamically creates modal box (fancybox form example) with html content.

The problem is that if that modal's html content includes "components" tags, they are not initialized as (converted to) working Vuejs components. How to make Vuejs work with Rails ajax functionality?

Reply

Thanks for the insight Chris. It took me a while to wrap my head around this one.

Reply

Using the inline-template in this way is an interesting way to use ERB inside your Vue components, but is there a way to do that using the traditional single-file-component approach? Something along the lines of the rails-erb-loader to create ###.vue.erb files?

Reply

Did any of you guys solve this for production yet?

Reply
Join the discussion
Create an account Log in

Want to stay up-to-date with Ruby on Rails?

Join 82,329+ developers who get early access to new tutorials, screencasts, articles, and more.

    We care about the protection of your data. Read our Privacy Policy.