PyCharm 2024.1 EAP 2 Is Out!
The second EAP build of PyCharm 2024.1 has landed and is now available for you to explore.
You can download this new build from our website, through the free Toolbox App, or via snaps for Ubuntu.
This new build introduces a reworked Terminal tool window and brings an ability to run or debug both client and server in a single npm configuration. Take a look!
Revamped Terminal tool window
PyCharm 2024.1 EAP 2 brings an overhauled terminal with both visual and functional enhancements to make terminal-based tasks simpler and more convenient. This update both improves the tool visually and expands its feature set.
The new Terminal tool window seamlessly integrates with the new UI, aligning it with the IDE’s refreshed look-and-feel, and it comes complete with a new color scheme that enhances readability.
One standout improvement is the presentation of each command in a distinct block. This makes it easy to identify the start and end of each one, enhancing the overall clarity of output. Easily navigate between blocks using the arrow keys or switch the focus between the prompt and output with the ⌘↑ / Ctrl + ↑ and ⌘↓ / Ctrl + ↓ keyboard shortcuts.
We introduced a convenient command history with filtering options, making navigation through recently executed commands a breeze.
The updated terminal supports only Bash, Zsh, and PowerShell (currently only for Windows 11). We are actively working on supporting more shell integrations.
Run or debug both client and server in a single npm configuration
You can now use the same npm configuration to run and debug both the server and client sides of your application. The new Browser / Live Edit tab in the Run/Debug Configurations editor allows you to set up a run configuration to open a browser automatically after launch. If needed, you can attach the debugger to the opened browser right away.
These are the most notable updates for this week. For the full list of the implemented changes, please consult the release notes.
Try out these new features and let us know what you think in the comments below or on X (formerly Twitter). If you encounter any bugs, please report them via our issue tracker.
Happy developing!