Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Remove Router from core?
See original GitHub issueHello!
Just looking through HyperApp and I am very impressed! 👍 I am just wondering why Router is in the core package that everyone downloads because it’s just a plugin. Wouldn’t it be better to separate Router from core and put Router and similar plugins elsewhere? It’s just a question, as I was wondering about community plugins/extensibility. E.g. The core hyperapp repo is just h and app and Router and other similar plugins could be in other repos and the user could choose which one they install alongside hyperapp.
npm install hyperapp
npm install hyperapp-router
...
What do you think?
Issue Analytics
- State:
- Created 6 years ago
- Reactions:9
- Comments:20 (12 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
@lukejacksonn You dropped something: \
@Facel3ss1 we thought about this a lot. Main reason is primarily that this doesn’t have any major disadvantages, while it maintains the “one system” aspect of hyperapp.
Look at react, there are 20 different routers, 20 different state manangement libraries and they don’t integrate nicely with each other. Hyperapp (while not forcing you to use our router) gets rid of most of these problems by providing it out-of-the-box.