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

@forcloud/client

v7.2.2

Published

Client for Portive API

Downloads

6

Readme

@forcloud/client

Usage

import { creatAuthToken } from "@forcloud/auth"
import { Client, uploadFile } from "@forcloud/client"

const authToken = createAuthToken(API_KEY, {
  path: "on/$yyyy/$mm/$dd",
  expiresIn: "1h",
})

const client = new Client({ authToken, apiOrigin })

const uploadResult = await uploadFile({
  client,
  file,
  onProgress(e) {
    console.log(e)
  },
})

Design Strategy

  • Separate auth and client: Keep @forcloud/auth separate from @forcloud/client because once we've developed a component, we don't need to import @forcloud/client explicitly anymore.
  • authToken option always provided on Component: When a Component is created that uses Portive, it needs to take authToken as part of its arguments. It is not necessary to take apiOrigin because that is only required if you aren't hitting the production endpoint. When an end-developer uses the Component, they will likely never be hitting a non-production endpoint.
  • Don't pass in Client to Component: Because authToken is the only necessary argument, we don't ask the Component user to pass in a Client. It's an unnecessary extra step.
  • Do have a Client object though. That being said, we do have a Client object that needs to be created. We have this because it helps the Component developer in these ways:
    1. It's obvious what options should be passed in to the Component. It is all the options on the Client object. For example, it takes authToken but taking an apiOrigin as optional and perhaps a path as optional will be really helpful as well.
    2. By forcing the Component developer to create a Client object, it will be more likely that the Component developer will create the Client object during the initialization phase and then all the options will be passed properly whenever an API call is made. For example, let's say we have the uploadFile call but also a collaborate call. We don't want to introduce an error like forgetting to pass the apiOrigin to collaborate even though we've passed it through to uploadFile. After using the options to create a new Client, we don't have to worry about forgetting to pass through correct options through.