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

create-locator

v0.0.25

Published

Creates HTML element locators for tests πŸ“Œ

Downloads

267

Readme

create-locator πŸ“Œ

NPM version dependencies: none minzipped size code style: prettier Conventional Commits License MIT

The create-locator πŸ“Œ library allows you to mark HTML elements with locators and find these elements by their locators in tests.

Marking an HTML element with a locator in the application code looks like this (example in JSX):

export const Foo = () => {
  return <div {...locator('foo')}>HelloπŸ‘‹ world!</div>;
};

In the browser, this element will render into the following DOM structure:

<div data-testid="foo">HelloπŸ‘‹ world!</div>

In tests you can use locators in this way (example in Playwright):

await locator('foo').click();

Install

npm install create-locator

Usage

The first argument of the locator function is called the locator's testId. Typically, it’s a unique string that allows you to find the element marked by the locator in tests.

The locator can also have an optional set of arbitrary parameters (only the line with the locator is shown):

<div {...locator('foo', {bar: 'baz'})}>

This element with the locator will render into the following DOM structure:

<div data-testid="foo" data-test-bar="baz">

The values of the parameters can also be numbers and boolean values:

<div {...locator('foo', {bar: true, baz: 12})}>

This will render as:

<div data-testid="foo" data-test-bar="true" data-test-baz="12">

Parameters with null and undefined values will be omitted:

<div {...locator('foo', {bar: null, baz: undefined, qux: false})}>

This will render as:

<div data-testid="foo" data-test-qux="false">

The testId of the locator can consist of multiple parts, including numbers and boolean values:

<div {...locator('foo', 'qux', 3)}>

This will render as:

<div data-testid="foo-qux-3">

An object with parameters can also follow several parts of the testId:

<div {...locator('foo', 'qux', 3, {bar: true, baz: 12})}>

This will render as:

<div data-testid="foo-qux-3" data-test-bar="true" data-test-baz="12">

The ability to specify a testId composed of multiple parts is useful for dynamic components, which can accept an optional testId string property in their props:

type Properties = {..., testId?: string};

export const Button = ({..., testId}: Properties) => (
  <label {...locator(testId, 'label')}>
    <button {...locator(testId, 'button')}>{/* ... */}</button>
  </label>
)

For example, with testId="submitButton", this will render into the following DOM structure:

<label data-testid="submitButton-label">
  <button data-testid="submitButton-button">{/* ... */}</button>
</label>

License

MIT