-
Notifications
You must be signed in to change notification settings - Fork 780
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Logger middleware, middleware composer, and router #918
Comments
Maybe create a PR to https://github.com/jorgebucaran/awesome-hyperapp ? |
Because of hyperapp minimalistic design almost every hyperapp developer writes something similar - here is my hyperapp-middlewares package and router :), imo, even though there are many different packages from developers, they shouldn't be pushed into the core - hyperapp core should stay as it is without any additional functionality |
@frenzzy props for reminding us about awesome-hyperapp. That really needs a complete refresh or a big fat disclaimer though. All of it as far as I can tell is v1 related. Should we start a new one? Or is that what the upcoming “ecosystem” page on the website is for @jorgebucaran? |
I think a PR to awesome-hyperapp is better than nothing for now! 💯 Thank you, @chrisdavies! |
Will do... after I tidy up the packages a bit more! |
I put together a few tools to help with my current hyperapp project.
hypermiddleware is a middleware logger similar to redux-logger, and a middleware composer (allowing you to write N middleware functions, and then easily compose them into a single middleware function).
hyperoute is a router.
If you'd like to incorporate any of these into the core libs, I'm happy to open PRs for that, and then maintain these moving forward. Otherwise, feel free to close this issue!
Thanks for hyperapp!
The text was updated successfully, but these errors were encountered: