IDE
Libraries and dependencies
External libraries are added per project, using the identifier the language's own ecosystem uses. There is no JDoodle-specific package name to look up.
Which languages support libraries
Twenty-three languages can install external libraries. Each uses its own package manager, and you type the name in that manager's usual format.
| Language | Package manager | Example |
|---|---|---|
| Java, Scala, Groovy, Kotlin | Maven | org.apache.commons:commons-lang3:3.4 |
| NodeJS, Typescript | npm | lodash:4.17.21 |
| Python 2, Python 3 | pip | pandas |
| C#, VB.Net | NuGet | Newtonsoft.Json |
| PHP | Composer | markrogoyski/math-php |
| Perl | CPAN | DateTime@1.65 |
| Ruby | RubyGems | faker:2.18.0 |
| R Language | CRAN | dplyr |
| Dart | pub | advance_math |
| Lua | LuaRocks | lua-zlib |
| Swift | Swift | gsl |
| C | Arch package | pcre |
| C-99 | Arch package | gsl |
| C++, C++ 14, C++ 17 | Arch package | boost |
| Bash Shell | Arch package | jq |
If your language is not listed, it has no library support in the editor. In a framework or database environment you install packages yourself from the terminal instead.
Per project, not per account
Libraries belong to the project that declared them. Copying code into a new project does not bring them along, which is the usual reason something that ran a minute ago stops compiling.
Where it is unavailable
Not every language has an ecosystem we install from. Where there is none, the library control is absent, and in an environment you install packages yourself from the terminal instead, which is a different and less restricted route.
What next
Saving, naming and sharing are what turn a project into something you can hand to somebody.
Supported languages lists every language that takes libraries, and where its packages come from.