You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
One of the improvements of buildium was migrating from an ancient tarball of term.js to the npm-hosted xterm. Still, this package is three major versions behind the latest release of xterm. Rather than investing time to upgrade to xterm@latest, I want to question the integration of a terminal and suggest using one of the many existing terminal packages (e.g. atomic-terminal).
Motivation
I want to limit this package's features (and size) to its bare minimum - it should provide an API build providers can consume. There's no need to duplicate functionality, such as a terminal when there are packages that are better at this and more actively maintained. The biggest question for me is, how that allows keeping the existing functionality, e.g. the timer and the action buttons.
Describe alternatives you've considered
Upgrade xterm to v3 or later, ideally v4
The text was updated successfully, but these errors were encountered:
Summary
One of the improvements of
buildium
was migrating from an ancient tarball ofterm.js
to the npm-hostedxterm
. Still, this package is three major versions behind the latest release ofxterm
. Rather than investing time to upgrade toxterm@latest
, I want to question the integration of a terminal and suggest using one of the many existing terminal packages (e.g.atomic-terminal
).Motivation
I want to limit this package's features (and size) to its bare minimum - it should provide an API build providers can consume. There's no need to duplicate functionality, such as a terminal when there are packages that are better at this and more actively maintained. The biggest question for me is, how that allows keeping the existing functionality, e.g. the timer and the action buttons.
Describe alternatives you've considered
Upgrade
xterm
to v3 or later, ideally v4The text was updated successfully, but these errors were encountered: