You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
hey @arj03 since DAT has been in, whenever I open the devTools, I get hammered because DAT is hanging on errors that are being thrown. It makes debugging other things , or doing styling work a nightmare
For the moment I've added a env variable which means you can start Patchbay and skip initialising the DAT stuff :
$ DAT=false npm start
This is a workable solution but might be nice to find something less manual in the future
The text was updated successfully, but these errors were encountered:
Don't know. The debugger hangs on things trying to check line length or a
bunch of mundane stuff.
Let me know if you can't replicate and want to do anything about it and I
can take screenshot
On Sat, 18 May 2019, 10:15 Anders Rune Jensen, ***@***.***> wrote:
The errors are if the files are not there anymore right?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#334?email_source=notifications&email_token=AAUK3HRVGHZGWVQBHEQGDPTPV4U67A5CNFSM4HNI22U2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODVV7LVI#issuecomment-493614549>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAUK3HUAFKCQF7RLGK5DJCLPV4U67ANCNFSM4HNI22UQ>
.
hey @arj03 since DAT has been in, whenever I open the devTools, I get hammered because DAT is hanging on errors that are being thrown. It makes debugging other things , or doing styling work a nightmare
For the moment I've added a env variable which means you can start Patchbay and skip initialising the DAT stuff :
This is a workable solution but might be nice to find something less manual in the future
The text was updated successfully, but these errors were encountered: