Module vs Module - DEBORAH KURATA

By: ng-conf

94   1   3824

Uploaded on 04/06/2017

www.ng-conf.org

ng-conf is a two day, single track conference focused on delivering the highest quality training in the Angular JavaScript framework. 500 to 700 Developers from across the country will converge on beautiful Salt Lake City, UT to participate in training sessions by the Google Angular team, and other Angular experts. In addition to the invaluable training, ng-conf will deliver a premier conference experience for attendees, providing opportunities to network with other developers, relax at social events, and engage in some of the unique entertainment opportunities available in Utah.

Comments (10):

By anonymous    2017-09-20

An Angular module provides for template resolution. Any nested component, directive, or pipe used by a template associated with a component declared in an Angular module must also be either declared or imported into that Angular module.

You can share components, directives, and pipes using a shared module.

See this video for more information on template resolution and shared modules: https://www.youtube.com/watch?v=ntJ-P-Cvo7o&t=4s

Original Thread

By anonymous    2017-09-20

As it being already stated here you can use Angular CLI to start your project having all best practices in place and to check out Angular styleguide that give you some more details/theory on that.

However it is also very important to get your project logical structure right for that you can check this repo as example (FYI it is build with Angular CLI) and that ng-conf talk by @DeborahK also checkout this article on the same matter.

Original Thread

By anonymous    2017-09-20

With this code below, the HeroLogoComponent will available to every component declared within the same declarations array.

@NgModule({
  declarations: [
  MyApp,
  HeroLogoComponent,
], ...

If you have multiple Angular modules and want it accessible to every component in every Angular module, put it in a shared module as Aravind recommended. Then ensure the shared module is imported into every Angular module you define that has components that needs it.

To find out more information, check this out: https://www.youtube.com/watch?v=ntJ-P-Cvo7o&t=6s

Original Thread

By anonymous    2017-10-01

ng modules simply logical units that contained components, services, pipes, directives, providers, etc.

The main benefit of ng modules is that they help you to organize the logical structure of your app - this way is much easier to maintain the codebase over time, etc.

There is a different types of modules:

A while ago I was giving a talk on that matter also you might take a look at code sample

Also I would recommend to watch this talk https://www.youtube.com/watch?v=ntJ-P-Cvo7o from the latest ngconf that covers the purpose of ng modules.

Original Thread

By anonymous    2017-12-04

There are quite a few rules here on how this works. Consider checking out my video on the topic from ngConf here: https://www.youtube.com/watch?v=ntJ-P-Cvo7o&t=1s

Original Thread

By anonymous    2018-02-18

If you are interested in understanding more about what the `import` and `export` keywords do, I have a video here: https://www.youtube.com/watch?v=ntJ-P-Cvo7o&t=2s (which primarily focused on Angular modules, but covers the import and exports keywords as well.)

Original Thread

By anonymous    2018-03-18

This may help as well: https://www.youtube.com/watch?v=ntJ-P-Cvo7o

Original Thread

Submit Your Video

If you have some great dev videos to share, please fill out this form.