Love.js-Api-Player VS love.js

Also, if you want to call JS functions from within love while running in the browser check out https://github.com/MrcSnm/Love.js-Api-Player. For example, if you want to set the window to fullscreen from within the game.

If you want to make a web version of your game your friends can play in browser, I use davidobot's love.js fork. If you follow the instructions there, you can make a nice web version of your game. (I have to use "compatibility mode" to make it play nice with itch.) Itch makes it easy to set up web games: just upload the finished love.js zip export, making sure there's an "index.html" file. The easiest way to go is to use the default love.js export, and just set itch to open the page in fullscreen. If you want to make the game run inside your itch page without opening into its own window, you'll need to edit the index.html file to remove all the frame stuff around your game.

I am using love.js in order to create the webbuild, I plan on doing the usual stuff for the downloadables.

There's some info here and here. Never actually done though.

Does this: https://github.com/Davidobot/love.js allow for network communication in a web browser?

I'm intending to make more simple browser games in Love2D and I'd like to get ahead of any future headaches. Is this something that I can fix on my end, without the users having to manually allow a cookie? Is the cookie required for lovejs to work? Should I try compiling the most recent version of lovejs myself (instead of relying on makelove) and see if that fixes it?

The version the wiki recommends atm: https://github.com/Davidobot/love.js

You can use LÖVE framework and love.js. LÖVE is based on Lua, an easy to learn dynamic language - you can find many tutorials both for Love and Lua. Love.js transcripts your code to javascript, ready for browser. For simple games, no need to know javascript, love.js works quite well and does all the job.