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

@webiny/api-headless-cms

v5.41.1

Published

GraphQL API for Webiny Headless CMS.

Downloads

4,641

Readme

@webiny/api-headless-cms

code style: prettier PRs Welcome

Install

npm install --save @webiny/api-headless-cms

Or if you prefer yarn:

yarn add @webiny/api-headless-cms

Testing

Due to possibility of multiple storage operations, the tests are completely decoupled from those storage operations.

The jest.setup.js is using @webiny/project-utils/testing/presets.js to find and load all the packages containing @webiny/api-headless-cms and storage-operations keywords in their package.json file. Those packages are then used to build the test run - one for each of the packages. So depending on how many storage operations there are in the repository, that much of api-headless-cms tests will run.

Defining test environment

To make it possible for api-headless-cms tests to run with a storage operations package you MUST create presets.js file in storage-operations-package-path/__tests__/__api__/ directory. That file is loaded when setting up the api-headless-cms tests.

It MUST contain the testEnvironment variable which contains path to the environment definition file.

That environment file MUST define the test environment which extends NodeEnvironment class.

Test environment MUST expose __getStorageOperationsPlugins method, via this.global property of the class, which will load the required plugins in the api-headless-cms tests.

Examples of preset and test environment files

The first implementation of the decoupled storage operations is DynamoDB/Elasticsearch, which you can find in @webiny/api-headless-cms-ddb-es. Files which you can check to help you define your own presets and test environment are:

  • presets.js - an array of presets of which last one defines the environment to be loaded
  • environment.js - a class which extends NodeEnvironment and exposes __getStorageOperationsPlugins to the tests

Debugging when testing

For the WebStorm (PhpStorm,...) when starting a test you must have some values defined in the run/debug configurations screen:

Node options

--inspect=9229

Working directory

PATH_TO_YOUR_PROJECT_ROOT

example:

~/webiny/webiny-js/

Jest options

For DynamoDB + Elasticsearch storage operations tests:

--keyword=cms:base --keyword=cms:ddb-es

For the DynamoDB storage operations tests:

--keyword=cms:base --keyword=cms:ddb

Note that base keyword is the cms:base. It tells Jest setup to load the api-headless-cms tests with the api-headless-cms-ddb-es tests.

Environment variables

If you want to use local Elasticsearch:

ELASTICSEARCH_PORT=9200;LOCAL_ELASTICSEARCH=true

Nothing if you do not want to use the local Elasticsearch.