opal-webpack-loader 0.11.1 → 0.12.0

Sign up to get free protection for your applications and to get access to all the features.
checksums.yaml CHANGED
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  SHA256:
3
- metadata.gz: f1a1b24301ed05a439abf847ae77a460919a227d250432d0c769d3080d100dec
4
- data.tar.gz: 48f48641c277ecbf2fd50a7c274bdcf94b960dc28bf5103da70555815b70112f
3
+ metadata.gz: cd885fbcf9cc014f09d6f42a31ad1d0b815b17d587d33808156ec79579255f86
4
+ data.tar.gz: 2558ff9c76e5a07d98b6f0a94f829dcd51460197ef7176ff25fed2f742af2c31
5
5
  SHA512:
6
- metadata.gz: 7ef00f2c1e57f71eadaae2a3b2edc6c47745c980a1f85921b0ca9e6e0b092e960c9c3971826ffec3ca22b42e56d45a9b36bd6d692b794b97f23c2343f043e25d
7
- data.tar.gz: a5ebdd0518490d0eea2e78de43f1527f333b32ab778603fd24cc8052c3870aa4e5408a631c6a0a676185d7355f488c4cc605f5b8a793418a2072ed3c09174b85
6
+ metadata.gz: '07961ad0a9c60e9de83f6caedb60c1038bd721e898b52a8eaf5e8b118b268baba5d4527764d500a1e6a8bacb2ae88543896a959fd45245e61f331dbf21809f6c'
7
+ data.tar.gz: 7ecd145ff65cee4b2c5f9b59a5f096736356e0283f8548ae7743bcd845e2d0400df5ed0dd8087166269622aeadf58cf1c06da8f555d52954338f0c0b1c918bb0
data/README.md CHANGED
@@ -1,216 +1,212 @@
1
- <h1 align="center">
2
- <img src="https://raw.githubusercontent.com/isomorfeus/opal-webpack-loader/master/docs/owl.png"
3
- align="center" title="Opal logo by Elia Schito combined with Webpack Logo" width="111" height="125" />
4
- <br/>
5
- opal-webpack-loader<br/>
6
- <img src="https://img.shields.io/badge/Opal-Ruby%20💛%20JavaScript%20💛%20Webpack-yellow.svg?logo=ruby&style=social&logoColor=777"/>
7
- </h1>
8
-
9
- Bundle assets with webpack, resolve and compile opal ruby files and import them in the bundle, without sprockets or the webpacker gem
10
- (but can be used with both of them too).
11
- Includes a loader and resolver plugin for webpack.
12
-
13
- ### Community and Support
14
- At the [Isomorfeus Framework Project](http://isomorfeus.com)
15
-
16
- ### Tested
17
- [TravisCI](https://travis-ci.org): [![Build Status](https://travis-ci.org/isomorfeus/opal-webpack-loader.svg?branch=master)](https://travis-ci.org/isomorfeus/opal-webpack-loader)
18
-
19
- ### Features
20
- - comes with a installer for rails and other frameworks
21
- - webpack based build process
22
- - very fast, asynchronous and parallel builds of opal code:
23
- opal-webpack-loader-0.7.1 compiles all of opal, a bunch of gems and over 19000SLC on a
24
- Intel® Core™ i7-7700HQ CPU @ 2.80GHz × 8, with 8 workers in around 1850ms
25
- - support for memcached or redis as compiler cache
26
- - fast builds on windows too, parallel when building multiple assets with parallel-webpack
27
- - opal modules are packaged as es6 modules
28
- - support for rails with webpacker
29
- - other webpack features become available, like:
30
- - source maps
31
- - multiple targets: web (for browsers), node (for server side rendering) and webworker (for Web Workers)
32
- - hot module reloading for opal ruby code and stylesheets and html views
33
- - tree shaking
34
- - code splitting
35
- - lazy loading
36
- - everything else webpack can do, like loading stylesheets, etc.
37
-
38
- ### Requirements
39
- - npm or yarn
40
- - opal-webpack-loader consists of 2 parts, the npm package and the gem, both are required and must be the same version.
41
- - webpack ^4.46
42
- - webpack-dev-server ^3.11.0
43
- - one of the ES6 modules branches of opal
44
- - [PR#1973](https://github.com/opal/opal/pull/1973), (experimental) implementing ES6 modules and changes for 'strict' mode,
45
- based on Opal master 1.0.0 using javascript string objects "mutable strings" by default for all strings
46
-
47
- `gem 'opal', github: 'janbiedermann/opal', branch: 'es6_modules_string'`
48
-
49
- - [PR#1976](https://github.com/opal/opal/pull/1976), (recommended) implementing ES6 modules and changes for 'strict' mode,
50
- based on Opal master 1.1.0 using javascript string primitives and providing nice features like `require_lazy 'my_module'`
51
-
52
- `gem 'opal', github: 'janbiedermann/opal', branch: 'es6_modules_1_1'`
53
-
54
- - if you have the webpacker gem installed somewhere, it should be a version supporting webpack 4
55
- - ruby, version 2.5 or higher recommended
56
- - bundler, latest version recommended
57
-
58
- ### Installation
59
-
60
- #### Using the installer
61
- First install the gem:
62
- ```
63
- gem install 'opal-webpack-loader'
64
- ```
65
-
66
- Continue here:
67
- - [Install for Rails like projects](https://github.com/isomorfeus/opal-webpack-loader/blob/master/docs/installation_rails.md)
68
- - [Install for Cuba, Roda, Sinatra and other projects with a flat structure](https://github.com/isomorfeus/opal-webpack-loader/blob/master/docs/installation_flat.md)
69
- - [Manual Installation](https://github.com/isomorfeus/opal-webpack-loader/blob/master/docs/installation_manual.md)
70
-
71
- ### Example applications
72
- - [Are here](https://github.com/isomorfeus/opal-webpack-loader/tree/master/example_apps/)
73
- - A minimal webpack only example from @sunrick is [here](https://github.com/sunrick/opal-hello-world-webpack).
74
-
75
- ### General Usage without Webpacker
76
-
77
- After installing owl with the installer, three scripts are provided in package.json:
78
- - `development` - runs the webpack-dev-server, use for general development, provides fast reloads, entry is application.js
79
- - `debug` - runs the webpack-dev-server, use for debugging, provides source maps, entry is application_debug.js. Additional debugging tools may be added there.
80
- - `production_build` - runs webpack to build assets for production, entry is application.js
81
-
82
- These scripts can for example be run with:
83
- `yarn run debug` or `npm run debug`
84
-
85
- The default config provides several targets and entries:
86
-
87
- - **Browser**: the webpack target is 'web' and the javascript entry file for imports is `application.js` - general use for the application with all
88
- browser features, the opal ruby entry file is `opal_loader.rb` in the opal or app/opal directory of the app.
89
- - **Server Side Rendering**: the webpack target is `node` and the javascript entry file for imports is `application_ssr.js` - general use for the
90
- application server side rendering, several Browser features are unavailable, no `window`, no `document`, some node features are available,
91
- like `Buffer`, the opal ruby entry file is `opal_loader.rb` in the opal or app/opal directory of the app.
92
- (meant to be used with isomorfeus-speednode, standard ExecJS limitations prevent certain webpack features)
93
- - **Web Worker**: the webpack target is 'webworker' and the javascript entry file for imports is `application_webworker.js` - used to initialize Web
94
- Workers in the browser, the opal ruby entry file is `opal_webworker_loader.rb` in the opal or app/opal directory of the app.
95
-
96
- Only the browser target is build by default. To builds the other target, just add the needed targets to the last line of the webpack config,
97
- for example to `development.js`:
98
- default config:
99
- ```javascript
100
- module.exports = [ browser ];
101
- ```
102
- modified config with ssr and web_worker targets enabled:
103
- ```javascript
104
- module.exports = [ browser, ssr, web_worker ];
105
- ```
106
- Same works for the `debug.js` and `production.js` webpack config files.
107
-
108
- Also a Procfile has been installed, for rails its easy to startup rails and webpack with foreman:
109
- `foreman start` (`gem install foreman` if you dont have it already). It will start rails and webpack-dev-server with the development script.
110
-
111
- For non rails installation check the Procfile and add a starter for your app.
112
-
113
- #### Opal Ruby Application Files
114
- For rails installations with the installer they all go into: `app/opal`, for flat installations in the `opal` directory.
115
- In this directory there already is a `opal_loader.rb` which is the entry point for your app.
116
-
117
- #### Stylesheets
118
- Stylesheets are hot reloaded too with the default config installed by the installer. Also they are imported into application.js by default.
119
- For rails like applications stylesheets are in `app/assets/stylesheets/application.css`, for flat applications they are in `styles/application.css`.
120
- SCSS is supported too by the default config.
121
-
122
- #### Views
123
- For rails like applications a watcher for `app/views` is installed by default. The watcher will trigger a page reload when views are changed.
124
- For flat applications nothing is configured by default, as there are to many ways to generate views, they are not even needed with
125
- frameworks like isomorfeus. Instead the section for configuring a view watcher is included in the development.js and debug.js webpack
126
- config, but it is commented out. Please see those files and adjust to your liking.
127
-
128
- #### Parallel compilation for speed
129
-
130
- Since version 0.8.0 the number of CPUs is automatically determined and a appropriate number of of compile server workers is started automatically.
131
-
132
- ### Source Maps
133
-
134
- [Source Maps](https://github.com/isomorfeus/opal-webpack-loader/blob/master/docs/source_maps.md)
135
-
136
- ### Hot Module Reloading
137
- [Hot Module Reloading](https://github.com/isomorfeus/opal-webpack-loader/blob/master/docs/hot_module_reloading.md)
138
-
139
- ### Opal Load Path
140
- The projects directory for opal ruby files must be in the opal load path. This is done in the initializer for rails apps in
141
- config/initializers/opal_webpack_loader.rb or in 'owl_init.rb' for non rails apps, for example:
142
- ```ruby
143
- Opal.append_path(File.realdirpath('app/opal'))
144
- ```
145
-
146
- ### View Helper
147
- In Rails or frameworks that support `javscript_include_tag`, add to the app/helpers/application_helper.rb
148
- ```ruby
149
- module ApplicationHelper
150
- include OpalWebpackLoader::RailsViewHelper
151
- ```
152
- in other frameworks that dont have a `javascript_include_tag`:
153
- ```ruby
154
- module MyProjectsViewThings
155
- include OpalWebpackLoader::ViewHelper
156
- ```
157
-
158
- Then you can use in your views:
159
- ```ruby
160
- owl_script_tag('application.js')
161
- ```
162
- #### Compile Server and app_loader.rb
163
- For non rails projects, determining Opal load paths, for the resolver and compile server to work properly, may not be obvious. For these cases
164
- a file `app_loader.rb` in the projects root can be created which just loads all requirements without starting anything.
165
- Usually it would just setup bundler with the appropriate options, for example:
166
- ```ruby
167
- require 'bundler/setup'
168
- if ENV['RACK_ENV'] && ENV['RACK_ENV'] == 'test'
169
- Bundler.require(:default, :test)
170
- elsif ENV['RACK_ENV'] && ENV['RACK_ENV'] == 'production'
171
- Bundler.require(:default, :production)
172
- else
173
- Bundler.require(:default, :development)
174
- end
175
- Opal.append_path(File.realdirpath('opal')) # this is a good place to add the directory with opal files to the opal load path
176
- ```
177
- When this file exists, the compile server will load it and generate Opal load paths accordingly for the resolver.
178
-
179
- #### Project configuration options for the view helper
180
- These setting are in the initializer in config/initializers/opal_webpack_loader.rb for rails like apps, or owl_init.rb for others.
181
- ```ruby
182
- OpalWebpackLoader.use_manifest = false
183
- ```
184
- If the manifest file should be used, use_manifest should be true.
185
- ```ruby
186
- OpalWebpackLoader.manifest_path = File.join(Dir.getwd, 'public', 'assets', 'manifest.json')
187
- ```
188
- Sets the path to the webpack (with the [webpack-manifest-plugin](https://www.npmjs.com/package/webpack-manifest-plugin)) generated manifest.json to look up assets.
189
- ```ruby
190
- OpalWebpackLoader.client_asset_path = 'http://localhost:3035/assets/'
191
- ```
192
- The path to prepend to the assets as configured in the webpack config 'publicPath'.
193
- In the config example below its `publicPath: 'http://localhost:3025/assets'` so
194
- client_asset_path should be set to the same.
195
-
196
- For **production** use with readily precompiled and compressed assets which contain a fingerprint in the name (webpacks [chunkhash]),
197
- and if the path in the manifest is the full path to the asset as configured in webpack,
198
- these settings would work:
199
- ```ruby
200
- OpalWebpackLoader.use_manifest = true
201
- OpalWebpackLoader.manifest_path = File.join(Dir.getwd, 'public', 'assets', 'manifest.json')
202
- OpalWebpackLoader.client_asset_path = ''
203
- ```
204
-
205
- For **development** use with webpack-dev-server, with no manifest, these settings would work:
206
- ```ruby
207
- OpalWebpackLoader.use_manifest = false
208
- OpalWebpackLoader.manifest_path = File.join(Dir.getwd, 'public', 'assets', 'manifest.json') # doesn't matter, not used
209
- OpalWebpackLoader.client_asset_path = 'http://localhost:3035/assets/'
210
- ```
211
- ### Advanced Options
212
- [Advanced Options](https://github.com/isomorfeus/opal-webpack-loader/blob/master/docs/advanced_options.md)
213
- ### Tests
214
- - clone the repo
215
- - `bundle install`
216
- - `bundle exec rspec`
1
+ <h1 align="center">
2
+ <img src="https://raw.githubusercontent.com/isomorfeus/opal-webpack-loader/master/docs/owl.png"
3
+ align="center" title="Opal logo by Elia Schito combined with Webpack Logo" width="111" height="125" />
4
+ <br/>
5
+ opal-webpack-loader<br/>
6
+ <img src="https://img.shields.io/badge/Opal-Ruby%20💛%20JavaScript%20💛%20Webpack-yellow.svg?logo=ruby&style=social&logoColor=777"/>
7
+ </h1>
8
+
9
+ Bundle assets with webpack, resolve and compile opal ruby files and import them in the bundle, without sprockets or the webpacker gem
10
+ (but can be used with both of them too).
11
+ Includes a loader and resolver plugin for webpack.
12
+
13
+ ### Community and Support
14
+ At the [Isomorfeus Framework Project](http://isomorfeus.com)
15
+
16
+ ### Tested
17
+ [TravisCI](https://travis-ci.org): [![Build Status](https://travis-ci.org/isomorfeus/opal-webpack-loader.svg?branch=master)](https://travis-ci.org/isomorfeus/opal-webpack-loader)
18
+
19
+ ### Features
20
+ - comes with a installer for rails and other frameworks
21
+ - webpack based build process
22
+ - very fast, asynchronous and parallel builds of opal code:
23
+ opal-webpack-loader-0.7.1 compiles all of opal, a bunch of gems and over 19000SLC on a
24
+ Intel® Core™ i7-7700HQ CPU @ 2.80GHz × 8, with 8 workers in around 1850ms
25
+ - support for memcached or redis as compiler cache
26
+ - fast builds on windows too, parallel when building multiple assets with parallel-webpack
27
+ - opal modules are packaged as es6 modules
28
+ - support for rails with webpacker
29
+ - other webpack features become available, like:
30
+ - source maps
31
+ - multiple targets: web (for browsers), node (for server side rendering) and webworker (for Web Workers)
32
+ - hot module reloading for opal ruby code and stylesheets and html views
33
+ - tree shaking
34
+ - code splitting
35
+ - lazy loading
36
+ - everything else webpack can do, like loading stylesheets, etc.
37
+
38
+ ### Requirements
39
+ - npm or yarn
40
+ - opal-webpack-loader consists of 2 parts, the npm package and the gem, both are required and must be the same version.
41
+ - webpack ^4.46
42
+ - webpack-dev-server ^3.11.0
43
+ - the ES6 modules branch of opal
44
+
45
+ - [PR#2266](https://github.com/opal/opal/pull/2266),
46
+ based on Opal 1.2.0 using javascript string primitives and providing nice features like `require_lazy 'my_module'`
47
+
48
+ `gem 'opal', github: 'janbiedermann/opal', branch: 'es6_modules_1_2'`
49
+
50
+ - if you have the webpacker gem installed somewhere, it should be a version supporting webpack 4
51
+ - ruby, version 2.5 or higher recommended
52
+ - bundler, latest version recommended
53
+
54
+ ### Installation
55
+
56
+ #### Using the installer
57
+ First install the gem:
58
+ ```
59
+ gem install 'opal-webpack-loader'
60
+ ```
61
+
62
+ Continue here:
63
+ - [Install for Rails like projects](https://github.com/isomorfeus/opal-webpack-loader/blob/master/docs/installation_rails.md)
64
+ - [Install for Cuba, Roda, Sinatra and other projects with a flat structure](https://github.com/isomorfeus/opal-webpack-loader/blob/master/docs/installation_flat.md)
65
+ - [Manual Installation](https://github.com/isomorfeus/opal-webpack-loader/blob/master/docs/installation_manual.md)
66
+
67
+ ### Example applications
68
+ - [Are here](https://github.com/isomorfeus/opal-webpack-loader/tree/master/example_apps/)
69
+ - A minimal webpack only example from @sunrick is [here](https://github.com/sunrick/opal-hello-world-webpack).
70
+
71
+ ### General Usage without Webpacker
72
+
73
+ After installing owl with the installer, three scripts are provided in package.json:
74
+ - `development` - runs the webpack-dev-server, use for general development, provides fast reloads, entry is application.js
75
+ - `debug` - runs the webpack-dev-server, use for debugging, provides source maps, entry is application_debug.js. Additional debugging tools may be added there.
76
+ - `production_build` - runs webpack to build assets for production, entry is application.js
77
+
78
+ These scripts can for example be run with:
79
+ `yarn run debug` or `npm run debug`
80
+
81
+ The default config provides several targets and entries:
82
+
83
+ - **Browser**: the webpack target is 'web' and the javascript entry file for imports is `application.js` - general use for the application with all
84
+ browser features, the opal ruby entry file is `opal_loader.rb` in the opal or app/opal directory of the app.
85
+ - **Server Side Rendering**: the webpack target is `node` and the javascript entry file for imports is `application_ssr.js` - general use for the
86
+ application server side rendering, several Browser features are unavailable, no `window`, no `document`, some node features are available,
87
+ like `Buffer`, the opal ruby entry file is `opal_loader.rb` in the opal or app/opal directory of the app.
88
+ (meant to be used with isomorfeus-speednode, standard ExecJS limitations prevent certain webpack features)
89
+ - **Web Worker**: the webpack target is 'webworker' and the javascript entry file for imports is `application_webworker.js` - used to initialize Web
90
+ Workers in the browser, the opal ruby entry file is `opal_webworker_loader.rb` in the opal or app/opal directory of the app.
91
+
92
+ Only the browser target is build by default. To builds the other target, just add the needed targets to the last line of the webpack config,
93
+ for example to `development.js`:
94
+ default config:
95
+ ```javascript
96
+ module.exports = [ browser ];
97
+ ```
98
+ modified config with ssr and web_worker targets enabled:
99
+ ```javascript
100
+ module.exports = [ browser, ssr, web_worker ];
101
+ ```
102
+ Same works for the `debug.js` and `production.js` webpack config files.
103
+
104
+ Also a Procfile has been installed, for rails its easy to startup rails and webpack with foreman:
105
+ `foreman start` (`gem install foreman` if you dont have it already). It will start rails and webpack-dev-server with the development script.
106
+
107
+ For non rails installation check the Procfile and add a starter for your app.
108
+
109
+ #### Opal Ruby Application Files
110
+ For rails installations with the installer they all go into: `app/opal`, for flat installations in the `opal` directory.
111
+ In this directory there already is a `opal_loader.rb` which is the entry point for your app.
112
+
113
+ #### Stylesheets
114
+ Stylesheets are hot reloaded too with the default config installed by the installer. Also they are imported into application.js by default.
115
+ For rails like applications stylesheets are in `app/assets/stylesheets/application.css`, for flat applications they are in `styles/application.css`.
116
+ SCSS is supported too by the default config.
117
+
118
+ #### Views
119
+ For rails like applications a watcher for `app/views` is installed by default. The watcher will trigger a page reload when views are changed.
120
+ For flat applications nothing is configured by default, as there are to many ways to generate views, they are not even needed with
121
+ frameworks like isomorfeus. Instead the section for configuring a view watcher is included in the development.js and debug.js webpack
122
+ config, but it is commented out. Please see those files and adjust to your liking.
123
+
124
+ #### Parallel compilation for speed
125
+
126
+ Since version 0.8.0 the number of CPUs is automatically determined and a appropriate number of of compile server workers is started automatically.
127
+
128
+ ### Source Maps
129
+
130
+ [Source Maps](https://github.com/isomorfeus/opal-webpack-loader/blob/master/docs/source_maps.md)
131
+
132
+ ### Hot Module Reloading
133
+ [Hot Module Reloading](https://github.com/isomorfeus/opal-webpack-loader/blob/master/docs/hot_module_reloading.md)
134
+
135
+ ### Opal Load Path
136
+ The projects directory for opal ruby files must be in the opal load path. This is done in the initializer for rails apps in
137
+ config/initializers/opal_webpack_loader.rb or in 'owl_init.rb' for non rails apps, for example:
138
+ ```ruby
139
+ Opal.append_path(File.realdirpath('app/opal'))
140
+ ```
141
+
142
+ ### View Helper
143
+ In Rails or frameworks that support `javscript_include_tag`, add to the app/helpers/application_helper.rb
144
+ ```ruby
145
+ module ApplicationHelper
146
+ include OpalWebpackLoader::RailsViewHelper
147
+ ```
148
+ in other frameworks that dont have a `javascript_include_tag`:
149
+ ```ruby
150
+ module MyProjectsViewThings
151
+ include OpalWebpackLoader::ViewHelper
152
+ ```
153
+
154
+ Then you can use in your views:
155
+ ```ruby
156
+ owl_script_tag('application.js')
157
+ ```
158
+ #### Compile Server and app_loader.rb
159
+ For non rails projects, determining Opal load paths, for the resolver and compile server to work properly, may not be obvious. For these cases
160
+ a file `app_loader.rb` in the projects root can be created which just loads all requirements without starting anything.
161
+ Usually it would just setup bundler with the appropriate options, for example:
162
+ ```ruby
163
+ require 'bundler/setup'
164
+ if ENV['RACK_ENV'] && ENV['RACK_ENV'] == 'test'
165
+ Bundler.require(:default, :test)
166
+ elsif ENV['RACK_ENV'] && ENV['RACK_ENV'] == 'production'
167
+ Bundler.require(:default, :production)
168
+ else
169
+ Bundler.require(:default, :development)
170
+ end
171
+ Opal.append_path(File.realdirpath('opal')) # this is a good place to add the directory with opal files to the opal load path
172
+ ```
173
+ When this file exists, the compile server will load it and generate Opal load paths accordingly for the resolver.
174
+
175
+ #### Project configuration options for the view helper
176
+ These setting are in the initializer in config/initializers/opal_webpack_loader.rb for rails like apps, or owl_init.rb for others.
177
+ ```ruby
178
+ OpalWebpackLoader.use_manifest = false
179
+ ```
180
+ If the manifest file should be used, use_manifest should be true.
181
+ ```ruby
182
+ OpalWebpackLoader.manifest_path = File.join(Dir.getwd, 'public', 'assets', 'manifest.json')
183
+ ```
184
+ Sets the path to the webpack (with the [webpack-manifest-plugin](https://www.npmjs.com/package/webpack-manifest-plugin)) generated manifest.json to look up assets.
185
+ ```ruby
186
+ OpalWebpackLoader.client_asset_path = 'http://localhost:3035/assets/'
187
+ ```
188
+ The path to prepend to the assets as configured in the webpack config 'publicPath'.
189
+ In the config example below its `publicPath: 'http://localhost:3025/assets'` so
190
+ client_asset_path should be set to the same.
191
+
192
+ For **production** use with readily precompiled and compressed assets which contain a fingerprint in the name (webpacks [chunkhash]),
193
+ and if the path in the manifest is the full path to the asset as configured in webpack,
194
+ these settings would work:
195
+ ```ruby
196
+ OpalWebpackLoader.use_manifest = true
197
+ OpalWebpackLoader.manifest_path = File.join(Dir.getwd, 'public', 'assets', 'manifest.json')
198
+ OpalWebpackLoader.client_asset_path = ''
199
+ ```
200
+
201
+ For **development** use with webpack-dev-server, with no manifest, these settings would work:
202
+ ```ruby
203
+ OpalWebpackLoader.use_manifest = false
204
+ OpalWebpackLoader.manifest_path = File.join(Dir.getwd, 'public', 'assets', 'manifest.json') # doesn't matter, not used
205
+ OpalWebpackLoader.client_asset_path = 'http://localhost:3035/assets/'
206
+ ```
207
+ ### Advanced Options
208
+ [Advanced Options](https://github.com/isomorfeus/opal-webpack-loader/blob/master/docs/advanced_options.md)
209
+ ### Tests
210
+ - clone the repo
211
+ - `bundle install`
212
+ - `bundle exec rspec`
@@ -1,7 +1,6 @@
1
1
  #!/usr/bin/env ruby
2
2
  require 'digest'
3
3
  require 'oj'
4
- require 'c_lexer'
5
4
  require 'optparse'
6
5
  require 'opal/paths'
7
6
  require 'opal/source_map'
@@ -1,7 +1,6 @@
1
1
  #!/usr/bin/env ruby
2
2
  require 'digest'
3
3
  require 'oj'
4
- require 'c_lexer'
5
4
  require 'optparse'
6
5
  require 'opal/paths'
7
6
  require 'opal/source_map'
@@ -64,6 +63,10 @@ modules_to_require.each do |mod|
64
63
  require mod
65
64
  end
66
65
 
66
+ def compiler_options_digest(compiler_options)
67
+ @compiler_options_digest ||= Digest::SHA1.hexdigest(Oj.dump(compiler_options, mode: :strict))
68
+ end
69
+
67
70
  def compile(request, cache, compiler_options)
68
71
  begin
69
72
  request_json = Oj.load(request.chop!, mode: :strict)
@@ -73,7 +76,7 @@ def compile(request, cache, compiler_options)
73
76
  source = File.read(filename)
74
77
  if cache
75
78
  source_digest = Digest::SHA1.hexdigest(source)
76
- key = "owl_#{compiler_options_digest}_#{source_digest}_#{compile_source_map}"
79
+ key = "owl_#{compiler_options_digest(compiler_options)}_#{source_digest}_#{compile_source_map}"
77
80
  result_json = cache.get(key)
78
81
  return result_json if result_json
79
82
  end
@@ -95,6 +98,7 @@ end
95
98
  if ARGV[0] == 'start'
96
99
  number_of_instances = ARGV[1].to_i
97
100
  number_of_instances == 4 if number_of_instances == 0
101
+ number_of_instances == 16 if number_of_instances > 16
98
102
  else
99
103
  raise 'arguments must be either "stop" or "start number_of_instances"'
100
104
  exit(1)
@@ -112,8 +116,7 @@ begin
112
116
  STDERR.puts "Exiting with drama."
113
117
  exit(0)
114
118
  else
115
- result = compile(request, cache, compiler_options)
116
- result
119
+ compile(request, cache, compiler_options)
117
120
  end
118
121
  end
119
122
  end.run