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

Move to modern tekkers? #3

Open
larister opened this issue Jul 10, 2016 · 2 comments
Open

Move to modern tekkers? #3

larister opened this issue Jul 10, 2016 · 2 comments

Comments

@larister
Copy link

e.g. Webpack, ES6 etc

@larister larister changed the title Move to modern tekkers Move to modern tekkers? Jul 31, 2016
@orangespaceman
Copy link
Collaborator

I had a think about this, I don't think it's worth it. I like the idea that you can check out the project and run it straight in a browser without needing to touch the console or run a web server. It would be a shame to add extra barriers to entry.

@larister
Copy link
Author

Yeah I was of the same opinion; although we could just run webpack as a pre-commit hook to update the dist and keep it sans web server - not sure it's worth it though. We probably could broadly upgrade to ES6 if we wanted as we don't really have to support legacy browsers, but I don't think we should rewrite the whole codebase specifically - more allow people to use it if they wish.

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

2 participants