Loading env variables in React using Vite

 To load environment variables in a React application using Vite, you can use the `vite-env` plugin. This plugin provides support for loading environment variables from `.env` files in your Vite project. Here's how you can set it up:


1. **Install the `vite-env` plugin**:


   Install the `vite-env` plugin as a development dependency in your project using npm or yarn:


   ```bash

   npm install --save-dev vite-env

   # or

   yarn add --dev vite-env

   ```


2. **Create Environment Variables Files**:


   Create one or more `.env` files in the root of your Vite project. You can create different `.env` files for different environments (e.g., `.env.development`, `.env.production`, etc.).


   Inside these `.env` files, define your environment variables in the format `VARIABLE_NAME=value`. For example:


   ```

   REACT_APP_API_KEY=your_api_key

   REACT_APP_API_URL=https://api.example.com

   ```


   Prefixing your variables with `REACT_APP_` is a convention for React projects to make them available to your React application.


3. **Configure Vite to Use the `vite-env` Plugin**:


   In your `vite.config.js` file, import and use the `vite-env` plugin:


   ```javascript

   import env from 'vite-env';


   export default {

     plugins: [

       env(), // Use the vite-env plugin

     ],

   };

   ```


4. **Access Environment Variables in Your React Application**:


   You can now access your environment variables in your React application as follows:


   ```javascript

   // For example, in a React component

   const apiKey = import.meta.env.VITE_REACT_APP_API_KEY;

   const apiUrl = import.meta.env.VITE_REACT_APP_API_URL;


   // Use apiKey and apiUrl in your component

   ```


   The `import.meta.env` object provides access to the environment variables defined in your `.env` files.


5. **Use Different Environment Variables for Different Environments**:


   To use different environment variables for different environments (e.g., development, production), create separate `.env` files (e.g., `.env.development`, `.env.production`) and specify which environment you want to build for using Vite's command line options.


   For example, to build for production:


   ```bash

   vite build --mode production

   ```


   Vite will use the `.env.production` file when you specify `--mode production`.


By following these steps, you can load environment variables in your React application using Vite and the `vite-env` plugin, which provides a convenient way to manage different sets of variables for different environments.

Comments

Post a Comment

Popular posts from this blog

bad character U+002D '-' in my helm template

 In Helm templates, the hyphen character (`-`) can sometimes be treated as a reserved character, particularly when defining values or labels. To include a hyphen character in a Helm template without issues, you can use one of the following approaches: 1. **Quoting the Hyphen:**    You can enclose the hyphen in double quotes, like this:    ```yaml    key: "-"    ```    This way, Helm will interpret the hyphen as a string rather than an operator. 2. **Using Backticks:**    If you need to use the hyphen within a Go template function or inside backticks, you can escape it with a backslash (`\`), like this:    ```yaml    value: `{{ .Values.someField | printf "%s \\-" }}`    ```    The backslash prevents Helm from interpreting the hyphen as a special character. 3. **Variable Assignment:**    Assign the value to a variable and use it. For example:    ```yaml    {{- $hyphen := "-" }}    key: {{ $hyphen }}    ```    This way, you can use the variable `$hyphen` wher
Read more

GitLab pipeline stopped working with invalid yaml error

 When your GitLab pipeline has stopped working with an "invalid YAML" error, it means there's a problem with your `.gitlab-ci.yml` file. This could be due to syntax errors, incorrect indentation, or other issues in your pipeline configuration. Here's how to troubleshoot and resolve this issue: 1. **Check for Syntax Errors**:    Carefully review your `.gitlab-ci.yml` file for any syntax errors. Common issues include missing colons, indentation problems, or mismatched quotation marks. Use a YAML linter or an online YAML validator to identify and correct syntax errors. 2. **Indentation**:    YAML relies heavily on proper indentation. Make sure that all lines within the same block have consistent indentation (typically using spaces, not tabs). Incorrect indentation can cause YAML parsing errors. 3. **Dashes and Lists**:    Ensure that you use the correct syntax for lists (arrays) in YAML by starting each item with a dash (`-`). Be consistent with your use of dashes throug
Read more

How do I add a printer in OpenSUSE which is being shared by a CUPS print server?

 To add a printer in openSUSE that is being shared by a CUPS print server, you can use the following steps: 1. **Ensure CUPS Client is Installed:**    Make sure your openSUSE system has the CUPS client tools installed. You can install them using the following command:    ```bash    sudo zypper install cups-client    ``` 2. **Discover Available Printers:**    Use the `lpinfo` command to discover available printers on your CUPS print server. Replace `cups-server-hostname` with the hostname or IP address of your CUPS server:    ```bash    lpinfo -v -h cups-server-hostname:631    ```    This command should list the printers shared by the CUPS server. 3. **Add a Printer:**    Use the `lpadmin` command to add a printer. Replace `printer-name` with the name of the printer you want to add and `printer-uri` with the URI obtained from the `lpinfo` command:    ```bash    sudo lpadmin -p printer-name -E -v printer-uri    ```    For example:    ```bash    sudo lpadmin -p MyPrinter -E -v socket://cu
Read more