-
-
Notifications
You must be signed in to change notification settings - Fork 429
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
Silently fails/stalls webpack with no error #100
Comments
got this issue too. the directory structure is something like this.
also I used the build succeeds when I first remove the |
That's strange, thx for reporting this. Could you set up a small gist that reproduces the error? |
Does putting |
I'm reporting the same issue. |
Sorry, it helps but builds very slowly. I've been waiting for a couple of minutes and it have compiled after all :) |
Also downgrading to 0.5.0 and using node-sass 3.1.1 fixed this for me. |
3.1.1 also suffers from threading problem, so there must be some other, additional issue. @evandegr can you post somewhere a minimal but complete example to reproduce this issue? |
I had this same issue. It happens when I import a utility .scss file (it has mixins) into 2 or more other scss files. If I just import it into 1 scss file, webpack builds correctly. However, I have no problem with config .scss files that only define variables. I can include those into as many .scss files with no build problem.
|
Weird, I have the same problem and fixed it by downgrading to 0.5.0. Tried 0.6.0 and it didn't work. |
We experienced this issue as well - multiple imports over different files of a global ( |
I would really love if webpack community could produce a simple, self-contained setup to reproduce the issue. |
@saper I'm literally doing that right now ;) |
@haustraliaer nice! :) i was going going to do it this weekend but ran out of time. Would really love to get this resolved so we can stop adding 30 sass include paths into our build. Let me know if you need any help! |
I have a sample for you to fiddle with: https://github.com/piotrf/webpack-playground
Hope that helps. |
Hah, beat me to it... Here's my project anyway which shows pretty clearly where it breaks: |
Any updates on this? Still not working and hangs :( |
@mmahalwy It seems like the node-sass guys are gonna take a while to update this issue - as it's not a simple problem to fix. I'm honestly about to bail on sass in favour of postcss. |
Dzięki, @PiotrF Right now I am getting the same With https://github.com/saper/webpack-playground/tree/uncommenting@f547bb0 I get: https://gist.github.com/e0ec0e85bc048922ca27 With the master (saper/webpack-playground@f547bb0) it gives https://gist.github.com/9255315d068b8edc36b Not a big difference, if any.... No hangs... |
@haustraliaer great suggestion! PostCss looks amazing! |
@haustraliaer 's example shows the hangs. |
|
I can unfortunately confirm that https://github.com/haustraliaer/sass-webpack hangs due to sass/node-sass#857 |
Just in case this helps anybody I also had this precise issue with importing a partial just fine until I imported it again for the third time. Webpack would simply hang. Upgrading |
yeah, upgrading the sass-loader version solved for me also, thanks @mderrick |
Running into the same issue using a simple mixin, but not sure of it's entirely the same or whether I should create a new issue. Using @mixin font-sans($font: 'Lato') {
font-family: $font, sans-serif;
font-style: normal;
}
@mixin font-sans-light {
@include font-sans();
font-weight: 300;
} Note the Kind of a "nevermind" here as I just found the culprit, though I'd expect it to throw some errors. Accidentally defined 2 mixins with the same name where one then referenced itself: @mixin font-sans($font: 'Lato') {
font-family: $font, sans-serif;
font-style: normal;
}
@mixin font-sans {
@include font-sans;
font-weight: 400;
} Probably stuck in an infinite loop or something and made it quit altogether. |
I just run into this exact same issue. I'm using My webpack configuration looks like this: {
devtool: 'eval',
entry: {
app: path.resolve(__dirname, 'start.js'),
},
module: {
loaders: [
{
loader: 'babel',
test: /\.jsx?$/,
},
{
loader: ExtractTextPlugin.extract('css?modules&importLoaders=1&localIdentName=[name]--[local]___[hash:base64:5]!sass!postcss-loader'),
test: /\.scss$/,
},
],
},
plugins: [
new ExtractTextPlugin('styles.css', { allChunks: true }),
],
postcss: [
Autoprefixer,
],
output: {
path: path.resolve(__dirname, 'dist'),
filename: '[name].js',
},
resolve: {
extensions: ['', '.js', '.jsx'],
},
watch: true,
} Am I doing anything wrong? Is this a known problem of using CSS modules with SASS? Is there anything I can try to fix this either temporarily or permanently? Help with this would be truly appreciated since I'm completely stuck with this issue. Thank you! |
This still happens to me with |
I have same error with latest sass-loader |
happens "sass-loader": "^4.0.2", |
This is still happening, 2 years and there is no final resolution? I'm using |
If someone can publish a project that makes this reproducible, that would be a big help 👍 |
From what i can gather, it's really a cyclical import issue. I don't think there's anything to do for sass-loader other than to detect/report the problem for the user to fix. |
Webpack stalled at compiling Javascript files through babel. Adding the options below to watchOption: {
aggregateTimeout: 1,
poll: 1000
} So my Webpack config file looks now like this var path = require('path');
module.exports = {
entry: ["./js/index.js"],
devtool: "source-map",
output: {
path: path.join(__dirname, 'public/dist'),
filename: "bundle.js"
},
module: {
loaders: [
{
test: /\.js?$/,
loader: "babel",
query: {
presets: ["es2015"],
plugins: ["transform-flow-strip-types", "transform-class-properties"]
},
include: [
path.join(__dirname, 'js')
]
},
{
test: /\.css$/,
loaders: ['style', 'css']
},
{
test: /\.json$/,
loaders: ['json'],
include: [
path.join(__dirname, 'js'),
],
},
]
},
resolve: {
extensions: ['','.js', '.jsx', '.json', '.css']
},
watchOptions: {
aggregateTimeout: 1,
poll: 1000
}
}; |
Staging was hanging indefinitely when it started optimizing assets (part of the `npm run build` postinstall script). I didn't investigate fully, but it seems to be related to Node's poor grasp of system resources[1,2,3]. One suspect was identified in the build output: ``` > npm run build (node:46) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 SIGINT listeners added. Use emitter.setMaxListeners() to increase limit ``` [1] webpack/webpack#2012 (comment) [2] webpack/webpack#4558 [3] webpack-contrib/sass-loader#100
Staging was hanging indefinitely when it started optimizing assets (part of the `npm run build` postinstall script). I didn't investigate fully, but it seems to be related to Node's poor grasp of system resources[1,2,3]. One suspect was identified in the build output: ``` > npm run build (node:46) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 SIGINT listeners added. Use emitter.setMaxListeners() to increase limit ``` [1] webpack/webpack#2012 (comment) [2] webpack/webpack#4558 [3] webpack-contrib/sass-loader#100
Staging was hanging indefinitely when it started optimizing assets (part of the `npm run build` postinstall script). I didn't investigate fully, but it seems to be related to Node's poor grasp of system resources[1,2,3]. One suspect was identified in the build output: ``` > npm run build (node:46) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 SIGINT listeners added. Use emitter.setMaxListeners() to increase limit ``` [1] webpack/webpack#2012 (comment) [2] webpack/webpack#4558 [3] webpack-contrib/sass-loader#100
Staging was hanging indefinitely when it started optimizing assets (part of the `npm run build` postinstall script). I didn't investigate fully, but it seems to be related to Node's poor grasp of system resources[1,2,3]. One suspect was identified in the build output: ``` > npm run build (node:46) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 SIGINT listeners added. Use emitter.setMaxListeners() to increase limit ``` [1] webpack/webpack#2012 (comment) [2] webpack/webpack#4558 [3] webpack-contrib/sass-loader#100
Staging was hanging indefinitely when it started optimizing assets (part of the `npm run build` postinstall script). I didn't investigate fully, but it seems to be related to Node's poor grasp of system resources[1,2,3]. One suspect was identified in the build output: ``` > npm run build (node:46) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 SIGINT listeners added. Use emitter.setMaxListeners() to increase limit ``` [1] webpack/webpack#2012 (comment) [2] webpack/webpack#4558 [3] webpack-contrib/sass-loader#100 Signed-off-by: Lee Porte <lee.porte@digital.cabinet-office.gov.uk>
Staging was hanging indefinitely when it started optimizing assets (part of the `npm run build` postinstall script). I didn't investigate fully, but it seems to be related to Node's poor grasp of system resources[1,2,3]. One suspect was identified in the build output: ``` > npm run build (node:46) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 SIGINT listeners added. Use emitter.setMaxListeners() to increase limit ``` [1] webpack/webpack#2012 (comment) [2] webpack/webpack#4558 [3] webpack-contrib/sass-loader#100 Signed-off-by: Lee Porte <lee.porte@digital.cabinet-office.gov.uk>
Staging was hanging indefinitely when it started optimizing assets (part of the `npm run build` postinstall script). I didn't investigate fully, but it seems to be related to Node's poor grasp of system resources[1,2,3]. One suspect was identified in the build output: ``` > npm run build (node:46) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 SIGINT listeners added. Use emitter.setMaxListeners() to increase limit ``` [1] webpack/webpack#2012 (comment) [2] webpack/webpack#4558 [3] webpack-contrib/sass-loader#100
Staging was hanging indefinitely when it started optimizing assets (part of the `npm run build` postinstall script). I didn't investigate fully, but it seems to be related to Node's poor grasp of system resources[1,2,3]. One suspect was identified in the build output: ``` > npm run build (node:46) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 SIGINT listeners added. Use emitter.setMaxListeners() to increase limit ``` [1] webpack/webpack#2012 (comment) [2] webpack/webpack#4558 [3] webpack-contrib/sass-loader#100 Signed-off-by: Lee Porte <lee.porte@digital.cabinet-office.gov.uk>
Staging was hanging indefinitely when it started optimizing assets (part of the `npm run build` postinstall script). I didn't investigate fully, but it seems to be related to Node's poor grasp of system resources[1,2,3]. One suspect was identified in the build output: ``` > npm run build (node:46) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 SIGINT listeners added. Use emitter.setMaxListeners() to increase limit ``` [1] webpack/webpack#2012 (comment) [2] webpack/webpack#4558 [3] webpack-contrib/sass-loader#100 Signed-off-by: Lee Porte <lee.porte@digital.cabinet-office.gov.uk>
Staging was hanging indefinitely when it started optimizing assets (part of the `npm run build` postinstall script). I didn't investigate fully, but it seems to be related to Node's poor grasp of system resources[1,2,3]. One suspect was identified in the build output: ``` > npm run build (node:46) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 SIGINT listeners added. Use emitter.setMaxListeners() to increase limit ``` [1] webpack/webpack#2012 (comment) [2] webpack/webpack#4558 [3] webpack-contrib/sass-loader#100 Signed-off-by: Lee Porte <lee.porte@digital.cabinet-office.gov.uk>
Staging was hanging indefinitely when it started optimizing assets (part of the `npm run build` postinstall script). I didn't investigate fully, but it seems to be related to Node's poor grasp of system resources[1,2,3]. One suspect was identified in the build output: ``` > npm run build (node:46) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 SIGINT listeners added. Use emitter.setMaxListeners() to increase limit ``` [1] webpack/webpack#2012 (comment) [2] webpack/webpack#4558 [3] webpack-contrib/sass-loader#100 Signed-off-by: Lee Porte <lee.porte@digital.cabinet-office.gov.uk>
Staging was hanging indefinitely when it started optimizing assets (part of the `npm run build` postinstall script). I didn't investigate fully, but it seems to be related to Node's poor grasp of system resources[1,2,3]. One suspect was identified in the build output: ``` > npm run build (node:46) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 SIGINT listeners added. Use emitter.setMaxListeners() to increase limit ``` [1] webpack/webpack#2012 (comment) [2] webpack/webpack#4558 [3] webpack-contrib/sass-loader#100
I have 2 imports that I use in multiple scss files that look like the following:
Everything works fine until I hit one file that has the exact same imports. Then, I see webpack build stall and it shows no errors. If I remove the import for this file, everything works, if I add it, it stalls. I don't understand why its happening because it's using the exact same imports. Problem still occurs if I remove everything in that file except for the imports. Problem does not occur if I remove the imports as well.
The text was updated successfully, but these errors were encountered: