Built static site

Signed-off-by: Dimitris Kolovos <dimitris.kolovos@york.ac.uk>

Author: kolovos

playground/dist/bundle.js

@@ -36,6 +36,8 @@ class Panel {
             // folding: false
         });
 
+        // Fix the editor's end-of-line character to avoid issues with live
+        // sharing across different operating systems
         this.editor.getModel().setEOL(monaco.editor.EndOfLineSequence.LF);
 
         this.visible = true;

playground/dist/bundle.js.map

@@ -166,9 +166,7 @@ export class MonacoBinding {
     {
       const ytextValue = ytext.toString()
       if (monacoModel.getValue() !== ytextValue) {
-        const eol = monacoModel.getEndOfLineSequence();
         monacoModel.setValue(ytextValue)
-        monacoModel.setEOL(eol);
       }
     }
     this._monacoChangeHandler = monacoModel.onDidChangeContent(event => {

playground/js/Panel.js

@@ -1832,7 +1832,7 @@ <h2 id="running-yjs-locally">Running YJS locally<a class="headerlink" href="#run
 <li><code>HOST=localhost PORT=1234 npx y-websocket</code></li>
 </ul>
 <h2 id="y-monaco">y-monaco<a class="headerlink" href="#y-monaco" title="Permanent link">&para;</a></h2>
-<p><code>y-monaco.js</code> is a local copy of a <a href="https://github.com/kolovos/y-monaco/blob/master/src/y-monaco.js">forked version</a> of the <code>y-monaco</code> package. The original package suffers from two issues (<a href="https://github.com/yjs/y-monaco/issues/6#issuecomment-2163299125">#1</a> and <a href="https://github.com/yjs/y-monaco/pull/23">#2</a>) that have been fixed in the fork. The fixes have been proposed by others to the package maintainer however, they have not been accepted yet. Once the fixes are accepted by the package maintainer, we can use the npm package again.</p>
+<p><code>y-monaco.js</code> is a local copy of a <a href="https://github.com/kolovos/y-monaco/blob/master/src/y-monaco.js">forked version</a> of the <code>y-monaco</code> npm package. The original package suffers from <a href="https://github.com/yjs/y-monaco/pull/23">an issue</a>) that has been fixed in the fork. The fix has been proposed by others to the package maintainer however, it has not been accepted yet. Once the fix is accepted, we can use the npm package again.</p>