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

@pantheon-systems/pcc-cli

v3.10.0-beta.1

Published

Pantheon Content Cloud CLI

Downloads

328

Readme

Installation

npm

npm install @pantheon-systems/pcc-cli --global

yarn

yarn add @pantheon-systems/pcc-cli --global

Usage

# Login the user
$ pcc login

# Create project with nextjs template
$ pcc init new_proj

# Create project with gatsby template
$ pcc init new_proj --template=gatsby

# Create project using pnpm package manager
$ pcc init new_proj --use-pnpm

# Create Typescript project and setup ESLint in it
$ pcc init new_proj --ts --eslint

# Create project without installing dependencies
$ pcc init new_proj --noInstall

# Create project and provide site ID to pre-populate .env file with
$ pcc init new_proj --site-id 123456789example1234

# Create new token
$ pcc token create

# Create new site
$ pcc site create --url test-site.com

# Get webhooks event delivery logs for a site ID
$ pcc site webhooks history 123456789example1234

# Generate preview link for given document ID
$ pcc document preview 1234567890example1234567890exam_ple123456789

# Generate preview link for given document URL
$ pcc document preview https://docs.google.com/document/d/1234567890example1234567890exam_ple123456789

# Get details of logged-in user
$ pcc whoami

# Logout the user
$ pcc logout

Import existing content from a Drupal site

You must ensure that the JSON API for your Drupal site is enabled (which it should be by default). https://www.drupal.org/docs/core-modules-and-themes/core-modules/jsonapi-module/api-overview

Once you've ensured that it's working, you will need to determine the URL which PCC can use to get the initial results page of posts (e.g. https://example.com/jsonapi/node/article). But please note that the exact URL will depend on which resource type(s) you want to import.

The second and last piece of information you will need before proceeding to import, is the id of the PCC site which the posts should be imported into. Posts are NOT going to be published automatically after importing, but they will be automatically connected to the site id provided.

With this information, you can now run the import command.

$ pcc import drupal https://example.com/jsonapi/node/article siteid12345