Anywhere! You don't need to think too much about NgModules anymore. All components are standalone and have their own imports section without having to rely on a module registrations.
Here's two: 1. To lazy-load individual components instead of modules. 2. To write a lot less code than having to maintain ng-modules (with all the mess they involve: circular dependencies, etc.)
Hello Angular Team we are migarate our code from Angular 12 to Angular 17 and that working fine! we are facing the issue on update the build on server (deploye on server), one we are create the build with "ng build" and its generate the dist folder and we are try to upload dist on server but its not working can you made video on how to upload the build on server? or can you guide for the same? Thank you
I don't really get the move towards standalone components. Having to define all your dependencies again and again, just makes it tedious and cluttered. If in some way it would help decrease the clutter for writing tests, sure go ahead but it just doesn't hold a lot of benefit imo. Especially if you create one of those standard applications that most people will use Angular for.
I think the motivation is to reduce the learning curve. What you said is true, but the upside is you don't have to understand modules and all those other pre-requisites just to produce something useful.
There are always trade offs, but one that I can think of that I do like about standalone is I can create a reusable component without having to import a shared module just to use that one component in another component/module. It does annoy me to have to import common module all the time, but again, it's a trade off.
Not a lot of benefit? NgModules are basically a black box. I keep trying to find my component's dependencies and I jump from ngmodule to ngmodule trying to figure out what goes where - it's ridiculous. Also defining providers inside routes files is sooo much cleaner than having to manage this ngmodule hell. Standalone component are a godsent gift!
One of the main benefits is not having to import an entire module with all the components it might contain if you're using just 1 of them. Also reduces complexity as you don't risk to have circular dependencies between modules and having to mess around on how to organize them. Overall organization is much cleaner and easier. And you hardly use that many directives and components to having to import a huge list of them and have the imports section taking half your file... Unless you're too bad at designing your components 😅
3:03 "you can even create your own transforms, the only limit is your imagination" - nope, there is one important caveat, the transform has to be a simple, pure function, so the static analysis would understand; this is pretty limiting
vite is buggy in v17. i'm finding myself needing to restart the dev server quite often. it rarely recovers from build errors. especially with scss. the old dev server was much more robust.
Same, but it's just the beginning guys. It is super great that they're switching to Vite and I believe it will get as robust as the webpack builder very soon!
I think all these JS libraries are bound to die one day. They are unnecessarily complicated, have too long build times and very high initial learning curves. Something much more simpler, easier and efficient is needed.
Check out our website → goo.gle/AngularDev
Thanks Angular team for such awesome website 🎉
Add some material Icon. It help to not use any other library for icons. Please thing about this point. You guys are working awesome. ❤❤ thank alot.
glad angular has brought about these changes, looking forward to further improvements
Thank you.
Thank you for this release.
your team is awesome.
I need a proper testcase or scenerio where this standalone can be useful in a big Enterprise application
Anywhere! You don't need to think too much about NgModules anymore. All components are standalone and have their own imports section without having to rely on a module registrations.
@@CesarDemi81and they should occupy a half of a length of the file 😁
@@ThePilesosjust don't write so huge components
Here's two: 1. To lazy-load individual components instead of modules. 2. To write a lot less code than having to maintain ng-modules (with all the mess they involve: circular dependencies, etc.)
In many projects I've found giant modules with components not used anymore but not removed. They just add unnecessary size to result bundle
Nice angular vite👍
Hello Angular Team
we are migarate our code from Angular 12 to Angular 17 and that working fine!
we are facing the issue on update the build on server (deploye on server), one we are create the build with "ng build" and its generate the dist folder and we are try to upload dist on server but its not working
can you made video on how to upload the build on server? or can you guide for the same?
Thank you
Angular 😍😍😍
Thanks for your updates! BTW Somebody already made any code obfuscation with Angular 17?
Is it true Angular is turning away from webpack?
The answer is in the video.
I don't really get the move towards standalone components. Having to define all your dependencies again and again, just makes it tedious and cluttered. If in some way it would help decrease the clutter for writing tests, sure go ahead but it just doesn't hold a lot of benefit imo. Especially if you create one of those standard applications that most people will use Angular for.
I think the motivation is to reduce the learning curve. What you said is true, but the upside is you don't have to understand modules and all those other pre-requisites just to produce something useful.
There are always trade offs, but one that I can think of that I do like about standalone is I can create a reusable component without having to import a shared module just to use that one component in another component/module. It does annoy me to have to import common module all the time, but again, it's a trade off.
Not a lot of benefit? NgModules are basically a black box. I keep trying to find my component's dependencies and I jump from ngmodule to ngmodule trying to figure out what goes where - it's ridiculous. Also defining providers inside routes files is sooo much cleaner than having to manage this ngmodule hell. Standalone component are a godsent gift!
One of the main benefits is not having to import an entire module with all the components it might contain if you're using just 1 of them. Also reduces complexity as you don't risk to have circular dependencies between modules and having to mess around on how to organize them. Overall organization is much cleaner and easier. And you hardly use that many directives and components to having to import a huge list of them and have the imports section taking half your file... Unless you're too bad at designing your components 😅
Hmmm... I've gotta get through Sololearn, 😂
3:03 "you can even create your own transforms, the only limit is your imagination" - nope, there is one important caveat, the transform has to be a simple, pure function, so the static analysis would understand; this is pretty limiting
vite is buggy in v17. i'm finding myself needing to restart the dev server quite often. it rarely recovers from build errors. especially with scss. the old dev server was much more robust.
In the same situation myself. Even if it's much faster, having to restart often is very frustrating.
Same situation
Same, but it's just the beginning guys. It is super great that they're switching to Vite and I believe it will get as robust as the webpack builder very soon!
I think all these JS libraries are bound to die one day. They are unnecessarily complicated, have too long build times and very high initial learning curves. Something much more simpler, easier and efficient is needed.