Vite

JetBrains Rider integrates with the Vite build tool that improves the frontend development experience. Vite consists of a dev server and a build command. The build server serves your source files over native ES modules. The build command bundles your code with Rollup, which is pre-configured to output highly optimized static assets for production.

JetBrains Rider supports tsconfig.json and jsconfig.json path mappings in Vue style tags and recognizes Vite aliases.

In projects that consist of multiple modules with different Vite configurations, JetBrains Rider can automatically detect the relevant configuration file for each module and use the module resolution rules from it, refer to Specifying the Vite configuration file to use below.

Before you start

Download and install Node.js.
Make sure the JavaScript and TypeScript plugin is enabled in the settings. Press Ctrl+Alt+S to open the IDE settings and then select Plugins. Click the Installed tab. In the search field, type JavaScript and TypeScript. For more information about plugins, refer to Managing plugins.
Install and enable the Vite plugin on the Settings/Preferences | Plugins page, tab Marketplace, as described in Installing plugins from JetBrains Marketplace.

Create a new Vite application

Install Vite in an existing or an empty solution

Learn more about adding Vite to a project from the Vite official website.

Create an empty JetBrains Rider solution

Click New Solution on the Welcome screen or select File | New Solution from the main menu. The New Solution dialog opens.
In the left-hand pane, choose Empty Solution. In the right-hand pane, specify the application folder and click Create.

Install Vite in an empty solution

Open the empty solution where you will use Vite.
In the embedded Terminal (Alt+F12) , type:
npm install --save-dev vite

Start with an existing Vite application

To continue developing an existing Vite application, open it in JetBrains Rider and download the required dependencies.

Open the application sources that are already on your machine

Click Open on the Welcome screen or select File | Open | Open from the main menu. In the dialog that opens, select the folder where your sources are stored.

Check out the application sources from your version control

Click Get from VCS on the Welcome screen.
Alternatively, select Git | Clone… or VCS | Get from Version Control from the main menu.
Instead of Git in the main menu, you may see any other Version Control System that is associated with your project. For example, Mercurial or Perforce.
In the dialog that opens, select your version control system from the list and specify the repository to check out the application sources from. For more information, refer to Check out a project (clone).

Download the dependencies

Click Run 'npm install' or Run 'yarn install' in the popup:
You can use npm, Yarn 1, or Yarn 2, refer to npm and Yarn for details.
Alternatively, select Run 'npm install' or Run 'yarn install' from the context menu of package.json in the editor or in the Project tool window.

Project security

When you open a project that was created outside JetBrains Rider and was imported into it, JetBrains Rider displays a dialog where you can decide how to handle this project with unfamiliar source code.

Select one of the following options:

Preview in Safe Mode: in this case, JetBrains Rider opens the project in a preview mode. It means that you can browse the project's sources but you cannot run tasks and script or run/debug your project.
JetBrains Rider displays a notification on top of the editor area, and you can click the Trust project… link and load your project at any time.
Trust Project: in this case, JetBrains Rider opens and loads a project. That means the project is initialized, project's plugins are resolved, dependencies are added, and all JetBrains Rider features are available.
Don't Open: in this case, JetBrains Rider doesn't open the project.

Configure Vite in JetBrains Rider

Create Vite configuration files

Create one or several configuration files depending on your project structure: select a parent folder in the Project tool window and then select New | JavaScript file from the context menu.
The acceptable names are vite.config.js/vite.config.ts, vite.config.mjs, or vite.config.cjs.
Learn more from the Vite official website.
If necessary, use alias that will be later recognized in import statements. Make sure you specify absolute paths in definitions of aliases. Learn more from the Vite official website.

Specify the Vite configuration files to use

Based on the analysis of a Vite configuration file, JetBrains Rider understands the Vite configuration, resolves modules, and provides coding assistance in JavaScript and TypeScript files.

In JetBrains Rider, you can choose between two configuration modes – automatic and manual.

With automatic configuration, JetBrains Rider auto-detects the relevant Vite configuration file for each JavaScript or TypeScript file.

With manual configuration, you specify the Vite configuration file to use in your project. Manual configuration is useful if the name of your Vite configuration file is not recognized by JetBrains Rider, refer to the list of recognized Vite config names below.

Choose how to detect Vite configuration

Open the Settings/Preferences dialog (Ctrl+Alt+S) and go to Languages & Frameworks | JavaScript | Vite.
In the Detect Vite configuration files for module resolution area, select one of the following options:
- Automatically: In this mode, for a JavaScript or TypeScript file, JetBrains Rider will first look for a Vite configuration file in the folder where this JavaScript or TypeScript file is located, then in its parent folder, and so on.
  As a result, if your project consists of multiple modules with different Vite configurations, each module will use the module resolution rules from its own Vite configuration file (if such config is found).
  JetBrains Rider recognizes JavaScript or TypeScript Vite configuration files with the following names and in the following order:
  - vite.config.js/vite.config.ts
  - vite.config.mjs
  - vite.config.cjs
- Manually: In the Configuration file field, specify the location of the Vite config to use.
  In this mode, the resolution rules from the specified configuration file will be applied to all modules in your project.
  Select this option if the name of your Vite configuration file is not recognized by JetBrains Rider, refer to the list of recognized Vite config names above.

Run a Vite application

For applications created with create-vite, JetBrains Rider generates an npm configuration . This configuration runs the vite command that launches the development server and starts your application in the development mode.

In other cases, you need to create a run/debug configuration with the actual settings, such as, host, port, etc., manually.

Select the npm dev run configuration from the list on the toolbar and click next to it.
Alternatively, run npm dev in the Terminal Alt+F12, or double-click the dev task in the npm tool window (View | Tool Windows | npm), or click in the gutter next to the dev script in package.json.
Wait till the application is compiled and the development server is ready.
The Run tool window or the Terminal shows the URL at which your application is running, by default it is http://localhost:4200/. Click this link to view the application.

Debug a Vite application

Debug applications created with create-vite

Set the breakpoints in your code.
Start the application in the development mode as described above and wait till the application is compiled and the development server is ready.
In the Run tool window or the Terminal, hold Ctrl+Shift, and click this URL link.

Debug applications running on localhost

Set the breakpoints in your code.
Start the application in the development mode as described above and wait till the application is compiled and the development server is ready.
The Run tool window or the Terminal shows the URL at which your application is running, by default it is http://localhost:<port>/. Hold Ctrl+Shift and click this URL link. JetBrains Rider starts a debugging session with an automatically generated localhost:<port> configuration of the type JavaScript Debug.

Debug applications running on custom URLs

Set the breakpoints in your code.
Start the application in the development mode as described above and wait till the application is compiled and the Webpack development server is ready.
The Run tool window or the Terminal shows the URL at which your application is running. Copy this URL address, you will later specify it in a debug configuration. To view your application, just click the link.
Create a JavaScript Debug configuration. To do that, go to Run | Edit Configurations in the main menu, click , and select JavaScript Debug from the list. In the Run/Debug Configuration: JavaScript Debug dialog, paste the saved URL in the URL field and save the configuration.
To launch your newly created configuration, select it from the list of configurations and click next to the list.

Troubleshooting for Node.js 17+

If you are using Node.js version 17 or later, during a debugging session you may face network connectivity issues that result in problems with attaching the debugger or with loading sourcemaps.

The workaround is to pass --host 127.0.0.1 to the server. You can do that in one of the following ways:

Update the dev script in your package.json:
"dev": "vite --host=127.0.0.1"
Alternatively, add dns.setDefaultResultOrder('ipv4first') to your vite.config.ts.

Last modified: 21 March 2024