The USPTO Registered Logo Badge of the Medical Marijuana Initiative of North America - International Limited, an Arizona Benefit Corporation to the left of Mt Hood sunlit from the northwest in June followed by the proprietary MMINAIL octocopter delivery bot.

How To Install The Webpack Bundler In Mac Os Sierra


Welcome! This is the Installing the Webpack Bundler page of the MMINAIL.


Note. This page has explicit access to the local jQuery library as well as a local complimentary working (.js) file.


Installing The Webpack Bundler


To install the Webpack Bundler, or WPB onto your development machine, first install both node and the Node Package Manager, or NPM.

After the developer has installed both node and and the Node Package Manager, or NPM onto his or her development machine, the WPB may then be installed globally using npm, as follows:

From the global Terminal prompt $ ...

npm install -g webpack

Updating The WPB


Hey! The Web Pack Bundler Team just came out with a new, updated version of the Webpack Bundler WPB.

How do I upgrade the WPB?

To upgrade the WPB, you must first counter-intuitively uninstall the old version of the WPB and then cleanse the cache!

As follows:

From the global Terminal prompt $ ...

npm uninstall -g webpack cache clean

Once the old version of the WPB has been removed from your development machine ...

And, the cache has been cleansed ...

You may simply next re-install the WPB, first globally as above, and then next within your local app(s), for either development purposes, as follows:

From the Integrated Terminal prompt $ in Visual Studio Code representing the root directory of the targeted project ...

npm install --save-dev webpack

Or, as a distributed app without the development flag.

From the Integrated Terminal prompt $ in Visual Studio Code representing the root directory of the targeted project ...

npm install --save webpack

Decisions, Decisions!


So, now that you have been shown two flag configurations to the solution, which one do you use?


Respuesta


That all depends upon where in the package dot json file you wish to house your dependency.

Your choices are simple 'dependencies' or 'dev' Dependencies.

Which of the above two choices correlates to the install flag --save-dev and which one correlates to the install flag --save?

If you guessed 'dev' Dependencies correlate with the install flag --save-dev you are correct!

Therefore, by extension, simple 'dependencies' correlates to the install flag --save.

Each flag directs traffic to a specifc spot in the package dot json file.

As the following excerpt shows, it's the simple 'dependencies' first, the 'dev' Dependencies second when installing a dependency ( separate app ) to your Angular 4 project.

From the package.json file ...

"dependencies": {
    "@angular/common": "4.0.1",
    "@angular/compiler": "4.0.1",
    "@angular/core": "4.1.0",
    "@angular/forms": "4.0.3",
    "@angular/http": "4.0.3",
    "@angular/platform-browser": "4.0.3",
    "@angular/platform-browser-dynamic": "4.0.3",
    "@angular/router": "4.0.3",
    "bootstrap": "3.3.7",
    "core-js": "2.4.1",
    "font-awesome": "4.7.0",
    "jquery": "3.2.1",
    "jquery-mobile": "1.5.0-alpha.1",
    "rxjs": "5.3.0",
    "tether": "1.4.0",
    "zone.js": "0.8.9"
  },
  "devDependencies": {
    "@angular/cli": "1.0.1",
    "@angular/compiler-cli": "4.0.3",
    "@types/jasmine": "2.5.38",
    "@types/node": "6.0.70",
    "codelyzer": "2.0.1",
    "jasmine-core": "2.5.2",
    "jasmine-spec-reporter": "3.2.0",
    "karma": "1.4.1",
    "karma-chrome-launcher": "2.0.0",
    "karma-cli": "1.0.1",
    "karma-coverage-istanbul-reporter": "0.2.3",
    "karma-jasmine": "1.1.0",
    "karma-jasmine-html-reporter": "0.2.2",
    "protractor": "5.1.1",
    "ts-node": "2.0.0",
    "tslint": "4.5.1",
    "typescript": "2.2.2",
    "webpack": "2.4.1",
    "webpack-dev-server": "~2.4.2",
    "autoprefixer": "^6.5.3",
    "css-loader": "^0.27.3",
    "cssnano": "^3.10.0",
    "exports-loader": "^0.6.3",
    "file-loader": "^0.10.0",
    "json-loader": "^0.5.4",
    "karma-sourcemap-loader": "^0.3.7",
    "less-loader": "^4.0.2",
    "postcss-loader": "^1.3.3",
    "postcss-url": "^5.1.2",
    "raw-loader": "^0.5.1",
    "sass-loader": "^6.0.3",
    "script-loader": "^0.7.0",
    "source-map-loader": "^0.1.5",
    "istanbul-instrumenter-loader": "^2.0.0",
    "style-loader": "^0.13.1",
    "stylus-loader": "^3.0.1",
    "url-loader": "^0.5.7"
  }

What you may ask is a 'simple' dependency as opposed to a 'dev' Dependency?

Well, as the title suggests, the 'dev' Dependency points to a separate app or dependency in your Angular 4 project that is required to compile itself during development.

Yet, the separate app, or dependency gets tossed aside never making it into the final output dist of your ng build --prod command.

Whereas, the separate app(s) tag'd with 'simple' dependencies get bundled at the end with the production copy.

So, which dependency is what type?


Da Rule


Rule. If the dependency in question is required to render a component within the production copy of your Angular 4 project ...

Then, include the separate app as a 'simple' dependency and use the simple install --save flag configuration.

If, on the other hand, the dependency in question is required only for the mechanical final building of your Angular 4 production project ...

Then, be sure to use the install --save-dep flag to continue to segregate within the package dot json file those dependencies that are deemed 'user friendly' and those 'dev' Dependencies that are deemed 'machine friendly'.


The Angular CLI


