stack-run
Like cabal run for stack (by yamadapc)
stack
The Haskell Tool Stack (by commercialhaskell)
| stack-run | stack | |
|---|---|---|
| - | 49 | |
| 29 | 3,992 | |
| - | -0.1% | |
| 0.0 | 9.7 | |
| almost 6 years ago | 2 days ago | |
| Haskell | Haskell | |
| MIT License | BSD 3-clause "New" or "Revised" License |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
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.
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-run
Posts with mentions or reviews of stack-run.
We have used some of these posts to build our list of alternatives
and similar projects.
We haven't tracked posts mentioning stack-run yet.
Tracking mentions began in Dec 2020.
stack
Posts with mentions or reviews of stack.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2024-09-12.
-
Why Haskell?
Thanks! So it seems to be not packages, but templates, and this comment suggests it wasn't GitHub doing the rate limiting after all: https://github.com/commercialhaskell/stack/issues/4979#issue...
> Every other language I've used allows you to build code without authenticating to a remote service.
Sure, the problem here wasn't "building". It was downloading a package template (which one doesn't tend to do 60 times per hour). I agree packages shouldn't be fetched from GitHub.
-
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
- Help, i get this error when executing the command "xmonad"
-
ANN: stack-2.11.1
Fix incorrect warning if allow-newer-deps are specified but allow-newer is false. See #6068.
-
[ANN] First release candidate for stack-2.11.1
You can download binaries for this pre-release from: Release rc/v2.11.0.1 (release candidate) · commercialhaskell/stack · GitHub .
-
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
-
How to suppress warnings from external packages?
Opened a ticket on GitHub.
-
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.
-
`Stack build` fails with `gcc' failed in phase `Assembler'
FYI this was solved in here: https://github.com/commercialhaskell/stack/issues/5958