Jetbrains products are professional tools and they are meant for professional users. The first time i made an electron app with more than 2000 lines of code was when i realized that vscode wasn't practical in large applications, but if your are just making some basic HTML5 project you're probably better off.

• Phpstorm Electronico
• Webstorm Electron 调试

• Making full screen effects with electron. The image is compressed and looks ugly. Using phpstorm to develop in wsl2 under windows, modifying wsl2.
• Hey I use WSL2 and PHPStorm daily for work. So far I have found the absolute easiest setup so far (on going journey!) is keeping your git repositories in a WSL2 Distro I use Ubuntu 20.04. Then use that as your main environment, either creating a container off it using docker, or I setup Symfony CLI, PHP and Composer inside Ubuntu itself.

Features

Don't Compromise
on the Development Experience

The smartest editor

Use the full power of the modern JavaScript ecosystem – WebStorm’s got you covered! Enjoy the intelligent code completion, on-the-fly error detection, powerful navigation and refactoring for JavaScript, TypeScript, stylesheet languages, and all the most popular frameworks.

Mobile

• Ionic
• Cordova
• React Native

• Electron

Debugger

Debug your client-side and Node.js apps with ease in the IDE – put breakpoints right in the source code, explore the call stack and variables, set watches, and use the interactive console.

Debugger

Debug your client-side and Node.js apps with ease in the IDE – put breakpoints right in the source code, explore the call stack and variables, set watches, and use the interactive console.

Seamless tool integration

Take advantage of the linters, build tools, test runners, REST client, and other tools, all deeply integrated with the IDE. But any time you need Terminal, it's also available as an IDE tool window.

Unit testing

Run and debug tests with Karma, Mocha, Protractor, and Jest in WebStorm. Immediately see test statuses right in the editor, or in a handy treeview from which you can quickly jump to the test.

Integration with VCS

Use a simple unified UI to work with Git, GitHub, Mercurial, and other VCS. Commit files, review changes, and resolve conflicts with a visual diff/merge tool right in the IDE.

What’s New in WebStorm 2021.1

Smarter completion for JavaScript

ML-assisted completion for JavaScript and TypeScript is now enabled by default. Additionally, suggestions for symbol names have become a bit smarter.

Improvements for HTML and CSS

A built-in HTML preview, better support for Stylelint, and details about selector specificity in CSS will help you work more productively.

Usability enhancements

This version is packed with new settings for choosing editor font weight, the ability to maximize tabs in the split view, and fixes for a lot of known issues.

Why WebStorm

Get up and running quickly

Start working on your projects immediately instead of wasting time juggling multiple plugins. With a variety of built-in developer tools and out-of-the-box language and framework support, there’s everything needed for productive JavaScript development.

Increase your productivity

Don’t spend your time going back and forth between the terminal and text editor or on things that can be automated with the help of refactorings and quick fixes; it’s what the IDE is best at. It puts the most critical developer tools like the debugger and Git at your fingertips.

Write better code with less effort

Write cleaner and more reliable code as the IDE runs dozens of inspections as you type and promptly detects potential errors and redundancies. Save time exploring the code base with autocompletion that suggests which variables and methods are most relevant in the current context.

Swiftly find what you need

Get around your code faster regardless of how large your projects are. Jump to the definition for any class, function, method, variable, or component and find its usages in just a few clicks. Easily navigate through the file you have opened with an at-a-glance view of its structure.

Tailor the look and feel to your liking

Don’t feel like using the defaults? Adjust the appearance and behavior of the IDE by playing around with themes, code styles, plugins, and more, so that it fits your unique needs better. You can also automatically share your custom settings between different instances of WebStorm.

Join our customers

Teams all over the world use WebStorm. Join them and get the best development experience

What our customers say

Installation

Project Goals

The goal of the project is to create a beautiful and extensible experience for command-line interface users, built on open web standards. In the beginning, our focus will be primarily around speed, stability and the development of the correct API for extension authors.

In the future, we anticipate the community will come up with innovative additions to enhance what could be the simplest, most powerful and well-tested interface for productivity.

Extensions

Extensions are available on npm. We encourage everyone to includehyper in the keywordsfield in package.json.

Then edit .hyper.js and add it to plugins

Hyper will show a notification when your modules are installed to .hyper_plugins.

Keymaps

All command keys can be changed. In order to change them, edit.hyper.js and add your desired change to keymaps.

Then Hyper will change the default with your custom change.

Example: 'window:devtools': 'Cmd+Alt+O'

Default keymaps:

Configuration

Config location

Note: config at ~/.hyper.js still supported, but will be ignored, if config in application directory present. Otherwise it will be moved to the application directory at first run.

The config object seen above in.hyper.js admits the following

Extensions API

Extensions are universal Node.js modules loaded by both Electron and the renderer process.

The extension system is designed around composition of the APIs we use to build the terminal: React components andRedux actions.

Instead of exposing a custom API method or parameter for every possible customization point, we allow you to intercept and compose every bit of functionality!

The only knowledge that is therefore required to successfully extendHyper is that of its underlying open source libraries.

You can find additional details about plugin developmentin the Hyper repository.

Your module has to expose at least one of these methods:

Module loading

The user can hot-load and hot-reload plugins by pressing Command + R (refresh). Please strive to make plugins that don't require a complete restart of the application to work.

Notice

Plugins affecting the `BrowserWindow` will the effect on new windows after hot-reload.

In the future we might do this automatically.

When developing, you can add your plugin to.hyper_plugins/local and then specify it under the localPlugins array in.hyper.js. We load new plugins:

• Periodically (every few hours)
• When changes are made to the configuration file (plugins or localPlugins)
• When the user clicks Plugins > Update all now

The process of reloading involves

• Running npm prune and npm install in.hyper_plugins.
• Pruning the require.cache in both electron and the renderer process
• Invoking on* methods on the existing instances and re-rendering components with the fresh decorations in place.

Plugins location

Note: plugins at ~/.hyper_plugins still supported, but will be ignored, if plugins in application directory present. Otherwise they will be moved to the application directory at first run.

Note: on the main process, plugins are registered as soon as possible (we fire onLoad). On the browser, it's up to the user to trigger their load by pressing command+R. We put the user in control of the loading in this way to prevent them from losing critical work by extensions that reset state or don't preserve it correctly.

Decorating components

We give you the ability to provide a higher order component for every piece of the Hyper UI.
Its structure is as follows:

All the decorate* methods receive the following references in an object passed as the second parameter:

All the components accept the following two properties to extend their markup:

Your higher order component can supply a onDecoratedproperty to the decorated component to get a reference to its instance.

Your Term higher order component can supply anonCursorMovehandler property that be called when cursor has moved with an object parameter representing its relative position to Term origin:

We encourage you to maintain compatibility with other decorators. Since many can be set, don't assume that yours is the only one.

For example, if you're passing children, compose potential existing values:

Or if you use onDecorated property

Phpstorm Electronico

Actions and Effects

All theRedux actionsare available for you to handle through your middleware and reducers. For an example, refer to the Hyperpowerreference plugin.

Side effects occur in two fundamental forms:

• Some actions dispatch other actions based on state.
• Some actions do async work by communicating over the RPC channel to the main process

In all cases, the side effect is passed as the effect key in the action and later handled by our middleware.

This means that you can override, compose or completely eliminate effects! In other words, this is how you can change the default functionality or behavior of the app.

As an example, consider the action we use to increase the font size when you press Command+=:

The underlying terminal

Hyper achieves a lot of its speed and functionality thanks to the power ofxterm.js

Additional APIs

The Electron app objects are extended with the following properties:

Webstorm Electron 调试

Electron BrowserWindow objects are extended with the following parameters:

Renderer windows are similarly extended with:

The rpc object is symmetrical between browser and renderer process. The API is the same as Node.js, with the exception that it only admits a single object as its parameters only:

Example theme: Hyperyellow

The following extension simply alters the config to add CSS and yellow colors! Here's thecode.

Themes are simply plugins! Only one hook, decorateConfigis needed:

I grabbed the class names by inspecting the term with Devtools, which you can trigger from View -> Toggle Developer Tools. When you do so, notice that some classes are automatically generated and followed by a random nonce (e.g.: term_13hv8io). Ignore those: they change with every new window!

Notice the emphasis on playing nice with other extensions. Specifically, we create a new object, extend only the keys we are interested in, and we compose the CSS to preserve the user's setting and that of other authors':

Example extension: Hyperpower

The following extension renders particles as the caret moves:

Let's walk throughits code.
First, we intercept the Redux action SESSION_ADD_DATA. You can find the full list of actionsin the repository.

Notice that we don't re-dispatch the action, which means we never render the output of the command to the terminal. Instead, we dispatch an action of our own, which we grab in the uiReducerand later map:

We then want to decorate the <Term> component so that we can access the underlying caret.

However, <Term> is not a container that we can map props to. So we use getTermProps to pass the property further down:

The extension thenreturnsa higher order component to wrap <Term>. Notice we pass the onDecoratedproperty to access the base Term component and its DOM ref, and theonCursorMove property to use Hyper cursor API: