ENV variables not being set either in config file or using --env flag in cli

Hi there,

I’m having trouble with environment variables, seems like adding them in cypress.config.js or using --env cli does not register them in cypress. When I inspect the settings in the UI or print the env vars during tests I see the following.

If I use cypress.env.json, it registers my variables but it also shows the same error.

Versions

• Cypress version: 10.9.0
• Preprocessor version: 13.0.2
• Node version: 18.9.1

my cypress.config.js file looks like this:

const { defineConfig } = require("cypress");
const createBundler = require("@bahmutov/cypress-esbuild-preprocessor");
const addCucumberPreprocessorPlugin =
  require("@badeball/cypress-cucumber-preprocessor").addCucumberPreprocessorPlugin;
const createEsbuildPlugin =
  require("@badeball/cypress-cucumber-preprocessor/esbuild").createEsbuildPlugin;

require('dotenv').config({path: './.env'});

module.exports = defineConfig({
 
  e2e: {
    async setupNodeEvents(on, config) {
      const bundler = createBundler({
        plugins: [createEsbuildPlugin(config)],
      });

      on("file:preprocessor", bundler);
      await addCucumberPreprocessorPlugin(on, config);

      return config;
    },

    specPattern: "cypress/e2e/features/*.feature",
    chromeWebSecurity: false,
  },

});

my package.json contains the following:

  "cypress-cucumber-preprocessor": {
    "stepDefinitions": "./cypress/e2e/step_definitions/*.cy.js"
  }

Checklist

• I’ve read the FAQ.
• I’ve read Instructions for logging issues.
• I’m not using cypress-cucumber-preprocessor@4.3.1 (package name has changed and it is no longer the most recent version, see #689).

[badeball]

It’s not an error, but something set by the plugin and not something you need to be concerned about.

[mazza1892]

Great! so that works, but still seeing the error message too. Any idea what that is?