![]() ![]() So I installed ufw, allowed port 8080 access, changed the magicmirror config to whitelist my local network (in my case, 10.1.1.0/24). So now I had a server running on a piece of hardware on my local network, but no display for that server.Īh, but I did. You get cool new features (and security fixes). ![]() But, I ended up getting a newer version of Chromium that supported optional chaining! The site loaded! I realised this about an hour into the roughly two hour apt dist-upgrade process (not including time lost to user prompts that sat there, waiting for input). So I didn’t have any display to permenantly use. However, at this point I hadn’t purchased any hardware, just used what I had on hand. ![]() This would be a problem if I wanted to open the website on a display connected to the raspberry pi. The server worked, I just couldn’t fully load the website. I could possibly do an OS upgrade and get new things. Running an apt upgrade brought it up to Chromium 72, still not new enough. I could also reproduce this issue by trying to run the code sample on MDN, which was neat. Support for optional chaining was introduced to Chrome 80, in in Feb 2020. syntax, if the function called is undefined or null, undefined is returned (rather than throwing an error). This error didn’t occur on my laptop, using a clone of the repo at the same commit.Ī recent addition to JavaScript is optional chaining. After slowly loading the developer tools in Chromium, where was a syntax error in weather.js line 165.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |