I'm using npm and webpack to compile and bundle javascript while also minifying and auto prefixing sass.
That and browser sync to make our lives a little easier while doing html/css.
Nothing too complicated to be honest.
Most of the time when I'm the one having problems I can fix it pretty quick.
The real misery begins when a Windows user is getting weird output from npm for whatever reason.
The last problem was when someone encountered this error.
(Couldn't open browser (if you are using BrowserSync in a headless environment, you might want to set the open option to false))
I do not have the issue on my mac while it completely breaks everything for the other developer.
Googling the issue did not make me any wiser.
For some reason it's also the person that really does not like build tools with the biggest and weirdest issues.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I'm using npm and webpack to compile and bundle javascript while also minifying and auto prefixing sass.
That and browser sync to make our lives a little easier while doing html/css.
Nothing too complicated to be honest.
Most of the time when I'm the one having problems I can fix it pretty quick.
The real misery begins when a Windows user is getting weird output from npm for whatever reason.
The last problem was when someone encountered this error.
(Couldn't open browser (if you are using BrowserSync in a headless environment, you might want to set the open option to false))
I do not have the issue on my mac while it completely breaks everything for the other developer.
Googling the issue did not make me any wiser.
For some reason it's also the person that really does not like build tools with the biggest and weirdest issues.