For coders
Build a project
A project is what a single run is not: named, saved to your account, and there when you come back. It is also where more than one file becomes possible.
More than one file
Once a program has a second file, put it in a project rather than pasting everything into one. Imports and includes then work the way they do anywhere else, which is usually the point at which a snippet stops being a snippet.
Libraries
External libraries are added by the coordinate your ecosystem already uses, rather than by a JDoodle-specific name:
| Ecosystem | What you type |
|---|---|
| Maven | org.apache.commons:commons-lang3:3.4 |
| npm | lodash:4.17.21 |
| pip | pandas |
| NuGet | Newtonsoft.Json |
| pacman | boost |
The editor shows what you have added, so a project carries its dependencies with it rather than depending on what happened to be installed.
Keeping them straight
My Projects lists everything you have saved, filtered by language and searchable by name. Name things for what they are rather than what they were when you started. It is much easier to find "generics" later than "test2".
What next
If what you are building needs a server, a package manager you drive yourself, or a database, none of that lives in a project. It lives in an environment.
Multi-file projects and libraries cover the project side in detail.