Closed joacim-boive closed 6 years ago
Hey @joacim-boive, node-sass-once-importer doesn't write any files to the file system.
Where is compiler.watch
coming from?
@maoberlehner - Huh. That's weird then.
compiler.watch is just Webpack with the current configuration loaded:
const webpack = require('webpack');
const compiler = webpack(config);
This is equivalent to: webpack --watch
But I am using the Node.js API of webpack for my build script: https://webpack.js.org/api/node/
It would be great if you could provide me with a minimal setup to reproduce this error (just: webpack.config.js
, build.js
, entry.js
, index.scss
). That would make things a lot easier :)
(and all those files containing only the bare minimum code to cause the error)
Yes, I understand. I'll see what I can do - it's part of our big build script the on to "solve all problems". ;)
My bad - I was a configuration issue in my build script.
Thanks for letting me know, and for solving the problem yourself 👍
@joacim-boive What ended up being the problem? I'm experiencing the same endless loop issue when I use the SASS magic importer.
@isaacpz In my case I happened to be running the script twice.
The build is invalidated and re-builds - ends up in an endless loop.
I'm guessing it stores some temp files somewhere that I need to configure webpack to ignore(?).
I am already ignoring [/node_modules/, /build/]
If I remove importer: require('node-sass-once-importer')(), then the watcher works as expected.