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

vtex-order-placer

v0.3.1

Published

A package to place orders in VTEX eCommerce

Downloads

12

Readme

:loudspeaker: Important

This package is still Work in progress. It's API may change until it reaches v1.

:inbox_tray: Installation

npm install vtex-order-placer

Or you can also install it globally to use as a CLI command anywhere:

npm install --global vtex-order-placer

Or you can just run it without installing:

npx vtex-order-placer

:hammer_and_wrench: Configuration file

The runtime configurations are handled by a .vtexrc file, normally created in your project root dir, or in the current directory if running with npx.

This package uses rc to load config file. It will look for it in this locations.

You can also pass options by setting env variables or passing cli arguments (see rc documentation for more details).

This are the available configuration options with it's default values:

{
  "accountName": "", // REQUIRED. The VTEX account name
  "apiKey": "", // REQUIRED. A valid API Key for your account
  "apiToken": "", // REQUIRED. A valid API Token for your account
  "customerEmail": "", // REQUIRED. The email of the customer for the order. This must be an existing customer with registered addresses
  "paymentSystemId": null, // REQUIRED. The payment system ID (Number) that should be used to place the orders
  "placedOrdersQuantity": 1, // The amount of orders you want to place
  "placedOrdersConcurrency": 1, // The amount of orders that will be placed concurrently
  "placeDifferentOrders": false, // Whether or not every order should be different from each other
  "salesChannel": 1, // The sales channel where orders will be placed
  "seller": "1", // The seller where orders will be placed
  "itemsSearchText": "", // Some text to search products that will be used for placing orders
  "itemsSearchFilter": [] // Filters to search products that will be used for placing orders.
                          // Each element of the array must be an object with two properties: `type` and `value`. `type` can be one of the following: `productId`, `skuId`, `referenceId`, `ean`, `categoryTree`, `priceRange`, `clusterId`
  "minItemsQuantity": 1, // Min quantity of different SKUs that each order must contain
  "maxItemsQuantity": 1, // Max quantity of different SKUs that each order must contain
  "interactiveShipping": false // Indicates if the logistic of each item should be selected by user or automatically
}