If I do a search on a topic on UA-cam and I find a hit on Monstelessons, that will be the first video I watch. The content development is superb. Thanks so much for helping us all out here.
Perfect timing! I wanna do something like this soon. I do however have a question. I have a project with a core, feature(s) and a shared module. Every feature imports the shared module. I'm going to move all the components, directives etc from the shared module into the angular library so I can be used in multiple projects. Do I now put the Library module inside the shared module (sort of becomes wrapped) or do I directly use the library module inside the features? Because the shared module will be pretty empty and useless after moving everything into the lib module. Any suggestions or tips on how to approach this?
Seems like modules are no longer there when libraries are installed now and all components are standalone by default. Do we have to import each component in the public-api?
But how does this work with multiple components though? I'm trying to have a library where I can have like 30-40 custom components if necessary. This only allows for one component because we only have the one file that was generated in our `lib` folder?
Для учбових відео краще використовуй Visual Code в дефолтному вигляді, бо в цьому редакторі що в тебе погано сприймається файлова структура, і в нумерації строк кода теж погано орієнтуватись... Це прям очевидно...
there's nothing new compared to the other tutorials there's no info about adding dependencies, handling multiple style files(especially from dependencies), handling config injection etc
WATCH NEXT: Angular Unit Testing Course - All That You Need to Know About Testing - ua-cam.com/video/bv9z_UfSqgM/v-deo.htmlsi=WVzOWtdQUZWEbqsz
I appreciate all your content!
Happy to hear that!
Thank you so much!
In angular project, we can update a package like: ng update @angular/core
How to update package in a library?
Thanks a lot Monsterlessons Academy. Great contents !!!
Glad you like it!
If I do a search on a topic on UA-cam and I find a hit on Monstelessons, that will be the first video I watch. The content development is superb. Thanks so much for helping us all out here.
Great idea. Please make a payed course with monorepo, libs, multiple projects, etc.
Thank you for the idea. I will add it to the list
Perfect timing! I wanna do something like this soon.
I do however have a question. I have a project with a core, feature(s) and a shared module.
Every feature imports the shared module.
I'm going to move all the components, directives etc from the shared module into the angular library so I can be used in multiple projects.
Do I now put the Library module inside the shared module (sort of becomes wrapped) or do I directly use the library module inside the features?
Because the shared module will be pretty empty and useless after moving everything into the lib module.
Any suggestions or tips on how to approach this?
Keep it simple. You don't need shared in lib if you don't share anything.
Seems like modules are no longer there when libraries are installed now and all components are standalone by default. Do we have to import each component in the public-api?
Just export components
But how does this work with multiple components though? I'm trying to have a library where I can have like 30-40 custom components if necessary. This only allows for one component because we only have the one file that was generated in our `lib` folder?
export * from './lib/mla-users.component';
export * from './lib/mla-foo.component';
export * from './lib/mla-bar.component';
hi, is there any way to use global css variables through all the components of the library in order to create different themes?
sure. css variables kind of ignore angular rules. so you provide variable in parent and it will work
Thank you, very useful content !!
Glad you like it!
What are your thoughts on NX?
It is good. I have a video about it. ua-cam.com/video/m1NTKbHwNJk/v-deo.html
Getting NG023 while consuming library locally
No idea, sorry
Для учбових відео краще використовуй Visual Code в дефолтному вигляді, бо в цьому редакторі що в тебе погано сприймається файлова структура, і в нумерації строк кода теж погано орієнтуватись... Це прям очевидно...
Have you already achieved 100% coverage using Library?
100% tests coverage is not needed. You need enough so your app doesn't break.
there's nothing new compared to the other tutorials
there's no info about adding dependencies, handling multiple style files(especially from dependencies), handling config injection etc
I never promised to deliver what you wrote down. It is a beginners guide.
his content is really good, however his accent is not really easy to listen to