[aerogear-dev] Adding ES6 to node sender

[Luke Holmquist]

hello,

I just created a JIRA for the node ups sender, https://issues.jboss.org/browse/AGJS-308, that tracks the addition of using ES6(the next version of Javascript).

My thoughts were to use the new features where ever possible.

Since not every feature is available on all versions of node, we would use Babel.js https://babeljs.io/ , to transpile that code back to ES5(the version before es6 :)). 

This transpilation would happen during an "npm publish" so users would never really see a difference.  

The cool thing about Babel is that we can specify which features we want transpiled,  so in the future this list of transpiled features would hopefully get smaller and smaller.

The latest versions of node have a lot of new features in them, so it would be nice to start coding that way.  For instance, this plugin, https://www.npmjs.com/package/babel-preset-node5  , is a preset for the features that node 5 has.  

wanted to get some thoughts on this.

-Luke

_______________________________________________
aerogear-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/aerogear-dev

[tolis emmanouilidis]

+1 on ES6 features & Babel JS

Do you plan to use ES6 promises or replacing the existing HTTP,HTTPS requests with something like https://www.npmjs.com/package/request-promise ?

I'd also like to see an AeroGear Sender "class" inside module by using ES6 class.

Thanks,

Tolis   

2016-01-29 20:10 GMT+02:00 Luke Holmquist <[hidden email]>:

hello,

I just created a JIRA for the node ups sender, https://issues.jboss.org/browse/AGJS-308, that tracks the addition of using ES6(the next version of Javascript).

My thoughts were to use the new features where ever possible.

Since not every feature is available on all versions of node, we would use Babel.js https://babeljs.io/ , to transpile that code back to ES5(the version before es6 :)). 

This transpilation would happen during an "npm publish" so users would never really see a difference.  

The cool thing about Babel is that we can specify which features we want transpiled,  so in the future this list of transpiled features would hopefully get smaller and smaller.

The latest versions of node have a lot of new features in them, so it would be nice to start coding that way.  For instance, this plugin, https://www.npmjs.com/package/babel-preset-node5  , is a preset for the features that node 5 has.  

wanted to get some thoughts on this.

-Luke

_______________________________________________
aerogear-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/aerogear-dev

_______________________________________________
aerogear-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/aerogear-dev

[Luke Holmquist]

On Mon, Feb 8, 2016 at 6:17 AM, tolis emmanouilidis <[hidden email]> wrote:

+1 on ES6 features & Babel JS

Do you plan to use ES6 promises or replacing the existing HTTP,HTTPS requests with something like https://www.npmjs.com/package/request-promise ?

i think the plan was to use Native promises.  while bluebird (which is what is the underlying promise implementation for that request-promise module) is a solid library, i'd like to stick to the spec. 

I'd also like to see an AeroGear Sender "class" inside module by using ES6 class.

baby steps :) 

Thanks,

Tolis   

2016-01-29 20:10 GMT+02:00 Luke Holmquist <[hidden email]>:

hello,

I just created a JIRA for the node ups sender, https://issues.jboss.org/browse/AGJS-308, that tracks the addition of using ES6(the next version of Javascript).

My thoughts were to use the new features where ever possible.

Since not every feature is available on all versions of node, we would use Babel.js https://babeljs.io/ , to transpile that code back to ES5(the version before es6 :)). 

This transpilation would happen during an "npm publish" so users would never really see a difference.  

The cool thing about Babel is that we can specify which features we want transpiled,  so in the future this list of transpiled features would hopefully get smaller and smaller.

The latest versions of node have a lot of new features in them, so it would be nice to start coding that way.  For instance, this plugin, https://www.npmjs.com/package/babel-preset-node5  , is a preset for the features that node 5 has.  

wanted to get some thoughts on this.

-Luke

_______________________________________________
aerogear-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/aerogear-dev

_______________________________________________
aerogear-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/aerogear-dev

_______________________________________________
aerogear-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/aerogear-dev

[tolis emmanouilidis]

Thanks Luke :)  

I was thinking to contribute some parts on that task. would you please share the branch when you start working on it?

2016-02-08 15:55 GMT+02:00 Luke Holmquist <[hidden email]>:

On Mon, Feb 8, 2016 at 6:17 AM, tolis emmanouilidis <[hidden email]> wrote:

+1 on ES6 features & Babel JS

Do you plan to use ES6 promises or replacing the existing HTTP,HTTPS requests with something like https://www.npmjs.com/package/request-promise ?

i think the plan was to use Native promises.  while bluebird (which is what is the underlying promise implementation for that request-promise module) is a solid library, i'd like to stick to the spec. 

I'd also like to see an AeroGear Sender "class" inside module by using ES6 class.

baby steps :) 

Thanks,

Tolis   

2016-01-29 20:10 GMT+02:00 Luke Holmquist <[hidden email]>:

hello,

I just created a JIRA for the node ups sender, https://issues.jboss.org/browse/AGJS-308, that tracks the addition of using ES6(the next version of Javascript).

My thoughts were to use the new features where ever possible.

Since not every feature is available on all versions of node, we would use Babel.js https://babeljs.io/ , to transpile that code back to ES5(the version before es6 :)). 

This transpilation would happen during an "npm publish" so users would never really see a difference.  

The cool thing about Babel is that we can specify which features we want transpiled,  so in the future this list of transpiled features would hopefully get smaller and smaller.

The latest versions of node have a lot of new features in them, so it would be nice to start coding that way.  For instance, this plugin, https://www.npmjs.com/package/babel-preset-node5  , is a preset for the features that node 5 has.  

wanted to get some thoughts on this.

-Luke

_______________________________________________
aerogear-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/aerogear-dev

_______________________________________________
aerogear-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/aerogear-dev

_______________________________________________
aerogear-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/aerogear-dev

_______________________________________________
aerogear-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/aerogear-dev

[Luke Holmquist]

On Mon, Feb 8, 2016 at 9:30 AM, tolis emmanouilidis <[hidden email]> wrote:

Thanks Luke :)  

I was thinking to contribute some parts on that task. would you please share the branch when you start working on it?

yea, no doubt,  that would be awesome.

 

2016-02-08 15:55 GMT+02:00 Luke Holmquist <[hidden email]>:

On Mon, Feb 8, 2016 at 6:17 AM, tolis emmanouilidis <[hidden email]> wrote:

+1 on ES6 features & Babel JS

Do you plan to use ES6 promises or replacing the existing HTTP,HTTPS requests with something like https://www.npmjs.com/package/request-promise ?

i think the plan was to use Native promises.  while bluebird (which is what is the underlying promise implementation for that request-promise module) is a solid library, i'd like to stick to the spec. 

I'd also like to see an AeroGear Sender "class" inside module by using ES6 class.

baby steps :) 

Thanks,

Tolis   

2016-01-29 20:10 GMT+02:00 Luke Holmquist <[hidden email]>:

hello,

I just created a JIRA for the node ups sender, https://issues.jboss.org/browse/AGJS-308, that tracks the addition of using ES6(the next version of Javascript).

My thoughts were to use the new features where ever possible.

Since not every feature is available on all versions of node, we would use Babel.js https://babeljs.io/ , to transpile that code back to ES5(the version before es6 :)). 

This transpilation would happen during an "npm publish" so users would never really see a difference.  

The cool thing about Babel is that we can specify which features we want transpiled,  so in the future this list of transpiled features would hopefully get smaller and smaller.

The latest versions of node have a lot of new features in them, so it would be nice to start coding that way.  For instance, this plugin, https://www.npmjs.com/package/babel-preset-node5  , is a preset for the features that node 5 has.  

wanted to get some thoughts on this.

-Luke

_______________________________________________
aerogear-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/aerogear-dev

_______________________________________________
aerogear-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/aerogear-dev

_______________________________________________
aerogear-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/aerogear-dev

_______________________________________________
aerogear-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/aerogear-dev

_______________________________________________
aerogear-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/aerogear-dev