cabal-install-parsers
strong-path
Our great sponsors
| cabal-install-parsers | strong-path | |
|---|---|---|
| 3 | 2 | |
| 425 | 14 | |
| -0.2% | - | |
| 7.3 | 0.0 | |
| 4 days ago | over 1 year ago | |
| Haskell | Haskell | |
| GNU General Public License v3.0 only | MIT 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.
cabal-install-parsers
-
[ANN] get-tested: A tool to generate a build matrix from your cabal file
This reminds me of haskell-ci, which also generates GH Actions workflows based on tested-with: (as well as further stuff), is there a comparison?
-
[ANN] Initial release of tasty-autocollect
ah, I see. Then I highly recommend you to use haskell-ci within Github actions. It catches cabal failures pretty well.
-
How do I figure out dependency version bounds for my library (when publishing on Hackage)?
If you're on github, I'd look at https://github.com/haskell-CI/haskell-ci , which generates a GH actions template from the tested-with: fields in the cabal file.
strong-path
-
[Request for Review] Tutorial on determining dependency version bounds
To support this with an example, executable with pinned dependencies would be https://github.com/wasp-lang/wasp/blob/master/waspc/package.yaml , while a library with loose dependencies would be https://github.com/wasp-lang/strong-path/blob/master/package.yaml .
-
How do I figure out dependency version bounds for my library (when publishing on Hackage)?
I wrote a strong-path package, which I published on Hackage. I am using Stack to build it: I have stack.yaml and package.yaml as sources of truth, while strong-path.cabal is generated by Stack but I also commit it into vcs.
What are some alternatives?
cabal-edit - A utility for managing Hackage dependencies and manipulating Cabal files from the command line.
haskell-handbook - Best practices on how to be efficient with Haskell in production
cabal-appimage - Cabal support for creating AppImage applications
aeson-schemas - Easily consume JSON data on-demand with type-safety
cabal-plan - Library and utility for processing cabal's plan.json file
semver - Semantic Versioning Specification
cabal-fmt - An experiment of formatting .cabal files
wasp - The fastest way to develop full-stack web apps with React & Node.js.
cabal-bundle-clib - [Moved to: https://github.com/IsumiF/cabal-bundle-clib]
cabal-cache - CI assistant
reactive-banana-gi-gtk - Functional Reactive Programming (FRP) with GObject Introspection in Haskell
hadolint - Dockerfile linter, validate inline bash, written in Haskell