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

rqe-core-common

v0.0.0

Published

Common Core Functions for the RQE platform

Downloads

3

Readme

IFS RQE Javascript Library Template

This repo is a template repo to create a Vanilla Javascript Library using Rollup JS as the packager, ESLint for linting, and Karma/Jasmine for running unit tests. One should be able to use this as a template, run npm install and be ready to go. To ensure that all of your code is exported and built (not tree shaken out), it must be included in the main.ts file. See example code.

Once you have created a repo from the template, update the README, package.json file, and LICENSE file appropriately. If you thing there is something we should add to the template, please create a PR.

All peerDependencies and dependencies are automatically made to be externals as part of the rollup build. They will need to be installed by the consuming app if peerDependencies. Regular dependencies are automatically installed by NPM, but their use is discourage as you can have package version conflicts.

Global NPM packages to install on your box#

These packages should be installed globally for convenience.

  • Rollup: npm install rollup -g
  • Karma CLI: npm install karma-cli -g

Commands

These commands should not be changed to enforce consistency across the libraries. If you believe there is something that should be added as a standard build command, plese branch and submit a PR for consideration.

  • npm run lint-lib Lint the library
  • npm run test-lib Run Karam/Jasmine Unit Tests
  • npm run build-lib Builds the library using rollup and places in the \dist\ folder
  • npm run publish-patch Will automatically increment the patch number, push to npm, and commit and tag github repo
  • npm run publish-minor Will automatically increment the patch number, push to npm, and commit and tag github repo
  • npm run publish-major Will automatically increment the patch number, push to npm, and commit and tag github repo