madsem

Needed this too, after playing around for a while with the suggestions from this issue and some others, I made this widget and just added some style: ```js import React,...

Not sure if it helps @MykalMachon, I removed webpack and babel and switched to esbuild. Now everything is working again and my dev server starts :)

@danez tried using Node 16 before I came here, it didn't change anything. @MykalMachon scratch my previous reply, it just started happening again. Edit: ``` ❯ ping localhost PING localhost...

Here is the output on Node 16: ``` via  v16.16.0 on ☁️ took 2s ❯ netlify dev ◈ Netlify Dev ◈ ◈ Ignored general context env var: LANG (defined...

@danez, you lifesaver! :) Amazing, thank you very much!! It's weird though, there was nothing anywhere that configured 8081, I tried changing the port via `--serve --port=8080`, browsersync was still...

I have this issue as well, in my case it's with the vagrant aws provider tho. Every time I do a vagrant reload, the IP of my aws instance changes...

yeah using a cluster in production on AWS Elasticache. A workaround is to change the config locally to default when running a migration, but that just introduces problems because I...

Ok true, or I switch to cluster mode disabled. Luckily I am flexible there. Laravel itself also has issues with Cache::tags() & cluster mode enabled.

This is the fix suggested by someone in the Laravel repo for using flush with cache tags, it might also solve this issue here as I saw Lada cache also...

Can't say anything about the connection looping, I tested the curly brace solution with Laravel 5.6 and there it seemed to fix the issue indeed, after implementation the errors about...