@nx/vite:configuration
Configure a project to use Vite.js.
The State of JS survey is live, featuring a monorepo tools sectionThe State of JS survey is live, featuring a monorepo tools sectionVote for us
Configure a project to use Vite.js.
This generator is used for converting an existing React or Web project to use Vite.js and the @nx/vite executors.
It will change the build
and serve
targets to use the @nx/vite
executors for serving and building the application. If you choose so, it will also change your test
target to use the @nx/vite:test
executor. It will create a vite.config.ts
file at the root of your project with the correct settings, or if there's already a vite.config.ts
file, it will modify it to include the correct settings.
This generator will modify your code, so make sure to commit your changes before running it.
1nx g @nx/vite:configuration
2
When running this generator, you will be prompted to provide the following:
project
, as the name of the project you want to generate the configuration for.uiFramework
you want to use. Supported values are: react
and none
.You must provide a project
and a uiFramework
for the generator to work.
You may also pass the includeVitest
flag. This will also change your test
target to use the @nx/vite:test
executor, and configure your project for testing with Vitest, by adding the test
configuration in your vite.config.ts
file.
By default, the @nx/vite:configuration
generator will search your project's configuration to find the targets for serving, building, and testing your project, and it will attempt to convert these targets to use the @nx/vite
executors.
Your targets for building, serving and testing may not be named build
, serve
and test
. Nx will try to infer the correct targets to convert, and it will attempt to convert the first one it finds for each of these actions if you have more than one. If you have more than one target for serving, building, or testing your project, you can pass the --serveTarget
, --buildTarget
, and --testTarget
flags to the generator, to tell Nx specifically which targets to convert.
Nx will determine if the targets you provided (or the ones it inferred) are valid and can be converted to use the @nx/vite
executors. If the targets are not valid, the generator will fail. If no targets are found - or recognized to be either supported or unsupported - Nx will ask you whether you want to convert your project anyway. If you choose to do so, Nx will configure your project to use Vite.js, creating new targets for you, and creating or modifying your vite.config.ts
file. You can then test on your own if the result works or not, and modify the configuration as needed. It's suggested that if Nx does not recognize your targets automatically, you commit your changes before running the generator, so you can revert the changes if needed.
@nx/vite
executorsUsually, React and Web projects generated with the @nx/react
and the @nx/web
generators can be converted to use the @nx/vite
executors without any issues.
The list of executors for building, testing and serving that can be converted to use the @nx/vite
executors is:
build
executors@nxext/vite:build
@nx/js:babel
@nx/js:swc
@nx/webpack:webpack
@nx/rollup:rollup
@nx/web:rollup
serve
executors@nxext/vite:dev
@nx/webpack:dev-server
test
executors@nx/jest:jest
@nxext/vitest:vitest
@nx/angular:ng-packagr-lite
@nx/angular:package
@nx/angular:webpack-browser
@angular-devkit/build-angular:browser
@angular-devkit/build-angular:dev-server
@nx/esbuild:esbuild
@nx/react-native:start
@nx/next:build
@nx/next:server
@nx/js:tsc
We cannot guarantee that projects using unsupported executors - or any executor that is NOT listed in the list of "supported executors" - for either building, testing or serving will work correctly when converted to use the @nx/vite
executors.
If you have a project that does not use one of the supported executors you can try to configure it to use the @nx/vite
executors manually, but it may not work properly.
You can read more in the Vite package overview page.
1nx g @nx/vite:configuration --project=my-react-app --uiFramework=react --includeVitest
2
This will change the my-react-app
project to use the @nx/vite
executors for building, serving and testing the application.
1nx g @nx/vite:configuration --project=my-web-app --uiFramework=none --includeVitest
2
This will change the my-web-app
project to use the @nx/vite
executors for building, serving and testing the application.
1nx g @nx/vite:configuration --project=my-react-app --uiFramework=react --includeVitest --buildTarget=my-build --serveTarget=my-serve --testTarget=my-test
2
This will change the my-build
, my-serve
and my-test
targets to use the @nx/vite
executors for building, serving and testing the application, even if you have other targets for these actions as well.
1nx generate configuration ...
2
1nx g config ... #same
2
By default, Nx will search for configuration
in the default collection provisioned in workspace.json.
You can specify the collection explicitly as follows:
1nx g @nx/vite:configuration ...
2
Show what will be generated without writing to disk:
1nx g configuration ... --dry-run
2
The build target of the project to be transformed to use the @nx/vite:build executor.
babel
babel
, swc
Compiler to use for Vite when UI Framework is React.
Add a library build option and skip the server option.
Use vitest for the test suite.
false
Is this a new project?
The name of the project.
The serve target of the project to be transformed to use the @nx/vite:dev-server and @nx/vite:preview-server executors.
The test target of the project to be transformed to use the @nx/vite:test executor.
jsdom
node
, jsdom
, happy-dom
, edge-runtime
The vitest environment to use. See https://vitest.dev/config/#environment.
none
react
, none
UI Framework to use for Vite.
false
Skip formatting files.