stack
nix-haskell-example
Our great sponsors
| stack | nix-haskell-example | |
|---|---|---|
| 47 | 1 | |
| 3,889 | 0 | |
| 0.1% | - | |
| 0.0 | 0.0 | |
| 4 days ago | over 1 year ago | |
| Haskell | Nix | |
| BSD 3-clause "New" or "Revised" License | - |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
stack
-
Leaving Haskell Behind
Ah, didn't run into this issue, as I don't use vscode.
Apparently there is some work being done to improve the stack <> hls experience, but I wouldn't know how it's going and when it's being delivered: https://github.com/commercialhaskell/stack/issues/6154
-
ANN: stack-2.11.1
Fix incorrect warning if allow-newer-deps are specified but allow-newer is false. See #6068.
See https://haskellstack.org/ for installation and upgrade instructions.
-
PEP 582 rejected - consensus among the community needed
Fair enough! Thanks for the suggestion, then. In fact, the non-Python language I develop most in (Haskell, with the Stack package manager) has exactly that behaviour as a default: new packages are installed to a sandboxed local directory, and it takes an explicit request to install something globally. (And even then, you can switch between different global "known good configurations" of package versions which work well together – a pretty handy feature.)
- Any open source projects to contribute to for beginners
-
ANN: stack-2.9.3
In YAML configuration files, the hackage-security key of the package-index key or the package-indices item can be omitted, and the Hackage Security configuration for the item will default to that for the official Hackage server. See #5870.
See https://haskellstack.org/ for installation and upgrade instructions.
-
[ANN] First release candidate for stack-2.9.3
Yes, that is correct. Stack's allow-newer: true configuration has always actually meant 'ignore bounds'. However, the author of the allow-newer-deps development has in mind a further development that will introduce an actual ignore-bounds key with the same expressive syntax that is used by Cabal. This is discussed at Stack #5910.
You can download binaries for this pre-release from: Release rc/v2.9.2.1 (release candidate) · commercialhaskell/stack · GitHub.
-
how do I specify cabal fields to stack?
I'm trying to use the cabal mixins feature to automatically replace every implicit prelude import with a custom prelude (in this case relude). apparently it doesn't play well with `stack repl` https://github.com/commercialhaskell/stack/issues/5077 but I don't really use it anyway.
nix-haskell-example
-
Managing issues with the Haskell Stack projects under NixOS
Here: I threw together an example (without flakes): https://github.com/erikbackman/nix-haskell-example
What are some alternatives?
ghcup-hs - THIS REPO IS A MIRROR, BUG REPORTS GO HERE:
Cabal - Official upstream development repository for Cabal and cabal-install
ghcid - Very low feature GHCi based IDE
haskell-language-server - Official haskell ide support via language server (LSP). Successor of ghcide & haskell-ide-engine.
castle - A tool to manage shared cabal-install sandboxes.
profiterole - GHC prof manipulation script
implicit-hie - Auto generate a stack or cabal multi component hie.yaml file
bisect-binary - Tool to determine relevant parts of binary data
stack-yaml - parse stack.yaml files
hdocs - Haskell docs tool
fast-tags - Incremental vi and emacs tags for haskell.
bumper - Haskell tool to automatically bump package versions transitively.