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

labking

v1.5.0

Published

A LabKey module to allow creation and editing of Study module datasets in a subject-centric way

Downloads

23

Readme

LabKing :crown:

Rule over your subjects in LabKey

Build Status Coverage Status

Building the project

The build process does a few things:

  1. Compiles your ES6 JavaScript into a single ES5-compatible file in the web resources directory (this is what you reference in your HTML).
  2. Copies your HTML over into the target.
  3. Generates a module.xml file for LabKey.
  4. Generates WebParts and View XML files based on the webParts and webViews attributes in package.json.
  • npm build builds the module
  • npm test runs the test suite
  • npm watch watches for changes and builds each time

These are really just wrappers for Gulp (gulp, gulp test, and gulp watch respectively).

Creating Web Parts

  1. Create a WebPart definition in package.json, e.g. for sample.html:

        "webParts": [
            { "name": "WebPart Friendly Name",  "htmlFilePrefix": "sample" }
        ]
  2. Create views/sample.html:

    <div>
    <h1>Hello World!</h1>
    </div>

Browser requirements

LabKing is unapologetically built for the modern world. You'll need IE9+, or a reasonably up-to-date version of Chrome, Firefox, Opera, or similar to make the most of it. You may find it works on IE8, and we'd love to hear your experiences to flesh out the documentation. More than that, we'd love for you to upgrade to a modern browser for general happiness :cocktail: :beers: :wine_glass:.

License

This project is MIT licensed.

Contributing

We'd love to get your feedback, pull requests and contributions. There are some notes on contributing.