Capybara and webpacker problem · Issue #301 · rails/webpackerYou signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session. Dismiss alert
Release v3.5.0 · webpack/webpack
Features: add stats.excludeAssets to allow to filter assets in list (@ldrick) add import(/* webpackMode: "weak" */ "module") to try to load a module without network request (@faceyspacey) add 4. argument to require.context which is the context mode. Can be false, "eager", "lazy-once", "weak" and "async-weak". (@faceyspacey) require.resolveWeak now support expressions (@faceyspacey) generate only a
webpack/examples/pure-module at feature/pure-module · webpack/webpack · GitHub
README.md This example features the pure-module flag. The example contains a assumingly big library named big-module . This library is splitted into multiple child modules a , b and c . The exports from these modules are reexported in the entry ( index.js ) of the library. A consumer uses some of the exports by importing them from the library via import { a, b } from "big-module" . In this case ac
Release v3.4.0 · webpack/webpack
Features: Improved optimization bailout messages NamedModulesPlugins and HashedModuleIdsPlugin work now properly with delegated modules (DllReferencePlugin) and externals. add --config-name option to choose a config by name for compiling a part of the config Improved error message when parsing in ModuleConcatenationPlugin fails Upgrade a lot of dependencies Child compilation names are not relative
Node API - supporting of reading entry from memory · Issue #4440 · webpack/webpack
Do you want to request a feature or report a bug? Feature request What is the current behavior? In webpack config entry accepts only a disk path to an entry. What is the expected behavior? It would be nice, If entry also accepts a file from memory stream. I'm creating a webpack dynamic bundler as a service using webpack node api. I created the following very simple node code that allows me to retu
Running the server does not compile files or reload page in windows. · Issue #155 · webpack/webpack-dev-server
From the docs it says: It binds a small express server on localhost:8080 which serves your static assets as well as the bundle (compiled automatically). It automatically updates the browser page when a bundle is recompiled (socket.io). Open http://localhost:8080/webpack-dev-server/bundle in your browser. However if I run it this doesn't happen: I just get the following, but when I go to the servin
Process out of memory - Webpack · Issue #1914 · webpack/webpack
<--- Last few GCs ---> 9223585 ms: Scavenge 1390.0 (1454.7) -> 1390.0 (1454.7) MB, 9.0 / 0 ms (+ 0.7 ms in 1 steps since last GC) [allocation failure] [incremental marking delaying mark-sweep]. 9224727 ms: Mark-sweep 1390.0 (1454.7) -> 1388.3 (1452.7) MB, 1142.7 / 0 ms (+ 9.8 ms in 89 steps since start of marking, biggest step 2.5 ms) [last resort gc]. 9225694 ms: Mark-sweep 1388.3 (1452.7) -> 138
Webpack client does not throw error code when build failed · Issue #708 · webpack/webpack
Hi, I'd like to know when a build failed using the webpack client (because of a module not found for example). Right now, it seems that the client is outputting the error to the console but the status code of the webpack client process is 0 (success). Is it the normal behavior? I can imagine that when using the watch option we don't want the process to end on a build failure but without the option
Webpack 3 RC ModuleConcatenationPlugin crash, out of memory · Issue #5089 · webpack/webpack
Do you want to request a feature or report a bug? Bug What is the current behavior? Webpack crashes trying to build our application when using Webpack.optimize.ModuleConcatenationPlugin(). Also note up until the crash the build time is also showing a >60% increase in regards to build time with this plugin. If the current behavior is a bug, please provide the steps to reproduce. Building a large ap
Release v3.0.0 · webpack/webpack
Changes from 2.6.1 to 3.0.0 Features node_modules no longer mangle to ~ in stats [breaking change] timeout for HMR requests is configurable added experimental Scope Hoisting (webpack.optimize.ModuleConcatenationPlugin) some performance improvements added output.libraryExport to select an export for the library sourceMapFilename now supports [contenthash] [breaking change] module.noParse supports f
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く
s3-plugin-webpack/README.md at master · MikaAK/s3-plugin-webpack
webpack/examples/dll-app-and-vendor at main · webpack/webpack
difference between require and import ? · Issue #1973 · webpack/webpack
Release v3.0.0 · webpack-contrib/extract-text-webpack-plugin
Unable to HMR (Hot Module Replacement) css/scss with Webpack 2.2.0 and webpack-dev-server 2.2.1 · Issue #384 · webpack-contrib/extract-text-webpack-plugin
Release v3.1.0 · webpack/webpack
GitHub - webpack-contrib/babel-minify-webpack-plugin: [DEPRECATED] Babel Minify Webpack Plugin![GitHub - webpack-contrib/babel-minify-webpack-plugin: [DEPRECATED] Babel Minify Webpack Plugin](https://cdn-ak-scissors.b.st-hatena.com/image/square/2388c337f5bc0b4968774a1f280d5533dc78e45b/height=288;version=1;width=512/https%3A%2F%2Fopengraph.githubassets.com%2Fc12bf377dca64add9ae62c7b67c9327d66d63214c343f859f96bd5ab26346a2e%2Fwebpack-contrib%2Fbabel-minify-webpack-plugin)
Large resolve.extensions make build process slower significantly · Issue #5205 · webpack/webpack
Update to webpack 3 by lencioni · Pull Request #946 · webpack/webpack-dev-server
UglifyJsPlugin does not work with node5 babel preset · Issue #2836 · webpack/webpack
