webpack-2

问题 I'm using webpack-html-plugin to generate a one-page static website. I'm trying to implement cache busting for the static assets, images especially. I also have a meta tag for an open graph image, which is listed bellow. My webpack.config.js looks something along the lines of this: module.exports = { entry: './src/init.js', output: { path: './build', filename: 'bundle.js', }, module: { loaders: [{ test: /\.js?$/, exclude: /node_modules/, loader: 'babel-loader' }, { test: /\.(jpe?g|png|gif|svg

问题 I want to reproduce this Gulp script with webpack to have only one process who listen on files but i can't make it work. This is my Gulp task gulp.task('scripts', function(){ return gulp.src( WATCH_SCRIPTS.SCRIPTS ) .pipe(plumber()) .pipe(sourcemaps.init()) .pipe(concat('plugins.min.js')) .pipe(babel({ compact: false, babelrc: false, presets: ['es2015-allow-top-level-this'] })) .pipe(ifElse(PROD_ENV, () => {return uglify({ hoist_vars: true, global_defs: { jQuery: false, $: false, } })}, () =>

问题 I am trying to implement a custom RxJS operator as described in this answer. Here are the relevant snippets in my application: rxjs-extensions.ts import { Observable } from 'rxjs/Observable'; function restrictToCommand<T>(this: Observable<T>): Observable<T> { console.log('works'); return Observable.empty() } declare module 'rxjs/Observable' { interface Observable<T> { restrictToCommand: typeof restrictToCommand; } } Observable.prototype.restrictToCommand = restrictToCommand; consumer.ts

问题 In trying to optimize the vendor bundle when building with webpack, I'm using the NgcWebpackPlugin. This is the vendor bundle visually presented: What surprises me is the presence of the angular compiler module even tho we are utilizing AOT. Do I need to somehow explicitly declare that I don't need the compiler in the bundle? Or am I missing something else? Here's the vendor.ts : import '@angular/platform-browser'; import '@angular/platform-browser-dynamic'; import '@angular/core'; import '

问题 I'm using the react/react-router/webpack stack with dynamic routing between my different pages of the app which means every page loads asynchronously by demand. Everything works great but when I deploy a new version, my current active users who didn't fetch all of the Js file of all the pages will get stuck once the'll try to navigate to another page they haven't visited yet. EXAMPLE lets say I have a code split app with the following .js generated files and md5 (for cache busting): main.123

问题 I am using webpack to create a *.js bundle var path = require('path'); var webpack = require('webpack'); const ExtractTextPlugin = require("extract-text-webpack-plugin"); module.exports = { entry: { site: [ './wwwroot/js/site.js', './node_modules/jquery/dist/jquery.js', './Scripts/jquery.global.js', './node_modules/jquery-validation/dist/jquery.validate.js', './node_modules/jquery-validation-unobtrusive/jquery.validate.unobtrusive.js', './node_modules/popper.js/dist/popper.js', './node

问题 After spending most of the day googling and trying - i did not get it to work and at this point i'm not sure what's missing. I already have jQuery working (and verified it works) in webpack.common.js: new ProvidePlugin({ jQuery: 'jquery', $: 'jquery', jquery: 'jquery' }) For example i have a "MetisMenu" plugin, where should i configure it? I tried various combinations of require/include in my app.module.ts. Like (including assigning them to a constant/var but import/require always give this

问题 My webpack.config.js looks as below : var debug = process.env.NODE_ENV !== "production"; var webpack = require('webpack'); var path = require('path'); var node_dir = __dirname + '/node_modules'; const autoprefixer = require('autoprefixer'); const ProvidePlugin = require('webpack/lib/ProvidePlugin'); module.exports = { context: path.join(__dirname, "src"), devtool: debug ? "inline-sourcemap" : null, entry: ['tether', 'font-awesome-loader',"bootstrap-loader","./js/client.js"], resolve: {

问题 I have an electron app that I'm building with webpack 2. I have a config file that I'm including like a normal webpack resource: config.js: export default { config1: 1, config2: 2 } main.js: import config from '../some/path/config'; console.log(config.config1); The config file code ends up in my bundle.js file as you would expect. The problem is that the point of config files is that you can change them after deployment. This set up requires me to re-webpackify everything if I want config

问题 I have installed node type definitions using the following command npm install --save-dev @types/node After that, when I try to import the node type definitions using the following statement import { Process } from '@types/node'; or import { Process } from 'node'; I get the following error [ts] File '<root_path>/node_modules/@types/node/index.d.ts' is not a module. I am sure there is something very basic that I am missing here but I cannot figure out. Few more things I am using Windows 8 I am