Skip to content
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

Decide on a router #1

Open
lastmjs opened this issue Aug 20, 2018 · 1 comment
Open

Decide on a router #1

lastmjs opened this issue Aug 20, 2018 · 1 comment

Comments

@lastmjs
Copy link
Member

lastmjs commented Aug 20, 2018

I've crossed the Vaadin router off the list, as it is just missing basic features. Skate's router might be really good once they fully support es modules (get rid of page.js or somehow compile it to es modules). The ion-router might be a good choice too, looking into that

@lastmjs
Copy link
Member Author

lastmjs commented Sep 5, 2018

I think I'm going to stick with Zwitterion and no bundling. Bundling just has too many fallbacks or issues, and I think it's worth it (hopefully) to keep living in the future. There is just one dependency that skate has that I'll need to fix. The problem is with other libraries that continue to not be written in es modules, or that haven't upgraded yet. But, I think I have a good solution for that that requires minimal work, and can be undone in the future easily. Just create a rollup bundled es module output, and throw that up on npm until the day comes that the original library is rewritten. Zwitterion I believe has a future yet, it's just too simple to use to not be worthwhile.

Check it out, they're working on it: visionmedia/page.js#499

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant