No, not the browser.
I probably should have explained in the beginning of my post that my first steps were to just follow the instructions for Linux and see what happens.
So I cloned the Github repo, changed the branch, and ran
Of course, it didn't work. So I looked through the output, and it looks like the errors were caused by one dependency that npm couldn't install:
It's just a package that the browser needs to compile, because beaker uses IPFS too. Since that package couldn't be installed via
npm, I just compiled that individual
go-ipfs package by itself, which is where I got stuck because I wasn't sure how to make npm use my compiled version to fulfill the dependency (or if such a thing is even possible... Like I said, I don't much about how npm works and what it can do)
Edit: Here's my output from running
npm install in the beaker directory. I snipped out what looked like irrelevant output, and hid my log-in name...