Berry React
v4.0.0
v4.0.0
  • Introduction
  • Package
  • Getting Started
    • Pre-requisites
    • Quick Start
    • Mock backend
    • Deployment
    • Licensing
  • Setup
    • Seed
    • To Existing Project
  • Folder Structure
  • State Management
  • Multi Language
  • Authentication
    • Firebase
    • Auth0
    • AWS Cognito
    • Supabase
  • API Calls
  • Routing
    • New Menu
    • Login as First Page
    • Skip Login
    • Render Menu from the backend
    • Remove menu render via backend
  • Theme
    • Configuration
    • Presets
    • Style
      • Color
      • Typography
      • Overrides
      • Shadows
    • Layouts
    • Logo
  • How to
    • Remove eslint
    • Remove prettier
  • Components
    • Avatar
    • AnimateButton
    • Accordion
    • Breadcrumbs
    • Chip
    • ImageList
    • MainCard
    • Transitions
    • SubCard
  • Dependencies
  • Support
    • Roadmap
    • Changelog
    • FAQ
  • Berry Eco System
Powered by GitBook
On this page
  • Pre-requisites
  • Troubleshooting

Was this helpful?

  1. Getting Started

Pre-requisites

Here is a list of the requirements needed to begin using Berry React.

Was this helpful?

No need to set up or configure tools such as Webpack or Babel - they are already configured, allowing you to focus on the code.

Pre-requisites

  1. - Version 20.x.x recommended

  2. /package manager

  3. When copying folders, include hidden files like .env. This file contains important theme settings. Do not delete the .env file. Update its values according to your organization’s needs, but do not change the keys.

  4. The theme includes two lock files: yarn.lock (for Yarn) and package-lock.json (for npm). Each of these files corresponds to a different package manager. To ensure consistency and avoid potential conflicts:

    1. Choose a Package Manager: Decide whether you will use Yarn or npm for managing dependencies in your project.

      • If using Yarn: Retain yarn.lock and delete package-lock.json.

      • If using npm: Retain package-lock.json and delete yarn.lock.

    2. Do Not Modify Lock Files Manually: Avoid editing the contents of yarn.lock or package-lock.json directly. Manually changing these files can lead to dependency issues and inconsistencies. Always use the appropriate package manager commands (yarn or npm) to update or regenerate these files.

You can check your current version using following commands:

c:\> node -v
c:\> yarn -v
c:\> npm -v

This documentation primarily uses Yarn. You can replace Yarn commands with npm if needed.

Troubleshooting

If you face the following error in your terminal, it means Yarn is not installed in your system.

c:\> yarn -v
'yarn' is not recognized as an internal or external command,
operable program or batch file.

Please install it using this as it does not come with Node automatically.

Node JS
Yarn
NPM
link