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

@withuno/locust

v0.4.7

Published

A fork of @buttercup/locust with TypeScript support and new features incoming...

Downloads

18

Readme

Locust

Login form location utility forked from @buttercup/locust.

Run Unit & Integration Tests npm

About

Locust helps find login forms by searching the DOM for common login form elements. It processes a page and returns targets which can be used for automating logins.

Installation

npm install @withuno/locust

Usage

import { LoginTarget } from "@withuno/locust";

const target = LoginTarget.find();

if (target) {
  const form = target.get("form");
  const usernameInput = target.get("username");
  const passwordInput = target.get("password");
  const submitButton = target.get("submit");

  usernameInput.value = "myUsername";
  passwordInput.value = "myPassword";
  submitButton.click();
}

The example above enters the username and password in the best form found on the page and then proceeds to submit that form (logging the user in).

To find all forms on a page, use the LoginTarget.findAll() method instead, which returns an array of login targets. You can then sort through these to find all the different login forms that may exist.

[!NOTE] LoginTarget.find() may return null if no form is found.


Development

Environment Setup

  1. First, download all dependencies using NPM:

    npm install
  2. You can start serving a hot-reloading development server with the following command:

    npm run dev

Testing

Unit tests:

npm run test:unit

Integration tests:

npm run test:integration

On-demand integration test:

npm run test:integration <url>

# for example:
npm run test:integration https://github.com/login

VSCode Workspace Setup (optional)

Recommended Extensions:

Optimal Settings:

{
  // A listing of language IDs which should be validated by ESLint.
  // NOTE: If not installed, ESLint will show an error.
  "eslint.validate": [
    "javascript",
    "javascriptreact",
    "typescript",
    "typescriptreact"
  ],

  // ESLint rules that should be executed when computing `codeActionsOnSave`.
  // You can ignore rules using glob patterns (e.g.: "!@typescript-eslint/no-unsafe-assignment").
  "eslint.codeActionsOnSave.rules": [
    "*"
  ],

  // Code actions to be executed upon save.
  //
  // NOTE: To improve performance, code actions
  // should be "opt-in" on a per-extension basis.
  "editor.codeActionsOnSave": {
    "source.fixAll": false,
    "source.organizeImports": false,
    "source.fixAll.eslint": true,
  },
}