Usually, but not always, the pertinent instructional data page for any separate app house'd at the Node Package Manager, or NPM should include which flavor of flag to be used at npm install.

But, not always!

As a guide, when tweaking the Angular Command Line Interface, or CLI, for example ... First venture into the package dot json file to see how the original install of the Angular CLI for your project did indeed segregate at the respective time of install.

	Finito! 

Supporting Content


Welcome! This is the Supporting Content section for the MMINAIL Central Live Repository.


E Books


With today's explosion of modern devices, some consumers like to read their articles on their Kindles or iPads.

Therefore, a method to convert any page of this website into an 'eBook' is auto-built into the top of the navigation stack as well as in the footer of every page.

Simply click the small dot epub button eBook icon to render the current page as an Overdrive (.epub) or a Kindle (.mobi) for external reading.

Note. The Apple iBooks platform also reads and displays the (.epub) format.


The A's Have It!


In today's complicated world of coding, even the use of the standard hyperlink has come into question.

Therefore, to make it easy for the end-user, this User Interface, or UI will show safe internal links in the bootstrap default color of light dodger blue.

On the other hand, external links, when designated https secure ... Will be shown in the color of forest green.

All other external links designated with standard http will be shown in the color of indian red.


Acronyms


For an acronym to be visually effective when reading a line of text, the acronym must first be declared.

In addition, the acronym must stand out from the body of information.

To accomplish both of these objectives, the authors have selected Ashley Gold, a primary color within the registered logo badge of the Benefit corporation for which to highlight acronyms.

Whenever the end user spies a designated acronym of Ashley Gold color, simply hover over the acronym to reveal the underlying meaning of the acronym letters.


Screen Responsiveness


This page has been tested for mobile responsiveness on a virtual Galaxy S5 smartphone emulator.

The authors have determined the accuracies of the page renderings at both a portrait width of 360px and a landscape width of 640px.

In addition, pages are also tested against an Amazon Kindle Fire HDX 7, 3rd Generation tablet.

On the Kindle tablet, both portrait and landscape renderings appear accurate, as well.

And, on the Amazon Fire phone, using automatic screen rotation, both portrait and landscape renderings appear accurate.


How To Navigate This Website


  • The Navigation to your right is set up to return to this Home page by clicking on the Home icon   south of the divider.

  • To select any of the other topics or subtopics, simply click on the corresponding glyphicon to open up the referenced file.

  • If you get stuck, simply click on the Home icon   below the divider to be hyperlinked back to this Home page.

Got An Idea?


If you have an idea that will spruce this site up even better than it already is, then you know the drill.

Simply go ahead and fork this repo, make your changes, and send me a pull request.


Site Monitoring


Note. The Http Headers of this repo are being monitored by Internet Supervision dot com


25 Mile Rule


The MMINAIL is dedicated to the preservation of the hard-earned rights of Medical patients to grow up to (12) state-legal Medicinal plants.

In a connective cartography of ideas and hyperlinks spanning the entire connectome of the modern Medical Marijuana Initiative ...

The open source authors of this project hope to enlighten the world to the plight of the common medical patient.

Due to a labyrinth of government regulations and costs, today's common medical patient is virtually devoid of healing phyto-cannabinoids and other beneficial terpenes globally for no other reason than his or her current residential address.


Unconstitutional


"When residing 25 miles extant of a state legalized dispensary"

Doesn't that sound a bit strange to you?

Restricting access to medicine ...

Almost Un-constitutional, isn't it?

And, with patients in Arizona paying anywhere from $75 to $90 USD for a (1/8) ounce of medicine ...

Don't you think it is time that we allow ALL patients the right to grow, stash, and cure their own medicines?


Make Contact


We do at the MMINAIL.

If you agree, why don't you donate a little spare cash?

Or, a little of your coding time?

Or, simply contact your favorite Arizona State Senators and Congressional Representatives today!


No Warranty


Disclaimer. The author of this website has made every effort to ensure the accuracy of the information herein.

However, the information contained in this website, and in its pages, is offered to the public without any warranty expressed or implied.

Therefore, the author of this website, and by extension its pages and content cannot be held liable for any damages that may be caused indirectly or directly by the software instructions or tutorials contained in the pages of this website.

For further review, please see the License page of this website and/or the Privacy Policy page of this website to clarify.


Reproduction In Part


Most authors will allow the reproduction of their works in part when the case of brief quotations embodied in critical articles or reviews is addressed.

Therefore, please remember to provide a Link-back to the original author, or to the publisher of the original publication when citing.

Thank you for your consideration.


Fork It


If you are an expert in your field of specialty, then I suggest you fork the working repo of this Website and create a Sub-menu topic of your choosing that may be beneficial to our readers.


Send us a Pull Request.


Our team of coders will review your contribution and get back to you with a "thumbs up" ( or, "thumbs down" ).


Can You Contribute?


As we can now decipher the time spent by our functions at the code block level ...

How much of your coding time are you willing to invest in this project?

As we rely heavily upon contributions from the coding community, your contribution of either cash or code will be greatly appreciated.


Thank you for your contribution.


The Management

The USPTO Registered Logo Badge of the Medical Marijuana Initiative of North America - International Limited, an Arizona Benefit Corporation

Copyright © 2000 - 2017

The Medical Marijuana Initiative of North America Small Registered MMINAIL™ Logo Badge Small Registered MMINAIL™ Logo Badge
- International Limited Small R-Reggae™ Trademark Symbol Logo Badge Small R-Reggae™ Trademark Symbol Logo Badge


To create an iBook/Overdrive (.epub)

or

a Kindle (.mobi) of this page ...

Click the small dot epub button button


This Open Source project is being hosted with Jekyll via GitHub Pages.

All rights reserved. Except where explicity granted.