[js] D8 Port

I doubt there will be a D8 version of this module. Core was significantly refactored to handle REST style requests much easier and faster. Most of what this module provides is likely antiquated and unnecessary in comparison.

So I've been thinking about this.

Even if it doesn't actually implement the bootstrapping reduction (like is needed in 7.x), there's still a lot of "helpers" that were introduced in 7.x-2.x that allows easier creation/execute of JS callbacks.

I don't think it could hurt to try and port a watered down version?

Well this really puts a hamper on things :-/

Note: any work on D8 will need this related issue core patch.

Alright, I've gone ahead and done some initial port work: 2637e55.

As mentioned above, this won't enable unless that core patch is applied.

Things are probably about 80% of the way there. Everything is in the "right place", just need to hook up a few remaining bits.

I really, really, don't want to change the project name.

Nor would I name it anything like "bootstrap" since there's https://www.drupal.org/project/bootstrap and it would confuse people.

8.x also now has a kernal... not a "bootstrap" process like in prior versions.

I don't care what the name is

I know you don't, but I do.

I don't want to have to maintain two separate projects (7.x and 8.x) that do the same thing. Not to mention porting patches will be even more difficult.

Please keep the name, it will help a lot to mograte to 8

don't fork - colaborate

If you do eventually have to rename the project, may I suggest “jsch”? “JavaScript Callback Handler” is the full human-readable name, and “jsch” is a good abbreviation that wouldn’t conflict with file type extensions.

Also, I know of several instances where one module was superseded entirely by another with a different name. Since js 7.x-1.x is defunct and a security risk and people should move away from it ASAP anyway, why not let it keep that “js” name and make its page a defunct module page pointing to a new “jsch” (or “jscb” as @RobKoberg suggested) with the existing 7.x-2.x code (appropriately internally renamed, of course)? Then the 8.x branch could go there as well.

On a somewhat related question: why is the 8.x branch “8.x-3.x”? Does it implement things in a drastically different manner even compared to 7.x-2.x? Are you planning on a 7.x-3.x branch?

(Accidental duplicate comment.)

I'm just going to close this. It's been years since I've opened it and a D8 port of this module is likely never to happen since D8 has rest and jsonapi now.