Tools like Plunker, JSBin, or Codepen have been around for a long time, so why is Codesanbox a better the best choice?
1. Codesandbox has the functionality for collaborative coding
This project created by the Dutch guy Ives van Hoorne has a collaborative coding mode to work together on code-files like we are used to with Google docs. This feature comes with a lot of options: You can, for example, make files read-only during a part of your workshop.
2. Create a folder structure to organize your projects for yourself and your team
In each feature of this open-source project, you can see the focus on collaboration for developers. With your own dashboard, you can organize your project structure for your teams and team-members.
3. Complete Github-integration to version your code.
Version control is very important these days for your project. Especially if you want to collaborate. With the Github-integration you can easily make pull-requests or create new repo’s.
4. Develop, test and deploy your server-side rendered web-application in the browser
Experimenting with code is always a pleasure, but server-side rendered web-application are becoming bigger and more complex. To develop and deliver decent software you have to test your code. With the Jest integration in Codesanbox, you are able to test your code in the browser. Below you see an example which I’ve found with the search in Codesandbox. It shows a basic vue-cli project with some unit tests.
5. Support for node.js app development
For productivity on development, I think most developers still prefer their own local development environment. Especially when you know your IDE and all their short-cuts. But if you are experimenting, preparing a workshop, writing a blog post? Codesandbox is the way to go. It helps you to focus on what matters and I think that focus has slipped away last years in the front-end.