Libraries to create
lpil opened this issue · 6 comments
lpil commented
- JSON
- toml
- HTTP types
- Bindings to Erlang web servers
- Elli
- Cowboy
- PostgreSQL client
- SQLite client
- MariaDB / MySQL client
- Password hashing
- Dates + times
- Currency
- Email construction and sending
- SMTP
- Various email sending APIs
- Easy to use Gleam based HTTP client
- Out of the box TLS verification
- HTTP 1
- HTTP 2
- Websockets
- Manipulates Erlang socket directly to avoid excess data copying between processes
- Optional connection pooling
- Gleam based HTTP server
- HTTP 1
- HTTP 2
- HTTP 3
- Websockets
- Performance competitive with Cowboy
- Bindings to the Erlang telemetry library
- Binding to Erlang's TCP modules
- Gleam HTTP CORS
- Gleam HTTP cookies
- CSRF protection
- Signing
- Encryption
- GraphQL server
- GraphQL client
- JSON RPC
- Command line options parsing
- Fuzz testing
- Snapshot testing
- Property testing
- Random value generation
- Temporary files
- CSV (https://github.com/BrianHicks/elm-csv)
- JS DOM bindings
- JS VDOM
- JavaScript HTTP server adapter for the Gleam HTTP library
- XML parsing
- HTML parsing
- ical parsing + generation
- Type safe postgresql client using codegen (launchbadge/sqlx#1925)
- S3 client
- Redis client
- MeiliSearch client
- Logging
- Metrics collection
- Convention based web framework
- Generic pattern for collecting multiple errors (https://hackage.haskell.org/package/monad-validate-1.2.0.1/docs/Control-Monad-Validate.html)
dropwhile commented
Some other libraries that might be useful to have:
- base32, base64
- protocol buffers
- twirp rpc
lpil commented
Twirp is so cool! I'd love to see that
lpil commented
I'm gunna close this as the ecosystem has matured a lot and folks can work out what they need themselves
nohehf commented
I think this (maybe in a GitHub wiki tho) is still useful, to coordinate efforts ? WDYT ?
David-Klemenc commented
To build Open Api library like open_api_spex a JSON schema library would be useful.
lpil commented
Agreed!