[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$f1fyezeita5ebr":3},{"code":4,"message":5,"data":6,"timestamp":52},10000,"success",{"full_name":7,"position":8,"description":9,"language":10,"stars":11,"forks":12,"stars_gained":13,"age_days":14,"hn_threads":15,"one_liner":31,"summary_md":32,"topic":33,"github_topics":36,"license":42,"homepage":43,"updated_at":44,"history":45},"JetBrains\u002Fintellij-community",10,"IntelliJ IDEA & IntelliJ Platform","Java",20658,6108,3,5503,[16,22,27],{"id":17,"title":18,"points":19,"comments":20,"posted_at":21},47805612,"IntelliJ IDEA and IntelliJ Platform and become open source",2,1,"2026-04-17",{"id":23,"title":24,"points":20,"comments":25,"posted_at":26},6440206,"JetBrains open sources its IntelliJ Community Edition IDE",0,"2013-09-24",{"id":28,"title":29,"points":20,"comments":25,"posted_at":30},13129059,"IntelliJ IDEA Community Edition","2016-12-08","Source for JetBrains IDEs, for people building plugins on the IntelliJ Platform or reading the IDE's internals.","This is JetBrains' own codebase, not a turnkey editor you install instead of IntelliJ IDEA. Its value is as a source of platform behavior and as the substrate for plugin development; treating it as a quick fork-and-ship starting point will disappoint.\n\n## The problem\nYou want to write an IntelliJ platform plugin, or you need to know exactly how a platform API behaves before relying on it. Documentation and forum answers leave gaps, and copying snippets from older plugin tutorials may not match the current master. Cloning the repo and opening it pulls the actual platform sources, so an API question becomes a code search rather than a guess. The result is a working platform build and a reference you can step through in the debugger.\n\n## What's different\nThis repository contains the open-source part of the JetBrains IDEs and is also the basis for IntelliJ Platform development, per the README. That means plugin authors can read the platform implementation directly and run the community IDE from source, rather than depending solely on published docs. The build is mid-migration to Bazel; the README says building with only the IDE's built-in capabilities is no longer supported, so the Bazel plugin becomes part of the workflow. Some tests still cannot run under Bazel and are directed to the `tests.cmd` script.\n\nThe trade-off is scale and churn. This is a large, long-lived codebase whose master branch targets the next major release, so code you read there may not match the version your plugin compiles against. The repo also needs the separate Android modules fetched by a script, and both repositories must be checked out to the same branch or tag.\n\n## Who should try it\nGood fit: a plugin developer debugging a platform behavior, or someone preparing a platform-level contribution, who benefits from stepping through real sources and from the documented test runner. Also reasonable for a developer who wants to build the community IDE and inspect the installer build options.\n\nPoor fit: someone who wants a lightweight open-source IDE to use daily, or who expects a simple clone-and-run experience. The Bazel dependency, the Android module fetch and the master-branch drift all add work that a user just wanting an editor does not need. Those users are better served by installing a released IntelliJ IDEA build.\n\n## Requirements and limitations\nOpening the sources requires IntelliJ IDEA 2026.1 or newer plus the Bazel plugin, according to the README, and the Maven path variable may need to be set. Building from the command line goes through `bazel-build-all-community.cmd`; installers come from `installers.cmd`. The separate Android modules must be fetched with the provided script, and the README stresses keeping the `intellij-community` and `android` repositories on matching branches or tags.\n\nOngoing upkeep matters more than initial setup: because master moves toward the next major version, code and build scripts can shift under you, and the README itself warns of migration rough edges around IDE integration. For plugin compatibility, verify the platform API against the build number range for the release you target rather than assuming master reflects it. A Docker-based environment is documented for building installer packages with preinstalled dependencies, and a shallow clone option reduces download size.\n\n## HotRepo's take\nHotRepo recorded this repository at 20,657 stars on 2026-10-24 (+5) and 20,658 on 2026-10-25 (+3), with two daily-board appearances in that span. That span is too short to judge any trend, and the repository dates to 2011, so the snapshots say little about momentum. Before investing time, check the [build number ranges](https:\u002F\u002Fplugins.jetbrains.com\u002Fdocs\u002Fintellij\u002Fbuild-number-ranges.html) against the IDE version your plugin targets, since master is aimed at the next major release.",{"slug":34,"name":35},"developer-tools","Developer Tools",[37,38,39,40,41],"code-editor","ide","intellij","intellij-community","intellij-platform","NOASSERTION","https:\u002F\u002Fjetbrains.com\u002Fidea","2026-10-25T03:21:17Z",[46,50],{"date":47,"stars":48,"stars_gained":49},"2026-10-24",20657,5,{"date":51,"stars":11,"stars_gained":13},"2026-10-25",1792918783]