Nullified
Nullified
Please share your settings, this is a configuration error rather than a bug.
I'd vote for the server-side event handler. Giving the client less control over stuff is a great idea considering the amount of cheaters etc. Overall this is a good idea...
Is there any update on this issue? It's been a problem for a while, and I can not figure out how to use the CSS prop without manually adding the...
> Is there an update on this matter? I just made a simple logger till this is fixed/ someone knows a workaround, but I haven't spent much energy on trying...
Like shown above, I opened a pull request that will solve this issue. Until it gets released, I suggest building the code locally to solve the error. As far as...
@itschip I think this can be implemented now, will prevent people from getting errors in build mode. Since updating it or not won't have any effect on #32 anyway, better...
> Seems like you've installed some packages with npm instead of yarn. Please remove the package-lock file and install again with yarn to update the yarn.lock file :P This PR...
> I'm alive and kicking. I just didn't reply to the original comments - must have lost them in the email spam. > > > ~Just tested with Yarn and...
I totally forgot that this was about the boilerplate, my apologies 😂 Your solution is good, I agree.
I just updated this code so it does not have any merge conflicts (unfortunately lacking on some sleep; sorry about the messy rebase...)