Experiencing an error when attempting to pass strings from .env.local to a new Redis instance

Question

Experiencing an error when attempting to pass strings from .env.local to a new Redis instance

Encountering an issue with TypeScript while setting up a new Redis instance. I have configured an .env.local file with matching names for the redis URL and token.

Below is the code snippet:

import { Redis } from "@upstash/redis";

// @ts-ignore
export const db: Redis = new Redis({
    url: process.env.UPSTASH_REDIS_REST_URL,
    token: process.env.UPSTASH_REDIS_REST_TOKEN
})

The TypeScript error message I'm receiving is as follows:

 TS2769: No overload matches this call.   Overload 2 of 2, '(requesters: Requester): Redis', gave the following error.     Argument of type '{ url: string | undefined; token: string | undefined; }' is not assignable to parameter of type 'Requester'.       Object literal may only specify known properties, and 'url' does not exist in type 'Requester'.

While referencing the upstash/redis documentation for guidance, the code works but the error remains persistent.

Attempting different actions in WebStorm to prevent the TypeScript errors has been unsuccessful so far.

typescript next.js redis

Answer 1

Answer №1

It's strange that it's not working as expected.

Here's a simple solution you can try:

const db = Redis.fromEnv()

By doing this, the variables will be loaded from your environment automatically without going through the constructor.

Answer 2

It's strange that it's not working as expected.

Here's a simple solution you can try:

const db = Redis.fromEnv()

By doing this, the variables will be loaded from your environment automatically without going through the constructor.

Answer 3

Answer №2

Earlier today, I encountered the same issue,

However, I managed to successfully resolve it.

If you are facing a similar problem, try using this piece of code :

import { Redis } from '@upstash/redis';

export const db: Redis = new Redis({
   url: process.env.UPSTASH_REDIS_REST_URL || '',
   token: process.env.UPSTASH_REDIS_REST_TOKEN || ''
});

It worked like a charm for me.

Answer 4

Earlier today, I encountered the same issue,

However, I managed to successfully resolve it.

If you are facing a similar problem, try using this piece of code :

import { Redis } from '@upstash/redis';

export const db: Redis = new Redis({
   url: process.env.UPSTASH_REDIS_REST_URL || '',
   token: process.env.UPSTASH_REDIS_REST_TOKEN || ''
});

It worked like a charm for me.

Answer 5

Answer №3

Regrettably, I am unable to provide feedback on Ugur Eren's response. However, the example you shared accurately demonstrates the functionality of Redis.fromEnv().

Answer 6

Regrettably, I am unable to provide feedback on Ugur Eren's response. However, the example you shared accurately demonstrates the functionality of Redis.fromEnv().

Answer 7

Answer №4

Although this response may be delayed, it is important for anyone encountering this issue to know that Typescript sometimes doubts whether the env variable will contain a value, so it is defined as string | undefined. To resolve this, simply add an exclamation mark at the end of the variable. Further information can be found here.

export const db: Redis = new Redis({
   url: process.env.UPSTASH_REDIS_REST_URL!,
   token: process.env.UPSTASH_REDIS_REST_TOKEN!
});

Answer 8

Although this response may be delayed, it is important for anyone encountering this issue to know that Typescript sometimes doubts whether the env variable will contain a value, so it is defined as string | undefined. To resolve this, simply add an exclamation mark at the end of the variable. Further information can be found here.

export const db: Redis = new Redis({
   url: process.env.UPSTASH_REDIS_REST_URL!,
   token: process.env.UPSTASH_REDIS_REST_TOKEN!
});

Answer 9

Answer №5

When no variables with the specified names are defined in env files, this error will be shown. If you wish, you can define them in next.config.mjs:

const nextConfig = {
  env: {
    VARIABLE_NAME: 'value',
    UPSTASH_REDIS_REST_URL: 'https://...',
  }
};

This will make sure that the variables can be accessed in process.env.

Local Redis REST API

If you prefer not to connect your software to a third-party server like Upstash for any reason, you have the option of installing Webdis. Webdis is a REST API built on top of a Redis base server. The only requirement is to have the Redis server installed and running.
https://github.com/nicolasff/webdis

Answer 10

When no variables with the specified names are defined in env files, this error will be shown. If you wish, you can define them in next.config.mjs:

const nextConfig = {
  env: {
    VARIABLE_NAME: 'value',
    UPSTASH_REDIS_REST_URL: 'https://...',
  }
};

This will make sure that the variables can be accessed in process.env.

Local Redis REST API

If you prefer not to connect your software to a third-party server like Upstash for any reason, you have the option of installing Webdis. Webdis is a REST API built on top of a Redis base server. The only requirement is to have the Redis server installed and running.
https://github.com/nicolasff/webdis

Experiencing an error when attempting to pass strings from .env.local to a new Redis instance

Answer №1

Answer №2

Answer №3

Answer №4

Answer №5

Local Redis REST API

Similar questions

Querying subdocuments within an array using MongoDB's aggregation framework

Is there an option for keyPrefix in i18next?

Executing TypeORM commands yields no output

Filter the angular accordion by passing a simple array value into the input

Creating Component Variants for Google Optimize A/B testing in Next.js

Utilizing Mantine dropzone in conjunction with React Hook Form within a Javascript environment

In Production mode, Angular automatically reloads the page every time my data request service is executed to fetch data from the API

I encountered the issue: "The specified resource is not a valid image for /public/logoicon/logoOrange.png, it was received as text/html; charset=utf-8."

Getting the current page name within the app.component.ts file in Ionic 3 - a simple guide

Adding a type declaration to the severity property in React Alert - A guide to Typescript

Issue in Next.js 13: Byte index exceeds limits when running 'npm run dev' command

Creating a randomly generated array within a Reactjs application

Is it possible to integrate two calendars into the `DatePicker` component of MUI?

The type '{}' does not contain a property named 'map'

Tips for successfully mocking axios.get in Jest and passing AxiosPromise type value

The specified property 'slug' is not found within the designated type 'ParsedUrlQuery | undefined'

The expiration of the Gitlab CI/CD cache leads to the failure of the build process

Is TypeScript 2.8 Making Type-Safe Reducers Easier?

Utilizing TypeScript/React to Access Data from an Excel Spreadsheet

Creating enduring designs in Next.js