I remember watching this video one year earlier. And now I'm better understanding the practices and problems nuxt are trying to solve. Nice framework .
The problem I have with nuxt, vue and all of that is no matter how much I research them, they lead to more research to the point I'm crippled in my ability to create something practical.
What's preventing you from stopping researching and just start doing? Premature optimization is the root of all evil. Just do it first, and deal with the problems later. If Facebook can start off with PHP, you'll be fine with barebones Vue.
Well that is web development in general (might as well as programming), and the fact that everything is always moving forward and change often happens in the industry. One always find ways to learn something new everyday, even senior devs also had to keep up with the trend (especially if the company requires it).
lol, what are you looking at? does the script keep moving to the left and right of you or are you pretending to look at the overlay animations....must know...
The horror you get from configuration of third party modules as well as inability to flexibly use global client side vars like window or document would distance you away from nuxt as far as possible.
@@themetracktor9574 Sure, but my comment is abstracted from anything to do with server side. Having a "production ready app" should not be hinged on SSR regardless.
@@Andrey-il8rh agreed, but the specific examples in the video were VueX, Vue Router, a proper folder structure etc. All these things are achievable with Vue CLI or just by using your own brain. More and more I see developers relying on bespoke tooling that's masked with voodoo rather than just learning how the damn thing works.
Hey Gregg! Sorry for the unrelated comment but I recently wondered what happened to the CodeSchool team and it's great to see you around! I've gotten my start on JS frameworks years ago with your AngularJS course and now that I'm looking into Vue I can't think of a better dude for the job. You rock my man, stay fresh.
So we are using vue.js to create a single page application, right? So now we are using nuxt.js to make the vue.js application to a multi page application... Well, imma make a new framework so we can create a nuxt.js application as a single page application :) All these js frameworks on top of js frameworks, combined with css frameworks combined with frontend frameworks like ionic 5 so we can make pwa combined with a backend containing js frameworks on js frameworks This shit is just crazy. Framework do have their place. But one should think about the purpose of an application before building it. If you want it high ranking in the search engine, don't build a single page application. If you need a single page app/ real time app then use a framework. If you need both, split them. Have one website under www.domain.com Have your app under app.domain.com. Link from the website to your app.
So.... Nuxt is bascially required for 99% of what people do with vue these days... so why isn't it part of the vue core? I see that a lot in the Javascript world; frameworks like react and vue are extremely popular, but you always need external libraries to make it work. An app basically cannot work without state so why is vuex a separate thing? Any website that takesitself seriously will rewuire SSR so why is Nuxt a separate thing? Don't tell me that it's because you can choose another library, because no, I can't.If I want to produce software that can be maintained by my collegues at diffeent companies then I must choose a popular, well documented library. Let me put it another way: in the PHP and Python world, there are no frameworks that provide only part of the stuff you need. They all have ways of talking to the database, ways of doign authentication etc. They *never* require that you figure out which library you can use to mae the thing work. Again I feel that the Javascrpit world is re-inventing the wheel of application development and making all the mistakes that the rst of the development world has fixed decades ag.
True dat! However, in the case of Vuejs it was meant to be like that... being a 'progressive' framework that can be implemented gradually according to the needs. Still, I generally agree with you.
server side frameworks have the benefit of only generating what you need and dont need to all be sent into the browser. basically without good codesplitting that would be a nightmare. Evan talks about the design decisions in a few talks. a big framework like Angular vs a small library like React, Vue sits in the middle with an aim to serve all kinds of different users . when i am creating an admin dashboard, i dont need ssr when am intergrating vue on only a small part of a page as a jquery replacement, i dont need state. and most time people never use the router its a progressive framework vuex and router still maintained by official vue team so no big deal
What are the problems with NUXT, waiting for that in the next video? --- Don't i need a node server for server side apps? Right now , i can deploy my static site with cloud functions to netlify or S3 with continuous integration. If i choose NUXT as a server side app, i need to find a high end node server and manage all the server security and everything that goes along with that... - am i wrong, i would like to be wrong as this is the only reason i have stated away from nuxt for the time being.
Yes, you are in fact wrong ;) Nuxt supports 3 different modes of building your app, one of which is a fully generated web site that doesn't need any complex server
so the mode you suggest is basically vue with opinionated folder structure and routing for dummies? ;) - im fine with plain old vue for that... i am interested in the ssr but that does need a node server.
Would be very interested in seeing a video specifically contrasting Nuxt with vue-cli. I'm sure there are advantages and disadvantages to each. I find it very odd that this video didn't even mention vue-cli.
@@juliamihet4237 vue-cli basically let's you quickly put together your own custom framework, with many of the same features as Nuxt, but using first-party tools (or substituting whatever you want). Nuxt is just too opinionated. I much prefer the Unix philosophy of combining multiple small tools that each do one job very well.
@@hackel137 Well, some people like opinionated frameworks like me. It saves me a ton of time so that I can focus on the core logic & value of the application.
I am new in Vue js i want to create a vue application with vue+vuetify+.net or webapi . Kindly tell me what is best practice. Or anyother .net or .entity framework library
Now someone is going to make another sub-framework for nuxt ....i dont think i need to read more docs i rather handle the configs than keep learning these framworks .Vue-cli is enouph.. thanks
what is the intro and outro beat/music you use for your videos. I really really love it, I could play it in the background while I code. Can it sheared?
@@tkdevlop -cli has good folder structure too, really can't see what is better by nuxt -just because you can create file? and what to do with settings, meta, naming, params? do not see really any dificulties with editing one single small file -as I can guess you can install only one plugin and will have SEO too -how? cli loads emty html with one js and css file, that can also be split up
@@tkdevlop Nuxt is useful for lazy & noob Vue developers... Any high-end JS developer won't have problems while producing with vue-cli... Btw if you don't know JS in advanced level don't produce any app !
Moving from one Nuxt application to another is super-simple? Best-practise folder arrangement? Are we 12? fwiw: that folder arrangement is hiding your actual application behind an arbitrary view of the world dictated by nuxt. Are you writing "a nuxt application" or are you writing "an application". It's awful practise to have your application hard-tied into a framework. See: MVC for reasons why.
Use regular Vue if: 1) You simply want to build a website that is static while also having the benefits of data reactivity. 2) You don't wanna use React and Angular
@@scottamolinari thanks dude. Found quasar ssr docs and looks quite capable. I am using quasar but was just looking into nuxt for ssr only. Now dont see any use for nuxt except it being bunch of conventions that anyways all projects should try to adopt.
@@Rivhoy6ivu7r Hi man what you think of nuxt vs quasar now? Really like vue.js. You think I should try quasar, like you mentioned dont see any point using nuxt since quasar offers ssr and much more.
Nuxt is server side framework for Vue while Next is for React.
5 років тому+2
Hi team, I love working with Vue. As a beginner, my question is that can NUXTJS help us to hide our API keys from client-side? If it can, would you be able to share the related documentation link?
i guess NUXT will need to sit on a node server somewhere, and you can store your API keys in a process.env file and then include that as you would normally as process.env.SECRET_API...... or store it in webpack somewhere.
I remember watching this video one year earlier. And now I'm better understanding the practices and problems nuxt are trying to solve. Nice framework .
Thanks a lot to you. Every time you teach us difficult topics very easily. That's why I love to learn from Vue Mastery.
Nicely explained with informative slides. Definitely going to check out nuxt now. Thanks you for the upload
The problem I have with nuxt, vue and all of that is no matter how much I research them, they lead to more research to the point I'm crippled in my ability to create something practical.
whenever you find something you like you have to create something with it
What's preventing you from stopping researching and just start doing? Premature optimization is the root of all evil. Just do it first, and deal with the problems later. If Facebook can start off with PHP, you'll be fine with barebones Vue.
use React
Well that is web development in general (might as well as programming), and the fact that everything is always moving forward and change often happens in the industry. One always find ways to learn something new everyday, even senior devs also had to keep up with the trend (especially if the company requires it).
Uh... Vue CLI 3 gets you mostly there, right?
Great video. Nuxt is the best framework.
lol, what are you looking at? does the script keep moving to the left and right of you or are you pretending to look at the overlay animations....must know...
Kamel Jabber lol. I was looking at the script. Strategically placed so it looked like I was looking at the screen. 😂
Video making tip: Put your teleprompter thingie somewhere higher.
I love Nuxt so far but think the visual flow diagram things in the docs are pretty hard to follow. Otherwise I love it. Sooo fast
I wonder why $nuxt variable is not readily available to be used in nuxt-ts project(maybe in nuxt js project too)! Same goes with $apollo.
how do i access window global object's property from vue component??
What about quasar?
is good!
The only thing i use nuxt for is SSR
Because all these other 6 reasons aren't really that helpful
Blade/php runs in the server and returns html to the client right?
It's literally not so good as it lacks many direct server features
How to have styles by layout? Nuxt is just applying the default styles to whatever layout.
I hate third party app like that.. I love pure Vuejs
vue is third party...
Nuxt is pretty awesome dude
I guess binary is your thing.
Don't use Nuxt. Use vue
Just use Vue-CLI, and your brain. None of these problems are real.
Exactly what I was thinking 🤭
True!!
😂😂😂
Why using Vue-CLI when you can use ES5 and your brain?
Why not using Angular app to render a Vue app both created with CLI ?
Nuxt is a very good framework, if you want to do it on your own, just please, do not use it ... and please stop complain about it.
"building production ready apps" - the benefits listed are all provided with the Vue CLI? That's hardly a benefit of Nuxt...
Nuxt is server side.
The horror you get from configuration of third party modules as well as inability to flexibly use global client side vars like window or document would distance you away from nuxt as far as possible.
@@themetracktor9574 Sure, but my comment is abstracted from anything to do with server side. Having a "production ready app" should not be hinged on SSR regardless.
@@jshrssll production level app is a very broad term and can mean a lot of different things
@@Andrey-il8rh agreed, but the specific examples in the video were VueX, Vue Router, a proper folder structure etc. All these things are achievable with Vue CLI or just by using your own brain. More and more I see developers relying on bespoke tooling that's masked with voodoo rather than just learning how the damn thing works.
It solves 7 problems but add multiple bugs on top of vue.js bugs.
can you please private this video since it's 4 years old and it was recommend to me today. Tnx.
Hey Gregg! Sorry for the unrelated comment but I recently wondered what happened to the CodeSchool team and it's great to see you around! I've gotten my start on JS frameworks years ago with your AngularJS course and now that I'm looking into Vue I can't think of a better dude for the job. You rock my man, stay fresh.
Same here, man! A lot of courses were watched at CodeSchool. All the best for Gregg!
I still have some of the pdfs from CodeSchool. I remember watching his video about Nodejs and not understanding anything 🤣.
Nuxt is indeed really great!
So we are using vue.js to create a single page application, right?
So now we are using nuxt.js to make the vue.js application to a multi page application...
Well, imma make a new framework so we can create a nuxt.js application as a single page application :)
All these js frameworks on top of js frameworks, combined with css frameworks combined with frontend frameworks like ionic 5 so we can make pwa combined with a backend containing js frameworks on js frameworks
This shit is just crazy. Framework do have their place. But one should think about the purpose of an application before building it.
If you want it high ranking in the search engine, don't build a single page application.
If you need a single page app/ real time app then use a framework.
If you need both, split them.
Have one website under www.domain.com
Have your app under app.domain.com.
Link from the website to your app.
nuxt is great but some vue plugins don't compatible with nuxt, when using vue-cli i follow best practice that nuxt implemented
So.... Nuxt is bascially required for 99% of what people do with vue these days... so why isn't it part of the vue core?
I see that a lot in the Javascript world; frameworks like react and vue are extremely popular, but you always need external libraries to make it work. An app basically cannot work without state so why is vuex a separate thing? Any website that takesitself seriously will rewuire SSR so why is Nuxt a separate thing? Don't tell me that it's because you can choose another library, because no, I can't.If I want to produce software that can be maintained by my collegues at diffeent companies then I must choose a popular, well documented library.
Let me put it another way: in the PHP and Python world, there are no frameworks that provide only part of the stuff you need. They all have ways of talking to the database, ways of doign authentication etc. They *never* require that you figure out which library you can use to mae the thing work.
Again I feel that the Javascrpit world is re-inventing the wheel of application development and making all the mistakes that the rst of the development world has fixed decades ag.
True dat! However, in the case of Vuejs it was meant to be like that... being a 'progressive' framework that can be implemented gradually according to the needs. Still, I generally agree with you.
server side frameworks have the benefit of only generating what you need and dont need to all be sent into the browser.
basically without good codesplitting that would be a nightmare.
Evan talks about the design decisions in a few talks. a big framework like Angular vs a small library like React, Vue sits in the middle with an aim to serve all kinds of different users
.
when i am creating an admin dashboard, i dont need ssr
when am intergrating vue on only a small part of a page as a jquery replacement, i dont need state.
and most time people never use the router
its a progressive framework
vuex and router still maintained by official vue team so no big deal
I'm seeing the nuxt codesandbox project now uses yarn. Is that what we should all be using as the latest best practice when running nuxtjs?
What are the problems with NUXT, waiting for that in the next video? --- Don't i need a node server for server side apps? Right now , i can deploy my static site with cloud functions to netlify or S3 with continuous integration. If i choose NUXT as a server side app, i need to find a high end node server and manage all the server security and everything that goes along with that... - am i wrong, i would like to be wrong as this is the only reason i have stated away from nuxt for the time being.
Yes, you are in fact wrong ;) Nuxt supports 3 different modes of building your app, one of which is a fully generated web site that doesn't need any complex server
I mentioned that ' if i choose nuxt as a server side app ' .. then i need a node server.. is this wrong?
so the mode you suggest is basically vue with opinionated folder structure and routing for dummies? ;) - im fine with plain old vue for that... i am interested in the ssr but that does need a node server.
Using Nuxt with Typescript is a pain to set up and with vuex Typescript, there are no official docs
Thank you😊
Does the Vue Cli-3 cover some of these problems and would one say that learning Nuxt is less important now?
Nuxt uses Vue.
could also just use svelte, and organize your code into pages and use a router.
@3:45 💖💖
i ddint knew zayn malik is coding vue too..
Would be very interested in seeing a video specifically contrasting Nuxt with vue-cli. I'm sure there are advantages and disadvantages to each. I find it very odd that this video didn't even mention vue-cli.
vue-cli is just a cli for Vue.js. Why would somebody compare a cli with a framework?
@@juliamihet4237 vue-cli basically let's you quickly put together your own custom framework, with many of the same features as Nuxt, but using first-party tools (or substituting whatever you want). Nuxt is just too opinionated. I much prefer the Unix philosophy of combining multiple small tools that each do one job very well.
@@hackel137 Well, some people like opinionated frameworks like me. It saves me a ton of time so that I can focus on the core logic & value of the application.
I am new in Vue js i want to create a vue application with vue+vuetify+.net or webapi .
Kindly tell me what is best practice.
Or anyother .net or .entity framework library
ありがとうございます！知りたいことが理解できました
Now someone is going to make another sub-framework for nuxt ....i dont think i need to read more docs i rather handle the configs than keep learning these framworks .Vue-cli is enouph.. thanks
what is the intro and outro beat/music you use for your videos. I really really love it, I could play it in the background while I code. Can it sheared?
Basically what rails does for developers. Less configuration. I love it
I am using Angular... How does this fit with Nuxt? I'm confused. Please explain.
it doesn't
more real courses will be nice..
pratical. medium and large applications. deploy etc..
isnt this the same as Next.js for react? well giving a proper structure to react and vue apps is what next and nuxt is doing isnt it
a framework for a framework: a Meta Framework
And what is the difference from current vue-cli?
Better folder structure
Easy routing
Seo support
Intial page load faster.
@@tkdevlop
-cli has good folder structure too, really can't see what is better by nuxt
-just because you can create file? and what to do with settings, meta, naming, params? do not see really any dificulties with editing one single small file
-as I can guess you can install only one plugin and will have SEO too
-how? cli loads emty html with one js and css file, that can also be split up
@@tkdevlop Nuxt is useful for lazy & noob Vue developers... Any high-end JS developer won't have problems while producing with vue-cli... Btw if you don't know JS in advanced level don't produce any app !
@@hyp3ri0nn Aren't the best developers lazy by default?
@@Quabbe2 Amen brothaa
should i learn vuejs first? or can i start with nuxt?
start with Vuejs, then come back to nuxtjs if you wanted to take advantage of the features it provides
Hmmmm
Moving from one Nuxt application to another is super-simple? Best-practise folder arrangement? Are we 12? fwiw: that folder arrangement is hiding your actual application behind an arbitrary view of the world dictated by nuxt. Are you writing "a nuxt application" or are you writing "an application". It's awful practise to have your application hard-tied into a framework. See: MVC for reasons why.
That part is totally optional. You can disable all parts of nuxt you don't like.
Well, as others has already implied, I have counter question - why use regular Vue instead of Nuxt?
Use regular Vue if: 1) You simply want to build a website that is static while also having the benefits of data reactivity. 2) You don't wanna use React and Angular
Will you cover Gridsome when it comes out?
best idea ever
Sounds great, but those problems don't apply to my project
You all should have a look at Quasar Framework. Does Nuxt stuff and a whole lot more.
thats spa not ssr
@@Rivhoy6ivu7r What's SPA, not SSR? Quasar? Look again.
@@scottamolinari thanks dude. Found quasar ssr docs and looks quite capable. I am using quasar but was just looking into nuxt for ssr only. Now dont see any use for nuxt except it being bunch of conventions that anyways all projects should try to adopt.
@@Rivhoy6ivu7r Hi man what you think of nuxt vs quasar now? Really like vue.js. You think I should try quasar, like you mentioned dont see any point using nuxt since quasar offers ssr and much more.
Is nuxt.js anyway related to next.js?
Nuxt is server side framework for Vue while Next is for React.
Hi team, I love working with Vue. As a beginner, my question is that can NUXTJS help us to hide our API keys from client-side? If it can, would you be able to share the related documentation link?
i guess NUXT will need to sit on a node server somewhere, and you can store your API keys in a process.env file and then include that as you would normally as process.env.SECRET_API...... or store it in webpack somewhere.
nuxt using server rendering so why its could be better than php?
Yes. It beats laravelvue combonation.
lovely tips thanks... time to try nuxt out
I tried to intigrate mdbvue to nuxt and it didn't work, please solve the problem
Is it possible to convert Nuxt.js to Android while it's using server side rendering?
No, use React if you want to have native android frontend for your project
Please stop looking at your cheat sheet, it's very distracting...
next js
Hi, can we use jsx with Nuxt?
I tweeted this