webpacker 3.0.1 → 3.0.2

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 6509ab0499053e37d9af22b79262832b33f8cd91
-  data.tar.gz: 869403b35f9178ea48884343782822282b91afde
+  metadata.gz: e29d1fa9bd905782462ea86943ac0f6c41bc610b
+  data.tar.gz: a8d0c7cc0b52389cdf3e3d4c65bb7b6a74b75b00
 SHA512:
-  metadata.gz: 8fd1e44cf21efb3ab7cb0e581c09e7ace7e3cb73412b227592885db69b5ffb57379f4386635f3937d1211e52aca75e907b4a417c7f2d255b2419e75681716cbc
-  data.tar.gz: 1c2cf1efddda9af825334f9e1cace219082ab6b24dbb1db307721c516533474b7451363c3b089819082adec696daea40967a0c55d4cfbe82d66d664b51b645a9
+  metadata.gz: 00202a0bca78706ba430c3e2475103cf78a38947d664c40ef00a64ccffbd4f7ef608d5f4dad4f1bbbcdd3a5b6f6317ce308543c41cdff9379a164a8ffd14a354
+  data.tar.gz: 9bcd5eb3dab53f78807b811d94efa673edee119eeb72d85d1830f89794c996583a1da502e6a8b81fd83c047617089587fb227f102f7cd13a2b618cbfd031b0a5

data/.eslintignore

