To make sure you never lose any of your work, Replit auto-saves your code as you write. If you ever lose an edit to your code that you'd like to recover, rewind back in time with File History.
Repls that are written in the following languages can use a built-in, multiplayer debugger:
You can find the current resource usage of your Repl in the bottom of the workspace sidebar. This includes the amount of RAM, CPU, and Storage currently being used by your Repl to run your code, the LSP, and other background services.
Secrets and Environment Variables
Sensitive information, such as credentials and API keys, must be kept secure. Keeping this information separate from your code helps to protect it from unauthorized access when you share your code with others.
Getting repl metadata
In some cases, it's useful to automatically retrieve metadata about a Repl from within that Repl. Your Repl's environment variables are pre-populated with some data that you can use. However, please avoid printing out the entirety of your Repl's environment variables in a public Repl, as it will expose any secrets you've added.
Multiplayer in Replit allows two or more users to code together in real-time.
With Inline Threads, you can make comments and discuss topics with collaborators directly in your code.
We believe computing is for everyone. Read our committment to accessibility here. Having trouble using Replit? Talk to us at [email protected]