xterm.js 3.0

This is an issue here to keep track of and discuss the candidate upcoming changes in xterm.js 3.0.

Tentative release date is set on the first Monday of November (6 Nov 2017), approx. 3 months after 2.9.0 to give us a fair amount of time to work on the breaking changes and 13 months after 2.0 to justify the new breaking changes 😁.

What’s in 3.0

🆕 Candidate features

• Support for true color (#484 and #756)
• Custom keybindings support (#487)
• Allow handling of custom escape codes (#576)
• State serialization, state loading and headless mode (#595, #613)

⚠️ Breaking changes (full list of issues)

• Drop Bower support (#406)
• Stop focusing automatically when opening the terminal in a DOM node (#646)
• Remove attachCustomKeydownHandler in favor of attachCustomKeyEventHandler (#744)

🛠 Internal improvements

• Migrate code base to TypeScript (#335)
• Switch to a CSS preprocessor (from https://github.com/sourcelair/xterm.js/issues/782#issuecomment-315015265)
• Buffer performance improvements (#791)

🎸 Interesting goodies

• Rebrand the website (https://xtermjs.org) with a dark theme to look more “terminal-y”
• Introduce an officially supported React component in a separate repo (#260)
• Incubate the xterm-terminal custom element: https://github.com/parisk/xterm-terminal

Notes

• All issues scheduled for this release should be available at the 3.0.0 milestone.
• All development will happen in the v3 release branch.

/cc @Tyriar to make sure you are on track with this.

[parisk]

@vincentwoo yep. It will be later today.

[Tyriar]

Closing this off as it’s pretty out of date at this point, so far the big focuses on v3 have been:

• The new canvas-based renderer and dealing with the fallout from that https://github.com/sourcelair/xterm.js/pull/938
• Making breaking changes that made sense https://github.com/sourcelair/xterm.js/issues?q=is%3Aissue+label%3Abreaking-change+milestone%3A3.0.0

All issues: https://github.com/sourcelair/xterm.js/milestone/8?closed=1