JS Bin VS JupyterLab

JS Bin is one of the useful JavaScript debugging tools designed for developers working with HTML, CSS, and JavaScript. It gives them the opportunity to test and debug their code snippets in a real-world setting. The fact that this tool is open-source is fantastic.

If I paste both in jsbin.com, the both show all content on 1 line.

A running example in https://jsbin.com/ might be easier to help with

JSBin : Front end playground, Output is not framed, so it allows you to share those snippets that will break inside an iframe.

> What if you want introduce some diagramming or Latex rendering in your blog ?

Then you are starting to step beyond what I was referring to as “a simple blog” (text, formatting, maybe some pictures or SVG).

Though there are options that don't require a CI/CD pipeline. Depending on what Latext you need MathJax may do the trick (just include the JS in your standard page header, and drop the Latex code straight in inline where needed as per their standard example: https://jsbin.com/?html,output. There are similar charting options like mermaid too. I don't know of inline charting options off the top of my head but I expect several exist.

Post your code on codesandbox.io or jsitor.com or jsbin.com or jsfiddle.net or whatever other site you prefer. Then we can look at it and see what is wrong. Otherwise, it's like showing us a picture of your cat and asking whether we think you might be allergic to it.

Important note: do not perform tests with WeakRefs in dev tools. Your objects won't be GCed in it due to DevTools specific behaviour. Instead, use jsbin, codesandbox, runkit or perform tests in Node.js. Localhost is okay when you open files using http:// protocol, as file:// also has specific behaviour.

https://jsbin.com/ (Type in the code; press go)

Does this allow to run a long running task in the background so that a user can close & reopen the tab and continue seeing all the output that has been produced thus far?

This is currently being worked on in Jupyter: https://github.com/jupyterlab/jupyterlab/pull/15448

This is a problem with codemirror 6. You can upvote https://github.com/jupyterlab/jupyterlab/issues/14589 and help by contributing (or sponsor someone to do so)

https://github.com/jupyterlab/jupyterlab/issues/12422

That whole issue feels so stupid.

I quite enjoy jupyter lab otherwise, even if a lot of it is brittle and annoying.

Could you add your details to https://github.com/jupyterlab/jupyterlab/issues/14625 it seems like a browser specific kssue

This will be possible in JupyterLab 4.0 and Jupyter Notebook 7 to be released in Q2/Q3 this year, see https://github.com/jupyterlab/jupyterlab/pull/13285

The posted SO is irrelevant. The true answer is that a new dependency included in 3.6 did not have binaries for some platforms. These were now uploaded so after refreshin pip cache you should be good to go. If it still does not work please post details in https://github.com/jupyterlab/jupyterlab/issues/13920

After a quick look I found the same issue here.

Yes, Jupyter notebook has used CodeMirror for nearly a decade. The official Jupyter notebook has never used Monaco, but the Google version (colab) uses Monaco in order to very nicely leverage LSP support (similar to VS Code). There is preliminary work under way right now to switch from CodeMirror 5 to CodeMirror 6 in the official Jupyter project, but that's going to be significant work (see https://github.com/jupyterlab/jupyterlab/pull/11638).

It doesn't seem like there is much overlap between Replit and Jupyter notebooks right now, as far as I can tell...

With the support of a team member with prior experience auditing for accessibility, we pinpointed specific ways in which JupyterLab lacked support for accessibility broken up by WCAG 2.1 standards.