nimble VS nimlsp

I was using Nim for some of last years Advent of Code problems. I was mostly liking the syntax. Was a bit bother by the standard library have a snake case and camel case reference for each function (if I'm remember that correctly).

At the time nimble also required me to have NPM to install the the Nim package manager, Nimble. This was not ideal, but looking at [the nimble project install docs](https://github.com/nim-lang/nimble#installation) it seems like it is now package with the language.

Might try dusting it off for some AoC puzzles this year :)

nimble develop -g doesn't work A possible solution is to add "g" to where "global" is placed.

I meant it's unfortunate that Nimble has no standard system-wide library management. It's one of the mains thing holding Nim back from being more prevalent in the Linux sphere in my opinion.

`nimble` is the package manager for the programming language `nim` [1].

From [2], we can see that `nimble scss` simply generates the CSS files for the frontend.

The benefit of OSS is you can answer these questions yourself with a bit of poking around! IMO this is a fairly standard installation process, maybe the fact that it's using Nim instead of a more mainstream language makes it look more daunting than it is. The only out-of-the-ordinary thing here, IMO, is `nimble build` instead of `make build`.

[1]: https://github.com/nim-lang/nimble

[2]: https://github.com/zedeus/nitter/blob/master/nitter.nimble

Something I'm excited about: v1.6.2 integrates support for (not yet released) Nimble[1] v0.14, which introduces lockfiles. I've had terrible experiences with lockfiles in JS land, but they are sorely needed for Nim projects as (fingers crossed) they'll allow for reproducible builds without having to resort to the nimbus-build-system[2]. The latter isn't completely horrible — a lot of much appreciated hard work has gone into it, and it's been a real workhorse — but some days it feels like a big ball and chain.

[1] https://github.com/nim-lang/nimble#nimble

[2] https://github.com/status-im/nimbus-build-system

So you wouldn't have a problem with a package manager where the configuration is in the same language, such as Nimble?

if you structure your project with nimble (which can be be used for both libraries and applications) you can use nimble build and nimble run. While I do use nimble for managing dependencies for projects I don't use these commands that often while developing, e.g. because I'm working on a single test or something like that.

Having similar syntax to Ruby makes it easier to port Ruby code to Crystal (ex: digest-crc -> digest-crc.cr). The Crystal stdlib is very complete and they have a growing "shards" ecosystem, roughly the same age as Rust's https://crates.io or Nim's nimble. You should look into Crystal again.

Downloading https://github.com/PMunch/nimlsp using git

Cloning into '.'... From https://github.com/pmunch/nimlsp * tag v0.4.4 -> FETCH_HEAD + nimble build -y --localdeps Warning: Using project local deps mode Verifying dependencies for [email protected] Prompt: No local packages.json found, download it from internet? -> [forced yes] Downloading Official package list Success Package list downloaded. Installing jsonschema@>= 0.2.1 Downloading https://github.com/PMunch/jsonschema using git Verifying dependencies for [email protected] Installing ast_pattern_matching@any version Downloading https://github.com/nim-lang/ast-pattern-matching using git Verifying dependencies for [email protected] Installing [email protected] Success: ast_pattern_matching installed successfully. Installing [email protected] Success: jsonschema installed successfully. Installing asynctools@>= 0.1.1 Downloading https://github.com/cheatfate/asynctools using git Verifying dependencies for [email protected] Installing [email protected] Success: asynctools installed successfully. Building nimlsp/nimlsp_debug using c backend [1m/home/terrior/.local/share/nvim/mason/.packages/nimlsp/src/nimlsppkg/suggestlib.nim(3, 18) [0m[31mError: [0mcannot open file: nimsuggest/nimsuggest[36m[0m[0m Tip: 30 messages have been suppressed, use --verbose to show them. Error: Build failed for package: nimlsp ... Execution failed with exit code 1 ... Command: /usr/bin/nim c --colors:on --noNimblePath -d:NimblePkgVersion=0.4.4 --path:/home/terrior/.local/share/nvim/mason/.packages/nimlsp/nimbledeps/pkgs/ast_pattern_matching-1.0.0 --path:/home/terrior/.local/share/nvim/mason/.packages/nimlsp/nimbledeps/pkgs/jsonschema-0.2.1 --path:/home/terrior/.local/share/nvim/mason/.packages/nimlsp/nimbledeps/pkgs/asynctools-0.1.1 --hints:off -o:/home/terrior/.local/share/nvim/mason/.packages/nimlsp/nimlsp_debug /home/terrior/.local/share/nvim/mason/.packages/nimlsp/src/nimlsp_debug.nim spawn: bash failed with exit code 1 and signal 0.

nimlangserver is an implementation of Language Server Protocol with the goal to make nim IDE experience more mature. The main difference between nimlangserver and the existing nimlsp is that nimlangserver runs nimsuggest in a separate process and that nimlangserver is using a newly introduced version of nimsuggest v3(see bellow). nimlangserver is currently integrated in VScode via vscode-nim and in Emacs via lsp-mode but adding integraion with other editors should be trivial.

Downloading https://github.com/PMunch/nimlsp using gitTVerifying dependencies for [email protected]: Dependency on jsonschema@>= 0.2.1 already satisfiedVerifying dependencies for [email protected]: Dependency on ast_pattern_matching@any version already satisfiedVerifying dependencies for [email protected]: Dependency on asynctools@any version already satisfiedVerifying dependencies for [email protected] [email protected] nimlsp/nimlsp using c backend/tmp/nimble_153465/githubcom_PMunchnimlsp/src/nimlsppkg/baseprotocol.nim(2, 8) Warning: imported and not used: 'logger' [UnusedImport]/tmp/nimble_153465/githubcom_PMunchnimlsp/src/nimlsppkg/suggestlib.nim(11, 8) template/generic instantiation of `mImport` from here/tmp/nimble_153465/githubcom_PMunchnimlsp/src/nimlsppkg/suggestlib.nim(7, 14) Error: cannot open file: /usr/nimsuggest/nimsuggest.nimPrompt: Build failed for '[email protected]', would you like to try installing 'nimlsp@#head' (latest unstable)? [y/N]Answer: NTip: 10 messages have been suppressed, use --verbose to show them.Error: Aborting installation due to build failureimlsp using gitT Verifying dependencies for [email protected] Info: Dependency on jsonschema@>= 0.2.1 already satisfied Verifying dependencies for [email protected] Info: Dependency on ast_pattern_matching@any version already satisfied Verifying dependencies for [email protected] Info: Dependency on asynctools@any version already satisfied Verifying dependencies for [email protected] Installing [email protected] Building nimlsp/nimlsp using c backend /tmp/nimble_153465/githubcom_PMunchnimlsp/src/nimlsppkg/baseprotocol.nim(2, 8) Warning: imported and not used: 'logger' [UnusedImport] /tmp/nimble_153465/githubcom_PMunchnimlsp/src/nimlsppkg/suggestlib.nim(11, 8) template/generic instantiation of `mImport` from here /tmp/nimble_153465/githubcom_PMunchnimlsp/src/nimlsppkg/suggestlib.nim(7, 14) Error: cannot open file: /usr/nimsuggest/nimsuggest.nim Prompt: Build failed for '[email protected]', would you like to try installing 'nimlsp@#head' (latest unstable)? [y/N] Answer: N Tip: 10 messages have been suppressed, use --verbose to show them. Error: Aborting installation due to build failure