Install Fails #411
Comments
|
Same issue here. |
|
same here |
|
What about the other install method?
It worked on Ubuntu 18.04 ( |
|
same; |
|
The problem is with text-buffer dependency and node-inspector (dev-dependency). I upgraded everything to latest (in three projects slap, editor-widget, base-widget) https://github.com/cancerberoSgx/slap It currently doesn't work with node 12 so you have to use 11 or and it works with node.js 11 or older (it currently doesn't work with node.js 12 - working on that), so these are instructions to use |
This is unfortunately broken in Jun 2019. It seems to break in almost the same way, here complaining about the install script of |
Certainly. |
|
@oliver-daniel same here |
|
@iayaz @oliver-daniel - my fork - cancerberosgx/slap currently doesn't work with node 12 - only 11 and older (i'm working on it). I updated install instructions in my original comment #411 (comment) |
|
update: this is now the dependency not supporting node 12 - atom/superstring#75 |
Dear @cancerberoSgx Based on your work i followed up on all the issues pertaining to upstream build failures in a NodeJS 12 context, also stumpeling onto other issues in the dependency chain (like unreferenced required binaries & build tools @ It required forking 5 repos ( To install npm install --global git+https://github.com/sidneys/slap.git#masterCheers, |
|
See this issue, I have answered it, #414 |
|
This project seemed like it was the solution to all my terminal editing woes, but installing it is a slap in the face. I can't believe the install process is so messy :( @sidneys your solution sadly isn't compatible with Node LTS v14. So sad. |
|
@darkguy2008 Wow, such entitlement. Here's a thought: why don't you use your smarts for the good of the community (and yourself) and contribute a better install process? |
I always do when I find the solution, unfortunately for this project, I don't have the time nor the will to go through the messy process of fixing npm dependencies, but I think it's evident how hard it is considering there's about 3+ issues opened about the install process:
Plus, the shell script wants to install Node v6 which is pretty old already. I fail to see how there's users still using this, and nobody (not even the owner) seems to have showed any interest in fixing it properly. The last commit was in 2016 so... I'd say it's pretty much abandoned. If my comment is offensive to you I suggest you just keep scrolling or ignore it, I'm entitled to my opinion as much as you are, and I lost about 30 minutes or so just trying to get this going without success. |
|
The project (and the author thereof) is very much dead, sadly. |
Oof.Size() = Int32.MaxValue; Oof, really. That's a bummer, and now I feel bad... Alright, I'll try to see if I can find a solution to this ASAP, and maybe make a PR/fork or something. So sad though :( |
|
If anyone is still interesting in this editor, I have a fork that runs under node 16(haven't tried 17). My plan is maintain the project as open source/update the codebase as i get time. Personally I like js more than lua/vimscript/emacs, so this editor seemed like nice change of pace. It also uses less resources than VSCode |
:) Please share the fork, thanks! |
That would be https://github.com/ajstrand/slap |
|
@cancerberoSgx @Toby222 i ran into issues trying to convert the project to use es2015/es6 modules, so right now the project is kind of at a standstill. I’ll post the branch that I’ve been working with later this evening or tomorrow. Feel free to fill issues/pull requests if you would like to contribute. |
$ npm i -g slap@latestcommand fails;
/home/oytun/.npm/_logs/2019-02-08T11_14_40_409Z-debug.log last lines;
The text was updated successfully, but these errors were encountered: