.env 文件访问令牌适用于 API 而不是 Next.js 中的另一个

Question

I'm calling two DBs -- WordsAPI and Spotify API. For each DB there is an access token/db key, both of which I've stored in a .env file.

I'm fetch the data in identical ways in getStaticProps and it's working just fine for WordsAPI but not Spotify. In Postman, Spotify works just fine.

Here are the calls:

export async function getStaticProps(context) {
  const wordsRes = await fetch(
    `https://wordsapiv1.p.rapidapi.com/words/${context.params.word}/definitions`,
    {
      method: "GET",
      headers: {
        "x-rapidapi-key": process.env.NEXT_PUBLIC_DB_KEY,
        "x-rapidapi-host": "wordsapiv1.p.rapidapi.com",
      },
    }
  )
    .then((response) => {
      return response;
    })
    .catch((err) => {
      console.error(err);
    });
  const songsRes = await fetch(
    `https://api.spotify.com/v1/search?q=${context.params.word}&type=track`,
    {
      method: "GET",
      headers: {
        authorization: "Bearer " + process.env.NEXT_PUBLIC_SPOTIFY_ACCESS_TOKEN,
      },
    }
  )
    .then((response) => {
      return response;
    })
    .catch((err) => {
      console.error(err);
    });
  const wordsData = await wordsRes.json();
  const songsData = await songsRes.json();
  return {
    props: {
      wordsData,
      songsData,
    },
  };
}

the .env file is as simple as follows:

NEXT_PUBLIC_SPOTIFY_ACCESS_TOKEN=BQDcgHT2IfAXsXXX_XXX_XXX
NEXT_PUBLIC_DB_KEY=a2c92537d6mshXXX

I heard that leaving the key at the bottom of the file without an extra line can mess it up, but switching them around didn't change anything. I've also tried various combinations of switching to string format in each file, switching the header key to "authorization" , using string interpolation etc. Also tried naming my file .env.local (as was recommended for Next.js), but nothing works.

Most of the solutions on SO seem to be about .env files not working at all, which isn't the case here.

Answer 1

I have reviewed the code everything looks fine in general. It would help if you restarted the server whenever you made a new file, I believe. Try restating the server. It should work.