Skip to content

Commit

Permalink
Use xterm@1ec7b91
Browse files Browse the repository at this point in the history
  • Loading branch information
@chabou
chabou committed Feb 20, 2018
1 parent daa2880 commit 01e632b
Show file tree
Hide file tree
Showing 2 changed files with 4 additions and 4 deletions.
2 changes: 1 addition & 1 deletion package.json
View file
Original file line number Diff line number Diff line change
Expand Up @@ -194,7 +194,7 @@
"semver": "5.4.1",
"shebang-loader": "0.0.1",
"uuid": "3.1.0",
"xterm": "chabou/xterm.js#95178dd"
"xterm": "chabou/xterm.js#b9dac85"
},
"devDependencies": {
"ava": "0.24.0",
Expand Down
6 changes: 3 additions & 3 deletions yarn.lock
View file
Original file line number Diff line number Diff line change
Expand Up @@ -6653,9 +6653,9 @@ xtend@~2.1.1:
dependencies:
object-keys "~0.4.0"

xterm@chabou/xterm.js#95178dd:
version "3.0.0-hyper.1"
resolved "https://codeload.github.com/chabou/xterm.js/tar.gz/95178dddcb7c9e88b3a9444188789696b41788d1"
xterm@chabou/xterm.js#b9dac85:
version "3.0.0-hyper.2"
resolved "https://codeload.github.com/chabou/xterm.js/tar.gz/b9dac85cf33bdc19c31ac0ba223c5f2a3b11e6d2"

y18n@^3.2.1:
version "3.2.1"
Expand Down

2 comments on commit 01e632b

@saamalik
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@chabou just out of curiousity -- why not still use xterm: 3.1.0? Why do we need to just set a different version in xterm/package.json?

@albinekb
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Because it broke some of our CSS stuff, and we want to use unreleased features.. we will eventually fall back to using the published module when everything works as expected. @saamalik

Please sign in to comment.