Google Drive
Google Drive for fancy-flow — as four imported, versioned packages, one per runtime. Not vendored source: a copy cannot be upgraded, and third-party APIs change.
| Runtime | Package | Install |
|---|---|---|
| Authoring surface (every host) | @particle-academy/google-drive-ui |
npm install @particle-academy/google-drive-ui |
| Node | @particle-academy/google-drive-js |
npm install @particle-academy/google-drive-js |
| PHP 8.4+ | particle-academy/google-drive-php |
composer require particle-academy/google-drive-php |
| Python 3.11+ | fancy-google-drive |
pip install fancy-google-drive |
The ui package is the editor surface and is React on every host — a PHP or
Python project installs it and its own runtime package, and never the js one.
What it costs you
One dependency: @particle-academy/fancy-connector-core (or
particle-academy/fancy-connector-core on Composer), which the js and php
packages pull in themselves. The Python package has zero runtime
dependencies.
No Google Drive SDK. Plain HTTP, deliberately: a vendor SDK is third-party code subject to the kit's full approval bar, and one per provider is hundreds of dependencies nobody is tracking.
Run it before you have credentials
Every operation ships a faker, whether or not Google Drive has a sandbox. Set a
node's mode to fake and it returns the shape Google Drive actually publishes — the
same field names, deterministically — so you can wire the downstream nodes before
touching an account, a key, or a network.
This repository is generated
provider/ is the source. Everything under packages/ is emitted from it and
must not be hand-edited — CI regenerates and diffs on every push, and the
next protocol sync destroys anything it finds. See AGENTS.md.
Two namespaces, which do not match on purpose
The repo is github.com/Fancy-Friends/google-drive; the packages publish under
particle-academy. Nothing derives one from the other — the names come from
weaver's friends.json and nowhere else.
Licence
MIT.
Metadata
Release files for fancy-google-drive 0.2.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| fancy_google_drive-0.2.0.tar.gz | 14.2 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| fancy_google_drive-0.2.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 30.6 kB
Release files / fancy_google_drive-0.2.0.tar.gz
| Download URL | fancy_google_drive-0.2.0.tar.gz |
|---|---|
| Size | 14.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d7869baef8dab158a2f9b3cbb6553ae9cc1cb19a7f5baef52fd0a7e44b2d53f1
|
|
BLAKE2b-256 checksum How to use checksums |
3e027071fe3eaa6038fac80d55f459b5e68f55b8e53fda5ca4ed1ece72712201
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.1
|
Release files / fancy_google_drive-0.2.0-py3-none-any.whl
| Download URL | fancy_google_drive-0.2.0-py3-none-any.whl |
|---|---|
| Size | 16.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
b0cc686216f70499cf7f5f976b6cc8700f6dda34cb108dc441fdb8a7b14d90b9
|
|
BLAKE2b-256 checksum How to use checksums |
9a778869bc447c49577f0e3e8e96ea0bac61643d6caad1773e0518fb52ca90af
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.1
|