diff --git a/_includes/head.html b/_includes/head.html index 078f901..cb8d4e0 100644 --- a/_includes/head.html +++ b/_includes/head.html @@ -12,4 +12,16 @@ + \ No newline at end of file diff --git a/_posts/2016-10-03-xtermjs-2.0.md b/_posts/2016-10-03-xtermjs-2.0.md new file mode 100644 index 0000000..4ba9fcf --- /dev/null +++ b/_posts/2016-10-03-xtermjs-2.0.md @@ -0,0 +1,44 @@ +--- +title: Announcing xterm.js 2.0 +author: parisk +categories: xtermjs update +--- + +We are excited to announce a new major update for xterm.js; **xterm.js 2.0**! This new release includes the following great updates: + +1. Launch of official project website with [public API docs](/docs/) and [blog](/blog/) +2. Migration of code base to ES2015 modules to make development much easier +3. Significant features and improvements + +Let's take a quick look on each one of this updates. + +## Project website +Xterm.js definitely deserved it's own place in the web, so we gifted [xtermjs.org](http://xtermjs.org) to it! Here you can find the official [docs](/docs/) for the public API of the project, including some high-level guides and a [blog](/blog/), where we will post articles about xterm.js, like releases, presentations, engineering etc. + +**⚠️ Attention:** From now on, our public API is only the one documented in [http://xtermjs.org/docs/](http://xtermjs.org/docs/). Any other attributes, methods or events that you might be relying in previous versions should not be considered stable and might change without notice! + +## Migration to ES2015 +Xterm.js used to be a huge monolith and it was a real pain to work on, especially when dealing with core parts like rendering. We decided to take a big step forward, break the code base into multiple native ES2015 modules and ship xterm.js as a [UMD](https://github.com/umdjs/umd) monolith which can be imported using either native modules, CommonJS, RequireJS or no module system at all! + +This will allow us to develop xterm.js faster, with less hassle and friction and at the end ship a better open source project to the world. + +### ⚠️ Migrating from xterm.js 1.0 to 2.0 +Since this is a major xterm.js release, we had to break our public API because of this update, so take a look here before migrating! + +The only thing that you have to take into account when migrating from xterm.js 1.0 to 2.0 is importing the appropriate files. The xterm.js core is not stored as two built files (one JavaScript and one CSS) into the `dist` directory of the code base (instead of `src`, where they used to be). + +To learn more about how to import xterm.js properly into your project, take a look at the [Importing](/docs/guides/import/) documentation page. + +**Note**: If you are importing xterm.js using CommonJS, there should be nothing to change there, since we updated the package.json file of the project accordingly. + +## Features and improvements +Xterm.js 2.0 ships with a few great improvements: + +- New APIs to [get](http://xtermjs.org/docs/api/Terminal/#getoptionkey) and [set](http://xtermjs.org/docs/api/Terminal/#setoptionkey-value) terminal options +- New API to [clear](http://xtermjs.org/docs/api/Terminal/#clear) terminal +- Better mouse and mouse wheel support +- Improved scrolling in oh-my-zsh + +As always, this release could not be made possible without the contribution of our [**amazing contributors**](https://github.com/sourcelair/xterm.js/blob/2.0.1/AUTHORS), so **THANK YOU** for making this happen! + +Xterm.js 2.0 is available at [npm](http://npmjs.org/package/xterm), [bower](https://bower.io) and [GitHub Releases](https://github.com/sourcelair/xterm.js/releases/tag/2.0.1) as usual, so go get it and create amazing terminal apps now! \ No newline at end of file