sandpack VS shell-driver

For us at CodeSandbox, we stand by it as a company but also as individuals. We released our browser editor, Sandpack, and parts of Nodebox as open source and we want to give back any time we can!

If you have any suggestions on how we can improve Sandpack, feel free to open an issue on GitHub. And if you have added Sandpack to our docs, we’d love to see the result—tweet it @CodeSandbox.

Sandpack? From codesandbox? https://sandpack.codesandbox.io/

As for the portal itself then I was thinking of making another post that explains how the site is built. But sandpack by codebox is the standard solution for live code execution.

https://sandpack.codesandbox.io/ Sandpack is what they're using. Go check out the docs, and I'm sure there's plenty of tutorials if you search it up

Create a new file in the codesandbox/sandpack/sandpack-themes/src folder with the following name [myAwesomeTheme].ts

Hi, Can anyone please let me know what this type of animation is called? Is it a type of Parallax effect or something else? Thanks. Reference: https://sandpack.codesandbox.io/ (Top section)

Danilo: Yes, we've been working hard to bring more optimizations to Sandpack, both on the React package (such as SSR improvements, lazily loading heavy dependencies, and removing redundant code) and in the bundler side too (you can find more details here: https://github.com/codesandbox/sandpack/issues/295).

I needed a way to document my shell scripts (or code snippets) and to quickly replace “parameters”. For example, if you want to download a YT video as mp3, you have to remember this command “youtube-dl --extract-audio --audio-format mp3 ” . You can use the autocomplete & history in the terminal but you still have to remember parts of the command and replace the old URL with the new one. You can also save it in a text file, and replace … too many select/replace/copy/paste ops…

A few months ago I made a good enough solution for my problem https://github.com/alexadam/reactive-doc - it saves ~ 10 minutes/day when I have to run complex devops scripts. And I can quickly share the ‘docs’ because they are just plain html files / or markdown.

Now I just finished the next iteration - better ‘syntax’ for input widgets, runnable @shell commands and a web based terminal https://github.com/alexadam/shell-driver with custom filters and selection actions (useful for me)

Next steps: add more features to the web based terminal -> convert history to scripts, autocomplete with parameters, command palette & context aware menus, multiple terminals (with tabs or panels). I also want to add support for React components in the MD editor.