eiac/xterm.js
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 1 Wiki Activity

Use jsdoc/multiline-blocks instead of multiline-comment-style

Browse Source 
Replace multiline-comment-style (starred-block), which also forces
multiline // comments into block comments, with jsdoc/multiline-blocks.
That rule only enforces starred JSDoc layout for /** blocks (no text on
the opening line) and leaves multiline // comments unchanged for
internal documentation.

Fix multiline JSDoc in Types.ts.

Fixes #5899

Co-authored-by: Daniel Imms <Tyriar@users.noreply.github.com>
This commit is contained in:
Cursor Agent
2026-05-26 20:32:23 +00:00
co-authored by Daniel Imms
parent 4ec85e67ba
commit df3422fb0b
138 changed files with 1834 additions and 3028 deletions
Download Patch File Download Diff File Expand all files Collapse all files
demo/server/server.ts
+5 -9
View File
@@ -180,11 +180,9 @@ function startServer(): void {
}
const send = (USE_BINARY ? bufferUtf8 : buffer)(ws, 3, 262144);
/*
* WARNING: This is a naive implementation that will not throttle the flow of data. This means
* it could flood the communication channel and make the terminal unresponsive. Learn more about
* the problem and how to implement flow control at https://xtermjs.org/docs/guides/flowcontrol/
*/
// WARNING: This is a naive implementation that will not throttle the flow of data. This means
// it could flood the communication channel and make the terminal unresponsive. Learn more about
// the problem and how to implement flow control at https://xtermjs.org/docs/guides/flowcontrol/
term.onData(function(data) {
try {
send(data as string & Buffer);
@@ -211,10 +209,8 @@ function startServer(): void {
app.listen(port, host, 0);
}
/*
* HACK: There is an EPIPE error thrown when reloading a page. This only seems to happen on Windows
* and it's unclear why it happens. Suppressing the error here since this is just the demo server.
*/
// HACK: There is an EPIPE error thrown when reloading a page. This only seems to happen on Windows
// and it's unclear why it happens. Suppressing the error here since this is just the demo server.
process.on('uncaughtException', (error) => {
if (process.platform === 'win32' && error.message === 'read EPIPE') {
return;