-
Notifications
You must be signed in to change notification settings - Fork 0
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
Pick language and technology stack for the project #6
Comments
My proposition: Babel Language: ECMAScript 6 (newest version of JavaScript) Sample chrome extension using Babel: https://github.com/schovi/webpack-chrome-extension |
Language:
Build tool: Testing:
|
Some people consider coffee script to be less relevant in when they can use ES6 (source). Dart, on the other hand, seems to be an interesting idea. |
My proposition is ScalaJS with SBT - it's the technology I'd like to learn anyway. |
OK, so the final decision is Babel. |
What about build tool? Do we want to raise new issue for that? |
@balawama I did some digging and I think that WebPack will be sufficient as a build tool. So to summarise:
This issue is closed but I will create new issue to set up sample project with stub js file and sample test |
Not really my business but webpack has some serious issues with css sourcemaps . Thought I might save you the pain. webpack-contrib/style-loader#55 We switched to browserify which still is not perfect as debugging coffeescript in the browser stinks. (that was easier to handle in webpack) IE browserify problem. browserify/browserify#1233 Browserify/Webpack also integrates quite nicely into brunch.io as well. Also gulp works well with either too. But if you go gulp use 4.0 branch.. way easier. |
Hi @nmccready We will consider it when we finally find some time to work on the project. |
We need to pick technologies that we can use to build our plugin. Particularly we need to choose:
This story depends on the outcome of #5
The text was updated successfully, but these errors were encountered: