JavaScript Rising Stars 2017

I found an intersting article on the rising stars in the JavaScript world in 2017. There are the most important sections taken from the report.

Most Popular Projects Overall

Vue.js strikes again

Once again, Vue.js is the trendiest project of the year, with more than 40,000 stars added on GitHub during the year.

Front-end Frameworks

The Big-3: Vue, React and Angular

Without surprise, the 3 most popular UI frameworks are Vue.jsReact and Angular

Node.js Frameworks

Despite its age, Express was not only the trendiest node.js framework in 2017 but it’s also used as the backbone of many other frameworks or CMS, including FeathersKeystone or Nest.

React Ecosystem

In 2016 Create React App solved the problem of how to start coding a React application by providing a nice set of presets, very well packaged. Facebook keeps releasing new versions very often and it was by far the most popular project in 2017 among the React ecosystem.

Vue Ecosystem

Element and iView are the two most popular UI component kits, both focused on rapid desktop UI development. Mint UI and vux, on the other hand, are the two most popular mobile-focused UI kits.


JavaScript is so versatile that it can also be used to build mobile applications, meaning that you can share components between the web and the mobile platforms.

In this category, we find again the 3 main actors of the “Front-end frameworks”:


JavaScript has basic dynamic types but not static types. A lot of developers feel like they need types in their code, especially in big code base, to make it more robust and easier to read/understand.

And then, if you think you need types, the 2 main contenders are: TypeScript, provided by Microsoft and Flow, provided by Facebook (and used on their main projects: ReactReact NativeJest…)

Build Tools

It’s maybe the biggest surprise of the year, the trendiest building tool is Parcel, a brand new project that gathered more than 14,000 stars since the project was launched on GitHub in August.

Parcel offers all the goodies of modern web development with a killer feature: zero configuration!

Testing Frameworks

As we predicted last year (it’s the first time we predicted something right!), Jest became the trendiest testing framework in 2017.

IDEs & Editors

In 2016, VS Code, backed by Microsoft and Atom, backed by GitHub were really close at the top of the category.

They also led the way in 2017 but VS Code took a big advantage over its rival.

CSS in JavaScript

Styled Components was by far the trendiest project in this category this year. It lets developers include regular CSS syntax inside the React components, using a recent addition to the JavaScript language: tagged template literals.

Static Sites

Static site generators (or “SSG”) are tools that generate a bunch of .html, .css and JavaScript files that you can deploy on any web server without the fuss of setting up a database. Static web sites are fast, robust and easy to maintain.

Number 2 in 2016, Gatsby gets revenge in 2017. It comes with a lot of great features to optimize your static site:

  • Fast browsing & exporting
  • Aggressive preloading
  • Intelligent code splitting (templates + page data)

Gatsby uses React as the view layer and GraphQL to query the content at the building time. It has a strong community and React official web site itself is built with Gatsby.


Major companies such as the New York Times have started adopting GraphQL, and on the library front both Relay and Apollo (the two main GraphQL client libraries) released major updates this year.

This were the most important sections in this article.


Google Wave API combined with the Wookie engine and integrated in a Moodle platform

Wookie Moodle Google Wave

Everybody who is interesteded in Widget Mash-ups for Personal Learning Environments (PLEs) should take a look at this article posted on Scott Wilson’s Workblog. He demonstrates a very nice usage of the Google Wave API in combination with the Wookie engine integrated into a Moodle platform. Here is a part of his blogpost:

I’ve created a Moodle course that uses some widgets, all of which make use of the Wave Gadget API. Some of these are Google examples (converted to W3C format) and some are ones we’ve created.

To take a look, you need to head over to our Moodle sandbox and register yourself a profile (you’ll need to confirm your email address to activate the login). After that, go and enrol yourself on this course.

Feel free to play Sudoku, mess with the poetry magnets, use the chat, and vote in the polls. All these tools are Widgets, written entirely in regular HTML and JavaScript, and don’t use any PHP or any part of the Moodle platform they appear in other than using the context it supplies (the course ID in this case) and participant information (display name and avatar image); this means they can be embedded into any platform. Wave – the actual conversation engine – is the obvious one, but I think it makes sense to put live-updating collaborative applications into many different kinds of contexts – social networks, VLEs, blogs – anything with users and contexts.

In addition to the W3C Widgets API and Google Wave Gadgets API, the Wookie engine that renders the widgets also provides a moderator API, enabling admins to lock and unlock widgets. (However, test accounts are in the “student” role and so won’t see these controls)

The most interesting aspect of this demonstration is the combination of the Google Wave Gadget API with Moodle and the Wookie engine. The Wookie engine implements and even extends the W3C Widget Specification. Also the fact that all the Widgets are written entirely in regular HTML and JavaScript in order to be decoupled from the underlying Widget container (in this case Moodle) is an advantageous feature of this demonstration.

Google Wave combined with the Wookie engine implementing the W3C Widget API and integrated in a Moodle platform results in an interesting standardized Widget Mash-up system for learning environments.

Reblog this post [with Zemanta]