How to use Vue 3 and Meta-Tag (Options API) - vue.js

How can I implement Meta Tag in vue 3 with options api?
please provide any work around, plugins or code snippets.
Thanks for you help.

There is package vue-meta which you can use, see this post for more details.
This package vueuse/head maybe more reliable though i havent used it personally.

Related

Do I have to use the Composition API in Vue 3, or can I still do things the "Vue 2" way?

Is it possible to install Vue 3, but still do things the "Vue 2" way? In other words, I see that Vue 3 has the new Composition API, but is that optional or the required way of doing things in Vue 3?
For some reason, I was thinking that Vue 3 still allowed you to do things the Vue-2 way, using the Options API instead. Is that not the case? Thanks.
Vue 3 does not require using the Composition API. The Options API is still available and will not be removed, as explained by two Vue core team members:
Thorsten Lünborg in Vue 3: Data down, Events up (19-MAY-2020):
IMPORTANT: The composition API is additive, it’s a new feature, but it doesn’t and will not replace the good ole “Options API” you know and love from Vue 1 and 2. Just consider this new API as another tool in your toolbox that may come in handy in certain situations that feel a little clumsy to solve with the Options API.
Ben Hong in Enjoy the Vue #48: "New in Vue 3: The Composition API" (19-JAN-2021):
[00:01:03] T: Yeah. Well, the first thing I remember hearing was that it was replacing the options API.
[00:01:08] BH: Big disclaimer. That isn’t happening. Big disclaimer.
...
[00:09:10] BH: [...] this is not something you need to go and rewrite your app in. [...] the composition API is not like, drop the options do composition. It's an additive thing that when you have a problem that it can solve, it's really great for that.
An early RFC for the Composition API had only considered deprecating the Options API:
A previous draft of this RFC indicated that there is the possibility of deprecating a number of 2.x options in a future major release, which has been redacted based on user feedback.
The Vue docs also confirm this:
Will Options API be deprecated?
No, we do not have any plan to do so. Options API is an integral part of Vue and the reason many developers love it. We also realize that many of the benefits of Composition API only manifest in larger-scale projects, and Options API remains a solid choice for many low-to-medium-complexity scenarios.

VUEJS SSR, how to?

I made a VueJS 3 app (WebPack 3.12.0), with prerendering (not serverside), and the content of some page are loaded via ajax request, so google bots can't see the text (this is the problem here).
I read that I need to use SSR to do this. So I tried a couple of tutorials but no one seem to works (some do nothing, others crashes my app). I don't really know which one is the best and they are all using differents solutions.
First of all, do I need to use SSR to achieve what I want ? And if yes, anyone have a good tutorial (and a working one) ?
Thanks guys !
The best solution for SSR with Vue is to use Nuxt.js: https://nuxtjs.org/
It's not that complex, working really great !
It will probably be migrated to Vue3 really soon (Nuxt 2.15.2 is using Vue2 still), maybe even today during the JS World Conference.
Also, you can check those videos of Debbie who does a nice job of explaining things in a clear and simple way: https://www.youtube.com/c/DebbieOBrien/videos

How can I use CKEditor 5 classic in VueJS 2 WITHOUT NPM?

My question is simple. I'm using VueJS 2, and I want to implement CKEditor 5 Classic. I know better than to just hook it up in HTML, but due to constraints I can NOT use NPM/Webpack. I need a component wrapper that's in JS format.
Can anyone help?
What do you mean when you say "I know better than to just hook it up in HTML"? After all, the files are included in your HTML anyways, that's how HTML works with JavaScript.
The best option is to use the corresponding source-file from CDN of CKEditor. Either by including the direct CDN link or (in case you have doubts about availability) after you download them manually or via shell and ship them with your application.
If you don't want to go one of these ways, I don't think you'll be able to use the desired library at all.

React Admin : How to use bootstrap instead of Material Design?

and first of all thank you for your amazing work.
The README file indicates that it is possible to use Bootstrap instead of Material Design, but I can’t find any documentation of how to implement it.
Does anybody has already done that ? Thank you in advance :)
Unfortunately, we did not find the time to document the ra-core package properly yet, so you'll have to explore the source code for now. I doubt you'll find any example for doing this as the separation into two packages (ra-core and ra-material-ui) is quite recent.
Be aware that building a bootstrap version of react-admin will take a lot of time. You'll have to explore the ra-material-ui package and build a bootstrap version of every components.

Alternate for template engines in express

I dove into express.j and encountered pug (template engine).Now, i don't like the idea of writing code that works very similar to HMTL+ some identation.I'd rather stick with normal HTML.I want to discard view engines altogether . Is there another way to hook these html,css and javascript files instead of pug.I read Angular is utilized. Could someone elaborately with a form examlple,styled with css and how to integrate Angular with express.js . Perhaps any tutorial available online...
P.S. Please refrain from using too much technical terminology..I'm a noob. Simple english is appreciated.
You can use 'handlebarsjs'.
That is a great tutorial to get start.
https://www.youtube.com/watch?v=1srD3Mdvf50
Good luck.