webpacker 5.4.0 → 6.0.0.rc.6

data/docs/v4-upgrade.md

@@ -1,142 +0,0 @@
-# Webpacker Upgrade Guide
-
-
-To update a Webpacker v3.5 app to v4, follow these steps:
-
-1. Update the `webpacker` gem and the `@rails/webpacker` package to v4. This will upgrade Webpack itself from 3.x to 4.x, make sure you're aware of [any deprecations which might effect you](https://webpack.js.org/migrate/4/). Also make sure any other packages you depend on support Webpack 4 and don't require any changes, e.g. if you explicitly include `webpack` you need to upgrade it to 4.x, and if you use `webpack-dev-server` you need to upgrade it to 3.x.
-
-2. Browser support definitions have been moved from [`.browserslistrc`](../lib/install/config/.browserslistrc) to `/`.
-
-3. Merge any differences between [`config/webpacker.yml`](../lib/install/config/webpacker.yml) and your `config/webpacker.yml`.
-
-4. Webpacker v4 upgrades Babel to [v7](https://babeljs.io/docs/en/v7-migration), see also [the release blog post](https://babeljs.io/blog/2018/08/27/7.0.0). Many packages were moved to the `@babel/` namespace, any babel plugins you have will need to be updated. It may be worth checking out [babel-upgrade](https://github.com/babel/babel-upgrade) if you have problems. ([#1564](https://github.com/rails/webpacker/pull/1564))
-
-5. `.babelrc` should be replaced with `babel.config.js` and `.postcssrc.yml` should be replaced with `postcss.config.js` ([#1822](https://github.com/rails/webpacker/pull/1822)). If you never changed these files from their defaults, the versions of [babel.config.js](../lib/install/config/babel.config.js) and [postcss.config.js](../lib/install/config/postcss.config.js) in the webpacker repository should be usable.
-
-6. Due to the change in [#1625](https://github.com/rails/webpacker/pull/1625), you'll want to make sure that `extract_css` is set to true for the `default` environment in `webpacker.yml` if you want to have Webpacker supply your CSS.
-
-## SplitChunks Configuration
-
-If you used the `CommonsChunkPlugin` you'll need to upgrade to using the new `splitChunks`.
-
-Originally, chunks (and modules imported inside them) were connected by a parent-child relationship in the internal Webpack graph. The `CommonsChunkPlugin` was used to avoid duplicated dependencies across them, but further optimizations were not possible.
-
-In Webpack v4, the `CommonsChunkPlugin` was removed in favor of `optimization.splitChunks`.
-
-For the full configuration options of `splitChunks`, see the [Webpack documentation](https://webpack.js.org/plugins/split-chunks-plugin/).
-
-```js
-// config/webpack/environment.js
-const WebpackAssetsManifest = require('webpack-assets-manifest');
-
-// Enable the default config
-environment.splitChunks()
-
-// or using custom config
-environment.splitChunks((config) => Object.assign({}, config, { optimization: { splitChunks: false }}))
-```
-
-Then use the `javascript_packs_with_chunks_tag` and `stylesheet_packs_with_chunks_tag` helpers to include all the transpiled
-packs with the chunks in your view, which creates html tags for all the chunks.
-
-```erb
-<%= javascript_packs_with_chunks_tag 'calendar', 'map', 'data-turbolinks-track': 'reload' %>
-
-<!-- Creates the following: -->
-<script src="/packs/vendor-16838bab065ae1e314.js" data-turbolinks-track="reload"></script>
-<script src="/packs/calendar~runtime-16838bab065ae1e314.js" data-turbolinks-track="reload"></script>
-<script src="/packs/calendar-1016838bab065ae1e314.js" data-turbolinks-track="reload"></script>
-<script src="/packs/map~runtime-16838bab065ae1e314.js" data-turbolinks-track="reload"></script>
-<script src="/packs/map-16838bab065ae1e314.js" data-turbolinks-track="reload"></script>
-```
-
-**Important:** Pass all your pack names to the helper otherwise you will get duplicated chunks on the page.
-
-```erb
-<%# DO %>
-<%= javascript_packs_with_chunks_tag 'calendar', 'map' %>
-
-<%# DON'T %>
-<%= javascript_packs_with_chunks_tag 'calendar' %>
-<%= javascript_packs_with_chunks_tag 'map' %>
-```
-
-## Package-Specific Notes
-
-- If you're using React, you need to add `"@babel/preset-react"`, to the list of `presets` in your babel config.
-- If you're using Vue Loader, you'll need to upgrade to [v15](https://vue-loader.vuejs.org/migrating.html) for Webpack 4.
-- To see what Webpacker generates for a given framework with v4, you may want to re-run `bundle exec rake webpacker:install:FRAMEWORK` and let it override the files for your given JavaScript framework, and then compare them to see what changes you'll need to make.
-
-## Excluding node_modules From Being Transpiled By Babel-Loader
-
-One change to take into consideration, is that Webpacker 4 transpiles the
-`node_modules` folder with the `babel-loader`. This folder used to be ignored by
-Webpacker 3. The new behavior helps in case some library contains ES6 code, but in
-some cases it can lead to issues. To avoid running `babel-loader` in the
-`node_modules` folder, replicating the same behavior as Webpacker 3, the
-following code can be added to `config/webpack/environment.js`:
-
-```javascript
-environment.loaders.delete('nodeModules')
-```
-
-Alternatively, in order to skip only a specific library in the `node_modules`
-folder, this code can be added:
-
-```javascript
-const nodeModulesLoader = environment.loaders.get('nodeModules')
-if (!Array.isArray(nodeModulesLoader.exclude)) {
-  nodeModulesLoader.exclude = (nodeModulesLoader.exclude == null)
-    ? []
-    : [nodeModulesLoader.exclude]
-}
-nodeModulesLoader.exclude.push(/some-library/) // replace `some-library` with
-                                               // the actual path to exclude
-```
-
-## Source Maps Enabled By Default
-
-Source maps are now enabled in production to make debugging in production easier. Enabling source maps doesn't have drawbacks for most of the applications since maps are compressed by default and aren't loaded by browsers unless Dev Tools are opened.
-
-If you want to keep the old behavior source maps can be disabled in any environment configuration, e.g:
-
-```js
-// config/webpack/production.js
-
-const environment = require('./environment')
-environment.config.merge({ devtool: false })
-
-module.exports = environment.toWebpackConfig()
-```
-
-## Namespaces
-
-The compiled packs in the public directory are now stored under namespaces:
-
-- JavaScripts are stored under `js`
-- Stylesheets are stored under `css`
-- Other resources are stored under `media`
-
-```rb
-# Before
-"runtime~hello_react" => "/packs/runtime~hello_react-da2baf7fd07b0e8b6d17.js"
-
-# After
-"runtime~hello_react" => "/packs/js/runtime~hello_react-da2baf7fd07b0e8b6d17.js"
-```
-
-## Upgrading projects with custom Webpack setups that use only the view helpers
-The default value for `extract_css` is **false** in `config/webpack.yml`. Custom webpack builds that extract the CSS such as often used with [React on Rails](https://github.com/shakacode/react_on_rails) should set this value to true or else no CSS link tags are generated.
-
-  ```yml
-  default: &default
-     # other stuff
-     extract_css: true
-     # by default, extract and emit a css file. The default is false
-  ```
-
-## Example Upgrades
-
-This is what an upgrade to Webpacker 4 looked like for existing Rails apps (please contribute yours!):
-
-- https://github.com/connorshea/ContinueFromCheckpoint/pull/77

data/docs/webpack-dev-server.md

@@ -1,92 +0,0 @@
-# webpack-dev-server
-
-
-## HTTPS
-
-If you're using the `webpack-dev-server` in development, you can serve your packs over HTTPS
-by setting the `https` option for `webpack-dev-server` to `true` in `config/webpacker.yml`,
-then start the dev server as usual with `./bin/webpack-dev-server`.
-
-Please note that the `webpack-dev-server` will use a self-signed certificate,
-so your web browser will display a warning/exception upon accessing the page. If you get
-`https://localhost:3035/sockjs-node/info?t=1503127986584 net::ERR_INSECURE_RESPONSE`
-in your console, simply open the link in your browser and accept the SSL exception.
-Now if you refresh your Rails view everything should work as expected.
-
-
-## HOT module replacement
-
-Webpacker out-of-the-box supports HMR with `webpack-dev-server` and
-you can toggle it by setting `dev_server/hmr` option inside `webpacker.yml`.
-
-Check out this guide for more information:
-
-- https://webpack.js.org/configuration/dev-server/#devserver-hot
-
-To support HMR with React you would need to add `react-hot-loader`. Checkout this guide for
-more information:
-
-- https://gaearon.github.io/react-hot-loader/getstarted/
-
-**Note:** Don't forget to disable `HMR` if you are not running `webpack-dev-server`
-otherwise you will get not found error for stylesheets.
-
-
-## Nginx
-
-If you use Nginx in development to proxy requests to your Rails server from
-another domain, like `myapp.dev`, the Webpacker middleware will be able to
-forward requests for "packs" to the webpack dev server.
-
-If you're using `inline` mode behind Nginx, you may also need to provide the
-hostname to webpack dev server so it can initiate the websocket connection for
-live reloading ([Webpack
-docs](https://webpack.js.org/configuration/dev-server/#devserver-public)).
-
-To do so, set the `public` option in `config/webpacker.yml`:
-
-```yaml
-development:
-  # ...
-  dev_server:
-    # ...
-    public: myapp.dev
-```
-
-You may also need to add the following location block to your local Nginx server
-configuration for your Rails app.
-
-```
-server {
-    listen 80;
-    server_name myapp.dev
-
-    # Proxy webpack dev server websocket requests
-    location /sockjs-node {
-        proxy_redirect off;
-        proxy_http_version 1.1;
-        proxy_set_header Upgrade $http_upgrade;
-        proxy_set_header Connection "upgrade";
-        proxy_pass http://127.0.0.1:3035; # change to match your webpack-dev-server host
-    }
-
-    # ...
-}
-```
-
-## Customizing Logging
-
-By default, the dev server will display a colored progress notification while
-your code is being compiled.  (Under the hood, we are using `webpack-dev-server
---progress --color`).  However, this might cause issues if you don't use
-`foreman` and/or try to log webpack-dev-server's output to a file.  You can
-disable this stylized output by adding `pretty: false` to your `dev_server`
-config:
-
-```yaml
-development:
-  # ...
-  dev_server:
-    # ...
-    pretty: false
-```

data/docs/webpack.md

@@ -1,364 +0,0 @@
-# webpack
-
-
-## Configuration
-
-Webpacker gives you a default set of configuration files for test, development and
-production environments in `config/webpack/*.js`. You can configure each individual
-environment in their respective files or configure them all in the base
-`config/webpack/environment.js` file.
-
-By default, you don't need to make any changes to `config/webpack/*.js`
-files since it's all standard production-ready configuration. However,
-if you do need to customize or add a new loader, this is where you would go.
-
-Here is how you can modify webpack configuration:
-
-```js
-// config/webpack/custom.js
-module.exports = {
-  resolve: {
-    alias: {
-      jquery: 'jquery/src/jquery',
-      vue: 'vue/dist/vue.js',
-      React: 'react',
-      ReactDOM: 'react-dom',
-      vue_resource: 'vue-resource/dist/vue-resource',
-    }
-  }
-}
-
-// config/webpack/environment.js
-const { environment } = require('@rails/webpacker')
-const customConfig = require('./custom')
-
-// Set nested object prop using path notation
-environment.config.set('resolve.extensions', ['.foo', '.bar'])
-environment.config.set('output.filename', '[name].js')
-
-// Merge custom config
-environment.config.merge(customConfig)
-environment.config.merge({ devtool: 'none' })
-
-// Delete a property
-environment.config.delete('output.chunkFilename')
-
-module.exports = environment
-```
-
-If you need access to configs within Webpacker's configuration,
-you can import them like so:
-
-```js
-const { config } = require('@rails/webpacker')
-
-console.log(config.output_path)
-console.log(config.source_path)
-```
-
-## Loaders
-
-You can add additional loaders beyond the base set that Webpacker provides by
-adding it to your environment. We'll use `json-loader` as an example:
-
-```
-yarn add json-loader
-```
-
-```js
-// config/webpack/environment.js
-const { environment } = require('@rails/webpacker')
-
-const jsonLoader = {
-  test: /\.json$/,
-  use: 'json-loader'
-}
-
-// Insert json loader at the end of list
-environment.loaders.append('json', jsonLoader)
-
-// Insert json loader at the top of list
-environment.loaders.prepend('json', jsonLoader)
-
-// Insert json loader after/before a given loader
-environment.loaders.insert('json', jsonLoader, { after: 'style'} )
-environment.loaders.insert('json', jsonLoader, { before: 'babel'} )
-
-module.exports = environment
-```
-
-Finally add `.json` to the list of extensions in `config/webpacker.yml`. Now if you `import()` any `.json` files inside your JavaScript
-they will be processed using `json-loader`. Voila!
-
-You can also modify the loaders that Webpacker pre-configures for you. We'll update
-the `babel` loader as an example:
-
-```js
-// config/webpack/environment.js
-const { environment } = require('@rails/webpacker')
-
-const babelLoader = environment.loaders.get('babel')
-babelLoader.options.cacheDirectory = false
-
-module.exports = environment
-```
-
-### Coffeescript 2
-
-Out of the box webpacker supports coffeescript 1,
-but here is how you can use Coffeescript 2:
-
-```
-yarn add coffeescript@2.0.1
-```
-
-```js
-// config/webpack/environment.js
-const { environment } = require('@rails/webpacker')
-
-const babelLoader = environment.loaders.get('babel')
-
-// Replace existing coffee loader with CS2 version
-environment.loaders.insert('coffee', {
-  test: /\.coffee(\.erb)?$/,
-  use:  babelLoader.use.concat(['coffee-loader'])
-})
-
-module.exports = environment
-```
-
-### React SVG loader
-
-To use react svg loader, you should append svg loader before file loader:
-
-```js
-const { environment } = require('@rails/webpacker')
-
-const babelLoader = environment.loaders.get('babel')
-
-environment.loaders.insert('svg', {
-  test: /\.svg$/,
-  use: babelLoader.use.concat([
-    {
-      loader: 'react-svg-loader',
-      options: {
-        jsx: true // true outputs JSX tags
-      }
-    }
-  ])
-}, { before: 'file' })
-
-const fileLoader = environment.loaders.get('file')
-fileLoader.exclude = /\.(svg)$/i
-```
-
-
-### Url Loader
-
-```js
-// config/webpack/loaders/url.js
-
-module.exports = {
-  test: [/\.bmp$/, /\.gif$/, /\.jpe?g$/, /\.png$/],
-  use: [{
-    loader: 'url-loader',
-    options: {
-      limit: 10000,
-      name: '[name]-[hash].[ext]'
-    }
-  }]
-}
-
-// config/webpack/environment.js
-
-const { environment } = require('@rails/webpacker')
-const url = require('./loaders/url')
-
-environment.loaders.prepend('url', url)
-
-// avoid using both file and url loaders
-environment.loaders.get('file').test = /\.(tiff|ico|svg|eot|otf|ttf|woff|woff2)$/i
-```
-
-### Overriding Loader Options in webpack 3+ (for CSS Modules etc.)
-
-In webpack 3+, if you'd like to specify additional or different options for a loader, edit `config/webpack/environment.js` and provide an options object to override. This is similar to the technique shown above, but the following example shows specifically how to apply CSS Modules, which is what you may be looking for:
-
-```javascript
-const { environment } = require('@rails/webpacker')
-const merge = require('webpack-merge')
-
-const myCssLoaderOptions = {
-  modules: {
-    localIdentName: '[name]__[local]___[hash:base64:5]'
-  },
-  sourceMap: true,
-}
-
-const CSSLoader = environment.loaders.get('sass').use.find(el => el.loader === 'css-loader')
-
-CSSLoader.options = merge(CSSLoader.options, myCssLoaderOptions)
-
-module.exports = environment
-```
-
-See [issue #756](https://github.com/rails/webpacker/issues/756#issuecomment-327148547) for additional discussion of this.
-
-For this to work, don't forget to use the `stylesheet_pack_tag`, for example:
-
-```
-<%= stylesheet_pack_tag 'YOUR_PACK_NAME_HERE' %>
-```
-
-## Plugins
-
-The process for adding or modifying webpack plugins is the same as the process
-for loaders above:
-
-```js
-// config/webpack/environment.js
-const { environment } = require('@rails/webpacker')
-const webpack = require('webpack')
-
-// Get a pre-configured plugin
-const manifestPlugin = environment.plugins.get('Manifest')
-manifestPlugin.options.writeToFileEmit = false
-
-// Add an additional plugin of your choosing : ProvidePlugin
-environment.plugins.prepend(
-  'Provide',
-  new webpack.ProvidePlugin({
-    $: 'jquery',
-    jQuery: 'jquery',
-    jquery: 'jquery',
-    'window.Tether': 'tether',
-    Popper: ['popper.js', 'default'],
-    ActionCable: 'actioncable',
-    Vue: 'vue',
-    VueResource: 'vue-resource',
-  })
-)
-
-// Insert before a given plugin
-environment.plugins.insert('CommonChunkVendor',
-  new webpack.optimize.CommonsChunkPlugin({
-    name: 'vendor', // Vendor code
-    minChunks: (module) => module.context && module.context.indexOf('node_modules') !== -1
-  })
-, { before: 'manifest' })
-
-module.exports = environment
-```
-
-## Resolved modules
-
-To add new paths to `resolve.modules`, the API is same as loaders and plugins:
-
-```js
-const { environment } = require('@rails/webpacker')
-
-// Resolved modules list API - prepend, append, insert
-environment.resolvedModules.append('vendor', 'vendor')
-```
-
-### Add SplitChunks (Webpack V4)
-Originally, chunks (and modules imported inside them) were connected by a parent-child relationship in the internal webpack graph. The CommonsChunkPlugin was used to avoid duplicated dependencies across them, but further optimizations were not possible.
-
-Since webpack v4, the CommonsChunkPlugin was removed in favor of optimization.splitChunks.
-
-For the full configuration options of SplitChunks, see the [Webpack documentation](https://webpack.js.org/plugins/split-chunks-plugin/).
-
-```js
-// config/webpack/environment.js
-
-// Enable the default config
-environment.splitChunks()
-
-// or using custom config
-environment.splitChunks((config) => Object.assign({}, config, { optimization: { splitChunks: false }}))
-```
-
-Then use the `javascript_packs_with_chunks_tag` and `stylesheet_packs_with_chunks_tag` helpers to include all the transpiled
-packs with the chunks in your view, which creates html tags for all the chunks.
-
-```erb
-<%= javascript_packs_with_chunks_tag 'calendar', 'map', 'data-turbolinks-track': 'reload' %>
-
-<script src="/packs/vendor-16838bab065ae1e314.js" data-turbolinks-track="reload"></script>
-<script src="/packs/calendar~runtime-16838bab065ae1e314.js" data-turbolinks-track="reload"></script>
-<script src="/packs/calendar-1016838bab065ae1e314.js" data-turbolinks-track="reload"></script>
-<script src="/packs/map~runtime-16838bab065ae1e314.js" data-turbolinks-track="reload"></script>
-<script src="/packs/map-16838bab065ae1e314.js" data-turbolinks-track="reload"></script>
-```
-
-**Important:** Pass all your pack names when using this helper otherwise you will
-get duplicated chunks on the page.
-
-```erb
-<%# DO %>
-<%= javascript_packs_with_chunks_tag 'calendar', 'map' %>
-
-<%# DON'T %>
-<%= javascript_packs_with_chunks_tag 'calendar' %>
-<%= javascript_packs_with_chunks_tag 'map' %>
-```
-
-For the old configuration with the CommonsChunkPlugin see below. **Note** that this functionality is deprecated in Webpack V4.
-
-#### Preloading
-
-Before preload or prefetch your assets, please read [https://developer.mozilla.org/en-US/docs/Web/HTML/Preloading_content](https://developer.mozilla.org/en-US/docs/Web/HTML/Preloading_content).
-
-Webpack also provide it's own methods for preload or prefetch [https://medium.com/webpack/link-rel-prefetch-preload-in-webpack-51a52358f84c](https://medium.com/webpack/link-rel-prefetch-preload-in-webpack-51a52358f84c).
-
-You can preload your assets with the `preload_pack_asset` helper if you have Rails >= 5.2.x.
-
-```erb
-<%= preload_pack_asset 'fonts/fa-regular-400.woff2' %>
-```
-
-**Warning:** You don't want to preload the css, you want to preload the fonts and images inside the css so that fonts, css, and images can all be downloaded in parallel instead of waiting for the browser to parse the css.
-
-### Add common chunks (deprecated in Webpack V4)
-
-The CommonsChunkPlugin is an opt-in feature that creates a separate file (known as a chunk), consisting of common modules shared between multiple entry points. By separating common modules from bundles, the resulting chunked file can be loaded once initially, and stored in the cache for later use. This results in page speed optimizations as the browser can quickly serve the shared code from the cache, rather than being forced to load a larger bundle whenever a new page is visited.
-
-Add the plugins in `config/webpack/environment.js`:
-
-```js
-const webpack = require('webpack')
-
-environment.plugins.append(
-  'CommonsChunkVendor',
-  new webpack.optimize.CommonsChunkPlugin({
-    name: 'vendor',
-    minChunks: (module) => {
-      // this assumes your vendor imports exist in the node_modules directory
-      return module.context && module.context.indexOf('node_modules') !== -1
-    }
-  })
-)
-
-environment.plugins.append(
-  'CommonsChunkManifest',
-  new webpack.optimize.CommonsChunkPlugin({
-    name: 'manifest',
-    minChunks: Infinity
-  })
-)
-```
-
-Now, add these files to your `layouts/application.html.erb`:
-
-```erb
-<%# Head %>
-
-<%= javascript_pack_tag "manifest" %>
-<%= javascript_pack_tag "vendor" %>
-
-<%# If importing any styles from node_modules in your JS app %>
-
-<%= stylesheet_pack_tag "vendor" %>
-```
-
-More detailed guides available here: [webpack guides](https://webpack.js.org/guides/)

data/docs/yarn.md

@@ -1,23 +0,0 @@
-# Yarn
-
-Webpacker by default uses `yarn` as a package manager for `node_modules`
-
-
-## Add a new npm module
-
-To add any new JS module you can use `yarn`:
-
-```bash
-yarn add bootstrap material-ui
-```
-
-## Add an npm module to `devDependencies`
-To add a new JS module that will only be available to local development:
-
-```bash
-yarn add --dev browser-sync
-```
-
-Be careful not to add any build or app related JS modules in this fashion. Adding JS modules to `devDependencies` [will block them from being installed in **any** production environment](https://yarnpkg.com/lang/en/docs/cli/install/#toc-yarn-install-production-true-false).
-
-Docs from JS modules may instruct you to use `--dev` or `devDependencies`, but this is generally under the assumption that you are using a `node.js` workflow.

data/lib/install/angular.rb

@@ -1,23 +0,0 @@
-require "webpacker/configuration"
-
-say "Copying angular example entry file to #{Webpacker.config.source_entry_path}"
-copy_file "#{__dir__}/examples/angular/hello_angular.js", "#{Webpacker.config.source_entry_path}/hello_angular.js"
-
-say "Copying hello_angular app to #{Webpacker.config.source_path}"
-directory "#{__dir__}/examples/angular/hello_angular", "#{Webpacker.config.source_path}/hello_angular"
-
-say "Installing all angular dependencies"
-run "yarn add core-js zone.js rxjs @angular/core @angular/common @angular/compiler @angular/platform-browser @angular/platform-browser-dynamic"
-
-if Rails::VERSION::MAJOR == 5 && Rails::VERSION::MINOR > 1
-  say "You need to enable unsafe-eval rule.", :yellow
-  say "This can be done in Rails 5.2+ for development environment in the CSP initializer", :yellow
-  say "config/initializers/content_security_policy.rb with a snippet like this:", :yellow
-  say "if Rails.env.development?", :yellow
-  say "  policy.script_src :self, :https, :unsafe_eval", :yellow
-  say "else", :yellow
-  say "  policy.script_src :self, :https", :yellow
-  say "end", :yellow
-end
-
-say "Webpacker now supports angular 🎉", :green

data/lib/install/coffee.rb

@@ -1,25 +0,0 @@
-require "webpacker/configuration"
-
-say "Copying coffee loader to config/webpack/loaders"
-copy_file "#{__dir__}/loaders/coffee.js", Rails.root.join("config/webpack/loaders/coffee.js").to_s
-
-say "Adding coffee loader to config/webpack/environment.js"
-insert_into_file Rails.root.join("config/webpack/environment.js").to_s,
-  "const coffee =  require('./loaders/coffee')\n",
-  after: /require\(('|")@rails\/webpacker\1\);?\n/
-
-insert_into_file Rails.root.join("config/webpack/environment.js").to_s,
-  "environment.loaders.prepend('coffee', coffee)\n",
-  before: "module.exports"
-
-say "Updating webpack paths to include .coffee file extension"
-insert_into_file Webpacker.config.config_path, "- .coffee\n".indent(4), after: /\s+extensions:\n/
-
-say "Copying the example entry file to #{Webpacker.config.source_entry_path}"
-copy_file "#{__dir__}/examples/coffee/hello_coffee.coffee",
-  "#{Webpacker.config.source_entry_path}/hello_coffee.coffee"
-
-say "Installing all Coffeescript dependencies"
-run "yarn add coffeescript@1.12.7 coffee-loader"
-
-say "Webpacker now supports Coffeescript 🎉", :green

data/lib/install/config/.browserslistrc

@@ -1 +0,0 @@
-defaults