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
Release v3.1.0 · webpack/webpack
Features: Allow different library names for UMD Support for passing a defined identifier as this in a IIFE Use the new resolve performance option cacheWithContext: false by default when it's safe Support array of functions as configuration add sortModules to Chunk which is required in extract-text-plugin to support webpack 3 Bugfixes: ! with truthy webpack identifier will evaluate correctly assets
Leaving for Microsoft
This post is dedicated to my wife Mallory. Without her patience and support to allow me to pursue my endeavors, I would not be where I am today. ❤ Today, with a ginormous lump in my throat, I gave my current employer my 2 weeks notice, and informed them that I would be leaving Nebraska, to join Microsoft in Seattle, Washington. 😍 I will be joining the EdgeHTML team as a Program Manager for F12 De
🍾🚀 webpack 3: Official Release!! 🚀🍾
After we released webpack v2, we made some promises to the community. We promised that we would deliver the features you voted for. Moreover, we promised to deliver them in a faster, more stable release cycle. No more year-long betas, no breaking changes between release candidates. We promised to do you right by you, the community that makes webpack thrive. The webpack team is proud to announce th
Release v3.0.0-rc.0 · webpack/webpack
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 functions add node: false opt
Release v2.3.0 · webpack/webpack
Features: add extensions option to DllReferencePlugin add warningsFilter to UglifyJsPlugin to hide warnings selectively add extractComments to UglifyJsPlugin to move kept comments into separate file (i. e. LICENSE file) validate relative and absolute paths in configuration validate stats options allow to match on compiler (name in configuration) in rules i. e. allows to specify different rules for
🚀 webpack 2 and beyond 🚀
Today we’ve published webpack 2 to npm under the latest tag on npm! You can install it in your project using npm install webpack. 👀 Why Update? 👀The upgrade from webpack 1 to 2 comes with some very exciting features. 🙅 ES6 Support 🙅You no longer have to use babel to transpile import and export statements in your code. webpack now supports parsing of these statements. This allows us to leverag
🎉 webpack 2.2: The Final Release 🎉
Last month we shipped our first Release Candidate for webpack 2.2. Since then, we’ve been hard at work fixing any bugs that you reported. Not only that, but we’ve merged over 220 pull requests from the community in helping us refactor our core library to ES2015 (yes, this means our minimum supported NodeJS version is now 4.3). On behalf of the entire webpack team, I’m proud to announce that webpac
Release v2.2.0-rc.4 · webpack/webpack
Node.js dropped support for 0.12, so we do. Breaking changes: Using CommonJS or AMD export stuff in a ES2015 module will emit errors. Usablility: performance hints are off by default. It was too annoying, but you can still see the [big] flag by default. Bugfixes: webpack now exits with non-zero exit code when configuration Promise is rejected. Features: ProvidePlugin supports passing array to acce
webpack 2.2: The Release Candidate
The talks of webpack 2 started back in January of 2015. Since then we have published multiple versions from 2.0 to 2.1-beta.28. For awhile, things were moving slowly, and then as of June, we had formed a Core Team, conducted weekly meetings, published meeting notes, and completed our first milestone for our brand new documentation webpage. In addition, we secured our organization for the future th
Webpack 2 Tree Shaking Configuration
Tree Shaking, a modern dead code elimination algorithm for ECMAScript 2015+ is one of the most anticipated features in the upcoming Webpack 2. By eliminating unused ES6 exports, Webpack can further help the minification process to get your bundle much smaller than ever before. Tree shaking, ultimately, bundles only the modules you import into your scripts. Any exports that were not imported will n
VMware Tanzu Application Catalog (Applications Tutorials) Documentation
VMware Tanzu Application Catalog (Applications Tutorials) Documentation This section provides information about how to use OSS applications available via VMware Tanzu Application Catalog. Create Your First Helm Chart Best practices writing a Dockerfile Best Practices for Creating Production-Ready Helm charts Running non-root containers on Openshift Work With Non-Root Containers for Bitnami Applica
Getting Started with webpack – Insightful Software
Jun 2017 edit: 3 was just released! The syntax for 3.x is identical to 2.x, which means this article is still up-to-date (if I missed something, please comment!). The version bump was for more behind-the-scenes stuff, but it did add an easy-to-add “Scope Hoisting” plugin that can cut down on your bundle size that’s worth checking out! Jump to the bottom of this article for the “Upgrading to 3” sec
Webpack 2 Tree Shaking Configuration
Tree Shaking, a modern dead code elimination algorithm for ECMAScript 2015+ is one of the most anticipated features in Webpack 2. By eliminating unused ES6 exports, Webpack can further help the minification process to get your bundle much smaller than ever before. Update 11/14/2016: Webpack 2 sample application code has been updated to match the most recent updates in Webpack (v2.2), React (v15.4)
Browserify vs Webpack
In the land of JavaScript, no one is king for long. Just last year Grunt was effectively dethroned by Gulp. And now, just as Gulp and Browserify are finally reaching critical mass, Webpack threatens to unseat them both. Is there truly a compelling reason to change your front-end build process yet again? Let’s consider the merits of each approach. Browserify (and friends…)Browserify is conceptually
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く
Release v3.0.0-rc.1 · webpack/webpack
webpack 2.6.0 can't find variable: Promise on require async · Issue #4916 · webpack/webpack
Webpack 2: -p option does not set NODE_ENV to "production" in webpack config · Issue #2537 · webpack/webpack
GitHub - NekR/offline-plugin: Offline plugin (ServiceWorker, AppCache) for webpack (https://webpack.js.org/)
Webpack 2 by sokra · Pull Request #861 · webpack/webpack
