npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

cypress-env-plugin

v1.0.0

Published

An unofficial plugin for loading your environment into your Cypress environment, such as dotenv.

Downloads

13

Readme

Cypress Env Plugin

An unofficial plugin for loading your environment into your Cypress environment, such as dotenv.

Installation

npm

npm i -D cypress-env-plugin

yarn

yarn add -D cypress-env-plugin

Usage

In your cypress/plugins/index.js file:

Basic example

const { createEnvPlugin } = require('cypress-env-plugin');
/**
 * With no prefix a .env of:
 * SECRET_KEY=SECRET_KEY
 * CYPRESS_API_URL=https://api.cool.com/api/
 *
 * Will expose to Cypress Env:
 * API_URL=https://api.cool.com/api/
 */
// Initialise the plugin
const envPlugin = createEnvPlugin({
  env: require('dotenv').config(),
});

module.exports = (on, config) => {
  // Add the plugin
  envPlugin(config);
  return config;
};

Remove prefix restriction example

By default, we filter out any environment variables unless they're prefixed with CYPRESS_, if you want to load everything from your .env you can pass null to the prefix property,

const { createEnvPlugin } = require('cypress-env-plugin');
/**
 * With a null prefix a .env of:
 * SECRET_KEY=SECRET_KEY
 * CYPRESS_API_URL=https://api.cool.com/api/
 *
 * Will expose to Cypress Env:
 * SECRET_KEY=SECRET_KEY
 * CYPRESS_API_URL=https://api.cool.com/api/
 */
// Initialise the plugin
const envPlugin = createEnvPlugin({
  env: require('dotenv').config(),
});

module.exports = (on, config) => {
  // Add the plugin
  envPlugin(config);
  return config;
};

Custom prefix example

You can also provide your own prefix:

const withCustomPrefix = createEnvPlugin({
  prefix: 'WHATEVER_',
  env: require('dotenv').config(),
});

Plain object example

I'm not sure why, but you can also pass a plain object for your environment. process.env maybe?

const withCustomPrefix = createEnvPlugin({
  prefix: 'WHATEVER_',
  env: {
    WHATEVER_API_KEY: '123578123718923',
  },
});

Contributing

Local Development

Below is a list of commands you will probably find useful.

npm start or yarn start

Runs the project in development/watch mode. Your project will be rebuilt upon changes.

npm run build or yarn build

Bundles the package to the dist folder. The package is optimized and bundled with Rollup into multiple formats (CommonJS, UMD, and ES Module).

npm test or yarn test

Runs the test watcher (Jest) in an interactive mode. By default, runs tests related to files changed since the last commit.