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

wct-none

v0.1.1

Published

WCT plugin for not running a browser

Downloads

10

Readme

wct-none Build Status

A plugin for web-component-tester that provides a dummy browser.

The intent for this plugin is to make it possible to start the WCT webserver, but not waste any resources on starting a browser for tests. Instead the user can start whatever testing/debugging environment they want manually.

Example using Visual Studio as debugger

This examples show hows to use Visual Studio Code and the Debugger for Chrome plugin to debug a component's test.

  1. Install web-component-tester and the wct-none plugin into the project

    npm install --save-dev web-component-tester wct-none

    It is safe to save the plugin as development dependency in package.json, it will do nothing unless explicitly activated.

  2. Create or modify .vscode/launch.json in the project

    {
        "version": "0.2.0",
        "configurations": [
             {
                 "type": "node",
                 "request": "launch",
                 "name": "Run wct",
                 "program": "${workspaceRoot}/node_modules/.bin/wct",
                 "args": [
                     "-p",
                     "--skip-plugin", "local",
                     "--plugin", "none",
                     "--webserver-port", "2000",
                     "--expanded",
                     "--simpleOutput",
                     "path/to/tests"
                 ]
             },
             {
                 "type": "chrome",
                 "request": "launch",
                 "name": "Run chrome for wct",
                 "url": "http://localhost:2000/components/COMPONENT_NAME/generated-index.html",
                 "webRoot": "${workspaceRoot}",
                 "userDataDir": "${workspaceRoot}/.vscode/chrome"
             }
        ]
    }

    Note that you must replace COMPONENT_NAME in the URL for Chrome, and path/to/tests with the path to the root of the test suite.

  3. Enable the debug.allowBreakpointsEverywhere setting in the user or workspace preferences

    This makes it possible to set breakpoints everywhere, and let's Chrome work out how to best do that.

  4. Launch the 'Run wct' configuration

    This will log an error about not being able to connect to 127.0.0.1:4444, which can be ignored. PR's welcome :)

  5. Launch the 'Run chrome for wct' configuration

  6. Set breakpoints etc inside Visual Studio

License

This software is licensed under the Apache 2 license, quoted below.

Copyright 2017 Collaborne B.V. <http://github.com/Collaborne/>

Licensed under the Apache License, Version 2.0 (the "License"); you may not
use this file except in compliance with the License. You may obtain a copy of
the License at

    http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS, WITHOUT
WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the
License for the specific language governing permissions and limitations under
the License.