#
Frontend framework
#
Introduction
Rocket offers you the option of integrating a frontend framework during the rocket ignite process.
It is possible that Rocket overwrites existing files. It is therefore essential to check whether any of the existing and required files have been overwritten before committing.
#
Options
#
Plain
You can use Rocket without frontend framework with plain vanilla javascript. If you select this option, none of the steps in the ignite process will be skipped.
The current working directory must be empty (with the exception of .git and package.json)
#
Custom
To use Rocket in combination with a frontend framework, you first have to implement your frontend framework and then start the ignite process in your root directory. Rocket will then skip the steps to add ESLint and prettier and skip the .gitignore step as well, if it already exists. If you already have an .env file and have variables that you need there, you should select the backup option in the env step and then manually add the required variables from the two files to your .env.
Please make sure that you run ignite directly after adding the frontend framework and do not make several other configurations in the meantime.
The current working directory must contain files (with the exception of .git and package.json)
#
Next.js
Rocket offers the option of integrating Next.js during the ignite process. For this, npx create-next-app@latest is used. Rocket will then skip the steps to add ESLint, prettier and .gitignore.
The current working directory must be empty (with the exception of .git)
#
Next Commerce
You can use the customized version of Next.js Commerce (incl. adapter for commercetools and contentful). For this, the Next.js Commerce kernpunkt repository is cloned during the ignite process. Rocket will then skip the steps to add ESLint, prettier and .gitignore.
The current working directory must be empty and the selected packagemanager must be yarn