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 🙏

© 2026 – Pkg Stats / Ryan Hefner

aqopi-summary-to-omniplan

v0.1.4

Published

The project is tested using unit tests. These tests are automatically executed before increasing the package version (using `npm version`) and before publishing, to ensure that things don't unexpectedly break between releases. The unit tests can be found

Downloads

28

Readme

Testing

The project is tested using unit tests. These tests are automatically executed before increasing the package version (using npm version) and before publishing, to ensure that things don't unexpectedly break between releases. The unit tests can be found in the test folder. Every .spec.ts file in the test folder is executed during a test.
To manually execute the tests run npm test.

Running a single test

You can run a single test by replacing: it('Should...' ()=>true) with: it.only('Should...' ()=>true)

Build

Builds are automatically executed before publishing and should not need to be done manually. If for whatever reason a manual build is required, a build can be executed by running npm run build.

Publishing

To publish a new version use: npm publish. This will build and publish the package to the npm repository and also deploy a new version to S3 (production). It is also possible to only deploy to S3, however this is to be avoided for production.
To only deploy to S3 use: npm run publish-s3 -- [--env <env>] [--profile <profile>]. Env is the target environment, acct for acceptance and prod for production, will default to acct.

Known issue, deploy script naar prod lijkt niet te werken.

using the library in the browser

<script src="https://parser-prod.aqopi.com/omniplan/aqopi-summary-to-omniplan.min.js"></script>

or

<script src="https://parser-acct.aqopi.com/omniplan/aqopi-summary-to-omniplan.min.js"></script>

...

// Get util
const AqopiSummaryToOmniplan = window.aqopi.omniplan;

// Generate Omniplan dossier
const dossier = await AqopiSummaryToOmniplan.transform(summary, partnerSummary);