To turn this into a module in the simplest way, we can just change the file extension to .psm1. Once we have done this, we can import the module by pointing directly to the .psm1 file, as follows:
Similar to when we dot-sourced the script file, here we also don't see any real indication that the import-module cmdlet did anything. If we look at the output of get-command now, we can see that these functions are now listed as part of a module. We can, also, use the –Module parameter for get-command to show all the functions that were exported from the module:
Now, these functions are much easier to discover, since we can see that they fit together somehow.
Module files with a .psm1 extension are called script modules, for obvious reasons. One huge benefit of using script modules is that they are simple to create. Another reason for using script modules is that they provide the opportunity to hide elements that you don't want to be public.
