Webpack not detecting CSS errors
up vote
0
down vote
favorite
I have a simple Webpack environment set up. The dev server and auto reload are all working fine for both CSS and JS files, however if I make a syntax error in my CSS, the console does not give me any error messages. also when I set overlay: true in my config, I get no notification of an error in the console or the site. Any help is appreciated.
webpack.dev.js
const path = require("path");
module.exports = {
entry: {
main: ["./src/main.js"]
},
mode: "development",
output: {
filename: "[name]-bundle.js",
path: path.resolve(__dirname, "../js"),
publicPath: "/js"
},
devServer: {
contentBase: "../tester",
overlay: true
},
module: {
rules: [
{
test: /.css$/,
use: [
{
loader: "style-loader"
},
{
loader: "css-loader"
}
]
}
]
}
};
webpack webpack-dev-server webpack-4 webpack-style-loader
asked Nov 21 at 14:06
Dmitriy
316112
add a comment |
up vote
0
down vote
favorite
I have a simple Webpack environment set up. The dev server and auto reload are all working fine for both CSS and JS files, however if I make a syntax error in my CSS, the console does not give me any error messages. also when I set overlay: true in my config, I get no notification of an error in the console or the site. Any help is appreciated.
webpack.dev.js
const path = require("path");
module.exports = {
entry: {
main: ["./src/main.js"]
},
mode: "development",
output: {
filename: "[name]-bundle.js",
path: path.resolve(__dirname, "../js"),
publicPath: "/js"
},
devServer: {
contentBase: "../tester",
overlay: true
},
module: {
rules: [
{
test: /.css$/,
use: [
{
loader: "style-loader"
},
{
loader: "css-loader"
}
]
}
]
}
};
webpack webpack-dev-server webpack-4 webpack-style-loader
asked Nov 21 at 14:06
Dmitriy
316112
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I have a simple Webpack environment set up. The dev server and auto reload are all working fine for both CSS and JS files, however if I make a syntax error in my CSS, the console does not give me any error messages. also when I set overlay: true in my config, I get no notification of an error in the console or the site. Any help is appreciated.
webpack.dev.js
const path = require("path");
module.exports = {
entry: {
main: ["./src/main.js"]
},
mode: "development",
output: {
filename: "[name]-bundle.js",
path: path.resolve(__dirname, "../js"),
publicPath: "/js"
},
devServer: {
contentBase: "../tester",
overlay: true
},
module: {
rules: [
{
test: /.css$/,
use: [
{
loader: "style-loader"
},
{
loader: "css-loader"
}
]
}
]
}
};
webpack webpack-dev-server webpack-4 webpack-style-loader
asked Nov 21 at 14:06
Dmitriy
316112
I have a simple Webpack environment set up. The dev server and auto reload are all working fine for both CSS and JS files, however if I make a syntax error in my CSS, the console does not give me any error messages. also when I set overlay: true in my config, I get no notification of an error in the console or the site. Any help is appreciated.
webpack.dev.js
const path = require("path");
module.exports = {
entry: {
main: ["./src/main.js"]
},
mode: "development",
output: {
filename: "[name]-bundle.js",
path: path.resolve(__dirname, "../js"),
publicPath: "/js"
},
devServer: {
contentBase: "../tester",
overlay: true
},
module: {
rules: [
{
test: /.css$/,
use: [
{
loader: "style-loader"
},
{
loader: "css-loader"
}
]
}
]
}
};
webpack webpack-dev-server webpack-4 webpack-style-loader
webpack webpack-dev-server webpack-4 webpack-style-loader
asked Nov 21 at 14:06
Dmitriy
316112
asked Nov 21 at 14:06
Dmitriy
316112
asked Nov 21 at 14:06
Dmitriy
316112
asked Nov 21 at 14:06
Dmitriy
316112
asked Nov 21 at 14:06
Dmitriy
316112
316112
add a comment |
add a comment |
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53413861%2fwebpack-not-detecting-css-errors%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
