webpacker-jets 3.2.100

data/Gemfile

@@ -0,0 +1,13 @@
+source "https://rubygems.org"
+
+gemspec
+
+gem "rails"
+gem "rake", ">= 11.1"
+gem "rubocop", ">= 0.49", require: false
+gem "rack-proxy", require: false
+
+group :test do
+  gem "minitest", "~> 5.0"
+  gem "byebug"
+end

data/Gemfile.lock

@@ -0,0 +1,154 @@
+PATH
+  remote: .
+  specs:
+    webpacker-jets (3.2.100)
+      activesupport (>= 4.2)
+      rack-proxy (>= 0.6.1)
+      railties (>= 4.2)
+
+GEM
+  remote: https://rubygems.org/
+  specs:
+    actioncable (5.2.1)
+      actionpack (= 5.2.1)
+      nio4r (~> 2.0)
+      websocket-driver (>= 0.6.1)
+    actionmailer (5.2.1)
+      actionpack (= 5.2.1)
+      actionview (= 5.2.1)
+      activejob (= 5.2.1)
+      mail (~> 2.5, >= 2.5.4)
+      rails-dom-testing (~> 2.0)
+    actionpack (5.2.1)
+      actionview (= 5.2.1)
+      activesupport (= 5.2.1)
+      rack (~> 2.0)
+      rack-test (>= 0.6.3)
+      rails-dom-testing (~> 2.0)
+      rails-html-sanitizer (~> 1.0, >= 1.0.2)
+    actionview (5.2.1)
+      activesupport (= 5.2.1)
+      builder (~> 3.1)
+      erubi (~> 1.4)
+      rails-dom-testing (~> 2.0)
+      rails-html-sanitizer (~> 1.0, >= 1.0.3)
+    activejob (5.2.1)
+      activesupport (= 5.2.1)
+      globalid (>= 0.3.6)
+    activemodel (5.2.1)
+      activesupport (= 5.2.1)
+    activerecord (5.2.1)
+      activemodel (= 5.2.1)
+      activesupport (= 5.2.1)
+      arel (>= 9.0)
+    activestorage (5.2.1)
+      actionpack (= 5.2.1)
+      activerecord (= 5.2.1)
+      marcel (~> 0.3.1)
+    activesupport (5.2.1)
+      concurrent-ruby (~> 1.0, >= 1.0.2)
+      i18n (>= 0.7, < 2)
+      minitest (~> 5.1)
+      tzinfo (~> 1.1)
+    arel (9.0.0)
+    ast (2.4.0)
+    builder (3.2.3)
+    byebug (10.0.2)
+    concurrent-ruby (1.0.5)
+    crass (1.0.4)
+    erubi (1.7.1)
+    globalid (0.4.1)
+      activesupport (>= 4.2.0)
+    i18n (1.1.1)
+      concurrent-ruby (~> 1.0)
+    jaro_winkler (1.5.1)
+    loofah (2.2.3)
+      crass (~> 1.0.2)
+      nokogiri (>= 1.5.9)
+    mail (2.7.1)
+      mini_mime (>= 0.1.1)
+    marcel (0.3.3)
+      mimemagic (~> 0.3.2)
+    method_source (0.9.0)
+    mimemagic (0.3.2)
+    mini_mime (1.0.1)
+    mini_portile2 (2.3.0)
+    minitest (5.11.3)
+    nio4r (2.3.1)
+    nokogiri (1.8.5)
+      mini_portile2 (~> 2.3.0)
+    parallel (1.12.1)
+    parser (2.5.3.0)
+      ast (~> 2.4.0)
+    powerpack (0.1.2)
+    rack (2.0.5)
+    rack-proxy (0.6.5)
+      rack
+    rack-test (1.1.0)
+      rack (>= 1.0, < 3)
+    rails (5.2.1)
+      actioncable (= 5.2.1)
+      actionmailer (= 5.2.1)
+      actionpack (= 5.2.1)
+      actionview (= 5.2.1)
+      activejob (= 5.2.1)
+      activemodel (= 5.2.1)
+      activerecord (= 5.2.1)
+      activestorage (= 5.2.1)
+      activesupport (= 5.2.1)
+      bundler (>= 1.3.0)
+      railties (= 5.2.1)
+      sprockets-rails (>= 2.0.0)
+    rails-dom-testing (2.0.3)
+      activesupport (>= 4.2.0)
+      nokogiri (>= 1.6)
+    rails-html-sanitizer (1.0.4)
+      loofah (~> 2.2, >= 2.2.2)
+    railties (5.2.1)
+      actionpack (= 5.2.1)
+      activesupport (= 5.2.1)
+      method_source
+      rake (>= 0.8.7)
+      thor (>= 0.19.0, < 2.0)
+    rainbow (3.0.0)
+    rake (12.3.1)
+    rubocop (0.60.0)
+      jaro_winkler (~> 1.5.1)
+      parallel (~> 1.10)
+      parser (>= 2.5, != 2.5.1.1)
+      powerpack (~> 0.1)
+      rainbow (>= 2.2.2, < 4.0)
+      ruby-progressbar (~> 1.7)
+      unicode-display_width (~> 1.4.0)
+    ruby-progressbar (1.10.0)
+    sprockets (3.7.2)
+      concurrent-ruby (~> 1.0)
+      rack (> 1, < 3)
+    sprockets-rails (3.2.1)
+      actionpack (>= 4.0)
+      activesupport (>= 4.0)
+      sprockets (>= 3.0.0)
+    thor (0.20.0)
+    thread_safe (0.3.6)
+    tzinfo (1.2.5)
+      thread_safe (~> 0.1)
+    unicode-display_width (1.4.0)
+    websocket-driver (0.7.0)
+      websocket-extensions (>= 0.1.0)
+    websocket-extensions (0.1.3)
+
+PLATFORMS
+  ruby
+
+DEPENDENCIES
+  bundler (~> 1.12)
+  byebug
+  minitest (~> 5.0)
+  rack-proxy
+  rails
+  rake (>= 11.1)
+  rubocop (>= 0.49)
+  webpacker-jets!
+
+BUNDLED WITH
+   1.16.3

