Skip to content

[WDS] Nothing changed. #850

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
aep opened this issue Mar 16, 2017 · 2 comments
Closed

[WDS] Nothing changed. #850

aep opened this issue Mar 16, 2017 · 2 comments

Comments

@aep
Copy link

aep commented Mar 16, 2017

const path = require('path');
module.exports = {
    devServer: {
        contentBase: path.join(__dirname, "dist")
    },
    entry: './src/app.js',
    output: {
        path:       path.join(__dirname, 'dist'),
        filename:   'bundle.js'
    }
};

app.js is empty.
When i now add random garbage to app.js (be it correct syntax or not), dev-server correctly spots the change and starts compiling, but apparantly not the file i just saved.

webpack: Compiling...
Hash: 5a194bf652a9d1f48771
Version: webpack 2.2.1
Time: 33ms
chunk    {0} bundle.js (main) 300 kB [entry]
   [36] ./src/app.js 60 bytes {0} [built]
     + 85 hidden modules
webpack: Compiled successfully.

the hash does not change, no matter what i put in app.js

and chrome dev console says:
[WDS] Nothing changed.

and manually GETing /bundle.js shows its still serving the old file.

However, when i just restart the server, the hash changes and the new content is used.

@SpaceK33z
Copy link
Member

This is a usage error, please ask on stackoverflow, you'll get better help there.

@shellscape
Copy link
Contributor

@theBull because most folks will benefit from learning how something works versus being fed answers. given the age of this issue, I'd also wager that keez can tell it's user error based on given input and output, but can't say specifically what it is given the limitation of info in the issue. Hashes are also an issue with webpack proper, rather than webpack-dev-server.

I'll add that it appears you stopped by just to drop a comment that had no real purpose other than to try to paint keez as a jerk. We don't welcome that here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants