This plugin creates a dependency graph between collections and globals. The graph updates automatically, because the plugin observes the changes made on any collection or globals.
Installation
npm i payload-dependency-graph14
Stars
0
Forks
1
Open Issues
2 years ago
Last Updated
2
Weekly Downloads
v2.3.0
npm Version
145.7 KB
Unpacked Size
0
Dependencies
Trends appear after 7 days of data. Daily snapshots have not started yet.
Trends appear after 7 days of data. Daily snapshots have not started yet.
Each point is npm's rolling 7-day download count.
Health Score
Composite score based on GitHub activity, stars, npm downloads, publish recency, dependency count, and package size.
Badge for your README
[](https://payloaddirectory.dev/plugins/698381771-root)<a href="https://payloaddirectory.dev/plugins/698381771-root"><img src="https://payloaddirectory.dev/badge/698381771-root.svg" alt="Payload Directory"></a>README
# Payload Dependency Graph Plugin [](https://badge.fury.io/js/payload-dependency-graph) [](https://github.com/GeorgeHulpoi/payload-dependency-graph/actions/workflows/test.yml) [](https://www.npmjs.com/package/payload-dependency-graph)
# Payload Dependency Graph Plugin [](https://badge.fury.io/js/payload-dependency-graph) [](https://github.com/GeorgeHulpoi/payload-dependency-graph/actions/workflows/test.yml) [](https://www.npmjs.com/package/payload-dependency-graph) This plugin creates a dependency graph between collections and globals. The graph updates automatically, because the plugin observes the changes made on any collection or globals. This plugin is created and maintained by [gvhdev.com](https://gvhdev.com). ## Use Cases The plugin is useful when it comes to cached content or relationship-based changes. - You're caching a static page that uses nested relationship fields. If the page has fields with blocks, and these blocks are recursive and have their own relationship fields, it can be difficult to know which cache needs to be purged. For this situation, the plugin is perfect for knowing which resource is dependent on whom. - You're caching the API responses that contain a depth greater than 0. You can purge that cache for that specific resource when its dependencies change. ## [Documentation and API](https://georgehulpoi.github.io/payload-dependency-graph/)
payload upstash
Upstash Redis key-value adapter for Payload's built-in KV store
690/wk7v3
payload revalidate
Field-driven Next.js cache revalidation and tagged cached finders for Payload collections and globals
67151/wk18v3
payload plugin switch env
Switch between production and development databases or copy production data to development from the Payload admin
430/wk5v3
payloadcms redis cache
Redis client helper for caching Payload collection data in Next.js apps
410/wk2v?
payloadcms redis plugin
Transparent Redis caching layer for Payload database read queries with automatic invalidation on writes
400/wk15v3
cached local api
Cache Payload Local API operations with Next.js unstable_cache and automatic tag revalidation
380/wk334v3