data/MIT-LICENSE

@@ -0,0 +1,20 @@
+Copyright (c) 2016-2017 David Heinemeier Hansson, Basecamp
+
+Permission is hereby granted, free of charge, to any person obtaining
+a copy of this software and associated documentation files (the
+"Software"), to deal in the Software without restriction, including
+without limitation the rights to use, copy, modify, merge, publish,
+distribute, sublicense, and/or sell copies of the Software, and to
+permit persons to whom the Software is furnished to do so, subject to
+the following conditions:
+
+The above copyright notice and this permission notice shall be
+included in all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
+EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
+MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
+NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE
+LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION
+OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION
+WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

data/README.md

@@ -0,0 +1,445 @@
+# Webpacker
+
+NOTE: This is a fork of [rails/webpacker](https://github.com/rails/webpacker) to work with [jets](http://rubyonjets.com/). The master branch tries to mirror the upstream repo and jets changes are actually in the [tongueroo/webpacker jets branch](https://github.com/tongueroo/webpacker/tree/jets).
+
+In that branch the gem is also renamed and released as webpacker-jets.
+
+## Release
+
+    git checkout jets
+    rake release
+
+The rest of the Readme is the original README.
+
+---
+
+![travis-ci status](https://api.travis-ci.org/rails/webpacker.svg?branch=master)
+[![node.js](https://img.shields.io/badge/node-%3E%3D%206.0.0-brightgreen.svg)](https://nodejs.org/en/)
+[![Gem](https://img.shields.io/gem/v/webpacker.svg)](https://github.com/rails/webpacker)
+
+Webpacker makes it easy to use the JavaScript pre-processor and bundler
+[webpack 3.x.x+](https://webpack.js.org/)
+to manage application-like JavaScript in Rails. It coexists with the asset pipeline,
+as the primary purpose for webpack is app-like JavaScript, not images, CSS, or
+even JavaScript Sprinkles (that all continues to live in app/assets).
+
+However, it is possible to use Webpacker for CSS, images and fonts assets as well,
+in which case you may not even need the asset pipeline. This is mostly relevant when exclusively using component-based JavaScript frameworks.
+
+<!-- START doctoc generated TOC please keep comment here to allow auto update -->
+<!-- DON'T EDIT THIS SECTION, INSTEAD RE-RUN doctoc TO UPDATE -->
+## Table of Contents
+
+- [Prerequisites](#prerequisites)
+- [Features](#features)
+- [Installation](#installation)
+  - [Usage](#usage)
+  - [Development](#development)
+  - [webpack configuration](#webpack-configuration)
+  - [Upgrading](#upgrading)
+  - [Yarn Integrity](#yarn-integrity)
+- [Integrations](#integrations)
+  - [React](#react)
+  - [Angular with TypeScript](#angular-with-typescript)
+  - [Vue](#vue)
+  - [Elm](#elm)
+  - [Coffeescript](#coffeescript)
+  - [Erb](#erb)
+- [Paths](#paths)
+  - [Resolved](#resolved)
+  - [Watched](#watched)
+- [Deployment](#deployment)
+- [Docs](#docs)
+- [License](#license)
+
+<!-- END doctoc generated TOC please keep comment here to allow auto update -->
+
+
+## Prerequisites
+
+* Ruby 2.2+
+* Rails 4.2+
+* Node.js 6.0.0+
+* Yarn 0.25.2+
+
+
+## Features
+
+* [webpack 3.x.x](https://webpack.js.org/)
+* ES6 with [babel](https://babeljs.io/)
+* Automatic code splitting using multiple entry points
+* Stylesheets - Sass and CSS
+* Images and fonts
+* PostCSS - Auto-Prefixer
+* Asset compression, source-maps, and minification
+* CDN support
+* React, Angular, Elm and Vue support out-of-the-box
+* Rails view helpers
+* Extensible and configurable
+
+
+## Installation
+
+You can either add Webpacker during setup of a new Rails 5.1+ application
+using new `--webpack` option:
+
+```bash
+# Available Rails 5.1+
+rails new myapp --webpack
+```
+
+Or add it to your `Gemfile`:
+
+```ruby
+# Gemfile
+gem 'webpacker', '~> 3.0'
+
+# OR if you prefer to use master
+gem 'webpacker', git: 'https://github.com/rails/webpacker.git'
+```
+
+and finally, run following to install Webpacker:
+
+```bash
+bundle
+jets webpacker:install
+
+# OR (on rails version < 5.0)
+bundle exec rake webpacker:install
+```
+
+
+### Usage
+
+Once installed you can start writing modern ES6-flavored JavaScript app today:
+
+```yml
+app/javascript:
+  ├── packs:
+  │   # only webpack entry files here
+  │   └── application.js
+  └── src:
+  │   └── application.css
+  └── images:
+      └── logo.svg
+```
+
+You can then link the JavaScript pack in Rails view using `javascript_pack_tag` helper.
+If you have styles imported in your pack file, you can link using `stylesheet_pack_tag`:
+
+```erb
+<%= javascript_pack_tag 'application' %>
+<%= stylesheet_pack_tag 'application' %>
+```
+
+If you want to link a static asset for `<link rel="prefetch">` or `<img />` tag, you
+can use `asset_pack_path` helper:
+
+```erb
+<link rel="prefetch" href="<%= asset_pack_path 'application.css' %>" />
+<img src="<%= asset_pack_path 'images/logo.svg' %>" />
+```
+
+**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`.
+Both are thin wrappers around the standard `webpack.js` and `webpack-dev-server.js`
+executable to ensure that the right configuration file and environment variables
+are loaded depending on your environment.
+
+In development, Webpacker compiles on demand rather than upfront by default. This
+happens when you refer to any of the pack assets using the Webpacker helper methods.
+That means you don't have to run any separate process. Compilation errors are logged
+to the standard Rails log.
+
+If you want to use live code reloading, or you have enough JavaScript that on-demand compilation is too slow, you'll need to run `./bin/webpack-dev-server` or `ruby ./bin/webpack-dev-server` if on windows,
+in a separate terminal from `bundle exec rails s`. This process will watch for changes
+in the `app/javascript/packs/*.js` files and automatically reload the browser to match.
+
+```bash
+# webpack dev server
+./bin/webpack-dev-server
+
+# watcher
+./bin/webpack --colors --progress
+
+# standalone build
+./bin/webpack
+```
+
+Once you start this development server, Webpacker will automatically start proxying all
+webpack asset requests to this server. When you stop the server, it'll revert to
+on-demand compilation again.
+
+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, and that the _same_ environment variables must
+be available to the `rails server` process.
+
+```bash
+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 set the `host` when running `./bin/webpack-dev-server` binstub:
+
+```bash
+WEBPACKER_DEV_SERVER_HOST=0.0.0.0 ./bin/webpack-dev-server
+```
+
+**Note:** You need to allow webpack-dev-server host as allowed origin for `connect-src` if you are running your application in a restrict CSP environment like Rails 5.2+. This can be done in Rails 5.2+ for development environment in the CSP initializer `config/initializers/content_security_policy.rb` with a snippet like this:
+
+```ruby
+  p.connect_src :self, :https, 'http://localhost:3035', 'ws://localhost:3035' if Rails.env.development?
+```
+
+**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 related npm modules:
+
+```bash
+bundle update webpacker
+yarn upgrade @rails/webpacker --latest
+yarn upgrade webpack-dev-server --latest
+```
+
+### Yarn Integrity
+
+By default in development, webpacker runs a yarn integrity check to ensure that all local npm packages are up-to-date. This is similar to what bundler does currently in Rails, but for JavaScript packages. If your system is out of date, then Rails will not initialize and you will be asked to upgrade your local npm packages by running `yarn install`.
+
+To turn off this option, you will need to override the default by adding a new config options to your Rails development environment configuration file (`config/environment/development.rb`):
+
+```
+config.webpacker.check_yarn_integrity = false
+```
+
+You may also turn on this option by adding the config option to any Rails environment configuration file:
+
+```
+config.webpacker.check_yarn_integrity = true
+```
+
+## Integrations
+
+Webpacker ships with basic out-of-the-box integration for React, Angular, Vue and Elm.
+You can see a list of available commands/tasks by running `jets webpacker`:
+
+### React
+
+To use Webpacker with [React](https://facebook.github.io/react/), create a
+new Rails 5.1+ app using `--webpack=react` option:
+
+```bash
+# Rails 5.1+
+rails new myapp --webpack=react
+```
+
+(or run `jets webpacker:install:react` in a existing Rails app already
+setup with Webpacker).
+
+The installer will add all relevant dependencies using Yarn, any changes
+to the configuration files and an example React component to your
+project in `app/javascript/packs` so that you can experiment with React right away.
+
+
+### Angular with TypeScript
+
+To use Webpacker with [Angular](https://angular.io/), create a
+new Rails 5.1+ app using `--webpack=angular` option:
+
+```bash
+# Rails 5.1+
+rails new myapp --webpack=angular
+```
+
+(or run `jets webpacker:install:angular` on a Rails app already
+setup with Webpacker).
+
+The installer will add TypeScript and Angular core libraries using Yarn plus
+any changes to the configuration files. An example component is written in
+TypeScript will also be added to your project in `app/javascript` so that
+you can experiment with Angular right away.
+
+By default Angular uses a JIT compiler for development environment, this
+compiler is not compatible with restrictive CSP (Content Security
+Policy) environments like Rails 5.2+. You can use Angular AOT compiler
+in development with the [@ngtools/webpack](https://www.npmjs.com/package/@ngtools/webpack#usage) plugin.
+
+Alternatively if you're using Rails 5.2+ you can enable `unsafe-eval` rule for
+development environment, this can be done in the `config/initializers/content_security_policy.rb`
+with the following configuration:
+
+```ruby
+  if Rails.env.development?
+    p.script_src :self, :https, :unsafe_eval
+  else
+    p.script_src :self, :https
+  end
+```
+
+
+### Vue
+
+To use Webpacker with [Vue](https://vuejs.org/), create a
+new Rails 5.1+ app using `--webpack=vue` option:
+
+```bash
+# Rails 5.1+
+rails new myapp --webpack=vue
+```
+(or run `jets webpacker:install:vue` on a Rails app already setup with Webpacker).
+
+The installer will add Vue and required libraries using Yarn plus
+any changes to the configuration files. An example component will
+also be added to your project in `app/javascript` so that you can
+experiment Vue right away.
+
+If you're using Rails 5.2+ you need to enable `unsafe-eval` rule for development environment,
+this can be done in the `config/initializers/content_security_policy.rb` with the following
+configuration:
+
+```ruby
+  if Rails.env.development?
+    p.script_src :self, :https, :unsafe_eval
+  else
+    p.script_src :self, :https
+  end
+```
+You can read more this in [Vue docs](https://vuejs.org/v2/guide/installation.html#CSP-environments).
+
+
+### Elm
+
+To use Webpacker with [Elm](http://elm-lang.org), create a
+new Rails 5.1+ app using `--webpack=elm` option:
+
+```
+# Rails 5.1+
+rails new myapp --webpack=elm
+```
+
+(or run `jets webpacker:install:elm` on a Rails app already setup with Webpacker).
+
+The Elm library and core packages will be added via Yarn and Elm itself.
+An example `Main.elm` app will also be added to your project in `app/javascript`
+so that you can experiment with Elm right away.
+
+### Coffeescript
+
+To add [Coffeescript](http://coffeescript.org/) support,
+run `bundle exec rails webpacker:install:coffee` on a Rails app already
+setup with Webpacker.
+
+An example `hello_coffee.coffee` file will also be added to your project
+in `app/javascript/packs` so that you can experiment with Coffeescript right away.
+
+### Erb
+
+To add [Erb](https://apidock.com/ruby/ERB) support in your JS templates,
+run `bundle exec rails webpacker:install:erb` on a Rails app already
+setup with Webpacker.
+
+An example `hello_erb.js.erb` file will also be added to your project
+in `app/javascript/packs` so that you can experiment with Erb flavoured
+javascript right away.
+
+
+## Paths
+
+By default, Webpacker ships with simple conventions for where the JavaScript
+app files and compiled webpack bundles will go in your Rails app,
+but all these options are configurable from `config/webpacker.yml` file.
+
+The configuration for what webpack is supposed to compile by default rests
+on the convention that every file in `app/javascript/packs/*`**(default)**
+or whatever path you set for `source_entry_path` in the `webpacker.yml` configuration
+is turned into their own output files (or entry points, as webpack calls it). Therefore you don't want to put anything inside `packs` directory that you do not want to be
+an entry file. As a rule of thumb, put all files you want to link in your views inside
+"packs" directory and keep everything else under `app/javascript`.
+
+Suppose you want to change the source directory from `app/javascript`
+to `frontend` and output to `assets/packs`. This is how you would do it:
+
+```yml
+# config/webpacker.yml
+source_path: frontend
+source_entry_path: packs
+public_output_path: assets/packs # outputs to => public/assets/packs
+```
+
+Similarly you can also control and configure `webpack-dev-server` settings from `config/webpacker.yml` file:
+
+```yml
+# config/webpacker.yml
+development:
+  dev_server:
+    host: localhost
+    port: 3035
+```
+
+If you have `hmr` turned to true, then the `stylesheet_pack_tag` generates no output, as you will want to configure your styles to be inlined in your JavaScript for hot reloading. During production and testing, the `stylesheet_pack_tag` will create the appropriate HTML tags.
+
+
+### Resolved
+
+If you are adding Webpacker to an existing app that has most of the assets inside
+`app/assets` or inside an engine and you want to share that
+with webpack modules then you can use `resolved_paths`
+option available in `config/webpacker.yml`, which lets you
+add additional paths webpack should lookup when resolving modules:
+
+```yml
+resolved_paths: ['app/assets']
+```
+
+You can then import them inside your modules like so:
+
+```js
+// Note it's relative to parent directory i.e. app/assets
+import 'stylesheets/main'
+import 'images/rails.png'
+```
+
+**Note:** Please be careful when adding paths here otherwise it
+will make the compilation slow, consider adding specific paths instead of
+whole parent directory if you just need to reference one or two modules
+
+
+### Watched
+
+By default, the lazy compilation is cached until a file is changed under
+tracked paths. You can configure the paths tracked
+by adding new paths to `watched_paths` array, much like Rails `autoload_paths`:
+
+```rb
+# config/initializers/webpacker.rb
+# or config/application.rb
+Webpacker::Compiler.watched_paths << 'bower_components'
+```
+
+
+## Deployment
+
+Webpacker hooks up a new `webpacker:compile` task to `assets:precompile`, which gets run whenever you run `assets:precompile`. If you are not using Sprockets `webpacker:compile` is automatically aliased to `assets:precompile`. Remember to set NODE_ENV environment variable to production during deployment or when running the rake task.
+
+## Docs
+
+You can find more detailed guides under [docs](./docs).
+
+
+## License
+Webpacker is released under the [MIT License](https://opensource.org/licenses/MIT).