bbcode-preview isn’t a published package.
You don’t have any need to fork the package unless you want to modify the code and publish it. The only action you need to take is to clone the repo. However, since the package in question seems to have been abandoned (it was created five years ago and has had no code changes for over a year), it might be prudent to keep a copy on your GitHub account just in case, and clone from your account. If you do decide that you want to modify the code, having the remote repo be under your account will make it easy for you to upload your changes and save or share them.
Actually, I just started up Atom, and it shows that bbcode-preview is installed now, but I don’t know if it is installed correctly.
It’s not, because
oniguruma hasn’t been built.
oniguruma, according to your debug log, is a dependency of
highlights (look at the section that starts with
154 silly saveTree). Even though Atom includes
oniguruma, it doesn’t include
highlights and APM, when it’s installing a package, doesn’t have access to the modules contained in the archive that stores all of Atom’s code, so it assumes that it needs to install
oniguruma contains C++ code that compiles into a regular expression engine, it automatically tries to run the module
node-gyp to compile the code.
node-gyp is just a binding for C++ build tools, which most Unix-based operating systems contain by default. Microsoft has never been one to assume that its users would be at all interested in software development, so the Microsoft build tools are available as optional downloads and you have to install Python yourself. There are instructions in the
node-gyp documentation about how to configure Windows to be able to build modules that rely on native code.
Using the built-in installer will not fix this (it’s the exact same APM process, just with a GUI). Windows is simply incapable of running the build process until you set it up to do so.