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-wdi5

v2.0.5

Published

a quick bootstrap for using wdi5 (wdio-ui5-service)

Downloads

575

Readme

wdi5 Logo wdi5 quickstart

Fast lane for adding wdi5 for e2e tests to your UI5 application

Quickstart

$> cd your/ui5/app
# for JavaScript projects:
$> npm init wdi5@latest
# for TypeScript projects:
$> npm init wdi5@latest -- --ts

Or, if you are working with yarn

$> yarn create wdi5@latest
$> yarn create wdi5@latest -- --ts

Or, if you are working with pnpm

$> pnpm create wdi5@latest
$> pnpm create wdi5@latest -- --ts

Note that this quickstart command is suited as a complimentary tool to yo easy-ui5!

How it works

The initializer will…

| for JavaScript | for TypeScript | | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | install wdi5 and all required WebdriverIO peer dependencies | (← same) | | assume that you're running the UI5 app with the ui5-tooling on port 8080 | (← same) | | - add a config file (wdio.conf.js) info $ui5-app/webapp/test/e2e/- assume that your tests are in $ui5-app/webapp/test/e2e/**/* and follow the name pattern *.test.js | - add the wdi5 config file (wdio.conf.ts) and a TypeScript config file (tsconfig.json ) to $ui5-app/webapp/test/e2e/- assume that your tests are in $ui5-app/webapp/test/e2e/**/* and follow the name pattern *.test.ts | | set an npm script named "wdi5" to run wdi5 so you can immediately do npm run wdi5 | (← same) |

Note that this is a minimal install for running wdi5

  • locally
  • with Chrome as target browser
  • plain JavaScript as notation
  • mocha as the syntax for tests
  • spec as the output format of the test results

The wdi5 config is already prepared for

  • --headless: runs Chrome in headless mode (npm run wdi5 -- --headless)
  • --debug: extends test timeouts and auto-opens Chrome's developer tools pane (npm run wdi5 -- --debug)

Supported Options

You can pass the following optional flags to modify the quickstart of wdi5:

  • --configPath <path to config> custom path where your config file (wdio.conf.(j|t)s) should be created
  • --specs <path to specs> custom path where your specs files are located
  • --baseUrl <application url> custom url to your application