Drive Uploady

Provides a custom React Uploady provider for uploading to Google Drive. All Uploady functionality such as hooks and components (ex: Upload-Preview) can be used with this package.

Uploads are sent to the multipart endpoint: Google Drive docs.

Note: no support for URL based uploads, only files.

Installation

#Yarn:  
   $ yarn add drive-uploady @rpldy/uploady

#NPM:
   $ npm i drive-uploady @rpldy/uploady

Props

All other Uploady props can be passed as well. See docs here.

Note: no support for concurrent > 1

Example

import React from "react";
import DriveUploady from "drive-uploady";
import UploadButton from "@rpldy/upload-button";

export const App = () => {
  return (
    <DriveUploady
      clientId="<my-client-id>"
      scope="https://www.googleapis.com/auth/drive.file"
    >
      <h2>Drive Uploady</h2>

      <UploadButton>Upload to Drive</UploadButton>
    </DriveUploady>
  );
};

Upload to folder

import React from "react";
import DriveUploady from "drive-uploady";
import UploadButton from "@rpldy/upload-button";

export const App = () => {
  return (
    <DriveUploady
      clientId="<my-client-id>"
      scope="https://www.googleapis.com/auth/drive.file"
      params={{ parents: ["folder-id"] }}
    >
      <h2>Drive Uploady</h2>

      <UploadButton>Upload to Drive</UploadButton>
    </DriveUploady>
  );
};

Authentication

By default, Drive-Uploady will load and use its own Google Authentication Provider. The process involves loading the scripts from Google:

1. https://apis.google.com/js/api.js
2. https://accounts.google.com/gsi/client

Note: Using two scripts is due to Google's deprecation decision.

Once the scripts are loaded. Internally, a TokenClient will be created (google.accounts.oauth2.initTokenClient) and will be used in order to retrieve an access token for the user.

The user will be shown a pop-up through which they can sign-in (if not already) and approve the application to access their Drive.

The application (created in the API Console) must have the right scope (ex: https://www.googleapis.com/auth/drive.file).

As long as the page isn't refreshed and the token is still valid, the user will not be prompted to approve again when uploading additional files. In case the token is expired, the user will be prompted again.

Own Authentication

In case you are already implementing your own use of the oauth flow with Google. Drive-Uploady let's you pass in a getToken method as a prop that will be used to retrieve the access token when needed.

All scripts and authentication will be assumed to have been loaded and set up separately from Drive-Uploady.

GetTokenMethod

export type AuthToken = {
  access_token: string;
  expires_in: number;
};

export type GetTokenMethod = (cb: (token: AuthToken) => void) => void;

Example use of getToken() implementation:

import React from "react";
import DriveUploady from "drive-uploady";
import UploadButton from "@rpldy/upload-button";

const getToken = (cb) => {
  const tokenClient = window.google.accounts.oauth2.initTokenClient({
    client_id: "MY-CLIENT_ID",
    scope: "MY-SCOPE",
    callback: (response) => {
      cb(response);
    },
  });

  tokenClient.requestAccessToken({ prompt: "consent" });
};

export const App = () => {
  return (
    <DriveUploady
      getToken={getToken}
    >
      <h2>Drive Uploady</h2>

      <UploadButton>Upload to Drive</UploadButton>
    </DriveUploady>
  );
};

Revoke Token

The library provides a utility function to revoke the token previously retrieved on the page:

import { revokeToken } from "drive-uploady";

const RevokeButton = () => {
	return (
    <button onClick={revokeToken}>Revoke Token</button>
  );
};