Roman Usherenko

I've hit this issue after we've switched to yarn workspaces. It was working fine with a monolithic app but now with the monorepo it takes 10+ seconds on each change...

@leehambley I've posted a failing test in #784 Don't know if you get notifications to closed issues. If you did get that too, sorry for the doubleposting

Well, I didn't propose any changes. I simply created a 'case I expect to work'. I understand that this is an opinionated topic. There's a handful of issues related to...

the thing is i want `context` to remain `.` because that's where the app code is. the `../` appears only because of how workspaces hoist node_modules. Additionally, as you can...

hmm... I see. I'll probably have to drop the `[pathname]` part as a workaround (I can't change the context because too many things in the build rely on it: babel...

@alexander-akait yes, I'm using a monorepo powered by yarn workspaces. which hoist all the node_modules to the root level. what do you mean by "default values"?

well... I don't really remember why it was done like this (years ago). I think I'll just use the defaults now, was just surprised that webpack5 behaves differently than file-loader

@tiagobnobrega how did you manage to workaround this? replying with [0, 'Network Error'] returns an error with both `response` and `request` set, so that'd trigger the `if (error.response)` branch actually...

daaaamn :D you're right, I've just recently disabled the Less plugin. Thanks a lot for your help I think some other plugins warn you when you're trying to disable their...

thanks for the review, @mislav! I ended up reverting most of my changes and instead dropped the fixture usage in favor of an inline definition to avoid future false negatives...