d147843c76
- Introduced blog routing using Next.js App Router - Implemented dynamic [slug] pages for blog posts - Added MDX-based content loading via lib/posts - Integrated shared TopBar layout with navigation - Established clear content, lib and component separation
67 lines
2.7 KiB
TypeScript
67 lines
2.7 KiB
TypeScript
/**
|
|
* A cross-platform on-disk best-effort advisory exclusive lockfile
|
|
* implementation.
|
|
*
|
|
* On Windows, this opens a file in write mode with the `FILE_SHARE_WRITE` flag
|
|
* unset, so it still allows reading the lockfile. This avoids breaking tools
|
|
* that read the contents of `.next`.
|
|
*
|
|
* On POSIX platforms, this uses `flock()` via `std::fs::File::try_lock`:
|
|
* https://doc.rust-lang.org/std/fs/struct.File.html#method.try_lock
|
|
*
|
|
* On WASM, a dummy implementation is used which always "succeeds" in acquiring
|
|
* the lock.
|
|
*
|
|
* This provides a more idiomatic wrapper around the lockfile APIs exposed on
|
|
* the native bindings object.
|
|
*
|
|
* If this lock is not explicitly closed with `unlock`, we will:
|
|
* - If `unlockOnExit` is set (the default), it will make a best-effort attempt
|
|
* to unlock the lockfile using `process.on('exit', ...)`. This is preferrable
|
|
* on Windows where it may take some time after process exit for the operating
|
|
* system to clean up locks that are not explicitly released by the process.
|
|
* - If we fail to ever release the lockfile, the operating system will clean up
|
|
* the lock and file descriptor upon process exit.
|
|
*/
|
|
export declare class Lockfile {
|
|
/**
|
|
* The underlying `Lockfile` object returned by the native bindings.
|
|
*
|
|
* This can be `undefined` on wasm, where we don't acquire a real lockfile.
|
|
*/
|
|
private bindings;
|
|
private nativeLockfile;
|
|
private listener;
|
|
private constructor();
|
|
/**
|
|
* Attempts to create or acquire an exclusive lockfile on disk. Lockfiles are
|
|
* best-effort, depending on the platform.
|
|
*
|
|
* - If we fail to acquire the lock, we return `undefined`.
|
|
* - If we're on wasm, this always returns a dummy `Lockfile` object.
|
|
*/
|
|
static tryAcquire(path: string, unlockOnExit?: boolean): Lockfile | undefined;
|
|
/**
|
|
* Attempts to create or acquire a lockfile using `Lockfile.tryAcquire`. If
|
|
* that returns `undefined`, indicating that another process or caller has the
|
|
* lockfile, then this will output an error message and exit the process with
|
|
* a non-zero exit code.
|
|
*
|
|
* This will retry a small number of times. This can be useful when running
|
|
* processes in a loop, e.g. if cleanup isn't fully synchronous due to child
|
|
* parent/processes.
|
|
*/
|
|
static acquireWithRetriesOrExit(path: string, processName: string, unlockOnExit?: boolean): Promise<Lockfile>;
|
|
/**
|
|
* Releases the lockfile and closes the file descriptor.
|
|
*
|
|
* If this is not called, the lock will be released by the operating system
|
|
* when the file handle is closed during process exit.
|
|
*/
|
|
unlock(): Promise<void>;
|
|
/**
|
|
* A blocking version of `unlock`.
|
|
*/
|
|
unlockSync(): void;
|
|
}
|