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

dotenv-processor

v0.1.7

Published

This project demonstrates how to use `.env` files to manage environment variables in a Playwright project.

Downloads

14

Readme

Playwright Project with .env File Support

This project demonstrates how to use .env files to manage environment variables in a Playwright project.

Table of Contents

Introduction

This repository shows how to manually load environment variables from a .env file using Node.js built-in modules in a Playwright project.

Setup

Prerequisites

  • Node.js (version 12 or higher)
  • Playwright

Installation

Install dependencies:

npm install dotenv-processor@latest

or

yarn add dotenv-processor@latest

Environment Variables

  1. Create a .env file at the root of the project. Add your environment variables in the format KEY=VALUE. For example:

    BASE_URL=https://example.com
    API_KEY=your_api_key_here

Usage

Loading Environment Variables

  1. Modify your Playwright configuration file (e.g., playwright.config.ts) to load the environment variables by importing the loadEnv method from the dotenv-processor library and calling it as demonstrated below:

    import { defineConfig } from '@playwright/test';
    import { loadEnv } from "dotenv-processor";
    
    // Load environment variables
    loadEnv();
    
    export default defineConfig({
      use: {
        baseURL: process.env.BASE_URL,
        // other Playwright configurations
      },
      // other configurations
    });

Writing Tests

Use the environment variables in your test files as follows:

// example.spec.ts
import { test, expect } from '@playwright/test';

test('example test', async ({ page }) => {
  await page.goto(process.env.BASE_URL as string);
  // Perform actions and assertions using environment variables
});