@@ -0,0 +1,3 @@
+lib/*
+node_modules/*
+vendor/*

data/.gitignore

@@ -4,5 +4,3 @@
 node_modules
 .byebug_history
 /test/test_app/tmp
-Gemfile.lock
-yarn.lock

data/.travis.yml

@@ -1,9 +1,9 @@
 sudo: false
 language: ruby
 rvm:
-  - 2.2.6
-  - 2.3.3
-  - 2.4.1
+  - 2.2.8
+  - 2.3.5
+  - 2.4.2
 cache:
   bundler: true
   directories:

data/CHANGELOG.md

@@ -1,3 +1,45 @@
+## [3.0.2] - 2017-10-04
+
+### Added
+
+- Allow dev server connect timeout (in seconds) to be configurable, default: 0.01
+
+```rb
+# Change to 1s
+Webpacker.dev_server.connect_timeout = 1
+```
+
+- Restrict the source maps generated in production [#770](https://github.com/rails/webpacker/pull/770)
+
+- Binstubs [#833](https://github.com/rails/webpacker/pull/833)
+
+- Allow dev server settings to be overriden by env variables [#843](https://github.com/rails/webpacker/pull/843)
+
+- A new `lookup` method to manifest to perform lookup without raise and return `nil`
+
+```rb
+Webpacker.manifest.lookup('foo.js')
+# => nil
+Webpacker.manifest.lookup!('foo.js')
+# => raises Webpacker::Manifest::MissingEntryError
+```
+
+- Catch all exceptions in `DevServer.running?` and return false [#878](https://github.com/rails/webpacker/pull/878)
+
+### Removed
+
+- Inline CLI args for dev server binstub, use env variables instead
+
+- Coffeescript as core dependency. You have to manually add coffeescript now, if you are using
+it in your app.
+
+```bash
+yarn add coffeescript@1.12.7
+
+# OR coffeescript 2.0
+yarn add coffeescript
+```
+
 ## [3.0.1] - 2017-09-01
 
 ### Fixed
@@ -94,9 +136,11 @@ live reload when manifest changes. If you have applied this workaround from [#72
 
 ### Breaking changes
 
-- Add `compile` option to `config/webpacker.yml` for configuring lazy compilation of packs when a file under tracked paths is changed [#503](https://github.com/rails/webpacker/pull/503). To enable expected behavior, update `config/webpacker.yml`:
+- Add `compile` and `cache_path` options to `config/webpacker.yml` for configuring lazy compilation of packs when a file under tracked paths is changed [#503](https://github.com/rails/webpacker/pull/503). To enable expected behavior, update `config/webpacker.yml`:
 
   ```yaml
+    default: &default
+      cache_path: tmp/cache/webpacker
     test:
       compile: true
 

data/Gemfile.lock

@@ -0,0 +1,144 @@
+PATH
+  remote: .
+  specs:
+    webpacker (3.0.2)
+      activesupport (>= 4.2)
+      rack-proxy (>= 0.6.1)
+      railties (>= 4.2)
+
+GEM
+  remote: https://rubygems.org/
+  specs:
+    actioncable (5.0.1)
+      actionpack (= 5.0.1)
+      nio4r (~> 1.2)
+      websocket-driver (~> 0.6.1)
+    actionmailer (5.0.1)
+      actionpack (= 5.0.1)
+      actionview (= 5.0.1)
+      activejob (= 5.0.1)
+      mail (~> 2.5, >= 2.5.4)
+      rails-dom-testing (~> 2.0)
+    actionpack (5.0.1)
+      actionview (= 5.0.1)
+      activesupport (= 5.0.1)
+      rack (~> 2.0)
+      rack-test (~> 0.6.3)
+      rails-dom-testing (~> 2.0)
+      rails-html-sanitizer (~> 1.0, >= 1.0.2)
+    actionview (5.0.1)
+      activesupport (= 5.0.1)
+      builder (~> 3.1)
+      erubis (~> 2.7.0)
+      rails-dom-testing (~> 2.0)
+      rails-html-sanitizer (~> 1.0, >= 1.0.2)
+    activejob (5.0.1)
+      activesupport (= 5.0.1)
+      globalid (>= 0.3.6)
+    activemodel (5.0.1)
+      activesupport (= 5.0.1)
+    activerecord (5.0.1)
+      activemodel (= 5.0.1)
+      activesupport (= 5.0.1)
+      arel (~> 7.0)
+    activesupport (5.0.1)
+      concurrent-ruby (~> 1.0, >= 1.0.2)
+      i18n (~> 0.7)
+      minitest (~> 5.1)
+      tzinfo (~> 1.1)
+    arel (7.1.4)
+    ast (2.3.0)
+    builder (3.2.3)
+    byebug (9.0.6)
+    concurrent-ruby (1.0.5)
+    erubis (2.7.0)
+    globalid (0.3.7)
+      activesupport (>= 4.1.0)
+    i18n (0.8.1)
+    loofah (2.0.3)
+      nokogiri (>= 1.5.9)
+    mail (2.6.4)
+      mime-types (>= 1.16, < 4)
+    method_source (0.8.2)
+    mime-types (3.1)
+      mime-types-data (~> 3.2015)
+    mime-types-data (3.2016.0521)
+    mini_portile2 (2.1.0)
+    minitest (5.10.1)
+    nio4r (1.2.1)
+    nokogiri (1.7.0.1)
+      mini_portile2 (~> 2.1.0)
+    parallel (1.12.0)
+    parser (2.4.0.0)
+      ast (~> 2.2)
+    powerpack (0.1.1)
+    rack (2.0.1)
+    rack-proxy (0.6.1)
+      rack
+    rack-test (0.6.3)
+      rack (>= 1.0)
+    rails (5.0.1)
+      actioncable (= 5.0.1)
+      actionmailer (= 5.0.1)
+      actionpack (= 5.0.1)
+      actionview (= 5.0.1)
+      activejob (= 5.0.1)
+      activemodel (= 5.0.1)
+      activerecord (= 5.0.1)
+      activesupport (= 5.0.1)
+      bundler (>= 1.3.0, < 2.0)
+      railties (= 5.0.1)
+      sprockets-rails (>= 2.0.0)
+    rails-dom-testing (2.0.2)
+      activesupport (>= 4.2.0, < 6.0)
+      nokogiri (~> 1.6)
+    rails-html-sanitizer (1.0.3)
+      loofah (~> 2.0)
+    railties (5.0.1)
+      actionpack (= 5.0.1)
+      activesupport (= 5.0.1)
+      method_source
+      rake (>= 0.8.7)
+      thor (>= 0.18.1, < 2.0)
+    rainbow (2.2.2)
+      rake
+    rake (12.0.0)
+    rubocop (0.49.1)
+      parallel (~> 1.10)
+      parser (>= 2.3.3.1, < 3.0)
+      powerpack (~> 0.1)
+      rainbow (>= 1.99.1, < 3.0)
+      ruby-progressbar (~> 1.7)
+      unicode-display_width (~> 1.0, >= 1.0.1)
+    ruby-progressbar (1.8.1)
+    sprockets (3.7.1)
+      concurrent-ruby (~> 1.0)
+      rack (> 1, < 3)
+    sprockets-rails (3.2.0)
+      actionpack (>= 4.0)
+      activesupport (>= 4.0)
+      sprockets (>= 3.0.0)
+    thor (0.19.4)
+    thread_safe (0.3.6)
+    tzinfo (1.2.2)
+      thread_safe (~> 0.1)
+    unicode-display_width (1.3.0)
+    websocket-driver (0.6.5)
+      websocket-extensions (>= 0.1.0)
+    websocket-extensions (0.1.2)
+
+PLATFORMS
+  ruby
+
+DEPENDENCIES
+  bundler (~> 1.12)
+  byebug
+  minitest (~> 5.0)
+  rack-proxy
+  rails
+  rake (>= 11.1)
+  rubocop (>= 0.49)
+  webpacker!
+
+BUNDLED WITH
+   1.15.4

data/README.md

@@ -20,8 +20,10 @@ in which case you may not even need the asset pipeline. This is mostly relevant
 - [Prerequisites](#prerequisites)
 - [Features](#features)
 - [Installation](#installation)
+  - [Upgrading](#upgrading)
   - [Usage](#usage)
   - [Development](#development)
+  - [Webpack configuration](#webpack-configuration)
 - [Integrations](#integrations)
   - [React](#react)
   - [Angular with TypeScript](#angular-with-typescript)
@@ -90,6 +92,7 @@ bundle exec rails webpacker:install
 bundle exec rake webpacker:install
 ```
 
+
 ### Usage
 
 Once installed you can start writing modern ES6-flavored JavaScript app today:
@@ -124,6 +127,7 @@ can use `asset_pack_path` helper:
 **Note:** In order for your styles or static assets files to be available in your view,
 you would need to link them in your "pack" or entry file.
 
+
 ### Development
 
 Webpacker ships with two binstubs: `./bin/webpack` and `./bin/webpack-dev-server`.
@@ -155,24 +159,36 @@ Once you start this development server, Webpacker will automatically start proxy
 webpack asset requests to this server. When you stop the server, it'll revert to
 on-demand compilation again.
 
-You can also pass CLI options supported by [webpack-dev-server](https://webpack.js.org/configuration/dev-server/). Please note that inline options will always take
-precedence over the ones already set in the configuration file.
+You can use environment variables as options supported by [webpack-dev-server](https://webpack.js.org/configuration/dev-server/) in the form `WEBPACKER_DEV_SERVER_<OPTION>`. Please note that these environment variables will always take precedence over the ones already set in the configuration file.
 
 ```bash
-./bin/webpack-dev-server --host example.com --inline true --hot false
+WEBPACKER_DEV_SERVER_HOST=example.com WEBPACKER_DEV_SERVER_INLINE=true WEBPACKER_DEV_SERVER_HOT=false ./bin/webpack-dev-server
 ```
 
 By default, webpack dev server listens on `localhost` in development for security
 but if you want your app to be available over local LAN IP or VM instance like vagrant
-you can pass an additional config option `--listen-host`
-when running `./bin/webpack-dev-server` binstub:
+you can set the `host` when running `./bin/webpack-dev-server` binstub:
 
 ```bash
-./bin/webpack-dev-server --listen-host 0.0.0.0
+WEBPACKER_DEV_SERVER_HOST=0.0.0.0 ./bin/webpack-dev-server
 ```
 
 **Note:** Don't forget to prefix `ruby` when running these binstubs on windows
 
+### Webpack configuration
+
+See [docs/Webpack](docs/webpack.md) for modifying webpack configuration and loaders.
+
+
+### Upgrading
+
+You can run following commands to upgrade webpacker to the latest stable version, this involves upgrading the gem and npm module:
+
+```bash
+bundle update webpacker
+yarn upgrade @rails/webpacker --latest
+```
+
 ## Integrations
 
 Webpacker ships with basic out-of-the-box integration for React, Angular, Vue and Elm.
@@ -198,7 +214,7 @@ project in `app/javascript/packs` so that you can experiment with React right aw
 
 ### Angular with TypeScript
 
-To use Webpacker with [Angular](https://angularjs.org/), create a
+To use Webpacker with [Angular](https://angular.io/), create a
 new Rails 5.1+ app using `--webpack=angular` option:
 
 ```bash

data/docs/deployment.md

@@ -9,13 +9,10 @@ The `javascript_pack_tag` and `stylesheet_pack_tag` helper method will automatic
 By default the output will look like this in different environments:
 
 ```html
-  <!-- In development mode -->
-  <script src="/packs/calendar.js"></script>
-  <link rel="stylesheet" media="screen" href="/packs/calendar.css">
   <!-- In development mode with webpack-dev-server -->
-  <script src="http://localhost:8080/calendar.js"></script>
-  <link rel="stylesheet" media="screen" href="http://localhost:8080/calendar.css">
-  <!-- In production mode -->
+  <script src="http://localhost:8080/calendar-0bd141f6d9360cf4a7f5.js"></script>
+  <link rel="stylesheet" media="screen" href="http://localhost:8080/calendar-dc02976b5f94b507e3b6.css">
+  <!-- In production or development mode -->
   <script src="/packs/calendar-0bd141f6d9360cf4a7f5.js"></script>
   <link rel="stylesheet" media="screen" href="/packs/calendar-dc02976b5f94b507e3b6.css">
 ```

data/docs/env.md

@@ -17,7 +17,7 @@ console.log(process.env.FOO) // Compiles to console.log("hello")
 You may want to store configuration in environment variables via `.env` files,
 similar to the [dotenv Ruby gem](https://github.com/bkeepers/dotenv).
 
-In development, if you use Foreman or [Invoker](http://invoker.codemancers.com)
+In development, if you use [Foreman](http://ddollar.github.io/foreman) or [Invoker](http://invoker.codemancers.com)
 to launch the Webpack server, both of these tools have basic support for a
 `.env` file (Invoker also supports `.env.local`), so no further configuration
 is needed.

data/docs/misc.md

@@ -14,7 +14,7 @@ and add `ignore-loader` to `config/webpack/environment.js`
 ```js
 // ignores vue~ swap files
 const { environment } = require('@rails/webpacker')
-environment.loaders.add('ignore', {
+environment.loaders.set('ignore', {
   test:  /.vue~$/,
   loader: 'ignore-loader'
 })

data/docs/props.md

@@ -78,7 +78,7 @@ Now, modify your Vue app to expect the properties.
     props: ["message","name"],
     data: function () {
       return {
-          test: 'This will display: ',
+        test: 'This will display: '
       }
     }
   }
@@ -103,3 +103,121 @@ document.addEventListener('DOMContentLoaded', () => {
 ```
 
 You can follow same steps for Angular too.
+
+
+## Elm
+
+Just like with other implementations, we'll render our data inside a `data`
+attribute:
+
+```erb
+<%= content_tag :div,
+  id: "hello-elm",
+  data: {
+    message: "Hello",
+    name: "David"
+  }.to_json do %>
+<% end %>
+```
+
+We parse the JSON data and pass it to Elm as flags:
+
+```js
+import Elm from '../Main'
+
+document.addEventListener('DOMContentLoaded', () => {
+  const node = document.getElementById('hello-elm')
+  const data = JSON.parse(node.getAttribute('data'))
+  Elm.Main.embed(node, data)
+})
+```
+
+Defining `Flags` as a `type alias`, we instruct Elm to demand flags `message`
+and `name` of type `String` on initialization.
+
+Using `programWithFlags` we bring all the pieces together:
+
+
+```elm
+module Main exposing (..)
+
+import Html exposing (Html, programWithFlags, h1, text)
+import Html.Attributes exposing (style)
+
+
+-- MODEL
+
+
+type alias Flags =
+    { message : String
+    , name : String
+    }
+
+
+type alias Model =
+    { message : String
+    , name : String
+    }
+
+
+type Msg
+    = NoOp
+
+
+
+-- INIT
+
+
+init : Flags -> ( Model, Cmd Msg )
+init flags =
+    let
+        { message, name } =
+            flags
+    in
+        ( Model message name, Cmd.none )
+
+
+
+-- UPDATE
+
+
+update : Msg -> Model -> ( Model, Cmd Msg )
+update msg model =
+    case msg of
+        NoOp ->
+            ( model, Cmd.none )
+
+
+
+-- SUBSCRIPTIONS
+
+
+subscriptions : Model -> Sub Msg
+subscriptions model =
+    Sub.none
+
+
+
+-- VIEW
+
+
+view : Model -> Html Msg
+view model =
+    h1 [ style [ ( "display", "flex" ), ( "justify-content", "center" ) ] ]
+        [ text (model.message ++ ", " ++ model.name ++ "!") ]
+
+
+
+-- MAIN
+
+
+main : Program Flags Model Msg
+main =
+    programWithFlags
+        { view = view
+        , init = init
+        , update = update
+        , subscriptions = subscriptions
+        }
+
+```