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

@adobe/commerce-cif-commercetools-product

v1.2.1

Published

Adobe Commerce Integration Framework (CIF REST) Commercetools Integration Product Project

Downloads

17

Readme

CIF REST products services for commercetools

This package contains the actions of the /products API endpoints.

To deploy all the actions in a shared Openwhisk package, make sure that you currently have a .wskprops file with the credentials of a user/namespace meant to deploy shared packages, and simply call npm run deploy-package.

This will create a shared package called name@version where the name and version fields are taken from the current package.json file. For example, it would create a shared package called [email protected] at the time of writing this documentation.

It will also create a shared package called commercetools-products-actions@latest which always points to the latest version of the actions. This concept is borrowed from the latest tag concept of npm. The latest package is used by the customer-deployment example project.

To remove all the actions and packages, simply call npm run remove-package.

Important: the actions in the shared package are not meant to be used directly. A customer should create a package binding with the right Commercetools credentials, and a package with web actions/sequences. See the customer-deployment example project to see how a customer would typically use that shared package.