Seems Webpack watch doesn&#39;t work if the file is not saved directly. Please try turning &#39;`Safe write`&#39; option ( `Settings | Appearance &amp; Behavior | System Settings | Use &quot;safe write&quot; (save changes to temporary file first)`) off.

In 2020.* the option name is `Back up files before saving`

Also make sure you use Node&#39;s path construction instead of slashes. Example:

    entry: {
         &#39;MyPackage&#39;: path.join(__dirname, &#39;modules&#39;, &#39;PkgEntry.js&#39;),
    ...

instead of:

    entry: {
         &#39;MyPackage&#39;: &#39;\\modules\\PkgEntry.js&#39;),
    ...



Had the same issue today. And accepted answer didn&#39;t help me.

Check this page https://confluence.jetbrains.com/display/IDEADEV/Inotify+Watches+Limit and try to increase your **Inotify Watches Limit**. Helped me.



I want to write an asynchronous method that returns a [`CompletableFuture`][1]. The only purpose of the future is to track when the method is complete, not its result. Would it be better to return `CompletableFuture&lt;Void&gt;` or `CompletableFuture&lt;?&gt;`? Is there a reason to prefer one or the other, or are they interchangeable?

* [`CompletableFuture`][1] itself returns `CompletableFuture&lt;Void&gt;` from many of its methods.
* `java.nio` has a `Future&lt;Void&gt;` in [`AsynchronousSocketChannel`][4]: `Future&lt;Void&gt; connect(SocketAddress remote)`.
* On the other hand, `java.util.concurrent` classes like [`ExecutorService`][2] and [`ScheduledExecutorService`][3] return `Future&lt;?&gt;`: for instance, with `Future&lt;?&gt; submit(Runnable task)`.

Note that I&#39;m only asking about return types, not parameter lists, variable declarations, or other contexts.

[1]: http://docs.oracle.com/javase/8/docs/api/java/util/concurrent/CompletableFuture.html
[2]: http://docs.oracle.com/javase/8/docs/api/java/util/concurrent/ExecutorService.html
[3]: http://docs.oracle.com/javase/8/docs/api/java/util/concurrent/ScheduledExecutorService.html
[4]: http://docs.oracle.com/javase/8/docs/api/java/nio/channels/AsynchronousSocketChannel.html

Return CompletableFuture&lt;Void&gt; or CompletableFuture&lt;?&gt;?

I recently started using ES6&#39;s [destructuring](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Operators/Destructuring_assignment) assignment syntax and started to get familiar with the concept. I was wondering if it&#39;s possible to extract a nested property using the same syntax. 

For example, let&#39;s say I have the following code:

    let cagingIt = {
      foo: {
        bar: &#39;Nick Cage&#39;
      }
    };

I know I am able to access extract `foo` into a variable by doing:

    // where foo = { bar: &quot;Nick Cage&quot; }
    let { foo } = cagingIt;


However, is it possible to extract a deeply nested property, like `bar`. Perhaps something like this:

    // where bar = &quot;Nick Cage&quot;
    let { foo[bar] } = cagingIt;

I&#39;ve tried finding documentation on the matter but to no avail. Any help would be greatly appreciated. Thank you!
 

Destructuring deep properties

So basically I have a project using Webpack, if I build using `Webpack -w`, editing the file with another editor will trigger the watch; however if I edit the file using Webstorm, nothing will happen. 

I have came across this [post][1], which seems I&#39;m not the only one, however that solution is for Ubuntu, so I was wondering if there is anything similar for Windows?

Thanks


  [1]: https://devnet.jetbrains.com/thread/466233;jsessionid=4E17E9ABA28D55378CDB8A43F53A8511

Webpack watch not working on Webstorm on Windows?

So basically I have a project using Webpack, if I build using <code>Webpack -w</code>, editing the file with another editor will trigger the watch; however if I edit the file using Webstorm, nothing will happen.
I have came across this <a href="https://devnet.jetbrains.com/thread/466233;jsessionid=4E17E9ABA28D55378CDB8A43F53A8511" target="_blank" rel="noopener noreferrer">post</a>, which seems I'm not the only one, however that solution is for Ubuntu, so I was wondering if there is anything similar for Windows?
Thanks

The IDE being used is WebStorm 11.0.3, the tslint is configured and works, but, it hangs because it tries to parse large *.d.ts library files. 

Is there a way to ignore a particular file or directory?

How to ignore a particular directory or file for tslint?

I use webpack path aliases for ES6 module loading. 

_E.g._ If I define an alias for `utils` instead of something like  
`import Foo from &quot;../../../utils/foo&quot;`, I can do  
`import Foo from &quot;utils/foo&quot;`

The problem is that once I start using aliases, WebStorm looses track of the import and I&#39;m left with warnings and no auto-completion.

Is there a way to instruct WebStorm to use such aliases?

Path aliases for imports in WebStorm

When I push `cmd + alt + l` Webstorm doing some reformating to beautify my JavaScript sources. Ho to make Webstorm automatically change double quotes to single quotes in my sources?

How to make Webstorm &quot;Reformatting Source Code&quot; to change double quotes to single quotes?

I&#39;m trying to run a piece of JavaScript code written in a tutorial that looks like this:

**main.js**

    import Vue from &#39;Vue&#39;;
    import Alert from &#39;./components/Alert.vue&#39;;
    
    new Vue({
        el: &#39;body&#39;,
    
        components: { Alert }
    })

However, PhpStorm is giving the following error:  

&gt; Import declarations are not supported by current JavaScript version

How I can get a newer(?) JavaScript version in PhpStorm? Is that really the problem here?

Import not working with JavaScript in PhpStorm/Webstorm

I am trying to use new tools available for coding in JavaScript. I&#39;ve seen the post https://stackoverflow.com/questions/35772101/phpstorm-let-definition-are-not-supported-by-current-javascript-version. I&#39;ve tried as suggested over there, but do not work.

When I hover over the `export`

&gt; Export declarations are not supported by current JavaScript version

When I hover over the `yield`

&gt; Generators are not supported by current JavaScript version

and hovering over the `let`

&gt; Let definition are not supported by current JavaScript version

So the question is how to upgrade the JavaScript version?

WebStorm “Let definition are not supported by current JavaScript version”

I&#39;m writing a web app using `react` and `webpack` as my module bundler.
My `jsx` code is really light so far, the size of the entire folder is 25 kb.

My `bundle.js` created from `webpack` is 2.2 mb though. After running the optimization with the `-p` flag, it reduces the bundle to 700kb, which is still extremely big.

I have looked into the `react.min.js` file and its size is 130kb.

Is it possible that the webpack produces such big files or am I doing something wrong?

webpack.config.js

    var path = require(&#39;path&#39;);
    var webpack = require(&#39;webpack&#39;);

    module.exports = {
      entry: &#39;./public/components/main.jsx&#39;,
      output: {
        path: __dirname + &quot;/public&quot;,
        filename: &#39;bundle.js&#39;
      },
      module: {
        loaders: [{
          test: /.jsx?$/,
          loader: &#39;babel-loader&#39;,
          exclude: /node_modules/,
          query: {
            presets: [&#39;es2015&#39;, &#39;react&#39;]
          }
        }, {
          test: /\.css$/,
          loader: &quot;style!css&quot;
        }]
      }
    };

**EDIT**

package.json: 

    {
      &quot;name&quot;: &quot;XChange&quot;,
      &quot;version&quot;: &quot;0.0.0&quot;,
      &quot;private&quot;: true,
      &quot;scripts&quot;: {
        &quot;start&quot;: &quot;node ./bin/www&quot;
      },
      &quot;main&quot;: &quot;./bin/www&quot;,
      &quot;devDependencies&quot;: {
        &quot;body-parser&quot;: &quot;~1.13.2&quot;,
        &quot;cookie-parser&quot;: &quot;~1.3.5&quot;,
        &quot;debug&quot;: &quot;~2.2.0&quot;,
        &quot;express&quot;: &quot;~4.13.1&quot;,
        &quot;jade&quot;: &quot;~1.11.0&quot;,
        &quot;morgan&quot;: &quot;~1.6.1&quot;,
        &quot;serve-favicon&quot;: &quot;~2.3.0&quot;,
        &quot;react-dom&quot;: &quot;~0.14.3&quot;,
        &quot;react&quot;: &quot;~0.14.3&quot;,
        &quot;webpack&quot;: &quot;~1.12.9&quot;,
        &quot;babel-loader&quot;: &quot;~6.2.0&quot;,
        &quot;babel-core&quot;: &quot;~6.2.1&quot;,
        &quot;babel-preset-react&quot;: &quot;~6.1.18&quot;,
        &quot;babel-preset-es2015&quot;: &quot;~6.1.18&quot;,
        &quot;react-bootstrap&quot;: &quot;~0.28.1&quot;,
        &quot;material-ui&quot;: &quot;~0.14.0-rc1&quot;,
        &quot;history&quot;: &quot;~1.13.1&quot;,
        &quot;react-router&quot;: &quot;~1.0.2&quot;,
        &quot;style-loader&quot;: &quot;~0.13.0&quot;,
        &quot;css-loader&quot;: &quot;~0.18.0&quot;
      },
      &quot;dependencies&quot;: {
        &quot;express-validator&quot;: &quot;~2.18.0&quot;,
        &quot;mongoose&quot;: &quot;~4.2.9&quot;,
        &quot;kerberos&quot;: &quot;~0.0.17&quot;,
    	&quot;bcrypt&quot;: &quot;~0.8.5&quot;
      }
    }


How to minimize the size of webpack&#39;s bundle?

I am wondering how to set up an inline svg with webpack? 

I am following the [react-webpack-cookbook](https://github.com/christianalfoni/react-webpack-cookbook/wiki/Loading-SVG). 

I have my **webpack.config** set up correctly with the **file loader**. 

However the example shows using a background image like this: 

    .icon {
       background-image: url(./logo.svg);
    }

which works fine, but I want to have an inline svg image how do I do this to include my **logo.svg** inline in my react component?

    import React, { Component } from &#39;react&#39;
    
    class Header extends Component {
    
      render() {
        return (
      		&lt;div className=&#39;header&#39;&gt;
                &lt;img src={&#39;./logo.svg&#39;} /&gt;
      		&lt;/div&gt;
        );
      }
    };
    
    export default Header



how to set up an inline svg with webpack

Suppose that I have class like this (written in typescript) and I bundle it with webpack into `bundle.js`.

    export class EntryPoint {
        static run() {
            ...
        }
    }

In my index.html I will include the bundle, but then I would also like to call that static method.

    &lt;script src=&quot;build/bundle.js&quot;&gt;&lt;/script&gt;
    &lt;script&gt;
        window.onload = function() {
            EntryPoint.run();
        }
    &lt;/script&gt;

However, the `EntryPoint` is undefined in this case. How would I call the bundled javascript from another script then?

**Added**: [Webpack config file][1].


  [1]: http://pastebin.com/ty3BKhUn

Calling webpacked code from outside (HTML script tag)

I am using webpack and the HtmlWebpackPlugin to inject bundled js and css into an html template file.

    new HtmlWebpackPlugin({
       template: &#39;client/index.tpl.html&#39;,
       inject: &#39;body&#39;,
       filename: &#39;index.html&#39;
    }),

And it produces the following html file.

    &lt;!doctype html&gt;
    &lt;html lang=&quot;en&quot;&gt;
      &lt;head&gt;
        ...
        &lt;link href=&quot;main-295c5189923694ec44ac.min.css&quot; rel=&quot;stylesheet&quot;&gt;
      &lt;/head&gt;
      &lt;body&gt;
        &lt;div id=&quot;app&quot;&gt;&lt;/div&gt;
        &lt;script src=&quot;main-295c5189923694ec44ac.min.js&quot;&gt;&lt;/script&gt;
      &lt;/body&gt;
    &lt;/html&gt;


This works fine when visiting the root of the app `localhost:3000/`, but fails when I try to visit the app from another URL, for example, `localhost:3000/items/1` because the bundled files are not injected with an absolute path. When the html file is loaded, it will look for the js file inside the non-exist `/items` directory because react-router hasn&#39;t loaded yet.

How can I get HtmlWebpackPlugin to inject the files with an absolute path, so express will look for them at the root of my `/dist` directory and not at `/dist/items/main-...min.js`? Or maybe I can change my express server to work around the issue?

    app.use(express.static(__dirname + &#39;/../dist&#39;));

    app.get(&#39;*&#39;, function response(req, res) {
      res.sendFile(path.join(__dirname, &#39;../dist/index.html&#39;));
    });

Essentially, I just need to get the line:

    &lt;script src=&quot;main...js&quot;&gt;&lt;/script&gt;

to have a slash at the start of the source.

    &lt;script src=&quot;/main...js&gt;&lt;/script&gt;



HtmlWebpackPlugin injects relative path files which breaks when loading non-root website paths

As I write webpack.config.js like this 

    module.exports = {
      entry: &#39;./index.jsx&#39;,
      output: {
        filename: &#39;bundle.js&#39;
      },
      module: {
        loaders: [{
          test: /\.jsx?$/,
          exclude: /node_modules/,
          loader: &#39;babel&#39;,
          query: {
            presets: [&#39;es2015&#39;, &#39;react&#39;]
          }
        }]
      }
    };

And in `index.jsx` I import a `react` module `App`

    import React from &#39;react&#39;;
    import { render } from &#39;react-dom&#39;;
    
    import App from &#39;./containers/App&#39;;
    
    let rootElement = document.getElementById(&#39;box&#39;)
    render(
      &lt;App /&gt;,
      rootElement
    )

I find if I named module app in `App.jsx`, then webpack will say in `index.jsx` can&#39;t find module `App`, but if I named named module app in `App.js`, it will find this module and work well.

So, I&#39;m confuse about it. In my `webpack.config.js`, I have writed `test: /\.jsx?$/` to check file, but why named `*.jsx` can&#39;t be found?

[![enter image description here][1]][1]


  [1]: http://i.stack.imgur.com/cRtyD.png

webpack can&#39;t find module if file named jsx

Since I&#39;ve updated my version of intelliJ (14.x to 15.x) it has started automatically collapsing single line methods in the `Java` editor:

Previous version:

    public void setContext(SecurityContext context) {
        this.context = context;
    }

Latest version:

    public void setContext(SecurityContext context) { this.context = context; }

Is there a way to prevent this?  I find the original version much easier on the eyes!

Thanks.

IntelliJ collapsing single line methods

In **IntelliJ IDEA**, is there an option to find and replace a symbol for whole project with on time operation?

Find and Replace symbol for whole project intellij?

I run webpack-dev-server from the root folder of my project.
I have *assets* folder in */src/assets* that is copied by CopyWebPackPlugin:

    new CopyWebpackPlugin([ { from: &#39;src/assets&#39;, to: &#39;assets&#39; } ])

If I put *logo.png* inside assets folder then After running webpack-dev-server I can&#39;t access *http://localhost/assets/logo.png* file, but can access *http://localhost/src/assets/logo.png* file. However if I run in production mode the situation turns upside down.

How to configure webpack server to make *http://localhost/assets/logo.png* file accessible in development mode?

Serving static assets in webpack dev server

I am very new to webpack, I found that in production build we can able to reduce the size of overall code.
Currently webpack builds around 8MB files and main.js around 5MB.
How to reduce the size of code in production build?
I found a sample webpack configurtion file from internet and I configured for my application and I run `npm run build` and its started building and it generated some files in `./dist/` directory.

 1. Still these files are heavy(same as development version)
 2. How to use these files? Currently I am using webpack-dev-server to
    run the application.

package.json file

    {
      &quot;name&quot;: &quot;MyAPP&quot;,
      &quot;version&quot;: &quot;0.1.0&quot;,
      &quot;description&quot;: &quot;&quot;,
      &quot;main&quot;: &quot;src/server/server.js&quot;,
      &quot;repository&quot;: {
        &quot;type&quot;: &quot;git&quot;,
        &quot;url&quot;: &quot;&quot;
      },
      &quot;keywords&quot;: [
      ],
      &quot;author&quot;: &quot;Iam&quot;,
      &quot;license&quot;: &quot;MIT&quot;,
      &quot;homepage&quot;: &quot;http://example.com&quot;,
      &quot;scripts&quot;: {
        &quot;test&quot;: &quot;&quot;,
        &quot;start&quot;: &quot;babel-node src/server/bin/server&quot;,
        &quot;build&quot;: &quot;rimraf dist &amp;&amp; NODE_ENV=production webpack --config ./webpack.production.config.js --progress --profile --colors&quot;
      },
      &quot;dependencies&quot;: {
        &quot;scripts&quot; : &quot;&quot;, ...
      },
      &quot;devDependencies&quot;: {
        &quot;scripts&quot; : &quot;&quot;, ...
      }
    }


webpack.config.js


    var path = require(&#39;path&#39;);
    var webpack = require(&#39;webpack&#39;);
    var HtmlWebpackPlugin = require(&#39;html-webpack-plugin&#39;);
    var public_dir = &quot;src/frontend&quot;;
    var ModernizrWebpackPlugin = require(&#39;modernizr-webpack-plugin&#39;);
    
    module.exports = {
      devtool: &#39;eval-source-map&#39;,
      entry: [
        &#39;webpack-hot-middleware/client?reload=true&#39;,
        path.join(__dirname, public_dir , &#39;main.js&#39;)
      ],
      output: {
        path: path.join(__dirname, &#39;/dist/&#39;),
        filename: &#39;[name].js&#39;,
        publicPath: &#39;/&#39;
      },
      plugins: [
        plugins
      ],
      module: {
        loaders: [loaders]
      }
    };


webpack.production.config.js

    var path = require(&#39;path&#39;);
    var webpack = require(&#39;webpack&#39;);
    var HtmlWebpackPlugin = require(&#39;html-webpack-plugin&#39;);
    var public_dir = &quot;src/frontend&quot;;
    var ModernizrWebpackPlugin = require(&#39;modernizr-webpack-plugin&#39;);
    console.log(path.join(__dirname, &#39;src/frontend&#39; , &#39;index.html&#39;));
    
    module.exports = {
      devtool: &#39;eval-source-map&#39;,
      entry: [
        &#39;webpack-hot-middleware/client?reload=true&#39;,
        path.join(__dirname, &#39;src/frontend&#39; , &#39;main.js&#39;)
      ],
      output: {
        path: path.join(__dirname, &#39;/dist/&#39;),
        filename: &#39;[name].js&#39;,
        publicPath: &#39;/&#39;
      },
      plugins: [plugins],
      resolve: {
        root: [path.resolve(&#39;./src/frontend/utils&#39;), path.resolve(&#39;./src/frontend&#39;)],
        extensions: [&#39;&#39;, &#39;.js&#39;, &#39;.css&#39;]
      },
    
      module: {
        loaders: [loaders]
      }
    };



Webpack how to build production code and how to use it

I&#39;m using webpack to run my react frontend successfully using the following config:

    {
        name: &#39;client&#39;,
        entry: &#39;./scripts/main.js&#39;,
        output: {
            path: __dirname,
            filename: &#39;bundle.js&#39;  
        },
        module: {
            loaders: [
                {
                    test: /.jsx?$/,
                    loader: &#39;babel-loader&#39;,
                    exclude: /node_modules/,
                    query:{
                        presets: [&#39;es2015&#39;, &#39;react&#39;, &#39;stage-2&#39;]
                    }
                }
            ]
        }
    }

I&#39;m trying to put up a node.js express backend as well, and would like to run that through webpack as well, so that I have a single server running both the backend and frontend, and because I want to use babel to  transpile my javascript.

I made a quick testserver looking like this:

    var express = require(&#39;express&#39;);
    console.log(&#39;test&#39;);

    var app = express();

    app.get(&#39;/&#39;, function(req, res){
        res.send(&quot;Hello world from Express!!&quot;);
    });

    app.listen(3000, function(){
        console.log(&#39;Example app listening on port 3000&#39;);
    });

If I run this with `node index.js` and open my browser on `localhost:3000` it prints &quot;Hello world from Express!!&quot;. So far so good. Then I tried creating a web-pack config for it:

    var fs = require(&#39;fs&#39;);
    var nodeModules = {};
    fs.readdirSync(&#39;node_modules&#39;)
        .filter(function(x) {
            return [&#39;.bin&#39;].indexOf(x) === -1;
        })
        .forEach(function(mod) {
            nodeModules[mod] = &#39;commonjs &#39; + mod;    
    });

    module.exports = [
    {
        name: &#39;server&#39;,
        target: &#39;node&#39;,
        entry: &#39;./index.js&#39;,
        output: {
            path: __dirname,
            filename: &#39;bundle.js&#39;
        },
        externals: nodeModules,
        module: {
            loaders: [
                { 
                    test: /\.js$/,
                    loaders: [
                        &#39;babel-loader&#39;
                    ]
                },
                {
                    test:  /\.json$/, 
                    loader: &#39;json-loader&#39;
                }
            ]
        }
    }   

When I run the command `webpack-dev-server` it starts up successfully (it seems). However, if I go to my browser on `localhost:3000` now, it just says that the webpage is not available, just as when the server is not running at all.

I&#39;m very new to both node and webpack, so either I have made a small mistake somewhere, or I&#39;m way off ;)

Running a node express server using webpack-dev-server

I&#39;m trying to use webpack-dev-server to compile files and start up a dev web server. 

In my `package.json` I have the script property set to:

    &quot;scripts&quot;: {
      &quot;dev&quot;: &quot;webpack-dev-server --hot --inline&quot;,
     }

So the `--hot` and `--inline` should enable the webserver and the hot reloading (as I understand it). 

In my `webpack.config.js` file I set the entry, output, and devServer settings as well as add a loader to look for changes in `.vue` files:

    module.exports = {
        entry: &#39;./src/index.js&#39;,
        output: {
            path: __dirname + &#39;/public&#39;,
            publicPath: &#39;/public&#39;,
            filename: &#39;bundle.js&#39;
        },
        devtool: &#39;source-map&#39;,
        devServer:{
            contentBase: __dirname + &#39;/public&#39;
        },
        module:{
            loaders:[
                { test: /\.vue$/, loader: &#39;vue&#39;}
            ]
        }
    };


So with this setup, I run `npm run dev`. The webpack-dev-server starts up, the module loader test works (i.e. when I save any .vue file it causes webpack to recompile), but:

- The browser never refreshes
- The compiled javascript that gets stored in memory is never made available to the browser

On that second bullet, I can see this because in the browser window the vue placeholders are never replaced and if I open up the javascript console the Vue instance is never created or made available globally. 

[![Gif of issue][1]][1]

What am I missing?

  [1]: http://i.stack.imgur.com/ByBH5.gif

Content Type	Original Author	Original Content on Stackoverflow
Question	luanped	View Question on Stackoverflow
Solution 1 - Webstorm	lena	View Answer on Stackoverflow
Solution 2 - Webstorm	bsandhu	View Answer on Stackoverflow
Solution 3 - Webstorm	Volod	View Answer on Stackoverflow

Webpack watch not working on Webstorm on Windows?

Webstorm Problem Overview

Webstorm Solutions

Solution 1 - Webstorm

Solution 2 - Webstorm

Solution 3 - Webstorm

Destructuring deep properties

Return CompletableFuture<Void> or CompletableFuture<?>?

Attributions