Closed salascz closed 1 year ago
Hello, the error on your screenshot is from dev console and not from SPFx. Do you see this error as a full screen error?
Hello, Thanks for additional question. I tried the behaviour on empty SPFx solutions.
It might be connected with experimental "hotRefresh": true
configuration :-(.
true
or false
to fullScreenErrors
serve
and test my issue
Sorry, I was not aware this is connected to experimental hotRefresh
feature. Not sure if there is anything to do about....
Yeah, unfortunately I cannot do a lot with this hotRefresh feature, because it's an experimental and intended to be used in "normal" react solutions. It was a miracle, that it worked in SPFx, because everything is lot more complicated when it comes to extending SPFx builds. I will try to take a look at this problem and maybe will be able to fix the current errors.
No problem, experimental function is not something you should spent much time.
Thanks for your effort, let me close this issue.
Hello, I am using the spfx-fast-server in versions for spfx 1.15.2 and 1.16.1.
Is there any way, how to disable FullScreenErrors? The configuration does not seem to work. I tried to find this topic in general webpack4 issue list, but I was not able to find proper fix.
I like the FullScreenErrors in general, but there is an annoying error message presented on every reload for our tenant connected with Cortex which I am not able to influence from my position. (=> I have to close the webpack fullscreen error even without an error in my code)