Videos on how to extend Flarum

@clarkwinkelmann, do you know of a good node.js / yarn (meow) video tutorial which starts at the very beginning? Something to help me learn why that yarn command (js compilation, I guess) is needed and what that is doing? Yeah, I need something that basic.

Edit: Ooo. I'm looking into how can I do all of this online on a simple Chromebook for example. So that I don't have to use my Mac desktop and be tied to that if I don't want to. I've come across codeenvy.io. You can set up a workspace and stack for free online. A tutorial on creating a Flarum Extension, but 100% online, not in a local offline environment, would be .

And another edit: After a pure fork of your poke demo and installing on my Flarum, I get:

Flarum encountered a boot error (Error)
Class 'ClarkWinkelmann\Poke\Extenders\ForumAttributes' not found
thrown in /vendor/zerosonesfun/poke/extend.php on line 24

But the class exists. I'm not seeing typos. I did see that in the extend file the forum/admin JavaScript was pointing to a dist folder which doesn't exist. I updated that.

010101 Class 'ClarkWinkelmann\Poke\Extenders\ForumAttributes' not found

In vendor/composer/autoload_static.php, find the array prefixDirsPsr4, and add:

    'ClarkWinkelmann\\Poke\\' =>
    array (
        0 => __DIR__ . '/..' . '/clarkwinkelmann/flarum-ext-poke/src',
    ),

010101 I did see that in the extend file the forum/admin JavaScript was pointing to a dist folder which doesn't exist

Yes, I did encounter that issue too. So, I ended up moving admin.js and forum.js into a /dist folder

So finally, have you installed the extension successfully?

clarkwinkelmann Arhhh.. sorry for not taking full attention in the class

EDIT: Yassssss!!! I manage to install it on my Flarum finally It works like a charm

010101 I guess when you do a yarn command in your tutorials you are doing something a little different.

It has the same effect. npm is the original package manager for Node.js that was born about 10 years ago. The company maintains the npmjs.com website, the npm public registry and the npm terminal utility that is usually bundled with Node.js.

The npm history is quite bumpy, and there was a period where very little improvements were made to the npm CLI. One of the main problems was that it was veeery slow to install packages (still faster than composer though). It also had some other annoying bugs and weird behaviours.

So some alternatives were born, the most popular being yarn by Facebook. yarn still uses the npm public registry (it actually mirrors it on Facebook's servers) but provides a different terminal utility that does similar things, presumably better. It was a common opinion that it was true (and a fact wrt performance), at the time, but today npm is much better than it was and has catched up on many aspects, so as far as I'm concerned there aren't many reasons to prefer yarn over npm today. I found npm to be actually faster than yarn in my limited testing.

In short, I would suggest to stick with npm unless you have a real reason for not using it. There's a lot more documentation and resources about npm than yarn on the web.