New in Angular 14 – Standalone Components and Optional Modules (2022)

ще раз подивився відео, трішки освіжив скіли. дякую.

One of things i love about Angular is its modularity...And they are trying to take it away from Angular. Without modules, it will be another react sh*t. Unreadable, unscalable and shitty structure !

Только мне все эти импорты-экспорты в модулях кажутся путанными и не интуитивными? Новая система, вроде, чуть попроще. Но не менее путанная.

Mah-jewel

After introducing standalone component, if that ngModule contains many dependencies, then need to imports them all in each component, so in this way code length will be even more bigger. I would be prefer to have ngModules and this is more organized.
May I know the exact reason this introduction?

I'm still struggling to see what issue Standalone Components is solving?
So far it seems like the only benefit is getting rid of the modules file, but now you have to copy paste all those imports to every single component that needs them. It is not easier to just put them in one file, you know, the modules file? 😅
The only place I genuinely can see for this is a shared module that has little, if any dependencies, but is instead depended heavy on. So maybe a component library, i.e. the Angular Material project. It's really the only place I see this making sense 🤔

Thanks for video
ha, back to good old times) I remember NgModule was introduced in Angular 4. There were no modules since Angular 2 was introduced, so I remember the pain of migrating the existing projects to it

I have to double check that I have hit the like button!, great job!

Great video! Helped me a lot to migrate my own angular app (created for learning) to standalone components. I really appreciate!

now remove the need to explicitly declare providers from the code my team has to write and handle that behind the scenes (some form of reverse tree shaking in the transpile??), the DI system is great (seriously, LOVE it), but I'd say still needs a bit more work to entice more DEVs to this platform for new/small projects, IMO providers were more obvious when you had to explicitly write the module files...now it feels odd to have to go to the main.ts file and {provide: XDirective, useClass: XDirective} though I expect I'll get over the odd feeling after more time with this

Hi, at first, I really appreciate your way of introducing 14. You just update 13 to 14 and showed what is changed along with the details. bravo.. Cheers🤘

Is it necessary to make AppModule a standaolone component ? We can boostrap out the application via the appmodule and create other components as standalone? I think it would be cleaner that way.

Thank you for your videos!!! You are top at Angular video bloggers!

Thank you so much for these great videos, great work.

That was awesome, thanks, really simple really understandable.

meh, I am good with NgModule actually

I have created a component with standalone is there a way to change it back to normal component

Thank god. All this module boilerplate code was driving me crazy.

I don't know...looks like each component gets a module...

You're a brilliant instractor

Good job on making such a great angular content, each video teaches me something new! Also thanks for creating such a great community in comments and speaking up on some real angular topics. Anyway I was waiting for this feature so long. Looking forward to upgrade my pet project.

Яшчэ раз шчыры дзякуй і Слава Украіне!

Thank you so muc, I just started learning angular..and I see all other course are legacy versions... Could u please create or advise if there is any course on angular 14 with analytics website.. the other challenges with courses are data level permission, authentication and authorisation... If u could advise q course on these that wil help Sir.. :)

I Liked standalone components concept, it can make our code more easily and small. In all of my applications i have ngModules declarating only one component, many modules code... Modules are necessary, not your mandatory!

I do not like this approach of Angular 14, modules keep your work organized.

I also have some questions, what is the advantage to this approach, does it make Angular a better choice for lightweight applications.

If that is not the case, I do not see any valid reason for this change

Thank you for the explanations, it was really clear! I really like this approach, I feel like angular app architecture will be simplier with standalone components. I wish in the future there will be a way to lazy load a component when it appears in the template, without having to use the router.

Great features

Somehow there is a huge loss in your voice quality between the intro and the rest of the video.

I think total depending on standalone compnents will make the structure of projects messy in large scale projects but it still an optional till now so it is ok

Always thankful for sharing amazing content. But this time I don't know why I'm not liking the standalone feature. By the way thanks again ☺️

It seems like Angular is trying to provide an alternative in order to compete with React. By having the capability to use Modules as well as standalone components. I think by enabling the standalone components they will eventually have a schematic for smaller scale projects that don't require the heavy framework load.

What about shared modules that we used to create aiming to share pipes and components? How can we do this?

I really like this feature, but I think I will only use the standalone for dumny components. Module keeps the application organized, moving modulea responsibility to components could make the application a mess

Great feature but imports array is annoying. I hope it disappear in next versions. It seems that TS imports should be sufficient or be done behind the scene.

Great video, thanks!!

angular is the worst framework ever

Hi, Do you know if Standalone components are compatible with, for example multiple providers in app.module.ts? And with multiple .forRoot like ngx-translate?

Thanks you!

I think this feature is a good solution for the "dumb components".

introducing a new way of making a mess :-)

This is why I hate Angular, these boneheads keep introducing breaking changes which causes a lot of pain for developer, ROI and the nightmare of application maintenance. I think I am going to make a switch to Vue, it's looking really solid and simplifies a lot of over-engineered angular concepts. I've been using Angular since Angular 2 beta.

Having said this, I always thought angular module was a stupid idea, an example of over engineering and bloatware and useless boilerplate.

Wow. This standalone stuff will be really usefull.

I think so the feature is good but also to be enjoyed with caution, I mean well it depends here on what you want. If I now only have a small widget which has little dependencies and is almost alone in the module, it makes sense.

But one advantage that modules have is for example which components we want to expose to the outside. And they are better configurable. So rather for more complex things. This does not necessarily make it easier for newcomers, because they have to think about what I want to achieve. Do I use a standalone component or rather a module.

But however I see that already before me if something new is there everything must be built so, in the case it is only an import. But the reality looks a bit different ;). Okay not every component needs all the imports that are defined but let it grow to 3 - 4 or more, then you may need another service that you define here because it should not necessarily run in the global scope.

This will get very ugly very fast.

Thank you!

I really like the concept of modules. With modules you have the power to keep some components private and expose only the components you want to be referred in other components. From dependency management view you have more control which parts of your code have an higher dependency with others. Without modules it feels for my more like anarchie.

I think this new feature can be the turning point for angular. And more devs will use angular for smaller projects, this can make development fast like in other frameworks (react and vue). As we know, right now angular use for medium to large projects only.

Awesome video thanks a ton💖, I have one qn, how we can handle Singleton services in set of components, previously, Modules are taking care of this, is there any alternative way in this Architecture?

I don't find it much beneficial but I see it creating extra overhead for each standalone component making build process slow.
It seems as if we can are creating a separate dedicated ngModule (with only one component inside behind the scene) for each standalone component.
It's no rocket science in it.

Dude, дякую

I am currently trying that standalone component and my code become cleaner. Next job is angular without ngzone

Can we use react npm package inside angular application.. is this possible??