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

Pick language and technology stack for the project #6

Closed
nejdaw opened this issue Oct 16, 2015 · 9 comments
Closed

Pick language and technology stack for the project #6

nejdaw opened this issue Oct 16, 2015 · 9 comments
Assignees
Milestone

Comments

@nejdaw
Copy link
Contributor

nejdaw commented Oct 16, 2015

We need to pick technologies that we can use to build our plugin. Particularly we need to choose:

  • language
  • build tool
  • testing framework (unit / system tests)

This story depends on the outcome of #5

@nejdaw
Copy link
Contributor Author

nejdaw commented Oct 23, 2015

My proposition: Babel

Language: ECMAScript 6 (newest version of JavaScript)
Build tool: WebPack
Compiler: Babel (compiles ECMAScript 6 to ECMAScript 5)
Testing framework: Mocha, Karma

Sample chrome extension using Babel: https://github.com/schovi/webpack-chrome-extension

@balawama
Copy link
Contributor

@nejdaw
Copy link
Contributor Author

nejdaw commented Oct 24, 2015

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.

@mkordas
Copy link
Contributor

mkordas commented Oct 24, 2015

My proposition is ScalaJS with SBT - it's the technology I'd like to learn anyway.

@nejdaw
Copy link
Contributor Author

nejdaw commented Oct 26, 2015

OK, so the final decision is Babel.

@balawama
Copy link
Contributor

What about build tool? Do we want to raise new issue for that?

@nejdaw
Copy link
Contributor Author

nejdaw commented Oct 26, 2015

@balawama I did some digging and I think that WebPack will be sufficient as a build tool. So to summarise:

  1. Runtime environment: node.js
  2. Compiler: babel
  3. Build tool: webpack
  4. Tests: lets start with Mocha and then replace it if something is wrong

This issue is closed but I will create new issue to set up sample project with stub js file and sample test

@nmccready
Copy link

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
webpack-contrib/css-loader#29

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.

https://www.npmjs.com/package/browserify-brunch

@nejdaw
Copy link
Contributor Author

nejdaw commented Nov 4, 2015

Hi @nmccready
Thanks for contribution!

We will consider it when we finally find some time to work on the project.

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

4 participants