knallimall.org knallimall.org

User Tools

Site Tools

webpack_complete_webdevelopment_config

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
webpack_complete_webdevelopment_config [2018/02/05 22:36] – adminwebpack_complete_webdevelopment_config [2018/02/05 22:48] (current) – [Slide 3] admin
Line 24: Line 24:
   * Define "workspaces" to install packages recursively   * Define "workspaces" to install packages recursively
     * Workspace will be linked to ./node_modules/JoRo.Library (package.json -> "name")     * Workspace will be linked to ./node_modules/JoRo.Library (package.json -> "name")
-    * Dependenies end up in ./node_modules/ :!:+    * Dependencies end up in ./node_modules/ :!:
   * Centralize/unify build commands   * Centralize/unify build commands
   * Compatible with NPM but creates a yarn.lock file   * Compatible with NPM but creates a yarn.lock file
-  * Commands are slightly differen than NPMs (e.g. yarn add packageName)+  * Commands are slightly different than NPMs (e.g. yarn add packageName)
  
 <code bash Commands> <code bash Commands>
Line 320: Line 320:
 ===== The Good, the Bad ... ===== ===== The Good, the Bad ... =====
  
 +  * **Yarn**
 +    * Workspaces
 +    * Smart caching (??)
 +    * Works flawlessly with existing package.json
 +  * **Webpack**:
 +    * Webpack lets you use require() on local "static assets," meaning non-Javascript files.
 +    * https://blog.andrewray.me/webpack-when-to-use-and-why/#thegood
webpack_complete_webdevelopment_config.1517870185.txt.gz · Last modified: by admin

Page Tools