Urgent.News

What's breaking now, across thousands of outlets.

Tech

Vite+ — Chapter 3: Vite+ in Practice

In the previous chapter, we looked at what Vite+ is made of . We saw that Vite+ brings together tools such as: Vite Vitest Rolldown tsdown Oxlint Oxfmt Vite Task But knowing what these tools are is only half the story. The more interesting question is: What does developing a real project with Vite+ actually look like? That's what we'll explore in this chapter. We'll create a project, start the…

In this chapter, we explore what developing a real project with Vite+ looks like. We create a project, start the development server, run checks and tests, and finally create a production build.

1. Installing Vite+ provides a vp command-line interface that serves as the main doorway into your JavaScript project. You can check the installed version by running `vp --version`.

2. To create a new Vite+ project, use the `vp create` command. The tool ships with built-in templates, such as `vp vite:monorepo`, `vp vite:application`, and `vp vite:library`. Move into the newly created project directory with `cd my-project`.

3. Installing dependencies is streamlined with the `vp install` command. Vite+ works with various package managers and automatically detects the package-manager setup used by the project.

4. Starting the development server is as simple as running `vp dev`. This uses Vite's development server, providing a fast development experience with hot module updates.

5. Before committing your code, you can check it using `vp check`. This command integrates formatting, linting, and type checking into a single workflow, eliminating the need to remember multiple commands for each step.

6. Running tests is also simplified with `vp test`. Vite+ runs the tests through Vitest, making the development, checking, and testing workflows consistent across the project.

7. When your application is ready for production, you can build it using `vp build`. This command builds the application for production using Vite and Rolldown, optimizing the output for deployment.

8. After building, you can preview the production build with `vp preview`. This lets you check the production version locally before deploying it to a live environment.

In summary, the basic Vite+ workflow consists of the following commands:

- Create a project: `vp create`

- Install dependencies: `vp install`

- Start development: `vp dev`

- Check code: `vp check`

- Run tests: `vp test`

- Build for production: `vp build`

- Preview production build: `vp preview`

By providing a consistent command interface for these tasks, Vite+ simplifies the development process and eliminates the need for developers to remember multiple commands for each step of the workflow.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

Two Iceberg Clients, One Protocol: Where the Time Goes

This article provides a step by step comparison of the Rust and Python clients for Apache Iceberg REST catalogs. It times both clients on the same operations against the same tables, then breaks one…

  • Rust Iceberg client is 1.90x to 4.29x faster than Python client on small calls
  • Majority of time difference due to HTTP library: reqwest (Rust) vs requests (Python)
  • pyiceberg supports 21 of 25 catalog endpoints, iceberg-catalog-rest supports 13

More from Friday 25 September →