ijavascript VS quokka

As an enthusiast of JavaScript, I've always wanted to harness the potential of this environment for Node.js. To achieve this, I selected Jupyter Notebook - a leading open-source alternative. It enables in-browser code editing and execution, presenting computational outcomes. Moreover, it's adaptable, supporting an array of languages, inclusive of a Javascript command shell.

No need to wait, there is a Javascript kernel for Jupyter Notebook:

https://github.com/n-riesco/ijavascript

I used this for interactive debugging AWS API calls using the AWS Javascript SDK. It worked great!

Data pipeline? Believe it or not, Javascript

That'd be Jupyter notebooks - Obsidian has a community plugin here. So far it only supports python. You could be the one to contribute integration for the IJavascript kernel, or maybe the .NET Interactive kernel (which I'm interested in 😉)

For more features and details check out the official docs https://quokkajs.com/

Used to be true, but between Quokka.js for quick prototypes, Wallaby.js for running tests smartly within the IDE, and now Console Ninja which enables inline console.log within the VSCode while running servers for common tooling (webpack, vite). As well as continuously improving collaboration tools like Live Share, And it's become hard for me to find an argument that Webstorm is still better for productivity here.

I use https://quokkajs.com/ it has a free version!

There are some fantastic tools such as Quokka which make "more algorithmic" development very interactive and fun

There's also extensions like https://quokkajs.com/

Quokka.js

I’m a Clojure(script) dev learning TS. My Clojure REPL flow is Cursive + IntelliJ. The closest equivalent I’ve found is https://quokkajs.com for inline evaluation and https://wallabyjs.com for test evaluation. Both are paid products but have free 30 day evaluation periods. Both work in IntelliJ and VsCode.

If you want to code and practice your JS in a sandbox, I highly recommend using VS Code (if you're not already using that for your HTML/CSS) in conjunction with Quokka.js. If you use `console.log()` function to log your results, Quokka will output directly in the editor. There are online resources that do something similar like codesandbox.io but I've found it nice to have a local environment.