You are correct, and Nuclide shouldn’t matter if it doesn’t replace
that package is not in my .atom/packages so where is it (Debian 9 linux)?
It’s in the ASAR archive bundled with the executable. But you don’t need to mess with that. Just clone the package repo. No work has happened since the last release, so you don’t even have to check out a specific commit.
Is there a way to do what I want and have it survive an upgrade to atom/tabs? Do I finally have to learn coffeescript?
Yes and probably, but only if you want to.
APM gives you the option to use
apm link in a package code folder to create a symbolic link from
.atom/packages. When Atom starts up, any package in
.atom/packages with the same name as a core package will be loaded instead of the core package. Using these two behaviors, you can download and edit any core package you want, then reload Atom and see your changes in effect. If you want to revert to the core package, just delete the symbolic link and your code is fine. You can also use
apm link -d to create the symlink in
.atom/dev/ and have it only activate in developer mode, but I find it tedious to reopen Atom in developer mode when I’m messing with a package, so I do everything in normal mode.
As for CoffeeScript, it would probably be best to make your changes in the language and dialect spoken by the package authors, but you can also plug the whole package through a CS-to-JS converter, paste the JS into a renamed code file, and make your changes there. Change the package main file in