Issue with Vite variables

Hi,

So I have been using the following in my .env file for a while now:

VITE_PUSHER_APP_KEY="${PUSHER_APP_KEY}"
VITE_PUSHER_HOST="${PUSHER_HOST}"
VITE_PUSHER_PORT="${PUSHER_PORT}"
VITE_PUSHER_SCHEME="${PUSHER_SCHEME}"

...and all has been well. However, recently the pusher connection I was using stopped working, and instead of the variables being completed by the previous environment variable declarations, it now is just passing the variables through as literal strings e.g. import.meta.env.VITE_PUSHER_APP_KEY = "${PUSHER_APP_KEY}"

I don't believe anything has changed in my vite setup, and I can't see a reason as to why it would have been working and now wont. Has anyone else experienced something similar?

LaryAI

2 years ago

Level 58

It seems like the issue you're facing is related to the usage of environment variables in Vite. The problem is that the variables are being passed as literal strings instead of being replaced with their corresponding values.

To resolve this issue, you can try the following steps:

Make sure that you have properly defined the environment variables in your .env file. Double-check the variable names and their values.
Ensure that you have installed the necessary dependencies for handling environment variables in Vite. You can use the dotenv package to load the variables from the .env file. Install it by running the following command:
```
npm install dotenv --save-dev
```

In your Vite configuration file (usually vite.config.js), import and configure the dotenv package to load the environment variables. Here's an example:

import { defineConfig } from 'vite';
import dotenv from 'dotenv';

export default defineConfig(() => {
  dotenv.config();
  // Rest of your Vite configuration
});

Restart your Vite development server to ensure that the changes take effect.

With these steps, Vite should be able to replace the environment variables with their corresponding values. You can then access them using import.meta.env.VITE_VARIABLE_NAME in your code.

If the issue persists, it might be worth checking if there are any recent updates or changes in the Vite or dotenv packages that could be causing this behavior. Additionally, you can consult the Vite documentation or seek help from the Vite community for further assistance.

I hope this helps! Let me know if you have any further questions.

amrit-pal

2 years ago

Level 1

have you found any solution

stonebitsrl

2 years ago

Level 12

Same issue here. Anyone have an idea why that happens?

Please or to participate in this conversation.