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 🙏

© 2026 – Pkg Stats / Ryan Hefner

@frames/automator

v2.0.35

Published

Frames Automator

Readme

Morphis Frames Automator

Install

$ npm i @frames/automator

Usage

$ automator --help
Frames Automator v2.0.35

Usage: automator [options] [configFile]
config file defaults to frames.conf.js.

Options:
  --help, -h     prints automator help menu
  --version, -v  prints automator version
  --dir, -d      automator tests directory

Example

describe('Starts, Login and Opens a Task', () => {
    before(() => {
        frames.login()
            .assert(frames.Validations.isActive('BLOCK', 'FIELD'), 'active item is not BLOCK.FIELD');
    });
    it('Open and Exit Task', () => {
        frames.openTask('TASK_NAME')
            .navigate('BLOCK1', 'FIELD')
            .value('123').next()
            .navigate('BLOCK2', 'EXECUTE_BTN')
            .closeTask()
    });
});

Selenium Testing

Local

Download Selenium Standalone Server and started locally.

You will need the browser driver also. To get chrome working just download the latest version of ChromeDriver.

java -Dwebdriver.chrome.driver=/Users/kimus/Downloads/chromedriver \
     -jar ~/Downloads/selenium-server-standalone-3.4.0.jar

Docker

Using the Selenium Docker project to provide a local Selenium standalone server hub and node configurations with Chrome and Firefox.

$ docker run -d --name selenium -p 4444:4444 selenium/standalone-chrome

To stop container:

$ docker stop selenium

To start the container again:

$ docker start selenium

Maintainers

For start developing in Frames Automator you will need to start the watch process in a terminal for building the javascripts on write like this:

$ npm run watch

If you change the root index.js you will need to build it like this:

$ npm run compile:index

Testing

../bin/automator -d sample <configFile>

Changelog

2.0.35

  • Added support to setting combobox value using option index
  • Fixed navigation to radio buttons in repeaters
  • Added new API method "clickTabPage" that navigates to any tabpage given its ID

2.0.34

  • Added support to multiselect in grids and listboxes
  • Added support to toggle workspace menus (Tools and Related)
  • Improved clickMenuItem API to use the menu entry's relative index
  • Added support to export action