Home

Published

- 1 min read

Hashnode Sync

portfolio
img of Hashnode Sync

A CLI that syncs a folder of local markdown files to Hashnode. I built it in a day for the Hashnode GraphQL hackathon because I wanted “content-as-code” for blogging.

TL;DR

  • Content-as-code workflow: edit locally, run one command, post updates remotely.
  • The nice trick: a Proxy that auto-persists state whenever you mutate the config object.

Tech Stack: Node.js GraphQL npm

The trick: state that saves itself

The CLI needs to remember sync state between runs - which files were synced, their Hashnode IDs, content hashes. The typical approach: manual read/write calls everywhere.

Instead, I wrapped the config object in a JavaScript Proxy. Any property change automatically persists to disk:

function getSyncedJson(path) {
	const obj = JSON.parse(fs.readFileSync(path))
	return new Proxy(obj, {
		set(target, property, value) {
			Reflect.set(target, property, value)
			saveJsonFile(path, target) // Auto-persist on any change
			return true
		}
	})
}

Now config.lastSync = Date.now() just works - no explicit save calls. The codebase got much simpler.

Change detection

SHA-256 hashing on file content + metadata. Only files with changed hashes trigger API calls. No diff logic needed - if the hash matches, skip it.

What it does

  • Watches a folder of markdown files
  • Detects new/changed/deleted posts
  • Syncs to Hashnode via their GraphQL API
  • One command: hashnode-sync

Published on npm. Content-as-code workflow for blogs.